WO2014079019A1 - 一种机器通信中群组管理的方法和装置 - Google Patents

一种机器通信中群组管理的方法和装置 Download PDF

Info

Publication number
WO2014079019A1
WO2014079019A1 PCT/CN2012/085062 CN2012085062W WO2014079019A1 WO 2014079019 A1 WO2014079019 A1 WO 2014079019A1 CN 2012085062 W CN2012085062 W CN 2012085062W WO 2014079019 A1 WO2014079019 A1 WO 2014079019A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
type
consistency
members
server
Prior art date
Application number
PCT/CN2012/085062
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
Priority to JP2015543229A priority Critical patent/JP6137649B2/ja
Priority to CN201810381077.6A priority patent/CN108769931B/zh
Priority to PCT/CN2012/085062 priority patent/WO2014079019A1/zh
Priority to EP12888718.9A priority patent/EP2925028B1/en
Priority to ES12888718.9T priority patent/ES2665585T3/es
Priority to EP17170554.4A priority patent/EP3297302B1/en
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201280002346.4A priority patent/CN104041086B/zh
Priority to KR1020157016227A priority patent/KR101711462B1/ko
Priority to AU2012395266A priority patent/AU2012395266B2/en
Publication of WO2014079019A1 publication Critical patent/WO2014079019A1/zh
Priority to US14/718,351 priority patent/US10244549B2/en
Priority to US16/297,372 priority patent/US10638496B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • 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/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present invention relates to the field of information technologies, and in particular, to a method and an apparatus for group management in machine communication. Background technique
  • Machine-to-Machine Communications is a networked application and service centered on machine intelligence interaction. It embeds wireless or wired communication modules and application processing logic inside the machine to realize user informationization requirements for monitoring, command scheduling, data collection and measurement.
  • various M2M devices such as various sensors, are directly connected to the M2M service platform through the M2M gateway. Thereby implementing various M2M services, such as power meter reading, intelligent transportation, and the like.
  • M2M services such as power meter reading, intelligent transportation, and the like.
  • data collected by the M2M device can be obtained, or the M2M device can be controlled and managed.
  • M2M devices There are many types of M2M devices, such as application type, access rights type, management object type, etc., which can group M2M devices.
  • the group has a group type, which is used to indicate the type of members in the group, if the member type in the group Consistently, the group type is this consistent type. If the member types in the group are inconsistent, the group type is mixed.
  • an M2M service often needs to perform grouping operations on a group of devices of the same type at the same time, and does not want other types of members to be included in the group, and the group server receives a request to create a group or update a group.
  • the type of the member in the group is checked, if the check fails, it will directly lead to the failure to create a group or update the group. Because the check fails, for example, the device to which the member belongs in the group may be in a sleep state and cannot be checked. Thus, the possibility of creating a group or updating a group is high, which severely restricts the flexibility of the user.
  • an embodiment of the present invention provides a group management in machine communication. Methods and devices to increase user flexibility in creating M2M groups.
  • an embodiment of the present invention provides a method for group management in a machine communication, including: receiving a group creation request sent by a requesting device, where the group creation request includes a group type requesting to create a group;
  • a group creation response containing a consistency check result is returned to the requesting device.
  • the method further includes: determining that a member type of one member in the group is inconsistent with the group type; deleting the member that is inconsistent with the group type from the group , or delete the group directly.
  • the attribute of the group includes a consistency policy, and determining, according to the consistency policy, that when a member type of one member in the group is inconsistent with the group type, Whether to delete the member that is inconsistent with the group type from the group, or whether to delete the created group.
  • the consistency between the member type of the member in the checking group and the group type includes: determining that the member in the group is unreachable; and subscribing to the service platform The online status of the unreachable member home device, when the online status changes, receiving a notification message sent by the service platform, or periodically polling the home device of the unreachable member until the unreachable After the member is reachable, the member type of the member is obtained, and the member type of the member is determined to be consistent with the group type.
  • the determining, by the checking group, the member type of the member in the checking group is consistent with the group type, the determining that the member of the group is a non-subgroup member, Determining the member type according to the member's uniform resource identifier URI; determining the member type, determining the consistency of the member type of the member with the group type.
  • the checking the member type of the member in the group The consistency with the group type specifically includes: determining that the sub-group member in the group does not complete its own consistency check; subscribing the status of the sub-group to the sub-group home device; receiving the sub-group The status notification determines the subgroup type according to the status notification, and determines the consistency of the type of the subgroup with the group type.
  • the group type is a non-hybrid type
  • the consistency of the member type of the member in the group with the group type is checked.
  • an embodiment of the present invention provides a method for group management in machine communication, including: sending a group creation request to a group server, where the group creation request includes a group type requesting to create a group;
  • the group creation response includes the result of the consistency check of the member type and the group type of the members in the group.
  • the method further includes: subscribing to a group server status of the group according to the group creation response.
  • an embodiment of the present invention provides a group server for machine communication, including: a receiving unit, configured to receive a group creation request sent by a requesting device, where the group creation request includes a group type that requests to create a group ;
  • a consistency checking unit configured to check consistency between a member type of a member in the group and the group type, and set a consistency check identifier of the group according to a consistency check result
  • a sending unit configured to return, to the requesting device, a group creation response including a consistency check result.
  • the method further includes: a policy unit, configured to delete, when the member type of one member in the group is inconsistent with the group type, A member that is inconsistent with the group type, or delete the group directly.
  • the attribute of the group includes a consistency policy
  • the policy unit further determines, according to the consistency policy, a member class of a member in the group. Whether the type is inconsistent with the group type, whether the member that is inconsistent with the group type is deleted from the group, or whether the created group is deleted.
  • the group server further includes a subscribing unit, configured to: when the member in the group is unreachable, subscribe the service platform to the online device of the unreachable member home device a state, when the online status changes, receiving a notification message sent by the service platform; the consistency checking unit determines that the member is reachable, acquires a member type of the member, and determines a member type of the member Consistency with the group type.
  • a subscribing unit configured to: when the member in the group is unreachable, subscribe the service platform to the online device of the unreachable member home device a state, when the online status changes, receiving a notification message sent by the service platform; the consistency checking unit determines that the member is reachable, acquires a member type of the member, and determines a member type of the member Consistency with the group type.
  • the consistency checking unit is specifically configured to: determine that a member of the group is a non-subgroup member, and determine the member according to a member's uniform resource identifier URI. Type; after determining the member type, determining the consistency of the member type of the member with the group type.
  • the group server further includes a subscribing unit, configured to: when determining that the subgroup members in the group have not completed their consistency check, to the subgroup
  • the group home device subscribes to the status of the sub-group, and receives a status notification of the sub-group; the consistency checking unit determines the sub-group type according to the status notification, and determines the type of the sub-group and The consistency of the group type.
  • an embodiment of the present invention provides a request device for machine communication, including:
  • a sending unit configured to send a group creation request to the group server, where the group creation request includes a group type that requests to create a group;
  • a receiving unit configured to receive a returned group creation response, where the group creation response includes a result of a consistency check of a member type and a group type of a member in the group.
  • the method further includes: a subscribing unit, configured to subscribe the group server to a status of the group according to the group creation response.
  • the consistency check identifier of the group is set, and the one-time identifier of the requesting device is notified in the group creation response, so that the group creation does not fail due to type checking, etc. Increased user flexibility in using M2M technology.
  • FIG. 1 is a system architecture diagram of group management according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for group management according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of another method for managing group groups according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of still another method for group management according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of still another method for group management according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of still another method for group management according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of still another method for group management according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a group server according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a request apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another group server according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another requesting apparatus according to an embodiment of the present invention.
  • the embodiment of the invention provides a system for managing M2M groups.
  • the M2M group management system includes a group server and a requesting device.
  • the group server is configured to receive a group creation request sent by the requesting device, where the group creation request includes a group type for requesting to create a group; and checking consistency of a member type of the member in the group with the group type And setting a consistency check identifier of the group according to the consistency check result; returning a group creation response including a consistency check result to the requesting device.
  • the requesting device is configured to send a group creation request to the group server, and receive the returned group creation response, where the group creation response includes a result of the consistency check of the member type and the group type of the members in the group.
  • the service platform, the M2M gateway, and the M2M device that can store and maintain the group can be used as a group server, and the created group belongs to the group server.
  • the requesting device may also request the device to establish a group in the group server for the service platform, the M2M gateway, and the M2M device.
  • An embodiment of the present invention provides a method for managing an M2M group. As shown in FIG. 2, the method includes the following steps:
  • the group server receives a group creation request sent by the requesting device, where the group creation request includes a group type that requests to create a group.
  • the group creation request includes a group type, and optionally, a group identifier or a group member.
  • the group server checks the consistency of the member type of the member in the group with the group type, and sets the consistency check identifier of the group according to the consistency check result.
  • URI Uniform Resource Identifier
  • the member that is inconsistent with the group type may be deleted from the group, or the created group may be directly deleted.
  • a consistency policy may be included in the attribute of the group to determine whether the member that is inconsistent with the group type is deleted from the group when the member type of one member in the group is inconsistent with the group type. , or, delete the created group.
  • the service platform registered by the device to which the unreachable member is registered may subscribe to the online status of the unreachable member, and when the device to which the unreachable member belongs is online, the registered service is The platform sends a notification message to the subscriber.
  • the device is periodically polled to the unreachable member home device. After the device is reachable, the member type is obtained and the consistency with the group type is determined.
  • the member type of the group member is obtained from the cached record, and the member type of the member is determined to be consistent with the group type. After the subsequent members are reachable, the consistency of this member with the group type can be further determined.
  • the group server may first create the group, and set the consistency check identifier of the group according to the consistency check result. If all members are reachable and complete the check, the consistency check flag can be set to "check completed”. If some members do not complete the consistency check due to unreachable reasons, etc., it can be set to "Check is not completed,".
  • Unreachable members can be recorded first, and then reach the consistency.
  • the group server returns, to the requesting device, a group creation interface that includes a consistency check result.
  • the group server may include a "check incomplete" flag in the group creation response for notifying the M2M requesting device. If the group consistency check is successful and created successfully, the success flag can be included in the group creation response.
  • the embodiment of the present invention further provides a method for managing an M2M group. As shown in FIG. 3, the method includes the following steps:
  • the requesting device sends a group creation request to the group server, where the group creation request includes a group type that requests to create a group.
  • the group creation request includes a group type, and optionally, a group identifier or a group member.
  • the group server may include a "check incomplete" flag in the group creation response to notify the M2M requesting device. If the group consistency check is successful and created successfully, the success flag can be included in the group creation response.
  • the requesting device may subscribe to the status of the group according to the received group creation response. After the group status is changed on the group server, for example, after the consistency check is completed, the requesting device can be notified.
  • an embodiment of the present invention further provides a method for group management.
  • a group 1 needs to be created, and the members included in the group 1 have sub-group members, such as sub-group 2 and sub-group 3, and device members, such as device 4 and device 5.
  • Specific steps of the specific process of the method include:
  • the requesting device sends a group creation request message, requesting to create group 1.
  • the requesting device may be an M2M device, an M2M gateway, or a service platform
  • the group server may be a Service Capability Layer (SCL) device to which the group belongs
  • the service platform may be an SCL (SCL, Service Capability Layer) of the M2M. )device.
  • SCL Service Capability Layer
  • the group 1 requested to be created belongs to the SCL device 1, that is, the group server 1, the subgroup 2, and the subgroup 3 are respectively attributed to the SCL devices 2 and 3, that is, the group servers 2 and 3.
  • the two device member devices 4 and 5 of group 1 are also attributed to the SCL device 1.
  • the group creation request includes the group type of the group that is requested to be created, and this embodiment does not have this type. For non-hybrid classes, such as application classes, it indicates that all group members should be of a consistent type.
  • the group server 1 checks the consistency of the group member type and the group type after receiving the group creation request.
  • the group server After receiving the group creation request, the group server determines whether the consistency needs to be checked according to the group type. If the group type is a hybrid type, it is not necessary to check the consistency. This embodiment assumes that it is necessary to check the consistency.
  • the group server gets the member types of all members in the group member list.
  • the member of the local group can directly obtain the type of the member for comparison. If the group includes the remote group member, the group server needs to further obtain the member type of the member from the device to which the remote member belongs.
  • Whether the group includes the remote group member can be determined by the Uniform Resource Identifier (URI) of the group.
  • URI Uniform Resource Identifier
  • the group server 1, 2, 3, and the domain name are separated.
  • the group 1 URI is: "coap://gl .example.com/groups/grou l "
  • the subgroup 2 URI is: " coa : //d 1. example . com/ groups/ group2 "
  • the group 3 URI is:
  • two device members of group 1 and device 4 and device 5 are local members, and the member types can be directly obtained, and the type consistency is determined.
  • Subgroup 2 and subgroup 3 are assumed to be remote members, and it is assumed here that subgroup 2 and subgroup 3 have not passed the membership type consistency check because the group server 1 belongs to the group to which subgroups 2 and 3 belong respectively.
  • the access response to the access request is not received within the set duration.
  • the access request here can be the type attribute of the access group.
  • Group Server 1 Create a group 1 and set a property of the group, the consistency check identifier to "check is not completed", because subgroup 2 and subgroup 3 have not completed the consistency check.
  • the group server 1 returns a group creation response to the requesting device.
  • the identity of the group creation response can carry "consistency check is not completed".
  • the group server 1 subscribes to the service platform for the online status of the unreachable members.
  • the group server 1 can send a subscription request to the service platform for the unreachable member.
  • the group server 1 subscribes to the online status of the group server 2 and the group server 3 to which the subgroup 2 and the subgroup 3 belong. Since the group server 2 and the group server 3 have been registered on the service platform, the platform can return a subscription success response after receiving the subscription request.
  • the requesting device may send a subscription request to the group server 1 according to the "check uncompleted" identifier carried in the response, requesting to subscribe to the state of the group 1.
  • Group Server 1 can return a successful response to the subscription.
  • the online status registered on the service platform changes, and the service platform sends a notification message to the subscriber group server 1 to notify that the group server 3 is reachable.
  • the group server 1 After receiving the notification message, the group server 1 sends an access request to the group server 3, and requests to obtain the group attribute of the subgroup 3.
  • the group server 1 receives the access response returned by the group server 3, and includes the group type of the subgroup 3.
  • Group server 1 Check whether the group type of the subgroup 3 is the same as the group type of the group 1. If the inconsistency is shown in FIG. 4, the group server 1 deletes the created group 1.
  • the group server sends a notification message.
  • the group server 1 can notify the requesting device that "because of the member 'subgroup 3, the type is inconsistent, the group 1 has been deleted".
  • FIG. 5 shows another method for group group management provided by an embodiment of the present invention. As shown in Figure 4 The embodiment is similar. In this embodiment, as an example, group 1 is also created. The members included in group 1 have sub-group members, such as sub-group 2 and sub-group 3, and device members, such as device 4 and Device 5. Specific steps of the specific process of the method include:
  • the group server 1 receives the group creation request, creates the group, and returns a response. And subscribed to the business platform for the online status of group servers 2 and 3. After the group server 3 is reachable, the group type of the subgroup 3 is obtained.
  • the group server 1 checks whether the group type of the subgroup 3 is the same as the group type of the group 1. The assumptions shown in FIG. 5 are the same, but the group server 2 is unreachable, and the group of the subgroup 2 is unreachable. The type is not yet available, so the consistency check ID for group 1 is still "not completed".
  • the service platform After the group server 2 is reachable, the online status of the resource registered on the service platform changes, and the service platform sends a notification message to the subscriber group server 1 to notify that the group server 2 is reachable.
  • the group server 1 After receiving the notification message, the group server 1 sends an access request to the group server 2, and requests to obtain the group attribute of the subgroup 2.
  • the group server 1 receives the access response returned by the group server 2, and includes the group type of the subgroup 2.
  • the group server 1 checks whether the group type of the subgroup 2 is the same as the group type of the group 1. 4, as shown in FIG. 5, all the members of the group 1 have checked the consistency. Therefore, the consistency check flag of group 1 is set to "completed".
  • the member types of all members are the same as the group type of the group.
  • the group server sends a notification message.
  • the group server 1 can notify the requesting device group 1 "the consistency check has been completed".
  • FIG. 6 is a method for managing another population group according to an embodiment of the present invention. Similar to the embodiment shown in FIG. 4, in this embodiment, as an example, group 1 is also created, and members included in group 1 have sub-group members, such as sub-group 2 and sub-group 3, and device members. , such as device 4 and device 5. Specific steps of the specific process of the method include:
  • the group server 1 receives the group creation request, creates the group, and returns a response. And subscribed to the business platform for the online status of group servers 2 and 3. After the group server 3 is reachable, the group type of the subgroup 3 is obtained.
  • the group server 1 checks whether the group type of the subgroup 3 is the same as the group type of the group 1. Assume that the inconsistency is shown in FIG. 6, which is different from that shown in FIG. Strategy" to determine how to handle. For example, you can delete the created group directly, as shown in Figure 4. You can also remove members of this type that are inconsistent from the created group, for example, delete subgroup 3 from group 1. Since the group server 2 is unreachable after deletion, the group type of the subgroup 2 cannot be obtained, so the consistency check of the group 1 is also "not completed".
  • the consistency policy can be configured on the group server, or can be carried in the group creation request by the requesting device. After the group server receives the group, the "consistency policy" is applied to the group created by the request. If the consistency policy indicates "delete group”, the group server deletes the group after determining that the group has a member whose type does not match the group type. If the consistency policy indicates "delete member”, the group server determines that the type of the member of the group is inconsistent with the group type, and removes the inconsistent member from the group.
  • the group server sends a notification message.
  • the requesting device subscribes to the status of the group 1, and the group server 1 can notify the requesting device that "one member of group 1" subgroup 3, the type is inconsistent, has been deleted from the group, and can also notify that the consistency check is still "not carry out” .
  • the service platform After the group server 2 is reachable, the online status of the resource registered on the service platform changes, and the service platform sends a notification message to the subscriber group server 1 to notify that the group server 2 is reachable.
  • the group server 1 After receiving the notification message, the group server 1 sends an access request to the group server 2, Find the group attribute of subgroup 2.
  • the group server 1 receives the access response returned by the group server 2, where the group type of the subgroup 2 is included.
  • the group server 1 checks whether the group type of the subgroup 2 is the same as the group type of the group 1. 4 is consistent with the group shown in FIG. 5, and all members of the group 1 have checked the consistency. Therefore, the consistency check flag of group 1 is set to "completed". Here, the member types of all members are the same as the group type of the group.
  • the group server sends a notification message.
  • the requesting device subscribes to the status of the group 1, and the group server 1 can notify the requesting device to check "completed” at one time.
  • FIG. 7 shows another method for managing group groups according to an embodiment of the present invention.
  • the type of the subgroup also needs to wait for consistency confirmation because the member is unreachable.
  • group 1 needs to be created, and members included in group 1 have sub-group members, such as sub-group 2 and sub-group 3, and device members, such as device 4 and devices. 5.
  • Specific steps of the specific process of the method include:
  • the requesting device sends a group creation request message, requesting to create group 1.
  • the requesting device may be an M2M device, an M2M gateway, or a service platform
  • the group server may be a Service Capability Layer (SCL) device to which the group belongs
  • the service platform may be an SCL (SCL, Service Capability Layer) of the M2M. )device.
  • SCL Service Capability Layer
  • the group 1 requested to be created belongs to the SCL device 1, that is, the group server 1, the subgroup 2, and the subgroup 3 are respectively attributed to the SCL devices 2 and 3, that is, the group servers 2 and 3.
  • the two device member devices 4 and 5 of group 1 are also attributed to the SCL device 1.
  • the group creation request includes the group type of the group that is requested to be created, and this embodiment does not have this type. For non-hybrid classes, such as application classes, it indicates that all group members should be of a consistent type.
  • the group server 1 After receiving the group creation request, the check determines the consistency of the group member type and the group type.
  • the group server After receiving the group creation request, the group server determines whether the consistency needs to be checked according to the group type. If the group type is a hybrid type, it is not necessary to check the consistency. This embodiment assumes that it is necessary to check the consistency.
  • the group server gets the member types of all members in the group member list.
  • the member of the local group can directly obtain the type of the member for comparison. If the group includes the remote group member, the group server needs to further obtain the member type of the member from the SCL device to which the remote member belongs.
  • the two device member devices 4 and 5 of the group 1 are local members, and the member types can be directly obtained, and the consistency of the types is determined.
  • Subgroup 2 and subgroup 3 are assumed to be remote members, where subgroup 2 and subgroup 3 have not passed the membership type consistency check.
  • the group server 1 sends an access request to the group server 2 and the group server 3 to which the subgroups 2 and 3 belong, respectively, requesting to acquire the type attribute of the subgroup, and then separately collecting To the access response returned by the group server 2 and the group server 3, the response includes parameters indicating that the subgroup 2 and the subgroup 3 are consistently "incomplete". Possible reasons for subgroups not completing verification include that some members of the subgroup are currently unreachable.
  • Group Server 1 Create a group 1 and set the consistency check flag of the group to "not completed” because subgroup 2 and subgroup 3 have not completed the consistency check.
  • the group server 1 returns a group creation response to the requesting device.
  • the one-time identification attribute of the group can be carried in the group creation response. In this embodiment, it is "not redundant".
  • the group server 1 subscribes to the group servers 2 and 3 to subscribe to the status of the subgroup that has not completed the consistency check.
  • the group server 1 may belong to the group to which the subgroup belongs to the subgroup that has not completed the consistency check.
  • the server sends a subscription request.
  • the group server 1 subscribes the status of the subgroup 2 and the subgroup 3 to the group server 2 and the group server 3, respectively.
  • the requesting device may send a subscription request to the group server 1 according to the consistency check "uncompleted" identifier carried in the response, requesting the status of the group 1 to be subscribed, and the status of the group 1 is changed.
  • the group server 1 can notify the requesting device.
  • the group server 1 accepts the subscription, it can return a successful response.
  • the group server 3 can process according to the "consistency policy" of the sub-group 3, where there is no sub-group 3 contains members of inconsistent type, and "consistency policy” is "delete members when inconsistent”. Then the group server 3 deletes the inconsistent members in the subgroup 3. Sub-group after deletion 3 - The check mark is "Completed”. Since the group server 1 subscribes to the status change of the subgroup 3, the group server 3 sends a notification message to the subscriber group server 1, notifying that "subgroup 3 - the check of the consistency has been completed".
  • the group server 1 checks whether the group type of the subgroup 3 is the same as the group type of the group 1. This embodiment is set to be inconsistent, and the "consistency policy" of the group 1 is "disappeared when inconsistent”. Member " , then delete subgroup 3 from group 1. After the deletion, the consistency check of the group 1 has not been completed, so the consistency check of the group 1 has not been completed.
  • the group server 2 can process according to the "consistency policy" of the sub-group 2, where there is no sub-group 2 Contains members of inconsistent type, and "consistency policy" is "delete group when inconsistent”. Then group server 2 deletes subgroup 2 directly. Since the group server 1 subscribes to the status change of the subgroup 2, the group server 2 sends a notification message to the subscriber group server 1 notifying that "subgroup 2 has been deleted".
  • the group server 1 After receiving the notification that "Subgroup 2 has been deleted", the group server 1 deletes from the group 1. In addition to subgroup 2. All members of group 1 have checked for consistency, so set the consistency check ID for group 1 to "Completed". Here, the member types of all members are the same as the group type of the group.
  • the group server sends a notification message.
  • FIG. 8 is a schematic diagram of a group server for machine communication according to an embodiment of the present invention, including:
  • the receiving unit is configured to receive a group creation request sent by the requesting apparatus, where the group creation request includes a group type that requests to create a group.
  • the consistency checking unit is configured to check consistency between a member type of a member in the group and the group type, and set a consistency check identifier of the group according to a consistency check result.
  • the sending unit is configured to return, to the requesting device, a group creation response that includes a consistency check result.
  • the group server may further include: 804, a policy unit, configured to delete the group type from the group when determining that a member type of one member in the group is inconsistent with the group type Inconsistent members, or delete the group directly.
  • a policy unit configured to delete the group type from the group when determining that a member type of one member in the group is inconsistent with the group type Inconsistent members, or delete the group directly.
  • the attribute of the group includes a consistency policy
  • the policy unit further determines, according to the consistency policy, whether the group type of one member in the group is inconsistent with the group type.
  • the member that is inconsistent with the group type is deleted from the group, or whether the created group is deleted.
  • the group server further includes: 805, a subscribing unit, configured to: when the member in the group is unreachable, subscribe to an online status of the unreachable member home device to the service platform, where the online status is Receiving, by the service platform, a notification message sent by the service platform; the consistency checking unit determines that the member is reachable, acquires a member type of the member, and determines a member type of the member and the group type consistency.
  • a subscribing unit configured to: when the member in the group is unreachable, subscribe to an online status of the unreachable member home device to the service platform, where the online status is Receiving, by the service platform, a notification message sent by the service platform; the consistency checking unit determines that the member is reachable, acquires a member type of the member, and determines a member type of the member and the group type consistency.
  • the consistency checking unit is specifically configured to: determine that the members of the group are non-subgroups The member determines the member type according to the member's uniform resource identifier URI; after determining the member type, determining the consistency of the member type of the member with the group type.
  • the group server further includes a subscribing unit, configured to subscribe the subgroup home device to the subgroup home device when determining that the subgroup member in the group does not complete its own consistency check. a status, and receiving a status notification of the sub-group; the consistency checking unit determines the sub-group type according to the status notification, and determines the consistency of the type of the sub-group with the group type.
  • FIG. 9 is a schematic diagram of a request device for machine communication according to an embodiment of the present invention, including:
  • the sending unit is configured to send a group creation request to the group server, where the group creation request includes a group type that requests to create a group.
  • the receiving unit is configured to receive a returned group creation response, where the group creation response includes a result of a consistency check of a member type and a group type of a member in the group.
  • the method further includes: 903, a subscription unit, configured to subscribe to the group server for the status of the group according to the group creation response.
  • FIG. 10 is a schematic diagram showing another structure of a group server according to an embodiment of the present invention.
  • the program code for executing the solution of the present invention is stored in a memory and controlled by a processor.
  • the group server includes a bus, a processor (1001), a memory (1002), and a communication interface (1003).
  • the bus can include a path to transfer information between various components of the computer.
  • the processor may be a general purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • One or more memories included in the computer system which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or Other types of dynamic storage devices that store information and instructions may also be disk storage. These memories are routed through the bus The processors are connected.
  • any device such as transceiver can be used to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Network
  • a memory such as RAM, stores an operating system and a program for executing the inventive arrangements.
  • the operating system is a program that controls the running of other programs and manages system resources.
  • the program code for carrying out the inventive arrangement is stored in a memory and controlled by the processor for execution.
  • a program stored in the memory is used by the instruction processor to perform a method of group management in machine communication, including:
  • a group creation response containing a consistency check result is returned to the requesting device.
  • the method further includes: determining that a member type of one member in the group is inconsistent with the group type; deleting the member that is inconsistent with the group type from the group, or deleting the group directly group.
  • the attribute of the group includes a consistency policy, and determining, according to the consistency policy, whether the member type of one member in the group is inconsistent with the group type, and whether the group is deleted from the group. A member that is inconsistent with the group type, or whether the created group is deleted.
  • the consistency between the member type of the member in the check group and the group type includes: determining that the member in the group is unreachable; and subscribing to the service platform the online status of the unreachable member home device Receiving, by the service platform, a notification message sent by the service platform, or performing periodic polling on the home device of the unreachable member until the unreachable member is reachable; determining that the member is reachable After that, the member type of the member is obtained, and the member type of the member is determined to be consistent with the group type.
  • the consistency between the member type of the member in the check group and the group type includes: determining that the member of the group is a non-subgroup member, and determining, according to the member's uniform resource identifier URI The member type; after determining the member type, determining the consistency of the member type of the member with the group type.
  • the consistency between the member type of the member in the check group and the group type includes: determining that the sub-group member in the group does not complete its own consistency check;
  • the device subscribes to the status of the sub-group; receives a status notification of the sub-group, determines the sub-group type according to the status notification, and determines consistency between the type of the sub-group and the group type.
  • FIG. 11 is a schematic diagram showing another structure of a requesting apparatus according to an embodiment of the present invention.
  • the general computer system structure is used, and the program code for executing the solution of the present invention is stored in a memory and controlled by a processor.
  • the group server includes a bus, a processor (1101), a memory (1102), and a communication interface (1103).
  • the bus can include a path to transfer information between various components of the computer.
  • the processor can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the inventive program.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • One or more memories included in the computer system which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or Other types of dynamic storage devices that store information and instructions may also be disk storage. These memories are connected to the processor via a bus.
  • any device such as transceiver can be used to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Network
  • a memory such as RAM, stores an operating system and a program for executing the inventive arrangements.
  • the operating system is a program that controls the running of other programs and manages system resources.
  • the program code for carrying out the inventive arrangement is stored in a memory and controlled by the processor for execution.
  • a program stored in the memory is used by the instruction processor to perform a method of group management in machine communication, including:
  • the group creation request including a group type requesting to create a group
  • the group creation response includes the result of the consistency check of the member type and the group type of the members in the group.
  • the method further includes: subscribing to the group server the status of the group according to the group creation response.
  • the various embodiments in the present specification are described in a progressive manner, and the same similar parts between the various embodiments may be referred to each other, and each embodiment focuses on different embodiments from other embodiments.
  • the description is relatively simple, and the execution process of each unit specific function can be referred to the description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located in one place. , or it can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)
  • Selective Calling Equipment (AREA)

