A method of load balancing based on mqtt protocol multi-broker

Abstract

The invention discloses a method for realizing load balancing based on the MQTT protocol with multiple Brokers, comprising the steps of: a device obtains the information of the gateway service and sends a request to the gateway service; forwards the request to the business service through the gateway service; the business service obtains the information list of all Brokers and sends Assemble it into a key, and determine the parameter value forwarded by the gateway service; the business service obtains the number of device connections corresponding to each Broker; the business service obtains the Broker information according to the load balancing algorithm; returns the Broker information to the device; the device sends a connect request to the Broker ; Assemble Broker's information into a key; redis performs an auto-increment operation; Broker assembles the packet information and returns it to the device and maintains a heartbeat with the device. The present invention can dynamically switch the Broker connected to the device without upgrading the device, and the number of device connections is controllable.

Description

technical field [0001] The invention relates to the technical field of communication, in particular to a method for realizing load balancing based on MQTT protocol with multiple Brokers. Background technique [0002] The MQTT protocol is used in smart devices, so that after the device establishes a connection with the Broker server, it can maintain a long connection (that is, the heartbeat detection mechanism). At present, most solutions are to generate certificate information (also called a certificate file, which contains the domain name or IP address of the Broker server) for the device, and burn the certificate information into the device. At this time, the address of the Broker server will be After burning into the device, the device obtains the address of the Broker server through the burned domain name or IP, so that the device establishes a connection with the Broker server through the MQTT protocol. This solution has the following problems: First, the same domain n...

AI Technical Summary

Problems solved by technology

This solution has the following problems: First, the same domain name or IP is used for the general certificate burning, which will cause a large number of subsequent devices to be connected to the same Broker server, and there may be downtime problems; Second, even if a different domain name or IP is used, it will cause a device to connect to a fixed Broker server. If the Broker server is down, the device will not be able to connect to the Broker server, and the device needs to be upgraded to connect The new Broker address, on the one hand, affects the connection of the device. The device needs to perform a lot of operations such as upgrading, and the device cannot be restored to the normal state in time. On the other hand, it is related to the domain name or IP burned by the device and the number of devices. , the number of Broker connections is affected by the device certificate and the number of devices, which may cause the number of connections to a certain Broker server to be uncontrollable, making it difficult to control the number of devices connected to the Broker server

Therefore, in view of the above technical design defects, it is necessary to provide a method based on MQTT protocol multi-Broker to achieve load balancing, to solve the problem that the expansion of the number of devices does not affect the peak of the number of Broker server connections, and to ensure that the burning of device certificates is not limited The device is connected to a fixed Broker server, so as to solve the problem that the device cannot be connected due to the downtime of a certain Broker service

Images