(19)
(11)EP 3 297 302 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
06.05.2020 Bulletin 2020/19

(21)Application number: 17170554.4

(22)Date of filing:  22.11.2012
(51)Int. Cl.: 
H04W 4/08  (2009.01)

(54)

METHOD AND APPARATUS FOR GROUP MANAGEMENT DURING MACHINE-TO-MACHINE COMMUNICATION

VERFAHREN UND VORRICHTUNG ZUR GRUPPENVERWALTUNG BEI MASCHINE-ZU-MASCHINE-KOMMUNIKATION

PROCÉDÉ ET APPAREIL DE GESTION DE GROUPES PENDANT UNE COMMUNICATION MACHINE-MACHINE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(43)Date of publication of application:
21.03.2018 Bulletin 2018/12

(62)Application number of the earlier application in accordance with Art. 76 EPC:
12888718.9 / 2925028

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventor:
  • GAO, Ying
    shenzhen, Guangdong (CN)

(74)Representative: Kreuz, Georg Maria 
Huawei Technologies Duesseldorf GmbH Riesstraße 25
80992 München
80992 München (DE)


(56)References cited: : 
WO-A2-2011/129575
CN-A- 102 130 773
CN-A- 101 938 705
  
  • Etsi: "Machine-to-Machine communications (M2M); Functional architecture Technical Specification", , 1 October 2011 (2011-10-01), XP055155948, Retrieved from the Internet: URL:http://www.etsi.org/deliver/etsi_ts/10 2600_102699/102690/01.01.01_60/ts_102690v0 10101p.pdf [retrieved on 2014-12-01]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

TECHNICAL FIELD



[0001] The present invention relates to the field of information technologies, and in particular, to a method and an apparatus for group management during machine-to-machine communication.

BACKGROUND



[0002] Machine-to-machine communication (Machine-to-Machine Communications, M2M) is a network based application and service focusing on intelligent interaction between machines. By embedding a wireless or wired communication module and application processing logic in a machine, M2M implements information requirements of users in surveillance, commanding and scheduling, data collection, and measurement. In an M2M system, all types of M2M devices, such as varied sensors, are connected to an M2M service platform directly via an M2M gateway. Thereby, different M2M services are implemented, such as electric meter reading and intelligent traffic control. Data collected by M2M devices can be acquired or M2M devices can be controlled and managed through service capabilities provided by the M2M service platform.

[0003] There are many types of M2M devices, such as an application type, an access right type, and a management object type. M2M devices can be grouped and each group has a group type to indicate the type of members in the group. If all members of a group belong to one type, the type of the group is this consistent type. If the members of a group belong to different types, the type of the group is a hybrid type.

[0004] In a prior art, M2M services always require group operations on a group of devices of the same type without expecting other types of members in the group. When a group server receives a group creation request or group update request, the group server checks the type of members in the group. A failure of the check will immediately lead to a failure of group creation or group update. Yet the check failure may be a result of many causes; for example, some member devices in the group are dormant and cannot be checked. Therefore, the probability of the group creation or group update failure is high, which seriously hinders the flexibility of use.

[0005] ETSI TS 102 690 V1.1.1 (2011-10), contains the overall end to end M2M functional architecture, including the identification of the functional entities and the related reference points.

SUMMARY



[0006] To overcome the disadvantage of the prior art, the present invention provides a method and an apparatus for group management during machine-to-machine communication, to increase the flexibility of creating and using M2M groups. The objects are solved by the features of the independent claims. The invention is defined by the claims.

[0007] According to a first aspect, the present invention provides a method for group management during machine-to-machine communication according to claim 1. Preferably, the method includes:

receiving a group creation request sent by a requesting apparatus, where the group creation request carries a group type of a group requested to be created;

checking consistency between member types of members in the group and the group type and setting a consistency check flag of the group according to a consistency check result; and

returning a group creation response that carries the consistency check result to the requesting apparatus.



[0008] In a first possible implementation of the first aspect, the method further includes: determining that the member type of one member in the group is inconsistent with the group type; and deleting the member whose member type is inconsistent with the group type from the group or deleting the group directly.

[0009] In a second possible implementation of the first aspect, attributes of the group include a consistency policy and the method further includes determining, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete the created group when it is determined that the member type of the member in the group is inconsistent with the group type.

[0010] In a third possible implementation of the first aspect, the checking consistency between member types of members in the group and the group type specifically includes: determining that a member in the group is unreachable; subscribing to an online status of a home device of the unreachable member from a service platform, and when the online status changes, receiving a notification message sent by the service platform, or polling the home device of the unreachable member periodically until the unreachable member is reachable; and after determining that the member is reachable, obtaining the member type of the reachable member and determining consistency between the member type of the reachable member and the group type.

[0011] In a fourth possible implementation of the first aspect, the checking consistency between member types of members in the group and the group type specifically includes: determining that a member in the group is a non-subgroup member and determining the member type according to a uniform resource identifier URI of the member; and after determining the member type of the member, determining consistency between the member type of the member and the group type.

[0012] In a fifth possible implementation of the first aspect, the checking consistency between member types of members in the group and the group type specifically includes: determining that the consistency check of a subgroup member in the group is uncompleted; subscribing to a status of a subgroup from a home device of the subgroup; and receiving a status notification of the subgroup, determining the type of the subgroup according to the status notification, and determining consistency between the type of the subgroup and the group type.

[0013] In a sixth possible implementation of the first aspect, when the group type is a non-hybrid type, the method further includes checking consistency between the member type of members in the group and the group type.

[0014] According to a second aspect, the present invention provides a device for machine-to-machine communication according to claim 8. The device preferably includes:

a receiving unit, configured to receive a group creation request sent by a requesting apparatus, where the group creation request carries a group type of a group requested to be created;

a consistency check unit, configured to check consistency between member types of members in the group and the group type and set a consistency check flag of the group according to a consistency check result; and

a sending unit, configured to return a group creation response that carries the consistency check result to the requesting apparatus.



[0015] In a first possible implementation of the second aspect, the group server further includes: a policy unit, configured to: when it is determined that the member type of one member in the group is inconsistent with the group type, delete the member whose member type is inconsistent with the group type from the group or delete the group directly.

[0016] In a second possible implementation of the second aspect, attributes of the group include a consistency policy and the policy unit further determines, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete the created group when it is determined that the member type of the member in the group is inconsistent with the group type.

[0017] In a third possible implementation of the second aspect, the group server further includes a subscribing unit, configured to subscribe to an online status of a home device of an unreachable member in the group from a service platform when the member is determined to be unreachable, and when the online status changes, receive a notification message sent by the service platform; and the consistency check unit obtains the member type of the member after determining that the member is reachable and determines consistency between the member type of the member and the group type.

[0018] In a fourth possible implementation of the second aspect, the consistency check unit is specifically configured to: determine that a member of the group is a non-subgroup member and determine the member type according to a uniform resource identifier URI of the member; and determine consistency between the member type of the member and the group type after determining the member type.

[0019] In a fifth possible implementation of the second aspect, the group server further includes a subscribing unit, configured to: when it is determined that the consistency check of a subgroup member in the group is uncompleted, subscribe to a status of a subgroup from a home device of the subgroup and receive a status notification of the subgroup; and the consistency check unit determines the type of the subgroup according to the status notification and determines consistency between the type of the subgroup and the group type.

[0020] According to the present invention, by setting the consistency check flag of a group and notifying the requesting apparatus of the consistency check flag in a group creation response, the creation of the group will not fail because of type check, which greatly increases the flexibility of using the M2M technology.

BRIEF DESCRIPTION OF DRAWINGS



