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

Glossary term · Identifier

TMGI

Temporary Multicast Group Identifier

Identifier →

TMGI is a unique identifier used in 3GPP networks to identify a specific MBMS session, enabling user equipment to discover, join, and receive multicast or broadcast content.

Introduced
Rel-6
Where
Services › Codecs
Specifications
55 specs
Also in
Core Network, Radio Access Network, User Equipment
TMGI Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Temporary Multicast Group Identifier (TMGI) is a critical identifier within the 3GPP Multimedia Broadcast Multicast Service (MBMS) architecture. It uniquely identifies a specific MBMS session within a PLMN (Public Land Mobile Network) or across PLMNs. A TMGI is not a permanent address but is temporarily assigned for the duration of a specific MBMS service session. Its structure, defined in 3GPP TS 23.003, typically includes a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a service-specific group ID, allowing for global or network-specific uniqueness.

The TMGI's primary function is to act as a handle for the entire MBMS service delivery chain. Service announcement procedures, which inform User Equipment (UE) about available MBMS content, include the TMGI. When a UE wishes to receive a service, it uses the TMGI to initiate a join procedure towards the network, indicating its interest in the specific multicast group. Within the core network, the BM-SC (Broadcast Multicast Service Center) allocates the TMGI and uses it to identify the bearer and session towards the access network. In the radio access network (RAN), the TMGI is used to identify the common radio resources (like an MBMS Point-to-Multipoint Control Channel) allocated for that session, enabling multiple UEs to efficiently receive the same data stream.

From a protocol perspective, the TMGI is carried in multiple layers. It appears in NAS (Non-Access Stratum) signaling messages for session management, in RRC (Radio Resource Control) messages for multicast group management in the RAN, and is integral to the IP multicast addressing scheme used for the data plane. The network uses the TMGI to map the MBMS service to a specific IP multicast address and port combination for data distribution. This end-to-end binding ensures that from the service originator (BM-SC) to the receiving UE, all network elements can correctly identify and process the data flow associated with a particular broadcast or multicast session.

Purpose & Motivation

The TMGI was created to solve the fundamental problem of identifying and managing multicast sessions in a cellular environment. Unlike unicast, where a connection is unique to a single UE, multicast involves delivering the same content to potentially millions of devices. A unique, session-specific identifier was needed to allow UEs to signal their interest (join/leave), for the network to allocate shared resources efficiently, and to distinguish between multiple concurrent MBMS services.

It addresses the limitations of using only IP multicast addresses for this purpose in a mobile context. An IP multicast group address alone does not contain the necessary network routing context (e.g., home network) and is not ideal for signaling in mobile-specific control planes. The TMGI provides a structured, mobile-network-friendly identifier that incorporates PLMN identity, enabling network-based service discovery, access control, and roaming support. Its creation was motivated by the introduction of MBMS in Release 6, which aimed to enable efficient mass content delivery (like mobile TV) over 3GPP networks, requiring a robust session management and identification mechanism tailored for cellular architectures.

What changed in its specifications

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

TS 23.246Rel-18 → Rel-19

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

Full comparison in TS 23.246 →
TS 23.247Rel-17 → Rel-18

Rel-18 adds 5G MBS Phase 2 features such as group message delivery and power-saving support for MBS reception. It also adds NR RedCap UE long eDRX support in RRC_INACTIVE, SEAL data delivery architecture with new reference points, and a new Nnef_MBSGroupMsgDelivery service.

Full comparison in TS 23.247 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method
  • TMGI used together with MBMS Bearer Service
    “The TMGI is a radio resource efficient MBMS bearer service identification, which is equivalent to the MBMS bearer service identification consisting of IP multicast address and APN.” TS 23.246

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 10 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-6 introduced

TMGI was added to the specifications in Rel-6 as an identifier for MBMS, with its structure and use for MBMS notification specified.

  • Addition of TMGI TS 23.003CR088r1
  • Structure and use of TMGI for MBMS notification TS 25.304CR0150
Rel-7 1 CR

A change request to TS 23.003 addresses the structure of the TMGI, indicating a technical correction or addition to how the identifier is defined.

Rel-12 specification text

TS 29468 (MB2-C) is first specified here, defining TMGI assignment by the BM-SC to the GCS AS, expiration handling, Flow ID association, and the TMGI Allocation procedure.

  • “A TMGI shall be assigned by the BM‑SC upon request of the GCS AS.” TS 29.468 v12.5.0
  • “The TMGI Allocation procedure may be used by the GCS AS to request a set of TMGIs” TS 29.468 v12.5.0
  • “The combination of TMGI and Flow Identifier shall uniquely identify an MBMS bearer.” TS 29.468 v12.5.0
Rel-13 1 CR

In 29468 the TMGI-related MB2-C procedures changed: MBMS Cell List feature added to bearer activation and modification, and TMGI allocation and deallocation results now carry error bits including internal BM-SC errors.

  • “The GCS AS can find out whether the BM‑SC supports the MBMS Cell List feature prior to applying the Activate MBMS Bearer Procedure” TS 29.468 v13.5.0
  • “The requested TMGI allocation failed due to internal system error in the BM-SC.” TS 29.468 v13.5.0
  • Addition of ProSe Per-Packet Priority & QCI in the TMGI Monitoring Request procedure TS 23.303CR0310
