Proxy Server Dynamic API Service Scheme Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing API service schemes are inefficient as they maintain a static manner of generating and sending service callouts, leading to unchanged inefficiencies unless manually modified by developers, and lack dynamic improvement based on performance data.

Innovation Solution

A proxy server analyzes initial proxy code at development time and collects performance data at runtime to suggest and implement modifications in the service scheme, such as altering service callout sequences and caching policies, to optimize API request handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a static service scheme is used to generate and send service callouts, then the system structure is simple and easy to implement, but the API service efficiency deteriorates over time as inefficiencies accumulate and cannot be dynamically improved

Engineering Contradiction:
ImproveAPI service efficiencyVSAvoidservice scheme complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service schemes by allowing the proxy server to automatically modify service callout sequences, timing, and caching policies based on real-time performance data collection and analysis. The system transitions from static configuration to dynamic adaptation, where service schemes evolve continuously to optimize API response times and efficiency without manual developer intervention.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent establishes a feedback mechanism where performance data collected during API request processing is analyzed to identify inefficiencies. The system uses this feedback to automatically adjust service callout sequences and caching strategies, creating a closed-loop optimization system that continuously improves API service efficiency based on actual performance metrics.

Inventive Principle:
Principle #23Feedback

2Productivity

If manual modification of proxy code is required to improve service schemes, then the system maintains control and reliability, but the time required for optimization increases and productivity deteriorates

Engineering Contradiction:
Improveservice scheme optimization speedVSAvoidtime for manual modification
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements self-service optimization where the proxy server automatically analyzes performance data, identifies service callout inefficiencies, and modifies service schemes without requiring manual developer intervention. The system performs self-diagnosis and self-optimization by collecting performance metrics, analyzing them to detect patterns, and automatically adjusting service callout sequences and caching policies to improve API response times.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by proactively modifying service schemes before performance degradation occurs. The system analyzes performance data trends and preemptively adjusts service callout sequences and caching strategies to prevent inefficiencies from manifesting, rather than waiting for problems to arise and then manually fixing them.

Inventive Principle:
Principle #10Preliminary action

3Speed

If service callouts are made sequentially in a fixed order, then the implementation is simple and reliable, but the response time increases when multiple independent services are involved

Engineering Contradiction:
ImproveAPI response timeVSAvoidservice callout management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent implements dynamic service callout sequencing where the proxy server analyzes performance data to determine optimal callout orders and timing. The system dynamically adjusts the sequence and parallelization of service callouts based on real-time performance metrics, transitioning from fixed sequential execution to adaptive multi-step processing that optimizes response times.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments service callouts into independent steps that can be executed in parallel or sequence based on performance analysis. By dividing the service callout process into discrete, manageable segments, the system can optimize the execution order and timing of each segment independently, reducing overall response time while maintaining implementation simplicity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10642585B1Enhancing API service schemes
Publication Date: 2020.05.05 GOOGLE LLC
  • US10642585B1 patent drawing
  • US10642585B1 patent drawing
  • US10642585B1 patent drawing

AI summary

Embodiments of enhancing API servicing schemes are disclosed. A set of proxy code associated with servicing the API requests of an application is analyzed during development time to determine if any portion can be modified to improve the service scheme, prior to executing the set of proxy code in a runtime. After the set of proxy code is deployed in a runtime environment, performance data associated with the current service scheme is collected and periodically used to determine whether the service scheme for the API requests of the application is to be updated.