KR101438358B1 - Method for Providing Machine to Machine Overlay Network, System, Server And Gateway Therefor - Google Patents

Abstract

A method for providing an M2M overlay network and a system, a server and a gateway for the same are disclosed.
M2M overlay network is formed to reduce overhead in resource processing due to device movement for M2M communication, distribute traffic generated from multiple devices, enable quick processing of real time events, Servers and gateways for providing M2M overlay networks to support wireless roaming.

Description

METHOD FOR PROVIDING M2M OVERLAY NETWORK, SYSTEM, SERVER AND GATEWAY FOR THE SAME,

The present embodiment relates to a method of providing an M2M overlay network and a system, a server and a gateway therefor. More specifically, it forms an M2M overlay network to reduce overhead in resource processing according to movement of a device for M2M communication, to distribute traffic generated from a plurality of devices, to enable rapid processing of real time events And a system, a server and a gateway for the M2M overlay network providing method for supporting roaming of a device.

The contents described in this section merely provide background information on the present embodiment and do not constitute the prior art.

Although the object intelligence communication is defined somewhat differently internationally, the terms are generally defined as M2M (Machine to Machine, ETSI), Internet of Things (ITU-T), MTC (Machine Type Communications, 3GPP) About such intelligent communications The Korea Communications Standards Commission (KCC) is a service that intelligently collects, processes, processes and transmits information through telecommunication, broadcasting, and internet infrastructures, '. The meaning of the agreement means communication between machines and between devices and machines in which people operate. In a broad sense, it means that all the infrastructure, systems, terminals, etc. that can confirm the information of objects at remote places by combining communication and ICT technology Means solution.

Mobile office, home service, health service, vehicle service, settlement, logistics management, security, etc. are attracting attention as the main application fields of the intelligent communication, and it is possible to create new business model through convergence with other industries Do. This kind of intelligent communication is a major policy for fostering new growth engines of each country together with Smart Grid, Cloud Computing and Smart Work around the world. In other words, major governments and global corporations are rushing to build aggressive investment and service development infrastructure. In particular, they are applying the intelligent communication technology and services to green IT, telematics, location-based services, remote meter reading and logistics management.

Meanwhile, some of the intelligent communication services provided in Korea include card settleters, traffic systems, remote meter reading, smart grids, and weather control systems. In addition, various services for intelligent automobiles are being developed through convergence with the automobile industry. As the convergence service based on the object intelligence communication is diversified, it is necessary to develop a platform for providing the optimal service for the M2M communication between the object (device) and the object (device). In addition, although standardization is currently being promoted through domestic and overseas standards organizations, standardization is proceeding centering on the structure and function of the object intelligence communication platform for new services rather than interworking between existing object intelligence communication platforms.

Recently, according to this trend, M2M communication also requires an overlay network.

This embodiment forms an M2M overlay network to reduce overhead in resource processing according to the movement of a device for M2M communication, to distribute traffic generated in a plurality of devices, to enable rapid processing of real time events , A method for providing an M2M overlay network for roaming support of a device, and a system, a server and a gateway for the main purpose.

According to an aspect of the present invention, an MSBC (M2M Service Bootstrapping and Connection) procedure is performed between a server and a gateway, a service capability layer (SCL) is registered, and a neighboring gateway list A discovery procedure for constructing a resource tree based on the neighbor gateway list; And a Network Organization Procedure for performing Mutual Trusted Relationship Handshaking, Mutual Announcement procedure, and Mutual Sharing between each of the gateways and the adjacent gateways of the neighbor gateway list, The method of providing an M2M overlay network according to an embodiment of the present invention will now be described.

According to an aspect of the present invention, an MSBC procedure is performed between a server and a gateway, a service capability layer is registered, a neighboring gateway list for the gateway is calculated, and a resource tree is constructed based on the neighboring gateway list. process; A network organization process for performing a mutual trust relationship, a mutual declaration procedure, and a resource information sharing between each of the gateways and adjacent gateways of the neighbor gateway list; A first device application participating process of performing a device registration procedure between the device and the gateway and updating the location information of the device in the gateway; And a second device application participating step of, when the device moves, renewing the resource tree in a new gateway.

According to an aspect of the present invention, an MSBC procedure is performed between a server and a gateway, a service capability layer is registered, a neighboring gateway list for the gateway is calculated, and a resource tree is constructed based on the neighboring gateway list. process; A network organization process for performing a mutual trust relationship, a mutual declaration procedure, and a resource information sharing between each of the gateways and adjacent gateways of the neighbor gateway list; A first device for registering the service capability layer after performing the MSBC procedure between the server and the device, calculating a device neighbor gateway list for the device, and constructing a resource tree based on the device neighbor gateway list, Participation in Service Capability Layer; And a second device service capability layer participation step of performing the mutual trust relationship, the mutual declaration procedure, and the resource information sharing between the moved device and each new neighboring gateway in the device neighboring gateway list. To provide an M2M overlay network providing method.
According to an aspect of the present invention, there is provided a method for managing a gateway, the method comprising: a server for registering a service capability layer after performing an MSBC procedure with a gateway, calculating and transmitting a neighbor gateway list for the gateway; And a gateway group for constructing a resource tree based on the received neighboring gateway list and performing mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list. And provides an overlay network providing system.
According to an aspect of the present invention, there is provided a method for managing a gateway, the method comprising: a server for registering a service capability layer after performing an MSBC procedure with a gateway, calculating and transmitting a neighbor gateway list for the gateway; Constructing a resource tree based on the received neighboring gateway list, performing a mutual trust relationship, a mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list, performing a device and a device registration procedure, And a gateway group for updating the location information of the device and updating the resource tree using a new gateway when moving the device.
According to an aspect of the present invention, there is provided a method for managing a gateway, the method comprising: a server for registering a service capability layer after performing an MSBC procedure with a gateway, calculating and transmitting a neighbor gateway list for the gateway; And a gateway group for constructing a resource tree based on the received neighboring gateway list and performing mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list, And registers the service capability layer after performing the MSBC procedure with the device, calculates a device neighbor gateway list for the device, and transmits the device neighbor gateway list to the device, and the device transmits, to the device, And the mutual trust relationship, the mutual declaration procedure, and the resource information sharing are performed between the moved device and each new neighboring gateway in the device neighboring gateway list. Overlay network provides a delivery system.
According to an aspect of the present invention, an NSCL (Network Service Capability Layer) for registering a service capability layer after performing an MSBC procedure with a gateway, calculating a neighbor gateway list for the gateway and transmitting the list to the gateway; And an NA (Network Application) for performing intra-device communication.
According to an aspect of the present invention, a service capability layer is registered after performing an MSBC procedure with a server, a resource tree is constructed based on a list of neighboring gateways received from the server, and each neighboring gateway A mutual trust relationship, a mutual declaration procedure, and resource information sharing, performs a device and device registration procedure, updates location information on the device, and performs GSCL (Gateway Service Capability Layer); And a Gateway Application (GA) for performing intra-gateway communication).

According to the present embodiment, an M2M overlay network is formed to reduce an overhead in resource processing according to movement of a device for M2M communication, to distribute traffic generated in a plurality of devices, And it is possible to support roaming of the device.

1 is a block diagram schematically showing an M2M overlay network system according to the present embodiment,
2 is a block diagram schematically showing a device, a gateway and a server according to the present embodiment,
3 is a flowchart illustrating a method of providing an M2M overlay network using a DA according to an embodiment of the present invention.
4 is a flowchart for explaining a discovery process according to the present embodiment,
FIG. 5 is a flowchart illustrating a network organization process according to the present embodiment.
6 is a flowchart for explaining a device application participating process according to the present embodiment,
FIG. 7 is a flowchart illustrating a method of providing an M2M overlay network using DSCL according to an embodiment of the present invention.
FIG. 8 is a flowchart illustrating a process of joining a device service capability layer according to the present embodiment.
9 is an exemplary view showing a resource tree at the application level in the discovery process according to the present embodiment,
10 is an exemplary view of a newly defined resource tree in the discovery process according to the present embodiment,
11 is an exemplary diagram illustrating a related resource tree in the network organization process according to the present embodiment,
12 is an exemplary view of a vehicle accident scene where the M2M overlay network according to the present embodiment is applied.

Hereinafter, the present embodiment will be described in detail with reference to the accompanying drawings.

The mId, dId, mIa, dIa, etc. described in the present embodiment are defined in the standard document ETSI TS 102 690 V2.0.3 and accordingly, the meanings for the terms described in this embodiment are defined as follows.