[0021] To illustrate the technical solutions of the present invention more clearly, in the following the accompanying drawings are briefly introduced describing embodiments of the present invention. Apparently, the accompanying drawings show merely some embodiments of the present invention, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

FIG. 1 is a system architecture diagram for 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 group management 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 invention;

FIG. 9 is a schematic structural diagram of a requesting apparatus according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of another group server according to an embodiment of the present invention; and

FIG. 11 is a schematic structural diagram of another requesting apparatus according to an embodiment of the present invention.


DESCRIPTION OF EMBODIMENTS



[0022] The following describes the technical solutions of the present invention with reference to the accompanying drawings of embodiments of the present invention. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0023] An embodiment of the present invention provides a system for M2M group management. As shown in FIG. 1, the system for M2M group management includes a group server and a requesting apparatus.

[0024] The group server is configured to: receive a group creation request sent by the requesting apparatus, where the group creation request carries a group type of a group requested to be created; check consistency between member types of members in the group and the group type and set a consistency check flag of the group according to a consistency check result; and return a group creation response that carries the consistency check result to the requesting apparatus.

[0025] The requesting apparatus is configured to send the group creation request to the group server and receive the returned group creation response, where the group creation response carries the result of the consistency check between the member types of members in the group and the group type.

[0026] In the embodiment of the present invention, the group server may be a service platform, an M2M gateway, or an M2M device that can store and maintain groups and a created group is homed to the group server. The requesting apparatus may also be a service platform, an M2M gateway, or an M2M device and a group that the requesting apparatus requests to create is in the group server.

[0027] An embodiment of the present invention provides a method for M2M group management. As shown in FIG. 2, the method includes the following steps:
201. A group server receives a group creation request sent by a requesting apparatus, where the group creation request carries a group type of a group requested to be created.

[0028] The group creation request carries the group type and optionally may carry information such as a group identifier and group members.

[0029] 202. The group server checks consistency between member types of members in the group and the group type and sets a consistency check flag of the group according to a consistency check result.

[0030] For subgroup members in the group, the group server may obtain the "group type" attribute of a subgroup; for non-subgroup members in the group, the group server may determine their member types according to the uniform resource identifier (Uniform Resource Identifier, URI) of each member. For example, the URI of one member is "coap://ggl.example.com/applications/templ", where "applications" indicates that the type of the member is an "application" type. After determining the member types, the group server further determines the consistency between the member types and the group type.

[0031] When the group type is hybrid, the group server does not need to check consistency between member types of members in the group and the group type.

[0032] Preferably, when the group server determines that the type of one member in the group is inconsistent with the group type, the group server may delete the member whose member type is inconsistent with the group type from the group or delete the created group directly. Further, a consistency policy may be included in the group attributes for determining whether to delete the member whose member type is inconsistent with the group type or delete the created group when it is determined that the member type of one member in the group is inconsistent with the group type.

[0033] Optionally, when the group server determines that a member in the group is unreachable, the group server may subscribe to the online status of the unreachable member from a service platform where a home device of the unreachable member is registered, and when the home device of the unreachable member is online, the service platform sends a notification message to the subscriber. Or, the group server polls the home device of the unreachable device periodically until the device is reachable and then obtains the member type of the member and determines its consistency with the group type.

[0034] Optionally, when a group member is unreachable, the group server may first obtain the member type of the group member from a cached record and determine consistency between the member type of the member and the group type. After the member is reachable, the group server further determines consistency between the member type and the group type.

[0035] The group server may first create the group and set the consistency check flag of the group according to the consistency check result. If all members are reachable and checked, the consistency check flag may be set to "check completed"; if the consistency check of some members is uncompleted for reasons such as unreachability, the flag may be set to "check uncompleted".

[0036] The unreachable member may be first recorded and its consistency is checked after it is reachable.

[0037] 203. The group server returns a group creation response that carries the consistency check result to the requesting apparatus.

[0038] If the consistency check is uncompleted, the group server includes a "check uncompleted" flag in the group creation response to notify the M2M requesting apparatus. If the group consistency check is successful and the creation is successful, the group server may include a success flag in the group creation response.

[0039] An embodiment of the present invention provides another method for M2M group management. As shown in FIG. 3, the method includes the following steps:
301. Send a group creation request to a group server, where the group creation request carries a group type of a group requested to be created.

[0040] The group creation request carries the group type and optionally may carry a group identifier or group members or other information.

[0041] 302. Receive a returned group creation response, where the group creation response carries a result of a consistency check between member types of members in the group and the group type.

[0042] If the consistency check is uncompleted, the group server includes a "check uncompleted" flag in the group creation response to notify the M2M requesting apparatus. If the group consistency check is successful and the creation is successful, the group server may include a success flag in the group creation response.

[0043] The requesting apparatus may subscribe to the status of the group according to the received group creation response. After the status of the group changes on the group server, for example, after the consistency check is completed, the requesting apparatus may be notified.

[0044] As shown in FIG. 4, an embodiment of the present invention also provides a method for group management. In the embodiment, as an example, group 1 needs to be created. Group 1 includes subgroup members such as subgroup 2 and subgroup 3 and device members such as device 4 and device 5. A specific procedure of the method includes the following steps:
401. A requesting apparatus sends a group creation request message, requesting to create group 1.

[0045] Herein, the requesting apparatus may be an M2M device, an M2M gateway, or a service platform, and the group server may be a home service capability layer (Service Capability Layer, SCL) device of the group, and the service platform may be an M2M SCL (SCL, Service Capability Layer) device. For example, in the embodiment, group 1 requested to be created is homed to SCL device 1, which is group server 1, and subgroup 2 and subgroup 2 are homed respectively to SCL device 2 and SCL device 3, which are group server 2 and group server 3. The two device members of group 1: device 4 and device 5, are also homed to SCL device 1.

[0046] The group creation request carries the group type of the group requested to be created. The embodiment assumes this type is a non-hybrid type, such as an application type, which indicates that all group members should belong to a consistent type.

[0047] 402. After receiving the group creation request, group server 1 checks consistency between member types of members in the group and the group type.

[0048] After receiving the group creation request, the group server determines, according to the group type, whether consistency check is necessary. If the group type is hybrid, consistency check is unnecessary. The embodiment assumes that consistency check is necessary.

[0049] The group server obtains the member types of all members in a group member list. The types of local group members may be obtained directly for comparison. If the group includes a remote group member, the group server needs to obtain the member type of the member from the home device of the remote member.

[0050] Whether the group includes a remote group member may be determined according to the uniform resource identifier (Uniform Resource Identifier, URI) of the group. For example, in the embodiment, it is assumed that the domain names of group servers 1, 2, and 3 are gl.example.com, dl.example.com, and d2.example.com, respectively. The URI of group 1 is "coap://gl.example.com/groups/groupl", that of subgroup 2 is "coap://dl.example.com/groups/group2", and that of subgroup 3 is "coap://d2.example.com/groups/group3". This indicates that group 1 and subgroups 2 and 3 have different home devices and that subgroups 2 and 3 are remote group members of group 1.

[0051] In the embodiment, it is assumed that the two device members of group 1: device 4 and device 5, are local members, whose member types can be directly obtained for consistency check. Subgroup 2 and subgroup 3 are remote members. Herein, the embodiment assumes that subgroup 2 and subgroup 3 have not passed the member type consistency check because, group server 1, after sending access requests respectively to the home group server 2 and group server 3 of subgroup 2 and subgroup 3, receives no access response to the access requests after a specified period of time. The access requests may be requests to access the type attribute of the group.

