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.

11 General<br />

11.1 Overview<br />

Page 151<br />

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

Clause 11 to 14 specify the protocol elements to be used to provide the MAP services described in<br />

clause 5.<br />

Clause 12 specifies the elements of procedures for the MAP protocol. Clause 13 specifies the mapping on<br />

to TC service primitives. Clause 14 specifies the application contexts, operation packages and abstract<br />

syntaxes for the MAP protocol as well as the encoding rules to be applied.<br />

11.2 Underlying services<br />

The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of signalling system<br />

number 7, as referenced in clause 4.<br />

11.3 Model<br />

The MAP Protocol Machine (MAP PM) can be modelled as a collection of service state machines (SSMs) -<br />

one per MAP specific service invoked - coordinated by a MAP dialogue control function with its one state<br />

machine: MAP dialogue state machine (DSM). There are two types of Service State Machines: Requesting<br />

Service State Machines (RSM) and Performing Service State Machines (PSM).<br />

A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a<br />

TC-BEGIN indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific<br />

service invoked during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is<br />

created at the performer's side.<br />

This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not<br />

intended to suggest any implementation. SDL descriptions are organized according to this model.<br />

How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local<br />

implementation matter.<br />

How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.<br />

11.4 Conventions<br />

The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One<br />

major difference is that the MAP requests the transfer of the application-context-name by TC only for<br />

those contexts which do not belong to the so-called "version one context set".<br />

The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1<br />

implementation according to the latest phase 1 version of TS <strong>GSM</strong> <strong>09.02</strong>. This set is defined in clause 12.<br />

The procedures described in clause 12 are used when the application-context-name does not refer to a<br />

dialogue between an MSC and its VLR. When the application-context-name refers to a dialogue between<br />

an MSC and its VLR the MAP PM procedures are a local implementation matter.

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

Saved successfully!

Ooh no, something went wrong!