ATIS 0410003-0020-2012 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 45).pdf

1、 ATIS-0410003-0020 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 45 ATIS-0410003-0020 UOM-ASR Volume III Issued March 23, 2012 Issue 20 for ASOG v45 2 The Alliance for Telecommunication Industry Solutions (ATIS) is the leading technical planni

2、ng 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, Focus and Expl

3、oratory Groups address emerging industry priorities. For more information, please visit ATIS 0410003-0020 Unified Ordering Model (UOM) Volume III - Design Is an ATIS standard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Ordering and Billing Foru

4、m (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, in an electronic retrieval sy

5、stem 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. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to profes

6、sionals 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 regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0410003-0020 UOM

7、-ASR Volume III Issued March 23, 2012 Issue 20 for ASOG v45 3 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

8、 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, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUEN

9、TIAL 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 SUMMARY OF CHANGES ASOG V45 Page 1 of 4 This issue of the Unified Ordering Model (UOM) Volume III Design provides the XML schemas that support the Access Ser

10、vice Ordering Guidelines (ASOG) and the Unified Ordering Model Volume I Business Requirements for Version 45. Changes to this document have been made in support of the following issues: 3430, 3431, 3433, 3435 The following issues went into Final Closure; however they resulted in no impact to the con

11、tents of this document: 3432 (Withdrawn), 3434 Global Changes Change all ASOG 44 to ASOG 45; Version 44 to Version 45; Issue 19 to Issue 20. Change ATIS document number from ATIS-0410003-0019 to ATIS-0410003-0020. Update Issue Date. Sort the placement of some element and complexType definition struc

12、tures alphabetically. (Note: The sequence of elements within a structure are not changed.) Other grammatical and spelling corrections that do not impact the technical content of this document are not reflected in the Summary of Changes. Table of Contents Updated to reflect document re-pagination. SU

13、MMARY OF CHANGES ASOG V45 Page 2 of 4 UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V45 Schema Issue # Element Name Description of Change UOM-BASE UOM-BASE All ASOG_VER_Type Changed the enumeration value from 44 to 45. UOM-BASE CleanUp ASR_REMARKS_Type Renamed this simpleType to Remarks186_Type.

14、UOM-BASE CleanUp CNR_REMARKS_Type Renamed this simpleType to Remarks225_Type. UOM-BASE CleanUp REMARKS_Type Renamed this simpleType to Remarks124_Type. UOM-BASE 3430 BUM_Type Added this new simpleType (maxLength=1) with metadata references for the new BUM (TRANSPORTSA-005, ACI-007 and EUSA-013) elem

15、ent. UOM-BASE 3431 OTC_Type Added a metadata reference for the new OTC (EVC-016) element. UOM-BASE 3433 BI_Type Added this new simpleType (maxLength=1) with metadata references for the new BI (TRANSPORTSA-005, ACI-007 and EUSA-013) element. UOM-BASE 3433 Profile_Type Changed the maxLength value from

16、 25 to 30. UOM-BASE 3435 ACT_Type Added a metadata reference for the new VACT (EVC-016) element. UOM-ASR UOM-ASR CleanUp ADMIN Changed the existing ASR_REMARKS element to utilize Remarks186_Type (renamed from ASR_REMARKS_Type). UOM-ASR CleanUp ARI Changed the existing REMARKS element to utilize Rema

17、rks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp EOD Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp EUSA_SVC_DETAILS Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp EVC

18、Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp FGA_SVC_DETAILS Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp MSL Changed the existing REMARKS element to utilize Remarks124_Typ

19、e (renamed from REMARKS_Type). UOM-ASR CleanUp RING_SVC_DETAILS Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). SUMMARY OF CHANGES ASOG V45 Page 3 of 4 UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V45 Schema Issue # Element Name Description of Change

20、UOM-ASR CleanUp SACNXX Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp TQ Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp TRANSPORT Changed the existing REMARKS element to utiliz

21、e Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp TRUNK_SVC_DETAILS Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanUp VC Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR CleanU

22、p WAL Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASR 3430 ACI Added the BUM element in the sequence. UOM-ASR 3430 EUSA_SVC_DETAILS Added the BUM element in the sequence. UOM-ASR 3430 TRANSPORT Added the BUM element in the sequence. UOM-ASR 3431 U