[0052] 403. Group server 1 creates group 1 and sets one attribute of the group, the consistency check flag, to "check uncompleted" because the consistency check of subgroup 2 and subgroup 3 is not yet completed.

[0053] 404. Group server 1 returns a group creation response to the requesting apparatus.

[0054] The group creation response may carry the "consistency uncompleted" flag.

[0055] 405. Group server 1 subscribes to the online status of the unreachable member from the service platform.

[0056] For an unreachable member, group server 1 may send a subscription request to the service platform. In the embodiment, group server 1 subscribes to the online status of the home group server 2 and group server 3 of subgroup 2 and subgroup 3. Because group server 2 and group server 3 are already registered with the service platform, the platform may return a subscription success response after receiving the subscription request.

[0057] 406. The requesting apparatus subscribes to the status of the group.

[0058] After receiving the returned group creation response, the requesting apparatus may send a subscription request to group server 1 according to the "check uncompleted" flag carried in the response, requesting to subscribe to the status of group 1. Group server 1 may return a subscription success response after receiving the subscription request.

[0059] 407. When group server 3 is reachable, its online status registered with the service platform is changed and the service platform sends a notification message to the subscriber, that is, group server 1, notifying that "group server 3 is reachable".

[0060] 408. After receiving the notification message, group server 1 sends an access request to group server 3, requesting to obtain the group attributes of subgroup 3.

[0061] 409. Group server 1 receives an access response returned by group server 3, where the group type of subgroup 3 is carried.

[0062] 410. Group server 1 checks whether the group type of subgroup 3 is consistent with the group type of group 1, and if the types are inconsistent, as shown in FIG. 4, group server 1 deletes the created group 1.

[0063] 411. The group server 1 sends a notification message.

[0064] Because the requesting apparatus has subscribed to the status of group 1, group server 1 may notify the requesting apparatus that "group 1 is deleted due to inconsistency of the type of member 'subgroup'".

[0065] In the embodiment, by adding a consistency check flag in a group and notifying the requesting apparatus of the consistency check flag in a group creation response, the creation of the group does not fail because of type check, which greatly increases the flexibility of using the M2M technology.

[0066] As shown in FIG. 5, an embodiment of the present invention provides another method for group management. This embodiment is similar to the embodiment shown in FIG. 4. In this embodiment, as an example, group 1 also needs to be created. Group 1 includes subgroup members such as subgroup 2 and subgroup 3 and device members such as device 4 and device 5. A specific procedure of the method includes the following steps:

[0067] 501-509. The steps are the same as steps 401-409 in the embodiment shown in FIG. 4, that is, group server 1 receives a group creation request, creates a group, and returns a response. Group server 1 also subscribes to the online status of group server 2 and group server 3 from a service platform. After group server 3 is reachable, the group type of subgroup 3 is obtained.

[0068] 510. Group server 1 checks whether the group type of subgroup 3 is consistent with the group type of group 1. It is assumed that, as shown in FIG. 5, the types are consistent, but because group server 2 is unreachable, the group type of subgroup 2 is not obtained, and therefore, the consistency check flag of group 1 is still "uncompleted".

[0069] 511. When group server 2 is reachable, its resource online status registered with the service platform is changed and the service platform sends a notification message to the subscriber, i.e. group server 1, notifying that "group server 2 is reachable".

[0070] 512. After receiving the notification message, group server 1 sends an access request to group server 2, requesting to obtain the group attributes of subgroup 2.

[0071] 513. Group server 1 receives an access response returned by group server 2, where the group type of subgroup 2 is carried.

[0072] 514. Group server 1 checks whether the group type of subgroup 2 is consistent with the group type of group 1. It is assumed that, as shown in FIG. 5, the types are consistent. Then the consistency check of all members of group 1 is completed, and therefore, group server 1 sets the consistency check flag of group 1 to "completed". Herein, the member types of all members are consistent with the group type of the group.

[0073] 515. The group server 1 sends a notification message.

[0074] Because the requesting apparatus has subscribed to the status of group 1, group server 1 may notify the requesting apparatus that "consistency check of group 1 is completed".

[0075] In the embodiment, by adding a consistency check flag in a group and notifying the requesting apparatus of the consistency check flag in a group creation response, the creation of the group does not fail because of type check, which greatly increases the flexibility of using the M2M technology.

[0076] As shown in FIG. 6, an embodiment of the present invention provides another method for group management. This embodiment is similar to the embodiment shown in FIG. 4. In this embodiment, as an example, group 1 also needs to be created. Group 1 includes subgroup members such as subgroup 2 and subgroup 3 and device members such as device 4 and device 5. A specific procedure of the method includes the following steps:
601-609. The steps are the same as steps 401-409 in the embodiment shown in FIG. 4, that is, group server 1 receives a group creation request, creates a group, and returns a response. Group server 1 also subscribes to the online status of group server 2 and group server 3 from a service platform. After group server 3 is reachable, the group type of subgroup 3 is obtained.

[0077] 610. Group server 1 checks whether the group type of subgroup 3 is consistent with the group type of group 1. It is assumed that, as shown in FIG. 6, the types are inconsistent. Unlike that shown in FIG. 4, group server 1 determines the processing according to one "consistency policy". For example, group server 1 may directly delete a created group, which is the same as that shown in FIG. 4. Or, group server 1 may delete a member whose type is inconsistent with the group type from the created group; herein, for example, subgroup 3 is deleted from group 1. After the deletion, because group server 2 is unreachable, the group type of subgroup 2 cannot be obtained, and therefore, the consistency check of group 1 is "uncompleted".

[0078] The consistency policy may be configured on the group server or carried in the group creation request of the requesting apparatus, and after receiving the consistency policy, the group server applies the consistency policy to the group requested to be created. If the consistency policy is "deleting group", the group server deletes the group after determining that the type of one member in the group is inconsistent with the group type. If the consistency policy is "deleting member", the group server deletes the member of an inconsistent type from the group after determining that the type of one member in the group is inconsistent with the group type.

[0079] 611. The group server 1 sends a notification message. Because the requesting apparatus has subscribed to the status of group 1, group server 1 may notify the requesting apparatus that "the type of one member 'subgroup 3' of group 1 is inconsistent with the group type and the member is deleted from the group" and may also notify that the consistency check is still "uncompleted".

[0080] 612. When group server 2 is reachable, its resource online status registered with the service platform is changed and the service platform sends a notification message to the subscriber, that is, group server 1, notifying that "group server 2 is reachable".

[0081] 613. After receiving the notification message, group server 1 sends an access request to group server 2, requesting to obtain the group attributes of subgroup 2.

[0082] 614. Group server 1 receives an access response returned by group server 2, where the group type of subgroup 2 is carried.

[0083] 615. Group server 1 checks whether the group type of subgroup 2 is consistent with the group type of group 1. It is assumed that, as shown in FIG. 5, the types are consistent. Then the consistency check of all members of group 1 is completed, and therefore, group server 1 sets the consistency check flag of group 1 to "completed". Herein, the member types of all members are consistent with the group type of the group.

[0084] 616. The group server 1 sends a notification message.

[0085] Because the requesting apparatus has subscribed to the status of group 1, group server 1 may notify the requesting apparatus that the consistency check is "completed".

[0086] In the embodiment, by adding a consistency policy in a group, the flexibility of consistency processing in group creation is further improved, which increases the flexibility of using the M2M technology.

[0087] As shown in FIG. 7, an embodiment of the present invention provides another method for group management. In the embodiment, the type of a subgroup is also pending consistency check because a member of the subgroup is unreachable. This embodiment is similar to the foregoing embodiment. In this embodiment, as an example, group 1 needs to be created. Group 1 includes subgroup members such as subgroup 2 and subgroup 3 and device members such as device 4 and device 5. A specific procedure of the method includes the following steps:

