KR20200046348A - Method and apparatus for performing group management in m2m system - Google Patents

Abstract

The present invention relates to a method for performing group management in a machine-to-machine (M2M) system. According to the present invention, a group management method may comprise the step of controlling group members included in a group based on a group resource.

Description

Method and device for performing group management in M2M system {METHOD AND APPARATUS FOR PERFORMING GROUP MANAGEMENT IN M2M SYSTEM}

The present invention relates to a method and apparatus for performing group management in a machine-to-machine (M2M) system. More specifically, it relates to a method and apparatus for managing devices in a group in an M2M system.

Recently, M2M (Machine-to-Machine) systems have been actively introduced. M2M communication may refer to a communication performed between a machine and a machine without human intervention. M2M may refer to Machine Type Communication (MTC), Internet of Things (IoT), or Device-to-Device (D2D). However, hereinafter, for convenience of description, it is referred to as M2M, but is not limited thereto. The terminal used for M2M communication may be an M2M device. The M2M terminal may be a device having low mobility while transmitting less data. At this time, the M2M terminal may be used in connection with an M2M server that centrally stores and manages communication information between machines.

Also, the M2M terminal can be applied in various systems such as object tracking, vehicle interlocking, and power metering.

Meanwhile, in relation to M2M terminals, the oneM2M standardization organization provides requirements for M2M communication, IoT, IoT technology, architecture, API specification, security solution, and interoperability. The specifications of the oneM2M standardization organization provide a framework to support various applications and services such as smart city, smart grid, connected car, home automation, security, and health.

In addition, the use of vehicles is increasing as an M2M terminal, and there is an increasing demand for vehicles to manage objects through groups, such as cluster driving.

An object of the present invention is to provide a method and apparatus for performing group management in an M2M system.

According to an embodiment of the present invention, it is directed to a method for performing group management in an M2M system. At this time, the group management method may include controlling group members included in the group based on the group resource.

According to the present disclosure, it is possible to provide a method and apparatus for performing group management in an M2M system.

The effects obtainable in the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those skilled in the art from the following description. will be.

1 is a diagram illustrating a hierarchical structure of an M2M system according to the present disclosure.
2 is a view showing a reference point according to the present disclosure.
3 is a diagram illustrating each node according to the present disclosure.
4 is a diagram showing a common service function according to the present disclosure.
5 is a diagram illustrating a method of performing group management in an M2M system.
FIG. 6 is a diagram illustrating group-related operations based on a location policy resource.
7 is a diagram illustrating a method of performing resource announcement.
8 is a diagram showing a device configuration of an M2M terminal according to the present disclosure.

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present disclosure pertains can easily carry out the embodiments. However, the present disclosure can be implemented in many different forms and is not limited to the embodiments described herein.

In the present disclosure, terms such as first and second are used only for the purpose of distinguishing one component from other components, and do not limit the order or importance of components, etc., unless otherwise specified. Accordingly, within the scope of the present disclosure, the first component in one embodiment may be referred to as the second component in other embodiments, and likewise the second component in one embodiment may be the first component in another embodiment It can also be called.

In the present disclosure, when a component is said to be "connected", "coupled" or "connected" with another component, this is not only a direct connection relationship, but also an indirect connection relationship in which another component exists in the middle. It may also include. Also, when a component is said to "include" or "have" another component, this means that other components may be further included instead of excluding other components unless specifically stated to the contrary. .

In the present disclosure, the components that are distinguished from each other are for clarifying each feature, and the components are not necessarily separated. That is, a plurality of components may be integrated to be composed of one hardware or software unit, or one component may be distributed to be composed of a plurality of hardware or software units. Accordingly, such integrated or distributed embodiments are included within the scope of the present disclosure, unless otherwise stated.

In the present disclosure, components described in various embodiments are not necessarily essential components, and some may be optional components. Accordingly, an embodiment comprised of a subset of components described in one embodiment is also included in the scope of the present disclosure. Also, embodiments that include other elements in addition to the elements described in various embodiments are included in the scope of the present disclosure.

In describing the embodiments of the present disclosure, when it is determined that a detailed description of a known configuration or function may obscure the subject matter of the present disclosure, detailed description thereof will be omitted. In the drawings, parts irrelevant to the description of the present disclosure are omitted, and similar reference numerals are used for similar parts.

