Browser Framework Priority Event Preemption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Browser-based devices with markup language user interfaces struggle to prioritize events, leading to issues like missed incoming calls during page downloads, as they cannot interrupt ongoing tasks, and require full-function OSs to manage separate threads for telephony and browsing functions.
Innovation Solution
A browser-enabled device with a browser-based user interface and control architecture that includes a browser core, framework, and OS kernel, which uses priority attributes to manage event registrations, allowing higher-priority events to halt and resume the loading of URI content in a single-threaded environment, reducing the need for a full-function OS.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a browser-based interface and control architecture is used with markup language, then the user interface can be written faster and more flexibly, but the system cannot prioritize events and interrupt ongoing tasks
Solution Approach 1:
The patent introduces a priority parameter associated with each event registration. When an event is registered, it includes a priority value that determines its importance. The browser framework examines this priority field and compares it with currently executing events, allowing high-priority events (like incoming calls) to preempt low-priority events (like page downloads) without changing the underlying single-threaded markup language architecture.
2Productivity
If separate threads are used for telephony and browsing functions, then event prioritization is possible, but a full-function OS is required with increased resource usage
Solution Approach 1:
The patent segments the event handling process into distinct phases: event registration with priority assignment, event queue management, and selective execution based on priority comparison. This segmentation allows the single-threaded browser framework to simulate multi-threaded behavior by systematically managing event priorities and preemptions without requiring actual multiple threads or a full-function OS.
Solution Approach 2:
The browser framework acts as an intermediary layer between the markup language user interface and the browser core. It introduces priority-based event registration and management mechanisms that mediate between incoming events and the single-threaded execution environment, enabling prioritization without requiring complex OS support or multiple threads.
3Device complexity
If a single thread is used for simplified programming model, then device complexity is reduced, but the system cannot interrupt ongoing tasks for higher priority events
Solution Approach 1:
The patent introduces dynamic priority-based preemption into the single-threaded execution model. The browser framework continuously monitors registered events and dynamically adjusts execution based on priority comparisons. When a high-priority event is registered while a low-priority event is executing, the system dynamically switches to the high-priority event, maintaining simplicity while enabling responsive critical event handling.
Data Source
AI summary
A browser-enabled device includes a browser-based user interface and control architecture, which has a browser core, a browser framework, and a user interface. The user interface is written using a markup language. In processing event registrations, the browser framework receives an event registration. The received event registration having a response unique resource identifier (URI) content and a priority field. The priority field of the received event registration is examined to determine priority of the received event registration. If the browser core is loading the response URI content of a prior event registration and if the priority of the received event registration is higher than the priority of the prior event registration, then the loading of the response URI content of the prior event registration is halted, and loading of the response URI content of the received event registration is begun.