train voice radio systems - rssb iss 1.pdfpage 4 of 51 rssb railway group standard gk/rt0094 issue...

Railway Group Standard

GK/RT0094

Issue One

Date March 2013

Train Voice Radio Systems

Synopsis

This document sets out the mandatory requirements for the application of train voice radio systems, specifically interface requirements for the infrastructure manager and the railway undertakings.

Copyright in the Railway Group Standards is owned by Rail Safety and Standards Board Limited. All rights are hereby reserved. No Railway Group Standard (in whole or in part) may be reproduced, stored in a retrieval system, or transmitted, in any form or means, without the prior written permission of Rail Safety and Standards Board Limited, or as expressly permitted by law.

RSSB Members are granted copyright licence in accordance with the Constitution Agreement relating to Rail Safety and Standards Board Limited.

In circumstances where Rail Safety and Standards Board Limited has granted a particular person or organisation permission to copy extracts from Railway Group Standards, Rail Safety and Standards Board Limited accepts no responsibility for, nor any liability in connection with, the use of such extracts, or any claims arising therefrom. This disclaimer applies to all forms of media in which extracts from Railway Group Standards may be reproduced.

Published by: RSSB Block 2 Angel Square 1 Torrens Street London EC1V 1NY © Copyright 2013 Rail Safety and Standards Board Limited

Uncontrolled When Printed Document comes into force 01/06/2013 Supersedes GERT8080 Iss 1, GERT8081 Iss 1 and GERT8082 Iss 1 on 01/06/2013 Superseded by RIS-0794-CCS Iss 2 with effect from 04/03/2017

of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Issue record

Issue Date Comments

One March 2013 The content of this document sets out the requirements for train voice radio for the Great Britain (GB) rail network.

Superseded documents

The following Railway Group documents are superseded, either in whole or in part as indicated:

Superseded documents Sections superseded

Date when sections are superseded

GE/RT8080 issue one Train Radio Systems for Voice and Related Messaging Communications

All 01 June 2013

GE/RT8081 issue one Requirements for GSM-R Voice Radio System

All 01 June 2013

GE/RT8082 issue one GSM-R Cab Mobile, Great Britain Open Interface Requirements (Rapid Response)

All 01 June 2013

GE/RT8080 issue one Train Radio Systems for Voice and Related Messaging Communications, ceases to be in force and is withdrawn as of 01 June 2013.

GE/RT8081 issue one Requirements for GSM-R Voice Radio System, ceases to be in force and is withdrawn as of 01 June 2013.

GE/RT8082 issue one GSM-R Cab Mobile, Great Britain Open Interface Requirements (Rapid Response), ceases to be in force and is withdrawn as of 01 June 2013.

Supply

The authoritative version of this document is available at www.rgsonline.co.uk. Uncontrolled copies of this document can be obtained from Communications, RSSB, Block 2, Angel Square, 1 Torrens Street, London EC1V 1NY, telephone 020 3142 5400 or e-mail [email protected]. Other Standards and associated documents can also be viewed at www.rgsonline.co.uk.


http://www.rgsonline.co.uk/

mailto:[email protected]


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Contents

Section Description Page

Part 1 Purpose and Introduction 6 1.1 Purpose 6 1.2 Introduction 6 1.3 Approval and authorisation of this document 7

Part 2 General Requirements for Train Voice Radio Systems 8 2.1 Introduction 8 2.2 Installation 8

Part 3 Technical Requirements for the GSM-R Train Voice Radio 9 3.1 Introduction 9 3.2 Train voice radio software management 9 3.3 Driver only operation of passenger trains 9 3.4 Protection of phonebook entries 9 3.5 SIM card and network access arrangements 9 3.6 Journey registration using alphanumeric input 9 3.7 Pre-defined text messages 10 3.8 GB specific UUS1 tags 11 3.9 UUS1 message definitions: pre-defined text message 12 3.10 UUS1 message definitions: pre-defined text message acknowledge 13 3.11 UUS1 message definitions: network status logging 14 3.12 UUS1 message definitions: supplementary registration data 16 3.13 eMLPP for high-priority point-to-point call 17 3.14 Number format of phonebook 17 3.15 Speech quality subjective testing 17 3.16 Speech quality objective testing 17 3.17 Testing 18 3.18 EIRENE Call Type (CT) numbering as applied in GB 19 3.19 Unauthorised functional numbers 20 3.20 Train identity 20 3.21 Railway emergency call 20

Part 4 Operational Requirements for GSM-R Train Voice Radio 21 4.1 Introduction 21 4.2 SIM card and network access arrangements 21 4.3 Phonebook 21 4.4 Journey registration 21

Part 5 Technical Requirements for GSM-R Network 22 5.1 Introduction 22 5.2 Network software management 22 5.3 Journey registration 22 5.4 GB specific UUS1 tags 22 5.5 UUS1 message definitions: pre-defined text message 23 5.6 UUS1 message definitions: network status logging 23 5.7 UUS1 message definitions: pre-defined text message acknowledge 25 5.8 UUS1 message definitions: supplementary registration data 26 5.9 Enhanced Presentation of Functional Number 26 5.10 eMLPP for high-priority point-to-point call 26 5.11 SIM file definition 27 5.12 GB connectivity 28 5.13 Network coverage 28


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


5.14 Public emergency call 28 5.15 Railway emergency group calls 28 5.16 Testing 28 5.17 Positional information 28 5.18 Overview of EIRENE Call Type (CT) numbering as applied in GB 29 5.19 Signs 30 5.20 Driver only operation of passenger trains 30

Part 6 GSM-R Network Operational Requirements 31 6.1 Introduction 31 6.2 Alternative communications system 31 6.3 SIM card and network access arrangements 31

Part 7 Performance Requirements 32 7.1 Call success rates 32 7.2 Speech quality 32 7.3 Head code registration 33 7.4 Call set-up times 33

Part 8 National Radio Network (NRN) Requirements 34 8.1 Introduction 34 8.2 Regional controller initiated emergency broadcast call 34 8.3 Call set-up time performance 34 8.4 Electrical Control Room Operator (ECRO) calls 34 8.5 Shunting operation 34 8.6 System management 34

Part 9 Cab Secure Radio 35 9.1 Introduction 35 9.2 Requirement for use 35 9.3 Emergency calls 35 9.4 Call set-up time performance 35 9.5 Electrical Control Room Operator (ECRO) calls 35 9.6 System management 35 9.7 Driver only operation of passenger trains 36

Part 10 Application of this document 37 10.1 Application – infrastructure managers 37 10.2 Application – railway undertakings 38 10.3 Health and safety responsibilities 38

Appendices Appendix A.1 Algorithm for Converting Head Code to Train Running Number 39 Appendix A.2 Algorithm for Converting Train Running Number to Head Code 40 Appendix B Great Britain Connectivity Matrix 41 Definitions 47 Abbreviations and Acronyms 49

References 51

Tables Table 1 Incoming pre-defined text messages 11 Table 2 Outgoing pre-defined text messages 11 Table 3 Application of tags on the GB network 12 Table 4 Pre-defined text message definition numbers 13 Table 5 Definition of the Acknowledge byte 14 Table 6 Latitude coding 16


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Table 7 Longitude coding 16 Table 8 Functions and associated numbers 17 Table 9 CT3 UIN number format 19 Table 10 GB specific tags 23 Table 11 Pre-defined text message definition numbers 23 Table 12 Latitude coding 25 Table 13 Longitude coding 25 Table 14 Definition of the ‘Acknowledge’ byte 26 Table 15 eMLPP priorities and associated numbers 27 Table 16 SIM card file structure 27 Table 17 SIM card profile 27 Table 18 CT3 UIN number format 29 Table 19 Call success rates 32 Table 20 Speech quality for all voice call types 32 Table 21 Head code registration 33 Table 22 Call set-up times 33 Table 23 GB connectivity matrix 46


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Part 1 Purpose and Introduction

