Systems, methods, and computer program products for providing a distributed hardware platform interface (HPI) architecture

• US 7,693,068 B2
• Filed: 11/07/2006
• Issued: 04/06/2010
• Est. Priority Date: 11/07/2006
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Crosson, John A., Blackburn, Laurie J., Bubnis, Robert K., Tomasko, Robert J., Nguyen, Huyen L., Wands, Michael J., Joslin, Andrew A., Freedman, Steven M.
• Primary Examiner(s): Jung; Min
• Application Number:
  US11/594,013
• Publication Number:
  US 20080107032A1
• Time in Patent Office: 1,246 Days
• Field of Search: None
• US Class Current: 370/236.2
• CPC Class Codes: H04L 41/24 using dedicated network management hardware

Abstract

Systems, methods, and computer program products for providing a distributed hardware platform interface (HPI) architecture are disclosed. According to one aspect, the subject matter described herein includes a system for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment. The system includes a first shelf that includes first hardware components, a second shelf that includes second hardware components, and an OAM module for providing an OAM function. The system also includes a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the OAM module, and a second HPI daemon for communicating OAM-related information between the second hardware components and the OAM module.

Claims

1. A system for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the system comprising:

(a) a first shelf including first hardware components and a second shelf including second hardware components;

(b) a first OAM module for providing an OAM function;

(c) a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the first OAM module, wherein the first HPI daemon provides a client side library to the first OAM module through which the first OAM module can perform monitoring, control, and management of the first hardware components; and

(d) a second HPI daemon for communicating OAM-related information between the second hardware components and the first OAM module, wherein the second HPI daemon provides a client side library to the first OAM module through which the first OAM module can perform monitoring, control, and management of the second hardware components.

2. The system of claim 1 comprising a third shelf including third hardware components, wherein the first HPI daemon communicates OAM-related information between the third hardware components and the first QAM module.

3. The system of claim 1 wherein the OAM function comprises at least one of a component status query function, a component identification query function, a component configuration function, a logging function, an alarm detection and response function, a command function, a graphical user interface function, and a command line interface function.

4. The system of claim 1 comprising a third HPI daemon for communicating OAM-related information between the first hardware components and the first OAM module.

5. The system of claim 1 wherein the first HPI daemon is adapted to communicate OAM-related information between the second hardware components and the first OAM module and wherein the second HPI daemon is adapted to communicate OAM-related information between the first hardware components and the first OAM module.

6. The system of claim 5 wherein the first and second HPI daemons operate in a load-sharing manner.

7. The system of claim 1 comprising an Internet protocol multimedia subsystem (IMS) cluster node, wherein the first and second shelves, the first OAM module, and the first and second HPI daemons are components of the IMS cluster node.

8. A system for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the system comprising:

(a) a first shelf including first hardware components and a second shelf including second hardware components;

(b) a first OAM module for providing an OAM function;

(c) a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the first OAM module; and

(d) a second HPI daemon for communicating OAM-related information between the second hardware components and the first OAM module, wherein the first OAM module includes a plurality of process threads for communicating OAM-related information with the first and second HPI daemons and wherein at least one of the plurality of threads communicates with a different HPI daemon than the other threads.

9. The system of claim 8 wherein the threads include a first thread for communicating OAM-related information with the first shelf and a second thread for communicating OAM-related information with the second shelf.

10. A system for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the system comprising:

(a) a first shelf including first hardware components and a second shelf including second hardware components;

(b) a first OAM module for providing an OAM function;

(c) a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the first OAM module;

(d) a second HPI daemon for communicating OAM-related information between the second hardware components and the first OAM module; and

(e) a second OAM module for providing an OAM function, wherein the first HPI daemon communicates OAM-related information between the first hardware components and the second OAM module, and wherein the second HP daemon communicates OAM-related information between the second hardware components and the second OAM module.

11. The system of claim 10 wherein the first and second OAM modules communicate OAM-related information to each other.

12. A system for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the system comprising:

(a) a first shelf including first hardware components and a second shelf including second hardware components;

(b) a first OAM module for providing an OAM function;

(c) a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the first OAM module;

(d) a second HPI daemon for communicating OAM-related information between the second hardware components and the first OAM module; and