23、NI_MAPPING Added the OTC element in the sequence. UOM-ASR 3433 ACI Added the BI element in the sequence. UOM-ASR 3433 ACI Rearranged the sequence of elements, moving the following elements: DIVCKT, DIVPON UOM-ASR 3433 EUSA_SVC_DETAILS Added the BI element in the sequence. UOM-ASR 3433 EUSA_SVC_DETAI

24、LS Rearranged the sequence of elements, moving the following elements: ES, LAG_ID UOM-ASR 3433 TRANSPORT Added the BI element in the sequence. UOM-ASR 3433 TRANSPORT Rearranged the sequence of elements, moving the following elements: LAG_ID, DIVCKT, DIVPON UOM-ASR 3435 CEVLAN_MAPPING Created this ne

25、w complexType to associate the new VACT element with the existing CE_VLAN reference. UOM-ASR 3435 UNI_MAPPING Changed the existing CE_VLAN reference (014 occurrences) to a new CEVLAN_MAPPING reference (010 occurrences), and moved this new reference to immediately precede the existing LREF_MAPPING re

26、ference. SUMMARY OF CHANGES ASOG V45 Page 4 of 4 UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V45 Schema Issue # Element Name Description of Change UOM-ASRInquiry UOM-ASRInquiry CleanUp ADDR_LIST Removed minOccurs=“0“ from the ADDR element in the sequence. (Changes the ADDR element from “optiona

27、l” to “required” when ADDR_LIST is provided.) UOM-ASRNotify UOM-ASRNotify CleanUp CN Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASRNotify CleanUp CNR Changed the existing REMARKS element to utilize Remarks225_Type (renamed from CNR_REMARKS_Type).

28、 UOM-ASRNotify CleanUp DLR_ADMIN Changed the existing REMARKS element to utilize Remarks186_Type (renamed from ASR_REMARKS_Type). UOM-ASRNotify CleanUp WATS_OPEN_BILLING Changed the existing REMARKS element to utilize Remarks124_Type (renamed from REMARKS_Type). UOM-ASRNotify 3435 EVC Reduced the CE

29、_VLAN “maxOccurs” attribute from 14 to 10. ATIS-0410003-0020 UOM-ASR Volume III Issued March 23, 2012 Issue 20 for ASOG v45 4 TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION 5 1.1 SCOPE . 5 1.2 PURPOSE . 5 1.3 APPLICATION . 5 2. STANDARDS/REFERENCES 6 2.1 ATIS REFERENCES 6 2.2 OTHER STA

30、NDARDS . 6 2.3 ACRONYMS 7 3. DEFINITIONS 8 4. OVERVIEW OF UOM-ASR VOLUME III . 9 4.1 INTRODUCTION TO UOM . 9 4.2 REQUIREMENTS OF THIS DOCUMENT . 11 4.3 STRUCTURE OF THIS DOCUMENT 11 4.4 HOW TO USE THIS DOCUMENT 12 5. REQUIREMENTS OVERVIEW 13 6. ANALYSIS OVERVIEW . 13 7. IMPLEMENTATION OVERVIEW . 13

31、8. DESIGN (TECHNOLOGY INFORMATION MODEL) 14 8.1 TML SCHEMAS . 14 8.1.1 CONFORMANCE STATEMENT TO THE TML FRAMEWORK . 15 8.1.2 UOM-BASE SCHEMA 16 8.1.3 UOM-ASR SCHEMA . 167 8.1.4 UOM-ASRINQUIRY SCHEMA . 202 8.1.5 UOM-ASRNOTIFY SCHEMA . 208 ATIS-0410003-0020 UOM-ASR Volume III Issued March 23, 2012 Iss

32、ue 20 for ASOG v45 5 1. Scope, Purpose and Field of Application 1.1 Scope The scope of this specification is to develop an Alliance for Telecommunications Industry Solutions (ATIS) standard that specifies an interface for the Unified Ordering Model Access Service Request (UOM-ASR). The interface is

33、specified using the telecommunications Markup Language (an extension of XML), as defined in tML Framework Document (ITU-T M.3030). 1.2 Purpose This standard defines tML Schemas for the TMN X-interface (M.3010) to support the UOM-ASR. This standard uses tML Schemas for conveying request, response, no

34、tification, acknowledgement, and exception response information across an interactive interface. This standard allows access service customers to do the following interactions: Request Response Notification Acknowledgement Exception Response 1.3 Application The tML Schemas presented in this document

35、 are based on the packages in UOM, an information model described in UOM-ASR Volume II. The tML Schemas included in this document are: UOM-Base, UOM-ASR, UOM-ASRInquiry and UOM-ASRNotify. The UOM-Base Schema defines all reusable domain specific and non-domain specific common types and elements that

