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 LIST OF FIGURES ...... iii 6 LIST OF TABLES...... iv 7 FOREWORD...... v 8 EDITORIAL KEY...... vi 9 ASSUMPTIONS...... vii 10 REVISION HISTORY...... vii 11 1. INTRODUCTION...... 1 12 1.1 OBJECTIVE...... 1 13 1.2 SCOPE...... 1 14 1.3 ORGANIZATION...... 1 15 2. TIA/EIA-41-D Chapter 1 “Functional Overview” Modifications...... 2 16 17 2.1 NORMATIVE REFERENCES ...... 2 18 3.1 DEFINITIONS ...... 2 19 International Mobile Subscriber Identity (IMSI) ...... 2 20 Mobile Station Identity (MSID)...... 2 21 4 SYMBOLS AND ABBREVIATIONS...... 2 22 7 GENERAL BACKGROUND AND ASSUMPTIONS...... 3 23 3. TIA/EIA-41-D Chapter 3 “Automatic Roaming Information Flows” Modifications ...... 4 24 4.17.2 Successful LocationRequest: Route to a Local MS...... 4 25 4.17.3 Successful LocationRequest: Route to an MS on Another MSC...... 5 26 4.17.5 Successful LocationRequest: Route to Multiple Terminations...... 6 27 4. TIA/EIA-41-D Chapter 5 “Signaling Protocol” Modifications ...... 7 28 5.1 ANSI SS7-BASED DATA TRANSFER SERVICES ...... 7 29 5.1.2 Signaling Connection Control Part...... 7 30 5.3 ITU-T SS7-BASED DATA TRANSFER SERVICES...... 12 31 5.3.2 Signaling Connection Control Part...... 12 32 33 6.4.2.4 AuthenticationRequest...... 17 34 6.4.2.13 FeatureRequest ...... 19 35 6.4.2.24 InterSystemPage ...... 23 36 6.4.2.27 LocationRequest ...... 26 37 6.4.2.30 OriginationRequest...... 29 38 6.4.2.31 QualificationDirective ...... 32 39 6.4.2.32 QualificationRequest ...... 34 40 6.4.2.33 RedirectionDirective...... 36 41 6.4.2.37 RegistrationNotification ...... 37 42 6.4.2.46 TransferToNumberRequest ...... 41 43 6.5.2.5 AnnouncementCode ...... 44 44 6.5.2.58 Digits ...... 45 45 6.5.2.76 Local Termination ...... 47 46 6.5.2.83 MSCIdentificationNumber ...... 49 47 6.5.2.89 OriginationIndicator ...... 50 48 6.5.2.90 OriginationTriggers ...... 51 49 50 6.5.2.93 PC_SSN...... 54 51 6.5.2.97 Profile ...... 56 52 6.5.2.98 PSTNTermination...... 58 53 6.5.2.113 RestrictionDigits...... 59 54 6.5.2.116 SenderIdentificationNumber...... 60 55 6.5.2.123 SMS_Address...... 61 56 6.5.2.140 SPINITriggers ...... 65 57 6.5.3.2 DigitsType...... 67 58 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 1 3.2.3 MSC Analyze MS Dialed Number...... 70 2 4.25.2 MSC Receiving InterSystemPage ...... 71 3 4.38.2 VLR Receiving RegistrationNotification INVOKE...... 72 4 5 4.41.3 MSC Receiving RoutingRequest INVOKE...... 73 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 Figure 66 Digits parameter for BCD digits...... 45 6 Figure 84 LocalTermination parameter...... 47 7 Figure 91 MSCIdentificationNumber parameter for BCD digits ...... 49 8 Figure 97 OriginationIndicator parameter...... 50 9 Figure 98 OriginationTriggers parameter...... 51 10 Figure 101 PC_SSN parameter (ANSI) ...... 54 11 Figure 101A PC_SSN parameter (generic)...... 55 12 Figure 105 Profile Macro...... 56 13 Figure 106 PSTNTermination parameter...... 58 14 Figure 121 RestrictionDigits parameter for BCD digits...... 59 15 Figure 124 SenderIdentificationNumber parameter for BCD digits ...... 60 16 Figure 132 SMS_Address parameter for BCD digits...... 61 17 18 Figure 133 SMS_Address Encoding for an IP address ...... 62 19 Figure 134 SMS_Address parameter for an ANSI SS7 Point Code Address ...... 63 20 Figure 134A SMS_Address Parameter for a Generic SS7 Point Code Address ...... 64 21 Figure 157 SPINITriggers parameter...... 65 22 Figure XXX 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 ANSI SS7 – MIN to HLR Global Title ...... 8 5 Table 5.1.2b ANSI SS7 – MIN to MC Global Title ...... 9 6 Table 5.1.2c ANSI SS7 – E.212 Global Title...... 10 7 Table 5.1.2d ANSI SS7 – MDN to HLR (E.164) Global Title...... 10 8 Table 5.1.2e ANSI SS7 – IMSI to MC Global Title ...... 11 9 Table 5.3.2a ITU-T SS7 – E.212 Global Title ...... 13 10 Table 5.3.2b ITU-T SS7 – E.164 Global Title ...... 15 11 Table 17 AuthenticationRequest INVOKE Parameters ...... 17 12 Table 35 FeatureRequest INVOKE Parameters...... 19 13 Table 36 FeatureRequest RETURN RESULT Parameters...... 21 14 15 Table 57 InterSystemPage INVOKE Parameters...... 23 16 Table 58 InterSystemPage RETURN RESULT Parameters...... 25 17 Table 63 LocationRequest INVOKE Parameters ...... 26 18 Table 64 LocationRequest RETURN RESULT Parameters...... 27 19 Table 68 OriginationRequest INVOKE Parameters ...... 29 20 Table 69 OriginationRequest RETURN RESULT Parameters...... 30 21 Table 70 QualificationDirective INVOKE Parameters...... 32 22 Table 72 QualificationRequest INVOKE Parameters...... 34 23 Table 73 QualificationRequest RETURN RESULT Parameters...... 35 24 Table 76 RedirectionDirective INVOKE Parameters...... 36 25 Table 82 RegistrationNotification INVOKE Parameters...... 37 26 Table 83 RegistrationNotification RETURN RESULT Parameters ...... 39 27 Table 100 TransferToNumberRequest INVOKE Parameters...... 41 28 Table 101 TransferToNumberRequest RETURN RESULT Parameters...... 42 29 Table 117 AnnouncementCode value ...... 44 30 Table 154 OriginationIndicator value...... 50 31 32 Table 155 OriginationTriggers value...... 51 33 Table 177 SPINITriggers value ...... 65 34 Table 196 DigitsType value...... 68 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 This Interim Standard contains recommendations for modifications and enhancements to 6 ANSI/TIA/EIA-41-D that are required to support international intersystem operations. 7 8 The ANSI recommendation upon which this Interim Standard builds is: 9 • TIA/EIA-41-D Cellular Radiotelecommunications Intersystem Operations, 10 Industry Association; December 1997. 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

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 5 diffmarks, strikethrough lines, and underscore lines. The editorial style employed is: 6 7 a. TIA/EIA-41-D original text deleted by N.S0016-0 has a strikethrough line. 8 9 b. Original text added by N.S0016-0 has a single underline. 10 c. Both additions and deletions are indicated by a right hand margin vertical 11 diffmark. 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 The following items are basic understandings used during the development of this 6 document: 7 8 a. E.212 global title translation is provisioned for message routing between national 9 networks. 10 b. A national SS7 network is an administrative set of SS7 nodes that are interconnected 11 12 by a common national signaling point code addressing scheme. 13 c. The signal transfer points which reside in both the international and national 14 signaling levels (i.e., gateway STPs) convert from national MTP and SCCP to 15 international MTP and SCCP and vice versa. This conversion includes changes to 16 17 global title indicator, translation type, numbering plan, encoding scheme, and nature 18 of address indicator. 19 d. International addressing implementations not employing global title translation are 20 beyond the scope of this interim standard. 21 22 e. An MSC supporting N.S0016-0 or later is assumed to be capable of receiving digit 23 strings in parameters of DigitsType with Nature of Number indicating International 24 as well as in parameters of DigitsType with Nature of Number indicating National. 25 Moreover, if the MSC receives a digit string containing the International encoding of 26 27 E.164 number from its own country’s telephony numbering plan (or the leading digits 28 of such a number), the MSC is assumed to be capable of stripping the 29 from that digit string to convert it to National (Significant) Number form. 30 31 32 REVISION HISTORY 33 34 Revision Date Remarks 35 36 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 8 This Interim Standard (N.S0016-0) provides recommendations for supporting 9 internationalization enhancements for ANSI/TIA/EIA-41-D. 10 11 12 1.2 SCOPE 13 14 This document specifies the ANSI/TIA/EIA-41-D Chapters 1, 3, 5 and 6 enhancements 15 that are necessary to support international intersystem operations. 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

1Introduction N.S0016-0 v 1.0

1 2 2. TIA/EIA-41-D Chapter 1 3 4 “Functional Overview” Modifications 5 6 7 8 2.1 NORMATIVE REFERENCES 9 (TIA/EIA-41-D Chapter 1, page 1-2) 10 11 ITU-T: 12 13 • Recommendation E.212 - The International Identification Plan for Mobile 14 Terminals and Mobile Users, November 1998. 15 16 • Recommendation Q.713 (07/96) - Signalling Connection Control Part formats 17 and codes, July 1996. 18 19 20 21 ANSI T1 Standards: 22 • ANSI T1.112-19961988 Signaling System Number 7 - Signaling Connection 23 Control Part (SCCP) 24 25 26 27 TIA/EIA: 28 29 • TIA/EIA IS-751 TIA/EIA 41-D Modifications to Support IMSI, February 1998. 30 31 32 3.1 DEFINITIONS 33 (TIA/EIA-41-D Chapter 1, page 1-5) 34 35 International Mobile Subscriber Identity (IMSI) 36 37 The IMSI is a string of decimal digits, up to a maximum of 15 digits, that identifies a 38 unique mobile terminal or mobile subscriber internationally. The IMSI consists of three 39 fields: the mobile country code, the mobile network code, and the mobile subscriber 40 41 identification number. 42 43 Mobile Station Identity (MSID) 44 45 The identifier for a mobile station. A choice of either MIN or IMSI. 46 47 48 4 SYMBOLS AND ABBREVIATIONS 49 (TIA/EIA-41-D Chapter 1, page 1-14) 50 51 IMSI International Mobile Subscriber Identity 52 MSID Mobile Station Identity 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 3 (TIA/EIA-41-D Chapter 1, page 1-30) 4 5 The omitted portions of this section are retained without modification. 6 7 8 Against this background, pProcedures for the implementation of the identified intersystem 9 services have been defined with due regard to the following general considerations: 10 11 The omitted portions of this section are retained without modification. 12 13 14 8) The procedures defined here are based on the assumption that intersystem 15 handoff relies upon dedicated intersystem trunks. This is required since 16 intersystem handoff is a tightly controlled activity of the cellular systems 17 involved. Intersystem handoff cannot be considered any differently than an inter- 18 cell handoff. The intersystem handoff may or may not be inter-LATA (Local 19 Access and Transport Area) depending upon where the LATA boundary is and 20 also where the mobile call was placed. 21 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 2 3. TIA/EIA-41-D Chapter 3 3 4 “Automatic Roaming Information Flows” 5 6 Modifications 7 8 9 4.17.2 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 16 by the Originating MSC) and returns this information to the Originating MSC in the 17 locreq. 18 19 Parameters are as in Section 4.18.1, Step-b, with the exception that PSTNRoutingInfo is 20 not included and with the following additions: 21 Parameters Usage Type 22 23 PC_SSN Originating MSC PC_SSN. Include if SS7 O 24 carriage services are used. 25 LocalRoutingInfo: Call routing information: 26 27 [TerminationList] Local termination information. Include if O 28 TerminationList is allowed. 29 [Digits(Destination)] Destination digits for use in intra-MSC call O 30 routing (may be MS’s MIN). Include if 31 applicable and if TerminationList is not 32 allowed. 33 34 [RoutingDigits] Special routing instructions. Include if O 35 applicable and if not specified within the 36 TerminationList parameter. 37 [Digits(Carrier)] Called subscriber’s PIC for use in intra-MSC, O 38 inter-LATA exchange call routing. Include if 39 applicable and if not specified within the 40 TerminationList parameter. 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 b. The HLR determines that the call shall be routed to an MS on another MSC and 9 returns this information to the Originating MSC in the locreq. 10 11 Parameters are as in Section 4.17.1, Step-b, with the exception that PSTNRoutingInfo is 12 not included and with the following additions: 13 14 Parameters Usage Type 15 PC_SSN Serving MSC PC_SSN. Include if SS7 carriage O 16 services are used. 17 18 IntersystemRoutingInfo: Call routing information: 19 [TerminationList] Intersystem termination information. Include if O 20 TerminationList is allowed. 21 22 [Digits(Destination)] Destination digits for use in inter-MSC call O 23 routing. Include if TerminationList is not allowed. 24 25 [RoutingDigits] Special routing instructions. Include if O 26 applicable and if not specified within the 27 TerminationList parameter. 28 [Digits(Carrier)] Called subscriber’s PIC for use in inter-MSC, O 29 inter-LATA exchange call routing. Include if 30 applicable and if not specified within the 31 TerminationList parameter. 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 The omitted portions of this section are retained without modification. 5 6 7 b. The HLR determines that the call shall be routed to multiple terminations and 8 returns this information to the Originating MSC in the locreq. 9 10 Parameters are as in Section 4.17.1, Step-b, with the exception that MSCID, PC_SSN, and 11 PSTNRoutingInfo are not included and with the following additions: 12 13 Parameters Usage Type 14 MultipleRoutingInfo: Call routing information: 15 16 [TerminationList] Multiple termination information. R 17 [RoutingDigits] Special routing instructions. Include if O 18 applicable and if not specified within the 19 TerminationList parameter. 20 21 [Digits(Carrier)] Called subscriber’s PIC for use in inter-MSC, O 22 inter-LATAexchange call routing. Include if 23 applicable and if not specified within the 24 TerminationList parameter. 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. TIA/EIA-41-D Chapter 5 4 5 “Signaling Protocol” Modifications 6 7 5.1 ANSI SS7-BASED DATA TRANSFER SERVICES 8 (TIA/EIA-41-D Chapter 5, page 5-6) 9 10 11 The omitted portions of this section are retained without modification. 12 13 14 5.1.2 Signaling Connection Control Part 15 (TIA/EIA-41-D Chapter 5, page 5-8) 16 17 For TIA/EIA-41 applications, the SCCP is defined in ANSI T1.112, with the following 18 exceptions and limitations: 19 20 • SCCP Class 0 connectionless service is used. 21 • The message types are Unitdata (UDT) and Unitdata Service (UDTS). The 22 SCCP shall return a UDTS message when a received UDT message cannot be 23 delivered to the specified destination and has the return message on error option 24 25 set. 26 • Whether to set the return message on error or discard message on error option 27 in the Protocol Class parameter of the UDT message is at the discretion of the 28 implementation. 29 30 •The TIA/EIA-41 has assigned the following Subsystem 31 Numbers (SSN). Use of the following SSN values are is recommended: 32 33 - 5: Mobile Application Part (MAP) 34 35 - 6: Home Location Register (HLR) 36 37 - 7: Visitor Location Register (VLR) 38 - 8: Mobile Switching Center (MSC) 39 40 - 9: Equipment Identification Register (EIR) (reserved)1 41 42 - 10: Authentication Center (AC) 43 44 - 11: Short Message Service 45 46 • In accordance with ANSI T1.112 an SSN shall be included in all messages even 47 if message routing is based on Global Title Translation (GTT). The null SSN 48 (i.e., value 0) should be used when the subsystem is not known (e.g., before a 49 global title translation takes place) per ANSI T1.112. 50 51 • Global title addresses are required in the SCCP Called Party Address and the 52 SCCP Calling Party Address for international roaming purposes. 53 54 55 56 57 58 1Detailed transactions relative to SSN value 9 are for further study. 59 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 1 communication with the HLR on the ANSI SS7 network.1 The following 2 3 encoding may be used: 4 5 Table 5.1.2a ANSI SS7 – MIN to HLR Global Title 6 7 Field Sub-field Value 8 9 Address Indicator SSN Indicator 1 10 Point Code Indicator 0 or 1 11 12 13 Global Title Indicator 2 (00102) 14 Routing Indicator 0 15 16 National or International Indicator 1 (National use) 17 18 Include applicable value 19 if known or zero 20 21 Global Title Translation Type 3 (000000112) “Cellular 22 Nationwide Roaming 23 Service” 24 25 Address Information MIN 26 27 28 • Global Title Translation on Mobile Identification Number can be used for 29 communication with the HLR. Global Title Indicator type 2 (0010) is used. A 30 translation type value of 3 is used for “MIN to HLR” translation. The global title 31 address information field contains the 10-digit MIN2. The encoding scheme is 32 BCD. Each address signal is coded as described in Section 3.4.2.3.1 of the ANSI 33 T1.112 specification. 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 55 code addressing scheme. 56 57 2Dialed digits must be converted to a 10-digit MIN for the Location Request Task and Call Data 58 Request Task when Global Title Translation communication with the HLR is used. 59 60

