3GPP2 X.

S0004-511-E
Version 1.0.0
Date: March 2004

ANS/SS7 Transport Signaling

Protocols

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational 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 Organizational Partner's
documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
Revision History

Revision Date
Rev. 0 Initial Publication March 2004
 X.S0004-511-E v1.0

1
2 PART 511
3
4
5
6 1 MESSAGE TRANSFER PART
7
8
The MTP is defined in ANSI T1.111, with the following supplemental information.
9
10 The MAP messages that are transported on an intersystem basis may be assigned a message priority
11 value of either 0 or 1. The INVOKE, RETURN RESULT, RETURN ERROR, and REJECT
12
components associated with the same operation (e.g., FacilitiesDirective) shall have the same
13
message priority value. The operations with message priority value 1 are listed below. All others
14
have message priority value 0.
15
16 Table 1 TIA-41 Operations having MTP Message Priority Value 1
17
18 TIA-41 Operation
19
FacilitiesDirective2
20
21 FacilitiesDirective
22
23
FacilitiesRelease
24 HandoffBack2
25
26 HandoffBack
27
HandoffToThird
28
29 HandoffToThird2
30
InterSystemAnswer (see note a)
31
32 MobileOnChannel
33
RedirectionDirective
34
35 RedirectionRequest
36
TransferToNumberRequest
37
38
Notes:
39
a. The MTP Message Priority value for the InterSystemAnswer has changed in rev. E
40
41
42 The message priority value may be determined by the TIA-41 MAP based on the message type and
43 may be passed down to the MTP through the SCCP. In the case when a REJECT component is to be
44 returned, the message priority of the REJECT component should be the same as that of the rejected
45
message.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

511-1 Message Transfer Part

X.S0004-511-E v1.0

2 SIGNALING CONNECTION CONTROL PART 1

2
3

For TIA-41 applications, the SCCP is defined in ANSI T1.112, with the following exceptions and 4
5
limitations:
6

SCCP Class 0 connectionless service is requested from the SCCP. (However, in accordance 7

with SCCP procedures, if a TIA-41 message is segmented by the SCCP, the sequence of XUDT 8
9
messages carrying the segments are sent using SCCP Class 1 sequenced connectionless service.
10
The In-Sequence Delivery Option field of the segmentation parameter within each of the XUDT
11
messages is set to 0 to reflect the original request for Class 0 service.)
12
13
Whether to set the return message on error or discard message on error option in the Protocol
14
Class parameter of the UDT or XUDT message is at the discretion of the implementation. If
15
return message on error is requested by the SCCP user for a segmented message, then only the
16
first XUDT message sent shall have return message on error requested. 17
18
The TIA-41 Mobile Application Part has assigned the following Subsystem Numbers (SSN).
19
Use of the following SSN values is recommended1: 20
21
5: Mobile Application Part (MAP) 22
6: Home Location Register (HLR) 23
24
7: Visitor Location Register (VLR)
25
8: Mobile Switching Center (MSC) 26
2 27
9: Equipment Identification Register (EIR) (reserved)
28
10: Authentication Center (AC) 29
11: Short Message Service (SMS) 30
31
12: Over-The-Air Service Provisioning Function (OTAF)
32
In accordance with ANSI T1.112 an SSN shall be included in all messages even if message 33
routing is based on Global Title Translation (GTT). The null SSN (i.e., value 0) should be used 34
when the subsystem is not known (e.g., before a global title translation takes place) per ANSI 35
T1.112. 36
37
Global title addresses are required in the SCCP Called Party Address and the SCCP Calling 38
Party Address for international roaming purposes. 39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
1
Further SSN assignments are not planned. 58
2
Detailed transactions relative to SSN value 9 are for further study. 59
60

Signaling Connection Control Part 511-2

 X.S0004-511-E v1.0

