Intelligent messaging application programming interface

• US 20060168331A1
• Filed: 12/23/2005
• Published: 07/27/2006
• Est. Priority Date: 01/06/2005
• Status: Abandoned Application

• Current Assignee: Tervela, Inc. (Box Incorporated)
• Original Assignee: Terevela Incorporated
• Inventors: Fraval, Pierre, Singh, Kul, Thompson, J. Barry
• Application Number:
  US11/317,280
• Publication Number:
  US 20060168331A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0879 Manual configuration through operator
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/18 : Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Message publish/subscribe systems are required to process high message volumes with reduced latency and performance bottlenecks. The intelligent messaging application programming interface (API) introduced by the present invention is designed for high-volume, low-latency messaging. The API is part of a publish/subscribe middleware system. With the API, this system operates to, among other things, monitor system performance, including latency, in real time, employ topic-based and channel-based message communications, and dynamically optimize system interconnect configurations and message transmission protocols.

Claims

1. An application programming interface for communications between applications and a publish/subscribe middleware system, comprising:

a communication engine configured to function as a gateway for communications between applications and a publish/subscribe middleware system with the communication engine being operative, transparently to the applications, for using a dynamically selected message transport protocol and for monitoring and dynamically controlling, in real time, transport channel resources and flow;

one or more stubs for communications between the applications and the communication engine; and

a bus for communications between the one or more stubs and the communication engine.

2. An application programming interface as in claim 1, wherein the bus is an inter-process or intra-process communications bus.

3. An application programming interface as in claim 1, with the communication engine being further operative for dynamically adjusting the number of messages packed in a frame.

4. An application programming interface as in claim 1, with the communication engine being further operative for session-based fault tolerance.

5. An application programming interface as in claim 1, with the communication engine being further operative for temporary caching of messages.

6. An application programming interface as in claim 1, with the communication engine being further operative for value-added message processing.

7. An application programming interface as in claim 6, wherein the value-added message processing includes deployment of a content-based access control list with each entry in the list being associated with a an access condition and action.

8. An application programming interface as in claim 1, with the communication engine being further operative for registering with and becoming logically connected to a messaging appliance in the publish/subscribe middleware system.

9. An application programming interface as in claim 8, wherein the registration is a logging request and a subscription is topic-based, where a topic defines a shared-access domain as to which the application programming interface has a publish/subscribe entitlement.

10. An application programming interface as in claim 1, with the communication engine being further operative for late schema binding.

11. An application programming interface as in claim 1, with the communication engine being further operative for partial message publishing.

12. An application programming interface as in claim 1, with the communication engine being further operative for direct memory access to stored messages by the applications.

13. An application programming interface as in claim 1, with the communication engine being further operative for handling bulk messaging.

14. An application programming interface as in claim 12, wherein handling the bulk messaging involves message queuing with a restriction to avoid queue overflow and communication latency.

15. An application programming interface as in claim 1, wherein the real time message transport resources and flow control employs a policy of either identifying and disregarding old messages or blending messages.

16. An application programming interface as in claim 15, wherein the policy is applied globally to all message transport paths associated with the application programming interface.

17. An application programming interface as in claim 15, wherein the policy is user defined.

18. An application programming interface as in claim 15, wherein the policy is defined and implemented at application subscription time.

19. An application programming interface as in claim 1, with the communication engine being further operative for handling messages in raw compressed data format and binding the raw data to its schema.

20. An application programming interface as in claim 6, wherein the value-added message processing is defined during application registration.

21. An application programming interface as in claim 1, with the communication engine being further operative to offload message processing to an interface card.

22. An application programming interface as in claim 1, wherein the publish/subscribe middleware system includes a messaging appliance, and wherein the protocol optimization is distributed between the messaging appliance and the application programming interface in a master-slave-based configuration with the application programming interface being the slave.

23. An application programming interface as in claim 2, wherein the inter-process communications bus, if used, is implemented using sockets or shared memory and the intra-process communications bus, if used, is implemented using a function call.

33. An application programming interface as in claim 23, wherein the communication engine and the one or more stubs are compiled and linked to the applications which use the application programming interface for communicating with the publish/subscribe middleware system.

34. An application programming interface as in claim 23, with the communication engine being further operative for late binding schema.

35. An application programming interface as in claim 34, wherein the application delivery routing engine is operative to bind schema to raw message data, thereby allowing the applications to transparently access message information.

36. An application programming interface as in claim 1, further comprising a presentation engine operative to translate between application data format and messaging data schema for ingress and egress messages to and from the applications.

24. An application programming interface for communications between applications and a publish/subscribe middleware system, comprising:

a communication engine configured to function as a gateway for communications between applications and a publish/subscribe middleware system, the communication engine having logical layers including a message layer and a message transport layer, wherein the message layer includes an application delivery routing engine, an administrative message layer and a message routing engine and wherein the message transport layer includes a channel management portion for controlling transport paths of messages handled by the message layer in real time based on system resources usage;

one or more stubs for communications between the applications and the communication engine; and

a bus for communications between the one or more stubs and the communication engine.

25. An application programming interface as in claim 24, wherein the communication engine is deployed on top of an operating system.

26. An application programming interface as in claim 24, wherein the operating system includes a driver for an interface card through which the channel management portion interfaces with a physical medium for transporting messages to and from the applications.

27. An application programming interface as in claim 26, wherein the interface card is a network interface card operative for memory interconnect or for message processing offloading.

28. An application programming interface as in claim 26, wherein the interface card includes a hardware-based networking I/O (input/output) stack and is operative for direct memory access and caching for transmission.

29. An application programming interface as in claim 24, wherein the message routing engine includes a transport protocol optimization service portion.

30. An application programming interface as in claim 24, wherein the application delivery routing engine is operative for mapping applications to topic subscriptions.

31. An application programming interface as in claim 24, wherein the channel management portion controls a plurality of channels and the application delivery routing engine delivers messages to applications based on the mapping.

32. An application programming interface as in claim 30, wherein the administrative message layer handles administrative messages and the routing and application delivery routing engines handle data messages.