Virtualization Process for Native Virtual Namespace Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The integration of native applications with virtualized environments is challenging due to the inability of components within native applications to access resources available through virtual namespaces, leading to failed interactions and limited functionality.

Innovation Solution

A virtualization process that monitors calls initiated by components within native applications to identify integrated calls requiring access to virtual namespaces, providing access to these resources through the virtual namespace, thereby enabling seamless interaction between native and virtual environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If components within native applications are restricted to access only resources through the native namespace, then the stability and isolation of the native application environment is maintained, but the functionality and integration capability with virtualized environments is limited

Engineering Contradiction:

Improveintegration capabilityVSAvoidnamespace access complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A virtualization process is introduced as an intermediary component that sits between the native namespace and virtual namespace. This process monitors calls from native applications, identifies integrated calls requiring virtual namespace access, and provides the necessary access permissions dynamically. The intermediary resolves the contradiction by enabling integration capability without requiring components to directly manage complex namespace access rules.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The namespace access model transitions from a static restriction to a dynamic permission system. The virtualization process dynamically evaluates each call to determine whether virtual namespace access is needed, granting permissions on-demand rather than through fixed configuration. This dynamic approach enables adaptability while maintaining system stability through automated decision-making.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If proxies are registered in place of components to provide virtual namespace access, then access to virtual resources is enabled, but the system complexity and overhead increase significantly

Engineering Contradiction:

Improvevirtual namespace accessVSAvoidproxy registration overhead

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The proxy functionality is extracted from the component level and consolidated into a centralized virtualization process. Instead of registering proxies for each individual component, the system extracts the namespace access management function to a single process that handles all integrated calls. This reduces the proliferation of proxies and simplifies the overall system architecture.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The virtualization process serves multiple functions: it monitors calls, identifies integrated calls, manages virtual namespace access permissions, and coordinates between native and virtual environments. By consolidating these diverse functions into a single universal process, the system avoids the complexity of multiple specialized proxies while maintaining comprehensive virtual namespace access capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If components within native applications are allowed to access resources through virtual namespaces without monitoring, then integration functionality is improved, but system stability and security are compromised

Engineering Contradiction:

Improveintegration functionalityVSAvoidsystem stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The virtualization process implements a feedback mechanism by monitoring calls initiated by native application components. The system observes call patterns, identifies integrated calls requiring virtual namespace access, and responds by providing appropriate permissions. This feedback loop ensures that access is granted based on actual needs rather than blanket permissions, maintaining system stability while enabling integration functionality.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary analysis of calls to determine whether they require virtual namespace access before granting permissions. By pre-evaluating each call and identifying integrated calls in advance, the system can prepare appropriate access permissions without compromising stability. This preliminary action prevents unauthorized or inappropriate access while enabling necessary integration functionality.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10423471B2Virtualizing integrated calls to provide access to resources in a virtual namespace

Publication Date: 2019.09.24 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Disclosed herein are systems, methods, and software for facilitating the integration of native applications and virtualized applications. Calls initiated from within a native application associated with a native namespace are monitored for integrated calls. The integrated calls involve resources accessible through a virtual namespace. Upon detecting an integrated call, the integrated call is provided with access to a corresponding resource by way of the virtual namespace.