Split Transaction System Using Profile Directory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic transaction technologies lack the capability to manage electronic split transactions involving multiple users, particularly when contact information of one user is missing from the initiating device.

Innovation Solution

A data processing system that includes a processor and a profile directory database to retrieve and manage user profiles, enabling the initiation of split transactions by obtaining missing contact information from associated user devices, either through proximity or indirect methods, and linking it with user profiles for accurate transaction execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing electronic transaction technologies are used, then simple two-party transactions can be conducted, but multi-user split transactions cannot be managed when contact information is missing

Engineering Contradiction:
Improvecapability to manage split transactionsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the contact information retrieval process into multiple independent steps: first retrieving contact info from local device memory, then querying the profile directory database for missing information, and finally obtaining additional missing info from other user devices. This segmentation allows the system to handle multi-user split transactions by breaking down the complex information retrieval task into manageable parts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The profile directory database serves as an intermediary component between user devices and transaction processing. It stores and manages user profiles including contact information, enabling the system to retrieve missing contact details for users not present in the initiator's device. This intermediary resolves the contradiction by providing a centralized information repository without requiring direct peer-to-peer communication between all users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If contact information is obtained from multiple sources, then transaction accuracy improves, but information retrieval time increases

Engineering Contradiction:
Improvetransaction accuracyVSAvoidinformation retrieval time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by first checking local device memory for contact information before querying external sources. This preliminary check quickly retrieves commonly used contact details without network latency. Only when information is missing does the system proceed to query the profile directory database or contact other user devices, thereby minimizing overall retrieval time while ensuring accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the profile directory database provides contact information to the transaction processing system, which then verifies and uses this information to complete the split transaction. This feedback loop ensures that accurate information is obtained while the system can optimize the process by learning from previous transactions and pre-caching frequently accessed contact information.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11328274B2Data processing system and method for managing electronic split transactions using user profiles
Publication Date: 2022.05.10 BANK OF AMERICA CORP
  • US11328274B2 patent drawing
  • US11328274B2 patent drawing
  • US11328274B2 patent drawing

AI summary

A system configured for managing a split transaction is disclosed. The system receives a request from a first user device associated with a first user to initiate a split transaction session between the first, second, and third users. A first user device associated with the first user includes second contact information associated with the second user. A second user device associated with the second user includes third contact information associated with the third user. The system receives an API request from the first user device to retrieve a third user profile. The system sends a request to the second user device to retrieve the third user profile. The second user device retrieves the third user profile and sends it to the system. The system retrieves the second and third user profiles and adds them to the split transaction session. The system conducts the split transaction session.