Transmission control protocol (TCP) packet loss recovery techniques

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can detect a transmission control protocol (TCP) packet loss based at least in part on a packet data convergence protocol (PDCP) payload of a packet. The UE can transmit a plurality of retransmission requests for the packet based at least in part on the detection of the TCP packet loss for the packet. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 199,718, filed January 19, 2021, entitled “TECHNIQUES FOR TRANSMISSION CONTROL PROTOCOL (TCP) PACKET LOSS RECOVERY”, and U.S. Non-Provisional Patent Application No. 17 / 647,421, filed January 7, 2022, entitled “TECHNIQUES FOR TRANSMISSION CONTROL PROTOCOL (TCP) PACKET LOSS RECOVERY”, which are hereby expressly incorporated by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for Transmission Control Protocol (TCP) packet loss recovery. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies, which enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communication between a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, while "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0006] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards. Specific methods include: using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), using CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] In some aspects, a user equipment (UE) for wireless communication includes: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: detect Transmission Control Protocol (TCP) packet loss at least in part based on the Packet Data Convergence Protocol (PDCP) payload of the packet; and send multiple retransmission requests for the packet at least in part based on the detection of TCP packet loss of the packet.

[0008] In some aspects, a method of wireless communication performed by a UE includes: detecting TCP packet loss based at least in part on the PDCP payload of the packet; and sending multiple retransmission requests for the packet based at least in part on the detection of TCP packet loss of the packet.

[0009] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: detect TCP packet loss at least in part based on the PDCP payload of the packet; and send multiple retransmission requests for the packet at least in part based on the detection of TCP packet loss of the packet.

[0010] In some aspects, an apparatus for wireless communication includes: components for detecting TCP packet loss based at least in part on the PDCP payload of the packet; and components for sending a plurality of retransmission requests for the packet based at least in part on the detection of TCP packet loss of the packet.

[0011] In some aspects, a UE for wireless communication includes: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: detect TCP packet loss based at least in part on TCP sequences and in the absence of PDCP loss; and to send multiple retransmission requests for packets based at least in part on the detection of TCP packet loss of packets.

[0012] In some aspects, a method of wireless communication performed by a UE includes: detecting TCP packet loss based at least in part on TCP sequences and in the absence of PDCP loss; and sending multiple retransmission requests for packets based at least in part on the detection of TCP packet loss of packets.

[0013] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: detect TCP packet loss based at least in part on a TCP sequence and in the absence of PDCP loss; and send multiple retransmission requests for packets based at least in part on the detection of TCP packet loss of the packets.

[0014] In some aspects, an apparatus for wireless communication includes: components for detecting TCP packet loss based at least in part on TCP sequences and in the absence of PDCP loss; and components for sending multiple retransmission requests for packets based at least in part on the detection of TCP packet loss of the packets.

[0015] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems as substantially described herein with reference to the accompanying drawings and description.

[0016] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limitation of the claims. Attached Figure Description

[0017] To gain a more detailed understanding of the features described above, reference can be made to various aspects for a more specific description of the content briefly outlined above, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of the disclosure and should therefore not be considered as limiting its scope, as the description may allow for other equivalent aspects. The same reference numerals in different drawings can identify the same or similar elements.

[0018] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0019] Figure 2 This is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to this disclosure.

[0020] Figure 3 This is a diagram illustrating an example of the user plane protocol stack and control plane protocol stack of the BS and core network for communicating with the UE according to this disclosure.

[0021] Figure 4 This is a diagram illustrating an example of a radio access network according to this disclosure.

[0022] Figure 5 This is a diagram illustrating an example of an IAB network architecture according to this disclosure.

[0023] Figure 6 This is a diagram illustrating an example of a Transmission Control Protocol (TCP) data stream that results in packet loss according to this disclosure.

[0024] Figure 7 This is a diagram illustrating an example of TCP packet loss recovery according to this disclosure.

[0025] Figures 8 to 9 This is a diagram illustrating an exemplary process associated with TCP packet loss recovery according to this disclosure.

[0026] Figures 10 to 11 This is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. Detailed Implementation

[0027] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully communicate the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of the disclosure herein, whether implemented independently of any other aspect of this disclosure or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method that is practiced using a structure, function, or structure and function other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0028] Several aspects of a telecommunications system will now be presented with reference to various devices and technologies. These devices and technologies will be described in detail below and illustrated in the accompanying drawings through various frames, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0029] Although terms commonly associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used in this document to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0030] Figure 1This diagram illustrates an example of a wireless network 100 according to this disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Base station 110 is the entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a Transmit / Receive Point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​base station 110 and / or the base station subsystem serving that coverage area, depending on the context in which the term is used.

[0031] Base station 110 can provide communication coverage for macro cells, pico cells, femtocells, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow UE 120 unrestricted access via a service subscription. A pico cell can cover a relatively small geographic area and can allow UE 120 unrestricted access via a service subscription. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access for UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Base station 110 for macro cells can be referred to as a macro base station. Base station 110 for pico cells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femtocell or an in-home base station. Figure 1 In the example shown, BS110a can be a macro base station for macro cell 102a, BS110b can be a pico base station for pico cell 102b, and BS110c can be a femto base station for femto cell 102c. A base station can support one or more (e.g., three) cells.

[0032] In some examples, the cell may not be fixed, and the geographical area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, base station 110 may interconnect with each other and / or interconnect to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0033] Wireless network 100 may include one or more relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., base station 110 or UE 120) and transmit data transmissions to a downstream station (e.g., UE 120 or base station 110). A relay station may be a UE 120 that can relay transmissions for other UE 120s. Figure 1 In the example shown, BS110d (e.g., a relay base station) can communicate with BS110a (e.g., a macro base station) and UE 120d to facilitate communication between BS110a and UE 120d. The base station 110 used for relay communication can be referred to as a relay station, relay base station, repeater, etc.

