You are on page 1of 12

3GPP2 X.

S0004-520-E

v 2.0

Date: July 2007

Mobile Application Part (MAP) -


TCAP APPLICATION SIGNALING PROTOCOLS

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual OPs may
copyright and issue documents or standards publications in individual Organizationial Partner’s
name based on this document. Requests for reproduction of this document should be directed to the
3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizationial Part-
ner’s documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
REVISION HISTORY
Revision Date Remarks

X.S0004-520-E v2.0 July 2007 Incorporated changes from Miscel-


laneous Rev. E standards.
X.S0004-520-E v2.0

1
2 PART 520
3
4
5
6 1 APPLICATION SERVICES
7
8
9
10 1.1 APPLICATION SERVICES ARCHITECTURE
11
12
The Application Services architecture introduced in MAP-500 is reproduced in the following figure.
13
14
15
16
Application Layer
17
18
Mobile Application Part
19
(MAP)
20
21 Transaction Capabilities
22 Application Part (TCAP)
23
24 APPLICATION
25 SERVICES
Presentation Layer ANSI
26
27
Transaction
28 Capabilities
29 Session Layer
30
31
32 Transport Layer
33
34
35 Figure 1 Application Services Architecture
36
37
Application Services are comprised of the ANSI Transaction Capabilities (TC) specified in ANSI
38
T1.114, along with the Mobile Application Part (MAP).
39
40 The TC Transport, Session, and Presentation layers are null layers in this Standard, just as they are
41
described in ANSI T1.114. They are included here for completeness; future revisions of this Standard
42
may make use of them.
43
44 The Application Layer contains the working part of the MAP Application Services. It is described in
45
the remainder of this part and in parts MAP-540, -550, -551.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

520 -1 APPLICATION SERVICES


X.S0004-520-E v2.0

1.2 APPLICATION LAYER STRUCTURE 1


2
3
The following figure illustrates the TIA-41 Application Layer Structure. 4
5
6
7
Mobile Application Part 8
(MAP) 9
10
11
12
13
ANSI TCAP 14

Application 15
Component Layer 16
sub-layer 17
18
19
20
21
Transaction 22
sub-layer 23
24
25
26
27
to and from 28
underlying layers 29
30
31
Figure 2 TIA-41 Application Layer Structure
32
33
As illustrated, the Mobile Application Part (MAP) defined in this Standard is supported by the ANSI 34
Transaction Capabilities Application Part (TCAP). TCAP, in turn, is structured in two sub-layers: 35
36
• the component sub-layer, which deals with individual actions or data, called components. 37
38
• the transaction sub-layer, which deals with the exchange of messages containing components
39
between two MAP entities.
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

APPLICATION LAYER STRUCTURE 520 -2


X.S0004-520-E v2.0

1
2
1.3 TCAP FORMATS AND PROCEDURES
3
4
5
1.3.1 Transaction Portion
6
7
This Standard employs the TCAP package formats and procedures defined in ANSI T1.114 with the
8
9
following exceptions and limitations:
10
• Special procedures for “Handover,” defined in the ANSI TCAP standard, are not supported.
11
12
13
14 1.3.2 Component Portion
15
16 This Standard employs the TCAP component formats and procedures defined in ANSI T1.114 with
17 the following exceptions and limitations:
18
19 • Special procedures for “Handover,” defined in the ANSI TCAP standard, are not supported.
20
21
• The Operation Code Identifier is coded as Private TCAP.
22
• The Operation Code is partitioned into an Operation Family followed by a Specifier associated
23
24
with each Operation Family member. For MAP the Operation Family is coded as decimal 9. Bit
25
H of the Operation Family is always coded as 0.
26
• A TCAP INVOKE component shall contain a Component ID Length greater than zero.
27
28
• A TCAP RETURN RESULT component shall only be transmitted in response to an INVOKE
29
Component.
30
31 • A TCAP RETURN ERROR component shall only be sent in response to an INVOKE
32
component, not a RETURN RESULT component.
33
34 • If a problem is detected by TCAP (i.e., the received message does not conform to ANSI
35 T1.114.3), a TCAP REJECT component with one of the following Problem Specifiers shall be
36
sent:
37
38 - All families, General, Transaction Portion: All specifiers.
39
40 - INVOKE: Unrecognized Correlation ID.
41
42 - RETURN RESULT: Unrecognized Correlation ID, Unexpected Return Result.
43
44
- RETURN ERROR: Unrecognized Correlation ID, Unexpected Return Error.
45
• If a problem is detected by MAP (i.e., the received message does not conform to MAP), a TCAP
46
REJECT component with one of the following TCAP Problem Specifiers shall be sent:
47
48
- INVOKE: Duplicate Invoke ID, Unrecognized Operation Code or Incorrect Parameter.
49
50 - RETURN RESULT: Incorrect Parameter.
51
52 - RETURN ERROR: Incorrect Parameter, Unrecognized Error, Unexpected Error.
53
54 • If an error is detected by a MAP user except SMSDeliveryBackward, SMSDeliveryForward,
55 and SMSDeliveryPointToPoint, a TCAP RETURN ERROR component shall be sent. For
56 SMSDeliveryBackward, SMSDeliveryForward, and SMSDeliveryPointToPoint, a TCAP
57 RETURN RESULT with an SMS_CauseCode parameter shall be sent.
58
59
60

