ATIS 0410003-0019-2011 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 44).pdf

1、 ATIS-0410003-0019 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 44 ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 2 The Alliance for Telecommunication Industry Solutions (ATIS) is the leading technical pl

2、anning 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

3、Exploratory Groups address emerging industry priorities. For more information, please visit ATIS 0410003-0019 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

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

5、l 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 pr

6、ofessionals 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-0019

7、 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 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

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

9、ONSEQUENTIAL 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 ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 4 TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION 5

10、 1.1 SCOPE . 5 1.2 PURPOSE. 5 1.3 APPLICATION . 5 2. STANDARDS/REFERENCES 6 2.1 ATIS REFERENCES . 6 2.2 OTHER STANDARDS . 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 H

11、OW TO USE THIS DOCUMENT . 12 5. REQUIREMENTS OVERVIEW 13 6. ANALYSIS OVERVIEW . 13 7. IMPLEMENTATION OVERVIEW . 13 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-ASRI

12、NQUIRY SCHEMA . 201 8.1.5 UOM-ASRNOTIFY SCHEMA 207 ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 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) st

13、andard that specifies an interface for the Unified Ordering Model Access Service 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 th

14、e TMN X-interface (M.3010) to support the UOM-ASR. This standard uses tML Schemas 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: Reques

15、t Response Notification Acknowledgement Exception Response 1.3 Application The 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-ASRNot

16、ify. The UOM-Base Schema defines all reusable domain specific and non-domain specific 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 excepti

17、on response functions are supported in the UOM (information model in UOM-ASR Volume 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

18、 access domain interactions of the information model described in UOM-ASR Volume II. The tML Schemas (namely UOM-ASR, UOM-ASRInquiry and UOM-ASRNotify) present the service request, inquiry, notification, acknowledgement, and exception response interactions in the access domain. ATIS-0410003-0019 UOM

19、-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 6 2. Standards/References The following standards and industry guidelines provide supportive documentation to this document. 2.1 ATIS References ATIS-0404000-0044: Access Service Ordering Guidelines (ASOG), September 2011 ATIS-0404100-0

20、044: Access Service Request (ASR) Mechanized Interface Specification Issue 33, ASR Version 44, September 2011 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

21、ATIS-0404110-0019: Unified Ordering Model Access Service Request (UOM-ASR) Volume I Business Requirements for an Electronic Ordering Interface, September 2011, Issue 19, ASOG Version 44 ATIS-0410002-0019: Unified Ordering Model Access Service Request (UOM-ASR) Volume II Analysis for ASOG Version 44,

22、 September 2011, Issue 19 ATIS-0300079 : tML Transport Profile, March 2006 Note: 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/o

23、bf/download.asp 2.2 Other Standards ITU-T Rec. M.3010: Principles for a Telecommunications 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

24、Markup Language (XML) 1.0 (Second Edition), 6 October 2000 World Wide Web Consortium (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

25、XML, 14 January 1999 Note: ITU-T Recommendations and ISO standards are available from the American National Standards Institute, 11 West 42ndStreet, New York, NY 10036. ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 7 2.3 Acronyms ASO Access Service Ordering ASR

26、 Access Service Request ANSI American National Standards Institute ATIS Alliance 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

27、documents as element types and attribute names. Namespaces are used in XML to qualify 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 co

28、llection (vocabulary) of type definitions and element declarations whose names 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

29、 these constructs to constrain and document the meaning, usage and relationships 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 instan

30、ce 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, Attri

31、bute declarations, Element declarations, attribute group definitions, identity-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

32、meaning, usage and relationships of the constituent parts of tML instance documents. 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 spec

33、ification to provide system architects working on object analysis and design with one consistent language for specifying, visualizing, constructing, and documenting the artifacts of software systems and for modeling of business processes ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011

34、 Issue 19 for ASOG v44 9 4. Overview of UOM-ASR Volume III 4.1 Introduction to 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 desi

35、gn related to unified ordering via electronic interfaces. This document provides 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 ex

36、changing data for an ASR application. Because of the level of complexities inherent 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 documen

37、tation using an end-to-end structured methodology. The scope of UOM encompasses 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 requireme

38、nts. This volume includes a high-level overview of the three primary processes 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 functiona

39、l data matrix. The UOM-ASR Volume I is focused on ordering for access services 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 V

40、olume II - Analysis This analysis document provides the logical view of the business 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 Langu

41、age (UML). The UML provides the notation used within Volume II. Because of the 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

42、 to map the details in Volume II to the Business Requirements. Some additional 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 Volum

43、e I documents are developed, this Volume II may need to be expanded to address 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

44、the Analysis Phase, is translated into the language appropriate for the selected 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 p

45、rotocol as it is assumed that the trading partners will determine ATIS-0410003-0019 UOM-ASR Volume III Issued September 23, 2011 Issue 19 for ASOG v44 10 the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The O

46、BF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. Volume III specifies the interface standard for the Unified Ordering Model for access services using the telecommunications Markup Language (an extension of XML), as defined in tML Framework. All Funct

47、ions in this standard are designed as optional features. The implementation of the functions (use cases) will be determined between individual customer and provider negotiations. UOM Volume IV Generic Implementation Guideline This document includes implementation specifications that must be addresse

48、d before the system specifications can be realized using the selected implementation technology. In addition, a sample Joint Implementation Agreement (JIA) may be included as an appendix for trading partners to use as a starting template. As with the Design Phase, the Implementation Phase may also h

49、ave to be repeated in order to provide support for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirements-Business Validation Rules2. Logical Analysis:-Informational Model-Behavioral Model-Sequence Diagrams-Class/Object Diagrams-State Diagrams-Traceability Matrix3. Technical Standard:-Technology Specific- Interface Specific