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

Glossary term · Protocol

IGMP

Internet Group Management Protocol

Protocol →

IGMP is a network-layer protocol used by IP hosts and adjacent multicast routers to establish and manage multicast group memberships for efficient one-to-many data distribution in 3GPP networks.

Introduced
Rel-6
Where
Core Network › Legacy Core
Specifications
7 specs
Also in
Services
IGMP Description Purpose What changed Neighbours Specifications

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.

What changed in its specifications

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

TS 23.316Rel-18 → Rel-19

Rel-19 adds text to TS 23.316 for W-5GAN support of ECN marking for L4S, plus PDU Set based handling. Related procedures and references are also updated.

Full comparison in TS 23.316 →
TS 29.060Rel-18 → Rel-19

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

Full comparison in TS 29.060 →

Evolution Across Releases

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

Rel-6 Initial

Introduced IGMP support within the 3GPP architecture to enable IP multicast services, primarily for Multimedia Broadcast Multicast Service (MBMS). Defined the tunneling of IGMP messages between the UE and the GGSN within the PDP context, establishing the basic host-router model over the mobile network.

Defining Specifications

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

SpecificationTitleRelease
TS 23.316 vj30 Wireless and wireline convergence access support Rel-19 read
TS 23.846 v610 MBMS Architecture and Functionality Rel-6 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.281 vj20 GTPv1-U Protocol Specification Rel-19 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read