1、 Page 1 ATIS-0412002-0803 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II Analysis For Local Service Ordering Guidelines (LSOG) 3Q08 ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 2 ATIS is a technical planning and standards development organization that is committed
2、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. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry comm
3、ittees, and its Incubator Solutions Program. www.atis.org ATIS 0412002-0803 Unified Ordering Mode Local Service Ordering (UOM-LSR) Volume II Analysis Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum LSOP Tech
4、nical Group Published by ATIS 1200 G Street, NW, Suite 500 Washington, 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 writt
5、en permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 3 Notice of Disclaimer and Limitation of Liability The information provided in this document is dire
6、cted 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 regulations. No recommendation as to products or vendors is made or should be implied.
7、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 MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLE
8、CTUAL 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 INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR REL
9、IANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 4 Change History Issue # Document Release Description of Changes OBF/LSOP Issue 2632 Issue 1 Initial Issue of UOM-LSR Volume II for Local Service Ordering (L
10、SR LSOG Version 9) OBF/UOM-LSR Issue 2989 Issue 2 Initial Issue of UOM-LSR Volume II for Local Service Ordering (LSR LSOG Version 10) OBF/UOM-LSR Issue 3064 Issue 3 Initial Issue of UOM-LSR Volume II for Local Service Ordering (LSR LSOG Version 11) OBF/UOM-LSR Issue 3078 Issue 4 Initial Issue of UOM
11、-LSR Volume II for Local Service Ordering( LSR LSOG Version 12) OBF/UOM-LSR Issue 3167 Issue 5 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 13) OBF/UOM-LSR Issue 3168 Issue 6 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 14) OBF/UO
12、MLSR Issue 3193 3Q08 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 3Q08) ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 5 Table of Contents 1. Introduction to UOM Documentation 7 1.1 UOM-LSR Volume I - Business Process Definition 7 1.2 UOM-LSR Volume I
13、I - Analysis . 8 1.3 UOM-LSR Volume III - Design. 8 1.4 UOM Generic Implementation Guidelines (GIG) Volume IV - Implementation. 8 2. UOM Requirements Summary . 9 2.1 System Requirements . 9 2.2 Security Requirements 9 2.3 Messaging Requirements 9 2.4 Reporting Requirements. 11 3. Overview of UOM-LSR
14、 Volume II 11 3.1 Intended Audience 11 3.2 Purpose . 11 3.3 Scope 11 3.4 Development Note 12 3.5 Assumptions of this Document. 12 3.6 Structure of Document 12 4. UOM-LSR High Level Process Overview . 13 5. Use Cases and Sequence Diagrams 15 5.1 UOM-LSR Pre-Order . 16 5.1.1 Address Validation . 18 5.
15、1.2 Telephone Number Assignment . 20 5.1.3 Feature / Service Availability . 22 5.1.4 Appointment Scheduling / Appointment Reservation 24 5.1.5 Service Configuration. 26 5.1.6 Loop Qualification 27 5.1.7 Customer Service Inquiry. 28 5.1.8 Facility Assignment Verification 29 5.1.9 Directory Listing In
16、quiry (DLI) 30 5.2 UOM-LSR Service Order Request and Response 31 5.2.1 Service Order Request 32 5.2.1.1 Local Service Request (LSR) . 32 5.2.1.2 End User (EU) 32 5.2.1.3 Loop Service (LS) 32 5.2.1.4 Number Portability (NP) 32 5.2.1.5 Loop Service with Number Portability (LSNP) 32 5.2.1.6 Resale Serv
17、ice (RS) 32 5.2.1.7 Port Service (PS) 33 5.2.1.8 Resale Private Line (RPL) 33 5.2.1.9 Resale Frame Relay (RFR). 33 5.2.1.10 CENTREX Resale Services (CRS). 33 5.2.1.11 DID/DOD/PBX Services (DDPS) 33 5.2.1.12 Hunt Group Information (HGI) 33 5.2.1.13 ISDN BRI/PRI Service (IS) 33 5.2.1.14 Directory List
18、ing Service (DL). 34 5.2.2 Service Order Response 34 5.2.2.1 Local Response (LR) 34 5.3 UOM-LSR Post Order 35 5.3.1 Service Order Inquiry Process (SOIP) 36 5.3.2 Provider Notification (PN) . 36 6. Information Model 37 6.1 UOM-LSR High Level View 38 6.2 LSR Inquiry Request and Response Classes 38 ATI
19、S 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 6 6.3 Abbreviation List 38 6.4 Data Groups 39 6.5 UOM-LSR GRP Types Class Diagrams. 40 6.6 UOM-LSR Pre-Order . 41 6.6.1 Address Validation Class Diagram. 41 6.6.2 Telephone Number Assignment Class Diagram. 42 6.6.3 Feature / Service Availabil
20、ity Class Diagram. 43 6.6.4 Appointment Scheduling Class Diagram 44 6.6.5 Service Configuration Class Diagram 45 6.6.6 Loop Qualification Class Diagram . 46 6.6.7 Local Customer Service Inquiry (CSI) Class Diagram. 48 6.6.8 Facility Assignment Verification Class Diagram . 49 6.6.9 Directory Listing
21、Inquiry (DLI) Class Diagram . 50 6.7 UOM-LSR Service Order Request and Response 51 6.7.1 LSR Service Request Classes . 51 6.7.2 LSR Service Type Classes 51 6.7.3 LSR Basic Forms 52 6.7.3.1 Local Service Request (LSR) Class Diagram. 53 6.7.3.2 End User (EU) Class Diagram 54 6.7.3.3 Loop Service (LS)
22、Class Diagram 55 6.7.3.4 Number Portability (NP) Class Diagram 56 6.7.3.5 Loop Service with Number Portability (LSNP) Class Diagram . 57 6.7.3.6 Resale (RS) Class Diagram 58 6.7.3.7 Port Service (PS) Class Diagram 59 6.7.3.8 Resale Private Line (RPL) Class Diagram . 60 6.7.3.9 Resale Frame Relay (RF
23、R) Class Diagram 61 6.7.3.10 CENTREX Resale Services (CRS) Class Diagram 62 6.7.3.11 DID/DOD/PBX Service (DDPS) Class Diagram . 63 6.7.3.12 Hunt Group Information (HGI) Class Diagram 64 6.7.3.13 ISDN BRI/PRI (IS) Class Diagram 65 6.7.3.14 Directory Listing (DL) Class Diagram . 66 6.7.4 LSR Service R
24、esponse Classes. 67 6.7.4.1 Local Response (LR) Class Diagram 68 6.8 UOM-LSR Post Order 69 6.8.1 Service Order Inquiry Process (SOIP) 69 6.8.1.1 SOIP Service Order List Class Diagram 69 6.8.1.2 SOIP Service Order Detail Class Diagram 70 6.8.1.3 SOIP Service Order Activities Class Diagram 71 6.8.2 Pr
25、ovider Notification (PN) Class Diagram. 72 6.9 Simple Port Service Request (SPSR) . 73 6.9.1 SPSR Diagram 73 Appendix A: Requirements Traceability Matrix 74 Appendix B: Change Control Process 76 References 77 ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 7 1. Introduction to UOM Docum
26、entation 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 within the UOM in fou
27、r 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. Implementation Gu
28、idelines- 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 and Document Development1.1 UOM-LSR Vo
29、lume I - Business Process Definition UOM-LSR Volume I provides 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 requirements for LSR functionalit
30、y 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 LSOG practices may be grouped into the following funct
31、ional 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 business rules and the information regardin
32、g use of the pre-order functions within the practice. ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 8 The Service Order practices describe the various forms used for the purpose of requesting local service. It includes field definitions, conventions, descriptions, and various scenario
33、s 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. 1.2 UOM-LSR Volume II - Analysis This analysis document provides the logical view of the proposed solution to meet the needs of the busin
34、ess 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. Because of the level of co
35、mplexities 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 additional requirements are inclu
36、ded 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 additional requiremen
37、ts. The OBF LSOP Technical Group maintains the UOM-LSR Volume II. 1.3 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 the implementation te
38、chnology 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 selected. The OBF LS
39、OP Technical Group maintains the UOM-LSR Volume III for XML implementation 1.4 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 selected implem
40、entation 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. Th
41、e UOM-ASR and LSOP Committees maintain the UOM-GIG Volume IV. The LSOP Technical Group maintains UOM-LSR Appendices related to LSR in Volume IV. ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 9 2. UOM Requirements Summary 2.1 System Requirements Additional system requirements are neede
42、d to support an implemented UOM interface. These requirements are in addition to the business requirements specified by the various OBF documents and address issues involving security, messaging, and account profiles that will be provided in UOM Volume IV. Additional requirements may also be added b
43、ased upon customer provider negotiations as documented in pair wise Joint Implementation Agreements. 2.2 Security Requirements Security requirements include encryption, authentication, and non-repudiation. Refer to tML Transport Specification found in the ATIS Document Center. 2.3 Messaging Requirem
44、ents Messaging requirements include attributes needed for message handling, delivery, responses, acknowledgements, and exceptions. Element MESSAGE_ID: Class: UOM_HDR_Type Attribute: MESSAGE_ID Usage: Required Type: Character string with maximum length of 25 Description: Used as an invocation id. Mes
45、sage originator assigns a new message id to each message of type Request or Notification. Message recipient responds with the same message id with each message of type Response, Acknowledgement, or Exception. Element MSG_TIMESTAMP: Class: UOM_HDR_Type Attribute: MSG_TIMESTAMP Usage: Required Type: x
46、s:dateTime Description: Used to timestamp each message with the date and time the message was created. It is assumed messages are created just prior to transmission. This field is indented for logging purposes to help debugging and evaluating performance. Element TYPE: Class: EXCEPTION_RESPONSE Attribute: TYPE ATIS 0412002-0803 UOM-LSR Volume II Issued 9/30/08 LSOG 3Q08 10 Usage: Required Type: ExceptionType_Type (enumeration) Values: GENERAL_FAILURE GENERAL_ERROR_RETRYABLE TRANSPORT_
