ATIS 1000004-2004 Thousands Block Number Pooling Using Number Portability.pdf

1、 ATIS-1000004 THOUSANDS BLOCK NUMBER POOLING USING NUMBER PORTABILITY 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 stan

2、dards 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-1000004, Thousan

3、ds Block Number Pooling Using Number Portability 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 2006

4、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 at

5、 . Printed in the United States of America. ATIS-1000004 Technical Requirements for THOUSANDS BLOCK NUMBER POOLING USING NUMBER PORTABILITY Secretariat Alliance for Telecommunications Industry Solutions Approved October, 2004 Abstract This technical requirements document defines the switching system

6、, Number Portability Database (NPDB), and Number Portability Global Title Translation (NP GTT) requirements for thousands Block Number Pooling in Number Portability (NP) capable wireline networks. ATIS-1000004 ii FOREWORD The Alliance for Telecommunication Industry Solutions (ATIS) serves the public

7、 through improved understanding between carriers, customers, and manufacturers. The Packet Technologies and Systems Committee (PTSC) - formerly T1S1 - develops and recommends standards and technical reports related to services, architectures, and signaling, in addition to related subjects under cons

8、ideration 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 and prepares contributions on such matters for submission to U.S. ITU-T and U.S. ITU-R Study Groups or othe

9、r 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 portability is a circuit switched network capability that allows an end user to move their North American Numbe

10、ring Plan (NANP) number from one serving switch in a network to another switch in the same or different circuit switched network. This technical requirements document defines the switching system, Number Portability Database (NPDB), and Number Portability Global Title Translation (NP GTT) requiremen

11、ts for thousands Block Number Pooling in Number Portability (NP) capable wireline networks. This uses the Location Routing Number (LRN) method for number portability. Thousands Block Number Pooling shares an NPA-NXX among carriers allocating numbers in blocks of one-thousand numbers with the same NP

12、A-NXX-X. Number pooling is a number administration and assignment process that allocates numbering resources to a shared reservoir associated with a designated geographic area such that blocks of directory numbers (DNs) smaller than an entire NXX code are available for assignment by service provider

13、s. Information contained in normative annexes is considered part of this technical requirements document. Information contained in informative annexes is not considered part of these technical requirements but is auxiliary to the specification. Similarly, footnotes are informative. ANSI guidelines s

14、pecify two categories of requirements: mandatory and recommendation. 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

15、currently identifiable as having distinct compatibility 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 PTS

16、C.3 Subcommittee was responsible for the development of this document. ATIS-1000004 iii TABLE OF CONTENTS FOREWORD .II 1 SCOPE AND OVERVIEW. 5 1.1 SCOPE 5 1.2 OVERVIEW . 5 2 INTRODUCTION . 7 2.1 NETWORK PREREQUISITES FOR NUMBER POOLING 7 2.2 ASSUMPTIONS 7 2.3 ACRONYMS AND DEFINITIONS 8 2.3.1 Acronym

17、s 8 2.3.2 Definitions. 9 2.3.3 References. 10 2.3.3.1 Normative References 10 2.3.3.2 INFORMATIVE REFERENCES . 11 3 USER PERSPECTIVE 11 3.1 END USER PERSPECTIVE (HUMAN INTERFACE) . 11 3.2 SERVICE PROVIDER PERSPECTIVE . 11 3.3 CALL FLOWS 12 3.3.1 NP-Reserved Marking. 12 3.3.1.1 Call Flow without NP-R

18、eserved Marking 12 3.3.1.2 Call Flow with NP-Reserved Marking . 14 3.3.2 Ported Out Marking for LRN-Routed Calls 14 4 NUMBER POOLING REQUIREMENTS 16 4.1 SWITCHING SYSTEM REQUIREMENTS 16 4.1.1 Default Routing. 17 4.1.2 LRN Routing to Unallocated Numbers 18 4.1.2.1 PROVISIONING AND ADMINISTRATION OF N

19、P-RESERVED AND PORTED OUT MARKINGS 19 4.1.2.2 Call Processing Associated with NP-Reserved and Ported Out Markings. 20 4.2 NPDB AND NP GTT REQUIREMENTS . 21 4.3 SIGNALING AND PROTOCOL REQUIREMENTS . 22 4.4 FEATURE INTERACTIONS 22 4.5 OPERATIONS, ADMINISTRATION AND PROVISIONING REQUIREMENTS 22 4.5.1 M

