Browser Cache Mirroring for Handheld Devices

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Handheld electronic devices face processing overhead and resource consumption due to versatile original software providing unnecessary notifications, and limitations in API functions for third-party software operations.

Innovation Solution

Implementing a method to mirror the browser cache on a server, allowing only necessary notifications to be processed and reducing communication bandwidth by storing frequently used objects locally, and using algorithms to filter and ignore irrelevant notifications based on predetermined criteria.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the original software provides a versatile API with many notifications for third-party software, then the adaptability and versatility are improved, but the processing overhead and resource consumption increase

Engineering Contradiction:

ImproveAPI versatilityVSAvoidprocessing overhead

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and mirrors only the necessary browser cache data to the server, separating essential information from unnecessary notifications. This allows third-party software to receive only relevant updates without processing overhead from redundant notifications, while maintaining API versatility through selective data extraction.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements local quality by storing frequently accessed objects locally in the browser cache on the handheld device, while mirroring only specific cache changes to the server. This ensures that third-party software receives notifications with appropriate detail level - full local access for common operations, selective remote synchronization for relevant changes.

Inventive Principle:

Principle #3Local quality

2Reliability

If the original software provides comprehensive notifications through API, then the reliability of data provided to third-party software is improved, but the quantity of unnecessary notifications increases causing resource consumption

Engineering Contradiction:

Improvedata completenessVSAvoidnotification quantity

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies partial action by implementing selective mirroring of browser cache data - only specific cache entries and changes are transmitted to the server based on predetermined criteria. This provides third-party software with sufficient reliable data for operation without the excessive quantity of unnecessary notifications, achieving optimal balance between data completeness and notification volume.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent creates a mirror copy of selected browser cache data on the server rather than transmitting all notifications. This copying approach ensures data reliability for third-party software by maintaining an accurate replica of relevant cache state, while significantly reducing notification quantity by only mirroring necessary changes.

Inventive Principle:

Principle #26Copying

3Speed

If the device stores frequently used objects in browser cache locally, then the speed of data access is improved, but the communication bandwidth consumption increases when synchronizing with server

Engineering Contradiction:

Improvedata access speedVSAvoidcommunication bandwidth

Core Design Contradiction:

SpeedVSLoss of energy

Solution Approach 1:

The patent segments the browser cache synchronization process by dividing cache data into distinct categories and applying different mirroring strategies to each segment. Frequently accessed objects remain purely local for fast access, while only specific cache changes are segmented for transmission to the server, optimizing the balance between data access speed and communication bandwidth consumption.

Inventive Principle:

Principle #1Segmentation

4Ease of operation

If the API provides all possible functions for third-party software, then the ease of operation is improved, but the device complexity increases

Engineering Contradiction:

Improvesoftware operation easeVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary between the browser cache and third-party software. This intermediary handles the complexity of cache management, filtering, and mirroring operations, while presenting a simplified interface to third-party software through selective notifications. The server mediates between the complex local cache system and the needs of third-party applications, reducing perceived device complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS7644149B2Method of reflecting on another device an addition to a browser cache on a handheld electronic device, and associated device

Publication Date: 2010.01.05 MALIKIE INNOVATIONS LTD

AI summary

An improved handheld electronic device includes an Application Programming Interface (API) that generates various notifications in certain circumstances. The handheld electronic device provides an improved method of employing the notifications to enable another device to reflect an addition to a browser cache on the handheld electronic device.