US11165628B2ActiveUtilityA1

Systems and methods for registering computer server event notifications

85
Assignee: WORLDPAY LLCPriority: Dec 2, 2016Filed: Nov 26, 2019Granted: Nov 2, 2021
Est. expiryDec 2, 2036(~10.4 yrs left)· nominal 20-yr term from priority
Inventors:Sachin Pawaskar
H04L 41/0604H04L 41/06H04L 41/24H04L 41/069H04L 41/28
85
PatentIndex Score
3
Cited by
32
References
20
Claims

Abstract

A system for secure transmission of business event notifications includes a memory, at least one processor, a service gateway configured to: publish application programming interfaces (APIs) for secure transmission of business event notifications, a notification server configured to: publish APIs for secure transmission of business event notifications corresponding to the APIs published by the service gateway, obtain a new business event to report, determine a partner to receive a notification of the new business event, transmit an event notification to the partner by way of the service gateway APIs, and register the event notification in a database.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A method for controlled transmission of computer server event notifications, the method comprising:
 receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type; 
 generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 receiving, by the notification server, a request for computer server event details from the partner system; and 
 transmitting, by the notification server, the computer server event details to the partner system in response to the received request. 
 
     
     
       2. The method of  claim 1 , wherein the time threshold defines a length of a time period between two consecutive notifications. 
     
     
       3. The method of  claim 2 , wherein the quantity threshold defines a minimum number of computer server events to include in the notification. 
     
     
       4. The method of  claim 3 , wherein, if the time threshold is reached before the quantity threshold is reached, the notification is transmitted to the partner system before the quantity threshold is reached. 
     
     
       5. The method of  claim 2 , wherein the quantity threshold defines a maximum number of computer server events to include in the notification. 
     
     
       6. The method of  claim 5 , wherein, if the quantity threshold is reached before the time threshold is reached, the notification is transmitted to the partner system before the time threshold is reached. 
     
     
       7. The method of  claim 1 , further comprising:
 publishing, by the notification server, an application programming interface (API) for secure communication with the partner system over a computer network, the API corresponding to an API published by a service gateway, 
 wherein the notification is transmitted over the computer network by way of the API published by the service gateway. 
 
     
     
       8. The method of  claim 7 , wherein the API published by the service gateway include features for secure transmission of notifications. 
     
     
       9. The method of  claim 8 , wherein the features for secure transmission of notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS). 
     
     
       10. The method of  claim 8 , wherein the API published by the service gateway include interfaces for receiving computer server events from external services. 
     
     
       11. A system for controlled transmission of computer server event notifications, the system comprising:
 at least one processor; and 
 at least one data storage comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform a method comprising:
 receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type; 
 generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 receiving, by the notification server, a request for computer server event details from the partner system; and 
 transmitting, by the notification server, the computer server event details to the partner system in response to the received request. 
 
 
     
     
       12. The system of  claim 11 , wherein the time threshold defines a length of a time period between two consecutive notifications. 
     
     
       13. The system of  claim 12 , wherein the quantity threshold defines a minimum number of computer server events to include in the notification. 
     
     
       14. The system of  claim 13 , wherein, if the time threshold is reached before the quantity threshold is reached, the notification is transmitted to the partner system before the quantity threshold is reached. 
     
     
       15. The system of  claim 12 , wherein the quantity threshold defines a maximum number of computer server events to include in the notification. 
     
     
       16. The system of  claim 15 , wherein, if the quantity threshold is reached before the time threshold is reached, the notification is transmitted to the partner system before the time threshold is reached. 
     
     
       17. A non-transitory computer readable medium for controlled transmission of computer server event notifications, the non-transitory computer readable medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform a method comprising:
 receiving, by a notification server, a subscription registration request from a partner system, the subscription registration request comprising at least one event type; 
 generating, by the notification server, a notification associated with one or more computer server events of the at least one event type in accordance with a quantity threshold indicating a number of server events to associate with the notification, the quantity threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 transmitting, by the notification server, the notification to the partner system in accordance with a time threshold indicating a predetermined time period to associate with the notification, the time threshold calculated based on at least one of the at least one event type, the partner system, and a current time; 
 receiving, by the notification server, a request for computer server event details from the partner system; and 
 transmitting, by the notification server, the computer server event details to the partner system in response to the received request. 
 
     
     
       18. The non-transitory computer readable medium of  claim 17 , wherein the method further comprises:
 publishing, by the notification server, an application programming interface (API) for secure communication with the partner system over a computer network, the API corresponding to an API published by a service gateway, 
 wherein the notification is transmitted over the computer network by way of the API published by the service gateway. 
 
     
     
       19. The non-transitory computer readable medium of  claim 18 , wherein the API published by the service gateway include features for secure transmission of notifications. 
     
     
       20. The non-transitory computer readable medium of  claim 19 , wherein the features for secure transmission of notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS).

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.