hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.4 Post-conditions | The communication is established to the FRMCS Equipment the FRMCS User has selected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.16.2-001]
The FRMCS System shall be able to provide communication to the FRMCS User based on the arbitration information associated with the communication.
A
TS 22.280 section 6.19.1
[R-9.16.2-002]
The FRMCS System shall be able to accept, reject, hold, queue or prompt the user for his choice on the incoming communication.
A
TS 22.280
Automatic arbitration in on-network mode: covered by requirements in section 6.19.1: MCX request to transmit are granted, rejected or queued (put on hold and queue are considered as similar mechanism).
Automatic arbitration in off-network mode: covered by requirements in section 7.3.2.
Manual arbitration (user selection) in on-network mode: accept and reject are covered by section 6.7.6. Mechanism to queue is not covered.
Manual arbitration (user selection) in off-network mode is not covered.
[R-9.16.2-003]
When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to establish the communication to the appropriate FRMCS Equipment, based on FRMCS User selected option.
A
TS 22.280
[R-6.7.2-005] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3 Use case: Arbitration for communication auto-connection | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.1 Description | The FRMCS System shall be able to automatically accept incoming communications without asking the FRMCS User, based on configuration (i.e., configured arbitration rules). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.2 Pre-conditions | The FRMCS System is authorised to perform arbitration on communication on the FRMCS Equipment (i.e., end user device). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.3 Service flows | FRMCS User is using a single FRMCS Equipment
When the communication is received by the FRMCS User on any of its identities (including registered functional identities), the FRMCS System automatically accepts the incoming private or group communication if arbitration rules are configured to do so.
FRMCS User is using multiple FRMCS Equipment simultaneously
If arbitration rules allow configuration for automatic answering and if an FRMCS User is logged in multiple FRMCS Equipment simultaneously, the FRMCS System automatically accepts the incoming private or group communication to the FRMCS User’s default FRMCS Equipment when the communication is received by the FRMCS User on any of its registered functional identities.
The FRMCS User’s default FRMCS Equipment is set up by either the FRMCS User or by the FRMCS System Administrator.
If the FRMCS System fails to automatically accept the incoming private or group communication to the FRMCS User’s default FRMCS Equipment, the FRMCS System automatically accepts the incoming private or group communication to another FRMCS Equipment the FRMCS User is logged in.
Arbitration rules
Arbitration rules allows configuration for automatic answering based on:
• The FRMCS User identities;
• The FRMCS User registered functional identities;
• The FRMCS Application identities;
• The FRMCS User’s default FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.4 Post-conditions | The incoming communication is automatically accepted to the relevant FRMCS Equipment the FRMCS User is logged in. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.16.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.16.3-001]
When an incoming private communication is received by the FRMCS User, the FRMCS System shall be able to automatically accept the communication if arbitration rules are configured to do so (based on FRMCS User identities, registered functional identities or FRMCS Application types).
A
22.280
Partly covered by private call setup in automatic commencement mode (request for automatic commencement mode – automatic answering – is trigerred by the calling party, not by the System).
In addition, configuration for automatic commencement mode is based on MC User ID only. Arbitration rules based on FRMCS Application types (i.e., MCPTT, MCData or MCVideo) is supported but not on Functional Alias(es).
Editor’s note: CR is needed.
[R-9.16.3-002]
When an incoming group communication is received by the FRMCS User, the FRMCS System shall be able to automatically accept the communication if arbitration rules are configured to do so (based on FRMCS User identities, registered functional identities or FRMCS Application types).
A
22.280
Covered by affiliation and functional alias mechanisms.
[R-9.16.3-003]
When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to automatically accept an incoming private communication to the default FRMCS Equipment.
A
22.280
Covered by 5.10 Support for multiple devices (i.e., multiple MCX UEs) and [R-6.7.2-005] default device designated by the receiving user.
Editor’s note on multiple devices support: default UE covered by stages 2&3? (didn’t find it)
[R-9.16.3-004]
The default FRMCS Equipment is configured by either the FRMCS User or by the FRMCS System Administrator.
A
22.280
5.10 Support for multiple devices (i.e., multiple MCX UEs) and [R-6.7.2-005] & [R-6.7.2-006]:
[R-9.16.3-005]
When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to automatically accept an incoming private communication to other FRMCS Equipment if communication to the default FRMCS Equipment fails to be established.
A
22.280
[R-6.7.2-006] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17 Data communication to exchange key information for train safety application use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.1 Introduction | In this chapter the use cases related to Key management communication are defined. The following use cases are defined:
• Initiation of a Key Management data communication
• Termination of a Key Management data communication
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2 Use case: Initiation of a Key Management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.1 Description | Key Management communication is the application which performs the functions that ensure the exchange of credentials/keys required by other applications (such as ATO, ATP) to ensure the correct authentication of the end users of each application and the integrity of the messages exchanged.
Some Key Management systems require radio communication to interchange the relevant data between a train and its corresponding key distribution centre (Key Management Center). This key distribution centre may be located in the same network or in an external network.
The users in this case are the Key Management applications both on-board of the train and in the key distribution centre at the trackside (ground system).
Key Management communication is considered to be user-to-user data communication.
The communication of keys may be requested each time that an ATP or ATO communication session is established or at any other time, depending on the specific configuration of the Key Management application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.2 Pre-conditions | The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the authorisation of communication application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.3 Service flows | The initiating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) initiates the Key Management data communication to the receiving side on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). The QoS profile of the communication is managed by the QoS Profile application. The data communication requests the QoS profile which matches the application category of CRITICAL DATA (see [QoS]) within the FRMCS system, depending on the application needs.
The FRMCS system establishes the bearer service required for the data communication within a setup time specified as IMMEDIATE (see [QoS]).
The arbitration is managed by the arbitration application on the FRMCS equipment.
The communication is recorded by the Data recording and access to recorded data application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.4 Post-conditions | The initiating application on the FRMCS equipment is connected to the receiving application.
Data can be exchanged between the Key Management applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.17.2.5-001]
For Key management communication, the communication shall be considered to be user-to-user data communication.
A
TS 22.282
TS 22.282
Sub-clause: 5.5
Note: Application Layer Key Management is transparent to the transport and communications services. Reference transport.
[R-9.17.2.5-002]
For Key management communication, the initiating and the receiving application on the FRMCS equipment shall be able to be authorised to initiate the Key management communication. This shall be managed by the authorisation of data communication application.
A
TS 22.280
TS 22.280
Sub-clause: 5.5, and 5.12.
Note: Application Layer Key Management is transparent to the transport and communications services.
[R-9.17.2.5.2-003]
For Key management communication, the initiating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) shall be able to initiate the Key Management data communication to the receiving side on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). The QoS profile of the communication shall be managed by the QoS Profile application. The data communication shall be able to request the QoS profile which matches the application category of CRITICAL DATA (see [QoS]) within the FRMCS system, depending on the application needs.
A
N/A
See sub-clause 12.10.
[R-9.17.2.5-004]
For Key management communication, the FRMCS system shall be able to establish the bearer service required for the data communication within a setup time specified as IMMEDIATE (see [QoS]).
A
N/A
See sub-clause 12.10.
[R-9.17.2.5-005]
For Key management communication, the arbitration shall be managed by the arbitration application on the FRMCS equipment.
A
TS 22.280
TS 22.280 Sub-clause: 6.4.7
[R-9.17.2.5-006]
For Key management communication, the communication shall be recorded by the recording and access to recorded data application.
A
TS 22.280
TS 22.280 sub-clause 6.15.4 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3 Use case: Termination of a Key Management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.1 Description | The initiating or the receiving application can terminate de Key Management data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.2 Pre-conditions | The Key Management applications on-board and trackside have a data communication initiated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.3 Service flows | The terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) terminates the Key Management data communication with the receiving side application on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train).
The FRMCS system terminates the bearer service required for the data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.4 Post-conditions | The terminating Key Management data application is disconnected from the receiving application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-9.17.3.5-001]
For Key management communication, the terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) shall be able to terminate the Key Management data communication with the receiving side application on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train).
A
TS 22.280
TS 22.280
Sub-clause: 5.5, and 5.12.
Note: Application Layer Key Management is transparent to the transport and communications services.
[R-9.17.3.5-002]
For Key management communication, the FRMCS system shall be able to terminate the bearer service required for the data communication.
A
TS 22.282
TS 22.282
Sub-clause: 5.5
Note: Application Layer Key Management is transparent to the transport and communications services. Reference transport. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4 Use case: service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.1 Description | For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS system for Key Management data communication needs to be clear.
Depending on the migration scenario a key distribution centre can be attached to the FRMCS system, to the GSM-R system or both. The on-board Key Management application can be attached either in the GSM-R system or in the FRMCS system. Functional identities are applicable in one system only.
This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
Online Key Management data exchange is supported only with a packet switched (PS) bearer in the GSM-R system. Therefore, for service interworking and service continuation only the PS bearer is required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.2 Pre-conditions | The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the authorisation of communication application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.3 Service flows | Initiating Key Management application attached to GSM-R
When the initiating Key Management application on the FRMCS equipment is attached to the GSM-R system and is initiating data communication to another Key Management application, the GSM-R system will route the data communication accordingly.
If the other Key Management application on the FRMCS equipment is attached to the FRMCS system, the GSM-R system can only route the data communication if the destination can be reached by an address or identity understood by the GSM-R system. The role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the role management and presence application is used to route the communication and to present the identities.
Initiating Key Management application attached to FRMCS
When the initiating Key Management application on the FRMCS equipment is attached to the FRMCS system and is initiating data communication to another Key Management application, the FRMCS system will route the communication accordingly.
If the other Key Management application on the FRMCS equipment is attached to the GSM-R system, the FRMCS system can only route the data communication if the destination can be reached by an address or identity understood by the FRMCS system. The role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
The information from the role management and presence application is used to route the communication and to present the identities.
Key Management application moving from GSM-R to FRMCS
When the Key Management application on the FRMCS equipment is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS system. An interruption of data communication is acceptable.
Key Management application moving from FRMCS to GSM-R
When the Key Management application on the FRMCS equipment is detached from the FRMCS system, the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of data communication is acceptable. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 9.17.4.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 10 Performance support applications related use cases | Editor’s Note: Text to be provided. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11 Business support applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1 Charging and Billing information related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.1 Introduction | In this chapter the use cases related to charging and billing are defined. The following use cases are defined:
- Obtaining charging and billing information |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2 Use case: Obtaining charging and billing information | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.1 Description | The Railway operators may have the obligation or the desire to charge FRMCS Users of their FRMCS Networks, or to use billing information for statistical reasons.
An entitled FRMCS User shall be able to obtain information for any type of FRMCS communications from the FRMCS system, to be able to generate bills. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.2 Pre-conditions | An entitled FRMCS User is logged on to the FRMCS system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.3 Service flows | The entitled FRMCS User requests billing information for a single FRMCS User or a group of FRMCS Users.
The entitled FRMCS User selects defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Identity) to get more detailed results.
The entitled FRMCS User configures the FRMCS system to generate the billing information once or periodically. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.4 Post-conditions | The requested billing information is generated from the FRMCS System. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 11.1.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-11.1.2-001]
The FRMS System shall be able to generate charging records for one or multiple FRMCS Users based on defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Identity).
A/T
Partly covered (only CDR covered by 3GPP – billing system outside the 3GPP domain).
6.15.4
[R-11.1.2-002]
The FRMCS System shall allow to charge separately for each type of FRMCS Application and/or each type of application category.
A/T
TS 22.261 section 9.2
Support collection of charging information based on resource usage (e.g. QoS, applications).
[R-11.1.2-003]
The FRMCS System shall allow to charge for different Service Attributes.
A/T
TS 22.261 section 9.2
Support collection of charging information based on resource usage (e.g. QoS, applications). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12 FRMCS System principles related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.1 FRMCS System principles overview | In this chapter, FRMCS System related use cases are described which are complying with principles such as:
- Provide broadband and/or mission critical services with seamless connectivity
- Offer high-quality control functions and real-time performance monitoring
- Interworking with legacy systems including GSM-R and LMR
- Build stable positioning framework for FRMCS services and devices including trainborne (in-train) and handheld (in-train, and in/out-door) UEs
- Bearer flexibility
- QoS in a railway environment
- FRMCS System security framework
To describe the use cases, an example system is assumed by adapting LTE for railway communication [4] as follows:
Figure 12.1-1. An example system for FRMCS System principle use cases
The example system is consisted of the train control centre, 3GPP network such as LTE with UE and the trainborne UE. The backbone network connects the train control centre, 3GPP network and legacy systems. FRMCS System is interworking with the legacy systems such as GSM-R and TRS. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.2 Area Broadcast Group Communication interworking between GSM-R and FRMCS Users | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.2.1 Description | This use case describes an area broadcast group communication between FRMCS User(s) and GSM-R User(s), and vice versa.
12.2.2 Pre-condition
FRMCS User A and GSM-R User B and User C are authorized Users to perform group communication together by the FRMCS System.
User A and User B and User C are in the same group communication area defined by the FRMCS System. |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.