ATO over ETCS

ATO-OB / ATO-TS FFFIS

Application Layer

REF : SUBSET – 126

ISSUE : 0.0.20
DATE : 17-01-2021

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 1/40
1. MODIFICATION HISTORY
Issue Number
Section Number Modification / Description Author
Date
0.0.1
All First issue of the document UNISIG ATO WP
07-01-2014
Document updated after UNISIG
0.0.2 ATO WG comments and review
All UNISIG ATO WP
08-04-2014 meetings (11-12/02/2014 and 11-
12/03/2014).
0.0.3 Document updated after UNISIG
All UNISIG ATO WP
30-04-2014 ATO WG comments.
Document updated after UNISIG
0.0.4 ATO WG comments to version
All UNISIG ATO WP
06-05-2014 0.0.3 and call conference of
05/05/2014.
Document updated after EUG
0.0.5
All review and SUBSET-125-006 and UNISIG ATO WP
05-09-2014 007 discussions and update.
Document updated after UNISIG
ATO WG review. All the
0.0.6
All requirements and explanation UNISIG ATO WP
29-09-2014 have been deleted from the
document.
The document content has been
updated according to the EUG
0.0.7
All and ERA comments to version UNISIG ATO WP
13-05-2015 0.0.5 and the SUBSET-125
update to version 0.0.10.

0.0.8 Minor changes according to

Table 7, Table 8,
UNISIG ATO WG Workshops of UNISIG ATO WP
07-01-2016 Table 9
May, June and July 2015.
0.0.9 Document updated after UNISIG
All UNISIG ATO WP
11-04-2016 ATO WG review.
0.0.10 5.1, 6.3.3, 6.3.4, Document updated after UNISIG
UNISIG ATO WP
19-07-2016 6.3.5 ATO WG review.
0.0.11 5.1, 5.2, 6.3.3.2, Document updated after UNISIG
UNISIG ATO WP
25-08-2016 6.3.4.2, 6.3.5.2 ATO WG review.

0.0.12 Modification according to UNISIG

All UNISIG ATO WP
27-04-2017 SG, EUG and ATO WG review.

0.0.13 Modification according to ATO

All UNISIG ATO WP
19-05-2017 WG review.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 2/40
 0.0.14 draft A Modification to align with
All UNISIG ATO WP
15-12-2017 SUBSET-125-0017 draftC.

0.0.14 Modification to align with

7.2.1.2, 7.3.6 UNISIG ATO WP
22-12-2017 SUBSET-125-0017.

Modification following ATO-WP

review on version 0.0.14 and
0.0.15 alignment with SUBSET-125-
7.2.1.2, 7.3.8.2 0018. Change of N_ITER UNISIG ATO WP
16-03-2018 Description and Resolution /
Formula. Minor spelling
corrections.
Modification to align with
0.0.16 SUBSET-125-010 and SUBSET-
All UNISIG ATO WP
07-05-2018 130-010. Offsets replaced by Item
Number.
Review comments and following
S2R comments against Subset-
126 solved: 1, 2, 6, 7, 8, 9, 10, 12,
13, 14, 16, 19, 22, 23, 25, 26, 27,
0.0.17 28, 29, 30, 31, 32, 33, 34, 35, 36,
All 37, 38, 45, 50, 54, 55, 57, 58, 59, UNISIG ATO WP
05.08.2020 64, 66, 67, 68, 71, 72, 74, 76, 77,
79, 80, 82, 83, 84, 85, 86, 87, 88,
89, 91, 92, 93, 94, 98, 100, 101,
103, 104, 105, 106, 107, 108,
109, 110, 111
Following S2R comments solved:
114, 115, 137
0.0.18 Following EECT comments
All UNISIG ATO WP
22.10.2020 solved: 1, 2, 3, 4, 9, 12, 13, 14,
15, 16, 20, 23, 24, 25, 26, 29, 32,
36, 37
0.0.19 Following EECT comments
All UNISIG ATO WP
02.11.2020 solved: 5, 6, 7

0.0.20 Following EECT comments

All UNISIG ATO WP
17.01.2021 solved: 10

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 3/40
2. TABLE OF CONTENTS
1. MODIFICATION HISTORY .................................................................................................................. 2
2. TABLE OF CONTENTS ...................................................................................................................... 4
3. TABLE OF FIGURES .......................................................................................................................... 6
4. LIST OF TABLES ............................................................................................................................... 7
5. INTRODUCTION ................................................................................................................................ 8
5.1. Scope and purpose of the document ....................................................................................... 8
5.2. Reference and applicable documents ..................................................................................... 8
5.3. Abbreviations ............................................................................................................................ 9
5.4. Definitions ................................................................................................................................. 9
6. PRINCIPLES ................................................................................................................................... 10
6.1. Introduction ............................................................................................................................. 10
6.2. Definition of the Variables ...................................................................................................... 10
6.3. Definition of the Packets ........................................................................................................ 11
7. DETAILED DESCRIPTION OF THE APPLICATION LEVEL ..................................................................... 12
7.1. List of Packets ........................................................................................................................ 12
7.2. ATO Header ........................................................................................................................... 12
7.3. ATO Packets Applicable Content........................................................................................... 13
7.3.1. Introduction ................................................................................................................................... 13
7.3.2. Handshake Request Packet (HSReq) .......................................................................................... 13
7.3.3. Handshake Acknowledgement Packet (HSAck) .......................................................................... 14
7.3.4. Handshake Reject Packet (HSRej) .............................................................................................. 14
7.3.5. Journey Profile Request Packet (JPReq) ..................................................................................... 15
7.3.6. Journey Profile Packet (JP) .......................................................................................................... 15
7.3.7. Journey Profile Acknowledgement Packet (JPAck) ..................................................................... 20
7.3.8. Segment Profile Request Packet (SPReq)................................................................................... 20

7.3.9. Segment Profile Packet (SP) ........................................................................................................ 21

7.3.10. Status Report Packet (STR) ......................................................................................................... 36
7.3.11. Status Report Acknowledgement Packet (STRAck) .................................................................... 38
7.3.12. Session Termination Request Packet (SESSTermReq) .............................................................. 38

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 4/40
 7.3.13. Session Termination Packet (SESSTerm) ................................................................................... 38

APPENDIX ............................................................................................................................................ 40
A.1. Example Encoded Handshake Request Packet .................................................................... 40
A.1.1. The following example shows the encoding of a Handshake Request Packet............................ 40

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 5/40
3. TABLE OF FIGURES

Figure 1 Encoded Handshake Request Packet ................................................................................ 40

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 6/40
4. LIST OF TABLES
Table 1 Reference and applicable documents .................................................................................... 8
Table 2 Packet summary ................................................................................................................... 12
Table 3 ATO Header structure ........................................................................................................... 13
Table 4 Handshake Request Packet structure .................................................................................. 14
Table 5 Handshake Acknowledgement Packet structure ................................................................. 14
Table 6 Handshake Reject Packet structure ..................................................................................... 15
Table 7 Journey Profile Request Packet structure ............................................................................ 15
Table 8 Journey Profile Packet structure........................................................................................... 19
Table 9 Journey Profile Acknowledgement Packet structure ............................................................ 20
Table 10 Segment Profile Request Packet structure ........................................................................ 21
Table 11 Segment Profile Packet structure ....................................................................................... 33
Table 12: Type Classification for Segment Profile Data.................................................................... 34
Table 13 Status Report Packet structure........................................................................................... 37
Table 14 Status Report Acknowledgement Packet structure ............................................................ 38
Table 15 Session Termination Request Packet structure ................................................................. 38
Table 16 Session Termination Packet structure................................................................................ 39

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 7/40
5. INTRODUCTION
5.1. Scope and purpose of the document

5.1.1.1. The purpose of this System Interface Description document is to present the
interoperable interface between the two subsystems of the Automatic Train Operation (ATO)
system, namely the ATO trackside (ATO-TS) and the ATO on-board (ATO-OB). The scope of the
document is to define the interoperable packets exchanged between the on-board subsystem
(ATO-OB) and the trackside subsystem (ATO-TS) according to the ATO over ETCS System
Requirements Specification [Ref 1].

