Virtualized Network Function

Description

A Virtualized Network Function (VNF) is a software-based realization of a network function that was traditionally implemented as a dedicated physical appliance. In the context of 3GPP and ETSI NFV, a VNF is a deployable unit of functionality—such as a Mobility Management Entity (MME), a Packet Data Network Gateway (PGW), or a Session Border Controller (SBC)—that is packaged as software and can run on virtual machines (VMs) or containers atop a shared, cloud-like infrastructure called the NFV Infrastructure (NFVI). The VNF itself comprises one or more internal components (VNF Components - VNFCs) that may be deployed on separate virtualized resources. Each VNF has a descriptor (VNFD) that defines its requirements: compute, storage, networking needs, and lifecycle management behavior.

How a VNF works involves its instantiation, configuration, and management by an NFV Management and Orchestration (MANO) framework. The orchestrator (NFVO) uses the VNFD to request the allocation of virtual resources (from NFVI) via the Virtualized Infrastructure Manager (VIM). Once the virtual environment (e.g., a VM with specific CPU, memory, network interfaces) is created, the VNF software image is deployed onto it. The VNF Manager (VNFM) then handles the lifecycle of that specific VNF instance: starting it, configuring it with network parameters (like IP addresses, routing rules), scaling it (adding/removing VNFCs based on load), updating it, and terminating it. The VNF executes its intended network function (e.g., routing packets, managing sessions) just as the physical node would, but it communicates over virtual networks and uses abstracted resources.

Key components within the VNF architecture include the VNFCs, which are the modular software processes; the VNF's internal management interface for the VNFM; and its external functional interfaces that connect to other VNFs or physical network functions (PNFs) to form a service chain. For example, a VNF implementing a 5G Core Network Function (like an AMF) would have interfaces to communicate with other core VNFs (SMF, UPF) and the RAN. Its role in the network is to provide the same telecom service as a hardware box, but with the agility of software: it can be rapidly deployed, elastically scaled to handle traffic fluctuations, and centrally managed, which drastically reduces costs and increases operational flexibility. 3GPP specifications, particularly in the management domain (e.g., TS 28.541, TS 28.545), define requirements and interfaces for VNFs as part of the overall virtualized network architecture.

Purpose & Motivation

The VNF concept exists to transform telecommunications networks from hardware-centric to software-centric, addressing the problems of high cost, long deployment cycles, and inflexibility associated with proprietary physical appliances. Traditional network nodes were monolithic, requiring dedicated space, power, and manual configuration. Scaling required buying and installing more boxes. This model was unsustainable with the explosion of data traffic and the need for rapid service innovation. Virtualization, inspired by cloud computing, motivated the creation of VNFs to decouple network functions from hardware.

NFV, and thus VNFs, were created to solve these limitations by allowing network functions to run as software on commercial off-the-shelf servers in data centers. This reduces capital expenditure (shared hardware) and operational expenditure (automated management). It also enables faster introduction of new services by simply deploying new VNF software. For 3GPP, the adoption of VNFs (formalized in Rel-13) was driven by the need to make core networks (EPC, 5GC) more agile and scalable to support diverse services like IoT and network slicing. It allows operators to dynamically allocate resources where needed, improving efficiency.

The historical context is that the telecom industry, led by ETSI's NFV ISG, began this transformation around 2012. 3GPP integrated these concepts into its management specifications to ensure that virtualized 3GPP network functions (like those in the 5G Core) could be managed consistently. VNFs are the fundamental enablers of cloud-native networks, supporting automation, scalability, and the economic model needed for future telecom services.

Key Features

• Software implementation of a network function, deployable on virtualized infrastructure
• Defined by a VNF Descriptor (VNFD) specifying resource and connectivity requirements
• Composed of one or more VNF Components (VNFCs) for modular deployment
• Lifecycle managed by a VNF Manager (VNFM) (instantiation, scaling, termination)
• Can be elastically scaled (in/out, up/down) based on load and policies
• Interconnects with other VNFs/PNFs via virtual networks to provide end-to-end services

Evolution Across Releases

Defining Specifications