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.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 enviro... |
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. |
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 witho... |
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 onc... |
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 tim... |
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 ... |
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 ... |
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 transf... |
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... |
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 t... |
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/... |
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 s... |
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-... |
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 t... |
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... |
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.17... |
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 FRM... |
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,... |
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... |
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 ... |
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 ... |
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 ... |
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 identit... |
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 MCV... |
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 FRM... |
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 MCV... |
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 MCV... |
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 establi... |
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 MCV... |
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 establi... |
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 MCV... |
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 F... |
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 MCV... |
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 ... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.