Browser Plugin Disabling via Virtual Capability Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing techniques for controlling browser plugins are cumbersome and inefficient, leading to malware risks, battery drain, and unnecessary user intervention, as they often require manual activation or deactivation and do not effectively manage plugin usage.

Innovation Solution

Implementing a method on electronic devices to automatically determine if a plugin meets disabling criteria, reporting to data sources that the plugin is not installed even when it is, allowing media to be served in more secure and efficient formats like HTML5, thereby reducing malware risks and conserving battery life.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a plugin is kept installed to play media from specific webpages, then media playback capability is maintained, but the device becomes vulnerable to malware attacks and experiences reduced performance

Engineering Contradiction:
Improvemedia playback capabilityVSAvoidmalware vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the plugin functionality by creating a virtual representation of the plugin's capability information without actually installing the plugin binary. This allows the browser to report support for specific media formats to websites while preventing the malicious plugin code from executing on the device.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism that mediates between the browser and websites regarding plugin capability reporting. The system acts as a intermediary layer that provides capability information to websites while blocking the actual plugin installation and execution, thus preventing malware exposure while maintaining playback capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If a plugin is manually disabled through user interface, then malware risk is reduced, but user time and device energy are wasted due to multiple key presses and navigation

Engineering Contradiction:
Improvemalware riskVSAvoiduser time and device energy
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The system implements self-service by automatically determining whether to block plugin installation based on predefined criteria without requiring user intervention. The browser autonomously evaluates the plugin against disabling criteria and makes the decision to block or allow installation, saving user time and device energy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by pre-establishing disabling criteria for plugins before they are encountered. The system prepares the blocking logic in advance based on factors such as security risks, performance impact, and user preferences, so that when a plugin is encountered, the decision is already made and executed immediately without requiring user navigation or input.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If a plugin is disabled, then security and efficiency are improved, but websites may not serve media in alternative formats

Engineering Contradiction:
Improvesecurity and efficiencyVSAvoidmedia format compatibility
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic capability reporting where the browser can adaptively report plugin support based on the specific context. When a website requests media playback, the browser dynamically determines whether to report plugin support based on the disabling criteria and the specific media format requested, allowing flexibility in maintaining compatibility while enforcing security.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of plugin capability reporting by allowing the browser to selectively report support for specific media formats while blocking the actual plugin. The system can report support for HTML5 video formats while blocking Flash plugins, effectively changing which parameters (media formats) are reported as supported without installing the problematic plugin.

Inventive Principle:
Principle #35Parameter changes

4Ease of operation

If existing manual techniques are used to control plugins, then user control is maintained, but the process is cumbersome and inefficient

Engineering Contradiction:
Improveuser controlVSAvoidoperational efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system implements feedback by continuously monitoring plugin installation attempts and automatically applying the pre-established disabling criteria. The browser provides feedback to websites about plugin support status based on this automated evaluation, eliminating the need for users to manually navigate through interface options while maintaining effective control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10037216B2Intelligent disabling of browser plugins
Publication Date: 2018.07.31 APPLE INC
  • US10037216B2 patent drawing
  • US10037216B2 patent drawing
  • US10037216B2 patent drawing

AI summary

Systems and methods for disabling one or more plugins associated with a browser application are provided. In one exemplary method, a plugin is installed on an electronic device, and the device receives data from a data source, where that data is associated with the installed plugin. Whether the installed plugin meets a disabling criteria is determined. In accordance with a determination that that the installed plugin meets a disabling criteria: performance of a function with the installed plugin is foregone; and it is reported to the data source that the installed plugin is not installed on the electronic device. In accordance with a determination that the installed plugin does not meet the disabling criteria, the function is performed with the installed plugin.