hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.2 Pre-conditions | The UE is switched off.
Note: In this use case and all the following it is assumed the UE contains a FRMCS Application, thus an UE with FRMCS Application is further referred to as FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.3 Service flows | Successful self-test
The user switches on the UE.
The FRMCS Application performs a self-test. If the test is successful, the user is informed about this.
Unsuccessful self-test
The user switches on the UE.
The FRMCS Application performs a self-test. If the test is not successful, the user is informed about this. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.4 Post-conditions | The UE is switched on and attached to a 3GPP network following normal 3GPP defined network selection procedures but not logged into any FRMCS System. The user is informed about the results of the self-test. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.3-001]
The FRMCS Application shall be capable to perform a self-test and inform the user about the results.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4 Use case: Access to the FRMCS System to activate the FRMCS Equipment | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.1 Description | This use case describes how the FRMCS Equipment registers to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.2 Pre-conditions | The UE is powered on and attached to a 3GPP network but is not registered to the FRMCS System.
The UE has a subscriber identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.3 Service flows | The FRMCS Equipment selects an applicable FRMCS System and logs on to it.
The FRMCS Equipment is initialised by the FRMCS System according to its type. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.4 Post-conditions | The FRMCS Equipment capabilities are activated.
The FRMCS Application(s) are running on the device.
The FRMCS Equipment is logged in to the FRMCS System |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.4-001]
When a FRMCS Equipment registers to the FRMCS System, the FRMCS Equipment capabilities are activated and the FRMCS Equipment shall be reachable by its FRMCS Equipment Identity.
A
N/A
Implementation requirement |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5 Use case: Controlled power down of UE | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.1 Description | The UE is powered down. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.2 Pre-conditions | The UE is switched on and the FRMCS Equipment is registered to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.3 Service flows | The user / FRMCS User initiates power-down of the UE.
If logged in, a FRMCS User is logged-out from the FRMCS System.
The FRMCS Equipment will deregister all identities which are active.
The FRMCS Equipment de-registers from the FRMCS System.
The UE is switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.4 Post-conditions | The UE is de-registered from the FRMCS System and switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.5-001]
When the UE is about to be powered down, a FRMCS User logged into the FRMCS System shall be logged off first.
A
N/A
Implementation requirement
[R-5.5-002]
By logging off the functional Role of a FRMCS User shall be deregist... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6 Use case: Uncontrolled power down UE | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.1 Description | This use case describes the case when the UE is powered down in an uncontrolled way e.g. due to battery failure. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.2 Pre-conditions | The UE is switched on, the FRMCS Equipment is registered to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.3 Service flows | The UE loses power probably without being able to notify the FRMCS System.
The UE is without power.
The FRMCS System will deregister all identities associated with the FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.4 Post-conditions | The UE is de-registered from the FRMCS System and switched off. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 5.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-5.6-001]
When the UE is uncontrolled powered down, a FRMCS User logged into the FRMCS System shall be logged out from the FRMCS System.
A
N/A
Implementation requirement
[R-5.6-002]
By logging out the functional Role of the FRMCS Use... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6 Critical communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.1 Introduction | Critical communications applications are essential for train movements, safety, shunting, presence, trackside maintenance, legal aspects such as emergency communications, etc. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2 Multi-train voice communication for Drivers and Ground FRMCS User(s) | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.1 Introduction | In this chapter the use cases related to the function of Multi-train voice communication from the Drivers and/or a Ground FRMCS User towards the Driver and/or Ground FRMCS Users are defined. Ground FRMCS Users may include Controllers. The following use cases are defined:
• Initiation of Multi-train voice communication ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2 Use case: Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.1 Description | A Driver and/or a Ground FRMCS User is able to initiate a voice communication to other Drivers and/or Ground FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.2 Pre-conditions | The Driver and the Ground FRMCS User are authorised to initiate the communication. This is managed by the authorisation of communication application.
The authorisation application authorises the Driver and the Ground FRMCS User to use the Multi-train voice communication for Drivers and Ground FRMCS User(s) |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.3 Service flows | The Driver and/or Ground FRMCS User initiates the voice communication to the (other) Driver(s) and/or Ground FRMCS Users. The priority of the communication is managed by the prioritisation application. The voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within t... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.4 Post-conditions | The Driver and/or the Ground FRMCS User is connected to requested Driver(s) and/or Ground FRMCS User (s). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.2-001]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS Users shall be able to initiate the voice communication to FRMCS Users in trains or on ground.
A
22.280
22.179
TS 22.179 Floor Control ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3 Use case: Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.1 Description | The Driver is able to either put on hold, leave, or terminate (by configuration) the voice communication.
The Driver is automatically disconnected from the voice communication when the conditions to be included in it are not fulfilled
The Ground FRMCS User(s) is able to either put on hold, leave or terminate the voice ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.2 Pre-conditions | There is an ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s) communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.3 Service flows | Driver on hold
The Driver is able to put the voice communication on hold.
After the Driver has put the voice communication on hold, the communication remains in the FRMCS System, and the Driver is able to return to the communication again. When put on hold the other participants in the communication are informed and ca... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.4 Post-conditions | A Ground FRMCS User or a Driver has put on hold or left the voice communication, or a Driver, Ground FRMCS User or FRMCS system has terminated the communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.3-001]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Driver or a Ground FRMCS User shall be able to put the voice communication on hold. The voice communication between the remaining users shall n... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication needs to be defined.
Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
Depending... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.3 Service flows | Driver attached to GSM-R
When the Driver is attached to the GSM-R system and is initiating voice communication to other Drivers and Ground FRMCS User, the FRMCS system routes the group call to the appropriate Drivers and Ground FRMCS User(s) attached to the FRMCS.
The Multi-train voice communication for Drivers and Gro... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.2.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.4-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
22.280... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3 On-train outgoing voice communication from the Driver towards the Controller(s) of the train | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.1 Introduction | In this chapter the use cases related to the function of On-train outgoing voice communication from the Driver towards the Controller(s) of the train are defined. This use case allows the Driver to only communicate with Controllers. The following use cases are defined:
• Initiation of Driver to Controller(s) voice comm... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2 Use case: Initiation of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.1 Description | The Driver shall be able to initiate a voice communication to the Controller(s) that was, is, or will be responsible for the movement of the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.2 Pre-conditions | The Driver is authorised to initiate the voice communication to the Controller. This is managed by the authorisation of voice communication application.
The Driver is authorised to use the On-train outgoing voice communication from the Driver towards the Controller(s) of the train application by the application authori... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.3 Service flows | Driver to responsible Controller(s)
The Driver initiates the voice communication to the Controller. The priority of the communication is managed by the prioritisation application.
The FRMCS System determines the responsible Controller(s), based on:
• location information of the train provided by the locations services ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.4 Post-conditions | The Driver is connected to the requested Controller. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.3.2-001]
For Driver to Controller voice communication, the Driver shall be able to initiate a voice communication to the Controller who is currently responsible for the train. The application layer priority of the voice communicat... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3 Use case: Termination of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.1 Description | The Driver shall be able to terminate the Driver to Controller voice communication. The Driver is not able to leave the communication or to put on hold.
The Controller(s) shall be able to either put on hold, leave or terminate the Driver to Controller communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.2 Pre-conditions | The Driver to Controller voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.3 Service flows | Driver termination
The Driver shall be able to terminate the voice communication. The FRMCS System terminates the voice communication. All involved Controllers are informed.
Note: The Driver is not able to leave the communication or to put on hold.
Controller on hold
A Controller shall be able to put the Driver to Cont... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.4 Post-conditions | A Controller has left the voice communication or the Driver to Controller voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.3.3-001]
For Driver to Controller communication the Driver shall be able to terminate the communication.
A
22.280
22.179
22.280 6.4.9 001
22.179 6.4.9 002, 6.2.4 008
[R-6.3.3-002]
For Driver to Controller communication the FRMCS S... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS of Driver to Controller(s) voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Driver to Controller(s) voice communication needs to be defined.
Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
Depending on the migration scenario a Controller... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.3 Service flows | Driver attached to GSM-R
When the Driver is attached to the GSM-R system and is initiating voice communication to Controller(s), the GSM-R system will route the voice communication to the Controller(s) accordingly.
If the Controller is located in the FRMCS System, the GSM-R system can only route the call to the Control... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.3.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.3.4-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
Covere... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4 Railway emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.1 Introduction | In this chapter the use cases related to Railway emergency communication are defined. The following use cases are defined:
- Initiation of the Railway emergency alert
- New entry to the Railway emergency alert
- Changing of the Railway emergency alert
- Merging of Railway emergency alerts
- Leaving of the Railway emerg... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.2 General overview | Railway emergency communication serves two main purposes in railway operation
- Alert Drivers or other railway staff about an emergency. Receiving such alert will result in immediate actions to be taken by the recipients. These actions are defined by operational rules, e.g. a Driver will slow down train speed to 40km/h... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3 Use case: Initiation of the railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3.1 Description | An FRMCS- user is able to initiate a railway emergency alert. Based on a set of conditions the FRMCS System will determine which FRMCS Users that shall be informed about the emergency (see 6.4.2 General overview). The targeted FRMCS User can be e.g. a mobile FRMCS User, a Driver, an External System, a Controller, maint... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3.2 Pre-conditions | The initiating FRMCS User is authorised to establish a railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3.3 Service flows | In any service flow, a mobile FRMCS User, e.g. a Driver, a maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
Controller initiated
The Controller provides the conditions (e.g. train number/area/track section/station) to the FRMCS System selecting the appropr... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3.4 Post-conditions | The applicable FRMCS Users are alerted. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.3-001]
The FRMCS System shall be able to deliver railway emergency alerts. Requests to initiate a railway emergency alerts may come from Controllers, External Systems or mobile FRMCS Users
A
22.280
R-5.6.2.4.1-002 ( etc.)
R-5.6.... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4 Use case: New entry to the railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4.1 Description | The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of the railway emergency alert. The FRMCS User can be e.g. a mobile FRMCS User, a Driver, maintenance staff, a member of a shunting team or a Controller. The additional FRMCS Users receive the railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4.2 Pre-conditions | The FRMCS User is authorised (referring to authorisation of application) to receive the railway emergency alert. There is an ongoing railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4.3 Service flows | The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of the railway emergency alert. The FRMCS User can be e.g. a mobile FRMCS User, a Driver, maintenance staff, a member of a shunting team or a Controller.
The FRMCS System alerts the FRMCS- users within a setup time specified as IMME... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4.4 Post-conditions | The additional FRMCS Users are alerted. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.4-001]
The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of a railway emergency alert.
A
22.280
R-6.6.4.2-002b
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.1... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5 Use case: Changing of the railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5.1 Description | An authorised Controller or an External System is able to change the conditions selecting the appropriate recipients of the railway emergency alert. The change may result in an expansion or a reduction of FRMCS Users that shall be informed about the emergency. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5.2 Pre-conditions | The FRMCS User is authorised to change the conditions of the railway emergency alert. This is managed by the application authorisation of application.
There is an ongoing railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5.3 Service flows | The Controller or an External System shall be able to change the conditional criteria selecting the appropriate recipients of the railway emergency alert.
The FRMCS System shall continuously check if FRMCS Users still meet the conditions of the railway emergency alert. The FRMCS User can be e.g., a mobile FRMCS User, a... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5.4 Post-conditions | The appropriate recipients remain as alerted, while non-appropriate recipients are not alerted anymore. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.5-001]
If alert conditions are changed by an authorised Controller or an External System, the FRMCS System shall check if additional FRMCS Users match the conditions of the railway emergency alert.
A
22.280
R-6.6.4.2-002b
MCX se... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6 Use case: Leaving of the railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6.1 Description | The FRMCS System shall continuously check if FRMCS Users do match to the condition of the railway emergency alert. If not, FRMCS System terminates the alert of the concerned FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6.2 Pre-conditions | The FRMCS User is authorised to receive the railway emergency alert. This is managed by the application authorisation of application.
There is an ongoing railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6.3 Service flows | Mobile FRMCS User
The FRMCS System shall continuously check if FRMCS Users do match to the conditions of the railway emergency alert.
The FRMCS System shall update the FRMCS Users for whom the railway emergency alert is no longer valid and terminates the alert of these FRMCS Users. The termination notification of the F... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6.4 Post-conditions | The appropriate recipients are still alerted, while non-appropriate recipients are not alerted anymore. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.6-001]
The FRMCS System shall continuously check if FRMCS Users do not match the conditions of the railway emergency alert anymore.
The FRMCS System shall withdraw the alert from those FRMCS Users who do not match the conditions... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7 Use case: Termination of the railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7.1 Description | The Controller is able to terminate the railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7.2 Pre-conditions | The Controller is authorised to terminate the railway emergency alert.
There is an ongoing railway emergency alert. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7.3 Service flows | The Controller terminates the railway emergency alert. A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to terminate the railway emergency alert via actions on the end user device.
Based on the alert termination request, FRMCS System forwards a termination notification t... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7.4 Post-conditions | The railway emergency alert is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.7.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.7-001]
The FRMCS System shall only allow a Controller to terminate the railway emergency alert.
A
22.280
R-6.8.8.4.2-XXX
[R-6.4.7-002]
The FRMCS System shall notify the FRMCS Users of the terminated railway emergency alert.
The ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8 Use case: Initiation of railway emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.1 Description | Based on operational rules, additional information about the emergency can be exchanged using voice communication. E.g. the initiator of the railway emergency voice communication may inform other involved FRMCS Users about the emergency.
Railway emergency voice communication is based on on-net communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.2 Pre-conditions | The railway emergency alert is active. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.