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

Glossary term · Services

TGI

Temporary MCVideo Group Identity

Services →

TGI is a temporary identifier that uniquely identifies a specific group session for video communication within the Mission Critical Video (MCVideo) service.

Introduced
Rel-13
Where
Services › IMS
Specifications
4 specs
TGI Description Purpose What changed Neighbours Specifications

Description

The Temporary MCVideo Group Identity (TGI) is a crucial identifier within the 3GPP Mission Critical Services (MCS) framework, specifically for the MCVideo service. MCVideo provides real-time group video communication for public safety, emergency services, and other mission-critical users. The TGI is a temporary, session-specific identifier assigned by the MCVideo system to a particular group call or video session. It is used to uniquely distinguish that session from all other ongoing sessions within the network for the duration of its activity. Unlike a permanent group ID (which identifies the predefined group of users), the TGI identifies the active communication instance itself.

Architecturally, the TGI is generated and managed by the core MCVideo service components, primarily the MCVideo Application Server. When an authorized user (e.g., a dispatcher or team leader) initiates a group video call, the server allocates a TGI for that session. This TGI is then disseminated to all participants' User Equipment (UE) and relevant network functions. It is used in the signaling plane to route session control messages (e.g., using SIP protocols) and in the media plane to identify the media streams associated with the call. The TGI is included in protocol messages for session establishment, modification, and termination, ensuring that all actions pertain to the correct session.

How it works involves several layers. At the service layer, the MCVideo client on a UE receives the TGI during session initiation signaling. The UE uses this TGI in all subsequent communication with the MCVideo server. In the underlying 3GPP system, the TGI may be mapped or associated with specific bearers or QoS flows to ensure the video traffic receives the appropriate priority and resources, as per the mission-critical QoS requirements. From a security perspective, the TGI is part of the security context; it can be used in key derivation for encrypting the video media, ensuring confidentiality within that specific group session. Its temporary nature is key—it is valid only for the lifetime of the call. Once the session ends, the TGI can be released and potentially reused later for a different session, aiding in resource management and preventing identifier exhaustion.

Purpose & Motivation

The TGI was created to address the specific needs of dynamic, secure, and manageable group communication in mission-critical environments. Traditional cellular group calls or conferencing systems often lacked a standardized, secure, and temporary identifier dedicated to a single session instance. Mission-critical operations require the ability to quickly spin up ad-hoc video groups, ensure communication is isolated and secure to that group, and efficiently manage multiple simultaneous ongoing incidents or operations. A permanent group identity alone is insufficient, as the same group of users may be engaged in multiple distinct video sessions (e.g., different tactical operations) concurrently.

The purpose of the TGI is to provide a handle for the system to uniquely manage each active session. It solves the problems of session disambiguation, secure media binding, and efficient routing. Historically, proprietary systems or early group communication services might have used less robust methods, leading to potential confusion or security mix-ups. The TGI, introduced as part of the standardized 3GPP MCVideo service from Release 13 onwards, provides a clean, scalable mechanism. It was motivated by the public safety community's requirements (led by organizations like TCCA and 3GPP SA6) for LTE-based mission-critical communications that are interoperable, reliable, and secure. The TGI enables features like dynamic group formation, strict access control to a specific session, and end-to-end encrypted media for that session, which are vital for law enforcement, firefighting, and emergency medical services.

What changed in its specifications

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

TS 24.281Rel-17 → Rel-18

Added MBS session management and XML schema types. Added MCVideo emergency and imminent peril adhoc group call procedures. Added MCVideo gateway UE function for non-3GPP access. Added 5G ProSe support to MCVideo. Added migration service authorization for MCVideo clients.

Full comparison in TS 24.281 →
TS 24.379Rel-18 → Rel-19

Rel-19 adds participant-criteria handling for ad hoc group emergency alerts, a Reason header with cause 200 on session-leaving messages, and SIP 302 rejection for migrated MCPTT IDs. It also adds location-information conditions for INVITE and REFER requests, removes implicit floor grants from such requests, and changes prearranged group call and emergency alert authorisation rules.

Full comparison in TS 24.379 →

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-13 Initial

Initially introduced with the foundational MCVideo service specifications. Defined the TGI as a core parameter for identifying a mission-critical video group session, establishing its role in session establishment, control, and security within the new MCVideo architecture over LTE.

Defining Specifications

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

SpecificationTitleRelease
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read
TS 36.579 3GPP TR 36.579 Rel-13 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read