Stage-3 Signaling Protocol 8 TIA/EIA-41-D Chapter 5 Modifications N.S0016-0 v 1.0

1 • Global Title Translation on Mobile Identification Number can be used for 2 communication with a Message Center on the ANSI SS7 network. The following 3 encoding can be used: 4 5 6 Table 5.1.2b ANSI SS7 – MIN to MC Global Title 7 8 Field Sub-field Value 9 Address Indicator SSN Indicator 1 10 11 Point Code Indicator 0 or 1 12 13 Global Title Indicator 2 (00102) 14 15 Routing Indicator 0 16 17 National or International Indicator 1 (National use) 18 19 Subsystem Number Include applicable value 20 if known or zero 21 22 Global Title Translation Type 12 (000011002) 23 “Wireless MIN-Based 24 Short Message Service” 25 26 Address Information MIN 27 28 29 • Global Title Translation on Mobile Identification Number can be used for 30 communication with a Message Center. Global Title Indicator type 2 (0010) is 31 used. A translation type value of 12 is used for Short Message Service for “MIN 32 to MC” translation. The encoding scheme is BCD. Each address signal is coded 33 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 1 Identity) can be used for communication from a Serving System (MSC or VLR) 2 to an HLR on the same, or a different, national SS7 network using the IMSI of a 3 roaming mobile. It may also be used for communication to any network element 4 5 that is identified by an E.212 formatted address on the same, or a different 6 national SS7 network. The following encoding can be used: 7 8 Table 5.1.2c ANSI SS7 – E.212 Global Title 9 10 Field Sub-field Value 11 12 Address Indicator SSN Indicator 1 13 14 Point Code Indicator 0 or 1 15 16 Global Title Indicator 2 (00102) 17 Routing Indicator 0 18 19 National or International Indicator 1 (National use) 20 21 Subsystem Number Include applicable value 22 if known or zero 23 24 Global Title Translation Type 9 (000010012) “National 25 and International PCS 26 Roaming” 27 28 Address Information IMSI or other E.212 29 formatted address 30 31 32 • Global Title Translation on an E.164 number (e.g. Mobile Directory Number) 33 can be used for communication to an HLR on the same, or a different, national 34 SS7 network based on the Mobile Directory Number. The following encoding 35 can be used: 36 37 Table 5.1.2d ANSI SS7 – MDN to HLR (E.164) Global Title 38 39 Field Sub-field Value 40 41 Address Indicator SSN Indicator 1 42 43 Point Code Indicator 0 or 1 44 45 Global Title Indicator 2 (0010 ) 2 46 47 Routing Indicator 0 48 National or International Indicator 1 (National use) 49 50 Subsystem Number Include applicable value 51 if known or zero 52 53 Global Title Translation Type 14 (000011102) “Mobile 54 Subscriber Addressing” 55 56 Address Information E.164 Mobile Directory 57 Number 58 59 60

Stage-3 Signaling Protocol 10 TIA/EIA-41-D Chapter 5 Modifications N.S0016-0 v 1.0

