Batched API Request Generation for Interaction Data Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Processing interactions individually consumes significant computing resources and network bandwidth, necessitating a more efficient method for handling interaction data.

Innovation Solution

A computing system receives images from a mobile device, extracts interaction data, and generates an application programming interface (API) request in batches to an entity server, reducing the number of requests and optimizing resource usage by processing interactions in groups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If interactions are processed individually, then each interaction can be handled independently and accurately, but computing resource consumption and network bandwidth usage increase significantly

Engineering Contradiction:

Improveinteraction processing accuracyVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent combines multiple individual interaction processing requests into a single batched API request. Instead of sending separate requests for each interaction, the system aggregates multiple interactions into one request payload, allowing the entity server to process them together. This merging approach maintains processing accuracy while significantly reducing the number of network round trips and computing resources consumed.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The API request structure is designed to handle multiple interactions of different types within a single request. The system can accommodate various interaction types (deposits, withdrawals, transfers, etc.) in the same batch request, making the processing mechanism universally applicable to different interaction scenarios without requiring separate processing logic for each type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Device complexity

If interactions are processed individually, then processing can be simple and straightforward, but network bandwidth consumption increases

Engineering Contradiction:

Improveprocessing simplicityVSAvoidnetwork bandwidth usage

Core Design Contradiction:

Device complexityVSLoss of substance

Solution Approach 1:

Multiple interaction data records are merged into a single JSON payload that is transmitted in one API request. The request structure includes a header with metadata about the batch (number of interactions, total amount) and a body containing all interaction details, reducing network traffic compared to sending separate requests for each interaction.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary aggregation of interaction data before sending to the entity server. Interaction data is collected, validated, and organized into batched requests in advance, so that when the API call is made, the data is already structured and ready for processing, reducing the overhead of multiple separate network transactions.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If interactions are processed individually, then each request can be handled independently, but processing speed decreases

Engineering Contradiction:

Improveprocessing independenceVSAvoidprocessing speed

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system merges multiple independent interaction processing tasks into a single batched request that the entity server processes concurrently. The entity server receives all interactions in one request and handles them in parallel within the same processing cycle, achieving higher throughput while maintaining the independence of each interaction's processing logic through structured data organization.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The batched request structure enables continuous processing of multiple interactions without interruption. Once the API request is received, the entity server can process all interactions in the batch continuously in one operation, eliminating the start-stop nature of individual requests and maintaining steady processing flow for higher productivity.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS20240345850A1Generating an application programming interface request using sets of interaction data

Publication Date: 2024.10.17 TRUIST BANK

AI summary

A computing system can receive, from a mobile application executing on a mobile device, at least one image that has been captured on the mobile device and corresponds to an interaction. The computing system can extract interaction data from each image. The computing system can transmit an application programming interface request to an entity server that is configured to cause the entity server to process the plurality of interactions and receive a confirmation from the entity server that the plurality of interactions have been processed.