KR20150001434A

KR20150001434A - Method and apparatus of dynamic controlling data transmission and reception in M2M System

Info

Publication number: KR20150001434A
Application number: KR20130074657A
Authority: KR
Inventors: 제갈영찬; 김정근; 서동섭; 서명우
Original assignee: 주식회사 케이티
Priority date: 2013-06-27
Filing date: 2013-06-27
Publication date: 2015-01-06
Also published as: KR102012028B1

Abstract

The present invention relates to a method and a device for dynamically controlling data transmission and reception in an M2M system. More specifically, an intermediate node according to an embodiment of the present invention, which transceives data with a first node and a second node, comprises: a first transceiving unit to transceive data with the first node and to receive data type information from an application included in the first node; a data management unit to store the data type information; a session management unit to set or release connection according to the data type information; and a second transceiving unit to transceive data with the second node, wherein the session management unit controls the second transceiving unit to transceive data with the second node by a connection method corresponding to the data type information.

Description

[0001] The present invention relates to a method and apparatus for dynamically controlling transmission and reception of data in an M2M system,

The present invention relates to a M2M (Machine to Machine Communication) technology, and proposes a method and apparatus for dynamically controlling transmission / reception of data in an M2M system.

"Machine to Machine Communication" or MTC, "Machine Type Communication" or "Smart Device Communication" or "Machine oriented communication" or "Internet of Things" In which communication is performed without intervening in the network. Recently, oneM2M has been discussing M2M, but there are no technical elements to meet the architecture and requirements of oneM2M. For example, gateways, intermediate nodes, etc., which are intermediate in the recently developed M2M, apply the same network-based communication method to all data types, so that the load of the network and the importance of the data are not reflected, .

In order to solve the above-described problems, the present invention provides a method and apparatus for efficiently controlling connection establishment and dynamically controlling transmission / reception of data types generated from M2M nodes, To provide efficient network management and resource management, as well as to provide reliability such as lost data recovery in the event of a failure.

The intermediate node transmitting and receiving data to and from the first node and the second node according to an embodiment of the present invention transmits and receives the data to and from the first node and receives the data type information from the application included in the first node A session management unit for establishing or releasing a connection according to the data type information and a second transceiver for transmitting and receiving the data to and from the second node, The management unit is a device that controls the second transmitting and receiving unit to transmit and receive the data to and from the second node in a connection mode corresponding to the data type information.

An apparatus for transmitting and receiving data to and from an intermediate node according to an exemplary embodiment of the present invention includes an application for controlling data type information, a first transmitting and receiving unit for receiving data type information of the data from the application, A session management unit for establishing or releasing a connection according to the data type information and a second transceiver for transmitting and receiving the data to and from the intermediate node, 2 transmitting / receiving unit transmits / receives the data to / from the intermediate node.

A method according to an embodiment of the present invention is an M2M system comprising a first node, a second node and an intermediate node for transmitting and receiving data between the first node and a second node, Determining information and transmitting the determined information to the intermediate node, the intermediate node storing the received data type information, and determining a connection mode according to the data type information, wherein the intermediate node transmits the determined connection The method comprising the steps of: transmitting information about the method to the first node; generating an application of the first node to transmit the generated data to the intermediate node; and transmitting the connection method according to the data type information of the received data And transmitting the data to the second node using the second node.

When an embodiment of the present invention is implemented, a connection can be established and controlled so as to efficiently transmit / receive data according to the characteristics of data generated from the M2M device or the network / device situation. When implementing an embodiment of the present invention, not only efficient resource management considering the data processing state and system state information of M2M entities, but also reliability such as lost data recovery in case of failure can be provided.

1 is a diagram showing a configuration of a system constituting the present invention.
Fig. 2 is a diagram showing a system constituting the present invention from a functional viewpoint of a higher level.
3 is a diagram showing a functional structure constituting the present invention.
4 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention. Fig. 4 includes a function of processing identification information.
5 is a diagram illustrating a common service entity according to another embodiment of the present invention.
6 is a diagram illustrating a configuration of an intermediate node according to an embodiment of the present invention.
7 is a diagram illustrating a configuration of a base node or a device node according to an embodiment of the present invention.
FIG. 8 is a block diagram illustrating interactions of modules or internal configuration functions of AF and CSF of each node of M2M according to an exemplary embodiment of the present invention. Referring to FIG.
9 is a table showing initial connection control information set and managed in the CSF of each node for data types according to an embodiment of the present invention.
10 is a flowchart illustrating an operation flow for connection control between AF and CSF in each device and connection establishment between CSFs of each device for seamless raw data and event data according to an embodiment of the present invention.
11 is a flowchart illustrating an operation flow for connection control between AF and CSF in the device and connection establishment between CSFs of each device for M2M device control data according to an embodiment of the present invention.
12 is a flowchart illustrating a process of changing and controlling a connection mode according to an embodiment of the present invention.
13 is a diagram illustrating a process of changing and controlling a connection scheme according to another embodiment of the present invention.
14 is a diagram illustrating a data loss recovery process according to an embodiment of the present invention.
15 is a diagram illustrating a process of dynamically controlling transmission / reception of data in the M2M system according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference numerals whenever possible, even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