1 • Global Title Translation on IMSI can be used for communication from a Serving 2 System (MSC or VLR) to a Message Center on the same, or a different, national 3 SS7 network.1 The following encoding may be used: 4 5 6 Table 5.1.2e ANSI SS7 – IMSI to MC Global Title 7 8 Field Sub-field Value 9 10 Address Indicator SSN Indicator 1 11 Point Code Indicator 0 or 1 12 13 Global Title Indicator 2 (00102) 14 15 Routing Indicator 0 16 17 National or International Indicator 1 (National use) 18 19 Subsystem Number Include applicable value 20 if known or zero 21 22 Global Title Translation Type 13 (000011012) 23 “Wireless IMSI-based 24 Short Message Service” 25 26 Address Information IMSI 27 28 29 • Use of signaling point codes, global titles, and subsystem numbers must meet 30 ANSI T1.112 requirements; such that, any allowable combination of these 31 addressing elements is supported. For example, as stated in T1.112.3, Section 32 3.4.1: 33 34 “The address consists of any one or any combination of the following elements: 35 1) signaling point code, 36 2) global title (MIN-to-HLR for TIA/EIA-41), 37 38 3) subsystem number, 39 where, the referenced address is either the called party address or the calling 40 party address fields in SCCP messages.” 41 42 • When an originating functional entity sends an SS7 message within a national 43 SS7 signaling network with a global title in the SCCP called party address field, 44 the SCCP calling party address field should include the point code and 45 subsystem number of the originating functional entity. Note that a Signaling 46 Transfer Point (STP) is considered to be an intermediate functional entity, not an 47 originating functional entity. 48 49 • When an originating functional entity sends an SS7 message across a national 50 51 SS7 signaling network boundary, the SCCP calling party address field should 52 include an E.212 global title address identifying the originating functional entity 53 to allow response messages (RETURN RESULT, RETURN ERROR, or 54 REJECT) to be routed back to the originating node. 55 56 57 58 1 No ITU-T Q.713 translation selector exists for IMSI to Message Center translation. 59 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 1 Party Address, in accordance with ANSI T1.112. (As exceptions, if the PC_SSN 2 parameter is received in an AuthenticationRequest INVOKE or in a 3 RegistrationNotification INVOKE, the address used for the response may be 4 5 derived from the received PC_SSN parameter provided the INVOKE was 6 received from a functional entity within the same national SS7 signaling 7 network.) 8 9 10 5.3 ITU-T SS7-BASED DATA TRANSFER SERVICES 11 12 (TIA/EIA-41-D Chapter 5, page 5-11) 13 14 The omitted portions of this section are retained without modification. 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 21 following exceptions and limitations: 22 23 • SCCP Class 0 connectionless service is used. 24 • The message types are Unitdata (UDT) and Unitdata Service (UDTS). The 25 SCCP shall return a UDTS message when a received UDT message cannot be 26 delivered to the specified destination and has the return message on error option 27 28 set. 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 33 34 in the Protocol Class parameter of the UDT message is at the discretion of the 35 implementation. 36 • Use of the following SSN values are is recommended: 37 38 - 5: Mobile Application Part (MAP) 39 40 - 6: Home Location Register (HLR) 41 - 7: Visitor Location Register (VLR) 42 43 - 8: Mobile Switching Center (MSC) 44 45 - 9: Equipment Identification Register (EIR) (reserved)1 46 47 - 10: Authentication Center (AC) 48 - TBD:Short Message Service (SMS) 49 50 - 11: Short Message Service 51 52 • In accordance with ITU Q.713 an SSN is recommended to be included in all 53 messages even if message routing is based on Global Title Translation (GTT). 54 The null SSN (i.e., value 0) should be used when the subsystem is not known 55 (e.g., before a global title translation takes place). 56 57 58 1Detailed transactions relative to SSN value 9 are for further study. 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 2 SCCP Calling Party Address for international roaming purposes. 3 4 • Global Title Translation on Mobile Identification Number (MIN), for 5 communication with an HLR or MC, is left to mutual agreement. 6 7 • Global Title Translation on International Mobile Subscriber Identity (IMSI) can 8 be used for communication with the HLR on the same, or a different, national 9 SS7 network. It may also be used for communication to any network element 10 that is identified by an E.212 formatted address on the same, or a different 11 national SS7 network. The following encoding can be used: 12 13 14 Table 5.3.2a ITU-T SS7 – E.212 Global Title 15 Field Sub-field Value 16 17 Address Indicator Point Code Indicator (PCI) 0 or 1 18 19 SSN Indicator (SSNI) 1 20 21 Global Title Indicator (GTI) 4 (01002) 22 23 Routing Indicator (RI) 0 24 25 Reserved for national use 0 (international use) or 1 26 (national use)1 27 28 Subsystem Include applicable value if 29 Number known or zero 30 31 Global Title Translation Type 0 32 33 Encoding Scheme 1=odd number of digits, 2=even 34 Numbering Plan 6 (0110 ) 35 2 36 Nature of address indicator 4 (0000100 ) 37 2 38 Address Information E.212 IMSI or other E.212 39 40 formatted address 41 42 43 44 45 46 47 48 49 50 51 52 1 53 The national/international indicator is intended to indicate the “format” of the encoding and not 54 the national or international nature of the type of address. A national/international indicator = 0 55 means that both the address indicator and the address are encoded according to international 56 specifications. A national/international indicator = 1 means that both the address indicator and 57 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 1 International Mobile Station Identifier (IMSI) can be used for communication 2 with the HLR. Global Title Indicator type 4 (0100) is used. The following figure 3 represents the Global title format for indicator 0100: 4 5 8 7 6 5 4 3 2 1 6 7 Translation type Octet 1 8 Numbering plan Encoding scheme Octet 2 9 10 Spare Nature of address indicator Octet 3 11 Address information Octet 4 12 and further 13 14 15 1 The global title address information field contains the 10-digit MIN . 16 17 The encoding scheme is 1 for an uneven number of BCD Digits, and 2 for 18 an even number of BCD Digits. 19 20 The Nature of Address is 3 for National Significant Number and 4 for 21 International Number. 22 Each address signal is coded as described the ITU Q.713 specification. 23 24 Translation Type assignment is left to mutual agreements. 25 26 Numbering Plan for Global Titles based on MIN is left to mutual 27 agreements. 28 29 • Global Title Translation on Mobile Identification Number or International 30 Mobile Station Identity can be used for communication with a Message Center 31 based on mutual agreement. 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 1 52 Dialed digits must be converted to a 10-digit MIN for the Location Request Task and Call Data 53 Request Task when Global Title Translation communication with the HLR is used. 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 • Global Title Translation on Mobile Directory Number can be used for routing 2 messages to an HLR connected to the same or different national signaling levels: 3 4 5 Table 5.3.2b ITU-T SS7 – E.164 Global Title 6 Field Sub-field Value 7 8 Address Indicator Point Code Indicator (PCI) 0 or 1 9 10 SSN Indicator (SSNI) 1 11 12 Global Title Indicator (GTI) 4 (01002) 13 14 Routing Indicator (RI) 0 15 16 Reserved for national use 0 (international use) or 1 17 (national use)1 18 19 Subsystem Include applicable value if 20 Number known or zero 21 22 Global Title Translation Type 0 23 24 Encoding Scheme 1=odd number of digits, 2=even 25 26 Numbering Plan 1 (00012) 27 28 Nature of address indicator 4 (00001002) 29 30 Address Information E.164 Mobile directory number 31 32 33 • Use of signaling point codes, global titles, and subsystem numbers must meet 34 ITU Q.713 requirements; such that, any allowable combination of these 35 addressing elements is supported. For example, as stated in ITU Q.713: 36 “The address consists of one or any combination of the following elements: 37 38 1) signaling point code, 39 40 2) subsystem number, 41 3) global title (MIN-to-HLR for TIA/EIA-41).” 42 43 • When an originating functional entity sends an SS7 message within a national 44 SS7 signaling network with a global title in the SCCP called party address field, 45 the SCCP calling party address field should include the point code and 46 subsystem number of the originating network entity. 47 48 • When an originating functional entity sends an SS7 message across a national 49 SS7 signaling network boundary, the SCCP calling party address field should 50 include an E.212 global title address identifying the originating functional entity 51 52 1 53 The national/international indicator is intended to indicate the “format” of the encoding and not 54 the national or international nature of the type of address. A national/international indicator = 0 55 means that both the address indicator and the address are encoded according to international 56 specifications. A national/international indicator = 1 means that both the address indicator and 57 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 1 REJECT) to be routed back to the originating node. 2 3 • Replies to messages shall use the received Calling Party Address as the Called 4 Party Address. (As exceptions, if the PC_SSN parameter is received in an 5 AuthenticationRequest INVOKE or in a RegistrationNotification INVOKE, the 6 address used for the response may be derived from the received PC_SSN 7 parameter provided the INVOKE was received from a functional entity within 8 the same national SS7 signaling network.) 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 (TIA/EIA-41-D Chapter 5, page 5-34) 4 The AuthenticationRequest operation is used to request authentication of an 5 6 authentication-capable MS. 7 The AuthenticationRequest operation is initiated with a TCAP INVOKE (LAST). This is 8 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 12 Table 17 AuthenticationRequest INVOKE Parameters 13 AuthenticationRequest INVOKE Parameters Timer: ART 14 15 Field Value Type Reference Notes 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 18 Length variable octets M 6.3.2.1 19 Contents 20 21 ElectronicSerialNumber M 6.5.2.63 22 MobileIdentificationNumber M 6.5.2.81 23 MSCID (Serving MSC) M 6.5.2.82 24 25 SystemAccessType M 6.5.2.145 26 SystemCapabilities (Serving) M 6.5.2.146 27 AuthenticationData O 6.5.2.9 a 28 29 AuthenticationResponse O 6.5.2.10 b 30 CallHistoryCount O 6.5.2.18 b 31 ConfidentialityModes (Actual) O 6.5.2.50 c 32 33 Digits (Dialed) O 6.5.2.58 d 34 PC_SSN (Serving MSC or VLR or HLR) O 6.5.2.93 e 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 Notes: 41 42 a. Include if the SystemAccessType value is Call Origination and if the air 43 interface encoding of dialed digits is not TBCD. 44 45 b. Include if the SystemAccessType value is Call Origination, Page Response, or 46 Registration and the authentication parameters were requested (AUTH=1 in the 47 Overhead Message Train) on the system access. 48 49 c. Include if the SystemAccessType value is Flash Request and if the 50 SignalingMessageEncryptionKey parameter was provided to the Serving MSC. 51 d. Include if the SystemAccessType value is Call Origination or Flash Request. 52 53 e. Include to override lower layer addressing if the receiving VLR, HLR, or AC is 54 known to be in the same national SS7 network. If included, it identifies the 55 functional entity sending the message. 56 57 f. Include to identify the functional entity sending the message. 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 This operation was named RemoteFeatureControlRequest prior to this revision of the 6 Interim Standard. 7 8 9 The FeatureRequest operation is used to request feature-related treatment on behalf of a 10 registered MS. 11 12 The FeatureRequest operation is initiated with a TCAP INVOKE (LAST). This is carried 13 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 14 follows: 15 16 Table 35 FeatureRequest INVOKE Parameters 17 18 FeatureRequest INVOKE Parameters Timer: FRRT 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 6.3.2.1 22 Length variable octets M 6.3.2.1 23 24 Contents 25 Digits (Dialed) M 6.5.2.58 26 ElectronicSerialNumber M 6.5.2.63 27 28 MobileIdentificationNumber M 6.5.2.81 29 BillingID (Originating) O 6.5.2.16 a 30 CallingPartyNumberDigits1 O 6.5.2.21 b, k 31 32 CallingPartyNumberDigits2 O 6.5.2.22 b, k 33 CallingPartySubaddress O 6.5.2.25 b 34 ConferenceCallingIndicator O 6.5.2.49 c 35 36 MobileDirectoryNumber O 6.5.2.80 d 37 MSCID (Serving) O 6.5.2.82 e 38 MSCIdentificationNumber O 6.5.2.83 b j 39 40 OneTimeFeatureIndicator O 6.5.2.88 f 41 PC_SSN O 6.5.2.93 g 42 43 SenderIdentificationNumber O 6.5.2.116 h 44 TransactionCapability O 6.5.2.160 i 45 46 Notes: 47 48 a. Include for recording purposes or for call correlation (see DMH). 49 b. Include if applicable. 50 51 c. Include to indicate the number of conferees already in the call. 52 53 d. Include if available for recording purposes (see DMH). 54 55 e. Include to identify the Anchor MSC. (This may become the Originating MSC for 56 subsequent call redirection.) 57 58 f. Include if any OneTimeFeatureIndicator parameter status bits are set (i.e., have 59 value of 1). 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. 1 2 h. Include if different from the MSCIdentificationNumber to identify the functional 3 entity sending the message. 4 5 i. Include on IS-41-C or later. 6 7 j. Include on N.S0016-0 or later to identify the MSC sending the message. Do not 8 include if N.S0016-0 is not supported by this entity. 9 10 k. Send only the National (Significant) Number (with Nature of Number set to 11 National) if the E.164 country code of the caller’s number matches the E.164 12 country code used for numbers from the MSC’s Country’s numbering plan. 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 The FeatureRequest operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 3 as follows: 4 5 6 Table 36 FeatureRequest RETURN RESULT Parameters 7 FeatureRequest RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 12 Length variable octets M 6.3.2.2 13 Contents 14 FeatureResult M 6.5.2.67 15 16 AccessDeniedReason O 6.5.2.1 a 17 ActionCode O 6.5.2.2 b 18 AnnouncementList O 6.5.2.6 c 19 20 CallingPartyNumberString1 O 6.5.2.23 d 21 CallingPartyNumberString2 O 6.5.2.24 d 22 23 CallingPartySubaddress O 6.5.2.25 d 24 CarrierDigits O 6.5.2.28 d 25 ConferenceCallingIndicator O 6.5.2.49 e 26 27 Digits (Dialed) O 6.5.2.58 f 28 DMH_AccountCodeDigits O 6.5.2.59 g 29 DMH_AlternateBillingDigits O 6.5.2.60 g 30 31 DMH_BillingDigits O 6.5.2.61 g 32 DMH_RedirectionIndicator O 6.5.2.62 d 33 GroupInformation O 6.5.2.69 h 34 35 MobileDirectoryNumber O 6.5.2.80 g 36 NoAnswerTime O 6.5.2.87 d 37 OneTimeFeatureIndicator O 6.5.2.88 i 38 39 PACAIndicator O 6.5.2.91 j 40 PilotNumber O 6.5.2.95 h 41 42 RedirectingNumberDigits O 6.5.2.107 d 43 RedirectingNumberString O 6.5.2.108 d 44 RedirectingSubaddress O 6.5.2.109 d 45 46 RoutingDigits O 6.5.2.114 d 47 TerminationList O 6.5.2.156 k 48 TerminationTriggers O 6.5.2.159 d 49 50 51 Notes: 52 a. Include if access is denied. If included, no other optional parameters shall be 53 included (with the exception of the AnnouncementList parameter). 54 55 b. Include if action to be performed is not implied through presence of other 56 parameters. 57 58 c. Include if provision of one or more tones or announcements is required. 59 60

TIA/EIA-41-D Chapter 5 Modifications 21 Stage-3 Signaling Protocol N.S0016-0 v 1.0

d. Include if applicable. 1 2 e. Include to direct that ongoing call be transformed into a Conference Call. 3 4 f. Include if digits remain to be analyzed by the MSC. Encode the Digits (Dialed) 5 as International if: 6 7 • The digits being returned are the result of a stored translation of the 8 termination address into a destination address (e.g., the expansion of an 9 abbreviated dialing string), and 10 11 • the Serving MSC is known to be capable of accepting digits in International 12 format (e.g., the MSCIdentificationNumber parameter was received). 13 14 g. Include if applicable and for recording purposes (see DMH). 15 h. Include for multileg calls. 16 17 i. Include if modification to normal feature processing is required for call in 18 progress. 19 20 j. Include to indicate PACA priority level. 21 22 k. Include if call routing is required. 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 InterSystemPage INVOKE Parameters 9 10 InterSystemPage INVOKE Parameters Timer: ISPRT 11 Field Value Type Reference Notes 12 13 Identifier SET [NATIONAL 18] M 6.3.2.1 14 Length variable octets M 6.3.2.1 15 16 Contents 17 BillingID (Originating) M 6.5.2.16 18 ElectronicSerialNumber M 6.5.2.63 19 20 MobileIdentificationNumber M 6.5.2.81 21 DMH_AccountCodeDigits O 6.5.2.59 a 22 AlertCode O 6.5.2.3 a 23 24 CallingPartyNumberString1 O 6.5.2.23 a 25 CallingPartyNumberString2 O 6.5.2.24 a 26 27 CallingPartySubaddress O 6.5.2.25 a 28 CDMASlotCycleIndex O 6.5.2.40 b 29 CDMAStationClassMark O 6.5.2.41 c 30 31 DMH_AlternateBillingDigits O 6.5.2.60 a 32 DMH_BillingDigits O 6.5.2.61 a 33 ExtendedMSCID (Serving MSC) O 6.5.2.64 d 34 35 ExtendedSystemMyTypeCode (Serving MSC) O 6.5.2.65 e 36 LegInformation O 6.5.2.75 f 37 LocationAreaID O 6.5.2.77 f 38 39 MobileDirectoryNumber O 6.5.2.80 a 40 MSCID (Originating MSC) O 6.5.2.82 g 41 MSCIdentificationNumber (Originating MSC) O 6.5.2.83 f n 42 43 OneTimeFeatureIndicator O 6.5.2.88 f 44 PageIndicator O 6.5.2.92 h 45 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 49 50 RedirectingNumberString O 6.5.2.108 a 51 RedirectingSubaddress O 6.5.2.109 a 52 SenderIdentificationNumber (Serving MSC) O 6.5.2.116 f m 53 54 SystemMyTypeCode (Originating MSC) O 6.5.2.147 l 55 TerminationTreatment O 6.5.2.158 f 56 TerminationTriggers O 6.5.2.159 a 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 4 b. Included when the Serving MSC knows that the MS is operating in CDMA 5 Slotted Mode. 6 7 c. Include if a CDMA channel is in use. 8 9 d. Include to identify serving system. 10 11 e. Include to identify serving system manufacturer. 12 f. Include if known. 13 14 g. Include to identify originating system. 15 16 h. Include if request is to listen only. May include if request is to page. 17 18 i. Include if available for subsequent call redirection. 19 20 j. Include if appropriate. 21 k. Include on a multileg call. 22 23 l. Include to identify originating system manufacturer. 24 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 28 N.S0016-0 is not supported by this entity. 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 The InterSystemPage operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 3 as follows: 4 5 6 Table 58 InterSystemPage RETURN RESULT Parameters 7 InterSystemPage RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 12 Length variable octets M 6.3.2.2 13 Contents 14 AccessDeniedReason O 6.5.2.1 a 15 16 BillingID (Terminating) O 6.5.2.16 b, c 17 ConditionallyDeniedReason O 6.5.2.48 d 18 Digits (Destination) O 6.5.2.58 c 19 20 ExtendedMSCID (Border MSC) O 6.5.2.64 c 21 ExtendedSystemMyTypeCode (Border MSC) O 6.5.2.65 c 22 23 MSCIdentificationNumber O 6.5.2.83 e 24 PC_SSN (Border MSC) O 6.5.2.93 f 25 26 Notes: 27 28 a. Include if access may be denied. 29 b. Required for recording purposes (see DMH). 30 31 c. If one parameter is present, they all must be present. 32 33 d. Include if Call Waiting is possible. 34 35 e. Include to identify the Border MSC. 36 f. Include if Digits (Destination) parameter is provided, and SS7 is used. Include if 37 38 Digits (Destination) parameter is provided, SS7 is used, and the Originating 39 MSC and the Border MSC may be in the same national SS7 network. 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) 3 4 The LocationRequest operation is used by an Originating MSC to obtain call treatment 5 instructions from the HLR. The call is identified by the dialed MS address digits received 6 by the Originating MSC. 7 8 The LocationRequest operation is initiated with a TCAP INVOKE (LAST). This is 9 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 10 encoded as follows: 11 12 Table 63 LocationRequest INVOKE Parameters 13 14 LocationRequest INVOKE Parameters Timer: LRT 15 Field Value Type Reference Notes 16 17 Identifier SET [NATIONAL 18] M 6.3.2.1 18 Length variable octets M 6.3.2.1 19 Contents 20 21 BillingID (Originating) M 6.5.2.16 22 Digits (Dialed) M 6.5.2.58 23 24 MSCID (Originating) M 6.5.2.82 25 SystemMyTypeCode (Originating) M 6.5.2.147 26 CallingPartyNumberDigits1 O 6.5.2.21 a, f 27 28 CallingPartyNumberDigits2 O 6.5.2.22 a, f 29 CallingPartySubaddress O 6.5.2.25 a 30 MSCIdentificationNumber O 6.5.2.83 b 31 32 PC_SSN (Originating) O 6.5.2.93 c 33 RedirectingNumberDigits O 6.5.2.107 a 34 RedirectingSubaddress O 6.5.2.109 a 35 36 TerminationAccessType O 6.5.2.155 d 37 TransactionCapability O 6.5.2.160 e 38 39 Notes: 40 41 a. Include if available (i.e., provided in call origination). 42 43 b. Include on N.S0016-0 or later to identify the MSC sending the message. Do not 44 include if N.S0016-0 is not supported by this entity. 45 c. Include if SS7 may be used for subsequent call redirection. 46 47 d. Include if call involves a special access situation (e.g., Roamer port access). 48 49 e. Include on IS-41-C or later. 50 51 f. Send only the National (Significant) Number (with Nature of Number set to 52 National) if the E.164 country code of the caller’s number matches the E.164 53 country code used for numbers from the MSC’s Country’s numbering plan. This 54 consideration only applies for MS to MS calls recognized as such by the MSC 55 serving the calling MS. 56 57 58 59 60

