ATIS 0412002-0004-2007 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II C Analysis Issue 4.pdf

《ATIS 0412002-0004-2007 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II C Analysis Issue 4.pdf》由会员分享，可在线阅读，更多相关《ATIS 0412002-0004-2007 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II C Analysis Issue 4.pdf（115页珍藏版）》请在麦多课文档分享上搜索。

1、 Page 1 ATIS-0412002-0004 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II Analysis Issue 4 ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 2 ATIS is a technical planning and standards development organization that is committed to rapidly developing and promot

2、ing 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 Soluti

3、ons Program. www.atis.org ATIS 0412002-0004 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

4、 G Street, 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. Fo

5、r information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 3 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professio

6、nals 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 WAR

7、RANTY 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. A

8、TIS 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 INFORMAT

9、ION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 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 (LSR LSOG Versio

10、n 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-LSR Volume II

11、 for Local Service Ordering( LSR LSOG Version 12) ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 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 - Desig

12、n. 9 1.4 UOM Generic Implementation Guidelines (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

13、Purpose . 12 3.3 Scope 12 3.4 Development 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 . 19 5.1.2 Telephone Number Assignment . 21 5.1.3

14、Feature / Service Availability . 23 5.1.4 Appointment Scheduling / Appointment Reservation 25 5.1.5 Service Configuration. 27 5.1.6 Loop Qualification 28 5.1.7 Customer Service Inquiry. 29 5.1.8 Facility Assignment Verification 30 5.1.9 Directory Listing Inquiry (DLI) 31 5.2 UOM-LSR Service Order Re

15、quest and Response 32 5.2.1 Service Order Request 33 5.2.1.1 Local Service Request (LSR) . 33 5.2.1.2 End User (EU) 33 5.2.1.3 Loop Service (LS) 33 5.2.1.4 Number Portability (NP) 33 5.2.1.5 Loop Service with Number Portability (LSNP) 33 5.2.1.6 Resale Service (RS) 33 5.2.1.7 Port Service (PS) 34 5.

16、2.1.8 Resale Private Line (RPL) 34 5.2.1.9 Resale Frame Relay (RFR). 34 5.2.1.10 CENTREX Resale Services (CRS). 34 5.2.1.11 DID/DOD/PBX Services (DDPS) 34 5.2.1.12 Hunt Group Information (HGI) 34 5.2.1.13 ISDN BRI/PRI Service (IS) 34 5.2.1.14 Directory Listing Service (DL). 35 5.2.2 Service Order Re

17、sponse 35 5.2.2.1 Local Response (LR) 35 5.3 UOM-LSR Post Order 36 5.3.1 Service Order Inquiry Process (SOIP) 37 5.3.2 Provider Notification (PN) . 37 5.3.3 Loss Alert / Transition Information (LATI) . 37 6. Information Model 39 6.1 UOM-LSR High Level View 40 ATIS 0412002-0004 UOM-LSR Volume II Issu

18、ed 7/12/07 Issue 4 for LSOG 12 6 6.2 LSR Inquiry Request and Response Classes 40 6.3 Abbreviation List 40 6.4 Data Groups 41 6.5 UOM-LSR GRP Types Class Diagrams. 44 6.6 UOM-LSR Pre-Order . 46 6.6.1 Address Validation Data Fields 46 6.6.2 Address Validation Class Diagram. 47 6.6.3 Telephone Number A

19、ssignment Data Fields 48 6.6.4 Telephone Number Assignment Class Diagram. 49 6.6.5 Feature / Service Availability Data Fields 50 6.6.6 Feature / Service Availability Class Diagram. 51 6.6.7 Appointment Scheduling Data Fields. 52 6.6.8 Appointment Scheduling Class Diagram 53 6.6.9 Service Configurati

20、on Data Fields 54 6.6.10 Service Configuration Class Diagram 55 6.6.11 Loop Qualification Data Fields 56 6.6.12 Loop Qualification Class Diagram . 57 6.6.13 Local Customer Service Inquiry (CSI) Data Fields 58 6.6.14 Local Customer Service Inquiry (CSI) Class Diagram. 60 6.6.15 Facility Assignment Ve

21、rification Data Fields. 61 6.6.16 Facility Assignment Verification Class Diagram . 62 6.6.17 Directory Listing Inquiry (DLI) Data Fields 63 6.6.18 Directory Listing Inquiry (DLI) Class Diagram . 64 6.7 UOM-LSR Service Order Request and Response 66 6.7.1 LSR Service Request Classes . 66 6.7.2 LSR Ser

22、vice Type Classes 66 6.7.3 LSR Basic Forms 67 6.7.3.1 Local Service Request (LSR) Data Fields 68 6.7.3.2 Local Service Request (LSR) Class Diagram. 69 6.7.3.3 End User (EU) Data Fields. 70 6.7.3.4 End User (EU) Class Diagram 71 6.7.3.5 Loop Service (LS) Data Fields . 72 6.7.3.6 Loop Service (LS) Cla

23、ss Diagram 73 6.7.3.7 Number Portability (NP) Data Fields . 74 6.7.3.8 Number Portability (NP) Class Diagram 75 6.7.3.9 Loop Service with Number Portability (LSNP) Data Fields 76 6.7.3.10 Loop Service with Number Portability (LSNP) Class Diagram . 77 6.7.3.11 Resale Services (RS) Data Fields . 78 6.

24、7.3.12 Resale (RS) Class Diagram 79 6.7.3.13 Port Service (PS) Data Fields .80 6.7.3.14 Port Service (PS) Class Diagram 81 6.7.3.15 Resale Private Line (RPL) Data Fields. 82 6.7.3.16 Resale Private Line (RPL) Class Diagram 84 6.7.3.17 Resale Frame Relay (RFR) Data Fields 85 6.7.3.18 Resale Frame Rel

25、ay (RFR) Class Diagram 86 6.7.3.19 CENTREX Resale Services (CRS) Data Fields . 87 6.7.3.20 CENTREX Resale Services (CRS) Class Diagram 88 6.7.3.21 DID/DOD PBX Services (DDPS) Data Fields . 89 6.7.3.22 DID/DOD/PBX Service (DDPS) Class Diagram . 90 6.7.3.23 Hunt Group Information (HGI) Data Fields . 9

26、1 6.7.3.24 Hunt Group Information (HGI) Class Diagram 92 6.7.3.25 ISDN BRI/PRI Services (IS) Data Fields. 93 6.7.3.26 ISDN BRI/PRI (IS) Class Diagram 94 6.7.3.27 Directory Listing (DL) Data Fields 95 6.7.3.28 Directory Listing (DL) Class Diagram . 96 6.7.4 LSR Service Response Classes. 97 ATIS 04120

27、02-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 7 6.7.4.1 Local Response (LR) Data Fields.98 6.7.4.2 Local Response (LR) Class Diagram 100 6.8 UOM-LSR Post Order 101 6.8.1 Service Order Inquiry Process (SOIP) 101 6.8.1.1 SOIP Service Order List Inquiry/Response Data Fields 101 6.8.1.2 S

28、OIP Service Order List Class Diagram 103 6.8.1.3 SOIP Service Order Detail Inquiry/Response Data Fields 104 6.8.1.4 SOIP Service Order Detail Class Diagram 105 6.8.1.5 SOIP Service Order Activities Inquiry/Response Data Fields. 106 6.8.1.6 SOIP Service Order Activities Class Diagram 107 6.8.2 Loss A

29、lert / Transition Information Data Fields. 108 6.8.3 Loss Alert / Transition Information Class Diagram . 109 6.8.4 Provider Notification (PN) Data Fields 110 6.8.5 Provider Notification (PN) Class Diagram. 111 Appendix A: Requirements Traceability Matrix 112 Appendix B: Change Control Process 114 Re

30、ferences 115 ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 8 1. Introduction to UOM Documentation 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

31、 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 IVolume IIVol

32、ume 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 Valida

33、tion Rules- Scenarios- Activity DiagramsLSOPESOC/UOM LSR UOMLSRUOMLSR/UOMASRUOM Process and Document 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 us

34、er 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 separat

35、ed 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. ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 9 The Pre-Order practice describes the pre-order

36、 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 the variou

37、s 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. 1

38、.2 UOM-LSR 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 models

39、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 modeling language tool has been used to develop this Volume II. A traceability matrix is include

40、d 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 services via electronic inter-exchange. Volume II is not specific to any particular technol

41、ogy or protocol. If additional Volume I documents are developed, this Volume II may need to be expanded to address additional requirements. The OBF 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 A

42、nalysis Phase, is translated into the language appropriate for the selected implementation 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 approp

43、riate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF UOM-LSR Committee maintains the UOM-LSR Volume III for XML implementation and the EDI LSOG Mechanization Specifications (ELMS) documents for EDI implementation.

44、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 implementation technology. In addition, a sample Joint Implementation Agreement (

45、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 ATIS 0412002-0004 UOM-LSR Volume II Issued 7/12/07 Issue 4 for LSOG 12 10 multiple technologies. The

46、 UOM-ASR and UOM-LSR Committees maintain the UOM-GIG Volume 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 the various OBF documents and address issues involving security, messaging, and account profiles that will be provided in UO