In addition, this specification describes a network based on M2M communication, and operations performed in the M2M communication network may be performed in a process of controlling a network and transmitting data in a system that controls the communication network.

In addition, in this specification, the M2M terminal may be a terminal performing M2M communication, but may be a terminal operating in a wireless communication system in consideration of backward compatibility. That is, the M2M terminal may mean a terminal that can operate based on the M2M communication network, but is not limited to the M2M communication network. The M2M terminal may be able to operate based on other wireless communication networks, and is not limited to the above-described embodiment.

In addition, the M2M terminal may be fixed or mobile. Further, the M2M server refers to a server for M2M communication and may be a fixed station or a mobile station.

Also, in this specification, an entity may refer to hardware such as an M2M device, an M2M gateway, and an M2M server. Further, as an example, an entity may be used to refer to a software configuration in the hierarchical structure of the M2M system, and is not limited to the above-described embodiment.

In addition, as an example, the present invention is mainly described in the M2M system, but the present invention is not limited to the M2M system.

Further, the M2M server may be an M2M terminal or a server that communicates with another M2M server. In addition, the M2M gateway may serve as a connection point connecting the M2M terminal and the M2M server. For example, when the networks of the M2M terminal and the M2M server are different, they may be connected to each other through an M2M gateway. In this case, as an example, both the M2M gateway and the M2M server may be M2M terminals, and are not limited to the above-described embodiment.

1 is a view showing the hierarchical structure of the M2M system.

Referring to FIG. 1, a layered structure of an M2M system may include an application layer 110, a common service layer 120, and a network service layer 130. In this case, the application layer 110 may be a layer operating based on a specific application. For example, the application may be a vehicle tracking application, a remote blood sugar monitoring application, a power metering application, or a control application. That is, the application layer may be a layer for a specific application. In this case, the entity operating based on the application layer may be an application entity (AE).

The common service layer 120 may be a layer for a common service function. For example, the common service layer 120 is a layer for providing common services such as data management, device management, M2M service subscription management, location services, and the like. You can. For example, an entity operating based on the common service layer 120 may be a common service entity (CSE).

The network service layer 130 may provide services such as device management, location service, and device triggering to the common service layer 120. At this time, an entity operating based on the network layer 130 may be a network service entity (NSE).

2 is a view showing the M2M system structure.

Referring to FIG. 2, the M2M system structure may be divided into a field domain and an infrastructure domain. At this time, each entity in each domain may perform communication through a reference point. As an example, a reference point may indicate a communication flow between respective entities. In this case, referring to FIG. 2, an Mca reference point that is a reference point between AE and CSE, an Mcc reference point that is a reference point between different CSEs, and a Mcn reference point that is a reference point between CSE and NSEs may be set.

3 is a view showing the configuration of the M2M system structure.

Referring to FIG. 3, an infrastructure domain of a specific M2M service provider may provide a specific infrastructure node 310 (infrastructure node, IN). At this time, the CSE of IN can perform communication based on AE and Mca reference points of other infrastructure nodes. At this time, one IN may be set for each M2M service provider. That is, IN may be a node that performs communication with an M2M terminal of another infrastructure based on the infrastructure structure. Also, as an example, the concept of a node may be a logical entity or a software configuration.

Next, the application designated node (320, Application Dedicated Node, ADN) may include a node that includes at least one AE and does not include a CSE. At this time, the ADN may be set in the field domain. That is, the ADN may be a dedicated node for AE. For example, the ADN may be a node that is set in the M2M terminal in hardware. Further, the application service node (330, Application Service Node, ASN) may be a node including one CSE and at least one AE. The ASN can be set in the field domain. That is, it may be a node including AE and CSE. At this time, the ASN may be a node connected to IN. For example, the ASN may be a node that is configured in the M2M terminal in hardware.

Also, the middle node 340 (Middle Node, MN) may include a CSE, and may include zero or more AEs. At this time, the MN may be set in the field domain. The MN may be connected to another MN or IN based on a reference point. Also, as an example, the MN may be configured in the M2M gateway in hardware.

Further, as an example, the non-M2M terminal node 350 (Non-M2M device node, NoDN) may be a node that does not include M2M entities and performs M2M system management or collaboration.

4 is a diagram showing a common service function.

