1、 ATIS-0409001-0500 Unified Ordering Model (UOM) Volume I Business Requirements Wireless Intercarrier Communications Interface Specification (WICIS) for Local Number Portability Version 5.0.0 Sunrise 5.0.0: June 6, 2010; 00:00:00 (ET) Sunset 4.0.0: February 13, 2011; 00:00:00 (ET) ATIS-0409001-0500 W
2、ICIS Version 5.0.0, Volume I Published 12/18/09 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 communications and related info
3、rmation 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 attention is called to the possibility that compl
4、iance 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, filed a statement of willingness to grant
5、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-0409001-0500 Wireless Intercarrier Communications Interface Specification Volume I Business Requirements, Version 5.0.
6、0 Is an ATIS standard developed by the Wireless Committee under the ATIS Ordering and Billing Forum (OBF). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2009 by Alliance for Telecommunications Industry Solutions All rights
7、 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. 2ATIS-0409001-0500 W
8、ICIS Version 5.0.0, Volume I Published 12/18/09 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted
9、engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATI
10、ON, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AN
11、D IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. 3 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 Cha
12、nge History Date Version Section Number Summary of changes February 2007 4.0.0 Initial UOM release Issue 2847 was the foundation for this new document. XML replaces the existing CORBA interface. As a result, the IDL methods have been replaced with SOAP operations. January 2009 5.0.0 5.2 Issue 3118:
13、Added a new ICP operation/message (#5) WPRR-Jeopardy. This message is submitted by the OSP (non-wireless) in response to a WPR or SPR to indicate that the port is in jeopardy of being completed. January 2009 5.0.0 5.2.1 Issue 3118: Added Jeopardy (step #16) on the Intercarrier Communication Process
14、flow Figure 2 and added Figure 4 to Wireline to Wireless Jeopardy Response. January 2009 5.0.0 5.2.1.1 Issue 3118: Added Jeopardy (steps #16, 32, 33, 34, and 35) to the Detail Description of Process Boxes. January 2009 5.0.0 5.2.1.2 Issue 3118: Added Jeopardy to Narrative for Process Flow January 20
15、09 5.0.0 6.18 Issue 3118: Added Jeopardy Use Case (#18) to WICIS Use Cases. January 2009 5.0.0 5.5 Issue 3207: Updated the Version Control rules to describe how sunrise and sunset dates are determined and to require support for the new WICIS Version on the sunrise date. October 2009 5.0.0 5.2.1.1, 5
16、.2.1.2 Issue 3344: The process flow diagram description and narrative have been modified to indicate an SPR1 may be sent by the NNSP after the NNSP has sent the WPR but prior to the ONSP acknowledging the WPR. October 2009 5.0.0 6.9 Issue 3344: The use case for sending an SPR1 prior to receiving a W
17、PRR has been modified to indicate an SPR1 being sent by the NNSP after a StoreStatus indicating success has been returned by the next ICP System for the WPR. October 2009 5.0.0 5.1.1, 5.1.2, 5.2 and 5.2.1.3 Issue 3346 Removed complex port references in sections 5.1.1, 5.1.2, 5.2 and 5.2.1.3. October
18、 2009 5.0.0 6.4 and 6.13 Issue 3349: Removed LNUM references. 4 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 Table of Contents TABLE OF FIGURES .7 1. WICIS OVERVIEW .8 1.1 INTRODUCTION 8 1.2. BACKGROUND .8 2. INTRODUCTION TO UOM .11 3. UML INTRODUCTION12 4. WICIS VOLUME I BUSIN
19、ESS REQUIREMENTS PROCESS .13 5. INTERCARRIER COMMUNICATIONS PROCESS AND SCENARIOS13 5.1. IMPACTS AND RESPONSIBILITIES.13 5.1.1. New Service Provider14 5.1.2. Old Service Provider .14 5.2. WIRELESS PORTING PROCESS.15 5.2.1. Wireless Porting Process Flow16 5.2.1.1. Detail Description of Process Boxes
20、.20 5.2.1.2. Narrative for Process Flow 23 5.2.1.3. Complex Ports .27 5.3. CLEARINGHOUSE.27 5.4. INDUSTRY ESTABLISHED RESPONSE TIMELINES 27 5.5. VERSION CONTROL .28 5.6. BACKWARD COMPATIBILITY29 5.7. IMPLEMENTATION SCHEDULE .30 6. WICIS USE CASES 31 6.1. SINGLE LINE PORT W/CONFIRM RESPONSE 31 6.2. S
21、INGLE LINE PORT W/DELAY THEN CONFIRM RESPONSE.32 6.3. SINGLE LINE PORT W/ RESOLUTION REQUIRED - MDN NOT ACTIVE FOLLOWED BY AN SPR133 6.4. SINGLE LINE PORT W/ RESOLUTION REQUIRED - MDN NOT FOUND - FOLLOWED BY A NEW REQUEST WITH CORRECTED TN 34 6.5. MULTI LINE PORT W/ RESOLUTION REQUIRED SSN INVALID F
22、OLLOWED BY AN SPR3 TO UPDATE THE CUSTOMER INFORMATION 35 6.6. MULTI LINE PORT W/ RESOLUTION REQUIRED ACCOUNT NUMBER INVALID- FOLLOWED BY AN SPR3 TO UPDATE THE CUSTOMER INFORMATION.36 6.7. SINGLE LINE PORT W/CONFIRM RESPONSE, FOLLOWED BY AN SPR2.37 6.8. SINGLE LINE PORT W/RESOLUTION REQUIRED RESPONSE
23、, FOLLOWED BY AN SPR3 W/CONFIRM RESPONSE, FOLLOWED BY AN SPR2 W/RESOLUTION REQUIRED RESPONSE, FOLLOWED BY AN SPR2 W/CONFIRM RESPONSE .38 6.9. SINGLE LINE PORT (WHICH HAS NOT RECEIVED A RESPONSE), FOLLOWED BY AN SPR1 TO CANCEL WITHOUT A CONFIRM RESPONSE39 6.10. MULTI LINE PORT W/RESOLUTION REQUIRED R
24、ESPONSE, FOLLOWED BY AN SPR3 40 6.11. SINGLE LINE PORT W/ RESOLUTION REQUIRED ACCOUNT NUMBER INVALID FOLLOWED BY AN SPR3 .41 6.12. SINGLE LINE PORT REQUEST INITIATED BY A RESELLER .42 6.13. MULTI LINE PORT WITH RESOLUTION REQUIRED MDN NOT ACTIVE FOLLOWED BY AN SPR2 .43 6.14. PORT REQUEST AND RESPONS
25、E DO NOT COMPLY WITH WICIS44 6.15. A SERVICE PROVIDER SENDS BROADCAST NOTIFICATION45 6.16. SINGLE LINE PORT FOLLOWED BY AN SPR146 6.17. CLEARINGHOUSE VENDOR SENDS A TEST MESSAGE QUERY TO TRADING PARTNERS.47 5 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 6.18. PORT REQUEST WITH
26、JEOPARDY RESPONSE 48 APPENDIX A: ACRONYMS.49 6 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 Table of Figures FIGURE 1-UOM WICIS PROCESS AND DOCUMENT DEVELOPMENT12 FIGURE 2-WIRELESS PORTING PROCESS .17 FIGURE 3-WIRELESS PORT CANCELLATION 18 FIGURE 4-WIRELINE TO WIRELESS JEOPARDY
27、 RESPONSE.19 7 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 1. WICIS Overview 1.1 Introduction The purpose of this document is to clearly define the business requirements for Wireless Intercarrier Communications Interface Specification (WICIS) for Local Number Portability. It i
28、s the first volume, in the set of four, defined within the Unified Ordering Model (UOM) process. WICIS was converted to UOM in order to align with technology changes and to better facilitate interoperability. The primary audience for this specification document is Commercial Mobile Radio Service (CM
29、RS) providers along with wireless equipment and service vendors who assist in the definition, development and deployment of Wireless Number Portability (WNP) solutions. It assumes the reader is familiar with WNP and the wireless telecommunications technologies. WICIS defines the operational requirem
30、ents and technical specifications for the exchange of information needed for the Intercarrier Communication Process (ICP). It represents a consensus developed by the members of the OBF Wireless Committee and is applicable to all CMRS carriers. Proprietary implementations are outside the scope of WIC
31、IS. WICIS defines number portability intercarrier communications processes for wireless providers. References to wireless interactions with a wireline provider through fields, values or processes within WICIS have been identified to allow for the potential synchronization with intermodal processes a
32、nd internal company system implementation efforts. WICIS is not intended to supersede any regulatory decision regarding number portability or intercarrier communications, but is intended to describe the process and specifications as it involves CMRS. 1.2. Background The Federal Communications Commis
33、sion (FCC) Number Portability First Order and Report and Further Notice on Proposed Rulemaking, CC Docket 95-116, dated July 2, 1996, mandated all CMRS providers provide Local Number Portability (LNP) by June 30, 1999. In January 1998, Cellular Telecommunications Industry Association (CTIA), sponsor
34、ed workshop on intercarrier communications recommended adopting a phased approach to Wireless Number Portability (WNP) intercarrier communications. Given the short compliance timeline, the first phase was to begin June 30, 1999 using a modified version of the wireline Local Service Request (LSR) for
35、ms and process. It was suggested that the second phase eliminate the wireline LSR method from the WNP processes for intercarrier communications. The workshop recommended that the 8 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 second phase consider an enhancement to the Number P
36、ortability Administration Center (NPAC) or an alternative method which would enable wireless carriers to exchange information about porting customers through a third party communication, rather than using direct carrier-to-carrier communications. Service providers wanted a process that would not neg
37、atively impact customers, was user friendly, low cost, focused on the necessities, and reduced porting conflicts. This single process should be implemented by all wireless service providers. This process was developed with consideration given to wireline issues thereby lending itself to adoption by
38、the wireline industry. Requirements that were considered are as follows: Product Related One simple and consistent process for integrated and stand-alone platforms Automated system Easy to modify and maintain Ability to set timers based on type and direction of port Help functions Reporting capabili
39、ties Timestamps and confirmation of receipt of transactions Ability to integrate into multiple systems such as billing, Point of Sale (POS) and Service Order Administration (SOA) systems Data Related Same data structure for all ports User defined parameters for record retention Ability to maintain h
40、istorical database of request and response transactions based on user defined parameters Ability to maintain Service Provider (SP) database When applicable, use the existing wireline reason codes When communication occurs between wireless carriers electronically, the date and time fields will be con
41、verted to Greenwich Mean Time (GMT). The offset of local time will be included in the electronic interface data structure. This will enable both service providers ICP systems to use the offset to display a local time. Communication Protocols Adopt standard protocols for communication between carrier
42、s Effective and efficient communication methodology including web access Encryption The CTIA Report on Wireless Number Portability was issued to the industry in August 1998. In that report, the LSR was defined as a method of communication between service providers. To support the unique requirements
43、 of the CMRS providers, a business case was developed to enable a wireless-to-wireless port to complete within 2 9 ATIS-0409001-0500 WICIS Version 5.0.0, Volume I Published 12/18/09 hours. The Intercarrier Communication Process (ICP) response was allotted 30 minutes. On February 8, 1999, the FCC gra
44、nted the CMRS industry an extension regarding their Local Number Portability obligations until November 24, 2002. The additional time granted to CMRS providers made possible the launch of WNP with an intercarrier communications process that adequately supported the industrys needs. A Wireless Interc
45、arrier Communication Sub Group was created to define and agree upon specific business requirements for an intercarrier communication process. The five alternatives previously established by the industry underwent an extensive analysis. Based on specific goals, they developed a process and specificat
46、ion that included a standardized data structure, common data elements, and communication protocols providing wireless carriers the best opportunity to complete the intercarrier communication process within a reasonable interval. The operational requirements and technical specifications for the wirel
47、ess industry solution are detailed in this document. It has been determined as the solution that provides the most benefits with the least cost or risk. While it was not a specific goal of the sub group to provide a wireline solution, it is believed that this solution would allow future incorporatio
48、n of wireline processes. On July 16, 2002, the FCC granted an additional extension for the implementation of WNP. The implementation date was set at November 24, 2003. Initially a significant number of data elements on a port order were being validated by wireless carriers backend systems, which res
49、ulted in high fallout. Subsequent to the implementation of WNP, some carriers agreed to reduce the number of data element validations in their backend system to reduce fallout and still minimize inadvertent ports. Although the backend validations were reduced, wireless carriers must still refer to the Data Dictionary for
