Content for TS 23.012 Word version: 18.0.0

1… 4… 4.1.1.2 4.1.2… 4.1.2.1a 4.1.2.2 4.1.2.3 4.1.2.4… 4.1.2.6… 4.1.2.8… 4.1.2.10… 4.1.3… 4.1.3.2 4.1.3.3… 4.1.4… 4.2 4.2A 4.3 4.4…

4.4 Purge MS

4.4 Purge MS p. 64

4.4.1 Detailed procedure in the VLR p. 64

4.4.1.1 Procedure Purge_MS_VLR p. 64

Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in TS 23.116. If the VLR and the originating HLR support the Super-Charger functionality, processing continues from the "Yes" exit of the test "Result=Pass?".

Copy of original 3GPP image for 3GPP TS 23.012, Fig. 4.4.1.1-1: (Sheet 1 of 1) Procedure Purge_MS_VLR

Figure 4.4.1.1-1: (Sheet 1 of 1) Procedure Purge_MS_VLR
(⇒ copy of original 3GPP image)

4.4.2 Detailed procedure in the HLR p. 66

4.4.2.1 Process Purge_MS_HLR p. 66

The procedure Check_Parameters is specified in TS 23.018.

If the received VLR number and the stored VLR number do not match, the HLR sends Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different VLR area, it is not appropriate to block mobile terminated calls or short messages to the MS, but the VLR which initiated the purging procedure can safely purge its record for the MS without freezing the TMSI.

If the received SGSN number and the stored SGSN number do not match, the HLR sends a Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different SGSN area, it is not appropriate to block short messages to the MS, but the SGSN which initiated the purging procedure can safely purge its record for the MS without freezing the P-TMSI.

Copy of original 3GPP image for 3GPP TS 23.012, Fig. 4.4.2.1-1: (Sheet 1 of 1) Procedure Purge_MS_HLR