Decoupling Container Image Layers for Privacy and Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Container image management is inefficient due to the need for frequent updates of multiple layers, and existing methods for preserving privacy, such as encrypting entire images, are insecure and cumbersome, especially when dealing with sensitive data.

Innovation Solution

Decoupling container image layers into individual layers with unique URLs and credentials for secure access, allowing for layer-by-layer updates and privacy preservation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If container image layers are kept together as a complete image, then privacy is harder to preserve, but update efficiency is reduced

Engineering Contradiction:
Improveprivacy preservationVSAvoidupdate efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides a container image into multiple independent layers, each with its own URL and access credentials. This segmentation allows selective access to specific layers (improving privacy) while enabling independent updates of individual layers without updating the entire image (improving update efficiency). The layers are stored separately but can be assembled into a complete container image when needed.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire container images are encrypted to preserve privacy, then security is improved, but computational overhead increases

Engineering Contradiction:
ImprovesecurityVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the security mechanism from traditional full-image encryption and applies it selectively to individual layers. Instead of encrypting the entire container image, the system encrypts only specific layers that contain sensitive data, and manages encryption keys on a per-layer basis. This reduces computational overhead while maintaining security for sensitive information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different security measures to different layers based on their sensitivity. Not all layers require the same level of encryption and access control. This local quality approach optimizes computational resources by applying strong encryption only where necessary while using lighter security mechanisms for non-sensitive layers.

Inventive Principle:
Principle #3Local quality

3Loss of information

If multiple container layers are updated frequently, then data freshness is improved, but management complexity increases

Engineering Contradiction:
Improvedata freshnessVSAvoidmanagement complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent creates a universal management system that handles multiple layers through a common interface and methodology. The same mechanisms for URL generation, credential management, and access control are applied uniformly across all layers, regardless of their specific content or sensitivity level. This multi-functionality simplifies management despite the increased number of layers.

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

Data Source

PatentUS11314880B2Decoupling container image layers to preserve privacy
Publication Date: 2022.04.26 RED HAT INC
  • US11314880B2 patent drawing
  • US11314880B2 patent drawing
  • US11314880B2 patent drawing

AI summary

An example system includes a memory, one or more processors in communication with the memory, and a container image generator. The container image generator receives a first set of information. The container image generator receives a second set of information, including secure information that requires validation to be accessed. The container image generator generates a first container layer, including a first URL associated with the first set of information. The container image generator generates a second container layer, including a second URL associated with the second set of information. The container image generator stores the first container layer and the second container layer at a storage location.