Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.007  Word version:  18.4.0

Top   Top   Up   Prev   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…

 

5  Restoration of data in the HLR/HSSp. 25

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.

5.1  Restart of the HLR/HSSp. 26

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 TS 23.303), 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 TS 23.285), 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".
Up

5.2  Procedures During Restorationp. 26

5.2.1  Mobile terminated callp. 26

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

5.2.2  Mobile Originated Activity for CSp. 26

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

5.2.3  Mobile Originated Activity for ProSe |R12|p. 26

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 TS 29.344.
When the HSS receives a "ProSe Subscriber Information Retrieval" request from the ProSe Function, it shall proceed as described in the TS 29.344.
Up

5.2.4  Procedures in the SGSN |R13|p. 27

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 TS 29.018).
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.
Up

5.2.5  Procedures in the MME |R13|p. 27

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 TS 29.118).
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.
Up

5.2.6  Mobile Originated Activity for V2X |R14|p. 27

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 TS 29.388.
When the HSS receives a "V2X Subscriber Information Retrieval" request from the V2X Control Function, it shall proceed as described in the TS 29.388.
Up

Up   Top   ToC