Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

DHCP

Dynamic Host Configuration Protocol

Protocol →

DHCP is a network management protocol used in 3GPP networks to dynamically assign IP addresses and other configuration parameters to User Equipment and network functions for efficient resource management and connectivity.

Introduced
R99
Where
Core Network › Legacy Core
Specifications
25 specs
Also in
Services, Management
DHCP Description Purpose What changed Neighbours Specifications

Description

The Dynamic Host Configuration Protocol (DHCP) is a client-server protocol standardized by the IETF (RFC 2131) and adopted within 3GPP architectures to automate the assignment of IP configuration to network endpoints. Within a 3GPP system, DHCP operates primarily in the packet-switched domain, often facilitated by network elements like the Packet Data Network Gateway (PGW) in EPS or the User Plane Function (UPF) in 5GC. The protocol's primary role is to provide a UE with an IP address, subnet mask, default gateway, and DNS server addresses upon network attachment or during a PDN connection establishment, eliminating the need for manual configuration.

The protocol operates through a four-message exchange known as DORA: Discover, Offer, Request, and Acknowledge. When a UE initiates a PDN connection, its DHCP client broadcasts a DHCPDISCOVER message. A DHCP server, which may be co-located with a gateway or be a separate network entity, responds with a DHCPOFFER containing a proposed IP address and configuration. The UE then sends a DHCPREQUEST to formally request the offered parameters, and the server confirms with a DHCPACK, finalizing the lease. This lease has a defined lifetime, after which the address can be reclaimed and reassigned, managed through renewal and rebinding processes.

Key architectural components include the DHCP client (residing in the UE), the DHCP server, and optionally, DHCP relay agents. Relay agents are crucial in large-scale 3GPP deployments as they forward DHCP messages between clients on different IP subnets (e.g., the mobile access network) and centralized servers. The protocol supports various message types for different operations, including lease renewal (DHCPREQUEST), release (DHCPRELEASE), and informational queries (DHCPINFORM). In 3GPP, DHCP is integral to IP address management (IPAM) and is used not only for initial UE configuration but also for provisioning parameters in scenarios like Wireless Local Area Network (WLAN) interworking and fixed-mobile convergence.

Beyond basic IP assignment, DHCP in 3GPP networks can deliver a wide array of configuration options defined in RFCs, such as SIP server addresses, P-CSCF discovery information for IMS, and specific routing policies. Its integration is specified across multiple 3GPP technical specifications, detailing its use within the GTP-based S5/S8 interfaces, the Packet Data Protocol (PDP) context activation procedures, and service-based interfaces in 5GC. The protocol's stateless and stateful modes provide flexibility, with stateless DHCPv6 being used for parameter provisioning when addresses are configured via other means like SLAAC.

Purpose & Motivation

DHCP was created to solve the administrative burden and scalability limitations of manual IP address configuration (static assignment) in IP networks. Prior to DHCP, network administrators had to manually configure each device with a unique IP address, subnet mask, and gateway, a process prone to human error, address conflicts, and inefficiency, especially in large or dynamic environments like mobile networks where devices frequently connect and disconnect.

In the context of 3GPP, the adoption of DHCP was motivated by the transition to all-IP core networks starting with GPRS and UMTS. As mobile networks evolved to support packet-switched data services for a massive number of User Equipment, a dynamic, automated method for IP address management became essential. DHCP enables efficient pooling and reuse of scarce IPv4 addresses, supports the mobility of devices across network points of attachment, and allows for centralized management of network policies. It solves the problem of providing consistent, error-free network configuration to millions of devices without manual intervention.

Furthermore, DHCP facilitates advanced services and network architectures. It is a foundational enabler for IP Multimedia Subsystem (IMS) by providing UEs with the addresses of critical call session control functions (P-CSCF). It also supports network evolution, including the integration of non-3GPP access (like WLAN) and the deployment of dual-stack IPv4/IPv6. By automating configuration, DHCP reduces operational costs, minimizes service provisioning time, and enhances the user experience through seamless 'always-on' connectivity.

What changed in its specifications

The latest release-to-release comparison of specifications that define DHCP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.057Rel-4 → Rel-5

Rel-5 added MExE Classmark 4 for CLI Compact Profile devices, covering architecture, security, charging, and capability negotiation.

Full comparison in TS 23.057 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced DHCP as the primary mechanism for dynamic IP address allocation within the GPRS/UMTS packet core. It was integrated into the PDP context activation procedure, allowing the Gateway GPRS Support Node (GGSN) to act as or interface with a DHCP server to provide the UE with an IP address and essential configuration parameters, establishing the foundation for automated IP management in 3GPP networks.

Defining Specifications

3GPP specifications that define or reference DHCP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.234 vd10 3GPP-WLAN Interworking Index Rel-13 read
TS 23.327 vd10 3GPP-WLAN Mobility Stage 2 Description Rel-13 read
TS 23.804 v710 SMS/MMS over IP Access Networks Rel-7 read
TS 23.868 v900 Study on IMS Emergency Calls Rel-9 read
TR 23.976 vj00 Push Service Requirements Analysis Rel-19 read
TR 23.981 vj00 IPv4 IMS Interworking and Migration Study Rel-19 read
TS 24.228 v590 IP Multimedia Call Control Signaling Flows Rel-5 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19 read
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20 read
TS 24.523 vj00 NGCN-NGN Interconnection Scenarios Rel-19 read
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19 read
TS 28.314 vk10 Plug and Connect Concepts and Requirements Rel-20 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.161 vc00 3GPP-WLAN Interworking Requirements Rel-12 read
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.501 vj00 Self-Configuration of Network Elements Concepts Rel-19 read
TS 33.812 v920 M2M Remote Subscription Management Security Rel-9 read