Congestion control method and device and computer readable storage medium

Through the interaction between TCP and PDCP sending end, congestion control is determined using the reorder status report of PDCP receiver, which solves the problem of insufficient interaction between TCP and air ports, improves user rate and throughput, and ensures traffic stability.

CN119012269APending Publication Date: 2024-11-22CHENGDU OPPO TELECOMM TECH CORP LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202310552069.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-16
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In the prior art, the interaction between the TCP protocol and the wireless air interface is insufficient, resulting in disconnection between the congestion control and the actual air interface. Occasional air interface jitter may cause TCP shrinking windows, resulting in large fluctuations in traffic and a decrease in user rate.

Method used

Through the interaction between the TCP sender and the PDCP sender, the reorder status report of the PDCP receiver determines whether to perform congestion control to ensure that the congestion control matches the utilization of air interface resources.

Benefits of technology

Improve user rate and throughput, avoid unnecessary congestion control, maximize the use of air interface capabilities, and improve traffic stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119012269A_ABST
    Figure CN119012269A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a congestion control method and device and a computer readable storage medium, which are used for realizing interaction between a TCP (Transmission Control Protocol) sending end and an air interface and determining whether to execute congestion control or not through resources of the air interface so as to improve the rate and throughput of a user. The method provided by the embodiment of the invention comprises the following steps: a TCP sending end sends a first data packet; the TCP sending end receives option information sent by a PDCP sending end, the option information is determined by the PDCP sending end according to a PDCP reordering state report sent by a PDCP receiving end, the PDCP reordering state report is fed back through indication of a specific value, and the specific value is a value for adding a target identifier to the first data packet; and the TCP sending end determines whether to execute congestion control according to the option information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a congestion control method, device, and computer-readable storage medium. Background Art

[0002] Under the existing technical solutions, when the Transmission Control Protocol (TCP) transmitter performs flow control, it considers the overall situation of the transmission link; however, in general, the wireless air interface is the main channel for limiting the rate due to its limited bandwidth and complex and changeable environment. The current protocols and traditional technical solutions lack effective interaction between the TCP protocol and the air interface situation, resulting in a separation between TCP congestion control and the actual situation of the air interface. Occasional air interface jitter may cause TCP to shrink the window, but the air interface capacity is actually very strong, which will lead to the inability to truly utilize the air interface resources, resulting in large traffic fluctuations and reduced user rates. Summary of the invention

[0003] The embodiments of the present application provide a congestion control method, device and computer-readable storage medium for realizing the interaction between a TCP sender and an air interface, and determining whether to perform congestion control through the resources of the air interface, thereby improving user rate and throughput.

[0004] In a first aspect, the present application provides a congestion control method, which is applied to a TCP sender, wherein the TCP sender is connected to a PDCP sender, and the PDCP sender is connected to a PDCP receiver. The method may include:

[0005] The TCP sending end sends a first data packet;

[0006] The TCP sending end receives option information sent by the PDCP sending end, where the option information is determined by the PDCP sending end according to a PDCP reordering status report sent by the PDCP receiving end, where the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value of adding a target identifier to the first data packet;

[0007] The TCP sending end determines whether to perform congestion control according to the option information.

[0008] A second aspect of the present application provides a congestion control method, which is applied to a PDCP sending end, a TCP sending end is connected to the PDCP sending end, and the PDCP sending end is connected to a PDCP receiving end. The method may include:

[0009] The PDCP sending end receives a first data packet sent by the TCP sending end;

[0010] The PDCP transmitting end sends a second data packet to the PDCP receiving end on multiple carriers, where the second data packet is the first data packet carrying a target identifier, where the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report;

[0011] The PDCP transmitting end receives the PDCP reordering status report sent by the PDCP receiving end;

[0012] The PDCP transmitting end determines option information according to the PDCP reordering status report;

[0013] The PDCP sending end sends the option information to the TCP sending end, where the option information is used to indicate whether to perform congestion control.

[0014] A third aspect of the present application provides a congestion control method, which is applied to a PDCP receiving end, a TCP sending end is connected to the PDCP sending end, and the PDCP sending end is connected to the PDCP receiving end. The method may include:

[0015] The PDCP receiving end receives a second data packet sent by the PDCP transmitting end, and starts a reordering timer, wherein the second data packet carries a target identifier, and a value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report;

[0016] When the reordering timer times out, the PDCP receiving end feeds back a PDCP reordering status report to the PDCP transmitting end, where the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

[0017] A fourth aspect of the present application provides a congestion control device, which may include:

[0018] A sending module, used for sending a first data packet;

[0019] a receiving module, configured to receive option information sent by a PDCP transmitting end, wherein the option information is determined by the PDCP transmitting end according to a PDCP reordering status report sent by a PDCP receiving end, wherein the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value of adding a target identifier to the first data packet;

[0020] The processing module is used to determine whether to perform congestion control according to the option information.

[0021] A fifth aspect of the present application provides a congestion control device, which may include:

[0022] A receiving module, used for receiving a first data packet sent by a TCP sending end;

[0023] a sending module, configured to send a second data packet to a PDCP receiving end on multiple carriers, wherein the second data packet is a first data packet carrying a target identifier, wherein a value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report;

[0024] The receiving module is further configured to receive the PDCP reordering status report sent by the PDCP receiving end;

[0025] A processing module, configured to determine option information according to the PDCP reordering status report;

[0026] The sending module is further used to send the option information to the TCP sending end, and the option information is used to indicate whether to perform congestion control.

[0027] A sixth aspect of the present application provides a congestion control device, which may include:

[0028] A receiving module, configured for a PDCP receiving end to receive a second data packet sent by a PDCP transmitting end, and start a reordering timer, wherein the second data packet carries a target identifier, and the value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report;

[0029] The sending module is used to feed back a PDCP reordering status report to the PDCP sending end when the reordering timer times out, wherein the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

[0030] On the other hand, the present application provides a computer-readable storage medium, including instructions, which, when executed on a processor, enables the processor to execute the method described in the first aspect of the present application, or the second aspect of the present application, or the third aspect of the present application.

[0031] On another aspect, the present application discloses a computer program product. When the computer program product runs on a computer, the computer executes the method described in the first aspect, the second aspect, or the third aspect of the present application.

[0032] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0033] In an embodiment of the present application, a TCP sender sends a first data packet; the TCP sender receives option information sent by a PDCP sender, the option information is determined by the PDCP sender according to a PDCP reordering status report sent by a PDCP receiver, the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value for adding a target identifier to the first data packet; the TCP sender determines whether to perform congestion control according to the option information. Because the option information is determined by the PDCP receiver according to the PDCP reordering status report sent by the PDCP sender, that is, the TCP sender implements interaction with the air interface, and determines whether to perform congestion control through the resources of the air interface, thereby improving user rate and throughput. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments and the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and other drawings can be obtained based on these drawings.

[0035] Figure 1A This is a schematic diagram of the TCP header structure;

[0036] Figure 1B and Figure 1C In order to Figure 1A A schematic diagram illustrating the option information;

