CN118890389A - An instant messaging method, server, client and system based on MQTT protocol - Google Patents

Abstract

The invention discloses an instant messaging method based on an MQTT protocol, which is applied to a server and comprises the following steps: receiving a message data PUBLISH packet sent by a client; sending a confirmation message PUBACK packet to the client; wherein the acknowledgement message PUBACK packet includes a payload that includes an identification of at least 8 bytes of acknowledgement message PUBACK packet. The invention also discloses an instant messaging method based on the MQTT protocol, which is applied to the client. The invention can realize that a plurality of clients and servers can respectively and conveniently manage the messages returned by the servers without increasing the sending quantity of the messages, thereby improving the convenience of the instant messaging message management. The invention also discloses a server, a client and a system for realizing the method.

Description

An instant messaging method, server, client and system based on MQTT protocol

Technical Field

The present invention relates to the field of satellite observation technology, and in particular to an instant messaging method, server, client and system based on the MQTT protocol.

Background Art

Message Queuing Telemetry Transport (MQTT) is a message protocol based on the Publish/Subscribe paradigm and developed by the International Organization for Standardization based on the ISO/IEC PRF 20922 standard. The MQTT protocol is lightweight, simple, open, and easy to implement, which makes it widely applicable. Based on these advantages, the MQTT protocol can also be applied to instant messaging of multiple clients. However, in the process of instant messaging applications, due to the interaction between multiple clients and servers, when the instant messaging client publishes a message (PUBLISH), the instant messaging server can only confirm the receipt of the message (PUBACK), and the confirmation message has no identification (confirmation message ID). If the confirmation message ID needs to be returned, the server needs to publish a message with an ID through PUBLISH, and the client needs to confirm the receipt of the message through PUBACK, so that the client and server can complete the operation of sending messages and recording IDs, which increases the message sending and processing volume of the server and client, and is very inconvenient for the client and server to manage messages.

Summary of the invention

In order to solve the above problems existing in the prior art, the present invention provides an instant messaging method, server, client and system based on the MQTT protocol. The technical problem to be solved by the present invention is achieved through the following technical solutions:

A first aspect of an embodiment of the present invention provides an instant messaging method based on the MQTT protocol, which is applied to a server and includes the following steps:

Receive the message data PUBLISH package sent by the client;

Sending a confirmation message PUBACK packet to the client; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes.

A second aspect of an embodiment of the present invention provides an instant messaging method based on the MQTT protocol, which is applied to a client and includes the following steps:

Receive a confirmation message PUBACK packet sent by the server; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes;

Parsing the confirmation message PUBACK packet;

Determine whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length; wherein the preset byte length is greater than or equal to 10 bytes;

If it is greater than or equal to the preset byte length, a correspondence between its own message data and the identifier of the confirmation message PUBACK packet is constructed according to the confirmation message PUBACK packet and the effective load.

In one embodiment of the present invention, constructing a correspondence between its own message data and an identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load includes:

Read the variable message header of the confirmation message PUBACK packet to obtain the identifier of the message data PUBLISH packet;

Read the payload of the confirmation message PUBACK packet to obtain the identifier of the confirmation message PUBACK packet;

Determine its own message data according to the identifier of the message data PUBLISH package;

Construct a correspondence between the message data of the device itself and the identifier of the confirmation message PUBACK packet.

In one embodiment of the present invention, the method further includes: when the remaining byte length of the confirmation message PUBACK packet is less than a preset byte length, deleting the confirmation message PUBACK packet, and marking the message data corresponding to the variable header in the confirmation message PUBACK packet as sending failure.

In one embodiment of the present invention, the method further comprises:

In response to a processing operation on the message data, a processing message PUBLISH package is sent to the server; wherein the subject name in the processing message PUBLISH package indicates the processing operation, and the payload of the processing message PUBLISH package includes an identifier of a confirmation message PUBACK package corresponding to the message data; the processing operation includes a withdrawal operation or a deletion operation.

In one embodiment of the present invention, the subject name is 3 to 5 bytes;

The payload in the PUBLISH packet of the processing message is at least 8 bytes.

In one embodiment of the present invention, the method further comprises:

Send file data to the server via HTTP protocol;

A file data PUBLISH packet is sent to a server; wherein the effective load in the file data PUBLISH packet includes an HTTP link of the file data returned by the server.