(M2M Network Interface Device) refers to the interface between the M2M network and the device, dId (Device Interface Device) refers to the interface between the device and the device, and mIa (M2M Network Interface Application) refers to the M2M network Means a server as a physical device) and an application-to-application interface, and dIa (Device Interface Application) means an interface between a device and an application. In addition, Gateway Interworking Proxy (GIP) means a gateway interworking proxy, NIP (Network Interworking Proxy) means a server interworking proxy, and DIP (Device Interworking Proxy) means a interworking proxy of devices.

Meanwhile, DA (Device Application) means a device application for M2M communication, and DAs means a plurality of DAs. The NA (Network Application) means a network application (an application at a server terminal) for M2M communication, and the GA (Gateway Application) means a gateway application for M2M communication. Also, GSCL (Gateway Service Capability Layer) means a set of gateway capabilities for M2M service, and GSCLs means a plurality of GSCLs. The NSCL (Network Service Capability Layer) means a set of network (server side) capabilities for M2M service, and the DSCL (Device Service Capability Layer) means a set of device capabilities for M2M service.

Meanwhile, the M2M overlay network described in this embodiment refers to another network formed on the basis of the existing M2M network (infrastructure). That is, it is a virtual network formed by configuring separate nodes (Nodes) and logical links on the existing M2M network. In an M2M overlay network, neighbor nodes are logical neighbor nodes, not physical neighbor nodes. As a result, it is possible to provide more efficient M2M network service by utilizing existing M2M network. In other words, an M2M overlay network can reconfigure a logical topology by another need on top of existing physical or logical topology, thereby improving the performance of M2M communication, And the like.

The M2M overlay network shares resources among the objects forming the M2M overlay network, and all devices serve as both a server and a client. When peers existing on the physical network register with the M2M service, A M2M overlay network is formed. Here, an object is a concept including all devices that perform M2M communication. Also, peers on the M2M overlay network can share and exchange information directly with other peers without the help of a server.

1 is a block diagram schematically showing an M2M overlay network system according to the present embodiment.

The M2M overlay network system according to the present embodiment includes a device 110, a gateway 120 and a server 130. In this embodiment, the M2M overlay network system includes only the device 110, the device 112, the gateway group 120, and the server 130. However, Those skilled in the art will appreciate that various modifications and changes may be made to the elements included in the M2M overlay network system without departing from the essential characteristics of the present embodiment.

The device 110 refers to all terminals or function modules for transmitting and receiving various data for M2M communication. That is, the device 110 refers to a device having a memory for storing a program or protocol for communicating with the gateway group 120 for M2M communication, and a module for executing and controlling the corresponding program. The device `112` refers to a terminal equipped with a DSCL and a DA for M2M communication, and drives a DSCL or DA installed for M2M communication. Device `112 refers to all terminals or function modules for transmitting and receiving various data for M2M communication. The device `112` means a device for communicating with the gateway group 120 for M2M communication, a memory for storing a protocol, and a module for executing and controlling the corresponding program. The device 110 refers to a terminal equipped with a DA for M2M communication, drives a DA installed for M2M communication, and communicates with the GSCL through a dIa interface. On the other hand, the device `112 is driven by mounting only DA.

The gateway group 120 is a network point serving as an entrance for entering another network for M2M communication. The gateway group 120 is a group including a plurality of gateways. In this embodiment, the first gateway 122, the second gateway 124, the third gateway 126, and the Nth gateway 128 .

The server 130 has the same hardware configuration as a typical server. However, in software, it may include a program module implemented in any language such as C, C ++, Java, Visual Basic, and Visual C. The server 130 may be implemented in the form of a conventional server. For example, the server 130 is generally connected to an unspecified number of clients and / or other servers via an open computer network such as the Internet, receives requests for work performed by clients or other servers, Computer system and computer software installed for it.

Hereinafter, the operation of the device 110, the gateway 120, and the server 130 according to the present embodiment will be described. (M2S Service Bootstrapping and Connection) procedure between the server 130 and the gateway group 120 and registers a service capability layer (SCL: Service Capability Layer) between the server 130 and the gateway group 120. In the gateway group 120, And constructs a resource tree based on the neighbor gateway list. The gateway group 120 performs Mutual Trusted Relationship Handshaking, Mutual Announcement procedure, and Mutual Sharing between each neighboring gateway in the neighbor gateway list. And then performs a device registration procedure between the device 112 and the second gateway 124 of the gateway group 120 and updates the location information of the device 112 in the second gateway 124. When the device 112 is moved, the third gateway 126, which is a new gateway, updates the resource tree.

Meanwhile, an MSBC procedure is performed between the server 130 and the gateway group 120, a service capability layer is registered, a neighboring gateway list is calculated in the gateway group 120, and a resource tree is constructed based on the neighboring gateway list . The gateway group 120 performs a mutual trust relationship, mutual declaration procedure, and resource information sharing among respective adjacent gateways in the neighbor gateway list. Performs an MSBC procedure between the server 130 and the device 110, registers a service capability layer, calculates a device neighbor gateway list for the device 110, and builds a resource tree based on the device neighbor gateway list. Mutual trust relationship, mutual declaration procedure, and resource information sharing are performed between the device 110 and each new neighboring gateway in the device neighboring gateway list.

Hereinafter, the discovery procedure of the M2M overlay network performed between the gateway group 120 and the server 130 according to the present embodiment will be described. Performs an MSBC procedure between the gateway group 120 and the server 130, and registers the service capability layer. That is, the GSCL # 1 to GSCL # N of the first to Nth gateways 128 to 128 included in the gateway group 120 and the NSCL # 1 of the server 130 mutually perform an MSBC procedure And registers the service capability layer. Then, the server 130 calculates a neighboring gateway list in the gateway group 120. The NSCL # 1 of the server 130 is connected to the gateway group 120 based on the location information received from the GSCL of the specific gateway in the gateway group 120, 1 to GSCL # N of the first to Nth gateways 128 to 128, which are the respective gateways in the first to eighth gateways 122 to 128, respectively. The server 130 transmits the neighbor gateway list to the gateway group 120. That is, the NSCL # 1 of the server 130 transmits the adjacent GSCL lists for the registered GSCL # 1 to GSCL # N to the GSCL # 1 to GSCL # N of the gateway group 120. Thereafter, a resource tree is constructed based on the neighbor gateway list received from the gateway group 120. That is, GSCL # 1 to GSCL # N of the gateway group 120 construct a resource tree based on the received neighbor GSCL list.

Hereinafter, a network organization procedure of the M2M overlay network between the gateway group 120 and the server 130 according to the present embodiment will be described. Establishes a mutual trust relationship with each neighboring gateway in the neighboring gateway list in the gateway group 120. That is, GSCL # 1 to GSCL # N of the gateway group 120 establish a mutual trust relationship between GSCLs of respective adjacent gateways in the neighbor gateway list. Next, the first gateway 122 to the Nth gateway 128 perform the service capability layer registration procedure without further authentication between the gateway and the neighboring gateway in which the mutual trust relationship is established. That is, between the first gateway 122 to the Nth gateway 128, a service capability layer registration procedure is performed without further authentication between the GSCL of the gateway in which the mutual trust relationship is established and the GSCL of the neighboring gateway, Resource creation and interesting resources. Thereafter, the first gateway 122 to the Nth gateway 128 perform a mutual declaration procedure for the resource of the registered device between the gateway registered with the service capability layer and the neighboring gateway. That is, the first gateway 122 to the Nth gateway 128 perform the mutual declaration procedure for the resources of the devices registered between the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway, Perform the subscription procedure for. Next, the first gateway 122 to the Nth gateway 128 perform the related resource creation and the interested resource subscription procedure for the devices that are mutually declared in the gateway and the gateway in which the service capability layer is registered. That is, the first gateway 122 to the Nth gateway 128 perform the related resource creation and the interested resource subscription procedure for the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighbor gateway, respectively. Then, the first gateway 122 to the Nth gateway 128 mutually share the related resources and the interested resources between the gateway to which the service capability layer is registered and the neighbor gateway. That is, the GSCL of the gateway to which the service capability layer is registered in the first gateway 122 to the Nth gateway 128 and the GSCL of the neighboring gateway share mutually related resources and resources of interest.

