KR20130135009A - Managing apparatus and method for machine-to-machine communications - Google Patents

Abstract

A management apparatus for M2M communication and a method are disclosed. The present invention periodically synchronizes information, manages machine-to-machine (M2M) communication through an interface which accesses resources, and abstracts a device through a device master template and a resource master template. According to the present invention, the scalability problem of a system and the heterogeneity problem of the interface, which can approach to the resources, can be solved. The load of network service capability layer (NSCL) is minimized without reducing the service quality. [Reference numerals] (AA) Registration request of device #A

Description

[0001] The present invention relates to a management apparatus and method for M2M communication,

The present invention relates to a management apparatus and method for an M2M communication, and more particularly, to a management apparatus and method for an M2M communication. More particularly, the present invention abstracts a device through a device master template and a resource master template, To machine-to-machine communications (M2M) communication through an accessible interface, and to an apparatus and method for periodically synchronizing information.

ETSI has established the ETSI Machine-to-Machine (M2M) standard in the European telecommunications standards institute (ETSI), an international standardization organization, to facilitate communication services between objects and equipment. The ETSI M2M standard consists of a network application (NA), a device application (DA), a network service capability layer (NSCL), a service capability layer (SCL) It defines the same concept and improves the convenience of service development by standardizing URI (uniform resource identifier) that accesses resources based on representational state transfer (REST).

The ETSI M2M standard defines that a legacy device that does not conform to the standard can be connected to the Network Service Capability Layer (NSCL), but its specific method is not defined. However, in a real environment, many devices are legacy devices, and the following problems arise when such legacy devices are connected to the network service capability layer (NSCL). The first problem is the scalability of the system, which can lead to performance degradation when multiple devices are connected to a single network serviceability layer (NSCL). The second problem relates to the heterogeneity of interfaces that can access resources. Even the same type of device, the access interface may be different for each manufacturer or model. Here, the heterogeneity problem can occur in both form and semantics. In terms of form, communication protocols may be different from each other, and in terms of contents (semantics), the languages (namespace, taxonomy, grammar, etc.) .

In addition, the Network Service Capability Layer (NSCL) may include a read / write buffer for smooth communication between the device and the network application (NA). When a buffer is utilized, the data that the network application (NA) sends to the device or the data that the device sends to the network application (NA) is first stored in this buffer. With this method, it is possible to increase the availability of data or to reduce redundancy requests. Container-related URIs or network interworking proxies (NIP) defined in the ETSI M2M standard can be used to access this buffer.

When using these read / write buffers, synchronization efficiency will have a significant impact on overall system performance. If synchronization occurs at an excessively high frequency in a situation where a plurality of network applications (NA) and a plurality of devices are connected to one network service capability layer (NSCL), the network service capability layer (NSCL) , Which results in an increase in system construction cost. On the other hand, if synchronization occurs at an excessively low frequency, the load on the system will be low, but the network application (NA) may not meet requirements such as desired message delivery rate and the like. Therefore, there is a need for a method capable of efficiently performing synchronization while considering characteristics of M2M communication such as a short packet length, a large number of packets, and a variety of device specifications.

Patent Document 1 discloses an M2M module having an emergency notification function, an M2M device selectively connected to the M2M module, and a driving method thereof. In Patent Document 1, The M2M device requests the M2M device to acquire the emergency notification information having the data format, receives the emergency notification information from the M2M device, and sets the emergency notification information to take necessary actions And the emergency notification information acquired from the M2M device to the service server. Patent Document 2 discloses a service control method and system for subscriber traffic data of an M2M application, and Patent Document 2 discloses a service control method for a subscriber traffic data of an M2M application, Based on the service quality reference information of the subscriber based on the trend information of the application received from the M2M module, the subscriber traffic data transmitted and received exceeds the limited range The contents of which are controlled so as not to be displayed.

An object of the present invention is to provide an interface for abstracting a device and accessing resources through a device master template and a resource master template, To-machine communication (M2M) communication through a communication network, and to periodically synchronize information.

An object of the present invention is to provide an interface for abstracting a device and accessing resources through a device master template and a resource master template, The present invention provides a computer-readable recording medium on which a program for executing a management method for M2M communication, which manages M2M communication (Machine-to-Machine communications) through a network and periodically synchronizes information,

According to an aspect of the present invention, there is provided a management apparatus for an M2M communication system including a storage unit for storing a device master template and a resource master template; And a control unit for receiving the device master template stored in the storage unit and the resource master template stored in the storage unit upon receiving a registration request message from the device, And a registering unit for registering.

According to another aspect of the present invention, there is provided a management method for an M2M communication, the method comprising: receiving a registration request message from a device; And registering the device through a device master template stored in advance and a resource master template stored in advance.

According to another aspect of the present invention, there is provided a computer readable medium storing a program for causing a computer to execute any one of the above methods.

According to the management apparatus and method for an M2M communication according to the present invention, a device performs a machine-to-machine communications (M2M) communication through a device master template and a resource master template, Services can be used. Accordingly, when a new device emerges, a device master entry and a resource master entry corresponding to a new device are created and added, so that a new device can be also used for machine-to-machine communications (M2M) Services are available. Therefore, the scalability problem of the system can be solved.

In addition, a device master template and a resource master template, in which device communication information, expression format information of a resource content, and lexical information used for expressing resource content are stored for each device, A master template can be used to abstract the device and provide an interface to access the resource. Accordingly, even if the same device is used, an interface may be different for each manufacturer or model. However, if a device master template and a resource master template according to the present invention are used, Devices that are different from each other can also use the M2M (Machine-to-Machine communications) service. Therefore, it is possible to solve the heterogeneity problem of an interface that can access a resource.

