Checksum-Based Version Verification for Local CAD Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the AEC industry, users face challenges in maintaining version control of CAD designs without central storage, leading to multiple conflicting local versions and concerns about storing proprietary data online.

Innovation Solution

A method that generates and stores a checksum of the latest design version, allowing users to verify if a printed/static copy is up-to-date by referencing the checksum, which can be checked against the online server using a cell phone or website, ensuring the local version is current.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If designs are stored locally without central storage, then user control and security are improved, but version control and identification of the latest version deteriorate

Engineering Contradiction:
Improveuser control and securityVSAvoidversion control information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts the essential version identification information (checksum) from the complete design file and stores only this small data element locally and online. This allows users to maintain full design files locally for security and control while still having the ability to verify version status by comparing the extracted checksum against the online server, thus resolving the contradiction between local storage security and version control capability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism (checksum verification system) that mediates between local design storage and central version control. The checksum acts as a mediator that can be independently verified against the online server without requiring users to store or access the complete design files online, enabling version control while maintaining local storage autonomy

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If multiple local versions are maintained, then user autonomy is improved, but conflicts and confusion between versions worsen

Engineering Contradiction:
Improveuser autonomyVSAvoidversion consistency
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where users can query the online server with their local checksum to receive immediate feedback on whether their version is current. This feedback loop allows users to maintain autonomy in their local file management while having a reliable method to detect version conflicts and ensure they are working with the latest version, thus preventing version confusion

Inventive Principle:
Principle #23Feedback

3Loss of information

If designs are stored online centrally, then version control is improved, but user security concerns and data protection worsen

Engineering Contradiction:
Improveversion controlVSAvoidsecurity risks
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only the essential checksum data from the complete design files and stores this minimal information online. The full design files remain stored locally with users, eliminating the security risk of storing proprietary data online while maintaining the ability to perform version control through checksum comparison against the online server

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10127267B2Hard copy status check
Publication Date: 2018.11.13 AUTODESK INC
  • US10127267B2 patent drawing
  • US10127267B2 patent drawing
  • US10127267B2 patent drawing

AI summary

A method, apparatus, and system provide the ability to determine a validity of a file. A static image of a first version of the file is output. The outputting includes determining first identifying information that identifies the first version of the file, generating a first reference identifier that is associated with the first identifying information, storing the first reference identifier, and generating the static image that includes a visual representation of the first reference identifier. A second reference identifier (that is associated with second identifying information that identifies a second version of the file) is received. Based on the second identifying information, a determination is made regarding which version of the file is more recent. A validity or invalidity of the second version of the file is confirmed based on the determination.