Abstract

本发明提供了一种机器通信中群组管理的方法及装置，以便提高用户创建使用M2M群组的灵活性。该机器通信中群组管理的方法包括：接收请求装置发送的群组创建请求，所述群组创建请求包括请求创建群组的群组类型；检查群组中成员的成员类型与所述群组类型的一致性，根据一致性检查结果设置所述群组的一致性检查标识；向所述请求装置返回包含一致性检查结果的群组创建响应。通过设置群组的一致性检查标识，并在群组创建响应中通知请求装置所述一次性标识，使得群组的创建不会因为类型检查等而失败，极大提高了用户使用M2M技术的灵活性。

Description

一种机器通信中群组管理的方法和装置 技术领域 本发明涉及信息技术领域， 尤其涉及一种机器通信中群组管理的方法及装 置。 背景技术
机器通信 ( Machine-to-Machine Communications, M2M )是一种以机器智能 交互为核心的、 网络化的应用与服务。 它通过在机器内部嵌入无线或有线通信 模块以及应用处理逻辑， 实现用户对监控、 指挥调度、 数据釆集和测量等方面 的信息化需求。 M2M系统中，各种 M2M设备，如各种传感器，直接经过 M2M 网关接入到 M2M业务平台。 从而实现各种 M2M业务， 例如电力抄表、 智能 交通等。 通过 M2M业务平台所提供的业务能力， 可以获取 M2M设备釆集的 数据， 或对 M2M设备进行控制和管理。
M2M设备有多种类型， 例如应用型、 访问权限型、 管理对象型等， 可以 对 M2M设备分组， 群组有一个群组类型， 用于表示群组内成员的类型， 如果 群组内成员类型一致， 群组类型就是这个一致的类型， 如果群组内成员类型不 一致， 群组类型就是混合型。
现有技术中， M2M业务往往需要同时对一组相同类型的设备进行群组化 操作， 而不希望有其他类型成员包含在群组中， 群组服务器接收到创建群组请 求或更新群组请求时， 对群组中成员的类型做相应的检查， 如果检查失败， 将 直接导致创建群组或更新群组失败。 由于导致检查失败的情况很多， 例如群组 中成员归属的设备可能处于休眠状态而无法检查。 从而创建群组或更新群组失 败的可能性很高， 严重制约了用户使用的灵活性。
发明内容
为克服现有技术的缺陷， 本发明实施例提供了一种机器通信中群组管理的 方法及装置， 以便提高用户创建使用 M2M群组的灵活性。
第一方面， 本发明实施例提供一种机器通信中群组管理的方法， 包括： 接收请求装置发送的群组创建请求， 所述群组创建请求包括请求创建群组 的群组类型；
检查群组中成员的成员类型与所述群组类型的一致性， 根据一致性检查结 果设置所述群组的一致性检查标识；
向所述请求装置返回包含一致性检查结果的群组创建响应。
在第一方面的第一种可能的实现方式中， 还包括： 确定群组中一个成员的 成员类型与所述群组类型不一致； 从所述群组中删除所述与群组类型不一致的 成员， 或者直接删除所述群组。
在第一方面的第二种可能的实现方式中， 所述群组的属性包括一致性策 略； 根据所述一致性策略确定当群组中一个成员的成员类型与所述群组类型不 一致时， 是否从所述群组中删除所述与群组类型不一致的成员， 或者， 是否删 除所述已创建的群组。
在第一方面的第三种可能的实现方式中， 所述检查群组中成员的成员类型 与所述群组类型的一致性具体包括： 确定所述群组中成员不可达； 向业务平台 订阅所述不可达成员归属设备的在线状态， 当所述在线状态改变时， 接收所述 业务平台发送的通知消息， 或者对所述不可达成员的归属设备进行周期性轮 询， 直到所述不可达成员可达； 确定所述成员可达后， 获取所述成员的成员类 型， 并确定所述成员的成员类型与所述群组类型的一致性。
在第一方面的第四种可能的实现方式中， 所述检查群组中成员的成员类型 与所述群组类型的一致性具体包括： 确定所述群组的成员为非子群组成员， 根 据成员的统一资源标识符 URI确定所述成员类型； 确定所述成员类型后， 确定 所述成员的成员类型与所述群组类型的一致性。
在第一方面的第五种可能的实现方式中， 所述检查群组中成员的成员类型 与所述群组类型的一致性具体包括： 确定所述群组中的子群组成员未完成自身 的一致性检查； 向子群组归属设备订阅所述子群组的状态； 接收子群组的状态 通知， 根据所述状态通知确定所述子群组类型， 并确定所述子群组的类型与所 述群组类型的一致性。
在第一方面的第六种可能的实现方式中， 当所述群组类型为非混合型时， 检查群组中成员的成员类型与所述群组类型的一致性。
第二方面， 本发明实施例提供一种机器通信中群组管理的方法， 包括： 向群组服务器发送群组创建请求， 所述群组创建请求包括请求创建群组的 群组类型；
接收返回的群组创建响应， 所述群组创建响应中包含群组中成员的成员类 型与群组类型的一致性检查的结果。
在第二方面的第一种可能的实现方式中，还包括：根据所述群组创建响应， 向群组服务器订阅所述群组的状态。
第三方面， 本发明实施例提供一种机器通信的群组服务器， 包括： 接收单元， 用于接收请求装置发送的群组创建请求， 所述群组创建请求包 括请求创建群组的群组类型；
一致性检查单元， 用于检查群组中成员的成员类型与所述群组类型的一致 性 , 根据一致性检查结果设置所述群组的一致性检查标识；
发送单元， 用于向所述请求装置返回包含一致性检查结果的群组创建响 应。
在第三方面的第一种可能的实现方式中， 还包括： 策略单元， 用于当确定 群组中一个成员的成员类型与所述群组类型不一致时， 从所述群组中删除所述 与群组类型不一致的成员， 或者直接删除所述群组。
在第三方面的第二种可能的实现方式中， 所述群组的属性包括一致性策 略， 所述策略单元进一步根据所述一致性策略确定当群组中一个成员的成员类 型与所述群组类型不一致时， 是否从所述群组中删除所述与群组类型不一致的 成员， 或者， 是否删除所述已创建的群组。
在第三方面的第三种可能的实现方式中， 所述群组服务器还包括订阅单 元， 用于确定所述群组中成员不可达时， 向业务平台订阅所述不可达成员归属 设备的在线状态， 当所述在线状态改变时，接收所述业务平台发送的通知消息； 所述一致性检查单元确定所述成员可达后， 获取所述成员的成员类型， 并确定 所述成员的成员类型与所述群组类型的一致性。
在第三方面的第四种可能的实现方式中， 所述一致性检查单元具体用于： 确定所述群组的成员为非子群组成员，根据成员的统一资源标识符 URI确定所 述成员类型； 确定所述成员类型后， 确定所述成员的成员类型与所述群组类型 的一致性。
在第三方面的第五种可能的实现方式中， 所述群组服务器还包括订阅单 元， 用于当确定所述群组中的子群组成员未完成自身的一致性检查时， 向子群 组归属设备订阅所述子群组的状态， 并接收子群组的状态通知； 所述一致性检 查单元根据所述状态通知确定所述子群组类型， 并确定所述子群组的类型与所 述群组类型的一致性。
第四方面， 本发明实施例提供一种机器通信的请求装置， 包括：
发送单元， 用于向群组服务器发送群组创建请求， 所述群组创建请求包括 请求创建群组的群组类型；
接收单元， 用于接收返回的群组创建响应， 所述群组创建响应中包含群组 中成员的成员类型与群组类型的一致性检查的结果。
在第四方面的第一种可能的实现方式中， 还包括订阅单元， 用于根据所述 群组创建响应， 向群组服务器订阅所述群组的状态。
本发明实施例通过设置群组的一致性检查标识， 并在群组创建响应中通知 请求装置所述一次性标识， 使得群组的创建不会因为类型检查等而失败， 极大 提高了用户使用 M2M技术的灵活性。 附图说明
为了更清楚地说明本发明实施例的技术方案， 下面将对实施例或现有技术 描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅 是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动 的前提下， 还可以根据这些附图获取其他的附图。
图 1为本发明实施例提供的一种群组管理的系统架构图；
图 2为本发明实施例提供的一种群组管理的方法流程图；
图 3为本发明实施例提供的另一种群组管理的方法流程图；
图 4为本发明实施例提供的又一种群组管理的方法流程图；
图 5为本发明实施例提供的又一种群组管理的方法流程图；
图 6为本发明实施例提供的又一种群组管理的方法流程图；
图 7为本发明实施例提供的又一种群组管理的方法流程图；
图 8为本发明实施例提供的一种群组服务器的结构示意图；
图 9为本发明实施例提供的一种请求装置的结构示意图；
图 10为本发明实施例提供的另一种群组服务器的结构示意图；
图 11为本发明实施例提供的另一种请求装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明的一部分实施例， 而不 是全部实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创造 性劳动前提下获取的所有其他实施例， 都属于本发明保护的范围。 本发明实施例提供一种 M2M群组管理的系统，如图 1所示， M2M群组管 理系统包括群组服务器和请求装置。 所述群组服务器用于接收请求装置发送的群组创建请求， 所述群组创建请 求包括请求创建群组的群组类型； 检查群组中成员的成员类型与所述群组类型 的一致性， 根据一致性检查结果设置所述群组的一致性检查标识； 向所述请求 装置返回包含一致性检查结果的群组创建响应。
所述请求装置用于向群组服务器发送群组创建请求， 接收返回的群组创建 响应， 所述群组创建响应中包含群组中成员的成员类型与群组类型的一致性检 查的结果。
本发明实施例中， 可以存储和维护群组的业务平台、 M2M网关、 M2M设 备都可以作为群组服务器， 所创建的群组归属于此群组服务器。 请求装置也可 以为业务平台、 M2M网关、 M2M设备， 请求装置请求建立一个群组在群组服 务器中。 本发明实施例提供一种 M2M群组管理的方法， 如图 2所示， 包括下面的 步骤：
201、 群组服务器接收请求装置发送的群组创建请求， 所述群组创建请求 包括请求创建群组的群组类型；
群组创建请求中包括群组类型， 可选的， 还可以包括群组标识或群组成员 等信息。
202、 群组服务器检查群组中成员的成员类型与所述群组类型的一致性， 并根据一致性检查结果设置所述群组的一致性检查标识；
对于群组中包含的子群组成员， 可以获取子群组的 "群组类型" 属性； 对 于群组成员中的非子群组成员， 可以根据成员的统一资源标识符 （Uniform Resource Identifier, URI ) 来确定所述成员类型， 例如， 一个成员的 URI为：
"coap : //ggl. example, com/appl icat ions/tempi" , 其中, "applications" 就 说明此成员类型为 "应用" 型。 确定成员类型后， 再确定与所述群组类型的一 致性。 当群组类型为混合型时， 可以不用检查群组中成员的成员类型与所述群组 类型的一致性。
优选的， 当确定群组中一个成员的成员类型与所述群组类型不一致后， 可 以从所述群组中删除此与群组类型不一致的成员， 也可以直接删除所述已创建 的群组。 进一步， 可以在群组的属性中包括一致性策略， 用于确定当群组中一 个成员的成员类型与所述群组类型不一致时， 是否从所述群组中删除与群组类 型不一致的成员， 或者， 是否删除所述已创建的群组。
可选地， 当确定所述群组中成员不可达后， 可以向不可达成员归属的设备 所注册的业务平台订阅不可达成员的在线状态， 当不可达成员归属的设备在线 后， 注册的业务平台会向订阅者发送通知消息； 或者， 直接对不可达成员归属 设备周期性轮询， 直到设备可达后， 获取成员的成员类型， 确定与群组类型的 一致性。
可选的， 当群组成员不可达时， 也可以先从緩存的记录中获取所述群组成 员的成员类型， 确定所述成员的成员类型与所述群组类型的一致性。 后续成员 可达后， 可以再进一步确定此成员与群组类型的一致性。
群组服务器可以先创建所述群组， 根据一致性检查结果设置所述群组的一 致性检查标识。如果所有成员都可达并完成检查，一致性检查标识可设置为 "检 查完成" ， 如果部分成员因为不可达等原因未完成一致性检查， 可设置为 "检 查未完成，， 。
不可达的成员可以先记录下来， 可达后再确定一致性。
203、 群组服务器向所述请求装置返回包含一致性检查结果的的群组创建 口向应。
如果一致性检查未完成， 群组服务器可在群组创建响应中包含一 "检查未 完成"标识， 用于通知 M2M请求装置。 如果群组一致性检查成功并创建成功， 可在群组创建响应中包括成功标识。 本发明实施例还提供一种 M2M群组管理的方法， 如图 3所示， 包括下面 的步骤：
301 , 请求装置向群组服务器发送群组创建请求， 所述群组创建请求包括 请求创建群组的群组类型；
群组创建请求中包括群组类型， 可选的， 还可以包括群组标识或群组成员 等信息。
302 , 接收返回的群组创建响应， 所述群组创建响应中包含群组中成员的 成员类型与群组类型的一致性检查的结果。
如果一致性检查未完成， 群组服务器可在群组创建响应中包含一 "检查未 完成"标识， 用于通知 M2M请求装置。 如果群组一致性检查成功并创建成功， 可在群组创建响应中包括成功标识。
请求装置可以根据收到的群组创建响应， 订阅所述群组的状态。 群组服务 器上所述群组状态改变后， 例如完成一致性检查后， 可以通知所述请求装置。 如图 4所示， 本发明实施例还提供一种群组管理的方法。 在本实施例中， 作为举例， 需创建群组 1 , 群组 1包括的成员有子群组成员， 如子群组 2和子 群组 3 , 和设备成员， 如设备 4和设备 5。 该方法具体流程具体步骤包括：
401、 请求装置发送群组创建请求消息， 请求创建群组 1。
这里， 请求装置可以是 M2M设备、 M2M网关或业务平台， 群组服务器可 以为群组所归属的业务能力层 （Service Capability Layer, SCL )设备， 业务平 台可以是 M2M的 SCL ( SCL, Service Capability Layer )设备。 例如， 本实施例 中， 请求创建的群组 1归属于 SCL设备 1 , 即群组服务器 1 , 子群组 2和子群 组 3分别归属于 SCL设备 2和 3 , 即群组服务器 2和 3。 群组 1的两个设备成 员设备 4和设备 5也归属于 SCL设备 1。
群组创建请求中包括了请求创建的群组的群组类型， 本实施例 H没此类型 为非混合类， 例如应用类， 表明所有群组成员应是一致的类型。
402、 群组服务器 1 收到群组创建请求后， 检查群组成员类型与群组类型 的一致性。
群组服务器收到群组创建请求后， 根据群组类型确定是否需要检查一致 性， 如果群组类型是混合类型， 则不必检查一致性。 本实施例假设需要检查一 致性。
群组服务器获取群组成员列表中的所有成员的成员类型。 本地群组成员可 以直接获取成员的类型进行比较， 若群组包含远程群组成员， 群组服务器需要 进一步向远程成员所归属的设备获取所述成员的成员类型。
群组是否包含远程群组成员可以通过群组的统一资源标识符 （ Uniform Resource Identifier, URI )来确定， 例如， 本实施例中， 4叚设群组服务器 1、 2、 3 々域名分另 ll为： gl .example.com、 dl .example.com、 d2.example.com。 而群组 1 URI为： "coap://gl .example.com/groups/grou l " , 子群组 2 URI为： " coa ： //d 1. example . com/ groups/ group2 " ， 子 群 组 3 URI 为 ：
" coa ://d2. example . com/groups/group3 " , 则可见群组 1和子群组 2、 3分另 归 属于不同的设备， 子群组 2、 3为群组 1的远程群组成员。
本实施例中， 4叚设群组 1的两个设备成员， 设备 4和设备 5 , 为本地成员， 可直接获取成员类型， 确定类型的一致性。 而子群组 2和子群组 3假设为远程 成员， 这里假设子群组 2和子群组 3尚未通过成员类型一致性检查， 因为当群 组服务器 1分别向子群组 2和 3归属的群组服务器 2和群组服务器 3发送访问 请求后， 设定时长内没有收到对访问请求的访问响应。 这里的访问请求可以是 访问群组的类型属性。
403、 群组服务器 1创建群组 1 , 将群组的一个属性， 一致性检查标识设置 为 "检查未完成" ， 因为子群组 2和子群组 3还没有完成一致性检查。
404、 群组服务器 1向请求装置返回群组创建响应。 该群组创建响应中可以携带 "一致性检查未完成" 的标识。
405、 群组服务器 1向业务平台订阅不可达成员的在线状态。
群组服务器 1对于不可达成员， 可以向业务平台发送订阅请求， 本实施例 中， 群组服务器 1订阅子群组 2和子群组 3归属的群组服务器 2和群组服务器 3的在线状态， 由于群组服务器 2和群组服务器 3已在业务平台注册， 平台收 到订阅请求后可返回订阅成功响应。
406、 请求装置订阅所述群组的状态。
请求装置收到返回的群组创建响应后， 可以根据响应中携带的 "检查未完 成" 标识， 向群组服务器 1发送订阅请求， 请求订阅群组 1的状态。 群组服务 器 1接受订阅后可返回订阅成功的响应。
407、 群组服务器 3 可达后， 其在业务平台上注册的在线状态改变， 业务 平台向订阅者群组服务器 1发送通知消息， 通知 "群组服务器 3可达" 。
408、 群组服务器 1收到通知消息后， 向群组服务器 3发送访问请求， 请 求获取子群组 3的群组属性。
409、群组服务器 1收到群组服务器 3返回的访问响应， 其中包括子群组 3 的群组类型。
410、 群组服务器 1检查子群组 3的群组类型与群组 1的群组类型是否一 致， 假设图 4所示为不一致， 则群组服务器 1删除已创建的群组 1。
411、 群组服务器发送通知消息。
由于请求装置订阅了群组 1的状态， 群组服务器 1可以通知请求装置 "由 于成员 '子群组 3， 类型不一致， 群组 1已删除" 。
本实施例通过在群组中增加一致性检查标识， 并在群组创建响应中通知请 求装置所述一次性标识， 使得群组的创建不会因为类型检查等而失败， 极大提 高了用户使用 M2M技术的灵活性。 如图 5所示的是本发明实施例提供的另一种群组管理的方法。 与图 4所示 实施例类似， 在这个实施例中， 作为举例， 同样需创建群组 1 , 群组 1 包括的 成员有子群组成员， 如子群组 2和子群组 3 , 和设备成员， 如设备 4和设备 5。 该方法具体流程具体步骤包括：
501- 509、 与图 4所示实施例的步骤 401~ 409相同， 群组服务器 1接收了 创建群组请求， 创建群组， 返回响应。 并向业务平台订阅了群组服务器 2和 3 的在线状态。 群组服务器 3可达后， 获取到了子群组 3的群组类型。
510、 群组服务器 1检查子群组 3的群组类型与群组 1的群组类型是否一 致， 图 5所示假设为一致， 但由于群组服务器 2不可达， 子群组 2的群组类型 还无法获取， 因此群组 1的一致性检查标识还是 "未完成" 。
511、 群组服务器 2可达后， 其在业务平台上注册的资源在线状态改变， 业务平台向订阅者群组服务器 1发送通知消息， 通知 "群组服务器 2可达" 。
512、 群组服务器 1收到通知消息后， 向群组服务器 2发送访问请求， 请 求获取子群组 2的群组属性。
513、群组服务器 1收到群组服务器 2返回的访问响应， 其中包括子群组 2 的群组类型。
514、 群组服务器 1检查子群组 2的群组类型与群组 1的群组类型是否一 致， 4叚设图 5所示为一致， 则群组 1的所有成员都已检查过一致性， 因此将群 组 1的一致性检查标识设为 "已完成" 。 这里， 所有成员的成员类型都与群组 的群组类型一致。
515、 群组服务器发送通知消息。
由于请求装置订阅了群组 1的状态， 群组服务器 1可以通知请求装置群组 1 "一致性检查已完成" 。
本实施例通过在群组中增加一致性检查标识， 并在群组创建响应中通知请 求装置所述一次性标识， 使得群组的创建不会因为类型检查等而失败， 极大提 高了用户使用 M2M技术的灵活性。 如图 6所示的是本发明实施例提供的另一种群组管理的方法。 与图 4所示 实施例类似， 在这个实施例中， 作为举例， 同样需创建群组 1 , 群组 1 包括的 成员有子群组成员， 如子群组 2和子群组 3 , 和设备成员， 如设备 4和设备 5。 该方法具体流程具体步骤包括：
601- 609、 与图 4所示实施例的步骤 401~ 409相同， 群组服务器 1接收了 创建群组请求， 创建群组， 返回响应。 并向业务平台订阅了群组服务器 2和 3 的在线状态。 群组服务器 3可达后， 获取到了子群组 3的群组类型。
610、 群组服务器 1检查子群组 3的群组类型与群组 1的群组类型是否一 致， 假设图 6所示为不一致， 这里与图 4所示不同的是， 可以根据一个 "一致 性策略" 来确定如何处理。 例如可以直接删除已创建的群组， 这就如同图 4所 示。 还可以从已创建的群组中删除此类型不一致的成员， 例如这里就从群组 1 中删除子群组 3。 删除后由于群组服务器 2不可达， 子群组 2的群组类型还无 法获取， 因此群组 1的一致性检查还 "未完成" 。
一致性策略可以配置在群组服务器上， 也可以由请求装置携带在群组创建 请求中， 群组服务器收到后， 对请求创建的群组适用此 "一致性策略" 。 如果 一致性策略表示 "删除群组" ， 则群组服务器确定群组有一个成员的类型与群 组类型不一致后， 就删除此群组。 如果一致性策略表示 "删除成员" ， 则群组 服务器确定群组有成员的类型与群组类型不一致后， 就从群组中删除类型不一 致的成员。
611、 群组服务器发送通知消息。 请求装置订阅了群组 1 的状态， 群组服 务器 1可以通知请求装置 "群组 1的一个成员 '子群组 3， 类型不一致， 已从 群中删除" ， 还可以通知一致性检查仍然 "未完成" 。
612、 群组服务器 2可达后， 其在业务平台上注册的资源在线状态改变， 业务平台向订阅者群组服务器 1发送通知消息， 通知 "群组服务器 2可达" 。
613、 群组服务器 1收到通知消息后， 向群组服务器 2发送访问请求， 请 求获取子群组 2的群组属性。
614、群组服务器 1收到群组服务器 2返回的访问响应， 其中包括子群组 2 的群组类型。
615、 群组服务器 1检查子群组 2的群组类型与群组 1的群组类型是否一 致， 4叚设图 5所示为一致， 则群组 1的所有成员都已检查过一致性， 因此将群 组 1的一致性检查标识设为 "已完成" 。 这里， 所有成员的成员类型都与群组 的群组类型一致。
616、 群组服务器发送通知消息。
请求装置订阅了群组 1的状态， 群组服务器 1可以通知请求装置一次性检 查 "已完成" 。
本实施例通过在群组中增加一致性策略， 进一步提高了群组创建时关于一 致性处理的灵活性， 提高了用户使用 M2M技术的灵活性。 如图 7所示为本发明实施例提供的另一种群组管理的方法。 本实施例中， 子群组的类型由于成员的不可达， 也需要等待一致性确认。 与前述类似， 在本 实施例中， 作为举例， 需创建群组 1 , 群组 1 包括的成员有子群组成员， 如子 群组 2和子群组 3 , 和设备成员， 如设备 4和设备 5。 该方法具体流程具体步 骤包括：
701、 请求装置发送群组创建请求消息， 请求创建群组 1。
这里， 请求装置可以是 M2M设备、 M2M网关或业务平台， 群组服务器可 以为群组所归属的业务能力层 （Service Capability Layer, SCL )设备， 业务平 台可以是 M2M的 SCL ( SCL, Service Capability Layer )设备。 例如， 本实施例 中， 请求创建的群组 1归属于 SCL设备 1 , 即群组服务器 1 , 子群组 2和子群 组 3分别归属于 SCL设备 2和 3 , 即群组服务器 2和 3。 群组 1的两个设备成 员设备 4和设备 5也归属于 SCL设备 1。
群组创建请求中包括了请求创建的群组的群组类型， 本实施例 H没此类型 为非混合类， 例如应用类， 表明所有群组成员应是一致的类型。
702、 群组服务器 1 收到群组创建请求后， 检查确定群组成员类型与群组 类型的一致性。
群组服务器收到群组创建请求后， 根据群组类型确定是否需要检查一致 性， 如果群组类型是混合类型， 则不必检查一致性。 本实施例假设需要检查一 致性。
群组服务器获取群组成员列表中的所有成员的成员类型。 本地群组成员可 以直接获取成员的类型进行比较， 若群组包含远程群组成员， 群组服务器需要 进一步向远程成员所归属的 SCL设备获取所述成员的成员类型。
本实施例中， 假设群组 1的两个设备成员设备 4和设备 5为本地成员， 可 直接获取成员类型， 确定类型的一致性。 而子群组 2和子群组 3假设为远程成 员， 这里 4叚设子群组 2和子群组 3尚未通过成员类型一致性检查。 与图 4所示 实施例不同的是， 群组服务器 1分别向子群组 2和 3归属的群组服务器 2和群 组服务器 3发送访问请求， 请求获取子群组的类型属性， 然后分别收到群组服 务器 2和群组服务器 3返回的访问响应， 响应中包括了参数分别表明子群组 2 和子群组 3—致性验证 "未完成" 。 子群组未完成验证的可能原因包括子群组 的成员中有些成员当前不可达。
703、群组服务器 1创建群组 1 ,将群组的一致性检查标识设置为"未完成"， 因为子群组 2和子群组 3还没有完成一致性检查。
704、 群组服务器 1向请求装置返回群组创建响应。
该群组创建响应中可以携带群组的一次性标识属性， 本实施例中， 这里为 "未冗成" 。
705、 群组服务器 1分别向群组服务器 2和 3订阅订阅未完成一致性检查 的子群组的状态。
群组服务器 1对于未完成一致性检查的子群组， 可以向子群组归属的群组 服务器发送订阅请求， 本实施例中， 群组服务器 1分别向群组服务器 2和群组 服务器 3订阅子群组 2和子群组 3的状态。
706、 请求装置订阅群组状态。
请求装置收到返回的群组创建响应后， 可以根据响应中携带的一致性检查 "未完成" 标识， 向群组服务器 1发送订阅请求， 请求订阅群组 1的状态， 群 组 1 的状态改变后，群组服务器 1可通知请求装置。群组服务器 1接受订阅后 可返回订阅成功的响应。
707、 接收群组服务器 3的通知消息。
群组服务器 3在完成子群组 3的一致性检查后， 例如子群组 3的不可达成 员可达后， 可以根据子群组 3的 "一致性策略" 进行处理， 这里 H没子群组 3 包含了类型不一致的成员， 而 "一致性策略" 为 "不一致时删除成员" 。 则群 组服务器 3删除子群组 3中不一致的成员。 删除后子群组 3—致性检查标识为 "已完成" 。 由于群组服务器 1订阅了子群组 3的状态改变， 群组服务器 3向 订阅者群组服务器 1发送通知消息， 通知 "子群组 3—致性检查已完成" 。
708、 群组服务器 1检查子群组 3的群组类型与群组 1的群组类型是否一 致， 本实施例^^设为不一致， 且群组 1的 "一致性策略" 为 "不一致时删除成 员" ， 则从群组 1中删除子群组 3。 删除后由于群组服务器 2仍未完成一致性 检查， 因此群组 1的一致性检查还未完成。
709、 接收群组服务器 2的通知消息。
群组服务器 2在完成子群组 2的一致性检查后， 例如子群组 2的不可达成 员可达后， 可以根据子群组 2的 "一致性策略" 进行处理， 这里 H没子群组 2 包含了类型不一致的成员， 而 "一致性策略" 为 "不一致时删除群组" 。 则群 组服务器 2直接删除子群组 2。由于群组服务器 1订阅了子群组 2的状态改变， 群组服务器 2向订阅者群组服务器 1发送通知消息，通知"子群组 2已被删除"。
710、 群组服务器 1收到 "子群组 2已被删除" 的通知后， 从群组 1 中删 除子群组 2。 群组 1的所有成员都已检查过一致性， 因此将群组 1的一致性检 查标识设为 "已完成" 。 这里， 所有成员的成员类型都与群组的群组类型一致。
711、 群组服务器发送通知消息。
请求装置订阅了群组 1的状态， 群组服务器 1可以通知请求装置一致性检 查 "已完成" ， 并进一步通知 "子群组 2删除， 子群组 3删除" 。 图 8所示为本发明实施例提供的一种机器通信的群组服务器示意图，包括：
801 , 接收单元， 用于接收请求装置发送的群组创建请求， 所述群组创建 请求包括请求创建群组的群组类型；
802 , 一致性检查单元， 用于检查群组中成员的成员类型与所述群组类型 的一致性， 根据一致性检查结果设置所述群组的一致性检查标识；
803 , 发送单元， 用于向所述请求装置返回包含一致性检查结果的群组创 建响应。
可选的， 群组服务器还可以包括： 804 , 策略单元， 用于当确定群组中一 个成员的成员类型与所述群组类型不一致时， 从所述群组中删除所述与群组类 型不一致的成员， 或者直接删除所述群组。
可选的， 所述群组的属性包括一致性策略， 所述策略单元进一步根据所述 一致性策略确定当群组中一个成员的成员类型与所述群组类型不一致时， 是否 从所述群组中删除所述与群组类型不一致的成员， 或者， 是否删除所述已创建 的群组。
可选的， 所述群组服务器还包括： 805 , 订阅单元， 用于确定所述群组中 成员不可达时， 向业务平台订阅所述不可达成员归属设备的在线状态， 当所述 在线状态改变时， 接收所述业务平台发送的通知消息； 所述一致性检查单元确 定所述成员可达后， 获取所述成员的成员类型， 并确定所述成员的成员类型与 所述群组类型的一致性。
可选的， 所述一致性检查单元具体用于： 确定所述群组的成员为非子群组 成员， 根据成员的统一资源标识符 URI确定所述成员类型； 确定所述成员类型 后， 确定所述成员的成员类型与所述群组类型的一致性。
可选的， 所述群组服务器还包括订阅单元， 用于当确定所述群组中的子群 组成员未完成自身的一致性检查时， 向子群组归属设备订阅所述子群组的状 态， 并接收子群组的状态通知； 所述一致性检查单元根据所述状态通知确定所 述子群组类型， 并确定所述子群组的类型与所述群组类型的一致性。 图 9所示为本发明实施例提供的一种机器通信的请求装置示意图， 包括：
901 , 发送单元， 用于向群组服务器发送群组创建请求， 所述群组创建请 求包括请求创建群组的群组类型；
902 , 接收单元， 用于接收返回的群组创建响应， 所述群组创建响应中包 含群组中成员的成员类型与群组类型的一致性检查的结果。
可选的， 还包括： 903 , 订阅单元， 用于根据所述群组创建响应， 向群组 服务器订阅所述群组的状态。 图 10 所示的是本发明实施例提供的群组服务器的另一种结构示意图， 釆 用通用计算机系统结构， 执行本发明方案的程序代码保存在存储器中， 并由处 理器来控制执行。 群组服务器包括总线， 处理器 （1001 ) ， 存储器（ 1002 ) ， 通信接口 （ 1003 ) 。
总线可包括一通路， 在计算机各个部件之间传送信息。
处理器可以是一个通用中央处理器（CPU ) ， 微处理器， 特定应用集成电 路 application-specific integrated circuit (ASIC),或一个或多个用于控制本发明方 案程序执行的集成电路。 计算机系统中包括的一个或多个存储器， 可以是只读 存储器 read-only memory (ROM) 或可存储静态信息和指令的其他类型的静态 存储设备，随机存取存储器 random access memory (RAM) 或者可存储信息和指 令的其他类型的动态存储设备， 也可以是磁盘存储器。 这些存储器通过总线与 处理器相连接。
通信接口， 可以使用任何收发器一类的装置， 以便与其他设备或通信网络 通信， 如以太网， 无线接入网 ( RAN ) , 无线局域网（WLAN)等.
存储器， 如 RAM, 保存有操作系统和执行本发明方案的程序。 操作系统 是用于控制其他程序运行， 管理系统资源的程序。 执行本发明方案的程序代码 保存在存储器中， 并由处理器来控制执行。
存储器中存储的程序用于指令处理器执行一种机器通信中群组管理的方 法， 包括：
接收请求装置发送的群组创建请求， 所述群组创建请求包括请求创建群组 的群组类型；
检查群组中成员的成员类型与所述群组类型的一致性， 根据一致性检查结 果设置所述群组的一致性检查标识；
向所述请求装置返回包含一致性检查结果的群组创建响应。
可选的， 所述方法还包括： 确定群组中一个成员的成员类型与所述群组类 型不一致； 从所述群组中删除所述与群组类型不一致的成员， 或者直接删除所 述群组。
可选的， 所述群组的属性包括一致性策略； 根据所述一致性策略确定当群 组中一个成员的成员类型与所述群组类型不一致时 , 是否从所述群组中删除所 述与群组类型不一致的成员， 或者， 是否删除所述已创建的群组。
可选的， 所述检查群组中成员的成员类型与所述群组类型的一致性具体包 括： 确定所述群组中成员不可达； 向业务平台订阅所述不可达成员归属设备的 在线状态， 当所述在线状态改变时， 接收所述业务平台发送的通知消息， 或者 对所述不可达成员的归属设备进行周期性轮询， 直到所述不可达成员可达； 确 定所述成员可达后， 获取所述成员的成员类型， 并确定所述成员的成员类型与 所述群组类型的一致性。 可选的， 所述检查群组中成员的成员类型与所述群组类型的一致性具体包 括： 确定所述群组的成员为非子群组成员， 根据成员的统一资源标识符 URI 确定所述成员类型； 确定所述成员类型后， 确定所述成员的成员类型与所述群 组类型的一致性。
可选的， 所述检查群组中成员的成员类型与所述群组类型的一致性具体包 括： 确定所述群组中的子群组成员未完成自身的一致性检查； 向子群组归属设 备订阅所述子群组的状态； 接收子群组的状态通知， 根据所述状态通知确定所 述子群组类型， 并确定所述子群组的类型与所述群组类型的一致性。 图 11 所示的是本发明实施例提供的请求装置的另一种结构示意图， 釆用 通用计算机系统结构， 执行本发明方案的程序代码保存在存储器中， 并由处理 器来控制执行。 群组服务器包括总线， 处理器（1101 ) , 存储器（1102 ) , 通 信接口 （1103 ) 。
总线可包括一通路， 在计算机各个部件之间传送信息。
处理器可以是一个通用中央处理器（CPU ) ， 微处理器， 特定应用集成电 路 application-specific integrated circuit (ASIC),或一个或多个用于控制本发明方 案程序执行的集成电路。 计算机系统中包括的一个或多个存储器， 可以是只读 存储器 read-only memory (ROM) 或可存储静态信息和指令的其他类型的静态 存储设备，随机存取存储器 random access memory (RAM) 或者可存储信息和指 令的其他类型的动态存储设备， 也可以是磁盘存储器。 这些存储器通过总线与 处理器相连接。
通信接口， 可以使用任何收发器一类的装置， 以便与其他设备或通信网络 通信， 如以太网， 无线接入网 ( RAN ) , 无线局域网（WLAN)等.
存储器， 如 RAM, 保存有操作系统和执行本发明方案的程序。 操作系统 是用于控制其他程序运行， 管理系统资源的程序。 执行本发明方案的程序代码 保存在存储器中， 并由处理器来控制执行。 存储器中存储的程序用于指令处理器执行一种机器通信中群组管理的方 法， 包括：
向群组服务器发送群组创建请求， 所述群组创建请求包括请求创建群组的 群组类型；
接收返回的群组创建响应， 所述群组创建响应中包含群组中成员的成员类 型与群组类型的一致性检查的结果。
可选的， 所述方法还包括： 根据所述群组创建响应， 向群组服务器订阅所 述群组的状态。 需要说明的是， 本说明书中的各个实施例均釆用递进的方式描述， 各个实 施例之间相同相似的部分互相参见即可， 每个实施例重点说明的都是与其他实 施例的不同之处。 尤其，对于装置实施例而言， 由于其基本相似于方法实施例， 所以描述得比较简单， 各单元具体功能的执行过程参见方法实施例的部分说明 即可。 以上所描述的装置实施例仅仅是示意性的， 其中作为分离部件说明的单 元可以是或者也可以不是物理上分开的， 作为单元显示的部件可以是或者也可 以不是物理单元， 即可以位于一个地方， 或者也可以分布到多个网络单元上。 可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目 的。 本领域普通技术人员在不付出创造性劳动的情况下， 即可以理解并实施。
总之， 以上所述仅为本发明技术方案的较佳实施例而已， 并非用于限定本 发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1、 一种机器通信中群组管理的方法， 其特征在于， 包括：
接收请求装置发送的群组创建请求， 所述群组创建请求包括请求创建群组 的群组类型；
检查群组中成员的成员类型与所述群组类型的一致性， 根据一致性检查结 果设置所述群组的一致性检查标识；
向所述请求装置返回包含一致性检查结果的群组创建响应。
2、 如权利要求 1所述的方法， 其特征在于， 所述方法还包括：
确定群组中一个成员的成员类型与所述群组类型不一致；
从所述群组中删除所述与群组类型不一致的成员， 或者直接删除所述群 组。
3、 如权利要求 1或 2所述的方法， 其特征在于， 所述群组的属性包括一 致性策略； 根据所述一致性策略确定当群组中一个成员的成员类型与所述群组 类型不一致时， 是否从所述群组中删除所述与群组类型不一致的成员， 或者， 是否删除所述已创建的群组。
4、 如权利要求 1至 3任一项所述的方法， 其特征在于， 所述检查群组中 成员的成员类型与所述群组类型的一致性具体包括：
确定所述群组中成员不可达；
向业务平台订阅所述不可达成员归属设备的在线状态， 当所述在线状态改 变时， 接收所述业务平台发送的通知消息， 或者
对所述不可达成员的归属设备进行周期性轮询， 直到所述不可达成员可 达； 确定所述成员可达后， 获取所述成员的成员类型， 并确定所述成员的成员 类型与所述群组类型的一致性。
5、 如权利要求 1至 4任一项所述的方法， 其特征在于， 所述检查群组中 成员的成员类型与所述群组类型的一致性具体包括：
确定所述群组的成员为非子群组成员， 根据成员的统一资源标识符 URI 确定所述成员类型；
确定所述成员类型后， 确定所述成员的成员类型与所述群组类型的一致 性。
6、 如权利要求 1至 5任一项所述的方法， 其特征在于， 所述检查群组中 成员的成员类型与所述群组类型的一致性具体包括：
确定所述群组中的子群组成员未完成自身的一致性检查；
向子群组归属设备订阅所述子群组的状态；
接收子群组的状态通知， 根据所述状态通知确定所述子群组类型， 并确定 所述子群组的类型与所述群组类型的一致性。
7、 如权利要求 1至 6任一项所述的方法， 其特征在于， 当所述群组类型 为非混合型时， 检查群组中成员的成员类型与所述群组类型的一致性。
8、 一种机器通信中群组管理的方法， 其特征在于， 包括：
向群组服务器发送群组创建请求， 所述群组创建请求包括请求创建群组的 群组类型；
接收返回的群组创建响应， 所述群组创建响应中包含群组中成员的成员类 型与群组类型的一致性检查的结果。
9、 如权利要求 8所述的方法， 其特征在于， 还包括：
根据所述群组创建响应， 向群组服务器订阅所述群组的状态。
10、 一种机器通信的群组服务器， 其特征在于， 包括：
接收单元， 用于接收请求装置发送的群组创建请求， 所述群组创建请求包 括请求创建群组的群组类型；
一致性检查单元， 用于检查群组中成员的成员类型与所述群组类型的一致 性 , 根据一致性检查结果设置所述群组的一致性检查标识；
发送单元， 用于向所述请求装置返回包含一致性检查结果的群组创建响 应。
11、 如权利要求 10所述的群组服务器， 其特征在于， 还包括：
策略单元， 用于当确定群组中一个成员的成员类型与所述群组类型不一致 时，从所述群组中删除所述与群组类型不一致的成员，或者直接删除所述群组。
12、 如权利要求 10或 11所述的群组服务器， 其特征在于， 所述群组的属 性包括一致性策略， 所述策略单元进一步根据所述一致性策略确定当群组中一 个成员的成员类型与所述群组类型不一致时， 是否从所述群组中删除所述与群 组类型不一致的成员， 或者， 是否删除所述已创建的群组。
13、 如权利要求 10至 12任一项所述的群组服务器， 其特征在于， 所述群 组服务器还包括订阅单元， 用于确定所述群组中成员不可达时， 向业务平台订 阅所述不可达成员归属设备的在线状态， 当所述在线状态改变时， 接收所述业 务平台发送的通知消息； 所述一致性检查单元确定所述成员可达后， 获取所述 成员的成员类型， 并确定所述成员的成员类型与所述群组类型的一致性。
14、 如权利要求 10至 13任一项所述的群组服务器， 其特征在于， 所述一 致性检查单元具体用于：
确定所述群组的成员为非子群组成员， 根据成员的统一资源标识符 URI 确定所述成员类型；
确定所述成员类型后， 确定所述成员的成员类型与所述群组类型的一致 性。
15、 如权利要求 10至 14任一项所述的群组服务器， 其特征在于， 所述群 组服务器还包括订阅单元， 用于当确定所述群组中的子群组成员未完成自身的 一致性检查时， 向子群组归属设备订阅所述子群组的状态， 并接收子群组的状 态通知； 所述一致性检查单元根据所述状态通知确定所述子群组类型， 并确定 所述子群组的类型与所述群组类型的一致性。
16、 一种机器通信的请求装置， 其特征在于， 包括：
发送单元， 用于向群组服务器发送群组创建请求， 所述群组创建请求包括 请求创建群组的群组类型；
接收单元， 用于接收返回的群组创建响应， 所述群组创建响应中包含群组 中成员的成员类型与群组类型的一致性检查的结果。
17、 如权利要求 16所述的请求装置， 其特征在于， 还包括：
订阅单元， 用于根据所述群组创建响应， 向群组服务器订阅所述群组的状
PCT/CN2012/085062 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置 WO2014079019A1 (zh)

