Draft Functions List

ERTMS Trackside Approval Learning Case

Issues Log (Main Level)

Applicant: demonstration of controlling issue - Agency: comments

No. Id. Issues Specific issue Initial question issue log Applicant: comments Issue Status
> reference to documentation. and conditions
Level transitions Transition point 1) If level transitions to level 0/NTC are planned to be implemented next to SH areas, could an on-board be tripped in SH mode and reach a level transition to level
0/NTC while in trip mode?
X 1.1.1
2) If the answer to 1) is yes, how do you manage the situation of the undefined B2 on-board behaviour ending up in UN/SN mode with no valid Train Data?

Level transitions Transition point 1) Do you plan to engineer a trackside subsystem with a transition from level NTC to level 1, 2 or 3 announced in such a way that it leads to the display of the level
transition acknowledgement less than 6 seconds before the start location of a Mode Profile is reached?

In case the answer to the question 1 is Yes:

X 1.1.2
2) How is a driver acknowledgment of the mode that would occur more than 5s after the train has entered the Mode Profile controlled and managed?

Level transitions Transition point If shunting movements in level 0/NTC are allowed next to an ETCS border area (i.e. transition from level 0/NTC to level 1/2/3), what will prevent the train from entering
X 1.1.5 into the ETCS area in Level 0/SH or Level NTC/SH?

Level transitions Transition point 1) Are the level transition announcements (i.e. not the immediate or conditional level transition order given by balise group at the border) planned to be sent by RBC?

2) If the answer to 1) is yes, does the location of the transition in the announcement match the location of the border balise group?

X 1.1.6 3) If the answer to 2) is no, how is it avoided that inconsistent level transition orders are received at the same time by the on-board?

Level transitions Transition point Is it planned to send a packet 90 together with an immediate LTO (or a conditional LTO) that causes a transition to level 2 or level 3?
X 1.1.7

Level transitions Transition point 1) Is it planned to send an SH mode profile for current location together with an immediate LTO (or a conditional LTO) that causes a transition to level 0 or NTC?

2) Is it planned that the trackside sent an SH mode profile for current location together with an immediate LTO (or a conditional LTO) that causes a transition from level
X 1.1.8
2/3 to level 1?

Level transitions Transition point 1) Which are the trackside engineering provisions to ensure that the Level 3 RBC (or the Level 2 RBC relying on train integrity confirmation) knows that the entire train
has crossed its exit border (due to level transition or RBC Handover)?
X 1.1.9 2) How is the communication session with the Level 3 RBC (or the Level 2 RBC relying on train integrity confirmation) terminated when the train exits the RBC area?

Level transitions Train in approach In the following scenario: Level transition with table of priority containing L3 (as highest priority) and LNTC,

1) Do you expect all trains being able to establish a communication session with the RBC to operate in L3, regardless whether they are fitted with a TIMS or not?

X 1.2.2
2) If the answer to 1) is yes, do you apply the mitigation stipulated in the Technical Opinion OPI-2020-2 - CR1353 and if not applied what is the alternative measure?

Level transitions Train in approach 1) Is the BG that is planned to send the first communication session establishment order when the train is approaching to Level 2/3 a BG marked as unlinked?
If the answer to the question 1 is yes,

2) Are there any engineering trackside provisions planned to be implemented to avoid that D_LRBG / L_DOUBTUNDER / L_DOUBTOVER and L_TRAININT exceed the limit
values?

3) On the concerned access tracks, are all the subsequently encountered balise groups, including the border balise group transmitting an immediate level transition
X 1.2.3
order, marked as unlinked?

If the answer to question 3 is yes:

4) Once the train has entered the level 2/3 area, can a subsequent SoM considered as being part of the normal service be performed while the train has not
encountered any balise groups marked as linked?

Level transitions Degraded situations In transitions from level NTC to ETCS level 2/3, are both the ETCS and the NTC trackside systems planned to provide coherent information regarding a stopping aspect
X 1.3.2 of the signal at the border?

Level transitions Infill information at What infill information is planned to be implemented in an area after there has been an announcement for the level transition and until it is executed?
the level transition If the answer to the question includes packet 66 and/or packet 44, please consider to issue 6.7.1
X 1.8.1

Level transitions Linking information 1) In the area from the level transition announcement and the level transition border, do both linking information from the current level and the one stored in the
at the level transition transition buffer include the same balise groups?

X 1.9.1 2) If the answer to the question 1 is no, what are the provisions taken to avoid that, in case the level transition occurs before the border BG is received, information
extracted from the transition buffer is relocated based on the estimated travelled distance between its reference BG and the current LRBG?

Level transitions Linking information 1) In a transition from an area where the linking is not used to a level 1, 2 or 3 area, does linking information stored in the transition buffer include all the balise groups
at the level transition marked as linked that are encountered by the train from the time the level transition announcement is received to the time the level transition is executed?

2) If the answer to the question 1 is no, what are the provisions taken to take into account that, in case the level transition occurs before the border BG is received, the
X 1.9.2
on-board has to use information extracted from the transition buffer referring to a BG whose distance to the current LRBG cannot be retrieved from linking
information?

Level transitions Conditional level 1) Is the Conditional Level Transition Order (packet 46) planned to be sent from balise group together with Level Transition Order (packet 41)?
transition
2) Is the Conditional Level Transition Order (packet 46) planned to be sent between announcement and execution of the Level Transition Order (packet 41)?
X 1.10.1

RBC handover Authorisation across 1) What are the provisions taken to take into account that, in case the on-board has sent a position report to the ACC RBC with the max safe front end having passed
the handover the announced border location (i.e. it considers the ACC RBC as the supervising one) but not referring to the border BG as LRBG (the border BG has been missed or
location the train has not yet passed the border BG with its antenna), the ACC RBC is able to interprete this position report such that it detects that it has become the
supervising RBC?
X 2.2.4
2) What are the provisions taken to cope with the case the ACC RBC does not receive the position report sent by the on-board with the max safe front end having
passed the announced border location (radio loss) such that it does not consider yet being the supervising RBC while the on-board does?

RBC handover Network registration 1) Are RBC handovers planned to be implemented together with a change of communication network?

2) In this case, how and at which location are they planned to be implemented?
X 2.6.1
3) If in a station, how is it planned to implement this, in order to ensure that the on-board is always able to connect to the RBC that controls the area where the vehicle
is going to circulate?

RBC handover Shunting protection Is it possible that the train operates in SH in the RBC handover area and crosses the RBC-RBC border in spite of the rule § 4.1.4.1 of the SUBSET-040 v2.0.0? ?
X 2.7.1 in RBC handover

