RBCIL应用层接口规范

1、庞巴迪RBC IL Interface,Application layer for WuGuang DPL武广客运专线无线闭塞中心（RBC） 联锁（IL）应用层接口规范Responsible Division:责任部门Responsible Unit: 责任单位Document Type:文档类型Distribution Status:发布情况Document State: 文档状态RCSEML规范INTERNAL内部发行Released发布Prepared编撰:Majid SepehriRBCProject Engineer, WG 武广RBC项目工程师Verified:审核Jerzy Ar

2、edzkiTechnical Project Manger, WG 武广项目技术经理Approved:批准Gregory EnjalbertProject Manager, WG 武广项目经理Name / Role姓名/职位Signature签名Date日期Filename:：ea10b4e250d98c47da8e1c4826b035fd.pdf 文件名：ea10b4e250d98c47da8e1c4826b035fd.pdf庞巴迪This document and its contents are the property of Bombardier Inc. or its subsidi

3、aries. This document contains confidential proprietary information. The reproduction, distribution, utilization or the communication of this document or any part thereof, without express authorisation is strictly prohibited. Offenders will be held liable for the payment of damages. 本文档及其内容版权归庞巴迪或其子公

4、司所有。本文档包含保密的专利信息。严禁未经明确授权而复制、发布、使用或交流本文档或其中任何一部分的内容。违者将担负赔偿责任。© 2005, Bombardier Inc. or its subsidiaries. All rights reserved.© 2005，庞巴迪或其子公司版权所有。Identity Number:标识号3NSS008253D0005Effective Date:生效日期Revision:版本Language:语言2009-046-2042.98En/Cn英语/中文Filename:：ea10b4e250d98c47da8e1c4826b035fd

5、.pdf 文件名：ea10b4e250d98c47da8e1c4826b035fd.pdf3NSS008253D0005版本Revision :2.89Revision Log 修订记录Revision版本Date日期Description of Changes 更改说明1.62007-09-16Created based on 3NSS007094D0009, v1.6 Document no. changed to CWGE-2005基于3NSS007094D0009，创建1.6版本文档编号改为CWGE-20051.72007-11-20CRSC meeting 2007-11-21基于2

6、007年11月21日与CRSC（中国铁路通信信号集团公司）会议1.82007-11-23Updated after meeting Info from both IL to both RBC at RBC borders会议后的更新版本，RBC边界两端RBC与两端联锁资料1.92007-11-27Project review项目审查Replace SR with Basic/Advanced 用基本/高级替换SRChanges in the TIM/SA 更改TIM/SA Removed: RouteAnswer->SettingofOSAccepted, RouteQuestion-&

7、gt; OSRouteRequest, DegradedStatus->EMAset删除：进路回答-接受OS设置、进路问询-OS进路请求、降级情况-EMA设置Changed: RouteStatus->Used更改：进路状态-占用1.102007-12-03CRSC Scenario meeting in Stockholm与通号公司在斯德哥尔摩召开场景会议Make 4 passing through interactions通过交流制定4个越行场景Add joining, including Shunting routes增加重联，包括调车进路CKE review comment

8、s CKE 评审意见1.112007-12-062007-12-11CRSC Scenario meeting in Stockholm与CRSC在斯德哥尔摩召开场景会议CRSC Scenario meeting in Stockholm与CRSC在斯德哥尔摩召开场景会议1.122007-12-14CRSC Scenario meeting in Stockholm, aligning the contents with the Operations Scenarios document. /by Clas Kemstedt与CRSC在斯德哥尔摩召开场景会议，同时制定了场景内容文件/ 由Cla

9、s Kemstedt完成1.132007-12-18Updated after first review at CRSC Scenario meeting in Stockholm /by R Mauritzson对CRSC在斯德哥尔摩场景会议上第一次审定后内容的更新/ R Mauritzson 1.142007-12-19Updated after review at CRSC Scenario meeting in Stockholm Document number corrected.对CRSC在斯德哥尔摩场景会议上审定后内容的更新。更正文档编号。1.152007-12-20Editor

10、ial updates. 版本更新。Comments on Operational scenarios for Danger point and Signal to stop in Chapter 0 moved to the Op. Sc. document 3NSS008131D0032.对运营场景文件3NSS008131D0032第0章危险点和信号机到停车的意见。Joint reviewing team (CRSC and Bombardier) regards the document ready for approval and release.联合审核小组(CRSC和庞巴迪) 对准

