Browser Extension Auto-Update via Segmented File Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing browser extension update systems are inefficient, often requiring browser restarts and relying on user-initiated updates, leading to multiple versions being installed across different browsers.

Innovation Solution

A method and system for automatically updating browser extensions by communicating with a remote server to determine and install updates, allowing seamless integration of new versions without user intervention, even while the old version is still executed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If client-side periodic update software is used to update browser extensions, then updates can be automatically initiated, but the browser must be restarted or the computer system restarted for updates to take effect

Engineering Contradiction:
Improveautomatic update initiationVSAvoidbrowser restart requirement
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The browser extension is segmented into multiple independent files (HTML, CSS, JavaScript files) stored in a local extension database. This segmentation allows individual files to be updated and replaced without requiring the entire extension to be reinstalled or the browser to be restarted. The extension execution module can load updated files dynamically while the browser remains running.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If users are prompted to update browser extensions, then users can choose to update, but users often decline updates or disable periodic update software

Engineering Contradiction:
Improveuser choice in updatesVSAvoidextension version consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements self-service update mechanisms where the browser extension automatically checks for updates, downloads updated files, and replaces old files without requiring user intervention. The extension execution module automatically loads the updated files, ensuring all browsers have the latest version while maintaining the ability to customize based on user behavior and settings.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple browser extension versions are installed across different browsers, then user preferences can be maintained, but system complexity increases and compatibility issues arise

Engineering Contradiction:
Improveuser preference maintenanceVSAvoidmultiple version management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system creates a universal update mechanism that operates across all browsers consistently. The extension execution module in each browser automatically communicates with the remote server, checks for updates, and applies them using the same process. This universal approach ensures version consistency across different browsers while maintaining compatibility through standardized update procedures and file formats.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8667480B1Automatically updating browser extensions, and applications thereof
Publication Date: 2014.03.04 GOOGLE LLC
  • US8667480B1 patent drawing
  • US8667480B1 patent drawing
  • US8667480B1 patent drawing

AI summary

Embodiments of invention relate to automatically updating browser extensions. In an embodiment, a method for updating browser extensions is provided. In the method, an input to execute a browser extension installed in a local browser extension database is received. In response to receipt of the input, a remote server is automatically communicated with to determine whether a portion of the browser extension should be updated. An updated portion of the browser extension is received if the browser extension should be updated. Finally, the updated portion of the browser extension is installed in the local browser extension database.