5.1.1.2. This document does not contain the communication requirements associated to the
ATO-OB / ATO-TS Interface. These requirements are included in [Ref 1] §10.1.

5.1.1.3. Specific ATO Packets are defined in this document with a unique packet identification
number.

5.2. Reference and applicable documents

5.2.1.1. This section presents the reference and applicable documents.

Ref. N° Title Reference Author

[Ref 1] ATO over ETCS System

SUBSET-125 UNISIG
Requirements Specification
ERA, UNISIG,
[Ref 2] System Requirements Specification SUBSET-026 EEIG ERTMS
Users Group
EEIG ERTMS
[Ref 3] ATO over ETCS Glossary 13E154
Users Group
[Ref 4] FFFIS STM Application Layer SUBSET-058 UNISIG
ERA, UNISIG,
Glossary of Terms and
[Ref 5] SUBSET-023 EEIG ERTMS
Abbreviations
Users Group
ERA, UNISIG,
[Ref 6] FIS Juridical Recording SUBSET-027 EEIG ERTMS
Users Group
ATO-OB / TCMS Interface
[Ref 7] SUBSET-139 UNISIG
Specification FIS + FFFIS

Table 1 Reference and applicable documents

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 8/40
5.3. Abbreviations

5.3.1.1. For ATO related abbreviations see ATO over ETCS Glossary [Ref 3].

5.3.1.2. For ETCS related abbreviations see SUBSET-023 [Ref 5].

5.4. Definitions

5.4.1.1. For ATO related definitions see ATO over ETCS Glossary [Ref 3].

5.4.1.2. For ETCS related definitions see SUBSET-023 [Ref 5].

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 9/40
6. PRINCIPLES

6.1. Introduction

6.1.1.1. The composition of each packet element is presented using a class diagram and a
table detailing each variable in order.

6.1.1.2. Inside the class diagrams the declaration of the variables including their types
(“T_<xxx>”) can be seen and should not be confused with the time/date prefix of variable names.

6.2. Definition of the Variables

6.2.1.1. Variables are used to encode single data values. Variables cannot be split in minor
units.

6.2.1.2. Variables may have special values which are related to the basic meaning of the
variable.

6.2.1.3. Special values which are not spare, have always the highest values in a variable (e.g.
32767 = “unknown”).

6.2.1.4. Spare values are located between the normal and special values in the variable range
except where justified.

6.2.1.5. Names of variables are unique with respect to their meaning. A variable is used in
context with the meaning as described in the variable definition. Variables with different meanings
have different names.

6.2.1.6. One bit variables (Boolean) always use 0 for false and 1 for true.

6.2.1.7. Offsets for numerical values are avoided (0 is used for 0, 1 for 1, etc.) except where
justified.

6.2.1.8. Encoding of variables shall start with the most significant bit. See example in Appendix
A.1.

6.2.1.9. The encoding order shall respect the order of variables listed in the packet format (from
top to bottom).

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 10/40
6.3. Definition of the Packets

6.3.1.1. Packets are multiple variables grouped into a single unit, with a defined internal
structure.

6.3.1.2. Optional variables inside a packet are marked with constraints. Only if the constraint is
evaluated to true the variable and possible nested variables will follow in the packet. Otherwise the
packet will continue with the next variable without constraint or with a constraint evaluated to true.

6.3.1.3. An ATO Packet consists of:

• A specific ATO Header. This header is generated by the subsystem (ATO-OB or

ATO-TS) that sends the packet;
• The Applicable Content itself.

6.3.1.4. Any packet exchanged between ATO-OB and ATO-TS shall add the needed quantity of
bits in order to be byte aligned.

6.3.1.4.1. Note: Thus, the maximum number of potentially added bits is 7 bits.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 11/40
7. DETAILED DESCRIPTION OF THE APPLICATION LEVEL

7.1. List of Packets

7.1.1.1. This section details the application level of the interface.

Packet Number
Packet Name Source Sink Page N°
(NID_PACKET_ATO)

0 Handshake Request ATO-OB ATO-TS 13

1 Handshake Acknowledgement ATO-TS ATO-OB 14

2 Handshake Reject ATO-TS ATO-OB 14

3 Journey Profile Request ATO-OB ATO-TS 15

4 Journey Profile ATO-TS ATO-OB 15

5 Journey Profile Acknowledgement ATO-OB ATO-TS 20

6 Segment Profile Request ATO-OB ATO-TS 20

7 Segment Profile ATO-TS ATO-OB 21

8 Status Report ATO-OB ATO-TS 36

9 Status Report Acknowledgement ATO-TS ATO-OB 38

10 Session Termination Request ATO-TS ATO-OB 38

11 Session Termination ATO-OB ATO-TS 38

Table 2 Packet summary

7.2. ATO Header

7.2.1.1. This section details the ATO specific header of a packet exchanged between the ATO-
OB and the ATO-TS.

7.2.1.2. The information in the header allows each packet to be uniquely identified.

7.2.1.3. ATO Header composition:

ATO Header

Item Variable Name Description Length Resolution/Formula

001 NID_PACKET_ATO Packet number, used in the header for each 8 bits Numbers
packet, allowing the receiving equipment to Special Values:
identify the data which follows.
12 - 255 = spare

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 12/40
 ATO Header

Item Variable Name Description Length Resolution/Formula

002 NID_OPERATIONAL See [Ref 2], Section 7.5.1.92. 32 bits See [Ref 2], Section 7.5.1.92.

003 NID_ENGINE See [Ref 2], Section 7.5.1.88. 24 bits See [Ref 2], Section 7.5.1.88.

004 T_Timestamp_Date Date of timestamp of the packet. 15 bits Date of a timestamp in UTC.
The variable represents the
number of days from the 1st
January 2010.
Values from 0 (01/01/2010) to
32767 (18/09/2099)

005 T_Timestamp_Seconds Seconds of timestamp of the packet in UTC. 17 bits Seconds of a timestamp in
UTC. The variable represents
the number of seconds from the
beginning of the day.
Values from 0 (00:00:00) to
86399 (23:59:59)

006 N_Packet_Counter Packet counter sent from the sending 8 bits Binary to numeric
subsystem. This value is a circulating
counter. In case of an overflow the value
might jump from the maximum value to the
minimum value. The value is maintained by
the sender for each NID_PACKET_ATO
separately during the entire session.

Table 3 ATO Header structure

7.3. ATO Packets Applicable Content

7.3.1. Introduction

7.3.1.1. This section defines the actual ATO information contained in the packet.

7.3.2. Handshake Request Packet (HSReq)

7.3.2.1. This section details the structure of a HSReq Packet sent by ATO-OB to ATO-TS.

7.3.2.2. Handshake Request composition:

Packet Number 0

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Handshake Details

002 N_ITER_ATO Number of iterations of ATO-OB supported 5 bits Binary to numeric

versions.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 13/40
 Packet Number 0

Item Variable Name Description Length Resolution/Formula

003 M_ATO_Version (k) ATO system version supported. 16 bits 1st byte for the major Version
2nd byte for the minor Version
Applicable values:
0x0100 = ATO version 1.0

Table 4 Handshake Request Packet structure

7.3.3. Handshake Acknowledgement Packet (HSAck)

7.3.3.1. This section details the structure of the HSAck Packet sent by ATO-TS to ATO-OB.

7.3.3.2. Handshake Acknowledgement composition:

Packet Number 1

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Handshake Acknowledgement Details

002 NID_C Identity of the ATO-TS’s country or region. 10 bits See [Ref 2], Section 7.5.1.86.

003 NID_ATOTS Identifier of the ATO-TS. 14 bits Binary to numeric

004 M_ATO_Version ATO system version to be used. 16 bits 1st byte for the major Version
2nd byte for the minor Version
Applicable values:
0x0100 = ATO version 1.0

