KR20150002412A - A method for dependable M2M data transport using secondary intermediate node - Google Patents

Abstract

The present invention relates to a method for transmitting a machine to machine communications (M2M) data with reliability using a secondary node in an M2M system. More specifically, an intermediate node (secondary node) connected to an end node through a session used to transmit data at a specific time point is constructed for the backup of an intermediate node (primary node). If the primary node receives data from the end node, the primary node transmits the data to the secondary node. The end node is connected to the secondary node to allow the secondary node to recover an existing transmission session and an existing context to transmit the data when the primary node has faults, and thus, can not transmit/receive data, thereby transmitting data with reliability.

Description

[0001] The present invention relates to a method for transmitting a reliable M2M data using a secondary node,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an M2M (Machine to Machine Communication) technology, and more particularly to an M2M (Machine-to-Machine) To be used as a backup, thereby reliably transferring data.

"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 existing technology, the End Node application refers to the CSE of one intermediate node and the application does not provide a method for continuously transmitting the data when the reference CSE of the intermediate node fails to operate because of an error. In addition, when storing and transmitting M2M data at an intermediate node, it does not provide a method for recovering the stored data.

If the end node needs to transmit important data at a certain time, for example, if the intermediate node with the corresponding node does not operate at the time of transmitting important data from a factory, a nuclear power plant, or a medical device, have.

In order to solve the above-described problem, the present invention provides an intermediate node (hereinafter referred to as a secondary node) for backup of an intermediate node (hereinafter, referred to as an " intermediate node " When data is received from the Node, it is transmitted to the Secondary Node. When the Primary Node fails to transmit or receive data, the End Node connects to the Secondary Node, and the Secondary Node recovers the existing transmission Session and Context to transmit the data. This is a method for reliably transmitting data.

Unlike the conventional backup server technology, the present invention dynamically constructs a secondary node only when important data is transmitted in order to remove the inefficiency of constructing an intermediate node in a redundant manner, and releases the secondary node when it is not needed. Also, unlike the conventional backup server technology, the secondary node can operate as a primary node for other end nodes and functions as a general intermediate node to optimize the resources of the intermediate node.

For the above purpose, a method for achieving the object of the present invention is devised based on the architecture and requirements proposed in oneM2M as an M2M system architecture for implementing this.

In the M2M system, when an Intermediate Node (Primary Node) that is connected when an important data is transmitted in an application is interrupted, an Intermediate Node (Backup Node) is set up in advance and when the application receives data, So that reliable data transmission can be achieved.

The present invention does not require a separate backup node by utilizing an intermediate node that is normally operating as a backup node. In the present invention, since the secondary node can be dynamically set and released only when reliable data transmission is required in the application, the load of the M2M system is reduced in performing the backup.

It also has the advantage of being applicable to various fields based on international standard documents.

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 system configuration and a data transmission flow in the present invention.
FIG. 7 shows a configuration and a data flow when the primary node fails in FIG. 6 according to the present invention.
8 is a procedure for setting a reliable data transmission interval.
9 is a procedure for transmitting data when the primary node is normal
10 is a procedure for transmitting data when the primary node is abnormal.
11 is a procedure for releasing a reliable data transmission interval.
12 is a data structure for the present invention.
13 is a diagram showing the operation of the DMR CSF applied in the present invention.
14 is a diagram showing a configuration of a system constituting the present invention.
Fig. 15 is a diagram showing a system constituting the present invention from a functional viewpoint at a high level.
16 is a diagram showing a functional structure constituting the present invention.
FIG. 17 is a diagram illustrating a common service entity according to an exemplary embodiment of the present invention. Referring to FIG.
18 is a diagram illustrating a communication flow at a reference point according to an embodiment of the present invention.
19 is a diagram illustrating an architecture of a common service object to which an embodiment of the present invention is applied.

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.

Common Service Functions (CSFs) for implementing the present invention include Identification, Communication Management / Delivery Handling, Session Management, Data Management & Repository, Discovery ). Identification The CSF provides a function to determine which application and application group the data transmitted from the intermediate node and the infrastructure node belongs to. In the present invention, the Delivery CSF processes the transmission protocol and transmits or processes data based on the Delivery Policy. In the present invention, the Session Management CSF manages the session between the application and the CSE. In the present invention, the Session Management CSF includes session establishment and management between the primary node and the secondary node. Data Management & Repository CSF manages data transferred from applications. Secondary Node stores data as much as backup window which is the size of data storage space for backup requested from Primary Node. In the present invention, the Discovery CSF functions to find a node operable as a secondary node around an intermediate node requesting a secondary node setup.

With the CSF as described above, the present invention has a system configuration as shown in FIG. The following describes the scenario of transferring data from End Node's application in this system component.