RBC handover RBC handover For each RBC covering a border of the line:
Interface - Is subset 39 planned to be implemented?
- Is subset 98 planned to be implemented?
- If at least one of them is not implemented, detailed plans for implementation for the RBC handover should be provided.

X 2.8.1
Remark: Even In the case that currently there is no RBC Handover, please explain how the possible future interface with other RBCs is foreseen.

RBC handover RBC handover Which are the values agreed at project level for the ‘configuration management’ of the RBC handover defined in Subset 039 (See table 13 configuration items)?
X 2.8.2 Interface

RBC handover RBC handover What are the specific engineering provisions planned to be implemented to cover the degraded situation when the handover is performed by an on-board able to
Interface handle one communication session at a time?

X 2.8.5 In case there is no RBC Handover currently planned, please explain how the possible future interface with other RBCs is foreseen.

RBC handover RBC handover What are the engineering provisions planned to be implemented for the handover involving an RBC compliant with the Subset 039 v2.3.0 (B2) and a RBC compliant
Interface with a B3 Subset 039?
X 2.8.6
In case that there is no RBC Handover currently planned, please explain how the possible future interface with other RBCs is foreseen.

RBC handover Communication 1) Are packets 42 containing a communication session establishment order with the Accepting RBC planned to be implemented in the vicinity of the RBC/RBC border?
establishment
X 2.9.1 2) In this case, are such packets 42 sent together with the RBC transition order (packet 131)?

Braking curves Harmonised braking What are the provisions to take into account the fact that a train fitted with a B3 on-board or with a B2 on-board which implements the harmonised braking model will
model run with the default values?
X 3.1.4

Braking curves Harmonised braking How will the technical compatibility between the line and the trains fitted with a B2 on-board that does not implement the ERA_ERTMS_040022 be ensured?
X 3.1.5 model

Braking curves Harmonised braking In case it is planned to neither use the packet 71 nor the update of adhesion factor by driver to manage the operation under reduced adhesion conditions, do you rely
model on the pre-indication to help the driver to reduce him/herself the speed of the train?
In case the answer is yes: for B3R2 trains, do you require additional DMI information (TTI or target display in CSM) together with the mandatory planning info as a full
X 3.1.6 substitute of the pre-indication?

Authorising the First authorisation to How is the start of mission planned to be implemented in the line and in particular which are the checks implemented prior to the sending of the first authorisation to
X 4.1.2 vehicle to move run run?

Authorising the First authorisation to In the following scenario:

vehicle to move run • During a start of mission procedure in level 2/3,
• After the RBC sends an authorisation to run in Staff Responsible (SR) mode (message 2),
X 4.1.3 • An On Sight (OS) route is established before the driver acknowledges the SR mode

Are the RBCs designed to wait for the on-board to report the SR mode, before sending an OS movement authority?

Authorising the First authorisation to If during a start of mission the on-board sends the SoM position report with status “invalid”, is it planned that the RBC sends a train accepted message containing the
X 4.1.4 vehicle to move run LRBG ID set to "unknown"?

Authorising the First authorisation to Do you plan to engineer a level 1 to level 2/3 transition in such a way that the RBC does not send any MA before the on-board equipment has reported its position
vehicle to move run using the level transition border BG and with this border BG transmitting an MA possibly with a Mode Profile OS or SH for current location?
Assumption: the on-board equipment is in communication session with the RBC before reaching the level transition border.

X 4.1.6 If the answer to the question is yes:

in case the RBC does not know the route information from the border to the next signal, does it rely on the mode FS reported in the first position report referring to
the border BG to send the first FS MA to the train?

Authorising the Timers 1) How is it planned to manage the section timers, the end section timers and/or the overlap timers such that the issues depicted in the ETCS-H0012 are avoided?
vehicle to move
X 4.2.1 2) Is it planned to implement balise groups whose closest balise is installed less than 1.5 seconds times the line speed +1.3m before the start location of an end
section or an overlap timers?

Authorising the Timers In case the RBC sends a movement authority (MA) containing an overlap/end section timer (i.e. T_ENDTIMER≠ ∞ and/or T_OL ≠ ∞), will it be possible that it could be
vehicle to move repeated by the RBC after the on-board passes both the interlocking and the MA overlap/end section timer start location?
X 4.2.2

Authorising the Renewal of the Are there Movement Authorities (MA) planned to be implemented with an LOA speed higher than the maximum restricted speed profile for this location?
vehicle to move Movement Authority
If the answer to the question is yes:
X 4.3.1 For MAs not ending to the exit of the line or ending at the exit to a level 1 area without any level 1 MA available at the transition: what does trigger the renewal of the
MA if there is no MA request from the on-board to the RBC?

Authorising the Renewal of the How is a change in the train data planned to be managed by the L3 RBC (or the L2 RBC relying on train integrity confirmation) in case a train is split?
X 4.3.4 vehicle to move Movement Authority

Authorising the Renewal of the 1) Is the RBC expected to send Track Ahead Free requests (message 34) in On-Sight areas?
vehicle to move Movement Authority
X 4.3.5 2) If this is the case, does the RBC rely solely on the reception of a message 149 “Track Ahead Free Granted” from the on-board to extend the MA beyond the end of
the OS area? If not, which are the other alternatives planned?

Authorising the Release speed The harmonised braking curves indicates that the intervention arising from passing the EoA will not occur at that time if a balise group message is received in the
vehicle to move vicinity of the EoA. Intervention will be delayed until the BG message is processed.
X 4.5.1 Have appropriate measures been taken to compensate the wrong calculation of the OBU release speed not considering the delay in the brakes intervention?

Authorising the Release speed 1) How is it planned to calculate the value of the fixed release speed(s) sent by trackside and in particular what are the provisions taken to ensure a fair balance
vehicle to move between the risk of passing the Supervised location after the on-board has tripped the train on passing the EOA and the driving performance on approaching the EOA?

2) What are the assumptions made regarding the on-board processing times and the odometer accuracy?

3) Do the assumptions referred to in question 2 take into account the possible additional delay to command the emergency brake due to the processing of a balise
group message in the vicinity of the EOA?

X 4.5.2 4) For level 2/3 only: Does the fixed release speed rely on the following assumption: when passing over a relocation balise group installed in the vicinity of the EOA, any
on-board equipment trips the train as soon as it has processed the message from this balise group, because regardless of the raw odometer over-reading amount after
the reset of the train position confidence interval, the on-board should immediately consider that the min safe front end of the train has passed the EOA, taking into
account the balise location reference detection accuracy (1m) as stipulated in the Subset 036 clause 4.2.10.2 and the minimum distance between Eurobalise antenna
and train front (2m) as stipulated in the Subset 040?

