Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.007  Word version:  18.4.0

Top   Top   None   None   Next
1…   2…   4…   5…   6…   10…   11…   12…   14…   15…   15A…   16…   17…   17A…   17B…   17C…   18…   20…   20.3…   21…   22…   25…   27…   28…   31…   31.3…   31.4…   31.6…

 

1  Scopep. 10

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 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.
Up

1.1  Referencesp. 11

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]
TR 21.905: "Vocabulary of 3GPP Specifications ".
[2]  Void
[3]  Void
[4]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[5]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[6]
TS 29.002: "Mobile Application Part (MAP) specification".
[7]
TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification".
[8]
TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunneling Protocol (GTP) across the Gn and Gp interface".
[9]
TS 43.005: "Technical performance objectives".
[10]
TS 23.071: "Location Services (LCS); Functional description; Stage 2".
→ to date, withdrawn by 3GPP
[11]  Void
[12]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[13]
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[14]
TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification".
[15]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[16]
TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunneling protocols; Stage 3".
[17]
TS 29.281: "General Packet Radio System (GPRS) Tunneling Protocol User Plane (GTPv1-U)".
[18]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[19]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[20]
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[21]
TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping ".
[22]
RFC 5847:  "Heartbeat Mechanism for Proxy Mobile IPv6".
[23]
TS 23.018: "Basic call handling; Technical realization".
[24]
TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[25]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[26]
RFC 7077:  "Update Notifications for Proxy Mobile IPv6".
[27]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[28]
TS 36.444: "EUTRAN M3 Application Protocol (M3AP)".
[29]
TS 25.413: "UTRAN Iu interface RANAP signalling".
[30]
TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[31]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ".
[32]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[33]
TS 23.303: "Proximity based Services; Stage 2".
[34]
TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects; Stage 3".
[35]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[36]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[37]
TS 29.303: "Domain Name System Procedures; Stage 3".
[38]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[39]
TS 23.161: "Network-Based IP Flow Mobility (NBIFOM); Stage 2".
[40]
TS 23.285: "Architecture enhancements for V2X services; Stage 2".
[41]
TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)".
[42]
TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2".
[43]
TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; stage 3".
[44]
TS 29.674: " Interface between the UCMF and the MME; Stage 3".
[45]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[46]
TS 23.502: "Procedures for the 5G System; Stage 2".
[47]
TS 23.632: "User data interworking, coexistence and migration; Stage 2".
Up

1.2  Abbreviationsp. 12

For the purposes of the present document, the abbreviations listed in TR 21.905 apply.

1.3  Definitions |R13|p. 13

For the purposes of the present document, the terms and definitions given in TR 21.905 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.
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.
Up

Up   Top   ToC