hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.2.3 Service flow | FRMCS System to GSM-R
FRMCS User A initiates a new area broadcast group communication (based on location etc., of GSM-R User B and C).
FRMCS User A broadcasts group communication invitations to all Users in the same area.
GSM-R User B and User C receive the group communication invitations.
GSM-R User B and User C accept the invitation and join the group communication. Or GSM-R User B and User C automatically join this group communication.
GSM-R to FRMCS
GSM-R User B initiates a new group call (based on location etc., of FRMCS User A and GSM-R User C).
GSM-R User B broadcasts group call invitations to all Users in the same area.
FRMCS User A and GSM-R User C receive the group call invitations.
FRMCS User A and GSM-R User C accept the invitation and join the group call. Or FRMCS User A and GSM-R User C automatically join this group call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.2.4 Post-condition | FRMCS User A, GSM-R User B and User C can communicate among each other in a group call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.2.5 Potential requirements | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[12.2-001]
FRMCS System shall provide a means to initiate group communication between FRMCS Users and GSM-R Users.
A
22.179
R-6.18.3.5-003
[12.2-002]
FRMCS System shall provide means to FRMCS Users to join the group calls of GSM-R
A
22.179
R-6.18.3.5-003 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.3 Location Service interworking between GSM-R and FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.3.1 Description | This use case allows FRMCS System and GSM-R system to obtain and share the location information of their users.
12.3.2 Pre-condition
User A is an authorized FRMCS User.
User B is an authorized GSM-R User.
User A and User B are affiliated to a group that consists of FRMCS User(s) and GSM-R User(s). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.3.3 Service flow | FRMCS System to GSM-R
FRMCS User A sends a location request to the specific GSM-R User B.
GSM-R User B accepts and return his location information as requested.
GSM-R to FRMCS System
GSM-R User B sends a location request to the specific FRMCS User A.
FRMCS User A accepts and returns his location information as requested. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.3.4 Post-condition | FRMCS User A’s location information is sent to GSM-R User B.
GSM-R User B’s location information is sent to FRMCS User A. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.3.5 Potential requirements | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[12.3-001]
FRMCS System shall provide a means to obtain and share with FRMCS User the location information of GSM-R User(s).
A
22.280
R-6.17.3.1-001
[12.3-002]
FRMCS System shall provide means to provide location information of FRMCS User to GSM-R.
A
22.280
R-6.17.3.1-001 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.4 Presence interworking between GSM-R and FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.4.1 Description | Service interworking of user’s presence between GSM-R and FRMCS Systems is not required.
12.4.2 Pre-condition
Void. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.4.3 Service flow | Void. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.4.4 Post-condition | Void. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.4.5 Potential requirements | Void. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.5 Point to Point communication between GSM-R and FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.5.1 Description | This use case allows a FRMCS User to communicate with a GSM-R User, vice versa.
12.5.2 Pre-condition
User A is an authorized FRMCS User.
User B is an authorized GSM-R Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.5.3 Service flow | FRMCS System to GSM-R
FRMCS User A initiates a point to point communication to GSM-R User B.
GSM-R User B accepts the communication and joins the communication.
GSM-R to FRMCS System
GSM-R User B initiates a point to point call to FRMCS User A.
FRMCS User A accepts the call and joins the call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.5.4 Post-condition | GSM-R User B and FRMCS User A are communicating with each other. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.5.5 Potential requirements | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[12.5-001]
FRMCS System shall provide a means for point to point communication between an authorized FRMCS User and a GSM-R User,
A
22.179
R-6.18.3.5-004
FRMCS System |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6 Interworking with legacy systems including LMR | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6.1 Description | This use case describes the way of interworking with legacy systems including LMR. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6.2 Pre-conditions | The train driver uses the trainborne UE.
Train crews have a LMR UE for each.
The operator at the train control centre has a 3GPP UE.
The train control centre is connected to the public safety centre via 3GPP network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6.3 Service flows | The train driver calls the train control centre to report an emergency of the train and wants to share the report with train crews in the train.
The FRMCS System initiates a 3GPP call to the operator at train control centre.
The FRMCS System initiates a LMR call to all of train crews.
The train driver reports the situation. The FRMCS System transmits the report to the train control centre via 3GPP network and to train crews in the train via LMR.
The train control centre received the report and forward the call via 3GPP network to report the situation to the public safety centre.
The train control centre activates the switching device on the railway track to pass other trains via the signal control network.
The train control centre orders the train crews to do a counter-action on the situation.
Train crews are shared with the report and order, and deal with the situation properly. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6.4 Post-conditions | The situation has been handled.
The train control centre has the information on the situation, the counter-action and its result.
The public safety centre gets the report on the situation in real-time. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[12.6-001]
The FRMCS System shall provide interworking related functionality between the 3GPP network and the legacy network of LMR, e.g. TETRA and P25.
A/T
22.179
The requirement is covered by 6.18.3 Interworking with non-3GPP PTT systems of 22.179
[12.6-002]
The FRMCS System should provide interworking with the signal control network.
A
22.280
This requirement is covered by the combination of functional alias, affiliation mechanism, and IP connectivity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7 Use case: Builds stable positioning framework for FRMCS services and devices including trainborne and handheld devices | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7.1 Description | This use case considers stable positioning framework for FRMCS services and devices are placed in indoor and/or outdoor. The use case focuses covering “GPS shadow area” with ad-hoc positioning technology such as LTE location service. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7.2 Pre-conditions | The trainborne UE has GNSS function.
The trainborne UE has 3GPP Communication Module.
The train control centre monitors the train traffics. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7.3 Service flows | The operator at the train control centre requests location information from a train.
The train is running through a very long tunnel, therefore the GNSS in the trainborne UE does not work.
The operator at the train control centre connects the location service in the 3GPP system as an alternative way and obtains the train’s location which is actually the location of the trainborne UE.
The operator at the train control centre determines the train path and controls railway tracks by signalling the track circuit device. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7.4 Post-conditions | The train control centre obtains the location of the train.
The track circuit for the train is reorganized. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.7.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[12.7-001]
The FRMCS System shall provide the alternative means than GNSS to obtain the position of the FRMCS Equipment.
A
TS 22.280
The interfacing method and format of the location information from the LTE system is covered by 3GPP specification such as UE positioning in E-UTRAN[5].
Covered by [R-5.11-002a] of TS 22.280 which is
“The MCX Service shall be able to provide a mechanism for obtaining high accuracy Location information by integrating position information from multiple external sources (e.g. magnetometers, orientation sensors, GNSS)”.
[12.7-002]
The positioning information shall provide an accuracy of [TBD] whilst the UE is travelling at a maximum of 500 km/h.
A/T
TS 22.261
TS 22.261 sub-clause 6.27.2
TS 22.261 sub-clause 7.3.2 – refer to positioning service level 3 (only one speed limit supported – up to 500 km/h – with horizontal accuracy of 1m)
See [R-12.14.2-001] of clause 12.14.2.5. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8 Interworking between GSM-R and FRMCS | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.1 Introduction | GSM-R is the widely used wireless communication system of the railways. It provides the bearer service for current critical and supportive railway applications. The deployment of FRMCS and the migration to FRMCS is expected to encompass a large timeframe estimated currently at 10 years. During this period, coexistence and interworking of both communication systems is required. Interworking between the FRMCS System and GSM-R system shall be provided.
Interworking on functional level e.g. numbering plan alignment is not part of this use case.
Note 1: Interworking is the functionality of two networks to talk to each other enabling services to be delivered across the two networks (source: GSMA Document IR.65 "IMS Roaming, Interconnection and Interworking Guidelines").
Note 2: 3GPP MCX specifications have different understandings of Interworking and Interconnection than GSMA and the Railways. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2 Circuit Switched interworking between GSM-R and FRMCS | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2.1 Description | Background:
Circuit switched bearer services are used in GSM-R for voice and data communication. That encompasses user-to-user as well as multiuser voice communication.
Description:
FRMCS and the GSM-R will coexist for a period estimated currently at 10 years that demands interworking for circuit switched bearer services to cover voice. It requires the necessary circuit switched transport adaptation, the necessary conversion of the signalling and the user data coding among the systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2.2 Pre-conditions | GSM-R user is attached to the GSM-R system.
FRMCS Users is attached to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2.3 Service flows | GSM-R user establishes a user-to-user voice communication to a FRMCS User.
GSM-R user establishes a multiuser communication including FRMCS Users.
FRMCS User establishes a user-to-user voice communication to a GSM-R user.
FRMCS User establishes a multiuser voice communication including GSM-R users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2.4 Post-conditions | User-to-user voice communication between GSM-R user and FRMCS User are established.
Multiuser voice communication between GSM-R user and FRMCS Users are established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.8.2-001]
FRMCS-system to GSM-R circuit switched signalling and bearer service interworking shall be supported for user-to-user and multiuser voice communication.
A/T
22.179
[R-6.18.4.2-003], [R-6.18.4.2-004]
[R-12.8.2-002]
FRMCS System shall support the current voice codecs used by GSM-R.
A/T
22.179
[R-6.18.4.2-005]
[R-12.8.2-003]
The FRMCS System shall be able to support interworking of GSM-R MLPP based call priorities to the priority mechanisms of the FRMCS System.
A
22.179
[R-6.18.4.2-003]
[R-12.8.2-004]
The FRMCS System shall be able to support interworking between the arbitration scheme used in GSM-R and the arbitration scheme used in the FRMCS System.
A
22.179
[R-6.18.4.2-003]] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3 Packet Switched interworking between GSM-R and FRMCS | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3.1 Description | Packet switched bearer services i.e. GPRS/EGPRS are used in GSM-R for data communication e.g. ATP. FRMCS and the GSM-R will coexist for a period estimated currently at 10 years that demands an interconnection for packet switched based communication. It requires the necessary packet switched transport adaptation to FRMCS, the conversion of the signalling and the user data coding among the systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3.2 Pre-conditions | GSM-R user is attached to the GSM-R system.
FRMCS Users are attached to the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3.3 Service flows | GSM-R user establishes a user-to-user packet switched communication to a FRMCS User.
FRMCS User establishes a user-to-user packet switched communication to a GSM-R user. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3.4 Post-conditions | Packet Switched communication among GSM-R user and FRMCS User are established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.8.3-001]
FRMCS-system to GSM-R packet switched interworking shall be supported.
A/T
N/A
According to latest decision from UIC (see FRMCS project activities status report in ERIG#70 (July 2018), the requirement is not required.
No use case has been identified by UIC ((E )GPRS EVC could not be connected to any FRMCS RBC). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4 SMS/SDS interworking between GSM-R and FRMCS | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4.1 Description | SMS has been widely used in GSM-R.
FRMCS and GSM-R will coexist for some period. So, interworking between the FRMCS System and Short Message Service in GSM-R is needed.
A possible scenario is that a GSM-R user sends a short message to a FRMCS User to transfer some information. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4.2 Pre-conditions | GSM-R user is attached to the GSM-R system.
FRMCS User is attached to the FRMCS system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4.3 Service Flows | A GSM-R user sends a short message to a FRMCS User to transfer some information. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4.4 Post-conditions | The FRMCS User can communicate with the GSM-R user. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.8.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.8.4-001]
The FRMCS System shall be able to interwork with the Short Message Service in GSM-R.
A
22.282
[R-7.2-001] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9 Use case: Bearer flexibility | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9.1 Description | FRMCS envisages bearer flexibility to allow a certain level of independence between Railway Applications and the underlying transport system. FRMCS includes wireless and wireline access. It comprises multiple access systems and shall support various voice and data applications.
The rationale behind these requirements is that the lifecycle of railway applications is in general much longer than the lifecycle of telecommunication access/transport systems. Moreover, bearer flexibility aims at improving service availability and performance.
The characteristics of bearer flexibility are:
1. A Railway Application may use one or several access systems as appropriate.
2. Connection of FRMCS Equipment to different access systems is dynamic (i.e. the most appropriate 3GPP or non-3GPP access technologies are selected automatically, potentially using multiple access technologies for one or more Railway Applications).
3. The set of access systems chosen meets the defined QoS and the service requirements e.g. FRMCS User mobility and connectivity which are necessary to guarantee the functionality.
4. The introduction of a new access system should not negatively impact existing Railway Applications.
The approach taken within FRMCS allows the integration of 3GPP and non-3GPP radio access evolution.
IP is used as a generic interface towards Railway Applications, facilitating connectivity, quality of service control, security and the separation of transport system and applications. NOTE: Non-3GPP access can consist of non-terrestrial e.g. Satellite as well as of terrestrial access systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9.2 Pre-conditions | The Railway Adaptation Sub-System as part of the FRMCS System is embedded between the Railway Applications and the Multi Access Core Network (MACN) and enables the access system independence towards those applications. This Sub-System adapts application characteristics to the access systems. It manages e.g. QoS, address conversion, functional roles and train location information.
The MACN has the ability to manage and interwork with wireless access systems (i.e. 3GPP and non-3GPP) as well as with wireline access systems. It encompasses for example the management of FRMCS User mobility, FRMCS User session/communication handling and control of end-to-end communication prioritisation. The MACN interworks with legacy communication systems and other FRMCS Systems.
The Access Control & Management function of the FRMCS Equipment is able to manage the different access systems as well as access via GSM-R (for roaming and simultaneous operation). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9.3 Service flows | Case 1 (data communication)
As an example the Automatic Train Protection (ATP) application of a train establishes a data communication session with the applicable ground communication entity which is connected via the fixed network service. For ATP message exchange, the on-board system can encompass a railway operated private 3GPP 4G access system and a public 3GPP 5G access system (e.g. a VPN service) as part of the FRMCS System. ATP periodically reports train position information and receives Control Command instructions from the ground communication entity. The FRMCS Equipment is registered to both access systems and uses these simultaneously if applicable.
Simultaneous use of radio access systems may improve communication resilience, availability, and QoS and increases bandwidth.
The concept as described here can generally be extended to other data communication applications and (non-)3GPP access systems.
Case 2 (railway emergency voice communication)
The on-board FRMCS Users are registered to the FRMCS System. An on-board FRMCS User establishes a Railway Emergency Communication (REC) from a specific location in the FRMCS network. This particular communication request takes into account the most appropriate radio access system, for example the railway-operated private 3GPP network. The FRMCS System notifies the applicable users determined by the location of the initiator of the communication by using all available access system(s) e.g. 3GPP (public and private), WLAN or wireline. The applicable Controller is notified via the wireline access system. The intended recipients of the call may be using different access systems.
The concept as described here can in general be extended to other voice group communication applications and point to point communication services.
Case 3 (telemetry operation at a railway depot)
A train is located in a railway depot where only WLAN coverage (non-3GPP access) as part of the FRMCS System is provided. FRMCS Users of this train are attached to the FRMCS System. An FRMCS User starts a data session towards the applicable vehicle diagnostic entity. At that point in time WLAN provides the radio access system for this telemetry communication. Once the train leaves the depot and enters into a 3GPP coverage area, the FRMCS Equipment adapts the transmission of the telemetry data session to the most QoS effective radio access system (3GPP access). The telemetry session continues uninterrupted when the train changes its location.
The concept as described here can in general be extended to other voice and data applications where other combinations of access systems at specific locations are possible.
Case 4 (Backup operation/resilience)
In a certain area with dedicated 3GPP access, coverage fails. Despite unavailability of the dedicated railway 3GPP access, FRMCS Users have the capability to continue communications by using public 3GPP access using an access system which may support the required or some degraded form of QoS and which is provided in the area and which serves as a backup or complementary system. Communication applications on trains continue to operate, service continuity is preserved. When the functionality of the dedicated 3GPP access system is restored, the FRMCS Equipment resumes operation on that system.
The concept as described here can generally be extended to any combination of access systems, e.g. WLAN and private 3GPP access.
Case 5 (Notification of radio bearer availability)
In general, there is only little radio spectrum resources allocated to railways in most regions. These should be preferably used for operational rail communication purposes. In parallel, there are communications that require broadband wireless communication services. The availability of broadband wireless access can be limited e.g. to railway stations. Thus, the FRMCS System is able to take into account radio bearer availability at the FRMCS User’s position allowing to start communication such as a file download/upload not harming operational rail communication.
Case 6 (Use of Satellite Communication)
In some regions, trains are circulating in rural areas, on low traffic lines. For such situation, deploying dedicated rail terrestrial radio access is not economically viable and public mobile operator’s service is very limited due to low population density rate. Satellite access is foreseen as an alternative to terrestrial radio access that reduces investment in access infrastructure. In this first approach, satellite access is considered as an enabler to extend communication service of rail lines with FRMCS.
Some rail applications require service continuity for railways operation. In some situation, rail traffic is stopped when communication services are not available. To overcome situations of temporary outage or total destruction of terrestrial access, use of non-terrestrial access systems by the FRMCS system could be envisaged to deliver a highly resilient transport service. In this second approach, satellite access is foreseen as a backup from terrestrial radio access.
It is envisaged that the FRMCS application could be configured with preconditions that trigger an alternate mode of operation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9.4 Post-conditions | Case 1 (data communication)
The train protected by ATP arrives on time without service interruptions of the communication.
Case 2 (railway emergency voice communication)
Railway emergency voice communication is established to all FRMCS Users in the designated area independent of the used access network.
Case 3 (telemetry operation at a railway depot)
Telemetry communication continued while relocating the train/vehicle.
Case 4 (Backup operation/resilience)
Communication continued when the private 3GPP access is unavailable in an area.
Case 5 (Notification of radio bearer availability)
none
Case 6 (Use of Satellite Communication)
Communication continued when the 3GPP terrestrial radio access coverage is physically not provided in an area.
Communication continued when the 3GPP terrestrial radio access is temporarily not available in an area. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.9.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.9-001]
The FRMCS System shall be able to manage 3GPP access systems and non-3GPP access systems (terrestrial and non-terrestrial) simultaneously.
A/T
TS 22.278
TS 22.261
TS 22.278 sub-clause 5.0
TS 22.261 sub-clause 6.3.2.1
[R-12.9-002]
If provided by the FRMCS Equipment, the FRMCS Application on the FRMCS Equipment shall be able to make use of 3GPP and non-3GPP access systems simultaneously.
A
TS 22.278
TS 22.261
TS 22.278 sub-clause 6.2
TS 22.261 sub-clause 6.3.2.1
[R-12.9-003]
The FRMCS User shall not experience service interruptions in the usage of applications due to a change of an access system.
A
TS 22.278
TS 22.261
TS 22.278 sub-clause 5.0
TS 22.261 sub-clause 6.2.3
broader functional spectrum
[R-12.9-004]
The FRMCS transport system including 3GPP and non-3GPP access shall be agnostic to Railway Applications.
T
TS 22.278
TS 22.261
TS 22.278 sub-clause 5.0
TS 22.261 sub-clause 6.2.1/6.2.3
broader functional spectrum
[R-12.9-005]
New access technology shall not require changes for the pre-existing application layer to be able to make use of this new access technology.
Note: Changes are required if the application layer wants to make use of the new capabilities of a new access technology.
A/T
TS 22.261
TS 22.278 only partially compliant because of missing satellite access support
[R-12.9-006]
The transport layer shall allow using IP as a generic interface.
T
TS 22.278
TS 22.261
TS 22.278 sub-clause 7.2
TS 22.261 sub-clause 5.1.2.3
[R-12.9-007]
For recording purposes, the FRMCS System shall be able to provide communication content as well as the associated communication related information.
A
TS 22.280
TS 22.278
TS 22.261
TS 22.280 sub-clause 6.15.4
TS 22.278 sub-clause 9.2
TS 22.261 sub-clause 8.6
[R-12.9-008]
The FRMCS System shall be able to make use of one or more of the followings:
3GPP radio access (i.e. 4G and/or 5G) through railway-dedicated licensed spectrum
3GPP radio access (i.e. 4G and/or 5G) provided by public providers
3GPP radio access (e.g. LTE-U) through unlicensed spectrum
Non-3GPP radio access (e.g. IEEE 802.11 based and/or satellite based)
Wireline access
Note 1: GSM-R, TETRA, and P25 are not considered as a radio access technology of FRMCS.
Note 2: Not all of the radio access technologies may support all of the FRMCS requirements.
T
TS 22.261
TS 22.278 reduced capabilities; partially encompasses only 4G access
[R-12.9-009]
The FRMCS System shall consider the availability of radio bearer services at the position of the FRMCS User to allow communication.
A
TS 22.261
6.3.2.1: The 5GS shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type.
[R-12.9-010]
The FRMCS System shall select appropriate radio bearer service with consideration of the FRMCS applications configurable preconditions (e.g. ranking of the available bearer services).
T
TS 22.261
TS 22.261 sub-clause 6.3.2.1
TS 22.278 reduced capabilities; partially encompasses only 4G access
TS 22.278 sub-clause 7.1.6
[R-12.9-011]
The FRMCS System shall provide indication to FRMCS application on which bearer service is being used.
T
N/A
Implementation requirement
[R-12.9-012]
Session continuity between 3GPP access and non-3GPP access shall not require FRMCS Users intervention.
T
TS 22.261
6.2.3: service continuity
6.3.2.1: The 5GS shall be able to support mobility between the supported access networks |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10 Use Case: QoS in a railway environment | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.1 Introduction | This system principle use case provides the framework for Quality of Service and priority level within the FRMCS System including the railway applications. The main purpose is to specify the list of attributes applicable to the FRMCS bearer service.
Railway applications exhibit different characteristics, e.g., in terms of latency or reliability. On the other hand, the FRMCS System offers bearer services with different properties.
In this context, two types of applications can be distinguished:
1. Applications that are aware of their transport service requirements and that are able to request those from the FRMCS System.
2. Applications that are not aware of their transport service requirements and that are therefore not able to request those.
Railway applications require a QoS classification ranging from high to low as low is “best effort”. The most important QoS parameters that determine the quality of the transport system are latency of the user data and reliability of the communication. In addition, guaranteed bandwidth assures the continuation of critical communication.
QoS impacts train punctuality and the entire utilisation of the track system. Therefore, the FRMCS System has to consider the various QoS requirements.
Apart from high train speed operation, which goes up to 500kmh-1, other fundamental factors affect wireless communication. Railways are facing various radio signal propagation conditions such as in free space and in tunnels. Free space encompasses various structural and constructional scenarios. Railway corridors in hilly terrain or forest aisle are some examples.
Radio propagation in large railway stations and shunting yards is different from the one of the main lines. Moving trains in stations or moving cargo wagons in shunting yards cause different propagation conditions.
Radio tower site-to-site distance requires special attention. This distance varies depending on the type of area (rural or urban) and is determined by the boundary conditions of the RF signal (e.g. frequency band and power budget). Railways clearly require to deploy FRMCS while keeping the same distance between the radio towers in order to reuse the infrastructure deployed for GSM-R.
Voice communication is commonly used during rail operation to give instructions to a driver of a locomotive in shunting operation, track maintenance etc. Rail environmental conditions like slowdown or movement of a train can impact the understandability of the voice.
Radio propagation conditions in a rail environment are quite specific. For example train speed up to 500km/h or the insertion loss of the radio signal into a train. Staff has to work in the train, beside a train or under the train etc. while voice communication is ongoing. Such conditions shall not lower the intelligibility of the voice.
Radio spectrum constraints in some regions require high efficiency in terms of radio bandwidth utilisation where voice communication coexists with other communication types simultaneously. The resulting voice codec has to consider these specific conditions.
In this chapter, the use cases related to Quality of Service (QoS) and priority are defined.
QoS and Priority includes:
• A QoS characteristics (latency, reliability, throughput, setup time) expected from the FRMCS System in order to fulfil the required level of communication quality
• A priority level, the priority in which the communication is handled by the FRMCS System
The following use cases are defined:
• • Allocation of resources meeting the QoS and priority level
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2 Use case: Allocation of resources meeting the QoS and priority level | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2.1 Description | The basis for this use case is the UIC FRMCS URS wherein communication attributes define the QoS to be achieved for the various kinds of railway applications. These attributes are not part of the functional use case description but relevant for the FRMCS System and therefore subject of this use case.
Regarding the URS communication attributes, not all attributes are covered in the QoS use case. The following items are considered:
• Type of communication
• Latency, the delay between action and reaction
• Session Reliability
• Setup of communication, the time to establish a voice or data communication session
• Talker assignment time in group communication
• Audio (Voice) Quality
For further details, refer to the corresponding use cases in chapters 5 – 9. In these chapters the QoS requirements are specified on functional level. A reference is used which refers to real values’ in this QoS use case.
In order to be able to deliver a certain level of communication quality, the FRMCS System enables the allocation of resources meeting a Quality of Service (QoS) characteristics for each communication.
In order to be able to deliver a certain level of communication precedence, the FRMCS System enables the allocation of a priority for each communication.
The FRMCS System allows communications with a higher priority to take precedence over communications with a lower priority and have the ability to pre-empt other communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2.2 Pre-conditions | The pre-conditions of the functional use cases out of chapter 5 – 9 are applicable.
The QoS and priority level allowed for each communication, are predefined by the FRMCS network operator. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2.3 Service flows | The service flows of the functional use cases out chapter 5 – 9 are applicable.
Application categories
Application categories describe the data transfer characteristic to be achieved by a bearer service. The FRMCS System shall consider the following user plane application categories:
Voice for user to user or multiuser communication; Voice follows the typical conversational pattern and requires low delay inside the transport system;
Critical Voice follows the voice conversational pattern but requires immediate session setup;
Video used for general observations purposes, e.g. maintenance;
Critical Video with indirect impact on train operation, e.g. passenger surveillance;
Very Critical Video with direct impact on safety- related critical train control and operation, e.g. used in driverless ( e.g. GoA3/GoA4) operation for automated detection of objects (no human in the loop) or video-based remote control (human in the loop).
Very critical data for future rail applications;
Critical data follows the response pattern and requires high reliable transport. This category comprises future and legacy applications e.g. ETCS;
Non-Critical data used for the exchange of railway system or communication relevant information; requires high reliable transmission and preservation of the response pattern;
Messaging for the exchange of non-critical short information messages, recorded voice (for example voicemail), data, pictures, video; requires reliable transmission;
Priority Level
In order to reach the QoS applicable for each application category, transport priority levels are required to differentiate among the communication urgency. Priority handling of communication service encompasses the assignment of a priority to a communication and involves the seizing of resources, which are in use by a communication having a lower ranking in the absence of idle resources. Priority handling includes as well discontinuation of an ongoing communication having a lower priority to allow an incoming communication of higher priority. Priority handling needs to be provided to a FRMCS User for all communications.
Priorities are treated by the FRMCS User/Equipment in the FRMCS System based on the following conditions:
• The priority level depends on the FRMCS User initiating the communication.
• The communication can have the priority level selected by the FRMCS User at setup or the priority level is predefined at registration. The treatment of priority level also applies when the FRMCS User is registered to a visited FRMCS network.
• The definition of the priority level which may cause pre‑emption of another ongoing communication needs to be stored and can be changed by the FRMCS User.
• The FRMCS System is able to allocate setup classes i.e. communication setup time requirements and resource pre-emption capabilities to each priority level.
• In case of resource pre‑emption, the pre‑empted FRMCS user needs to be provided with a suitable indication.
• The priority level can be selected by the FRMCs User on a per communication basis.
The FRMCS User may select any priority level up to the authorised priority level. The maximum priority level needs to be stored on the UICC. At communication setup, the FRMCS Equipment and the FRMCS System verify the priority level at setup against the maximum authorised priority level. If the FRMCS User has not selected a priority level at setup, the FRMCS System applies a FRMCS User specific default priority level. If the FRMCS User has selected at setup a priority level higher than the maximum authorised priority level, the maximum authorised priority level is applied for the communication.
Service Attributes
From FRMCS User point of view there are two main service attributes latency and communication reliability.
For the Latency two classifications are applicable:
Low User data delay harms the functioning of the application.
Normal User data delay does not harm the sequence and progress of the application.
From FRMCS System point of view, latency quantifies the end-to-end user data transport delay between the involved communication entities.
Reliability (in accordance to TS 22.261): in the context of network layer packet transmissions, percentage value of the amount of sent network layer packets successfully delivered to a given system entity within the time constraint required by the targeted service, divided by the total number of sent network layer packets.
Two levels are to be taken into account:
High The packet loss at transport level is exceptional rare.
Normal The packet loss at transport level is seldom.
The FRMCS System is able to assign multiple individual FRMCS User communications having individual QoS profile to a single IP address.
To meet the different application characteristics e.g. conversational pattern, real-time or critical data further itemisation is necessary. The mapping of the service attributes latency and reliability among functional requirements and FRMCS System as well as their target values are summarised in Table 12.10-1.
Service Attribute
FRMCS - Functional Requirement
FRMCS – System Requirement
Service Attribute value
Latency
Low
Ultra-Low
≤10ms
Low
≤100ms
Normal
Normal
≤500ms
Best Effort
>500ms
Reliability
High
Ultra-High
99.9999%
High
99.9%
Normal
Normal
99%
Table 12.10-1 - Service attribute mapping
Some application categories are time stringent e.g. critical voice or critical data.
The range of latency and reliability requirements have a certain dependency on the speed of the trains. In general, the requirement is that the service attributes can be guaranteed up to 500kmh-1. Certain combinations of latency and reliability apply only to Low Speed (≤ 40kmh-1).
The applications are considered as real-time when the FRMCS functional requirement for the latency is specified as “Low” and “Ultra Low”, according to table 12.10 1.
Session handling
Setup time of a communication session is essential because of their safety related character. Communication session setup encompasses the value of the elapsed time between the communication establishment request and the indication of successful communication session establishment. The FRMCS User requires two classes:
Immediate The FRMCS User requires immediate setup of the communication session. The duration of the immediate communication session establishment shall not exceed 1 second.
Normal Normal communication session setup time range does not harm the use of the application. The time duration of the normal communication session establishment shall not exceed 3 seconds.
Talker assignment time comprises the timeframe between talker request and the permission to talk applicable to group communication. This timeframe shall be lower than 300ms. Talker assignment time assumes that a group communication has been set up.
Session Loss Rate (SLR) indicates the number of sessions released unintentionally per accumulated session time. SLR shall be <10-2/h.
Communication and QoS assignment
In order to provide the required level of communication quality, the FRMCS System will request the applicable resources as required for the communication service from the underlying 3GPP transport system and if appropriate also from non-3GPP transport systems. The transport resources are characterised by latency, reliability, guaranteed bitrate/non-guaranteed bitrate and communication service priority.
If no specific service attributes are required for a certain communication service, the FRMCS System is able to apply a predefined default.
Each communication service resource characteristic can be requested independently of the others.
As result of the request to the underlying transport system, the FRMCS System may offer different values than the ones requested but which fit to the categories summarised in Table 12.10-1.
The available radio spectrum in certain regions, for example in Europe is rather limited, therefore the FRMCS System might apply different resources for the same communication service in different regions to achieve a radio resource efficient use of the available bandwidth.
Audio quality
Voice intelligibility strongly depends on the audio bandwidth. FRMCS System has to consider for voice communication following minimum requirements:
• Encoding of speech encompass in minimum the range of 200–7000 Hz;
• The codec meets the local radio channel and capacity requirements of the FRMCS system;
• The coding of speech signals is robust to radio impairments sacrificing voice clarity;
General functional service flows
The QoS characteristics and priority levels allowed for each application are predefined by the network operator.
The performance of the QoS and the priority parameters of the corresponding communication are constantly monitored by the FRMCS System.
The FRMCS System indicates QoS degradations to the communication application.
When the required QoS is not achieved, the communication application is able to:
• maintain the communication, or;
• release the communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2.4 Post-conditions | The post conditions of the functional use cases out of chapter 5 – 9 are applicable. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.10.2-001]
The FRMCS System shall be capable of providing different levels of QoS.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 1
[R-12.10.2-002]
The FRMCS-system service attributes shall be allocated unambiguously per application and/or per session and/or per FRMCS User.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 1
sub-clause 6.8 paragraph 3, 4
[R-12.10.2-003]
The FRMCS System shall support the efficient use of the radio resources.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 3
sub-clause 6.23.2
[R-12.10.2-004]
The FRMCS System shall provide service attribute control on a peer to peer basis.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 6
sub-clause 6.8 paragraph 3
[R-12.10.2-005]
The FRMCS System shall provide a mapping between application characteristics and the bearer service attributes.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 1
[R-12.10.2-006]
The FRMCS System shall be able to support different QoS for uplink and downlink of asymmetric bearers.
(A)T
TS 22.261
sub-clause 6.7.2 paragraph 2
[R-12.10.2-007]
The FRMCS System shall be able to modify service attributes during an active communication session.
A/T
TS 22.261
TS 22.280
TS 22.261 sub-clause 6.8 paragraph 1
TS 22.280 sub-clause 6.8
[R-12.10.2-008]
The FRMCS System shall detect and process the various user data traffic characteristics, latency and session reliability requirements. These requirements are summarised in Table 12.10-2.
(A)T
TS 22.261
sub-clause 6.8 paragraph 6
[R-12.10.2-009]
The FRMCS System shall support the applicable QoS requirements up to a train speed of 500kmh-1 at all locations along the track unless restrictions are indicated which are:
Low speed ≤ 40kmh-1.
T
22.289
sub-clause 5.2.2
[R-12.10.2-010]
To prioritize among the application categories and their related QoS, the FRMCS System shall support 15 priority levels.
T
22.280
[R-6.8.7.2-005]
[R-12.10.2-011]
The FRMCS System shall be able to request service attributes (latency, reliability, guaranteed bitrate/ non-guaranteed bitrate and priority) from the underlying 3GPP transport system and if appropriate also from non-3GPP transport systems.
T
TS 22.261
sub-clause 6.7.2 paragraph 5, 8
[R-12.10.2-012]
The FRMCS System shall be able to apply predefined default service attributes.
T
TS 22.261
sub-clause 6.8 paragraph 4-6
[R-12.10.2-013]
The FRMCS System shall be able to request each communication service attributes independently of the others.
T
TS 22.261
sub-clause 6.7.2 paragraph 1, 2, 6
[R-12.10.2-014]
The FRMCS System shall be able to assess whether the communication service attributes received from the transport system are sufficient to support the communication service fully or in a restricted way and report this information to the FRMCS application.
T
TS 22.261
sub-clause 6.7.2 paragraph 3
[R-12.10.2-015]
The FRMCS System shall be able to keep the communication priority independent from the QoS parameters latency, reliability, guaranteed/non-guaranteed bitrate.
T
TS 22.261
sub-clause 6.7.2 paragraph 4
[R-12.10.2-016]
The FRMCS System shall provide a radio resource efficient allocation of the communication bandwidth.
T
TS 22.261
sub-clause 6.7.2 paragraph 3
sub-clause 6.23.2
[R-12.10.2-017]
Talker assignment time, the timeframe between talker request and the permission to talk in a multi-user voice communication, shall be lower than 300ms.
A/T
22.179
[R-6.15.3.2-012] The MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT Request.
[R-6.15.3.2-013] For MCPTT Emergency Group Calls and Imminent Peril Calls the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 99% of all MCPTT Requests.
[R-12.10.2-018]
FRMCS system shall support at least encoding of speech signals between 200–7000 Hz.
A/T
22.280
26.441
TS 22.280
sub-clause 5.13
TS 26.441
entire document
[R-12.10.2-019]
The FRMCS voice codec shall be robust to meet different radio channel impairments caused by the different working conditions in the train, beside or under the train.
A/T
22.280
26.445
clause 5
s0504-s0506
[R-12.10.2-020]
The encoding of speech signals in the FRMCS system shall be efficient to meet limited radio resource availability.
A/T
22.280
26.445
clause 5
s0504-s0506
[R-12.10.2-021]
Priority handling of communication service in the FRMCS System shall encompass the assignment of a priority to a communication and involves the seizing of resources, which are in use by a communication having a lower ranking in the absence of idle resources.
A/T
22.280
[R-6.8.7.2-001]
[R-12.10.2-022]
Priority handling of the FRMCS System shall support discontinuation of an ongoing communication having a lower priority to allow an incoming communication of higher priority.
A/T
22.280
[R-6.8.7.2-004]
[R-12.10.2-023]
The FRMCS System shall always consider the priority of the FRMCS User initiating the communication.
A
22.280
[R-6.8.7.2-002]
[R-12.10.2-024]
The FRMCS System shall consider for a communication the priority level selected by the FRMCS User at setup or the priority level predefined at registration.
A
22.280
[R-6.8.7.2-004]
[R-12.10.2-025]
The FRMCS System shall treat the communication priority levels when the FRMCS User is registered to a FRMCS network.
A
22.280
[R-6.8.7.2-001]
[R-12.10.2-026]
The definition of the priority level which may cause pre-emption of another ongoing communication shall be stored and can be changed by the FRMCS User.
A
22.280
[R-6.8.7.2-004]
[R-12.10.2-027]
The FRMCS System shall be able to allocate setup classes i.e. communication setup time requirements and resource pre-emption capabilities to each priority level.
A/T
22.280
[R-6.8.7.2-003]
[R-12.10.2-028]
In case of resource pre-emption, the pre-empted FRMCS user shall be provided with a suitable indication.
A
N/A
It is an implemenation choice
[R-12.10.2-029]
The priority level shall be selected by the FRMCS User on a per communication basis.
A/T
22.280
[R-6.8.7.2-001]
[R-12.10.2-030]
The FRMCS User shall be able to select any priority level up to the authorised priority level. The maximum priority level shall be stored on the UICC.
A
22.280
[R-6.8.7.2-006]
[R-6.8.7.2-007]
[R-12.10.2-031]
At communication setup, the FRMCS Equipment/UE and the FRMCS System shall verify the priority level at setup against the maximum authorised priority level.
A
22.280
[R-6.8.7.2-008]
[R-12.10.2-032]
If the FRMCS User has not selected a priority level at setup, the FRMCS System shall apply a FRMCS User specific default priority level.
A
22.280
[R-6.8.7.2-009]
[R-12.10.2-033]
If the FRMCS User has selected at setup a priority level higher than the maximum authorised priority level, the maximum authorised priority level shall be applied by the FRMCS System for the communication.
A
22.280
[R-6.8.7.2-010]
[R-12.10.2-034]
The FRMCS System shall take into account the service attributes to allow selection of the available bearer services.
T
TS 22.261
sub-clause 6.7.2 paragraph 5, 8
[R-12.10.2-035]
The FRMCS System shall be able to assign multiple individual FRMCS User communications having individual QoS profile to a single IP address.
A/T
TS 22.261
TS 22.280
TS 22.261
sub-clause 6.8 paragraph 3
TS 22.280
sub-clause 5.15
[R-12.10.2-036]
The FRMCS System shall provide a mechanism to derive the communication characteristics of an application and map those on a data flow with a predefined QoS profile.
A/T
TS 22.261
TS 22.280
TS 22.261
sub-clause 6.8 paragraph 3
TS 22.280
sub-clause 5.15
[R-12.10.2-037]
The FRMCS System shall be able to notify the communication application when the network is not able to provide the requested QoS. When the required QoS is not achieved, the communication application shall be able to maintain or release the communication.
A
22.280
[R-6.8.6.2-005] communication application notification
Decision to maintain / release the communication is out of the scope of 3GPP.
Application categories and their related service attributes are grouped into specific QoS class. Table 12.10-2 summarises the QoS classes and their applicable service attributes.
Application Category
Service Attribute (according to Table 12.10-1)
Session establishment
Session Loss Rate
Latency peer to peer
Reliability
Voice
Low
Normal
Normal
NA
Critical Voice
Low
High
Immediate
NA
Video
Normal
High
Normal
NA
Critical Video
Low
High
Immediate
NA
Very Critical Video
Ultra Low or Low
Note 1
High
Normal
NA
Critical Data
(future applications)
Low
Ultra-High
Immediate
NA
Very Critical Data
Ultra-Low or Low (Note 1)
Ultra- High
Immediate
NA
Critical Data
(legacy applications)
Normal
High
Normal
<10-2/h
Non-Critical data
Normal
High
Normal
NA
Messaging
Best Effort
High
Normal
NA
Note 1: The latency “Ultra low” is restricted to low speed ≤40 kmh- 1.
Table 12.10-2 - Service and Service Attribute requirements
Railway specific conditions
1.) Following propagation conditions are to be considered:
• Free space in general
• Railway corridors in general and especially in hilly terrain
• Forest Aisle
• Underground / tunnel environment
• Moving trains or objects in a railway station and shunting yards
2.) FRMCS System should be able to reuse the existing GSM-R sites. A non-exhaustive example list provides the typical site-to-site deployment scenarios:
Rural environment: between 5 - 7km.
Urban environment: <5km. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3 Use case: service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS system for QoS and Priority level needs to be clear.
Depending on the migration scenario a user can be attached to the FRMCS system, to the GSM-R system or both.
For user-to-user/Multi-user communication the QoS/arbitration information between FRMCS and GSM-R needs to be exchanged.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3.3 Service flows | For user-to-user/Multi-user communication in the direction from GSM-R to FRMCS, the GSM-R priority level needs to be exchanged. The FRMCS System enables interworking of priorities between GSM-R and FRMCS allowing a mapping of GSM-R priority level to FRMCS priority level.
For user-to-user/Multi-user communication in the direction from FRMCS to GSMR, the FRMCS priority level is exchanged. The FRMCS System enables interworking of priorities between GSM-R and FRMCS allowing a mapping of FRMCS priority level to GSM-R priority level by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.10.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.10.3-001]
The FRMCS System shall enable interworking of priorities between GSM-R and FRMCS Systems allowing a mapping of GSM-R priority level to FRMCS priority level.
A
TS 22.179
TS 22.280
6.18.4.2
6.17.3.1
[R-12.10.3-002]
The FRMCS System shall enable interworking of priorities between GSM-R and FRMCS Systems allowing a mapping of FRMCS priority level to GSM-R priority level.
A
TS 22.179
TS 22.280
6.18.4.2
6.17.3.1
Refer to clause 12.13.5 (Use case: Provide call priority during interworking with LMR) for further requirements. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11 Use case: Provide broadband and mission critical services with seamless connectivity | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11.1 Description | The FRMCS shall provide the broadband and mission critical services with seamless connectivity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11.2 Pre-conditions | The operator at the train control centre has a Railway Emergency Call to a train which is in operation with 500km/h speed via 3GPP network.
Using a trainborne UE, the train driver is discussing an issue on operation of the train with train crews by a video call via a proximity-based services such as ProSe. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11.3 Service flows | The operator at the train control centre calls the train driver to give an emergency information including broadband video via the 3GPP network of FRMCS System.
The FRMCS System indicates the train driver is currently having a video call which has a normal priority with train crews.
The FRMCS System compares the priority of the Railway Emergency Call and the ongoing call.
Due to the higher priority of the Railway Emergency Call, the FRMCS System puts the ongoing call on hold and the participants receive a notification.
Within 300ms, the train driver is connected to the railway emergency call.
During the Railway Emergency Call, the train driver watches the broadband video as a supplement material to understand the emergency easier.
The train driver recognizes the emergency and does some proper works. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11.4 Post-conditions | After the Railway Emergency Call is ended, the hold call is resumed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.11.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.11.5-001]
The FRMCS System shall be able to define the priority level of Railway Emergency Call.
A
22.280
This requirement is covered by 22.280 [R-5.16.2-002]
[R-12.11.5-002]
The FRMCS System shall be able to handle the priority level of Railway Emergency Call.
A
22.280
This requirement is covered by 22.280 [R-5.16.2-002]
[R-12.11.5-003]
The FRMCS System shall support switching between on-network service and off-network service.
A
22.280
[This requirement is covered by 22.280 [R-6.18-001] to [R-6.18-006].]
[R-12.11.5-004]
The FRCMS system shall handle a priority call less than 300ms of call setup time in the environment of train speed up to 500km/h.
A
22.289
This requirement is covered by section 5.2.2 of 22.289.
[R-12.11.5-005]
The FRMCS System shall be able to present a video included in the Railway Emergency Call.
A
22.281
This requirement is covered by 22.281 [R-5.1.9.2.2-001] to [R-5.1.9.2.2-003]. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12 Use case: Offer railway services high-quality control functions with real-time train status monitoring | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12.1 Description | The FRMCS System offers high-quality control functions for railway services with real-time train status monitoring.
The train runs on railway by 500km/h of speed. The operator at the train control centre makes request to get the status of the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12.2 Pre-conditions | The train runs on railway by 500km/h of speed.
In the train, there is a trainborne UE and it is connected via 3GPP network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12.3 Service flows | The operator at the train control centre makes request to get the status of a train which runs on railway by 500km/h of speed.
The request is made with the train number, rather than the trainborne UE equipment identity.
The request goes through the backbone network and 3GPP network, reaches a trainborne UE.
The trainborne UE gets the train status such as speed and location and records the video monitoring data of the train.
The train status data are encrypted in the security reason by the trainborne UE and is responded back to the train control centre via the 3GPP network.
The trainborne UE requests the moving authority data to the train control system in the train control centre. The moving authority is a permission for a train to move to a specific location with supervision of speed.
The train control system responds the moving authority data to the trainborne UE within a time which is defined in FRMCS QoS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12.4 Post-conditions | The train control centre de-crypts the train status data and is able to see the status of the train including the streaming video of monitoring.
The train receives the moving authority data and references the data. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.12.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.12-001]
The FRMCS System shall provide a mapping between FRMCS Equipment Identity and the train number.
A
22.280
This requirement is covered by [R-5.9a-018] of 22.280
[R-12.12-002]
The FRMCS System shall be able to maintain a secure data channel for the train status monitoring communication.
A
22.280
This requirement is covered by [R-5.12-001] and [R-5.12-009] of 22.280
[R-12.12-003]
The FRMCS should be able to define a minimum bandwidth of video monitoring.
A
22.289
This requirement is covered by section 5.2.2 of 22.289
[R-12.12-004]
The FRMCS should be able to define a minimum delay time of communicating the train status monitoring.
A
22.289
This requirement is covered by section 5.2.2 of 22.289
[R-12.12-005]
The FRMCS should be able to define a minimum delay time of communicating the moving authority data.
A
22.289
This requirement is covered by section 5.2.2 of 22.289. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13 Use case: Provide call priority during interworking with LMR | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13.1 Description | There are Mission Critical Services such as Railway, use many kinds of communication technology, e.g. TRS and LTE. To make interworking between the networks to during provide FRMCS communication, it needs to manage call priority between calls which are made between the networks.
During the interworking between FRMCS and LMR systems including TETRA and P25, FRMCS provides call priority based on factors such as the situation, group priority, level of user, etc. For example, a Railway Emergency Call could be categorized as a public announcement on emergency (low-level priority) or an operation emergency call (high-level priority).
Examples on the priority of calls in FRMCS are provided in the following table:
Table 12.13-1: Priority of calls in FRMCS
Call Type
Priority
Related Action
Operation Emergency Call
0
(the highest)
Stop all the calls have priority lower than or equal to Control Safety Announcement
Control Safety Announcement (between Operation Users)
1
Stop all the calls have priority lower than or equal to Public Announcement on Emergency
Public Announcement on Emergency
2
Stop all the calls have priority lower than or equal to Operation Call
Operation Call
(not emergency case)
3
Stop all the calls have priority lower than or equal to Service Information Announcement
Service Information Announcement
4
-
The examples in the table 12.13-1 are made by modifying of the call priority of the railway communication system as a mission critical service [4].
If an operation emergency call is invoked by a user (maybe a train driver), it should have higher level of priority than the public announcement on emergency call of other user. In this case, all the lower priority calls may need to be pre-empted or queued to allow the operation emergency call.
In order to provide the call priority, the interworking needs to be able to maintain the information on the priority of each call and each user who invoked a call or a group call. When a call is invoked, FRMCS should compare the priority between the current call and the new call and decide which one is allowed to go through. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13.2 Pre-conditions | The operator at the train control centre has a Railway Emergency Call to a train which is in operation with 500km/h speed via 3GPP network.
Using a trainborne UE, the train driver has an announcement of control safety to the train crews via LMR such as TRS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13.3 Service flows | The operator at the train control centre calls the train driver and the train crews to give an emergency notice via the 3GPP network of FRMCS System.
The FRMCS System indicates the train driver and the train crews are currently having a group call which has a lower priority then the emergency notice call.
The FRMCS System queues the ongoing TRS call and connects the train control centre and the trainborne UE.
The emergency notice call from the train control centre via the 3GPP network, is relayed to TRS to make announce to the train driver and the train crews.
The train driver and the train crews recognize the emergency and do some proper works. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13.4 Post-conditions | After the emergency notice call is ended, the queued TRS call is resumed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.13.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.13-001]
FRMCS should be able to handle call priority when interworking with LMR communication systems.
A
22.179
22.280
This requirement is covered by 22.179 [R-6.18.3.2-006] to [R-6.18.3.2-009] and 22.179 [R-6.18.3.3-006] to [R-6.18.3.3-007].
The high level requirements of handling call priority are covered by many sections of 22.280, e.g. section 5.1.7 and 5.6.
TETRA and P25 may need considerations as follows:
a. TETRA may provide some customizable features to maintain the call priority such as Call ownership and Call priority.
b. P25 has no features to support the call priority.
c. FRMCS has many basic information to handle the call priority such as ‘Priority of the user for initiating/receiving calls’ in the user profile data and ‘Priority of the group’ in the group configuration data.]
[R-12.13-002]
The FRMCS System should be able to define a maximum call setup time for a call between 3GPP system and LMR system.
A
22.289
This requirement is covered by section 5.2.3 of 22.289
[R-12.13-003]
FRMCS should provide the call priority supporting features to interworking with LMR.
A
22.179
22.280
This requirement is covered by 22.179 [R-6.18.3.2-006] to [R-6.18.3.2-009] and 22.179 [R-6.18.3.3-006] to [R-6.18.3.3-007].
The high level requirements of handling call priority are covered by many sections of 22.280, e.g. section 5.1.7 and 5.6.
[R-12.13-004]
FRMCS should provide interworking between FRMCS System and LMR system.
A
22.179
covered by 22.179 [R-6.18.3.2-001] and [R-6.18.3.3-001] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14 Use Case: FRMCS Positioning Accuracy | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.1 Introduction | This system principle use case describes the positioning accuracy requirements to position a train, track side worker as well as other stationary and non-stationary object inside the track system. In general, positioning accuracy will become a major building block to increase the automation level of train operation. The main purpose is to specify the accuracy parameter values. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2 Use case: FRMCS Positioning Accuracy | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2.1 Description | Today fixed mounted balise are used to derive the train position inside the track-system. This kind of train positioning is precise enough when the train is moving. Static conditions like in stations, push-pull train operation or the frequent change between static and dynamic conditions during shunting operation require hundreds of fixed mounted balise. Thus, a balise without stationary reference shall overcome this circumstance.
According to Figure 12.14-1, individual coaches, trains, track side worker get equipped which such devices that report continuously the process status towards the applicable control centre enriched with the actual position information.
Figure 12.14-1 Positioning application areas
Tracks/lines or shunting areas are subdivided into autonomous hazard areas (red blocks see Figure 12.14-1). The continuous processing of positioning information allows the control centre to detect when hazard areas start to overlap. Based on the computed risk integral, the control centre is able to instruct the vehicles or trains in the concerned area to lower the speed up to a full stop.
To guarantee fail-safe operation in deriving the position of the vehicle, track-side worker etc., and independent positioning sources need to be provided. Beside inertial navigation, GNSS and others, the FRMCS System is required to be part of the positioning data acquisition process. This results from rather low predictable availability of satellite systems especially in mountain regions, multilevel railway station as well as in tunnels. In the worst case, “rough” positioning information only derived from the FRMCS – Land Mobile Network is present.
The combination of 3GPP radio access network and the train on-board system is able to support mechanisms that can be used to locate an entire train, stationary as well as non-stationary objects. Together with the positioning information of other sources (see Figure12.14-2) e.g. inertial navigation and GNSS, consolidated positioning information of the train/object will be computed that is able to fulfil higher accuracy of the positioning information. Train Onboard system as well as FRMCS location information system will receive the consolidated location positioning information for further processing by the train safety applications and/or FRMCS location information system.
Error! Objects cannot be created from editing field codes.
Figure 12.14-2 Consolidation of positioning source information
The subject described is applicable to other FRMCS functional use cases. The resulting positioning requirements in this use case are relevant for the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2.2 Pre-conditions | Railway line consist of station A, B and C. Station B is between station A and C.
FRMCS User 1 is used by an InterRegio train that stops in station A, B and C.
FRMCS User 2 is used by a high speed train that stops in station A and station C.
FRMCS User 3 is used on a parked train in station B.
FRMCS User 4 is used by mobile warning equipment located in station B.
Ground FRMCS User processes the received positioning information of the different train FRMCS Users for safety purposes.
FRMCS Users on the train (safety application) established the communication to the ground FRMCS User (safety application) that is responsible for train safety purposes on the line between the stations A and C including station B.
Base stations are covering the line between station A and station C. The structure of the base station along the line is linear. In some cases dual base stations per site can be used. The distance between adjacent base stations various between 1 and 10km.
Train speed profile ranges between 0 - 500km/h.
The base stations covering the line between station A and C are enhanced cellular base stations that are able to form a carrier grade positioning network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2.3 Service flows | Train FRMCS User 1 (safety application) as part of the InterRegio train approaches station B coming from station A.
Train FRMCS User 2 (safety application) as part of a high speed train passes station B coming from station C.
Train FRMCS User 3 (safety application) as part of the parked train in station B that continuous later.
Train FRMCS User as part of a mobile warning system protects a line section that is under construction.
All train FRMCS Users (safety application) periodically report their current position to the ground FRMCS User (safety application). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2.4 Post-conditions | Every train approached his final destination.
No harm to the ongoing construction work in station B. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.14.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.14.2-001]
The consolidated positioning information i.e. the location information resulting from the combination of all positioning sources available to the FRMCS System shall support following absolute positioning accuracy based on the train speed at >= 90% of the occasions:
0 - 40km/h Longitudinal: ≤1 m lateral: 1 - 3 m
Up to 120km/h Longitudinal: ≤34m lateral: 1 - 3 m
Up to 160km/h Longitudinal: ≤45m lateral: 1 - 3 m
Up to 320km/h Longitudinal: ≤89m lateral: 1 - 3 m
Up to 500km/h Longitudinal: ≤200m lateral: 1 - 3 m
See [9]
A/T
TS 22.261
TS 22.261 sub-clause 6.27.2
TS 22.261 sub-clause 7.3.2 – refer to positioning service level 3 (only one speed limit supported – up to 500 km/h – with horizontal accuracy of 1m)
TS 22.278 does not consider this requirement.
[R-12.14.2-002]
FRMCS System shall be able to support an initial positioning fix time of ≤5s.
A/T
TS 22.261
TS 22.261 sub-clause 7.3.2
TS 22.278 does not consider this requirement.
[R-12.14.2-003]
To avoid large offsets between adjacent hazard areas due to limited track space in a railway station, FRMCS System shall be able to support a sampling interval between two positioning cycles of <1s.
A/T
Not covered
TS 22.261
TS 22.261 sub-clause 7.3.2 (Positioning service latency = 1 s)
TS 22.278 does not consider this requirement.
[R-12.14.2-004]
FRMCS Equipment power consumption due to the use of positioning capabilities shall be minimised.
A/T
TS 22.261
TS 22.261 sub-clause 6.27.2 and 7.3.2.3 (location power saving mode with restriction in update rate)
TS 22.278 does not consider this requirement. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15 Use Case: FRMCS System security framework | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.1 Introduction | The security framework protects the FRMCS System against attacks and threats, like misuse, Denial of Service (DoS), unauthorized access to services, interception, man-in-the-middle attacks, replay attacks and intended data modification. It encompasses the protection of security attributes confidentiality, privacy, integrity, availability and non-reputation. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2 Use case: FRMCS System security framework | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.1 Description | The security framework protects:
• Services provided by the FRMCS System;
• Bearer flexible access including 3GPP as well as non-3GPP access;
• Direct interaction between FRMCS Equipment;
• Interaction between the FRMCS end user devices and FRMCS network;
• Interaction between FRMCS network functions;
• Stored data within the FRMCS System;
• Interworking between a FRMCS System and another FRMCS System;
• Interworking between a FRMCS System and a legacy system. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.