Method and device for client/server communication according to the standard protocol OPC UA

1. A method for communication between a client and a server in a client/server system using an OPC UA protocol, comprising:

making a OPC UA service call for interaction between an OPC UA client and an OPC UA server; and

carrying out communications between the OPC UA client and the OPC UA server via transactions integrated in OPC UA service calls in a transaction context using a transaction management component, such that OPC UA clients arranged to carry out transactions each communicate with an OPC UA server using transactions wherein for communication between an OPC UA client and an OPC UA server using transactions:

configuring an OPC UA session;

calling a method for starting a transaction by the OPC UA client;

receiving, at the transaction management component of the OPC UA server, information relating to the start of a transaction;

manipulating data at the OPC UA client and checking the permissibility of the manipulation by the transaction management component; and

calling, in order to conclude the transaction, via the OPC UA client, a method for confirming the transaction and, after corresponding checking by the transaction management component, inducing the manipulation of data in an addressed device.

2. The method as claimed in claim 1 , comprising:

supplementing the OPC UA server with a transaction management component;

and carrying out transactions both with OPC UA clients arranged to carry out transactions and, in a client function, with the OPC UA server.

3. The method as claimed in claim 2 , comprising:

configuring the OPC UA servers to also communicate with OPC UA clients, which are not arranged to carry out transactions, without using transactions.

4. The method as claimed in claim 1 , comprising:

configuring the OPC UA server to also communicate with OPC UA clients, which are not arranged to carry out transactions, without using transactions.

5. A device for communication between clients and servers in a client/server system using an OPC UA protocol, wherein OPC UA service calls are used for interaction between an OPC UA client and an OPC UA server, the device comprising:

a transaction management component for supplementing all OPC UA servers in the system in order to integrate a transaction context in OPC UA service calls; and OPC UA clients arranged to carry out transactions, wherein for communicating between the OPC UA client and the OPC UA server using transactions, the device is configured to configure an OPC UA session;

call a method for starting a transaction by the OPC UA client;

receive, at the transaction management component of the OPC UA server, information relating to the start of a transaction;

manipulate data at the OPC UA client and checking the permissibility of the manipulation by the transaction management component; and

call, in order to conclude the transaction, via the OPC UA client, a method for

confirming the transaction and, after corresponding checking by the transaction management component, inducing the manipulation of data in an addressed device.

6. The device as claimed in claim 5 , wherein the device is configured to:

aggregate OPC UA servers in the system which are each supplemented with a transaction management component for carrying out transactions both with OPC UA clients arranged to carry out transactions and, in a client function, with OPC UA servers.

7. The device as claimed in claim 6 , wherein the OPC UA server with an implemented transaction management component is configured to accept required configuration data from a configuration database and also

real-time data from controllers and devices connected thereto or other data sources and to manipulate data there, and the configuration database is set up to support transactions.

8. The device as claimed in one of claim 6 , wherein the OPC UA server is configured to support interleaved transactions.

9. The device as claimed in claim 5 , wherein the OPC UA server with an implemented transaction management component is configured to accept required configuration data from a configuration database and also real-time data from controllers and devices connected thereto or other data sources and to manipulate data there, and the configuration database is set up to support transactions.

10. The device as claimed in claim 9 , wherein the OPC UA server is configured to use a real-time data transaction device to check whether requested changes are permissible and to delay the operation of making the changes until a respective OPC UA client confirms the transaction.

11. The device as claimed in claim 10 , wherein the OPC UA server is configured to use a cache memory and caching mechanisms to store potentially changed data in order to provide the OPC UA client with a correct representation of the data in the transaction context.

12. The device as claimed in one of claim 10 , wherein the OPC UA server is configured to support interleaved transactions.

13. The device as claimed in claim 9 , wherein the OPC UA server is configured to use a cache memory and caching mechanisms to store potentially changed data in order to provide the OPC UA client with a correct representation of the data in the transaction context.

14. The device as claimed in one of claim 13 , wherein the OPC UA server configured to support interleaved transactions.

15. The device as claimed in one of claim 9 , wherein the OPC UA server is configured to support interleaved transactions.

16. The device as claimed in one of claim 5 , wherein the OPC UA server is configured to support interleaved transactions.