Authorising the Release speed Is it planned that a level transition from Level 2/3 to Level 1, located in rear of the EOA derived from a Movement Authority delivered by the RBC could be executed
X 4.5.3 vehicle to move while the on-board is in Release Speed Monitoring?

Authorising the Release speed 1) Are there speed restrictions lower than the release speed in the vicinity of the release speed monitoring area:
vehicle to move • whose end is located at a distance, in rear of the presumed RSM start location (see Subset 026 clause 3.13.9.4.9), shorter than the foreseeable value of the train
position confidence interval (depending on the location of the LRBG and on Subset 041 clause 5.3.1.1) when the train front end reaches the presumed RSM start
location, AND
• which precedes another MRSP element with a higher speed?

2) If the answer to the question 1 is yes, how is managed the risk of a train accelerating too early (i.e. before the min safe rear end has reached the end of the speed
X 4.5.4 restriction) in a RSM area?
Note: it is assumed that at the concerned locations, the IM knows the MRSP that will be computed by the on-board (especially from the following information not
transmitted by the ETCS trackside: the train length, the maximum train speed and when relevant the STM max speed/STM system speed). It is also assumed that the IM
knows the presumed RSM start location (and the release speed value calculated on-board if relevant), which is deduced from the braking characteristics of the train by
applying the Subset 026 section 3.13.9.4.

Authorising the Protective Is it planned that the RBC triggers a restrictive reaction (e.g. the sending of an unconditional emergency stop) if it receives an unexpected/misleading combination of
vehicle to move programming level/mode in a position report (e.g. a position report with level 2/mode FS in a track section known to be travelled in OS)?
X 4.7.2

Authorising the Protective 1) Is it planned that the RBC monitors unexpected behaviour of the on-boards, even if they are not strictly against specific requirements included in the technical
vehicle to move programming specification for interoperability?

2) In this case, which are these additional protective programming mechanisms foreseen by the RBC?
X 4.7.3
3) Is it foreseen that the RBC monitors the sent Train positions reports with odometry confidence intervals exceeding the thresholds? Which is the expected reaction
that the RBC would perform in this situation?

Authorising the Emergency stops and Could a co-operative shortening of MA with a mode profile be sent while a Conditional Emergency Stop is applied (not yet revoked)? How is this situation managed?
X 4.8.3 vehicle to move shortening of
movement authority
Authorising the Emergency stops and Are conditional emergency stop messages planned to be sent as high priority data?
vehicle to move shortening of
movement authority If the answer to the question is yes:
X 4.8.4
Is there an expectation regarding the resetting (or the non-ressetting) of T_NVCONTACT upon reception of such message by the on-board, which if not followed by the
on-board would be problematic in terms of undue (or absence of) on-board reaction?

Authorising the Emergency stops and Are requests to shorten movement authority (message 9) planned to be sent while the on-board is supervising a movement authority with a mode profile?
vehicle to move shortening of
X 4.8.5 movement authority

Authorising the Emergency stops and 1) On approaching the level 2/3 area, is sending of emergency stops planned to be implemented while the on-board is not yet in level 2/3?
vehicle to move shortening of
movement authority If the answer to the question 1 is yes:
2) Does the RBC expect the reception of the emergency stop acknowledgement of use (message 147) as soon as it is received on-board?

X 4.8.6
If the answer to the question 2 is yes:
3) Which specific trackside functionality relies on such early reception?

Authorising the Emergency stops and Regarding the locations planned to be implemented as stop location for the conditional emergency stop (CES):
vehicle to move shortening of 1) Can it be located in advance of the supervised location (SvL) derived from the previously sent movement authority ?
movement authority 2) Can it be located between the end of authority (EOA) and the supervised location (SvL) derived from the previously sent movement authority?
3) Can it be located in advance of the LOA of the previously sent movement authority and in rear of a speed restriction lower than the LOA (i.e. a speed restriction
relevant for the on-board to calculate the safe supervision limits when approaching the LOA)?
4) Can it be located between the start location of a mode profile (or a route suitability location or the start location of a not protected level crossing (LX)) and the end
of the Movement Authority?

If the answer to the question 2 is yes:

5) What are the provisions taken to deal with the risk induced by the on-board keeping the SvL untouched, i.e. not shifting it at the CES stop location?
X 4.8.7
If the answer to the question 1, 2 or 3 is yes:
6) What are the provisions taken to ensure that, upon the reception of the first movement authority after the CES revocation, the on-board does not use obsolete (i.e.
information that has been previously received and is no longer valid) track description or other trackside information which is not part of the track description (e.g. not
yet applicable NVs, level transition announcement)?

Authorising the Emergency stops and If the conditional emergency stop is used to shorten an MA with release speed value, what are the provisions taken to prevent the on-board attaching the trackside
vehicle to move shortening of release speed given in that MA (i.e. not calculated on-board) to the CES stop location?
X 4.8.9 movement authority

Authorising the Reversing Have you considered the scenarios leading to the sending of Train Data by a B2 on-board, while the train is performing a reverse movement in RV mode?
X 4.9.1 vehicle to move

120 Rue Marc Lefrancq | BP 20392 | FR-59307 Valenciennes Cedex

Tel. +33 (0)327 09 65 00 | era.europa.eu
Page 1 of 3
 Draft Functions List
ERTMS Trackside Approval Learning Case

Authorising the NID_C How is it planned to enforce the National Values, including for engines that are moved cold to the line?
vehicle to move Which are, if any, the provisions taken to deal with the situation of the on-board of a leading engine using the default values when the first balise group after a Start of
X 4.10.1 Mission is crossed?

Authorising the NID_C 1) Is it planned to transmit a set of national values which is valid at a specific non-null distance?
vehicle to move If the answer to question 1 is yes:
X 4.10.2 2) What are the provisions taken to deal with the situations when an on-board equipment is switched-off after the reception of the National Values referred to in
question 1 and before the location defined by the validity distance is reached?

Authorising the NID_C Is it foreseen to send national values with no NID_C (Packet 3 with N_ITER = 0) to the on-boards ?
X 4.10.3 vehicle to move

Authorising the NID_C 1) Is it planned that balise groups not announced by linking but installed on the corresponding route contain a NID_C that is not included in the NID_C(s) of the
vehicle to move currently applicable set of National Values?

X 4.10.4 If the answer to question 1 is yes:

2) What are the provisions taken if upon reception of a balise group referred to in question 1, a B2 on-board uses the default National Values?

