Remote Resource Launch via Container Broker

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing systems lack a secure and integrated method to access and launch remote resources, as they often allow direct access to the file system, which can lead to security vulnerabilities and limitations in resource management.

Innovation Solution

A remote resource application is associated with an application container that restricts direct access to the file system, using a broker component to manage access and a decision component to determine whether remote resources are launched from within or outside the container, ensuring secure and integrated access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the remote resource application allows direct access to the file system, then the application can easily access and launch remote resources, but security vulnerabilities increase and resource management becomes limited

Engineering Contradiction:
Improveaccess to remote resourcesVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a broker component as an intermediary between the remote resource application and the file system. The broker receives launch requests from the application, resolves the appropriate launch mechanism, and mediates the actual launch process. This intermediary layer prevents direct file system access while maintaining the ability to launch remote resources securely through controlled channels.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the remote resource application operates within the application container, then security is enhanced by restricting direct file system access, but the complexity of managing launch mechanisms increases

Engineering Contradiction:
ImprovesecurityVSAvoidlaunch mechanism management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The broker component is designed with multi-functionality to handle various launch scenarios uniformly. It can resolve different launch mechanisms (internal launch within container, external launch to host, or redirection to alternative containers) through a single unified interface. This universal approach simplifies the application code while managing the complexity of multiple launch mechanisms centrally.

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

3Reliability

If the application container restricts direct access to the file system, then security is improved, but the flexibility to access various remote resources is reduced

Engineering Contradiction:
ImprovesecurityVSAvoidaccess to remote resources
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The broker component implements dynamic resolution of launch mechanisms based on the specific resource being accessed. It evaluates the resource type, location, and launch requirements to determine the appropriate launch strategy at runtime. This dynamic approach allows the containerized application to adaptively access various remote resources while maintaining security constraints, rather than requiring static pre-configured access paths.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8935402B2Resource launch from application within application container
Publication Date: 2015.01.13 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8935402B2 patent drawing
  • US8935402B2 patent drawing
  • US8935402B2 patent drawing

AI summary

A remote resource application that is associated with an application container in a manner that the application container restricts the remote resource application from directly accessing at least a file system of the computing system. The remote resource application provides a visualization for each of multiple remote resources. The user may launch the remote resource by selecting the corresponding visualization. Some of the remote resources are accessed by launching from the remote resource application itself in the context of the application container. Others of the remote resources are launched outside of the application container. The remote desktop application may operate securely within the application container, and still serve as an integrated location from which a user can access remote resources, regardless of whether the remote resource is launched from internal or external to the application container.