11、备提交批复和发布的文档进行审核。1.162008-01-08Editorial clarifications in chapter 5. More explanations to route statuses NoRoute, Used and FailedinRoute. New table showing how variables in SA-information may be combined. Minor editorials. 在第 5章，版本明确化。增加了对进路状态、无进路、占用进路和无效进路的解释。新的表格中描述了SA信息中变量如何组合。微调。1.192008-02-21Up

12、dated after second Design Liaison meeting in Beijing. 根据在北京召开的第二次设计联络会议后进行的更新。2.02008-10-01Updated with Core RBC-1.2 changes根据核心RBC-1.2变更进行更新2.12008-11-28Updated according to CRSC (Wu Yong) request:根据通号公司（吴永）的要求更新Direction IL-> RBC compatible with RBC-1.1, deleted RouteGeneration Index方向联锁-> R

13、BC与 RBC-1.1一致，删除产生进路 索引Direction RBC-> IL comapatible with RBC-1.2方向RBC-> IL与RBC-1.2一致2.22008-12-15Reviewed by CRSC 通号公司审核Direction IL -> RBC use v1.19Direction RBC -> IL use v2.0Modify the RBC-IL Interface Adaptation compatible with Core RBC-1.1 2.32008-12-18Deleted Defualt values as su

14、ggested by CRSC above.根据通号公司的上述建议删除默认值2.42009-03-20All references to Shunting route deleted. 删除了所有与调车相关的参考资料Agreed in DL4 第四次设计联络会议上达成共识2.52009-03-25CRSC comment in DL4: 通号公司在第四次设计联络会以上的意见：Route type Berth section cannot change status to Used,进路分类的“停车区”状态不能改为“占用”2.5.12009-04-01Translated version 翻译版

15、2.62009-04-02NCR arn_023#337 Section 8.2.2 updated:SRS-389When a train communication session is closed, then RBC shall de-register the train and notify the CTC.若RBC与列车通信会话关闭，则RBC应注销该列车并通知CTC。2.72009-04-08Tord review commentsSection 8.2.2 updated:SRS-1057When the RBC considers the connection to the i

16、nterlocking lost, then the RBC shall send an alarm to the CSM.若RBC认为与联锁的某连接通道故障，则RBC应向CSM发送报警。SRS-1056When the RBC considers the session to the interlocking terminated, then the RBC shall send an alarm to the CTC and CSM.若RBC认为与联锁的通信中断，则RBC应向CTC和CSM发送报警。SRS-1068When the RBC considers the session to

17、the interlocking terminated, then the RBC shall stop sending messages to all trains with position in the area controlled by the interlocking.若RBC认为与联锁的通信中断，则RBC应停止向位于该联锁控制区域内的所有列车发送消息。SRS-1069When the RBC considers the session to the interlocking terminated, then the RBC shall stop sending messages

18、to all trains with MA having extended into the area controlled by the interlocking.若RBC认为与联锁的通信中断，则RBC应停止向MA已经延伸到该联锁控制区域内的所有列车发送消息。2.82009-04-20CRSC comment and Chinese translation updated.2.92009-06-24CRSC requests to compact data size in message SAM and EAMTable of Contents目录Section章节Subject题目Page

19、页码Revision Log 修订记录3Table of Contents目录71Definitions and Abbreviation 定义和缩写92References参考文件103INTRODUCTION引言104Connection/Transmission连接/传输114.1General概述114.2External Identity 外部标识124.3Direction from the IL to the RBC从联锁到无线闭塞中心方向124.4Direction from the RBC to the IL从无线闭塞中心到联锁方向134.5Connection Status

20、连接状态145Basic concepts基本概念155.1Object model对象模型155.2SA-signal SA信号155.3EMA object EMA对象176Detailed Information详细信息186.1General概述186.2Train status列车状态196.3Signalling Authorisation信号授权246.4Emergency Area紧急区域337Miscellaneous其它情况357.1Calling-on route引导进路357.2Successive route 延续进路357.3Approach locking接近锁闭

21、368Safety 安全378.1IINTERLOCKING 联锁378.1.1IINTERLOCKING restart 联锁重启378.1.2RBC or RBC - IINTERLOCKING communication out of function RBC或RBC-联锁通信失效378.2RBC378.2.1RBC restart RBC重新启动378.2.2IINTERLOCKING or IINTERLOCKING - RBC communication out of function 联锁或联锁-RBC通信失效371 Definitions and Abbreviation 定义

