Systems and methods are disclosed for secure transmission of high-priority computer server event notifications. One method comprises obtaining a new computer server event to report; generating a first notification message pertaining to the computer server event; generating a second notification message pertaining to the computer server event and to the delivery of the first notification message; storing the first notification message; storing the second notification message; and transmitting the first notification message to a partner over a computer network.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for secure transmission of high-priority computer server event notifications, the method comprising: receiving server event information from a notification source; performing a create event operation based on the server event information; generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message; transmitting the delayed delivery message to a queue client; transmitting the high-priority notification message to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); determining whether an acknowledgment message is received from the partner system; de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system; and transmitting the delayed delivery message to a downstream system, wherein the downstream system includes at least one of: a consumer credit management service provider system or a consumer risk management service provider system.
2. The method of claim 1 , wherein the one or more data components collected via the create event operation comprise one or more of: a notification identifier (ID), a notification type, and notification details.
A system and method for managing data components in a notification system involves collecting and processing data during a create event operation. The system captures specific data components associated with notifications, including a notification identifier (ID), notification type, and notification details. These components are used to categorize, track, and manage notifications within the system. The notification ID uniquely identifies each notification, the notification type defines the category or purpose of the notification, and the notification details provide additional context or content. The collected data components enable efficient notification handling, such as filtering, prioritization, and routing, ensuring that notifications are processed and delivered accurately. This approach enhances the system's ability to manage notifications in a structured and organized manner, improving overall performance and user experience. The method ensures that all relevant notification data is captured during creation, facilitating seamless integration with other system processes.
3. The method of claim 1 , wherein the delayed delivery message indicates a notification error.
A system and method for managing message delivery in communication networks addresses the problem of ensuring reliable and timely notification of message delivery status to users. The invention provides a mechanism for generating and transmitting delayed delivery messages when a primary notification fails, ensuring users are informed of potential issues. The delayed delivery message includes an indication of a notification error, allowing recipients to recognize that the original message may not have been successfully delivered or acknowledged. The system monitors message transmission and, upon detecting a failure in the primary notification process, triggers the generation of a secondary delayed message. This secondary message is formatted to explicitly signal a notification error, distinguishing it from standard delivery confirmations. The method involves tracking message delivery attempts, identifying failures, and initiating corrective actions to enhance communication reliability. The invention is particularly useful in environments where real-time delivery confirmation is critical, such as in enterprise messaging, healthcare, or financial services, where timely and accurate notifications are essential for operational efficiency and compliance. The delayed error notification ensures users are aware of potential delivery issues, enabling them to take appropriate follow-up actions.
4. The method of claim 1 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
A system and method for managing high-priority notification messages in a communication network addresses the challenge of efficiently conveying critical information in real-time scenarios. The invention enhances notification systems by structuring high-priority messages to include detailed, actionable data. These messages may contain an event type to categorize the notification, case information to provide context, control information for system adjustments, device information to identify relevant hardware, contact information for responsible parties, transaction details for financial or operational updates, and a variable list for additional customizable data. This structured approach ensures that recipients receive comprehensive, organized information, improving response times and decision-making in time-sensitive situations. The method supports dynamic message composition, allowing systems to tailor notifications based on the specific requirements of the event or user. By integrating multiple data types into a single notification, the invention reduces the need for follow-up communications and minimizes errors caused by fragmented information. This solution is particularly valuable in industries such as healthcare, finance, and emergency response, where timely and accurate notifications are critical. The system may be implemented in software, hardware, or a combination of both, ensuring flexibility across different deployment environments.
5. The method of claim 4 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
A system and method for managing high-priority notification messages in a communication network addresses the challenge of efficiently conveying critical alerts while ensuring compliance with reporting requirements. The invention involves generating and transmitting high-priority notification messages that include detailed status information, such as whether the message has been successfully delivered or acknowledged by the recipient. Additionally, the notification message contains metadata indicating whether reporting to a downstream system has been opted out, allowing for better tracking and compliance monitoring. This ensures that critical alerts are not only delivered promptly but also properly logged and reported according to system policies. The method supports dynamic adjustments to notification handling based on real-time conditions, such as network congestion or recipient availability, to optimize delivery reliability. By integrating opt-out reporting information directly into the notification message, the system provides a unified and transparent way to manage compliance and reporting obligations without requiring separate tracking mechanisms. This approach enhances operational efficiency and reduces the risk of missed or improperly reported alerts in mission-critical applications.
6. The method of claim 1 , further comprising: removing the delayed delivery message from a queue in communication with the queue client based on determining that the acknowledgment is received from the partner system.
This invention relates to message processing systems, specifically methods for handling delayed delivery messages in a queue-based communication system. The problem addressed is ensuring reliable message delivery and proper queue management when acknowledgments are received from a partner system. The method involves monitoring a queue that stores delayed delivery messages, where these messages are intended for a partner system but are temporarily held due to delivery constraints. A queue client interacts with this queue to manage message flow. When the partner system successfully processes a delayed message, it sends an acknowledgment back to the system. Upon receiving this acknowledgment, the method removes the corresponding message from the queue to prevent redundant processing or storage. This ensures that the queue remains clean and efficient, avoiding unnecessary retention of already processed messages. The system may also include mechanisms to track message status and handle cases where acknowledgments are not received within a specified timeframe, ensuring robust message delivery. The invention improves system reliability and performance by dynamically managing message retention based on acknowledgment feedback.
7. The method of claim 1 , further comprising: determining whether an update regarding the server event is received from the partner system; de-queuing the delayed delivery message based on determining that the update is not received from the partner system; and transmitting the delayed delivery message to a downstream system.
This invention relates to message processing systems that handle server events and delayed message delivery in distributed computing environments. The problem addressed is ensuring reliable and timely delivery of messages while managing dependencies on external partner systems. The system monitors for updates from a partner system regarding a server event. If no update is received within a specified time, the system de-queues a previously delayed message and transmits it to a downstream system. This mechanism prevents indefinite delays and ensures message flow continues even when partner system responses are delayed or missing. The method involves tracking server events, managing message queues, and dynamically adjusting delivery based on external system behavior. The system may also include features for initial message queuing, delay period configuration, and event tracking to support this functionality. The solution improves system reliability by avoiding message stagnation and ensuring downstream systems receive critical data in a timely manner.
8. The method of claim 1 , wherein the delayed delivery message is transmitted to the downstream system based on a service level agreement.
A system and method for managing message delivery in a distributed computing environment addresses the challenge of ensuring reliable and timely transmission of messages between systems, particularly when downstream systems may be temporarily unavailable or overloaded. The invention provides a mechanism to store messages temporarily when immediate delivery is not possible, then forward them once conditions permit, while adhering to predefined service level agreements (SLAs). The method involves intercepting messages intended for a downstream system, determining whether immediate delivery is feasible, and if not, storing the messages in a buffer or queue. The system monitors the downstream system's availability and performance metrics, such as response times or error rates, to assess when conditions are suitable for retransmission. When the downstream system is ready to receive messages, the stored messages are transmitted in accordance with the agreed-upon SLA, which may specify delivery time windows, priority levels, or other constraints. This approach ensures that messages are not lost during temporary disruptions while maintaining compliance with service agreements. The system may also include features for message prioritization, retry logic, and notification of delivery failures to upstream systems. The invention is particularly useful in enterprise environments where uninterrupted communication between systems is critical, such as in financial transactions, supply chain management, or healthcare data exchange.
9. A system for secure transmission of high-priority computer server event notifications, the system comprising: one or more processors; and one or more computer readable media comprising instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving server event information from a notification source; performing a create event operation based on the server event information; generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message; transmitting the delayed delivery message to a queue client; transmitting the high-priority notification message to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); determining whether an acknowledgment message is received from the partner system; de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system; and transmitting the delayed delivery message to a downstream system, wherein the downstream system includes at least one of: a consumer credit management service provider system or a consumer risk management service provider system.
This system addresses the challenge of securely transmitting high-priority event notifications from computer servers while ensuring reliable delivery. The system processes server event data from a notification source, creating an event record and generating two types of messages: a high-priority notification and a delayed delivery message. The high-priority notification is transmitted to a partner system using a secure protocol, such as message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS). If the partner system does not acknowledge receipt, the delayed delivery message is retrieved from a queue and sent to a downstream system, which may include a consumer credit or risk management service provider. This ensures critical notifications are either securely delivered or redirected for fallback processing, improving system reliability and security in event-driven architectures. The system prioritizes real-time transmission while maintaining failover mechanisms for uninterrupted service.
10. The system of claim 9 , wherein the one or more data components collected via the create event operation comprise one or more of: a notification identifier (ID), a notification type, and notification details.
A system for managing data components in a notification system collects and processes information during a create event operation. The system is designed to handle notifications within a digital environment, addressing the need for structured and organized data collection to improve notification management, tracking, and processing. During the create event operation, the system gathers specific data components related to the notification, including a notification identifier (ID) to uniquely identify the notification, a notification type to categorize the notification (e.g., alert, update, reminder), and notification details to provide additional context or content about the notification. These components are collected to ensure that notifications are properly identified, classified, and processed within the system. The collected data components are then used to facilitate subsequent operations, such as notification delivery, tracking, and user interaction. This structured approach enhances the efficiency and reliability of notification systems by ensuring that all relevant information is captured and organized during the creation phase. The system may also integrate with other components, such as notification distribution modules or user interface elements, to provide a comprehensive notification management solution.
11. The system of claim 9 , wherein the delayed delivery message indicates a notification error.
A system for managing message delivery in a communication network addresses the problem of ensuring reliable message transmission when network conditions or recipient availability are suboptimal. The system includes a message processing module that receives an incoming message and determines whether immediate delivery is feasible. If immediate delivery is not possible, the system generates a delayed delivery message, which may include a notification error indicating a failure or issue in the delivery process. The system then stores the original message in a queue for later retransmission when conditions improve. The delayed delivery message is sent to the sender or another designated recipient to inform them of the delivery status. The system also includes a retransmission module that periodically checks the queue and attempts to resend queued messages until successful delivery is confirmed. This approach ensures that messages are not lost due to temporary network issues or recipient unavailability, improving overall communication reliability. The system may also include logging and reporting features to track delivery attempts and errors for troubleshooting and performance monitoring.
12. The system of claim 9 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
A system for managing high-priority notifications in a communication network addresses the challenge of efficiently conveying critical information to users or devices. The system prioritizes and transmits urgent messages, ensuring timely delivery and action. The high-priority notification message includes structured data fields to enhance clarity and usability. These fields may encompass an event type to categorize the notification, case information to provide context, control information to dictate system behavior, device information to identify relevant hardware, contact information for recipient details, transaction information for financial or operational data, or a variable list for additional customizable parameters. This structured approach ensures that notifications are both informative and actionable, improving response times and system reliability. The system dynamically processes and routes these messages based on their content, optimizing communication workflows in environments where rapid decision-making is essential. By incorporating multiple data fields, the system adapts to diverse use cases, from security alerts to operational updates, ensuring comprehensive and efficient notification management.
13. The system of claim 12 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
A system for managing high-priority notifications in a communication network addresses the challenge of ensuring critical alerts are delivered reliably while respecting user preferences. The system includes a notification processor that evaluates incoming messages to determine their priority level, categorizing them as high-priority or standard. High-priority notifications are processed with urgency, bypassing typical delays or filters to ensure immediate delivery. The system also includes a reporting module that tracks the status of these notifications, including whether they were successfully delivered or if any errors occurred during transmission. Additionally, the system monitors user opt-out preferences, allowing individuals to decline reporting of their notification status to downstream systems. This feature ensures compliance with privacy regulations and user consent requirements. The system may integrate with external databases or analytics platforms to provide insights into notification performance and user engagement. By combining prioritization, delivery tracking, and opt-out management, the system enhances the reliability and transparency of critical communication in networked environments.
14. The system of claim 9 , the operations further comprising: removing the delayed delivery message from a queue in communication with the queue client based on determining that the acknowledgment is received from the partner system.
This invention relates to message processing systems, specifically addressing the challenge of managing delayed message delivery in distributed systems. The system ensures reliable message transmission between a sender and a partner system by implementing a queue-based mechanism. When a message is sent, it is initially placed in a queue managed by a queue client. The system monitors for an acknowledgment from the partner system, indicating successful receipt. If the acknowledgment is received, the message is removed from the queue to prevent redundant processing. If no acknowledgment is received within a specified time, the system may resend the message or take other corrective actions. The queue client acts as an intermediary, facilitating communication between the sender and the partner system while tracking message status. This approach improves system reliability by ensuring messages are delivered and acknowledged before being removed from the queue, reducing the risk of lost or duplicate messages in distributed environments. The system may also include additional features such as error handling, retry mechanisms, and logging to enhance robustness.
15. The system of claim 9 , the operations further comprising: determining whether an update regarding the server event is received from the partner system; de-queuing the delayed delivery message based on determining that the update is not received from the partner system; and transmitting the delayed delivery message to a downstream system.
This invention relates to a system for managing message delivery in a distributed computing environment, particularly where message delivery must be coordinated with external partner systems. The problem addressed is ensuring reliable and timely message delivery while accounting for dependencies on external systems that may not always be available or responsive. The system includes a message queue that holds delayed delivery messages, which are messages that cannot be immediately sent to a downstream system due to dependencies on external partner systems. The system monitors for updates from these partner systems regarding server events that may affect message delivery. If no update is received from the partner system within a specified time, the system de-queues the delayed delivery message and transmits it to the downstream system, bypassing the dependency. This ensures that message delivery is not indefinitely stalled due to unresponsive partner systems. The system also includes mechanisms for tracking message delivery status, managing message priorities, and handling retries for failed deliveries. The delayed delivery functionality allows the system to temporarily hold messages until certain conditions are met, such as confirmation from a partner system that a required event has occurred. This ensures that messages are only sent when all necessary prerequisites are satisfied, preventing downstream systems from receiving incomplete or invalid data. The system is designed to operate in environments where multiple systems must coordinate actions, such as financial transactions, data synchronization, or event-driven workflows.
16. One or more non-transitory computer readable media comprising instructions which, when executed by one or more processors, cause the one or more processors to perform operations for secure transmission of high-priority computer server event notifications, the operations comprising: receiving server event information from a notification source; performing a create event operation based on the server event information; generating i) a high-priority notification message based on one or more data components collected via the create event operation and ii) a delayed delivery message; transmitting the delayed delivery message to a queue client; transmitting the high-priority notification message to a partner system via a security protocol, the security protocol being one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); determining whether an acknowledgment message is received from the partner system; de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system; and transmitting the delayed delivery message to a downstream system, wherein the downstream system includes at least one of: a consumer credit management service provider system or a consumer risk management service provider system.
This invention relates to secure transmission of high-priority event notifications from computer servers, particularly in systems requiring reliable delivery to partner or downstream systems. The problem addressed is ensuring timely and secure delivery of critical server events, such as those related to consumer credit or risk management, while maintaining data integrity and availability. The system receives server event information from a notification source and processes it through a create event operation to collect relevant data components. Based on this data, it generates two types of messages: a high-priority notification and a delayed delivery message. The high-priority notification is transmitted to a partner system using a secure protocol, such as message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS). The system then checks for an acknowledgment from the partner system. If no acknowledgment is received, the delayed delivery message is dequeued and transmitted to a downstream system, which may include consumer credit or risk management service providers. This ensures that critical notifications are either securely delivered or fall back to an alternative system if the primary transmission fails. The approach enhances reliability and security in event-driven systems handling sensitive data.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
March 23, 2020
March 8, 2022
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.