A third aspect of an embodiment of the present invention provides an instant messaging server based on the MQTT protocol, comprising:

The first receiving module is used to receive the message data PUBLISH package sent by the client;

A sending module is used to send a confirmation message PUBACK packet to the client; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes.

A fourth aspect of an embodiment of the present invention provides an instant messaging client based on the MQTT protocol, comprising:

A second receiving module is used to receive a confirmation message PUBACK packet sent by the server; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes;

A parsing module, used for parsing the confirmation message PUBACK packet;

A judging module, used to judge whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length; wherein the preset byte length is greater than or equal to 10 bytes;

The determination module is used to construct a corresponding relationship between its own message data and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load if it is greater than or equal to the preset byte length.

A fifth aspect of the embodiments of the present invention provides an instant messaging system based on the MQTT protocol, comprising: a server according to the third aspect of the embodiments of the present invention and a client according to the fourth aspect of the embodiments of the present invention.

Beneficial effects of the present invention:

The present invention carries the identifier of the confirmation message PUBACK packet through the effective load in the confirmation message PUBACK packet. Both the server and the client can obtain the identifier, and the messages returned by the server to the client can be managed on the local side through the identifier. Without increasing the amount of message sending, multiple clients and servers can each conveniently manage the messages returned by the server, thereby improving the convenience of instant messaging message management.

Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings.

The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

FIG1 is a flow chart of an instant messaging method based on the MQTT protocol provided by an embodiment of the present invention;

FIG2 is a schematic diagram of a flow chart of another instant messaging method based on the MQTT protocol provided by an embodiment of the present invention;

FIG3 is a block diagram of an instant messaging server based on the MQTT protocol provided in an embodiment of the present invention;

FIG. 4 is a block diagram of an instant messaging client based on the MQTT protocol provided in an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention is further described in detail below with reference to specific embodiments, but the embodiments of the present invention are not limited thereto.

The present invention aims to provide a safe, efficient and real-time communication service. By using the instant messaging system, information can be quickly transmitted within the organization, the collaborative office capability can be improved, and strong support can be provided for the decision-making and action of the organization.

As shown in FIG. 1 , a first aspect of an embodiment of the present invention provides an instant messaging method based on the MQTT protocol, which is applied to a server and includes the following steps:

Step 11: Receive the message data PUBLISH package sent by the client.

Step 12: Send a confirmation message PUBACK packet to the client.

The confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes.

In this embodiment, the message level is QoS=1. The Quality of Service (QoS) of the MQTT message queue represents the service quality of message transmission. QoS=1 means that the message arrives at least once. This level ensures that the message arrives, but the message may be repeated. The instant messaging client PUBLISH publishes the message, and the instant messaging server PUBACK confirms the receipt of the message, and returns the server's confirmation message PUBACK packet identifier to the client through the Payload of the PUBACK message, which is the ID of the confirmation message PUBACK packet. Payload is the effective load.

It should be noted that the PUBACK packet is used by the server to feedback to the client to confirm that the message sent by the client has been received. The PUBACK packet and the PUBLISH packet are message data packets. In the prior art, there is no Payload and no PUBACK packet ID in the PUBACK packet returned by the server. When used in instant messaging, multiple clients need to send messages to the server, and the server needs feedback. However, each client has the same identification for the PUBLISH packet, and the server cannot manage it when returning the PUBACK packet. The confirmation message PUBACK packet of this embodiment adds a Payload to the prior art, and the Payload at least includes the ID of the confirmation message PUBACK packet. The server can obtain the identification of the confirmation message PUBACK packet to facilitate the management of the confirmation message.

As shown in FIG. 2 , a second aspect of an embodiment of the present invention provides an instant messaging method based on the MQTT protocol, which is applied to a client and includes the following steps:

Step 21: Receive a confirmation message PUBACK packet sent by the server.

In this step, the client sends a message data PUBLISH packet to the server, and the server returns a confirmation message PUBACK packet to the client.

The confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes.

Step 22, parse the confirmation message PUBACK packet.

Step 23, determining whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length.

Among them, the preset byte length is greater than or equal to 10 bytes.

Step 24: If it is greater than or equal to the preset byte length, then a corresponding relationship between its own message data and the identifier of the confirmation message PUBACK packet is constructed according to the confirmation message PUBACK packet and the effective load.