520 -3 TCAP FORMATS AND PROCEDURES


X.S0004-520-E v2.0

• As exceptions to the TCAP procedures related to the use of Component Types marked as “Last” 1
2
if a ConnectResource INVOKE, a DisconnectResource INVOKE, a InstructionRequest
3
INVOKE, a RemoteUserInteractionDirective INVOKE, a ResetTimer INVOKE, or an
4
SRFDirective INVOKE is received encoded as a response to the INVOKE component of some
5
other MAP operation, it should not be treated as the final response to that other INVOKE 6
component. 7
8
• As exceptions to the TCAP procedures related to the use of Component Types marked as “Last”
9
a SeizeResource RETURN RESULT should not treated as the final response to a SeizeResource 10
INVOKE component. 11
12
13
1.3.2.1 TCAP INVOKE Component 14
15
The structure of an ANSI TCAP package containing an INVOKE component is shown in the 16

following table. 17
18
19
Table 1 Structure of TCAP Package with INVOKE Component
20

Package Type Identifier 21


22
Total TCAP Message Length 23
24
Transaction ID Identifier
25
Transaction ID Length 26
27
Transaction IDs
28
Component Sequence Identifier 29
30
Component Sequence Length
31
Component Type Identifier 32
33
Component Length
34

Component ID Identifier 35
36
Component ID Length 37

Component IDs 38
39
Operation Code Identifier 40
41
Operation Code Length
42
Operation Code 43
44
Parameter Set Identifier
45
Parameter Set Length 46
47
Parameter Set
48
49
50
1.3.2.1.1 INVOKE Response Philosophy
51
52
1. If a network entity receives an INVOKE with an incorrect TCAP message (e.g., ill-
53
formatted), it shall respond with a REJECT to report this error.
54

2. If a network entity receives an INVOKE and is unable to initiate or complete the operation, 55
56
it shall respond with a RETURN ERROR.
57
58
59
60

TCAP FORMATS AND PROCEDURES 520 -4


X.S0004-520-E v2.0

1 3. If a network entity receives an INVOKE and is able to complete the operation, it shall
2
respond with a RETURN RESULT to report the completion of the operation, except for the
3
messages HandoffMeasurementRequest and MobileOnChannel.
4
5
6
7
1.3.2.2 TCAP RETURN RESULT Component
8
9 The structure of a TCAP package containing a RETURN RESULT component is shown in the
10 following table.
11
12 Table 2 Structure of TCAP Package with RETURN RESULT Component
13
14 Package Type Identifier
15
Total TCAP Message Length
16
17 Transaction ID Identifier
18
Transaction ID Length
19
20 Transaction IDs
21
22
Component Sequence Identifier
23 Component Sequence Length
24
25 Component Type Identifier
26
Component Length
27
28 Component ID Identifier
29
Component ID Length
30
31 Component IDs
32
Parameter Set Identifier
33
34 Parameter Set Length
35
Parameter Set
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

520 -5 TCAP FORMATS AND PROCEDURES


X.S0004-520-E v2.0

1.3.2.3 TCAP RETURN ERROR Component 1


2
3
The structure of a TCAP package containing a RETURN ERROR component is shown in the
4
following table.
5
6
Table 3 Structure of TCAP Package with RETURN ERROR Component 7
8
Package Type Identifier
9
Total TCAP Message Length 10
11
Transaction ID Identifier
12