[0034] Wireless network 100 can be a heterogeneous network comprising different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 can have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro base stations can have high transmit power levels (e.g., 5 watts to 40 watts), while pico base stations, femto base stations, and relay base stations can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0035] Network controller 130 can be coupled to or communicate with a group of base stations 110, and can provide coordination and control for these base stations 110. Network controller 130 can communicate with base stations 110 via backhaul communication links. Base stations 110 can communicate with each other directly or indirectly via wireless or wired backhaul communication links.

[0036] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be fixed or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, and / or any other suitable device configured to communicate via wireless or wired media.

[0037] Some UEs 120 can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 can be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 can be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] Typically, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, air interface, etc. A frequency can be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as a medium for communication with each other). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0040] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often referred to (interchangeably) as the “below 6GHz” band in various documents and articles. Similar naming issues sometimes arise with FR2, although it differs from the Extremely High Frequency (EHF) band (30GHz–300GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU), it is often referred to (interchangeably) as the “millimeter wave” band in documents and articles.

[0041] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) frequencies. Recent 5G NR research has identified the operating bands of these IF frequencies as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to IF frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF (Extremely High Frequency) band.

[0042] Considering the examples above, unless otherwise specified, it should be understood that the use of terms such as "below 6 GHz" herein can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include intermediate frequency bands. Furthermore, unless otherwise specified, it should be understood that the use of terms such as "millimeter wave" herein can broadly refer to frequencies that may include intermediate frequency bands, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF (Extremely High Frequency) band. It is conceivable that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, UE 120 may include communication manager 140. As described in more detail elsewhere herein, communication manager 140 may detect Transmission Control Protocol (TCP) packet loss at least in part based on the Packet Data Convergence Protocol (PDCP) payload of the packet; and send multiple retransmission requests for the packet at least in part based on the detection of TCP packet loss. In some aspects, communication manager 140 may detect TCP packet loss at least in part based on the TCP sequence and in the absence of PDCP loss; and send multiple retransmission requests for the packet at least in part based on the detection of TCP packet loss. Alternatively or additionally, communication manager 140 may perform one or more other operations described herein. In some aspects, base station 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may receive retransmission requests from UE 120 and may retransmit one or more lost packets at least in part based on the receipt of retransmission requests. Alternatively or additionally, communication manager 150 may perform one or more other operations described herein.

[0044] As mentioned above, Figure 1 This is provided as an example. Other examples may differ from those provided. Figure 1 The content described.

[0045] Figure 2 This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0046] At base station 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) the data of UE 120, at least in part, based on the MCS selected for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., for Semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., Cell-Specific Reference Signal (CRS) or Demodulation Reference Signal (DMRS)) and synchronization signals (e.g., Primary Synchronization Signal (PSS) or Secondary Synchronization Signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0047] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 and / or other base stations 110, and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols if applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) detected symbols, provide decoded data of the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0048] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0049] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, a group or more groups of antenna elements, and / or one or more antenna arrays. Antenna panels, antenna groups, a group of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

[0050] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., references). Figures 7 to 11 ).

[0051] At base station 110, uplink signals from UE 120 and / or other UEs can be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of base station 110 may include modulator and demodulator. In some examples, base station 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., references). Figures 7 to 11 ).

[0052] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other components may perform one or more techniques associated with Transmission Control Protocol (TCP) packet loss recovery, as described in more detail elsewhere in this document. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 8 The process 800 Figure 9 The operation of process 900 and / or other processes described herein. Memory 242 and memory 282 may store data and program code of base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 8 The process 800 Figure 9 The operation of process 900 and / or other processes described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0053] In some aspects, UE 120 includes: components for detecting TCP packet loss based at least in part on the Packet Data Convergence Protocol (PDCP) payload of the packet; and / or components for sending multiple retransmission requests for the packet based at least in part on the detection of TCP packet loss of the packet. In some aspects, UE 120 includes: components for detecting TCP packet loss based at least in part on the TCP sequence and in the absence of PDCP loss; and components for sending multiple retransmission requests for the packet based at least in part on the detection of TCP packet loss of the packet. In some aspects, UE 120 includes components for sending a set of duplicate acknowledgments based at least in part on the detection of TCP packet loss of the packet. In some aspects, UE 120 includes components for detecting TCP packet loss based at least in part on the size or content of the PDCP payload. In some aspects, UE 120 includes components for detecting TCP packet loss based at least in part on the inspection of the PDCP payload header. In some aspects, UE 120 includes components for detecting TCP packet loss based at least in part on the packet being invalid. In some aspects, UE 120 includes components for detecting TCP packet loss based at least in part on packets having zero or spurious payloads. In some aspects, UE 120 includes components for detecting TCP packet loss based at least in part on the expiration of a PDCP timer of UE 120. In some aspects, UE 120 includes components for detecting Radio Link Control (RLC) level packet loss. Components for enabling UE 120 to perform the operations described herein may include, for example, one or more of antenna 252, demodulator, MIMO detector 256, receive processor 258, transmit processor 264, TXMIMO processor 266, modulator controller / processor 280, or memory 282.

[0054] although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to the boxes can be implemented as a single hardware, software, or combined component, or as various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be performed by or under the control of the controller / processor 280.

[0055] As mentioned above, Figure 2 This is provided as an example. Other examples may differ from those provided. Figure 2 The content described.

[0056] Figure 3This is a diagram illustrating an example 300 of a base station 110 and a core network user plane protocol stack and a control plane protocol stack for communicating with a UE 120, according to the present disclosure.

[0057] On the user plane, UE 120 and base station 110 may include corresponding Physical (PHY) layers, Medium Access Control (MAC) layers, Radio Link Control (RLC) layers, Packet Data Convergence Protocol (PDCP) layers, and Service Data Adaptation Protocol (SDAP) layers. User plane functions handle user data transmission between UE 120 and base station 110. On the control plane, UE 120 and base station 110 may include corresponding Radio Resource Control (RRC) layers. Furthermore, UE 120 may include a Non-Access Stratum (NAS) layer that communicates with the NAS layer of Access and Management Mobility Functions (AMF). AMF may be associated with the core network (such as a 5G core network (5GC) or Next Generation Radio Access Network (NG-RAN)) associated with base station 110. Control plane functions handle control information transmission between the UE and the core network. Generally, if a first layer is further from the PHY layer than a second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layers may be referred to as being higher than the PHY layer and lower than the RRC layer. Figure 3 The application (APP) layer, not shown, can be higher than the SDAP / PDCP / RLC / MAC layers. In some cases, an entity can handle the services and functions of a given layer (e.g., a PDCP entity can handle the services or functions of the PDCP layer), although the description herein mentions that the layer itself handles the services or functions.

