CN102136976A - Machine transaction control method, device and system - Google Patents

Abstract

The embodiment of the invention discloses a machine transaction control method, which comprises that: a machine-to-machine (M2M) platform receives a transaction handling request from a requester; the M2M platform generates and transmits a transaction operating command to transaction participating equipment or a gateway according to the connection properties of the transaction participating equipment, wherein the transaction operating command carries a transaction execution processing instruction; and the transaction participating equipment or the gateway executes a transaction according to the transaction operating command, and returns a transaction operating response to the M2M platform according to the transaction execution processing instruction. Therefore, the transaction handling efficiency is improved.

Description

A machine business control method, device and system

technical field

The present invention relates to the technical field of communications, in particular to a machine transaction control method, device and system.

Background technique

In the field of transaction processing, transactions usually have four properties, namely, atomicity, consistency, isolation, and durability. Atomicity requires that all operations on transactions occur or none occur. Consistency requires transactions to maintain their operating data. Consistency, isolation requires that a transaction does not read the intermediate results of another transaction, and durability requires that the results of a committed transaction are durable. Traditionally, distributed systems have utilized two-phase commit protocols and transaction coordinators to ensure operation atomicity and data consistency. Transaction participants provide isolation and durability. Each participant in the two-phase commit protocol votes to decide whether to succeed or abort the transaction, and sends its vote result to the transaction coordinator. Then, the transaction coordinator based on the Only when all participants voted successfully, the transaction coordinator submits the transaction, as shown in Figure 1(a), when both transaction participants voted successfully, the transaction coordinator submits the transaction . Otherwise, the transaction coordinator will abort the transaction, as shown in Figure 1(b), one of the two transaction participants fails to vote, and the transaction coordinator rolls back.

The M2M (machine to machine, machine to machine) system allows M2M devices to access multiple wired and wireless methods. Under different access methods, depending on the capabilities of the devices, some M2M devices are directly connected to the platform, and some are connected to the platform through a gateway. M2M The system supports transaction handling (Transaction Handling), the purpose is to ensure the four characteristics of the operation between several entities in the machine communication system, such as: allowing the system to roll back from wrong operations, and the M2M platform and gateway in the M2M system have the ability to aggregate transaction responses.

M2M devices in transaction operations can be directly connected to the platform or connected to the platform via a gateway. Correspondingly, there are multiple aggregation methods for M2M transactions. How to issue transaction operation requests in different situations, and how the platform and gateway cooperate with the aggregation transaction operation response will affect the transaction The execution efficiency of operations, inappropriate transaction aggregation or the inability to judge the final result of transactions, or a large amount of unnecessary information interaction between device platforms are all problems that need to be solved.

In the prior art, the transaction coordinator adds additional associated data to the transaction preparation request sent by the transaction participants, including: transaction identifier, transaction execution command, and identification of other participating nodes in the transaction, thereby reducing or completely unnecessary the log of the transaction coordinator Forced writing, when a failure occurs, the coordinator interacts with the participating nodes to determine the correct transaction status information before the failure.

Contents of the invention

A machine transaction control method, characterized in that the method comprises,

The machine-to-machine M2M platform receives the transaction processing request sent by the requester;

The M2M platform generates and sends transaction operation commands to the transaction participating devices or the M2M gateway according to the connection attributes of the transaction participating devices;

The M2M platform receives the transaction operation response returned by the transaction participating device or the M2M gateway. The transaction operation response is returned after the transaction participating device or the M2M gateway executes the transaction according to the transaction operation command.

A machine transaction control system, characterized in that the system includes,

The machine-to-machine M2M platform is used to receive the transaction processing request sent by the requesting party, and generate and issue transaction operation commands according to the connection attributes of the transaction participating devices;

The transaction participating device is configured to execute the transaction according to the transaction operation command, and send a transaction operation response to the M2M platform.

A machine-to-machine platform, characterized in that the machine-to-machine platform includes,

a receiving unit, configured to receive a transaction processing request sent by a requesting party;

The generating unit is used to generate a transaction operation command according to the connection attributes of the transaction participating devices after the receiving unit receives the transaction processing request;

The sending unit is configured to send the transaction operation command generated by the generating unit to the transaction participating device or the M2M gateway.

A machine-to-machine gateway, characterized by comprising:

The receiving unit is configured to receive a transaction operation command from the M2M platform, the transaction operation command includes a transaction execution processing instruction instructing the M2M gateway to converge and forward the transaction operation response; receive the transaction operation response returned by the transaction participating device;

The converging unit is used for converging the transaction operation responses received by the receiving unit;

The sending unit is configured to send transaction operation commands to the connected transaction participating devices; and send the transaction operation responses gathered by the converging unit to the M2M platform.

A machine-to-machine gateway, characterized by comprising:

The receiving unit is used to receive a transaction operation command from the M2M platform. The transaction operation command includes a transaction execution processing instruction that instructs the M2M gateway to control and execute the subsequent transaction update operation and return the transaction execution result; receive the transaction preparation response returned by the connected transaction participating device ; Receive a transaction update response from a transaction participating device;

The aggregation processing unit is used to aggregate the received transaction preparation responses according to the transaction execution processing instructions, and generate transaction update instructions according to the results of the aggregated transaction preparation responses; aggregate the received transaction update responses according to the transaction execution processing instructions;

The sending unit is configured to issue a transaction preparation instruction to the transaction participating device according to the transaction execution processing instruction; issue a transaction update instruction to the transaction participating device; return the execution result corresponding to the transaction update response gathered by the convergence processing unit to the M2M platform.

Description of drawings

Figure 1(a) is a schematic diagram of transaction processing in the prior art;

