KR20150002238A

KR20150002238A - M2M System comprising intermediate node with priority alteration and switching function

Info

Publication number: KR20150002238A
Application number: KR1020130075818A
Authority: KR
Inventors: 이원영
Original assignee: 주식회사 케이티
Priority date: 2013-06-28
Filing date: 2013-06-28
Publication date: 2015-01-07

Abstract

The present invention relates to a M2M (Machine to Machine Communication) technology, and provides a method for efficiently managing connection and data transmission of Nodes through a function provided by a CMF in a CSE connected to a plurality of nodes. Priority is given to NODEs connected to CSEs with limited resources, and then managed dynamically so that the connection with CSEs with Nodes can be effectively managed. Based on this, it is possible to efficiently collect data through the Node.

Description

[0002] The present invention relates to an M2M system including an intermediate node having a priority changing function and a switching function,

The present invention relates to a M2M (Machine to Machine Communication) technology, and provides a method for effectively managing connection and data transmission of Nodes through a function provided by a CMF in a CSE connected to a plurality of Nodes.

"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.

In the case of the existing M2M system, when multiple nodes are connected to the CSE and data is exchanged, the resources available to the CSE are limited if the maximum number of nodes that the CSE can reach is limited, At least one of the nodes in the network eventually became unable to communicate with the CSE, so the service or function did not work properly.

In order to solve these problems and operate as a stable system, a special method is needed. The proposed method guarantees the connection of the new node and suggests a method that can collect and process the data sent by the connected node.

The present invention prioritizes NODEs connected to a CSE having a limited resource, and dynamically manages the NODEs so that the connection with the CSEs with the Nodes can be effectively managed. Based on this, it is possible to efficiently collect data through the Node.

The dynamically changed priority is determined by the order of the result of analyzing the data transmitted by the NODE to the CSE. Also, the present invention proposes a rank setting and management method, a message transmission method, and a data type and a processing method included in a message for efficiently managing Nodes.

In order to solve the above problem, it is necessary to determine the priority of the nodes dynamically, analyze the collected data in real time, and control the communication with the nodes. In addition, an M2M system consisting of Nodes capable of receiving and processing CSE control commands is needed.

An expanded performance CSE that can manage connections by dynamically assigning priorities to nodes by analyzing the information sent by the nodes can collect data from the nodes while varying the communication connection of the nodes according to the importance of the data have. This is different from the case where the CSE refuses to provide a function or data reception for a new node due to a shortage of available resources or simply terminates the connection to terminate the connection. Data collection is possible even if there are restrictions on resources.

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.
FIG. 6 shows the contents and procedures of the CSE in order to process a connection request of a new node based on priority information.
7 shows an operation of selecting a child Node to communicate with a new Node and deactivating communication.
FIG. 8 shows an operation for managing Nodes by prioritizing after a new Node connection.

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.

In the present invention, when the communication function between the nodes and the CSE is activated in the M2M system, when the CSE can use the X reference point only up to the number of nodes P due to the resource limitation, when the (P + 1) As an example.

In the existing M2M system, even if the new P + 1th Node P 'requests and uses the function provided by the CSE's CSF, since several nodes are simultaneously connected and communicating, the resources are insufficient. Therefore, the function can not be used normally.

If it is necessary to exchange information between the Node P 'and the CSE, it is only necessary to terminate the communication of the other Node in communication, not the Node P', so that the CSE secures resources for communication with the Node P '. In this case, it is general that the connection of other nodes which were in communication is not resumed.

To solve these problems, the method proposed by the present invention has the following features.

The CSE selects the node with the lowest priority through the priority information managed by the nodes, releases the resources to allow the new node P 'to communicate, and the node with which communication has been canceled returns again after a certain time designated by the CSE Use the method to request and resume communication.

In addition, a Node whose communication is suspended or delayed because it has the lowest priority must be able to receive control information sent by the CSE before the communication is interrupted. This control information includes time information for resuming the communication request after the stop, and the Node resumes communication after the specified delay time.

For this purpose, the communication management / transfer handling function (CMF) among the various functions of the CSE includes a function of having a management table for connected nodes. Also, priority information of each node is managed. Data analysis is performed on the transmission data of each of the collected Nodes through the data management and storage function, and priority is generated and managed by matching each node.

The priorities for the nodes communicating with the CSE are generated by classifying and generating data using the following methods A and B in sequence, and selecting the lowest-ranked node as the communication-stopped node.

Method A) Classification of transmission period

- Nodes with irregular data transmission cycle / Nodes with constant data transmission cycle

Method B) Data type Priority classification method

One). A series of continuous / discontinuous transmission data that requires continuous transmission, including stream data such as video, sound, etc., takes precedence over items 2), 3) and 4). However, in the case of data being caught easily by the cognitive ability at the time of data interruption, or in the case of the status data sent by the node which is responsible for checking status information such as the risk, it is classified into the following 2), 3) and 4) Even with data, priority is given to the highest priority.

2) Data that can not determine the range (band) of the measured value even if it is Alpha Numeric data takes precedence of 3).

3) Data determined as abnormal range value among the data which can calculate range of data shall take precedence of 4).

4) Among the data that can calculate the range of the data, the data determined as the normal range value has the lowest rank

In order to prioritize Nodes by applying Method A) and Method B), CSE shall follow the procedure described in method C) as follows.

Method C) How to choose a priority-based disconnect node

end. CSE analyzes and stores the data transmission cycle of each node based on data reception times.

I. Each Node is referred to as' A. Transmission period classification method 'into two groups.

All. For each group, search for the lowest priority Node with the following rule.

- Newly connected nodes are given top priority until they are connected.

- Rank each node according to 'data type priority classification mechanism'

- 1 group) and 2 subgroups) have the same rank, then 1 group of Nodes takes precedence over Node.

la. CSE matches the transmission cycle by Node or x-reference and manages it with ranking.

hemp. Each Node receives a message from the CSE that specifies the next reconnection and transmission time before it is disconnected because its priority is low.

bar. A disconnected node saves the collected data inside the Node and sends it on reconnection.

four. The CSE performs the operation for specifying the reconnection / transmission time using the transmission cycle information for the lowest-order node, and transmits the message to the lowest-order node before the connection is disconnected.

FIG. 6 shows the contents and procedures of the CSE in order to process a connection request of a new node based on priority information.

7 shows an operation of selecting a child Node to communicate with a new Node and deactivating communication.

FIG. 8 shows an operation for managing Nodes by prioritizing after a new Node connection.

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

Claims

For each node that composes the M2M system and transmits the data to be collected, and the data transmitted by each node
An M2M system with a Common Service Entity that prioritizes Node or x reference values according to data analysis results and switches communication activation / de-energization according to rank