Gateway-Based Address Verification for Automation Networks
Solution Overview
Problem
Existing automation systems face challenges in ensuring secure and reliable addressing of automation components, particularly in hyperconverged infrastructures where multiple control processes are executed on central hardware, due to limited address space and the complexity of implementing device-specific identifiers.
Innovation Solution
A device and method for coupling a device network to a communications network using a processing device that signs and verifies data telegrams with device-specific identifiers, such as 64-bit BaseIDs, and acts as a gateway to adapt data telegrams between networks, ensuring correct addressing and verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional addressing methods with codenames are used, then addressing can be implemented with existing hardware, but the address space is limited and organizational effort is considerable
Solution Approach 1:
The patent changes the parameter of identifier length from 32-bit to 64-bit, dramatically expanding the address space from approximately 4 billion to 18 quintillion possible addresses. This parameter change allows unique addressing of automation devices without increasing organizational complexity, as the extended identifier format is automatically handled by the gateway device.
2Adaptability or versatility
If control processes for multiple automation systems are consolidated on central hardware, then a unified software environment is achieved, but the challenge for correct addressing and verification increases
Solution Approach 1:
The gateway device serves as an intermediary between the central control device and automation devices. It receives data telegrams from the control device, adds or verifies extended 64-bit identifiers, and forwards them to the appropriate automation devices. This intermediary function maintains reliability by ensuring correct addressing even in consolidated control architectures where multiple control processes run on shared hardware.
3Reliability
If device-specific identifiers are implemented in existing automation devices, then secure addressing is achieved, but implementation complexity increases for existing hardware
Solution Approach 1:
The gateway device acts as an intermediary that handles the complexity of extended identifier management externally. For automation devices that support 64-bit identifiers, the gateway adds or verifies these identifiers transparently. For devices without native support, the gateway performs the verification function centrally, allowing secure addressing without modifying existing automation device hardware.
Solution Approach 2:
The patent segments the identifier handling function between the gateway device and automation devices. The gateway manages the complex 64-bit identifier generation, verification, and formatting, while automation devices can use simplified processing. This segmentation allows existing hardware to benefit from enhanced security without requiring complex modifications.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The invention relates to a system for verifying the addressing of components in an automation system with a hyper-converged infrastructure. In particular, a gateway is proposed which can extend data telegrams with a device-specific signature if such a signature cannot be implemented by the automation device of the automation system itself.