1、 ATIS-1000003 NUMBER PORTABILITY DATABASE AND GLOBAL TITLE TRANSLATION TECHNICAL REQUIREMENTS The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations sta
2、ndards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees and its Incubator Solutions Program. ATIS-1000003, Number
3、 Portability Database and Global Title Translation Is an ATIS Standard developed by the PTSC.3 Subcommittee under the ATIS Packet Technologies and Systems Committee (PTSC). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 200
4、6 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online
5、at . Printed in the United States of America. ATIS-1000003 Technical Requirements for NUMBER PORTABILITY DATABASE AND GLOBAL TITLE TRANSLATION Secretariat Alliance for Telecommunications Industry Solutions Approved October, 2004 Abstract This document defines the Number Portability Database and Glob
6、al Title Translation technical requirements for number portability (NP) using the Location Routing Number (LRN) Method. ATIS-1000003 ii FOREWORD This document defines the Number Portability Database and Global Title Translation technical requirements for number portability (NP) using the Location Ro
7、uting Number (LRN) Method. The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manufacturers. The Packet Technologies and Systems Committee (PTSC) - formerly T1S1 - develops and recommends standards and techni
8、cal reports related to services, architectures, and signaling, in addition to related subjects under consideration in other North American and international standards bodies. PTSC coordinates and develops standards and technical reports relevant to telecommunications networks in the U.S., reviews an
9、d prepares contributions on such matters for submission to U.S. ITU-T and U.S. ITU-R Study Groups or other standards organizations, and reviews for acceptability or per contra the positions of other countries in related standards development and takes or recommends appropriate actions. Number portab
10、ility is a circuit switched network capability that allows an end user to move their North American Numbering Plan (NANP) number from one serving switch in a network to another switch in the same or different circuit switched network. NP is transparent to all end users. Requirements provided in this
11、 document address number portability using the LRN obtained from a centralized database to identify the recipient switch when numbers are ported. This document does not address number portability for subscribers with directory numbers that are also used for packet switched data. This document provid
12、es the requirements for service provider portability, and location portability within a rate center. Number portability outside a rate center is beyond the scope of this document. This document does not address resale or unbundling. Information contained in normative annexes is considered part of th
13、is technical requirements document. Information contained in informative annexes is not considered part of this technical requirements document but is rather auxiliary to the specification. Similarly, footnotes are informative. ANSI guidelines specify two categories of requirements: mandatory and re
14、commendation. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently identifiable as having distinct compatibility
15、 or performance advantages. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, ATIS Secretariat, and 1200 G Street NW, Suite 500, Washington, DC 20005. The PTSC.3 Subcommittee was responsible for the development of
16、 this document. ATIS-1000003 iii TABLE OF CONTENTS FOREWORD .II 1 SCOPE AND OVERVIEW 1 1.1 SCOPE 1 1.2 OVERVIEW 2 2 INTRODUCTION 3 2.1 NETWORK PREREQUISITES FOR NUMBER PORTABILITY 3 2.2 ASSUMPTIONS . 4 2.3 ACRONYMS AND DEFINITIONS . 6 2.3.1 Acronyms . 6 2.3.2 Definitions 8 2.4 REFERENCES . 10 2.4.1
17、Normative References 10 2.4.2 Informative References 11 3 USER PERSPECTIVE 13 3.1 NP CAPABILITY OVERVIEW. 13 3.2 END USER PERSPECTIVE (HUMAN INTERFACE). 15 3.3 SERVICE PROVIDER PERSPECTIVE 15 3.3.1 Operations Personnel 16 3.3.2 Provisioning of NP Data 16 3.4 CALL FLOWS. 16 4 NETWORK IMPACTS 22 4.1 S
18、WITCHING SYSTEMS 23 4.2 SIGNAL TRANSFER POINT (STP) 23 4.3 LOCAL SERVICE MANAGEMENT SYSTEM (LSMS) . 23 4.4 NUMBER PORTABILITY ADMINISTRATION CENTER (NPAC). 24 4.5 OPERATIONS SYSTEMS IMPACTS 24 4.6 OPERATOR SERVICES SYSTEMS . 24 4.7 CUSTOMER PREMISES EQUIPMENT (CPE) AND USER EQUIPMENT NEEDS AND IMPAC
19、TS . 24 4.8 WIRELESS SERVICE PROVIDERS. 25 4.9 SECURITY ISSUES 25 4.10 GENERAL NETWORK CAPACITY IMPACTS 25 5 NP CAPABILITY REQUIREMENTS . 25 5.1 DATA STRUCTURES. 26 5.1.1 Data for Ported DNs 26 5.1.1.1 Minimum Data for NPDB application 26 5.1.1.1.1 Minimum Data Needed for Ported DN in the NPDB appli
20、cation. 26 5.1.1.1.2 Other Data Needed for the NPDB application. 27 5.1.1.2 Minimum Data for NP GTT Function . 27 5.1.2 Data for Default GTT Routing . 29 5.1.3 Other Data Items 30 5.2 NPDB APPLICATION PROCESSING REQUIREMENTS 30 5.2.1 Processing of NP Query Messages 31 5.2.1.1 Parameters Received in
21、ANSI IN Messages 31 5.2.1.1.1 CalledPartyID Parameter Received in ANSI IN Message 32 5.2.1.1.2 TriggerCriteriaType Parameter Received in ANSI IN Message. 32 5.2.1.1.3 acgEncountered Parameter Received in ANSI IN Messages 33 5.2.1.1.4 Other Optional Parameters in Received ANSI IN Messages 33 5.2.1.2
22、Parameters Received in pre-IN (IN/1) Messages 33 5.2.2 Responses for Ported DN. 34 5.2.2.1 analyzeRoute Response for Ported DN . 34 ATIS-1000003 iv 5.2.2.2 ConnectionControl:Connect Response for Ported DN. 35 5.2.3 Responses for Non-Ported DN . 36 5.2.3.1 analyzeRoute Response for Non-Ported DN . 36
23、 5.2.3.2 pre-IN (IN/1) ConnectionControl:Connect Response for Non-Ported DN 36 5.2.4 Other ANSI IN Responses and Messages . 37 5.2.4.1 ANSI IN ACG Message . 37 5.2.5 Other Pre-IN (IN/1) Responses 37 5.3 NP GLOBAL TITLE TRANSLATION FUNCTION. 38 5.3.1 NP GTT Function Processing for Ten Digit GTAI. 41
24、5.3.1.1 Performing Final GTT For a Ported DN . 41 5.3.1.2 Performing Non-Final GTT For a Ported DN 42 5.3.1.3 Performing Final GTT For a Non-Ported DN 42 5.3.1.4 Performing Non-Final GTT For a Non-Ported DN 42 5.3.2 NP GTT for Less than Ten-Digit GTAI 42 5.4 OPERATOR SERVICES SUPPORT FUNCTIONS . 44
25、5.5 ERRORS AND EXCEPTIONS . 44 5.6 SIGNALING AND PROTOCOL REQUIREMENTS FOR INTERFACES . 47 5.6.1 NPAC to LSMS. 47 5.6.2 LSMS to NPDB and NPGTT Systems. 47 5.6.3 Switch to NPDB application 47 5.6.3.2 NP Response Messages. 48 5.6.3.3 NP Message Parameters. 50 5.6.4 Operator Services Systems to NPDB ap
26、plication System. 50 5.6.5 TCAP Message Formats for NP GTT Function . 50 5.6.5.1 LIDB TCAP Message Formats 50 5.6.5.2 GTT Routing of CLASS Response Messages 52 5.7 HARDWARE INTERFACE REQUIREMENTS 53 5.8 OPERATIONS, ADMINISTRATION, MAINTENANCE AND PROVISIONING REQUIREMENTS 53 5.8.1 Measurements 53 5.
27、8.2 Network Management 54 5.8.3 Maintenance Requirements 55 5.8.4 Billing 55 5.8.5 Administrative I/O Messages and Reports . 56 5.8.6 Audits . 56 5.9 INITIALIZATION AND RECOVERY REQUIREMENTS. 58 5.10 CAPACITY, PERFORMANCE AND RELIABILITY REQUIREMENTS . 58 ANNEX A LOOPING OR MISROUTING OF SIGNALING M
28、ESSAGES WITH NUMBER PORTABILITY . 62 A1. INTRODUCTION. 62 A2. BACKGROUND 62 A3. PROBLEM STATEMENT 62 A4. POSSIBLE ALTERNATIVES . 65 A4.1. The ten-digit GTT node always performs final GTT. 65 A4.2. TT mapping on internetwork linksets. 66 A4.3. Update GTT provisioning in ported to network prior to upd
29、ating the provisioning in other networks 67 A4.4. Gateway Screening of SS7 messages . 67 A4.5. Transaction comparison list 67 A4.6. MTP loop detection and removal procedures 68 A4.7. MTP hop counter. 69 A4.8. SCCP hop counter . 70 A4.9. Hop counter in a TCAP parameter 70 A4.10. Internetwork OMAP 71
30、A4.11. Hop counter in the SSN field of the GTAI. 71 A4.12. TT mapping at the ten-digit GTT node . 71 A4.13. TT mapping and GTAI replacement at the ten-Digit GTT node . 72 ATIS-1000003 A4.14. Multiple alias point codes. 73 A4.15. Separate pre however, if the B or D channels are carrying packet data,
31、the channels have packet addresses, which are not portable. 2. The NP capability addresses the requirements necessary for location portability and service provider portability within a rate center. Service portability is not explicitly addressed by this document. 3. It is assumed that NP will not be
32、 “flash cut” into a network(s). 4. Ported numbers that become vacant will be returned to the donor switch. 5. Systems that support NPDB queries or the NP GTT function, along with their supporting LSMS, must be able to support NPA splits. NOTE - The NPAC system will not download data changes due to N
33、PA splits. Updates to records affected by an NPA split must be performed by the service providers systems. Also, the NPDB application and the NP GTT function must be able to support both old and new NPAs during permissive dialing periods. Location Routing Number (LRN)6. Each switch has at least one
34、NPA-NXX that is “homed” to the switch (assigned in the LERG) and this NPA-NXX can be used for the LRN. This may be an existing NPA-NXX or newly assigned NPA-NXX to the switch. 7. Only one NPA-NXX is needed for the first 6 digits of an LRN per LATA to identify the switch. 8. LRNs may also be DNs assi
35、gned to customers and these DNs may also be portable. Systems that Make NPDB Queries 9. Switches from which numbers have been ported (“donor“ switches) must be configured to perform NP queries for calls to those DNs which have not encountered NP triggers in previous portions of the call path. ATIS-1
36、000003 5 General Items about Platforms Supporting NP Queries10. An NPDB application only needs to support receiving the types of NP queries that are generated by the switches served by that NPDB application. Similarly, an NPDB application only needs to support sending the NP responses recognized by
37、the switches served by that NPDB application. 11. Nothing in this document restricts the NPDB application platform from running other applications in addition to the NPDB application described by this document, including other NP applications. 12. These requirements make no assumptions about the dep
38、loyed architecture of the NPDB application platforms which provide the NPDB application, or the method by which the NPDB application platforms are connected to the SS7 network. NPDB application platforms may be deployed in simplex, mated (duplex), N+1, or any other configuration, and can be connecte
39、d to the SS7 network using simplex or mated (duplex) Signaling Transfer Points (STPs). Selecting an appropriate network architecture is an exercise for each service provider, based on their requirements for reliability, survivability, performance under failure conditions, etc. 13. These requirements
40、 make no assumptions about the NPDB application platform software or hardware platform which supports the NPDB application. 14. These requirements make no assumptions about the way in which NP data may be distributed among multiple instances of NPDB applications used by a single service provider. 15
41、. An NP GTT function is available to each service providers network. The NP GTT function can be supported in an STP, SCP, or other suitable platform. It is assumed that SS7 translations throughout the service providers network are configured to route SS7 messages requiring the NP GTT function to the
42、 system performing the NP GTT function. 16. If a single platform supports both the NPDB application and the NP GTT function, then addressing resource and capacity conflicts between the two functions is a matter to be resolved between service providers and their vendors, and is not addressed by this
43、document. Miscellaneous Coding and Routing Items 17. Translation Type (TT) 11 has been defined for internetwork NP Queries. Therefore, this TT value can be provisioned for NP queries as distinct from other American National Standards Institute (ANSI) Intelligent Network (IN) or pre-IN (IN/1) queries
44、. 18. Service Codes (e.g., 411) or numbers with Service Access Codes (e.g., 800) are not subject to NP triggers. 19. These requirements assume that SS7 translations in the switch and STP are configured to route NP queries to the NPDB application containing data to process the specific NP query. 20.
45、It is assumed that no changes to SS7 gateway screening requirements (GR-82-CORE, Appendix C) are necessary to support NP. Any interactions between existing gateway screening capabilities and NP are not addressed by this document. At this time, no need for gateway screening following the NP GTT has b
46、een identified. 21. The interactions between Automatic Code Gapping (ACG) procedures, various NPDB application deployment configurations (mated pairs, N+1), different SS7 addressing ATIS-1000003 6 methods (point code, alias point code), and traffic balancing methods (load sharing, primary and second
47、ary routing) are not addressed by this document. These issues are left to each carrier to resolve based on their specific network architecture and system capabilities. 22. Query messaging traffic controls (such as ACG for ANSI IN and pre-IN (IN/1), and similar controls for LIDB queries) currently ar
48、e often based upon 6 digits (NPA-NXX). Now that a given NPA-NXX may be shared among multiple service providers, controls issued from one NPDB application on an NPA-NXX basis may also restrict queries that affect other service providers that share the same NPA-NXX. Resolution of the multiple service
49、provider interactions of query messaging traffic controls is not addressed by this document. 23. The definition of any requirements necessary to support Operations Maintenance Application Part (OMAP) message routing as a result of NP impacts is for future study, and is not addressed by this document. 2.3 Acronyms and Definitions 2.3.1 Acronyms AC Automatic Callback ACG Automatic Code Gapping AIN Advanced Intelligent Network AMA Automatic Message Accounting ANI Automatic Number Identification (a.k.a. Billing Number) ANSI American National Standard Institute ANSI IN American Nat