20、easurements . 22 4.5.2 Network Management . 22 4.5.3 Billing . 23 4.6 MAINTENANCE REQUIREMENTS 23 4.7 CAPACITY, PERFORMANCE AND RELIABILITY REQUIREMENTS 23 5 OTHER NETWORK IMPACTS . 23 5.1 CUSTOMER PREMISES EQUIPMENT (CPE) . 23 5.2 SIGNAL TRANSFER POINT (STP). 23 5.3 SERVICE MANAGEMENT SYSTEM (SMS).

21、 23 5.4 OPERATIONS SYSTEMS . 23 5.5 OPERATOR SERVICES NETWORK ELEMENTS 23 5.6 NON-NP-CAPABLE NETWORK ELEMENTS. 23 5.7 WIRELESS SERVICE PROVIDERS 24 5.8 TOLL NETWORK INTERFACE . 24 ANNEX A NP-RESERVED AND PORTED OUT MARKINGS . 25 ATIS-1000004 TABLE OF FIGURES FIGURE 1: NETWORK CONFIGURATION FOR NP-RE

22、SERVED MARKING 13 FIGURE 2: CALL FLOW WITHOUT NP-RESERVED MARKING . 14 FIGURE 3: CALL FLOW WITH NP-RESERVED MARKING 14 FIGURE 4: PORTED OUT MARKING NETWORK CONFIGURATION . 15 FIGURE 5: CALL FLOW WITH PORTED OUT MARKING 16 FIGURE 6: DEFAULT ROUTING . 17 FIGURE 7: NP-RESERVED MARKING FOR NUMBER POOLIN

23、G 18 TABLE OF TABLES TABLE 1: CALL TREATMENTS 21 TABLE 2: SUGGESTED SETTINGS FOR NP-RESERVED AND PORTED OUT MARKINGS FOR GIVEN SCENARIOS . 26 TABLE 3: SUGGESTED SETTINGS FOR NP-RESERVED AND PORTED OUT MARKINGS FOR INTERCEPT AND AGING SCENARIOS. 29 iv Technical Requirements ATIS-1000004 Technical Req

24、uirements for Telecommunications Thousands Block Number Pooling Using Number Portability 1 SCOPE AND OVERVIEW 1.1 Scope This technical requirements document defines the Switching System, Number Portability Database (NPDB), and Number Portability Global Title Translation (NP GTT) requirements for Tho

25、usands Block Number Pooling1in Number Portability (NP) capable wireline networks. This uses the Location Routing Number (LRN) method for number portability. Thousands Block Number Pooling shares an NPA-NXX among carriers allocating numbers in blocks of one-thousand numbers with the same NPA-NXX-X. T

26、he pooling of numbers in blocks smaller than one-thousand (e.g., Individual Telephone Number Pooling) and the pooling of numbers outside a rate center are not addressed. 1.2 Overview Pooling of geographic numbers in a number portability environment is a number administration and assignment process,

27、which allocates numbering resources to a shared reservoir associated with a designated geographic area. This document addresses the pooling of numbers within an existing rate center within a geographic Number Plan Area (NPA). The numbering resource in the shared reservoir is made available in blocks

28、 of one-thousand numbers for assignment to competing service providers participating in number pooling for the purpose of providing services to customers in that area. The assignment of numbers to service providers in blocks of one-thousand (i.e. NPA-NXX-X) rather than the existing practice of assig

29、ning numbers in blocks of 10,000 (i.e. NPA-NXX) may improve the utilization of number resources. Further, a pool of numbers, if available to all providers serving a defined area, need only be large enough to accommodate the collective needs of those providers. Within a pooled environment, the total

30、number of NXX codes assigned could be fewer than if a full NXX code were assigned to each service provider; therefore numbering resources may last for a longer period of time. Existing network routing mechanisms are based upon the understanding that geographic numbers are assigned on a central offic

31、e (NXX) basis and associated with a specific switch, and the recognition that the network address to which the call must be routed is embedded in the first six digits (NPA-NXX) of the called number. The use of number pooling eliminates this association of NXX to end office and demands an alternative

32、 routing mechanism for call completion. Such a mechanism is provided with the infrastructure associated with the LRN method for NP. Therefore, in December 1997, the Industry Numbering Committee (INC) 1To avoid confusion with the acronym for number portability (NP), this document does not use an acro

