Operational description:
1. The TCC receives a request to establish a safe connection set-up with a traction unit.
2. The TCC sends back the system version used.
3. Having checked if the system version is compatible with the on board system, the on board
sends the “session established report” to the TCC, including its unique ETCS identification,
train running number and an “invalid” position report referring to the last relevant balise group
stored on board.
4. The TCC checks its information stored.
5. The TCC detects the ETCS identification with position data.
6. The TCC checks if the train running number is available in the database for operation.
7. The TCC can find the number in the data base for operation.
8. The TCC checks if there has been another registration for that train running number at the
same time.
9. The TCC cannot find a timetable conflict for that train running number.
10. The TCC registers the train running number.
11. The TCC reports to the controller requiring a confirmation for the position of that traction unit.
12. The controller confirms the position to the TCC
13. The TCC confirms the position to the on board.
14. The TCC indicates the traction unit with the train running number on the controller’s screen.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Example Operational Scenarios etcs_lc_scenarios.pdf | application/pdf | 1.11 MB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
This document is meant to support the understanding of the requirements for the ERTMS REGIONAL
FRS. The functions of the system are described step by step to express clearly how
the system is expected to work from an operational point of view.