HTML5 EPG Data Manager Module for Memory Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current HTML5-based electronic programming guide (EPG) applications face performance issues due to memory and processor intensity when handling large datasets, with existing approaches either limiting customization or causing slow navigation and high memory usage.

Innovation Solution

An EPG data manager module is introduced to interface with the HTML5 EPG application, using scriptable data objects and an intermediary event handler to efficiently manage and render EPG data, offloading data management and navigation from the presentation layer, allowing for optimal performance and customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If EPG data is managed entirely in HTML/JS implementation, then customization flexibility is improved, but memory usage and processing time increase significantly

Engineering Contradiction:
Improvecustomization flexibilityVSAvoidmemory usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system divides EPG data into fixed-time interval segments (e.g., 30-minute blocks) and only loads the segments required for the current display window into memory. This segmentation allows the HTML5 application to maintain customization flexibility while significantly reducing memory consumption by loading only necessary data portions rather than the entire EPG dataset.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary module or service layer is introduced between the HTML5 presentation layer and the underlying EPG data source. This intermediary handles data retrieval, segmentation, and formatting, allowing the HTML5 application to remain lightweight and customizable without bearing the full burden of data management, thus reducing memory and processing requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If EPG data is managed entirely in HTML/JS implementation, then customization flexibility is improved, but navigation speed deteriorates

Engineering Contradiction:
Improvecustomization flexibilityVSAvoidnavigation speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

EPG data is segmented into fixed-time intervals that map directly to display window requirements. When navigation occurs, the system quickly identifies and loads only the relevant segmented data for the new time range, avoiding the need to process entire datasets. This segmentation strategy maintains fast navigation speed while supporting HTML5 customization flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary organization of EPG data into time-based segments during data ingestion or caching phases. This preliminary segmentation enables rapid retrieval and navigation during user interaction, as the data is pre-structured for efficient access patterns matching typical EPG navigation behaviors, thus maintaining speed while allowing HTML5 customization.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If a native visual plug-in is used to manage EPG data, then processing performance is improved, but customization capability is limited

Engineering Contradiction:
Improveprocessing performanceVSAvoidcustomization capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

An intermediary service layer is positioned between the native plug-in (which handles high-performance data processing) and the HTML5 presentation layer (which provides customization). The intermediary translates and formats data for HTML5 consumption while allowing the native plug-in to maintain optimal processing performance, thus resolving the contradiction between performance and customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments EPG data processing into two parts: heavy lifting (data retrieval, decomposition, initial formatting) performed by the native visual plug-in for optimal performance, and presentation-specific rendering handled by customizable HTML5 code. This segmentation allows both high processing performance and full customization capability to coexist.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If all EPG data is loaded into memory for HTML5 processing, then data access flexibility is improved, but device resource consumption increases

Engineering Contradiction:
Improvedata access flexibilityVSAvoiddevice resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

EPG data is divided into time-based segments corresponding to display window intervals. Only the segments required for the current viewing window are loaded into memory, providing sufficient data access flexibility for navigation while minimizing memory allocation and associated device resource consumption. This segmentation enables flexible data access within the loaded segments without requiring entire datasets in memory.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements local quality optimization by loading high-detail EPG data only for the currently visible time range and using lower-detail or summary data for adjacent time periods. This approach maintains data access flexibility for the displayed content while reducing overall memory usage and device resource consumption by applying different data quality levels to different temporal regions.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9386341B2Optimized HTML5 electronic programming guide application
Publication Date: 2016.07.05 ESPIAL GROUP
  • US9386341B2 patent drawing
  • US9386341B2 patent drawing
  • US9386341B2 patent drawing

AI summary

An electronic programming guide (EPG) data manager module is provided. The EPG data module provides an event driven infrastructure to provide EPG data to a hypertext markup language 5 (HTML5) applications. The HTML5 EPG application presents an EPG data window in a user interface on a display device. The EPG data is provided to the EPG application in scriptable data objects generated to be rendered by the HTML5 EPG application based upon the EPG data window to be presented.