Description
The Internet Group Management Protocol (IGMP) is a fundamental component for IP multicast communication within 3GPP packet-switched networks. It operates between a host (such as a User Equipment - UE) and its directly connected multicast router, typically residing in the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW) in earlier and later architectures, respectively. IGMP is used by hosts to report their multicast group membership to neighboring routers, and by routers to query the multicast group membership of hosts on their directly attached subnets. This protocol is essential for the efficient delivery of multicast traffic, such as live video streaming or content distribution, over mobile networks.
IGMP functions through a series of message exchanges. The primary message types are Membership Query, sent by a router to discover which multicast groups have members on its attached links; and Membership Report, sent by a host to indicate it wishes to join a specific multicast group or in response to a query. A third type, the Leave Group message, allows a host to signal it is leaving a group, enabling routers to implement faster leave latency mechanisms. In a 3GPP context, the UE acts as the IGMP host. The protocol messages are typically tunneled within the Packet Data Protocol (PDP) context or PDN connection between the UE and the gateway node. The gateway, acting as the multicast router, processes these messages and interfaces with the IP multicast routing infrastructure (e.g., using Protocol Independent Multicast - PIM) to manage the flow of multicast traffic from the source into the mobile core network.
The protocol's role is to manage group membership on a per-link basis. When a UE wishes to receive traffic for a specific multicast group address, it sends an unsolicited IGMP Membership Report for that group. The router receives this report and, if it is not already receiving traffic for that group, initiates the process to join the appropriate multicast distribution tree. The router also periodically sends General Query messages to the 'all-hosts' multicast address. All hosts listening for multicast must respond with reports for the groups they are still interested in, allowing the router to prune groups that no longer have any local members. This state is maintained in the router's IGMP cache. For 3GPP, this mechanism is adapted to work over the logical point-to-point link represented by the GTP tunnel between the UE and the network, ensuring efficient use of radio and core network resources for multicast services.
Purpose & Motivation
IGMP was integrated into 3GPP standards to enable efficient IP-based multicast services over mobile networks. Prior to its adoption, delivering the same content to multiple users (e.g., a live sports event) would require separate unicast streams to each subscriber, leading to massive duplication of data and inefficient use of network capacity, especially on the radio interface. The primary problem IGMP solves is enabling scalable one-to-many and many-to-many communication models within the IP framework of 3GPP's packet core.
Its creation was motivated by the growing demand for bandwidth-intensive group communication services, such as mobile TV (MBMS), content distribution, and push-to-talk services. By allowing UEs to dynamically join and leave multicast groups, IGMP provides the network with the intelligence to deliver multicast packets only where they are requested, optimizing resource utilization. This was a critical enabler for 3GPP's Multimedia Broadcast Multicast Service (MBMS), where IGMP (and its IPv6 counterpart, MLD) serves as the signaling protocol for UEs to indicate their interest in specific MBMS content streams delivered over the IP layer.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-15.
In Release 15, the IGMP function was enhanced to support IPTV services by introducing a new "IP Multicast Accept" action for Packet Filters. This allows the system to process IGMP and MLD Membership Reports to accept multicast joins and add a PDU Session to the requested multicast group distribution. The support explicitly includes IGMPv2 and IGMPv3 as part of the Packet Filter Set.
In Release 16, the enhancements for IGMP were introduced within the broader context of session management for Fixed Network Residential Gateways (FN-RG) and 5G-RGs. Specifically, the protocol stacks for the Wireline 5G Access Network (W-5GAN) were updated, and Packet Filters were extended to explicitly support IGMPv2 and IGMPv3 for IP multicast services. Furthermore, a new "IP Multicast Accept" action was defined within PDU Session policies to control the acceptance of IGMP Membership Reports for multicast group joins.
In Release 18, the specification introduced explicit support for IGMP (and MLD) within Packet Filters for user plane management, referencing IGMPv2 and IGMPv3. Furthermore, a new "IP Multicast Accept" action was defined for session management rules, governing whether an IGMP Membership Report should be accepted to join a multicast group distribution within a PDU Session.
- Registration Management of AUN3 devices to follow TS 23.501 clause 5.5.1 TS 23.316CR2126
Explore further
Broader topics and technologies where IGMP plays a role.
Defining Specifications
3GPP specifications that define or reference IGMP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.316 vj30 | Wireline and Wireless Convergence Access Support | Rel-19 |
| TS 23.846 v1600 | MBMS Architecture and Functionality | Rel-6 |
| TS 26.802 vj20 | Multicast Enhancements for 5G Media Streaming | Rel-19 |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 |
| TS 29.061 vj00 | Packet Domain Interworking for PLMN | Rel-19 |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 |
| TS 33.820 v1830 | Home NodeB/eNodeB Security Architecture | Rel-8 |