Upload Interface Identification via Request Packet Content Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for identifying upload interfaces are incomplete, leading to a high detection missing probability and reduced comprehensiveness, as they rely solely on detecting the 'input type="file' label, which misses other forms of upload interfaces.

Innovation Solution

An upload interface identification method that analyzes request packets for specific content features indicative of upload requests, such as those used in HTTP protocols, to accurately determine the presence and address of upload interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the upload interface is identified by detecting the 'input type="file"' label in the page, then the identification method is simple, but the detection missing probability increases and comprehensiveness decreases

Engineering Contradiction:
Improveidentification method complexityVSAvoidupload interface detection accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

Instead of detecting upload interfaces by looking for specific HTML labels in the page structure, the patent inverts the approach by analyzing request packets sent from the client to the server. It identifies upload interfaces by detecting characteristic content features in the request packets (such as file upload protocols, boundary markers, and upload-specific headers), thereby discovering upload interfaces that may not have standard HTML labels.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces request packet analysis as an intermediary method between the client and server to identify upload interfaces. By examining the communication content (request packets) that passes through the system, the method can detect upload interfaces without directly parsing the page structure, thus overcoming the limitations of label-based detection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If the upload interface identification relies solely on 'input type="file"' label detection, then the implementation is straightforward, but the comprehensiveness of identification is reduced

Engineering Contradiction:
Improveimplementation easeVSAvoidupload interface form coverage
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal identification method that works across multiple upload interface forms. By analyzing request packet content features rather than relying on specific HTML labels, the method can identify various types of upload interfaces including those with 'input type="file"', those without labels, those using JavaScript-based uploads, and other alternative upload mechanisms, thereby achieving multi-functionality and broad coverage.

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

Solution Approach 2:

The patent changes the detection parameter from HTML structure elements (labels) to communication protocol elements (request packet content features). This parameter change allows the identification method to adapt to different upload interface implementations, as request packets reveal the actual upload behavior regardless of how the interface is presented in the HTML.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10972496B2Upload interface identification method, identification server and system, and storage medium
Publication Date: 2021.04.06 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US10972496B2 patent drawing
  • US10972496B2 patent drawing
  • US10972496B2 patent drawing

AI summary

Embodiments of this application provide an upload interface identification method performed at an identification server. The identification server obtains a to-be-identified request packet that is contained in request packets from a page client to a page server. After parsing a content feature of the to-be-identified request packet, the server determines whether the content feature corresponds to a predefined content feature of an upload request packet authorized by the page server. The server then determines that an interface address indicated by the upload request packet corresponds to an upload interface of the to-be-identified request packet if the content feature corresponds to the set content feature of the upload request packet.