16.1 Dialogue control

09.023GPPMobile Application Part (MAP) specificationTS

Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP PM.

16.1.1 Directly mapped parameters

The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the corresponding parameters of the TC-BEGIN primitives:

– destination address;

– originating address.

16.1.2 Use of other parameters of dialogue handling primitives Dialogue Id

The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner. Application-context-name

The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of TC dialogue handling primitives according to the rules described in subclause 15.1. User information

The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs. Component present

This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP user. Termination

The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end". P-Abort-Cause

Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the MAP-P-ABORT indication primitive according to table 16.1/1, except in the dialogue initiated phase for the "incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the "potential incompatibility problem" value of the refuse-reason parameter of the MAP-OPEN cnf primitive. The source parameter in the MAP-P-ABORT ind takes the value "TC problem". Quality of service

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

– Return option: "Return message on error" or "Discard message on error" as required by the network operator;

– Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator;

"Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber data in response to SendParameters). It may also be appropriate to use Sequence guaranteed when a series of InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling operations is used.

It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue responder shall ensure that this requirement is met by:

– Sending the dialogue acceptance message in a TC‑END, if the dialogue structure requires it; or

– Using "Sequence guaranteed", if the dialogue acceptance message is sent in a TC‑CONTINUE; or

– Waiting until the dialogue acceptance message has been acknowledged by the dialogue initiator before sending a subsequent message, if the dialogue acceptance message is sent in a TC‑CONTINUE.

Table 16.1/1: Mapping of P-Abort cause in TC-P-ABORT indication on to provider-reason in MAP-P-ABORT indication

TC P-Abort cause

MAP provider-reason

unrecognized message type

provider malfunction

unrecognized transaction Id

supporting dialogue released


provider malfunction


provider malfunction (note)


resource limitation


provider malfunction


version incompatibility

NOTE: Or version incompatibility in the dialogue initiated phase.