TSI

Transport Session Identifier

Identifier →
Introduced in Rel-8

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-8
Where
Services › Codecs
Specifications
5 specs
TSI Description Purpose Related Classification Detected Changes 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

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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-8, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the TSI (Transport Session Identifier) function was newly introduced to support the SAND (Service and Network-Assisted Delivery) capability for MBMS, enabling enhanced delivery methods. This release also introduced the application of Forward Error Correction (FEC) and Robust Header Compression (ROHC) specifically for mission-critical services delivered over MBMS bearers, improving reliability and efficiency for these user services.

  • Support for SAND for MBMS TS 26.946CR0015
  • FEC and ROHC for mission critical services over MBMS TS 29.116CR0021
Rel-16 4 changes

In Release 16, the TSI function was enhanced to improve the management of MBMS delivery sessions. Specifically, updates addressed the handling of the Session Announcement file for download delivery sessions and resolved issues with missing push URLs in file-based sessions. These changes ensured more reliable session establishment and resource allocation for MBMS user services.

  • Missing XML Data Type for Attributes in MBMS USD TS 26.346CR0658
  • MBMS resource sharing TS 29.116CR0037
  • SA file returned for the download delivery session TS 29.116CR0038
  • Fix the missing push url in file session TS 29.116CR0047
Rel-19 2 changes

In Release 19, the TSI function was enhanced to support in-session unicast repair for MBMS object distribution, allowing for the recovery of lost data during an ongoing multicast session. This was complemented by improvements to time synchronization mechanisms for MBMS, ensuring more reliable and coordinated delivery of content components. These updates provided greater robustness and efficiency for MBMS user services utilizing the download delivery method.

  • [AMD_PRO-MED] In-session Unicast Repair for MBMS Object Distribution TS 26.346CR0677
  • Improved Time Synchronization for MBMS TS 26.346CR0672

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