hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.2 Description | Automatic Train Protection (ATP) is the application which performs some or all the functions that ensures the safe movement of a train. ATP supervises the train ensuring that speed and movement limits are kept and the train proceeds only when it is allowed to do so.
Some ATP systems require radio communication to interchange safety relevant data between a train and the corresponding control center.
The FRMCS Users in this case are the Automatic Train Protection applications both on-board of the train and in the control center at the trackside (ground system).
Depending on the implementations, ATP systems require communication between on-board applications of different trains using On-network communication mode.
ATP is considered to be user-to-user communication. Due to safety relevance of Automatic Train Protection (ATP), data communication requires a non-delay tolerant bearer service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3 Use case: Initiation of an Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.1 Description | The FRMCS Application is able to initiate data communication for communication having continuous characteristics between the on-board applications and ground system and/or the on-board applications of other trains. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.2 Pre-conditions | The FRMCS User at the train and at the FRMCS User at ground are authorised to initiate the Automatic Train Protection data communication.
The receiving application is authorised to use the Automatic Train Protection data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.3 Service flows | The FRMCS User (i.e. on-board of the train or the control center at the track side) initiates the Automatic Train Protection data communication (i.e. control center at the trackside or on-board the train).
For the operation of ATP, a non-delay tolerant bearer service is required that corresponds to application category CRITICAL DATA/VERY CRITICAL DATA according to QoS definition in chapter 12.10.
The FRMCS system takes into account the appropriate access criterion to establish the data bearer service within a setup time specified as IMMEDIATE (see QoS).
The arbitration among ATP and other applications applies. The communication is recorded by the data recording application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.4 Post-conditions | ATP related data can be exchanged between the Automatic Train Protection communication entities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.21.3-001]
Upon request of an authorised FRMCS User, the FRMCS System shall be able to provide a non-delay tolerant data bearer for ATP data communication that matches to the application category of CRITICAL DATA/ VERY CRITICAL DATA (see QoS).
A/T
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 5.5.2
See section 12.10 below
[R-6.21.3-002]
For ATP, the FRMCS System shall take into account the appropriate access criterion to establish the bearer service required for ATP communication within a setup time specified as IMMEDIATE (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.21.3-003]
The FRMCS System shall apply arbitration to ATP data communication.
A
TS 22.280
Arbitration:
[R-5.4.2-004]
[R-5.4.2-004A]
[R-5.4.2-004B]
[R-6.21.3-004]
The ATP data communication shall be recorded.
A
TS 22.280
[R-6.15.4-003] for on-network
Not applicable to off-network (see table C-1). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4 Use case: Termination of an Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.1 Description | The FRMCS User is able to terminate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.2 Pre-conditions | The Automatic Train Protection related data communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.3 Service flows | The FRMCS User (i.e. on-board of the train or the control centre at the track side) terminates the Automatic Train Protection data communication.
The FRMCS System terminates the bearer service required for ATP related data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.4 Post-conditions | The Automatic Train Protection data communication has been released. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.21.4-001]
The FRMCS User shall be able to terminate the Automatic Train Protection data communication. The FRMCS System shall terminate the bearer service.
A
TS 22.280
TS 22.280 Requirements [R-6.4.9-001] on termination conditions.
[R-6.7.6-002]
7.4: specific termination conditions for off-net. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22 Voice communication transfer related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.1 Introduction | In this chapter the use cases related to the transfer of incoming or ongoing voice communication are defined. The following use cases are defined:
- Transfer of an incoming voice communication
- Transfer of an ongoing voice communication
- Service interworking and service continuation with GSM-R
To provide some background, a description of one use case based on operational rules is described: a railway station could temporarily be closed for any operational reasons. In that case, railway staff could not be joined anymore. A mechanism of transferring calls to railway staff located in another railway stations shall be provided.
The use cases are applicable for user-to-user voice communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2 Use case: Transfer of an incoming voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.1 Description | When FRMCS User receives a notification of an incoming voice communication, and the FRMCS Equipment does not automatically accept the communication, the FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.2 Pre-conditions | FRMCS User is registered to a single or multiple FRMCS Equipment.
FRMCS User is or is not part of an ongoing communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.3 Service flows | The FRMCS System provides and activates a mechanism to transfer communications.
FRMCS User is authorised to use the mechanism to transfer communications.
When the notification of an incoming voice communication is received by the FRMCS equipment, a notification is presented to appropriate FRMCS User allowing the transfer of the incoming voice communication to another FRMCS User.
FRMCS User selects the new FRMCS User out of a list (e.g. telephone book) or entered manually based on either FRMCS User Identity, FRMCS Functional Identity or MSISDN.
The arbitration is managed by the arbitration application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.4 Post-conditions | The incoming voice communication is transferred to the new FRMCS User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.2-001]
The FRMCS System shall enable FRMCS User to transfer incoming voice communications based on different criteria
A/T
22.179
Limited to private calls because group communication already provides other meachnisms
[R-5.6.3-015], [R-6.7.4-016]
[R-6.22.2-002]
The FRMCS System shall support the transfer of incoming voice communications based on following criteria:
• Unconditional;
• When not reachable;
• Busy;
• Not answering;
A/T
22.179
22.280
Partly covered (Busy excluded). Limited to private calls because group communication already provides other meachnisms
[R-5.6.3-015], [R-6.7.4-016].
Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14).
[R-6.22.2-003]
The FRMCS System shall be able to support configurable time when the FRMCS User is busy and shall be able to support configurable time when the FRMCS User is not answering
A/T
22.179
22.280
Partly covered (Busy excluded). Limited to private calls because group communication already provides other meachnisms
[R-5.6.3-015], [R-6.7.4-016].
Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14).
[R-6.22.2-004]
The FRMCS System shall support the transfer of incoming voice communications for user-to-user.
A/T
22.179
Indicated by sub-clause
5.6.3 Private Call (with Floor control) commencement requirements
6.7.4 Private Call (without Floor control) commencement requirements
[R-6.22.2-005]
The FRMCS System shall be aware of the busy condition of the targeted FRMCS user to forward the incoming voice communication to another FRMCS User.
A/T
22.179
Partly covered (Busy excluded). Limited to private calls because group communication already provides other meachnisms
[R-5.6.3-015], [R-6.7.4-016].
Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3 Use case: Transfer of an ongoing voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.1 Description | When FRMCS User is part of an ongoing voice communication, FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.2 Pre-conditions | FRMCS User is registered to a single or multiple FRMCS Equipment.
FRMCS User is part of an ongoing voice communication.
The FRMCS System provides and activates a mechanism to transfer communications.
FRMCS User is authorised to use the mechanism to transfer communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.3 Service flows | Whilst in an ongoing voice communication, the FRMCS Equipment provides an option to the FRMCS User allowing the transfer of the current communication to another FRMCS User.
FRMCS User selects the new FRMCS User out of a list (e.g. telephone book) or entered manually based on either FRMCS User Identity, FRMCS Functional Identity or MSISDN. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.4 Post-conditions | The ongoing voice communication is transferred to the new FRMCS User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.3-001]
The FRMCS System shall enable FRMCS User to transfer ongoing voice communications.
A/T
22.179
Limited to private calls because group communication already provides other mechanisms
[R-5.6.3-014], [R-6.7.4-015] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.1 Description | For coexistence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
Transfer of incoming voice communication to a GSM-R User shall be provided by the FRMCS System.
Transfer of ongoing communication to a GSM-R User shall be provided by the FRMCS System.
Service interworking for the automatic transfer function is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.2 Pre-conditions | FRMCS User is attached to the FRMCS System.
GSM-R User is attached to GSM-R System.
The transfer procedure (either transfer of incoming voice communication or transfer of ongoing communication) has been initiated by the FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.3 Service flows | FRMCS User selects the new GSM-R User out of a list (e.g. telephone book) or entered manually based on the functional address of the GSM-R User or E.164 numbering plan. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.4 Post-conditions | The incoming voice communication or the ongoing voice communication is transferred to the new GSM-R User by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.22.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.22.4-001]
The FRMCS System shall allow FRMCS User to forward of incoming voice communications and transfer of ongoing communication to GSM-R User using the applicable the addressing scheme.
A/T
22.280
[R-5.19.2-006] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23 Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.1 Introduction | In this chapter the use cases related to Virtual Coupling data communication are described, the following use cases are identified:
• Initiation of a Virtual Coupling data communication
• Termination of a Virtual Coupling data communication
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.2 Description | In virtual coupling use case, multiple trains can synchronously move together as a platoon, where the distance between each train can be shorter than the absolute braking distance.
Virtual Coupling is the application which performs some or all the functions of, synchronous acceleration and braking, protection of individual train within the platoon.
For trains to move synchronously, Virtual Coupling systems require radio communication to interchange performance and/or safety relevant data among adjacent trains in the same platoon periodically.
Due to its safety relevance, the radio communication requires very high reliability as well as very low latency. In order to achieve high reliability and low latency, Virtual Coupling system may use combined On-and Off-network communication mode depending on the proximity.
The FRMCS users in this case are the Virtual Coupling application on-board of each of two trains that could potentially form a platoon.
NOTE: Multiple user-to-user communication and group communication for Virtual Coupling data communication are FFS |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3 Use case: Initiation of a Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.1 Description | The FRMCS user is able to initiate data communication for virtual coupling. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.2 Pre-conditions | The initiating FRMCS user is authorised to initiate the virtual coupling data communication from the trackside control centre.
The trackside control centre has requested the initiating FRMCS user to initiate the Virtual Coupling data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.3 Service flows | The initiating FRMCS user in a train initiates the Virtual Coupling data communication to the receiving FRMCS user in the other train.
The FRMCS System establishes a data bearer services for Virtual Coupling data communication which matches to the application category of VERY CRITICAL DATA, the latency attributes of ULTRA-LOW and the reliability attributes of ULTRA-HIGH (see 12.10).
The FRMCS System establishes the data bearer service(s) within the timeframe specified as IMMEDIATE (see 12.10).
When Off-network communication becomes available for the receiving side, the initiating FRMCS user initiates the Off-network Virtual Coupling data communication to the receiving side.
NOTE: The requirements for the Off-network Virtual Coupling communication are defined in sub-clause 5.8 of TR 22.990 [14] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.4 Post-conditions | The Virtual Coupling data communication is established.
Data can be exchanged between the FRMCS users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.23.3-001]
The FRMCS System shall support Virtual Coupling data communication in Off-network, On-network and a combination of On-network/Off-network mode.
A
TS 22.282
On-network is covered by TS 22.282 subclause 5.5.
Off-network is FFS.
[R-6.23.3-002]
Upon request received from a functional identity entitled to set up Virtual Coupling data communication, the FRMCS System shall be able to setup a On-and/or Off-network data bearer for Virtual Coupling of a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282
This requirement is covered by TS 22.282 subclause 5.5. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4 Use case: Termination of a Virtual Coupling data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.1 Description | The FRMCS user is able to terminate data communication for virtual coupling. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.2 Pre-conditions | The Virtual Coupling data communication is ongoing.
The trackside control centre has requested the terminating FRMCS user to terminate te the Virtual Coupling data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.3 Service flows | The terminating FRMCS user in a train terminates the Virtual Coupling data communication with the receiving FRMCS user in the other train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.4 Post-conditions | The Virtual Coupling data communication has been released. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.23.4-001]
The FRMCS System shall be able to terminate the Virtual Coupling data communication upon a request received from the functional identity that initiated the Virtual Coupling data communication.
A
TS 22.282
This requirement is covered by TS 22.282 subclause 5.5. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.5 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.23.5.1 Description | Service interworking of Virtual Coupling data communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24 Public train emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.1 Introduction | In this chapter the following use cases related to Public train emergency communication are considered:
- Initiation of the Public train emergency alert
- New entry to the Public train emergency alert
- Changing of the Public train emergency alert
- Merging of Public train emergency alerts
- Leaving of the Public train emergency alert
- Termination of the Public train emergency alert;
- Initiation of Public train emergency voice communication
- Termination of Public train emergency voice communication
- Initiation of Data communication during Public train emergency Alert
- Service interworking and service continuation with GSM-R
- Interface to train borne recorder |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.2 General overview | The Public train emergency communication behaves as a Railway emergency communication, but with a limited/local impact (e.g. a platform of a level crossing). The communication can be initiated by railway staff but also by a member of the public using a dedicated FRMCS Equipment.
The Public train emergency alert serves the purpose of enabling the FRMCS User to warn trains of a potentially hazardous situation. For example, when a person fell from a platform onto the track, or when a car is broken down on a level crossing.
When a Public train emergency alert is triggered by a FRMCS User, the FRMCS System reacts in the same way as it would with a Railway emergency communication only the geographical area in which users receive the alert is generally much smaller (less users involved) than with a Railway emergency communication: usually one or a few tracks (where a train approaches) are involved.
In addition, the priority of the Public train emergency communication is lower than the one of the Railway emergency communication.
The following sections capture only use cases that show deltas compared to Railway emergency communication. For all other use cases (listed in 6.24.1), description, service flow and requirements would be the same as the corresponding Railway emergency communication use cases, except that they are applicable to Public train emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3 Use case on Initiation of the Public train emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.1 Description | A FRMCS User is able to initiate the Public train emergency alert to users that are informed about the emergency situation, e.g. that fulfil the conditions of the emergency situation. The FRMCS User can be e.g. a member of the public, mobile user, a driver, an external system, a controller, maintenance staff or a member of a shunting team. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.2 Service flows | External FRMCS System initiated
This use case is similar to Railway emergency alert, except that this is applicable to Public train emergency alert. Please refer to corresponding Railway emergency alert section in the current document for relevant service flows.
Mobile FRMCS User initiated
This use case is similar to the Railway emergency alert, except that this is applicable to Public train emergency alert and the FRMCS User presses the Public train emergency activation device (not the Railway emergency button).
Please refer to corresponding Railway emergency alert section in the current document for relevant service flows. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.3.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.3-001]
( [R-6.4.3-001] not applicable to Public train emergency)
The FRMCS System shall be able to deliver Public train emergency alerts. Request to initiate a Public train emergency alert may come from a railway staff, an external system, but also from a member of the public using a dedicated FRMCS Equipment (i.e., the member of the public will be identified as a specific FRMCS User by the FRMCS System).
A
22.280
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-001 (the member of the public will be identified as a specific FRMCS User by the FRMCS System).
[R-6.24.3-002]
During the initiation of a Public train emergency alert, the FRMCS System shall react in the same way as it would with a Railway emergency alert, only the geographical area in which FRMCS Users receive the alert would be generally much smaller.
A
22.280
MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-001 & R-6.15.5.2-014 (the MCX Service System shall differentiate Public train emergency and Railway emergency communication to determine relevant participants using pre-defined criteria such as location of initiator or FRMCS Equipment label of initiator).
[R-6.24.3-003]
([R-6.4.3-010] not applicable to Public train emergency)
The Railway emergency alert is able to pre-empt any other ongoing alert including Public train emergency alert
A
22.280
<Needs analysis of R-6.8.8 (Communication types based on priorities)> |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4 Use case on Initiation of Public train emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.1 Description | Based on operational rules, additional information about the Public train emergency situation can be exchanged using voice communication, e.g the initiator of the Public train emergency voice communication may inform other involved FRMCS Users about the emergency situation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.2 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Public train emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Public train emergency voice communication is not able to pre-empt Railway emergency communication.
• the Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Public train emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.4-001]
The Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Public train emergency voice communication
A
[Needs analysis] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.1 Description | The description is similar to the termination of Railway emergency communication, except that this is applicable to Public train emergency communication and no interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required.
Please refer to corresponding Railway emergency communication section in the current document for relevant description. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.2 Service flows | Service flows for interworking - Mobile FRMCS User attached to GSM-R
There is no GSM-R counterpart for the FRMCS Public train emergency communication. No interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required since a GSM-R Railway emergency call already initiates a FRMCS Railway Emergency Communication.
Service flows for interworking - Mobile FRMCS User attached to FRMCS
The Service flows for interworking for a Mobile FRMCS User attached to FRMCS is similar to the Railway emergency communication, except that this is applicable to Public train emergency communication.
Please refer to corresponding Railway emergency communication section in the current document for relevant description.
Service flows for service continuation
The Service flows for service continuation is similar to the Railway emergency communication.
Please refer to corresponding Railway emergency communication section in the current document for relevant description. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.3 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.5-001]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Public train emergency alert and /or Public train 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.24.5-002]
In case of overlapping GSM-R and FRMCS serving the same geographical area, the FRMCS System shall update GSM-R about ongoing Public train Emergency communication / Public train emergency alert occurring in the FRMCS System.
Note: No interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required since a GSM-R REC already initiates a FRMCS Railway Emergency Communication.
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.24.5-003]
When the Railway Emergency Call in the GSM-R system is terminated, the linked Public train emergency alert and Public train emergency voice communication in the FRMCS System shall also be terminated.
A
22.179
Covered in 6.18.4.2
[R-6.24.5-004]
When the Public train 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 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25 Railway staff emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.1 Introduction | In this chapter the use cases related to Railway staff emergency communication are defined. The following use cases are defined:
- Initiation of the Railway staff emergency alert
- New entry to the Railway staff emergency alert
- Changing of the Railway staff emergency alert
- Merging of Railway staff emergency alerts
- Leaving of the Railway staff emergency alert
- Termination of the Railway staff emergency alert;
- Initiation of Railway staff emergency voice communication
- Termination of Railway staff emergency voice communication
- Initiation of Data communication during Railway staff emergency Alert
- Service interworking and service continuation with GSM-R
- Interface to train borne recorder |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.2 General overview | The Railway staff emergency communication is very similar to the Railway emergency communication, but both serve two different purposes.
The Railway emergency communication is meant to address staff of all Railway Undertakings in a given area, whereas the Railway staff emergency communication addresses only the users of a specific Railway Undertaking in a given area.
Subsequently, where the Railway emergency communication has the Infrastructure Manager’s Controller a pivotal person in the call, in the Railway staff emergency communication, this is a Railway Undertaking’s Operator - usually someone that has a pivotal function in railways staff safety and has connections to railway police or other Railway Undertaking staff concerning safety and security.
In addition, the priority of the Railway staff emergency communication is lower than the one of the Railway emergency communication.
Furthermore, since the Railway staff emergency communication does not exist in GSM-R, no service interworking is required.
The following sections capture only use cases that show deltas compared to Railway emergency communication. For all other use cases (listed in 6.25.1), description, service flow and requirements would be the same as the corresponding Railway emergency communication use cases, except that they are applicable to Railway staff emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3 Use case on Initiation of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.1 Description | An FRMCS User is able to initiate the Railway staff 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.25.2 General overview). The targeted FRMCS User can be e.g., railway staff, train staff, a train driver, an external system, a Railway staff emergency operator or maintenance staff. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.2 Service flows | In any service flow, a mobile FRMCS User, e.g., a train driver, railway staff, train staff or maintenance staff of a specific organisation is not able to leave or terminate the railway emergency alert.
Operator initiated
Service flows are similar to Railway emergency communication, except that the operator is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document.
External system initiated
Service flows are similar to Railway emergency communication, except that the external system is not owned and operated by an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document.
Mobile FRMCS User initiated
Service flows are similar to Railway emergency communication, except that the Mobile FRMCS User initiator is from a specific organisation and can only communicate with staff from its own organisation. Criteria to determine the FRMCS Users to be included in the Railway staff emergency alert are similar to Railway emergency communication, limited to staff from initiator’s organisation e.g., location and full or subparts of the FRMCS Functional Identity of the FRMCS Users. An example of a full FRMCS Functional Identity of an FRMCS User is a specific driver on a specific train from a specific organisation. An example of a subpart of an FRMCS Functional Identity of an FRMCS User is all train drivers and train staff from the same organisation.
Please refer to corresponding section in the current document for relevant service flows. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.3-001]
([R-6.4.3-001] not applicable to Railway staff emergency)
Request to initiate a railway staff emergency alert may come from Operators external to FRMCS Operator, External Systems or mobile FRMCS Users.
A
22.280
Operators and mobile FRMCS Users covered by R-6.15.5.2-001.
Not covered for external systems.
[R-6.25.3-002]
([R-6.4.3-002] not applicable to Railway staff emergency)
For requests from Operators, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway staff emergency alert, based on the conditions supplied with the requests (e.g., a list/train number/area/track section/station).
A
22.280
Covered by R-6.15.5.2-014 (if MCX Service Ad Hoc Group mechanism can differentiate between railway staff emergency & railway emergency during initiation).
[R-6.25.3-003]
([R-6.4.3-003] not applicable to Railway staff emergency)
For requests from mobile FRMCS Users, based on the location information of the initiator and certain other conditions such as the FRMCS Functional Identity or subparts of the FRMCS Functional Identity of the FRMCS Users, 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 staff emergency alert.
A
22.280
Covered by R-6.15.5.2-014 (if MCX Service Ad Hoc Group mechanism can differentiate between railway staff emergency & railway emergency during initiation).
[R-6.25.3-004]
([R-6.4.3-007] not applicable to Railway staff emergency)
The FRMCS System shall be able to provide all applicable alerts to an Operator independent of whether involved in another alert or not to allow the Operators to switch between different alerts.
A
22.280
[R-5.4.2-007a]
[R-6.25.3-005]
([R-6.4.3-010] not applicable to Railway staff emergency)
The Railway emergency alert is able to pre-empt any other ongoing alert including Railway staff emergency alert
A
22.280
<Needs analysis of R-6.8.8 (Communication types based on priorities)> |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4 Use case on New entry to the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.1 Description | Description is similar to Railway emergency communication, except that additional FRMCS Users can be e.g., railway staff, train staff, a train driver, a Railway staff emergency operator or maintenance staff. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5 Use case on Changing of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6 Use case on Merging of Railway Staff Emergency Alerts | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7 Use case on Initiation of railway staff emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.1 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Railway staff emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Railway staff emergency voice communication is not able to pre-empt Railway emergency communication.
• the Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Railway staff emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.2 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.7-001]
The Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Railway staff emergency voice communication
A
[Needs analysis] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8.1 Description | Service interworking of Railway staff emergency communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7 Performance communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1 Use cases related to transmission of real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.1 Introduction | In this clause, the use cases related to the function of transmitting video in real time are defined.
- An FRMCS User requesting another FRMCS User to transmit real time video
- An FRMCS User receiving a request to transmit real time video
- An FRMCS User accepting a request to transmit real time video
- An FRMCS User rejecting a request to transmit real time video
- An FRMCS User ignoring a request to transmit real time video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2 Use Case: An FRMCS User requesting another FRMCS User to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.1 Description | An FRMCS User can request another FRMCS User to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.2 Pre-conditions | The FRMCS User has a functional Role entitled to request other FRMCS Users to transmit real time video.
The requested FRMCS User can be addressed by the assigned functional identity(ies), FRMCS User Identity, or FRMCS Equipment Identity.
The FRMCS Equipment of the requested user is capable of providing video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.3 Service flows | Requesting FRMCS User
From a list of FRMCS Users provided by the FRMCS System, or by entering an unlisted identity, the requesting FRMCS User selects another FRMCS User to be invited. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities, or phone numbers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.4 Post-conditions | The FRMCS User has been requested transmission of real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.2-001]
The FRMCS System shall enable an entitled FRMCS User to request another FRMCS User to transmit video in real time.
A
22.281
5.1.2.2.2-xxx
[R-7.1.2-002]
The FRMCS System shall provide a list of identities for the requesting FRMCS User to select from. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities or E.164 numbers.
A
22.281
5.1.3.2.2-xxx
[R-7.1.2-003]
The real time video request shall either be based on the functional identity, FRMCS User Identity, FRMCS Equipment Identity or E.164 number.
A
22.280
This requirement is covered by MCCore for rail esp. 5.9a |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3 Use Case: An FRMCS User receiving a real time video request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.1 Description | An FRMCS User will receive a real time video request originated by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.2 Pre-conditions | The FRMCS User has a functional Role that is entitled to receive real time video request from other FRMCS Users.
The FRMCS User’s equipment has a capability to capture real time video.
NOTE: Examples of Role management, like functional Roles, functional identities, FRMCS Equipment Identities, etc. in the railway environment are covered by Annex A.
The FRMCS User may or may not be transmitting real time video to an FRMCS User different from the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.3 Service flows | Requested FRMCS User
The real time video request is indicated to the FRMCS User by audible and visual notification. If the FRMCS User is not managed by a human, the audible and visual notification is not necessary. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.4 Post-conditions | The FRMCS User has received the real time video request.
Ongoing real time video transmission of the requested FRMCS User continues unaffected. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.