[0058] The RRC layer handles communications related to configuring and operating UE 120, such as: broadcasting system information related to the Access Layer (AS) and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual connections; security functions, including key management; establishment, configuration, maintenance, and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (e.g., handover and context transfer, UE cell selection and reselection, and control of cell selection and reselection, inter-RAT mobility); Quality of Service (QoS) management functions; control of UE measurement reports and notifications; detection and recovery of radio link failures; and NAS message delivery between the UE 120's NAS layer and lower layers. The RRC layer is often referred to as Layer 3 (L3).

[0059] The SDAP, PDCP, RLC, and MAC layers can be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if UE 120 is transmitting uplink communication or base station 110 is transmitting downlink communication), the SDAP layer can receive data streams in the form of QoS streams. A QoS stream is associated with a QoS identifier (which identifies the QoS parameters associated with the QoS stream) and a QoS stream identifier (QFI) (which identifies the QoS stream). Policy and charging parameters are enforced at the QoS stream granularity. A QoS stream can include one or more Service Data Streams (SDFs), provided that each SDF of the QoS stream is associated with the same policy and charging parameters. In some aspects, the RRC / NAS layer can generate control information to be transmitted and can map the control information to one or more radio bearers for provision to the PDCP layer.

[0060] The SDAP or RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles the QoS flows on the transmitting side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearer. The PDCP layer can map radio bearers to RLC channels. The PDCP layer can handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), user data transmission, reordering and deduplication (if sequential delivery to layers above the PDCP layer is required), PDCP Protocol Data Unit (PDU) routing (in the case of separate bearers), retransmission, encryption and decryption of PDCP Service Data Units (SDUs), PDCP SDU dropping (e.g., according to timers, as described elsewhere in this document), PDCP reconstruction and data recovery in RLC Acknowledgment Mode (AM), and PDCP PDU duplication. The PDCP layer can handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, control plane data transmission, deduplication, and PDCP PDU duplication.

[0061] The PDCP layer can provide data to the RLC layer in the form of PDCP PDUs via the RLC channel. The RLC layer can handle the transmission of upper-layer PDUs to the MAC and / or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and resegmentation, SDU reassembly, RLC SDU discarding, and RLC reconstruction.

[0062] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include: mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing MACSDUs belonging to one or different logical channels into / from a transport block (TB) delivered to / from the physical layer on the transport channel, demultiplexing, scheduling information reporting, error correction via Hybrid ARQ (HARQ), prioritization among UEs via dynamic scheduling, prioritization among logical channels of a UE via logical channel priority allocation, and padding.

[0063] The MAC layer can encapsulate data from logical channels into data blocks (TBs) and can provide the TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to data signal transmission, such as... Figure 2 In more detail, the PHY layer is often referred to as Layer 1 (L1).

[0064] On the receiving side (e.g., if UE 120 is receiving downlink communication or base station 110 is receiving uplink communication), the operation can be similar to, but reversed, the operation described for the transmitting side. For example, the PHY layer can receive the transport channel (TB) and can provide the TB to the MAC layer on one or more transport channels. The MAC layer can map the transport channels to logical channels and can provide data to the RLC layer via the logical channels. The RLC layer can map the logical channels to RLC channels and can provide data to the PDCP layer via the RLC channels. The PDCP layer can map the RLC channels to radio bearers and can provide data to the SDAP layer or RRC / NAS layer via the radio bearers.

[0065] Data can be transferred between layers in the form of PDUs and SDUs. An SDU is a data unit passed from a layer or sublayer to a lower layer. For example, the PDCP layer can receive PDCP SDUs. A given layer can then encapsulate the data unit into a PDU and pass the PDU to a lower layer. For example, the PDCP layer can encapsulate a PDCP SDU into a PDCP PDU and pass that PDCP PDU to the RLC layer. The RLC layer can receive a PDCP PDU as an RLC SDU, encapsulate the RLC SDU into an RLCPDU, and so on. In effect, the PDU carries the SDU as a payload.

[0066] As mentioned above, Figure 3 This is provided as an example. Other examples may differ from those provided. Figure 3 The content described.

[0067] Figure 4This is a diagram illustrating an example 400 of a radio access network according to this disclosure.

[0068] As shown by reference numeral 405 in the attached figures, a conventional (e.g., 3G, 4G, or LTE) radio access network may include multiple base stations 410 (e.g., access nodes (ANs)), each base station 410 communicating with the core network via a wired backhaul link 415 (such as a fiber optic connection). Base stations 410 may communicate with a UE 420 via an access link 425, which may be a radio link. In some aspects, Figure 4 The base station 410 shown can be Figure 1 The base station 110 is shown. In some respects, Figure 4 The UE 420 shown can be Figure 1 The UE 120 shown.

[0069] As indicated by reference numeral 430 in the attached figure, the radio access network may include a wireless backhaul network, sometimes referred to as an Integrated Access and Backhaul (IAB) network. In an IAB network, at least one base station is an anchor base station 435 that communicates with the core network via a wired backhaul link 440 (such as a fiber optic connection). The anchor base station 435 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 445, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). Non-anchor base stations 445 may communicate directly or indirectly with anchor base station 435 via one or more backhaul links 450 (e.g., via one or more non-anchor base stations 445) to form a backhaul path to the core network for carrying backhaul services. The backhaul link 450 may be a radio link. Anchor base station 435 and / or non-anchor base station 445 may communicate with one or more UEs 455 via an access link 460, which may be a radio link for carrying access services. In some aspects, Figure 4 The anchor base station 435 and / or non-anchor base station 445 shown can be Figure 1 The base station 110 is shown. In some respects, Figure 4 The UE455 shown can be Figure 1 The UE 120 shown.

