Automation System Program Update via Parallel Processing Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing automation systems face downtime and loss of redundancy during system software updates, which is disruptive and contradicts customer expectations of reliability.

Innovation Solution

A method for updating system programs in automation systems involves synchronizing processing instances across subsystems, loading updated system programs onto secondary processing instances, and transferring state information to ensure seamless redundancy during the update process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If system software update is performed in automation system, then system functionality is improved, but system downtime increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidsystem downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The automation system is divided into multiple processing instances (primary and secondary) that can operate independently. The update process is segmented by loading new software onto the secondary processing instance first, then switching over, allowing continuous operation during updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The secondary processinginstance pre-loads and pre-tests the updated system software before switching over. This preliminary action ensures the new software is ready and functional before taking over control, minimizing downtime.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If system software update is performed in automation system, then system functionality is improved, but redundancy is lost

Engineering Contradiction:
Improvesystem functionalityVSAvoidredundancy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system maintains separate primary and secondary processing instances with independent software instances. During update, the secondary instance runs the new software while the primary continues running the old software, preserving redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The secondary processinginstance pre-loads and pre-tests the updated system software before switching over. This preliminary action ensures the new software is ready and functional before taking over control, minimizing downtime.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If redundant processing instances are maintained, then system reliability is improved, but system complexity increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The secondary processinginstance is a copy of the primary processinginstance with identical hardware and software architecture. This copying approach maintains reliability through redundancy while simplifying the update process by using identical components.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The secondary processinginstance pre-loads and pre-tests the updated system software before switching over. This preliminary action ensures the new software is ready and functional before taking over control, minimizing downtime.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4567591A1Method for updating a system program in an automation system
Publication Date: 2025.06.11 SIEMENS AG
  • EP4567591A1 patent drawingFigure 1
  • EP4567591A1 patent drawingFigure 2
  • EP4567591A1 patent drawingFigure 3

AI summary

A method for updating a system program in an automation system, comprising the steps of: a) executing a first control program installed on a first system program on a first processing instance in a first subsystem of the automation system and executing a second control program installed on a second system program on a first processing instance in a second subsystem of the automation system, b) providing a second processing instance in each of the first and second subsystems, loading an updated version of the first and second system programs onto the respective second processing instances, and starting the respective second processing instances in parallel to step a), wherein a third control program is installed on the updated version of the first system program and a fourth control program is installed on the updated version of the second system program,and c) updating the third control program in dependence on a memory image of all state information of the first control program and updating the fourth control program in dependence on a memory image of all state information of the second control program.