Bus Device OS Update via Segmented Application

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

End customers in the field of bus-oriented programmable electrical installations, such as KNX bus systems, face difficulties in performing operating system updates as existing methods are cumbersome, costly, and require removing and re-installing bus devices, lacking a storage space-efficient solution.

Innovation Solution

A method involving an update application with a communication stack and hardware adaptation for flash access, which takes control of the bus device, initializes interrupt vectors, and updates the operating system without requiring extensive storage space, allowing for efficient updates without external tools and minimizing development effort by separating the update application from the new operating system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the existing method for operating system updates is used (removing and re-installing bus devices), then the update can be performed, but the process is cumbersome, costly, and time-consuming

Engineering Contradiction:
Improveease of operating system updateVSAvoidtime for update process
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the update process by separating the update application from the operating system itself. The update application is loaded into RAM as a separate entity that can execute update functions without requiring physical device removal or full system reinstallation, thereby simplifying the update process and reducing time loss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The update application acts as an intermediary between the configuration device and the operating system. It provides a communication interface that allows the configuration device to transfer the new operating system to the bus device's memory and execute the update process without requiring physical intervention, thus making the update easier and faster.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Extent of automation

If a comprehensive update application including communication stack and hardware adaptations is loaded into memory, then the update can be performed autonomously, but memory space requirements increase

Engineering Contradiction:
Improveautonomy of update processVSAvoidmemory space requirement
Core Design Contradiction:
Extent of automationVSQuantity of substance

Solution Approach 1:

The update application is designed to be dynamically loaded into RAM only when needed for the update process. After the update is completed and the new operating system is installed, the update application can be unloaded or overwritten, allowing the memory to be reused. This dynamic approach provides automation while managing memory space efficiently.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the state of the update application from a permanent resident program to a temporary loaded program. By controlling when the update application is loaded into RAM (only during update operations) and allowing it to be overwritten or removed afterward, the system achieves high automation during updates while minimizing long-term memory space requirements.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If the update application takes full control of the bus device, then the existing operating system can be completely replaced, but the device becomes inaccessible during the update

Engineering Contradiction:
Improveability to replace operating systemVSAvoiddevice accessibility during update
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The update application performs preliminary actions by establishing full control and loading the new operating system into memory before the old system is discarded. This ensures that the replacement process is complete and successful before the device transitions to the new system, maintaining reliability through careful sequencing of control transfer and system replacement.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the physical mechanism of device removal and reinstallation with a software-based substitution where the update application temporarily takes control in memory space. This substitution allows complete operating system replacement while keeping the device physically accessible and connected throughout the process, maintaining both adaptability and reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP3118739B1Method for carrying out an operating system update
Publication Date: 2020.01.29 SIEMENS SCHWEIZ AG
  • EP3118739B1 patent drawingFigure 1~2
  • EP3118739B1 patent drawingFigure 3~4
  • EP3118739B1 patent drawingFigure 5

AI summary

A method for performing an operating system update for a bus device of a bus-oriented programmable electrical installation, wherein the bus device comprises a processor (microcontroller) and memory, the method comprising the following steps: - generating an update application that includes a communication stack and corresponding hardware adaptation for communication and flash access of the device; - loading the update application into memory, wherein after loading the update application takes control of the bus device and the existing operating system is no longer accessible; - initializing the interrupt vectors so that they point to the update application; and - performing the operating system update, wherein the device's individual data is stored in such a way that the update application can access it during the execution of the operating system update;and wherein, during the execution of the operating system update, the communication of the bus device takes place via the update application.