Professional Documents
Culture Documents
Contents
Role of Session Border Control in todays networks Border Control test challenges and test tool requirements NGN and IMS SBC architectures and function overview Hammer test tools for Border Control devices and functions Test Scenarios: Autonomous SBC Testing Distributed SBC testing A-BGF, C-BGF, and I-BGF Testing I-BCF Testing IWF Testing RACF/PDF Testing Hammer testing solution features and specifications
Testing Session Border Control in NGN and IMS Environments with Hammer from Empirix
Session Border Controllers in Todays Networks
Session Border Controllers, or SBCs, play a critical role in a variety of VoIP network architectures. SBCs are commonly used to act as a VoIP-aware firewall to assist with network peering and NAT traversal. In NGN and IMS networks, SBCs are increasingly used for more advanced functionality, such as: Core network protection and security Access network resource and admission control Policy coordination and control VoIP protocol interworking SBCs are available in a variety of architectures and for different network sizes and needs. Several vendors offer stand-alone SBCs with specialized variants for different network sizes and/or Access or Peer-Interconnected networks. In addition, SBCs may be specialized for signaling and media control and manipulation. Several other vendors also incorporate SBC functionality into other gateway and switching devices. The IMS standards further decompose SBCs and border devices into several distinct elements. These functions may be integrated into a single SBC or located in several different physical devices in a Distributed SBC.
SBC Architectures
SBCs may be deployed in a variety of physical architectures. As shown in Figure 1, the most basic SBC architecture involves a single, fully integrated SBC that operates independently and performs all border control functionality within the single device. As border control requirements became more sophisticated and VoIP networks grew more complex, the SBC evolved into a distributed form, with a controller that directs the activities of one or more Border Elements (SBE) or Border Gateway devices. As Figure 2 illustrates, the Border Elements/Gateways interface with the public/untrusted network and are controlled by a MGC or softswitch, typically via H.248. The Border Element/Gateway opens and closes pin-holes and passes VoIP Signaling information to the Controller for processing there. Media information is handled at the edge and may not be passed to the core, allowing for better resource utilization and scalability.
SBCs may be further decomposed into additional elements in NextGeneration networks, giving them additional border control capabilities and allowing for a wider variety of physical-deployment options. IMS specifications define several distinct border control functions such as: Border Gateway Functions (BGF) Physical interfaces to other networks (including firewalling, NAT traverals, and other options like media transcoding) Access Border Gateway Functions (A-BGF) or Core Border Gateway Function (C-BGF) - specialzed BGFs for mediating connectivity between the core and the operators own fixed and wireless access networks Interconnect Border Gateway Function (I-BGF) specialized Figure 2- Distributed SBC BGFs for connecting to external peer IP networks Interconnect Border Control Functions (I-BCF) - Controllers of I-BGF devices Policy Decision Function (PDF) or Serving Policy Decision Function (SPDF) Control of network policies for bearer access Resource and Admission Control Function (RACF) Enforcing network access and controlling bandwith Interworking Function (IWF) - Network signaling and protocol interworking Call/session Control Functions (CSCF) Control of SIP session establishment and communication Proxy Call/Session Control Function (P-CSCF) SIP proxy and initial entry to/from the IMS core Interrogating Call/Session Control Function (I-CSCF) Toplogy hiding and to connect different internal and external domains Other standardization and industry groups, such as ETSI TISPAN and the Multi Service Forum (MSF) specifiy very similar architectures but may have different names and descriptions for some of these functions. In addition, there are significant differences in Border architecture across the various versions of 3GPP IMS, each of which may need to be tested. Vendors may choose to integrate all of these components into a single device, but many are developing several SBC products that can function in a disaggregated manner to comply with IMS. In addition, many other non-SBC vendors are also adapting their gateway, signaling, softswitch, policy server, and access network control products to comply with these functions.
Border Element/Gateway Isolation Testing Border Elements and Gateways require a border control device or softswitch to function. In cases where it is not practical or economical to obtain one of these control devices, Hammer Device Emulation can be used to emulate the signaling from a H.248-based Border Controller or from an integrated SIP/H.248 Softswitch. The Hammer Device Emulator supports: Signaling connections across IPv4, IPv6, UDP, TCP, and TLS Supports registrar and authentication functionality Can establish hundreds of sessions per second in load mode Offers basic CLASS 5 features, and Much more.
Used in conjunction with Hammer Call Generation, the DUT can be completely surrounded for a true isolation test. Hammer Device Emulation also supports advanced negative testing, remote control, and automation.
All the Hammer Call Generation scenarios can be run simultaneously from the same tool and same interface. The Hammer Device Emulation elements can also be collocated in the same chassis.
Interconnect Border Control Function (IBCF) Testing IBCF devices control BGF devices, may receive signaling from an Interworking Function and must interact with CSCFs in the IMS core. Hammer Device Emulation can be used to emulate H.248-based BGFs. The same Device Emulation platform can also emulate CSCF interaction over the Mw interface. Hammer Call Generation can then be used to general signaling messages as if they were coming directly from the interconnecting network, traversing the IWF, and/or coming from the IMS core itself. Figure 8 - IMS IBCF Testing
This signaling-only test setup can be used for functional testing, negative testing, or load testing of the IBCF.
Interworking Function (IWF) / Signaling Manipulation Testing The Interworking Function (IWF) converts and corrects signaling from a peer network coming into an operators core network. The same Hammer Call Generation tool can be used as both the original and terminating nodes to verify the proper signaling changes. Numerous profiles can be run simulatenously, including IMS SIP, RFC 3261 SIP, H.323, and even MGCP, NCS, or Cisco Skinny. Each protocol can also be run with modified protocol state-machines for negative tests and to simulate proprietary vendor implementations. Figure 9 - IMS IWF Testing
Policy Decision Function (PDF) and Resource and Admission Control Function (RACF) Testing The Policy Decision Function (PDF) and Resource Admission Control Functions (RACF) coordinate policy infromation via the Diameter protocol and may control a BGF via H.248. Hammer Device Emulation can be used to emulate both the Diameter and H.248 interfaces in and out of the DUT. The Hammer Device Emulation includes a Diameter state-machine that can be modified to fit specific Gq/Gq implementations.
Empirix is the leading provider of voice and Web application testing and monitoring solutions. For a complete list of offices worldwide, or to find an authorized distributor in your area, please visit www.empirix.com/contactus. 2008 Empirix. All rights reserved. All descriptions, specifications and prices are intended for general information only and are subject to change without notice. Some mentioned features are optional. All names, products, services, trademarks are used for identification purposes only and are the property of their respective organizations. LAB:OT:ANSBC: 0708
www.empirix.com