6 and 6-1), the Identification CSF and the Session Management CSF check the identifier (or application ID) of the application transmitting the data and the currently transmitted Session, and a secondary node is set Ensure that the session is transmitting data. (FIGS. 6 and 6-2). According to the delivery policy, data is stored. When the secondary node is set, context and data are transmitted to the secondary node (FIGS. (FIGS. 6 and 6-5) In the secondary node receiving the context and data from the primary node, it is checked whether the primary node and the generated session are for backup (FIGS. 6 and 6) 6, 6-7) In case of the backup session, the data is not transmitted to the Infrastructure Node, and the data received normally is transmitted to the Infrastructure Node (FIGS. 6 and 6-8). (Figs. 6 and 6-9)

When the primary node fails in the system configuration shown in FIG. 6, the data transmission session is restored and the data is transmitted to the secondary node as shown in FIG.

If the primary node fails, the application uses the secondary reference information to connect to the secondary node and send recovery information to recover the session. (FIGS. 7 and 7-1). In the secondary node, applications are distinguished (FIGS. 7 and 7-2), and the session that was being backed up is recovered with the recovery information transmitted from the application (FIGS. 7 and 7-3) When the data is transmitted, it compares the context / data and transmits the data to the infrastructure node according to the Delivery Policy. (Fig. 7, 7-4) In the Infrastructure node, related data is transmitted to the application. (FIGS. 7 and 7). Also, for the corresponding session between the end node and the secondary node, the secondary node operates as a primary node and negotiates with another intermediate node to designate a secondary intermediate node for backup. (Figs. 7 and 7-6)

FIG. 8 is a process for setting a secondary intermediate node for reliable data transmission in the present invention.

In an end node application (Application 1, for example), when an intermediate node A (primary node) is connected and a session is created (for example, Session 1, Fig. 8 and 8-1) It is determined whether or not to transmit. (Figs. 8 and 8-2) Data is transmitted without a secondary node unless it is necessary to transmit important data. (Figs. 8 and 8-4). When it is necessary to transmit important data, a request is made to the intermediate node A, which is currently connected, to set up a secondary node. (FIGS. 8 and 8-3) Intermediate Node A, which receives a request of 8-3, requests a list of secondary nodes available to the infrastructure node. (FIGS. 8 and 8-5) In the Infrastructure Node, intermediate nodes managed by an Infrastructure Node are transmitted according to a specific setting (for example, local device only or capacity based) (FIGS. 8, 8-6 ) Intermediate A selects the corresponding intermediate node (for example, Intermediate Node B) and establishes a session. (Eg Session 2, Figure 8, and 8-7) and sends back up request to the corresponding intermediate node after session setup. (FIG. 8, 8-8) At this time, the transmitted information includes application information (Application 1) of the end node requesting a reliable data transmission interval, session information (Session 1) set with the corresponding application and the intermediate node, Window, and Timeout. The intermediate node B receiving the backup request checks and secures the storage capacity according to the backup window, checks the processing capacity of the intermediate node B, determines whether it is acceptable, and forms a data structure for the backup. (Fig. 8, 8-9) The information to be stored at this time includes End Node Application information (Application 1), Session information (Session 1) between the application and the primary node to be backed up, Intermediate Node information requesting the Backup, Session information (Session 2) and Backup Window are included. (FIGS. 12 and 12-3) When the intermediate node B receives the backup request, the intermediate node A stores the corresponding information. 8, 8-10). Information stored at this time includes End Node Application information (Application 1), Session information (Session 1) generated between the end node and the primary node, Backup session information (Session 2) Secondary Node information (Node B), Backup Window, Available Time, etc. (Figs. 12 and 12-2). Then the Primary Node sends Secondary Node information to the End Node Application. (Intermediate Node B, Session 2) In the end node application, Intermediate Node A and Session 1 are stored as primary reference information and Intermediate Node B, Session 1 and Session 2 are stored as secondary reference information. (Fig. 8, 8-11, Fig. 12, and 12-1) When the secondary reference information is set, important data starts to be transmitted. (FIGS. 8 and 8-12) In FIG. 8, 8-13 is a period for transmitting data in general and a reliability transmission period after a secondary reference is set. (Figs. 8 and 8-14)

FIG. 9 is a flowchart for normally transmitting data when a secondary node is set.

When the secondary node is configured, it checks whether the primary reference is normal when data is generated in the end node application (for example, Application 1, Session 1 formation with the primary node). (FIGS. 9 and 9-1) A method of checking whether the primary reference is normal may be various methods such as confirming the network connection with the primary node or confirming that an ACK is sent when specific data is sent. If it is judged that the primary reference has failed, the transmission scenario starts with the secondary reference. (FIGS. 9 and 9-3) The secondary reference transmission scenario is described in FIG. If the primary reference is normal, data is transmitted to the primary reference. (Application 1) and Session (Session 1) in the Secondary Node setting information (FIG. 12, 12-2) are received by the Secondary Node Is set. (Fig. 9, 9-4) If the secondary node is not set, data is transmitted to the infrastructure node as in the case of transmitting general data. In the infrastructure node, data is transmitted to the related application. (FIG. 9, 9-5, 9-6) If a secondary node is set in 9-4, the secondary node (Intermediate Node B) and the connection session (Session 2) are inquired in the secondary node setting information And transmits the data and the context to the secondary node. In the Secondary Node, it is checked whether the Session (Session 2) of the primary node is a Backup Session in the Backup setting information (Figs. 12 and 12-3) (Fig. 9 and 9-9) And stores the data. (FIGS. 9 and 9-10) When the backup is completed in the secondary node, the primary node stores the data in the corresponding node and transmits the data to the infrastructure node according to the delivery policy. (Fig. 9, 9-11) In Infrastructure Node, relevant data is transferred to related application, and Application processes data. (Figs. 9, 9-12, 9-13)