Hereinafter, a device application participation procedure (DA Join Procedure) of the M2M overlay network between the device 112, the gateway group 120, and the server 130 according to the present embodiment will be described. (112) between the device `112` and the second gateway (124) of the gateway group (120). That is, the registration procedure for the device 112 is performed between the DA # 1 of the device 112 and the GSCL # 2 of the second gateway 124. Thereafter, the second gateway 124 generates related resources for the registered device 112, and the first gateway 122, the third gateway 126, the Nth gateway 128, and the server 130). ≪ / RTI > That is, the GSCL # 2 of the second gateway 124 is connected to the GSCL # 1, the GSCL # 3 to the GSCL # N of the first gateway 122, the third gateway 126 to the Nth gateway 128 which are the adjacent gateways, (112) registered with the NSCL # 1 of the network device (130). Next, the second gateway 124 receives the neighbor gateway list from the first gateway 122, the third gateway 126, and the Nth gateway 128, which are the adjacent gateways. The second gateway 124 updates the location information of the device 112 and transmits the roaming information based on the location and coverage information of the first gateway 122, the third gateway 126 to the Nth gateway 128, And performs a fast handover by predicting a roaming area. That is, the GSCL # 2 of the second gateway 124 is adjacent to the GSCL # 1, GSCL # 3 to GSCL # N of the first gateway 122, the third gateway 126 to the Nth gateway 128, And receives a gateway list. The second gateway 124 updates the location information of the device 112 and transmits the location information of the first gateway 122, the third gateway 126 to the Nth gateway 128 to the GSCL # 1, the GSCL # And performs a fast handover by predicting the roaming area based on the location and coverage information for GSCL # N.

Then, the third gateway 126, which is a new gateway, performs the registration procedure for the device 112 due to the movement of the device 112. That is, the DA of the device `112 performs the registration procedure for the device` 112 with the GSCL # 3 of the third gateway 126 as a new gateway. The third gateway 126, which is a new gateway, updates the resources related to the device 112 in the resource tree. That is, the GSCL # 3 of the third gateway 126, which is a new gateway, updates the resources related to the device 112 in the resource tree. The information of the device 112 is transmitted from the third gateway 126 as a new gateway to the server 130 and the first gateway 122, the second gateway 126 or the Nth gateway 128, which are the adjacent gateways. do. Here, the neighboring gateways of the third gateway 126 may be the second gateway 126 and the Nth gateway 128, but FIG. 1 is merely illustrative of the technical idea of the present embodiment, 122 and the third gateway 126 are within a predetermined distance from each other, the third gateway 126 may recognize the first gateway as a neighboring gateway. That is, GSCL # 3 of the third gateway 126, which is a new gateway, transmits information about the device 112 to the NSCL # 1 of the server 130 and GSCL # 1 of the first gateway 122 which is the adjacent gateway, To the GSCL # 2 of the gateway 124 or to the GSCL # N of the Nth gateway 128. [

Hereinafter, a DSCL Join Procedure of the device service capability layer of the M2M overlay network between the device 110, the gateway group 120, and the server 130 according to the present embodiment will be described. Performs an MSBC procedure between the device 110 and the server 130, and registers a service capability layer. That is, the DSCL # 1 of the device 110 and the NSCL # 1 of the server 130 perform mutual MSBC procedures and register a service capability layer. Thereafter, the server 130 calculates a neighbor gateway list for the gateway group 120. That is, the NSCL # 1 of the server 130 calculates the device neighbor GSCL list for the DSCL # 1 of each device 110 based on the location information received from the DSCL # 1 of the mutually authenticated device 110 . Next, the server 130 transmits the list of neighboring gateways to the device 110. That is, the NSCL # 1 of the server 130 transmits the device neighbor GSCL list for each registered DSCL # 1 to the DSCL # 1 of the device 110. And constructs a resource tree based on the neighbor gateway list received from the device 110. That is, the DSCL # 1 of the device 110 constructs a resource tree based on the received device neighbor GSCL list.

Thereafter, a mutual trust relationship is established between the device 110 and each device neighboring gateway in the device neighbor gateway list. That is, DSCL # 1 of the device 110 establishes a mutual trust relationship between GSCLs of device neighboring gateways in the device neighboring gateway list. The service capability layer registration procedure is performed without further authentication between the device 110 in which the mutual trust relationship is established and the device adjacent gateway. That is, the service capability layer registration procedure is performed between the DSCL of the device in which the mutual trust relationship is established and the GSCL of each device adjacent gateway in the device neighbor gateway list without additional authentication, and resource creation and mutual interest resources To perform the subscription procedure. The mutual service capability layer performs the mutual declaration procedure for the resource of the device registered between the device 110 registered with the inter-serviceability layer and the device neighboring gateway. That is, the DSCL of the device to which the service capability layer is registered and the GSCL of the device neighboring gateways of the device neighbor gateway list are subjected to the mutual declaration procedure for resources of the devices registered in the device neighbor gateway list, .

And performs related resource creation and interested resource subscription procedures for devices that are mutually declared between the device having the inter-service capability layer registered therein and the device neighboring gateway. That is, the DSCL of the device in which the mutual service capability layer is registered and the GSCL of the device neighboring gateway in the device neighbor gateway list are used to perform the related resource creation and the interested resource subscription procedure for the device mutually declared. The mutual service capability layer mutually shares the related resources and the interested resources in the device registered with the device neighbor gateway. That is, the DSCL of the device in which the mutual service capability layer is registered and the GSCL of each device neighboring gateway in the device neighbor gateway list are mutually shared.

That is, in the M2M overlay network system shown in FIG. 1, communication between the gateway group 120 / device 110 and the gateway group 120 / device 112, or between the device 110 and another device or device 112, And other devices `to communicate with the M2M overlay network can be configured. Through this M2M overlay network system, the traffic of the core network can be reduced through the rapid propagation of distributed processing based events / data. Further authentication omission through formation of a mutual trusted relationship between the NSCL # 1 of the server 130 and the GSCLs (GSCL # 1 to GSCL # N) of the gateway group 120 and the DSCLs of the device 110, Through the related resource sharing, the overload is reduced according to the mobility of the device `112. Communication between the gateway 130 and the gateway group 120 is called a network domain and communication between the gateway group 120 and the device 110 / Area network (M2M Area Network).

2 is a block diagram schematically showing a device, a gateway and a server according to the present embodiment.

The device 110 according to the present embodiment includes DA, DIP, and DSCL, the device 112 includes DA, the first and second gateways 122 and 124 include GA, GIP, and GSCL, The server 130 includes NA, NIP, and NSCL. In this embodiment, the device 110 includes DA, DIP, and DSCL, the device 112 includes DA, the first and second gateways 122 and 124 include GA, GIP, and GSCL, The present invention is not limited to the above-described embodiments, but includes only NA, NIP, and NSCL # 1. However, this is merely an example of the technical idea of the present embodiment. The first and second gateways 122 and 124 and the server 130 may be variously modified and modified without departing from the essential characteristics of the present embodiment.

The device 110 includes DA, DIP, DSCL to perform M2M communication with the first gateway 122, the server 130, or other devices. That is, the DSCL of the device 110 performs the M2M communication with the NSCL # 1 of the server 130 using the mId. Also, the DSCL of the device 110 performs M2M communication with GSCL # 1 to GSCL # N of the gateway group 120 using mId or dId. In addition, DA and DSCL communicate internally via dIa, and device 110 can perform M2M communication with another device using DIP. On the other hand, the device `112 includes a DA to perform M2M communication with the second gateway 124, the server 130, or another device`. That is, the DA of the device `112 performs M2M communication with the GSCL of the second gateway 124.

The first and second gateways 122 and 124 may communicate with the devices 110 and 112 or the server 130 or other gateways (e.g., neighboring gateways, new gateways) . That is, the GSCL of the first and second gateways 122 and 124 performs M2M communication with the NSCL of the server 130 using the mId. Also, the GSCL # 1 to GSCL # N of the gateway group 120 may perform M2M communication with the DSCL of the device 110 using the mId or dId, or may perform M2M communication with the device 112. [ Also, within the first and second gateways 122 and 124, the GA and the GSCL communicate with each other through the dIa, and can perform M2M communication with other gateways or other devices using the GIP.

The server 130 includes NA, NIP, and NSCL for performing M2M communications with the device 110, the gateway group 120, and the like. That is, the NSCL of the server 130 performs the M2M communication with the GSCL # 1 to GSCL # N of the gateway group 120 or the DSCL of the device 110 using the mId. Internally, NA and NSCL communicate internally via mIa and include an NIP.

