External event processor system and method

• US 20030050983A1
• Filed: 09/12/2001
• Published: 03/13/2003
• Est. Priority Date: 09/12/2001
• Status: Abandoned Application

• Current Assignee: Alcatel SA (Nokia Corporation)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Johnson, Paul A.
• Application Number:
  US09/952,779
• Publication Number:
  US 20030050983A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

An External Event Processor (EEP) system and method incorporating a separate software component that permits reformatting of received events and transportation of these events to previously registered event consumers is disclosed. The present invention teaches creation of a separate software component to handle event processing and transportation, running within a separate software process. This separate software process has a remote interface utilized by a Network Management application to send events in their most basic form to the External Event Processor (EEP). Subsequently, the EEP performs all other functions that are necessary to convert the supplied even to the proper form and type required by the external event consumers. In addition, the EEP provides the event with Quality of Service (QoS) properties required by external consumers.

Claims

1. An external event processor (EEP) system comprising:

(a) one or more event suppliers;

(b) one or more event consumers;

(c) one or more notification channel means; and

(d) an external event processor software subsystem means;

wherein

said external event processor software subsystem means translates events between said event suppliers and said event consumers;

said external event processor software subsystem means has an external interface to receive events from said event suppliers through a main software application;

said external event processor software subsystem means may receive events from one or more network elements via said external interface.

2. The external event processor (EEP) system of claim 1 further comprising:

(a) MainAppDispatcher means;

(b) ClientTranslatorListener means;

(c) ClientListener means;

(d) ClientDispatcher means;

(e) ClientChannelListener means; and

(f) ChannelSupplier means;

wherein

said events are processed sequentially through said means (a)-(f).

3. The external event processor (EEP) system of claim 1 further comprising:

(a) EEP;

;

app means;

(b) EEP;

;

util means;

(c) EEP;

;

common means;

(d) EEP;

;

client means;

(e) EEP;

;

server means;

(f) EEP;

;

transport means; and

(g) EEP;

dispatch means.

4. The external event processor (EEP) system of claim 1 wherein said event suppliers and event consumers reside on separate nodes within a computer network.

5. The external event processor (EEP) system of claim 1 wherein one or more components of said system is implemented within an application programming interface (API).

6. The external event processor (EEP) system of claim 1 wherein said transport occurs over the Internet.

7. The external event processor (EEP) system of claim 1 wherein one or more components of said system is implemented on a personal computer (PC).

8. The external event processor (EEP) system of claim 7 wherein said personal computer utilizes a HP-UX™

operating environment.

9. The external event processor (EEP) system of claim 7 wherein said personal computer utilizes a LINUX™

operating environment.

10. The external event processor (EEP) system of claim 7 wherein said personal computer utilizes a SOLARIS™

operating environment.

11. The external event processor (EEP) system of claim 7 wherein said personal computer utilizes a UNIX™

operating environment.

12. The external event processor (EEP) system of claim 7 wherein said personal computer utilizes a Microsoft®

Windows™

operating environment.

13. An external event processor (EEP) method comprising:

(1) receiving an event from a network element or other event supplier;

(2) transferring said event to an external event processor (EEP) software component via an external interface;

(3) translating said event into a form suitable for interpretation by an event consumer;

(4) transmitting said translated event to an event consumer. wherein

said events are transferred from said event suppliers to said event consumers through one or more event channels.

14. The external event processor (EEP) method of claim 13 further comprising sequential processing said event through:

(a) MainAppDispatcher means;

(b) ClientTranslatorListener means;

(c) ClientListener means;

(d) ClientDispatcher means;

(e) ClientChannelListener means; and

(f) ChannelSupplier means.

15. The external event processor (EEP) method of claim 13 further comprising processing of said event by:

(a) EEP;

;

app means;

(b) EEP;

;

util means;

(c) EEP;

;

common means;

(d) EEP;

;

client means;

(e) EEP;

;

server means;

(f) EEP;

;

transport means; and

(g) EEP;

dispatch means.

16. The external event processor (EEP) method of claim 13 wherein said event suppliers and event consumers reside on separate nodes within a computer network.

17. The external event processor (EEP) method of claim 13 wherein one or more steps of said method is implemented within an application programming interface (API).

18. The external event processor (EEP) method of claim 13 wherein said transport occurs over the Internet.

19. The external event processor (EEP) method of claim 13 wherein one or more steps of said method is implemented on a personal computer (PC).

20. The external event processor (EEP) method of claim 19 wherein said personal computer utilizes a HP-UX™

operating environment.

21. The external event processor (EEP) method of claim 19 wherein said personal computer utilizes a LINUX™

operating environment.

22. The external event processor (EEP) method of claim 19 wherein said personal computer utilizes a SOLARIS™

operating environment.

23. The external event processor (EEP) method of claim 19 wherein said personal computer utilizes a UNIX™

operating environment.

24. The external event processor (EEP) method of claim 19 wherein said personal computer utilizes a Microsoft®

Windows™

operating environment.

25. An external event processor (EEP) encoded propagated signal data stream constructed using

(1) one or more event suppliers;

(2) one or more event consumers;

(3) a communications network;

(4) encoded event signaling data; and

(5) an external event processor (EEP) means;

wherein

said external event processor means translates event information between said event suppliers and event consumers over said communications network via an external interface to a main software application that pushes event data to said EEP through said external interface;

said translation occurs via encoding of event information from said event suppliers to said event consumers via said communication channel.

26. A computer usable medium having computer-readable program code means providing external event processor (EEP) functionality, said computer-readable program means comprising:

(1) computer program code means for receiving an event from a network element or other event supplier;

(2) computer program code means for transferring said event to an external event processor (EEP) software component via an external interface;

(3) computer program code means for translating said event into a form suitable for interpretation by an event consumer;

(4) computer program code means for transmitting said translated event to an event consumer;

wherein

said events are transferred from said event suppliers to said event consumers through one or more event channels.

27. The computer usable medium of claim 26 wherein said events are sequentially processed through:

(a) MainAppDispatcher computer program code means;

(b) ClientTranslatorListener computer program code means;

(c) ClientListener computer program code means;

(d) ClientDispatcher computer program code means;

(e) ClientChannelListener computer program code means; and

(f) ChannelSupplier computer program code means.

28. The computer usable medium of claim 26 further comprising processing of said event by:

(a) EEP;

;

app computer program code means;

(b) EEP;

;

util computer program code means;

(c) EEP;

;

common computer program code means;

(d) EEP;

;

client computer program code means;

(e) EEP;

;

server computer program code means;

(f) EEP;

;

transport computer program code means; and

(g) EEP;

dispatch computer program code means.

29. The computer usable medium of claim 26 wherein said event suppliers and event consumers reside on separate nodes within a computer network.

30. The computer usable medium of claim 26 wherein one or more steps of said functionality is implemented within an application programming interface (API).

31. The computer usable medium of claim 26 wherein said transport occurs over the Internet.

32. The computer usable medium of claim 26 wherein said medium is compatible with a personal computer (PC).

33. The computer usable medium of claim 32 wherein said personal computer utilizes a HP-UX™

operating environment.

34. The computer usable medium of claim 32 wherein said personal computer utilizes a LINUX™

operating environment.

35. The computer usable medium of claim 32 wherein said personal computer utilizes a SOLARIS™

operating environment.

36. The computer usable medium of claim 32 wherein said personal computer utilizes a UNIX™

operating environment.

37. The computer usable medium of claim 32 wherein said personal computer utilizes a Microsoft®

Windows™

operating environment.