1、 ATIS-0411000-0001 VoIP Ordering and Billing Issues and Concerns Issue 1 ATIS 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 w
2、orldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 22 industry committees, and its Incubator Solutions Program. www.atis.orgATIS 0411001-0001 VoIP Ordering and Billing Issues and Concerns Is an ATIS standard
3、developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2005 by Alliance for Telecommunications Industry Solutions. All other trademarks are the property of
4、their respective owners. 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 information contact ATIS at 202.628.6380. ATIS is online at http:/www.atis.org. Printed
5、in the United States of America. 9/22/05 Page 2 of 40 ATIS-0411001-0001 Publish Date September, 2005 Notice of Disclaimer 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 interpre
6、t 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 WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR C
7、ONFORMS 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. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY
8、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 INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. 9/22/05 Page 3 of 4
9、0 Table of Contents 1. Executive Summary.5 2. Voice over Internet Protocol Overview 6 3. Scope.6 4. Call Scenarios6 4.1. Concerns and Assumptions6 4.1.1. Non-OBF Concerns.6 4.2. Call Flow Scenarios7 4.2.1. IP NNI7 4.2.1.1. VoIP Agent North America VoIP Agent North America (IP NNI).8 4.2.1.2. VoIP Ag
10、ent Wireless Phone (IP NNI) 10 4.2.2. TDM NNI12 4.2.2.1. VoIP Agent CLEC - ILEC (via Tandem) - Wireless Not Using IXC (TDM NNI).12 4.2.2.2. VoIP Agent ILEC Wireline Phone (via Tandem) (TDM NNI) .14 4.2.2.3. VoIP Agent Wireless Phone (via Tandem) (TDM NNI) .16 4.2.2.4. VoIP Agent Wireless Phone (No T
11、andem) (TDM NNI) 18 4.2.2.5. VoIP Agent LEC (via Access Tandem) (TDM NNI) .20 4.2.2.6. ILEC Wireline Phone (via Tandem) VoIP Agent (TDM NNI) .22 4.2.3. UNI Interconnection.24 4.2.3.1. VoIP Agent LEC (No Tandem) (UNI Interconnection).25 4.2.3.2. VoIP Agent CLEC IXC - ILEC (via Tandem) (UNI Interconne
12、ction).27 4.2.3.3. VoIP Agent CLEC ILEC (No Tandem) (UNI Interconnection) 29 4.2.3.4. VoIP Agent North America International TDM IXC (UNI Interconnection) 31 4.2.3.5. VoIP Agent Dialing 8YY VoIP Agent North America (UNI Interconnection)33 4.2.3.6. VoIP Agent Dialing 8YY VoIP Agent North America (UNI
13、 Interconnection)35 4.2.3.7. VoIP Agent LEC IXC - Wireless via Access Tandem (UNI Interconnection) .37 5. Acronyms and Abbreviations .39 9/22/05 Page 4 of 40 9/22/05 Page 5 of 40 1. Executive Summary Voice over Internet Protocol (also Voice over IP or VoIP) This document is a compilation of question
14、s, comments, concerns and assumptions identified by the Ordering and Billing Forum (OBF) Strategic Advisory Group (SAG) Committees VoIP Sub-team surrounding VoIP and the related challenges for intercarrier ordering and billing. An attempt is made to outline, via call flows, some of the issues and co
15、ncerns developing due to the implementation of VoIP in the absence of industry standards for VoIP business processes. With the inherent mobile nature of VoIP and the lack of regulatory response to these issues, the industry is developing and discussing issues without clear guidance or the ability to
16、 solve the ordering and billing problems that arise from carrier inter-connection. Some of the major findings include the following: There is not consensus on how to apply the rules for intercarrier compensation regarding VoIP traffic (e.g. how such traffic should be jurisdictionalized and taxed und
17、er different interconnection arrangements). Although the industry may agree on certain business processes, the information to support the processes is often not available. There is little, if any, definition of business processes that apply when interconnection makes use of an IP network-to-network
18、interface. It is realized that existing rules related to VoIP could change at any time and cause current negotiated arrangements to change. The goal is to develop standards that will minimize the impact to the Public Switched Telephone Network (PSTN) or Internet Protocol (IP)-based systems and can b
19、e easily modified or expanded to accommodate any regulatory rulings. The following items were found to be of specific interest to the OBF: As a result of Petitions submitted to the FCC related to Number Assignment for VoIP Providers, each committee will assess the impacts and work issues as needed.
20、This waiver allows non-certified companies to obtain numbering resources directly from NANPA. If the PTSC develops technical standards identifying VoIP traffic as such, the impacted committees will submit and work issues as needed. Pending further development in the area of Directory Services and Di
21、rectory Assistance, the LSOP Committee will need to ensure their processes and data exchange allow for these ancillary products. Other findings were identified but were determined to be outside the scope of OBF and are not discussed in detail within this document. 9/22/05 Page 6 of 40 2. Voice over
22、Internet Protocol Overview Voice over Internet Protocol (also Voice over IP or VoIP) is a technology for making telephone calls using an IP packet switched network for transport instead of a traditional Time Division Multiplex (TDM) circuit switched network. The method of converting voice traffic in
23、to data packets allows the delivery of voice traffic to any point on an IP network that has a valid IP address. The packet-based voice traffic can be transported with other types of data for separation at the far end. This eliminates the need for separate voice and data infrastructures, and streamli
24、nes network management and operation. VoIP uses different signaling protocols (e.g., Session Initiation Protocol (SIP) than circuit switched telephony. IP networks interconnect differently from conventional circuit switched telephone networks. As voice becomes an additional application on an IP netw
25、ork, interconnection arrangements may be expected to change although the details remain to be determined. The changes in signaling, interconnection and impacts of VoIP on business models will in turn impact carrier ordering and billing processes that are under the purview of the OBF. 3. Scope The sc
26、ope of this document is to assist in identifying the necessary interface standards to be produced by the OBF to support those ordering and billing functions that will allow interoperability for VoIP. This currently includes ordering, billing, settlements and record exchange, along with capabilities
27、needed for exchange of routing information. Once all the interface standards are identified, the VoIP Sub-team will ensure that issues are opened in the committees responsible for these requirements. 4. Call Scenarios This section deals with call scenarios developed by the VoIP Sub-team. These flows
28、 are not intended to represent all possibilities but do depict some of the most common call scenarios that were identified by the VoIP Sub-team. 4.1. Concerns and Assumptions 4.1.1. Non-OBF Concerns Communications for Law Enforcement Act (CALEA) o Will all VoIP providers be responsible for law enfor
29、cement requests and will they be held to the same level of standards as the PSTN? E911 o E911 services should be ubiquitous through all telecom providers. The public should not be responsible for opting into E911. o VoIP providers, like PSTN providers, should bear an equal share of responsibility fo
30、r maintaining the E911 system. Regardless of the platform used, providers should share in the support of public E911. Note: The E911 concerns have been addressed by the FCCs recent order. There will be a need for trouble analysis recordings. There will be a need for unified trouble reporting informa
31、tion for the purposes of trouble isolation. It is unclear whether VoIP providers will be required to contribute to the Universal Service Fund (USF) or whether the USF will be needed once VoIP is fully deployed. 9/22/05 Page 7 of 40 4.2. Call Flow Scenarios The following call flow scenarios will use
32、the icons represented on Figure 1. Some of the scenarios below are architecturally redundant. However, for purposes of identifying OBF related issues several call flows are portrayed with minor differences to allow for such analysis. Call Scenario LegendSS7NetworkIPPublic/PrivateCall Routing/Call Id
33、entificationLNPDatabaseMSCEndOfficeTandemPOTSVoice over Broadbandconnection is using aSession BorderController (IP NNI)Public or PrivateInternet ConnectionDatabase function toconvert 10 Digit E.164Numbers to DNS/URI/URL AddressPSTN SignalingSystem 7 NetworkPSTN Local NumberPortability DatabaseMobile
34、 SwitchingCenterWireless End UserPSTN Wireline EndOffice SwitchPSTN WirelineTandem Switch(Access, Local, LD)PSTN Plain OldTelephone ServiceEnd User8YYDatabasePSTN 8YY Toll FreeDatabaseVoice over Broadbandconnection is using aMedia Gateway(TDM NNI)Line that separatesService ProvidersNetworkServerVoIP
35、 AgentSessionBorderControlerServerVoIP AgentMediaGatewayIMSIP MultimediaSubsystemFigure 1 4.2.1. IP NNI IP Network-to-Network Interface - Standardization of the IP NNI is currently work in progress, for example, in the PTSC-SAC. Exchange of traffic over such an interface does not appear to be regula
36、ted and the intercarrier compensation regime is putatively bill and keep. The PTSC liaison of December 6, 2004 notes that the current ASR process does not support such direct IP interconnection, and processes will be required that allow carriers to identify IP Point of Interfaces (POIs) for central
37、office codes and Carrier Identification Codes (CICs). A further analysis of interconnection topologies is needed to drive new Access Service Request (ASR) requirements. 9/22/05 Page 8 of 40 4.2.1.1. VoIP Agent North America VoIP Agent North America (IP NNI) Call flow depicts two VoIP service provide
38、rs making a pure VoIP call without interface with the PSTN network. The call routing/call identification function that returns a URI designating the POI for call delivery from SP A to SP B could be public or a proprietary arrangement between VoIP providers. This drawing depicts one point of interfac
39、e, a VoIP provider to a VoIP Provider, no TDM. IPPublic/PrivateVoIP Agent North America - VoIP Agent North AmericaService Provider A Service Provider BSIP/H323(R2)(R1)Call Routing/Call IdentificationCall Routing/Call IdentificationServerSessionBorderControlerVoIP AgentServer VoIP AgentSession Border
40、ControlerFigure 2 OBF Concerns The geographic location of the VoIP end user may become available once VoIP E911 is implemented. It is not certain this information will be available for billing purposes. How is Local Number Portability (LNP) dealt with when IP Network-to-Network Interface (NNI) is in
41、volved? Quality of Service (QoS) measurements may be needed for Service Level Agreements (SLA) between service providers. Subscriber authentication and identification of E.164 numbers would be the responsibility of the VoIP provider originating the call. There may be a need to have a better associat
42、ion of the calling party to the billed entity. This scenario addresses the request the OBF Interconnection Service Ordering and Provisioning (ISOP) Committee received from the PTSC. This requires the originating provider to be able to identify with Service Provider Bs Point of Interconnection (POI).
43、 There is a concern with the advent of VoIP and whether the ability to rate, route, and derive ownership of a call by Country Code NPA/NXX will be compromised by the dynamic distribution of E.164 numbers by VoIP providers. OBF Assumptions Call routing/call identification is required by Service Provi
44、der (SP) B (this may be a proprietary function) in order to identify the target user and complete the call. Call routing/call identification is required between the providers in order to identify the Carrier of Record (COR) and the terminating route and complete the call. Scenario assumes “bill and
45、keep”. 9/22/05 Page 9 of 40 The call recording may be of a proprietary nature. The use (development) of a standard record may need to be considered. ATIS Telecom Management and Operations Committee (TMOC) is working on developing this intra-provider record standard in conjunction with input from IPD
46、R.org. Is record exchange required between SP A and SP B? If so, the requirements will need to be developed by OBF in conjunction with IPDR.org. Drawing depicts E.164 dialing. Recording Points (R1) Recording made to bill originating end user if needed. o Originating-RADIUS/Diameter, IPDR, CDR or oth
47、er proprietary recording (R2) Recording made to bill terminating end user if needed. o Terminating-RADIUS/Diameter, IPDR, CDR or other proprietary recording Ordering Points Ordering issues have been identified. Additional ordering work will need to take place following the PTSC and technical committ
48、ees identifying the IP NNI requirements. Record Exchange There is currently no industry standard record exchange format. o Note: The IPDR format could be developed using the IPDR frame work or the existing EMI record format used to designate IP originated traffic. 9/22/05 Page 10 of 40 4.2.1.2. VoIP
49、 Agent Wireless Phone (IP NNI) Call flow depicts two VoIP service providers making a VoIP call without interface with the PSTN network. In this call, SP B receives the call via an IP network and completes the call within its own network to the wireless customer via an IMS network. The call routing/call identification function that returns a U
