Cloud-Based File Repair System for Malicious Code Removal

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file repair technologies face challenges in achieving complete removal of malicious code, often leaving residual code and causing system failures, especially when files are heavily infected, and crucial system files cannot be restored to a normal state.

Innovation Solution

A method and system that involves scanning files at user terminals for abnormalities, acquiring file characteristics information, and replacing infected files with secure versions from a cloud server, ensuring complete deletion of malicious code and system integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If malicious code is deleted from infected files using conventional repair methods, then some viral behaviors are removed, but complete repair is hard to achieve and residual malicious code remains

Engineering Contradiction:
Improvecomplete repair rateVSAvoidcomplexity of virus variants
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by creating and storing secure backup copies of files before they become infected. When infection is detected, these pre-prepared secure versions are directly restored, eliminating the need for complex analysis and deletion of various virus variants. This resolves the contradiction by preparing repair solutions in advance rather than attempting to remove diverse malicious codes when infection occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates accurate copies of secure file versions and stores them in a cloud-based repository. When a file is infected, the system retrieves the corresponding clean copy from the repository and replaces the infected version. This copying approach achieves complete repair by substituting the infected file with a known-good replica, bypassing the complexity of analyzing and removing different virus variants.

Inventive Principle:
Principle #26Copying

2Ease of operation

If malicious code is deleted from heavily infected files, then some functionality is restored, but many files cannot be executed normally after repair

Engineering Contradiction:
Improvefile executabilityVSAvoidrepair completeness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Instead of attempting to repair heavily infected files by deleting malicious code, the system retrieves exact copies of secure versions from the cloud repository and replaces the infected files. This ensures both complete repair (100% reliability) and normal executability (ease of operation) because the replaced files are guaranteed to be clean and functional.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by maintaining secure backup copies of files in the cloud before infection occurs. When files are heavily infected and cannot be normally executed, these pre-prepared secure copies are directly deployed to restore both functionality and completeness, resolving the contradiction between executability and repair completeness.

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If crucial system files are retained without deletion, then system stability is maintained, but malicious code cannot be completely removed

Engineering Contradiction:
Improvesystem stabilityVSAvoidmalicious code removal
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

For crucial system files that cannot be deleted, the system retrieves accurate copies of secure versions from the cloud repository and replaces the infected versions in place. This approach achieves both complete malicious code removal and system stability because the replacement files are verified clean copies that maintain system integrity while eliminating all viral content.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by maintaining secure backup copies of crucial system files in the cloud. When these files become infected, the pre-prepared secure versions are directly restored, ensuring both complete virus removal and system stability without requiring file deletion or complex repair operations.

Inventive Principle:
Principle #10Preliminary action

4Loss of time

If conventional file repair methods are used, then processing time is reduced, but complete deletion of malicious code cannot be ensured

Engineering Contradiction:
Improvefile repair timeVSAvoidmalicious code deletion completeness
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system retrieves pre-prepared secure copies from the cloud repository and directly replaces infected files, achieving both rapid processing (minimal time loss) and complete malicious code deletion. This copying method is faster than conventional repair because it eliminates the time-consuming analysis and incremental deletion of virus variants, while ensuring 100% removal completeness through verified clean copies.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by maintaining secure backup copies in the cloud before infection occurs. When infection is detected, these pre-prepared versions are directly deployed, achieving both speed (minimal time loss) and completeness (full virus removal) simultaneously, resolving the contradiction between repair time and deletion completeness.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9652632B2Method and system for repairing file at user terminal
Publication Date: 2017.05.16 BEIJING QIHOOD TECHNOLOGY CO LTD
  • US9652632B2 patent drawing
  • US9652632B2 patent drawing
  • US9652632B2 patent drawing

AI summary

Provided are a method and system for repairing a file at user terminal. The method comprises: scanning a file at user terminal, determining whether the file is abnormal, and acquiring file characteristics information; if the file is abnormal, then according to the file characteristics information, acquiring from a cloud server a secure file corresponding to the abnormal file and uploaded before abnormity occurring, wherein the secure file in the cloud server is acquired by directly uploading file of user terminal; and replacing the corresponding abnormal file of the user terminal with the secure file. The method and system save the secure files of each user terminal in a cloud server, and when an abnormal file occurs in the user terminal, download the secure version of a corresponding file from the cloud server to replace the local abnormal file, thus ensuring recovery of the correct version of the file into the system, and solving the problems that the abnormal file cannot be restored to normal status during the conventional file repair process or cannot be repaired due to complexities caused by virus infection.