005 T_Timeout_ATOTS_Respon Minimum time the ATO-OB shall wait before 8 bits Binary to numeric (in seconds)
se repeating a request if there was no
Response.

006 T_Reporting_Time Reporting time cycle for triggering a Status 8 bits Binary to numeric (in seconds)
Report for data reporting purposes.

Table 5 Handshake Acknowledgement Packet structure

7.3.4. Handshake Reject Packet (HSRej)

7.3.4.1. This section details the structure of the HSRej Packet sent by ATO-TS to ATO-OB.

7.3.4.2. Handshake Reject composition:

Packet Number 2

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Handshake Reject Details

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 14/40
 Packet Number 2

Item Variable Name Description Length Resolution/Formula

002 Q_Reject_Reason Qualifier indicating the reason for the 2 bits 0 = ATO system version
rejection. incompatible

1 = Another ATO-TS in charge

2 = ATO-TS in charge unknown

3 = Spare

ATO-TS Contact Information - If [ Q_Reject_Reason == Another ATO-TS in charge ]

003 NID_C If [ Q_Reject_Reason == Another ATO-TS 10 bits See [Ref 2], Section 7.5.1.86.
in charge ]
Identity of the ATO-TS’s country or region.

004 NID_ATOTS If [ Q_Reject_Reason == Another ATO-TS 14 bits Binary to numeric

in charge ]
Identifier of the ATO-TS.

Table 6 Handshake Reject Packet structure

7.3.5. Journey Profile Request Packet (JPReq)

7.3.5.1. This section details the structure of a JPReq Packet sent by the ATO-OB to the ATO-
TS.

7.3.5.2. Journey Profile Request Packet composition:

Packet Number 3

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Journey Profile Request Details

002 NID_C Identity of the reference SP’s country or 10 bits See [Ref 2], Section 7.5.1.86.
region. Not relevant if NID_SP is undefined.

003 NID_SP Identity of the Segment Profile from which a 32 bits Binary to numeric
Journey Profile is requested. 4294967295 for undefined
value.

Table 7 Journey Profile Request Packet structure

7.3.6. Journey Profile Packet (JP)

7.3.6.1. The section details the structure of a JP Packet sent by the ATO-TS to the ATO-OB.

7.3.6.2. Journey Profile Packet composition:

Packet Number 4

Item Variable Name Description Length Resolution/Formula

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 15/40
 Packet Number 4

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Journey Profile Details

002 Q_JP_Status Status of the Journey Profile: 3 bits 0 = Invalid

'Valid': JP containing the data requested. 1 = Valid

'Unavailable': JP specifies that the requested 2 = Unavailable
part of the Journey Profile is currently not
available yet (but all the previously sent JPs 3 = Update
are still applicable). 4 = Overwrite
'Invalid': JP specifies that the SP identifier
[5-7] = Spare
asserted in the JPReq does not belong to
the preceding JP already sent to the ATO-
OB.
'Update': JP specifies that the Journey
Profile has been updated by the TMS within
the current visibility of the ATO-OB.
'Overwrite': JP specifies that the previously
sent JPs shall be completely overwritten by
this data.

Segment Profile Reference - If [ Q_JP_Status <> Invalid and Q_JP_Status <> Unavailable ]

003 N_ITER_SP If [ Q_JP_Status <> Invalid and 8 bits Binary to numeric

Q_JP_Status <> Unavailable ]
Number of iterations of SPs. If N_ITER_SP
is 0 then no data set is following.

004 NID_C (k) Identity of the SP’s country or region. 10 bits See [Ref 2], Section 7.5.1.86.

005 NID_SP (k) SP identity. 32 bits Binary to numeric

006 M_SP_Version (k) Identifier of the segment profile version. See 16 bits 1 byte for the major version and
section Segment Profile Packet (SP). 1 byte for the minor one.

007 Q_SP_DIR (k) Qualifier to indicate the valid travelling 1 bits 0 = Reverse
direction of the SP. 1 = Nominal

Timing Point Constraints

008 N_ITER_ATO (k) Number of iterations of TPs information. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

009 NID_TP (k,l) TP identity. The NID_TP is unique within the 32 bits Binary to numeric.
NID_C of the Segment Profile.

010 T_Latest_Arrival_ Date of the requested arrival time at the TP. 15 bits Date of a timestamp in UTC.
Date (k,l) The variable represents the
number of days from the 1st
January 2010.
Values from 0 (01/01/2010) to
32767 (18/09/2099)

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 16/40
 Packet Number 4

Item Variable Name Description Length Resolution/Formula

011 T_Latest_Arrival_ Seconds of the requested arrival time at the 17 bits Seconds of a timestamp in
Seconds (k,l) TP. UTC. The variable represents
the number of seconds from the
beginning of the day.
Values from 0 (00:00:00) to
86399 (23:59:59)

012 T_Arrival_Window Acceptable time allowance to be earlier at 10 bits Binary to numeric (in seconds).
(k,l) the TP. The value is 0 for Stopping
Points.

013 Q_TP_Alignment This qualifier defines if the TP location is 2 bits 0 = Front

(k,l) applicable from the front, middle or rear of 1 = Middle
the train.
2 = Rear

3 = Spare

014 Q_Stop_Skip_Pas Specifies if the Timing Point is a Passing 2 bits 0 = Stopping Point
s (k,l) Point, an operational Stopping Point or a 1 = Stopping Point to be
skipped Stopping Point. skipped (with symbol shown to
driver)

2 = Passing Point

3 = Spare

015 Q_TP_Information Specifies some information specific for the 2 bits 0 = No specific information
(k,l) TP. 1 = End of Journey

[2-3] = Spare

016 Q_Day_Light_Savi This variable defines if the day light saving 1 bits 0 = No saving hour
ng (k,l) hour is applicable to calculate the local time. 1 = Saving hour

Stopping Point Information - If [ Q_Stop_Skip_Pass == Stopping Point ]

017 Q_Opening_Door If [ Q_Stop_Skip_Pass == Stopping Point 2 bits 00 = none
_Side (k,l) ] 01 = right
Specifies if the ATO-OB has to manage the
10 = left
train doors opening and on which side the
passenger exchange doors have to be 11 = both
opened. The side is relative to the direction
of the Journey Profile.

018 Q_Centralised_Op If [ Q_Stop_Skip_Pass == Stopping Point 1 bits 0 = Opening by passengers

ening (k,l) ] 1 = Centralised automatic
This variable defines if the doors are to be opening of the relevant doors
opened centralised or by the passengers.

Stopping Point Departure Details - If [ Q_Stop_Skip_Pass == Stopping Point and Q_TP_Information <> End of
Journey ]
019 Q_Train_Hold (k,l) If [ Q_Stop_Skip_Pass == Stopping Point 1 bits 0 = Do not hold Train
and Q_TP_Information <> End of Journey 1 = Hold train
]
The variable defines if the train is requested
to be held at the Stopping Point or not.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 17/40
 Packet Number 4

Item Variable Name Description Length Resolution/Formula

020 T_Departure_Date If [ Q_Stop_Skip_Pass == Stopping Point 15 bits Date of a timestamp in UTC.

(k,l) and Q_TP_Information <> End of Journey The variable represents the
and Q_Train_Hold <> Hold train ] number of days from the 1st
Date of the expected departure time from the January 2010.
Stopping Point. Values from 0 (01/01/2010) to
32767 (18/09/2099)

021 T_Departure_Sec If [ Q_Stop_Skip_Pass == Stopping Point 17 bits Seconds of a timestamp in

onds (k,l) and Q_TP_Information <> End of Journey UTC. The variable represents
and Q_Train_Hold <> Hold train ] the number of seconds from the
Seconds of the expected departure time beginning of the day.
from the Stopping Point. Values from 0 (00:00:00) to
86399 (23:59:59)