In this embodiment, since the confirmation message PUBACK packet contains the Payload, the client needs to determine whether the remaining parsed byte length of the confirmation message PUBACK packet is valid when parsing. If it is valid, it means that the PUBACK packet is valid and usable. If it is invalid, the PUBACK packet is invalid and unusable. After confirming that the PUBACK packet is valid, a corresponding relationship between the message returned by the server and the local message data is established locally on the client to facilitate the subsequent management of all messages.

Here, in combination with the methods provided in the first and second aspects of the embodiments of the present invention, the instant messaging method for interaction between the server and the client of the present invention is described in detail. The third aspect of the embodiment of the present invention provides an instant messaging method based on the MQTT protocol, comprising the following steps: (the same contents as those in the first and second aspects of the embodiments of the present invention are not repeated here)

Step 31: The client sends a message data PUBLISH packet to the server.

Step 32: The server receives the message data PUBLISH packet sent by the client.

Step 33: The server sends a confirmation message PUBACK packet to the client.

The confirmation message PUBACK packet includes a payload, and the payload includes an identification of the confirmation message PUBACK packet of at least 8 bytes. Here, the payload can also carry other information, that is, the payload of the confirmation message PUBACK packet can be composed of the identification of the confirmation message PUBACK packet and other information. At this time, the bytes of the Payload are greater than 8, and the identification of the confirmation message PUBACK packet occupies at least 8 bytes.

In a feasible implementation, the identifier of the confirmation message PUBACK packet uses the long type, a total of 8 bytes, and occupies 64 bits, of which 43 bits are timestamps, 6 bits are node numbers, and 15 bits are sequence numbers. The identifier generated by the server is guaranteed to be incremental and unique. For example, the message data of the confirmation message PUBACK packet is shown in Table 1 below:

Table 1

Among them, MSB and LSB represent the identifier of the message data PUBLISH packet, Byte represents byte, and Bit represents bit.

Step 34: The client receives a confirmation message PUBACK packet sent by the server.

Step 35: The client parses the confirmation message PUBACK packet.

Step 36: The client determines whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to the preset byte length.

The preset byte length is greater than or equal to 10 bytes. The remaining byte length is the bytes following the remaining length in Table 1.

When the client parses the message at the remaining byte length, it is determined whether the value of the remaining byte length in the message is greater than or equal to 10 bytes. For example, as shown in Table 1, the preset byte length is 10, and when the message is parsed to the remaining length, it is determined whether the value here is equal to 10.

Step 37: If the length is greater than or equal to the preset byte length, the client constructs a corresponding relationship between its own message data and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load. The specific steps of step 37 include: Step 371-Step 374:

Step 371: If it is greater than or equal to the preset byte length, the client reads the variable message header of the confirmation message PUBACK packet to obtain the identifier of the message data PUBLISH packet.

Step 372, the client reads the payload of the confirmation message PUBACK packet and obtains the identifier of the confirmation message PUBACK packet. Steps 371 and 372 parse the same confirmation message PUBACK packet, and the identifier of the message data PUBLISH packet obtained by parsing corresponds to the identifier of the confirmation message PUBACK packet.

Step 373, the client determines its own message data according to the identifier of the message data PUBLISH package. In this step, the client can find the local message data corresponding to the identifier according to the identifier of the message data PUBLISH package in the confirmation message PUBACK package.

Step 374, the client constructs a correspondence between its own message data and the identifier of the corresponding confirmation message PUBACK packet. In this step, the correspondence between the found own message data and the identifier of the corresponding confirmation message PUBACK packet is stored, so as to facilitate the subsequent relevant processing of the own message data corresponding to the identifier of the returned confirmation message PUBACK packet.

Step 38: When the remaining byte length of the confirmation message PUBACK packet is less than the preset byte length, the confirmation message PUBACK packet is deleted, and the message data corresponding to the variable header in the read confirmation message PUBACK packet is marked as sending failure.

In a feasible implementation manner, based on the above embodiment, the correspondence between the own message data and the identifier of the confirmation message PUBACK packet has been established. When the client wants to withdraw or delete the message data corresponding to the message data PUBLISH packet, the following steps are included:

Step A1: In response to a processing operation on message data, the client sends a processing message PUBLISH packet to the server.

