Network Function Virtualisation (NFV) In computer science, network function virtualisation (NFV) is a network architecture concept which uses the technologies of IT virtualisation. It is used to virtualise entire classes of network node functions into building blocks that may connect, or chain together, to create communication services.
1. Fast standard hardware Software based Devices Routers, Firewalls, Broadband Remote Access Server (BRAS) A.k.a. white box implementation
2. Function Modules (Both data plane and control plane) DHCP (Dynamic Host control Protocol), NAT (Network Address Translation), Rate Limiting,
3. Virtual Machine implementation Virtual appliances All advantages of virtualization (quick provisioning, scalability, mobility, Reduced CapEx, Reduced OpEx, …)
4. Standard APIs: New ISG (Industry Specification Group) in ETSI (European Telecom Standards Institute) set up in November 2012
Virtualised Network Function (VNF) NFV relies upon, but differs from, traditional server-virtualisation techniques, such as those used in enterprise IT. A virtualised network function, or VNF, may consist of one or more virtual machines running different software and processes. They are run on top of standard high-volume servers, switches and storage, or even cloud computing infrastructure, instead of having custom hardware appliances for each network function.
Why We need NFV?
1. Virtualization: Use network resource without worrying about where it is physically located, how much it is, how it is organized, etc.
2. Orchestration: Manage thousands of devices
3. Programmable: Should be able to change behavior on the fly.
4. Dynamic Scaling: Should be able to change size, quantity
6. Visibility: Monitor resources, connectivity
7. Performance: Optimize network device utilization
9. Service Integration
10. Openness: Full choice of Modular plug-ins
NFV Framework Requirements
1. General: Partial or full Virtualization, Predictable performance
2. Portability: Decoupled from underlying infrastructure
3. Performance: as described and facilities to monitor
4. Elasticity: Scalable to meet SLAs. Movable to other servers.
5. Resiliency: Be able to recreate after failure. Specified packet loss rate, calls drops, time to recover, etc.
6. Security: Role-based authorization, authentication
7. Service Continuity: Seamless or non-seamless continuity after failures or migration.