Priority Applications (11)

Application Number Priority Date Filing Date Title
CN201810381077.6A CN108769931B (zh) 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置
PCT/CN2012/085062 WO2014079019A1 (zh) 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置
EP12888718.9A EP2925028B1 (en) 2012-11-22 2012-11-22 Method and device for group management in machine communication
ES12888718.9T ES2665585T3 (es) 2012-11-22 2012-11-22 Método y dispositivo para la gestión de grupos en comunicación de máquinas
EP17170554.4A EP3297302B1 (en) 2012-11-22 2012-11-22 Method and apparatus for group management during machine-to-machine communication
JP2015543229A JP6137649B2 (ja) 2012-11-22 2012-11-22 マシン・ツー・マシン通信の間のグループ管理のための方法および装置
CN201280002346.4A CN104041086B (zh) 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置
KR1020157016227A KR101711462B1 (ko) 2012-11-22 2012-11-22 기기 간 통신 중 그룹 관리를 위한 방법 및 장치
AU2012395266A AU2012395266B2 (en) 2012-11-22 2012-11-22 Method and device for group management in machine communication
US14/718,351 US10244549B2 (en) 2012-11-22 2015-05-21 Method and apparatus for group management during machine-to-machine communication
US16/297,372 US10638496B2 (en) 2012-11-22 2019-03-08 Method and apparatus for group management during machine-to-machine communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/085062 WO2014079019A1 (zh) 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/718,351 Continuation US10244549B2 (en) 2012-11-22 2015-05-21 Method and apparatus for group management during machine-to-machine communication

