Binary File Deep Comparison for Precise Patch File Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional technologies fail to accurately identify changed files within compiled binary files, resulting in large and difficult-to-install patch installation packages due to inclusion of unchanged files, lack of flexible comparison tools, and inability to analyze various file types and permissions.

Innovation Solution

A deep file compare system generates human-readable files from binary files, classifies them into types, and applies schema rules to determine and output only the subset of changed files, considering file permissions and symbolic links.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional file comparison technologies are used to identify changed files, then the process is simple, but the precision of identifying changed files is low resulting in inclusion of unchanged files in patch packages

Engineering Contradiction:
Improveprecision of identifying changed filesVSAvoidcomplexity of file comparison system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the file comparison process into multiple stages: initial filtering using hash algorithms, detailed comparison of changed files using deep file comparison technology, and hierarchical organization of comparison rules. This segmentation enables high-precision identification of changed files while managing system complexity through modular processing steps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of file representation by converting binary files into human-readable formats (such as assembly language or structured data representations) before comparison. This parameter transformation enables precise detection of changes in binary files while maintaining manageable complexity through standardized conversion processes.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If all files are included in patch installation packages to ensure completeness, then the reliability of patch installation is improved, but the volume of patch packages increases making installation difficult

Engineering Contradiction:
Improvereliability of patch installationVSAvoidvolume of patch installation package
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary changed files from the complete file set by implementing a multi-stage comparison process. It identifies and extracts specifically modified files, their dependencies, and required resources, excluding all unchanged files. This extraction approach ensures patch package reliability by including all necessary files while minimizing volume by excluding unnecessary ones.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary file comparison and classification before patch package generation. By pre-identifying changed files, analyzing their dependencies, and organizing required files in advance, the system ensures that the final patch package contains exactly what is needed for reliable installation without unnecessary bloat.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If deep comparison of binary files is implemented to accurately identify changes, then the precision of change detection is improved, but the time required for file comparison increases

Engineering Contradiction:
Improveprecision of change detectionVSAvoidtime required for file comparison
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent segments the comparison process into fast initial filtering using hash algorithms followed by detailed deep comparison only for files that show potential changes. This hierarchical segmentation achieves high precision in change detection while minimizing time loss by avoiding deep comparison of obviously unchanged files.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial deep comparison by performing full deep analysis only on files that pass the initial filtering stage, rather than applying exhaustive deep comparison to all files. This partial action approach maintains high precision for detecting actual changes while reducing overall comparison time by limiting intensive processing to relevant files only.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250272084A1File deep compare tool realization
Publication Date: 2025.08.28 DELL PROD LP
  • US20250272084A1 patent drawing
  • US20250272084A1 patent drawing
  • US20250272084A1 patent drawing

AI summary

Methods, system, and non-transitory processor-readable storage medium for a file deep compare system are provided herein. An example method includes a patch installation package generator system that receives a plurality of files and a request to generate a patch installation package incorporating a subset of changed files for installation, where the plurality of files comprises the subset of changed files and a subset of unchanged files. A deep file compare system generates human readable files from binary files, wherein the plurality of files comprises the binary files. The deep file compare system determines the subset of changed files within the plurality of files, using the human readable files, and outputs the subset of changed files for generation of the patch installation package incorporating the subset of changed files.