Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
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.
This invention relates to computer-implemented systems and methods for efficiently decrypting data payloads. The problem addressed is the need for fast decryption, particularly in scenarios involving authentication and data storage. The core of the invention is a method that utilizes a message queuing protocol to manage event notifications. This protocol is operatively connected to two databases: a read-only database and a read/write database. The system receives event notifications from the read-only database, which contain information related to the authentication of received payloads. A computing device then uses this notification data to authenticate the payloads. Crucially, the event notifications are first queued. Before transmitting these queued notifications to the read/write database, the system verifies that the read/write database is ready to accept them. This queuing and conditional transmission mechanism is designed to optimize the decryption process by ensuring efficient handling of authentication events and data flow between the databases.
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.
A system and method for managing read-only databases in a distributed computing environment addresses the challenge of efficiently distributing and synchronizing read-only data across multiple database instances. The invention involves a master read-only database that is operatively connected to at least one slave read-only database. The master database serves as the primary source of data, while the slave databases replicate the data from the master to ensure consistency and availability. This architecture allows for load balancing, redundancy, and improved performance by distributing read operations across multiple database instances. The system ensures that all slave databases maintain an up-to-date copy of the data from the master, enabling high availability and fault tolerance. The method may include mechanisms for synchronizing data between the master and slave databases, such as periodic updates or real-time replication, to ensure data consistency. This approach is particularly useful in applications requiring high read throughput, such as content delivery networks, analytics platforms, or distributed caching systems. The invention optimizes resource utilization and minimizes latency by offloading read operations from the master database to the slave databases, thereby enhancing overall system efficiency.
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.
This invention relates to a distributed database system designed to enhance data consistency and authentication in a high-availability environment. The system includes a primary database and at least one slave read-only database, where the primary database generates event notifications upon receiving payloads. These notifications are distributed to the slave databases, which store data corresponding to the payloads. A frontend server is operatively connected to the slave databases and receives the payloads. The frontend server authenticates the payloads by comparing their included data with the data stored in the slave databases, which was derived from the event notifications. This ensures that the payloads are validated against the most recent and consistent data across the distributed system. The method improves reliability by leveraging multiple read-only databases to verify payload authenticity, reducing the risk of data corruption or unauthorized access. The system is particularly useful in applications requiring high availability and strong consistency, such as financial transactions or distributed ledger systems.
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.
A computer-implemented method involves securely processing data payloads in a distributed system, particularly addressing challenges related to data encryption and secure access control. The method includes receiving one or more encrypted payloads from a client device, where each payload contains encrypted data segments. A frontend server processes these payloads, managing access control and authentication to ensure only authorized users or systems can interact with the data. The method further integrates a hardware security module (HSM) operatively connected to the frontend server. The HSM is responsible for decrypting the encrypted portions of the received payloads, ensuring that sensitive data remains protected during processing. This approach enhances security by offloading decryption tasks to a dedicated hardware component, reducing the risk of exposure to software-based vulnerabilities. The system may also include additional features such as payload validation, secure storage, and audit logging to maintain data integrity and compliance with security standards. The overall solution is designed for environments requiring high levels of data protection, such as financial transactions, healthcare records, or enterprise data management.
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.
A computer-implemented method involves securing data transmission between a frontend server and a hardware security module (HSM) using an intermediary hardware security module server. The HSM is a specialized cryptographic device designed to protect sensitive data, such as encryption keys, from unauthorized access. The frontend server handles user interactions and data processing but lacks the secure environment needed for cryptographic operations. The hardware security module server acts as a bridge, facilitating secure communication between the frontend server and the HSM. This setup ensures that cryptographic operations, such as key generation, encryption, and decryption, are performed within the HSM, which is physically and logically isolated from the frontend server. The method enhances security by centralizing cryptographic functions in a dedicated, tamper-resistant device while allowing the frontend server to manage general data processing tasks. This approach mitigates risks associated with storing sensitive cryptographic material in less secure environments, such as general-purpose servers. The hardware security module server may also handle protocol translation, load balancing, or failover management to ensure reliable and secure communication between the frontend server and the HSM. This architecture is particularly useful in applications requiring high levels of data protection, such as financial transactions, identity verification, and secure communications.
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.
This invention relates to a computer-implemented method for managing event notifications in a system where a read/write database may temporarily be unavailable to receive them. The method involves using a message queuing protocol to handle event notifications when the database is unable to process them. The protocol is designed to store these notifications temporarily until the database becomes available again, ensuring no data loss occurs during periods of unavailability. The system monitors the database's status and dynamically adjusts the handling of event notifications based on its ability to accept them. This approach improves system reliability by preventing the loss of critical event data when the database is offline or overloaded. The method ensures seamless operation by buffering notifications in a queue until the database can process them, maintaining data integrity and system performance. The queuing protocol may include features such as prioritization, retry mechanisms, or expiration policies to manage the stored notifications efficiently. This solution is particularly useful in distributed systems where database availability may fluctuate due to network issues, maintenance, or high load conditions.
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.
A system and method for managing event notifications in a database environment addresses the challenge of efficiently handling and processing event notifications in distributed database systems. The method involves monitoring a read/write database to determine whether it is configured to accept event notifications. When the database is ready to receive notifications, the system transmits stored event notifications to the database. This ensures that event notifications are processed in a timely manner, reducing latency and improving system performance. The method may also include storing event notifications in a buffer or queue when the database is not ready to accept them, ensuring that no notifications are lost during periods of high load or temporary unavailability. The system may further include mechanisms for prioritizing notifications based on urgency or importance, ensuring critical events are processed first. By dynamically adjusting the transmission of notifications based on the database's readiness, the method optimizes resource utilization and maintains data consistency across distributed systems. This approach is particularly useful in real-time applications where timely processing of events is critical, such as financial transactions, IoT device monitoring, or distributed logging systems.
8. The computer-implemented method of claim 1 , wherein the read/write database is a P2PE manager.
A computer-implemented method involves managing a read/write database that functions as a Point-to-Point Encryption (P2PE) manager. P2PE systems are used to secure payment card data by encrypting it at the point of interaction, such as a payment terminal, before it is transmitted or stored. The method includes processing data transactions through the P2PE manager, which ensures that sensitive payment information is encrypted before being stored in the database. This encryption prevents unauthorized access to the data, even if the database is compromised. The P2PE manager may also handle decryption when authorized access is required, such as for legitimate payment processing. The system ensures compliance with security standards like PCI DSS by minimizing exposure of unencrypted cardholder data. The method may further include validating encryption keys, monitoring transaction integrity, and logging security events to maintain audit trails. By integrating P2PE functionality directly into the database management system, the method enhances security and simplifies compliance for organizations handling payment transactions.
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.
This invention relates to a computer-implemented method for managing message queuing in a distributed system, specifically addressing the challenge of ensuring message reliability and availability in environments where a read/write database may experience failures or downtime. The method involves a messaging queuing protocol designed to handle message transmission between components, with an additional feature for providing backup storage for messages intended for the read/write database. This backup mechanism ensures that messages are not lost if the primary database becomes unavailable, allowing the system to recover and process messages once the database is restored. The protocol may include mechanisms for detecting database failures, temporarily storing messages in a backup queue, and resuming message delivery once the database is operational again. The system may also include error handling and retry logic to manage message delivery attempts, ensuring that messages are eventually processed even in the presence of transient or persistent database issues. The overall solution improves system resilience by preventing message loss and maintaining data consistency in distributed messaging environments.
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.
A computer-implemented method involves managing data access in a distributed system where a read/write database may experience downtime. The method addresses the challenge of maintaining data consistency and availability when the primary database is offline. It employs a messaging queuing protocol to handle write requests during such outages. When the read/write database is unavailable, the protocol queues incoming write requests instead of rejecting them, ensuring no data loss. Once the database comes back online, the queued requests are processed in sequence, restoring normal operation. This approach prevents data corruption and ensures that all write operations are eventually executed, even if they occur during downtime. The system may also include mechanisms to prioritize or batch queued requests based on system load or other criteria. The method is particularly useful in high-availability systems where uninterrupted data access is critical, such as financial services, healthcare, or cloud computing environments. By decoupling write operations from immediate database access, the system improves resilience and reliability.
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.
The system accelerates decryption of encrypted payloads by leveraging a message queuing protocol to manage authentication events between read-only and read/write databases. The technology addresses inefficiencies in traditional decryption processes, where delays occur due to direct database interactions or lack of synchronization between authentication and decryption steps. The system includes at least one computing device that implements the message queuing protocol to handle event notifications from the read-only database. These notifications contain authentication data for received payloads, which the computing device uses to verify the payloads. The system queues these notifications and transmits them to the read/write database only when the database is ready to accept them, ensuring smooth and timely decryption. This approach minimizes latency and improves system performance by decoupling authentication events from immediate database writes, allowing for scalable and efficient payload processing. The read-only database provides authenticated payload data, while the read/write database stores processed results, with the queuing protocol acting as an intermediary to manage data flow.
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.
A system for managing message processing in a distributed computing environment addresses the challenge of ensuring reliable message delivery and data consistency in systems where messages are exchanged between components. The system includes a messaging queuing protocol that facilitates communication between a read/write database and other system components. The protocol is designed to handle message queuing, ensuring that messages are properly routed and processed. In addition to basic queuing functionality, the protocol provides a backup mechanism for messages intended for the read/write database. This backup feature ensures that messages are not lost in the event of a failure or disruption in the primary message processing path. The backup mechanism may involve storing messages in an alternative storage system or queue until they can be successfully delivered to the read/write database. This redundancy improves system reliability and data integrity by preventing message loss during operational issues. The system may also include additional components, such as message producers and consumers, that interact with the messaging queuing protocol to send and retrieve messages. The overall architecture ensures that messages are processed efficiently while maintaining high availability and fault tolerance.
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.
A system for managing database operations includes a messaging queuing protocol that facilitates communication between a read/write database and one or more client devices. The system ensures data consistency and availability by coordinating read and write operations across distributed components. The messaging queuing protocol is designed to handle high-throughput data transactions while maintaining reliability. In scenarios where the read/write database is offline, the protocol is configured to queue write requests temporarily, preventing data loss and ensuring that pending operations are processed once the database becomes available again. This queuing mechanism allows the system to maintain operational continuity even during temporary disruptions, improving fault tolerance and system resilience. The protocol may also include features for prioritizing queued requests, retry mechanisms, and status monitoring to optimize performance and user experience. The system is particularly useful in environments requiring high availability and low-latency data access, such as cloud-based applications, financial systems, or real-time analytics platforms.
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.
A system for managing read-only databases in a distributed computing environment addresses the need for efficient data access and consistency across multiple database instances. The system includes a master read-only database that is operatively connected to at least one slave read-only database. The master database serves as the primary source of data, while the slave databases replicate the data from the master to ensure consistency and availability. This architecture allows for load balancing, as read operations can be distributed across multiple slave databases, reducing the load on the master database and improving overall system performance. The system ensures that all slave databases maintain an up-to-date copy of the data from the master, either through periodic synchronization or real-time replication, depending on the implementation. This setup is particularly useful in scenarios where high availability and fault tolerance are critical, such as in large-scale web applications or financial systems where data integrity and quick access are essential. The system may also include mechanisms to handle failover scenarios, where a slave database can temporarily take over the role of the master if the primary master becomes unavailable. This ensures continuous data access and minimizes downtime. The system may further include monitoring and management tools to track the status of the databases, detect inconsistencies, and trigger corrective actions as needed.
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.
A system for managing event notifications in a distributed computing environment addresses the challenge of ensuring reliable delivery of notifications when a read/write database is unavailable. The system includes a message queuing protocol that temporarily stores event notifications when the database cannot accept them, preventing data loss during outages or high-load conditions. The queuing protocol dynamically monitors the database's availability and automatically resumes notification delivery once the database is operational. This ensures continuous system functionality and data integrity. The system also includes a notification service that generates and distributes event notifications to subscribed clients, and a database interface that manages communication between the notification service and the database. The queuing protocol may use persistent storage to retain notifications until successful delivery, supporting fault tolerance and scalability in distributed systems. This approach enhances reliability in applications requiring real-time event processing, such as financial transactions, IoT device monitoring, or collaborative software systems.
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.
The invention relates to a system for fast decryption and processing of encrypted payloads in a distributed computing environment. The system addresses the challenge of efficiently authenticating and decrypting payloads while ensuring data consistency across multiple databases. A message queuing protocol connects a read-only database and a read/write database, facilitating secure and synchronized data processing. The protocol receives event notifications from the read-only database, each containing authentication data for one or more encrypted payloads. The system authenticates the payloads using this data and queues the notifications. Once the read/write database is ready to accept new data, the queued notifications are transmitted, ensuring timely decryption and processing without overloading the system. This approach improves performance by decoupling authentication and decryption operations from database write operations, reducing latency and enhancing scalability. The system is particularly useful in environments requiring high-speed decryption of encrypted data while maintaining data integrity across distributed storage systems.
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.
The invention relates to a system for managing message queuing in a distributed computing environment, particularly for ensuring reliable message delivery to a read/write database. The system addresses the challenge of maintaining data integrity and availability in scenarios where the primary database may experience failures or disruptions. The messaging queuing protocol is designed to handle message transmission between components, ensuring that messages are not lost even if the database is temporarily unavailable. The protocol includes a backup mechanism that stores messages intended for the read/write database, allowing them to be resent or processed later when the database is operational again. This backup functionality prevents data loss and ensures that all messages are eventually delivered, even in the presence of transient failures. The system may also include additional features such as message prioritization, error handling, and recovery procedures to further enhance reliability. The overall goal is to provide a robust messaging infrastructure that supports high availability and fault tolerance in distributed systems.
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.
A system and method for managing data storage and retrieval in a distributed computing environment addresses the challenge of maintaining data consistency and availability across multiple nodes. The system includes a read/write database that stores data and a messaging queuing protocol that facilitates communication between nodes. The protocol ensures that write requests are processed in a consistent order, preventing data corruption or conflicts. When the read/write database is offline, the messaging queuing protocol queues incoming write requests, preserving them until the database is back online. This prevents data loss and ensures that all write operations are eventually processed in the correct sequence. The system also includes a read-only database that provides fast access to frequently requested data, reducing the load on the primary read/write database. The messaging queuing protocol coordinates between the read/write and read-only databases to maintain synchronization. This approach improves system reliability, scalability, and performance by efficiently managing data consistency and availability in distributed environments.
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.
A system and method for managing database access in a distributed computing environment addresses the challenge of ensuring data consistency and availability across multiple nodes while minimizing latency and resource overhead. The invention involves a master read-only database that is operatively connected to at least one slave read-only database. The master database serves as the primary source of data, while the slave databases replicate the data from the master to provide redundant access points. This architecture improves fault tolerance and load balancing by distributing read operations across multiple slave databases, reducing the burden on the master database. The system ensures data consistency by synchronizing updates from the master to the slaves, either in real-time or through periodic synchronization. The invention is particularly useful in high-traffic applications where low-latency read operations are critical, such as content delivery networks, financial systems, or large-scale web services. By decoupling read and write operations, the system enhances performance and scalability while maintaining data integrity. The solution is implemented via a non-transitory computer-readable medium containing instructions for executing the database management processes.
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.
A system and method for managing event notifications in a distributed computing environment involves a message queuing protocol that facilitates communication between a read/write database and one or more client devices. The system addresses the challenge of ensuring reliable event notification delivery when the database is temporarily unavailable or unable to process incoming notifications. The message queuing protocol is configured to store event notifications in a queue when the read/write database is not configured to accept them, preventing data loss and ensuring notifications are processed once the database becomes available. The protocol may also include mechanisms for prioritizing, filtering, or batching notifications to optimize performance and resource usage. The system may further include a notification service that monitors the database's status and dynamically adjusts the queuing behavior based on availability, load, or other operational conditions. This approach enhances system reliability and ensures timely delivery of event notifications even under fluctuating database conditions. The solution is particularly useful in high-availability environments where uninterrupted communication between components is critical.
Unknown
April 7, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.