Transaction Data Classification and Schema Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge lies in correlating and consolidating metadata from diverse data transfers, which often lack consistent information and formatting, making it difficult to track transactions and infer additional data about entities involved.

Innovation Solution

A method and system that classify data transfers by receiving information associated with a transmission, determining a classification, and formatting data into specific schemas to request and update location information, thereby correlating and completing transaction records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If metadata from diverse data transfers is collected without standardization, then the quantity of data transfers tracked increases, but the difficulty of correlating and consolidating metadata increases

Engineering Contradiction:
Improvequantity of data transfers trackedVSAvoiddifficulty of correlating and consolidating metadata
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent applies homogeneity by implementing a standardized schema that transforms diverse, heterogeneous metadata from different data transfers into a uniform structure. This schema defines consistent fields and formats for storing transaction information, enabling efficient correlation and consolidation of metadata across multiple data transfers without increasing system complexity

Inventive Principle:
Principle #33Homogeneity

Solution Approach 2:

The patent implements universality through a multi-functional schema design that can accommodate various types of data transfers (payments, transfers, transactions) using a single standardized framework. This universal schema structure allows the system to handle diverse metadata types while maintaining consistent organization and enabling broad applicability across different transaction scenarios

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If location information is requested for all data transfers, then the completeness of transaction records improves, but the amount of data processing and schema formatting required increases

Engineering Contradiction:
Improvecompleteness of transaction recordsVSAvoidamount of data processing and schema formatting
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies partial action by selectively requesting location information based on the classification of data transfers. Rather than universally requesting location data for all transactions, the system identifies specific transaction types that benefit from location information and processes those selectively, reducing overall data processing requirements while maintaining record completeness where needed

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements preliminary action by classifying data transfers and determining schema requirements before actual data processing occurs. This upfront classification enables the system to pre-determine which transactions need location information and prepare appropriate schemas in advance, reducing the processing burden during actual data consolidation operations

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250139130A1Categorization of transactions using third-party data
Publication Date: 2025.05.01 APPLE INC
  • US20250139130A1 patent drawing
  • US20250139130A1 patent drawing
  • US20250139130A1 patent drawing

AI summary

A method may include receiving information associated with a transmission of data. The method may include determining a classification for the information associated with the transmission of data. Based on the classification and in response to a trigger, the method may include formatting a portion of the information into a first schema associated with a location service. The method may also include transmitting a request for location information corresponding to the portion of the information to the location service according to the first schema. The method may include receiving, from the location service, the location information according to the first schema and formatting the location information from the first schema to a second schema associated with the computing device. The method may include updating the information associated with the transmission of data to include the location information.