Figure 1(b) is a schematic diagram of transaction processing in the prior art;

FIG. 2 is a flow chart of a machine transaction control method according to an embodiment of the present invention;

FIG. 3 is a flowchart of another machine transaction control method according to an embodiment of the present invention;

Fig. 4 is a flow chart of the transaction operation command of the gateway processing platform according to the embodiment of the present invention;

5 is a schematic structural diagram of a machine transaction control system according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of another machine transaction control system according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of another machine transaction control system according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of another machine transaction control system according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an M2M platform according to an embodiment of the present invention;

FIG. 10 is a specific implementation flow chart of a machine transaction control method according to an embodiment of the present invention;

FIG. 11 is a flow chart of a specific implementation of another machine transaction control method according to an embodiment of the present invention;

Fig. 12 is a specific implementation flowchart of another machine transaction control method according to the embodiment of the present invention;

FIG. 13 is a schematic structural diagram of an M2M gateway according to an embodiment of the present invention;

FIG. 14 is a schematic structural diagram of another M2M gateway according to an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Fig. 2 is a schematic flow chart of the method of the first embodiment of the present invention, including:

A1. The machine-to-machine M2M platform receives the transaction processing request sent by the requesting party;

The requester here is an authorized entity, that is, an entity that has the right to apply for transaction processing from the M2M platform, which may be a personal terminal, a server, or other equipment, and the transaction processing request here includes transaction information to be processed.

A2. The M2M platform generates and sends a transaction operation command to the transaction participating device or gateway according to the connection attribute of the transaction participating device;

Wherein, the transaction operation command can specifically be a transaction preparation instruction or a transaction update instruction. Specifically, according to the difference of transaction update (transaction update can be divided into transaction commit and transaction rollback), the transaction update instruction can include transaction commit instruction and transaction rollback. There are two types of rolling instructions, among which, the transaction commit instruction is an instruction to instruct the transaction participating equipment to execute the transaction when the transaction participating equipment is ready to execute the transaction; the transaction rollback instruction is when the transaction participating equipment is not ready to execute the transaction. An instruction that instructs a transaction-participating device to restore the state it was in prior to the preparation.

Wherein, according to different connection attributes of transaction participating devices, the transaction operation command may also carry different transaction execution processing instructions.

A3. The transaction participating device or gateway executes the transaction according to the transaction operation command, and returns a transaction operation response to the M2M platform according to the transaction execution processing instruction.

Correspondingly, depending on the transaction operation command, the transaction operation response is also different. When the transaction operation command is a transaction preparation instruction, the corresponding transaction operation response is a transaction preparation response, and when the transaction operation command is a transaction update instruction, the corresponding transaction operation response is is a transaction update response, specifically, when the transaction update command is a transaction commit command, the corresponding transaction operation response is a transaction commit response, and when the transaction update command is a transaction rollback command, the corresponding transaction operation response is a transaction rollback response.

Embodiment 1 The transaction processing request sent by the requester is received by the machine-to-machine M2M platform; the M2M platform generates and sends a transaction operation command to the transaction participation device or gateway according to the connection attribute of the transaction participation device, and the transaction operation command carries a transaction Executing a processing instruction: the transaction participating device or gateway executes a transaction according to the transaction operation command, and returns a transaction operation response to the M2M platform according to the transaction execution processing instruction, thereby improving transaction processing efficiency.

Wherein, the M2M platform processing process in one embodiment of the present invention is shown in Figure 3, and the specific steps are:

301. The M2M platform receives a transaction processing request;

The transaction processing request here is the transaction processing request in step A1;

302. The M2M platform retrieves the ownership of the M2M device gateway, judges whether to hand over the transaction update control process to the home gateway, and adds a transaction execution processing instruction to the transaction operation command;

The M2M platform retrieves the attribution status of the M2M device gateway, which is divided into four situations: A. The transaction participating device directly connects to the M2M platform; B. A single device among the transaction participating devices connects to the M2M platform through the gateway; C. Multiple transaction participating devices A device is connected to the M2M platform through the same gateway, and all devices in D. transaction participating devices are connected to the M2M platform through the same gateway. The M2M platform adds corresponding transaction execution processing indications according to the gateway ownership of the transaction participating devices. Specifically, relative to A, the transaction execution processing indication is empty, and relative to B, the transaction execution processing indication is empty or instructs the gateway to forward the transaction operation response. C, the transaction execution processing instruction is to instruct the M2M gateway to aggregate and forward the transaction operation response, and relative to D, the transaction execution processing instruction is to instruct the M2M gateway to control and execute the subsequent transaction update operation, and then return the transaction execution result.

And, only in case D, the transaction update control process is handed over to the home gateway for processing.

303. The M2M platform issues a transaction operation command to the device or the gateway;

304. The M2M platform receives the transaction operation response returned by the device or the gateway, and judges the final execution status of the transaction;

Wherein, when all the transaction preparation responses are prepared successfully, the M2M platform judges that the transaction preparation is successful, and sends a transaction submission instruction to the transaction participating device; otherwise, it determines that the transaction is unsuccessful, and sends a transaction rollback instruction to the transaction participating device.

In one embodiment of the present invention, the M2M gateway processing process is shown in Figure 4, and the specific steps are:

401. The gateway receives an M2M platform transaction operation command, and the transaction operation command carries a transaction execution processing instruction;

Here only for the situation B, C, D in step A2;

402. The gateway issues a transaction operation command to the transaction participating device;

Among them, relative to A, the gateway can directly forward the transaction operation command to the transaction participating device;

