Train Voice Radio Systems

Transcription

1 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 s is owned by Rail Safety and Standards Board Limited. All rights are hereby reserved. No (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. 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 s may be reproduced. Published by: Block 2 Angel Square 1 Torrens Street London EC1V 1NY Copyright 2013 Rail Safety and Standards Board Limited

2 Train Voice Radio Systems record Date Comments 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 GE/RT8080 issue one Train Radio Systems for Voice and Related Messaging Communications GE/RT8081 issue one Requirements for GSM-R Voice Radio System GE/RT8082 issue one GSM-R Cab Mobile, Great Britain Open Interface Requirements (Rapid Response) Sections superseded Date when sections are superseded All 01 June 2013 All 01 June 2013 All 01 June 2013 Supply 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 GE/RT8081 issue one Requirements for GSM-R Voice Radio System, ceases to be in force and is withdrawn as of 01 June 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 The authoritative version of this document is available at Uncontrolled copies of this document can be obtained from Communications,, Block 2, Angel Square, 1 Torrens Street, London EC1V 1NY, telephone or enquirydesk@rssb.co.uk. Other Standards and associated documents can also be viewed at Page 2 of 51

3 Train Voice Radio Systems Contents Section Description Page Part 1 Purpose and Introduction Purpose Introduction Approval and authorisation of this document 7 Part 2 General Requirements for Train Voice Radio Systems Introduction Installation 8 Part 3 Technical Requirements for the GSM-R Train Voice Radio Introduction Train voice radio software management Driver only operation of passenger trains Protection of phonebook entries SIM card and network access arrangements Journey registration using alphanumeric input Pre-defined text messages GB specific UUS1 tags UUS1 message definitions: pre-defined text message UUS1 message definitions: pre-defined text message acknowledge UUS1 message definitions: network status logging UUS1 message definitions: supplementary registration data emlpp for high-priority point-to-point call Number format of phonebook Speech quality subjective testing Speech quality objective testing Testing EIRENE Call Type (CT) ing as applied in GB Unauthorised functional s Train identity Railway emergency call 20 Part 4 Operational Requirements for GSM-R Train Voice Radio Introduction SIM card and network access arrangements Phonebook Journey registration 21 Part 5 Technical Requirements for GSM-R Network Introduction Network software management Journey registration GB specific UUS1 tags UUS1 message definitions: pre-defined text message UUS1 message definitions: network status logging UUS1 message definitions: pre-defined text message acknowledge UUS1 message definitions: supplementary registration data Enhanced Presentation of Functional Number emlpp for high-priority point-to-point call SIM file definition GB connectivity Network coverage 28 Page 3 of 51

4 Train Voice Radio Systems 5.14 Public emergency call Railway emergency group calls Testing Positional information Overview of EIRENE Call Type (CT) ing as applied in GB Signs Driver only operation of passenger trains 30 Part 6 GSM-R Network Operational Requirements Introduction Alternative communications system SIM card and network access arrangements 31 Part 7 Performance Requirements Call success rates Speech quality Head code registration Call set-up times 33 Part 8 National Radio Network (NRN) Requirements Introduction Regional controller initiated emergency broadcast call Call set-up time performance Electrical Control Room Operator (ECRO) calls Shunting operation System management 34 Part 9 Cab Secure Radio Introduction Requirement for use Emergency calls Call set-up time performance Electrical Control Room Operator (ECRO) calls System management Driver only operation of passenger trains 36 Part 10 Application of this document Application infrastructure managers Application railway undertakings 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 s 13 Table 5 Definition of the Acknowledge byte 14 Table 6 Latitude coding 16 Page 4 of 51

5 Train Voice Radio Systems Table 7 Longitude coding 16 Table 8 Functions and associated s 17 Table 9 CT3 UIN format 19 Table 10 GB specific tags 23 Table 11 Pre-defined text message definition s 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 s 27 Table 16 SIM card file structure 27 Table 17 SIM card profile 27 Table 18 CT3 UIN 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 Page 5 of 51

6 Train Voice Radio Systems Part 1 Purpose and Introduction 1.1 Purpose 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) 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 Background 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) 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 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 Europeancompliant digital train voice radio system (namely GSM-R) Related requirements in other documents 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 Page 6 of 51