[0070] As indicated by reference numeral 465 in the accompanying drawings, in some aspects, radio access networks, including IAB networks, can utilize millimeter-wave technology and / or directional communication (e.g., beamforming) to communicate between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, a radio backhaul link 470 between base stations can use millimeter-wave signals to carry information and / or can be beamformed to a target base station. Similarly, a radio access link 475 between a UE and a base station can use millimeter-wave signals and / or can be beamformed to a target radio node (e.g., the UE and / or the base station). This reduces inter-link interference.

[0071] Figure 4 The configuration of the base station and UE is shown as an example, and other examples are also considered. For example, Figure 4 The one or more base stations shown can be replaced by one or more UEs communicating via a UE-to-UE access network (e.g., a peer-to-peer network or a device-to-device network). In this context, "anchor node" can refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0072] As mentioned above, Figure 4 This is provided as an example. Other examples may differ from those provided. Figure 4 The content described.

[0073] Figure 5 This is a diagram illustrating an example 500 of the IAB network architecture according to this disclosure.

[0074] like Figure 5 As shown, the IAB network may include an IAB donor 505 (shown as an IAB-donor) connected to the core network via a wired connection (shown as a wired backhaul). For example, the Ng interface of the IAB donor 505 may terminate in the core network. Alternatively or additionally, the IAB donor 505 may connect to one or more devices in the core network that provide core access and mobility management functions (e.g., AMF). In some aspects, the IAB donor 505 may include a base station 110, such as an anchor base station, as described above. Figure 4As described, as shown in the figure, the IAB donor 505 may include a central unit (CU) that can perform Access Node Controller (ANC) functions and / or AMF functions. The CU may configure the distributed units (DUs) of the IAB donor 505 and / or may configure one or more IAB nodes 510 (e.g., the MTs and / or DUs of IAB nodes 510) connected to the core network via the IAB donor 505. Therefore, the CU of the IAB donor 505 can control and / or configure the entire IAB network connected to the core network via the IAB donor 505, for example, by using control messages and / or configuration messages (e.g., Radio Resource Control (RRC) configuration messages or F1 Application Protocol (F1AP) messages).

[0075] like Figure 5 As further illustrated, the IAB network may include IAB nodes 510 (shown as IAB node 1, IAB node 2, and IAB node 3) connected to the core network via IAB donor 505. As shown, IAB node 510 may include Mobile Terminal (MT) functions (sometimes also referred to as UE functions (UEF)) and may include DU functions (sometimes also referred to as Access Node Functions (ANF)). The MT function of IAB node 510 (e.g., a child node) may be controlled and / or scheduled by another IAB node 510 (e.g., the parent node of the child node) and / or by IAB donor 505. The DU function of IAB node 510 (e.g., the parent node) may control and / or schedule other IAB nodes 510 (e.g., child nodes of the parent node) and / or UE 120. Therefore, DU may be referred to as a scheduling node or scheduling component, and MT may be referred to as a scheduled node or scheduled component. In some aspects, IAB donor 505 may include DU functions but not MT functions. In other words, the IAB donor 505 can configure, control, and / or schedule the communication of the IAB node 510 and / or the UE 120. The UE 120 may include only the MT function and not the DU function. That is, the communication of the UE 120 can be controlled and / or scheduled by the IAB donor 505 and / or the IAB node 510 (e.g., the parent node of the UE 120).

[0076] When the first node controls and / or schedules the communication of the second node (e.g., when the first node provides the DU function for the MT function of the second node), the first node can be referred to as the parent node of the second node, and the second node can be referred to as the child node of the first node. The child node of the second node can be referred to as the grandchild node of the first node. Therefore, the DU function of the parent node can control and / or schedule the communication of the parent node's child node. The parent node can be IAB donor 505 or IAB node 510, and the child node can be IAB node 510 or UE 120. The communication of the MT function of the child node can be controlled and / or scheduled by the child node's parent node.

[0077] like Figure 5 As further illustrated, the link between UE 120 (e.g., having only MT functionality and not DU functionality) and IAB donor 505, or the link between UE 120 and IAB node 510, can be referred to as access link 515. Access link 515 can be a radio access link that provides radio access to the core network to UE 120 via IAB donor 505 and optionally via one or more IAB nodes 510. Therefore, the network shown in 5 can be referred to as a multi-hop network or a wireless multi-hop network.

[0078] like Figure 5 As further illustrated, the link between IAB donor 505 and IAB node 510, or between two IAB nodes 510, can be referred to as backhaul link 520. Backhaul link 520 can be a wireless backhaul link that provides radio access to the core network to IAB node 510 via IAB donor 505 and optionally via one or more other IAB nodes 510. In the IAB network, network resources for wireless communication (e.g., time resources, frequency resources, and / or spatial resources) can be shared between access link 515 and backhaul link 520. In some aspects, backhaul link 520 can be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link can be used if the primary backhaul link fails, becomes congested, and / or becomes overloaded. For example, if the primary backhaul link between IAB node 2 and IAB node 1 fails, a backup link between IAB node 2 and IAB node 3 can be used for backhaul communication. As used in this article, "node" or "wireless node" may refer to IAB donor 505 or IAB node 510.

[0079] As mentioned above, Figure 5 This is provided as an example. Other examples may differ from those provided. Figure 5 The content described.

[0080] Figure 6This is a diagram illustrating an example 600 of a TCP data stream according to this disclosure, where packet loss on the downlink occurs due to a timer being discarded at the base station. Figure 6 As shown, different protocol layers exist in the UE (left), base station (middle), and one or more core network devices (right).