1.1 Purpose

1.1.1 This document mandates the technical requirements for the application of train voice radio systems using Global System for Mobile communications − Railway (GSM-R) or National Radio Network (NRN) or Cab Secure Radio (CSR). Specifically, this document defines interface requirements for the infrastructure manager (IM) and the railway undertakings (RUs).

1.1.2 This document excludes requirements for the Interim Voice Radio System (IVRS), GSM-R shunting radios, GSM-R general purpose radios and GSM-R operational radios (except where a GSM-R operational radio is used by train crew as a GSM-R train voice radio). It excludes use of GSM-R and NRN as data bearers, for example for the European Train Control System (ETCS) and Radio Electronic Token Block (RETB) respectively. It also excludes the manner in which cross-border issues are dealt with.

1.2 Introduction

1.2.1 Background

1.2.1.1 This document and its associated documents: GK/GN0694 issue one Guidance on Train Voice Radio Systems; RIS-0794-CCS issue one Rail Industry Standard for the GSM-R Train Voice Radio System; BR 1661 Train to Signalbox Radio System (Train Radio); BR 1845 Train to Signalbox Radio System (Fixed Equipment), and BR 1609 VHF Band III for the National Radio Network, set out the technical requirements to facilitate the use of train voice radio systems in Great Britain (GB).

1.2.1.2 This document and its associated documents GK/GN0694 and RIS-0794-CCS support the Technical Specification for Interoperability (TSI) relating to the Control, Command and Signalling (CCS) subsystem. The technical requirements that are set out in the TSI do not form part of this document.

1.2.1.3 The CCS TSI mandates through various related documents (for example, the Functional Requirements Specification / System Requirements Specification (FRS/SRS) and European Telecommunications Standards Institute (ETSI) Standards) technical requirements for a European-compliant digital train voice radio system (namely GSM-R).

1.2.2 Related requirements in other documents

1.2.2.1 The technical requirements for legacy radio (Cab Secure Radio (CSR) and National Radio Network (NRN)) that remain different from the GSM-R requirements are mandated to facilitate the continued use of the legacy train voice radio systems within GB. These requirements are set out in Parts 8 and 9 of this document. Copies of the Technical Specification for CSR (BR 1661 and BR 1845) and NRN (BR 1609) are available from www.rgsonline.co.uk.



RSSB of 51


GK/RT0094

Issue One

Date March 2013


1.2.2.2 The technical requirements for RETB are set out in GK/RT0054 issue one, and the technical requirements for ETCS are set out in the CCS TSI and RIS-0340-CCS issue one.

1.2.3 Supporting documents

1.2.3.1 The following Railway Group documents support this Railway Group Standard:

GK/GN0694 Guidance on Train Voice Radio Systems.

RIS-0794-CCS Rail Industry Standard for the GSM-R Train Voice Radio Systems.

1.3 Approval and authorisation of this document

1.3.1 The content of this document was approved by Control Command and Signalling (CCS) Standards Committee on 24 January 2013, and was supported by Traffic Operation and Management (TOM) Standards Committee on 16 January 2013.

1.3.2 This document was authorised by RSSB on 01 February 2013.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Part 2 General Requirements for Train Voice Radio Systems

2.1 Introduction

2.1.1 This part sets out the general requirements that the train voice radio system and infrastructure network have to supply.

2.2 Installation

2.2.1 Train voice radio installation

2.2.1.1 A train voice radio shall be operable from each cab that is required to be used as a driving cab of a train in service.

2.2.1.2 The train voice radio shall be compatible with the train voice radio system selected for trains using the route.

2.2.2 Infrastructure installation

2.2.2.1 The train voice radio fixed infrastructure shall be compatible with the train voice radio system selected for trains using the route.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Part 3 Technical Requirements for the GSM-R Train Voice Radio

3.1 Introduction

3.1.1 This part sets out the technical requirements for the GSM-R train voice radio.

3.2 Train voice radio software management

3.2.1 GSM-R train voice radio software updates shall not disrupt train operation while the train is in service.

3.3 Driver only operation of passenger trains

3.3.1 Train voice radios on trains that are to be operated as Driver Only Operation (Passenger) DOO(P) trains shall interface to the:

a) Driver Safety Device (DSD).

b) Public Address (PA).

3.3.2 The DSD alarm message shall provide location information.

3.3.3 The DSD alarm message shall be sent with priority Multi-Level Precedence and Pre-emption (eMLPP) 2.

3.4 Protection of phonebook entries

3.4.1 The GSM-R train voice radio shall not allow entries in phonebooks to be modified by GSM-R train voice radio users where the train voice radio has a called party look-up capability.

3.5 SIM card and network access arrangements

3.5.1 Only SIM cards configured in the train voice radio category shall be used in a GSM-R train voice radio.

3.6 Journey registration using alphanumeric input

3.6.1 If the GSM-R train voice radio is capable of accepting input of alphanumeric format GB train head codes and the GSM-R train voice radio is camped on the network, with network reference 234 13, it shall:

a) Translate an entered head code and location code into an eight digit numeric journey registration number using an algorithm, as set out in Appendix A.1, with the entered head code, to calculate the first five digits of the registration number.

b) Append the entered three digit location code to the calculated five digits, to form the journey registration number.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


c) Present a progress indication on the Human Machine Interface (HMI), which shall remain displayed until an Unstructured Supplementary Service Data (USSD) registration response code is received from the network to show journey registration has completed, or until a USSD journey registration response code is received from the network to show failure of registration, after the third attempt.

d) Provide specific instruction to the GSM-R train voice radio user in the progress indication to wait for the successful completion of the journey registration process.

e) Use the lowest numerical value of the three five digit numbers returned by the algorithm for the first journey registration attempt.

f) Use the second lowest of the three five digit numbers for a second journey registration attempt, only if the USSD request utilising the lowest numerical value train number returns a response code indicating that the number is a duplicate.

g) Use the highest numerical value of the three possible five digit numbers for a third journey registration attempt, only if the USSD request utilising the second lowest numerical value train number returns a response code indicating that the number is a duplicate.

h) On successful completion of journey registration of the leading driver functional number, the cab mobile shall automatically register the PA if configured for GSM-R.

i) Show on the HMI the entered head code, if successful, in completion of the USSD registration process.

j) Indicate failure to the user with information identifying that the attempt failed due to the journey registration number being a duplicate, if the USSD request utilising the highest numerical value train number returns a response code indicating that the number is a duplicate.

k) If the network does not respond or sends an error message, this journey registration failure shall be indicated to the user.

l) Accept and acknowledge the User-to-User Signalling 1 (UUS1) ‘supplementary registration data’ message from the network (if it is sent).

m) Not display the content of the UUS1 ‘supplementary registration data’.

3.7 Pre-defined text messages

3.7.1 Background

3.7.1.1 The specific pre-defined text message function provides the facility for text-based communications between, typically, the signaller and the GSM-R train voice radio, offering advantages in speed of operation, reduced driver workload and reduced signaller workload.

3.7.2 GB specific UUS1 tags

3.7.2.1 The requirements of 3.7.3, 3.7.4, and 3.8 to 3.12 shall only apply if a GSM-R train voice radio is capable of processing the GB specific UUS1 tags.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


3.7.2.2 Those GSM-R train voice radios, incapable of processing GB specific UUS1 tags, as set out in 3.8 to 3.12, shall:

a) Continue to operate normally following receipt of a GB specific tag.

b) Not present the contents of the UUS1 tags to the user.

c) Not acknowledge the GB specific UUS1 tags.

