MHP

MHP
Name	MHP
Developer	DVB Project; contributors from European Broadcasting Union, EICTA, BBC, ETSI
Released	2000
Latest release	1.1 (2010)
Written in	Java (programming language), HTML
Operating system	Linux, Windows CE, Real-time operating system
Platform	Digital Video Broadcasting platforms, set-top boxes, digital televisions
License	Royalty-free specifications; implementations under varied proprietary and open-source licenses

MHP is a suite of specifications for interactive digital television middleware designed to enable applications across broadcast, broadband, and return channels on Digital Video Broadcasting systems. It defines a Java-based execution environment, conditional access interfaces, and profiles for set-top boxes and integrated digital televisions, aiming to standardize interactive services among stakeholders such as broadcasters, manufacturers, and service providers. MHP was developed through collaboration among European standards bodies and industry consortia to harmonize interactive TV services across platforms and markets.

Etymology and Acronym Variants

The name derives from a three-word phrase used in European standards forums and is commonly referenced by its acronym in technical literature and industry reports. Within documents from organizations like ETSI and the DVB Project, several variant labels and profile names appear to clarify deployment scope—terminology adopted in white papers from BBC, Canal+, and RTE. Academic analyses by researchers at Imperial College London and TU Delft often enumerate profile variants to compare middleware approaches across deployments in countries such as United Kingdom, France, and Germany.

History and Development

Specification work began in multinational working groups convened after milestones such as the establishment of the DVB Project and early trials by broadcasters including ZDF and RAI. Influence from trials led by BBC interactive initiatives and experimental projects with Canal+ shaped early drafts. Formalization occurred through collaboration between ETSI technical committees and the European Broadcasting Union, with input from chipset vendors like STMicroelectronics and Broadcom. Subsequent revisions incorporated lessons from deployments in markets pioneered by Telefónica and TF1, while academic evaluations from University of Cambridge and Universität Erlangen–Nürnberg informed performance and security considerations.

Technical Specifications and Standards

MHP defines a Java-based execution environment derived from Java (programming language) and subsets of DVB-SI, MPEG-2, and MPEG-4 systems for signaling and media handling. It specifies an application environment using profiles—such as interactive broadcast and internet access—aligned with existing standards like ETSI EN 302 799 and integrating conditional access interfaces compatible with systems from Nagravision, Viaccess, and Irdeto. Security models reference public-key infrastructures akin to methods discussed by RSA (cryptosystem) researchers and certificate handling practices used in X.509 deployments. Content signaling interoperates with transport technologies from DVB-S and DVB-T2 ecosystems, while user interface definitions draw on HTML 4.0 subsets and resource management constrained by processor and memory profiles typical of STB silicon from vendors such as Intel and ARM Holdings.

Applications and Use Cases

MHP has been used to deliver interactive program guides, electronic program guides pioneered by broadcasters like RTL Group and Sky Group, audience polling and voting services similar to implementations by Endemol productions, and enhanced teletext-like services analogous to systems from ORF and SVT. It supported interactive advertising pilots run by Clearcast and subscription management features like those implemented by BSkyB and NDS Group integrations. Educational and telemedicine prototypes developed in collaborations with institutions such as Karolinska Institute and École Polytechnique explored video-assisted learning and remote consultation workflows. Trial deployments in municipalities coordinated with telecom carriers such as Deutsche Telekom and Portugal Telecom demonstrated hybrid broadcast-broadband use cases.

Implementation and Compatibility

Commercial middleware stacks and reference implementations were provided by vendors including Convergence and chipset manufacturers like Broadcom and STMicroelectronics, while open-source projects adapted Java television runtimes influenced by OpenJDK implementations. Compatibility matrices evaluated interoperability across set-top boxes from manufacturers like Humax, Samsung Electronics, and Philips (company), and integrated TV platforms from Sony Corporation and LG Electronics. Interworking with conditional access modules and middleware from companies such as Irdeto and Nagravision required conformance testing under test suites maintained by ETSI and interoperability events organized by the DVB Project.

Controversies, Limitations, and Criticism

Critics pointed to performance constraints on low-cost hardware common in deployments by operators like Sky Deutschland and Telefónica and to challenges in achieving vendor-neutral interoperability highlighted in reports by Which? and standards analyses from Fraunhofer Society. The reliance on a Java-based middleware raised concerns about resource overhead compared with native approaches used by companies such as Netflix and Amazon (company) in streaming clients. Regulatory and market observers in jurisdictions involving Ofcom and the European Commission debated the role of standardized middleware versus proprietary platforms for fostering innovation, while security researchers affiliated with CWI (research institute) and KTH Royal Institute of Technology identified potential vulnerabilities in certificate handling and platform isolation models.

Category:Digital_video_broadcasting