3GPP2 N.S0016-0
Version 1.0
TIA/EIA-41-D Internationalization
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 [email protected]. Requests
to reproduce individual Organizational Partner's documents should be directed to that
Organizational Partner. See www.3gpp2.org for more information.
N.S0016-0 v 1.0
1
2
3
CONTENTS
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
LIST OF FIGURES ....................................................................................................................................... iii
LIST OF TABLES......................................................................................................................................... iv
FOREWORD .................................................................................................................................................. v
EDITORIAL KEY ......................................................................................................................................... vi
ASSUMPTIONS........................................................................................................................................... vii
REVISION HISTORY.................................................................................................................................. vii
1.
INTRODUCTION................................................................................................................................. 1
1.1 OBJECTIVE..................................................................................................................................... 1
1.2 SCOPE.............................................................................................................................................. 1
1.3 ORGANIZATION............................................................................................................................ 1
2.
TIA/EIA-41-D Chapter 1 “Functional Overview” Modifications......................................................... 2
2.1 NORMATIVE REFERENCES ........................................................................................................ 2
3.1 DEFINITIONS ................................................................................................................................. 2
International Mobile Subscriber Identity (IMSI) ......................................................................... 2
Mobile Station Identity (MSID)................................................................................................... 2
4
SYMBOLS AND ABBREVIATIONS............................................................................................. 2
7
GENERAL BACKGROUND AND ASSUMPTIONS..................................................................... 3
3.
TIA/EIA-41-D Chapter 3 “Automatic Roaming Information Flows” Modifications ........................... 4
4.17.2 Successful LocationRequest: Route to a Local MS................................................................. 4
4.17.3 Successful LocationRequest: Route to an MS on Another MSC............................................. 5
4.17.5 Successful LocationRequest: Route to Multiple Terminations................................................ 6
4.
TIA/EIA-41-D Chapter 5 “Signaling Protocol” Modifications ............................................................. 7
5.1 ANSI SS7-BASED DATA TRANSFER SERVICES ...................................................................... 7
5.1.2
Signaling Connection Control Part.......................................................................................... 7
5.3 ITU-T SS7-BASED DATA TRANSFER SERVICES ................................................................... 12
5.3.2
Signaling Connection Control Part........................................................................................ 12
6.4.2.4
AuthenticationRequest................................................................................................. 17
6.4.2.13
FeatureRequest ............................................................................................................ 19
6.4.2.24
InterSystemPage .......................................................................................................... 23
6.4.2.27
LocationRequest .......................................................................................................... 26
6.4.2.30
OriginationRequest ...................................................................................................... 29
6.4.2.31
QualificationDirective ................................................................................................. 32
6.4.2.32
QualificationRequest ................................................................................................... 34
6.4.2.33
RedirectionDirective.................................................................................................... 36
6.4.2.37
RegistrationNotification .............................................................................................. 37
6.4.2.46
TransferToNumberRequest ......................................................................................... 41
6.5.2.5
AnnouncementCode .................................................................................................... 44
6.5.2.58
Digits ........................................................................................................................... 45
6.5.2.76
Local Termination ....................................................................................................... 47
6.5.2.83
MSCIdentificationNumber .......................................................................................... 49
6.5.2.89
OriginationIndicator .................................................................................................... 50
6.5.2.90
OriginationTriggers ..................................................................................................... 51
6.5.2.93
PC_SSN....................................................................................................................... 54
6.5.2.97
Profile .......................................................................................................................... 56
6.5.2.98
PSTNTermination........................................................................................................ 58
6.5.2.113 RestrictionDigits.......................................................................................................... 59
6.5.2.116 SenderIdentificationNumber........................................................................................ 60
6.5.2.123 SMS_Address .............................................................................................................. 61
6.5.2.140 SPINITriggers ............................................................................................................. 65
6.5.3.2
DigitsType ................................................................................................................... 67
5.
TIA/EIA-41-D Chapter 6 “Signaling Procedures” Modifications ....................................................... 70
59
60
i
Contents
N.S0016-0 v 1.0
2.1 INTERSYSTEM HANDOFF PROCEDURES .............................................................................. 70
3.2.3
MSC Analyze MS Dialed Number........................................................................................ 70
4.25.2 MSC Receiving InterSystemPage ......................................................................................... 71
4.38.2 VLR Receiving RegistrationNotification INVOKE .............................................................. 72
4.41.3 MSC Receiving RoutingRequest INVOKE........................................................................... 73
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Contents
ii
N.S0016-0 v 1.0
1
2
3
LIST OF FIGURES
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Figure 66
Figure 84
Figure 91
Figure 97
Figure 98
Figure 101
Figure 101A
Figure 105
Figure 106
Figure 121
Figure 124
Figure 132
Figure 133
Figure 134
Figure 134A
Figure 157
Figure XXX
Digits parameter for BCD digits ............................................................................................ 45
LocalTermination parameter.................................................................................................. 47
MSCIdentificationNumber parameter for BCD digits ........................................................... 49
OriginationIndicator parameter.............................................................................................. 50
OriginationTriggers parameter............................................................................................... 51
PC_SSN parameter (ANSI) ................................................................................................... 54
PC_SSN parameter (generic)................................................................................................. 55
Profile Macro......................................................................................................................... 56
PSTNTermination parameter................................................................................................. 58
RestrictionDigits parameter for BCD digits........................................................................... 59
SenderIdentificationNumber parameter for BCD digits ........................................................ 60
SMS_Address parameter for BCD digits............................................................................... 61
SMS_Address Encoding for an IP address ............................................................................ 62
SMS_Address parameter for an ANSI SS7 Point Code Address ........................................... 63
SMS_Address Parameter for a Generic SS7 Point Code Address ......................................... 64
SPINITriggers parameter....................................................................................................... 65
DigitsType parameter type variant for a generic SS7 point code address.............................. 67
23
24
25
26
27
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
iii
List of Figures
N.S0016-0 v 1.0
1
2
LIST OF TABLES
3
4
Table 5.1.2a
Table 5.1.2b
Table 5.1.2c
Table 5.1.2d
Table 5.1.2e
Table 5.3.2a
Table 5.3.2b
Table 17
Table 35
Table 36
Table 57
Table 58
Table 63
Table 64
Table 68
Table 69
Table 70
Table 72
Table 73
Table 76
Table 82
Table 83
Table 100
Table 101
Table 117
Table 154
Table 155
Table 177
Table 196
ANSI SS7 – MIN to HLR Global Title ................................................................................... 8
ANSI SS7 – MIN to MC Global Title ..................................................................................... 9
ANSI SS7 – E.212 Global Title............................................................................................. 10
ANSI SS7 – MDN to HLR (E.164) Global Title................................................................... 10
ANSI SS7 – IMSI to MC Global Title .................................................................................. 11
ITU-T SS7 – E.212 Global Title ........................................................................................... 13
ITU-T SS7 – E.164 Global Title ........................................................................................... 15
AuthenticationRequest INVOKE Parameters ........................................................................ 17
FeatureRequest INVOKE Parameters.................................................................................... 19
FeatureRequest RETURN RESULT Parameters ................................................................... 21
InterSystemPage INVOKE Parameters.................................................................................. 23
InterSystemPage RETURN RESULT Parameters................................................................. 25
LocationRequest INVOKE Parameters ................................................................................. 26
LocationRequest RETURN RESULT Parameters................................................................. 27
OriginationRequest INVOKE Parameters ............................................................................. 29
OriginationRequest RETURN RESULT Parameters............................................................. 30
QualificationDirective INVOKE Parameters......................................................................... 32
QualificationRequest INVOKE Parameters........................................................................... 34
QualificationRequest RETURN RESULT Parameters .......................................................... 35
RedirectionDirective INVOKE Parameters ........................................................................... 36
RegistrationNotification INVOKE Parameters...................................................................... 37
RegistrationNotification RETURN RESULT Parameters ..................................................... 39
TransferToNumberRequest INVOKE Parameters................................................................. 41
TransferToNumberRequest RETURN RESULT Parameters ................................................ 42
AnnouncementCode value ..................................................................................................... 44
OriginationIndicator value..................................................................................................... 50
OriginationTriggers value...................................................................................................... 51
SPINITriggers value .............................................................................................................. 65
DigitsType value.................................................................................................................... 68
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
List of Tables
iv
N.S0016-0 v 1.0
1
2
3
FOREWORD
4
5
6
This Interim Standard contains recommendations for modifications and enhancements to
ANSI/TIA/EIA-41-D that are required to support international intersystem operations.
7
8
9
10
11
The ANSI recommendation upon which this Interim Standard builds is:
• TIA/EIA-41-D
Cellular Radiotelecommunications Intersystem Operations,
Telecommunications Industry Association; December 1997.
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
v
Foreword
N.S0016-0 v 1.0
1
2
EDITORIAL KEY
3
4
This section identifies the editorial style for the use of the right-hand margin vertical
diffmarks, strikethrough lines, and underscore lines. The editorial style employed is:
5
6
7
a. TIA/EIA-41-D original text deleted by N.S0016-0 has a strikethrough line.
b. Original text added by N.S0016-0 has a single underline.
c. Both additions and deletions are indicated by a right hand margin vertical
diffmark.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Editorial Key
vi
N.S0016-0 v 1.0
1
2
3
ASSUMPTIONS
4
5
6
The following items are basic understandings used during the development of this
document:
7
8
a.
E.212 global title translation is provisioned for message routing between national
networks.
b.
A national SS7 network is an administrative set of SS7 nodes that are interconnected
by a common national signaling point code addressing scheme.
c.
The signal transfer points which reside in both the international and national
signaling levels (i.e., gateway STPs) convert from national MTP and SCCP to
international MTP and SCCP and vice versa. This conversion includes changes to
global title indicator, translation type, numbering plan, encoding scheme, and nature
of address indicator.
d.
International addressing implementations not employing global title translation are
beyond the scope of this interim standard.
e.
An MSC supporting N.S0016-0 or later is assumed to be capable of receiving digit
strings in parameters of DigitsType with Nature of Number indicating International
as well as in parameters of DigitsType with Nature of Number indicating National.
Moreover, if the MSC receives a digit string containing the International encoding of
E.164 number from its own country’s telephony numbering plan (or the leading digits
of such a number), the MSC is assumed to be capable of stripping the country code
from that digit string to convert it to National (Significant) Number form.
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
REVISION HISTORY
33
34
35
36
Revision
Date
Remarks
0.0
August, 1999
Initial Publication
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
vii
Assumptions
N.S0016-0 v 1.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
(This page intentionally left blank.)
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
viii
N.S0016-0 v 1.0
1
2
3
1. INTRODUCTION
4
5
6
1.1
OBJECTIVE
7
This Interim Standard (N.S0016-0) provides recommendations
internationalization enhancements for ANSI/TIA/EIA-41-D.
8
9
for
supporting
10
11
12
1.2
SCOPE
13
This document specifies the ANSI/TIA/EIA-41-D Chapters 1, 3, 5 and 6 enhancements
that are necessary to support international intersystem operations.
14
15
16
17
18
1.3
ORGANIZATION
19
20
This document is organized as per ANSI/TIA/EIA-41-D.
21
22
23
24
25
26
27
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
1
Introduction
N.S0016-0 v 1.0
1
2. TIA/EIA-41-D Chapter 1
“Functional Overview” Modifications
2
3
4
5
6
7
2.1
8
NORMATIVE REFERENCES
9
(TIA/EIA-41-D Chapter 1, page 1-2)
10
11
12
ITU-T:
13
• Recommendation E.212 - The International Identification Plan for Mobile
Terminals and Mobile Users, November 1998.
14
15
16
• Recommendation Q.713 (07/96) - Signalling Connection Control Part formats
and codes, July 1996.
17
18
19
20
21
ANSI T1 Standards:
•
22
ANSI T1.112-19961988 Signaling System Number 7 - Signaling Connection
Control Part (SCCP)
23
24
25
26
27
TIA/EIA:
28
29
• TIA/EIA IS-751
TIA/EIA 41-D Modifications to Support IMSI, February 1998.
30
31
3.1
32
DEFINITIONS
33
(TIA/EIA-41-D Chapter 1, page 1-5)
34
35
36
International Mobile Subscriber Identity (IMSI)
37
The IMSI is a string of decimal digits, up to a maximum of 15 digits, that identifies a
unique mobile terminal or mobile subscriber internationally. The IMSI consists of three
fields: the mobile country code, the mobile network code, and the mobile subscriber
identification number.
38
39
40
41
42
43
Mobile Station Identity (MSID)
44
45
The identifier for a mobile station. A choice of either MIN or IMSI.
46
47
4
SYMBOLS AND ABBREVIATIONS
(TIA/EIA-41-D Chapter 1, page 1-14)
48
49
50
51
IMSI
MSID
International Mobile Subscriber Identity
Mobile Station Identity
52
53
54
55
56
57
58
59
60
Functional Overview
2
TIA/EIA-41-D Chapter 1 Modifications
N.S0016-0 v 1.0
1
2
7
GENERAL BACKGROUND AND ASSUMPTIONS
(TIA/EIA-41-D Chapter 1, page 1-30)
3
4
5
The omitted portions of this section are retained without modification.
6
7
8
9
Against this background, pProcedures for the implementation of the identified intersystem
services have been defined with due regard to the following general considerations:
10
11
12
The omitted portions of this section are retained without modification.
13
14
15
16
17
18
19
20
21
8) The procedures defined here are based on the assumption that intersystem
handoff relies upon dedicated intersystem trunks. This is required since
intersystem handoff is a tightly controlled activity of the cellular systems
involved. Intersystem handoff cannot be considered any differently than an intercell handoff. The intersystem handoff may or may not be inter-LATA (Local
Access and Transport Area) depending upon where the LATA boundary is and
also where the mobile call was placed.
22
23
The remainder of this section is retained without modification.
24
25
26
27
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
TIA/EIA-41-D Chapter 1 Modifications
3
Functional Overview
N.S0016-0 v 1.0
1
3. TIA/EIA-41-D Chapter 3
“Automatic Roaming Information Flows”
Modifications
2
3
4
5
6
7
8
4.17.2
9
Successful LocationRequest: Route to a Local MS
10
(TIA/EIA-41-D Chapter 3, page 3-76)
11
12
The omitted portions of this section are retained without modification.
13
14
15
b.
The HLR determines that the call shall be routed to a local MS (i.e., an MS served
by the Originating MSC) and returns this information to the Originating MSC in the
locreq.
16
17
18
19
Parameters are as in Section 4.18.1, Step-b, with the exception that PSTNRoutingInfo is
not included and with the following additions:
20
Parameters
Usage
22
PC_SSN
Originating MSC PC_SSN. Include if SS7
carriage services are used.
Type
21
23
LocalRoutingInfo:
O
24
25
26
Call routing information:
27
[TerminationList]
[Digits(Destination)]
[RoutingDigits]
[Digits(Carrier)]
Local termination information. Include if
TerminationList is allowed.
O
Destination digits for use in intra-MSC call
routing (may be MS’s MIN). Include if
applicable and if TerminationList is not
allowed.
O
Special routing instructions. Include if
applicable and if not specified within the
TerminationList parameter.
O
Called subscriber’s PIC for use in intra-MSC,
inter-LATA exchange call routing. Include if
applicable and if not specified within the
TerminationList parameter.
O
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
Stage-2 Scenarios
4
TIA/EIA-41-D Chapter 3 Modifications
N.S0016-0 v 1.0
1
2
4.17.3
Successful LocationRequest: Route to an MS on Another MSC
3
(TIA/EIA-41-D Chapter 3, page 3-77)
4
5
The omitted portions of this section are retained without modification.
6
7
8
9
10
11
12
b.
The HLR determines that the call shall be routed to an MS on another MSC and
returns this information to the Originating MSC in the locreq.
Parameters are as in Section 4.17.1, Step-b, with the exception that PSTNRoutingInfo is
not included and with the following additions:
13
14
15
Parameters
Usage
PC_SSN
Serving MSC PC_SSN. Include if SS7 carriage
services are used.
IntersystemRoutingInfo:
Call routing information:
16
Type
O
17
18
19
[TerminationList]
Intersystem termination information. Include if
TerminationList is allowed.
O
[Digits(Destination)]
Destination digits for use in inter-MSC call
routing. Include if TerminationList is not
allowed.
O
[RoutingDigits]
Special routing instructions. Include if
applicable and if not specified within the
TerminationList parameter.
O
[Digits(Carrier)]
Called subscriber’s PIC for use in inter-MSC,
inter-LATA exchange call routing. Include if
applicable and if not specified within the
TerminationList parameter.
O
20
21
22
23
24
25
26
27
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
TIA/EIA-41-D Chapter 3 Modifications
5
Stage-2 Scenarios
N.S0016-0 v 1.0
1
4.17.5
Successful LocationRequest: Route to Multiple Terminations
2
(TIA/EIA-41-D Chapter 3, page 3-79)
3
4
5
The omitted portions of this section are retained without modification.
6
7
b.
The HLR determines that the call shall be routed to multiple terminations and
returns this information to the Originating MSC in the locreq.
Parameters are as in Section 4.17.1, Step-b, with the exception that MSCID, PC_SSN, and
PSTNRoutingInfo are not included and with the following additions:
8
9
10
11
12
13
Parameters
Usage
Type
MultipleRoutingInfo:
Call routing information:
14
15
16
[TerminationList]
Multiple termination information.
R
[RoutingDigits]
Special routing instructions. Include if
applicable and if not specified within the
TerminationList parameter.
O
Called subscriber’s PIC for use in inter-MSC,
inter-LATAexchange call routing. Include if
applicable and if not specified within the
TerminationList parameter.
O
17
18
19
20
21
[Digits(Carrier)]
22
23
24
25
26
27
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
Stage-2 Scenarios
6
TIA/EIA-41-D Chapter 3 Modifications
N.S0016-0 v 1.0
1
2
3
4
5
4. TIA/EIA-41-D Chapter 5
“Signaling Protocol” Modifications
6
7
8
5.1
ANSI SS7-BASED DATA TRANSFER SERVICES
(TIA/EIA-41-D Chapter 5, page 5-6)
9
10
The omitted portions of this section are retained without modification.
11
12
13
14
5.1.2
Signaling Connection Control Part
15
(TIA/EIA-41-D Chapter 5, page 5-8)
16
17
18
19
20
21
22
For TIA/EIA-41 applications, the SCCP is defined in ANSI T1.112, with the following
exceptions and limitations:
•
SCCP Class 0 connectionless service is used.
•
The message types are Unitdata (UDT) and Unitdata Service (UDTS). The
SCCP shall return a UDTS message when a received UDT message cannot be
delivered to the specified destination and has the return message on error option
set.
•
Whether to set the return message on error or discard message on error option
in the Protocol Class parameter of the UDT message is at the discretion of the
implementation.
•
The TIA/EIA-41 Mobile Application Part has assigned the following Subsystem
Numbers (SSN). Use of the following SSN values are is recommended:
23
24
25
26
27
28
29
30
31
32
33
-
5:
Mobile Application Part (MAP)
-
6:
Home Location Register (HLR)
-
7:
Visitor Location Register (VLR)
-
8:
Mobile Switching Center (MSC)
-
9:
Equipment Identification Register (EIR) (reserved)1
-
10: Authentication Center (AC)
-
11: Short Message Service
34
35
36
37
38
39
40
41
42
43
44
45
46
•
In accordance with ANSI T1.112 an SSN shall be included in all messages even
if message routing is based on Global Title Translation (GTT). The null SSN
(i.e., value 0) should be used when the subsystem is not known (e.g., before a
global title translation takes place) per ANSI T1.112.
•
Global title addresses are required in the SCCP Called Party Address and the
SCCP Calling Party Address for international roaming purposes.
47
48
49
50
51
52
53
54
55
56
57
58
59
1Detailed transactions relative to SSN value 9 are for further study.
60
TIA/EIA-41-D Chapter 5 Modifications
7
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
•
Global Title Translation on Mobile Identification Number can be used for
communication with the HLR on the ANSI SS7 network.1 The following
encoding may be used:
1
2
3
4
5
Table 5.1.2a
ANSI SS7 – MIN to HLR Global Title
6
7
Field
Sub-field
Value
Address Indicator
SSN Indicator
1
Point Code Indicator
0 or 1
Global Title Indicator
2 (00102)
13
0
15
Routing Indicator
8
9
10
11
12
14
16
National or International Indicator
1 (National use)
17
18
Subsystem Number
Include applicable value
if known or zero
19
20
21
Global Title
Translation Type
3 (000000112) “Cellular
Nationwide Roaming
Service”
22
23
24
25
Address Information
MIN
26
27
28
•
Global Title Translation on Mobile Identification Number can be used for
communication with the HLR. Global Title Indicator type 2 (0010) is used. A
translation type value of 3 is used for “MIN to HLR” translation. The global title
address information field contains the 10-digit MIN2. The encoding scheme is
BCD. Each address signal is coded as described in Section 3.4.2.3.1 of the ANSI
T1.112 specification.
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
1An administrative set of SS7 nodes that are interconnected by a common national signaling point
code addressing scheme.
55
56
2Dialed digits must be converted to a 10-digit MIN for the Location Request Task and Call Data
Request Task when Global Title Translation communication with the HLR is used.
57
58
59
60
Stage-3 Signaling Protocol
8
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
•
2
3
4
Global Title Translation on Mobile Identification Number can be used for
communication with a Message Center on the ANSI SS7 network. The following
encoding can be used:
5
Table 5.1.2b
6
7
8
9
10
ANSI SS7 – MIN to MC Global Title
Field
Sub-field
Value
Address Indicator
SSN Indicator
1
Point Code Indicator
0 or 1
Global Title Indicator
2 (00102)
Routing Indicator
0
National or International Indicator
1 (National use)
11
12
13
14
15
16
17
18
19
Subsystem Number
Include applicable value
if known or zero
20
21
22
Global Title
Translation Type
12 (000011002)
“Wireless MIN-Based
Short Message Service”
Address Information
MIN
23
24
25
26
27
28
29
30
31
32
33
•
Global Title Translation on Mobile Identification Number can be used for
communication with a Message Center. Global Title Indicator type 2 (0010) is
used. A translation type value of 12 is used for Short Message Service for “MIN
to MC” translation. The encoding scheme is BCD. Each address signal is coded
as described in Section 3.4.2.3.1 of the ANSI T1.112 specification.
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
TIA/EIA-41-D Chapter 5 Modifications
9
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
•
Global Title Translation on IMSI (ITU-T E.212 International Mobile Subscriber
Identity) can be used for communication from a Serving System (MSC or VLR)
to an HLR on the same, or a different, national SS7 network using the IMSI of a
roaming mobile. It may also be used for communication to any network element
that is identified by an E.212 formatted address on the same, or a different
national SS7 network. The following encoding can be used:
1
2
3
4
5
6
7
8
Table 5.1.2c
ANSI SS7 – E.212 Global Title
9
10
Field
Sub-field
Value
Address Indicator
SSN Indicator
1
Point Code Indicator
0 or 1
Global Title Indicator
2 (00102)
16
Routing Indicator
0
18
National or International Indicator
1 (National use)
20
11
12
13
14
15
17
19
21
Subsystem Number
Include applicable value
if known or zero
22
23
24
Global Title
Translation Type
9 (000010012) “National
and International PCS
Roaming”
25
26
27
28
Address Information
IMSI or other E.212
formatted address
29
30
31
•
Global Title Translation on an E.164 number (e.g. Mobile Directory Number)
can be used for communication to an HLR on the same, or a different, national
SS7 network based on the Mobile Directory Number. The following encoding
can be used:
32
33
34
35
36
37
Table 5.1.2d
ANSI SS7 – MDN to HLR (E.164) Global Title
38
39
Field
Sub-field
Value
Address Indicator
SSN Indicator
1
Point Code Indicator
0 or 1
Global Title Indicator
2 (00102)
Routing Indicator
0
National or International Indicator
1 (National use)
40
41
42
43
44
45
46
47
48
49
50
Subsystem Number
Include applicable value
if known or zero
51
52
53
Global Title
Translation Type
14 (000011102) “Mobile
Subscriber Addressing”
54
55
56
Address Information
E.164 Mobile Directory
Number
57
58
59
60
Stage-3 Signaling Protocol
10
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
•
2
3
4
Global Title Translation on IMSI can be used for communication from a Serving
System (MSC or VLR) to a Message Center on the same, or a different, national
SS7 network.1 The following encoding may be used:
5
Table 5.1.2e
6
ANSI SS7 – IMSI to MC Global Title
7
8
9
10
Field
Sub-field
Value
Address Indicator
SSN Indicator
1
Point Code Indicator
0 or 1
Global Title Indicator
2 (00102)
Routing Indicator
0
National or International Indicator
1 (National use)
11
12
13
14
15
16
17
18
19
Subsystem Number
Include applicable value
if known or zero
20
21
22
Global Title
Translation Type
13 (000011012)
“Wireless IMSI-based
Short Message Service”
Address Information
IMSI
23
24
25
26
27
28
29
•
30
31
32
Use of signaling point codes, global titles, and subsystem numbers must meet
ANSI T1.112 requirements; such that, any allowable combination of these
addressing elements is supported. For example, as stated in T1.112.3, Section
3.4.1:
33
“The address consists of any one or any combination of the following elements:
34
35
1)
signaling point code,
36
2)
global title (MIN-to-HLR for TIA/EIA-41),
3)
subsystem number,
37
38
where, the referenced address is either the called party address or the calling
party address fields in SCCP messages.”
39
40
41
42
•
When an originating functional entity sends an SS7 message within a national
SS7 signaling network with a global title in the SCCP called party address field,
the SCCP calling party address field should include the point code and
subsystem number of the originating functional entity. Note that a Signaling
Transfer Point (STP) is considered to be an intermediate functional entity, not an
originating functional entity.
•
When an originating functional entity sends an SS7 message across a national
SS7 signaling network boundary, the SCCP calling party address field should
include an E.212 global title address identifying the originating functional entity
to allow response messages (RETURN RESULT, RETURN ERROR, or
REJECT) to be routed back to the originating node.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
1 No ITU-T Q.713 translation selector exists for IMSI to Message Center translation.
60
TIA/EIA-41-D Chapter 5 Modifications
11
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
•
Replies to messages shall use the received Calling Party Address as the Called
Party Address, in accordance with ANSI T1.112. (As exceptions, if the PC_SSN
parameter is received in an AuthenticationRequest INVOKE or in a
RegistrationNotification INVOKE, the address used for the response may be
derived from the received PC_SSN parameter provided the INVOKE was
received from a functional entity within the same national SS7 signaling
network.)
1
2
3
4
5
6
7
8
9
10
5.3
ITU-T SS7-BASED DATA TRANSFER SERVICES
(TIA/EIA-41-D Chapter 5, page 5-11)
The omitted portions of this section are retained without modification.
11
12
13
14
15
16
17
5.3.2
Signaling Connection Control Part
18
(TIA/EIA-41-D Chapter 5, page 5-11)
19
20
For TIA/EIA-41 applications, the SCCP is defined in ITU Q.711 - Q.714, with the
following exceptions and limitations:
•
SCCP Class 0 connectionless service is used.
•
The message types are Unitdata (UDT) and Unitdata Service (UDTS). The
SCCP shall return a UDTS message when a received UDT message cannot be
delivered to the specified destination and has the return message on error option
set.
21
22
23
24
25
26
27
28
29
30
Note: Other message types may have to be supported for segmentation.
31
32
•
•
Whether to set the return message on error or discard message on error option
in the Protocol Class parameter of the UDT message is at the discretion of the
implementation.
Use of the following SSN values are is recommended:
33
34
35
36
37
38
-
5:
Mobile Application Part (MAP)
-
6:
Home Location Register (HLR)
-
7:
Visitor Location Register (VLR)
42
-
8:
Mobile Switching Center (MSC)
44
-
9:
Equipment Identification Register (EIR) (reserved)1
-
10: Authentication Center (AC)
-
TBD:Short Message Service (SMS)
-
11: Short Message Service
39
40
41
43
45
46
47
48
49
50
51
52
•
In accordance with ITU Q.713 an SSN is recommended to be included in all
messages even if message routing is based on Global Title Translation (GTT).
The null SSN (i.e., value 0) should be used when the subsystem is not known
(e.g., before a global title translation takes place).
53
54
55
56
57
1Detailed transactions relative to SSN value 9 are for further study.
58
59
60
Stage-3 Signaling Protocol
12
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
•
Global title addressing is required on the SCCP Called Party Address and the
SCCP Calling Party Address for international roaming purposes.
•
Global Title Translation on Mobile Identification Number (MIN), for
communication with an HLR or MC, is left to mutual agreement.
•
Global Title Translation on International Mobile Subscriber Identity (IMSI) can
be used for communication with the HLR on the same, or a different, national
SS7 network. It may also be used for communication to any network element
that is identified by an E.212 formatted address on the same, or a different
national SS7 network. The following encoding can be used:
2
3
4
5
6
7
8
9
10
11
12
13
Table 5.3.2a
14
15
16
17
Field
ITU-T SS7 – E.212 Global Title
Sub-field
Value
Address Indicator Point Code Indicator (PCI)
0 or 1
18
19
SSN Indicator (SSNI)
1
Global Title Indicator (GTI)
4 (01002)
Routing Indicator (RI)
0
Reserved for national use
0 (international use) or 1
(national use)1
20
21
22
23
24
25
26
27
28
29
Subsystem
Number
Include applicable
known or zero
value
if
30
31
Global Title
Translation Type
0
Encoding Scheme
1=odd number of digits, 2=even
Numbering Plan
6 (01102)
Nature of address indicator
4 (00001002)
Address Information
E.212 IMSI or other E.212
formatted address
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 The national/international indicator is intended to indicate the “format” of the encoding and not
the national or international nature of the type of address. A national/international indicator = 0
means that both the address indicator and the address are encoded according to international
specifications. A national/international indicator = 1 means that both the address indicator and
the address are encoded according to national specifications.
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
13
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
•
Global Title Translation on Mobile Identification Number (MIN) or
International Mobile Station Identifier (IMSI) can be used for communication
with the HLR. Global Title Indicator type 4 (0100) is used. The following figure
represents the Global title format for indicator 0100:
8
7
6
5
4
3
2
1
2
3
4
5
6
1
7
Translation type
Numbering plan
Spare
Encoding scheme
Nature of address indicator
Address information
Octet 1
Octet 2
Octet 3
Octet 4
and further
8
9
10
11
12
13
14
15
The global title address information field contains the 10-digit MIN1.
The encoding scheme is 1 for an uneven number of BCD Digits, and 2 for
an even number of BCD Digits.
The Nature of Address is 3 for National Significant Number and 4 for
International Number.
16
17
18
19
20
21
22
Each address signal is coded as described the ITU Q.713 specification.
23
Translation Type assignment is left to mutual agreements.
25
24
26
Numbering Plan for Global Titles based on MIN is left to mutual
agreements.
27
28
29
•
Global Title Translation on Mobile Identification Number or International
Mobile Station Identity can be used for communication with a Message Center
based on mutual agreement.
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
1Dialed digits must be converted to a 10-digit MIN for the Location Request Task and Call Data
Request Task when Global Title Translation communication with the HLR is used.
52
53
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
14
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
•
2
Global Title Translation on Mobile Directory Number can be used for routing
messages to an HLR connected to the same or different national signaling levels:
3
4
Table 5.3.2b
5
6
7
8
9
Field
ITU-T SS7 – E.164 Global Title
Sub-field
Value
Address Indicator Point Code Indicator (PCI)
10
0 or 1
SSN Indicator (SSNI)
1
Global Title Indicator (GTI)
4 (01002)
Routing Indicator (RI)
0
Reserved for national use
0 (international use) or 1
(national use)1
11
12
13
14
15
16
17
18
19
20
Subsystem
Number
Include applicable
known or zero
value
if
21
22
Global Title
Translation Type
0
Encoding Scheme
1=odd number of digits, 2=even
Numbering Plan
1 (00012)
Nature of address indicator
4 (00001002)
Address Information
E.164 Mobile directory number
23
24
25
26
27
28
29
30
31
32
33
•
34
35
36
Use of signaling point codes, global titles, and subsystem numbers must meet
ITU Q.713 requirements; such that, any allowable combination of these
addressing elements is supported. For example, as stated in ITU Q.713:
“The address consists of one or any combination of the following elements:
37
38
1)
signaling point code,
2)
subsystem number,
3)
global title (MIN-to-HLR for TIA/EIA-41).”
39
40
41
42
43
•
When an originating functional entity sends an SS7 message within a national
SS7 signaling network with a global title in the SCCP called party address field,
the SCCP calling party address field should include the point code and
subsystem number of the originating network entity.
•
When an originating functional entity sends an SS7 message across a national
SS7 signaling network boundary, the SCCP calling party address field should
include an E.212 global title address identifying the originating functional entity
44
45
46
47
48
49
50
51
52
53
54
55
56
57
1 The national/international indicator is intended to indicate the “format” of the encoding and not
the national or international nature of the type of address. A national/international indicator = 0
means that both the address indicator and the address are encoded according to international
specifications. A national/international indicator = 1 means that both the address indicator and
the address are encoded according to national specifications.
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
15
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
to allow response messages (RETURN RESULT, RETURN ERROR, or
REJECT) to be routed back to the originating node.
1
2
3
•
Replies to messages shall use the received Calling Party Address as the Called
Party Address. (As exceptions, if the PC_SSN parameter is received in an
AuthenticationRequest INVOKE or in a RegistrationNotification INVOKE, the
address used for the response may be derived from the received PC_SSN
parameter provided the INVOKE was received from a functional entity within
the same national SS7 signaling network.)
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
16
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.4
AuthenticationRequest
3
4
5
6
7
8
9
10
(TIA/EIA-41-D Chapter 5, page 5-34)
The AuthenticationRequest operation is used to request authentication of an
authentication-capable MS.
The AuthenticationRequest operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
11
Table 17
12
13
14
AuthenticationRequest INVOKE Parameters
Field
15
16
AuthenticationRequest INVOKE Parameters
Value
Timer: ART
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
18
Length
variable octets
M
6.3.2.1
19
Contents
17
Notes
20
21
ElectronicSerialNumber
M
6.5.2.63
22
MobileIdentificationNumber
M
6.5.2.81
23
MSCID (Serving MSC)
M
6.5.2.82
25
SystemAccessType
M
6.5.2.145
26
SystemCapabilities (Serving)
M
6.5.2.146
AuthenticationData
O
6.5.2.9
a
29
AuthenticationResponse
O
6.5.2.10
b
30
CallHistoryCount
O
6.5.2.18
b
ConfidentialityModes (Actual)
O
6.5.2.50
c
33
Digits (Dialed)
O
6.5.2.58
d
34
PC_SSN (Serving MSC or VLR or HLR)
O
6.5.2.93
e
24
27
28
31
32
35
36
RandomVariable
O
6.5.2.101
b
37
SenderIdentificationNumber
O
6.5.2.116
f
38
TerminalType
O
6.5.2.154
g
39
40
41
42
Notes:
a.
Include if the SystemAccessType value is Call Origination and if the air
interface encoding of dialed digits is not TBCD.
b.
Include if the SystemAccessType value is Call Origination, Page Response, or
Registration and the authentication parameters were requested (AUTH=1 in the
Overhead Message Train) on the system access.
c.
Include if the SystemAccessType value is Flash Request and if the
SignalingMessageEncryptionKey parameter was provided to the Serving MSC.
d.
Include if the SystemAccessType value is Call Origination or Flash Request.
e.
Include to override lower layer addressing if the receiving VLR, HLR, or AC is
known to be in the same national SS7 network. If included, it identifies the
functional entity sending the message.
f.
Include to identify the functional entity sending the message.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
17
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
The remainder of this section is retained without modification.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
18
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.13
FeatureRequest
3
(TIA/EIA-41-D Chapter 5, page 5-48)
4
5
6
This operation was named RemoteFeatureControlRequest prior to this revision of the
Interim Standard.
7
8
9
10
The FeatureRequest operation is used to request feature-related treatment on behalf of a
registered MS.
11
12
13
14
The FeatureRequest operation is initiated with a TCAP INVOKE (LAST). This is carried
by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
follows:
15
16
Table 35
FeatureRequest INVOKE Parameters
17
18
FeatureRequest INVOKE Parameters
19
Field
20
Value
Timer: FRRT
Type
Reference
21
Identifier
SET [NATIONAL 18]
M
6.3.2.1
22
Length
variable octets
M
6.3.2.1
23
24
Notes
Contents
25
Digits (Dialed)
M
6.5.2.58
26
ElectronicSerialNumber
M
6.5.2.63
28
MobileIdentificationNumber
M
6.5.2.81
29
BillingID (Originating)
O
6.5.2.16
a
CallingPartyNumberDigits1
O
6.5.2.21
b, k
32
CallingPartyNumberDigits2
O
6.5.2.22
b, k
33
CallingPartySubaddress
O
6.5.2.25
b
27
30
31
34
ConferenceCallingIndicator
O
6.5.2.49
c
36
MobileDirectoryNumber
O
6.5.2.80
d
37
MSCID (Serving)
O
6.5.2.82
e
MSCIdentificationNumber
O
6.5.2.83
bj
40
OneTimeFeatureIndicator
O
6.5.2.88
f
41
PC_SSN
O
6.5.2.93
g
43
SenderIdentificationNumber
O
6.5.2.116
h
44
TransactionCapability
O
6.5.2.160
i
35
38
39
42
45
46
47
48
49
50
51
Notes:
a.
Include for recording purposes or for call correlation (see DMH).
b.
Include if applicable.
c.
Include to indicate the number of conferees already in the call.
d.
Include if available for recording purposes (see DMH).
e.
Include to identify the Anchor MSC. (This may become the Originating MSC for
subsequent call redirection.)
f.
Include if any OneTimeFeatureIndicator parameter status bits are set (i.e., have
value of 1).
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
19
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
g.
Include if SS7 may be used for subsequent call redirection.
h.
Include if different from the MSCIdentificationNumber to identify the functional
entity sending the message.
1
2
3
4
5
i.
Include on IS-41-C or later.
j.
Include on N.S0016-0 or later to identify the MSC sending the message. Do not
include if N.S0016-0 is not supported by this entity.
6
7
k.
Send only the National (Significant) Number (with Nature of Number set to
National) if the E.164 country code of the caller’s number matches the E.164
country code used for numbers from the MSC’s Country’s numbering plan.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
20
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
3
4
The FeatureRequest operation success is reported with a TCAP RETURN RESULT
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
as follows:
5
Table 36
6
7
FeatureRequest RETURN RESULT Parameters
FeatureRequest RETURN RESULT Parameters
8
Field
9
10
Value
Type
Reference
Notes
Identifier
SET [NATIONAL 18]
M
6.3.2.2
12
Length
variable octets
M
6.3.2.2
13
Contents
FeatureResult
M
6.5.2.67
16
AccessDeniedReason
O
6.5.2.1
a
17
ActionCode
O
6.5.2.2
b
11
14
15
18
AnnouncementList
O
6.5.2.6
c
20
CallingPartyNumberString1
O
6.5.2.23
d
21
CallingPartyNumberString2
O
6.5.2.24
d
23
CallingPartySubaddress
O
6.5.2.25
d
24
CarrierDigits
O
6.5.2.28
d
25
ConferenceCallingIndicator
O
6.5.2.49
e
27
Digits (Dialed)
O
6.5.2.58
f
28
DMH_AccountCodeDigits
O
6.5.2.59
g
19
22
26
29
DMH_AlternateBillingDigits
O
6.5.2.60
g
31
DMH_BillingDigits
O
6.5.2.61
g
32
DMH_RedirectionIndicator
O
6.5.2.62
d
GroupInformation
O
6.5.2.69
h
35
MobileDirectoryNumber
O
6.5.2.80
g
36
NoAnswerTime
O
6.5.2.87
d
OneTimeFeatureIndicator
O
6.5.2.88
i
39
PACAIndicator
O
6.5.2.91
j
40
PilotNumber
O
6.5.2.95
h
42
RedirectingNumberDigits
O
6.5.2.107
d
43
RedirectingNumberString
O
6.5.2.108
d
44
RedirectingSubaddress
O
6.5.2.109
d
46
RoutingDigits
O
6.5.2.114
d
47
TerminationList
O
6.5.2.156
k
TerminationTriggers
O
6.5.2.159
d
30
33
34
37
38
41
45
48
49
50
51
Notes:
52
a.
Include if access is denied. If included, no other optional parameters shall be
included (with the exception of the AnnouncementList parameter).
b.
Include if action to be performed is not implied through presence of other
parameters.
c.
Include if provision of one or more tones or announcements is required.
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
21
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
d.
Include if applicable.
e.
Include to direct that ongoing call be transformed into a Conference Call.
f.
Include if digits remain to be analyzed by the MSC. Encode the Digits (Dialed)
as International if:
2
3
4
5
6
7
•
•
The digits being returned are the result of a stored translation of the
termination address into a destination address (e.g., the expansion of an
abbreviated dialing string), and
the Serving MSC is known to be capable of accepting digits in International
format (e.g., the MSCIdentificationNumber parameter was received).
g.
Include if applicable and for recording purposes (see DMH).
h.
Include for multileg calls.
i.
Include if modification to normal feature processing is required for call in
progress.
8
9
10
11
12
13
14
15
16
17
18
19
20
j.
Include to indicate PACA priority level.
k.
Include if call routing is required.
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
22
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.24
InterSystemPage
3
(TIA/EIA-41-D Chapter 5, page 5-71)
4
5
The omitted portions of this section are retained without modification.
6
7
8
Table 57
9
10
InterSystemPage INVOKE Parameters
InterSystemPage INVOKE Parameters
11
Field
12
Value
Timer: ISPRT
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
Length
variable octets
M
6.3.2.1
BillingID (Originating)
M
6.5.2.16
ElectronicSerialNumber
M
6.5.2.63
20
MobileIdentificationNumber
M
6.5.2.81
21
DMH_AccountCodeDigits
O
6.5.2.59
13
14
15
16
17
18
19
22
Notes
Contents
a
AlertCode
O
6.5.2.3
a
24
CallingPartyNumberString1
O
6.5.2.23
a
25
CallingPartyNumberString2
O
6.5.2.24
a
27
CallingPartySubaddress
O
6.5.2.25
a
28
CDMASlotCycleIndex
O
6.5.2.40
b
29
CDMAStationClassMark
O
6.5.2.41
c
31
DMH_AlternateBillingDigits
O
6.5.2.60
a
32
DMH_BillingDigits
O
6.5.2.61
a
23
26
30
33
ExtendedMSCID (Serving MSC)
O
6.5.2.64
d
35
ExtendedSystemMyTypeCode (Serving MSC)
O
6.5.2.65
e
36
LegInformation
O
6.5.2.75
f
LocationAreaID
O
6.5.2.77
f
39
MobileDirectoryNumber
O
6.5.2.80
a
40
MSCID (Originating MSC)
O
6.5.2.82
g
MSCIdentificationNumber (Originating MSC)
O
6.5.2.83
fn
43
OneTimeFeatureIndicator
O
6.5.2.88
f
44
PageIndicator
O
6.5.2.92
h
46
PC_SSN (Originating MSC)
O
6.5.2.93
i
47
PilotBillingID
O
6.5.2.94
j
48
PilotNumber
O
6.5.2.95
k
34
37
38
41
42
45
49
50
RedirectingNumberString
O
6.5.2.108
a
51
RedirectingSubaddress
O
6.5.2.109
a
SenderIdentificationNumber (Serving MSC)
O
6.5.2.116
fm
54
SystemMyTypeCode (Originating MSC)
O
6.5.2.147
l
55
TerminationTreatment
O
6.5.2.158
f
TerminationTriggers
O
6.5.2.159
a
52
53
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
23
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
Notes:
2
a.
Include if available (i.e., provided in the associated RoutingRequest INVOKE).
3
b.
Included when the Serving MSC knows that the MS is operating in CDMA
Slotted Mode.
5
4
6
7
c.
Include if a CDMA channel is in use.
d.
Include to identify serving system.
e.
Include to identify serving system manufacturer.
f.
Include if known.
g.
Include to identify originating system.
h.
Include if request is to listen only. May include if request is to page.
i.
Include if available for subsequent call redirection.
j.
Include if appropriate.
k.
Include on a multileg call.
22
l.
Include to identify originating system manufacturer.
24
8
9
10
11
12
13
14
15
16
17
18
19
20
21
23
25
m. Include to identify the Serving MSC.
26
27
n.
Include on N.S0016-0 or later to identify the originating system. Do not include if
N.S0016-0 is not supported by this entity.
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
Stage-3 Signaling Protocol
24
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
3
4
The InterSystemPage operation success is reported with a TCAP RETURN RESULT
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
as follows:
5
Table 58
6
7
InterSystemPage RETURN RESULT Parameters
InterSystemPage RETURN RESULT Parameters
8
Field
9
10
Value
Type
Reference
Notes
Identifier
SET [NATIONAL 18]
M
6.3.2.2
12
Length
variable octets
M
6.3.2.2
13
Contents
AccessDeniedReason
O
6.5.2.1
a
16
BillingID (Terminating)
O
6.5.2.16
b, c
17
ConditionallyDeniedReason
O
6.5.2.48
d
11
14
15
18
Digits (Destination)
O
6.5.2.58
c
20
ExtendedMSCID (Border MSC)
O
6.5.2.64
c
21
ExtendedSystemMyTypeCode (Border MSC)
O
6.5.2.65
c
23
MSCIdentificationNumber
O
6.5.2.83
e
24
PC_SSN (Border MSC)
O
6.5.2.93
f
19
22
25
26
27
28
29
30
31
Notes:
a.
Include if access may be denied.
b.
Required for recording purposes (see DMH).
c.
If one parameter is present, they all must be present.
d.
Include if Call Waiting is possible.
e.
Include to identify the Border MSC.
f.
Include if Digits (Destination) parameter is provided, and SS7 is used. Include if
Digits (Destination) parameter is provided, SS7 is used, and the Originating
MSC and the Border MSC may be in the same national SS7 network.
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
TIA/EIA-41-D Chapter 5 Modifications
25
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.4.2.27
LocationRequest
2
(TIA/EIA-41-D Chapter 5, page 5-77)
The LocationRequest operation is used by an Originating MSC to obtain call treatment
instructions from the HLR. The call is identified by the dialed MS address digits received
by the Originating MSC.
The LocationRequest operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
3
4
5
6
7
8
9
10
11
12
Table 63
LocationRequest INVOKE Parameters
LocationRequest INVOKE Parameters
Field
Value
13
Timer: LRT
Type
Reference
Notes
14
15
16
17
Identifier
SET [NATIONAL 18]
M
6.3.2.1
18
Length
variable octets
M
6.3.2.1
19
20
Contents
21
BillingID (Originating)
M
6.5.2.16
22
Digits (Dialed)
M
6.5.2.58
23
MSCID (Originating)
M
6.5.2.82
SystemMyTypeCode (Originating)
M
6.5.2.147
CallingPartyNumberDigits1
O
6.5.2.21
a, f
CallingPartyNumberDigits2
O
6.5.2.22
a, f
CallingPartySubaddress
O
6.5.2.25
a
30
MSCIdentificationNumber
O
6.5.2.83
b
31
PC_SSN (Originating)
O
6.5.2.93
c
RedirectingNumberDigits
O
6.5.2.107
a
34
RedirectingSubaddress
O
6.5.2.109
a
35
TerminationAccessType
O
6.5.2.155
d
37
TransactionCapability
O
6.5.2.160
e
38
24
25
26
27
28
29
32
33
36
39
40
Notes:
41
a.
Include if available (i.e., provided in call origination).
b.
Include on N.S0016-0 or later to identify the MSC sending the message. Do not
include if N.S0016-0 is not supported by this entity.
43
c.
Include if SS7 may be used for subsequent call redirection.
46
d.
Include if call involves a special access situation (e.g., Roamer port access).
e.
Include on IS-41-C or later.
f.
Send only the National (Significant) Number (with Nature of Number set to
National) if the E.164 country code of the caller’s number matches the E.164
country code used for numbers from the MSC’s Country’s numbering plan. This
consideration only applies for MS to MS calls recognized as such by the MSC
serving the calling MS.
42
44
45
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
26
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
3
4
The LocationRequest operation success is reported with a TCAP RETURN RESULT
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
as follows:
5
Table 64
6
7
LocationRequest RETURN RESULT Parameters
LocationRequest RETURN RESULT Parameters
8
Field
9
10
Value
Type
Reference
Notes
Identifier
SET [NATIONAL 18]
M
6.3.2.2
12
Length
variable octets
M
6.3.2.2
13
Contents
ElectronicSerialNumber
M
6.5.2.63
a
16
MobileIdentificationNumber
M
6.5.2.81
a
17
MSCID (Serving MSC)
M
6.5.2.82
b
11
14
15
18
AccessDeniedReason
O
6.5.2.1
c
20
AnnouncementList
O
6.5.2.6
d
21
CallingPartyNumberString1
O
6.5.2.23
e
23
CallingPartyNumberString2
O
6.5.2.24
e
24
Digits (Carrier)
O
6.5.2.58
f
25
Digits (Destination)
O
6.5.2.58
g, h, p
27
DMH_AccountCodeDigits
O
6.5.2.59
i
28
DMH_AlternateBillingDigits
O
6.5.2.60
i
19
22
26
29
DMH_BillingDigits
O
6.5.2.61
i
31
DMH_RedirectionIndicator
O
6.5.2.62
j
32
GroupInformation
O
6.5.2.69
k
MobileDirectoryNumber
O
6.5.2.80
i
30
33
34
35
NoAnswerTime
O
6.5.2.87
l
36
OneTimeFeatureIndicator
O
6.5.2.88
m
PC_SSN (Serving MSC or VLR)
O
6.5.2.93
n
39
RedirectingNumberDigits
O
6.5.2.107
j
40
RedirectingNumberString
O
6.5.2.108
f
42
RedirectingSubaddress
O
6.5.2.109
e, j
43
RoutingDigits
O
6.5.2.114
f
44
TerminationList
O
6.5.2.156
o
TerminationTriggers
O
6.5.2.159
f
37
38
41
45
46
47
48
Notes:
49
a.
Value is all zeroes, if unknown.
b.
Value is MSCID (Originating), if access is denied or routing to a directory
number.
c.
Include if access may be denied.
d.
Include if one or more tones or announcements is to be applied to the MS.
e.
Include if feature is active and if a LocalTermination parameter is included
within the TerminationList parameter.
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
27
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
f.
Include if applicable.
g.
Include if call is to be routed over a network.
h.
Use only with system not capable of using the TerminationList parameter.
i.
Include if available for recording purposes (see DMH).
j.
Include if available and call redirection may apply.
2
3
4
5
6
7
8
9
10
k.
Include for multileg calls.
l.
Include to request an override of the Originating MSC’s default No Answer Time
value.
11
12
13
14
m. Include if modification to normal feature processing is required for a call in
progress.
15
16
17
n.
Use is for further study.
o.
Include if call routing is required.
p.
For N.S0016-0 or later, encode the Digits (Destination) as International if it is
known that the Originating MSC can accept the digits in this format (e.g., the
MSCIdentificationNumber parameter was received in the INVOKE) and an HLR
stored number is being provided.
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
28
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.30
OriginationRequest
3
4
5
6
7
8
9
10
(TIA/EIA-41-D Chapter 5, page 5-81)
The OriginationRequest operation is used to request call origination treatment on behalf
of a registered MS.
The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
11
Table 68
12
13
14
OriginationRequest INVOKE Parameters
Field
15
16
OriginationRequest INVOKE Parameters
Value
Timer: ORT
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
18
Length
variable octets
M
6.3.2.1
19
Contents
17
Notes
20
21
BillingID (originating)
M
6.5.2.16
22
Digits (Dialed)
M
6.5.2.58
23
ElectronicSerialNumber
M
6.5.2.63
25
MobileIdentificationNumber
M
6.5.2.81
26
MSCID (Originating MSC)
M
6.5.2.82
OriginationTriggers
M
6.5.2.90
29
TransactionCapability
M
6.5.2.160
30
CallingPartyNumberDigits1
O
6.5.2.21
a, g
CallingPartyNumberDigits2
O
6.5.2.22
a, g
33
CallingPartySubaddress
O
6.5.2.25
a
34
MobileDirectoryNumber
O
6.5.2.80
b
36
MSCIdentificationNumber
O
6.5.2.83
c
37
OneTimeFeatureIndicator
O
6.5.2.88
d
38
PC_SSN (Originating MSC)
O
6.5.2.93
e
SenderIdentificationNumber
O
6.5.2.116
f
24
27
28
31
32
35
39
40
41
42
43
Notes:
a.
Include if applicable.
b.
Include if available for recording purposes (see DMH).
c.
Include on N.S0016-0 or later to identify the MSC initiating the message. Do not
include if N.S0016-0 is not supported by this entity.
d.
Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).
e.
Include if SS7 may be used for subsequent call redirection.
f.
Include to identify intermediate message sender if different from the
MSCIdentificationNumber to identify the functional entity sending the message.
g.
Send only the National (Significant) Number (with Nature of Number set to
National) if the E.164 country code of the caller’s number matches the E.164
country code used for numbers from the MSC’s Country’s numbering plan.
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
29
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
The OriginationRequest operation success is reported with a TCAP RETURN RESULT
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
as follows:
1
2
3
4
5
Table 69
OriginationRequest RETURN RESULT Parameters
6
7
OriginationRequest RETURN RESULT Parameters
8
Field
Value
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.2
Length
variable octets
M
6.3.2.2
Notes
9
10
11
12
13
Contents
14
AccessDeniedReason
O
6.5.2.1
a
ActionCode
O
6.5.2.2
b
16
AnnouncementList
O
6.5.2.6
c
17
CallingPartyNumberString1
O
6.5.2.23
d, e
CallingPartyNumberString2
O
6.5.2.24
d, e
20
CallingPartySubaddress
O
6.5.2.25
d, e, f
21
CarrierDigits
O
6.5.2.28
g
23
Digits (Dialed)
O
6.5.2.58
h
24
DMH_AccountCodeDigits
O
6.5.2.59
i
25
DMH_AlternateBillingDigits
O
6.5.2.60
i
27
DMH_BillingDigits
O
6.5.2.61
i
28
DMH_RedirectionIndicator
O
6.5.2.62
i, j
GroupInformation
O
6.5.2.69
k
31
MobileDirectoryNumber
O
6.5.2.80
i
32
NoAnswerTime
O
6.5.2.87
l
OneTimeFeatureIndicator
O
6.5.2.88
m
35
PilotNumber
O
6.5.2.95
k
36
RedirectingNumberDigits
O
6.5.2.107
f
RedirectingNumberString
O
6.5.2.108
d
39
RedirectingSubaddress
O
6.5.2.109
d, e
40
RoutingDigits
O
6.5.2.114
g
42
TerminationList
O
6.5.2.156
n
43
TerminationTriggers
O
6.5.2.57
o
44
15
18
19
22
26
29
30
33
34
37
38
41
46
Notes:
a.
45
47
Include if access is denied. If included, no other optional parameters shall be
included (with the exception of the AnnouncementList parameter).
48
49
50
b.
Include if action to be performed is not implied through presence of other
parameters.
51
52
53
c.
Include if one or more tones or announcements are to be applied to the MS.
d.
Include if a LocalTermination parameter is included in the TerminationList
parameter.
e.
Include if the related feature is active.
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
30
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
f.
Include if a PSTNTermination parameter or an IntersystemTermination
parameter is included within the TerminationList parameter.
g.
Include if applicable.
h.
Include if digits remain to be translated by the MSC. Encode the Digits (Dialed)
as International if:
2
3
4
5
6
7
8
9
•
The digits being returned are the result of a stored translation of the
termination address into a destination address (e.g., the expansion of an
abbreviated dialing string),and
•
the Serving MSC is known to be capable of accepting digits in International
format (e.g., the MSCIdentificationNumber parameter was received).
10
11
12
13
14
15
16
17
i.
Include if available for recording purposes (see DMH).
j.
Include if redirection may apply.
k.
Include for multileg calls.
l.
Include to request an override of the Serving MSC’s default No Answer Time
value.
18
19
20
21
22
23
24
25
26
27
28
29
m. Include if modification to normal feature processing is required for the call in
progress.
n.
Include if call routing is required.
o.
Include to indicate processing in the Originating MSC for failed call attempts.
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
TIA/EIA-41-D Chapter 5 Modifications
31
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.4.2.31
QualificationDirective
2
(TIA/EIA-41-D Chapter 5, page 5-84)
The QualificationDirective operation is used to update the authorization information,
profile information, or both, previously obtained for an MS.
The QualificationDirective operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
3
4
5
6
7
8
9
10
11
Table 70
QualificationDirective INVOKE Parameters
QualificationDirective INVOKE Parameters
Field
12
Timer: QDT
Value
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
Length
variable octets
M
6.3.2.1
Notes
13
14
15
16
17
18
19
Contents
20
ElectronicSerialNumber
M
6.5.2.63
21
MobileIdentificationNumber
M
6.5.2.81
22
QualificationInformationCode
M
6.5.2.99
23
SystemMyTypeCode (HLR or VLR)
M
6.5.2.147
AuthorizationDenied
O
6.5.2.13
a
AuthorizationPeriod
O
6.5.2.14
b
DeniedAuthorizationPeriod
O
6.5.2.53
c
29
Digits (Carrier)
O
6.5.2.58
d, e
30
Digits (Destination)
O
6.5.2.58
d, f, j
LocationAreaID
O
6.5.2.77
g
33
Profile **Macro**
O
6.5.2.97
h, k
34
SenderIdentificationNumber
O
6.5.2.116
i
24
25
26
27
28
31
32
35
36
37
Notes:
a.
38
If included, no other optional parameters except the DeniedAuthorizationPeriod
parameter shall be present.
39
40
41
b.
Include if validation is being updated.
c.
May be included if the AuthorizationDenied parameter is present to indicate the
interval before re-authorization may be attempted.
42
43
44
45
46
d.
Use only on systems not capable of supporting the TransactionCapability
parameter.
47
48
49
e.
Include if profile is being updated and preferred carrier is applicable.
f.
Include if profile is being updated and originations are restricted (e.g., set to
NPA-NXX to restrict originations to a 6-digit NANP office code or set to
NPA-NXX-XXXX to restrict originations to a single NANP directory number).
51
g.
May be included from VLR to MSC-V. Usage from the HLR is not defined.
55
h.
Include applicable parameter(s) (see 6.5.2.97).
i.
Include to identify the functional entity sending the message.
50
52
53
54
56
57
58
59
60
Stage-3 Signaling Protocol
32
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
j.
For N.S0016-0 or later, encode the Digits (Destination) as International if it is
known that the Serving MSC can accept the digits in this format (e.g., the
MSCIdentificationNumber parameter was received during registration).
k.
For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and
RestrictionDigits parameters should be encoded as International when loaded
into the profile if it is known that the Serving MSC can accept them in this
format (e.g., the MSCIdentificationNumber parameter was received during
registration).
2
3
4
5
6
7
8
9
10
11
12
The remainder of this section is retained without modification.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
TIA/EIA-41-D Chapter 5 Modifications
33
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.4.2.32
QualificationRequest
2
(TIA/EIA-41-D Chapter 5, page 5-86)
The QualificationRequest operation is used (a) to request validation of an MS, (b) to
request an MS’s profile information, or (c) both.
The QualificationRequest operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
3
4
5
6
7
8
9
10
11
Table 72
QualificationRequest INVOKE Parameters
QualificationRequest INVOKE Parameters
Field
Value
12
Timer: QRT
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
Length
variable octets
M
6.3.2.1
Notes
13
14
15
16
17
18
19
Contents
20
ElectronicSerialNumber
M
6.5.2.63
21
MobileIdentificationNumber
M
6.5.2.81
22
QualificationInformationCode
M
6.5.2.99
23
SystemMyTypeCode (MSC or VLR)
M
6.5.2.147
MSCID (Serving MSC or Originating MSC)
O
6.5.2.82
a
MSCIdentificationNumber
O
6.5.2.83
c
SenderIdentificationNumber
O
6.5.2.116
b
29
SystemAccessType
O
6.5.2.145
a
30
TransactionCapability
O
6.5.2.160
a
24
25
26
27
28
31
32
33
Notes:
34
a.
Should be included on IS-41-C or later.
b.
Include to identify the functional entity sending the message.
c.
Include on N.S0016-0 or later to identify the MSC sending the message. Do not
include if N.S0016-0 is not supported by this entity.
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
Stage-3 Signaling Protocol
34
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
3
4
The QualificationRequest operation success is reported with a TCAP RETURN RESULT
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
as follows:
5
Table 73
6
7
QualificationRequest RETURN RESULT Parameters
QualificationRequest RETURN RESULT Parameters
8
Field
9
10
Value
Type
Reference
Notes
Identifier
SET [NATIONAL 18]
M
6.3.2.2
12
Length
variable octets
M
6.3.2.2
13
Contents
SystemMyTypeCode (VLR or HLR)
M
6.5.2.147
16
AuthorizationDenied
O
6.5.2.13
a
17
AuthorizationPeriod
O
6.5.2.14
b
11
14
15
18
DeniedAuthorizationPeriod
O
6.5.2.53
c
20
Digits (Carrier)
O
6.5.2.58
d
21
Digits (Destination)
O
6.5.2.58
e, h
23
MSCID (HLR)
O
6.5.2.82
f
24
Profile **Macro**
O
6.5.2.97
g, i
19
22
25
26
27
28
Notes:
a.
If included, no other optional parameters except the DeniedAuthorizationPeriod
parameter shall be present.
b.
Include if validation requested.
c.
May be included if the AuthorizationDenied parameter is present to indicate the
interval before re-authorization may be attempted.
d.
Include if profile requested and preferred carrier is applicable and
TransactionCapability parameter is not received.
e.
Include if profile requested and originations are restricted to NPA-NXX or
NPA-NXX-XXXX and TransactionCapability parameter is not received.
f.
Include on IS-41-C and later and authorization is not denied.
g.
Include applicable parameter(s) (see 6.5.2.97).
h.
For N.S0016-0 or later, encode the Digits (Destination) as International if it is
known that the Serving MSC can accept the digits in this format (e.g., the
MSCIdentificationNumber parameter was received in the INVOKE).
i.
For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and
RestrictionDigits parameters should be encoded as International when loaded
into the profile if it is known that the Serving MSC can accept them in this
format (e.g., the MSCIdentificationNumber parameter was received in the
INVOKE).
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
TIA/EIA-41-D Chapter 5 Modifications
35
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.4.2.33
RedirectionDirective
2
(TIA/EIA-41-D Chapter 5, page 5-89)
The RedirectionDirective operation is used during feature processing to direct the MSC to
forward the indicated call.
The RedirectionDirective operation is initiated with a TCAP INVOKE (LAST). This is
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
3
4
5
6
7
8
9
10
11
Table 76
RedirectionDirective INVOKE Parameters
RedirectionDirective INVOKE Parameters
Field
Value
12
Timer: RDT
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
Length
variable octets
M
6.3.2.1
Notes
13
14
15
16
17
18
19
Contents
20
BillingID (Originating)
M
6.5.2.16
21
Digits (Destination)
M
6.5.2.58
22
ElectronicSerialNumber
M
6.5.2.63
23
MobileIdentificationNumber
M
6.5.2.81
25
SystemMyTypeCode (MSC)
M
6.5.2.147
26
Digits (Carrier)
O
6.5.2.58
a
DMH_AccountCodeDigits
O
6.5.2.59
b
29
DMH_AlternateBillingDigits
O
6.5.2.60
b
30
DMH_BillingDigits
O
6.5.2.61
b
MSCIdentificationNumber
O
6.5.2.83
c
33
RedirectingNumberString
O
6.5.2.108
d
34
RedirectingSubaddress
O
6.5.2.109
d
SenderIdentificationNumber
O
6.5.2.116
e
24
27
28
31
32
35
36
37
38
Notes:
39
40
a.
Include if applicable.
b.
Include if available for recording purposes (see DMH).
42
c.
MSC initiating the message.
Include on N.S0016-0 or later to identify the initiating
Do not include if N.S0016-0 is not supported by this entity.
44
41
43
45
46
d.
Optionally, include to override normal Originating MSC redirection number
treatment.
47
48
49
e.
Include if the sending functional entity’s identification number is not equal to the
initiating
MSC’s
identification
number
if
different
from the
MSCIdentificationNumber to identify the functional entity sending the message.
50
51
52
53
The remainder of this section is retained without modification.
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
36
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.37
RegistrationNotification
3
4
5
6
7
8
9
10
11
(TIA/EIA-41-D Chapter 5, page 5-94)
The RegistrationNotification operation is used to report the location of an MS and,
optionally, to (a) validate the MS or (b) validate the MS and obtain its profile
information.
The RegistrationNotification operation is initiated with a TCAP INVOKE (LAST). This
is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
12
Table 82
13
14
15
RegistrationNotification INVOKE Parameters
RegistrationNotification INVOKE Parameters
16
Field
Value
Timer: RNT
Type
Reference
Notes
17
18
Identifier
SET [NATIONAL 18]
M
6.3.2.1
19
Length
variable octets
M
6.3.2.1
20
Contents
21
22
ElectronicSerialNumber
M
6.5.2.63
23
MobileIdentificationNumber
M
6.5.2.81
MSCID (Serving MSC)
M
6.5.2.82
26
QualificationInformationCode
M
6.5.2.99
27
SystemMyTypeCode (Serving MSC or VLR)
M
6.5.2.147
AvailabilityType
O
6.5.2.15
a
30
BorderCellAccess
O
6.5.2.17
b
31
ControlChannelData
O
6.5.2.51
b
33
ExtendedMSCID (VLR)
O
6.5.2.64
c
34
LocationAreaID
O
6.5.2.77
d
35
MSCIdentificationNumber (Serving MSC)
O
6.5.2.83
l
24
25
28
29
32
36
37
PC_SSN (Serving MSC or VLR)
O
6.5.2.93
e
38
ReceivedSignalQuality
O
6.5.2.106
b
ReportType
O
6.5.2.112
f
41
SenderIdentificationNumber
O
6.5.2.116
g
42
SMS_Address
O
6.5.2.123
h
SMS_MessageWaitingIndicator
O
6.5.2.129
i
45
SystemAccessData
O
6.5.2.144
b
46
SystemAccessType
O
6.5.2.145
j
39
40
43
44
47
SystemCapabilities
O
6.5.2.146
k
49
TerminalType
O
6.5.2.154
j
50
TransactionCapability
O
6.5.2.160
j
48
51
52
53
54
Notes:
a.
Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode
or sleep mode).
b.
Include if access occurred in a border cell (based on internal algorithms).
c.
Included by VLR if its MSCID is different than the MSC’s MSCID.
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
37
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
d.
May be included from MSC to VLR.
e.
Include to override lower layer addressing if the receiving VLR or HLR is
known to be in the same national SS7 network.
2
3
4
5
f.
Include if authentication parameters were requested by the Serving MSC
(AUTH=1 in the Overhead Message Train) but were not received from the MS
for the system access.
6
7
8
9
g.
Include to identify message sender.
h.
Include to indicate that the Serving MSC supports Short Message Service.
i.
Include if the MS was previously registered with this VLR, the MS is registering
to a new serving MSC that does not support SMS, and an SMS message is
pending delivery in the previous serving system. This is only used between a
VLR and an HLR.
13
j.
Include on IS-41-C and later.
18
k.
Include if the system is authentication capable (including voice channel
authentication only systems where all flags are zero).
20
10
11
12
14
15
16
17
19
21
22
l.
Include on N.S0016-0 or later to identify the MSC sending the message. Do not
include if N.S0016-0 is not supported by this entity.
23
24
25
26
27
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
Stage-3 Signaling Protocol
38
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
3
4
The RegistrationNotification operation success is reported with a TCAP RETURN
RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is
encoded as follows:
5
Table 83
6
7
RegistrationNotification RETURN RESULT Parameters
RegistrationNotification RETURN RESULT Parameters
8
Field
9
10
Value
Type
Reference
Notes
Identifier
SET [NATIONAL 18]
M
6.3.2.2
12
Length
variable octets
M
6.3.2.2
13
Contents
SystemMyTypeCode (VLR or HLR)
M
6.5.2.147
16
AuthorizationDenied
O
6.5.2.13
a
17
AuthorizationPeriod
O
6.5.2.14
b
11
14
15
18
ControlChannelData
O
6.5.2.51
c
20
DeniedAuthorizationPeriod
O
6.5.2.53
d
21
Digits (Carrier)
O
6.5.2.58
e
23
Digits (Destination)
O
6.5.2.58
f, k
24
MSCID (HLR)
O
6.5.2.82
g
25
Profile **Macro**
O
6.5.2.97
h, l
27
ReceivedSignalQuality
O
6.5.2.106
c
28
SenderIdentificationNumber
O
6.5.2.116
i
19
22
26
29
30
31
SMS_MessageWaitingIndicator
O
6.5.2.129
j
SystemAccessData
O
6.5.2.144
c
32
33
Notes:
34
a.
If included, only the ControlChannelData, DeniedAuthorizationPeriod,
ReceivedSignalQuality, and SystemAccessData optional parameters have
significance.
b.
Include if validation requested.
c.
Include if AuthorizationDenied parameter is included with value of Multiple
Access.
d.
May be included if the AuthorizationDenied parameter is present to indicate the
interval before re-authorization may be attempted.
e.
Include if the profile is requested, the preferred carrier is applicable, and the
CarrierDigits parameter is not included in the Profile macro.
f.
Include if the profile is requested, originations are restricted to NPA-NXX or
NPA-NXX-XXXX, and the RestrictionDigits parameter is not included in the
Profile macro.
g.
Include on IS-41-C and later and authorization is not denied.
h.
Include applicable parameter(s) (see 6.5.2.97).
i.
Include to identify the functional entity sending the message.
j.
Include to indicate that an SMS message is pending delivery.
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
TIA/EIA-41-D Chapter 5 Modifications
39
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
k.
l.
For N.S0016-0 or later, encode the Digits (Destination) as International if it is
known that the Serving MSC can accept the digits in this format (e.g., the
MSCIdentificationNumber parameter was received in the INVOKE).
1
For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and
RestrictionDigits parameters should be encoded as International when loaded
into the profile if it is known that the Serving MSC can accept them in this
format (e.g., the MSCIdentificationNumber parameter was received in the
INVOKE).
5
2
3
4
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
40
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.4.2.46
TransferToNumberRequest
3
4
5
6
7
8
9
10
(TIA/EIA-41-D Chapter 5, page 5-110)
The TransferToNumberRequest operation is used during feature processing to obtain an
MS’s forward-to number from the HLR.
The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST).
This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
encoded as follows:
11
Table 100 TransferToNumberRequest INVOKE Parameters
12
13
14
TransferToNumberRequest INVOKE Parameters
Field
15
16
Value
Timer: TTNRT
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.1
18
Length
variable octets
M
6.3.2.1
19
Contents
17
Notes
20
21
ElectronicSerialNumber
M
6.5.2.63
22
MobileIdentificationNumber
M
6.5.2.81
23
RedirectionReason
M
6.5.2.110
25
SystemMyTypeCode (MSC)
M
6.5.2.147
26
BillingID (Originating)
O
6.5.2.16
a
GroupInformation
O
6.5.2.69
b
29
LegInformation
O
6.5.2.75
c
30
MSCID (Originating)
O
6.5.2.82
d
MSCIdentificationNumber
O
6.5.2.83
eg
33
PilotBillingID
O
6.5.2.94
f
34
PilotNumber
O
6.5.2.95
f
TransactionCapability
O
6.5.2.160
e
24
27
28
31
32
35
36
37
38
Notes:
39
a.
Include to identify the Originating MSC and its BillingID for subsequent call
redirection.
b.
Include if available (i.e., if provided in the associated RoutingRequest INVOKE
or LocationRequest RETURN RESULT) for the None Reachable termination
trigger.
c.
Include if available (i.e., if provided in the associated RoutingRequest INVOKE
or LocationRequest RETURN RESULT) for any termination trigger except
None Reachable.
d.
Include on TIA/EIA-41 or later.
e.
Include on IS-41-C or later.
f.
Include if available.
g.
Include on N.S0016-0 or later to identify the MSC initiating the message. Do not
include if N.S0016-0 is not supported by this entity.
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
41
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
The TransferToNumberRequest operation success is reported with a TCAP RETURN
RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is
encoded as follows:
1
2
3
4
5
Table 101 TransferToNumberRequest RETURN RESULT Parameters
6
7
TransferToNumberRequest RETURN RESULT Parameters
8
Field
Value
Type
Reference
Identifier
SET [NATIONAL 18]
M
6.3.2.2
Length
variable octets
M
6.3.2.2
Notes
9
10
11
12
13
Contents
14
Digits (Destination)
M
6.5.2.58
a, k
AccessDeniedReason
O
6.5.2.1
b
16
ActionCode
O
6.5.2.2
c
17
AnnouncementList
O
6.5.2.6
d
CallingPartyNumberString1
O
6.5.2.23
e
20
CallingPartyNumberString2
O
6.5.2.24
e
21
CallingPartySubaddress
O
6.5.2.25
e, f
23
Digits (Carrier)
O
6.5.2.58
g
24
DMH_AccountCodeDigits
O
6.5.2.59
h
25
DMH_AlternateBillingDigits
O
6.5.2.60
h
27
DMH_BillingDigits
O
6.5.2.61
h
28
DMH_RedirectionIndicator
O
6.5.2.62
h
GroupInformation
O
6.5.2.69
i
31
MobileDirectoryNumber
O
6.5.2.80
h
32
NoAnswerTime
O
6.5.2.87
g
RedirectingNumberDigits
O
6.5.2.107
f
35
RedirectingNumberString
O
6.5.2.108
e
36
RedirectingSubaddress
O
6.5.2.109
e, f
TerminationList
O
6.5.2.156
j
39
TerminationTriggers
O
6.5.2.159
g
40
15
18
19
22
26
29
30
33
34
37
38
41
42
Notes:
43
a.
This parameter is ignored if the TerminationList parameter is provided.
b.
Include if access is denied. If included, no other optional parameters shall be
included (with the exception of the AnnouncementList).
44
45
c.
Include if action to be performed is not implied through presence of other
parameters.
46
47
48
49
50
d.
Include if one or more tones or announcements are to be applied to the MS.
51
e.
Include if related feature is active and if a LocalTermination parameter is
included within the TerminationList parameter.
53
52
54
55
f.
Optionally
include
if
a
PSTNTermination
parameter
or
an
IntersystemTermination parameter is included within the TerminationList
parameter.
56
57
58
59
60
Stage-3 Signaling Protocol
42
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
g.
Include if applicable.
h.
Include if available for recording purposes (see DMH).
i.
Include for multileg calls.
j.
Include if call routing is required.
k.
For N.S0016-0 or later, encode the Digits (Destination) as International if it is
known that the requesting MSC can accept the digits in this format (e.g., the
MSCIdentificationNumber parameter was received in the INVOKE) and an HLR
stored number is being provided.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
TIA/EIA-41-D Chapter 5 Modifications
43
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.5
AnnouncementCode
2
(TIA/EIA-41-D Chapter 5, page 5-133)
3
4
The omitted portions of this section are retained without modification.
5
6
7
Table 117 AnnouncementCode value
11
Bits H G F E D C B A
Value
0 0
0 0
0 0
0 0
0
0 0
0 0
0 0
0 1
1
0 0
0 0
0 0
1 0
2
0 0
0 0
0 0
1 1
3
0 0
0 0
9
10
Tone (octet 1)
0 0
8
0 0
0 0
0 0
0 1
0 1
0 1
0 0
4
0 1
5
1 0
6
Meaning
DialTone. A continuous 350 Hz tone added to a
440 Hz tone.
RingBack or AudibleAlerting. A 440 Hz tone
added to a 480 Hz tone repeated in a 2s on 4s
off pattern.
InterceptTone or MobileReorder. Alternating
440 Hz and 620 Hz tones, each on for 250 ms.
CongestionTone or ReorderTone. A 480 Hz
tone added to a 620 Hz tone repeated in a 250
ms on, 250 ms off cycle.
BusyTone. A 480 Hz tone added to a 620 Hz
tone repeated in a 500 ms on, 500 ms off cycle.
ConfirmationTone. A 350 Hz tone added to a
440 Hz tone repeated 3 times in a 100 ms on,
100 ms off cycle.
AnswerTone. Answer tone is not presently used
in many North American networks. Answer tone
is not presently used in North American
networks.
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
The remainder of this section is retained without modification.
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
Stage-3 Signaling Protocol
44
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.58
Digits
3
4
5
6
(TIA/EIA-41-D Chapter 5, page 5-189)
The Digits parameter is based on the Digits parameter defined in Section 3 of ANSI
T1.114-1988. Where there are differences, this Standard takes precedence.
7
Field
8
9
10
11
12
13
Value
Type
Reference
Notes
a
Identifier
Digits IMPLICIT DigitsType
M
6.5.1.2
Length
variable octets
M
6.5.1.1
Contents
H
G
F
E
D
C
B
A
octet
Notes
1
b
14
Type of Digits
15
Nature of Number
16
17
Numbering Plan
18
Encoding
Number of Digits
19
20
2nd
21
4th
22
nth
24
c
d, e
4
f
BCD Digit
1st
BCD Digit
5
BCD Digit
3rd
BCD Digit
6
•••
23
2
3
•••
n-1st
BCD Digit
•••
m
BCD Digit
25
Figure 66 Digits parameter for BCD digits
26
27
28
Notes for all Digits parameter variants:
29
30
a.
Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field
encoding.
d.
The Numbering Plan field is set to Telephony Numbering.
e.
The Encoding field is set to BCD.
31
32
33
34
35
36
37
38
39
Notes for the Digits (Dialed) as the dialed number variant:
b.
The Type of Digits field is set to Dialed Number. The digits are the digits dialed
by an MS with an unknown Nature of Number (or Numbering Plan).
c.
The Nature of Number field is National or International ignored on receipt.
f.
The Number of Digits is between 0 and 32.
40
41
42
43
44
45
46
47
48
49
Notes for the Digits (Dialed) as the called number variant:
b.
The Type of Digits field is set to Dialed Number. The digits should be a
directory number assigned to a MS or for other specialized purposes.
c.
The Nature of Number field is National.
f.
The Number of Digits is set appropriately. 10 for a North American Numbering
Plan number, although this may vary by country or by bilateral agreement.
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
45
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
Notes for the Digits (Carrier) variant:
2
b.
The Type of Digits field is set to Carrier.
c.
The Nature of Number field is National or International.
3
4
5
6
7
Notes for the Digits (Destination) as a profile restriction variant:
b.
The Type of Digits field is set to Destination Number. The digits specify a the
national leading digits of the directory number (e.g., 6-digit NANP office code)
or the leading digits of an international E.164 number or a full directory number
(e.g., 10-digit NANP directory number) or a full international E.164 number
used to restrict the numbers dialed by an MS as indicated by the
OriginationIndicator parameter.
c.
The Nature of Number field is set to National or to International as appropriate.
f.
The Number of Digits is set appropriately (e.g. either 6 or 10 for NANP).
8
9
10
11
12
13
14
15
16
17
18
19
20
Notes for the Digits (Destination) as a network destination variant:
21
22
b.
c.
The Type of Digits field is set to Destination Number. The digits specify a
telephone network destination address.
The Nature of Number field is set as necessary:
i.
ii.
i.
23
24
25
26
for a destination within the same country (or multi-country integrated
numbering plan) the digits may consist of a national number without prefix
digits. The Nature of Number field is set to National.
27
otherwise, the digits should consist of a full E.164 number, including
country code. The Nature of Number field is set to International.
31
from NANP countries to destinations within NANP, the digits should
consist of 10 digits without prefix digits. The Nature of Number field is set
to National.
34
28
29
30
32
33
35
36
37
ii.
from non NANP countries to destinations within NANP, the Nature of
Number field is set to International.
38
39
40
iii. for destinations within the same country outside of NANP, the digits should
consist of a national number without prefix digits. The Nature of Number
field is set to National.
41
42
43
44
iv. for destinations between countries outside of NANP, the digits shall consist
of a country code followed by a national number without prefix digits. The
Nature of Number field is set to International.
45
46
47
48
v.
for destinations between different systems (even within the same country),
the digits may consist of a country code followed by a national number
without prefix digits. The Nature of Number field is set to International.
49
50
51
52
vi. from NANP countries to destinations outside of NANP, the digits may
consist of a country code followed by a national number without prefix
digits. The Nature of Number field is set to International.
f.
The Number of Digits is between 0 and at least 15.
53
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
46
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.76
Local Termination
3
4
5
6
(TIA/EIA-41-D Chapter 5, page 5-208)
The LocalTermination (LOCTERM) parameter is used to provide an MSC with routing
information for calls which are to be terminated on the same MSC.
7
Field
8
9
12
Type
Reference
Identifier
LocalTermination
IMPLICIT SET
M
6.5.1.2
Length
variable
M
6.5.1.1
6.5.2.63
10
11
Value
Notes
13
Contents
14
ElectronicSerialNumber
M
15
MobileIdentificationNumber
M
6.5.2.81
17
TerminationTreatment
M
6.5.2.158
18
AlertCode
O
6.5.2.3
19
CarrierDigits
O
6.5.2.28
b, c
21
DestinationDigits
O
6.5.2.56
d, e
22
LegInformation
O
6.5.2.75
a
23
MobileDirectoryNumber
O
6.5.2.80
b, f
OneTimeFeatureIndicator
O
6.5.2.88
b, g
26
RoutingDigits
O
6.5.2.114
b, h
27
TerminationTriggers
O
6.5.2.159
a, b
VoiceMailboxPIN
O
6.5.2.165
i
30
VoiceMailboxNumber
O
6.5.2.164
31
•••
16
a, b
20
24
25
28
29
j
k
32
Figure 84 LocalTermination parameter
33
34
35
36
37
38
39
Notes:
a.
Optional, if the TerminationTreatment indicates termination to an MS.
b.
This parameter has precedence for this call leg over the parameters outside the
TerminationList parameter or the subscriber’s profile.
c.
Optional, for intra-MSC, inter-LATA preferred carrier call routing.
d.
Optionally include if TerminationTreatment parameter value is Dialogue, to
select a dialogue or to provide information to a dialogue.
e.
Optionally include if TerminationTreatment parameter value
VoiceMailRetrieval or VoiceMailStorage to select the voice mail system.
f.
Include to identify the MS if different than MIN for call recording purposes.
g.
Include if modification to normal feature processing is required.
h.
Optional, for special routing purposes.
i.
Optional, if the TerminationTreatment value is VoiceMailRetrieval or
VoiceMailStorage.
j.
Include if the TerminationTreatment value is
VoiceMailStorage and the mailbox is not the MIN.
40
41
42
43
44
45
46
47
is
48
49
50
51
52
53
54
55
56
57
58
VoiceMailRetrieval
or
59
60
TIA/EIA-41-D Chapter 5 Modifications
47
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
k.
1
Ignore unexpected parameters, if received.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
Stage-3 Signaling Protocol
48
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.83
MSCIdentificationNumber
3
4
5
6
(TIA/EIA-41-D Chapter 5, page 5-215)
The MSCIdentificationNumber (MSCIN) parameter indicates the identification number
of an MSC sending a message.
7
Field
8
9
Value
12
13
14
Reference
Notes
a
Identifier
MSCIdentificationNumber
IMPLICIT DigitsType
M
6.5.1.2
Length
variable octets
M
6.5.1.1
10
11
Type
Contents
H
G
F
E
D
C
B
A
octet
Notes
1
b
15
Type of Digits
16
17
Nature of Number
18
Numbering Plan
19
Encoding
Number of Digits
20
21
2nd
1st
BCD Digit
2
c
3
d, e
4
f
BCD Digit
5
3rd BCD Digit
6
•••
•••
22
4th BCD Digit
23
24
•••
25
nth
26
27
n-1st
BCD Digit
m
BCD Digit
Figure 91 MSCIdentificationNumber parameter for BCD digits
28
29
30
Notes:
31
a.
Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field
encoding.
b.
Set to Not Used. The Type of Digits field is ignored on receipt.
c.
The Nature of Number field bit A is set as applicable to International. Other bits
are set as applicable.
d.
The Numbering Plan field is set to Land Mobile Numbering (E.212) as
applicable.
e.
The Encoding field is set to BCD.
f.
The Number of Digits is between 0 and at least 15.
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
TIA/EIA-41-D Chapter 5 Modifications
49
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.89
OriginationIndicator
2
(TIA/EIA-41-D Chapter 5, page 5-222)
The OriginationIndicator (ORIGIND) parameter defines the type of calls the MS is
allowed to originate.
3
4
5
6
7
Field
Value
Identifier
Length
Type
Reference
OriginationIndicator
IMPLICIT Unsigned Enumerated
M
6.5.1.2
1 octet
M
Notes
9
10
11
6.5.1.1
12
Contents
H
8
13
G
F
E
D
C
B
A
octet
Notes
1
a, b
14
15
Allowed Call Types
Figure 97 OriginationIndicator parameter
16
17
18
19
Notes:
20
a.
b.
For values 4, 5, and 8, the Digits (Destination) parameter (see 6.5.2.58) shall
accompany the OriginationIndicator parameter and shall contain the selected
leading digits or directory number (e.g., NPA-NXX or NPA-NXX-XXXX for
NANP) or international E.164 number.
21
Value 8, Single directory number (e.g., NPA-NXX-XXXX for NANP), shall
cause all originations to be treated as if this single number had been dialed, with
exceptions (e.g., “9-1-1,” “*-9-1-1”).
26
22
23
24
25
27
28
29
30
Table 154 OriginationIndicator value
31
32
33
Allowed Call Types (octet 1)
34
Bits H G F E D C B A
Value
Meaning
35
36
0
0
0
0
0
0
0
0
0
0
0 0
0
0
0
0
0
0
0
0
0
0
0 0
0
0
0
0
0
0
0
0
0
1
0 1
0
0
1
1
0
0
1
0
1
0
0
1
2
3
4
0 1
5
0 0
0 0
0 1
1 0
6
0 0
0 0
0 1
1 1
7
0 0
0 0
1 0
0 0
8
Not used.
Prior agreement.
Origination denied.
Local calls only.
Selected leading digits of directory number or
of international E.164 number (e.g.,
NPA-NXX for NANP). See Note (a) above.
Selected leading digits of directory number
or of international E.164 number and local
calls only (e.g., NPA-NXX for NANP). See
Note (a) above.
National long distance (includes local calls and
may include neighboring countries).
International calls (includes national long
distance and local calls).
Single directory number or international
E.164 number (e.g., NPA-NXX-XXXX for
NANP). See Notes (a) and (b) above.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
The remainder of this section is retained without modification.
56
57
58
59
60
Stage-3 Signaling Protocol
50
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.90
OriginationTriggers
3
4
5
6
(TIA/EIA-41-D Chapter 5, page 5-223)
The OriginationTriggers (ORIGTRIG) parameter defines the origination trigger points
that are currently active for the subscriber.
7
Field
8
9
Value
12
13
14
15
16
OriginationTriggers
IMPLICIT OCTET STRING
M
6.5.1.2
Length
variable octets
M
6.5.1.1
H
G
F
E
RvtC
Unrec
WZ
Int’l
D
Reserved
21
22
C
OLATA ILATA
NLTOLL LTOLL
B
A
octet
Local
All
1
PA
DP
Pound
DS
Star
2
7
digits
6
digits
5
digits
4
digits
3
digits
2
digits
1
digit
No
digits
3
15
digits
14
digits
13
digits
12
digits
11
digits
10
digits
9
digits
8
digits
4
18
20
Notes
Contents
17
19
Reference
Identifier
10
11
Type
23
n
•••
24
25
Notes
a
b
Figure 98 OriginationTriggers parameter
26
27
28
29
Notes:
a.
Set reserved values to 0 when sending, and process other triggers before treating
received reserved values the same as All.
b.
If unknown octets with bits set are received, process other triggers before
treating the same as All. Send only defined (or significant) octets.
30
31
32
33
34
35
Table 155 OriginationTriggers value
36
37
38
All Origination (All) (octet 1, bit A)
39
Bits H G F E D C B A
40
Value
0
1
41
42
0
1
43
44
45
46
Meaning
Trigger is not active.
Launch an OriginationRequest for any call
attempt. This overrides all other values.
Local (octet 1, bit B)
Bits H G F E D C B A
47
Value
0
1
48
0
1
49
Meaning
Trigger is not active.
Launch an OriginationRequest for any local call
attempt.
50
51
52
Local Intra-LATA Toll (LTOLL ILATA) (octet 1, bit C)
Bits H G F E D C B A
Value
Meaning
53
0
1
54
55
0
1
56
57
Trigger is not active.
Launch an OriginationRequest for any local toll
intra-LATA call attempt. Refers to intra-LATA
toll within the NANP.
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
51
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
Table 161 OriginationTriggers value (continued)
2
3
Inter-LATA Non-Local Toll (OLATA NLTOLL) (octet 1, bit D)
Bits H G F E D C B A
Value
0
1
0
1
4
Meaning
5
Trigger is not active.
Launch an OriginationRequest for any interLATA toll call attempt toll calls outside the
local carrier's serving area.
6
7
8
9
10
International (Int’l ) (octet 1, bit E)
Bits H G F E D C B A
11
Value
0
1
0
1
12
Meaning
Trigger is not active.
Launch an OriginationRequest
international call attempt.
13
14
for
any
15
16
17
World Zone (WZ) (octet 1, bit F)
Bits H G F E D C B A
18
Value
Meaning
19
20
0
1
0
1
Trigger is not active.
Launch an OriginationRequest for any call
attempt outside of the current World Zone (as
defined in ITU-T Rec. E.164). [not
recommended for use].
21
22
23
24
25
26
Unrecognized Number (Unrec) (octet 1, bit G)
27
Bits H G F E D C B A
Value
0
1
0
1
Meaning
Trigger is not active.
Launch an OriginationRequest for any call
attempt to an unrecognized number.
28
29
30
31
32
Revertive Call (RvtC) (octet 1, bit H)
Bits H G F E D C B A
33
Value
Meaning
34
35
0
1
0
1
Trigger is not active.
Launch an OriginationRequest for any Revertive
Call attempt.
36
37
38
39
Star (octet 2, bit A)
40
Bits H G F E D C B A
Value
Meaning
41
42
0
1
0
1
Trigger is not active.
Launch an OriginationRequest for any number
beginning with a Star ‘*’ digit.
44
45
46
Double Star (DS) (octet 2, bit B)
Bits H G F E D C B A
43
47
Value
0
1
0
1
Meaning
Trigger is not active.
Launch an OriginationRequest for any number
beginning with two Star ‘**’ digits.
48
49
50
51
52
Pound (octet 2, bit C)
53
Bits H G F E D C B A
Value
0
1
0
1
Meaning
54
Trigger is not active.
Launch an OriginationRequest for any number
beginning with a Pound ‘#’ digit.
56
55
57
58
59
60
Stage-3 Signaling Protocol
52
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
The remainder of this section is retained without modification.
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
TIA/EIA-41-D Chapter 5 Modifications
53
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.93
PC_SSN
2
(TIA/EIA-41-D Chapter 5, page 5-230)
The PC_SSN parameter carries the ANSI national SS7 Point Code (PC) and Subsystem
Number (SSN) of a particular wireless network cellular functional entity. Type indicates
the type of functional entity (e.g., HLR, VLR, MSC). Used for subsequent routing by the
application and takes precedence over lower layer addressing. The Point Code may
represent a single entity or an alias for mated pair entities. Two descriptions of the format
are shown, one for ANSI SS7 point codes and a more general format for other national
point code formats.
3
4
5
6
7
8
9
10
11
12
Field
Value
Type
Reference
Identifier
PC_SSN
IMPLICIT OCTET STRING
M
6.5.1.2
Length
5 octets
M
6.5.1.1
Notes
14
15
16
17
Contents
H
13
18
G
F
E
D
C
B
A
19
octet
Notes
ReservedType
1
b
21
ANSI Point Code—Member Number
2
a
22
ANSI Point Code—Cluster Number
3
a
ANSI Point Code—Network Number
4
a
25
Subsystem Number (SSN)
5
a
26
20
23
24
27
Figure 101 PC_SSN parameter (ANSI)
28
29
30
Notes:
31
a.
See 5.1.2.
b.
Reserved bits shall be ignored on receipt and set to zero on sending.
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
Stage-3 Signaling Protocol
54
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
3
Value
Field
2
6
7
Reference
Identifier
PC_SSN
IMPLICIT OCTET STRING
M
6.5.1.2
Length
5 octets
M
6.5.1.1
4
5
Type
Notes
Contents
8
9
H
G
F
10
E
D
C
B
A
Reserved
octet
Notes
1
a
2
b,c
3
b,c
4
b,c
5
c
11
12
13
Point Code
14
15
16
Subsystem Number (SSN)
17
18
Figure 101A
19
PC_SSN parameter (generic)
20
21
Notes:
22
a.
Reserved bits shall be ignored on receipt and set to zero on sending.
b.
Bit A of Octet 2 is the first bit that would be emitted if the point code was
transmitted by the MTP layer. If the point code is less than 24 bits in length, then
all bits beyond the end of the point code up to and including bit H of Octet 4,
should be set to 0.
c.
See 5.3.
23
24
25
26
27
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
TIA/EIA-41-D Chapter 5 Modifications
55
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.97
Profile
2
(TIA/EIA-41-D Chapter 5, page 5-234)
The Profile is a collection of the subscriber’s calling profile information. This information
is a list of optional parameters. The Profile macro has been defined solely for editorial
convenience, and does not affect the encoding in any way.
3
4
5
6
7
8
PROFILE
9
Type
Reference
Notes
10
11
Contents
12
13
AuthenticationCapability
O
6.5.2.8
a
CallingFeaturesIndicator
O
6.5.2.20
b
CarrierDigits
O
6.5.2.28
c
16
DMH_AccountCodeDigits
O
6.5.2.59
d
17
DMH_AlternateBillingDigits
O
6.5.2.60
d
19
DMH_BillingDigits
O
6.5.2.61
d
20
GeographicAuthorization
O
6.5.2.68
e
21
MessageWaitingNotificationCount
O
6.5.2.78
f
23
MessageWaitingNotificationType
O
6.5.2.79
g
24
MobileDirectoryNumber
O
6.5.2.80
d
OriginationIndicator
O
6.5.2.89
h
27
OriginationTriggers
O
6.5.2.90
i
28
PACAIndicator
O
6.5.2.91
j
PreferredLanguageIndicator
O
6.5.2.96
k
31
RestrictionDigits
O
6.5.2.113
l
32
RoutingDigits
O
6.5.2.114
m
SMS_OriginationRestrictions
O
6.5.2.136
n
35
SMS_TerminationRestrictions
O
6.5.2.138
o
36
SPINIPIN
O
6.5.2.139
p
38
SPINITriggers
O
6.5.2.140
q
39
TerminationRestrictionCode
O
6.5.2.157
r
40
TerminationTriggers
O
6.5.2.159
s
14
15
18
22
25
26
29
30
33
34
37
Figure 105 Profile Macro
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
56
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
Notes:
2
3
4
5
6
a.
Include on IS-41-C or later.
b.
Include to identify feature authorization and activity.
c.
Include if preferred carrier is applicable and TransactionCapability supported.
d.
Include if available for recording purposes (see DMH).
e.
Include if available for certain authorization restricted areas.
f.
Include if MessageWaitingNotificationType is Message Waiting Indication and
number of messages waiting is authorized.
g.
Include if Message Waiting Notification feature is active and a message is
waiting.
h.
Include to indicate the type of calls allowed for origination service.
i.
Include to indicate OriginationRequest triggers.
j.
Include to identify the PACA feature.
k.
Include to identify the Preferred Language feature.
l.
Include if originations are restricted, e.g., to NPA-NXX or NPA-NXX-XXXX
and TransactionCapability supported. Set Nature of Number to International if it
is known that the destination network element for the profile can accept digits in
this format (e.g. MSCIdentificationNumber parameter previously received.)
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
m. Include for special routing information.
n.
Include for MS originated Short Message Service.
o.
Include for MS terminated Short Message Service.
p.
Include if local SPINI operation supported.
q.
Include to indicate Subscriber PIN Intercept triggers.
r.
Include to indicate the type of call termination service.
s.
Include to indicate the RedirectionRequest or TransferToNumberRequest
triggers.
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
TIA/EIA-41-D Chapter 5 Modifications
57
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.98
PSTNTermination
2
(TIA/EIA-41-D Chapter 5, page 5-236)
The PSTNTermination (PSTNTERM) parameter is used to provide an MSC with routing
information for calls which are to be terminated in the PSTN.
3
4
5
6
7
Field
Type
Reference
PSTNTermination
IMPLICIT SET
M
6.5.1.2
variable
M
6.5.1.1
DestinationDigits
M
6.5.2.56
h
14
CarrierDigits
O
6.5.2.28
a, b
15
ElectronicSerialNumber
O
6.5.2.63
c
17
LegInformation
O
6.5.2.75
d
18
MobileIdentificationNumber
O
6.5.2.81
c, e
19
RoutingDigits
O
6.5.2.114
b, e
21
TerminationTriggers
O
6.5.2.159
b, f
22
g
23
Identifier
Length
Value
Notes
8
9
10
11
12
Contents
13
16
20
•••
24
Figure 106 PSTNTermination parameter
25
26
27
Notes:
28
a.
b.
Optional, for preferred carrier inter-LATA call routing. Note that this
information may not be valid across international boundaries.
This parameter has precedence for this call leg over the parameters outside the
TerminationList parameter or the subscriber profile.
29
30
31
32
33
34
c.
Optional, for recording purposes.
d.
Include if part of a multi leg call.
e.
Optional, for special routing purposes.
f.
Include to indicate processing for failed call attempts.
g.
Ignore unexpected parameters, if received.
h.
Encode the DestinationDigits as International if the Originating MSC is known
to be capable of accepting digits in International format (e.g.
MSCIdentificationNumber parameter was received.)
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
Stage-3 Signaling Protocol
58
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.113 RestrictionDigits
3
4
5
6
7
8
(TIA/EIA-41-D Chapter 5, page 5-248)
The RestrictionDigits parameter specifies either the leading digits of the directory number
(e.g., 6-digit NANP office code) or a full directory number (e.g., 10-digit NANP directory
number) for which call originations are allowed, as indicated in the OriginationIndicator
parameter.
9
Field
10
11
Value
14
15
16
Reference
Notes
a
Identifier
RestrictionDigits
IMPLICIT DigitsType
M
6.5.1.2
Length
variable octets
M
6.5.1.1
12
13
Type
Contents
H
G
F
E
D
C
B
A
octet
Notes
17
18
Type of Digits
1
b
19
Nature of Number
2
c
3
d, e
4
f
20
Numbering Plan
Encoding
21
Number of Digits
22
23
2nd
24
4th
25
BCD Digit
1st
BCD Digit
5
BCD Digit
3rd
BCD Digit
6
•••
26
27
nth
•••
n-1st
BCD Digit
•••
m
BCD Digit
28
Figure 121 RestrictionDigits parameter for BCD digits
29
30
31
32
33
Notes:
a.
Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field
encoding.
b.
Ignore the field Type of Digits on receipt.
c.
The Nature of Number field is set as applicable.
d.
The Numbering Plan field is set to Telephony Numbering.
e.
The Encoding field is set to BCD.
f.
The Number of Digits is set as applicable (e.g. either 6 or 10 in NANP).
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
TIA/EIA-41-D Chapter 5 Modifications
59
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
6.5.2.116 SenderIdentificationNumber
2
(TIA/EIA-41-D Chapter 5, page 5-251)
The SenderIdentificationNumber (SENDERIN) parameter indicates the identification
number of the functional entity that is sending a message.
3
4
5
6
7
Field
Value
Identifier
Length
Type
Reference
Notes
SenderIdentificationNumber
IMPLICIT DigitsType
M
6.5.1.2
a
variable octets
M
9
10
11
6.5.1.1
12
Contents
H
8
13
G
F
E
D
C
B
A
14
octet
Notes
Type of Digits
1
b
16
Nature of Number
2
c
17
3
d, e
4
f
15
Numbering Plan
Encoding
Number of Digits
2nd
1st
BCD Digit
5
4th BCD Digit
3rd BCD Digit
6
•••
•••
•••
nth BCD Digit
n-1st BCD Digit
m
BCD Digit
18
19
20
21
22
Figure 124 SenderIdentificationNumber parameter for BCD digits
23
24
25
26
27
28
29
Notes:
a.
30
Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field
encoding.
31
32
33
b.
Set to Not Used. The Type of Digits field is ignored on receipt.
c.
The Nature of Number field bit A is set as applicable to International. Other bits
are set as applicable.
34
35
36
37
38
d.
The Numbering Plan field is set to Land Mobile Numbering (E.212) as
applicable.
39
40
41
e.
The Encoding field is set to BCD.
f.
The Number of Digits is between 0 and at least 15.
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Stage-3 Signaling Protocol
60
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.123 SMS_Address
3
4
5
6
7
8
9
(TIA/EIA-41-D Chapter 5, page 5-258)
The SMS_Address (SMSADDR) parameter is used to convey the current routing address
of the Serving MSC for the purpose of short message termination to an MS-based SME.
If SS7 is used for international SMS message routing, this parameter should be formatted
as an E.212 number. If SS7 is used for national message routing, this parameter may be
formatted either as an SS7 point code address or as an E.212 number.
10
Field
11
12
Value
Type
Reference
Notes
a
Identifier
SMS_Address IMPLICIT
DigitsType
M
6.5.1.2
15
Length
variable octets
M
6.5.1.1
16
Contents
13
14
17
18
H
G
F
E
D
C
B
A
octet
Notes
19
Type of Digits
1
b
20
Nature of Number
2
c
3
d, e
4
f
21
Numbering Plan
22
Encoding
Number of Digits
23
24
2nd
25
4th
26
27
BCD Digit
1st
BCD Digit
5
BCD Digit
3rd
BCD Digit
6
•••
•••
•••
28
nth
29
30
n-1st
BCD Digit
BCD Digit
m
Figure 132 SMS_Address parameter for BCD digits
31
32
33
Notes:
34
a.
See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding.
b.
Type of Digits is ignored on receipt.
c.
Nature of Number may be National or International.
d.
Numbering Plan supported shall include E.164, E.212, X.121, and Private
numbering plan for this parameter variant.
e.
The encoding field shall always be set to BCD for this parameter variant.
f.
The Number of Digits ranges from 0 to at least 15.
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
TIA/EIA-41-D Chapter 5 Modifications
61
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
Field
Value
Identifier
Length
Type
Reference
Notes
SMS_Address IMPLICIT
DigitsType
M
6.5.1.2
a
variable octets
M
1
2
3
4
5
6.5.1.1
6
Contents
H
7
G
F
E
D
C
B
A
Type of Digits
Nature of Number
Numbering Plan
Encoding
octet
Notes
8
1
b
10
2
c
11
3
d, e
12
9
13
MSB
IP Address
4
14
5
15
6
LSB
7
Figure 133 SMS_Address Encoding for an IP address
16
17
18
19
20
21
Notes:
a.
22
See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding.
23
24
b.
Type of Digits is ignored on receipt.
c.
Nature of Number may be National or International.
d.
Numbering Plan shall be IP for this parameter variant.
e.
Encoding shall be octet string for this parameter variant.
25
26
27
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
Stage-3 Signaling Protocol
62
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
Field
2
3
Value
Reference
Notes
a
Identifier
SMS_Address IMPLICIT
DigitsType
M
6.5.1.2
Length
variable octets
M
6.5.1.1
4
5
Type
6
7
8
Contents
H
G
F
E
9
D
C
B
A
Type of Digits
10
Nature of Number
11
12
Numbering Plan
Encoding
octet
Notes
1
b
2
c
3
d, e
13
14
Point Code—Member Number
4
15
Point Code—Cluster Number
5
Point Code—Network Number
6
Subsystem Number (SSN)
7
16
17
18
19
20
Figure 134 SMS_Address parameter for an ANSI SS7 Point Code Address
21
22
23
Notes:
a.
See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding.
b.
Type of Digits is ignored on receipt.
c.
Nature of Number may shall be National or International.
d.
Numbering Plan shall be SS7 for this parameter variant.
e.
Encoding shall be octet string for this parameter variant.
24
25
26
27
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
TIA/EIA-41-D Chapter 5 Modifications
63
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
Value
Type
Reference
Notes
SMS_Address IMPLICIT
DigitsType
M
6.5.1.2
a
variable octets
M
Field
Identifier
Length
1
2
3
4
5
6.5.1.1
6
Contents
H
7
G
F
E
D
C
B
Type of Digits
Nature of Number
Numbering Plan
Encoding
A
octet
Notes
8
1
b
10
2
c
11
3
d, e
12
4
f
9
13
Point Code
5
6
Subsystem Number (SSN)
Figure 134A
7
SMS_Address Parameter for a Generic SS7 Point Code
Address
14
15
16
17
18
19
20
21
22
Notes:
23
a.
See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding.
24
b.
Type of Digits is ignored on receipt.
26
c.
Nature of Number shall be National.
d.
Numbering Plan shall be SS7 for this parameter variant.
e.
Encoding shall be octet string for this parameter variant.
f.
Bit A of Octet 4 is the first bit that would be emitted if the point code was
transmitted by the MTP layer. If the point code is less than 24 bits in length, then
all bits beyond the end of the point code up to and including bit H of Octet 6,
should be set to 0.
25
27
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
Stage-3 Signaling Protocol
64
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.2.140 SPINITriggers
3
4
5
6
(TIA/EIA-41-D Chapter 5, page 5-287)
The SPINITriggers parameter defines the trigger points that are currently active for the
subscriber.
7
Field
8
9
Value
12
13
14
15
16
SPINITriggers
IMPLICIT OCTET STRING
M
6.5.1.2
Length
variable octets
M
6.5.1.1
H
G
F
E
RvtC
Unrec
WZ
Int’l
D
Reserved
21
22
C
OLATA ILATA
NLTOLL LTOLL
B
A
octet
Local
All
1
PA
DP
Pound
DS
Star
2
7
digits
6
digits
5
digits
4
digits
3
digits
2
digits
1
digit
No
digits
3
15
digits
14
digits
13
digits
12
digits
11
digits
10
digits
9
digits
8
digits
4
18
20
Notes
Contents
17
19
Reference
Identifier
10
11
Type
23
n
•••
24
25
Notes
a
b
Figure 157 SPINITriggers parameter
26
27
28
29
Notes:
a.
Set reserved values to 0 when sending, and process other triggers before treating
received reserved values the same as All.
b.
If unknown octets with bits set are received, process other triggers before
treating the same as All. Send only defined (or significant) octets.
30
31
32
33
34
35
Table 177 SPINITriggers value
36
37
38
All Origination (All) (octet 1, bit A)
39
40
Bits H G F E D C B A
41
Value
0
1
42
0
1
43
Meaning
Trigger is not active.
Execute local SPINI procedures for any call
origination. This overrides all other values.
44
45
46
Local (octet 1, bit B)
Bits H G F E D C B A
Value
Meaning
47
0
1
48
49
0
1
50
Trigger is not active.
Execute local SPINI procedures for any local
call attempt.
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
65
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
Table 177 (continued)
1
2
Local Intra-LATA Toll (LTOLL ILATA) (octet 1, bit C)
Bits H G F E D C B A
Value
0
1
0
1
Meaning
Trigger is not active.
Execute local SPINI procedures for any local
toll intra-LATA call attempt. Refers to intraLATA toll within the NANP.
3
4
5
6
7
8
9
10
Inter-LATA Non-Local Toll (OLATA NLTOLL) (octet 1, bit D)
Bits H G F E D C B A
Value
0
1
0
1
Meaning
Trigger is not active.
Execute local SPINI procedures for any interLATA toll call attempt toll calls outside the
local carrier's serving area.
11
12
13
14
15
16
17
18
International (Int’l) (octet 1, bit E)
Bits H G F E D C B A
19
Value
Meaning
20
21
0
1
0
1
Trigger is not active.
Execute local SPINI procedures for any
international call attempt.
23
24
25
World Zone (WZ) (octet 1, bit F)
Bits H G F E D C B A
22
26
Value
0
1
0
1
Meaning
Trigger is not active.
Execute local SPINI procedures for any call
attempt outside of the current World Zone (as
defined in ITU-T Rec. E.164). This value is not
recommended for use.
27
28
29
30
31
32
33
Unrecognized Number (Unrec) (octet 1, bit G)
Bits H G F E D C B A
Value
34
Meaning
35
36
0
1
0
1
Trigger is not active.
Execute local SPINI procedures for any call
attempt to an unrecognized number.
38
39
40
Revertive Call (RvtC) (octet 1, bit H)
Bits H G F E D C B A
37
41
Value
Meaning
42
43
0
1
0
1
Trigger is not active.
Execute local SPINI procedures for any
Revertive Call attempt.
44
45
46
47
Star (octet 2, bit A)
48
Bits H G F E D C B A
Value
0
1
0
1
Meaning
Trigger is not active.
Execute local SPINI procedures for any number
beginning with a Star ‘*’ digit.
49
50
51
52
53
54
The remainder of this section is retained without modification.
55
56
57
58
59
60
Stage-3 Signaling Protocol
66
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
2
6.5.3.2
DigitsType
3
(TIA/EIA-41-D Chapter 5, page 5-323)
4
5
The omitted portions of this section are retained without modification.
6
7
8
The minimum length of this parameter type variant is 7 octets.
9
Field
10
11
Value
Type
Reference
Identifier
DigitsType IMPLICIT OCTET
STRING
M
6.5.1.2
14
Length
m variable octets
M
6.5.1.1
15
Contents
12
Notes
13
16
17
H
G
F
E
D
C
B
A
Type of Digits
18
19
Nature of Number
a
octet
Notes
1
b
2
c
3
d,e
4
f
5
f
6
f
20
Numbering Plan
21
Encoding
22
23
Point Code
24
25
26
Subsystem Number (SSN)
7
27
28
Figure XXX
29
DigitsType parameter type variant for a generic SS7 point
code address
30
31
Notes:
32
33
34
35
36
a.
Where m = 7 for this parameter type variant.
b.
Type of Digits is ignored upon receipt.
c.
Nature of Number shall be National.
d.
Numbering Plan shall be SS7 for this parameter variant.
e.
Encoding shall be octet string for this parameter variant.
f.
Bit A of Octet 4 is the first bit that would be emitted if the point code was
transmitted by the MTP layer. If the point code is less than 24 bits in length, then
all bits beyond the end of the point code up to and including bit H of Octet 6,
should be set to 0.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
67
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
Table 196 DigitsType value
1
2
3
Type of Digits (octet 1, bits A-H)
Bits H G F E D C B A
0
0
0
0
0
0
0
0
0 0
0 0
0
0
0
0
0
0
0
0
0 0
0 0
0
0
0
0
0
0
0
0
0 1
0 1
0
0
1
1
4
Value
0
1
0
1
0
1
2
3
0 0
4
0 1
5
0 0
0 0
0 1
1 0
6
0 0
0 0
0 0
0 0
0 1
1 0
1 1
0 0
7
8
Meaning
Not Used.
Dialed Number or Called Party Number.
Calling Party Number.
Caller Interaction. These are the digits dialed
by a user in response to a prompt (not used in
this Standard).
Routing Number. This number is used to steer
a call towards its ultimate destination.
Billing Number. This is the number to use for
ANI, Charge Number or other recording
purposes.
Destination Number. This is the network
address of the called party.
LATA (not used in this Standard).
Carrier. The identity of In North America the
three, four, or five digits represent an
interexchange or international a preferred
carrier.
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
X X X X X X X X
-
Other values are reserved.
25
26
27
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
Stage-3 Signaling Protocol
68
TIA/EIA-41-D Chapter 5 Modifications
N.S0016-0 v 1.0
1
Table 196 (continued)
2
3
4
5
Nature of Number (octet 2, bits A-H)
Bits H G F E D C B A
Value
Meaning
6
0
1
7
8
0
1
9
10
0
1
11
12
0
0
1
1
13
14
15
16
17
18
19
20
-
0
1
0
1
X X
X
National.
International.
Presentation Allowed.
Presentation Restricted.
Number is available.
Number is not available.
User provided, not screened.
User provided, screening passed.
User provided, screening failed.
Network provided.
Reserved.
Encoding (octet 3, bits A-D)
Bits H G F E D C B A
21
22
23
24
Value
0 0
0 0
0 0
0 0
0 1
1 0
0
1
2
0 0
1 1
3
X X X X
-
25
26
27
28
Meaning
Not used.
BCD (see Digit definition below).
IA5. The International Alphabet 5 as defined in
ITU-T Rec. T.50. (also known as the
International Reference Alphabet (IRA)).
Octet string. This is used for IP and SS7
addresses.
Other values are reserved.
29
30
31
32
33
34
35
Numbering Plan (octet 3, bits E-H)
Bits H G F E D C B A
Value
0 0
0 0
0 0
0 0
0 1
1 0
0
1
2
0 0
1 1
3
0 1
0 0
4
0 1
0 1
5
0 1
0 1
1 0
1 1
6
7
1 1
0 1
13
1 1 1 0
1 1 1 1
X X X X
14
15
-
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Meaning
Unknown or not applicable.
ISDN Numbering (not used in this Standard).
Telephony Numbering (ITU-T Rec. E.164,
E.163).
Data Numbering (ITU-T Rec. X.121) (not used
in this Standard).
Telex Numbering (ITU-T Rec. F.69) (not used
in this Standard).
Maritime Mobile Numbering (not used in this
Standard).
Land Mobile Numbering (ITU-T Rec. E.212)
Private Numbering Plan (service provider
defined).
ANSI SS7 Point Code (PC) and Subsystem
Number (SSN).
Internet Protocol (IP) Address.
Reserved for extension.
Other values are reserved.
51
52
The remainder of this section is retained without modification.
53
54
55
56
57
58
59
60
TIA/EIA-41-D Chapter 5 Modifications
69
Stage-3 Signaling Protocol
N.S0016-0 v 1.0
1
5. TIA/EIA-41-D Chapter 6
“Signaling Procedures” Modifications
2
3
4
5
6
2.1
INTERSYSTEM HANDOFF PROCEDURES
(TIA/EIA-41-D Chapter 6, page 6-5)
This section provides the transaction procedures defined for the Intersystem Handoff. All
messages and associated parameters are defined in Chapter 5; Timer values are specified
in Section 7 of this Chapter.
7
8
9
10
11
12
13
14
The omitted portions of this section are retained without modification.
15
16
The procedures defined here are based on the assumption that intersystem handoff relies
upon dedicated intersystem trunks. This is required since intersystem handoff is a tightly
controlled activity of the cellular systems involved. Intersystem handoff cannot be
considered any differently than an inter-cell handoff. The intersystem handoff may or may
not be inter-LATA depending upon where the LATA boundary is and also where the
mobile call was placed.
17
18
19
20
21
22
23
24
The handoff procedures specified in the following sections can be applied to consecutive
inter-MSC handoffs for the same MS. A non-Anchor Serving MSC that has handed off a
call becomes a Tandem MSC. The initial Serving MSC retains its role as an Anchor
MSC.
25
26
27
28
29
30
3.2.3
MSC Analyze MS Dialed Number
31
(TIA/EIA-41-D Chapter 6, page 6-15)
Upon demand the Anchor MSC shall do the following:
32
33
34
35
The omitted portions of this section are retained without modification.
36
37
38
9
ELSEIF the OriginationTriggers Revertive Call trigger is on AND the dialed number
is the MS’s mobile directory number (or MIN if the mobile directory number is not
available):1
9-1
Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
PointOfReturn.
39
40
41
42
43
44
45
The omitted portions of this section are retained without modification.
46
47
11 ELSEIF any of OriginationTriggers Local, LTOLL ILATA, OLATA, NLTOLL, Int’l,
WZ, or Unrec, triggers are on AND the call type matches the corresponding trigger:
11-1
Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
PointOfReturn.
11-2
IF a Digits (Dialed) parameter is received:
48
49
50
51
52
53
54
1 If the MS is a foreign roamer and plus code dialing has not been used, the revertive call condition
is satisfied if the dialed digits consist of the international prefix followed by the full E.164 form
of the MS’s MDN. If the MS is a foreign roamer and plus code dialing has been used, this
condition is detected if the dialed digits consist of the full E.164 form of the MS’s MDN.
55
56
57
58
59
60
Stage-3 Signaling Procedures
70
TIA/EIA-41-D Chapter 6 Modifications
N.S0016-0 v 1.0
1
11-2-1
IF the type of the Digits is unknown.
2
3
11-2-1-1
4
11-2-2
5
11-3
6
Process the dialed number locally to set the PointOfReturn.
ENDIF.
ENDIF.
12 ELSEIF the any unknown OriginationTriggers are on (e.g., reserved bits set to 1 or
extra octets with any bit set to 1):
7
8
9
12-1
Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
PointOfReturn.
12
12-2
IF a Digits (Dialed) parameter is received:
13
12-2-1
10
11
14
IF the type of the Digits is unknown.
15
12-2-1-1
16
12-2-2
17
12-3
18
Process the dialed number locally to set the PointOfReturn.
ENDIF.
ENDIF.
13 ELSEIF the call type matches an active trigger in the SPINITriggers parameter:1
19
20
13-1
21
22
Execute the “MSC SPINI Originating Call Invocation” task (see 5.21.3) to set
the PointOfReturn.
23
The omitted portions of this section are retained without modification.
24
25
26
27
4.25.2
MSC Receiving InterSystemPage
28
(TIA/EIA-41-D Chapter 6, page 6-177)
29
30
When an MSC receives an InterSystemPage INVOKE, it shall perform the following:
31
32
The omitted portions of this section are retained without modification.
33
34
35
1-9-6-2-1-5
Include the Digits (Destination) parameter set to the assigned
TLDN.
1-9-6-2-1-5
IF the MSCIdentificationNumber parameter was received (or
the originating MSC is otherwise known to support
internationally formatted TLDNs):
36
37
38
39
40
41
1-9-6-2-1-5-1
42
43
44
45
46
1-9-6-2-1-X
1-9-6-2-1-X-1
47
48
49
50
1-9-6-2-1-Y
Include the Digits (Destination) parameter set equal to the
TLDN in international E.164 format with the nature of
number set to International.
ELSE:
Include the Digits (Destination) parameter set equal to the
TLDN in national E.164 format with the Nature of Number
set to National.
ENDIF.
51
52
53
54
55
56
57
58
59
1 If the MS is a foreign roamer and plus code dialing has not been used, the revertive call condition
is satisfied if the dialed digits consist of the international prefix followed by the full E.164 form
of the MS’s MDN. If the MS is a foreign roamer and plus code dialing has been used, this
condition is detected if the dialed digits consist of the full E.164 form of the MS’s MDN.
60
TIA/EIA-41-D Chapter 6 Modifications
71
Stage-3 Signaling Procedures
N.S0016-0 v 1.0
1
The remainder of this section is retained without modification.
2
3
4
4.38.2
VLR Receiving RegistrationNotification INVOKE
(TIA/EIA-41-D Chapter 6, page 6-235)
5
6
7
8
The omitted portions of this section are retained without modification.
9
10
11
(The MS is geographically authorized.)
12
12-11
IF an SMS_Address parameter is received:
12-11-1
12-11-1-1
12-11-2
12-12
13
IF the SMS_Address is different than the current SMS temporary routing
address:
15
16
GOTO Register the MS.
17
ENDIF.
18
19
ELSE:
12-12-1
14
20
IF an SMS temporary routing address exists:
12-12-1-1
Clear the SMS temporary routing address.
12-12-1-2
GOTO Register the MS (to report loss of SMS capability).
21
22
23
12-12-2
25
ENDIF.
26
12-13
ENDIF.
12-x
If the MSCIdentificationNumber parameter is received:
12-x-1
27
IF the current serving MSC did not provide its MSCIdentificationNumber
during registration:
12-x-1-1
GOTO Register the MS.
12-x-2
24
28
29
30
31
32
33
ENDIF.
34
12-y
ELSE (the MSCIdentificationNumber parameter is not received):
12-y-1
IF the current serving MSC did provide its MSCIdentificationNumber
during registration:
35
36
37
38
12-y-1-1
GOTO Register the MS.
12-y-2
39
ENDIF.
40
41
12-z
ENDIF.
12-14
IF the information requested by the QualificationInformationCode is available:
12-14-1
42
IF the QualificationInformationCode indicates Profile only or Validation
and profile:
12-14-1-1
Execute the “Loading of Profile Parameters” task (see 3.1.3).
43
44
45
46
47
48
12-14-2
ENDIF.
12-14-3
IF the QualificationInformationCode indicates Validation only or Validation
and profile:
49
12-14-3-1
Include the AuthorizationPeriod parameter set appropriately.
51
52
53
12-14-4
ENDIF.
12-14-5
Send a RETURN RESULT to the requesting MSC.
12-14-6
Exit this task.
12-15
50
54
55
56
57
ENDIF.
58
59
60
Stage-3 Signaling Procedures
72
TIA/EIA-41-D Chapter 6 Modifications
N.S0016-0 v 1.0
1
13 ENDIF.
2
Register the MS:
3
4
5
4.41.3
MSC Receiving RoutingRequest INVOKE
6
7
8
(TIA/EIA-41-D Chapter 6, page 6-254)
When an MSC receives a RoutingRequest INVOKE, it shall perform the following:
9
10
The omitted portions of this section are retained without modification.
11
12
13
1-4-6-1-2
IF the paging was successful on a bordering system.
14
1-4-6-1-2-1
Relay all parameters received via the InterSystemPage
RETURN RESULT or UnsolicitedResponse INVOKE.
1-4-6-1-2-X
IF a TLDN was received in the UnsolicitedResponse
INVOKE:
15
16
17
18
19
1-4-6-1-2-X-1
IF the MSCIdentificationNumber parameter was received
in the RoutingRequest INVOKE (or the originating MSC
is otherwise known to support internationally formatted
TLDNs):
20
21
22
23
24
1-4-6-1-2-X-1-1
Convert the Digits (Destination) to International
format, using, as country code, the country code
of the border MSC.
25
26
27
28
1-4-6-1-2-X-2
ENDIF.
29
1-4-6-1-2-Y
ENDIF.
30
1-4-6-1-2-2
Send a RETURN RESULT to the requesting VLR.
1-4-6-1-2-3
Exit this task.
31
32
33
34
The omitted portions of this section are retained without modification.
35
36
37
(TLDN is selected here.)
38
1-6
39
1-6-1
IF TLDN is available:
CASE termination treatment OF:
40
41
The omitted portions of this section are retained without modification.
42
43
44
1-6-7
ENDCASE.
45
1-6-8
Include the Digits (Destination) parameter set equal to the TLDN.
1-6-8
IF the MSCIdentificationNumber parameter was received (or the originating
MSC is otherwise known to support internationally formatted TLDNs):
46
47
48
49
1-6-8-1
50
51
52
53
1-6-8A
54
1-6-8A-1
55
56
57
1-6-8B
Include the Digits (Destination) parameter set equal to the TLDN in
international E.164 format with the Nature of Number set to
International.
ELSE:
Include the Digits (Destination) parameter set equal to the TLDN in
national E.164 format with the Nature of Number set to National.
ENDIF.
58
59
60
TIA/EIA-41-D Chapter 6 Modifications
73
Stage-3 Signaling Procedures