hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.1 Introduction | FRMCS Users have to indicate events that endanger public safety or emergency that requires the public safety involvement. For this reason, the FRMCS System is able to route the emergency call based on the current position of the initiating FRMCS User. The initiation of an emergency call has no dependency on the registration status of the FRMCS User.
Depending on the national rules, the operator of the FRMCS System may decide if the routing of the public emergency numbers is supported.
Following use cases related to public emergency call handling has been identified.
• Initiation of a public emergency call
• Termination of a public emergency call
• Call back the public emergency call initiator |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2 Use case: Initiation of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.1 Description | If enabled by the FRMCS System, an FRMCS User is able to report an emergency to an officer of the Public Safety Answering Point (PSAP) that will be responsible of bringing assistance or organizing response. The second scenario addresses the call back of a PSAP officer to the originator of the public emergency call which is a FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.2 Pre-conditions | The underlying transport of the FRMCS System supports emergency calls and the FRMCS System allows FRMCS Users to make use of emergency calls. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.3 Service flows | The FRMCS User or a public user initiates the public emergency call voice communication by dialling a public emergency call number.
The voice communication is recorded by the voice recording and access application.
The arbitration is managed by the arbitration application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.4 Post-conditions | The PSAP officer has received the public emergency call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.8.2-001]
The FRMCS System shall be able to allow or inhibit the processing of public emergency numbers.
A
TS 22.280
TS 22.280 sub-clause 6.16 Requirement [R-6.16-001]
[R-6.8.2-002]
In case public emergency call setup is allowed, the 3GPP defined handling of public emergency calls shall be applied.
A
TS 22.280
TS 22.280 sub-clause 6.16 Requirement [R-6.16-001] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3 Use case: Termination of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.1 Description | Both the initiating user, FRMCS User or a public user, and the PSAP officer shall be able to terminate the public emergency call voice communication.
The PSAP officer shall be able to put on hold the public emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.2 Pre-conditions | The public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.3 Service flows | PSAP officer on hold
A PSAP officer shall be able to put the public emergency call on hold.
After the PSAP officer has put the voice communication on hold, the communication remains in the FRMCS System, and the PSAP officer is able to be part of the communication again.
Termination
The FRMCS User or a public user, and/or the PSAP officer shall be able to terminate the public emergency call.
The FRMCS System terminates the voice communication. All involved users are informed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.4 Post-conditions | The public emergency call voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Note: Procedures for normal emergency call behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4 Use case: Call back the public emergency call initiator | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.1 Description | The PSAP officer shall be able to establish the communication towards the FRMCS user or a public user, who previously initiated the public emergency call (e.g. in the case the initial call was dropped). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.2 Pre-conditions | The public emergency call initiator is reachable via FRMCS System or a public network.
The FRMCS System is connected to the Public Safety Answering Point. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.3 Service flows | The PSAP officer initiates the voice communication by using the subscriber identity or the device identity of the previous calling user, FRMCS User or a public user, of a public emergency call. The QoS class of the communication is managed by the QoS class application. The voice communication requests the QoS class which matches the application category of CRITICAL VOICE (see [QoS]) within the FRMCS System.
The FRMCS System establishes the voice communication to the public emergency initiator within a setup time specified as IMMEDIATE (see [QoS]).
The arbitration is managed by the arbitration application.
The voice communication is recorded by the voice recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.4 Post-conditions | The call-back of the public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Normal emergency call service behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9 Data communication for possession management related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.1 Introduction | In this chapter the use cases related to possession management data communication are described, the following use cases are identified:
• Initiation of a possession management data communication
• Termination of a possession management data communication
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2 Use case: Initiation of a possession management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.1 Description | The application supports the processes involved in taking possession of an area of railway infrastructure for engineering purposes (for example for track maintenance). This application is intended to allow track side workers to remotely take control of infrastructure elements to perform safe engineering works on those elements. The application provides the communication bearer in a safe and secure way. The possession management application is able to initiate, release data communication for possession related data of a certain track section. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.2 Pre-conditions | The initiator (Controller(s), trackside maintenance personnel, ground system) is authorised to initiate the possession management data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.3 Service flows | The FRMCS Equipment initiates the possession management data communication towards the track possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.4 Post-conditions | The communication for possession management has been established.
Application messages can be exchanged between the possession management application and the possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.9.2-001]
The FRMCS System shall be able to support the transfer of messages to/from an authorised FRMCS Equipment identity, FRMCS User identity or functional identity with a QoS, priority and setup time as defined in clause 12.10 to/from an external system.
A
22.280
[R-5.9a-020] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority to which a Private Communication (without Floor control) can be made by an MCX User registered to this particular functional alias.
[R-5.9a-021] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority from which Private Communication (without Floor control) is allowed to an MCX User registered to this particular functional alias.
[R-5.9a-022] For private calls to functional aliases the authorizations in clause 5.9a.2 shall replace the authorizations defined in clause 6.7.3.
[R-5.9a-023] The MCX Service system shall be capable of handling private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users by using group call mechanisms and by using first-to-answer private call mechanisms.
[R-5.9a-024] The MCX Service system shall enable an MCX Service Administrator to select the mechanism to be used for handling of private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10 Recording of communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.1 Introduction | In this chapter the use cases related to recording and access are described, the following use cases are identified
• Recording |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2 Use case: Recording | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.1 Description | The FRMCS System is able to provide means to record communication and communication related information for voice, video and data services. The means of recording include FRMCS User identities, functional identities and location information of all involved users.
Which communication is applicable for recording is configurable. Criteria for recording can be based on different attributes or a combination of those e.g. communication application, functional identity, type of communication, location, certain context. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.2 Pre-conditions | A communication is configured to be recorded. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.3 Service flows | Recording of the communication starts when the particular communication becomes initiated.
The recording stops when the communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.4 Post-conditions | The recorded communication is stored and ready for post-analysis |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.10.2-001]
The FRMCS System shall provide the means to record communication and communication related information to an external system. That encompasses voice, video and data services.
A
22.280
On-Network: 6.15.4-001 - 010
Off-Network: covered by [R-7.14-001]: Only metadata are logged, no recording of transmissions of group/private communications as provided in on-network ([R-6.15.4-003]).
[R-6.10.2-002]
The FRMCS System shall be able to select the communication to be provided to the external system based on the following criteria:
• Communication application / use case
• FRMCS User identities
• functional identities
• location information of all involved users
A
22.280
On-Network: 6.15.4-001 - 010
Off-Network: not applicable. No selection mechanism are supported. All communication and non-communication activity metadata from an MCX UE are collected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11 Remote control of engines communication related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.1 Introduction | In this chapter the use cases related to remote control of engines communication are described, the following use cases are identified
• Initiation of a remote control of engines communication
• Termination of a remote control of engines communication |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2 Use case: Initiation/termination of a remote control of engines communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.1 Description | Remote control requires secure data communication between the FRMCS Equipment as part of on-board control system and the FRMCS User as part of a remote-control device, either via Off-network or On-network communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.2 Pre-conditions | The FRMCS User are authorised to initiate engine remote control communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.3 Service flows | The FRMCS User at the ground initiates the engine remote control communication to the FRMCS Equipment in the locomotive.
The communication requests the QoS which matches to the application category as defined by the operator within the FRMCS System.
The FRMCS User at the ground terminates the engine remote control communication to the FRMCS Equipment in the locomotive. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.4 Post-conditions | Remote control communication for the engine is established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.11.2-001]
Upon a request received from an authorised FRMCS User, the FRMCS System shall establish or terminate communication for remote control of engines communication.
A
Covered
22.280
Covered by
[R-5.21.1.2-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely initiate an MCX Service Private Communication or MCX Service Group Communication from another user’s MCX UE.
[R-5.21.2.1-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely terminate an MCX Service Private Communication or MCX Service Group Communication from another user’s MCX UE.
[R-6.11.2-002]
The FRMCS System shall support engine remote control communication in both On-network and off-network communication mode.
A
Covered by
22.280
As the whole section 5 is applicable for both on-network and off-network. i.e., “MCX Service requirements common for on the network and off the network”
So the requirements (” [R-5.21.1.2-001] and[R-5.21.2.0-001]) are naturally supported by on/off – network communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12 Automatic Train Operation data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.1 Introduction | In this chapter the use cases related Automatic Train Operation (ATO) communication are described, the following use cases are identified
• Initiation of an Automatic Train Operation data communication
• Termination of an Automatic Train Operation data communication
Note: A plain 3GPP bearer is requested below, as additional layers such as MCData are adding additional hurdles in achieving certification by railway regulatory authorities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.2 Description | Automatic Train Operation (ATO) is the application which performs some or all the functions of automatic speed regulation, accurate stopping, door opening and closing, performance level regulation, and other functions assigned to a train driver or train attendant.
Some ATO systems require radio communication to interchange performance and/or safety relevant data between a train and the corresponding trackside control center.
The (FRMCS) users in this case are the ATO application both on-board of the train and in the control center at the trackside (ground system).
ATO systems may require communication between on-board applications of different trains (on-network).
Some modes of ATO operation require real time video between a train and the corresponding trackside control center. Please refer to the Real Time Video streaming use cases. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3 Use case: Initiation of an Automatic Train Operation data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.1 Description | The FRMCS Application is able to initiate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.2 Pre-conditions | The initiating functional identity is authorised to initiate the automatic train operation data communication to the trackside control centre. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.3 Service flows | The initiating FRMCS Application (e.g. on-board of the train) initiates the Automatic Train Operation data communication to the receiving side (e.g. control centre at the trackside). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.4 Post-conditions | ATO communication is established.
Data can be exchanged between the Automatic Train Operation applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.12.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.12.3-001]
Upon request received from a functional identity entitled to set up ATO communication the FRMCS System shall be able to setup and terminate a data bearer for ATO operation of a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 5.5.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13 Monitoring and control of critical infrastructure related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.1 Introduction | In this chapter the use cases related to monitoring and control of critical infrastructure communication are described. The following use cases are identified
• Initiation of Monitoring and control of critical infrastructure communication
• Termination of a Monitoring and control of critical infrastructure |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2 Use case: Initiation of a Monitoring and control of critical infrastructure communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.1 Description | This use case enables FRMCS to setup data communication between infrastructure systems and a ground based or train based system in order to monitor or control critical infrastructure such as train detection, signals and indicators, movable infrastructure, level crossing elements, including barrier controls vehicle sensors, lighting controls and alarms. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.2 Pre-conditions | The initiating application is authorised to initiate Monitoring and control of critical infrastructure communication.
The receiving application is authorised to use the Monitoring and control of critical infrastructure communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.3 Service flows | The initiating application initiates the monitoring and control of critical infrastructure communication to the receiving side. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.4 Post-conditions | Monitoring and control of critical infrastructure data is made available to the application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.13.2-001]
Upon request from an authorised FRMCS Application the FRMCS System shall be able to establish data communication between a FRMCS Equipment and a central monitoring infrastructure system for monitoring and controlling critical infrastructures.
A
Covered by 22.282
[R-6.1.2.1.2-001] The MCData Service shall enable the control of robots.
1) A FRMCS Equipment can be seen as a certain kind of robots.
[R-6.1.3.2-001] The MCData Service shall provide a means to share in real-time operational status information between members of a selected group.
2) Sharing the operational status information can be seen as monitoring.
[R-6.13.2-002]
The FRMCS System shall setup the monitoring of critical infrastructure communication with an operator defined QoS and priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
Mission critical is already supported by 3GPP QoS (QCI or 5QI)
[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
See section 12.10 below. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3 Use case: Termination of a Monitoring and control of critical infrastructure communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.1 Description | Terminate data communication between infrastructure systems and a ground based or train-based system used to monitor or control critical infrastructure. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.2 Pre-conditions | The Monitoring and control of critical infrastructure applications have an ongoing data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.3 Service flows | One of the communication entities terminates the monitoring and control of critical infrastructure communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.4 Post-conditions | The terminating Monitoring and control of critical infrastructure application entity is disconnected from the receiving application entity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.13.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.13.3-001]
The FRMCS System shall be able to terminate data communication between the infrastructure systems and a central monitoring infrastructure system upon request by either communication partner.
A
Covered by 22.280, 22.282,
TS 22.280 [R-6.7.6-002] The MCX Service shall provide a means by which an MCX User ends a Private Communication (without Floor control) in which the MCX User is a Participant. TS 22.282
[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being sent and cancel streaming of data remaining buffered in the system waiting to be streamed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14 Use case: Data transmission in real time | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.1 Description | This use case allows the authorized FRMCS Users to exchange data in real time from each other, for example, health and status of train are transferred between intelligent on-train systems and train maintenance. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.2 Pre-conditions | The user A is authorized FRMCS User (e.g., administrator who has authorization to the data).
User B is an equipment for monitoring the train.
User C is a normal FRMCS User (e.g., user without authorization to the data) |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.3 Service flows | User A requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
User B receives the request from User A and accepts the request.
User B starts to transmit the requested data in real time to User A.
User C requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
User B receives the request from C and rejects the request (e.g., without authorization to the data).
User C receives a notification that the request was rejected by User B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.4 Post-conditions | The data of User B is sent to User A in real time.
The data of User B is not sent to User C in real time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.14.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.14.5-001]
The FRMCS System shall enable an authorized FRMCS User to request another FRMCS User to establish real time data transmission.
A
TS 22.282
Covered by 22.282 [R-5.5.2-003]: remote initiation of MCData Point-to-point IP connectivity between two MCData Users
[R-6.14.5-002]
The FRMCS System shall provide a list of identities for the requesting authorized FRMCS User to select from. The list may contain functional identities, FRMCS User identities, or FRMCS Equipment Identities
A
TS 22.280
Covered by functional alias requirements.
[R-6.14.5-003]
The real time data request shall either be based on the functional identity, FRMCS User Identity, or FRMCS Equipment Identity.
A
TS 22.280
[R-5.9a-002] If the MCX Service system supports functional aliases, the MCX User shall be reachable by its functional alias(es).
Functional Alias is specified by merging functional identity, user identity, and equipment identity.
[R-6.14.5-004]
The FRMCS User shall be able to accept a real time data transmission request.
A
TS 22.282
Only an authorised person can enable authorisation of IP connectivity to a specific destination.
[R-6.14.5-005]
The FRMCS User shall be able to reject a data in real time transmission request.
A
TS 22.282
Only an authorised person can revoke authorisation of IP connectivity to a specific destination.
[R-6.14.5-006]
The requesting FRMCS User shall be notified if the request is rejected or ignored.
A
TS 22.282
Implicit requirement. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15 On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | 6.15.1 Introduction
This use case is based on the International Union of Railways User Requirements Specification on FRMCS [15].
It is considered as a necessary scenario in China railway market that an authorised controller shall be able to set up a voice communication to a driver. As stated in URS 2.0, this application allows an authorised controller to establish voice communication with the driver of a specific train for operational purposes, for example to support the transfer of orders, to advise of delays, reporting of a disturbance, assault or staff security support.
The controller shall be able to call the drivers located in the area managed by the controller.
The controller can initiate the voice or video call to the drivers using the function alias.
The following use cases related to the function of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers are defined.
• Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
• Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2 Use case: Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | 6.15.2.1 Description
An authorised Controller shall be able to set up a voice or video communication to the drivers within a configured area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.2 Pre-conditions | The authorisation application authorises the Controller to call the drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.3 Service Flows | Controller(s) to Drivers
The Controller initiates the voice or video communication to the drivers. The priority of the communication is managed by the prioritisation application.
The FRMCS System determines the drivers, based on:
• Location information of the train provided by the locations services application, and/or
• Functional identity provided by the Role management and presence application.
• System configuration (To identify which Controller is responsible for which part of the track/station/etc.)
The FRMCS System establishes the voice or video communication to the drivers within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Drivers and Controller. Also, the location of the Drivers is presented to the Controller which is retrieved from the location services application.
If the controller is connected to more than one train, the multiuser talker control application is used.
The voice or video communication is recorded by the Voice or video recording and access application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.4 Post-conditions | The controller is connected to the requested drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.15.2-001]
For Controller to drivers voice or video communication, the FRMCS System shall be able to determine the responsible driver(s), based on the location of the train and/or the function alias and/or the System configuration on the Controller who is responsible for which part of the track/station/etc.
A
22.280
6.6.4.2 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3 Use case: Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.1 Description | Only the controller can terminate the On-train incoming voice or video communication from the Controller(s) of the train towards the drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.2 Pre-conditions | The controller is connected to the requested drivers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.3 Service Flows | Only the controller is able to terminate the voice or video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.4 Post-conditions | The controller terminates the voice or video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.15.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.15.3-001]
For Controller to Driver communication, only the controller shall be able to terminate the On-train incoming voice or video communication.
A
22.280
R-5.9a-012a
R-5.9a-012b |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16 Use cases on data communication for Train Operation System Communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.1 Introduction | In this chapter the use cases related to data communication for Train Operation System are described. The following use cases are identified:
• Train dispatch order data communication between driver and controller
• LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive
• Data communication for Security use cases between two approaching trains |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2 Use case: Train dispatch order data communication between controller and driver | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.1 Description | In this use case, the FRMCS system transmits the train dispatch order between Controller and Driver, including train orders, station receiving route, running tokens, etc.
It is needed that the information are received in due time by the driver to avoid any collision with any other train standing in another lines. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.2 Pre-conditions | User A and User B are authorized FRMCS User.
User A is a Driver entering in the train station.
User B is Controller of the train responsible for the train’s current area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.3 Service flows | User B initiates a data communication to User A in order to send station route within short time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.4 Post-conditions | User A receives the station line to follow when entering in the train station. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.2-001
The FRMCS system shall support data communication between Controller and Driver with a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3 Use case: LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.1 Description | The multi-headed locomotive has several engines, all the engines act synchronized as the LOCOTROL information will be sent between engines through FRMCS system.
It is quite important to ensure this LOCOTROL information is sent to the corresponding locomotives safely and in an integrated way so that synchronized actions can be taken. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.2 Pre-conditions | User A and User B are authorized FRMCS User.
User A is a leading locomotive.
User B is a subordinate locomotive. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.3 Service flows | User A initiates a data communication to send the LOCOTROL information to transport information regarding synchronization with the User B in safely and timely method, e.g., with a QoS and priority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.4 Post-conditions | User B receives the LOCOTROL information, so User B can be kept synchronized with User A. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
6.16.3-001
The FRMCS system shall provide a mean to exchange messages between different FRMCS Equipment with a QoS, priority and setup time as defined in clause 12.10.
A
TS 22.282 (data bearer)
N/A (QoS)
TS 22.282 sub-clause 6.1.2
See section 12.10 below |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4 Use case: data communication for security between two approaching trains | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.16.4.1 Description | This use case describes data communication between FRMCS Users in order to avoid train accident, for example, two trains exchange warning data to each other when one train is approaching to another train.
And it is also used for the case that different devices in different carriages send detection data to head device in the train, so that the Driver can take appropriate actions.
This data information needs to be transported in a safe and timely manner so that the train can operate in a safe way. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.