ASawwaf
commented
4 years ago Late 2012 European Telecommunication Standards Institute ( ETSI ) Industry Specification Group ( ISG ) for Network Functions Virtualization NFV is founded by world's leading telecoms network operators CSPâsâ networks are populated with a large and increasing variety of proprietary hardware appliances. To launch a new network service its required more variety of hardware appliances , which requires more space and power to accommodate these boxes and its increase by introducing multivendor and more Services ; compounded by the increasing costs of energy, capital investment challenges and the rarity of skills necessary to design, integrate and operate increasingly complex hardware-based appliances. Moreover, hardware based appliances now have shorter life cycle to accommodate move innovated services making the return of investment lower and lower when deploying new services, and slower time to market to introduce a new services with high OPEX and CAPEX investment The Target of ETSI ISG NFV to address these problems by leveraging standard IT virtualization technology by decoupling between software ( Network Function ) and hardware , so this software can run on a range of industry standard hardware âCommodity on the Self - server , switches and Storage In this case the CSPâs can convert many Network function as Mobile and Fixed network ( EPC , IMS , BNG ,..) form PNF to VNF which able to carry Data and control plan To complement and automation the deployment of NFV , Software Defined Networking (SDN ) come into the picture to be a key enabler technology for NFV to provides the means of dynamically control the network and the provisioning of networks as a service ETSI NFV is not only piece of software and hardware , it is complete reference architecture with reference interfaces , information modeling and Solution / detailed specification that support the complete life cycle management of VNFâs Resources requirements form compute , Storage and Networking ( NFVI) by VIM , and automated and orchestrated way of VNFâs onboarding based on standard VNF packages and descriptors ( NFVO) , finally manage VNFâs life cycle management ( VNFM)
https://www.etsi.org/technologies/689-network-functions-virtualisation
ETSI NFV publish 3 Release till the date , By time of this white paper , ETSI started working on NFV Release 4 specification focus on but limited to :
- NFVI evolution, focusing on enhancements to support lightweight virtualization technologies, optimizing NFV Infrastructure (NFVI) abstraction for reducing the coupling of VNFs to infrastructure, and optimizing networking integration into the infrastructure fabric to ease the connectivity for Virtualized Network Functions (VNFs) and Network Services (NSes)
- Enhancing NFV automation and capabilities, covering aspects such as: improving life-cycle management and orchestration, the simplification of VNF and NS management aspects leveraging virtualization, and handling advances in autonomous networking
- Evolving the NFV-MANO (Management and Orchestration) framework, focusing primarily on optimizing internal NFV-MANO capability exposure and usage
- Accompanying operationalization aspects which include: the simplification of NFV to ease development and deployment of sustainable NFV based solutions, verification (and certification) procedures and mechanisms, and operationalization, integration and use of NFV with other management and network frameworks Which it is related to CNCF TUG white paper : ⢠As example For 1st point , focus on âfocusing on enhancements to support lightweight virtualization technologies, optimizing NFV Infrastructure (NFVI) abstraction for reducing the coupling of VNFs to infrastructure, and optimizing networking integration into the infrastructure fabric to ease the connectivity for Virtualized Network Functions (VNFs) and Network Services (NSes)â by other word it focuses on container infrastructure
During last period starting from NFV , there is a lot of challenges that CSP suffer which lead the slowly NFV adoption as but not limited to :
- First and most important factors is the VNF architecture itself in terms of : o Monolithic Architecture ( Elephant architecture ) o Stat-full VNF , which all VNF state reside in VNF itself o Scalability & elasticity problems in terms of scaling up/down and in/out
- Telco-grade KPIs ( five 9sâ) and resiliency
- High throughput and performance required of some VNF which required some special acceleration technologies which against of Cloud concept
- Long cycle for VNF to certified/onboarded on the targeted NFVi
This was the same pattern followed during server virtualisation, when initial efforts focused on replicating physical servers as virtual entities. Cloud native however, requires a more fundamental redesign and rethink of how telco and backbone/core network systems function. In that sense, as well, cloud native for telco is actually not dissimilar from forklifting over monolithic legacy applications into virtual environments and then decoupling the tightly bundled functions and processes to create a more resilient, manageable, and performant infrastructure that derives immutability precisely from its ephemerality. In reality, CNFs will be introduced alongside VNFs and PNFs (physical network functions) and will need to fit into operational models that govern those earlier types of network functions. Additionally, CNFs will require the capability to be orchestrated by management systems already present in the service providers' networks.
ASalkever
Add some content in "1.5 Cloud Native for Telcos " and move " 1.4 Cloud Native Network Functions" To be under "1.5 Cloud Native for Telcos " as 1.5.x