Hardware-Accelerated OPC UA Server Dual Address Space

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional embedded OPC UA Server applications are too slow to meet real-time operation requirements and are insufficient for handling large amounts of data, particularly in instrumentation devices.

Innovation Solution

A hardware-accelerated OPC UA Server is implemented with a dual address space architecture, where a hardware control circuit determines the access type (slow or fast) based on data requirements, storing non-time-critical data in a conventional memory unit and time-critical data in a hardware-implemented second address space for efficient access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a pure software-based OPC UA Server is used, then it can handle several thousand nodes in the address space, but it is too slow to meet real-time operation requirements

Engineering Contradiction:
Improvenumber of nodesVSAvoiddata access speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The address space is segmented into two separate memory structures: a first memory structure for non-time-critical data and a second memory structure for time-critical data. This segmentation allows the system to handle large numbers of nodes while providing fast access paths for real-time operations by routing time-critical data through dedicated hardware logic.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A control circuit acts as an intermediary between the OPC UA client and the dual memory structures. The control circuit determines whether requested data is time-critical or non-time-critical and routes the access accordingly, enabling the system to maintain both high capacity and real-time performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If a hardware-accelerated OPC UA Server is used, then it can provide fast data access, but it can only handle a few hundred nodes which is too small for all needed data

Engineering Contradiction:
Improvedata access speedVSAvoidnumber of nodes
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The address space is segmented into two separate memory structures: a first memory structure for non-time-critical data and a second memory structure for time-critical data. This segmentation allows the system to handle large numbers of nodes while providing fast access paths for real-time operations by routing time-critical data through dedicated hardware logic.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The hardware-accelerated control circuit is designed to handle both time-critical and non-time-critical data routing decisions, making it a universal interface that can manage diverse data types. The system can adaptively route different data types through appropriate paths, enabling the hardware to serve multiple functions simultaneously.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Device complexity

If data is stored in a single memory location, then storage is simplified, but access speed varies depending on data type requirements

Engineering Contradiction:
Improvememory structure complexityVSAvoiddata access speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The address space is segmented into two separate memory structures: a first memory structure for non-time-critical data and a second memory structure for time-critical data. This segmentation allows the system to handle large numbers of nodes while providing fast access paths for real-time operations by routing time-critical data through dedicated hardware logic.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different memory locations are optimized for different data access requirements. The second memory structure is optimized for fast time-critical access with dedicated hardware logic, while the first memory structure handles non-time-critical data. This local optimization ensures that each data type is stored in the most appropriate location for its access pattern.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP4068104B1Method for controlling an OPC UA server, OPC UA server, computer program, and computer-readable medium
Publication Date: 2024.06.12 ABB (SCHWEIZ) AG
  • EP4068104B1 patent drawingFigure 1~2
  • EP4068104B1 patent drawingFigure 3~4
  • EP4068104B1 patent drawingFigure 5

AI summary

A method for controlling an OPC UA Server (20) and an OPC UA Server (20) are provided. The method comprises: receiving a request (50) for data from an OPC UA Client (40); determining, whether the request (50) and/or the data requires a slow data access or a fast data access, by a hardware implemented control circuit (28) of the OPC UA Server (20); obtaining first data (54) from a memory unit (24, 26) of the OPC UA Server (20), if the request (50) and/or the data requires the slow data access; obtaining second data (56) from an second address space (30) of the control circuit (28), if the request (50) and/or the data requires the fast data access; and sending the obtained first or second data (56) to the OPC UA Client (40).