ATIS 0404100-0045-2012 Access Service Request (ASR) Mechanized Interface Specifications (Issue 34 ASR Version 45).pdf

1、 ATIS-0404100-0045 Access Service Request (ASR) Mechanized Interface Specifications Issue 34 ASR Version 45 September 2012 ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 The Alliance for Telecommunication Industry Solutions (ATIS) is the leading t

2、echnical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees. In addition, numerous Incubators,

3、 Focus and Exploratory Groups address emerging industry priorities. For more information, please visit ATIS 0404100-0045 Access Service Request (ASR) Mechanized Interface Specifications Is an ATIS standard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the

4、 ATIS Ordering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2012 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form

5、, 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 . Limited Exception for “Customized” Forms. In recognition of the business needs and processes Implemented N/A by companies through

6、out the industry, ATIS, on behalf of the OBF, grants the following limited exception to the copyright policy given above. The forms contained within this document, once “Customized,” may be reproduced, distributed and used by an individual or company provided that the following legend is placed on a

7、ll “Customized” forms: ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 “This form/screen is based upon the Ordering and Billing Forums (OBF) industry consensus approved guidelines, found in the Access Service Ordering Guidelines (ASOG) document. Th

8、e ASOG may be obtained by contacting the Alliance for Telecommunications Industry Solutions (ATIS) at 1-800-387-2199 or: http:/www.atis.org/docstore/default.aspx” For purposes of this limited exception, the term “Customized” means, the modification, by a company, of an ASOG form to be issued to a tr

9、ading partner to make it company specific by, for example, adding a company logo, graying-out optional fields not required by that specific issuing company, and converting into an electronic format/screen. This limited exception does not affect the ASOG document itself which remains copyrighted and

10、may not be reproduced in whole or part. Telcordia Technologies, Inc. was formerly known as Bell Communications Research, Inc. or Bellcore. Portions of this document, previously published by Bellcore, may still reflect the former name as it was embedded in the documentation under a prior license from

11、 the owners of the BELL trademark, which license has now expired. The use of this name does not suggest that Telcordia Technologies has licensed the names BELL, Bell Communications Research, or Bellcore for new uses or that the owners of the BELL trademark sponsor, endorse or are affiliated with Tel

12、cordia Technologies or its products. Printed in the United States of America. 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 accor

13、dance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 NO REPRESENTATION OR WAR

14、RANTY 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 OF INTELLECTUAL PROPERTY RIGHTS. A

15、TIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT 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 INFORMAT

16、ION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0045 Access Service Request (ASR) Mechanized Interface Specifications Issue 34, ASR Version 4

17、5 Summary ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 SUMMARY OF CHANGES This issue of the Mechanized Interf

18、ace Specifications provides the details to support the mechanization implementation of the following OBF issues: Issue Numbers 3430, 3431, 3433, 3435 The following OBF Issues went into Final Closure; however, they have no impact on mechanization on the record layouts/rules defined within this docume

19、nt: Issue Numbers 3432 (Wthd), 3434 Section 1: No changes were made to this section Section 2: The following existing record types were modified with ASOG 45: REC TYP = J END USER SPECIAL ACCESS Inserted new field (BUM) at line #34 replacing Filler (Issue 3430) Expanded existing field (PROFE) at lin

20、e #59 (Issue 3433) Expanded existing field (PROFI) at line #60 (Issue 3433) Inserted new field (BI) at line #61 (Issue 3433) Changed data area length from 749 to 760 Changed number of fields from 60 to 61 REC TYP = P TRANSPORT Inserted new field (BUM) at line #19 replacing Filler (Issue 3430) Expand

21、ed existing field (PROFE) at line #52 (Issue 3433) Expanded existing field (PROFI) at line #53 (Issue 3433) Inserted new field (BI) at line #54 (Issue 3433) Changed data area length from 686 to 697 Changed number of fields from 53 to 54 REC TYP = C ADDITIONAL CIRCUIT INFORMATION Expanded existing fi

