Flexible Namespace Prioritization in Virtualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtualization environments face challenges in managing access to overlapping sets of system resources with conflicting names, requiring a flexible method to prioritize namespaces and resolve conflicts transparently to applications.

Innovation Solution

A virtualization layer with a policy engine dynamically prioritizes resource namespaces by applying policies to determine the appropriate namespace for resource access, allowing flexible and context-dependent prioritization of namespaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a virtualization environment manages access to multiple overlapping sets of system resources with conflicting names, then resource access management becomes complex and conflicts arise between namespaces, but applications require transparent and predictable resource access without modification

Engineering Contradiction:
Improvenamespace prioritization flexibilityVSAvoidresource access management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic namespace prioritization where the priority order of namespaces is not fixed but can change based on policies. The system evaluates multiple namespaces and dynamically determines which namespace should take precedence for each resource access request, allowing flexible adaptation to different scenarios while managing complexity through structured policy evaluation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of namespace priority dynamically rather than using a static hierarchy. By applying policies that can modify the effective priority of namespaces based on resource type, application context, and other factors, the system achieves adaptability without requiring complex manual configuration or application modification.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a fixed priority order is used for namespaces, then resource access is predictable, but the system lacks flexibility to adapt to different resource types and access scenarios

Engineering Contradiction:
Improveresource access predictabilityVSAvoidnamespace prioritization flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the priority parameter dynamically based on policies rather than using a fixed order. Policies can specify different priority rules for different resource types, applications, or contexts, maintaining predictability through consistent policy application while achieving adaptability through policy variability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system transitions from static namespace priority to dynamic priority determination. The evaluation process dynamically assesses which namespace should take precedence for each request based on applicable policies, ensuring predictable outcomes through systematic evaluation while adapting to diverse scenarios through policy flexibility.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If the virtualization layer modifies its behavior to prioritize namespaces flexibly, then resource conflicts are resolved better, but applications would need to be aware of and adapted to the virtualization layer's internal mechanisms

Engineering Contradiction:
Improveconflict resolution capabilityVSAvoidapplication transparency
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a policy evaluation mechanism as an intermediary between the application and the actual resource access. This intermediary transparently manages namespace priority conflicts by evaluating policies and determining the appropriate namespace without requiring applications to understand or interact with the complex namespace management mechanisms directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The virtualization layer autonomously resolves namespace conflicts by applying policies without requiring application intervention. The system self-manages the complexity of multiple overlapping namespaces by automatically evaluating which namespace should take precedence and handling the resource access accordingly, keeping applications simple and unaware of the underlying complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8862590B2Flexible namespace prioritization
Publication Date: 2014.10.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8862590B2 patent drawing
  • US8862590B2 patent drawing
  • US8862590B2 patent drawing

AI summary

Access to resources on a computer may be provided by using a first namespace of resources and a second namespace of resources, where one or more names are common to both namespaces and those names refer to different respective instances of resources. A request is received for a first resource name from an application, where the first resource name exists in the first resource namespace and in the second resource namespace. In response to the request, whether to obtain a resource from the first namespace or from the second namespace is determined by applying one or more resource policies to the first resource namespace and to the second resource namespace.