Browser Engine Relay for Cross-Origin Local Server Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional server-based network computing is expensive, incurs latency, and requires a network connection, limiting functionality in remote or network-constrained environments, and lacks full application programming interfaces (APIs) for advanced programming tasks.
Innovation Solution
A web browser engine is enhanced to locally execute runtime software like Node.js, Python, Ruby, and PHP within secure containers, enabling local execution of complex operations without relying on remote servers, using local operating system APIs and secure containers to isolate and manage resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network browsing functionality is integrated into the mobile phone's web browser, then users can access internet services directly on mobile devices, but the mobile phone's processing resources are consumed and battery power is depleted
Solution Approach 1:
The patent introduces a WAP gateway as an intermediary between the mobile terminal and the internet. The gateway performs protocol conversion, transforming WAP format requests from mobile devices into standard HTTP requests that can be processed by web servers. This allows mobile phones to access internet services without requiring powerful local processing capabilities, thereby reducing battery consumption while maintaining browsing functionality.
Solution Approach 2:
The patent replaces the need for complex local processing mechanisms in mobile devices with server-side processing. Instead of requiring mobile phones to execute complex web rendering and protocol handling locally (mechanical processing), the system substitutes this with automated server-side processing and protocol conversion at the WAP gateway, reducing the computational burden on mobile devices.
2Adaptability or versatility
If network browsing is supported on mobile phones, then users gain internet access capability, but the system complexity of the mobile phone increases
Solution Approach 1:
The WAP gateway acts as an intermediary that handles protocol conversion and processing complexity. Mobile phones only need to implement simple WAP protocol clients, while the complex HTTP protocol handling, web rendering, and protocol translation are performed at the gateway server, thereby reducing the system complexity required in mobile devices.
Solution Approach 2:
The patent segments the network browsing system into distinct components: a simplified WAP client in the mobile phone, a protocol conversion function at the WAP gateway, and standard web servers handling HTTP requests. This segmentation allows mobile phones to have minimal browsing functionality while complex processing is distributed to external systems.
3Adaptability or versatility
If protocol conversion is implemented at the WAP gateway, then compatibility between WAP and HTTP systems is improved, but the gateway processing load increases
Solution Approach 1:
The WAP gateway is designed with multi-functionality, handling both WAP protocol conversion and HTTP protocol processing within a single system. By consolidating these functions, the gateway can optimize resource allocation and reuse processing components across different protocol handlers, reducing overall processing load compared to having separate dedicated systems for each protocol.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An improved computing system is arranged for cross-origin network communications on a single computing device. The system includes a processor, a networking module, and memory with software instructions arranged to operate a local computing server resource on a first local domain, instantiate a relay mechanism that has an iFrame and an invisible window, instantiate a local web server on a second local domain, install a service worker on the invisible window, receive a request for information at the local web server, verify a presence of the local computing server resource on the first local domain, communicatively connect the second local domain to the iFrame, and directly communicate, via the at least one networking module, at least one message between the local computing server resource on the first local domain and the local web server on the second local domain using the relay mechanism.