hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 deregistered from the FRMCS System.
A
N/A
Implementation requirement
[R-5.5-003]
After logging off the FRMCS User, the FRMCS Equipment capabilities shall be deactivated and the FRMCS Equipment shall be removed from the FRMCS System.
A
N/A
Implementation requirement |
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 User shall be deregistered from the FRMCS System.
A
N/A
Implementation requirement |
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 for Drivers and Ground FRMCS User(s) communication
• Join a Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
• Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
• Interworking GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) 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 the FRMCS System.
The FRMCS System determines the Driver(s) and the Ground FRMCS User(s) to be included in the communication, based on:
• location information of all users provided by the locations services application, and/or
• functional identity of all users provided by the Role management and presence application.
• System configuration on which Ground FRMCS User is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication 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 Driver(s) and Ground FRMCS User(s). The initiating Driver is indicated to the Ground FRMCS User(s). Also the location of the Driver(s) in the voice communication is presented to the Ground FRMCS User(s) which is retrieved from the location services application.
If the Driver and/or Ground FRMCS User is connected to more than one Drivers and/or Ground FRMCS Users, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Driver and the Ground FRMCS User is managed by the prioritisation application.
The voice communication is recorded by the FRMCS System voice recording and access application. |
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 clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 Req # 2
[R-6.2.2-002]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the application layer priority of the communication shall be managed by the prioritisation application.
A
22.280
6.8.7 Application layer priority, 7.6 MCX Service priority requirements
[R-6.2.2-003]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to determine the FRMCS User(s) to be included in the voice communication, based, amongst others, on the following criteria:
location information, speed and direction of travel provided by the locations services application, and/or functional identity provided by the Role management and presence application.
System configuration on which Ground FRMCS Useris responsible for which part of the track/station/etc.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2-004]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS System shall be able to add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall establish the communication within a setup time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.2.2-006]
The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
Presentation of the id of the speaker is sufficient
See reqs in 6.4.5
[R-6.2.2-006a]
The FRMCS System shall be able to present the location of the Driver(s) to the Ground FRMCS Users involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.2.2-006b]
The FRMCS System shall be able to update the presentation of the location of the Drivers as they move.
A
22.280
5.11 007, 009, 013
6.12 006
[R-6.2.2-007]
A Multi-train voice communication for Drivers and Ground FRMCS User(s) always includes more than two participants.
If only two participants remain, the communication shall be treated as a user-to-user communication.
A
N/A
This is not a service requirement. It is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication.
[R-6.2.2-008]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases").
A
22.179
6.2.3.7
[R-6.2.2-009]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), on the application layer the precedence of the incoming voice communication at the Driver and the Ground FRMCS User shall be managed by the prioritisation application.
A
N/A
See section 9.16 below
[R-6.2.2-010]
The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers and Ground FRMCS User(s) for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented
6.2.2a Use case: Join an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
6.2.2a.1 Description
An authorised FRMCS User is automatically connected to the ongoing Multi-train voice communication when meeting conditions based on location and/or functional identities.
An authorised FRMCS User can request to connect to an ongoing Multi-train voice communication, that has been previously left, when meeting conditions based on location and/or functional identities.
6.2.2a.2 Pre-conditions
The FRMCS User is authorised to connect to a Multi-train voice communication for Drivers and Ground FRMCS User(s) communication. This is managed by the application “authorisation of communication” (see 9.8).
The FRMCS User is authorised to use the Multi-train voice communication for Drivers and Ground FRMCS User(s) application. This is managed by the application “authorisation of application” (see 9.9).
There is an ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s) communication.
6.2.2a.3 Service flows
When a Driver and/or Ground FRMCS User meets the criteria (location and/or functional identity) for being involved in the ongoing Multi-train voice communication for Drivers and Ground FRMCS User(s), the User application automatically sends the request to connect to the ongoing voice communication, or the FRMCS User sends this request by selecting or dialling the corresponding communication.
The FRMCS system connects the Driver and/or Ground FRMCS User to the ongoing call.
The information from the Role management and presence application is used to present the identities for both Driver(s) and Ground FRMCS User(s) to the parties in the call.
If the Driver and/or Ground FRMCS User is connected to more than one Drivers and/or Ground FRMCS Users, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Driver and the Ground FRMCS User is managed by the prioritisation application.
The voice communication is recorded by the FRMCS System Voice recording and access application.
6.2.2a.4 Post-conditions
The Driver and/or the Ground FRMCS User is connected to the on-going Multi-train voice communication for Drivers and Ground FRMCS User(s) communication.
6.2.2a.5 Potential requirements and gap analysis
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.2.2a-001]
The FRMCS System shall be able to notify the user application of an authorised FRMCS User about an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s) when conditions based on location and/or functional identities are met.
A
22.280
22.179
TS 22.179 Floor Control clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 Req # 2, 6.4.9 req #6, 5.17 req # 3, 6.1 req #5
[R-6.2.2a-002]
When the user application of an authorised FRMCS User receives a notification of an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s), it shall be able to request automatically to the FRMCS System a connection to the communication.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R6.6.5.2-00X
6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-003]
When the user application of an authorised FRMCS User receives a notification of an ongoing Multi-train voice-communication for Drivers and Ground FRMCS User(s) that has been previously left, it shall be able to request to the FRMCS System a connection to the communication again
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R6.6.5.2-00X
6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-004]
When a FRMCS User joins a Multi-train voice communication for Drivers and Ground FRMCS User(s), the application layer priority of the communication shall be managed by the prioritisation application.
A
22.280
6.8.7 Application layer priority, 7.6 MCX Service priority requirements
[R-6.2.2a-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to determine the FRMCS User(s) to be joined in the ongoing voice communication, based, amongst others, on the following criteria:
location information, speed and direction of travel provided by the locations services application, and/or functional identity provided by the Role management and presence application.
A
22.280
6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X
6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b
5.9a-006, 5.9a-008a
[R-6.2.2a-006]
When a FRMCS User joins a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to mutually present the identities of all communication partners involved in the communication.
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
Presentation of the id of the speaker is sufficient
See reqs in 6.4.5
[R-6.2.2a-007]
The FRMCS System shall be able to present the location of the newly added Driver(s) to the Ground FRMCS Users involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s).
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.2.2a-008]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), multiuser talker control shall be used for the newly added FRMCS Users (See "9.7 Multiuser talker control related use cases").
A
22.179
6.2.3.7
[R-6.2.2a-009]
When a FRMCS User joins an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s), the precedence of the incoming voice communication at the Driver and the Ground FRMCS User shall be managed by the prioritisation application.
A
N/A
See section 9.16 below
[R-6.2.2a-010]
When a FRMCS User joins an on-going Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System shall be able to make available the speech and communication related data for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented |
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 communication. |
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 can continue the communication.
Driver leaving
The Driver is able to leave the voice communication.. When a Driver has left the other participants in the communication are informed and can continue the communication if there are still Driver(s) involved in the communication.
The Driver automatically leaves the voice communication if the conditions to be included in it are not fulfilled
The FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Ground FRMCS Users are still active in the communication). All involved FRMCS Users are informed.
Driver termination
By configuration, a Driver is able to terminate the voice communication. The FRMCS system terminates the voice communication. All involved users are informed.
Ground FRMCS User on hold
A Ground FRMCS User is able to put the voice communication on hold in the case that more than one Ground FRMCS User is part of the voice communication. The Ground FRMCS User is able to be part of the communication again.
When put on hold the other participants in the communication are informed and can continue the communication.
Ground FRMCS User leaving
A Ground FRMCS User is able to leave the voice communication.
After the Ground FRMCS User has left the voice communication, the remaining users are informed.
Ground FRMCS User termination
Any Ground FRMCS User is able to terminate the voice communication.
The FRMCS System terminates the voice communication. All involved users are informed. |
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 not be affected by a Driver or Ground FRMCS User putting the voice communication on hold.
A
22.280
5.4.1, 5.4.2, 5.1.5
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-002]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Driver shall be able to leave the voice communication at any time. After a Driver has left the communication, the remaining users are informed.
A
22.280
TS 22.280: R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-003]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the Driver is able to terminate the communication based on configuration (authorised FRMCS User).
A
22.179
22.280
TS 22.179: 6.2.3.4, 6.2.3.5, 6.2.4
TS 22.280: R-6.4.4-003, R-6.4.4-004
[R-6.2.3-005]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), the FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Ground FRMCS Users are still active in the communication). All involved users are informed.
A
22.280
22.179
22.179 6.2.4 008
22.280 6.4.9 001
CR 22.280 0048 rev1: R-6.1-006, R-6.4.9-001
[R-6.2.3-006]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), a Ground FRMCS User shall be able to leave the communication. After a Ground FRMCS User has left the communication, the remaining users are informed.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behaviour.
[R-6.2.3-007]
For a Multi-train voice communication for Drivers and Ground FRMCS User(s), any Controller shall be able to terminate the communication. All involved users are informed.
A
N/A
Due to the use of the affiliation mechanism and the burst-oriented nature of the MCPTT communication there is no such thing like a termination of a communication. It is simply not used anymore and the MCX Service deletes the identifiers and reservation for it after some time. |
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 on the migration scenario a Ground FRMCS User or a Driver can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE |
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 Ground FRMCS User(s) communication is linked between GSM-R and FRMCS. It is controlled by the FRMCS system.
Service interworking between the talker control in the GSM-R system and the FRMCS system is not required but is expected to be done independently in the GSM-R and FRMCS systems.
If the Driver or the Ground FRMCS User is located in the FRMCS System, the GSM-R system can only route the call if it can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User.
Driver attached to FRMCS
When the Driver is attached to the FRMCS System and is initiating voice communication to other Drivers and Ground FRMCS User(s), the FRMCS System will route the communication through the GSM-R to the appropriate GSM-R Drivers and Ground GSM-R User(s)..
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
Driver moving from GSM-R to FRMCS
When the GSM-R user equipment of the Driver is detached from the GSM-R system, the FRMCS end user device provides service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
Note: It is assumed the FRMCS Application on the FRMCS Equipment will have some control on the GSM-R part of the UE.
Driver moving from FRMCS to GSM-R
When the FRMCS User equipment of the Driver is detached from the FRMCS System, the FRMCS end user device provides service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
Note: It is assumed the FRMCS Application on the FRMCS Equipment will have some control on the GSM-R part of the UE. |
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
TS 22.179: Covered in 6.18.4.2
TS 22.280: R-6.17.3.1-001 to 005
[R-6.2.4-001a]
The FRMCS System shall provide the necessary means to Driver attached to the GSM-R system to set up a Multi-train voice communication for Drivers and Ground FRMCS User(s) for users attached to the FRMCS system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side
A
22.179
22.280
TS 22.179: Covered in 6.18.4.2
TS 22.280: R-6.17.3.1-001 to 005
[R-6.2.4-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Multi-train voice communication for Drivers and Ground FRMCS User(s) also to users in legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
Covered in 6.18.4.2
[R-6.2.4-003]
For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the GSM-R UE becomes detached from the GSM-R system, e.g. due to coverage problems, the end user device, if capable of making use of the FRMCS System, shall be able to set up the communication on the FRMCS System. An interruption of voice communication is acceptable.
Note 1: This use case only applies to end user devices containing a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
22.280
Covered by 6.6.4.1.2 and 6.6.5.2
[R-6.2.4-004]
For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the FRMCS Equipment becomes detached from the FRMCS System, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R, shall be able to set up the communication on legacy GSM-R. An interruption of voice communication is acceptable.
Note 2: This use case only applies to end user devices containing a FRMCS Equipment and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
N/A
Covered by GSM-R “Late Entry |
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 communication
• Termination of Driver to Controller(s) voice communication
• Interworking GSM-R and FRMCS of Driver to Controller(s) communication |
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 authorisation of application. |
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 application, and/or
• functional identity provided by the Role management and presence application.
• system configuration on which Controller is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication to the Controller(s) 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 Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
If the Driver is connected to more than one Controller, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
The voice communication is recorded by the voice recording and access application.
Driver to another Controller(s)
The Driver initiates the voice communication to the Controller who was or will be responsible for the movement of the train. The addressing is performed by selecting an entry from a list or entered manually. The priority of the communication is managed by the prioritisation application.
The FRMCS System presents the list of Controllers to the Driver, based on:
• location information provided by the locations services application, and/or
• functional identity provided by the Role management and presence application.
• system configuration on which Controller is responsible for which part of the track/station/etc.
The FRMCS System establishes the voice communication to the Controller(s) 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 Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
If the Driver is connected to more than one Controller, the multiuser talker control application is used.
The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
The voice communication is recorded by the Voice recording and access application. |
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 communication shall be managed by the prioritisation application.
A
22.280
22.280 6.8.7.1, 6.8.7.2; 5.1.1 002
22.179 6.2.3.7.3 001
[R-6.3.2-002]
For Driver to Controller voice communication the FRMCS System shall be able to determine the responsible Controller(s), based on e.g.:
location information, speed and direction provided by the locations services application, and/or
functional identity provided by the Role management and presence application.
System configuration on which Controller is responsible for which part of the track/station/etc.
A
22.280
CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-003]
For Driver to Controller voice communication the FRMCS System shall add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area.
A
22.280
CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-004]
For Driver to Controller communication the FRMCS System shall establish the communication to the Controller(s) within a setup time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.3.2-005]
The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Driver to Controller(s) voice communication.
A
22.280
TS 22.280, 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
22.280 6.12-006
The id of the speaker is considered sufficient
See reqs in 6.4.5
[R-6.3.2-006]
The FRMCS System shall be able to present the location of the Driver to the Controller(s) involved in a Driver to Controller(s) voice communication.
A
22.280
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
22.280 R-6.4.4-003, R-6.4.4-004
[R-6.3.2-007]
The FRMCS System shall be able to update the presentation of the location of the Drivers as they move.
22.280
22.280
5.11 007, 009, 013
6.12 006
[R-6.3.2-007 a]
For Driver to Controller communication, if the Driver is connected to just one Controller, the communication shall be considered as a user-to-user communication.
A
22.280
This is not a service requirement it is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication
[R-6.3.2-008]
For Driver to Controller voice communication, if the Driver is connected to more than one Controller, the multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases").
A
22.179
CRs 22.179 adding and CRs subsequently changing Section 5.9a
[R-6.3.2-009]
For Driver to Controller communication on application layer the precedence of the incoming voice communication at the Controller shall be managed by the prioritisation application.
A
22.280
See section 9.16 below
[R-6.3.2-010]
The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers including Ground FRMCS User(s) for recording.
A
22.280
On-Net:6.15.4-001 – 010
Off-Net: Not implemented
[R-6.3.2-011]
For Driver to Controller communication the Driver shall be able to initiate the communication to the Controller who was previously or will be responsible next for the movement of the train. The selection shall be performed by selecting an entry from a list or entered manually. The priority of the communication on application layer shall be managed by the prioritisation application.
A
22.280
CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b
[R-6.3.2-012]
For Driver to Controller communication the FRMCS System shall be able to present the list of Controllers to the Driver in order to select from, based on, amongst others, the following criteria:
location information, speed and direction provided by the locations services application, and/or
functional identity provided by the Role management and presence application.
System configuration on which Controller is responsible for which part of the track/station/etc.
A
22.280
CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
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 Controller voice communication on hold in the case that more than one Controller is part of the voice communication.
After the Controller has put the voice communication on hold, the communication remains in the FRMCS System, and the Controller is able to be part of the communication again.
Controller leaving
A Controller shall be able to leave the Driver to Controller voice communication in the case that more than one Controller is part of the voice communication.
After the Controller has left the voice communication he is not able to return to the communication and the remaining users are informed.
Controller termination
Any Controller shall be able to terminate the Driver to Controller voice communication.
The FRMCS System terminates the voice communication. All involved users are informed. |
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 System shall allow the operator to configure whether a Driver shall be able to leave the voice communication.
A
22.280
CR 22.280: 5.9a-012a, 5.9a-012b
[R-6.3.3-003]
For Driver to Controller communication the FRMCS System shall allow the operator to configure whether a Driver shall be able to put the voice communication on hold.
A
22.280
22.280, 5.4.1, 5.4.2, 5.1.5
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-004]
For Driver to Controller communication a Controller shall be able to put the voice communication on hold in the case that more than one Controller is part of the communication. The voice communication between the remaining users shall not be affected by a Controller putting the voice communication on hold.
A
22.280
22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008
22.280 R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-005]
For Driver to Controller communication a Controller shall be able to leave the Driver to Controller communication in the case that more than one Controller is part of the communication. After a Controller has left the communication, the remaining users shall be informed.
A
22.280
22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008
22.280 R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is considered sufficient to mimic the desired behavior.
[R-6.3.3-006]
For Driver to Controller communication any Controller shall be able to terminate the Driver to Controller communication. All involved users shall be informed.
A
22.280
22.179
22.280 6.4.9 001
22.179 6.2.4 008 |
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 can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems. |
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 Controller if the Controller can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller.
Driver attached to FRMCS
When the Driver is attached to the FRMCS System and is initiating voice communication to Controller(s), the FRMCS System will route the communication to the Controller(s) accordingly. The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller. The Role management in FRMCS shall provide the appropriate address or identity e.g. by provide a mapping of GSM-R identities and FRMCS identities.
Driver moving from GSM-R to FRMCS
When the GSM-R user equipment of the Driver is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
Driver moving from FRMCS to GSM-R
When the FRMCS User equipment of the Driver is detached from the FRMCS System the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE. |
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
Covered in 6.18.4.2
[R-6.3.4-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Driver to Controller voice communication also to users in legacy GSM-R systems. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side.
A
22.179
Covered in 6.18.4.2
[R-6.3.4-003]
For Driver to Controller communication, when the GSM-R UE becomes detached from the GSM-R system, e.g. due to coverage problems, the end user device, if capable of making use of the FRMCS System shall be able set up the communication on the FRMCS System. An interruption of voice communication is acceptable.
Note 1: This use case only applies to end user devices containing a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
N/A
Call has to be re-established by UE. This is UE function outside scope of 3GPP standardization
[R-6.3.4-004]
For Driver to Controller communication, when the FRMCS Equipment, becomes detached from the FRMCS System, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R shall be able to set up the communication on legacy GSM-R. An interruption of voice communication is acceptable.
Note 2: This use case only applies to end user devices containing a FRMCS Equipment and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.
A
N/A
Call has to be re-established by UE. This is UE function outside scope of 3GPP |
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 emergency alert
- Termination of the Railway emergency alert;
- Initiation of railway emergency voice communication
- Termination of railway emergency voice communication
- Initiation of Data communication during Railway emergency Alert
- Service interworking and service continuation with GSM-R
- Interface to train borne recorder |
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, drive on sight, etc.
- Based on operational rules, additional information about the emergency can be exchanged using voice and/or data communication.
While the alert needs to be setup very fast, the information part that may follow is less time critical and not always required. The Railway emergency Communication consists of:
1. A mandatory alert phase indicating the emergency;
2. An optional voice and/or data communication phase depending on operational situation and / or operational rules.
Alert is the general term used that encompasses the different phases initiation, continuation and termination. This receives priority handling which is linked to the application category within the FRMCS System (see 12.10).
When a railway emergency alert is triggered by a FRMCS User, the FRMCS System determines which other FRMCS Users shall receive an alert, depending on following conditions:
- Location, accuracy of the location, track, functional identity, direction of movement, speed of the initiating entity
- Location, accuracy of the location, track, functional identity, direction of movement, speed of the FRMCS Users which are concerned of the emergency
- Any additional information provided by the initiating entity
By applying alert conditions, only FRMCS Users who are concerned by this emergency will receive an alert. Figure 6.4.2-1 outlines this principle.
Figure 6.4.2-1 Illustration of FRMCS Users in an railway emergency alert area
Independently of any ongoing interactions between the FRMCS User and the FRMCS Equipment, the railway emergency alert has to be continuously indicated to the FRMCS User until the railway emergency is over (alert is terminated).
While an alert is active, the FRMCS System shall continuously check:
- If additional FRMCS Users do match to the conditions of the railway emergency alert. FRMCS User entering the emergency area/location/etc. will receive the alert.
- If an FRMCS User does not fulfil the conditions to be alerted anymore, because the FRMCS User has moved away from the emergency area, the alert will be withdrawn from this FRMCS User.
A Controller is able to change the conditions to select the applicable FRMCS Users while an alert is active.
While an alert is active on a FRMCS Equipment, the FRMCS User is still able to establish and / or receive other types of communication. If a railway emergency voice communication is established by the FRMCS User of an ongoing alert, any other ongoing voice communications are terminated. |
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, maintenance staff or a member of a shunting team. |
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 appropriate recipients of the railway emergency alert. The conditions (e.g. train number/area/track section/station) can be pre-configured for comfortable selection by the Controller. The Controller may need to confirm the selection.
The FRMCS System will determine, based on the conditions, which FRMCS Users are to receive the railway emergency alert.
The FRMCS System alerts the FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which is presented to the FRMCS User.
The priority of the railway emergency alert is managed by the arbitration rules. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In case a FRMCS User is already active in another Railway emergency alert, the new alert is sent by the FRMCS system to the FRMCS Equipment. The presentation of the alert(s) to the FRMCS User is managed by the arbitration rules (out of 3GPP scope).
The Controller is informed about the alerted FRMCS Users.
The FRMCS Equipment of a Controller shows multiple alerts when active.
The communication is recorded by the Data recording and access to recorded data application.
External system initiated
FRMCS System receives the conditions from the External System (e.g. a list/train number/area/track section/station) to address/determine the appropriate recipients of the railway emergency alert.
The FRMCS System will determine, based on the conditions, which users will receive the railway emergency alert.
The FRMCS System alerts the FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which are presented to the FRMCS Users.
The priority of the railway emergency alert is managed by the arbitration rules. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In case a mobile FRMCS User is already active in another Railway emergency alert, the new alert is sent by the FRMCS system to the FRMCS Equipment. The presentation of the alert(s) to the FRMCS User is managed by the arbitration application (out of 3GPP scope).
The Controller is informed about the alerted FRMCS Users and the alert initiating External System.
The FRMCS Equipment of a Controller shows multiple alerts when active.
The communication is recorded by the Data recording and access to recorded data application.
Mobile FRMCS User initiated
A FRMCS User, like a Driver, maintenance staff or a member of a shunting team, presses the railway emergency button.
The FRMCS Equipment requests the alert communication to the FRMCS System.
The FRMCS System determines the FRMCS Users to be included in the railway emergency alert. This is based on the location information of the initiator and certain conditions (e.g. functional identity, track area, accuracy of the location, maximum track speed, station, shunting yard, location/speed/direction of users).
The FRMCS System alerts the FRMCS- users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which are forwarded to the concerned FRMCS Users.
The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In case a mobile FRMCS User is already active in another Railway emergency alert, the new alert is sent by the FRMCS system to the FRMCS Equipment. The presentation of the alert(s) to the FRMCS User is managed by the arbitration application (out of 3GPP scope).
The applicable Controller(s) is informed about the alerted FRMCS Users, including which user initiated the alert.
The FRMCS Equipment of a Controller shows multiple alerts when active.
The communication is recorded by the Data recording and access to recorded data application. |
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.2.1.2-002
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-005 &. R-6.15.6.2-002
[R-6.4.3-002]
For requests from Controllers or External Systems, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway emergency alert, based on the conditions supplied with the requests (e.g. a list/train number/area/track section/station).
A
22.280
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-004
[R-6.4.3-003]
For requests from FRMCS- users, based on the location information of the initiator and certain other conditions such as functional identity, track area, accuracy of the location, maximum track speed, station, shunting yard, speed and direction, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway emergency alert.
A
22.280
R-5.6.2.1.2-002
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-004
[R-6.4.3-004]
In case no FRMCS- users can be determined to be alerted the FRMCS System shall apply the behaviour as specified in 6.4.4 "New entry".
A
22.280
R-6.6.4.2-002b
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-004
[R-6.4.3-005]
The FRMCS System shall be able to provide additional information (e.g. text, voice prompts) in the railway emergency alert to be forwarded to the FRMCS Users
A
22.282
Using MCData SDS and File Distribution for that - based on the same group i.e. after the MCX Emergency Alert a SDS is initiated and potentially a File Dist. as described in MCData
22.282 R-5.2.2-XXX & 5.3.2-XXX
[R-6.4.3-006]
The FRMCS System shall be able to send a Railway emergency alert to FRMCS Equipment involved in another Railway emergency alert, to receive an additional railway emergency alert. I.
A
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.3-007]
The FRMCS System shall be able to provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts.
A
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.3-008]
The FRMCS System shall not prevent a FRMCS User to make use of other communication services while involved in a railway emergency alert.
A
22.280
Covered by the affiliation mechanism
[R-6.4.3-009]
The FRMCS System shall be able to deliver the railway emergency alert within a time specified as IMMEDIATE (see 12.10).
A&T
N/A
See section 12.10 below
[R-6.4.3-010]
For railway emergency alert the application layer priority of the communication shall be managed by the arbitration rules.
A
22.280
5.4.2-XXX
5.6.X, 6.8.7.X, etc
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-001
[R-6.4.3-011]
When setting up and during the alert, the FRMCS System shall inform the initiator and the involved Controller(s) which FRMCS Users are alerted and who initiated the railway emergency alert.
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
6.12-006
The id of the speaker is considered sufficient
[R-6.4.3-012]
The FRMCS System shall be able to make available the speech and communication related data of a railway emergency alert for recording.
A
22.280
6.15.4-001 - 010 |
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 IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which is forwarded to the FRMCS Equipment.
The priority of the railway emergency alert is managed by the arbitration rules. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In the case of an ongoing railway emergency voice communication, the additional FRMCS User is added to the ongoing voice communication.
In case a FRMCS User is already active in another Railway emergency alert, the new alert is sent by the FRMCS system to the FRMCS Equipment. The presentation of the alert(s) to the FRMCS User is managed by the arbitration application (out of 3GPP scope).
A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
The Controller, the initiator and relevant participants are informed about the updated list of alerted FRMCS User.
The FRMCS Equipment of a Controller shows multiple alerts when active.
The communication is recorded by the Data recording and access to recorded data application. |
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.15.6.2-004
[R-6.4.4-002]
The FRMCS System shall be able to deliver the railway emergency alert to the new FRMCS User(s) within a setup time specified as IMMEDIATE (see 12.10).
A&T
N/A
See section 12.10 below
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-001
[R-6.4.4-003]
The FRMCS System shall be able to forward additional information (e.g., text, voice prompts) in the railway emergency alert to the new FRMCS Users.
A
22.280
[R-6.15.6.2-003]
[R-6.4.4-004]
When added to a railway emergency alert a FRMCS User shall still be able to use other communications.
A
N/A
No requirements identified that might prevent a MCX User to receive other communication while in MEA
[R-6.4.4-005]
For railway emergency alert the application layer priority of the communication shall be managed by the arbitration rules.
A
22.280
5.4.2-XXX
5.6.X, 6.8.7.X
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-001
[R-6.4.4-006]
The FRMCS System shall be able to send a Railway emergency alert to FRMCS Equipment involved in another Railway emergency alert.
A
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.4-007]
The FRMCS System shall provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts.
A
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.4-008]
The FRMCS System shall inform the initiator, the involved Controller(s) and relevant participants which FRMCS Users are additionally alerted.
A
22.280
5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2
22.280 6.12-006
See reqs in 6.4.5
MCX service Ad hoc Group as an alternative to User regroup:
[R-6.15.6.2-005a]
[R-6.4.4-009]
The FRMCS System shall be able to make available the speech and communication related data of a railway emergency voice communication for recording.
A
22.280
6.15.4-001 - 010 |
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 Driver, maintenance staff, a member of a shunting team or a Controller.
The FRMCS System shall forward the railway emergency alert to all additional FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g., text, voice prompts) which are forwarded to the FRMCS User.
The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In case of an ongoing railway emergency voice or data communication, the relevant FRMCS Users are added or removed.
In case a FRMCS User is already active in another Railway emergency alert, the new alert is sent by the FRMCS system to the FRMCS Equipment. The presentation of the alert(s) to the FRMCS User is managed by the arbitration application (out of 3GPP scope).
The FRMCS System shall update the FRMCS Users for whom the railway emergency alert is no longer applicable and terminates the alert. The termination notification of the alert can include additional information (e.g., text, voice prompts) which are forwarded to the FRMCS User.
The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
In case railway emergency alert conditions does not match any longer to a FRMCS User and if there is an ongoing railway emergency voice communication, the FRMCS User will remain in the ongoing railway emergency voice communication.
FRMCS System informs the Controller, the initiator and relevant participants[R-6.15.6.2-005a] about the FRMCS Users who have left and have joined 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 leave or terminate the Railway emergency alert.
The communication is recorded by the Data recording and access to recorded data application. |
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 service Ad hoc Group Communication as an alternative to User regroup:
R-6.15.6.2-004a
[R-6.4.5-002]
The FRMCS System shall forward the railway emergency alert to new FRMCS Users that match the conditions and inform the initiating Driver and Controller(s) accordingly.
A
22.280
[R-5.2.2-014]
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-005a
[R-6.4.5-002a]
When alert conditions are changed, in case of an ongoing railway emergency voice or data communication, the FRMCS System shall add new FRMCS Users that match the conditions to the ongoing railway emergency voice or data Communication.
A
22.280
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-007
[R-6.4.5-003]
The FRMCS System shall withdraw the alert from those FRMCS Users who do not match the conditions anymore and inform them and the initiating Driver and Controller(s) accordingly.
A
22.280
R-5.3-XXX
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: [R-6.15.6.2-005a]
[R-6.4.5-003a]
When alert conditions are changed, in case of an ongoing railway emergency voice or data communication, the FRMCS System shall remove the FRMCS Users who do not match the conditions anymore.
A
22.280
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-007
[R-6.4.5-004]
The FRMCS System shall be able to forward the railway emergency alert to new FRMCS User(s) within a setup time specified as IMMEDIATE (see 12.10).
A&T
N/A
See section 12.10 below
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-001
[R-6.4.5-005]
Void.
[R-6.4.5-006]
The FRMCS System shall be able to forward additional information (e.g., text, voice prompts) in the railway emergency alert to new FRMCS Users.
A
22.280
[R-5.2.2-014]
[R-6.4.5-007]
For railway emergency alert the application layer priority of the communication shall be managed by the arbitration rules.
A
22.280
5.4.2-XXX
5.6.X, 6.8.7.X
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.6.2-001
[R-6.4.5-008]
The FRMCS System shall be able to send a Railway emergency alert to FRMCS Equipment involved in another Railway emergency alert.
A
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.5-009]
Void.
6.4.5a Use case: Merging of Railway Emergency Alerts
6.4.5a.1 Description
An authorized FRMCS User (i.e., Controller) or an External System (e.g., Traffic Management System or Train Tracking System) is able to merge two or more existing Railway Emergency Alerts. The merging may result in changed alert conditions. The affected FRMCS Users are notified.
6.4.5a.2 Pre-conditions
An FRMCS User (i.e., Controller) is authorized to merge Railway Emergency Alerts. There are two or more ongoing Railway Emergency Alerts. FRMCS Users involved in those alerts have been regrouped into separate temporary groups for use during the alerts.
6.4.5a.3 Service flows
It has been determined that the alert area must be extended to include users involved in the ongoing alerts.
An authorized FRMCS User (i.e., Controller) or an External System is able to provide the FRMCS System with changed alert conditions (e.g., extension of the area or combination of track sections) including selection of the appropriate recipients of the new (i.e., merged) Railway Emergency Alert. The FRMCS Users involved in the new/merged alert are regrouped into a new temporary group.
The alert condition is declared by the Controller, or authorized FRMCS User, on this new temporary group. The FRMCS system sends the new/merged Railway Emergency Alert to all FRMCS Users in the new temporary group within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include all relevant information including details of the merged alerts, if needed, (e.g., text, voice prompts) which is forwarded to and presented on the end user device of the regrouped FRMCS Users.
The FRMCS system continuously check’s if FRMCS Users still meet the alert conditions of the Railway Emergency Alert. The FRMCS User can be, for example, a mobile user, a driver, maintenance staff, a member of a shunting team or a controller.
The priority of the Railway Emergency Alert is managed by the arbitration application. The alert has the priority which matches the application category CRITICAL DATA (see 12.10).
In the case that a mobile FRMCS User is already active in a Railway Emergency Alert, the new Railway Emergency Alert is sent by the FRMCS System to the end user device. The presentation of the alert(s) to the user is managed by the client arbitration application.
In case that a mobile FRMCS User is already active in an ongoing Railway Emergency Voice and/or Data communications of another Railway Emergency Alert (i.e., call in progress), the ongoing Railway Emergency Voice and/or Data communications is terminated either using normal termination condition (e.g., an authorized user terminate the call) or using configuration parameters of the FRMCS System (e.g., timeout when latest transmission ends).
When ongoing Railway Emergency Voice and/or Data communications of another Railway Emergency Alert are terminated, the next request to establish Railway Emergency Voice and/or Data communication is made on the associated merged Railway Emergency Alert (i.e., next call occurs on regroup group).
If a Railway Emergency Voice and/or Data communication is established by the FRMCS User of an ongoing Railway Emergency Alert, any other ongoing non-emergency-voice communications are put in the queue.
A FRMCS User - other than the initiating FRMCS User (i.e., Controller) - is not able to manually leave the temporary group of the new Railway Emergency Alert.
The FRMCS system notifies the FRMCS Users for whom the Railway Emergency Alert is no longer applicable and terminates the alert of these FRMCS Users. The termination notification of the alert can include additional information (e.g., text, voice prompts) which is presented on the end user device of the FRMCS Users. These FRMCS Users are removed from the merged alert temporary group.
In the case an FRMCS User no longer meets the conditions of the Railway Emergency Alert, but there is an ongoing Railway Emergency Voice or Data Communication, the FRMCS User will remain in the ongoing Railway Emergency Voice or Data communication.
The initiating FRMCS User (i.e., Controller) is notified which FRMCS Users are still part of the Railway Emergency Alert. FRMCS Users who have left the Railway Emergency Alert are separately indicated to the initiating FRMCS User (i.e., Controller).
The communication is recorded by the Data recording and access to recorded data application.
6.4.5a.4 Post-conditions
The appropriate FRMCS Users remain in the temporary group of the merged Railway Emergency Alert, while non-appropriate FRMCS Users are returned to their previous condition.
6.4.5a.5 Potential requirements and gap analysis |
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 FRMCS System can include additional information (e.g. text, voice prompts) which are forwarded to the FRMCS User.
A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS-System
In case a FRMCS User does not match to the conditions of the railway emergency alert and the particular FRMCS User is part of an ongoing railway emergency voice communication, the FRMCS User will remain in the ongoing railway emergency voice communication.
The Controller is informed by the FRMCS System about the remaining FRMCS Users of the railway emergency alert. The applicable Controller is updated by the FRMCS System about the particular FRMCS Users which do not match to the conditions of the railway emergency alert.
The communication is recorded by the Data recording and access to recorded data application.
Controller
An entitled Controller is able to leave the railway emergency alerts, unless the leaving Controller is the last Controller in the alert.
The FRMCS Equipment of a Controller shows multiple alerts when active.
The communication is recorded by the Data recording and access to recorded data application. |
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 anymore and inform them and the initiating Driver and Controller(s) accordingly.
A
22.280
R-5.3-XXX
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-014
[R-6.4.6-002]
The FRMCS System shall provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts
A
22.280
5.1.2, 5.1.5, 5.4.2, 6.8.8.4.1-005
[R-6.4.6-003]
The FRMCS System shall be able to ensure that at least one Controller is always involved in the railway emergency alert.
Note: The FRMCS will prevent other FRMCS User, e.g. Drivers, maintenance staff or members of a shunting team, to leave railway emergency alert.
A
22.280
[R-6.6.4.2-002a/b]
6.4.6.1-002/003
R-6.4.4-003, R-6.4.4-004
MCX service Ad hoc Group Communication as an alternative to User regroup: not covered |
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 to all FRMCS Users involved in the railway emergency alert. The alert termination notification can include additional information (e.g. text, voice prompts) which are forwarded by the FRMCS System presented on the FRMCS User.
The priority of the termination of the railway emergency alert is managed by the prioritisation application. The termination of the alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
When the Controller terminated the railway emergency alert, in the case of manual initiation of railway emergency voice communication, the related ongoing railway emergency voice communication remains unaffected. On the FRMCS Equipment this can be a separate action for the Controller or can be triggered as a combined action with the termination of the alert.
When the controller terminates the railway emergency alert, in the case of an automatic initiation of a railway emergency voice communication after a railway emergency alert initiation, the railway emergency voice communication is automatically terminated.
The communication is recorded by the Data recording and access to recorded data application. |
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 FRMCS System shall be able to forward additional information (e.g. text, voice prompts) as part of the alert termination.
A
22.282
R-5.6.2.4.2-003
R-5.2.2-014
[R-6.4.7-003]
When the controller terminates the railway emergency alert, in case of manual initiation of railway emergency voice communication, the related railway emergency voice communication remains unaffected.
A
22.280
<Needs analysis based on ongoing MCX service Ad hoc Group Communication>
[R-6.4.7-004]
When the controller terminates the railway emergency alert, in case of automatic initiation of railway emergency voice communication, the related railway emergency voice communication is automatically terminated.
A
22.280
<Needs analysis based on ongoing MCX service Ad hoc Group Communication> |
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.3 Service flows | Automatic initiation of Emergency Voice Communication
Upon activation of the railway emergency alert, the FRMCS System automatically initiates voice communication.
FRMCS Users that are part of an active railway emergency alert shall be included in the voice communication.
The railway emergency voice communication does not interrupt the railway emergency alert but is able to pre-empt any other ongoing voice communication.
The FRMCS System establishes the railway emergency voice communication within a setup time specified as IMMEDIATE (see 12.10). The information from the Role management and presence application is used to present the identities to the FRMCS Users involved in the communication.
The location of the initiator of the railway emergency voice communication is forwarded and presented to the Controller. The necessary location information is retrieved from the location services application.
Multiuser talker control application is used in railway emergency voice communication.
The precedence handling of the incoming railway emergency voice communication for the FRMCS User is managed by the prioritisation application. The railway emergency voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within the FRMCS System.
The communication is recorded by the FRMCS System voice recording and access to recorded data application.
The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active.
Manual initiation of Emergency Voice Communication
Any FRMCS User having an active railway emergency alert shall be able to initiate voice communication by a simple user action.
All the users receiving the active railway emergency alert shall be included in the voice communication.
The railway emergency voice communication shall not interrupt the railway emergency alert but shall pre-empt any other ongoing voice communication.
The FRMCS System establishes the railway emergency voice communication within a setup time specified as IMMEDIATE (see 12.10). The information from the Role management and presence application is used to forward the identities to the FRMCS Users involved in communication.
The location of the initiator of the railway emergency voice communication is forwarded to the Controller. The location information is retrieved from the location services application.
The multiuser talker control application is used in railway emergency voice communication.
The handling of the incoming railway emergency voice communication for both the Controllers and mobile FRMCS Users is managed by the prioritisation application. The railway emergency voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within the FRMCS System.
The communication is recorded by the FRMCS System voice recording and access to recorded data application.
The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.4 Post-conditions | The railway emergency voice communication is active. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.8-001]
Following a railway emergency alert the FRMCS System shall be able to automatically initiate a railway emergency voice communication.
A
22.280
R-5.6.2.4.1-013
[R-6.4.8-002]
The railway emergency voice communication does not interrupt the railway emergency, but is able to pre-empt any other ongoing voice communication.
A
N/A
Can be achieved by proper priority configuration further alert and (voice) communication do not compete for the same user interface resources
[R-6.4.8-003]
The FRMCS System shall also be able to initiate a railway emergency voice communication on manual request by FRMCS Users e.g. Controllers and External Systems
A
22.280
R-5.6.2.2.1-XXX
[R-6.4.8-004]
To determine which FRMCS Users have to be included in the communication the FRMCS System shall apply the mechanism as defined in [R-6.4.3-003]
N/A
22.280
R-5.6.2.1.2-002
R-5.6.2.4.1-004
R-6.8.8.4.1-006
(Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.1-XXX User regroup
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-001 & R-6.15.5.2-014
[R-6.4.8-005]
The FRMCS System shall be able to establish the railway emergency voice communication within a time specified as IMMEDIATE (see 12.10).
A
N/A
See section 12.10 below
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008
[R-6.4.8-006]
For railway emergency voice communication the application layer priority of the communication shall be managed by the prioritisation application.
A
22.280
5.4.2-XXX
5.6.X, 6.8.7.X
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008
[R-6.4.8-007]
The location of the initiator of the railway emergency voice communication is forwarded and presented to the Controller.
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.4.8-008]
The FRMCS System shall be able to mutually forward and continuously update the location of all FRMCS Users involved in a railway emergency voice communication.
A
22.280
5.11 007, 009, 013
6.12 006
[R-6.4.8-009]
For railway emergency voice communication the FRMCS System shall apply multiuser talker control (See "9.7 Multiuser talker control related use cases").
A
22.179
MCX service Ad hoc Group Communication as an alternative to User regroup: 6.2.3.7.2XXX
[R-6.4.8-010]
The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active.
22.280
5.4.2-XXX
[R-5.4.2-007a]
[R-6.4.8-011]
The FRMCS System shall be able to make available the content and communication related data of the railway emergency voice communication for recording purposes.
A
22.280
6.15.4-001 - 010 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9 Use case: Termination of railway emergency voice communication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.