CN112039884B - Application method of quick interconnection protocol QUIC in distributed database system - Google Patents
Application method of quick interconnection protocol QUIC in distributed database system Download PDFInfo
- Publication number
- CN112039884B CN112039884B CN202010895495.4A CN202010895495A CN112039884B CN 112039884 B CN112039884 B CN 112039884B CN 202010895495 A CN202010895495 A CN 202010895495A CN 112039884 B CN112039884 B CN 112039884B
- Authority
- CN
- China
- Prior art keywords
- quic
- protocol
- server
- connection
- data
- 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
- 238000000034 method Methods 0.000 title claims abstract description 53
- 230000004044 response Effects 0.000 claims abstract description 9
- 230000005540 biological transmission Effects 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 8
- 239000000872 buffer Substances 0.000 claims description 7
- 238000012544 monitoring process Methods 0.000 claims description 7
- 230000000903 blocking effect Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 5
- 238000001514 detection method Methods 0.000 claims description 5
- 230000006835 compression Effects 0.000 claims description 3
- 238000007906 compression Methods 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/164—Adaptation or special uses of UDP protocol
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- 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
Abstract
The invention particularly relates to an application method of a quick interconnection protocol QUIC in a distributed database system. The application method of the rapid interconnection protocol QUIC in the distributed database system uses the QUIC protocol for connection when each node in the database cluster carries out network interconnection to transmit service data, the gPRC service end node monitors a network address based on the QUIC protocol, and receives application data and replies a response when the data arrives; the gPC client node establishes QUIC protocol connection with the gPC server end through dialing, sends application data through a QUIC channel and waits for response, so that the node connection speed is increased and the expenditure of system resources is saved. The application method of the rapid interconnection protocol QUIC in the distributed database system can rapidly establish network connection between nodes when the nodes in the database cluster are increased in a large scale, effectively reduces the expenditure of system resources, and ensures the stable operation and rapid expansion of the distributed database system.
Description
Technical Field
The invention relates to the technical field of distributed database systems, in particular to an application method of a quick interconnection protocol QUIC in a distributed database system.
Background
QUIC (quick UDP Internet connection) is a UDP-based, low-latency Internet transport layer protocol. QUIC addresses well the various requirements faced by today's transport and application layers, including handling more connections, security and low latency. QUIC combines the characteristics of protocols including TCP, TLS, HTTP/2, etc. but based on UDP transmission, so it is fast, and has less resource consumption, and based on UDP transmission means more light weight, and has much less error check, which means more efficient.
In particular, QUIC has the following advantages:
1) for the conventional HTTPS, the TCP handshake for the transport layer requires 3 RTTs (Round-Trip Time) for the establishment of the low-latency connection, and if the encryption part is calculated, an extra RTT is generated, that is, at least more than 4 RTTs are required for the HTTPS to perform a complete handshake. However, for the QUIC, if the client connects to the server for the first time, the initial handshake normally requires only 1 RTT to complete the handshake, due to the characteristics of the QUIC that uses UDP as a transport layer protocol and combines transmission with encryption. Under the condition of repeated connection, if the certificate is valid, the client side can directly send the data encryption packet without waiting for reply, and delay-free connection is realized.
2) The QUIC protocol currently uses the congestion control algorithm of TCP by default, and is improved correspondingly on the basis of the congestion control algorithm. TCP congestion control actually comprises four algorithms: slow start, congestion avoidance, fast retransmission, fast recovery. The main improvement points are as follows:
A) the pluggable design, that is, the support of an operating system and a kernel is not needed, and different congestion controls can be configured for different connections;
B) the monotonically increasing Packet Number solves the problem of ambiguity of the serial Number of the TCP retransmission message;
C) the method does not allow the relaying, namely the received message is not allowed to be discarded, so that retransmission interference is reduced;
D) the Quic Ack Frame can provide 256 Ack blocks at the same time, and under the network with higher packet loss rate, more Sack blocks can improve the recovery speed of the network and reduce the retransmission amount;
E) the QUIC calculates the Ack Delay time of the server side, so that more accurate RTT is possessed;
3) the QUIC also multiplexes the multiplexing functions of the HTTP/2 protocol, but avoids the problem of HTTP/2 head-of-line blocking since the QUIC is UDP based. HTTP/2 transmits a plurality of streams simultaneously on a TCP connection, if a certain Stream in the middle loses a packet, TCP needs the transmitting end to retransmit the lost packet in order to ensure data reliability, and although the packets of other streams have arrived at the receiving end at this time, the packets are blocked and need to wait for the previous Stream to receive the retransmitted packet, which is called head-of-queue blocking. While QUIC multiplexing can avoid this problem because all streams are independent of each other under the QUIC connection, and packet loss on one Stream does not affect data transmission of other streams.
4) Each data packet of the QUIC protocol can carry partial data of other data packets besides own data, and under the condition of a small amount of lost packets, the redundant data of other data packets can be used for completing data assembly without retransmission, so that the transmission speed of the data is improved. The specific implementation is similar to RAID5, and the checksum (exclusive or) of N packets is established to be sent as a single data packet, so that if one packet is lost in the N packets, the data packet can be directly recovered, and besides, the data packet can be used to check the correctness of the packet.
5) For the TCP protocol, 4 parameters are needed to identify a TCP connection, namely source IP, source port, destination IP and destination port. Any one of these parameters changes and the TCP connection needs to be re-created. This is of little impact to a conventional network because the source and destination IPs are relatively fixed. But in wireless networks the situation is quite different. During the movement of the device, the TCP connection may need to be re-created due to network switching (e.g., switching from the WIFI network to the 4G network environment). The QUIC protocol uses the UDP protocol and the quad parameters are no longer needed. Meanwhile, the QUIC protocol realizes a session marking mode of the self, and the session marking mode is called as connection UUID. When the network environment of the equipment is switched, the UUID of the connection does not change, so that the handshake does not need to be carried out again.
6) Since TCP is implemented in the operating system kernel and middleware firmware, significant changes to TCP are almost impossible. And the QUIC is realized based on UDP and runs in a user domain instead of a system kernel, so that the QUIC protocol can be rapidly updated and deployed, and the difficulty of TCP protocol deployment and updating is well solved.
Since the QUIC protocol is very complex, even more complex than HTTP/2, the client is complex to implement. In addition, because of using the UDP protocol, the support for the UDP channel in the network is not sufficient and is not stable. Today the QUIC working group of the IETF is responsible for the standardization process of the QUIC protocol. A preliminary QUIC protocol version has been used in google's services and Chrome browsers and is deployed by a few third party developers.
In order to reduce the consumption of system resources, improve the speed of network connection, ensure the stability of the system and further ensure the functions of stable operation, capacity expansion and the like of a distributed database system, the invention provides an application method of a quick interconnection protocol QUIC in the distributed database system.
Disclosure of Invention
In order to make up for the defects of the prior art, the invention provides a simple and efficient application method of a quick interconnection protocol QUIC in a distributed database system.
The invention is realized by the following technical scheme:
an application method of a quick interconnection protocol QUIC in a distributed database system is characterized in that: all messages in the database cluster are sent and received by depending on a gRPC remote procedure call framework, and the method comprises the following steps:
the first step, when all nodes in a database cluster are interconnected with each other through a network to transmit service data, a QUIC protocol is used for connection, a gPC server node monitors a network address based on the QUIC protocol, and receives application data and replies a response when the data arrives;
and secondly, the gPC client node establishes QUIC protocol connection with the gPC server end through dialing, and sends application data through a QUIC channel and waits for response, so that the node connection speed is increased and the expenditure of system resources is saved.
The gPRC remote procedure call framework conforms to a server/client model, so that network connection is established between application programs for communication; when the system is used, the server starts monitoring the corresponding network address and receives data, and the client establishes network connection and initiates data transmission by dialing the network address.
The gPC remote process call framework utilizes protocol buffers to define and transmit data formats of all applications, and network connection based on a QUIC protocol is established in the gPC remote process call framework on the basis of QUIC-go.
The first step comprises the following steps:
s1, creating a gPC service at the service end node, and configuring service end parameters for the gPC service;
s2, protocol buffers are used to define gossip connection, heartbeat detection and copy sending services in the distributed database system, define data transmission formats, interaction methods, parameters sent by the client and data contents responded by the server of each application, and register implementation methods of the applications to the gRPC service.
S3, the connection of the network address is monitored at the service end to prepare for receiving data, the gPC service uses a TCP protocol to start monitoring the network address by default, monitors the network address under the UDP protocol after adopting the QUIC protocol and generates a QUIC connection channel, and finally transmits the QUIC channel to the gPC service.
In step S1, the service parameters configured for the gRPC service include thresholds for sending and receiving data through the connection channel, the size of the congestion window, the number of multiplexing connections, and the security certificate.
In step S3, a blocking method is used to wait for the arrival of data.
And in the second step, the client node is connected with a QUIC channel of the server through gRPC dialing, parameters of the client are configured by a dialing method, the parameters comprise a threshold value of sending and receiving data by the connection channel, the size of a congestion window, a compression option, an interceptor and a security certificate, and simultaneously UDP dialing is carried out by using the QUIC dialing option provided by QUIC-go to realize connection with the QUIC channel.
In the second step, QUIC negotiation needs to be completed once when the QUIC channel is connected for the first time;
firstly, a Client sends a CHLO (include Client hello) message to a server, and the server replies an REJ (rejection) message after receiving the CHLO message, wherein the REJ message comprises a public key and certificate information of the server;
after receiving the reject information of the server, the client sends client hello information containing the public key information of the server to the server again; and after the server receives the client hello information, the connection is successfully established.
The invention has the beneficial effects that: the application method of the rapid interconnection protocol QUIC in the distributed database system can rapidly establish network connection between nodes when the nodes in the database cluster are increased in a large scale, effectively reduces the expenditure of system resources, and ensures the stable operation and rapid expansion of the distributed database system.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of the structure of a QUIC network.
FIG. 2 is a schematic diagram of a distributed database node start command according to the present invention.
FIG. 3 is a schematic diagram of the steps of the QUIC protocol of the present invention applied to a gPC.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the embodiment of the present invention. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The wave cloud sea distributed database DRDB is a cloud native distributed NewSQL database, and after each node in a database cluster is started, network connection needs to be established to complete the database service functions of node interconnection, heartbeat detection, copy migration and the like. A gPC remote process call framework is used for communication when network connection is established, the gPC follows a server/client model, monitoring of TCP connection is started at a server and data is waited when default use is carried out, and a registered application service method is called after the client dials the TCP connection to the network address of the server, so that data transmission can be started.
As the size of nodes in a cluster increases, various application messages in the system also increase in an exponential scale, and various overhead burdens of the system also increase in multiples. Since TCP needs to perform a large number of handshake connections, if the database system operates in the security mode and also needs negotiation of the security protocol, a large amount of system resources are occupied, and even some nodes and even the whole system are crashed.
Due to the advantages of the QUIC protocol in the aspects of resource occupation and connection speed, if the gRPC connection is established on the QUIC, the consumption of system resources can be greatly reduced, the speed of network connection is increased, the stability of the system is ensured, and the functions of stable operation, capacity expansion and the like of the distributed database system are further ensured. In addition, the QUIC protocol is realized by a user mode, so that the updating maintenance and the rapid deployment can be conveniently realized under the condition of not updating the kernel of the operating system, and the maintainability and controllability of the system are improved.
When the nodes of the wave cloud sea distributed database system are started through a command line, the IP addresses and the port numbers of the nodes are appointed, and the IP addresses and the port numbers form a unique network address to identify the nodes. If the subsequent node wants to form a cluster with the started node when starting, the subsequent node can choose to join the network address of the started node, and after starting, the subsequent node establishes network connection with other nodes by sending a gossip request message and receiving a gossip response message to form the cluster and mutually exchanges local known network node information. After network connection is established, each node in the cluster maintains the node connection state by regularly sending and receiving heartbeat detection messages, and meanwhile, each node in the cluster synchronously copies in real time to maintain consistency.
The application method of the quick interconnection protocol QUIC in the distributed database system is realized by relying on a gRPC remote procedure call framework to send and receive all messages in a database cluster, and comprises the following steps:
the method comprises the steps that firstly, nodes in a database cluster are connected through a QUIC protocol when being networked to transmit service data, a gPRC server node monitors a network address based on the QUIC protocol, and receives application data and replies a response when the data arrive;
and secondly, the gPC client node establishes QUIC protocol connection with the gPC server end through dialing, and sends application data through a QUIC channel and waits for response, so that the node connection speed is increased and the expenditure of system resources is saved.
The gPRC remote procedure call framework follows a server/client model, so that network connection is established among application programs for communication; when the system is used, the server starts monitoring the corresponding network address and receives data, and the client establishes network connection and initiates data transmission by dialing the network address. When in use, the client calls the interface provided by the server just like calling a local function.
The gPC remote process call framework utilizes protocol buffers to define and transmit data formats of all applications, and network connection based on a QUIC protocol is established in the gPC remote process call framework on the basis of QUIC-go.
protocol buffers is a method for serializing structural data with no language, no platform and no expansion, and can be used for data communication protocol, data storage and the like. It features flexibility, high efficiency, and smaller size and faster speed than XML.
And the QUIC-Go is a QUIC protocol implementation library rewritten by using the Go language, the implementation interface is clear, and the deployment and the updating are convenient.
The first step comprises the following steps:
s1, creating a gPC service at the service end node, and configuring service end parameters for the gPC service;
s2, defining gossip connection, heartbeat detection and duplicate sending services in the distributed database system by protocol buffers, defining data transmission formats, interaction methods, parameters sent by the client and data contents responded by the server of each application, and registering the implementation methods of the applications to the gPC service.
S3, the connection of the network address is monitored at the service end to prepare for receiving data, the gPC service uses a TCP protocol to start monitoring the network address by default, monitors the network address under the UDP protocol after adopting the QUIC protocol and generates a QUIC connection channel, and finally transmits the QUIC channel to the gPC service.
In step S1, the service parameters configured for the gRPC service include thresholds for sending and receiving data through the connection channel, the size of the congestion window, the number of multiplexing connections, and the security certificate.
In step S3, a blocking method is used to wait for the arrival of data.
And in the second step, the client node is connected with a QUIC channel of the server through gRPC dialing, parameters of the client are configured by a dialing method, the parameters comprise a threshold value of sending and receiving data by the connection channel, the size of a congestion window, a compression option, an interceptor and a security certificate, and simultaneously UDP dialing is carried out by using the QUIC dialing option provided by QUIC-go to realize connection with the QUIC channel.
In the second step, one QUIC negotiation is completed when the QUIC channel is connected for the first time;
firstly, a Client sends a CHLO (include Client hello) message to a server, and the server replies an REJ (rejection) message after receiving the CHLO message, wherein the REJ message comprises a public key and certificate information of the server;
after receiving the reject information of the server, the client sends client hello information containing the public key information of the server to the server again; and after the server receives the client hello information, the connection is successfully established.
Data may be sent directly if a connection is previously established.
In the second step, after the connection channels of the client and the server are established, corresponding application methods can be called to complete the sending and receiving of data, and the connection channels used by the data transmitted by the gRPCs in the database cluster are established based on a QUIC protocol.
The distributed database system runs the TPCC for testing after applying the QUIC scheme, the testing environment is a Ubuntu system of the virtual machine, 8g of memory, the maximum value is obtained after continuous running for 5 times, and compared with the TCP connection scheme, the result is as follows, the transaction execution times of the system in the specified time are obviously improved, and the system performance is obviously improved.
Operating results under the TCP scheme:
_elapsed_______tpmC____efc__avg(ms)__p50(ms)__p90(ms)__p95(ms)__p99(ms)_pMax(ms)
180.0s 1555.3 1209.4% 798.5 604.0 1543.5 2080.4 3892.3 12348.0
run results under QUIC protocol:
_elapsed_______tpmC____efc__avg(ms)__p50(ms)__p90(ms)__p95(ms)__p99(ms)_pMax(ms)
180.1s 1602.8 1246.3% 802.8 604.0 1610.6 2080.4 3355.4 9126.8
the above-described embodiment is only one specific embodiment of the present invention, and general changes and substitutions by those skilled in the art within the technical scope of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. An application method of a quick interconnection protocol QUIC in a distributed database system is characterized in that: all messages in the database cluster are sent and received by depending on a gRPC remote procedure call framework, and the method comprises the following steps:
the method comprises the steps that firstly, nodes in a database cluster are connected through a QUIC protocol when being networked to transmit service data, a gPRC server node monitors a network address based on the QUIC protocol, and receives application data and replies a response when the data arrive;
and secondly, the gPC client node establishes QUIC protocol connection with the gPC server end through dialing, transmits application data through a QUIC channel and waits for response.
2. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 1, characterized in that: the gPRC remote procedure call framework follows a server/client model, so that network connection is established among application programs for communication; when the system is used, the server starts monitoring the corresponding network address and receives data, and the client establishes network connection and initiates data transmission by dialing the network address.
3. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 1 or 2, characterized in that: the gPC remote process call framework utilizes protocol buffers to define and transmit data formats of all applications, and network connection based on a QUIC protocol is established in the gPC remote process call framework on the basis of QUIC-go.
4. Method for the application of the QUIC in a distributed database system according to claim 3, characterised in that: the first step comprises the following steps:
s1, creating a gPC service at the service end node, and configuring service end parameters for the gPC service;
s2, defining gossip connection, heartbeat detection and copy sending services in the distributed database system by protocol buffers, defining data transmission formats, interaction methods, parameters sent by the client and data contents responded by the server of each application, and registering implementation methods of the applications to the gPC service;
s3, the connection of the network address is monitored at the service end to prepare for receiving data, the gPC service uses a TCP protocol to start monitoring the network address by default, monitors the network address under the UDP protocol after adopting the QUIC protocol and generates a QUIC connection channel, and finally transmits the QUIC channel to the gPC service.
5. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 4, characterized in that: in step S1, the service parameters configured for the gRPC service include thresholds for sending and receiving data through the connection channel, the size of the congestion window, the number of multiplexing connections, and the security certificate.
6. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 4, characterized in that: in step S3, a blocking method is used to wait for the arrival of data.
7. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 3, characterized in that: and in the second step, the client node is connected with a QUIC channel of the server through gRPC dialing, parameters of the client are configured by a dialing method, the parameters comprise a threshold value of sending and receiving data by the connection channel, the size of a congestion window, a compression option, an interceptor and a security certificate, and simultaneously UDP dialing is carried out by using the QUIC dialing option provided by QUIC-go to realize connection with the QUIC channel.
8. Method for the application of the quickinterconnect protocol QUIC in a distributed database system according to claim 7, characterized by the fact that: in the second step, one QUIC negotiation is completed when the QUIC channel is connected for the first time;
firstly, a client sends CHLO information to a server, and a server replies REJ information after receiving the CHLO information, wherein the REJ information comprises a public key and certificate information of the server;
after receiving the reject information of the server, the client sends client hello information containing the public key information of the server to the server again; and after the server receives the client hello information, the connection is successfully established.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010895495.4A CN112039884B (en) | 2020-08-31 | 2020-08-31 | Application method of quick interconnection protocol QUIC in distributed database system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010895495.4A CN112039884B (en) | 2020-08-31 | 2020-08-31 | Application method of quick interconnection protocol QUIC in distributed database system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112039884A CN112039884A (en) | 2020-12-04 |
| CN112039884B true CN112039884B (en) | 2022-05-31 |
Family
ID=73587442
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010895495.4A Active CN112039884B (en) | 2020-08-31 | 2020-08-31 | Application method of quick interconnection protocol QUIC in distributed database system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112039884B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112636972B (en) * | 2020-12-22 | 2022-11-18 | 广东南方新媒体科技有限公司 | Method for optimizing network performance based on plug-in technology and QUIC protocol |
| CN112860799A (en) * | 2021-02-22 | 2021-05-28 | 浪潮云信息技术股份公司 | Management method for data synchronization of distributed database |
| CN115842876A (en) * | 2021-09-18 | 2023-03-24 | 华为技术有限公司 | Method, system, device and storage medium for processing message |
| CN115150204B (en) * | 2022-09-05 | 2023-01-10 | 广州中浩控制技术有限公司 | Data transmission system |
| CN115297194A (en) * | 2022-10-09 | 2022-11-04 | 深圳市信润富联数字科技有限公司 | Data processing method, device and equipment of wind power monitoring equipment and storage medium |
| CN116232940A (en) * | 2022-12-30 | 2023-06-06 | 天翼云科技有限公司 | Performance test system, method and device based on QUIC protocol |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064792A (en) * | 2019-12-19 | 2020-04-24 | 北京航天云路有限公司 | Method for accelerating data acquisition of sensor equipment based on QUIC protocol |
| CN111414208A (en) * | 2020-03-13 | 2020-07-14 | 百度在线网络技术（北京）有限公司 | Application program starting method, device and equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9026783B2 (en) * | 2013-03-07 | 2015-05-05 | Google Inc. | Low latency server-side redirection of UDP-based transport protocols traversing a client-side NAT firewall |
| WO2019147157A1 (en) * | 2018-01-29 | 2019-08-01 | Huawei Technologies Co., Ltd | Method of improving qoe for video and web services using cross-layer information |
-
2020
- 2020-08-31 CN CN202010895495.4A patent/CN112039884B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064792A (en) * | 2019-12-19 | 2020-04-24 | 北京航天云路有限公司 | Method for accelerating data acquisition of sensor equipment based on QUIC protocol |
| CN111414208A (en) * | 2020-03-13 | 2020-07-14 | 百度在线网络技术（北京）有限公司 | Application program starting method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112039884A (en) | 2020-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112039884B (en) | Application method of quick interconnection protocol QUIC in distributed database system | |
| Briscoe et al. | Reducing internet latency: A survey of techniques and their merits | |
| JP4164365B2 (en) | Technology for improving TCP performance over a wireless interface by providing a dual proxy device | |
| US7860985B2 (en) | Method for synchronizing connection state in data communication, and communication node using the same | |
| US7801135B2 (en) | Transport protocol connection synchronization | |
| JP7142722B2 (en) | Transmission control method and device | |
| WO2018205688A1 (en) | Method, apparatus and system for data transmission | |
| CN109412946B (en) | Method, device, server and readable storage medium for determining back source path | |
| US20150373135A1 (en) | Wide area network optimization | |
| WO2011100911A2 (en) | Detection processing method, data transmitter, data receiver and communication system | |
| WO2016106780A1 (en) | User data transmission method and apparatus and terminal | |
| CN115766605A (en) | Network congestion control method, device and system | |
| CN103607311B (en) | System and method for reestablishing TCP connection seamlessly | |
| JP2001045093A (en) | Layer 2 tunneling protocol(l2tp) oriented sender initiation recovery algorithm(sira) | |
| CN113726648B (en) | Multipath communication method, device, electronic equipment and computer readable medium | |
| JP2016162324A (en) | Information processing system, control program and control method | |
| JP3665309B2 (en) | COMMUNICATION SYSTEM, COMMUNICATION DEVICE, AND COMMUNICATION METHOD | |
| US20140369189A1 (en) | Method of controlling packet transmission in network system and network system transmitting packet using pseudo-tcp agent | |
| WO2016062085A1 (en) | Virtual network realization method, nve and nva device and system | |
| WO2022089245A1 (en) | Service transmission method, communication device and storage medium | |
| Singh et al. | An SDN-based true end-to-end TCP for wireless LAN | |
| JP3867896B2 (en) | Router device | |
| KR101396785B1 (en) | Method for performing tcp functions in network equipmment | |
| CN117640530A (en) | Method and device for low-delay reliable data transmission of cluster network | |
| EP2139188B1 (en) | A l2c method, device and system |
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 |