10. Is a flowchart for transmitting data when a primary node fails.

When data is transmitted in an end node application (Application 1, for example), it is checked whether the reference of the primary intermediate node is normal (FIGS. 10 and 10-1). If the primary reference fails, the secondary reference information is inquired. (Fig. 10, 10-2, Fig. 12, and 12-1), connects to the secondary node, and creates the secondary node and the session. (For example, Session 3, FIG. 10, and FIG. 10-3), and then the end node application transmits backup session information. (Session 1, Session 2) In the Secondary Node, confirm the backup setting information (FIGS. 12 and 12-3) in the application distinguisher Application 1, Session 1, and Session 2 to see if it is the backup session. (FIGS. 10 and 10-4). If the session is not the backup session, the reference connection is rejected (FIGS. 10 and 10-5) and the flow ends. If the session was backed up, release the backup information and allow connection to the reference. 10 and 10-6). The end node application transmits the context and data to the reference of the secondary intermediate node (FIGS. 10 and 10-7), and the intermediate node B confirms the context and data (FIG. 10, And transmits the stored data to the Infrastructure Node according to the Delivery Policy. (Fig. 10, 10-9) The Infrastructure Node receives the corresponding data and transmits the data to the application, and the application processes the related data. (FIGS. 10, 10-10, and 10-11) Intermediate Node B starts a scenario of setting a secondary node when data and reference are restored. (FIGS. 10 and 10-12) This scenario applies the process from 11-5 to 11-10 in FIG. When the secondary node setup is completed, related information is transmitted to the end node, and in the end node application, the primary reference and the secondary reference information are updated and the process is terminated. (At this time, the Primary Node becomes the Intermediate Node B and the Secondary Node becomes the Intermediate Node C.)

11. Is the process of releasing the Secondary Node configuration. When a reliable data transfer interval is no longer needed in the end node application, a request to release the secondary node is sent to the primary node (for example, the intermediate node A). (FIGS. 11 and 11-1). The primary node receives the request of 8-1 and inquires the secondary configuration information (FIGS. 12 and 12-2) to inquire the secondary node that has been set (FIGS. 11 and 11-2) The information used is session information (Session 1) between Application 1, Primary Node, and Application. And sends a Backup release request to the Secondary Node as the inquired Secondary Node (Node B, Session 2). 11 and 11-3). At this time, Session information (Session 1) and Application distinguisher (Application 1) connected to the application are transmitted. The secondary node inquires the backup setting information (Figs. 12 and 12-3), releases the storage set in the secondary node, and deletes the backup setting information. (FIGS. 11 and 11-5), the secondary node deletes the secondary setup information (FIGS. 11 and 11-6) and deletes the primary / secondary reference information from the end node. 11 and 11-7). In FIG. 11, 11-9 is a reliable transmission interval and 11-10 is a normal transmission interval.

12. Is the main data structure of the present invention.

12-1 is primary / secondary reference information to be stored in the application of the end node which transmits data. Reference information includes application session information, which is an application-primary node session to be delivered when a primary node fails, and backup session information, which is a primary node-secondary node session. 12-2 is secondary configuration information to be stored in the primary node. A target application discriminator, an application session which is a currently set application-primary node session, a session between a primary node and a secondary node transmitting backup data, a backup node information, a backup window, and a validity time. The validity time is used to set the backup for a specific time. 12-3 is Backup setting information stored in the Secondary Node. Application ID that is being backed up, Application Session which is Application-Primary Node Session, Primary Node information, and Backup window information for data storage. According to the Backup Window, the Secondary Node creates a circular queue buffer and stores the Context and data. (Figs. 12 and 12-4)

In summary, the present invention supports a function of mirroring data of other CSEs for critical data recovery in the CSR (DMR CSF) responsible for data management & repository .

The operation of the DMR CSF applied in the present invention is shown in FIG.

In the description of the present invention, what is described as an end node includes an ASN or an ADN to be described later. In this regard, the following will be described in more detail.

