Transactional OS with Isolated Virtual Process Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Operating Systems face challenges with error reduction, security, and compatibility issues due to their complex nature, requiring frequent updates and struggling to function across various platforms while maintaining development costs down.

Innovation Solution

A network service with a servicing component that analyzes process representations before initialization, providing error reduction and heightened security by monitoring processes, employing a transactional Operating System with rollback mechanisms, and ensuring continuous execution regardless of client connectivity status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional Operating Systems use traditional single-threaded or basic multithreaded approaches, then device complexity and resource management are simplified, but error reduction and security are compromised

Engineering Contradiction:
Improveerror reductionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the operating system into a base OS layer and a virtualized service layer, where processes are divided into isolated virtual instances. Each virtual process runs in its own container with independent memory and system resources, allowing error containment and security isolation without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a virtualization layer as an intermediary between the physical hardware and the running processes. This virtualization layer includes virtual processors, memory managers, and system resource allocators that mediate between process requests and physical resources, enabling error isolation and security without direct hardware access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If conventional Operating Systems implement frequent updates and patches to address security and compatibility issues, then reliability improves, but device complexity and maintenance requirements increase

Engineering Contradiction:
ImprovesecurityVSAvoidupdate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates virtual copies of processes and system states within isolated containers. Each virtual process is a copy that can be independently managed, snapshotted, and restored. This allows security patches to be applied to virtual instances without affecting the host system, and enables rollback to previous versions if issues arise.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements beforehand cushioning by creating isolated virtual environments before running untrusted or potentially problematic processes. These virtual containers act as a cushion that contains potential security breaches or errors, preventing them from affecting the host system or other processes.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Productivity

If conventional Operating Systems manage multiple processes sequentially, then system complexity is reduced, but productivity and responsiveness decrease

Engineering Contradiction:
Improveconcurrent execution capabilityVSAvoidprocess management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments process management into independent virtual processes, each with its own execution context, memory space, and system calls. This allows true parallel execution of multiple processes simultaneously while maintaining simple individual process management through the virtualization layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial action by providing process isolation and virtualization only where needed, while maintaining simple process management for standard operations. The virtualization infrastructure is activated selectively based on process requirements, balancing complexity and functionality.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If conventional Operating Systems provide comprehensive process analysis and monitoring, then error detection and security improve, but device complexity and processing overhead increase

Engineering Contradiction:
Improveprocess monitoring capabilityVSAvoidmonitoring system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service monitoring where each virtual process automatically reports its own state, errors, and security events to the virtualization layer. The monitoring function is integrated into the process execution model itself rather than requiring separate complex monitoring systems.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent establishes feedback mechanisms where the virtualization layer continuously receives information from virtual processes about their execution state, resource usage, and errors. This feedback enables automatic error detection, security monitoring, and resource management without requiring complex manual monitoring systems.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7647522B2Operating system with corrective action service and isolation
Publication Date: 2010.01.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7647522B2 patent drawing
  • US7647522B2 patent drawing
  • US7647522B2 patent drawing

AI summary

The claimed subject matter provides a system and/or a method that facilitates re-locating a web application associated with a network service utilizing a portion of serialized data. The network service can be any collection of resources that are maintained by a party (e.g., third-party, off-site, etc.) and accessible by an identified user over a network (e.g., WAN, Internet, etc.). A receiver component can receive a request for initiating and execution of a process that is maintained by the network service. A servicing component can analyze representations of multiple processes within the network service and determines whether to enable initiation and execution of the process based at least in part upon the analysis.