ATIS 0412003-0803-2008 Unified Ordering Model Local Service Ordering Guidelines Volume III - Design (LSOG 13).pdf

《ATIS 0412003-0803-2008 Unified Ordering Model Local Service Ordering Guidelines Volume III - Design (LSOG 13).pdf》由会员分享，可在线阅读，更多相关《ATIS 0412003-0803-2008 Unified Ordering Model Local Service Ordering Guidelines Volume III - Design (LSOG 13).pdf（236页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0412003-0803 Unified Ordering Model (UOM) Volume III - Design For Local Service Ordering Guidelines (LSOG) 3Q08 ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 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-0803 Unified Ordering Model (UOM) Volume III - Design Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum UMA UOM-LSR Published by ATIS 1200 G Street, NW, Suite 500 Washingt

4、on, DC 20005 Copyright 2008 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 contact ATIS at 202

5、.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 3Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of exp

6、erience 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 INFORMATION IS TECHN

7、ICALLY 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, BEYOND THE AMOUNT

8、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 IS AT THE RIS

9、K OF THE USER ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 4TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION .5 SCOPE.5 PURPOSE.5 APPLICATION5 2. NORMATIVE REFERENCES 5 STANDARDS .5 OTHER REFERENCES.5 3. DEFINITIONS.6 4. ACRONYMS7 5. OVERVIEW OF UOM-LSR VOLUME III8 INTRO

10、DUCTION TO UOM8 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 SUMMARY10 SYSTEM REQUIREMENTS 10 SECURITY REQUIREMENTS .10 MESSAGING REQUIREMENTS10

11、HOW TO USE THIS DOCUMENT 11 7. REQUIREMENTS OVERVIEW.11 8. ANALYSIS OVERVIEW .11 9. IMPLEMENTATION OVERVIEW12 10. DESIGN (TECHNOLOGY INFORMATION MODEL) 12 TML SCHEMAS.12 Conformance Statement to the tML Framework12 Schema Structure.13 UOM-Base Schema14 UOM-LSR Pre-Order Schema.151 UOM-LSR Order Sche

12、mas 176 UOM-LSR Post-Order Schema221 UOM-LSR Simple Port Service Request (SPSR) Base schema230 UOM-LSR Simple Port Service Request (SPSR) Order schema234 11. APPENDIX A: CONTRIBUTORS TO UOM-LSR VOLUME III.236 ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 51. Scope, Purpose and Field

13、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 Service Request (UOM-LSR). The interface is specified using the telecommunications Markup Language

14、 (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 associated with Local Services Request Ordering; Pre-Ordering, Ordering, and Post-Ordering. Application The

15、 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 set of schemas for LSR Pre-Order, the set of schemas for LSR Ordering, and the set of schemas for

16、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, response, notification, acknowledgement, and exception response functions are supported in the UOM (in

17、formation 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 Volume III is a technology-specific definition of the access domain interactions of the information mod

18、el 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 The following standards and industry guidelines contain provisions that, through reference in this

19、 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 this American National Standard are encouraged to investigate the possibility of applying the most

20、 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 Consortium (W3C) Recommendation, XML Schema Part 1: Structures, 2 May 2001 World Wide Web Consortium (

21、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-0803: Unified Ordering Model Local Service Request (UOM-LSR) Volume II Analysis for LSR Version 3Q08 ATIS 0412003-0803 UOM-LSR

22、 Volume III Issued 9/30/08 LSOG 3Q08 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 form is available on the ATIS web site at: http:/www.atis.org/obf/download.asp 3. Definitions Namesp

23、ace: 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 in order to separate them from other names. Note: A URI has a similar format to a URL. It is not a

24、lways 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 allowable contents of a class

25、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 content, attributes and their values, entities and

26、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

27、kinds of schema components defined: named components (Simple type definitions, Complex type definitions, Attribute declarations, Element declarations, attribute group definitions, identity-constraint definitions, model group definitions, notation declarations, annotations), and un-named components (

28、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 Schemas are based on the W3C XML Schema Recommendation. tML Namespace: A collection of names, identif

29、ied 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 consistent language for specifying, visualizing, constructing, and documenting the artifacts of software

30、 systems and for modeling of business processes ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 74. Acronyms ANSI American National Standards Institute ATIS Alliance for Telecommunications Industry Solutions GTDD Generic Telecom Data Dictionary HTTP(s) HyperText Transfer Protocol, Secu

31、re IETF Internet Engineering Task Force ISOP Interconnection Services Ordering and Provisioning ITU International Telecommunications Union LSR Local Service Request OAM&P Operations, Administration, Maintenance & Provisioning OBF Ordering and Billing Forum OMG Object Management Group RFC Request For

32、 Comment TMOC Telecom Management and Operations Committee tML telecommunications Markup Language TMN Telecommunications Management Network UML Unified Modeling Language UOM Unified Ordering Model URI Universal Record Identifier URL Universal Record Locator URN Universal Record Name W3C World Wide We

33、b Consortium XML eXtensible Markup Language Acronyms for OBF data elements used in this document are defined in ATIS/OBF documents. ATIS 0412003-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 85. Overview of UOM-LSR Volume III Introduction to UOM The intent of Unified Ordering Model (UOM) is to de

34、velop 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 are defined within the UOM in four volumes depicted in the figure below. Process2. AnalysisUn

35、ified Model2. Logical Model- Class/Object Diagrams- Data Traceablity- Interaction Diagrams- State DiagramsVolume IVolume IIVolume IIIVolume IV3. Design 3. Information Model- Technology Information Model4. Implementation 4. Implementation Guidelines- Technology Specifications- Implementation Profile1

36、. Business Process . Definition 1. Business Requirements- High Level Use Cases- Data/Presentation Requirement- Business Validation Rules- Scenarios- Activity DiagramsLSOPLSOP LSOPLSOP/UOMASRUOM Process and Document DevelopmentUOM-LSR Volume I - Business Process Definition UOM-LSR Volume I provide an

37、 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 requirements for LSR functionality are described in ATIS/OBF Local Service Ordering Guideline (LSO

38、G). The OBF LSOP Committee 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 be grouped into the following functional areas: Pre-Order, Service Order, and Post-Order. The Pre-Or

39、der 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 business rules and the information regarding use of the pre-order functions within the practice. ATIS 041200

40、3-0803 UOM-LSR Volume III Issued 9/30/08 LSOG 3Q08 9The Service Order practices describe the various forms used for the purpose of requesting local service. It includes field definitions, conventions, descriptions, and various scenarios to outline the process for a local service request. The Post-Or

41、der 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 meet the needs of the business requirements stated in ATIS/OBF LSR process. The primary sections inc

42、lude 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. Because of the level of complexities inherent in such an electronic ordering model, a unified model

43、ing 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 additional requirements are included in Volume II in order to accommodate fundamental aspects of ordering

44、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 address additional requirements. The OBF LSOP Technical Group maintains the UOM-LSR Volume II. UOM-LSR

45、 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 the implementation technology that is currently supported. This document does not specify a partic

46、ular 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 LSOP Technical Group maintains the UOM-LSR Volume III for XML implementation UO

47、M 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 selected implementation technology. In addition, a sample Joint Implementation Agreement (JIA) may