3.7.3 Incoming GB specific pre-defined text messages

3.7.3.1 The GSM-R train voice radio shall support the incoming pre-defined text messages set out in Table 1.

Message Purpose

Wait Sent by signaller in response to driver originated

‘Standing at signal’ message

Contact signaller Sent by signaller at any time to prompt driver to make a

voice call

Contact fixed

terminal

Sent by operator other than signaller, with a fixed

terminal to a GSM-R train voice radio user to prompt

user to make a voice call, when user is ready to make

the call

Table 1 Incoming pre-defined text messages

3.7.3.2 On receipt of a valid UUS1 message, the GSM-R train voice radio Human Machine Interface (HMI) shall automatically display the associated pre-defined text message and provide an audible indication.

3.7.4 Outgoing pre-defined text messages

3.7.4.1 The train voice radio shall support the outgoing pre-defined text message, as set out in Table 2.

Message Purpose

Standing at signal Sent by driver to inform signaller that train is waiting at a

signal

Table 2 Outgoing pre-defined text messages

3.7.4.2 If the outgoing message transaction is unsuccessful, the train voice radio shall provide a specific indication on its HMI to inform the user that the called terminal has not successfully received the message.

3.8 GB specific UUS1 tags

3.8.1 Background

3.8.1.1 The tag value identifies the type of message. Values in the range 128 to 255 are reserved for national use.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


3.8.2 Tag definitions

3.8.2.1 The GB specific UUS1 messages shall use the UUIE format specified by the EIRENE System Requirements Specification.

3.8.2.2 The tags set out in Table 3 shall be used for GB specific applications.

Tag Name Originator Recipient Purpose

National

128 Pre-defined text message

GSM-R train voice radio

Network Presentation of pre-defined text messages (see tag 133)

132 Network status logging


Designated terminal

Coverage loss and recovery flag use

133 Pre-defined text message acknowledge


Network Acknowledgement of received pre-defined text messages (see tag 128)

134 Supplementary registration data

Network GSM-R train voice radio

Presentation of alphanumeric head code during journey registration (see tag 135)

135 Supplementary registration data acknowledge


Network Acknowledgement of receipt of journey registration head code (see tag 134)

Table 3 Application of tags on the GB network

3.8.3 Exceptional procedures or unsuccessful outcome for outgoing messages

3.8.3.1 The outgoing message shall not include unassigned or reserved tags.

3.9 UUS1 message definitions: pre-defined text message

3.9.1 Application

3.9.1.1 Pre-defined text messages shall be received when sent by the network or shall be sent to the network when initiated by the train voice radio user.

3.9.2 UUS1 message format

3.9.2.1 This UUS1 message shall consist of tag 05 followed by tag 128.

3.9.2.2 Tag 128 shall be in the format set out below:

Byte 1

Byte 2

Message number

Tag representing Pre-defined Message = '128'1 0 0 0 0 0 0 0

Byte 3

Pre-defined

MessageMessage Number length = 1

0 0 0 0 0 0 0 1

8 7 6 5 4 3 2 1


RSSB of 51


GK/RT0094

Issue One

Date March 2013


3.9.3 Message number definitions

3.9.3.1 The definitions of message numbers shall be as set out in Table 4.

Message

number field

Text message name Originator

1 Standing at signal Train voice radio

2 Wait Network

5 Contact signaller Network

7 Contact fixed terminal Network

Table 4 Pre-defined text message definition numbers

3.10 UUS1 message definitions: pre-defined text message acknowledge

3.10.1 Application

3.10.1.1 A ‘pre-defined text message acknowledge shall be sent by the train voice radio on receipt of a pre-defined text message.

3.10.2 Format



Byte 1

Byte 2

Message Number Byte 3

Pre-defined message

Acknowledge

Acknowledge Byte 4

Message Number Acknowledge length = 20 0 0 0 0 0 1 0

Tag representing Pre-defined Message Acknowledge = '133'1 0 0 0 0 1 0 1

8 7 6 5 4 3 2 1

3.10.2.3 The Message Number byte shall be the number set out in Table 4.

3.10.2.4 The Acknowledge byte shall be as set out in Table 5.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Acknowledge field

Name Meaning

0 Delivered Destination available to receive pre-defined text message and message

number recognised by recipient. Message format correct and length

correct

1 Not delivered Destination not available or not in correct state to receive UUS1 pre-

defined message

2 Invalid format Message format or length incorrect, or sender’s functional number absent

3 Undefined message Message number not recognised by the recipient

Table 5 Definition of the Acknowledge byte

3.11 UUS1 message definitions: network status logging

3.11.1 Application

3.11.1.1 If the GSM-R train voice radio is capable of supporting network diagnostic information, when the network is recovered after a period of loss, the GSM-R train voice radio shall send diagnostic information recording the GPS location, date and time when the network was lost and regained.


3.11.2.1 This UUS1 message shall consist of tag 132.



RSSB of 51


GK/RT0094

Issue One

Date March 2013



3.11.3.1 UTC Time format shall be the time in seconds since midnight (00:00:00), January 1 1970.

3.11.3.2 A UTC Value of 0 shall indicate no valid time is available.

3.11.3.3 The ‘valid bit’ in the location is used to indicate if the location is valid; 1 = Valid, 0 = Invalid.

3.11.3.4 The location information (latitude and longitude) is formatted as set out in Table 6 and Table 7.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Units Range Number of bits Example

Degrees 0-90 7 89

Minutes 0-59 6 59’

Hundredths of seconds

0-5999 13 59.99”

Direction S = 0 1 N

N = 1

Total 27

Table 6 Latitude coding


Degrees 0-180 8 179

Minutes 0-59 6 59’


0-5999 13 59.99”

Direction E = 0 1 E

W = 1

Total 28

Table 7 Longitude coding

3.11.3.5 The Stock Number digits shall be in EIRENE engine number format.

3.12 UUS1 message definitions: supplementary registration data

3.12.1 Application

3.12.1.1 On successful completion of the journey registration process, the GSM-R train voice radio shall be ready to accept the Supplementary Registration Data UUS1 message.

3.12.2 Format

3.12.2.1 This UUS1 message shall consist of tag 134 only.


Head Code

Byte 1Tag representing Supplementary Registration Data = '134'1 0 0 0 0 1 1 0

8 7 6 5 4 3 2 1

ASCII Head Code First Character Byte 3

ASCII Head Code Second Character Byte 4

Byte 5ASCII Head Code Third Character

ASCII Head Code Fourth Character Byte 6

Byte 1Supplementary Registration Data length = 40 0 0 0 0 1 00

3.12.2.3 The head code characters shall be alphanumeric ASCII characters.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


3.13 eMLPP for high-priority point-to-point call

3.13.1 Designated call priorities

3.13.1.1 The eMLPP priority designations and numbers for the functions set out in this document shall be as set out in Table 8.

Function eMLPP priority Associated number

Incoming high-priority point-

to-point voice call

Set by network CT2/CT3

Outgoing high-priority point-

to-point voice call

2 GBUSC

Table 8 Functions and associated numbers

3.14 Number format of phonebook

3.14.1 The International Telecommunication Union Telephone Standardisation Sector (ITU-T) E.164 international number format shall be used for all GSM-R train voice radio phonebook entries with the exception of CT1 location dependent numbers.

3.15 Speech quality subjective testing

3.15.1 An evaluation shall be undertaken of voice quality from the GSM-R train voice radio on the GB GSM-R network, such that the voice quality is considered acceptable by an independent expert witness.

3.16 Speech quality objective testing

3.16.1 Test exemption

3.16.1.1 The train voice radio shall be tested objectively, as set out in 3.16.2 to 3.16.4, unless it has been previously type-tested and certified for operational use.