7 Train Voice Radio Systems 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 Supporting documents The following Railway Group documents support this Railway Group Standard: GK/GN0694 Guidance on Train Voice Radio Systems. RIS-0794-CCS Radio Systems. Rail Industry Standard for the GSM-R Train Voice 1.3 Approval and authorisation of this document 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 This document was authorised by on 01 February Page 7 of 51

8 Train Voice Radio Systems Part 2 General Requirements for Train Voice Radio Systems 2.1 Introduction This part sets out the general requirements that the train voice radio system and infrastructure network have to supply. 2.2 Installation Train voice radio installation 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 The train voice radio shall be compatible with the train voice radio system selected for trains using the route Infrastructure installation The train voice radio fixed infrastructure shall be compatible with the train voice radio system selected for trains using the route. Page 8 of 51

9 Train Voice Radio Systems Part 3 Technical Requirements for the GSM-R Train Voice Radio 3.1 Introduction This part sets out the technical requirements for the GSM-R train voice radio. 3.2 Train voice radio software management 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 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) The DSD alarm message shall provide location information The DSD alarm message shall be sent with priority Multi-Level Precedence and Pre-emption (emlpp) Protection of phonebook entries 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 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 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 , it shall: a) Translate an entered head code and location code into an eight digit numeric journey registration using an algorithm, as set out in Appendix A.1, with the entered head code, to calculate the first five digits of the registration. b) Append the entered three digit location code to the calculated five digits, to form the journey registration. Page 9 of 51

10 Train Voice Radio Systems 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 s returned by the algorithm for the first journey registration attempt. f) Use the second lowest of the three five digit s for a second journey registration attempt, only if the USSD request utilising the lowest numerical value train returns a response code indicating that the is a duplicate. g) Use the highest numerical value of the three possible five digit s for a third journey registration attempt, only if the USSD request utilising the second lowest numerical value train returns a response code indicating that the is a duplicate. h) On successful completion of journey registration of the leading driver functional, 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 being a duplicate, if the USSD request utilising the highest numerical value train returns a response code indicating that the 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 Background 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 GB specific UUS1 tags 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. Page 10 of 51

11 Train Voice Radio Systems 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 Incoming GB specific pre-defined text messages The GSM-R train voice radio shall support the incoming pre-defined text messages set out in Table 1. Message Wait Contact signaller Contact fixed terminal Purpose Sent by signaller in response to driver originated Standing at signal message Sent by signaller at any time to prompt driver to make a voice call 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 On receipt of a valid UUS1 message, the GSM-R train voice radio Human Machine Interface (HMI) shall automatically display the associated predefined text message and provide an audible indication Outgoing pre-defined text messages The train voice radio shall support the outgoing pre-defined text message, as set out in Table 2. Message Standing at signal Purpose Sent by driver to inform signaller that train is waiting at a signal Table 2 Outgoing pre-defined text messages 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 Background The tag value identifies the type of message. Values in the range 128 to 255 are reserved for national use. Page 11 of 51

12 Train Voice Radio Systems Tag definitions The GB specific UUS1 messages shall use the UUIE format specified by the EIRENE System Requirements Specification 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 132 Network status logging 133 Pre-defined text message acknowledge 134 Supplementary registration data 135 Supplementary registration data acknowledge Table 3 GSM-R train voice radio GSM-R train voice radio GSM-R train voice radio Network GSM-R train voice radio Network Designated terminal Network GSM-R train voice radio Network Application of tags on the GB network Presentation of pre-defined text messages (see tag 133) Coverage loss and recovery flag use Acknowledgement of received pre-defined text messages (see tag 128) Presentation of alphanumeric head code during journey registration (see tag 135) Acknowledgement of receipt of journey registration head code (see tag 134) Exceptional procedures or unsuccessful outcome for outgoing messages The outgoing message shall not include unassigned or reserved tags. 3.9 UUS1 message definitions: pre-defined text message Application 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 UUS1 message format This UUS1 message shall consist of tag 05 followed by tag Tag 128 shall be in the format set out below: Pre-defined Message Tag representing Pre-defined Message = '128' Message Number length = Message Byte 1 Byte 2 Byte 3 Page 12 of 51