022 T_Minimum_Dwell If [ Q_Stop_Skip_Pass == Stopping Point 10 bits Binary to numeric (in seconds)
_Time (k,l) and Q_TP_Information <> End of Journey
and Q_Train_Hold <> Hold train ]
Minimum dwell time at given Stopping Point
(in seconds).

023 Q_Automatic_Clos If [ Q_Stop_Skip_Pass == Stopping Point 1 bits 0 = ATO-OB does not manage
ing (k,l) and Q_TP_Information <> End of Journey train doors closing
and Q_Train_Hold <> Hold train ] 1 = ATO-OB manages train
This variable defines if the ATO-OB has to doors closing
manage the train doors Closing.

Temporary Constraints

024 N_ITER_ATO (k) Number of iterations of Temporary 5 bits Binary to numeric

Constraints. If N_ITER is 0 then no data set
is following.

025 Q_TC_Type (k,l) Type of the temporary constraint. 3 bits 0 = ASR

1 = Low Adhesion

2 = ATO Inhibition Zone

3 = DAS Inhibition Zone

4 = Current Limitation

[5-7] = Spare

026 Q_Range (k,l) Specifies if the temporary constraint starts, 2 bits 0 = Starts
ends, starts and ends or covers the whole 1 = Ends
concerning Segment Profile.
2 = StartsEnds

3 = WholeSP

027 D_TC_Start_Locat If [ Q_TC_Range == Starts or 24 bits Binary to numeric (in

ion (k,l) Q_TC_Range == StartsEnds ] centimetres)
Start location of the temporary constraint
relatively to the beginning of the SP.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 18/40
 Packet Number 4

Item Variable Name Description Length Resolution/Formula

028 D_TC_End_Locati If [ Q_TC_Range == Ends or Q_TC_Range 24 bits Binary to numeric (in

on (k,l) == StartsEnds ] centimetres)
End location of the temporary constraint
relatively to the beginning of the SP.

Additional Speed Restriction - If [ Q_TC_Type == ASR ]

029 Q_FRONT (k,l) If [ Q_TC_Type == ASR ] 1 bits see [Ref 2], Section 7.5.1.109
see [Ref 2], Section 7.5.1.109

030 V_Speed_Level If [ Q_TC_Type == ASR ] 7 bits [0..120] x 5 km/h <=> [0..600]

(k,l) Value of the speed level restriction. The km/h;
variable used is comparable to V_STATIC, [121-127] = Spare
as defined in [Ref 2], Section 7.5.1.171,
hence only the first 120 values provided by
the 7 bits are used to determine that speed
Level.

Low Adhesion - If [ Q_TC_Type == Low Adhesion ]

031 Q_Adhesion_Cate If [ Q_TC_Type == Low Adhesion ] 3 bits 0 = Dry Rail
gory (k,l) Adhesion category aligned with the definition 1 = Medium
in EN15595 of the wheel-rail interface for the
2 = Normal Low
lower boundaries.
Dry Rail: Conditions where 100% of the 3 = Low Adhesion
brake force of the vehicle can be applied 4 = Very Low Adhesion
with no axle sliding of more than
2% (adhesion level typically above 0.15µ) 5 = Extremely Low Adhesion
Medium: Conditions where the wheel/rail [6-7] = Spare
adhesion is in the range 0.15 – 0.10 (Damp
rails with some contamination)
Normal Low: Conditions where the
wheel/rail adhesion is in the range 0.10 –
0.08 (Typical autumn mornings due to
dew/dampness often combined with light
overnight rust)
Low Adhesion: Conditions where the
wheel/rail adhesion is in the range 0.08 –
0.05
Very Low Adhesion: Conditions where the
wheel/rail adhesion is in the range 0.05-0.03
Extremely Low Adhesion: Conditions
where the wheel/rail adhesion is below 0.03

Current Limitation - If [ Q_TC_Type == Current Limitation ]

032 M_CURRENT (k,l) If [ Q_TC_Type == Current Limitation ] 10 bits See [Ref 2], Section 7.5.1.62.1
See [Ref 2], Section 7.5.1.62.1
Note: a powerless section is indicated as a
current limit “0” (zero)

Table 8 Journey Profile Packet structure

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 19/40
7.3.6.3. If the status of the JP is invalid or unavailable, the Journey Profile Details shall finish
after Q_JP_Status (Item 002).

7.3.6.4. Temporary Constraints

7.3.6.4.1. The location dependent data type of the Temporary Constraints is ATO Area Type. The
requirements as given in chapter 7.3.9.4 shall be applied.

7.3.6.4.2. For each type of constraint, the Temporary Constraints in a Journey Profile shall be
listed in the order given by their starting location in the Segment Profile.

7.3.7. Journey Profile Acknowledgement Packet (JPAck)

7.3.7.1. This section details the structure of a Journey Profile Acknowledgement Packet sent by
the ATO-OB to the ATO-TS in response to an updated/overwritten Journey Profile Packet.

7.3.7.2. Journey Profile Acknowledgement Packet composition:

Packet Number 5

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Journey Profile Acknowledgement Details

002 T_JP_Reference_Timestam Date of the timestamp of the Journey Profile 15 bits Date of a timestamp in UTC.
p_Date Packet (see 7.2 ATO Header) for which the The variable represents the
acknowledgement is provided. number of days from the 1st
January 2010.
Values from 0 (01/01/2010) to
32767 (18/09/2099)

003 T_JP_Reference_Timestam Seconds of the timestamp of the Journey 17 bits Seconds of a timestamp in
p_Seconds Profile Packet in UTC (see 7.2 ATO Header) UTC. The variable represents
for which the acknowledgement is provided. the number of seconds from the
beginning of the day.
Values from 0 (00:00:00) to
86399 (23:59:59)

004 N_JP_Reference_Packet_C N_Packet_Counter of the Journey Profile 8 bits Binary to numeric

ounter Packet (see 7.2 ATO Header) for which the
acknowledgement is provided.

Table 9 Journey Profile Acknowledgement Packet structure

7.3.8. Segment Profile Request Packet (SPReq)

7.3.8.1. The section details the structure of a SPReq Packet sent by the ATO-OB to the ATO-
TS.

7.3.8.2. Segment Profile Request Packet composition:

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 20/40
 Packet Number 6

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Segment Profile Request Details

002 N_ITER_ATO Number of iterations of SPs requested. The 5 bits Binary to numeric
minimum value for the variable in this packet
is 1.

003 NID_C (k) Identity of the SP's country or region. 10 bits See [Ref 2], Section 7.5.1.86.

004 NID_SP (k) Identity of the requested Segment Profile. 32 bits Binary to numeric

Table 10 Segment Profile Request Packet structure

7.3.9. Segment Profile Packet (SP)

7.3.9.1. This section details the structure of a Segment Profile Packet sent by the ATO-TS to
the ATO-OB.

7.3.9.2. Segment Profile Packet composition:

Packet Number 7

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Segment Profile Status

002 N_ITER_ATO Number of iterations of SPs in the packet. 5 bits Binary to numeric

003 NID_C (k) Identity of the SP's country or region. 10 bits See [Ref 2], Section 7.5.1.86.

004 NID_SP (k) SP identity. 32 bits Binary to numeric

005 Q_SP_Status (k) Status of the Segment Profile: 1 bits 0 = Invalid

"Valid": SP requested. 1 = Valid

"Invalid": SP not found in ATO-TS database.

Segment Profile Details - If [ Q_SP_Status <> Invalid ]

006 M_SP_Version (k) If [ Q_SP_Status <> Invalid ] 16 bits 1 byte for the major version and
Identifier of the segment profile version. 1 byte for the minor one.

007 L_SP (k) If [ Q_SP_Status <> Invalid ] 24 bits Binary to numeric (in
Length of the segment of railway covered by centimetres)
the SP. Minimum Value: 1

008 D_EoA_Offset (k) If [ Q_SP_Status <> Invalid ] 24 bits Binary to numeric (in
Distance to stop the train before an EoA. centimetres)

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 21/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

009 Q_UTC_Offset (k) If [ Q_SP_Status <> Invalid ] 7 bits Binary to numeric