3.16.2 Transmitted speech quality requirements

3.16.2.1 For speech originated from the handset microphone, the GSM-R train voice radio shall transmit speech that is received with an average TOSQA Mean Opinion Score (TMOS) of no less than 3.7.

3.16.2.2 This TMOS requirement shall be achieved for all call types involving speech originated from the GSM-R train voice radio.

3.16.3 Received speech quality requirements

3.16.3.1 Two cases shall be assessed for received speech quality at the GSM-R train voice radio:

a) Case one: Speech output via the loudspeaker only.

b) Case two: Speech output via the handset earpiece only.

3.16.3.2 For all call types, the GSM-R train voice radio shall provide an average received speech quality TMOS of no less than 3.3.

3.16.4 General requirements for speech quality measurements

3.16.4.1 All measurements for speech quality shall be made using the TOSQA2001 algorithm.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


3.16.4.2 The test set-up shall be calibrated and equalised as prescribed by TOSQA2001.

3.16.4.3 A Head And Torso Simulator (HATS) as set out in ITU-T Recommendation P.58 shall be used to provide the acoustical interface to the GSM-R train voice radio.

3.16.4.4 The HATS shall be equipped with an artificial mouth that conforms to ITU-T Recommendation P.58.

3.16.4.5 The HATS shall be equipped with an artificial ear that conforms to ITU-T Recommendation P.57 artificial ear type 3.4.

3.16.4.6 All speech samples shall fulfil the requirements of ITU-T, P.800 recommendations.

3.16.4.7 All measurements shall be made in an anechoic chamber.

3.17 Testing

3.17.1 The railway undertaking (RU) shall, in consultation with the infrastructure manager (IM), organise compatibility tests to demonstrate that the system behaves as requested, including the following:

a) Working with the IM supplied SIM cards.

b) Basic voice calls.

c) Railway emergency calls.

d) High-priority point-to-point calls.

e) Pre-defined text messages.

f) Journey registration and deregistration.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


3.18 EIRENE Call Type (CT) numbering as applied in GB

3.18.1 GB format for Call Type 3 (CT3) User Identifier Number (UIN)

3.18.1.1 The format of a CT3 UIN for traction units with home network reference 234 13 shall be in accordance with the requirements set out in Table 9.

CT3 UIN content (total eight digits)

Type of

traction unit

number to

be coded as

UIN

Digit#1

(cab

differen-

tiator)

Digit#2

(train

differen-

tiator)

Digit#3 Digit#4 Digits#5 to

8

Four digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘4’ ‘4’ ‘4’ The four

digit

vehicle /

unit

number

Five digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘5’ ‘0’ for on

track

machines

with five

digit

numbers

prefixed by

‘DR’

‘5’ for

other

vehicles

and units

First digit

of the five

digit

vehicle /

unit

number

Remaining

digits of

the five

digit

vehicle /

unit

number

Six digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘6’ First digit

of the six

digit

vehicle /

unit

number

Second

digit of the

six digit

vehicle /

unit

number

Remaining

digits of

the six

digit

vehicle /

unit

number

Seven digit

vehicle / unit

number

‘3’ for Cab

A

‘4’ for Cab

B

First digit

of the

seven digit

vehicle /

unit

number

Second

digit of the

seven digit

vehicle /

unit

number

Third digit

of the

seven digit

vehicle /

unit

number

Remaining

digits of

the seven

digit

vehicle /

unit

number

Table 9 CT3 UIN number format


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


3.18.1.2 In cases where a CT3 or CT4 number could be used, CT3 numbers shall be used.

3.19 Unauthorised functional numbers

3.19.1 The train voice radio shall prevent certain types of users from registering functional numbers that they are not authorised to use.

3.20 Train identity

3.20.1 Correlation between train identity or stock number and radio number shall be provided to allow the network user to be shown this information.

3.21 Railway emergency call

3.21.1 It shall be possible for users receiving an emergency call to speak to all others responding to the emergency call.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Part 4 Operational Requirements for GSM-R Train Voice Radio

4.1 Introduction

4.1.1 This part sets out the operational requirements for the RUs which are considered necessary for operational compatibility with the GB network.


4.2.1 The RU shall make a request to the issuing IM to remotely disable SIM cards, when they are no longer required.

4.2.2 The RU shall inform the issuing IM that SIM cards have been detected as having been used for a purpose for which they are not intended, or have been lost, stolen or damaged.

4.2.3 The RU shall, on receipt of confirmation of SIM cards being disabled, return those SIM cards to the issuing IM in a secure manner.

4.3 Phonebook

4.3.1 The RU shall supply any additional or changed phone numbers it requires to the IM according to an agreed plan.

4.4 Journey registration

4.4.1 The RU shall have a process in place for its drivers to attempt journey registration of the GSM-R train voice radio.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Part 5 Technical Requirements for GSM-R Network

5.1 Introduction

5.1.1 This part sets out technical requirements for the GSM-R network.

5.2 Network software management

5.2.1 GSM-R network software updates shall not disrupt train operation.

5.3 Journey registration

5.3.1 Where an eight digit numeric journey registration is provided, the head code shall be determined using the algorithm set out in Appendix A.2.

5.3.2 On entry of an alphanumeric format GB head code, the signalling control centre display shall show the first five digits of the journey registration number returned from the algorithm set out in Appendix A.1.

5.3.3 The network shall permit multiple journey registrations where there are different functional numbers and the location code is a wild card number of 99x.

5.4 GB specific UUS1 tags

5.4.1 Background

5.4.1.1 The tag value identifies the type of message. Values in the range 128 to 255 are reserved for national use.

5.4.2 Tag definitions

5.4.2.1 The Great Britain specific UUS1 messages shall use the UUIE format specified by the EIRENE System Requirements Specification.

5.4.2.2 The tags set out in Table 10 shall be used for GB specific applications.

Tag Name Originator Recipient Use

National

128 Pre-defined

text message

Train voice

radio

Network Presentation of

pre-defined text

messages (see tag 133) Network Train voice

radio

132 Network status

logging

Train voice

radio

Designated

terminal

Coverage loss and

recovery logging

133 Pre-defined

text message

acknowledge

Train voice

radio

Network Acknowledgement of

received pre-defined text

messages (see tag 128) Network Train voice

radio

134 Supplementary

registration

data

Network Train voice

radio

Presentation of

alphanumeric ASCII head

code


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Tag Name Originator Recipient Use

National

135 Supplementary

registration

data

acknowledge

Train voice

radio

Network Acknowledgement of

receipt of journey

registration head code

(see tag 134)

Table 10 GB specific tags

5.4.2.3 Use of Tag 132 shall not disrupt train operation.

5.5 UUS1 message definitions: pre-defined text message

5.5.1 Application

5.5.1.1 Pre-defined text messages shall be sent to the GSM-R train voice radio and received from the GSM-R train voice radio when sent by the driver.




Byte 1

Byte 2

Message number

Tag representing Pre-defined Message = '128'1 0 0 0 0 0 0 0

Byte 3

Pre-defined

MessageMessage Number length = 1

0 0 0 0 0 0 0 1

8 7 6 5 4 3 2 1


5.5.3.1 The definitions of message numbers shall be as set out in Table 11.

Message

number field

Text message name Originator

1 Standing at signal GSM-R train

voice radio

2 Wait Network

3 Stop acknowledge GSM-R train

voice radio

5 Contact signaller Network

7 Contact fixed terminal Network

Table 11 Pre-defined text message definition numbers

5.6 UUS1 message definitions: network status logging

5.6.1 Application

5.6.1.1 When the network is recovered after a period of loss, the GSM-R train voice radio can send diagnostic information recording the GPS location, date and time when the network was lost and regained.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013