(e) an Internet protocol multimedia subsystem (IMS) network element, wherein the first and second shelves, the first OAM module, and the first and second HPI daemons are components of the IMS network element.

13. A system for providing distributed operations, administration, and maintenance (OAM) functionality for hardware and software, the system comprising:

(a) a first shelf including first hardware components and first software components;

(b) a first OAM module for providing an OAM function;

(c) a first hardware platform interface (HPI) daemon for communicating OAM-related information between the first hardware components and the first OAM module;

(d) a second shelf including second hardware components and second software components;

(e) a second HPI daemon for communicating OAM-related information between the second hardware components and the first OAM module;

(f) a first simple network management protocol (SNMP) manager for providing an SNMP function; and

(g) a first SNMP agent for communicating SNMP-related information between the first software components and the first SNMP manager.

14. The system of claim 13 wherein the OAM function comprises at least one of a component status query function, a component identification query function, a component configuration function, a logging function, an alarm detection and response function, a command function, a graphical user interface function, and a command line interface function.

15. The system of claim 13 comprising a second SNMP agent for communicating SNMP-related information between the first software components and the first SNMP manager.

16. The system of claim 13 comprising a second SNMP manager for providing an SNMP function, and wherein the first SNMP agent communicates SNMP-related information between the first software components and the second SNMP manager.

17. The system of claim 16 wherein the first and second SNMP managers communicate SNMP-related information to each other.

18. The system of claim 13 comprising a second SNMP agent for communicating SNMP-related information between the second software components and the first SNMP manager.

19. The system of claim 18 wherein the first SNMP agent communicates SNMP-related information to and receives SNMP-related information from the second software components, and wherein the second SNMP agent communicates SNMP-related information to and receives SNMP-related information from the first software components.

20. The system of claim 19 wherein the first and second SNMP agents operate in a load-sharing manner.

21. The system of claim 18 comprising a second SNMP manager for providing an SNMP function, and wherein the first SNMP agent communicates SNMP-related information to and receives SNMP-related information from the second SNMP manager, and wherein the second SNMP agent communicates SNMP-related information to and receives SNMP-related information from the first SNMP manager.

22. The system of claim 21 wherein the first and second SNMP managers communicate SNMP-related information to each other.

23. The system of claim 18 wherein the first OAM module includes a plurality of process threads for communicating SNMP-related information with the first and second SNMP agents, and wherein at least one of the plurality of threads communicates with a different SNMP agent than the other threads.

24. The system of claim 23 wherein the threads include a first thread for communicating SNMP-related information with the first shelf and a second thread for communicating SNMP-related information with the second shelf.

25. The system of claim 23 wherein at least one thread for communicating SNMP-related information comprises an SNMP manager.

26. A method for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the method comprising:

(a) monitoring, using a first hardware platform interface (HPI) daemon, hardware components of a first shelf;

(b) monitoring, using a second HPI daemon, hardware components of a second shelf; and

(c) communicating, using a first OAM function, OAM-related information between the first OAM function and the first and second HPI daemons1 wherein the first HPI daemon provides a client side library to the first OAM function for monitoring, controlling, and managing the hardware components of the first shelf and wherein the second HPI daemon provides a client side library to the first OAM function for monitoring, controlling, and managing the hardware components of the second shelf.

27. The method of claim 26 comprising communicating OAM-related information between the first and second HPI daemons.

28. The method of claim 26 comprising monitoring, using the first HPI daemon, hardware components of a third shelf.

29. The method of claim 26 comprising monitoring, using a third HPI daemon, hardware components of the first shelf.

30. The method of claim 26 comprising monitoring, using the second HPI daemon, hardware components of the first shelf and monitoring, using the first HPI daemon, hardware components of the second shelf.

31. The method of claim 30 wherein the first and second HPI daemons operate in a load-sharing manner.

32. The method of claim 26 comprising communicating, using a plurality of process threads instantiated by the first OAM function, OAM-related information between the first OAM function and the first and second HPI daemons, wherein at least one of the plurality of threads communicates with a different HPI daemon than the other threads.

33. The method of claim 32 wherein communicating OAM-related information includes communicating, using a first thread, OAM-related information with the first shelf, and communicating, using a second thread, OAM-related information with the second shelf.

