ATIS 0409002-0001-2005 Wireless to Wireline Number Portability Fax Form Instructions.pdf

《ATIS 0409002-0001-2005 Wireless to Wireline Number Portability Fax Form Instructions.pdf》由会员分享，可在线阅读，更多相关《ATIS 0409002-0001-2005 Wireless to Wireline Number Portability Fax Form Instructions.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0409002-0001 WIRELESS TO WIRELINE NUMBER PORTABILITY FAX FORM INSTRUCTIONS VERSION 1 DECEMBER 2, 2005 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

2、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. www.atis.org ATIS 0409002-0001 Wireless to Wireline Number Po

3、rtability Fax Form Instructions Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 The following statements must be posted with each link prov

4、iding access to this document and/or the associated form: Copyright 2005 by the Alliance for Telecommunications Industry Solutions. The “WIRELESS TO WIRELINE NUMBER PORTABILITY FAX FORM INSTRUCTIONS” was created by the ATIS Ordering and Billing Forum (OBF). ATIS permits OBF members and their custome

5、rs to use and distribute these documents. This document may not be reproduced by others in any form, in an electronic retrieval system or otherwise, without the prior written permission of ATIS. For information, contact ATIS at 202.628.6380. ATIS is online at: http:/www.atis.org. The information pro

6、vided in the “WIRELESS TO WIRELINE NUMBER PORTABILITY FAX FORM INSTRUCTIONS” is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable reg

7、ulations. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT

8、OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE WITH RESPECT TO ANY CLAIM, AND 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 RIS

9、K OF THE USER.” Printed in the United States of America 2 ATIS0409002-0001 Publish Date December 2, 2005 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 inte

10、rpret its contents in accordance with generally accepted 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

11、OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, 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

12、 BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND 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 TABLE OF CONT

13、ENTS 1. INTRODUCTION. 5 2. FAX FORM GUIDELINES . 5 3. DATA DICTIONARY 54 1. Introduction The purpose of this document is to define the operational requirements for the fax exchange of information needed for wireless to wireline porting. It explains the procedures for the completion of a Wireless Fax

14、 Form Port Request by a wireline carrier familiar with the Local Service Request (LSR) process. 2. Fax Form Guidelines This section contains information and requirements regarding the use of these fax forms to complete the Intercarrier Communications Process (ICP) between wireless service providers

15、and wireline service providers. In order to reduce incorrect interpretations of data, it is highly desirable that the population of data on the fax forms is by mechanical means as opposed to handwriting. If handwritten, all characters should be in upper case block style as shown on the sample fax fo

16、rms. If mechanically generated, all characters must be in upper case, 18 point, Courier New font. It is important to ensure that each character is contained entirely within the space allotted on the fax form. There is no requirement for the recipient of a fax to respond back with a confirmation rece

17、ipt. When processing requests via fax, the onus is on the New Service Provider (NSP) to ensure their faxed request has been received, processed and responded to in a written form by the Old Service Provider (OSP). 3. Data Dictionary The following section describes the data element specification and

18、usage for all data fields indicated on the fax port request. All fields presented in the data dictionary should be left justified with no trailing spaces or blanks, unless otherwise stated for a specific data element. Variable length fields (identified by a minimum and/or maximum length in the Valid

19、ation Description column) are initialized to an empty value. A non-populated field is represented as an empty value. These fax forms incorporate the following conventions for the population of form entries: Required The field must be populated in order for the port request to be considered valid. Op

20、tional The field may or may not be populated. Prohibited The field must not be populated. Conditional Population of this field is dependent upon the presence, absence, or combination of other data entries. 5 Justification Local service ordering forms utilize the following general instructions: Quant

21、ity fields are right justified with no leading zeros. Fields with text are left justified. Fields not following these justification rules are so noted within the context of the definition and usage statement. Valid Character Set Definitions Alpha (A) = A to Z Numeric (N) = 0 through 9 Alphanumeric (

22、AN) = A to Z and 0 through 9 Element Description Validation Description Form Section AGAUTH Agency Authorization Status - Indicates that the Customer (Carrier) is acting as an end users agent and has authorization on file Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Required Values: Alpha Va