Authorising the Override At a signal with stopping aspect which has to be passed with the Override procedure:
vehicle to move 1 - is it planned that the main BG transmits the "Stop if in SR" packet together with the packet 12 with V_MAIN=0?
X 4.11.1 2 - Is it planned that the main BG transmitting a level transition order to level 1 and a packet 12 with V_MAIN=0 is not included in the list of balises in SR that was given
by the RBC?

Balises, linking and Repositioning How is the repositioning function planned to be implemented?
repositioning In particular, are there provisions to avoid that, once the current MA section is adjusted by repositioning information, the on-board considers that the MA has been
X 5.1.1
shortened?

Balises, linking and Repositioning Is it planned to engineer the limit between two MA sections in the area starting from the balise group announcing the repositioning and the main balise group?
repositioning In case the answer is yes, what are the provisions taken to ensure that the MA section whose length is adjusted by repositioning is the one expected by the trackside,
X 5.1.2 taking into account the on-board odometer inaccuracy?

Balises, linking and Relocation 1) Have you taken into consideration the fact that it is not specified at all how an on-board deals with trackside information referring to a balise group that is no longer
repositioning the current LRBG or that refers to a balise group marked as unlinked?
2) Have you engineered location based information sent from balise groups whose distance from/to other balise groups is not provided by linking?
X 5.2.1
3) If the answer to 2) is yes, have you taken provisions for the engineering of the distances counted from these balise groups?

Balises, linking and Relocation In case the distance between balise groups is not provided by linking (e.g. on tracks operated in LS mode), have you taken into consideration the relocation of location
X 5.2.2 repositioning based information (e.g. MA, SSP, gradient…) through the estimated travelled distance between these balise groups, as stipulated in the Subset 026 clauses 3.6.4.3 b)
and 3.6.4.7.2?

Balises, linking and Availability 1) Are duplicated balises within a balise group planned to be implemented?
X 5.3.1 repositioning
2) How is it managed in case information from the duplicated balises is lost?

Balises, linking and Virtual balise cover 1) Will VBC(s) be enabled before this ETCS installation is put into service?
repositioning
X 5.4.1 If the answer to the question 1 is yes:
2) How is the enforcement of the virtual balise cover planned to be managed?
3) How will the validity time of the virtual balise cover be determined?

Balises, linking and Virtual balise cover 1) Can a BG which is covered by a VBC be announced by linking (packet 5) with a Q_LINKREACTION set to 0 or 1?
repositioning
If the answer to the question 1 is yes:
X 5.4.5 2) Do you expect that a B3 on-board does not trigger the linking reaction of the packet 5 mentioned in the question 1 when it receives such balise group while the
corresponding VBC is set either by trackside through a packet 6 “Virtual Balise Cover order” or by the driver?

Balises, linking and Linking 1) Do you plan to engineer two balise groups announced consecutively by linking, both of them with a linking reaction set to "no reaction" and both of them
repositioning consisting of non-duplicated balises?

In case the answer ot the question 1 is yes:

X 5.5.2 2) In case the messages from the two balise groups referred to in question 1 are engineered so that they refer to the same trackside information (e.g. a TSR) and should
this information not being considered by the on-board (e.g. because at least one of the balises is out of order in each group), do you expect that the on-board
commands the service brake when "the end of the expectation window of the second balise group has been passed" as per Subset 026 clause 3.16.2.7.1.1.?

Balises, linking and Unlinked BG 1) Do you plan to engineer balise group(s) marked as unlinked that can be passed by trains which have not passed any balise group marked as linked since a Start of
repositioning Mission procedure was ended with the status of train position set to "unknown"?
In case the answer to question 1 is yes and if a subsequent Start of Mission can take place while this BG marked as unlinked is the last passed (i.e. while still no LRBG is
stored on-board):

X 5.6.1
2) If such SoM takes place with no ETCS on-board power off/on in between or with an ETCS on-board power off/on but without cold movement whose absence is
expected to be confirmed by a Cold Movement Detector, can the necessity for the driver to systematically re-validate the level during the SoM be considered as
preventing the normal service?

Balises, linking and Unlinked BG 1 - Do you plan to engineer balise group(s) marked as unlinked that can be passed by trains which have not passed any balise group marked as linked since a Start of
repositioning Mission procedure was ended with the status of train position set to "unknown"?
In case the answer to question 1 is yes and if a subsequent Start of Mission can take place while this BG marked as unlinked is the last passed (i.e. while still no LRBG is
stored on-board):
X 5.6.2 2 - Which are the trackside engineering provisions planned to be implemented to manage the situation where the RBC receives a SoM position report including the
variable Q_STATUS set to "Invalid" or "Valid" and a variable NID_LRBG not set to "Unknown" but whose value is not known to the RBC?

Balises, linking and Unlinked BG In the following scenario:

repositioning - The train encounters a balise group marked as unlinked which provides National Values applicable at a further distance.
- Before reaching the location where the NVs become applicable, EoM and subsequent SoM with no ETCS on-board power off/on in between or with an ETCS on-board
power off/on but without cold movement whose absence is expected to be confirmed by a Cold Movement Detector

X 5.6.3 What are the engineering provisions planned to be implemented for managing the situation where the train position vs. the BG marked as unlinked is deleted during
the new SoM and the on-board equipment does not apply the National Values when reaching the location given by the BG marked as unlinked?

Balises, linking and Unlinked BG 1) Do you plan to implement a level 1 area without any balise group marked as linked?
repositioning
X 5.6.4 If the answer to question 1 is yes,
2) Are there any engineering trackside provisions planned to be implemented to avoid that D_LRBG / L_DOUBTUNDER / L_DOUBTOVER and L_TRAININT exceed the limit
values?

Balises, linking and Balise location 1) Do you plan to engineer balise group(s) marked as linked (i.e. BG whose all telegrams include the variable Q_LINK = 1) installed with a tolerable accuracy different
repositioning accuracy from:
a) 12 m in case the line is operated with X=1?
b) Only for B3: The applicable Q_NVLOCACC in case the line is operated with X=2?
c) Only for B3: 12 m in case a neighbouring area is operated with X=1 and the 12m become applicable while the balise group is still LRBG?
d) A National Value Q_NVLOCACC from a neighbouring area, which becomes applicable while the balise group is still LRBG?

If the answer to any of the cases of question 1 is "yes":

2) In case the balise group installation accuracy is greater than the 12 m or a Q_NVLOCACC value referred to in question 1 (i.e. the inappropriate use by the on-board of
these 12 m or of such Q_NVLOCACC value for the LRBG would lead to an underestimation of the train position confidence interval), can this balise group:
• be the reference of a packet 5, which announces balise groups with Q_LINKREACTION = 2 (i.e. "No Reaction"), whose message includes safety related information, OR
X 5.7.1 • be the reference of location based information which is supervised with regards to the max safe front end?