Transaction ID Length 13
14
Transaction IDs 15

Component Sequence Identifier 16


17
Component Sequence Length 18
19
Component Type Identifier
20
Component Length 21
22
Component ID Identifier
23
Component ID Length 24
25
Component IDs
26
Error Code Identifier 27
28
Error Code Length
29

Error Code 30
31
Parameter Set Identifier 32

Parameter Set Length 33


34
Parameter Set 35
36
37
The Parameter Set is encoded as follows: 38
39
40
RETURN ERROR Parameters
41

Field Value Type Reference Notes 42


43
Identifier Set [NATIONAL 18] M 44
45
Length variable octets M
46
Contents 47
48
FaultyParameter O 550-2.120 a
49
50

Notes: 51
52
a. Include if the error involved a specific parameter. 53
54
55
1.3.2.3.1 Error Definitions 56
57
The detailed handling of operation errors is specified in the operations procedures. 58
59
60

TCAP FORMATS AND PROCEDURES 520 -6


X.S0004-520-E v2.0

1 The following definitions for errors are not exhaustive, but are included so that different
2
manufacturers and users have a common understanding of the mapping between a reported error and
3
the occurrence which generates it. The detection of the errors is not mandatory, however, if an error
4
is detected for one of the examples given, then the indicated error code should be used.
5
6
Implementations should not give cause for these reasons to be generated. For
7
SMSDeliveryBackward, SMSDeliveryForward, and SMSDeliveryPointToPoint, detected errors
8 should be mapped into the SMS_CauseCode parameter returned in the RETURN RESULT.
9
10
UnrecognizedMIN
11
a. Supplied MIN is not currently served by the VLR.
12
13 b. Supplied MIN is not currently served by the HLR.
14
15 c. Supplied MIN is not currently served by the Serving MSC.
16
17 d. Supplied MIN does not currently have an active call on an originating MSC.
18
19
UnrecognizedESN
20
a. Supplied ESN does not match HLR’s stored value for subscriber’s ESN.
21
22
b. Supplied ESN does not match VLR’s stored value for subscriber’s ESN.
23
24 c. Supplied ESN is negative listed.
25
26 ID/HLRMismatch
27
28 a. Supplied MSID is not resident on the HLR.
29
30
b. Supplied MDN is not resident on the HLR.
31
c. Supplied MSID is not in the AC’s, MC’s, or OTAF’s range of MSIDs.
32
33 OperationSequenceProblem
34
35 a. Unexpected INVOKE in response to an INVOKE.
36
37 b. Operation is not allowed in the current state.
38
39
ResourceShortage
40
a. Network entity congestion.
41
42
b. Application (or function) congestion.
43
44 c. Network congestion.
45
46 d. No transaction IDs available.
47
48 e. Internal processing resource shortage (memory, I/O, disk, processor, etc.)
49
50
f. No TLDNs available.
51
OperationNotSupported
52
53 a. Operation is not supported on the addressed network entity.
54
55 TrunkUnavailable
56
57 a. Specific requested trunk is not available.
58
59
b. No trunks are available, but are required to perform the operation.
60

520 -7 TCAP FORMATS AND PROCEDURES


X.S0004-520-E v2.0

ParameterError 1
2
a. Parameter errors and parameter encoding errors (550-2). Parameter errors include exactly 3

one FaultyParameter parameter in the parameter set. 4


5
UnrecognizedParameterValue 6
7
a. UnrecognizedParameterValue is a parameter value which is encoded properly (550-2), but 8
its value is not recognized. UnrecognizedParameterValue errors should include exactly one 9
FaultyParameter parameter in the parameter set. 10
11
SystemFailure 12
13
a. System component failure. 14
15
b. Network component failure.
16

c. Chained operation failure. 17


18
d. Required subsystem failure. 19
20
FeatureInactive 21
22
a. Cannot reroute call because indicated feature is inactive. 23
24
MissingParameter
25
26
a. Expected optional parameter is missing.
27

b. All profile parameters are expected, but some are missing. 28


29
c. All qualification parameters are expected, but some are missing. 30
31
d. MissingParameter errors should include exactly one FaultyParameter parameter in the 32
parameter set. 33
34
Note that this Error Code is not used to indicate a missing mandatory parameter; a REJECT 35
component with a Problem Specifier of Incorrect Parameter is used in this case. 36
37
38
UnrecognizedIMSI/TMSI
39