In addition, by synchronizing only the transactions selected using the requirements of the network application (NA) and the transaction information (TSD) supported by the device, the network service capability layer (NSCL) Synchronization can be performed with minimal load. Accordingly, the performance requirement of the network service capability layer (NSCL) generated as the number of connected devices increases can be reduced, and the infrastructure construction cost required for the M2M communication (machine-to-machine communications) service can be reduced .

1 is a block diagram illustrating a management apparatus for an M2M communication according to a preferred embodiment of the present invention.
FIG. 2 is a block diagram illustrating a configuration of a management apparatus for M2M communication according to a preferred embodiment of the present invention,
3 is a diagram illustrating an example of a device master entry according to a preferred embodiment of the present invention,
4 is a diagram illustrating an example of a resource master entry according to a preferred embodiment of the present invention;
5 is a diagram for explaining a registering operation of a device according to a preferred embodiment of the present invention;
6 is a view for explaining an example of a virtual device instance according to a preferred embodiment of the present invention,
FIG. 7 is a view for explaining an example of a resource chunk instance according to a preferred embodiment of the present invention;
8 is a block diagram illustrating a configuration of a synchronization unit according to a preferred embodiment of the present invention,
9 is a view for explaining an example of requirements of a network application according to a preferred embodiment of the present invention;
10 is a view for explaining an example of an integration cycle for a device according to a preferred embodiment of the present invention;
11 and 12 are diagrams for explaining a transaction management operation according to a preferred embodiment of the present invention;
13 is a view for explaining an example of device-supported transaction information according to a preferred embodiment of the present invention;
14 is a view for explaining an example of elements constituting job request list information according to a preferred embodiment of the present invention;
15 is a view for explaining an example of job request list information according to a preferred embodiment of the present invention;
16 is a view for explaining an example of a transaction subject to push gain calculation among device-supported transaction information according to a preferred embodiment of the present invention;
17 is a view for explaining an example of a throughput index for a transaction belonging to device supported transaction information according to a preferred embodiment of the present invention;
18 is a view for explaining an example of a transaction selection operation according to a preferred embodiment of the present invention,
19 is a flowchart illustrating a method for managing M2M communication according to a preferred embodiment of the present invention,
20 is a flowchart for explaining a synchronization method according to a preferred embodiment of the present invention in more detail.

Hereinafter, a preferred embodiment of a management apparatus and method for M2M communication according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram illustrating a management apparatus for a M2M communication according to a preferred embodiment of the present invention.

Referring to FIG. 1, a management apparatus 100 for a M2M communication according to the present invention may be connected to a plurality of devices 200-1 through 200-n through a communication network 300. FIG.

The M2M communication management apparatus 100 is a device used for M2M communication (Machine-to-Machine communication), and provides a registration of a device, a resource access interface for a device, and the like. The management device 100 for M2M communication is provided with a network service capability layer (NSCL) and a network application (NA) defined in the machine-to-machine (M2M) standard established by the European Telecommunications Standards Institute (ETSI) .

Here, the Network Service Capability Layer (NSCL) is a kind of service platform, providing communication and resource access. The network application NA is a machine-to-machine (M2M) application registered in the network service capability layer NSCL, and includes a network service capability layer NSCL and another service capability layer SCL. To provide services to users. That is, the registration of the device is performed through the network service capability layer (NSCL), and data transmission / reception is performed between the network application (NA) and the device application (DA). Then, data synchronization is performed according to the requirements of the network application (NA) or the device application (DA) through the network service capability layer (NSCL).

In addition, resources are declared in the network application (NA). The declared resources describe what resources are to be accessed when the network application (NA) is operating. For example, declared resources are described in the specification or source code of the network application (NA). In other words, when creating a network application, a resource can be treated as an accessible variable or object. When a network application (NA) is executed and connected to actual devices at a later time, ) Are connected and the network application (NA) performs the work. Such a variable or object represents a declared resource in a network application (NA).

The devices 200-1 to 200-n are devices for requesting M2M communication (machine-to-machine communications), such as a temperature controller, a radiator, a radiator, and a television. The devices 200-1 through 200-n may be standard devices conforming to the ETSI M2M standard or may be proprietary devices not conforming to the ETSI M2M standard. The devices 200-1 through 200-n correspond to the "device application DA" defined in the Machine-to-Machine (M2M) standard established by the European Telecommunications Standards Institute (ETSI).

The devices 200-1 to 200-n request the M2M communication management apparatus 100 to register their own devices for machine-to-machine communications.

The communication network 300 may include a data communication network including a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) It does not matter whether it is wired or wireless, and any communication method can be used.

2 is a block diagram illustrating the configuration of a management apparatus for M2M communication according to a preferred embodiment of the present invention in more detail.

2, the management device 100 for a M2M communication includes a storage unit 110, a registration unit 130, and a synchronization unit 150.

The storage unit 110 stores a device master template and a resource master template. Also, the storage unit 110 may have a data storage space such as a read / write buffer. The read / write buffer is used for smooth communication between the network application (NA) and the device.

Here, the device master template is composed of a plurality of device master entries. The device master entry includes device manufacturer identification information, device identification information, device communication information, and device resource information.

The device manufacturer identification information is a unique code that can identify the manufacturer of the device, and includes a manufacturer name, a GTIN (global trade item number) code, and the like. The device identification information is a unique code capable of identifying the device, and includes a serial number of the device, an activation code of the device, and the like. The device communication information refers to address information and route information for the M2M communication management apparatus 100 to access the device.

The device resource information is information about a resource supported by the device, and includes a type of a resource, a controllability, and unique resource identifying information that can be identified in the device. Here, the type of the resource uses the vocabulary defined in the resource master entry described below.

3 is a diagram illustrating an example of a device master entry according to a preferred embodiment of the present invention.

For example, a device master entry corresponding to an air conditioner capable of measuring temperature and humidity is as follows.

Referring to Fig. 3, the device manufacturer identification information is composed of a manufacturer name "A-Company ", which is a unique code capable of identifying a manufacturer through a tag" manufacturer ". The device identification information includes serial numbers "102-8364-02934, 107-8364-63456, 795-5846-11634, etc.", which are unique codes capable of identifying the device through the tag "serial-number-pool and serial-number" . The device communication information is composed of a protocol type "IPv4" which is information for accessing the device through a tag "communication, protocol,

The device resource information is composed of "temperature and humidity" which is information about a resource supported by the device through the tag "resources and resource ". Here, the device resource information is expressed by "temperature or humidity" which is a type of resource through an attribute "type" for each resource and is controlled through an attribute "assignable" Quot; 1-Measured Temperature, 2-Measured Humidity, or 3-Measured Humidity, which is unique resource identification information identifiable within the device through the attribute "id & Target Temperature "is expressed.

The resource master template is composed of a plurality of resource master entries. A resource master entry includes expression format information of a resource content and lexical information used for expressing a resource content. Here, a resource content represents a content of a resource that can be measured / observed / controlled in the device. The resource corresponds to "<container>" in the RESTful URI structure defined in the ETSI M2M standard. For example, in the case of a cooler provided with a temperature sensor, the resource content of the cooler includes a temperature measurement value (measurable content) and a target temperature value (controllable content).

Representation format information of resource content refers to information about a standardized expression language such as extensible markup language (XML), JavaScript object notation (JSON), and the like. For example, an XML representation format can be defined with a document type definition (DTD).

The taxonomy and / or namespace information used to represent the resource content may be used to describe the resource content among the various terms used to represent the resource content. Information.

4 is a diagram illustrating an example of a resource master entry according to a preferred embodiment of the present invention.

4, a resource master entry includes a representation format information of a resource content, a taxonomy and / or namespace information used for representing a resource content, .

The "representation format" information of the resource content defines "type, value and unit" which is a representation format of the resource content through a DTD (document type definition) language.

The taxonomy and / or namespace information used to represent the resource content includes a vocabulary used to represent the resource content in a format expressed in a document type definition (DTD) Or namespace "PCDATA" is defined. For example, a resource master entry for a temperature value may be made up of "temperature" in the field "type", "numeric value" in the field "value", and "celsius" in the field "unit" The resource master entry for the humidity value can be made up of "humidity" in the field "type", "numeric value" in the field "value", and "percent" in the field "unit"

Upon receiving the registration request message from the first device 200-1, the registration unit 130 registers the device master template previously stored in the storage unit 110 and the device master template stored in the storage unit 110 And registers the first device 200-1 through a resource master template. Here, the registration request message includes device manufacturer identification information, device identification information, and the like. That is, the registering unit 130 registers a virtual device instance and a resource chunk instance corresponding to the first device 200-1 through a device master template and a resource master template, resource chunk instance) to be stored in the storage unit 110, thereby registering the first device 200-1.

More specifically, the registering unit 130 registers the device master template stored in the storage unit 110 using device manufacturer identification information, device identification information, and the like included in the registration request message received from the first device 200-1. and searches for a device master entry corresponding to the first device 200-1 in the device master template. The registering unit 130 generates a virtualized device instance corresponding to the first device 200-1 through a device master entry corresponding to the first device 200-1 . Here, the virtualized device instance includes device master entry identification information, device identification information, device communication information, resource chunk instance identification information, and the like.

In addition, the registering unit 130 may register the resource master template (resource master) stored in the storage unit 110 through the device resource information included in the device master entry corresponding to the first device 200-1 template to retrieve the corresponding resource master entry. Then, the registering unit 130 generates at least one resource chunk instance through the searched resource master entry. Here, the number of generated resource chunk instances is the same as the number of resource master entries searched. A resource chunk instance includes at least one resource content generated from the same resource master entry.

The registering unit 130 registers the resource content included in the resource chunk instance of the first device 200-1 as resource content head data and resource content body data resource content body data), and store them in the storage unit 110. Here, the resource content head data represents meta data of a resource content. For example, the meta data may include resource content identification information, a resource type, and the like. The resource content body data represents actual data.

That is, the registering unit 130 can independently store and separate resource content head data and resource content body data. For example, the registering unit 130 registers a device master template, a resource master template, a virtualized device instance, and a resource chunk instance in a relational DBMS. It is possible to store resource content head data and store resource content body data of a resource chunk instance in the NoSQL DBMS.

The registering unit 130 stores a virtualized device instance corresponding to the first device 200-1 and a resource chunk instance of the first device 200-1 in the storage unit 110, .

5 is a diagram for explaining a registering operation of a device according to a preferred embodiment of the present invention.

5, when the device #A requests the M2M communication management apparatus 100 to register, the registration unit 130 registers the device manufacturer identification information, device identification information, and the like included in the registration request message received from the device #A (One of DME_1 to DME_J) corresponding to the device #A in the device master template DM stored in the storage unit 110 using the retrieved device master entry and corresponds to the device #A through the searched device master entry And stores the generated virtual device instance VD_A in the storage unit 110.

6 is a view for explaining an example of a virtual device instance according to a preferred embodiment of the present invention.

