Real-Time Antivirus for Large Cloud File Uploads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing antivirus software systems face limitations in real-time scanning of large file uploads in cloud computing infrastructure due to time restrictions and cost constraints, particularly in cloud infrastructure services.

Innovation Solution

A computing system that facilitates real-time antivirus scanning by generating a presigned URL for large files, transmitting them to a third party for scanning, and storing clean file identifiers in both cloud and on-premises storage containers, with a private subnet connected to a virtual private cloud for secure access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional antivirus scanning methods are used for large file uploads in cloud infrastructure, then scanning completeness can be maintained, but time restrictions and cost constraints prevent real-time scanning

Engineering Contradiction:
Improvescanning completenessVSAvoidscanning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the scanning operation from the main file upload process by using webhooks to notify a third-party scanning service. The file identifier is separated from the file data itself, allowing the scanner to access only the identifier rather than the entire large file, thus reducing scanning time while maintaining reliability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

A webhook mechanism acts as an intermediary between the cloud storage container and the third-party scanning service. This mediator enables automatic notification and coordination without requiring direct, time-consuming interaction between the upload process and scanning process, resolving the time restriction issue

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If large files are scanned directly in cloud infrastructure, then virus detection capability is maintained, but cost constraints are exceeded

Engineering Contradiction:
Improvevirus detection capabilityVSAvoidscanning cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Instead of scanning the original large file directly in the cloud infrastructure, the system creates and transmits a copy of the file identifier to a third-party scanning service. This copying approach allows virus detection capability to be maintained while significantly reducing the computational cost and energy consumption associated with scanning large files

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent uses disposable, low-cost file identifiers instead of expensive large file data for the scanning operation. The file identifier is a lightweight, inexpensive object that can be easily transmitted and processed by third-party services without incurring high cloud infrastructure costs

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Productivity

If presigned URLs are generated for large files, then real-time scanning becomes feasible, but system complexity increases

Engineering Contradiction:
Improvescanning speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The presigned URL mechanism serves multiple functions: it provides secure access to large files, enables real-time scanning by third-party services, and maintains compatibility with existing cloud storage infrastructure. This multi-functionality reduces the need for separate specialized components, thereby managing system complexity while improving productivity

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

Data Source

PatentUS12464013B2Real-time antivirus
Publication Date: 2025.11.04 TRUIST BANK
  • US12464013B2 patent drawing
  • US12464013B2 patent drawing
  • US12464013B2 patent drawing

AI summary

Systems and methods include a cloud object storage container that receives an object file exceeding a predetermined size. A channel, communicatively connected to the cloud object storage container, is configured to automatically read data from the object file to facilitate generating a presigned URL. The generated presigned URL is attached to the object file, thereby creating a file identifier. The file identifier is stored in the cloud object storage container, which is automatically transmitted to a third party for scanning the file identifier for viruses or malware. A confirmation of a clean file scan is received from the third party, and the confirmed clean file identifier is stored in a clean cloud storage container. The clean cloud storage container is communicatively connected to an on-premises file storage container to facilitate storage of the clean file identifier. The on-premises file storage container stores the clean file identifier to facilitate future access.