Stage-3 Signaling Protocol 26 TIA/EIA-41-D Chapter 5 Modifications N.S0016-0 v 1.0

1 The LocationRequest operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 3 as follows: 4 5 6 Table 64 LocationRequest RETURN RESULT Parameters 7 LocationRequest RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 12 Length variable octets M 6.3.2.2 13 Contents 14 ElectronicSerialNumber M 6.5.2.63 a 15 16 MobileIdentificationNumber M 6.5.2.81 a 17 MSCID (Serving MSC) M 6.5.2.82 b 18 AccessDeniedReason O 6.5.2.1 c 19 20 AnnouncementList O 6.5.2.6 d 21 CallingPartyNumberString1 O 6.5.2.23 e 22 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 26 27 DMH_AccountCodeDigits O 6.5.2.59 i 28 DMH_AlternateBillingDigits O 6.5.2.60 i 29 DMH_BillingDigits O 6.5.2.61 i 30 31 DMH_RedirectionIndicator O 6.5.2.62 j 32 GroupInformation O 6.5.2.69 k 33 MobileDirectoryNumber O 6.5.2.80 i 34 35 NoAnswerTime O 6.5.2.87 l 36 OneTimeFeatureIndicator O 6.5.2.88 m 37 PC_SSN (Serving MSC or VLR) O 6.5.2.93 n 38 39 RedirectingNumberDigits O 6.5.2.107 j 40 RedirectingNumberString O 6.5.2.108 f 41 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 45 46 TerminationTriggers O 6.5.2.159 f 47 48 Notes: 49 a. Value is all zeroes, if unknown. 50 51 b. Value is MSCID (Originating), if access is denied or routing to a directory 52 number. 53 54 c. Include if access may be denied. 55 56 d. Include if one or more tones or announcements is to be applied to the MS. 57 e. Include if feature is active and if a LocalTermination parameter is included 58 59 within the TerminationList parameter. 60

TIA/EIA-41-D Chapter 5 Modifications 27 Stage-3 Signaling Protocol N.S0016-0 v 1.0

f. Include if applicable. 1 2 g. Include if call is to be routed over a network. 3 4 h. Use only with system not capable of using the TerminationList parameter. 5 6 i. Include if available for recording purposes (see DMH). 7 j. Include if available and call redirection may apply. 8 9 k. Include for multileg calls. 10 11 l. Include to request an override of the Originating MSC’s default No Answer Time 12 value. 13 14 m. Include if modification to normal feature processing is required for a call in 15 progress. 16 17 n. Use is for further study. 18 19 o. Include if call routing is required. 20 p. For N.S0016-0 or later, encode the Digits (Destination) as International if it is 21 known that the Originating MSC can accept the digits in this format (e.g., the 22 MSCIdentificationNumber parameter was received in the INVOKE) and an HLR 23 24 stored number is being provided. 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 (TIA/EIA-41-D Chapter 5, page 5-81) 4 The OriginationRequest operation is used to request call origination treatment on behalf 5 6 of a registered MS. 7 The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is 8 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 12 Table 68 OriginationRequest INVOKE Parameters 13 OriginationRequest INVOKE Parameters Timer: ORT 14 15 Field Value Type Reference Notes 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 18 Length variable octets M 6.3.2.1 19 Contents 20 21 BillingID (originating) M 6.5.2.16 22 Digits (Dialed) M 6.5.2.58 23 ElectronicSerialNumber M 6.5.2.63 24 25 MobileIdentificationNumber M 6.5.2.81 26 MSCID (Originating MSC) M 6.5.2.82 27 OriginationTriggers M 6.5.2.90 28 29 TransactionCapability M 6.5.2.160 30 CallingPartyNumberDigits1 O 6.5.2.21 a, g 31 CallingPartyNumberDigits2 O 6.5.2.22 a, g 32 33 CallingPartySubaddress O 6.5.2.25 a 34 MobileDirectoryNumber O 6.5.2.80 b 35 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 39 40 SenderIdentificationNumber O 6.5.2.116 f 41 42 Notes: 43 a. Include if applicable. 44 45 b. Include if available for recording purposes (see DMH). 46 47 c. Include on N.S0016-0 or later to identify the MSC initiating the message. Do not 48 include if N.S0016-0 is not supported by this entity. 49 50 d. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 51 e. Include if SS7 may be used for subsequent call redirection. 52 53 f. Include to identify intermediate message sender if different from the 54 MSCIdentificationNumber to identify the functional entity sending the message. 55 56 g. Send only the National (Significant) Number (with Nature of Number set to 57 National) if the E.164 country code of the caller’s number matches the E.164 58 country code used for numbers from the MSC’s Country’s numbering plan. 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 1 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 2 as follows: 3 4 5 Table 69 OriginationRequest RETURN RESULT Parameters 6 OriginationRequest RETURN RESULT Parameters 7 8 Field Value Type Reference Notes 9 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 Length variable octets M 6.3.2.2 12 Contents 13 14 AccessDeniedReason O 6.5.2.1 a 15 ActionCode O 6.5.2.2 b 16 AnnouncementList O 6.5.2.6 c 17 18 CallingPartyNumberString1 O 6.5.2.23 d, e 19 CallingPartyNumberString2 O 6.5.2.24 d, e 20 CallingPartySubaddress O 6.5.2.25 d, e, f 21 22 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 26 DMH_AlternateBillingDigits O 6.5.2.60 i 27 DMH_BillingDigits O 6.5.2.61 i 28 29 DMH_RedirectionIndicator O 6.5.2.62 i, j 30 GroupInformation O 6.5.2.69 k 31 MobileDirectoryNumber O 6.5.2.80 i 32 33 NoAnswerTime O 6.5.2.87 l 34 OneTimeFeatureIndicator O 6.5.2.88 m 35 PilotNumber O 6.5.2.95 k 36 37 RedirectingNumberDigits O 6.5.2.107 f 38 RedirectingNumberString O 6.5.2.108 d 39 RedirectingSubaddress O 6.5.2.109 d, e 40 41 RoutingDigits O 6.5.2.114 g 42 TerminationList O 6.5.2.156 n 43 TerminationTriggers O 6.5.2.57 o 44 45 46 Notes: 47 a. Include if access is denied. If included, no other optional parameters shall be 48 included (with the exception of the AnnouncementList parameter). 49 50 b. Include if action to be performed is not implied through presence of other 51 parameters. 52 53 c. Include if one or more tones or announcements are to be applied to the MS. 54 55 d. Include if a LocalTermination parameter is included in the TerminationList 56 parameter. 57 e. Include if the related feature is active. 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 2 parameter is included within the TerminationList parameter. 3 4 g. Include if applicable. 5 6 h. Include if digits remain to be translated by the MSC. Encode the Digits (Dialed) 7 as International if: 8 9 • The digits being returned are the result of a stored translation of the 10 termination address into a destination address (e.g., the expansion of an 11 abbreviated dialing string),and 12 13 • the Serving MSC is known to be capable of accepting digits in International 14 format (e.g., the MSCIdentificationNumber parameter was received). 15 i. Include if available for recording purposes (see DMH). 16 17 j. Include if redirection may apply. 18 19 k. Include for multileg calls. 20 21 l. Include to request an override of the Serving MSC’s default No Answer Time 22 value. 23 24 m. Include if modification to normal feature processing is required for the call in 25 progress. 26 27 n. Include if call routing is required. 28 o. Include to indicate processing in the Originating MSC for failed call attempts. 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 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) 3 4 The QualificationDirective operation is used to update the authorization information, 5 profile information, or both, previously obtained for an MS. 6 The QualificationDirective operation is initiated with a TCAP INVOKE (LAST). This is 7 8 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 Table 70 QualificationDirective INVOKE Parameters 12 13 QualificationDirective INVOKE Parameters Timer: QDT 14 Field Value Type Reference Notes 15 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 Length variable octets M 6.3.2.1 18 Contents 19 20 ElectronicSerialNumber M 6.5.2.63 21 MobileIdentificationNumber M 6.5.2.81 22 QualificationInformationCode M 6.5.2.99 23 24 SystemMyTypeCode (HLR or VLR) M 6.5.2.147 25 AuthorizationDenied O 6.5.2.13 a 26 27 AuthorizationPeriod O 6.5.2.14 b 28 DeniedAuthorizationPeriod O 6.5.2.53 c 29 Digits (Carrier) O 6.5.2.58 d, e 30 31 Digits (Destination) O 6.5.2.58 d, f, j 32 LocationAreaID O 6.5.2.77 g 33 Profile **Macro** O 6.5.2.97 h, k 34 35 SenderIdentificationNumber O 6.5.2.116 i 36 37 Notes: 38 a. If included, no other optional parameters except the DeniedAuthorizationPeriod 39 parameter shall be present. 40 41 b. Include if validation is being updated. 42 43 c. May be included if the AuthorizationDenied parameter is present to indicate the 44 interval before re-authorization may be attempted. 45 46 d. Use only on systems not capable of supporting the TransactionCapability 47 parameter. 48 49 e. Include if profile is being updated and preferred carrier is applicable. 50 f. Include if profile is being updated and originations are restricted (e.g., set to 51 NPA-NXX to restrict originations to a 6-digit NANP office code or set to 52 53 NPA-NXX-XXXX to restrict originations to a single NANP directory number). 54 g. May be included from VLR to MSC-V. Usage from the HLR is not defined. 55 56 h. Include applicable parameter(s) (see 6.5.2.97). 57 58 i. Include to identify the functional entity sending the message. 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 2 known that the Serving MSC can accept the digits in this format (e.g., the 3 MSCIdentificationNumber parameter was received during registration). 4 5 k. For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and 6 RestrictionDigits parameters should be encoded as International when loaded 7 into the profile if it is known that the Serving MSC can accept them in this 8 format (e.g., the MSCIdentificationNumber parameter was received during 9 registration). 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) 3 4 The QualificationRequest operation is used (a) to request validation of an MS, (b) to 5 request an MS’s profile information, or (c) both. 6 The QualificationRequest operation is initiated with a TCAP INVOKE (LAST). This is 7 8 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 Table 72 QualificationRequest INVOKE Parameters 12 13 QualificationRequest INVOKE Parameters Timer: QRT 14 Field Value Type Reference Notes 15 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 Length variable octets M 6.3.2.1 18 Contents 19 20 ElectronicSerialNumber M 6.5.2.63 21 MobileIdentificationNumber M 6.5.2.81 22 QualificationInformationCode M 6.5.2.99 23 24 SystemMyTypeCode (MSC or VLR) M 6.5.2.147 25 MSCID (Serving MSC or Originating MSC) O 6.5.2.82 a 26 27 MSCIdentificationNumber O 6.5.2.83 c 28 SenderIdentificationNumber O 6.5.2.116 b 29 SystemAccessType O 6.5.2.145 a 30 31 TransactionCapability O 6.5.2.160 a 32 33 Notes: 34 a. Should be included on IS-41-C or later. 35 36 b. Include to identify the functional entity sending the message. 37 38 c. Include on N.S0016-0 or later to identify the MSC sending the message. Do not 39 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

Stage-3 Signaling Protocol 34 TIA/EIA-41-D Chapter 5 Modifications N.S0016-0 v 1.0

