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.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 ... |
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 identit... |
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],... |
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 Locati... |
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 infor... |
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 reque... |
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 c... |
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 locat... |
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 covere... |
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... |
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... |
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 t... |
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 o... |
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 co... |
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 FRM... |
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 ... |
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 t... |
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... |
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) att... |
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 syst... |
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
• Servi... |
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... |
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 se... |
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 applicat... |
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... |
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 communi... |
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,... |
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-... |
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 commun... |
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 requeste... |
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 ... |
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.
T... |
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 f... |
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 do... |
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 sh... |
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.
T... |
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 ... |
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 ind... |
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]
[... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.