36、are used in tML Schemas for various UOM applications. The first application is UOM-ASR as described in this document. The request, response, notification, acknowledgement, and exception response functions are supported in the UOM (information model in UOM-ASR Volume II) by defining object classes, t

37、heir properties, and their relationships. While the UOM-ASR Volume II is the technology-independent specification of UOM, UOM-ASR Volume III is a technology-specific definition of the access domain interactions of the information model described in UOM-ASR Volume II. The tML Schemas (namely UOM-ASR,

38、 UOM-ASRInquiry and UOM-ASRNotify) present the service request, inquiry, notification, acknowledgement, and exception response interactions in the access domain. ATIS-0410003-0020 UOM-ASR Volume III Issued March 23, 2012 Issue 20 for ASOG v45 6 2. Standards/References The following standards and ind

39、ustry guidelines provide supportive documentation to this document. 2.1 ATIS References ATIS-0404000-0045: Access Service Ordering Guidelines (ASOG), March 2012 ATIS-0404100-0045: Access Service Request (ASR) Mechanized Interface Specification Issue 34, ASR Version 45, March 2012 ATIS-0404130-0011:

40、Design Layout Report Guidelines for Access Service Issue 11, September 2008 ATIS-0404131-0006: Design Layout Report Mechanized Interface Specification Issue 6, March 2003 ATIS-0404110-0020: Unified Ordering Model Access Service Request (UOM-ASR) Volume I Business Requirements for an Electronic Order

41、ing Interface, March 2012, Issue 20, ASOG Version 45 ATIS-0410002-0020: Unified Ordering Model Access Service Request (UOM-ASR) Volume II Analysis for ASOG Version 45, March 2012, Issue 20 ATIS-0300079 : tML Transport Profile, March 2006 Note: ATIS/OBF Documents can be ordered from OBF Manager, ATIS

42、, 1200 G Street N.W., Suite 500, Washington, DC 20005. A complete OBF document catalog and ordering form is available on the ATIS web site at: http:/www.atis.org/obf/download.asp 2.2 Other Standards ITU-T Rec. M.3010: Principles for a Telecommunications Management Network, 2000 ITU-T M.3030: telecom

43、munications Markup Language (tML) Framework, 2002 ITU-T Rec. M.3400: TMN Management Functions, 2000 World Wide Web Consortium (W3C) Recommendation XML: eXtensible Markup Language (XML) 1.0 (Second Edition), 6 October 2000 World Wide Web Consortium (W3C) Recommendation, XML Schema Part 1: Structures,

44、 2 May 2001 World Wide Web Consortium (W3C) Recommendation, XML Schema Part 2: Datatypes, 2 May 2001 World Wide Web Consortium (W3C) Recommendation, Namespaces in XML, 14 January 1999 Note: ITU-T Recommendations and ISO standards are available from the American National Standards Institute, 11 West

45、42ndStreet, New York, NY 10036. ATIS-0410003-0020 UOM-ASR Volume III Issued March 23, 2012 Issue 20 for ASOG v45 7 2.3 Acronyms ASO Access Service Ordering ASR Access Service Request ANSI American National Standards Institute ATIS Alliance for Telecommunications Industry Solutions GTDD Generic Telec

46、om Data Dictionary HTTP(s) HyperText Transfer Protocol, Secure IETF Internet Engineering Task Force ITU International Telecommunications Union OAM used in XML documents as element types and attribute names. Namespaces are used in XML to qualify names in order to separate them from other names. Note:

47、 A URI has a similar format to a URL. It is not always possible to resolve a URI to find an instance of an XML schema. Schema: A set of schema components. A collection (vocabulary) of type definitions and element declarations whose names belong to a particular namespace called a target namespace. A

48、schema defines the allowable contents of a class of XML documents. The purpose of a schema is to define and describe a class of XML instance documents by using these constructs to constrain and document the meaning, usage and relationships of their constituent parts: datatypes, elements and their co

49、ntent, attributes and their values, entities and their contents, and notations. A class of documents refers to all possible permutations of structure in instance documents that will still conform to the rules of the schema. Schema Component: The generic term for the building blocks that comprise the abstract data model of the schema. There are 13 kinds of schema components defined: named components (Simple type definitions, Complex type definitions, Attribute declarations, Element declarations, attribute group definitions, ide