hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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]. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.6 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7 Multiuser talker control related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.1 General Description and potential requirements | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.1.1 General Description | In this chapter the use cases related to multiuser talker control for voice communication are defined. The following use cases are defined:
• Set the number of simultaneous talkers
• Set initial talker permissions and priorities
• Request permission to talk
• Grant permission to talk
• Revoke permission to talk
• Service interworking and service continuation with GSM-R
Note: For examples of Role management, like functional identities, FRMCS Equipment Identities, etc. in the railway environment, see annex A.
Multiuser Talker Control service is available in both on-network and off-network
operations.
The Multiuser Talker Control service is available in both user-to-user voice communication9and in multi-user voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.1.2 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.1-001]
Multiuser talker control shall be available for both on-net and off-net communication.
A
22.179
Covered for On-net only
[R-9.7.1-002]
Multiuser Talker Control service shall be available in multi-user voice communication
A
22.179
6.2.3.7.2
[R-9.7.1-003]
Multiuser Talker Control service shall be available in user-to-user voice communication
A
22.179
6.7.4 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2 Use case: Set the number of simultaneous talkers | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2.1 Description | For multiuser communication, i.e. when several users are involved in the same communication, the number of FRMCS FRMCS Users that are granted the right to talk at the same time can be limited to either one, a limited number or unrestricted number.
The communication application (e.g. shunting team communication) will set the number of simultaneous talkers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2.2 Pre-conditions | An active communication application capable to use the Multiuser Talker Control service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2.3 Service flows | The communication application sends the number of simultaneous talker(s) information to the Multiuser Talker Control service.
This information is used by Multiuser T
alker Control service when setting up the communication.
If there is a need to change the number of simultaneous talkers, it is the communication application which sends this information to the Multiuser Talker Control service.
If the number of simultaneous talkers is reduced and the reduction results in having more active talkers than permitted, refer to the use case “Grant permission to talk” (9.7.5).
The Multiuser Talker Control service then uses this updated information for controlling the number of simultaneous talkers in the communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2.4 Post-conditions | The Multiuser Talker Control service is aware about the number of simultaneous FRMCS Users and uses this information during communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.2-001]
The FRMCS System shall be able to limit the number of simultaneous talkers in a multiuser communication.
A
22.179
R-6.2.3.7.2-005
[R-9.7.2-002]
The maximum number of simultaneous talkers in a multiuser communication shall be provided by the communication application. The number of simultaneous talkers can be either one, a limited number or an unrestricted number and shall be changeable during the communication.
A
22.179
R-6.2.3.7.2-006 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3 Use case: Set initial talker permissions and priorities | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3.1 Description | There are different requirements for talker permissions and to prioritise talkers in different communication applications.
The FRMCS Users are identified by their functional identities.
The communication application defines the talker permissions and priorities based on the functional identities and the type of communication application, e.g., railway emergency call, shunting, multi train.
One or multiple FRMCS Users can be granted with the permission to perform as talker in a certain communication. These FRMCS Users are able to request permission to talk during communication.
Certain FRMCS User (s) that have requested the permission to talk at the same time or while another user is talking can be granted with an initial talker permission i.e., they will be given the permission first before requests of others are served independent of whether they were the first requesting the permission to talk or not. This initial talker permission granted for certain FRMCS User(s) is limited in time by system configuration.
Different FRMCS Users can be granted with a different talker priority. In case of parallel requests for permission to talk, the permission is granted to the FRMCS User (s) with highest talker priority. The requests with identical talker priorities will be queued based on the time of request. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3.2 Pre-conditions | An active communication application capable to use the multiuser talker control. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3.3 Service flows | The communication application sends information about talker permissions and talker priorities to the multiuser talker control application.
This information is used in multiuser talker control when setting up the communication.
If there is a need to change the information about talker permissions and talker priorities, it is the communication application that sends this information to multiuser talker control.
The multiuser control then uses this updated information for controlling the talker permissions and talker priorities in the communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3.4 Post-conditions | The multiuser control is aware of the talker permissions and talker priorities and uses this information for communication control/setup. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.3-001]
The FRMCS System shall be able to handle talker permissions and priorities as provided by the communication application, e.g., railway emergency call, shunting, multi train
A
22.179
R-6.2.3.7.4.1-002
R-6.2.3.7.4.1-004
[R-9.7.3-002]
The FRMCS System shall allow to grant several FRMCS Users with the permission to perform as talker in a certain communication.
A
22.179
R-6.2.3.7.4.1-002
R-6.2.3.7.4.1-003
[R-9.7.3-003]
FRMCS Users shall be able to request permission to talk during communication.
A
22.179
R-6.2.3.7.3-004
[R-9.7.3-004]
The FRMCS System shall be able to grant FRMCS Users an initial talker permission (i.e., be the first speaker in the communication) ensuring that the entitled FRMCS User (s) are able to talk first, once the communication is established.
A
22.179
R-6.2.3.7.4.1-003
[R-9.7.3-004a]
This initial talker permission granted for certain FRMCS User(s) is limited in time by system configuration.
A
22.179
Partly covered by floor priority, override mechanism and dynamic change of maximum number of simultaneous talkers (section 6.2.3.7).
How to identify that certain user(s) can be granted (e.g., train driver initiating the call) is not in the scope of 3GPP.
No timer in current specification to limit time for initial talker permission.
[R-9.7.3-005]
The FRMCS System shall be able to grant the permission to talk based on a FRMCS User talker priority. In case of pending requests for permission to talk, the permission shall be granted to the FRMCS User with highest talker priority. Requests of identical talker priority shall be handled based on the time of request.
A
22.179
R-6.2.3.7.4.1-004
R-6.2.3.7.3-004b |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4 Use case: Request permission to talk | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4.1 Description | There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
• Emergency communication
• Shunting communication
• Trackside worker communication
The system shall therefore be able to limit the number of simultaneous talkers in a voice communication.
An entitled FRMCS User shall be able to select and de-select FRMCS User (s) being able to talk in a voice communication.
The FRMCS User shall be able to request the permission to talk (raise the hand). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4.2 Pre-conditions | The FRMCS User is involved in an active voice communication. The number of simultaneous talkers is limited in this communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4.3 Service flows | The FRMCS User requests permission to talk on the MMI of the communication application (e.g. by pressing a Push-to-talk button)
The communication application sends the request to the multiuser talker control in the FRMCS System.
The communication application indicates on the MMI that talker permission has been requested. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4.4 Post-conditions | Permission to talk has been requested and a response from the multiuser talker control in the FRMCS System expected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.4-001]
An entitled FRMCS User shall be able to select and de-select FRMCS User (s) being able to talk in a voice communication.
A
22.179
[R-6.2.3.7.2-002]
[R-9.7.4-002]
The FRMCS User shall be able to request permission to talk of the FRMCS UE (e.g. by pressing a Push-to-talk button). The FRMCS UE shall indicate the talker permission has been requested.
A
22.179
[R-6.2.3.7.3-001] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5 Use case: Grant permission to talk | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5.1 Description | There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
• Emergency communication
• Shunting communication
• Trackside worker communication
The system shall be able to limit the number of simultaneous talkers in a voice communication.
The list of FRMCS Users with permission to talk and those who have requested it, shall be available to the Multiuser Talker Control service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5.2 Pre-conditions | The FRMCS User is an active voice communication.
The Multiuser Talker Control service is configured by the communication application to limit the number of simultaneous talkers.
The Multiuser Talker Control service uses priorities to manage the requests automatically
In addition, an entitled FRMCS User (i.e. based on functional identity) who is monitoring the progress of the communication can select and de-select simultaneous talkers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5.3 Service flows | Automatic management of requests
The Multiuser Talker Control service in the FRMCS System receives a request to talk from a FRMCS User.
The Multiuser Talker Control service in the FRMCS System verifies the number of FRMCS Users who already have permission to talk.
If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control service grants automatically the permission to the requester.
If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers, the Multiuser Talker Control service decides based on priorities who will keep the permission to talk and who will lose the permission to talk. The Multiuser Talker Control service configures the system accordingly.
If the number of simultaneous talkers is reduced and the reduction results in having more active talkers than permitted, the active talkers immediately lose their permission to talk according to their priority level starting with the lowest, and those remaining having the same priority level will lose their permission to talk as soon as they stop talking (i.e. voice detection, release PTT) until the new maximum allowed number of talkers is met.
The initial talker is granted the permission to talk for a configurable time (like 5 seconds).
The Multiuser Talker Control service sends an indication to the FRMCS Users whose permission to talk has been changed due to that.
Management of requests by an entitled FRMCS User
The Multiuser Talker Control service in the FRMCS System receives a request to talk from a FRMCS User.
The Multiuser Talker Control service in the FRMCS System verifies the number of FRMCS Users who already have permission to talk.
If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control service grants automatically the permission to the requester.
If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers, the Multiuser Talker Control service alerts the entitled FRMCS User that is monitoring the communication, who is presented with the list of simultaneous talkers and the list of pending requests and decides who will keep the right to speak and who will be granted the permission to talk by selecting and de-selecting the corresponding FRMCS User.
The Multiuser Talker Control service configures the system accordingly.
The Multiuser Talker Control service sends an indication to the FRMCS Users whose permission to talk has been changed due to that. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5.4 Post-conditions | Permission to talk is granted to the selected FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.5-001]
Multiuser Talker Control service shall keep track of FRMCS Users with permission to talk and FRMCS Users requesting to talk.
A
22.179
[R-6.2.3.7.3-004]
[R-6.2.3.7.4.1-002]
[R-9.7.5-002]
Multiuser Talker Control service shall use priorities to manage the requests automatically.
A
22.179
[R-6.2.3.7.4.1-003]
[R-9.7.5-003]
Based on its functional identity an entitled FRMCS User shall be able to select and de-select simultaneous talkers.
A
22.179
Partly covered by participant type [R-6.2.3.7.4.1-002]
[R-6.2.3.7.4.1-006] override mechanism by authorized participant.
[R-9.7.5-004]
If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control service shall grant automatically the permission to additional requestors.
A
22.179
[R-6.2.3.7.4.1-001]
[R-6.2.3.7.4.1-004]
[R-9.7.5-005]
If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers:
the Multiuser Talker Control service shall decide based on priorities who will keep the right to talk and who will be granted the permission to talk. Affected FRMCS Users shall be informed of their changed permission to talk.
A
22.179
[R-6.2.3.7.4.1-001]
[R-6.2.3.7.4.1-004]
[R-6.2.3.7.3-004b]
[R-6.2.3.7.3-005]
[R-9.7.5-006]
If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers:
the Multiuser Talker Control service shall be able to present to an entitled FRMCS User who is monitoring the communication, the list of simultaneous talkers and the list of pending requests to decide who will keep the right to speak and who will be granted the permission to talk. Affected FRMCS Users shall be informed of their changed permission to talk.
A
22.179
[R-6.2.3.7.4.1-005]
[R-6.2.3.7.4.1-006]
[R-6.2.3.7.3-004a]
[R-9.7.5-007]
If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers due to some talkers having the same priority level, the Multiuser Talker Control service shall be able to remove automatically the permission to talk to active talkers as soon as they stop talking (e.g. voice detection, release PTT) until the new maximum allowed number of talkers is met. Affected FRMCS Users shall be informed of their changed permission to talk.
A
22.179
6.2.3.7.4 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6 Use case: Revoke permission to talk | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6.1 Description | There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
• Emergency communication
• Shunting communication
• Trackside worker communication
The system shall be able to limit the number of simultaneous talkers in a voice communication.
The list of FRMCS Users with permission to talk shall be available to the Multiuser Talker Control service.
An entitled FRMCS User who monitors the progress of the communication shall be able at any point to revoke the permission to talk of any of the FRMCS Users with permission to talk. Automatic revocation of talkers in case the maximum number of simultaneous talkers has been reached and a request to talk is received, is included in the use case above. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6.2 Pre-conditions | A number of FRMCS Users are in an active voice communication for which Multiuser Talker Control is enabled and have been granted permission to talk.
An entitled FRMCS User is monitoring the progress of the communication and shall be able at any point to revoke the permission to talk of any of the FRMCS Users currently with permission to talk. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6.3 Service flows | The Multiuser Talker Control service presents a list of simultaneous talkers to an entitled FRMCS User, who decides who will not keep the right to speak by de-selecting the corresponding FRMCS User.
The Multiuser Talker Control service configures the system accordingly.
The Multiuser Talker Control service sends an indication to the FRMCS Users who have modified their situation with respects to the permission to talk.
The FRMCS User is no longer able to talk after the entitled FRMCS User has changed the permission. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6.4 Post-conditions | Permission to talk is revoked for the de-selected FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.7.6-001]
An entitled FRMCS User who monitors the progress of the communication shall be able at any point to revoke the permission to talk of any of the FRMCS Users currently with permission to talk.
A
22.179
[R-6.2.3.7.4.1-008]
[R-9.7.6-002]
The FRMCS User who’s permission to talk has been revoked, shall no longer be able to talk after the entitled FRMCS User has revoked the permission.
A
22.179
[R-6.2.3.7.4.1-004] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.7 Use case: Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.7.7.1 Description | No service interworking and service continuation with GSM-R is required.
The handling of the talker control is expected to be done independently in the GSM-R and FRMCS systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8 Authorisation of communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.1 Introduction | In this chapter the use cases related to authorisation of communication are described, the following use cases are identified:
• Permit / deny communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2 Use case: Permit / deny communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.1 Description | The purpose of the authorisation function it to allow the network operator to control and regulate communications in order to avoid disruption/distraction to the users (for example Drivers during voice communication) and preventing unauthorised communication and to minimise network load.
The FRMCS System may therefore restrict communication based on a configurable access matrix related to the FRMCS subscriber identity, the FRMCS Functional Identity of the equipment, the FRMCS User Identity, the FRMCS Functional Identity of the FRMCS Users considering the source and destination address.
Decision to permit or deny communication is based on full or subparts of the FRMCS Functional Identity of the FRMCS Users. An example of a full FRMCS Functional Identity of an FRMCS User is a specific driver on a specific train. An example of a subpart of an FRMCS Functional Identity of an FRMCS User is all train drivers. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.