1、1 ATIS-0300104 Including ATIS-0300109, ATIS-0300111, and ATIS-0300112 ATIS Standard on Next Generation Interconnection Interoperability Forum (NGIIF) NGN Reference Document NGN Basics, Emergency Services, NGN Testing, and Network Survivability Alliance for Telecommunications Industry Solutions Updat
2、ed June 2017 Abstract This document provides basic information regarding Next Generations Networks, as applicable to the Next Generation Interconnection Interoperability Forum (NGIIF). ATIS-0300104 ii Foreword The Alliance for Telecommunications Industry Solutions (ATIS) serves the public through im
3、proved understanding between carriers, customers, and manufacturers. The Next Generation Interconnection Interoperability Forum (NGIIF) addresses next-generation network interconnection and interoperability issues associated with emerging technologies. Specifically, it develops operational procedure
4、s which involve the network aspects of architecture, disaster preparedness, installation, maintenance, management, reliability, routing, security, and testing between network operators. In addition, the NGIIF addresses issues which impact the interconnection of existing and Next Generation Networks
5、(NGNs) and facilitate the transition to emerging technologies. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal curren
6、tly identifiable as having distinct compatibility or performance advantages. The word may denotes an optional capability that could augment the standard. The standard is fully functional without the incorporation of this optional capability. Suggestions for improvement of this document are welcome.
7、They should be sent to the Alliance for Telecommunications Industry Solutions, NGIIF, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time of consensus on this document, NGIIF, which was responsible for its development, had the following leadership: A. Hindman, NGIIF Co-Chair (Verizon Wire
8、less) R. Ryan, NGIIF Co-Chair (Comcast) ATIS-0300104 iii Table of Contents 1 Scope, Purpose, Protocol specification.8ATIS-1000009, IP Network-To-Network Interface (NNI) Standard for VoIP.9ATIS-1000026, Session Border Controller Functions and Requirements.10ATIS-1000038, Technical Parameters for IP N
9、etwork to Network Interconnection Release 1.0.111This document is available from the International Telecommunications Union. . 2This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) at . 3This document is available from ATIS at . 4This document is available fr
10、om ATIS at . 5This document is available from ATIS at . 6This document is available from the IETF . 7This document is available from ATIS at . 8This document is available from the Third Generation Partnership Project (3GPP) . 9This document is available from ATIS at . 10This document is available fr
11、om ATIS at . 11This document is available from ATIS at . ATIS-0300104 3 ATIS-1000039, Testing Configuration for IP Network to Network Interconnection Release 1.0.12ATIS-1000040, Protocol Suite Profile for IP Network to Network Interconnection Release 1.0.13ATIS-1000041, Test Suites for IP Network to
12、 Network Interconnection Release 1.0.14ATIS-1000014, VoIP Network-to-Network Interface Testing Framework.15ATIS-1000053, Emergency Telecommunications Service (ETS) Profile and Tests for IP Network-to-Network Interconnection.16ATIS-0300100, IP Network Disaster Recovery Framework.17ATIS-0300202, Inter
13、network Operations Guidelines for Network Management of the Public Telecommunications Networks under Disaster Conditions.18ATIS-0100019, NRSC Hurricane Checklist.19ATIS-0100018, NRSC Pandemic Checklist.20ITU-T Recommendation Y.2011 (10/2004), General Principles and General Reference Model for Next G
14、eneration Networks.21ITU-T Recommendation Y.2012 (04/10), Functional Requirements and Architecture of the NGN.22Executive Order No. 13618, 6 July 2012, Vol. 77, No. 133, Federal Register 40779, “Assignment of National Security and Emergency Preparedness Communications Functions,” which revoked and s
15、uperseded Executive Order No. 12472, 3 April 1984, as amended by Executive Order No. 13286 of 28 February 2003.23IETF RFC 3261, SIP: Session Initiation Protocol.24IETF RFC 5390, Requirements for Management of Overload in the Session Initiation Protocol.25In the Matter of The Development of Operation
16、al, Technical and Spectrum Requirements, For Meeting Federal, State and Local Public Safety Agency Communication Requirements Through the Year 2010, WT Docket No. 96-86, Second Report and Order FCC 00-242, July 3, 2000.263GPP TR 22.952 version 6.3.0 Release 6, Digital cellular telecommunications sys
17、tem (Phase 2+); Universal Mobile Telecommunications System (UMTS); Priority service guide.27TIA/EIA TSB16-A, Assignment of Access Overload Classes in the Cellular Telecommunications Services.2812This document is available from ATIS at . 13This document is available from ATIS at . 14This document is
18、available from ATIS at . 15This document is available from ATIS at . 16This document is available from ATIS at . 17This document is available from ATIS at . 18This document is available from ATIS at . 19This document is available from ATIS at . 20This document is available from ATIS at . 21This docu
19、ment is available from the International Telecommunications Union at . 22This document is available from the International Telecommunications Union at . 23This document is available from the Federal Register at . 24This document is available from the IETF at . 25This document is available from the I
20、ETF at . 26This document is available from the Federal Communications Commission (FCC) at . 27This document is available from 3GPP at . 28This document is available from the Telecommunications Industry Association (TIA) at . ATIS-0300104 4 3GPP TS 22.011 V3.8.0, 3rd Generation Partnership Project; T
21、echnical Specification Group Services and System Aspects; Service Accessibility (Release 1999).29CSRIC II WG-4B, Final Report, Transition to Next Generation 9-1-1, March 2011.303 Definitions, Acronyms, the nature of the specific mechanisms used depends on the networks underlying technology and trans
22、mission protocols. For communications paths that span multiple networks, the interoperation of one networks QoS control mechanisms with the control mechanisms of the other network is facilitated via standardized mappings. Some common QoS mechanisms include: Differentiated Services (DiffServ) Code Po
23、int (DSCP). QoS Class Identifier (QCI). Allocation and Retention Priority (ARP). Guaranteed Bit-Rate (GBR). Multi-Protocol Label Switching (MPLS). And others. Quality of Experience (QoE) The Quality of Experience (QoE) is the collective effect of a services performance. It determines the degree of s
24、atisfaction of a user of the service. End-to-End End-to-End refers to the flow of communications between two end points (e.g., end-user devices) and specifically implies taking into account the end points and all intervening elements. End-to-Middle End-to-Middle, also known as end-to-edge, refers to
25、 connections that take into account a single end-point, an element at the edge of a providers network (often the far edge), and all intervening elements. Middle-to-Middle Middle-to-Middle refers to portions of communications networks that are either contained within one providers transit network, or
26、 span transit networks. Single providers middle-to-middle service is confined to the boundaries of a single providers network, edge to edge. Multiple providers middle-to-middle service spans multiple providers networks, usually from one providers near edge to another providers far edge, and includes
27、 the effects of interoperability between the service providers networks. Throughput Throughput can be characterized in a variety of ways depending on context. Normally Throughput is defined in the contexts of Internet Protocol (IP) or User Datagram Protocol (UDP) throughput, and Transmission Control
28、 Protocol (TCP) throughput. IP Throughput focuses on the transmission of packets between two adjacent IP nodes (one or more lower layer devices may exist between the two IP nodes but they are transparent in the determination of throughput between the two IP nodes). Factors that determine IP Throughp
29、ut include transmission delays between the nodes and processing delay within the nodes. TCP Throughput is defined as the average rate of successful delivery of data from a source IP node to a destination IP node over a TCP network. Factors that influence IP Throughput (described above) contribute to
30、 TCP ATIS-0300104 12 Throughput. In addition, TCP Throughput is also affected by the constraints of this protocol31. As a result, throughput of TCP traffic will always be lower than the available raw (IP, or UDP) bandwidth. 6.3.2 Performance Measures Performance measures may apply to a network, or t
31、o a specific service provided by a network. 6.3.2.1 Network Performance Measures Network performance measures apply to the performance of a network without regard to any specific service. These may include the following: 1. Throughput. 2. Data errors (packet loss). 3. Latency (one-way or round-trip
32、delay). 4. Jitter (variability of latency across multiple packets). 5. And others. These network performance measures are described in more detail below: Throughput (“throughput” here refers specifically to IP Throughput) Short-term (burst) throughput: Short-term (burst) throughput is the average th
33、roughput that a user will receive during the initial, transient period of a transfer. One of the benefits of short-term (burst) throughput is its ability to characterize the throughput of a link on small data transfers. Sustainable throughput: Long-term (Sustainable) throughput is the steady-state e
34、xpected throughput that a user should receive after an initial, transient period of higher throughput. Sustainable throughput needs to be considered for both upload and download, to capture asymmetry in data transfer rates. Minimum throughput: Minimum throughput captures degradation in throughput th
35、at might result from congestion, throttling, or high network utilization. Bulk Transfer Capacity (BTC): Bulk Transfer Capacity (BTC) represents the achievable throughput by a single connection. BTC applies only to TCP connections and depends on how TCP shares bandwidth among individual TCP flows. BT
36、C is unique among throughput measurements in that it does not directly measure actual throughput, but rather the maximum throughput obtainable. Goodput Goodput is the effective transmission rate of the payload data while discounting overhead bits, control messages, re-transmissions, etc. TCP Goodput
37、 measures the number of TCP payload bytes per second that the system can transfer. 31As an illustration, the maximum size of the receive buffer of the destination IP node is limited by TCP to 65,536 bytes. Using a slow satellite path of 0.5 seconds as an example, a single TCP connection can then use
38、 only a maximum of 1.05 Mbit per second (65,536 Bytes / 0.5 seconds), regardless of the links capacity. ATIS-0300104 13 Throughput measurements often suffer from high variability due to differences in access technologies, providers traffic shaping policies, and congestion during peak hours. Addition
39、ally, the actual throughput of a TCP connection is very difficult to measure due to complicating factors such as transfer size, types of cross traffic, and the number of competing connections. As a result, BTC may be the most useful of the throughput metrics. Packet Loss Loss Rate: Loss Rate is the
40、average packet loss over a period of time. Loss Burst Length: Loss Burst Length is the average duration of a packet loss episode. Packet loss measurement is valuable in that it has implications for TCP throughput and TCP timeouts. For instance, studies have shown that the loss of even a single packe
41、t can severely degrade streaming video quality, and that bursts of loss have similarly deleterious effects on performance. Latency Round Trip Time (RTT): Round Trip Time (RTT) is the time delay between sending a packet and receiving a response. RTT can be measured by sending small UDP packets to a t
42、est node and timing the responses (while treating any response receipt delay longer than a specified threshold as packet loss). Last-Mile Latency: Last-Mile Latency is the latency between an end-user device and the first device inside a service providers network. Last-Mile Latency characterizes the
43、access link and is therefore more useful for describing short data transfers. Last-Mile Latency is a strong metric because service providers can guarantee a maximum Last-Mile Latency that users should expect even during congestion. The standard deviation of Last-Mile Latency can also be used to esti
44、mate jitter in a given segment. Latency Under Load: Latency Under Load is the actual latency that a user experiences during an upload or download. Latency Under Load reflects issues with buffer bloat, active queuing, and traffic shaping. Latency, much like throughput, can be difficult to measure due
45、 to complicating factors: The quality of access links, modem buffering, and cross-traffic in customer premise equipment all interfere with latency measurements. Jitter Maximum Jitter (i.e., maximum delay variability): Maximum Jitter is the largest value of jitter that users should experience, and in
46、dicates whether the data transmission characteristics are satisfactory for a given application. Jitter and latency are closely related, as are packet loss and throughput. 6.3.2.2 Service Performance Measures Service Performance Measures are generally specific to each service: The performance measure
47、s that apply to voice over IP (VoIP) service, for instance, are different from the performance measures that are applicable to electronic mail (e-mail). Some performance measures, however, are universal (or nearly so) across multiple services. These generic service performance measures may include t
48、he following: 1. Uplink and downlink goodput (i.e., net throughput, discounting overhead transmissions). 2. Round trip latency per transaction. 3. Data session setup time. 4. Data session setup success rate. ATIS-0300104 14 5. Percentage of failed transaction. 6. Data session drop rate. 7. Mean Opin
49、ion Score (MOS).328. And others. The purposes of Service Performance Measures are to allow the service provider to measure the users quality of experience by monitoring their services in near real time, and for identifying and responding to degradations in performance. From a service-users perspective, Service Performance Measures answer questions such as: What is the likelihood that a data session can be completed? Responsiveness, i.e., o How long does it take to connect to the server? o How long does it take to download/upload the desired information?
