1、 ATIS-0410503-0002 Unified Ordering Model (UOM) Volume III - Design Issue 2 For Local Service Ordering Guidelines (LSOG) Version 10 2 Above is the page number. They are always in 10 point, regular, centered, Arial. Style Sheet: Page number. ATIS-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issu
2、e 2 for LSOG 10 3ATIS is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach.
3、Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees, and its Incubator Solutions Program. www.atis.org ATIS 0410503-0002 Unified Ordering Model (UOM) Volume III - Design Is an ATIS standard developed by the following committee(s) under the AT
4、IS Ordering and Billing Functional Group: Ordering and Billing Forum UMA UOM-LSR Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2006 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in
5、 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 of America. ATIS-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 4Notice of Discla
6、imer 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 its contents in accordance with generally accepted engineering or other professional standards and applicable regul
7、ations. 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 CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHA
8、NTABILITY 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 ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INC
9、IDENTAL 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-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 5TABLE OF CONTENTS 1. SCOPE, PURPOSE AND FIELD OF APPLICATION
10、.7 1.1 SCOPE 7 1.2 PURPOSE 7 1.3 APPLICATION .7 2. NORMATIVE REFERENCES 7 2.1 STANDARDS .7 2.2 OTHER REFERENCES 7 3. DEFINITIONS.8 4. ACRONYMS9 5. OVERVIEW OF UOM-LSR VOLUME III10 5.1 INTRODUCTION TO UOM .10 5.2 UOM-LSR VOLUME I - BUSINESS PROCESS DEFINITION .10 5.3 UOM VOLUME II - ANALYSIS11 5.4 UO
11、M-LSR VOLUME III - DESIGN 11 5.5 UOM GENERIC IMPLEMENTATION GUIDELINES (GIG) VOLUME IV - IMPLEMENTATION.11 6. UOM REQUIREMENTS SUMMARY11 6.1 SYSTEM REQUIREMENTS11 6.2 SECURITY REQUIREMENTS.12 6.3 MESSAGING REQUIREMENTS12 6.4 HOW TO USE THIS DOCUMENT 13 7. REQUIREMENTS OVERVIEW.13 8. ANALYSIS OVERVIE
12、W .13 9. IMPLEMENTATION OVERVIEW13 10. DESIGN (TECHNOLOGY INFORMATION MODEL) 14 10.1 TML SCHEMAS14 10.1.1 Conformance Statement to the tML Framework14 10.1.2 Schema Structure.14 10.1.3 UOM-Base Schema15 10.1.4 UOM-LSR Base Schema 117 10.1.5 UOM-LSR Pre-Order Schema .127 10.1.5.1 UOM-LSR Pre-Order Pr
13、ocesses (POP) schema.127 10.1.5.2 UOM-LSR Customer Service Inquery (CSI) schema 137 10.1.5.3 UOM-LSR Directory Listing Inquery (DLI) schema.142 10.1.6 UOM-LSR Order Schemas.145 10.1.6.1 UOM-LSR Local Sercice Request (LSR).147 10.1.6.2 UOM-LSR End User (EU) 151 10.1.6.3 UOM-LSR Loop Service (LS)153 1
14、0.1.6.4 UOM-LSR Number Portability (NP).155 10.1.6.5 UOM-LSR Loop Sercice with Number Portability (LSNP).156 10.1.6.6 UOM-LSR Resale Sercice (RS) 157 10.1.6.7 UOM-LSR Port Sercice (PS).158 10.1.6.8 UOM-LSR Resale Private Line (RPL) 160 10.1.6.9 UOM-LSR Resale Frame Rely (RFR) .163 10.1.6.10 UOM-LSR
15、CENTREX Resale Services (CRS).165 ATIS-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 610.1.6.11 UOM-LSR DID/DOD/PBX Sercices (DDPS) .167 10.1.6.12 UOM-LSR Hunt Group Information (HGI) 170 10.1.6.13 UOM-LSR ISDN/BRI/PRI Sercice (IS) 171 10.1.6.14 UOM-LSR Directory Listing Serc
16、ice (DL)173 10.1.6.15 UOM-LSR Local Response (LR) schema 176 10.1.6.16 UOM-LSR Directory Service Request Completion (DSCN) schema.179 10.1.6.17 UOM-LSR Directory Service Request Error Detail (DSRED) schema.181 10.1.6.18 UOM-LSR Local Service Response Completion (LSRCM) schema 182 10.1.7 UOM-LSR Post
17、-Order Schema.183 10.1.7.1 UOM-LSR Provider Notification (PN) schema.183 10.1.7.2 UOM-LSR Service Order Inquery Process (SOIP) schema184 10.1.7.3 UOM-LSR Loss Alert / Transition Information (LATI) schema188 APPENDIX A: CONTRIBUTORS TO UOM-LSR VOLUME III .191 ATIS-0410503-0002 UOM-LSR Volume III Issu
18、ed 10/27/2006 Issue 2 for LSOG 10 71. Scope, Purpose and Field of Application 1.1 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
19、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 document defines tML Schemas to support the UOM-LSR. The schemas provide for the three broad functions associated with Local Services Reque
20、st Ordering; Pre-Ordering, Ordering, and Post-Ordering. 1.3 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
21、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, response, notification, ack
22、nowledgement, 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 Volume III is a technology-s
23、pecific 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 The following standards
24、 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 this American National
25、Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. 2.1 Standards World Wide Web Consortium (W3C) Recommendation XML: eXtensible Markup Language (XML) 1.0 (Second Edition), 6 October 2000 World Wide Web Consortium (W3C) Recomm
26、endation, 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 2.2 Other References ATIS0410502-0002: Unified Ordering Model Local Service
27、Request (UOM-LSR) Volume II Analysis for LSR Version 10, Issue 2 ATIS-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 8 TCIF-03-003: tML Transport Profile, July 2003 Note: ATIS/OBF Documents can be ordered from OBF Manager, ATIS, 1200 G Street N.W., Suite 500, Washington, DC 20
28、005. 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 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
29、 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 collection (vocabulary) of type definition
30、s 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 these constructs to constrain and docum
31、ent 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 instance documents that will still conform to
32、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, Attribute declarations, Element declarations,
33、 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 meaning, usage and relationships of the
34、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 specification to provide system architects w
35、orking 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-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 94. Acronyms ANSI American
36、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 ISOP Interconnection Services Ordering and Provisioning ITU International Telecommunications Unio
37、n LSR Local Service Request OAM&P Operations, Administration, Maintenance & 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 Networ
38、k UML Unified Modeling Language UOM Unified Ordering Model URI Universal 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-
39、0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 105. Overview of UOM-LSR Volume III 5.1 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 b
40、usiness requirements, analysis, design, and implementation. Logically, these components 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 IVolum
41、e IIVolume IIIVolume IV3. Design 3. Information Model- Technology Information Model4. Implementation 4. Implementation Guidelines- Technology Specifications- Implementation Profile1. Business Process . Definition 1. Business Requirements- High Level Use Cases- Data/Presentation Requirement- Business
42、 Validation Rules- Scenarios- Activity DiagramsLSOPESOC/UOM LSR UOMLSRUOMLSR/UOMASRUOM Process and Document Development5.2 UOM-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”
43、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 (LSOG). The OBF LSOP Committee maintains the LSOG documents. The LSOG constitutes UOM-LSR Volume I. It is s
44、eparated into several practices that address specific business functions. The ATIS-0410503-0002 UOM-LSR Volume III Issued 10/27/2006 Issue 2 for LSOG 10 11LSOG practices may be grouped into the following functional areas: Pre-Order, Service Order, and Post-Order. The Pre-Order practice describes the
45、 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. The Service Order practices describe
46、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-Order practices outline the forms provided for local service responses and service order inquiries. 5.3 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 include the use case and sequence diagrams, and informational model. The informational
