Outlines the objectives and scope for the NFV ISG in the next phase of work. http://www.cablelabs.com/etsi-nfv-industry-specification-group-publishes-second-release-of-documents/
Introduction to Network Function Virtualization (NFV)rjain51
Class lecture by Prof. Raj Jain on Introduction to Network Function Virtualization (NFV). The talk covers Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline, Introduction to, Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline. Video recording available in YouTube.
Andrea Pinnola
Telecom Italia
NFV-SDN Synergy
Technology Track Session
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
SDN and NFV: Facts, Extensions, and Carrier Opportunitiesrjain51
Slides of a seminar talk by Prof. Raj Jain to AT&T SDN Forum, April 10, 2014.
It is well known that software defined networking and network function virtualization are key to the future of carriers. What may not be well known is the contentious debate among the industry leaders on approaches to these. In this talk, both sides of these arguments will be presented followed by an extension to the NFV idea that should be of interest to carriers.
The second part of the talk describes our current research in the area of service chaining of globally distributed VNFs. In this presentation we describe OpenADN (Open Application Delivery Network) which allows multiple providers to chain both application-level and network-level services via VNFs distributed globally on several private/public clouds. This is similar to the "Cloud of Clouds" idea currently developing in the industry. There is immense opportunity for carriers to play the key role in this space.
This document discusses network function virtualization (NFV) and the management and orchestration (MANO) stack. It provides an overview of NFV and its benefits over traditional hardware appliances. It describes the ETSI NFV reference architecture and the roles of the main MANO components: the virtualized infrastructure manager (VIM), virtual network function manager (VNFM), and NFV orchestrator (NFVO). It notes that while the lower layers like the VIM are more standardized, there is still work being done to standardize the NFVO and its interfaces. It also discusses some open source MANO implementations and the goal of the OPNFV project to develop a reference implementation through collaboration.
Network functions virtualization (NFV) decouples network functions from proprietary hardware appliances and implements them as software virtual network functions (VNFs) that run on standard commercial off-the-shelf (COTS) servers. This allows network functions to be consolidated on shared hardware and provides benefits such as reduced costs, increased flexibility and service agility, and faster innovation. The European Telecommunications Standards Institute (ETSI) is developing open standards for NFV. Orchestration is a key enabling technology that manages the lifecycle of VNFs and coordinates their placement with physical network resources to automate service provisioning.
Network Function Virtualization : Infrastructure Overviewsidneel
This document provides an overview of network function virtualization (NFV) infrastructure, including:
- The NFV infrastructure architecture focuses on the compute, hypervisor, and infrastructure domains. The hypervisor domain provides resources and interfaces for software appliances running as virtual machines.
- NFV infrastructure principles include defining functional blocks and their interfaces, and how network functions are divided between host functions and virtual network functions after virtualization.
- The document discusses NFV infrastructure in relation to cloud computing models like SaaS, PaaS, and IaaS and covers NFV infrastructure domains, interfaces, and challenges related to performance.
1. The document discusses the convergence of IT and telecommunications (CT) infrastructure through OpenStack and network functions virtualization (NFV).
2. It provides an overview of relevant industry trends like software-defined networking and computing. It also discusses the perspectives and interests of telco operators and NFV.
3. The document identifies challenges for deploying network functions on OpenStack clouds, such as the need for cross-data center resource scheduling and affinity scheduling to meet telco application requirements for high availability. It proposes solutions like service container-based resource allocation and an application-centric networking platform.
The document discusses network function virtualization (NFV) and its benefits, challenges, and use cases. NFV aims to implement network functions through software running on commercial off-the-shelf servers and storage, to provide benefits like reduced costs, increased agility, and flexibility compared to proprietary hardware appliances. The ETSI NFV Industry Specification Group is working on requirements and an architecture for NFV. Examples of potential applications include virtualized routers, firewalls, traffic monitoring functions and mobile network nodes. Both NFV and SDN aim to make networks more programmable and automated but through different approaches.
Introduction to Network Function Virtualization (NFV)rjain51
Class lecture by Prof. Raj Jain on Introduction to Network Function Virtualization (NFV). The talk covers Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline, Introduction to, Four Innovations of NFV, Network Function Virtualization, NFV, Why We need NFV?, NFV and SDN Relationship, Mobile Network Functions, ETSI NFV ISG, NFV Specifications, NFV Architecture, NFV Concepts, Network Forwarding Graph, NFV Reference Points, NFV Framework Requirements, NFV Use Cases, NFV Proof of Concepts, PoCs, ETSI ISG Timeline. Video recording available in YouTube.
Andrea Pinnola
Telecom Italia
NFV-SDN Synergy
Technology Track Session
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
SDN and NFV: Facts, Extensions, and Carrier Opportunitiesrjain51
Slides of a seminar talk by Prof. Raj Jain to AT&T SDN Forum, April 10, 2014.
It is well known that software defined networking and network function virtualization are key to the future of carriers. What may not be well known is the contentious debate among the industry leaders on approaches to these. In this talk, both sides of these arguments will be presented followed by an extension to the NFV idea that should be of interest to carriers.
The second part of the talk describes our current research in the area of service chaining of globally distributed VNFs. In this presentation we describe OpenADN (Open Application Delivery Network) which allows multiple providers to chain both application-level and network-level services via VNFs distributed globally on several private/public clouds. This is similar to the "Cloud of Clouds" idea currently developing in the industry. There is immense opportunity for carriers to play the key role in this space.
This document discusses network function virtualization (NFV) and the management and orchestration (MANO) stack. It provides an overview of NFV and its benefits over traditional hardware appliances. It describes the ETSI NFV reference architecture and the roles of the main MANO components: the virtualized infrastructure manager (VIM), virtual network function manager (VNFM), and NFV orchestrator (NFVO). It notes that while the lower layers like the VIM are more standardized, there is still work being done to standardize the NFVO and its interfaces. It also discusses some open source MANO implementations and the goal of the OPNFV project to develop a reference implementation through collaboration.
Network functions virtualization (NFV) decouples network functions from proprietary hardware appliances and implements them as software virtual network functions (VNFs) that run on standard commercial off-the-shelf (COTS) servers. This allows network functions to be consolidated on shared hardware and provides benefits such as reduced costs, increased flexibility and service agility, and faster innovation. The European Telecommunications Standards Institute (ETSI) is developing open standards for NFV. Orchestration is a key enabling technology that manages the lifecycle of VNFs and coordinates their placement with physical network resources to automate service provisioning.
Network Function Virtualization : Infrastructure Overviewsidneel
This document provides an overview of network function virtualization (NFV) infrastructure, including:
- The NFV infrastructure architecture focuses on the compute, hypervisor, and infrastructure domains. The hypervisor domain provides resources and interfaces for software appliances running as virtual machines.
- NFV infrastructure principles include defining functional blocks and their interfaces, and how network functions are divided between host functions and virtual network functions after virtualization.
- The document discusses NFV infrastructure in relation to cloud computing models like SaaS, PaaS, and IaaS and covers NFV infrastructure domains, interfaces, and challenges related to performance.
1. The document discusses the convergence of IT and telecommunications (CT) infrastructure through OpenStack and network functions virtualization (NFV).
2. It provides an overview of relevant industry trends like software-defined networking and computing. It also discusses the perspectives and interests of telco operators and NFV.
3. The document identifies challenges for deploying network functions on OpenStack clouds, such as the need for cross-data center resource scheduling and affinity scheduling to meet telco application requirements for high availability. It proposes solutions like service container-based resource allocation and an application-centric networking platform.
The document discusses network function virtualization (NFV) and its benefits, challenges, and use cases. NFV aims to implement network functions through software running on commercial off-the-shelf servers and storage, to provide benefits like reduced costs, increased agility, and flexibility compared to proprietary hardware appliances. The ETSI NFV Industry Specification Group is working on requirements and an architecture for NFV. Examples of potential applications include virtualized routers, firewalls, traffic monitoring functions and mobile network nodes. Both NFV and SDN aim to make networks more programmable and automated but through different approaches.
The document discusses Network Functions Virtualization (NFV) and OpenStack. It provides an overview of NFV, describing what NFV is and its key benefits. It also summarizes the work completed in Phase 1 of the ETSI NFV Industry Specification Group, including published documents on NFV architecture, interfaces, and requirements. The document then presents examples of NFV proofs-of-concept involving virtualized network functions and orchestration using OpenStack. It concludes with a discussion of requirements for integrating NFV and OpenStack, such as support for multiple hypervisors, hardware acceleration, and security.
The document discusses SDN and NFV for carriers. It outlines challenges like network inflexibility and high costs, and opportunities like virtualization and software-defined networking. It provides an overview of NFV and SDN, including definitions and benefits. Use cases are presented that demonstrate how SDN and NFV can address challenges and enable new services. A phased approach is suggested for service providers to adopt NFV and SDN technologies.
KEYNOTE @ NFV World Congress 2017, San José
Francisco-Javier Ramón | Head of Network Virtualisation, GCTO | Telefónica
Chair | ETSI OSM
ABSTRACT:
- How Telefónica is architecting its new Core Network with NFV to enable the dynamic re-allocation of capacity wherever needed.
- Why orchestration is the latest technical challenge to realize this vision, and what Telefónica is doing in this space.
- How Open Source MANO (OSM) has become the reference platform for interoperability after the launch of its third release.
- How this fits into Telefónica plans for virtualization.
The document outlines topics to be discussed at an NFV BOF meeting at APRICOT 2015, including advanced NFV topics like data plane connectivity models for VNFs, overlay encapsulation for MPLS operators, NFV service assurance, service chaining, and the applicability of Linux containers. It also includes basics like an NFV introduction. The organizer seeks active participation from attendees on these and other topics.
1) The document discusses network function virtualization (NFV) and how it relates to OpenStack. NFV aims to virtualize network functions through standard servers and storage to reduce costs and improve flexibility. (2) ETSI has defined NFV reference architectures, use cases, and an NFV management and orchestration framework. (3) The document outlines ongoing work by ETSI on NFV specifications and interoperability testing to advance the NFV ecosystem.
Network Function Virtualization (NFV) BoF, by Santanu Dasgupta.
A presentation given at the APNIC 40 APNIC Network Function Virtualization (NFV) BoF session on Tue, 8 Sep 2015.
NFV is an initiative to virtualize network functions that were previously carried out by dedicated hardware. Alten Calsoft is a pioneer in the NFV space since 2012 and is a member of ETSI NFV ISG. NFV works by decoupling network functions like routers, firewalls, and load balancers from dedicated hardware devices and running them as virtual machines on commercial off-the-shelf servers. A hypervisor manages the virtual machines and allows multiple operating systems to share a single hardware processor or host. Virtual machines can imitate multiple virtual hardware platforms in an isolated manner and enable operating systems like Linux or Windows server to run on the same physical host, saving costs by reducing physical hardware systems.
The Next Step ofOpenStack Evolution for NFV DeploymentsDirk Kutscher
NFV is now a well-known concept and in an early deployment stage, leveraging and adapting OpenStack and other Open Source Software systems. In the OPNFV project, a large group of industry peers is building a carrier-grade, integrated, open source reference platform for the NFV community. The telco industry has successfully adopted Open Source Software for carrier-grade deployments. It is now time for taking the next steps and to extend the colloaboration with upstream projects -- by opening up previously proprietary developments, by contributing code and other artifacts in order to create a ecosystem of NFV platforms, applications, and management/orchestration systems.
This talk shares some insights on how Red Hat and NEC are working together to foster collaboration in the NFV ecosystem by actively working with OpenStack and other upstream projects.
NEC has pioneered the adoption of Linux, KVM, Open vSwitch, and OpenStack for their mobile network core product line (virtualized EPC) and has gained significant experience through development work and deployments. NEC's extensions for high efficiency and high availability have led to contributions of new features to OpenStack, such as DPDK vSwitch control and CPU allocation features. For NEC, it is very important to have those features integrated into the mainstream code base for building reliable infrastructure systems.
Red Hat, one of main contributors to OpenStack, leads the development of those functions to meet NFV requirements in OpenStack, making critical and demanding applications run of top of open platforms. The presentation explains how NEC and Red Hat are integrating and optimizing Red Hat Enterprise Linux OpenStack Platform and NFV, along with contributions to open source communities, including OpenStack and Open Platform for NFV (OPNFV).
Summit 16: ETSI NFV Interface and Architecture OverviewOPNFV
The document discusses the work of the ETSI NFV Interfaces and Architecture Working Group (IFA WG). It provides an overview of the MANO architectural framework, including basic concepts, the architectural framework diagram, and information model. It also maps the MANO components to IFA work items, such as specifications for reference points and interfaces. Finally, it shows how the VIM northbound interfaces are mapped to relevant OPNFV projects.
This document discusses Network Function Virtualization (NFV) and its relationship to OpenStack. It provides an overview of NFV and the ETSI NFV specifications. It describes how ETSI NFV defines the virtualization of network functions and services. It also discusses how OpenStack addresses some of the infrastructure requirements for NFV such as multi-hypervisor support, different virtualization models, and exposing network and resource functions. The document presents examples of how NFV would virtualize a media resource function and related descriptors. It concludes by discussing the relationship between ETSI NFV and OpenStack/OPNFV and their collaborative efforts.
A Connectionist Approach to Dynamic Resource Management for Virtualised Netwo...Rashid Mijumbi
1. The document proposes a connectionist approach using graph neural networks for dynamic resource management in virtualized network functions to improve efficiency while ensuring reliability.
2. It aims to predict VNF resource requirements to avoid unnecessary resources being kept active/standby through topology-aware resource management using a GNN model.
3. The GNN model takes VNFC features and states as input and computes VNFC states over iterations before outputting resource forecasts to dynamically manage resources.
This document discusses network function virtualization (NFV), including its use cases, architecture, and virtualization requirements. It describes NFV's benefits in reducing costs and increasing flexibility compared to proprietary hardware appliances. The NFV architecture framework separates network functions into software-based virtual network functions (VNFs) that run on a shared virtualized infrastructure. It also covers NFV specifications, use cases like NFV infrastructure as a service, and virtualization requirements around performance, security, and resilience.
Summit 16: Keynote: HPE Presentation- Transforming Communication Service Prov...OPNFV
Open Transformation
Three sentences:
HPE's OpenNFV program aims to accelerate NFV transformations through an open partner ecosystem focused on bridging gaps between open source projects, ecosystems, and deployable solutions. The program provides a proven and innovative environment for NFV by integrating technology partners' components, validating application partners' VNFs, and leveraging services partners' industry strengths. HPE is also contributing learnings from its OpenNFV labs back to the OPNFV project to help bridge gaps between open source and ecosystems.
The document provides guidance for architecting a greenfield cloud solution to support Network Functions Virtualization (NFV) based on VMware best practices. It describes the core components of the VMware vCloud NFV platform and how they map to the ETSI NFV reference model. The platform is comprised of NFVI, VIM, and operations management components which abstract, manage, and monitor the underlying virtualized infrastructure to support the deployment and management of virtualized network functions.
OPNFV is an open source project that aims to develop an integrated and tested open source platform for network functions virtualization (NFV) to help operators meet increasing demands on networks. The project was launched in September 2014 and is supported by telecom operators and vendors. It will integrate existing open source NFV components and develop new code to provide a carrier-grade reference platform for NFV that supports performance, scale, and reliability requirements of networks.
Cisco SDN/NVF Innovations (SDN NVF Day ITB 2016)SDNRG ITB
The document discusses Cisco's innovations in software-defined networking (SDN) and network functions virtualization (NFV). It provides an overview of Cisco's strategy, which involves various models of programmability including classic SDN with OpenFlow, network virtualization with overlays, and hybrid approaches. The document also discusses Cisco's NFV reference architecture and innovations like the Virtualized Mobility Supervisor (vMS) and virtualized branch solutions.
NFV resiliency whitepaper - Ali Kafel, Stratus TechnologiesAli Kafel
This white paper makes the case for:
Why Resiliency Management Needs to be in the Software Infrastructure. It Covers:
- Fault Management and Resiliency Management
- Seamless Protection for Faster and Simpler Devl
- Multiple Levels of Availability
- Speed of Service Restoration & Redundancy Restoration
- State Management
- Higher Flexibility and Efficiency of Resiliency
- Demonstrating Carrier Grade Availability and Resiliency
The document discusses Network Functions Virtualization (NFV) and OpenStack. It provides an overview of NFV, describing what NFV is and its key benefits. It also summarizes the work completed in Phase 1 of the ETSI NFV Industry Specification Group, including published documents on NFV architecture, interfaces, and requirements. The document then presents examples of NFV proofs-of-concept involving virtualized network functions and orchestration using OpenStack. It concludes with a discussion of requirements for integrating NFV and OpenStack, such as support for multiple hypervisors, hardware acceleration, and security.
The document discusses SDN and NFV for carriers. It outlines challenges like network inflexibility and high costs, and opportunities like virtualization and software-defined networking. It provides an overview of NFV and SDN, including definitions and benefits. Use cases are presented that demonstrate how SDN and NFV can address challenges and enable new services. A phased approach is suggested for service providers to adopt NFV and SDN technologies.
KEYNOTE @ NFV World Congress 2017, San José
Francisco-Javier Ramón | Head of Network Virtualisation, GCTO | Telefónica
Chair | ETSI OSM
ABSTRACT:
- How Telefónica is architecting its new Core Network with NFV to enable the dynamic re-allocation of capacity wherever needed.
- Why orchestration is the latest technical challenge to realize this vision, and what Telefónica is doing in this space.
- How Open Source MANO (OSM) has become the reference platform for interoperability after the launch of its third release.
- How this fits into Telefónica plans for virtualization.
The document outlines topics to be discussed at an NFV BOF meeting at APRICOT 2015, including advanced NFV topics like data plane connectivity models for VNFs, overlay encapsulation for MPLS operators, NFV service assurance, service chaining, and the applicability of Linux containers. It also includes basics like an NFV introduction. The organizer seeks active participation from attendees on these and other topics.
1) The document discusses network function virtualization (NFV) and how it relates to OpenStack. NFV aims to virtualize network functions through standard servers and storage to reduce costs and improve flexibility. (2) ETSI has defined NFV reference architectures, use cases, and an NFV management and orchestration framework. (3) The document outlines ongoing work by ETSI on NFV specifications and interoperability testing to advance the NFV ecosystem.
Network Function Virtualization (NFV) BoF, by Santanu Dasgupta.
A presentation given at the APNIC 40 APNIC Network Function Virtualization (NFV) BoF session on Tue, 8 Sep 2015.
NFV is an initiative to virtualize network functions that were previously carried out by dedicated hardware. Alten Calsoft is a pioneer in the NFV space since 2012 and is a member of ETSI NFV ISG. NFV works by decoupling network functions like routers, firewalls, and load balancers from dedicated hardware devices and running them as virtual machines on commercial off-the-shelf servers. A hypervisor manages the virtual machines and allows multiple operating systems to share a single hardware processor or host. Virtual machines can imitate multiple virtual hardware platforms in an isolated manner and enable operating systems like Linux or Windows server to run on the same physical host, saving costs by reducing physical hardware systems.
The Next Step ofOpenStack Evolution for NFV DeploymentsDirk Kutscher
NFV is now a well-known concept and in an early deployment stage, leveraging and adapting OpenStack and other Open Source Software systems. In the OPNFV project, a large group of industry peers is building a carrier-grade, integrated, open source reference platform for the NFV community. The telco industry has successfully adopted Open Source Software for carrier-grade deployments. It is now time for taking the next steps and to extend the colloaboration with upstream projects -- by opening up previously proprietary developments, by contributing code and other artifacts in order to create a ecosystem of NFV platforms, applications, and management/orchestration systems.
This talk shares some insights on how Red Hat and NEC are working together to foster collaboration in the NFV ecosystem by actively working with OpenStack and other upstream projects.
NEC has pioneered the adoption of Linux, KVM, Open vSwitch, and OpenStack for their mobile network core product line (virtualized EPC) and has gained significant experience through development work and deployments. NEC's extensions for high efficiency and high availability have led to contributions of new features to OpenStack, such as DPDK vSwitch control and CPU allocation features. For NEC, it is very important to have those features integrated into the mainstream code base for building reliable infrastructure systems.
Red Hat, one of main contributors to OpenStack, leads the development of those functions to meet NFV requirements in OpenStack, making critical and demanding applications run of top of open platforms. The presentation explains how NEC and Red Hat are integrating and optimizing Red Hat Enterprise Linux OpenStack Platform and NFV, along with contributions to open source communities, including OpenStack and Open Platform for NFV (OPNFV).
Summit 16: ETSI NFV Interface and Architecture OverviewOPNFV
The document discusses the work of the ETSI NFV Interfaces and Architecture Working Group (IFA WG). It provides an overview of the MANO architectural framework, including basic concepts, the architectural framework diagram, and information model. It also maps the MANO components to IFA work items, such as specifications for reference points and interfaces. Finally, it shows how the VIM northbound interfaces are mapped to relevant OPNFV projects.
This document discusses Network Function Virtualization (NFV) and its relationship to OpenStack. It provides an overview of NFV and the ETSI NFV specifications. It describes how ETSI NFV defines the virtualization of network functions and services. It also discusses how OpenStack addresses some of the infrastructure requirements for NFV such as multi-hypervisor support, different virtualization models, and exposing network and resource functions. The document presents examples of how NFV would virtualize a media resource function and related descriptors. It concludes by discussing the relationship between ETSI NFV and OpenStack/OPNFV and their collaborative efforts.
A Connectionist Approach to Dynamic Resource Management for Virtualised Netwo...Rashid Mijumbi
1. The document proposes a connectionist approach using graph neural networks for dynamic resource management in virtualized network functions to improve efficiency while ensuring reliability.
2. It aims to predict VNF resource requirements to avoid unnecessary resources being kept active/standby through topology-aware resource management using a GNN model.
3. The GNN model takes VNFC features and states as input and computes VNFC states over iterations before outputting resource forecasts to dynamically manage resources.
This document discusses network function virtualization (NFV), including its use cases, architecture, and virtualization requirements. It describes NFV's benefits in reducing costs and increasing flexibility compared to proprietary hardware appliances. The NFV architecture framework separates network functions into software-based virtual network functions (VNFs) that run on a shared virtualized infrastructure. It also covers NFV specifications, use cases like NFV infrastructure as a service, and virtualization requirements around performance, security, and resilience.
Summit 16: Keynote: HPE Presentation- Transforming Communication Service Prov...OPNFV
Open Transformation
Three sentences:
HPE's OpenNFV program aims to accelerate NFV transformations through an open partner ecosystem focused on bridging gaps between open source projects, ecosystems, and deployable solutions. The program provides a proven and innovative environment for NFV by integrating technology partners' components, validating application partners' VNFs, and leveraging services partners' industry strengths. HPE is also contributing learnings from its OpenNFV labs back to the OPNFV project to help bridge gaps between open source and ecosystems.
The document provides guidance for architecting a greenfield cloud solution to support Network Functions Virtualization (NFV) based on VMware best practices. It describes the core components of the VMware vCloud NFV platform and how they map to the ETSI NFV reference model. The platform is comprised of NFVI, VIM, and operations management components which abstract, manage, and monitor the underlying virtualized infrastructure to support the deployment and management of virtualized network functions.
OPNFV is an open source project that aims to develop an integrated and tested open source platform for network functions virtualization (NFV) to help operators meet increasing demands on networks. The project was launched in September 2014 and is supported by telecom operators and vendors. It will integrate existing open source NFV components and develop new code to provide a carrier-grade reference platform for NFV that supports performance, scale, and reliability requirements of networks.
Cisco SDN/NVF Innovations (SDN NVF Day ITB 2016)SDNRG ITB
The document discusses Cisco's innovations in software-defined networking (SDN) and network functions virtualization (NFV). It provides an overview of Cisco's strategy, which involves various models of programmability including classic SDN with OpenFlow, network virtualization with overlays, and hybrid approaches. The document also discusses Cisco's NFV reference architecture and innovations like the Virtualized Mobility Supervisor (vMS) and virtualized branch solutions.
NFV resiliency whitepaper - Ali Kafel, Stratus TechnologiesAli Kafel
This white paper makes the case for:
Why Resiliency Management Needs to be in the Software Infrastructure. It Covers:
- Fault Management and Resiliency Management
- Seamless Protection for Faster and Simpler Devl
- Multiple Levels of Availability
- Speed of Service Restoration & Redundancy Restoration
- State Management
- Higher Flexibility and Efficiency of Resiliency
- Demonstrating Carrier Grade Availability and Resiliency
NFV : Virtual Network Function Architecturesidneel
This document discusses network function virtualization (NFV) and virtual network functions (VNFs). It covers the overview of VNF architecture in the NFV framework, including VNF design patterns, properties, lifecycle, and fault management. VNFs are software implementations of network functions that run over NFV infrastructure and are orchestrated by NFV orchestrators and VNF managers. A VNF consists of one or more VNF components that have well-defined interfaces and can be deployed, managed, and upgraded independently. The document describes the various states, interfaces, and descriptors involved in the lifecycle of VNF instantiation, scaling, updating and upgrading.
An introductory slides for explaining the SDN and NFV technologies. what's the difference between them and when each one is used. Also it talk about some of Cisco products in each area either SDN or NFV or the Automation with some of real use cases deployed in today's service provider network.
Hope you like it
The document discusses use case diagrams and use case descriptions for modeling system requirements. It covers drawing use case diagrams to show functional requirements and actors, common mistakes, and writing use case descriptions including basic, alternate, and exception flows of events. The document provides examples and exercises to help understand use cases for requirements modeling.
This document provides an introduction to OpenFlow, SDN, and NFV. It describes the need for new networking paradigms and outlines some of the key problems with traditional networking approaches. OpenFlow is presented as providing open interfaces and programmability to network nodes. SDN is defined as separating the control logic from the forwarding plane and enabling programmable automation through open APIs. NFV aims to virtualize network functions to improve flexibility, reduce costs, and accelerate service deployment using standard IT virtualization technologies.
OPNFV is an open source project that aims to accelerate the introduction of new NFV products and services. It provides a carrier-grade, integrated platform built from upstream open source NFV components like OpenStack, OpenDaylight, OVS, and Ceph. OPNFV's first release, Arno, provides an initial build of the NFV Infrastructure and Virtual Infrastructure Manager components. The project works with upstream communities to integrate new requirements and features on a continuous basis through collaboration, deployment and testing efforts.
Ichiro Fukuda, Chief Architect, Infrastructure at NTT i3, delivered this Carrier-Class NFV Use-Case at OpenStack Summit (May, 2015) together with Pratik Roychowdhury, Director of Product Management at Juniper.
The presentation discusses challenges of enterprise infrastructure expansion to new branches and how ESI (Elastic Service Infrastructure) enables agile deployment of IT systems into new office/service locations.
ETSI has defined several documents related to NFV testing including performance characteristics and metrics, quality metrics, and testing methodologies. OPNFV has also built a continuous integration platform called Octopus with several open source test projects like FuncTest, Yardstick, and Qtip that leverage ETSI specifications and test the functionality, infrastructure, and performance of the OPNFV platform.
Automatic Integration, Testing and Certification of NFV in China MobileOPNFV
Qiao Fu, China Mobile, Liang Gao, Huawei
As Operators expand their deployment of NFV, automatic integration, testing and compliance certification become more and more important. In this speech, we would like to share our experience and progress in the China Mobile OPNFV Testlab on an automatic system of integration, testing and certification. This system takes fully use of OPNFV opensource tools, including installers such as Compass, testing such as Functest and Yardstick, compliance testing such as Dovetail. Such automatic system extremely decreases the human cost of Operators when deploying and testing the NFV cloud before large scale deployment.
Ildikó Váncsa, Chris Price, and Carsten Rossenhövel's presentation at the 2017 Open Networking Summit.
Communications service providers (CSPs) have a wide range of options when building virtualized services from the ground up including multiple choices for each functional block in the ETSI NFV reference architecture. CSPs prefer heterogeneous systems with building blocks from different vendors including open source software; for such deployments interoperability becomes a crucial requirement.
OpenStack, as the NFVI and VIM, serves as a widely used cloud platform for telecom and NFV use cases. As a common base, OpenStack offers the means for vendors and other open source projects to ease the interoperability challenge by providing a set of open API’s while focusing on upgradeability and backward compatibility.
However, when it comes to productization, interoperability testing often falls short and is sometimes left to the carrier as shown by the testing programs actively run by no fewer than 10 organizations today.
Join Carsten Rossenhövel from the European Advanced Networking Test Center (EANTC) and the rapporteur (editor) of ETSI’s NFV interoperability standards, Ildikó Váncsa from the OpenStack Foundation, and Chris Price, Ericsson and OpenStack board director to learn more about
The ETSI NFV Release 2 interoperability testing activities - standardization and recently completed ETSI PlugTest. Over 40 commercial and open source implementations were tested for interoperability, including 20 virtual network functions, 10 management and orchestration solutions and 10 NFV platforms.
The New IP Agency (NIA) interoperability testing campaigns of commercial NFV implementations executed by EANTC, focusing on results, lessons learned and recommendations.
How vendors and open source projects are stepping up to the challenge, realizing they must work together.
How to stay up-to-date with OpenStack releases and the community.
How to get involved to ensure you are aware of the latest developments and contribute what you need to OpenStack.
What will I learn from attending this session?
CSPs, open source projects and vendors alike will learn more about the recent ETSI PlugTest and NIA-commissioned interoperability testing, their results and how to architect full NFV solutions that will work together. Interoperability API tests and associated marks from OpenStack will be covered, as well as features to help stay current on OpenStack releases. Attendees will also hear from Ericsson about a vendor’s point of view, and how other projects such a OPNFV are evolving and expanding in scope to address this challenge.
Open Platform for NFV (OPNFV) is a new open source project focused on accelerating the evolution of Network Functions Virtualization (NFV). OPNFV will establish a carrier-grade, integrated, open source reference platform that industry peers will build together to advance the evolution of NFV and to ensure consistency, performance and interoperability among multiple open source components. Because multiple open source NFV building blocks already exist, OPNFV will work with upstream projects to coordinate continuous integration and testing while filling development gaps.
Achievements and future works of ITU-T Study Group 11 on Signalling requirements, protocols and test specifications
Presented at WTSA-16 by Mr Kaoru Kenyoshi, Vice-Chairman, on behalf of Mr Wei Feng, Chairman of of ITU-T Study Group 11
The document summarizes a session on gearing up for transport SDN deployment. It discusses how recent proofs-of-concept have shown progress towards commercial SDN deployment in transport networks. It outlines that network providers and vendors are collaborating through standards bodies and laboratories to address technical and business challenges inhibiting adoption. The OIF panelists will review findings from a global transport SDN prototype demo and steps to clear roadblocks to wide-scale deployment. They will discuss transport SDN drivers, needs, challenges and review the demo. It aims to accelerate adoption through providing guidance on use cases, requirements, frameworks and demonstrations.
OIF experts presented project updates, discussed overcoming implementation challenges through interoperability and open optical networking and disaggregation at NGON & DCI World 2022 held in Barcelona, Spain June 21–23, 2022.
Speakers gave an overview of OIF’s 400ZR work, including results from a recent interoperability demonstration, co-packaging, Common Management Interface Specification (CMIS), common electrical interfaces (112G and 224G) and Transport Software Defined Networking (SDN) Application Program Interface (API).
Текущее состояние рынка SDN/NFV и Huawei на нём. Взгляд с трех основных напра...ARCCN
Эдуард Василенко — директор по развитию решений SDN/NFV компании Huawei с докладом «Текущее состояние рынка SDN/NFV и Huawei на нём. Взгляд с трех основных направлений: услуги, бизнес-процессы, технологии»
Mallik Tatipamula is the Vice President of Service Provider and Cloud Solutions at F5 Networks. He has over 23 years of experience in telecommunications and networking technologies. The presentation outlines F5's perspective on deploying Network Functions Virtualization (NFV) in phases, beginning with simplifying the SGi network and virtualizing value-added services platforms, then virtualizing control plane functions and finally access and core network elements. The goals are to make networks more programmable, simplify operations, and lower costs through a flexible, software-based architecture.
The document introduces OPNFV, an open source platform for accelerating NFV products and services. It discusses key industry trends driving NFV adoption like growth of network data and cloud computing. It also covers key industry needs addressed by NFV like service agility. OPNFV provides an integrated, carrier-grade platform and ecosystem for NFV collaboration and testing. It leverages various upstream open source projects and provides common mechanisms for NFV functions like VNF lifecycle management and dynamic scaling.
Considerations for Deploying Virtual Network Functions and ServicesOpen Networking Summit
The document discusses considerations for deploying virtual network functions and services using network function virtualization (NFV). It describes the key concepts of NFV including separating network functions from dedicated hardware, increasing network elasticity, and addressing heterogeneity. It outlines the main business drivers for NFV including reducing costs, simplifying network management, and shortening time to market for new services. Finally, it discusses carrier Ethernet use cases, virtual network function deployment models, and options for deploying functions at customer premises.
Open Source Software development models are changing the way the telco industry is creating products and systems. This presentation at ONS-2015 discusses how innovation, agile development and Open Source Software are linked together.It presents experience with transforming telco vendor development from closed to open source and provides an outlook of future activities in the NFV space.
Demystifying Network Function Virtualization (NFV) Service AssuranceZenoss
Presented by SOPRIS Technologies and Zenoss by SOPRIS' David Stevenson (CSO), and Zenoss' Kent Erickson (Senior Manager, Channel Marketing) and Laszlo Bojtos (Staff Sales Engineer).
Access the full presentation recordings for GalaxZ17 here: http://ow.ly/WyBu30cakk0
Telco networks are undergoing a transformation driven by factors like increased capacity demands, network and data center convergence, and the need for programmable networks. This is leading telcos to adopt network functions virtualization (NFV), which uses virtualization techniques to virtualize entire classes of network functions into software that can run on commercial off-the-shelf servers rather than proprietary hardware. NFV aims to provide benefits like elastic scaling, faster deployment cycles, network slicing, and lower total cost of ownership. The European Telecommunications Standards Institute established an industry specification group in 2012 with over 50 members to develop NFV standards. NFV allows operators to reduce costs, improve efficiency, and provide opportunities for energy savings, openness and innovation.
James Gibbons has over 15 years of experience in networking, security, and telecommunications. He has a Master's degree in telecommunications and holds CCNP and CCNA certifications. Currently he works as a network engineer providing project management, engineering, and deployment support for the Defense Information Systems Agency. Previously he has held various network engineering roles testing and deploying routing, switching, security, and telecommunications technologies.
Integrated SDN/NFV Framework for Transitioning to Application Delivery ModelF5 Networks
While service providers continue to validate various use cases associated with NFV, new advanced devices, increasing usage of high bandwidth applications,
and the Internet of Things (IoT) are all pushing them to commercialize these NFV initiatives to enable them to profitably scale their networks and deploy new revenue generating business models. We will explore:
• Why hybrid architectures are key to scale and evolve NFV environments
• The importance of the evolution of standards and ecosystems
• Key technologies that are crucial to realize the benefits of NFV
Presentation titled "NFV - moving from vision to reality" by Mallik Tatipamula, VP Service Provider Solutions, F5 Networks, at NFV World Congress in May 2015.
"Future Impact of IoT and the Implications of Security" Keynote by Brian Scri...CableLabs
The coevolution of humanity with the technology we create to accompany us continues. As this takes place there will be painful hurdles and beneficial leaps forward; how we approach each of these will dictate the success of this relationship. Join us as the future is laid out ahead for this coevolution.
Brian Scriber
Security WG Chair, OCF, & Principal Architect Security, CableLabs
https://www.cablelabs.com/informed/
Technology & Policy Interaction Panel at Inform[ED] IoT SecurityCableLabs
As IoT insecurity creates vulnerabilities, policymakers become concerned about the health of the Internet. How can public policy address these concerns in a smart way, targeting their efforts to improve IoT security without imposing unnecessary costs across the Internet ecosystem or creating unintended effects? What is the role of government versus industry?
Rob Alderfer, Moderator
Vice President Technology Policy, CableLabs
Gerald Faulhaber
Professor Emeritus, Business Economics & Public Policy, Wharton School
Chaz Lever
Lead Reseacher, Georgia Tech
Jason Livingood
Vice President, Technology Policy & Standards, Comcast
Protecting ISP Networks and the Internet at Inform[ED] IoT SecurityCableLabs
Insecure IoT devices have enabled the largest DDoS service attacks on the internet to date and are threatening the basic functionality of the Internet. A panel of experts will discuss how ISPs are working to mitigate these attacks and protect their networks and the Internet from the growing number of insecure devices.
Rich Compton
Principal Engineer, Charter Communications
Michael Glenn
Vice President Security Services, CableLabs
Brian Rexroad
VP, Security Platforms, AT&T
Clarke Stevens, Moderator
Principal Architect, Shaw Communications
André van der Walt
Interim VP & CISO, Liberty Global
https://www.cablelabs.com/informed/
"The State of IoT Security" Keynote by Shawn Henry at Inform[ED] IoT SecurityCableLabs
Join Shawn Henry as he discusses his vision of IoT Security. What will be the impact of insecured IoT devices for consumers in the home, smart cities and other industrial and critical infrastructures? Looking forward five years, what is the landscape to consider?
Shawn Henry
President, CrowdStrike Services & CSO
https://www.cablelabs.com/informed/
Internet of Things (IoT) Security and Privacy Recommendations by Jason Living...CableLabs
As IoT insecurity creates vulnerabilities, policymakers become concerned about the health of the Internet. How can public policy address these concerns in a smart way, targeting their efforts to improve IoT security without imposing unnecessary costs across the Internet ecosystem or creating unintended effects? What is the role of government versus industry?
Jason Livingood
Vice President, Technology Policy & Standards, Comcast
https://www.cablelabs.com/informed/
IoT and Cybersecurity: What can be done? by Gerald Faulhaber at Inform[ED] Io...CableLabs
As IoT insecurity creates vulnerabilities, policymakers become concerned about the health of the Internet. How can public policy address these concerns in a smart way, targeting their efforts to improve IoT security without imposing unnecessary costs across the Internet ecosystem or creating unintended effects? What is the role of government versus industry?
Gerald Faulhaber
Professor Emeritus, Business Economics & Public Policy, Wharton School
https://www.cablelabs.com/informed/
Innovation in Connected Healthcare by Summer Knight MD at Inform[ED] Connecte...CableLabs
What market opportunities exist with connected healthcare? How will remote care management and device monitoring impact hospitals, healthcare delivery organizations, network operators, and patients?
Summer Knight, M.D.
Managing Partner / "The Innovation Doctor", MBA, Firecracker International
https://www.cablelabs.com/informed/
Keynote by Simon Kos at Inform[ED] Connected HealthcareCableLabs
Technology is fundamentally changing society as it becomes more accessible, affordable and capable. Health is no exception, and the potential for meaningful impact is huge. This presentation will describe how digital transformation can deliver on the promise of a more affordable, accessible, and agile health system. Starting from the Quadruple Aim framework, we will use real-world examples to examine technology innovation along the dimensions of engaging patients, empowering care teams, optimizing clinical and operational effectiveness, and transforming the care continuum.
Simon Kos, M.D.
Chief Medical Officer of Worldwide Health, Microsoft
https://www.cablelabs.com/informed/
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Architectural Framework Revision 2 Summary of Changes:
EMS replaced by EM (Element Management)
Clarifying that VNF Forwarding Graph sequence can be defined at design time or at run time.
Diagram modified: service, VNF, Infrastructure descriptor put inside the MANO block (Se-Ma reference point deleted), “EMS” labels replaced by “EM”
EVE001: Requirements on the hypervisor to enable use of a stand-alone (*) vswitch - Support of VNF(C) live migration. 2) Restructure/rewrite the existing text to clearly distinguish between normative requirements to be fulfilled by the hypervisor domain and other informative material (e.g. best practices) 3) Update the state-of-the-art (e.g. options for vswitch implementations) and identification of challenges, based on industry progress and lessons learnt from the PoCs. 4) Update the document to align with the “vSwitch Benchmarking and Acceleration” deliverable (*) In the above context, “stand-alone” refers to a vswitch whose lifecycle events (restart, upgrade…) do not directly impact virtual machines and that can be provided by software vendor independent from the hypervisor provider The deliverable will contain normative provisions.
EVE002: Describe the application of MEF Carrier Ethernet services use cases in an NFV environement and develop new use cases as needed. The deliverable for this work item will be informative. The MEF’s “Third Network” combines the on-demand agility and ubiquity of the Internet with the performance and security assurances of Carrier Ethernet 2.0 (CE 2.0). The Third Network will also enable services between not only physical service endpoints used today, such as Ethernet ports (UNIs), but also virtual service endpoints running on a blade server in the cloud to connect to Virtual Machines (VMs) or Virtual Network Functions (VNFs).
EVE003: Develop a report to study the internal architectural structure/physical components of an NFVI Node and provide a set of guidelines to support an NFV environment. The goai is to facilitate the availability of these components in a multi-vendor environment. The scope is limited to the “Hardware Resources” portion of Figure 2 of the Infrastructure Overview GS INF001 V1.1.1. These Resources include the Compute, Storage, and Network hardware. Accordingly, this document will study: - Applicable Architectural Principles (e.g., Open Compute Project) - Physical Hardware Components - Node Construction (e.g., COTS Products, Rack Designs, Processors, Heating/Cooling Issues) - Interconnection Methods - “Building” NFVI Node Configurations with generic set of components (e.g., Transport, Access, Customer Premises, Provider Edge, etc.) - Support Various Use Cases specified in GS INF001 (e.g., Cloud Computing Services, Cloud Deployment Models, etc.) - Scaling Issues (Minimum configuration to support specified function, Stacking components to meet various node “size” requirements) The proposed GS intends to cover these topics at an acceptable level of detail. It is expected that this study may highlight the need for additional requirements for individual components such as processors. Such requirements can then be pursued either in the ISG or in other SDO’s as applicable.
EVE004: The hypervisor approach has some cost in terms of efficiency and the scalability may not be sufficient for cases where a huge number of virtualisation containers need to be deployed and managed. The scope of this work item is twofold: Identify the impact of using alternative virtualisation technologies on the NFV framework and specifications, and propose appropriate changes. - Provide an analysis of the pros and cons of these alternative technologies Alternative virtualisation technologies to be considered include – but are not limited to – the following ones: - Container-based operating system virtualization such as LXC - Higher layer container technology such as Java virtual machines The deliverable will contain informative material only, including recommendations on how to modify other ETSI NFV specifications to cover Non-hypervisor-based virtualisation. These modifications are expected to be performed under separate work items.
EVE005: Identify use cases, clarify the different usages of SDN within the context of the NFV architecture framework, including SDN Controller as a VNF, SDN Controller as a realization of the Infrastructure network controller, etc. , and proposes requirements to be fulfilled, e.g. by an SDN controller playing the role of network controller in the NFV architecture (cf. MAN001 clause 5.6). Network domains to be covered include datacenter SDN, datacenter-WAN interworking, access network and WAN. The WI will also provide a comparison with other forms of network controllers. The work item will leverage existing work from ETSI ISG NFV. It will support discussions with other SDO and Open Source projects such as IETF, OPNFV, ONF, OpenStack, OpenDaylight and others as appropriate. The deliverable will contain informative material only but will also make recommendations as to whether normative work should be initiated as a follow-up activity.
IFA001: Suggests a common architecture and abstraction layer for the NFV acceleration (hardware & software), which allows deployment of various accelerators within NFVI and facilitates interoperability between various VNFs and accelerators. As well as presenting the general overview of the NFV acceleration, this WI also describes a set of use cases illustrating the usage of NFV acceleration in NFV environment. The deliverable will contain informative material only. This Work Item is the 1st of a series of Work Items on NFV Acceleration. Its deliverable will be the 1st part of a multi-part Group Specification.
IFA002: Addresses: 1) Requirements for a set of abstract interfaces, enabling a VNF to leverage acceleration services from the infrastructure, regardless of their implementation. 2) A description (such as UML) for each of the above NFVI execution interfaces. 3) An deployment model of the above interfaces. The list of abstract interfaces to be specified will be derived from the use cases described in Part 1 (Overview and Use Cases) of the multi-part GS on NFV Acceleration. Results will be a normative specification . This Work Item is the 2nd of a series of Work Items on NFV Acceleration. Its deliverable will be the 2nd part of a multi-part Group Specification.
IFA003: Define performance benchmarking parameters for virtual switching in the usage models provided in the companion work item “Overview & Use Cases”. - Define requirements for virtual switch acceleration, and quantify possible gains in performance, latency & SLA metrics. - Define deployment scenarios for compute node based virtual switching that is supportable in any virtual switch data path or in any intelligent NIC, in a consistent manner across multiple vendor implementations. - Define requirements for common virtual switching functions across usage models such as packet delivery into VNFs, network overlay and tunnel termination, stateful NAT, service chaining, load balancing and, in general, match-action based policies applied to network functions running in VMs. - Recommendations for potential follow-on PoCs to demonstrate feasibility. The deliverable's will contain both normative provisions and informative material.
IFA004: Provides requirements, architecture and the description of the interface exposed by the NFVI for NFV acceleration from infrastructure management perspective. This includes the controlling and management of acceleration resources, e.g. dynamic allocation, modification, release, reclamation of acceleration resources. The NFV Acceleration will be addressed by a multi-part Group Specification, addressing the Overview & Use Cases, VNF Interface, vSwitch Acceleration, and the Management Aspects. The deliverable of this WID include: - Normative GS – Part 4 Document that provides the management requirements, architecture and interfaces of NFV acceleration.
IFA005: Complete functional requirements for interfaces on the Or-Vi reference point in between the NFVO and the VIM(s), to address the functions specified in GS NFV MAN 001. The results of the work item will include: 1) Detailed description of interfaces and its operations functionality. 2) Information flows and information elements of: a) Virtualized resource management interfaces, for: i) Lifecycle management of virtualized resources, including instantiation, modification, configuration and termination of such virtualized resources. ii) Fault management of virtualized resources. iii) Performance management of virtualized resources. iv) Accounting management of virtualized resources. v) Security management of virtualized resources. b) Resource orchestration interfaces, for: i) Virtualized resources/NFVI capacity management. ii) Resources reservation management. iii) Virtualized resources catalogue management. The resulting deliverable will contain normative provisions.
IFA006: Complete functional requirements for interfaces on the Vi-Vnfm reference point in between the VNFM and the VIM(s), to address the functions specified in GS NFV MAN 001. The results of the work item will include: 1) Detailed description of interfaces and its operations functionality. 2) Information flows and information elements of: a) Virtualized resource management interfaces, for: i) Lifecycle management of virtualized resources, including instantiation, modification, configuration and termination of such virtualized resources. ii) Fault management of virtualized resources. iii) Performance management of virtualized resources. b) Resource management interfaces, for: i) Resources reservation information retrieval. ii) Virtualized resources catalogue information retrieval. iii) VNF image management.
IFA007: Complete functional requirements for interfaces on the Or-Vnfm reference point between the VNFM and the NFVO, to address the functions specified in GS NFV MAN 001. The results of the work item will include: 1) Detailed description of interfaces and its operations functionality. 2) Information flows and information elements of: a) VNF lifecycle management interfaces, for: i) Lifecycle management of VNFs, including the instantiation, modification, update, scaling and termination of VNFs. ii) Lifecycle change notifications of VNFs. b) VNF orchestration interfaces, for: i) Lifecycle operation and resource granting. c) Other related VNF management interfaces, for: i) VNF fault information retrieval and management. ii) VNF performance information retrieval and management. iii) VNF package management. iv) Policy management.
IFA008: The reference point Ve-Vnfm described as part of the NFV architecture framework in GS NFV002 is actually further split in the informative GS NFV MAN001 in two reference points – one between the VNF Manager and a VNF (Ve-Vnfm-vnf) and one between the VNF Manager and an EM associated with that VNF (Ve-Vnfm-em); these reference points are mainly used for the lifecycle management of that VNF. The scope of the Work Item will include the functional and information requirements of all VNF management interfaces over the reference points between the VNFM and theVNF/EM, based on which complete interfaces technical specifications can subsequently be defined, for interoperability purposes.. The results of the work item will include: • Detailed description of interfaces and its operations functionality. • Detailed information model requirements of related VNF lifecycle management interfaces, for: – Lifecycle management of VNFs, including the instantiation, modification, update, scaling, healing and termination of VNFs. – Lifecycle change notifications of VNFs. • Detailed information model requirements of other related generic VNF management interfaces, for: – VNF fault management. – VNF performance management. – VNF configuration • Detailed information model requirements of any other generic VNF management interfaces (new and/or previously described in GS NFV MAN 001) needed to be exposed between in support of VNF/EM and VNFM, in support of necessary VNF-related management operations. • Validation of interface operations and information model requirements against end-to-end flows. Data models/schemas and protocols needed to implement the detailed functional requirements are not covered in this deliverable. The WI will leverage GS NFV MAN001 and will consider any applicable other guidelines, studies and requirements as appropriate, in close collaboration with the other organizations working on these aspects, such as 3GPP SA5 and TMF.
IFA009: An architecture study that shall: • outline clearly a set of possible functional/architectural options • analyse the impact of different interactions between some functional blocks in the NFV architectural framework (EM, VNF, OSS) and NFV-MANO functional blocks (NFVO, VNFM, VIM) on the functional partitioning/distribution/consolidation of functionality amongst NFV-MANO functional blocks • analyse the scope of the VNFM and NFVO and clarify the difference and impact, if any, of separating VNFM from the NFVO versus having those functionalities combined • analyse the impact of centralized versus distributed VNFM functionality • analyze and outline functional/architectural impact of separating versus combining the two broad functions of the NFVO (Network Service Orchestration and Resource Orchestration); • analyze and outline functional/architectural options of VNFM, NFVO, VIM to support operations across administrative domains boundaries and identify the necessary interfaces. • identify for each architectural option views of usage of the interfaces and functional blocks, and which management interfaces are significant • provide valuable insights for consideration by other normative work on NFV architecture and interfaces.
IFA010: Contains all the normative functional requirements for NFV management and orchestration e.g. to support VNF migration, VNF Healing, Health-check. The following aspects need to be considered (in-scope) while developing such a deliverable • Consolidating all the functional requirements scattered in various phase 1 GSs (SWA GS, REL GS, INF GSs, MAN GS, NFV004) for management and orchestration. ISG level requirements from NFV004 should be considered as default requirement for phase 2 unless specific corrections to certain requirements are agreed in ISG level. • Refining functional requirements for concepts defined in Phase 1 Defining selection criteria for data models. The functional requirements on interfaces and data models related to interfaces are not in scope of this WI.
IFA011: Develop a specification for packaging VNFs to be delivered to service providers. An informative GS document addressing: - Requirements for the structure and format of the VNF archive, list of mandatory and optional files and authorized formats -Extensible language independent meta-model for describing the VNF properties and resource requirements building on existing work on VNFD. This will require using consistent terminology and refinement of the existing VNF model -Recommendation for Implementation ready packaging structure by selecting and reusing (e.g., profiling or identifying requirements for extension of) existing cloud services (e.g. TOSCA) and network configuration specifications (e.g. DMTF, MEF). This work item will benefit from the SDO gap analysis and it will be used as input to open source activities related to packaging tools, runtime package interpreters and execution environments. The output of this work should be used as formal requirements for extensions into normative specifications developed by other SDOs identified in the analysis.
IFA012: Specify the interface(s) and the corresponding requirements that comprise the Os-Ma-nfvo reference point as currently defined in the GS NFV-MAN 001 regarding applications/services on top of Network Services (NS). The reference point is used for management interactions between OSS and the NFV framework. The work item will leverage GS NFV-MAN 001 and will consider any applicable other guidelines, studies and requirements as appropriate. Additionally it will have close connections with the Work Items DGS/NFV-IFA010 for data modeling requirements and DGS/NFV-IFA013 regarding the OSS-Orchestrator interface handling of the NS. The impact on the NS shall be explored. Therefore the DGS/NFV-IFA013 is dependent upon the output of this WI and shall be started immediately after the corresponding output is available. This ensures the alignment and the usage of same methods, mechanism etc. to the greatest possible extent between work items regarding the several types of applications/services. Specifically, the following items will be addressed: •This reference point shall be realized by open, standardized interface(s), i.e. non-proprietary •A minimal set of operations will be defined and detailed §operations originating from the NFVO as well as the OSS will be included with all associated information elements and descriptors respectively as well as information models considered §based on the identified functionality which shall be realized •Unambiguous information model requirements shall be described •A set of message flows for all identified operations will be specified •Dependencies of other interfaces and functional blocks including their functionalities and information models shall be considered •The reference point/interface(s) shall support aspects from the following topics §E2E view (e. g. concerning applications/services, ...) §Assurance (e. g. Configuration, Performance and Fault management) §Order management and Fulfillment §Inventory management §Policy management §Life cycle management of Services (applications/services on top of NS) §Flexible/dynamic service orchestration including creation and modification (e. g. orchestration, launching of a service and adaptation of running services) §Real-time capabilities (e. g. concerning real-time services) §Automation (recovery, healing, etc.) §Monitoring/Tracing (e. g. concerning services) §Testing §Advanced data analytics/Big data including usage of several data sources §Interoperability e.g. §Handling of virtualized and non-virtualized environments in parallel §Between NFVO (Orchestrator(s)) from different vendors and OSS providers (i.e. platform interoperability)
IFA013: Os-Ma-nfvo is a reference point between the OSS and the NFV Orchestrator. This reference point is used for all management interactions between OSS and the NFV-specific management framework, and mainly used for the lifecycle management Network Services (a group of VNFs with defined relationship between them).The scope of the Work Item will include the detailed functional and information requirements of all NFV management interfaces over the reference point Os-Ma-nfvo, based on which complete interfaces technical specifications can subsequently be defined, for interoperability purposes. The results of the work item will include: • Detailed description of interfaces and its operations functionality. • Detailed information model requirements of related NS lifecycle management interfaces, for: - Management of NS Descriptor and VNF Packages; - Lifecycle management of Network Services, including the instantiation, modification, update, scaling, and termination, testing of NSs. - Lifecycle change notifications of NSs. • Complete and detailed information model requirements of other related NFV management interfaces, for: - NS monitoring (e.g. NS fault information retrieval and management, NS performance information retrieval and management). - Policy Management • Detailed information model requirements of any other NFV management interfaces (new and/or previously described in GS NFV MAN 001) needed to be exposed between OSS and NFVO in support of necessary OSS-driven E2E operations. • Validation of interface operations and information model requirements against end-to-end flows. Data models/schemas and protocols needed to implement the detailed functional requirements are not covered in this deliverable. The WI will leverage GS NFV MAN001, and will consider any applicable other guidelines, studies and requirements as appropriate.
TST001: Develop recommendations for pre-deployment validation of NFV functional blocks in a lab environment. The following aspects of lab testing will be addressed: 1) Functional validation of VNFs interaction with NFV functional blocks. 2) User and control plane performance validation. Including the assessment of capacity management e.g. during VNF scale-out to ensure that performance levels adhere to SLAs. 3) Validation of reliability and availability of VNFs, NFVI and services during workload migrations. The deliverable may propose potential enhancements to the ETSI NFV architecture to better support testing.
TST002: Analysis of the NFV interoperability methodology landscape and suggests a framework to be addressed. Analyze pre-existent work on NFV interoperability testing methodology from NFV ISG work, PoCs, other SDOs, open source projects, general ETSI experience in this area, etc. - Review current NFV ISG work for testable interoperability requirements - Evaluate the requirements for NFV use case-agnostic interoperability and application-level interoperability for NFV-related use cases This work item will not deal with performance metrics.
REL002: Study of how to design processing components to achieve scalability, efficiency, and reliability in NFV environments. To meet the low-latency and high-availability requirements, this will require new techniques and abstractions for managing shared processing state. The hope is to identify application-independent techniques that can be applied generally, rather than have each VNF use its own idiosyncratic method for meeting these goals. Although an individual VNF could manage its own scale and replication, it is envisioned that an end-to-end service composed of many disparate VNFs would require a single coherent manager, such as an orchestrator that would manage the scale and capacity of the VNFs.
REL003: Study software reliability estimation models, reliability/availability methods and software upgrade mechanisms for E2E resiliency. Propose guidelines and procedures that describe how to realize services with different resiliency levels.
REL004: Describe methods for active monitoring and failure detection. It will address the following aspects: 1) Periodic testing of VNFs and service chains to ensure adherence to SLAs. 2) Proactive failure detection and recovery. The deliverable will propose potential enhancements to the ETSI NFV architecture to better support active monitoring.
SEC004: Expand the problem statement for application of Lawful Interception (LI) in NFV. The report shall identify the security and architecture pre-conditions for the provision of LI in an NVF based network. The report shall identify the requirements for provision of the points of interception for each of Intercept Related Information (IRI) and Content of Communication (CC) with respect to the handover requirements defined by ETSI TC LI.
SEC005: Provide guidance on the use of certificates and Certificate Authorities. It will look at various certificate deployment scenarios and describe certificate specific use cases, threats to the certificate management structure, and resulting requirements for NFV. In addition, this work will provide an overall certificate management guidance and trust validation applied for VM (Virtual Machine) and Virtualized Network Function (VNF).
SEC006: Develop a guide to assist with addressing the security aspects and regulatory concerns of NFV related documents and applications. This will include a template to assist the development of ETSI NFV deliverables and broader guidance for developers, architects and designers of hardware and software.
SEC007: Identify gaps in existing attestation technologies and practices, as applicable to NFV systems. These will include, but not limited to: • Levels of assurance • Assumed capabilities from the NFVI • Operational procedures • Requirements for interoperability • A gap analysis of current (established or newly proposed) attestation technology • Recommendations for follow-on PoCs to demonstrate feasibility of such attestation procedures.
SEC008: Investigate the security monitoring requirements in an NFV environment in order to provide security analytics, for detecting threats and mitigating attacks. This WI will investigate the underlying problem of both passive and active monitoring of subscriber and management information flows, where subscriber information includes signaling and content. This WI will recommend potential methodologies and placement of security visibility and control elements for fulfilling the requirements identified in this study. This is an informative study that will be useful to VNF and NFVI providers, network operators and research community. As part of this informative study, the GS will include the following activities: 1) Study existing security monitoring use cases and technologies for various types of networks (e.g., mobility networks, CDN and Enterprise) 2) Investigate issues (incl. data access) and security monitoring requirements for various NFV deployment scenarios 3) Explore security monitoring architecture for NFV deployment scenarios, including for security analytics. There are no associated dependencies with other work items.The scope of this WI is limited to monitoring traffic for security.