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

• US 10,616,188 B2
• Filed: 06/15/2018
• Issued: 04/07/2020
• Est. Priority Date: 03/19/2014
• Status: Active Grant

• Current Assignee: Bluefin Payment Systems LLC
• Original Assignee: Bluefin Payment Systems LLC
• Inventors: Barnett, Timothy William, Kasatkin, Alexander I., Miyata, Christopher Hozumi, Ruehle, Daniel
• Primary Examiner(s): Okeke, Izunna
• Application Number:
  US16/009,583
• Publication Number:
  US 20180367510A1
• Time in Patent Office: 662 Days
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/73 by creating or determining hardware identification, e.g. serial numbers
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 70/00 ICT specially adapted for the handling or processing of medical references
• CPC Class Codes: G16H 70/60 relating to pathologies
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0435 : wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/061 : for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 : based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3226 : using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04L 9/3234 : involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

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

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.