1、 ATIS-1000001 NUMBER PORTABILITY OPERATOR SERVICES 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 stand
2、ards 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. NOTE - The users atten
3、tion is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or any patent rights in connection therewith. The patent holder has, however
4、, filed a statement of willingness to grant license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. ATIS-1000001, Number Portability Operator Services Switching Systems Is an ATIS
5、 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 Industry Solutions All r
6、ights 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 America. ATIS-1000001 Te
7、chnical Requirements for NUMBER PORTABILITY OPERATOR SERVICES SWITCHING SYSTEMS Secretariat Alliance for Telecommunications Industry Solutions Approved October, 2004 Abstract This document defines the Operator Services Switching Systems technical requirements for number portability (NP) using the lo
8、cation routing number (LRN) method. ATIS-1000001 ii FOREWORD This document defines the Operator Services Switching Systems technical requirements for number portability (NP) using the location routing number (LRN) method. The Alliance for Telecommunication Industry Solutions (ATIS) serves the public
9、 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
10、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
11、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
12、ring Plan (NANP) number from one serving switch in a network to another switch in the same or different circuit switched network. Other users can connect to the portable subscriber without any changes to their dialing procedures. Requirements provided in this document address number portability usin
13、g 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 service provider
14、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 unbundling. N
15、ormative annexes are considered a part of ATIS Technical Requirements. Informative annexes of ATIS Technical Requirements provide useful information, but do not contain requirements. Similarly, footnotes are informative. This Technical Requirements (TRQ) document was developed by PTSC in accordance
16、with ANSI and ATIS procedural guidelines and represents the consensus position of the formulating group. This document was processed and approved for submittal to ATIS. Committee approval of this specification does not necessarily imply that all committee members voted for its approval. ATIS guideli
17、nes 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 represents a
18、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 20005. The PT
19、SC.3 Subcommittee was responsible for the development of this document. Stuart Goldman PTSC.3 Chair & PTSC.3 Senior Technical Editor Wesley Downum, PTSC.3 Vice-Chair Brian Foster, PTSC.3 Editor ATIS-1000001 iii TABLE OF CONTENTS FOREWORD .II 1 SCOPE AND OVERVIEW . 1 1.1 SCOPE 1 1.2 PURPOSE 1 1.3 APP
20、LICATION 1 1.4 BACKGROUND 1 2 INTRODUCTION . 2 2.1 NETWORK PREREQUISITES FOR NUMBER PORTABILITY . 2 2.2 ASSUMPTIONS 3 2.3 ACRONYMS AND DEFINITIONS 3 2.3.1 Acronyms 3 2.3.2 Definitions 5 2.4 REFERENCES 6 2.4.1 Normative References. 6 2.4.2 INFORMATIVE REFERENCES 7 3 CUSTOMER PERSPECTIVE 7 3.1 END USE
21、R PERSPECTIVE . 7 3.2 SERVICE PROVIDER PERSPECTIVE . 7 3.3 SAMPLE CALL FLOWS. 8 3.3.1 0-CALL (STATION PAID BILLING). 8 3.3.2 Calling Card Call - LIDB Validation . 9 3.3.3 Out of Region Calling Card - LIDB Validation 11 3.3.4 Calling Card Call - LIDB Validation, Out of Region OSS . 12 3.3.5 Third Par
22、ty Number Billing - LIDB Validation 14 3.3.6 Collect Call - LIDB Validation. 15 3.3.7 Busy Line Verification, Voice-to-Voice Hand-off . 17 3.3.8 Busy Line Verification - Non-NP capable OSS 19 3.3.9 “Worst Case“ example - NP capable OSS 20 3.3.10 “Worst Case“ example - Non-NP capable OSS 27 4 NETWORK
23、 IMPACTS. 32 4.1 SECURITY ISSUES . 32 4.2 SIGNAL TRANSFER POINT (STP) . 32 4.3 NUMBER PORTABILITY DATABASE (NPDB) . 33 4.4 NP GLOBAL TITLE TRANSLATION (GTT) FUNCTION . 33 4.5 OUT OF REGION OSS 33 5 FEATURE REQUIREMENTS. 33 5.1 NP QUERY PROCESSING . 34 5.1.1 Queries. 34 5.1.1.1 BLV Queries. 35 5.1.2
24、Response Processing (Normal) 35 5.1.2.1 BLV Responses. 35 5.1.3 Response Processing (Abnormal). 36 5.1.3.1 Default Routing 36 5.1.3.2 Unexpected Parameters . 37 5.1.3.3 Unexpected Messages 37 5.1.3.4 Automatic Code Gapping (ACG) . 38 5.1.4 Generic Address Parameter (GAP) Generation and FCI Determina
25、tions . 38 5.2 SIGNALING AND PROTOCOL REQUIREMENTS . 39 5.2.1 Originating Switch to OSS Interfaces. 39 5.2.2 Signaling Formats 39 ATIS-1000001 iv 5.2.2.1 TCAP Formats . 39 5.2.2.1.1 Query Messages (OSS to NPDB). 39 5.2.2.1.2 Response Messages (NPDB to OSS) 40 5.2.2.1.3 LIDB Queries 40 5.2.2.2 ISUP S
26、ignaling Formats 40 5.2.2.3 OSS Signaling 42 5.2.2.4 Multiple applications . 44 5.2.3 Other Intra-Network Interfaces 44 5.3 HARDWARE INTERFACES REQUIREMENTS . 44 5.4 INTERACTIONS AND TRANSPARENCIES WITH OTHER FEATURES . 44 5.4.1 Advanced Service Platform (T1.667) Services Interactions . 44 5.5 OPERA
27、TIONS, ADMINISTRATION AND PROVISIONING REQUIREMENTS 45 5.5.1 Service Changes . 45 5.5.1.1 OSS Provisioning Modifications - NP 45 5.5.2 Measurements 47 5.5.3 Network Management. 47 5.5.4 AMA Recording 47 5.5.4.1 Calling Number 48 5.5.4.2 Called Number. 49 5.5.4.3 Billed Number 50 5.5.4.4 Party Identi
28、fier Population 51 5.5.4.5 AMA Access Records . 52 5.5.4.6 Operator Services CAMA. 52 5.5.4.7 NP AMA Module Code. 52 5.5.4.8 Rules for Busy and Unanswered Call Recording. 53 5.6 MAINTENANCE REQUIREMENTS 53 5.7 INITIALIZATION AND RECOVERY REQUIREMENTS 53 5.8 CAPACITY, PERFORMANCE AND RELIABILITY REQU
29、IREMENTS 53 TABLE OF FIGURES FIGURE 1: CALL COMPLETION CALL FLOW 0-CALL 8 FIGURE 2: CALLING CARD CALL LIDB VALIDATION . 9 FIGURE 3: OUT OF REGION CALLING CARD - LIDB VALIDATION . 11 FIGURE 4: CALLING CARD CALL LIDB VALIDATION, OUT OF REGION OSS. 13 FIGURE 5: THIRD PARTY NUMBER BILLING LIDB VALIDATIO
30、N . 14 FIGURE 6: COLLECT CALL LIDB VALIDATION. 16 FIGURE 7: BUSY LINE VERIFICATION, VOICE-TO-VOICE HAND-OFF. 18 FIGURE 8: BUSY LINE VERIFICATION - NON-NP CAPABLE OSS 19 FIGURE 9: WORST CASE SCENARIO - THIRD PARTY (AUTHORIZATION REQUIRED) - THREE DIFFERENT ZONES OF PORTABILITY. 22 FIGURE 10: WORST CA
31、SE SCENARIO - THIRD PARTY (AUTHORIZATION REQUIRED) - NON-NP CAPABLE OSS . 28 TECHNICAL REQUIREMENT ATIS-1000001 Technical Requirement for Telecommunications Number Portability Operator Services Switching Systems 1 1 SCOPE AND OVERVIEW 1.1 Scope This document defines technical requirements for number
32、 portability as they apply to operator services switching systems. It describes the network capability for handling operator services involving portable numbers. The network capability functions in conjunction with the capability described in ATIS-1000002, and ATIS-1000003. The operator services cal
33、l types (i.e., methods for reaching an operator) to which this document applies include Toll and Assistance (0-, 0+, 1+ screened, 00-, 1+ 800/888/etc., and international prefix equivalents), Listing Services (Directory Assistance - 411, (NPA) 555-1212), and Intercept Service (changed number, discont
34、inued service). This network capability, Operator Services with Portable Numbers (OSPN) as defined by the requirements in this document, is available for calls received with either Signaling System No. 7 (SS7) or Multi Frequency (MF) signaling. However, certain aspects of OSPN require SS7. This netw
35、ork capability applies to service provider portability with location portability within a rate center, including portability between wireline service providers and the impacts on the functions performed in the wireline network. This document only addresses facility based service providers. This netw
36、ork capability encompasses operator services provided in the wireline network as part of the wireline networks operator service. Requirements in this document apply to operator services switching systems. Network capabilities pertaining to database architecture, internal switch call processing, and
37、network operations and administration are beyond the scope of OSPN. The terms Number Portability (NP) and Local Number Portability (LNP) are used interchangeably within this document. 1.2 Purpose OSPN supports both routing and billing functions for portable numbers. The operator system may need to d
38、etermine the network location of a called party number for routing and the network location of one or more of the calling party, called party, and billing numbers for billing. When it is available, service provider information may reduce the need for network location information for billing purposes
39、. 1.3 Application OSPN supports the implementation of NP for operator services in the competitive local service environment. 1.4 Background This clause provides a brief reminder of some key elements of Operator Services and Number Portability (NP), and is intended to provide perspective on some of t
40、he elements to consider when ATIS-1000001 2 reading this document. Check the Acronyms and Definitions clauses in Clause 2.3 of this document for further assistance. NP affects the way numbers are translated and signaled, and it creates a need for additional information when they are used in billing
41、records. As a result, NP particularly affects Alternate Billing Services (ABS) and Busy Line Verification (BLV). ABS calls (e.g. Collect, Person-to-Person, Third Party Billed, Calling Card) are impacted because of the verifications required on the alternative billing information and the additional i
42、nformation required for billing (e.g. who is the service provider). BLV calls are impacted because of the special routing requirements of these calls. Historically, all Directory Numbers (DNs) in one NPA-NXX belonged to a single telephone switch. With the introduction of NP, individual DNs in one NP
43、A-NXX may be moved to a different telephone switch. This has tremendous implications for call routing, as the first six digits of a DN (i.e. the NPA-NXX) no longer uniquely identify the switch that serves that DN. Hence the concept of a Location Routing Number (LRN) was introduced. Each switch which
44、 hosts portable numbers has at least one ten-digit LRN assigned to it, which is used in routing a call to that switch. The actual dialed digits must also be signaled to allow the call to be completed. For ABS calls, there can be up to three different Directory Numbers (DNs) of interest: Calling Part
45、y Number (CgPN), Called Party Number (CdPN), and Billing Number (BN). There are three functions of these calls to consider: routing, billing, and verification. The Called Party Number is used to route a call. For ported DNs, the LRN of the terminating switch is inserted into the CdPN parameter, with
46、 the dialed digits saved in the Generic Address Parameter (GAP). The LRNs of all three numbers (CgPN, CdPN, BN) may be included in AMA billing records. The requested alternate billing can be verified by querying a Line Information Database (LIDB) or other validation database for information using an
47、y of the three numbers (e.g. validating a calling card, or checking if third number billing is permitted for a DN). These LIDBs are typically geographically dispersed, and do not contain data for all regions or all service providers. Each NP capable network element (switch, Signal Transfer Point (ST
48、P), Number Portability Database (NPDB), or Operator Services System (OSS) will maintain a list of NPA-NXXs which are considered portable, at least for its own zone of portability. An NPDB provides the LRNs for ported DNs. The correct LIDB for a DN is determined by ten-digit Global Title Translation,
49、 performed by a GTT function, which may be implemented on the NPDB, STP, or STP adjunct. 2 INTRODUCTION 2.1 Network Prerequisites for Number Portability The OSS requires the same network preparation for NP as required for other network switching nodes. In networks where pseudo NPAs have been used to support routing of BLV traffic via tandems, translations and routing will have to be changed. If the trunk between the OSS and tandem is an MF trunk, the tandem will need the actual (dialable) ten-digit target number in order to look up the LRN. If the trunk between the OSS and tand
