Information and status and statistics messaging method and system for inter-process communication

• US 20070106778A1
• Filed: 10/26/2006
• Published: 05/10/2007
• Est. Priority Date: 10/27/2005
• Status: Abandoned Application

• Current Assignee: Trapeze Networks Incorporated (Juniper Networks Incorporated)
• Original Assignee: Trapeze Networks Incorporated (Juniper Networks Incorporated)
• Inventors: Williams, Joseph, Zeldin, Paul
• Application Number:
  US11/588,878
• Publication Number:
  US 20070106778A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

System, method, architecture, network device, and computer programs and computer program products for inter-process communications. Message structure, procedure for generating the message structure, applications of the message structure and messaging method for obtaining status, statistics, and other information and for performing an information or parameter set operation across one or more process boundaries, and to other device and system architectures and methods for utilizing the messages and messaging methodology.

Claims

1. A method for obtaining an information from an information producer process to an information consumer process, where the producer and consumer processes are separated by at least one process boundary, the method comprising:

generating an information request in the consumer process;

communicating a message including the information request from the consumer process to the producer process;

receiving the information request by the producer process;

processing the request and generating a response; and

communicating a message including the response that includes the requested information to the consumer process.

2. A method as in claim 1, wherein the information comprises a status or statistical information and the message comprises a status or statistical information (STAT) message.

3. A method as in claim 2, wherein the consumer and producer processes are two different processes within a network switch device.

4. A method as in claim 2, wherein one of the processes is a configuration process responsible for configuring settings or parameter of the network switch and the other of the two process is a network process responsible for providing one or more parameters or status information items.

5. A method as in claim 4, wherein the request is received from the consumer process by the producer process via a dispatcher.

6. A method as in claim 4, wherein the response is sent from the producer process to the consumer process via a dispatcher.

7. A method as in claim 4, wherein a the information is a statistical or status (STAT) information, and the method further comprises:

a dispatcher receiving the STAT message, decodes the STAT message based on the received message type, and then provides and optionally executes an appropriate callback function.

8. A method as in claim 1, wherein the communicated message comprises an information passing STAT message type.

9. A method as in claim 8, wherein the information passing STAT message may optionally include a STAT message header, a key, and/or a message record.

10. A method as in claim 9, wherein the information passing STAT message may provide a null or absent message header, a null or absent key, and a null or absent message header.

11. A method as in claim 8, wherein the information passing STAT message includes a header or implementation file in the information request and in the response to that information request, but does not include one or more of the key and the message record.

12. A method as in claim 1, wherein the communicated message includes a STAT header or interface description for a STAT information request and a STAT information response.

13. A method as in claim 12, wherein the STAT header or interface description includes:

a length field indicating a size or number of octets in the message not including any STAT header;

a sequence number field indicating an ever-increasing message sequence number;

a number of records field indicating a total number of records included in the message not including any message keys that might optionally be present;

a flags field that uses a first bit to indicate a get-exact or a get-next operation is indicated and a second bit to indicate a first or a not-first operation; and

a result field indicating a returned result from an operation that is optional in request and in response messages; and

a last record field indicating an offset to the last record in the message.

14. A method as in claim 12, wherein the message key element includes reference information on the process on the other side for the STAT message to return, and the returned response STAT message includes a similar key or reference information for use by the receiver of the response.

15. A method as in claim 12, wherein the record or key may include a variable length message type field that defines the type of message;

a number of parameters field identifying the number of parameters in the record or key; and

a parameters field that indicates the parameters encoded with any one or more of parameter identifier, parameter type, parameter length, and parameter value.

16. A method as in claim 12, wherein a return status code is optionally sent in the STAT response message.

17. A method as in claim 1, wherein the information messages comprise STAT messages that are defined as a DTD format in the XML programming language.

18. A method as in claim 1, wherein the information message includes a capability for returning an information item from another process across an inter-process boundary.

19. A method as in claim 18, wherein the information item is selected from the set of information items consisting of a value, a statistical information, a plurality of information items, a status, a set or plurality of status items, a state, or any combination of these.

20. A method as in claim 1, wherein the communicated message comprises a STAT message and includes a first key element that permits reference from the STAT message sender requesting the information, and a second key element that is included with the message back from the responding process so that the process receiving the response has a reference to match it back with either the requested information or with the requesting process.

21. A method as in claim 1, wherein the information message comprises a STAT message for gathering information from a process into another process;

and the STAT message optionally an indicator that has at least two states and identifies that the STAT message should be executed as a synchronous communication or message, or as an asynchronous communication or message.

22. A method as in claim 1, wherein the message comprises a STAT message that generates interfaces for statistics and the interfaces automatically create both request and response message prototypes.

23. A method as in claim 1, wherein the message comprises a STAT message that generates interfaces for statistics and the interfaces automatically create both request and response message prototypes;

and provides either one of the synchronous and asynchronous prototypes.

24. A method as in claim 2, wherein for each STAT message defined there are a plurality of functions automatically generated using a STAT message transformation or conversion tool including an Application Program Interface (API) which may be used when implementing STAT information gathering or retrieval.

