hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.2 Pre-conditions | An FRMCS User attempts to establish a communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.3 Service flows | Upon an attempt to establish a communication, the FRMCS System checks if the source FRMCS User address is allowed to invite the destination FRMCS User address. The FRMCS System shall consider for the verification process the source and destination FRMCS User address.
If multiple identities are simultaneously active to a FRMCS User, the following order shall be applied to determine the authorisation of the communication establishment:
• Functional identities or subparts of functional identities related to the FRMCS User
• FRMCS User Identity
• FRMCS functional identities related to the equipment
• FRMCS subscriber identity
If the FRMCS User is allowed to establish the communication, the FRMCS System proceeds the communication setup.
If the FRMCS User is not allowed establish the communication, the FRMCS System shall reject the attempt including the reason of the rejection. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.4 Post-conditions | Either the communication has been established or the FRMCS User has been informed about the denial of the call attempt. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.8.2-001]
The FRMCS System shall be able to control and restrict the establishment of communication in order to avoid disruption/distraction of the FRMCS Users (for example Drivers).
A
TS 22.280
TS 22.280 sub-clause 6.7.3 Requirement [R-6.7.3-007a]
[R-9.8.2-002]
The FRMCS System shall be able to restrict communication based on related to the FRMCS subscriber identity, the FRMCS Equipment Identity, the FRMCS Functional Identity of the equipment, the FRMCS User Identity, the FRMCS Functional Identity or subparts of the FRMCS Functional Identity of the FRMCS Users considering the source and destination address.
A
TS 22.280
TS 22.280 Requirements [R-5.17-001] for group calls and
[R-6.7.2-002] for private calls.
Covered by [R-5.9a-020] and [R-5.9a-021] for functional identities.
[R-9.8.2-003]
The FRMCS System shall inform the FRMCS User in case the FRMCS User is not allowed to establish a communication.
A
TS 22.280
Implicit in many requirements. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9 Authorisation of application | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.1 Introduction | In this chapter the use cases related to authorisation of application are described, the following use case is identified
• Enabling/Disabling applications
• Robust mission critical group communication services
• Enabling/Disabling communication privileges per FRMCS User based on identities/talker status |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2 Use case: Enabling/Disabling applications | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.1 Description | The FRMCS System shall allow the network operators to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his Role.
The FRMCS System shall therefore be able to enable / disable FRMCS Applications for a FRMCS User depending on subscriber identity, the functional identity of the FRMCS Equipment, the FRMCS User Identity or the functional identity/ies of the FRMCS User. Also, context based criteria like location and other conditions are to be taken into account. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.2 Pre-conditions | The FRMCS User equipment is powered on and the FRMCS Application on the FRMCS User equipment has started. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.3 Service flows | Power-on
After powering on the FRMCS Equipment and start of the FRMCS Application on the FRMCS Equipment, the FRMCS System enables the FRMCS Application(s) on the FRMCS Equipment according to the Role related to the FRMCS subscriber identity.
Change of registration status
Upon a change in registration status by registration / deregistration to / from a functional identity, change of a functional identity, user login /logout to / from the FRMCS System, the FRMCS System enables / disables applications.
If multiple identities are active, the following order is used to determine the correct state:
• FRMCS functional identities related to the FRMCS User
• FRMCS User identity
• FRMCS functional Identities related to the FRMCS Equipment
• FRMCS subscriber identity
If a FRMCS User has registered to multiple functional identities, the FRMCS User is authorised to use all applicable FRMCS Applications related to the different FRMCS functional identities.
If an FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications is managed by the FRMCS System.
Only authorised FRMCS Applications shall be presented to the FRMCS User.
Change of location
If the FRMCS User enters a certain area, the FRMCS System may prevent the use of FRMCS Application(s) which had been authorised previously.
If the FRMCS User enters a certain area, the FRMCS System may enable the use of FRMCS Application(s) which had not been authorised previously.
If a FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications is managed by the FRMCS System.
Only authorised FRMCS Applications shall be presented to the FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.4 Post-conditions | The FRMCS User has access to all authorised FRMCS Applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.9.2-001]
The FRMCS System shall allow the network operator to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his Role.
A
TS 22.280, requirement
[R-6.6.4.2-002]
[R-6.7.3-007]
[R-6.7.3-007a]
Covered for both group and private communications with CR 0053 to TS 22.280
[R-9.9.2-002]
The FRMCS System shall be able to enable / disable FRMCS Applications for a FRMCS User depending on subscriber identity, the functional identity of the FRMCS Equipment, the FRMCS User Identity or the functional identity/ies of the FRMCS User. The FRMCS System shall also be able to take context-based criteria like location, speed, direction of travel and other conditions be taken into account.
A
TS 22.280, requirement
[R-6.6.4.2-002]
Covered for group communication with CR 0053 to TS 22.280
[R-9.9.2-003]
After powering on the FRMCS Equipment and start of the FRMCS Application on the FRMCS Equipment, the FRMCS System shall enable the FRMCS Application(s) on the FRMCS Equipment according to the Role related to the FRMCS subscriber identity.
A
Not applicable
This is related to implementation and is outside 3GPP scope.
[R-9.9.2-004]
Upon a change in registration status by registration / deregistration to / from a functional identity, a change of a functional identity, user login /logout to / from the FRMCS System, the FRMCS System shall be able to enable / disable applications.
A
[TS 22.280, requirement
[R-5.9a-001]
[R-9.9.2-005]
The FRMCS System shall allow the operator to configure the order in which the FRMCS functional Identities related to the FRMCS User
identity
FRMCS functional Identities related to the FRMCS Equipment
FRMCS subscriber identity
are evaluated to determine with the set of application authorised for use
A
Not covered
TS 22.280: only authorisation based on MCX Service User ID is supported.
[R-9.9.2-006]
If a FRMCS User has registered to multiple functional identities, the FRMCS User shall be authorised to use all applicable FRMCS Applications related to the different FRMCS functional identities.
A
Implicitly covered
This requirement is implicitly covered.
Chapter 5.9a.1 in TS 22.280 states that “The activation of the functional alias(es) will take place after the user has signed in to the MCX Service using the MCX User ID.”
So the user is already authorized to use the services when functional ID is activated.
[R-9.9.2-007]
If the FRMCS User enters a certain area, the FRMCS System shall prevent the use of FRMCS Application(s) which had been authorised previously.
A
Covered by [R-5.9a-015] in TS 22.280
[R-9.9.2-008]
If the FRMCS User enters a certain area, the FRMCS System shall enable the use of FRMCS Application(s) which had not been authorised previously.
A
Covered by [R-5.9a-015] in TS 22.280
[R-9.9.2-009]
If a FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications shall be managed by the FRMCS System.
A
Not applicable
This requirement should be covered in implementation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3 Use case: Robust mission critical group communication services | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.1 Description | For reliable railway services, conventional way is to use dualization methodology. Most of railway services are based on on-network communication, which is supported by base station and core networks under 3GPP standard. However, when disaster happens so that the communication infrastructure is not feasible, railway service based on the communication infrastructure cannot be maintained any more. From 3GPP Rel. 12, device-to-device communications has been considered to be supported not only in the transport layer but also in the application layer. In addition, interworking of FRMCS System with legacy systems including GSM-R and TRS is expected to be supported in Rel. 15. As a consequence, off-network and legacy systems will become feasible for group communication services in 3GPP technology. Therefore, by considering not only off-network but also legacy systems, reliability of mission critical group communication service in the on-network can be enhanced. Figure 9.9-1 depicts a required transformation of group communication service mode. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.2 Pre-conditions | FRMCS Equipment for train driver, customer service staff, and train operations staff support device to device communications in the perspective of transport layer.
FRMCS Equipment for train driver, customer service staff, and train operations staff support on-network, off-network group communication services in the perspective of applications layer.
Figure 9.9.3.2-1. Transformation of group communication service mode |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.3 Service Flows | 1. After initial disaster happens, emergency message (including voice or data) delivery service based on on-network group communication among train driver, customer service staff, or train operations staff have been preceded without any problem.
2. Disaster becomes worse, and associated communication infrastructure is destroyed and is not usable anymore.
3. Transformation of on-network group communication service into off-network or legacy network-based group communication service is accomplished among group members for maintaining the group communication services even in the worse disaster. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.1.4 Post-conditions | Off-network or legacy network-based group communication among train driver, customer service staff, or train operations staff is activated and group communication service is maintained normally. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.9.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.9.3-001]
FRMCS Equipment shall support on-network based group communications.
A/T
TS 22.179 V.14.2.0
Support
[R-9.9.3-002]
FRMCS Equipment shall support off-network based group communications.
A/T
TS 22.179 V.14.2.0
Support
[R-9.9.3-003]
FRMCS Equipment should support legacy network- based group communications optionally.
A/T
N/A
Implementation option.
[R-9.9.3-004]
FRMCS System shall provide a mechanism in the application layer to transform on-network based group communication into off-network based group communication.
A
TS 22.280
Automatic and manual switching from on-network service to off-network service are supported.
[R-7.13-004] On-going MCX service communication interruption are minimized when switching from on-network to -off-network services.
[R-9.9.3-005]
FRMCS System shall provide a mechanism in the application layer to transform on-network based group communication into legacy networkbased group communication.
A
22.179
22.280
TS 22.179
Project 25: subclause 6.18.3.2.
TETRA: subclause 6.18.3.3.
TIA-603 systems: subcla use 6.18.3.4.
GSM-R: 6.18.4.
TS 22.280
GSM-R: subclause 6.17.3.1.
9.9.3a Use case: Enabling/Disabling communication privileges per FRMCS User based on identities/talker status
9.9.3a.1 Description
In addition to enable the control of use of of FRMCS Applications, the FRMCS System shall allow the network operators and/or the FRMCS Users to control the use of FRMCS Applications with communication privileges per FRMCS User.
FRMCS User authorization shall be based on the FRMCS User Identity and/or the functional identity/ies of the FRMCS User, the functional identity of the FRMCS Equipment, and/or the talker status for ongoing communications.
Regarding this last parameter (i.e., communication privileges based on talker status), as an example, if an FRMCS User A who is involved as a listener in a voice communication, and FRMCS User B is talking in this voice communication, FRMCS User A is allowed or not to put on hold/leave/terminate the call, and/or to kick out FRMCS User B based on talker status of both FRMCS Users A and B.
9.9.3a.2 Pre-conditions
The FRMCS User equipment is powered on and the FRMCS Application on the FRMCS User equipment has started.
9.9.3a.3 Service flows
Change of FRMCS User authentication and authorisation status
Upon a change in FRMCS User authentication and authorisation status, the FRMCS System triggers a change of communication privileges (e.g., FRMCS User profiles) for that particular FRMCS User.
The following use cases are concerned:
• An FRMCS User is authorised or not to initiate a private or group voice, video or data communication;
• An FRMCS User is authorised or not to put a group voice communication on hold;
• An FRMCS User is authorised or not to leave a group voice communication;
• An FRMCS User is authorised or not to terminate a private or group voice communication;
• An FRMCS User is authorised or not to merge Railway Emergency Alerts;
• An FRMCS User is authorised or not to kick out another FRMCS User from a group voice communication;
• An FRMCS User is authorised or not to invite another FRMCS User to a group voice communication.
Change of FRMCS User registration status
Upon a change in registration status by registration / deregistration to / from a functional identity, the FRMCS System triggers a change of communication privileges (e.g., FRMCS User profiles) for that particular FRMCS User.
The following use cases are concerned:
• An FRMCS User is authorised or not to initiate a private or group voice, video or data communication;
• An FRMCS User is authorised or not to put a group voice communication on hold;
• An FRMCS User is authorised or not to leave a group voice communication;
• An FRMCS User is authorised or not to terminate a private or group voice communication;
• An FRMCS User is authorised or not to merge Railway Emergency Alerts;
• An FRMCS User is authorised or not to kick out another FRMCS User from a group voice communication;
• An FRMCS User is authorised or not to invite another FRMCS User to a group voice communication.
Change of FRMCS User’s talker status during ongoing group voice communication
Upon a change of talker status when an FRMCS User is involved in an ongoing group voice communication (i.e., the current talker becomes listener and vice-versa), the FRMCS System may be able to trigger a change of communication privileges (e.g., FRMCS User profiles) for all FRMCS Users affiliated to that group.
The following use cases are concerned:
• An FRMCS User is authorised or not to put an ongoing group voice communication on hold;
• An FRMCS User is authorised or not to leave an ongoing group voice communication;
• An FRMCS User is authorised or not to terminate an ongoing group voice communication;
• An FRMCS User is authorised or not to merge Railway Emergency Alerts;
• An FRMCS User is authorised or not to kick out another FRMCS User from an ongoing group voice communication;
• An FRMCS User is authorised or not to invite another FRMCS User to an ongoing group voice communication.
9.9.3a.4 Post-conditions
The FRMCS User is authorized or not to use FRMCS Applications.
9.9.3a.5 Potential requirements and gap analysis
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.9.2-001]
When an FRMCS User performs MCX authentication and authorisation, the FRMCS System shall be able to trigger a change of communication privileges for that particular FRMCS User.
A
Partly covered (refer to communication privileges below)
Identification of the targeted user of the communication privilege status change: partly covered by MCX authentication and authorisation mechanism (MC ID only, no FA).
Change of user profiles on MCX authentication and authorisation: covered MCX User Service Authorization is the function that validates whether or not a MCX user has the authority to access certain MCX services.
[R-9.9.2-002]
When an FRMCS User activates or deactivates Functional Alias(es), the FRMCS System shall be able to trigger a change of communication privileges for that particular FRMCS User.
A
Partly covered (refer to communication privileges below)
Identification of the targeted user of the communication privilege status change: covered by FA mechanism (MC ID + list of FA(s)).
Change of user profiles on FA activation or creation of new profiles for FA: not covered.
Editor’s note: CR is needed
[R-9.9.2-003]
When the floor is granted or released for a particular FRMCS User (including multi-talker floor control), the FRMCS System shall be able to trigger a change of communication privileges for all FRMCS Users affiliated to that group.
A
Partly covered
Identification of the targeted users of the communication privilege status change: Partly covered. Only MCPTT ID(s) and list of FA(s) of the requester(s) (floor control request & multi-talker) are known by the system.
Editor’s note: CR is needed
Change of user profiles when floor granted/released: not covered.
Editor’s note: CR is needed
[R-9.9.2-004]
The FRMCS System shall support Communication privilege as (1) authorisation to put a group voice communication on hold.
A
Covered
Put a group voice communication on hold: covered by the affiliation mechanism which is considered sufficient to mimic the desired behaviour.
Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status:not covered.
Editor’s note: CR is needed
[R-9.9.2-005]
The FRMCS System shall support Communication privilege as (2) authorisation to leave a group voice communication.
A
Covered
Leave a group voice communication: covered by the affiliation mechanism which is considered sufficient to mimic the desired behaviour.
Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status:not covered.
Editor’s note: CR is needed
[R-9.9.2-006]
The FRMCS System shall support Communication privilege as (3) authorisation to terminate a group voice communication.
A
Not covered
Terminate a group voice communication: strictly performed by the system.
Authorisation mechanism: not covered.
Editor’s note: CR is needed
[R-9.9.2-007]
The FRMCS System shall support Communication privilege as (4) authorisation to merge Railway Emergency Alerts.
A
[Need analysis]
[Need analysis – finalize potential requirements for Merging of Railway Emergency Alerts first]
[R-9.9.2-008]
The FRMCS System shall support Communication privilege as (5) authorisation to kick out another FRMCS User from a group voice communication.
A
Covered by 22.280
Kick out another user: covered by remote change of affiliation (mandatory mode) 22.280 6.4.6.1.
Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status:not covered.
Editor’s note: CR is needed
[R-9.9.2-009]
The FRMCS System shall support Communication privilege as (6) authorisation to invite another FRMCS User to a group voice communication.
A
Covered by 22.280
Invite a user to join: covered by remote change of affiliation (negotiated mode) 22.280 6.4.6.2.
Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status: not covered.
Editor’s note: CR is needed
[R-9.9.2-010]
The FRMCS System shall support Communication privilege as (7) authorisation to initiate private voice, video or data communication.
A
Covered by 22.280
Initiate private voice, video or data communication: covered by MC private call request mechanism.
Authorisation mechanism: covered by authorisation check based on user profile.
[R-9.9.2-011]
The FRMCS System shall support Communication privilege as (8) authorisation to initiate group voice, video or data communication.
A
Covered by 22.280
Initiate group voice, video or data communication: covered by group call request mechanism.
Authorisation mechanism: covered by authorisation check based on user profile. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10 Sharing FRMCS Equipment by FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.1 Description | Commonly, FRMCS Users may share FRMCS Equipment, e.g. a trainborne UE. To use the shared equipment securely, it is needed to identify the user for the equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.2 Pre-conditions | A train driver is in a train.
The train driver has an identification card. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.3 Service Flows | The train driver wants to use a trainborne UE to make communication to train control centre.
The train driver puts his/her identification card in the trainborne UE to identify himself/herself. In this case, the identification card is an example. It can be a type of ID number, finger-print, etc. instead.
The trainborne UE reads the identification information from the card and requests authentication to FRMCS security server.
FRMCS security server confirms the information and replies the authentication information to the trainborne UE.
FRMCS registers the train driver as the user of the trainborne UE to relay a call for the train driver to the trainborne UE.
The trainborne UE indicates readiness to use for the train driver. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.4 Post-conditions | The train driver makes a call to the train control centre.
The train driver receives a call using the trainborne UE that is relayed by FRMCS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.10.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.10-001]
The FRMCS System shall be able to provide a mean to identify a FRMCS User (for example, the train driver).
A
TS 22.280
TS 22.280 sub-clause 5.9a and covered by many requirements in MCX
[R-9.10-002]
The FRMCS System shall be able to provide a mapping between the FRMCS User identification information and FRMCS Equipment in order to route communication.
A
TS 22.280
Covered by many requirements in MCX
[R-9.10-003]
The FRMCS System shall be able to provide communication routing based on the mapping information.
A
TS 22.280
Covered by many requirements in MCX
[R-9.10-004]
The FRMCS System should provide functions for the shared FRMCS Equipment to get identification information from the FRMCS User who wants to use the equipment.
A
TS 22.280
Covered by many requirements in MCX |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11 FRMCS naming authority | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.1 Description | The FRMCS Naming Authority (NA) is a registry service provided by FRMCS System to facilitate the handling of various namespaces, number spaces or other information sets needed to support FRMCS services.
For example, FRMCS User identification requires a registry to manage the identification information which shall not be duplicated during its registration process.
The information may contain sensitive information such as personal information, e.g. finger-print image. Therefore, FRMCS NA should consider strong security mechanisms to store the information. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.2 Pre-conditions | A new train driver is registered as a new user of FRMCS.
A new trainborne UE is installed in a train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.3 Service Flows | The new train driver wants to use FRMCS System.
The train driver makes a request to register the user identification information in FRMCS with his/her finger-print as an identification method.
The FRMCS checks the duplication of the user identification under the guidance of FRMCS NA and registers the user identification information in its registry.
During the registration, the user identification information is handled by using a secure storage. FRMCS communicates with the secure storage to store the information.
The train driver installs a new trainborne UE in the train. During the installation process, the trainborne UE is registered as a new FRMCS UE in FRMCS registry under the guidance of FRMCS NA to avoid duplication of FRMCS UE address. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.4 Post-conditions | The train driver is registered as a new user in FRMCS System without duplication of user identification information.
The user identification information is stored in the secure storage safely.
The trainborne UE is installed in the train and is registered as a new FRMCS UE in FRMCS System without duplication of UE address. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.11.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.11-001]
The FRMCS System shall be able to avoid duplication of identities.
A
22.280
covered by 22.280
[R-6.9-002]
[R-9.11-002]
The FRMCS System shall be able to provide secure method to store the identification information.
A
Not covered
FFS |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12 Wayside-Centric Automatic Train Control | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.1 Description | Signalling block system, which is a fundamental factor in the perspective of train control, enables the safe and efficient operation of railways to avoid collisions between trains. The signalling block system basically keeps a train away from entering the block occupied by the other train. It is commonly known that moving block system compared to fixed block system. As shown in Figure 9.12-1, the train in moving block system can approach the leading train more closely.
Figure 9.12-1 Examples of various railways block systems
One way to realize the moving block system is that a centralized server communicates with trains and manages the moving block based on the positions of the trains. The On-board Automatic Train Protection (OATP), which is on the train, report the position of the train to the Wayside Automatic Train Protection (WATP), and the WATP decides and provide the movement authority of the train to the OATP. The train controls itself based on the movement authority, and trigger brake when it approaches the border of its authorized moving area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.2 Pre-conditions | 1. The user equipment dedicated to train control gets power-on, and registers to the train control system.
2. WATPs are located in the Packet Data Network (PDN), and each train knows the nearby WATP which can offer a movement authority and make it move.
3. The user equipment establishes a connection through the 3GPP network for transporting periodical data between WATP and OATP. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.3 Service flows | 1. The OATP periodically report its position to the serving WATP.
2. The WATP periodically provide movement authority to the OATP
3. The train accelerates, or triggers brake based on the last received movement authority. It moves till the position that it is authorized to move, and stops if it reaches to the border of the authorized area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.4 Post-conditions | The train triggers emergency brake and stops immediately if the connection is lost and data is not received for a certain time from WATP. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.12.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/
Transport
SA1 spec covering
Comments
[9.12-001]
The FRMCS System shall provide a mechanism for a train to autonomously discover an assigned application server which can offer movement authority.
A/T
22.280
This requirement is covered by the combination of functional alias, affiliation mechanism, and IP connectivity.
[9.12-002]
Train control data shall be able to be transported with the highest priority.
T
22.280
Covered by 22.280 [R-6.8.7.2-001], [R-6.8.7.2-010] and [R-5.1.7-002]. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13 Autonomous Train Control and Operation | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.1 Description | In legacy train control systems, trains typically decide its movement by interacting with trackside devices (e.g. track circuits, balise, radio block system) or communicating with a trackside server. If a train can autonomously figure out the positions of the nearby trains and decide its movement authority, the transport capacity of the railway will be enhanced. In the autonomous train control system whose service concept is aligned to the eV2X service, trains share its position by exchanging the information without any centralized server, and each train decides how far it can be authorized to move based on the position information. It is expected that main application area will be mass transportation such as subway.
Figure 9.13.-1 An example of autonomous train control scenario |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.2 Pre-conditions | 1. Trains know the overall schedule, and the user equipment of each train is connected to the user equipment of the other trains operating at the same time.
2. A user equipment of each train is able to establish a connection with the object Controller for the nearby point machine. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.3 Service Flows | 1. A train gets started and try registration to the currently operating trains. The registration message includes the position of the train.
2. The train gets the responses of the registration from the other trains and estimates the positions of the trains.
3. The train decides its movement authority based on the position information and starts moving.
4. The train positions in the corresponding areas are shared through multicasting.
5. Based on the periodically updated information, each train updates its movement authority and conduct train control based on it.
6. If needed, the train connects to the nearby point machine and sends switch command. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.4 Post-conditions | The autonomous train control is achieved by activating movement authority for each train or activating object Controller for nearby point machine. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.13.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/Transport
SA1 spec covering
Comments
[9.13-001]
The 3GPP network shall provide a mechanism using on-network communications to establish a bearer from a user equipment to the other user equipment
A
22.280
The requirement of [R-5.9a-002] “The MC User shall be reached by its functional alias(es) from within the MCX Service system where the functional alias was activated.” Includes point to point MCData transport service.
[9.13-002]
The 3GPP network shall provide an efficient way to disseminate data to multiple FRMCS UEs for train control.
A/T
22.282
22.280
The requirements of [R-6.2.2.1-002a] and
[R-6.2.2.1-002b] of 22.282 include a dissemination of data to multiple receiving users.
The efficient way of the dissemination is covered by functional alias in 5.9a requirements of 22.280.
[9.13-003]
The 3GPP network shall be able to multicast train control data originated from one FRMCS UE to the other FRMCS UE.
A/T
22.282
The requirements of [R-6.2.2.1-002a] and
[R-6.2.2.1-002b] include a multicast of data to chosen receiving users.
[9.13-004]
The FRMCS System shall provide a mechanism to discover feasible objects for point machine.
A
22.280
Covered by [R-5.9a-002] “The MCX User shall be reachable by its functional alias(es) from within the MCX Service system where the functional alias was activated.” |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14 Virtual Coupling | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.1 Description | One of the important missions that the future railway service should achieve is to increase its transport capacity. A straight-forward solution is to minimize the distance between successive trains so that train interval is reduced. It is difficult to do so in a legacy train control system, because the successive trains need to have distance as much as a safety margin, which should be larger than the full braking distance.
Figure 9.14-1 Sharing acceleration and braking control information to shorten safety margin
This safety margin can be further shortened if the successive trains share control information (acceleration and braking) and apply it to its own train control. As shown in Figure 9.14.1, the safety margin can be shortened if the following train immediately knows that the leading train starts braking and also triggers braking. This is the fundamental principle and the main purpose of virtual coupling. Figure 9.14.2 shows the basic concept of the virtual coupling scenario. Multiple trains which are in close distance move together as they are physically coupled. As the distance between two trains gets smaller, the control information of a train should be delivered to the other in shorter time.
Figure 9.14-2 The concept of virtual coupling scenario
9.14.2. Pre-conditions
1. The leading and following trains in operation recognize each other and have just got configured to be coupled virtually.
2. The user equipment for train control support device to device communications in the perspective of transport layer.
Figure 9.14-3 Overall procedure of virtual coupling |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.3 Service Flows | 1. The following train begins to approach to the leading train by exchanging the information about their position. The two trains, which are far enough to allow a certain amount of end-to-end latency, are initially connected through the 3GPP network.
2. As the following train approaches to the leading train, they start exchanging the information about movement control and each train then controls itself while considering the control of the other train. The two trains, which are still far enough to allow a certain amount of end-to-end latency, keep the connection through the 3GPP network.
3. As the following train further approaches to the leading train, the safe braking distance gets shorter and they are required to have a connection of which end-to-end latency is very short for delicate train control. At this moment, they seamlessly switch the connection from the 3GPP network to PC5 interface |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.4 Post-conditions | For safety train operation, integrity needs to be checked for train control information delivery in the perspective of application or transport layer. Any error on integrity check shall be immediately reported to the train control application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.14.5 Potential requirements and gap analysis | Requirement Reference Number
Requirement text
Application/Transport
SA1 spec covering
Comments
[9.14-001]
An On-board FRMCS UE for automatic train control shall be able to communicate through off-network up to 3km in the line of sight channel environment.
T
22.289
This requirement is covered by section 5.2.2 of TS22.289
[9.14-002]
Integrity protection shall be provided for each data transfer between FRMCS UEs for train control
A/T
22.280
Covered by [R-5.12-001]” The MCX Service shall provide a means to support the confidentiality and integrity of all user traffic and signalling at the application layer.”
[9.14-003]
The 3GPP system shall support service continuity between on-network based connection and off-network based connection.
A/T
22.280
[R-7.11-001] An MCX UE shall be capable of utilizing off-network MCX Service communications and on-network MCX Service communications at the same time.
[R-7.13-004] On-going MCX service communication interruption are minimized when switching from on-network to -off-network services.
[9.14-004]
FRMCS UEs for train control shall communicate through off-network, where the FRMCS UEs’ relative speed is less than 40km/h.
T
22.289
This requirement is covered by section 5.2.2 of TS22.289 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15 Composite-based train operation | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.1 Description | This use case considers the composition and decomposition of trains or tractions. One is the case, where two autonomous trains / traction (train A and train B) are conducted as one composition (Train C). The other case describes the decomposition of a train set (Train C) into autonomous train A and train B. For these scenarios, specific FRMCS Equipment Identity management need to be provided by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.2 Pre-conditions | Train A and Train B share information for train operation such as position and velocity profile. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.3 Service Flows | Train composition
1. Train/traction A and Train/traction B are autonomous trains and moving on different tracks.
2. Train/traction A and the train/traction B are put together into one train composition using the same railway.
3. Consequently, the different FRMCS UE identities of train/traction A and train/traction B are changed into common FRMCS UE identity composite train C/traction C.
Train decomposition
1. Train/traction C which is the composition of train/traction A and train/traction B is moving along the railway.
2. Based on the train routing i.e. different destination of train/traction A and train/traction B of train/traction A and train/traction B uses two different railways.
Consequently, the FRMCS UE identity of train/traction C is decomposed again into FRCMS UE identities of train/traction A and train/traction B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.4 Post-conditions | 1. Train/traction C arrives at the destination consisting of train/traction A&B
2. Train A and Train B arrive at the planned destination. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.15.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[9.15-001]
The FRMCS System shall be able to assign and withdraw an FRMCS Equipment Identity common to several FRMCS Equipment, e.g. for trains being coupled together in order to be reachable under the same FRMCS Equipment Identity.
A
22.280
Covered by [R-5.9a-015] The MCX Service system shall allow an MCX Service Administrator to make use of information (e.g. operational schedules, locations, velocity or direction) from external sources to create or delete a functional alias.and [R-5.9a-18] The MCX Service shall support automatic activation and de-activation of a functional alias based on the operational criteria (e.g. MCX User ID, login/logoff from the MCX Service system, specific external information supplied by external systems). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16 Arbitration related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.1 Introduction | In this chapter the use cases related to arbitration are defined. The following use cases are defined:
• Arbitration
• Arbitration for communication auto-connection |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2 Use case: Arbitration | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.1 Description | The FRMCS System shall be able to perform arbitration, based on the context of the communication. Arbitration in this context means that the FRMCS System is able to determine the behaviour of the end user device in case of multiple competing communications. Additionally, the FRMCS System may ask the FRMCS User which communication to accept. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.2 Pre-conditions | The FRMCS System is authorised to perform arbitration on communication on the end user device. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.3 Service flows | Incoming communication
When the communication is received by the FRMCS User on any of its registered functional identities, the FRMCS System provides to the FRMCS User arbitration information.
FRMCS System is able to present arbitration options to the FRMCS User to select from.
Arbitration of communication determines automatically to accept, reject, put on hold or queue the incoming and/or the ongoing communication, based on both the incoming and the ongoing communication characteristics.
Outgoing communication
The FRMCS User is initiating a new communication. Arbitration information is available from the FRMCS application.
The arbitration application has the possibility to present arbitration options to the end user to select from.
The arbitration application decides to accept, reject, and put on hold or queue, the ongoing and/or the new communication, based on both the incoming and the ongoing communication characteristics. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.