Interface 'K' Specification

Interface 'K' Specification

ERTMS/ETCS Interface 'K' Specification REF : SUBSET-101 ISSUE : 2.0.0 DATE : February 24, 2012 Company Technical Approval Management approval ALSTOM ANSALDO BOMBARDIER INVENSYS SIEMENS THALES © This document has been developed and released by UNISIG SUBSET-101 Interface 'K' Specification Page 1/56 Issue 2.0.0 Page 2 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 MODIFICATION HISTORY Issue Number Section Num- Modification / Description Author Date ber 0.0.1, Initial draft based on meeting discus- B. Sjöbergh 2004-02-16 sions. 0.0.2, Update including Bombardier sug- P. Lundberg 2004-02-25 gestions for improvements. 0.0.3, Update considering conclusions from P. Lundberg 2004-03-19 the fourth WGKI meeting, and Bom- bardier suggestions for improve- ments. 0.0.4, Update considering conclusions from P. Lundberg 2004-05-06 the fifth WGKI meeting, and Bom- bardier suggestions for improve- ments. 0.0.5, Update considering discussions from P. Lundberg 2004-08-09 the seventh WGKI meeting, and Bombardier suggestions for im- provements. 0.0.6, Update considering Bombardier sug- P. Lundberg 2004-10-04 gestions for improvements. 0.0.7, Update considering discussions dur- P. Lundberg 2004-10-19 ing the ninth WGKI meeting. 0.0.8, Update considering discussions dur- P. Lundberg 2004-10-29 ing the tenth WGKI meeting. 0.0.9, Update considering discussions dur- P. Lundberg 2004-12-03 ing the eleventh WGKI meeting. 0.0.10, Update considering discussions dur- P. Lundberg 2005-01-17 ing the twelfth WGKI meeting. 0.0.11, Update considering discussions dur- P. Lundberg 2005-02-17 ing the thirteenth WGKI meeting. 0.0.12, Update considering e-mail discus- P. Lundberg 2005-02-25 sions. 0.1.0, First official draft. P. Lundberg 2005-03-09 0.1.1, Update considering conclusions from P. Lundberg 2005-05-13 the fifteenth and sixteenth WGKI meetings. Page 3 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 Issue Number Section Num- Modification / Description Author Date ber 0.1.2, Final working draft. P. Lundberg 2005-06-15 0.2.0, Second official draft. P. Lundberg 2005-06-23 0.2.1, 3.1.1, 4.1.1.3.1, Update considering conclusions from P. Lundberg 2005-09-01 4.1.1.3.2 the eighteenth WGKI meeting. 1.0.0, Final update (only change of issue P. Lundberg 2005-10-04 status). 1.0.1, 3.1.2, 3.1.4 Clarifications to CRC generation. P. Lundberg 2006-04-27 1.0.2 3.1.2, 3.1.4, Updated in accordance with CR 1049 P. Lundberg 2012-02-20 3.1.6, 4.1.2.7 and CR 1052. 2.0.0 Baseline 3 release version (only P. Lundberg 2012-02-24 change of Issue number). Page 4 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 Foreword This document is the specification for the Interface ‘K’ between the ERTMS/ETCS On-board BTM functionality and the KER STM’s. The purpose of Interface ‘K’ is to make it possible to have a common Balise antenna used by ERTMS/ETCS On-board Equipment as well as by one or several KER STM’s. Page 5 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 Contents 1 GENERAL ______________________________________________________________ 7 1.1 Introduction ________________________________________________________________7 1.2 Scope ______________________________________________________________________8 1.3 Functional Description ________________________________________________________9 1.4 Alternative Interfaces ________________________________________________________9 2 TERMINOLOGY ________________________________________________________ 10 2.1 Abbreviations ______________________________________________________________10 2.2 Acronyms _________________________________________________________________10 2.3 Definitions _________________________________________________________________11 3 PHYSICAL TRANSMISSION _______________________________________________ 13 3.1 Alternative 1 _______________________________________________________________13 3.1.1 Architecture _____________________________________________________________________ 13 3.1.2 Functional Data __________________________________________________________________ 15 3.1.3 Electrical Data ___________________________________________________________________ 18 3.1.4 Data Transmission________________________________________________________________ 18 3.1.5 Timing Requirements _____________________________________________________________ 20 3.1.6 Procedural Requirements __________________________________________________________ 20 3.1.7 Handling of Safety Diversified Data __________________________________________________ 22 3.2 Alternative 2 _______________________________________________________________23 3.2.1 Architecture _____________________________________________________________________ 23 3.2.2 Functional Data __________________________________________________________________ 23 3.2.3 Electrical Data ___________________________________________________________________ 23 3.2.4 Data Transmission________________________________________________________________ 23 3.2.5 Timing Requirements _____________________________________________________________ 24 3.2.6 Procedural Requirements __________________________________________________________ 25 3.2.7 Handling of Safety Diversified Data __________________________________________________ 25 4 FUNCTIONAL REQUIREMENTS ____________________________________________ 26 4.1 Alternative 1 _______________________________________________________________26 4.1.1 STM Functionality _______________________________________________________________ 26 4.1.2 ERTMS/ETCS Functionality _______________________________________________________ 35 4.1.3 Odometer Requirements for Side Lobe Handling ________________________________________ 41 4.1.4 Balise Separation _________________________________________________________________ 41 4.1.5 Balise Group Separation ___________________________________________________________ 41 Page 6 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 4.2 Alternative 2 _______________________________________________________________42 4.2.1 STM Functionality _______________________________________________________________ 42 4.2.2 ERTMS/ETCS Functionality _______________________________________________________ 45 4.2.3 Odometer Requirements for Side Lobe Handling ________________________________________ 48 4.2.4 Balise Separation _________________________________________________________________ 48 4.2.5 Balise Group Separation ___________________________________________________________ 48 5 RAMS REQUIREMENTS _________________________________________________ 49 5.1 Transmission System Aspects _________________________________________________49 5.2 Balise Aspects ______________________________________________________________49 5.3 On-board Transmission Equipment and STM Aspects ____________________________49 5.3.1 General ________________________________________________________________________ 49 5.3.2 Safety Integrity Requirements related to Interface ‘K’ ____________________________________ 50 6 REFERENCES __________________________________________________________ 52 ANNEX A, ON-BOARD TYPE 1 SPECIFICS _______________________________________ 53 A1 GENERAL ___________________________________________________________ 53 A2 SAFETY INTEGRITY REQUIREMENTS _____________________________________ 53 A3 MAXIMUM NUMBER OF CONSECUTIVE ‘ONES ’ ______________________________ 53 ANNEX B, ON-BOARD TYPE 2 SPECIFICS _______________________________________ 54 B1 GENERAL ___________________________________________________________ 54 B2 SAFETY INTEGRITY REQUIREMENTS _____________________________________ 54 B3 MAXIMUM NUMBER OF CONSECUTIVE ‘ONES ’ ______________________________ 54 ANNEX C, ON-BOARD TYPE 3 SPECIFICS _______________________________________ 55 C1 GENERAL ___________________________________________________________ 55 C2 SAFETY INTEGRITY REQUIREMENTS _____________________________________ 55 C3 MAXIMUM NUMBER OF CONSECUTIVE ‘ONES ’ ______________________________ 55 ANNEX D, ON-BOARD TYPE 4 SPECIFICS _______________________________________ 56 D1 GENERAL ___________________________________________________________ 56 D2 SAFETY INTEGRITY REQUIREMENTS _____________________________________ 56 D3 MAXIMUM NUMBER OF CONSECUTIVE ‘ONES ’ ______________________________ 56 Page 7 of 56 SUBSET-101, Issue 2.0.0 February 24, 2012 1 General 1.1 Introduction This document defines an interface between the ERTMS/ETCS On-board BTM function and the KER STM’s in order to allow for a common Balise antenna to be used by ERTMS/ETCS On-board Equip- ment as well as by one or several KER STM’s. This interface is called Interface ‘K’. The Eurobalise Transmission System is a safe spot transmission based system conveying safety related information between the wayside infrastructure and the train, and vice-versa. Several countries use an older generation of Balises, as a group known as KER Balises. These are similar enough to make it pos- sible to read both Eurobalises and KER Balises with the same On-board BTM function and antenna unit if the BTM function and antenna are properly adapted. The combination of the antenna and the BTM function is hereafter denominated “On-board Transmission Equipment”. The overall architecture of the ERTMS/ETCS On-board Constituent and the KER STM’s regarding the Interface ‘G’ and the Interface ‘K’ is shown in Figure 1. Profibus carrying STM FFFIS ERTMS/ETCS ERTMS/ETCS On-board Kernel Constituent ‘K’ KER BTM function On-board STM Transmission Equipment Antenna Unit ‘A’ ‘G’ Eurobalise KER Balise ‘C’ Wayside LEU Encoder Signalling Equipment ‘S’ From / to Wayside Signaling or Interlocking Figure 1:

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    56 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us