25. A method as in claim 24, wherein the STAT message transformation or conversion tool comprises a STAT message compiler.

26. A method as in claim 24, wherein ones of the plurality of functions are selected from the set of functions consisting of STAT message producer functions and STAT message consumer functions.

27. A method as in claim 26, wherein the functions are selected from the set of functions consisting of marshall, unmarshall, register, dispatch, get, next record, next key, allocate, deallocate, insert, and combinations of these.

28. A method as in claim 24, wherein at least one of the automatically generated Application Program Interfaces is a per-message API, and at least one of the automatically generated Application Program Interfaces is a per-catalog API.

29. A method as in claim 24, wherein a set of application program interfaces (APIs) are automatically generated for each message and for each catalog and include at least one of an internal API, a consumer process side API, and a producer process side API.

30. A method as in claim 2, wherein the messaging includes the use of application program interfaces by the STAT producer and the STAT consumer including general application program interfaces used by callback functions.

31. A method as in claim 2, wherein a plurality of APIs are generated that are specific to the given particular STAT message.

32. A method as in claim 2, wherein an API is automatically generated that is used by a STAT consumer to retrieve the next record in a STAT message response.

33. A method as in claim 2, wherein an API is automatically generated that is used by a STAT message consumer to retrieve a key to be used for a next get request.

34. A method as in claim 2, wherein an API is automatically generated that is used to send a STAT request message from STAT consumer to STAT producer, and when the message is intended to be a synchronous message this function blocks and waits for a STAT response message from the STAT producer.

35. A method as in claim 2, wherein an API is automatically generated that is used by a STAT producer to register a producer handler function for a given message.

36. A method as in claim 2, wherein an API is automatically generated that is used to allocate memory for the record of the given message type.

37. A method as in claim 2, wherein an API is automatically generated that is used to free memory for the record of the given message type.

38. A method as in claim 2, wherein an API is automatically generated that is used by a STAT Producer to insert a record into a STAT Response message.

39. A method as in claim 2, further comprising providing a STAT message interface, the stat interface enabling a messaging mechanism for open-ended requesting of status information, statistical information, and/or other information, in any combination.

40. A method as in claim 1, wherein the response is returned back to the requesting consumer process from the message destination producer process;

and the response includes a state variable within the response returned back to the message requesting process.

41. A method as in claim 2, wherein the method includes a STAT messaging model where for each STAT message sent to a recipient process, a response will be returned to the sending process and provides an automated request and response. Mechanism.

42. A method as in claim 1, wherein the method provides an open-ended request mechanism for obtaining the status, statistics, and/or other information from the destination process.

43. A method as in claim 1, wherein the method provides a closed-ended request mechanism for obtaining the status, statistics, and/or other information from the destination process.

44. A method as in claim 42, wherein the requesting process can later make an additional open-ended request to obtain additional information beginning at the information where the first request ended without needed to specify an identifier of that last information.

45. A method as in claim 42, wherein the last information is an information from a last port and the information where the first request ended is an information from an ending port.

46. A method as in claim 44, wherein the starting and stopping points for the information are automatically incorporated into the subsequent request message with optional incrementing as required.

47. A method according to claim 1, wherein for each message send by a sender consumer process, a response back to the sender consumer process from the destination receiving producer process is received with the requested status, statistics, and/or other information.

48. A method according to claim 1, wherein for each message defined and processed as a stat message there are two automatically generated messages including the first request message and the second response message.

49. A computer readable medium encoded with a computer program for directing a computer to obtain an information from an information producer process to an information consumer process, where the producer and consumer processes are separated by at least one process boundary, the computer program including a module that includes executable instructions for:

generating an information request in the consumer process;

communicating a message including the information request from the consumer process to the producer process;

receiving the information request by the producer process;

processing the request and generating a response; and

communicating a message including the response that includes the requested information to the consumer process.

50. A system for obtaining an information from an information producer process to an information consumer process, where the producer and consumer processes are separated by at least one process boundary, the computer system comprising:

means for generating an information request in the consumer process;

means for communicating a message including the information request from the consumer process to the producer process;

means for receiving the information request by the producer process;

means for processing the request and generating a response; and

means for communicating a message including the response that includes the requested information to the consumer process.

51. A method for defining information to be obtained from in an external process in a computing machine or device, the method comprising:

defining a message using a high-level language;

automatically generating a plurality of application programming interfaces (APIs) including implementation code and any interfaces; and

using the APIs to transfer information, data, or state from one process to another process across a process boundary.

52. A method for designing an information gathering message comprising:

(1) defining an information gathering (STAT) message in a high-level descriptive language;

(2) running the high-level descriptive language through an STAT message transformation or modification tool adapted to the high-level descriptive language to generate per-STAT message Application Program Interfaces (APIs); and

(3) using these APIs to obtain the STAT information from one process to another process.

53. A method according to claim 52, wherein the high-level descriptive language includes the XML computer program language.

54. A method according to claim 52, wherein the STAT message transformation or modification tool adapted to the high-level descriptive language comprises an STAT message compiler.

55. A method according to claim 52, wherein the high-level descriptive language includes the XML computer program language, and the STAT message compiler comprises an XML language compiler.