DOCSLIB.ORG

23. Balise Engineering for L2 and L3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
23. Balise Engineering for L2 and L3 EEIG ERTMS Users Group 123-133 Rue Froissart, 1040 Brussels, Belgium Tel: +32 (0)2 673.99.33 - TVA BE0455.935.830 Website: www.ertms.be E-mail: [email protected] ERTMS USERS GROUP - ENGINEERING GUIDELINE 23. Balise Engineering for L2 and L3 Ref: 23. Balise Engineering for L2 and L3 Version: 1.0 Date: 10/01/2019 EUG GDL Balise_Engineering v1.0.docx 23. Balise Engineering Page 1/40 EEIG ERTMS Users Group Modification history Version Date Modification / Description Editor 0.1 10/12/15 First draft PS 0.2 14/06/16 Modification after review of AB, SMc and AJM PS Structure modification 0.8 17/12/18 Merged version after ESG71 DC 0.9 17/12/18 Clean version. Candidate for version 1.0 DC 1.0 10/01/19 Version 1.0 DC EUG GDL Balise_Engineering v1.0.docx 23. Balise Engineering Page 2/40 EEIG ERTMS Users Group Table of Contents 1 Introduction ................................................................................................................................ 9 1.1 Background ........................................................................................................................ 9 1.2 Scope and Field of Application ........................................................................................... 9 1.3 Applicable system versions ................................................................................................. 9 1.4 Intentionally deleted .......................................................................................................... 10 1.5 Document structure .......................................................................................................... 10 2 References and Abbreviations ................................................................................................. 11 2.1 Abbreviations .................................................................................................................... 11 2.2 References ....................................................................................................................... 11 3 Balise implementation rules/advice depending on their ETCS content ..................................... 13 3.1 ETCS Packet – Transmission channel .............................................................................. 13 3.1.1 Section goal ............................................................................................................... 13 3.1.2 ETCS Packets only transmittable by balise ................................................................ 13 3.1.3 ETCS Packet transmittable by balise or other means ................................................ 15 Table 3: ETCS Packet - Balise transmission possible .............................................................. 15 3.1.4 ETCS Packet that cannot be transmitted by balise .................................................... 16 3.1.5 Constraints ................................................................................................................ 16 3.2 Analysis of ETCS Packet – Introduction ............................................................................ 17 3.3 Packet 0 – Virtual Balise Cover Marker ............................................................................. 17 3.3.1 Possible transmission Channel .................................................................................. 17 3.3.2 Goals and functions linked to the Packet ................................................................... 17 3.3.3 Use Cases ................................................................................................................. 17 3.3.4 Implementation advice / Requirements ...................................................................... 18 3.3.5 Packet content ........................................................................................................... 18 3.3.6 System Version applicability ...................................................................................... 18 3.4 P2 – System Version Order .............................................................................................. 18 3.4.1 Possible transmission Channel .................................................................................. 18 3.4.2 Goals and functions linked to the Packet ................................................................... 18 3.4.3 Use Cases ................................................................................................................. 18 3.4.4 Implementation advice / Requirements ...................................................................... 18 3.4.5 Packet content ........................................................................................................... 19 3.4.6 System Version applicability ...................................................................................... 19 3.5 P3 – National Values ........................................................................................................ 19 3.5.1 Possible transmission Channel .................................................................................. 19 3.5.2 Goals and functions linked to the Packet ................................................................... 19 3.5.3 Use Cases ................................................................................................................. 19 EUG GDL Balise_Engineering v1.0.docx 23. Balise Engineering Page 3/40 EEIG ERTMS Users Group 3.5.4 Implementation advice / Requirements ...................................................................... 19 3.5.5 Packet content ........................................................................................................... 19 3.5.6 System Version applicability ...................................................................................... 19 3.6 P6 – Virtual Balise Cover Order ........................................................................................ 19 3.6.1 Possible transmission Channel .................................................................................. 19 3.6.2 Goals and functions linked to the Packet ................................................................... 19 3.6.3 Use Cases ................................................................................................................. 20 3.6.4 Implementation advice / Requirements ...................................................................... 20 3.6.5 Packet content ........................................................................................................... 20 3.6.6 System Version applicability ...................................................................................... 20 3.7 P41- Level Transition Order .............................................................................................. 20 3.7.1 Possible transmission Channel .................................................................................. 20 3.7.2 Goals and functions linked to the Packet ................................................................... 20 3.7.3 Use Cases ................................................................................................................. 20 3.7.4 Implementation advices / Requirements .................................................................... 20 3.7.5 Packet content ........................................................................................................... 21 3.7.6 System Version applicability ...................................................................................... 21 3.8 P42 – Session Management ............................................................................................. 21 3.8.1 Possible transmission Channel .................................................................................. 21 3.8.2 Goals and functions linked to the Packet ................................................................... 21 3.8.3 Use Cases ................................................................................................................. 21 3.8.4 Implementation advice / Requirements ...................................................................... 21 3.8.5 Packet content ........................................................................................................... 21 3.8.6 System Version applicability ...................................................................................... 21 3.9 P44 – Data used by applications outside the ERTMS/ETCS ............................................. 21 3.9.1 Possible transmission Channel .................................................................................. 21 3.9.2 Goals and functions linked to the Packet ................................................................... 21 3.9.3 Use Cases ................................................................................................................. 22 3.9.4 Implementation advice / Requirements ...................................................................... 22 3.9.5 Packet content ........................................................................................................... 22 3.9.6 System Version applicability ...................................................................................... 22 3.10 P45 – Radio Network registration ..................................................................................... 22 3.10.1 Possible transmission Channel .................................................................................. 22 3.10.2 Goals and functions linked
Load more

