Container Validation via Local Client Routines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for validating computer application containers lack efficiency and security, particularly in ensuring that containers are properly generated and validated without exposing private client information, and do not effectively streamline the validation process across multiple validation entities.

Innovation Solution

A method and system for validating containers that generate and validate executable packages including source code and runtime information, utilizing a plurality of container validation routines specified by different entities, while ensuring that private client information remains secure by performing validation on a client computer system without transmitting it to a server system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If container validation is performed by transmitting container information to a server system, then centralized validation control is improved, but security deteriorates due to exposure of private client information

Engineering Contradiction:
Improvecentralized validation controlVSAvoidexposure of private client information
Core Design Contradiction:
Extent of automationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a validation routine that acts as an intermediary between the container and validation entities. This routine executes validation logic locally on the client system, allowing centralized validation procedures to be implemented while keeping private container information isolated within the client environment. The validation routine serves as a mediator that processes validation requests without exposing sensitive data to external server systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the validation execution environment from the server system and places it at the client system. By taking out the actual validation execution from the centralized server and performing it locally through validation routines, the system achieves centralized control over validation procedures while extracting sensitive information handling from the server environment, thereby improving security.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If multiple validation entities perform validation routines, then validation thoroughness is improved, but validation time deteriorates due to extensive communication latency

Engineering Contradiction:
Improvevalidation thoroughnessVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges multiple validation routines into a single integrated validation procedure that executes sequentially or in parallel on the client system. By combining the validation logic of multiple validation entities into unified routines that run locally, the system maintains thorough multi-entity validation while eliminating the communication latency that would occur with distributed validation across networked systems.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary local validation through validation routines before any potential server communication. By executing validation checks locally in advance, the system reduces the amount of data that needs to be transmitted and validated centrally, thereby reducing overall validation time while maintaining thoroughness through the multi-entity validation routine structure.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10884896B2Validation of containers
Publication Date: 2021.01.05 CA TECH INC
  • US10884896B2 patent drawing
  • US10884896B2 patent drawing
  • US10884896B2 patent drawing

AI summary

Techniques are disclosed relating to generating and validating a container for an application. A container for an application may an executable package that include the source code for the application along with the runtime information, system tools, system libraries, and settings for the application. A container validation procedure is determined for the container using a plurality of container validation routines. The container validation routines may reflect the role various validation entities have in validating the container and approving it for deployment. If the container successfully passes the container validation procedure, the container may be deployed on a computer system.