3) In case the balise group installation accuracy is lower than the 12 m or a Q_NVLOCACC value referred to in question 1 (i.e. the inappropriate use by the on-board of
12 m or of such Q_NVLOCACC value for the LRBG would lead to an overestimation of the train position confidence interval), can this balise group be the reference of a
Movement Authority (i.e. the LRBG of the Movement Authority itself or the current LRBG after relocation of the MA information) without any further balise group
announced by linking located between this LRBG and the EOA/LOA?

Track description, text Level crossings How are level crossings (LX) planned to be implemented in ETCS?
messages and
X 6.1.1 temporary speed
restriction

Track description, text Level crossings In case a LX is actually unprotected and it has been previously announced by the RBC through the sending of a packet 88 with Q_LXSTATUS = 1 to the on-board, can
messages and the RBC repeat the unprotected LX information while the train has already passed the LX start location with its min safe front end but has not yet passed the LX end
X 6.1.2 temporary speed location with it min safe rear end for more than 300m?
restriction

Track description, text Track conditions 1) How is the change of traction system planned to be implemented?
messages and
X 6.3.1 temporary speed 2) Is the change of traction system planned to be implemented together with the lower pantograph track condition?
restriction

Track description, text Track conditions How are the track conditions planned to be implemented?
messages and
X 6.3.2 temporary speed
restriction

Track description, text Track conditions Does the planned route suitability information include provision for diesel trains?
messages and
X 6.3.3
temporary speed
restriction
Track description, text Train categories 1) Do you plan to engineer a packet 27 “International Static Speed Profile” with a combination of at least one specific SSP for trains belonging to a “cant deficiency”
messages and train category (i.e. NC_DIFF ≠ 9, 10 and 11) together with at least one specific SSP for trains belonging to a “non-cant deficiency” train category (i.e. NC_DIFF = 9, 10 or
temporary speed 11) on the same piece of track?
restriction
X 6.4.2 If the answer to the question 1 is yes:
2) For a same piece of track, can the (or one of the) specific SSP(s) for trains belonging to a “non-cant deficiency” train category (i.e. NC_DIFF = 9, 10 or 11) be less
restrictive than the (or any of the) specific SSP(s) for trains belonging to a “cant deficiency” train category (i.e. NC_DIFF ≠ 9, 10 and 11)?

Track description, text Temporary speed Do you plan to engineer trackside constituents transmitting a packet 65 with a revocable TSR whose ID is identical with the one referred to in a packet 66 (TSR
messages and restrictions revocation) sent in the same message?
X 6.5.1 temporary speed
restriction

Track description, text Temporary speed Do you plan to engineer trackside constituents transmitting more than one non-revocable TSR in the same message?
X 6.5.2 messages and restrictions
temporary speed
Track description, text Temporary speed Is a TSR revocation (i.e. packet 66) planned to be sent as infill information (i.e. after packet 136)?
messages and restrictions
X 6.5.3
temporary speed
restriction
Track description, text Text messages How are the text messages planned to be implemented in the line (i.e. which are the start/end conditions)?
messages and In particular, if any of the following combinations of parameters are used, please describe the expected on-board behaviour:
temporary speed 1) All start display events set to "No limitation" AND/OR all end display events set to "No limitation" together with Q_TEXTCONFIRM ≠ 0 (text to be acknowledged)
restriction 2) Upon reception of a text message to be acknowledged (Q_TEXTCONFIRM ≠ 0) the start and end display conditions are fulfilled immediately
3) The start and/or end display condition includes a mode event which can be left by the on-board as a result from a mode profile for current location, an immediate
level transition order or from a conditional level transition order given in the same trackside message
4) The start and/or end display condition includes a level event which can be left by the on-board as a result from an immediate level transition order or from a
conditional level transition order given in the same trackside message
X 6.6.1 5) A level or mode as the only event or as one of the end events (combined with a logical “or”, i.e. Q_TEXTDISPLAY = 0) defining its end condition, while the text
message could already be displayed when the on-board is not yet in the considered level/mode (e.g. because the display start condition is not mode dependent)
6) Several events which must be all fulfilled (combined with a logical “and" i.e. Q_TEXTDISPLAY = 1) define the start display condition or the end display condition.

Track description, text Text messages Text messages that require acknowledgement (Q_TEXTCONFIRM≠ 0) and whose start of display occurs in the vicinity of a level transition or of the start location of a
messages and Mode Profile which requires another acknowledgment: do you plan to engineer any of the following combinations of parameters?
temporary speed 1) Text message whose display can start less than 6 seconds before an MA with a Mode Profile (OS or LS) for current location is received
restriction 2) A trackside message including:
• a text message whose, upon reception of the message, display start condition is immediately fulfilled and display end condition is not fulfilled
• the first announcement of a level transition to be acknowledged (i.e. L1/2/3 -> L0 or L1/2/3 -> LNTC), whose acknowledgement window start location is already
passed by the max safe front end of the train upon reception of the message
and:
whose text message display end condition can be fulfilled less than 11 seconds after the reception of the message while the value of Q_TEXTCONFIRM is 2 or 3
AND/OR
which is received by the on-board less than 6 seconds before the level transition is executed
X 6.6.2
3) A trackside message including:
• a text message whose, upon reception of the message, display start condition is immediately fulfilled and whose display end condition can be fulfilled less than 11
seconds after the reception of the message while the value of Q_TEXTCONFIRM is 2 or 3
• an immediate level transition order (L1/2/3 -> L0 or LNTC -> L1) not previously announced, whose acknowledgement window start location is already passed by the
max safe front end of the train upon reception of the message
4) A trackside message including:
• a text message whose, upon reception of the message, display start condition is immediately fulfilled and whose display end condition can be fulfilled less than 11
seconds after the reception of the message while the value of Q_TEXTCONFIRM is 2 or 3
• an MA with a Mode Profile (OS or LS) for current location

Track description, text Text messages Is any of the modes NL, SH, SL, SF, IS, SE or SN planned to be implemented as an event defining the start or end display condition of a text message?
messages and
X 6.6.3 temporary speed
restriction

Track description, text Infill information 1) Do you plan to implement trackside constituents transmitting as infill information (i.e. after packet 136) a TSR revocation (packet 66):
messages and • Which refers to a TSR whose start location is in rear of the main BG the infill information relates to, and
temporary speed • Which is expected to take place only from the main BG location?
restriction 2) Do you plan to implement trackside constituents transmitting as infill information (i.e. after packet 136) a packet 44 to be forwarded to a National System (i.e. with
X 6.7.1
NID_XUSER = 102), whose content includes location based information referred to the balise group identified in the packet 136 (i.e. the main BG)?

