Protocol agnostic message oriented middleware for IoT, SaaS and enterprise integration

• US 10,484,251 B1
• Filed: 11/22/2016
• Issued: 11/19/2019
• Est. Priority Date: 11/24/2015
• Status: Active Grant

• Current Assignee: SRB Technologies, Inc.
• Original Assignee: SRB Technologies, Inc.
• Inventors: Gupta, Bramh, Zhang, Eamin, Yatzeck, Frederick
• Primary Examiner(s): Keller, Michael A
• Assistant Examiner(s): Duong, Thao D
• Application Number:
  US15/359,388
• Time in Patent Office: 1,092 Days
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/20 Network management software packages
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A method for providing a protocol agnostic message oriented middleware for IoT, SaaS and enterprise application integration. The method includes connecting a first application and device to a protocol-less integration middleware broker. Further, the method includes converting data of an industry standard integration protocol from the first application and device to a common protocol used within the protocol-less integration middleware broker. Furthermore, the method includes converting the data from the common protocol to a desired protocol pertaining to a second application and device. Moreover, the method includes exchanging data to the second application and device wherein the data is transformed from one protocol to another.

Claims

1. A computer-implemented method for providing protocol agnostic message oriented middleware for integration, the computer-implemented method comprising:

connecting a first application and device to a protocol-less integration middleware broker, wherein the protocol-less integration middleware broker does not have a proprietary application programming interface (API) stored for integrating the first application and device with a second application and device;

converting data of an industry standard integration protocol from the first application and device to a common protocol used within the protocol-less integration middleware broker;

converting the data from the common protocol to a desired protocol pertaining to the second application and device; and

exchanging data to the second application and device wherein the data is transformed from one protocol to another protocol.

2. The computer-implemented method of claim 1 and further comprising:

supporting all industry standard integration protocols thereby providing hooks to the protocol-less integration middleware broker using any of the preferred integration protocol of connecting devices, applications and systems, wherein the protocol-less middleware broker is capable of establishing connection between any devices, sensors, enterprise software, relational databases, and SaaS applications.

3. The computer-implemented method of claim 1, wherein converting data from one protocol to another protocol achieves easy integration of diverse devices and systems to connect together with least effort and cost.

4. The computer-implemented method of claim 1 and further comprising:

sending a message in a first protocol to a receiving application that receives the message in a second protocol;

converting the message to a common protocol;

processing the message within the protocol-less integration middleware broker using the common protocol; and

converting the information to a second desired protocol by a second application.

5. The computer-implemented method of claim 1 and further comprising:

allowing on-premise and site specific application to collaborate locally without the hop to the cloud on the centralized enterprise messaging broker.

6. The computer-implemented method of claim 5 further comprising a hybrid messaging cloud which uses a message routing pattern.

7. A computer program product stored on a non-transitory computer-readable medium that when executed by a processor, performs a method for providing protocol agnostic message oriented middleware for integration, the computer program product comprising:

connecting a first application and device to a protocol-less integration middleware broker, wherein the protocol-less integration middleware broker does not have a proprietary application programming interface (API) stored for integrating the first application and device with a second application and device;

converting data of an industry standard integration protocol from the first application and device to a common protocol used within the protocol-less integration middleware broker;

converting the data from the common protocol to a desired protocol pertaining to a second application and device; and

exchanging data to the second application and device wherein the data is transformed from one protocol to another protocol.

8. The computer program product of claim 7 and further comprising:

supporting all industry standard integration protocols thereby providing hooks to the protocol-less integration middleware broker using any of the preferred integration protocol of connecting devices, applications and systems, wherein the protocol-less integration middleware broker is capable of establishing connection between any devices, sensors, enterprise software, relational databases, and SaaS applications.

9. The computer program product of claim 7 wherein converting data from one protocol to another protocol achieves easy integration of diverse devices and systems to connect together with least effort and cost.

10. The computer program product of claim 7 and further comprising:

sending a message in a first protocol to a receiving application that receives the message in a second protocol;

converting the message to a common protocol;

processing the message within the protocol-less integration middleware broker using the common protocol; and

converting the information to a second desired protocol by a second application.

11. The computer program product of claim 7 and further comprising:

allowing on-premise and site specific application to collaborate locally without the hop to the cloud on the centralized enterprise messaging broker.

12. The computer program product of claim 11 further comprising a hybrid messaging cloud which uses a message routing pattern.

13. A system for providing protocol agnostic message oriented middleware for integration using a server, the server comprising a plurality of processors, the system comprising:

a suite of adapters and connectors that enable the ability to support all and any standard integration protocol thereby allowing any system to send and receive data using integration protocol of its own choice;

wherein the adapters comprise first processors of the plurality of processors coupled with a memory, the first processors configured for protocol conversion using the industry standard protocols, wherein a first adapter connects a first application to a protocol-less integration middleware broker and a second adapter connects a second application to the protocol-less integration middleware broker, and wherein the protocol-less integration middleware broker does not have a proprietary application programming interface (API) stored for integrating the first application with the second application;

wherein the connectors comprise second processors of the plurality of processors coupled with a memory, wherein the second processors are configured for application specific protocol conversion; and

a core message broker communicatively coupled with the suite of adapters and connectors responsible for routing, indirection and transformation.

14. The system of claim 13, wherein the suite of adapters and connectors includes the first application and the second application.

15. The system of claim 13, Wherein the adapters provide support to all standard protocols so that any system can send and receive data using the integration protocol of its own choice, and wherein the protocol-less integration middleware broker is capable of establishing connection between any devices, sensors, enterprise software, relational databases, and SaaS applications.

16. The system of claim 13 wherein the adapters convert any standard integration protocols to a common protocol used within the protocol-less integration middleware broker thereby a protocol-less or protocol agnostic middleware integration platform is established.

17. The system of claim 13 and further comprising:

a hybrid messaging cloud to federate and deliver messages to local brokers one of the centralized cloud and enterprise broker.

18. The system of claim 13 and further comprising:

an IoT Analytics real-time engine configured with the suite of adapters and connectors to deliver unstructured device data to the protocol-less integration middleware broker; and

a component engine configured in the protocol-less integration middleware broker to store and index the unstructured data in a timer sequence database.