For example, the device #A is an air conditioner capable of measuring temperature and humidity, the manufacturer of the device #A is "A-Company", the serial number of the device #A is "107-8364-63456" The virtual device instance corresponding to the device #A generated when the registration of the device #A is requested at the address "10.1.1.2 " is as follows.

Referring to FIG. 6, the device master entry identification information is a device used to generate a virtualized device instance corresponding to the device #A via the "device-master-entry-number & And "11" which is the identification information of the master entry (device master entry).

The device identification information is composed of " 107-8364-63456 " which is identification information of the device #A via the tag "serial-number ".

The device communication information is composed of "10.1.1.2 " which is communication information of the device #A via the tag" communication, ipv4,

The resource chunk instance identification information includes identification information of a resource chunk instance generated for the resource supported by the device #A through the tag "resource-chunks and resource-chunk & 11111, 12222 and 13333 ".

Referring again to FIG. 5, the virtual device instance VD_A corresponding to the device #A is generated, and the registering unit 130 registers the virtual device instance VD_A corresponding to the device # (At least one of RME_1 to REM_K) corresponding to the resource master template RM stored in the storage unit 110 and stores the resource chunk instances RC_A_1 to RC_A_m of the device #A in the retrieved resource master entry And stores it in the storage unit 110.

7 is a view for explaining an example of a resource chunk instance according to a preferred embodiment of the present invention.

For example, a resource chunk instance generated through a resource master entry having a resource content as a "temperature measurement value " is made up of the following resource content.

Referring to FIG. 7, in the resource content, " temperature ", which is the type of resource, is detected through the tag " type ", "35.5" ", The unit of the value" celsius "is expressed.

In this manner, the registering unit 130 generates and stores a virtualized device instance and a resource chunk instance corresponding to each of the devices 200-1 to 200-n that have requested registration, And registers the requested devices 200-1 to 200-n.

The synchronization unit 150 transmits a message to and receives a message from the first device 200-1 and stores the resource chunk instance of the first device 200-1 stored in the storage unit 110 and the resource chunk instance of the first device 200- 1 in the first device 200-1 corresponding to the resource chunk instance of the first device 200-1. That is, when the status of the virtualized device instance corresponding to the first device 200-1 is changed, the synchronization unit 150 also reflects the status of the virtual device instance to the first device 200-1, 1 is also changed, the virtual device instance corresponding to the first device 200-1 is also reflected.

8 is a block diagram showing the configuration of a synchronization unit according to a preferred embodiment of the present invention in more detail.

Referring to FIG. 8, the synchronization unit 150 includes a requirement management unit 151, a transaction management unit 153, a transaction selection unit 155, and a transaction execution unit 157.

The requirement management unit 151 manages requirements for periodic reading / writing from each of a plurality of network applications (NA) to a specific device. That is, the requirement management unit 151 grasps and maintains information on how the requirements of the network application (NA) are reflected in the specific device. In addition, the requirement management unit 151 requests the transaction management unit 153 and the transaction selection unit 155 to perform a job if necessary.

More specifically, when the new network application (NA) is registered in the network service capability layer (NSCL) or the already registered network application (NA) is changed, the requirement management section (151) And a read / write period is calculated and updated for each resource.

Here, the read / write cycle can be extracted from the network application (NA) properties on the network service capability layer (NSCL). For example, the network application (NA) registration information includes a specification defining a network application (NA), a network application (NA) source code, and the like. In addition, the read / write cycle may be determined based on statistical information that monitors the request of the network application (NA). For example, an average of a time interval of a read request for a specific resource, a moving average, an average of upper values, and the like may be determined periodically.

On the other hand, if there are a plurality of reference values to determine the period of a specific resource, the smallest reference value is determined as the period of the corresponding resource. For example, according to the network application (NA) registration information, 5 or 3 seconds are required as a read period for a specific resource. According to the statistical information, if the read period is 10 seconds, the read period of the resource is 3 Seconds.

In short, the requirement management unit 151 calculates a read / write cycle for the resource X declared in the network application (NA) through the following equation (1).

9 is a diagram for explaining an example of requirements of a network application according to a preferred embodiment of the present invention.

There are two network applications (NA) NA1 and NA2 running on the network service capability layer (NSCL), NA1 declares three resources (A, B, C) and NA2 declares four resources , C, and D), the requirement management unit 151 acquires information about the resource declared by each NA and the read / write cycles (NARP, NAWP) for the resource, as shown in FIG. 9 Can be extracted and maintained.

The requirement management unit 151 is a unit for managing a read period (NARP) or write (NARP) of a resource of a network application (NA) When the period NAWP changes or the network application NA connected to the device is terminated, the integrated read (NARP) and write cycle (NAWP) are used for each resource of the device / Calculate and update the merged read / write period.

Here, a merged read period (MRP) and a merged write period (MWP) are calculated for a device resource. On the other hand, the read period (NARP) and the write period (NAWP) are each calculated for a declared resource in the network application (NA).

For example, the integrated read cycle (MRP) of a resource Y of a specific device is a minimum value of a read cycle (NARP) of resources connected to a resource Y among resources declared by all currently running network applications (NA) . The integrated write cycle (MWP) is also determined in this manner. Here, all currently executed network applications (NA) refer to both a newly executed network application (NA) and a currently executed network application (NA).

In summary, the requirement management unit 151 calculates an integrated read / write cycle for resource Y of a specific device through the following equation (2).

FIG. 10 is a diagram for explaining an example of the integration period for a device according to a preferred embodiment of the present invention.

The device D1 has two resources R1 and R2 and the NA1 is executed so that the resources B and C of NA1 are respectively connected to the resources R1 and R2 of the device D1 and the NA2 is executed, The requirements management unit 151 can calculate and maintain information about the integrated read / write cycles MRP and MWP for the device D1 as shown in FIG. 10 have.

