Time and Date Table

Description

The Time and Date Table (TDT) is a crucial synchronization element within the 3GPP Multimedia Broadcast/Multicast Service (MBMS) architecture, specified in TS 26.917. It is a specific type of table or message that carries absolute time and date information, explicitly mapping the MBMS common timeline—a continuous, network-wide counter—to Coordinated Universal Time (UTC). The MBMS common timeline itself is conveyed via the MCT (Common Timeline) table, which provides a relative count of ticks. The TDT provides the essential anchor point by stating, at a specific moment, what the corresponding UTC date and time is.

Architecturally, the TDT is generated and inserted into the MBMS transport stream by the Broadcast Multicast Service Centre (BM-SC). It is then distributed across the MBMS bearer network to all evolved NodeBs (eNBs) in the broadcast area. The TDT works in conjunction with the System Frame Number (SFN) synchronization mechanism in the radio access network. By receiving the TDT, UE devices can perform two key functions: first, they can synchronize their internal clocks to UTC with high accuracy; second, and more importantly, they can calculate the precise UTC time for any future event scheduled on the MBMS common timeline. This allows UEs to wake up from idle or sleep states at exactly the right moment to receive scheduled content, conserving battery life.

Its role is foundational for time-based service delivery in MBMS and evolved MBMS (eMBMS). Services like File Delivery over Unidirectional Transport (FLUTE) for downloading files, electronic service guides (ESG), and scheduled broadcast sessions rely on the TDT for synchronization. For example, a service announcement may tell a UE that a valuable software update will be broadcast at common timeline tick value X. Without the TDT, the UE only knows a relative tick. With the TDT, the UE can convert tick X into an absolute UTC date and time, schedule its receiver accordingly, and ensure it is active to capture the transmission. This enables efficient, network-controlled, battery-friendly mass content distribution.

Purpose & Motivation

The TDT was created to solve the synchronization challenge in asynchronous broadcast/multicast networks. In a point-to-point cellular network, timing can be managed through direct signaling with each UE. In a broadcast scenario, where a single transmission targets potentially millions of devices, a efficient, common method for aligning all receivers to a universal schedule was needed. Previous approaches lacked a standardized way to correlate the network's internal delivery schedule with real-world time.

Its introduction, particularly with eMBMS enhancements, was motivated by the need to support scheduled content delivery services like mobile TV, large file distribution (e.g., for automotive software updates), and public warning systems. These services require devices to know precisely *when* to listen, not just *what* to listen for. The TDT addresses the limitation of having only a relative timeline (MCT) by providing the absolute time anchor. This enables power-saving features (discontinuous reception aligned with content schedules) and reliable service activation, which are critical for consumer broadcast services and mission-critical IoT applications alike. It provides the temporal foundation that makes scheduled MBMS services practical and efficient.

Key Features

• Provides absolute UTC time and date correlation for the MBMS common timeline
• Essential for synchronizing UE receivers to scheduled broadcast/multicast sessions
• Enables power-saving through precise wake-up scheduling for content reception
• Generated and distributed by the BM-SC across the MBMS network
• Works in conjunction with the MCT (Common Timeline) table
• Fundamental for FLUTE file delivery and electronic service guide (ESG) operation

Evolution Across Releases

Defining Specifications