WO2013127145A1 - 针对群组资源的操作方法、群组服务器 - Google Patents

针对群组资源的操作方法、群组服务器 Download PDF

Info

Publication number
WO2013127145A1
WO2013127145A1 PCT/CN2012/078742 CN2012078742W WO2013127145A1 WO 2013127145 A1 WO2013127145 A1 WO 2013127145A1 CN 2012078742 W CN2012078742 W CN 2012078742W WO 2013127145 A1 WO2013127145 A1 WO 2013127145A1
Authority
WO
WIPO (PCT)
Prior art keywords
operation request
resource
identifier
group
member resource
Prior art date
Application number
PCT/CN2012/078742
Other languages
English (en)
French (fr)
Inventor
高莹
金雷
张永靖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP12869697.8A priority Critical patent/EP2706729A4/en
Publication of WO2013127145A1 publication Critical patent/WO2013127145A1/zh
Priority to US14/145,844 priority patent/US8918528B2/en
Priority to US14/546,293 priority patent/US9438601B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/104—Grouping of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1014—Server selection for load balancing based on the content of a request
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the field of Machine-to-Machine Communications (M2M) technology, and more particularly to a group resource method, a group server.
  • M2M Machine-to-Machine Communications
  • Machine-to-Machine Communications is a networked application and service centered on machine intelligent interaction.
  • M2M technology enables data communication without manual intervention by embedding wireless or wired communication modules and application processing logic inside the machine to meet the information needs of users for monitoring, command scheduling, data acquisition and measurement.
  • a communication method for group resources is described.
  • each application or the first data object running on the M2M application, the M2M platform, the M2M terminal, the M2M gateway, and the M2M terminal and the M2M gateway is regarded as a REpresentational State Transfer style.
  • the RESTful resource, and the Universal Resource Identifier (URI) identifies the application or the data object, and performs group operations on the multiple resources by constructing various group resources.
  • URI Universal Resource Identifier
  • the user may need to perform the same operation on the member resources such as the M2M terminal or the gateway included in the group resource by creating a group.
  • the group resource created above is also a resource, and the group resource includes a resource of the group resource itself and a member resource included in the group resource.
  • the resource of the group resource itself may be the identifier of the group resource, the group server to which it belongs, the status (such as whether it is a stateful group resource), and the member resources included in the group resource may be a list of member resources.
  • the member resources in the M2M group resource may belong to the local group server or may belong to the remote group server.
  • two group resources may be member resources of each other.
  • a zone police station can set a monitoring group of a neighboring cell to include monitoring groups of each other, and when an alarm occurs, it can support each other according to actual conditions; for example, in a future smart home system, Users can manage the home appliances (such as lights, doors and windows, meter reading, etc.). If the children consider that their parents are older, they can nest their parents' home appliances to help them manage. It rains to help close the window.
  • the operation request sent to the group resource may be cyclically sent in the group resource included in the mutual, and when the same member resource is simultaneously included in at least two group resources. There is a possibility that an operation request for the at least two group resources may be repeatedly executed for the member resource.
  • the operation method for the group resource, the group server, and the device for performing the operation for the group resource provided by the embodiment of the present invention can avoid repeated processing or loop processing on the operation request of the member resource.
  • An aspect of the present invention provides an operation method for a group resource, including: receiving an operation request for a member resource; generating, by the operation request for the member resource, a first operation request identifier; and the member to which the member resource belongs The device sends a first member resource operation request, where the first member resource operation request includes the first operation request identifier, so that the member device to which the member resource belongs determines the operation stored by the member device according to the first operation request identifier. Whether the first operation request identifier is included in the request identifier, and processing the member resource operation request according to the judgment result.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; before the generating the first operation request identifier for the operation request for the member resource, the method further includes: Determining, according to the group resource identifier, a first operation request identifier to be generated for the operation request of the pair of member resources.
  • the determining, according to the group resource identifier, that the first operation request identifier is to be generated for the operation request for the member resource includes: determining, according to the group resource identifier, the group resource identified by the group resource identifier The sub-group resource is included as a member resource; it is determined that the first operation request identifier needs to be generated for the operation request for the member resource.
  • the determining, according to the group resource identifier, that the first operation request identifier is to be generated for the operation request for the member resource is: determining, according to the group resource identifier, the group identified by the group resource identifier The sub-group resource included in the resource is a remote group resource, or the member resource included in the group resource identified by the group resource identifier is determined by the group resource identifier to be included in the group resource identifier.
  • Group resource determine that a first operation request identifier needs to be generated for an operation request for a member resource.
  • the method before the generating the first operation request identifier for the operation request for the member resource, the method further includes: determining that the operation request for the member resource is an update request.
  • the method further includes: receiving a second member resource operation request, where the second member resource operation request includes a second operation request identifier; determining that the stored operation request identifier list includes the second operation request identifier, The indicated operation returns an error response to the sender of the second member resource operation request, or determines that the stored operation request identifier list does not include the second operation request identifier, stores the second operation request identifier, and executes the second member The operation indicated in the resource operation request; or
  • the method further includes: receiving a second member resource operation request, where the second member resource operation request includes a second operation request identifier and a sub-group resource identifier; determining that the stored operation request identifier list includes the second operation request When identifying, returning an error response to the sender of the second member resource operation request, or determining that the stored operation request identifier list does not include the first And when the operation request identifier is used, the third member resource operation request is sent to the member device to which the member resource included in the sub-group resource identified by the sub-group resource identifier belongs.
  • Another aspect of the present invention provides another method for operating a group resource, including: receiving a second member resource operation request; determining that the second member resource operation request carries a second operation request identifier; determining the stored operation request Whether the second operation request identifier is included in the identifier list, and processing the second member resource operation request according to the judgment result.
  • the processing the second member resource operation request according to the determination result is: determining that the stored operation request identifier list includes the second When the request identifier is operated, the error response is returned to the sender of the second member resource operation request; or when the stored operation request identifier list does not include the second operation request identifier, the identifier identified by the sub-group resource identifier
  • the member device to which the member resource included in the sub-group resource belongs sends a third member resource operation request; or, when the second member resource operation request does not carry the sub-group resource identifier, the processing, according to the determination result, processing the second member resource
  • the operation request is specifically: when determining that the stored operation request identifier list includes the second operation request identifier, returning an error response to the sender of the second member resource operation request; or determining that the stored operation request identifier list does not include the And storing, by the second request identifier, the second operation request identifier, and Execute
  • the method further includes: receiving an operation request for the member resource; generating a first operation request identifier for the operation request of the member resource; and sending a first member resource operation request to the member device to which the member resource belongs;
  • the first member resource operation request includes a first operation request identifier, so that the member device to which the member resource belongs determines whether the first operation request is included in the operation request identifier stored by the member device according to the first operation request identifier. Identify, and process member resource operation requests based on the judgment result.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; before the generating the first operation request identifier for the operation request for the member resource, the method further includes: Determining, according to the group resource identifier, The operation request of the resource is generated by the first operation request identifier.
  • the determining, according to the group resource identifier, that the first operation request identifier is to be generated for the operation request for the member resource is: determining, according to the group resource identifier, the group identified by the group resource identifier The resource includes a sub-group resource as a member resource; determining that a first operation request identifier needs to be generated for an operation request for the member resource.
  • the determining, according to the group resource identifier, that the first operation request identifier is to be generated for the operation request for the member resource is: determining, according to the group resource identifier, the group identified by the group resource identifier The sub-group resource included in the resource is a remote group resource, or the member resource included in the sub-group resource identified by the sub-group resource identifier is determined to include the group resource according to the sub-group resource identifier. Identifying the identified group resource; determining that a first operation request identifier needs to be generated for an operation request for the member resource.
  • the method before the generating an operation request identifier for the operation request for the member resource, the method further includes: determining that the operation request for the member resource is an update request.
  • a further aspect of the present invention provides a group server, comprising: a receiving module, configured to receive an operation request for a member resource; and a generating module, configured to generate a first operation request identifier for the operation request of the member resource; a module, configured to send a member resource operation request to the member device to which the member resource belongs, where the first member resource operation request includes the first operation request identifier, so that the member device to which the member resource belongs is according to the An operation request identifier determines whether the first operation request identifier is included in the operation request identifier stored by the member device, and processes the member resource operation request according to the determination result.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; the group server further includes: a determining module, configured to determine, according to the group resource identifier A first operation request identifier is generated for the operation request for the member resource.
  • the determining module is specifically configured to: determine, according to the group resource identifier, that the group resource identified by the group resource identifier includes a sub-group resource as a member resource; Generating a first operation request identifier for the operation request for the member resource; or the determining module is specifically configured to: determine, according to the group resource identifier, the sub-group resource included in the group resource identified by the group resource identifier Determining, by the group resource identifier, the group resource included in the group resource identified by the group resource identifier, and the group resource identified by the group resource identifier; A first operation request identifier needs to be generated for an operation request for a member resource.
  • the group server further includes: an operation request determining module, configured to determine that the operation request for the member resource is an update request.
  • the receiving module is further configured to: receive a second member resource operation request, where the second member resource operation request includes a second operation request identifier; the group server further includes: a determining module, configured to determine The stored operation request identifier list includes the second operation request identifier, and returns an error response to the sender of the second member resource operation request; or, the method for determining that the stored operation request identifier list does not include the second operation request Identifying, storing the second operation request identifier, and performing an operation indicated in the second member resource operation request; or, the receiving module is further configured to: receive a second member resource operation request, the second member resource operation request The second operation request identifier and the sub-group resource identifier are included, and the group server further includes: the determining module is configured to determine that the stored operation request identifier list includes the second operation request identifier, and the second member resource operation request The sender returns an error response; or the operation used to determine the store Request identifier list does not include the second operation request identifier, a member
  • a further aspect of the present invention provides an apparatus for performing an operation on a group resource, including: a receiving module, configured to receive a second member resource operation request; and a determining module, configured to determine that the member resource operation request carries a second The operation request identifier is used to determine whether the operation request identifier is included in the stored operation request identifier list, and the second member resource operation request is processed according to the judgment result.
  • the determining module is specifically configured to: determine that the stored operation request identifier list includes the second operation request identifier, to the second The sender of the member resource operation request returns an error response; or the stored operation request identifier list does not include the second operation request identifier, and the member resources included in the identified sub-group resource belong to the sub-group resource identifier
  • the member device sends a third member resource operation request; or, when the second member resource operation request does not carry the sub-group resource identifier, the determining module is specifically configured to: determine that the stored operation request identifier list includes the The second operation request identifier returns an error response to the sender of the second member resource operation request; determining that the stored operation request identifier list does not include the second operation request identifier, storing the second operation request identifier, and executing the The operation indicated in the second member resource operation request.
  • the receiving module is further configured to: receive an operation request for the member resource; the device further includes: a generating module, configured to generate a first operation request identifier for the operation request of the member resource; And sending, by the member device to which the member resource belongs, a member resource operation request, where the first member resource operation request includes the first operation request identifier, so that the member device to which the member resource belongs is according to the first operation.
  • the request identifier determines whether the first operation request identifier is included in the operation request identifier stored by the member device, and processes the member resource operation request according to the determination result.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; the determining module is further configured to: determine, according to the group resource identifier, that the pair member is required The operation request of the resource generates a first operation request identifier.
  • the determining, by the determining, the determining, by the group resource identifier, the first operation request identifier that is to be generated for the operation request of the member resource is: determining, according to the group resource identifier, the group resource identifier
  • the identified group resource includes the sub-group resource as the member resource; determining that the first operation request identifier is generated for the operation request for the member resource; or determining the identifier of the group resource identifier according to the group resource identifier
  • the sub-group resource included in the group resource is a remote group resource, or the group resource identifier is determined according to the group resource identifier.
  • the member resource included in the identified group resource includes the group resource identified by the group resource identifier; and the first operation request identifier is determined to be required for the operation request to the member resource.
  • the determining module is further configured to: determine that the operation request for the member resource is an update request.
  • the operation request identifier is carried in the member resource operation request sent to the member device, so that the member device to which the member resource belongs determines the member device to store according to the operation request identifier. Whether the operation request identifier is included in the operation request identifier, and processing the member resource operation request according to the judgment result. Therefore, the subsequent member device can be prevented from repeatedly processing the member resource operation request.
  • FIG. 1 is a schematic diagram of group resources included in each other according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for operating a group resource according to an embodiment of the present invention
  • FIG. 3 is a flowchart of another method for operating a group resource according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for operating a member resource in a group resource of a nested group according to an embodiment of the present disclosure
  • Figure 6 is a flowchart of a method for operating a group resource according to an embodiment of the present invention
  • Figure 7a is a schematic structural diagram of a group server according to an embodiment of the present invention
  • FIG. 7b is a schematic structural diagram of another group server according to an embodiment of the present disclosure.
  • FIG. 8a is a schematic structural diagram of an apparatus for performing an operation on a group resource according to an embodiment of the present invention.
  • FIG. 8b is a schematic structural diagram of another apparatus for performing operations on a group resource according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a group resource according to an embodiment of the present invention.
  • the member resources included in the group resource group 1 are: a sub-group resource group 2, a first member resource M1, and a second member resource M2; and the member resources included in the second group resource group 2 are: a sub-group Resource Group 1, first member resource M1, third member resource M3.
  • the same group server may generate an operation request identifier after receiving an operation request for the member resource, and send a member resource operation request carrying the operation request identifier, and may receive another group.
  • the member resource operation request carried by the group server carrying the operation request identifier is referred to as a first member resource operation request, where the operation request identifier indicated by the first member resource operation request is the first An operation request identifier.
  • the member resource operation request received by the device of the same group server or the operation for the group resource is the second member resource operation request
  • the identifier carried by the second member resource operation request is the second operation request identifier. That is, the first member resource operation request and the second member resource operation request, and the first and second of the first operation request identifier and the second operation request identifier are merely names, first and second. It has no technical meaning in itself.
  • FIG. 2 is a flowchart of a method for operating a group resource according to an embodiment of the present invention, including the following steps: Step 201: Receive an operation request for a member resource.
  • the group server receives an operation request for a member resource in the group resource.
  • the operation request for the member resource includes the group resource identifier of the group resource to which the member resource belongs.
  • the first group server receives an access request for the member resource contained in the group resource whose group resource identifier is Grpl: GET littp://'g 1. example, org/groups/grp 1 /membersContent/data HTTP/1.1.
  • Gr l is a group resource identifier
  • the "membersContent" part indicates that the request is an operation for all member resources in the group resource corresponding to grp 1
  • "data" is an instance of the suffix to indicate the request. Specifically, you should access the "data" data for each member resource.
  • the operation request for the member resource may also be a request for updating, deleting, etc. of the member resource.
  • the group resource identifier may also be a name of the group resource, a URL indicating the group resource, and the like, which are not limited herein.
  • Step 202 Generate an operation request identifier for the operation request for the member resource.
  • the group server may determine, according to the group resource identifier, the sub-group resource included in the group resource identified by the group resource identifier.
  • Member resources As an embodiment of the present invention, the sub-group resource herein refers to a group resource that is included in a group resource as a member resource, and Group 2 included in Group 1 in FIG. 1 is a sub-group of Group 1. Resources, and since Group 1 is also included by Group 2, Group 1 is also a subgroup resource of Group 2. In the case of Fig. 1 of the embodiment of the present invention, the group resources Group 1 and Group 2 form a group nesting.
  • the group server may perform the judgment according to the member resource list included in the group resource.
  • Group 2 httpi/'/g 1. exampie.org/groups/grp2;
  • the list of group resources included in Group2 is specifically as follows:
  • Group 1 http://g 1 , example, com/groups/grp 1
  • the group server can determine that Group 1 includes the sub-group resource Grp2 as a member resource according to the group resource identifier Grp2 included in the member resource list included in Group 1.
  • the sub-group resource included in the group resource may be a group resource set in the group server, or may be a group resource set in another group server (generally called a remote group resource). ).
  • group resources can also be nested with each other, that is, Group 2 as shown in FIG. 1 is a sub-group resource of Group 1, and the same Group 1 is also a sub-group of Group 2. Resources.
  • Step 203 Send an operation request for the member resource to the member device to which the member resource belongs, where the member resource operation request includes the operation request identifier, so that the member device to which the member resource belongs is requested according to the operation.
  • the identifier determines whether the operation request identifier is included in the operation request identifier stored by the member device, and processes the member resource operation request according to the judgment result.
  • the group server sends a member resource operation request to the member device to which the member resource resource belongs according to the member resource list included in the group resource. If the member resource list includes a sub-group resource, as shown in FIG. 1 , for the operation request of the member resource of the group 1 , the group server sends the member resource operation request to the member resource included in the group 1 Member device, that is, the group server to which sub-group resource Group 2 belongs, the device to which M emberl belongs, and the device to which M ember2 belongs.
  • the group server in the M2M may be an M2M platform, an M2M gateway, or an M2M device, unless otherwise specified. That is, in the M2M network, as long as there is a service middleware, devices, gateways, and platforms that can store and maintain group resources can be used as group servers.
  • the resources in the embodiment of the present invention may be an M2M application, and an M2M. Platform, M2M terminal, M2M gateway, and every application or first data object running on M2M terminal and M2M gateway, group nesting is not limited to M2M service field, other includes mail group, address book contact Other applications for group nesting and member repetitive inclusions, such as people groups, are equally applicable to the present invention.
  • the operation request identifier is carried in the member resource operation request sent to the member device, so that the member device to which the member resource belongs determines the member device to store according to the operation request identifier. Whether the operation request identifier is included in the operation request identifier, and processing the member resource operation request according to the judgment result.
  • FIG. 3 is a flowchart of a method for processing a group server after receiving an operation request for a member resource according to an embodiment of the present invention, and the operation request identifier in the request is a mandatory parameter, and includes the following steps:
  • Step 301 The group server receives an operation request for the group resource.
  • the operation request for the group resource may be an operation request for the member resource.
  • the operation request of the member resource may be an access request for the member resource in the step 201, and may also be an update request for the member resource and other requests, which are not limited herein by the embodiment of the present invention.
  • the operation request includes the group resource identifier of the group resource to which the member resource belongs.
  • the operation request for the group resource received by the group server may be a member resource operation request carrying the REQ-ID, where the member resource operation request may also carry the member resource as a child of the sub-group resource.
  • Group resource ID may be a member resource operation request carrying the REQ-ID, where the member resource operation request may also carry the member resource as a child of the sub-group resource.
  • Step 302 The group server determines whether the operation request identifier REQ-ID is carried in the operation request for the group resource. If the operation request for the group resource does not carry the REQ-ID, the operation request for the group resource is a pair of groups. The operation request of the member resource of the group resource and the group server performs step 303. Otherwise, the operation request for the group resource is a member resource operation request, and step 303' is performed.
  • Step 303 The group server generates a REQ-ID for the operation request of the member resource, and records the generated REQ-ID.
  • the REQ-ID generated by the group server is a unique indication to the member resources.
  • the REQ-ID may be obtained by performing a hash encryption algorithm on the identifier of the group server (such as the address of the group server, etc.) plus the random number generated by the group server.
  • the REQ-ID may be carried in the message header or the message body in the operation request for the member resource, which is not limited herein.
  • the group server after generating the REQ-ID, the group server also needs to store the generated REQ-ID, and specifically, the REQ-ID may be stored as a group resource attribute in the group resource, such as requestTag, to indicate the first group server.
  • An operation request for a member resource corresponding to the REQ-ID has been processed.
  • Step 303 After the group server determines that the received operation request for the group resource carries the REQ-ID (that is, after determining that the operation request for the group resource is a member resource operation request), the REQ-ID and the group to be carried The REQ-ID that has been processed by the group server recorded in the group resource attribute requestTag is compared, and it is judged whether the REQ-ID with the same REQ-ID is stored in the list of the requestTag record. If the REQ-ID carried in the member resource operation request is already stored in the list of the requestTag record, step 304 is performed, otherwise step 304 is performed.
  • Step 304 If the member resource operation request carrying the REQ-ID does not carry the sub-group resource identifier, the group server performs the operation indicated in the member resource operation request carrying the REQ-ID, and the member resource operation request is The carried REQ-ID is stored in the group resource attribute requestTag; or if the member resource operation request carrying the REQ-ID further carries the sub-group resource identifier, the identified sub-group resource is identified to the sub-group resource
  • the member device to which the member resource belongs includes a third member resource operation request, and stores the REQ-ID carried in the member resource operation request into the group resource attribute requestTag.
  • the third member resource operation request is generated according to the second member resource operation request, and points to each member resource included in the sub-group resource identified by the sub-group identifier.
  • adding the attribute requestTag to the group resource to record the REQ-ID carried in the member resource operation request is only a method for recording the REQ-ID.
  • the group server may also maintain a list of the requested REQ-IDs that are processed by each group, or may be maintained by other feasible methods, which is not limited herein. For the sake of simplicity, the following steps and examples are no longer Repeated interpretation and emphasis are all illustrated by the requestTag method.
  • Step 304 The group server determines that the REQ-ID carried in the member resource operation request is stored in the list of the requestTag records, and indicates that the operation indicated in the member resource operation request corresponding to the carried REQ-ID has been processed.
  • the group server returns an error response (loop detected) to the sender (other group server) that sent the member resource operation request, indicating that the request message is a duplicate transmission.
  • Step 305 The group server receives a response message for the member resource operation request returned by each member device, and aggregates the response message returned by each member device.
  • the group server can ignore the error response returned by each member device; as an optional method, the group server can also aggregate these Error response.
  • Step 306 The group server returns the aggregated response message, and the process ends.
  • FIG. 4 is a flowchart of still another method for operating a group resource according to an embodiment of the present invention.
  • the operation request identifier in the request is not a mandatory parameter, and the group is different from the embodiment provided in FIG.
  • the server After determining that the operation request for receiving the group resource is an operation request for the member resource, the server also needs to determine whether to generate an operation request identifier REQ-ID for the operation request for the member resource according to various conditions.
  • the embodiment shown in FIG. 4 specifically includes the following steps:
  • Step 401 The group server receives an operation request for the group resource.
  • the operation request for the group resource may be an operation request for the member resource.
  • the operation request of the member resource may be an access request to the member resource in the step 201, and may also be an update request for the member resource of the pin and other requests, which are not limited herein by the embodiment of the present invention.
  • the group resource identifier of the group resource to which the member resource belongs in the operation request may be an access request to the member resource in the step 201, and may also be an update request for the member resource of the pin and other requests, which are not limited herein by the embodiment of the present invention.
  • the operation request for the group resource that is received by the group service is a member resource operation request carrying the REQ-ID, and the member resource operation request may also carry the group resource identifier of the group resource to which the member resource belongs.
  • Step 402 The group server determines whether the operation request for the group resource carries the operation.
  • the identifier REQ-ID is obtained. If the operation request for the group resource does not carry the REQ-ID, the operation request for the group resource is an operation request for the member resource and step 402-1 is performed; otherwise, the group resource is The operation request is a member resource operation request, and step 403' is performed.
  • Step 402-1 the group server determines whether the received operation request is an update request, if it is an update request, step 403 is performed, otherwise, step 402-2 is performed;
  • Step 402-2 The group server determines, according to the group resource identifier carried in the operation request for the member resource, whether the group resource identified by the group resource identifier includes a subgroup resource (subgroup) as a member resource, if the group The group resource identified by the resource identifier includes a subgroup resource (subgroup) as a member resource, and step 402-3 is performed; otherwise, step 404 is performed;
  • Step 402-3 The group server determines whether the subgroup resource (subgroup) included in the group resource is a remote subgroup resource. If yes, go to step 403, otherwise go to step 402-4;
  • the remote sub-group resource is a group resource created by another group server, and the group resource created by the other group server is used as the group resource identifier carried in the operation request for the member resource.
  • Member resource of the identified group resource For example, assume that the operation member resource request is received: GET http: // g 1.example.org/groups/grp3/membersContent/data HTTP / 1.1, then 1 J ⁇ shellfish: the group member resource operation request
  • the group server is gl
  • the group resource identifier carried in the operation request of the member resource is: grp3; the group resource group 3 not corresponding to the group resource identifier grp3 includes the following member resources:
  • Group 4 http ://g4. example. coni/groups/grp4
  • the group server to which the group 4 belongs is g4, not gl. Therefore, the subgroup resource Goup 4 included in Group 3 is Remote subgroup resource. That is, in step 402-3, the group server determines that the sub-group resource (Goup 4) included in the group resource Group 3 includes the remote sub-group resource (Goup 4).
  • the group server determines whether there is group nesting of the group resource (assumed to be a group resource) identified by the group resource identifier carried in the operation request of the member resource. That is, the group server determines whether the member resources included in the group resource include the sub-group resources, and whether the group resources included in the sub-group resources include the group resources. That is, whether the group resource identified by the group resource identifier carried in the operation request of the member resource and the sub-group resource included in the group resource are sub-group resources.
  • the group server acquires the member resource list included in the group resource, and the sub-group resource (ie, the sub-group resource) when the member resource included in the group resource includes the sub-group resource (assumed to be a sub-group resource)
  • the received operation request for the member resource is: GET http://g 1.example.org/groups/grp 1/membersContent/data HTTP/1.1.
  • Group 2 http: ⁇ g 1. examp le . org/ roup s/ gxp2;
  • Group 1 bttp://g 1. example.com/groups/grp 1
  • group resources Group 1 and Group 2 respectively have group nesting.
  • the group server gl determines whether the group nesting needs to be determined according to the member resources included in the member resource group 2 included in the group 1. In this case, the group server is required to obtain the member resource Group 2 included in the group 1.
  • the group server to which the aforementioned Group 2 belongs and the group server to which Group 1 belongs are both gl, ra ' can easily obtain Group 2 inclusions than gl Member resources.
  • the group server gl determines that the group server to which the member resource group 2 included in the group 1 belongs is g2, the group resource group 1 can be directly determined according to step 402-2.
  • the included sub-group resource Group 2 includes the remote sub-group resource Group2, and it is no longer necessary to obtain the member resources included in the Group2 from the group server g2 to which the Group2 belongs.
  • Step 403 is the same as step 303, and the embodiment of the present invention is not described in detail herein.
  • Step 403 is the same as step 303, and the embodiment of the present invention is not described in detail herein.
  • Step 404 is the same as step 304, and the embodiment of the present invention is not described in detail herein.
  • Step 404 which is the same as step 304, the embodiment of the present invention is not described in detail herein.
  • Step 405 is the same as step 305, and the embodiment of the present invention is not described in detail herein.
  • Step 406 is the same as step 306, and embodiments of the present invention are not described in detail herein.
  • Steps 402-1 through 402-4 are optional, the execution portion can be selected, and there is no clear sequence between step 402-1 and step 402-2 through step 402-4.
  • FIG. 5 is a flowchart of a method for an operation request for a member resource of a group resource of a nested group according to an embodiment of the present invention.
  • the group resource group 1 shown in FIG. 1 includes the following steps: Step 501: The application server sends an operation request to the group resource group 1 to the first group server gl where the group resource Group1 is located.
  • the application server may be an independent application server, or an application server of the M2M network, or an application module disposed in the gateway, or an application module disposed on the M2M device, where the application server may also be a group resource.
  • the module of the business capability layer of the host device may be an independent application server, or an application server of the M2M network, or an application module disposed in the gateway, or an application module disposed on the M2M device, where the application server may also be a group resource.
  • the operation request for the group resource Group 1 may be for the member resource.
  • the operation request for the group resource Group 1 carries the group resource identifier of the group 1.
  • the embodiment of the present invention assumes that the operation request for the group resource Group 1 is an operation request for the member resource.
  • the operation request for the member resource may be similar to the access request of the member resource or the update, deletion, and the like of the member resource, which is not limited herein.
  • the first group server gl After receiving the operation request for the group resource Group 1, the first group server gl determines that the operation request identifier for the group resource does not carry the operation request identifier REQ-ID, that is, the operation request for the group resource group 1 is An operation request for a member resource. And perform any of steps 402-1 to 402-4.
  • the member resources included in the group 1 include the sub-group resource Group 2, and the group 2 belongs to the second group server, that is, the group 2 belongs to the remote sub-group, and the group 2 includes the group 1 at the same time. That is, the first group server may determine in step 402-3 that Group 1 includes a remote subgroup. Therefore, when the first group server performs steps 402-2 to 402-4, step 403 may be performed after any of steps 402-1 to 402-4, that is, the operation request for the pair of member resources is generated.
  • REQ-ID records the generated REQ-ID.
  • the first group server may also not carry the operation request identifier REQ-ID in the operation request for determining the group resource, that is, the operation request for the group resource Group 1 is After the operation request of the member resource, step 402-1 is directly executed to determine whether the operation request for the member resource is an update request.
  • Step 502 The first group server performs the operation indicated in the member resource operation request, and the generated REQ-ID is carried in the member resource operation request and sent to the group 1
  • the member devices to which the member resources belong that is, the second group server g2, the member device 1 and the member device 2.
  • Step 503 After the member device 1 and the member device 2 receive the member resource operation request, perform The action indicated in the member resource operation request.
  • the member device 1 and the member device 2 determine that the member resource operation request carries the REQ-ID, and determines that the REQ-ID carried in the member resource operation request is stored in the list of the requestTag record, and indicates that the REQ-ID is carried.
  • the operation indicated in the corresponding member resource operation request has been executed, the operation indicated in the operation request is no longer executed, and an error response is returned to the first group server.
  • the member device 1 and the member device 2 determine that the REQ-ID carried in the member resource operation request is not stored in the list of the requestTag record, and the member resource operation request is stored in the list of the requestTag record.
  • the REQ-ID carried in, and performs the operations indicated in the member resource operation request it is assumed that the member device 1 and the member device 2 determine that the REQ-ID carried in the member resource operation request is not stored in the list of the requestTag record, and the member resource operation request is stored in the list of the requestTag record.
  • the REQ-ID carried in and performs the operations indicated in the member resource operation request.
  • Steps 504 and 504 the member device 1 and the member device 2 respectively return a response message to the first group server.
  • Step 505 The second group server determines that the REQ-ID carried in the member resource operation request is not stored in the list of the requestTag record, and stores the REQ-ID carried in the member resource operation request in the list of the requestTag record.
  • the second group server determines that the REQ-ID carried in the member resource operation request has been stored in the list of the requestTag record, it indicates that the operation indicated in the member resource operation request corresponding to the carried REQ-ID has been executed. The operation indicated in the operation request is no longer executed, and an error response is returned to the first group server.
  • Steps 506 and 506 the second group server sends a member resource request message to the member resource Group 1, the member device 1 and the member device 3 respectively included in the group 2.
  • Step 507 is similar to step 503.
  • the member device 3 determines that the REQ-ID carried in the member resource operation request is not stored in the list of the requestTag record, and stores the REQ-ID carried in the member resource operation request in the list of the requestTag record, and executes the member resource operation request. Indicated action.
  • Step 507, and step 507" the first group server and the member device 1 determine the member resource operation
  • the REQ-ID carried in the request is already stored in the list of the requestTag record, indicating that the operation indicated in the member resource operation request corresponding to the carried REQ-ID has been executed, and the operation indicated in the operation request is not executed.
  • Step 508 The member device 3 returns a response message to the second group server.
  • Step 508, and step 508" the first group server and the member device 1 respectively return an error response to the second group server.
  • Step 509 The second group server aggregates the received response messages from the first group server, the member device 1, and the member device 3. However, since the first group server and the member device 1 both return an error response, the response message returned to the member device 3 to the second group server does not need to be aggregated.
  • Step 510 The second group server returns a first aggregated group response message to the first group server.
  • Step 511 The first group server aggregates the received response message from the member device 1 and the member device 2, and the first aggregated group response message from the second group server. Step 512, the first group The server returns a second aggregated group member response message to the application server.
  • group 1 and group 2 shown in Figure 5 are assumed to be located in different group servers, and group 2 is the remote group remote group of group 1.
  • group 1 and group 2 may be in the same group server, ie group2 is the local subgroup of groupl local subgroup diff
  • FIG. 6 is a flowchart of a method for operating a group resource according to an embodiment of the present invention, including the following steps:
  • Step 601 Receive a second member resource operation request.
  • the member device receives the member resource operation request sent by the group server described by the member device, or the group server receives the second member resource operation request sent by the other group server gl, as shown in step 502. Therefore, the embodiment of the present invention will receive the member of the second request.
  • a device or group server is collectively referred to as a device that performs operations on a group resource.
  • Step 602 Determine that the second member resource operation request carries the second operation request identifier.
  • the device that performs the operation on the group resource determines that the second member resource operation request sent by the group server includes the second operation request. logo.
  • the device that operates the group resource may also receive the member resource operation request that does not include the operation request identifier, and the operation of the embodiment of the present invention is performed after receiving the member resource operation request that does not include the operation request identifier. Do not make a statement.
  • Step 603 Determine whether the stored operation request identifier list includes the carried second operation request identifier, and process the second member resource operation request according to the judgment result.
  • the processing of the second member resource operation request according to the determination result is: when the second member resource operation request further carries the sub-group resource identifier, the processing the second member resource operation request according to the determination result is specifically: Determining that the stored operation request identifier list includes the second operation request identifier, and returning an error response to the sender of the second member resource operation request; or determining that the stored operation request identifier list does not include the second operation request identifier, Sending, to the member device to which the member resource included in the group resource identified by the sub-group resource identifier belongs, a third member resource operation request; or
  • the processing the second member resource operation request according to the determination result is: determining that the stored operation request identifier list includes the second operation request identifier, Returning an error response to the sender of the second member resource operation request; or determining that the stored operation request identifier list does not include the second request identifier, storing the second operation request identifier, and performing a member resource operation request The operation indicated in .
  • the device that performs the operation on the group resource may determine that the second member resource operation request includes the second operation request identifier, and process the second member according to the determined result.
  • the resource operates on the request, thereby avoiding repeated processing of the processed operation request.
  • the device may be a group server, and thus the steps performed by the group server in the embodiment corresponding to FIG. 2 to FIG. 4 may also be performed, and the embodiments of the present invention are not described in detail herein.
  • FIG. 7 is a schematic structural diagram of a group server according to an embodiment of the present invention, including: a receiving module 701, configured to receive an operation request for a member resource; and a generating module 702, configured to generate a first operation request for the member resource An operation request identifier; the sending module 703, configured to send a member resource operation request to the member device to which the member resource belongs, where the first member resource operation request includes the first operation request identifier; The member device determines, according to the first operation request identifier, whether the operation request identifier stored in the member device includes the first operation request identifier, and processes the member resource operation request according to the determination result.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; the group server further includes: a determining module 704, configured to determine, according to the group resource identifier, that the The operation request for the member resource generates a first operation request identifier.
  • the determining module 704 is specifically configured to: determine, according to the group resource identifier, that the group resource identified by the group resource identifier includes a sub-group resource as a member resource; determining that the operation request for the member resource is generated a first operation request identifier; or, the determining module 704 is specifically configured to: determine, according to the group resource identifier, a sub-group resource included in the group resource identified by the group resource identifier as a remote group resource, or according to the The group resource identifier determines that the member resource included in the group resource identified by the group resource identifier includes a group resource corresponding to the group resource identifier; and determines an operation request for the member resource.
  • a first operation request identifier is generated.
  • the group server further includes an operation request determining module 705, configured to determine that the operation request for the member resource is an update request.
  • the receiving module 701 is further configured to receive a second member resource operation request, where the second member resource operation request includes a second operation request identifier
  • the group server further includes: a determining module 706, configured to determine the stored operation request The second operation request identifier is included in the identifier list An error response is returned to the sender of the second member resource operation request; or the second operation request identifier is not included in the operation request identifier list for storing, the second operation request identifier is stored, and the second operation request identifier is stored The operation indicated in the two-member resource operation request; or, the receiving module 701 is further configured to receive the second member resource operation request, where the second member resource operation request includes the second operation request identifier and the sub-group resource identifier; 706.
  • the operation request identifier list used to determine the storage includes the second operation request identifier, and returns an error response to the sender of the second member resource operation request; or is used to determine that the stored operation request identifier list does not include the
  • the second operation request identifier sends a third member resource operation request to the member device to which the member resource included in the group resource identified by the sub-group resource identifier belongs.
  • FIG. 7b is a schematic structural diagram of another group server according to an embodiment of the present invention, including a memory 700, and a processor 600.
  • the memory 600 is used to store the modules described in FIG. 7a, and the processor 600 is connected to the memory 700.
  • the modules running the memory 600 perform the respective functions of the modules in the memory 600.
  • the functions of the modules in the memory 600 in Fig. 7b are the same as those of the modules in Fig. 7a, and the embodiments of the present invention will not be described in detail herein.
  • FIG. 8 is a schematic structural diagram of an apparatus for performing operations on a group resource according to an embodiment of the present invention, including: a receiving module 801, configured to receive a second member resource operation request; and a determining module 802, configured to determine the member resource operation request
  • the second operation request identifier is carried in the determining unit 803, and is configured to determine whether the operation request identifier is included in the stored operation request identifier list, and perform an operation indicated in the member second resource operation request according to the determination result.
  • the determining module 803 is specifically configured to determine that the stored operation request identifier list includes the second operation request identifier, and the second member resource is The sender of the operation request returns an error response; or determines that the stored operation request identifier list does not include the second operation request identifier, and identifies the member device to which the member resource included in the group resource identified by the sub-group resource belongs Sending a third member resource operation request; or, when the second member resource operation request does not carry the sub-group resource identifier, the determining module is specifically configured to: determine that the stored operation request identifier list includes the second operation The request identifier returns an error response to the sender of the second member resource operation request; determining that the stored operation request identifier list does not include the second operation request identifier, storing the second operation request identifier, and executing the second The action indicated in the member resource operation request.
  • the receiving module 801 is further configured to receive an operation request for the member resource.
  • the generating module 804 is configured to generate a first operation request identifier for the operation request of the member resource
  • the sending module 804 is configured to send a member resource operation request to the member device to which the member resource belongs, where the first member resource operation request is The first operation request identifier is included in the device, and the member device to which the member resource belongs is determined according to the first operation request identifier, and whether the operation request identifier stored in the member device includes the first operation request identifier, and according to the determination result Process member resource operation requests.
  • the operation request for the member resource carries the group resource identifier of the group resource to which the member resource belongs; the determining module 802 is further configured to: determine, according to the group resource identifier, the required member resource The operation request generates a first operation request identifier.
  • the determining module 802 according to the group resource identifier, determining that the first operation request identifier is to be generated for the operation request of the member resource, is: determining the group resource identifier according to the group resource identifier.
  • the identified group resource includes the sub-group resource as the member resource; determining that the first operation request identifier is generated for the operation request for the member resource; or determining the identifier of the group resource identifier according to the group resource identifier
  • the sub-group resource included in the group resource is a remote group resource, or the member resource included in the group resource identified by the group resource identifier is determined to be included in the group resource according to the group resource identifier.
  • the group resource identifies the group resource identified; and determines that the first operation request identifier needs to be generated for the operation request for the member resource.
  • the determining module 802 is further configured to: determine that the operation request for the member resource is an update request.
  • FIG. 8b is a schematic structural diagram of another apparatus for performing operations on a group resource according to an embodiment of the present invention, including a memory 800, and a processor 900.
  • the memory 600 is used to store the modules described in FIG. 8a, and the processor 900 is connected to the memory 800, and each module in the memory 800 is executed.
  • the functions of the modules in the memory 800 in FIG. 8b are the same as those of the modules in FIG. 8a, and the embodiments of the present invention are not described in detail herein.
  • the operation request identifier is carried in the member resource operation request sent to the member device, so that the member device to which the member resource belongs determines the member device to store according to the operation request identifier. Whether the operation request identifier is included in the operation request identifier, and processing the member resource operation request according to the judgment result. Assuming that the operation request identifier stored in the member device contains the operation request identifier, an error response is returned, and the member resource operation request is no longer processed. Therefore, the subsequent member device can be prevented from repeatedly processing the member resource operation request.
  • the M2M platform may be a computer, a device having a processor.
  • the M2M gateway and the M2M terminal are not strictly distinguished on the device.
  • the gateway device can also be used as a terminal, and also for various terminal devices, such as mobile phones, computers, PDAs, notebook computers, remote controllers, household appliances, various Instrumentation, sensors, etc. can be used as gateways or terminals for M2M networks.
  • each module included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding function can be implemented; in addition, the specific names of the functional modules are only for convenience. They are distinguished from each other and are not intended to limit the scope of protection of the present invention.
  • the above-described method of implementing operation of a group resource and functions of each function module of a group server or a device performing an operation on a group resource may each be operated by a group server or a processor executing a device operating for a group resource
  • the completion of the module, as well as the above-described method of implementing the group server and the functions of the functional modules of the group server, can be performed by the processor of the group server.
  • the group server in FIG. 7a and FIG. 7b may perform any of the steps performed by the group server in the foregoing method flow embodiment, and the apparatus for performing operations on the group resource in FIG. 8a and FIG. 8b may perform the foregoing method flow.
  • Any step performed by the group server in the embodiment may also be performed Any of the steps performed by the member devices in the foregoing method flow embodiments are not described herein again.
  • the above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Educational Administration (AREA)
  • Tourism & Hospitality (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明提供了一种针对群组资源的操作方法、群组服务器和执行针对群组资源的操作的装置，通过在发送给成员设备的成员资源操作请求中携带操作请求标识，以便成员资源所属的成员设备根据所述操作请求标识判断成员设备存储的操作请求标识中是否包含所述操作请求标识，并根据判断结果处理成员资源操作请求。从而能够避对成员资源的操作请求进行重复处理或循环处理。

Description

针对群组资源的操作方法、 群组服务器
本申请要求于 2012年 02月 29 日提交中国专利局、 申请号为
2012100501 31. 1 , 发明名称为 "针对群组资源的操作方法、 群组服务器"， 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域 本发明涉及机器通信 ( Machine-to-Machine Communications, M2M )技 术领域， 尤其涉及针对群组资源方法、 群组服务器。
背景技术 机器通信 ( Machine-to-Machine Communications, M2M )是一种以机器 智能交互为核心的、 网络化的应用与服务。 M2M技术通过在机器内部嵌入 无线或有线通信模块以及应用处理逻辑， 实现无需人工干预的数据通信， 以满足用户对监控、 指挥调度、 数据采集和测量等方面的信息化需求。 目 前的 M2M架构中， 描述了一种面向群组资源的通信方法。 该方法中， M2M 应用、 M2M平台、 M2M终端、 M2M网关以及 M2M终端和 M2M网关上所运 行的每一个应用或第一个数据对象均被看做一种表述性状态转移 (REpresentational State Transfer )风格的 RESTful资源， 并由通用资源标识符 ( Universal Resource Identifier, URI )来标识应用或数据对象， 并通过构建 各种群组资源对上述多个资源进行群组操作。
在一些常见的 M2M业务中， 用户可能需要通过创建群组的方式同时对 群组资源包含的 M2M终端或网关等成员资源进行相同的操作。可以理解的， 上述被创建的群组资源本身也是作为一种资源， 群组资源包括群组资源本 身的资源和群组资源包含的成员资源。 其中， 群组资源本身的资源可以是 群组资源的标识， 所属的群组服务器， 状态（如是否为有状态的群组资源） 等， 群组资源包含的成员资源既可以是成员资源的列表， 还可以是成员资 源的相关信息在群组资源的映射。 M2M群组资源中的成员资源可能归属于 本地的群组服务器， 也可能归属于远程的群组服务器。 然而， 在某些情况 下， 两个群组资源有可能互为成员资源。 比如在智能安防系统中， 片区派 出所可以将相邻小区的监控群组设为包含彼此的监控群组， 当出现报警情 况时， 可以根据实际情况相互支援； 又比如， 未来的智能家居系统中， 用 户可以对家里的电器 （如电灯、 门窗、 抄表等）进行群组管理， 如子女考 虑到父母年纪大了， 可以嵌套包含父母家中电器群组帮助其管理， 下雨了 帮忙关窗， 晚上确认门窗关闭， 关闭所有电器等， 而父母考虑到子女工作 忙碌， 经常出差在外等情况， 也可以嵌套包含子女家中电器群组， 帮助子 女照顾家庭。 在另一种情况下， 还有可能同一成员资源同时被两个群组资 源包含。
针对上述的情况， 群组资源相互包含时可能会导致发送给群组资源的 操作请求在相互包含的群组资源中循环发送的错误， 而针对同一成员资源 同时被至少两个群组资源包含时有可能导致针对该至少两个群组资源的操 作请求对该成员资源重复执行的错误。
发明内容
本发明的实施例提供的针对群组资源的操作方法、 群组服务器和执行 针对群组资源的操作的装置， 能够避对成员资源的操作请求进行重复处理 或循环处理。
本发明一方面提供了一种针对群组资源的操作方法， 包括： 接收对成 员资源的操作请求； 针对所述对成员资源的操作请求生成第一操作请求标 识； 向所述成员资源所属的成员设备发送第一成员资源操作请求， 所述第 一成员资源操作请求中包含所述第一操作请求标识； 以便所述成员资源所 属的成员设备根据所述第一操作请求标识判断成员设备存储的操作请求标 识中是否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作 请求。 可选的， 所述对成员资源的操作请求中携带所述成员资源所属群组资 源的群组资源标识； 所述针对对成员资源的操作请求生成第一操作请求标 识之前， 该方法进一步包括： 根据所述群组资源标识确定需针对所述对成 员资源的操作请求生成第一操作请求标识。
可选的， 所述根据所述群组资源标识确定需针对对成员资源的操作请 求生成第一操作请求标识包括： 根据所述群组资源标识确定所述群组资源 标识所标识的群组资源中包含子群组资源作为成员资源； 确定需针对对成 员资源的操作请求生成第一操作请求标识。
可选的， 所述根据所述群组资源标识确定需针对对成员资源的操作请 求生成第一操作请求标识具体为： 根据所述群组资源标识确定所述群组资 源标识所标识的群组资源中包含的子群组资源为远程群组资源， 或根据所 述群组资源标识确定所述群组资源标识所标识的群组资源所包含的成员资 源中包含所述群组资源标识所标识的群组资源； 确定需针对对成员资源的 操作请求生成第一操作请求标识。
可选的， 所述针对对成员资源的操作请求生成第一操作请求标识之前， 该方法进一步包括： 确定对成员资源的操作请求为更新请求。
可选的， 该方法进一步包括： 接收第二成员资源操作请求， 所述第二 成员资源操作请求中包含第二操作请求标识； 判断存储的操作请求标识列 表中包含所述第二操作请求标识， 指示的操作向第二成员资源操作请求的 发送方返回错误响应， 或判断存储的操作请求标识列表中不包含所述第二 操作请求标识， 存储所述第二操作请求标识， 并执行第二成员资源操作请 求中指示的操作； 或
该方法进一步包括： 接收第二成员资源操作请求， 所述第二成员资源 操作请求中包含第二操作请求标识以及子群组资源标识； 判断存储的操作 请求标识列表中包含所述第二操作请求标识时， 向第二成员资源操作请求 的发送方返回错误响应， 或判断存储的操作请求标识列表中不包含所述第 二操作请求标识时， 向所述子群组资源标识所标识的子群组资源包含的成 员资源所属的成员设备发送第三成员资源操作请求。
本发明另一方面还提供另一种针对群组资源的操作方法， 包括： 接收第二成员资源操作请求； 确定所述第二成员资源操作请求中携带 第二操作请求标识； 判断存储的操作请求标识列表中是否包含所述第二操 作请求标识， 并根据判断结果处理第二成员资源操作请求。
可选的， 当所述第二成员资源操作请求还携带子群组资源标识时， 所 述根据判断结果处理第二成员资源操作请求具体为： 判断存储的操作请求 标识列表中包含所述第二操作请求标识时， 向第二成员资源操作请求的发 送方返回错误响应； 或判断存储的操作请求标识列表中不包含所述第二操 作请求标识时， 向所述子群组资源标识所标识的子群组资源包含的成员资 源所属的成员设备发送第三成员资源操作请求； 或， 当所述第二成员资源 操作请求不携带子群组资源标识时， 所述根据判断结果处理第二成员资源 操作请求具体为： 判断存储的操作请求标识列表中包含所述第二操作请求 标识时， 向第二成员资源操作请求的发送方返回错误响应； 或， 判断存储 的操作请求标识列表中不包含携所述第二作请求标识时， 存储所述第二操 作请求标识， 并执行第二成员资源操作请求中指示的操作。
可选的， 该方法进一步包括： 接收对成员资源的操作请求； 针对所述 对成员资源的操作请求生成第一操作请求标识;向所述成员资源所属的成员 设备发送第一成员资源操作请求;所述第一成员资源操作请求中包含第一操 作请求标识， 以便所述成员资源所属的成员设备根据所述第一操作请求标 识判断成员设备存储的操作请求标识中是否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作请求。
可选的， 所述对成员资源的操作请求中携带所述成员资源所属群组资 源的群组资源标识； 所述针对对成员资源的操作请求生成第一操作请求标 识之前， 该方法进一步包括： 根据所述群组资源标识确定需针对所述对成 员资源的操作请求生成第一操作请求标识。
可选的， 所述根据所述群组资源标识确定需针对对成员资源的操作请 求生成第一操作请求标识具体为： 根据所述群组资源标识确定所述群组资 源标识所标识的群组资源中包含子群组资源作为成员资源； 确定需针对对 成员资源的操作请求生成第一操作请求标识。
可选的， 所述根据所述群组资源标识确定需针对对成员资源的操作请 求生成第一操作请求标识具体为： 根据所述群组资源标识确定所述群组资 源标识所标识的群组资源中包含的子群组资源为远程群组资源， 或根据所 述子群组资源标识确定所述子群组资源标识所标识的子群组资源所包含的 成员资源中包含所述群组资源标识所标识的群组资源； 确定需针对对成员 资源的操作请求生成第一操作请求标识。
可选的， 所述针对对成员资源的操作请求生成操作请求标识之前， 该 方法进一步包括： 确定对成员资源的操作请求为更新请求。
本发明又一方面还提供一种群组服务器， 包括： 接收模块， 用于接收 对成员资源的操作请求； 生成模块， 用于针对所述对成员资源的操作请求 生成第一操作请求标识； 发送模块， 用于向所述成员资源所属的成员设备 发送成员资源操作请求， 所述第一成员资源操作请求中包含所述第一操作 请求标识； 以便所述成员资源所属的成员设备根据所述第一操作请求标识 判断成员设备存储的操作请求标识中是否包含所述第一操作请求标识， 并 根据判断结果处理成员资源操作请求。
可选的， 所述对成员资源的操作请求中携带所述成员资源所属群组资 源的群组资源标识； 所述群组服务器进一步包括： 确定模块， 用于根据所 述群组资源标识确定需针对所述对成员资源的操作请求生成第一操作请求 标识。
可选的， 所述确定模块具体用于： 根据所述群组资源标识确定所述群 组资源标识所标识的群组资源中包含子群组资源作为成员资源； 确定需针 对对成员资源的操作请求生成第一操作请求标识； 或所述确定模块具体用 于： 根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含的子群组资源为远程群组资源， 或根据所述群组资源标识确定所述群组 资源标识所标识的群组资源所包含的成员资源中包含与对所述群组资源标 识所标识的群组资源； 确定需针对对成员资源的操作请求生成第一操作请 求标识。
可选的， 上述群组服务器进一步包括： 操作请求确定模块， 用于确定 对成员资源的操作请求为更新请求。
可选的， 所述接收模块进一步用于： 接收第二成员资源操作请求， 所 述第二成员资源操作请求中包含第二操作请求标识； 所述群组服务器进一 步包括： 判断模块， 用于判断存储的操作请求标识列表中包含所述第二操 作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 或， 用于 判断存储的操作请求标识列表中不包含所述第二操作请求标识， 存储所述 第二操作请求标识， 并执行第二成员资源操作请求中指示的操作； 或， 所 述接收模块进一步用于： 接收第二成员资源操作请求， 所述第二成员资源 操作请求中包含第二操作请求标识及子群组资源标识， 所述群组服务器进 一步包括： 判断模块用于判断存储的操作请求标识列表中包含所述第二操 作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 或用于判 断存储的操作请求标识列表中不包含所述第二操作请求标识， 向所述子群 组资源标识所标识的子群组资源包含的成员资源所属的成员设备发送第三 成员资源操作请求。
本发明再一方面还提供一种执行针对群组资源的操作的装置， 包括： 接收模块， 用于接收第二成员资源操作请求； 确定模块， 用于确定所述成 员资源操作请求中携带第二操作请求标识； 判断模块， 用于判断存储的操 作请求标识列表中是否包含所述操作请求标识， 并根据判断结果处理第二 成员资源操作请求。 可选的， 当所述第二成员资源操作请求还携带子群组资源标识时， 所 述判断模块具体用于： 判断存储的操作请求标识列表中包含所述第二操作 请求标识， 向第二成员资源操作请求的发送方返回错误响应； 或判断存储 的操作请求标识列表中不包含所述第二操作请求标识， 向所述子群组资源 标识所标识的子群组资源包含的成员资源所属的成员设备发送第三成员资 源操作请求； 或， 当所述第二成员资源操作请求不携带子群组资源标识时， 所述判断模块具体用于： 判断存储的操作请求标识列表中包含所述第二操 作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 判断存储 的操作请求标识列表中不包含所述第二操作请求标识， 存储所述第二操作 请求标识， 并执行所述第二成员资源操作请求中指示的操作。
可选的， 所述接收模块进一步用于： 接收对成员资源的操作请求； 所 述装置进一步包括： 生成模块， 用于针对所述对成员资源的操作请求生成 第一操作请求标识； 发送模块， 用于向所述成员资源所属的成员设备发送 成员资源操作请求， 所述第一成员资源操作请求中包含所述第一操作请求 标识； 以便所述成员资源所属的成员设备根据所述第一操作请求标识判断 成员设备存储的操作请求标识中是否包含所述第一操作请求标识， 并根据 判断结果处理成员资源操作请求。
可选的， 所述对成员资源的操作请求中携带所述成员资源所属群组资 源的群组资源标识； 所述确定模块进一步用于： 根据所述群组资源标识确 定需针对所述对成员资源的操作请求生成第一操作请求标识。
可选的， 所述确定模块根据所述群组资源标识确定需针对所述对成员 资源的操作请求生成第一操作请求标识具体为： 根据所述群组资源标识确 定所述群组资源标识所标识的群组资源中包含子群组资源作为成员资源； 确定需针对对成员资源的操作请求生成第一操作请求标识； 或， 根据所述 群组资源标识确定所述群组资源标识所标识的群组资源中包含的子群组资 源为远程群组资源， 或根据所述群组资源标识确定所述群组资源标识所标 识的群组资源所包含的成员资源中包含对与所述群组资源标识所标识的群 组资源； 确定需针对对成员资源的操作请求生成第一操作请求标识。
可选的， 所述确定模块进一步用于： 确定对成员资源的操作请求为更 新请求。
由上述本发明的实施例提供的技术方案可以看出， 通过在发送给成员 设备的成员资源操作请求中携带操作请求标识， 以便成员资源所属的成员 设备根据所述操作请求标识判断成员设备存储的操作请求标识中是否包含 所述操作请求标识， 并根据判断结果处理成员资源操作请求。 从而， 可以 避免后续成员设备重复处理成员资源操作请求。
附图说明 为了更清楚地说明本发明实施例的技术方案， 下面将对实施例描述中 所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是 本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳 动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的群组资源互相包含的示意图；
图 2为本发明实施例提供的针对群组资源的操作方法的流程图； 图 3为本发明实施例提供的另一针对群组资源的操作方法的流程图； 图 4为本发明实施例提供的又一针对群组资源的操作方法的流程图 图 5为本发明实施例提供的存在嵌套群组的群组资源中的成员资源的 操作请求的方法流程图；
图 6为本发明实施例提供的针对群组资源的操作方法的流程图； 图 7a为本发明实施例提供的群组服务器的结构示意图；
图 7b为本发明实施例提供的另一群组服务器结构示意图；
图 8a为本发明实施例提供的执行针对群组资源的操作的装置结构示意 图；
图 8b为本发明实施例提供的另一执行针对群组资源的操作的装置结构 示意图。
具体实施方式 下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进 行清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没 有作出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的 范围。
图 1为本发明实施例提供的群组资源的示意图。具体的，群组资源 group 1包含的成员资源为： 子群组资源 Group 2,第一成员资源 Ml , 第二成员资源 M2; 而第二群组资源 Group 2包含的成员资源为： 子群组资源 Group 1,第一 成员资源 Ml , 第三成员资源 M3。
值得说明的是， 本发明实施例中， 由于同一群组服务器即可以在接收 对成员资源的操作请求后生成操作请求标识， 并发送携带操作请求标识的 成员资源操作请求， 又可以接收别的群组服务器发送过来的携带操作请求 标识的成员资源操作请求。 因此， 为了名称的区分， 将群组服务器或执行 针对群组资源的操作的装置发送的成员资源操作请求称为第一成员资源操 作请求， 其中第一成员资源操作请求指示的操作请求标识为第一操作请求 标识。 由同一群组服务器或执行针对群组资源的操作的装置接收到的成员 资源操作请求为第二成员资源操作请求， 而第二成员资源操作请求携带的 标识为第二操作请求标识。 也就是说， 第一成员资源操作请求和第二成员 资源操作请求,以及第一操作请求标识和第二操作请求标识中的第一和第二 仅仅是做名称上的区分， 第一和第二本身没有技术上的意义。
图 2为本发明实施例提供的针对群组资源的操作方法的流程图， 包括如 下步骤： 步骤 201、 接收对成员资源的操作请求；
具体的， 群组服务器接收针对群组资源中的成员资源的操作请求。 其 中， 所述对成员资源的操作请求中包含成员资源所属群组资源的群组资源 标识。
例如： 第一群组服务器接收到针对群组资源标识为 Grpl的群组资源包 含 的 的 成 员 资 源 的 访 问 请 求 ： GET littp://'g 1. example, org/groups/grp 1 /membersContent/data HTTP/ 1.1。其中, Gr l 为群组资源标识， "membersContent"部分表明此请求为针对 grp 1对应的群 组资源中所有成员资源的操作， "data"即为所述后缀的一个实例， 用以表 明该请求具体应该访问每个成员资源的 "data"数据。 当然， 对成员资源的 操作请求还可以是对成员资源的更新， 删除等请求。 在其它的可选方式中， 群组资源标识还可以是指群组资源的名称， 指示群组资源的 URL等， 本发 明实施例在此不做限定。
步骤 202、 针对所述对成员资源的操作请求生成操作请求标识； 具体的， 群组服务器可以根据群组资源标识， 确定所述群组资源标识 所标识的群组资源中包含子群组资源作为成员资源。 作为本发明的实施例， 这里的子群组资源是指作为成员资源被包含于一个群组资源中的群组资 源， 如图 1中的被 Group 1包含的 Group 2为 Group 1的子群组资源， 而由于 Group 1同样也被 Group 2包含， 因此 Group 1也是 Group 2的子群组资源。 在 本发明实施例图 1中的情况， 群组资源 Group 1和 Group 2形成群组嵌套。
而群组服务器在确定所述群组资源标识所标识的群组资源中包含子群 组资源作为成员资源时， 可以根据群组资源包含的成员资源列表进行判断。
如图 1中 Group 1包含的成员资源列表具体为：
m 1 = coap://dl . example.com/xxx/templ
m 2 = coap：〃 gl .example.com/xxx/templ
Group 2= httpi/'/g 1. exampie.org/groups/grp2； Group2包含的群组资源列表具体为：
m 1 = coap://dl . example.com/xxx/templ
m 3 = coap://d2. example.org/xxx/temp 1
Group 1 = http://g 1 , example, com/groups/grp 1
群组服务器则可以根据 Group 1 包含的成员资源列表中包含的群组资 源标识 Grp2 , 确定 Group 1包含子群组资源 Grp2作为成员资源。
其中， 被群组资源包含的子群组资源可以是设立于该群组服务器中的 群组资源， 也可以是设立于别的群组服务器中的群组资源 （通常称之为远 程群组资源） 。 而由上述图 1还可以看出， 群组资源之间还可以相互嵌套， 即图 1所述的 Group 2作为 Group 1的子群组资源， 同样的 Group 1也作为 Group 2的子群组资源。
步骤 203、 向所述成员资源所属的成员设备发送针对所述成员资源的操 作请求， 所述成员资源操作请求中包含所述操作请求标识； 以便所述成员 资源所属的成员设备根据所述操作请求标识判断成员设备存储的操作请求 标识中是否包含所述操作请求标识， 并根据判断结果处理成员资源操作请 求。
具体的， 群组服务器根据群组资源包含的成员资源列表， 向成员资源 资源所属的成员设备发送成员资源操作请求。 如果群组资源包含的成员资 源列表中包含子群组资源，如图 1所述，针对 Group 1的成员资源的操作请求， 则群组服务器将成员资源操作请求发送给 Group 1包含的成员资源所属的成 员设备， 即子群组资源 Group 2所属的群组服务器， M emberl所属的设备和 M ember2所属的设备。
在本发明所有的实施例中， 如不作特别说明， M2M 中的群组服务器可 以为 M2M平台 , M2M网关 , 也可以为 M2M设备。 即在 M2M网络中， 只 要具有业务中间件， 可以存储和维护群组资源的设备、 网关、 和平台都可 以作为群组服务器。此外，本发明实施例中的资源可以是 M2M应用、 M2M 平台、 M2M终端、 M2M网关以及 M2M终端和 M2M网关上所运行的每一 个应用或第一个数据对象等，群组嵌套也并不仅限于 M2M业务领域中， 其 他包括邮件群组、 通讯簿联系人群组等在内的其他关于群组嵌套以及成员 重复包含的应用同样适用本发明方案。
由上述本发明的实施例提供的技术方案可以看出， 通过在发送给成员 设备的成员资源操作请求中携带操作请求标识， 以便成员资源所属的成员 设备根据所述操作请求标识判断成员设备存储的操作请求标识中是否包含 所述操作请求标识， 并根据判断结果处理成员资源操作请求。 图 3为本发明 实施例提供的群组服务器收到对成员资源的操作请求后进行处理的方法流 程图， 且请求中的操作请求标识为必选参数， 包括如下步骤：
步骤 301、 群组服务器接收到对群组资源的操作请求；
具体的， 对群组资源的操作请求可以为对成员资源的操作请求。 该对 成员资源的操作请求可以为步骤 201中的对成员资源的访问请求， 还可以是 针对成员资源的更新请求以及其它的请求， 本发明实施例在此不做限定， 所述对成员资源的操作请求中包含成员资源所属群组资源的群组资源标 识。
可替代地， 群组服务器接收到的对群组资源的操作请求可以为携带有 REQ-ID的成员资源操作请求， 其中， 该成员资源操作请求中也可以携带成 员资源作为子群组资源的子群组资源标识。
步骤 302、 群组服务器确定对群组资源的操作请求中是否携带操作请求 标识 REQ-ID, 若对群组资源的操作请求中没有携带 REQ-ID, 则对群组资源 的操作请求为对群组资源的成员资源的操作请求且群组服务器执行步骤 303 , 否则， 对群组资源的操作请求为成员资源操作请求， 并执行步骤 303'。
步骤 303、群组服务器针对所述对成员资源的操作请求生成 REQ-ID,记 录生成的 REQ-ID。
在本发明实施例中， 群组服务器生成的 REQ-ID是唯一指示对成员资源 操作请求的标识。 具体的， REQ-ID可以为对群组服务器的标识（如群组服 务器的地址等 )再加上由群组服务器生成的随机数进行哈希加密算法得到。
而本发明实施例中， REQ-ID可以携带在对成员资源的操作请求中的消 息头或消息体中， 本发明实施例在此不做限定。
此外， 群组服务器在生成 REQ-ID后， 还需要存储生成的 REQ-ID, 具体 的可将 REQ-ID作为群组资源属性存储于群组资源中， 比如 requestTag, 以表 明第一群组服务器已处理过与 REQ-ID对应的对成员资源的操作请求。
步骤 303， 、 群组服务器确定接收到的对群组资源的操作请求中携带 REQ-ID后 （即确定对群组资源的操作请求为成员资源操作请求之后） ， 将 携带的 REQ-ID与群组资源属性 requestTag中记录的群组服务器已经处理过 的 REQ-ID进行比较， 判断 requestTag记录的列表中是否存储有与携带的 REQ-ID相同的 REQ-ID。 如果成员资源操作请求中携带 REQ-ID已存储在 requestTag记录的列表中， 则执步骤步 304，， 否则执行步骤 304。
步骤 304、 如果携带 REQ-ID的成员资源操作请求中并没有携带子群组 资源标识，则群组服务器将执行携带 REQ-ID的成员资源操作请求中指示的 操作， 并将成员资源操作请求中携带的 REQ-ID 存储到群组资源属性 requestTag中； 或如果携带 REQ-ID的成员资源操作请求中还携带子群组资 源标识， 则向所述子群组资源标识所标识的子群组资源包含的成员资源所 属的成员设备发送第三成员资源操作请求， 并将成员资源操作请求中携带 的 REQ-ID存储到群组资源属性 requestTag中。其中， 第三成员资源操作请 求根据第二成员资源操作请求生成， 指向子群组标识所标识的子群组资源 包含的各成员资源。
当然， 在群组资源中新增属性 requestTag以记录成员资源操作请求中携 带的 REQ-ID只是一种记录 REQ-ID的方法。 此外，群组服务器还可以维护 每个群组所处理过的请求 REQ-ID列表， 或者通过其他可行的方法来维护， 本发明实施例在此不作限定。 为了简单起见， 以下的步骤和实施例中不再 重复解译和强调， 都以 requestTag方法为例说明。
步骤 304，、 群组服务器确定成员资源操作请求中携带的 REQ-ID 已存 储在 requestTag记录的列表中，则表示与携带的 REQ-ID对应的成员资源操 作请求中指示的操作已被处理。 群组服务器向发送成员资源操作请求的发 送方（其它的群组服务器）返回错误响应（loop detected, 检测到循环）， 指 示该请求消息为重复发送。
步骤 305、 群组服务器接收各成员设备返回的针对成员资源操作请求的 响应消息， 并汇聚各成员设备返回的响应消息。
当然， 如果群组服务器在接收到的响应消息中包含成员设备反回的错误 响应， 则群组服务器可以忽略各成员设备返回的错误响应； 作为一种可选 方式， 群组服务器还可以汇聚这些错误响应。
步骤 306、 群组服务器返回汇聚的响应消息， 并结束本流程。
图 4为本发明实施例提供的又一针对群组资源的操作方法的流程图； 与 图 3 所提供的实施例不同的是， 本实施中请求中的操作请求标识不是必选 参数， 群组服务器在确定收到群组资源的操作请求为对成员资源的操作请 求后， 还需要根据各种条件确定是否针对对成员资源的操作请求生成操作 请求标识 REQ-ID。 图 4所示的实施例具体包括如下步骤：
步骤 401、 群组服务器接收到对群组资源的操作请求；
具体的， 对群组资源的操作请求可以为对成员资源的操作请求。 该对 成员资源的操作请求可以为步骤 201中的对成员资源的访问请求， 还可以是 对针成员资源的更新请求以及其它的请求， 本发明实施例在此不做限定， 所述对成员资源的操作请求中成员资源所属群组资源的群组资源标识。
或群组服务哭接收到的对群组资源的操作请求为携带有 REQ-ID的成员 资源操作请求， 且成员资源操作请求也可以携带成员资源所属群组资源的 群组资源标识。
步骤 402、 群组服务器确定对群组资源的操作请求中是否携带操作请 求标识 REQ-ID, 若对群组资源的操作请求中没有携带 REQ-ID, 则对群组 资源的操作请求为对成员资源的操作请求并执行步骤 402-1 , 否则， 对群组 资源的操作请求为成员资源操作请求， 并执行步骤 403'。
步骤 402-1、 群组服务器判断接收到的操作请求是否为更新请求， 如果 是更新请求， 执行步骤 403 , 否则， 执行步骤 402-2;
步骤 402-2、 群组服务器根据对成员资源的操作请求中携带的群组资源 标识，确定群组资源标识所标识的群组资源是否包含子群组资源（ subgroup ) 作为成员资源， 如果群组资源标识所标识的的群组资源包含子群组资源 ( subgroup )作为成员资源， 执行步骤 402-3 , 否则， 执行步骤 404;
步骤 402-3、 群组服务器确定群组资源包含的子群组资源 （subgroup ) 是否为远程子群组资源 （remote subgroup )。 如是， 执行步骤 403 , 否则执 行步骤 402-4;
本发明实施例中， 远程子群组资源为由其它的群组服务器创建的群组资 源， 且该由其它群组服务器创建的群组资源作为对成员资源的操作请求中 携带的群组资源标识所标识的群组资源的成员资源。 例如， 假设接收到的 对 成 员 资 源 的 操 作 请 求 为 ： GET http://g 1.example.org/groups/grp3/membersContent/data HTTP/1.1 , 贝1 J接^:该 成员资源操作请求的群组服务器为 gl , 该对成员资源的操作请求中携带的 群组资源标识为： grp3; 没与群组资源标识 grp3对应的群组资源 Group 3 包含的成员资源如下：
m 1 = coap://dl . example.com/xxx/templ
m 3 = coap://d2. example.org/xxx/temp 1
Group 4 = http ://g4. example. coni/groups/grp4
则 群 组 服 务 器 gl 根 据 成 员 资 源 Grp4 = littp:/7'g4. example, com/groups/grp4 '确定 grp4 †应 ά 群组资〉 Group 4所属的 群组服务器为 g4, 而非 gl。 因此， Group 3所包含的子群组资源 Goup 4为 远程子群组资源。 即， 步骤 402-3中， 群组服务器确定群组资源 Group 3包 含的子群组资源 （Goup 4 ) 中包含远程子群组资源 （Goup 4 )。
402-4、群组服务器确定对成员资源的操作请求中携带的群组资源标识所 标识的群组资源 （假设为群组资源）是否存在群组嵌套。 也就是说， 群组 服务器确定群组资源所包含的成员资源中是否包含子群组资源， 且子群组 资源所包含的成员资源中是否包含群组资源。 即对成员资源的操作请求中 携带的群组资源标识所标识的群组资源是否与该群组资源包含的子群组资 源互为子群组资源。 进一步的， 群组服务器获取群组资源所包含的成员资 源列表， 以及群组资源包含的成员资源包含子群组资源 （假设为子群组资 源） 时的子群组资源 （即子群组资源） 包含的成员资源列表， 再确定子群 组资源所包含的成员资源中是否包含对成员资源的操作请求中携带的群组 资源标识所标识的群组资源 （即群组资源）。
作为一种实施例， 假设接收到的对成员资源的操作请求为： GET http://g 1.example.org/groups/grp 1/membersContent/data HTTP/1.1。
如图 1中 Group 1包含的成员资源列表具体为：
m 1 = coap://dl . example.com/xxx/templ
m 2 = coap：〃 gl .example.com/xxx/templ
Group 2 = http：〃g 1. examp le . org/ roup s/ gxp2；
Group2包含的群组资源列表具体为：
m 1 = coap://dl . example.com/xxx/templ
m 3 = coap://d2. example.org/xxx/temp 1
Group 1 = bttp://g 1. example.com/groups/grp 1
则， 群组资源 Group 1和 Group 2分别存在群组嵌套。 在本步骤中， 群 组服务器 gl确定 Groupl是否存在群组嵌套需要根据 Group 1包含的成员资 源 Group 2所包含的成员资源确定，此时要求群组服务器获取 Group 1包含 的成员资源 Group 2的成员资源列表。前述的 Group 2所属的群组服务器与 Group 1所属的群组服务器均为 gl , ra '比 gl可以很容易获取 Group 2包含 的成员资源。
假设， 前述 Group 1包含的成员资源 Group 2的访问地址为： Grp2 = htt ://g2. example. org/groups/grp2；則 gl还需要才艮据- Group 2的访问地址 Grp2 = http!//g2.examp1e.org/groups/gn 2从群组服务器 gl获取 Group 2包含的成员 资源。作为一种可选方式，在执行本发明时， 当群组服务器 gl确定 Group 1 包含的成员资源 Group 2所属的群组服务器为 g2 时， 则可直接根据步骤 402-2确定群组资源 Group 1包含的子群组资源 Group 2中包含远程子群组 资源 Group2, 而无需再从 Group2所属的群组服务器 g2中获取 Group2所 包含的成员资源。
步骤 403与步骤 303相同， 本发明实施例在此不在详述。
步骤 403， 与步骤 303， 相同， 本发明实施例在此不在详述。
步骤 404与步骤 304相同， 本发明实施例在此不在详述。
步骤 404， 与步骤 304， 相同， 本发明实施例在此不在详述。
步骤 405与步骤 305相同， 本发明实施例在此不在详述。
步骤 406与步骤 306相同， 本发明实施例在此不在详述。
值得说明的是： 步骤 402-1到步骤 402-4是可选的， 可以选择执行部分， 并且步骤 402-1和步骤 402-2到步骤 402-4之间没有明确的先后顺序。
图 5为本发明实施例提供的针对存在嵌套群组的群组资源的成员资源的 操作请求的方法流程图。以图 1所示的群组资源 Group 1为例包括如下步骤： 步骤 501、 应用服务器给群组资源 Groupl所在的第一群组服务器 gl发 送对群组资源 Group 1的操作请求。
具体的， 应用服务器可以为独立的应用服务器， 还可以是 M2M网络的 应用服务器， 或者是设置于网关中的应用模块， 又或者是设置于 M2M设备 的应用模块， 应用服务器还可以是群组资源所在宿主设备的业务能力层的 模块。
与步骤 301类似， 对群组资源 Group 1的操作请求可以是对成员资源的 操作请求或携带有 REQ-ID的成员资源操作请求。 并且， 对群组资源 Group 1的操作请求中携带 Group 1的群组资源标识。 本发明实施例假设对群组资 源 Group 1的操作请求为对成员资源的操作请求。此外，对成员资源的操作 请求可以与步骤 201 类似的对成员资源的访问请求或对成员资源的更新、 删除等请求， 本发明实施例在此不做限定。
第一群组服务器 gl收到对群组资源 Group 1的操作请求后，确定对群组 资源的操作请求中并没有携带操作请求标识 REQ-ID, 即对群组资源 Group 1的操作请求为对成员资源的操作请求。 并执行步骤 402-1到 402-4的任一 步骤。
在本发明实施例中， 假设 Group 1 包括的成员资源中包括子群组资源 Group 2,且 Group 2归属于第二群组服务器， 即 Group 2属于远程子群组， 且 Group 2同时包含 Group 1 , 即第一群组服务器可以在步骤 402-3中确定 Group 1包含远程子群组。 因此，第一群组服务器在执行步骤 402-2到 402-4 时， 可以在步骤 402-1到 402-4中的任一步骤后执行步骤 403 , 即生成针对 所述对成员资源操作请求的 REQ-ID, 记录生成的 REQ-ID。
当然， 作为另一可选方式， 第一群组服务器还可以在收到确定对群组资 源的操作请求中并没有携带操作请求标识 REQ-ID, 即对群组资源 Group 1 的操作请求为对成员资源的操作请求后， 直接执行步骤 402-1 , 判断对成员 资源的操作请求是否为更新请求。 因为对成员资源的操作请求为更新请求， 则生成针对所述对成员资源操作请求的 REQ-ID, 记录生成的 REQ-ID, 不 并执行步骤 402-2到 402-4的任一步骤， 否则， 选择执行步骤 402-2至步骤 402-4; 步骤 502、 第一群组服务器执行成员资源操作请求中指示的操作， 即将生成的 REQ-ID携带在成员资源操作请求中发送给 Group 1所包含的成 员资源各自所属的成员设备， 即第二群组服务器 g2,成员设备 1和成员设备 2。
步骤 503、 成员设备 1和成员设备 2在收到成员资源操作请求后， 执行 成员资源操作请求中指示的操作。
具体的， 成员设备 1 和成员设备 2 确定成员资源操作请求中携带 REQ-ID, 将确定成员资源操作请求中携带的 REQ-ID 已存储在 requestTag 记录的列表中，则表示与携带的 REQ-ID对应的成员资源操作请求中指示的 操作已被执行， 不再执行该操作请求中指示的操作， 而向第一群组服务器 返回错误响应。
然而， 在本发明实施例中， 假设成员设备 1和成员设备 2确定成员资源 操作请求中携带的 REQ-ID并没有存储在 requestTag记录的列表中， 则在 requestTag记录的列表中存储成员资源操作请求中携带的 REQ-ID, 并执行 成员资源操作请求中指示的操作。
步骤 504和 504，、成员设备 1和成员设备 2分别向第一群组服务器返回 响应消息。
步骤 505、 第二群组服务器确定成员资源操作请求中携带的 REQ-ID并 没有存储在 requestTag记录的列表中，则在 requestTag记录的列表中存储成 员资源操作请求中携带的 REQ-ID。
当然， 假设第二群组服务器确定成员资源操作请求中携带的 REQ-ID已 存储在 requestTag记录的列表中，则表示与携带的 REQ-ID对应的成员资源 操作请求中指示的操作已被执行， 不再执行该操作请求中指示的操作， 而 向第一群组服务器返回错误响应。
步骤 506和 506，、 第二群组服务器分别向 Group 2所包含的成员资源 Group 1,成员设备 1和成员设备 3发送成员资源请求消息。
步骤 507, 与步骤 503类似。 成员设备 3确定成员资源操作请求中携带 的 REQ-ID并没有存储在 requestTag记录的列表中，则在 requestTag记录的 列表中存储成员资源操作请求中携带的 REQ-ID,并执行成员资源操作请求 中指示的操作。
步骤 507， 和步骤 507"、 第一群组服务器和成员设备 1确定成员资源操 作请求中携带的 REQ-ID已存储在 requestTag记录的列表中，则表示与携带 的 REQ-ID对应的成员资源操作请求中指示的操作已被执行，不再执行该操 作请求中指示的操作。
步骤 508、 成员设备 3向第二群组服务器返回响应消息。
步骤 508， 和步骤 508"、 第一群组服务器和成员设备 1分别向第二群 组服务器返回错误响应。
步骤 509、 第二群组服务器将接收到的来自第一群组服务器、 成员设备 1和成员设备 3的响应消息进行汇聚。 然而， 由于第一群组服务器、 成员设 备 1均返回的是错误响应， 对第二群组服务器并不需要对成员设备 3返回 的响应消息并不需要汇聚。
步骤 510、 第二群组服务器向第一群组服务器返回第一汇聚的群组响应 消息。
步骤 511、 第一群组服务器将接收到的来自成员设备 1和成员设备 2的 响应消息， 以及来自第二群组服务器的第一汇聚的群组响应消息进行汇聚. 步骤 512、 第一群组服务器向应用服务器返回第二汇聚的群组成员响应 消息。
图 5所示的 group 1 和 group2假设位于不同的群组服务器， group2为 group 1的远程子群组 remote group。 作为一种可选方式, group 1和 group2 可能处于相同的群组服务器， 即 group2 为 groupl 的本地子群组 local subgroup„
图 6为本发明实施例提供的针对群组资源的操作方法的流程图， 包括如 下步骤：
步骤 601、 接收第二成员资源操作请求；
具体的， 成员设备接收成员设备所述的群组服务器发送的成员资源操 作请求， 或群组服务器如 g2接收其它的群组服务器 gl发送的第二成员资源 操作请求（如步骤 502所示） 。 因此， 本发明实施例将接收第二请求的成员 设备或群组服务器统称执行针对群组资源的操作的装置。
步骤 602、 确定所述第二成员资源操作请求中携带第二操作请求标识； 具体的， 执行针对群组资源的操作的装置确定群组服务器发送的第二 成员资源操作请求中包含第二操作请求标识。 当然， 群组资源的操作的装 置 （尤其是成员设备）还有可能接收不包含操作请求标识的成员资源操作 请求， 本发明实施例对接收到不包含操作请求标识的成员资源操作请求后 的操作不作叙述。
步骤 603、判断存储的操作请求标识列表中是否包含携带的第二操作请 求标识， 并根据判断结果处理第二成员资源操作请求。
具体的 , 并根据判断结果处理第二成员资源操作请求具体为： 当所述第二成员资源操作请求还携带子群组资源标识时， 所述根据判 断结果处理第二成员资源操作请求具体为： 判断存储的操作请求标识列表 中包含所述第二操作请求标识， 向第二成员资源操作请求的发送方返回错 误响应； 或判断存储的操作请求标识列表中不包含所述第二操作请求标识， 向所述子群组资源标识所标识的群组资源包含的成员资源所属的成员设备 发送第三成员资源操作请求； 或
当所述第二成员资源操作请求不携带子群组资源标识时， 所述根据判 断结果处理第二成员资源操作请求具体为： 判断存储的操作请求标识列表 中包含所述第二操作请求标识， 向第二成员资源操作请求的发送方返回错 误响应； 或， 判断存储的操作请求标识列表中不包含携所述第二作请求标 识， 存储所述第二操作请求标识， 并执行成员资源操作请求中指示的操作。
在上述实施例中， 执行针对群组资源的操作的装置在接收到第二成员 资源操作请求后， 可以确定第二成员资源操作请求包含第二操作请求标识， 并根据判断的结果处理第二成员资源操作请求， 从而可以避免对已处理过 的操作请求进行重复处理。
此外， 作为图 6 的对应的实施例的补充， 由于执行针对群组资源的操 作的装置可以是群组服务器， 因此还可以执行图 2-图 4对应的实施例中群 组服务器执行的步骤， 本发明实施例在此不再详述。
图 7为本发明实施例提供的群组服务器的结构示意图， 包括： 接收模块 701 , 用于接收对成员资源的操作请求； 生成模块 702, 用于 针对所述对成员资源的操作请求生成第一操作请求标识； 发送模块 703 , 用 于向所述成员资源所属的成员设备发送成员资源操作请求， 所述第一成员 资源操作请求中包含所述第一操作请求标识； 以便所述成员资源所属的成 员设备根据所述第一操作请求标识判断成员设备存储的操作请求标识中是 否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作请求。
进一步的， 所述对成员资源的操作请求中携带所述成员资源所属群组 资源的群组资源标识； 群组服务器还包括： 确定模块 704, 用于根据所述群 组资源标识确定需针对所述对成员资源的操作请求生成第一操作请求标 识。
进一步的， 确定模块 704具体用于： 根据所述群组资源标识确定所述群 组资源标识所标识的群组资源中包含子群组资源作为成员资源； 确定需针 对对成员资源的操作请求生成第一操作请求标识； 或， 确定模块 704具体用 于： 根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含的子群组资源为远程群组资源， 或根据所述群组资源标识确定所述群组 资源标识所标识的群组资源所包含的成员资源中包含与对与所述群组资源 标识对应的群组资源； 确定需针对对成员资源的操作请求生成第一操作请 求标识。
进一步的， 群组服务器还包括操作请求确定模块 705 , 用于确定对成员 资源的操作请求为更新请求。
进一步的， 接收模块 701进一步用于接收第二成员资源操作请求， 所述 第二成员资源操作请求中包含第二操作请求标识； 群组服务器还包括： 判 断模块 706, 用于判断存储的操作请求标识列表中包含所述第二操作请求标 识， 向第二成员资源操作请求的发送方返回错误响应； 或， 用于判断存储 的操作请求标识列表中不包含所述第二操作请求标识， 存储所述第二操作 请求标识， 并执行第二成员资源操作请求中指示的操作； 或， 接收模块 701 进一步用于接收第二成员资源操作请求， 所述第二成员资源操作请求中包 含第二操作请求标识及子群组资源标识； 判断模块 706, 用于判断存储的操 作请求标识列表中包含所述第二操作请求标识， 向第二成员资源操作请求 的发送方返回错误响应； 或用于判断存储的操作请求标识列表中不包含所 述第二操作请求标识， 向所述子群组资源标识所标识的群组资源包含的成 员资源所属的成员设备发送第三成员资源操作请求。
图 7b为本发明实施例提供的又一群组服务器的结构示意图， 包括存储 器 700, 和处理器 600。 其中存储器 600用于存储图 7a所述的各模块， 处理器 600与存储器 700连接， 运行存储器 600中的各模块执行存储器 600中各模块 的相应功能。 图 7b中存储器 600中各模块的功能与图 7a中的各模块的功能相 同， 本发明实施例在此不再详述。
图 8为本发明实施例提供的执行针对群组资源的操作的装置结构示意 图， 包括： 接收模块 801 , 用于接收第二成员资源操作请求； 确定模块 802, 用于确定所述成员资源操作请求中携带第二操作请求标识； 判断模块 803 , 用于判断存储的操作请求标识列表中是否包含所述操作请求标识， 并根据 判断结果执行成员第二资源操作请求中指示的操作。
可选的， 当所述第二成员资源操作请求还携带子群组资源标识时， 判 断模块 803具体用于判断存储的操作请求标识列表中包含所述第二操作请 求标识， 向第二成员资源操作请求的发送方返回错误响应； 或判断存储的 操作请求标识列表中不包含所述第二操作请求标识， 向所述子群组资源标 识所标识的群组资源包含的成员资源所属的成员设备发送第三成员资源操 作请求； 或， 当所述第二成员资源操作请求不携带子群组资源标识时， 所 述判断模块具体用于： 判断存储的操作请求标识列表中包含所述第二操作 请求标识， 向第二成员资源操作请求的发送方返回错误响应； 判断存储的 操作请求标识列表中不包含所述第二操作请求标识， 存储所述第二操作请 求标识， 并执行所述第二成员资源操作请求中指示的操作。
可选的,接收模块 801还用于接收对成员资源的操作请求。生成模块 804 用于针对所述对成员资源的操作请求生成第一操作请求标识； 发送模块 804, 用于向所述成员资源所属的成员设备发送成员资源操作请求， 所述第 一成员资源操作请求中包含所述第一操作请求标识； 以便所述成员资源所 属的成员设备根据所述第一操作请求标识判断成员设备存储的操作请求标 识中是否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作 请求。
可选的， 所述对成员资源的操作请求中携带所述成员资源所属群组资 源的群组资源标识； 确定模块 802还用于： 根据所述群组资源标识确定需针 对所述对成员资源的操作请求生成第一操作请求标识。
可选的， 所述确定模块 802根据所述群组资源标识确定需针对所述对成 员资源的操作请求生成第一操作请求标识具体为： 根据所述群组资源标识 确定所述群组资源标识所标识的群组资源中包含子群组资源作为成员资 源； 确定需针对对成员资源的操作请求生成第一操作请求标识； 或， 根据 所述群组资源标识确定所述群组资源标识所标识的群组资源中包含的子群 组资源为远程群组资源， 或根据所述群组资源标识确定所述群组资源标识 所标识的群组资源所包含的成员资源中包含与对所述群组资源标识所标识 的群组资源； 确定需针对对成员资源的操作请求生成第一操作请求标识。
可选的， 确定模块 802进一步用于： 确定对成员资源的操作请求为更新 请求。
图 8b为本发明实施例提供的又一执行针对群组资源的操作的装置的结 构示意图， 包括存储器 800, 和处理器 900。 其中存储器 600用于存储图 8a所 述的各模块， 处理器 900与存储器 800连接， 运行存储器 800中的各模块执行 存储器 800中各模块的相应功能。 图 8b中存储器 800中各模块的功能与图 8a 中的各模块的功能相同， 本发明实施例在此不再详述。
由上述本发明的实施例提供的技术方案可以看出， 通过在发送给成员 设备的成员资源操作请求中携带操作请求标识， 以便成员资源所属的成员 设备根据所述操作请求标识判断成员设备存储的操作请求标识中是否包含 所述操作请求标识， 并根据判断结果处理成员资源操作请求。 假设成员设 备存储的操作请求标识中包含所述操作请求标识， 则返回错误响应， 不再 处理成员资源操作请求。 从而， 可以避免后续成员设备重复处理成员资源 操作请求。
上述针对群组服务器或执行针对群组资源的操作的装置中包含的各模 块的处理功能的实施方式在之前的方法实施例中已经描述， 在此不再重复 描述。 此外， 在 M2M网络中， M2M平台可以是各计算机， 具有处理器的设 备。 M2M网关和 M2M终端在设备上没有严格的区分， 比如做网关的设备也 可以做为终端， 此外为各种终端设备， 如手机， 计算机， PDA, 笔记本电 脑， 远程控制器， 家用电器， 各种仪器仪表、 传感器等都可以做为 M2M网 络的网关或终端。 在上述模块实施例中， 所包括的各个模块只是按照功能 逻辑进行划分的， 但并不局限于上述的划分， 只要能够实现相应的功能即 可； 另外， 各功能模块的具体名称也只是为了便于相互区分， 并不用于限 制本发明的保护范围。 上述实现对群组资源操作的方法及群组服务器或执 行针对群组资源的操作的装置的各功能模块的功能均可以由群组服务器或 执行针对群组资源的操作的装置的处理器运行各模块完成， 以及上述实现 群组服务器执行的方法及群组服务器各功能模块的功能均可以由群组服务 器的处理器完成。
此外， 图 7a和图 7b中的群组服务器可以执行前述方法流程实施例中群 组服务器执行的任一步骤， 图 8a和图 8b中执行针对群组资源的操作的装置 既可以执行前述方法流程实施例中群组服务器执行的任一步骤， 也可以执 行前述方法流程实施例中成员设备执行的任何步骤， 本发明在此不再—— 伴述。 以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并 不局限于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到的变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本 发明的保护范围应该以权利要求的保护范围为准。

