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.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the DHCP function saw corrections to name fields and protocol numbers, as well as an update to N3AN node configuration information. Additionally, an editor's note was added regarding the usage of the Any_PLMN entry configuration.
- TCP protocol as inner transport layer protocol for NAS signaling TS 24.502CR0040
- Correction of name fields and protocol numbers TS 24.502CR0029
- Editor's note on usage of Any_PLMN entry configuration TS 24.502CR0034
- Correction on N3AN node configuration information TS 24.502CR0043
- No UE configuration parameters for connectivity to ePDG by UICC TS 24.302CR0675
In Release 16, the updates to the DHCP function included a correction to the IKEv2 protocol's RFC number and introduced specifications for handling the protocol type field within GRE encapsulated user data packets. These changes refined the protocol data unit handling for specific packet formats. The modifications were implemented through updates to the relevant elementary procedures governing these protocol interactions.
In Release 17, the update for the DHCP function specifically involved a reference update to align with the HTTP/1.1 protocol. This change ensures that the application protocol procedures for service access are current. No other new capabilities or procedures for DHCP were introduced in this release beyond this referential update.
- Reference update for HTTP/1.1 protocol TS 29.201CR0049
In Release 18, the DHCP function was enhanced to support the configuration of an extended home N3IWF identifier and slice-specific N3IWF prefix information for both IMS and non-IMS services. These updates facilitate improved N3IWF selection procedures by providing more granular configuration data to the user equipment. The changes enable the network to provision specific access parameters based on the network slice and service type.
- Update N3AN node configuration information provisioning TS 24.502CR0222
- N3IWF selection for non-IMS services supporting extended home N3IWF identifier configuration and slice-specific N3IWF prefix configuration TS 24.502CR0248
- N3IWF selection for IMS services supporting extended home N3IWF identifier configuration and slice-specific N3IWF prefix configuration TS 24.502CR0236
- Encabsulating EAP-5G message in the link layer protocol for the trusted non-3GPP access TS 24.502CR0264
In Release 19, the DHCP function was updated to resolve the configuration for the Emergency Number (EN) for the Standalone IMS Data Channel (DC) feature. Additionally, the release provided clarification on the configuration of Public Service Identities (PSI) on the User Equipment (UE).
Explore further
Broader topics and technologies where DHCP plays a role.
Defining Specifications
3GPP specifications that define or reference DHCP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 |
| TS 23.060 vj00 | GPRS Service Description Stage 2 | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 |
| TS 23.327 vd10 | 3GPP-WLAN Mobility Stage 2 Description | Rel-13 |
| TS 23.804 v1700 | SMS/MMS over IP Access Support | Rel-7 |
| TS 23.868 v900 | Study on IMS Emergency Calls | Rel-9 |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 |
| TR 23.981 vj00 | IPv4 IMS Interworking and Migration Study | Rel-19 |
| TS 24.228 v1500 | IP Multimedia Call Control Signaling Flows | Rel-5 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 24.523 vj00 | NGCN-NGN Interconnection Scenarios | Rel-19 |
| TR 26.944 vj00 | QoE, ESQoS and SQoS metrics for 3G multimedia services | Rel-19 |
| TS 28.314 vk00 | Management and Orchestration - Plug and Connect | Rel-20 |
| TS 29.061 vj00 | Packet Domain Interworking for PLMN | Rel-19 |
| TS 29.161 vc00 | 3GPP-WLAN Interworking Requirements | Rel-12 |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.501 vj00 | Self-Configuration of Network Elements Concepts | Rel-19 |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 |