hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.2 Pre-conditions | FRMCS System is in use. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.3 Service flows | FRMCS System security framework related service flows cover the following aspects:
• identity management;
• authentication;
• authorization;
• key management;
• data protection (regarding integrity, confidentiality, privacy, non-reputation);
• prevention of attacks;
• detection of attacks;
• reaction on detected attacks. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.4 Post-conditions | The FRMCS System is protected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.15.2-001]
The FRMCS System security framework shall enable the use of unique identities.
A
TS 22.228
TS 22.280
A- TS 22.228 sub-clause 7.5.1
A- TS 22.280 [R-5.12-002]
[R-12.15.2-002]
The FRMCS System security framework shall allow the grouping of identities.
A
TS 22.228
TS 22.280
A- TS 22.228 sub-clause 7.5.1
A- TS 22.280 sub-clause 5.1.3, 5.12
[R-12.15.2-003]
The FRMCS System security framework shall provide mechanisms to authenticate a unique identity.
A/T
TS 22.278
TS 22.261
TS 22.228
TS 22.280
T- TS 22.278 sub-clause 9.2
T- TS 22.261 sub-clause 8.3
A- TS 22.228 sub-clause 11.2, H 2.3, H 3.3, H 4.3
A- TS 22.280 sub-clause 5.12
[R-12.15.2-004]
The FRMCS System security framework shall provide authentication mechanisms required for the secured interaction between FRMCS network functions.
A/T
N/A
Implementation requirement
[R-12.15.2-005]
The FRMCS System security framework shall provide mechanisms to authorise communications and the use of applications.
A
TS 22.280
TS 22.228
sub-clauses:5.9a2, 5.12, 5.16, 5.19, 6.4.2, 6.4.5, 6.4.6, 6.6, 6.7, 6.8, 6.13, 6.19.1
TS 22.228: sub-clause 5
[R-12.15.2-006]
The FRMCS System security framework shall provide a management of identities, passwords and keys required for the protection of FRMCS User communication, the interaction between FRMCS network functions as well as subscribers and service related data.
A/T
TS 22.261
TS 22.280
TS 22.261: Identity management (see section 8.5)
TS 22.280: Key management, profile management (see section 5.12
Password management is an implementation requirement.
[R-12.15.2-007]
The FRMCS System security framework shall be able to block the use of any FRMCS Equipment when it is detected as being stolen or lost.
A/T
TS 22.261
TS 22.280
T TS 22.261 sub-clause 8.7
A TS 22.280 sub-clause 6.13.4
[R-12.15.2-008]
The FRMCS System security framework shall be able to unblock the use any recovered stolen or lost FRMCS Equipment.
A/T
TS 22.278
TS 22.261
TS 22.280
T TS 22.261 sub-clause 8.7
A TS 22.280 sub-clause 6.13.4
[R-12.15.2-009]
The FRMCS System security framework shall protect the
services provided by the FRMCS System;
bearer flexible access including 3GPP as well as non-3GPP access;
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.
A/T
TS 22.261
TS 22.280
TS 22.261 sub-clause 8.2
TS 22.280: [R-6.13.6-001]
[R-12.15.2-010]
The FRMCS System security framework shall prevent software based attacks which have an impact on any of the following security attributes:
data confidentiality;
information privacy;
data integrity;
non-repudiation of data;
FRMCS System availability.
T
N/A
Implementation requirement
[R-12.15.2-011]
The FRMCS System security framework shall be able to detect software based attacks
which have an impact on any of the following security attributes:
data confidentiality;
information privacy;
data integrity;
non-repudiation of data transfer;
FRMCS System availability.
T
N/A
Implementation requirement
[R-12.15.2-012]
The FRMCS System security framework shall be able to react on detected software based attacks:
which have an impact on any of the following security attributes:
data confidentiality;
information privacy;
data integrity;
non-repudiation of data transfer;
FRMCS System availability.
T
N/A
Implementation requirement
[R-12.15.2-013]
The FRMCS System security framework shall provide procedures and mechanisms for management of FRMCS System security.
T
N/A
Implementation requirement
[R-12.15.2-014]
The FRMCS System security framework shall be able to track users’ actions such as usage of communication services, management operations, configuration changes etc.
A
TS 22.280
TS 22.280 sub-clause 6.15.4
[R-12.15.2-015]
The FRMCS System security framework shall be able to store security related data for post-analysis, e.g. forensic.
A
TS 22.280
TS 22.280 sub-clause 6.15.4 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16 Use Case: Interworking to external networks | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16.1 Introduction | This section describes the general interworking between FRMCS System, based on 3GPP transport and external communication/data networks.
12.16.2 Use case: FRMCS System external network interworking
12.16.2.1 Description
Apart from the communication facilities within one FRMCS network, FRMCS User(s) require as well communication facilities to and from other external networks. Thus an FRMCS System has to provide various communication facilities between FRMCS User(s) and external network user(s).
The term “user” is hereby meant as either an individual or an application.
The necessary interworking to external networks is able to provide incoming and outgoing voice- and data bearer services.
The following are considered as external networks:
• Public Switched Telephone Network (PSTN)
• Private Telephone Network
• Private Mobile Radio (PMR) or Land Mobile Radio (LMR): refer to section 12.6 for additional use cases to interworking between FRMCS and LMR.
• Public Land Mobile network (PLMN)
• Other GSM-R networks: refer to section 12.8 for additional use cases to interworking between FMCS and GSM-R.
• Other FRMCS networks
• Other Wireless Access
• Other packet data networks, e.g. Internet. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16.2.2 Pre-conditions | The FRMCS User is attached to the FRMCS System.
The external network user is attached to the external network.
Authentication and authorization of the FRMCS User(s) and communications initiated by the FRMCS Users are managed within the FRMCS System.
The required Quality of Service is managed by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16.2.3 Service flows | Case 1 (Communication is to be established from FRMCS system towards an external network)
An entitled FRMCS User enters a destination address for establishment of a communication session. The destination address can be of the following formats:
• E.164 address
• Uniform Resource Identifier (URI) (e.g. SIP address, URL, e-mail address…)
• EIRENE functional number
• FRMCS Functional Identity
• FRMCS User Identity
• FRMCS subscriber identity
Based on the destination address, the FRMCS System performs the following:
• Detects the correct bearer type including characteristics
• Translates the destination address to a routable format
• Analyses if the destination is external to FRMCS System
• Selects an available interconnection for the bearer type. (Interconnection selection can be either a direct or indirect connection, e.g. gateway)
• Attempts to setup the communication session
Case2 (Communication is to be established from an external network towards FRMCS system)
An external network user tries to establish a communication session towards an FRMCS User. The destination address can be of the following formats, depending of the capabilities of the external network:
• E.164 address
• Uniform Resource Identifier (URI) (e g SIP address, URL, e-mail address…)
• FRMCS Functional Identity (other FRMCS networks)
• FRMCS User Identity (other FRMCS networks)
• FRMCS subscriber identity (other FRMCS networks)
Based on the destination address, the FRMCS System does the following:
• Locates user(s) within the FRMCS System to detect possible roaming case
• Translates the destination address into a routable format
• Detects the correct bearer characteristics
• Establishes the communication session. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16.2.4 Post-conditions | Case1
An FRMCS User is able to establish voice and/or data communication with intended user(s) in an external network.
Case2
An external network user is able to establish voice and/or data communication with intended user(s) managed by the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.16.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.16.2-001]
The FRMCS System shall provide means of regulated interworking (s) for telephony services to/from external public networks e.g. system administrator has the ability to restrict access telephony services to/from external networks.
T
Covered by TS 22.179
TS 22.280
For GSM-R, covered in 22.179 [R-6.18.4.2-001-5].
For other MCX systems, covered in 22.280 [R-6.17.2-001-7]
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For PLMN and PSTN, covered by 22.280 [R.6.17.3.2-002]
[R-12.16.2-002]
The FRMCS System shall provide Packet switched (PS) interworking (s) to/from external networks.
T
Partly covered by TS 22.280
For GSM-R and 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).
For other MCX systems, covered in 22.280 [R-6.17.2-001-7].
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For PLMN and PSTN, interworking is not covered.
[R-12.16.2-003]
The FRMCS System shall provide the necessary signalling and voice codec adaptation in the context of interworking with external networks.
T
Partly covered by TS 22.179
For GSM-R covered in 22.179 [R-6.18.4.2-005] For other MCX systems, not required.
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For PLMN and PSTN, interworking is not covered
[R-12.16.2-004]
The FRMCS System shall provide interworking for supplementary services related to the external network.
A
Not covered.
For other MCX systems, not applicable (other mechanisms are provided).
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For other external systems, not covered.
[R-12.16.2-005]
The FRMCS System shall provide interworking communication with external networks in a secured way.
A/T
Partly covered by TS 22.280
For other MCX systems covered in 22.280 [R-6.17.2-001], [R-6.17.2-002], [R-6.17.2-007].
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For PLMN and PSTN, interworking is not covered.
For other external systems, not covered.
[R-12.16.2-006]
The FRMCS System shall provide interworking communication with external networks with the required Quality of Service.
T
Partly covered by TS 22.280
For other MCX systems, not covered.
For GSM-R, covered by [R-6.17.3.1-002].
For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.
For PLMN and PSTN, interworking is not covered.
[R-12.16.2-007]
The FRMCS System shall be able to select interconnection based on multiple interconnections of the same type (i.e. redundancy of physical/logical paths and transmission links for both control and user planes including load aggregation and/or warm stand-by techniques).
A/T
N/A (physical paths)
TS 22.280
Implementation requirement for redundant physical paths.
Partly covered by clause 6.17.3.1 for GSM-R.
Load aggregation and/or warm stand-by techniques to be supported by the Interworking Function (IWF).
[R-12.16.2-008]
The FRMCS System shall select the bearer characteristics based on exchanged signalling information (i.e. dynamic and automatic configuration of interconnections parameters).
T
TS 22.280
Partly covered by clause 6.17.3.1 for GSM-R.
Dynamic and automatic configuration of interconnections parameters to be supported by the Interworking Function (IWF).
[R-12.16.2-009]
The FRMCS System shall select the appropriate interconnection type, e.g. CS or PS based on the destination address of the target user.
T
N/A
For GSM-R, PS interworking is not required (see above). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17 Use Case: FRMCS On-network/Off-network communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.1 Introduction | Typical communication will involve the transport capabilities of the FRMCS network but some of the FRMCS communication scenarios require the use of Off-network bearer services. Also a combination of On-network and Off-network bearer services can increase the entire availability of the entire FRMCS transport system which is essential for railways especially in Automated Train Operation.
This results into three global FRMCS communications modes:
• On-network only communication
• Off-network only communication
• Combined On-network and Off-network communication.
Note: The different types of communication use cases related to On-network and/or Off-network are summarised in Annex C. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2 Use case: On-network/Off-network communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2.1 Description | On-network only communication mode uses the bearer services that are provided by the FRMCS land mobile network. It relies on the flexible use of 3GPP and non 3GPP bearer services and allows user to user as well as multi-user communication.
Figure 12.17-1 FRMCS On-network communication mode
On-network communication is used for Mobile FRMCS User (onboard) to Ground FRMCS User (controller) communication.
Off-network only communication mode uses a dedicated radio bearer service for proximity communication which is supported by FRMCS Equipment. It relies on an appropriate 3GPP bearer service that allows user to user as well as multi-user communication without direct involvement of FRMCS land mobile network. A relay function in Off-network communication mode can extend the range of the communication facilities. FRMCS Equipment may bridge a distance for proximity communications of up to 3km.
Figure 12.17-2: FRMCS Off-network communication mode
Off-network communication can be used for e.g. shunting or banking communication where not always a ground FRMCS User i.e. controller is necessary. Off-network communication provides also the backup if On-network communication is unavailable.
Combined On-and Off-network communication mode encompasses the parallel use of the FRMCS land mobile network and the radio bearer service for proximity communication. There are various sub-categories for this communication mode:
Relay mode 1: A FRMCS Equipment uses On-network and Off-network communication and constitutes an On- and Off-network relay function to other FRMCS Equipment’s that are in Off-network only communication mode.
Figure 12.17-3: FRMCS On-network and Off-network communication mode - Relay mode 1
On-network and off network communication mode relay mode 1 bridge over the coupling loss for FRMCS Users in a train that do not have access to the roof antenna. Hence, relay mode 1 helps to overcome radio link issues in a train.
Relay mode 2: FRMCS equipment encompasses On-network and Off-network communication that enables Off-network bearer service for an Off-network only communication relay function.
Figure 12.17- 4: FRMCS On-network/Off-network communication mode - Relay mode 2
Relay mode 2 is an extension of relay mode 1 that allows e.g. the concatenation of maintenance teams during tunnel maintenance activities.
Relay mode 3: FRMCS Equipment encompasses On-network and Off-network communication. Each FRMCS Equipment is able to constitute an On-network and Off-network relay function. Interworking between one and several of such relay functions allows the use of multipath transport facilities for communication purposes.
Figure 12.17-5: FRMCS On-network-and Off-network communication mode - Relay mode 3
Relay mode 3 allows multipath transport facilities for FRMCS Applications that require extreme high communication reliability e.g. control command signaling applications like ATP. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2.2 Pre-conditions | On-network only communication
FRMCS Equipment is authorised to use On-network communication mode.
FRMCS Users are attached to the FRMCS System and is authorised to establish user to user and/or multi-user communication.
Off-network only communication
FRMCS Equipment is authorised to use Off-network only communication mode. Some of the FRMCS Equipment’s are authorised to establish an Off-network communication relay function.
The FRMCS Users are authorised to establish user to user and/or multi-user communication.
Combined On-network-and Off-network communication
The FRMCS Users are authorised to establish user to user and/or multi-user communication.
Relay Mode 1
The FRMCS Equipment that supports in On-network/Off-network relay communication mode is authorised to establish Off-network communication to other FRMCS Equipment’s which are in Off-network only communication mode.
Relay Mode 2
FRMCS Equipment that supports Off-network relay communication mode is authorised to establish a communication to other FRMCS Equipment’s that are in Off-network communication mode. FRMCS Equipment that is in Off-network relay communication mode is authorised to establish an Off-network communication to an On-network and Off-network relay communication mode FRMCS Equipment.
Relay Mode 3
FRMCS Equipment’s in On-network and Off-network communication mode are authorised to establish On- and Off-network communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2.3 Service flows | FRMCS Users are involved in the different types of communication modes establishes user to user and/or multi-user communications.
On-network only communication
The FRMCS equipment establishes On-network only communication.
Off-network only communication
The FRMCS Equipment in Off-network relay communication mode and the FRMCS Equipment’s in Off-network communication mode establish the Off-network communication.
Combined On-network-and Off-network communication
Relay Mode 1
The FRMCS Equipment in On-network/Off-network communication mode establishes:
• an On-network communication
• Off-network communication to FRMCS Equipment’s in Off-network only communication mode
Relay Mode 2
The FRMCS Equipment in On-network and Off-network communication mode establishes:
• an On-network communication
• Off-network communication to a FRMCS Equipment in Off-network relay communication mode
The FRMCS equipment in Off-network relay communication mode establishes Off-network communication to FRMCS equipment’s in Off-network only communication mode.
Relay Mode 3
The FRMCS equipment’s in On-network and Off-network communication mode establishes:
• an On-network communication
• Off-network communication to a FRMCS Equipment in On-network-and Off-network relay communication mode. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2.4 Post-conditions | On-network only communication
User-to-user and/or multi-user communication is established.
Off-network only communication
User-to-user and/or multi-user communication is established.
Combined On-network/Off-network communication
User-to-user and/or multi-user communication is established that encompasses both communication modes. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.17.2.5 Potential requirements and gap analysis | Reference Number
Application / Transport
SA1 spec covering
Comments
[R-12.17.2-001]
FRMCS security requirements according to chapter 12.15 shall apply to On-network and Off-network communication.
A/T
TS 22.278
TS 22.261
TS 22.228
TS 22.280
Covered for on-network (refer to section 12.15).
[R-12.17.2-002]
FRMCS QoS requirements (reference QoS section 12.10) shall apply to On-network and Off-network communication.
A/T
TS 22.261
TS 22.280
TS 22.289
Covered for on-network (refer to section 12.10).
[R-12.17.2-003]
FRMCS positioning accuracy requirements according to chapter 12.14 shall apply to On-network and Off-network communication.
A/T
TS 22.261
Partly covered for on-network (refer to section 12.14).
[R-12.17.2-004]
The FRMCS System requirements applicable for communication recording as specified in the recording and access application use cases shall apply to On-network and Off-network communication.
A/T
TS 22.280
See gap analysis of sub-clause 6.10.
[R-12.17.2-005]
FRMCS On-network communication shall support the flexible use of different radio bearers (see Bearer Flexibility).
A/T
TS 22.278
TS 22.261
TS 22.280
TS 22.280
See sub-clauses in chapter 5 and 6
[R-12.17.2-006]
FRMCS Equipment shall support On-network only as well as On-and Off-network relay communication.
T
TS 22.278
TS 22.261
TS 22.280
22.278 – sub-clause 7A:
Mode 1 covered by ProSe UE-to-Network relay (single-hop relay with UE-to-Network relay UE between remote UE and gNb)
Mode 2 not covered by ProSe UE-to-UE Relay (multi-hop relays not covered)
Mode 3 not covered (multi-hop relays not covered).
22.261: UE-to-Network Relay not covered in 5GS.
22.280 [R-7.11-001]: use of off-net and on-net MCX Services simultaneously
[R-12.17.2-007]
FRMCS shall be able to support Off-network communication that tide over a distance between FRMCS UE’s of up to 3km.
T
TS 22.289
Covered by table 5.2.2-2 (relevant for Off-Network MCData Service only)
[R-12.17.2-008]
FRMCS Equipment shall support Off-network only as well as Off-network relay communication.
T
TS 22.278
TS 22.261
TS 22.280
22.278 – sub-clause 7A:
Mode 1 covered by ProSe UE-to-Network relay (single-hop relay with UE-to-Network relay UE between remote UE and gNb)
Mode 2 not covered by ProSe UE-to-UE Relay (multi-hop relays not covered)
Mode 3 not covered (multi-hop relays not covered).
22.261: UE-to-Network Relay not covered in 5GS.
22.280 [R-7.11-001]: use of off-net and on-net MCX Services simultaneously |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18 Call restriction service | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18.1 Description | Call restriction based on location information and/or user identity is widely used in China railway market. It is proposed that FRMCS supports this service. This service restricts calls outside specific area according to the location information and/or user identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18.2 Pre-conditions | FRMCS user is attached to the FRMCS system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18.3 Service Flows | Scenario 1: The dispatcher calls the driver; the call shall be allowed in the area managed by the dispatcher according to the location information (i.e. calls outside area managed by dispatcher are restricted)
Scenario 2: The user calls the dispatcher, whether the call is allowed or restricted depends on the user identity. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18.4 Post-conditions | If the driver is located within the area managed by the dispatcher, the call is allowed.
If the driver is outside the area managed by the dispatcher, the call is restricted.
Only an authorised user (e.g. the driver) is able to initiate the call to dispatcher, calls from other users to dispatcher will be restricted. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.18.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.18-001]
The FRMCS System shall be able to support the call restriction service taking into account the user identity and/or location information.
A
22.280
Covered by R-5.9a-020, R-5.9a-021, R-5.11-0XX, in particular R-5.11-007 and R-5.11-009 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19 Allocation and isolation of FRMCS communication resources | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.1 Introduction | Rail communication distinguishes between critical, performance and business applications. It is an essential task of the FRMCS System to support segregation of data transmission, in this context the isolation of railway application data utilizing the same available transport resources. The principle of segregation of data transmission applies to:
- FRMCS communication infrastructure may be shared by multiple railway undertakings;
- Different railway applications of one railway undertaking require isolated and customized communication resources (transport resources and functionalities) for each application.
In general, it is anticipated that isolated transport services can be provided with a predictable and guaranteed QoS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2 Use case: Isolation of FRMCS communication resources | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2.1 Description | Scenario 1: Isolation for individual railway undertakings
An FRMCS System infrastructure manager may have to host different railway undertakings. Due to isolation reasons, these railway undertakings require segregation of their communication and a predictable and guaranteed QoS.
Scenario 2: Isolation among categories of applications belonging to one railway undertaking
Railway community has classified their application to different categories, i.e. critical, performance and business. Due to isolation reasons, the related communications require segregation of data transmission having a predictable and guaranteed QoS for the different categories of applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2.2 Pre-conditions | General
Segregation of data transmission is supported by the FRMCS system.
Scenario 1: Isolation reasons for individual railway undertakings
Railway undertakings need their own segregated transport resources and network functionalities needed for their communications.
Scenario 2: Isolation among categories of applications belonging to one railway undertaking
Railway undertaking assigns each application category to their own segregated transport resources and network functionalities needed for their communications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2.3 Service flows | Scenario 1: Isolation reasons for individual railway undertakings
Each railway undertaking in a country utilises dedicated and isolated transport resources and network functionalities.
Scenario 2: Isolation among categories of applications belonging to one railway undertaking
Each application category of one railway undertaking utilises dedicated and isolated transport resources and network functionalities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2.4 Post-conditions | Scenario1
Each railway undertaking in a country obtains dedicated and segregated transport resources and network functionalities.
Scenario2
Each application category of one railway undertaking obtains dedicated and segregated transport resources and network functionalities. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.19.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.19.2.5-001]
The FRMCS System shall be able to support the segregation of transport data for different application categories.
A/T
22.261, clause 4
“Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers.”
[R-12.19.2.5-002]
The FRMCS System shall support dedicated QoS handling for segregation of transport data.
T
22.261 clause 6.1.1
“Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g., priority, charging, policy control, security, and mobility), differences in performance requirements (e.g., latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g., MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO).” |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20 FRMCS Equipment capabilities for multiple FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.1 Introduction | For communication, rail vehicles today have a dedicated terminal approach. For each type of application, voice or data (e.g. ATP), one (1:1) or several mobile terminals (1: n) are used. Multiple Mobile Terminals for one application are required for operational or availability reasons.
With the introduction of the FRMCS System, the number of applications will multiply. More recent train compositions already have a large number of sensors whose information is exchanged for control or diagnosis between the vehicle and the ground control centre.
With the continuation of the 1:1 principle (application equals mobile terminal) this would correspond to a multiplication of the mobile terminals. In addition, the space required for mobile terminals and roof antennas would significantly increase. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.2 Description | In the case of vehicle/train composition, FRMCS Users can take full advantage of the transport facilities of the 3GPP system while ensuring priority, latency and reliability for each communication. FRMCS User and the associated communication applications need to be decoupled from the FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.3 Pre-conditions | At least one FRMCS Equipment is installed at the vehicle/train that provides transport capabilities between vehicle/train to ground or vice versa. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.4 Service flows | Multiple FRMCS Users starts communication, for example:
- ATP;
- ATO;
- Sensor information exchange. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.5 Post-conditions | FRMCS Users on the vehicle/train are able to communicate to FRMCS Users on the ground or to other vehicles/trains. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.20.6 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.20.6-001]
Multiple FRMCS Users in the vehicle/train shall be able to use one FRMCS Equipment simultaneously.
A/T
TS 22.280
TS 22.280 sub-clause 5.15
5.15-001
[R-12.20.6-002]
The service capabilities of an FRMCS Equipment shall be attributable individually to multiple FRMCS Users.
A/T
TS 22.280
TS 22.280 [R-5.15-002] & [R-5.15-003]
[R-12.20.6-003]
When an FRMCS Equipment is simultaneously used by multiple FRMCS Users, the communication for each of the FRMCS Users shall receive its required priority and QoS (latency and reliability) within the FRMCS System.
T
TS 22.280
TS 22.280 [R-5.15-003] [
[R-12.20.6-004]
When an FRMCS Equipment is simultaneously used by multiple FRMCS Users, each of the FRMCS Users shall be individually addressable.
A
TS 22.280
TS 22.280 [R-5.15-002] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21 FRMCS System/FRMCS User roaming capabilities | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.1 Introduction | FRMCS Roaming use cases address the ability for an FRMCS User to make use of FRMCS Applications when he is provided service by a network different from his Home FRMCS Network. A specific use case applies for FRMCS Functional Identities (see 12.21.3 use case).
It is essential for the operation of international trains, transporting passenger or freight across borders, that FRMCS Users are using the capabilities and services of other FRMCS networks.
The situations envisaged also encompass situations where trains are moving to an area where a dedicated FRMCS network has been deployed for an urban area, for a region, for a rail track operated by a different company in a tunnel, in a large industrial area.
Other cases are pertinent for rail operation such as trains running in countries or regions where communications services provided by the local responsible Rail Infrastructure Manager are different from the one where they have subscription or where service can only be provided by a Public Mobile Network Operator.
FRMCS Roaming capabilities are necessary to ensure that Railways Undertaking will be able to use a single FRMCS Equipment for their FRMCS Users while roaming. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2 Use case: FRMCS User is relocating towards a Visited (FRMCS) Network | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2.1 Description | This use case addresses the situation where an FRMCS User is moving beyond the coverage of its Home FRMCS Network and where communications services can be provided by another Visited (FRMCS) Network. Following scenarios for an FRMCS User are:
- Relocation from Home FRMCS Network to a Visited (FRMCS) Network and vice versa;
- Relocation from a Visited (FRMCS) Network to another Visited (FRMCS) Network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2.2 Pre-conditions | The Visited (FRMCS) Network is capable to retrieve FRMCS Users information from applicable Home FRMCS network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2.3 Service flows | FRMCS User is relocating from Home FRMCS Network to Visited (FRMCS) Network, or from a Visited (FRMCS) Network to another Visited (FRMCS) Network.
FRMCS User makes use of FRMCS Applications that are applicable in the Home FRMCS Network and the FRMCS Application that are applicable in the Visited (FRMCS) Network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2.4 Post-conditions | FRMCS User is able to use FRMCS Applications after relocating to a Visited (FRMCS) Network.
FRMCS User has not experienced service interruption of FRMCS Application while relocating. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.21.2-001]
The FRMCS System shall provide the technical means to allow communication services between FRMCS Users that are belonging to different administrative realms of the FRMCS System i.e. Home FRMCS Network and Visited (FRMCS) Network.
A/T
T TS 22.261
A TS 22.280
T sub-clause 5.1.2.1
T sub-clause 5.1.2.2
A sub-clause 6.17.2
[R-12.21.2-002]
The FRMCS System shall provide communication services to FRMCS Users visiting another administrative realm i.e. Visited (FRMCS) Network.
A/T
T TS 22.261
A TS 22.280
T sub-clause 5.1.2.1
T sub-clause 5.1.2.2
A sub-clause 6.17.2
[R-12.21.2-003]
The FRMCS System shall support a mechanism for an administrator to determine if a FRMCS User is able to use communication services in the Visited (FRMCS) Network.
A/T
T TS 22.261
A TS 22.280
T sub-clause 5.1.2.1
A sub-clause 6.17.2
[R-12.21.2-004]
The FRMCS System shall be able to provide service continuity when relocating between FRMCS Network without the FRMCS User noticing the change.
A/T
T TS 22.261
A TS 22.280
T sub-clause 6.18.2
A sub-clause 6.17.2
[R-12.21.2-005]
The FRMCS system shall be able to provide the same Quality of Service for the use of FRMCS Applications regardless of whether the FRMCS User is using the Home FRMCS Network or Visited (FRMCS) Network.
A/T
T TS 22.261
A TS 22.280
T sub-clause 5.1.2.1
A sub-clause 6.17.2 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3 Use case: Functional Identities in FRMCS Roaming situations | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3.1 Description | This use case addresses the situation where an FRMCS User or FRMCS Equipment is moving beyond the coverage of its Home FRMCS Network and where communications services can be provided by another Visited (FRMCS) Network.
An FRMCS User or FRMCS Equipment in FRMCS Roaming situations (referring to 12.21.2 use case) shall be able to make use of FRMCS Functional Identities, from its Home FRMCS Network and, when applicable, from Visited (FRMCS) Networks. For instance, an FRMCS User or FRMCS Equipment in a train can be registered to a permanent FRMCS Functional Identity with its Home FRMCS Network (associated with the engine), and an FRMCS Functional Identity registered with a Visited (FRMCS) Network. For train cross border operations (e.g. FRMCS Roaming situations), some registered FRMCS Functional Identities shall remain valid for the duration of the train international run, the same FRMCS Functional Identity keeping the same association to FRMCS Equipment while border crossing.
Each FRMCS Network shall maintain its own FRMCS Functional Identity addressing scheme. For the purpose of FRMCS roaming, an international FRMCS Functional Identity scheme will be used and national scheme will align on it. If a train (e.g. an FRMCS User) is involved in cross border operation, the FRMCS System shall detect automatically if an activated FRMCS Functional Identity requires a re-association to the local applicable addressing domain. The responsible local functional addressing entity in the Visiting (FRMCS) Network aligns the Home FRMCS Network functional addressing entity about FRMCS Functional Identity re-association. The activation status of the re-associated FRMCS Functional Identity will be aligned accordingly. The responsible entity of the functional address is keeping the status (active/inactive). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3.2 Pre-conditions | FRMCS User is registered to at least one FRMCS Functional Identity F1 with its Home FRMCS Network.
FRMCS Equipment is associated with a permanent Functional Identity administrated by the Home FRMCS Network.
The Visited (FRMCS) Network is capable to retrieve FRMCS Users information from applicable Home FRMCS network. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3.3 Service flows | FRMCS User is relocating from Home FRMCS Network to Visited (FRMCS) Network, or from a Visited (FRMCS) Network to another Visited (FRMCS) Network.
FRMCS Users and FRMCS Equipment register to at least one FRMCS Functional Identity F2 with the Visited (FRMCS) Network.
FRMCS User makes use of FRMCS Functional Identities associated with the Home FRMCS Network, at least F1, and the FRMCS Functional Identities associated with the Visited (FRMCS) Network, at least F2. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3.4 Post-conditions | An FRMCS User and FRMCS Equipment in FRMCS Roaming situations are able to use FRMCS Functional Identities associated with both Home FRMCS Network and Visited (FRMCS) Networks. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.21.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.21.3-001]
The FRMCS System shall be able to establish communication services based on FRMCS Functional Identity(ies) between FRMCS Users or FRMCS Equipment associated with different FRMCS Networks.
A/T
TS 22.280
For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]
Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a]
[R-12.21.3-002]
The FRMCS System shall be able to establish a communication services based on FRMCS Functional Identity(ies) associated with different FRMCS Networks.
A/T
TS 22.280
For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]
Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a]
[R-12.21.3-003]
The FRMCS System shall provide the necessary means for a FRMCS User or FRMCS Equipment to register and deregister FRMCS Functional Identity(ies) with the Home FRMCS Network and/or with the Visited (FRMCS) network.
A/T
TS 22.280
For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]
Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a]
[R-12.21.3-004]
When the FRMCS User or FRMCS Equipment is relocating between networks, the FRMCS System shall provide a mechanism to perform necessary registration/deregistration of one or multiple FRMCS Functional Identity(ies) with the Visited (FRMCS) Network operator and inform the Home FRMCS Network.
A/T
TS 22.280
For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]
Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22 Use case: Availability – increasing measures | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22.1 Description | In some regions railways are a major constituent for the economy. Disturbance in the complex railway system can have a significant impact for example in the manufacturing process if components cannot be delivered in-time. There are significant improvements in train punctuality and track utilisation by using Automatic Train Protection (ATP) systems. Unavailability of the FRMCS System, FRMCS sub-systems or simple components can cause a significant impact to railway operation.
ATP provides different levels of operation. The moving block mode is the most demanding one that requires multiple times more information in one second, e.g., position reports from the train towards the ground controlling entity which computes continuously the risk that consecutive trains can collide.
In order to minimise the risk of FRMCS System unavailability, Single Point of Failures (SPOF) need to be eliminated. There are different strategies such as duplication of components, subsystems or the entire system. The mode of system redundancy ranges from hot-standby, warm-standby to cold-standby. Hot-standby is the most demanding mode and requires an instantaneous continuation of the end-to-end service. Also the use of only one spectrum block represents a SPOF. In case one spectrum block become unavailable due to wideband jamming or similar, the FRMCS System needs to be able to make flexible use of spectrum to minimize the risk of radio path unavailability.
FRMCS System or sub-system maintenance may cause outages of some minutes or hours. Today, a high utilisation of rail tracks already reduces the number of maintenance windows. A redundant deployment of the radio access sub-system allows continuation of rail operation while one part of radio access sub-system is under maintenance. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22.2 Pre-conditions | The basis for setting up the FRMCS System takes into account the elimination of Single Point Of Failure which encompasses:
• Usage of multiple independent spectrum blocks;
• Duplication of system functionalities/entities of the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22.3 Service flows | Case 1:
During train control operation, some portion of the used spectrum block is disturbed, e.g., through interference from an external source.
Case 2:
During train control operation a FRMCS sub-system fails or has been put under maintenance. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22.4 Post-conditions | The communication service continues without interruption.
Train operation efficiency is not affected in any way despite the disturbances caused by:
• Interference (intentional or unintentional);
• Unavailability of FRMCS sub-systems due to planned (maintenance) or unplanned (outage) reasons. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.22.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.22-001]
The FRMCS System shall be able to provide a mechanism to allow redundancy of transmission paths making use of multiple spectrum blocks.
T
Covered in TS 22.261 chapter 7.2 by referring to TS 22.289
The reliability figures for rail is included in 22.289 (KPI for rail) and referenced in 22.261 sub-clause 7.2 on low latency and high reliability.
[R-12.22-002]
The FRMCS System shall provide a mechanism that minimizes the risk of single point of failure.
A/T
Covered in TS 22.261 chapter 7.2 by referring to TS 22.289
The reliability figures for rail is included in 22.289 (KPI for rail) and referenced in 22.261 sub-clause 7.2 on low latency and high reliability. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.