KR101792331B1 - Method and System for Transaction in the M2M/IoT Platform - Google Patents

Abstract

A transaction support method and system is provided on the M2M / IoT platform. A transaction support method according to an exemplary embodiment of the present invention transmits a transaction command message to a child node, receives a transaction status report message from a child node, and transmits an optional subsequent processing message to a child node with reference to the transaction status report message. This enables reliable data processing, setup and control with transaction support on the M2M / IoT platform.

Description

[0001] The present invention relates to a transaction method and system for a M2M / IoT platform,

The present invention relates to an M2M / IoT platform, and more particularly to a method and system for supporting transactions in an M2M / IoT platform.

The development of information and communication technology is changing the networking and internet environment centered on computers such as personal computers and notebook computers with small devices that can be moved such as smart phones and portable multimedia devices including computers.

However, small devices capable of arithmetic, communication, and networking functions can be attached to general objects such as meters and thermometers as well as information devices. These small devices attached to objects can automatically acquire information of objects or mutually share information through communication networks between objects.

The term "Internet of Things", "M2M" (machine-to-machine communication) is used to refer to concepts and technologies for connecting objects to a network or establishing a communication network between objects using communication devices attached to objects. Machine and intelligent communication.

In this network environment, communication network between object and object as well as person-to-person and person-to-object communication becomes possible and information sharing among all objects becomes possible, which is an essential technical element for evolving into the future ubiquitous information service society.

However, in the current M2M / IoT platform system, there is no guarantee of reliability for the setting and control of various devices. That is, there is no countermeasure for the error occurrence after a series of messages are transmitted to the registered devices.

It is an object of the present invention to provide a method and system for supporting transaction in M2M / IoT platform as a method for reliable data processing, setting and control.

According to an aspect of the present invention, there is provided a transaction support method including: a first transmission step in which an upper node transmits a transaction command message to a lower node; The upper node receiving a Transaction Status Report Message from the lower node; And a second transmission step of referring to the transaction status report message and the upper node transmitting an optional subsequent process message to the lower node.

The transaction command message may be a resource update message of the lower node, and the transaction status report message may be a message indicating whether the resource update of the lower node is successful.

In addition, when the lower node receives the transaction command message from the upper node, the lower node performs an update after copying the target resource, and the second transmission step transmits a final commit message if the resource update is successful , The lower node can delete the copied target resource upon receiving the final commit message.

In the second transmission step, if the resource update is failed, a Rollback message is transmitted. When the lower node receives the Rollback message, the lower node can restore the updated target resource to the copied resource.

The first transmission step also transmits transaction command messages to a plurality of lower nodes, and the receiving step receives transaction status report messages from a plurality of lower nodes, And may transmit an optional subsequent processing message to at least one of the child nodes with reference to at least one of the report messages.

According to another aspect of the present invention, there is provided a transaction support method including: a first receiving step of a lower node receiving a transaction command message from an upper node; The lower node transmits a Transaction Status Report Message to the upper node; And a second receiving step of receiving, from the superordinate node, a subsequent process message determined by the superordinate node with reference to the transaction status report message.

As described above, according to the embodiments of the present invention, reliable data processing, setting, and control can be performed with transaction support in the M2M / IoT platform. In particular, according to embodiments of the present invention, if a desired result is not obtained in a series of processes for M2M / IoT devices, a function of rolling back to a state before a series of processes is supported, When it is obtained, it supports the function of final commit to guarantee the reliability of the M2M / IoT platform system.

1 is a diagram illustrating an M2M / IoT system to which the present invention is applicable,
2 is a conceptual diagram illustrating a resource structure of a child node and a resource update method;
3 to 6 are diagrams provided in a specific description of a process of updating a resource of a lower node,
7 is a diagram illustrating policies for management of transaction processing in the M2M / IoT system.

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

The embodiment of the present invention proposes a transaction support system for reliable data processing in the M2M / IoT platform. To this end, the transaction support system according to the embodiment of the present invention supports the commit function and the rollback function, thereby assuring the reliability of the setting and control of the devices.

1 is a diagram showing an M2M / IoT system to which the present invention is applicable. The illustrated M2M / IOT system is constructed by connecting an Infrastructure Node (IN) to be able to communicate with Middle Node (MN) and Application Service Node (ASN).

It can be understood that IN is a node corresponding to a server, MN is a node corresponding to a gateway, and ASN is a node corresponding to an end-point.

FIG. 1 shows a process of processing a transaction message between IN, MNs and ASNs. Specifically, in Fig. 1,

1) If IN sends a Transaction Command Message to MNs and ASNs,

2) MNs and ASNs return a Transaction Status Report Message to IN,

3) Referring to the returned message, IN shows a process of selectively sending a final commit message or a rollback message to MNs and ASNs.

In FIG. 1, it is assumed that the transaction command is a resource update (UPDATE). FIG. 2 shows the resource structure of the lower nodes MN and ASN. FIG. 2 conceptually shows a method of updating a resource contained in "container1".

As shown in Fig. 2, in order to update a resource recorded in "container1", a SNAPSHOT corresponding to a copy of a resource must be preceded, and then the resource may be updated or rolled back originally.