Compared with B, when the transaction operation command issued by the M2M platform does not include the transaction execution processing instruction, the gateway can directly forward the transaction operation command to the transaction participating device; when the transaction operation command issued by the M2M platform contains the transaction execution processing instruction, the gateway can Delete the transaction operation command and send it to the transaction participating device after including the transaction execution processing instruction, or regenerate the transaction operation command and send it to the transaction participating device;

Compared with C and D, the gateway can delete the transaction operation command including the transaction execution processing instruction and send it to the transaction participating device, or can regenerate the transaction operation command and send it to the transaction participating device.

403. The gateway receives the transaction operation response returned by the device;

After the transaction participating device executes the transaction, it returns the transaction operation response to the gateway;

404. The gateway directly forwards the transaction operation response to the M2M platform according to the transaction execution processing instruction, or aggregates the transaction operation response;

After the gateway receives the transaction operation response from the transaction participating device, it executes the transaction instruction according to the transaction execution processing instruction. If the transaction execution processing instruction is a forwarding response, the gateway forwards the transaction operation response to the M2M platform. If the transaction execution processing instruction is a convergence response or the M2M gateway Control the execution of subsequent transaction update operations, then go to step 405;

405. The gateway determines whether the transaction is controlled by the gateway;

The gateway first judges whether all the transaction operation responses have been received, and if so, then determines whether the transaction is controlled by the gateway, if not controlled by the gateway, then go to step 406; if the transaction is controlled by the gateway, then go to step 407 or 408. Specifically, if the transaction operation command issued by the M2M platform received by the gateway includes a transaction execution processing instruction instructing the gateway to return a transaction execution result after the subsequent transaction update operation is controlled and executed, the gateway determines that the transaction is controlled by the gateway.

406. Send the aggregated transaction operation response to the M2M platform

407. The gateway sends a transaction submission instruction to the transaction participating device;

The gateway judges whether all transaction operation responses have been received, and after all transaction operation responses to be received are successful, the gateway sends a transaction submission request to the transaction participating device, and goes to step 408;

408. The gateway sends a transaction rollback instruction to the transaction participating device;

The gateway judges whether all transaction operation responses have been received, and when at least one of all transaction operation responses to be received is unsuccessful, the gateway sends a transaction rollback instruction to the transaction participating device, and turns to step 408;

409. The gateway reports the transaction execution result to the M2M platform.

After receiving the transaction commit response or transaction rollback response returned by all devices, the gateway aggregates the returned transaction commit response or transaction rollback response, and sends the transaction execution result corresponding to the aggregated transaction commit response or transaction rollback response to the M2M Report on the platform.

The process ends.

Fig. 5 is a schematic diagram of the system structure of the second embodiment of the present invention, including:

The machine-to-machine M2M platform 501 is used to receive the transaction processing request sent by the requesting party, generate and issue transaction operation commands according to the connection attributes of the transaction participating devices; for specific descriptions, refer to step A2 and steps 301 to 305 of Embodiment 1, which will not be repeated here repeat.

The transaction participating device 502 is configured to execute a transaction according to a transaction operation command, and send a transaction operation response to the M2M platform.

Fig. 6 is a schematic diagram of the system structure of the third embodiment of the present invention, wherein one of the transaction participating devices 502 is connected to the M2M platform 501 via the first M2M gateway 503, including:

The M2M platform 501 is used to receive the transaction processing request sent by the requesting party, and generate and issue a transaction operation command according to the connection attribute of the transaction participating device; for a detailed description, refer to step A2 and steps 301 to 305 of Embodiment 1, which will not be repeated here.

The first M2M gateway 503 is configured to issue a transaction operation command to the one transaction participating device 502 , and send a received transaction operation response to the M2M platform 501 .

The one transaction participating device 502 is configured to execute a transaction according to a transaction operation command, and send a transaction operation response to the M2M platform 501 . Wherein, sending the transaction operation response to the M2M platform is specifically sending the transaction operation response to the first M2M gateway 503, and the first M2M gateway 503 performs subsequent processing.

Fig. 7 is a schematic diagram of the system structure of the fourth embodiment of the present invention, wherein at least two devices 502 among the transaction participating devices are connected to the M2M platform 501 via the second M2M gateway 504;

The M2M platform 501 is configured to receive the transaction processing request sent by the requesting party, generate and issue a transaction operation command according to the connection attributes of the transaction participating devices, and the transaction operation command includes a transaction execution processing instruction instructing the second M2M gateway to aggregate and forward the transaction operation response; For a specific description, refer to step A2 and steps 301 to 305 in Embodiment 1, and details are not repeated here.

The second M2M gateway 504 is configured to issue a transaction operation command to the at least two transaction participating devices 502, aggregate the transaction operation responses returned by the at least two devices according to the transaction operation command, and send the aggregated transaction operation response to M2M platform 501 .

The at least two transaction participating devices 502 are configured to execute a transaction according to a transaction operation command, and send a transaction operation response to the M2M platform 501 . Wherein, sending the transaction operation response to the M2M platform is specifically sending the transaction operation response to the second M2M gateway 504, and the second M2M gateway 504 performs subsequent processing.

FIG. 8 is a schematic diagram of a system structure according to a fifth embodiment of the present invention, wherein the number of transaction participating devices 502 is at least two, and the at least two transaction participating devices are connected to the M2M platform 501 via a third M2M gateway 505;

The M2M platform 501 is configured to receive the transaction processing request sent by the requesting party, generate and issue a transaction operation command according to the connection attributes of the transaction participating devices, and the transaction operation command includes instructing the third M2M gateway 505 to control and execute the subsequent transaction update operation, and return the transaction The transaction execution processing instruction of the execution result; for a specific description, refer to step A2 and steps 301 to 305 of Embodiment 1, and details are not repeated here.