Rel-14 2 CRs

TMGI handling was extended in Rel-14, with a reserved TMGI range for Receive Only Mode and TMGI/PLMN ID use for shared MBMS networks, plus TMGI AVP use in MBMS bearer activation with the V2X feature.

  • Reserved range of TMGI for Receive Only Mode TS 23.003CR0472
  • Use of TMGI & PLMN ID for Shared MBMS Network TS 23.246CR0408
  • “For the activation of an MBMS bearer, the TMGI AVP, the MBMS‑Start‑Time AVP and the MB2U‑Security AVP may be included” TS 29.468 v14.6.0
Rel-15 1 CR

TMGI handling was specified and corrected: TS 29.122 gained TMGI allocation, renewal and deallocation procedures via the SCEF, and TS 29.468 changed TMGI AVP inclusion rules and the TMGI Deallocation Result value.

  • “the SCEF shall initiate TMGI allocation by the BM-SC as defined in subclause 5.2.1 of 3GPP TS 29.468 [36].” TS 29.122 v15.18.0
  • “In order to deallocate the TMGI, the SCS/AS shall send an HTTP DELETE message to the SCEF to the resource "Individual TMGI Allocation".” TS 29.122 v15.18.0
  • Correction of Value for TMGI Deallocation Result AVP TS 29.468CR0029
Rel-16 1 CR

A change request for TS 29.122 renews TMGI expiration handling, altering how the TMGI lifetime is managed.

Rel-17 1 CR

Rel-17 specifies TMGI use for 5G MBS: allocation and deallocation via the new Nmbsmf_TMGI service, TMGI use for multicast and broadcast MBS sessions, and TMGI-based paging.

  • “The TMGI Allocate service operation (Nmbsmf_TMGI_Allocate) shall be used by NF Service Consumers to request the allocation of TMGI(s).” TS 29.532 v17.5.0
  • “is used to be able to identify a broadcast MBS Session or a multicast MBS session.” TS 23.247 v17.12.0
  • Definition of TMGI for MBS in 5GS TS 23.003CR0617
Rel-18 2 CRs

TMGI handling changed in Rel-18: a CR resolved the editor's note on TMGI index and TMGI update for MOCN configuration, and NG-RAN may now advertise the TMGI and reuse radio resources for the same content.

  • Resolving the EN on TMGI index and TMGI update for the configuration mechanism in the MOCN enhancement TS 23.247CR0232
  • “the NG-RAN advertises the TMGI of the broadcast MBS session, and reuses such already allocated radio resource for the MBS data transmission” TS 23.247 v18.8.0
  • Indicate to lower layer to delete stored TMGI R18 TS 24.501CR4810
Rel-20 1 CR

A correction was made to the TMGI field in the MBS subchannel control, as stated by a CR approved for Rel-20 in TS 24.380.

  • Correction of TMGI field in MBS subchannel control R20 TS 24.380CR0382

Defining Specifications

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

SpecificationTitleRelease
TS 23.246 vj00 MBMS Bearer Service Stage 2 Description Rel-19 read
TS 23.247 vk00 5G Multicast and Broadcast Services Rel-20 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19 read
TS 23.479 vj00 MBMS API for Mission Critical Services Rel-19 read
TS 23.768 vc10 GCSE_LTE Architecture Study Rel-12 read
TR 23.780 ve00 MBMS for Mission Critical Communication Services Rel-14 read
TS 23.792 vg00 MBMS API for Mission Critical Services Rel-16 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TS 24.008 vk10 NAS Call, Mobility and Session Procedures Rel-20 read
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.334 vj00 ProSe Protocols and Procedures Rel-19 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.575 vj00 UE Pre-configuration for MBS Rel-19 read
TS 24.578 vj00 UE policies for A2X services in 5GS Rel-19 read
TS 24.581 vj30 MCVideo Media Plane Control Rel-19 read
TS 24.587 vj30 V2X Services Protocols for 5G System Rel-19 read
TS 24.588 vj00 UE Policies for V2X Services in 5GS Rel-19 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.517 vj30 5G MBS User Service Protocols Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12 read
TS 26.852 ve20 MBMS user service profiles, APIs and transport enabler study Rel-14 read
TS 26.880 ve00 MBMS Enhancements for Mission Critical Video Rel-14 read
TR 26.946 vj00 MBMS User Services Overview Rel-19 read
TR 26.981 vj00 MBMS Provisioning & Content Ingestion Interface Study Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.532 vk00 Nmbsmf Service Based Interface Specification Rel-20 read
TS 29.549 vk10 SEAL Service APIs Rel-20 read
TS 29.580 vk00 MBSF Nmbsf Service-Based Interface Rel-20 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read
TR 33.883 vi01 Technical Report on 5G Multicast-Broadcast Services Security Rel-18 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.579 3GPP TR 36.579 Rel-6 read
TS 36.868 vc00 Study on Group Communication for E-UTRA Rel-12 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 43.246 vj00 MBMS in GERAN Stage 2 Specification Rel-19 read
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19 read