Event Record API Serial Processing for DFS Reconciliation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communication delays or errors between systems and software programs in digital finance services (DFS) can lead to inaccurate recording of transactional events, resulting in pending payments not being updated as completed in the events database.

Innovation Solution

A computer system configured to collect and modify pending event records for batch processing by an API, converting them into a serial format to avoid time-consuming CSV conversion, allowing for automated determination of event status by comparing records against completed event indications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If event records are converted to CSV format for batch processing, then processing efficiency is improved, but processing time increases significantly

Engineering Contradiction:
Improvebatch processing efficiencyVSAvoidconversion time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent extracts the format conversion step from the batch processing workflow by directly passing event records in their native format to the API, eliminating the time-consuming CSV conversion step while maintaining batch processing capabilities

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary processing layer that adapts the event records format to match API expectations without requiring full CSV conversion, enabling efficient batch processing while avoiding the time penalty of traditional format transformation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If communication between systems is increased to maintain real-time updates, then data accuracy is improved, but system complexity increases

Engineering Contradiction:
Improveevent status accuracyVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The API performs self-service by automatically determining event status through internal comparisons and logic, eliminating the need for complex inter-system communication and manual status verification while maintaining high accuracy

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent creates a simplified copy of the event data structure that contains only the essential fields needed for status determination, allowing the API to process events independently without requiring access to complex source systems

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240184644A1Automated status determination of events collected in records for network service provider
Publication Date: 2024.06.06 T MOBILE US INC
  • US20240184644A1 patent drawing
  • US20240184644A1 patent drawing
  • US20240184644A1 patent drawing

AI summary

A method for determining status of events collected in records includes retrieving a group of records of respective events from an events database. The method includes extracting records from the group of records to generate a subgroup of records and storing the subgroup of records temporarily at a memory of a computer system. The subgroup of records is arranged serially at the memory of the computer system for processing by an application programming interface (API). Responsive to requests, the API serially processes respective records of the subgroup of records by comparing each record in the subgroup of records against indications of completed events. The method includes performing a self-executing action based on an output of the API including an indication of a status of a particular event in the subgroup of records. In one example, the status indicates that the particular event is complete or incomplete.