The third M2M gateway 505 is configured to issue a transaction preparation instruction to all connected devices according to the transaction execution processing instruction; after receiving the transaction preparation responses from all devices, aggregate the received transaction preparation responses according to the transaction execution processing instruction, and according to the aggregated The result of the transaction preparation response is to generate and issue transaction update instructions to all devices; after receiving the transaction update responses from all the devices, aggregate the received transaction update responses according to the transaction execution processing instructions, and update the aggregated transaction update responses The result is returned to the M2M platform 501 .

The transaction participating device 502 is configured to execute the transaction according to the transaction operation command, and send a transaction operation response to the M2M platform. Wherein, sending the transaction operation response to the M2M platform is specifically sending the transaction operation response to the third M2M gateway 505, and the third M2M gateway 505 performs subsequent processing.

The transaction participating device 501 is used to execute the transaction and return a transaction operation response to the gateway or platform. The gateway 502 is configured to execute the transaction according to the transaction operation command, and return the transaction operation response to the M2M platform according to the transaction execution processing instruction, and the M2M platform 503 is configured to receive the transaction processing request sent by the requesting party, and according to the transaction participation device The connection attribute generates and sends a transaction operation command to a transaction participating device or gateway, and the transaction operation command carries a transaction execution processing instruction, which improves transaction processing efficiency.

FIG. 9 is a schematic structural diagram of an M2M platform according to a sixth embodiment of the present invention, including:

The receiving unit 601 is configured to receive the transaction processing request sent by the requesting party.

The generating unit 602 is configured to generate a transaction operation command according to the connection attribute of the transaction participating device after the receiving unit 601 receives the transaction processing request;

Wherein, when compared to the above-mentioned case A, the transaction operation command generated by the generating unit 602 may not carry a transaction execution processing instruction;

When compared to the above case B, the transaction operation command generated by the generating unit 602 may not carry a transaction execution processing instruction, or may carry a transaction execution processing instruction;

With respect to the above cases C and D, the transaction operation command generated by the generating unit 602 carries a transaction execution processing instruction;

The sending unit 603 is configured to send the transaction operation command to the transaction participating device or the M2M gateway.

Optionally, the transaction operation command is a transaction preparation instruction; in this case, the receiving unit 601 may also be configured to receive a transaction preparation response returned by a transaction participating device or gateway; the M2M platform further includes,

The judging unit 604 is configured to aggregate the transaction preparation responses received by the receiving unit 601, and judge the transaction preparation status according to the aggregated transaction preparation. If successful, it will send a transaction submission instruction to the thing participating device; A participating device sends a transaction rollback command.

For the detailed description of the above units, refer to step A2 and steps 301 to 305 of the first embodiment, which will not be repeated here.

Embodiment 6 An M2M platform includes a receiving unit, configured to receive a transaction processing request sent by a requesting party, receive a transaction operation response returned by a participating device or a gateway, and a generating unit, configured to generate a transaction according to the connection attribute of a transaction participating device. An operation command, the transaction operation command carries a transaction execution processing instruction; an issuing unit is configured to issue the transaction operation command to a transaction participating device or a gateway, thereby improving transaction processing efficiency.

FIG. 10 is a flow chart of a specific implementation of a machine transaction control method according to the seventh embodiment of the present invention, including the requester, the M2M platform, the gateway, the transaction participating device 1, the transaction participating device 2, the transaction participating device 1 directly and the M2M platform connected, the transaction participating device 2 is connected to the M2M platform via the gateway, and the specific steps include:

701. The requester sends a transaction processing request to the M2M platform;

The purpose of this step is to create a transaction resource. The transaction processing request includes the application ID, address resource ID, new resource ID, processing content, and access permission ID. For specific implementation, refer to the following procedure:

POST .../{api Version}/m2mResource/transaction/platformCoordinator? resForm

at=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionResource xmlns:ts="urn:m2m:xml:rest:transaction:1">

<indicator>

<m2m:process>“aggregation”</m2m:process>

<m2m:commit-right>true</m2m:commit-right>

</indicator>

<participant-lists>

<participant name="smart metering A">

<entry uri="http://example.org/m2mResource/dev1"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering B">

<entrv uri=" http://example.org/m2mResource/gateway/dev2 "></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</participant-lists>

</m2m:transactionResource>

702. The M2M platform sends a transaction preparation instruction to the gateway;

The transaction preparation instruction specifically includes the application ID, address resource ID, transaction resource ID, and processing operation content. At the same time, it is specially pointed out that Process = "relay", Commit-Right = "false", to indicate that the transaction operation response is forwarded, and there is no commit authority. The implementation refers to the following program:

POST .../{apiVersion}/m2mResource/transaction/gatewayCoordinator? resForma

t=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionOperationResource

xmlns:ts="urn:m2m:xml:rest:transaction:1">

<m2m:transactionResource id="1234"/>

<indicator>

<m2m:process>“relay”</m2m:process>

<m2m:commit-right>false</m2m:commit-right>

</indicator>

<participant name="smart metering A">

<entry uri=" http://example.org/m2mResource/dev1 "></entrv>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</m2m:transactionOperationResource>

703. The M2M platform sends a transaction preparation instruction to the transaction participating device 1;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content.

704. The gateway issues a transaction preparation instruction to the transaction participating device 2;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content. The delivered transaction preparation instruction may be generated by the gateway itself, or the gateway may directly forward the transaction preparation instruction from the M2M platform.

705. The transaction participating device 1 returns a transaction preparation response to the M2M platform;

Including transaction resource ID and transaction operation ID.

706. The transaction participating device 2 returns a transaction preparation response to the gateway;

Including transaction resource ID and transaction operation ID.

707. The gateway sends a transaction preparation response to the M2M platform;

