hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15 Use Case: FRMCS System security framework | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.1 Introduction | The security framework protects the FRMCS System against attacks and threats, like misuse, Denial of Service (DoS), unauthorized access to services, interception, man-in-the-middle attacks, replay attacks and intended data modification. It encompasses the protection of security attributes confidentiality, privacy, inte... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2 Use case: FRMCS System security framework | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 12.15.2.1 Description | The security framework protects:
• Services provided by the FRMCS System;
• Bearer flexible access including 3GPP as well as non-3GPP access;
• Direct interaction between FRMCS Equipment;
• Interaction between the FRMCS end user devices and FRMCS network;
• Interaction between FRMCS network functions;
• Stored data wit... |
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 attack... |
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 allo... |
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 commu... |
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,... |
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... |
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 whic... |
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 u... |
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 m... |
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 th... |
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 communica... |
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 requi... |
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 ident... |
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 an... |
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 d... |
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 o... |
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 applicati... |
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 un... |
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 t... |
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... |
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... |
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, t... |
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 ve... |
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... |
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... |
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 a... |
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... |
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 T... |
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 ... |
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 req... |
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 contig... |
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 a... |
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. ... |
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 t... |
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.
- Fo... |
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 connec... |
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 ... |
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 s... |
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 s... |
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 th... |
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 H... |
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 "Subsc... |
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 indi... |
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-attache... |
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... |
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 informatio... |
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 ... |
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... |
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 Sub... |
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 "Unidenti... |
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... |
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 c... |
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", "Loca... |
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 use... |
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... |
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... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.