Secure Device Onboarding via Local Identifier Assignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secured automation systems face challenges in efficiently and securely onboarding new devices without manual configuration steps, particularly in establishing mutual trust and authentication for secure communication.

Innovation Solution

A method and system that automates the onboarding process by using a secure communication server to check device identifiers, assigning a local identifier if necessary, and interacting with an authentication authority to ensure secure communication, enabling devices to authenticate and communicate with the automation system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If an automated onboarding process is implemented to minimize manual configuration steps, then ease of operation is improved, but secure authentication and mutual trust establishment become more complex

Engineering Contradiction:
Improvedevice onboardingVSAvoidauthentication procedure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a secure communication server as an intermediary component that mediates between the device and the automation system. This server handles the complex authentication and credential exchange processes, allowing devices to be onboarded automatically without manual configuration while maintaining secure authentication. The intermediary absorbs the complexity of the authentication procedure, presenting a simple interface to end users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a VPN connection is used for secure communication between devices and the automation system, then system security is improved, but device complexity and configuration requirements increase

Engineering Contradiction:
Improvecommunication securityVSAvoidnetworking configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where the secure communication server automatically manages VPN connections and credential distribution. Devices don't require manual networking configuration or VPN setup - the server handles these tasks automatically during the onboarding process. This maintains the security benefits of VPN connections while eliminating the complexity of manual networking configuration.

Inventive Principle:
Principle #25Self-service

3Reliability

If mutual trust is established before credential exchange in the onboarding process, then system security is improved, but the onboarding process cannot be fully automated

Engineering Contradiction:
Improveauthentication securityVSAvoidonboarding process
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The patent implements preliminary action by having the secure communication server pre-generate and distribute credentials to devices during the initial connection phase, before formal authentication occurs. This allows the onboarding process to be fully automated while maintaining security, as the credentials are established in advance through automated key exchange protocols, eliminating the need for manual trust establishment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4704378A1Method and system for establishing a secure communication between a device and a component of a secured automation system
Publication Date: 2026.03.04 SIEMENS SCHWEIZ AG
  • EP4704378A1 patent drawingFigure 1~2
  • EP4704378A1 patent drawing
  • EP4704378A1 patent drawing

AI summary

The invention relates to a method and a system for establishing a secure communication (SC) between a device (Dev) and a component (C) of a secured automation system, the method comprising: a) establishing a communication (SC) between the device (Dev) and a secure communication server (SCS), b) checking a device identifier (IDevID, LDevID) of the device (Dev), c1) if the device identifier (IDevID, LDevID) is an initial device identifier (IDevID), assigning a local device identifier (LDevID) to the device (Dev), stopping the communication (SC) between the device (Dev) and the secure communication server (SCS), and returning to step a), or c2) if the device identifier (IDevID, LDevID) is a local device identifier (LDevID), establishing a secure communication (SC) between the device (Dev) and the component (C) of the secured automation system using the local device identifier (LDevID).