1、 ATIS-0413001-0001 Next Generation Network Operations Business and Functional Requirements for Ordering and Billing/Settlement Version 1.0.0 ATIS-0413001-0001 Issued January 22, 2010 The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organi
2、zation 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. Over 1,100 participants from more than 350 communications companies are active
3、 in ATIS 23 industry committees and its Incubator Solutions Program. NOTE - The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity
4、 of this claim or any patent rights in connection therewith. The patent holder has, however, filed a statement of willingness to grant license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the
5、 publisher. ATIS-0413001-0001 Next Generation Network Operations Business and Functional Requirements for Ordering and Billing/Settlement, Version 1.0.0 Is an ATIS standard developed by the Internet Protocol Network-to-Network Interface Committee (IP-NNI) and currently maintained by the Ordering Sol
6、utions Committee under the ATIS Ordering and Billing Forum (OBF). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2010 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication ma
7、y be reproduced in any form, in 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-0413001-0001 Issued January 22, 2010 ii Notice of Discla
8、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
9、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
10、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
11、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-0413001-0001 Issued January 22, 2010 iii TABLE OF CONTENTS TABLE OF CONTENTSIII TABLE OF FIGURES IV 1 SCOPE, PURPOSE, however, that
12、 has not yet been completed. The OBF has noted it needs to take this into consideration in its development of Supplier/Partner records and settlement standards. As part of the ATIS-TMOC adoption of the trading partner accounting and settlements service-neutral standard in 2005 2, the following servi
13、ce-independent set of commercial arrangements/applications were considered in determining the settlement standards: Retail Billing The rendering of an invoice for charges due to a Service Provider by a Subscriber to their services, as per an agreed rate plan and service agreement. Wholesale Billing
14、The rendering of an invoice for charges due to a Network Operator from a Service Provider for access or transport services via which the Service Providers services were delivered. Intercarrier Settlement The process by which Service Providers determine the periodic charges due from one party to anot
15、her for services rendered by each of the parties on behalf of the others Subscribers. Internal Cost Accounting (e.g., Chargeback) Use of accounting information by a commercial Subscriber for separating the aggregate usage into sub-accounts associated with the enterprises financial components. Custom
16、er Care All those activities associated with the sustenance of satisfactory Subscriber service levels, including inquiries, account changes, restoral, and termination. Marketing Information Demographic, financial, statistical, geographical, and temporal data used to aid in decision making and direct
17、ion setting for product and services positioning and introduction by a Service Provider. Lawful Intercept Capture of targeted service usage entries, requested by a legal order for use by various agencies of law enforcement. Capacity Planning Predictive extension of existing usage patterns to allow f
18、or adequate resources to be staged in such a timeframe as to ensure continuity of agreed service levels. Traffic Profiling Statistical portrayal of usage information for characterizing the patterns of usage levels and concentrations at nodal points and across transport boundaries. Traffic Engineerin
19、g Use of traffic profile information to manage the configuration of infrastructure resources so as to ensure service level continuity. Performance Management Use of statistical data derived from network and service element telemetry to adapt the configuration of those elements to ensure service leve
20、l continuity. ATIS-0413001-0001 Issued January 22, 2010 7 Revenue Assurance - Any activity an organization performs to ensure that processes, practices, and procedures result in revenue that is billed and collected completely, accurately, and in a timely manner. This involves all areas of the organi
21、zation, crossing all boundaries from customer care and network systems to invoicing and collections and finance. Revenue leakage which is revenue the company has earned, but has neither billed for nor collected. This revenue is lost. Revenue assurance includes Fraud Abatement (e.g., Attack/Intrusion
22、 Detection), the use of statistical and pattern recognition results to detect, prevent, and interdict in usage by Service Consumers not authorized for such usage by a Subscription agreement. QoS Monitoring / SLA Management Use of all varieties of network and BSS data in the tracking and adaptation o
23、f network behavior to ensure service level continuity. The generic requirements for all commercial arrangements/application types along with the suggested level of requirements, per application, for every single requirement, are specified in section 7 of ATIS-0300075 1. 2 NORMATIVE REFERENCES The fo
24、llowing standards contain provisions which, through reference in this text, constitute provisions of this ATIS Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this ATIS Standard are encouraged to inves
25、tigate the possibility of applying the most recent editions of the standards indicated below. 1 ATIS-0300075, Usage Data Management for Packet-Based Services - Service-Neutral Architecture and Protocol Requirements.12 ATIS-0300075.1.2006, Usage Data Management for Packet-Based Services - Service-Neu
26、tral Protocol Specification for Billing Applications.13 ATIS Contribution TMOC-AIP-2006-016R4, ITU-T Harmonization of Accounting Management Mechanisms for NGN.24 ATIS-0406000-2203, Exchange Message Interface (EMI), Issue 22 Revision 3.15 ATIS Contribution TMOC-AIP-2007-004, IPTV OSS Functional Requi
27、rements and Reference Architecture Working Text.26 ATIS-0410100-0003, Unified Modeling Approach (UMA) Committees Guiding Principles, Issue 3.17 ATIS-0401004-0009, Multiple Exchange Carrier Access Billing (MECAB).18 ATIS-0300092, High-level OSS/BSS Functional Requirements and Reference Architecture f
28、or IPTV.11This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 2This reference is a committee contribution. OBF committee participants can access this document at . Copies of this contribution will be made
29、 available to all other interested parties upon request. Such request should be made to the ATIS Document Center Administrator at . ATIS-0413001-0001 Issued January 22, 2010 8 9 ATIS Exploratory Group on Convergence (EGC) Report and Recommendations, September 2007.110 ATIS-Inter-Carrier VoIP Call Ro
30、uting (IVCR) Assessment and Workplan, February 2008.111 ITU-T M.3050.2, eTOM Process Decomposition and Descriptions.112 ATIS-0404110-0014, Unified Ordering Model Access Service Requests (UOM-ASR), Volume 1: Business Requirements for an Electronic Ordering Interface, Version 14.113 TMF GB921 Addendum
31、 D, Enhanced Telecom Operations Map (eTOM), The Business Process Framework, Version 7.1.114 TMF GB921 Addendum D, Enhanced Telecom Operations Map (eTOM), The Business Process Framework, Version 8.3.13 TERMINOLOGY, ACRONYMS, whereas, the S/PIM is specific to those providers offering a service for pur
32、chase and resale to an end-user customer or another network/service provider. 5.1.1 Customer Interface Management (CIM) The (CIM) process manages interactions between the IP Service Provider (SP) and potential/existing customers. The process components of CIM include: Manage Contact This process pro
33、vides for the management of all contacts between the SP and existing or potential interconnecting service provider customers. Manage Request (Including Self Service) The SP must have the ability to manage incoming and outgoing Customer requests and communication. This can be accomplished through var
34、ious media (web, phone, direct mail, fax). The types of service requests to be managed for the IP-NNI include the receipt of orders for IP network interconnection and related customer care support, including customer disputes or complaints. Analyze and Report on Customers The SP must have the abilit
35、y to perform all necessary analysis on closed (completed or unfulfilled) requests and on customer contacts. The analysis generates information that can be utilized for process improvement activities, proactive problems prevention, up-sell opportunities definition, service quality, customer required
36、reporting, etc. Mediate and Orchestrate Customer Interaction The SP will need to ensure that the format/protocol used between its Customers are consistent with industry standards. This requires the SP to stay abreast of all necessary data formats to provide the Customer with an adequate Customer exp
37、erience. 5.1.2 S/P (Supplier/Partner) Interface Management S/P (Supplier/Partner) Interface Management processes manage the contacts between the IP SP and its suppliers/partners (e.g., NPs and CPs) for products or IP Services. The process components associated with S/P Interface Management include:
38、Manage S/P Requests (including Self Service) The SP must have the ability to accept requests and enable the supplier/partner to obtain the desired information from the IP Service Provider, or to identify and activate the appropriate process area to accomplish the request. Analyze and b) showing the
39、relationships between design elements. The UML should be used to document all the relevant relationships that are important in describing this abstract view. The constructs used in Volume I are: Use Cases that define the users view of the system. Diagrams that can be used to describe process flows.
40、This document also incorporates the content established in the Multiple Exchange Carrier Access Billing (MECAB) document dated December 8, 1988 7 and the TMF eTOM model 11. Finally, this document will incorporate the resolution of IP-related ordering and billing issues. One goal is to identify commo
41、n data elements critical to the provisioning of verifiable and auditable bills while providing procedures for exchange of data between providers. The record exchange models will be based on multiple sources. References to existing documents will be included. 9 SERVICE SPECIFICATIONS OBF Billing and
42、Record Exchange Committee should define what is to be encompassed in the overall data exchange and settlement/billing, including the ATIS-0300075 “E” Interface 1 for Supplier/Partners utilizing the accounting interfaces between packet-based network and service elements and OSS/BSS. The recommendatio
43、n is to build on the framework specified in documents ATIS-0300075 1 and ATIS-0300075.1 2. The processes and requirements denoted in Sections 5-7 provide the fundamentals needed for Order and Billing Management in the IP Services environment. Further detailed work is needed to identify and develop s
44、pecific Ordering and Billing standards to a specific service level. Additional documents will be created by the OBF and other ATIS Standards committees to provide IP Service specific specifications surrounding these Level 2 and 3 requirements defined above. 9.1 Specification Approach There is a need
45、 for OBF to produce an ITU-T Recommendation regarding the data exchange between Suppliers and Partners utilizing the accounting interfaces as described in ATIS-0300075.1 “E” Interface 2. The recommendation is to build on the American National Standard framework developed by TMOC-AIP/IPDR as reflecte
46、d in ATIS documents ATIS-0300075 1 and ATIS-0300075.1 2. It should include business processes and procedures supporting packet based network and service elements such as VoIP gateways, gatekeepers, media gateway controllers, etc. ATIS-0413001-0001 Issued January 22, 2010 29 Future documents will beg
47、in creating specific specifications and standards surrounding services that would be provided in a packet-based environment. This will begin with OBF Issue 3228, creation of IP-to-IP Scenarios and Use Cases. These services include but are not limited to voice, data, and video, as well as contract re
48、lated billing for products and services offered. As denoted previously in the introduction, these new specifications will follow the Unified Modeling Approach methodology 12 established with the ATIS Joint Leadership. The order in which the specifications are completed will be based on the business
49、needs identified by participating companies. 9.2 Ordering and Billing Architecture Model The ATIS UMA methodology identified above will be used in the creation of service specific Ordering and Billing/Settlement records. The created records may need to be added to the ATIS-0300075 1 and ATIS-0300075.1 2 models already defined.