Track description, text EUROLOOP Is it possible to receive via cross talk (considering also neighbouring areas) a version 1 (X=1) Euroloop message whose header includes a NID_C value different from the
messages and NID_C values applicable to the version 2 (X=2) area?
temporary speed If the answer is yes:
restriction 1) Is it foreseen to implement balise groups transmitting "Stop if in SR" information while an "SR authorisation" can be transmitted together with a "list of balises in SR
X 6.8.1 Authority" (packet 63) that includes the identifier of such balise group(s)?
2) Are there balise groups installed on the trackside sending National Values (packet 3) in a telegram marked with X=1, while the trackside expects that the
Q_NVLOCACC and V_NVLIMSUPERV National Values applicable to the area this track belongs to, whose at least one of them is different from its default value, are kept
untouched by the on-board?

Track description, text EUROLOOP Is it possible to receive via cross talk from a neighbouring area a version 2 (X=2) Euroloop message?
messages and
temporary speed If the answer is yes:
restriction 1) Is it foreseen to implement balise groups transmitting "Stop if in SR" information while an "SR authorisation" issued by a neighbouring RBC X=2 can be transmitted
X 6.8.2 together with a "list of balises in SR Authority" (packet 63) that includes the identifier of such balise group(s)?
2) Are balise groups installed on the track providing National Values (Packet 3) in addition to the border balise group whose message contains a "System version
order" (packet 2) to the system version X=1?

Mode profiles Protect SH What are the precautions planned to be implemented in order to avoid that the situations in Subset 113 appendix C (except case 8) can occur?
X 7.1.1 specificities movements

Mode profiles Protect SH 1) Can there be SH movements in level 0/NTC?

specificities movements
X 7.2.1
2) How are they planned to be implemented and these movements protected?

Level 2 timing Movement authority Which are the values for T_CYCRQST (packet 57: movement authority request parameters) and for T_CYCLOC (packet 58: position report parameters) planned to be
request parameters implemented?
X 8.1.1

Signalling and ETCS registration to 1) Which are the rules and restrictions for the locations where a start of mission after a cold movement is planned to occur?
communication radio network
X 9.1.1 interface 2) Is it planned to implement orders for registration to a radio network at these points where start of mission after a cold movement can be performed?

Signalling and ETCS registration to How will it be ensured that there is coverage from the desired radio network at the location where registration is planned to be requested to the EDOR?
X 9.1.2 communication radio network
interface

Signalling and Location of base How is it planned to avoid the same location of the radio handovers and RBC handovers & and stopping points?
communication transceiver station
interface handovers in relation
to RBC handovers
X 9.2.1 and stopping points

Signalling and Initiation of How is the functionality "establishment of a communication session initiated by the RBC" planned to be implemented?
X 9.3.1 communication communication
interface session by RBC
Signalling and Transmission speeds What is (are) the transmission speed(s) of the CS radio Bearer Service(s) supported by your trackside implementation (both RBC/RIU & GSM-R network)?
communication supported by RBC
X 9.4.1 interface

Signalling and Network common 1) Regarding the network timing, how it is a common time source planned to be used for the radio network, the fixed communication network and the ETCS trackside
communication timing elements?
X 9.5.1 interface
2) Is this common source to planned to be used by any debugging element?

Signalling and Session Is there a plan to consider an area without GSMR-R coverage as a radio hole for ETCS (installing a balise group with an order to establish connection at the end of an
communication establishment and announced radio hole area) or is it planned to be covered with operational rules or other means (e.g. driver to initiate start of mission at the area without coverage,
X 9.5.2 interface recovery T_NVCONTACT and its reaction engineered accordingly)?

Signalling and Session Does the RBCs enter the information transfer phase on reception of the (first) SABME message and consequently initiates the link resetting procedure on reception of
communication establishment and a second SABME frame before the first I frame during the link set-up (see Annex D “Applicability conditions of ISO/IEC 7776 (1995)” in Subset 037)?
X 9.5.3
interface recovery

Signalling and Session After a link reset event is notified by the underlying Euroradio Data Link layer in the RBC (i.e. when the number of retransmission attempts exceeds N2), is it planned
X 9.5.4 communication establishment and that the RBC considers the communication established for the following 5 minutes?
interface recovery
Signalling and Euroradio HDLC How have you considered the balance between different operational factors in the definition of the T_NVCONTACT timer?
X 9.6.1 communication parameters
interface
Signalling and Euroradio HDLC Does the calculation of the value of T_NVCONTACT rely on the fact that a disconnection/connection re-establishment could take place without the T_NVCONTACT
communication parameters elapsing on-board?
X 9.6.2 interface If the answer is yes, in order to achieve the connection re-establishment within T_NVCONTACT with a high enough probability, did you make assumptions on the HDLC
parameters T1&N2 used by the on-board?

Signalling and Euroradio HDLC Is there a plan to implement a value of T_NVCONTACT lower than 40 seconds?
communication parameters
X 9.6.3
interface

120 Rue Marc Lefrancq | BP 20392 | FR-59307 Valenciennes Cedex

Tel. +33 (0)327 09 65 00 | era.europa.eu
Page 2 of 3
 Draft Functions List
ERTMS Trackside Approval Learning Case

Signalling and Exchange of keys What is the expected key exchange frequency?
X 9.7.1 communication
interface

Signalling and Exchange of keys 1) Is there a process planned to be established for distribution of keys to the RBCs and to the on-board vehicles?
communication
X 9.7.2 interface 2) Is there a process planned in order to contact the corresponding home key management centrerscentres available to all the relevant organisations (railway
undertakings, infrastructure managers, others)?

Signalling and Exchange of keys Is online key management planned to be implemented as the only possible mechanism to renew the key on-board the trains?
X 9.7.3 communication
interface
Signalling and Exchange of keys For online key management, is it planned to configure the network to allow the connection of the on-board to its home key management center also in case it is
X 9.7.4 communication outside the KM domain the line belongs to?
interface

Signalling and Exchange of keys 1) How is it planned to deal with B2 on-board configurable with a limited number (possibly reduced to one single key) of different KMAC?
communication
interface 2) Is the capacity of storage of keys in the RBCs planned to be implemented sufficient for the chosen strategy of allocation of keys to the on-boards?
X 9.7.5

