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 Use case: Initiation/termination of a remote control of engines communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.1 Description | Remote control requires secure data communication between the FRMCS Equipment as part of on-board control system and the FRMCS User as part of a remote-control device, either via Off-network or On-network communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.2 Pre-conditions | The FRMCS User are authorised to initiate engine remote control communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.3 Service flows | The FRMCS User at the ground initiates the engine remote control communication to the FRMCS Equipment in the locomotive.
The communication requests the QoS which matches to the application category as defined by the operator within the FRMCS System.
The FRMCS User at the ground terminates the engine remote control comm... |
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... |
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 addi... |
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 interch... |
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 ... |
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 sens... |
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 cri... |
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,
... |
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 ... |
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 co... |
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 applicatio... |
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... |
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 ... |
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 locomo... |
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... |
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... |
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 ... |
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 i... |
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 t... |
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 ar... |
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 ... |
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 n... |
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 est... |
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 r... |
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. Th... |
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) w... |
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]
T... |
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 fi... |
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 Autho... |
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 em... |
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 ... |
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 Cr... |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.