Method of handling overlapping notification requests in networks with open application programming interfaces

• US 7,599,986 B2
• Filed: 03/26/2002
• Issued: 10/06/2009
• Est. Priority Date: 03/26/2002
• Status: Active Grant

• Current Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Original Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Inventors: Meeuwissen, Hendrik B., Van Tellingen, Harmanus
• Primary Examiner(s): Nguyen, Thu Ha T
• Application Number:
  US10/105,393
• Publication Number:
  US 20030225823A1
• Time in Patent Office: 2,751 Days
• Field of Search: 709200-201, 709/203, 709223-224, 709/227, 709/238, 707/3, 707/10, 707/104.1, 715700-866
• US Class Current: 709/203
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04M 3/42323 PBX's with CTI arrangements

Abstract

In the method of handling overlapping notification requests in a network with an open application programming interface, a response is received from a server to a notification request sent to the server based on a notification request entry in a plist. The notification request requests access to at least one object. Then, notification request entries in an rlist associated with the notification entry in the plist are identified, and the response is sent to an application associated with one of the identified notification request entries in the rlist. When a new notification request is received from an application, the new notification request is added to the rlist, and at least one of the plist and links between the notification request entries in the rlist and plist are altered. When a disable request requesting that a notification request be disabled is received from an application, at least one of the plist and links between the notification request entries in the plist and the rlist are altered.

Claims

1. A method of handling overlapping notification requests in a network with an open application programming interface, comprising:

receiving, at a device, a notification request from an application in a computer system requesting access required by the application, the device including at least one memory unit;

identifying notification request entries in a first list associated with a notification request entry in a second list, the first list and second list being stored in the at least one memory unit; and

sending, from the device, a response to the notification request based on the notification request entry in the second list to the application associated with one of the identified notification request entries in the first list, the notification request requesting access to at least one object, and notification request entries in the second list are non-overlapping requests so as to comply with the open application programming interface.

2. A method of handling overlapping notification requests in a network with an open application programming interface, comprising:

receiving, at a device, a response from a server to a notification request sent by an application to the server based on a notification request entry in a plist, the notification request requesting access to at least one object;

identifying notification request entries in an rlist associated with the notification entry in the plist, the plist and rlist being stored in at least one memory unit; and

sending, from the device, the response to an application associated with one of the identified notification request entries in the rlist,

wherein notification request entries in the plist list are non-overlapping requests so as to comply with the open application programming interface.

3. The method of claim 2, wherein the identifying step identifies notification request entries in the rlist based on links between the notification request entries in the plist and the notification request entries in the rlist.

4. The method of claim 3, wherein at least one notification request entry in the plist has a link to more than one notification request entry in the rlist.

5. The method of claim 3, wherein the rlist includes at least two overlapping notification request entries.

6. The method of claim 2, further comprising:

receiving a new notification request from an application;

adding the new notification request to the rlist; and

altering at least one of the plist and links between the notification request entries in the rlist and plist.

7. The method of claim 6, wherein the altering step comprises:

comparing the new notification request to notification request entries in the plist to determine if overlap exists between the new notification request and the notification request entries in the plist; and

changing at least one of the plist and the links between the notification request entries in the rlist and the plist based on results of the comparing step.

8. The method of claim 7, wherein the changing step adds the new notification request to the plist if the comparing step indicates that the new notification request does not overlap with the notification request entries in the plist.

9. The method of claim 7, wherein the changing step updates a notification request entry in the plist to the new notification request and updates the links between the plist and the rlist accordingly if the comparing step indicates that a notification request entry in the plist is covered by the new notification request.

10. The method of claim 7, wherein the changing step updates the links between the rlist and the plist without changing the plist when the comparing step indicates that the new notification entry is covered by a notification request entry in the plist.

11. The method of claim 7, wherein the changing step expands the plist to cover non-overlapping requested objects when the comparing step indicates one of (i) the new notification request partially covers a notification request entry in the plist and (ii) a notification request entry in the plist partially covers the new notification request entry.

12. The method of claim 2, further comprising:

receiving, from an application, a disable request requesting that a notification request be disabled; and

altering at least one of the plist and links between the notification request entries in the plist and the rlist.

13. The method of claim 12, wherein the altering step alters one of the plist and the links between the notification request entries in the plist and the rlist based on the links from the disabled notification request entry in the rlist to notification request entries in the plist, hereinafter referred to as linked notification request entries, and the links from the linked notification request entries in the plist to non-disabled notification request entries in the rlist.

14. The method of claim 12, wherein the altering step comprises:

first determining the number of links from the disabled notification request entry in the rust to notification request entries in the plist;

removing the disabled notification request entry from the rlist;

removing the notification request entry in the plist linked to the disabled notification entry in the rlist if the first determining step determines that one link exists.

15. The method of claim 14, further comprising:

second determining the number of links from the removed notification request entry in the plist linked to notification request entries in the rlist other than the disabled notification request entry if the first determining step determines that one link exists;

third determining if the other notification request entries in the rlist have links to notification request entries in the plist excluding the removed notification request entry in the plist if the second determining step determines that more than one link exists; and

altering the plist and the links between the plist and the rlist based on the other notification request entries when the third determining step determines that the other notification request entries have no links to notification request entries in the plist other than the removed notification request entry.

16. The method of claim 14, further comprising:

second determining the number of links from the removed notification request entry in the plist linked to notification request entries in the rlist other than the disabled notification request entry if the first determining step determines that one link exists;

third determining if the other notification request entries in the rlist have links to notification request entries in the plist excluding the removed notification request entry if the second determining step determines that more than one link exists;

for each of the other notification request entries, when the third determining step determines that the other notification request entries do have links to notification request entries in the plist other than the removed notification request entry,

identifying notification request entries in the plist linked to each of the other notification request entries;

for each identified notification request entry in the plist,

removing the links from the identified notification request entry in the plist to the other notification request entry;

fourth determining whether another link exists from the identified notification request entry in the plist to a notification request entry in the rlist;

removing the identified notification request entry in the plist if the fourth determining step determines that no other links exist; and

altering the rlist, the plist and the links between the rlist and plist based on the other notification request entries.

17. The method of claim 12, wherein the altering step comprises:

first determining the number of links from the disabled notification request entry in the rlist to notification request entries in the plist;

removing the disabled notification request entry from the rlist;

identifying the notification request entries in the plist linked to the disabled notification request entry if the first determining step determines that more than one link exists;

removing the links from the identified notification request entries in the plist to the disabled notification request entry;

second determining, for each identified notification request entry in the plist, if links exist from the identified notification request entry in the plist to another notification entry in the rlist; and

removing the identified notification request entry in the plist from the plist if the second determining step determines that no links exist.

18. The method of claim 2, wherein the object is one of a call object, a software object and a reference to an interface.

19. The method of claim 2, further comprising:

receiving, from an application, a request to change a notification request entry in the rlist from a first notification request to a second notification request;

altering the rlist and at least one of the plist and links between the notification request entries in the plist and the rust as if the received request requested disabling the first notification request; and

second altering the rlist and at least one of the plist and links between the notification request entries in the plist and the rlist as if the second notification request was a newly received notification request.

20. The method of claim 19, wherein the second altering step is performed before the first altering step.

21. The method of claim 2, further comprising:

receiving, from an application, a request to change a notification request entry in the rlist from a first notification request to a second notification request; and

determining not to change the rlist, plist or the links between the notification request entries in the plist and rlist.

22. The method of claim 2, further comprising:

receiving, from an application, a request to change a notification request entry in the rlist from a first notification request to a second notification request; and

changing criteria in at least a notification entry in the rlist based on the request to change a notification request entry.