CDN API Payload Content Detection and Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

API messages lack standardized methods for optimizing inlined or referenced content, such as images, HTML, JS, and CSS, making it difficult for CDNs to efficiently optimize and deliver content due to the arbitrary formats and unknown locations of this content within the payload.

Innovation Solution

A CDN server is configured to detect and optimize inlined content in API messages using content location instructions, verifying the identity of the content and swapping it with optimized versions, with the assistance of an offline analysis service that generates instructions based on observed traffic patterns to streamline the optimization process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If CDNs manually configure knowledge of message formats for each API, then optimization capability is improved, but device complexity and resource requirements increase significantly

Engineering Contradiction:
Improveoptimization capabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing the CDN to automatically discover and learn API message formats through observation of traffic patterns. The offline analysis service autonomously profiles APIs and generates content location instructions without manual configuration, making the system adapt to new APIs automatically as they are deployed

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The offline analysis service performs preliminary analysis of API traffic patterns to profile message formats and generate content location instructions in advance. This preliminary action prepares the CDN optimization system with pre-configured knowledge of content locations and formats before actual optimization is needed, eliminating the need for manual configuration at deployment time

Inventive Principle:
Principle #10Preliminary action

2Productivity

If CDNs apply optimization techniques to inlined content in API payloads, then content delivery efficiency is improved, but the ability to locate and verify content instances deteriorates due to arbitrary formats

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoidcontent location difficulty
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system uses feedback from observed API traffic patterns to continuously refine and update content location instructions. The offline analysis service monitors actual message formats and adjusts its understanding of content locations based on real-world usage, improving detection accuracy over time

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes parameters by dynamically generating content location instructions based on observed traffic patterns rather than using fixed, predetermined locations. The instructions adapt to variations in message formats, content types, and structural parameters, enabling reliable content location across different API implementations

Inventive Principle:
Principle #35Parameter changes

3Productivity

If CDN performs real-time optimization of API messages, then content optimization is improved, but message delivery latency increases

Engineering Contradiction:
Improveoptimization qualityVSAvoidmessage delivery latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary optimization by pre-processing and caching optimized versions of content during offline analysis. When actual API messages are received, the CDN can quickly swap in pre-optimized content without performing full real-time optimization, significantly reducing latency while maintaining optimization quality

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system segments the optimization process into offline analysis phase and online delivery phase. The computationally intensive format profiling and content analysis are performed offline, while the online phase only requires lightweight content swapping based on pre-generated instructions, separating heavy processing from time-critical operations

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240054036A1Detection and Optimization of Content in The Payloads of API Messages
Publication Date: 2024.02.15 AKAMAI TECHNOLOGIES INC
  • US20240054036A1 patent drawing
  • US20240054036A1 patent drawing
  • US20240054036A1 patent drawing

AI summary

A server in a content delivery network (CDN) can examine API traffic and extract therefrom content that can be optimized before it is served to a client. The server can apply content location instructions to a given API message to find such content therein. Upon finding an instance of such content, the server can verify the identity of the content by applying a set of content verification instructions. If verification succeeds, the server can retrieve an optimized version of the identified content and swap it into the API message for the original version. If an optimized version is not available, the server can initiate an optimization process so that next time the optimized version will be available. In some embodiments, an analysis service can assist by observing traffic from an API endpoint over time, detecting the format of API messages and producing the content location and verification instructions.