23、lid Values: Y = Authorization on file 1 position A Local Service Request Administrative AUTHNM Authorization Name - Identifies the end user who signed the authorization Record: INITIAL NUMBER PORT REQUEST, SUP3 Conditions: Required Values: Alpha Format: FirstName MiddleInitial LastName Maximum of 60

24、 positions A Local Service Request Administrative BANO Billing Address Street Number - This field is intended to capture the street/house number of the billing address NOTE: Those wireless carriers who validate address information use billing address. (No service address exists in wireless). Record:

25、 INITIAL NUMBER PORT REQUEST, SUP3Conditions: Conditional Required if billing street address is used; optional for all other address types (PO Box, Rural Route, Military, Foreign, Rural Free Delivery, etc.). Values: Alphanumeric Maximum of 10 positions AN End User Information Location And Access 6 E

26、lement Description Validation Description Form Section BASN Billing Address Street Name - Identifies the street name of the end users billing address Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Required Values: Alphanumeric Examples: Lucerne Way Rural Route 30 P. O. Box 1146 Peachtree Rd Su

27、ite 200 Old National Hwy Room 10 Milton Lane Apt 2B Maximum of 60 positions AN End User Information Location And Access BCITY End User City - Identifies the city, village, township, etc. of the end users billing address Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Required Values: Alphanumer

28、ic Maximum of 35 positions AN End User Information End User Billing Details BCOUNTRY Country - Identifies the country of the end users billing address Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Optional Values: Alpha Examples: USA, CAN, GER Maximum of 3 positions A End User Information End

29、 User Billing Details BILLFIRSTNM Billing First Name - Identifies the first name of the person, office or company to whom the bill is rendered Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Conditional Required when the End User is an individual. Prohibited when the End User is a business, off

30、ice or company. Values: Alpha Example: Bill Maximum of 25 positions A End User Information End User Billing Details BILLLASTNM Billing Last Name - Identifies the last name of the person, or the name of the office or company to whom the bill is rendered Record: INITIAL NUMBER PORT REQUEST, SUP3Condit

31、ions: Required. Values: Alphanumeric Examples: Smith Sherrys House of Hair Maximum 25 positions AN End User Information End User Billing Details 7 Element Description Validation Description Form Section BSTATE End User State/Province - Identifies the abbreviation for the state or province to where t

32、he bill is renderedRecord: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Conditional Required when Country is USA, CAN or not populated, otherwise optional. Values: Alphanumeric, NULL When Country is USA, CAN or not populated, the Valid Values are the US Postal Abbreviations for the US States, US Ter

33、ritories and Canadian States/Provinces. (For more specific information, please refer to the US Postal Service Website.) 2 positions AN End User Information Location And Access BZIP Billing Zip Code - Identifies the ZIP code, ZIP code + extension or postal code to where the bill is rendered Record: I

34、NITIAL NUMBER PORT REQUEST, SUP3Conditions: Conditional Required when Country is USA, CAN or not populated, otherwise optional. Values: Alphanumeric Valid Values: When Country is USA, CAN or not populated, the valid format for Zip is either xxxxx-xxxx for US (with 5 characters being the minimum) or

35、xxxxxx for Canadian Maximum 10 positions AN xxxxx-xxxx for US xxxxxx for Canadian End User Information Location And Access CC Company Code - Identifies the exchange carrier initiating the transaction. Note 1: Valid Company Codes are available from NECA. Record: INITIAL NUMBER PORT REQUEST, SPR Condi

36、tions: Required; LSR Required when the CCNA field is CUS”, otherwise Optional NNSP field is has a dependency on this field when it is different than the CC field. Required when the REQTYP=B or C, NPT = D and NNSP entry is different than CC field Values: Alphanumeric Valid Values: Any valid OCN, SPID