Including transaction resource ID and transaction operation ID.

708. The M2M platform submits the transaction;

The M2M platform judges the current transaction execution status according to the aggregated transaction preparation responses. If the two returned transaction preparation responses are all successful, it will be submitted, and if not, it will be rolled back.

709. The M2M platform sends a transaction submission instruction to the transaction participating device 1;

The transaction commit command specifically includes the application ID, address resource ID, transaction resource ID, processing operation content, and commit, which means that the transaction participating device 1 has the right to commit, that is, the current transaction is completed by the transaction participating device 1 alone.

710. The M2M platform sends a transaction submission instruction to the gateway;

The transaction commit instruction specifically includes the application ID, address resource ID, transaction resource ID, processing operation content, and commit, which means that the transaction participating device 2 has the right to commit, that is, the current transaction is completed by the transaction participating device 2 alone.

711. The gateway issues a transaction submission instruction to the transaction participating device 2;

712. The transaction participating device 1 returns a transaction submission response to the M2M platform;

It includes a transaction resource ID and a transaction operation ID, and includes confirm, which means confirmation by the M2M platform.

713. The transaction participating device 2 returns a transaction submission response to the gateway;

It includes a transaction resource ID and a transaction operation ID, and includes confirm, which means confirmation by the M2M platform.

714. The gateway sends a transaction submission response to the M2M platform;

It includes a transaction resource ID and a transaction operation ID, and includes confirm, which means confirmation by the M2M platform.

Wherein, in an embodiment of the present invention, the M2M platform may further return the final result to the transaction requester. Specifically, the M2M platform may directly return the execution result, or wait for the requester to subsequently query the execution result.

Embodiment 7 is applicable to the scenario where transaction participating devices are directly connected to M2M, or a single transaction participating device is directly connected through a gateway. The M2M platform adopts the aggregation of transaction operation responses to control the way of transaction submission, so as to improve the efficiency of transaction processing.

FIG. 11 is a flow chart of a specific implementation of a machine transaction control method according to the eighth embodiment of the present invention, including a requester, an M2M platform, a gateway, a transaction participating device 1, a transaction participating device 2, other gateways or transaction participating devices, and a transaction Participating device 1 and transaction participating device 2 are connected to the gateway, and other gateways or transaction participating devices are connected to the M2M platform. The specific implementation process is as follows:

801. The requester sends a transaction processing request to the M2M platform;

The purpose of this step is to create a transaction resource. The transaction processing request includes the application ID, address resource ID, new resource ID, processing content, and access permission ID. For specific implementation, refer to the following procedure:

POST .../{apiVersion}/m2mResource/transaction/platformCoordinator? resForm

at=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionResource xmlns:ts=urn:m2m:xml:rest:transaction:1″>

<indicator>

<m2m:process>“aggregation”</m2m:process>

<m2m:commit-right>true</m2m:commit-right>

</indicator>

<participant-lists>

<participant name="smart metering A">

<entry uri="http://example.org/m2mResource/gateway/dev1"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering B">

<entry uri="http://example.org/m2mResource/gateway/dev2"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering C">

<entry uri=" http://example.org/m2mResource/dev3 "></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</participant-lists>

</m2m:transactionResource>

802. The M2M platform sends a transaction preparation instruction to the gateway;

The transaction preparation instruction specifically includes the application ID, address resource ID, transaction resource ID, and processing operation content. At the same time, it is specially pointed out that Process = "aggregation" and Commit-Right = "false" to indicate that the aggregation transaction operation response has no commit authority. The implementation refers to the following procedures;

POST .../{apiVersion}/m2mResource/transaction/gatewayCoordinator? resForma

t=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionOperationResource

xmlns:ts="urn:m2m:xml:rest:transaction:1">

<m2m:transactionResource id="1234"/>

<indicator>

<m2m:process>“aggregation”</m2m:process>

<m2m:commit-right>false</m2m:commit-right>

</indicator>

<participant-list>

<participant name="smart metering A">

<entry uri="http://example.org/m2mResource/gateway/dev1"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering B">

<entry uri="http://example.org/m2mResource/gateway/dev2"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</participant-list>

</m2m:transactionOperationResource>

803. The gateway issues a transaction preparation instruction to the transaction participating device 1;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content. The delivered transaction preparation instruction may be generated by the gateway itself, or the gateway may directly forward the transaction preparation instruction from the M2M platform.

804. The gateway issues a transaction preparation instruction to the transaction participating device 2;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content. The delivered transaction preparation instruction may be generated by the gateway itself, or the gateway may directly forward the transaction preparation instruction from the M2M platform.

805. The M2M platform sends a transaction preparation instruction to other gateways or transaction participating devices;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content.

806. The transaction participating device 1 returns a transaction preparation response to the gateway;

Include the transaction resource ID.

807. The transaction participating device 2 returns a transaction preparation response to the gateway;

Include the transaction resource ID.

808. The gateway aggregates the transaction preparation responses;

Where the transaction preparation response of the transaction participating device 2 is failure, it is determined that the current transaction is failure.

809. The gateway returns a failed transaction preparation response to the M2M platform;

810. Other gateways or transaction participating devices return a transaction preparation response to the M2M platform;

811. The M2M platform determines that a rollback is required;

After collecting all transaction operation responses, the M2M platform determines that the current transaction execution status is failed according to at least the failed transaction preparation response in step 811, and determines that a rollback is required.

812. The M2M platform sends a transaction rollback instruction to the gateway;

The transaction rollback instruction specifically includes the application ID, address resource ID, transaction resource ID, processing operation content, and carries the transaction rollback instruction "Rollback", which means rollback;

813. The gateway issues a transaction rollback instruction to the transaction participating device 1;