[0088] 701. A requesting apparatus sends a group creation request message, requesting to create group 1.

[0089] Herein, the requesting apparatus may be an M2M device, an M2M gateway, or a service platform and the group server may be a home service capability layer (Service Capability Layer, SCL) device of the group, and the service platform may be an M2M SCL (SCL, Service Capability Layer) device. For example, in the embodiment, group 1 requested to be created is homed to SCL device 1, which is group server 1, and subgroup 2 and subgroup 2 are homed respectively to SCL device 2 and SCL device 3, which are group server 2 and group server 3. The two device members of group 1: device 4 and device 5, are also homed to SCL device 1.

[0090] The group creation request carries the group type of the group requested to be created. The embodiment assumes this type is a non-hybrid type, such as an application type, which indicates that all group members should belong to a consistent type.

[0091] 702. After receiving the group creation request, group server 1 checks consistency between member types of members in the group and the group type.

[0092] After receiving the group creation request, the group server determines, according to the group type, whether consistency check is necessary. If the group type is hybrid, consistency check is unneeded. The embodiment assumes that consistency check is needed.

[0093] The group server obtains the member types of all members in a group member list. The types of local group members may be obtained directly for comparison. If the group includes a remote group member, the group server needs to obtain the member type of the member from the home SCL device of the remote member.

[0094] In the embodiment, it is assumed that the two device members of group 1: device 4 and device 5, are local members, whose member type can be directly obtained for consistency check. Subgroup 2 and subgroup 3 are remote members and it is assumed that subgroup 2 and subgroup 3 have not passed the member type consistency check. Unlike the embodiment shown in FIG. 4, group server 1 sends access requests respectively to the home group server 2 and group server 3 of subgroup 2 and subgroup 3, requesting to obtain the type attribute of the subgroups, and then receives the access responses returned by subgroup 2 and subgroup 3, where the responses include parameters indicating that the consistency check of subgroup 2 and subgroup 3 is "uncompleted". A possible reason why the check of the subgroups is uncompleted is that some members in the subgroups are currently unreachable.

[0095] 703. Group server 1 creates group 1 and sets the consistency check flag of the group to "uncompleted" because the consistency check of subgroup 2 and subgroup 3 is not yet completed.

[0096] 704. Group server 1 returns a group creation response to the requesting apparatus.

[0097] The group creation response may carry the consistency check flag attribute of the group, which, in the embodiment, is "uncompleted".

[0098] 705. Group server 1 subscribes to the status of subgroups whose consistency check is uncompleted respectively from group server 2 and group server 3.

[0099] For a subgroup whose consistency check is uncompleted, group server 1 may send a subscription request to the home group server of the subgroup. In the embodiment, group server 1 subscribes to the status of subgroup 2 and subgroup 3 from group server 2 and group server 3 respectively.

[0100] 706. The requesting apparatus subscribes to the status of the group.

[0101] After receiving the returned group creation response, the requesting apparatus may send a subscription request to group server 1 according to the consistency check "uncompleted" flag carried in the response, requesting to subscribe to the status of group 1. After the status of group 1 changes, group server 1 may notify the requesting apparatus. Group server 1 may return a subscription success response after receiving the subscription request.

[0102] 707. Receive a notification message from group server 3.

[0103] After the consistency check of subgroup 3 is completed, for example, after the unreachable members of subgroup 3 are reachable, group server 3 may proceed according to the "consistency policy" of subgroup 3. Herein, it is assumed that subgroup 3 includes a member of an inconsistent type and that the "consistency policy" is "deleting member when inconsistent". Then, subgroup 3 deletes the inconsistent member from subgroup 3. After the deletion, the consistency check flag of subgroup 3 is "completed". Because group server 1 has subscribed to the status change of subgroup 3, group server 3 sends a notification message to the subscriber, that is, group server 1, notifying that "the consistency check of subgroup 3 is completed".

[0104] 708. Group server 1 checks whether the group type of subgroup 3 is consistent with the group type of group 1. In the embodiment, it is assumed that the types are inconsistent and that the "consistency policy" of group 1 is "deleting member when inconsistent". Then, group server 1 deletes subgroup 3 from group 1. After the deletion, because group server 2 has not yet completed consistency check, the consistency check of group 1 is still uncompleted.

[0105] 709. Receive a notification message from group server 2.

[0106] After the consistency check of subgroup 2 is completed, for example, after the unreachable members of subgroup 2 are reachable, group server 2 may proceed according to the "consistency policy" of subgroup 2. Herein, it is assumed that subgroup 2 includes a member of an inconsistent type and that the "consistency policy" is "deleting group when inconsistent". Then, group server 2 deletes subgroup 2 directly. Because group server 1 has subscribed to the status change of subgroup 2, group server 2 sends a notification message to the subscriber, ,that is, group server 1, notifying that "subgroup 2 is deleted".

[0107] 710. After receiving the notification that "subgroup 2 is deleted", group server 1 deletes subgroup 2 from group 1. Now the consistency check of all members of group 1 is completed, and therefore the consistency check flag of group 1 is set to "completed". Herein, the member types of all members are consistent with the group type of the group.

[0108] 711. The group server 1 sends a notification message.

[0109] Because the requesting apparatus has subscribed to the status of group 1, group server 1 may notify the requesting apparatus that the consistency check is "completed" and further notify that "subgroup 2 is deleted and subgroup 3 is deleted".

[0110] FIG. 8 is a schematic diagram of a group server for machine-to-machine communication according to an embodiment of the present invention. The group server includes:

a receiving unit 801, configured to receive a group creation request sent by a requesting apparatus, where the group creation request carries a group type of a group requested to be created;

a consistency check unit 802, configured to check consistency between member types of members in the group and the group type and set a consistency check flag of the group according to a consistency check result; and

a sending unit 803, configured to return a group creation response that carries the consistency check result to the requesting apparatus.



[0111] Optionally, the group server may further include a policy unit 804, configured to: when it is determined that the member type of one member in the group is inconsistent with the group type, delete the member that is inconsistent with the group type from the group or delete the group directly.

[0112] Optionally, attributes of the group include a consistency policy and the policy unit further determines, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete the created group when it is determined that the member type of the member in the group is inconsistent with the group type.

[0113] Optionally, the group server further includes a subscribing unit 805, configured to subscribe to an online status of a home device of an unreachable member from a service platform when the member in the group is determined to be unreachable, and when the online status changes, receive a notification message sent by the service platform; and the consistency check unit obtains the member type of the member after determining that the member is reachable and determines consistency between the member type of the member and the group type.

[0114] Optionally, the consistency check unit is specifically configured to: determine that a member of the group is a non-subgroup member and determine the member type according to a uniform resource identifier URI of the member; and determine consistency between the member type of the member and the group type after determining the member type.

[0115] Optionally, the group server further includes a subscribing unit, configured to: when it is determined that the consistency check of a subgroup member in the group is uncompleted, subscribe to the status of the subgroup from a home device of the subgroup and receive a status notification of the subgroup; and the consistency check unit determines the type of the subgroup according to the status notification and determines consistency between the type of the subgroup and the group type.

[0116] FIG. 9 is a schematic diagram of a requesting apparatus for machine-to-machine communication according to an embodiment of the present invention. The requesting apparatus includes:

a sending unit 901, configured to send a group creation request to a group server, where the group creation request carries a group type of a group requested to be created; and

