Radio Block Centre Multi-Version Management for ETCS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current ETCS system version management strategy requires all trains in a fleet to be upgraded before the RBC can be upgraded to a new version, leading to delays in deploying up-to-date systems, especially in scenarios with diverse train operators, and necessitates extensive agreements between infrastructure owners and operators.

Innovation Solution

An enhanced RBC capable of managing multiple ETCS system versions, including a primary module for the latest version and subsidiary modules for lower versions, with a table to track each train's and RBC's version compatibility, allowing for independent migration and seamless communication across different version levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the current ETCS system version management strategy is applied, then all trains must be upgraded before the RBC can be upgraded to a new version, but this leads to delays in deploying up-to-date systems and requires extensive agreements between infrastructure owners and operators

Engineering Contradiction:
Improvesystem compatibilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The RBC is divided into multiple version-specific modules (e.g., module 26 for version N+1, modules 27 and 28 for versions N and lower). Each module handles communication with trains of corresponding versions independently, allowing the RBC to support multiple ETCS versions simultaneously without requiring all trains to be upgraded at once.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The RBC is designed with multi-version capability, where a single RBC unit can communicate with trains running different ETCS versions (N, N+1, etc.). The connection module 22 automatically detects the train's version and routes communication to the appropriate module, making the RBC universal across version differences.

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

2Reliability

If the current ETCS system version management strategy is applied, then extensive agreements between infrastructure owners and train operators are required, but this increases system complexity and slows down deployment

Engineering Contradiction:
Improveversion compatibilityVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The connection module 22 automatically performs version detection and module selection without human intervention. When a train connects, the system autonomously identifies the train's ETCS version and routes it to the appropriate RBC module, eliminating the need for manual coordination agreements between operators and infrastructure owners.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback from the train's version identification (detected by the connection module 22) to automatically adjust the communication routing. This closed-loop approach ensures the correct module handles each train based on its version, reducing coordination complexity while maintaining compatibility.

Inventive Principle:
Principle #23Feedback

3Reliability

If the RBC waits for all trains to be upgraded before upgrading to a new version, then the latest ETCS version can be deployed, but this requires the entire fleet to be upgraded simultaneously which is impractical

Engineering Contradiction:
Improvesystem interoperabilityVSAvoidupgrade speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The RBC dynamically adapts its behavior based on the version of each connecting train. The connection module 22 continuously monitors incoming trains, detects their versions, and automatically switches between different internal modules (26, 27, 28) to maintain compatibility. This dynamic adaptation allows gradual fleet upgrading without requiring simultaneous upgrades.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The RBC is pre-configured with multiple version modules before deployment. This preliminary preparation allows the RBC to immediately handle trains of different versions as they connect, eliminating the need to wait for fleet-wide upgrades before deploying new ETCS versions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2993106B1ERTMS / ETCS radio block centre; method for establishing a connection with said radio block centre
Publication Date: 2018.03.07 ALSTOM TRANSPORT TECH SAS
  • EP2993106B1 patent drawingFigure 1~2
  • EP2993106B1 patent drawingFigure 3

AI summary

Radio Block Centre according to the ERTMS / ETCS standard, for train supervision along an area of a railway, comprising a radio communication module and a means for train supervision, characterised in that, said means for train supervision being a primary means for the supervision of trains according to a first version of the ETCS standard, the Radio Block Centre (20, 30) further comprise a secondary means for the supervision of trains according to a second version of the ETCS standard, and a connection module capable of detecting the ETCS system version of an On Board Unit (10) of a train (3) trying to connect to the Radio Block Centre, based on a table associating to an ETCS identifier of said On Board Unit, a list comprising at least one ETCS system version said On Board Unit supports, and establishing a communication session for the supervision of said train according to the detected ETCS system version.