Synthetic Test Proxy Stitching for Low-Traffic End-to-End Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Synthetic network testing in wireless communication networks can trigger distributed denial of service (DDoS) attacks and security policy enforcement, leading to inaccurate results due to high volumes of network traffic, especially when testing applications behind a common gateway or security component.
Innovation Solution
Proxying application and network performance tests into two segments, with a network element or security component acting as a test proxy, and stitching results from endpoints to the target, reducing network traffic volume and generating comprehensive end-to-end test results.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If synthetic monitoring generates network traffic to test performance metrics, then testing accuracy is improved, but network traffic volume increases triggering DDOS detection
Solution Approach 1:
The patent introduces a broker as an intermediary component that sits between synthetic monitoring agents and the monitored application. The broker receives test traffic from multiple agents, aggregates it, and forwards consolidated requests to the application. This intermediary approach reduces the total volume of network traffic while maintaining testing accuracy, preventing DDOS detection while still enabling comprehensive performance monitoring.
Solution Approach 2:
The patent combines multiple individual test requests from different synthetic monitoring agents into a single aggregated request through the broker. Instead of each agent independently contacting the application (which would generate high traffic volume), the broker merges these requests and sends one consolidated request to the application, thereby reducing network traffic while preserving the ability to measure performance metrics accurately.
2Adaptability or versatility
If multiple endpoints perform synthetic testing simultaneously, then testing coverage is improved, but network traffic volume increases triggering security policy enforcement
Solution Approach 1:
The broker serves as a central intermediary that coordinates testing activities across multiple endpoints. Each synthetic monitoring agent communicates with the broker rather than directly with the application. The broker manages the distribution of test requests, ensuring comprehensive coverage across different endpoints while controlling the overall traffic volume by aggregating and coordinating requests, thus avoiding security policy enforcement.
Solution Approach 2:
The patent segments the testing architecture into three distinct components: synthetic monitoring agents at various endpoints, a central broker, and the monitored application. This segmentation allows each component to perform its specific function efficiently. The agents generate test requests, the broker aggregates and coordinates them, and the application receives consolidated requests. This segmented approach enables wide testing coverage while maintaining controlled traffic volumes that don't trigger security policies.
3Measurement precision
If end-to-end testing is performed directly from endpoints to application, then testing accuracy is improved, but network traffic volume increases
Solution Approach 1:
The broker acts as an intermediary that enables end-to-end testing functionality while reducing traffic volume. It receives detailed test requests from multiple agents, consolidates them into fewer requests, and forwards them to the application. This maintains the end-to-end testing capability (measuring performance from endpoint to application) while significantly reducing the quantity of network traffic through aggregation.
Solution Approach 2:
The patent implements partial action by having the broker handle the aggregation and coordination functions, rather than requiring every agent to perform complete end-to-end testing independently. Each agent performs partial testing (sending requests to the broker), and the broker completes the end-to-end measurement by forwarding consolidated requests to the application and collecting results. This partial action approach achieves end-to-end testing accuracy with reduced traffic volume.
Data Source
AI summary
Application and network tests executed for paths between endpoints and an application are proxied to reduce network traffic sent to application as part of synthetic testing. Testing for each endpoint behind a network element or security component acting as a test proxy for a path between the endpoint to the application is split into two segments: a segment from each endpoint to the test proxy, and a segment from the test proxy to the application. A service obtains test results from agents executing on the endpoints and the test proxy and “stitches” the results of each segment together to generate test results for the path from endpoint to application. Stitching refers to aggregating, combining, or otherwise joining the results obtained for each path segment to generate a set of test results for the path. The manner of stitching can vary depending on test type and/or types of performance metrics collected.