Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.007  Word version:  19.0.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… 
4 Restoration of data in the VLR  4.0 VLR Failure with Restart  4.0a VLR Failure without Restart  4.1 Restart of the VLR  4.2 Restoration Procedures  4.2.0 General  4.2.1 Incoming Call  4.2.2 Mobile Terminated Short Message  4.2.3 Mobile Terminating Location Request (MT-LR)  4.2.4 Incoming LCS Information Request (GSM only)  4.2.5 Outgoing MS request  4.2.6 Outgoing LMU Request (GSM only)  4.2.7 Location Updating or IMSI Attach  4.2.8 Use of TMSI  4.2.9 SGSN associations  4.2.10 MME associations 
...

 

4  Restoration of data in the VLR  p. 18

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.

4.0  VLR Failure with Restart |R8|  p. 18

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

4.0a  VLR Failure without Restart |R11|  p. 19

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

4.1  Restart of the VLR  p. 20

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

4.2  Restoration Procedures  p. 20

4.2.0  General |R11|  p. 20

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.

4.2.1  Incoming Call  p. 20

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

4.2.2  Mobile Terminated Short Message  p. 21

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 TS 23.040 and TS 29.002; 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.
Up

4.2.3  Mobile Terminating Location Request (MT-LR)  p. 22

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

4.2.4  Incoming LCS Information Request (GSM only)  p. 23

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

4.2.5  Outgoing MS request  p. 23

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

4.2.6  Outgoing LMU Request (GSM only)  p. 24

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

4.2.7  Location Updating or IMSI Attach  p. 24

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

4.2.8  Use of TMSI  p. 25

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:
    1. 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.
    2. 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.
Up

4.2.9  SGSN associations  p. 25

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

4.2.10  MME associations |R8|  p. 25

Based on configuration data, "Reset" messages are sent on the SGs-interface to the MMEs by the VLR as described in the TS 29.118. 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.
Up

Up   Top   ToC