Embodiments of the present invention will be described with reference to object communication. Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . OneM2M has recently introduced many technical issues related to object communication. Object communication refers to various communication in which communication is performed without a person intervening in the communication process. In the field of telecommunication, there are various fields such as energy field, enterprise field, healthcare field, public service field, residential field, retail field, transportation field, and others Field, and so on. The present invention includes the above-mentioned fields, and is applicable to other fields.

In the present invention, identification refers to a process of recognizing entities in a specific domain differently from other entities. Authentication means determining the identity of an entity or establishing a source of information. Authorization is the granting of rights, which involves assigning based on access rights. Confidentiality refers to a property that makes information unavailable or unauthorized for unauthorized entities or processes. Credentials are data objects used in a security procedure and used to uniquely identify an entity. Encryption refers to the process of generating a plaintext as a ciphertext using a cryptographic algorithm and a key. Integrity means ensuring the accuracy and completeness of the processing of information and methods. A key is a parameter used in combination with an encryption algorithm. An entity having information on the key can reproduce the key or perform the encryption process inversely, and an entity having no information about the key can perform the reproduction Or reverse performance. Mutual authentication refers to entity authentication that ensures mutual identity. Privacy may be the right of individuals to control or influence relevant information collected and stored by the subject to be disclosed. Repudiation means denying an event or action requested from an entity. Security means a state in which a system conforms to an applicable security policy, and security means a state of a system generated by generating and maintaining a scheme for protecting the system. Sensitive data refers to the classification of stakeholder data that is problematic if it is tampered with, without the consent of stakeholders that are unintentionally known or affected. A subscription is a classification of an aggrement, which means the agreement between a provider and a subscriber on the use (or consumption) of a service over a period of time. Subscriptions usually mean commercial agreement. Trust refers to the relationship between two components, only if component x has confidence that a component y will behave in a predefined manner that does not violate the given security congestion, y and has a relationship of activity and security policy. Verification means confirmation through the provision of objective evidence that a specific requirement is satisfied.

An M2M application is an application that runs service logic and uses one M2M common service with one open interface in oneM2M. The M2M application infrastructure node is a device (a collection of physical servers of the M2M application service provider). The M2M application-based node manages data and implements an adjustment function of the M2M application service. An application-based node hosts one or more M2M applications.

The M2M application service is implemented through the service logic of the M2M application and is operated by the M2M application service provider or the user. An M2M application service provider is an entity that provides M2M application services to a user. The M2M Area Network is a form of an underlying network and provides data transport services between M2M gateways, M2M devices, and Sensing / Actuation Equipment. M2M local area networks (LANs) can use heterogeneous communication technologies and may or may not support IP access.

The field domain consists of M2M gateway, M2M device, sensing / actuation device, and M2M local network. The Infrastructure Domain consists of an application infrastructure and an infrastructure. A sensing / actuation device provides functionality that senses or influences the physical environment by interacting with one or more M2M application services. It interacts with the M2M system but does not host the M2M application. An M2M solution is a system that is implemented or deployed to meet the following criteria: it meets the end-to-end M2M communication requirements of a specific user. An M2M system refers to a system that implements or deploys an M2M solution. An underlying network means a function, network, bus or other technology for data transmission / connection services

1 is a diagram showing a configuration of a system constituting the present invention. 1 illustrates an application 110, a common service 120, and an underlying network service 130. Each of them constitutes an application layer, a common service layer, and a network service layer. The application layer contains the business logic and operational logic associated with oneM2M applications. The common service layer consists of a oneM2M service function that operates the oneM2M application. For this, management, discovery, and policy enforcement are applied.

A common service entity is an instantiate of a common service function. The common service entity provides a subset of the common service functions to be used and shared by the M2M application. The common service entity uses the functions of the underlying network and interacts with other common service objects to implement the service.

Fig. 2 is a diagram showing a system constituting the present invention from a functional viewpoint of a higher level. Application Function (AF) 210 provides application logic for an end-to-end M2M solution. For example, a fleet tracking application such as a vehicle, a remote blood sugar monitoring application, or a remote power metering and controlling application. A common service function (CSF) 220 is a set of service functions, and these service functions are functions commonly used in the M2M environment. These service functions are exposed as other functions through Reference Points X and Y, and use the base network service using reference point Z. Examples are Data Management, Device Management, and M2M Subscription Management. When the CSF of oneM2M node is implemented as a common service entity, some of the service functions may be mandatory and some may be optional.

An underlying network services function (NSF) 230 provides services to the common service entity. Examples of services include device management, location services and device triggering.

Reference points are supported in the common service function, and the X reference point is the instantiation of the application function and the reference point between the common service objects. The Y reference point is a reference point between two common service objects. The Z reference point is a reference point between the common service entity and the implementation of one network service function.

