1、 Page 1 ATIS-0412002-0001 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II Analysis Issue 1 ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 2 ATIS is a technical planning and standards development organization that is committed to rapidly developing and prom
2、oting 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 Solu
3、tions Program. www.atis.org ATIS 0412002 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 UOM- LSR Committee Published by ATIS 1200 G
4、Street, NW, Suite 500 Washington, DC 20005 Copyright 2005 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 i
5、nformation contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 3 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to profession
6、als 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 WARR
7、ANTY 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. AT
8、IS 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 INFORMATI
9、ON PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 4 Change History Issue # Document Release Description of Changes OBF/LSOP Issue 2632 R0.1 Initial Draft version of UOM-LSR Volume II for Local Service Ordering (LSR LSOG
10、Version 9) ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 5 Table of Contents 1. Introduction to UOM Documentation 8 1.1 UOM-LSR Volume I - Business Process Definition 8 1.2 UOM-LSR Volume II - Analysis . 9 1.3 UOM-LSR Volume III - Design. 9 1.4 UOM Generic Implementation G
11、uidelines (GIG) Volume IV - Implementation. 9 2. UOM Requirements Summary . 10 2.1 System Requirements . 10 2.2 Security Requirements 10 2.3 Messaging Requirements 10 2.4 Reporting Requirements. 12 3. Overview of UOM-LSR Volume II 12 3.1 Intended Audience 12 3.2 Purpose . 12 3.3 Scope 12 3.4 Develop
12、ment Note 13 3.5 Assumptions of this Document. 13 3.6 Structure of Document 13 4. UOM-LSR High Level Process Overview . 14 5. Use Cases and Sequence Diagrams 16 5.1 UOM-LSR Pre-Order . 17 5.1.1 Address Validation . 18 5.1.2 Telephone Number Assignment . 20 5.1.3 Feature / Service Availability . 22 5
13、.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 Loss Alert / Transition Information 29 5.2 UOM-LSR Service Order Request and Response 30 5.2.1 Service Order Request 31 5.2.1.1 Local Service
14、Request (LSR) . 31 5.2.1.2 End User (EU) 31 5.2.1.3 Loop Service (LS) 31 5.2.1.4 Number Portability (NP) 31 5.2.1.5 Loop Service with Number Portability (LSNP) 31 5.2.1.6 Resale Service (RS) 31 5.2.1.7 Port Service (PS) 32 5.2.1.8 Resale Private Line (RPL) 32 5.2.1.9 Resale Frame Relay (RFR). 32 5.2
15、.1.10 CENTREX Resale Services (CRS). 32 5.2.1.11 DID/DOD/PBX Services (DDPS) 32 5.2.1.12 Hunt Group Information (HGI) 32 5.2.1.13 ISDN BRI/PRI Service (IS) 32 5.2.1.14 Directory Listing Service (DL). 33 5.2.2 Service Order Response 33 5.2.2.1 Local Response (LR) 33 5.2.2.2 Directory Service Request
16、Completion Notice (DSCN). 33 5.2.2.3 Directory Service Request Error Detail (DSRED) . 33 5.2.2.4 Local Service Response / Completion (LSRCM). 34 5.3 UOM-LSR Post Order 35 5.3.1 Service Order Inquiry Process (SOIP) 36 5.3.2 Provider Notification (PN) . 36 5.3.3 Directory Listing Inquiry (DLI) 36 ATIS
17、 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 6 6. Information Model 37 6.1 UOM-LSR High Level View 38 6.2 LSR Inquiry Request and Response Classes 38 6.3 Abbreviation List 38 6.4 Data Groups 39 6.5 UOM-LSR GRP Types Class Diagrams. 43 6.6 UOM-LSR Pre-Order . 45 6.6.1 Address
18、Validation Data Fields 45 6.6.2 Address Validation Class Diagram. 46 6.6.3 Telephone Number Assignment Data Fields 47 6.6.4 Telephone Number Assignment Class Diagram. 48 6.6.5 Feature / Service Availability Data Fields 49 6.6.6 Feature / Service Availability Class Diagram. 50 6.6.7 Appointment Sched
19、uling Data Fields. 51 6.6.8 Appointment Scheduling Class Diagram 52 6.6.9 Service Configuration Data Fields 53 6.6.10 Service Configuration Class Diagram 54 6.6.11 Loop Qualification Data Fields 55 6.6.12 Loop Qualification Class Diagram . 56 6.6.13 Local Customer Service Inquiry (CSI) Data Fields 5
20、7 6.6.14 Local Customer Service Inquiry (CSI) Class Diagram. 60 6.6.15 Loss Alert / Transition Information Data Fields. 61 6.6.16 Loss Alert / Transition Information Class Diagram . 62 6.7 UOM-LSR Service Order Request and Response 64 6.7.1 LSR Service Request Classes . 64 6.7.2 LSR Service Type Cla
21、sses 64 6.7.3 LSR Basic Forms 65 6.7.3.1 Local Service Request (LSR) Data Fields 66 6.7.3.2 Local Service Request (LSR) Class Diagram. 67 6.7.3.3 End User (EU) Data Fields. 68 6.7.3.4 End User (EU) Class Diagram 69 6.7.3.5 Loop Service (LS) Data Fields . 70 6.7.3.6 Loop Service (LS) Class Diagram 72
22、 6.7.3.7 Number Portability (NP) Data Fields . 73 6.7.3.8 Number Portability (NP) Class Diagram 74 6.7.3.9 Loop Service with Number Portability (LSNP) Data Fields 75 6.7.3.10 Loop Service with Number Portability (LSNP) Class Diagram . 76 6.7.3.11 Resale Services (RS) Data Fields . 77 6.7.3.12 Resale
23、 (RS) Class Diagram 78 6.7.3.13 Port Service (PS) Data Fields .79 6.7.3.14 Port Service (PS) Class Diagram 80 6.7.3.15 Resale Private Line (RPL) Data Fields. 81 6.7.3.16 Resale Private Line (RPL) Class Diagram 83 6.7.3.17 Resale Frame Relay (RFR) Data Fields 84 6.7.3.18 Resale Frame Relay (RFR) Clas
24、s Diagram 85 6.7.3.19 CENTREX Resale Services (CRS) Data Fields . 86 6.7.3.20 CENTREX Resale Services (CRS) Class Diagram 87 6.7.3.21 DID/DOD PBX Services (DDPS) Data Fields . 88 6.7.3.22 DID/DOD/PBX Service (DDPS) Class Diagram . 89 6.7.3.23 Hunt Group Information (HGI) Data Fields . 90 6.7.3.24 Hu
25、nt Group Information (HGI) Class Diagram 91 6.7.3.25 ISDN BRI/PRI Services (IS) Data Fields . 92 6.7.3.26 ISDN BRI/PRI (IS) Class Diagram 93 6.7.3.27 Directory Listing (DL) Data Fields 94 6.7.3.28 Directory Listing (DL) Class Diagram . 95 6.7.4 LSR Service Response Classes. 96 ATIS 0412002-0001 UOM-
26、LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 7 6.7.5 LSR Notification Classes 97 6.7.5.1 Local Response (LR) Data Fields.98 6.7.5.2 Local Response (LR) Class Diagram 99 6.7.5.3 Directory Service Request Completion Notice (DSCN) Data Fields . 100 6.7.5.4 Directory Service Request Completion Not
27、ice (DSCN) Class Diagram 101 6.7.5.5 Directory Service Request Error Detail (DSRED) Data Fields 102 6.7.5.6 Directory Service Request Error Detail (DSRED) Class Diagram. 102 6.7.5.7 Local Service Response / Completion (LSRCM) Data Fields 103 6.7.5.8 Local Service Response/Completion (LSRCM) Class Di
28、agram 103 6.8 UOM-LSR Post Order 104 6.8.1 Directory Listing Inquiry (DLI) Data Fields 104 6.8.2 Directory Listing Inquiry (DLI) Class Diagram . 105 6.8.3 Service Order Inquiry Process (SOIP) 106 6.8.3.1 SOIP Service Order List Inquiry/Response Data Fields 106 6.8.3.2 SOIP Service Order List Class D
29、iagram 107 6.8.3.3 SOIP Service Order Detail Inquiry/Response Data Fields 108 6.8.3.4 SOIP Service Order Detail Class Diagram 109 6.8.3.5 SOIP Service Order Activities Inquiry/Response Data Fields. 110 6.8.3.6 SOIP Service Order Activities Class Diagram 111 6.8.4 Provider Notification (PN) Data Fiel
30、ds 112 6.8.5 Provider Notification (PN) Class Diagram. 113 Appendix A: Requirements Traceability Matrix 114 Appendix B: Change Control Process 116 Appendix C: Contributors 117 References 118 ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 8 1. Introduction to UOM Documentati
31、on 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 four volu
32、mes depicted in the figure below. Process 2. Analysis Unified Model 2. Logical Model- Class/Object Diagrams- Data Traceablity- Interaction Diagrams- State Diagrams Volume I Volume II Volume III Volume IV 3. Design 3. Information Model- Technology Information Model 4. Implementation 4. Implementation
33、 Guidelines- Technology Specifications- Implementation Profile 1. Business Process . Definition 1. Business Requirements - High Level Use Cases - Data/Presentation Requirement - Business Validation Rules - Scenarios - Activity Diagrams LSOP ESOC/ UOM LSR UOM LSR UOM LSR/ UOM ASR UOM Process and Docu
34、ment Development1.1 UOM-LSR Volume 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 req
35、uirements 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 LSOG practices may be gr
36、ouped into the following functional areas: Pre-Order, Service Order, and Post-Order. ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 9 The Pre-Order practice describes the pre-order inquiry and response functions that may take place prior to the ordering process. The practic
37、e 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 the various forms used for the purpose of requesting local service. It includes field definitions, conv
38、entions, 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. 1.2 UOM-LSR Volume II - Analysis This analysis document provides the logical view of the propo
39、sed 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 models are described using the Unified Modeling Language (UML). The UML provides the notation used w
40、ithin Volume 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 L
41、SOG. Some additional 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 b
42、e expanded to address additional requirements. The OBF ESOC and UOM-LSR Committees maintain 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 implemen
43、tation technologies. XML and EDI are implementation technologies that are 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 t
44、han one implementation technology is selected. The OBF UOM-LSR Committee maintains the UOM-LSR Volume III for XML implementation and the OBF ESOC maintains the EDI LSOG Mechanization Specifications (ELMS) documents for EDI implementation. 1.4 UOM Generic Implementation Guidelines (GIG) Volume IV - I
45、mplementation 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 be included as an appendix for trading partners to u
46、se as a starting template. As with the Design Phase, the Implementation Phase may also have to be repeated in order to provide support for ATIS 0412002-0001 UOM-LSR Volume II Issued 12/16/2005 Issue 1 for LSOG 9 10 multiple technologies. The UOM-ASR and UOM-LSR Committees maintain the UOM- GIG Volum
47、e IV. The UOM-LSR Committee maintains UOM-LSR Appendices related to LSR in Volume IV. 2. UOM Requirements Summary 2.1 System Requirements Additional system requirements are needed to support an implemented UOM interface. These requirements are in addition to the business requirements specified by th
48、e 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 based 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 Tran
