HbbTV keeps growing because it sits at the intersection of broadcast reach and web-style interaction. The AIT, or Application Information Table, is the broadcast signal that advertises a hybrid application and tells a receiver how to find it. That makes AIT the control plane for HbbTV discovery.
The idea is simple: the DVB stream announces the service, timing, and network context, then AIT adds the application layer on top. Receivers use that metadata to decide whether to show a launch icon, auto-start an app, or fetch resources from a carousel or HTTP endpoint.
Why the market is still growing
HbbTV keeps expanding because broadcasters want interactive features without losing broadcast reliability. Viewer habits have shifted toward richer menus, catch-up access, recommendations, and second-screen style journeys, while operators still need the efficiency of one-to-many delivery. HbbTV answers both needs.
A simple mental model
Broadcast service
└─ PSI/SI tables
└─ AIT advertises HbbTV app
├─ carousel / broadcast app
└─ HTTP / web appThis is the most useful way to think about it. The AIT does not replace the broadcast service model; it extends it. Once the receiver sees the AIT entry, it can discover the app and decide how to launch it. The actual application payload may sit in the multiplex or live online, but the advertisement path starts in broadcast.
What operators care about most
The first concern is service binding. The application must be tied to the right service, otherwise users may see the wrong experience when changing channels. The second concern is descriptor quality. Identifiers, language values, visibility flags, and control codes need to be consistent so different receiver brands make the same decision. Launch behaviour matters too: some applications should appear as a visible button, some should launch automatically, and some should stay hidden until triggered.
Carousel or broadband?
HbbTV can point to a broadcast carousel, an HTTP endpoint, or a hybrid approach. Carousel delivery is resilient and self-contained, which helps when broadband is weak or unavailable. HTTP delivery is easier to update and can support richer experiences, but it depends on connectivity and device support.
Many deployments use both. AIT becomes the anchor that tells the receiver where the application lives and how it should be treated. That flexibility is one reason the market keeps moving: broadcasters can pick the delivery model that fits the region, service, and audience.
Why it matters now
HbbTV is not just a feature for large broadcasters. It is becoming a baseline expectation in many markets because it lets services offer interactive navigation, local information, and branded experiences over a broadcast backbone. In an era where viewers expect television to behave a bit more like software, that matters.
Quick takeaway
HbbTV keeps growing because it gives broadcasters a standard way to add interactivity without abandoning broadcast economics. AIT makes discovery possible, binds the app to the service, and tells receivers what to do next. For a visual reference, see AIT/HbbTV in PSI Generator.
AIT/HbbTV in PSI Generator
If you want a visual reference for the configuration concepts in this article, open AIT/HbbTV in PSI Generator.