814. The gateway issues a transaction rollback instruction to the transaction participating device 2;

815. The M2M platform sends a transaction rollback instruction to other gateways or transaction participating devices;

The transaction rollback instruction specifically includes the application ID, address resource ID, transaction resource ID, processing operation content, and carries the transaction rollback instruction "Rollback", which means rollback;

816. The transaction participating device 1 returns a transaction rollback response to the gateway;

Include the transaction resource ID.

817. The transaction participating device 2 returns a transaction rollback response to the gateway;

Include the transaction resource ID.

818. The gateway aggregates the transaction rollback response;

Where both transaction participating device 2 and transaction participating device 1 are successful, it is determined that the rollback of the current transaction is successful. Specifically, two successful transaction rollback responses returned by transaction participating device 2 and transaction participating device 1 can be aggregated into a successful transaction rollback response.

819. The gateway returns a transaction rollback response to the M2M platform;

820. Other gateways or transaction participating devices return a transaction rollback response to the M2M platform;

If other gateways or transaction participating devices return transaction rollback responses to the M2M platform as success, it is determined that the current transaction rollback is successful.

Wherein, in an embodiment of the present invention, the M2M platform may further return the final result to the transaction requester. Specifically, the M2M platform may directly return the execution result, or wait for the requester to subsequently query the execution result.

Embodiment 8 is applicable to the case where multiple transaction participating devices are connected to the M2M platform through the same gateway. The M2M platform generates and sends a transaction operation command to the transaction participation device or the gateway according to the connection attributes of the transaction participation devices, and the transaction operation command carries transaction execution Processing instructions: instructing the gateway to aggregate the transaction operation responses of the multiple transaction participating devices, which improves transaction processing efficiency.

Fig. 12 is a flowchart of a specific implementation of a machine transaction control method according to the ninth embodiment of the present invention, including a requester, an M2M platform, a gateway, a transaction participating device 1, a transaction participating device 2, a transaction participating device 1 and a transaction participating device 2 is connected to the gateway, and transaction participating device 1 and transaction participating device 2 participate in a transaction at the same time, the specific implementation process is as follows:

901. The requester sends a transaction processing request to the M2M platform;

The purpose of this step is to create a transaction resource. The transaction processing request includes the application ID, address resource ID, new resource ID, processing content, and access permission ID. For specific implementation, refer to the following procedure:

POST .../{apiVersion}/m2mResource/transaction/platformCoordinator? resForm

at=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionResource xmlns:ts="urn:m2m:xml:rest:transaction:1">

<indicator>

<m2m:process>“aggregation”</m2m:process>

<m2m:commit-right>true</m2m:commit-right>

</indicator>

<participant-lists>

<participant name="smart metering A">

<entry uri="http://example.org/m2mResource/gateway/dev1"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering B">

<entry uri="http://example.org/m2mResource/gateway/dev2"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</participant-lists>

</m2m:transactionResource>

902. The M2M platform sends a transaction preparation instruction to the gateway;

The transaction preparation instruction specifically includes the application ID, address resource ID, transaction resource ID, and processing operation content. At the same time, it is specially pointed out that Process = "aggregation", Commit-Right = "true", to instruct the gateway to aggregate transaction operation responses, and the gateway has committed Permissions, the specific implementation refers to the following procedures;

POST .../{apiVersion}/m2mResource/transaction/gatewayCoordinator? resForma

t=XML HTTP/1.1

Content-Type: application/xml; charset=UTF-8

Host: example.com:80

<? xml version="1.0" encoding="UTF-8"? >

<m2m:transactionOperationResource

xmlns:ts="urn:m2m:xml:rest:transaction:1">

<m2m:transactionResource id="1234"/>

<indicator>

<m2m:process>“aggregation”</m2m:process>

<m2m:commit-right>true</m2m:commit-right>

</indicator>

<participant-list>

<participant name="smart metering A">

<entry uri="http://example.org/m2mResource/gateway/dev1"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

<participant name="smart metering B">

<entry uri="http://example.org/m2mResource/gateway/dev2"></entry>

<operations type="prepare">

<m2m:turn-on>true</m2m:turn-on>

</operations>

</participant>

</participant-list>

</m2m:transactionOperationResource>

903. The gateway issues a transaction preparation instruction to the transaction participating device 1;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content. The delivered transaction preparation instruction may be generated by the gateway itself, or the gateway may directly forward the transaction preparation instruction from the M2M platform.

904. The gateway issues a transaction preparation instruction to the transaction participating device 2;

The transaction preparation instruction specifically includes application ID, address resource ID, transaction resource ID, and processing operation content. The delivered transaction preparation instruction may be generated by the gateway itself, or the gateway may directly forward the transaction preparation instruction from the M2M platform.

905. The transaction participating device 1 returns a transaction preparation response to the gateway;

Include the transaction resource ID.

906. The transaction participating device 2 returns a transaction preparation response to the gateway;

Include the transaction resource ID.

907. The gateway aggregates the transaction preparation execution response

Wherein, the transaction preparation response of the transaction participating device 2 is failure, and the aggregated result is that the transaction preparation execution fails. If all transaction participating devices return a successful transaction preparation execution response, the aggregated result indicates that the transaction preparation execution is successful.

908. Since the execution result of the current transaction preparation is failure, and the gateway has the decision right to commit the transaction, it decides to perform a transaction rollback operation on the transaction participating devices 1 and 2 under its jurisdiction; if the execution result of the transaction preparation is successful, the gateway can decide Perform a transaction commit operation on the transaction participating devices 1 and 2 under its jurisdiction.

909. The gateway sends a transaction rollback instruction to the transaction participating device 1, which carries a transaction rollback instruction "Rollback", indicating rollback;

