Set Top Box MHP Application Version Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing set top box control methods do not effectively inform users of available updates, leading to unnecessary loading of new application versions and requiring a secondary 'launcher' application for update management.
Innovation Solution
A method where the version number of MHP applications is transmitted in the AIT table, allowing users to compare primary and secondary version changes, enabling optional updates and permitting the use of older versions if not necessary, with a 'launchable with older version' flag allowing startup of stored applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the version number is transmitted in the AIT table and users are informed of updates, then users can make informed update decisions, but the system complexity increases due to version comparison logic
Solution Approach 1:
The version number is segmented into primary version (bits 1-10) and secondary version (bits 11-31), allowing the system to distinguish between major updates requiring user attention and minor updates that can be applied automatically. This segmentation resolves the contradiction by providing transparent update information while keeping the comparison logic manageable through hierarchical version evaluation.
Solution Approach 2:
The version number is pre-transmitted in the AIT table alongside application metadata, enabling the set-top box to perform version comparison before user interaction is required. This preliminary action allows the system to prepare update information in advance, reducing the complexity of real-time decision-making while maintaining full information transparency.
2Reliability
If a secondary launcher application is implemented to manage updates, then update control is improved, but the device complexity and number of required applications increase
Solution Approach 1:
The update management functionality is merged into the existing MHP application lifecycle by utilizing the AIT table and integrated version comparison mechanisms. Instead of adding a separate launcher application, the update control is combined with the application's existing metadata and startup procedures, maintaining reliability while avoiding additional application complexity.
Solution Approach 2:
The AIT table is enhanced to serve multiple functions: it continues to provide application metadata and startup information while also conveying version number data for update management. This multi-functionality eliminates the need for a dedicated launcher application, as the existing infrastructure is extended to handle update control universally across all MHP applications.
3Reliability
If the older application version is restricted after update transmission, then update compliance is improved, but user flexibility and access to functional applications decrease
Solution Approach 1:
The system dynamically determines whether to restrict older versions based on the version comparison result. If the primary version number matches, the older version remains accessible, providing user flexibility. If the primary version differs, indicating a significant update, then restrictions are applied to ensure compliance. This dynamic approach balances update reliability with user access flexibility based on the actual update significance.
Solution Approach 2:
The restriction policy changes based on the version number parameters. By evaluating the primary and secondary version fields, the system adjusts its behavior: allowing older versions when only minor secondary version changes occur, and restricting them when primary version changes indicate substantial updates. This parameter-based policy maintains both compliance and flexibility without requiring absolute restrictions.
Data Source
AI summary
The aim of the invention is to indicate the availability of an update for an MHP application, which is modified only periodically, to the user of a set top box, while helping him or her to decide whether the modified update is actually required and optionally still maintaining the availability of the older update without restrictions. To achieve this, information concerning the scope and/or type of modification in relation to the older version is provided in the transmitted version number for the modified MHP application. The set top box starts the saved older version if special information exists (“launchable with older version” flag) and permits a comparison of the version number with the received version number of the modified MHP application as to whether the modifications of the modified MHP application are of such significance that the modified version must be received and saved in the cache memory. If an update of the cache memory is required, the user of the set top box receives an indication to switch to the narrow-band transponder channel and to receive the modified MHP application.