1 The QualificationRequest operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 3 as follows: 4 5 6 Table 73 QualificationRequest RETURN RESULT Parameters 7 QualificationRequest RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 12 Length variable octets M 6.3.2.2 13 Contents 14 SystemMyTypeCode (VLR or HLR) M 6.5.2.147 15 16 AuthorizationDenied O 6.5.2.13 a 17 AuthorizationPeriod O 6.5.2.14 b 18 DeniedAuthorizationPeriod O 6.5.2.53 c 19 20 Digits (Carrier) O 6.5.2.58 d 21 Digits (Destination) O 6.5.2.58 e, h 22 23 MSCID (HLR) O 6.5.2.82 f 24 Profile **Macro** O 6.5.2.97 g, i 25 26 Notes: 27 28 a. If included, no other optional parameters except the DeniedAuthorizationPeriod 29 parameter shall be present. 30 b. Include if validation requested. 31 32 c. May be included if the AuthorizationDenied parameter is present to indicate the 33 interval before re-authorization may be attempted. 34 35 d. Include if profile requested and preferred carrier is applicable and 36 TransactionCapability parameter is not received. 37 38 e. Include if profile requested and originations are restricted to NPA-NXX or 39 NPA-NXX-XXXX and TransactionCapability parameter is not received. 40 41 f. Include on IS-41-C and later and authorization is not denied. 42 43 g. Include applicable parameter(s) (see 6.5.2.97). 44 h. For N.S0016-0 or later, encode the Digits (Destination) as International if it is 45 known that the Serving MSC can accept the digits in this format (e.g., the 46 MSCIdentificationNumber parameter was received in the INVOKE). 47 48 i. For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and 49 RestrictionDigits parameters should be encoded as International when loaded 50 into the profile if it is known that the Serving MSC can accept them in this 51 format (e.g., the MSCIdentificationNumber parameter was received in the 52 53 INVOKE). 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) 3 4 The RedirectionDirective operation is used during feature processing to direct the MSC to 5 forward the indicated call. 6 The RedirectionDirective operation is initiated with a TCAP INVOKE (LAST). This is 7 8 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 Table 76 RedirectionDirective INVOKE Parameters 12 13 RedirectionDirective INVOKE Parameters Timer: RDT 14 Field Value Type Reference Notes 15 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 Length variable octets M 6.3.2.1 18 Contents 19 20 BillingID (Originating) M 6.5.2.16 21 Digits (Destination) M 6.5.2.58 22 ElectronicSerialNumber M 6.5.2.63 23 24 MobileIdentificationNumber M 6.5.2.81 25 SystemMyTypeCode (MSC) M 6.5.2.147 26 27 Digits (Carrier) O 6.5.2.58 a 28 DMH_AccountCodeDigits O 6.5.2.59 b 29 DMH_AlternateBillingDigits O 6.5.2.60 b 30 31 DMH_BillingDigits O 6.5.2.61 b 32 MSCIdentificationNumber O 6.5.2.83 c 33 RedirectingNumberString O 6.5.2.108 d 34 35 RedirectingSubaddress O 6.5.2.109 d 36 SenderIdentificationNumber O 6.5.2.116 e 37 38 Notes: 39 40 a. Include if applicable. 41 b. Include if available for recording purposes (see DMH). 42 43 c. Include on N.S0016-0 or later to identify the initiati MSCng initiating the message. 44 Do not include if N.S0016-0 is not supported by this entity. 45 46 d. Optionally, include to override normal Originating MSC redirection number 47 treatment. 48 49 e. Include if the sending functional entity’s identification number is not equal to the 50 initiating MSC’s identification number if different from the 51 MSCIdentificationNumber to identify the functional entity sending the message. 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 (TIA/EIA-41-D Chapter 5, page 5-94) 4 The RegistrationNotification operation is used to report the location of an MS and, 5 6 optionally, to (a) validate the MS or (b) validate the MS and obtain its profile 7 information. 8 The RegistrationNotification operation is initiated with a TCAP INVOKE (LAST). This 9 is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 10 11 encoded as follows: 12 13 Table 82 RegistrationNotification INVOKE Parameters 14 RegistrationNotification INVOKE Parameters Timer: RNT 15 16 Field Value 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 24 MSCID (Serving MSC) M 6.5.2.82 25 26 QualificationInformationCode M 6.5.2.99 27 SystemMyTypeCode (Serving MSC or VLR) M 6.5.2.147 28 AvailabilityType O 6.5.2.15 a 29 30 BorderCellAccess O 6.5.2.17 b 31 ControlChannelData O 6.5.2.51 b 32 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 36 37 PC_SSN (Serving MSC or VLR) O 6.5.2.93 e 38 ReceivedSignalQuality O 6.5.2.106 b 39 ReportType O 6.5.2.112 f 40 41 SenderIdentificationNumber O 6.5.2.116 g 42 SMS_Address O 6.5.2.123 h 43 SMS_MessageWaitingIndicator O 6.5.2.129 i 44 45 SystemAccessData O 6.5.2.144 b 46 SystemAccessType O 6.5.2.145 j 47 SystemCapabilities O 6.5.2.146 k 48 49 TerminalType O 6.5.2.154 j 50 TransactionCapability O 6.5.2.160 j 51 52 Notes: 53 54 a. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode 55 or sleep mode). 56 57 b. Include if access occurred in a border cell (based on internal algorithms). 58 c. Included by VLR if its MSCID is different than the MSC’s MSCID. 59 60

TIA/EIA-41-D Chapter 5 Modifications 37 Stage-3 Signaling Protocol N.S0016-0 v 1.0

d. May be included from MSC to VLR. 1 2 e. Include to override lower layer addressing if the receiving VLR or HLR is 3 known to be in the same national SS7 network. 4 5 f. Include if authentication parameters were requested by the Serving MSC 6 (AUTH=1 in the Overhead Message Train) but were not received from the MS 7 for the system access. 8 9 g. Include to identify message sender. 10 11 h. Include to indicate that the Serving MSC supports Short Message Service. 12 i. Include if the MS was previously registered with this VLR, the MS is registering 13 14 to a new serving MSC that does not support SMS, and an SMS message is 15 pending delivery in the previous serving system. This is only used between a 16 VLR and an HLR. 17 j. Include on IS-41-C and later. 18 19 k. Include if the system is authentication capable (including voice channel 20 authentication only systems where all flags are zero). 21 22 l. Include on N.S0016-0 or later to identify the MSC sending the message. Do not 23 include if N.S0016-0 is not supported by this entity. 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 The RegistrationNotification operation success is reported with a TCAP RETURN 2 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is 3 encoded as follows: 4 5 6 Table 83 RegistrationNotification RETURN RESULT Parameters 7 RegistrationNotification RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 12 Length variable octets M 6.3.2.2 13 Contents 14 SystemMyTypeCode (VLR or HLR) M 6.5.2.147 15 16 AuthorizationDenied O 6.5.2.13 a 17 AuthorizationPeriod O 6.5.2.14 b 18 ControlChannelData O 6.5.2.51 c 19 20 DeniedAuthorizationPeriod O 6.5.2.53 d 21 Digits (Carrier) O 6.5.2.58 e 22 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 26 27 ReceivedSignalQuality O 6.5.2.106 c 28 SenderIdentificationNumber O 6.5.2.116 i 29 SMS_MessageWaitingIndicator O 6.5.2.129 j 30 31 SystemAccessData O 6.5.2.144 c 32 33 Notes: 34 a. If included, only the ControlChannelData, DeniedAuthorizationPeriod, 35 ReceivedSignalQuality, and SystemAccessData optional parameters have 36 significance. 37 38 b. Include if validation requested. 39 40 c. Include if AuthorizationDenied parameter is included with value of Multiple 41 Access. 42 43 d. May be included if the AuthorizationDenied parameter is present to indicate the 44 interval before re-authorization may be attempted. 45 46 e. Include if the profile is requested, the preferred carrier is applicable, and the 47 CarrierDigits parameter is not included in the Profile macro. 48 49 f. Include if the profile is requested, originations are restricted to NPA-NXX or 50 NPA-NXX-XXXX, and the RestrictionDigits parameter is not included in the 51 Profile macro. 52 53 g. Include on IS-41-C and later and authorization is not denied. 54 h. Include applicable parameter(s) (see 6.5.2.97). 55 56 i. Include to identify the functional entity sending the message. 57 58 j. Include to indicate that an SMS message is pending delivery. 59 60

TIA/EIA-41-D Chapter 5 Modifications 39 Stage-3 Signaling Protocol N.S0016-0 v 1.0

k. For N.S0016-0 or later, encode the Digits (Destination) as International if it is 1 known that the Serving MSC can accept the digits in this format (e.g., the 2 MSCIdentificationNumber parameter was received in the INVOKE). 3 4 l. For N.S0016-0 or later, the DMH_BillingDigits, MobileDirectoryNumber and 5 RestrictionDigits parameters should be encoded as International when loaded 6 into the profile if it is known that the Serving MSC can accept them in this 7 format (e.g., the MSCIdentificationNumber parameter was received in the 8 INVOKE). 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 (TIA/EIA-41-D Chapter 5, page 5-110) 4 The TransferToNumberRequest operation is used during feature processing to obtain an 5 6 MS’s forward-to number from the HLR. 7 The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST). 8 This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 9 encoded as follows: 10 11 12 Table 100 TransferToNumberRequest INVOKE Parameters 13 TransferToNumberRequest INVOKE Parameters Timer: TTNRT 14 15 Field Value Type Reference Notes 16 Identifier SET [NATIONAL 18] M 6.3.2.1 17 18 Length variable octets M 6.3.2.1 19 Contents 20 21 ElectronicSerialNumber M 6.5.2.63 22 MobileIdentificationNumber M 6.5.2.81 23 RedirectionReason M 6.5.2.110 24 25 SystemMyTypeCode (MSC) M 6.5.2.147 26 BillingID (Originating) O 6.5.2.16 a 27 GroupInformation O 6.5.2.69 b 28 29 LegInformation O 6.5.2.75 c 30 MSCID (Originating) O 6.5.2.82 d 31 MSCIdentificationNumber O 6.5.2.83 e g 32 33 PilotBillingID O 6.5.2.94 f 34 PilotNumber O 6.5.2.95 f 35 36 TransactionCapability O 6.5.2.160 e 37 38 Notes: 39 a. Include to identify the Originating MSC and its BillingID for subsequent call 40 redirection. 41 42 b. Include if available (i.e., if provided in the associated RoutingRequest INVOKE 43 or LocationRequest RETURN RESULT) for the None Reachable termination 44 trigger. 45 46 c. Include if available (i.e., if provided in the associated RoutingRequest INVOKE 47 or LocationRequest RETURN RESULT) for any termination trigger except 48 None Reachable. 49 50 d. Include on TIA/EIA-41 or later. 51 52 e. Include on IS-41-C or later. 53 f. Include if available. 54 55 g. Include on N.S0016-0 or later to identify the MSC initiating the message. Do not 56 include if N.S0016-0 is not supported by this entity. 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 1 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is 2 encoded as follows: 3 4 5 Table 101 TransferToNumberRequest RETURN RESULT Parameters 6 TransferToNumberRequest RETURN RESULT Parameters 7 8 Field Value Type Reference Notes 9 10 Identifier SET [NATIONAL 18] M 6.3.2.2 11 Length variable octets M 6.3.2.2 12 Contents 13 14 Digits (Destination) M 6.5.2.58 a, k 15 AccessDeniedReason O 6.5.2.1 b 16 ActionCode O 6.5.2.2 c 17 18 AnnouncementList O 6.5.2.6 d 19 CallingPartyNumberString1 O 6.5.2.23 e 20 CallingPartyNumberString2 O 6.5.2.24 e 21 22 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 26 DMH_AlternateBillingDigits O 6.5.2.60 h 27 DMH_BillingDigits O 6.5.2.61 h 28 29 DMH_RedirectionIndicator O 6.5.2.62 h 30 GroupInformation O 6.5.2.69 i 31 MobileDirectoryNumber O 6.5.2.80 h 32 33 NoAnswerTime O 6.5.2.87 g 34 RedirectingNumberDigits O 6.5.2.107 f 35 RedirectingNumberString O 6.5.2.108 e 36 37 RedirectingSubaddress O 6.5.2.109 e, f 38 TerminationList O 6.5.2.156 j 39 TerminationTriggers O 6.5.2.159 g 40 41 Notes: 42 43 a. This parameter is ignored if the TerminationList parameter is provided. 44 45 b. Include if access is denied. If included, no other optional parameters shall be 46 included (with the exception of the AnnouncementList). 47 48 c. Include if action to be performed is not implied through presence of other 49 parameters. 50 d. Include if one or more tones or announcements are to be applied to the MS. 51 52 e. Include if related feature is active and if a LocalTermination parameter is 53 included within the TerminationList parameter. 54 55 f. Optionally include if a PSTNTermination parameter or an 56 IntersystemTermination parameter is included within the TerminationList 57 parameter. 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. 2 3 h. Include if available for recording purposes (see DMH). 4 5 i. Include for multileg calls. 6 7 j. Include if call routing is required. 8 k. For N.S0016-0 or later, encode the Digits (Destination) as International if it is 9 known that the requesting MSC can accept the digits in this format (e.g., the 10 MSCIdentificationNumber parameter was received in the INVOKE) and an HLR 11 12 stored number is being provided. 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 8 9 10 Tone (octet 1) 11 Bits H G F E D C B A Value Meaning 12 13 00000000 0 DialTone. A continuous 350 Hz tone added to a 14 440 Hz tone. 15 00000001 1 RingBack or AudibleAlerting. A 440 Hz tone 16 added to a 480 Hz tone repeated in a 2s on 4s off pattern. 17 00000010 2 InterceptTone or MobileReorder. Alternating 18 440 Hz and 620 Hz tones, each on for 250 ms. 19 00000011 3 CongestionTone or ReorderTone. A 480 Hz 20 tone added to a 620 Hz tone repeated in a 250 21 ms on, 250 ms off cycle. 22 00000100 4 BusyTone. A 480 Hz tone added to a 620 Hz 23 tone repeated in a 500 ms on, 500 ms off cycle. 24 00000101 5 ConfirmationTone. A 350 Hz tone added to a 25 440 Hz tone repeated 3 times in a 100 ms on, 26 100 ms off cycle. 27 00000110 6 AnswerTone. Answer tone is not presently used 28 in many North American networks. Answer tone 29 is not presently used in North American 30 networks. 31 32 33 The remainder of this section is retained without modification. 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 (TIA/EIA-41-D Chapter 5, page 5-189) 4 The Digits parameter is based on the Digits parameter defined in Section 3 of ANSI 5 6 T1.114-1988. Where there are differences, this Standard takes precedence. 7 8 Field Value Type Reference Notes 9 Identifier Digits IMPLICIT DigitsType M 6.5.1.2 a 10 Length variable octets M 6.5.1.1 11 12 Contents 13 HGFEDCBAoctetNotes 14 15 Type of Digits 1 b 16 Nature of Number 2 c 17 Numbering Plan Encoding 3 d, e 18 19 Number of Digits 4 f 20 2nd BCD Digit 1st BCD Digit 5 21 4th BCD Digit 3rd BCD Digit 6 22 23 • • • • • • • • • 24 nth BCD Digit n-1st BCD Digit m 25 26 Figure 66 Digits parameter for BCD digits 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 31 encoding. 32 33 d. The Numbering Plan field is set to Telephony Numbering. 34 e. The Encoding field is set to BCD. 35 36 37 38 Notes for the Digits (Dialed) as the dialed number variant: 39 b. The Type of Digits field is set to Dialed Number. The digits are the digits dialed 40 by an MS with an unknown Nature of Number (or Numbering Plan). 41 42 c. The Nature of Number field is National or International ignored on receipt. 43 44 f. The Number of Digits is between 0 and 32. 45 46 47 Notes for the Digits (Dialed) as the called number variant: 48 b. The Type of Digits field is set to Dialed Number. The digits should be a 49 directory number assigned to a MS or for other specialized purposes. 50 51 c. The Nature of Number field is National. 52 53 f. The Number of Digits is set appropriately. 10 for a North American Numbering 54 Plan number, although this may vary by country or by bilateral agreement. 55 56 57 58 59 60