In the present invention, identification refers to a process of recognizing an entity in a specific domain differently from other entities (recognizing an entity in a particular domain as different from other entities). Authentication is the process of determining the identity of an entity or establishing the source of the information. Authorization is the granting of rights, which involves assigning based on access rights (The granting of rights, which includes granting of access based on access rights). Confidentiality refers to a property that makes information unavailable or unavailable to unauthorized entities or processes. (This property is not available or disclosed to unauthorized individuals, entities, or processes.) . Credentials are data objects that are used in security procedures and are used to uniquely identify entities. (Data objects are used to uniquely identify entities and which are used in security procedures. . Encryption refers to the process of generating a plaintext as a ciphertext using a cryptographic algorithm and a key. (The process of changing a plaintext into a ciphertext using a cryptographic algorithm and key). Integrity means ensuring the accuracy and completeness of the processing of information and methods (Safeguarding the accuracy and completeness of information and processing 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 a reverse operation can not be performed (A parameter used in conjunction with a cryptographic algorithm that determines the operation in such a way that an entity with knowledge of the key can reproduce or reverse the operation, while an entity without knowledge of the key can not ). Mutual authentication refers to entity authentication that ensures mutual identity. (Entity authentication, which guarantees each other's identity). Privacy is the ability of individuals to control or influence information to be collected and stored by those who are to be exposed (see below). and to whom that information may be disclosed. Repudiation means denying an event or action requested from an entity. (Denial by an entity of a claimed event or action.) Secure means not to be vulnerable to all attacks, to resist vulnerable attacks or to recover damage from attacks in spite of vulnerabilities (not vulnerable to most attacks) Security is the state of the system that occurs by creating and maintaining a scheme to protect the system (for example, A system condition that results in the establishment and maintenance of measures to protect the system. Sensitive data refers to the classification of stakeholder data that causes problems if they are inadvertently known or tampered with without the consent of the affected stakeholder. If it is not possible, then it will not be possible for the owner of the affected stakeholder. 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. A subscription usually refers to a commercial agreement. (A classification of an agreement, where the agreement is between a provider and a subscriber for a period of time. 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, (a relationship between two elements, a set of activities and a security policy), and a trust relationship between the activity and the security policy. A well defined way (with respect to the activities) that does not violate the given security policy. Verification means confirmation through the provision of objective evidence that a particular requirement is satisfied. (Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled).

An M2M application is an application that runs service logic and uses an M2M common service with a specific open interface in oneM2M (applications that run the service logic and use M2M Common Services accessible via a set of oneM2M specified open interfaces. Specification of M2M Applications is not subject to the current oneM2M specifications). 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. (eg a set of physical servers of the M2M Application Service Provider) that manages data and executes coordination functions of M2M Application Services.

The M2M application service is implemented through the service logic of the M2M application, and is operated by an M2M application service provider or a user (an M2M application service is realized through the service logic of an M2M application and is operated by the User or an M2M Application Service Provider). An M2M application service provider is an entity that provides M2M application services to users (M2M Application Services to the 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 LAN (Local Area Network) can utilize heterogeneous communication technologies and may or may not support IP access (M2M Gateway (s), M2M Device (s), and Sensing & Actuation Equipment. M2M Local Area Networks can use heterogeneous network technologies that may or may not support IP access.

The field domain consists of M2M gateway, M2M device, sensing / actuation device, and M2M local network. Infrastructure Domain is composed of Infrastructure and Service Infrastructure (consists of M2M Devices, M2M Gateways, Sensing and Acting (S & A) Equipment and M2M Area Networks). 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 (M2M Application Services, which interacts with the M2M System, however does not host the M2M application) not host an 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. The M2M system refers to a system that implements or deploys an M2M solution (satisfying all the following criteria: 1. It satisfies the end-to-end M2M communication requirements of particular users; Some part of the M2M Solution is realized by including services compliant to oneM2M specifications). Underlying network means functions, networks, busses or other technologies for data transmission / connection services (Functions, networks, busses and other technologies assisting in data transport connectivity services).

14 is a diagram showing a configuration of a system constituting the present invention. FIG. 14 shows an application 110, a common service 120, and an underlying network service 130. This layered model comprises three layers: an Application Layer, a Common Services Layer the Underlying Network Services Layer. 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 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 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. 15 is a diagram showing a system constituting the present invention from a functional viewpoint of a high level. The Application Entity (AE) 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 (Application Entity (AE): Application Entity provides application logic for the end-to-end M2M solutions. Examples of the Application Entities can be fleet tracking application, remote blood sugar monitoring application, or remote power metering and controlling application. A common service entity (CSE) 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. An example is data management, device management, M2M subscription management, location service, and the like. The subfunctions provided by the CSE can be logically understood as a CSF (Common Service Function). Some of the CSFs within the CSE of oneM2M node are mandatory and some may be optional. Likewise, the subfunctions in the CSF can be either mandatory or optional (Common Services Entity (CSE): A Common Services Entity is the set of "service functions" that are common to the M2M environments and are specified by oneM2M. Subcontractors, Location Management, etc. M2M Subscription Management, Location Management, etc. These subfunctions are provided by the CSE: Data Management, Device Management, (CSFs), some of the CSFs can be mandatory and others can be optional. Also, inside a CSF, some subfunctions can be mandatory or (eg, inside a "Device Management" CSF, some of the subfunctions like "Application Software Installation", "Firmware Updates", "Logging", "Monitoring" ory or 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. (Underlying Network Services Entity (NSE): An Underlying Network Services Entity provides services to the CSEs. 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 application entity (AE) 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 object, and the application object and the common service object may reside in the same physical entity or in different physical entities. Entity and a CSE. The X reference point shall allow an Application Entity to use the CSE, and for the CSE to communicate with the Application Entity. The CSE. The Application Entity and the CSE it invokes may or may not be co-located within the same physical entity. 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 object (this is the reference point between two CSEs. The Y reference point SHOULD allow a CSE to use the services of another CSE in order to fulfill necessary functionality The reference point is the base network that provides the required functionality, and the reference point is the point where the two CSEs are supported by the CSEs. To enable a common service entity that wishes to use the service entity of the service entity, which provides services other than transport and connection. An instance of the Z reference point is implemented depending on the service provided in the underlying network. The exchange of information between two physical M2M nodes can use the transport and connectivity services of the underlying network to provide basic services (the Z-reference is a reference point between a CSE and the underlying network services entity). The point of reference is to provide the services that are provided by the underlying network services. The services provided by the underlying network services are as follows: Entity. Information exchange between two M2M nodes assumes the usage of the transport and connectivity services of the underlying network services entity.

16 is a diagram showing a functional structure constituting the present invention. In the Functional Architecture of FIG. 16, AE represents an application entity, and CSE represents a common service entity. (Application Dedicated Node, ADN), 313 and 314 denote Application Service Nodes (ASN), and 321 and 322 denote Middle (MN), and 330 denotes an infrastructure node (IN). 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 application specific nodes 311 and 312 are nodes including at least one application entity (AE) and not including a common service entity (CSE). The application dedicated nodes 311 and 312 communicate with the intermediate nodes 321 and 322 or the base node 330 using an X reference point. (An Application Dedicated Node is a Node that contains at least one Application Entity and does not contain a Common Services Entity An Application Dedicated Node communicates with a Middle Node or an Infrastructure Node over an X reference point.

The application service nodes 313 and 314 are nodes including one common service entity (CSE) and including at least one application entity (AE). The application service node communicates through the Y reference point as follows. Communicates with one intermediate node 321, or communicates with one base node 330. The communication scheme can communicate with exactly one intermediate node or base node. (An Application Service Node contains a Node that contains one Common Services Entity and contains at least one Application Entity. An Application Service Node may communicate over a reference point with either: exactly one Middle Node, or exactly one Infrastructure Node.

The intermediate nodes 321 and 322 are nodes including one common service entity (CSE) and including at least one application entity (AE). The intermediate node communicates with two or more nodes via the Y reference point as follows, which does not operate exclusively. Communicate with one or more application service nodes, communicate with one or more intermediate nodes, or communicate with one infrastructure node. The intermediate node can communicate with the application specific nodes 313 and 314 using an X reference point (A Middle Node is a Node that contains one Common Services Entity and may contain Application Entities. One or more middle nodes may communicate with one or more middle nodes, and one or more middle nodes may communicate with one or more other nodes (not exclusively).

The base node 330 is a node that includes one common service entity (CSE) and includes at least one application entity (AE). The intermediate node communicates with two or more nodes through the Y reference point as follows. Communicate with one or more intermediate nodes, and / or communicate with one or more application service nodes. Based node may communicate with application-specific nodes 313 and 314 using an X reference point (an Infrastructure Node is a Node that contains one Common Services Entity and may contain Application Entities. An Application Node (s). An Infrastructure Node may communicate with one or more Application Dedicated Nodes over one or more respective X reference points.

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

The functions provided by the common service object are summarized as shown in FIG. 17, and the functions such as Addressing & Identification, Data Management & Repository, Location, Security, Communication Management / / Delivery Handling, Registration, Session Management, Device Management, Subscription / Notification, Connectivity Management, Discovery, Service Charging / Settlement 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.

Each of the functions will be described as follows.

Addressing and Identification (AID) provides the information needed to identify and manipulate physical and logical resources in an M2M environment. Logical resources are software, such as applications, CSEs, and data. Physical resources are hardware-related entities associated with the underlying network and M2M devices. The AID CSF supports the provision of different types of M2M identifiers and the combination of identifiers with M2M applications, CSE, M2M devices (Identification and Identification (AID) CSF provides information on identifying and manipulating physical and logical resources in M2M environment . The logical resources are entities related to software such as CSEs and Data. The physical resources are hardware related entities such as the entities in the Underlying Network and M2M Devices etc. The AID CSF provides for the provision of different types of M2M Identifiers and the association of such Identifiers with M2M Applications, CSEs, M2M Devices etc.).

Communication Management and Delivery Handling (CMDH) is responsible for communication between other CSEs, AEs, and NSEs. CMDH is responsible for storing the communication requests at which time to communicate using which communication connection (CSE-CSE communication), when it is needed and when it is allowed, and when the transmission of the communication is postponed. CMDH is performed according to the provisioning policy and delivery handling parameters specific to each request for communication. Based network data transmission service, the underlying network can support the same forwarding handling function. In this case, CMDH can use the underlying network and act as a front-end that accesses the same forwarding-handling function to the underlying network (CSDs CSFs, CSEs, AEs and NSEs. The CMDH CSF is responsible for deciding what time to communicate and which CSE-to-CSE communication is used. In this paper, we propose a new CMDH CSF based on the proposed CMDH-based CSDF, which is based on the CMDH protocol. The CMDH CSF is available on the Underlying Network, and it may act as a fro nt end to access the underlying network equivalent delivery handling functionality.

Data Management and Repository (DMR) allows M2M applications to exchange data with other objects. The DMR CSF provides the ability to provide and coordinate data storage. It also includes the ability to collect and combine large amounts of data, convert data to a specific format, or store data for analysis and semantic processing. "Data " means raw data that is extracted transparently from an M2M device, or may refer to data processed or combined and processed by an M2M entity. Collecting a large amount of data constitutes what is known as a Big Data Storage function. (One of the goals of one M2M CSEs is to enable M2M Applications to exchange data with each other. Data Management and Repository The "data" can be either raw data transparently retrieved from the M2M Device, or orbiting the data. This is a collection of large amounts of data constitutes what is known as the Big Data Repository functionality.

DMG (Device Management) CSF enables device management to provide one or more of the following functions: Installation and configuration of application software, configuration settings and provisioning, firmware updates, logging and monitoring and analysis, topology management of area networks, and devices within this network management. (DMG) CSF enables the management of device capabilities including one or more of the following: Application software installation and settings; Configuration settings and Provisioning; Firmware updates; Logging, Monitoring, Diagnostics; Area Network Management.)

The DIS (Discovery) CSF is responsible for retrieving the information and resources granted in the given scope and subject (including those allowed in the M2M service subscription) and the request from the Originator within a given scope Loses. The originator can be an application or another CSE. The scope of the search may be one CSE or multiple CSEs. The discovery result is returned to the originator (Discovery (DIS) CSF is responsible for searching for information / resources according to a request from an originator within a given scope and subject to permissions. The CSE is a collection of CSE files that can be downloaded from the CSE web site.

Group Management (GMG) handles the group associated with the request. Requests are sent for the management of group and group membership, and are also responsible for the bulk operations supported by the group. When adding or deleting members to a group, you need to make sure that the members conform to the purpose of the group. Bulk operations include read, write, subscribe, notify, and device management. The request or subscription is made through the group, and the group is responsible for combining these requests and notifications. Members of a group have the same role in access rights to resources. In this case, access control is done by the group. If the underlying network provides broadcasting and multicasting capabilities, then the GMG CSF should use this functionality (Group Management (GMG) CSF is responsible for handling Group Group related requests. Membership as well as bulk operations are supported by the Group. Bulk operations include read, write, subscribe, and notify. , device management, etc. The Group is a member of the Group, the Group is responsible for aggregating its responses and notifications. This case, access control is facilitated by grouping, and the GMG CSF is able to utilize such capability.

LOC (Location) The CSF enables the M2M application to acquire the geographic location information of M2M entities (eg M2M devices and gateways) for location-based services. This location information may be requested from M2M applications residing within the same or different M2M nodes. (M2M Devices and Gateways) M2M Applications (M2M Devices and Gateways) M2M Applications to M2M Applications to M2M Applications (M2M Devices and Gateways) Nodes.)

The NSE (Network Service Exposure) CSF manages communication with the underlying network to access the network service functions via the Z reference points on the available or supportable way for service requests from M2M systems on behalf of M2M applications. The NSE CSF conceals other CSFs and AFs from specific technologies and mechanisms supported in the underlying network. The network service functions provided from the underlying network include, but are not limited to, device triggering, small data transfer, location notification, policy rule setting, location query, IMS service, device management and the like. These functions do not include general transport services (eg, Network Service Exposure, Service Execution and Triggering (NSE) CSF manages communications with the underlying network services functions The NSE CSF shields other CSFs and AFs are supported by the Underlying Networks. The network services functions are provided by the underlying network, including but not limited to, device triggering, small data transmission, location notification, policy rules settings, location queries, IMS services, device management.

REG (Registration) is responsible for handling applications or other CSEs to register with the CSE, which allows the registration of entities that want to use the services provided by the CSE. The REG CSF handles the registration of the device's properties / attributes as well as the registration of the device to the CSE (Registration (REG) CSF is responsible for handling an application or CSE to register with a CSE in order to allow registered entities to use The REG CSF handles registration of a Device as well as the registration of the Device's properties / attributes with the CSE.

SEC (Security) provides careful (sensitive) data handling, security operations, secure association configuration, authorization and access control, and identity protection. The SEC CSF provides sensitive data handling capabilities to protect local credentials that require security during storage and manipulation. Sensitive data handling also uses security algorithms. This feature supports separate security environments with different cryptographic techniques. The security operations function provides the following functions, first providing the creation and operation of a secure environment dedicated to being supported by the sensitive data handling function. It also supports post provisioning of root credentials protected in a secure environment and supports the provisioning and operation of subscriptions related to M2M services and M2M application services. The security association setting function establishes a security association between M2M nodes to enable confidentiality, integrity, authentication, and authorization. Authorization and access control functions control the access of services and data to authorized entities according to the provisioned security policies and assigned roles. A unique identifier of an entity may be used for authorization, and an identity protection function may provide an anonymity that serves as a temporary identifier so that it is not linked to an entity or an actual identity associated with the user (SEC (SEC) : Sensitive Data Handling functionality; Security Association Establishment functionality; Authorization and Access Control functionality; Identity Protection Functionality; Sensitive Data Handling functionality in the SEC; CSF protects the local credentials on which security relies during storage and manipulation. It performs other sensitive functions as well as security algorithms such as the following: - Creation and administration of dedicated security environments Upported by Sensitive Data Handling functionality; Provisioning and administration of subscriptions related to M2M services and M2M application services. Security Association Establishment functionality is responsible for establishing security association between corresponding M2M nodes, in order to provide services such as confidentiality, integrity, authentication, authorization, etc. Authorization and Access Control functionality is responsible for authorizing services and data access to authenticated entities. The unique identifiers of an entity are used for authentication, the Identity Protection functionality provides pseudonyms which serve as temporary identifiers.

Service Charging and Accounting (SCA) provides billing for the service layer. Supports different billing models, including online and offline billing. The SCA CSF acquires billable events, stores information, and generates billing records and billing information. The SCA CSF can interact with the billing system of the underlying network. However, the SCA CSF is responsible for generating and recording billing information at the final service level. The SCA CSF of the base node or service layer charging server is responsible for handling the charging information for charging (Service Charging and Accounting (SCA) CSF provides charging functions for the Service Layer. The SCA CSF is responsible for capturing chargeable events, recording of information, generating charging records and charging information. The SCA CSF can interact with the charging system in the Underlying Network also. It is the responsibility of the SCA to support the charging of the SCA in the service layer.

The SMG (Session Management) CSF manages the M2M service session, which is an end-to-end service layer connection. The SMG CSF manages M2M service sessions between M2M applications, or between M2M applications and CSEs, or between CSEs. Management of the M2M service session includes management of the session state, establishment and authentication of the session, management of the underlying network connection and service related to the session, coordination of the session expansion of the CSE multi-hop cse, . Within a given M2M service session, the SMG CSF uses the CMDH CSF in the local CSE to send / receive messages to / from the next hop CSE or application. The SMG CSF uses the SEC CSF for the session credentials of the session participants and for session management related to authentication. The SMG CSF generates a session-specific billing event and also communicates with the SCA CSF in the local CSE (an M2M service session is an end-to-end Service Layer connection managed by the Session Management (SMG) CSF. The SMG CSF manages the M2M service M2M Application, a CSE, or CSEs. The management of a M2M service session includes capabilities such as session state, session authentication and establishment, management of the underlying network connections and services related to the session , the coordination of sessions spanning multiple hops of CSEs, the exchange of information between session endpoints, and session termination. The SMG CSF uses the CMDH CSF within its local CSE for sending / receiving messages to / from the next-hop CSE or to / from an The SMG CSF also uses the SEC CSF for session management related session credentials and authentication of the session participant ts. The SMG CSF generates session specific charging events as well as the CSA within its local CSE. ).

Subscription and Notification (SUB) provides notification to maintain subscriptions and tracks changes in resources (for example, deletion of resources). The subscription of the resource is initiated by the M2M application or CSE, and the access right is granted by the hosting CSE. During an active subscription, the hosting CSE sends a notification to the subscribed owner if a change occurs in the subscribed resource. (The Subscriber and Notification (SUB) CSF is responsible for providing notifications for changes to a resource , delete a resource). A subscription to a resource is initiated by an M2M Application or a CSE, and is granted by the hosting CSE subject to access rights. to notify of a change on the subscribed-to resource.)

17 and the description thereof are embodiments for implementing a common service entity, and the present invention is not limited thereto.

Meanwhile, an identifier required for implementing the present invention will be described as follows. The M2M identifier includes an M2M Service Provider Identifier (M2M-SP-ID), an App-Inst-ID (Application Instance Identifier), an App-ID (Application Identifier), a CSE-ID (CSE Identifier), an M2M- A Node Identifier / Device Identifier, an M2M Service Subscription Identifier (M2M-Sub-ID), and an M2M-Request-ID (Request Identifier).

The following M2M framework, M2M system, and M2M architecture are interchangeable words.

The M2M service provider shall be uniquely identified by the M2M-SP-ID. The M2M-SP-ID is a static value assigned to the service provider (an M2M Service Provider will be uniquely identified by the M2M Service Provider Identifier (M2M-SP-ID). Service Provider.). The App-Inst-ID is an identifier that uniquely identifies an application instance (M2M Application Instance) present in the M2M M2M node, or an identifier that identifies an M2M application instance that interacts with the M2M node. The App-Inst-ID is used to identify an application from an application within the M2M framework or to interact with it towards an application (an Application Instance Identifier (App-Inst-ID) uniquely identifies an M2M Application instance resident on an An M2M node or an M2M application instance that interacts with an M2M node. An App-Inst-ID will identify an application for the M2M framework. The M2M service provider must ensure that the App-Inst-ID is globally unique and the App-Inst-ID contains the application identifier (App-ID) App-Inst-ID is globally unique. The App-Inst-ID will include the Application ID). App-ID corresponds to an application and does not guarantee that it is globally unique (this is equivalent to the application name and is not guaranteed to be globally unique on its own).

The CSE-ID identifies the CSE and is globally unique and is used when the CSE is instantiated on the M2M node within the M2M architecture. The CSE-ID is used to identify the CSE in all interactions from or to the CSE within the M2M framework (CSE-ID, when the CSE-ID is instantiated within an M2M node in the M2M architecture. The CSE-ID shall identify the CSE for the purpose of all interactions from / to the CSE within the M2M framework.

The M2M-Node-ID uniquely identifies the M2M node hosting the CSE and / or application. In the M2M system, the M2M service provider sets the CSE-ID and the M2M-Node-ID to the same value. The M2M-Node-ID allows the M2M service provider to bind the CSE-ID to a specific M2M node (an M2M node, hosting a CSE and / or Application (s) Node-ID. The M2M system shall allow the M2M Service Provider to set the CSE-ID and the M2M-Node-ID to the same value. specific M2M node.

The M2M-Sub-ID allows the M2M service provider to bind the application, M2M node, and CSEs to a specific M2M service subscription. Therefore, the M2M-Sub-ID belongs to the M2M service provider, identifies the subscription to the M2M service provider, enables communication with the M2M service provider, and is distinguished from the M2M Underlying Network Subscription Identifier It may be changed according to the change of M2M service provider. There are a number of M2M-Sub-IDs available for M2M-based networks (The M2M-Sub-ID enables the M2M Service Provider to bind application (s), M2M nodes, CSEs to a particular M2M service subscription. The M2M Service Provider is an M2M service provider that enables the M2M service provider to communicate with the M2M service provider. The M2M service provider is capable of communicating with the M2M service provider. There can be multiple M2M Service Subscription Identifiers per M2M Underlying Network subscription.).

The M2M-Request-ID (M2M Request Identifier) is an identifier that tracks the request initiated from the CSE in a one-to-one fashion. It is also included in the response to the request. The M2M-Request-ID is assigned by the CSE that initiated the request. A request initiated by the CSE may be the result of an application request, or it may be the result of a request automatically initiated by the CSE to satisfy the service. Here, the CSE that has received the request from the peer CSE must include the received M2M-Session-ID in all requests (including the case of the received request) that are generated by adding it, and may be combined with the received request if applicable . If applicable, the same M2M-Session-ID can be included in the interaction with the underlying network. The M2M-Request-ID must be globally unique (this is an identifier that tracks a Request initiated by a CSE end to end. The request is initiated by the CSE and may result in an Application Request, or a Request initiated autonomously by the CSE to fulfill a service. Request-ID in its interactions with the underlying network, where applicable. The CSE shall include the same. . An M2M-Request-ID allocated to a CSE shall be globally unique.

18 is a diagram illustrating a communication flow at a reference point according to an embodiment of the present invention.

510 is the originator and 520 is the receiver. Information exchange between the two entities is made via the X reference point between the application and the CSE, or between the CSE and the Y reference point. In addition, information is exchanged between Send and Respond. A send request is made from the originator 510 to the receiver 520 and includes the following information.

"op" is an operation to be executed, and includes C (Create), R (Retrieve), U (Update), and D (Delete). "to" is the address of the target resource, and "fr" is the address of the resource representing the originator. "hd" is a header including meta information for a transmission request, and "cn"

The to can be a target resource known by the originator, which can be known at pre-provisioning or by discovery. It may further contain a "mi" field, which means meta information about the request.

19 is a diagram illustrating an architecture of a common service object to which an embodiment of the present invention is applied. A common service entity includes a set of common service functions and a set of enabler functions. The Enabler function consists of a Service Extension Enabler and an Other Enabler. The Service Extension Enabler allows the CSE to provide M2M services via X, Y reference points. . The Service Extension Enabler provides the following features: check policy authorizations, check for nodeless leases, check for interoperability between existing modules, and check policies and permissions to determine how to deal with conflicts, V) register a new module, vi) add a new service because the new module is added to the service list, vii) modify the API to reflect the new service capability, And viii) change the inter-module communication to combine the new modules. (The CSE comprises a set of Common Service Functions (CSFs) and a set of Enabler Functions (EFs). The Services Extension Enabler enables the CSE to offer M2M 3. Check interoperability with Existence: 1. Check module authentication 2. Check node resources 3. Check interoperability with exist 5. Register new module. 6. Add new module (s) due to new module to list of services. 7. Modify inter-module communications to incorporate new module capabilities.

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 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 within the scope of equivalents should be construed as falling within the scope of the present invention.

110: Application
120: Common Services
130: Infrastructure Network Services

Claims (1)

Configuring an intermediate node (hereinafter referred to as a secondary node) for backing up an intermediate node (hereinafter, referred to as a primary node) having a session for transmitting data at a specific point in time;
When the primary node receives data from the end node, it transmits the data to the secondary node. When the primary node fails to transmit and receive data, the end node accesses to the secondary node and the existing transmission session and context are recovered from the secondary node And transmitting the data constituted by the step of transmitting the data.

Images