OPC UA Aggregated Address Space for Multi-Server Version Conflicts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing OPC UA-based client-server communication systems are limited to connecting with a single server at a time, face version incompatibilities leading to type conflicts, and are incapable of handling runtime changes in the server's address space.

Innovation Solution

An aggregator system that generates an aggregated address space by browsing and mapping nodes from multiple servers, using unique identifiers to avoid conflicts, and dynamically updates the space in real-time to handle data and model change events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple instances of the client are deployed to connect to multiple servers, then the client can communicate with multiple servers, but the development effort and system complexity increase

Engineering Contradiction:
Improveability to connect to multiple serversVSAvoiddevelopment effort
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple server connections into a single client instance by introducing an aggregator component that consolidates address spaces from multiple servers. The aggregator combines nodes and variables from different servers into unified address spaces (first and second address spaces), allowing a single client to interact with multiple servers through consolidated interfaces, thereby reducing development effort while maintaining multi-server connectivity

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If servers implement different versions of information models, then each server can use its own version, but type conflicts occur between versions

Engineering Contradiction:
Improvesupport for different server versionsVSAvoidtype conflicts
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the address space into distinct first and second address spaces, where each address space corresponds to a specific server version. This segmentation allows different versioned servers to coexist without type conflicts, as each maintains its own namespace. The system handles version compatibility by organizing nodes and variables in separate address spaces that can be independently managed and accessed by the client

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If the server address space changes at runtime, then the server can adapt dynamically, but existing OPC UA client-server communication cannot handle these changes

Engineering Contradiction:
Improveruntime address space changesVSAvoidcommunication stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic address space management by enabling the aggregator to detect, process, and adapt to runtime changes in server address spaces. The system monitors for additions, deletions, and modifications of nodes and variables, automatically updating the consolidated address spaces to reflect current server states. This dynamic capability allows the client to maintain stable communication while servers evolve their address spaces at runtime

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4160415B1System and method for enabling client-server communication using OPC UA protocol
Publication Date: 2026.04.29 SIEMENS MOBILITY GMBH
  • EP4160415B1 patent drawingFigure 1A
  • EP4160415B1 patent drawingFigure 1B
  • EP4160415B1 patent drawingFigure 2

AI summary

Disclosed herein is a system (100) and method for enabling client-server communication using OPC UA protocol. The method comprises establishing connection with one or more servers (110), by an aggregator (105) associated with a client device (115). Further, an aggregated address space for the servers (110) is generated, by the aggregator (105), based on address spaces of the servers (110). Further, an event in an address space of at least one of the servers (110) is detected, by the aggregator (105), in real-time. Based on the event, the aggregated address space is updated, by the aggregator (105).