Referring to FIG. 4, common service functions may be provided. For example, common service functions include application and service layer management, communication management and delivery handling, data management and storage, and device management. , Discovery, Group Management, Location, Network Service Exposure / Service Execution and Triggering, Registration, Security, Service Billing and At least one function may be provided among service charging and accounting, service session management, and subscription / notification. At this time, M2M terminals may operate based on the common service function. In addition, the common service function may be possible in other embodiments, and is not limited to the above-described embodiments.

5 is a diagram illustrating a method of performing group management in an M2M system. As a result, FIG. 5 is a diagram illustrating a case where M2M terminals are managed as one group. In FIG. 5, the M2M terminal is illustrated based on the mobile device, but is not limited thereto. For example, the M2M terminal may be a mobile device, a vehicle, a home appliance, etc., and is not limited to the above-described embodiment.

In addition, as an example, in the M2M system, the M2M terminal is a low-power terminal, and multiple M2M terminals can coexist. Further, as an example, the M2M terminal is a vehicle, and may consider a cluster driving operation of the vehicle. That is, it is necessary to manage a plurality of M2M terminals as a group for efficient management of the M2M terminals.

Meanwhile, as an example, device management may be considered in relation to an M2M system. In this case, device management may refer to managing various device configurations and objects of devices in an M2M system. For example, information included in devices in the M2M system may be continuously updated, and may be operated in consideration of the presence or absence of a device in the M2M system. Also, as an example, device management may be considered to process events, notifications, and the like generated on devices.

Also, as an example, a resource may be used in an M2M system. In this case, the resource may mean a data structure that is addressed based on a unique address. For example, in an M2M system, M2M terminals may operate based on resources. In addition, in the M2M system, resources may have a tree structure, and may be managed and stored by a common service layer. Also, the lisso may be logically connected at each terminal. For example, the common service layer of the M2M terminal, M2M server, and M2M gateway may operate based on the above-described resource structure. Also, as an example, a resource may have an attribute. At this time, the attribute may define a specific operation for the resource. Further, the resource may have a child resource, and may operate based on the tree structure described above. For example, a container resource existing under the baseURL resource and the basaeURL resource may be defined. In addition, as an example, there may be a subscription resource related to subscription / notification and a discovery resource searching for a specific resource. In addition, other resources may exist and are not limited to the above-described embodiment.

For example, group resources may be defined, and group resources may be defined as shown in Table 1 below. That is, a group resource may be set in relation to an operation on members included in the group, which will be described in more detail below.

[Table 1]

In addition, as an example, the group attribute may be as shown in Table 2 below, and is not limited to the following examples.

[Table 2]

In addition, as an example, in addition to the above-described Table 2, group attributes as shown in Table 3 below may be further defined. More specifically, a resource for mobility for a group can be defined. For example, as an M2M system, a group resource may be defined for an M2M terminal or an M2M vehicle. In this case, the M2M terminal or the M2M vehicle may be a terminal having mobility. In addition, for example, a group resource may be defined for devices attached to a specific location among M2M terminals such as home appliances. As another example, M2M vehicles, M2M terminals, etc. may consider terminals operating at a constant speed (e.g. M2M terminal groups in the subway), and the following attributes may be defined as group mobility in consideration of the above. At this time, for example, the attributes for the following groups may be individually set, and are not limited to the above-described embodiment. For example, as a property for group mobility, information about a group for a member in a fixed position, other groups for the same moving speed, and a group having a different speed (other group) may be indicated. Same as That is, an attribute for group mobility may be defined, and specific contents may be set differently, and is not limited to the above-described embodiment.

[Table 3]

As another example, when a group includes a plurality of members, an instruction for a leader member may be required. For example, a group may include a plurality of members, and when the operation for the group members is indicated, the operation may be indicated based on the leader member. As another example, a terminal receiving information about a group from an external terminal is a leader member, and group members can share information based on the leader member.

That is, an instruction for a group member may be required in relation to a group resource, and based on this, a leader member may be defined as attribute information, and is not limited to the above-described embodiment.

[Table 4]