22、和缩写Definitions and abbreviations specific for this document can be found in table below. 本文件中所使用的定义和缩写见下表。Term术语 Definition定义CEMConditional Emergency Stop Message有条件的紧急停车消息CTCCentralised Traffic Control调度集中控制DPLDedicated Passenger Line客运专线EMAEmergency Area 紧急区域GALGeneric Application Layer 通用应用层ILInt

23、erlocking联锁MAMovement Authority移动授权N/ANot Applicable不适用RBCRadio Block Centre无线闭塞中心SASignalling Authorisation信号授权SAMSignalling Authorisation Message信号授权消息SMAShortened Movement Authority短移动授权TBDTo Be Determined待定TIMTrain Information Message列车信息消息2 References参考文件Reference / Document Name参考文件/文件名称Docume

24、nt Id文件编号1 ETCS Safe Communication Interface欧洲列车控制系统安全通信接口Subset 098098子集2 Generic Application Layer Interface GAL, Adapted to STP 2.x usageRBC_IL Generic Safety Layer Interface GAL无线闭塞中心联锁通用安全层接口-通用应用层接口，STP 2.x适配3NSS008527D0006CWGE-20203 INTRODUCTION引言The purpose with this document is to define th

25、e application level of the interface between the Radio Block system (RBC) and the Interlocking System (IL) in the WuGuang DPL project.本文档旨在定义武广客运专线项目中无线闭塞中心系统(RBC)与联锁系统（IL）之间的应用层接口。4 Connection/Transmission连接/传输4.1 General概述This document specifies the interface between the application layers in the

26、IL and RBC (see Figure 3-1). 本文档旨在规范联锁和无线闭塞中心的应用层之间的接口（见图3-1）。 Figure 3-1 Communication architecture 图3-1 通信结构The communication between the IL and the RBC is according to behaviour 3 in RBC_IL Generic Application Layer, ref. 2.联锁和无线闭塞中心之间的通信参照 RBC_IL通用应用层协议的情况3进行（参考2）。The transmission system shall b

27、e safe in the sense that a message received by either the IL or the RBC can be trusted. 传输系统应该是安全的，无论联锁还是RBC均可认为其收到的消息都是可信的。The lower levels of the interface shall comply with requirements in the ETCS standard, Subset 098.下级接口层应该遵照欧洲列车控制系统标准中第098子集的要求。Absence of a message gives no information to the

28、 receiver, this is the safe state. It is up to the receiving party to assess how long time it can rely on a previously given information.消息缺失接收方将收不到任何信息，这是一种安全状态。这取决于接受方估计它可以依赖前一条信息多长时间。4.2 External Identity 外部标识Each common object exchanged over the interface has a, for the interface, unique identif

29、ier.在接口中交换的每个通用对象都有一个唯一的标识符。4.3 Direction from the IL to the RBC从联锁到无线闭塞中心方向The transmission in this direction is cyclically driven by the IL program cycle. The states of all active objects are sent each cycle from the IL. Each cycle shall be 300 ms. If no object is active an empty message is sent.

30、The RBC needs to change its stored information only when there is a change. If more than 1000 ms has gone since the RBC received the latest message from the IL, the RBC will consider absence of message. This means that two messages can be lost, after 300 ms and after 600 ms. If a third message is re

31、ceived after 900 ms, the RBC will not consider absence of message.在该传输方向上，联锁程序将循环发送消息。此情况中的所有活动对象由联锁系统在每一个循环中发送。每个循环为300毫秒。如果没有任何活动的对象，则发送一个空消息。只有在有变化时，无线闭塞中心才需要修改其所存储的信息。如果无线闭塞中心收到联锁最后的命令1000毫秒后，RBC将认为消息缺失。这就意味着两个消息可能丢失，在300毫秒后的和600毫秒后的。如果在900毫秒后，接收到第三个消息，则无线闭塞中心不会认为消息缺失。In case of absence of a mes

32、sage (data timeout on the application level or loss of connection as reported by lower levels of the interface) all RBC inputs are set to safe states. 当消息缺失（数据在应用层超时或者下级接口层向上报告连接过程丢失）时，无线闭塞中心的所有输入将被置为安全状态。The variable values with priority default in the tables below shall be considered as the safe s

33、tates. Note that some of the Default values are safe only when other variables in the interface from the IL to RBC take default values. For example for DegradedStatus the default value NoDefault is safe only if the takes the default value NoRoute. For Emergency Area Status the default value “The obj

