OPC UA Transaction Management for Data Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The OPC UA protocol lacks a specified transaction context for individual service calls, leading to issues where some write operations may succeed while others fail, especially in scenarios with multiple OPC UA clients making changes to a server.
Innovation Solution
A transaction management component is integrated into OPC UA service calls to establish a transaction context, enabling OPC UA clients to communicate with servers using transactions, and supporting features like two-phase commit protocols and caching mechanisms to manage data changes and confirmations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple OPC UA clients simultaneously make changes to an OPC UA server without transaction context, then individual write operations can be performed, but data integrity and consistency cannot be guaranteed when some operations succeed and others fail
Solution Approach 1:
The patent segments the write operations into individual service calls within a transaction context, allowing each operation to be tracked and managed separately. This segmentation enables the system to identify which specific operations succeeded or failed, forming the basis for reliable transaction management and data integrity assurance.
Solution Approach 2:
The patent introduces a transaction context as an intermediary layer between multiple OPC UA clients and the server. This intermediary manages the coordination of simultaneous write operations, ensuring that either all operations commit successfully or none do, thereby preventing partial updates that would compromise data integrity.
2Reliability
If a transaction context is integrated into OPC UA service calls, then data consistency across multiple service calls is ensured, but the complexity of the communication protocol increases
Solution Approach 1:
The patent merges the transaction context management directly into the existing OPC UA service call structure. By combining transactional capabilities with the standard service call mechanism, the system ensures data consistency without requiring a completely separate communication protocol, thus limiting the increase in overall system complexity.
Solution Approach 2:
The transaction context is designed as a universal mechanism that can be applied to any OPC UA service call. This multi-functional approach allows the same transaction management infrastructure to handle various types of operations (reads, writes, configuration changes), reducing the need for operation-specific complexity while ensuring consistent transactional behavior across all service calls.
Data Source
AI summary
A method and a corresponding device are disclosed for communicating between clients and servers of a client/server system using the standard protocol OPC UA, and for the interaction of an OPC UA client with an OPC UA server, OPC UA service calls are used. In order to integrate a transaction context in OPC UA service calls, all OPC UA servers of the system are complemented by a transaction management component, and in order to carry out transactions, appropriately configured OPC UA clients communicate with respective OPC UA servers using transactions.