37、 4 positions ANLocal Service Request Administrative 8 Element Description Validation Description Form Section CHC Coordinated Hot Cut - Identifies that the Customer (Carrier) is requesting near seamless cutover activity. Note 1: This field may require manual intervention and coordination between the

38、 Customer/Provider Record: INITIAL NUMBER PORT REQUEST, SUP2 OR SUP3 Conditions: Optional used if the NSP requires coordination of port request. On an INITIAL NUMBER PORT REQUEST, SUP2 or SUP3 the NSP can either not populate the CHC field or populate with Y. DFDT has two uses: 1. Indicates the windo

39、w for cutover time when CHC is NOT populated 2. Indicates the desired specific cutover time when CHC is populated The time will reflect the local time of the end users /senders location. Values: Alpha Valid Values: Y, or Not Populated Y = Hot Cut Requested by NSP Non Populated No Coordinated Hot Cut

40、 requested1 position A Local Service Request Administrative DATED Date of Agency Authorization - This field indicates the date that the port authorization was received Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Conditional Required when AGAUTH = Y, optional Values: Numeric Valid Values (Se

41、e US Standard): MM = 01 12 Two digit month (01-12) DD = 01 31 Two digit day (01-31) YYYY = 20xx (Four digit year 0000-9999) 8 positions N Local Service Request Administrative DDD Desired Due Date - Identifies the Customers (Carrier) desired due date Record: INITIAL NUMBER PORT REQUEST, SUP2 or SUP3

42、Conditions: Required Values: Alphanumeric Valid Values (See US Standard): MM = 01 12 Two digit month (01-12) DD = 01 31 Two digit day (01-31) YYYY = Four digit year (0000-9999) Examples: 03-22-1996 10 positions (including 2 hyphens) AN Local Service Request Administrative 9 Element Description Valid

43、ation Description Form Section DFDT Desired Frame Due Time - Identifies desired frame cutover time Record: INITIAL NUMBER PORT REQUEST, SUP2 or SUP3 Conditions: Conditional Required when the CHC field is populated. Note 1: A range of time is not permitted in this field Values: Alphanumeric Valid Val

44、ues: HH =Two digit hour (01-12) MM = Two digit minute (00-59) And AM or PM indicator LSOG NOTE: The time will reflect the local time of the end user location(s). (See D/TSENT below) Examples: 1015PM 6 positions AN Local Service Request Administrative D/TSENT Date and Time Sent - Identifies the date

45、and time the transaction is sent Note 1: The date and time populated in this field represents the time populated within the NSPs internal process. Note 2: The time value must be local to the location from which the transmission originates. Record: INITIAL NUMBER PORT REQUEST, SPR Conditions: Require

46、d Values: Alphanumeric Format: Date and time MM = 01 12 DD = 01 31 YYYY = 20xx HH = 01 12 MM = 00 59 and AM or PM US standard is as follows: Two digit month (01-12) Two digit day (01-31) Two digit century (00-99) Two digit year (00-99) Two digit hour (01-12) Two digit minute (00-59) AM or PM Example

47、: 05-22-1996-1115AM 17 positions AN Local Service Request Administrative 10 Element Description Validation Description Form Section EAN Existing Account Number - Identifies the end users existing account number Note 1: When porting from a wireless carrier to wireline this field represents the wirele

48、ss account number and not the wireless telephone number. Note 2: Account Number should be formatted as contiguous characters consisting solely of the digits 0 through 9 and the letters A through Z and a through z with no blanks Record: INITIAL NUMBER PORT REQUEST, SUP3 Conditions: Required Values: A

49、lphanumeric Examples: 987456A01 GSM8795263214MMS Maximum of 20 positions AN End User Information Bill EBILLNM End User Bill Name - Identifies the phone end user; Name repeats as part of an array Record: INITIAL NUMBER PORT REQUEST, SUP3Conditions: Optional Values: Alpha Maximum of 60 positions A End User Information Bill IMPCON Implementation Contact - Identifies the Customers (Carrier) representative or office responsible for co