34、ect is inactive” is safe only if all SA-signals related to the area take the default value NoRoute.在下表中拥有优先级的默认变量值应该被认为是安全状态。注意，仅当在从联锁到无线闭塞中心接口中的其他变量也使用默认值时，一些默认的变量值才是安全的。例如，仅当使用默认值“无进路”时，“状态降级”的默认值“非默认”才是安全的；对于紧急区域来说，仅当与此区域相关的所有SA-信号都使用默认值“无进路”时，默认值“此对象是非活动的”才是安全的。With exception to the rule for rou

35、te status “NoRoute” the RBC shall not send any message at all to any train until the communication has been re-established and all inputs have been refreshed by new information from the Interlocking.除进路状态“无进路”规则之外，无线闭塞中心将不会向任何列车发送任何信息，直到重新建立通信，对由联锁输入的所有信息进行刷新。The states of all active objects are sen

36、t as they are at the time of sending. Intermediate state transitions may be lost.在预定的信息发送的时候，所有活动对象的状态将被一次发送。中间转换情况可能丢失。If more than one batch of messages is received all messages have to be checked but only the latest one shall be used and all others shall be discarded.如果同周期收到的信息超过一组，则所有信息都必须被检查，只使

37、用最新的一组信息，并删除其它信息。4.4 Direction from the RBC to the IL从无线闭塞中心到联锁方向The transmission in this direction is event driven. All active objects are sent when one of them has changed, or latest after 1000 milliseconds if no change has happened before.此方向上的传输是由事件驱动的。如果任何一个活动对象发生变化，或者最近的1000毫秒后没有任何变化发生时，所有的活动对

38、象将被发送。If more than 3500 ms has gone since the IL received the latest message from the RBC the IL will consider absence of message. This means that two messages can be lost, after 1000 ms and after 2000 ms. If a third message is received after 3000 ms, the IL will not consider absence of message.当联锁从

39、无线闭塞中心收到最新的消息超过3500毫秒后，联锁将认为消息丢失。这就意味着两个消息可能丢失，分别在1000毫秒后和2000毫秒后。如果在3000毫秒后接收到第三个消息，则联锁不会认为消息丢失。In case of absence of a message (data timeout on the application level or loss of connection as reported by lower levels of the interface) safe states shall be used by the IL. The variable values with pr

40、iority default in the table below shall be considered as the safe states. Note that the default value for MAStatus NoMA is safe only if all manual route release is done with time delay in case of absence of message from the RBC.当消息丢失（数据在应用层超时或者下级接口层向上报告连接过程丢失）时，联锁的所有输入将被置为安全状态。在下表中拥有优先级的默认变量值应该被认为是安

41、全状态。注意，对于默认值“移动授权状态”，仅当在无线闭塞中心的消息丢失的，所有手动进路都在时间延迟内完成解锁的情况下， “无移动授权”才是安全的。The states of all active objects are sent as they are at the time of sending. Intermediate state transitions may be lost. Note that the position and speed values reported from trains may be some seconds old.在预定的信息发送时候，所有活动对象的状态

42、将被一次发送。中间转换情况可能丢失。注意，从列车上报告的位置和速度值可能是数秒之前的旧数值。If more than one batch of messages is received all messages have to be checked but only the latest one shall be used and all others shall be discarded.如果一个周期内收到的信息超过一组，则所有信息都必须被检查，但只使用最新的一组信息，并删除其它信息。4.5 Connection Status连接状态The transmission system must

43、maintain a connection status in the IL and in the RBC, informing whether the transmission is functioning or not. This status shall reflect that information can flow from the IL to the RBC, as well as from the RBC to the IL. 在联锁和无线闭塞中心系统中，传输系统必须维护一个连接状态，以确认传输功能是否正常。该状态必须能够反映出信息可以从联锁到无线闭塞中心，也可以从无线闭塞中心

44、到联锁。The lower transportation levels of the communication layers must detect loss of communication within a configurable time and indicate this status to the application upon request. This configurable time shall be set at 5 s.通信层的较低传输层必须能在可配置时间内检测到通信丢失的状态，并根据请求将状态显示给应用层。可配置的时间值应设置为5秒。A connection st

45、atus field readable in the IL must be updated at all times. Status UP shall be read when the connection is alive and information has been received from the RBC. Status DOWN shall be read as soon as the connection is not alive. 必须实时更新一个可以被联锁系统读取的连接状态字段。当连接正常，所发送的信息可以被无线闭塞中心接收时，状态UP应被读取。一旦连接中断，状态 DOWN

