1、 ATIS-0410003-0017 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 42 ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 2The Alliance for Telecommunication Industry Solutions (ATIS) is the leading technical pla
2、nning 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 E
3、xploratory Groups address emerging industry priorities. For more information, please visit ATIS 0410003-0017 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 F
4、orum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2010 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval
5、 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. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to pro
6、fessionals 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-0017
7、UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 3NO 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 F
8、ITNESS 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 CON
9、SEQUENTIAL 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 V42 4This issue of the Unified Ordering Model (UOM) Volume III Design provides the XML schemas that support the Access Service
10、Ordering Guidelines (ASOG) and the Unified Ordering Model Volume I Business Requirements for Version 42. Changes to this document have been made in support of the following issues: 3386, 3390 The following issues went into Final Closure; however they resulted in no impact to the contents of this doc
11、ument: 3336 (Withdrawn), 3378 (Withdrawn), 3379, 3388, 3389, 3391 Global Changes Change all ASOG 41 to ASOG 42; Version 41 to Version 42; Issue 16 to Issue 17. Change ATIS document number from ATIS-0410003-0016 to ATIS-0410003-0017. Update Issue Date. Other grammatical and spelling corrections that
12、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. SUMMARY OF CHANGES ASOG V42 5UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V42 Schema Issue # Element Name Description of Change UOM-BASE
13、All ASOG_VER_Type Changed the enumeration value from 41 to 42. UOM-BASE 3386 IPV4_Type Added TRANSPORTSA-005 metadata references to reflect the addition of IP_ADDRESS and SUBNET_MASK. UOM-BASE 3390 DSCP_Type Increased maxLength value from 6 to 12. UOM-ASR 3386 TRANSPORT Added a new element in the se
14、quence called IP_ADDRESS. UOM-ASR 3386 TRANSPORT Added a new element in the sequence called SUBNET_MASK. ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 6TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION 7 1.1 SCOPE .7 1.2 PURPOSE.7 1.3 APPLICATION.7 2
15、. STANDARDS/REFERENCES 8 2.1 ATIS REFERENCES8 2.2 OTHER STANDARDS.8 2.3 ACRONYMS9 3. DEFINITIONS10 4. OVERVIEW OF UOM-ASR VOLUME III.11 4.1 INTRODUCTION TO UOM.11 4.2 REQUIREMENTS OF THIS DOCUMENT.13 4.3 STRUCTURE OF THIS DOCUMENT .13 4.4 HOW TO USE THIS DOCUMENT14 5. REQUIREMENTS OVERVIEW15 6. ANAL
16、YSIS OVERVIEW.15 7. IMPLEMENTATION OVERVIEW.15 8. DESIGN (TECHNOLOGY INFORMATION MODEL)16 8.1 TML SCHEMAS.16 8.1.1. Conformance Statement to the tML Framework17 8.1.2 UOM-Base Schema.18 8.1.3 UOM-ASR Schema 180 8.1.4 UOM-ASRInquiry Schema.219 8.1.5 UOM-ASRNotify Schema.225 ATIS-0410003-0017 UOM-ASR
17、Volume III Issued September 24, 2010 Issue 17 for ASOG v42 71. 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 Servi
18、ce Request (UOM-ASR). The interface is 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 Sche
19、mas for conveying request, response, notification, 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
20、 tML Schemas presented in this document 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 s
21、pecific common types and elements that 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 V
22、olume II) by defining object classes, their 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 Volu
23、me II. The tML Schemas (namely UOM-ASR, UOM-ASRInquiry and UOM-ASRNotify) present the inquiry, service request, notification, acknowledgement, and exception response interactions in the access domain. ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 82. Standards/
24、References The following standards and industry guidelines provide supportive documentation to this document. 2.1 ATIS References ATIS-0404000-0042: Access Service Ordering Guidelines (ASOG), September 2010 ATIS-0404100-0042: Access Service Request (ASR) Mechanized Interface Specification Issue 31,
25、ASR Version 42, September 2010 ATIS-0404130-0011: 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-0017: Unified Ordering Model Access Service Request (UOM-ASR) Vol
26、ume I Business Requirements for an Electronic Ordering Interface, September 2010, Issue 17, ASOG Version 42 ATIS-0410002-0017: Unified Ordering Model Access Service Request (UOM-ASR) Volume II Analysis for ASOG Version 42, September 2010, Issue 17 ATIS-0300079 : tML Transport Profile, March 2006 Not
27、e: ATIS/OBF Documents can be ordered from OBF Manager, ATIS, 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 Teleco
28、mmunications Management Network, 2000 ITU-T M.3030: telecommunications 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 Cons
29、ortium (W3C) Recommendation, XML Schema Part 1: Structures, 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 availab
30、le from the American National Standards Institute, 11 West 42ndStreet, New York, NY 10036. ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 92.3 Acronyms ASO Access Service Ordering ASR Access Service Request ANSI American National Standards Institute ATIS Allianc
31、e for Telecommunications Industry Solutions GTDD Generic Telecom 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 q
32、ualify names in order to separate them from other names. Note: 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
33、belong to a particular namespace called a target namespace. A 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 relationship
34、s of their constituent parts: datatypes, elements and their content, 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 Compone
35、nt: 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, identity-
36、constraint definitions, model group definitions, notation declarations, annotations), and un-named components (model groups, particles, wildcards, and attribute uses). tML Schema: Constructs to constrain and document the meaning, usage and relationships of the constituent parts of tML instance docum
37、ents. tML Schemas are based on the W3C XML Schema Recommendation. tML Namespace: A collection of names, identified by a URI reference RFC2396, that is used in tML documents as element types and attributes UML: An OMG specification to provide system architects working on object analysis and design wi
38、th one consistent language for specifying, visualizing, constructing, and documenting the artifacts of software systems and for modeling of business processes ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 114. Overview of UOM-ASR Volume III 4.1 Introduction to
39、UOM The document, Unified Ordering Model Access Service Request Volume III Design, (UOM-ASR Volume III) is part of a set of documents that provides an end-to-end structured systems engineering approach to perform the design related to unified ordering via electronic interfaces. This document provide
40、s the design of the detailed business and analysis for an ordering model for the UOM interface. It describes the tML/XML Schemas with the intent that service providers and their vendors can use the tML/XML Schemas when exchanging data for an ASR application. Because of the level of complexities inhe
41、rent in such an electronic ordering model, a tML Framework Document (ITU-T M.3030) has been used as a guide to develop this volume. The intent of Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structured methodology. The scope of UOM encompasses
42、 business requirements, analysis, design, and implementation. Logically, these components are defined within the UOM in four volumes. UOM-ASR Volume I - Business Requirements This document describes the business requirements. This volume includes a high-level overview of the three primary processes
43、in ordering: pre-ordering, service request, and post-confirmation activities. It also includes more detailed information in the use cases and activity diagrams. Two appendices include the data dictionary and the functional data matrix. The UOM-ASR Volume I is focused on ordering for access services
44、only. As other services are added in the future, additional Volume I documents may be developed. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains the UOM-ASR Volume I document. UOM-ASR Volume II - Analysis This analysis document provides the logical view of the bus
45、iness requirements stated in Volume I. The primary sections include the information model, sequence diagrams, and behavior model. Both the informational and behavioral models are described using the Unified Modeling Language (UML). The UML provides the notation used within Volume II. Because of the
46、level of complexities inherent in such an electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop this Volume II. A traceability matrix is included in the appendix to map the details in Volume II to the Business Requirements. Some additional
47、requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic interexchange. Volume II is not specific to any particular technology or protocol. If additional Volume I documents are developed, this Volume II may need to be expanded to address
48、additional requirements. The OBF Ordering Solutions Committee, Access Service Ordering Subcommittee maintains UOM-ASR Volume II. UOM-ASR Volume III - Design The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the selecte
49、d implementation technology. The first technology selected was XML; therefore UOM-ASR Volume III includes appropriate XML schemas related to unified access ordering. This document does not specify a particular transport protocol as it is assumed that the trading partners will determine the appropriate transport protocol. It may be necessary to repeat the ATIS-0410003-0017 UOM-ASR Volume III Issued September 24, 2010 Issue 17 for ASOG v42 12Design Phase when more than one implementation technology is selected. The OBF O