a receiving unit 902, configured to receive a returned group creation response, where the group creation response carries a result of a consistency check between member types of members in the group and the group type.



[0117] Optionally, the requesting apparatus further includes a subscribing unit 903, configured to subscribe to the status of the group from the group server according to the group creation response.

[0118] FIG. 10 is another schematic structural diagram of a group server according to an embodiment of the present invention. The group server adopts a general computer system structure, where program codes that execute the solution of the present invention are stored in a memory and the execution is controlled by a processor. The group server includes a bus, a processor 1001, a memory 1002, and a communication interface 1003.

[0119] The bus may include a closed circuit that transfers information between different parts of the computer.

[0120] The processor may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the solution program of the present invention. The one or more memories included in the computer system may be a read-only memory (ROM) or other types of static memory devices able to store static information and instructions, or a random access memory (RAM) or other types of dynamic memory devices able to store information and instructions, or a magnetic disk storage. The memories are connected to the processor via the bus.

[0121] The communication interface may be any transceiver-like apparatus for communication with other devices or a communication network, such as an Ethernet, a radio access network (RAN), and a wireless local area network (WLAN).

[0122] The memory, such as a RAM, stores an operating system and a program executing the solution of the present invention. The operating system is a program that controls the operation of other programs and manages system resources. The program codes that execute the solution of the present invention are stored in the memory and the execution is controlled by the processor.

[0123] The program stored in the memory is used to instruct the processor to execute a method for group management during machine-to-machine communication, including:

receiving a group creation request sent by a requesting apparatus, where the group creation request carries a group type of a group requested to be created;

checking consistency between member types of members in the group and the group type and setting a consistency check flag of the group according to a consistency check result; and

returning a group creation response that carries the consistency check result to the requesting apparatus.



[0124] Optionally, the method further includes: determining that the member type of one member in the group is inconsistent with the group type; and deleting the member whose member type is inconsistent with the group type from the group or deleting the group directly.

[0125] Optionally, attributes of the group include a consistency policy and the method further includes determining, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete the created group when it is determined that the member type of the member in the group is inconsistent with the group type.

[0126] Optionally, the checking consistency between member types of members in the group and the group type specifically includes: determining that a member in the group is unreachable; subscribing to an online status of a home device of the unreachable member from a service platform, and when the online status changes, receiving a notification message sent by the service platform, or polling the home device of the unreachable member periodically until the unreachable member is reachable; after determining that the member is reachable, obtaining the member type of the member and determining consistency between the member type of the member and the group type.

[0127] Optionally, the checking consistency between member types of members in the group and the group type specifically includes: determining that a member in the group is a non-subgroup member and determining the member type according to a uniform resource identifier URI of the member; and after determining the member type of the member, determining consistency between the member type of the member and the group type.

[0128] Optionally, the checking consistency between member types of members in the group and the group type specifically includes: determining that the consistency check of a subgroup member in the group is uncompleted; subscribing to the status of a subgroup from a home device of the subgroup; receiving a status notification of the subgroup, determining the type of the subgroup according to the status notification, and determining consistency between the type of the subgroup and the group type.

[0129] FIG. 11 is another schematic structural diagram of a requesting apparatus according to an embodiment of the present invention. The requesting apparatus adopts a general computer system structure, where program codes that execute the solution of the present invention are stored in a memory and the execution is controlled by a processor. The requesting apparatus includes a bus, a processor 1101, a memory 1102, and a communication interface 1103.

[0130] The bus may include a closed circuit that transfers information between different parts of the computer.

[0131] The processor may be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the solution program of the present invention. The one or more memories included in the computer system may be a read-only memory (ROM) or other types of static memory devices able to store static information and instructions, or a random access memory (RAM) or other types of dynamic memory devices able to store information and instructions, or a magnetic disk storage. The memories are connected to the processor via the bus.

[0132] The communication interface may be any transceiver-like apparatus for communication with other devices or a communication network, such as an Ethernet, a radio access network (RAN), and a wireless local area network (WLAN).

[0133] The memory, such as a RAM, stores an operating system and a program executing the solution of the present invention. The operating system is a program that controls the operation of other programs and manages system resources. The program codes that execute the solution of the present invention are stored in the memory and the execution is controlled by the processor.

[0134] The program stored in the memory is used to instruct the processor to execute a method for group management during machine-to-machine communication, including:

sending a group creation request to a group server, where the group creation request carries a group type of a group requested to be created; and

receiving a returned group creation response, where the group creation response carries a result of a consistency check between member types of members in the group and the group type.



[0135] Optionally, the method further includes subscribing to the status of the group from the group server according to the group creation response.

[0136] Further embodiments of the present invention are provided in the following. It should be noted that the numbering used in the following section does not necessarily need to comply with the numbering used in the previous sections.

Embodiment 1. A method for group management during machine-to-machine communication, comprising:

receiving a group creation request sent by a requesting apparatus, wherein the group creation request carries a group type of a group requested to be created;

checking consistency between member types of members in the group and the group type and setting a consistency check flag of the group according to a consistency check result; and

returning a group creation response that carries the consistency check result to the requesting apparatus.

Embodiment 2. The method according to embodiment 1, further comprising:

determining that the member type of one member in the group is inconsistent with the group type; and

deleting the member whose member type is inconsistent with the group type from the group or deleting the group directly.

Embodiment 3. The method according to embodiment 1 or 2, wherein: attributes of the group comprise a consistency policy; and the method further comprises: when determining that the member type of the member in the group is inconsistent with the group type, determining, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete a created group.

Embodiment 4. The method according to any one of embodiments 1 to 3, wherein the step of checking consistency between member types of members in the group and the group type specifically comprises:

determining that a member in the group is unreachable;

subscribing to an online status of a home device of the unreachable member from a service platform, and when the online status changes, receiving a notification message sent by the service platform, or

polling the home device of the unreachable member periodically until the unreachable member is reachable; and

after determining that the member is reachable, obtaining the member type of the reachable member and determining consistency between the member type of the reachable member and the group type.

Embodiment 5. The method according to any one of embodiments 1 to 4, wherein the step of checking consistency between member types of members in the group and the group type specifically comprises:

determining that a member in the group is a non-subgroup member and determining a member type of the member according to a uniform resource identifier URI of the member; and

after determining the member type, determining consistency between the member type of the member and the group type.

Embodiment 6. The method according to any one of embodiments 1 to 5, wherein the step of checking consistency between member types of members in the group and the group type specifically comprises:

determining that the consistency check of a subgroup member in the group is uncompleted;

subscribing to a status of a subgroup from a home device of the subgroup; and

receiving a status notification of the subgroup, determining the type of the subgroup according to the status notification, and determining consistency between the type of the subgroup and the group type.

Embodiment 7. The method according to any one of embodiments 1 to 6, further comprising: when the group type is a non-hybrid type, checking consistency between the member types of the members in the group and the group type.

Embodiment 8. A method for group management during machine-to-machine communication, comprising:

sending a group creation request to a group server, wherein the group creation request carries a group type of a group requested to be created; and

receiving a returned group creation response, wherein the group creation response carries a result of a consistency check between member types of members in the group and the group type.

Embodiment 9. The method according to embodiment 8, further comprising:
subscribing to a status of the group from the group server according to the group creation response.

Embodiment 10. A group server for machine-to-machine communication, comprising:

a receiving unit, configured to receive a group creation request sent by a requesting apparatus, wherein the group creation request carries a group type of a group requested to be created;

a consistency check unit, configured to check consistency between member types of members in the group and the group type and set a consistency check flag of the group according to a consistency check result; and

a sending unit, configured to return a group creation response that carries the consistency check result to the requesting apparatus.

