# US 12,184,479 B2 · Systems and methods for real-time processing and transmitting of high-priority notifications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,184,479 B2 - Document ID: US12184479B2 - Status: Granted - Kind: B2 - Application number: 18/310,752 - Filed: 2023-05-02 - Published: 2023-08-24 - Granted: 2024-12-31 - Earliest claimed: 2017-12-15 - Assignees: Worldpay, LLC - Applicants: Worldpay, LLC - Inventors: Sachin Pawaskar - Web page: https://patentgrep.com/patent/US12184479B2 ## CPC - H04L 41/0686: Additional information in the notification, e.g. enhancement of specific meta-data - H04L 41/069: using logs of notifications; Post-processing of notifications - H04L 63/168: {above the transport layer} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract 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. ## Claims ### Claim 1 A method for secure transmission of high-priority computer server event notifications, the method comprising: generating a high-priority notification message based on one or more data components collected via a create event operation; transmitting the high-priority notification message to a first queue client; transmitting a delayed delivery message to a second queue client; denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol, wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or 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. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving server event information from a notification source; and performing a create event operation based on the server event information. ### Claim 3 (depends on 1) The method of claim 1, wherein the delayed delivery message indicates a notification error. ### Claim 4 (depends on 1) The method of claim 1, wherein the high-priority notification message comprises at least one of: an event type, case information, control information, device information, contact information, transaction information, or a variable list. ### Claim 5 (depends on 4) 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. ### Claim 6 (depends on 1) The method of claim 1, wherein the acknowledgement is received concurrently with a status update. ### Claim 7 (depends on 1) The method of claim 1, wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details. ### Claim 8 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: generating a high-priority notification message based on one or more data components collected via a create event operation; transmitting the high-priority notification message to a first queue client; transmitting a delayed delivery message to a second queue client; denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or 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. ### Claim 9 (depends on 8) The system of claim 8, wherein the operations further comprise: receiving server event information from a notification source; and performing a create event operation based on the server event information. ### Claim 10 (depends on 8) The system of claim 8, wherein the delayed delivery message indicates a notification error. ### Claim 11 (depends on 8) The system of claim 8, 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. ### Claim 12 (depends on 11) The system of claim 11, wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system. ### Claim 13 (depends on 8) The system of claim 8, wherein the acknowledgement is received concurrently with a status update. ### Claim 14 (depends on 8) The system of claim 8, wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details. ### Claim 15 A non-transitory computer-readable medium 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: generating a high-priority notification message based on one or more data components collected via a create event operation; transmitting the high-priority notification message to a first queue client; transmitting a delayed delivery message to a second queue client; denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol, wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or 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. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the operations further comprise: receiving server event information from a notification source; and performing a create event operation based on the server event information. ### Claim 17 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the delayed delivery message indicates a notification error. ### Claim 18 (depends on 15) The non-transitory computer-readable medium of claim 15, 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. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system. ### Claim 20 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details.