hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23 Use case: Flexible use of available contiguous spectrum blocks(s) and related bandwidth(s) | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.1 Introduction | Globally, different contiguous spectrum block(s) with related bandwidth(s) may be available for rail communication in different areas. An FRMCS Equipment may also support different contiguous spectrum block(s) with related bandwidth(s) than the infrastructure deployed in the area. The use case addresses the general requirements related to the ability of the FRMCS System to flexibly use the maximum extent of rail spectrum available in an area, also considering the capabilities of the FRMCS Equipment that is served. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.2 Description | It is essential that the FRMCS system can flexibly utilize the available bandwidth of the contiguous spectrum block(s), for both On-network and Off-network communication, also considering the contiguous spectrum block(s) and related bandwidth(s) supported by served FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.3 Pre-conditions | In certain areas, specific contiguous spectrum block(s) and related bandwidth(s) are available for rail communication. An FRMCS Equipment served in the area supports (possibly different) specific contiguous spectrum block(s) and their related bandwidth(s). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.4 Service flows | The FRMCS System obtains information about the specific contiguous spectrum block(s) and their related bandwidth(s) supported by the FRMCS Equipment.
The FRMCS System allocates the locally available contiguous spectrum block(s) and their related bandwidth(s), and serves FRMCS Equipment according to its supported contiguous spectrum block(s) and their related bandwidth(s). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.5 Post-conditions | The FRMCS System is able to flexibly use the maximum extent of rail spectrum available in a given area, also considering the capabilities of the FRMCS Equipment that is served. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.23.6 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-12.23-001]
The FRMCS System shall be able to support for individual contiguous spectrum blocks, bandwidths less than 5 MHz (e.g. 1.4 MHz or 3 MHz).
T
N/A
Covered by RAN specifications:
• Covered by E-UTRA,
• Not covered by NR. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 13 Potential New Requirements | This chapter lists the potential new requirements that have been considered for introduction in Rel-15 normative specifications. Only parts of “9.3 Role management and presence” and “9.7 Multiuser talker control related use cases” were introduced. All other requirements identified in the TR above but not listed below are not covered in Rel-15.
The third column “SA1 spec covering” identifies the specification and the requirement number within that specification where the 22.889 requirement with the number as specified in the first column of the table is covered. The fourth column provide additional explanation if needed. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 14 Conclusion and Recommendations | This TR provides use cases and potential requirements for Railway Communication. It is proposed to start normative work based on these potential requirements. Where applicable, it is proposed to include the requirements identified by this work into the set of existing stage 1 missing critical and other specifications. Requirements not fitting to any existing specification are proposed to go into a new TS. Annex A: Examples of Role management This annex gives some examples on how Role management is used in the railway environment. This is to better understand the use. Functional identity Every operational railway function e.g. train driver, a shunter or Controller is identified by their functions. A non-exhaustive list is provided in the table underneath. Functional identities Leading train driver Driver 2 Driver 3 Shunting leader Shunting member Track side maintenance leader Track side maintenance member Primary train controller Secondary train controller Power controller Shunting controller Trackside maintenance controller Platform inspector Public announcement Chief conductor Second conductor Third conductor Catering staff chief Diagnostics In order to make a function of a user known to other users, the user has to register itself to a specific functional identity. For example, user can be authorised by the railway undertaking to be a train driver (functional Role) of a train. When the Driver starts the scheduled train ride, from A to B at time x, the train running schedule assigns a specific train running number for this train. In principle the train keeps this number for the complete journey. The train driver uses his communication equipment to register himself, as the leading train driver (functional Role), of train number 123 (functional identity). After registration the train driver is now registered to the FRMCS System as the leading train driver of train 123. In some cases there can be multiple Drivers on one train, so the individual Drivers can register themselves accordingly. FRMCS Equipment Type The equipment used in the railway environment can be very specific. The FRMCS Equipment is constituted of an UE and the FRMCS Application on this UE. This depends on the location and situation the equipment is used. The following different equipment types can be used, as an example: Equipment type Equipment Capabilities (Examples) Cabin radio Emergency button, external loudspeaker Shunting radio Loudspeaker, hands free Trackside maintenance radio Security staff radio Emergency button, public emergency call button Catering staff radio Train controller device Emergency button, call to maintenance staff button, call to power controllers button Shunting controller device Sensor No HMI These different types of FRMCS Equipment are relevant for the registration process of functional identities. For example a train driver cannot register to a functional identity using a FRMCS Equipment which is not fit for the train driver to perform his Role. So a train driver cannot perform a registration as train driver of train 123 if he uses a catering staff FRMCS Equipment (where there is no train emergency button available, no loudspeaker and handset, etc.). The registration request will be rejected by the FRMCS System. The FRMCS Equipment shall also be reachable based on the identity of the FRMCS Equipment. For example the cabin radio of a specific train can be reached by their FRMCS Equipment Identity. FRMCS User identity The railway employee (a specific person) is also reachable even if no functional identity has been assigned. This is done by using a unique FRMCS User identity. This can be an E.164 number, any other number according to a specific railways numbering plan or by fully qualified domain names (FQDN). Such a number or FQDN is dedicated/ assigned to a specific railway employee. After the employee has performed the log-in procedure to the FRMCS System, he is reachable via his individual FRMCS User identity. Annex B: Minimum functional and performance requirements for FRMCS from a perspective of Korea LTE-based railway services In this annex, minimum functional and performance requirements [5]-[6] are introduced for FRMCS from a perspective of Korea's LTE-based railway services. Here, the term ‘minimum’ is used from the fact that the requirements are expected to be satisfied even with previous Rel. version of 3GPP LTE. Specifically, all the functionalities and performance requirements except for the high speed (500km/h) listed in the above have been shown to be fully supported by LTE Rel. 9, which have been validated in a commercial railway with a length of 54.2km [7]. Also, train control service named as Korea Radio-Based Train Control System (KRTCS) has been shown to be feasible by handling priorities among multiple data, where the level of KRTCS is equivalent to European Train Control System (ETCS) level 3 in a train control perspective. All the specific test scenarios regarding functional and performance requirements including KRTCS have been validated in a commercial railway [8]. For promising FRMCS supporting LTE Rel. 15, more enhanced and sophisticated requirements should be provided. In that sense, these requirements can be considered as basic functional and performance requirements for FRMCS. Minimum functional requirements In a communication perspective, the followings can be minimum functional requirements for LTE based railway communication systems. The contents of each function and each digital radio equipment are described in detail in [5]-[6]. Service Detailed service Description Mandatory/Optional (M/O) Voice service Individual voice call The system shall support voice calling between two callers. M Public emergency call The system shall allow the user to make a public emergency call. M Broadcasting voice call The system shall support a broadcasting call. M Group voice call The system shall support a group call. M Multi-party voice call The system shall support a multi-party call between at least 3 different parties. M Data service Multimedia message service The network shall support point-to-point and point-to-multi-point message transmission from the ground to mobile radio equipment users. M General data service The system shall support broadband data communication between ground and mobile radio equipment users. M Train control service The system shall support seamless data communication for stable train control. M Video service Individual video call The system shall support video calling between two callers. M Group video call The system shall support group video calling. M Video information transmission The system shall support the video information transmission function related to safe train operation. M Call related service Receiver /Caller ID display The equipment shall display the receiver or caller ID in the form of a standard telephone number. M Receiver /caller ID display restriction The system shall allow the ID of a specific user to be prevented from being displayed on the mobile radio equipment. O Priority and preemptive right A function in which a call is allocated to the member who has top priority among the members who have different priority levels shall be provided. M Closed user group The user group who can access the Korean railway integrated radio network from outside shall be restricted. M Call transfer The incoming call or data message for one user shall be transferred to other devices in the network. M Call holding The network shall allow the user to hold a call temporarily from an existing call. M Call waiting The network shall be able to notify the user of the existing call that another user is attempting to access. M Charging information When there is a network service charge, the network shall be able to provide the information on call charge and ongoing call charges. O Call restriction The system shall be able to restrict a call using the network management or maintenance facility. M Automatic answering service A call shall be answered automatically according to the priority of an incoming call. M All voice/ Video call recording A call shall be answered automatically according to the priority of an incoming call. M Railway specialized service Functional addressing The system shall provide the addressing system in which the Controller can set communication with the train driver using train number M Location-dependent addressing The system shall provide the location-dependent addressing system in order to identify the destination number, which varies depending on the location of users M Railway emergency call The network shall provide the system to handle a voice call with high priority for a railway emergency call M Shunting mode The network shall provide the system to regulate and control the user’s access to the function and features of mobile radio equipment being used for shunting mode communication M Direct communication The system shall support direct communication between terminals in the event that an LTE-based railway communication service is not normally available due to a failure in eNb. O Minimum performance requirements In the following table, specific performance requirements are listed as a base line of performance requirements for real FRMCS. The detailed performance of a railway communications system and the contents of the interface for each equipment are described in detail in [5]-[6]. Items Description Remarks Coverage and performance Coverage shall be continuous from a time and space perspective, and the temporal and spatial range to guarantee stability shall be more than 98% based on the vehicle being equipped with an external antenna. The network shall be able to accommodate the mobile terminal for railway communication. The system shall be able to provide communication when moving at track speed limit or 500 km/h, whichever is lower. Call setting time Railway emergency call < 1s (90%), < 2s (99% or more) Broadcasting or group call < 1s (90%), < 2.5s (99% or more) All voice/video calls that do not correspond to the above < 3.5s (90%), < 5s (99% or more) * External PSTN connection not considered Handover success The network shall be able to have seamless data transmission, and the handover success rate shall be 99% or more. Call access success The call access success rate shall be 99% or more. Connection drop rate The system shall be able to guarantee a call disconnection rate less than 0.01 times per hour during a lengthy call Train control data transmission The network shall guarantee more than 99% data reliability to transmit data for train control. Train control data shall have top priority. Network redundancy The network including eNb equipment, core equipment and server shall be designed to be redundant for stability and availability. However, the application scope of redundancy is determined by the operator. Broadcasting and group call area Radio equipment in a restricted area can participate in broadcasting and group call, and the radio equipment out of broadcasting and group call area during call shall be excluded from call. Annex C: Applicability to On-network/Off-network communication The different types of communication and support applications related to On-Network and Off-Network are covered by the table below: Section Use case Applicability to On-Network Applicability to Off-Network 5.3 Power on the UE Yes Not applicable 5.4 Access to the FRMCS System to activate the FRMCS Equipment Yes Not applicable 5.5 Controlled power down of UE Yes Not applicable 5.6 Uncontrolled power down UE Yes Not applicable 6.2 Multi-train voice communication for Drivers and Ground FRMCS User(s) Yes Yes 6.3 On-train outgoing voice communication from the Driver towards the Controller(s) of the train Yes No 6.4 Railway emergency communication Yes No 6.5 Automatic Train Protection (ATP) support by the FRMCS System Yes No 6.6 Trackside Maintenance Warning System communication 6.6.2 6.6.3 Yes Yes Yes Yes 6.7 Pushed Real Time Video streaming Yes No 6.8 Public emergency call Yes No 6.9 Data communication for possession management Yes No 6.10 Recording of communication 6.10.2 Yes Yes 6.11 Remote control of engines communication 6.11.2 Yes Yes 6.12 Automatic Train Operation data communication 6.12.3 Yes Yes 6.13 Monitoring and control of critical infrastructure Yes No 6.14 Data transmission in real time Yes No 6.15 On-train incoming voice or video communication from the Controller(s) of the train towards the drivers Yes No 6.16 Data communication for Train Operation System Communication 6.16.2 6.16.3 6.16.4 Yes Yes Yes No Yes Yes 6.17 On-train safety device to ground communication Yes No 6.18 Train Integrity monitoring data communication 6.18.2 Yes Yes 6.19 Broadcast of public emergency warning information Yes No 6.20 Safety related Critical advisory messaging 6.20.2 6.20.3 Yes Yes Yes No 6.21 Automatic Train Protection data communication Yes No 6.22 Voice communication transfer Yes No 7.1 Transmission of real time video Yes No 7.2 Transfer of CCTV archives Yes No 7.3 Massive Inter-carriage data transfer Yes Yes 7.5 On-train outgoing voice communication from train staff towards a ground user Yes No 8.2 Live streaming of multimedia Yes Yes 8.3 Bulk transfer of multimedia from ground to train Yes Yes 9.2 Assured voice communication (AVC) 9.2.2 9.2.3 9.2.4 9.2.5 Yes Yes Yes Yes Yes Yes Yes Yes 9.3 Functional identities and role management 9.3.3 9.3.4 9.3.5 9.3.6 9.3.7 9.3.8 9.3.9 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No 9.4 Location services 9.4.2 9.4.3 9.4.4 Yes Yes Yes Yes Yes Yes 9.5 FRMCS-user communication handling 9.5.2 9.5.3 9.5.4 9.5.5 9.5.6 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 9.7 Multiuser talker control 9.7.2 9.7.3 9.7.4 9.7.5 9.7.6 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 9.8.1 Robust mission critical group communications Yes Yes 9.8 Authorisation of communication 9.8.2 Yes Yes 9.9 Authorisation of application 9.9.2 9.9.1 Yes Yes Yes1 Yes 9.10 Sharing FRMCS Equipment by FRMCS Users Yes Yes 9.11 FRMCS naming authority Yes No 9.12 Wayside-Centric Automatic Train Control Yes No 9.13 Autonomous Train Control and Operation Yes Yes 9.14 Virtual Coupling Yes Yes 9.15 Composite-based train operation Yes Yes 9.16 Arbitration 9.16.2 Yes Yes 9.17 Data communication to exchange key information for train safety application Yes No 11.1 Charging and Billing information Yes No Table C-1. Applicability to On-network/Off-network to use cases. Annex D: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2020-09 SA#89 - - - - Created from TR 22.889, same technical content as TR 22.889 v.17.3.0 18.0.0 2021-03 SA#91e SP-210200 0001 1 D Align TR with SA1 drafting rules on Inclusive Language 18.1.0 2021-03 SA#91e SP-210223 0002 1 C Changes to Critical Support Applications “Inviting-a-FRMCS User to a voice communication” use case 18.1.0 2021-03 SA#91e SP-210223 0003 1 C Merging of Railway Emergency Communications 18.1.0 2021-09 SA#93e SP-211049 0004 1 C Changes to Critical Support Applications Inviting-a-FRMCS User to a voice communication use case to support Interworking with GSM-R 18.2.0 2021-09 SA#93e SP-211049 0006 1 C Changes to Critical Support Applications Multiuser talker control use case to support configurable initial talker permission 18.2.0 2021-12 SP-94 SP-211489 0008 2 C Triggering a change of communication privileges for a particular FRMCS User based on identities and/or talker status 18.3.0 2021-12 SP-94 SP-211489 0009 C Arbitration: automatic answer 18.3.0 2021-12 SP-94 SP-211489 0010 2 C Alignment between Changing conditions of Railway Emergency Alert and Merging Railway Emergency Alert 18.3.0 2021-12 SP-94 SP-211489 0011 C Service interworking between FRMCS and GSM-R of presence is no more required 18.3.0 2022-03 SP#95e SP-220079 0012 1 B Adding MCX Service Ad hoc Group Communication as alternative capability to support Railway Emergency Communication 18.4.0 2022-06 SA#96 SP-220430 15 1 F Call restriction based on subparts of functional identities 18.5.0 2022-06 SA#96 SP-220431 13 1 B Virtual Coupling data communication use case 19.0.0 2022-06 SA#96 SP-220431 14 1 B Real-time automatic translation of languages related use cases 19.0.0 2022-09 SA#97 SP-220934 16 1 C Enhancement and clean-up of Railway Emergency Communication related use cases 19.1.0 2022-09 SA#97 SP-220934 17 1 B Public Train Emergency Communication related use cases 19.1.0 2022-09 SA#97 SP-220934 18 1 B Railway staff Emergency Communication related use cases 19.1.0 2022-12 SA#98 SP-221261 0019 2 C Enhancement of Multi-train voice communication for Drivers and Ground FRMCS User(s) related use cases 19.2.0 2022-12 SA#98 SP-221261 0020 3 C Enhancement of Multiuser talker control related use cases 19.2.0 2022-12 SA#98 SP-221261 0021 3 C Update of QoS in a railway environment Use Case 19.2.0 2022-12 SA#98 SP-221261 0022 3 C Enhancement of Railway Emergency Communication 19.2.0 2022-12 SA#98 SP-221261 0023 3 C Enhancement of FRMCS naming authority use case 19.2.0 2023-06 SA#100 SP-230528 0024 1 D Introduction and updates of Smart railway definitions 19.3.0 2023-06 SA#100 SP-230528 0026 1 F Clean-up of Railway Emergency Communication related use cases 19.3.0 2023-06 SA#100 SP-230528 0027 3 B Transportation convenience service for the passengers for the reduced mobility 19.3.0 2023-06 SA#100 SP-230528 0028 3 B Multiple concurrent mobility services 19.3.0 2023-09 SA#101 SP-231021 0029 1 F Update of gap analysis of railway emergency alert, multi-talker control, authorisation of communication, arbitration use cases 19.4.0 |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 1 Scope | The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. The present document defines the necessary procedures.
The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
Procedures for supporting these functions are defined in 3GPP TS 29.002 [6] and 3GPP TS 29.060 [8].
The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
The GGSN (Gateway GPRS Support Node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart are described in this document.
The SGSN (Serving GPRS Support Node) is the node that is serving the MS. The SGSN stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
The MME (Mobility Management Entity) is the node that is serving the UE when attached to E-UTRAN. The MME stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this MME information after a restart are described in this document.
A Type A LMU (Location Measurement Unit) is a network node, accessed over the GSM air interface, that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU except where specified otherwise. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary of 3GPP Specifications ".
[2] Void
[3] Void
[4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[6] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[7] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification".
[8] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunneling Protocol (GTP) across the Gn and Gp interface".
[9] 3GPP TS 43.005: "Technical performance objectives".
[10] 3GPP TS 23.071: " Location Services (LCS); Functional description; Stage 2".
[11] Void
[12] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[13] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[14] 3GPP TS 29.118:"Mobility Management Entity (MME) – Visitor Location Register (VLR) SGs interface specification".
[15] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[16] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunneling protocols; Stage 3".
[17] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunneling Protocol User Plane (GTPv1-U)".
[18] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[19] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[20] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[21] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping ".
[22] IETF RFC 5847: "Heartbeat Mechanism for Proxy Mobile IPv6".
[23] 3GPP TS 23.018: "Basic call handling; Technical realization".
[24] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[25] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[26] IETF RFC 7077: "Update Notifications for Proxy Mobile IPv6".
[27] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[28] 3GPP TS 36.444: "EUTRAN M3 Application Protocol (M3AP)".
[29] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".
[30] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[31] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ".
[32] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[33] 3GPP TS 23.303: "Proximity based Services; Stage 2".
[34] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects; Stage 3".
[35] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[36] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[37] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3".
[38] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[39] 3GPP TS 23.161: "Network-Based IP Flow Mobility (NBIFOM); Stage 2".
[40] 3GPP TS 23.285: "Architecture enhancements for V2X services; Stage 2".
[41] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)". .
[42] 3GPP TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2".
[43] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; stage 3".
[44] 3GPP TS 29.674:" Interface between the UCMF and the MME; Stage 3".
[45] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[46] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[47] 3GPP TS 23.632: "User data interworking, coexistence and migration; Stage 2". |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 1.2 Abbreviations | For the purposes of the present document, the abbreviations listed in 3GPP TR 21. 905 [1] apply. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 1.3 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
PDN Connection: "PDN Connection" in this specification only refers to the PDN connection through the SGW and PGW.
SCEF PDN Connection: The PDN connection to the SCEF. Unless otherwise indicated in a clause or clause, "PDN Connections" do not refer to any SCEF PDN Connection. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 2 Design objectives | To avoid loss of all the data stored in a location register when part of the equipment of the location register fails, a regime must be implemented to secure the data. This regime can include replication of volatile storage units and periodic back-up of data to non-volatile storage. If the data security regime ensures the integrity of the data in spite of failure of part of the location register equipment then there will be no impact on service. This Technical Specification describes the procedures to be used when the integrity of data in the location register cannot be ensured; that situation is referred to below as "failure".
The VLR and SGSN shall erase all IMSI records affected by the failure when it restarts after a failure. The GGSN shall erase all non-static PDP records affected by the failure and restore static PDP records when it restarts after a failure.
For the HLR/HSS or CSS, periodic back-up of data to non-volatile storage is mandatory.
The reliability objectives of location registration are listed in 3GPP TS 43.005 [9].
The MME, S-GW and P-GW must similarly have a regime to secure the PDN connection and bearer data at failures. When an MME, SGW or PGW has a full node restart or fails all PDN connections and bearer records associated with the failing node shall be erased and any internal resources released.
Clause 18 "GTP-C based restart procedures" specifies how a GTP-C entity restart is detected and handled by the peer. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3 Restoration indicators in location registers and in GPRS support nodes | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.1 Restoration Indicators in the VLR | Three restoration indicators are provided in the VLR for each IMSI record: "Confirmed by Radio Contact", "Subscriber Data Confirmed by HLR" and "Location Information Confirmed in HLR".
The indicator "Confirmed by Radio Contact" indicates whether the VLR"s record of location area identity and MSC number for the mobile station is confirmed by radio contact.
The indicator "Confirmed by Radio Contact" in an IMSI record is set to the initial value "Not Confirmed" when the VLR receives a "Provide Roaming Number" request, an "Update Location Area" request or an "IMSI Attach" request for an MS for which the VLR does not have an IMSI record. The indicator "Confirmed by Radio Contact" in an IMSI record may also be set to the initial value "Not Confirmed" when the VLR receives a Reset indication message from the SGSN serving the MS if the MS is attached to both GPRS and non-GPRS services (see 3GPP TS 29.018 [7]) , or a Reset indication message from the MME serving the UE if the UE is attached to both EPS and non-EPS services or for SMS only (see 3GPP TS 29.118 [14]).
The indicator "Confirmed by Radio Contact" is set to "Confirmed" when the radio contact that has been established with the MS is authenticated.
The indicator "Subscriber Data Confirmed by HLR" indicates whether the subscriber data set for the mobile station held by the VLR is consistent with that held by the HLR.
The indicator "Subscriber Data Confirmed by HLR" is set to the initial value "Not Confirmed" when the VLR receives a "Provide Roaming Number" request, an "Update Location Area" request or an "IMSI Attach" request for an MS for which the VLR does not have an IMSI record.
The indicator "Subscriber Data Confirmed by HLR" is set to "Confirmed" at either of the following events:
- The VLR successfully performs an "Update Location" to the HLR;
- The VLR successfully performs a "Restore Data" operation to the HLR.
The indicator "Location Information Confirmed in HLR" indicates whether the HLR's record of VLR number and MSC number for the mobile station is confirmed by radio contact.
The indicator "Location Information Confirmed in HLR" is set to "Not Confirmed" at any of the following events:
- The VLR receives an "Update Location Area" request or an IMSI Attach" request for an MS for which the VLR has no IMSI record;
- A VLR which serves two or more MSCs receives a "Provide Roaming Number" request for an MS for which the VLR has no IMSI record;
- The VLR receives a "Reset" message from the HLR with which the MS is registered;
- The VLR in a Super-Charged network receives a Send Identification message from the serving VLR;
- The VLR in a Super-Charged network receives a Cancel Location message that indicates an "updateProcedure".
The indicator "Location Information Confirmed in HLR" is set to "Confirmed" at either of the following events:
- A VLR which serves only one MSC receives a "Provide Roaming Number" request for an MS for which the VLR has no IMSI record;
- Successful completion of the "Update Location" procedure triggered by authenticated radio contact.
The indicator "Location Information Confirmed in SMLC" indicates whether an SMLC's record of MSC number for a particular LMU is confirmed by radio contact.
The indicator "Location Information Confirmed in SMLC" is set to "Not Confirmed" at any of the following events:
- The VLR receives an "Update Location Area" request or an "IMSI Attach" request for an MS for which the VLR has no IMSI record. The indicator, in this case, becomes valid only if HLR subscriber data later indicates an LMU;
- The VLR receives an "LCS Reset" message from an SMLC where the message is targetted to either a specific LMU or all LMUs registered with the SMLC;
- The VLR receives an "IMSI Detach" from an LMU that is registered with an SMLC.
The indicator "Location Information Confirmed in SMLC" is set to "Confirmed" at the following event:
- Successful completion of the "LCS Registration" procedure triggered by a successful location update;
- Successful transfer of an LCS Information message from an SMLC to the LMU.
Also the following two restoration indicators may be provided in the VLR for each IMSI record: "Subscriber Data Confirmed by CSS" and "Location Information Confirmed by CSS".
The indicator "Subscriber Data Confirmed by CSS" indicates whether the CSG subscriber data set for the roaming mobile station held by the VLR is consistent with that held by the CSS.
The indicator "Subscriber Data Confirmed by CSS" is set to the initial value "Not Confirmed" at the following event:
- The VLR receives a "Provide Roaming Number" request, an "Update Location Area" request or an "IMSI Attach" request for a roaming MS for which the VLR does not have an IMSI record.
- The VLR receives a "Cancel VCSG Location Request" message from the CSS after the VLR restart if the roaming MS attached to the macro cell after the VLR restart.The indicator "Subscriber Data Confirmed by CSS" is set to "Confirmed" at the following event:
- The VLR successfully performs an "Update VCSG Location" to the CSS.
- The VLR receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the VLR restart if the roaming MS attached to the macro cell after the VLR restart.
The indicator "Location Information Confirmed by CSS" indicates whether the VLR number for the roaming mobile station registered is confirmed by the CSS.
The indicator "Location Information Confirmed by CSS" is set to "Not Confirmed" at any of the following events:
- The VLR receives an "Update Location Area" request or an "IMSI Attach" request for a roaming MS for which the VLR has no IMSI record;
- The VLR receives a "Reset" message from the CSS with which the roaming MS is registered.
- The VLR receives a "Cancel VCSG Location Request" message from the CSS after the VLR restart if the roaming MS attached to the macro cell after the VLR restart.
The indicator "Location Information Confirmed by CSS" is set to "Confirmed" at the following event:
- Successful completion of the "Update VCSG Location" procedure to the CSS.
- The VLR receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the VLR restart if the roaming MS attached to the macro cell after the VLR restart. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.2 Restoration Indicators in the HLR | As an implementation option, one restoration indicator may be provided in the HLR for each IMSI record: "Check SS".
The "Check SS" indicator is set to "Check Required" when the HLR restarts after a failure.
The "Check SS" indicator is checked whenever the HLR receives an "Update Location" request from a VLR. If it is set to "Check Required", after successful completion of subscriber data retrieval that ran embedded in the "Update Location" procedure the HLR sends a "Forward Check SS Indication" request message to the VLR and sets the "Check SS" indicator to "Check Not Required". |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.3 Restoration Indicators in the SGSN | Two restoration indicators are provided in the SGSN for reach IMSI record: "Subscriber Data Confirmed by HLR" and "Location Information Confirmed in HLR".
The indicator "Subscriber Data Confirmed by HLR" indicates whether the subscriber data set for the mobile station held by the SGSN is consistent with that held by the HLR.
The indicator "Subscriber Data Confirmed by HLR" is set to the initial value "Not Confirmed" when the SGSN receives a Routing Area Update request or an IMSI- and/or GPRS Attach request for an MS for which the SGSN does not have an IMSI record.
The indicator "Subscriber Data Confirmed by HLR" is set to "Confirmed" at the following event:
- The SGSN successfully performs an Update GPRS Location to the HLR;
The indicator "Location Information Confirmed in HLR" indicates whether the HLRs record of the SGSN address for the mobile station is confirmed by radio contact.
The indicator "Location Information Confirmed in HLR" is set to "Not Confirmed" at any of the following events:
- The SGSN receives a Routing Area Update request or an IMSI- and/or GPRS Attach request for an MS for which the SGSN has no IMSI record;
- The SGSN receives a "Reset" message from the HLR with which the MS is registered;
- The SGSN in a Super-Charged network receives a Send Identification message from the serving SGSN;
- The SGSN in a Super-Charged network receives a Cancel Location message that indicates an "updateProcedure".
The indicator "Location Information Confirmed in HLR" is set to "Confirmed" at the following event:
- Successful completion of the Update GPRS Location procedure to the HLR.
The indicator "VLR-Reliable" indicates whether the VLR serving the MS has performed a restart.
The indicator "VLR-Reliable" is set to the value "false" when the SGSN receives a Reset indication message from the VLR serving the MS if the MS is attached to both GPRS and non-GPRS services. The indicator "VLR-Reliable" is set to the value "true" when the SGSN receives a confirmation from a VLR that a location update procedure to the affected VLR has been successfully performed.
The indicator "SGSN-Reset" indicates whether the SGSN has recently experienced a restart.
The indicator "SGSN-Reset" is set to the value "true" when the SGSN suffers a restart. This indicator is unique per SGSN. The indicator "SGSN-Reset" is set to the value "false" after a certain time specified by the operator. The value of the timer controlling the reset of the "SGSN-Reset" indicator shall be longer than the periodic routeing area update timer value used by the MSs.
Also the following two restoration indicators may be provided in the SGSN for each IMSI record: "Subscriber Data Confirmed by CSS" and "Location Information Confirmed by CSS".
The indicator "Subscriber Data Confirmed by CSS" indicates whether the CSG subscriber data set for the roaming mobile station held by the SGSN is consistent with that held by the CSS.
The indicator "Subscriber Data Confirmed by CSS" is set to the initial value "Not Confirmed" at any of the following events:
- The SGSN receives a Routing Area Update request or an IMSI- and/or GPRS Attach request for a roaming MS for which the SGSN does not have an IMSI record.
- The SGSN receives a "Cancel VCSG Location Request" message from the CSS after the SGSN restart if the roaming MS attached to the macro cell after the SGSN restart.
The indicator "Subscriber Data Confirmed by CSS" is set to "Confirmed" at the following event:
- The SGSN successfully performs an "Update VCSG Location" to the CSS.
- The SGSN receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the SGSN restart if the roaming MS attached to the macro cell after the SGSN restart.
The indicator "Location Information Confirmed by CSS" indicates whether the SGSN address for the roaming mobile station registered is confirmed by the CSS.
The indicator "Location Information Confirmed by CSS" is set to "Not Confirmed" at any of the following events:
- The SGSN receives a Routing Area Update request or an IMSI- and/or GPRS Attach request for a roaming MS for which the SGSN has no IMSI record;
- The SGSN receives a "Reset" message from the CSS with which the roaming MS is registered.
- The SGSN receives a "Cancel VCSG Location Request" message from the CSS after the SGSN restart if the roaming MS attached to the macro cell after the SGSN restart.The indicator "Location Information Confirmed by CSS" is set to "Confirmed" at the following event:
- Successful completion of the "Update VCSG Location" procedure to the CSS.
- The SGSN receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the SGSN restart if the roaming MS attached to the macro cell after the SGSN restart. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.4 Restoration Indicators in the MME | Two restoration indicators are provided in the MME for each IMSI record: "Subscriber Data Confirmed by HSS" and "Location Information Confirmed in HSS".
The indicator "Subscriber Data Confirmed by HSS" indicates whether the subscriber data set for the mobile station held by the MME is consistent with that held by the HSS.
The indicator "Subscriber Data Confirmed by HSS" shall be set to the initial value "Not Confirmed" when the MME receives a Tracking Area Update request or an Attach request for an UE for which the MME does not have an IMSI record.
The indicator "Subscriber Data Confirmed by HSS" shall be set to "Confirmed" at the following event:
- The MME successfully performs an Update Location to the HSS;
The indicator "Location Information Confirmed in HSS" indicates whether the HSS's record of the MME address for the UE is confirmed by radio contact.
The indicator "Location Information Confirmed in HSS" shall be set to "Not Confirmed" at any of the following events:
- The MME receives a Tracking Area Update request or an Attach request for an UE for which the MME has no IMSI record;
- The MME receives a "Reset" message from the HSS with which the UE is registered;
The indicator "Location Information Confirmed in HSS" shall be set to "Confirmed" at the following event:
- Successful completion of the Update Location procedure to the HSS.
Also the following two restoration indicators may be provided in the MME for each IMSI record: "Subscriber Data Confirmed by CSS" and "Location Information Confirmed by CSS".
The indicator "Subscriber Data Confirmed by CSS" indicates whether the CSG subscriber data set for the roaming UE held by the MME is consistent with that held by the CSS.
The indicator "Subscriber Data Confirmed by CSS" is set to the initial value "Not Confirmed" at any of the following events:
- The MME receives a Tracking Area Update request or an Attach request for a roaming UE for which the MME has no IMSI record;
- The MME receives a "Cancel VCSG Location Request" message from the CSS after the MME restart if the roaming UE attached to the macro cell after the MME restart.
The indicator "Subscriber Data Confirmed by CSS" is set to "Confirmed" at the following event:
- The MME successfully performs an "Update VCSG Location" to the CSS.
- The MME receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the MME restart if the roaming UE attached to the macro cell after the MME restart.
The indicator "Location Information Confirmed by CSS" indicates whether the MME address for the roaming UE registered is confirmed by the CSS.
The indicator "Location Information Confirmed by CSS" is set to "Not Confirmed" at any of the following events:
- The MME receives a Tracking Area Update request or an Attach request for a roaming UE for which the MME has no IMSI record;
- The MME receives a "Reset" message from the CSS with which the roaming UE is registered.
- The MME receives a "Cancel VCSG Location Request" message from the CSS after the MME restart if the roaming UE attached to the macro cell after the MME restart.
The indicator "Location Information Confirmed by CSS" is set to "Confirmed" at the following event:
- Successful completion of the "Update VCSG Location" procedure to the CSS.
- The MME receives an "Insert/Delete VCSG Subscription Data Request" message from the CSS after the MME restart if the roaming UE attached to the macro cell after the MME restart. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.5 Restoration Indicator in the ProSe Function | One restoration indicator is provided in the ProSe Function for each IMSI record: "Subscriber Data Confirmed by HSS".
The indicator "Subscriber Data Confirmed by HSS" indicates whether the subscriber data set for the user equipment held by the ProSe Function is consistent with that held by the HSS.
The indicator "Subscriber Data Confirmed by HSS" shall be set to "Confirmed" at the following event:
- Successful retrieval of ProSe subscriber information from the HSS.
The indicator "Subscriber Data Confirmed by HSS" shall be set to "Not Confirmed" at the following event:
- The ProSe Function receives a request for ProSe Service from an UE for which the ProSe Function does not have associated UE context;
- The ProSe Function receives a "Reset" message from the HSS with which the UE is registered. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 3.6 Restoration Indicator in the V2X Control Function | One restoration indicator is provided in the V2X Control Function for each IMSI record: "Subscriber Data Confirmed by HSS".
The indicator "Subscriber Data Confirmed by HSS" indicates whether the subscriber data set for the user equipment held by the V2X Control Function is consistent with that held by the HSS.
The indicator "Subscriber Data Confirmed by HSS" shall be set to "Confirmed" at the following event:
- Successful retrieval of V2X subscriber information from the HSS.
The indicator "Subscriber Data Confirmed by HSS" shall be set to "Not Confirmed" at the following event:
- The V2X Control Function receives a request for V2X Service from an UE for which the V2X Control Function does not have associated UE context;
- The V2X Control Function receives a "Reset" message from the HSS with which the UE is registered. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4 Restoration of data in the VLR | The effect on service of failure of a VLR is different from the effect of failure of an HLR. The procedures for restoration of a VLR and an HLR are therefore different. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.0 VLR Failure with Restart | When a VLR fails, all its associations with SGSNs affected by the failure become invalid and may be deleted. Based on configuration data, the MSC/VLR sends a BSSAP+ Reset message to each of its associated SGSNs. The SGSNs mark all associations containing the restarted VLR as invalid. For an MS that is both GPRS-attached and IMSI-attached, the SGSN may then:
- upon reception of a combined routing area update request, perform immediately the location update for non-GPRS services procedure towards the VLR; or.
- upon reception of a periodic routing Area update request, dependent on network configuration and operator policy,
- return a Detach Request (Detach Type) message with the Detach Type set to IMSI Detach immediately after the completion of the periodic routing area update procedure, in order to request the MS to perform a combined routing area update, , or
- perform immediately the location update for non-GPRS services procedure towards the VLR.
When a VLR fails, all its associations with MMEs affected by the failure become invalid and may be deleted. The VLR and MME shall behave as per clause 4.2.10. For a UE that is attached to both EPS and non-EPS services, the MME may then:
- upon reception of a combined tracking area update request, perform immediately the location update for non-EPS services procedure towards the VLR; or
- upon reception of a periodic tracking area update request, dependent on network configuration and operator policy,
- request the UE to re-attach to non-EPS services immediately after the completion of the periodic tracking area update procedure; or
- perform immediately the location update for non-EPS services procedure towards the VLR.
4.0a VLR Failure without Restart
If the VLR serving a MS that is attached for non-GPRS services is no longer in service, the SGSN may:
- upon reception of a combined routing area update request, perform immediately the location update for non-GPRS services procedure towards an alternative (available) VLR; or
- upon reception of a periodic routing area update request, dependent on network configuration and operator policy,
- request the MS to re-attach to non-GPRS services immediately after the completion of the periodic routing area update procedure and then select an alternative (available) VLR to serve the UE for non-GPRS services during the subsequent combined routing area update procedure; or
- perform immediately the location update for non-GPRS services procedure towards an alternative (available) VLR.
See 3GPP TS 29.018 [7].
If the VLR serving a UE that is attached for non-EPS services is no longer in service, the MME may :
- upon reception of a combined tracking area update request, perform immediately the location update for non-EPS services procedure towards an alternative (available) VLR; or
- upon reception of a periodic tracking area update request, dependent on network configuration and operator policy,
- request the UE to re-attach to non-EPS services immediately after the completion of the periodic tracking area procedure and then select an alternative (available) VLR to serve the UE for non-EPS services during the subsequent combined tracking area update procedure; or
- perform immediately the location update for non-EPS services procedure towards an alternative (available) VLR.
Upon reception of an Uplink NAS Transport message from a UE that is attached for non-EPS service, if the VLR serving the UE is no longer in service, the MME may request the UE to re-attach to non-EPS services and then select an alternative available VLR to serve the UE for MO SMS and other CS services during the subsequent combined TA / LA update procedure.
See 3GPP TS 29.118 [14].
NOTE: How an SGSN or MME detects that a VLR is no longer in service is implemention specifc, e.g. if there are no more SCTP associations in service with that VLR for a given period. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.1 Restart of the VLR | When a VLR restarts after a failure, all IMSI records affected by the failure are erased.
There will be no subscriber data or location information stored for an affected mobile station until after the VLR has received either a "Provide Roaming Number" request or an "Update location Area" request for that mobile station.
The VLR causes all affected TMSIs and all affected LMSIs to become invalid. "Invalid" in this context means that the TMSI and LMSI can no longer be regarded as accurate. The term is used to avoid unnecessary constraints on the implementation.
On receipt of either a "Provide Roaming Number" request or an "Update Location Area" request, restoration of subscriber data in the VLR is triggered individually for each IMSI record as described below. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2 Restoration Procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.0 General | The objective of the restoration procedure is to handle all traffic for each mobile subscriber correctly. In order to meet this objective, the procedure must make the subscriber data in the VLR consistent with that in the HLR or in the CSS, and make the location information in the HLR and VLR or the location information in the CSS and VLR reflect accurately the current location of the MS. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.1 Incoming Call | a) Send Routing Information (GMSC->HLR):
The HLR sends "Provide Roaming Number" to the VLR as for normal operation. The LMSI is updated by the VLR when the VLR requests the transfer of subscriber data from the HLR using the "Restore Data" operation.
b) Provide Roaming Number (HLR->VLR):
- Regardless of whether the VLR has an IMSI record corresponding to the IMSI in the "Provide Roaming Number", it returns an MSRN. If no IMSI record exists, the VLR creates a skeleton IMSI record, sets the indicators "Subscriber Data Confirmed by Radio Contact" and "Subscriber Data Confirmed by HLR" to "Not Confirmed" and (if IMSI Attach is used) marks the IMSI as attached. If the VLR serves two or more MSCs, the VLR sets the indicator "Location Information Confirmed in HLR" to "Not Confirmed". Otherwise, if the VLR serves only one MSC, the indicator "Location Information Confirmed in HLR" is set to the initial value "Confirmed". Also the VLR may set the indicators "Subscriber Data Confirmed by CSS" and "Location Information Confirmed by CSS" to "Not Confirmed".
- If the indicator "Subscriber Data Confirmed by HLR" is "Not Confirmed" the VLR requests authentication data, if required and still not available and subscriber data from the HLR. When the dialogue that covers the subscriber data retrieval procedure is completed successfully, the VLR sets the indicator "Subscriber Data Confirmed by HLR" to "Confirmed". The indicators "Confirmed by Radio Contact" and "Location Information Confirmed in HLR" remain unchanged.
- If the IMSI record for the MS is marked "Subscriber Data Confirmed by HLR" but "Not Confirmed by Radio Contact" the operator may choose an appropriate method to limit the number of "Search for MS" procedures for that MS.
c) Send Information for I/C Call Setup (MSC->VLR)
- If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR" the VLR returns a "System Failure" error.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Not Confirmed by Radio Contact", the VLR handles the request in the normal way, except that the "Search for MS" procedure is used instead of the "Page MS" procedure.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Confirmed by Radio Contact", the VLR handles the request in the normal way; for this MS, VLR restoration is complete.
- The state of the indicator "Location Information Confirmed in HLR" does not affect the "Send Information for I/C Call Setup" procedure.
d) Process Access Request in Response to Search (MSC->VLR):
- If the MS responds to paging, the MSC sends a positive response to the search request and a "Process Access Request" to the VLR. After successful authentication, if required, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed", sets the location area information for the MS, and handles the request in the normal way.
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" the VLR shall start an "Update VCSG Location" procedure to the CSS if the roaming MS is still in the CSG cell. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this MS, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.2 Mobile Terminated Short Message | a) Send Routing Information for MT SMS (SMS-GMSC->HLR):
The HLR returns the MSC number as for normal operation.
b) Send Information for MT SMS (MSC->VLR) - MAP version 2:
- If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR", the VLR proceeds as follows:
- the VLR returns an "Unidentified Subscriber" error. This causes the MSC to report a short message delivery failure, with cause "Unidentified Subscriber", to the SMS gateway MSC. The Gateway MSC sends a "Report SM Delivery Status" request, with a cause of "Absent Subscriber", to the HLR. This causes the HLR to set the "Mobile Station Not Reachable Flag" for the MS, as described in Technical Specifications 3GPP TS 23.040 [4] and 3GPP TS 29.002 [6]; or
- the VLR performs the data restoration procedure as specified in clause 4.2.1 for an incoming call and delay the mobile terminating SMS until the data restoration procedure is complete. During the data restoration procedure, the HLR shall send to the VLR the MME name or/and the SGSN Number if the subscriber is registered on this VLR and is registered to EPS or/and GPRS services respectively.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Not Confirmed by Radio Contact", the VLR handles the request in the normal way, except that the "Search for MS" procedure is used instead of the "Page MS" procedure.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Confirmed by Radio Contact", the VLR handles the request in the normal way; for this MS, VLR restoration is complete.
- The state of the indicator "Location Information Confirmed in HLR" does not affect the "Send Information for MT SMS" procedure.
c) Send Information for I/C Call Setup (MSC->VLR) - MAP version 1:
- If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR", the VLR proceeds as follows:
- the VLR returns a "System Failure" error. This causes the MSC to report a short message delivery failure, with cause "System Failure", to the SMS gateway MSC; or
- the VLR performs the data restoration procedure as specified in clause 4.2.1 for an incoming call and delay the mobile terminating SMS until the data restoration procedure is complete. During the data restoration procedure, the HLR shall send to the VLR the MME name or/and the SGSN Number if the subscriber is registered on this VLR and is registered to EPS or/and GPRS services respectively.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Not Confirmed by Radio Contact", the VLR handles the request in the normal way, except that the "Search for MS" procedure is used instead of the "Page MS" procedure.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Confirmed by Radio Contact", the VLR handles the request in the normal way; for this MS, VLR restoration is complete.
- The state of the indicator "Location Information Confirmed in HLR" does not affect the "Send Information for MT SMS" procedure.
d) Process Access Request in Response to Search (MSC->VLR):
- If the MS responds to paging, the MSC sends a positive response to the search request and a "Process Access Request" to the VLR. After successful authentication, if required, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed", sets the location area information for the MS, and handles the request in the normal way.
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed, the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" the VLR shall start an "Update VCSG Location" procedure to the CSS if the roaming UE is still in the CSG cell. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this MS, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.3 Mobile Terminating Location Request (MT-LR) | Receipt of an MT-LR for a target MS identified by its IMSI in a serving MSC during VLR restoration is supported by the procedures below.
a) Provide Subscriber Location (GMLC->MSC/VLR):
- If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR" the VLR returns an "Unidentified Subscriber" error. This causes the MSC to report a location failure, with cause "Unidentified Subscriber", to the GMLC.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Not Confirmed by Radio Contact", the VLR handles the request in the normal way, except that the "Search for MS" procedure is used instead of the "Page MS" procedure when paging for the MS.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Confirmed by Radio Contact", the VLR handles the request in the normal way; for this MS, VLR restoration is complete.
- The state of the indicator "Location Information Confirmed in HLR" does not affect the "Provide Subscriber Location" procedure.
b) Process Access Request in Response to Search (MSC->VLR):
- If the MS responds to paging, the MSC sends a positive response to the search request and a "Process Access Request" to the VLR. After successful authentication, if required, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed", sets the location area information for the MS, and handles the request in the normal way.
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed, the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" and the roaming MS is still in the CSG cell, the VLR shall start an "Update VCSG Location" procedure to the CSS. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this MS, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.4 Incoming LCS Information Request (GSM only) | Receipt of an incoming BSSMAP-LE LMU Connection Request from an SMLC directed to a specific Type A LMU is supported by the procedures below.
a) Request associated with an LMU (SMLC->MSC/VLR):
- If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR", the VLR returns an "Unidentified Subscriber" error.
- If the VLR has an IMSI record for an LMU marked "Subscriber Data Confirmed by HLR" and "Not Confirmed by Radio Contact", the VLR handles the request in the normal way, except that the "Search for MS" procedure is used instead of the "Page MS" procedure when paging for the LMU.
- If the VLR has an IMSI record marked "Subscriber Data Confirmed by HLR" and "Confirmed by Radio Contact", the VLR handles the request in the normal way. For this LMU, data restoration is complete.
- The state of the indicator "Location Information Confirmed in HLR" does not affect the incoming LMU Connection Request.
b) Process Access Request in Response to Search (MSC->VLR):
- If the LMU responds to paging, the MSC sends a positive response to the search request and a "Process Access Request" to the VLR. After successful authentication, if required, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed", sets the location area information for the LMU, and handles the request in the normal way.
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed, the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" and the roaming MS is still in the CSG cell, the VLR shallstart an "Update VCSG Location" procedure to the CSS. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this LMU, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.5 Outgoing MS request | An outgoing request (MS originated call, mobile originated Short Message or call-independent supplementary service activity) from the MS causes the VLR to check its IMSI record for that MS.
- If the MS is unknown in this VLR (i.e. the VLR has no IMSI record for the MS) or there is an IMSI record marked "Subscriber Data Not Confirmed by HLR" the outgoing request is rejected with error cause "Unidentified Subscriber". This causes the MS to initiate the location registration procedure described below.
- If the VLR has an IMSI record for the MS marked "Subscriber Data Confirmed by HLR" the request is handled in the normal way, and after any necessary authentication and/or IMEI checking the record is marked "Confirmed by Radio Contact".
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" and the roaming MS is still in the CSG cell, the VLR shall start an "Update VCSG Location" procedure to the CSS. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this MS, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.6 Outgoing LMU Request (GSM only) | An outgoing request (CM ServiceRequest) for LCS from a Type A LMU causes the VLR to check its IMSI record for that LMU.
- If the LMU is unknown in this VLR (i.e. the VLR has no IMSI record for the LMU) or there is an IMSI record marked "Subscriber Data Not Confirmed by HLR" the outgoing request is rejected with error cause "Unidentified Subscriber". This causes the LMU to initiate the location registration procedure described below.
- If the VLR has an IMSI record for the MS marked "Subscriber Data Confirmed by HLR", the request is handled in the normal way, and after any necessary authentication and/or IMEI checking the record is marked "Confirmed by Radio Contact".
- The VLR checks the indicator "Location Information Confirmed in HLR". If it indicates "Not Confirmed" the VLR starts an "Update Location" procedure to the HLR. When this procedure is successfully completed the VLR sets the indicator "Location Information Confirmed in HLR" to "Confirmed".
- If the MS is roaming, the VLR checks the indicators "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS". If either of them indicates "Not Confirmed" the VLR and the roaming MS is still in the CSG cell, may start an "Update VCSG Location" procedure to the CSS. When this procedure is successfully completed the VLR sets the indicator "Subscriber Data Confirmed by CSS" if the CSS has the corresponding valid CSG subscription data and "Location Information Confirmed by CSS" to "Confirmed".
For this LMU, VLR restoration is complete. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.7 Location Updating or IMSI Attach | A location registration request (location updating or IMSI attach) from an MS causes the VLR to check its IMSI record for that MS.
- If the MS is unknown in this VLR (i.e. the VLR has no IMSI record for the MS) the VLR creates a skeleton IMSI record for the MS and sets the indicators "Confirmed by Radio Contact", "Location Information Confirmed in HLR", "Subscriber Data Confirmed by HLR", "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" to "Not Confirmed". If authentication is required, the VLR retrieves authentication data. When the radio contact with the Mobile Station is authenticated, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed. The VLR then performs an "Update Location" to the HLR. If this is successful, the VLR sets the indicators "Location Information Confirmed in HLR" and "Subscriber Data Confirmed by HLR" to "Confirmed". For this MS, VLR restoration is complete. If the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the VLR may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the VLR sets the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" to "Confirmed" if the CSS has the corresponding valid CSG subscription data.
- If the VLR has an IMSI record for the MS, after successful authentication, if required, the VLR sets the indicator "Confirmed by Radio Contact" to "Confirmed". If the record is marked "Location Information Not Confirmed in HLR" or "Subscriber Data Not Confirmed by HLR" the VLR performs an "Update Location" to the HLR. If this is successful, the VLR sets the indicators "Location Information Confirmed in HLR" and "Subscriber Data Confirmed by HLR" to "Confirmed". For this MS, VLR restoration is complete. If the record is marked "Location Information Not Confirmed by CSS" or "Subscriber Data Not Confirmed by CSS" if the CSS has the valid CSG subscription data, and the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the VLR may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the VLR sets the indicators "Location Information Confirmed by CSS" if the CSS has the valid CSG subscription data and "Subscriber Data Confirmed by CSS" to "Confirmed". |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.8 Use of TMSI | After the VLR has restarted but before the next authenticated radio contact the TMSI known by the MS is invalid, as it was allocated before the VLR restarted. The VLR therefore uses the IMSI to identify the MS on the first radio contact during restoration.
- A VLR which initiates a "Search for Subscriber" procedure uses the IMSI to identify the MS.
- If an MS identifies itself by a TMSI in a "Location Registration" request, the VLR proceeds as follows:
a) The VLR checks the location area identity (LAI) of the previous location area sent by the MS. If this LAI is in a VLR different from the current one, the request is handled in the normal way.
b) If the LAI is in the current VLR, the status of the TMSI is checked:
- If the TMSI was allocated after the VLR restarted, and corresponds to a valid IMSI record, the request is handled as described in clause 4.2.7.
- If the TMSI was allocated before the VLR restarted, or does not correspond to a valid IMSI record, the VLR requests the IMSI from the MS. If the MS returns an IMSI the VLR proceeds as described in clause 4.2.7. If the MS does not return an IMSI the network aborts the location registration procedure.
- If an MS identifies itself by a TMSI in an outgoing MS request, the VLR proceeds as follows:
- If the TMSI was allocated after the VLR restarted, and corresponds to a valid IMSI record, the request is handled as described in clause 4.2.5.
- If the TMSI was allocated before the VLR restarted, or does not correspond to a valid IMSI record, the VLR requests the IMSI from the MS. If the MS returns an IMSI the VLR proceeds as described in clause 4.2.5. If the MS does not return an IMSI the network aborts the outgoing request. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.9 SGSN associations | Based on configuration data, "Reset" messages are sent on the Gs-interface to the SGSNs in the Location Areas served by the VLR as described in the 3GPP TS 29.018 [7]. The SGSNs mark all associations with the VLR as unreliable by setting the restoration indicator "VLR-Reliable" to "False" for the UEs served by that VLR. The associations will be re-initiated one by one by the SGSN at the next Routing Area update or combined RA/LA update from each UE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 4.2.10 MME associations | Based on configuration data, "Reset" messages are sent on the SGs-interface to the MMEs by the VLR as described in the 3GPP TS 29.118 [14]. The MMEs mark all associations with the VLR as unreliable by setting the restoration indicator "VLR-Reliable" to "False" for the UEs served by that VLR. The associations will be re-initiated one by one by the MME at the next Tracking Area update or combined TA/LA update from each UE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5 Restoration of data in the HLR/HSS | The loss or corruption of subscriber data in the HLR/HSS has an impact not only in the HLR/HSS's own PLMN but also on the service for its mobiles in other PLMNs. Restoration of the data in the HLR/HSS requires co-operation from all the VLRs, SGSNs and MMEs at which its mobiles are registered. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.1 Restart of the HLR/HSS | The periodic backup of HLR/HSS data to non-volatile storage is mandatory.
When an HLR/HSS restarts after failure it shall perform the following actions for the subscriber data records that have been affected by the HLR/HSS fault:
- reload all data from the non-volatile back-up;
- reset all "MS Purged" flags;
- mark each subscriber record "SS Check Required" by setting the "Check SS" indicator if the "Forward Check SS Indication" service is implemented;
- send a "Reset" message to each VLR where one or more of its MSs are registered. This causes each VLR concerned to mark each relevant subscriber record "Location Information Not Confirmed in HLR", and
- send a "Reset" message to each SGSN where one or more of its MSs are registered. This causes each SGSN to mark each relevant MM context "Location Information Not Confirmed in HLR".
- send a "Reset" message to each MME where one or more of its UEs are registered. This causes each MME to mark each relevant MM context "Location Information Not Confirmed in HSS".
- send a "Reset" message to each ProSe Function (see 3GPP TS 23.303 [33]), where one or more of its UEs are registered for ProSe Services. This causes each ProSe Function to mark each relevant UE context "Subscriber Data Not Confirmed by HSS".
- send a "Reset" message to each V2X Control Function (see 3GPP TS 23.285 [40]), where one or more of its UEs are registered for V2X Services. This causes each V2X Control Function to mark each relevant UE context "Subscriber Data Not Confirmed by HSS". |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2 Procedures During Restoration | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.1 Mobile terminated call | If the VLR receives a "Process Access Request" request in response to a "Page" or "Search for MS" operation, after successful authentication, if required, it checks the indicator "Location Information Confirmed in HLR". If this indicates "Not Confirmed" the VLR triggers an "Update Location" to the HLR as described in clause 4.2.1.d).
When the HLR receives the "Update Location" request it stores the VLR number, MSC number and LMSI in the subscriber record as for normal operation.
If the "Forward Check SS Indication" service is implemented, the HLR checks the indicator "Check SS". If this indicates "Check Required", after successful completion of the subscriber data retrieval procedure that ran embedded in the "Update Location" procedure the HLR sends a "Forward Check SS Indication" to the VLR and marks the subscriber record "Check Not Required. When the VLR receives the "Forward Check SS Indication" request it forwards an indication to the MS to alert the user that supplementary service parameters should be checked. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.2 Mobile Originated Activity for CS | When the VLR receives a request from an MS (MS originated call, mobile originated Short Message, call-independent supplementary service activity or location registration request) whose IMSI record is marked "Location Information Not Confirmed in HLR", it will perform an "Update Location" to the HLR as described in clauses 4.2.5 and 4.2.7 above.
When the HLR receives an "Update Location" request from the VLR, it proceeds as described in clause 5.2.1. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.