Embodiment 11. The group server according to embodiment 10, further comprising:
a policy unit, configured to: when it is determined that the member type of one member in the group is inconsistent with the group type, delete the member whose member type is inconsistent with the group type from the group or delete the group directly.

Embodiment 12. The group server according to embodiment 10 or 11, wherein: attributes of the group comprise a consistency policy; and the policy unit further determines, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete a created group when it is determined that the member type of the member in the group is inconsistent with the group type.

Embodiment 13. The group server according to any one of embodiments 10 to 12, wherein: the group server further comprises a subscribing unit, configured to subscribe to an online status of a home device of an unreachable member in the group from a service platform when the member is determined to be unreachable, and when the online status changes, receive a notification message sent by the service platform; and the consistency check unit obtains the member type of the member after determining that the member is reachable and determines consistency between the member type of the reachable member and the group type.

Embodiment 14. The group server according to any one of embodiments 10 to 13, wherein the consistency check unit is specifically configured to:

determine that a member in the group is a non-subgroup member and determine a member type of the member according to a uniform resource identifier URI of the member; and

after determining the member type, determine consistency between the member type of the member and the group type.

Embodiment 15. The group server according to any one of embodiments 10 to 14, wherein: the group server further comprises a subscribing unit, configured to: when it is determined that the consistency check of a subgroup member in the group is uncompleted, subscribe to a status of a subgroup from a home device of the subgroup and receive a status notification of the subgroup; and the consistency check unit determines the type of the subgroup according to the status notification and determines consistency between the type of the subgroup and the group type.

Embodiment 16. A requesting apparatus for machine-to-machine communication, comprising:

a sending unit, configured to send a group creation request to a group server, wherein the group creation request carries a group type of a group requested to be created; and

a receiving unit, configured to receive a returned group creation response, wherein the group creation response carries a result of a consistency check between member types of members in the group and the group type.

Embodiment 17. The requesting apparatus according to embodiment 16, further comprising:
a subscribing unit, configured to subscribe to a status of the group from the group server according to the group creation response.



[0137] It should be noted that the embodiments herein are described in a progressive manner, where the similar or identical parts between the embodiments can be obtained by reference and the stress of each embodiment is different. Particularly, in the case of apparatus embodiments, because they are similar to the method embodiments, the description is simple, where the function execution processes of the units may be obtained by reference to the related parts of the method embodiments. The foregoing apparatus embodiments are exemplary. The units described as separated parts may be physically separated or physically not separated. The parts illustrated as units may or may not be physical units. This means that the parts may be located in one location or distributed in multiple network elements. The purpose of the technical solution of the embodiments may be achieved through a portion of or all modules described herein depending on the practical needs. Persons of ordinary skill in the art will understand and implement the technical solution of the present invention without creative labor.

[0138] To sum up, the foregoing embodiments are only some preferred embodiments of the present invention and not intended to limit the protection scope of the present invention. The present invention is intended to cover all modifications, equivalent replacements, and improvements made to the present invention without departing from the principle of the present invention.


Claims

1. A method for group management during machine-to-machine communication, comprising:

receiving (201) a group creation request sent by a requesting apparatus, wherein the group creation request carries a group type of a group requested to be created;

checking (202) consistency between member types of members in the group and the group type;

determining that a member in the group is unreachable and setting a consistency check flag of the group to indicate the consistency check uncompleted;

creating the group and returning (203) a group creation response that carries the consistency check flag of the group to the requesting apparatus; and

after determining that the member is reachable, obtaining the member type of the reachable member and checking consistency between the member type of the reachable member and the group type.


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

determining that the member type of one member in the group is inconsistent with the group type; and

deleting the member whose member type is inconsistent with the group type from the group or deleting the group directly.


 
3. The method according to claim 1 or 2, wherein: attributes of the group comprise a consistency policy; and the method further comprises: when determining that the member type of the member in the group is inconsistent with the group type, determining, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete a created group.
 
4. The method according to any one of claims 1 to 3, further comprising:

subscribing to an online status of a home device of the unreachable member from a service platform, and when the online status changes, receiving a notification message sent by the service platform, or

polling the home device of the unreachable member periodically until the unreachable member is reachable.


 
5. The method according to any one of claims 1 to 4, wherein the step of checking consistency between member types of members in the group and the group type specifically comprises:

determining that a member in the group is a non-subgroup member and determining a member type of the member according to a uniform resource identifier URI of the member; and

after determining the member type, determining consistency between the member type of the member and the group type.


 
6. The method according to any one of claims 1 to 5, wherein the step of checking consistency between member types of members in the group and the group type specifically comprises:

determining that the consistency check of a subgroup member in the group is uncompleted;

subscribing to a status of a subgroup from a home device of the subgroup; and

receiving a status notification of the subgroup, determining the type of the subgroup according to the status notification, and determining consistency between the type of the subgroup and the group type.


 
7. The method according to any one of claims 1 to 6, further comprising: when the group type is a non-hybrid type, checking consistency between the member types of the members in the group and the group type.
 
8. A device for machine-to-machine communication, comprising:

a receiving unit (801), configured to receive a group creation request sent by a requesting apparatus, wherein the group creation request carries a group type of a group requested to be created;

a consistency check unit (802), configured to check consistency between member types of members in the group and the group type, determine that a member in the group is unreachable and set a consistency check flag of the group to indicate the consistency check uncompleted;

a sending unit (803), configured to create the group and return a group creation response that carries the consistency check flag of the group to the requesting apparatus; and

wherein the consistency check unit (802) further obtains the member type of the member after determining that the member is reachable and checks consistency between the member type of the reachable member and the group type.


 
9. The device according to claim 8, further comprising:
a policy unit (804), configured to: when it is determined that the member type of one member in the group is inconsistent with the group type, delete the member whose member type is inconsistent with the group type from the group or delete the group directly.
 
10. The device according to claim 8 or 9, wherein: attributes of the group comprise a consistency policy; and the policy unit (804) further determines, according to the consistency policy, whether to delete a member whose member type is inconsistent with the group type from the group or delete a created group when it is determined that the member type of the member in the group is inconsistent with the group type.
 
11. The device according to any one of claims 8 to 10, wherein: the device further comprises a subscribing unit (805), configured to subscribe to an online status of a home device of an unreachable member in the group from a service platform, and when the online status changes, receive a notification message sent by the service platform.
 
12. The device according to any one of claims 8 to 11, wherein the consistency check unit (802) is specifically configured to:

determine that a member in the group is a non-subgroup member and determine a member type of the member according to a uniform resource identifier URI of the member; and

after determining the member type, determine consistency between the member type of the member and the group type.


 
13. The device according to any one of claims 8 to 12, wherein: the device further comprises a subscribing unit (805), configured to: when it is determined that the consistency check of a subgroup member in the group is uncompleted, subscribe to a status of a subgroup from a home device of the subgroup and receive a status notification of the subgroup; and the consistency check unit determines the type of the subgroup according to the status notification and determines consistency between the type of the subgroup and the group type.
 
14. The device according to any one of claims 8 to 13, wherein when the group type is a non-hybrid type, the consistency check unit checks consistency between the member types of the members in the group and the group type.
 


Ansprüche

1. Verfahren zum Gruppenmanagement während einer Maschine-zu-Maschine-Kommunikation, umfassend:

Empfangen (201) einer Gruppenerzeugungsanforderung, die von einer anfordernden Vorrichtung gesendet wurde, wobei die Gruppenerzeugungsanforderung einen Gruppentyp einer Gruppe, deren Erzeugung angefordert wird, beinhaltet;

