Client-Side QoS Tracking via Server-Provided Aggregation Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed systems primarily focus on server-side quality of service (QoS) measurements, which do not accurately reflect the QoS experienced by clients, and fail to account for client-side issues such as performance problems or bugs in client libraries, leading to incomplete performance assessments.
Innovation Solution
Implementing a client-side measurement system that receives aggregation rules from a server to collect and manipulate quality of service metrics, generating aggregated data that is then reported back to the server for storage and analysis, allowing for comprehensive QoS control and data mining with reduced data transmission and flexible rule updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If server-side QoS measurements are implemented, then QoS data can be collected and stored, but the measurements do not accurately reflect the QoS experienced by clients
Solution Approach 1:
The patent inverts the traditional server-side QoS measurement approach by implementing QoS tracking at the client device. Instead of the server measuring QoS, the client device itself performs the measurements using a measurement client that collects QoS metrics locally, thereby obtaining accurate client-side QoS data while maintaining system manageability through server-provided aggregation rules
Solution Approach 2:
The patent introduces an intermediary measurement client component that bridges the gap between the client application and the server. This measurement client collects QoS metrics at the client device, processes them according to aggregation rules, and reports them to the server, thereby enabling accurate client-side measurements while maintaining server control
2Reliability
If comprehensive QoS tracking is implemented at the server, then server performance can be monitored, but client-side issues such as client library bugs are not detected
Solution Approach 1:
The patent implements self-service by enabling the client device to autonomously perform QoS measurements and collections. The measurement client at the client device automatically collects QoS metrics, applies aggregation rules, and reports data without requiring complex server-side tracking infrastructure, thereby achieving comprehensive monitoring while simplifying the overall system
Solution Approach 2:
The measurement client component serves multiple functions: it acts as a data collector, a rule processor, and a communication interface. This multi-functional design enables comprehensive QoS tracking including client library performance detection without requiring separate complex systems for each function
3Loss of information
If detailed QoS metrics are collected and transmitted to the server, then comprehensive analysis is possible, but data transmission and processing burdens increase
Solution Approach 1:
The patent applies preliminary action by performing data aggregation and processing at the client device before transmission. The measurement client collects raw QoS metrics, applies aggregation rules to consolidate data, and then transmits only the aggregated results to the server, thereby preserving information completeness while reducing transmission burden
Solution Approach 2:
The patent extracts only the essential aggregated QoS data from the raw metrics at the client side. By applying aggregation rules locally and extracting only the consolidated results for transmission, the system maintains data completeness for analysis while minimizing the volume of transmitted data and associated energy consumption
4Adaptability or versatility
If client libraries are made more functional to access distributed systems, then service capability improves, but client library performance issues and bugs negatively impact perceived QoS
Solution Approach 1:
The patent segments the QoS measurement function from the client library itself by introducing a separate measurement client component. This segmentation allows the client library to maintain its full functionality for accessing distributed systems while the measurement client independently tracks QoS metrics, thereby preventing client library performance issues from contaminating QoS measurements
Data Source
AI summary
Server-side control of client-side quality-of-service tracking is provided. When a service is being provided to a client device, a server provides aggregation rules to a client device as part of the service. The client device executes instructions in the aggregation rules to collect QoS metrics regarding the service on the client device and to manipulate the QoS metrics to generate aggregated QoS data. The client device reports the aggregated QoS data to a server for storage and analysis.