[0081] like Figure 6 As further illustrated, the data server can provide a set of M packets to the gateway (GW) via the S1U interface. The gateway can then route these M packets as a set of N packets to the base station and the UE via the NG-U interface. The base station can receive the packets at the Packet Data Convergence Protocol (PDCP) downlink (DL) entity of the CU and route them as a set of P packets to the base station's DU (and associated Radio Link Control (RLC) and Media Access Control (MAC) / Layer 1 (L1) entities) via the NR-U interface. The base station can transmit data to the UE via the over-the-air (OTA) interface, and the UE can pass the transmitted packets up the protocol stack from the UE's MAC / L1 entity, RLC entity, and PDCP entity to the UE's TCP entity / higher-level operating system (HLOS). Each of the above data transmissions can be associated with a buffer. For example, there can be a first buffer for the S1-U interface, a second buffer for the NG-U interface, a third buffer for the NR-U interface, or a fourth buffer for the OTA interface, etc.

[0082] Due to changes in load conditions on the OTA interface, some data available in the base station's buffer may not be transmitted within the configured time (e.g., before the timer associated with the data expires). This situation can be referred to as timer discard (T_discard) because it can occur when a timer expires and a packet intended for transmission is discarded due to failure to meet latency requirements (e.g., Real-time Transport Protocol (RTP) or TCP latency requirements). When packets are lost at the base station and access stratum (AS) levels, the UE may not receive explicit notification of packet loss. For example, the base station may send a set of PDCP packets to the UE with ordered PDCP sequence numbers (SNs) and RLC SNs. Because the PDCP packets are ordered relative to the PDCP SN and RLC SN ("clean"), no reordering occurs at the UE, and the UE's PDCP entity detects that the packets have been correctly received. However, because the base station's PDCP entity discards the packets in the base station's buffer, the PDCP packets may have empty payloads. In other words, the UE receives a MAC Service Data Unit (SDU) with 10 bytes, which includes a 3-byte PDCP header, a 3-byte RLC header, a 2-byte MAC header (if the SDU is less than 255 octets, otherwise a 3-byte MAC header), and a 2-byte pseudo payload (e.g., padding bits) or zero payload (e.g., zero bits).

[0083] At the UE's TCP entity, the UE can detect that a packet has been lost, and the UE can send a TCP Duplicate Uptake (DUP) Acknowledgment (ACK) to the base station for each packet. After a threshold number of DUP ACKs, retransmission of the dropped packet is triggered. For example, depending on the configuration, retransmission may occur after a number ranging from 3 to 17 DUP ACKs. The interval between DUP ACK transmissions may be greater than the threshold, which may result in poor network performance for the UE.

[0084] As mentioned above, Figure 6 This is provided as an example. Other examples may differ from those provided. Figure 6 The content described.

[0085] Several aspects described in this article enable TCP packet loss recovery. For example, the UE can detect that the PDCP payload is a zero payload, an invalid payload, or a spurious payload, and can determine that TCP packet loss has occurred at the base station (e.g., the base station has dropped the TCP packet at the buffer of the PDCP entity at the base station). In this case, the UE can repeat the transmission of DUP ACK to trigger fast retransmission of the lost packet. For example, the UE can manually generate multiple DUP ACKs for a single detected packet loss, thereby immediately triggering a retransmission, rather than waiting to generate a threshold amount of DUP ACKs based at least in part on a threshold amount of detected packet loss. In this way, the UE improves the detection of packet loss and reduces the amount of time spent retransmitting lost packets, thereby improving the UE's network performance.

[0086] Figure 7 This is a diagram illustrating example 700 associated with TCP packet loss recovery according to this disclosure. Figure 7 As shown, Example 700 includes communication between base station 110, UE 120, and one or more core network devices 710. In some aspects, base station 110 and UE 120 may be included in a wireless network, such as wireless network 100. Base station 110 and UE 120 may communicate via a radio access link, which may include an uplink and a downlink.

[0087] like Figure 7 As shown by reference numeral 720 in the accompanying drawings, UE 120 can detect TCP packet loss. For example, UE 120 can detect TCP packet loss at least in part based on the PDCP payload of the packet. In this case, UE 120 can detect TCP packet loss at least in part based on the detection of PDCP loss, as described herein. Alternatively or additionally, UE 120 can detect TCP packet loss at least in part based on the TCP sequence. In this case, UE 120 can detect TCP packet loss even without PDCP loss, as described herein.

[0088] In some respects, UE 120 can detect TCP packet loss by analyzing the contents of the payload header. For example, after PDCP decryption, UE 120 can parse the packet payload to determine where to send the packet up the protocol stack. In this case, UE 120 can use an IP packet processing entity (e.g., an IP Accelerator (IPA) entity) to parse the payload, which can be a hardware component (IPAHW) or a software component (IPA SW). Based at least in part on the parsing of the payload, UE 120 can determine that the packet includes a spurious payload or other invalid type of payload added at the PDCP entity of base station 110. Alternatively or additionally, UE can detect another type of packet loss, such as RLC packet loss. Alternatively or additionally, UE can detect packet loss based at least in part on the expiration of the PDCP timer at UE. In some respects, UE can detect packet loss without PDCP loss occurring. For example, UE can detect an out-of-order TCP sequence indicating packet loss.

[0089] like Figure 7 Furthermore, as shown by reference numeral 730, UE 120 can send a retransmission request. For example, based at least in part on the detection of TCP packet loss, UE 120 can send a retransmission request to trigger packet retransmission (e.g., at the modem level of UE 120). In this case, UE 120 can send a set of consecutive TCP DUP ACKs to trigger packet retransmission much faster than UE 120 would wait to trigger retransmission at its TCP entity. In some aspects, UE 120 can generate and send a set of duplicates of DUP ACK packets (e.g., duplicates of a threshold number K) at the modem located at the header of the PDCP entity in UE 120's protocol stack. Alternatively or additionally, UE 120 can generate and send this set of duplicates of DUP ACK packets at UE 120's IPA HW or IPA SW entity. In some aspects, UE 120 can generate and send this set of duplicates at the UE 120's higher-level operating system (HLOS) driver level. Alternatively, UE 120 may generate and send this set of duplicates at its TCP entity (but reduce the amount of time required to trigger retransmissions before other TCP retransmission criteria are met). In this way, UE 120 reduces the amount of time spent retransmitting data dropped at the PDCP entity of base station 110, thereby improving network and device performance.

[0090] As mentioned above, Figure 7 This is provided as an example. Other examples may differ from those provided. Figure 7 The content described.

[0091] Figure 8 This is a diagram illustrating an exemplary process 800 performed, for example, by a UE according to this disclosure. Exemplary process 800 is an example of an operation performed by a UE (e.g., UE 120) in connection with a technique for TCP packet loss recovery.

[0092] like Figure 8 As shown, in some aspects, process 800 may include detecting TCP packet loss at least in part based on the PDCP payload of the packet (box 810). For example, the UE (e.g., using...) Figure 10 The detection component 1008 shown can detect TCP packet loss at least in part based on the PDCP payload of the packet, as described above.

[0093] like Figure 8 As further shown, in some aspects, process 800 may include sending multiple retransmission requests for packets based at least in part on the detection of TCP packet loss (box 820). For example, the UE (e.g., using...) Figure 10 The sending component 1004 shown can send multiple retransmission requests for packets based at least in part on the detection of TCP packet loss, as described above.

[0094] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0095] In the first aspect, sending multiple retransmission requests includes sending a set of duplicate acknowledgments based at least in part on the detection of TCP packet loss of the packet.

[0096] In the second aspect, either alone or in combination with the first aspect, the group is repeatedly transmitted by the modem associated with the UE's PDCP entity.

[0097] In the third aspect, either alone or in combination with one or more of the first and second aspects, the group is repeatedly transmitted by the hardware or software components of the IP packet processing entity.

[0098] In the fourth aspect, the group is repeatedly sent by the higher operating system entity, either alone or in combination with one or more of the first to third aspects.

[0099] In the fifth aspect, this group of repetitions is sent by the TCP entity, either alone or in combination with one or more of the first through fourth aspects.

[0100] In the sixth aspect, detecting TCP packet loss, either alone or in combination with one or more of the first to fifth aspects, includes detecting TCP packet loss based at least in part on the size of the PDCP payload or the content of the PDCP payload.

[0101] In the sixth aspect, detecting TCP packet loss, either alone or in combination with one or more of the first to fifth aspects, includes detecting TCP packet loss based at least in part on the size of the PDCP payload or the content of the PDCP payload.

[0102] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the inspection of the PDCP payload header is performed using hardware or software components of the IP packet processing entity.

[0103] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the detection of TCP packet loss includes: detecting TCP packet loss based at least in part on the fact that the packet is invalid.

[0104] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the detection of TCP packet loss includes: detecting TCP packet loss based at least in part on packets having zero payload or spurious payload.

[0105] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the detection of TCP packet loss includes: detecting TCP packet loss based at least in part on the expiration of the UE's PDCP timer.

[0106] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the detection of TCP packet loss includes: detecting RLC-level packet loss.

[0107] although Figure 8 An exemplary box of process 800 is shown, but in some aspects, process 800 may include additional boxes, fewer boxes, different boxes, or boxes similar to those shown. Figure 8 The different arrangements of the boxes depicted. Alternatively or concurrently, two or more boxes of process 800 may be executed in parallel.

[0108] Figure 9 This is a diagram illustrating an exemplary process 900 performed, for example, by a UE according to this disclosure. Exemplary process 900 is an example of a UE (e.g., UE 120) performing operations associated with TCP packet loss recovery.

[0109] like Figure 9As shown, in some aspects, process 900 may include at least partially based on TCP sequences and detecting TCP packet loss in the absence of PDCP loss (box 910). For example, the UE (e.g., using...) Figure 10 The communication manager 140 and / or detection component 1008 shown can be based at least in part on TCP sequences and detect TCP packet loss in the absence of PDCP loss, as described above.

[0110] like Figure 9 As further shown, in some aspects, process 900 may include sending multiple retransmission requests for packets based at least in part on the detection of TCP packet loss (box 920). For example, the UE (e.g., using...) Figure 10 The communication manager 140 and / or the sending component 1004 shown may send multiple retransmission requests for packets based at least in part on the detection of TCP packet loss, as described above.

[0111] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0112] In the first aspect, process 900 includes sending a set of duplicate acknowledgments based at least in part on the detection of TCP packet loss of packets.

[0113] In the second aspect, either alone or in combination with the first aspect, the group is repeatedly transmitted by the modem associated with the UE's PDCP entity.

[0114] In the third aspect, alone or in combination with one or more of the first and second aspects, the group is repeatedly transmitted by the hardware or software components of the Internet Protocol (IP) packet processing entity.

[0115] In the fourth aspect, the group is repeatedly sent by the higher operating system entity, either alone or in combination with one or more of the first to third aspects.

[0116] In the fifth aspect, this group of repetitions is sent by the TCP entity, either alone or in combination with one or more of the first through fourth aspects.

[0117] although Figure 9 An exemplary box of process 900 is shown, but in some aspects, process 900 may include additional boxes, fewer boxes, different boxes, or boxes similar to those shown. Figure 9 The different arrangements of the boxes depicted. Alternatively or concurrently, two or more boxes of process 900 may be executed in parallel.

[0118] Figure 10This is a block diagram of an exemplary device 1000 for wireless communication. Device 1000 may be a UE, or a UE may include device 1000. In some aspects, device 1000 includes a receiving component 1002 and a transmitting component 1004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1000 can use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, a base station, or another wireless communication device). As further shown, device 1000 may include a detection component 1008, etc.

[0119] In some aspects, the device 1000 may be configured to perform one or more operations as described herein. Additionally or alternatively, the device 1000 may be configured to perform one or more processes as described herein, such as... Figure 8 process 800 or Figure 9 The process 900, etc. In some aspects, the device 1000 includes a receiving component 1002 and a transmitting component 1004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). Additionally or alternatively, Figure 10 One or more components shown can be combined on top. Figure 2 Implemented within one or more of the described components. Alternatively or additionally, one or more of the components in the group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0120] Receiver 1002 may receive communications from device 1006, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 1006. In some aspects, receiver 1002 may include the above-described combinations. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0121] Transmitting component 1004 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1006. In some aspects, one or more other components of device 1006 can generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1006. In some aspects, transmitting component 1004 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and transmit the processed signals to device 1006. In some aspects, transmitting component 1004 may include the above-described combinations... Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1004 may be located in the same location within the transceiver as the receive component 1002.

