Analytics Framework Selection via Event Agents

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Developers face difficulties in selecting and switching between different analytics providers for application analytics, as existing solutions require significant modifications to the application code, making it time-consuming and inflexible.

Innovation Solution

A flexible, scalable, provider-independent analytics framework that allows selection of analytics providers through a provider type constant, using a generic event reporting instance and multiple event agents to route events to various providers, enabling easy changes without modifying the application code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers use existing analytics solutions that are integrated into application code, then analytics data collection is achieved, but switching analytics providers requires significant code modifications and is time-consuming

Engineering Contradiction:

ImproveAbility to switch analytics providersVSAvoidTime required to modify application code

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary analytics framework that sits between the application code and the analytics provider. This framework includes event agents that capture analytics events and route them to selected providers, allowing developers to switch providers without modifying application code. The framework acts as a mediator that handles the complexity of provider integration and switching.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the analytics integration into separate modular components: event agents that capture events, a routing mechanism that directs events to providers, and provider interfaces that handle provider-specific logic. This segmentation allows independent modification of the provider selection without affecting the core application code or other analytics components.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If developers integrate analytics providers directly into application code, then analytics functionality is implemented, but the application code becomes tightly coupled to specific providers making it inflexible

Engineering Contradiction:

ImproveFlexibility in analytics provider selectionVSAvoidComplexity of application code structure

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The analytics framework serves as an intermediary layer that manages the complexity of multi-provider integration. It includes event agents that standardize event capture, a routing system that directs events to appropriate providers, and adapter patterns that handle provider-specific requirements. This intermediary structure increases flexibility while containing complexity within the framework rather than the application code.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal analytics framework that can work with multiple different analytics providers through a common interface. The event agents and routing mechanism are provider-agnostic, allowing the same framework to support different providers without requiring separate integration code for each provider in the application logic.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If developers want to support multiple analytics providers, then analytics versatility is improved, but code complexity and difficulty of implementation increase

Engineering Contradiction:

ImproveSupport for multiple analytics providersVSAvoidComplexity of analytics integration code

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework introduces intermediary components that simplify multi-provider support: event agents that uniformly capture events regardless of provider, a routing mechanism that intelligently directs events to selected providers, and interface adapters that handle provider-specific protocols. These intermediaries abstract the complexity of multi-provider integration away from the application code.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses template patterns and interface copying where a standard event interface is defined once and then implemented or adapted for different providers. The routing mechanism copies events from the standardized format to provider-specific formats, eliminating the need to write separate capture logic for each provider and reducing overall code complexity.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11016825B2Flexible analytics framework selection

Publication Date: 2021.05.25 OMNISSA LLC

AI summary

The flexible selection among analytics providers is described. In one example, an application is developed for use with a number of different analytics providers. After the application is developed, one or more of the analytics providers can be easily selected based on a constant defined in an analytics framework of the application. During execution of the application, the application can identify the selected analytics provider based on the predetermined constant in the analytics framework. When an event is triggered at a certain occasion or step during the process, the analytics framework can route the event to an event agent for the selected analytics provider. Further, the event agent can perform an event report call based on the event, where the event report call is tailored for the interface of the selected analytics provider by the event agent. The analytics provider can be easily changed by updating the predetermined constant.