UNISIG Class 1互操作性规范：SUBSET-026-5 v300的系统要求与修订历史

需积分: 25 182 浏览量更新于2024-07-15 收藏 486KB PDF 举报

SUBSET-026-5 v300是一份关于UNISIG Class 1范围内互操作性的规范文档，由ERA*UNISIG*EEIGERTMSUSERSGROUP制定。该文档详细定义了系统需求规格，特别是针对Chapter 5的Procedures部分，共涉及81页，涵盖了ERA*UNISIG*EEIGERTMSUSERSGROUP对标准化的通信系统的修改历史、版本更新和状态转换图表。文档的核心内容包括以下几个要点： 1. 系统要求规格：文档定义了Class 1的系统所需的基本功能和标准，旨在确保不同系统间的兼容性和一致性。章节5集中于具体的操作程序，每个程序都由强制性要求和/或状态转换图（当适用时）来表述。 2. 版本更新历史：从0.0.1版本开始，文档经历了多次迭代，反映了根据Class 1提案进行的更新（1.1.1版本）、根据7月22/23会议决定的修订（0.1.0版本），以及在Stuttgart召开的最终化会议（1.0.0版本）。此后，版本号不断更新，直到1.3.0版本，这是基于12月15/16日评审会议的决策。 3. ECSA/UNISIG数据库的参与：在1.2.1版本中，文档根据ECSA/UNISIG数据库中的“一般”类别提议和评论进行了更新，显示了与行业组织合作的重要性。 4. 调试和改进：2.0.0版本标志着正式发布，随后的更新如2.0.1和2.1.0则包含了调试决策和进一步优化，直至10月17日。这份文档对于理解和实施UNISIG Class 1通信标准至关重要，它不仅定义了技术上的操作流程，还记录了标准演进的历史，以便用户和开发者了解当前的最佳实践和未来可能的改动方向。对于IT专业人员和系统集成者来说，掌握这份文档中的规定是实现设备间无缝协作的关键。

ERA * UNISIG * EEIG ERTMS USERS GROUP

SUBSET-026-5

3.0.0

23/12/08

System Requirements Specification

Chapter 5

Procedures

Page 14/81

ID in Flow

Chart

Requirements

S23

The ERTMS/ETCS on-board equipment shall require an acknowledgement from the

driver for running in Unfitted mode. When the driver acknowledges (E31), the mission

starts in Unfitted mode (refer to SRS chapter 4, transitions between modes: transition

from SB to UN)

Following E31, if the position is still invalid, the ERTMS/ETCS on-board shall delete

the train position data (new status: “unknown”)”

S24

The ERTMS/ETCS on-board equipment shall require an acknowledgement from the

driver for running in Staff Responsible mode. When the driver acknowledges (E32),

the mission starts in SR mode (refer to SRS chapter 4, transitions between modes:

transition from SB to SR)

Following E32, if the position is still invalid, the ERTMS/ETCS on-board shall delete

the train position data (new status: “unknown”)”

S25

The ERTMS/ETCS on-board equipment shall require an acknowledgement from the

driver for running in On Sight/Limited Supervision/Shunting mode. When the driver

acknowledges (E33), the mission starts in On Sight/Limited Supervision/Shunting

mode (refer to SRS chapter 4, transitions between modes: transition from SB to OS or

SH)

A31

The ERTMS/ETCS on-board equipment shall open the session with the RBC.

If driver has entered a new Radio Network ID (see S3), registration of Mobile

Terminal(s) to this new Radio Network shall be ordered prior to the establishment of

session with RBC.

D31 If the opening of the session is successful, the process shall go to D32

If the opening of the session has failed, the process shall go to A32

A32

The driver shall be informed when the on-board equipment fails to open a radio

session.

Opening of a radio session has failed if

• No connection to the RBC can be established (see section 3.5.3.7) OR

• The ERTMS/ETCS on-board equipment, based on the system configuration

reported by the RBC, decides that compatibility is not ensured and terminates the

communication session

This condition leads to S10 (The driver has to unlock the situation to continue e.g.

selection of new level).

D32 If the stored position is valid, the process shall go to A33

If the stored position is invalid, the process shall go to A34

A33

If the train position data stored in the on-board equipment is of status “valid”, the train

position, marked as “valid” shall be transmitted to the RBC via the "SoM position

report" message.

