10.12.2012 Views

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Page 366<br />

<strong>GSM</strong> <strong>09.02</strong> <strong>Version</strong> <strong>5.3.0</strong>: August 1996<br />

16.3.2 HLR fault recovery procedures<br />

The following processes are involved with the restart of the HLR:<br />

- HLR_RESTART subclause 16.3.2;<br />

- REC_RESET_IN_VLR subclause 16.3.2.<br />

In the case of a location registration request from the MS, the following processes are involved with the<br />

HLR restoration procedure:<br />

- Update_Location_Area_VLR subclause 16.1.1.3;<br />

- Update_Location_HLR subclause 16.1.1.4.<br />

In the case of a mobile originated service request, the<br />

- Macro Process_Access_Request_VLR subclause 21.4.2; and the<br />

- Process Update_Location_HLR subclause 16.1.1.4,<br />

are involved with the HLR restoration procedure.<br />

For the HLR, periodic back-up of data to non-volatile memory is mandatory.<br />

Data that have been changed in the period of time after the last back-up storage and before the restart of<br />

the HLR cannot be recovered by reload from the non-volatile memory. Therefore, a restoration procedure<br />

is triggered individually for each IMSI record that has been affected by the HLR fault at the first<br />

authenticated radio contact that is established with the MS concerned.<br />

The HLR restoration procedure forces updating of MSC number, VLR number and, if provided by the VLR,<br />

LMSI in the HLR. Consistency of subscriber data that are stored in the VLR for an MS that has been<br />

affected by a HLR fault with the subscriber data stored in the HLR for this MS will be achieved.<br />

As an implementation option, a notification can be forwarded to the MS to alert the subscriber to check the<br />

parameters for supplementary services that allow subscriber controlled input<br />

(MAP_FORWARD_CHECK_SS_INDICATION service). If the VLR receives this notification from the HLR it<br />

shall forward the notification to the MS.<br />

Figure 16.3/2 illustrates the signalling sequence for HLR restoration.<br />

After a restart, the home location register performs the following actions for the subscriber data records<br />

that have been affected by the HLR fault (see figure 16.3/3):<br />

- reload all data from the non-volatile back-up;<br />

- if the MAP_FORWARD_CHECK_SS_INDICATION service is implemented, mark each subscriber<br />

record "SS Check Required" by setting the "Check SS" indicator;<br />

- set subscriber tracing deactive in the VLR for each of its Mss;<br />

- reset the "MS Purged" flag for each of its MSs;<br />

- send a MAP_RESET request to the VLRs where its MSs are located (see figure 16.3/4).<br />

The MAP_RESET request contains the HLR number and optionally the HLR Identity List.<br />

When receiving a MAP_RESET indication, the VLR will derive all involved MSs of that HLR either from the<br />

HLR Identity List (if present), or from the HLR number. The VLR will then mark these MSs with the<br />

indicator "Location Information Confirmed in HLR" set to "Not Confirmed" and will deactivate all subscriber<br />

tracings for these Mss (see figure 16.3/5).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!