Hereinafter, a specific process in which the resource update is performed in the lower node (MN, ASN) by the process shown in FIG. 1 will be described in detail with reference to FIG. 3 to FIG.

The transaction command message received from the IN includes a command (UPDATE), a target resource, and data. In Fig. 1, the command has been assumed to be UPDATE. The data is new data to replace the data of the target resource.

The target resource is information specifying / specifying the resource to be updated, and can be specified / specified by URI. In Fig. 2, the target resource is assumed to be "container1 ", and expressed as a URI is" CSEBase / remoteCSE / AE / container1 ".

The child node receiving the resource update from the IN copies the corresponding resource (SNAPSHOT) as shown in FIG. 3, and generates a copy (backup copy) of "container1".

Next, the child node updates "container1" with the data included in the transaction command message received from the IN, as shown in Fig. The update may or may not succeed. An update failure is caused by a problem on the link between IN and the lower node or an internal error of the lower node.

The child node then returns a transaction status report message to the IN. The transaction status report message returned from IN to the IN contains information about whether the update succeeded or failed.

If the update succeeds, IN sends the final commit message to the child node. The child node then deletes the SNAPSHOT copied copy, as shown in FIG.

On the other hand, if the update fails, IN sends a Rollback message to the child node. Then, the child node restores the SNAPSHOT copied copy (backup copy) of the resource that has attempted to update, as shown in FIG.

Up to now, a preferred embodiment of a transaction support method for reliable data processing in the M2M / IoT platform has been described in detail.

According to the embodiment, when the desired result is not obtained in the resource update process for the nodes corresponding to the M2M / IOT devices (i.e., the update fails), the function of rolling back to the state before the update start is supported, When the result is obtained (that is, when the update is successful), the function of finalizing the update completion state is supported, thereby ensuring the reliability of the M2M / IoT platform system.

In the above embodiment, it has been assumed that IN performs Commit / Rollback processing individually according to the success / failure of update of the lower node. However, since the child nodes may be related to each other, it is possible to operate the policy so that the commit / rollback of the child node depends on the success / failure of updating itself and other child nodes.

For example, as shown in Policy 1 (Policy 1) of FIG. 7, when only one of the lower nodes is failed to update, it is possible to implement rollback processing for all the lower nodes.

As another example, as shown in Policy 2 (Policy 2) in FIG. 7, the MN needs to successfully update not only itself but also other MNs, and the ASN can also be implemented as being committed to itself and successively updating other ASNs Do.

In FIG. 7, in the case of following policy 2 (Policy 2), all of the MNs are committed and all of the MNs are committed, but one of the ASNs fails to update (FaiL) Respectively.

The policies presented in FIG. 7 are exemplary only, and there is no limit to the number of policies to operate. These policies for management of transaction processing in M2M / IoT systems are restricted to at least one node (all / some nodes) in the event of an update failure on at least one node (all / some nodes) Can be set variously.

Further, in the above embodiments, the resource update of the M2M / IoT devices which are the lower nodes is assumed, and the update corresponds to a kind of command. It goes without saying that the above-described transaction support can be applied to other types of commands.

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

IN: Infrastructure Node
MN: Middle Node (intermediate node)
ASN: Application Service Node (Application Service Node)
Transaction Command Message: Transaction command message
Transaction Status Report Message: Transaction status report message
Final Commit Message: The final Commit message
Rollback Message: Rollback Message

Claims (6)

A first transmission step in which an upper node transmits transaction command messages to a plurality of lower nodes;
The upper node receiving transaction status report messages from the lower nodes; And
And a second transmission step of referring to the transaction status report messages, wherein the upper node transmits an optional subsequent processing message to the lower nodes,
Wherein the second transmission step comprises:
Referring to the transaction status report messages received from the lower level nodes of the first type, transmitting an optional subsequent process message to the lower level nodes of the first type,
And transmitting an optional subsequent process message to the lower level nodes of the second type with reference to the transaction status report messages received from the lower level nodes of the second type.
The method according to claim 1,
Wherein the transaction command messages are resource update messages of the lower nodes,
Wherein the transaction status report messages include messages indicating whether the resource update of the lower nodes is successful.
The method of claim 2,
Wherein the lower nodes, when receiving the transaction command message from the upper node, perform an update after copying the target resource,
Wherein if the resource update is successful, the second transmission step transmits a final commit message,
And the lower nodes delete the copied target resource upon receiving the final commit message.
The method of claim 3,
The second transmission step may include transmitting a rollback message if the resource update is unsuccessful,
And the lower nodes, when receiving the Rollback message, restore the updated target resource to the copied target resource.
delete A first receiving step in which the lower nodes receive transaction command messages from an upper node;
Transmitting, by the lower nodes, transaction status report messages to the upper node; And
And a second receiving step of the lower nodes receiving, from the upper node, subsequent processing messages determined by the upper node with reference to the transaction status report messages,
The superordinate node,
Referring to the transaction status report messages received from the lower level nodes of the first type, transmitting an optional subsequent process message to the lower level nodes of the first type,
And transmitting an optional subsequent process message to the lower level nodes of the second type with reference to the transaction status report messages received from the lower level nodes of the second type.

Images