13 Train Voice Radio Systems Message definitions The definitions of message s shall be as set out in Table 4. Message 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 s 3.10 UUS1 message definitions: pre-defined text message acknowledge Application Format A pre-defined text message acknowledge shall be sent by the train voice radio on receipt of a pre-defined text message This UUS1 message shall consist of tag 05 followed by tag Tag 133 shall be in the format set out below: Pre-defined message Acknowledge Tag representing Pre-defined Message Acknowledge = '133' Message Number Acknowledge length = Byte 1 Byte 2 Message Number Byte 3 Acknowledge Byte The Message Number byte shall be the set out in Table The Acknowledge byte shall be as set out in Table 5. Page 13 of 51

14 Train Voice Radio Systems Acknowledge field Name Meaning 0 Delivered Destination available to receive predefined text message and message recognised by recipient. Message format correct and length correct 1 Not delivered Destination not available or not in correct state to receive UUS1 predefined message 2 Invalid format Message format or length incorrect, or sender s functional absent 3 Undefined message Message not recognised by the recipient Table 5 Definition of the Acknowledge byte 3.11 UUS1 message definitions: network status logging Application 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 UUS1 message format This UUS1 message shall consist of tag Tag 132 shall be in the format set out below: Page 14 of 51

15 Train Voice Radio Systems Message definitions UTC Time format shall be the time in seconds since midnight (00:00:00), January A UTC Value of 0 shall indicate no valid time is available The valid bit in the location is used to indicate if the location is valid; 1 = Valid, 0 = Invalid The location information (latitude and longitude) is formatted as set out in Table 6 and Table 7. Page 15 of 51

16 Train Voice Radio Systems Units Range Number of bits Example Degrees Minutes Hundredths of seconds Direction S = 0 1 N N = 1 Total 27 Table 6 Latitude coding Units Range Number of bits Example Degrees Minutes Hundredths of seconds Direction E = 0 1 E W = 1 Total 28 Table 7 Longitude coding The Stock Number digits shall be in EIRENE engine format UUS1 message definitions: supplementary registration data Application Format 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 This UUS1 message shall consist of tag 134 only Tag 134 shall be in the format set out below: Tag representing Supplementary Registration Data = '134' Supplementary Registration Data length = Byte 1 Byte 1 ASCII Head Code First Character Byte 3 Head Code ASCII Head Code Second Character Byte 4 ASCII Head Code Third Character Byte 5 ASCII Head Code Fourth Character Byte The head code characters shall be alphanumeric ASCII characters. Page 16 of 51

17 Train Voice Radio Systems 3.13 emlpp for high-priority point-to-point call Designated call priorities The emlpp priority designations and s for the functions set out in this document shall be as set out in Table 8. Function emlpp priority Associated Incoming high-priority pointto-point voice call Set by network CT2/CT3 Outgoing high-priority pointto-point voice call 2 GBUSC Table 8 Functions and associated s 3.14 Number format of phonebook The International Telecommunication Union Telephone Standardisation Sector (ITU-T) E.164 international format shall be used for all GSM-R train voice radio phonebook entries with the exception of CT1 location dependent s Speech quality subjective testing 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 Speech quality objective testing Test exemption The train voice radio shall be tested objectively, as set out in to , unless it has been previously type-tested and certified for operational use Transmitted speech quality requirements 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 This TMOS requirement shall be achieved for all call types involving speech originated from the GSM-R train voice radio Received speech quality requirements 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 For all call types, the GSM-R train voice radio shall provide an average received speech quality TMOS of no less than General requirements for speech quality measurements All measurements for speech quality shall be made using the TOSQA2001 algorithm. Page 17 of 51

18 Train Voice Radio Systems 3.17 Testing The test set-up shall be calibrated and equalised as prescribed by TOSQA 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 The HATS shall be equipped with an artificial mouth that conforms to ITU-T Recommendation P The HATS shall be equipped with an artificial ear that conforms to ITU-T Recommendation P.57 artificial ear type All speech samples shall fulfil the requirements of ITU-T, P.800 recommendations All measurements shall be made in an anechoic chamber 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. Page 18 of 51