TIA/EIA-41-D Chapter 5 Modifications 45 Stage-3 Signaling Protocol N.S0016-0 v 1.0

Notes for the Digits (Carrier) variant: 1 2 b. The Type of Digits field is set to Carrier. 3 c. The Nature of Number field is National or International. 4 5 6 7 Notes for the Digits (Destination) as a profile restriction variant: 8 b. The Type of Digits field is set to Destination Number. The digits specify a the 9 national leading digits of the directory number (e.g., 6-digit NANP office code) 10 or the leading digits of an international E.164 number or a full directory number 11 (e.g., 10-digit NANP directory number) or a full international E.164 number 12 used to restrict the numbers dialed by an MS as indicated by the 13 OriginationIndicator parameter. 14 15 c. The Nature of Number field is set to National or to International as appropriate. 16 17 f. The Number of Digits is set appropriately (e.g. either 6 or 10 for NANP). 18 19 20 Notes for the Digits (Destination) as a network destination variant: 21 22 b. The Type of Digits field is set to Destination Number. The digits specify a 23 telephone network destination address. 24 25 c. The Nature of Number field is set as necessary: 26 i. for a destination within the same country (or multi-country integrated 27 numbering plan) the digits may consist of a national number without prefix 28 29 digits. The Nature of Number field is set to National. 30 ii. otherwise, the digits should consist of a full E.164 number, including 31 country code. The Nature of Number field is set to International. 32 33 i. from NANP countries to destinations within NANP, the digits should 34 consist of 10 digits without prefix digits. The Nature of Number field is set 35 to National. 36 37 ii. from non NANP countries to destinations within NANP, the Nature of 38 Number field is set to International. 39 40 iii. for destinations within the same country outside of NANP, the digits should 41 consist of a national number without prefix digits. The Nature of Number 42 field is set to National. 43 44 iv. for destinations between countries outside of NANP, the digits shall consist 45 of a country code followed by a national number without prefix digits. The 46 Nature of Number field is set to International. 47 48 v. for destinations between different systems (even within the same country), 49 the digits may consist of a country code followed by a national number 50 without prefix digits. The Nature of Number field is set to International. 51 52 vi. from NANP countries to destinations outside of NANP, the digits may 53 consist of a country code followed by a national number without prefix 54 digits. The Nature of Number field is set to International. 55 56 f. The Number of Digits is between 0 and at least 15. 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 (TIA/EIA-41-D Chapter 5, page 5-208) 4 The LocalTermination (LOCTERM) parameter is used to provide an MSC with routing 5 6 information for calls which are to be terminated on the same MSC. 7 8 Field Value Type Reference Notes 9 Identifier LocalTermination M 6.5.1.2 10 IMPLICIT SET 11 Length variable M 6.5.1.1 12 13 Contents 14 ElectronicSerialNumber M 6.5.2.63 15 MobileIdentificationNumber M 6.5.2.81 16 17 TerminationTreatment M 6.5.2.158 18 AlertCode O 6.5.2.3 a, b 19 CarrierDigits O 6.5.2.28 b, c 20 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 24 OneTimeFeatureIndicator O 6.5.2.88 b, g 25 26 RoutingDigits O 6.5.2.114 b, h 27 TerminationTriggers O 6.5.2.159 a, b 28 VoiceMailboxPIN O 6.5.2.165 i 29 30 VoiceMailboxNumber O 6.5.2.164 j 31 • • • k 32 33 Figure 84 LocalTermination parameter 34 35 Notes: 36 37 a. Optional, if the TerminationTreatment indicates termination to an MS. 38 b. This parameter has precedence for this call leg over the parameters outside the 39 TerminationList parameter or the subscriber’s profile. 40 41 c. Optional, for intra-MSC, inter-LATA preferred carrier call routing. 42 43 d. Optionally include if TerminationTreatment parameter value is Dialogue, to 44 select a dialogue or to provide information to a dialogue. 45 46 e. Optionally include if TerminationTreatment parameter value is 47 VoiceMailRetrieval or VoiceMailStorage to select the voice mail system. 48 49 f. Include to identify the MS if different than MIN for call recording purposes. 50 51 g. Include if modification to normal feature processing is required. 52 h. Optional, for special routing purposes. 53 54 i. Optional, if the TerminationTreatment value is VoiceMailRetrieval or 55 VoiceMailStorage. 56 57 j. Include if the TerminationTreatment value is VoiceMailRetrieval or 58 VoiceMailStorage and the mailbox is not the MIN. 59 60

TIA/EIA-41-D Chapter 5 Modifications 47 Stage-3 Signaling Protocol N.S0016-0 v 1.0

k. Ignore unexpected parameters, if received. 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

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 (TIA/EIA-41-D Chapter 5, page 5-215) 4 The MSCIdentificationNumber (MSCIN) parameter indicates the identification number 5 6 of an MSC sending a message. 7 8 Field Value Type Reference Notes 9 Identifier MSCIdentificationNumber M 6.5.1.2 a 10 IMPLICIT DigitsType 11 Length variable octets M 6.5.1.1 12 13 Contents 14 HGFEDCBAoctetNotes 15 16 Type of Digits 1 b 17 Nature of Number 2 c 18 Numbering Plan Encoding 3 d, e 19 20 Number of Digits 4 f 21 2nd BCD Digit 1st BCD Digit 5 22 th rd 23 4 BCD Digit 3 BCD Digit 6 24 • • • • • • • • • 25 th st m 26 n BCD Digit n-1 BCD Digit 27 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 32 encoding. 33 34 b. Set to Not Used. The Type of Digits field is ignored on receipt. 35 36 c. The Nature of Number field bit A is set as applicable to International. Other bits 37 are set as applicable. 38 39 d. The Numbering Plan field is set to Land Mobile Numbering (E.212) as 40 applicable. 41 e. The Encoding field is set to BCD. 42 43 f. The Number of Digits is between 0 and at least 15. 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) 3 4 The OriginationIndicator (ORIGIND) parameter defines the type of calls the MS is 5 allowed to originate. 6 7 Field Value Type Reference Notes 8 Identifier OriginationIndicator M 6.5.1.2 9 IMPLICIT Unsigned Enumerated 10 11 Length 1 octet M 6.5.1.1 12 Contents 13 HGFEDCBAoctetNotes 14 15 Allowed Call Types 1 a, b 16 17 Figure 97 OriginationIndicator parameter 18 19 Notes: 20 a. For values 4, 5, and 8, the Digits (Destination) parameter (see 6.5.2.58) shall 21 accompany the OriginationIndicator parameter and shall contain the selected 22 leading digits or directory number (e.g., NPA-NXX or NPA-NXX-XXXX for 23 24 NANP) or international E.164 number. 25 b. Value 8, Single directory number (e.g., NPA-NXX-XXXX for NANP), shall 26 cause all originations to be treated as if this single number had been dialed, with 27 exceptions (e.g., “9-1-1,” “*-9-1-1”). 28 29 30 31 Table 154 OriginationIndicator value 32 33 Allowed Call Types (octet 1) 34 Bits H G F E D C B A Value Meaning 35 36 00000000 0 Not used. 37 00000001 1 Prior agreement. 38 00000010 2 Origination denied. 39 Local calls only 00000011 3 . 40 00000100 4 Selected leading digits of directory number or 41 of international E.164 number (e.g., 42 NPA-NXX for NANP). See Note (a) above. 43 00000101 5 Selected leading digits of directory number 44 or of international E.164 number and local 45 calls only (e.g., NPA-NXX for NANP). See Note (a) above. 46 00000110 6 National long distance (includes local calls and 47 may include neighboring countries). 48 00000111 7 International calls (includes national long 49 distance and local calls). 50 00001000 8 Single directory number or international 51 E.164 number (e.g., NPA-NXX-XXXX for 52 NANP). See Notes (a) and (b) above. 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 (TIA/EIA-41-D Chapter 5, page 5-223) 4 The OriginationTriggers (ORIGTRIG) parameter defines the origination trigger points 5 6 that are currently active for the subscriber. 7 8 Field Value Type Reference Notes 9 Identifier OriginationTriggers M 6.5.1.2 10 IMPLICIT OCTET STRING 11 Length variable octets M 6.5.1.1 12 13 Contents 14 HGFEDCBAoctetNotes 15 16 RvtC Unrec WZ Int’l OLATA ILATA Local All 1 NLTOLL LTOLL 17 18 Reserved PA DP Pound DS Star 2 a 19 7 6 5 4 3 2 1 No 3 20 digits digits digits digits digits digits digit digits 21 15 14 13 12 11 10 9 8 22 digits digits digits digits digits digits digits digits 4 23 24 • • • n b 25 Figure 98 OriginationTriggers parameter 26 27 28 Notes: 29 a. Set reserved values to 0 when sending, and process other triggers before treating 30 received reserved values the same as All. 31 32 b. If unknown octets with bits set are received, process other triggers before 33 treating the same as All. Send only defined (or significant) octets. 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 Value Meaning 40 0 0 Trigger is not active. 41 1 1 Launch an OriginationRequest for any call 42 attempt. This overrides all other values. 43 44 Local (octet 1, bit B) 45 46 Bits H G F E D C B A Value Meaning 47 0 0 Trigger is not active. 48 1 1 Launch an OriginationRequest for any local call 49 attempt. 50 51 Local Intra-LATA Toll (LTOLL ILATA) (octet 1, bit C) 52 Bits H G F E D C B A Value Meaning 53 54 0 0 Trigger is not active. 55 1 1 Launch an OriginationRequest for any local toll 56 intra-LATA call attempt. Refers to intra-LATA 57 toll within the NANP. 58 59 60

TIA/EIA-41-D Chapter 5 Modifications51 Stage-3 Signaling Protocol N.S0016-0 v 1.0