Offset to add to the UTC time in order to Unsigned value
calculate the local time. Resolution: 15 min
0 = UTC - 14:00
56 = UTC ± 0
112 = UTC + 14:00
113 - 127 = Spare

010 M_SP_Altitude (k) If [ Q_SP_Status <> Invalid ] 20 bits Binary to numeric (in
Altitude at the beginning of the SP. centimetres) starting at -1000m
Considering ETRS89 as reference.

011 Q_ATOTS_Contact_Inf If [ Q_SP_Status <> Invalid ] 2 bits 0 = No Contact info follows

o_Dir (k) Qualifier indicating whether contact 1 = ATO-TS contact info for
information of another ATO-TS valid for nominal direction follows
nominal travelling direction of the SP, valid
2 = ATO-TS contact info for
for reverse travelling direction of the SP or
reverse direction follows
no contact information follows.
3 = Spare

ATO-TS Contact Information - If [ Q_ATOTS_Contact_Info_Dir == ATO-TS contact info for nominal direction
follows or Q_ATOTS_Contact_Info_Dir == ATO-TS contact info for reverse direction follows ]

012 NID_C_ATOTS (k) If [ Q_ATOTS_Contact_Info_Dir == ATO- 10 bits See [Ref 2], Section 7.5.1.86.
TS contact info for nominal direction
follows or Q_ATOTS_Contact_Info_Dir ==
ATO-TS contact info for reverse direction
follows ]
Identity of the ATO-TS’s country or region.

013 NID_ATOTS (k) If [ Q_ATOTS_Contact_Info_Dir == ATO- 14 bits Binary to numeric

TS contact info for nominal direction
follows or Q_ATOTS_Contact_Info_Dir ==
ATO-TS contact info for reverse direction
follows ]
Identifier of the adjacent ATO-TS.

014 NID_C (k) If [ Q_ATOTS_Contact_Info_Dir == ATO- 10 bits See [Ref 2], Section 7.5.1.86.
TS contact info for nominal direction
follows or Q_ATOTS_Contact_Info_Dir ==
ATO-TS contact info for reverse direction
follows ]
Identity of the SP’s country or region.

015 NID_SP (k) If [ Q_ATOTS_Contact_Info_Dir == ATO- 32 bits Binary to numeric

TS contact info for nominal direction
follows or Q_ATOTS_Contact_Info_Dir ==
ATO-TS contact info for reverse direction
follows ]
SP identity of the first segment in the
adjacent ATO-TS area.

Static Speed Profile Start

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 22/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

016 V_STATIC (k) Basic Static Speed Profile speed at the 7 bits [0..120] x 5 km/h <=> [0..600]
beginning of the Segment Profile. The km/h;
variable used is comparable to V_STATIC, [121-127] = Spare
as defined in [Ref 2], Section 7.5.1.171.

017 Q_FRONT (k) see [Ref 2], Section 7.5.1.109 1 bits see [Ref 2], Section 7.5.1.109
This is applicable only for step up.

Specific SSP

018 N_ITER_ATO (k) Number of iterations of Specific Static Speed 5 bits Binary to numeric
Profiles. If N_ITER is 0 then no data set is
following.

019 Q_DIFF (k,l) See [Ref 2], Section 7.5.1.102.1. 2 bits See [Ref 2], Section
7.5.1.102.1.

Cant Deficiency - If [ Q_DIFF == Cant Deficiency specific category ]

020 NC_CDDIFF (k,l) If [ Q_DIFF == Cant Deficiency specific 4 bits See [Ref 2], Section 7.5.1.82.1
category ]
See [Ref 2], Section 7.5.1.82.1

Other Specific SSP - If [ Q_DIFF == Other specific category, replaces the Cant Deficiency SSP or Q_DIFF ==
Other specific category, does not replace the Cant Deficiency SSP ]

021 NC_DIFF (k,l) If [ Q_DIFF == Other specific category, 4 bits See [Ref 2], Section 7.5.1.83.
replaces the Cant Deficiency SSP or
Q_DIFF == Other specific category, does
not replace the Cant Deficiency SSP ]
See [Ref 2], Section 7.5.1.83.

022 V_DIFF (k,l) See [Ref 2], Section 7.5.1.156 7 bits See [Ref 2], Section 7.5.1.156

Static Speed Profile Change

023 N_ITER_ATO (k) Number of iterations of Static Speed Profiles 5 bits Binary to numeric
changes. If N_ITER is 0 then no data set is
following.

024 D_Location (k,l) Location of the Static Speed Profile change 24 bits Binary to numeric (in
relatively to the beginning of the SP. centimetres)

025 V_STATIC (k,l) Basic Static Speed Profile speed. The 7 bits [0..120] x 5 km/h <=> [0..600]
variable used is comparable to V_STATIC, km/h;
as defined in [Ref 2], Section 7.5.1.171. [121-127] = Spare

026 Q_FRONT (k,l) see [Ref 2], Section 7.5.1.109 1 bits see [Ref 2], Section 7.5.1.109
This is applicable only for step up.

Specific SSP Change

027 N_ITER_ATO (k,l) Number of iterations of Specific Static Speed 5 bits Binary to numeric
Profiles. If N_ITER is 0 then no data set is
following.

028 Q_DIFF (k,l,m) See [Ref 2], Section 7.5.1.102.1. 2 bits See [Ref 2], Section
7.5.1.102.1.

Cant Deficiency Change - If [ Q_DIFF == Cant Deficiency specific category ]

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 23/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

029 NC_CDDIFF If [ Q_DIFF == Cant Deficiency specific 4 bits See [Ref 2], Section 7.5.1.82.1
(k,l,m) category ]
See [Ref 2], Section 7.5.1.82.1

Other Specific SSP Change - If [ Q_DIFF == Other specific category, replaces the Cant Deficiency SSP or Q_DIFF
== Other specific category, does not replace the Cant Deficiency SSP ]

030 NC_DIFF If [ Q_DIFF == Other specific category, 4 bits See [Ref 2], Section 7.5.1.83.
(k,l,m) replaces the Cant Deficiency SSP or
Q_DIFF == Other specific category, does
not replace the Cant Deficiency SSP ]
See [Ref 2], Section 7.5.1.83.

031 V_DIFF (k,l,m) See [Ref 2], Section 7.5.1.156 7 bits See [Ref 2], Section 7.5.1.156

Gradient Start
032 G_New_Gradient (k) Value of the new gradient at the beginning of 10 bits Binary to numeric (0-1023) with
the Segment Profile. The variable used is resolution 0.1‰
comparable to G_A, as defined in [Ref 2],
Section 7.4.2.6.

033 Q_GDIR (k) see [Ref 2], Section 7.5.1.110 1 bits see [Ref 2], Section 7.5.1.110

Gradients Change

034 N_ITER_ATO (k) Number of iterations of gradient changes. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

035 D_Location (k,l) Location of the gradient change relatively to 24 bits Binary to numeric (in
the beginning of the SP. centimetres)

036 G_New_Gradient Value of the new gradient. The variable used 10 bits Binary to numeric (0-1023) with
(k,l) is comparable to G_A, as defined in [Ref 2], resolution 0.1‰
Section 7.4.2.6.

037 Q_GDIR (k,l) see [Ref 2], Section 7.5.1.110 1 bits see [Ref 2], Section 7.5.1.110

Curve Start

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 24/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

038 Q_Radius_Category Curve category at the beginning of the 5 bits 0 = R>7000m

(k) Segment Profile. 1 = 7000m≥R>4500m

2 = 4500m≥R>2800m

3 = 2800m≥R>2000m

4 = 2000m≥R>1500m

5 = 1500m≥R>1250m

6 = 1250m≥R>1075m

7 = 1075m≥R>925m

8 = 925m≥R>825m

9 = 825m≥R>725m

10 = 725m≥R>625m

11 = 625m≥R>525m

12 = 525m≥R>475m

13 = 475m≥R>425m

14 = 425m≥R>375m

