System and method for optimizing inter-domain event services

• US 20050283477A1
• Filed: 06/15/2005
• Published: 12/22/2005
• Est. Priority Date: 06/17/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Sparks, Robert J., Campbell, Ben A., Donovan, Steven R., Deo, Ajay P., Roach, Adam B.
• Granted Patent: US 7,607,138 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A system and method for optimizing inter-domain event services includes receiving a first subscription request to receive an event state of an event source. A view associated with the first subscription request is determined. A notify message is sent that reflects a first defined view into the event state of the event source that corresponds to the first subscription request. A second subscription request is received to receive the event state of the event source. A view associated with the second subscription request is determined. It is determined if the first defined view corresponds to the second subscription request.

Claims

1. A method for optimizing inter-domain event services, comprising:

receiving a first subscription request to receive an event state of an event source;

determining a view associated with the first subscription request;

sending a notify message reflecting a first defined view into the event state of the event source that corresponds to the first subscription request;

receiving a second subscription request to receive the event state of the event source;

determining a view associated with the second subscription request;

determining if the first defined view corresponds to the second subscription request.

2. The method of claim 1, further comprising:

generating a view identifier to identify the event source, wherein the view identifier is a universal resource identifier;

sending the view identifier;

receiving a first view subscription request to subscribe to the first defined view of the event source.

3. The method of claim 1, further comprising:

reusing the first defined view that corresponds to the first subscription request if the first defined view corresponds to the second subscription request;

reusing a first view subscription to subscribe to the first defined view of the event source.

4. The method of claim 1, further comprising:

sending a second defined view that corresponds to the second subscription request if the first defined view does not correspond to the second subscription request;

receiving a second view subscription request to subscribe to the second defined view of the event source.

5. The method of claim 1, further comprising:

determining if the event state of the event source changes;

sending a change notification, wherein the change notification includes a view identifier of the event source.

6. The method of claim 1, further comprising:

collecting one or more change notifications over a time interval;

aggregating the one or more change notifications, wherein the aggregated change notifications include a view identifier;

sending the one or more change notifications.

7. The method of claim 6, wherein sending the one or more change notifications includes applying a compression algorithm to reduce a size of the aggregated change notifications.

8. The method of claim 1, further comprising sending a notification of a policy change using the first and second subscriptions established by the first and second subscription requests.

9. A system for optimizing inter-domain event services, comprising:

one or more event sources operable to provide event state information;

an event source server coupled to the one or more event sources operable to enable the one or more event sources to provide the event state information;

a plurality of event consumers each operable to subscribe to a defined view to receive the event state information based on subscription requests associated with the one or more event sources;

an event consumer server coupled to the event source server and the plurality of event consumers operable to enable the plurality of event consumers to subscribe to the one or more event sources, wherein the event source server is further operable to determine if the defined view subscribed to corresponds to an established defined view.

10. The system of claim 9, wherein the event source server is operable to:

generate a view identifier to identify the event source, the view identifier is a universal resource identifier;

send the view identifier;

receive a view subscription from each event consumer to subscribe to a defined view of the event source corresponding to the view identifier.

11. The system of claim 9, further comprising a link operable to couple the event source server and the event consumer server, wherein the link allows a plurality of subscription requests to correspond to a defined view.

12. The system of claim 11, if the defined view being subscribed to corresponds to the established defined view, the event source server is operable to reuse the defined view.

13. The system of claim 9, if the defined view being subscribed to does not correspond to the established defined view, the event source server is operable to send a new defined view.

14. The system of claim 9, wherein the event source server is operable to:

determine if the event state of the one or more event sources changes;

send a change notification to the event consumer server that includes a view identifier of each of the one or more event sources that changed.

15. The system of claim 9, wherein the event source server is operable to:

collect one or more change notifications of the one or more event sources over a time interval;

aggregate the one or more change notifications that include a view identifier of each event source;

send the one or more change notifications.

16. The system of claim 15, wherein the event consumer server is operable to send the change notifications of each event source to the plurality of event consumers subscribed to the event state.

17. The system of claim 15, wherein the event source server is operable to apply a compression algorithm to reduce a size of the aggregated change notifications.

18. The system of claim 9, wherein the event source server is operable to send a notification of a policy change using the subscription requests received from the plurality of event consumers.

19. A computer readable medium including logic for optimizing inter-domain event services, the logic operable to:

receive a first subscription request to receive an event state of an event source;

determine a view associated with the first subscription request;

send a notify message reflecting a first defined view into the event state of the event source that corresponds to the first subscription request;

receive a second subscription request to receive the event state of the event source;

determine a view associated with the second subscription request;

determine if the first defined view corresponds to the second subscription request.

20. The computer readable medium of claim 19, the logic operable to:

generate a view identifier to identify the event source, wherein the view identifier is a universal resource identifier;

send the view identifier;

receive a first view subscription request to subscribe to the first defined view of the event source.

21. The computer readable medium of claim 19, the logic operable to:

reuse the first defined view that corresponds to the first subscription request if the first defined view corresponds to the second subscription request;

reuse a first view subscription to subscribe to the first defined view of the event source.

22. The computer readable medium of claim 19, the logic operable to:

send a second defined view that corresponds to the second subscription request if the first defined view does not correspond to the second subscription request;

receive a second view subscription request to subscribe to the second defined view of the event source.

23. The computer readable medium of claim 19, the logic operable to:

determine if the event state of the event source changes;

send a change notification, wherein the change notification includes a view identifier of the event source.

24. The computer readable medium of claim 19, the logic operable to:

collect one or more change notifications over a time interval;

aggregate the one or more change notifications, wherein the aggregated change notifications include a view identifier;

send the one or more change notifications.

25. The computer readable medium of claim 24, wherein the logic operable to send the one or more change notifications includes applying a compression algorithm to reduce a size of the aggregated change notifications.

26. The computer readable medium of claim 19, the logic operable to send a notification of a policy change using the first and second subscriptions established by the first and second subscription requests.

27. A system for optimizing inter-domain event services, comprising:

means for receiving a first subscription request to receive an event state of an event source;

means for determining a view associated with the first subscription request;

means for sending a notify message reflecting a first defined view into the event state of the event source that corresponds to the first subscription request;

means for receiving a second subscription request to receive the event state of the event source;

means for determining a view associated with the second subscription request;

means for determining if the first defined view corresponds to the second subscription request.