ATIS 0412003-1402-2014 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume III - Design.pdf

1、 ATIS-0412003-1402 Unified Ordering Model (UOM) Volume III - Design For Local Service Ordering Guidelines (LSOG) 2Q14 ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 2ATIS is a technical planning and standards development organization that is committed to rapidly developing and promoti

2、ng technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees, and its Incubator Solutio

3、ns Program. www.atis.org ATIS 0412003-1402 Unified Ordering Model (UOM) Volume III - Design Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Forum: Ordering and Billing Forum Local Service Ordering Subcommittee Published by ATIS 1200 G Street, NW, Suite

4、 500 Washington, DC 20005 Copyright 2014 by Alliance for Telecommunications 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 contac

5、t ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 3Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate

6、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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMA

7、TION 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. ATIS SHALL NOT BE LIABLE, BEYON

8、D 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 INFORMATION PROVIDED IN THIS DOCUMENT

9、IS AT THE RISK OF THE USER ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 4TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION . 5 SCOPE . 5 PURPOSE . 5 APPLICATION 5 2. NORMATIVE REFERENCES 5 STANDARDS . 5 OTHER REFERENCES . 5 3. DEFINITIONS . 6 4. ACRONYMS 7 5. OVERVIEW OF

10、UOM-LSR VOLUME III 8 INTRODUCTION TO UOM 8 UOM-LSR VOLUME I - BUSINESS PROCESS DEFINITION . 8 UOM VOLUME II - ANALYSIS 9 UOM-LSR VOLUME III - DESIGN 9 UOM GENERIC IMPLEMENTATION GUIDELINES (GIG) VOLUME IV - IMPLEMENTATION . 9 6. UOM REQUIREMENTS SUMMARY 10 SYSTEM REQUIREMENTS 10 SECURITY REQUIREMENT

11、S . 10 MESSAGING REQUIREMENTS 10 HOW TO USE THIS DOCUMENT 11 7. REQUIREMENTS OVERVIEW . 11 8. ANALYSIS OVERVIEW . 11 9. IMPLEMENTATION OVERVIEW 12 10. DESIGN (TECHNOLOGY INFORMATION MODEL) 12 TML SCHEMAS . 12 Conformance Statement to the tML Framework 12 Schema Structure . 13 UOM-Base Schema 14 UOM-

12、LSR Pre-Order Schema . 14 UOM-LSR Order Schemas 178 UOM-LSR Post-Order Schema 178 UOM-LSR Simple Port Service Request (SPSR) Base schema Error! Bookmark not defined. UOM-LSR Simple Port Service Request (SPSR) Order schema Error! Bookmark not defined. 11. APPENDIX A: CONTRIBUTORS TO UOM-LSR VOLUME II

13、I . 242 ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 51. Scope, Purpose and Field of Application 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 Local

14、 Service Request (UOM-LSR). The interface is specified using the telecommunications Markup Language (an extension of XML), as defined in tML Framework Document (ITU-T M.3030). Purpose This document defines tML Schemas to support the UOM-LSR. The schemas provide for the three broad functions associat

15、ed with Local Services Request Ordering; Pre-Ordering, Ordering, and Post-Ordering. Application The tML Schemas presented in this document are based on the packages in UOM, an information model described in UOM-LSR Volume II. The tML Schemas included in this document are: UOM-Base, UOM-LSR-Base, the

16、 set of schemas for LSR Pre-Order, the set of schemas for LSR Ordering, and the set of schemas for LSR Post-Ordering. 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 request, res

17、ponse, notification, acknowledgement, and exception response functions are supported in the UOM (information model in UOM-LSR Volume II) by defining object classes, their properties, and their relationships. While the UOM-LSR Volume II is the technology-independent specification of UOM, UOM-LSR Volu

18、me III is a technology-specific definition of the access domain interactions of the information model described in UOM-LSR Volume II. The tML Schemas present the inquiry, service request, notification, acknowledgement, and exception response interactions in the access domain. 2. Normative References

19、 The following standards and industry guidelines contain provisions that, through reference in this text, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on

20、 this American National Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Standards World Wide Web Consortium (W3C) Recommendation XML: eXtensible Markup Language (XML) 1.0 (Second Edition), 6 October 2000 World Wide Web Con

