Rail Vehicle Control Software Checksum Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for authorizing control software in rail vehicles across multiple countries are inefficient, requiring frequent changes and re-authorization, leading to increased costs, complexity, and maintenance burdens due to country-specific regulations and the need for redundant memory systems and time-intensive reloading of programs.

Innovation Solution

A method that generates a unique overall checksum for the control software based on function-dependent and structure-dependent checksums, allowing for easy identification and verification of changes, enabling country-specific adaptations without altering the software's structure, and maintaining existing authorizations by using a country-specific checksum for verification and authorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If country-specific control software is kept on the rail vehicle and reloaded at borders, then authorization for different countries is achieved, but device complexity increases due to redundant memory systems and multiple controllers

Engineering Contradiction:
Improveauthorization for different countriesVSAvoidredundant memory systems and multiple controllers
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The control software is segmented into a country-identifying component and a functional component. The country identifier is stored in a compact form (e.g., single byte) rather than duplicating entire software versions, significantly reducing memory requirements while maintaining the ability to adapt to different countries' regulations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A single controller is designed to handle multiple countries' requirements through a universal architecture that uses the country identifier to dynamically adjust behavior. This eliminates the need for multiple dedicated controllers for different countries, reducing device complexity while maintaining versatility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If control software is reloaded at national borders, then country-specific authorization is achieved, but loss of time occurs due to time-intensive reloading process

Engineering Contradiction:
Improvecountry-specific authorizationVSAvoidtime-intensive reloading
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The country identifier is determined and processed in advance before the actual control software execution. By pre-identifying the country and loading only the necessary country-specific parameters rather than entire software versions, the system minimizes border crossing delays while ensuring proper authorization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The country-specific authorization information is extracted from the full control software into a separate, compact country identifier. This allows the system to quickly switch between countries by only loading the essential identifier and corresponding parameters, rather than reloading complete software versions, significantly reducing the time required at borders.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of manufacture

If standardized control software is used across multiple countries, then manufacturing cost is reduced, but authorization verification becomes more complex due to different country rules

Engineering Contradiction:
Improvestandardized control softwareVSAvoidauthorization verification process
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The control software is designed with local quality by incorporating a country identifier that enables the same standardized software to adapt to different local regulations. The country-specific parameters and rules are applied locally based on the identifier, allowing manufacturers to produce a single standardized version while maintaining compliance with various country-specific requirements through configuration rather than code changes.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12189825B2Method for identifying and verifying control software of a rail vehicle
Publication Date: 2025.01.07 SIEMENS MOBILITY GMBH
  • US12189825B2 patent drawing
  • US12189825B2 patent drawing
  • US12189825B2 patent drawing

AI summary

A method identifies and verifies control software of a rail vehicle. In the method, the control software is formed by functions, with each function fulfilling an associated task. As a networked collective, the functions form the structure of the control program. A function-dependent checksum is generated for each function. A structure-dependent checksum is generated for the structure. A total checksum is generated for the control software from the function-dependent checksums and the structure-dependent checksum. The total checksum identifies and verifies the control software for homologation in a country.