If the newly calculated integrated read / write cycle is different from the existing integrated read / write cycle, the requirement management unit 151 requests the transaction management unit 153 and the transaction selection unit 155 to perform a task. That is, the requirement management unit 151 requests the transaction management unit 153 and the transaction selection unit 155 to perform a job change when a requirement such as addition, change, deletion, or the like occurs. For example, the requirement management unit 151 may request a job while providing a request for periodic reading / writing from the network application (NA) to the device to the transaction management unit 153 or the transaction selection unit 155.

The transaction management unit 153 identifies and manages transactions supported by the device. That is, the transaction management unit 153 identifies and updates the message format and communication method supported by the device.

In other words, if the device registered in the network service capability layer NSCL is changed (newly registered, changed, deleted, or the like) or if there is a work request of the requirement management unit 151, It identifies and updates the types of transactions that can occur between the pervious layer (NSCL) and the device.

Here, a transaction refers to a sender sending a message once to a receiver, or a sender sending a message to a receiver once and receiving a response message therefor. Also, registering or changing a device includes not only physically connecting the device to the network service capability layer (NSCL) but also changing the device identification information. For example, the device identification information may change when a device manufacturer releases a new product that can be connected to the Network Service Capability Layer (NSCL) or changes specifications of an existing product.

At this time, the transaction that takes place between the device and the network serviceability layer (NSCL) depends on what resources the device reads or writes to the device, and whether the device and the network serviceability layer (NSCL) You can classify messages based on whether they send messages first. For example, the resource to read from the device is A, the resource to be written to the device is B, and the transaction to send the message first on the device side is made in the following two steps.

Step 1) The device sends a message to the Network Service Capability Layer (NSCL) containing the value A and requesting the value to set to B

Step 2) The network service capability layer (NSCL) receiving the message from the device responds to the device with a message containing the value to be set in B

In other words, if you know what resources a device has, you can set the resource to read from the device, the resource to write to the device, and any type of transaction, . A transaction supported by a device can be part of any type of transaction identified.

In summary, the transaction management unit 153 calculates a transaction supported by device (TSD) consisting of only transactions supported by the device among all types of transactions. At this time, the method of storing and maintaining the device supported transaction information (TSD) can be implemented by various methods. For example, it is possible to store all the elements of the device support transaction information (TSD), to store only some rules of the device support transaction information (TSD), to store only some rules of the device support transaction information Only transactions can be stored.

11 and 12 are views for explaining a transaction management operation according to a preferred embodiment of the present invention.

The transaction management unit 153 can acquire all possible types of transactions as shown in FIG. Here, 'push attribute' of 'transaction element' indicates whether it is device push or not. 'read element' indicates the resource to read from the device. The 'write element' indicates the resource to write to the device.

For example, in the last transaction, the network service capability layer (NSCL) reads R1 and R2 values from the device and simultaneously assigns R1 and R2 values to the device, Lt; / RTI &gt;

If the R1 and R2 values of the device D1 are currently 5 and 7, respectively, the device D1 transmits a message as shown in FIG. 12 (a) to the network serviceability layer NSCL). Here, 'request element' represents a resource to be received from the network service capability layer (NSCL). The 'read element' indicates the value of the resource that the network serviceability layer (NSCL) is to read from the device D1. Thereafter, if the network service capability layer (NSCL) receiving this message tries to set the values of R1 and R2 of the device D1 to 10 and 11, respectively, it can respond with a message as shown in FIG. 12 (b) . Here, 'write element' represents the value of the resource that the network service capability layer (NSCL) intends to write to device D1.

13 is a view for explaining an example of device-supported transaction information according to a preferred embodiment of the present invention.

The transaction management unit 153 determines the type of transaction supported by the device D1 by using the data sheet of the device D1 or the like and obtains the type of transaction supported by the device D1 The device-supported transaction information (TSD) composed of only transactions supported by the device-supported transaction information (TSD) can be extracted and maintained.

In addition, if there is a change in the type of transaction, the transaction management unit 153 requests the transaction selection unit 155 to perform a task. That is, the transaction management unit 153 notifies the transaction selection unit 155 of the change when the device-supported transaction information TSD is changed. For example, the transaction management unit 153 may provide the changed device support transaction information (TSD) to the transaction selection unit 155 to notify the change.

The transaction selection unit 155 determines the type and frequency of a transaction between the network service capability layer (NSCL) and the device. That is, the transaction selecting unit 155 determines the type and frequency of a transaction using a greedy algorithm, taking the characteristics of the communication request frequency and the device-specific communication method as resource as resource, do.

In other words, if there is a job request from the requirement management unit 151 or the transaction selection unit 155, the transaction selection unit 155 selects a transaction to be actually performed among the device support transaction information (TSD) And determines the execution cycle of each selected transaction. In the present invention, this problem is regarded as a weighted set cover problem and solved by using a greedy algorithm. At this time, the main variable is the integrated read cycle (MRP), the integrated write cycle (MWP), and the device supported transaction information (TSD).

