From railML 3 Wiki
Jump to navigation Jump to search




Autoexport from the XML-Schema for element IL:etcsGeneralData of railML® version 3.2
Documentation list of main ETCS variables of the RBC
Subschema interlocking
Parents* radioBlockCentre
Children None
  • mVersion: Version of the ETCS specification used with this RBC represented by the defined M_Version value. (optional; xs:nonNegativeInteger),

  • nidCountry: NID_C - Identity number of the country or region: Code used to identify the country or region in which the balise group, the RBC or the RIU is situated.

These need not necessarily follow administrative or political boundaries. (optional; xs:nonNegativeInteger),

  • nidRBC: NID_RBC - RBC ETCS identity number: This variable provides the identity of the RBC belonging to NID_C. The RBC ETCS identity is given by NID_C + NID_RBC. (optional; xs:nonNegativeInteger),

  • nidRadio: NID_RADIO - Radio subscriber number: Quoted as a 16 digit decimal number. The number is to be entered “left adjusted” starting with the first digit to be dialled. Padding by the

special value F shall be added after the least significant digit of the number.

For further information about NID_RADIO  refer to SUBSET-054. (optional; xs:string; patterns: 0x[0-9A-Fa-f]+|[0-9]),

  • nidRadioNetwork: NID_MN - Identity of Radio Network: The NID_MN identifies the GSM-R network the calling mobile station has to register with. The NID_MN consists of up to 6 digits which are entered left adjusted into the data field, the leftmost digit is the digit to be dialled first. In case the NID_MN is shorter than 6 digits, the remaining space is to be filled with special character “F”. For further information about NID_MN refer to Subset-54. (optional; xs:string; patterns: 0x[0-9A-Fa-f]{6})
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

This element does not appear in railML® 3.1. It is available only in railML® 3.2. Do not hesitate to contact for further questions.

Changes 3.1→3.2

Introduced with version 3.2


Best Practice / Examples

Additional Information


Open Issues