Batch Transaction Tracking for Large-Scale Record Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face inefficiencies when processing large numbers of records, as issues arising during processing can require reversing the entire cycle, wasting time and resources, and it is desirable to spread processing over multiple cycles to utilize non-peak times.
Innovation Solution
Automated generation of record subsets and concurrent monitoring by a system, using batch transaction records with subset identifiers and status fields to track processing, allowing for iterative submission and error handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a large number of records are processed in a single processing cycle, then processing efficiency is improved, but resource waste increases if problems arise requiring reversal of the entire cycle
Solution Approach 1:
The patent divides a large set of records into multiple smaller batches, where each batch is processed separately. This segmentation allows the system to process records in manageable units (e.g., batches of 1000 records) rather than all at once, so that if an error occurs, only the current batch needs to be reversed, not the entire processing cycle. The batch processing mechanism with individual batch identifiers and status tracking enables this granular approach to improve efficiency while reducing resource waste.
2Loss of energy
If processing is spread over multiple cycles, then resource waste is reduced, but processing time increases
Solution Approach 1:
The patent performs preliminary actions by pre-dividing records into batches and preparing batch transaction records before actual processing begins. The system pre-assigns batch identifiers and sets up the processing framework in advance, so that when processing starts, each batch can be handled immediately without setup delays. This preliminary organization reduces the time penalty associated with multi-cycle processing.
Solution Approach 2:
The patent maintains continuity of useful action by implementing an automated batch processing system that continuously processes batches without idle gaps. The system monitors batch status and automatically initiates the next batch processing cycle, ensuring that processing continues uninterrupted. This continuous operation minimizes the time loss that would otherwise occur between processing cycles.
3Reliability
If automated batch generation and monitoring is implemented, then error handling is improved, but system complexity increases
Solution Approach 1:
The patent implements self-service mechanisms where the batch processing system automatically monitors its own status, detects errors, and handles exceptions without requiring external intervention. The system automatically sets batch status to 'submitted,' monitors processing completion, detects errors through status checks, and can automatically retry or halt processing based on error conditions. This automation improves reliability while keeping complexity manageable by making the system self-sufficient.
Solution Approach 2:
The patent incorporates feedback mechanisms through status fields that track batch processing state (e.g., 'submitted,' 'completed,' 'error'). The system continuously monitors these status indicators and uses the feedback to determine next actions, such as whether to proceed to the next batch or handle an error. This feedback-driven approach improves error handling reliability by providing real-time visibility into processing state while maintaining relatively simple control logic.
Data Source
AI summary
Automated batch generation and subsequent submission and monitoring of batches processed by a system is disclosed. A plurality of records to be submitted to a system for processing is accessed. A plurality of record groups is generated, each record group corresponding to a different subset of records. A plurality of batch transaction records is generated. Each batch transaction record corresponds to one of the plurality of record groups, and includes a subset identifier that references a subset of records of a record group to which the batch transaction record corresponds, and a status field. A first batch transaction record that identifies a first subset of records is accessed. The status field of the first batch transaction record is set to a submitted value, and instructions are sent to the system to process the first subset of records.