API Analytics System Real-Time Pattern Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current API analytics systems lack real-time monitoring and pattern detection capabilities, struggle with scalability under high API traffic, and are limited in classifying activities based on similarity to predetermined usage patterns rather than exact matches.

Innovation Solution

An API analytics system that includes a usage identification module to form truncated API call data, a pattern classification module to generate decision trees, and real-time pattern detection, enabling classification of unknown activities based on similarity to predetermined patterns and handling high traffic through consolidation of duplicated API calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If real-time monitoring and pattern detection are implemented, then API usage analysis efficiency is improved, but system complexity increases

Engineering Contradiction:
ImproveAPI usage analysis efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the API analytics functionality into distinct modules: a usage identification module that forms truncated API call data by consolidating duplicated calls, and a pattern classification module that generates decision trees from predetermined usage patterns. This modular segmentation enables real-time monitoring while managing system complexity through organized, independent components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by establishing predetermined API usage patterns and generating decision trees in advance. These pre-computed classification structures enable rapid real-time analysis without requiring complex processing during actual API call monitoring, thus improving efficiency while controlling system complexity.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If duplicated API calls are consolidated, then data analysis volume is reduced, but information loss may occur

Engineering Contradiction:
Improvedata analysis volumeVSAvoidinformation loss
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The usage identification module extracts and consolidates duplicated API calls from the raw API call data, forming truncated API call data. This extraction process removes redundant information while preserving the essential usage patterns, thereby reducing data analysis volume without significant information loss about actual API usage behavior.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates a simplified copy of the API call data by forming truncated versions that consolidate duplicated calls. This copied representation maintains the essential characteristics of API usage patterns while reducing the overall data volume, enabling efficient analysis without requiring processing of every single duplicated call.

Inventive Principle:
Principle #26Copying

3Measurement precision

If classification based on similarity to predetermined patterns is used, then classification accuracy is improved, but processing time increases

Engineering Contradiction:
Improveclassification accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The pattern classification module generates decision trees from predetermined API usage patterns in advance. These pre-computed decision structures enable rapid classification of unknown activities by simply traversing the pre-built trees, achieving both high classification accuracy based on pattern similarity and fast processing times without requiring complex real-time computations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2871574B1Analytics for application programming interfaces
Publication Date: 2023.03.08 ACCENTURE GLOBAL SERVICES LTD
  • EP2871574B1 patent drawingFigure 1
  • EP2871574B1 patent drawingFigure 2
  • EP2871574B1 patent drawingFigure 3

AI summary

API analytics systems and methods are provided. Frequently occurring API usage patterns may be determined from API call data collected from across an API ecosystem. Alternatively or in addition, a classification structure, such as a decision tree, may be generated from the API usage patterns. A type of activity that resulted in a set of API calls being invoked may be determined from the classification structure. A similarity or difference between the set of API calls and the frequently occurring API usage patterns may also be determined and/or identified.