More specifically, the X reference point allows one M2M application to use the services supported by the common service entity. The services provided through the X reference point are dependent on the functionality provided by the common service entity, and the M2M application and the common service entity may reside in the same physical entity or in different physical entities. The Y reference point enables such use by a common service entity that wishes to use the services of other common service entities that provide the necessary functionality. The Y reference point may exist between common service objects of different M2M physical entities. The services provided through the Y reference point are dependent on the functionality provided by the common service entity. A Z reference point enables such a use for a common service entity wishing to use the services of the underlying network providing the necessary functionality. Information exchange between two physical M2M nodes can use the transport and connectivity services of the underlying network to provide basic services.

3 is a diagram showing a functional structure constituting the present invention. In the Functional Architecture of FIG. 3, A represents an application and CSE represents a common service entity. 311, 312, 313 and 314 denote device nodes, 320 denotes an intermediate node, 330 denotes an infrastructure node, . The CSEs of the different nodes are not identical to each other, and depend on the services supported by the CSE in the node.

The device nodes 311, 312, 313 and 314 may include one or more application function (AF) objects, a common service entity (CSE) providing a common service function, The device nodes 311, 312, 313, and 314 perform a function of a communication terminal device (M2M Device) for providing an M2M service and directly or indirectly process a common service function with the base node .

The intermediate node 320 relays a common service function between the device node and the base node 330 and performs a common service function for the node and the base node 330 to provide the M2M service. Therefore, unlike the node, the intermediate node 320 requires a common service entity (CSE).

The base node 330 exchanges information with the node or the common service object of the intermediate node 320 to collect various information, process it, and perform control functions related thereto. Hereinafter, a node that does not have a description, for example, a base node or a node that is not an intermediate node corresponds to a device node.

4 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention. Fig. 4 includes a function of processing identification information.

The functions provided by the common service object can be summarized as shown in FIG. 4 to provide identification, data management and repository, location, security, communication management / delivery Handling, Registration, Session Management, Device Management, Subscription / Notification, Connectivity Management, Discovery, Service Charging, / Accounting, Network Service Exposure / Service Execution and Triggering, and Group Management.

Of course, in addition to the above functions, it may include semantics, data analysis, application enablement, and network service function management.

5 is a diagram illustrating a common service entity according to another embodiment of the present invention.

The functions provided by the common service entity are divided into three parts as management, facilities, and security. The management area includes device management and the like. The facility is divided into Application Support, Information Support, and Communication Support, which support interaction with applications. The functions provided by the application support unit include registration, subscription, discovery, accounting / charging, provisioning, notification, device management, And security management. Information support consists of Data Management and Resources. Communication support consists of Connectivity Management and Session Management.

Security consists of Credential Management, Encryption Integrity, and Profile Management.

4 or 5 are embodiments for implementing a common service entity and the present invention is not limited thereto.

oneM2M is a requirement that must be fulfilled to implement the system. It includes overall system requirements, management requirements, data model & semantics requirements, security requirements Requirements, Charging Requirements, and Operational Requirements.

In this specification, M2M, especially oneM2M, will be mainly described. However, this description is not limited to M2M, but is applicable to all systems and structures providing inter-device communication, i.e., object communication, and communication occurring in these systems.

The conventional M2M service data control technology is implemented only for the control technology which depends on the M2M network-based connection technology through the network path control and the data priority control, and a method of flexibly implementing or controlling at the application level is proposed I did.

The present invention relates to a method of providing reliability of M2M data and efficiently managing and managing resources by providing an application level efficient connection setting control technique for various data types handled in the M2M service.

For example, the M2M data types processed in M2M-enabled systems, such as smart buildings, home automation, and energy measurement, are used for events such as raw data, alarms, And M2M control services in M2M applications such as M2M service providers (service providers) such as control data for controlling data and devices.

Smart buildings, for example, are provided with M2M services such as Light Control, Intruder Video Monitor, Fire Alarm and air-condition control, In order to provide service scenarios by collecting and processing low-level data generated from devices such as sensors, or providing event management and system control through M2M gateway functioning as nodes or devices and M2M intermediate nodes.

Generally, the currently developed M2M intermediate nodes use the same network communication for all data types, for example TCP socket network communication, without considering application level connection control between AF (Application Function) and CSF (Common Service Function) And transmits and receives data between the node (M2M Device), the intermediate node (M2M Gateway), and the base node in a temporal manner.

By applying the same transient TCP socket network communication between nodes (M2M Device), intermediate nodes (M2M Gateway) and base nodes for all M2M data types, it is possible to process the simultaneous batch data from M2M devices A resource problem such as a CPU load of a node may occur.

During the real-time provision of control services, M2M application service providers must be able to recover specific data that is lost in the event of an interruption, even if the intermediate node (M2M Gateway) is recovered after a failure. To achieve this, it is necessary to provide data recovery technology through duplication technology or application level connection control between nodes in the intermediate node.

Hereinafter, a communication method capable of applying a computing resource such as a communication between a M2M application in a device and a network domain, a CPU or a memory in the OneM2M will be described.

