1、IEEE Std 1474.3-2008IEEE Recommended Practice forCommunications-Based Train Control (CBTC)System Design and Functional AllocationsIEEE3 Park Avenue New York, NY 10016-5997, USA3 September 2008IEEE Vehicular Technology SocietySponsored by theRail Transit Vehicle Interface Standards Committee1474.3TMI
2、EEE Std 1474.3TM-2008 IEEE Recommended Practice for Communications-Based Train Control (CBTC) System Design and Functional Allocations Sponsor IEEE Rail Transit Vehicle Interface Standards Committee of the IEEE Vehicular Technology Society Approved 12 June 2008 IEEE-SA Standards Board Abstract: This
3、 recommended practice for communications-based train control (CBTC) system design and functional allocations builds on IEEE Std 1474.1 by decomposing each identified automatic train protection, automatic train operation and automatic train supervision function to a level where each subfunction can b
4、e allocated to one of the CBTC subsystems. Keywords: automation, communication, signaling, train control, function The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2008 by the Institute of Electrical and Electronics Engineers, Inc. All
5、 rights reserved. Published 3 September 2008. Printed in the United States of America. IEEE and 802 are registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clear
6、ance Center. iv Copyright 2008 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 1474.3-2008, IEEE Recommended Practice for Communications-Based Train Control (CBTC) System Design and Functional Allocations. IEEE Std 1474.1-2004 establishes performance and functional
7、requirements for communications-based train control (CBTC) systems. Although there could be many possible system designs to achieve these performance and functional requirements, the current state-of-the-art and industry trends reflect that in many areas there is a preferred approach to allocating t
8、he functional requirements to the individual CBTC subsystems. This recommended practice for CBTC system design and functional allocations documents these preferred approaches as current best industry practice. In those areas where there are no clear-cut recommendations, alternative approaches may be
9、 described. In such cases, however, it is not the intent to provide any recommendation or guide as to which alternative approach should be selected for a specific application. This decision would typically be made by the CBTC system supplier, in association with the authority having jurisdiction. Th
10、e approach adopted in this recommended practice is to build on IEEE Std 1474.1-2004 by decomposing each identified automatic train protection, automatic train operation, and automatic train supervision function to a level where each subfunction can be allocated to one of the CBTC subsystems. In addi
11、tion to capturing best industry practice, this recommended practice is intended to be of value in providing a means for interested parties to gain a better understanding of CBTC system architectures and principles of operation. Notice to users Laws and regulations Users of these documents should con
12、sult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publ
13、ication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use,
14、by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this
15、document. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in tim
16、e consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of v Copyright 2008 IEEE. All rights reserved. amendments,
17、corrigenda, or errata, visit the IEEE Standards Association Web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA Web site a
18、t http:/standards.ieee.org. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/updates/errata/. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at
19、the following URL: http:/standards.ieee.org/reading/ieee/interp/. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or val
20、idity of any patent rights in connection therewith. A patent holder or patent applicant has filed a statement of assurance that it will grant licenses under these rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair disc
21、rimination to applicants desiring to obtain such licenses. Other Essential Patent Claims may exist for which a statement of assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the lega
22、l validity or scope of Patents Claims, or determining whether any licensing terms or conditions are reasonable or non-discriminatory. Further information may be obtained from the IEEE Standards Association. Participants At the time this recommended practice submitted to the IEEE-SA Standards Board f
23、or approval, the Communications-Based Train Control Working Group had the following membership: Alan F. Rumsey, Chair Corrine Braban Frederick Childs Tom Eichorn Jeff Eilenberg Nicholas Estivals Stephane Gatellier Harvey Glickenstein Harry Heilmann James R. Hoelscher Bob Jahn Kenneth Karg John LaFor
24、ce Didier Lapalus Duncan Lewis Dale Logan Robert MacDonald David Male Charles Martin Norman May William Petit Louis Sanders Carl Schwellnus Bob Sudo Errol Taylor Carl Thompson Dave Thurston Robert Walsh Raj Wagley vi Copyright 2008 IEEE. All rights reserved. The following members of the individual b
25、alloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Bradford Benbow Stephane Bois Yunxiang Chen Frederick Childs Keith Chow Michael Crispo David Dimmer Thomas Eichorn Jeff Eilenberg Marc Emmelmann Nicholas Estivals Christian Girard Harvey Gli
26、ckenstein Randall Groves James R. Hoelscher Werner Hoelzl Paul Jamieson Kenneth Karg Karocki, Piotr Kurihara, Thomas John LaForce Didier Lapalus Duncan Lewis Robert MacDonald David Male Charles Martin Norman May Daniel McFadden Edwin Mortlock Hiroyuki Nakase Michael S.Newman William Petit D. Phelps
27、Alan F. Rumsey Louis Sanders Carl Schwellnus Errol Taylor Carl Thompson David Thurston John Vergis Firth Whitwam When the IEEE-SA Standards Board approved this recommended practice on 12 June, 2008, it had the following membership: Robert M. Grow, Chair Thomas A. Prevost, Vice Chair Steve M. Mills,
28、Past Chair Judith Gorman, SecretaryVictor Berman Richard DeBlasio Andrew Drozd Mark Epstein Alex Gelman William R. Goldbach Arnold M. Greenspan Kenneth S. Hanus James Hughes Richard H. Hulett Young Kyun Kim Joseph L. Koepfinger* John Kulick David J. Law Glenn Parsons Ronald C. Petersen Narayanan Ram
29、achandran Jon Rosdahl Anne-Marie Sahazizian Malcolm V. Thaden Howard L. Wolfman Don Wright*Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Satish K. Aggarwal, NRC Representative Michael H. Kelley, NIST Representative Don Messina IEEE Standards Program Mana
30、ger, Document Development Patricia A. Gerdon IEEE Standards Program Manager, Technical Program Development vii Copyright 2008 IEEE. All rights reserved. Contents 1. Overview .1 1.1 General1 1.2 Scope 2 1.3 Purpose.2 1.4 Application 2 2. Normative references2 3. Definitions, acronyms, and abbreviatio
31、ns.2 3.1 Definitions .2 3.2 Acronyms and abbreviations3 4. General requirements3 4.1 Range of applications3 4.2 Operating modes .3 4.3 Failure management .4 5. CBTC system design.4 5.1 CBTC system architecture .4 5.1.1 CBTC ATS equipment5 5.1.2 CBTC wayside equipment .5 5.1.3 CBTC train-borne equipm
32、ent 5 5.1.4 CBTC data communications equipment5 5.2 Principles of operation 7 5.3 External interfaces.7 5.3.1 Interlockings.7 5.3.2 Other external wayside equipment.8 5.3.3 Train subsystems8 5.3.4 User interfaces 8 5.4 Integration with other systems .8 6. ATP functional allocations 9 6.1 Train locat
33、ion determination .13 6.1.1 CBTC train location initialization.15 6.1.2 Determine location of CBTC train.17 6.1.3 Determine occupancy status of track sections .20 6.1.4 Failure management.21 6.2 Limit of safe route determination .24 6.2.1 Determine potential limits of safe route .26 6.2.2 Determine
34、limit of safe route .28 6.2.3 Provide route status information.29 6.3 Limit of movement protection and target point determination.29 6.3.1 Determine potential limits of movement protection31 6.3.2 Determine limit of movement protection35 6.3.3 Determine target point36 6.4 ATP profile determination.3
35、7 6.4.1 Determine permanent speed restrictions 39 6.4.2 Determine temporary speed restrictions41 6.4.3 Determine braking profiles.42 6.4.4 Calculate ATP profile43 viii Copyright 2008 IEEE. All rights reserved. 6.5 Authorized speed determination44 6.5.1 Determine authorized speed .44 6.6 Actual train
36、 speed/train travel direction determination .45 6.6.1 Determine actual train speed 46 6.6.2 Determine actual train travel direction .48 6.7 Supervise/enforce authorized speed and travel direction48 6.7.1 Speed supervision 50 6.7.2 Travel direction supervision.51 6.7.3 Failure management.52 6.8 Door
37、control interlocks 55 6.8.1 Door open interlocks.57 6.8.2 Departure interlocks .59 6.8.3 Failure management.60 6.9 External interlocking commands62 6.9.1 External interlocking interface.62 6.10 Highway grade crossing warning device control/supervision65 6.10.1 Control of highway grade crossing warni
38、ng device.66 6.10.2 Supervision of highway grade crossing warning device.67 6.11 Train-borne ATP user interfaces .68 6.11.1 Train-borne ATP display data interface 68 6.11.2 CBTC train-borne ATP input data interface .69 6.12 Fixed ATP data management 69 7. ATO functional allocations.70 7.1 Determine
39、ATO profile 72 7.1.1 Determine ATO profile for starting, stopping, and speed regulation .72 7.2 Determine train berthing location 73 7.2.1 Platform berthing control73 7.2.2 Platform entry control .75 7.3 Regulate train speed .76 7.3.1 Regulate train speed in accordance with ATO profile .76 7.4 Door
40、control 77 7.4.1 Opening train/platform doors.77 7.4.2 Closing train/platform doors 79 7.4.3 Failure management.81 7.5 Train-borne ATO user interfaces.83 7.5.1 Train-borne ATO display data interface.83 7.5.2 Train-borne ATO input data interface 83 8. ATS functional allocations 84 8.1 Train identific
41、ation86 8.1.1 Determine train identification.86 8.2 Train tracking87 8.2.1 Automatic train tracking87 8.3 Train routing .88 8.3.1 Route train88 8.4 Train regulation 90 8.4.1 Automatic train regulation90 8.5 Station stop functions93 8.5.1 Stop train at next station 93 8.5.2 Hold train at station.93 8
42、.5.3 Skip station stop94 8.5.4 Door control inhibit95 8.6 Restricting train operations.96 8.6.1 Stopping/restarting a train enroute.96 ix Copyright 2008 IEEE. All rights reserved. 8.6.2 Impose/remove temporary speed restrictions 97 8.6.3 Block/unblock route/section.98 8.6.4 Establish/remove work zon
43、es .99 8.7 Passenger information system interfaces 100 8.7.1 Wayside passenger information systems100 8.7.2 Train-borne passenger information systems 101 8.8 Fault reporting 102 8.8.1 CBTC fault reporting.102 8.8.2 Train fault reporting.103 8.9 ATS user interfaces.104 8.9.1 Display data .104 8.9.2 I
44、nput data .105 9. Data flows between CBTC subsystems .106 9.1 From CBTC ATS106 9.2 From CBTC wayside .108 9.3 From external wayside110 9.4 From CBTC train-borne 111 9.5 From external train-borne.113 A.1 Introduction.114 A.2 Train orientation .114 A.3 Track segment orientation114 A.4 Train polarity.1
45、15 A.5 Train travel direction116 A.6 Summary.116 1 Copyright 2008 IEEE. All rights reserved. IEEE Recommended Practice for Communications-Based Train Control (CBTC) System Design and Functional Allocations IMPORTANT NOTICE: This standard is not intended to assure safety, security, health, or environ
46、mental protection in all circumstances. Implementers of the standard are responsible for determining appropriate safety, security, environmental, and health practices or regulatory requirements. This IEEE document is made available for use subject to important notices and legal disclaimers. These no
47、tices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html.
48、 1. Overview 1.1 General This recommended practice establishes the system design and functional allocations for a communications-based train control (CBTC) system. It is divided into nine clauses, as follows: Clause 1 describes the scope and purpose of this recommended practice. Clause 2 lists norma
49、tive references that are useful in applying this recommended practice. Clause 3 provides definitions that are either not found in other IEEE standards or have been modified for use with this recommended practice. Clause 4 provides a top-level description of operations and train operating modes to be supported by CBTC systems. Clause 5 defines the general system architecture and principles of operation for CBTC systems. Clause 6 defines the detailed automatic train protection (ATP) functional requirements for CBTC systems, including allocation of subfunctions