2, the DSCL of the device 110, the DA of the device 112, the GSCL of the first and second gateways 122 and 124, and the NSCL # 1 of the server 130 are dIa and mId Or dId, and they interact with each other using DIP, GIP, and NIP, and as a result, they form an M2M overlay network and operate. To describe the M2M overlay network process between the devices, an MSBC procedure is performed between the NSCL # 1 of the server 130 and the GSCL of the first and second gateways 122 and 124, and then a service capability layer is registered. Calculates a neighbor gateway list in the gateway group 120, and builds a resource tree based on the neighbor gateway list. The mutual trust relationship, the mutual declaration procedure, and the resource information sharing between GSCL # 1 to GSCL # N of the gateway group 120 and each adjacent gateway of the neighbor gateway list. The device registration procedure is performed between the DA of the device 112 and the GSCL # 1 of the first gateway 122 and the location information of the DA of the device 112 in the GSCL # 1 of the first gateway 122 Update. Then, when the device `112 moves, the resource tree is updated in the new gateway. After performing the MSBC procedure between the NSCL # 1 of the server 130 and the DA of the device 110, the service capability layer is registered, the device neighbor gateway list for the moved device is calculated, and based on the device neighbor gateway list Build a resource tree. Mutual trust relationship, mutual declaration procedure, and resource information sharing are performed between the device 110 and each new neighboring gateway in the device neighboring gateway list.

