TSI

Transport Session Identifier

Identifier →
Introduced in Rel-6

TSI is a unique identifier for a transport session, such as an MBMS bearer, that enables a 3GPP network to correctly route and manage data flows for point-to-multipoint services.

Category
Identifier
Introduced
Rel-6
Where
Services › Codecs
Specifications
5 specs
TSI Description Purpose Related Classification Specifications

Description

The Transport Session Identifier (TSI) is a fundamental element within the 3GPP Multimedia Broadcast/Multicast Service (MBMS) architecture, specifically defined for the MBMS Bearer Service. It serves as a unique, network-wide identifier for a specific MBMS transport session. A transport session represents the data flow for a particular MBMS service, such as a live TV stream or a software update distribution, over a defined period. The TSI is assigned by the Broadcast-Multicast Service Center (BM-SC), which is the core network entity responsible for authorizing and initiating MBMS sessions.

Architecturally, the TSI is carried within MBMS-specific control and user plane protocols. In the control plane, it is included in session start and stop messages sent from the BM-SC to the MBMS Gateway (MBMS-GW) and further to the radio access network (e.g., the eNB in LTE or gNB in 5G NR). This allows all network elements involved in the MBMS data path to uniquely identify the session they are to handle. In the user plane, the TSI is typically part of the packet headers (e.g., in the Generic Routing Encapsulation (GRE) key for the M1 interface between MBMS-GW and eNB/gNB), enabling the correct multiplexing and demultiplexing of data packets belonging to different MBMS sessions over shared transport resources.

The TSI works in conjunction with other identifiers, such as the Temporary Mobile Group Identity (TMGI), which identifies the MBMS service from a user subscription perspective. While the TMGI is known to the UE and used for service discovery and joining, the TSI is primarily a network-internal identifier for session management and routing. Its role is critical for scalability and efficiency, as it allows a single radio cell to broadcast multiple concurrent MBMS services. The network uses the TSI to map the correct data to the correct radio bearers and to manage session lifecycle events, like activation and deactivation, without ambiguity.

Key components interacting with the TSI include the BM-SC (which generates it), the MBMS Gateway (which uses it for bearer binding and packet forwarding), and the radio access network nodes (which use it to establish the appropriate point-to-multipoint radio bearers). Its consistent use across these interfaces ensures synchronized session state across the network. The TSI is a cornerstone for reliable MBMS operation, preventing data misdelivery and enabling efficient resource utilization for broadcast and multicast traffic, which is essential for applications like public safety communications, content delivery to large audiences, and V2X messaging.

Purpose & Motivation

The TSI was created to address the fundamental requirement of uniquely identifying individual transport sessions within the 3GPP MBMS framework. Prior to MBMS, cellular networks were optimized for point-to-point (unicast) communication, where a dedicated connection is established between the network and each user. This model is inefficient for delivering identical content to many users simultaneously, as it duplicates data across the core and radio network, wasting bandwidth and radio resources.

The introduction of MBMS in 3GPP Release 6 required a new paradigm: point-to-multipoint delivery. This introduced the concept of a 'session'—a temporary data flow for a specific service. The network needed a robust mechanism to distinguish between multiple concurrent sessions, especially in a single cell broadcasting several TV channels or data streams. The TSI solves this by providing a unique handle for the network infrastructure. It allows the BM-SC to instruct the network to start or stop carrying a specific data flow, and it enables routers and base stations to correctly associate incoming IP packets with the correct broadcast radio bearer.

Without a unique transport session identifier, the network would be unable to manage multiple broadcast flows, leading to potential misrouting of data, inability to independently control sessions, and overall unreliability of the MBMS service. The TSI, therefore, is a key enabler for the scalability and manageability of broadcast and multicast services in 3GPP networks, forming an essential part of the control and user plane separation for group communication. It addressed the limitations of pure unicast delivery for mass content distribution and laid the groundwork for evolved multimedia broadcast services like eMBMS (Evolved MBMS) and FeMBMS (Further evolved MBMS).

Classification

Part ofMBMS
Related approachesTMGIBM-SC

Release Timeline

Evolution Across Releases

Rel-6 Initial

The TSI was initially introduced as part of the foundational Multimedia Broadcast/Multicast Service (MBMS) architecture. It was defined as a key identifier within the MBMS bearer context, carried in session control signaling from the BM-SC and used for establishing point-to-multipoint packet data contexts in the UTRAN.

Enhancements to MBMS continued, with refinements to procedures involving the TSI for session start, update, and stop. Support for MBMS in the PS domain was solidified.

TSI was carried forward into the Evolved Packet System (EPS) for LTE. The architecture evolved with the introduction of the MBMS Gateway (MBMS-GW) and the M1 interface, where the TSI is used as part of the GRE key for user plane identification between MBMS-GW and eNB.

Further integration of MBMS into LTE (eMBMS). The TSI's role remained consistent in the updated control plane procedures for E-UTRAN.

No major changes to the TSI concept. MBMS enhancements focused on other areas like service continuity.

No major changes to the TSI concept. Work on MBMS service layer aspects continued.

No major changes to the TSI concept. MBMS work included integration with Wi-Fi and service discovery.

No major changes to the TSI concept. Focus on proximity services and public safety.

Introduction of Further evolved MBMS (FeMBMS) and EnTV. The TSI remained a core component for broadcast session management in the enhanced architecture supporting standalone broadcast operation.

TSI carried forward into 5G for 5G Broadcast. The principle remained the same, with the identifier used within the 5G core network for 5G Media Streaming and multicast-broadcast session management.

Enhancements for 5G multicast-broadcast services. The TSI's role persisted in the context of the 5G Multicast-Broadcast User Service, ensuring backward compatibility and consistent session identification.

Continued work on 5G multicast-broadcast, including integration with NR. The TSI remains a fundamental identifier for transport sessions within the 5G system architecture.

Ongoing evolution of 5G Advanced features for multicast-broadcast. The TSI continues to be specified as the key transport session identifier.

The TSI is maintained as a stable identifier within the 5G multicast-broadcast service framework, supporting new use cases and enhancements.

Explore further

Broader topics and technologies where TSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TS 26.852 ve20 MBMS user service profiles, APIs and transport enabler study Rel-14
TR 26.946 vj00 MBMS User Services Overview Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.