Recommended publications
  • ERTMS/ETCS Railway Signalling
    Appendix A ERTMS/ETCS Railway Signalling Salvatore Sabina, Fabio Poli and Nazelie Kassabian A.1 Interoperable Constituents The basic interoperability constituents in the Control-Command and Signalling Sub- systems are, respectively, defined in TableA.1 for the Control-Command and Sig- nalling On-board Subsystem [1] and TableA.2 for the Control-Command and Sig- nalling Trackside Subsystem [1]. The functions of basic interoperability constituents may be combined to form a group. This group is then defined by those functions and by its remaining exter- nal interfaces. If a group is formed in this way, it shall be considered as an inter- operability constituent. TableA.3 lists the groups of interoperability constituents of the Control-Command and Signalling On-board Subsystem [1]. TableA.4 lists the groups of interoperability constituents of the Control-Command and Signalling Trackside Subsystem [1]. S. Sabina (B) Ansaldo STS S.p.A, Via Paolo Mantovani 3-5, 16151 Genova, Italy e-mail: [email protected] F. Poli Ansaldo STS S.p.A, Via Ferrante Imparato 184, 80147 Napoli, Italy e-mail: [email protected] N. Kassabian Ansaldo STS S.p.A, Via Volvera 50, 10045 Piossasco Torino, Italy e-mail: [email protected] © Springer International Publishing AG, part of Springer Nature 2018 233 L. Lo Presti and S. Sabina (eds.), GNSS for Rail Transportation,PoliTO Springer Series, https://doi.org/10.1007/978-3-319-79084-8 234 Appendix A: ERTMS/ETCS Railway Signalling Table A.1 Basic interoperability constituents in the Control-Command
    [Show full text]
  • EULYNX the Next Generation Signalling Strategy for Europe
    European Initiative Linking Interlocking Subsystems EULYNX The next generation signalling strategy for Europe Signalling Seminar IRSE ITC – JR East Frans Heijnen 7 April 2016 With thanks to Maarten van der Werff What would you do? European Initiative Linking Interlocking Subsystems Situation: • You are an infra manager (…. passenger, tax payer) • Expectations concerning signalling • Huge installed base • Many generations of equipment • Obsolete within 10..20 years • Not enough budget to replace And you know: “At all European railways these problems are similar …” EULYNX 2 What is the problem? European Initiative Linking Interlocking Subsystems • Each railway project adds new assets to become obsolete again • They get overage sooner than expected • Costs depend on whoever was chosen in the past as the supplier of the system • There are potential savings but the railway is stuck with current solutions • But you don’t have a strategy for a new solution EULYNX 3 EULYNX. What is EULYNX? European Initiative Linking Interlocking Subsystems EULYNX is the strategic approach for standardisation of signalling systems Because standardisation is a key factor to reduce: • A ‘technology zoo’ with many different systems, • The number of multiple incompatible interfaces • The cost involved in replacing and renewal EULYNX 4 The vision that becomes reality European Initiative Linking Interlocking Subsystems By systems engineering and the development process • Use a common architecture • With a common apportionment of functionalities • Define standardised
    [Show full text]
  • Balise Lifecheck the Control of Balises Is Mainly Manual and Often Basic
    utomation of Balise A maintenance Balise LifeCheck The control of balises is mainly manual and often basic. There are several tools available on the market to help performing balise maintenance, but a vast majority of them follow a corrective approach. ERTMS Solutions’ BaliseLifeCheck is the only on-board tool able to do predictive maintenance. he Tsolution • Compatibility with all balises’ and legacy KER balises (KVB, EBICAB,...) • Geolocalization of the balises and creation of a cartography • Detection of possible Big Metal Masses on the track that will affect BTM performances • Computation of a signature on measurements • Auto-marking on all balises matching signature • Generation of a full report after each test journey The BaliseLifeCheck is a preventive balise measurement instrument that can be used on both diagnostic and commercial trains. While capable of measuring balise, the BaliseLifeCheck is also highly customizable and can be set-up to deliver preventive maintenance to any ‘legacy’ Automatic Train Protection (ATP) balises, regardless if they are fitted or not with ERTMS. The Benefits On-board The system has been designed to be installed on-board a test or maintenance train which purpose is to analyze test tracks and active lines. Measurement It measures key electrical parameters of the up link signal and verifies if they comply with the requirements of Subset-036 in the case of ETCS balises. In this case some measurements/tests are performed against requirements of Subset-085. Diagnosis The main goal of the tool is to provide measurements and evidences which assess the correct behavior of balises that are already deployed on the field.
    [Show full text]
  • ERTMS/ETCS - Indian Railways Perspective
    ERTMS/ETCS - Indian Railways Perspective P Venkata Ramana IRSSE, MIRSTE, MIRSE Abstract nal and Balise. Balises are passive devices and gets energised whenever Balise Reader fitted on Locomo- European Railway Traffic Management System tive passes over it. On energisation, balises transmits (ERTMS) is evolved to harmonize cross-border rail telegrams to OBE. Telegram may consist of informa- connections for seamless operations across European tion about aspect of Lineside Signal, Gradients etc., nations. ERTMS is stated to be the most performant Balises are generally grouped and unique identifica- train control system which brings significant advan- tion will be provided to each balise. It helps to detect tages in terms of safety, reliability, punctuality and the direction of train. There four types of balises ex- traffic capacity. ERT.MS is evolving as a global stan- ist based their usage - Switchable, Infill, Fixed and dard. Many countries outside Europe - US, China, Repositioning balises. Switchable balises will be pro- Taiwan, South Korea and Saudi Arabia have adopted vided near lineside signals and they transmit aspect ERTMS standards for train traffic command and con- of lineside signal, permanent speed restrictions, gra- trol. dient information etc., Infill balises are provided in advance of signals to convey aspect of lineside signals earlier than Switchable balises. Fixed balises convey 1 Introduction information in regard to temporary speed restrictions and Repositioning balises provides data corrections. Signalling component of ERTMS has basically Balises transmit data in long or short telegrams four components - European Train Control System and those pertaining to direction. They are of two (ETCS) with Automatic Train Protection System, types - standard and reduced.
    [Show full text]
  • TRANSMISSION MODULE (STM) – EBICAB GENERAL TECHNICAL REQUIREMENTS Version 100 200 E 004 V
    Approved Approved SPECIFIC TRANSMISSION MODULE (STM) – EBICAB GENERAL TECHNICAL REQUIREMENTS Version 100 200 E 004 v. 6.1 GRS STM General Technical Requirements Specification TR GRS v6.1 2017-05-12 Sign:______ Sign:______ Document Modification History Version Modification Valid from Prepared Approved Updated requirements for Baseline 3 accor- M Olsson, 6.1 12 Maj 2017 ding to [STM-Delta-FRS-B3-List-v0.12]. Trafikverket Updated requirements for Baseline 3 accor- 6 ding to [STM-Delta-FRS-B3-List-v0.06]. 10 Oct.2014 B Bryntse, ÅF Updated requirements for Baseline 2 accor- 5.2 ding to [STM-Delta-FRS-List-v1.26] 8 Oct 2014 B Bryntse, ÅF Updated or new national requirements: B Bryntse, 5.1 G64, G57A, G57B. Index chapter added. 28.10.2009 Improved format of text and headers. Teknogram 5.0 Update of national requirements 26.6.2009 S Wallin 4.2 “STM Delta-GRS-List ver A” is introduced K.Hallberg 4.1 Final corrections 15.2.2007 U.Svensson F. Åhlander 4.0 I/F C deleted, recorder info changed U.Svensson Changes according to STM National, 3.0 new I/F F U.Svensson 2.1 Clarification G 58, G34 and G35 15.4.2003 J Öhrström S-H Nilsson 2.0 Added info regarding radio I/F chapter 2.3 20.6.2002 F Åhlander S-H Nilsson 1.4 For approval by RHK, JBV, BV 6.6.2002 F Åhlander S-H Nilsson EBICAB STM General technical Requirements Specification – 100 200 E 004 Version 6.1 100 200 E 004 Version 6.1 Page 3 (35) EBICAB STM General Technical Requirements Specification List of contents 1 INTRODUCTION...................................................................5 1.1 Applicable standards ....................................................................................5 1.2 List of definitions ...........................................................................................7 1.3 System definition ...........................................................................................8 2 INTERFACES ....................................................................
    [Show full text]
  • Western Route Strategic Plan Version 8.0: Delivery Plan Submission March 2019
    Western Route Strategic Plan Version 8.0: Delivery Plan submission March 2019 Western Route Strategic Plan Contents Foreword and summary ........................................................................................................................................................................................................... 3 Route objectives ..................................................................................................................................................................................................................... 10 Safety ..................................................................................................................................................................................................................................... 14 Train performance .................................................................................................................................................................................................................. 19 Locally driven measures ........................................................................................................................................................................................................ 24 Sustainability & asset management capability ....................................................................................................................................................................... 27 Financial performance ...........................................................................................................................................................................................................
    [Show full text]
  • Travelling Virtual Balise for Etcs
    A. Filip, Int. J. Transp. Dev. Integr., Vol. 1, No. 3 (2017) 578–588 TRAVELLING VIRTUAL BALISE FOR ETCS A. FILIP Faculty of Electrical Engineering and Informatics, University of Pardubice, Czech Republic. ABSTRACT The railway industry has taken a great effort and is currently focused on exploitation of global naviga- tion satellite system (GNSS) for the European train control system (ETCS). It has been assessed that replacement of track balises, used for safe train location determination, with virtual balises (VBs) de- tected by means of GNSS will significantly reduce the track-side infrastructure and operational costs. However, this innovated ETCS can be put into operations only in the case when detection of VBs by means of GNSS will achieve the same safety integrity level (SIL 4) and availability as it is required for physical balise groups (BGs). This paper describes a novel travelling virtual balise (TVB) concept, which was proposed to meet the demanding ETCS safety requirements for GNSS using the existing European Geostationary Navigation Overlay Service (EGNOS) safety-of-life (SoL) service. The TVB concept profits from the basic feature of GNSS – i.e. the ability of abundant train position determination in GNSS service volume, which can- not be realized by current track balise groups (BGs) with a spacing of hundreds of metres or more. The frequent GNSS train positions are utilized for (1) fast diagnostics of on-board location determination system (LDS), (2) introduction of reactive fail-safety into LDS and (3) derivation and justification of the ETCS safety requirements for EGNOS. The TVB concept brings one significant advantage to ETCS in contrast to the static VBs – i.e.
    [Show full text]
  • View / Open TM Database Composite.Pdf
    • • • • TRANSPORTATION-MARKINGS • DATABASE • COMPOSITE CATEGORIES • CLASSIFICATION & INDEX • • • -­ • III III • 1 TRANSPORTATION-MARKINGS: A STUDY IN CO.MMUNICATION MONOGRAPH SERIES Alternate Series Title: An Inter-modal Study of Safety Aids Transportatiol1-Markings Database Alternate T-M Titles: Transport [ation] Mark [ing]s / Transport Marks / Waymarks T-MFoundations, 4th edition, 2005 (Part A, Volume I, First Studies in T-M) (3rd edition, 1999; 2nd edition, 1991) Composite Categories A First Study in T-M: The US, 2nd edition, 1993 (Part B, Vol I) Classification & Index International Marine Aids to Navigation, 2nd edition, 1988 (parts C & D, Vol I) [Unified First Edition ofParts A-D, University Press ofAmerica, 1981] International Traffic Control Devices, 2nd edition, 2004 (Part E, Volume II, Further Studies in T-M) (lst edition, 1984) Part Iv Volume III, Additional Studies, International Railway Signals, 1991 (Part F, Vol II) International Aero Navigation Aids, 1994 (Part G, Vol II) Transportation-Markil1gs: A Study il1 T-M General Classification with Index, 2nd edition, 2004 (Part H, Vol II) (1st edition, 1994) Commllnication Monograph Series Transportation-Markings Database: Marine Aids to Navigation, 1st edition, 1997 (I'art Ii, Volume III, Additional Studies in T-M) TCDs, 1st edition, 1998 (Part Iii, Vol III) Railway Signals. 1st edition, 2000 (part Iiii, Vol III) Aero Nav Aids, 1st edition, 2001 (Part Iiv, Vol III) Composite Categories Classification & Index, 1st edition, 2006 (part Iv, Vol III) (2nd edition ofDatabase, Parts Ii-v,
    [Show full text]
  • Dimensioning and Engineering Rules
    ERTMS/ETCS Dimensioning and Engineering rules REF : SUBSET-040 ISSUE : 3.4.0 DATE : 16/12/15 Company Technical Approval Management approval ALSTOM ANSALDO AZD BOMBARDIER CAF SIEMENS THALES © This document has been developed and released by UNISIG SUBSET-040 Dimensioning and Engineering Rules Page 1/47 3.4.0 1. MODIFICATION HISTORY Issue Number Section Number Modification / Description Author Date 0.0.1 All First issue NG 22-jun-99 0.0.2 3.2 After meeting 24-Jun-99 NG 25-jun-99 4.1.1.4 – 4.1.1.5 4.1.2.1 – 4.1.2.2 4.3.2.1 (f) 0.0.3 All After comments from WGE NG 9-jul-99 group 0.1.0 3.1 – 3.2 After meeting 2-Sept-99 NG 17-sept-99 4.1.1 note 4.1.1.1.b 4.1.1.2 – 3 – 4 – 5 – 6 4.1.1.7 – 8 – 9 – 10 4.1.1.11 4.1.2.1 – 4.2.1.2 4.2.2.1 – 3 4.3.1.1. b – c 4.3.2.1 all 4.3.3.1 – 4.3.4.1 Appendix 0.1.1 4.1.1 – note After meeting 6-Oct-99 NG 13-Oct-99 4.1.1.1 a – b 4.1.1.4 – 5 – 7 – 9 4.1.1.10 – 12 4.1.2.1 4.1.3 4.2.2.3 4.2.3 4.3.2 Appendix 1.0.0 4.1.1.1 a After comments from WGE NG 28-Oct-99 4.1.1.12 group © This document has been developed and released by UNISIG SUBSET-040 Dimensioning and Engineering Rules Page 2/47 3.4.0 Issue Number Section Number Modification / Description Author Date 1.0.1 4.1.1.1 a After comments from WGE NG 29-Oct-99 group 1.0.2 All (including re-numbering NG 23-Feb-00 of the sections), after meeting 22-Feb-00 1.1.0 Final for distribution U.
    [Show full text]
  • Western Route Strategic Plan V7
    Route Strategic Plan Western Route Version 7.0: Strategic Business Plan submission 2nd February 2018 Western Route Strategic Plan Contents Section Title Description Page 1 Foreword and summary Summary of our plan giving proposed high level outputs and challenges in CP6 3 2 Stakeholder priorities Overview of customer and stakeholder priorities 14 3 Route objectives Summary of our objectives for CP6 using our scorecard 26 4 Activity prioritisation on a page Overview of the opportunities, constraints and risks associated with each objective area, the 32 controls for managing these and the resulting output across CP5 and CP6 5 Activities & expenditure High level summary of the cost and activity associated with our plan based on the prioritisation in 41 section 4 6 Customer focus & capacity strategy Summary of customer and capacity themed strategies that will be employed to deliver our plan 66 7 Cost competitiveness & delivery strategy Summary of delivery strategies that will be employed, and of headwinds and efficiency plans 69 accounted developed to date 8 Culture strategy Summary of the culture themed strategies that will be deployed to deliver our plan 80 9 Strategy for commercial focus Summary of our strategy and plans to source alternative investment 86 10 CP6 regulatory framework Information relating to our revenue requirement and access charging income 88 11 Sign-off Senior level commitment from relevant functions 91 Appendix A Joint performance activity prioritisation by Overview of the opportunities, constraints and risks associated
    [Show full text]
  • A Multi-Sensor Positioning Method Based Train Localization System for Low Density Line
    > REPLACE THIS LINE WITH YOUR PAPER IDENTIFICATION NUMBER (DOUBLE-CLICK HERE TO EDIT) < 1 A multi-sensor positioning method based train localization system for Low Density Line Wei Jiang, Sirui Chen, Baigen Cai, Jian Wang, Wei Shangguan and Chris Rizos Belt, One Road” policy, railway construction has been Abstract—The BeiDou Navigation Satellite System (BDS) has accelerating in western China and neighboring countries and been widely applied in many areas, including communications, territories. Because of the vast territory and sparse population, transportation, emergency rescue, public security, surveying, the railways in China’s western region are designed as Low precise positioning, and many other industrial applications. The integration of BDS and an Inertial Navigation System (INS) has Density Lines (LDLs). The LDLs have the characteristics of the ability to achieve a more consistent and accurate positioning long mileage, low traffic volume, inadequate infrastructure, and solution. However, during long BDS outages, the performance of simple topology, normally operated as single track [1-2]. One such an integrated system degrades because of the characteristics example LDL is the Chinese Qinghai-Tibet railway, which is of the Inertial Measurement Unit (IMU) – the sensor errors located in mountainous area of the Tibet province and Qinghai accumulate rapidly with time when operated in a standalone province. Qinghai-Tibet railway is the highest and the longest mode. In this paper, a BDS/INS/odometer/map-matching (MM) positioning methodology for train navigation applications is plateau railway in the world, with more than 300km of proposed, to solve the problem of positioning during BDS outages depopulated zone at altitudes of more than 4000m above sea when trains pass through signal obstructed areas such as under level, see Figure 1.
    [Show full text]
  • ERTMS Programme Signalling System Engineering Process Guideline Engineering Guidelines
    ERTMS Programme Signalling System Engineering Process Guideline Engineering Guidelines 017 Updated document 16.12.2020 GRIGUN 16E Updated document 07.04.2020 INGGJO NEDJON KJHO 15E Updated document 05.02.2020 INGGJO NEDJON KJHO 00E First Issue 12.12.2020 JANRUN KJHO MAGHEG Revision Reason for issue Date Created by Contr. by Appr. by Title: Pages: 210 ERTMS Programme Produced by: Bane NOR Digitalisation and Technology Signalling System Engineering Process Guideline Engineering Guidelines Prod.doc.no.: Rev: Replaces: Replaced by: Project: ERTMS Programme Document number: Revision: Area: Trackside ERP-30-S-00097 017 Operator's document no.: Operator's rev.: NA NA Page: 2 of 210 ERTMS Signalling System Doc. No: ERP-30-S-00097 Programme Engineering Guidelines Rev: 017 Date: 16.12.2020 This document was created by DOORS and updated by the author with correct revision details, signatures, operator details, and other empty fields not provided by DOORS. The DOORS module name is: Signalling System Engineering Guidelines The DOORS baseline is: Current The DOORS export date: 2020 12 16 Page: 3 of 210 ERTMS Signalling System Doc. No: ERP-30-S-00097 Programme Engineering Guidelines Rev: 017 Date: 16.12.2020 LIST OF CONTENTS 1 INTRODUCTION ............................................................................................................................ 8 1.1 Background ............................................................................................................................ 8 1.2 Purpose and scope ...............................................................................................................
    [Show full text]