Communication (both Interferences 1) Are the mechanisms to manage the risks of interferences from public network considered, as agreed in:
voice and ETCS level 2 · DV81: GSM-R interferences and coexistence with public mobile networks, 13/07/2016
data) · ECC REPORT 162: Practical mechanism to improve the compatibility between GSM-R and public mobile networks and guidance on practical coordination, May 2011
· ECC REPORT 229: Guidance for improving coexistence between GSM-R and MFCN in the 900 MHz band, May 2015
2) Are they planned to be put in place before the project is implemented or during implementation of the project? Is the discussion group already in place or is it
1 10.1.1 planned to be set? (discussion with public networks on radio levels, possible installation of filters in the GSM-R network nor in the public network, reinforcement of
GSM-R network with additional base transceiver station, etc.)
Please justify your answers.

Communication (both Capacity of the Regarding the hot spots identification:

voice and ETCS level 2 network
data) Given that it is only possible to establish 8 simultaneous communications per radio cell in a base transceiver station in circuit switching (CS), (to be used for voice and
data, all together):

1) Do you plan to have areas where the availability of frequencies is lower than in the rest of the network (e.g. at stations, shunting yards, depots, or lines at border
areas- due to the frequency arrangements with the neighbouring country-)?
2 10.2.1
2) Is the capacity of the planned radio network sufficient to handle the communication needs for the intended operation? Do the design rules include traffic analysis
(voice and ETCS data, # of simultaneous trains and corresponding radio communication sessions in a specific location – including trains in Sleeping mode, notification
of change of mode-, in particular, in train stations, shunting yards, depots)? Do you plan to use GSM-R also for other applications than related to train operation and
is this included in the design rules/traffic analysis?
Please justify your answers.

Communication (both Capacity of the 1) Do you plan to engineer trackside constituents transmitting a packet 42 (Session Management) with Q_RBC = 0 (Terminate communication session) and
voice and ETCS level 2 network Q_SLEEPSESSION = 0 (Ignore session management information)?
data) If the answer to question 1 is yes:
2) Do you expect that the session termination order described in question 1 systematically apply to sleeping units?
X 10.2.2 If the answer to question 2 is yes:
3) Should a sleeping unit ignore the session termination order described in question 1.1 (i.e. the ERTMS/ETCS on-board takes into account the value of
Q_SLEEPSESSION), do you consider that not releasing the corresponding radio channel could prevent the normal service (e.g. leading to no more available radio
resources in busy stations)?

Communication (both Change of radio How do the design rules for GSM-R on border crossing lines consider the overlapping coverage and the planning of the 'handover break period'? Is the change of radio
voice and ETCS level 2 network network planned to be announced with line side signs?
3 10.3.1 data)

Communication (both Change of radio Is there a plan to agree at border areas the frequency planning together with the neighbouring country? Please justify it.
voice and ETCS level 2 network
4 10.3.2 data)

Communication (both Change of radio 1) Do you plan to engineer track sections that can be travelled by a train in normal operation conditions where the trackside constituents transmit messages including
voice and ETCS level 2 network a Radio Network registration order (packet 45) whose first instance referring to a given Radio Network received by the on-board also includes a communication session
data) establishment order to an RBC belonging to this Radio Network (i.e. through a packet 42 with Q_RBC =1 or a packet 131)?

X 10.3.3
If the answer to the question 1 is yes:
2) Does the first instance referred to in question 1 represent the sole instance of both a session establishment order for the concerned RBC and the Radio Network
registration order for the concerned Radio Network?

Communication (both Use of extended Is the network planned to be configured to use other frequencies outside the UIC band (876-880 MHz paired with 921-925 MHz)?
voice and ETCS level 2 band (E-GSM-R)
data) Note that other bands are not for interoperable functions: this has to be correctly configured in the GSM-R network. Please provide the evidences that this is taken
X 10.4.1 into account in the network configuration (or that operational procedures are planned for vehicles that cannot use the non-interoperable radio frequency bands).

Communication (both Registration to radio 1) Are roaming agreements planned with neighbouring GSM-R networks? Please justify it.
voice and ETCS level 2 network
5 10.5.1 data) 2) What is the mechanism planned to establish these agreements when needed, potentially with all the EU GSM-R networks?

Communication (both Registration to radio 1) Is a roaming agreement envisaged for the national GSM-R users to use public GSM network? When yes, will this be used for train operation (e.g. driver-signaller
voice and ETCS level 2 network communication)? Please justify it.
data)
2) In case such a roaming agreement is envisaged, does it plan to include foreign GSM-R users visiting the national GSM-R network? Please justify it.
X 10.5.2
3) In case the use of public network is planned to be considered as a need (as backup, for example): Are there operational rules planned to be implemented for those
on-board vehicles not able to use the public network? Please justify it.

Communication (both Availability/ coverage 1) Is it planned to configure the network to provide the minimum coverage level required for voice communication and/or ETCS? Is there a plan to increase the coverage
voice and ETCS level 2 in case this is needed? On which cases?
6 10.6.1 data)
2) Is it planned to implement a mechanism to check the coverage level periodically?

Communication (both Availability/ coverage How is it planned to consider in the availability of the overall network (i.e. system availability) the fixed part, optical links, etc., on top of the radio coverage availability?
voice and ETCS level 2
7 10.6.2 data)

Communication (both SIM card 1) Is a SIM card provisioning process and a platform to commission them planned to become available?
voice and ETCS Level 2 configuration 2) What Elementary Files and which configuration in them do you plan to implement in your GSM-R SIM cards?
8 10.7.1 data)

ETCS Level 2 Data General packet radio 1) Has a study been made on the number of on-board vehicles expected to run in ETCS level 2/3 that would not support GPRS? Has a plan been foreseen to ensure
Communication service (GPRS) that there are sufficient radio resources to carry the additional circuit switched (CS) calls from non-packet switched (PS) - ETCS level 2/3 trains and for the required
voice communications in the GPRS areas?

X 11.1.1 2) Is there a plan to implement a mechanism to adjust the radio channel configuration to the operational needs (number of radio channels dedicated to CS and to PS)?
Is this automatic or manual?

3) In relation to PS communications, are there any time limits defined for the PPP establishment?

ETCS Level 2 Data General packet radio 1 - Is the ETCS DNS planned to be configured to accept queries done with the CLASS "IN"? Is the DNS planned to be configured to accept the queries for A and TXT
Communication service (GPRS) fields done in two separate requests? Please justify it.
X 11.1.2 2 - How is ETCS DNS query repetition expected to be handled in order to achieve a successful establishment of a PS connection with the RBC?

ETCS Level 2 Data General packet radio Is there a plan to implement a specific operational procedure for the start of mission in packet switching (PS) or circuit switching (CS)? (e.g. to call the traffic control
X 11.1.3 Communication service (GPRS) center before start of mission, to get the permission to establish the connection to the RBC)

