hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3.4 Post-conditions | The German traffic controller listens to translated speech in its native language without any major errors of translation in rail terminology. The French lead driver is informed that translated speech has been delivered/received by the German traffic controller. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.3.5 Potential requirements and gap analysis | Editor’s note: potential requirements and gap analysis will be further elaborated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.4 Real-time Speech to Text (S2T) translation | 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 typing and receiving translated text in his own native language or dialect used in Country B.
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.
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, and translated text in destination language 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.
7.7.3.4 Post-conditions
The German traffic controller receives translated text in its native language without any major errors of translation in rail terminology. The French lead driver is informed that translated text has been delivered/received by the German traffic controller.
7.7.3.5 Potential requirements and gap analysis
Editor’s note: potential requirements and gap analysis will be further elaborated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.5 Real-time Text to Speech (T2S) translation | 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 typing and receiving translated text 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.
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.
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 enters text description of the incident making use of technical railway vocabulary in its native language.
The point-to-point communications using Real-Time Speech to Speech translation are encrypted to prevent eavesdropping.
Source text, 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.
7.7.3.4 Post-conditions
The German traffic controller listens to translated speech in its native language without any major errors of translation in rail terminology. The French lead driver is informed that translated text has been delivered/received by the German traffic controller.
7.7.3.5 Potential requirements and gap analysis
Editor’s note: potential requirements and gap analysis will be further elaborated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.6 Real-time Text to Text (T2T) translation | 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 typing and receiving translated text in his own native language or dialect used in Country A.
FRMCS User B is typing and receiving translated text in his own native language or dialect used in Country B.
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.
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 enters text description of the incident making use of technical railway vocabulary in its native language.
The point-to-point communications using Real-Time Speech to Speech translation are encrypted to prevent eavesdropping.
Source text and translated text in destination language 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.
7.7.3.4 Post-conditions
The German traffic controller receives translated text in its native language without any major errors of translation in rail terminology. The French lead driver is informed that translated text has been delivered/received by the German traffic controller.
7.7.3.5 Potential requirements and gap analysis
Editor’s note: potential requirements and gap analysis will be further elaborated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.7.7 Service interworking with GSM-R | Service interworking of real-time automatic translation of languages with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8 Business communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.1 Multimedia applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.1.1 Introduction | In this chapter, the following use cases related to Multimedia applications are defined:
• Live streaming of multimedia
• Bulk transfer of multimedia data bases from ground to train |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2 Use Case: Live streaming of multimedia | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2.1 Description | This use case describes the live streaming of multimedia content from ground to train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2.2 Pre-conditions | • FRMCS User equipment is registered into the FRMCS System.
• Passengers can access live streaming services through the FRMCS System in the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2.3 Service flows | 1. FRMCS System provides data communication for the live streaming services.
2. FRMCS User equipment requests data communication for the live streaming services from the FRMCS System.
3. FRMCS System allocates requested data communication for the FRMCS User equipment.
4. FRMCS User equipment allocates the communication to the passengers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2.4 Post-conditions | FRMCS User equipment deregisters from the FRMCS System upon the reception of live streaming is ceased. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-8.2.5-001]
The FRMCS System SHALL enable bandwidth for the live streaming inside the train through the FRMCS System.
22.261
Live streaming service covered by 22.261 Table 7.1-1.
[R-8.2.5-002]
The FRMCS User equipment SHALL be able to balance the bandwidth between the passengers.
22.261
Live streaming service covered by 22.261 Table 7.1-1.
NOTE: Live streaming of multimedia from ground to train is not considered to be a mission critical service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3 Use Case: Bulk transfer of multimedia from ground to train | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3.1 Description | This use case describes the transfer of multimedia databases from ground to train. The multimedia may contain movies, TV shows, cached webpages etc.
Figure 1 illustrates an example calculation of upload time of movies with different bitrates, when 1-100 movies are uploaded, and the upload speed is 1 Gbps.
Figure 8.3.1-1. An example calculation of upload time of movies with different bitrates and 1 Gbps upload speed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3.2 Pre-conditions | FRMCS System enables transfer of multimedia databases from ground to train while the train stops at the stations or is at the depot. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3.3 Service flows | 1. Train has stopped at the station or at the depot and
2. FRMCS User equipment responsible for the bandwidth allocation for the transfer of on-board multimedia database is registered into the FRMCS System
3. FRMCS User equipment asks from FRMCS System to allocate needed bandwidth for the transfer of the multimedia database upon request by the content server. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3.4 Post-conditions | FRMCS User equipment responsible for the bandwidth allocation for the transfer of on-board multimedia database de-registers from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-8.3.5-001]
For the sufficient transfer of large sized multimedia databases, the FRMCS System SHALL support throughput speed minimum of 1 Gbps.
22.289
22.261
TS 22.289 [R4.2.2-2] s
NOTE: Bulk transfer of multimedia from ground to train is not considered to be a mission critical service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4 Use case: Transportation convenience service for the passengers for the reduced mobility | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4.1 Description | In the Railway Smart Station, a transportation convenience service for the passengers with the reduced mobility can be feasible, such as a mobility service for the passengers to arrive at the desired destination.
Figure 8.4.1-1. Example of transport convenience service for passenger with reduced mobility |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4.2 Pre-conditions | 1. There exist feasible Mobile Intelligent Assistants in the Railway Smart Station, where the Mobile Intelligent Assistants support 3GPP system.
2. The Mobile Intelligent Assistants are operated under the central control system via 3GPP access.
3. There is at least one passenger with reduced mobility in the Railway Smart Station, where the weak passenger has difficulty moving toward the desired destination.
4. The passenger has an equipment supporting 3GPP access. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4.3 Service flows | 1. A passenger with reduced mobility is reserved in advance, where a Railway Smart Station already knows that the passenger needs help to get to the desired destination.
2. Once the passenger enters the Railway Smart Station, one Mobile Intelligent Assistant stands by for mobile support to the desired destination.
3. The Mobile Intelligent Assistant takes the passenger to the desired place. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4.4 Post-conditions | 1. The Railway Smart Station traces and manages the route of movement of the passenger with reduced mobility. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-8.4.5-001]
The FRMCS service shall be able to support obtaining and conveying location information as a scalable zone information describing the position of the UE supporting a Mobile Intelligent Assistant application.
A/T
N/A |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5 Use case: Multiple concurrent mobility services | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5.1 Description | In the Railway Smart Station, a transportation convenience service for the passengers with the reduced mobility can be feasible, such as a mobility service for the passengers to arrive at the desired destination.
Figure 8.5.1-1. Example of multiple concurrent mobility services |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5.2 Pre-conditions | 1. There exist feasible Mobile Intelligent Assistants in the smart station, where the Mobile Intelligent Assistants support 3GPP system.
2. The Mobile Intelligent Assistants are operated under the central control system via 3GPP access.
3. Each Mobile Intelligent Assistant supports corresponding mobility service.
4. There exist more than or equal to two mobility services, where each mobility service requires different location accuracy, and is supported by different Mobile Intelligent Assistant. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5.3 Service flows | 1. Two different mobility services are initiated by the central control system.
2. A Mobile Intelligent Assistant#1 and a Mobile Intelligent Assistant#2 move along the predetermined path. Here, each path is characterized by the representative location of corresponding zone.
3. The Mobile Intelligent Assistant#1 and the Mobile Intelligent Assistant#2 moves along the representative location of blue and red zone.
5. Two different mobility services are completed by the Mobile Intelligent Assistant #1 and the Mobile Intelligent Assistant #2, where the completion time can be different. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5.4 Post-conditions | 1. Two different mobility services are supported in the Railway Smart Station. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 8.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-8.5.5-001]
The FRMCS system shall support obtaining and conveying location information describing the positions of each UE supporting a Mobile Intelligent Assistant application with different location accuracy simultaneously.
A/T
N/A |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9 Critical support applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.1 Overview | Critical applications are essential for train movements, safety, shunting, presence, trackside maintenance, legal aspects such as emergency communications, etc. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2 Assured voice communication (AVC) | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.1 Introduction | In this chapter the use cases related to the function of assured voice communication are defined. Assured Voice Communication (AVC) shall provide an indication to FRMCS Users as soon as a voice communication link is interrupted. It is invoked on an existing voice communication between two or more FRMCS Users.
The following use cases are defined:
- Invocation of AVC
- Stopping AVC
- Degradation of a communication link (e.g. bad quality of the signal quality or interruption of a communication link)
- Extension of AVC |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2 Use case: Invocation of Assured Voice Communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2.1 Description | This use case describes the invocation of Assured Voice Communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2.2 Pre-conditions | A FRMCS User is part of a voice communication with one or more FRMCS Users for which Assured Voice Communication can be invoked either automatically or manually. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2.3 Service flows | Automatic Invocation
Upon establishment of a voice communication for which automatic AVC is activated, AVC will be invoked by the FRMCS System.
The involved FRMCS Users are informed about the successful activation of AVC.
Manual Invocation
The user invokes AVC in the FRMCS System.
The involved FRMCS Users are informed about the successful activation of AVC. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2.4 Post-conditions | The voice communication links of all FRMCS Users involved in the communication are supervised. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.2.2-001]
Upon establishment of a voice communication for which automatic AVC is activated, AVC shall be invoked by the FRMCS System.
A
22.280
R-6.2.1-001
But the AVC remains as OTT application while 3GPP building block provides the enabling framework."
[R-9.2.2-002]
If entitled, a FRMCS User shall be able to invoke AVC manually.
A
22.280
MCX Services take the approach that all communication are acknowledged and the MCPTT User is given the choice to proceed without acknowledgement 22.280 R-6.2.1-010 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3 Use case: Stopping Assured Voice Communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3.1 Description | This use case describes the deactivation of the communication link supervision. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3.2 Pre-conditions | A FRMCS User is part of a voice communication with one or more FRMCS Users for which Assured Voice Communication was invoked. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3.3 Service flows | Automatic stopping
If the ongoing voice communication is terminated by one of the involved users, the Assured Voice Communication is stopped.
The involved FRMCS Users are informed about the successful stop of AVC.
Manual stopping
The FRMCS User who has previously manually invoked AVC may stop AVC.
The involved FRMCS Users are informed about the successful stop of AVC. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3.4 Post-conditions | Automatic stopping
The FRMCS User is no longer part of a voice communication with one or more FRMCS Users.
Manual stopping
The FRMCS User is still part of a voice communication with one or more FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.2.3-001]
If the voice communication is terminated stopping of AVC shall be done by the FRMCS System automatically.
A
N/A
Implicit as done on burst basis
[R-9.2.3-002]
Only the FRMCS User who requested the end-to-end supervision shall be able to stop AVC.
A
22.280
Communication is acknowledged on a per talk burst basis so stopping that ack processing can be done by
R-6.2.1-008
R-6.2.1-010" |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4 Use case: Degradation of a communication link | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4.1 Description | Alternative 1: The FRMCS System provides a so called negative notification to the FRMCS Users as soon as voice communication link is interrupted.
Alternative 2: A positive notification will be given by the FRMCS System as long as the voice communication link is unaffected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4.2 Pre-conditions | A FRMCS User is part of a voice communication with one or more FRMCS Users.
AVC is invoked on all links of the voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4.3 Service flows | Positive Notification
The FRMCS System continuously checks whether the voice communication links are unaffected (e.g. bad quality of the signal quality or interruption of a communication link).
The FRMCS System indicates to all FRMCS Users involved in the voice communication service is working properly e.g.by a periodic audio signal.
If an interruption of at least one of the communication links is detected, the positive notification is immediately stopped.
If AVC itself fails, the positive notification shall be stopped immediately.
Active speech transmission shall suppress the positive notification to all FRMCS Users involved.
Optionally all FRMCS Users have to confirm their availability periodically (e.g. by pressing a button or by talking). If this confirmation is not received, AVC shall be stopped immediately.
A FRMCS User terminating his participation in the voice communication shall immediately stop AVC.
When AVC is stopped the ongoing voice communication is continued. Assured Voice Communication may be reinvoked for the remaining FRMCS Users of the ongoing voice communication.
Negative Notification
The FRMCS System continuously checks whether the voice communication links are unaffected (e.g. bad quality of the signal quality or interruption of a communication link).
If a degradation of a voice communication link is detected the FRMCS System warns all involved FRMCS Users, e.g. by generating a warning audio signal. If possible, the FRMCS User with the interrupted communication link shall also be warned.
If AVC itself fails, the negative notification shall be given immediately e.g. by a warning tone.
A FRMCS User terminating his participation in the voice communication shall stop AVC and a negative notification shall be given immediately e.g. by a warning tone.
Optionally all FRMCS Users have to confirm their availability periodically (e.g. by pressing a button or by talking). If this confirmation is not received, AVC shall be stopped and a negative notification shall be given immediately e.g. by a warning tone.
When AVC is stopped the ongoing voice communication is continued. Assured Voice Communication may be reinvoked for the remaining FRMCS Users of the ongoing voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4.4 Post-conditions | The voice communication between the remaining FRMCS Users continues. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.2.4-001]
The FRMCS System shall be able to continuously supervise the voice communication links to all involved FRMCS Users.
A
22.280
22.179
Result of this supervision is provided by
22.179 6.2.1-001-010
22.280 5.20.2-001
[R-9.2.4-001a]
The FRMCS System shall be able to provide indications to AVC on the signal quality of the link/connection to take decision to maintain a reliable communication path.
T
22.261
Covered by QoS monitoring.
[R-9.2.4-002]
If a degradation of a voice communication link is detected, the remaining FRMCS Users shall be informed. The ongoing voice communication among the remaining FRMCS Users shall continue.
A FRMCS User quitting the communication shall cause the AVC to stop.
A
22.280
22.179
Done by
22.179 6.2.1-001-010
22.280 5.20.2-001
Supervision is done on a per talk burst basis, if user drops out or de-affiliates during the burst 22.280 5.20.2-001 takes effect, if user drop out between the bursts this will be noticed during the ack process as described in 22.179 6.2.1-001-010
[R-9.2.4-003]
The FRMCS System shall be able to inform the FRMCS Users of an interrupted voice communication link by either positive or negative notification.
A
22.179
R-6.2.1-008
R-6.2.1-009
[R-9.2.4-004]
In case of positive notification all FRMCS Users shall receive a periodic audio signal while no voice communication is ongoing. Active speech transmission shall supress the positive notification.
A
22.280
22.179"
Information conveyed to UE by
22.179 6.2.1-001-010
22.280 5.20.2-001R-6.2.1-002
how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication
It rather should be notified at the set-up that certain users did not acknowledge see 22.179 6.2.1-010
[R-9.2.4-005]
In case of negative notification all FRMCS Users shall receive an audio signal when an interrupted voice communication link is detected, the AVC has failed or a FRMCS terminated his participation in the voice communication.
A
22.280
22.179"
Information conveyed to UE by
22.179 6.2.1-001-010
22.280 5.20.2-001R-6.2.1-002
how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication
It rather should be notified at the set-up that certain users did not acknowledge see 22.179 6.2.1-010a
[R-9.2.4-006]
Negative notification shall be stopped after acknowledgement by all remaining FRMCS Users in the voice communication.
A
22.280
22.179"
Information conveyed to UE by
22.179 6.2.1-001-010
22.280 5.20.2-001R-6.2.1-002
how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication
It rather should be notified at the set-up that certain users did not acknowledge see 22.179 6.2.1-010a |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5 Use case: Extension of Assured Voice Communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5.1 Description | The assured voice communication application shall provide the ability to extend an assured voice communication to a user who has joined an ongoing communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5.2 Pre-conditions | The use of Assured Voice Communication is activated for the ongoing voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5.3 Service flows | If a user joins an ongoing assured voice communication, the initiator of the assured voice communication is informed. The joining user is not supervised yet but is part of the communication.
The initiator shall have the option to extend the assured voice communication to this new user. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.