Nap extras
- 1. Network Functions Virtualisation (NFV) and Software-Defined Networking (SDN) eNB SGW VM Hypervisor HW (COTS) SD SD SD R R R PDN: Internet IMS MME VM HV HW HSS VM PGW VM #1 HV HW PGW PGW VM #2 HV HW Controlled packet forwarding (e.g. OpenFlow) Benefits of SDN: • Programmable • Real-time flexibility • Centralized NW management Compute Node HV HW Spare HW Issues: • scalability • changing traffic pattern • redundancy CTRL• Start/stop/move VMs • Create/delete Networks • On-board new services • Knows NFVI resources • Knows VM image files and metadata • Measure usage MANO Management and Orchestration NFV Infrastructure (NFVI) Packet treatment based on Rules in SD: • pre-configured • requested when needed SDN Rules: ”If”: ”Then”: Packet Description: • addresses • ports • VLAN • ... Action: • routing • switching • blocking • … PGW HSS eNB EPCLTE IP Network SGW MME Network Functions (NF) MME S-PGW HSS OS HW LTE/EPC Network (4G) – Non Virtualized • specialized HW • in static locations Remember: SD SD SD SD L2 tunneling (e.g. VxLAN) SDN NFV Benefits of NFV: • Better HW resource usage • Flexible NW topology • Uses less power aaS as-a-Service CPU Central Processing Unit COTS Commercial Off-The-Shelf CTRL Control DPI Deep Packet Inspection ETSI European Telecommunications Standards Institute FW Firewall HD Hard Drive HV Hypervisor HW Hardware IMS IP Multimedia Subsystem NIC Network Interface Card OS Operating System SD SDN Device VM Virtual Machine
- 2. NFV Building Blocks PGWeNB SGW LTE/EPC Network (4G) – Non-Virtualized Internet / IMS NF NF NF • IP traffic handling • Radio mgmnt • Signalling • IP traffic handling • Signalling • IP traffic handling • Policy Control • Signalling IP IP IP IP Network (Could be SDN-Based) NFVI = Totality of all hardware and software in which VNFs are run and managed Virtualized Network Function: • ”Virtual version of legacy network node” VNF Components: • VMs that build up a VNF • Several VNFC instances can be used for increased capacity or redundancy IP VNF-3 VM VNFC…. VNFC VNF-2 VM …. VNFC HV HW HV HW VNF-1 VNFC A VNFCVNFC B VNFCVNFC C VM VM VM VM VM Paris PoP Berlin PoP Before (legacy, non-virtual) After (NFV) Note: Also known as Physical NF (PNF) HV HW HV HW eNB aaS as-a-Service CPU Central Processing Unit COTS Commercial Off-The-Shelf HD Hard Drive HV Hypervisor HW Hardware NFVI NFV Infrastructure NFVI-PoP NFVI Point-of-Presence NIC Network Interface Card NS Network Service VM Virtual Machine VNF Virtualized Network Function VNFC VNF Component VNFFG VNF Forwarding Graph
- 3. NFV Flexibility Scaling = Dynamically extend/reduce resources granted to a VNF HORIZONTAL SCALING VERTICAL SCALING LIVE MIGRATION Add/remove VNFC instances (VMs) in a VNF Modify virtual hardware of a VNFC (virtual machine) Move a VM between compute nodes without the VM noticing VNF VNFC VNFC VNFC VNF VNFC VNFC VNFC VNFC VNFC VNF VNF SCALE UP VNFC SCALE DOWN Less: • CPU • RAM • Storage More: • CPU • RAM • Storage VNFC A Complete state of the VM Compute Node X (e.g in Paris) VNFC A Compute Node Y (e.g. in London) The same VNF and VNFC! The same VNF! Complete state of the VM Move: • CPU state • RAM content • Hard drive content • IP and MAC address • TCP sessions • etc. IP Network SCALE OUT SCALE IN = a VNFC Example: Scale out a PGW because of increased traffic load GTP Signalling Virtual PGW 1 DIAMETER Signalling Virtual PGW 1 GTP Signalling DIAMETER Signalling SCALE OUT Setting up data bearers Policies and charging rules IP Router User data IP Router IP Router IP Router Tripled used data capacity Same signalling capacity Remember: Reasons for live migration: • Use less HW during low load (saves power) • Move low-latency services closer to users • O&M-related Reason for scaling: Time Load Load-balancing e.g. with DNS GTP GPRS Tunneling Protocol PGW Packet Data NW Gateway VM Virtual Machine VNF Virtual Network Function VNFC VNF Component