a. Supplied IMSI is not currently served by the VLR. 40


41
b. Supplied IMSI is not currently served by the HLR. 42
43
c. Supplied IMSI is not currently served by the Serving MSC. 44
45
d. Supplied IMSI does not currently have an active call on an originating MSC. 46
47
e. Supplied TMSI is not currently served by the Old Serving VLR. TMSI_ZONE may be
48
matched, but TMSI_CODE is not matched.
49
50
f. Supplied TMSI is not currently served by the Serving VLR. TMSI_ZONE may be matched,
51
but TMSI_CODE is not matched.
52

TMSI/VLRMismatch 53
54
a. Supplied TMSI is not resident on the Old Serving VLR. 55
56
b. Supplied TMSI is not resident on the Serving VLR. 57
58
59
60

TCAP FORMATS AND PROCEDURES 520 -8


X.S0004-520-E v2.0

1 For MAP the Error Code Identifier is coded as Private TCAP. Error Codes are coded as follows:
2
3
4
Table 4 Error Codes
5
Error Code Name Error Code
6
7
H G F E D C B A
8
UnrecognizedMIN 1 0 0 0 0 0 0 1
9
10 UnrecognizedESN 1 0 0 0 0 0 1 0
11
12
ID/HLRMismatch 1 0 0 0 0 0 1 1
13 OperationSequenceProblem 1 0 0 0 0 1 0 0
14
15 ResourceShortage 1 0 0 0 0 1 0 1
16
OperationNotSupported 1 0 0 0 0 1 1 0
17
18 TrunkUnavailable 1 0 0 0 0 1 1 1
19
20 ParameterError 1 0 0 0 1 0 0 0
21
SystemFailure 1 0 0 0 1 0 0 1
22
23 UnrecognizedParameterValue 1 0 0 0 1 0 1 0
24
25
FeatureInactive 1 0 0 0 1 0 1 1
26
MissingParameter 1 0 0 0 1 1 0 0
27
28 UnrecognizedIMSI/TMSI 1 0 0 0 1 1 0 1
29
30
TMSI/VLRMismatch 1 0 0 0 1 1 1 0
31 Reserved 1 0 0 0 1 1 1 1
32
(Note a) through
33
34
1 1 1 0 1 1 1 1
35 Reserved for Protocol Extension 1 1 1 0 0 0 0 0
36
(Note b) through
37
38
1 1 1 1 1 1 1 1
39
40
41
Notes:
42
a. Treat a reserved value the same as value 133 (decimal), ResourceShortage.
43
44 b. Error codes 224 to 255 (decimal) shall be reserved for protocol extension. If unknown, treat
45
the same as value 133 (decimal), Resource Shortage.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

520 -9 TCAP FORMATS AND PROCEDURES


X.S0004-520-E v2.0

1.3.3 TCAP REJECT Component 1


2
3
The structure of a TCAP package containing a REJECT component is shown in the following table.
4
5
Table 5 Structure of TCAP Package with REJECT Component 6
7
Package Type Identifier
8

Total TCAP Message Length 9


10
Transaction ID Identifier 11

Transaction ID Length 12
13
Transaction IDs 14
15
Component Sequence Identifier
16
Component Sequence Length 17
18
Component Type Identifier
19
Component Length 20
21
Component ID Identifier
22
Component ID Length 23
24
Component IDs
25

Problem Code Identifier 26


27
Problem Code Length 28

Problem Code 29
30
Parameter Set Identifier 31
32
Parameter Set Length
33
Parameter Set 34
35
36
A TCAP REJECT component with a TCAP Problem Code containing a Problem Specifier with one 37
of the following values may include one occurrence of a FaultyParameter parameter identifying the 38
parameter in error: 39
40
a. INVOKE: Incorrect Parameter 41
42
b. RETURN RESULT: Incorrect Parameter
43
44
c. RETURN ERROR: Incorrect Parameter
45

When a network entity receives a message with protocol errors, it shall return with a REJECT 46

component. 47
48
When a network entity receives a REJECT component it should: 49
50
a. Stop timer for current task. 51
52
b. Exit the current task. 53
54
c. Begin recovery procedures according to the network entity’s internal algorithm.
55
56
d. If it needs to respond to another network entity due to an ongoing transaction, it should send
57
a RETURN ERROR component indicating System Failure.
58
59
60

TCAP FORMATS AND PROCEDURES 520 -10