Eliminating redundant notifications to SIP/simple subscribers

• US 10,158,595 B2
• Filed: 09/26/2017
• Issued: 12/18/2018
• Est. Priority Date: 01/11/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ben-Ezra, Asaf, Berezin, Olga, Schneider, Haim, Tal-Aviv, Ofira, Zinger, Asaf
• Primary Examiner(s): Nawaz, Asad M
• Assistant Examiner(s): Waqas, Saad A.
• Application Number:
  US15/715,780
• Publication Number:
  US 20180019965A1
• Time in Patent Office: 448 Days
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Abstract

A system for eliminating redundant notifications to SIP/SIMPLE subscribers, the system including a notification fingerprinter configured to generate a fingerprint from the contents of a SIP/SIMPLE subscriber notification using a predefined fingerprinting method, a fingerprint comparator configured to compare a fingerprint of a previously-sent notification with a fingerprint of a waiting-to-be-sent notification, and a server configured to send the waiting-to-be-sent notification to the subscriber only if the fingerprints do not match.

Claims

1. A system for eliminating redundant notifications to subscribers, the system comprising:

at least one hardware processor configured to;

generate a fingerprint from contents of a subscriber notification using a predefined fingerprinting method;

compare a fingerprint of a previously-sent notification with a fingerprint of a waiting-to-be-sent notification; and

determine to omit sending said waiting-to-be-sent notification to an email account of a subscriber in response to the comparing yielding that said fingerprint of said waiting-to-be-sent notification and said fingerprint of said previously-sent notification match,

wherein, in response to the processor determining that said fingerprint of said waiting-to-be-sent notification and said fingerprint of said previously-sent notification do not match, sending said waiting-to-be-sent notification to the email account of said subscriber and replacing said fingerprint of said previously-sent notification with a fingerprint of a currently sent notification, and

wherein at least one of the subscriber notification, the previously-sent notification, the waiting to be sent notification and the currently sent notification is a session initiation protocol (SIP) notification.

2. The system according to claim 1, wherein the at least one hardware processor is further configured to create a hash value from any of said notifications in accordance with a predefined hash algorithm.

3. The system according to claim 1, wherein the at least one hardware processor is further configured to create said fingerprint wherein a probability that two different notifications will have the same fingerprint is below a predefined threshold.

4. The system according to claim 1, wherein said notifications are session initiation protocol (SIP)/instant messaging and presence leveraging extensions (SIMPLE) notifications, including the (SIP) notification.

5. The system according to claim 1, wherein, in response to said comparison yielding that said fingerprint of said waiting-to-be-sent notification matches with said fingerprint of said previously-sent notification, the at least one hardware processor is further configured to determine that the said waiting-to-be-sent notification is a duplicate of said previously-sent notification and discards said waiting-to-be-sent notification.

6. The system according to claim 1, wherein, said previously-sent notification and said waiting-to-be sent notification comprise an update to presence information of session initiation protocol (SIP)/instant messaging and presence leveraging extensions (SIMPLE) subscribers.

7. The system according to claim 6, wherein the at least one hardware processor is further configured, in response to determining to omit to send said waiting-to-be sent notification, to discard the said waiting-to-be sent notification.

8. The system according to claim 1, wherein said previously-sent notification is a most recently sent notification to the subscriber.

9. The system according to claim 1, wherein each of the subscriber notification, the previously-sent notification, the waiting to be sent notification and the currently sent notification are session initiation protocol (SIP) notifications.

10. A method for eliminating redundant notifications to subscribers, the method comprising:

generating a fingerprint from contents of a first subscriber notification using a predefined fingerprinting method;

sending said first subscriber notification to a subscriber;

generating a fingerprint from the contents of a subsequent subscriber notification using said predefined fingerprinting method;

comparing said fingerprints;

determining to omit to send said subsequent notification to an email account of said subscriber in response to a result of said comparison yielding that said fingerprint of said subsequent notification matches with said fingerprint of said first subscriber notification; and

sending said subsequent notification to the email account of said subscriber and replacing said fingerprint of said first subscriber notification with a fingerprint of a currently sent notification in response to the result of said comparison yielding that said fingerprint of said subsequent notification does not match with said fingerprint of said first subscriber notification,

wherein at least one of the first subscriber notification, the subsequent subscriber notification and the currently sent notification is a session initiation protocol (SIP) notification.

11. The method according to claim 10, further comprising creating a hash value from any of said notifications in accordance with a predefined hash algorithm.

12. The method according to claim 10, further comprising creating said fingerprint wherein a probability that two different notifications will have the same fingerprint is below a predefined threshold.

13. The method according to claim 10, wherein said notifications are session initiation protocol (SIP)/instant messaging and presence leveraging extensions (SIMPLE) notifications, including the (SIP) notification.

14. The method according to claim 10, wherein, in response to said comparison yielding that said fingerprint of said subsequent notification matches with said fingerprint of said first subscriber notification, determining that the said subsequent notification is a duplicate of said first subscriber notification and discarding said subsequent notification.

15. The method according to claim 10, wherein, said first subscriber notification and said subsequent notification comprise an update to presence information of session initiation protocol (SIP)/instant messaging and presence leveraging extensions (SIMPLE) subscribers.

16. The method according to claim 15, wherein, in response to the determining to omit to send said subsequent notification, said subsequent notification is discarded.

17. A non-transitory computer-readable storage medium comprising instructions for enabling a computer to execute a method for eliminating redundant notifications to subscribers, the method comprising:

generating a fingerprint from contents of a first subscriber notification using a predefined fingerprinting method;

sending said first subscriber notification to said subscriber;

generating a fingerprint from the contents of a subsequent subscriber notification using said predefined fingerprinting method;

comparing said fingerprints;

determining to omit sending said subsequent notification to an email account of said subscriber in response to the comparing yielding that said fingerprint of said subsequent notification matches with said fingerprint of said first subscriber notification; and

sending said subsequent notification to the email account of said subscriber and replacing said fingerprint of said first subscriber notification with a fingerprint of a currently sent notification in response to the comparing yielding that said fingerprint of said subsequent notification does not match with said fingerprint of said first subscriber notification,

wherein at least one of the first subscriber notification, the subsequent subscriber notification and the currently sent notification is a session initiation protocol (SIP) notification.