22、eld (PROFE) at line #49 (Issue 3433) Expanded existing field (PROFI) at line #50 (Issue 3433) Inserted new field (BI) at line #51 (Issue 3433) Inserted new field (BUM) at line #52 (Issue 3430) Changed data area length from 611 to 623 Changed number of fields from 50 to 52 ATIS-0404100-0045 Effective

23、 September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 REC TYP = F47A ETHERNET VIRTUAL CONNECTION Change existing field (CEVLAN) at line #24 to an array and renamed to CEVLAN DATA (Issue 3435) Changed number of occurrences of CEVLAN from 14 to 10 Inserted new field (VACT) into the

24、array Changed start position of existing fields (RUID, FILLER, SVLAN IND, SVLAN and R/L) at lines #25 - 29 Inserted new field (OTC) at line #30 (Issue 3431) using 4-bytes from existing Filler field Changed length of Reserved Filler field at line #31 from 44 to 62 Renumbered lines 30 through 34 to 31

25、 through 35 Changed number of fields from 34 to 35 Section 3: The following existing record type was modified with ASOG 45: REC TYP = X VIRTUAL CONNECTION / ETHERNET VIRTUAL CONNECTION CONFIRMATION Changed number of occurrences of CEVLAN field at line #21 from 14 to 10 (Issue 3435) Changed start pos

26、ition of existing fields (SVLAN, EVCID, EVCORD and EVCCKR) at lines #22 - 25 Changed data area length from 399 to 367 Section 4: No changes were made to this section Section 5: No changes were made to this section Section 6: Added new Sections 6.2.1 (PROFE), 6.2.2 (PROFI) and 6.2.3 (CEVLAN) to expla

27、in the conversion of embedded base data due to the length change or deletion of the specified fields. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0045 Access Service Request (ASR) Mechanized Inte

28、rface Specifications Issue 34, ASR Version 45 Section 1 General ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012

29、MECHANIZED INTERFACE SPECIFICATIONS SECTION 1 TABLE OF CONTENTS 1. GENERAL 1-1 1.1 MECHANIZED INTERFACE OVERVIEW . 1-1 1.2 RECORD LAYOUT AND FILE STRUCTURE 1-3 1.2.1 CONTROL DATA 1-4 1.3 TRANSMISSION PROCESSING 1-7 1.3.1 Customer Provider . 1-7 1.3.2 Provider Customer . 1-7 ATIS-0404100-0045 Effecti

30、ve September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 1-1 1. GENERAL This document describes the rules that govern the mechanized transmission of data between entities ordering and providing access services. This document supports the Access Service Ordering Guidelines Industry

31、Support Interface (ASOG Document) which describes the industry agreed upon guidelines for the ordering of access services. The ASR Mechanized Interface Specifications contains file structures, rules for mechanized transmission and acceptance and confirmation of data as necessitated by the ASR. It al

32、so provides error conditions for systems that support the provisioning of Access Services. In an effort to insure that all possible customers and providers of Access Services are addressed in all issues and documentation maintained by or on behalf of the Ordering the specific components of each file

33、; the rules governing provider/customer transmission of the request; error conditions; and the criteria for data formation generic to the request. This document further defines those operative guidelines that the provider/customer systems utilize. Figure 1-1 identifies the files, which may be transm

34、itted between provider and customer. The transmission times are negotiated between provider and customer. 1. The customer transmits access order requests via a bulk transfer file. This file, referred to as the REQUEST FILE, is described in Section 2.0. 2. The REQUEST FILE is loaded into the provider

35、 system. 3. An input response file is created by the provider and is transmitted to the customer. This file, referred to as the RESPONSE FILE, is described in Section 3.0. 4. Records accepted into the provider database from the REQUEST FILE are processed. 5. In addition to the response file, the pro