As another example, in relation to a group, a group may be set in consideration of a communication environment in which the group is set. For example, in order to deliver the same indication to group members, information may be transmitted only to members included in the group boundary, and information transmission may be difficult when the group boundary is out of range. Therefore, even if the ID is set as a group member, if communication is not possible, it may be meaningless to be included in the group member, so it may be necessary to check the group boundary. In addition, as an example, in the case of an M2M terminal or an M2M vehicle operating in an M2M system, since group members may be dynamically changed based on mobility, there is a need to check boundary information for the group. In this case, as an example, the criteria of the boundary may be a leader member. That is, members within a certain distance based on the leader member may have a valid boundary, and are not limited to the above-described embodiment.

That is, it is necessary to check the valid boundary (BoundaryValidated) of the group, for this purpose can be defined as shown in Table 5.

[Table 5]

As another example, there is a need to provide connection status information between a plurality of members in a group. For example, when operating based on a group, connection status information of each member may be required. That is, in performing the operation, it is necessary to operate only when the connection status is valid, and thus, information may be required for the connection status. As an example, in a group between vehicles, a connection state may have a great influence on stability, there is a need to check information on this, and attribute information on this may be defined, which may be defined as in Table 6 below. .

[Table 6]

FIG. 6 is a diagram illustrating group-related operations based on a location policy resource.

A location policy resource may be created in the M2M system. In this case, as an example, attributes for a location policy resource may be as shown in Table 7 below. In more detail, it is necessary to check the location of the M2M terminal in the M2M system, and a policy resource for location confirmation may be defined. At this time, specific attribute information for the location policy is defined, and based on this, the M2M terminal may acquire location information.

[Table 7]

In this case, as an example, “locationInformationType” may be defined among location policy attributes, which may be as shown in Table 8 below.

[Table 8]

At this time, as an example, locationInformationType may indicate a “Position fix” method of directly indicating longitude and latitude to indicate a physical location. That is, the physical location of the M2M terminal may be indicated. As another example, it may indicate whether to enter or leave a specific area. As an example, it may be important whether it is located in a specific area in relation to the operation of the M2M terminal, and this may be indicated through the above-described information.

In this case, as an example, a group event indication method may be further defined as locationInformationType. For example, in the case of an M2M vehicle as an M2M terminal, it may be controlled as a group. That is, it can operate based on the group resource. In this case, in the case of a group-controlled M2M terminal, a physical location may not be required. For example, a leader member may exist in a group. At this time, the leader member may be a subject that communicates with the outside and exchanges information. The group members can receive information from the leader member and perform operations as a group based on this. At this time, as an example, in the case of a leader member, a physical location may be indicated as described above. On the other hand, in the case of group members other than the leader member, only the relative position with the leader member can be instructed. That is, when the group is maintained, group members can perform a group-related operation only with relative position information with the leader member. Accordingly, a group event is defined as locationInformationType, and location information of group members can be indicated. At this time, the group members may only be directed to relative distance, relative speed and direction information from the leader member based on the group event. At this time, the group members may perform group operations based on the leader member based on the above-described information, and are not limited to the above-described embodiment.

As a specific example, referring to FIG. 6, an M2M vehicle operating in an M2M system may be considered. In this case, as an example, a group in which the first vehicle 610, the second vehicle 620, and the third vehicle 630 exist may be considered. However, this is only an example, and is not limited to the above-described embodiment. At this time, the second vehicle 620 may be a leader member in the group. In the above-described situation, since the first vehicle 610 and the third vehicle 630 operate based on a group, only information about the group may be needed. For example, the location information of the first vehicle 610 and the third vehicle 630 may be sufficient if only relative information is indicated compared to the second vehicle 620. Accordingly, relative distance information, relative speed information, and direction information with the second vehicle 620 may be indicated based on the group event described above. Through this, the first vehicle 610 and the third vehicle 630 may perform a defined operation within the group, and location information may be set differently in consideration of the specificity of the group, limited to the above-described embodiment Does not work.

As another example, access rights may be granted for each group with respect to access restrictions. As an example, the access authority may be controlled based on at least one of a time window, a location, and an IP address as follows. That is, conditions as shown in Table 9 below may be set as a criterion for granting access, and based on this, access to the M2M terminal may be controlled in the M2M system.

[Table 9]