19 Train Voice Radio Systems 3.18 EIRENE Call Type (CT) ing as applied in GB GB format for Call Type 3 (CT3) User Identifier Number (UIN) The format of a CT3 UIN for traction units with home network reference shall be in accordance with the requirements set out in Table 9. CT3 UIN content (total eight digits) Type of traction unit to be coded as UIN Digit#1 (cab differentiator) Digit#2 (train differentiator) Digit#3 Digit#4 Digits#5 to 8 Four digit vehicle / unit 1 for Cab A 2 for Cab B The four digit vehicle / unit Five digit vehicle / unit 1 for Cab A 2 for Cab B 5 0 for on track machines with five digit s prefixed by DR First digit of the five digit vehicle / unit Remaining digits of the five digit vehicle / unit 5 for other vehicles and units Six digit vehicle / unit 1 for Cab A 2 for Cab B 6 First digit of the six digit vehicle / unit Second digit of the six digit vehicle / unit Remaining digits of the six digit vehicle / unit Seven digit vehicle / unit 3 for Cab A 4 for Cab B First digit of the seven digit vehicle / unit Second digit of the seven digit vehicle / unit Third digit of the seven digit vehicle / unit Remaining digits of the seven digit vehicle / unit Table 9 CT3 UIN format Page 19 of 51

20 Train Voice Radio Systems In cases where a CT3 or CT4 could be used, CT3 s shall be used Unauthorised functional s The train voice radio shall prevent certain types of users from registering functional s that they are not authorised to use Train identity Correlation between train identity or stock and radio shall be provided to allow the network user to be shown this information Railway emergency call It shall be possible for users receiving an emergency call to speak to all others responding to the emergency call. Page 20 of 51

21 Train Voice Radio Systems Part 4 Operational Requirements for GSM-R Train Voice Radio 4.1 Introduction This part sets out the operational requirements for the RUs which are considered necessary for operational compatibility with the GB network. 4.2 SIM card and network access arrangements The RU shall make a request to the issuing IM to remotely disable SIM cards, when they are no longer required 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 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 The RU shall supply any additional or changed phone s it requires to the IM according to an agreed plan. 4.4 Journey registration The RU shall have a process in place for its drivers to attempt journey registration of the GSM-R train voice radio. Page 21 of 51

22 Train Voice Radio Systems Part 5 Technical Requirements for GSM-R Network 5.1 Introduction This part sets out technical requirements for the GSM-R network. 5.2 Network software management GSM-R network software updates shall not disrupt train operation. 5.3 Journey registration Where an eight digit numeric journey registration is provided, the head code shall be determined using the algorithm set out in Appendix A On entry of an alphanumeric format GB head code, the signalling control centre display shall show the first five digits of the journey registration returned from the algorithm set out in Appendix A The network shall permit multiple journey registrations where there are different functional s and the location code is a wild card of 99x. 5.4 GB specific UUS1 tags Background The tag value identifies the type of message. Values in the range 128 to 255 are reserved for national use Tag definitions The Great Britain specific UUS1 messages shall use the UUIE format specified by the EIRENE System Requirements Specification 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 Network Train voice radio Presentation of pre-defined text messages (see tag 133) 132 Network status logging Train voice radio Designated terminal Coverage loss and recovery logging 133 Pre-defined text message acknowledge Train voice radio Network Network Train voice radio Acknowledgement of received pre-defined text messages (see tag 128) 134 Supplementary registration data Network Train voice radio Presentation of alphanumeric ASCII head code Page 22 of 51

23 Train Voice Radio Systems 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 Use of Tag 132 shall not disrupt train operation. 5.5 UUS1 message definitions: pre-defined text message Application 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 UUS1 message format This UUS1 message shall consist of tag 05 followed by tag Tag 128 shall be in the format set out below: Pre-defined Message Tag representing Pre-defined Message = '128' Message Number length = Message Byte 1 Byte 2 Byte Message definitions The definitions of message s shall be as set out in Table 11. Message 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 s 5.6 UUS1 message definitions: network status logging Application 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. Page 23 of 51

24 Train Voice Radio Systems UUS1 message format This UUS1 message shall consist of tag Tag 132 shall be in the format set out below: Message definitions UTC Time format shall be the time in seconds since midnight (00:00:00), January A UTC Value of 0 shall indicate no valid time is available The valid bit in the location is used to indicate if the location is valid; 1 = Valid, 0 = Invalid. Page 24 of 51

