hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.1 Introduction | FRMCS Users have to indicate events that endanger public safety or emergency that requires the public safety involvement. For this reason, the FRMCS System is able to route the emergency call based on the current position of the initiating FRMCS User. The initiation of an emergency call has no dependency on the registration status of the FRMCS User.
Depending on the national rules, the operator of the FRMCS System may decide if the routing of the public emergency numbers is supported.
Following use cases related to public emergency call handling has been identified.
• Initiation of a public emergency call
• Termination of a public emergency call
• Call back the public emergency call initiator |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2 Use case: Initiation of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.1 Description | If enabled by the FRMCS System, an FRMCS User is able to report an emergency to an officer of the Public Safety Answering Point (PSAP) that will be responsible of bringing assistance or organizing response. The second scenario addresses the call back of a PSAP officer to the originator of the public emergency call which is a FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.2 Pre-conditions | The underlying transport of the FRMCS System supports emergency calls and the FRMCS System allows FRMCS Users to make use of emergency calls. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.3 Service flows | The FRMCS User or a public user initiates the public emergency call voice communication by dialling a public emergency call number.
The voice communication is recorded by the voice recording and access application.
The arbitration is managed by the arbitration application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.4 Post-conditions | The PSAP officer has received the public emergency call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.8.2-001]
The FRMCS System shall be able to allow or inhibit the processing of public emergency numbers.
A
TS 22.280
TS 22.280 sub-clause 6.16 Requirement [R-6.16-001]
[R-6.8.2-002]
In case public emergency call setup is allowed, the 3GPP defined handling of public emergency calls shall be applied.
A
TS 22.280
TS 22.280 sub-clause 6.16 Requirement [R-6.16-001] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3 Use case: Termination of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.1 Description | Both the initiating user, FRMCS User or a public user, and the PSAP officer shall be able to terminate the public emergency call voice communication.
The PSAP officer shall be able to put on hold the public emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.2 Pre-conditions | The public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.3 Service flows | PSAP officer on hold
A PSAP officer shall be able to put the public emergency call on hold.
After the PSAP officer has put the voice communication on hold, the communication remains in the FRMCS System, and the PSAP officer is able to be part of the communication again.
Termination
The FRMCS User or a public user, and/or the PSAP officer shall be able to terminate the public emergency call.
The FRMCS System terminates the voice communication. All involved users are informed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.4 Post-conditions | The public emergency call voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Note: Procedures for normal emergency call behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4 Use case: Call back the public emergency call initiator | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.1 Description | The PSAP officer shall be able to establish the communication towards the FRMCS user or a public user, who previously initiated the public emergency call (e.g. in the case the initial call was dropped). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.2 Pre-conditions | The public emergency call initiator is reachable via FRMCS System or a public network.
The FRMCS System is connected to the Public Safety Answering Point. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.3 Service flows | The PSAP officer initiates the voice communication by using the subscriber identity or the device identity of the previous calling user, FRMCS User or a public user, of a public emergency call. The QoS class of the communication is managed by the QoS class application. The voice communication requests the QoS class which matches the application category of CRITICAL VOICE (see [QoS]) within the FRMCS System.
The FRMCS System establishes the voice communication to the public emergency initiator within a setup time specified as IMMEDIATE (see [QoS]).
The arbitration is managed by the arbitration application.
The voice communication is recorded by the voice recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.4 Post-conditions | The call-back of the public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Normal emergency call service behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9 Data communication for possession management related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.1 Introduction | In this chapter the use cases related to possession management data communication are described, the following use cases are identified:
• Initiation of a possession management data communication
• Termination of a possession management data communication
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2 Use case: Initiation of a possession management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.1 Description | The application supports the processes involved in taking possession of an area of railway infrastructure for engineering purposes (for example for track maintenance). This application is intended to allow track side workers to remotely take control of infrastructure elements to perform safe engineering works on those elements. The application provides the communication bearer in a safe and secure way. The possession management application is able to initiate, release data communication for possession related data of a certain track section. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.2 Pre-conditions | The initiator (Controller(s), trackside maintenance personnel, ground system) is authorised to initiate the possession management data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.3 Service flows | The FRMCS Equipment initiates the possession management data communication towards the track possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.4 Post-conditions | The communication for possession management has been established.
Application messages can be exchanged between the possession management application and the possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.9.2-001]
The FRMCS System shall be able to support the transfer of messages to/from an authorised FRMCS Equipment identity, FRMCS User identity or functional identity with a QoS, priority and setup time as defined in clause 12.10 to/from an external system.
A
22.280
[R-5.9a-020] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority to which a Private Communication (without Floor control) can be made by an MCX User registered to this particular functional alias.
[R-5.9a-021] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority from which Private Communication (without Floor control) is allowed to an MCX User registered to this particular functional alias.
[R-5.9a-022] For private calls to functional aliases the authorizations in clause 5.9a.2 shall replace the authorizations defined in clause 6.7.3.
[R-5.9a-023] The MCX Service system shall be capable of handling private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users by using group call mechanisms and by using first-to-answer private call mechanisms.
[R-5.9a-024] The MCX Service system shall enable an MCX Service Administrator to select the mechanism to be used for handling of private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10 Recording of communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.1 Introduction | In this chapter the use cases related to recording and access are described, the following use cases are identified
• Recording |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2 Use case: Recording | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.1 Description | The FRMCS System is able to provide means to record communication and communication related information for voice, video and data services. The means of recording include FRMCS User identities, functional identities and location information of all involved users.
Which communication is applicable for recording is configurable. Criteria for recording can be based on different attributes or a combination of those e.g. communication application, functional identity, type of communication, location, certain context. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.2 Pre-conditions | A communication is configured to be recorded. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.3 Service flows | Recording of the communication starts when the particular communication becomes initiated.
The recording stops when the communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.4 Post-conditions | The recorded communication is stored and ready for post-analysis |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.10.2-001]
The FRMCS System shall provide the means to record communication and communication related information to an external system. That encompasses voice, video and data services.
A
22.280
On-Network: 6.15.4-001 - 010
Off-Network: covered by [R-7.14-001]: Only metadata are logged, no recording of transmissions of group/private communications as provided in on-network ([R-6.15.4-003]).
[R-6.10.2-002]
The FRMCS System shall be able to select the communication to be provided to the external system based on the following criteria:
• Communication application / use case
• FRMCS User identities
• functional identities
• location information of all involved users
A
22.280
On-Network: 6.15.4-001 - 010
Off-Network: not applicable. No selection mechanism are supported. All communication and non-communication activity metadata from an MCX UE are collected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11 Remote control of engines communication related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.1 Introduction | In this chapter the use cases related to remote control of engines communication are described, the following use cases are identified
• Initiation of a remote control of engines communication
• Termination of a remote control of engines communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2 Use case: Initiation/termination of a remote control of engines communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.1 Description | Remote control requires secure data communication between the FRMCS Equipment as part of on-board control system and the FRMCS User as part of a remote-control device, either via Off-network or On-network communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.2 Pre-conditions | The FRMCS User are authorised to initiate engine remote control communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.3 Service flows | The FRMCS User at the ground initiates the engine remote control communication to the FRMCS Equipment in the locomotive.
The communication requests the QoS which matches to the application category as defined by the operator within the FRMCS System.
The FRMCS User at the ground terminates the engine remote control communication to the FRMCS Equipment in the locomotive. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.