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 740<br />

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

Annex C (informative): Formal protocol incompatibilities between versions 1<br />

and 2 of MAP<br />

C.1 Introduction<br />

Annex C is not normative; it presents for information those parts of the MAP version 2 protocol which are<br />

not backward compatible with (i.e. a true superset of) the MAP version 1 protocol. For each incompatibility<br />

there is a commentary on the impact on the interworking of MAP version 1 and MAP version 2 entities.<br />

SMG have decided that the MAP specification should include the operations and procedures used on the B<br />

interface (MSC/VLR) only for modelling purposes; the B interface cannot be implemented as an open<br />

interface. Hence any incompatibilities which affect operations used only on the B interface have no impact<br />

on the interworking of MAP version 1 and MAP version 2 entities.<br />

C.2 Deletion of operations and errors<br />

This subclause lists the operations and errors which have been completely removed from the MAP<br />

protocol.<br />

C.2.1 Deletion of operation DeregisterMobileSubscriber<br />

Although it is defined in the protocol in the MAP version 1 specification, this operation is not used<br />

(see subclause 1.2 of the latest phase 1 version of TS <strong>GSM</strong> <strong>09.02</strong>).<br />

C.2.2 Deletion of operation RegisterChargingInfo<br />

There is no known implementation of MAP version 1 which supports this operation. The deletion has been<br />

approved by SMG.<br />

C.2.3 Deletion of operation ForwardSS-Notification<br />

There is no known implementation of MAP version 1 which supports this operation. The deletion has been<br />

approved by SMG.<br />

C.2.4 Deletion of operations used only on the B-interface<br />

The following operations (listed in alphabetical order) are not defined in the MAP version 2 protocol,<br />

because they are used only on the B-interface:<br />

AllocateHandoverNumber; AttachIMSI; Authenticate; CompleteCall; DetachIMSI; ForwardNewTMSI;<br />

InvokeSS; Page; ProcessAccessRequest; ProvideIMSI; SearchForMobileSubscriber;<br />

SendHandoverReport; SendInfoForIncomingCall; SendInfoForOutgoingCall; SetCipheringMode;<br />

UpdateLocationArea.<br />

C.2.5 Deletion of error InsufficientBearerCapabilities<br />

This error is defined in the MAP version 1 protocol, but it is not specified for use with any operation.<br />

C.3 Deletion of errors for operations<br />

This subclause lists the cases where an error which is specified for use with an operation in the MAP<br />

version 1 specification is not specified for use with the same operation in the MAP version 2 specification.<br />

C.3.1 Error NegativePW-Check for operation RegisterSS<br />

Password checking is not used for the supplementary services to which registration applies.

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

Saved successfully!

Ooh no, something went wrong!