15 = 375m≥R>325m

16 = 325m≥R>300m

17 = 300m≥R>275m

18 = 275m≥R>250m

19 = 250m≥R>225m

20 = 225m≥R>200m

21 = 200m≥R>175m

22 = 175≥R>150m

23 = = R≤150m

[24-31] = Spare

Curves Change

039 N_ITER_ATO (k) Number of iterations of curve changes. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

040 D_Location (k,l) Location of the curve change relatively to the 24 bits Binary to numeric (in
beginning of the SP. centimetres)

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 25/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

041 Q_Radius_Catego Curve category. 5 bits 0 = R>7000m

ry (k,l) 1 = 7000m≥R>4500m

2 = 4500m≥R>2800m

3 = 2800m≥R>2000m

4 = 2000m≥R>1500m

5 = 1500m≥R>1250m

6 = 1250m≥R>1075m

7 = 1075m≥R>925m

8 = 925m≥R>825m

9 = 825m≥R>725m

10 = 725m≥R>625m

11 = 625m≥R>525m

12 = 525m≥R>475m

13 = 475m≥R>425m

14 = 425m≥R>375m

15 = 375m≥R>325m

16 = 325m≥R>300m

17 = 300m≥R>275m

18 = 275m≥R>250m

19 = 250m≥R>225m

20 = 225m≥R>200m

21 = 200m≥R>175m

22 = 175≥R>150m

23 = = R≤150m

[24-31] = Spare

Power Voltage Start

042 M_VOLTAGE (k) See [Ref 2], Section 7.5.1.78 4 bits See [Ref 2], Section 7.5.1.78

043 NID_CTRACTION (k) If [ M_VOLTAGE <> Line not fitted with 10 bits See [Ref 2], Section 7.5.1.86.1
any traction system ]
See [Ref 2], Section 7.5.1.86.1

Power Voltage Change

044 N_ITER_ATO (k) Number of iterations of voltage changes. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

045 D_Location (k,l) Location of the voltage change relatively to 24 bits Binary to numeric (in
the beginning of the SP centimetres)

046 M_VOLTAGE (k,l) See [Ref 2], Section 7.5.1.78 4 bits See [Ref 2], Section 7.5.1.78

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 26/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

047 NID_CTRACTION If [ M_VOLTAGE <> Line not fitted with 10 bits See [Ref 2], Section 7.5.1.86.1
(k,l) any traction system ]
See [Ref 2], Section 7.5.1.86.1

Current Limitation Start

048 M_CURRENT (k) See [Ref 2], Section 7.5.1.62.1 10 bits See [Ref 2], Section 7.5.1.62.1
Note: a powerless section is indicated as a
current limit “0” (zero)

Current Limitation Change

049 N_ITER_ATO (k) Number of iterations of allowed current 5 bits Binary to numeric
consumption changes. If N_ITER is 0 then
no data set is following.

050 D_Location (k,l) Location of the allowed current consumption 24 bits Binary to numeric (in
change relatively to the beginning of the SP centimetres)

051 M_CURRENT (k,l) See [Ref 2], Section 7.5.1.62.1 10 bits See [Ref 2], Section 7.5.1.62.1
Note: a powerless section is indicated as a
current limit “0” (zero)

Balise Group

052 N_ITER_ATO (k) Number of iterations of balise groups. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

053 Q_NEWNID_C Qualifier to indicate if NID_C of this balise 1 bits 0 = Use NID_C of SP
(k,l) group is following or the NID_C of the SP is 1 = NID_C to be used follows
valid for this balise group.

054 NID_C (k,l) If [ T_Q_NEWNID_C == NID_C to be used 10 bits See [Ref 2], Section 7.5.1.86.
follows ]
Identity of the BG's country or region.

055 NID_BG (k,l) See [Ref 2], Section 7.5.1.85. 14 bits See [Ref 2], Section 7.5.1.85.

Balises
056 N_TOTAL (k,l) See [Ref 2], Section 7.5.1.82. 3 bits See [Ref 2], Section 7.5.1.82.

057 N_PIG (k,l,m) See [Ref 2], Section 7, 5.1.81 3 bits See [Ref 2], Section 7, 5.1.81

058 D_Location Location of the balise relatively to the 24 bits Binary to numeric (in
(k,l,m) beginning of the SP. centimetres)

Timing Points

059 N_ITER_ATO (k) Number of iterations of Timing Points. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

060 NID_TP (k,l) TP identity. The NID_TP is unique within a 32 bits Binary to numeric.
NID_C.

061 D_Location (k,l) Location of the Timing Point relatively to the 24 bits Binary to numeric (in
beginning of the SP. centimetres)

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 27/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

062 Q_Stop_Location_ Required stopping tolerance to use when the 5 bits 0 = 10cm
Tolerance (k,l) TP is a Stopping Point. 1 = 20cm

2 = 30cm

3 = 40cm

4 = 50cm

5 = 1m

6 = 1,5m

7 = 2m

8 = 2,5m

9 = 3m

10 = 5m

11 = 7,5m

12 = 10m

13 = 15m

14 = 20m

15 = 25m

16 = 30m

17 = 50m

18 = 75m

19 = 100m

[20-30] = Spare

31 = No requirement

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 28/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

063 Q_STP_Reached Distance from a Stopping Point to consider it 24 bits 0 = 10cm

(k,l) as reached. 1 = 20cm

2 = 30cm

3 = 40cm

4 = 50cm

5 = 1m

6 = 1,5m

7 = 2m

8 = 2,5m

9 = 3m

10 = 5m

11 = 7,5m

12 = 10m

13 = 15m

14 = 20m

15 = 25m

16 = 30m

17 = 50m

18 = 75m

19 = 100m

[20-30] = Spare

31 = No requirement

Timing Point Name

064 L_TEXT (k,l) See [Ref 4], Section 8.1.11. 8 bits See [Ref 4], Section 8.1.11.

065 X_TEXT Name of the TP. 8 bits See [Ref 4], Section 8.1.120.
(k,l,m)

Platform Area
066 N_ITER_ATO (k) Number of iterations of Platform Areas. If 5 bits Binary to numeric
N_ITER is 0 then no data set is following.

067 Q_Range (k,l) Specifies if the Platform Area starts, ends, 2 bits 0 = Starts
starts and ends or covers the whole 1 = Ends
concerning Segment Profile
2 = StartsEnds

3 = WholeSP

068 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the platform start relatively to the
beginning of the SP.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 29/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

069 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the platform end relatively to the
beginning of the SP.

Tunnel
070 N_ITER_ATO (k) Number of iterations of tunnels. If N_ITER is 5 bits Binary to numeric
0 then no data set is following.

071 Q_Range (k,l) Specifies if the Tunnel starts, ends, starts 2 bits 0 = Starts
and ends or covers the whole concerning 1 = Ends
Segment Profile.
2 = StartsEnds

3 = WholeSP

072 Q_Tunnel_Catego Category of the Tunnel. 2 bits 0 = Single track tunnel

ry (k,l) 1 = Double track tunnel

2 = Wide-cross section tunnel

3 = Spare

073 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the tunnel start relatively to the
beginning of the SP.

074 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the tunnel end relatively to the
beginning of the SP.

Axle Load Speed Profile

075 N_ITER_ATO (k) Number of iterations of Axle Load Speed 5 bits Binary to numeric
Profiles. If N_ITER is 0 then no data set is
following.

076 Q_Range (k,l) Specifies if the Axle Load Speed Profile 2 bits 0 = Starts
starts, ends, starts and ends or covers the 1 = Ends
whole concerning Segment Profile.
2 = StartsEnds

3 = WholeSP

077 M_AXLELOADCA See [Ref 2], Section 7.5.1.62 7 bits See [Ref 2], Section 7.5.1.62
T (k,l)

078 V_New_Speed_Le Speed restriction to be applied if the axle 7 bits [0..120] x 5 km/h <=> [0..600]
vel (k,l) load of the train ≥ M_AXLELOADCAT (k,v) km/h;
[121-127] = Spare