21、sortium (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 Other References ATIS0412002-1402: Unified Ordering Mode

22、l Local Service Request (UOM-LSR) Volume II Analysis for LSR Version 2Q14 ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 6Note: 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 f

23、orm is available on the ATIS web site at: http:/www.atis.org/obf/download.asp 3. Definitions Namespace: A conceptual collection of unique names identified by a URI or a URN reference IETF RFC2396; used in XML documents as element types and attribute names. Namespaces are used in XML to qualify names

24、 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 belong to a

25、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 relationships of their c

26、onstituent 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: The gene

27、ric 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-constraint d

28、efinitions, 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 documents. tML Sc

29、hemas 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 one consi

30、stent language for specifying, visualizing, constructing, and documenting the artifacts of software systems and for modeling of business processes ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 74. Acronyms ANSI American National Standards Institute ATIS Alliance for Telecommunication

31、s Industry Solutions GTDD Generic Telecom Data Dictionary HTTP(s) HyperText Transfer Protocol, Secure IETF Internet Engineering Task Force ISOP Interconnection Services Ordering and Provisioning ITU International Telecommunications Union LSR Local Service Request OAM&P Operations, Administration, Ma

32、intenance & Provisioning OBF Ordering and Billing Forum OMG Object Management Group RFC Request For Comment TMOC Telecom Management and Operations Committee tML telecommunications Markup Language TMN Telecommunications Management Network UML Unified Modeling Language UOM Unified Ordering Model URI U

33、niversal Record Identifier URL Universal Record Locator URN Universal Record Name W3C World Wide Web Consortium XML eXtensible Markup Language Acronyms for OBF data elements used in this document are defined in ATIS/OBF documents. ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 85. Ove

34、rview of UOM-LSR Volume III Introduction to UOM 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 compo

35、nents are defined within the UOM in four volumes depicted in the figure below. Process2. AnalysisUnified Model2. Logical Model- Class/Object Diagrams- Data Traceablity- Interaction Diagrams- State DiagramsVolume IVolume IIVolume IIIVolume IV3. Design 3. Information Model- Technology Information Mode

36、l4. Implementation 4. Implementation Guidelines- Technology Specifications- Implementation Profile1. Business Process . Definition 1. Business Requirements- High Level Use Cases- Data/Presentation Requirement- Business Validation Rules- Scenarios- Activity DiagramsLSOPLSOP LSOPLSOP/UOMASRUOM Process

37、 and Document DevelopmentUOM-LSR Volume I - Business Process Definition UOM-LSR Volume I provide an explanation of the business requirements and a conceptual overview of the solution. It defines “what” the user initially sees as the problem and “how” the user sees the business solution. The business

38、 requirements for LSR functionality are described in ATIS/OBF Local Service Ordering Guideline (LSOG). The OBF LSO Subcommittee maintains the LSOG documents. The LSOG constitutes UOM-LSR Volume I. It is separated into several practices that address specific business functions. The LSOG practices may

39、 be grouped into the following functional areas: Pre-Order, Service Order, and Post-Order. The Pre-Order practice describes the pre-order inquiry and response functions that may take place prior to the ordering process. The practice also defines each data element and contains both the common busines

40、s rules and the information regarding use of the pre-order functions within the practice. ATIS 0412003-1402 UOM-LSR Volume III Issued 6/30/14 LSOG 2Q14 9The Service Order practices describe the various forms used for the purpose of requesting local service. It includes field definitions, conventions

41、, descriptions, and various scenarios to outline the process for a local service request. The Post-Order practices outline the forms provided for local service responses and service order inquiries. UOM Volume II - Analysis This analysis document provides the logical view of the proposed solution to

42、 meet the needs of the business requirements stated in ATIS/OBF LSR process. The primary sections include the use case and sequence diagrams, and informational model. The informational models are described using the Unified Modeling Language (UML). The UML provides the notation used within Volume II

43、. Because of the level of complexities inherent in such an electronic ordering model, a unified modeling language tool has been used to develop this Volume II. A traceability matrix is included in Appendix A to map the details in Volume II to the Business Requirements defined in the LSOG. Some addit

44、ional requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic inter-exchange. 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 a

45、ddress additional requirements. The OBF LSO Subcommittee maintains the UOM-LSR Volume II. UOM-LSR Volume III - Design The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the selected implementation technologies. XML is t

46、he implementation technology that is currently supported. This document does not specify a particular 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

47、selected. The OBF LSO Subcommittee maintains the UOM-LSR Volume III for XML implementation UOM Generic Implementation Guidelines (GIG) Volume IV - Implementation This document includes implementation specifications that must be addressed before the system specifications can be realized using the selec