Description
A Service Function Chain defines a directed graph of Service Functions (SFs) that must be applied to packets or flows in a specific order to realize a network service. In the 3GPP architecture, particularly within the 5G Core network, SFC is a key enabler for network slicing and service-aware traffic steering. The chain is described by a Network Service Descriptor (NSD) which includes the topology and requirements of the virtualized network functions (VNFs) and/or containerized network functions (CNFs) that constitute the service.
The implementation of SFC involves several components: the Service Function Forwarder (SFF) which directs traffic between SFs, the SFC Classifier which maps incoming packets to a specific chain based on policies, and the SFC Proxy which may adapt traffic for legacy SFs. Traffic is often encapsulated with a Network Service Header (NSH) or similar metadata that carries the SFC context, including the chain identifier and position, ensuring packets traverse the correct sequence of functions regardless of the underlying network topology.
Within 3GPP, SFC is managed by the Network Slice Selection Function (NSSF) and the Network Repository Function (NRF) in conjunction with the Service Communication Proxy (SCP). It allows for the creation of end-to-end network slices where each slice can have its own unique SFC tailored for specific service requirements, such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), or massive IoT. This orchestration is typically controlled by management and orchestration (MANO) systems like NFV Orchestrator (NFVO) and SDN controllers.
Purpose & Motivation
Service Function Chaining was created to address the rigidity of traditional hardware-based middlebox deployments, where network services were implemented as physical appliances in fixed locations and sequences. This made service innovation, scaling, and maintenance costly and slow. SFC, enabled by Network Functions Virtualization (NFV) and Software-Defined Networking (SDN), allows operators to dynamically compose and deploy chains of virtualized functions, leading to agile service creation and efficient resource utilization.
The evolution towards 5G and network slicing necessitated a mechanism to provide isolated, customized logical networks over a shared physical infrastructure. SFC provides the technical framework to realize these slices by defining how traffic for a particular tenant or service type is processed through a specific set of functions (e.g., a firewall, NAT, TCP optimizer, video optimizer). It solves the problem of static, monolithic network architectures by enabling automated, policy-driven traffic steering.
Furthermore, SFC supports multi-vendor interoperability and service automation. By standardizing the chaining logic and headers (e.g., via IETF and 3GPP collaborations), it prevents vendor lock-in and allows mixed environments. This capability is crucial for meeting diverse 5G use case requirements, enabling operators to rapidly deploy new revenue-generating services with guaranteed performance and security characteristics.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the primary focus for the SFC (Service Function Chain) function was on foundational corrections and clarifications rather than introducing new capabilities. The changes consisted of editorial corrections and alignments to the existing SFC terminology and its abbreviation within the specifications. This included various fixes to the definition of SFC functionality to ensure consistency and clarity across the technical documentation.
- SFC CR 23.501 TS 23.501CR3860
- Corrections and alignments of SFC terminology TS 23.501CR4415
- Various corrections to the definition of SFC functionality TS 29.514CR0636
- Correction on SFC terminology and editorial issues TS 29.519CR0429
- Correction on SFC abbreviation TS 29.512CR1111
- Correction on SFC abbreviation TS 29.513CR0486
+ 1 more changes
Explore further
Broader topics and technologies where SFC plays a role.
Defining Specifications
3GPP specifications that define or reference SFC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TS 29.519 vj40 | UDR Usage for Policy & Exposure Data | Rel-19 |
| TS 46.008 vj00 | GSM Half Rate Speech Codec Performance | Rel-19 |