Hereinafter, a device node is an M2M device, a device functioning as a terminal, and a node having no other modifier is an abbreviation of a device node. The intermediate node is a device that performs the function of the M2M gateway.

6 is a diagram illustrating a configuration of an intermediate node according to an embodiment of the present invention. The intermediate node 600 includes a data management unit 610, a first transmission / reception unit 620, a second transmission / reception unit 640, a session management unit 630, and a device management unit 650. The device management unit 650 may optionally be included and monitors the physical state of the device 600.

The intermediate node 600 transmits and receives data to and from the first node and the second node. The first transmission / reception unit 620 transmits / receives the data to / from the first node, receives the data type information from an application included in the first node, and the data management unit 610 stores the data type information And the session management unit 630 sets or releases the connection according to the data type information. The second transmitting / receiving unit 640 transmits / receives the data to / from the second node. The session management unit 630 may control the second transmission / reception unit 640 to transmit / receive the data to / from the second node in a connection mode corresponding to the data type information. When the first transmission / reception unit 620 receives the data type information, the first transmission / reception unit 620 can transmit connection method information corresponding to the type information to the first node. If the first node is a device node, the second node is a base node, and conversely, if the first node is an infrastructure node, the second node can be a device node. In addition, the connection method may include at least one of a connection method of the data type information with the first node and a connection method with the second node, and the first transmission / reception unit 620 Upon receiving the data type information, connection method information corresponding to the type information may be transmitted to the first node. Also, when the type information is changed, the second node may be informed of the change of the type information.

7 is a diagram illustrating a configuration of a base node or a device node according to an embodiment of the present invention.

The base node or the device node is configured as 700 and the configuration is configured by an application 705, a data management unit 710, a first transmission / reception unit 720, a second transmission / reception unit 740, a session management unit 730, (750). The device management unit 750 may be optionally included.

In more detail, the device of FIG. 7 is an underlying node or device node, which transmits and receives data to and from an intermediate node. The application 705 controls data type information, and the first transceiver 720 receives the data type information of the data from the application. In addition, the data management unit 710 stores the data type information, and the session management unit 730 sets or releases the connection according to the data type information. The second transmission / reception unit 740 transmits / receives the data to / from the intermediate node.

The session management unit 730 can control the second transceiver 740 to transmit and receive the data to and from the intermediate node in a connection mode corresponding to the data type information. The device management unit 750 may optionally be included and monitors the physical condition of the device 700.

The type information includes at least one of the type of the data, the occurrence frequency of the data, and the importance of the data. The second transceiver 740 transmits the type information to the intermediate node, Information on the connection method corresponding to the information can be received from the intermediate node. In addition, the first transceiver 720 receives a message indicating the change of type information from the application 705, the session manager 730 transmits the changed type information to the intermediate node, The second transmission / reception unit 740 can be controlled to receive the connection method information corresponding to the type information.

In order to support retransmission of data transmitted to an intermediate node, the apparatus 700 of FIG. 7 may further provide a function of storing loss data until an ACK is confirmed after data transmission have. 7, the apparatus of FIG. 7 further includes a loss data control unit, wherein the lossy data control unit stores the lost data by checking whether the data transmitted by the second transmission / reception unit is lost, And controls the transmission / reception unit 740 to retransmit the lost data.

6 and 7, when a system including the devices as shown in FIG. 6 and FIG. 7 is implemented, data types processed in the M2M service, such as normal row data generated from M2M devices such as sensors, event data such as alarms, It is possible to provide efficient resource management considering the data processing state and system state information of M2M entities and to provide reliability such as lost data recovery in case of failure by applying an application level efficient connection setting control technique.

According to an embodiment of the present invention, the M2M data to be processed for providing the M2M service is classified according to the service characteristic from the viewpoint of the M2M service provider, Can be controlled. That is, the M2M data type can be classified into regular low-level data generated from a device such as a sensor, event data such as an alarm, and control data for controlling the device. Also, the underlying node or device node can granularly classify data in a periodic or non-periodic manner from the data control perspective for each data type it uses. Also, event data may be classified into major or minor event data, and differential connection or dynamic connection control techniques may be applied to each of the event data.

The connection setting method for each of the M2M data is initially set statically and the connection setting method is dynamically changed according to the data processing state and the system state information during the system operation, And to maintain a resource state below the reference level at which the intermediate node can operate stably.

The initial connection setup of the M2M data may be based on a periodic or non-periodic control data generated in the base node, such as a Temporary / Request-Response or a Permanent / Request-Response connection Way ACK (One-Way Acknowledge), a temporary / one-way ACK (One-Way ACK) according to the periodic event data (Major / Minor) ) Connection setting method. In addition, non-periodic raw data generated from devices such as sensors can be classified into permanent, one-way, temporary, or one-way connection according to periodicity or non-periodicity. have.

As the above-mentioned data connection setting, the unidirectional method is a connection setting mode in which data is transmitted in one direction, there is no feedback on the reception result, and protection against data loss is not provided. The unidirectional ACK scheme is a form of data connection setting in which data is transmitted unidirectionally and a response is received from the other party. In case that ACK is not received due to a system failure or the like, the unidirectional ACK connection setup method can retransmit data lost during system recovery by application level connection setting control. In addition, the request-response method is a form of data connection setting that confirms the response to the processing result from the other party to the control data request from the viewpoint of the M2M application service provider.