The subject name in the processing message PUBLISH packet indicates the processing operation, and the effective load includes the identifier of the confirmation message PUBACK packet corresponding to the message data; the processing operation includes a withdrawal operation or a deletion operation.

In this step, after the user performs the withdrawal or deletion processing operation on the client, the client sends a processing message PUBLISH package to the server. Here, on the basis of the traditional PUBLISH package, the subject name of the PUBLISH package is given a new value, which can indicate the withdrawal or deletion operation, and the corresponding confirmation message PUBACK package identifier is carried in the Payload of the PUBLISH package (the corresponding relationship has been established in the above embodiment). In this way, when the server receives and reads the processing message PUBLISH package, the server can uniquely determine which confirmation message PUBACK package is to be withdrawn or deleted.

Preferably, the subject name is 3 to 5 bytes; the payload in the PUBLISH packet of the processing message is at least 8 bytes.

In a feasible implementation, during the instant messaging process, the client and the server can transmit text, pictures, videos and other information. The text can be carried in the Payload of the PUBLISH message. The pictures or videos form files, which are transmitted via the HTTP protocol (Hypertext Transfer Protocol) or the Hypertext Transfer Protocol Secure, and the links to the files are carried in the Payload of the PUBLISH message. Specifically, the following steps are included:

Step B1, the client sends file data to the server via HTTP protocol (or Hypertext Transfer Protocol Secure), wherein the file data includes relatively large files such as pictures, videos, and audios.

Step B2, the server receives the file data and generates a link, and then sends the link of the file data to the client via HTTP protocol (or Hypertext Transfer Protocol Secure);

Step B3: The client sends a file data PUBLISH packet to the server.

The payload in the file data PUBLISH packet includes an HTTP link of the file data.

In this embodiment, when transmitting large file data, the HTTP protocol and the MQTT protocol are used for transmission respectively. The HTTP protocol transmits the file data, and the MQTT protocol transmits the link message of the file data, so that the file data transmission is not easy to be lost. At the same time, if the file data is damaged, it will not affect the sending of the MQTT message with the link. The file data sent through the HTTP protocol will not occupy the resources of other messages of the MQTT protocol, forming resource isolation.

Here, after receiving the file data PUBLISH package, the server sends the message to other clients in the form of a PUBLISH package, which can also be understood as the server forwarding the file data PUBLISH package.

As shown in FIG3 , a fourth aspect of an embodiment of the present invention provides an instant messaging server based on the MQTT protocol, including:

The first receiving module 41 is used to receive a message data PUBLISH packet sent by a client;

The sending module 42 is used to send a confirmation message PUBACK packet to the client; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes.

As shown in FIG. 4 , a fifth aspect of an embodiment of the present invention provides an instant messaging client based on the MQTT protocol, including:

The second receiving module 51 is used to receive a confirmation message PUBACK packet sent by the server; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes;

A parsing module 52, configured to parse a confirmation message PUBACK packet;

The judging module 53 is used to judge whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length; wherein the preset byte length is greater than or equal to 10 bytes;

The determination module 54 is used to construct a corresponding relationship between its own message data and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load if it is greater than or equal to the preset byte length.

In one embodiment of the present invention, constructing a correspondence between its own message data and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load includes:

Read the variable message header of the confirmation message PUBACK packet to obtain the identifier of the message data PUBLISH packet;

Read the payload of the confirmation message PUBACK packet and obtain the identifier of the confirmation message PUBACK packet;

Determine its own message data according to the identifier of the message data PUBLISH package;

Construct the correspondence between its own message data and the identifier of the confirmation message PUBACK packet.

In one embodiment of the present invention, it also includes: when the remaining byte length of the confirmation message PUBACK packet is less than the preset byte length, deleting the confirmation message PUBACK packet, and marking the message data corresponding to the variable header in the confirmation message PUBACK packet as sending failure.

In one embodiment of the present invention, it also includes:

In response to a processing operation on the message data, a processing message PUBLISH package is sent to the server; wherein the subject name in the processing message PUBLISH package indicates the processing operation, and the payload includes an identifier of a confirmation message PUBACK package corresponding to the message data; the processing operation includes a withdrawal operation or a deletion operation.

In one embodiment of the present invention, the subject name is 3 to 5 bytes; the payload in the processing message PUBLISH packet is at least 8 bytes.