5.6.2.1 This UUS1 message shall consist of tag 132.



5.6.3.1 UTC Time format shall be the time in seconds since midnight (00:00:00), January 1 1970.

5.6.3.2 A UTC Value of 0 shall indicate no valid time is available.

5.6.3.3 The ‘valid bit’ in the location is used to indicate if the location is valid; 1 = Valid, 0 = Invalid.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


5.6.3.4 The location information (latitude and longitude) is formatted as set out in Table 12 and Table 13.


Degrees 0-90 7 89

Minutes 0-59 6 59’


0-5999 13 59.99”

Direction S = 0 1 N

N = 1

Total 27

Table 12 Latitude coding


Degrees 0-180 8 179

Minutes 0-59 6 59’


0-5999 13 59.99”

Direction E = 0 1 E

W = 1

Total 28

Table 13 Longitude coding

5.6.3.5 The Stock Number digits shall be in EIRENE engine number format.

5.7 UUS1 message definitions: pre-defined text message acknowledge

5.7.1 Application

5.7.1.1 A pre-defined text message acknowledge, shall be sent by the network on receipt of a pre-defined text message.

5.7.2 Format



Byte 1

Byte 2

Message Number Byte 3

Pre-defined message

Acknowledge

Acknowledge Byte 4

Message Number Acknowledge length = 20 0 0 0 0 0 1 0

Tag representing Pre-defined Message Acknowledge = '133'1 0 0 0 0 1 0 1

8 7 6 5 4 3 2 1

5.7.2.3 The Message Number byte shall be the number set out in Table 11.

5.7.2.4 The Acknowledge byte shall be defined as set out in Table 14.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Acknowledge

field

Name Meaning

0 Delivered Destination available to receive pre-

defined text message and message

number recognised by recipient.

Message format correct and length

correct

1 Not delivered Destination not available or not in correct

state to receive UUS1 pre-defined

message

2 Invalid format Message format or length incorrect, or

sender’s functional number absent

3 Undefined message Message number not recognised by the

recipient

Table 14 Definition of the ‘Acknowledge’ byte

5.8 UUS1 message definitions: supplementary registration data

5.8.1 Application

5.8.1.1 The supplementary registration data message shall be sent by the network when an eight digit journey registration is successful.

5.8.2 Format

5.8.2.1 This UUS1 message shall consist of tag 134 only.

5.8.2.2 Tag 134 shall be in the format as set out below:

Head Code

Byte 1Tag representing Supplementary Registration Data = '134'1 0 0 0 0 1 1 0

8 7 6 5 4 3 2 1

ASCII Head Code First Character Byte 3

ASCII Head Code Second Character Byte 4

Byte 5ASCII Head Code Third Character

ASCII Head Code Fourth Character Byte 6

Byte 1Supplementary Registration Data length = 40 0 0 0 0 1 00

5.8.2.3 The head code characters shall be alphanumeric ASCII characters.

5.9 Enhanced Presentation of Functional Number

5.9.1 The network shall send Enhanced Presentation of Functional Number information with the identity of the sender in tag 9.

5.10 eMLPP for high-priority point-to-point call

5.10.1 Designated call priorities

5.10.1.1 The eMLPP priority designations and associated numbers for the functions set out in this document shall be as set out in Table 15.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Function eMLPP priority Associated number

Incoming high-priority point-

to-point voice call

Set by GSM-R

train voice radio

N/A

Outgoing high-priority point-

to-point voice call

2 CT2/CT3

Table 15 eMLPP priorities and associated numbers

5.11.1.2 The length of the alpha identifier shall be 14 characters in the SDN file.

5.11.2 SIM card profile

5.11.2.1 The GB GSM-R train voice radio SIM card profile shall include the elementary file (EF) information, as set out in Table 17.

Table 17 SIM card profile

5.11.3 User identity

5.11.3.1 The SIM cards shall be configured in such a manner that users cannot withhold their identity.

5.11 SIM file definition

5.11.1 SIM card access conditions and file structure

5.11.1.1 The SIM card file structure shall be as set out in Table 16.

DF TELECOM (7F10):

EF Name File type Maximum

number of

records

6F49 SDN linear 20

Table 16 SIM card file structure

Name Description Values

SDN Record 11 Outgoing high-priority point-to-point

voice call

GBUSC 2 1119

SDN Record 12 Outgoing pre-defined text message

‘Standing at signal’

GBSAS 3 1801

SDN Record 14 GB DSD mode GBDSD 2 1700

SDN Record 16 GB statistics for network status logging GBSTC 4

74800260


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


5.12 GB connectivity

5.12.1 The network shall be configured as set out in Appendix B.

5.13 Network coverage

5.13.1 The level of coverage shall be at least 95% of the time over 95% of the designated coverage area for a radio installed in a vehicle with an external antenna.

5.14 Public emergency call

5.14.1 Public emergency call numbers (‘999’ and ‘112’) shall be directed to the railway telephone system emergency operator.

5.14.2 Following connection of the emergency voice call, the regional controller shall have access to a speech connection in order to pass information.

5.15 Railway emergency group calls

5.15.1 Incoming emergency calls

5.15.1.1 During emergency calls, speech shall be possible to allow only one signaller receiving the warning tone to give information.

5.15.1.2 Speech shall be possible to allow a controller receiving the warning tone to give information.

5.15.1.3 Speech shall be possible to allow train voice radio users receiving the warning tone to give information.

5.15.2 Handling of multiple emergency calls

5.15.2.1 The IM, in consultation with the RUs, shall define how the train voice radio system handles multiple emergency calls made from train voice radios in the same or overlapping areas.

5.16 Testing

5.16.1 The IM shall, in consultation with the RU, organise compatibility tests to demonstrate that the system behaves as required, including the following:

a) Working with the IM supplied SIM cards.

b) Basic voice calls, including echo test calls.

c) Railway emergency calls.

d) High-priority point-to-point calls.

e) Pre-defined text messages.

f) Journey registration and deregistration.

5.17 Positional information

5.17.1 Where available, the network shall utilise ground-based signalling positional information for enhanced location dependent addressing.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


5.18 Overview of EIRENE Call Type (CT) numbering as applied in GB

5.18.1 GB format for Call Type 3 (CT3) User Identifier Number (UIN)

5.18.1.1 The format of CT3 UIN for traction units with home network reference 234 13 shall be in accordance with the requirements set out in Table 18.

CT3 UIN content (total eight digits)

Type of

traction

unit

number to

be coded

as UIN

Digit#1

(cab

differen-

tiator)

Digit#2

(train

differen-

tiator)

Digit#3 Digit#4 Digits#5 to

8

Four digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘4’ ‘4’ ‘4’ The four

digit

vehicle/

unit

number

Five digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘5’ ‘0’ for on

track

machines

with five

digit

numbers

prefixed by

‘DR’

‘5’ for

other

vehicles

and units

First digit

of the five

digit

vehicle /

unit

number

Remaining

digits of

the five

digit

vehicle /

unit

number

Six digit

vehicle / unit

number

‘1’ for Cab

A

‘2’ for Cab

B

‘6’ First digit

of the six

digit

vehicle /

unit

number

Second

digit of the

six digit

vehicle /

unit

number

Remaining

digits of

the six

digit

vehicle /

unit

number

Seven digit

vehicle / unit

number

‘3’ for Cab

A

‘4’ for Cab

B

First digit

of the

seven digit

vehicle /

unit

number

Second

digit of the

seven digit

vehicle /

unit

number

Third digit

of the

seven digit

vehicle/

unit

number

Remaining

digits of

the seven

digit

vehicle /

unit

number

Table 18 CT3 UIN number format


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


5.19 Signs

5.19.1 A consistent policy for lineside signs shall be developed to support the train voice radio system.


