Application Information Table

Description

The Application Information Table (AIT) is a fundamental component within the 3GPP Multimedia Broadcast/Multicast Service (MBMS) and evolved MBMS (eMBMS) ecosystem, specified in detail in TS 26.953. It functions as a signaling table, analogous to the Program Map Table (PMT) in traditional MPEG-2 Transport Streams, but specifically designed for application signaling within IP-based broadcast delivery frameworks like FLUTE/ALC. The AIT is transported as a file within the File Delivery over Unidirectional Transport (FLUTE) session, allowing it to be reliably delivered to all receivers in the broadcast coverage area.

Architecturally, the AIT resides within the application layer of the broadcast protocol stack. It is generated by the service provider or broadcast application server and is multiplexed into the broadcast transport stream alongside audio, video, and other data carousels. The table itself is structured using XML or binary formats as defined by the specification, containing a list of application descriptors. Each descriptor provides comprehensive metadata for a single application, including a globally unique application identifier, version information, priority, visibility controls, and, most critically, the transport parameters required to retrieve the application itself. These parameters specify the FLUTE session (via Source IP, Destination IP, and Transport Session Identifier - TSI) and the file (via Transport Object Identifier - TOI) where the application's executable code or resources are located.

When a receiver (User Equipment - UE) tunes into a broadcast service, it first acquires the service announcement information, which points to the FLUTE session carrying the AIT. Upon receiving and parsing the AIT, the UE's middleware or application manager can identify all applications associated with the current service. The UE then evaluates the application descriptors based on its capabilities, user preferences, and security policies. If an application is deemed suitable and authorized, the UE uses the transport parameters in the AIT to join the corresponding FLUTE session and download the application's files. The AIT also controls the application lifecycle, specifying whether an application should be launched automatically, pre-fetched for later use, or merely listed as available. This mechanism enables a seamless, declarative model for application delivery, decoupling the service discovery process from the application retrieval and execution logic.

The role of the AIT is pivotal in enabling value-added services on top of pure audio/video broadcast. It transforms a passive broadcast channel into an interactive service platform. For example, in an eMBMS-based mobile TV service, the AIT can signal an associated voting application, a companion information portal, or a targeted advertisement engine. In Public Warning System (PWS) implementations, the AIT can signal the delivery of a rich-media emergency alert application containing maps, evacuation routes, or multi-language instructions. The standardized format ensures interoperability between broadcast network equipment from different vendors and receivers from different manufacturers, which is essential for the widespread deployment of interactive broadcast services.

Purpose & Motivation

The Application Information Table was created to solve the fundamental problem of how to dynamically associate and deliver executable applications with linear broadcast content in a standardized, efficient, and receiver-agnostic manner. Prior to its standardization, proprietary methods or limited signaling mechanisms (like simple triggers) were used, which led to fragmentation, increased receiver complexity, and hindered the development of a rich ecosystem for broadcast applications. The AIT provides a unified, declarative framework that tells the receiver exactly what applications are available, how to get them, and what to do with them.

Historically, the push for AIT emerged with the evolution of 3GPP's MBMS towards richer media experiences and the integration of broadcast with IP networks (leading to eMBMS). As broadcast services evolved beyond simple audio and video streams to include interactive elements, companion content, and personalized components, there was a clear need for a robust signaling protocol. The AIT addresses the limitations of previous ad-hoc approaches by offering a structured, network-efficient solution. It allows the network to signal application information once to a massive audience, leveraging the broadcast nature of the delivery, rather than requiring each device to individually query an application server (which would overload cellular unicast networks).

Furthermore, the AIT enables service and application lifecycle management from the network side. Service providers can update, add, or remove applications associated with a live broadcast service simply by updating the AIT file in the broadcast carousel. This gives broadcasters dynamic control over the user experience. The creation of the AIT was also motivated by the need for security and trust; the table can include information about application origin and signatures, allowing the receiver to verify authenticity before execution. Ultimately, the AIT exists to unlock the commercial and functional potential of broadcast networks by making them a platform for deployable, interactive software, bridging the gap between traditional linear broadcasting and the on-demand, app-centric world of modern digital services.

Key Features

• Standardized XML/binary format for application signaling defined in 3GPP TS 26.953
• Declarative application descriptor model including ID, version, priority, and visibility controls
• Integrated transport signaling using FLUTE/ALC session parameters (Source IP, Dest IP, TSI, TOI)
• Supports application lifecycle management (auto-start, pre-fetch, kill commands)
• Enables network-controlled association of applications with linear broadcast services
• Facilitates secure application delivery through signature and origin information inclusion

Evolution Across Releases

Defining Specifications