25 Train Voice Radio Systems The location information (latitude and longitude) is formatted as set out in Table 12 and Table 13. Units Range Number of bits Example Degrees Minutes Hundredths of seconds Direction S = 0 1 N N = 1 Total 27 Table 12 Latitude coding Units Range Number of bits Example Degrees Minutes Hundredths of seconds Direction E = 0 1 E W = 1 Total 28 Table 13 Longitude coding The Stock Number digits shall be in EIRENE engine format. 5.7 UUS1 message definitions: pre-defined text message acknowledge Application Format A pre-defined text message acknowledge, shall be sent by the network on receipt of a pre-defined text message This UUS1 message shall consist of tag 05 followed by tag Tag 133 shall be in the format set out below: Pre-defined message Acknowledge Tag representing Pre-defined Message Acknowledge = '133' Message Number Acknowledge length = Byte 1 Byte 2 Message Number Byte 3 Acknowledge Byte The Message Number byte shall be the set out in Table The Acknowledge byte shall be defined as set out in Table 14. Page 25 of 51

26 Train Voice Radio Systems Acknowledge field Name Meaning 0 Delivered Destination available to receive predefined text message and message 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 absent 3 Undefined message Message not recognised by the recipient Table 14 Definition of the Acknowledge byte 5.8 UUS1 message definitions: supplementary registration data Application Format The supplementary registration data message shall be sent by the network when an eight digit journey registration is successful This UUS1 message shall consist of tag 134 only Tag 134 shall be in the format as set out below: Tag representing Supplementary Registration Data = '134' Supplementary Registration Data length = Byte 1 Byte 1 ASCII Head Code First Character Byte 3 Head Code ASCII Head Code Second Character Byte 4 ASCII Head Code Third Character Byte 5 ASCII Head Code Fourth Character Byte The head code characters shall be alphanumeric ASCII characters. 5.9 Enhanced Presentation of Functional Number The network shall send Enhanced Presentation of Functional Number information with the identity of the sender in tag emlpp for high-priority point-to-point call Designated call priorities The emlpp priority designations and associated s for the functions set out in this document shall be as set out in Table 15. Page 26 of 51

27 Train Voice Radio Systems Function emlpp priority Associated Incoming high-priority pointto-point voice call Set by GSM-R train voice radio N/A Outgoing high-priority pointto-point voice call 2 CT2/CT3 Table 15 emlpp priorities and associated s 5.11 SIM file definition SIM card access conditions and file structure The SIM card file structure shall be as set out in Table 16. DF TELECOM (7F10): EF Name File type Maximum of records 6F49 SDN linear 20 Table 16 SIM card file structure The length of the alpha identifier shall be 14 characters in the SDN file SIM card profile The GB GSM-R train voice radio SIM card profile shall include the elementary file (EF) information, as set out in Table 17. Name Description Values SDN Record 11 SDN Record 12 Outgoing high-priority point-to-point voice call Outgoing pre-defined text message Standing at signal GBUSC GBSAS SDN Record 14 GB DSD mode GBDSD SDN Record 16 GB statistics for network status logging GBSTC Table 17 SIM card profile User identity The SIM cards shall be configured in such a manner that users cannot withhold their identity. Page 27 of 51

28 Train Voice Radio Systems 5.12 GB connectivity The network shall be configured as set out in Appendix B Network coverage 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 Public emergency call Public emergency call s ( 999 and 112 ) shall be directed to the railway telephone system emergency operator Following connection of the emergency voice call, the regional controller shall have access to a speech connection in order to pass information Railway emergency group calls Incoming emergency calls During emergency calls, speech shall be possible to allow only one signaller receiving the warning tone to give information Speech shall be possible to allow a controller receiving the warning tone to give information Speech shall be possible to allow train voice radio users receiving the warning tone to give information Handling of multiple emergency calls 5.16 Testing 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 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 Positional information f) Journey registration and deregistration Where available, the network shall utilise ground-based signalling positional information for enhanced location dependent addressing. Page 28 of 51

29 Train Voice Radio Systems 5.18 Overview of EIRENE Call Type (CT) ing as applied in GB GB format for Call Type 3 (CT3) User Identifier Number (UIN) The format of CT3 UIN for traction units with home network reference shall be in accordance with the requirements set out in Table 18. CT3 UIN content (total eight digits) Type of traction unit to be coded as UIN Digit#1 (cab differentiator) Digit#2 (train differentiator) Digit#3 Digit#4 Digits#5 to 8 Four digit vehicle / unit 1 for Cab A 2 for Cab B The four digit vehicle/ unit Five digit vehicle / unit 1 for Cab A 2 for Cab B 5 0 for on track machines with five digit s prefixed by DR First digit of the five digit vehicle / unit Remaining digits of the five digit vehicle / unit 5 for other vehicles and units Six digit vehicle / unit 1 for Cab A 2 for Cab B 6 First digit of the six digit vehicle / unit Second digit of the six digit vehicle / unit Remaining digits of the six digit vehicle / unit Seven digit vehicle / unit 3 for Cab A 4 for Cab B First digit of the seven digit vehicle / unit Second digit of the seven digit vehicle / unit Third digit of the seven digit vehicle/ unit Remaining digits of the seven digit vehicle / unit Table 18 CT3 UIN format Page 29 of 51