33、nym for number pooling. ATIS-1000004 recommended that the industry proceed with thousands block number pooling supported by the LRN NP infrastructure. Accordingly, and most importantly, number pooling can only be implemented in NP-capable networks.2Subsequently, the Federal Communications Commission

34、 issued its Numbering Resource Optimization order, FCC 00-104, mandating the deployment of thousands block number pooling. The Order states “ we adopt the PSTC Committee Technical Requirements as the technical standard for a national thousands-block number pooling mechanism.” Similarly, non-call ass

35、ociated signaling messages associated with database (e.g., Line Information Database (LIDB) queries, or the processing of certain supplementary services, are traditionally routed using six digit analysis of a designated telephone number. Again, number pooling breaks the association of NPA-NXX with t

36、he required destination and demands more granular analysis. The mechanisms available with NP also provide this capability. Currently, call rating is derived from the geographic information embedded in the calling and called party numbers, specifically the first six digits of those numbers (the NPA-N

37、XX). In a number pooling environment, these rating mechanisms are still supported provided that the area of pooling - that is, the area in which numbers are assigned and shared among different service providers - is consistent with the established rate center boundaries, and that the NPA-NXX(s) assi

38、gned to the pool uniquely identify the rate center in which subscribers assigned numbers reside.3Thus, the same constraints that limit current implementations of NP to areas of portability within the rate center also limit current support for number pooling to areas of number pooling within a rate c

39、enter. When number pooling is implemented in a particular geographic area, NXXs are still assigned to a single service provider (code holder) in the Local Exchange Routing Guide (LERG), but blocks of one-thousand numbers are assigned to various service providers (block holders). The block holders th

40、en determine when to put (activate) their numbers into the Number Portability Administration Center (NPAC) Service Management System (SMS) and thus service providers NP routing databases (i.e., NPDBs). Number pooling, like number portability, may increase the number of NPA-NXX-Xs that must be opened

41、 on the switch. While this document does not specify a requirement on the minimum number of NPA-NXX-Xs that must be supported, it is recognized that all switch types will have some limitation. Some switches reach their limitation to accept additional thousands blocks earlier than others and, thus, t

42、he ability to receive additional thousands blocks for pooling may be restricted. 2Although switch based seven digit analysis and translation can conceivably be supported in many switches and could, therefore, be used to route calls in some pooled number environments, this capability is administrativ

43、ely burdensome and inefficient in its use of switch memory. Therefore, this document defines an NP-based approach for number pooling. 3The assignment of numbers to those subscribers who reside in the rate center to which a given NPA-NXX is assigned is a wireline service provider paradigm. It should

44、be recognized that wireless service providers typically are not constrained by this assignment procedure and may assign numbers to their subscribers from a given NPA-NXX even if those subscribers reside outside the rate center with which the NPA-NXX is associated. 6 ATIS-1000004 2 INTRODUCTION 2.1 N

45、etwork Prerequisites for Number Pooling This clause addresses network prerequisites that must be met for number pooling to function properly as defined in this document. 1) Number pooling, as defined in this document, requires functions defined in the following: ATIS-1000001, Number Portability Oper

46、ator Services Switching Systems. ATIS-1000002, Number Portability Switching Systems. ATIS-1000003, Number Portability Database and Global Title Translation. 2) All changes to GTT data that results in a GTT on greater than six digits in an NP GTT node must be initiated by an NPAC SMS download. When n

47、o NPAC information applies, default routing of GTT-routed Transaction Capabilities Application Part (TCAP) messages will be based on six digit defaults (e.g., for LIDB the 6-digit default is defined in the LIDB Access Routing Guide (LARG). A third data source for GTT data, such as block holder infor

48、mation from the LERG, should not be used, since this could drastically increase the risk of looping for GTT-routed Signaling System 7 (SS7) TCAP messages. 3) All NP GTT-routed messages (e.g., LIDB queries and messages for some supplementary services) for vacant and unassigned numbers should be route

49、d to the appropriate application system as specified in Network Prerequisite 2. 4) Call routing is generally done based on the 6-digit NPA-NXX of the Directory Number (DN) as defined in the LERG. Changes to call routing due to NP and Number Pooling will be initiated by an NPAC SMS download to the service providers NPDB, via the Local Service Management System (LSMS). 2.2 Assumptions 1) Number pooling can only be implemented in NP-capable networks. 2) The pooling of numbers is limited to the geographic area defined by e