Prüfen (202) der Konsistenz zwischen Mitgliedstypen von Mitgliedern in der Gruppe und dem Gruppentyp;

Bestimmen, dass ein Mitglied in der Gruppe unerreichbar ist, und Setzen eines Konsistenzprüfungs-Flags der Gruppe zum Angeben, dass die Konsistenzprüfung unvollständig ist;

Erzeugen der Gruppe und Zurücksenden (203) einer Gruppenerzeugungsantwort, welche das Konsistenzprüfungs-Flag der Gruppe beinhaltet, an die anfordernde Vorrichtung; und

nach dem Bestimmen, dass das Mitglied erreichbar ist, Gewinnen des Mitgliedstyps des erreichbaren Mitglieds und Prüfen der Konsistenz zwischen dem Mitgliedstyp des erreichbaren Mitglieds und dem Gruppentyp.


 
2. Verfahren nach Anspruch 1, ferner umfassend:

Bestimmen, dass der Mitgliedstyp eines Mitglieds in der Gruppe mit dem Gruppentyp inkonsistent ist; und

Löschen des Mitglieds, dessen Mitgliedstyp mit dem Gruppentyp inkonsistent ist, aus der Gruppe, oder direktes Löschen der Gruppe.


 
3. Verfahren nach Anspruch 1 oder 2, wobei Attribute der Gruppe ein Konsistenz-Regelwerk umfassen und das Verfahren ferner Folgendes umfasst: wenn bestimmt wird, dass der Mitgliedstyp des Mitglieds in der Gruppe mit dem Gruppentyp inkonsistent ist, Bestimmen, gemäß dem Konsistenz-Regelwerk, ob ein Mitglied, dessen Mitgliedstyp mit dem Gruppentyp inkonsistent ist, aus der Gruppe zu löschen ist oder eine erzeugte Gruppe zu löschen ist.
 
4. Verfahren nach einem der Ansprüche 1 bis 3, ferner umfassend:

Abonnieren eines Online-Status eines Hausgerätes des unerreichbaren Mitglieds von einer Dienstplattform, und, wenn sich der Online-Status ändert, Empfangen einer von der Dienstplattform gesendeten Benachrichtigungsnachricht, oder

periodisches Abfragen des Hausgerätes des unerreichbaren Mitglieds, bis das unerreichbare Mitglied erreichbar ist.


 
5. Verfahren nach einem der Ansprüche 1 bis 4, wobei der Schritt des Prüfens der Konsistenz zwischen Mitgliedstypen von Mitgliedern in der Gruppe und dem Gruppentyp insbesondere Folgendes umfasst:

Bestimmen, dass ein Mitglied in der Gruppe ein Nicht-Untergruppenmitglied ist, und Bestimmen eines Mitgliedstyps des Mitglieds gemäß einem einheitlichen Bezeichner für Ressourcen (Uniform Resource Identifier, URI) des Mitglieds; und

nach dem Bestimmen des Mitgliedstyps, Bestimmen der Konsistenz zwischen dem Mitgliedstyp des Mitglieds und dem Gruppentyp.


 
6. Verfahren nach einem der Ansprüche 1 bis 5, wobei der Schritt des Prüfens der Konsistenz zwischen Mitgliedstypen von Mitgliedern in der Gruppe und dem Gruppentyp insbesondere Folgendes umfasst:

Bestimmen, dass die Konsistenzprüfung eines Untergruppenmitglieds in der Gruppe unvollständig ist;

Abonnieren eines Status einer Untergruppe von einem Hausgerät der Untergruppe; und

Empfangen einer Statusbenachrichtigung der Untergruppe, Bestimmen des Typs der Untergruppe gemäß der Statusbenachrichtigung und Bestimmen der Konsistenz zwischen dem Typ der Untergruppe und dem Gruppentyp.


 
7. Verfahren nach einem der Ansprüche 1 bis 6, ferner umfassend: wenn der Gruppentyp ein Nicht-Hybridtyp ist, Prüfen der Konsistenz zwischen den Mitgliedstypen der Mitglieder in der Gruppe und dem Gruppentyp.
 
8. Vorrichtung für eine Maschine-zu-Maschine-Kommunikation, umfassend:

eine Empfangseinheit (801), die dafür ausgelegt ist, eine Gruppenerzeugungsanforderung zu empfangen, die von einer anfordernden Vorrichtung gesendet wurde, wobei die Gruppenerzeugungsanforderung einen Gruppentyp einer Gruppe, deren Erzeugung angefordert wird, beinhaltet;

eine Konsistenzprüfungseinheit (802), die dafür ausgelegt ist, die Konsistenz zwischen Mitgliedstypen von Mitgliedern in der Gruppe und dem Gruppentyp zu prüfen, zu bestimmen, dass ein Mitglied in der Gruppe unerreichbar ist, und ein Konsistenzprüfungs-Flag der Gruppe auf zum Angeben, dass die Konsistenzprüfung unvollständig ist, zu setzen;

eine Sendeeinheit (803), die dafür ausgelegt ist, die Gruppe zu erzeugen und eine Gruppenerzeugungsantwort, welche das Konsistenzprüfungs-Flag der Gruppe beinhaltet, an die anfordernde Vorrichtung zurückzusenden; und

wobei die Konsistenzprüfungseinheit (802) nach dem Bestimmen, dass das Mitglied erreichbar ist, ferner den Mitgliedstyp des Mitglieds gewinnt und die Konsistenz zwischen dem Mitgliedstyp des erreichbaren Mitglieds und dem Gruppentyp prüft.


 
9. Vorrichtung nach Anspruch 8, ferner umfassend:
eine Regelwerkeinheit (804), die dafür ausgelegt ist, wenn bestimmt wird, dass der Mitgliedstyp eines Mitglieds in der Gruppe mit dem Gruppentyp inkonsistent ist, das Mitglied, dessen Mitgliedstyp mit dem Gruppentyp inkonsistent ist, aus der Gruppe zu löschen oder die Gruppe direkt zu löschen.
 
10. Vorrichtung nach Anspruch 8 oder 9, wobei: Attribute der Gruppe ein Konsistenz-Regelwerk umfassen; und die Regelwerkeinheit (804) ferner gemäß dem Konsistenz-Regelwerk bestimmt, ob ein Mitglied, dessen Mitgliedstyp mit dem Gruppentyp inkonsistent ist, aus der Gruppe zu löschen ist oder eine erzeugte Gruppe zu löschen ist, wenn bestimmt wird, dass der Mitgliedstyp des Mitglieds in der Gruppe mit dem Gruppentyp inkonsistent ist.
 
11. Vorrichtung nach einem der Ansprüche 8 bis 10, wobei: die Vorrichtung ferner eine Abonniereinheit (805) umfasst, die dafür ausgelegt ist, einen Online-Status eines Hausgerätes eines unerreichbaren Mitglieds in der Gruppe von einer Dienstplattform zu abonnieren, und, wenn sich der Online-Status ändert, eine von der Dienstplattform gesendete Benachrichtigungsnachricht zu empfangen.
 
12. Vorrichtung nach einem der Ansprüche 8 bis 11, wobei die Konsistenzprüfungseinheit (802) insbesondere dafür ausgelegt ist:

zu bestimmen, dass ein Mitglied in der Gruppe ein Nicht-Untergruppenmitglied ist, und einen Mitgliedstyp des Mitglieds gemäß einem einheitlichen Bezeichner für Ressourcen (Uniform Resource Identifier, URI) des Mitglieds zu bestimmen; und

