hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.8.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.8-001]
The FRMCS User or the FRMCS-equipment shall be able to interrogate the FRMCS System to provide the functional identity(ies) registered to a certain FRMCS User identity.
The FRMCS System shall return the functional identity(ies) of the FRMCS User.
A
TS 22.280
TS 22.280
R-5.9a-011
R-5.9a-012
[R-9.3.8-002]
The FRMCS User or the FRMCS-equipment shall be able to interrogate the FRMCS System to provide the functional identity(ies) based on a subscriber identity.
The FRMCS System shall return the functional identity(ies) of a subscriber identity.
A
TS 22.280
TS 22.280
R-5.9a-011
R-5.9a-012
[R-9.3.8-003]
The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the FRMCS User identity registered to a functional identity.
The FRMCS System shall return the FRMCS User identity/identities.
A
TS 22.280
TS 22.280
R-5.9a-011
R-5.9a-012
[R-9.3.8-004]
The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the FRMCS User identity based on a subscriber identity.
The FRMCS System shall return the FRMCS User identity/identities.
A
TS 22.280
TS 22.280
R-5.9a-011
R-5.9a-012
[R-9.3.8-005]
The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the subscriber identity based on a functional identity
The FRMCS System shall return the subscriber identity(ies).
A
TS 22.280
[R-5.9a-011]
9.3.9 Use case: Service interworking with GSM-R
9.3.9.1 Description
Service interworking with legacy communication systems is of importance for the time period both systems have to coexist. In this section service interworking between the GSM-R System and the FRMCS System for functional identities and its associated roles will be addressed.
Functional Address
On top of the E.164 numbering plan alternative addressing scheme called functional addressing is used in the context with GSM-R. Functional addressing scheme allows the establishment of communication without knowing each E.164 number associated with a particular train. A functional address consists of:
IC+CT+UN
IC International code is used to route calls to the appropriate GSM-R network
CT Call Type prefix defines how to interpret the User Number (UN) as train function number, engine function number, group calls etc.
UN User Number is of variable length and depends on the information i.e. train function number etc. Within the UN a Functional Code (FC) is associated and provides the information of the person or equipment on a particular train, or a particular team within a given area. Therefore, the UN consists of User Identification Number (UIN) i.e. train number etc. and the Functional Code (FC) resulting into: UN= UIN+FC
A functional address only consists of numeric characters.
9.3.9.2 Pre-conditions
Following user addressing scenarios applies between FRMCS System and GSM-R system when using alternative addressing schemes in FRMCS:
A GSM-R user is able to obtain communication services from the GSM-R system. E.164 numbering plan and functional addressing scheme applies.
A FRMCS User is able to obtain communication services from the FRMCS System or from the GSM-R system. If the FRMCS User, in this sense the FRMCS Equipment is registered to the FRMCS System, user addressing of the FRMCS system applies comprising the use of functional identity addressing scheme. If the FRMCS Equipment is registered to the GSM-R system, E.164 numbering plan and functional addressing i.e. IC+CT+UIN+FC scheme applies.
For a train route which encompasses both GSM-R and FRMCS coverage areas the functional identity registration for users and equipment travelling this route shall be made in two parallel entries in the respective GSM-R functional addressing and FRMCS Functional Aliasing databases.
Any subsequent modification of functional addressing or functional aliasing while the user or equipment is registered shall be done in parallel on both systems
The deregistration of the functional aliasing or functional addressing for the user or equipment with parallel registration shall be deregistered in parallel.
9.3.9.3 Service flows
FRMCS User relocates from GSM-R system to the FRMCS System
When the FRMCS Equipment relocates from GSM-R system to the FRMCS System, the applicable functional address(es) associated with the FRMCS User require(s) a conversion to the functional identity format applicable within the FRMCS System. The functional address remains active until the corresponding functional identity becomes deactivated.
FRMCS User relocates from FRMCS System to the GSM-R system
When the FRMCS Equipment relocates from RMCS System to the GSM-R system, the applicable functional identity or identities associated with FRMCS user require(s) a conversion to the functional address format applicable within the GSM-R system. The functional identity or identities remains active until the corresponding functional address becomes deactivated.
Bilateral communication addressing between FRMCS System and GSM-R
A FRMCS User establishes a communication using the functional identity of another FRMCS User whose FRMCS Equipment is registered to GSM-R.
A FRMCS User establishes a communication using the functional address of a GSM-R user whose GSM-R equipment is registered to GSM-R.
A GSM-R user establishes a communication using the functional identity of a FRMCS User.
9.3.9.4 Post-conditions
After successful relocation following is applicable:
• From GSM-R point of view, the FRMCS User is reachable for communication by its functional address.
• From FRMCS System point of view, the FRMCS User is reachable for communication by its functional identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.3.9.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.3.9-001]
The FRMCS System shall support the conversion between functional identity encompassing the associated role and functional addressing as part of the GSM-R system.
A
22.179
22.280
22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005]
[R-9.3.9-002]
The FRMCS System shall support functional addressing format consisting of:
IC+CT+UN
IC International code is used to route calls to the appropriate GSM-R network
CT Call Type prefix defines how to interpret the User Number (UN) as train function number, engine function number, group calls etc.
UN User Number is of variable length and depends on the information i.e. train function number etc. Within the UN a Functional Code (FC) is associated and provides the information of the person or equipment on a particular train, or a particular team within a given area. Therefore, the UN consists of User Identification Number (UIN) i.e. train number etc. and the Functional Code (FC) resulting into: UN= UIN+FC
A functional address only consists of numeric characters.
A
22.280
[ [R-5.9a-014]
[R-9.3.9-003]
A FRMCS User shall be reachable by its FRMCS Functional Identity if the FRMCS Equipment is registered to the GSM-R system
A
22.179
22.280
22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005]
[R-9.3.9-004]
A GSM-R User shall be reachable if a FRMCS User is registered to the FRMSC System using the functional address of the particular GSM-R user.
A
22.179
22.280
22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005
[R-9.3.9-005]
A FRMCS User shall be reachable if a GSM-R user uses the functional identity of the particular FRMCS User.
A
22.179
22.280
[ 22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4 Location services related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.1 Introduction | In this chapter the use cases related to location services are defined. The following use cases are defined:
• Provide location information
• Request for location information
• Request for identities based on location
The location information of an FRMCS Equipment consists of the following elements:
• Geographic Location,
• Velocity (the combination of speed and direction),
• Infra Location (additional information specifying railway infra elements; for example: signal 123, switch 456, track section 789A, etcetera), and
• Quality of Service information (horizontal and vertical accuracy, response time, QoS class, accuracy of Infra Location). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2 Use Case: Provide location information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2.1 Description | The FRMCS Equipment provides its location information to the FRMCS System for further processing e.g. for automatic train operation. External systems can be supported in providing additional location information with or without functional identity reference to the FRMCS System for further processing.
The location information may be shared directly with other applications on the same FRMCS Equipment without the involvement of the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2.2 Pre-conditions | The FRMCS Equipment supports some mechanisms to obtain its location. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2.3 Service flows | The FRMCS Equipment determines its current location in a periodic or an event-triggered manner. The frequency of the location reporting may change according to the application requirements.
The FRMCS Equipment reports location information that may include its applicable FRMCS Equipment Identity. At any time, upon request, the FRMCS Equipment shall be able to report its location information.
External systems can provide additional information to the FRMCS System in order to improve location accuracy of an FRMCS Equipment.
The received location information is stored by FRMCS System.
In case of periodic location reporting, the FRMCS System supervises the continuous supply of the location information. If the supply of periodic location information by the FRMCS Equipment stops, the FRMCS System initiates the re-establishment of the periodic location information data flow. The FRMCS System can correlate other identities from the FRMCS Equipment Identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2.4 Post-conditions | The location information of the FRMCS Equipment is available in the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.4.2-001]
The FRMCS Equipment shall be able to provide its location to the FRMCS System.
A
22.280
This requirement can be supported by existing 3GPP requirements
[R-9.4.2-001a]
The location information of an FRMCS Equipment shall consist of:
• The geographic location,
• The velocity,
• The infra location, and
• The Quality of service information.
A
22.071
Partly covered by TS 22.071.
Location Information of a UE consists of Geographic Location, Velocity, Civic Location and Quality of Service information.
Civic location (also called Dispatchable Location) is only applicable to emergency services based on regional regulatory requirements (wireless 911 calls).
[R-9.4.2-002]
The FRMCS System shall be able to request the FRMCS Equipment to provide its location.
A
22.280
This requirement can be supported by existing 3GPP requirements
[R-9.4.2-003]
The FRMCS System shall be able to request the FRMCS Equipment to provide its location periodically.
A
22.280
This requirement can be supported by existing 3GPP requirements
[R-9.4.2-004]
The FRMCS System shall be able to request the FRMCS Equipment to stop providing its location periodically.
A
22.280
This requirement can be supported by existing 3GPP requirements
[R-9.4.2-005]
The FRMCS System shall be able to handle additional location information from other external sources.
A
22.280 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3 Use Case: Request for location information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3.1 Description | A FRMCS User, an application or an External System can request the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3.2 Pre-conditions | The FRMCS User, an application or an External System, is entitled to request location information from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3.3 Service flows | A FRMCS User, an application or an External System requests location information to the FRMCS System based on a functional identity, FRMCS User identity or FRMCS Equipment Identity.
The location requesting entity can request for a single location information or a periodical update of the location information.
The location requesting entity can send a request to the FRMCS System to stop the periodical update of location information.
Positive outcome
The FRMCS System provides the location information as requested, either once or periodically.
Negative outcome
The location information is not available, or the identity is not known in the FRMCS System.
The FRMCS System sends a response back to the requesting FRMCS User, application or External System if the location information is not available. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3.4 Post-conditions | The location information is provided, if available. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.4.3-001]
Upon request from FRMCS Users, applications or External Systems the FRMCS System shall be able to provide the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity.
A
Partly covered by TS 22.280.
Remaining functionality are outside scope of 3GPP.
This requirement is partly covered by TS 22.280 [R-5.9a-027] and TS 22.280 [R-6.12-006].
[R-9.4.3-002]
Upon request from FRMCS Users, applications or External Systems the FRMCS System shall be able to periodically provide the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity.
A
Partly covered by TS 22.280.
Remaining functionality are outside scope of 3GPP.
This requirement is partly covered by TS 22.280 [R-6.12-006].
[R-9.4.3-003]
The FRMCS System shall only allow the FRMCS User, the application or the External System initially requesting periodic location reporting to stop the periodic location reporting.
A
Partly covered by TS 22.280.
Remaining functionality are outside scope of 3GPP.
This requirement is partly covered by TS 22.280 [R-5.11-005] and TS 22.280 [R-6.12-007]. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4 Use Case: Request for identities in a certain area | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4.1 Description | A FRMCS User, an application or an External System can request identities based on location information from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4.2 Pre-conditions | The FRMCS User, an application or an External System, is entitled to request location information from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4.3 Service flows | The FRMCS User, an application or an External System requests the FRMCS System to provide a list of functional identities, FRMCS User identities or FRMCS Equipment Identities at a certain point, area, station, track section, etc.
The FRMCS User, an application or an External System can request the list of identities to be given once or periodically by the FRMCS System.
Only the FRMCS User, the application or the External System initially requesting periodic reporting can stop the periodic reporting by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4.4 Post-conditions | The FRMCS System provides the list of identities as requested. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.4.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.4.4-001]
The FRMCS System shall allow a FRMCS User, an application or an External System to request a list of functional identities, FRMCS User identities or FRMCS Equipment Identities in a certain area either periodically or as a onetime request.
A
Covered by TS 22.280.
Serving an external system is outside the scope of 3GPP.
This requirement is covered by existing 3GPP Location Services and MCCore requirements.
[R-5.9a-031]
[R-9.4.4-002]
The FRMCS System shall be able to provide the list of identities and their location to the requesting FRMCS User, application or External System either periodically or as a onetime report.
A
Covered by TS 22.280.
Serving an external system is outside the scope of 3GPP.
This requirement is covered by existing 3GPP Location Services and MCCore requirements.
[R-5.9a-031]
[R-9.4.4-003]
The FRMCS System shall allow only the requesting FRMCS User, application or External System to stop the periodic reporting.
A
Covered by TS 22.280.
Serving an external system is outside the scope of 3GPP.
This requirement is covered by existing 3GPP Location Services and MCCore requirements.
[R-5.9a-031] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5 FRMCS User communication handling related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.1 Introduction | In this chapter the use cases related to the function of inviting a FRMCS User to a communication are defined.
- Invite-a-FRMCS User to a FRMCS communication
- FRMCS User receiving an invitation to a FRMCS communication
- FRMCS User accepting an invitation to a FRMCS communication
- FRMCS User rejecting an invitation to a FRMCS communication
- FRMCS User ignoring an invitation to a FRMCS communication
- Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2 Use Case: Inviting-FRMCS User(s) to a voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2.1 Description | An authorized FRMCS User can invite other(s) FRMCS User(s) to join an ongoing voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2.2 Pre-conditions | The inviting FRMCS User is part of an already established FRMCS voice communication of two or more FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2.3 Service flows | Inviting user
From a list of FRMCS Users provided by the FRMCS System or by entering an unlisted identity, the inviting FRMCS User selects another FRMCS User, or a pre-defined group of users, to be invited. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2.4 Post-conditions | The FRMCS User (s) have been invited.
The inviting FRMCS User remains connected to the FRMCS voice communication involving two or more FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.5.2-001]
If authorized to, a FRMCS User shall be able to invite other(s) FRMCS User(s) to join an ongoing voice communication.
A
22.280
Partially covered by 6.4.6.2 Negotiated change" provides the basic functionality (limited to ongoing group communications).
[R-9.5.2-002]
The FRMCS System shall provide a list of identities for the inviting FRMCS User to select from.
A
N/A
Implementation option: 22.280 6.4.6.2 Negotiated change does not make any assumption on the way and means an authorised user gets the identities to be included - i.e. this happens on application layer
[R-9.5.2-003]
The invitation request shall either be based on the functional identity, FRMCS User Identity, FRMCS Equipment Identity.
A
N/A
Implementation option: Keep it on application layer as otherwise, considering the sheer number of users, we would have to give an indication on how to filter that list. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3 Use Case: FRMCS User receiving an invitation to a voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3.1 Description | A FRMCS User will receive the invitation originated by the inviting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3.2 Pre-conditions | The FRMCS User may or may not be involved in voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3.3 Service flows | The invitation is indicated to the FRMCS User by audible and visual notification. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3.4 Post-conditions | The FRMCS User has received the invitation.
Voice communication of the invited FRMCS User continues unaffected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.5.3-001]
If entitled to, a FRMCS User shall be able to receive invitations to voice communication(s), independent of being involved in communication.
A
22.280
Implicitly provided by the normal function of MCX Communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4 Use case: FRMCS User accepting an invitation to a voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4.1 Description | A FRMCS User can accept the invitation sent by the inviting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4.2 Pre-conditions | The FRMCS User has received an invitation to a voice communication which is not yet expired. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4.3 Service flows | Invited FRMCS User not involved in a voice communication
The FRMCS User accepts the invitation of the voice communication.
The FRMCS User joins the ongoing voice communication. If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication.
Other FRMCS Users involved in the voice communication receive a notification that the FRMCS User has joined the communication by which the joining FRMCS User is identified to the other FRMCS Users.
Invited FRMCS User is involved in a voice communication
The FRMCS User accepts the invitation of the voice communication.
The FRMCS System prompts the invited FRMCS User about the treatment of the existing voice communication.
The FRMCS User may have the choice between some or all of these options:
• Terminate: The FRMCS User terminates the current voice communication.
• Leave the existing voice communication. If the communication consisted only of two participants, a participant leaving the communication will cause the communication to be terminated.
• Merge: The FRMCS System merges the two voice communications into one single voice communication.
The FRMCS User joins the ongoing voice communication. If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication.
Other FRMCS Users involved in the voice communication(s) are notified that the invited user has joined the communication or the communication has been merged. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4.4 Post-conditions | The invited FRMCS User is participating in the voice communication he was invited to.
The invited FRMCS User is indicated as connected to the voice communication to all FRMCS Users in the communication.
The presence status of the invited user is updated with the appropriate attributes. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.5.4-001]
The FRMCS User shall be able to accept an invitation to join a voice communication.
A
22.280
R-6.4.6.2-005
[R-9.5.4-002]
When accepting a communication invitation, in case the FRMCS User has a voice communication, the FRMCS User shall be able to leave, terminate or merge the voice communication. If the FRMCS User decides to merge the communications both voice communications shall be merged.
A
22.280
5.4.1, 5.4.2, 5.1.5
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior of leave and terminate
Merging can be done by 22.280 6.6.1 Group regrouping"
[R-9.5.4-003]
When accepting a communication invitation (i.e. the FRMCS User joins the ongoing voice communication), If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication.
A
Not covered
TS 22.280 6.4.6.2 Negotiated change is limited to group communications.
[R-9.5.4-004]
When accepting a communication invitation, other FRMCS Users involved in the voice communication(s) are notified that the invited user has joined the communication, or the communication has been merged.
A
22.280
Covered by the affiliation mechanism. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5 Use case: FRMCS User rejecting an invitation to a voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5.1 Description | A FRMCS User can reject the invitation sent by the inviting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5.2 Pre-conditions | The FRMCS User has received an invitation to a voice communication which is not expired yet. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5.3 Service flows | The FRMCS User rejects the invitation.
The inviting FRMCS User receives a notification that the invitation was rejected by the invited FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5.4 Post-conditions | The invited FRMCS User is not participating in the voice communication related to the received invitation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.5.5-001]
The FRMCS User shall be able to reject the invitation to join a voice communication.
A
22.280
R-6.4.6.2-005
[R-9.5.5-002]
The inviting FRMCS User sending the invitation shall be informed.
The inviting FRMCS User shall be notified.
A
22.280
R-6.4.6.2-005 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6 Use case: FRMCS User ignoring an invitation to a voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6.1 Description | A FRMCS User can ignore the invitation sent by the inviting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6.2 Pre-conditions | The FRMCS User has received an invitation which is not yet expired. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6.3 Service flows | The invited FRMCS User does not respond to the received invitation within a certain period of time
The inviting FRMCS User receives a notification that the invitation was rejected as it was not accepted within a certain period of time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6.4 Post-conditions | The invited FRMCS User does not participate in the voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.5.6-002]
If the receiving FRMCS User has not reacted on the invitation within a certain period of time [t1] the FRMCS System shall notify the inviting FRMCS User accordingly and stop the invitation request.
A
N/A
This is left to the app layer design to decide what happens if a MCX User does not react in due time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.7 Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.7.1 Description | For migration purposes, the service interworking between the GSM-R system and FRMCS system for inviting a user needs to be defined.
The following interworking use cases are needed for alerting a controller functionality: the case that there is a group call in GSM-R and a user would like to invite a controller who is in FRMCS:
Figure 9.5.7.1-1. Inviting-a-user from GSM-R to FRMCS
The case that there is a group communication in FRMCS, and a user would like to invite a controller who is in GSM-R also applies:
Figure 9.5.7.1-2. Inviting-a-user from FRMCS to GSM-R
The above use cases only apply if the controller system is connected to only one system. If the controller system is connected to both FRMCS and GSM-R systems, there is no need.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
9.5.7.2 Pre-condition
Group call in GSM-R and controller in FRMCS
A voice group call has been established in GSM-R System.
The controller in charge of the area is attached to FRMCS System only. This controller is not part of the voice group call.
Group call in FRMCS and controller in GSM-R
A voice group call has been established in FRMCS System.
The controller in charge of the area is attached to GSM-R System only. This controller is not part of the voice group call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.7.3 Service flow | Group call in GSM-R and controller in FRMCS
When there is an ongoing voice group call in GSM-R system and when a GSM-R User part of this group call is initiating an alerting-a-controller to invite a controller to join this group call, the request to join this group call shall be routed to the relevant Controller(s) attached to FRMCS System.
Group call in FRMCS and controller in GSM-R
When there is an ongoing voice group call in FRMCS system and when a FRMCS User part of this group call is initiating an Inviting-FRMCS User(s) to a voice communication to invite a controller to join this group call, the request to join this group call shall be routed to the relevant Controller(s) attached to GSM-R System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.7.4 Post-condition | Group call in GSM-R and controller in FRMCS
The relevant Controller(s) attached to FRMCS System are invited to join the ongoing voice group call in GSM-R system.
Group call in FRMCS and controller in GSM-R
The relevant Controller(s) attached to GSM-R System are invited to join the ongoing voice group call in FRMCS system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.5.7.5 Potential requirements | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[9.5.7-001]
The FRMCS System shall provide service interworking between the alerting a controller functionality in the GSM-R system and in the FRMCS System.
A
22.280
Covered by [R-6.17.3.1-002] to [R-6.17.3.1-005]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.