Browser Plug-in Power Management via Visibility Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Increased processor utilization and power consumption due to plug-ins on web pages, especially when not in focus or related to non-central elements like advertisements, lead to excessive battery usage in mobile devices, with existing browsers lacking means to recognize and reduce such power usage effectively.
Innovation Solution
A browser application that identifies and applies power-saving procedures by replacing processing-intensive plug-in activities with static images and suspending or reducing non-media plug-in execution on non-visible web page content, coordinating with the operating system for further power reduction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If plug-ins are executed to display video and provide additional functionality on web pages, then content presentation capability is improved, but processor utilization and power consumption increase
Solution Approach 1:
The browser dynamically adjusts plug-in execution based on tab visibility state. When a tab becomes inactive or hidden, the browser suspends plug-in execution in that tab, reducing power consumption while maintaining functionality in active tabs. This dynamic switching resolves the contradiction by adapting resource usage to actual user needs.
Solution Approach 2:
The browser applies different execution policies to different tabs based on their visibility state. Active tabs receive full plug-in execution resources while inactive tabs have plug-ins suspended. This localized quality differentiation allows the system to maintain high content presentation capability where needed while reducing power consumption in areas where it is not required.
2Reliability
If plug-ins continue to execute when web page is not in focus or minimized, then content functionality is maintained, but battery power consumption increases
Solution Approach 1:
The browser implements periodic monitoring of tab visibility states and adjusts plug-in execution accordingly. When a tab switches from active to inactive state, the browser suspends plug-in execution. When the tab becomes active again, execution is resumed. This periodic adjustment maintains functionality during active periods while extending battery life during inactive periods.
Solution Approach 2:
The browser performs preliminary suspension of plug-in execution when detecting that a tab is becoming inactive or hidden, before the user would notice any functionality loss. This preliminary action prevents unnecessary power consumption while ensuring functionality is restored immediately when the tab becomes active again, thus extending battery life without compromising user experience.
3Duration of action of moving object
If processing is reduced for non-visible web page content, then battery life is extended, but content update responsiveness may be delayed
Solution Approach 1:
The browser dynamically adjusts the processing level for non-visible content based on its visibility state. For completely hidden tabs, processing is suspended to maximize battery life. For tabs that are visible but not active, processing is reduced but not completely stopped, maintaining basic responsiveness. This dynamic adjustment resolves the contradiction by matching processing intensity to actual user needs.
Solution Approach 2:
Different processing levels are applied to different tabs based on their specific visibility state. Active tabs receive full processing priority for immediate responsiveness. Inactive but visible tabs receive reduced processing. Completely hidden tabs have processing suspended. This localized quality differentiation extends battery life while maintaining responsiveness where it matters most.
Data Source
AI summary
The embodiments disclosed herein describe ways that a browser application or other process can reduce power usage by a computing device. Methods include the process suspending one or more plug-ins on a web page by replacing them with a snapshot taken from the plug-in, and reducing processing on non-media plug-ins and non-visible portions of web pages running in the browser, but not currently in focus, such as when a tab is in the background behind a different tab, when a browser window is minimized, or when the web page is entirely or partially occluded.