Client Telemetry Engine for Distributed Data Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service providers face inefficiencies in monitoring and analyzing large amounts of data from multiple client devices, consuming valuable server and network resources, and requiring manual interaction and separate tools for data collection and diagnosis.

Innovation Solution

A telemetry engine integrated into client applications, comprising a telemetry transport component, data collection module, and rule manager/analyzer, which collects and analyzes data locally and reports it to a service provider, reducing the need for manual intervention and separate tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If large amounts of raw application data are transmitted over the network to the service provider for analysis, then the service provider can detect and diagnose application issues, but valuable server and network resources are consumed and the server is overly burdened

Engineering Contradiction:
Improveapplication issue detection capabilityVSAvoidserver and network resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments the data analysis function by dividing it between the telemetry engine on client devices and the service provider server. The telemetry engine performs local data collection, filtering, and preliminary analysis, while the server receives only processed telemetry data for final analysis. This segmentation reduces network traffic and server resource consumption while maintaining issue detection capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The telemetry engine performs preliminary data processing actions locally before transmission to the service provider. This includes collecting raw application data, filtering it according to predefined criteria, and preparing it for analysis. By performing these preliminary actions at the client device, the system reduces the amount of data that needs to be transmitted and processed by the server, thereby reducing resource consumption.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If separate tools are installed on client devices to facilitate data monitoring and analysis, then data collection capability is enhanced, but device complexity increases and manual installation is required

Engineering Contradiction:
Improvedata collection capabilityVSAvoidnumber of installed components
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The telemetry engine merges multiple data collection and analysis functions into a single integrated component that is built into the application itself. This eliminates the need for separate monitoring tools to be installed on client devices. The telemetry engine combines data collection, filtering, and preliminary analysis capabilities within the application package, reducing device complexity while maintaining enhanced data collection capability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The telemetry engine is designed as a universal component that can collect and analyze various types of application data across different client devices. It performs multiple functions including data collection, filtering, and preliminary analysis within a single integrated system. This multi-functional design eliminates the need for multiple separate tools, reducing the number of components installed on each device while maintaining comprehensive data collection capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If direct interaction with client devices is necessary to collect and analyze data, then data access is achieved, but operational complexity and time requirements increase

Engineering Contradiction:
Improvedata access capabilityVSAvoidmanual interaction requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The telemetry engine enables the application to self-monitor and self-report its own performance and state data. The system automatically collects telemetry data from the application without requiring manual interaction with client devices. The telemetry engine continuously monitors application behavior, filters data according to predefined criteria, and transmits it to the service provider autonomously, eliminating the need for manual data collection operations while maintaining reliable data access.

Inventive Principle:
Principle #25Self-service

4Speed

If application data is continuously monitored across large numbers of distributed client devices, then real-time issue detection is improved, but resource consumption and system complexity compound

Engineering Contradiction:
Improveissue detection speedVSAvoidresource consumption across distributed devices
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The system segments the continuous monitoring function by distributing the telemetry engine across client devices while maintaining centralized coordination by the service provider. Each telemetry engine independently monitors its local application data continuously, performing local filtering and preliminary analysis. This segmentation enables real-time issue detection at the source while reducing the overall resource consumption by avoiding centralized processing of all raw data from distributed devices.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9590880B2Dynamic collection analysis and reporting of telemetry data
Publication Date: 2017.03.07 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9590880B2 patent drawing
  • US9590880B2 patent drawing
  • US9590880B2 patent drawing

AI summary

Technologies are generally described for collecting, analyzing and reporting telemetry data. A telemetry engine is built into a client application installed on a client device, and the telemetry engine is configured to collect and analyze application data at the client device and report the analyzed data to a service provider associated with the application. The telemetry application includes a specialized set of components, such as a telemetry transport component configured to communicate with the service provider, a data collection module configured to retrieve data from the application, and a rule manager and analyzer configured to analyze collected data according to a set of data collection rules provided by the service provider. The telemetry engine enables collection and analysis of telemetry data from multiple distributed client devices. The client devices dynamically change over time to ensure that current and important information is reported to the service provider.