Claims

权利要求
1、 一种针对群组资源的操作方法， 其特征在于， 包括：
接收对成员资源的操作请求；
针对所述对成员资源的操作请求生成第一操作请求标识；
向所述成员资源所属的成员设备发送第一成员资源操作请求， 所述第 一成员资源操作请求中包含所述第一操作请求标识； 以便所述成员资源所 属的成员设备根据所述第一操作请求标识判断成员设备存储的操作请求标 识中是否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作 请求。
2、 如权利要求 1所述的方法， 其特征在于， 所述对成员资源的操作请 求中携带所述成员资源所属群组资源的群组资源标识； 所述针对对成员资 源的操作请求生成第一操作请求标识之前， 该方法进一步包括：
根据所述群组资源标识确定需针对所述对成员资源的操作请求生成第 一操作请求标识。
3、 如权利要求 2所述的方法， 其特征在于， 所述根据所述群组资源标 识确定需针对对成员资源的操作请求生成第一操作请求标识包括：
根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含子群组资源作为成员资源；
确定需针对对成员资源的操作请求生成第一操作请求标识。
4、 如权利要求 2所述的方法， 其特征在于， 所述根据所述群组资源标 识确定需针对对成员资源的操作请求生成第一操作请求标识具体为：
根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含的子群组资源为远程群组资源， 或根据所述群组资源标识确定所述群组 资源标识所标识的群组资源所包含的成员资源中包含所述群组资源标识所 标识的群组资源；
确定需针对对成员资源的操作请求生成第一操作请求标识。
5、 如权利要求 1所述的方法， 其特征在于， 所述针对对成员资源的操 作请求生成第一操作请求标识之前， 该方法进一步包括：
确定对成员资源的操作请求为更新请求。
6、 如权利要求 1-5任一所述的方法， 其特征在于，
该方法进一步包括： 接收第二成员资源操作请求， 所述第二成员资源 操作请求中包含第二操作请求标识； 判断存储的操作请求标识列表中包含 所述第二操作请求标识， 指示的操作向第二成员资源操作请求的发送方返 回错误响应， 或判断存储的操作请求标识列表中不包含所述第二操作请求 标识， 存储所述第二操作请求标识， 并执行第二成员资源操作请求中指示 的操作； 或
该方法进一步包括： 接收第二成员资源操作请求， 所述第二成员资源 操作请求中包含第二操作请求标识以及子群组资源标识； 判断存储的操作 请求标识列表中包含所述第二操作请求标识时， 向第二成员资源操作请求 的发送方返回错误响应， 或判断存储的操作请求标识列表中不包含所述第 二操作请求标识时， 向所述子群组资源标识所标识的子群组资源包含的成 员资源所属的成员设备发送第三成员资源操作请求。
7、 一种针对群组资源的操作方法， 其特征在于， 包括：
接收第二成员资源操作请求；
确定所述第二成员资源操作请求中携带第二操作请求标识；
判断存储的操作请求标识列表中是否包含所述第二操作请求标识， 并 根据判断结果处理第二成员资源操作请求。
8、 如权利要求 7所述的方法， 其特征在于， 当所述第二成员资源操作 请求还携带子群组资源标识时， 所述根据判断结果处理第二成员资源操作 请求具体为：
判断存储的操作请求标识列表中包含所述第二操作请求标识时， 向第 二成员资源操作请求的发送方返回错误响应； 或判断存储的操作请求标识 列表中不包含所述第二操作请求标识时， 向所述子群组资源标识所标识的 子群组资源包含的成员资源所属的成员设备发送第三成员资源操作请求； 当所述第二成员资源操作请求不携带子群组资源标识时， 所述根据判 断结果处理第二成员资源操作请求具体为：
判断存储的操作请求标识列表中包含所述第二操作请求标识时， 向第 二成员资源操作请求的发送方返回错误响应； 或， 判断存储的操作请求标 识列表中不包含携所述第二作请求标识时， 存储所述第二操作请求标识， 并执行第二成员资源操作请求中指示的操作。
9、 如权利要求 7或 8所述的方法， 其特征在于， 该方法进一步包括： 接收对成员资源的操作请求；
针对所述对成员资源的操作请求生成第一操作请求标识；
向所述成员资源所属的成员设备发送第一成员资源操作请求；所述第一 成员资源操作请求中包含第一操作请求标识， 以便所述成员资源所属的成 员设备根据所述第一操作请求标识判断成员设备存储的操作请求标识中是 否包含所述第一操作请求标识， 并根据判断结果处理成员资源操作请求。
10、 如权利要求 9所述的方法， 其特征在于， 所述对成员资源的操作请 求中携带所述成员资源所属群组资源的群组资源标识； 所述针对对成员资 源的操作请求生成第一操作请求标识之前， 该方法进一步包括：
根据所述群组资源标识确定需针对所述对成员资源的操作请求生成第 一操作请求标识。
11、 如权利要求 10所述的方法， 其特征在于， 所述根据所述群组资源 标识确定需针对对成员资源的操作请求生成第一操作请求标识具体为： 根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含子群组资源作为成员资源；
确定需针对对成员资源的操作请求生成第一操作请求标识。
12、 如权利要求 10所述的方法， 其特征在于， 所述根据所述群组资源 标识确定需针对对成员资源的操作请求生成第一操作请求标识具体为： 根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含的子群组资源为远程群组资源， 或根据所述子群组资源标识确定所述子 群组资源标识所标识的子群组资源所包含的成员资源中包含所述群组资源 标识所标识的群组资源；
确定需针对对成员资源的操作请求生成第一操作请求标识。
13、 如权利要求 9所述的方法， 其特征在于， 所述针对对成员资源的操 作请求生成操作请求标识之前， 该方法进一步包括：
确定对成员资源的操作请求为更新请求。
14、 一种群组服务器， 其特征在于， 包括：
接收模块， 用于接收对成员资源的操作请求；
生成模块， 用于针对所述对成员资源的操作请求生成第一操作请求标 识；
发送模块， 用于向所述成员资源所属的成员设备发送成员资源操作请 求， 所述第一成员资源操作请求中包含所述第一操作请求标识； 以便所述 成员资源所属的成员设备根据所述第一操作请求标识判断成员设备存储的 操作请求标识中是否包含所述第一操作请求标识， 并根据判断结果处理成 员资源操作请求。
15、 如权利要求 14所述的群组服务器， 其特征在于， 所述对成员资源 的操作请求中携带所述成员资源所属群组资源的群组资源标识；
所述群组服务器进一步包括：
确定模块， 用于根据所述群组资源标识确定需针对所述对成员资源的 操作请求生成第一操作请求标识。
16、 如权利要求 15所述的群组服务器， 其特征在于，
所述确定模块具体用于： 根据所述群组资源标识确定所述群组资源标 识所标识的群组资源中包含子群组资源作为成员资源； 确定需针对对成员 资源的操作请求生成第一操作请求标识； 或
所述确定模块具体用于： 根据所述群组资源标识确定所述群组资源标 识所标识的群组资源中包含的子群组资源为远程群组资源， 或根据所述群 组资源标识确定所述群组资源标识所标识的群组资源所包含的成员资源中 包含与对所述群组资源标识所标识的群组资源； 确定需针对对成员资源的 操作请求生成第一操作请求标识。
17、 如权利要求 14所述的群组服务器， 其特征在于， 进一步包括： 操作请求确定模块， 用于确定对成员资源的操作请求为更新请求。
18、 如权利要求 14-17任一所述的群组服务器， 其特征在于，
所述接收模块进一步用于： 接收第二成员资源操作请求， 所述第二成 员资源操作请求中包含第二操作请求标识； 所述群组服务器进一步包括： 判断模块， 用于判断存储的操作请求标识列表中包含所述第二操作请求标 识， 向第二成员资源操作请求的发送方返回错误响应； 或， 用于判断存储 的操作请求标识列表中不包含所述第二操作请求标识， 存储所述第二操作 请求标识， 并执行第二成员资源操作请求中指示的操作； 或
所述接收模块进一步用于： 接收第二成员资源操作请求， 所述第二成 员资源操作请求中包含第二操作请求标识及子群组资源标识， 所述群组服 务器进一步包括： 判断模块用于判断存储的操作请求标识列表中包含所述 第二操作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 或 用于判断存储的操作请求标识列表中不包含所述第二操作请求标识， 向所 述子群组资源标识所标识的子群组资源包含的成员资源所属的成员设备发 送第三成员资源操作请求。
19、 一种执行针对群组资源的操作的装置， 其特征在于， 包括： 接收模块， 用于接收第二成员资源操作请求；
确定模块， 用于确定所述成员资源操作请求中携带第二操作请求标识； 判断模块， 用于判断存储的操作请求标识列表中是否包含所述操作请 求标识， 并根据判断结果处理第二成员资源操作请求。
20、 如权利要求 19所述的装置， 其特征在于，
当所述第二成员资源操作请求还携带子群组资源标识时， 所述判断模 块具体用于： 判断存储的操作请求标识列表中包含所述第二操作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 或判断存储的操作请求 标识列表中不包含所述第二操作请求标识， 向所述子群组资源标识所标识 的子群组资源包含的成员资源所属的成员设备发送第三成员资源操作请 求； 或
当所述第二成员资源操作请求不携带子群组资源标识时， 所述判断模 块具体用于： 判断存储的操作请求标识列表中包含所述第二操作请求标识， 向第二成员资源操作请求的发送方返回错误响应； 判断存储的操作请求标 识列表中不包含所述第二操作请求标识， 存储所述第二操作请求标识， 并 执行所述第二成员资源操作请求中指示的操作。
21、 如权利要求 19或 20所述的装置， 其特征在于，
所述接收模块进一步用于： 接收对成员资源的操作请求； 所述装置进 一步包括：
生成模块， 用于针对所述对成员资源的操作请求生成第一操作请求标 识；
发送模块， 用于向所述成员资源所属的成员设备发送成员资源操作请 求， 所述第一成员资源操作请求中包含所述第一操作请求标识； 以便所述 成员资源所属的成员设备根据所述第一操作请求标识判断成员设备存储的 操作请求标识中是否包含所述第一操作请求标识， 并根据判断结果处理成 员资源操作请求。
22、 如权利要求 21所述的装置， 其特征在于， 所述对成员资源的操作 请求中携带所述成员资源所属群组资源的群组资源标识；
所述确定模块进一步用于： 根据所述群组资源标识确定需针对所述对 成员资源的操作请求生成第一操作请求标识。
23、 如权利要求 22所述的装置， 其特征在于， 所述确定模块根据所述 群组资源标识确定需针对所述对成员资源的操作请求生成第一操作请求标 识具体为：
根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含子群组资源作为成员资源； 确定需针对对成员资源的操作请求生成第一 操作请求标识； 或
根据所述群组资源标识确定所述群组资源标识所标识的群组资源中包 含的子群组资源为远程群组资源， 或根据所述群组资源标识确定所述群组 资源标识所标识的群组资源所包含的成员资源中包含对与所述群组资源标 识所标识的群组资源； 确定需针对对成员资源的操作请求生成第一操作请 求标识。
24、 如权利要求 22所述的装置， 其特征在于，
所述确定模块进一步用于： 确定对成员资源的操作请求为更新请求。
PCT/CN2012/078742 2012-02-29 2012-07-17 针对群组资源的操作方法、群组服务器 WO2013127145A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12869697.8A EP2706729A4 (en) 2012-02-29 2012-07-17 OPERATION EXECUTION METHOD FOR GROUP RESOURCES AND GROUP SERVER
US14/145,844 US8918528B2 (en) 2012-02-29 2013-12-31 Operating group resources in sub-groups and nested groups
US14/546,293 US9438601B2 (en) 2012-02-29 2014-11-18 Operating group resources in sub-groups and nested groups

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210050131.1 2012-02-29
CN201210050131.1A CN103297468B (zh) 2012-02-29 2012-02-29 针对群组资源的操作方法、群组服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/145,844 Continuation US8918528B2 (en) 2012-02-29 2013-12-31 Operating group resources in sub-groups and nested groups

Publications (1)

Publication Number Publication Date
WO2013127145A1 true WO2013127145A1 (zh) 2013-09-06

Family

ID=49081577

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/078742 WO2013127145A1 (zh) 2012-02-29 2012-07-17 针对群组资源的操作方法、群组服务器

Country Status (4)

Country Link
US (2) US8918528B2 (zh)
EP (2) EP2706729A4 (zh)
CN (1) CN103297468B (zh)
WO (1) WO2013127145A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103297468B (zh) * 2012-02-29 2017-12-01 华为技术有限公司 针对群组资源的操作方法、群组服务器
CN103873508B (zh) * 2012-12-12 2016-04-13 腾讯科技（深圳）有限公司 一种隐藏活动组成员识别信息的方法、服务器及终端
CN103944727B (zh) * 2014-04-25 2017-11-10 天地融科技股份有限公司 操作请求处理方法
CN103944726B (zh) * 2014-04-25 2018-05-29 天地融科技股份有限公司 操作请求处理系统
WO2016008102A1 (zh) * 2014-07-15 2016-01-21 华为技术有限公司 对群组资源中成员资源的操作请求的处理方法及装置
CN105635930B (zh) * 2014-10-31 2020-04-10 海尔优家智能科技（北京）有限公司 对组成员资源的删除操作的执行方法、装置及发起者装置
WO2016119260A1 (zh) * 2015-01-30 2016-08-04 华为技术有限公司 一种获取成员资源数据替代值的方法、装置及系统
KR102269035B1 (ko) * 2015-04-21 2021-06-24 삼성전자주식회사 서버 및 서버의 그룹 액션 제어방법
CN104954998A (zh) * 2015-04-28 2015-09-30 北京海尔广科数字技术有限公司 一种群组成员信息更新的方法和装置
CN105897500A (zh) * 2015-12-09 2016-08-24 乐视网信息技术（北京）股份有限公司 图片处理方法及装置
CN107018165A (zh) * 2016-01-28 2017-08-04 阿里巴巴集团控股有限公司 控制物联网设备的方法及装置、服务器、移动设备
CN108075908B (zh) * 2016-11-11 2023-01-17 京东方科技集团股份有限公司 处理操作请求的方法及装置
WO2018126065A1 (en) 2016-12-30 2018-07-05 Intel Corporation Decentralized data storage and processing for iot devices
CN109302300B (zh) * 2017-07-25 2022-03-15 阿里巴巴集团控股有限公司 数据分配和处理方法、系统及计算机可读记录介质
CN109905431B (zh) 2017-12-08 2021-01-26 京东方科技集团股份有限公司 消息处理方法及系统、存储介质、电子设备
CN110391963A (zh) * 2018-04-17 2019-10-29 成都野望数码科技有限公司 一种群组重合度的确定方法及装置
CN110798388B (zh) * 2019-11-05 2021-11-02 杭州行至云起科技有限公司 一种通信控制的方法及网关
US11769199B2 (en) * 2021-04-14 2023-09-26 Visa International Service Association System, method, and computer program product for network anomaly detection

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083537A (zh) * 2006-05-31 2007-12-05 华为技术有限公司 一种实现设备管理的方法、装置和系统
WO2009002236A1 (en) * 2007-06-27 2008-12-31 Telefonaktiebolaget Lm Ericsson (Publ) A method and apparatus for enabling connectivity in a communication network
CN102136933A (zh) * 2010-09-30 2011-07-27 华为技术有限公司 设备管理方法、中间件及机器通信平台、设备和系统
CN102244855A (zh) * 2010-05-10 2011-11-16 华为技术有限公司 一种基于位置的机器对机器通信方法、系统和装置

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19848342A1 (de) 1998-10-21 2000-04-27 Philips Corp Intellectual Pty Lokales Netzwerk mit einem Brücken-Terminal zur Übertragung von Daten zwischen mehreren Sub-Netzwerken und zur Schleifendetektion
US6839752B1 (en) * 2000-10-27 2005-01-04 International Business Machines Corporation Group data sharing during membership change in clustered computer system
US7054314B2 (en) * 2001-08-20 2006-05-30 Skystream Networks Inc. Controlling multiple nodes divided into groups
US8577795B2 (en) * 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US8341402B2 (en) * 2005-01-19 2012-12-25 Samsung Electronics Co., Ltd. Method of controlling content access and method of obtaining content key using the same
JP4862463B2 (ja) * 2006-04-11 2012-01-25 ブラザー工業株式会社 情報通信システム、コンテンツカタログ情報検索方法、及びノード装置等
US8115948B2 (en) 2006-04-21 2012-02-14 Microsoft Corporation Interactive paper system
US8559610B2 (en) * 2006-12-13 2013-10-15 Qualcomm Incorporated Method and apparatus for allocating network resources in a group communication system
EP1983701B1 (en) * 2007-04-17 2010-08-25 Alcatel Lucent Method and apparatus for reserving network resources for pseudo point-to-point connection
US8266286B2 (en) * 2007-06-05 2012-09-11 Cisco Technology, Inc. Dynamic key management server discovery
US20090070336A1 (en) * 2007-09-07 2009-03-12 Sap Ag Method and system for managing transmitted requests
US7856448B2 (en) * 2008-02-14 2010-12-21 International Business Machines Corporation Access control decision method and system
US8798579B2 (en) * 2008-09-30 2014-08-05 Xe2 Ltd. System and method for secure management of mobile user access to network resources
US8271635B2 (en) * 2009-06-17 2012-09-18 Microsoft Corporation Multi-tier, multi-state lookup
WO2011109404A2 (en) * 2010-03-01 2011-09-09 Ivy Corp. Automated communications system
US9729516B2 (en) * 2010-04-09 2017-08-08 Gemalto Sa Method of machine-to-machine communication
US8942191B2 (en) * 2010-05-03 2015-01-27 Mformation Software Technologies Llc Providing dynamic group subscriptions for M2M device communication
US20130252643A1 (en) * 2010-12-28 2013-09-26 Lg Electronics Inc. Method for transmitting and receiving idle-mode parameter update information, and apparatus therefor
WO2012106619A1 (en) * 2011-02-03 2012-08-09 Telcordia Technologies, Inc. System and method for group communications in 3gpp machine-to-machine networks
WO2012111952A2 (ko) * 2011-02-14 2012-08-23 엘지전자 주식회사 무선통신 시스템에서 파라미터 업데이트 정보를 전송 및 수신하는 방법 및 이를 위한 장치
CN102130773B (zh) * 2011-02-25 2012-12-19 华为技术有限公司 群组通信的方法和用于群组通信的装置
CN103297468B (zh) * 2012-02-29 2017-12-01 华为技术有限公司 针对群组资源的操作方法、群组服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083537A (zh) * 2006-05-31 2007-12-05 华为技术有限公司 一种实现设备管理的方法、装置和系统
WO2009002236A1 (en) * 2007-06-27 2008-12-31 Telefonaktiebolaget Lm Ericsson (Publ) A method and apparatus for enabling connectivity in a communication network
CN102244855A (zh) * 2010-05-10 2011-11-16 华为技术有限公司 一种基于位置的机器对机器通信方法、系统和装置
CN102136933A (zh) * 2010-09-30 2011-07-27 华为技术有限公司 设备管理方法、中间件及机器通信平台、设备和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2706729A4 *

Also Published As

Publication number Publication date
US9438601B2 (en) 2016-09-06
EP2706729A1 (en) 2014-03-12
US20140115169A1 (en) 2014-04-24
CN103297468B (zh) 2017-12-01
US20150074280A1 (en) 2015-03-12
US8918528B2 (en) 2014-12-23
EP2706729A4 (en) 2014-07-23
EP3151589A1 (en) 2017-04-05
CN103297468A (zh) 2013-09-11

Similar Documents

Publication Publication Date Title
WO2013127145A1 (zh) 针对群组资源的操作方法、群组服务器
KR101806257B1 (ko) 가입 통지를 구현하기 위한 방법 및 장치
CN108353094B (zh) 用于m2m服务层的跨资源订阅
KR102095436B1 (ko) 서비스 계층에서의 요청 처리
JP5805873B2 (ja) Ｍ２ｍデバイスサブスクリプションのための方法及び装置
KR20160082967A (ko) M2m 통신 시스템에서 구독 및 통지를 위한 방법 및 이를 위한 장치
WO2014067311A1 (zh) 资源订阅方法及装置
Aljohani et al. Real time face detection in ad hoc network of android smart devices
EP3227842A1 (en) Method for supporting negotiation service at a service layer
KR102500594B1 (ko) 통신 네트워크에서의 서비스 계층 메시지 템플릿들
WO2016054888A1 (zh) 一种创建订阅资源的方法和装置
WO2014079019A1 (zh) 一种机器通信中群组管理的方法和装置
WO2013056552A1 (zh) 业务数据处理的方法、装置和系统
EP3332513B1 (en) Service element host selection
WO2020009797A1 (en) Efficient resource representation exchange between service layers
WO2014067313A1 (zh) 终端外设的注销方法和装置
EP3148133B1 (en) Load control method and apparatus for notification messages
WO2014107956A1 (zh) 一种资源共享方法及装置
KR20180110456A (ko) oneM2M기반 서비스 연계를 위한 연동 시스템
JP2014209341A (ja) アンサンブルコンピューティング
Hudson Walkabout: an asynchronous messaging architecture for mobile devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12869697

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2012869697

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012869697

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE