Congestion control method, device and electronic device
The congestion control method addresses the lack of differentiated services in QUIC-based HTTP/3.0 by adapting to service and network types, ensuring optimal transmission experiences through integrated application and network perception.
Patent Information
- Application Number
- CN202111030513.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-09-03
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-09-03
AI Technical Summary
Existing transport layer protocols, such as QUIC-based HTTP/3.0, fail to provide differentiated experiences and services across diverse business scenarios and complex network conditions, treating all services equally without considering specific application and network requirements.
A congestion control method that adapts to service type and network type by selecting appropriate congestion control algorithms and parameters based on client requests, using a framework that integrates application and network perception modules with an adapter module for optimal transmission.
Provides differentiated and optimal transmission experiences by accurately matching congestion control algorithms and parameters to service and network types, enhancing performance in complex network environments.
Smart Images

Figure CN113726688B_ABST
Abstract
Description
[Technical field]
[0001] The embodiments of this specification relate to the field of Internet technology, and in particular, to a congestion control method, device, and electronic device. [Background technology]
[0002] As an emerging transport layer protocol, the Quick User Datagram Protocol Internet Connection (QUIC) protocol has many advantages, such as low link establishment overhead, no head blocking, support for connection migration and / or implementation in user mode. Hypertext Transfer Protocol (HTTP) 3.0 based on QUIC transmission is becoming the next generation of Internet protocol. As the types of business involved in third-party payment platforms increase, such as payment, insurance, funds, stocks, small games and / or blockchain, the network environment they face is becoming more and more complex: from domestic to overseas, from cities to rural areas, from wired to wireless or from long term evolution (LTE) to wireless fidelity (WIFI). Different business scenarios have different requirements for transmission. For example, payment information requires low latency, and different network conditions also have different adaptability to transmission.
[0003] However, in the existing related technologies, the transport layer treats all services equally and cannot provide differentiated experiences and services. Therefore, it is necessary to provide a solution to provide unified adaptive optimal transmission capabilities in multiple business scenarios and / or complex network conditions. [Summary of the invention]
[0004] The embodiments of this specification provide a congestion control method, apparatus, and electronic device to implement congestion control according to the service type requested by a client and the network type used by the client, thereby obtaining a differentiated and optimal transmission experience.
[0005] In a first aspect, an embodiment of the present specification provides a congestion control method, which is applied to a server, and the method includes: receiving a message sent by a client; obtaining from the message the service type requested by the client and the network type used by the client; if the service type and the network type respectively belong to the service type and the network type currently supported by the server, then selecting a first congestion control algorithm that matches the service type and the network type according to a predetermined matching rule, and performing congestion control using parameters corresponding to the first congestion control algorithm.
[0006] In the above-mentioned congestion control method, after receiving the message sent by the client, the service type requested by the client and the network type used by the client are obtained from the above-mentioned message. If the above-mentioned service type and the above-mentioned network type respectively belong to the service type and the above-mentioned network type currently supported by the server, then according to the predetermined matching rule, the first congestion control algorithm matching the above-mentioned service type and the above-mentioned network type is selected, and the parameters corresponding to the first congestion control algorithm are used to perform congestion control, so as to obtain a differentiated and optimal transmission experience.
[0007] In one possible implementation, after obtaining the service type requested by the client and the network type used by the client from the message, it also includes: if the service type does not belong to the service type currently supported by the server, and / or the network type does not belong to the network type currently supported by the server, congestion control is performed using a predetermined second congestion control algorithm and parameters corresponding to the second congestion control algorithm.
[0008] In one possible implementation manner, obtaining the service type requested by the client from the message includes: obtaining the service type requested by the client according to a value of an application transmission request identifier in a transmission parameter field of the message.
[0009] In one possible implementation manner, obtaining the network type used by the client from the message includes: obtaining the network type used by the client according to a value of a network type identifier in a transmission parameter field of the message.
[0010] In one possible implementation, the parameters include one or a combination of the following: an initial window size, a packet loss detection algorithm, a threshold corresponding to the packet loss detection algorithm, a PTO timer threshold, a recovery time target threshold, and a delayed confirmation threshold.
[0011] In a second aspect, an embodiment of the present specification provides a congestion control device, which is arranged in a server, and the device includes: a receiving module, which is used to receive a message sent by a client; an acquisition module, which is used to obtain the service type requested by the client and the network type used by the client from the message; a congestion control module, which is used to select a first congestion control algorithm that matches the service type and the network type according to a predetermined matching rule when the service type and the network type belong to the service type and the network type currently supported by the server respectively, and use parameters corresponding to the first congestion control algorithm to perform congestion control.
[0012] In one possible implementation, the congestion control module is also used to perform congestion control through a predetermined second congestion control algorithm and using parameters corresponding to the second congestion control algorithm when the service type does not belong to the service type currently supported by the server and / or the network type does not belong to the network type currently supported by the server.
[0013] In one possible implementation manner, the acquisition module is specifically configured to acquire the service type requested by the client according to the value of the application transmission request identifier in the transmission parameter field of the message.
[0014] In one possible implementation manner, the acquisition module is specifically configured to acquire the network type used by the client according to a value of a network type identifier in a transmission parameter field of the message.
[0015] In a third aspect, an embodiment of the present specification provides an electronic device, comprising: at least one processor; and at least one memory communicatively connected to the processor, wherein: the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the method provided in the first aspect.
[0016] In a fourth aspect, an embodiment of the present specification provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions enable the computer to execute the method provided in the first aspect.
[0017] It should be understood that the second to fourth aspects of the embodiments of this specification are consistent with the technical solutions of the first aspect of the embodiments of this specification, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.
Brief Description of the Drawings
[0018] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0019] Figure 1 A framework diagram of adaptive QUIC provided for one embodiment of this specification;
[0020] Figure 2 A flowchart of a congestion control method provided by one embodiment of this specification;
[0021] Figure 3 A schematic diagram of the structure of a congestion control device provided in one embodiment of this specification;
[0022] Figure 4 A schematic diagram of the structure of an electronic device provided in one embodiment of this specification. [Specific implementation method]
[0023] In order to better understand the technical solution of this specification, the embodiments of this specification are described in detail below with reference to the accompanying drawings.
[0024] It should be clear that the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.
[0025] The terms used in the embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit this specification. The singular forms "a", "said" and "the" used in the embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0026] Based on the problem that the transport layer cannot provide differentiated experience and services, existing related technologies provide two solutions. One solution is based on the deadline-aware transport protocol (DTP). DTP is a transmission protocol designed based on QUIC to perceive the deterministic delay (deadline) of applications. It meets the demands of different applications by designing a deadline-based scheduling algorithm on QUIC.
[0027] Another solution is the Rein system, which provides a data center to user congestion control framework that can sense the network type based on transport layer information, including round-trip time (RTT) and / or packet loss rate, and perform congestion control based on the network type.
[0028] However, DTP only perceives the application layer and the application deadline, and only performs scheduling optimization; the Rein framework only perceives the network, and the perception method is to control congestion through network status.
[0029] In response to the problems of the above two solutions, the embodiments of this specification provide a congestion control method, which implements adaptive transmission based on QUIC. With the convenience and scalability of QUIC in user mode, it can perceive applications upward and networks downward, and provide transmission performance at the most optimized connection level. Compared with DTP, the congestion control method provided in the embodiments of this specification can perceive both application types and network types, and make congestion control selections and parameter adjustments based on application types and network types; compared with the Rein framework, the congestion control method provided in the embodiments of this specification allows the client to directly carry relevant information of the network layer, which is accurate and convenient. At the same time, the congestion control method provided in the embodiments of this specification can perceive applications while perceiving the network. In addition to selecting congestion control algorithms, different congestion control parameters can also be set according to user needs.
[0030] Figure 1 A framework diagram of adaptive QUIC provided for one embodiment of this specification, such as Figure 1 As shown, the framework of adaptive QUIC includes three layers: application layer, QUIC-based adaptive transport layer and underlying network.
[0031] Among them, the application layer includes various types of services that the client may request, including delay-sensitive services, bandwidth-sensitive services, and packet loss-sensitive services. For example, the delay-sensitive services may be interactive applications such as games, the bandwidth-sensitive services may be services such as large file transfer and download, and the packet loss-sensitive services may be services such as live video broadcasting.
[0032] The underlying network includes the network type where the client is located, including: wireless network, wired network, public network, intranet, small bandwidth delay production (small BDP) network and / or long fat network, etc.; among them, BDP is the product of RTT and bandwidth, also called delay-bandwidth product, which is used to indicate the maximum amount of data that a network can transmit within one RTT; a long fat network refers to a network with a BDP value greater than 105 bits, indicating that the current network has a large response time (RT) or a high bandwidth.
[0033] The QUIC-based adaptive transport layer in the middle mainly includes the following components:
[0034] 1. Application layer perception module;
[0035] 2. Network layer perception module;
[0036] 3. Congestion control algorithm set;
[0037] 4. Congestion control related parameter set;
[0038] 5. Adapter module.
[0039] in:
[0040] 1. Application layer perception module: mainly determines the service type requested by the client based on the parameters carried by the client when using QUIC. This embodiment preliminarily defines three service types: delay-sensitive service, bandwidth-sensitive service, and packet loss-sensitive service.
[0041] Of course, only three business types are preliminarily defined here, and this embodiment is not limited thereto, and other business types may be further expanded, which is not limited in this embodiment.
[0042] In this embodiment, an application transmission request identifier (APP_Trans_Req_ID) is added to the transport parameter field of the QUIC message. The client carries this application layer information when initiating a request. The server obtains the application type requested by the client through this application transmission request identifier.
[0043] 2. Network layer perception module: mainly determines the network type used by the client based on the parameters carried by the client when using QUIC. This embodiment preliminarily defines the following network types:
[0044] 1) Wireless networks, including WIFI and / or LTE;
[0045] 2) Wired network;
[0046] 3) Public network;
[0047] 4) Intranet;
[0048] 5) small BDP;
[0049] 6) Grow a fat network.
[0050] Of course, only a few network types are listed here, and this embodiment is not limited to them. Other network types can be further expanded, and this embodiment does not limit this.
[0051] In this embodiment, a network type identifier (Network_Types_ID) is added to the transport parameter field of the QUIC message. The client carries this network information when initiating a request. The server obtains the network type used by the client through this network type identifier.
[0052] 3. Congestion control algorithm set: The congestion control algorithm set integrates multiple congestion control algorithms as candidate algorithms for selection by the Adapter module. For example, the congestion control algorithms may include: bottleneck bandwidth and round-trip propagation time (BBR), Cubic, DCTCP, Westwood+, etc. Similarly, other congestion control algorithms may continue to be integrated, which is not limited in this embodiment.
[0053] 4. Congestion control related parameter set: The congestion control related parameter set provides multiple parameters related to the congestion control algorithm to meet different needs, mainly including: initial window size, packet loss detection algorithm, threshold corresponding to the packet loss detection algorithm, PTO timer threshold, recovery time object (RTO) threshold and delay acknowledgment (Delay ACK) threshold. Similarly, other congestion control parameters can be further expanded, which is not limited in this embodiment.
[0054] 5. Adapter module: Aggregates application demands and underlying network demands and matches them to specific algorithms. Matching rules may include:
[0055] 1. A scoring mechanism based on experience. For example, for wireless network services, the algorithms used in the past are scored. The Westwood+ algorithm is selected first based on the score.
[0056] 2. Based on the system's self-feedback learning mechanism, for example, for some combinations, the algorithms and parameters used historically and the corresponding effects can be recorded for reinforcement learning for next use.
[0057] Of course, these are just two examples of matching rules and are not intended to be limiting of this embodiment. Other matching rules may also be extended.
[0058] Figure 2 A flowchart of a congestion control method provided for one embodiment of the present specification, wherein the congestion control method is applied to a server, wherein the server may be a QUIC server.
[0059] like Figure 2 As shown, the above congestion control method may include:
[0060] Step 202: Receive a message sent by the client.
[0061] In this embodiment, the client uses HTTP based on QUIC transmission, so the above message sent by the client can be a QUIC message.
[0062] Step 204: Obtain the service type requested by the client and the network type used by the client from the message. Then, execute step 206 or step 208.
[0063] Specifically, when the client initiates a request, the client can carry the service type requested by the client through the application transmission request identifier (APP_Trans_Req_ID) in the transmission parameter (TransportParameter) field of the QUIC message. The service type requested by the client can be selected from several service types currently supported by the server. If the service type requested by the client is not among the several service types currently supported by the server, the client can set the value of the application transmission request identifier to null.
[0064] In this way, the server may obtain the service type requested by the client from the message by: obtaining the service type requested by the client according to the value of the application transmission request identifier (APP_Trans_Req_ID) in the transmission parameter (Transport Parameter) field of the message.
[0065] Similarly, when initiating a request, the client can carry the network type used by the above client through the network type identifier (Network_Types_ID) in the transport parameter (TransportParameter) field of the QUIC message. The network type used by the above client can be selected from several network types currently supported by the server. If the network type used by the above client is not among the several network types currently supported by the server, the client can set the value of the above network type identifier to null.
[0066] In this way, the server may obtain the network type used by the client from the message by: obtaining the network type used by the client according to the value of the network type identifier in the transmission parameter field of the message.
[0067] In specific implementation, the server can Figure 1 The Adapter module in the embodiment realizes the function of obtaining the service type requested by the client and the network type used by the client from the above message.
[0068] Step 206: If the above-mentioned service type and the above-mentioned network type respectively belong to the service type and network type currently supported by the server, a first congestion control algorithm matching the above-mentioned service type and the above-mentioned network type is selected according to a predetermined matching rule, and congestion control is performed using parameters corresponding to the first congestion control algorithm.
[0069] Among them, congestion control is an algorithm used in reliable transmission protocols, such as transmission control protocol (TCP) to avoid congestion in the network. The most primitive congestion control includes several stages such as slow start, congestion avoidance, fast retransmission and fast recovery.
[0070] Specifically, the above-mentioned predetermined matching rules may include:
[0071] 1. A scoring mechanism based on experience. For example, for wireless network services, the congestion control algorithms used in the past are scored. The Westwood+ algorithm will be selected first based on the score.
[0072] 2. Based on the system's self-feedback learning mechanism, for example, the algorithms and parameters used historically under different business types and different network types and the corresponding effects can be recorded, and reinforcement learning can be performed to train an algorithm adaptation model. In this way, after obtaining the business type requested by the client and the network type used by the client, the obtained business type and network type can be input into the above-mentioned algorithm adaptation model to obtain the congestion control algorithm output by the algorithm adaptation model.
[0073] Of course, these are just two examples of matching rules and are not intended to be limiting of this embodiment. Other matching rules may also be extended.
[0074] Step 208: If the above service type does not belong to the service type currently supported by the server, and / or the above network type does not belong to the network type currently supported by the server, congestion control is performed using a predetermined second congestion control algorithm and parameters corresponding to the above second congestion control algorithm.
[0075] Specifically, when the value of the application transmission request identifier (APP_Trans_Req_ID) carried in the message sent by the client is null, it means that the service type requested by the client does not belong to the service type currently supported by the server; when the value of the network type identifier (Network_Types_ID) carried in the message sent by the client is null, it means that the network type used by the client does not belong to the network type currently supported by the server.
[0076] The predetermined second congestion control algorithm may be a default congestion control algorithm, which is not limited in this embodiment.
[0077] In step 206 and step 208, the parameters corresponding to the first congestion control algorithm and the parameters corresponding to the second congestion control algorithm may include one or a combination of the following: initial window size, packet loss detection algorithm, threshold corresponding to the packet loss detection algorithm, PTO timer threshold, recovery time target threshold and delay confirmation threshold.
[0078] In the above-mentioned congestion control method, after receiving the message sent by the client, the service type requested by the client and the network type used by the client are obtained from the above-mentioned message. If the above-mentioned service type and the above-mentioned network type respectively belong to the service type and the above-mentioned network type currently supported by the server, then according to the predetermined matching rule, the first congestion control algorithm matching the above-mentioned service type and the above-mentioned network type is selected, and the parameters corresponding to the first congestion control algorithm are used to perform congestion control, so as to obtain a differentiated and optimal transmission experience.
[0079] The congestion control method provided in the embodiment of this specification classifies the service type and designs the carrying parameters for the server to obtain the service type, and classifies the network type and designs the carrying parameters for the server to obtain the network type. At the same time, this embodiment integrates different congestion control algorithms and adjustment parameters in the user state, and realizes the matching of the optimal congestion control algorithm through the Adapter module.
[0080] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0081] Figure 3 This is a schematic diagram of the structure of a congestion control device provided in an embodiment of this specification. The congestion control device is set in a server. Specifically, the server may be a QUIC server. Figure 3 As shown, the congestion control device may include: a receiving module 31, an acquisition module 32 and a congestion control module 33;
[0082] Wherein, the receiving module 31 is used to receive the message sent by the client;
[0083] An acquisition module 32, used to acquire the service type requested by the client and the network type used by the client from the message;
[0084] The congestion control module 33 is used to select a first congestion control algorithm that matches the above-mentioned business type and the above-mentioned network type according to a predetermined matching rule when the above-mentioned business type and the above-mentioned network type respectively belong to the business type and the above-mentioned network type currently supported by the server, and use parameters corresponding to the first congestion control algorithm to perform congestion control.
[0085] Furthermore, the congestion control module 33 is also used to perform congestion control through a predetermined second congestion control algorithm and using parameters corresponding to the second congestion control algorithm when the above-mentioned service type does not belong to the service type currently supported by the server and / or the above-mentioned network type does not belong to the network type currently supported by the server.
[0086] In this embodiment, the acquisition module 32 is specifically configured to acquire the service type requested by the client according to the value of the application transmission request identifier in the transmission parameter field of the above message.
[0087] The acquisition module 32 is specifically configured to acquire the network type used by the client according to the value of the network type identifier in the transmission parameter field of the above message.
[0088] Figure 3 The congestion control device provided in the embodiment shown can be used to implement the present invention. Figure 2 The technical solution of the method embodiment shown, its implementation principle and technical effects can be further referred to the relevant description in the method embodiment.
[0089] Figure 4 A schematic diagram of the structure of an electronic device provided in one embodiment of this specification, such as Figure 4 As shown, the electronic device may include at least one processor; and at least one memory connected to the processor in communication, wherein: the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the instructions of this specification. Figure 2 The illustrated embodiment provides a congestion control method.
[0090] Among them, the above-mentioned electronic device can be a server, specifically, the above-mentioned server can be a QUIC server.
[0091] Figure 4 A block diagram of an exemplary electronic device suitable for implementing the embodiments of the present description is shown. Figure 4 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of this specification.
[0092] like Figure 4As shown, the electronic device is in the form of a general computing device. The components of the electronic device may include, but are not limited to: one or more processors 410, a communication interface 420, a memory 430, and a communication bus 440 connecting different components (including the memory 430, the communication interface 420 and the processing unit 410).
[0093] The communication bus 440 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus structures. For example, the communication bus 440 may include, but is not limited to, an industry standard architecture (ISA) bus, a micro channel architecture (MAC) bus, an enhanced ISA bus, a video electronics standards association (VESA) local bus, and a peripheral component interconnection (PCI) bus.
[0094] Electronic devices typically include a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device, including volatile and non-volatile media, removable and non-removable media.
[0095] The memory 430 may include a computer system readable medium in the form of a volatile memory, such as a random access memory (RAM) and / or a cache memory. The memory 430 may include at least one program product having a set (e.g., at least one) of program modules configured to execute the instructions of the present invention. Figure 2 Functionality of the illustrated embodiment.
[0096] A program / utility having a set (at least one) of program modules may be stored in the memory 430, such program modules including - but not limited to - an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include the implementation of a network environment. The program modules generally execute the instructions in this specification. Figure 2 The functions and / or methods in the described embodiments.
[0097] The processor 410 executes various functional applications and data processing by running the programs stored in the memory 430, such as implementing the present specification. Figure 2 The illustrated embodiment provides a congestion control method.
[0098] The embodiment of the present specification provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, wherein the computer instructions enable the computer to execute the present specification. Figure 2 The illustrated embodiment provides a congestion control method.
[0099] The above-mentioned non-transient computer-readable storage medium can adopt any combination of one or more computer-readable media. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, - but not limited to - electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive lists) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (read only memory, ROM), erasable programmable read-only memories (erasable programmable read only memory, EPROM) or flash memory, optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing programs, which can be used by instruction execution systems, devices or devices or used in combination with them.
[0100] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0101] The program code embodied on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
[0102] Computer program code for performing the operations of the present specification may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0103] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0104] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of this specification. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.
[0105] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this specification, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0106] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of this specification includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of this specification belong.
[0107] The word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.
[0108] It should be noted that the terminals involved in the embodiments of this specification may include but are not limited to personal computers (PCs), personal digital assistants (PDAs), wireless handheld devices, tablet computers, mobile phones, MP3 players, MP4 players, etc.
[0109] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0110] In addition, each functional unit in each embodiment of this specification may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0111] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes.
[0112] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.
Claims
1. A congestion control method, applied to a QUIC server, the method include: Receive a message sent by a client; wherein the message is a QUIC message; Acquire the service type requested by the client and the network type used by the client from the message; If the service type and the network type respectively belong to the service type and network type currently supported by the server, a first congestion control algorithm matching the service type and the network type is selected according to a predetermined matching rule, and congestion control is performed using parameters corresponding to the first congestion control algorithm.
2. The method according to claim 1, in, After obtaining the service type requested by the client and the network type used by the client from the message, the method further includes: If the service type does not belong to the service type currently supported by the server, and / or the network type does not belong to the network type currently supported by the server, congestion control is performed using a predetermined second congestion control algorithm and parameters corresponding to the second congestion control algorithm.
3. The method according to claim 1, in, The acquiring the service type requested by the client from the message includes: The service type requested by the client is obtained according to the value of the application transmission request identifier in the transmission parameter field of the message.
4. The method according to claim 1, in, The acquiring the network type used by the client from the message includes: The network type used by the client is obtained according to the value of the network type identifier in the transmission parameter field of the message.
5. The method according to any one of claims 1 to 4, in, The parameters include one or a combination of the following: initial window size, packet loss detection algorithm, threshold corresponding to the packet loss detection algorithm, PTO timer threshold, recovery time target threshold and delay confirmation threshold.
6. A congestion control device, arranged in a QUIC server, wherein the device include: A receiving module, used to receive a message sent by a client; wherein the message is a QUIC message; An acquisition module, used to acquire the service type requested by the client and the network type used by the client from the message; A congestion control module is used to select a first congestion control algorithm that matches the service type and the network type according to a predetermined matching rule when the service type and the network type respectively belong to the service type and the network type currently supported by the server, and use parameters corresponding to the first congestion control algorithm to perform congestion control.
7. The device according to claim 6, in, The congestion control module is also used to perform congestion control through a predetermined second congestion control algorithm and using parameters corresponding to the second congestion control algorithm when the service type does not belong to the service type currently supported by the server and / or the network type does not belong to the network type currently supported by the server.
8. The device according to claim 6, in, The acquisition module is specifically used to acquire the service type requested by the client according to the value of the application transmission request identifier in the transmission parameter field of the message.
9. The device according to claim 6, in, The acquisition module is specifically used to acquire the network type used by the client according to the value of the network type identifier in the transmission parameter field of the message.
10. An electronic device, include: at least one processor; as well as at least one memory in communication with the processor, wherein: The memory stores program instructions executable by the processor, and the processor can execute the method according to any one of claims 1 to 5 by calling the program instructions.
11. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions enable the computer to execute the method according to any one of claims 1 to 5.