30 Train Voice Radio Systems 5.19 Signs A consistent policy for lineside signs shall be developed to support the train voice radio system Driver only operation of passenger trains 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. Page 30 of 51

31 Train Voice Radio Systems Part 6 GSM-R Network Operational Requirements 6.1 Introduction This part sets out the operational requirements which are considered necessary for operational compatibility with the GB network. 6.2 Alternative communications system 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 SIM card and network access arrangements SIM card security 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 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 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 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 Phonebook The IM shall modify the phonebook when it requires a change The IM shall provide the RU with the amended phonebook for uploading into the GSM-R train voice radio. Page 31 of 51

32 Train Voice Radio Systems Part 7 Performance Requirements 7.1 Call success rates Call success rates shall be in accordance with the requirements set out in Table Measurements shall be made under mobile conditions to be representative of operational conditions. KPI definition Railway emergency group calls successfully connected and completed (for fixed-to-mobile and mobile-to-fixed calls). Network originated high priority point-to-point calls and train voice radio originated high priority point-to-point calls connected and completed. All other calls, not covered by the above, successfully connected and completed. Minimum performance level 98% 98% 97% Notes 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. Table 19 Call success rates 7.2 Speech quality The speech quality for all call types shall be in accordance with the requirements set out in Table 20. KPI definition Speech quality expressed as Mean Opinion Score (MOS) for successfully established calls. Minimum performance level MOS >=3 for 99% of speech samples. Notes MOS value of 3 represents the threshold for acceptable speech quality. Table 20 Speech quality for all voice call types Page 32 of 51

33 Train Voice Radio Systems 7.3 Head code registration 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. KPI definition Time to complete mobile to network transaction for UK alphanumeric head code registration. Minimum performance level 95% within 30s Notes Includes unsuccessful call attempts. Table 21 Head code registration 7.4 Call set-up times The performance for call set-up times shall be in accordance with the requirements set out in Table 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 The required call set-up times shall be achieved in at least 95% of cases The handover success rate should be at least 99.5% over train routes under design load conditions (as given in [GSM 03.05]). KPI definition All operational mobile-tofixed calls except railway emergency calls. All operational fixed-tomobile calls except railway emergency calls. All operational mobile-tomobile calls except group calls between drivers in the same area. Minimum performance level <5s <7s <10s Notes Including urgent point to-point calls. All low priority calls. <10s Table 22 Call set-up times Page 33 of 51

34 Train Voice Radio Systems Part 8 National Radio Network (NRN) Requirements 8.1 Introduction 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 Regional controller initiated emergency broadcast call The train voice radio system shall enable an emergency voice call to be made by a regional controller 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 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 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 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 The call shall be capable of being initiated by the driver, following a small of key presses. 8.5 Shunting operation 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 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. Page 34 of 51

35 Train Voice Radio Systems Part 9 Cab Secure Radio 9.1 Introduction 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 Requirement for use Controller s terminals 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 Recipients of emergency calls 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 Handling of multiple emergency calls 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 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 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 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. Page 35 of 51

36 Train Voice Radio Systems 9.7 Driver only operation of passenger trains 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). Page 36 of 51

37 Train Voice Radio Systems Part 10 Application of this document 10.1 Application infrastructure managers Scope 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 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 Action to bring existing train voice radio into compliance with the requirements of this document is not required 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 Exclusions from scope The requirements set out in Parts 3 and 4 do not apply to infrastructure managers Where the route is required to be compliant with the CCS TSI, Part 2 does not apply General compliance date for infrastructure managers This comes into force and is to be complied with from 01 June 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. Where it is considered not reasonably practicable to comply with the requirements, authorisation not to comply should be sought in accordance with the s Code. Page 37 of 51