Network Browser Engine With Local Runtime Sandboxing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional network computing, particularly thin client-server models, face challenges with remote computing servers being expensive, latency-prone, and requiring constant internet connectivity, and in-browser solutions lack full application programming interfaces (APIs) for advanced programming tasks, limiting functionality in network-constrained environments.

Innovation Solution

A web browser engine is enhanced to locally execute runtime software like Node.js, Python, Ruby, and PHP, utilizing local runtime environment containers and secure sandboxing to perform complex operations, enabling local execution of network-style software without relying on remote servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If remote computing servers are used for thin client computing, then complex operations can be executed in the cloud, but latency and dependency on constant internet connectivity increase

Engineering Contradiction:
Improvecomplex operation execution capabilityVSAvoidlatency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments computing operations into two categories: complex operations that require server execution and simple display/interaction operations that can be handled locally. The browser is divided into a rendering process that runs locally and a worker process that can execute code remotely or locally, allowing the system to optimize each segment independently based on network conditions and operation type.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-loading and caching code and data in the browser's local storage and memory before they are needed for execution. This includes pre-compiling JavaScript code to WebAssembly, pre-loading dependencies, and maintaining local copies of frequently accessed resources, thereby reducing latency when operations need to be executed.

Inventive Principle:
Principle #10Preliminary action

2Power

If remote computing servers are used, then computationally intensive operations can be performed, but cost and infrastructure requirements increase

Engineering Contradiction:
Improvecomputational powerVSAvoidinfrastructure complexity
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The system creates a universal computing platform that can function in multiple modes: fully remote execution, hybrid execution, and fully local execution. The same browser infrastructure can serve as a thin client, a standalone computing environment, or an offline-capable application host, eliminating the need for separate infrastructure for different computing scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The browser is designed to be self-sufficient by implementing its own runtime environment, code compiler, and execution engine. It can download and execute code locally without requiring continuous server interaction, manage its own memory and resources, and provide a complete development and execution environment within the browser itself, reducing dependency on external server infrastructure.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If in-browser solutions are used for code execution, then local execution capability is provided, but full API support for advanced programming tasks is lacking

Engineering Contradiction:
Improvelocal execution capabilityVSAvoidAPI functionality
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system introduces an intermediary layer consisting of a custom runtime environment and API bridge that translates between the browser's constrained environment and the full-featured programming APIs needed for advanced tasks. This intermediary provides virtual file systems, network interfaces, process management, and other operating system-level functionalities that would otherwise be unavailable in a browser, enabling full-stack development capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If code is executed remotely on servers, then security sandboxing is maintained, but network dependency and latency increase

Engineering Contradiction:
Improvesecurity sandboxingVSAvoidnetwork dependency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements a nested security model where a secure sandbox environment is embedded within the browser process, which itself runs within the operating system. The worker process executes code in an isolated context with controlled access to browser resources, while the browser maintains overall security policies. This nested structure allows local execution with the same security guarantees as remote execution, as each nesting level enforces its own security boundaries.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12457261B2Network browser engine
Publication Date: 2025.10.28 STACKBLITZ INC
  • US12457261B2 patent drawing
  • US12457261B2 patent drawing
  • US12457261B2 patent drawing

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.