API Consumption Prediction Using Social Network Analytics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack an effective method to predict API consumption patterns, which are crucial for developers and consumers in optimizing software service applications, as they rely on historical data and social network interactions.

Innovation Solution

A computer-implemented method using an API analytics engine that generates consumption prediction models based on API consumption history, user expertise, and social network relationships to identify trends and optimize API selection for users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If historical data and social network interactions are used to predict API consumption, then prediction accuracy is improved, but system complexity increases

Engineering Contradiction:
Improveprediction accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments the prediction problem by separating API consumption prediction from social network analysis. The API analytics engine independently processes consumption history and generates prediction models, while the social network component separately analyzes user relationships. This segmentation allows each component to be optimized independently, reducing overall system complexity while maintaining prediction accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The API analytics engine acts as an intermediary between the consumption history data and the prediction models. It processes historical data, incorporates social network factors, and generates predictions in a structured manner. This intermediary component simplifies the system architecture by providing a clear data flow from raw data to predictions, making the complex prediction process more manageable.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If API consumption prediction models are generated based on multiple factors, then prediction accuracy is improved, but data processing time increases

Engineering Contradiction:
Improveprediction accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary processing of API consumption history and social network data to pre-compute features and patterns. By analyzing historical data in advance and pre-processing social network relationships, the system reduces the computational burden during actual prediction time, thereby decreasing data processing time while maintaining high prediction accuracy through the pre-generated models.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If social network relationships are integrated into prediction models, then prediction accuracy is improved, but ease of operation decreases

Engineering Contradiction:
Improveprediction accuracyVSAvoidease of operation
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The API analytics engine automatically processes consumption history, retrieves social network data, and generates prediction models without requiring manual intervention. The system self-manages the complex tasks of data retrieval, model generation, and prediction, making it easy to operate while maintaining high accuracy through the integrated social network analysis.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9292363B2Predicting application programming interface consumption using social networks
Publication Date: 2016.03.22 TAIWAN SEMICONDUCTOR MANUFACTURING CO LTD
  • US9292363B2 patent drawing
  • US9292363B2 patent drawing
  • US9292363B2 patent drawing

AI summary

Predicting consumption of APIs is provided. A set of consumed APIs corresponding to a user and software service applications related to APIs associated with the user is determined based on an API consumption history. A set of users related to the set of consumed APIs corresponding to the user and the software service applications related to the APIs associated with the user is retrieved from an API analytics engine. A set of API consumption prediction models corresponding to the user is generated based on the APIs associated with the user, the software service applications related to the APIs associated with the user, the set of consumed APIs corresponding to the user and the software service applications related to the APIs associated with the user based on the API consumption history, the set of users related to the set of consumed APIs, and APIs associated with the set of users.