Table 161 OriginationTriggers value (continued) 1 2 Inter-LATA Non-Local Toll (OLATA NLTOLL) (octet 1, bit D) 3 4 Bits H G F E D C B A Value Meaning 5 6 0 0 Trigger is not active. 1 1 Launch an OriginationRequest for any inter- 7 LATA toll call attempt toll calls outside the 8 local carrier's serving area. 9 10 International (Int’l ) (octet 1, bit E) 11 12 Bits H G F E D C B A Value Meaning 13 0 0 Trigger is not active. 14 1 1 Launch an OriginationRequest for any 15 international call attempt. 16 17 World Zone (WZ) (octet 1, bit F) 18 Bits H G F E D C B A Value Meaning 19 20 0 0 Trigger is not active. 21 1 1 Launch an OriginationRequest for any call 22 attempt outside of the current World Zone (as 23 defined in ITU-T Rec. E.164). [not 24 recommended for use]. 25 Unrecognized Number (Unrec) (octet 1, bit G) 26 27 Bits H G F E D C B A Value Meaning 28 0 0 Trigger is not active. 29 1 1 Launch an OriginationRequest for any call 30 attempt to an unrecognized number. 31 32 Revertive Call (RvtC) (octet 1, bit H) 33 Bits H G F E D C B A Value Meaning 34 35 0 0 Trigger is not active. 36 1 1 Launch an OriginationRequest for any Revertive 37 Call attempt. 38 39 Star (octet 2, bit A) 40 Bits H G F E D C B A Value Meaning 41 42 0 0 Trigger is not active. 43 1 1 Launch an OriginationRequest for any number 44 beginning with a Star ‘*’ digit. 45 Double Star (DS) (octet 2, bit B) 46 47 Bits H G F E D C B A Value Meaning 48 0 0 Trigger is not active. 49 1 1 Launch an OriginationRequest for any number 50 beginning with two Star ‘**’ digits. 51 52 Pound (octet 2, bit C) 53 Bits H G F E D C B A Value Meaning 54 55 0 0 Trigger is not active. 56 1 1 Launch an OriginationRequest for any number 57 beginning with a Pound ‘#’ digit. 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 Modifications53 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) 3 4 The PC_SSN parameter carries the ANSI national SS7 Point Code (PC) and Subsystem 5 Number (SSN) of a particular wireless network cellular functional entity. Type indicates 6 the type of functional entity (e.g., HLR, VLR, MSC). Used for subsequent routing by the 7 application and takes precedence over lower layer addressing. The Point Code may 8 represent a single entity or an alias for mated pair entities. Two descriptions of the format 9 are shown, one for ANSI SS7 point codes and a more general format for other national 10 point code formats. 11 12 Field Value Type Reference Notes 13 14 Identifier PC_SSN M 6.5.1.2 15 IMPLICIT OCTET STRING 16 Length 5 octets M 6.5.1.1 17 Contents 18 19 HGFEDCBAoctetNotes 20 ReservedType 1b 21 ANSI Point Code—Member Number 2a 22 23 ANSI Point Code—Cluster Number 3a 24 ANSI Point Code—Network Number 4a 25 Subsystem Number (SSN) 5 a 26 27 Figure 101 PC_SSN parameter (ANSI) 28 29 Notes: 30 31 a. See 5.1.2. 32 33 b. Reserved bits shall be ignored on receipt and set to zero on sending. 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 Field Value Type Reference Notes 2 3 Identifier PC_SSN M 6.5.1.2 4 IMPLICIT OCTET STRING 5 Length 5 octets M 6.5.1.1 6 7 Contents 8 9 H G F E D C B A octet Notes 10 Reserved 1 a 11 12 2 b,c 13 Point Code 3 b,c 14 15 4 b,c 16 Subsystem Number (SSN) 5 c 17 18 Figure 101A PC_SSN parameter (generic) 19 20 21 Notes: 22 a. Reserved bits shall be ignored on receipt and set to zero on sending. 23 24 b. Bit A of Octet 2 is the first bit that would be emitted if the point code was 25 transmitted by the MTP layer. If the point code is less than 24 bits in length, then 26 all bits beyond the end of the point code up to and including bit H of Octet 4, 27 should be set to 0. 28 29 c. See 5.3. 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 Modifications55 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) 3 4 The Profile is a collection of the subscriber’s calling profile information. This information 5 is a list of optional parameters. The Profile macro has been defined solely for editorial 6 convenience, and does not affect the encoding in any way. 7 8 PROFILE 9 Type Reference Notes 10 11 Contents 12 AuthenticationCapability O 6.5.2.8 a 13 14 CallingFeaturesIndicator O 6.5.2.20 b 15 CarrierDigits O 6.5.2.28 c 16 DMH_AccountCodeDigits O 6.5.2.59 d 17 18 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 22 MessageWaitingNotificationCount O 6.5.2.78 f 23 MessageWaitingNotificationType O 6.5.2.79 g 24 25 MobileDirectoryNumber O 6.5.2.80 d 26 OriginationIndicator O 6.5.2.89 h 27 OriginationTriggers O 6.5.2.90 i 28 29 PACAIndicator O 6.5.2.91 j 30 PreferredLanguageIndicator O 6.5.2.96 k 31 RestrictionDigits O 6.5.2.113 l 32 33 RoutingDigits O 6.5.2.114 m 34 SMS_OriginationRestrictions O 6.5.2.136 n 35 SMS_TerminationRestrictions O 6.5.2.138 o 36 37 SPINIPIN O 6.5.2.139 p 38 SPINITriggers O 6.5.2.140 q 39 TerminationRestrictionCode O 6.5.2.157 r 40 41 TerminationTriggers O 6.5.2.159 s 42 Figure 105 Profile Macro 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 a. Include on IS-41-C or later. 4 b. Include to identify feature authorization and activity. 5 6 c. Include if preferred carrier is applicable and TransactionCapability supported. 7 8 d. Include if available for recording purposes (see DMH). 9 10 e. Include if available for certain authorization restricted areas. 11 12 f. Include if MessageWaitingNotificationType is Message Waiting Indication and 13 number of messages waiting is authorized. 14 g. Include if Message Waiting Notification feature is active and a message is 15 waiting. 16 17 h. Include to indicate the type of calls allowed for origination service. 18 19 i. Include to indicate OriginationRequest triggers. 20 21 j. Include to identify the PACA feature. 22 23 k. Include to identify the Preferred Language feature. 24 l. Include if originations are restricted, e.g., to NPA-NXX or NPA-NXX-XXXX 25 26 and TransactionCapability supported. Set Nature of Number to International if it 27 is known that the destination network element for the profile can accept digits in 28 this format (e.g. MSCIdentificationNumber parameter previously received.) 29 m. Include for special routing information. 30 31 n. Include for MS originated Short Message Service. 32 33 o. Include for MS terminated Short Message Service. 34 35 p. Include if local SPINI operation supported. 36 37 q. Include to indicate Subscriber PIN Intercept triggers. 38 r. Include to indicate the type of call termination service. 39 40 s. Include to indicate the RedirectionRequest or TransferToNumberRequest 41 triggers. 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 Modifications57 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) 3 4 The PSTNTermination (PSTNTERM) parameter is used to provide an MSC with routing 5 information for calls which are to be terminated in the PSTN. 6 7 Field Value Type Reference Notes 8 Identifier PSTNTermination M 6.5.1.2 9 IMPLICIT SET 10 11 Length variable M 6.5.1.1 12 Contents 13 DestinationDigits M 6.5.2.56 h 14 CarrierDigits O 6.5.2.28 a, b 15 16 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 20 RoutingDigits O 6.5.2.114 b, e 21 TerminationTriggers O 6.5.2.159 b, f 22 • • • g 23 24 Figure 106 PSTNTermination parameter 25 26 Notes: 27 28 a. Optional, for preferred carrier inter-LATA call routing. Note that this 29 information may not be valid across international boundaries. 30 31 b. This parameter has precedence for this call leg over the parameters outside the 32 TerminationList parameter or the subscriber profile. 33 c. Optional, for recording purposes. 34 35 d. Include if part of a multi leg call. 36 37 e. Optional, for special routing purposes. 38 39 f. Include to indicate processing for failed call attempts. 40 41 g. Ignore unexpected parameters, if received. 42 43 h. Encode the DestinationDigits as International if the Originating MSC is known 44 to be capable of accepting digits in International format (e.g. 45 MSCIdentificationNumber parameter was received.) 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 (TIA/EIA-41-D Chapter 5, page 5-248) 4 The RestrictionDigits parameter specifies either the leading digits of the directory number 5 6 (e.g., 6-digit NANP office code) or a full directory number (e.g., 10-digit NANP directory 7 number) for which call originations are allowed, as indicated in the OriginationIndicator 8 parameter. 9 10 Field Value Type Reference Notes 11 Identifier RestrictionDigits M 6.5.1.2 a 12 IMPLICIT DigitsType 13 Length variable octets M 6.5.1.1 14 15 Contents 16 HGFEDCBAoctetNotes 17 18 Type of Digits 1 b 19 Nature of Number 2 c 20 Numbering Plan Encoding 3 d, e 21 22 Number of Digits 4 f 23 2nd BCD Digit 1st BCD Digit 5 24 4th BCD Digit 3rd BCD Digit 6 25 26 • • • • • • • • • 27 nth BCD Digit n-1st BCD Digit m 28 29 Figure 121 RestrictionDigits parameter for BCD digits 30 31 Notes: 32 33 a. Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field 34 encoding. 35 36 b. Ignore the field Type of Digits on receipt. 37 c. The Nature of Number field is set as applicable. 38 39 d. The Numbering Plan field is set to Telephony Numbering. 40 41 e. The Encoding field is set to BCD. 42 43 f. The Number of Digits is set as applicable (e.g. either 6 or 10 in NANP). 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

TIA/EIA-41-D Chapter 5 Modifications59 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) 3 4 The SenderIdentificationNumber (SENDERIN) parameter indicates the identification 5 number of the functional entity that is sending a message. 6 7 Field Value Type Reference Notes 8 Identifier SenderIdentificationNumber M 6.5.1.2 a 9 IMPLICIT DigitsType 10 11 Length variable octets M 6.5.1.1 12 Contents 13 HGFEDCBAoctetNotes 14 15 Type of Digits 1 b 16 Nature of Number 2 c 17 18 Numbering Plan Encoding 3 d, e 19 Number of Digits 4 f 20 2nd BCD Digit 1st BCD Digit 5 21 22 th rd 4 BCD Digit 3 BCD Digit 6 23 • • • • • • • • • 24 25 th st m n BCD Digit n-1 BCD Digit 26 Figure 124 SenderIdentificationNumber parameter for BCD digits 27 28 29 Notes: 30 a. Refer to the DigitsType parameter type (see 6.5.3.2) for notes and field 31 encoding. 32 33 b. Set to Not Used. The Type of Digits field is ignored on receipt. 34 35 c. The Nature of Number field bit A is set as applicable to International. Other bits 36 are set as applicable. 37 38 d. The Numbering Plan field is set to Land Mobile Numbering (E.212) as 39 applicable. 40 41 e. The Encoding field is set to BCD. 42 f. The Number of Digits is between 0 and at least 15. 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 (TIA/EIA-41-D Chapter 5, page 5-258) 4 The SMS_Address (SMSADDR) parameter is used to convey the current routing address 5 6 of the Serving MSC for the purpose of short message termination to an MS-based SME. 7 If SS7 is used for international SMS message routing, this parameter should be formatted 8 as an E.212 number. If SS7 is used for national message routing, this parameter may be 9 formatted either as an SS7 point code address or as an E.212 number. 10 11 Field Value Type Reference Notes 12 Identifier SMS_Address IMPLICIT M 6.5.1.2 a 13 DigitsType 14 15 Length variable octets M 6.5.1.1 16 Contents 17 HGFEDCBAoctetNotes 18 19 Type of Digits 1 b 20 Nature of Number 2 c 21 22 Numbering Plan Encoding 3 d, e 23 Number of Digits 4 f 24 2nd BCD Digit 1st BCD Digit 5 25 26 4th BCD Digit 3rd BCD Digit 6 27 • • • • • • • • • 28 th st 29 n BCD Digit n-1 BCD Digit m 30 31 Figure 132 SMS_Address parameter for BCD digits 32 33 Notes: 34 a. See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding. 35 36 b. Type of Digits is ignored on receipt. 37 38 c. Nature of Number may be National or International. 39 40 d. Numbering Plan supported shall include E.164, E.212, X.121, and Private 41 numbering plan for this parameter variant. 42 43 e. The encoding field shall always be set to BCD for this parameter variant. 44 f. The Number of Digits ranges from 0 to at least 15. 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

1 Field Value Type Reference Notes 2 Identifier SMS_Address IMPLICIT M 6.5.1.2 a 3 DigitsType 4 Length variable octets M 6.5.1.1 5 6 Contents 7 HGFEDCBAoctetNotes 8 9 Type of Digits 1 b 10 Nature of Number 2 c 11 Numbering Plan Encoding 3 d, e 12 13 MSB 4 14 5 15 IP Address 6 16 17 LSB 7 18 19 Figure 133 SMS_Address Encoding for an IP address 20 21 Notes: 22 a. 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. 25 26 c. Nature of Number may be National or International. 27 28 d. Numbering Plan shall be IP for this parameter variant. 29 e. Encoding shall be octet string for this parameter variant. 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 Value Type Reference Notes 2 3 Identifier SMS_Address IMPLICIT M 6.5.1.2 a 4 DigitsType 5 Length variable octets M 6.5.1.1 6 7 Contents 8 HGFEDCBAoctetNotes 9 10 Type of Digits 1 b 11 Nature of Number 2 c 12 Numbering Plan Encoding 3 d, e 13 14 Point Code—Member Number 4 15 Point Code—Cluster Number 5 16 Point Code—Network Number 6 17 18 Subsystem Number (SSN) 7 19 Figure 134 SMS_Address parameter for an ANSI SS7 Point Code Address 20 21 22 Notes: 23 a. See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding. 24 25 b. Type of Digits is ignored on receipt. 26 27 c. Nature of Number may shall be National or International. 28 29 d. Numbering Plan shall be SS7 for this parameter variant. 30 e. Encoding shall be octet string for this parameter variant. 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

