Web Application Proxy Dynamic Counter Creation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in dynamically creating traffic counters in real-time web application layer proxies due to difficulties in determining exact parameter values and the impracticality of creating counters for every possible combination of source and destination IP addresses.

Innovation Solution

A mechanism for dynamically creating counters based on actual traffic by installing counting rules that specify parameters, allowing the web application layer proxy to create or update counters in real-time as web application layer requests are received, without pre-defining parameter values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If counters are created for every possible combination of source IP address and destination IP address, then complete traffic coverage is achieved, but system complexity and resource consumption become unmanageable

Engineering Contradiction:

Improvetraffic coverage completenessVSAvoidcounter management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the counter creation process into two stages: pre-defined counter templates with common parameter combinations, and dynamic counter creation only when actual traffic matches undefined combinations. This segmentation reduces the overall number of counters needed while maintaining complete traffic coverage.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-defining counter templates with common parameter combinations before traffic analysis begins. This preliminary setup covers the majority of expected traffic patterns, eliminating the need to pre-create counters for all possible IP combinations.

Inventive Principle:

Principle #10Preliminary action

2Measurement precision

If exact parameter values are determined in advance for traffic counting, then precise traffic monitoring is achieved, but adaptability to new traffic patterns is reduced

Engineering Contradiction:

Improvetraffic parameter precisionVSAvoidtraffic pattern adaptability

Core Design Contradiction:

Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by allowing the counter set to evolve during runtime. When new traffic patterns are detected that don't match existing counter templates, dynamic counters are automatically created to track these new patterns, ensuring both precision and adaptability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs self-service by automatically detecting new traffic patterns and creating appropriate counters without external intervention. The proxy server monitors incoming traffic and autonomously expands its counter set to cover newly observed parameter combinations.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If dynamic counter creation is implemented during runtime, then adaptability to actual traffic is improved, but processing overhead increases

Engineering Contradiction:

Improvereal-time traffic adaptabilityVSAvoidprocessing resource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by implementing dynamic counter creation only when necessary - specifically when incoming traffic doesn't match existing counter templates. The majority of traffic is handled by pre-defined counters, while dynamic creation occurs only for the minority of new, unseen patterns.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11329996B2Dynamic aggregation of information based on web application layer requests

Publication Date: 2022.05.10 IMPERVA INC

AI summary

A method by a web application layer proxy for dynamically creating counters during runtime based on actual web application layer requests received by the web application layer proxy. The method includes installing a counting rule in the web application layer proxy, where the counting rule specifies a set of parameters based upon which to create counters, receiving a web application layer request generated by a web application client that is intended for a web application server, determining a set of parameter values associated with the web application layer request that corresponds to the set of parameters specified by the counting rule, and creating a counter associated with the set of parameter values associated with the web application layer request in response to a determination that a counter associated with the set of parameter values associated with the web application layer request does not exist.