More specifically, the transaction selection unit 155 extracts job request list information (TaskSet) using data provided by the requirement management unit 151. [ Here, the task request list information (TaskSet) is a set of required synchronization tasks, and refers to a set to be covered by a weighted set cover problem.

The information of the integrated read cycle (MRP) and the integrated write cycle (MWP) for each resource becomes an element of the task request list information (TaskSet). The contents of each element are identified by a resource ID in the device, an operation flag, an integrated read cycle, or an integrated write cycle to identify whether the device is reading from or writing to the device in the network service capability layer (NSCL) . The content of an element can be expressed in various formats.

14 is a view for explaining an example of elements constituting job request list information according to a preferred embodiment of the present invention.

For example, an element whose integrated read period of the resource A is 5 seconds may be configured as a triple as shown in FIG.

15 is a view for explaining an example of job request list information according to a preferred embodiment of the present invention.

The transaction selection unit 155 extracts and maintains job request list information (TaskSet) as shown in FIG. 15 using data provided by the requirement management unit 151.

The transaction selector 155 selects a transaction to be started from a message sent from the device to the network service capability layer NSCL in each transaction belonging to the device supported transaction information TSD, The push gain is calculated through Equation (3). In the present invention, device push refers to the case where a transaction begins with a message sent from the device to the network service capability layer (NSCL). In general, device push transactions are not limited to network push / load (NSCL) of network / computing resources Little amount.

Here, the resources of the consumed network service capability layer (NSCL) can be measured through the number of messages exchanged, the network bandwidth consumption, and the CPU time of the NSCL process. In addition, the measurement method of resources of the Network Service Capability Layer (NSCL) consumed may vary depending on the detailed implementation such as the type of communication protocol and the structure of the NSCL thread. For example, if the number of messages exchanged and operated on the basis of the UDP protocol is used as a resource consumption measure, if the device reads a resource of a device and uses a device push method, Since the message is transmitted only once by the capability layer (NSCL), the total number of messages is 1, the push gain is calculated as 1, and if not by the device push method, the network service capability layer In NSCL, two messages are used in the process of requesting resources and the push gain is calculated as 2. In other words, how the push gain is calculated based on what criteria can be determined by how the network serviceability layer (NSCL) is actually constructed. Of course, it is not necessary to calculate the push gain for each device push transaction, but to push all of the device push method transactions in batch A push gain can also be set. In summary, the specific calculation of the push gain can be done in a variety of ways.

16 is a view for explaining an example of a transaction subject to push gain calculation among device-supported transaction information according to a preferred embodiment of the present invention.

The transaction selecting unit 155 selects a push gain for a transaction that becomes a device push as shown in FIG. 16 among transactions belonging to the device supported transaction information (TSD) ). The push gain for this transaction is assumed to be 2.

The transaction selection unit 155 calculates a throughput index for each transaction belonging to the device supported transaction information (TSD). Here, a throughput index is an index indicating how many user requests a transaction can handle. That is, the transaction selecting unit 155 may calculate a throughput index for the transaction X belonging to the device supported transaction information (TSD) through the following Equation (4).

That is, the throughput index is determined to be a value proportional to the frequency of execution of those that can be performed by the transaction X among the elements of the task request list information (TaskSet), and the transaction X is a device push , And finally multiply by the push gain. When the task request list information (TaskSet) changes, the throughput index also changes accordingly.

17 is a view for explaining an example of a throughput index for a transaction belonging to device supported transaction information according to a preferred embodiment of the present invention.

The transaction selection unit 155 calculates a throughput index as shown in FIG. 17 for each transaction belonging to the device supported transaction information (TSD) of the device D1.

The transaction selection unit 155 calculates a merged action period (MAP) for each transaction belonging to the device supported transaction information (TSD). Here, the integrated operation period (MAP) refers to the operation cycle of each transaction to meet the requirements of the network application (NA). That is, the transaction selection unit 155 can calculate the integrated operation period (MAP) for the transaction X belonging to the device supported transaction information (TSD) through the following equation (5).

When the task request list information (TaskSet) changes, the integrated operation period (MAP) also changes accordingly.

The transaction selection unit 155 uses the task request list information (TaskSet) based on the throughput index and the integrated operation cycle (MAP) for each transaction belonging to the device supported transaction information (TSD) A greedy algorithm is executed to select a transaction that can satisfy the requirements of the network application NA and to set an integrated operation cycle MAP of the corresponding transaction. The greedy algorithm is a heuristic for the set cover problem to cover job request list information (TaskSet) with elements of device supported transaction information (TSD). At this time, each element of the device support transaction information (TSD) can be regarded as a subset of the task request list information (TaskSet). The greedy algorithm according to the present invention is shown in Table 1 below.

Input: TaskSet, TSD

Output: Set of Tuples (selected transaction, integration cycle)

Repeat while TaskSet is not empty
X = The transaction in TSD with maximum throughput index
(If tie exists, select transaction with minimum of related resources)
T = The merged action period of X
Output = Output ∪ {(X, T)}
TaskSet = TaskSet - {tasks covered by transaction X}
End Repeat

Here, related resources related to a transaction refer to resources that are read or written in the corresponding transaction.

In summary, the transaction selection unit 155 identifies and updates the set of tuples.

18 is a view for explaining an example of a transaction selection operation according to a preferred embodiment of the present invention.

A transaction X with the maximum throughput index at the first execution of the iteration routine of the greedy algorithm is the transaction shown in Figure 18 (a). The integrated operation cycle (MAP) of transaction X is 4 as shown in FIG. 18 (b). After the execution of the one-time loop routine, the output is as shown in Fig. 18 (c). After the execution of the one-time loop routine, the task request list information (TaskSet) is changed as shown in FIG. 18 (d) in which the tasks to be processed in the transaction X are removed. Thereafter, when the iterative routine ends, the output is as shown in (e) of FIG.

If necessary, the transaction selecting unit 155 notifies the transaction executing unit 157 of the fact that a transaction to be performed has been changed. That is, the transaction selecting unit 155 provides a tuple set to the transaction executing unit 157 when the contents of the tuple set are changed.