At this time, as an example, in relation to access control, access may be controlled in groups as shown in Table 10 below. In more detail, access may be controlled to terminals included in the same group as an originator requesting authority for resources with the hosting CSE. In this case, as an example, in the M2M system, the terminals may be controlled based on the group operation as described above, and in this case, it is necessary to grant access only to terminals included in a specific group. For example, in the case of instructing group operation as a group resource, access control may be performed based on a group for security or other access control. That is, Table 10 may be added as “accesscontrolcontext” based on Table 9 described above, and is not limited to the above-described embodiment.

Table 10

7 is a diagram illustrating a method of performing resource announcement.

As described above, the resource may have a tree structure, and resources in the CSE may be searched based on resource search. In this case, as an example, the resource announcement (Resource Announcement) may mean a process of generating a resource (that is, the original resource) of a specific CSE in the form of an announced resource in another CSE. Through this, the remote CSE can know the existence of the original resource and access the original resource to use the service. Therefore, it is possible to easily check a desired resource through an announced resource without searching many CSEs in the resource search. In this case, as an example, in relation to the announced resource, not all information on the original resource in the CSE may be provided to the remote CSE. For example, information of a Mandatory Announced (MA) type may be information that is necessarily provided to a remote CSE. Also, as an example, there may be OA (Optional Announced) type information selectively notified according to the content of a specific attribute in the original resource. In addition, as an example, a type of information not provided by a remote CSE may be a type of Not Announced (NA).

In this case, as an example, the 'announcedAttribute' attribute may include OA type information provided to the remote CSE. Through this, the original resource can manage the announced resource. At this time, when the above-described information is changed, a procedure such as updating, releasing, and deleting of 'announcedAttribute' may be performed, and is not limited to the above-described embodiment.

In addition, as an example, the attributes for “announceTO” and “announcedAttribute” may be set in connection with the above-described announcement. For example, 'announceTO' and 'announcedAttribute' may be common attributes that can be used in various resource types. More specifically, when a specific resource is announced to a remote CSE, 'announceTO' of the original resource may include URL information for the announced resource. At this time, as an example, when there are multiple remote CSEs, URL information may exist in a list form, as described above. At this time, 'announceTO' may also be created, updated, canceled, and deleted based on the announcement. As an example, Create and Update sends a request message to the original-owning CSE after registration of the announced resource is completed (or updated), and the new CSE-ID or URI address is assigned to the 'announceTo' attribute. Can be added. In addition, the 'announcedAttribute' attribute may be a list of information on OAs provided to other CSEs within the original resource, and creation and update of the 'announcedAttribute' attribute are included in the announced resource. It can be performed when the changed OA type information is changed or registered.

More specifically, 'announceTo' and 'announcedAttribute' may be as shown in Table 11 below.

[Table 11]

In this case, as an example, group operations may be considered in relation to 'announceTo' and 'announcedAttribute'. For example, members in the same group may use the same group ID. In this case, as an example, for operation of vehicles in a group using the same group ID, a leader / non-reader vehicle (or terminal) may exist, and operation may be performed centering on the leader terminal. For example, the reader terminal receives external information, and the non-reader terminals may be configured to operate under the instruction of the reader terminal, as described above.

In this case, as an example, the resource announcement may be performed in group units. As an example, the operations of members included in a group may be often performed together based on group resources. In addition, the resource announcement may also consider cases where all members in the group are announced, and in this case, it may not be necessary to include the ID of each member in the 'announceTo'.

That is, it can be made to operate in consideration of the “announceTo” group ID. As another example, the group ID described above may be considered in the registration and update procedure. As a specific example, in the case where the original-owned CSE exists and a plurality of remote CSEs in the group exist, the original-owned CSE separately creates and updates an announcement resource with the plurality of remote CSEs, and based on this, individually The URL or CSE-ID could be stored in the “announceTo” attribute. However, considering the amount of information included in the URL list, the original-owned CSE performs an announcement resource creation / update procedure with a leader member in the group and a remote CSE, and when successful, stores the “Group ID” in “announceTo”. You can. That is, a group ID may be added as shown in Table 10 to Table 11 above.

As another example, the group ID may be used as described above in the case where the non-leader CSEs in the group can share information with the leader CSE or may be subject to the leader CSE operation. That is, if the original-owned CSE and the leader-terminal CSE successfully create an announcement resource, non-leader terminals in the group can also generate the original-owned CSE announcement resource in a certain way, and the above-described embodiment. It is not limited to.

Table 12

