Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
The IPTV ecosystem involves a complex chain of content providers, service providers, network operators, and consumer electronics manufacturers. Without standardized terminal profiles, a set-top box purchased in one region might not work with a service provider in another region, or a smart TV might support some features but not others required by a particular IPTV service. IEC 62766-8 solves this by defining three hierarchical profiles: the Open Internet Profile, the Baseline Managed Profile, and the Enhanced Managed Profile.
These profiles are based on the Open IPTV Forum (OIPF) specifications and define the minimum set of features that a terminal (called OITF — Open IPTV Terminal Function) must support for compliance. Critically, each profile is also the maximum set of features that a service can rely on being present — services cannot assume features from higher profiles are available unless the terminal explicitly declares support through capability exchange.
This profile targets basic over-the-top (OTT) services delivered over the public internet. It requires support for: IPTV services including scheduled content (linear TV) and streamed content-on-demand (CoD), residential network connectivity via a WAN gateway (typically a broadband modem), service provider discovery, content metadata for electronic program guides, authentication methods, and content/service protection. The media format requirements are limited to the most common codecs (H.264/AVC, AAC). This profile is suitable for low-cost retail streaming devices.
Building on the Open Internet Profile, this profile adds requirements for managed IPTV networks where the service provider controls the end-to-end quality of service. Additional features include: IMS (IP Multimedia Subsystem) gateway support for session control, enhanced content protection with more rigorous key management, OITF capability declarations for feature negotiation, and remote management protocols (TR-069). This profile is typical for telco IPTV deployments.
The most comprehensive profile adds support for: broadband content guide (BCG) for unified search across managed and unmanaged content, HTTP adaptive streaming (HAS) with multi-bitrate support, a procedural application environment (PAE) for advanced interactive applications, SVG Tiny 1.2 for rich graphics, and comprehensive remote management. This profile targets premium IPTV services with advanced features like network PVR, start-over TV, and multi-screen viewing.
| Feature Category | Open Internet | Baseline Managed | Enhanced Managed |
|---|---|---|---|
| IPTV scheduled content | M | M | M |
| Streamed CoD | M | M | M |
| IMS gateway | O | M | M |
| Application gateway | M | M | M |
| Broadband Content Guide | O | O | M |
| HTTP Adaptive Streaming | O | O | M |
| Declarative Application Env. | M | M | M |
| Procedural Application Env. | O | O | M |
| Remote Management | O | M | M |
M = Mandatory, O = Optional
The standard’s media format profiling table is a critical reference for SoC (system-on-chip) designers. It specifies required video codecs (H.264/AVC at minimum, with H.265/HEVC optional), audio codecs (AAC, AC-3, E-AC-3), and container formats (MP4, MPEG-TS). For each codec, the maximum resolution, frame rate, and bitrate are defined per profile level. This allows chip manufacturers to target specific profile levels with optimized hardware decoding blocks.
The Enhanced Managed Profile’s requirement for HTTP adaptive streaming reflects the industry’s move toward ABR (adaptive bitrate) streaming. The standard specifies support for MPEG-DASH (Dynamic Adaptive Streaming over HTTP) as the primary HAS format, with content metadata that includes bandwidth and resolution information for each representation. For engineers, this means the OITF must implement a robust adaptive bitrate algorithm that can switch between representations seamlessly based on network conditions.
The separation between declarative (DAE) and procedural (PAE) application environments allows different types of applications to coexist. DAE supports HTML5-based applications typical for EPG and portal screens, while PAE supports more demanding applications like games and interactive overlays. The standard specifies which DAE and PAE features are mandatory for each profile, enabling a predictable execution environment.
Yes, and this is the expected implementation approach. A set-top box that supports the Enhanced Managed Profile inherently supports the Baseline and Open Internet profiles by definition of the hierarchical structure. The device declares which profile it supports through capability exchange.
HbbTV (Hybrid Broadcast Broadband TV) is a complementary standard focused on the hybrid broadcast/broadband experience, primarily in Europe. IEC 62766-8 is more focused on pure IPTV delivery over managed and unmanaged networks. Some features overlap, but they serve different deployment scenarios.
The standard does not mandate specific DRM systems but specifies the content protection framework requirements. Common implementations include Microsoft PlayReady, Google Widevine, and Marlin, with key management and license acquisition protocols specified in the content and service protection clauses.
Yes. The protocol profiling section includes requirements for IPv6 support, reflecting the growing adoption of IPv6 in broadband networks. The OITF must support both IPv4 and IPv6 dual-stack operation.