1 Global Title Translation on Mobile Identification Number can be used for communication with
2
3
the HLR on the ANSI SS7 network1. The following encoding may be used:
4
5 Table 2 ANSI SS7 - MIN to HLR Global Title
6
7
Field Sub-field Value
8
Address Indicator SSN Indicator 1
9
10
11 Point Code Indicator 0 or 1
12
13
14 Global Title Indicator 2 (00102)
15
16
Routing Indicator 0
17
18
19 National or International 1 (National use)
20 Indicator
21
Subsystem Number Include applicable value if
22
known or zero.
23
24 Global Title Translation Type 3 (000000112) "Cellular
25 Nationwide Roaming Service"
26
27 Address Information MIN
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
1
58 An administrative set of SS7 nodes that are interconnected by a common national signaling point code
59 addressing scheme.
60

511-3 Signaling Connection Control Part

X.S0004-511-E v1.0

Global Title Translation on Mobile Identification Number can be used for communication with 1
2
a Message Center on the ANSI SS7 network. The following encoding may be used:
3
4
Table 3 ANSI SS7 - MIN to MC Global Title 5
6
Field Sub-field Value
7
8
Address Indicator SSN Indicator 1
9
10
Point Code Indicator 0 or 1 11
12
13
Global Title Indicator 2 (00102)
14
15
Routing Indicator 0 16
17
18
National or International 1 (National use) 19
Indicator 20

Subsystem Number Include applicable value if 21

known or zero. 22
23
Global Title Translation Type 12 (000011002) "Wireless 24
MIN-Based Short Message 25
Service" 26
27
Address Information MIN
28
29
30
31
32
33
34
35
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

Signaling Connection Control Part 511-4

 X.S0004-511-E v1.0

1 Global Title Translation on IMSI (ITU-T E.212 International Mobile Subscriber Identity) can
2
be used for communication from a Serving System (MSC or VLR) to an HLR on the same or a
3
different national SS7 network using the IMSI of a roaming mobile. It may also be used for
4
communication to any network element that is identified by an E.212 formatted address on the
5
6
same or a different SS7 network. The following encoding may be used:
7
8 Table 4 ANSI SS7 - E.212 Global Title
9
10 Field Sub-field Value
11
Address Indicator SSN Indicator 1
12
13
14 Point Code Indicator 0 or 1
15
16
17 Global Title Indicator 2 (00102)
18
19
Routing Indicator 0
20
21
22 National or International 1 (National use)
23 Indicator
24
Subsystem Number Include applicable value if
25
known or zero.
26
27 Global Title Translation Type 16 (000100002) Cellular/PCS
28 Interworking (see note a)
29
30 Address Information IMSI or other E.212 formatted
31 address
32
33
Notes:
34
a. Translation Type 9 may be used in some networks based on the initial IS-807 recom-
35 mendation.
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

511-5 Signaling Connection Control Part

X.S0004-511-E v1.0

Global Title Translation on an E.164 number (e.g., Mobile Directory Number) can be used for 1
2
communication to an HLR on the same or a different national SS7 network based on the Mobile
3
Directory Number. The following encoding may be used:
4
5
Table 5 ANSI SS7 - MDN to HLR (E.164) Global Title 6
7
Field Sub-field Value
8
9
Address Indicator SSN Indicator 1
10
11
Point Code Indicator 0 or 1 12
13
14
Global Title Indicator 2 (00102)
15
16

Routing Indicator 0 17
18
19
National or International 1 (National use) 20
Indicator 21
22
Subsystem Number Include applicable value if
23
known or zero.
24
Global Title Translation Type 14 (000011102) "Mobile 25
Subscriber Addressing" 26
27
Address Information E.164 Mobile Directory
28
Number
29
30
31
32
33
34
35
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

Signaling Connection Control Part 511-6

 X.S0004-511-E v1.0

1 Global Title Translation on an E.164 number (e.g., Mobile Directory Number) can be used for
2
communication to an MC on the same or a different national SS7 network based on the Mobile
3
Directory Number. The following encoding may be used:
4
5
6 Table 6 ANSI SS7 - MDN to MC (E.164) Global Title
7
Field Sub-field Value
8
9
Address Indicator SSN Indicator 1
10
11
12 Point Code Indicator 0 or 1
13
14
Global Title Indicator 2 (00102)
15
16
17 Routing Indicator 0
18
19
20 National or International 1 (National use)
21 Indicator
22
Subsystem Number Include applicable value if
23
known or zero.
24
25 Global Title Translation Type 17 (000100012) "Mobile
26 Subscriber Message Center
27 Addressing"
28
Address Information E.164 Mobile Directory Number
29
30
31
32
33
34
35
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