In addition to the data connection setting method, the connection method can be divided into a continuous method or a temporary method according to a method of maintaining a connection setting at the time of requesting a connection setup. The temporary connection method is a method of establishing a new connection each time data is transmitted, But it can save memory resources and is suitable for non-periodic data generation. On the other hand, unlike the temporary connection method, the persistent method maintains the data connection until the connection termination request, which is favorable in terms of load and performance, but may cause a waste of memory resources and is a suitable connection method when periodic data is generated.

In addition to providing the connection function between M2M nodes, that is, nodes and intermediate nodes, or between each CSF of the intermediate node and the base node, the connection control function of the application level of the AF and CSF of each node is combined with the M2M data to dynamically Manage resource status.

A function provided through the application level connection control between the AF and the CSF of each M2M node will be described below. First, the AF instructs the CSF to request the associated connection control information for establishing or releasing the connection, and instructs the connection control information to set or cancel the CSF connection for each data type. Second, the AF notifies the classification code change request to the CSF for detection notification of whether the cyclic event of the node is repeatedly generated. Third, the AF instructs the CSF to request a classification code change for the status information notification notified from the node or the intermediate node's CSF. In the CSF of the node and the intermediate node, status information on the CPU load and memory usage is checked, and when the reference value is exceeded, AF is notified. Detects whether or not the same repeated occurrence of M2M event data periodically generated and processed by the node and data loss is detected, and informs AF of the same.

I) the function of storing and managing the initial setting table between the CSFs of each node with respect to the classification code and connection establishment method for each M2M data type, ii) A function of dynamically updating and managing the CSF connection control setting table of each node in order to change the information of the application level connection control setting by the AF request instruction of the node, iii) And releasing the process associated with the release.

8-14 illustrate interactions between a device node, an intermediate node, and an underlying node according to an embodiment of the present invention. In an embodiment of the type information of the present invention, a data classification code divided into control data / event data / periodic data and periodic / non-periodic / main-non-main event is used, Method, and temporary / persistent / request-response / unidirectional ACK / unidirectional are presented as examples of the connection method. AF is an application function, and CSF is a common service function. The AF and CSF indicate whether each function or module of Figs. 8 and 10-14 is in the area of an application function or in the area of a common service function.

FIG. 8 is a block diagram illustrating interactions of modules or internal configuration functions of AF and CSF of each node of M2M according to an exemplary embodiment of the present invention. Referring to FIG.

The AF of the node 810 (M2M Device) and the base node 830 (Control Center) are nodes for initiating connection establishment and release, respectively. Accordingly, the AF of the two nodes includes a function of requesting the connection establishment control information to the CSF to instruct connection establishment and release for the corresponding data processing in the CSF or a module performing the function. The node 810 includes a connection setting information request indication function 811, a data type specific setting / release request function 812 and a data classification code change request indication function 813, Request indication function 831 and a data type-based connection setting / release request indication function 832. On the other hand, the intermediate node 820 provides a data type specific setting / release request indication function 821 and a data classification code change request indication function 822.

The CSF of each node includes a function of directly performing a process related to the connection and disconnection between CSFs of the nodes 810, 820 and 830 according to a request for AF, or a module performing the function.

The CSF of the node 810 includes a data type classification code setting management function 814, a data type connection setting / release function 815, a device load / memory status information check function 816, ), And loss event data detection function 818.

The CSF of the intermediate node 820 includes a data type-specific connection control information management function 824, a data type-specific connection setting / release function 825, and a gateway load / memory status information check function 826.

The CSF of the base node 830 includes a data classification type code setting management function 834, a data type specific connection setting / release function 835, and a loss event data detection function 836.

The AF of the node 810 and the intermediate node 820 includes a function 813 for requesting a change of the data classification code to the CSF for exceeding the reference value of the status information such as the respective CPU load and memory usage and the repeated occurrence of the periodic event data, 812). This is to control the processing load of the M2M data generated at the node 810 and the base node 830 by changing the classification code for the repeated occurrence of the periodic event data or over the reference value of the status information through dynamic connection setting change to be. This allows the resource usage of each node to be maintained in a steady state below the reference value.

The CSF of the node 810, the intermediate node 820 and the base node 830 stores and manages a classification code for each M2M data type and an initial setting table for the connection setting method for each classification code, A module for updating the initialization table dynamically by changing control setting information or a module for implementing the function.

The CSF of the node 810 checks the CPU load and memory status information of the module for detecting whether the cyclic event repetition is generated and notifies AF and the function of notifying the status information of the node 601 when AF exceeds the reference value, And a module implementing the function.

The CSF of the intermediate node 820 includes a function of checking the CPU load and memory status information of the intermediate node 602 and notifying the status information by AF when the reference value is exceeded, or a module implementing the function.

