1、 TECHNICAL REPORT ATIS-1000039 TESTING CONFIGURATION FOR IP NETWORK TO NETWORK INTERCONNECTION RELEASE 1.0 ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and commun
2、ications industry. More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Networks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operational Support. In addition, numerous Incubators,
3、 Focus and Exploratory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect, IPv6 and Convergence. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. con
4、tributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, please visit . Notice of Disclaimer 2) Media; and 3) Routing Wireless SIP device with SIP/media traffic ove
5、r wireless access; and PSTN elements with SS7/analog traffic over packet/circuit switched network access. In NGCI Release 1.0, the focus is to define an IP NNI service interface for native IP endpoints that is independent of the types of end user devices and their network access methods. Therefore,
6、only SIP devices with wireline access and SIP devices with wireless access are relevant for Release 1.0. Refer to clause 1 of this document for more information regarding the scope for both Release 1.0 and post-Release 1.0. ATIS-1000039 6 4.2 Provider Network Architecture For Release 1.0, the NGCI t
7、est configuration assumes two basic configurations for providers network architecture. A basic configuration offers a minimal view into a peering providers network across the NNI. Each configuration consists of six common elements. The locations of these elements differentiate one configuration from
8、 another. The following are the six elements and the two basic configurations. 4.2.1 SIP Server A SIP Server supports any or all of functions associated with the registration, re-direction, and proxy servers. From NGCIs perspective, the SIP Server supports the re-direct server and/or the proxy serve
9、r functions. The SIP Server is the signaling element that terminates and originates signaling traffic across the signaling interface over the NNI. The network element will be known to the interconnecting provider as the “Signaling Port.” 4.2.2 Media Endpoint A Media Endpoint represents a device that
10、 originates and terminates media traffic across the NNI. However, it may also be capable of handling local signaling traffic with other network elements within the providers own networks. However, this is outside the scope of this document. 4.2.3 Border Element A border element represents a gateway
11、for signaling and/or media traffic across network domains. A border element may be used to handle a providers inter-network traffic as well as inter-provider traffic. The functional specifications of a border element can be found in ATIS-1000026.2008. 4.2.4 Peering Edge Router A peering edge router
12、(PER) is similar to a border element, but it is functionally confined to the IP layer processing functions. The edge router serves as an IP layer gateway and is used to peer with other providers edge routers. However, the border elements behind the PER will be known to the interconnecting provider a
13、s the “Signaling Port” and the “Media Port.” 4.2.5 Advertised Routing Domain (ARD) An ARD is an IP network for which the routing information is advertised to peer networks. The network also shares a common address space with other connecting networks. 4.2.6 Unadvertised Routing Domain (URD) An URD i
14、s an IP network for which the routing information is not advertised to peer networks. IP endpoints in the URD can not exchange traffic with other IP endpoints outside the URD directly. Border elements are typically located on the edge of URD to support network address translation functions in order
15、to allow traffic exchange between the endpoints in the URD and outside networks. The IP address assignment for an URD has few limitations. Since it is not connected to any other networks, the IP endpoints in the URD can be assigned with public addresses, private addresses, or a combination of the tw
16、o. ATIS-1000039 7 4.2.7 Basic Network Configurations A basic network configuration provides a view of a providers network without exposing any unnecessary information about the providers internal/local networks. The information revealed in the basic configurations however allows the providers to cho
17、ose and negotiate the most appropriate option to connect to each other. The two basic network configurations considered in Release 1.0 are shown in Figure 2 and Figure 3 below. Additional configurations will be considered in future releases. The following disscussion on the figures focuses on the el
18、ements labebed with letters “A”, “B”, and “C”. These labels will be used to distinguish one network configuration from another across the NNI. Figure 2: Baseline Configuration (Media Endpoint Hidden) The Peering Edge Router (PER) is the front end IP network element facing the other providers network
19、s. It provides the IP network connectivity between the local ARD and the NNI. On the NNI side, the PER supports a port labeled as “A” in both Figures 2 and 3. Each port is assigned with one or more IP addresses. These addresses are used to exchange IP network routing information and forward IP traff
20、ic, among other PER functions. ATIS-1000039 8 Figure 3: Baseline Configuration (Media Endpoint Exposed) In both Figure 2 and Figure 3, the SIP Server is always connected to a URD behind a Border Element. The Border Element in both cases serve as a gateway to external SIP servers. . To ensure the SIP
21、 signaling messages across the ARD and NNI, providers may require the use of a secure protocol such as IPSec tunnel to transport the traffic. The IPSec tunnel or connection can terminate either in the border element or in a security gateway (not shown) adjacent to the Border Element. The signaling a
22、ddress to be advertised across the NNI is hosted by a port on the Border Element, and is represented by the letter “B” in both configurations. The Media Endpoint may be connected to an URD hidden behind a Border Element, in which case the Border Element would be known to the interconnecting provider
23、s as the Media Port as shown in Figure 2. Or, the Media Endpoint may not be hidden behind a separate border element, and therefore exposed by being direclty connected to an ARD and the Peering Edge Router as shown in Figure 3. In this case, the Media Port “C” in Figure 3 is the attached to the Media
24、 Endpoint. In summary, the Media Port address to be advertised (and known as the Media Port to the other providers) across the NNI may either be a port on the Border Element (Figure 2), or if the Media Endpoint is not behind a border element, then it will be a port on the (actual) Media Endpoint(s)
25、as shown in Fgure 3. In both figures, this port is labled with a letter “C”. 4.3 Service Under Test (SUT) Configurations The Test configurations are used by providers to conduct tests to verify the technical service agreement. The agreement (among other things outside the scope of this TR) consists
26、of service scenarios, protocol requirements, and parameters, which are covered in the other three companion NGCI TR documents. For Release 1.0 specifications, the test configurations on each side of the NNI are defined by a set of “logical” service ports (or ports): 1. Peering Edge Router Port; 2. S
27、IP Signaling Port; and 3. Media Port. ATIS-1000039 9 This set of ports and the basic network configurations are identified in the previous section. The information required to specify a test configuration is therefore reduced to the specification of these logical ports for voice services. The comple
28、te specification of these ports includes the protocol profiles and the selectable parameters and their values as specified during interconnection negotiation between providers. These port configuration parameters are documented in the companion NGCI TRs, including ATIS-1000040 and ATIS1000038. The v
29、alues of the fixed and selectable parameters will be specified by the providers per service agreement, which will finalize the actual design of the configuration for each test. Figure 4: Port Visibility at the NNI 4.3.1 Peering Edge Router Port This port supports IP peering functionality covering (f
30、or example) routing, control, and forwarding functions that a provider supports across an NNI. The port consists of one or more IP addresses and separate IP addresses may be assigned to handle signaling/control traffic and to forward VoIP signaling/media traffic. Facing the NNI, the port can configu
31、red using one of the two following general configurations based upon the Interconnection Method agreed upon by the two providers: 1. Private Interconnection: This configuration allows two providers to use a private dedicated layer 2 and/or layer 3 mechanism (Private Interconnection Method) to transp
32、ort IP traffic across the ATIS-1000039 10 NNI between their Peering Edge Routers via a private IP network (e.g., via a VPN). The connection will be used exclusively for the exchange of the interconnection service traffic. One or more physical links may be used to support the connection. 2. Public In
33、terconnection: This configuration allows two providers to use a public IP network to exchange service traffic. A public network refers to a routing domain shared by a large number of parties, as in the case of the Public Internet. Each provider specifies its own network links to connect to the publi
34、c network. As such, peering providers using this interconnection method may not use the same set of configuration parameters for their respective network links to connect to the public internet (or a public network). While a public network is used to support transporting of service traffic, the prov
35、iders will likely choose to specify the use of some tunneling mechanism like IPSec to protect the privacy and security of the service data transported over a public network. 4.3.2 SIP Signaling Port This port is same as the Signaling Port in the IP-IP NNI Reference Model. It is used to exchange SIP
36、messages between two providers over an NNI independent of interconnection type. The protocol requirements for the SIP traffic is specified in a companion document ATIS-1000040. Depending on the agreement between two providers, a point-to-point secured transport mechanism between their SIP Signaling
37、Ports may be used to support the privacy, authentication, authorization functions for the signaling traffic. This port consists of one or more IP addresses in an ARD - i.e., a routing domain that will be advertised across the NNI to the other provider. A provider, however, can choose to advertise only the portion of the IP routes necessary to support the service traffic to the peering providers. Additional configuration parameters such as bandwidth, message handling rate, load-balancing mechanism, etc., should also be considered, but are outside the scope of Release 1.0.
