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.

12.6.8 Load control<br />

Page 165<br />

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

As stated in the previous subclauses, before issuing a MAP-OPEN indication primitive the MAP PM<br />

performs a check to verify if there are sufficient resources to open the dialogue taking into account<br />

possible overload conditions.<br />

The decision is based on the priority allocated to the application-context whose name is explicitly included<br />

in the TC-BEGIN indication primitive or implied by the first operation invocation when V1 contexts are in<br />

use. How a V1 application-context-name is derived from an operation code is described in table 12.1/1.<br />

The priority level allocated to each application-context is described in clause 3 tables 3.1/1 and 3.1/2.<br />

13 Mapping on to TC services<br />

13.1 Dialogue control<br />

Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by<br />

the MAP PM.<br />

13.1.1 Directly mapped parameters<br />

The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to<br />

the corresponding parameters of the TC-BEGIN primitives:<br />

- destination address;<br />

- originating address.<br />

13.1.2 Use of other parameters of dialogue handling primitives<br />

13.1.2.1 Dialogue Id<br />

The value of this parameter is associated with the MAP PM invocation in an implementation dependent<br />

manner.<br />

13.1.2.2 Application-context-name<br />

If it does not belong to the MAP V1 context set. The application-context-name parameter of a MAP<br />

primitive is mapped to the application-context-name parameter of TC dialogue handling primitives<br />

according to the rules described in subclause 12.1. Otherwise the application-context-name parameter of<br />

TC dialogue handling primitives is never included.<br />

13.1.2.3 User information<br />

The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.<br />

13.1.2.4 Component present<br />

This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to<br />

the MAP user.<br />

13.1.2.5 Termination<br />

The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the<br />

release method parameter of the MAP-CLOSE request primitive, except when the dialogue state machine<br />

is in the state DIALOGUE INITIATED, in which case the Termination parameter shall always indicate<br />

"pre-arranged end".

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

Saved successfully!

Ooh no, something went wrong!