hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.4 Post-conditions | Remote control communication for the engine is established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.11.2-001]
Upon a request received from an authorised FRMCS User, the FRMCS System shall establish or terminate communication for remote control of engines communication.
A
Covered
22.280
Covered by
[R-5.21.1.2-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely initiate an MCX Service Private Communication or MCX Service Group Communication from another user’s MCX UE.
[R-5.21.2.1-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely terminate an MCX Service Private Communication or MCX Service Group Communication from another user’s MCX UE.
[R-6.11.2-002]
The FRMCS System shall support engine remote control communication in both On-network and off-network communication mode.
A
Covered by
22.280
As the whole section 5 is applicable for both on-network and off-network. i.e., “MCX Service requirements common for on the network and off the network”
So the requirements (” [R-5.21.1.2-001] and[R-5.21.2.0-001]) are naturally supported by on/off – network communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12 Automatic Train Operation data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.1 Introduction | In this chapter the use cases related Automatic Train Operation (ATO) communication are described, the following use cases are identified
• Initiation of an Automatic Train Operation data communication
• Termination of an Automatic Train Operation data communication
Note: A plain 3GPP bearer is requested below, as additional layers such as MCData are adding additional hurdles in achieving certification by railway regulatory authorities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.2 Description | Automatic Train Operation (ATO) is the application which performs some or all the functions of automatic speed regulation, accurate stopping, door opening and closing, performance level regulation, and other functions assigned to a train driver or train attendant.
Some ATO systems require radio communication to interchange performance and/or safety relevant data between a train and the corresponding trackside control center.
The (FRMCS) users in this case are the ATO application both on-board of the train and in the control center at the trackside (ground system).
ATO systems may require communication between on-board applications of different trains (on-network).
Some modes of ATO operation require real time video between a train and the corresponding trackside control center. Please refer to the Real Time Video streaming use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3 Use case: Initiation of an Automatic Train Operation data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.1 Description | The FRMCS Application is able to initiate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.2 Pre-conditions | The initiating functional identity is authorised to initiate the automatic train operation data communication to the trackside control centre. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.3 Service flows | The initiating FRMCS Application (e.g. on-board of the train) initiates the Automatic Train Operation data communication to the receiving side (e.g. control centre at the trackside). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.4 Post-conditions | ATO communication is established.
Data can be exchanged between the Automatic Train Operation applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.12.3-001]
Upon request received from a functional identity entitled to set up ATO communication the FRMCS System shall be able to setup and terminate a data bearer for ATO operation of a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 5.5.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13 Monitoring and control of critical infrastructure related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.1 Introduction | In this chapter the use cases related to monitoring and control of critical infrastructure communication are described. The following use cases are identified
• Initiation of Monitoring and control of critical infrastructure communication
• Termination of a Monitoring and control of critical infrastructure |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2 Use case: Initiation of a Monitoring and control of critical infrastructure communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.1 Description | This use case enables FRMCS to setup data communication between infrastructure systems and a ground based or train based system in order to monitor or control critical infrastructure such as train detection, signals and indicators, movable infrastructure, level crossing elements, including barrier controls vehicle sensors, lighting controls and alarms. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.2 Pre-conditions | The initiating application is authorised to initiate Monitoring and control of critical infrastructure communication.
The receiving application is authorised to use the Monitoring and control of critical infrastructure communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.3 Service flows | The initiating application initiates the monitoring and control of critical infrastructure communication to the receiving side. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.4 Post-conditions | Monitoring and control of critical infrastructure data is made available to the application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.13.2-001]
Upon request from an authorised FRMCS Application the FRMCS System shall be able to establish data communication between a FRMCS Equipment and a central monitoring infrastructure system for monitoring and controlling critical infrastructures.
A
Covered by 22.282
[R-6.1.2.1.2-001] The MCData Service shall enable the control of robots.
1) A FRMCS Equipment can be seen as a certain kind of robots.
[R-6.1.3.2-001] The MCData Service shall provide a means to share in real-time operational status information between members of a selected group.
2) Sharing the operational status information can be seen as monitoring.
[R-6.13.2-002]
The FRMCS System shall setup the monitoring of critical infrastructure communication with an operator defined QoS and priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
Mission critical is already supported by 3GPP QoS (QCI or 5QI)
[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
See section 12.10 below. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3 Use case: Termination of a Monitoring and control of critical infrastructure communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.1 Description | Terminate data communication between infrastructure systems and a ground based or train-based system used to monitor or control critical infrastructure. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.2 Pre-conditions | The Monitoring and control of critical infrastructure applications have an ongoing data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.3 Service flows | One of the communication entities terminates the monitoring and control of critical infrastructure communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.4 Post-conditions | The terminating Monitoring and control of critical infrastructure application entity is disconnected from the receiving application entity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.13.3-001]
The FRMCS System shall be able to terminate data communication between the infrastructure systems and a central monitoring infrastructure system upon request by either communication partner.
A
Covered by 22.280, 22.282,
TS 22.280 [R-6.7.6-002] The MCX Service shall provide a means by which an MCX User ends a Private Communication (without Floor control) in which the MCX User is a Participant. TS 22.282
[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being sent and cancel streaming of data remaining buffered in the system waiting to be streamed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14 Use case: Data transmission in real time | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.1 Description | This use case allows the authorized FRMCS Users to exchange data in real time from each other, for example, health and status of train are transferred between intelligent on-train systems and train maintenance. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.2 Pre-conditions | The user A is authorized FRMCS User (e.g., administrator who has authorization to the data).
User B is an equipment for monitoring the train.
User C is a normal FRMCS User (e.g., user without authorization to the data) |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.3 Service flows | User A requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
User B receives the request from User A and accepts the request.
User B starts to transmit the requested data in real time to User A.
User C requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
User B receives the request from C and rejects the request (e.g., without authorization to the data).
User C receives a notification that the request was rejected by User B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.4 Post-conditions | The data of User B is sent to User A in real time.
The data of User B is not sent to User C in real time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.14.5-001]
The FRMCS System shall enable an authorized FRMCS User to request another FRMCS User to establish real time data transmission.
A
TS 22.282
Covered by 22.282 [R-5.5.2-003]: remote initiation of MCData Point-to-point IP connectivity between two MCData Users
[R-6.14.5-002]
The FRMCS System shall provide a list of identities for the requesting authorized FRMCS User to select from. The list may contain functional identities, FRMCS User identities, or FRMCS Equipment Identities
A
TS 22.280
Covered by functional alias requirements.
[R-6.14.5-003]
The real time data request shall either be based on the functional identity, FRMCS User Identity, or FRMCS Equipment Identity.
A
TS 22.280
[R-5.9a-002] If the MCX Service system supports functional aliases, the MCX User shall be reachable by its functional alias(es).
Functional Alias is specified by merging functional identity, user identity, and equipment identity.
[R-6.14.5-004]
The FRMCS User shall be able to accept a real time data transmission request.
A
TS 22.282
Only an authorised person can enable authorisation of IP connectivity to a specific destination.
[R-6.14.5-005]
The FRMCS User shall be able to reject a data in real time transmission request.
A
TS 22.282
Only an authorised person can revoke authorisation of IP connectivity to a specific destination.
[R-6.14.5-006]
The requesting FRMCS User shall be notified if the request is rejected or ignored.
A
TS 22.282
Implicit requirement. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15 On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | 6.15.1 Introduction
This use case is based on the International Union of Railways User Requirements Specification on FRMCS [15].
It is considered as a necessary scenario in China railway market that an authorised controller shall be able to set up a voice communication to a driver. As stated in URS 2.0, this application allows an authorised controller to establish voice communication with the driver of a specific train for operational purposes, for example to support the transfer of orders, to advise of delays, reporting of a disturbance, assault or staff security support.
The controller shall be able to call the drivers located in the area managed by the controller.
The controller can initiate the voice or video call to the drivers using the function alias.
The following use cases related to the function of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers are defined.
• Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
• Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2 Use case: Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | 6.15.2.1 Description
An authorised Controller shall be able to set up a voice or video communication to the drivers within a configured area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.2 Pre-conditions | The authorisation application authorises the Controller to call the drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.3 Service Flows | Controller(s) to Drivers
The Controller initiates the voice or video communication to the drivers. The priority of the communication is managed by the prioritisation application.
The FRMCS System determines the drivers, based on:
• Location information of the train provided by the locations services application, and/or
• Functional identity provided by the Role management and presence application.
• System configuration (To identify which Controller is responsible for which part of the track/station/etc.)
The FRMCS System establishes the voice or video communication to the drivers within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Drivers and Controller. Also, the location of the Drivers is presented to the Controller which is retrieved from the location services application.
If the controller is connected to more than one train, the multiuser talker control application is used.
The voice or video communication is recorded by the Voice or video recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.4 Post-conditions | The controller is connected to the requested drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.15.2-001]
For Controller to drivers voice or video communication, the FRMCS System shall be able to determine the responsible driver(s), based on the location of the train and/or the function alias and/or the System configuration on the Controller who is responsible for which part of the track/station/etc.
A
22.280
6.6.4.2 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3 Use case: Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.1 Description | Only the controller can terminate the On-train incoming voice or video communication from the Controller(s) of the train towards the drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.2 Pre-conditions | The controller is connected to the requested drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.3 Service Flows | Only the controller is able to terminate the voice or video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.4 Post-conditions | The controller terminates the voice or video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.15.3-001]
For Controller to Driver communication, only the controller shall be able to terminate the On-train incoming voice or video communication.
A
22.280
R-5.9a-012a
R-5.9a-012b |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16 Use cases on data communication for Train Operation System Communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.1 Introduction | In this chapter the use cases related to data communication for Train Operation System are described. The following use cases are identified:
• Train dispatch order data communication between driver and controller
• LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive
• Data communication for Security use cases between two approaching trains |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2 Use case: Train dispatch order data communication between controller and driver | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.1 Description | In this use case, the FRMCS system transmits the train dispatch order between Controller and Driver, including train orders, station receiving route, running tokens, etc.
It is needed that the information are received in due time by the driver to avoid any collision with any other train standing in another lines. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.2 Pre-conditions | User A and User B are authorized FRMCS User.
User A is a Driver entering in the train station.
User B is Controller of the train responsible for the train’s current area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.3 Service flows | User B initiates a data communication to User A in order to send station route within short time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.4 Post-conditions | User A receives the station line to follow when entering in the train station. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.2-001
The FRMCS system shall support data communication between Controller and Driver with a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3 Use case: LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.1 Description | The multi-headed locomotive has several engines, all the engines act synchronized as the LOCOTROL information will be sent between engines through FRMCS system.
It is quite important to ensure this LOCOTROL information is sent to the corresponding locomotives safely and in an integrated way so that synchronized actions can be taken. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.2 Pre-conditions | User A and User B are authorized FRMCS User.
User A is a leading locomotive.
User B is a subordinate locomotive. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.3 Service flows | User A initiates a data communication to send the LOCOTROL information to transport information regarding synchronization with the User B in safely and timely method, e.g., with a QoS and priority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.4 Post-conditions | User B receives the LOCOTROL information, so User B can be kept synchronized with User A. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.3-001
The FRMCS system shall provide a mean to exchange messages between different FRMCS Equipment with a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4 Use case: data communication for security between two approaching trains | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.1 Description | This use case describes data communication between FRMCS Users in order to avoid train accident, for example, two trains exchange warning data to each other when one train is approaching to another train.
And it is also used for the case that different devices in different carriages send detection data to head device in the train, so that the Driver can take appropriate actions.
This data information needs to be transported in a safe and timely manner so that the train can operate in a safe way. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.2 Pre-conditions | User A, User B, User C and User D are authorized FRMCS Users.
User A is a Driver of train A.
User B is FRMCS Equipment used for detection of the environment (sensor).
User C is a Driver of train B.
Train A is approaching to train B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.3 Service flows | Train driver User A initiates a data communication to the other train driver User C to indicate the approaching event to train B.
The sensor User B initiates a data communication to train driver User A, to report what User B detected if some threshold is reached.
These two communications are transported in safely and timely method |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.4 Post-conditions | Train driver User C receives the approaching event and takes appropriate action.
Train driver User A receives the massage from sensor User B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.4-001
The FRMCS system shall support data communication between FRMCS Users with a QoS, priority and setup time as defined in clause 12.10
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17 On-train safety device to ground communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.1 Introduction | Based on a critical situation in the train (for example, triggered by a Driver Safety Device (DSD) or Dead Man Switch, a voice and/or data communication is automatically set up towards a ground user (controller or ground system).
In this chapter the use cases related to On-train safety device to ground communication are defined. The following use case describes:
• Initiation, termination of the On-train safety device data communication
• Voice communication between driver/train staff and controller/train control system |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2 Use case: Initiation of safety device to ground data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.1 Description | 1.) Based on a train safety issue, the Driver Safety Device will automatically establish a data communication to FRMCS User(s) at the ground (controller or train management system). The functional identity of the DSD and other FRMCS User(s) at the train are indicated to the FRMCS User(s) at the ground.
2.) On demand a voice communication can be established by the train staff (FRMCS User) or the FRMCS User at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.2 Pre-conditions | The FRMCS User at the train is authorised to initiate Driver Safety Device data communication.
The FRMCS User at the ground (controller or train management system) is authorised to receive Driver Safety Device data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.3 Service flows | If the driver is not reacting to the DSD, the Driver Safety Device (FRMCS User) may initiate a data communication to the FRMCS User at the ground to notify the controller or train management system about the safety issue of a running train.
After reception of this train safety issue, other trains in the same area get notified by an emergency alert to lower the instantaneous velocity of the train or stops completely.
The FRMCS User at the ground (controller or train management system) acknowledges the reception of DSD emergency notification. The DSD emergency notification remains active and is continuously transmitted until the train safety has been recovered.
In addition, the entitled train staff or entitled ground staff establishes a voice communication to commence further steps, to recover train safety again. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.4 Post-conditions | The emergency didn’t cause a safety issue at other trains as well as the people in those trains. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.17.2-001]
The FRMCS Equipment shall be able to integrate the Driver Safety Device (DSD).
A/T
N/A
Outside scope of 3GPP
[R-6.17.2-002]
Triggering the Driver Safety Device (DSD) the FRMCS User related to the DSD shall be able to establish a non-pre-emptible data communication that matches with QoS category CRICTICAL DATA (see QoS section), to FRMCS Users in the same area i.e. trains, controller and/or a train management system.
A
22.280
22.282
Covered by 22.282-5.2.2-XXX, 5.3.2-XXX, R-5.4.2-XXX, 5.5.2-XXX, 22.280 [R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-003]
The FRMCS System shall be able to forward the Driver Safety Device trigger to the Controller or external systems e.g. train operation management.
A
22.280
[R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-004]
Upon request by an authorised FRMCS user at the ground or the train, the FRMCS System shall be able to establish a non-pre-emptible voice communication.
A
22.280
Covered by [R-5.1.7-002], [R-5.6.2.2.1-006], [R-6.8.1-002], [R-6.8.1-003]
[R-6.17.2-005]
The FRMCS system shall determine the responsible FRMCS Users (e.g. trains, controllers or train management system) based on.
• location information, instantaneous velocity and direction of the concerned train (DSD trigger active)
• functional identity associated with the Driver Safety Device
• responsible controller
A
22.280
[R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-006]
Upon request by the Driver Safety Device (DSD), authorised FRMCS Users or authorised external systems, the FRMCS System shall terminate the data communication related to the DSD.
A
22.282
Covered by [R-6.2.3-001], [R-6.2.3-013]
[R-6.17.2-007]
For On-train safety device to ground communication, the communication shall be recorded by the recording and access to recorded data application.
A
22.280
[R-6.15.4-XXX] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18 Train Integrity monitoring data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.1 Introduction | Train integrity encompasses the continuous verification of the train completeness, i.e. trains integrity status, for the time of mission. The safety system on-board the train and/or at the ground will apply the foreseen safety reaction when the train integrity status becomes undefined or is unknown.
Due to its safety relevance, train integrity information exchange requires a very high reliable communication as well as very low packet data latency. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2 Use case: Data communication for train integrity information exchange | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.1 Description | The FRMCS System will be used to exchange such train integrity information. Every train regardless the type of composition requires this kind of data communication in a fully automated train operation scenario.
The FRMCS Users in this case are the train integrity entities on-board of the train and the ground system. There several options to determine train integrity:
1.) Train integrity information will be only determined by the applicable entities at the train. For this approach train integrity entities are located at the front and the end of the train as well as on demand partially between the front and the end. The front entity supplies the train’s integrity status to the safety entity on-board the train responsible for Control Command Signalling. This scenario requires Off-network communication bearer services for multi-user communication.
2.) Train integrity information will be determined by the applicable entities at the train and the ground. Train integrity entities are distributed equally over the total length of a train. The ground (train) integrity entity will collect the reported train integrity information and compute the train integrity status of a particular train. This scenario requires On-network communication bearer services. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.2 Pre-conditions | The FRMCS Users (train integrity entities) are authorised to initiate a train integrity data communication.
The FRMCS Users (train integrity entities) are authorised to use the train integrity application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.3 Service flows | Off-network communication
On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see chapter 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
The entire train integrity communication will be recorded.
On-network communication
On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train and the ground. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
The entire train integrity communication will be recorded. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.4 Post-conditions | Train integrity information can be exchanged continuously between the involved FRMCS Users
The train approaches its final destination without any delay. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.18.2-001]
The FRMCS System shall allow authorised FRMCS Users to establish/terminate train integrity communication.
A
TS 22.282
Sub-clause 5.5
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-002]
The FRMCS System shall allow authorised FRMCS Users to use train integrity monitoring.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-003]
The FRMCS System shall provide the necessary communication means to support train integrity monitoring.
T
TS 22.282
TS 22.282 sub-clause 5.5 (IP connectivity)
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-004]
The FRMCS System shall support train integrity monitoring in Off-network, On-network and a combination of On-network/Off-network mode.
T
TS 22.282
TS 22.280
TS 22.282: IP connectivity sub-clause 5.5. The whole section 5 is applicable for both on-network and off-network.
TS 22.280:
On network is covered by sub-clause 6.
Off network covered (see all R-6.18.2-XXX requirements).
[R-6.18.2-005]
The FRMCS System shall provide the QoS class as defined for CRITICAL DATA (see 12.10) within the FRMCS System.
A/T
N/A
See section 12.10 below
[R-6.18.2-006]
The FRMCS System shall setup train integrity monitoring within the time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.18.2-007]
The FRMCS System shall allow arbitration for Train Integrity communication.
A
TS 22.280
TS 22.280 sub-clause 5.4.2
The whole section 5 is applicable for both on-network and off-network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19 Use case: Broadcast of public emergency warning information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.1 Introduction | A Puablic Safety Authority is able to broadcast a public emergency warning to a subset of the civil population based on their location. The subset can include FRMCS Users because off the location or functional identity of the FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.2 Description | The Public Safety Authority (PSA) is able to broadcast textual messages, pictures, audio and video content to a subset of FRMCS Users.
6.19.2a Pre-conditions
The FRMCS User is active (logged in) in the FRMCS system.
The FRMCS System provides interworking with a Public Safety Authority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.3 Service flows | The FRMCS System is receiving broadcasting information from the PSA.
The FRMCS System determines the set of FRMCS Users based on:
• The location provided by the PSA broadcast system and/or;
• The functional addressing information of the concerned FRMCS Users provided by PSA and/or;
• The system configuration (e.g. a fixed routing or other conditions).
The FRMCS System establishes a data bearer services for PSA data communication which matches to the application category of CRITICAL DATA (see [QoS]).
The FRMCS System establishes the data bearer service(s) within the timeframe specified as IMMEDIATE (see [QoS]).
The data communication is recorded by the data recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.4 Post-conditions | The concerned FRMCS Users are informed about the public emergency information provided by the PSA.
6.19.5 Potential requirements and gap analysis
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.19.5-001]
The FRMCS System shall provide the interworking to the Public Safety Authority broadcast information system to convey public emergency warning information to authorised FRMCS Users.
A/T
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level.
[R-6.19.5-002]
The FRMCS System shall be able to locate FRMCS User for PSA broadcast information based on the location information provided by the PSA broadcast system and/or the functional identities of the authorised FRMCS Users.
A
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level.
[R-6.19.5-003]
The FRMCS System shall be able to address PSA broadcast information to FRMCS User functional identities by using a “broadcast” functional identity.
A
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20 Safety related critical advisory messaging | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.1 Introduction | Critical advisory information are exchanged among railway users in order to, for example, provide safety related instructions/information from a controller to a driver (e.g. written order, to inform about traffic disturbances, a change in the maximum authorized speed), provide information on how to proceed during an emergency, confirm to the controller the readiness of the train to start, exchange information between control centres on the traffic situation, etc.
Messages can be exchanged on user-to-user or on multi-user level and the exchange is applicable in On-network, Off-network as well as a combination of On-network and Off-network mode. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2 Use case: Initiation/Termination of safety device to ground data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.1 Description | In this chapter the use cases related to Critical advisory messaging services – safety related- communication are described; the following use cases are identified:
• The communication mode e.g. group communication required for Critical advisory messaging services
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.2 Pre-conditions | The FRMCS Users are authorised to initiate and terminate safety related - Critical advisory messaging service communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.3 Service flows | The authorised FRMCS User at the train/ground establishes safety related – Critical advisory messaging session that corresponds to the category CRITICAL DATA (see QoS chapter).
The FRMCS system establishes the bearer service required for the messaging-based communication within a setup time specified as IMMEDIATE (see QoS chapter).
The FRMCS System assigns a certain priority of the safety related – Critical advisory messaging within arbitration management.
The FRMCS Users provide their functional identity associated with the safety related – Critical advisory messaging communication.
The FRMCS Users are reachable by their functional identity associated with the safety related – Critical advisory messaging communication.
The FRMCS System records the communication of the involved FRMCS Users.
An authorised FRMCS User is able to terminate the safety related – Critical advisory messaging communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.4 Post-conditions | Safety related – Critical advisory messages can be exchanged among FRMCS Users.
On demand by an authorised FRMCS User, the safety related – Critical advisory messaging communication is terminated.
The FRMCS System was able to record the communication among the FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.20.2-001]
The FRMCS System shall allow authorised FRMCS Users to establish/terminate Critical advisory messaging.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
[R-6.20.2-002]
The FRMCS System shall allow authorised FRMCS Users to use Critical advisory messaging.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
[R-6.20.2-003]
The FRMCS System shall be able to support Critical advisory messaging in Off-network mode, On-network mode as well as a combination of On-network and Off-network mode.
A
TS 22.280
TS 22.282
.On network covered by TS 22.280 sub-clause 6.
.Partly covered by TS 22.282 sub-clause 5.2 SDS one-to-one and group but no predefined messages (not a 3GPP topic).
.Off-network is FFS.
[R-6.20.2-004]
The FRMCS System shall be able to provide for Critical advisory messaging the QoS class of CRITICAL DATA (see QoS chapter).
A
N/A
See section 12.10 below
[R-6.20.2-005]
The FRMCS System shall be able to manage Critical advisory messaging communication in the arbitration management.
A
TS 22.280
TS 22.280 sub-clause 5.4.2
[R-6.20.2-006]
The FRMCS Users shall be reachable by their functional identity/ies.
A
TS 22.280
[R-5.9a-002] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.1 Description | Service interworking of safety related - Critical advisory messaging service communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.2 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.3 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.5 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21 Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.1 Introduction | In this chapter the use cases related Automatic Train Protection (ATP) data communication are described, the following use cases are identified:
• Initiation of an Automatic Train Protection data communication
• Termination of an Automatic Train Protection data communication
• Service interworking with GSM-R |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.