1、 ATIS-1000002 NUMBER PORTABILITY SWITCHING SYSTEMS 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 standards for the commu
2、nications 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-1000002, Number Portability Switchi
3、ng Systems 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 by Alliance for Telecommunications Ind
4、ustry 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 . Printed in the United States of Ame
5、rica. ATIS-1000002 Technical Requirements for NUMBER PORTABILITY SWITCHING SYSTEMS Secretariat Alliance for Telecommunications Industry Solutions Approved October, 2004 Abstract This document defines the Switching Systems technical requirements for the number portability (NP) using the location rout
6、ing number (LRN) method. ATIS-1000002 ii FOREWORD This document defines the Switching Systems technical requirements for the number portability (NP) using the location routing number (LRN) method. The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved underst
7、anding 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 consideration in other North
8、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 other standards organizations
9、, 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 Numbering Plan (NANP) number f
10、rom one serving switch in a network to another switch in the same or different circuit switched network while retaining their same NANP number. Other users can connect to the portable subscriber without any changes to their dialing procedures. Requirements provided in this document address number po
11、rtability 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 provides the requirements for ser
12、vice 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 thousand block number pooling (see ATIS-1000004, Thousand Block Number Pooling Using Number Portability), resale or u
13、nbundling. 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 rather auxiliary to the specification. Similarly, footnotes are informative. AN
14、SI guidelines specify 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 rep
15、resents a goal 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, 1200 G Street NW, Suite 500, Washington, DC 200
16、05. The PTSC.3 Subcommittee was responsible for the development of this document. ATIS-1000002 iii TABLE OF CONTENTS FOREWORD .II 1 SCOPE AND OVERVIEW . 1 2 INTRODUCTION . 1 2.1 NETWORK PREREQUISITES FOR NUMBER PORTABILITY . 1 2.2 ASSUMPTIONS 2 2.3 ACRONYMS AND DEFINITIONS 3 2.3.1 Acronyms 3 2.3.2 D
17、efinitions 4 2.4 REFERENCES 6 2.4.1 Normative References. 6 2.4.2 Informative References. 6 3 USER PERSPECTIVE 7 3.1 END USER PERSPECTIVE (HUMAN INTERFACE) . 7 3.1.1 NP Network Capability Overview 8 3.2 SERVICE PROVIDER PERSPECTIVE . 9 3.2.1 Operational User Perspective 10 3.2.2 Operational Function
18、s . 10 3.2.2.1 Provisioning of NP Routing Tables 10 3.2.2.2 Provisioning and Discontinuance of Service . 10 3.3 CALL FLOWS 10 4 NETWORK IMPACTS. 25 4.1 SECURITY ISSUES . 25 4.2 SIGNAL TRANSFER POINT (STP) . 25 4.3 NUMBER PORTABILITY DATABASE (NPDB) . 25 4.4 LOCAL SERVICE MANAGEMENT SYSTEM (LSMS). 25
19、 4.5 OPERATIONS SYSTEMS IMPACTS . 25 4.6 OPERATOR SERVICES NETWORK ELEMENTS 25 4.7 CUSTOMER PREMISES EQUIPMENT (CPE) REQUIREMENTS OR IMPACTS. 25 4.8 WIRELESS SERVICE PROVIDERS 26 4.9 TOLL NETWORK INTERFACE . 26 4.9.1 Originating LATA. 26 4.9.2 Terminating LATA 26 4.10 Interactions with Non-NP Capabl
20、e Switches 26 5 FEATURE REQUIREMENTS. 26 5.1 CALL PROCESSING REQUIREMENTS. 26 5.1.1 NP Trigger Detection and Processing 30 5.1.1.1 NP Query . 30 5.1.1.2 Trigger Response Processing. 34 5.1.1.2.1 Routing Following the NP Query 35 5.1.1.2.2 NP Trigger Impact on Switch-based Call Redirection Informatio
21、n. 36 5.1.1.2.3 NP Trigger Default Routing 36 5.1.2 Generic Address Parameter (GAP) Generation and FCI Determinations . 36 5.2 SIGNALING AND PROTOCOL REQUIREMENTS . 38 5.2.1 Subscriber/Switch Interfaces 38 5.2.2 Switch/Switch Interfaces. 38 5.2.2.1 Signaling Formats 38 5.2.2.1.1 TCAP Formats . 38 5.
22、2.2.1.2 ISUP Signaling Formats 39 5.2.2.2 Switch without the Ported Subscriber 43 5.2.2.3 Intermediate Switch . 45 ATIS-1000002 iv 5.2.2.4 Recipient Switch. 49 5.2.3 Other Intra-Network Interfaces 53 5.3 HARDWARE INTERFACES REQUIREMENTS . 53 5.4 FEATURE INTERACTIONS. 53 5.4.1 T1.667 Services Interac
23、tions 53 5.4.1.1 T1.667 Next Event List Interactions. 54 5.4.1.2 T1.667 Serial Triggering Interactions . 54 5.4.1.3 Trigger Precedence 54 5.4.2 Attendant Features . 55 5.4.3 AUTOMATIC RECALL (AR). 55 5.4.4 Automatic Callback (AC) . 56 5.4.5 Call Forwarding. 57 5.4.6 Emergency (911) Services 57 5.4.7
24、 Message Waiting Indicator Control and Notification (MWN) 57 5.4.8 Multiway Calling/Flexible Calling Modular Feature. 58 5.4.9 ISDN. 58 5.4.10 OA NP QUERY AT IXC SWITCH 22 FIGURE 13: IXC-ROUTED CALL; NP QUERY AT ORIGINATING LEC SWITCH; IXC ACCEPTS NP INFORMATION 23 FIGURE 14: IXC-ROUTED CALL; IXC IG
25、NORES NP INFORMATION . 24 FIGURE 15: NP ROUTING TABLES 30 TABLE OF TABLES TABLE 1 FORWARD CALL INDICATORS . 39 TABLE 2 PORTED NUMBER GENERIC ADDRESS PARAMETER . 39 TABLE 3 JIP FORMAT. 40 TABLE 4 ORIGINATING SWITCH SIGNALING 43 TABLE 5 INTERMEDIATE SWITCH SIGNALING 46 TABLE 6 RECIPIENT SWITCH SIGNALI
26、NG. 50 TABLE 7 TRANSITION MECHANISM. 63 TABLE 8 PRECEDENCE REQUIREMENTS FOR SOURCE OF NUMBER PORTABILITY INFORMATION . 74 TABLE 9 RECORDING EXAMPLES 75 TABLE 10 CNA RECORD TRUNK GROUP SIGNALING TYPE. 94 TABLE 11 ORIGINATING NPA however, if the B or D channels are carrying packet data, the channels h
27、ave packet addresses, which are not portable. Requirements provided in this document address number portability using the LRN obtained from a centralized database to identify the recipient switch when numbers are ported. This document addresses the necessary requirements for service provider and loc
28、ation portability within a rate center. This document does not address number portability for subscribers with directory numbers that are also used for packet switched data. This technical requirements document does not fully address the billing issues associated with identifying multiple service pr
29、oviders on the same switch (no service provider line attribute), especially when the number moves from one service provider to another on the same switch. This document does not address the issues related to porting subscribers out of a non-NP capable switch. This document does not address any addit
30、ional requirements for porting between wireless networks, nor requirements for porting between wireless and wireline networks. For requirements related to porting between wireless networks, see TIA/EIA-41-D-97, T1.713, T1.711, T1.708, and TIA-756-A. The wireless switches follow the same network inte
31、rface (i.e., signaling the LRN) as wireline switches in accordance with the signaling standards defined in T1.660. 2 INTRODUCTION 2.1 Network Prerequisites for Number Portability This clause addresses network prerequisites that must be met for NP to function properly as defined in this document. Eac
32、h end office switch supporting number portability shall have at least one NPA-NXX that is “homed” to the switch (assigned in the Local Exchange Routing Guide (LERG). This NPA-NXX may be an existing NPA-NXX or newly assigned NPA-NXX. Violation of this network prerequisite will preclude the ability to
33、 use 6-digit routing to reach the serving switch. ATIS-1000002 2 2.2 Assumptions 1. Existing intra-switch features are not expanded to support subscribers on different switches if a subscriber access is moved from one switch to another. For example, intraswitch centrex groups can only be maintained
34、when the entire group of subscribers is served by the same switch. 2. Only Directory Numbers (DNs) associated with circuit-switched voice or data calls are portable. The porting of packet addresses is not supported by the NP capability. For example, DNs assigned to ISDN B-channels carrying either vo
35、ice or circuit-switched data can be ported; however, if the B or D channels are carrying packet data, the channels have packet addresses, which are not portable. 3. NP queries are the responsibility of the N-1 network. Upon receiving a call which has not had an NP query already performed (and in the
36、 absence of active ACG controls), an N-1 network will perform an NP query for the call, or will arrange for an NP query to be performed for the call. Queries may be performed in the originating LEC, by prior agreement between the LEC and the N-1 network. 4. Only one NPA-NXX is needed for the first 6
37、-digits of an LRN per Local Access Transport Area (LATA) to identify the switch. 5. Ported numbers that become vacant will be returned to the donor switch. 6. Translation Type 11 has been defined for the “Internetwork NP Query/Response“ application group. Therefore, this TT value can be provisioned
38、for NP queries as distinct from other T1.667or pre-IN (IN/1) queries. 7. Operator-destined calls will not be queried by the originating LEC and the call will be routed to the appropriate operator service without NP modification. 8. LRNs may also be DNs assigned to customers and these DNs may also be
39、 ported. 9. NP Triggers are not placed on Service Codes (e.g., 411) or Service Access Codes (e.g., 800). 10. Number Portability will not be “flash cut” into a network(s). 11. End-user rating and billing under NP will be unaffected by calls which transit over MF facilities. 12. Billing changes to sup
40、port NP will be transparent to end-user(s). 13. An end-user bill for a given call may be processed on a single AMA record. 14. Multiple rate centers may be served by the same switch. 15. A capability to bill for performing an NP query will be available to service providers. However, all of this func
41、tionality may not be provided by switch AMA recording. The Number Portability Database (NPDB) may also record peg counts for NP queries in an appropriate billing format. 16. Existing T1.667 or pre-IN (IN/1) procedures apply for Automatic Code Gapping (ACG) controls for NP queries. 17. Handling of ca
42、lls to blocked NXXs (e.g., 976) will continue to be an originating line restriction and should be blocked before the NP query is hit. 18. The rate center of a DN is determined by the NPA-NXX of the DN. Determination of rate center assignment is not part of switch-based functionality. 19. An NPA-NXX
43、used as a JIP is a LERG-assigned code on the switch. ATIS-1000002 3 2.3 Acronyms and Definitions 2.3.1 Acronyms AC Automatic Callback ACG Automatic Code Gapping AMA Automatic Message Accounting ANI Automatic Number Identification (a.k.a. Billing Number) ANSI American National Standard Institute AR A
44、utomatic Recall AT Access Tandem BAF Bellcore AMA Format CAC Carrier Access Code CAMA Centralized Automatic Message Accounting CdPN Called Party Number CDR Call Detail Record CgPN Calling Party Number CPE Customer Premises Equipment CSDC Circuit Switched Data Calls DID Direct Inward Dialing DN Direc
45、tory Number EO End Office FCI Forward Call Indicator GAP Generic Address Parameter GTT Global Title Translation IAM Initial Address Message IC Interexchange Carrier IN Intelligent Network INC International Interexchange Carrier ISDN Integrated Services Digital Network ISUP ISDN User PartIXC Interexc
46、hange Carrier JIP Jurisdiction Information Parameter LATA Local Access Transport Area LEC Local Exchange Carrier LERG Local Exchange Routing Guide LIDB Line Information Database LNP Local Number Portability LRN Location Routing Number MDR Message Detail Recording MF Multi Frequency signaling MWI Mes
47、sage Waiting Indicator MWN Message Waiting Indicator Control and Notification NANP North American Numbering Plan ATIS-1000002 4 NP Number Portability NPA Numbering Plan Area (i.e., A-B-C digits of NANP (ABC-DEF-GHIJ) NPAC Number Portability Administration Center NPDB Number Portability Database NXX
48、Central Office Code (i.e., D-E-F digits of NANP (ABC-DEF-GHIJ) OAM Operations, Administration and Maintenance OCN Original Called Number OHD Off-Hook Delay OLHB Outgoing Line History Block OS Operations Systems PIC Pre-subscribed Interexchange Carrier PRE-IN (IN/1) Pre-Intelligent Network (Telcordia
49、 Technologies TR-NWT-000533) RSU Remote Switching Unit SCCP Signaling Connection Control Part SCP Service Control Point SDS Specific_Digit_String SLE Screen List Editing SMS Service Management System SOAC Service Order Analysis and Control SPID Service Provider Identification SS7 Signaling System 7 SSP Service Switching Point STP Signal Transfer Point TAT Termination Attempt Trigger TCAP Transaction Capabilities Application Part WATS Wide-Area Telephone Service 2.3.2 Definitions 2.3.2.1 Automatic Code Gapping: Network management controls imposed on the switch by an SCP or NPDB applic
