1、 ATIS-0416001-0001 Next Generation Networks Carrier Interconnection Use Cases for Ordering ATIS-0416001-0001 September 2011 - 2 - ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, e
2、ntertainment and communications industry. More than 200 companies actively formulate standards in ATIS 17 Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Archi
3、tectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Orga
4、nizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the Americ
5、an National Standards Institute (ANSI). For more information, please visit www.atis.org. ATIS 0416001-0001 NEXT GENERATION NETWORKS CARRIER INTERCONNECTION USE CASES FOR ORDERING Is an ATIS standard developed by the Ordering Solutions Committee under the ATIS Ordering and Billing Forum (OBF). Publis
6、hed by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2011 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 otherw
7、ise, 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-0416001-0001 September 2011 - 3 - Notice of Disclaimer and Limitation of Liability The information provided in this document is
8、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 regulations. No recommendation as to products or vendors is made or should be impli
9、ed. 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 INT
10、ELLECTUAL 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
11、 RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0416001-0001 September 2011 - 4 - ATIS-0416001-0001 ATIS Standard on NEXT GENERATION NETWORKS CARRIER INTERCONNECTION USE CASES FOR ORDERING Alliance for Telecommunications Industry Solutions Approved Septembe
12、r 2011 Abstract This document provides a set of scenarios and use cases that will aid the OBF in the development of standards between Operators in the NGN environment.The focus of this document is on ordering impacts for layers 3 (IP) and 5 (application, e.g., SIP). It is assumed, unless otherwise s
13、tated, that existing methods will continue to be used to address layers 1-2 connectivity.ATIS-0416001-0001 September 2011 - 5 - Next Generation Networks Carrier Interconnection Use Cases for Ordering TABLE OF CONTENTS Section Page 1 Scope, Purpose, & Application 6 1.1 Introduction 6 1.2 Background .
14、 6 1.3 Scope 6 1.4 Scope Assumptions 6 1.5 Use Case Description Template . 8 2 Normative and Informative References . 9 3 Definitions, Acronyms, & Abbreviations . 10 3.1 Terminology . 10 3.2 Definitions 10 3.3 Acronyms & Abbreviations 11 4 IP Connectivity Scenarios and Use Cases for Voice Sessions .
15、 13 4.1 IP Interconnection, Direct-Connected . 14 4.1.1 Use Case 1: IP Interconnection, Direct-Connected . 15 4.2 IP Interconnection, Direct-Connected Layers 3 and 5 with Intermediate Layer 1 and 2 Provider16 4.2.1 Use Case 2 IP Interconnection, Direct-Connected Layers 3 and 5 with Intermediate Laye
16、r 1 and 2 Provider 17 4.3 IP Interconnection, Direct-Connected Layer 5 with Intermediate Layer 3 Provider 19 4.3.1 Use Case 3 IP Interconnection, Direct-Connected Layer 5 with Intermediate Layer 3 Provider 20 4.4 IP Interconnection, Indirect-Connected Layers 3 and 5 without Business relationship bet
17、ween Originating and Terminating Operators . 22 4.4.1 Use Case 4 IP Interconnection, Indirect-Connected Layers 3 and 5 without Business relationship between Originating and Terminating Operators . 23 4.5 IP Interconnection, Indirect-Connected Layers 3 and 5 with Business relationship between Origina
18、ting and Terminating Operators . 25 4.5.1 Use Case 5 IP Interconnection, Indirect-Connected Layers 3 and 5 With Business relationship between Originating and Terminating Operators . 26 5 IP Scenarios and Uses Cases for Database Data and Multi-media 28 5.1 IP Interconnection, Database Data Services 2
19、9 5.1.1 Use Case 6 - IP Interconnection, Database Data Services . 30 5.2 IP Interconnection, Content Data Downloading/Streaming 31 5.2.1 Use Case 7 - IP Interconnection, Content Data Downloading/Streaming . 32 6 Voice over IP Interconnection utilizing Federations . 33 7 Conclusions . 34 ATIS-0416001
20、-0001 September 2011 - 6 - 1 Scope, Purpose, & Application 1.1 Introduction The Ordering and Billing Forum (OBF) determined that there is a need to identify IP-IP direct interconnection session scenarios as a starting point to being able to further develop IP ordering, billing, and settlement recomm
21、endations and standards. These IP-based service scenarios will be used as a guide in determining which ordering requirements to focus on initially. 1.2 Background The OBF met and coordinated with several ATIS technical committees to understand the technology of switching and transporting a call or d
22、ata between two IP points since late 2005. It was concluded, based on the numerous scenarios discussed, that the main scenarios need to be documented to support the further development of Ordering and Billing standards as they relate to IP-to-IP connectivity and IP services between operators. The pu
23、rpose of this document is to identify and analyze the appropriate IP-IP interconnection ordering scenarios as a basis for future standards development. Scenarios and Use Cases are critical first steps in establishing an ordering methodology. This document further extends the work detailed in ATIS-04
24、13001, Next Generation Network Operations Business and Functional Requirements for Ordering and Billing/Settlement. Consideration of Billing/Settlement in these use cases is being deferred pending the FCCs review of intercarrier compensation arrangements for VoIP, which was underway at the time this
25、 document was developed. 1.3 Scope This document provides a set of scenarios and use cases that will aid the OBF in the development of standards between Operators in the NGN environment. The document also maps the steps identified in the Scenarios and Use Cases to the appropriate TMF eTOM Operations
26、 Business Process Function 1 and the Next Generation Network Operations Business and Functional Requirements for Ordering and Billing/Settlement 2. Those steps denoted in section 4 that fall within the scope of the OBF are identified with a “*” in the OBF Scope column of the Use Case Step tables. Th
27、e focus of this document is on ordering impacts for layers 3 (IP) and 5 (application, e.g., SIP). It is assumed, unless otherwise stated, that existing methods will continue to be used to address layer 1-2 connectivity. 1.4 Scope Assumptions There are a number of options available for IP connectivit
28、y, from non-regulated to fully regulated. The orienting assumption for this document is that the terms of NGN carrier interconnection will be a matter of commercial negotiation between interconnecting parties and that parties may interconnect at a smaller number of points than is the case today for
29、circuit-switched interconnection. The ATIS Packet Technologies and Systems Committee (PTSC) created the NGN Architecture Reference Diagram in Figure 1 as a part of their work on NGN Standards. ATIS-0416001-0001 September 2011 - 7 - IP PhoneIP PhoneProviderBProviderAPSTNPSTNMG MGSS7SS7WirelessWireles
30、sMediaSignalingIP-IP NNI Interconnect Reference DiagramMG: Media GatewayBE: Border ElementNNIRouting & TranslationOAM&PBEsBEsOAM&PSIPSIPSIPSIPOAM&PFigure 1: ATIS PTSC NG-CI Network-to-Network Interface (NNI) This reference model will be used as the baseline for the Use Case models that are represent
31、ed in Sections 4 and 5. The term Border Element (BE) is utilized as defined in ATIS NGN Architecture Phase 2 5. Layers 1-5, as utilized in this document, refer to the Layers defined in the Open System Interconnection Model (OSI Model). The PTSC work has also identified at Layer 5 that the signaling
32、(SIP) and media (RTP) could be routed separately and along different paths. However, in the Use Cases defined in sections 4 and 5, the OBF assumed that the RTP media and the call control signaling transverse the same path. Additional use cases may be created at a later point to address where the two
33、 paths differ. This document focuses on one type of signaling, SIP. However, it is recognized that alternative protocols exist in addition to SIP. As other signaling and media types are more widely deployed, additional Use Cases may need to be developed. The OBF recognizes the relevance of Quality o
34、f Service (QoS) to IP Interconnections and the discussions currently being held in other SDOs. Once a QoS standards determination has been made, the OBF may consider incorporating those standards into the Use Cases in this document. ATIS-0416001-0001 September 2011 - 8 - 1.5 Use Case Description Tem
35、plate The format of the Use Cases in sections 4 and 5 is based on the template outlined in TMOC Use Case Template 8. Additionally, the Use Cases depict the linkage between the “Steps” of the Use Cases and Section 6 of ATIS-0413001, Next Generation Network Operations Business and Functional Requireme
36、nts for Ordering and Billing/Settlement 2. For the purpose of consistency, the Use Cases in this document are written from the perspective of Operator B and do not presume a specific ordering flow between operators. ATIS-0416001-0001 September 2011 - 9 - 2 Normative and Informative References 1 ITU-
37、T M.3050.2, eTOM Process Decomposition and Descriptions, (TMF, GB921 Addendum D-Release 7.1), January 2007 2 ATIS-0413001-0001, Next Generation Network Operations Business and Functional Requirements for Ordering and Billing/Settlement, January 2010. 3 ATIS Inter-Carrier VoIP Call Routing Working Gr
38、oup (IVCR-WG) Assessment & Recommendations, February 2009 (Final). 4 ATIS PTSC-NGCI Contribution 2009-066R1, November 2009 5 PTSC-SAC-2011-031R2, Clean Baseline Text for ATIS NGN Architecture Phase 2 6 PTSC-SAC-2010-027, Revised Baseline Text for IP Network-to-Network Interface (NNI) Phase 2 Standar
39、d. 7 ATIS-1000026.2008 pre-pub, Session/Border Control Functions and Requirements, prepared by PTSC-SAC 8 TMOC-AIP-2008-020, TMOC Use Case Template. 9 ITU-T Y.2233, Requirements and framework allowing accounting and charging capabilities for NGN, pre-published recommendation, June 2010. 10 ITU-T Rec
40、ommendation L.55 (03), 3.6. ATIS-0416001-0001 September 2011 - 10 - 3 Definitions, Acronyms, & Abbreviations 3.1 Terminology The word “SHALL“ will be understood as denoting a mandatory requirement. “Shall“ will be used wherever the criterion for conformance with the specific recommendation requires
41、that there be no deviation. The word “SHOULD“ shall denote a recommendation. “Should“ shall be used wherever noncompliance with the specific recommendation is permissible. The words “CONDITIONAL MANDATORY” shall denote a requirement the implementation of which is optional, but which if it is impleme
42、nted shall be implemented in the exact manner specified. The word “MAY” shall denote an optional capability that may augment the standard. The standard is fully functional without the incorporation of this optional capability. 3.2 Definitions Flow: A flow is defined as a set of IP packets passing an
43、 observation point in the network during a certain time interval. All packets belonging to a particular flow have a set of common properties. Each property is defined as the result of applying a function to the values of: 1) one or more packet header fields (e.g., destination IP address), transport
44、header fields (e.g., destination port number) or application header fields (e.g., RTP header fields). 2) one or more characteristics of the packet itself (e.g., number of MPLS labels). 3) one or more fields derived from packet treatment (e.g., next hop IP address, output interface). Hot-Potato Routi
45、ng: The practice of passing traffic to the peer network as quickly as possible. Operator: The entity that holds the legal ownership of the transport and terminating infrastructure and the associated rights-of-way or real property 10. The document uses the term Operator generically to avoid limiting
46、the scope of provisioning/ownership of resources across multiple network services. Session: Logical connection (as opposed to physical connection) between parties involved in a packet-switched based communication. NOTE This term is used for IP-based connections rather than the term “call“ that is no
47、rmally used for a connection over conventional (circuit switched) systems. A session may be composed of one or more flows 9. The term will be used to refer to both voice and data services. ATIS-0416001-0001 September 2011 - 11 - 3.3 Acronyms & Abbreviations 3GPP 3rd Generation Partnership Project AA
48、A Authentication, Authorization, Accounting ANI Application-to-Network Interface ATIS Alliance for Telecommunications Industry Solutions ATM Asynchronous Transfer Mode BE Border Element BSS Business Support Systems CNAM Calling Name CP Content Provider DBF Data Border Function ENUM Electronic Number
49、ing eTOM Enhanced Telecom Operations Map IIF IPTV Interoperability Forum IMS IP Multimedia System IP Internet ProtocolIP-IP Internet Protocol to Internet Protocol (IP-to-IP) IPDR Internet Protocol Detail Record IPSec Internet Protocol Security ITU-T International Telecommunication Union - Telecommunication IX Interconnection LIDB Line Information DataBase LNP Local Number Portability LX, where X is a number. Layer X in the standard OSI protocol stack. Example: L2 means Layer 2 (Link Layer in the OSI protocol stack) NG-ECCI
