Containerized OS Anonymization for Privacy and Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing container-based virtualization solutions face challenges in allowing users to access resources while maintaining privacy and security, particularly in scenarios where user data needs to be anonymized and isolated from the host operating system.

Innovation Solution

A method is implemented where a containerized operating system is configured to anonymize user information by hiding it from the host operating system, allowing the anonymized containerized operating system to access resources by sending anonymized requests through a broker, which verifies the user's authorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If user data is shared between host computing system and container operating system, then application compatibility is improved, but user privacy and security are worsened

Engineering Contradiction:
Improveapplication compatibilityVSAvoiduser privacy exposure
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments user data into different categories (identifiable data vs. anonymized data) and selectively shares only anonymized data with the container operating system. This allows the container to access sufficient information for application compatibility while preventing exposure of personally identifiable information, thus resolving the contradiction between compatibility and privacy protection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (anonymization service or data mediation mechanism) that sits between the host computing system and the container operating system. This intermediary anonymizes user data before passing it to the container, enabling compatibility functionality while blocking direct access to sensitive personal information, thereby resolving the privacy-exposure issue.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If all user data on host operating system is allowed into container operating system, then data accessibility is improved, but security risk is worsened

Engineering Contradiction:
Improvedata accessibilityVSAvoidsecurity risk
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies different quality levels of data sharing to different data elements. Sensitive data elements are heavily anonymized or restricted, while less sensitive elements are shared more freely. This local differentiation of data sharing policies enables broad data accessibility for container operations while maintaining security by protecting critical sensitive information through targeted anonymization strategies.

Inventive Principle:
Principle #3Local quality

3Object-affected harmful factors

If user information is anonymized in containerized operating system, then user privacy is improved, but ability to access authorized resources is worsened

Engineering Contradiction:
Improveuser privacy protectionVSAvoidresource access capability
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent creates anonymized copies of user data that preserve the functional characteristics needed for resource access while removing personally identifiable information. These anonymized data copies enable the containerized operating system to authenticate and access authorized resources based on anonymized user profiles, thus maintaining resource access capability while protecting user privacy through the copying and anonymization process.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3619639B1Cross container user model
Publication Date: 2025.05.28 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3619639B1 patent drawingFigure 1~2
  • EP3619639B1 patent drawingFigure 3
  • EP3619639B1 patent drawingFigure 4

AI summary

A second operating system accessing resources from an external service. A method includes sending an anonymized request, for an anonymized user corresponding to an authorized user, for resources, through a broker. A request for proof indicating that the anonymized user is authorized to obtain the resources is received from the broker. As a result, a request is send to a first operating system for the proof that the anonymized user is authorized to obtain the resources. Proof is received from the first operating system, based on the anonymized user being associated with the authorized user, that the anonymized user is authorized to obtain the resources. The proof is provided to the broker. As a result, the resources are obtained by the second operating system from the service.