[0122] The detection component 1008 can detect TCP packet loss based at least in part on the PDCP payload of the packet. The sending component 1004 can send multiple retransmission requests for the packet based at least in part on the detection of TCP packet loss.

[0123] Figure 10 The number and arrangement of components shown are provided as an example. In practice, additional components, fewer components, different components, or components may be present. Figure 10 The components are arranged in different ways as shown. Furthermore, it is possible to implement this within a single component. Figure 10 The two or more components shown, or Figure 10 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 10 The set (one or more) components shown can perform actions described by Figure 10 The other set of components shown performs one or more functions.

[0124] Figure 11 This is a block diagram of an exemplary device 1100 for wireless communication. Device 1100 may be a BS, or a BS may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, device 1100 may include a retransmission component 1108, etc.

[0125] In some aspects, device 1100 may be configured to perform one or more operations described herein. Additionally or alternatively, device 1100 may be configured to perform one or more processes described herein. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include the above-described combination. Figure 2 One or more components of the described BS. Alternatively or optionally, Figure 11 One or more components shown can be combined on top. Figure 2 Implemented within one or more of the described components. Alternatively or additionally, one or more of the components in the group may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0126] Receiver 1102 may receive communications from device 1106, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 1106. In some aspects, receiver 1102 may include the above-described combinations. Figure 2 The described BS includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memories, or combinations thereof.

[0127] Transmitting component 1104 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1106. In some aspects, one or more other components of device 1106 can generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1106. In some aspects, transmitting component 1104 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and transmit the processed signal to device 1106. In some aspects, transmitting component 1104 may include the above-described combinations... Figure 2 The described BS includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1104 may be located in the same location within the transceiver as the receive component 1102.

[0128] The retransmission component 1108 can trigger the retransmission of discarded data based at least in part on receiving a set of retransmission requests.

[0129] Figure 11 The number and arrangement of components shown are provided as an example. In practice, additional components, fewer components, different components, or components may be present. Figure 11 The components are arranged in different ways as shown. Furthermore, it is possible to implement this within a single component. Figure 11 The two or more components shown, or Figure 11 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 11 The set (one or more) components shown can perform actions described by Figure 11 The other set of components shown performs one or more functions.

[0130] The following provides an overview of some aspects of this disclosure:

[0131] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: detecting Transmission Control Protocol (TCP) packet loss based at least in part on a Packet Data Convergence Protocol (PDCP) payload of the packet; and sending a plurality of retransmission requests for the packet based at least in part on the detection of the TCP packet loss of the packet.

[0132] Aspect 2: According to the method of aspect 1, sending the plurality of retransmission requests includes: sending a set of duplicate acknowledgments based at least in part on the detection of TCP packet loss of the packet.

[0133] Aspect 3: According to the method of aspect 2, wherein the group repeat is transmitted by a modem associated with the PDCP entity of the UE.

[0134] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the group repeat is transmitted by a hardware or software component of an Internet Protocol (IP) packet processing entity.

[0135] Aspect 5: The method according to any one of Aspects 2 to 4, wherein the group repetition is sent by an advanced operating system entity.

[0136] Aspect 6: The method according to any one of Aspects 2 to 5, wherein the group repeat is sent by a TCP entity.

[0137] Aspect 7: The method according to any one of Aspects 1 to 6, wherein detecting the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the size of the PDCP payload or the content of the PDCP payload.

[0138] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on an inspection of the header of the PDCP payload.

[0139] Aspect 9: The method according to aspect 8, wherein the inspection of the header of the PDCP payload is performed using hardware or software components of an Internet Protocol (IP) packet processing entity.

[0140] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the fact that the packet is invalid.

[0141] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the packet having zero payload or spurious payload.

[0142] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the expiration of the PDCP timer of the UE.

[0143] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the detection of said TCP packet loss includes: detecting Radio Link Control (RLC) level packet loss.

[0144] Aspect 14: A method for wireless communication performed by a user equipment (UE), the method comprising: detecting TCP packet loss based at least in part on a Transmission Control Protocol (TCP) sequence and in the absence of Packet Data Convergence Protocol (PDCP) loss; and sending a plurality of retransmission requests for the packet based at least in part on the detection of the TCP packet loss of the packet.

[0145] Aspect 15: The method according to aspect 14, wherein sending the plurality of retransmission requests includes: sending a set of duplicate acknowledgments based at least in part on the detection of TCP packet loss of the packet.

[0146] Aspect 16: The method according to aspect 15, wherein the group repeat is transmitted by a modem associated with the PDCP entity of the UE.

[0147] Aspect 17: The method according to any one of Aspects 15 and 16, wherein the group repeat is transmitted by a hardware or software component of an Internet Protocol (IP) packet processing entity.

[0148] Aspect 18: The method according to any one of aspects 15 to 17, wherein the group repetition is sent by an advanced operating system entity.

[0149] Aspect 19: The method according to any one of Aspects 15 to 18, wherein the group repeat is sent by a TCP entity.

[0150] Aspect 20: The method according to any one of Aspects 14 to 19, wherein detecting the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the size of the PDCP payload or the content of the PDCP payload.

[0151] Aspect 21: The method according to any one of Aspects 14 to 20, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on an inspection of the header of the PDCP payload.

[0152] Aspect 22: The method according to aspect 21, wherein the inspection of the header of the PDCP payload is performed using hardware or software components of an Internet Protocol (IP) packet processing entity.

[0153] Aspect 23: The method according to any one of Aspects 14 to 22, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the fact that the packet is invalid.

[0154] Aspect 24: The method according to any one of Aspects 14 to 23, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the packet having zero payload or spurious payload.

[0155] Aspect 25: The method according to any one of Aspects 14 to 24, wherein the detection of the TCP packet loss comprises: detecting the TCP packet loss based at least in part on the expiration of the PDCP timer of the UE.

[0156] Aspect 26: The method according to any one of Aspects 14 to 25, wherein the detection of said TCP packet loss includes: detecting Radio Link Control (RLC) level packet loss.