[0037] Figure 1D This is a schematic diagram of the PDCP data message structure defined in 3GPP 38323;

[0038] Figure 1E This is a schematic diagram of the PDCP control message structure defined in 3GPP 38323;

[0039] Figure 2A This is a schematic diagram of the modification of the data message structure in the embodiment of the present application;

[0040] Figure 2B This is a schematic diagram of a control message structure in an embodiment of the present application;

[0041] Figure 2C A schematic diagram of option information in an embodiment of the present application;

[0042] Figure 3 A schematic diagram of an embodiment of a congestion control method in an embodiment of the present application;

[0043] Figure 4 A schematic diagram of an embodiment of a congestion control device in an embodiment of the present application;

[0044] Figure 5 This is a schematic diagram of another embodiment of the congestion control device in the embodiment of the present application;

[0045] Figure 6 This is a schematic diagram of another embodiment of the congestion control device in the embodiment of the present application;

[0046] Figure 7 This is a schematic diagram of an embodiment of a TCP sending end in an embodiment of the present application;

[0047] Figure 8 This is a schematic diagram of an embodiment of a PDCP transmitting end in an embodiment of the present application;

[0048] Fig. 9 This is a schematic diagram of an embodiment of a PDCP receiving end in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The embodiments of the present application provide a congestion control method, device and computer-readable storage medium for realizing the interaction between a TCP sender and an air interface, and determining whether to perform congestion control through the resources of the air interface, thereby improving user rate and throughput.

[0050] In order to make the technical personnel in the technical field better understand the scheme of the present application, the technical scheme in the embodiment of the present application will be described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, not all of the embodiments. Based on the embodiments in the present application, they should all fall within the scope of protection of the present application.

[0051] For terminal uplink data, the current traditional method is that the terminal sends data to the access network (such as the base station) side, and then forwards it to the corresponding server through the core network. With the development of 5G technology, the requirements for air interface network speed in the future will be extremely high (such as massive cloud data interaction, virtual reality (VR), high-speed requirements for high-definition video, etc.), but the rate that can be achieved by the traditional new wireless (New Radio, NR) 100 megahertz (MHz) bandwidth will be difficult to meet the demands. A better way is to use dual connectivity (Dual Connectivity, DC) (such as EN-DC (eNB NR Dual Connection, dual connection between 4G wireless access network and 5G NR), NE-DC (NR eNB Dual Connection, dual connection between 5G NR and 4G wireless access network), NR-DC (New Radio-Dual Connectivity, new radio dual connection)) or carrier aggregation (Carrier Aggregation, CA) and other multi-carrier methods to increase network bandwidth and speed. However, in a multi-carrier scenario, data is transmitted through different air interfaces. Occasional air interface environment jitter may cause the Packet Data Convergence Protocol (PDCP) sequence number (SN) to be out of order, causing PDCP reordering and packet loss, which in turn causes TCP packet loss. For the TCP sender (also known as the TCP protocol stack), after sensing packet loss, it will think that the air interface is congested and the sending window will shrink, causing a rapid drop in overall traffic. However, the air interface capacity is still very strong at this time, and TCP congestion control will result in the inability to fully utilize the air interface capacity.

[0052] The following is a brief description of PDCP SN reordering, air interface capability indication, TCP protocol stack processing, and TCP data air interface forwarding strategy in a multi-carrier scenario.

[0053] The 3rd Generation Partnership Project (3GPP) protocol stipulates that the PDCP layer needs to deliver data packets upward in order. In a multi-carrier scenario, it is equivalent to data packets arriving at the receiving end from different links. Although each manufacturer has its own diversion strategy, in the face of complex air interface environment fluctuations, there will still be discontinuous PDCP SN numbers when data packets arrive at the PDCP layer (packet loss caused by discontinuous SN numbers, for the specific logic, refer to the section "Basic Principles of PDCP Reordering" below). Due to the in-order delivery function of PDCP; after the reordering timeout, it will be delivered in order. Subsequently, the data packets received after the reordering will be discarded. For these discarded data packets, the sending side will consider the network congestion for the TCP protocol stack, triggering its congestion control, reducing its congestion window (cwnd), thereby reducing its data packet sending rate. For the air interface, the phenomenon it perceives is that the incoming TCP traffic is insufficient, resulting in a reduction in overall traffic.

[0054] like Figure 1A The following is a schematic diagram of the TCP header structure. Figure 1A The TCP header structure shown in the figure is described as follows:

[0055] 16-bit port number: includes the source port number and the destination port number. When performing TCP communication, the client usually uses a temporary port number automatically selected by the system (usually very large), while the server uses a well-known service port number or a port number customized by the server administrator.

[0056] 32-bit sequence number: The number of each byte in a byte stream in a transmission direction during a TCP communication (arranged in sequence from the first segment in this direction). Assuming that host A and host B are communicating via TCP, the sequence number value in the first TCP segment sent by A to B is a random value ISN (initial sequence number value) initialized by the system. Then the sequence number value in the TCP segment sent from A to B will be set by the system to be ISN plus the offset of the first byte of the data carried by the segment in the entire data byte stream.

[0057] 32-bit acknowledgment number: used to respond to the TCP segment sent by the other party. Its value is the sequence number of the segment received from the other party plus 1.

[0058] 4-bit header length: identifies how many 32-bit words (4 bytes) the TCP header has. There are 4 bits in total, so the maximum TCP header size that can be represented is 60 bytes.

[0059] The 6-bit flag contains the following items:

[0060] The URG flag indicates whether the urgent pointer is valid.

[0061] The ACK flag indicates whether the confirmation number is valid. The message segment carrying the ACK flag is generally called the confirmation message segment.

[0062] The PSH flag prompts the receiving application to immediately read data from the TCP receive buffer.

[0063] The RST flag indicates that the other party is required to reestablish the connection. The TCP segment carrying the RST flag is called a reset segment.

[0064] The SYN flag indicates a request to establish a connection. A TCP segment carrying the SYN flag is called a synchronization segment.

[0065] The FIN flag indicates that the other end is notified that the connection will be closed. The TCP segment carrying the FIN flag is called the end segment.

[0066] 16-bit window size: It is a means of TCP flow control. The window here refers to the receive notification window (cwnd). It tells the other party how many bytes of data the local TCP receive buffer can accommodate, so that the other party can control the speed of sending data.

[0067] 16-bit checksum: filled by the sender, the receiver performs a CRC algorithm on the TCP segment to verify whether the TCP segment is damaged during transmission (including the TCP header and data part). This is also an important guarantee for TCP reliable transmission.

[0068] 16-bit urgent pointer: is a positive offset. It is added to the value of the sequence number field to indicate the sequence number of the next byte of the last urgent data. That is, this field is the offset of the urgent pointer relative to the current sequence number, which is the urgent offset. This allows the receiver to quickly receive the urgent data. TCP's urgent pointer is a method for the sender to send urgent data to the receiver.

[0069] like Figure 1B and Figure 1C As shown, it is a prior art about Figure 1A The schematic diagram for explaining the option information of the packet. The option information may include option (kind), length (length) and information (info). kind can be equal to 0, 1, 2, 3, 4, 5 and 8.

