Tech-invite   3GPPspecs   Glossaries   IETFRFCs   Groups   SIP   ABNFs   Ti+   Search in Tech-invite

Top   in Index   Prev   Next

TS 23.007 (CT4)
Restoration Procedures

3GPP‑Page   ETSI‑search   short‑ToC   full‑ToC   References    
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.3.0 (PDF)2019/06  110 p.
V14.6.0  2019/03  106 p.
V13.7.0  2017/06  100 p.
V12.9.0  2015/12  95 p.
V11.8.0  2014/03  72 p.
V10.7.0  2012/03  54 p.
V9.10.0  2011/12  42 p.
V8.9.0  2010/12  39 p.
V7.0.0  2006/06  22 p.
V6.2.0  2005/12  22 p.
V5.1.0  2004/01  22 p.
V4.2.0  2004/01  22 p.
V3.6.0  2004/01  22 p.
GSM Rel-98 v7.1.0  1999/12  21 p.
GSM Rel-97 v6.2.0  1999/06  18 p.
GSM Rel-96 v5.1.0  1997/10  18 p.
GSM Phase-2 v4.3.1  1996/01  15 p.
GSM Phase-1 v3.2.1  1992/02  13 p.


Rapporteur:  Mr. Lu, Fei

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. This TS 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 TS 29.002 and TS 29.060.
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.

short Table of Contents for  TS 23.007  Word version:   15.3.0

each level-1 title links to the equivalent title in the full ToC

 

Here   Top

 

1  Scope [R3]Word-p. 10
2  Design objectives [R3]Word-p. 12
3  Restoration indicators in location registers and in GPRS support nodes [R3]Word-p. 13
4  Restoration of data in the VLR [R3]Word-p. 18
5  Restoration of data in the HLR/HSS [R3]Word-p. 25
6  Periodic location updating [R3]Word-p. 27
7  Periodic routeing area updating [R3]
8  Stand-alone operation of the VLR [R3]
9  Stand-alone operation of the SGSN [R3]Word-p. 28
9A  Stand-alone operation of the MME [R8]
10  Restoration of data in the GGSN [R3]Up
11  Restoration of data in the SGSN [R3]Word-p. 29
12  Restoration of Data in an SMLC (GSM only) [R3]Word-p. 33
13  Restoration of Data in an LMU (GSM only) [R3]Word-p. 34
14  Restoration of data in the MME [R8]
15  Restoration of data in GERAN/UTRAN [R8]Word-p. 38
15A  Restoration of data in E-UTRAN [R8]Word-p. 40
16  Restoration of data in the SGW [R8]Word-p. 44
17  Restoration of data in the PGW [R8]Word-p. 51
17A  Restoration of data in the MBMS GW [R9]Word-p. 55
17B  Restoration of data in the ePDG [R10]Word-p. 56
17C  Restoration of data in the TWAN [R11]Word-p. 58
17D  Restoration of data in the BM-SC [R12]Word-p. 60
17E  Restoration of data in the GCS AS [R12]Word-p. 61
18  GTP-C based restart procedures [R8]
19  PMIPv6 based restart procedures [R8]Word-p. 62
19A  PFCP based restart procedures [R14]
20  Path management procedures [R8]Word-p. 63
21  Error Indication handling [R8]Word-p. 76
22  Downlink Data Notification Handling at MME/S4 SGSN [R8]Word-p. 80
23  General partial failure handling procedures [R9]Up
24  Restoration of data in the PCRF [R10]Word-p. 86
25  Network triggered service restoration procedure [R10]
26  Mobile terminated CS service delivery via an alternative MME in MME pool [R11]Word-p. 90
27  Restoration of PDN connections after an SGW failure [R11]Word-p. 92
28  Restoration of data in the CSS [R11]Word-p. 100
29  MBMS Heartbeat procedure [R12]
30  Restoration of the SCEF [R13]Word-p. 101
A  Change historyWord-p. 102

Up   Top