GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

5.5.2 Mapping of user specific services
Page 57
GSM 09.02 version 5.3.0: August 1996
Table 5.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto
TC services and table 5.5/4 gives the similar rules for mapping of TC services onto MAP user specific
services. Detailed mapping is given in clauses 11 to 14.
MAP service-primitive TC-service-primitive
MAP-xx request TC-INVOKE request
MAP-xx response TC-RESULT-L request
(note 1) TC-U-ERROR request
TC-U-REJECT request
TC-INVOKE request (note 2)
Table 5.5/3: Mapping of MAP user specific services onto TC services
TC-service-primitive MAP service-primitive
TC-INVOKE indication MAP-xx indication
TC-RESULT-L indication (note 4) MAP-xx confirm
TC-U-ERROR indication
TC-INVOKE indication (note 2)
TC-L-CANCEL indication
TC-U-REJECT indication MAP-xx confirm or
TC-L-REJECT indication MAP-NOTICE indication (note 3)
TC-R-REJECT indication
Notes to tables 5.10 and 5.11:
Table 5.5/4: Mapping of TC services onto MAP user specific services
NOTE 1: The mapping is determined by parameters contained in the MAP-xx response primitive.
NOTE 2: This applies only to TC class 4 operations where the operation is used to pass a result
of another class 2 or class 4 operation.
NOTE 3: The detailed mapping rules are given in clause 13.
NOTE 4: If RESULT-NL components are present they are mapped on to the same MAP-xx
confirm.
5.6 Definition of parameters
Following is an alphabetic list of parameters used in the common MAP-services in subclause 5.3:
Application context name 5.3.1 Refuse reason 5.3.1
Destination address 5.3.1 Release method 5.3.2
Destination reference 5.3.1 Responding address 5.3.1
Diagnostic information 5.3.4 Result 5.3.1
Originating address 5.3.1 Source 5.3.5
Originating reference 5.3.1 Specific information 5.3.1/5.3.2/5.3.4
Problem diagnostic 5.3.6 User reason 5.3.4
Provider reason 5.3.5