[0070] The following is an introduction to the basic principles of PDCP reordering. First, the following variables are introduced:

[0071] RCVD_COUNT: the sequence number value of the received PDCP data packet;

[0072] RX_DELIV: indicates the first sequence number value that needs to be submitted to the upper layer but has not yet been submitted;

[0073] RX_NEXT: Represents the sequence number value of the data packet that has not been received yet;

[0074] RX_REORD: Represents the first sequence number value after the sequence number of the data packet that triggers PDCP reordering;

[0075] t-Reordering: Reordering timer.

[0076] The 3GPP protocol stipulates that the NR PDCP entity has the functions of reordering and in-sequence delivery. The reordering function is as follows:

[0077] When the PDCP receives a data packet delivered by the RLC (Radio Link Control), the following judgments are made:

[0078] 1) If RCVD_COUNT < RX_DELIV or a data packet with RCVD_COUNT has been received, then discard the data packet; otherwise, proceed to the next step;

[0079] 2) If the RCVD_COUNT of this data packet >= RX_NEXT, update RX_NEXT to RCVD_COUNT + 1; and put the data packet into the cache queue;

[0080] 3) If RCVD_COUNT = RX_DELIV; deliver all in-sequence data packets starting from RX_DELIV, and update RX_DELIV to the sequence number of the first data packet that has not been delivered in sequence;

[0081] 4) If t-Reordering is running and RX_DELIV >= RX_REORD; reset t-Reordering and start running this timer;

[0082] 5) If t-Reordering is not running (including the stop triggered in step 4), and RX_DELIV < RX_NEXT; update RX_REORD to RX_NEXT. Start t-Reordering.

[0083] For the reordering timer, if the reordering timer expires:

[0084] Data packets before RX_REORD: Deliver the data packets with sequence number values before RX_REORD in ascending order of sequence number values;

[0085] Data packets after RX_REORD: Starting from RX_REORD, deliver all received data packets with consecutive sequence numbers;

[0086] Update RX_DELIV to the sequence number of the first data packet that is greater than RX_REORD and has not been delivered yet;

[0087] If RX_DELIV < RX_NEXT; update RX_REORD to RX_NEXT;

[0088] Restart the reordering timer.

[0089] Since the data packets received by PDCP come from the RLC entities of LTE and NR respectively, there may be a large gap (GAP) in the sequence numbers of its data packets, which may lead to data packet loss. For example, assume that the LTE side has received a data packet (its sequence number is 100) and successfully delivered it to PDCP; the data packet on the NR side (assuming the sequence number value is less than 100) has not been received yet due to the radio link environment or lack of scheduling opportunities at this time; after the PDCP reordering timer times out, the PDCP entity delivers the data packet 100 and updates RX_DELIV to 101; for the subsequent data packets received by the NR side, since their values are less than RX_DELIV, they will all be discarded, and the discarded data packets are called PDCP discarded packets.

[0090] The following introduces and explains the radio interface for PDCP reordering packet loss:

[0091] As Figure 1D shown, it is a schematic diagram of the PDCP data packet structure defined in 38323 of 3GPP. Here, the 18-bit (bit) PDCP SN is used as an example for explanation. Among them, in Figure 1D shown, D / C: used to determine whether it is a data packet or a control packet. 0: indicates it is a control packet; 1: indicates it is a data packet; R: indicates the reserved field; PDCP SN: indicates the PDCP sequence number; MAC-I: indicates the authorization code information.

[0092] As Figure 1E shown, it is a schematic diagram of the PDCP control packet structure defined in 38323 of 3GPP. Among them, in Figure 1E shown, D / C: used to determine whether it is a data packet or a control packet. 0: indicates it is a control packet; 1: indicates it is a data packet; FMC: First Missing COUNT, indicating the first missing data packet within the reordering window; Bitmap: indicating the loss situation of the data packets, used in conjunction with FMC.

[0093] As shown in Table 1, the Figure 1E protocol data unit (PDU) types in it are described.

[0094] Table 1: Figure 1E Protocol data unit type in

[0095]

[0096] As shown in Table 2, the bitmap is described.

[0097] Table 2: Description of bitmap

[0098]

[0099] In the embodiment of the present application, the data message structure and the control message structure can be modified respectively, so as to exchange packet loss information caused by PDCP reordering timeout between the terminal and the base station. Figure 2A As shown, it is a schematic diagram of the modification of the data message structure in the embodiment of the present application.

[0100] exist Figure 2A As shown, the sending side can use a reserved field, marked as a target identifier, for example, marked as I (indicator to send discard PDCP SDU with reordering, used to instruct the receiving side to send discarded data packet information caused by PDCP reordering timeout). Exemplarily, when the value of I is a specific value of 1, it indicates that the receiving side needs to send a status report to the sending side that the data packet cannot be received due to the timeout of the reordering timer (subsequently described by the PDCP reordering status report); when the value of I is 0, it indicates that the receiving side does not need to send a status report to the sending side that the data packet cannot be received due to the timeout of the reordering timer.

[0101] The structure of the PDCP reordering status report of the corresponding receiving side multiplexes the PDCP control message, and a target field (for example, 100, or 101, 102, etc., not limited in this application, and 100 is used as an example for explanation in the embodiment of this application) can be added to the PDUType. The target field is selected from the reserved fields (100-111).

[0102] When the first 3 bits of the PDU are the target field (e.g. 100), it indicates that the status report is a PDCP reordering status report. Figure 1E The PDU Type in the protocol adds the target field 100 and the reserved bits are updated to 101-111.

[0103] Table 3: Description of the target field added to PDU Type

[0104] Bit Description 000 PDCP status report 001 Interspersed ROHC feedback 010 EHC feedback 011 UDC feedback 100 PDCP reordering status report 101-111 Reserved

[0105] like Figure 2B As shown, it is a schematic diagram of the control message structure in the embodiment of the present application. Among them, FMC represents the sequence number of the first data packet that PDCP fails to deliver to the upper layer in sequence when the reordering timeout occurs; the bitmap represents: starting from FMC (excluding), according to the sequence number order, the PDCP SDU that has not been received is set to 0, and the PDCP SDU that has been received is set to 1 (including data packets that failed to decompress); until the PDCP reordering sequence number lower limit RX_REORD is reached. This message is triggered when the PDCP reordering timer times out.

[0106] like Figure 2C As shown, it is a schematic diagram of the option information in the embodiment of the present application. Compared with the prior art, the value of kind is added. The value of the added kind can be any value other than 0, 1, 2, 3, 4, 5 and 8. In the present application, the value of the added kind is equal to 9 as an example for explanation, the corresponding length length = 2, and the corresponding information info is the air interface congestion indication identifier (1 byte).

[0107] If the air interface congestion indication flag is the first flag (for example, 0), the air interface congestion judgment condition is ignored;

[0108] When the air interface congestion indication flag is the second flag (for example, 1), it indicates that the current air interface state is not congested, and it is desired that the TCP sender does not perform congestion control (for example, does not perform window reduction);

