hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.3 Mobile Originated Activity for ProSe | When the ProSe Function receives a request for ProSe Service from a UE whose associated context is marked as "Subscriber Data Not Confirmed by HSS", it shall initiate a "ProSe Subscriber Information Retrieval" request to the HSS as described in the 3GPP TS 29.344 [34].
When the HSS receives a "ProSe Subscriber Information Retrieval" request from the ProSe Function, it shall proceed as described in the 3GPP TS 29.344 [34]. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.4 Procedures in the SGSN | Upon receipt of a HLR/HSS reset, the SGSN shall mark each relevant MM contexts as invalid and shall set the Non-GPRS Alert Flag (NGAF) if an SGSN - MSC/VLR association exists. After detection of any activity (either signalling or data) from a marked MS or any other implementation dependent trigger for a marked MS in PMM-CONNECTED state with Direct tunnel, the SGSN performs an update location to the HLR/HSS as in the attach or inter-SGSN RA update procedures and, if NGAF is set, the procedure of "Non-GPRS Alert" is followed (see clause 7 in 3GPP TS 29.018 [7]).
The update location procedure and the procedure towards the VLR may be delayed by the SGSN for a maximum operator configuration-depending time period to avoid high signalling load. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.5 Procedures in the MME | Upon receipt of a HSS reset, the MME shall mark each relevant MM contexts as invalid and shall set Non-EPS Alert Flag (NEAF) if an MME - MSC/VLR association exists. After detection of any activity (either signalling or data) from a marked UE or any other implementation dependent trigger for a marked UE in ECM-CONNECTED state, the MME performs an update location to the HSS as in the attach or inter-MME TA update procedures and, if NEAF is set, the procedure of "NON-EPS Alert" is followed (see clause 5.3 in 3GPP TS 29.118 [14]).
The update location procedure and the procedure towards the VLR may be delayed by the MME for a maximum operator configuration-depending time period to avoid high signalling load. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 5.2.6 Mobile Originated Activity for V2X | When the V2X Control Function receives a request for V2X Service from a UE whose associated context is marked as "Subscriber Data Not Confirmed by HSS", it shall initiate a "V2X Subscriber Information Retrieval" request to the HSS as described in the 3GPP TS 29.388 [41].
When the HSS receives a "V2X Subscriber Information Retrieval" request from the V2X Control Function, it shall proceed as described in the 3GPP TS 29.388 [41]. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 6 Periodic location updating | The time taken to confirm the location of an MS after location register failure is governed by the frequency with which the MS establishes radio contact with the network. The location information for an MS which remains silent for a long time will remain doubtful for a long time.
A method of reducing this time is to require the MS to establish radio contact with the network at intervals, purely to confirm its location, if the MS does not move to a new location area (which would lead to a normal location registration) or respond to paging for a mobile terminated call or request a mobile originated call or call-independent supplementary service activity.
The interval between successive periodic location updatings is controlled by a timer in the MS; this timer is reset to its initial value at the end of each successfully established radio contact between the MS and the network.
The use of the periodic location update timer is described in 3GPP TS 23.122 [27]. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 7 Periodic routeing area updating | All GPRS-attached MSs, except MSs in class-B mode of operation engaged in CS communication, shall perform periodic RA updates. For MSs that are both IMSI-attached and GPRS-attached, the periodic updates depend on whether the Gs interface is installed or not:
- If the Gs interface is installed, periodic RA updates shall be performed, and periodic LA updates shall not be performed. If the SGSN has the indicator "VLR-reliable" set to ´false´ the SGSN shall perform a location area update procedure towards the VLR
- If the Gs interface is not installed, both periodic RA updates and periodic LA updates shall be performed independently. RA updates are performed via the Gb interface, and LA updates are performed via the A interface.
The periodic routeing area update is described in 3GPP TS 23.060 [5]. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 8 Stand-alone operation of the VLR | In a 2G authentication regime, triplets, regardless of its nature (generated in a 2G AuC or derived from quintuplets in a 3G VLR or a 3G HLR), may be reused when no unused authentication triplets are available in the VLR for an IMSI record. It is an operator option to define how many times an authentication triplet may be reused in the VLR.
In a 3G authentication regime, quintuplets, regardless of its nature (generated in a 3G AuC or derived from triplets in a 3G VLR), shall not be reused when no unused authentication quintuplets are available in the VLR for an IMSI record.
If the Update Location response contains an error different from "Unknown Subscriber" or "Roaming Not Allowed" or if there is a parameter problem (e.g. no HLR number included), no error shall be indicated to the MSC and the IMSI record in the VLR shall not be affected, provided that the associated "Subscriber Data Confirmed by HLR" indicator is in the "Confirmed" status. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 9 Stand-alone operation of the SGSN | In a 2G authentication regime, triplets, regardless of their nature (generated in a 2G AuC or derived from quintuplets in a 3G SGSN or a 3G HLR), may be reused when no unused authentication triplets are available in the SGSN for an IMSI record. It is an operator option to define how many times an authentication triplet may be reused in the SGSN.
In a 3G authentication regime, quintuplets, regardless of their nature (generated in a 3G AuC or derived from triplets in a 3G SGSN), shall not be reused when no unused authentication quintuplets are available in the SGSN for an IMSI record.
9A Stand-alone operation of the MME
In a E-UTRAN authentication regime, EPS authentication vectors shall not be reused when no unused EPS authentication vectors are available in the MME for an IMSI record. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10 Restoration of data in the GGSN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.0 GGSN failure | When a GGSN fails, all its PDP contexts affected by the failure become invalid and may be deleted. GGSN storage of subscriber data is volatile.
When the GGSN receives a GTP‑U PDU for which no PDP context exists, it shall discard the GTP‑U PDU and return a a GTP error indication to the originating node (the SGSN or, if Direct Tunnel is established, the RNC).
The GGSN should ensure as far as possible that previously used TEID values are not immediately reused after a GGSN restart, in order to avoid inconsistent TEID allocation throughout the network. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.1 Restart of the GGSN | After a GGSN restart, all the PDP contexts, the MBMS UE contexts, and the MBMS Bearer contexts stored in the GGSN and affected by the restart become invalid and may be deleted.
When the SGSN detects a restart in a GGSN (see clause 18 "GTP-C based restart procedures") with which it has one or more PDP contexts activated, it shall deactivate all these PDP contexts and request the MS to reactivate them. When the SGSN detects a restart in a GGSN with which it has MBMS Bearer context(s) and/or MBMS UE context(s), it shall delete all these MBMS Bearer context(s) and/or MBMS UE context(s). |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2 Restoration Procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.0 General | The GGSN will receive the SGSN restart counters in GTPv1 echo response from the SGSN. When a GGSN detects that a peer SGSN has restarted it shall delete all PDP context(s), MBMS UE context(s), MBMS Bearer context(s) associated with the peer node that failed as well as freeing any internal GGSN resources associated with those PDP context(s), MBMS UE context(s) and MBMS Bearer context(s). The GGSN may optionally perform other implementation specific actions such as messages to clear other external resources (e.g. PCC messages).
If the GGSN needs to send a request for IP-CAN Session Modification procedure towards a PCRF which is known to have restarted since the IP-CAN session establishment, the GGSN may discard the request and may tear down all the PDP context(s) associated with the PDP address of the IP-CAN session, based on operator policy, by initiating a PDP Context Deactivation procedure towards the SGSN with the cause set to "Reactivation requested". This leads the UE to initiate PDP Context Activation procedure for the same APN. Emergency sessions should not be torn down.
NOTE: The procedure above just enables to clean up all the PDP Context(s) associated with the PDP address of the IP-CAN session, affected by the PCRF failure when a specific interaction with the PCRF is required. Prior to that interaction, PCC controlled services cannot be provided to the UE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.1 Mobile terminated transmission | When the GGSN receives a mobile terminated PDU for which no valid PDP context exists the GGSN discards the received PDU and may also return an appropriate Error message depending on the protocol used. No further actions are performed by the GGSN. Alternatively, if the GGSN has static PDP information about the PDP address, the GGSN may try to deliver the PDU by initiating the Network-Requested PDP Context Activation procedure (see 3GPP TS 23.060 [5]). |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 10.2.2 Mobile originated transmission | When the GGSN receives a tunnel PDU for which no PDP context exists it discards the tunnel PDU and sends an Error indication message to the originating SGSN. The SGSN deactivates the PDP context and sends an Error indication to the MS. The MS may then re-activate the PDP context. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11 Restoration of data in the SGSN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0 SGSN Failure | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0.1 Gn/Gp SGSN failure | When an SGSN fails, it deletes all MM and PDP contexts affected by the failure. SGSN storage of subscriber data is volatile. Based on configuration data, the SGSN may send a Reset message to each of its associated VLRs. If a Reset message is sent, the VLR may mark all associations containing the restarted SGSN as unreliable. See 3GPP TS 29.018 [7]. In the case of optional CAMEL interaction the failing SGSN shall invoke the CAMEL-GPRS-Exception procedure towards the GSM‑SCFs.
If data or signalling, except GPRS attach and RA update, is received in an SGSN from an MS for which no MM context exists in the SGSN, the SGSN shall discard the data or signalling.
If an RA update request is received in an SGSN from an MS for which no MM context exists in the SGSN, or in the old SGSN for the inter-SGSN RA update case, the SGSN shall reject the RA update with an appropriate cause. In order to remain GPRS-attached, the MS shall then perform a new GPRS attach and should (re‑)activate PDP contexts.
If a service request is received in a 3G‑SGSN from an MS for which no MM context exists in the 3G‑SGSN, the 3G‑SGSN shall reject the service request with an appropriate cause. In order to remain GPRS-attached, the MS shall then perform a new GPRS attach and should (re‑) activate PDP contexts.
NOTE: In some cases, user interaction may be required, and then the MS cannot (re‑)activate the PDP contexts automatically.
When the SGSN receives a PDU Notification Request message for which no MM context exists, the SGSN returns a PDU Notification Response message to the GGSN with an appropriate cause (see clause "Unsuccessful Network-Requested PDP Context Activation Procedure" in 3GPP TS 23.060 [5]), and the SGSN may search the MS by paging with the IMSI in the SGSN area. An MS that is paged for PS services with IMSI as the identifier shall perform a new GPRS attach and should (re‑)activate PDP contexts.
When the SGSN receives a GTP‑U PDU from the GGSN for which no PDP context exists, it shall discard the GTP‑U PDU and send a GTP error indication to the originating GGSN.
When the SGSN receives a GTP‑U PDU from the RNC for which no PDP context exists, the SGSN shall discard the GTP‑U PDU and send a GTP error indication to the originating RNC.
When the SGSN receives a mobile-terminated SM from the SMS‑GMSC for an IMSI unknown in the SGSN, it rejects the request.
When the SGSN receives a paging request over the Gs interface for an IMSI unknown in the SGSN and the SGSN has not completed recovery, the SGSN may page the MS for packet services with IMSI as identifier in the area specified by the location information provided by the MSC/VLR. If no such location information is provided, the SGSN may page the MS in the routeing areas corresponding to that MSC/VLR. After the MS performs a combined GPRS attach, the SGSN may continue serving the Gs interface paging request. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.0.2 SGSN Failure using S4 | When the SGSN receives a GTP‑U PDU from the Serving GW for which no Bearer context exists, it shall discard the GTP‑U PDU and send a GTP error indication to the originating Serving GW.
When the SGSN receives a GTP‑U PDU from the MBMS GW for which no MBMS Point to Point Bearer context exists, it shall discard the GTP‑U PDU and send a GTP Error Indication to the originating MBMS GW.
An S4-SGSN and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25.
When the S4-SGSN which does not support the optional network triggered service restoration procedure as specified in clause 25 receives a Downlink Data Notification message for which no MM context exists, the S4-SGSN returns a Downlink Data Notification Acknowledge message to the Serving GW with an appropriate cause. The Serving GW shall delete the related Bearer context related to S4-SGSN; and if there is no ISR associated MME recorded on the related Bearer context the Serving GW shall also notify the PDN GW to delete the Bearer context. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.1 Restart of the SGSN | After an SGSN restart, the SGSN deletes all MM, PDP, MBMS UE, and MBMS Bearer contexts affected by the restart.
When the GGSN detects a restart in an SGSN (see clause 18 "GTP-C based restart procedures") with which it has PDP context(s) activated and/or MBMS UE context(s), it shall delete all these PDP context(s) and/or MBMS UE context(s). When the GGSN detects a restart in an SGSN with which it has any MBMS Bearer context, it shall not delete the MBMS bearer context unless all SGSNs connected to the GGSN restart.
When the MBMS GW detects a restart in an SGSN (see clause 18 "GTP-C based restart procedures") with which it has at least one MBMS Bearer context, the MBMS GW should re-establish the active MBMS bearer services affected by the SGSN restart by initiating MBMS Session Start procedure(s) towards the restarted SGSN (or an alternative SGSN in the same SGSN pool). The MBMS GW shall encode the contents of the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or as per the last MBMS Session Update Request received from the BM-SC if the original parameters were updated) with the following exceptions:
- the MBMS GW shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session;
- the MBMS GW may change the relative start time ("time to MBMS data transfer" parameter) to fasten the restoration of the MBMS service in UTRAN;
- the MBMS GW should set the estimated session duration to a value corresponding to the remaining duration of the session.
NOTE: If the MBMS GW receives an MBMS Session Update Request from the BM-SC during the SGSN restart, the contents of the MBMS Session Start Request sent to the SGSN after the SGSN restart can also differ from the parameters sent to the SGSN before its restart for the parameters that can be modified by the MBMS session update procedure (i.e. MBMS Session Area, MBMS Time to Data Transfer).
The MBMS GW shall not delete the MBMS Bearer context unless all SGSNs/MMEs serving the MBMS bearer service and connected to the MBMS GW have restarted and the MBMS-GW does not support re-establishing MBMS bearer services after an SGSN restart. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2 Restoration Procedures | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.1 Mobile terminated user data transmission | When a Gn-SGSN receives a tunnel PDU for which no PDP context or MBMS Bearer Context exists it discards the tunnel PDU and sends an Error indication message to the originating GGSN.
An S4-SGSN and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.2 Mobile terminated services requested by the MSC/VLR | When the SGSN receives a request for CS paging from an MSC/VLR for an IMSI unknown by the SGSN, if the "SGSN-Reset" indicator is set to "true", the SGSN sends the paging request with the location information provided by the VLR. If no such location information is provided, the SGSN should page for the MS in all the routeing areas corresponding to that SGSN.
If the "SGSN-Reset" indicator is set to "false" and the IMSI is unknown or the MS is marked as GPRS or non-GPRS detached by the SGSN, the paging request is rejected.
If the "SGSN-Reset" indicator is set to "false" and the IMSI is known and the MS is marked as GPRS and is non-GPRS attached by the SGSN, the paging request shall be sent to the MS. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.3 Mobile terminated SMS over GPRS | a) Send Routing Information for MT SMS (SMS-GMSC -> HLR):
The HLR returns the SGSN number as for normal operation.
b) Send Information for MT SMS:
- When the SGSN receives a mobile terminated SMS for an unknown MM context for the MS, or if the SGSN indicator "Subscriber Data Confirmed by HLR" is marked "Not Confirmed" it rejects the SMS request and returns a failure report with cause value "Unidentified Subscriber" to the SMS gateway MSC indicating unsuccessful delivery of the SMS. 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 for GPRS Flag" for the MS, as described in the Technical Specifications3GPP TS 23.040 [4] and 3GPP TS 29.002 [6].
- If the SGSN has the indicator "Subscriber Data Confirmed by HLR" set to "Confirmed", the SGSN handles the SMS request in the normal way.
The state of the indicator "Location Information Confirmed in HLR" does not affect the Mobile Terminated SMS procedure. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.4 Mobile originated Routeing Area Updating or Attach | For attach, where the MS is unknown in the SGSN (i.e. the SGSN has no MM context for the MS) the SGSN creates an MM context for the MS and sets the indicators "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 SGSN retrieves authentication data. The SGSN then performs an "Update GPRS Location" to the HLR. If this is successful, the SGSN sets the indicators "Location Information Confirmed in HLR" and "Subscriber Data Confirmed by HLR" to "Confirmed". If the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the SGSN may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the SGSN sets the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
For routing area update, where the MS is unknown in the SGSN (i.e. the SGSN has no MM context for the MS) or for inter-SGSN routing area update, where the MS is unkown in the old SGSN, the SGSN shall reject the RA update with an appropriate cause. In order to remain GPRS-attached, the MS shall then perform a new GPRS attach and should (re‑)activate its PDP contexts.
If the SGSN has an MM context for the MS, and the indicators "Location Information Confirmed in HLR" or "Subscriber Data Confirmed by HLR" is set to "Not Confirmed" the SGSN performs an "Update GPRS Location" to the HLR. If this is successful, the SGSN sets the indicators "Location Information Confirmed in HLR" and "Subscriber Data Confirmed by HLR" to "Confirmed". If the indicators "Location Information Confirmed by CSS" or "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data is set to "Not Confirmed", and the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the SGSN may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the SGSN sets the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
If the SGSN has an MM context for the MS with the indicator "Subscriber Data Confirmed by HLR" marked "Confirmed" the originated transmission is handled in the normal way.
The SGSN retrieves subscriber data from the HLR by sending an "Update GPRS Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR.
The SGSN retrieves CSG subscriber data from the CSS by sending an "Update VCSG Location" request, which triggers one or more "Insert Subscriber Data" operations from the CSS if the CSS has the valid CSG subscription data. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.5 Mobile originated LLC frame | If an SGSN receives an LLC frame for which no MM context exists in the SGSN, and if the LLC frame does not contain an Attach Request or a Routeing Area Update Request signalling message, then the LLC frame shall be discarded. The MS may determine that the network is not responding and attempt to re-attach or eventually a periodic Routing Area Update message is sent by the MS which initiates the attach procedures. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.2.6 Mobile originated Service Request | For service request, where the MS is unknown in the SGSN (i.e. the SGSN has no MM context for the MS), the SGSN shall reject the service request with an appropriate cause. In order to remain GPRS-attached, the MS shall then perform a new GPRS attach and should (re‑)activate its PDP contexts.
If the SGSN has an MM context for the MS, and the indicators "Location Information Confirmed by CSS" or "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data is set to "Not Confirmed", and the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the SGSN may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the SGSN sets the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
The SGSN retrieves CSG subscriber data from the CSS by sending an "Update VCSG Location" request, which triggers one or more "Insert Subscriber Data" operations from the CSS if the CSS has the valid CSG subscription data. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.3 Use of TLLI | After the SGSN has restarted but before the next authenticated radio contact the P‑TMSI and TLLI known by the MS are invalid, as the P-TMSI was allocated before the SGSN restarted. The SGSN may request the MS to identify itself with the IMSI in order to make a relationship between the IMSI and the received old TLLI. The SGSN shall allocate a new P-TMSI for that MS.
If an MS identifies itself by a TLLI in an MS originating transmission, the SGSN proceeds as follows:
a) The SGSN checks the routing area identity (RAI) of the previous routing area sent by the MS. If this previous RAI belongs to a different SGSN, the request is handled in the normal way.
b) If the previous RAI belongs to the current SGSN, the status of the TLLI is checked.
- If the P‑TMSI derived from the TLLI was allocated after the SGSN restarted, and corresponds to a valid IMSI record, then the request is handled in the normal way.
- If the P‑TMSI derived from the TLLI was allocated before the SGSN restarted, or does not correspond to a valid IMSI record, then the SGSN requests the IMSI from the MS. If the MS returns an IMSI the SGSN proceeds in the normal way. If the MS does not return an IMSI the network aborts the originating transmission request or location registration procedure. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.4 VLR associations | All associations with VLRs affected by the restart of an SGSN are marked as unreliable and may be deleted. Based on configuration data, Reset messages may be sent on the Gs-interface to the VLRs served by the SGSN. If Reset messages are sent, the VLRs may mark all associations with the SGSN as unreliable by setting the restoration indicator "Confirmed by radio contact" to "Not Confirmed" for the MSs served by that SGSN. See 3GPP TS 29.018 [7]. 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 MS. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5 Restart of a peer node | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5.1 SGW failure | When an SGSN detects that a peer SGW has failed with or without restart (relying on restart counter as specified in clause 18 "GTP-C based restart procedures" or implementation e.g. preconfigured path failure timer) it shall either:
- as a default delete all PDN connection table data/MM bearer contexts associated with the peer node that has failed as well as freeing any internal SGSN resources associated with those PDN connections. The SGSN may optionally perform other implementation specific actions such as to clear external resources (e.g. Iu messages to clear UTRAN resources) or more advanced forms of restoration;
or
- follow the procedures specified in clause 27 to restore the PDN connections affected by the SGW failure, if the SGSN and the PGW support these procedures.
NOTE: The SGSN will have the identity of the PGW and SGW currently in use for a PDN connection available in the SGSN's PDN connection table as part of existing EPC procedures as well as other peer state data. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 11.5.2 MBMS-GW failure | The behaviour of an SGSN when it detects that a peer MBMS GW has restarted is described in clause 17A.1. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12 Restoration of Data in an SMLC (GSM only) | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12.1 Restart of an SMLC | When an SMLC restarts after a failure, it performs the following actions for those of its associated LMUs whose records have been affected by the fault:
- Reload all administered LMU data from non-volatile back-up;
- Reinitialize other temporary data for each LMU to indicate no ongoing measurement or diagnostic activities;
- Perform data restoration for each affected Type A and Type B LMU as described below. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 12.2 Data Restoration for a Specific LMU | An SMLC may restore data for a specific LMU when the data in the SMLC or LMU is considered unreliable (e.g. if there is no communication between the SMLC and LMU for a long time or if messages received by the SMLC are inconsistent with the LMU state kept by the SMLC). To restore data for a specific LMU, the SMLC shall open a signalling connection to the LMU if this is Type A, as described in 3GPP TS 23.071 [10]. For both a Type A LMU and a Type B LMU, the SMLC shall then send an LLP Reset message to the LMU. On receiving an LLP Reset, an LMU shall cancel any LCS measurement and O&M tasks previously ordered by the SMLC and shall return an LLP Reset acknowledgement to the SMLC. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 13 Restoration of Data in an LMU (GSM only) | When an LMU restarts following a failure, it shall reinitialize all data concerning LCS measurement and O&M tasks to indicate that no tasks ordered by an SMLC are active. A Type A LMU shall then perform an "IMSI Attach". A Type A LMU shall then open a signalling connection to its controlling SMLC as described in 3GPP TS 23.071 [10]. Both a Type A LMU and a Type B LMU shall send an LLP Status Update message to their controlling SMLC containing an indication that the LMU has restarted following a failure. The SMLC shall update its data regarding the state of the LMU and shall return an LLP Update Status acknowledgment to the LMU. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14 Restoration of data in the MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1 Restart of the MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.1 Restoration Procedures | After an MME restart, the MME shall delete all MM Bearer contexts affected by the restart that it may have stored.
When the MBMS GW detects a restart in an MME (see clause 18 "GTP-C based restart procedures") with which it has at least one MBMS Bearer context, the MBMS-GW should re-establish the active MBMS bearer services affected by the MME restart by initiating MBMS Session Start procedure(s) towards the restarted MME (or an alternative MME in the same MME pool). The MBMS GW shall encode the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or as per the last MBMS Session Update Request received from the BM-SC if the original parameters were updated) with the following exceptions:
- the MBMS GW shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session;
- if no absolute start time ("MBMS data transfer start" parameter) has been received, the MBMS GW may change the relative start time ("time to MBMS data transfer" parameter) to fasten the restoration of the MBMS service in E-UTRAN;
- the MBMS GW should set the estimated session duration to a value corresponding to the remaining duration of the session.
The MCE shall be able to accept MBMS session requests with an absolute start time ("MBMS data transfer start" parameter) in the past.
NOTE: If the MBMS GW receives an MBMS Session Update Request from the BM-SC during the MME restart, the contents of the MBMS Session Start Request sent to the MME after the MME restart can also differ from the parameters sent to the MME before its restart for the parameters that can be modified by the MBMS session update procedure (i.e. MBMS Session Area, MBMS Time to Data Transfer, MBMS Data Transfer Start).
The MBMS GW shall not delete the MBMS Bearer context unless all SGSNs/MMEs serving the MBMS bearer service and connected to the MBMS GW have restarted and the MBMS-GW does not support re-establishing MBMS bearer services after an MME restart.
If the MCE receives an M3 Reset message from the MME (i.e. in case the restart event has resulted in loss of some or all M3 transactions reference information) with which it has at least one MBMS Bearer context, the MCE shall deactivate all the related MBMS Bearer contexts locally and towards E-UTRAN within which the MBMS bearer service is active, either immediately or after a pre-configured time period if the corresponding MBMS Bearer contexts are not re-established via any MME.
An MME and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25.
When the MME which does not support the optional network triggered service restoration procedure as specified in clause 25 receives a Downlink Data Notification message for which no MM context exists, the MME returns a Downlink Data Notification Acknowledge message to the Serving GW with an appropriate cause. The Serving GW shall delete the related Bearer context related to MME; and if there is no ISR associated S4-SGSN recorded on the related Bearer context the Serving GW shall also notify the PDN GW to delete the Bearer context. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.2 Mobile originated Tracking Area Updating or E-UTRAN Attach | For attach, where the UE is unknown in the MME (i.e. the MME has no MM context for the UE) the MME shall create an MM context for the UE and shall set the indicators "Location Information Confirmed in HSS", "Subscriber Data Confirmed by HSS", "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" to "Not Confirmed". If authentication is required, the MME shall retrieve the authentication data. The MME then performs an "Update Location" to the HSS. If this is successful, the MME shall set the indicators "Location Information Confirmed in HSS" and "Subscriber Data Confirmed by HSS" to "Confirmed". If the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the MME may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the MME shall set the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
For tracking area update, where the UE is unknown in the MME (i.e. the MME has no MM context for the UE) or for inter-MME tracking area update, where the UE is unkown in the old MME, the MME shall reject the TA update with an appropriate cause. In order to remain attached, the UE shall then perform a new attach and should (re‑)activate its EPS Bearer contexts.
If the MME has an MM context for the UE, and the indicator "Location Information Confirmed in HSS" or "Subscriber Data Confirmed by HSS" is set to "Not Confirmed" the MME shall perform an "Update Location" to the HSS. If this is successful, the MME shall set the indicators "Location Information Confirmed in HSS" and "Subscriber Data Confirmed by HSS" to "Confirmed". If the indicators "Location Information Confirmed by CSS" or "Subscriber Data Confirmed by CSS" is set to "Not Confirmed", and the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the MME may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the MME shall set the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
If the MME has an MM context for the UE with the indicator "Subscriber Data Confirmed by HSS" marked "Confirmed" the originated transmission shall be handled in the normal way.
The MME retrieves subscriber data from the HSS by sending an "Update Location" request, which triggers an "Update Location" answer which contains the subscriber data.
The MME retrieves CSG subscriber data from the CSS by sending an "Update VCSG Location" request, which triggers an "Update VCSG Location" answer which may contain the valid CSG subscription data. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.3 Mobile terminated services requested by the MSC/VLR | An MME and a VLR supporting mobile terminated CS service delivery via an alternative MME in MME pool shall behave as specified in clause 26.
When the MME receives a request for CS paging from an MSC/VLR for an IMSI unknown by the MME, if the "MME-Reset" indicator is set to "true", the MME sends the paging request with the location information provided by the VLR. If no such location information is provided, the MME should page for the UE in all the tracking areas corresponding to that MME. The MME may support and apply this procedure to a UE using extended idle mode DRX for MT-SMS service.
NOTE: How the restarted MME knows the UE's DRX parameter or the extended DRX parameters to page the UE is implementation dependent.
If the "MME-Reset" indicator is set to "false" and the IMSI is unknown or the UE is marked as EMM-DEREGISTERED by the MME, the paging request is rejected.
If the "MME-Reset" indicator is set to "false" and the IMSI is known and the UE is marked as EMM-REGISTERED by the MME, the paging request shall be sent to the UE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.4 Mobile terminated user data transmission | An MME and an SGW supporting the optional network triggered service restoration procedure shall behave as specified in clause 25. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.5 Mobile originated Service Request | For service request, where the UE is unknown in the MME (i.e. the MME has no MM context for the UE), the MME shall reject the service request with an appropriate cause. In order to remain attached, the UE shall then perform a new attach and should (re‑)activate its EPS Bearer contexts.
If the MME has an MM context for the UE, and the indicators "Location Information Confirmed by CSS" or "Subscriber Data Confirmed by CSS" is set to "Not Confirmed", and the VPLMN supports Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN, the MME may perform an "Update VCSG Location" to the CSS if the requested cell is a CSG/hybrid cell. If this is successful, the MME shall set the indicators "Location Information Confirmed by CSS" and "Subscriber Data Confirmed by CSS" if the CSS has the valid CSG subscription data to "Confirmed".
The MME retrieves CSG subscriber data from the CSS by sending an "Update VCSG Location" request, which triggers an "Update VCSG Location" answer which may contain the valid CSG subscription data. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.1.6 Mobile Terminated NIDD procedure | During the Mobile Terminated NIDD procedure, if the SCEF receives a MT-Data-Answer from the MME/SGSN with a failure cause that UE cannot be found, the SCEF shall delete all the bearer contexts of this UE and may notify the Operation and Maintenance network element.
NOTE: After that, if the SCEF receives a following NIDD Submit request from the SCS/AS for the deleted bearer, the SCEF behaves as specified in clause 5.13.3 of TS 23.682[38] step 2.
14.1A Restart of a peer node
14.1A.1 SGW Failure
When an MME detects that a peer SGW has failed with or without restart (relying on restart counter as specified in clause 18 "GTP-C based restart procedures" or implementation e.g. preconfigured path failure timer) it shall either:
- as a default delete all PDN connection table data/MM bearer contexts associated with the peer node that has failed as well as freeing any internal MME resources associated with those PDN connections. The MME may optionally perform other implementation specific actions such as to clear external resources (e.g. S1-MME messages to clear eNodeB resources) or more advanced forms of restoration;
or
- follow the procedures specified in clause 27 to restore the PDN connections affected by the SGW failure, if the MME and the PGW support these procedures.
NOTE: The MME will have the identity of the PGW and SGW currently in use for a PDN connection available in the MME's PDN connection table as part of existing EPC procedures as well as other peer state data.
14.1A.2 MBMS GW failure
The behaviour of an MME when it detects that a peer MBMS GW hast restarted is described in clause 17A.1.
14.1A.3 MCE Restart
When the MME detects a restart in an MCE (i.e. when the MME receives an M3 Reset or M3 Setup Request message from the MCE) with which it has at least one MBMS Bearer context, the MME shall behave as specified in clause 15A.3.
14.1A.4 UCMF Failure
When an MME detects that a peer UCMF has failed with or without restart (relying on restart counter as specified in clause 19B "URCMP based restart procedures" or implementation e.g. a preconfigured path failure timer as specified in clause 20 "Path management procedures"), it shall consider the dictionary mapping information received from the failed UCMF is deprecated, the subscription to get notifications from the UCMF become invalid; the MME may retrieve such mapping information upon subsequent UE - AMF signalling e.g. at registration procedure. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.2 VLR associations | All associations with VLRs affected by the restart of an MME are marked as unreliable and may be deleted. Based on configuration data, Reset messages may be sent on the SGs interface to the VLRs served by the MME. If Reset messages are sent, the VLRs may mark all associations with the MME as unreliable by setting the restoration indicator "Confirmed by radio contact" to "Not Confirmed" for the UEs served by that MME. See 3GPP TS 29.118 [14]. The associations will be re-initiated one by one by the MME at the next Combined TA/LA update from each UE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3 Partial Failure Handling at MME | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.1 General | See Clause 23. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.2 Procedures during PDN Connection Establishment | If the MME supports the feature, the following procedures apply.
During a PDN connection establishment, the MME shall provide one MME FQ-CSID containing exactly one CSID for that particular PDN connection to the SGW in the S11 Create Session Request. The MME shall store the Node-ID and CSID values from the FQ-CSID provided by the SGW and the PGW in the S11 Create Session Response in its PDN Connection table maintained as part of MME MM and EPS Bearer Contexts as specified in Table 5.6.2-15.7.2-1 in 3GPP TS 23.401 [15].
The MME should ensure as far as possible that previously used FQ-CSIDs are not immediately reused after a partial/full failure of an MME.
The MME determines that the SGW supports partial failure handling by the presence of the SGW FQ-CSID in the S11 Create Session Response. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.3 Procedures during MME Partial Failure | If the MME supports the feature the following procedures apply.
When an MME detects that it has undergone a partial failure, it shall verify that one or more corresponding CSID(s) are present for the component(s) undergoing a partial fault. If there is no such CSID, then the following does not apply. When one or more CSIDs are currently assigned, the MME shall perform the following.
The MME may perform implementation-specific operations to clean up any residual state associated with the CSID(s).
The MME shall send a GTPv2 Delete PDN Connection Set Request containing all the MME CSID(s) of the component(s) failing in MME FQ-CSID(s) to the SGW peers that support the feature.
Upon receiving a GTPv2 Delete PDN Connection Set Response message with Cause value "Success", the MME shall conclude that the SGW peer has initiated the internal deletion of the PDN connections corresponding to the FQ-CSID(s) present in the GTPv2 Delete PDN Connection Set Request message.
Regardless of the "Cause" value in the response, the MME is not required to perform any further recovery actions towards SGW and PGW peers for PDN connections in the connection set identified by the MME FQ-CSID(s). |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.4 Procedures during a Peer's Partial Failure | If the MME supports the feature, the following procedures apply.
When an MME receives a GTPv2 Delete PDN Connection Set Request message from an SGW, the MME shall retrieve all the PDN connections corresponding to each of the FQ-CSID(s) present in the message. The MME shall delete all the retrieved PDN connections and the associated resources. Other implementation-specific actions may be performed.
As a response, the MME shall send a GTPv2 Delete PDN Connection Set Response message with appropriate Cause value immediately to the SGW. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 14.3.5 Procedures during PDN Connection Removal or Modification | If an MME and an SGW support the feature, the following procedures apply.
During an S11 procedure, impacting an existing PDN connection removal or modification the following apply:
1) If the SGW is being relocated then the MME shall clear the currently stored SGW FQ‑CSID .
2) If an MME relocation occurs (for example, TAU with MME change), or if an SGW relocation occurs, (for example, TAU with SGW change), the MME shall include its MME FQ-CSID in the S11 Create Session Request for SGW change and the S11 Modify Bearer Request for MME change without SGW change.
3) Additionally, if MME decides to change own FQ-CSID, the MME shall include MME FQ-CSID in other S11 messages.
4) If the MME receives a FQ-CSID value of an SGW over S11, the MME shall overwrite the current stored SGW FQ‑CSID value with the received value.
5) If the MME receives a FQ-CSID value of a PGW over S11, the MME shall overwrite the current stored PGW FQ‑CSID value with the received value.
6) During a S11 procedure removing an existing PDN connection the MME removes the PDN data as well as any stored FQ-CSID values(s) of the PGW FQ-CSID and SGW FQ-CSID. The same actions are done on the old MME if there is an MME relocation.
The MME determines that the SGW supports partial failure handling by the presence of the SGW FQ-CSID in the S11 Create Session Response with SGW change; and S11 Modify Bearer Response without SGW change. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15 Restoration of data in GERAN/UTRAN | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.1 BSS Failure (A/Gb mode) | When a BSS fails, all its BSS contexts affected by the failure become invalid and shall be deleted. BSS storage of data is volatile. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.2 RNC/BSC Failure (Iu mode) | When an RNC/BSC fails, all its RNC/BSC contexts affected by the failure become invalid and shall be deleted. RNC/BSC storage of data is volatile. An SGSN that recognises unavailability of an RNC/BSC or receives a Reset from an RNC/BSC, shall locally release the RABs for all affected PDP contexts.
Any affected PDP contexts that use Direct Tunnel and have an invalid tunnel in GGSN will be recovered when the SGSN receives an Iu connection establishment request from the MS or when the GGSN informed the SGSN that the GGSN has received a GTP error indication from RNC.
When the RNC/BSC receives a GTP‑U PDU for which no RAB context exists, the RNC/BSC shall discard the GTP‑U PDU and return a GTP error indication to the originating node that may be SGSN or GGSN if Direct Tunnel is established.
The RNC should ensure as far as possible that previously used TEID values are not immediately reused after an RNC restart, in order to avoid inconsistent TEID allocation throughout the network. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.3 RNC/BSC Failure (Iu mode) using S4 | When an RNC/BSC fails, all its RNC/BSC contexts affected by the failure become invalid and shall be deleted. RNC/BSC storage of data is volatile. An SGSN that recognises unavailability of an RNC/BSC or receives a Reset from an RNC/BSC, shall locally release the RABs for all affected PDP contexts. If ISR is activated or direct tunnel is established, the S4-SGSN shall initiate release of the access bearer for all bearers towards the Serving GW as defined in Iu Release Procedure Using S4 in 3GPP TS 23.060 [5]. For the other cases, the S4-SGSN may send the Release Access Bearers Request message to the Serving GW to remove the downlink user plane address and TEID as specified in 3GPP TS 23.060 [5]. In addition, based on operator policy, the SGSN may initiate the Dedicated Bearer Deactivation procedure for bearers using streaming or conversational traffic class. Any affected EPS bearers contexts in Serving GW are recovered when the SGSN receives an Iu connection establishment request from the MS or when the Serving GW initiates the Network Triggered Service Request procedure as specified in 3GPP TS 23.060 [5].
When the RNC/BSC receives a GTP‑U PDU for which no RAB Context exists, the RNC/BSC shall discard the GTP‑U PDU and return a GTP Error Indication to the originating node that may be SGSN or Serving GW if Direct Tunnel is established.
An S4-SGSN that recognises unavailability of an RNC (e.g. no more SCTP association in service) or receives a Reset message from an RNC shall maintain the related MBMS bearer contexts but shall locally delete the RNC related information (i.e. Iu related resources) for all MBMS service association(s) or those indicated in the Reset message. See clause 8.26 of 3GPP TS 25.413 [29].
Upon receipt of a Reset message from the RNC, the S4-SGSN should then subsequently re-establish the MBMS bearer services affected by the RNC failure by initiating MBMS Session Start procedure(s) towards the RNC. The S4-SGSN shall encode the contents of the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or per the last MBMS Session Update Request received from the MBMS GW if the original parameters were updated) with the following exceptions:
- if the S4-SGSN has received recently an MBMS session re-establishment indication from the MBMS GW (i.e. within a past short period covering the time during which the same MBMS session may exist simultaneously in two S4-SGSNs of the S4-SGSN pool), the S4-SGSN shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session. Otherwise, the S4-SGSN shall not set "MBMS session re-establishment indication" flag;
- the S4-SGSN should set the estimated session duration to a value corresponding to the remaining duration of the session.
NOTE 1: During an Sn path failure when the MBMS GW moves the control of an MBMS session to an alternative S4-SGSN in the S4-SGSN pool (see clause 20.2.3.2), the MBMS session can exist in the old and in the new S4-SGSN for a short period of time. This time period is not bigger than the value of the maximum Sm path failure timer configured at the S4-SGSN. If an RNC happens to restart during this time, both S4-SGSNs will try to re-establish the MBMS session. In this case, it needs to be ensured that the control of the MBMS session remains at the new S4-SGSN, whatever the order of the MBMS Session Start Request messages the RNC will receive from both S4-SGSNs. The setting of the "MBMS session re-establishment indication" flag by the new S4-SGSN as specified above ensures that the new S4-SGSN, which has acquired the control of the MBMS session in the recent past, will get the control of the MBMS session.
NOTE 2: If the S4-SGSN receives an MBMS Session Update Request from the MBMS GW during the RNC failure, the contents of the MBMS Session Start Request sent to the RNC after the RNC recovery can also differ from the parameters sent to the RNC before its failure for the parameters that can be modified by the MBMS session update procedure (i.e. MBMS Session Area, MBMS Time to Data Transfer). |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.4 Other RNC functionality for MBMS restoration | The RNC should accept an MBMS Session Start Request received for an ongoing MBMS session (i.e. with the same TMGI)
- from the same or a different SGSN than the SGSN that currently controls the MBMS session, if the message contains the "MBMS session re-establishment indication" flag; or
- from the SGSN that currently controls the MBMS session, if the RNC supports the option to maintain MBMS bearer contexts during a pre-configured time period after an Iu path failure and the message is received during that period without the "MBMS session re-establishment indication" flag.
If it accepts the request from the SGSN, and if the message contains the "MBMS session re-establishment indication" flag, the RNC shall:
- replace the Iu related resources for this MBMS service associated to the previous SGSN by those assigned in the MBMS Session Request (if different) and consider that the MBMS session is now being controlled by the new SGSN (if different from the previous SGSN); for IP Unicast over Iu, the RNC receives the user plane data for this MBMS session via the new SGSN (if different from the previous SGSN);
- the RNC shall leave the former M1 transport network IP multicast address and join the new M1 transport network IP multicast address (including the IP address of the multicast source) if the MBMS Session Start Request contains a different transport network IP multicast distribution address and/or a different IP multicast source address; the RNC shall also use the C-TEID received in the MBMS Session Start Request
NOTE: This can also result in a change from IP Multicast to IP unicast or vice versa for the Iu userplane. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 15.5 Iu path failure using S4 | Upon detection of an Iu path failure (i.e. no more SCTP association in service),
- the RNC shall release all the MBMS services affected by the Iu path failure either immediately or after a pre-configured time period if the corresponding MBMS bearer contexts are not re-established via any S4-SGSN;
- the S4-SGSN shall maintain the related MBMS bearer contexts but shall locally delete the RNC related information (i.e. Iu related resources) for all MBMS service association(s).
Upon recovery of the Iu path, the RNC should initiate a Reset procedure towards the related S4-SGSN. Upon receipt of the Reset message from the RNC, the S4-SGSN should behave as specified for RNC failure in clause 15.3.
15A Restoration of data in E-UTRAN
15A.1 eNodeB Failure
15A.1.1 General
An MME which does not support UE context retention at SCTP recovery and recognises unavailability of an eNodeB (e.g. no more SCTP association in service) or an MME which receives a Reset or a S1 Setup message with UE Retention Information not set to "ues-retained" from an eNodeB, shall locally delete the eNodeB related information ("eNodeB Address in Use for S1-MME" and "eNodeB UE S1AP ID"). In this case, the MME initiates release of all S1 bearers towards the Serving GW by sending a Release Access Bearer Request message as defined in the S1 Release procedure in 3GPP TS 23.401 [15]. The MME shall initiate the Dedicated Bearer Deactivation procedure to deactivate the GBR bearers in the packet core; as an option, the MME may defer the deactivation of the GBR bearers for a short period (e.g. in the order of seconds) so as to allow the re-establishment of the corresponding radio and S1 bearers and thus avoid the GBR bearers deactivation if the MME receives a NAS Service Request or a GTP-C Downlink Data Notification message as a result of the SGW having received an Error Indication message from the eNodeB (see clause 22).
If the Serving GW receives Release Access Bearers Request message, the Serving GW shall release all eNodeB related information (address and TEIDs) for the UE, but other elements of the UE's Serving GW context shall not be affected. Any Bearer contexts affected by eNodeB failure that have no valid S1-U tunnel in Serving GW are recovered during the UE Triggered Service Request or during the Network Triggered Service Request procedure as specified in 3GPP TS 23.401 [15].
An MME, which supports UE context retention at SCTP recovery and recognises unavailability of an eNodeB (e.g. no more SCTP association in service), shall keep the UEs in ECM-CONNECTED and suspended UE Context data for UEs in ECM-IDLE, which have used the S1 signalling connection before it was broken. Upon the subsequent S1 Setup procedure, the MME and the eNB may agree that UE-related contexts and related signalling connection that have been existing before the S1 Setup shall not be affected as specified in the clause 19.2.2.8 of 3GPP TS 36.300 [32].
The eNodeB should ensure as far as possible that previously used TEID values are not immediately reused after an eNodeB restart, in order to avoid inconsistent TEID allocation throughout the network.
15A.1.2 PWS restoration
After an (H)eNodeB has restarted, it shall delete all its warning message data. If the warning message service is operational in one or more cell(s) of the (H)eNodeB, the (H)eNodeB shall send a PWS Restart Indication message, which shall include the identity of the (H)eNodeB, the identity of the restarted cell(s), and the TAI(s) and EAI(s) with which the restarted cell(s) are configured, to the CBC to request the CBC to re-load its warning message data if applicable.
The (H)eNB should send the PWS Restart Indication message via two MMEs of the MME pool, if possible, to ensure that the CBC receives the message even if one MME cannot propagate it to the CBC (e.g. due to an SBc path failure).
For HeNBs, the HeNB GW (respectively the MME) shall check the cell identity (respectively the HeNB identity) received in the PWS Restart Indication, as specified in clause 4.6.2 of 3GPP TS 36.300 [32].
Upon receipt of a PWS Restart Indication message, the CBC shall consider that the warning message service is restarted in the reported cell(s), i.e. the service is operational and no warning messages are being broadcast in the cell(s). The CBC shall then re-send the warning message data (with the same message identifier and serial number) to the (H)eNodeB for these cells, if any. When doing so, the CBC:
- shall include the identity of the (H)eNodeB received in the PWS Restart Indication into the Write-Replace-Warning-Request message(s) to enable the MME to forward the message(s) only to the (H)eNodeB (or HeNB GW) involved in the restart;
- should set the warning area list to the identities of the cell(s) to be reloaded which are relevant to the warning message data being reloaded; and
- may update the number of broadcasts requested, if necessary.
NOTE 1: Setting the warning area list to the identities of the cell(s) to be reloaded enables, for example, the HeNB GW to forward the message only to the involved HeNB when the restarted HeNB is connected to a HeNB GW.
The CBC shall consider a PWS Restart Indication message received shortly after a preceding one for the same cell identity as a duplicate restart indication for that cell which it shall ignore.
NOTE 2: The broadcast of warning messages can be configured in the network per individual cell, TAI and/or EAI. The CBC can use the list of cell(s), the TAI(s) and EAI(s) received in the PWS Restart Indication to derive the list of warning messages to be broadcast in the respective cell(s), TAI(s) and EAI(s).
Likewise, in other scenarios where the (H)eNodeB may need to reload its warning message data (e.g. when an individual cell is restarted), the (H)eNodeB shall send a PWS Restart Indication message (including the identity of the (H)eNodeB, the identity of the restarted cell(s), and the TAI(s) and EAI(s) with which the restarted cell(s) are configured) to the CBC to request the CBC to re-load its warning message data if applicable. The (H)eNodeB, MME and CBC shall then proceed as specified above for an (H)eNodeB restart.
15A.2 S1-AP path failure
Upon detection of an S1-AP path failure (i.e. no more SCTP association in service),
- the eNodeB shall either release the RRC connection of the affected UEs, or if UE context retention at SCTP recovery is supported, the eNodeB shall keep those UEs in RRC_CONNECTED and suspended UE Context data for UEs in ECM-IDLE, which have used the S1 signalling connection before it was broken;
- the MME shall proceed as specified for the eNodeB failure in clause 15A.1.
The eNodeB shall continue to broadcast warning messages, if any, during an S1AP path failure. Upon recovery of the S1AP path, the eNodeB shall proceed as if no S1AP path failure had occurred.
During an S1AP path failure, the warning message data stored in the eNodeB may become desynchronized with the CBC, e.g. if the CBC attempts to modify the warning message data during the S1AP path failure. The CBC and MME(s) should support the Write-Replace-Warning-Indication and Stop-Warning-Indication procedures (see 3GPP TS 23.041 [30]) to keep the warning message data synchronized in the eNodeB and the CBC.
15A.3 MCE Failure
When an MCE fails, the MCE shall release all the MBMS services affected by the failure locally and towards E-UTRAN within which the MBMS bearer services are active, either immediately or after a pre-configured time period if the corresponding MBMS bearer contexts are not re-established via any MME.
An MME that recognises unavailability of an MCE (e.g. no more SCTP association in service) or receives a Reset or a M3 Setup Request message from an MCE shall maintain the related MBMS bearer contexts but shall locally delete the MCE related information (i.e. M3 related resources) for all MBMS service association(s) or those indicated in the RESET message. See clauses 8.5 and 8.7 of 3GPP TS 36.444 [28].
Upon receipt of a Reset or M3 Setup Request message from the MCE, the MME should then subsequently re-establish the MBMS bearer services affected by the MCE failure by initiating MBMS Session Start procedure(s) towards the MCE. The MME shall encode the contents of the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or per the last MBMS Session Update Request received from the MBMS GW if the original parameters were updated) with the following exceptions:
- if the MME has received recently an MBMS session re-establishment indication from the MBMS GW (i.e. within a past short period covering the time during which the same MBMS session may exist simultaneously in two MMEs of the MME pool), the MME shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session. Otherwise, the MME shall not set "MBMS session re-establishment indication" flag;
- if no absolute start time ("MBMS data transfer start" parameter) has been received, the MME may change the relative start time ("time to MBMS data transfer" parameter) to fasten the restoration of the MBMS service in E-UTRAN;
- the MME should set the estimated session duration to a value corresponding to the remaining duration of the session.
The MCE shall be able to accept MBMS session requests with an absolute start time ("MBMS data transfer start" parameter) in the past.
NOTE 1: During an Sm path failure when the MBMS GW moves the control of an MBMS session to an alternative MME in the MME pool (see clause 20.2.3.1), the MBMS session can exist in the old and in the new MME for a short period of time. This time period is not bigger than the value of the maximum Sm path failure timer configured at the MME. If an MCE happens to restart during this time, both MMEs will try to re-establish the MBMS session. In this case, it needs to be ensured that the control of the MBMS session remains at the new MME, whatever the order of the MBMS Session Start Request messages the MCE will receive from both MMEs. The setting of the "MBMS session re-establishment indication" flag by the new MME as specified above ensures that the new MME, which has acquired the control of the MBMS session in the recent past, will get the control of the MBMS session.
NOTE 2: If the MME receives an MBMS Session Update Request from the MBMS GW during the MCE failure, the contents of the MBMS Session Start Request sent to the MCE after the MCE recovery can also differ from the parameters sent to the MCE before its failure for the parameters that can be modified by the MBMS session update procedure (i.e. MBMS Session Area, MBMS Time to Data Transfer, MBMS Data Transfer Start).
15A.4 M3AP path failure
Upon detection of an M3AP path failure (i.e. no more SCTP association in service),
- the MCE shall release all the MBMS services affected by the M3AP path failure locally and towards E-UTRAN within which the MBMS bearer services are active, either immediately or after a pre-configured time period if the corresponding MBMS bearer contexts are not re-established via any MME;
- the MME shall maintain the related MBMS bearer contexts but shall locally delete the MCE related information (i.e. M3 related resources) for all MBMS service association(s).
Upon recovery of the M3AP path, the MCE should initiate a Reset or M3 Setup Request procedure towards the related MME. Upon receipt of the Reset or M3 Setup Request message from the MCE, the MME should then subsequently re-establish the MBMS bearer services affected by the M3AP path failure by initiating MBMS Session Start procedure(s) towards the MCE. The MME shall encode the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or per the last MBMS Session Update Request received from the MBMS GW if the original parameters were updated) with the following exceptions:
- if the MME has received recently an MBMS session re-establishment indication from the MBMS GW (i.e. within a past short period covering the time during which the same MBMS session may exist simultaneously in two MMEs of the MME pool), the MME shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session. Otherwise, the MME shall not set "MBMS session re-establishment indication" flag;
- if no absolute start time ("MBMS data transfer start" parameter) has been received, the MME may change the relative start time ("time to MBMS data transfer" parameter) to fasten the restoration of the MBMS service in E-UTRAN;
- the MME should set the estimated session duration to a value corresponding to the remaining duration of the session.
The MCE shall be able to accept MBMS session requests with an absolute start time ("MBMS data transfer start" parameter) in the past.
NOTE 1: During an Sm path failure when the MBMS GW moves the control of an MBMS session to an alternative MME in the MME pool (see clause 20.2.3.1), the MBMS session can exist in the old and in the new MME for a short period of time. This time period is not bigger than the value of the maximum Sm path failure timer configured at the MME. If an M3AP path failure and recovery happens during this time, both MMEs will try to re-establish the MBMS session. In this case, it needs to be ensured that the control of the MBMS session remains at the new MME, whatever the order of the MBMS Session Start Request messages the MCE will receive from both MMEs. The setting of the "MBMS session re-establishment indication" flag by the new MME as specified above ensures that the new MME, which has acquired the control of the MBMS session in the recent past, will get the control of the MBMS session.
NOTE 2: If the MME receives an MBMS Session Update Request from the MBMS GW during the M3AP path failure, the contents of the MBMS Session Start Request sent to the MCE after the M3AP path recovery can also differ from the parameters sent to the MCE before the M3AP path failure for the parameters that can be modified by the MBMS session update procedure (i.e. MBMS Session Area, MBMS Time to Data Transfer, MBMS Data Transfer Start).
15A.5 Other MCE functionality for MBMS restoration
The MCE should accept an MBMS Session Start Request received for an on-going MBMS session (i.e. with the same TMGI)
- from the same or a different MME than the MME that currently controls the MBMS session, if the message includes the "MBMS session re-establishment indication" flag; or
- from the MME that currently controls the MBMS session, if the MCE supports the option to maintain MBMS bearer contexts during a pre-configured time period after an M3AP path failure, MME restart or MCE failure, and the message is received during that period without the "MBMS session re-establishment indication" flag.
If the MCE accepts the request from the MME, and if the message contains the "MBMS session re-establishment indication" flag,
- the MCE shall replace the M3 related resources for this MBMS service associated to the previous MME by those assigned in the MBMS Session Start Request (if different) and consider that the MBMS session is now being controlled by the new MME (if different from the previous MME);
- the eNodeB(s) involved in the broadcast of the MBMS session shall leave the former M1 transport network IP multicast address and join the new M1 transport network IP multicast address (including the IP address of the multicast source) if the MBMS Session Start Request contains a different transport network IP multicast distribution address and/or a different IP multicast source address; the eNodeB(s) shall also use the C-TEID received in the MBMS Session Start Request.
The MCE shall be able to accept MBMS session start/update/stop requests with an absolute start time ("MBMS data transfer start" or "MBMS data transfer stop" parameter) in the past.
15A.6 Other MME related functionality for MBMS restoration
When establishing MBMS bearer services in an MCE to ensure the distribution of content from ongoing MBMS sessions to an MCE which modifies the lists of the MBMS Service Areas it serves via the MCE Configuration Update procedure (see clause 5.9.2 of 3GPP TS 23.246 [12]), the MME shall encode the MBMS Session Start Request as specified in clause 15A.3 upon receipt of a Reset or M3 Setup Request message from the MCE. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16 Restoration of data in the SGW | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 16.1 Restart of the SGW |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.