079 Q_FRONT (k,l) see [Ref 2], Section 7.5.1.109 1 bits see [Ref 2], Section 7.5.1.109
This is applicable only for step up.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 30/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

080 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Axle Load Speed Profile start
relatively to the beginning of the SP.

081 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Axle Load Speed Profile end
relatively to the beginning of the SP.

Unprotected Level Crossing Stop

082 N_ITER_ATO (k) Number of iterations of stopping locations for 5 bits Binary to numeric
unprotected level crossings. If N_ITER is 0
then no data set is following.

083 D_UnprotectedLx_ Location of the stop in rear of an 24 bits Binary to numeric (in
Stop_Nominal (k,l) unprotected level crossing if the centimetres)
valid travelling direction of the SP is nominal. 16777215 = Undefined Location
Undefined if for this travelling direction the
location is not inside this SP.

084 D_UnprotectedLx_ Location of the stop in rear of an 24 bits Binary to numeric (in
Stop_Reverse (k,l) unprotected level crossing if the centimetres)
valid travelling direction of the SP is reverse. 16777215 = Undefined Location
Undefined if for this travelling direction the
location is not inside this SP.

Permitted Braking Distance

085 N_ITER_ATO (k) Number of iterations of Permitted Braking 5 bits Binary to numeric
Distance areas. If N_ITER is 0 then no data
set is following.

086 Q_Range (k,l) Specifies if the Permitted Braking Distance 2 bits 0 = Starts
area starts, ends, starts and ends or covers 1 = Ends
the whole concerning Segment Profile.
2 = StartsEnds

3 = WholeSP

087 D_Permitted_Braki Permitted Braking Distance value. 24 bits Binary to numeric (in
ng_Distance (k,l) centimetres)

088 Q_PBD_SBEB Whether the permitted braking distance is to 1 bits 0 = Service Brake
(k,l) be achieved with the Service Brake or 1 = Emergency Brake
Emergency Brake.

089 G_PBD (k,l) A single gradient value applicable for the 8 bits Binary to numeric (0-255) with
calculation resolution 1‰

090 Q_GDIR_PBD (k,l) Direction of the gradient. 1 bits 0 = Downhill

1 = Uphill

091 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Permitted Braking Distance
area start relatively to the beginning of the
SP.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 31/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

092 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Permitted Braking Distance
area end relatively to the beginning of the
SP.

Switch Off Regenerative Brake

093 N_ITER_ATO (k) Number of iterations of Switch off 5 bits Binary to numeric
Regenerative Brake areas. If N_ITER is 0
then no data set is following.

094 Q_Range (k,l) Specifies if the Switch off Regenerative 2 bits 0 = Starts
Brake area starts, ends, starts and ends or 1 = Ends
covers the whole concerning Segment
Profile. 2 = StartsEnds

3 = WholeSP

095 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off Regenerative
Brake area start relatively to the beginning of
the SP.

096 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off Regenerative
Brake area end relatively to the beginning of
the SP.

Switch Off Eddy Current Brake

097 N_ITER_ATO (k) Number of iterations of Switch off eddy 5 bits Binary to numeric
current brake for service brake areas. If
N_ITER is 0 then no data set is following.

098 Q_Range (k,l) Specifies if the Switch off eddy current brake 2 bits 0 = Starts
for service brake area starts, ends, starts 1 = Ends
and ends or covers the whole concerning
Segment Profile. 2 = StartsEnds

3 = WholeSP

099 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off eddy current brake
for service brake area start relatively to the
beginning of the SP.

100 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off eddy current brake
for service brake area end relatively to the
beginning of the SP.

Switch Off Eddy Current Emergency Brake

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 32/40
 Packet Number 7

Item Variable Name Description Length Resolution/Formula

101 N_ITER_ATO (k) Number of iterations of Switch off eddy 5 bits Binary to numeric
current brake for emergency brake areas. If
N_ITER is 0 then no data set is following.

102 Q_Range (k,l) Specifies if the Switch off eddy current brake 2 bits 0 = Starts
for emergency brake area starts, ends, starts 1 = Ends
and ends or covers the whole concerning
Segment Profile. 2 = StartsEnds

3 = WholeSP

103 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off eddy current brake
for emergency brake area start relatively to
the beginning of the SP.

104 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off eddy current brake
for emergency brake area end relatively to
the beginning of the SP.

Switch Off Magnetic Shoe Brake

105 N_ITER_ATO (k) Number of iterations of Switch off Magnetic 5 bits Binary to numeric
Shoe Brake areas. If N_ITER is 0 then no
data set is following.

106 Q_Range (k,l) Specifies if the Switch off Magnetic Shoe 2 bits 0 = Starts
Brake area starts, ends, starts and ends or 1 = Ends
covers the whole concerning Segment
Profile. 2 = StartsEnds

3 = WholeSP

107 D_Start_Location If [ Q_Range == Starts or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off Magnetic Shoe
Brake area start relatively to the beginning of
the SP.

108 D_End_Location If [ Q_Range == Ends or Q_Range == 24 bits Binary to numeric (in

(k,l) StartsEnds ] centimetres)
Location of the Switch off Magnetic Shoe
Brake area end relatively to the beginning of
the SP.

Table 11 Segment Profile Packet structure

7.3.9.3. If the status of the Segment Profile is invalid, the Segment Profile Details shall finish
after Q_SP_Status (Item 5).

7.3.9.4. Segment Profile Location Dependent Data Types

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 33/40
7.3.9.4.1. All location dependent data types of a Segment Profile can be clustered into the
following categories, which are explained in the consecutive chapters:

• ATO Position Types

• ATO Profile Types
• ATO Area Types

7.3.9.4.2. Table 14 assigns the category to the location dependent ATO data types.

Location Dependent Data ATO Type

Static Speed Profile Profile

Gradients Profile

Curves Profile

Power Voltage Profile

Current Limitation Profile

Balises Position

Timing Points Position

Platform Areas Area

Tunnels Area

Axle Load Speed Profiles Area

Unprotected LX Position

Permitted Braking Distances Area

Switch off regenerative brake areas Area

Switch off eddy current brake for SB Area

Switch off eddy current brake for EB Area

Switch off magnetic shoe brake Area

Table 12: Type Classification for Segment Profile Data

7.3.9.5. ATO Position Types

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 34/40
7.3.9.5.1. ATO Position Type elements are described by a distance relative to a reference point
only and do not have any extension. Consequently, the location dependent data assigned to the
Segment Profile is applicable at this position only.

7.3.9.5.2. At a specific position, only one element of the same position type shall be specified.

7.3.9.5.3. The data shall be sorted in ascending order of position.

7.3.9.6. ATO Profile Types

7.3.9.6.1. An ATO Profile Type always starts at the Segment Profile’s start point and is applicable
till (excluding) the next discontinuity given in the profile, if any.

7.3.9.6.2. For each ATO Profile Type, the element at the Segment Profile’s origin shall be given.

7.3.9.6.3. The position of any discontinuity shall not be located at the Segment Profile’s start
point. Discontinuities are optional.

7.3.9.6.4. At a specific position, only one element of the same ATO Profile Type shall be
specified.

7.3.9.6.5. The data shall be sorted in ascending order of position.

7.3.9.7. ATO Area Types

7.3.9.7.1. An ATO Area Type is defined by its start and end location and can cover multiple
Segment Profiles. Only in case the area extremities are located within this particular Segment
Profile they shall be given in this Segment Profile.

7.3.9.7.2. Data belonging to the same type/category (if applicable, e.g. M_AXLELOADCAT) shall
be sorted in ascending order of their start offset and shall neither overlap nor be nested.

7.3.9.7.3. If the start offset is not given, it is assumed as zero.

7.3.9.7.4. The end offset, if given, shall be unequal to the start offset of this particular type.

7.3.9.8. Speed values

7.3.9.8.1. If at the same position multiple speed values of different categories/types (beside the
static speed profile) are defined, they shall be sorted according to their category criterion. The
sorting depends on the category/type:

a) NC_CDDIFF: Ascending
b) NC_DIFF: Ascending
c) M_AXLELOADCAT: Ascending

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 35/40
7.3.10. Status Report Packet (STR)