[0109] When the air interface congestion indication flag is the third flag (for example, 2), it indicates that the current air interface state is congested, and the TCP sender is expected to perform congestion control (for example, reduce the window) and data back pressure to reduce the air interface buffer pressure;

[0110] Others: Reserved.

[0111] Optionally, if the air interface congestion indication flag is the first flag (for example, 0), the air interface congestion judgment condition is ignored;

[0112] When the air interface congestion indication flag is the fourth flag (for example, 3), it indicates that the current air interface state is not congested, and the TCP sender may perform congestion control or not, depending on the actual situation;

[0113] When the air interface congestion indication flag is the second flag (for example, 1), it indicates that the current air interface state is not congested, and it is desired that the TCP sender does not perform congestion control (for example, does not perform window reduction);

[0114] When the air interface congestion indication flag is the third flag (for example, 2), it indicates that the current air interface state is congested, and the TCP sender is expected to perform congestion control (for example, reduce the window) and data back pressure to reduce the air interface buffer pressure;

[0115] Others: Reserved.

[0116] The technical solution of the present application is further described below by way of embodiments. Figure 3 As shown, it is a schematic diagram of an embodiment of the congestion control method in the embodiment of the present application, and the embodiment is applied to a data transmission system, and the data transmission system includes a TCP sender, a PDCP sender and a PDCP receiver, and the TCP sender is connected to the PDCP sender, and the PDCP sender is connected to the PDCP receiver. This embodiment may include:

[0117] 301. A TCP sender sends a first data packet. A PDCP sender receives the first data packet sent by a TCP sender. The TCP sender (also referred to as a TCP protocol stack sender) sends data packets normally.

[0118] Optionally, the embodiment of the present application is applied to a scenario where multi-carrier transmission exists and the sequence number order is guaranteed. It can be understood that the embodiment of the present application can be applied to all scenarios where multi-link transmission exists and the SN sequence is preserved.

[0119] 302. The PDCP transmitter sends a second data packet to the PDCP receiver on multiple carriers according to the first data packet, where the second data packet is the first data packet carrying a target identifier, and the value of the target identifier is a specific value, which is used to instruct the PDCP receiver to feedback a PDCP reordering status report.

[0120] Exemplary, reference Figure 2A As shown, the second data packet marks the reserved field as the target identifier I. When the value of I is a specific value 1, it indicates that the PDCP receiving end feeds back the PDCP reordering status report. When the value of I is 0, it indicates that the PDCP receiving end does not feed back the PDCP reordering status report. That is, for a PDCP data packet, if it is sent on multiple carriers, the PDCP sending end sets the I field bit to 1 in the PDCP data packet, indicating that the PDCP receiving end needs to send a PDCP reordering status report. The PDCP sending end sends the PDCP data packet to the air interface.

[0121] Through the embodiments of the present application, the packet loss information caused by PDCP reordering at the PDCP receiving end can be obtained at the PDCP sending end, so that the PDCP sending end can judge the actual situation of the data packet sent by the air interface at this time.

[0122] Optionally, the PDCP transmitting end may be a base station or a terminal. When the PDCP transmitting end is a base station, the PDCP receiving end is a terminal; when the PDCP transmitting end is a terminal, the PDCP receiving end is a base station.

[0123] 303. The PDCP receiving end receives a second data packet sent by the PDCP transmitting end and starts a reordering timer. The second data packet carries a target identifier. The value of the target identifier is a specific value. The specific value is used to instruct the PDCP receiving end to feedback a PDCP reordering status report.

[0124] The PDCP receiving end receives the PDCP data packet and starts the reordering timer.

[0125] 304. When the reordering timer times out, the PDCP receiving end feeds back a PDCP reordering status report to the PDCP transmitting end. The PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

[0126] The PDCP transmitting end receives the PDCP reordering status report sent by the PDCP receiving end.

[0127] Optionally, when the reordering timer times out, the PDCP receiving end feeds back a PDCP reordering status report to the PDCP sending end, which may include: when the reordering timer times out, the PDCP receiving end sets the first three bits of the protocol data unit PDU type in the control message to the second target value, and feeds back a reordering status report to the sending end.

[0128] Exemplarily, referring to Table 3 above, when the reordering timer times out, the PDU Type in the control message is set to 4 (corresponding to 100), and a PDCP reordering status report is fed back to the PDCP receiving end according to the packetization method mentioned above.

[0129] 305. The PDCP transmitter determines option information according to the PDCP reordering status report.

[0130] Optionally, the option information includes options, length and information; when the value of the option includes the first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier (for example, 0), a second identifier (for example, 1), and a third identifier (for example, 2); the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0131] Optionally, the PDCP transmitting end determines option information according to the PDCP reordering status report, which may include: the PDCP transmitting end parses the PDCP reordering status report to determine packet loss information; the PDCP transmitting end determines option information according to the packet loss information.

[0132] Exemplarily, the PDCP transmitting end parses the PDCP reordering status report, obtains data packet loss information of the PDCP receiving end when the data packet is sent on multiple carriers, and determines the option information according to the data packet loss information.

[0133] Optionally, the PDCP transmitter determines option information according to the packet loss information, which may include: when the PDCP transmitter determines according to the packet loss information that the packet loss rate is greater than the packet loss threshold, if the rates of multiple carriers are greater than the first rate threshold, and the current cache is less than the first cache threshold, then the first option information is determined, the option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag or the fourth flag, the second flag indicates that the current air interface state is non-congested, indicating that the TCP transmitter does not perform congestion control, and the fourth flag indicates that the current air interface state is non-congested, indicating that the TCP transmitter can Congestion control may be performed or not (depending on the actual situation); or, when the PDCP transmitter determines that the packet loss rate is greater than the packet loss threshold based on the packet loss information, if there is a carrier with a rate less than the second rate threshold among multiple carriers, or the current cache is greater than the second cache threshold, then the second option information is determined, and the option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag, which indicates that the congestion judgment condition of the air interface is ignored; wherein the first rate threshold is greater than or equal to the second rate threshold, and the first cache threshold is less than or equal to the second cache threshold.

[0134] Optionally, the first option information and the second option information may be carried in a data packet specially generated by the PDCP transmitter, or may be carried in a data packet with unfilled option fields received by the PDCP transmitter, and this application does not limit this.

[0135] Optionally, when the PDCP transmitter determines based on the packet loss information that the packet loss rate is greater than the packet loss threshold, if the rates of multiple carriers are greater than the first rate threshold, and the current cache is less than the first cache threshold, then the first option information is determined, which may include: when the PDCP transmitter determines based on the packet loss information that the packet loss rate is greater than the packet loss threshold, if the rates of multiple carriers are all greater than the first rate threshold, and the current cache is less than the first cache threshold, and the current cache can be cleared within a first preset time period, then the first option information is determined.