Publications (1)

Publication Number Publication Date
WO2014079019A1 true WO2014079019A1 (zh) 2014-05-30

Family

ID=50775401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/085062 WO2014079019A1 (zh) 2012-11-22 2012-11-22 一种机器通信中群组管理的方法和装置

Country Status (8)

Country Link
US (2) US10244549B2 (zh)
EP (2) EP2925028B1 (zh)
JP (1) JP6137649B2 (zh)
KR (1) KR101711462B1 (zh)
CN (2) CN108769931B (zh)
AU (1) AU2012395266B2 (zh)
ES (1) ES2665585T3 (zh)
WO (1) WO2014079019A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016145900A1 (zh) * 2015-03-17 2016-09-22 中兴通讯股份有限公司 一种末梢网络建立方法、装置、系统及存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104869532B (zh) * 2015-04-28 2020-10-09 海尔优家智能科技（北京）有限公司 一种群组成员管理方法和装置
CN104869531B (zh) * 2015-04-28 2020-09-01 海尔优家智能科技（北京）有限公司 一种群组成员更新方法和装置
CN105791405A (zh) * 2016-03-02 2016-07-20 郭金发 一种围绕读物打通用户沟通壁垒的系统和方法
KR101895941B1 (ko) * 2016-09-20 2018-09-07 한림대학교 산학협력단 게이트웨이 및 그를 이용한 그룹 통신 방법
CN108989996B (zh) * 2018-07-03 2021-05-25 京东方科技集团股份有限公司 通信方法及通信装置、电子设备、存储介质
CN110769421B (zh) * 2018-07-26 2021-08-13 华为技术有限公司 一种群组创建方法、装置及系统
CN109391697B (zh) * 2018-11-21 2021-12-28 深圳市商汤科技有限公司 信息推送方法、用户终端、服务器及门禁控制终端
US10986646B1 (en) 2019-10-19 2021-04-20 Skylo Technologies, Inc. Scheduling virtual preambles for data source reporting

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101938705A (zh) * 2009-06-30 2011-01-05 华为技术有限公司 群组管理方法、网络设备和网络系统
CN102130773A (zh) * 2011-02-25 2011-07-20 华为技术有限公司 群组通信的方法和用于群组通信的装置
CN102487483A (zh) * 2010-12-06 2012-06-06 财团法人工业技术研究院 信号传输方法、基站及无线通信装置

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100370850C (zh) * 2005-09-26 2008-02-20 华为技术有限公司 一种创建群组和添加群组成员的方法、装置及系统
US20070245650A1 (en) * 2006-04-04 2007-10-25 Milgard Manufactoring Incorporated Framing corner joint and method of manufacture
FI20065479A0 (fi) 2006-07-05 2006-07-05 Nokia Corp Ryhmäkommunikaatio
CN102170641B (zh) * 2010-02-26 2016-03-30 中兴通讯股份有限公司 一种m2m业务组资源配置和分配的方法及系统
WO2011129575A2 (ko) * 2010-04-12 2011-10-20 엘지전자 주식회사 그룹 기반 ｍ2ｍ 통신을 수행하기 위한 장치 및 그 방법
JP5807055B2 (ja) * 2010-04-22 2015-11-10 ホアウェイ・テクノロジーズ・カンパニー・リミテッド 輻輳／過負荷制御方法および装置
US8942191B2 (en) * 2010-05-03 2015-01-27 Mformation Software Technologies Llc Providing dynamic group subscriptions for M2M device communication
CN101860807A (zh) * 2010-05-05 2010-10-13 工业和信息化部电信传输研究所 一种m2m终端设备组的管理、建立通信方法及装置
GB2484922B (en) * 2010-10-25 2014-10-08 Sca Ipla Holdings Inc Infrastructure equipment and method
WO2012111255A1 (ja) * 2011-02-14 2012-08-23 パナソニック株式会社 ページング方法、ページングシステム、通信デバイス及び通信相手ノード
CN102088668B (zh) * 2011-03-10 2013-09-25 西安电子科技大学 基于群组的机器类型通信设备的认证方法
US20120252518A1 (en) * 2011-04-01 2012-10-04 Interdigital Patent Holdings, Inc. Network initiated triggering of an offline device
US8818946B2 (en) * 2011-07-08 2014-08-26 Telefonaktiebolaget L M Ericsson (Publ) Machine to machine (M2M) application server, XDMS server, and methods for M2M applications group management

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101938705A (zh) * 2009-06-30 2011-01-05 华为技术有限公司 群组管理方法、网络设备和网络系统
CN102487483A (zh) * 2010-12-06 2012-06-06 财团法人工业技术研究院 信号传输方法、基站及无线通信装置
CN102130773A (zh) * 2011-02-25 2011-07-20 华为技术有限公司 群组通信的方法和用于群组通信的装置

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016145900A1 (zh) * 2015-03-17 2016-09-22 中兴通讯股份有限公司 一种末梢网络建立方法、装置、系统及存储介质
CN106034281A (zh) * 2015-03-17 2016-10-19 中兴通讯股份有限公司 一种基于m2m网关的末梢网络建立方法、装置和系统
CN106034281B (zh) * 2015-03-17 2018-08-14 中兴通讯股份有限公司 一种基于m2m网关的末梢网络建立方法、装置和系统
US10405180B2 (en) 2015-03-17 2019-09-03 Zte Corporation Stub network establishing method, device and system, and storage medium