34. The method of claim 26 comprising communicating, using a second OAM function, OAM-related information between the second OAM function and the first and second HPI daemons.

35. The method of claim 34 comprising communicating OAM-related information between the first and second OAM functions.

36. The method of claim 26 wherein using the first OAM function includes performing at least one of a component status query function, a component identification query function, a component configuration function, a logging function, an alarm detection and response function, a command function, a graphical user interface function, and a command line interface function.

37. A method for providing distributed operations, administration, and maintenance (OAM) functionality in a multi-shelf processing environment, the method comprising:

(a) monitoring, using a first hardware platform interface (HPI) daemon, first hardware components of a first shelf;

(b) communicating, using a first OAM function, OAM-related information between the first OAM function and the first HPI daemon;

(c) monitoring, using a second HPI daemon, second hardware components of a second shelf;

(d) communicating, using the first OAM function, OAM-related information between the first OAM function and the second HPI daemon;

(e) monitoring, using a first simple network management protocol (SNMP) agent, first software components of the first shelf; and

(f) communicating, using a first SNMP manager, SNMP-related information between the first SNMP manager and the first SNMP agent.

38. The method of claim 37 comprising communicating, using a second SNMP agent, SNMP-related information between the first software components and the first SNMP manager.

39. The method of claim 37 comprising communicating, using a second SNMP manager, SNMP-related information between the second SNMP manager and the first SNMP agent.

40. The method of claim 39 comprising communicating SNMP-related information between the first and second SNMP managers.

41. The method of claim 37 comprising:

(a) monitoring, using a second SNMP agent, second software components of the second shelf; and

(b) communicating, using the first SNMP manager, SNMP-related information between the first SNMP manager and the second SNMP agent.

42. The method of claim 41 comprising:

(a) communicating, using the first SNMP agent, SNMP-related information between the first SNMP agent and the second software components; and

(b) communicating, using the second SNMP agent, SNMP-related information between the second SNMP agent and the first software components.

43. The method of claim 42 wherein the first and second SNMP agents operate in a load-sharing manner.

44. The method of claim 41 comprising communicating, using a second SNMP manager, SNMP-related information between the second SNMP manager and the first and second SNMP agents.

45. The method of claim 44 comprising communicating SNMP-related information between the first and second SNMP managers.

46. The method of claim 41 comprising communicating, using a plurality of process threads instantiated by the first SNMP manager, SNMP-related information between the first SNMP manager and the first and second SNMP agents, wherein at least one of the plurality of threads communicates with a different SNMP agent than the other threads.

47. The method of claim 46 wherein communicating SNMP-related information includes communicating, using a first thread, SNMP-related information with the first shelf, and communicating, using a second thread, SNMP-related information with the second shelf.

48. The method of claim 37 wherein using the first OAM function includes performing at least one of a component status query function, a component identification query function, a component configuration function, a logging function, an alarm detection and response function, a command function, a graphical user interface function, and a command line interface function.

49. A computer program product comprising computer-executable instructions embodied in a non-transitory computer-readable medium for performing steps comprising:

(a) monitoring, using a first hardware platform interface (HPI) daemon, hardware components of a first shelf;

(b) monitoring, using a second HPI daemon, hardware components of a second shelf; and

(c) communicating;

using an OAM function, OAM-related information between the first and second HPI daemons, wherein the first HPI daemon provides a client side library to the first OAM function for monitoring, controlling, and managing the hardware components of the first shelf and wherein the second HPI daemon provides a client side library to the first OAM function for monitoring, controlling, and managing the hardware components of the second shelf.

50. A computer program product comprising computer-executable instructions embodied in a non-transitory computer-readable medium for performing steps comprising:

(a) monitoring, using a first hardware platform interface (HPI) daemon, hardware components of a first shelf;

(b) monitoring, using a second HPI daemon, hardware components of a second shelf;

(c) communicating, using an OAM function, OAM-related information between the first and second HPI daemons;

(d) monitoring, using a first simple network management protocol (SNMP) agent, first software components of the first shelf; and

(e) communicating, using a first SNMP manager, SNMP-related information between the first SNMP manager and the first SNMP agent.