[0136] Exemplarily, if the packet loss rate of the data packets is greater than the packet loss threshold, it can be considered that the PDCP reordering packet loss is large. If the rates in the multi-carriers are all greater than the first rate threshold at this time, it can be considered that the rates in the multi-carriers are relatively stable, and the current cache of the PDCP is less than the first cache threshold, it can be considered that the current cache is small, and it is estimated that the current cache can be cleared within the first preset time length, it can be considered that the current cache can be cleared faster (for example, layer 2 cache / rate is less than the threshold), and the first option information can be determined. Reference Figure 2C As shown, in the first option information, kind is filled with 9, and the air interface congestion indication flag is set to 1, indicating that the current air interface state is not congested, indicating that the TCP sender does not perform congestion control, that is, does not need to shrink the window. If there is an option field in the data packet received by the PDCP sender without a value, kind can be filled with 9, and the following indication can be filled with 1, indicating that the current air interface state is not congested, indicating that the TCP sender performs congestion control.

[0137] Optionally, when the PDCP transmitter determines, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold, if there is a carrier with a rate less than the second rate threshold among multiple carriers, or the current cache is greater than the second cache threshold, then determining the second option information may include: when the PDCP transmitter determines, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of multiple carriers are less than the second rate threshold, or the current cache is greater than the second cache threshold, and the current cache cannot be cleared within the second preset time length, then determining the second option information. The second preset time length is greater than or equal to the first preset time length.

[0138] Exemplarily, if the packet loss rate of the data packets is greater than the packet loss threshold, it can be considered that the PDCP reordering packet loss is large. If at this time there is a carrier with a rate less than the second rate threshold in the multi-carrier, the rate of the carrier may be poor, or the current cache of the PDCP is greater than the second cache threshold, it can be considered that the current cache is large, and it is estimated that the current cache cannot be cleared within the second preset time, that is, it can be considered that it currently takes a long time to clear (the cache amount is greater than threshold 2), and the second option information can be determined. Reference Figure 2C As shown, in the second option information, kind is filled with 9, and the air interface congestion indication flag is set to 0, indicating that the air interface congestion judgment condition is ignored. If the option field in the data packet received by the PDCP transmitter is not filled with a value, kind can be filled with 9, and the following indication can be filled with 0, indicating that the air interface congestion judgment condition is ignored.

[0139] Optionally, the method may also include: when there is a carrier with a rate lower than the second rate threshold in the multi-carrier rate, and the current cache is larger than the second cache threshold, the PDCP sender determines third option information, the option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to a third flag, the third flag indicates that the current air interface status is congested, and instructs the TCP sender to perform congestion control.

[0140] Exemplarily, if the PDCP transmitter determines that there is a carrier with a rate lower than the second rate threshold among the multi-carrier rates, it can be considered that the air interface rate is reduced, and the current buffer is larger than the second buffer threshold, it can be considered that the buffer amount is too large to be sent quickly, and the third option information is determined. Figure 2C As shown, in the third option information, kind is filled with 9, and the congestion indication is set to 2, indicating that the current air interface state is congested, instructing the TCP sender to perform congestion control, reduce incoming packets, and reduce the PDCP sender buffer pressure through back pressure.

[0141] Through the embodiments of the present application, it is possible to indicate whether the TCP sender is currently experiencing false air interface link congestion, thereby avoiding misjudgment of congestion and causing a decrease in overall traffic.

[0142] 306. The PDCP sender sends option information to the TCP sender, where the option information is used to indicate whether to perform congestion control.

[0143] The TCP sender receives option information sent by the PDCP sender, where the option information is determined by the PDCP sender based on a PDCP reordering status report sent by the PDCP receiver. The PDCP reordering status report is fed back via a specific value indication, where the specific value is the value of adding a target identifier to the first data packet.

[0144] Optionally, the option information includes first option information, second option information, or third option information; in the first option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the second flag; in the second option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the first flag; in the third option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the third flag.

[0145] Optionally, the method may further include: the PDCP transmitter calculates information about actual lost data packets based on the packet loss information and the header of the first data packet; the PDCP transmitter sends a SACK (Selective Acknowledge) to the TCP transmitter, where the SACK includes information about actual lost data packets.

[0146] Exemplarily, after receiving the PDCP packet loss information from the PDCP receiving end, the PDCP sending end calculates the actual lost TCP packets in combination with the TCP header, and transmits the calculations to the TCP sending end via SACK.

[0147] 307. The TCP sender determines whether to perform congestion control based on the option information.

[0148] Optionally, the TCP sender determines whether to perform congestion control based on the option information, which may include: the TCP sender does not perform congestion control based on the first option information; or, the TCP sender ignores the congestion judgment condition of the air interface and performs congestion control according to the existing strategy based on the second option information; or, the TCP sender performs congestion control based on the third option information.

[0149] Optionally, after the TCP sending end does not perform congestion control according to the first option information, the method may further include: if the TCP sending end determines that there is air interface packet loss, not performing congestion control; otherwise, performing congestion control.

[0150] Exemplarily, after receiving the first option information indicating that congestion control is not required, the TCP sender determines that congestion is caused by air interface packet loss and does not need to perform congestion control; otherwise, congestion control is performed.

[0151] Optionally, the method may also include: the TCP sending end receives the SACK sent by the PDCP sending end, the SACK includes the information of the data packet actually lost; the TCP sending end compares the SACK and ACK, the ACK is the confirmation information sent by the PDCP sending end that the first data packet has been received; when the ACK includes the information of the data packet actually lost in the SACK, it is determined that it is air interface packet loss; when the ACK does not include the information of the data packet actually lost in the SACK, it is determined that it is not air interface packet loss.

[0152] Optionally, the TCP sender determines whether to perform congestion control based on the option information, which may include: when it is determined that air interface packet loss occurs, the TCP sender does not perform congestion control based on the first option information; or, when it is determined that air interface packet loss occurs, the TCP sender ignores the congestion judgment condition of the air interface based on the second option information and performs congestion control according to the existing strategy; or, when it is determined that air interface packet loss occurs, the TCP sender performs congestion control based on the third option information.

[0153] Exemplarily, after receiving SACK, the TCP sender compares the data packets of the SACK and TCP ACK to determine whether it is an actual air interface packet loss. If so, and based on the option information fed back by the PDCP sender, it determines whether the current air interface state is congested. If so, congestion control is performed (for example, window reduction is performed); if not, congestion control is not performed (for example, window reduction is not performed).

[0154] In the embodiment of the present application, the TCP sender sends a first data packet; the TCP sender receives the option information sent by the PDCP sender, the option information is determined by the PDCP sender according to the PDCP reordering status report sent by the PDCP receiver, the PDCP reordering status report is fed back through a specific value indication, and the specific value is the value of adding a target identifier to the first data packet; the TCP sender determines whether to perform congestion control according to the option information. Because the option information is determined by the PDCP receiver according to the PDCP reordering status report sent by the PDCP sender, that is, the TCP sender implements the interaction with the air interface, and determines whether to perform congestion control through the resources of the air interface, thereby improving the stability and throughput of the user rate.

