CN111683158B - MQTT protocol communication method for realizing synchronous request response - Google Patents
MQTT protocol communication method for realizing synchronous request response Download PDFInfo
- Publication number
- CN111683158B CN111683158B CN202010804340.5A CN202010804340A CN111683158B CN 111683158 B CN111683158 B CN 111683158B CN 202010804340 A CN202010804340 A CN 202010804340A CN 111683158 B CN111683158 B CN 111683158B
- Authority
- CN
- China
- Prior art keywords
- mqtt
- message
- request
- response
- connection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an MQTT protocol communication method for realizing synchronous request response, which belongs to the network communication technology.A TCP connection for synchronous communication, namely a Service connection, is additionally arranged between each MQTT client and an MQTT proxy server; and adds a control message for request SERVICEREQ/response SERVICERSP with a value of 15. The invention supports synchronous communication through an extended service protocol, and uses TCP connection between each MQTT client and the MQTT proxy server as a channel of a synchronous request, thereby enabling the MQTT proxy server to realize synchronous communication between the clients through forwarding and transparent transmission, supporting the synchronous request of request/response, and being capable of being downward compatible with the current MQTT protocol.
Description
Technical Field
The invention belongs to the network communication technology, and particularly relates to an MQTT protocol communication method for realizing synchronous request response.
Background
In the existing internet of things technology, even if corresponding equipment works in an environment with low bandwidth and unreliable network through an MQTT protocol, network data interaction can be effectively carried out, and then a remote sensor and control equipment can communicate with a server in time.
However, as shown in fig. 1, in the current MQTT communication topology, only one TCP connection is established between an MQTT client and an MQTT proxy server, and is used for publishing and subscribing a topic, and the connection is referred to as a Message connection. However, as shown in fig. 3, since the MQTT protocol is based on asynchronous communication, it cannot implement synchronous communication of request response, and therefore, the conventional MQTT protocol cannot meet the technical development requirement of the internet of things.
Disclosure of Invention
The purpose of the invention is as follows: the invention aims to solve the defects in the prior art and provides an MQTT protocol communication method for realizing synchronous request response.
The technical scheme is as follows: the MQTT protocol communication method for realizing the synchronous request response comprises an MQTT proxy server and a plurality of MQTT clients, wherein each MQTT client establishes a TCP connection for publishing and subscribing a theme with the MQTT proxy server, and the TCP connection is published and subscribed, namely, Message connection; each MQTT client also is additionally provided with a TCP connection for synchronous communication, namely a Service connection channel, with the MQTT proxy server; the added value of 15 in the MQTT protocol is used for control messages of request SERVICEREQ/response SERVICERSP, and the request SERVICEREQ/response SERVICERSP control messages comprise Fixed header, Variable header and Payload.
The specific steps for realizing the synchronous request response are as follows:
step 1, if an MQTT client A needs to perform request response interaction with an MQTT client B, the MQTT client A and the MQTT client B need to establish a Service connection channel and perform periodic keep-alive operation during initialization;
step 2, after the Service connection channel is established, the MQTT client A sends SERVICEREQ requests to the MQTT proxy server, the MQTT proxy server transmits the requests to the MQTT client B, the MQTT client B analyzes the received request content and sends SERVICERSP requests to the MQTT proxy server, and the MQTT proxy server transmits the responses to the MQTT client A for processing; the complete request response interaction process is completed; and 3, sending Service DISCONNECT to close the Service channel when the MQTT client A and the MQTT client B are offline.
Further, the forwarding process of the MQTT request response in step 2 is as follows:
step 2.1, after receiving a request message (SERVICEREQ request) sent by a requester A (namely, an MQTT client A), the MQTT proxy server is put into a cache pool;
step 2.2, the MQTT proxy server takes out the request message from the request cache pool and receives a client identifier (namely an MQTT client B) according to the message;
step 2.3, the responder B sends a response message (SERVICERSP request) to the MQTT proxy server after receiving the request message;
step 2.4, the MQTT proxy server receives the response message and stores the response message into a response message buffer pool, removes the corresponding request message from the request message buffer pool, and if the response message is not received or the responder B is not online, makes a plurality of attempts within a corresponding time period (for example, 20S);
step 2.5, the MQTT proxy server takes out the response message from the response message cache pool and forwards the response message to the requester A according to the message receiving client identifier;
step 2.6, the requester A receives the response message and returns a response confirmation frame to the MQTT proxy server;
step 2.7, the MQTT proxy server removes the response message from the response message buffer pool, otherwise, it tries to resend many times. In the request SERVICEREQ/response SERVICERSP control message, the flag bit 0 of the control message type of the fixed header indicates whether the request or the response is, 0 represents the request control message, and 1 represents the response control message; the message identifier of the variable header Variableheader represents the unique identifier of the request, and the message identifier of the response is the same as the message identifier of the request.
In order to realize the creation of Service connection, in the fixed header of the CONNECT control Message of the MQTT protocol, the flag bit 0 of the control Message type is used to indicate whether a Message connection or a Service connection is created, 0 represents the Message connection, and 1 represents the Service connection.
In order to realize Service connection confirmation, in a fixed header of a CONNACK control Message of an MQTT protocol, a control Message type flag bit 0 bit indicates whether the connection confirmation is a Message connection or a Service connection, 0 represents the Message connection, and 1 represents the Service connection.
In order to realize the Service connection keep-alive request, in the PINGRQ control Message fixed header of the MQTT protocol, the flag bit 0 of the control Message type indicates whether the connection keep-alive request is a Message connection or a Service connection, 0 represents the Message connection, and 1 represents the Service connection.
In order to realize Service connection keep-alive response, in a PINGRSP control Message fixed header of an MQTT protocol, a control Message type flag bit 0 bit of the PINGRSP control Message fixed header indicates whether the connection keep-alive response is a Message connection or a Service connection, 0 represents the Message connection, and 1 represents the Service connection.
In order to realize the closing of Service connection, in a DISCONNECT control Message fixed header of an MQTT protocol, a control Message type flag bit 0 bit of the DISCONNECT control Message fixed header indicates whether the Message connection or the Service connection is closed, 0 represents the Message connection, and 1 represents the Service connection.
Has the advantages that: the invention supports synchronous communication through an extended service protocol, and takes TCP connection between each MQTT client and the MQTT proxy server as a channel of a synchronous request, thereby enabling the MQTT proxy server to realize the synchronous communication between the clients through forwarding and transparent transmission. Compared with the prior art, the invention has the following advantages: support request/response synchronous request and can be downward compatible with the current MQTT protocol.
Drawings
FIG. 1 is a prior art MQTT communication topology;
FIG. 2 is a MQTT communication topology diagram in the present invention;
FIG. 3 is a flow diagram of a conventional subscription publishing process;
FIG. 4 is a flow chart of a request response of the present invention;
FIG. 5 is an interaction diagram of MQTT request response of the present invention
FIG. 6 is a diagram illustrating a complete request-response interaction flow in the embodiment.
Detailed Description
The technical solution of the present invention is described in detail below, but the scope of the present invention is not limited to the embodiments.
As shown in fig. 2 and fig. 5, the present embodiment relates to an MQTT proxy server and a plurality of MQTT clients, each MQTT client establishes a TCP connection for publishing and subscribing to a topic with the MQTT proxy server, and the TCP connection is published and subscribed, that is, a Message connection; each MQTT client is also additionally provided with a TCP connection for synchronous communication, namely a Service connection, with the MQTT proxy server; the MQTT protocol adds a value of 15 control messages for request SERVICEREQ/response SERVICERSP.
The request SERVICEREQ/response SERVICERSP control message includes a Fixed header, a Variable header, and a Payload.
In the request SERVICEREQ/response SERVICERSP control message of this embodiment, bit 0 of the flag bit of the control message type of the fixed header indicates whether the request is a request or a response, 0 represents the request control message, and 1 represents the response control message, which is specifically shown in table 1.
TABLE 1 fixed header of request SERVICEREQ/response SERVICERSP control messages
In the request SERVICEREQ/response SERVICERSP control message of this embodiment, the message identifier of the variable header indicates the unique identifier of the current request, and the message identifier of the response is the same as the message identifier of the request, which is specifically shown in table 2.
TABLE 2 variable header of request SERVICEREQ/response SERVICERSP control message
In this embodiment, the protocol communication method for implementing synchronous request response specifically includes the following steps:
(1) if the MQTT client A needs to perform request response interaction with the MQTT client B, the MQTT client A and the MQTT client B need to establish Service connection and perform periodic keep-alive operation during initialization;
(2) after the Service connection channel is established, the MQTT client A sends SERVICEREQ a request to the MQTT proxy server, the MQTT proxy server transmits the request to the MQTT client B, the MQTT client B analyzes the received request content and sends SERVICERSP the request to the MQTT proxy server, and the MQTT proxy server transmits the response to the MQTT client A for processing; the complete request response interaction process is completed;
(3) and when the MQTT client A and the MQTT client B are offline, sending Service DISCONNECT to close the Service channel.
As shown in fig. 4 and fig. 6, the forwarding process of MQTT request response is as follows:
step 2.1, after receiving the request message sent by the requester A, the MQTT proxy server puts the request message into a cache pool;
step 2.2, the MQTT proxy server takes out the request message from the request cache pool and forwards the request message to a responder B according to the message receiving client identifier (shown in table 2);
step 2.3, the responder B sends a response message to the MQTT proxy server after receiving the request message;
step 2.4, the MQTT proxy server receives the response message and stores the response message into a response message buffer pool, removes the corresponding request message from the request message buffer pool, and if the response message is not received or the responder B is not online, the MQTT proxy server makes a plurality of attempts within 20S;
step 2.5, the MQTT proxy server takes out the response message from the response message cache pool and forwards the response message to the requester A according to the message receiving client identifier (shown in the table 2);
step 2.6, the requester A receives the response message and returns a response confirmation frame to the MQTT proxy server;
step 2.7, the MQTT proxy server removes the response message from the response message buffer pool, otherwise, it tries to resend many times.
In order to implement Service connection creation, in this embodiment, in a fixed header of a CONNECT control Message of an MQTT protocol, a flag bit 0 of a control Message type is used to indicate whether a Message connection or a Service connection is created, where 0 represents the Message connection, and 1 represents the Service connection. Specifically, the results are shown in Table 3.
Table 3 CONNECT control message fixed header supporting Service connection
In order to implement Service connection confirmation, in this embodiment, in the fixed header of the CONNACK control Message of the MQTT protocol, a control Message type flag bit 0 bit indicates whether the connection confirmation is a Message connection or a Service connection, 0 indicates the Message connection, and 1 indicates the Service connection. The details are shown in Table 4.
Table 4 CONNACK control message fixed header supporting Service connection
In order to implement a Service connection keep-alive request, in the fixed header of the PINGREQ control packet in the MQTT protocol in this embodiment, a flag bit 0 of a control packet type indicates whether the connection keep-alive request is a Message connection or a Service connection, 0 represents the Message connection, and 1 represents the Service connection. Specifically, the results are shown in Table 5.
Table 5 PINGREQ control message fixed header supporting Service connection
In order to implement Service connection keep-alive response, in the embodiment, in the PINGRSP control packet fixed header of the MQTT protocol, a control packet type flag bit 0 bit indicates whether the keep-alive response is connected by a Message connection or a Service connection, 0 indicates the Message connection, and 1 indicates the Service connection. Specifically, the results are shown in Table 6.
Table 6 PINGRSP control packet fixed header supporting Service connection
In order to implement the Service connection shutdown, in this embodiment, in the DISCONNECT control Message fixed header of the MQTT protocol, a control Message type flag bit 0 bit indicates whether the Message connection or the Service connection is closed, 0 indicates the Message connection, and 1 indicates the Service connection. Specifically, the results are shown in Table 7.
Table 7 DISCONNECT control message fixed header supporting Service connection
It can be seen from the above embodiments that the present invention supports synchronous communication through an extended service protocol, and TCP connections between each MQTT client (subscriber, publisher) and the MQTT proxy server are used as channels for synchronous requests, so that the MQTT proxy server realizes synchronous communication between clients through forwarding and transparent transmission.
Claims (3)
1. An MQTT protocol communication method for realizing synchronous request response comprises an MQTT proxy server and a plurality of MQTT clients, wherein each MQTT client establishes a TCP connection, namely a Message connection, for publishing and subscribing a theme with the MQTT proxy server; the method is characterized in that: each MQTT client also is additionally provided with a TCP connection for synchronous communication, namely a Service connection channel, with the MQTT proxy server; the added value of the control message of 15 in the MQTT protocol is used for requesting SERVICEREQ/responding SERVICERSP, and the request SERVICEREQ/responding SERVICERSP control message comprises fixed header Fixedheader, Variable header and Payload;
in a fixed header of a CONNECT control Message of an MQTT protocol, a control Message type flag bit 0 bit of the CONNECT control Message is used for representing whether a Message connection or a Service connection is established, wherein 0 represents the Message connection, and 1 represents the Service connection;
in a fixed header of a CONNACK control Message of an MQTT protocol, a control Message type flag bit 0 of the CONNACK control Message indicates whether the connection is confirmed by Message connection or Service connection, 0 represents the Message connection, and 1 represents the Service connection;
in a PINGRQ control Message fixed header of an MQTT protocol, a control Message type flag bit 0 of the PINGREQ control Message fixed header indicates whether a Message connection or a Service connection is connected with a keep-alive request, 0 represents the Message connection, and 1 represents the Service connection;
in a PINGRSP control Message fixed header of an MQTT protocol, a control Message type flag bit 0 of the PINGRSP control Message fixed header indicates that the connection keep-alive response is Message connection or Service connection, 0 represents the Message connection, and 1 represents the Service connection;
in a DISCONNECT control Message fixed header of an MQTT protocol, a control Message type flag bit 0 of the control Message fixed header indicates whether the Message connection or the Service connection is closed, 0 represents the Message connection, and 1 represents the Service connection;
the MQTT protocol communication method for realizing synchronous request response comprises the following steps:
step 1, if an MQTT client A needs to perform request response interaction with an MQTT client B, the MQTT client A and the MQTT client B need to establish a Service connection channel and perform periodic keep-alive operation during initialization;
step 2, after the Service connection channel is established, the MQTT client A sends SERVICEREQ requests to the MQTT proxy server, the MQTT proxy server transmits the requests to the MQTT client B, the MQTT client B analyzes the received request content and sends SERVICERSP requests to the MQTT proxy server, and the MQTT proxy server transmits the responses to the MQTT client A for processing; the complete request response interaction process is completed;
and 3, sending Service DISCONNECT to close the Service connection channel when the MQTT client A and the MQTT client B are offline.
2. The MQTT protocol communication method for implementing synchronous request response according to claim 1, wherein: the forwarding process of the MQTT agent request response in step 2 is as follows:
step 2.1, after receiving the request message sent by the MQTT client A, the MQTT proxy server is put into a cache pool;
step 2.2, the MQTT proxy server takes out the request message from the request cache pool and forwards the request message to the MQTT client B according to the message receiving client identifier;
step 2.3, after receiving the request message, the MQTT client B sends a response message to the MQTT proxy server;
step 2.4, the MQTT proxy server receives the response message and stores the response message into a response message buffer pool, removes the corresponding request message from the request message buffer pool, and if the response message is not received or the MQTT client B is not on-line, the MQTT client B makes a plurality of attempts within a corresponding time period;
step 2.5, the MQTT proxy server takes out the response message from the response message cache pool and forwards the response message to the MQTT client A according to the message receiving client identifier;
step 2.6, the MQTT client A receives the response message and returns a response confirmation frame to the MQTT proxy server;
step 2.7, the MQTT proxy server removes the response message from the response message buffer pool, otherwise, it tries to resend many times.
3. The MQTT protocol communication method for implementing synchronous request response according to claim 1, wherein: in the request SERVICEREQ/response SERVICERSP control message, the flag bit 0 of the control message type of the fixed header indicates whether the request or the response is, 0 represents the request control message, and 1 represents the response control message; the message identifier of the Variable header represents the unique identifier of the request, and the message identifier of the response is the same as the message identifier of the request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010804340.5A CN111683158B (en) | 2020-08-12 | 2020-08-12 | MQTT protocol communication method for realizing synchronous request response |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010804340.5A CN111683158B (en) | 2020-08-12 | 2020-08-12 | MQTT protocol communication method for realizing synchronous request response |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111683158A CN111683158A (en) | 2020-09-18 |
| CN111683158B true CN111683158B (en) | 2020-11-06 |
Family
ID=72458283
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010804340.5A Active CN111683158B (en) | 2020-08-12 | 2020-08-12 | MQTT protocol communication method for realizing synchronous request response |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111683158B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500583A (en) * | 2021-04-26 | 2022-05-13 | 华北电力大学 | Power distribution Internet of things real-time communication method based on MQTT protocol |
| CN113794752B (en) * | 2021-08-23 | 2024-02-20 | 哈尔滨工业大学 | Method for optimizing MQTT based on QUIC |
| CN114866528A (en) * | 2022-04-01 | 2022-08-05 | 广东美味鲜调味食品有限公司 | Data communication method based on MQTT and Websocket |
| CN116860466A (en) * | 2023-06-12 | 2023-10-10 | 深圳市网力软件有限公司 | Asynchronous communication to synchronous communication method based on MQTT |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103379130A (en) * | 2012-04-13 | 2013-10-30 | 深圳市腾讯计算机系统有限公司 | Network access system and method based on application layer data |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10645181B2 (en) * | 2016-12-12 | 2020-05-05 | Sap Se | Meta broker for publish-subscribe-based messaging |
| CN110099078B (en) * | 2018-01-29 | 2022-02-25 | 阿里巴巴集团控股有限公司 | Method, device, equipment and storage medium for communication between equipment and message synchronization |
| CN108810086A (en) * | 2018-04-27 | 2018-11-13 | 电子科技大学中山学院 | Intelligent equipment communication platform based on MQTT message protocol |
| CN110657472A (en) * | 2019-09-05 | 2020-01-07 | 杭州电子科技大学 | iOS-based intelligent range hood communication scheduling method |
| CN111212085B (en) * | 2020-01-16 | 2022-11-22 | 厦门网宿有限公司 | Method for synchronously calling Internet of things platform, internet of things system and network equipment |
-
2020
- 2020-08-12 CN CN202010804340.5A patent/CN111683158B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103379130A (en) * | 2012-04-13 | 2013-10-30 | 深圳市腾讯计算机系统有限公司 | Network access system and method based on application layer data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111683158A (en) | 2020-09-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111683158B (en) | MQTT protocol communication method for realizing synchronous request response | |
| JP4927334B2 (en) | Instant messaging proxy mechanism and method | |
| WO2019205907A1 (en) | Intelligent device communication platform based on mqtt message protocol | |
| CN104836723B (en) | Communication method based on MQTT topic subscription mechanism and access gateway | |
| JP5356502B2 (en) | Real-time communication with data transfer framework | |
| US8499083B2 (en) | Relay device and communication system | |
| JP5678198B2 (en) | Mobile Internet service realization method, gateway, proxy and system | |
| US20070288632A1 (en) | Method and system for remotely accessing devices in a network | |
| US11356522B2 (en) | Data transmission method, network device, terminal device, and computer readable storage medium | |
| CN108183967B (en) | OPC UA (optical proximity correction) publishing/subscribing method suitable for IPv6 wireless sensor network | |
| WO2012012109A2 (en) | Method and apparatus for reducing application update traffic in cellular networks | |
| WO2008064591A1 (en) | Method, system and device for increasing multimedia messaging service system capacity | |
| CN111092802B (en) | Message interaction method, sending equipment and receiving equipment | |
| CN113162989A (en) | MQTT-Websocket-based message transceiving method | |
| GB2445791A (en) | Interconnection of Universal Plug and Play Networks using eXtensible Messaging and Presence Protocol Streams | |
| CN111741129A (en) | MQTT protocol communication method and system for realizing multiplexing | |
| US11272001B1 (en) | Port prediction for peer-to-peer communications | |
| WO2011015020A1 (en) | File transmission method, system and client | |
| CN114051041A (en) | Intelligent agricultural machinery system and communication method based on RabbitMQ and MQTT | |
| US10567183B2 (en) | System and method for conference messaging between telephony devices in a first network and devices connected to a second network | |
| CN115134395B (en) | Data processing method and device | |
| KR100243693B1 (en) | Method for handling internet connection service by using satellite | |
| CN109379443B (en) | Method for realizing distributed message queue facing to Internet of things | |
| WO2010009642A1 (en) | Method, system and device for implementing short message among enterprises | |
| CN113572678A (en) | Instant messaging method realized based on websocket |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |