Network function virtualization: Difference between revisions

Content deleted Content added
Bc-or-fr (talk | contribs)
No edit summary
Tags: Mobile edit Mobile web edit
Line 1:
'''Network functions virtualization''' (also '''network function virtualization''' or '''NFV''')<ref>{{Cite web | url=http://www.etsi.org/technologies-clusters/technologies/nfv |title = ETSI - Standards for NFV - Network Functions Virtualisation &#124; NFV Solutions}}</ref> is a [[network architecture]] concept that uses the technologies of IT [[virtualization]] to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create communication services.
 
NFV relies upon, but differs from, traditional server-[[virtualization]] techniques, such as those used in enterprise IT. A virtualized network function, or VNF, may consist of one or more [[virtual machines]] or [[OS-level virtualization|containers]] running different software and processes, on top of standard high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function.
 
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 Load Balancing|load balancers]], [[Firewall (computing)|firewalls]], [[Intrusion detection system|intrusion detection devices]] and [[WAN optimization|WAN accelerators]].<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>