910. The gateway sends a transaction rollback instruction to the transaction participating device 2, which carries a transaction rollback instruction "Rollback", indicating rollback;

911. The transaction participating device 1 returns a transaction rollback response to the gateway;

Include the transaction resource ID.

912. The transaction participating device 2 returns a transaction rollback response to the gateway;

Include the transaction resource ID.

913. The gateway returns the transaction execution result to the M2M platform;

Wherein, in an embodiment of the present invention, the M2M platform may further return the final result to the transaction requester. Specifically, the M2M platform may directly return the execution result, or wait for the requester to subsequently query the execution result.

Embodiment 9 is applicable to the situation that all transaction participating devices are connected to the M2M platform through the same gateway, and the M2M platform generates and sends a transaction operation command to the transaction participating device or the gateway according to the connection attributes of the transaction participating devices, and the transaction operation The command carries a transaction execution processing instruction; instructing the gateway not only to aggregate the transaction preparation responses of the multiple transaction participating devices, but also to judge the transaction execution status locally by the gateway, so as to further process the commit or rollback operation of the transaction locally at the gateway, There is no need to return to the M2M platform to judge and execute subsequent transaction operations, which improves transaction processing efficiency.

Fig. 13 is a schematic structural diagram of a machine-to-machine gateway according to a tenth embodiment of the present invention, including:

The receiving unit 1301 is configured to receive a transaction operation command from the M2M platform, the transaction operation command includes a transaction execution processing instruction instructing the M2M gateway to converge and forward the transaction operation response; receive the transaction operation response returned by the transaction participating device;

An aggregation unit 1302, configured to aggregate the transaction operation responses received by the receiving unit 1301;

The sending unit 1303 is configured to send a transaction operation command to connected transaction participating devices; and send the transaction operation response collected by the converging unit 1302 to the M2M platform.

Fig. 14 is a schematic structural diagram of a machine-to-machine gateway according to an eleventh embodiment of the present invention, including:

The receiving unit 1401 is configured to receive a transaction operation command from the M2M platform, the transaction operation command includes instructing the M2M gateway to aggregate the transaction operation response and control the execution of the subsequent transaction update operation, and then return the transaction execution result of the transaction execution processing instruction; receive the connected transaction participation A transaction preparation response returned by the device; receiving a transaction update response from the transaction participating device;

The aggregation processing unit 1402 is configured to aggregate the received transaction preparation responses according to the transaction execution processing instruction received by the receiving unit 1401, and generate a transaction update instruction according to the result of the aggregation transaction preparation response; and aggregate the received transaction update responses according to the transaction execution processing instruction ;

The sending unit 1403 is configured to issue a transaction preparation instruction to the transaction participating device according to the transaction execution processing instruction received by the receiving unit 1401; issue a transaction update instruction to the transaction participating device; update and respond to the execution result corresponding to the transaction collected by the aggregation processing unit 1402 Return to the M2M platform.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the programs can be stored in a computer-readable storage medium. During execution, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random access memory (Random Access Memory, RAM), etc.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (16)

