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 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 C... |
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 t... |
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 recog... |
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 ... |
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 n... |
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 n... |
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... |
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 t... |
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-... |
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 dat... |
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 tra... |
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 Sma... |
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. T... |
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. Th... |
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... |
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/... |
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 follo... |
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 ... |
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 th... |
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 Us... |
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 sh... |
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 periodi... |
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... |
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 whe... |
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
- Interrogat... |
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... |
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 suppo... |
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 reque... |
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... |
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 func... |
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 function... |
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... |
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 identiti... |
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... |
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, ser... |
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 u... |
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 ... |
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 ... |
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 th... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8 Use case: Interrogation of identities within a certain context |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.