Distinguished name scoping system for event filtering

• US 6,484,200 B1
• Filed: 06/11/1999
• Issued: 11/19/2002
• Est. Priority Date: 06/11/1999
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Bhat, Shivaram, Angal, Rajeev, Bapat, Subodh, Roytman, Michael
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): DINH, KHANH Q
• Application Number:
  US09/330,790
• Time in Patent Office: 1,257 Days
• Field of Search: 709/203, 709/224, 709/227, 709/232, 709/216, 709/218, 709/206, 370/352, 710/10, 710/4
• US Class Current: 709/224
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies

Abstract

Method and system for allowing a computer network operations manager to subscribe for and receive notifications concerning network events from one or more objects or object levels, as defined by distinguished name scoping, and optionally having at least one event characteristic from a selected list. The selected list of characteristics may include: one or more levels of network objects involved in the event; one or more specified network nodes involved in the event; a specified geographical region in which said event occurs; a specified period of days within which the event occurs or is initiated; a specified time interval within which the event occurs or is initiated; a specified class of devices involved in the event; and an event of one or more specified event types.

Claims

1. A computer implemented method of managing operations on a network, the method comprising:

receiving on a network an event communication that characterizes an event that has occurred at, or that affects, one or more network participants;

examining the event communication to determine whether the event is associated with at least one object or object level on a selected object list having at least one specified object or object level; and

when the event is associated with at least one object or object level that is on the object list, taking at least one of two actions;

(1) communicating selected information that describes the event to a selected event information recipient; and

(2) storing selected information on the event; and

examining said event communication to determine whether said event has at least one event characteristic that appears on a selected event list of at least one specified event characteristic; and

when said event has at least one characteristic that is on the characteristic list, taking at least one of two actions;

(1) communicating said selected information on at least one selected event characteristic that describes said event to a selected event information recipient; and

(2) storing said selected information on said event;

wherein said characteristic list is chosen to include at least one of the following event characteristics;

one or more specified network nodes involved in said event;

a specified geographical region in which said event occurs;

a specified time interval within which said event occurs or is initiated;

a specified class of devices involved in said event;

specified severity of said event; and

said event is one or more specified event types.

2. The method of claim 1, further comprising:

when said event does not have at least one characteristic that is on said characteristic list, taking no action on said event communication.

3. The method of claim 1, further comprising storing said selected information on said event having at least one characteristic that is on said characteristic list, and communicating said selected information on said at least one selected event characteristic to said selected event information recipient at a selected later time.

4. The method of claim 1, further comprising modifying said characteristic list at least once for a selected reporting time interval.

5. The method of claim 1, further comprising modifying said object list at least once for a selected reporting time interval.

6. A computer implemented system for managing operations on a network, the method comprising a computer that is programmed:

to receive on a network an event communication that characterizes an event that has occurred at, or that affects, one or more network participants;

to examine the event communication to determine whether the event is associated with at least one object or object level on a selected object list having at least one specified object or object level; and

when the event is associated with at least one object or object level that is on the object list, to take at least one of two actions;

(1) communicate selected information that describes the event to a selected event information recipient; and

(2) store selected information on the event; and

to examine said event communication to determine whether said event has at least one event characteristic that appears on a selected event list of at least one specified event characteristic; and

when said event has at least one characteristic that is on the characteristic list, to take at least one of two actions;

(1) communicate said selected information on at least one selected event characteristic that describes said event to a selected event information recipient; and

(2) store said selected information on said event;

wherein said selected characteristic list is chosen to include at least one of the following event characteristics;

one or more specified network nodes involved in said event;

a specified geographical region in which said event occurs;

a specified time interval within which said event occurs or is initiated;

a specified class of devices involved in said event;

specified severity of said event; and

said event is one or more specified event types.

7. The system of claim 6, wherein, when said event does not have at least one characteristic that is on said characteristic list, said computer is programmed to take no action on said event communication.

8. The system of claim 6, wherein said computer is further programmed:

to store said selected information on said event having at least one characteristic that is on said characteristic list; and

to communicate said selected information on said at least one selected event characteristic to said selected event information recipient at a selected later time.

9. The system of claim 6, wherein said computer is further programmed to modify said characteristic list at least once for a selected reporting time interval.

10. The system of claim 6, wherein said computer is further programmed to modify said object list at least once for a selected reporting time interval.

11. A computer program product embodied in a computer usable medium having a computer readable code mechanism embodied therein for managing transactions, the computer program product comprising:

a first computer readable code mechanism configured to receive on a network an event communication that characterizes an event that has occurred at, or that affects, one or more network participants;

a second computer readable code mechanism configured to examine the event communication to determine whether the event is associated with at least one object or object level on a selected object list having at least one specified object or object level;

a third computer readable code mechanism configured so that, when the event is associated with at least one object or object level that is on the object list, to take at least one of two actions;

(1) communicate selected information on the event that describes the event to a selected event information recipient; and

(2) store selected information on the event; and

wherein at least one of said first, second and third code mechanisms is configured;

to examine said event communication to determine whether said event has at least one event characteristic that is on said characteristic list; and

when said event has at least one characteristic that is on said characteristic list, to take at least one of two actions;

(1) communicate said selected information on at least one selected event characteristic that describes said event to a selected event information recipient; and

(2) store said selected information on said event;

wherein said selected list associated with said second code mechanism includes at least one of the following event characteristics;

one or more specified network nodes involved in said event;

a specified geographical region in which said event occurs;

a specified time interval within which said event occurs or is initiated;

a specified class of devices involved in said event;

specified severity of said event; and

said event is one or more specified event types.

12. The computer program product of claim 11, wherein, when said event does not have at least one characteristic that is on said characteristic list, said third code mechanism takes no action on said event communication.

13. The computer program product of claim 11, wherein at least one of said first, second and third code mechanisms is further configured:

to store said selected information on said event having at least one characteristic that is on said characteristic list; and

to communicate said selected information on said at least one selected event characteristic to said selected event information recipient at a selected later time.

14. The computer program product of claim 11, at least one of said first, second and third code mechanisms is further configured to modify said characteristics list of said at least once for a selected reporting time interval.

15. The computer program product of claim 11, at least one of said first, second and third code mechanisms is further configured to modify said object list of said at least once for a selected reporting time interval.