The transaction execution unit 157 performs a transaction selected by the transaction selection unit 155 and synchronizes with the selected transaction. That is, the transaction execution unit 157 performs synchronization based on a set of tuples supplied from the transaction selection unit 155. In other words, the transaction executing unit 157 periodically performs a transaction, which is not a device push method, by a network service capability layer (NSCL), and performs a device push ) Requests the device to periodically send a message to start the transaction.

Meanwhile, a device master entry, a resource master entry, a virtualized device instance, a resource chunk instance, a device-supported transaction information (TSD), task request list information (TaskSet), etc. are expressed through JSON (JavaScript object notation), XML (extensible markup language), DTD (document type definition), etc. However, the present invention is not limited thereto But can be expressed in various formats according to embodiments.

FIG. 19 is a flowchart illustrating a method for managing M2M communication according to a preferred embodiment of the present invention.

The first device 200-1 requests the M2M communication management apparatus 100 to register the first device 200-1 (S810). At this time, the first device 200-1 transmits a registration request message including the manufacturer identification information of the first device 200-1, the identification information of the first device 200-1, and the like to the management device 100 for M2M communication, Lt; / RTI &gt;

Then, the M2M communication management apparatus 100 registers the first device 200-1 through a device master template and a resource master template, which are stored in advance. That is, the M2M communication management apparatus 100 manages the virtual device instance corresponding to the first device 200-1 and the virtual device instance corresponding to the resource 300 through the resource master template and the device master template, The first device 200-1 is registered by creating and storing a resource chunk instance.

More specifically, the M2M communication management apparatus 100 generates and stores a virtualized device instance of the first device 200-1 using a previously stored device master template (step &lt; RTI ID = 0.0 &gt; S830). That is, the M2M communication management apparatus 100 uses the device manufacturer identification information, the device identification information, and the like included in the registration request message received from the first device 200-1 to generate a device master template Searches for a device master entry corresponding to the first device 200-1 in the first device 200-1 and searches for a virtual device instance corresponding to the first device 200-1 through the searched device master entry, (virtualized device instance) is generated and stored.

The M2M communication management apparatus 100 generates and stores a resource chunk instance of the first device 200-1 using the resource master template stored in step S850, . That is, the M2M communication management apparatus 100 transmits the resource master entry corresponding to the resource master template stored in the resource master template through the device resource information included in the device master entry corresponding to the first device 200-1 (resource master entry) of the first device 200-1 and generates and stores a resource chunk instance of the first device 200-1 through the searched resource master entry.

Thereafter, the management device 100 for M2M communication exchanges messages with the first device 200-1 and synchronizes information with each other (S870).

Meanwhile, although it has been described that the resource chunk instance generation step S850 is performed after the generation of the virtualized device instance S830, the resource chunk instance generation step S850 is performed. However, the resource chunk instance generation step S850 is performed before the virtualized device instance generation step S830 or the virtualized device instance generation step S830 and the resource chunk instance ) Generating step S850.

20 is a flowchart for explaining a synchronization method according to a preferred embodiment of the present invention in more detail.

The management apparatus 100 for M2M communication manages the requirements of the network application (NA) (S871). That is, the management device 100 for M2M communication manages requirements for periodic reading / writing from each of a plurality of network applications (NA) to a specific device. More specifically, when the new network application (NA) is registered in the network service capability layer (NSCL) or the network application (NA) that has already been registered is changed, the management apparatus for M2M (100) Calculate and update the read / write period for each declared resource. The management apparatus 100 for M2M communication is configured to perform a read period NARP of a resource of a network application NA that is newly executed and connected to the device or connected to the device, When the NAWP is changed or the network application NA is terminated after being connected to the device, it is possible to integrate each resource of the device using the read period NARP and the write period NAWP. Calculates and updates the merged read / write period.

Then, the M2M communication management apparatus 100 manages the device support transaction information (TSD) (S873). That is, the M2M communication management apparatus 100 recognizes and manages transactions supported by the device. More specifically, the M2M communication management device 100 calculates device-supported transaction information (TSD) for each device, which is composed of only transactions supported by the devices in all types of transactions.

Then, the M2M communication management apparatus 100 selects a transaction based on the requirement and the device supporting transaction information (TSD) (S875). That is, the management device 100 for M2M communication uses the characteristics of the communication request frequency and the device-specific communication method as resources as the main variables, and uses the greedy algorithm to determine the type and frequency of transactions . More specifically, the M2M communication management apparatus 100 extracts task request list information (TaskSet) using the requirements of the network application (NA). The M2M communication management apparatus 100 transmits a push gain to a transaction starting with a message sent from the device to the network service capability layer (NSCL) in each transaction belonging to the device support transaction information (TSD) (push gain). Then, the M2M communication management apparatus 100 calculates a throughput index and an integrated operation period (MAP) for each transaction belonging to the device supported transaction information (TSD). The management apparatus 100 for M2M communication transmits task request list information (TaskSet) based on a throughput index and an integrated operation cycle (MAP) for each transaction belonging to the device support transaction information (TSD) A greedy algorithm is used to select a transaction that can satisfy the requirements of the network application and set an integrated operation cycle MAP of the corresponding transaction.

Finally, the M2M communication management apparatus 100 performs a selected transaction to synchronize information with the device (S877).

In this way, the device can use the M2M communication (Machine-to-Machine communication) service through the device master template and the resource master template stored and stored. Accordingly, when a new device emerges, a device master entry and a resource master entry corresponding to a new device are created and added, so that a new device can be also used for machine-to-machine communications (M2M) Services are available. Therefore, the scalability problem of the system can be solved.

