File Tracking via Bifurcated Static Dynamic Content Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Websites face resource drainage and slowed request handling due to indirect network traffic from third-party sites accessing static content, which is not efficiently handled by existing systems, leading to computational inefficiencies and potential system overload.

Innovation Solution

Implementing a bifurcated system architecture that processes static and dynamic content differently, allowing for parallel retrieval and merging of static and dynamic content into a single file, and embedding unique identifiers for tracking, thereby reducing unnecessary processing and enhancing resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the front-end processing layer processes all network requests (including static content from third-party sites), then access restrictions and customizations can be implemented, but system resources are severely drained and request handling slows down

Engineering Contradiction:

Improveaccess restriction enforcementVSAvoidrequest handling speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments network requests into two categories: requests originating from the website domain and requests originating from external domains. This segmentation allows the system to apply different processing rules to each category, with static content requests from external domains being served without front-end processing layer intervention, thereby resolving the contradiction between maintaining access control reliability and preserving request handling productivity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts static content delivery from the front-end processing layer's responsibility scope. By identifying and separating static content requests (particularly those from third-party sites) from dynamic content requests, the system removes the harmful processing overhead from the critical static content delivery path, thus improving request handling speed while maintaining necessary controls for dynamic content.

Inventive Principle:

Principle #2Taking out (Extraction)

2Reliability

If the front-end processing layer handles static content requests, then access restrictions can be enforced, but computational costs increase and system capacity is reached

Engineering Contradiction:

Improveaccess controlVSAvoidcomputational cost

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent inverts the traditional approach by not applying front-end processing to all requests. Instead, it applies processing only to requests that require it (dynamic content from the same domain), while allowing static content requests from external domains to pass through without processing. This inversion eliminates unnecessary computational costs while maintaining access control where needed.

Inventive Principle:

Principle #13The other way round (Inversion)

3Adaptability or versatility

If indirect traffic from third-party sites is allowed, then static content becomes widely accessible, but system resources are drained without corresponding increase in actual site visits

Engineering Contradiction:

Improvecontent accessibilityVSAvoidresource utilization efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent converts the harmful effect of indirect traffic from third-party sites into a beneficial outcome. By allowing these requests to access static content without front-end processing, the system maintains high content accessibility while improving resource utilization efficiency. The harm of resource drainage is eliminated while the benefit of widespread content accessibility is preserved.

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS9942362B2Tracking downloadable electronic files

Publication Date: 2018.04.10 RESGATE

AI summary

Client requests for electronic files (e.g., requests for download from a website) can be leveraged by augmenting the electronic files with unique identifiers and/or enriching (e.g., dynamic) content, and tracking distribution or usage of the files based on network requests associated with the electronic files, such as attempts to upload a previously downloaded file or content requests originating from links included in the augmented electronic files.