The CSF of the node 810 and the base node 830 detects ACK data not received from the intermediate node 820 with respect to the transmitted event data and control data, And a module for implementing the function.

The transmission / reception of type information between the intermediate node and the base / device node is performed by the data type type connection control information management function 824 and the data type classification code setting management function 814 and 834. On the other hand, the method for controlling the connection by data type is performed by connection establishment / release (815, 825, 835) for each data type of each node. Therefore, connection establishment / release (815, 825, 835) for each data type is included in the function of the session management unit of each node (810, 820, 830). However, the functions are not exclusively coupled to specific components, but functions that each component can perform are presented in parallel. For example, the functions of the first transceiver for transmitting and receiving information with the application at the base node or device node are all implemented at 814, 815, 834, and 835 as shown in FIG.

The dashed arrows in FIG. 8 illustrate interactions such as exchanging information or exchanging messages between AF and CSF, and the solid arrows show interactions exchanging data between CSFs.

9 is a table showing initial connection control information set and managed in the CSF of each node for data types according to an embodiment of the present invention. FIG. 9 shows data type information and connection (setting) method information corresponding to the type information.

Referring to FIG. 9, the CSF of the node 910, the intermediate node 920, and the base node 930 sets and stores initial connection control information for application level connection control for each M2M data type. The CSF of the node 910 and the base node 930 sets (912, 932) a data classification code for the data type, and the intermediate node 920 sets the classification code and information about the connection establishment method (922). When attempting to make a connection in the CSF of the node 910 and the base node 930 through application-level connection control, information on the data classification code, which is an embodiment of data type information, (920). This connection setting control information performs update synchronization dynamically between devices upon request of classification code change by the instruction of AF.

The data type and connection establishment method of FIG. 9 are classified into Non-Periodic or Periodic in 914, 924, and 934 and data characteristics (control / event / non-periodic). And event data consist of major event and minor event even periodically. Each data classification code is 001, 002, 003, 004, 005, 006, 007, and it is possible to confirm what kind of data it is through this classification code.

Meanwhile, the connection method (connection establishment method) according to each data type is either temporary, persistent, request-response or one-way ACK, or unidirectional without ACK processing Can be set differently.

10 to 14 show the interactions among the devices according to an embodiment of the present invention. Each of the functions (modules) in Figs. 10 to 14 is replaced by the description of Fig. 8 of the same reference numeral.

10 is a flowchart illustrating an operation flow for connection control between AF and CSF in each device and connection establishment between CSFs of each device for seamless raw data and event data according to an embodiment of the present invention.

The AF of the node 1010 requests connection control information on the connection setting of the corresponding M2M data to the CSF (S1051). The CSF of the node 1010 requests the connection setting method information of the classification code of the corresponding data to the CSF of the intermediate node 1020 in response to the AF request, and the CSF of the intermediate node 1020 requests The connection establishment method is searched to provide information on the connection establishment method to the CSF of the node 1010 (S1052).

In the AF of the node 1010, the CSF instructs the CSF of the intermediate node 1020 to establish connection with the classification code and connection establishment method of the corresponding M2M data (S1053).

In the CSF of the node 1010, a connection is established according to the connection establishment method between the CSFs of the intermediate node 1020 at the request of the AF (S1054). Also, connection is established between the intermediate node 1020 and the CSF of the base node 1030 using the same connection establishment method (S1055).

11 is a flowchart illustrating an operation flow for connection control between AF and CSF in the device and connection establishment between CSFs of each device for M2M device control data according to an embodiment of the present invention.

In the AF of the base node 1130, connection control information for the connection setting of the corresponding M2M control data is requested to the CSF (S11510). The CSF of the base node 1130 requests the connection establishment method information of the classification code of the corresponding data to the CSF of the intermediate node 1120 in response to the request of the AF and the CSF of the intermediate node 1120 requests And provides information on the connection establishment method to the CSF of the base node 1130 (S1152). In step 1153, the AF of the base node 1130 instructs the CSF to establish connection with the CSF of the intermediate node 1120 according to the classification code and connection establishment method of the corresponding M2M data.

In the CSF of the base node 1130, a connection is established according to the connection establishment method between the CSFs of the intermediate node 1120 at the request of the AF (S1154). Also, a connection is established between the intermediate node 1120 and the node 1110 using the same connection establishment method (S1155).

In the connection of S1155, the CSF of the intermediate node 1120 confirms the execution result of the control request of the base node 1130 from the node 1110, and the intermediate node 1120 connects the base node 1130 using the connection of S1154. Lt; RTI ID = 0.0 > CSF < / RTI >

12 is a flowchart illustrating a process of changing and controlling a connection mode according to an embodiment of the present invention. 12, in order to maintain the CPU load and the memory usage of the node 1210 and the intermediate node 1220 at a certain level or lower, connection control between AF and CSF in each device for dynamically controlling connection information change, and CSF And shows the operation flow for establishing the connection between the nodes.