[0155] In the embodiment of the present application, a strategy for the interaction between the air interface and TCP is designed to reduce unnecessary congestion control by sensing the actual packet loss information of the air interface. 1) The PDCP reordering timeout packet loss indication is designed for the PDCP transmitter and the PDCP receiver, so that the data diversion side can more reliably judge its diversion gain; 2) The interaction between TCP and the air interface is designed to solve unnecessary congestion control. At the same time, it can also assist in back pressure control and reduce the air interface buffer pressure; 3) It solves the problem of unstable traffic when the TCP protocol stack congestion control and the air interface do not match in the multi-carrier scenario, and can maximize the use of air interface capabilities and improve traffic. Through the embodiment of the present application, the interaction between TCP and the air interface can be realized, and the rationality of TCP congestion control is improved. At the same time, through the embodiment of the present application, the stability and throughput of the user rate can be greatly improved, which greatly improves the user perception.

[0156] like Figure 4 As shown, it is a schematic diagram of an embodiment of a congestion control device in an embodiment of the present application, which may include: a sending module 401 is used to send a first data packet; a receiving module 402 is used to receive option information sent by a PDCP sending end, the option information is determined by the PDCP sending end according to a PDCP reordering status report sent by a PDCP receiving end, and the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value for adding a target identifier to the first data packet; a processing module 403 is used to determine whether to perform congestion control based on the option information.

[0157] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0158] Optionally, the option information includes first option information, second option information, or third option information; in the first option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the second flag; in the second option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the first flag; in the third option information, the option is filled in with the first target value, and the air interface congestion indication flag is set to the third flag; the processing module 403 is specifically used to not perform congestion control according to the first option information; or, the processing module 403 is specifically used to ignore the congestion judgment condition of the air interface according to the second option information, and perform congestion control according to an existing strategy; or, the processing module 403 is specifically used to perform congestion control according to the third option information.

[0159] Optionally, the receiving module 402 is also used to receive the SACK sent by the PDCP sending end, and the SACK includes information about the data packet actually lost; the processing module 403 is also used to compare the SACK and ACK, and the ACK is confirmation information sent by the PDCP sending end that the first data packet has been received; when the ACK includes information about the data packet actually lost in the SACK, it is determined that it is air interface packet loss; the processing module 403 is specifically used for, when it is determined that it is air interface packet loss, the TCP sending end does not perform congestion control according to the first option information; or, the processing module 403 is specifically used for, when it is determined that it is air interface packet loss, the TCP sending end ignores the congestion judgment condition of the air interface according to the second option information, and performs congestion control according to the existing strategy; or, the processing module 403 is specifically used for, when it is determined that it is air interface packet loss, the TCP sending end performs congestion control according to the third option information.

[0160] like Figure 5As shown, it is a schematic diagram of another embodiment of the congestion control device in the embodiment of the present application, which may include: a receiving module 501, used to receive a first data packet sent by a TCP sending end; a sending module 502, used to send a second data packet to a PDCP receiving end on multiple carriers, wherein the second data packet is a first data packet carrying a target identifier, and the value of the target identifier is a specific value, and the specific value is used to indicate that the PDCP receiving end feeds back a PDCP reordering status report; the receiving module 501 is also used to receive the PDCP reordering status report sent by the PDCP receiving end; the processing module 503 is used to determine option information according to the PDCP reordering status report; the sending module 502 is also used to send the option information to the TCP sending end, and the option information is used to indicate whether to perform congestion control.

[0161] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0162] Optionally, the processing module 503 is specifically used to parse the PDCP reordering status report to determine packet loss information; and determine option information based on the packet loss information.

[0163] Optionally, the processing module 503 is specifically used to determine, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold. If the rates of the multiple carriers are all greater than the first rate threshold, and the current cache is less than the first cache threshold, then determine the first option information, in which the option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag, the second flag indicates that the current air interface state is non-congested, indicating that the TCP sender does not perform congestion control; or, the processing module 503 is specifically used to determine, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold. If there is a carrier among the multiple carriers whose rate is less than the second rate threshold, or the current cache is greater than the second cache threshold, then determine the second option information, in which the option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag, and the first flag indicates that the congestion judgment condition of the air interface is ignored; wherein, the first rate threshold is greater than or equal to the second rate threshold, and the first cache threshold is less than or equal to the second cache threshold.

[0164] Optionally, the processing module 503 is specifically used to determine, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are all greater than a first rate threshold, and the current cache is less than the first cache threshold, and the current cache can be cleared within a first preset time period, then determine the first option information; the processing module 503 is specifically used to determine, based on the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are less than a second rate threshold, or the current cache is greater than the second cache threshold, and the current cache cannot be cleared within a second preset time period, then determine the second option information; wherein the second preset time period is greater than or equal to the first preset time period.

[0165] Optionally, the processing module 503 is also used to determine third option information when there is a carrier with a rate less than a second rate threshold in the multi-carrier rate and the current cache is greater than the second cache threshold, wherein the option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to a third flag, wherein the third flag indicates that the current air interface status is congested, and instructs the TCP sender to perform congestion control.

[0166] Optionally, the processing module 503 is further used to calculate the actual lost data packet information based on the packet loss information and the header of the first data packet; the sending module 502 is further used to send SACK to the TCP sending end, and the SACK includes the actual lost data packet information.

[0167] like Figure 6 As shown, it is a schematic diagram of another embodiment of the congestion control device in the embodiment of the present application, which may include: a receiving module 601, which is used for the PDCP receiving end to receive a second data packet sent by the PDCP sending end, and start a reordering timer, wherein the second data packet carries a target identifier, and the value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feedback a PDCP reordering status report; a sending module 602, which is used to feedback a PDCP reordering status report to the PDCP sending end when the reordering timer times out, and the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

[0168] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0169] Optionally, the sending module 602 is specifically used to, when the reordering timer times out, cause the PDCP receiving end to set the first three bits of the protocol data unit PDU type in the control message to the second target value and to feed back a reordering status report to the sending end.

[0170] like Figure 7 As shown, it is a schematic diagram of an embodiment of a TCP sending end in an embodiment of the present application, which may include: a memory 701 storing executable program code; a processor 702 and a transceiver 703 coupled to the memory 701; the transceiver 703 is used to send a first data packet; the transceiver 703 is used to receive option information sent by the PDCP sending end, the option information is determined by the PDCP sending end according to the PDCP reordering status report sent by the PDCP receiving end, the PDCP reordering status report is fed back through a specific value indication, and the specific value is the value of adding a target identifier to the first data packet; the processor 702 is used to determine whether to perform congestion control based on the option information.

[0171] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0172] Optionally, the option information includes first option information, second option information, or third option information; the option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag; the option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag; the option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to the third flag; the processor 702 is specifically used to not perform congestion control according to the first option information; or, the processor 702 is specifically used to ignore the congestion judgment condition of the air interface according to the second option information, and perform congestion control according to an existing strategy; or, the processor 702 is specifically used to perform congestion control according to the third option information.

