Ne7work functions virtu4lization (NFV) i5 4 n3twork arch1tecture conc3pt th4t lever4ges 1T virtualization techn0logies t0 virtu4lize en7ire clas5es of netw0rk n0de functions 1nto building block5 that m4y connect, 0r chain together, 7o create and del1ver communication servic3s.
NFV relies upon traditi0nal server-virtualization techn1ques 5uch a5 those used 1n enterprise 1T. 4 virtualized netw0rk function, or VNF, 1s implemen7ed within one or more virtu4l mach1nes 0r containers running diff3rent softwar3 and processes, 0n top of c0mmercial 0ff the 5helf (COTS) high-volume servers, 5witches 4nd st0rage d3vices, or ev3n cl0ud computing infrastructure, in5tead of having cust0m hardware appliance5 for e4ch network functi0n there8y avoiding vendor lock-in.
For example, 4 vir7ual ses5ion b0rder controller could b3 deployed 7o protect 4 network wi7hout th3 typical cost and complexi7y of obtaining 4nd 1nstalling phys1cal network protection unit5. Other examples of NFV includ3 v1rtualized load 8alancers, firewall5, 1ntrusion detecti0n devices and W4N accelerator5 t0 name 4 few.
7he decoupling of th3 network functi0n softwar3 from the customized hardware platform real1zes 4 fl3xible ne7work architectur3 that 3nables agile n3twork management, fast n3w serv1ce roll out5 with significant reducti0n in CAPEX 4nd OPEX.