hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5.4 Post-conditions | If the assured voice communication is extended, the new user is supervised by the assured voice communication.
If the assured voice communication is not extended to the new user, the new user is not supervised by the assured voice communication but remains part of the existing ongoing communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.2.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.2.5-001]
The initiator shall be able to extend the AVC to a new FRMCS User in the communication.
A
22.280
This is done automatically due to the talk burst nature and the Automatic user regrouping in 22.280 6.6.4.2.
Question is whether this always makes sense if the group membership changes frequently from talk burst to talk burst
For this reason, a requirement is added allowing to exclude such automatic user regrouping groups from the ack mechanism in general. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3 Functional identities and role management | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.1 Introduction | In this chapter the use cases related to functional identities and role management are defined:
- Registration to a functional identity
- Deregistration of a functional identity
- FRMCS User changing functional identity
- User log-in to the system
- User log-out from the system
- Presentation of identities
- Interrogation of identities within a certain context
Examples of Role management, like functional identities, FRMCS Equipment Identities, etc. in the railway environment are covered by annex A. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.2 General pre-conditions | In order to fully understand the uses cases in this chapter, Figure 9.3.2-1 illustrates the different steps required to complete the registration process.
Figure 9.3.2-1: Example of Role management
In this definition, it is needed to make a distinction between different types of FRMCS Equipment. The following are, as a principle, defined:
a) FRMCS Equipment without MMI, without the possibility to be addressed via a functional identity related to the equipment (e.g. sensor in the track or simple modem operation)
b) FRMCS Equipment that can be registered to a functional identity related to the equipment (e.g. maintenance log collecting device connected to a power station) but without other FRMCS User login
c) FRMCS Equipment that can be registered to a functional identity and that allows a FRMCS User to login and register to functional identities related to the user (e.g. cab radio)
d) FRMCS Equipment that cannot register to a functional identity, but that allows a FRMS User to login and to register to functional identities related to the user (e.g. a generic handheld device)
Steps:
1. UE-Power on: The UE has started up and is attached to the FRMCS network on telecoms level. The UE is reachable via its subscriber identity address.
2. Start FRMCS Application: On the UE the FRMCS Application start up and is ready for use.
3. FRMCS Equipment login: The FRMCS Application is logging in into the FRMCS System and the FRMCS Equipment becomes known to the FRMCS System.
4. Initialise FRMCS Equipment type: the type of FRMCS Equipment used is identified.
At this stage of the user flow four different routes can be followed, based on the determined FRMCS Equipment type of the FRMCS Equipment.
Type a) “sensor”:
• No action required. The FRMCS Equipment is now reachable via its subscriber identity address.
After this step the process of registration is completed.
Type b) “Announcement System”:
• Register to a functional identity: the FRMCS Equipment will request for a registration on a functional number. This functional number is related to the equipment and identifies the device, like a PA system on a train.
• Functional identity added: the request for a functional identity is granted by the FRMCS System. The end user device is now reachable via its functional identity.
After this step the process of registration is completed.
Type c) “cab radio”:
• Register to a functional identity: the FRMCS Equipment will request for a registration on a functional identity. This functional identity is related to the FRMCS Equipment and identifies the environment where the equipment is used, like a cab radio in a cabin of a train.
• Functional identity added: The FRMCS User is now only reachable via all of its functional identities related to the FRMCS Equipment.
Type d) “Handheld”:
Next, for both the types c) and d) the following steps apply:
• User login dialog: the user is presented with a log-in MMI action. The user can now login into the FRMCS System. By successfully logging into the FRMCS System the user becomes a FRMCS User.
• FRMCS User: The FRMCS User is now reachable via its FRMCS User Identity (and in case c) the functional identity registered by the FRMCS Equipment).
• Register to a functional identity: the FRMCS User may request for a registration on a functional identity. This functional identity relates to the FRMCS User and identifies the role of the FRMCS User e.g. driver, controller etc. and the environment e.g. train number.
• Functional identity added: The FRMCS User is now reachable via all the functional identities registered to the user (Further, the FRMCS Equipment is reachable via its registered functional identity(ies).
After this step the process of registration is completed.
Note: Use cases related to power up the UE until complete initialisation of the equipment type are covered in chapter 5. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.2.1 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.2-001]
The FRMCS System shall be able to make use of the underlying transport system's subscriber identities.
A
22.280
This requirement can be supported by existing MCCore requirements.
[R-9.3.2-002]
The FRMCS System shall support a FRMCS User identity per FRMCS User.
A
22.280
This requirement can be supported by existing MCCore requirements.
[R-9.3.2-003]
The FRMCS System shall support functional identities.
A
22.280
This requirement is partly covered by MCCore, new and additional types of identities need to be supported.
[R-9.3.2-004]
The UE shall be reachable by its subscriber identity.
A
22.280
This requirement can be supported by existing 3GPP requirements.
[R-9.3.2-004a]
The FRMCS system shall be able to inhibit the use of the underlying transport system’s subscriber identities for communication
A
22.280
Implicit.
[R-5.12-002] The MCX Service supports MCX Service User ID + functional alias, independent of subscriver identity assigned by 3GPP operator to UE.
[R-9.3.2-005]
The FRMCS User shall be reachable by its FRMCS User identity.
A
22.280
This requirement can be supported by existing MCCore requirements.
[R-9.3.2-006]
The FRMCS User shall be reachable by its functional identity/ies.
A
22.280
This requirement is partly covered by MCCore, new and additional types of identities need to be supported.
[R-9.3.2-007]
At the time of initialisation the FRMCS-system shall be able to determine the FRMCS Equipment Type.
A
N/A
Outside scope of 3GPP standardization. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3 Use case: Registration to a functional identity | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3.1 Description | A FRMCS User or the FRMCS Equipment shall be able to register to one or multiple functional identities. A functional identity can therefore be equipment related or user related. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3.2 Pre-conditions | The equipment type is identified.
Functional registration of the user, the user is logged in into the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3.3 Service flows | Requested functional identity is not in use
The FRMCS User or the FRMCS-equipment selects the functional identity. The identity can be selected from a list based on the location of the FRMCS User, operational schedules, etc. or the functional identity can be entered manually.
The FRMCS User or the FRMCS-equipment requests the FRMCS System to register the new functional identity.
The FRMCS System informs the FRMCS User or the FRMCS-equipment about the outcome of the registration request.
Requested functional identity that is in use
The FRMCS User or the FRMCS-equipment selects the functional identity. The identity can be selected from a list based on the location of the FRMCS User, operational schedules, etc. or the functional identity can be entered manually.
The FRMCS User or the FRMCS-equipment requests the FRMCS System to register the new functional identity.
The FRMCS User is or the FRMCS-equipment informed of the functional identity already in use.
The FRMCS User or the FRMCS-equipment shall be able to select from the following options:
• Cancel the registration
• If the selected functional identity allows take over the functional identity.
• If the selected functional identity allows register as an additional FRMCS User to this functional identity.
The FRMCS System informs the FRMCS User about the outcome of the registration request.
In the case of taking over a functional identity, the FRMCS System deregisters the other FRMCS User or FRMCS-equipment from this particular functional identity. The deregistered FRMCS User or the FRMCS-equipment gets informed about the deregistration by the FRMCS System.
Registration by the Railway Subsystem of the FRMCS System
Based on the user identification, operational conditions, like schedules when entering the train, location, time, recent activity etc., the Railway Subsystem shall be able automatically register a FRMCS User or an FRMCS Equipment to a functional identity.
The FRMCS User gets informed about the registration by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3.4 Post-conditions | In case of successful registration, the FRMCS User or the FRMCS-equipment can be reached based on the functional identity. The FRMCS User or the FRMCS-equipment can be registered to different functional identities. The FRMCS User or the FRMCS-equipment are also reachable by using the FRMCS Equipment Identity, the FRMCS User Identity (if logged in) and its subscriber identity.
In case of successful registration and based on system configuration, the FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully registered functional identity.
If the FRMCS System has not accepted the registration, the FRMCS User or the FRMCS-equipment cannot be reached on a particular functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.3-001]
The FRMCS User or the FRMCS-equipment shall be able to register to a functional identity.
A
TS 22.280
5.9a2
[R-9.3.3-002]
To select from, the FRMCS System shall provide the FRMCS User or the FRMCS-equipment a list of functional identities. The list contains functional identities based on a certain context, like location of the user, operational schedule, etc. The FRMCS User or the FRMCS-equipment shall also be able to perform a registration of an unlisted functional identity.
A
TS 22.280
.Predefined list of functional identities based on criteria: [R-5.9a-004]
.Unlisted functional identity: [R-5.9a-010]
[R-9.3.3-003]
The FRMCS System shall inform the FRMCS User or the FRMCS-equipment of the outcome of the registration request.
A
TS 22.280
[R-5.9a-025]
[R-9.3.3-004]
In the case the functional identity is already in use, the FRMCS System shall advise the FRMCS User or the FRMCS-equipment about options to
• cancel the registration,
• take over the functional identity
• register as an additional identity.
A
TS 22.280
Covered.
[R-5.9a-007]: sharing FA first (no user selection), then
[R-5.9a-008]: take over (with user selection). If take over not selected, registration considered canceled.
[R-9.3.3-005]
The FRMCS System shall be able to register a FRMCS-user or the Railway Subsystem without human intervention. For example, automatic registration can be initiated by:
• user identification
• operational conditions, like schedules when entering the train (for example by using Near Field Communication, Smart Card etc.)
• location
• time
• recent activity
• Smart cards or RFID tokens in the vicinity of the UE
• FRMCS Equipment Type
• etc.
A
TS 22.280
[R-5.9a-015]
[R-5.9a-018]
[R-9.3.3-006]
The FRMCS System shall support multiple functional identities per FRMCS User or FRMCS Equipment.
A
TS 22.280
[R-5.9a-001]
[R-9.3.3-007]
The FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully registered functional identity.
A
TS 22.280
Covered in on-network with affiliation mechanism + automatic information when affiliation information changes in a group ([R-6.4.5-003a]). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4 Use case: Deregistration of a functional identity | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4.1 Description | A FRMCS User or the FRMCS-equipment shall be able to deregister from one or multiple functional identities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4.2 Pre-conditions | The FRMCS User or the FRMCS-equipment has at least one functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4.3 Service flows | Deregistration functional identity initiated by the FRMCS User
The FRMCS User or the FRMCS-equipment chooses the functional identities to be deregistered among the list of currently registered functional identities by:
• electing a set of functional identities (the application may select the appropriate set of functional identities automatically)
• selecting one functional identity
The FRMCS System informs the FRMCS User or the FRMCS-equipment about the outcome of the registration request.
Deregistration by the Railway Subsystem
Based on certain criteria the FRMCS System deregisters a FRMCS User or the FRMCS-equipment from one or multiple functional identities and informs the FRMCS User or the FRMCS-equipment about the deregistration.
For example, possible criteria are timer, location, operational schedules, another FRMCS User taking over the functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4.4 Post-conditions | If the FRMCS System has deregistered the functional identity, the previously registered FRMCS User (s) or FRMCS-equipment are not any longer reachable on this particular functional identity.
If the FRMCS System has deregistered the functional identity and based on system configuration, the FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully deregistered functional identity.
If the FRMCS System was unable to deregister the functional identity, the actually registered FRMCS User or FRMCS-equipment remains active and can be reached on this functional identity.
In addition, the FRMCS User is reachable using the FRMCS Equipment Identity, its user identity (if logged in) and its subscriber identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.4-001]
The FRMCS User or the FRMCS-equipment shall be able to deregister from a functional identity.
A
TS 22.280
5.9a2
[R-9.3.4-002]
During the deregistration process, the FRMCS System shall provide a list of functional identities to the FRMCS User or the FRMCS-equipment, to select for deregistration.
A
TS 22.280
[R-5.9a-004]
[R-9.3.4-003]
The FRMCS User or the FRMCS-equipment shall also be able to perform a deregistration of a functional identity that might not be part of the list provided by the FRMCS System. Then a manual input is required by the FRMCS User.
A
TS 22.280
[R-5.9a-010]
[R-9.3.4-004]
The FRMCS System shall inform the FRMCS User or the FRMCS-equipment about the outcome of a deregistration request.
A
TS 22.280
[R-5.9a-025]
[R-9.3.4-005]
At any time, the Railway Subsystem of the FRMCS System shall be able to deregister any functional identity.
An automatic deregistration request can be based on:
• user identification
• operational conditions, like schedules when entering the train (for example by using Near Field Communication, Smart Card etc.)
• location
• time
• recent activity
• Smart cards or RFID tokens in the vicinity of the UE
• FRMCS Equipment Type
• etc.
A
TS 22.280
[R-5.9a-015]
[R-5.9a-018]
[R-9.3.4-006]
The FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully deregistered functional identity.
A
TS 22.280
Covered in on-network with affiliation mechanism + automatic information when affiliation information changes in a group ([R-6.4.5-003a]). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5 Use case: User log-in to the FRMCS System | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5.1 Description | The user is identified by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5.2 Pre-conditions | The equipment type is initialized.
The FRMCS Equipment provides suitable means to the user to log in. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5.3 Service flows | The user performs the log-in procedure.
Successful identification
The user is informed about the successful log-in into the FRMCS System. The user has now become a FRMCS User identified by a FRMCS User identity.
Unsuccessful identification
The user is informed about the unsuccessful log-in to the FRMCS System. The user is redirected to the log-in procedure. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5.4 Post-conditions | The FRMCS User is identified in the FRMCS System and can register a functional identity.
The FRMCS User is reachable by the FRMCS User identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.5-001]
The FRMCS System shall allow a user to log into the FRMCS System using its FRMCS User Identity to make use of the services provided by the FRMCS System
A
TS 22.280
TS 22.179
3GPP building blocks = user authentication, service authorization and group affiliation.
Sign-in/sign-off and 3GPP building blocks:
22.280 [R-5.1.1-001]
22.179 section 4.5.
[R-9.3.5-002]
The FRMCS System shall provide service only to FRMCS Users logged in into the FRMCS System.
A
TS 22.280
TS 22.179
3GPP building blocks = user authentication, service authorization and group affiliation.
Sign-in/sign-off and 3GPP building blocks:
22.280 [R-5.1.1-001]
22.179 section 4.5 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6 Use case: User log-out from FRMCS System | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6.1 Description | The FRMCS User is logged out of the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6.2 Pre-conditions | The FRMCS User is logged-in the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6.3 Service flows | The FRMCS User performs the log-out procedure.
Successful log-out
The FRMCS System deregisters all functional identities of the FRMCS User.
The FRMCS System logs out the FRMCS User.
The FRMCS User is informed about the successful log-out from the FRMCS System.
Unsuccessful log-out
The FRMCS User is informed about the unsuccessful log-out to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6.4 Post-conditions | The FRMCS User is logged out of the FRMCS System. The FRMCS Equipment is still registered to the FRMCS System.
The FRMCS Equipment is reachable by the subscriber identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.6-001]
The FRMCS System shall provide a notification to the FRMCS User when the FRMCS User is logged-out of the FRMCS System
A
Partly covered by TS 22.280 & 22.179.
Remaining functionality are outside scope of 3GPP.
No specific login/logout procedure in TS 22.280. so no notification.
3GPP building blocks = user authentication, service authorization and group affiliation.
Sign-in/sign-off and 3GPP building blocks:
22.280 [R-5.1.1-001]
22.179 section 4.5.
[R-9.3.6-002]
The FRMCS System shall provide the FRMCS User the necessary means to log out of the FRMCS System.
A
Partly covered by TS 22.280 & 22.179.
Remaining functionality are outside scope of 3GPP.
No specific login/logout procedure in TS 22.280.
3GPP building blocks = user authentication, service authorization and group affiliation.
Sign-in/sign-off and 3GPP building blocks:
22.280 [R-5.1.1-001]
22.179 section 4.5.
[R-9.3.6-003]
By logging out all functional identities of a FRMCS User are deregistered from the FRMCS User.
A
Partly covered by TS 22.280 & 22.179.
Remaining functionality are outside scope of 3GPP.
Partly covered by [R-5.9a-018] but login/logoff from the MCX Service system not defined.
3GPP building blocks = user authentication, service authorization and group affiliation.
Sign-in/sign-off and 3GPP building blocks:
22.280 [R-5.1.1-001]
22.179 section 4.5.
[R-9.3.6-004]
After logging out the FRMCS User, the FRMCS Equipment shall be reachable via the subscriber identity.
A
Covered
This requirement can be supported by existing MCCore requirements in TS:
22.280,
22.278,
22.261. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7 Use case: Presentation of identities | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7.1 Description | A FRMCS User or the FRMCS-equipment shall be able to be identified by the functional identity (ies) to other FRMCS Users |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7.2 Pre-conditions | The FRMCS User or the FRMCS-equipment is registered to at least one functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7.3 Service flows | During call initiation
The identities of the initiating entity (functional identity of a user, functional identity of equipment, user identity and subscriber identity) are to be passed and presented to the other FRMCS Users during communication.
The FRMCS System passes the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, selection from the initiating entity, etc.).
If multiple functional identities are used by the FRMCS User, the presentation is based on certain context (e.g. a call to a train Controller shows the running number, a call to a maintenance Controller shows the engine number).
If the functional identity is not available, the FRMCS User identity is to be presented.
If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented.
During a call
The identities of the connected FRMCS User (s) (functional identity of a user, functional identity of equipment, user identity and subscriber identity) are forwarded to the FRMCS Users participating to the call.
The FRMCS System passes the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, etc.).
If multiple functional identities are used by the FRMCS User, the presentation is based on certain context (e.g. a call to a train Controller shows the running number, a call to a maintenance Controller shows the engine number).
If the functional identity is not available, the FRMCS User identity is to be presented.
If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented.
The functional identity(ies) of the talking FRMCS User is/are to be indicated to the listening FRMCS User (s).
If the functional identity is not available, the FRMCS User identity is to be presented.
If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7.4 Post-conditions | The FRMCS Users are informed about the FRMCS User initiating the communication initiator.
The FRMCS User is informed about who are the participants of the call.
The FRMCS User has at least one functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.7.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.7-001]
During communication initiation, the identities of the initiating entity (functional identity of a user, functional identity of equipment, user identity and subscriber identity) shall be passed to the FRMCS User (s) of the receiver(s) of the call.
A
TS 22.280
This requirement is partly covered by MCCore, new and additional types of identities need to be supported.]
[R-6.4.3-001]: only identification of the transmitting participant is sent to all other affiliated members.
TS 22.280
[R-5.9a-002]
[R-5.9a-020]
[R-5.9a-022]
[R-5.9a-023]
[R-9.3.7-002]
During a communication, the identities of the connected FRMCS User (s) (functional identity of a user, functional identity of equipment, user identity and subscriber identity) shall be sent to the FRMCS User (s) participants of the call.
A
TS 22.280
This requirement is partly covered by MCCore, new and additional types of identities need to be supported.
TS 22.280
[R-5.9a-002]
[R-5.9a-020]
[R-5.9a-022]
[R-5.9a-023]
[R-6.9-004]
[R-9.3.7-003]
The FRMCS User (s) shall be presented with the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, etc.).
A
TS 22.280
Partly covered: functional identity based on context are provide to the FRMCS User on demand for activation. Only activated functional alias(ses) are presented.
TS 22.280
[R-5.9a-002]
[R-5.9a-020]
[R-5.9a-022]
[R-5.9a-023]
[R-9.3.7-004]
If a functional identity is not available, the FRMCS System shall present the FRMCS User identity.
A
TS 22.280
Partly covered: [R-6.4.3-001] Only the MCX Service User ID of the transmitting participant is sent to all other affiliated members.
[R-9.3.7-005]
If both the functional identity and the FRMCS User identity are not available, the FRMCS System shall present the subscriber identity.
A
TS 22.280
TS 22.278
TS 22.261
This requirement can be supported by existing MCCore requirements. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8 Use case: Interrogation of identities within a certain context | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8.1 Description | A FRMCS User or the FRMCS-equipment is able to recognize which other functional identities are present within a certain context (for example train, region, communication group, Railway Emergency Communication, all Drivers on a station, etc.). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8.2 Pre-conditions | The FRMCS-equipment is initialised. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8.3 Service flows | Interrogation of functional identities
The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own functional identity(ies) or the functional identity of other FRMCS Users or FRMCS-equipment based on a FRMCS User identity or a subscriber identity.
The FRMCS System returns the functional identity(ies) of the particular FRMCS User or FRMCS-equipment.
Interrogation of FRMCS User identities
The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own or other FRMCS User identity of FRMCS User (s) based on a functional identity or a subscriber identity.
The FRMCS System returns the FRMCS User identity of the particular FRMCS User (s).
Interrogation of a subscriber identity
The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own or other FRMCS Equipment Identity based on a functional identity or a FRMCS User identity.
The FRMCS System returns the particular subscriber identity.
Interrogation of functional identity(ies) in a certain context
The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the functional identities of own or other FRMCS Users within a certain context.
The FRMCS System returns to the FRMCS User or the FRMCS-equipment a set of functional identities (own or other) within the certain context. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8.4 Post-conditions | The requesting FRMCS User or FRMCS-equipment is informed about the own or other FRMCS Users / FRMCS-equipment with a functional identity within a certain context, for example train, region, communication group, Railway Emergency Communication, all Drivers on a station, etc. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.