Also Published As

Publication number Publication date
EP2925028B1 (en) 2018-01-10
CN104041086A (zh) 2014-09-10
CN108769931B (zh) 2021-06-22
US10244549B2 (en) 2019-03-26
AU2012395266A1 (en) 2015-06-11
US20150257170A1 (en) 2015-09-10
EP2925028A1 (en) 2015-09-30
CN104041086B (zh) 2018-05-18
JP6137649B2 (ja) 2017-05-31
US10638496B2 (en) 2020-04-28
KR20150087354A (ko) 2015-07-29
JP2016508299A (ja) 2016-03-17
EP3297302B1 (en) 2020-05-06
KR101711462B1 (ko) 2017-03-02
EP2925028A4 (en) 2016-05-18
EP3297302A1 (en) 2018-03-21
CN108769931A (zh) 2018-11-06
ES2665585T3 (es) 2018-04-26
AU2012395266B2 (en) 2016-03-03
US20190208529A1 (en) 2019-07-04

Similar Documents

Publication Publication Date Title
WO2014079019A1 (zh) 一种机器通信中群组管理的方法和装置
JP6514315B2 (ja) マシン対マシンネットワークにおけるリソースおよび属性管理
JP5805873B2 (ja) Ｍ２ｍデバイスサブスクリプションのための方法及び装置
US9438601B2 (en) Operating group resources in sub-groups and nested groups
US10085244B2 (en) Method for guaranteeing operation of control message in wireless communication system and device for same
EP2547040B1 (en) Group communication method and device for use in group communication
JP6240312B2 (ja) Ｍ２ｍ通信システムにおいて購読及び通知のための方法及びそのための装置
JP6055111B2 (ja) 無線通信システムにおいて接近制御のための方法及び装置
CN110460978B (zh) 一种资源访问的方法和装置
KR102500594B1 (ko) 통신 네트워크에서의 서비스 계층 메시지 템플릿들
EP4178177A1 (en) Information processing method in m2m and apparatus
US20230421663A1 (en) Efficient resource representation exchange between service layers
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
WO2017136979A1 (zh) 一种远程访问的实现方法、装置和系统
CN105323186B (zh) 一种通知消息的负载控制方法和装置
CN104462235A (zh) 一种基于Restful Web Service的物联网通用事件服务机制
KR20180110456A (ko) oneM2M기반 서비스 연계를 위한 연동 시스템
WO2016008102A1 (zh) 对群组资源中成员资源的操作请求的处理方法及装置

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: 12888718

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015543229

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012888718

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2012395266

Country of ref document: AU

Date of ref document: 20121122

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20157016227

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: IDP00201503758

Country of ref document: ID