METHOD, GROUP SERVER, AND MEMBER DEVICE FOR ACCESSING MEMBER RESOURCES

• US 20140369251A1
• Filed: 06/16/2014
• Published: 12/18/2014
• Est. Priority Date: 01/06/2012
• Status: Active Grant

• Current Assignee: Huawei Cloud Computing Technologies Company Limited (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Zhang, Yongjing
• Granted Patent: US 9,450,772 B2
• Time in Patent Office: Days
• US Class Current: 370/312
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 12/1877 Measures taken prior to transmission
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

The present invention provides a method, a group server, and a member device for accessing member resources. By using an established mapping relationship between a multicast address and a fanout URI in a group resource, a member resource access request may be sent by multicast to member devices having member resources in the group resource, and the fanout URI is included in the member resource access request, so that the member devices having the member resources execute, according to access paths of the member resources on the member devices as indicated by the fanout URI, an operation indicated by the member resource access request. Therefore, the group server does not need to unicast the access request to each member device, and network overheads are saved.

Claims

1. A method for accessing member resources, the method comprising:

receiving a request for accessing member resources, wherein the request for accessing member resources carries a group resource identifier of a group resource to which the member resources belong;

obtaining, according to the group resource identifier, a fanout universal resource identifier URI corresponding to the member resources in the group resource and a multicast address corresponding to the fanout URI, wherein the fanout URI is used to indicate access paths of the member resources on member devices; and

sending, according to the multicast address, a member resource access request to the member devices having the member resources, wherein a destination URI of the member resource access request comprises the fanout URI corresponding to the member resources, so that the member devices having the member resources execute, according to the access paths of the member resources on the member devices as indicated by the fanout URI, an operation indicated by the member resource access request.

2. The method according to claim 1, further comprising:

receiving a group resource creation request, wherein the group resource creation request carries each member resource, and the member resources comprise member devices having the member resources and access paths of the member resources on the member devices; and

allocating a multicast address to the member resources according to the member devices having the member resources and the access paths of the member resources on the member devices, and establishing a mapping relationship between the multicast address and the fanout URI according to the access paths of the member resources on the member devices.

3. The method according to claim 2, wherein allocating a multicast address to the member resources according to the member devices having the member resources and the access paths of the member resources on the member devices, and establishing a mapping relationship between the multicast address and the fanout URI according to the access paths of the member resources on the member devices, comprises:

allocating a multicast address to member resources having a same access path on the member devices, and establishing a mapping relationship between the multicast address and the fanout URI, wherein the fanout URI is the access path of the member resources on the member devices; and

/or

allocating a virtual identifier to at least one member resource having a different access path on a member device, allocating a multicast address to the at least one member resource, establishing a mapping relationship between the multicast address and the virtual identifier and a mapping relationship between the virtual identifier and the member resource, and setting the virtual identifier to the fanout URI.

4. The method according to claim 2, further comprising:

sending, according to the mapping relationship between the multicast address and the fanout URI, a group advertisement for joining a multicast group to the member devices having the member resources, wherein the group advertisement for joining the multicast group carries the multicast address, so that the member devices having the member resources join, according to the group advertisement for joining the multicast group, the multicast group corresponding to the multicast address.

5. The method according to claim 4, wherein:

the group advertisement for joining the multicast group further carries a mapping relationship between the fanout URI and the member resources, so that the member devices having the member resources store the mapping relationship between the fanout URI and the multicast address and a mapping relationship between the member resources and the multicast address; and

the executing, by the member devices having the member resources, according to the access paths of the member resources on the member devices as indicated by the fanout URI, an operation indicated by the member resource access request is specifically as follows;

after receiving the access request carrying the fanout URI, determining, by the member devices having the member resources, according to the received fanout URI and the mapping relationship between the fanout URI and the member resources, the access paths of the member resources on the member devices, and executing, according to the determined access paths of the member resources on the member devices, an operation indicated by the member resource access request.

6. The method according to claim 1, wherein after obtaining, according to the group resource identifier, the fanout URI corresponding to the member resources in the group resource and the multicast address corresponding to the fanout URI, the method further comprises:

setting a destination address of the request for accessing member resources to the multicast address corresponding to the fanout URI, and setting a destination URI of the request for accessing member resources to the fanout URI corresponding to the member resources to generate a member resource access request; and

using the multicast address to send the member resource access request carrying the fanout URI corresponding to the member resources.

7. The method according to claim 1, wherein after obtaining, according to the group resource identifier, the fanout URI corresponding to the member resources in the group resource and the multicast address corresponding to the fanout URI, the method further comprises:

determining that a destination URI in the request for accessing member resources further comprises a suffix; and

setting a destination address of the request for accessing member resources to the multicast address corresponding to the fanout URI, setting the destination URI to the fanout URI corresponding to the member resources, and adding the suffix comprised in the destination URI to the fanout URI to generate a member resource access request.

8. The method according to claim 2, further comprising:

receiving a group resource update request for adding member resources, wherein the group resource update request for adding member resources carries the group resource identifier and member resources that need to join the group resource, and the member resources that need to join the group resource comprise member devices having the member resources and access paths of the member resources on the member devices; and

determining, according to the group resource identifier, that the access paths of the member resources that need to join the group resource on the member devices are the same as the fanout URI in the mapping relationship between the multicast address and the fanout URI in the group resource corresponding to the group resource identifier, and sending a group advertisement for joining the multicast group to the member devices having the member resources that need to join the group resource, wherein the group advertisement for joining the multicast group carries the multicast address in the mapping relationship between the multicast address and the fanout URI, so that the member devices having the member resources that need to join the group resource join the multicast group according to the multicast address and receive a member resource access request sent according to the multicast address;

or

determining, according to the group resource identifier, that the access paths of the member resources that need to join the group resource on the member devices are different from the fanout URI in the mapping relationship between the multicast address and the fanout URI in the group resource corresponding to the group resource identifier;

adding the member resources that need to join the group resource to the mapping relationship between the fanout URI and the member resources in the group resource corresponding to the group resource identifier, and sending a group advertisement for joining the multicast group to the member devices having the member resources that need to join the group resource, wherein the group advertisement for joining the multicast group carries the mapping relationship between the multicast address and the fanout URI in the group resource corresponding to the group resource identifier and the mapping relationship between the fanout URI and the member resources in the group resource corresponding to the group resource identifier, so that upon reception of the access request carrying the fanout URI, the member devices determine, according to the received mapping relationship between the fanout URI and the member resources, the access paths of the member resources on the member devices, and execute a corresponding member resource access request according to the determined access paths of the member resources on the member devices.

9. A method for accessing member resources, the method comprising:

receiving a member resource access request sent by a group server, wherein the member resource access request is a multicast member resource access request, and the member resource access request comprises a fanout URI corresponding to a member resource, wherein the fanout URI is used to indicate an access path of the member resource on a member device; and

determining, according to the fanout URI, the access path of the member resource on the member device, and executing, according to the access path of the member resource on the member device, an operation indicated by the member resource access request.

10. The method according to claim 9, further comprising:

receiving a group advertisement for joining a multicast group, wherein the group advertisement for joining the multicast group carries a multicast address, and joining, according to the group advertisement for joining the multicast group, the multicast group corresponding to the multicast address.

11. The method according to claim 10, wherein the group advertisement for joining the multicast group carries a mapping relationship between the fanout URI and the member resource, and the method further comprises:

storing a mapping relationship between the multicast address and the fanout URI and a mapping relationship between the member resource and the multicast address.

12. The method according to claim 9, further comprising:

receiving a group advertisement for leaving the multicast group, wherein the group advertisement for leaving the multicast group carries the multicast address corresponding to the multicast group that the member resource needs to leave and the member resource that needs to leave the group resource, and the member resource that needs to leave comprises the member device having the member resource that needs to leave the group resource and the access path of the member resource on the member device;

deleting the stored member resource that needs to leave the group resource in the multicast group information corresponding to the multicast address same as the multicast address in the group advertisement for leaving the multicast group; and

deleting the stored multicast group information corresponding to the multicast address same as the multicast address in the group advertisement for leaving the multicast group, and leaving the multicast group corresponding to the multicast address in the group advertisement for leaving the multicast group.

13. A group server, comprising:

a receiving module, configured to receive a request for accessing member resources, wherein the request for accessing member resources carries a group resource identifier of a group resource to which the member resources belong;

an obtaining module, configured to obtain, according to the group resource identifier, a fanout URI corresponding to the member resources in the group resource and a multicast address corresponding to the fanout URI, wherein the fanout URI is used to indicate access paths of the member resources on member devices; and

a sending module, configured to send, according to the multicast address, a member resource access request to the member devices having the member resources, wherein a destination URI of the member resource access request comprises the fanout URI corresponding to the member resources, so that the member devices having the member resources execute, according to the access paths of the member resources on the member devices as indicated by the fanout URI, an operation indicated by the member resource access request.

14. The group server according to claim 13, wherein:

the receiving module is further configured to receive a group resource creation request, wherein the group resource creation request carries each member resource, and the member resources comprise member devices having the member resources and access paths of the member resources on the member devices; and

the group server further comprises a processing module, configured to allocate a multicast address to the member resources according to the member devices having the member resources and the access paths of the member resources on the member devices, and establish a mapping relationship between the multicast address and the fanout URI according to the access paths of the member resources on the member devices.

15. The group server according to claim 14, wherein:

the processing module is specifically configured to allocate a multicast address to member resources having a same access path on the member devices, and establish a mapping relationship between the multicast address and the fanout URI, wherein the fanout URI is the access path of the member resources on the member devices; and

/or

configured to allocate a virtual identifier to at least one member resource having a different access path on a member device, allocate a multicast address to the at least one member resource, and establish a mapping relationship between the multicast address and the virtual identifier and a mapping relationship between the virtual identifier and the member resource, and set the virtual identifier to the fanout URI.

16. The group server according to claim 14, wherein:

the sending module is further configured to send, according to the mapping relationship between the multicast address and the fanout URI, a group advertisement for joining a multicast group to the member devices having the member resources, wherein the group advertisement for joining the multicast group carries the multicast address, so that the member devices having the member resources join, according to the group advertisement for joining the multicast group, the multicast group corresponding to the multicast address.

17. The group server according to claim 14, wherein:

the processing module is further configured to determine that a destination URI in the request for accessing member resources further comprises a suffix; and

set a destination address of the request for accessing member resources to the multicast address corresponding to the fanout URI, set the destination URI in the request for accessing member resources to the fanout URI corresponding to the member resources, and add the suffix comprised in the destination URI to the fanout URI to generate a member resource access request.

18. A member device, comprising:

a receiving module, configured to receive a member resource access request sent by a group server, wherein the member resource access request is a multicast member resource access request, the member resource access request comprises a fanout URI corresponding to the member resource, and the fanout URI is used to indicate an access path of the member resource on the member device; and

an operating module, configured to determine, according to the fanout URI, the access path of the member resource on the member device, and execute an access request operation according to the access path of the member resource on the member device.

19. The member device according to claim 18, wherein the receiving module is further configured to:

receive a group advertisement for joining a multicast group, wherein the group advertisement for joining the multicast group carries a multicast address; and

join, according to the group advertisement for joining the multicast group, the multicast group corresponding to the multicast address.

20. The member device according to claim 18, wherein the group advertisement for joining the multicast group carries a mapping relationship between the fanout URI and the member resource, and the member device further comprises:

a storing module, configured to store a mapping relationship between the fanout URI and the multicast address and a mapping relationship between the member resource and the multicast address.