46、应立即被读取。A connection status field in the RBC application must be updated at all times indicating UP when the level communication layer is connected and data has been received from the IL. Status DOWN shall be read as soon as the connection is not alive.当通信层的较低层已建立连接，并从联锁收到数据时，在无线闭塞中心应用层中的连接状态字段必须实时更新

47、指向UP，一旦连接中断，状态 DOWN应立即被读取。In case the communication has status DOWN the application (in both IL and RBC) shall initiate the communication set up. 当通信状态为DOWN时的应用层（包括联锁和无线闭塞中心）应启动通信建立过程。5 Basic concepts基本概念5.1 Object model对象模型The IL and the RBC both work with objects in a geographical model of the tra

48、ck layout. The two models, one in the RBC and one in the IL must use common objects used for exchange of information. 联锁和无线闭塞中心都应使用布局图中的地理模型对象。在无线闭塞中心与联锁中的两个模型，必须使用通用对象来交换信息。The Common Object Model consists of: 通用对象模型由以下部分组成：· SA-signals (IL <-> RBC) - throughout this document all common

49、objects for transfer of route and train information in the interface are called SA-signals,SA-信号 (联锁<->无线闭塞中心) 此文档中，所有在接口中用于传递进路和列车信息的通用对象都被称为SA-信号。· EMA-object (IL -> RBC) emergency area information in the interface is called EMA-objects 紧急区域-对象 (联锁<->无线闭塞中心)-接口中的紧急区域信息被称为紧急区域-对

50、象。5.2 SA-signal SA信号The SA-signal is an object used in the interface for transfer of information, in direction from the IL to the RBC and from the RBC to the IL. The information concerns the route or block section leading to the SA-signal.SA信号是一个在接口中传递信息的对象，方向为从联锁到无线闭塞中心以及从无线闭塞中心到联锁。此信息包括了终止于SA信号的进路

51、或闭塞分区。 An SA-signal has only one direction. If routes from both directions can end at the same position (route border or block section border) then one SA-signal for each direction must be defined in the interface between the IL and the RBC.一个SA-信号只有一个方向。如果两个方向的进路在同一位置结束（进路临界处或闭塞分区临界处），则联锁和无线闭塞中心之间的

52、接口中每个方向的SA信号必须被分别定义。An SA-signal corresponds to a signal in a station or to a block border on the open line. SA-signals are defined for both running directions at all block borders. 一个SA信号对应车站里的信号机或区间线路上的闭塞边界。在所有闭塞边界上，SA信号在两个运行方向上定义。The section between two track-wise consecutive SA-signals in the sa

53、me direction is an SA-section. An SA-section starts at one SA-signal and ends at the next SA-signal in the same direction. The SA-signal at the end of the SA-section identifies the SA-section and carries information between the RBC and the IL. 在相同方向的两个连续SA信号中的区段是一个SA区段，一个SA区段开始于一个SA信号，结束于同一方向的后一个SA信

54、号。SA区段末端的SA信号用于标识SA-区段并传送无线闭塞中心和联锁之间的信息。Note that by using the SA-signal at the end of the SA-section as identifier, the identification is valid also when the first section of the route has been released.注意，由于使用SA-区段末端的SA-信号作为标识符，进路的首个区段被解锁时此标识同样有效。The SA-section may have the same extent as a define

55、d CTC route but is more often a part of a CTC route. It is the smallest sub-route (basic route) that can be used for transfer of signalling information to the RBC or from the RBC to the IL. An SA-section can be seen as a small route in the signalling sub-system, allowing differentiated signalling in

56、 a longer CTC route.SA-区段可以和规定的调度集中控制进路的范围一样大小，但是通常它只是调度集中控制进路的一个部分。最小的子进路（基本进路）可以被用来向无线闭塞中心或者从无线闭塞中心到联锁传送信令信息 一个SA-区段在信令子系统中被看作是一个小型的进路，允许不同的信令在一个较长的调度集中控制进路中存在。In case there are points within an SA-section there may be several SA-sections ending at the same SA-signal. An additional identification

57、of the SA-section is then needed. Each possible route ending at the SA-signal is given an index number in site data. This variable is called SAId. If there is only one possible route the index number shall be 1.对于SA区段有道岔的情况，会存在多个SA区段在同一个SA信号上结束的情况，这时就需要一个附加标识。在现场数据中，每一条终止于该SA信号上的可能进路都被赋予一个索引编号。这个变量被称作SAId。如果只有一个可能的进路，索引编号应为1。When a route is set, the IL will give an SA for every