In addition, a device master template and a resource master template, in which device communication information, expression format information of a resource content, and lexical information used for expressing resource content are stored for each device, A master template can be used to abstract the device and provide an interface to access the resource. Accordingly, even if the same device is used, an interface may be different for each manufacturer or model. However, if a device master template and a resource master template according to the present invention are used, Devices that are different from each other can also use the M2M (Machine-to-Machine communications) service. Therefore, it is possible to solve the heterogeneity problem of an interface that can access a resource.

In addition, by synchronizing only the transactions selected using the requirements of the network application (NA) and the transaction information (TSD) supported by the device, the network service capability layer (NSCL) Synchronization can be performed with minimal load. Accordingly, the performance requirement of the network service capability layer (NSCL) generated as the number of connected devices increases can be reduced, and the infrastructure construction cost required for the M2M communication (machine-to-machine communications) service can be reduced .

The present invention can also be embodied as computer-readable codes on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer apparatus is stored. Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like in the form of a carrier wave . In addition, the computer-readable recording medium may be distributed to computer devices connected to a wired / wireless communication network, and a computer-readable code may be stored and executed in a distributed manner.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the appended claims.

100: management device for M2M communication,
200-1 to 200-n: devices,
300: Network

Claims (15)

A storage unit for storing a device master template and a resource master template; And
Upon receipt of a registration request message from the device, registers the device through a device master template previously stored in the storage unit and the resource master template stored in the storage unit, And a registering unit for registering the M2M communication apparatus. The method according to claim 1,
Wherein the device master template comprises a device master entry including device manufacturer identification information, device identification information, device communication information, and device resource information,
Wherein the resource master template comprises a resource master entry including expression format information of a resource content and lexical information used for expressing the resource content Management device for M2M communication. The method according to claim 1,
The register generates a virtualized device instance and a resource chunk instance corresponding to the device through the device master template and the resource master template, And registers the device in the storage unit. The method of claim 3,
The registration unit searches the device master template corresponding to the device from the device master template stored in the storage unit through the registration request message, A resource master entry supported by the device is retrieved from the resource master template stored in the storage unit through a device master entry, A virtualized device instance corresponding to the device and a resource chunk instance corresponding to the device using a device master entry and a resource master entry supported by the discovered device, ) M2M communication management apparatus characterized in that. The method of claim 3,
Further comprising a synchronization unit for exchanging a message with the device and for synchronizing information in the device corresponding to the resource chunk instance and the resource chunk instance stored in the storage unit, Management device for M2M communication. 6. The method of claim 5,
Wherein the synchronization unit comprises:
A requirement manager for managing requirements for periodic reading or writing from the network application (NA) to the device;
A transaction management unit for acquiring device supported transaction information (TSD) by recognizing a transaction supported by the device;
Selecting a transaction from the device supported transaction information (TSD) using the requirement and the device supported transaction information (TSD), and selecting a transaction to set an integrated operation cycle (MAP) of the selected transaction part; And
And a transaction execution unit for synchronizing information by performing the selected transaction. The method according to claim 6,
The transaction selection unit extracts the task request list information (TaskSet) using the request, and for each transaction belonging to the device supported transaction information (TSD), a throughput index and an integrated operation cycle MAP ) Using the task request list information (TaskSet) based on a throughput index and an integrated operation cycle (MAP) for each transaction belonging to the device supported transaction information (TSD) Selects a transaction from the device supported transaction information (TSD) and sets an integrated operation cycle (MAP) of the selected transaction. Receiving a registration request message from a device; And
And registering the device through a device master template stored in advance and a resource master template stored in the device master template. 9. The method of claim 8,
Wherein the device master template comprises a device master entry including device manufacturer identification information, device identification information, device communication information, and device resource information,
Wherein the resource master template comprises a resource master entry including expression format information of a resource content and lexical information used for expressing the resource content A management method for M2M communication characterized by. 9. The method of claim 8,
In the registering step, a virtualized device instance and a resource chunk instance corresponding to the device are generated through the device master template and the resource master template And the device is registered by registering the device. 11. The method of claim 10,
Wherein the registering step comprises:
Retrieving a device master entry corresponding to the device from the device master template previously stored through the registration request message;
Retrieving a resource master entry supported by the device from the resource master template previously stored through the device master entry corresponding to the searched device; And
A virtualized device instance corresponding to the device and a resource master entry corresponding to the discovered device using a device master entry corresponding to the searched device and a resource master entry supported by the searched device, And generating a resource chunk instance based on the generated resource chunk instance. 11. The method of claim 10,
Further comprising the step of synchronizing the information in the device with the resource chunk instance and the resource chunk instance by exchanging messages with the device, . 13. The method of claim 12,
The synchronization step comprises:
Managing requirements for periodic reading or writing from the network application (NA) to the device;
Acquiring device supported transaction information (TSD) by identifying a transaction supported by the device;
Selecting a transaction from the device supported transaction information (TSD) using the requirement and the device supported transaction information (TSD) and setting an integrated operation period (MAP) of the selected transaction;
And synchronizing the information by performing the selected transaction. 14. The method of claim 13,
Wherein the transaction selection step comprises:
Extracting a task request list (TaskSet) using the requirements;
Calculating a throughput index and an integrated operation period (MAP) for each transaction belonging to the device supported transaction information (TSD); And
Based on the throughput index and the MAP of each transaction belonging to the device supported transaction information (TSD), the device supported transaction information ( Selecting a transaction in the TSD and setting an integrated operation period (MAP) of the selected transaction. A computer-readable recording medium having recorded thereon a program for causing a computer to execute the management method for M2M communication according to any one of claims 8 to 14.

Images