The present invention relates to computer networks in general, and more particularly to providing information to networked entities regarding the status of other networked entities.
The Session Initiation Protocol (SIP) is a protocol for creating, modifying, and terminating computer network-based communication sessions, such as for an Internet-based telephone call between two or more participants. Since its introduction various enhancements to SIP have been proposed, including the SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE) framework in which one or more network entities, such as computer users, create subscriptions on a server, known as a “presence” server, to receive presence information regarding another network entity, referred to as a “presentity.” When a change in the presentity's presence information is detected, such as when the presentity “publishes” such a change to the presence server, SIP is used to send a notification to the subscribers including the presentity's current presence information.
Further enhancements to SIP/SIMPLE include enabling presentities to limit what presence information subscribers may receive in a notification, as well as enabling subscribers to limit what available presence information they wish to receive in a notification. For example, presentity Joe's presence information includes elements ABCDE, while Joe limits subscriber Bob to receive only elements BCDE. If a change occurs to any of elements ABCDE, the presence server managing Bob's subscription will send Joe a notification including elements BCDE. However, if the change is to element A, and Bob previously received a notification including elements BCDE, Bob will receive no new information in the notification, as Bob previously received elements BCDE and does not in any case receive element A. Similarly, if Bob is only interested in elements DE, and sets a notification filter accordingly, if the change is to any of elements ABC, and Bob previously received a notification including elements DE, Bob will receive no new information in the notification, as Bob only ever receives elements DE. In both these examples, the changes to Joe's presence information caused redundant notifications to be sent to Bob, needlessly consuming processing and bandwidth resources.
Systems and/or methods for eliminating redundant notifications to SIP/SIMPLE subscribers would therefore be advantageous.
The present invention in embodiments thereof discloses novel systems and methods for eliminating redundant notifications to SIP/SIMPLE subscribers.
In one aspect of the present invention a system is provided 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.
The present invention in embodiments thereof will be understood and appreciated more fully from the following detailed description taken in conjunction with the appended drawings in which:
The present invention is now described within the context of one or more embodiments, although the description is intended to be illustrative of the invention as a whole, and is not to be construed as limiting the invention to the embodiments shown. It is appreciated that various modifications may occur to those skilled in the art that, while not specifically shown herein, are nevertheless within the true spirit and scope of the invention.
Reference is now made to
Server 100 typically includes, or has access to, a notification fingerprinter 104 which generates a fingerprint from the contents of the notification using a predefined fingerprinting method. The fingerprint is generated using any conventional technique, such as by creating a hash value from the notification in accordance with a predefined hash algorithm. The fingerprint is preferably generated such that the probability that two different notifications will have the same fingerprint is below a predefined threshold. One fingerprint may be generated for the entire notification, or alternatively the notification may be split into multiple segments, with a separate fingerprint being created separately for each segment, and an overall fingerprint being formed from the separate fingerprints. The fingerprint is preferably stored in a data store 106, which may be any computer-readable storage medium, together with an identifier of the subscriber to which the notification is sent, such as a network address, and/or the subscription, such as the SIP session ID of the subscription for which the notification is sent.
Reference is now made to
Reference is now made to
Any of the elements shown in
It is appreciated that one or more of the steps of any of the methods described herein may be omitted or carried out in a different order than that shown, without departing from the true spirit and scope of the invention.
While the methods and apparatus disclosed herein may or may not have been described with reference to specific computer hardware or software, it is appreciated that the methods and apparatus described herein may be readily implemented in computer hardware or software using conventional techniques.
The present application is a continuation of application Ser. No. 14/734,650 filed Jun. 9, 2015, which is a continuation of application Ser. No. 11/972,650 filed Jan. 11, 2008, issued as U.S. Pat. No. 9,088,578, the disclosure of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
6185613 | Lawson | Feb 2001 | B1 |
6549957 | Hanson | Apr 2003 | B1 |
7080123 | Freed | Jul 2006 | B2 |
7149778 | Patel | Dec 2006 | B1 |
20040059933 | Levy | Mar 2004 | A1 |
20050060643 | Glass et al. | Mar 2005 | A1 |
20060031346 | Zheng et al. | Feb 2006 | A1 |
20070121596 | Kurapati | May 2007 | A1 |
20070234428 | Rash | Oct 2007 | A1 |
20080212846 | Yamamoto | Sep 2008 | A1 |
20080270373 | Oostveen | Oct 2008 | A1 |
20080282303 | Harkness | Nov 2008 | A1 |
20080307513 | Chow | Dec 2008 | A1 |
20090013193 | Matsuzaki | Jan 2009 | A1 |
20110072077 | Tomkow | Mar 2011 | A1 |
20110134898 | Robertson | Jun 2011 | A1 |
Entry |
---|
A. B. Roach; “Session Initiattion Protocol (SIP)—Specific Event Notification”; RFC 3265—Standards. Network Working Group. SIP—Specific Event Notification; Jun. 2002; pp. 1-38; http://www.ietf.org/rfc/rfc3265.txt?number=3265. |
H. Khartabil, et al.; “Functional Description of Event Notification Filtering”; RFC 4660—Standards. Network Working Group. Functional Description of Filtering.; Sep. 2006; pp. 1-31; http://www.ietf.org/rfc/rfc4660.txt?number=4660. |
H. Schulzrinne et al.; “Common Policy: A Document Format for Expressing Privacy Preferences”; RFC 4745—Standards. Network Working Group. Common Policy.; Feb. 2007; pp. 1-32; http://www.ietf.org/rfc/rfc4745.txt?number=4745. |
Number | Date | Country | |
---|---|---|---|
20180019965 A1 | Jan 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14734650 | Jun 2015 | US |
Child | 15715780 | US | |
Parent | 11972650 | Jan 2008 | US |
Child | 14734650 | US |