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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Page 626<br />

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

Error handling<br />

In case some error is detected during handling the access request, a respective error has been set.<br />

Before returning this error cause to the MSC in a MAP_PROCESS_ACCESS_REQUEST response, it<br />

need to be checked whether this access is for emergency call set-up, as this will require extra treatment.<br />

If the CM Service type given in the MAP_PROCESS_ACCESS_REQUEST indication is emergency call<br />

set-up, it is checked whether EC set-up in the particular error situation is permitted (operator option). If so,<br />

it is checked whether the IMEI is required, and if so the IMEI is requested from the MS (macro<br />

Obtain_IMEI_VLR, see subclause 21.6).<br />

The macro will terminate immediately with unsuccessful outcome if the MSC transaction has been<br />

aborted during the IMEI retrieval.<br />

In case of an error reported back from IMEI retrieval, MAP_PROCESS_ACCESS_REQUEST<br />

response containing the error cause set previously is returned to the MSC, the dialogue is closed<br />

(MAP_CLOSE request indicating normal release) and the macro terminates with unsuccessful<br />

outcome.<br />

When a subscriber identity required by the operator (IMSI or IMEI) is available, the user error set<br />

previously is deleted, the respective identity is returned in the MAP_PROCESS_ACCESS_REQUEST<br />

response to indicate acceptance of emergency call, and the macro terminates with successful outcome.<br />

In all other cases, the MAP_PROCESS_ACCESS_REQUEST response containing the error cause set<br />

previously is returned to the MSC, the dialogue is closed (MAP_CLOSE request indicating normal release)<br />

and the macro terminates with unsuccessful outcome.<br />

21.4.3 Macro Identification Procedure<br />

This macro is invoked by the macro Process_Access_Request_VLR in case the subscribers identity is not<br />

known in the VLR.<br />

If the identity received from the MS is an IMSI, the error Unidentified Subscriber will be set and reported<br />

back to the calling macro (to be sent in the MAP_PROCESS_ACCESS_REQUEST response). The same<br />

error is used in case a TMSI was received from the MS, but the operator does not allow open<br />

identification of the MS.<br />

If open identification of the MS is allowed, the macro Obtain_IMSI_VLR is invoked, requesting the<br />

subscribers IMSI from the MS (see subclause 21.8), with outcome<br />

OK, in which case it is checked whether for the IMSI received there exists a subscriber record in the<br />

VLR. If so, the macro terminates successfully, else the error Unidentified Subscriber will be set and<br />

reported back to the calling macro.<br />

Error, in which case the error System Failure will be set and reported back to the calling macro.<br />

Aborted, i.e. the MSC transaction is released, in which the macro terminates accordingly.

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

Saved successfully!

Ooh no, something went wrong!