7.3.10.1. The section details the structure of a Status Report Packet sent by the ATO-OB to the
ATO-TS.

7.3.10.2. Status Report Packet composition:

Packet Number 8

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Status Report Details

002 M_ATO_State The current ATO State in use. 4 bits 0 = Unknown

1 = CO

2 = NA

3 = AV

4 = RE

5 = EG

6 = DE

7 = FA

[8-15] = Spare

003 Q_STR_Indicators Bitset with the indicators state. 16 bits bit0 = JP SP Consistency Error

bit1 = Routing Error

bit2 = Next Stopping Point Skip

bit3 = Low adhesion reported by

the driver

bit4 = Operational conditions

fulfilment

bit5 = Train is moving

bit6 = Unable to stop at the next

Stopping Point

[bit7-bit15] = Spare

004 M_Adhesion_Factor See [Ref 7], Section 6.2.7.1 'Available 8 bits See [Ref 7], Section 7.3.3
adhesion factor'. 'M_TCMS_AvaAdh'

005 V_TRAIN_ATO Current speed of the train when the STR is 10 bits Binary to numeric.
sent. Resolution: 1 km/h

006 L_TRAIN See [Ref 2], Section 7.5.1.56. 12 bits See [Ref 2], Section 7.5.1.56.

007 DRIVER_ID See [Ref 6], Section 4.2.3.7. 128 bits See [Ref 6], Section 4.2.3.7.

STR Sending Location

008 NID_C Identity of the SP's country or region. Not 10 bits See [Ref 2], Section 7.5.1.86.
relevant if D_Sending_Position = Undefined
Location.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 36/40
 Packet Number 8

Item Variable Name Description Length Resolution/Formula

009 NID_SP SP identity. Not relevant if 32 bits Binary to numeric

D_Sending_Position = Undefined Location.

010 D_Sending_Position Position of the estimated front end of the 24 bits Binary to numeric (in
train at the moment the STR is sent centimetres)
(relatively from the beginning of the given 16777215 = Undefined Location
SP).

Previous TP Information

011 NID_C Identity of the previous TP's country or 10 bits See [Ref 2], Section 7.5.1.86.
region. Not relevant if NID_TP is undefined.

012 NID_TP Previous TP identity. The NID_TP is unique 32 bits Binary to numeric.
within a NID_C. 4294967295 for undefined
value.

013 Q_Pass_Stop_Depart Qualifier to indicate if train has stopped at 2 bits 0 = Train passed the TP
the TP, has departed from the TP or has 1 = Train stopped at the TP
passed the TP.
2 = Train departed from the TP

3 = Undefined

Accurate Stopping - If [ Q_Pass_Stop_Depart == Train stopped at the TP ]

014 Q_Accurate_Stopping If [ Q_Pass_Stop_Depart == Train 2 bits 0 = Undershoot

stopped at the TP ] 1 = Accurate
This qualifier specifies if the train has
2 = Overshoot
stopped accurately or not at the Operational
Stopping Point. 3 = Spare

Timing Point Estimation

015 N_ITER_ATO Number of iterations of TPs information. If 5 bits Binary to numeric

N_ITER is 0 then no data set is following.

016 NID_C (k) Identifier of the next TP's country or region. 10 bits See [Ref 2], Section 7.5.1.86.

017 NID_TP (k) Next TP identity. The NID_TP is unique 32 bits Binary to numeric.
within a NID_C.

018 T_Arrival_Date (k) Date to arrive at the TP. 15 bits Date of a timestamp in UTC.
The variable represents the
number of days from the 1st
January 2010.
Values from 0 (01/01/2010) to
32767 (18/09/2099)

019 T_Arrival_Seconds (k) Estimated time in seconds to arrive at the 17 bits Seconds of a timestamp in
TP. UTC. The variable represents
the number of seconds from the
beginning of the day.
Values from 0 (00:00:00) to
86399 (23:59:59)

Table 13 Status Report Packet structure

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 37/40
7.3.11. Status Report Acknowledgement Packet (STRAck)

7.3.11.1. The section details the structure of a Status Report Acknowledgement Packet sent by
the ATO-TS to the ATO-OB.

7.3.11.2. Status Report Acknowledgement Packet composition:

Packet Number 9

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Status Report Acknowledgement Details

002 T_STR_Reference_Timesta Date of the timestamp of the Status Report 15 bits Date of a timestamp in UTC.
mp_Date Packet (see 7.2 ATO Header) for which the The variable represents the
acknowledgement is provided. number of days from the 1st
January 2010.
Values from 0 (01/01/2010) to
32767 (18/09/2099)

003 T_STR_Reference_Timesta Seconds of the timestamp of the Status 17 bits Seconds of a timestamp in
mp_Seconds Report Packet in UTC (see 7.2 ATO Header) UTC. The variable represents
for which the acknowledgement is provided. the number of seconds from the
beginning of the day.
Values from 0 (00:00:00) to
86399 (23:59:59)

004 N_STR_Reference_Packet_ N_Packet_Counter of the Status Report (see 8 bits Binary to numeric
Counter 7.2 ATO Header) for which the
acknowledgement is provided.

Table 14 Status Report Acknowledgement Packet structure

7.3.12. Session Termination Request Packet (SESSTermReq)

7.3.12.1. The section details the structure of a Session Termination Request Packet sent by the
ATO-TS to the ATO-OB.

7.3.12.2. Session Termination Request Packet composition:

Packet Number 10

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Table 15 Session Termination Request Packet structure

7.3.13. Session Termination Packet (SESSTerm)

7.3.13.1. The section details the structure of a Session Termination Packet sent by the ATO-OB
to the ATO-TS.

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 38/40
7.3.13.2. Session Termination Packet composition:

Packet Number 11

Item Variable Name Description Length Resolution/Formula

001 ATO Header see chapter 7.2 -

Session Termination Details

002 Q_Termination_Reason Qualifier indicating the reason for the 3 bits 0 = End of Journey reached
communication session termination. 1 = ATO-TS Termination
Request

2 = Last SP left

3 = Cab closed

4 = TRN or train length not valid

5 = ETCS-OB in NL

6 = ETCS-OB in SH

7 = Spare

Table 16 Session Termination Packet structure

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 39/40
APPENDIX

A.1. Example Encoded Handshake Request Packet

A.1.1. The following example shows the encoding of a Handshake Request Packet.

NID_PACKET_ATO = 0 NID_OPERATIONAL = 100210

0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 1 1 1 1 1 1 1

0x00 0x10 0x02 0x10 0xFF

NID_ENGINE = 8849999

1 0 0 0 0 1 1 1 0 0 0 0 1 0 1 0 0 1 0 0 1 1 1 1

0x87 0x0A 0x4F

T_Timestamp_Date = 2022-04-01 T_Timestamp_Seconds = 11:59:55

0 0 1 0 0 0 1 0 1 1 1 1 0 0 1 0 1 0 1 0 1 0 0 0 1 0 1 1 1 0 1 1

0x22 0xF2 0xA8 0xBB

N_Packet_Counter = 1 N_ITER_ATO = 1 M_ATO_Version = 1.0

0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0

0x01 0x08 0x08 0x00

Resulting encoded hex string:

0x00 0x10 0x02 0x10 0xFF 0x87 0x0A 0x4F 0x22 0xF2 0xA8 0xBB 0x01 0x08 0x08 0x00

Figure 1 Encoded Handshake Request Packet

The hex string for the Handshake Request Packet example is as follows:
• 0x00100210FF870A4F22F2A8BB01080800

© This document has been developed and released by UNISIG

SUBSET-126 - 0.0.20 ATO over ETCS – ATO-OB / ATO-TS FFFIS Application Layer Page 40/40