36、vider system creates and transmits the following files: ERROR FILE CONFIRMATION (FOC) FILE SERVICE REQUEST CONFIRMATION (SRC) FILE PROVIDER CORRECTION (PC) FILE CLARIFICATION/NOTIFICATION REQUEST (C/NR) FILE These files are described in Section 3.0. ATIS-0404100-0045 Effective September 15, 2012 Iss

37、ued March 23, 2012 Implemented September 15, 2012 1-2 Figure 1-1. ASR Provider/Customer INTERFACE (1) FOC = Firm Order Confirmation (2) SRC = Service Request Confirmation - For companies supporting the 4 - Step process as defined in the Access Service Ordering Guidelines (ASOG) (3) PC = Provider Cor

38、rection (4) C/NR = Clarification/Notification Request CUSTOMERORDERPROCESSOR2. LOADVALIDATION4. PROCESSING1. REQUEST FILE(ASR RECORDS)3. RESPONSE FILES(acks / rejects)ERRORSRC(2)PC (3)C/NR (4)CUSTOMERPROVIDERFOC (1)ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 2012 Implemented Sept

39、ember 15, 2012 1-3 1.2 RECORD LAYOUT AND FILE STRUCTURE Each file contains fixed format, fixed length records padded to 1200 bytes. The structure of each file is illustrated in Figure 1-2. The data type for all fields is character. CONTROL HEADER PAD TO 1200 CONTROL ACCESS ORDER INFO PAD CONTROL ACC

40、ESS ORDER INFO PAD - - - CONTROL INFO PAD Figure 1-2. Structure of Transfer Files The first record in each file must be the Header Record that identifies the type of file being transmitted and the originator. When a files Header Record is in error, the entire file is rejected. Following the Header R

41、ecord, each file contains a specific set of records that convey the information for the access request. When no Application Records exist for a file, a Header Record must be transmitted for that file with 0 (zero) in the count field. ATIS-0404100-0045 Effective September 15, 2012 Issued March 23, 20

42、12 Implemented September 15, 2012 1-4 1.2.1 CONTROL DATA All data records have an initial control area (in the first 48 bytes or the first 100 bytes, depending on the record type) that enables a system to identify, process, and load the respective records into its database. Table 1-1 lists the field

43、s that are considered Control Data; table 1-2 provides the banking scheme that is associated with the REC_ID control data field; and table 1-3 provides the incrementing scheme for the extension of REC_ID. Table 1-1 Control Data Field Descriptions Field Definition Description REC_TYP Record Type A on

44、e-character field that identifies the particular record being processed. Invalid information in this field may cause the record or request to be rejected from the loading process. Record Type of F and R require an additional data element REC_ID, which is described below. Valid values for this field

45、may be found in table 2-2 for the forward feed records and in section 3.7 for the reverse feed records. REC_MODE Record Mode A one-character field that identifies the purpose of the request. Invalid information in this field may cause the record or request to be rejected from the loading process. RE

46、C_MODEs may not be intermixed - all records within the request must contain the same REC_MODE value. Valid entries in this field include the following: I = Initial Request (Forward Feed) A value of I indicates that the request is being submitted for the first time and must be used when the request h

47、as never been sent. If an initial request was rejected and all records associated with the request were also rejected, the records can be resubmitted with an I or C value. However, if the Admin Record (REC_TYP = S) on the initial request was accepted, then all records associated with this request mu

48、st be resubmitted with a REC_MODE of C. C = Change Request (Forward Feed) R = Response (Reverse Feed) X = Resend (Forward Feed) A value of X indicates that the request was previously sent and should exist in the providers database but the provider has asked for a resend of the request. ATIS-0404100-

49、0045 Effective September 15, 2012 Issued March 23, 2012 Implemented September 15, 2012 1-5 Field Definition Description REC_ID REC_CODE REC_EXT Record Identifier Record Code Record Extension A three-character code, applicable to the F and R series records that further identifies the record. Invalid information in this field may cause the record or request to be rejected from the loading process. The Record Code is the first two characters of the REC_ID. It is a two-cha