nach dem Bestimmen des Mitgliedstyps, die Konsistenz zwischen dem Mitgliedstyp des Mitglieds und dem Gruppentyp zu bestimmen.


 
13. Vorrichtung nach einem der Ansprüche 8 bis 12, wobei: die Vorrichtung ferner eine Abonniereinheit (805) umfasst, die dafür ausgelegt ist, wenn bestimmt wird, dass die Konsistenzprüfung eines Untergruppenmitglieds in der Gruppe unvollständig ist, einen Status einer Untergruppe von einem Hausgerät der Untergruppe zu abonnieren und eine Statusbenachrichtigung der Untergruppe zu empfangen; und die Konsistenzprüfungseinheit den Typ der Untergruppe gemäß der Statusbenachrichtigung bestimmt und die Konsistenz zwischen dem Typ der Untergruppe und dem Gruppentyp bestimmt.
 
14. Vorrichtung nach einem der Ansprüche 8 bis 13, wobei, wenn der Gruppentyp ein Nicht-Hybridtyp ist, die Konsistenzprüfungseinheit die Konsistenz zwischen den Mitgliedstypen der Mitglieder in der Gruppe und dem Gruppentyp prüft.
 


Revendications

1. Procédé de gestion de groupe durant une communication de machine à machine, comprenant :

la réception (201) d'une requête de création de groupe envoyée par un appareil demandeur, dans lequel la requête de création de groupe comporte un type de groupe d'un groupe à créer ;

la vérification (202) de la cohérence entre les types de membres des membres du groupe et le type de groupe ;

la détermination qu'un membre du groupe n'est pas joignable et l'établissement d'un fanion de vérification de cohérence du groupe pour indiquer que la vérification de cohérence est non achevée ;

la création du groupe et le renvoi (203) à l'appareil demandeur d'une réponse de création de groupe qui comporte le fanion de vérification de cohérence du groupe ; et

après la détermination que le membre est joignable, l'obtention du type de membre du membre joignable et la vérification de la cohérence entre le type de membre du membre joignable et le type de groupe.


 
2. Procédé selon la revendication 1, comprenant en outre :

la détermination que le type de membre d'un membre du groupe est incohérent avec le type de groupe ; et

la suppression du groupe du membre dont le type de membre est incohérent avec le type de groupe ou la suppression du groupe directement.


 
3. Procédé selon la revendication 1 ou 2, dans lequel des attributs du groupe comprennent une stratégie de cohérence ; et le procédé comprend en outre : quand il est déterminé que le type de membre du membre du groupe est incohérent avec le type de groupe, la détermination, conformément à la stratégie de cohérence, s'il convient de supprimer du groupe un membre dont le type de membre est incohérent avec le type de groupe ou de supprimer un groupe créé.
 
4. Procédé selon l'une quelconque des revendications 1 à 3, comprenant en outre :
la souscription à un état en ligne d'un dispositif de rattachement du membre non joignable depuis une plate-forme de services, et quand l'état en ligne change, la réception d'un message de notification envoyé par la plate-forme de services, ou l'interrogation périodique du dispositif de rattachement du membre non joignable jusqu'à ce que le membre non joignable soit joignable .
 
5. Procédé selon l'une quelconque des revendications 1 à 4, dans lequel l'étape de vérification de la cohérence entre les types de membres des membres du groupe et le type de groupe comprend spécifiquement :

la détermination qu'un membre du groupe n'est pas un membre de sous-groupe et la détermination d'un type de membre du membre conformément à un identifiant de ressource uniforme URI du membre ; et

après la détermination du type de membre, la détermination de la cohérence entre le type de membre du membre et le type de groupe.


 
6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel l'étape de vérification de la cohérence entre les types de membres des membres du groupe et le type de groupe comprend spécifiquement :

la détermination que la vérification de cohérence d'un membre de sous-groupe dans le groupe est non achevée ;

la souscription à un état d'un sous-groupe à partir d'un dispositif de rattachement du sous-groupe ; et

la réception d'une notification d'état du sous-groupe, la détermination du type du sous-groupe conformément à la notification d'état, et la détermination de la cohérence entre le type du sous-groupe et le type de groupe.


 
7. Procédé selon l'une quelconque des revendications 1 à 6, comprenant en outre :
quand le type de groupe est un type non hybride, la vérification de la cohérence entre les types de membres des membres dans le groupe et le type de groupe.
 
8. Dispositif pour des communications de machine à machine, comprenant :

une unité de réception (801), configurée pour recevoir une requête de création de groupe envoyée par un appareil demandeur, dans lequel la requête de création de groupe comporte un type de groupe d'un groupe à créer ;

une unité de vérification de cohérence (802), configurée pour vérifier la cohérence entre les types de membres des membres du groupe et le type de groupe, déterminer qu'un membre du groupe n'est pas joignable et établir un fanion de vérification de cohérence du groupe pour indiquer que la vérification de cohérence est non achevée ;

une unité d'envoi (803), configurée pour créer le groupe et renvoyer à l'appareil demandeur une réponse de création de groupe qui comporte le fanion de vérification de cohérence du groupe ; et

l'unité de vérification de cohérence (802) obtenant en outre le type de membre du membre après la détermination que le membre est joignable et vérifiant la cohérence entre le type de membre du membre joignable et le type de groupe.


 
9. Dispositif selon la revendication 8, comprenant en outre :
une unité de stratégie (804), configurée pour : quand il est déterminé que le type de membre d'un membre du groupe est incohérent avec le type de groupe, supprimer du groupe le membre dont le type de membre est incohérent avec le type de groupe ou supprimer le groupe directement.
 
10. Dispositif selon la revendication 8 ou 9, dans lequel : des attributs du groupe comprennent une stratégie de cohérence ; et l'unité de stratégie (804) détermine en outre, conformément à la stratégie de cohérence, s'il convient de supprimer du groupe un membre dont le type de membre est incohérent avec le type de groupe ou de supprimer un groupe créé quand il est déterminé que le type de membre du membre du groupe est incohérent avec le type de groupe.
 
11. Dispositif selon l'une quelconque des revendications 8 à 10, dans lequel : le dispositif comprend en outre une unité de souscription (805), configurée pour souscrire à un état en ligne d'un dispositif de rattachement d'un membre non joignable dans le groupe depuis une plate-forme de services, et quand l'état en ligne change, recevoir un message de notification envoyé par la plate-forme de services.
 
12. Dispositif selon l'une quelconque des revendications 8 à 11, dans lequel l'unité de vérification de cohérence (802) est configurée spécifiquement pour :

déterminer qu'un membre du groupe n'est pas un membre de sous-groupe et déterminer un type de membre du membre conformément à un identifiant de ressource uniforme URI du membre ; et

après la détermination du type de membre, déterminer la cohérence entre le type de membre du membre et le type de groupe.


 
13. Dispositif selon l'une quelconque des revendications 8 à 12, dans lequel : le dispositif comprend en outre une unité de souscription (805), configurée pour : quand il est déterminé que la vérification de cohérence d'un membre de sous-groupe dans le groupe est non achevée, souscrire à un état d'un sous-groupe à partir d'un dispositif de rattachement du sous-groupe et recevoir une notification d'état du sous-groupe ; et l'unité de vérification de cohérence détermine le type du sous-groupe conformément à la notification d'état, et détermine la cohérence entre le type du sous-groupe et le type de groupe.
 
14. Dispositif selon l'une quelconque des revendications 8 à 13, dans lequel, quand le type de groupe est un type non hybride, l'unité de vérification de cohérence vérifie la cohérence entre les types de membres des membres dans le groupe et le type de groupe.
 




Drawing
























REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Non-patent literature cited in the description