IP Library › Granted Patent US 12,231,408
Granted Patent B2
US 12,231,408 · App. 17/576,412 · Granted Feb 18, 2025

Secure data transfer request routing for peer-to-peer services

Inventors: Richard S. Scot (Huntersville, NC); James J. Siekman (Charlotte, NC); Neal Aaron Slensker (Fort Mill, SC); Basil C. Doyle (Chicago, IL)
Assignee: Bank of America Corporation
H04L63/04H04L45/308H04L67/306H04L67/63
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,231,408
App. No.
17/576,412
Granted
Feb 18, 2025
Kind
B2
Abstract

A device configured to receive a data transfer initiation request from a first user and to identify a user profile that is associated with a first user identifier for the first user. The device is further configured to obtain an account number and a routing number for the first user from the user profile. The device is further configured to obtain routing instructions for a service provider based on a service provider identifier. The device is further configured to generate a data transfer request that includes the account number for the first user, the routing number for the first user, a second user identifier for a second user, a data type identifier, and a data transfer type identifier. The device is further configured to send the data transfer request to the service provider in accordance with the routing instructions for the service provider.

Claims (83)

1. A data routing device, comprising:

a memory operable to store:

user profiles, wherein:

each user profile is associated with a user identifier for a user; and

each user profile is associated with an account number and a routing number; and

routing information for a plurality of service providers, wherein:

each service provider is configured to provide a peer-to-peer data transfer service:

each service provider is associated with a service provider identifier; and

each service provider identifier is linked with routing instructions for sending messages to a network device associated with a service provider; and

a processor operably coupled to the memory, configured to:

receive a data transfer initiation request from a first user, wherein the data transfer initiation request comprises:

a data type identifier, wherein the data type identifier identifies a type of data to be transferred;

a first user identifier for the first user;

a second user identifier for a second user;

a service provider identifier for a service provider; and

a data transfer type identifier, wherein the data transfer type identifier indicates one of a data transfer from the first user to the second user or a data transfer from the second user to the first user;

identify a user profile that is associated with the first user identifier;

obtain a first account number for the first user that is associated with the user profile;

obtain a first routing number for the first user that is associated with the user profile;

utilize the service provider identifier as a search token to identify the service provider within the routing information for the plurality of service providers in the memory;

utilize the service provider identifier as the search token to obtain routing instructions for a first network device that is associated with the service provider from the routing information for the plurality of service providers in the memory;

generate a data transfer request that comprises:

the first account number for the first user;

the first routing number for the first user;

the second user identifier for the second user;

the data type identifier; and

the data transfer type identifier;

send the data transfer request to the first network device that is associated with the service provider in accordance with the routing instructions for the service provider, wherein sending the data transfer request initiates a data transfer between the first user and the second user.

2. The device of claim 1 , wherein the second user identifier comprises a phone number for the second user.

3. The device of claim 1 , wherein the second user identifier comprises an email address for the second user.

4. The device of claim 1 , wherein the second user identifier comprises an alphanumeric code for the second user.

5. The device of claim 1 , wherein the data type identifier further identifies an amount of data to be transferred.

6. The device of claim 1 , wherein the data transfer type identifier indicates a data transfer from the second user to the first user.

7. The device of claim 1 , wherein the data transfer type identifier indicates a data transfer from the first user to the second user.

8. A data routing method, comprising:

receiving a data transfer initiation request from a first user, wherein the data transfer initiation request comprises:

a data type identifier, wherein the data type identifier identifies a type of data to be transferred;

a first user identifier for the first user;

a second user identifier for a second user;

a service provider identifier for a service provider, wherein the service provider is configured to provide a peer-to-peer data transfer service; and

a data transfer type identifier, wherein the data transfer type identifier indicates one of a data transfer from the first user to the second user or a data transfer from the second user to the first user;

identifying a user profile from among a plurality of user profiles that is associated with the first user identifier, wherein each user profile is associated with an account number and a routing number;

obtaining a first account number for the first user that is associated with the user profile;

obtaining a first routing number for the first user that is associated with the user profile;

utilizing the service provider identifier as a search token to identify the service provider within routing information for a plurality of service providers;

utilizing the service provider identifier as the search token to obtain routing instructions for a first network device that is associated with the service provider from the routing information for the plurality of service providers, wherein the routing information comprises routing instructions for sending messages to the first network device that is associated with the service provider;

generating a data transfer request that comprises;

the first account number for the first user;

the first routing number for the first user;

the second user identifier for the second user;

the data type identifier; and

the data transfer type identifier;

sending the data transfer request to the first network device that is associated with the service provider in accordance with the routing instructions for the service provider, wherein sending the data transfer request initiates a data transfer between the first user and the second user.

9. The method of claim 8 , wherein the second user identifier comprises a phone number for the second user.

10. The method of claim 8 , wherein the second user identifier comprises an email address for the second user.

11. The method of claim 8 , wherein the second user identifier comprises an alphanumeric code for the second user.

12. The method of claim 8 , wherein the data type identifier further identifies an amount of data to be transferred.

13. The method of claim 8 , wherein the data transfer type identifier indicates a data transfer from the second user to the first user.

14. The method of claim 8 , wherein the data transfer type identifier indicates a data transfer from the first user to the second user.

15. A non-transitory computer-readable medium storing instructions that when executed by a processor cause the processor to:

receive a data transfer initiation request from a first user, wherein the data transfer comprises:

a data type identifier, wherein the data type identifier identifies a type of data to be transferred;

a first user identifier for the first user;

a second user identifier for a second user;

a service provider identifier for a service provider, wherein the service provider is configured to provide a peer-to-peer data transfer service; and

a data transfer type identifier, wherein the data transfer type identifier indicates one of a data transfer from the first user to the second user or a data transfer from the second user to the first user;

identify a user profile from among a plurality of user profiles that is associated with the first user identifier, wherein each user profile is associated with an account number and a routing number;

obtain a first account number for the first user that is associated with the user profile;

obtain a first routing number for the first user that is associated with the user profile;

utilize the service provider identifier as a search token to identify the service provider within routing information for a plurality of service providers;

utilize the service provider identifier as the search token to obtain routing instructions for a first network device that is associated with the service provider from the routing information for the plurality of service providers, wherein the routing information comprises routing instructions for sending messages to the first network device that is associated with the service provider;

generate a data transfer request that comprises:

the first account number for the first user;

the first routing number for the first user;

the second user identifier for the second user;

the data type identifier; and

the data transfer type identifier;

send the data transfer request to the first network device that is associated with the service provider in accordance with the routing instructions for the service provider, wherein sending the data transfer request initiates a data transfer between the first user and the second user.

16. The non-transitory computer-readable medium of claim 15 , wherein the second user identifier comprises a phone number for the second user.

17. The non-transitory computer-readable medium of claim 15 , wherein the second user identifier comprises an email address for the second user.

18. The non-transitory computer-readable medium of claim 15 , wherein the data type identifier further identifies an amount of data to be transferred.

19. The non-transitory computer-readable medium of claim 15 , wherein the data transfer type identifier indicates a data transfer from the second user to the first user.

20. The non-transitory computer-readable medium of claim 15 , wherein the data transfer type identifier indicates a data transfer from the first user to the second user.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 14, 2022
From: SCOT, RICHARD S.; SIEKMAN, JAMES J.; SLENSKER, NEAL AARON; DOYLE, BASIL C.
To: BANK OF AMERICA CORPORATION
Reel/Frame 058662/0316 →
Continuity (1)
Related Publication 20230231832A1 · Jul 20, 2023
References Cited (43)
US 5243592A · Perlman et al. · 1993 [cited by applicant]
US 5367698A · Webber et al. · 1994 [cited by applicant]
US 5550976A · Henderson et al. · 1996 [cited by applicant]
US 5586260A · Hu · 1996 [cited by applicant]
US 6065062A · Periasamy et al. · 2000 [cited by applicant]
US 6260072B1 · Rodriguez-Moral · 2001 [cited by applicant]
US 6742028B1 · Wang et al. · 2004 [cited by applicant]
US 6928476B2 · Bucher · 2005 [cited by applicant]
US 6978294B1 · Adams et al. · 2005 [cited by applicant]
US 7127613B2 · Pabla et al. · 2006 [cited by applicant]
US 7275102B2 · Yeager et al. · 2007 [cited by applicant]
US 7363343B2 · Bucher · 2008 [cited by applicant]
US 7529785B1 · Spertus et al. · 2009 [cited by applicant]
US 7664861B2 · Guntupalli et al. · 2010 [cited by applicant]
US 7782866B1 · Walsh et al. · 2010 [cited by applicant]
US 11599885B1 · Allen · 2023 [cited by examiner]
US 11924159B2 · Nair · 2024 [cited by examiner]
US 11961055B1 · Bhatt · 2024 [cited by examiner]
US 20020007350A1 · Yen · 2002 [cited by applicant]
US 20020049760A1 · Scott et al. · 2002 [cited by applicant]
US 20020073204A1 · Dutta et al. · 2002 [cited by applicant]
US 20020098849A1 · Bloebaum et al. · 2002 [cited by applicant]
US 20020103998A1 · Debruine · 2002 [cited by applicant]
US 20020138552A1 · Debruine et al. · 2002 [cited by applicant]
US 20020138744A1 · Schleicher et al. · 2002 [cited by applicant]
US 20020178261A1 · Chang et al. · 2002 [cited by applicant]
US 20020188735A1 · Needham et al. · 2002 [cited by applicant]
US 20020198930A1 · Jones et al. · 2002 [cited by applicant]
US 20030009518A1 · Harrow et al. · 2003 [cited by applicant]
US 20030009586A1 · Harrow et al. · 2003 [cited by applicant]
US 20030009587A1 · Harrow et al. · 2003 [cited by applicant]
US 20030018712A1 · Harrow et al. · 2003 [cited by applicant]
US 20030115251A1 · Fredrickson et al. · 2003 [cited by applicant]
US 20030120699A1 · Hostetter et al. · 2003 [cited by applicant]
US 20030163702A1 · Vigue et al. · 2003 [cited by applicant]
US 20040019640A1 · Bartram et al. · 2004 [cited by applicant]
US 20040042403A1 · Xu et al. · 2004 [cited by applicant]
US 20040098502A1 · Xu et al. · 2004 [cited by applicant]
US 20050185636A1 · Bucher · 2005 [cited by applicant]
US 20060015562A1 · Kilian-Kehr et al. · 2006 [cited by applicant]
US 20070106805A1 · Marples et al. · 2007 [cited by applicant]
US 20190019174A1 · Mohsenzadeh · 2019 [cited by examiner]
US 20230134689A1 · Le · 2023 [cited by examiner]