1 Field Value Type Reference Notes 2 Identifier SMS_Address IMPLICIT M 6.5.1.2 a 3 DigitsType 4 Length variable octets M 6.5.1.1 5 6 Contents 7 H G F E D C B A octet Notes 8 9 Type of Digits 1 b 10 Nature of Number 2 c 11 Numbering Plan Encoding 3 d, e 12 13 4 f 14 Point Code 5 15 6 16 17 Subsystem Number (SSN) 7 18 19 Figure 134A SMS_Address Parameter for a Generic SS7 Point Code 20 Address 21 22 Notes: 23 a. See the DigitsType parameter type (see 6.5.3.2) for notes and field encoding. 24 25 b. Type of Digits is ignored on receipt. 26 27 c. Nature of Number shall be National. 28 29 d. Numbering Plan shall be SS7 for this parameter variant. 30 31 e. Encoding shall be octet string for this parameter variant. 32 f. Bit A of Octet 4 is the first bit that would be emitted if the point code was 33 transmitted by the MTP layer. If the point code is less than 24 bits in length, then 34 all bits beyond the end of the point code up to and including bit H of Octet 6, 35 36 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

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 (TIA/EIA-41-D Chapter 5, page 5-287) 4 The SPINITriggers parameter defines the trigger points that are currently active for the 5 6 subscriber. 7 8 Field Value Type Reference Notes 9 Identifier SPINITriggers M 6.5.1.2 10 IMPLICIT OCTET STRING 11 Length variable octets M 6.5.1.1 12 13 Contents 14 HGFEDCBAoctetNotes 15 16 RvtC Unrec WZ Int’l OLATA ILATA Local All 1 NLTOLL LTOLL 17 18 Reserved PA DP Pound DS Star 2 a 19 7 6 5 4 3 2 1 No 3 20 digits digits digits digits digits digits digit digits 21 15 14 13 12 11 10 9 8 4 22 digits digits digits digits digits digits digits digits 23 24 • • • n b 25 Figure 157 SPINITriggers parameter 26 27 28 Notes: 29 a. Set reserved values to 0 when sending, and process other triggers before treating 30 received reserved values the same as All. 31 32 b. If unknown octets with bits set are received, process other triggers before 33 treating the same as All. Send only defined (or significant) octets. 34 35 36 Table 177 SPINITriggers value 37 38 All Origination (All) (octet 1, bit A) 39 40 Bits H G F E D C B A Value Meaning 41 0 0 Trigger is not active. 42 1 1 Execute local SPINI procedures for any call 43 origination. This overrides all other values. 44 45 Local (octet 1, bit B) 46 Bits H G F E D C B A Value Meaning 47 48 0 0 Trigger is not active. 49 1 1 Execute local SPINI procedures for any local 50 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) 3 4 Bits H G F E D C B A Value Meaning 5 6 0 0 Trigger is not active. 1 1 Execute local SPINI procedures for any local 7 toll intra-LATA call attempt. Refers to intra- 8 LATA toll within the NANP. 9 10 Inter-LATA Non-Local Toll (OLATA NLTOLL) (octet 1, bit D) 11 12 Bits H G F E D C B A Value Meaning 13 0 0 Trigger is not active. 14 1 1 Execute local SPINI procedures for any inter- 15 LATA toll call attempt toll calls outside the 16 local carrier's serving area. 17 18 International (Int’l) (octet 1, bit E) 19 Bits H G F E D C B A Value Meaning 20 21 0 0 Trigger is not active. 22 1 1 Execute local SPINI procedures for any 23 international call attempt. 24 World Zone (WZ) (octet 1, bit F) 25 26 Bits H G F E D C B A Value Meaning 27 0 0 Trigger is not active. 28 1 1 Execute local SPINI procedures for any call 29 attempt outside of the current World Zone (as 30 defined in ITU-T Rec. E.164). This value is not 31 recommended for use. 32 33 Unrecognized Number (Unrec) (octet 1, bit G) 34 Bits H G F E D C B A Value Meaning 35 36 0 0 Trigger is not active. 37 1 1 Execute local SPINI procedures for any call 38 attempt to an unrecognized number. 39 40 Revertive Call (RvtC) (octet 1, bit H) 41 Bits H G F E D C B A Value Meaning 42 43 0 0 Trigger is not active. 44 1 1 Execute local SPINI procedures for any 45 Revertive Call attempt. 46 Star (octet 2, bit A) 47 48 Bits H G F E D C B A Value Meaning 49 0 0 Trigger is not active. 50 1 1 Execute local SPINI procedures for any number 51 beginning with a Star ‘*’ digit. 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 10 Field Value Type Reference Notes 11 Identifier DigitsType IMPLICIT OCTET M 6.5.1.2 12 STRING 13 14 Length m variable octets M 6.5.1.1 a 15 Contents 16 H G F E D C B A octet Notes 17 18 Type of Digits 1 b 19 Nature of Number 2 c 20 21 Numbering Plan Encoding 3 d,e 22 4 f 23 Point Code 5 f 24 25 6 f 26 Subsystem Number (SSN) 7 27 28 Figure XXX DigitsType parameter type variant for a generic SS7 point 29 code address 30 31 Notes: 32 33 a. Where m = 7 for this parameter type variant. 34 b. Type of Digits is ignored upon receipt. 35 36 c. Nature of Number shall be National. 37 38 d. Numbering Plan shall be SS7 for this parameter variant. 39 40 e. Encoding shall be octet string for this parameter variant. 41 42 f. Bit A of Octet 4 is the first bit that would be emitted if the point code was 43 transmitted by the MTP layer. If the point code is less than 24 bits in length, then 44 all bits beyond the end of the point code up to and including bit H of Octet 6, 45 should be set to 0. 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 Type of Digits (octet 1, bits A-H) 3 4 Bits H G F E D C B A Value Meaning 5 6 00000000 0 Not Used. 00000001 1 Dialed Number or Called Party Number. 7 00000010 2 Calling Party Number. 8 00000011 3 Caller Interaction. These are the digits dialed 9 by a user in response to a prompt (not used in 10 this Standard). 11 00000100 4 Routing Number. This number is used to steer 12 a call towards its ultimate destination. 13 00000101 5 Billing Number. This is the number to use for 14 ANI, Charge Number or other recording 15 purposes. 16 00000110 6 Destination Number. This is the network 17 address of the called party. 18 00000111 7 LATA (not used in this Standard). 19 00001000 8 Carrier. The identity of In North America the 20 three, four, or five digits represent an 21 interexchange or international a preferred 22 carrier. 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 2 Table 196 (continued) 3 4 Nature of Number (octet 2, bits A-H) 5 Bits H G F E D C B A Value Meaning 6 7 0-National. 8 1-International. 9 0-Presentation Allowed. 10 1-Presentation Restricted. 11 0-Number is available. 12 1-Number is not available. 13 00 - User provided, not screened. 14 01 - User provided, screening passed. 15 10 - User provided, screening failed. 16 11 - Network provided. 17 XX X - Reserved. 18 Encoding (octet 3, bits A-D) 19 20 Bits H G F E D C B A Value Meaning 21 0000 0 Not used. 22 0001 1 BCD (see Digit definition below). 23 0010 2 IA5. The International Alphabet 5 as defined in 24 ITU-T Rec. T.50. (also known as the 25 International Reference Alphabet (IRA)). 26 0011 3 Octet string. This is used for IP and SS7 27 addresses. 28 X X X X - Other values are reserved. 29 30 Numbering Plan (octet 3, bits E-H) 31 Bits H G F E D C B A Value Meaning 32 33 0 0 0 0 0 Unknown or not applicable. 34 0001 1 ISDN Numbering (not used in this Standard). 35 0010 2 Telephony Numbering (ITU-T Rec. E.164, 36 E.163). 37 0011 3 Data Numbering (ITU-T Rec. X.121) (not used 38 in this Standard). 39 0100 4 Telex Numbering (ITU-T Rec. F.69) (not used 40 in this Standard). 41 0101 5 Maritime Mobile Numbering (not used in this 42 Standard). 43 0110 6 Land Mobile Numbering (ITU-T Rec. E.212) 44 0111 7 Private Numbering Plan (service provider 45 defined). 46 1101 13 ANSI SS7 Point Code (PC) and Subsystem 47 Number (SSN). Protocol (IP) Address 48 1110 14 . 1 1 1 1 15 Reserved for extension. 49 X X X X - Other values are reserved. 50 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 2 5. TIA/EIA-41-D Chapter 6 3 4 “Signaling Procedures” Modifications 5 6 2.1 INTERSYSTEM HANDOFF PROCEDURES 7 8 (TIA/EIA-41-D Chapter 6, page 6-5) 9 This section provides the transaction procedures defined for the Intersystem Handoff. All 10 messages and associated parameters are defined in Chapter 5; Timer values are specified 11 in Section 7 of this Chapter. 12 13 14 The omitted portions of this section are retained without modification. 15 16 17 The procedures defined here are based on the assumption that intersystem handoff relies 18 upon dedicated intersystem trunks. This is required since intersystem handoff is a tightly 19 controlled activity of the cellular systems involved. Intersystem handoff cannot be 20 considered any differently than an inter-cell handoff. The intersystem handoff may or may 21 not be inter-LATA depending upon where the LATA boundary is and also where the 22 mobile call was placed. 23 24 The handoff procedures specified in the following sections can be applied to consecutive 25 inter-MSC handoffs for the same MS. A non-Anchor Serving MSC that has handed off a 26 call becomes a Tandem MSC. The initial Serving MSC retains its role as an Anchor 27 MSC. 28 29 30 3.2.3 MSC Analyze MS Dialed Number 31 32 (TIA/EIA-41-D Chapter 6, page 6-15) 33 Upon demand the Anchor MSC shall do the following: 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 39 is the MS’s mobile directory number (or MIN if the mobile directory number is not 40 available):1 41 42 9-1 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the 43 PointOfReturn. 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, 48 WZ, or Unrec, triggers are on AND the call type matches the corresponding trigger: 49 50 11-1 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the 51 PointOfReturn. 52 11-2 IF a Digits (Dialed) parameter is received: 53 54

55 1 If the MS is a foreign roamer and plus code dialing has not been used, the revertive call condition 56 is satisfied if the dialed digits consist of the international prefix followed by the full E.164 form 57 of the MS’s MDN. If the MS is a foreign roamer and plus code dialing has been used, this 58 condition is detected if the dialed digits consist of the full E.164 form of the MS’s MDN. 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 Process the dialed number locally to set the PointOfReturn. 4 11-2-2 ENDIF. 5 11-3 ENDIF. 6 7 12 ELSEIF the any unknown OriginationTriggers are on (e.g., reserved bits set to 1 or 8 extra octets with any bit set to 1): 9 12-1 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the 10 PointOfReturn. 11 12 12-2 IF a Digits (Dialed) parameter is received: 13 12-2-1 IF the type of the Digits is unknown. 14 15 12-2-1-1 Process the dialed number locally to set the PointOfReturn. 16 12-2-2 ENDIF. 17 18 12-3 ENDIF. 19 13 ELSEIF the call type matches an active trigger in the SPINITriggers parameter:1 20 21 13-1 Execute the “MSC SPINI Originating Call Invocation” task (see 5.21.3) to set 22 the PointOfReturn. 23 24 The omitted portions of this section are retained without modification. 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 36 TLDN. 37 1-9-6-2-1-5 IF the MSCIdentificationNumber parameter was received (or 38 the originating MSC is otherwise known to support 39 internationally formatted TLDNs): 40 41 1-9-6-2-1-5-1 Include the Digits (Destination) parameter set equal to the 42 TLDN in international E.164 format with the nature of 43 number set to International. 44 1-9-6-2-1-X ELSE: 45 46 1-9-6-2-1-X-1 Include the Digits (Destination) parameter set equal to the 47 TLDN in national E.164 format with the Nature of Number 48 set to National. 49 1-9-6-2-1-Y ENDIF. 50 51 52 53 54

55 1 56 If the MS is a foreign roamer and plus code dialing has not been used, the revertive call condition 57 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 58 condition is detected if the dialed digits consist of the full E.164 form of the MS’s MDN. 59 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 5 6 (TIA/EIA-41-D Chapter 6, page 6-235) 7 8 The omitted portions of this section are retained without modification. 9 10 (The MS is geographically authorized.) 11 12 12-11 IF an SMS_Address parameter is received: 13 12-11-1 IF the SMS_Address is different than the current SMS temporary routing 14 address: 15 16 12-11-1-1 GOTO Register the MS. 17 12-11-2 ENDIF. 18 12-12 ELSE: 19 20 12-12-1 IF an SMS temporary routing address exists: 21 12-12-1-1 Clear the SMS temporary routing address. 22 23 12-12-1-2 GOTO Register the MS (to report loss of SMS capability). 24 12-12-2 ENDIF. 25 26 12-13 ENDIF. 27 12-x If the MSCIdentificationNumber parameter is received: 28 12-x-1 IF the current serving MSC did not provide its MSCIdentificationNumber 29 30 during registration: 31 12-x-1-1 GOTO Register the MS. 32 12-x-2 ENDIF. 33 34 12-y ELSE (the MSCIdentificationNumber parameter is not received): 35 12-y-1 IF the current serving MSC did provide its MSCIdentificationNumber 36 during registration: 37 38 12-y-1-1 GOTO Register the MS. 39 12-y-2 ENDIF. 40 41 12-z ENDIF. 42 12-14 IF the information requested by the QualificationInformationCode is available: 43 12-14-1 IF the QualificationInformationCode indicates Profile only or Validation 44 and profile: 45 46 12-14-1-1 Execute the “Loading of Profile Parameters” task (see 3.1.3). 47 12-14-2 ENDIF. 48 49 12-14-3 IF the QualificationInformationCode indicates Validation only or Validation 50 and profile: 51 12-14-3-1 Include the AuthorizationPeriod parameter set appropriately. 52 53 12-14-4 ENDIF. 54 12-14-5 Send a RETURN RESULT to the requesting MSC. 55 12-14-6 Exit this task. 56 57 12-15 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 3 Register the MS: 4 5 4.41.3 MSC Receiving RoutingRequest INVOKE 6 (TIA/EIA-41-D Chapter 6, page 6-254) 7 8 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 15 RETURN RESULT or UnsolicitedResponse INVOKE. 16 1-4-6-1-2-X IF a TLDN was received in the UnsolicitedResponse 17 18 INVOKE: 19 1-4-6-1-2-X-1 IF the MSCIdentificationNumber parameter was received 20 in the RoutingRequest INVOKE (or the originating MSC 21 is otherwise known to support internationally formatted 22 TLDNs): 23 24 1-4-6-1-2-X-1-1 Convert the Digits (Destination) to International 25 format, using, as country code, the country code 26 of the border MSC. 27 1-4-6-1-2-X-2 ENDIF. 28 29 1-4-6-1-2-Y ENDIF. 30 1-4-6-1-2-2 Send a RETURN RESULT to the requesting VLR. 31 1-4-6-1-2-3 Exit this task. 32 33 The omitted portions of this section are retained without modification. 34 35 36 (TLDN is selected here.) 37 38 1-6 IF TLDN is available: 39 1-6-1 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. 46 1-6-8 IF the MSCIdentificationNumber parameter was received (or the originating 47 48 MSC is otherwise known to support internationally formatted TLDNs): 49 1-6-8-1 Include the Digits (Destination) parameter set equal to the TLDN in 50 international E.164 format with the Nature of Number set to 51 International. 52 53 1-6-8A ELSE: 54 1-6-8A-1 Include the Digits (Destination) parameter set equal to the TLDN in 55 national E.164 format with the Nature of Number set to National. 56 1-6-8B ENDIF. 57 58 59 60

TIA/EIA-41-D Chapter 6 Modifications 73 Stage-3 Signaling Procedures