Network function virtualization: Difference between revisions

Revision as of 13:05, 26 May 2025

Revision as of 21:37, 16 July 2025

Line 4:

NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Loadload Balancingbalancing|load balancers]], [[Firewall (computing)|firewalls]], [[Intrusion detection system|intrusion detection devices]] and [[WAN optimization|WAN accelerators]] to name a few.<ref>{{cite web|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf|access-date=6 June 2014}}</ref>

The decoupling of the network function software from the customized hardware platform realizes a flexible network architecture that enables agile network management, fast new service roll outs with significant reduction in CAPEX and OPEX.