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

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

13.1.2.6 P-Abort-Cause<br />

Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the<br />

MAP-P-ABORT indication primitive according to table 13.1/1, except in the dialogue initiated phase for the<br />

"incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the<br />

"potential incompatibility problem" value of the refuse-reason parameter of the MAP-OPEN cnf primitive.<br />

The source parameter in the MAP-P-ABORT ind takes the value "TC problem".<br />

13.1.2.7 Quality of service<br />

The quality of service of TC request primitives is set by the MAP as shown below.<br />

- Return option: "Return message on error" or "Discard message on error" as required by the network<br />

operator;<br />

- Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the<br />

network operator;<br />

"Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber<br />

data in response to SendParameters). It may also be appropriate to use Sequence guaranteed<br />

when a series of InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling<br />

operations is used.<br />

TC P-Abort cause MAP provider-reason<br />

unrecognized message type provider malfunction<br />

unrecognized transaction Id supporting dialogue released<br />

badlyFormattedTransactionPortion provider malfunction<br />

incorrectTransactionPortion provider malfunction (note)<br />

resourceLimitation resource limitation<br />

abnormalDialogue provider malfunction<br />

noCommonDialoguePortion version incompatibility<br />

NOTE: Or version incompatibility in the dialogue initiated phase.<br />

Table 13.1/1: Mapping of P-Abort cause in TC-P-ABORT indication on to provider-reason in<br />

MAP-P-ABORT indication<br />

13.2 Service specific procedures<br />

Specific services are mapped to TC component handling services.<br />

13.2.1 Directly mapped parameters<br />

The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id<br />

parameter of the component handling primitives.<br />

13.2.2 Use of other parameters of component handling primitives<br />

13.2.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.2.2.2 Class<br />

The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

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

Saved successfully!

Ooh no, something went wrong!