5.20.1 In signalling control centres which cover routes where train voice radios are to be operated as DOO(P) trains, access shall be given to call the Public Address (PA) on those trains.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Part 6 GSM-R Network Operational Requirements

6.1 Introduction

6.1.1 This part sets out the operational requirements which are considered necessary for operational compatibility with the GB network.

6.2 Alternative communications system

6.2.1 The IM shall provide, within the appropriate operating publications or late notices that are issued to staff, details of permitted arrangements for alternative communications during network failures and planned maintenance activities.


6.3.1 SIM card security

6.3.1.1 The issuing IM shall, when technical misuse of a SIM card is detected, take such actions necessary to control the risk arising from such misuse.

6.3.1.2 The issuing IM shall, where technical misuse of a SIM card is detected, inform the responsible RU of the technical misuse and the remedial actions that have been taken.

6.3.1.3 The issuing IM shall remotely disable SIM cards, when informed by the RU that those SIM cards are no longer required or have been detected as having been used for a purpose for which they were not intended, or have been lost, stolen or damaged.

6.3.1.4 The issuing IM shall confirm to the RU that SIM cards have been disabled, in order that those SIM cards can be returned in a secure manner by the RU.

6.3.2 Phonebook

6.3.2.1 The IM shall modify the phonebook when it requires a change.

6.3.2.2 The IM shall provide the RU with the amended phonebook for uploading into the GSM-R train voice radio.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Part 7 Performance Requirements

7.1 Call success rates

7.1.1 Call success rates shall be in accordance with the requirements set out in Table 19.

7.1.2 Measurements shall be made under mobile conditions to be representative of operational conditions.

KPI definition Minimum

performance

level

Notes

Railway emergency group

calls successfully

connected and completed

(for fixed-to-mobile and

mobile-to-fixed calls).

98%

Call ‘successfully connected’ is

defined as a call which is

successfully established between

the user terminals in question (in

other words, the call reaches the

called terminal).

Call ‘completed’ is defined as the

established call being held

continuously for a period of two

minutes and then terminated as a

normal release.

Network originated high

priority point-to-point calls

and train voice radio

originated high priority

point-to-point calls

connected and completed.

98%

All other calls, not covered

by the above, successfully

connected and completed.

97%

Table 19 Call success rates

7.2 Speech quality

7.2.1 The speech quality for all call types shall be in accordance with the requirements set out in Table 20.

KPI definition Minimum performance level

Notes

Speech quality expressed

as Mean Opinion Score

(MOS) for successfully

established calls.

MOS >=3 for

99% of

speech

samples.

MOS value of 3 represents the

threshold for acceptable speech

quality.

Table 20 Speech quality for all voice call types


RSSB of 51


GK/RT0094

Issue One

Date March 2013


7.3 Head code registration

7.3.1 If the GSM-R train voice radio is capable of accepting input of alphanumeric format GB train head codes, the head code registration shall be in accordance with the requirements set out in Table 21.


performance

level

Notes

Time to complete mobile

to network transaction for

UK alphanumeric head

code registration.

95% within

30s Includes unsuccessful call

attempts.

Table 21 Head code registration

7.4 Call set-up times

7.4.1 The performance for call set-up times shall be in accordance with the requirements set out in Table 22.

7.4.2 Measurements shall be based on the set-up time from the moment the caller operates the call request to the point that an alerting indication is provided at the called terminal.

7.4.3 The required call set-up times shall be achieved in at least 95% of cases.

7.4.4 The handover success rate should be at least 99.5% over train routes under design load conditions (as given in [GSM 03.05]).


performance

level

Notes

All operational mobile-to-

fixed calls except railway

emergency calls.

<5s

Including urgent point to-point calls.

All operational fixed-to-

mobile calls except

railway emergency calls.

<7s

All operational mobile-to-

mobile calls except group

calls between drivers in

the same area.

<10s

All low priority calls. <10s

Table 22 Call set-up times


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Part 8 National Radio Network (NRN) Requirements

8.1 Introduction

8.1.1 This part sets out the requirements that the train voice radio infrastructure network has to supply, being achieved through the legacy radio system pertaining to BR 1609, which is available from www.rgsonline.co.uk.

8.2 Regional controller initiated emergency broadcast call

8.2.1 The train voice radio system shall enable an emergency voice call to be made by a regional controller.

8.2.2 Following connection of the outgoing railway emergency group call, the regional controller shall have access to a speech connection in order to pass on information.

8.2.3 Recipients of the railway emergency group call shall include all drivers of trains in service in a pre-defined geographic area wholly or partly within the regional controller’s area of responsibility.

8.3 Call set-up time performance

8.3.1 For the remaining operational life of the NRN, periodic testing shall take place in co-operation with the RUs to determine that the call set-up time performance is not degrading to an unacceptable level.

8.4 Electrical Control Room Operator (ECRO) calls

8.4.1 The train voice radio system shall enable the driver to make a two-way non-emergency voice call to the ECRO responsible for that train within the ECRO’s area of responsibility.

8.4.2 The call shall be capable of being initiated by the driver, following a small number of key presses.

8.5 Shunting operation

8.5.1 Where the train voice radio system is to be used in conjunction with handheld shunting mobiles to support shunting operations, then the train voice radio system shall enable continuous communications to and from a shunter.

8.6 System management

8.6.1 Software and hardware updates shall be performed in a controlled fashion and in particular ensure that different system elements are utilising compatible software and hardware versions.



RSSB of 51


GK/RT0094

Issue One

Date March 2013


Part 9 Cab Secure Radio

9.1 Introduction

9.1.1 This part sets out the requirements that the train voice radio infrastructure network has to supply, being achieved through the legacy radio system pertaining to the Cab Secure Radio System BR 1661 issue D (March 1990) and BR 1845 issue H (April 1991). The CSR system technical specifications BR 1661 issue D (March 1990) and BR 1845 issue H (April 1991) are available from www.rgsonline.co.uk

9.2 Requirement for use

9.2.1 Controller’s terminals

9.2.1.1 The controls of the signaller’s and the regional controller’s terminals shall be appropriately protected against inadvertent or accidental use, especially with regard to the emergency call function.

9.3 Emergency calls

9.3.1 Recipients of emergency calls

9.3.1.1 Recipients of the emergency voice call shall also include all drivers of trains in service in a pre-defined geographic area, which is based on the location of the train.

9.3.2 Handling of multiple emergency calls

9.3.2.1 The IM, in consultation with the RUs, shall define how the train voice radio system handles multiple emergency calls made from train voice radios in the same or overlapping areas.

9.4 Call set-up time performance

9.4.1 For the remaining operational life of CSR, periodic testing shall take place in co-operation with the RUs to determine that the call set-up time performance is not degrading to an unacceptable level.

9.5 Electrical Control Room Operator (ECRO) calls

9.5.1 The train voice radio system shall enable the driver to make a two-way non-emergency voice call to the ECRO responsible for the current location of the train, via a signaller responsible for that area, if required.

9.6 System management

9.6.1 Software and hardware updates shall be performed in a controlled fashion and in particular ensure that different system elements are utilising compatible software and hardware versions.



of 51 RSSB


GK/RT0094

Issue One

Date March 2013



9.7.1 Train voice radios on trains that are to be operated as DOO(P) trains shall interface to the:

a) Driver Safety Device (DSD).

b) Public Address (PA).


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Part 10 Application of this document

10.1 Application – infrastructure managers

10.1.1 Scope

10.1.1.1 The requirements of this document apply to all work that affects the application of the train voice radio system networks on the managed infrastructure, whether new or alteration.