2 is a communication area between the server 130 and the gateway group 120 and an M2M area network is a communication area between the gateway group 120 and the device 110. [ . The first gateway 122 / device 110 and the second gateway 122 are connected via the device 110, the first and second gateways 122 and 124 and the server 130 for the M2M overlay network shown in FIG. (124) / device (112) or an interface for communication between the device (112) and another device `. That is, you can define an existing mId application or a new interface (eg, dId). On the other hand, a separate resource for the M2M overlay network can be defined. That is, a new resource tree can be defined or a resource tree of an application level can be created.

3 is a flowchart illustrating a method of providing an M2M overlay network using a DA according to an exemplary embodiment of the present invention.

A service capacity layer is registered after performing the MSBC procedure between the server 130 and the gateway group 120, a neighboring gateway list is calculated in the gateway group 120, and a discovery (S310). Step S310 will be described in detail with reference to FIG. The gateway group 120 performs a network organization process of performing mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighbor gateway list in step S320. Step S320 will be described in detail with reference to FIG.

Thereafter, a device registration procedure is performed between the device 112 and the second gateway 124, and a first device application participation process is performed to update location information on the device 112 in the second gateway 124 (S330). The third gateway 126, which is a new gateway, performs a second device application participation process of updating the resource tree when the device 112 is moved (S340). Steps S330 and S340 will be described in detail with reference to FIG.

The method of providing an M2M overlay network using DA in FIG. 3 is preferably to sequentially perform steps S310 to S340, but it is not limited thereto. Those skilled in the art will recognize that the essentials of the present embodiment And various modifications and changes may be made without departing from the spirit and scope of the invention.

4 is a flowchart illustrating a discovery process according to the present embodiment.

After performing the MSBC procedure between the gateway group 120 and the server 130, a service capability layer is registered (S410). In step S410, the GSCL # 1 to GSCL # N of the first gateway 122 to the Nth gateway 128, which are the gateways of the gateway group 120, and the NSCL # 1 of the server 130 mutually perform an MSBC procedure And then registers the service capability layer. More specifically, the GSCL # 1 to GSCL # N of the first to Nth gateways 128 to 128, which are the respective gateways, perform an MSBC procedure with the NSCL # 1 of the server 130 The GSCL # 1 to the GSCL # N of the first to Nth gateways 128 to 128 are connected to the device 110 / device 112, which is a corresponding device, Together with the location information of the terminal. For example, the gateway group 120 transmits location information (e.g., < gsclBase # i > / applications / < gpsDA # i > / containers / locationContainer) using the GPS DA of the device 110 / To the NSCL # 1 of the server 130 together. For example, the process of discovery of the NSCL # 1 of the server 130 in the GSCL # 1 to GSCL # N of the gateway group 120 can be performed through a pre-provisioned material. Further, the above-described location information may be transmitted by defining additional Protocol Value for Carrier Authentication for Network Access (PANA) AVPs (Attribute Value Pairs), or may be transmitted through resources.

The server 130 calculates a neighbor gateway list for the gateway group 120 (S420). In step S420, the NSCL # 1 of the server 130 accesses the first gateway 122 through the Nth gateway (Nth gateway) 122 based on the location information received from the GSCL of the specific gateway of the mutual authentication successful gateway group 120 128 to the GSCL # 1 to GSCL # N. More specifically, in step S420, the NSCL # 1 of the server 130 transmits, based on the location information received from the GSCLs (GSCL # 1 to GSCL # N) of the mutually authenticated gateway, (GSCL # 1 to GSCL # N) lists for the GSCL # 1 to GSCL # N of the Nth gateway 122 to the Nth gateway 128, respectively. At this time, the neighbor GSCLs (GSCL # 1 to GSCL # N) list calculation algorithm may be performed based on the physical location information or may generate logical location information based on various factors (e.g., response time, hop count, etc.) It can be performed based on this, and it can be calculated by applying various algorithms according to the situation.

The server 130 transmits the neighbor gateway list to the gateway group 120 (S430). In step S430, the NSCL # 1 of the server 130 transmits the adjacent GSCL lists for the registered GSCL # 1 to GSCL # N to the GSCL # 1 to GSCL # N of the gateway group 120, respectively. In other words, in S430, the server 130 obtains a list of adjacent GSCLs (GSCL # 1 to GSCL # N) for GSCL # 1 to GSCL # N of the calculated first to Nth gateways 122 to 128 To GSCL # 1 through GSCL # N, respectively. The gateway group 120 constructs a resource tree based on the neighbor gateway list received from the server 130 (S440). In step S440, GSCL # 1 to GSCL # N of the gateway group 120 construct a resource tree based on the received neighbor GSCL list. For example, in step S440, the GSCL # 1 to GSCL # N of the gateway group 120 construct the < m2mOverlayNetwork > resource tree based on the list of the received adjacent GSCLs (GSCL # 1 to GSCL # N).

It is preferable that the discovery process of FIG. 4 sequentially executes steps S410 to S440. However, the present invention is not limited thereto, and any person skilled in the art will be able to perform the discovery process in a range that does not depart from the essential characteristics of the embodiment Various modifications and variations will be possible.

FIG. 5 is a flowchart illustrating a network organization process according to the present embodiment.

The gateway group 120 establishes a mutual trust relationship with each neighboring gateway in the neighboring gateway list (S510). In step S510, GSCL # 1 to GSCL # N of the gateway group 120 and a GSCL of each adjacent gateway of the neighbor gateway list are established. In step S510, the GSCL # 1 to GSCL # N of the gateway group 120 establish mutual trust relationship with the adjacent GSCLs (GSCL # 1 to GSCL # N) based on the list of adjacent GSCLs (GSCL # GSCL # 1 to GSCL # N of the gateway group 120 are mutually authenticated with the NSCL # 1 of the server 130, so that the GSCLs (GSCL # 1 to GSCL # N) are mutually authenticated using the mId or dId, There is no need for a separate authentication process between the two.

The first gateway 122 to the Nth gateway 128 perform a service capability layer registration procedure without further authentication between the gateway having the mutual trust relationship established and the neighboring gateway at step S520. In step S520, the first gateway 122 to the Nth gateway 128 perform a service capability layer registration procedure without further authentication between the gateway having the mutual trust relationship established and the GSCL of the GSCL and the neighboring gateway, And performs the subscription procedure for the resources of interest to each other. That is, in step S520, a mutual trust relationship is established between the first gateway 122 and the Nth gateway 128, and the mutual trust relationship is established between the gateway and the neighboring gateway without performing a separate authentication process. SCL resource creation and subscription procedures for resources of mutual interest are performed.

The first gateway 122 to the Nth gateway 128 perform a mutual declaration procedure for the resource of the registered device between the gateway having the service capability layer registered therein and the neighboring gateway at step S530. In step S530, the first gateway 122 to the Nth gateway 128 perform the mutual declaration procedure for the resources of the devices registered between the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway, Perform the subscription procedure for the resource. That is, after completion of the SCL registration in step S530, a mutual declaration procedure of the DAs resources registered in GSCL # 1 to GSCL # N of the gateway group 120 is performed, and a DAs declaration resource creation and a join procedure Can be performed.

The first gateway 122 to the Nth gateway 128 perform a related resource creation and an interested resource subscription procedure for the device that is mutually declared in the gateway and the gateway in which the service capability layer is registered in operation S540. In step S540, the GSCL of the gateway to which the service capability layer is registered in the first gateway 122 to the Nth gateway 128, and the GSCL of the neighboring gateway perform a related resource creation and an interested resource subscription procedure do. That is, in step S540, after the mutual declaration, the gateway having the service capability layer registered in the first gateway 122 to the Nth gateway 128 and the neighboring gateway registers the related resource and the registration procedure for the mutually interested resource .

The first gateway 122 to the Nth gateway 128 share the related resources and the interested resources between the gateway to which the service capability layer is registered and the neighbor gateway in step S550. In step S550, the first gateway 122 to the Nth gateway 128 mutually share the related resources and the interested resources between the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway. That is, in step S550, the GSCLs (GSCL # 1 to GSCL # N) forming the M2M overlay network mutually share their cluster and resource information periodically / Even if the DSCL / DA of the device joined to #N moves to and joins the GSCL of the neighboring gateway, the GSCL of the neighboring gateway already shares the information and resource information of the DSCL / DA of the corresponding device.

The network organization process of FIG. 5 preferably executes steps S510 to S550 in order, but it is not limited thereto. Any person skilled in the art will understand that the scope of the network organization process It will be understood that the invention may be varied in many ways.

6 is a flow chart for explaining a device application participation process according to the present embodiment.

The registration process for the device 112 is performed between the device 112 and the second gateway 124 at step S610. In step S610, a registration procedure for the device 112 is performed between DA # 1 of the device 112 and GSCL # 2 of the second gateway 124. More specifically, in step S610, DA # 1 of the device 112 receives a pre-provisioned GSCLs (GSCL # 1 to GSCL # N) 2 GSCL # 2 of the gateway 124 or perform joining to the adjacent GSCL through the discovery procedure of FIG. 5 described above. At this time, the DA # 1 of the device 112 performs the DA registration procedure with the GSCL # 2 of the second gateway 124 that is reachable. In this process, DA # 1 of the device 112 And may transmit the collected local location information to the GSCL # 2 of the second gateway 124 as the corresponding gateway. Also, the GSCL of the neighboring gateway can proceed by broadcasting the Join Msg. Of the DA # 1 of the device `112 '.

The first gateway 122, the third gateway 126, the Nth gateway 128, and the Nth gateway 128, which are the neighboring gateways, are created (S620) (Step S630). In step S630, the GSCL # 2 of the second gateway 124 is connected to the GSCL # 1, GSCL # 3 to GSCL # N of the first gateway 122, the third gateway 126 to the Nth gateway 128 which are the adjacent gateways, And DA # 1 of the device 112 registered with the NSCL # 1 of the server 130. That is, when the DA # 1 registration of the device 112 is successful in step S630, the GSCL # 2 of the second gateway 124, which is the gateway, is connected to the first gateway 122, which is a neighboring gateway forming the M2M overlay network, 1 of the device 112 registered with the GSCLs (GSCL # 1, GSCL # 3 to GSCL # N) of the third gateway 126 to the Nth gateway 128, 130). &Lt; / RTI &gt; At this time, the GSCLs (GSCL # 1, GSCL # 3 to GSCL # N) of the first gateway 122, the third gateway 126 to the Nth gateway 128 which are adjacent gateways and the NSCL # 1 of the server 130 The corresponding resource can be created.

The second gateway 124 receives the neighbor gateway list from the neighboring gateways (the first gateway 122, the third gateway 126 to the Nth gateway 128) (S640). More specifically, in step S640, the second gateway 124 transmits the location information of the device 112 to the neighboring gateways (the first gateway 122, the third gateway 126, (112) is moved rather than receiving the neighboring gateway list from the home gateway (128), the location information is periodically updated to grasp and convey the accurate location information of the device. In addition, since proximity, which is the location information of the gateway in S640, can be calculated by various algorithms such as physical location information (i.e., GPS) or logical location information, information is exchanged periodically / aperiodically to maintain the overlay network topology .

The second gateway 124 updates the location information of the device 112 and predicts the roaming area based on the location and coverage information of the neighboring gateway to perform fast handover in operation S650. Here, it is possible to operate as a separate step of steps S640 and S650. On the other hand, in step S650, the GSCL # 2 of the second gateway 124 is allocated to the GSCL # 1, GSCL # 3, and # 3 of the adjacent gateways (the first gateway 122, the third gateway 126 to the Nth gateway 128) The location information of the device 112 is updated after receiving the neighbor gateway list from the GSCL # N and the GSCL # 1 of the neighboring gateways (the first gateway 122, the third gateway 126 to the Nth gateway 128) , GSCL # 3 to GSCL # N, and performs rapid handover by predicting the roaming area. That is, in step S650, the DA # 1 of the device `112 receives a connection from the GSCL # 2 of the second gateway 124, which is the joined gateway, to the adjacent gateway (the first gateway 122, the third gateway 126, (GSCL # 1, GSCL # 3 to GSCL # N) of the neighboring GSCLs (GSCL # 1, GSCL # 3 to GSCL # N) And predicts the roaming area based on the location and coverage information of the mobile station. At this time, various algorithms can be applied to the fast handover.

Based on the above-described S640, in step S650, that is, when the device `112 changes the location information, it notifies the updated location information to the joined gateway, and the joined gateway continuously updates the location information of the gateways updated 112 to participate in the fast handover process. As a result, the device `112 performs fast handover based on the latest location information of the device and the location information of the neighboring gateway obtained from the joined gateway.

The third gateway 126, which is a new gateway, performs a registration procedure for the device 112 due to the movement of the device 112 in operation S660. In step S660, DA # 1 of the device 112 performs the registration procedure for the device 112 of the GSCL # 3 of the third gateway 126, which is a new gateway due to the movement. That is, if the DA # 1 of the moved device 112 is to join with the GSCL # 3 of the third gateway 126, which is a new gateway in the area, due to the movement of the device 112 in step S660 , It is possible to perform services without having to perform procedures for terminating and registering new DA # 1 resources. That is, because the GSCL # 3 of the third gateway 126 having the already-announced resources can maintain the existing service / session through the DA identifier, the GSCL # 3 of the third gateway 126, which is the gateway of the moving area, 3 does not require additional resource creation or authentication.

The third gateway 126, which is a new gateway, updates the resource related to the device in the resource tree (S670). In step S670, the GSCL # 3 of the third gateway 126, which is a new gateway, updates the resource related to the device 112 in the resource tree. That is, in step S670, the DA # 1 of the moved device `112 may store data in the resource tree of the GSCL # 2 of the second gateway 124, which is the existing (before moving) gateway, 3) of the third gateway 126, which is a gateway that is connected to the second gateway 126. [ Also, the DA # 1 of the device 112 transmits the Notification sent from the NSCL # 1 of the server 130 to the gateway 122 via the GSCL # 2 of the second gateway 124 which is the existing gateway. 3 from the GSCL # 3 of the third gateway 126 or exchange information between the GSCL # 3 of the third gateway 126 that is the changed gateway and the NSCL # 1 of the server 130 through the second gateway 124 3 from the GSCL # 3 of the third gateway 126, which is a gateway that has been changed without passing through the GSCL # 2 of the third gateway 126.

The third gateway 126 as a new gateway transmits the information of the device 112 to the server 130 and the adjacent gateways (the first gateway 122, the second gateway 124, and the Nth gateway 128) (S680). In step S680, the GSCL # 3 of the third gateway 126, which is a new gateway, transmits information about the device 112 to the NSCL # 1 of the server 130 and the neighboring gateways (the first gateway 122, 124, and Nth gateway 128) to the GSCL # 1, GSCL # 2, and GSCL # N. That is, in step S680, the GSCL # 3 of the third gateway 126, which is the gateway of the moving area, transmits join information of the DA # 1 of the moved device 112 to the NSCL # 1 of the server 130 and the neighbor gateway (GSCL # 1, GSCL # 2, GSCL # N) of the first gateway 122, the second gateway 124, and the Nth gateway 128, respectively. At this time, DA # 1 of the moved device 112 can create a new content instance (ContentInstance) in the related resource tree of the GSCL # 3 of the third gateway 126 which is the gateway of the moving area. Here, the content instant field is a resource related to the DA # 1. Also, the notification message from the NSCL # 1 of the server 130 is delivered via the GSCL # 2 of the second gateway 124, which is an existing gateway, 112 directly to DA # 1.

The device application participation process of FIG. 6 preferably executes steps S610 through S680 in order, but is not limited thereto. Those skilled in the art will understand that the device application participation process of FIG. 6 does not deviate from the essential characteristics of the present embodiment It will be understood that the invention may be varied in many ways.

7 is a flowchart illustrating a method of providing an M2M overlay network using DSCL according to an embodiment of the present invention.

A service capacity layer is registered after performing the MSBC procedure between the server 130 and the gateway group 120, a neighboring gateway list is calculated in the gateway group 120, and a discovery (S710). A detailed description of step S710 is as shown in Fig. A network organization process is performed to perform mutual trust relationship, mutual declaration procedure, and resource information sharing among respective neighboring gateways of the neighboring gateway list in the gateway group 120 (S720). A detailed description of step S720 is as shown in Fig.

A MSBC procedure is performed between the server 130 and the device 110 to register a service capability layer, a device neighbor gateway list for the moved device is calculated, and a resource tree is constructed based on the device neighbor gateway list 1 device service capability layer participation procedure (First DSCL Join Procedure) (S730). The second device service capability layer participation procedure (second DSCL Join Procedure) for mutual trust relationship, mutual declaration procedure, and resource information sharing between the device 110 and each new neighboring gateway in the device neighbor gateway list is performed (S740). Steps S730 and S740 will be described in detail with reference to FIG.

The method of providing an M2M overlay network using the DSCL of FIG. 7 preferably executes steps S710 to S740 in order, but is not limited thereto. Those skilled in the art will recognize that the essential And various modifications and changes may be made without departing from the spirit and scope of the invention.

FIG. 8 is a flowchart illustrating a process of participating in a device service capability layer according to the present embodiment.

After performing the MSBC procedure between the device 110 and the server 130, the service capability layer is registered (S810). In step S810, the DSCL # 1 of the device 110 and the NSCL # 1 of the server 130 perform the MSBC procedure and register the service capability layer with each other. In step S810, the DSCL # 1 of the device 110 performs the MSBC procedure with the NSCL # 1 of the server 130 and then performs the registration process of the service capability layer. At this time, the DSCL # 1 of the device 110 And transmits the location information to the NSCL # 1 of the server 130 together. For example, the DSCL # 1 of the device 110 transmits the location information (e.g., <dsclBase # i> / applications / <gpsDA # i> / containers / locationContainer) to the NSCL # 1. Also, the process of discovery of NSCL # 1 of the server 130 in the DSCL # 1 of the device 110 can be performed through the preprovisioned material. Here, the location information may be transmitted by defining additional PANA AVPs or may be transmitted through the resource.

The server 130 calculates a neighbor gateway list for the gateway group 120 (S820). In step S820, the NSCL # 1 of the server 130 receives the device neighbor GSCL list for DSCL # 1 of each device 110 based on the location information received from the DSCL # 1 of the mutually authenticated device 110 . In step S820, the NSCL # 1 of the server 130 transmits the neighbor GSCLs (GSCL # 1 to GSCL # 1) to the DSCL # 1 of the device 110 based on the location information received from the DSCL # 1 of the mutually authenticated device 110 #N). Here, the list calculation algorithm of the adjacent GSCLs (GSCL # 1 to GSCL # N) may be performed based on the physical location information or may generate logical location information based on various factors (e.g., response time, hop count, etc.) And can be performed based on this. At this time, various algorithms can be applied according to the situation.

The server 130 transmits the neighbor gateway list to the device 110 (S830). In step S830, the NSCL # 1 of the server 130 transmits the device neighbor GSCL list for each registered DSCL to the DSCL of each device 110. The resource tree is constructed based on the neighbor gateway list received from the device 110 (S840). In step S840, DSCL of device 110 constructs a resource tree based on the received device neighbor GSCL list. That is, in step S840, the DSCL of the device 110 can construct the <m2mOverlayNetwork> resource tree based on the list of GSCLs (GSCL # 1 to GSCL # N) of the received neighboring gateways.

A mutual trust relationship is established between the device 110 and each device neighboring gateway in the device neighboring gateway list (S850). In step S850, mutual trust relationship is established between DSCL # 1 of the device 110 and GSCL of each device neighboring gateway in the device neighboring gateway list. That is, in step S850, the DSCL # 1 of the device 110 transmits the GSCLs (GSCL # 1 to GSCL # N) of the adjacent gateways (the first gateway 122 to the Nth gateway 128) )) List on the basis of the GSCL # 1 to GSCL # N of the neighboring gateways. At this time, mutual trust establishment procedure can be performed through the mId or dId interface. Since GSCL # 1 to GSCL # N of the gateway group 120 and DSCL # 1 of the device 110 are mutually authenticated with the NSCL # 1 of the server 130, GSCL # 1 to GSCL # N of the gateway group 120 And the DSCL # 1 of the device 110 are unnecessary.

The device 110 and the gateway group 120 can perform the service capability layer registration procedure without additional authentication between the device 110 and the device neighboring gateways (the first gateway 122 to the Nth gateway 128) (S860). In step S860, the device 110 and the gateway group 120 are added between the DSCL # 1 of the mutual trust relationship established device 110 and the GSCL # 1 to GSCL # N of the device neighboring gateways of the device neighbor gateway list Performs a service capability layer registration procedure without authentication, creates a resource for a service capability layer, and performs a join procedure for resources of mutual interest. That is, after establishing the mutual trust relationship in step S860, the device 110 and the gateway group 120 perform the mutual SCL registration procedure without a separate authentication process between the device 110 and the device adjacent gateway established mutual trust relationship And performs an SCL resource creation and subscription procedure for resources of mutual interest.

The device 110 and the gateway group 120 are connected to the device 110 registered with the mutual service capability layer and the device neighboring gateway (the first gateway 122 to the Nth gateway 128) A mutual declaration procedure is performed (S870). In step S870, the mutual declaration procedure for the resources of the devices registered between the DSCL # 1 of the device 110 to which the service capability layer is registered and the GSCL # 1 to GSCL # N of the device neighboring gateways of the device neighbor gateway lists And performs the subscription procedure for the mutual interested resource. That is, in step S870, after completing the SCL registration, the GAs / DAs registered in the GSCL # 1 to GSCL # N of the adjacent gateways (the first gateway 122 to the Nth gateway 128) and the DSCL # 1 of the device 110 Perform the mutual declaration procedure of the resources, generate the GAs / DAs declaration resource, and perform the join procedure for the mutually interested resource.

In operation S880, the device 110 and the gateway group 120 perform an associated resource creation and an interested resource subscription procedure for a device that is mutually declared between the device 110 and the device neighbor gateway in which the mutual service capability layer is registered. In step S880, the device 110 and the gateway group 120 exchange DSCL # 1 of the device 110 with which the mutual service capability layer is registered and the device neighboring gateways (first gateway 122, (N-th gateway 128)) between the GSCL # 1 and the GSCL # N. That is, in step S880, after the mutual declaration process, the mutual service capability layer generates related resources and mutual interest in the device 110 and the device neighboring gateways (the first gateway 122 to the Nth gateway 128) You can perform the subscription procedure for a resource.

The device 110 and the gateway group 120 mutually share the related resources and the interested resources in the devices with which the mutual service capability layer is registered and the device neighboring gateways (S890). In step S890, the DSCL # 1 of the device 110 in which the mutual service capability layer is registered and the GSCL # 1 to GSCL # N of the device neighboring gateways of the device neighbor gateway lists are mutually shared. That is, in step S890, the DSCL of the device forming the M2M overlay network mutually shares its status and resource information periodically / aperiodically, and the GSCL # 1 to the Nth gateway 128 of the first gateway 122 to the Nth gateway 128, Even when the DSCL # 1 of the device 110 that has joined GSCL # N moves to and joins the GSCL of another neighboring gateway, the GSCL of the neighboring gateway already shares information and resource information of DSCL # 1 of the corresponding device 110 . Even when the DSCL # 1 of the device 110 is to be joined with the GSCL of the gateway in the area where the device 110 has moved due to the movement of the device 110, an M2M overlay network is formed to form a mutual trust relationship. And the like are unnecessary.

The device service capability layer participation process of FIG. 8 preferably executes steps S810 through S890 sequentially, but it is not limited thereto. Those skilled in the art will recognize that the essential characteristics of the present embodiment It will be understood that the invention may be varied in many ways without departing from the spirit and scope of the invention.

FIG. 9 is a diagram showing an example of a resource tree at the application level in the discovery process according to the present embodiment. The resource tree at the application level in the discovery process of FIG. 9 is merely an exemplary description of the technical idea of the present embodiment, and it should be understood that any person skilled in the art to which the present invention belongs, Various modifications and variations will be possible. The resource tree at the application level in the discovery process shown in FIG. 9 is a structure for generating a resource tree at the application level, and generates a resource tree at the bottom of the application resource based on the location information. FIG. 10 is an exemplary view of a newly defined resource tree in the discovery process according to the present embodiment. The newly defined resource tree in the discovery process of FIG. 10 is merely an exemplary description of the technical idea of the present embodiment, and any person skilled in the art will be able to understand the present invention without departing from the essential characteristics of the present embodiment Various modifications and variations will be possible. The newly defined resource tree in the discovery process shown in FIG. 10 is a structure for generating a resource tree under the newly defined < m2mOverlayNetwork > resource based on the location information.

11 is an exemplary diagram of a related resource tree in a network organization process according to the present embodiment. The related resource tree in the network organization process of FIG. 11 is merely an exemplary description of the technical idea of the present embodiment, and any person skilled in the art to which the present invention pertains, Modifications and variations will be possible. The related resource tree in the network organization process shown in FIG. 11 forms an M2M overlay network through a mutual trust procedure, and a process of declaring a DA / GA mutual name registered in GSCL # 1 to GSCL # N of the gateway group 120 Through which the relevant resource tree is created. 12 is an exemplary view of a vehicle accident scene where the M2M overlay network according to the present embodiment is applied. As shown in FIG. 12, when an ITS (Intelligent Transport System) is applied to a vehicle accident scene where an M2M overlay network is applied, for example, a vehicle accident occurred is detected on the M2M overlay network by the first gateway 122 / It is possible to quickly propagate and monitor the accident vehicle information through communication between the second gateway 124 and the device 110 or communication between the device 112 and another device.

The foregoing description is merely illustrative of the technical idea of the present embodiment, and various modifications and changes may be made to those skilled in the art without departing from the essential characteristics of the embodiments. Therefore, the present embodiments are to be construed as illustrative rather than restrictive, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be construed according to the following claims, and all technical ideas within the scope of equivalents thereof should be construed as being included in the scope of the present invention.

110: device 112: device `
120: Gateway group 122: First gateway
124: second gateway 126: third gateway
128: Nth gateway 130:

Claims (34)

After performing an MSBC (M2M Service Bootstrapping and Connection) procedure between a server and a gateway, a Service Capability Layer (SCL) is registered, a neighbor gateway list for the gateway is calculated, A discovery procedure for constructing a resource tree based on the discovery procedure; And
A Network Organization Procedure for performing Mutual Trusted Relationship Handshaking, Mutual Announcement procedure, and Mutual Sharing between each of the gateways and neighboring gateways of the neighbor gateway list,
Wherein in the discovery process, the NSCL of the server calculates an adjacent GSCL list for the GSCL of the gateway based on the location information received from the GSCL of the gateway that succeeds mutual authentication, and the GSCL of the gateway And constructing the resource tree based on the neighbor GSCL list. The method according to claim 1,
In the discovery process,
A step 0 of registering the service capability layer after performing the MSBC procedure between the gateway and the server;
A step (1) of calculating, by the server, the neighbor gateway list for the gateway;
Transmitting, at the server, the neighbor gateway list to the gateway; And
Establishing the resource tree based on the neighbor gateway list received from the gateway;
The method of claim 1, 3. The method of claim 2,
In step 0, the GSCL (Gateway Service Capability Layer) of each gateway and the NSCL (Network Service Capability Layer) of the server register the service capability layer after performing the MSBC procedure with each other,
Wherein the NSCL of the server in step 2 sends a neighbor GSCL list for each registered GSCL to the GSCL of each of the registered gateways. The method according to claim 1,
The network organization process includes:
Establishing a mutual trust relationship with each of the neighboring gateways in the neighboring gateway list at the gateway;
Performing the service capability layer registration procedure without further authentication between the gateway and the neighboring gateway in which the mutual trust relationship is established;
A step 6 of performing the reciprocal declaration procedure for a resource of a device registered between the gateway registered with the service capability layer and the neighboring gateway;
Performing a related resource creation and an interested resource subscription procedure for the mutually declared device in the gateway and the neighbor gateway in which the service capability layer is registered; And
The step of sharing the related resource and the resource of interest mutually between the gateway in which the service capability layer is registered and the neighboring gateway
The method of claim 1, 5. The method of claim 4,
Establishing the mutual trust relationship between the GSCL of the gateway and the GSCL of each of the adjacent gateways in the neighbor gateway list in step 4,
Performing the service capability layer registration procedure without additional authentication between the GSCL of the gateway in which the mutual trust relationship is established and the GSCL of the neighboring gateway in step 5, Interesting Resources,
In step 6, performs the mutual declaration procedure for the resources of the devices registered between the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway,
In step 7, the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway perform a related resource creation and an interest resource addition procedure for the mutually declared device,
Wherein the related resource and the resource of interest are mutually shared between the GSCL of the gateway to which the service capability layer is registered and the GSCL of the neighboring gateway in step 8. The method according to claim 1,
A first DAA procedure for performing a device registration procedure between the device and the gateway and updating location information on the device in the gateway; And
A second device application participation process (Second DA Join Procedure) for updating the resource tree at a new gateway when the device is moved,
The method comprising the steps of: The method according to claim 6,
The first device application participation process includes:
Performing a registration procedure for the device between the device and the gateway;
A step 10 of generating an associated resource for the device registered in the gateway and performing an announcement to the neighboring gateway and the server; And
The gateway updates the location information of the device after receiving the neighboring gateway list from the neighboring gateway and predicts a roaming area based on the location and coverage information of the neighboring gateway to perform fast handover, Step 11
The method of claim 1, 8. The method of claim 7,
In step 9, a registration procedure for the device is performed between the DA (Device Application) of the device and the GSCL of the gateway,
In step 10, the GSCL of the gateway declares the GSCL of the neighboring gateway and the DA of the device registered with the NSCL of the server,
In step 11, the GSCL of the gateway receives the neighboring gateway list from the GSCL of the neighboring gateway, updates the location information of the neighboring gateway, and predicts the roaming area based on the location and coverage information of the neighboring gateway To perform the fast handover. The method according to claim 6,
The second device application participating process includes:
A step 12 in which a new gateway performs a registration procedure for the device due to movement of the device;
Updating the resource associated with the device in the resource tree in the new gateway; And
And transmitting the information of the device to the server and the neighboring gateway in the new gateway
The method of claim 1, 10. The method of claim 9,
In step 12, the DA of the device performs the registration procedure for the device by the GSCL of the new gateway due to the movement,
In step 13, the GSCL of the new gateway updates a resource related to the device in the resource tree,
Wherein in step 14, the GSCL of the new gateway transmits information on the device to the NSCL of the server and the GSCL of the neighboring gateway. The method according to claim 1,
A first device service that registers the service capability layer after performing the MSBC procedure between the server and the device, calculates a device neighbor gateway list for the device, and constructs a resource tree based on the device neighbor gateway list, A first DSCL Join Procedure; And
A second DSCL Join Procedure for performing the mutual trust relationship, the mutual declaration procedure, and the resource information sharing between the moved device and each new neighboring gateway in the device neighbor gateway list,
The method comprising the steps of: 12. The method of claim 11,
The first device service capability layer participation process includes:
A step 15 of registering the service capability layer after performing the MSBC procedure between the device and the server;
A step 16 of calculating the neighboring gateway list for the gateway from the server;
A step 17 of transmitting the neighboring gateway list from the server to the device; And
Step 18 of building the resource tree based on the neighbor gateway list received at the device
The method of claim 1, 13. The method of claim 12,
In step 15, the DSCL (Device Service Capability Layer) of the device and the NSCL (Network Service Capability Layer) of the server register the service capability layer after performing the MSBC procedure with each other,
In step 16, the NSCL of the server calculates a device neighbor GSCL list for each DSCL of each device based on the location information received from the DSCL of the device that has succeeded in mutual authentication,
In step 17, the NSCL of the server transmits the device neighbor GSCL list for each registered DSCL to the DSCL of each of the devices,
Wherein the DSCL of the device constructs the resource tree based on the received device neighbor GSCL list in step 18. Performing a MSBC procedure between a server and a gateway, registering a service capability layer, calculating a neighbor gateway list for the gateway, and constructing a resource tree based on the neighbor gateway list;
A network organization process for performing a mutual trust relationship, a mutual declaration procedure, and a resource information sharing between each of the gateways and adjacent gateways of the neighbor gateway list;
A first device application participating process of performing a device registration procedure between the device and the gateway and updating the location information of the device in the gateway; And
A second device application participating process of updating the resource tree at a new gateway when moving the device
The GSCL of the gateway in the first device application participation process receives the neighboring gateway list from the GSCL of the neighboring gateway and updates the location information of the device to obtain the location and coverage information of the GSCL of the neighboring gateway And a fast handover is performed by predicting a roaming area on the basis of the estimated handover frequency. 15. The method of claim 14,
The first device application participation process includes:
Performing a registration procedure for the device between the device and the gateway;
A step 10 of generating an associated resource for the device registered in the gateway and performing an announcement to the neighboring gateway and the server; And
The gateway updates the location information of the device after receiving the neighboring gateway list from the neighboring gateway and predicts a roaming area based on the location and coverage information of the neighboring gateway to perform fast handover, Step 11
The method of claim 1, 16. The method of claim 15,
In step 9, a registration procedure for the device is performed between the DA (Device Application) of the device and the GSCL of the gateway,
Wherein the GSCL of the gateway declares the GSCL of the neighboring gateway and the DA of the device registered with the NSCL of the server in step 10. 15. The method of claim 14,
The second device application participating process includes:
A step 12 in which a new gateway performs a registration procedure for the device due to movement of the device;
Updating the resource associated with the device in the resource tree in the new gateway; And
And transmitting the information of the device to the server and the neighboring gateway in the new gateway
The method of claim 1, 18. The method of claim 17,
In step 12, the DA of the device performs the registration procedure for the device by the GSCL of the new gateway due to the movement,
In step 13, the GSCL of the new gateway updates a resource related to the device in the resource tree,
Wherein in step 14, the GSCL of the new gateway transmits information on the device to the NSCL of the server and the GSCL of the neighboring gateway. Performing a MSBC procedure between a server and a gateway, registering a service capability layer, calculating a neighbor gateway list for the gateway, and constructing a resource tree based on the neighbor gateway list;
A network organization process for performing a mutual trust relationship, a mutual declaration procedure, and a resource information sharing between each of the gateways and adjacent gateways of the neighbor gateway list;
A first device service that registers the service capability layer after performing the MSBC procedure between the server and the device, calculates a device neighbor gateway list for the device, and constructs a resource tree based on the device neighbor gateway list, Participation in the Capability Layer; And
A second device service capability layer participation process for performing the mutual trust relationship, the mutual declaration procedure, and the resource information sharing between the moved device and each new neighboring gateway in the device neighboring gateway list
Wherein the service capability layer registration procedure is performed between the GSCL of the gateway in which the mutual trust relationship is established and the GSCL of the neighboring gateway in the network organization process without further authentication, And sharing the resource information between the GSCL and the GSCL of the neighboring gateway. 20. The method of claim 19,
The first device service capability layer participation process includes:
A step 15 of registering the service capability layer after performing the MSBC procedure between the device and the server;
A step 16 of calculating the neighboring gateway list for the gateway from the server;
A step 17 of transmitting the neighboring gateway list from the server to the device; And
Step 18 of building the resource tree based on the neighbor gateway list received at the device
The method of claim 1, 21. The method of claim 20,
In step 15, the DSCL (Device Service Capability Layer) of the device and the NSCL (Network Service Capability Layer) of the server register the service capability layer after performing the MSBC procedure with each other,
In step 16, the NSCL of the server calculates a device neighbor GSCL list for each DSCL of each device based on the location information received from the DSCL of the device that has succeeded in mutual authentication,
In step 17, the NSCL of the server transmits the device neighbor GSCL list for each registered DSCL to the DSCL of each of the devices,
Wherein the DSCL of the device constructs the resource tree based on the received device neighbor GSCL list in step 18. A server for registering a service capability layer after performing the MSBC procedure with the gateway, calculating a neighbor gateway list for the gateway, and transmitting the list; And
A gateway group for constructing a resource tree based on the received neighboring gateway list, and performing mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list
Wherein the NSCL of the server calculates a neighbor GSCL list for the GSCL of the gateway based on the location information received from the GSCL of the gateway that succeeded in mutual authentication and the GSCL of the gateway obtains the neighbor GSCL list And the resource tree is constructed based on the resource tree. 23. The method of claim 22,
The gateway group includes:
The device and the device registration procedure are performed, and the location information of the device is updated, and when the device is moved, the resource tree is updated using a new gateway. 24. The method of claim 23,
The server comprises:
And registers the service capability layer after performing the MSBC procedure with the device, calculates a device neighbor gateway list for the moved device, and transmits the device neighbor gateway list to the moved device. 25. The method of claim 24,
The device,
Constructing a resource tree based on the received device neighbor gateway list, and performing the mutual trust relationship, the mutual declaration procedure, and the resource information sharing between the moved device and each new neighbor gateway in the device neighbor gateway list Wherein the M2M overlay network providing system comprises: A server for registering a service capability layer after performing the MSBC procedure with the gateway, calculating a neighbor gateway list for the gateway, and transmitting the list; And
Constructing a resource tree based on the received neighboring gateway list, performing a mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list, performing a device and a device registration procedure, A gateway group which updates the location information of the device and updates the resource tree by using a new gateway when moving the device,
Wherein the service capability layer registration procedure is performed between the GSCL of the gateway in which the mutual trust relationship is established and the GSCL of the neighboring gateway without further authentication and the GSCL of the gateway in which the service capability layer is registered, And the resource information is shared between the GSCLs of the plurality of servers. A server for registering a service capability layer after performing the MSBC procedure with the gateway, calculating a neighbor gateway list for the gateway, and transmitting the list; And
A gateway group for constructing a resource tree based on the received neighboring gateway list, and performing mutual trust relationship, mutual declaration procedure, and resource information sharing among neighboring gateways of the neighboring gateway list
Wherein the server registers the service capability layer after performing the MSBC procedure with the device, calculates a device neighbor gateway list for the device, and transmits the device neighbor gateway list to the device, Constructing a resource tree based on the gateway list, performing the mutual trust relationship, the mutual declaration procedure, and the resource information sharing between the moved device and each new neighboring gateway of the device neighboring gateway list, Based on the location information received from the GSCL of the gateway with which mutual authentication has been successful, calculates a neighbor GSCL list for the GSCL of the gateway, and the GSCL of the gateway constructs the resource tree based on the received neighbor GSCL list M2M system provides an overlay network comprising. An NSCL (Network Service Capability Layer) for registering a service capability layer after performing the MSBC procedure with the gateway, calculating a neighbor gateway list for the gateway, and transmitting the list to the gateway; And
The network application (NA)
Wherein the NSCL uses an algorithm based on physical location information or an algorithm based on logical location information based on at least one of a response time and a hop count to calculate the neighbor gateway list And the server. 29. The method of claim 28,
The NSCL,
After performing the MSBC procedure with the Gateway Service Capability Layer (GSCL) of each of the gateways, the service capability layer is registered, and based on the location information received from the GSCL of the gateway, Calculates a neighbor GSCL list for GSCL and transmits a neighbor GSCL list for each registered GSCL to the GSCL of each of the registered gateways. 29. The method of claim 28,
The NSCL,
The service capability layer is registered after performing the MSBC procedure with the DSCL (Device Service Capability Layer) of the device, and based on the location information received from the DSCL of the mutually authenticated device, DSCL And transmits the device neighbor GSCL list for each registered DSCL to the DSCL of each of the devices. delete A service capability layer is registered after performing the MSBC procedure with the server, a resource tree is constructed based on the neighbor gateway list received from the server, and a mutual trust relationship, a mutual declaration procedure A GSCL (Gateway Service Capability Layer) for performing resource information sharing, performing a device and device registration procedure, updating location information about the device, and updating the resource tree when moving the device; And
Gateway application (GA) for performing gateway internal communication)
The GSCL establishes the resource tree based on the neighbor GSCL list received from the server, receives the neighbor gateway list from the GSCL of the neighbor gateway, updates the location information of the device, And performs a fast handover by predicting the roaming area based on the location and coverage information of the GSCL of the gateway. 33. The method of claim 32,
The GSCL,
Performing the service capability layer registration procedure without additional authentication between the GSCLs of the neighboring gateways, performing a resource creation for the service capability layer and a subscription procedure for mutual interested resources, Performs the mutual declaration procedure for the resources of the registered devices, performs the joining procedure for the mutual interested resource, and performs the related resource creation and the interested resource joining procedure for the cross-declared device in the GSCL of the neighboring gateway And sharing the related resources and the resources of interest among the GSCLs of the neighboring gateways. 33. The method of claim 32,
The GSCL,
(DA) of the device and the device, and declares the GSCL of the neighboring gateway and the DA of the device registered with the NSCL of the server.

Images