IP Library Granted Patent US 10,616,188
Granted Patent B2
US 10,616,188 · App. 16/009,583 · Granted Apr 7, 2020

Systems and methods for decryption as a service via a message queuing protocol

Inventors: Timothy William Barnett (Roswell, GA); Alexander I. Kasatkin (Alpharetta, GA); Christopher Hozumi Miyata (Tulsa, OK); Daniel Ruehle (Smyrna, GA)
Assignee: BLUEFIN PAYMENT SYSTEMS LLC
H04L63/0428G06F11/0766G06F16/23G06F16/2379G06F16/955G06F21/44G06F21/6227G06F21/6245G06F21/73G06Q20/223G06Q20/382G06Q20/401G06Q20/4014H04L9/0861H04L9/14H04L9/3226H04L9/3234H04L63/0435H04L63/061H04L63/08H04L63/0876H04L63/123G06F19/324G06Q10/10G06Q2220/00G16H10/60H04L63/20H04L2209/56H04L2209/80
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 10,616,188
App. No.
16/009,583
Granted
Apr 7, 2020
Kind
B2
Abstract

Systems and methods for decryption of payloads are disclosed herein. In various embodiments, systems and methods herein are configured for decrypting thousands of transactions per second. Further, in particular embodiments, the systems and methods herein are scalable, such that many thousands of transactions can be processed per second upon replicating particular architectural components.

Claims (35)

1. A computer-implemented method for fast decryption of one or more payloads, the method comprising providing a message queuing protocol operatively connected to a read-only database and a read/write database, the message queuing protocol configured for:

receiving, via at least one computing device, event notifications from the read-only database, wherein the event notifications each comprise one or more notifications regarding authentication of one or more received payloads;

authenticating, via the at least one computing device, the one or more received payloads based on data corresponding to the one or more notifications regarding the authentication of the one or more received payloads from each of the event notifications;

queuing, via the at least one computing device, the event notifications received from the read-only database; and

transmitting, via the at least one computing device, the event notifications to the read/write database upon determining that the read/write database is configured to accept event notifications.

2. The computer-implemented method of claim 1 , wherein the read-only database is a master read-only database operatively connected to at least one slave read-only database.

3. The computer-implemented method of claim 2 , further comprising providing a frontend server operatively connected to the at least one slave read-only database, the frontend server configured for receiving the one or more received payloads, wherein authenticating the one or more received payloads comprises comparing data included in the one or more received payloads with the data corresponding to the one or more notifications regarding the authentication of the one or more received payloads from each of the event notifications.

4. The computer-implemented method of claim 3 , further comprising providing a hardware security module, wherein the hardware security module is operatively connected to the frontend server and is for decrypting encrypted portions of the one or more received payloads.

5. The computer-implemented method of claim 4 , wherein the hardware security module is operatively connected to the frontend server via a hardware security module server.

6. The computer-implemented method of claim 1 , wherein the message queuing protocol is further configured for storing the event notifications upon determining the read/write database is not configured to accept event notifications.

7. The computer-implemented method of claim 1 , wherein upon determining the read/write database is configured to accept event notifications, transmitting the stored event notifications to the read/write database.

8. The computer-implemented method of claim 1 , wherein the read/write database is a P2PE manager.

9. The computer-implemented method of claim 1 , wherein the messaging queuing protocol is further configured for providing a backup for messages to be received by the read/write database.

10. The computer-implemented method of claim 1 , wherein the messaging queuing protocol is further configured for queuing write requests when the read/write database is offline.

11. A system for fast decryption of one or more payloads, the system comprising:

at least one computing device; and

a message queuing protocol operatively connected to a read-only database and a read/write database, the message queuing protocol configured to be implemented by the at least one computing device and configured for:

receiving event notifications from the read-only database, wherein the event notifications each comprise one or more notifications regarding authentication of one or more received payloads;

authenticating, via the at least one computing device, the one or more received payloads based on data corresponding to the one or more notifications regarding the authentication of the one or more received payloads from each of the event notifications;

queuing the event notifications received from the read-only database; and

transmitting the event notifications to the read/write database upon determining that the read/write database is configured to accept event notifications.

12. The system of claim 11 , wherein the messaging queuing protocol is further configured for providing a backup for messages to be received by the read/write database.

13. The system of claim 11 , wherein the messaging queuing protocol is further configured for queuing write requests when the read/write database is offline.

14. The system of claim 11 , wherein the read-only database is a master read-only database operatively connected to at least one slave read-only database.

15. The system of claim 11 , wherein the message queuing protocol is further configured for storing the event notifications upon determining the read/write database is not configured to accept event notifications.

16. A non-transitory computer-readable medium embodying a program for fast decryption of one or more payloads, the program, when executed by at least one computing devices, causes the at least one computing device to:

provide a message queuing protocol operatively connected to a read-only database and a read/write database, the message queuing protocol configured for:

receiving event notifications from the read-only database, wherein the event notifications each comprise one or more notifications regarding authentication of one or more received payloads;

authenticating, via the at least one computing device, the one or more received payloads based on data corresponding to the one or more notifications regarding the authentication of the one or more received payloads from each of the event notifications;

queuing the event notifications received from the read-only database; and

transmitting the event notifications to the read/write database upon determining that the read/write database is configured to accept event notifications.

17. The non-transitory computer-readable medium of claim 16 , wherein the messaging queuing protocol is further configured for providing a backup for messages to be received by the read/write database.

18. The non-transitory computer-readable medium of claim 16 , wherein the messaging queuing protocol is further configured for queuing write requests when the read/write database is offline.

19. The non-transitory computer-readable medium of claim 16 , wherein the read-only database is a master read-only database operatively connected to at least one slave read-only database.

20. The non-transitory computer-readable medium of claim 16 , wherein the message queuing protocol is further configured for storing the event notifications upon determining the read/write database is not configured to accept event notifications.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded Jun 7, 2022
From: GOLDMAN SACHS SPECIALTY LENDING GROUP, L.P.
To: BLUEFIN PAYMENT SYSTEMS LLC
Reel/Frame 060119/0857 →
SECURITY INTEREST Recorded Jun 6, 2022
From: BLUEFIN PAYMENT SYSTEMS LLC
To: TRUIST BANK
Reel/Frame 060105/0919 →
SECURITY INTEREST Recorded Sep 27, 2019
From: BLUEFIN PAYMENT SYSTEMS LLC
To: GOLDMAN SACHS SPECIALTY LENDING GROUP, L.P.
Reel/Frame 050509/0785 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2018
From: BARNETT, TIMOTHY WILLIAM; KASATKIN, ALEXANDER I.; MIYATA, CHRISTOPHER HOZUMI; RUEHLE, DANIEL
To: BLUEFIN PAYMENT SYSTEMS LLC
Reel/Frame 046302/0670 →
Continuity (10)
Continuation 15603976 · May 24, 2017
Continuation 15386707 · Dec 21, 2016
Continuation 15218332 · Jul 25, 2016
Continuation 14663238 · Mar 19, 2015
Continuation In Part 14591223 · Jan 7, 2015
Continuation In Part 14591171 · Jan 7, 2015
Continuation In Part 14591218 · Jan 7, 2015
Continuation In Part PCTUS2015010405 · Jan 7, 2015
Provisional Application 61955739 · Mar 19, 2014
Related Publication 20180367510A1 · Dec 20, 2018