Description
Hybrid Fiber-Coaxial (HFC) is a telecommunications access network technology that combines optical fiber and coaxial cable in a single network architecture. In the 3GPP context, HFC represents the cable access network infrastructure that can be integrated with 5G system architectures to provide converged fixed-mobile services. The HFC network typically consists of a headend or cable modem termination system (CMTS) connected via fiber optic cables to fiber nodes, which then distribute signals over coaxial cable to individual subscriber premises. This hybrid approach leverages the high bandwidth and low attenuation of fiber for the backbone and distribution segments while utilizing existing coaxial infrastructure for the last-mile drop to customer premises.
Within the 3GPP framework introduced in Release 16, HFC access is addressed primarily in the context of 5G convergence with fixed broadband networks. The specifications 23.716 describe the study on wireless and wireline convergence for the 5G system architecture, where HFC represents one of the key access technologies that can be integrated. The architecture allows an HFC access network to connect to the 5G core network through a wireline access gateway function (W-AGF), enabling cable subscribers to receive 5G services through their existing HFC infrastructure. This integration supports the concept of a single 5G core serving multiple access types including 3GPP access (NR, LTE) and non-3GPP access (WLAN, wireline including HFC).
Key components of the HFC architecture in the 3GPP context include the Cable Modem (CM) or Cable Modem Termination System (CMTS) at the network side, the fiber node that serves as the transition point between fiber and coaxial segments, and the customer premises equipment (CPE) that includes the cable modem. The 5G-RG (5G Residential Gateway) function is particularly important as it acts as the customer premises equipment that connects to the 5G core network via the HFC access network. The W-AGF in the 5G core network terminates the wireline access protocols and provides the interface between the HFC access network and the 5G core network functions such as AMF, SMF, and UPF.
The protocol architecture for HFC integration with 5G involves multiple layers. At the physical layer, DOCSIS (Data Over Cable Service Interface Specification) technology governs the transmission over the coaxial and fiber segments. The 3GPP specifications 29.214, 29.507, 29.512, 29.514, 29.525, 29.561, and 29.571 define various policy, charging, and management interfaces that apply to the converged architecture. The N1, N2, and N3 interfaces are extended to support wireline access, with the W-AGF translating between wireline-specific protocols and 3GPP core network protocols. The 38.413 specification addresses NG-RAN aspects that may interact with HFC-connected devices through the 5G core.
HFC integration with 5G networks enables operators to offer unified services across both mobile and fixed access, supporting use cases such as fixed wireless access replacement, converged billing, and seamless service continuity. It allows cable operators to become 5G service providers without deploying their own radio access networks, and enables mobile operators to extend coverage and capacity through existing cable infrastructure. The technology is particularly relevant for residential broadband, enterprise connectivity, and the delivery of enhanced mobile broadband (eMBB) services in areas where HFC infrastructure is already deployed.
Purpose & Motivation
HFC exists as a network architecture to leverage the complementary strengths of two transmission media: optical fiber provides high bandwidth, low attenuation, and immunity to electromagnetic interference over long distances, while coaxial cable provides a cost-effective last-mile solution that can reuse existing cable television infrastructure. The primary motivation for integrating HFC with 3GPP systems is to enable fixed-mobile convergence, allowing cable operators to offer 5G services and mobile operators to leverage cable infrastructure for backhaul and access.
Before the 3GPP integration work in Release 16, HFC networks operated independently using DOCSIS standards defined by CableLabs, with no standardized interworking with mobile core networks. Subscribers had separate subscriptions, separate billing, and no service continuity between fixed and mobile access. The convergence architecture defined in 3GPP specifications addresses these limitations by providing a standardized framework for connecting HFC access networks to the 5G core, enabling unified authentication, policy control, charging, and session management across access types.
The creation of HFC-related specifications in 3GPP was motivated by the industry trend toward network convergence, where operators seek to provide seamless services regardless of the access technology used. This is particularly important for delivering services like voice over Wi-Fi/cable, converged multimedia, and enterprise services that require consistent quality of experience across different access networks. The 5G-RG concept allows a single device to connect through HFC and receive the same services as a 5G mobile device, with the network handling the access-specific details transparently.
What changed in its specifications
The latest release-to-release comparison of specifications that define HFC. Each summary describes the whole specification, not only this term.
Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.
Full comparison in TS 23.003 →Rel-19 adds IMS disaster prevention and restoration enhancements, including PCEF failure detection and a new PC-Session-Recovery-Status AVP. It also adds Multimedia Priority Service for Messaging support and satellite access charging with a Serving-Satellite-Identity AVP.
Full comparison in TS 29.214 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference HFC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.003 vk10 | Numbering, Addressing and Identification | Rel-20 read |
| TS 23.716 vg00 | Wireline and Trusted Non-3GPP Access to 5G Core | Rel-16 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 29.507 vk10 | Access and Mobility Policy Control | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.525 vk10 | UE Policy Control Service | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.571 vk10 | 5G Common Data Types | Rel-20 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |