NFV network function virtualization is an ongoing network revolution. This change will rely on IT advanced technology to have a lasting and profound impact on the operator's operations. Currently, there is much discussion about how virtualization and cloud are used in the telecommunications industry to improve architecture and operation and maintenance TCO. From the application of NFV, the early work focused on optimizing hardware using virtualization capabilities, and now it is gradually turning to operation and maintenance.
NFV redefines operation and maintenance
Although virtualizing certain network functions does bring CAPEX savings, NFV's biggest contribution is not here, but it provides a new way to achieve telecommunications capabilities, far more than just optimizing the efficiency of current processes. simple.
According to the NFV standard architecture, in order to facilitate the dynamic management of virtual resources, the NFV network management support domain is defined to implement virtual resource management and scheduling, and virtual network element lifecycle management functions. The network management support domain is respectively NFVO (Network FuncTIon Virtual Orchestrator). ), VNFM (Virtual Network FuncTIon Management), VIM (Virtual Infrastructure Management). NFVO implements unified resource management and scheduling; VNFM implements virtualized network element lifecycle management, including generation, change, and deletion of virtual network elements; VIM implements unified management of virtualized resources and hardware resource pools.
Using the advantages of NFV technology to redefine the operator's current operation and maintenance requires three important steps: The first step is to elaborate each of the current processes. The second step is to analyze which ones can be automated (ie, processed through the NFV platform) to reduce complexity. In the third step, the operation and maintenance is redesigned to make it more simplified and faster.
The NFV deployment process differs from traditional processes in many ways. The introduction of NFV will have a major impact on existing maintenance systems. The existing network generally follows the mode of professional maintenance (such as wireless, switching, data, bearer, transmission, etc.), and the related network elements maintained by each professional include hardware, software, network configuration, and service quality. After the introduction of NFV, the changes in the maintenance system are mainly reflected in the following two aspects: First, the functional network elements of each entity evolve into virtual network elements in the form of software. Traditional professional maintenance still exists, but maintenance is no longer required for device hardware. Second, the newly added NFV cloud maintenance, virtual resource management for each data center NFV architecture, including the corresponding scheduling software, cloud resource pool hardware, cloud network IP network maintenance.
Due to the need for professional services during deployment, NFV will cost slightly higher in the initial deployment. However, this is a one-time cost. As operators become more familiar with this architecture, they may use their own operations staff to do this locally. With NFV, applications can share infrastructure, so operators' operations teams need only be familiar with very limited network elements.
The introduction of the NFV platform will not fundamentally change the way operators plan and acquire software. However, NFV can reduce time and reduce costs when testing and creating environments. Operators can use the "sandbox" test environment without the need for dedicated equipment. This allows operators to create simplified test cases that can be executed concurrently and reduce test time by approximately one-third.
Maintenance is also an OPEX infrastructure cost. It is directly related to the number and nature of the projects included in the management team's physical architecture. Network elements in many traditional architectures require annual maintenance fees, including servers and network devices such as load balancers, switches, and routing ports.
Although any NFV system is accompanied by licensing and maintenance costs, licensing costs are significantly reduced compared to traditional methods. This is because the new approach requires much less network elements in the infrastructure, and when capacity needs change, the NFV platform can be applied and shared with the service.
NFV Lifecycle Management Program
For NFV operation and maintenance management, Shanghai Bell CloudBand Management System is the industry's first cloud computing platform designed specifically for carrier business NFV virtualization. The CloudBand management system helps administrators to carefully schedule and automatically run and optimize cloud platforms and various network elements and services. Provide convenient access and management functions through a secure, user-friendly interface. The CloudBand management system enables operators to provide advanced services to users at the lowest cost, meet operational costs, customer needs and other requirements through various customized optimization methods, improve service release speed, and reduce CAPEX and OPEX. At the same time, the CloudBand node provides nodes for computing power, storage, and hardware and related software required for network switching to implement wide-area cloud services. It scales based on the carrier's network while managing access to a variety of other public, private, and third-party cloud platforms.
It is worth mentioning that Nuage Networks, as Shanghai Bell's SDN product, can be integrated into the CloudBand management system to form an NFV infrastructure platform that supports the upper-layer virtualization business.
The virtualized network element is deployed on the cloud computing resource pool through the Carrier PaaS middleware in the CloudBand management system. The Carrier PaaS layer follows the TOSCA (Topology and OrchestraTIon SpecificaTIon for Cloud Application) specification to write a control script for each application, and implements the application cloud according to the control script. The script defines how the Carrier PaaS implements the application deployment and management during operation. And so on. The script implements several important functions, including network configuration, security policies, resource quantification, and more. The application cloudization process includes the process of controlling script writing, script execution, and business deployment. Usually, the script needs to have complete control over the resource environment to complete the cloud process of the entire application. The control script is a set of specific hierarchical structure scripts that reflect the topology of the application and can be parsed and executed by the Carrier PaaS layer to implement the deployment and management functions of the application in the cloud computing environment. A control script consists of a service layer, application lifecycle management logic, self-healing rules, elastic scaling logic, and monitoring rules.
In a simple scenario, you can see how CloudBand and Nuage SDN work together and support NFV (see figure). In the first step, the operation and maintenance personnel will send the MME expansion command from the 5620 SAM network management. In the second step, since vMME is built on the CloudBand platform, the requirement will be sent to the CloudBand management system. In the CloudBand platform, many XaaS functions are provided. Most of the NFV functions will be provided by cPaaS (Carrier-PaaS), corresponding to the MME. The vMME cPaaS, cPaaS uses a pre-created expansion script to create a virtual machine. The script defines the specific configuration of the virtual machine and the MME function attributes of the bearer. In the third step, when the new vMME virtual machine is successfully created, the next step is to add it to the vMME Pool. The Nuage SDN carrying the CloudBand Node can detect the new virtual machine generation and know its MME characteristics. The connection between the vMME virtual machine and the original vMME Pool. In the fourth step, vMME will return the operation result to the 5620 SAM.
NFV has entered a period of rapid development. The NFV architecture will have a great impact on the maintenance of the carrier network. New requirements are placed in the equipment room, equipment management, fault handling, and quality assurance. Shanghai Bell is working with operators worldwide. Will bring the experience of trial, pre-commercial and commercial use in the NFV world to China, and help Chinese network operators and emerging virtual operators through the continuous improvement of CloudBand products and NFV virtualized network elements and open NFV ecosystem. , build a softer and greener future network in a down-to-earth manner.
DroneLiPo Battery Blance Charger,Li-Ion Battery Charger,12S Battery Charger,Li Fe Battery Charger, Charging HUB
Drone LiPo Battery Blance Charger,Li-Ion Battery Charger,12S Battery Charger,Li Fe Battery Charger,Charging HUB
shenzhen GC Electronics Co.,Ltd. , https://www.jmrdrone.com