[0157] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 13.

[0158] Aspect 28: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 13.

[0159] Aspect 29: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 13.

[0160] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described according to one or more of aspects 1 to 13.

[0161] Aspect 31: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects 1 to 13.

[0162] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 14 to 26.

[0163] Aspect 33: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more aspects 14 to 26.

[0164] Aspect 34: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 14 to 26.

[0165] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 14 to 26.

[0166] Aspect 36: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects of aspects 14 to 26.

[0167] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or can be derived from practice in the aspects.

[0168] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. "Software" should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, programs and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other names. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of systems and / or methods are described herein without reference to specific software code, as those skilled in the art will understand that software and hardware can be designed to implement systems and / or methods at least in part based on the descriptions herein.

[0169] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0170] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. Many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of the aspects includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, b+b+c, c+c and c+c+c, or any other ordering of a, b, and c).

[0171] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more”. Furthermore, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the”, and may be used interchangeably with “one or more”. Additionally, as used herein, the terms “set” and “group” are intended to include one or more items, and may be used interchangeably with “one or more”. If only one item is intended, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on”, unless otherwise explicitly stated. Furthermore, as used herein, unless otherwise explicitly stated (e.g., if used in combination with “any” or “only one of them”), the term “or” is intended to be inclusive when used in a series, and may be used interchangeably with “and / or”.

Claims

1. A user equipment (UE) for wireless communication, the user equipment comprising: Memory; and One or more processors coupled to the memory, the one or more processors being configured to: Detecting Transmission Control Protocol (TCP) packet loss is based at least in part on the Packet Data Convergence Protocol (PDCP) payload; and Multiple retransmission requests for the packet are sent, at least in part based on the detection of TCP packet loss of the packet. The sending of the plurality of retransmission requests includes a set of duplicate acknowledgments sent at least in part based on the detection of TCP packet loss of the packet. The group repeats are transmitted by a modem associated with the PDCP entity of the UE.

2. The UE according to claim 1, wherein, The one or more processors used to detect the loss of the TCP packets are configured to: The TCP packet loss is detected at least in part based on the size of the PDCP payload or the content of the PDCP payload.

3. The UE according to claim 1, wherein, The detection of the lost TCP packets includes: The detection of TCP packet loss is based at least in part on an inspection of the header of the PDCP payload.

4. The UE according to claim 3, wherein, The inspection of the header of the PDCP payload is performed using hardware or software components of the Internet Protocol (IP) packet processing entity.

5. The UE according to claim 1, wherein, The detection of the lost TCP packets includes: The detection of TCP packet loss is based at least in part on the fact that the packet is invalid.

6. The UE according to claim 1, wherein, The detection of the lost TCP packets includes: The TCP packet loss is detected at least in part based on the fact that the packet has zero payload or a spurious payload.

7. The UE according to claim 1, wherein, The detection of the lost TCP packets includes: The TCP packet loss is detected at least in part based on the expiration of the UE's PDCP timer.

8. The UE according to claim 1, wherein, The detection of the lost TCP packets includes: Detect packet loss at the Radio Link Control (RLC) level.

9. A user equipment (UE) for wireless communication, the user equipment comprising: Memory; and One or more processors coupled to the memory, the one or more processors being configured to: It is at least partially based on Transmission Control Protocol (TCP) sequences and detects TCP packet loss in the absence of Packet Data Convergence Protocol (PDCP) loss; and Multiple retransmission requests for the packet are sent, at least in part based on the detection of TCP packet loss of the packet. The sending of the plurality of retransmission requests includes a set of duplicate acknowledgments sent at least in part based on the detection of TCP packet loss of the packet. The group repeats are transmitted by a modem associated with the PDCP entity of the UE.

10. A method for wireless communication performed by a user equipment (UE), the method comprising: The detection of Transmission Control Protocol (TCP) packet loss is based at least in part on the Packet Data Convergence Protocol (PDCP) payload. as well as Multiple retransmission requests for the packet are sent, at least in part based on the detection of TCP packet loss of the packet. The sending of the plurality of retransmission requests includes a set of duplicate acknowledgments sent at least in part based on the detection of TCP packet loss of the packet. The group repeats are transmitted by a modem associated with the PDCP entity of the UE.

11. The method according to claim 10, wherein, The detection of the lost TCP packets includes: The TCP packet loss is detected at least in part based on the size of the PDCP payload or the content of the PDCP payload.

12. The method according to claim 10, wherein, The detection of the lost TCP packets includes: The detection of TCP packet loss is based at least in part on an inspection of the header of the PDCP payload.

13. The method according to claim 12, wherein, The inspection of the header of the PDCP payload is performed using hardware or software components of the Internet Protocol (IP) packet processing entity.

14. A method for wireless communication performed by a user equipment (UE), the method comprising: It is at least partially based on Transmission Control Protocol (TCP) sequences and detects TCP packet loss in the absence of Packet Data Convergence Protocol (PDCP) loss; as well as Multiple retransmission requests for the packet are sent, at least in part based on the detection of TCP packet loss of the packet. The sending of the multiple retransmission requests includes a set of duplicate acknowledgments sent, at least in part based on the detection of TCP packet loss of the packets. The group repeats are transmitted by a modem associated with the PDCP entity of the UE.

15. The method according to claim 14, wherein, The detection of the lost TCP packets includes: The TCP packet loss is detected at least in part based on the size of the PDCP payload or the content of the PDCP payload.

16. The method of claim 14, wherein, The inspection of the PDCP payload header is performed using hardware or software components of the Internet Protocol (IP) packet processing entity.

17. An apparatus for wireless communication, comprising components for performing the method according to any one of claims 10-13.

18. An apparatus for wireless communication, comprising components for performing the method according to any one of claims 14-16.

19. A non-transitory computer-readable medium storing computer-readable instructions, said computer-readable instructions including at least one instruction for causing at least one processor to perform the method according to any one of claims 10-13.

20. A non-transitory computer-readable medium storing computer-readable instructions, said computer-readable instructions including at least one instruction for causing at least one processor to perform the method according to any one of claims 14-16.

Images