hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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 | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.1 Description | Based on operational rules, the configuration determines whether a FRMCS user within an ongoing railway emergency alert can put on hold, leave, or join an ongoing railway emergency voice communication.
During a railway emergency alert, only entitled Controllers are able to terminate the railway emergency voice communication.
After the termination of railway emergency alert, the railway emergency voice communication is automatically terminated (case of automatic initiation) or only entitled Controllers are able to terminate it (case of manual initiation).
A railway emergency voice communication is terminated when the last entitled Controller leaves it. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.2 Pre-conditions | The railway emergency voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.3 Service flows | In the case a FRMCS
user no longer meets the conditions of the railway emergency alert and if there is an ongoing railway emergency voice communication, the FRMCS user will remain in the ongoing railway emergency voice communication.
On hold
Based on configuration, a FRMCS user is able to put the railway emergency voice communication on hold.
After the FRMCS user has put the railway emergency voice communication on hold, the communication remains active in the FRMCS System. The FRMCS user is able to revert back to the communication again.
Leaving
Based on configuration, a FRMCS user in an ongoing railway emergency voice communication is able to leave the railway emergency voice communication.
Joining
A FRMCS user in an ongoing railway emergency alert is able to join an ongoing railway emergency voice communication.
Termination
An entitled Controller is able to terminate the railway emergency voice communication although the railway emergency alert is still ongoing.
After the termination of the railway emergency alert, in the case of an automatic initiation of a railway emergency voice communication, the communication is automatically terminated (see 6.4.7.3).
After the termination of the railway emergency alert, in the case of a manual initiation of a railway emergency voice communication, an entitled Controller of the ongoing railway emergency voice communication is able to terminate the communication (see 6.4.7.3).
The railway emergency voice communication is terminated when the last entitled Controller leaves it. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.4 Post-conditions | A FRMCS user has left or joined the railway emergency voice communication, or the railway emergency voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.9-001]
In the case a FRMCS User no longer meets the conditions of railway emergency voice communication, the FRMCS system shall remove the FRMCS user from the ongoing railway emergency voice communication.
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.9-002]
For a railway emergency voice communication, only authorised FRMCS user based on configuration shall be able to put the voice communication on hold. The railway emergency voice communication between the remaining FRMCS users shall not be affected. The authorised FRMCS user is able to take up the communication again. All involved FRMCS users are informed.
A
22.280
5.4.1, 5.4.2, 5.1.5
6.4.4-003, 6.4.4-004
[R-6.4.9-003]
For a railway emergency voice communication, only authorised user based on configuration shall be able to leave the communication. All involved FRMCS users are informed.
A
22.280
6.4.4-002; 6.4.5-001; 5.4.2, 5.1.5 003-008
6.4.4-003, 6.4.4-004
6.4.9-001
[R-6.4.9-004]
For a railway emergency voice communication, only an entitled Controller shall be able to terminate the communication. All involved FRMCS users are informed.
A
22.280
6.4.9-001
R-6.8.8.4.2-XXX
MCX service Ad hoc Group Communication as an alternative:
6.15.5.2-003
[R-6.4.9-005]
The FRMCS system shall terminate a railway emergency voice communication when the last entitled Controller leaves it. All involved FRMCS users are informed.
A
22.280
6.4.9-001
MCX service Ad hoc Group Communication as an alternative:
6.15.5.2-003 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10 Use case: Initiation of Data communication during railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.1 Description | Based on operational rules, additional information about the emergency can be exchanged using data communication. A system or a FRMCS User is able to send the additional information (e.g. text, voice prompts). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.2 Pre-conditions | The railway emergency alert is active. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.3 Service flows | A FRMCS User, Controller or an External System is able to send additional information (e.g. text, voice prompts).
All the FRMCS Users shall receive the additional information.
The existence of data communications and the read/unread status are indicated to all FRMCS users involved in the related Railway emergency alert.
The FRMCS System establishes the data 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 users involved in communication.
The location of the initiator of the data communication is presented to a mobile FRMCS User, Controller or to an External System. The location information is retrieved from the location services application.
The handling of the incoming data communication 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.
It shall be possible to receive data communication during railway emergency voice communication.
In the case of an ongoing Data communication during railway emergency alert, the additional user is added to the ongoing Data communication during railway emergency alert.
The communication is recorded by the FRMCS System Data recording and access to recorded data application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.4 Post-conditions | Data communication is initiated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.5 Potential requirements and gap analysis | Independently on any actions between the user and the end user device, the additional information provided by data communication is presented to the user.
The user shall be able to send additional information by data communication using simple user actions e.g. by selecting predefined messages.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.10-001]
The FRMCS System shall allow a FRMCS User, Controller or an External System to send additional information (e.g. text, voice prompts, video) to FRMCS Users involved in a railway emergency alert or railway emergency voice communication.
A
22.282
R-5.2.2-014
[R-6.4.10-002]
The FRMCS System shall be able to deliver the additional data to a railway emergency alert or railway emergency voice communication within a time specified as IMMEDIATE (see 12.10).
A
N/A
See section 12.10 below
[R-6.4.10-003]
The location of the initiator of the data communication shall be presented to all participants in the railway emergency alert or railway emergency voice communication.
A
22.280
5.11 001, 008, 015
6.12 001,006,007
6.4.5 001, 003, 004
[R-6.4.10-004]
For railway emergency alert /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
[R-6.4.10-005]
The FRMCS System shall be able to make available the content and communication related data of the railway emergency data communication for recording purposes.
A
22.280
6.15.4-001 - 010
[R-6.4.10-006]
The existence of data communications shall be presented to all participants in the railway emergency alert.
A
22.280
5.1.1-003
[R-6.4.10-007]
The read/unread status shall be indicated to all participants in the railway emergency alert
A
N/A
Out of scope of 3GPP FFS |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11 Use case: Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.1 Description | For migration purposes, the service interworking and service continuation between the GSM-R system and FRMCS System for railway emergency alerts and railway emergency voice communication needs to be defined.
Service interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system specifications.
Depending on the migration scenario, a Controller can be attached to the FRMCS System, to the GSM-R system or both. The mobile FRMCS User can be attached either to the GSM-R system or to the FRMCS System.
The service continuation use cases only apply where a FRMCS Equipment and a GSM-R UE are linked together. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.3 Service flows | Mobile FRMCS User attached to GSM-R
When the mobile FRMCS User is attached to the GSM-R system and is initiating a Railway Emergency Call, the GSM-R system, (in parallel to processing the railway emergency call internally according to GSM-R definitions), routes the Railway Emergency Call to the FRMCS System, which requires the FRMCS System to be reachable by identities that are understood by the GSM-R system. The FRMCS System will determine, based on configuration, if a railway emergency alert needs to be established. If a railway emergency alert is established a railway emergency voice communication is initiated automatically.
The Railway Emergency Call in the GSM-R system and the railway emergency voice communication in the FRMCS System are linked together and controlled by the FRMCS System.
Service interworking between the talker control in the GSM-R system and the FRMCS System is required, but without changing the GSM-R system.
When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System is terminated too.
When the railway emergency voice communication in the FRMCS System is terminated and there is a Railway Emergency Call in the GSM-R system linked together, Railway Emergency Call in the GSM-R system and railway emergency alert / the Railway emergency voice communication in the FRMCS System are terminated too.
When the railway emergency alert in the FRMCS System is terminated and there is a railway emergency Call in the GSM-R system connected, both the Railway Emergency Call in the GSM-R system and Railway emergency voice communication in the FRMCS System are not terminated.
The information from the Role management and presence application is used to forward the identities between the systems. The identity of the initiator of the Railway Emergency Call in the GSM-R system is made available to the FRMCS System.
Mobile FRMCS User attached to FRMCS
When the FRMCS User is attached to the FRMCS System and is initiating a railway emergency alert, and the railway emergency alert is also relevant for the GSM-R system based on configuration, the railway emergency voice communication becomes initiated in the FRMCS System and as railway emergency Call in the GSM-R system.
The railway emergency voice communication in the FRMCS System and Railway Emergency Call in the GSM-R system are linked and controlled by the FRMCS System.
Service interworking between the talker control in the FRMCS System and the GSM-R system is required, but without changing the GSM-R system.
When the railway emergency voice communication in the FRMCS System is terminated and there is a railway emergency Call in the GSM-R system linked, railway emergency Call in the GSM-R system and Railway emergency alert / the Railway emergency voice communication in the FRMCS System are also terminated.
When the railway emergency alert in the FRMCS System is terminated and there is a linked Railway Emergency Call in the GSM-R system, both the Railway Emergency Call in the GSM-R system and railway emergency voice communication in the FRMCS System remain active.
When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System is terminated.
The information from the Role management and presence application is used to forward the identities between FRMCS System and GSM-R system. The identity of the initiator of the railway emergency alert in the FRMCS System is made available to the GSM-R system to be used accordingly.
Mobile FRMCS User moving from GSM-R to FRMCS
When the GSM-R system becomes unavailable e.g. lack of coverage, the FRMCS Equipment should provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable. It is up to the end user device implementation how this service continuation is as seamless as possible presented to the user.
Mobile FRMCS User moving from FRMCS to GSM-R
When the FRMCS radio access becomes unavailable, the FRMCS Equipment shall able to provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable. It is up to the end user device implementation how this service continuation is as seamless as possible presented to the user.
Note: Both scenarios described above only apply when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.11-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 should not require any changes on GSM-R network side
A/T
22.179
Covered in 6.18.4.2
[R-6.4.11-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a railway emergency alert and / or railway emergency voice communication also to users in the legacy GSM-R system. Interworking between FRMCS and GSM-R should not require any changes on GSM-R system.
A
22.179
Partially covered in 6.18.4.2. Voice is covered, Alert not, as there is no Emergency alert functionality available in GSM-R.
[R-6.4.11-003]
In case of overlapping GSM-R and FRMCS serving the same geographical area the FRMCS System shall update GSM-R about ongoing Railway Emergency Communication/railway emergency alert in the FRMCS System.
Note: To allow the FRMCS System to be updated of Railway Emergency Communication initiated in the GSM-R needs to be configured accordingly.
A
22.179
Basic functionality covered by 6.18.4.2. However, the areas in FRMCS and GSM-R will not exactly match, due to the fact that the capabilities wrt, to granularity of location in the two systems are different.
[R-6.4.11-004]
The FRMCS System shall provide service interworking between the talker control in the GSM-R system and the FRMCS System without changing the GSM-R system.
A
N/A
Based on latest decisions in ETSI-RT, there will be no interaction of talker control between the systems. As a consequence, only two related requirements on unmute/mute remain on the IWF
[R-6.4.11-005]
When the Railway Emergency Call in the GSM-R system is terminated, the linked railway emergency alert and the railway emergency voice communication in the FRMCS System shall also be terminated.
A
22.179
Covered in 6.18.4.2
[R-6.4.11-006]
When the railway emergency voice communication in the FRMCS System is terminated and there is a linked Railway Emergency Call in the GSM-R system, the Railway Emergency Call in the GSM-R system shall also be terminated.
A
22.179
Covered in 6.18.4.2
[R-6.4.11-007]
When the railway emergency alert in the FRMCS System is terminated and there is a Railway Emergency Call in the GSM-R system linked, the Railway Emergency Call in the GSM-R system shall not be terminated.
A
N/A
No I/W between FRMCS emergency alert and GSM-R voice communication. Therefore, requirement becomes obsolete.
[R-6.4.11-008]
When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System shall be terminated.
A
N/A
Voice communications gets terminated. No I/W between FRMCS emergency alert and GSM-R voice communication. Therefore, that part becomes obsolete
[R-6.4.11-009]
The information from the Role management and presence application of the FRMCS System shall be used to identify and address GSM-R users to be included in the railway emergency alert /railway emergency voice communication.
A
N/A
Approach has changed now, linked calls are used instead.
[R-6.4.11-010]
The identity of the initiator of a Railway Emergency Call in the GSM-R system shall be presented to the FRMCS Users involved in that railway emergency voice communication.
A
TS 22.179
Covered for on-network:
[R-6.18.4.2-003]
[R-6.4.11-011]
For a Railway Emergency Call, when the GSM-R system becomes unavailable, e.g. due to coverage problems, the FRMCS Equipment, if capable of making use of the FRMCS System shall be able to reconnect to the railway emergency alert and, if applicable, the railway emergency voice communication on the FRMCS System. An interruption of voice communication is acceptable.
Note 1: This use case only applies when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE.
A
22.280
Communication aspect covered by 6.6.4.1.2 and 6.6.5.2
[R-6.4.11-012]
For railway emergency alert / railway emergency voice communication, when the FRMCS System becomes unavailable, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R shall be able to reconnect to the railway emergency voice communication via GSM-R. An interruption of voice communication is acceptable.
Note 2: This use case only applies when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE.
A
Covered by GSM-R late entry |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12 Use case: Interface to train borne recorder | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.1 Description | The FRMCS Equipment shall provide information about railway emergency communication to the train borne recorder or other equipment via a dedicated interface. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.2 Pre-conditions | The FRMCS Equipment is switched on. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.3 Service flows | The following events on the FRMCS Equipment related to the railway emergency communication is provided to the train borne recorder:
- Initiation of the railway emergency alert
- Reception of the railway emergency alert
- Leaving of the railway emergency alert
- Termination of the railway emergency alert
- Initiation of railway emergency voice communication
- Termination of railway emergency voice communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.4 Post-conditions | User actions related to the railway emergency communication have been provided to the train borne recorder. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.12-001]
FRMCS Equipment shall provide a dedicated interface for train borne recording purposes
A
N/A
Interface for train borne recorder is outside scope of 3GPP.
[R-6.4.12-002]
FRMCS Equipment shall provide following information to the train borne recorder:
• Initiation of the railway emergency alert
• Reception of the railway emergency alert
• Leaving of the railway emergency alert
• Termination of the railway emergency alert
• Initiation of railway emergency voice communication
• Termination of railway emergency voice communication
A
TS 22.280
Covered for on-network:
[R-6.15.4-004]
[R-6.15.4-007]
[R-6.15.4-008]
Not applicable to off-network (see table C-1). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5 Use case: Automatic Train Protection (ATP) support by the FRMCS System | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.1 Description | For Automatic Train Protection (ATP) the train transmits its information (such as current location, current speed, etc.) to a radio block centre (RBC). As soon as a connection has been established between a train, a radio block centre and a train centre, the train sends its position and speed information periodically. The RBC uses the received information to decide movement authority of the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.2 Pre-conditions | It is assumed the current position of the train and its speed is provided by the Location Service as defined in 9.4.
It is assumed that there is a bearer of suitable QoS established between the train the radio block centre and the train control centre. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.3 Service flows | Via the bearer of suitable QoS the train provides its related information, e.g. train number, location, to the RBC. Via this bearer the train can request movement authority from the RBC and the RBC can grant this to the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.4 Post-conditions | A train Driver controls the speed of the train according to movement authority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.5-001]
The FRMCS System shall be able to provide the necessary QoS for a data bearer to be used for the Automatic Train Protection (ATP) used for e.g. movement authority messages or emergency brake messages.
A/T
TS 22.282
(MCData)
Sub-clause 5.5 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6 Trackside Maintenance Warning System communication related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.1 Introduction | Generally, trackside maintenance occur during daily train operation. For safety reasons trackside maintenance staff need to be informed about approaching trains entering the area of maintenance. Thus, the intention of a trackside warning system is to inform trackside staff about the approaching train.
Trackside warning system consists of several specific sensors and warning entities. The sensors are responsible to detect the approaching train and warning entities indicate trackside workers about the approaching train. A warning entity provides this indication in form of visual signal e.g. flashing light and an audio signal e.g. tone. In addition, the local maintenance staff will receive the train approaching indication on its FRMCS Equipment. When the train has left the track section, the warning system withdraws the indication.
Sensors and warning entities constitute the warning system that requires continuous communication between the sensors and the warning entities. In addition, it encompasses the communication among the warning system and the FRMCS Equipment of the local maintenance staff.
Due to the fact that such a warning system deployment is temporary and not always fixed network communication facilities are available at the track, FRMCS System provides necessary mobile communication services for the trackside warning system.
Hence this chapter describes the use cases related to Trackside Maintenance Warning System communication. The following use cases are identified:
• Initiation of a Trackside Maintenance Warning System communication
• Termination of a Trackside Maintenance Warning System communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2 Use case: Initiation of a trackside maintenance warning system communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.1 Description | The FRMCS User (sensors of the warning system entity) shall be able to initiate data communication to the FRMCS Equipment of trackside maintenance staff and/or trackside warning indication entities (FRMCS User) in the applicable area/track.
When a train approaches that FRMCS User (FRMCS Equipment of the trackside maintenance staff) and/or the warning indication entities of the warning system get notified. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.2 Pre-conditions | The FRMCS Users as part of the warning system and the FRMCS Users as part of the maintenance crew are authorised to initiate the trackside maintenance warning system communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.3 Service flows | The FRMCS Users (trackside maintenance warning system) and FRMCS User (trackside workers in the applicable area) initiate the trackside maintenance warning system communication to the receiving side.
A secure data communication application is used for the trackside maintenance warming system communication. The communication requests the QoS class which matches the application category of CRITICAL DATA (see QoS section 12.10) within the FRMCS System.
The arbitration is managed by the arbitration application.
The communication is recorded by the Data recording application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.4 Post-conditions | The FRMCS Users are part of the (warning system) communication are able to exchange data. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.6.2-001]
The FRMCS System shall be able to initiate data communication for Trackside Maintenance Warning System to FRMCS Users upon a request from a functional identity entitled to raise such communication.
A
22.282
Covered by R-5.2.2-XXX, 5.3.2-XXX, , R-5.4.2-XXX, 5.5.2-XXX
[R-6.6.2-002]
For Trackside Maintenance Warning System the FRMCS System shall provide QoS, priority and communication setup time as defined in [Reference to QoS section 12.10].
A
N/A
See section 12.10 below
[R-6.6.2-003]
The FRMCS System shall be able to select FRMCS users to deliver the Trackside Maintenance Warning to base on their functional identity and their location.
A
22.280
Covered by [R-6.6.4.2-002a], [R-6.6.5.2-007] ] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3 Use case: Termination of a trackside maintenance warning system communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.1 Description | FRMCS Users are able to terminate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.2 Pre-conditions | The data (trackside maintenance warning system) communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.3 Service flows | The FRMCS User terminates the trackside maintenance warning system communication with the receiving trackside worker applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.4 Post-conditions | The data communication has been released disconnected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.6.3-001]
The FRMCS System shall be able to terminate the Trackside Maintenance Warning System data communication upon a request received from the functional identity that initiated the Trackside Maintenance Warning System data communication.
A
22.282
Covered by [R-6.2.3-001], [R-6.2.3-013] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7 Pushed Real Time Video streaming | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.1 Introduction | In this chapter the use cases related to real time video streaming are described, the following use cases are identified
• Initiation of a real time video streaming
• Termination of a real time video streaming |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.2 Description | The video image quality depends on the application needs, e.g. lip reading, pattern detection.
Video based supervision for rail operational purposes requires also the support of Real time video capabilities from the FRMCS System. Multiple recipients are able to use the real time video for different purposes.
The FRMCS Users in this case are applications both onboard of the train and on the ground, for example FRMCS Users in a train control center.
For real time video streaming, both video and audio information are combined. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3 Use case: Initiation of a real time video streaming | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.1 Description | Video is streamed between FRMCS Users or FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.2 Pre-conditions | The streaming FRMCS User or FRMCS Equipment has registered to a functional identity that is authorised to initiate a real time video stream.
Note: Successful registration of a functional identity authorised to stream video implies the FRMCS Equipment is able to support streaming video (e.g. camera available)
The receiving FRMCS User or FRMCS Equipment has registered to a functional identity that is authorised to receive a real time video stream.
Note: Successful registration of a functional identity authorised to receive streaming video implies the FRMCS Equipment is able to support streaming video (e.g. monitor or recording device available) |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.3 Service flows | The initiating FRMCS User requests a real time video streaming to another FRMCS User.
The video streaming requests the QoS class which matches to the application category of VIDEO or CRITICAL VIDEO within the FRMCS System, depending on the application needs.
The video quality requested to the FRMCS System by the FRMCS User is checked by the FRMCS Application.
If the requested quality can be reached, the FRMCS System establishes the real time video data communication with a setup time specified as NORMAL (see 12.12).
If the requested quality cannot be reached, the FRMCS Application or the FRMCS User can decide to stop the request or to continue the setup of video streaming with a lower video quality, depending on the application needs.
During the real time video streaming the FRMCS Application constantly monitors the quality. If the delivered quality of the real time video data communication changes, the FRMCS Application or the FRMCS User is informed about the change. The FRMCS Application or the FRMCS User may decide to change the quality of the real time video streaming, depending on the applications needs.
If authorized, the real time video communication is recorded by the data recording and access to recorded data application.
The arbitration is managed by the arbitration application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.4 Post-conditions | Depending on the QoS offered, the FRMCS Application or a FRMCS User decide if video streaming is set up. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.7.3-001]
Depending on the information associated with the functional identity used by the initiator, the FRMCS System shall setup the real time video streaming to one or more FRMCS User(s) identified by functional identities that are able and authorised to receive streaming video.
A
TS 22.281 (MCVideo)
Functional identities covered under User identities in 4.7
[R-6.7.3-002]
Real time video streaming requests shall be set up by the FRMCS System with a QoS, priority and setup time as defined in [Reference to QoS section 12.10].
A
TS 22.281
(MCVideo)
Priority covered under Imminent Peril and Emergency cases. Corresponds to Critical Video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4 Use case: Termination of a real time video communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.1 Description | The FRMCS User is able to terminate a real time video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.2 Pre-conditions | There is an ongoing real time video data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.3 Service flows | The FRMCS Applications or FRMCS Users involved terminate the real time video data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.4 Post-conditions | The real time video data communication is terminated. The FRMCS Application or the FRMCS User is informed about the termination. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.7.4-001]
Upon request from the streaming or receiving FRMCS User, the FRMCS System shall be able to terminate the real time video streaming.
A
TS 22.281
(MCVideo)
This is covered in requirement R-5.2.8-001 clause 5.2.8. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8 Public emergency call related use cases |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.