ATIS 0410003-0031-2017 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 56).pdf

1、 ATIS-0410003-0031 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 56 ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 2As a leading technology and solutions development organization, the Alliance for Telecomm

2、unications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services,

3、 device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, so

4、ftware toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initi

5、ative, a member of and major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0410003-0031 Unified Ordering Model (UOM) Volume III - Design Is an ATIS st

6、andard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Ordering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2017 by Alliance for Telecommunicati

7、ons Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, 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 . Printed in the United States

8、 of America. ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 3Notice 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

9、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 OR CON

10、FORMS 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 BY AT

11、IS 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 ATIS-0410003-0031 UOM-

12、ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 4Table Of Contents TABLE OF CONTENTS 4 1 SCOPE, PURPOSE, 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: A URI has a similar format

13、 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 schema defines the allowabl

14、e contents of a class of XML documents. The purpose of a schema is to define and ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 8describe a class of XML instance documents by using these constructs to constrain and document the meaning, usage and relationships o

15、f 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 Component:

16、 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-con

17、straint 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 document

18、s. 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 with

19、one consistent language for specifying, visualizing, constructing, and documenting the artifacts of software systems and for modeling of business processes 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

20、 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 provides the design of the detailed business and analysis for an ordering model for the UOM interf

21、ace. 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 inherent in such an electronic ordering model, a tML Framework Document (ITU-T M.3030) has been

22、 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 business requirements, analysis, design, and implementation. Logically, these components a

23、re 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 in ordering: pre-ordering, service request, and post-confirmation activities. It also inclu

24、des 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 only. As other services are added in the future, additional Volume I documents may be devel

25、oped. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains the UOM-ASR Volume I document. ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 9ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 10UOM-AS

26、R Volume 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 La

27、nguage (UML). UOM-ASR Volume II utilizes UML for descriptive purposes and in some instances may not strictly adhere to existing UML specifications. The UML provides the notation used within Volume II. Because of the level of complexities inherent in such an electronic ordering model, unified modelin

28、g language tools (RationalRose and MyEclipse) have been used to develop Volume II. 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.

29、 If additional Volume I documents are developed, 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

30、), created in 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 particul

31、ar transport protocol as it is assumed that the trading partners will determine the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maint

32、ains 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 Functions in this standard are designed as optional features. The implementatio

33、n 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 addressed before the system specifications can be realized using the selected impl

34、ementation 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 have to be repeated in order to provide support for multiple technologies.

35、The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 11Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-D

36、ata/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 Specification4. Implementation Guidelines-Design Choice Sug

37、gestions-Implementation ProfileOBF 1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document DevelopmentFigure 1 - UOM ASR Process and Document Development 4.2 Requirements of this document The following requirements have be

38、en taken into account by the Ordering Solutions Committee/Access Service Ordering Subcommittee in the development of UOM-ASR Volume III: UOM-ASR Volume III should be technology-specific and tML is chosen to be the technology to present the syntax of information definition. Therefore, the tML Schemas

39、 defined for the UOM-ASR should conform to the tML Framework Document (ITU-T M.3030). UOM-ASR Volume III tML Schemas for the Design phase of the UOM-ASR project should reflect the current analysis described in UOM-ASR Volume II (that reflects the requirements in UOM-ASR Volume I). UOM-ASR Volume III

40、 should be backward compatible with UOM-ASR Volume I and UOM-ASR Volume II. UOM-ASR Volume III should be generic, flexible, and have reusability. UOM-ASR Volume III edits in the tML Schemas are minimized to the maximum data length and a minimum subset of required fields. Other validation rules and p

41、rocesses are generally left to the customer/provider back-end systems. ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 12 UOM-ASR Volume III will contain tag names not to exceed 20 characters in length and will be in upper case format to conform with the current

42、OBF guidelines. UOM-ASR Volume III does not convey licensing right to non-COMMON LANGUAGE licensees to use the COMMON LANGUAGE1code sets identified throughout the UOM-ASR Volume III document in their internal operations. Where COMMON LANGUAGE is provided, its intended use by non-COMMON LANGUAGE lice

43、nsees is limited. Allowable uses will be specified by the COMMON LANGUAGE licensee, per their COMMON LANGUAGE contract. 4.3 Structure of this document The remainder of the document consists of the following sections: Sections 5, 6 and 7 provide references to the documents that define the requirement

44、s, analysis, and implementation specifications for the UOM-ASR application. Section 8 consists of tML Schemas: o UOM-Base Schema, that defines all reusable domain specific and non-domain specific common types and elements that are used in tML Schemas for various UOM applications, and o UOM-ASR, UOM-

45、ASRInquiry, UOM-ASRMEC and UOM-ASRNotify that present the service request, inquiry, notification, acknowledgement, and exception response interactions in the access domain. 4.4 How to use this document This document should be used as a source to facilitate interoperability between trading partners o

46、n the TMN X interface using the UOM-ASR application. The document provides tML Schemas that enable such interoperability by enabling interchange of data between trading partners. The document serves as the repository for trading partners to find the UOM-ASR related tML Schemas. In addition, the resp

47、onsible group of the OBF should process the maintenance of the tML Schemas in this document as revisions of the document. 5 Requirements Overview The requirements process of UOM-ASR Volume III is defined in the UOM-ASR Volume I document. Please see UOM-ASR Volume I for ASR 55 dated March 2017 (effec

48、tive September 2017) for the requirements. 1COMMON LANGUAGE is a registered trademark and CLEI, CLLI, CLFI and CLCI are trademarks of Telcordia Technologies. ATIS-0410003-0031 UOM-ASR Volume III Issued September 22, 2017 Issue 31 for ASOG v56 136 Analysis Overview The analysis process of UOM-ASR Vol

49、ume III is defined in the UOM-ASR Volume II document. Please see UOM-ASR Volume II, Issue 29, dated September 2016 (effective March 2017) for the analysis. 7 Implementation Overview The implementation process of UOM-ASR Volume III is defined in the UOM-ASR Volume IV document. Please see UOM-ASR Volume IV for the implementation. 8 Design (Technology Information Model) The design process of UOM-ASR Volume III is based upon the analysis process described in the UOM-ASR Volume II that further reflects the requirements provided in UOM-ASR Volume I. The design