10.1.1.2 It is permissible for the infrastructure manager to designate specific infrastructure projects, ongoing when this document comes into force, for which compliance with the requirements of this document (applicable to the design, construction and commissioning of new or altered infrastructure) is not mandatory. When designating such projects, the infrastructure manager shall consider:

a) Its responsibilities under its current safety authorisation.

b) The stage reached by the project at the time this document comes into force (for example, approval in principle).

c) Whether compliance is necessary to ensure compatibility with other parts of the infrastructure.

d) Whether compliance is necessary to facilitate safe interworking having regard to changes to related requirements mandated on another infrastructure manager or a railway undertaking.

e) The economic impact of compliance, but subject to its current safety authorisation in relation to the infrastructure in question.

10.1.1.3 Action to bring existing train voice radio into compliance with the requirements of this document is not required.

10.1.1.4 Where GSM-R is installed on a route which is not required to be compliant with the CCS TSI, then the CCS TSI shall be applied with this document.

10.1.2 Exclusions from scope

10.1.2.1 The requirements set out in Parts 3 and 4 do not apply to infrastructure managers.

10.1.2.2 Where the route is required to be compliant with the CCS TSI, Part 2 does not apply.

10.1.3 General compliance date for infrastructure managers

10.1.3.1 This Railway Group Standard comes into force and is to be complied with from 01 June 2013.

10.1.3.2 After the compliance dates or the date by which compliance is achieved if earlier, infrastructure managers are to maintain compliance with the requirements set out in this Railway Group Standard. Where it is considered not reasonably practicable to comply with the requirements, authorisation not to comply should be sought in accordance with the Railway Group Standards Code.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


10.1.4 Exceptions to general compliance date

10.1.4.1 There are no exceptions to the general compliance date specified in 10.1.3 for infrastructure managers.

10.2 Application – railway undertakings

10.2.1 Scope

10.2.1.1 The requirements of this document apply to all new equipment used for the application of train voice radio systems.

10.2.1.2 Action to bring existing train voice radio systems into compliance with the requirements of this document is not required.

10.2.1.3 Where trains are to be used over routes which are not required to be compliant with the CCS TSI, and GSM-R is to be implemented, then the CCS TSI shall be applied with this document.

10.2.2 Exclusions from scope

10.2.2.1 The requirements set out in Parts 5 and 6 do not apply to railway undertakings.

10.2.3 General compliance date for railway undertakings

10.2.3.1 This Railway Group Standard comes into force and is to be complied with from 01 June 2013.

10.2.3.2 After the compliance dates or the date by which compliance is achieved if earlier, railway undertakings are to maintain compliance with the requirements set out in this Railway Group Standard. Where it is considered not reasonably practicable to comply with the requirements, authorisation not to comply should be sought in accordance with the Railway Group Standards Code.

10.2.4 Exceptions to general compliance date

10.2.4.1 There are no exceptions to the general compliance date specified in 10.2.3 for railway undertakings.

10.3 Health and safety responsibilities

10.3.1 Users of documents published by RSSB are reminded of the need to consider their own responsibilities to ensure health and safety at work and their own duties under health and safety legislation. RSSB does not warrant that compliance with all or any documents published by RSSB is sufficient in itself to ensure safe systems of work or operation or to satisfy such responsibilities or duties.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Appendix A.1 Algorithm for Converting Head Code to Train Running Number

The content of this appendix is mandatory

A.1.1 The first four characters of the alphanumeric train running number N1AN2N3 are

first converted to a decimal number P by the formula:

PM = 27000.M + 2700.N1 + 100.n(A) + 10.N2 + N3

Where n(A) maps the upper case alphabet to numbers in the range 0-25, for example A=0, B=1 etc and M is 0, 1 or 2.

A.1.2 Initially M shall be 0 and the values 1 and 2 can be used for M to generate alternative numbers to resolve a conflict with another train having the same alphanumeric number.

As a result of applying the formula, P is in the range 0 to 80899 inclusive.

A.1.3 A five-digit number, Q, is calculated by the following formula:

QM = (25007.PM)mod89989

To avoid potential confusion and incorrect use, the numeric value used for journey registration does not have an obvious relationship with the alphanumeric train running number. The encryption used is a simple linear mapping module 89989 which, although it is not a strong encryption in the cryptographic sense, is adequate to hide the relationship to the train running number to a casual viewer.

This calculation can be carried out using 32 bit arithmetic, which facilitates simple implementation on standard microprocessor hardware.

The result of this calculation, Q, is a five digit decimal number between 0 and 89988 inclusive.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Appendix A.2 Algorithm for Converting Train Running Number to Head Code

The content of this appendix is mandatory

A.2.1 It is necessary to calculate the alphanumeric number from the five digit number Q, which forms the first part of the CT-2 train running number as follows:

The numbers B, B' and C, C' are chosen such that:

(B.B')mod 89989 = 1, (C+C')mod 89989 = 0

This gives B' = 27842, C' = 0

A.2.2 P is then calculated using the equation:

P = (B'.Q + C')mod 89989

P must be a value between 0 and 80999 if the original value was of the form NANN.

A.2.3 The values N1, N2, A and N3 and M are found by successively dividing P by 10,10, 27 and 10:

P' = P/10, N1 = (P)mod10

P" = P' /10, N2 = (P')mod 10