511-7 Signaling Connection Control Part

X.S0004-511-E v1.0

Global Title Translation on IMSI can be used for communication from a Serving System (MSC 1
2
or VLR) to a Message Center on the same or a different national SS7 network. The following
3
encoding may be used:
4
5
Table 7 ANSI SS7 - IMSI to MC Global Title 6
7
Field Sub-field Value
8
9
Address Indicator SSN Indicator 1
10
11
Point Code Indicator 0 or 1 12
13
14
Global Title Indicator 2 (00102)
15
16
Routing Indicator 0 17
18
19
National or International 1 (National use)
20
Indicator
21
Subsystem Number Include applicable value if 22
known or zero. 23
24
Global Title Translation Type 13 (000011012) "Wireless
25
IMSI-based Short Message 26
Service" 27

Address Information IMSI 28

29
30
31
32
33
34
35
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

Signaling Connection Control Part 511-8

 X.S0004-511-E v1.0

1 Global Title Translation on portable Directory Number can be used for communication with the
2
NPDB. The following encoding may be used:
3
4
5 Table 8 ANSI SS7 - DN to NPDB Global Title
6
7 Field Sub-field Value
8
Address Indicator SSN Indicator 1
9
10
11 Point Code Indicator 0 or 1
12
13
14
Global Title Indicator 2 (00102)
15
16 Routing Indicator 0
17
18
19 National or International 1 (National use)
20
Indicator
21
Subsystem Number Include applicable value if
22 known or zero.
23
24 Global Title Translation Type 11 (000010112) "Internetwork
25 Number Portability
26 Query/Response"
27
Address Information E.164 Directory Number
28
29
30
31
32
33
34
35
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

511-9 Signaling Connection Control Part

X.S0004-511-E v1.0

Global Title Translation can be used for communication with a Service Control Point (SCP). 1
2
The following encoding may be used: 3
4
Table 9 ANSI SS7 - SCP Global Title Addressing 5
6
Field Sub-field Value 7
8
Address Indicator SSN Indicator 1
9
10

Point Code Indicator 0 or 1 11

12
13
Global Title Indicator 2 (00102) 14
15

Routing Indicator 0 16
17
18
National or International 1 (National use) 19
Indicator 20
21
Subsystem Number Include applicable value if
known or zero. 22
23
Global Title Translation Type 8 (000010002) "SCP assisted 24
call processing application" 25
26
Address Information Ten-digit global title address,
27
with the first 6 digits being the
Location specific part 28
(consists of Network ID and 29
Cluster ID of the destination 30
STP) and the last 4 digits 31
being the application specific
32
part (identifies the destination
SCP and application). 33
34
35
When an originating network entity sends an SS7 message within a national SS7 signaling 36
network with a global title in the SCCP called party address field, the SCCP calling party 37

address field should include the point code and subsystem number of the originating network 38

entity. Note that a Signaling Transfer Point (STP) is considered to be an intermediate network 39
40
entity, not an originating network entity.
41

When an originating network entity sends an SS7 message across a national SS7 signaling 42

network boundary, the SCCP calling party address field should include an E.212 global title 43
44
address identifying the originating network entity to allow response messages (RETURN
45
RESULT, RETURN ERROR, or REJECT) to be routed back to the originating network entity.
46

Replies to messages shall use the received Calling Party Address as the Called Party Address, 47
48
in accordance with ANSI T1.112. (An exception occurs if the PC_SSN parameter is received in
49
an AuthenticationRequest INVOKE or in a RegistrationNotification INVOKE. In this case, the
50
address used for the response may be derived from the received PC_SSN parameter provided
51
that the INVOKE was received from a network entity within the same national SS7 signaling 52
network.) 53
54
55
56
57
58
59
60

Signaling Connection Control Part 511-10