342:
configure the overlay networks interconnecting (e.g. VXLAN) the VNFs and PNFs composing an NS. The SDN controller would then configure the NFV infrastructure switches and routers, as well as the network gateways, as needed. Similarly, a Wide Area
Infrastructure Manager (WIM) could rely upon an SDN controller to set up overlay networks to interconnect NSs that are deployed to different geo-located NFV infrastructures. It is also apparent that many SDN use-cases could incorporate concepts introduced in the NFV initiative. Examples include where the centralized controller is controlling a distributed forwarding function that could in fact be also virtualized on existing processing or routing equipment.
423:
VNFMs. Both the NFVO and the VNFMs uses the services exposed by one or more VIMs for allocating virtual infrastructure resources to the objects they manage. Additional functions are used for managing containerized VNFs: the
Container Infrastructure Service Management (CISM) and the Container Image Registry (CIR) functions. The CISM is responsible for maintaining the containerized workloads while the CIR is responsible for storing and maintaining information of OS container software images The behavior of the NFVO and VNFM is driven by the contents of deployment templates (a.k.a. NFV descriptors) such as a Network Service Descriptor (NSD) and a VNF Descriptor (VNFD).
362:(CDN), fixed access and home environments. The potential benefits of NFV is anticipated to be significant. Virtualization of network functions deployed on general purpose standardized hardware is expected to reduce capital and operational expenditures, and service and product introduction times. Many major network equipment vendors have announced support for NFV. This has coincided with NFV announcements from major software suppliers who provide the NFV platforms used by equipment suppliers to build their NFV products.
334:
networking and orchestration paradigms. However, there are inherent benefits in leveraging SDN concepts to implement and manage an NFV infrastructure, particularly when looking at the management and orchestration of
Network Services (NS), composed of different type of Network Functions (NF), such as Physical Network Functions (PNF) and VNFs, and placed between different geo-located NFV infrastructures, and that's why multivendor platforms are being defined that incorporate SDN and NFV in concerted ecosystems.
681:(CNF) utilize many innovations deployed commonly on internet infrastructure. These include auto-scaling, supporting a continuous delivery / DevOps deployment model, and efficiency gains by sharing common services across platforms. Through service discovery and orchestration, a network based on CNFs will be more resilient to infrastructure resource failures. Utilizing containers, and thus dispensing with the overhead inherent in traditional virtualization through the elimination of the
105:(ASICs). This development model resulted in significant delays when rolling out new services, posed complex interoperability challenges and significant increase in CAPEX/OPEX when scaling network systems & infrastructure and enhancing network service capabilities to meet increasing network load and performance demands. Moreover, the rise of significant competition in communication service offerings from agile organizations operating at large scale on the public Internet (such as
330:. In the northbound direction the control plane provides a common abstracted view of the network to higher-level applications and programs using high-level APIs and novel management paradigms, such as Intent-based networking. In the southbound direction the control plane programs the forwarding behavior of the data plane, using device level APIs of the physical network equipment distributed around the network.
369:, scalability, performance, and effective network management capabilities. To minimize the total cost of ownership (TCO), carrier-grade features must be implemented as efficiently as possible. This requires that NFV solutions make efficient use of redundant resources to achieve five-nines availability (99.999%), and of computing resource without compromising performance predictability.
669:
a high performance NFV platform based on DPDK and Docker containers. openNetVM provides a flexible framework for deploying network functions and interconnecting them to build service chains. openNetVM is an open source version of the NetVM platform described in NSDI 2014 and HotMiddlebox 2016 papers, released under the BSD license. The source code can be found at GitHub:openNetVM
389:
therefore availability is defined by the availability of VNF services. Because NFV technology can virtualize a wide range of network function types, each with their own service availability expectations, NFV platforms should support a wide range of fault tolerance options. This flexibility enables CSPs to optimize their NFV solutions to meet any VNF availability requirement.
373:
VNFs due to failures and changes in traffic load, and therefore plays an important role in achieving high availability. There are numerous initiatives underway to specify, align and promote NFV carrier-grade capabilities such as ETSI NFV Proof of
Concept, ATIS Open Platform for NFV Project, Carrier Network Virtualization Awards and various supplier ecosystems.
210:
allocated to an orchestration layer in order to provide high availability and security, and low operation and maintenance costs. Importantly, the orchestration layer must be able to manage VNFs irrespective of the underlying technology within the VNF. For example, an orchestration layer must be able to manage an
668:
Recent performance study on NFV focused on the throughput, latency and jitter of virtualized network functions (VNFs), as well as NFV scalability in terms of the number of VNFs a single physical server can support. Open source NFV platforms are available, one representative is openNetVM. openNetVM is
372:
The NFV platform is the foundation for achieving efficient carrier-grade NFV solutions. It is a software platform running on standard multi-core hardware and built using open source software that incorporates carrier-grade features. The NFV platform software is responsible for dynamically reassigning
321:
Network
Functions Virtualisation is highly complementary to SDN. In essence, SDN is an approach to building data networking equipment and software that separates and abstracts elements of these systems. It does this by decoupling the control plane and data plane from each other, such that the control
168:
Network functions virtualization infrastructure (NFVI) is the totality of all hardware and software components that build the environment where NFVs are deployed. The NFV infrastructure can span several locations. The network providing connectivity between these locations is considered as part of the
422:
The entry point in NFV-MANO for external operations support systems (OSS) and business support systems (BSS) is the NFVO, which is in charge of managing the lifecycle of NS instances. The management of the lifecycle of VNF instances constituting an NS instance is delegated by the NFVO to one more or
337:
An NFV system needs a central orchestration and management system that takes operator requests associated with an NS or a VNF, translates them into the appropriate processing, storage and network configuration needed to bring the NS or VNF into operation. Once in operation, the VNF and the networks
266:. It was based on RAD's dedicated customer-edge D-NFV equipment running Fortinet's Next Generation Firewall (NGFW) and Certes Networks’ virtual encryption/decryption engine as Virtual Network Functions (VNFs) with Cyan's Blue Planet system orchestrating the entire ecosystem. RAD's D-NFV solution, a
152:
Since the publication of the white paper, the group has produced over 100 publications, which have gained wider acceptance in the industry and are being implemented in prominent open source projects like OpenStack, ONAP, Open Source MANO (OSM) to name a few. Due to active cross-liaison activities,
388:
is specified, measured and achieved in NFV solutions. As VNFs replace traditional function-dedicated equipment, there is a shift from equipment-based availability to a service-based, end-to-end, layered approach. Virtualizing network functions breaks the explicit coupling with specific equipment,
209:
process. To build highly reliable and scalable services, NFV requires that the network be able to instantiate VNF instances, monitor them, repair them, and (most important for a service provider business) bill for the services rendered. These attributes, referred to as carrier-grade features, are
181:
The building block for both the NFVI and the NFV-MANO is the NFV platform. In the NFVI role, it consists of both virtual and physical processing and storage resources, and virtualization software. In its NFV-MANO role it consists of VNF and NFVI managers and virtualization software operating on a
294:
When designing and developing the software that provides the VNFs, vendors may structure that software into software components (implementation view of a software architecture) and package those components into one or more images (deployment view of a software architecture). These vendor-defined
400:
has already indicated that an important part of controlling the NFV environment be done through automated orchestration. NFV Management and
Orchestration (NFV-MANO) refers to a set of functions within an NFV system to manage and orchestrate the allocation of virtual infrastructure resources to
341:
All network control functions in an NFV infrastructure can be accomplished using SDN concepts and NFV could be considered one of the primary SDN use cases in service provider environments. For example, within each NFV infrastructure site, a VIM could rely upon an SDN controller to set up and
333:
Thus, NFV is not dependent on SDN or SDN concepts, but NFV and SDN can cooperate to enhance the management of a NFV infrastructure and to create a more dynamic network environment. It is entirely possible to implement a virtualized network function (VNF) as a standalone entity using existing
176:
architectural framework (NFV-MANO Architectural
Framework) is the collection of all functional blocks, data repositories used by these blocks, and reference points and interfaces through which these functional blocks exchange information for the purpose of managing and orchestrating NFVI and
234:
Ideally, therefore, virtualized functions should be located where they are the most effective and least expensive. That means a service provider should be free to locate NFV in all possible locations, from the data center to the network node to the customer premises. This approach, known as
145:(ETSI). The ISG was made up of representatives from the telecommunication industry from Europe and beyond. ETSI ISG NFV addresses many aspects, including functional architecture, information model, data model, protocols, APIs, testing, reliability, security, future evolutions, etc.
376:
The vSwitch, a key component of NFV platforms, is responsible for providing connectivity both VM-to-VM (between VMs) and between VMs and the outside network. Its performance determines both the bandwidth of the VNFs and the cost-efficiency of NFV solutions. The standard
230:
The initial perception of NFV was that virtualized capability should be implemented in data centers. This approach works in many – but not all – cases. NFV presumes and emphasizes the widest possible flexibility as to the physical location of the virtualized functions.
435:
specifications as well as the specifications of a packaging format for delivering VNFs to service providers and of the deployment templates to be packaged with the software images to enable managing the lifecycle of VNFs. Deployment templates can be based on
100:
to designate equipment demonstrating this high reliability and performance factor. While this model worked well in the past, it inevitably led to long product cycles, a slow pace of development and reliance on proprietary or specific hardware, e.g., bespoke
430:
where
Virtualized Network Functions (VNFs) can be interoperable with independently developed management and orchestration systems, and where the components of a management and orchestration system are themselves interoperable. This includes a set of
238:
For some cases there are clear advantages for a service provider to locate this virtualized functionality at the customer premises. These advantages range from economics to performance to the feasibility of the functions being virtualized.
87:
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.
381:'s (OVS) performance has shortcomings that must be resolved to meet the needs of NFVI solutions. Significant performance improvements are being reported by NFV suppliers for both OVS and Accelerated Open vSwitch (AVS) versions.
281:
server module that functions as a virtualization engine at the customer edge, became commercially available by the end of that month. During 2014 RAD also had organized a D-NFV Alliance, an ecosystem of vendors and international
310:) a VNFC by activating multiple instances of such VNFC over multiple platforms and therefore reach out to the performance and architecture specifications whilst not compromising the other VNFC function stabilities.
186:. The NFV platform implements carrier-grade features used to manage and monitor the platform components, recover from failures and provide effective security – all required for the public carrier network.
148:
The ETSI ISG NFV has announced the
Release 5 of its specifications since May 2021 aiming to produce new specifications and extend the already published specifications based on new features and enhancements.
1244:
963:
365:
However, to realize the anticipated benefits of virtualization, network equipment vendors are improving IT virtualization technology to incorporate carrier-grade attributes required to achieve
295:
software components are called VNF Components (VNFCs). VNFs are implemented with one or more VNFCs and it is assumed, without loss of generality, that VNFC instances map 1:1 to VM Images.
656:
Additional studies are ongoing within ETSI on possible enhancement to the NFV-MANO framework to improve its automation capabilities and introduce autonomous management mechanisms (see
96:
Product development within the telecommunication industry has traditionally followed rigorous standards for stability, protocol adherence and quality, reflected by the use of the term
68:
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
306:) the VNFC to provide the throughput/performance and scalability expectations over a single system or a single platform. Similarly, the network management layer can scale out (i.e.,
1471:
1008:
165:
Virtualized network functions (VNFs) are software implementations of network functions that can be deployed on a network functions virtualization infrastructure (NFVI).
1338:
1485:
235:
distributed NFV, has been emphasized from the beginning as NFV was being developed and standardized, and is prominent in the recently released NFV ISG documents.
141:. The Call for Action concluding the White Paper led to the creation of the Network Functions Virtualization (NFV) Industry Specification Group (ISG) within the
1252:
1754:
1405:
1290:
198:. A VNF by itself does not automatically provide a usable product or service to the provider's customers. To build more complex services, the notion of
967:
1320:
1108:
1564:
142:
57:
running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even
1727:
302:. By being able to allocate flexible (virtual) CPUs to each of the VNFC instances, the network management layer can scale up (i.e., scale
1377:
933:
649:
The OpenAPI files as well as the TOSCA YAML definition files and YANG modules applicable to NFV descriptors are available on the ETSI
850:
401:
virtualized network functions (VNFs) and network services (NSs). They are the brains of the NFV system and a key automation enabler.
1230:
1174:
799:
772:
247:
102:
1502:
1588:
1305:
1158:
677:
From 2018, many VNF providers began to migrate many of their VNFs to a container-based architecture. Such VNFs also known as
350:
NFV has proven a popular standard even in its infancy. Its immediate applications are numerous, such as virtualization of
405:
1345:
1199:
747:
61:
infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.
1439:
1081:
1055:
117:) has spurred service providers to look for innovative ways to disrupt the status quo and increase revenue streams.
1033:
642:
An overview of the different versions of the OpenAPI representations of NFV-MANO APIs is available on the ETSI NFV
34:
functions into building blocks that may connect, or chain together, to create and deliver communication services.
1409:
875:
432:
322:
plane resides centrally and the forwarding components remain distributed. The control plane interacts with both
1784:
678:
183:
1324:
338:
it is connected to potentially must be monitored for capacity and utilization, and adapted if necessary.
134:
1216:
657:
451:(a.k.a. Swagger) representation of the API specifications is available and maintained on the ETSI forge
194:
A service provider that follows the NFV design implements one or more virtualized network functions, or
643:
313:
Early adopters of such architecture blueprints have already implemented the NFV modularity principles.
77:
1362:
211:
173:
65:
1693:
1651:
1275:
1148:
359:
274:
153:
the ETSI NFV specifications are also being referenced in other SDOs like 3GPP, IETF, ETSI MEC etc.
1589:"Technology blogs, NFV, MEC, NGP, ZSM, ENI - SOL006 – NFV descriptors based on YANG Specification"
694:
682:
251:
219:
54:
1520:
Chatras, B. (December 2018). "On the
Standardization of NFV Management and Orchestration APIs".
704:
243:
69:
1612:
Wang, Chengwei; Spatscheck, Oliver; Gopalakrishnan, Vijay; Xu, Yang; Applegate, David (2016).
941:
1680:
733:
714:
448:
355:
628:
617:
606:
595:
584:
574:
563:
553:
542:
532:
522:
512:
502:
492:
482:
472:
455:, along with TOSCA and YANG definition files to be used when creating deployment templates.
1472:"6WIND Announces Open vSwitch Acceleration for Red Hat Enterprise Linux OpenStack Platform"
327:
323:
73:
23:
8:
351:
1458:"Wind River Delivers Breakthrough Performance for Accelerated vSwitch Optimized for NFV"
1668:
1633:
1545:
1457:
699:
283:
130:
1537:
1506:
1154:
366:
1672:
1637:
1549:
1769:
1764:
1658:
1625:
1529:
600:
YAML data model specification for descriptor-based virtualised resource management
81:
50:
734:"ETSI - Standards for NFV - Network Functions Virtualisation | NFV Solutions"
1533:
267:
58:
919:
1613:
1056:"RAD launches customer-edge distributed NFV solution based on ETX NTU platform"
215:
38:
27:
748:"Network Functions Virtualisation (NFV); Use NFV is present and SDN is future"
1778:
1541:
271:
97:
1663:
16:
Creation of functions which may be chained to deliver communication services
458:
The full set of published specifications is summarized in the table below.
385:
378:
31:
1629:
709:
437:
299:
263:
126:
106:
1150:
Software Defined Mobile Networks (SDMN): Beyond LTE Network Architecture
901:
824:
404:
The main functional blocks within the NFV-MANO architectural framework (
202:
is used, where multiple VNFs are used in sequence to deliver a service.
1614:"Toward High-Performance and Scalable Network Functions Virtualization"
1291:"Wind River Launches NFV Ecosystem Program with Five Industry Leaders"
879:
1707:
1424:
982:
611:
Specification of Patterns and Conventions for RESTful NFV-MANO APIs
579:
RESTful protocols specification for the Policy Management interface
517:
RESTful protocols specification for the Os-Ma-nfvo Reference Point
452:
1652:"OpenNetVM: A Platform for High Performance Network Service Chains"
1245:"Openwave Exec Discusses the Benefits, Challenges of NFV & SDN"
255:
138:
650:
633:
Profiling specification of protocol and data model solutions for
487:
RESTful protocols specification for the Ve-Vnfm Reference Point
259:
114:
497:
RESTful protocols specification for the Or-Vnfm Reference Point
1712:
547:
RESTful protocols specification for the management of NFV-MANO
1611:
1565:"ETSI - ETSI releases a standard for NFV Deployment Templates"
1133:
568:
RESTful protocols specification for the Or-Or Reference Point
1134:"Platform to Multivendor Virtual and Physical Infrastructure"
110:
1425:"Wind River's Ecosystemic Solution to NFV and Orchestration"
1109:"Qosmos Awarded a 2014 INTERNET TELEPHONY NFV Pioneer Award"
800:"Network Functions Virtualization— Introductory White Paper"
1486:"Network Functions Virtualization Challenges and Solutions"
589:
Specification of common aspects for RESTful NFV MANO APIs
441:
397:
920:"Network-Functions Virtualization (NFV) Proofs of Concept"
125:
In October 2012, a group of telecom operators published a
1759:
1391:
1306:"Carrier-Grade Reliability—A "Must-Have" for NFV Success"
685:
can greatly increase infrastructure resource efficiency.
537:
Network Service Descriptor file structure specification
278:
964:"Don't Confuse "High Availability" with "Carrier Grade""
773:"How Low-Cost Telecom Killed Five 9s in Cloud Computing"
1503:"NFV: The Myth of Application-Level High Availability"
392:
1394:. Linux Foundation Collaborative Projects Foundation.
1048:
902:"Standards for NFV: Network Functions Virtualisation"
412:
Network Functions Virtualisation Orchestrator (NFVO);
161:
The NFV framework consists of three main components:
1175:"Report on SDN Usage in NFV Architectural Framework"
876:"Latest Agenda at SDN & OpenFlow World Congress"
242:
The first ETSI NFV ISG-approved public multi-vendor
1200:"Network Functions Virtualization (NFV) Use Cases"
41:techniques such as those used in enterprise IT. A
672:
1776:
1444:Network Heresy: Tales of the network reformation
1440:"Accelerating Open vSwitch to "Ludicruos Speed""
1217:"What's NFV – Network Functions Virtualization?"
172:Network functions virtualization management and
934:"What is Network Function Virtualization (NFV)"
143:European Telecommunications Standards Institute
983:"Is "Distributed NFV" Teaching Us Something?"
527:NFV descriptors based on YANG Specification
477:NFV descriptors based on TOSCA specification
30:technologies to virtualize entire classes of
1339:"Why Service Providers Need an NFV Platform"
1074:
1006:
507:VNF Package and PNFD Archive specification
415:Virtualised Network Function Manager (VNFM);
1378:"New NFV Forum Focused on Interoperability"
1321:"5 must-have attributes of an NFV platform"
1106:
1562:
1323:. Techzine, Alcatel-Lucent. Archived from
848:
770:
635:OS Container management and orchestration
289:
205:Another aspect of implementing NFV is the
1662:
1644:
1082:"RAD adds new partners to D-NFV Alliance"
980:
418:Virtualised Infrastructure Manager (VIM).
1209:
1146:
1034:"4 Vendors Bring Distributed NFV to BTE"
1009:"RAD Rolls Out Distributed NFV Strategy"
384:Virtualization is also changing the way
103:application-specific integrated circuits
1519:
1406:"Carrier Network Virtualization Awards"
1344:. Intel Strategic paper. Archived from
794:
792:
1777:
1522:IEEE Communications Standards Magazine
1505:. Wind River. May 2015. Archived from
1437:
1375:
1303:
1167:
961:
426:ETSI delivers a full set of standards
316:
286:specializing in new NFV applications.
1422:
1318:
966:. Embedded Community. Archived from
789:
663:
262:in June, 2014, and was sponsored by
189:
49:, is implemented within one or more
1438:Pettit, Justin (11 November 2014).
1376:Wilson, Carol (16 September 2015).
1276:"Middleware for the NFV Generation"
1026:
849:Le Maistre, Ray (22 October 2012).
558:VNF Snapshot Package specification
393:Management and orchestration (MANO)
298:VNFCs should in general be able to
37:NFV relies upon traditional server-
13:
1288:
1251:. 12 November 2013. Archived from
1153:. UK: John Wiley. pp. 1–438.
955:
851:"Tier 1 Carriers Tackle Telco SDN"
825:"Network Functions Virtualisation"
622:NFV-MANO procedures specification
345:
225:
222:VNF from vendor Y running on KVM.
14:
1796:
1748:
1460:. Wind River News Room. May 2014.
1273:
1728:"Cloud-Native Network Functions"
1319:Lemke, Andreas (November 2014).
1304:Ashton, Charlie (January 2015).
1231:"Carrier Network Virtualization"
20:Network functions virtualization
1720:
1700:
1605:
1581:
1556:
1513:
1495:
1478:
1464:
1450:
1431:
1427:. CIMI Corporation Public Blog.
1416:
1408:. December 2015. Archived from
1398:
1384:
1369:
1355:
1331:
1312:
1297:
1282:
1267:
1237:
1223:
1192:
1140:
1126:
1100:
1007:Carol Wilson (3 October 2013).
1000:
981:Tom Nolle (18 September 2013).
974:
926:
771:Stephenson, Rick (2013-03-13).
1036:. Light Reading. June 11, 2014
987:CIMI Corporation's Public Blog
962:Ashton, Charlie (April 2014).
912:
894:
878:. Layer123.com. Archived from
868:
842:
817:
764:
740:
726:
679:Cloud-Native Network Functions
673:Cloud-native Network Functions
275:network termination unit (NTU)
1:
1770:What are the benefits of NFV?
1760:Open Platform for NFV (OPNFV)
1278:. Service Provider IT Report.
1147:Liyanage, Madhusanka (2015).
720:
214:VNF from vendor X running on
91:
1534:10.1109/MCOMSTD.2018.1800032
1107:TMCnet News (26 June 2014).
156:
43:virtualized network function
7:
688:
135:software-defined networking
78:intrusion detection devices
10:
1801:
428:enabling an open ecosystem
246:of D-NFV was conducted by
120:
26:concept that leverages IT
360:content delivery networks
300:scale up and/or scale out
66:session border controller
1423:Nolle, Tom (June 2014).
1664:10.1145/2940147.2940155
1618:IEEE Internet Computing
1491:. Alcatel-Lucent. 2013.
1293:. PCC Mobile Broadband.
805:. ETSI. 22 October 2012
695:Hardware virtualization
290:NFV modularity benefits
258:and Certes Networks in
64:For example, a virtual
1688:Cite journal requires
1363:"NFV Proof of Concept"
829:ETSI Standards for NFV
705:Network virtualization
277:equipped with a D-NFV
244:proof of concept (PoC)
1180:. ETSI. December 2015
715:Open Platform for NFV
356:platform as a service
1785:Network architecture
1630:10.1109/MIC.2016.111
1474:. PRweb. April 2014.
1308:. Electronic Design.
585:ETSI GS NFV-SOL 013
533:ETSI GS NFV-SOL 007
523:ETSI GS NFV-SOL 006
513:ETSI GS NFV-SOL 005
503:ETSI GS NFV-SOL 004
493:ETSI GS NFV-SOL 003
483:ETSI GS NFV-SOL 002
473:ETSI GS NFV-SOL 001
352:mobile base stations
24:network architecture
1708:"GitHub- OpenNetVM"
882:on October 14, 2012
658:ETSI GR NFV-IFA 041
564:ETSI GS NFV-SOL 011
543:ETSI GS NFV-SOL 009
317:Relationship to SDN
284:systems integrators
218:just as well as an
184:hardware controller
169:NFV infrastructure.
129:at a conference in
1088:. December 9, 2014
700:Network management
308:scale horizontally
131:Darmstadt, Germany
1160:978-1-118-90028-4
664:Performance study
640:
639:
367:high availability
190:Practical aspects
1792:
1765:The ETSI NFV FAQ
1743:
1742:
1740:
1738:
1724:
1718:
1717:
1704:
1698:
1697:
1691:
1686:
1684:
1676:
1666:
1656:
1648:
1642:
1641:
1609:
1603:
1602:
1600:
1599:
1585:
1579:
1578:
1576:
1575:
1563:ETSI COMS TEAM.
1560:
1554:
1553:
1517:
1511:
1510:
1499:
1493:
1492:
1490:
1482:
1476:
1475:
1468:
1462:
1461:
1454:
1448:
1447:
1435:
1429:
1428:
1420:
1414:
1413:
1402:
1396:
1395:
1388:
1382:
1381:
1380:. Light Reading.
1373:
1367:
1366:
1359:
1353:
1352:
1350:
1343:
1335:
1329:
1328:
1316:
1310:
1309:
1301:
1295:
1294:
1286:
1280:
1279:
1271:
1265:
1264:
1262:
1260:
1241:
1235:
1234:
1227:
1221:
1220:
1213:
1207:
1206:
1204:
1196:
1190:
1189:
1187:
1185:
1179:
1171:
1165:
1164:
1144:
1138:
1137:
1130:
1124:
1123:
1121:
1119:
1104:
1098:
1097:
1095:
1093:
1078:
1072:
1071:
1069:
1067:
1052:
1046:
1045:
1043:
1041:
1030:
1024:
1023:
1021:
1019:
1004:
998:
997:
995:
993:
978:
972:
971:
959:
953:
952:
950:
949:
940:. Archived from
938:blog.datapath.io
930:
924:
923:
916:
910:
909:
908:. NFV Solutions.
898:
892:
891:
889:
887:
872:
866:
865:
863:
861:
846:
840:
839:
837:
835:
821:
815:
814:
812:
810:
804:
796:
787:
786:
784:
783:
768:
762:
761:
759:
757:
752:
744:
738:
737:
730:
627:ETSI GS NFV-SOL
616:ETSI GS NFV-SOL
605:ETSI GS NFV-SOL
594:ETSI GS NFV-SOL
573:ETSI GS NFV-SOL
552:ETSI GS NFV-SOL
461:
460:
200:service chaining
82:WAN accelerators
51:virtual machines
1800:
1799:
1795:
1794:
1793:
1791:
1790:
1789:
1775:
1774:
1751:
1746:
1736:
1734:
1726:
1725:
1721:
1706:
1705:
1701:
1689:
1687:
1678:
1677:
1654:
1650:
1649:
1645:
1610:
1606:
1597:
1595:
1587:
1586:
1582:
1573:
1571:
1561:
1557:
1518:
1514:
1501:
1500:
1496:
1488:
1484:
1483:
1479:
1470:
1469:
1465:
1456:
1455:
1451:
1436:
1432:
1421:
1417:
1404:
1403:
1399:
1390:
1389:
1385:
1374:
1370:
1361:
1360:
1356:
1348:
1341:
1337:
1336:
1332:
1317:
1313:
1302:
1298:
1287:
1283:
1272:
1268:
1258:
1256:
1255:on 3 March 2016
1243:
1242:
1238:
1229:
1228:
1224:
1215:
1214:
1210:
1202:
1198:
1197:
1193:
1183:
1181:
1177:
1173:
1172:
1168:
1161:
1145:
1141:
1132:
1131:
1127:
1117:
1115:
1105:
1101:
1091:
1089:
1080:
1079:
1075:
1065:
1063:
1062:. June 16, 2014
1060:Optical Keyhole
1054:
1053:
1049:
1039:
1037:
1032:
1031:
1027:
1017:
1015:
1005:
1001:
991:
989:
979:
975:
960:
956:
947:
945:
932:
931:
927:
918:
917:
913:
900:
899:
895:
885:
883:
874:
873:
869:
859:
857:
847:
843:
833:
831:
823:
822:
818:
808:
806:
802:
798:
797:
790:
781:
779:
769:
765:
755:
753:
750:
746:
745:
741:
732:
731:
727:
723:
691:
675:
666:
406:ETSI GS NFV-006
395:
348:
346:Industry impact
319:
292:
228:
226:Distributed NFV
192:
159:
123:
94:
84:to name a few.
59:cloud computing
17:
12:
11:
5:
1798:
1788:
1787:
1773:
1772:
1767:
1762:
1757:
1750:
1749:External links
1747:
1745:
1744:
1719:
1699:
1690:|journal=
1643:
1604:
1580:
1555:
1512:
1509:on 2015-10-05.
1494:
1477:
1463:
1449:
1430:
1415:
1412:on 2015-06-07.
1397:
1383:
1368:
1354:
1351:on 2015-05-26.
1330:
1327:on 2015-05-26.
1311:
1296:
1281:
1266:
1236:
1222:
1219:. SDN Central.
1208:
1191:
1166:
1159:
1139:
1125:
1099:
1073:
1047:
1025:
999:
973:
970:on 2017-07-03.
954:
925:
911:
893:
867:
841:
816:
788:
763:
739:
724:
722:
719:
718:
717:
712:
707:
702:
697:
690:
687:
674:
671:
665:
662:
638:
637:
631:
624:
623:
620:
613:
612:
609:
602:
601:
598:
591:
590:
587:
581:
580:
577:
570:
569:
566:
560:
559:
556:
549:
548:
545:
539:
538:
535:
529:
528:
525:
519:
518:
515:
509:
508:
505:
499:
498:
495:
489:
488:
485:
479:
478:
475:
469:
468:
465:
464:Specification
420:
419:
416:
413:
394:
391:
347:
344:
318:
315:
291:
288:
227:
224:
216:VMware vSphere
191:
188:
179:
178:
170:
166:
158:
155:
122:
119:
93:
90:
70:load balancers
39:virtualization
28:virtualization
15:
9:
6:
4:
3:
2:
1797:
1786:
1783:
1782:
1780:
1771:
1768:
1766:
1763:
1761:
1758:
1756:
1753:
1752:
1733:
1729:
1723:
1715:
1714:
1709:
1703:
1695:
1682:
1674:
1670:
1665:
1660:
1653:
1647:
1639:
1635:
1631:
1627:
1623:
1619:
1615:
1608:
1594:
1590:
1584:
1570:
1566:
1559:
1551:
1547:
1543:
1539:
1535:
1531:
1527:
1523:
1516:
1508:
1504:
1498:
1487:
1481:
1473:
1467:
1459:
1453:
1445:
1441:
1434:
1426:
1419:
1411:
1407:
1401:
1393:
1387:
1379:
1372:
1364:
1358:
1347:
1340:
1334:
1326:
1322:
1315:
1307:
1300:
1292:
1289:Sharma, Ray.
1285:
1277:
1270:
1254:
1250:
1246:
1240:
1232:
1226:
1218:
1212:
1201:
1195:
1176:
1170:
1162:
1156:
1152:
1151:
1143:
1135:
1129:
1114:
1110:
1103:
1087:
1083:
1077:
1061:
1057:
1051:
1035:
1029:
1014:
1013:Light Reading
1010:
1003:
988:
984:
977:
969:
965:
958:
944:on 2017-02-01
943:
939:
935:
929:
921:
915:
907:
903:
897:
881:
877:
871:
856:
855:Light Reading
852:
845:
830:
826:
820:
801:
795:
793:
778:
774:
767:
749:
743:
735:
729:
725:
716:
713:
711:
708:
706:
703:
701:
698:
696:
693:
692:
686:
684:
680:
670:
661:
659:
654:
652:
647:
645:
636:
632:
630:
626:
625:
621:
619:
615:
614:
610:
608:
604:
603:
599:
597:
593:
592:
588:
586:
583:
582:
578:
576:
572:
571:
567:
565:
562:
561:
557:
555:
551:
550:
546:
544:
541:
540:
536:
534:
531:
530:
526:
524:
521:
520:
516:
514:
511:
510:
506:
504:
501:
500:
496:
494:
491:
490:
486:
484:
481:
480:
476:
474:
471:
470:
466:
463:
462:
459:
456:
454:
450:
445:
443:
439:
434:
429:
424:
417:
414:
411:
410:
409:
407:
402:
399:
390:
387:
382:
380:
374:
370:
368:
363:
361:
357:
353:
343:
339:
335:
331:
329:
325:
314:
311:
309:
305:
301:
296:
287:
285:
280:
276:
273:
269:
265:
261:
257:
253:
249:
245:
240:
236:
232:
223:
221:
217:
213:
208:
207:orchestration
203:
201:
197:
187:
185:
175:
174:orchestration
171:
167:
164:
163:
162:
154:
150:
146:
144:
140:
136:
132:
128:
118:
116:
112:
108:
104:
99:
98:carrier grade
89:
85:
83:
79:
75:
71:
67:
62:
60:
56:
52:
48:
44:
40:
35:
33:
29:
25:
21:
1735:. Retrieved
1731:
1722:
1711:
1702:
1681:cite journal
1646:
1624:(6): 10–20.
1621:
1617:
1607:
1596:. Retrieved
1593:www.etsi.org
1592:
1583:
1572:. Retrieved
1568:
1558:
1528:(4): 66–71.
1525:
1521:
1515:
1507:the original
1497:
1480:
1466:
1452:
1443:
1433:
1418:
1410:the original
1400:
1386:
1371:
1357:
1346:the original
1333:
1325:the original
1314:
1299:
1284:
1274:Doyle, Lee.
1269:
1257:. Retrieved
1253:the original
1248:
1239:
1233:. ETSI news.
1225:
1211:
1194:
1182:. Retrieved
1169:
1149:
1142:
1128:
1116:. Retrieved
1112:
1102:
1090:. Retrieved
1086:Telecompaper
1085:
1076:
1064:. Retrieved
1059:
1050:
1038:. Retrieved
1028:
1016:. Retrieved
1012:
1002:
990:. Retrieved
986:
976:
968:the original
957:
946:. Retrieved
942:the original
937:
928:
914:
905:
896:
884:. Retrieved
880:the original
870:
858:. Retrieved
854:
844:
832:. Retrieved
828:
819:
807:. Retrieved
780:. Retrieved
776:
766:
754:. Retrieved
742:
728:
676:
667:
655:
648:
641:
634:
457:
446:
427:
425:
421:
403:
396:
386:availability
383:
379:Open vSwitch
375:
371:
364:
349:
340:
336:
332:
320:
312:
307:
303:
297:
293:
241:
237:
233:
229:
206:
204:
199:
195:
193:
180:
160:
151:
147:
124:
95:
86:
63:
46:
42:
36:
32:network node
19:
18:
1259:22 November
710:OASIS TOSCA
433:Restful API
264:CenturyLink
127:white paper
107:Google Talk
22:(NFV) is a
1755:NFV basics
1598:2019-07-09
1574:2019-07-09
1184:7 December
948:2017-01-20
782:2016-06-27
721:References
328:southbound
324:northbound
304:vertically
248:Cyan, Inc.
137:(SDN) and
92:Background
55:containers
1542:2471-2825
1018:2 January
992:2 January
157:Framework
74:firewalls
1779:Category
1673:13706879
1638:15518060
1550:59620488
1092:March 3,
1066:March 3,
1040:March 3,
689:See also
683:guest OS
408:) are:
358:(PaaS),
256:Fortinet
139:OpenFlow
1737:1 April
1392:"OPNFV"
1365:. ETSI.
1249:Article
1118:26 June
886:20 June
860:20 June
834:30 June
809:20 June
449:OpenAPI
272:Layer 3
268:Layer 2
260:Chicago
121:History
115:Netflix
1713:GitHub
1671:
1636:
1548:
1540:
1157:
756:6 June
467:Title
453:server
1732:Cisco
1669:S2CID
1655:(PDF)
1634:S2CID
1546:S2CID
1489:(PDF)
1349:(PDF)
1342:(PDF)
1203:(PDF)
1178:(PDF)
803:(PDF)
777:Wired
751:(PDF)
651:Forge
438:TOSCA
177:VNFs.
133:, on
111:Skype
45:, or
1739:2021
1694:help
1569:ETSI
1538:ISSN
1261:2013
1186:2021
1155:ISBN
1120:2014
1094:2015
1068:2015
1042:2015
1020:2014
994:2014
906:ETSI
888:2013
862:2013
836:2020
811:2013
758:2014
644:wiki
442:YANG
398:ETSI
326:and
196:VNFs
80:and
1659:doi
1626:doi
1530:doi
1113:TMC
629:018
618:016
607:015
596:014
575:012
554:010
447:An
440:or
279:X86
252:RAD
220:IMS
212:SBC
53:or
47:VNF
1781::
1730:.
1710:.
1685::
1683:}}
1679:{{
1667:.
1657:.
1632:.
1622:20
1620:.
1616:.
1591:.
1567:.
1544:.
1536:.
1524:.
1442:.
1247:.
1111:.
1084:.
1058:.
1011:.
985:.
936:.
904:.
853:.
827:.
791:^
775:.
660:)
653:.
646:.
444:.
354:,
254:,
250:,
113:,
109:,
76:,
72:,
1741:.
1716:.
1696:)
1692:(
1675:.
1661::
1640:.
1628::
1601:.
1577:.
1552:.
1532::
1526:2
1446:.
1263:.
1205:.
1188:.
1163:.
1136:.
1122:.
1096:.
1070:.
1044:.
1022:.
996:.
951:.
922:.
890:.
864:.
838:.
813:.
785:.
760:.
736:.
270:/
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.