hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.2 Pre-conditions | User A, User B, User C and User D are authorized FRMCS Users.
User A is a Driver of train A.
User B is FRMCS Equipment used for detection of the environment (sensor).
User C is a Driver of train B.
Train A is approaching to train B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.3 Service flows | Train driver User A initiates a data communication to the other train driver User C to indicate the approaching event to train B.
The sensor User B initiates a data communication to train driver User A, to report what User B detected if some threshold is reached.
These two communications are transported in safely and timely method |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.4 Post-conditions | Train driver User C receives the approaching event and takes appropriate action.
Train driver User A receives the massage from sensor User B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.4-001
The FRMCS system shall support data communication between FRMCS Users with a QoS, priority and setup time as defined in clause 12.10
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17 On-train safety device to ground communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.1 Introduction | Based on a critical situation in the train (for example, triggered by a Driver Safety Device (DSD) or Dead Man Switch, a voice and/or data communication is automatically set up towards a ground user (controller or ground system).
In this chapter the use cases related to On-train safety device to ground communication are defined. The following use case describes:
• Initiation, termination of the On-train safety device data communication
• Voice communication between driver/train staff and controller/train control system |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2 Use case: Initiation of safety device to ground data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.1 Description | 1.) Based on a train safety issue, the Driver Safety Device will automatically establish a data communication to FRMCS User(s) at the ground (controller or train management system). The functional identity of the DSD and other FRMCS User(s) at the train are indicated to the FRMCS User(s) at the ground.
2.) On demand a voice communication can be established by the train staff (FRMCS User) or the FRMCS User at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.2 Pre-conditions | The FRMCS User at the train is authorised to initiate Driver Safety Device data communication.
The FRMCS User at the ground (controller or train management system) is authorised to receive Driver Safety Device data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.3 Service flows | If the driver is not reacting to the DSD, the Driver Safety Device (FRMCS User) may initiate a data communication to the FRMCS User at the ground to notify the controller or train management system about the safety issue of a running train.
After reception of this train safety issue, other trains in the same area get notified by an emergency alert to lower the instantaneous velocity of the train or stops completely.
The FRMCS User at the ground (controller or train management system) acknowledges the reception of DSD emergency notification. The DSD emergency notification remains active and is continuously transmitted until the train safety has been recovered.
In addition, the entitled train staff or entitled ground staff establishes a voice communication to commence further steps, to recover train safety again. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.4 Post-conditions | The emergency didn’t cause a safety issue at other trains as well as the people in those trains. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.17.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.17.2-001]
The FRMCS Equipment shall be able to integrate the Driver Safety Device (DSD).
A/T
N/A
Outside scope of 3GPP
[R-6.17.2-002]
Triggering the Driver Safety Device (DSD) the FRMCS User related to the DSD shall be able to establish a non-pre-emptible data communication that matches with QoS category CRICTICAL DATA (see QoS section), to FRMCS Users in the same area i.e. trains, controller and/or a train management system.
A
22.280
22.282
Covered by 22.282-5.2.2-XXX, 5.3.2-XXX, R-5.4.2-XXX, 5.5.2-XXX, 22.280 [R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-003]
The FRMCS System shall be able to forward the Driver Safety Device trigger to the Controller or external systems e.g. train operation management.
A
22.280
[R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-004]
Upon request by an authorised FRMCS user at the ground or the train, the FRMCS System shall be able to establish a non-pre-emptible voice communication.
A
22.280
Covered by [R-5.1.7-002], [R-5.6.2.2.1-006], [R-6.8.1-002], [R-6.8.1-003]
[R-6.17.2-005]
The FRMCS system shall determine the responsible FRMCS Users (e.g. trains, controllers or train management system) based on.
• location information, instantaneous velocity and direction of the concerned train (DSD trigger active)
• functional identity associated with the Driver Safety Device
• responsible controller
A
22.280
[R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007]
[R-6.17.2-006]
Upon request by the Driver Safety Device (DSD), authorised FRMCS Users or authorised external systems, the FRMCS System shall terminate the data communication related to the DSD.
A
22.282
Covered by [R-6.2.3-001], [R-6.2.3-013]
[R-6.17.2-007]
For On-train safety device to ground communication, the communication shall be recorded by the recording and access to recorded data application.
A
22.280
[R-6.15.4-XXX] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18 Train Integrity monitoring data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.1 Introduction | Train integrity encompasses the continuous verification of the train completeness, i.e. trains integrity status, for the time of mission. The safety system on-board the train and/or at the ground will apply the foreseen safety reaction when the train integrity status becomes undefined or is unknown.
Due to its safety relevance, train integrity information exchange requires a very high reliable communication as well as very low packet data latency. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2 Use case: Data communication for train integrity information exchange | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.1 Description | The FRMCS System will be used to exchange such train integrity information. Every train regardless the type of composition requires this kind of data communication in a fully automated train operation scenario.
The FRMCS Users in this case are the train integrity entities on-board of the train and the ground system. There several options to determine train integrity:
1.) Train integrity information will be only determined by the applicable entities at the train. For this approach train integrity entities are located at the front and the end of the train as well as on demand partially between the front and the end. The front entity supplies the train’s integrity status to the safety entity on-board the train responsible for Control Command Signalling. This scenario requires Off-network communication bearer services for multi-user communication.
2.) Train integrity information will be determined by the applicable entities at the train and the ground. Train integrity entities are distributed equally over the total length of a train. The ground (train) integrity entity will collect the reported train integrity information and compute the train integrity status of a particular train. This scenario requires On-network communication bearer services. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.2 Pre-conditions | The FRMCS Users (train integrity entities) are authorised to initiate a train integrity data communication.
The FRMCS Users (train integrity entities) are authorised to use the train integrity application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.3 Service flows | Off-network communication
On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see chapter 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
The entire train integrity communication will be recorded.
On-network communication
On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train and the ground. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
The entire train integrity communication will be recorded. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.4 Post-conditions | Train integrity information can be exchanged continuously between the involved FRMCS Users
The train approaches its final destination without any delay. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.18.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.18.2-001]
The FRMCS System shall allow authorised FRMCS Users to establish/terminate train integrity communication.
A
TS 22.282
Sub-clause 5.5
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-002]
The FRMCS System shall allow authorised FRMCS Users to use train integrity monitoring.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-003]
The FRMCS System shall provide the necessary communication means to support train integrity monitoring.
T
TS 22.282
TS 22.282 sub-clause 5.5 (IP connectivity)
The whole section 5 is applicable for both on-network and off-network.
[R-6.18.2-004]
The FRMCS System shall support train integrity monitoring in Off-network, On-network and a combination of On-network/Off-network mode.
T
TS 22.282
TS 22.280
TS 22.282: IP connectivity sub-clause 5.5. The whole section 5 is applicable for both on-network and off-network.
TS 22.280:
On network is covered by sub-clause 6.
Off network covered (see all R-6.18.2-XXX requirements).
[R-6.18.2-005]
The FRMCS System shall provide the QoS class as defined for CRITICAL DATA (see 12.10) within the FRMCS System.
A/T
N/A
See section 12.10 below
[R-6.18.2-006]
The FRMCS System shall setup train integrity monitoring within the time specified as NORMAL (see 12.10).
A/T
N/A
See section 12.10 below
[R-6.18.2-007]
The FRMCS System shall allow arbitration for Train Integrity communication.
A
TS 22.280
TS 22.280 sub-clause 5.4.2
The whole section 5 is applicable for both on-network and off-network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19 Use case: Broadcast of public emergency warning information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.1 Introduction | A Puablic Safety Authority is able to broadcast a public emergency warning to a subset of the civil population based on their location. The subset can include FRMCS Users because off the location or functional identity of the FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.2 Description | The Public Safety Authority (PSA) is able to broadcast textual messages, pictures, audio and video content to a subset of FRMCS Users.
6.19.2a Pre-conditions
The FRMCS User is active (logged in) in the FRMCS system.
The FRMCS System provides interworking with a Public Safety Authority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.3 Service flows | The FRMCS System is receiving broadcasting information from the PSA.
The FRMCS System determines the set of FRMCS Users based on:
• The location provided by the PSA broadcast system and/or;
• The functional addressing information of the concerned FRMCS Users provided by PSA and/or;
• The system configuration (e.g. a fixed routing or other conditions).
The FRMCS System establishes a data bearer services for PSA data communication which matches to the application category of CRITICAL DATA (see [QoS]).
The FRMCS System establishes the data bearer service(s) within the timeframe specified as IMMEDIATE (see [QoS]).
The data communication is recorded by the data recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.19.4 Post-conditions | The concerned FRMCS Users are informed about the public emergency information provided by the PSA.
6.19.5 Potential requirements and gap analysis
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.19.5-001]
The FRMCS System shall provide the interworking to the Public Safety Authority broadcast information system to convey public emergency warning information to authorised FRMCS Users.
A/T
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level.
[R-6.19.5-002]
The FRMCS System shall be able to locate FRMCS User for PSA broadcast information based on the location information provided by the PSA broadcast system and/or the functional identities of the authorised FRMCS Users.
A
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level.
[R-6.19.5-003]
The FRMCS System shall be able to address PSA broadcast information to FRMCS User functional identities by using a “broadcast” functional identity.
A
22.268
This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20 Safety related critical advisory messaging | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.1 Introduction | Critical advisory information are exchanged among railway users in order to, for example, provide safety related instructions/information from a controller to a driver (e.g. written order, to inform about traffic disturbances, a change in the maximum authorized speed), provide information on how to proceed during an emergency, confirm to the controller the readiness of the train to start, exchange information between control centres on the traffic situation, etc.
Messages can be exchanged on user-to-user or on multi-user level and the exchange is applicable in On-network, Off-network as well as a combination of On-network and Off-network mode. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2 Use case: Initiation/Termination of safety device to ground data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.1 Description | In this chapter the use cases related to Critical advisory messaging services – safety related- communication are described; the following use cases are identified:
• The communication mode e.g. group communication required for Critical advisory messaging services
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.2 Pre-conditions | The FRMCS Users are authorised to initiate and terminate safety related - Critical advisory messaging service communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.3 Service flows | The authorised FRMCS User at the train/ground establishes safety related – Critical advisory messaging session that corresponds to the category CRITICAL DATA (see QoS chapter).
The FRMCS system establishes the bearer service required for the messaging-based communication within a setup time specified as IMMEDIATE (see QoS chapter).
The FRMCS System assigns a certain priority of the safety related – Critical advisory messaging within arbitration management.
The FRMCS Users provide their functional identity associated with the safety related – Critical advisory messaging communication.
The FRMCS Users are reachable by their functional identity associated with the safety related – Critical advisory messaging communication.
The FRMCS System records the communication of the involved FRMCS Users.
An authorised FRMCS User is able to terminate the safety related – Critical advisory messaging communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.4 Post-conditions | Safety related – Critical advisory messages can be exchanged among FRMCS Users.
On demand by an authorised FRMCS User, the safety related – Critical advisory messaging communication is terminated.
The FRMCS System was able to record the communication among the FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.20.2-001]
The FRMCS System shall allow authorised FRMCS Users to establish/terminate Critical advisory messaging.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
[R-6.20.2-002]
The FRMCS System shall allow authorised FRMCS Users to use Critical advisory messaging.
A
TS 22.280
TS 22.280 sub-clauses 5.1.x
[R-6.20.2-003]
The FRMCS System shall be able to support Critical advisory messaging in Off-network mode, On-network mode as well as a combination of On-network and Off-network mode.
A
TS 22.280
TS 22.282
.On network covered by TS 22.280 sub-clause 6.
.Partly covered by TS 22.282 sub-clause 5.2 SDS one-to-one and group but no predefined messages (not a 3GPP topic).
.Off-network is FFS.
[R-6.20.2-004]
The FRMCS System shall be able to provide for Critical advisory messaging the QoS class of CRITICAL DATA (see QoS chapter).
A
N/A
See section 12.10 below
[R-6.20.2-005]
The FRMCS System shall be able to manage Critical advisory messaging communication in the arbitration management.
A
TS 22.280
TS 22.280 sub-clause 5.4.2
[R-6.20.2-006]
The FRMCS Users shall be reachable by their functional identity/ies.
A
TS 22.280
[R-5.9a-002] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.1 Description | Service interworking of safety related - Critical advisory messaging service communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.2 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.3 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.20.3.5 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21 Automatic Train Protection data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.21.1 Introduction | In this chapter the use cases related Automatic Train Protection (ATP) data communication are described, the following use cases are identified:
• Initiation of an Automatic Train Protection data communication
• Termination of an Automatic Train Protection data communication
• Service interworking with GSM-R |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.