ATIS 0412003-0006-2007 Unified Ordering Model Local Service Ordering Guidelines Volume III - Design (LSOG 14).pdf

1、 ATIS-0412003-0006 Unified Ordering Model (UOM) Volume III - Design Issue 6 For Local Service Ordering Guidelines (LSOG) Version 14 ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 2ATIS is a technical planning and standards development organization that is committed to rap

2、idly developing and promoting 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

3、, and its Incubator Solutions Program. www.atis.org ATIS 0412003-0006 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 Str

4、eet, NW, Suite 500 Washington, DC 20005 Copyright 2007 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 info

5、rmation contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 3Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professional

6、s 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. NO REPRESENTATION OR WARRAN

7、TY 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 FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS

8、 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 CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION

9、 PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 4TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION .6 SCOPE.6 PURPOSE.6 APPLICATION6 2. NORMATIVE REFERENCES 6 STANDARDS .6 OTHER REFERENCES.6 3. DEFINITIONS.7

10、4. ACRONYMS8 5. OVERVIEW OF UOM-LSR VOLUME III9 INTRODUCTION TO UOM9 UOM-LSR VOLUME I - BUSINESS PROCESS DEFINITION .9 UOM VOLUME II - ANALYSIS 10 UOM-LSR VOLUME III - DESIGN 10 UOM GENERIC IMPLEMENTATION GUIDELINES (GIG) VOLUME IV - IMPLEMENTATION.10 6. UOM REQUIREMENTS SUMMARY11 SYSTEM REQUIREMENT

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

12、Schema14 UOM-LSR Base Schema141 UOM-LSR Pre-Order Schema.153 UOM-LSR Pre-Order Processes (POP) schema .154 UOM-LSR Customer Service Inquery (CSI) schema .168 UOM-LSR Directory Listing Inquery (DLI) schema .174 UOM-LSR Order Schemas 178 UOM-LSR Local Service Request (LSR)180 UOM-LSR End User (EU).184

13、 UOM-LSR Loop Service (LS) 188 UOM-LSR Number Portability (NP) .189 UOM-LSR Loop Service with Number Portability (LSNP)191 UOM-LSR Resale Service (RS).193 UOM-LSR Port Service (PS) .194 UOM-LSR Resale Private Line (RPL) .196 UOM-LSR Resale Frame Rely (RFR)200 UOM-LSR CENTREX Resale Services (CRS) .2

14、02 ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 5UOM-LSR DID/DOD/PBX Services (DDPS)206 UOM-LSR Hunt Group Information (HGI) .209 UOM-LSR ISDN/BRI/PRI Service (IS) .211 UOM-LSR Directory Listing Service (DL) 214 UOM-LSR Local Response (LR) schema.218 UOM-LSR Post-Order

15、Schema224 UOM-LSR Provider Notification (PN) schema .225 UOM-LSR Service Order Inquery Process (SOIP) schema.226 UOM-LSR Loss Alert / Transition Information (LATI) schema.233 APPENDIX A: CONTRIBUTORS TO UOM-LSR VOLUME III .237 ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 1

16、4 61. 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 Service Request (UOM-LSR). The interface is specified using the tel

17、ecommunications 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 associated with Local Services Request Ordering; Pre-Ordering, Ordering, and

18、 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 set of schemas for LSR Pre-Order, the set of schemas for LSR Orderi

19、ng, 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, response, notification, acknowledgement, and exception response functio

20、ns 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 Volume III is a technology-specific definition of the access domain inte

21、ractions 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 The following standards and industry guidelines contain provisions

22、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 this American National Standard are encouraged to investigate the p

23、ossibility 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 Consortium (W3C) Recommendation, XML Schema Part 1: Structures, 2 May 2

24、001 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-0006: Unified Ordering Model Local Service Request (UOM-LSR) Volume II Analysis for LSR Version

25、 14, Issue 6 ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 7Note: 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:/

26、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 in order to separate them from other names. Not

27、e: 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 particular namespace called a target namespace.

28、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 constituent parts: datatypes, elements and their

29、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 generic term for the building blocks that comprise t

30、he 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 definitions, model group definitions, notation de

31、clarations, 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 Schemas are based on the W3C XML Schema Recommenda

32、tion. 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 consistent language for specifying, visualizing, cons

33、tructing, and documenting the artifacts of software systems and for modeling of business processes ATIS-0412003-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 84. Acronyms ANSI American National Standards Institute ATIS Alliance for Telecommunications Industry Solutions GTDD Generic T

34、elecom 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, Maintenance & Provisioning OBF Orderi

35、ng 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 Universal Record Identifier URL Univ

36、ersal 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-0006 UOM-LSR Volume III Issued 12/18/2007 Issue 6 for LSOG 14 95. Overview of UOM-LSR Volum

37、e 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 components are defined with

38、in 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 Model4. Implementation 4.

39、Implementation Guidelines- Technology Specifications- Implementation Profile1. Business Process . Definition 1. Business Requirements- High Level Use Cases- Data/Presentation Requirement- Business Validation Rules- Scenarios- Activity DiagramsLSOPESOC/UOM LSR UOMLSRUOMLSR/UOMASRUOM Process and Docum

40、ent 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 requireme

41、nts for LSR functionality are described in ATIS/OBF Local Service Ordering Guideline (LSOG). 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 ATIS-0412003-0006 UOM-LSR Volu

42、me III Issued 12/18/2007 Issue 6 for LSOG 14 10LSOG practices may 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 al

43、so defines each data element and contains both the common business rules and the information regarding use of the pre-order functions within the practice. The Service Order practices describe the various forms used for the purpose of requesting local service. It includes field definitions, conventio

44、ns, 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

45、to 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

46、II. 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 add

47、itional 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 address add