The CSF of the node 1210 checks the CPU load state or the memory usage amount of the node 1210 and notifies the AF of the information of the CPU load state or the memory usage amount (S1251). The AF of the node 1210 confirms the above information notified by the CSF and instructs the CSF to request the change of the classification code for the corresponding M2M data type being processed (S1252). At this time, when the CPU load condition exceeds the reference value, the classification code change criterion changes the classification code as the continuous connection type and the continuous connection method as the temporary connection method when the reference level value of the memory usage is exceeded Change the classification code. In addition, the response method can be changed (request-response, unidirectional ACK, etc.). The node 1210, the intermediate node 1220, and the base node 1230 according to the request of the AF (S1253, S1254).

Then, the AF of the node 1210 requests connection control information on the connection setting of the corresponding M2M data to the CSF. In the CSF of the node 1210, the corresponding request received from the CSF of the intermediate node 1220 The changed connection setting method for the classification code of the data is transmitted to the AF (S1255).

In step S1256, the AF of the node 1210 requests connection establishment with the CSF of the intermediate node 1220 according to the classification code and the connection establishment method of the corresponding M2M data changed to the CSF.

In the CSF of the node 1210 receiving the request, a connection is established according to the connection establishment method between the CSFs of the intermediate node 1220 according to the AF request (S1257). Also, a connection is established between the intermediate node 1220 and the CSF of the base node 1230 using the same connection establishment method (S1258).

The process of changing the connection control information for checking the CPU load and the memory status information for the components performing the gateway0 function in the intermediate node 1220 is processed in the same manner as the above procedure, Load / memory status information check is done.

13 is a diagram illustrating a process of changing and controlling a connection scheme according to another embodiment of the present invention. 13 is a flowchart illustrating an operation for connection control between AF and CSF in each device and for setting connection between CSFs of each device for detecting whether the same event data periodically generated in the node 1310 is repeated or not, Flow.

The node 1310 detects whether the same event data that is periodically generated is repeated or not, and notifies AF thereof of the information (S1351). The periodic event repetition generation detection function (or module 817) performs the processes of S1371 to S1374. That is, in order to confirm the repetition of the periodic event, the data classification code is confirmed (S1371), the previously processed data classification codes are compared (S1372), and if the classification codes match (S1373) (S1374).

The AF of the node 1310 instructs the CSF to change the classification code of the event data to the above information notified from the CSF (S1352). At this time, the classification code change is changed from the classification code of the unidirectional ACK connection setting method of the corresponding M2M event data to the classification code of the unidirectional connection setting method. Thereafter, synchronization update is performed between the CSFs of the node 1310, the intermediate node 1320, and the base node 1330 dynamically based on the classification code change according to the AF requesting instruction (S1353, S1354).

In the AF of the node 1310, the connection control information for the connection setting of the corresponding M2M data is requested to the CSF. In the CSF of the node 1310, the corresponding data received from the CSF of the intermediate node 1320 The changed connection setting method for the classification code is transmitted to the AF (S1355).

In step S1356, the node 1310 requests the CSF of the intermediate node 1320 to establish connection with the classification code and connection establishment method of the corresponding M2M data changed to the CSF.

In the CSF of the node 1310, a connection is established according to the connection establishment method between the CSFs of the intermediate node 1320 at the request of the AF (S1357). Also, a connection is established between the intermediate node 1320 and the CSF of the base node 1330 using the same connection establishment method (S1358).

14 is a diagram illustrating a data loss recovery process according to an embodiment of the present invention. If ACK data is not received from the intermediate node 1420 for the non-periodic event data or the periodic major event data transmission of the node 1410, the AF and CSF in each node for recovering the loss of the corresponding data, And the connection establishment between the CSFs of the respective nodes.

The node 1410 checks the ACK data from the intermediate node 1420 to confirm that it has received normally from the intermediate node 1420 for the transmitted aperiodic event data or the periodic main event data. In the node 1410, (S1451), the detection of the data loss as a classification code of the corresponding event data lost at the time of non-receipt of ACK data N times from the ACK data 1420 is notified. In step S1473, it is determined whether the transmitted non-periodic event or periodic main data is normally received (S1471). If the ACK is not received (S1472), and the non-periodic event is repeated (S1473) (S1474). In this process, the node 1410 provides storage and retransmission functions for the lost data. If the acknowledgment of the transmitted data can not be confirmed directly or indirectly, the transmitted data can be temporarily stored.

In step S1452, the node 1410 requests connection control information for the connection setting of the corresponding M2M data to establish a connection for retransmission of the lost data to the information of the S1451 notified from the CSF.

The CSF of the node 1410 requests the connection establishment method information of the classification data of the corresponding loss data to the CSF of the intermediate node 1420 in response to the AF request. The CSF of the intermediate node 1420 requests And provides it to the CSF of the node 1410 (S1453).

The AF of the node 1410 requests connection establishment with the CSF of the intermediate node 1420 according to the classification code of the corresponding M2M data and the connection establishment method in the CSF (S1454).

In the CSF of the node 1410, a connection is established according to the connection establishment method between the CSFs of the intermediate node 1420 at the request of the AF (S1456). Also, a connection is established between the intermediate node 1420 and the CSF of the base node 1430 using the same connection establishment method (S1457).

