Method for transport agnostic communication between internet of things client and broker

• US 10,708,360 B2
• Filed: 03/14/2017
• Issued: 07/07/2020
• Est. Priority Date: 03/14/2017
• Status: Active Grant

• Current Assignee: infiswift Technologies, Inc.
• Original Assignee: infiswift Technologies, Inc.
• Inventors: Venkatesan, Sivakumar, Thulasingam, Saravanan
• Primary Examiner(s): Higa, Brendan Y
• Application Number:
  US15/458,764
• Publication Number:
  US 20180270310A1
• Time in Patent Office: 1,211 Days
• CPC Class Codes: G05B 2219/33149 Publisher subscriber, publisher, master broadcasts data to slaves, subscriber
• CPC Class Codes: H04L 12/1836 with heterogeneous network architecture
• CPC Class Codes: H04L 12/283 Processing of data at an internetworking point of a home automation network
• CPC Class Codes: H04L 12/2836 Protocol conversion between an external network and a home network controlling appliance services of a home automation network from a device located outside the home and the home network H04L12/2818; protocol conversion H04L69/08; adaptation of digital video signals for transport over a specific home network H04N7/24
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• 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/22 Parsing or analysis of headers

Abstract

Methods are provided for communicating between devices in a network and remote servers, which may be located behind intermediate devices such as load balancers, by encapsulating messages sent by those devices and, in one implementation, to a load balancer in a transport header that may be understood by that load balancer; decapsulating the message from the transport header; re-encapuslating the message in a GRE tunnel and passing the message to a server, where the GRE tunnel is removed. Methods are also provided for communicating between devices in a network and local gateways by encapsulating messages sent by those devices and, in one implementation, to a load balancer in a transport header that may be understood by that gateway, and decapsulating the message from the transport header at the gateway.

Claims

1. A system for connecting devices into a data network, the system comprising:

a first device, comprising;

at least memory comprising instructions;

at least a processor configured to execute the instructions to generate at least a message to be sent from said first device on the network to a second device, wherein said message is encapsulated using the MQTT messaging protocol with at least a first MQTT header to create one or more MQTT messages;

and said message is further encapsulated in at least a first transport header that may be understood by a second device on the network;

and transmitting said message encapsulated by said transport header from said first device to said second device;

said second device comprising;

at least memory comprising instructions;

at least a processor configured to process the MQTT messages and to decapsulate said message by removing said first MQTT header at said second device, and to execute the instructions to decapsulate said message by removing said first transport header at said second device, and to select one of the plurality of MQTT brokers to forward the decapsulated message by using a combination of a first device identifier, an MQTT topic, and at least a Quality of Service, in order to achieve an efficient distribution with low latency;

encapsulate said message at said second device in at least a second header that may be understood by a third device on the network;

and transmit said message from said second device to at least one of a plurality of said third devices, where said at least a processor on said second device is also configured to determine a load on each of said plurality of third devices and routing said message to one of said plurality of third devices based at least in part on said determination by said second device of relative loads on said plurality of third devices; and

the plurality of third devices comprising;

at least memory comprising instructions;

at least a processor configured to execute the instructions to decapsulate said message on said third device by removing said second header;

wherein said second device and said plurality of third devices are at a separate physical location from said first device;

wherein said third devices comprise a plurality of message brokers within a server cluster;

wherein said second device is connected with a plurality of said third devices; and

wherein said second device is aware of at least a messaging protocol used to communicate between said first device and said third device.

2. The system of claim 1 where said second device maintains different MQTT brokers to select from depending on a Quality of Service level in the said MQTT messages to enable low latency for higher Quality of Service levels and higher latency for lower Quality of Service levels.

3. The system of claim 1 where said first device encapsulates said message inside a GRE tunnel.

4. The system of claim 1 where said second device is capable of interpreting messages based on multiple transport protocols.

5. The system of claim 1 where said third device is capable of interpreting messages based on multiple transport protocols.

6. The system of claim 1 where said third device decapsulates JSON headers.

7. The system of claim 1 where said first device generates messages using the MQTT protocol.

8. The system of claim 1 where at least some communications between said first device and said second device take place using a cellular network.

9. The system of claim 1 where at least some communications between said first device and said second device take place using a wireless radio network.

10. The system of claim 1 where said second device is a load balancer.

11. A method for connecting devices into a data network, the method comprising:

generating at least a message to be sent from a first device on the network;

encapsulating said message using the MQTT messaging protocol with at least a first MQTT header to create one or more MQTT messages;

further encapsulating said message in at least a first transport header that may be understood by a second device on the network;

transmitting said message encapsulated in said transport header from said first device to said second device;

decapsulating said message by removing said first header at said second device;

encapsulating said message at said second device in at least a second header that may be understood by a third device on the network;

transmitting said message from said second device to at least one of a plurality of said third devices;

determining a load on each of said plurality of third devices;

routing said message to one of said plurality of third devices based at least in part on said determination by said second device of relative loads on said plurality of third devices; and

decapsulating said message on said third device by removing said second header;

configuring at least a processor to process MQTT messages and to decapsulate said message by removing said first MQTT header at said second device, and to execute the instructions to decapsulate said message by removing said first transport header at said second device, and to select one of the plurality of MQTT brokers to forward the decapsulated message by using a combination of the said first device identifier, an MQTT topic, and at least a Quality of Service, in order to achieve an efficient distribution with low latency;

wherein said second device and said plurality of third devices are at a separate physical location from said first device;

wherein said third devices comprise a plurality of message brokers within a server cluster;

wherein said second device is connected with a plurality of said third devices; and

wherein said second device is aware of at least a messaging protocol used to communicate between said first device and said third device.

12. The method of claim 11 where said second device maintains different MQTT brokers to select from depending on a Quality of Service level in the said MQTT messages to enable low latency for higher Quality of Service levels and higher latency for lower Quality of Service levels.

13. The method of claim 11 where said message is encapsulated by said first device inside a GRE tunnel.

14. The method of claim 11 where said second device is capable of interpreting messages based on multiple transport protocols.

15. The method of claim 11 where said third device is capable of interpreting messages based on multiple transport protocols.

16. The method of claim 11 where said third device decapsulates JSON headers.

17. The method of claim 11 where said first device generates messages using the MQTT protocol.

18. The method of claim 11 where at least some communications between said first device and said second device take place using a cellular network.

19. The method of claim 11 where at least some communications between said first device and said second device take place using a wireless radio network.

20. The method of claim 11 where said second device is a load balancer.