As another example, 'announcedAttribute' may determine MA, OA, and NA based on the original-owned CSE, and update the list for OA to store information, as described above. That is, the Mandatory Announced (MA) type that the original-owned CSE must provide, the Optional Announced (OA) type that is selectively notified according to the content of a specific attribute in the original resource, or the Not Notified (NA) type that is not notified for each remote CSE. It may also be possible to set it differently. At this time, for example, it may be possible to set the announcement resource differently according to the nature of the remote CSE. For example, based on the above-described group operation, when the remote CSE is a group leader CSE or a single CSE, or a remote CSE connected to a network end or a remote CSE not connected to a network end exists. Can be considered. In this case, the original-owned CSE may also have a different OA type for each remote CSE. That is, an attribute included in a resource announced in one remote CSE may not be included in a resource announced in another remote CSE. To this end, 'announcedAttribute' information managing the OA type may be generated and updated based on URL or ID information, and Table 9 described above may be changed as shown in Table 13 below.

[Table 13]

In addition, as an example, the definition of OA may be as shown in Table 14 below. That is, OA can also be defined based on each distinct CSE.

Table 14

As a specific example, referring to FIG. 7 (a), the requester 710 may instruct the original CSE 720 to update “announceTo” based on a certain condition. At this time, the original CSE 720 may instruct the remote CSE 730 to create an announced resource, and based on this, the remote CSE 730 may generate an announced resource.

On the other hand, in FIG. 7 (b), the requester 740 may instruct the original CSE 750 to update “announceTo” based on certain conditions. At this time, the original CSE 750 may instruct the group leader 760 to create an announcement resource based on the group ID, and based on this, the remote group leader 760 generates an announced leso can do. At this time, as described above, considering the amount of information included in the URL list, the original-owned CSE performs an announcement resource creation / update procedure with a leader member in the group and a remote CSE, and “announceTo” the “Group ID” upon success. It can be stored in ”. In addition, the group ID may be used as described above in the limited case that non-leader CSEs in a group may share information with the leader CSE or may be subject to the leader CSE operation. That is, if the original-owned CSE and the leader-terminal CSE successfully create an announcement resource, non-leader terminals in the group can also generate the original-owned CSE announcement resource in a certain way, and the above-described embodiment. It is not limited to.

8 is a view showing the configuration of an M2M terminal device according to the present disclosure.

The M2M terminal device 800 may include a processor 810 that controls the device and a transceiver 820 that transmits and receives wireless signals. At this time, the processor 810 may control the transceiver 820. Further, the M2M terminal device 800 may communicate with other M2M terminal devices 900. As an example, the above-described sender and receiver may each be the M2M terminal of FIG. 8. Another M2M terminal device 900 may also include a processor 910 and a transceiver 920, and may perform the same role. Also, the device of FIG. 8 may be another device. For example, it may be a device that performs communication, a device such as an automobile or a base station. That is, it refers to a device capable of performing communication, and is not limited to the above-described embodiment.

The above-described embodiments of the present invention can be implemented through various means. For example, embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.

The detailed description of preferred embodiments of the invention disclosed as described above has been provided to enable those skilled in the art to implement and practice the invention. Although described above with reference to preferred embodiments of the present invention, those skilled in the art variously modify and change the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You can understand that you can. Accordingly, the present invention is not intended to be limited to the embodiments presented herein, but to give the broadest scope consistent with the principles and novel features disclosed herein. In addition, although the preferred embodiments of the present specification have been illustrated and described above, the present specification is not limited to the specific embodiments described above, and the technical field to which the present invention pertains without departing from the gist of the present specification claimed in the claims In addition, various modifications can be implemented by those skilled in the art, and these modifications should not be individually understood from the technical idea or prospect of the present specification.

And in this specification, both object invention and method invention are described, and the description of both inventions can be applied supplementally as needed.

In addition, the present invention has been looked at focusing on the preferred embodiments. Those skilled in the art to which the present invention pertains will understand that the present invention can be implemented in a modified form without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments should be considered in terms of explanation, not limitation. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the equivalent range should be interpreted as being included in the present invention.

M2M terminal: 800 Processor: 810
Transceiver: 820 M2M terminal: 800
Processor: 810 Transceiver: 820?

Claims (1)

In the method of performing group management in the M2M system,
And controlling group members included in the group based on the crop resource.

Images