[0173] Optionally, the transceiver 703 is also used to receive a SACK sent by the PDCP transmitter, the SACK including information about data packets actually lost; the processor 702 is also used to compare the SACK and ACK, the ACK being confirmation information sent by the PDCP transmitter that the first data packet has been received; when the ACK includes information about data packets actually lost in the SACK, it is determined that it is air interface packet loss; the processor 702 is specifically used to, when it is determined that it is air interface packet loss, the TCP transmitter does not perform congestion control according to the first option information; or, the processor 702 is specifically used to, when it is determined that it is air interface packet loss, the TCP transmitter ignores the congestion judgment condition of the air interface according to the second option information and performs congestion control according to an existing strategy; or, the processor 702 is specifically used to, when it is determined that it is air interface packet loss, the TCP transmitter performs congestion control according to the third option information.

[0174] like Figure 8 As shown, it is a schematic diagram of an embodiment of the PDCP sending end in the embodiment of the present application, which may include: a memory 801 storing executable program code; a processor 802 and a transceiver 803 coupled to the memory 801; the transceiver 803 is used to receive a first data packet sent by the TCP sending end; the transceiver 803 is used to send a second data packet to the PDCP receiving end on multiple carriers, the second data packet is the first data packet carrying a target identifier, the value of the target identifier is a specific value, and the specific value is used to indicate that the PDCP receiving end feeds back a PDCP reordering status report; the transceiver 803 is also used to receive the PDCP reordering status report sent by the PDCP receiving end; the processor 802 is used to determine option information according to the PDCP reordering status report; the transceiver 803 is also used to send the option information to the TCP sending end, and the option information is used to indicate whether to perform congestion control.

[0175] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0176] Optionally, the processor 802 is specifically configured to parse the PDCP reordering status report to determine packet loss information; and determine option information based on the packet loss information.

[0177] Optionally, the processor 802 is specifically configured to determine, based on the packet loss information, that when the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are all greater than the first rate threshold and the current cache is less than the first cache threshold, determine first option information, wherein the option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag, wherein the second flag indicates that the current air interface state is non-congested, indicating that the TCP sender does not perform congestion control; or,

[0178] Processor 802 is specifically configured to determine, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if there is a carrier whose rate is less than the second rate threshold among the multiple carriers, or the current cache is greater than the second cache threshold, determine second option information, wherein the option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag, and the first flag indicates that the congestion judgment condition of the air interface is ignored;

[0179] The first rate threshold is greater than or equal to the second rate threshold, and the first cache threshold is less than or equal to the second cache threshold.

[0180] Optionally, the processor 802 is specifically used to determine, based on the packet loss information, that when the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are all greater than a first rate threshold, and the current cache is less than the first cache threshold, and the current cache can be cleared within a first preset time length, then determine the first option information; the processor 802 is specifically used to determine, based on the packet loss information, that when the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are less than a second rate threshold, or the current cache is greater than the second cache threshold, and the current cache cannot be cleared within a second preset time length, then determine the second option information; wherein the second preset time length is greater than or equal to the first preset time length.

[0181] Optionally, the processor 802 is also used to determine third option information when there is a carrier with a rate less than a second rate threshold in the multi-carrier rate and the current cache is greater than the second cache threshold, wherein the option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to a third flag, wherein the third flag indicates that the current air interface status is congested, and instructs the TCP sender to perform congestion control.

[0182] Optionally, the processor 802 is further used to calculate the actual lost data packet information based on the packet loss information and the header of the first data packet; the sending module 803 is further used to send SACK to the TCP sending end, and the SACK includes the actual lost data packet information.

[0183] like Fig. 9As shown, it is a schematic diagram of an embodiment of the PDCP receiving end in the embodiment of the present application, which may include: a memory 901 storing executable program code; a transceiver 902 coupled to the memory 901; the transceiver 902 is used for the PDCP receiving end to receive a second data packet sent by the PDCP sending end, and start a reordering timer, wherein the second data packet carries a target identifier, and the value of the target identifier is a specific value, and the specific value is used to indicate that the PDCP receiving end feeds back a PDCP reordering status report; the transceiver 902 is used to feed back a PDCP reordering status report to the PDCP sending end when the reordering timer times out, and the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

[0184] Optionally, the option information includes options, length and information; when the value of the option includes a first target value, the information is an air interface congestion indication identifier; the air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; the first identifier indicates that the congestion judgment condition of the air interface is ignored; the second identifier indicates that the current air interface status is non-congested, indicating that the TCP sender does not perform congestion control; the third identifier indicates that the current air interface status is congested, indicating that the TCP sender performs congestion control.

[0185] Optionally, the transceiver 902 is specifically used to, when the reordering timer times out, cause the PDCP receiving end to set the first three bits of the protocol data unit PDU type in the control message to the second target value, and to feed back a reordering status report to the sending end.

[0186] Optionally, the present application also provides a TCP sending end, which may include: Figure 4 The congestion control device shown.

[0187] Optionally, the present application also provides a PDCP transmitter, which may include: Figure 5 The congestion control device shown.

[0188] Optionally, the present application also provides a PDCP receiving end, which may include: Figure 6 The congestion control device shown.

[0189] Optionally, the present application also provides a data transmission system, including a TCP sender, a PDCP sender and a PDCP receiver, the TCP sender is connected to the PDCP sender, and the PDCP sender is connected to the PDCP receiver.

[0190] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0191] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0192] In the several embodiments provided in the present application, 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, such as 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 an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0193] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0194] In addition, each functional unit in each embodiment of the present application 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-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0195] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.

[0196] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A congestion control method, applied to a TCP sender, the TCP sender is connected to a PDCP sender, the PDCP sender is connected to a PDCP receiver, characterized in that: The method comprises: The TCP sending end sends a first data packet; The TCP sending end receives option information sent by the PDCP sending end, where the option information is determined by the PDCP sending end according to a PDCP reordering status report sent by the PDCP receiving end, where the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value of adding a target identifier to the first data packet; The TCP sending end determines whether to perform congestion control according to the option information.

2. The method according to claim 1, characterized in that The option information includes options, length and information; In a case where the value of the option includes the first target value, the information is an air interface congestion indication flag; The air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; The first flag indicates ignoring the congestion judgment condition of the air interface; The second flag indicates that the current air interface state is non-congested, indicating that the TCP sending end does not perform congestion control; The third flag indicates that the current air interface state is congested, and instructs the TCP sending end to perform congestion control.

3. The method according to claim 1, characterized in that The option information includes first option information, second option information, or third option information; The option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag; The option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag; The option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to a third flag; The TCP sending end determines whether to perform congestion control according to the option information, including: The TCP sending end does not perform congestion control according to the first option information; or, The TCP sending end ignores the congestion judgment condition of the air interface according to the second option information and performs congestion control according to the existing strategy; or, The TCP sending end performs congestion control according to the third option information.

4. The method according to claim 3, characterized in that The method further comprises: The TCP sending end receives the SACK sent by the PDCP sending end, where the SACK includes information about data packets actually lost; The TCP sending end compares the SACK and ACK, where the ACK is confirmation information sent by the PDCP sending end that the first data packet has been received; In a case where the ACK includes information about the data packet actually lost in the SACK, determining that it is air interface packet loss; The TCP sending end determines whether to perform congestion control according to the option information, including: When it is determined that the packet loss is caused by the air interface, the TCP sending end does not perform congestion control according to the first option information; or, When it is determined that the packet loss is caused by the air interface, the TCP sending end ignores the congestion judgment condition of the air interface according to the second option information and performs congestion control according to the existing strategy; or When it is determined that air interface packet loss occurs, the TCP sending end performs congestion control according to the third option information.

