Hierarchical Workspace Orchestration for Context-Based Secure Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional virtualization techniques for securing access to protected data in Information Handling Systems (IHS) are inefficient and burdensome, consuming large portions of memory and processing capabilities while failing to account for the context of use, leading to degraded productivity and user experience.

Innovation Solution

The system employs hierarchical workspace orchestration, where workspaces are instantiated and managed based on the security and risk context, allowing for flexible access control and resource utilization across various devices, including peripheral devices, using a workspace orchestration service to dynamically adjust access levels and computing architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional virtualization techniques are used to secure access to protected data, then data security is improved, but memory and processing resource consumption increases significantly

Engineering Contradiction:
Improvedata securityVSAvoidmemory and processing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system segments the virtualization environment into hierarchical workspaces with different security levels and resource allocations. Instead of providing full virtualization isolation to all users, the system creates segmented workspace instances that provide appropriate security and resource access based on user role and context, reducing overall resource consumption while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different virtualization security characteristics to different workspaces based on local quality principles. High-security workspaces receive full isolation and protection, while lower-security workspaces receive reduced isolation and fewer resources. This allows the system to maintain data security where needed while reducing memory and processing consumption in less critical areas.

Inventive Principle:
Principle #3Local quality

2Reliability

If conventional virtualization techniques implement all security protocols for all approved data and applications, then data protection is improved, but system complexity and overhead increases

Engineering Contradiction:
Improvedata protectionVSAvoidsystem complexity and overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system dynamically adjusts security protocols and virtualization characteristics based on the specific workspace, user context, and data sensitivity. Instead of implementing all security protocols universally, the system dynamically selects and applies only the necessary security measures for each workspace instance, reducing system complexity and overhead while maintaining adequate data protection.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes security parameters such as isolation levels, access control strictness, and resource allocation based on workspace hierarchy and user roles. By parameterizing security characteristics rather than implementing fixed comprehensive protocols, the system reduces complexity while maintaining appropriate data protection for different contexts.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If conventional virtualization techniques provide support for many capabilities, then versatility is improved, but unnecessary capabilities burden the operation and degrade productivity

Engineering Contradiction:
Improvecapability supportVSAvoidproductivity and user experience
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements partial virtualization capabilities rather than full comprehensive support for all possible capabilities. By providing only the necessary capabilities for each workspace based on user role and task requirements, the system avoids the burden of unnecessary features while maintaining adequate versatility for intended purposes, thereby improving productivity.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system applies different capability sets to different workspaces based on local quality principles. Each workspace receives only the capabilities and features appropriate to its security level and intended use, rather than providing full capability support universally. This reduces the operational burden of unnecessary capabilities while maintaining sufficient versatility for each workspace's specific purposes.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12632575B2Hierarchical workspace orchestration
Publication Date: 2026.05.19 DELL PROD LP
  • US12632575B2 patent drawing
  • US12632575B2 patent drawing
  • US12632575B2 patent drawing

AI summary

Systems and methods for hierarchical workspace orchestration are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include a processor and a memory, the memory having program instructions stored thereon that, upon execution, cause the IHS to: receive first one or more files from a workspace orchestration service, where the first one or more files are usable by the IHS to instantiate a first workspace; and provide second one or more files from the first workspace to a first peripheral device, where the second one or more other files are usable by the first peripheral device to instantiate a second workspace, where the second workspace is configured to provide third one or more files to a second peripheral device coupled to the first peripheral device, and where the third one or more files are usable by the second peripheral device to instantiate a third workspace.