Real-time Transaction Approval via Named Entity Parsing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing transaction approval systems face challenges in real-time processing due to the complexity of data handling, especially when dealing with non-standardized communication formats and noisy data fields, which can lead to delays and instability in server performance.

Innovation Solution

A transaction approval system comprising a first server for storing transaction data and a second authorizer server that applies named entity identification rules to parse and identify named entities in transaction data payloads, enabling real-time approval based on predefined rules and improving server stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the server handles thousands of requests per minute with real-time transaction approval, then the transaction speed is improved, but the server stability and processing reliability deteriorate due to data complexity and noisy fields

Engineering Contradiction:

Improvetransaction approval speedVSAvoidserver processing stability

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The system performs preliminary action by pre-processing transaction data to identify and filter out noisy fields before the actual approval process. The server anticipates potential data quality issues and prepares cleaned, validated data structures in advance, allowing rapid approval decisions without encountering data complexity during high-volume processing periods.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The approval process is segmented into distinct stages: data reception, data validation, noise filtering, named entity identification, and approval decision. Each stage handles specific aspects of data processing independently, preventing the complexity of the entire dataset from overwhelming the server during high-speed processing.

Inventive Principle:

Principle #1Segmentation

2Productivity

If the server uses standardized protocols for communication, then the data processing speed is improved, but the system's adaptability to customized transaction features deteriorates

Engineering Contradiction:

Improvedata processing speedVSAvoidcustomized transaction feature support

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The system employs dynamic data processing that adapts to different transaction formats in real-time. Rather than relying solely on fixed standardized protocols, the server dynamically identifies and processes both standard and customized fields, adjusting its parsing and validation logic based on the specific transaction structure received, thus maintaining high processing speed while supporting adaptability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The server implements a universal data processing framework that can handle multiple communication formats simultaneously. The system is designed to process standardized protocols efficiently while also accommodating customized transaction features, making the server multi-functional and adaptable to various transaction types without sacrificing processing speed.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If the server processes transaction data with noisy and non-standardized fields, then the system's adaptability is improved, but the data retrieval and processing time increases

Engineering Contradiction:

Improvenon-standardized communication supportVSAvoiddata retrieval and processing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The server performs preliminary data cleaning and validation actions immediately upon receiving transaction data, identifying and filtering out noisy fields before they affect processing time. This anticipatory approach ensures that even when non-standardized communication is used, the data is prepared in advance for rapid processing, minimizing time loss.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system extracts and isolates noisy, non-standardized fields from the transaction data, separating them from the core information needed for approval decisions. By taking out the problematic data elements, the server can process the essential information efficiently while maintaining adaptability to the original non-standardized communication format.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20250165713A1Real-time named entity based transaction approval

Publication Date: 2025.05.22 RAMP BUSINESS CORP

AI summary

A system for stable and streamlined transaction approval includes a rule management server and an authorizer server. The rule management server is configured to receive a transaction rule that includes a list of named entities specified by a client. The rule management server stores past transaction data and analyzes patterns in the past data to determine a named entity identification rule. The authorizer server receives a transaction data payload related to a pending transaction associated with the client and identifies a noisy data field in the transaction data payload. The noisy data field includes a representation of a particular named entity and one or more irrelevant strings. The authorizer server parses the particular named entity based on the named entity identification rule and determines whether the particular named entity is one of the named entities in the list. The authorizer server conducts a transaction evaluation using the result.