15 is a diagram illustrating a process of dynamically controlling transmission / reception of data in the M2M system according to an embodiment of the present invention.

In FIG. 15, if the first node is a device node, the second node may be an infrastructure node, and conversely, if the first node is an infrastructure node, the second node may be a device node. Fig. 15 shows an operation occurring at a first node, a second node and an intermediate node transmitting and receiving data therebetween.

When the application of the first node determines the data type information and transmits the determined information to the intermediate node (S1510), the intermediate node stores the received data type information, and according to the data type information, (S1520). The intermediate node then transmits information on the determined connection mode to the first node (S1530). The intermediate node may further include a step of transmitting information on the connection method to the second node.

Thereafter, an application of the first node generates data and transmits the data to the intermediate node. When the intermediate node receives data from the first node, the intermediate node transmits data to the second node (S1540).

As described above, according to the present invention, the data types processed in the M2M service such as illumination control, intruder video surveillance, fire alarm, air conditioning, that is, the intermittent processing of the M2M It is possible to provide a dynamic application-level connection control method to provide an M2M service while maintaining a stable resource state for data to be transmitted.

According to the present invention, in order to provide reliability of data loss recovery for a specific data type according to the demand of an M2M application service provider even if a node or an intermediate node (M2M Gateway) is recovered after a failure, The method can be changed and controlled at the application level.

The foregoing description is merely illustrative of the technical idea of the present invention and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.

110: Application
120: Common Services
130: Infrastructure Network Services
600, 820, 920, 1020, 1120, 1220, 1320, 1420:
810, 910, 1010, 1110, 1210, 1310, 1410:
830, 930, 1030, 1130, 1230, 1330, 1430:

Claims

An intermediate node for transmitting and receiving data to and from a first node and a second node,
A first transceiver for transmitting and receiving the data with the first node and receiving the data type information from an application included in the first node;
A data management unit for storing the data type information;
A session management unit for establishing or releasing a connection according to the data type information; And
And a second transceiver for transmitting and receiving the data to and from the second node,
And the session management unit controls the second transmission / reception unit to transmit and receive the data to and from the second node in a connection mode corresponding to the data type information.

The method according to claim 1,
And when the first transmission / reception unit receives the data type information, transmits the connection mode information corresponding to the type information to the first node.

The method according to claim 1,
Wherein the second node is a base node if the first node is a device node.

The method according to claim 1,
And the second node is a device node if the first node is an infrastructure node.

The method according to claim 1,
Wherein the connection method includes at least one of a connection method with the first node and a connection method with the second node with respect to the data of the data type information.

The method according to claim 1,
Wherein the intermediate node further comprises a device management unit for monitoring a physical condition.

The method according to claim 1,
And the second transceiver transmits information on the connection mode to the second node.

An apparatus for transmitting and receiving data to and from an intermediate node,
An application that controls data type information;
A first transceiver for receiving data type information of the data from the application;
A data management unit for storing the data type information;
A session management unit for establishing or releasing a connection according to the data type information; And
And a second transceiver for transmitting and receiving the data to and from the intermediate node,
And the session management unit controls the second transmitting and receiving unit to transmit and receive the data to and from the intermediate node in a connection mode corresponding to the data type information.

9. The method of claim 8,
Wherein the device is a device node or an underlying node.

9. The method of claim 8,
Wherein the device further comprises a device management unit for monitoring a physical condition.

9. The method of claim 8,
Wherein the type information includes at least one of a type of the data, a frequency of occurrence of the data, and an importance of the data.

9. The method of claim 8,
Wherein the second transceiver transmits the type information to the intermediate node and receives connection method information corresponding to the type information from the intermediate node.

9. The method of claim 8,
Further comprising a loss data control unit for storing the lost data by checking whether the data transmitted by the second transmission / reception unit is lost or not, and controlling the second transmission / reception unit to retransmit the lost data.

9. The method of claim 8,
Wherein the first transceiver receives a message indicating a change of type information from the application,
Wherein the session management unit transmits the changed type information to the intermediate node and controls the second transmission / reception unit to receive connection method information corresponding to the changed type information.

An M2M system comprising a first node, a second node and an intermediate node for transmitting and receiving data between the first node and the second node,
The application of the first node determining the data type information and transmitting the determined information to the intermediate node;
The intermediate node storing the received data type information and determining a connection mode according to the data type information;
The intermediate node transmitting information on the determined connection scheme to the first node;
The application of the first node generating and transmitting data to an intermediate node; And
And the intermediate node transmitting the data to the second node using a connection scheme according to the data type information of the received data.

16. The method of claim 15,
And if the first node is a device node, the second node is a base node.

16. The method of claim 15,
And the second node is a device node if the first node is an infrastructure node.

16. The method of claim 15,
And wherein the intermediate node further comprises transmitting information about the connection scheme to the second node.

16. The method of claim 15,
Wherein the first or second node checks whether the transmitted data is lost, stores the lost data, and controls to retransmit the lost data.