240 likes | 394 Vues
Kevin Isacks. Vice President, SBC Product Development, Sonus kisacks@sonusnet.com. Who is. ?. VoIP Foundation of the World’s Largest Networks. Fastest Growing SBC Portfolio on the Market. Global Leader in SIP Communications. NFV and SDN. Of the two,
E N D
Kevin Isacks Vice President, SBC Product Development, Sonus kisacks@sonusnet.com
Who is ? • VoIP Foundationof the World’s Largest Networks • Fastest Growing SBC Portfolio on the Market • Global Leader in SIP Communications
NFV and SDN Of the two, Virtualization is the more fundamental advance • NFV (Network Function Virtualization) • SDN (Software-Defined Networking) Control Plane • Separating network control and data planes • Enables centralized NFV control of distributed, programmable network elements • Improved manageability • Implementing network functionality on COTS (i.e. Intel) • Improved abstraction and functional modularity • Improved economics • Improved agility Data Plane Cloud
Why is Sonus interested in NFV? Secure QoSTunnel • Interworking Application Signaling Domains • Securing Application Domains • Enabling Application Control of Network Services • When you need to communicate between applications • Large-scale security and DOS protection • When you need more than “best efforts”
SBC Initiatives that Align with NFV SBC 5200 Carrier Grade SBC SBC Application Portedto Linux / x86 Sonus SBC SBC Application Virtualized • Industry’s First Example of Carrier-Grade NFV SBC • Common Codebase & Feature Set with HW-based SBC
Technology Implications It’s no longer just about specialized hardware • Virtualize (NFV) It’s no longer about unmanageable networks • Decompose (SDN) It’s no longer just about Voice • Diversify (Video and Web Interworking & Policy) It’s no longer just about Voice • Ubiquify (Service delivery over IP) • over SIP trunks • over 3G/4G enablement
SBC Decomposition Model for NFV NFV Application Decomposition Dimensions SBC HW • Media Plane Components: L7 – Call Control Open Source, SBC HW or SDN-Enabled Router DSP Processing L3 – Media Plane Switching & Security Sonus Confidential and Proprietary
Is Open Source the Key to NFV Success? • Open Source stops single vendor silos • As an SBC vendor, we only provide part of the NFV solution • Well supported Open Source project can complete the network • Management API’s (REST) • Router, firewall and other modules • Virtual switches – QoS, traffic shaping steering • Plug into SDN
Sonus NFV SBC with Multiple Scaling Models SBC Functions Scale Together DSP Processing Scales Independently NFV APP NFV APP Specialized HW Fully Integrated SBC Fully Integrated SBC Fully Integrated SBC Fully Integrated SBC Fully Integrated SBC (less DSP) Fully Integrated SBC Fully Integrated SBC Fully Integrated SBC L3 - DSP Processing L3 - DSP Processing L3 - DSP Processing Control L7–Session Mgmnt L7–Session Mgmnt L7 – L7 – L7 – Call Control L7 – Call Control Transcoded Media Signaling Media Signaling Media All SBC Functions Scale Independently SBC Scales with SDN-Offload Transcoded Media Transcoded Media NFV APP NFV APP Control Specialized HW Specialized HW Control L3 – Switching and Routing L3 - Switching L3 - Switching & Security Signaling Signaling L3 - DSP Processing L3 - DSP Processing L3 - DSP Processing L3 - DSP Processing L3 - DSP Processing L3 - DSP Processing SDN Element Media Media L3 - Switching Specialized HW NFV APP or Specialized HW Sonus Confidential and Proprietary
Simon Dredge Metaswitch t: @dredgie
CAN TELCOS BUILD ON OPEN SOURCE? Open source success: Hundreds / thousands of carriers build on Asterisk, FreeSWITCH, Kamailio, on COTS. Scalable and Resilient: Yes - with innovations in the area of five 9’s where there are fewer models to replicate.
ON THE SHOULDERS OF GIANTS • Reference Amazon Web Services as gold standard development environment. • Follow ‘best practice’ architecture for scalable web applications. • All components to be stateless except those which are explicitly and minimally data stores • All interfaces must be open ‘service interfaces’ • No shared data stores or memory between components • No backdoors or cross component assumptions, all interfaces must be fully implemented and policed • No reinventing the wheel - reuse existing technology wherever possible • Leverage Agile iterative and incremental development software development techniques • All components to be minimal in size and scope rather than maximal • Everything to be architected (not necessarily implemented) to scale to 100M subs WEB METHODS | WEB SCALE INNOVATION REVOLUTION: AT WEB SCALE AND INTERNET VELOCITY - Google: 2 trillion searches in 2012, 200M/hr - Facebook: 2012: Users online ~1 billion mins/hr - Netflix: Streams 5B hrs per qtr, 140M mins/hr - YouTube: Serves 6B hrsa month, 500M mins/hr - Amazon: EC2 estimated at 100,000-1M servers 1. Collaborative efforts 2. Build on each others achievements 3. Give back to the community
NETWORK OPERATOR TRADE-OFFS CLOSED VENDOR SOLUTION • Free to acquire • You control features • You control velocity • Greater Freedom • COTS hardware • Effort to develop • Effort to maintain • DevOps Methods • Expensive to acquire • Vendor controls features • Vendor controls velocity • Vendor Lock-in • Often custom hardware • No development effort • Expensive to maintain • Delivered at Telco speed OPEN SOURCE COMPONENTS
WEB METHODS equals WEB SCALE • Massively scalable SIP call control implementation • Delivering IMS Core components (and more) • Designed from the ground for the Cloud • Modeled on web design patterns for scalability, reliability and security • Components kept largely stateless and storing • Long-lived state stored in clustered data stores • Currently testing at 50M + BHCA • Trusted/untrusted zones w/security groups / FW rules • Highly portable - already demonstrated on VMware, OpenStack, Windows Azure • Development system in Amazon EC2 Cloud • Projected running costs < $0.02 per subscriber / year • Released as open source in May 2013 • First VNF adopted by the CloudNFVPoC consortium
BORN FROM OPEN SOURCE ~ 70 different pieces of open source code
NO EMOTIONAL ATTACHMENTS Clustered redundant and fast long-lived SIP store, such as registration data and event subscription state independent of a single Sprout node NEED SHORT SPRINTS | EXPERIMENT | FAST FAIL 1. Memcached 2. Infinispan 3. Memcached REVERTED AND BUILT ELASTIC SCALABILITY ON TOP OF MEMCACHED
LEVERAGE OPEN SOURCE COMMUNITY Constantly open communication PROJECT BLOGS | MESSAGE BOARDS CENTRALIZED CODE REPOSITORY BRANCHES | PULL REQUESTS | FORKS
CLEARWATER TO NFV SERVICE GRAPH… Distinct components with open interfaces HSS Mirror HSS Mirror VNFC 4 VNFC 4 Load Balancer Load Balancer VNFC 1 VNFC 1 BIND VNFC’s into a Service graph by linking interfaces I-CSCF I-CSCF VNFC 2 VNFC 2 S-CSCF S-CSCF IMS Core Expose external interfaces and create package VNFC 3 VNFC 3 VNF
… BROUGHT TO LIFE IN CLOUDNFV… Models based on TM Forum Frameworxcontracts CONSORTIUM PLAYERS Data Plane Acceleration 6WIND NFV Orchestrator Dell Cloud Network Controller Contract/resource/optimizer EnterpriseWeb Quantum WAN Network Controller Overture NFV Orchestrator & WAN Cloud Network Controller DPI Telemetry / Steering Qosmos Metaswitch SBC and IMS Core VNFs Edge Access Carrier Enet Switch Edge Access
… AND INSTANTIATED WITHIN AN IETF SFC Operator Infrastructure EPC FW DPI P-CF NAT APN Mobile Network IMS Offering SBC Core P-CF APN VoLTE or RCS/MMTEL Smartphone Web service Mobile Device PGW Proxy FW LB NAT APN Internet Video service NAT Vid Op FW DPI APN OTT Video SERVICE FUNCTION CHAIN EXAMPLES APN: Access Point Name LB: Load Balancer FW: Firewall SBC: Session Border Controller EPC: Evolved Packet Core Proxy: Web Proxy DPI: Deep Packet Inspection Core: IMS Core Components P-CF: Policy & Charging Functions Vid-Op: Video Optimizer NAT: Network Address Translator Middleboxesvia VNF / VNFC Forwarding Graphs (Package)
ClearWater Geo-Redundancy European node failure European node failure EMEA Registrations SINGLE INSTANCE SPANNING EC2 EUROPE & NORTH AMERICA Total outage was 2 minutes. Easily decreased with optimizations within a private infrastructure NA & CALA Registrations Note: All existing calls remained active
Clearwater Elastic Scalability Systems starts to scale-out Calls Stopped Scales linearly with load CPU threshold met