In one embodiment of the present invention, the file data is sent to the server via the HTTP protocol;

A file data PUBLISH packet is sent to the server; wherein the effective load in the file data PUBLISH packet includes an HTTP link of the file data returned by the server.

A sixth aspect of an embodiment of the present invention provides an instant messaging system based on the MQTT protocol, including the server and client in the above embodiment of the present invention.

A seventh aspect of an embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, an instant messaging method based on the MQTT protocol provided in the above embodiment of the present invention is implemented.

An eighth aspect of an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of an instant messaging method based on the MQTT protocol provided in the above embodiment of the present invention are implemented.

The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware systems.

The method provided in the embodiment of the present invention can be applied to electronic devices. Specifically, the electronic device can be: a desktop computer, a portable computer, an intelligent mobile terminal, a server, etc. This is not limited here, and any electronic device that can implement the present invention belongs to the protection scope of the present invention.

As for the system/electronic device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

The present invention is described with reference to the flowcharts and/or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a system for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims (10)

1. An instant messaging method based on the MQTT protocol, applied to a server, characterized in that it comprises the following steps: Receive the message data PUBLISH package sent by the client; Sending a confirmation message PUBACK packet to the client; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes. 2. An instant messaging method based on the MQTT protocol, applied to a client, characterized in that it comprises the following steps: Receive a confirmation message PUBACK packet sent by the server; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes; Parsing the confirmation message PUBACK packet; Determine whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length; wherein the preset byte length is greater than or equal to 10 bytes; If it is greater than or equal to the preset byte length, a correspondence between its own message data and the identifier of the confirmation message PUBACK packet is constructed according to the confirmation message PUBACK packet and the effective load. 3. The method according to claim 2, wherein the step of constructing a correspondence between the message data of the device and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the payload comprises: Read the variable message header of the confirmation message PUBACK packet to obtain the identifier of the message data PUBLISH packet; Read the payload of the confirmation message PUBACK packet to obtain the identifier of the confirmation message PUBACK packet; Determine its own message data according to the identifier of the message data PUBLISH package; Construct a correspondence between the message data of the device itself and the identifier of the confirmation message PUBACK packet. 4. The method as claimed in claim 2 is characterized in that the method also includes: when the remaining byte length of the confirmation message PUBACK packet is less than a preset byte length, deleting the confirmation message PUBACK packet, and marking the message data corresponding to the variable header in the confirmation message PUBACK packet as sending failure. 5. The method according to claim 2, characterized in that the method further comprises: In response to a processing operation on the message data, a processing message PUBLISH package is sent to the server; wherein the subject name in the processing message PUBLISH package indicates the processing operation, and the payload of the processing message PUBLISH package includes an identifier of a confirmation message PUBACK package corresponding to the message data; the processing operation includes a withdrawal operation or a deletion operation. 6. The method according to claim 5, characterized in that the subject name is 3 to 5 bytes; The payload in the PUBLISH packet of the processing message is at least 8 bytes. 7. The method according to claim 2, characterized in that the method further comprises: Send file data to the server via HTTP protocol; A file data PUBLISH packet is sent to a server; wherein the effective load in the file data PUBLISH packet includes an HTTP link of the file data returned by the server. 8. An instant messaging server based on the MQTT protocol, comprising: The first receiving module is used to receive the message data PUBLISH package sent by the client; A sending module is used to send a confirmation message PUBACK packet to the client; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identification of the confirmation message PUBACK packet of at least 8 bytes. 9. An instant messaging client based on the MQTT protocol, comprising: A second receiving module is used to receive a confirmation message PUBACK packet sent by the server; wherein the confirmation message PUBACK packet includes a valid load, and the valid load includes an identifier of the confirmation message PUBACK packet of at least 8 bytes; A parsing module, used for parsing the confirmation message PUBACK packet; A judging module, used to judge whether the remaining byte length of the confirmation message PUBACK packet is greater than or equal to a preset byte length; wherein the preset byte length is greater than or equal to 10 bytes; The determination module is used to construct a corresponding relationship between its own message data and the identifier of the confirmation message PUBACK packet according to the confirmation message PUBACK packet and the effective load if it is greater than or equal to the preset byte length. 10. An instant messaging system based on the MQTT protocol, comprising: the server according to claim 8 and the client according to claim 9.