hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.3-001]
The FRMCS System shall be able to deliver requests for real time video to a FRMCS User entitled to provide real time video independent of the FRMCS User being involved in another ongoing real time video transmission without excessively using radio resources.
A
22.281
5.1.3.2.2-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4 Use case: An FRMCS User accepting a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.1 Description | An FRMCS User can accept the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.3 Service flows | Requested FRMCS User
The FRMCS User accepts the request to transmit real time video.
Requesting FRMCS User
The FRMCS User receives a notification that the requested FRMCS User accepted the request. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.4 Post-conditions | The requested FRMCS User captures and transmits video in real time to the requesting FRMCS User.
In case the FRMCS User receives multiple requests to stream the video, the FRMCS System will handle this in a resource efficient way i.e. by streaming the video from the FRMCS User to the FRMCS System via the radio only once and distributing it from there to the different FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.4-001]
The FRMCS User shall be able to accept to accept a real time video transmission request.
A
22.281
5.1.3.2.2-xxx esp. 5.1.3.2.2-003
5.2.6.2.1-xxx
[R-7.1.4-002]
If entitled to, a FRMCS User shall be able to provide real time video captured by itself to the FRMCS User requesting the video.
A
22.281
5.1.3.2.2-xxx esp. 5.1.3.2.2-003
5.2.6.2.1-xxx
[R-7.1.4-003]
In case of multiple requests to stream the same video to several FRMCS Users the FRMCS System shall handle this in a resource efficient manner.
A
22.281
5.2.6.2.4-001 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5 Use case: An FRMCS User rejecting a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.1 Description | An FRMCS User can reject the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.3 Service flows | Requested FRMCS User
The FRMCS User rejects the request to transmit real time video.
Requesting FRMCS User
The FRMCS User receives a notification that the requested FRMCS User rejected the request. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.4 Post-conditions | The requested FRMCS User does not transmit video to the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.5-001]
The FRMCS User shall be able to reject a real time video transmission request.
A
22.281
5.2.6.2.4-xxx
[R-7.1.5-002]
The FRMCS System shall automatically reject requests to FRMCS Users not entitled to provide video or not capable of providing video (e.g. no camera in the FRMCS Equipment).
A
22.281
5.2.6.2.4-001
5.1.3.1.2-001
[R-7.1.5-003]
The requesting FRMCS User shall be notified of the reason for rejection.
A
22.280
This is an implicit functionality of group communication setup
6.2.1-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6 Use case: An FRMCS User ignoring a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.1 Description | An FRMCS User can ignore the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.3 Service flows | The requested FRMCS User does not respond.
The timeout expires.
The requesting FRMCS User receives a notification that the invitation was rejected due to a timeout. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.4 Post-conditions | The requested FRMCS User does not transmit video to the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
FRMCS User
[R-7.1.6-001]
If the receiving FRMCS User has not reacted on the invitation within a certain period of time [t1] the FRMCS System shall notify the inviting FRMCS User accordingly and stop the invitation request.
22.280
This is an implicit functionality of group communication setup
6.2.1-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2 Transfer of CCTV archives related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.1 Introduction | In this chapter, the use cases related to CCTV and the use of FRMCS are defined.
• Transfer of CCTV archives from Train to Ground
• Massive Inter-carriage data transfer |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2 Use Case: Bulk Transfer of CCTV archives from Train to Ground | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.1 Description | This use case describes the bulk transfer of CCTV archives from the on-board system to the ground system. This use case assumes the following:
• The retention time for the recordings in the on-board system is seven days.
• The minimum retention time for the CCTV recordings in the ground system is 31 days.
• Bulk transfer of CCTV archives is performed only when train approaches stations in order to stop and at the depot.
An example calculation of the CCTV storage need during 31 days period is provided in Figure.7.2.2.1-1.
Figure.7.2.2.1-1. Onboard CCTV storage sizes with different offload rates.
Next, an example estimation is provided to illustrate the offload performance with different uplink speeds, when the train is commuting from Helsinki to Kemijärvi. The parameters for the calculation are provided in Table 1, whereas the offload results for uplink speeds of 400 Mbps, 750 Mbps and 1000 Mbps are provided respectively in Figure 7.2.2.1-2, Figure 7.2.2.1-3 and in Figure 7.2.2.1-4.
Station
Arrives
Departs
Stop time
Time between stations
HELSINKI
18:52
PASILA
18:57
19:00
0:03
0:08
TIKKURILA
19:41
19:44
0:03
0:44
RIIHIMÄKI
20:19
20:22
0:03
0:38
HÄMEENLINNA
20:46
20:48
0:02
0:26
TAMPERE
21:38
22:11
0:33
1:23
PARKANO
23:03
23:06
0:03
0:55
SEINÄJOKI
0:08
0:10
0:02
1:04
KOKKOLA
1:37
1:39
0:02
1:29
YLIVIESKA
3:10
3:12
0:02
1:33
OULU
4:42
5:00
0:18
1:48
KEMI
6:08
6:12
0:04
1:12
ROVANIEMI
7:47
7:55
0:08
1:43
MISI
8:31
8:32
0:01
0:37
KEMIJÄRVI
9:00
9:05
0:05
0:33
Table 7.2.2.1-1. The parameters for the offload calculation for the train route between Helsinki and Kemijärvi.
Figure 7.2.2.1-2. The offload results with uplink speed of 450 Mbps.
Figure 7.2.2.1-3. The offload results with uplink speed of 750 Mbps.
Figure 7.2.2.1-4. The offload results with uplink speed of 1000 Mbps. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.2 Pre-conditions | • Bulk transfer of CCTV archives is performed only when the train stops at the stations.
• Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
• The ground system supports sufficient archiving system for the transferred recordings. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.3 Service flows | 1. The train approaches the station.
2. Mobile communication system in train establishes connection dedicated for the transfer of CCTV archives with the ground system at a priority level allowing critical communication to continue in parallel
3. The transfer of CCTV archives is started upon successful connection with the ground system.
4. The transfer of CCTV archives is stopped when the connection is no longer available. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.4 Post-conditions | • The on-board CCTV system may re-write over the seven days and older recordings that have been transferred.
• The on-board mobile communication system remains monitoring the next approach of station. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.2.2-001]
The FRMCS System shall be able to support that CCTV archives can be transferred into the ground system in a time and resource efficient way with a minimum of 1 Gbps in dedicated places such as stations or train depots.
A/T
TS 22.289
See: http://www.3gpp.org/technologies/keywords-acronyms/97-lte-advanced
TS 22.289
[R4.1.2-1]
[R4.1.2-2]
[R4.1.2-3]
[R4.1.2-4]
[R-7.2.2-002]
Transferring CCTV archives shall not affect mission critical communication.
NOTE: Transferring CCTV archives is not considered to be a mission critical service.
A/T
TS 22.289
TS 22.289
[R4.1.2-1]
[R4.1.2-2]
[R4.1.2-3]
[R4.1.2-4] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3 Use Case: Massive Inter-carriage data transfer | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.1 Description | This use case describes the transfer of CCTV archives inside the train from different storages and through Inter-carriage links into the FRMCS node providing the uplink connection with the ground system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.2 Pre-conditions | • Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
• The ground system supports sufficient archiving system for the transferred recordings.
• The Inter-carriage links support the same throughput speed as the FRMCS node providing the uplink. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.3 Service flows | Mobile communication system in train establishes connection between carriages of the train dedicated for the transfer of CCTV archives to a central node in the train form which the uplink to the ground system will take place. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.4 Post-conditions | Recording capacity is freed up in the carriages. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.3-001]
The FRMCS System shall facilitate the onboard CCTV communication between carriages of a train, to collect CCTV content at one place on the train for transfer to the ground system.
A/T
22.289
CR 22.289
R4.3.1-001-003
[R-7.3-002]
The onboard CCTV communication between carriages of a train shall not impact mission critical communication
NOTE: Transferring CCTV archives is not considered to be a mission critical service.
A/T
22.289
CR 22.289
R4.3.1-001-003 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5 On-train outgoing voice communication from train staff towards a ground user related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.1 Introduction | In this chapter the use cases related to on-train outgoing voice communication from train staff towards a ground user e.g. controller are defined. The following use cases are defined:
• Initiation of on-train outgoing voice communication by the train staff
• Termination of on-train outgoing voice communication by the train staff
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2 Use case: Initiation of on-train outgoing voice communication from train staff | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.1 Description | FRMCS User at the train shall be able to initiate a voice communication to any FRMCS User (s) at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.2 Pre-conditions | The FRMCS User, member of the train staff, is authorised to initiate the voice communication.
The FRMCS System is able to retrieve location information of the FRMCS User at the train to address the appropriate FRMCS Users at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.3 Service flows | The FRMCS User at the train (member of the train staff) initiates the voice communication to an FRMCS User at the ground (one or multiple). This kind of voice communication requires the QoS category of NON-CRITICAL VOICE (see [QoS]) within the FRMCS system.
The FRMCS System establishes the voice communication among the FRMCS user(s) within a setup time specified as NORMAL (see [QoS]).
The activated identities to the FRMCS User(s) are presented to all FRMCS Users during the entire voice communication.
This kind of communication can become part of the communication arbitration management.
On demand this voice communication can be recorded for post processing purposes.
If two or more than two FRMCS Users are part of the voice communication, multi talker control applies. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.4 Post-conditions | The FRMCS User at the train is able to communicate to the FRMCS Users at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.2-001]
The FRMCS System shall setup a voice communication between one FRMCS User at the train and one/multiple FRMCS Users on the ground based. The NON-CRITICAL VOICE QoS class shall apply for this kind of communication.
A
22.179
22.280
TS 22.179 Floor Control clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 req # 2
[R-7.5.2-002]
The location information of the FRMCS User at the train shall be used to locate and address the responsible FRMCS Users on the ground.
A
22.280
R-5.6.2.1.2-002
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.2-002b
R-6.6.4.1-XXX User regroup
[R-7.5.2-003]
The FRMCS System shall verify if the FRMCS User at the train as well as the FRMCS Users on the ground are authorised to establish the communication.
A
22.280
5.1.x
[R-7.5.2-004]
The FRMCS System shall establish the voice communication between the FRMCS User at the train and the FRMCS Users on the ground within a setup time specified as NORMAL (see [QoS]).
A
N/A
See section 12.10 below
[R-7.5.2-005]
The FRMCS System shall provide for on-train to one/multiple ground FRMCS User:
• arbitration information to the FRMCS User
• communication recording
• Multi-Talker Control.
A
22.280
Arbitration:
[R-5.4.2-004]
[R-5.4.2-004A]
[R-5.4.2-004B]
Multiuser talker control, recording: See relevant section |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3 Use case: Termination of on-train outgoing voice communication from train staff | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.1 Description | The FRMCS User that is member of train staff shall be able to terminate the voice communication towards the FRMCS Users on the ground.
The FRMCS User on the ground shall be able to put on hold, leave or terminate the on-train voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.2 Pre-conditions | The on-train outgoing voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.3 Service flows | Member of train staff termination
The FRMCS User that is member of the train staff terminates the voice communication.
The FRMCS system releases the voice communication.
Communication on hold
A FRMCS User on the ground put the voice communication on hold.
The communication remains active in the FRMCS system and the FRMCS User on the ground user is able to re-join the communication.
Leaving the communication
The FRMCS User at the ground user is able to leave the voice communication if more than one FRMCS User at the ground is part of the voice communication.
Communication Termination by the ground FRMCS User
Any FRMCS User on the ground is able to terminate the voice communication between train staff and the ground user.
The FRMCS system releases the voice communication. All involved FRMCS Users are informed about. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.4 Post-conditions | The on-train outgoing voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.3-001]
The FRMCS System shall allow an authorised FRMCS User at the train that is part of the On-train outgoing voice communication, to terminate the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-002]
Based on the On-train outgoing voice communication termination request, the FRMCS System shall release the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-003]
If authorised, a FRMCS User on the ground shall be able to put the train staff to ground user voice communication on hold if more than one ground FRMCS Users are part of the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-004]
After the FRMCS User has put the voice communication on hold, the communication shall remain active and the FRMCS User on the ground shall be able to re-join the communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-005]
If more than one FRMCS Users on the ground participate to an On-train outgoing voice communication from train staff towards a ground user, the FRMCS User on the ground user shall be able to withdraw from the communication with ability to re-join. The remaining FRMCS Users shall be informed about the withdrawn FRMCS User.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-006]
If authorised, the FRMCS User at the train or the FRMCS Users on the ground shall be able to terminate the train staff to ground user voice communication. The FRMCS system shall inform the involved FRMCS Users about the release of the communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior" |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.1 Description | For coe5istence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
Depending on the scenario a ground FRMCS User can be attached to the FRMCS system, to the GSM-R system or both. The FRMCS User at the train can be attached either to the GSM-R system or to the FRMCS system.
This use case only applies to an FRMCS Equipment that supports FRMCS System and GSM-R. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.2 Pre-conditions | The FRMCS User is either attached to the FRMCS System or to GSM-R. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.3 Service flows | FRMCS User (Train staff) attached to GSM-R
When the FRMCS User (member of the train staff) is attached to the GSM-R system and is initiating voice communication to FRMCS Users on the ground, the GSM-R system will route the voice communication to the FRMCS User on the ground accordingly.
If the FRMCS User on the ground is registered to the FRMCS System, the GSM-R system establishes the communication considering the appropriate addressing scheme.
FRMCS User (Train staff) attached to FRMCS System
When the FRMCS User (member of train staff) is active in the FRMCS system and is initiating voice communication to FRMCS Users on the ground, the FRMCS system will establish the communication considering the appropriate addressing schemes applicable for FRMCS System as well as to GSM-R accordingly.
FRMCS User (Train staff) relocates between GSM-R and FRMCS System/FRMCS System and GSM-R
When the FRMCS User (train staff) relocates between GSM-R - FRMCS System or vice versa the communication service requires continuation. An interruption of the applicable bearer service is acceptable. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.4 Post-conditions | The communication continues if the FRMCS User at the train relocates between GSM-R and FRMCS System or vice versa. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.4-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from the legacy GSM-R system.
A
22.179
Covered in 6.18.4.2
[R-7.5.4-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up On-train outgoing voice communication including users registered to the GSM-R system.
A
22.179
Covered in 6.18.4.2
[R-7.5.4-003]
When the FRMCS User has to relocate between FRMCS System and GSM-R or vice a versa, the voice communication service shall continue. The interruption of the bearer service associated with the relocating FRMCS User is acceptable.
Note : This requirement applies to FRMCS Equipment that contains FRMCS UE and GSM-R UE capabilities.
A
N/A
Call has to be re-established by UE. This is UE function outside scope of 3GPP |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6 Real-time video communication (video conferencing) related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.1 Introduction | A real-time video communication (video conferencing) can be used to support railway operations, such as maintenance staff when investigating infrastructure or vehicles components where help is needed from other staff or during testing of infrastructure or vehicles.
Real-time video communication (video conferencing) is supported by the FRMCS System. That encompasses user-to-user as well as multiuser video communication, including audio, and is applicable to On-network only.
In this chapter the use cases related to real-time video communication (video conferencing) are described. The following use cases are identified:
- An FRMCS User initiates a video conference
- An FRMCS User leaves and re-joins a video conference
- An FRMCS User terminates a video conference
- An FRMCS User changes from a video conference to a voice-only conference
- An FRMCS User changes from a voice-only conference to a video conference
- An FRMCS User joins an ongoing video conference |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2 Use case: Initiation of video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.1 Description | An FRMCS User is able to set up a video conference to other FRMCS User(s). This encompasses transmission of synchronized video aud audio information under conditions. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.2 Pre-conditions | The initiating FRMCS User is authorised to initiate a video conference.
The receiving FRMCS User(s) is(are) authorised to use video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.3 Service flows | An authorised FRMCS User initiates a video conference that corresponds to the application category VIDEO (see QoS chapter).
The FRMCS System determines the FRMCS User(s) to be included in the communication, based on:
- Selection by the initiating FRMCS User, or
- Location of all FRMCS Users, and/or
- Functional identity of all FRMCS Users, and/or
- System configuration.
The FRMCS system establishes the bearer service(s) required for the video conference within a setup time applicable to application category VIDEO (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
The FRMCS System assigns a certain priority of the video conference.
The receiving FRMCS User(s) is able to accept, reject, or ignore the incoming video conference.
The involved FRMCS Users are able to select which video content is to be presented (at both sender and receiver sides).
The FRMCS System records the communication of the initiating and receiving FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.4 Post-conditions | Real-time video (synchronized video and audio information) can be transmitted and received among authorised FRMCS Users involved in the ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3 Use case: Leave and re-join a video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3.1 Description | An FRMCS User is able to leave and re-join an ongoing video conference under conditions. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3.2 Pre-conditions | The video conference is ongoing.
The FRMCS User is authorised to leave and re-join an ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3.3 Service flows | The authorised FRMCS User is able to leave the video conference while receiving a new incoming communication or initiating another outgoing communication. The other involved FRMCS User(s) are informed and can continue the ongoing video conference if the number of remaining participants is sufficient.
The authorised FRMCS Users is then able to re-join the video conference.
The ongoing video conference is terminated if the number of remaining participants is not sufficient. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3.4 Post-conditions | The authorised FRMCS User has left the ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.3.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5 Use case: Termination of a video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5.1 Description | Any authorised FRMCS User is able to terminate an ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5.2 Pre-conditions | The video conference is ongoing.
The FRMCS User is authorised to terminate an ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5.3 Service flows | The authorised FRMCS User is able to terminate the video conference. The involved FRMCS User(s) are informed and the video conference is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5.4 Post-conditions | The authorised FRMCS User has terminated the ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.5.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6 Use case: Changes from a video conference to a voice-only conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6.1 Description | Any authorised FRMCS User is able to change from a video conference to a voice-only conference only. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6.2 Pre-conditions | There is an ongoing video conference.
The initiating FRMCS User is authorised to change from a video conference to a voice-only conference.
The initiating FRMCS User is authorised to initiate voice-only conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6.3 Service flows | An authorised FRMCS User initiates the change from a video conference to a voice-only conference.
The FRMCS System determines if the change can be proceeded, based on:
- Authorisation from initiating FRMCS User, and/or
- Authorisation from receiving FRMCS User(s), and/or
- System configuration.
The FRMCS system establishes the bearer service required for the voice-only conference within a setup time applicable to application category CRITICAL VOICE or VOICE (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
The FRMCS System assigns a certain priority of the voice-only conference.
The receiving FRMCS User(s) shall be able to accept, reject or ignore the change to a voice-only conference.
The bearer service required for the video conference is maintained under conditions (e.g. timer) to allow FRMCS Users to return to the video conference.
The receiving FRMCS User(s) are notified that a change from video conference to voice-only conference has been initiated by the authorised FRMCS User.
The FRMCS System records the communication of the initiating and receiving FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6.4 Post-conditions | After the change from video conference to voice-only conference, the FRMCS Users are not able to transmit and receive video anymore. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.6.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7 Use case: Change from a voice-only conference to a video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7.1 Description | Any authorised FRMCS User is able to change from a voice-only conference to a video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7.2 Pre-conditions | There is an ongoing voice-only conference.
The initiating FRMCS User is authorised to change from a voice-only conference to a video conference.
The initiating FRMCS User is authorised to initiate a video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7.3 Service flows | An authorised FRMCS User initiates the change from a voice-only conference to a video conference.
The FRMCS System determines if the change can be proceeded, based on:
• Authorisation from initiating FRMCS User, and/or
• Authorisation from receiving FRMCS User(s), and/or
• System configuration.
The FRMCS system establishes the bearer service required for the video conference within a setup time applicable to application category VIDEO (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
The FRMCS System assigns a certain priority of the video conference.
The receiving FRMCS User(s) is able to accept, reject or ignore the change to a video conference.
The bearer service required for the voice-only conference is maintained under conditions (e.g. timer) to allow FRMCS Users to return to the voice-only conference.
The receiving FRMCS User(s) are notified that a change has been initiated by the authorised FRMCS User.
The FRMCS System records the communication of the initiating and receiving FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7.4 Post-conditions | After the change from voice-only conference to video conference, the FRMCS Users are able to transmit and receive video and audio. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.7.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8 Use case: Join an ongoing video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8.1 Description | Any authorised FRMCS User is able to join an ongoing video conference under conditions. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8.2 Pre-conditions | There is an ongoing video conference.
An FRMCS User is authorised to join an ongoing video conference. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8.3 Service flows | The FRMCS System determines if the authorised FRMCS User can join an ongoing video conference, based on:
• Selection/Invitation by the initiating FRMCS User of the ongoing video conference, or
• Location of all FRMCS Users, and/or
• Functional identity of all FRMCS Users, and/or
• System configuration.
The authorised FRMCS User joins an ongoing video conference.
The involved FRMCS User(s) are notified that an FRMCS User has joined the ongoing video conference. FRMCS User(s) are using their registered functional identities and provide furthermore their location. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8.4 Post-conditions | The authorised FRMCS Users has joined the ongoing video conference. All involved FRMCS Users of the ongoing video conference are able to transmit and receive video and audio. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.8.5 Potential requirements and gap analysis | This use case is not in the scope of current normative work.
A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7 Real-time automatic translation of languages related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.1 Introduction | The language barrier is a significant obstacle to rail interoperability. All train drivers involved in cross-border rail traffic must have sufficient foreign language skills to cover normal operations, but also degraded and emergency situations e.g., traction problems of a train, damaged switch, train driver reporting persons near to track, etc.
Real-time automatic translation of languages enables train drivers and traffic controllers to communicate with one another, irrespective of their native tongue.
Figure XXX illustrates an example of French German translation between a French train driver and a German traffic controller when the French train driver is moving to Germany Railways.
Figure 7.7.1-1. Example of French German translation between a train driver and a traffic controller
Real-time automatic translation of languages could be considered as a serious game changer for rail interoperability by reducing the cost of language training, by reducing the demands on operating personnel and enables their more flexible assignment, by reducing stress for train drivers when incidents, by enabling the recruitment of staff with minor language skills, by enabling the rail traffic from being rerouted through neighbouring countries.
NOTE: Real-time automatic translation of languages related use cases are limited to point-to-point communications between a train driver and a traffic controller. It may be further extended in the future to other types of communications (e.g., group communications). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.2 General overview | Multiple end-to-end approaches for Real-time automatic translation of languages can be operated depending on Railway needs (Railway Operator’s choice):
• Approach #1: Speech to Speech (S2S) transforming the speech of FRMCS User A to anonymous speech for FRMCS User B.
• Approach #2: Speech to Text (S2T) transforming the speech of FRMCS User A to text for FRMCS User B.
• Approach #3: Text to Speech (T2S) transforming the text of FRMCS User A to anonymous speech for FRMCS User B.
• Approach #4: Text to Text (T2T) transforming the text of FRMCS User A to text for FRMCS User B.
Those various approaches rely on usage of 3 modular modules as part of the language translation tool as depicted in Figure XXX:
• Module #1: Speech to Text (S2T) module transforming the user speech to text format for further process of translation. This module uses Artificial Intelligence for automatic speech recognition.
• Module #2: Translation module ensuring the text translation.
• Module #3: Text to Speech (T2S) module transforming the translated text into speech.
Figure 7.7.2-1. Modular architecture of the language translation tool
Those modules which need extra computing and storage capacities can be located closed to the FRMCS Users (e.g., edge computing, on-board the train, dispatching system) or centrally (e.g., cloud-based) based on implementation options. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3 Real-time Speech to Speech (S2S) translation | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3.1 Description | When entering a visited Railway Operator in Country B, an FRMCS User A (e.g., a train driver) from Country A may be able to communicate with an FRMCS User B (e.g., traffic controller) from Country B in their respective native tongues.
FRMCS User A is talking and listening in his own native language or dialect used in Country A.
FRMCS User B is talking and listening in his own native language or dialect used in Country B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3.2 Pre-conditions | The French lead driver (i.e., an FRMCS User) is authorised to initiate point-to-point communications using Real-Time Speech to Speech translation when entering the German Railways.
The FRMCS System is aware of native language (e.g., French) of the French lead driver (e.g., configuration attributes or pre-selection by the driver).
Both French lead driver and German traffic controller have selected their roles to enable point-to-point communications using Real-Time Speech to Speech translation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3.3 Service flows | When crossing the borders from France to Germany, the French lead driver pre-selects the destination language (e.g., German), and, as an option, the source language (e.g., French). As an alternative, the FRMCS System or the language translation tool automatically detects the source language (based on e.g., speech recognition) and the destination language (based on e.g., the location of the lead driver) to be used for translation.
When an incident occurs, the French lead driver initiates a point-to-point communication using Real-Time Speech to Speech translation to the German traffic controller. Once initiated, the French lead driver orally dictates a description of the incident making use of technical railway vocabulary in its native language.
As an option, the French lead driver may then check the displayed translated text in French, his own language, before being sent for translation into German to the traffic controller.
The point-to-point communications using Real-Time Speech to Speech translation are encrypted to prevent eavesdropping.
Source speech, translated text in source language, translated text in destination language and destination speech are recorded (including metadata e.g., timestamp, originator, receiver) in case something bad happens and somebody wants to review the incident later.
Editor’s note: relevant metrics will be further elaborated. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.