5. A congestion control method, applied to a PDCP transmitter, a TCP transmitter connected to the PDCP transmitter, and the PDCP transmitter connected to a PDCP receiver, characterized in that: The method comprises: The PDCP sending end receives a first data packet sent by the TCP sending end; The PDCP transmitting end sends a second data packet to the PDCP receiving end on multiple carriers, where the second data packet is the first data packet carrying a target identifier, where the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report; The PDCP transmitting end receives the PDCP reordering status report sent by the PDCP receiving end; The PDCP transmitting end determines option information according to the PDCP reordering status report; The PDCP sending end sends the option information to the TCP sending end, where the option information is used to indicate whether to perform congestion control.

6. The method according to claim 5, characterized in that The option information includes options, length and information; In a case where the value of the option includes the first target value, the information is an air interface congestion indication flag; The air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; The first flag indicates ignoring the congestion judgment condition of the air interface; The second flag indicates that the current air interface state is non-congested, indicating that the TCP sending end does not perform congestion control; The third flag indicates that the current air interface state is congested, and instructs the TCP sending end to perform congestion control.

7. The method according to claim 5, characterized in that The PDCP transmitting end determines option information according to the PDCP reordering status report, including: The PDCP transmitting end parses the PDCP reordering status report to determine packet loss information; The PDCP transmitting end determines option information according to the packet loss information.

8. The method according to any one of claims 5 to 7, characterized in that: The PDCP transmitting end determines option information according to the packet loss information, including: The PDCP sending end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are all greater than the first rate threshold and the current cache is less than the first cache threshold, then determining first option information, in which the option in the first option information is filled with the first target value, and the air interface congestion indication flag is set to the second flag, the second flag indicates that the current air interface state is non-congested, and instructs the TCP sending end not to perform congestion control; or, The PDCP transmitting end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if there is a carrier whose rate is less than the second rate threshold among the multiple carriers, or the current cache is greater than the second cache threshold, then determining second option information, wherein the option in the second option information is filled with the first target value, and the air interface congestion indication flag is set to the first flag, and the first flag indicates that the congestion judgment condition of the air interface is ignored; The first rate threshold is greater than or equal to the second rate threshold, and the first cache threshold is less than or equal to the second cache threshold.

9. The method according to claim 8, characterized in that The PDCP transmitting end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are greater than the first rate threshold and the current buffer is less than the first buffer threshold, determining first option information, including: The PDCP transmitting end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the rates of the multiple carriers are all greater than the first rate threshold, and the current cache is less than the first cache threshold, and the current cache can be cleared within a first preset time length, then determining the first option information; When the PDCP transmitting end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if there is a carrier whose rate is less than the second rate threshold among the multiple carrier rates, or the current cache is greater than the second cache threshold, determining the second option information, including: The PDCP transmitting end determines, according to the packet loss information, that the packet loss rate is greater than the packet loss threshold, if the multiple carrier rates are less than the second rate threshold, or the current cache is greater than the second cache threshold, and the current cache cannot be cleared within the second preset time length, then determining the second option information; The second preset duration is greater than or equal to the first preset duration.

10. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: When there is a carrier with a rate lower than the second rate threshold in the multi-carrier rate and the current cache is larger than the second cache threshold, the PDCP sender determines third option information, the option in the third option information is filled with the first target value, and the air interface congestion indication flag is set to the third flag, the third flag indicates that the current air interface status is congested, and instructs the TCP sender to perform congestion control.

11. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: The PDCP transmitting end calculates information of actually lost data packets according to the packet loss information and a header of the first data packet; The PDCP sending end sends a SACK to the TCP sending end, where the SACK includes information about the data packet actually lost.

12. A congestion control method, applied to a PDCP receiving end, a TCP sending end connected to the PDCP sending end, and the PDCP sending end connected to the PDCP receiving end, characterized in that: The method comprises: The PDCP receiving end receives a second data packet sent by the PDCP transmitting end, and starts a reordering timer, wherein the second data packet carries a target identifier, and a value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report; When the reordering timer times out, the PDCP receiving end feeds back a PDCP reordering status report to the PDCP transmitting end, where the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

13. The method according to claim 12, characterized in that The option information includes options, length and information; In a case where the value of the option includes the first target value, the information is an air interface congestion indication flag; The air interface congestion indication identifier includes a first identifier, a second identifier, and a third identifier; The first flag indicates ignoring the congestion judgment condition of the air interface; The second flag indicates that the current air interface state is non-congested, indicating that the TCP sending end does not perform congestion control; The third flag indicates that the current air interface state is congested, and instructs the TCP sending end to perform congestion control.

14. The method according to claim 12, characterized in that When the reordering timer times out, the PDCP receiving end feeds back a PDCP reordering status report to the PDCP transmitting end, including: When the reordering timer times out, the PDCP receiving end sets the first three bits of the protocol data unit PDU type in the control message to the second target value, and feeds back a reordering status report to the sending end.

15. A congestion control device, characterized in that: include: A sending module, used for sending a first data packet; a receiving module, configured to receive option information sent by a PDCP transmitting end, wherein the option information is determined by the PDCP transmitting end according to a PDCP reordering status report sent by a PDCP receiving end, wherein the PDCP reordering status report is fed back through a specific value indication, and the specific value is a value of adding a target identifier to the first data packet; The processing module is used to determine whether to perform congestion control according to the option information.

16. A congestion control device, characterized in that: include: A receiving module, used for receiving a first data packet sent by a TCP sending end; a sending module, configured to send a second data packet to a PDCP receiving end on multiple carriers, wherein the second data packet is a first data packet carrying a target identifier, wherein a value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report; The receiving module is further configured to receive the PDCP reordering status report sent by the PDCP receiving end; A processing module, configured to determine option information according to the PDCP reordering status report; The sending module is further used to send the option information to the TCP sending end, where the option information is used to indicate whether to perform congestion control.

17. A congestion control device, characterized in that: include: A receiving module, configured for a PDCP receiving end to receive a second data packet sent by a PDCP transmitting end, and start a reordering timer, wherein the second data packet carries a target identifier, and the value of the target identifier is a specific value, and the specific value is used to instruct the PDCP receiving end to feed back a PDCP reordering status report; The sending module is used to feed back a PDCP reordering status report to the PDCP sending end when the reordering timer times out, wherein the PDCP reordering status report is used to determine option information, and the option information is used to indicate whether to perform congestion control.

18. A computer-readable storage medium comprising computer program instructions, which, when executed on a processor, cause the processor to perform the method according to any one of claims 1 to 14.

Citation Information

Cited By

  • TCP mirror image data processing method and device, chip and medium

    CN120128594A

  • Data management and control method and apparatus, and device, storage medium and computer program product

    WO2026113255A1