ETSI TS 102 610 V1.3.0 (2013-01)

Railways Telecommunications (RT); Global System for Mobile communications (GSM); Usage of the User-to-User Information Element for GSM Operation on Railways

RTS/RT-0022

General Information

• Status: Published
• Publication Date: 21-Jan-2013
• Technical Committee: RT - Railway telecommunications
• Current Stage: 12 - Completion
• Due Date: 15-Feb-2013
• Completion Date: 22-Jan-2013

Standards Content (Sample)

Technical Specification
Railways Telecommunications (RT);
Global System for Mobile communications (GSM);
Usage of the User-to-User Information Element
for GSM Operation on Railways
2 ETSI TS 102 610 V1.3.0 (2013-01)

Reference
RTS/RT-0022
Keywords
GSM, GSM-R, user
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2013.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 610 V1.3.0 (2013-01)
Contents
Intellectual Property Rights . 4
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 General UUIE Format . 8
4.1 Encoding protocol and information capacity . 8
4.2 General encoding of the user defined content . 9
4.3 Definition of tag values . 9
5 Definition of individual tag contents . 10
5.1 Presentation of functional number tag . 10
5.2 Confirmation of High Priority Calls tags . 10
5.2.1 CHPC tag definition for mobile device. 11
5.2.2 CHPC tag definition for collecting network device . 12
5.2.3 CHPC eREC extension tag definition for mobile device . 13
5.3 Enhanced presentation of functional number . 14
5.4 Presentation of text strings . 14
5.5 Transfer of train position . 15
5.6 Notification DSD alarm condition . 16
5.7 Notification of a request to alert a controller . 16
6 Transfer of functional number of initiator of railway emergency call . 17
6.1 Introduction . 17
6.2 Compressed OTDI encoding . 17
6.3 Conversion of compressed OTDI into UUIE . 18
7 Examples of use . 18
7.1 Examples according to general UUIE format . 18
7.1.1 Presentation of functional number . 18
7.1.2 Confirmation of High Priority Calls Application. 18
7.1.3 Enhanced presentation of functional number . 22
7.1.4 Transfer of train position for eLDA . 23
7.1.5 Notification of a DSD alarm condition . 23
7.1.6 Notification of request to alert a controller . 25
7.2 Example of transfer of functional number of initiator of a railway emergency call . 25
7.3 Examples of encoding of ePFN tag . 27
Annex A (informative): Bibliography . 28
History . 29