1. A machine transaction control method, characterized in that the method comprises, The machine-to-machine M2M platform receives the transaction processing request sent by the requester; The M2M platform generates and sends a transaction operation command to the transaction participating device or the M2M gateway according to the connection attribute of the transaction participating device; The M2M platform receives the transaction operation response returned by the transaction participating device or the M2M gateway, and the transaction operation response is returned after the transaction participating device or the M2M gateway executes the transaction according to the transaction operation command. 2. The method according to claim 1, wherein the transaction participating device is directly connected to the M2M platform; The M2M platform generates and sends transaction operation commands to the transaction participating devices or the M2M gateway according to the connection attributes of the transaction participating devices, including: The M2M platform generates and sends transaction operation commands to transaction participating devices, and the transaction operation commands are transaction preparation instructions or transaction update instructions; The transaction participating device or the M2M gateway executes the transaction according to the transaction operation command, and returns the transaction operation response according to the transaction execution processing instruction including: The transaction participating device executes the transaction preparation instruction and returns a transaction preparation response to the M2M platform, and the transaction participation device executes the transaction update instruction and returns a transaction update response to the M2M platform. 3. The method according to claim 1, wherein a single device among the transaction participating devices is connected to the M2M platform via the M2M gateway; The M2M platform generates and sends a transaction operation command to the transaction participation device or the M2M gateway according to the connection attribute of the transaction participation device, including: the M2M platform generates and sends the transaction operation command to the M2M gateway, and the M2M gateway sends the transaction operation commands to said single device; The transaction participating device or the M2M gateway executes the transaction according to the transaction operation command, and returns the transaction operation response according to the transaction execution processing instruction including: after the M2M gateway receives the transaction operation response from the single device, according to the The transaction operation command issued by the M2M platform forwards the transaction operation response to the M2M platform. 4. The method according to claim 3, wherein the transaction operation command issued by the M2M platform includes a transaction execution processing instruction instructing the gateway to send a transaction operation response. 5. The method according to claim 1, wherein at least two of the transaction participating devices are connected to the M2M platform via the same M2M gateway; The M2M platform generating and issuing transaction operation commands to transaction participating devices or M2M gateways according to the connection attributes of transaction participating devices includes: the M2M platform generating and issuing transaction operation commands to transaction M2M gateways, and the M2M gateway issuing transaction An operation command is sent to the at least two devices, the transaction operation command includes a transaction execution processing indication instructing the M2M gateway to aggregate and forward the transaction operation response; The transaction participating device or the M2M gateway executing the transaction according to the transaction operation command, and returning the transaction operation response according to the transaction execution processing instruction includes: after the M2M gateway receives the transaction operation response from the at least two devices, Aggregating received transaction operation responses according to the transaction execution processing instructions, and sending the aggregated transaction operation responses to the M2M platform. 6. The method according to claim 1, wherein all devices among the transaction participating devices are connected to the M2M platform via the same M2M gateway; The M2M platform generates and sends a transaction operation command to the transaction participation device or the M2M gateway according to the connection attribute of the transaction participation device. After the M2M gateway controls and executes the subsequent transaction update operation, it returns a transaction execution processing instruction of the transaction execution result; the M2M gateway sends a transaction preparation instruction to all devices according to the transaction execution processing instruction; The transaction participating device or the M2M gateway executes the transaction according to the transaction operation command, and returns the transaction operation response according to the transaction execution processing instruction including: The M2M gateway returns a transaction execution result to the M2M platform according to the transaction operation command issued by the M2M platform. 7. The method according to claim 6, wherein the M2M gateway returns a transaction execution result to the M2M platform according to the transaction operation command issued by the M2M platform, comprising: The M2M gateway aggregates the received transaction preparation responses from all devices according to the transaction execution processing instructions, generates and sends transaction update instructions to all devices according to the results of the aggregated transaction preparation responses; according to the transaction The execution processing instructs to aggregate the received transaction update responses from all devices, and return the execution results corresponding to the aggregated transaction update responses to the M2M platform. 8. The method according to claim 7, wherein when the result of the aggregated transaction preparation response is preparation success, the transaction update instruction is a transaction commit instruction; or When the result of the aggregated transaction preparation response is preparation failure, the transaction update instruction is a transaction rollback instruction. 9. A machine transaction control system, characterized in that the system comprises, The machine-to-machine M2M platform is used to receive the transaction processing request sent by the requesting party, and generate and issue transaction operation commands according to the connection attributes of the transaction participating devices; The transaction participating device is configured to execute a transaction according to the transaction operation command, and send a transaction operation response to the M2M platform. 10. The machine transaction control system according to claim 9, wherein one of the transaction participating devices is connected to the M2M platform via a first M2M gateway, and the first M2M gateway is used to provide The one transaction participating device issues a transaction operation command, and sends the received transaction operation response to the M2M platform. 11. The machine transaction control system according to claim 9, wherein at least two of the transaction participating devices are connected to the M2M platform via a second M2M gateway, and the transaction operation command includes instructing the second M2M The gateway aggregates and forwards the transaction execution processing indication of the transaction operation response; The second M2M gateway is configured to issue a transaction operation command to the at least two transaction participating devices, aggregate the transaction operation responses returned by the at least two devices according to the transaction operation command, and aggregate the transaction The operation response is sent to the M2M platform. 12. The machine transaction control system according to claim 9, wherein the number of the transaction participating devices is at least two, and the at least two transaction participating devices are connected to the M2M platform via a third M2M gateway, the The transaction operation command includes a transaction execution processing instruction that instructs the third M2M gateway to control and execute the subsequent transaction update operation and return the transaction execution result; The third M2M gateway is configured to issue a transaction preparation instruction to all the devices according to the transaction execution processing instruction; after receiving the transaction preparation responses from all the devices, aggregate the received transactions according to the transaction execution processing instruction A transaction preparation response, generating and issuing a transaction update instruction to all devices according to the result of the aggregated transaction preparation response; after receiving the transaction update responses from all the devices, aggregating received transaction updates according to the transaction execution processing instructions In response, the result of the aggregated transaction update response is returned to the M2M platform. 13. A machine-to-machine platform, characterized in that the machine-to-machine platform comprises, a receiving unit, configured to receive a transaction processing request sent by a requesting party; A generating unit, configured to generate a transaction operation command according to connection attributes of transaction participating devices after the receiving unit receives the transaction processing request; The sending unit is configured to send the transaction operation command generated by the generating unit to the transaction participating device or the M2M gateway. 14. The machine-to-machine platform of claim 13, wherein the transaction operation command is a transaction prepare instruction; The receiving unit is further configured to receive a transaction preparation response returned by a transaction participating device or a gateway; The machine-to-machine platform further includes, The judging unit is used to aggregate the transaction preparation responses received by the receiving unit, and judge the transaction preparation status according to the aggregated transaction preparation. If successful, it will send a transaction submission instruction to the transaction participating device, and if it fails, send a transaction submission instruction to the transaction participating device. Send a transaction rollback command. 15. A machine-to-machine gateway, comprising: The receiving unit is configured to receive a transaction operation command from the M2M platform, the transaction operation command includes a transaction execution processing instruction indicating that the M2M gateway converges and forwards the transaction operation response; receives the transaction operation response returned by the transaction participating device; an aggregation unit, configured to aggregate the transaction operation responses received by the receiving unit; The sending unit is configured to send a transaction operation command to the connected transaction participating devices; and send the transaction operation response collected by the convergence unit to the M2M platform. 16. A machine-to-machine gateway, comprising: The receiving unit is configured to receive a transaction operation command from the M2M platform, the transaction operation command includes instructing the M2M gateway to control and execute the subsequent transaction update operation, and then return the transaction execution result instruction; receive the transaction returned by the connected transaction participating device preparing a response; receiving a transaction update response from the transaction participating device; The aggregation processing unit is configured to aggregate received transaction preparation responses according to the transaction execution processing instruction, and generate a transaction update instruction according to the result of the aggregation transaction preparation response; aggregate the received transaction update responses according to the transaction execution processing instruction; A sending unit, configured to issue a transaction preparation instruction to the transaction participating device according to the transaction execution processing instruction; issue a transaction update instruction to the transaction participating device; Results are returned to the M2M platform.

Images