Background Process Manager for Persistent Rich Internet Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Web Browsers cannot support Rich Internet Applications (RIAs) to run in the background independently of the main Web Browser process, limiting their functionality and user experience, as they cannot notify users of events or maintain continuous operation after the browser is closed.
Innovation Solution
An Application Execution Server with a Background Process Manager creates and manages Background Processes that can interact with RIAs on Internet Enabled User Devices, enabling persistent communication and notification even when the Web Browser is closed, through a Persistent Rich Internet Application Manager and Client Network Function.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If RIAs are loaded from Web Server every time they are started, then development costs are cut and deployment is simplified, but the applications cannot run in the background independently once the Web Browser is closed
Solution Approach 1:
The patent segments the RIA system into two independent parts: a lightweight client-side component (RIA client) that can run locally in the background, and a server-side component (RIA server) that handles heavy processing. This segmentation allows the application to maintain background execution capability while keeping the client lightweight for easy deployment.
Solution Approach 2:
The patent introduces an RIA client as an intermediary layer between the Web Browser and the RIA server. This client acts as a persistent runtime environment that can execute RIA code independently of the browser, enabling background execution while the browser is closed. The client maintains communication with the server through persistent connections.
2Ease of operation
If a RIA is opened in the Web Browser, then the application can be accessed and updated, but it cannot notify users of events or maintain continuous operation after the browser is closed
Solution Approach 1:
The patent implements preliminary action by establishing persistent background connections and pre-configuring notification mechanisms before the browser is closed. The RIA client maintains active connections to the server and sets up event subscription in advance, ensuring that notifications can be delivered and processed even when the browser is not running.
Solution Approach 2:
The patent ensures continuity of useful action by implementing a persistent RIA client that runs independently in the background. This client maintains continuous communication channels with the server, allowing the application to receive updates, process events, and notify users without requiring the browser to remain open.
3Use of energy by moving object
If the Web Browser is closed to save resources, then battery life is extended, but the RIA cannot provide continuous updates or notifications
Solution Approach 1:
The patent employs a lightweight RIA client that consumes minimal system resources compared to a full browser instance. This client is designed to run efficiently in the background with low battery consumption, providing essential notification functionality without the overhead of a complete browser environment.
Solution Approach 2:
The RIA client implements self-service by autonomously managing its own execution, maintaining persistent connections to the server, and handling notification delivery without requiring user intervention or browser presence. The client independently monitors for events and delivers notifications, ensuring continuous operation with minimal resource usage.
Data Source
AI summary
An Application Execution Server and a method for managing a Background Process which is associated with a Rich Internet Application which is accessible via a Web Browser of an Internet Enabled User Device. The Application Execution Server comprises a Background Process Manager which is adapted to create a Background Process, in response to receiving a request for such a process from the Rich Internet Application, the Background Process being adapted to recognize a triggered event associated with said associated rich Internet application and to invoke the Rich Internet Application, irrespective of whether the Web Browser and/or the Rich Internet Application is presently running or not.