ETCS Level 2 Data Quality of service 1) Are the quality of service parameters indicated in the informative subset 093 planned to be required?
Communication
X 11.2.1
2) If not, what are the alternative parameters planned to be required to achieve the intended quality of service?

ETCS Level 2 Data Quality of service Are there plans to monitor the quality of service during operation to assure minimum quality required for ETCS data transmission?
X 11.2.2 Communication

Voice Communication Radio emergency call How is the existence of a Radio Emergency Call planned to be cascaded to the RBC (so that it automatically sends MA shortening for the train in the corresponding
area) and/or how is it planned to be connected to other equipment or network (such as public network)?
X 12.1.1

Voice Communication Radio emergency call What is the plan to configure the enhanced radio emergency call (eREC) areas? Is there a plan to ensure that a radio emergency call will always be launched in the
X 12.1.2 corresponding area when an eREC is started?

Voice Communication Group calls For the trains that may not be able to use GID 500 and/or GID 555, which are the specific operational procedures planned to be established?
9 12.2.1

Voice Communication Group calls What are the rules for using call GID 200?
10 12.2.2

Voice Communication Registration of How is it planned to ensure that functional numbers, including train running number, are unique even for border crossing trains?
11 12.3.1 functional numbers

Voice Communication Connection to/from Is there a plan to include users of Class B radio systems or emergency services in certain group calls (radio emergency call or other group calls)? If yes, please justify.
external users
12 12.4.1

Voice Communication Connection to/from 1) Is it planned to configure the GSM-R network to allow all GSM-R user equipment (cabradio, handhelds) to dial 112 (emergency number) (i.e. equipment fitted with
external users subscriber identity module (SIM) cards from GSM-R networks)? If not, please justify.

13 12.4.2 2) Is it planned to configure the GSM-R network to allow all user equipment (i.e. fitted with non GSM-R SIM cards but being able to use the GSM-R radio frequencies)
to dial 112 (emergency number)? If not, please justify.

Voice Communication Change of radio 1) Is the change of radio network planned to be implemented automatically or manually?
network
X 12.5.1
2) How is it planned to be coordinated with the neighbouring network?

Voice Communication Connection to 1) Is it planned to use mobile dispatchers only, fixed line dispatchers only or both?
Dispatchers 2) Is it planned to connect the GSM-R core to an existing dispatchers system?
3) What are the types of calls expected to be made to/from the dispatchers system? (Priorities, groups, point-to-point, calls to non-GSM-R groups- such as rescue
14 12.6.1 teams, firemen…)
4) What is the planned configuration of the Group Call Register in order to reflect the types of calls expressed in point 3 (above)?

Voice Communication Connection to 1) Is the specific allocation of areas of control to the dispatchers already planned?
Dispatchers 2) Is it planned to have an overlap between the areas of control and the dispatchers (i.e. may a specific dispatcher be involved in calls for only one geographical area or
15 12.6.2 for many)?
3) What is the planned configuration of the Group Call Register in order to reflect the areas of control according to the answer provided in point 2 (above)?

Voice Communication Connection to 1) Confirmation of Railway Emergency Call: is it planned that the dispatchers’ equipment will send confirmation of High Priority Calls to the Confirmation Center?
Dispatchers 2) In case this is the intention, is it planned to use User to User Information Elements?
16 12.6.3 3) What configuration of the confirmation parameters is planned to be implemented?

Voice Communication Connection to What are the maximum delays for the call processing times planned to be for the network and for the dispatchers system (in particular for the Railway Emergency Call
17 12.6.4 Dispatchers and for the group call to all drivers in an area)?

Voice Communication Connection to 1) Is it planned to use Dual-Tone Multi-Frequency signaling for the termination /leaving/muting/unmuting of Voice Group Calls and/or Voice Broadcast Calls by the
Dispatchers dispatchers system?
2) Is it planned to use message based explicit signaling option for the termination /leaving/muting/unmuting of Voice Group Calls and/or Voice Broadcast Calls by the
18 12.6.5
dispatchers system
3) Is the GSM-R core planned to be Release 99, Release 4 or mixed?

Voice Communication Connection to 1) Considering that minimum interaction is needed to establish Railway Emergency Calls: how is the launching of Railway Emergency Calls planned to be performed? Is
Dispatchers it planned to have a dedicated button/area on the screen only for this action or is it planned to have additional actions available in the same area?
19 12.6.6 2) Is it planned to have any protection against an unwanted initiation of a Railway Emergency Call (e.g. need to press a button for x seconds, confirmation screen)?

Voice Communication Availability/ coverage If there are areas planned not to be covered with GSM-R, which are the specific operational requirements planned to be implemented?
20 12.7.1

Other functions Data used by 1) Do you plan to implement packets 44 containing data to be forwarded to a National (signalling) System (i.e. a class B system)?
applications outside In case the answer to question 1 is yes, please specify the NID_XUSER value used and answer to the following questions:
the ERTMS/ETCS 2) In case the NID_NTC variable is not included in the packet 44, do you expect that such National data will be forwarded by the ETCS on-board STM control function
system without any other consideration than the SUBSET-035 v3.1.0 clause 10.11.1.1 for a B3 ETCS on-board equipment, or than the SUBSET-035 v2.1.1 section 5.2.13 for a
B2 ETCS on-board equipment, i.e. the forwarding to the on-board National System does not rely on any national requirements in case the ETCS on-board equipment is
interfaced to the national system through an STM?
3) Do you plan to engineer trackside constituents transmitting several packets 44 containing data to be forwarded to the same National System i.e. a trackside message
containing several packets 44 identifying the same NID_XUSER and, for X=2 RBCs and for balise telegrams marked with X=2, the same NID_NTC in case of NID_XUSER =
102 (e.g. national information contained in duplicated balise telegrams)?
X 13.1.1 If the answer to questions 2 and 3 is yes (NID_NTC variable not included in the packet 44):
If the answer to question 3 is yes (NID_NTC variable included in the packet 44):
4) Do you expect that all packets 44 mentioned in question 3 are forwarded unconditionally to the National System even when the ETCS on-board equipment is
interfaced to an STM (e.g. even though a packet 44 is contained in a balise telegram ignored/rejected by the ETCS on-board according to the ETCS rules, this latter
should still be forwarded to the STM by the STM control function)?

120 Rue Marc Lefrancq | BP 20392 | FR-59307 Valenciennes Cedex

Tel. +33 (0)327 09 65 00 | era.europa.eu
Page 3 of 3