ETSI
4 ETSI TS 102 610 V1.3.0 (2013-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Railway
Telecommunications (RT).
Introduction
The User-to-User Signalling Supplementary Service is widely used in the operation of GSM for Railways (GSM-R).
The applications "Presentation of Functional Numbers" [i.2] and [i.3] and "Confirmation of High Priority Calls" [i.4]
and [i.5] have been specified, implemented and tested in the framework of national GSM-R schemes. In defining
layouts for the new features, DSD Alarm Notification, Alerting of a Controller and CHPC for enhanced Railway
Emergency Call, care has been taken to ensure that existing implementations are not compromised or invalidated when
laying out a framework for flexible further extension. For any such further extension, therefore, it is mandatory to
define the use of UUIE in these various applications to avoid interoperability issues in the future.
ETSI
5 ETSI TS 102 610 V1.3.0 (2013-01)
1 Scope
The present document defines the contents of the User-to-User Information Element when used in the GSM-R
environment. This includes the basic EIRENE features Functional Addressing, Location Dependant Addressing,
Confirmation of High Priority Calls (including, but not exclusively, REC and eREC) and Presentation of Functional
Numbers. In addition the present document defines layouts for further features: Enhanced Presentation of Functional
Numbers, Enhanced Location Dependent Addressing, Driver's Safety Device alarm, Plain Text Messages, Presentation
of the Functional Number of the initiator of a Railway Emergency Call and Alerting of a Controller. Finally, the present
document describes the requirements to be followed by network operators to ensure compatibility and interoperability if
they wish to define specific fields for national and/or network use. The details of such fields are outside the scope of the
present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 123 038 (V3.3.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS); Alphabets and language-specific
information (3G TS 23.038 Release 1999)".
[2] ETSI TS 124 007 (V3.10.0): "Digital cellular telecommunications system (Phase 2+); Universal
Mobile Telecommunications System (UMTS); Mobile radio interface signalling layer 3; General
aspects (3GPP TS 24.007 Release 1999)".
[3] ETSI TS 100 933 (V8.6.0): "Digital cellular telecommunications system (Phase 2+); Voice Group
Call Service (VGCS); Stage 2 (3GPP TS 03.68 Release 1999)".
[4] ETSI TS 100 948 (V8.1.0): "Digital cellular telecommunications system (Phase 2+) (GSM);
Group Call Control (GCC) protocol (GSM 04.68 Release 1999)".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] EIRENE SRS: "UIC Project EIRENE System Requirements Specification".
NOTE: Available at UIC EIRENE Specifications.
[i.2] MORANE F 10 T 6003 4: "FFFS for Presentation of Functional Numbers to Called and Calling
Parties".
NOTE: Available at UIC GSM-R Normative Documents.
ETSI
6 ETSI TS 102 610 V1.3.0 (2013-01)
[i.3] MORANE F 12 T 6003 4: "FIS for Presentation of Functional Numbers to Called and Calling
Parties".
NOTE: Available at UIC GSM-R Normative Documents.
[i.4] MORANE F 10 T 6002 5: "FFFS for Confirmation of High Priority Calls".
NOTE: Available at UIC GSM-R Normative Documents.
[i.5] MORANE F 12 T 6002 5: "FIS for Confirmation of High Priority Calls".
NOTE: Available at UIC GSM-R Normative Documents.
[i.6] eLDA IRS (V5.0): "Interface Requirements Specification enhanced Location Dependent
Addressing".
NOTE: Available at UIC GSM-R Informative Documents.
[i.7] O-3151-1.0 eREC specification.
NOTE: Available at UIC GSM-R Informative Documents.
[i.8] O-3152-1.0 Definition and structure of eREC parameters.
NOTE: Available at UIC GSM-R Informative Documents.
[i.9] Void.
[i.10] Void.
[i.11] ETSI Directives.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in the ETSI directives [i.11] and the following
apply:
cab radio: radio and associated user and other interfaces installed in the cab of a locomotive and for use principally by
the locomotive driver
call type: prefix used to identify the type of user number dialled
coach number: number assigned to an item of rolling stock on a permanent basis
NOTE: The coach number may form a component of a functional number used to address users/systems on an
item of rolling stock.
controller: individual at a fixed location responsible for the conduct and co-ordination of some aspect of train
operations
NOTE: Also known as a dispatcher, in particular the term dispatcher is used in this context in ETSI specifications
relating to the VGCS and VBS.
dispatcher: individual at a fixed location responsible for the conduct and co-ordination of vehicle movements and
operations
NOTE: In railway operations, the dispatcher is usually known as a controller.
driver's safety device: on-train system which monitors the alertness of the driver and provides warning and alarms to
other systems as appropriate
ETSI
7 ETSI TS 102 610 V1.3.0 (2013-01)
engine number: number assigned to an item of traction stock on a permanent basis
NOTE: The engine number may form a component of a functional number used to address users/systems on an
item of traction stock.
enhanced railway emergency call: railway emergency call with enhanced functionality to sub-divide the area covered
by such a call
NOTE 1: Sub-divided areas which are covered by an eREC are used to include or exclude joining, crossing and
parallel tracks and also shunting areas.
NOTE 2: eREC allows discrimination of railway emergency calls in order to minimize production loss.
functional addressing/numbering: term used to describe the process of addressing a call using a number representing
the function a user is performing, rather than a number identifying the user's terminal equipment
functional identity: full alphanumeric description of the function performed by a called or calling party within the
functional numbering scheme, identifying them by function or role rather than by a specific item of radio equipment or
user subscription
NOTE: The functional identity can include characters and/or numbers.
functional number: full number used within the functional addressing scheme to contact an end user/system by
function or role rather than by a specific item of radio equipment or user subscription
group call: call made to all members of a pre-defined group within a local geographical area
NOTE: Only one member of the group may talk at any instant with all other group members listening only.
international code: prefix used to identify an EIRENE network outside the network the in which the calling party is
operating
location dependent addressing: term used to describe the process of addressing a particular function (typically a
controller) based on the current location of the user (typically a train)
railway emergency call: call of the highest priority for informing drivers, controllers and other concerned personnel of
a level of danger requiring all railway movements in a pre-defined area to follow specific operational procedures
NOTE: Two types of railway emergency calls are defined:
� train emergency calls (for railway emergencies whilst not involved in shunting operations);
� shunting emergency calls (for railway emergencies whilst involved in shunting operations).
train number: number given to a train by operational staff for a particular journey
NOTE: A train number may form a component of the functional number used to address users or systems on a
train.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASCII American Standard Code for Information Interchange
BCD Binary Coded Decimal
CBS Cell Broadcast Service
CHPC Confirmation of High Priority Call
CT Call Type
DSD Driver's Safety Device
EIRENE European Integrated Railway radio Enhanced Network
eLDA enhanced Location Dependent Addressing
ePFN enhanced Presentation of Functional Number
eREC enhanced Railway Emergency Call
FC Function Code
FFFS Form Fit Functional Specification
ETSI
8 ETSI TS 102 610 V1.3.0 (2013-01)
FIS Functional Interface Specification
FN Functional Number
GC_REF Group Call Reference
GPS Global Positioning System
GSM-R Global System for Mobile-Rail
HMI Human Machine Interface
IC International Code
IE Information Element
MCC Mobile Country Code
MNC Mobile Network Code
MORANE Mobile Radio for Railway Networks in Europe
MSC Mobile Switching Centre
OTDI Originator-To-Dispatcher-Information
PFN Presentation of Functional Number
REC Railway Emergency Call
TLV Tag Length Value
UIC Union Internationale des Chemins de fer
UIN User Identifier Number
UUI User-to-User Information
UUIE User-to-User Information Element
UUS User-to-User Signalling
UUS1 User-to-User Signalling Service 1
VBS Voice Broadcast Service
VGCS Voice Group Call Service
4 General UUIE Format
4.1 Encoding protocol and information capacity
The general format of the User-to-User Information Elements used in GSM-R is shown in figure 1.
8 7 6 5 4 3 2 1
User-to-user IEI Octet 1
UUIE
Length of user-user contents = 'm + 1' Octet 2
Header
User-to-user protocol discriminator
Octet 3
00 00000 0
UUIE
User-Defined Content m Octets
Content
Figure 1: General ETSI coding format for User-to-User Information Elements (UUIE)
The maximum length of user-defined information (m octets in figure 1) is limited to 32 octets (35 octets for the overall
maximum length of the UUIE) to ensure transparency through all mobile and fixed elements of a GSM-R network.
Binary encoding should generally be used to maximize the data content in this limited space. This requires the "protocol
discriminator" to be set to "User-Specific Protocol".
< User-to-User protocol discriminator >: 00000000 User Specific Protocol.
NOTE: In one special case, "Presentation of the Functional Identity of the Initiator of a Railway Emergency
Call", the ETSI specifications for VGCS make necessary the use of a different encoding and protocol
discriminator (see clause 6).
ETSI
9 ETSI TS 102 610 V1.3.0 (2013-01)
4.2 General encoding of the user defined content
The UUIE provides a limited space of 32 information octets. Therefore an efficient and flexible coding scheme based
on the "Tag-Length-Value" (TLV) structure is used. This coding scheme allows for easy and correct decoding of
received information even when information not understood by the receiving application is mixed with the desired
information. This scheme also supports the inclusion of multiple user information fields of variable lengths. The general
structure is illustrated in figure 2.
8 7 6 5 4 3 2 1
User-to-user IEI Octet 1
UUIE
Length of user-user contents Octet 2
Header
User-to-user protocol discriminator
Octet 3
000 000 00
Tag <1> representing contents feature information
Octet 4
Length of Tag <1> content = m Octet 5
Tag <1>
Information content for Tag <1> m octets
Tag <2> representing contents feature information
Octet 6+m
Octet
Length of Tag <2> content = n
6+m+1
Tag <2>
Information content for Tag <2> n octets
Tag <3> Octet
Tag <3> representing contents feature information
etc. 6+m+n+2
Figure 2: Generic coding format for User-to-User Information Elements (UUIE)
using user specific protocol in the GSM-R context
The structure of Tag, Length, Value is repeated, as many times as there are tags in the message and enough room for
them. This is the TLV structure. Restrictions on the order of TLV tags is as defined in clause 7.1.1.
4.3 Definition of tag values
The number of different tags for UUIE content complying with the TLV structure is limited to 255 where the tag range
0 to 127 is reserved for international use and the range 128 to 255 is reserved for national use.
The tags that are defined for international use are listed in table 1.
Table 1: Identification of GSM-R specific tags for international use
Tag Value Feature
2 Acknowledgement by Receiver of a High Priority Call and response from device
accepting the acknowledgement
3 Acknowledgement by Initiator of a High Priority Call
4 eREC extension for acknowledgement of a High Priority call
5 Presentation of Functional Number
6 to 8 enhanced Location Dependent Addressing
9 ePFN Information
10 User specific plain text according to alphabet indicator
11 DSD Alarm Notification
12 Alerting of a Controller Notification and Response

ETSI
10 ETSI TS 102 610 V1.3.0 (2013-01)
5 Definition of individual tag contents
This clause defines the content of each of the tags listed in table 1. The tags may be combined with other tags in specific
applications, and such uses are described in clause 7. Because tags may be combined, the illustrations in this clause only
contain the tag definition and do not illustrate the complete UUIE structure and content. Clause 7 contains complete
examples of that kind.
5.1 Presentation of functional number tag
According to [i.2] and [i.3], the Functional Number (FN) is always transferred in the UUS1 as an International FN, that
is:
FN = IC + CT + UIN + FC
This tag can be included in any allowed call control message where it is required to transfer the FN of the sending party
to the other party in the call. The general layout of the PFN tag is given in figure 3.
8 7 6 5 4 3 2 1
Tag representing Presentation of Functional Number = '05'
Octet 1
000 001 01
Functional number length = m octets - 2 octets Octet 2
BCD-coded FN digit #2 BCD-coded FN digit #1 Octet 3
... BCD-coded FN digit #3 Octet 4
Functional
Number
BCD-coded FN digit #p or $F BCD-coded FN digit #p-1 Octet m

NOTE 1: The FN length field specifies the number of octets present to carry the FN. Each digit of a FN is encoded
as a BCD digit (one nibble). The first FN digit is in bits 1 to 4 and the next digit is in bits 5 to 8 of octet 3 of
the tag; the following digit is in bits 1 to 4 of next octet and so on. If the FN consists of an odd number of
digits, then the last half octet (bits 4 to 7) of the FN should contain "0xF" as a filler. Therefore "0xF" can
never be a valid digit within the FN.
NOTE 2: The hexadecimal value "0xF" represents the binary value of 4 bits, all set to "1".

Figure 3: General Format of PFN Tag Content
Octets consisting of two half octets, both set to "0xF", shall not be used in PFN tags as a filler; only octets containing
valid BCD digits, or a single "0xF" nibble shall be included. If no valid FN is available for transmission, then a PFN tag
encoded as shown in figure 4 shall be used.
8 7 6 5 4 3 2 1
Tag representing Presentation of Functional Number = '05'
Octet 1
0 0 0 001 01
Functional number length = 0 Octet 2

Figure 4: PFN Tag Content to Indicate "No FN Available"
5.2 Confirmation of High Priority Calls tags
The procedure for the Confirmation of a High Priority Call, including REC and eREC, is defined in [i.4] and [i.5].
UUS1 tags are used by the mobiles involved in the call and also by the network device that is responsible for collecting
the confirmation messages. The tags involved are defined below.
ETSI
11 ETSI TS 102 610 V1.3.0 (2013-01)
5.2.1 CHPC tag definition for mobile device
8 7 6 5 4 3 2 1
Tag representing Confirmation of High Priority Call = '02' or '03'
Octet 1
000 0001 x
CHPC message length = 13 octets
Octet 2
T_DUR low octet
Duration
T_DUR mid octet Octets 3-5
of call
T_DUR high octet
T_REL low octet
T_REL mid-low octet
Relative time
Octets 6-9
of termination
T_REL mid-high octet
T_REL high octet
Priority level
PL_CALL Octet 10
of call
Cause of
CAUSE Octet 11
termination
GC_REF digit#2 GC_REF digit#1
GC_REF digit#4 GC_REF digit#3
Group call Octets
reference 12-15
GC_REF digit#6 GC_REF digit#5
GC_REF digit#8 GC_REF digit#7
Figure 5: CHPC tag content for mobile device
The tag content is identical in structure for both the call initiator and the call recipients and is illustrated in figure 5, only
the tag value differs for the two cases. The information is included in a SETUP message. The fields of the message have
the following interpretation:
• T_DUR: A 24-bit unsigned integer specifying the duration of the call in units of 100 ms.
• T_REL: A 32-bit unsigned integer specifying the interval between the end of the call and the transmission of
the confirmation message in units of 100 ms.
• PL_CALL: An 8 bit value giving the priority level of the call as follows (this is a general encoding and in
practice value 0x05 is the one usually to be employed):
- 0x00 no priority specified in call;
- 0x01 eMLPP priority of 4 (Railway Information);
- 0x02 eMLPP priority of 3 (Railway Operation);
- 0x03 eMLPP priority of 2 (Public Emergency/Group Calls);
- 0x04 eMLPP priority of 1 (Command and Control);
- 0x05 eMLPP priority of 0 (Railway Emergency).
• CAUSE: An 8 bit value giving the reason for termination of the call as follows:
- 0x00 no error;
- Bits #1 to 4 (least significant bits) system errors;
- Bit #1 mobile was powered off when receiving (power fail);
- Bit #2 call was interrupted due to radio link error;
ETSI
12 ETSI TS 102 610 V1.3.0 (2013-01)
- Bit #3 reserved;
- Bit #4 reserved;
- Bits #5 to 8 (most significant bits) user actions;
- Bit #5 call was left on user command;
- Bit #6 reserved;
- Bit #7 reserved;
- Bit #8 reserved.
• GC_REF: A 4-octet value giving the group call reference of the call [3], encoded as 8 nibbles with each nibble
being a BCD value representing one digit of the group call reference.
If this tag is being sent as part of the confirmation sequence of an eREC that the mobile station determined it should not
join then the values of some of the above fields shall be set to specific, non-intuitive, values as follows:
• T_DUR: A 24-bit unsigned integer of value 00 00 00.
• T_REL: A 32-bit unsigned integer giving the interval between the decision not to join the call and the
transmission of the confirmation message in units of 100 ms.
• PL_CALL: An 8 bit value giving the priority level of the call - unchanged from basic usage given above.
• CAUSE: An 8 bit value giving the reason for termination of the call - always 0x00 (no error).
• GC_REF: A 4-octet value giving the group call reference of the call - unchanged from basic usage given
above.
5.2.2 CHPC tag definition for collecting network device
The network device which collects the confirmation messages is required to indicate back to the sending mobile device
whether the information has been successfully received and stored or not. The tag is included in a
RELEASE_COMPLETE message which shall have the release cause value of "Normal Call Clearing". The tag content
is illustrated in fi
...