This condition leads to S10.

ERA * UNISIG * EEIG ERTMS USERS GROUP

SUBSET-026-5

3.0.0

23/12/08

System Requirements Specification

Chapter 5

Procedures

Page 15/81

ID in Flow

Chart

Requirements

A34

If the train position data stored in the on-board equipment is of status “invalid” or

"unknown", the train position, marked as “invalid” or "unknown" shall be transmitted to

the RBC via the "SoM position report" message.

The process shall then go to D33

D33

When the position report marked as "invalid" is received by the RBC, this latter shall

check whether it can validate this position report.

If the position report can be validated by the RBC, the process shall go to A35

Otherwise, if the position report was marked "unknown", or the "invalid" position report

cannot be validated by the RBC, the process shall go to D22

Note: How the RBC is able to validate the position report is a national issue, out of

the scope for this specification

A35

The RBC shall inform the ERTMS/ETCS onboard equipment that the reported position

is valid.

When this message is received by the ERTMS/ETCS on-board equi

pment, the status

of the position shall be set to "valid"

The procedure shall go to S10.

D22

If the reported train position is "unknown", or the RBC is not able to confirm a reported

"invalid" position, the RBC shall nevertheless decide whether it accepts the train or

not.

If yes, the process shall go to A23

If no, the process shall go to A38

Note: How the RBC assumes responsibility for the train is a national issue, out of the

scope for this specification

A23

The RBC shall inform the ERTMS/ETCS on-board equipment that it accepts the train

although the on-board has no "valid" position information.

A24

When the ERTMS/ETCS on-board equipment is informed that the train is accepted

without valid position data, it shall delete the train position data (new status:

“unknown”)

This condition leads to S10.

A38

The RBC shall inform the ERTMS/ETCS on-board equipment that it rejects the train

A39

When the ERTMS/ETCS on-board equipment is informed that the train is rejected, it

shall delete the train position data (new status: “unknown”) and shall terminate the

session with the RBC.

The process shall then go to A40

ERA * UNISIG * EEIG ERTMS USERS GROUP

SUBSET-026-5

3.0.0

23/12/08

System Requirements Specification

Chapter 5

Procedures

Page 17/81

5.4.3.3 Status of On-board Variables Affected by Start of Mission Procedure

State of On-board Variables

ERTMS/ETCS

Level

RBC ID/Phone

Number

Train position

data

Driver ID Train Data Train Running

Number

Transition conditions

Un-known

Invalid

Valid

Un-known

Invalid

Valid

Un- known

Invalid

Valid

Un- known

Invalid

Valid

Un- known

Invalid

Valid

Un- known

Invalid

Valid

Following S1 : Driver has

entered driver ID



Following S1 : Driver has re-

validated/ re-entered driver



Following S1 : Driver has

entered Train running

number

•

Following S1: Driver has re-

validated/ re-entered Train

running number

•

Following S1 : Driver elects

not to capture Train running

number

•

S2: Driver inhibits the

current level

•

Following S2 : driver has

entered level



Following S2 : driver has re-

validated/ re-entered level



S3: driver has re-entered a

Radio Network ID



Following S3 : driver has

entered RBC ID/Phone

Number



Following S3: driver has re-

validated/re-entered RBC

ID/Phone Number



Following D31: session has

been successfully opened



Following D31: session has

been successfully opened



A35 : RBC reports to On-

board : position valid



A24 : On-board deletes

stored position data



A39 : On-board terminates

session, deletes stored

position data



Following E10, E12, E15,

E30, E31, E32, On-board

deletes stored position data



Following S12: Train Data

have been entered



剩余80页未读，继续阅读

willnquaker

粉丝: 0
资源: 4

UNISIG Class 1互操作性规范：SUBSET-026-5 v300的系统要求与修订历史

ETCS/ERTMS系统原理：SUBSET-026-3 v300 版本3概述

掌握is-subset-of：验证数组或对象子集的方法

is-subset-of：验证数组或对象是否为子集的工具介绍

SUBSET-026-4 v300.pdf

SUBSET-026-2 v300.pdf

SUBSET-026-3 v300.pdf

ETCS SRS SUBSET-026-1 v300

3_Sample-Superstore-Subset-Excel.xlsx

实践题1：Sample-Superstore-Subset-Excel.xlsx

redis-desktop-manager-2019.4.0.exe

最新资源