P''' = P''/27, n(A) = (P'')mod 27

M= P'''/10, N3 = (P''')mod 10

The value of A is found using the simple mapping 0A, 1B, 2C …


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Appendix B Great Britain Connectivity Matrix

The content of this appendix is mandatory.

The train voice radio system communications connectivity shall be as set out in the following table:

Key ─ Y: Call permitted; Blank: Call not permitted

Initiator Recipient

Fixed terminals Train Voice

Radio (TVR)

Fixed extensions Fixed terminals Train Voice

Radio (TVR)

Fixed extensions

Description Priority

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes

Fixed terminal calls TVR

(PTP CT2) 3 Y Y Y


(PTP CT3) 3 Y Y Y Y Y Y


(PTP CT8) 3 Y Y Y Y Y Y

Fixed terminal calls Extn

(PTP CT9 & 0) 4 Y Y Y Y Y Y

Fixed terminal calls Extn

[999/112] (PTP CT9) 2 Y Y Y Y Y

Priority only applies to

network portion of call


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Initiator Recipient


Radio (TVR)


Radio (TVR)

Fixed extensions


Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes


PA (PTP CT2) 3 Y Y Y

Fixed terminal calls fixed

terminal (PTP CT7) 3 Y Y Y Y Y Y Y Y

Fixed terminal calls fixed

terminal (PTP CT8) 3 Y Y Y Y Y Y Y Y


[high priority] (PTP CT2) 2 Y

Y

Includes calling by head

code. Only CT2 numbers

in train list can be called.

Signaller is only terminal

with a train list


[high priority] (PTP CT3) 2 Y

Y Y

TVR calls fixed terminal

(PTP CT1) 3

Y Y Y

TVR calls route

control/ECRO [menu] [PTP

CT1] 3

Y Y Y Y Y


[phonebook] (PTP CT7) 3

Y Y Y Y Y

TVR configured to assign

priority 3 to CT7 calls from

phonebook


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Initiator Recipient


Radio (TVR)


Radio (TVR)

Fixed extensions


Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ng

ineerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes


[dialled] (PTP CT7) 4

Y Y Y Y Y Y


(PTP CT8) 4

Y Y Y Y Y Y

TVR calls Extn (PTP CT9 &

0) 4

Y Y

Y

Y

Subject to barring

TVR calls Extn [999/112]

(PTP CT9) 2

Y Y

Y

TVR calls TVR (PTP CT2) 3

#1

Could be implemented using

different FCs in Access

Matrix if required. #1Calls

from driver 1 to driver 2

registered to the same

functional number shall be

permitted

TVR calls TVR (PTP CT3) Barred by Access Matrix

TVR calls TVR (PTP CT8)

Not possible to bar through

Access Matrix

TVR calls TVR [PA] (PTP

CT2)

Barred by Access Matrix


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Initiator Recipient


Radio (TVR)


Radio (TVR)

Fixed extensions


Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eeri

ng

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes

TVR calls TVR [PA] (PTP

CT3]

Barred by Access Matrix


[high priority] (PTP CT1) 2

Y Y Y

Extn calls fixed terminal

(PTP CT8) 3

Y Y Y Y Y Y

Extn calls TVR (PTP CT8)

TBD if Access Matrix can be

used to bar

Fixed terminal makes

group call (VGCS CT5) 3 Y Y

Y Y Y Y

Controller recipients

configured in group call

register

Fixed terminal makes REC

(VGCS CT5) 0 Y Y

Y Y Y Y



register

TVR makes REC (VGCS

CT5) 0

Y Y Y Y Y Y



register

TVR sends 'Standing at

signal' 3

Y Y

Fixed terminal sends 'Wait' 3 Y Y


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Initiator Recipient


Radio (TVR)


Radio (TVR)

Fixed extensions


Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes

TVR sends 'DSD activated' 2

Y Y

TVR sends SMS Message 4

Fixed terminal sends

‘Contact Fixed Terminal’ 4

Y

Y Y

Fixed terminal sends

'Contact signaller' 3 Y

Y

TVR sends SMS to fixed

terminal

Barred through no

subscription to SMS MO

TVR sends SMS to TVR

Barred through no


TVR sends SMS to OPH

Barred through no


Fixed terminal makes

broadcast (VBS CT5) 3 Y Y Y

Y Y

Fixed terminal berth-

triggered call (PTP CT2) 3 Y

Y Y

TVR and fixed terminal

makes International calls 4


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Initiator Recipient


Radio (TVR)


Radio (TVR)

Fixed extensions


Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Sig

nalle

r or

sig

nalle

r superv

isor

Route

contr

olle

r

RU

serv

ice d

eliv

ery

centr

e

Te

lecom

mu

nic

atio

ns e

ngin

eerin

g

contr

ol centr

e

Ele

ctr

ical contr

ol opera

tor

Driver

Tra

in s

taff

Public

addre

ss

Fix

ed tele

com

munic

atio

ns

netw

ork

exte

nsio

n

Exte

nded t

runk d

ialin

g e

xte

nsio

n

Public

sw

itched t

ele

phone

netw

ork

exte

nsio

n

Rail

em

erg

ency c

all

handlin

g

centr

e

Notes

External terminal makes

access to GB GSM-R

network 4

Remote PA operation Y

Y

Table 23 GB connectivity matrix


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Definitions

Access matrix

A network system file that sets permission for connectivity between various users.

Alphanumeric input

A means by which a user can enter numbers and letters.

Cab secure radio

A legacy radio system complying with the technical specifications BR 1661 issue D (March 1990) and BR 1845 issue H (April 1991), including October 1991 amendment.

Control

A facility that can be used to initiate, modify or terminate a function, for example physical button.

Fixed terminal

The static equipment used by authorised staff at fixed locations, for example, signallers.

GSM-R

A digital radio system (Global System for Mobile Communications – Railways) based on the GSM mobile communication standard adapted for use on European railways. The GSM-R system, for the purposes of this document, is one that complies with the EIRENE Functional Requirements Specification (version seven) and the System Requirements Specification (version 15) and updates approved as part of the change control process.


GSM-R cab mobile or a GSM-R operational radio configured using a GSM-R train voice radio SIM card as a train voice radio.

Head code

A four digit alphanumeric string used in GB for identifying a train in the context of a journey. It is of the form nAnn, for example, 1A56.

Intrinsically Safe (IS)

Intrinsically safe equipment is defined as ‘equipment and wiring which is incapable of releasing sufficient electrical or thermal energy under normal or abnormal conditions to cause ignition of a specific hazardous atmospheric mixture in its most easily ignited concentration.’ (ISA-RP12.6).

Journey registration using alphanumeric input

A registration specific to GB using head code and location code.

Main radio unit

The equipment which utilises the antenna and drives the HMI, handset and loudspeaker.

National Radio Network

A legacy radio system complying with the technical specification BR 1609 issue two (Aug 1987).

Network

The whole ground system, which the train voice radio communicates with, including the fixed user terminals.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


Physical button

A button, which achieves its function by mechanical means.

Starting signal code

The identity number of the first signal to be passed on a particular journey, used for the purposes of journey registration by the train voice radio.

Train voice radio

The train voice radio includes all trainborne equipment for voice communications between infrastructure sites and the train. (See also definition of GSM-R train voice radio.)

Train voice radio system

The network and all train voice radios.

Wild card number

A set of digits reserved for special use.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


Abbreviations and Acronyms

ASCII

American Standard Code for Information Interchange.

CT

Call Type.

DSD

Driver Safety Device.

ECRO

Electrical Control Room Operator.

EF

Elementary File (SIM card file arrangements).

eMLPP

enhanced Multi-Level Precedence and Pre-emption.

ETSI

European Telecommunications Standards Institute.

FRS

EIRENE Functional Requirements Specification.

GSM

Global System for Mobile Communications.

GSM-R

Global System for Mobile communications – Railway.

HATS

Head And Torso Simulator.

HMI

Human Machine Interface.

ITU

International Telecommunications Union.

MOS

Mean Opinion Score.

OPH

Operational Hand Portable.

PTP

Point-to-Point.

RIS

Rail Industry Standard.


of 51 RSSB


GK/RT0094

Issue One

Date March 2013


SDN

Service Dialling Number.

SIM

Subscriber Identity Module.

SMS

Short Messaging Service.

SRS

EIRENE System Requirements Specification.

TMOS

TOSQA Mean Opinion Score.

TSI

Technical Specification for Interoperability.

TVR

Train Voice Radio.

UIC

International Union of Railways.

UIN

User Identifier Number.

USSD

Unstructured Supplementary Service Data (USSD).

UUS1

User to User Signalling (service 1).

VBS

Voice Broadcast Service.

VGCS

Voice Group Call Service.


RSSB of 51


GK/RT0094

Issue One

Date March 2013


References

The Catalogue of Railway Group Standards gives the current issue number and status of documents published by RSSB. This information is also available from www.rgsonline.co.uk.

RGSC 01 Railway Group Standards Code

RGSC 02 Standards Manual

Documents referenced in the text

RSSB documents

GK/GN0694 Guidance on Train Voice Radio Systems

RIS-0794-CCS Rail Industry Standard for the GSM-R Train Voice Radio System

Other references

BR 1609 VHF band III radio for the national radio network incorporating the train overlay system

BR 1661 Train to Signalbox Radio System (Train Radio)

BR 1845 Train to Signalbox Radio System (Fixed Equipment) (withdrawn)

EIRENE FRS UIC project European Integrated Railway Radio Enhanced

Network Functional Requirements Specification, version 7.3.0

EIRENE SRS UIC project European Integrated Railway Radio Enhanced

Network System Requirements Specification, version 15.3.0

ETSI TS 100 977 v8.10.0 Digital cellular telecommunications system (Phase 2+);

Specification of the Subscriber Identity Module – Mobile

Equipment (SIM-ME) Interface

ETSI ETS 300 641 v4.3.1 Digital cellular telecommunications system (Phase 2) (GSM);

Specification of the 3 Volt Subscriber Identity Module – Mobile

Equipment (SIM – ME) interface

ITU-T, P.800 (1996) Methods for subjective determination of transmission quality

TOSQA 2001 Telecommunications Objective Speech Quality Assessment 2001, Head Acoustics, GmbH

