Radio link control layer feedback reporting for rateless codes

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a receiving party can determine that a number of a first plurality of radio link layer (RLC) protocol data unit (PDU) packets received from a transmitting party satisfies a first quantity threshold. The receiving party can perform a decoding attempt for the first plurality of RLC PDU packets based at least in part on the determination. The receiving party can transmit, to the transmitting party, an RLC layer feedback report for the first plurality of RLC PDU packets. The RLC layer feedback report can be based at least in part on the decoding attempt. Numerous other aspects are provided.

Description

[0001] Cross Reference to Related Applications

[0002] This Patent Application claims priority to International Patent Application No. PCT / CN2020 / 093858, filed June 2, 2020, entitled “RADIO LINK CONTROL LAYER FEEDBACK REPORTING FOR RATELESS CODES” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is hereby incorporated by reference into this Patent Application.

[0003] Field of the Disclosure

[0004] Aspects of the disclosure relate generally to wireless communication and to techniques and apparatuses for radio link control layer feedback reporting for rateless codes.

[0005] BACKGROUND

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting 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 set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0007] A wireless network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A UE can communicate with a BS via the downlink and uplink. “Downlink” (or “forward link”) refers to the communication link from the BS to the UE, and “uplink” (or “reverse link”) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS can be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a new radio (NR) BS, a 5G Node B, and / or the like.

[0008] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols facilitating communication between wireless devices in cities, countries, regions, and even globally. NR, which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDM with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP- OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE, NR, and other radio access technologies.

[0009] SUMMARY

[0010] In some aspects, a method of wireless communication performed by a receiver includes determining that a quantity of a first plurality of radio link layer (RLC) protocol data unit (PDU) packets received from a transmitter satisfies a first quantity threshold; performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; and transmitting, to the transmitter, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving a second plurality of RLC PDU packets from the transmitter, wherein the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0011] 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 receiver, cause the receiver to: determine that a quantity of a first plurality of RLC PDU packets received from a transmitter satisfies a first quantity threshold; perform a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; and transmit, to the transmitter, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving a second plurality of RLC PDU packets from the transmitter, wherein the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0012] In some aspects, a receiver for wireless communication includes a memory; and one or more processors coupled with the memory, the memory and the one or more processors configured to: determine that a quantity of a first plurality of RLC PDU packets received from a transmitter satisfies a first quantity threshold; perform a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; and transmit, to the transmitter, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving a second plurality of RLC PDU packets from the transmitter, wherein the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0013] In some aspects, an apparatus for wireless communication includes means for determining that a quantity of a first plurality of RLC PDU packets received from a transmitter satisfies a first quantity threshold; means for performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; and means for transmitting, to the transmitter, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving a second plurality of RLC PDU packets from the transmitter, wherein the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0014] In some aspects, a method of wireless communication performed by a receiver includes determining that a RLC PDU packet having a particular packet SN is received from a transmitter; and performing a decoding attempt for a plurality of RLC PDU packets received from the transmitter based at least in part on determining that the RLC PDU packet having the particular packet SN is received, wherein the plurality of RLC PDU packets have packet SNs lower than the particular packet SN of the RLC PDU packet.

[0015] 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 receiver, cause the receiver to: determine that a RLC PDU packet having a particular packet SN is received from a transmitter; and perform a decoding attempt for a plurality of RLC PDU packets received from the transmitter based at least in part on determining that the RLC PDU packet having the particular packet SN is received, wherein the plurality of RLC PDU packets have packet SNs lower than the particular packet SN of the RLC PDU packet.

[0016] In some aspects, a receiver for wireless communication includes a memory, and one or more processors coupled with the memory, the memory and the one or more processors configured to: determine that a RLC PDU packet having a particular packet SN is received from a transmitter; and perform a decoding attempt for a plurality of RLC PDU packets received from the transmitter based at least in part on determining that the RLC PDU packet having the particular packet SN is received, wherein the plurality of RLC PDU packets have packet SNs lower than the particular packet SN of the RLC PDU packet.

[0017] In some aspects, an apparatus for wireless communication includes means for determining that a RLC PDU packet having a particular packet SN is received from a transmitter; and means for performing a decoding attempt for a plurality of RLC PDU packets received from the transmitter based at least in part on determining that the RLC PDU packet having the particular packet SN is received, wherein the plurality of RLC PDU packets have packet SNs lower than the particular packet SN of the RLC PDU packet.

[0018] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

[0019] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions not only follow from the scope of the claims but are intended to be encompassed thereby. The characteristics of the concepts disclosed herein both their organization and method of operation together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description and not as a definition of the limits of the claims.

[0020] Although the aspects are described in the context of some examples in the disclosure, those skilled in the art will appreciate that the aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platforms, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments, or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). The aspects can be implemented in chip-level components, module-level components, non-module-component level components, non-chip-level components, device-level components, or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of the claimed and described aspects. For example, transmission and reception of wireless signals can include a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of varying sizes, shapes, and constitution. HEDICATURE

[0022] To enable a detailed understanding of the above-described features of the present disclosure, reference will be made to certain aspects, which are described herein with some particularity. It should be appreciated that the accompanying drawings are intended to illustrate certain typical aspects of the present disclosure and are not to be construed as limiting the scope of the disclosure as it can be permitted to encompass other equally effective aspects. Identical reference numerals in different drawings can identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of a base station in communication with a UE in a wireless network, in accordance with the present disclosure.

[0025] Figure 3 An example logical architecture of a distributed Radio Access Network (RAN), in accordance with the present disclosure, is illustrated.

[0026] Figure 4 An example physical architecture of a distributed RAN, in accordance with the present disclosure, is illustrated.

[0027] Figure 5 is a diagram illustrating an example of network coding, in accordance with the present disclosure.

[0028] Figure 6A and Figure 6Bis a diagram illustrating an example associated with radio link control layer (RLC) feedback reporting for rateless codes in accordance with the present disclosure.

[0029] Figure 7 and Figure 8 is a diagram illustrating an example process associated with RLC feedback reporting for rateless codes in accordance with the present disclosure.

[0030] DETAILED DESCRIPTION

[0031] Various aspects of the disclosure are described more fully below. However, the disclosure may be implemented in any of numerous ways, and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. The scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such apparatus or method which

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0033] It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0034] Figure 1is a diagram illustrating an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 can be or can include elements of a 5G (NR) network and / or a LTE network, among other examples. The wireless network 100 can include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and can also be referred to as an NR BS, a NodeB, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), and / or the like. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0035] BSs can be macro BSs, pico BSs, femto BSs, and / or other types of BSs. A macro BS can cover a relatively large geographic area (e.g., 100s of feet to 10s of kilometers in radius) and can allow unrestricted access to users with service subscriptions. A pico BS can cover a relatively small geographic area (e.g., a home) and can allow restricted access to users with service subscriptions. A femto BS can cover a relatively small geographic area (e.g., a home) and can allow restricted access to users with service subscriptions. Figure 1 In an example shown in FIG. 1, BS 110a can be a macro BS for a macro cell 102a, BS 110b can be a pico BS for a pico cell 102b, and BS 110c can be a femto BS for a femto cell 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0036] In some aspects, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile BS. In some aspects, the BSs can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as a direct physical connection or a virtual network, using any suitable transmission medium) using any suitable transmission network.

[0037] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in Figure 1, relay BS 1 lOd can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, a relay base station, a relay, or the like.

[0038] Wireless network 100 can be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0039] A network controller 130 can couple to a set of BSs and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via a backhaul. The BSs can also communicate with one another directly or indirectly via a wireless or wireline backhaul.

[0040] UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE can be a cellular phone (e.g., a smart phone), 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0041] Some UEs can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet-of-Things (IoT) devices, and / or can be implemented as NB-IoT (narrowband

[0042] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, and / or the like. Frequencies can also be referred to as carriers, frequency channels, and / or the like. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0043] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110. Some communications between a UE 120 and a base station 110 can be transmitted on downlink channels (e.g., from the base station 110 to the UE 120) and / or uplink channels (e.g., from the UE 120 to the base station 110). Additionally, or alternatively, some communications can be transmitted on peer-to-peer (P2P) channels (e.g., between the UE 120 and one or more other UEs 120).

[0044] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various classes, bands, channels, and so on. For example, devices of wireless network 100 can communicate using an operating band having a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz, and / or can communicate using an operating band having a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, it will be understood that the term “sub-6 GHz” or like references, if used herein, can broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it will be understood that the term “millimeter wave” or like references, if used herein, can broadly represent frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and techniques described herein are applicable to those modified frequency ranges.

[0045] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to at least one of the following. Figure 1

[0046] Figure 2 is a diagram illustrating an example 200 in which a base station 110 is in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The base station 110 can be equipped with T antennas 234a through 234t, and the UE 120 can be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0047] ​At base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 can also 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. Transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively.

[0048] At the UE 120, the antennas 252a through 252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or channel quality indicator (CQI) parameters, among other examples. In some aspects, one or more components of UE 120 can be included in a housing 284.

[0049] The network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0050] Antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included in one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, among other examples. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include a set of co-planar antenna elements and / or a set of non-co-planar antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include antenna elements within a single housing and / or antenna elements within multiple housings. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 264 and / or a wireless communication manager 270). Figure 2 An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 264 and / or a wireless communication manager 270).

[0051] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 254) of the UE 120 can be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver can include any combination of antennas 252, modulators and / or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein, for example, as described with reference to Figure 6A , 6B and 7.

[0052] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and to controller / processor 240 for control information. Base station 110 can include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 can include a scheduler 246 to schedule UEs 120 for downlink and / or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 232) of the base station 110 can be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver can include any combination of antennas 234, modulators and / or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform any of the methods described herein, for example, as described with reference to Figure 6A , 6B and 7.

[0053] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with rate-code-free radio link control (RLC) layer feedback reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 7 The operation of process 700 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, 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, when executed by one or more processors of base station 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 7 The operation of process 700 and / or other processes as described herein. In some aspects, the execution instructions may include run instructions, translate instructions, compile instructions, and / or interpret instructions, etc.

[0054] In some aspects, UE 120 may include: means for determining that the number of a first plurality of RLC Protocol Data Unit (PDU) packets received from a transmitter satisfies a first quantity threshold; means for performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on the determination that the number of the first plurality of RLC PDU packets satisfies the first quantity threshold; and means for transmitting an RLC layer feedback report for the first plurality of RLC PDU packets to the transmitter after receiving a second plurality of RLC PDU packets from the transmitter, wherein the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and wherein the RLC layer feedback report is based at least in part on the decoding attempt, etc. In some aspects, such means may include a combination of Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0055] In some aspects, a base station 110 can include means for determining that a quantity of a first plurality of RLC PDU packets received from a transmitting party satisfies a first quantity threshold; means for performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; means for determining that a quantity of a second plurality of RLC PDU packets received from the transmitting party after receiving the first plurality of RLC PDU packets satisfies a second quantity threshold; means for transmitting, to the transmitting party, an RLC layer feedback report for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the second plurality of RLC PDU packets satisfies the second quantity threshold, wherein the RLC layer feedback report is based at least in part on the decoding attempt; and / or the like. In some aspects, such means can include one or more components of base station 110 described in connection with Figure 2 The described base station 110 can have one or more components described in connection with FIG. 2, such as, for example, antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and / or the like.

[0056] Although Figure 2 The blocks in FIG. 14 are illustrated as distinct components, but the functionality described above in relation to these blocks can be implemented in a single hardware, software, or combined component or a combination of various components. For example, the functionality described in relation to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0057] As indicated above, the Figure 2 are provided as examples. Other examples can differ from what is described in relation to the Figure 2 examples described in relation to FIG. 14.

[0058] Figure 3 An example logical architecture of a distributed RAN 300 is illustrated in accordance with aspects of the present disclosure. A 5G access node (AN) 306 can include an access node controller (ANC) 302. The ANC can be a central unit (CU) of the distributed RAN 300. The backhaul interface to the next generation core network (NG-CN or NG core) 304 can terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) can terminate at the ANC. The ANC can include one or more TRPs 308 (which can also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term). As described above, a “TRP” can be used interchangeably with “cell.”

[0059] The TRPs 308 can be distributed units (DUs). The TRPs can be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRPs can be connected to more than one ANC. The TRPs can include one or more antenna ports. The TRPs can be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

[0060] The local architecture of the RAN 300 can be used to illustrate fronthaul

[0061] The architecture can share features and / or components with LTE. According to aspects, a next generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0062] The architecture can enable cooperation between and among TRPs 308. For example, cooperation can be preset within a TRP and / or across TRPs via the ANC 302. According to aspects, no inter-TRP interface can be needed / present.

[0063] According to aspects, there can be a dynamic configuration of split logical functions within the architecture of the RAN 300. The packet data convergence protocol (PDCP), RLC, or medium access control (MAC) protocol can be adaptably placed at the ANC or TRP.

[0064] According to various aspects, a BS can include a CU (e.g., an ANC 302) and / or one or more DUs (e.g., one or more TRPs 308). In some aspects, a BS (e.g., a 5G AN 306) can be implemented as a virtual machine running on a physical host (e.g., a top-level assembly (TLA) virtualization). Figure 3The example distributed RAN 300 illustrated in FIG. 3 can be used to provide, broadcast, multicast, and / or unicast support for one or more UEs 120. For example, a BS can receive a multicast broadcast (MB) quality of service (QoS) flow from a 5G user plane function (UPF) device (e.g., network controller 130) in the NG-CN 304. The BS can receive the MB QoS flow via an N3 user plane interface and through a tunneling protocol (e.g., general packet radio service (GPRS) tunneling protocol or another type of tunneling protocol). The BS can receive the MB QoS flow at the CU (e.g., ANC 302). A 5G access and mobility management function (AMF) device (e.g., network controller 130) can provide control signaling to the CU over an N2 interface to establish and / or modify the MB QoS flow. The BS can map the MB QoS flow to one or more multicast radio bearers (MRBs) and can provide the MB QoS flow to one or more DUs (e.g., one or more TRPs 308) via the one or more MRBs. The DUs can multicast or broadcast the MB QoS flow to one or more UEs 120.

[0065] As indicated above, Figure 3 are provided by way of example. Other examples can differ from Figure 3 the examples described.

[0066] Figure 4 An example physical architecture of a distributed RAN 400 is illustrated. A centralized core network unit (C-CU) 402 can host core network functions that can be implemented by one or more network controllers 130. The core network functions can include 5G UPF, 5G AMF, and / or other core network functions. The C-CU can be centrally deployed. C-CU functionality can be offloaded (e.g., to advanced wireless services (AWS)) in an effort to handle peak capacity.

[0067] A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have a distributed deployment. The C-RU can be closer to the network edge. A DU 406 can host one or more TRPs. The DU can be located at the edge of the network with radio frequency (RF) functionality.

[0068] In some aspects, a BS can receive, via an N2 interface, a request from a network controller 130 to establish a multicast radio bearer (MRB) for a multicast broadcast service (MBS) session. The BS can transmit, via an N1 interface, a request to one or more UEs 120 to join the MBS session. The BS can receive, via the N2 interface, a request from the network controller 130 to modify the MRB. The BS can transmit, via the N1 interface, a request to the one or more UEs 120 to modify the MBS session. Figure 4The example distributed RAN 400 illustrated in FIG. 4 can be used to provide, broadcast, multicast, and / or unicast support for one or more UEs 120. For example, a BS can receive an MB QoS flow from a 5G UPF device of the C-CU 402 (e.g., network controller 130). The BS can receive the MB QoS flow via an N3 user plane interface and through a tunneling protocol (e.g., GPRS Tunneling Protocol or another type of tunneling protocol). The BS can receive the MB QoS flow at the C-RU 404. A 5G AMF device of the C-CU 402 (e.g., network controller 130) can provide control signaling on an N2 interface to the C-RU 404 to setup and / or modify the MB QoS flow. The BS can map the MB QoS flow to one or more MRBs and can provide the MB QoS flow to one or more DUs 406 via the one or more MRBs. The DUs 406 can multicast or broadcast the MB QoS flow to one or more UEs 120.

[0069] As indicated above, Figure 4 are provided as examples. Other examples can differ from what is described with respect to at least one of the described examples. Figure 4 are provided as examples. Other examples can differ from what is described with respect to at least one of the described examples.

[0070] Figure 5 is a diagram illustrating an example 500 of network coding in accordance with the present disclosure. The operations described in FIG. 5 can be performed by a transmitting party (also referred to as an encoder), such as a UE 120 or base station 110. Figure 5 The operations described in FIG. 5 can be performed by a transmitting party (also referred to as an encoder), such as a UE 120 or base station 110.

[0071] As shown by reference number 505, the transmitting party can generate an RLC service data unit (SDU) from one or more PDCP protocol data units (PDUs). In some aspects, a single PDCP PDU can be included in the RLC SDU. In some aspects, multiple PDCP PDUs can be included in the RLC SDU (e.g., by concatenating multiple PDCP PDUs). In some aspects, the transmitting party can determine whether to include a single PDCP PDU in a single RLC SDU or to concatenate multiple PDCP PDUs in a single RLC SDU based at least in part on a size of the PDCP PDU. For example, if the size of the PDCP PDU satisfies a threshold (e.g., is greater than or equal to the threshold), the encoder can include only that PDCP PDU (e.g., a single PDCP PDU) in a single RLC SDU. If the size of the PDCP PDU does not satisfy the threshold (e.g., is less than or equal to the threshold), the encoder can concatenate multiple PDCP PDUs (e.g., a group of PDCP PDUs with a total size less than or equal to the threshold) into a single RLC SDU.

[0072] As shown by reference number 510, the transmitter can divide the RLC SDU into a plurality of data blocks. For example, the transmitter can divide the RLC SDU into K data blocks (shown as si to sK) based at least in part on a set of network coding parameters. In some aspects, the set of network coding parameters can specify a value of K for a particular subset of parameters, such as a payload size of the RLC SDU, a size of a sequence number field in a RLC PDU header of the RLC SDU, and / or the like. In some aspects, the encoder can determine the value of K for the subset of parameters. K ). In some aspects, the set of network coding parameters can specify a value of K for a particular subset of parameters, such as a payload size of the RLC SDU, a size of a sequence number field in a RLC PDU header of the RLC SDU, and / or the like. In some aspects, the encoder can determine the value of K for the subset of parameters.

[0073] In some aspects, the operations associated with reference numbers 505 and 510 can be performed at a PDCP layer of the transmitter. The PDCP layer can provide the data blocks to an RLC layer of the transmitter. As shown by reference number 515, the transmitter can encode the K data blocks into N forward error correction (FEC) packets using network coding. For example, the transmitter can encode the K data blocks into N FEC packets (shown as pi to pN) based at least in part on a rateless code, such as a network code, a fountain code, a Luby transform (LT) code, a Raptor code, and / or the like. In particular, the transmitter can encode the K data blocks into the N FEC packets such that the N FEC packets include additional information or bits for the purposes of forward error correction. This permits a receiver to recover the FEC packets, e.g., if a number of received FEC packets is greater than a number of the K data blocks regardless of which FEC packets are received. N ). In some aspects, the set of network coding parameters can specify a value of K for a particular subset of parameters, such as a payload size of the RLC SDU, a size of a sequence number field in a RLC PDU header of the RLC SDU, and / or the like. In some aspects, the encoder can determine the value of K for the subset of parameters.

[0074] In some aspects, a number of RLC packets (e.g., a value of N) can be based at least in part on the set of network coding parameters. In some aspects, the set of network coding parameters can specify a value of N for a particular subset of parameters, a delay budget of the RLC SDU, available encoding and decoding computational resources of the transmitter, a value of K (e.g., a number of data blocks), a target error probability for one or more RLC PDU packets of the N FEC packets, channel conditions for transmission of the RLC PDU packets, a type of network code to be used to encode the K data blocks into the N FEC packets, and / or the like. In some aspects, the transmitter can determine the value of N for the subset of parameters.

[0075] As shown by reference number 520, the transmitter can map the N FEC packets into respective M RLC PDU packets. For example, the transmitter can map the N FEC packets into M RLC PDU packets (shown as PDUi to PDU M) such that each RLC PDU includes multiple FEC packets (e.g., two FEC packets per RLC PDU packet, four FEC packets per RLC PDU packet, and / or the like). In some aspects, the operations associated with reference numbers 515 and 520 can be performed at a RLC layer of the transmitting side. The RLC layer can receive the indication of the set of network coding parameters from the RRC layer and can perform the operations associated with reference numbers 515 and 520 based at least in part on the set of network coding parameters.

[0076] The RLC layer can provide the M RLC PDU packets to a MAC layer of the transmitting side. As shown by reference number 525, the transmitting side can generate a MAC PDU for the M RLC PDU packets. In some aspects, the MAC PDU can include a RLC PDU header or a MAC PDU header, which can include information associated with each of the M RLC PDUs. For example, the RLC PDU header or the MAC PDU header can include a sequence number field, which can include a sequence number associated with each of the M RLC PDUs. In some aspects, the operations associated with reference number 525 can be performed at a MAC layer of the transmitting side.

[0077] The MAC layer of the transmitting side can provide the MAC PDU to a physical (PHY) layer of the transmitting side. As shown by reference number 530, an encoder can transmit the M RLC PDU packets (e.g., in the MAC PDU) to a receiving side (also referred to as a decoder), such as a UE 120 or a base station 110. In some aspects, the PHY layer of the transmitting side can transmit the M RLC PDU packets (e.g., in the MAC PDU) over a wireless physical channel, such as a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), a physical uplink control channel (PDCCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), and / or the like.

[0078] As indicated above, Figure 5 are provided by way of example. Other examples can differ from Figure 5 the examples described.

[0079] In some cases, a transmitter and a receiver can implement automatic repeat request (ARQ) at the RLC layer to increase reliability and robustness of RLC layer communications between the transmitter and the receiver. In some cases, an ARQ scheme for the RLC layer can include a poll request / status report technique, in which the transmitter transmits a poll request to the receiver and the receiver responds with a status report. The poll request can be transmitted for a RLC window of RLC PDU packets, and the status report can indicate an acknowledgement (ACK) or negative acknowledgement (NACK) for each RLC PDU packet in the RLC window. Each poll request can slide the window forward by a certain number of RLC PDU packets. Further, each ACK and NACK can indicate a sequence number of the associated RLC PDU packet.

[0080] However, the poll request / status report technique can be inefficient because the transmitter will stop transmission of additional RLC PDU packets until retransmission of a failed RLC PDU packet (e.g., a RLC PDU packet for which a NACK is received) is performed. Further, the poll request / status report technique can be inefficient because the poll request / status report technique does not utilize the forward error correction capabilities of a rateless code, such as a network code or a fountain code.

[0081] Some aspects described herein provide techniques and apparatuses for RLC layer feedback reporting for rateless codes. In some aspects, a receiver (e.g., UE 120, base station 110, etc.) can receive a plurality of RLC PDU packets, each RLC PDU packet including one or more FEC packets encoded using a rateless network code. The receiver can determine, based at least in part on a number of the plurality of RLC PDU packets, when to transmit a RLC layer feedback report for the plurality of packets. In this way, the receiver can transmit RLC layer feedback for the plurality of RLC PDU packets without having to wait for a poll request from the transmitter, which reduces processing and memory resources and radio network resources of the transmitter that would otherwise be consumed in generating and transmitting the poll request. Further, the receiver can include various types of RLC layer feedback in the RLC layer feedback report to assist the transmitter in determining which FEC packets to retransmit, to assist the transmitter in determining whether to adjust network coding parameters for subsequent RLC PDU packets, to assist the transmitter in determining whether to transmit additional RLC PDU packets to enable more robust decoding and forward error correction, etc.

[0082] Figure 6A and Figure 6B is a diagram illustrating one or more examples 600 associated with RLC feedback reporting for rateless codes, in accordance with the present disclosure. As Figure 6A and 6BAs shown in the example 600, the first plurality of RLC PDU packets can be encoded to include one or more FEC packets. In some aspects, the one or more FEC packets can be encoded according to the techniques described above in connection with the example 500 and / or other network coding techniques. Accordingly, each of the first plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets.

[0083] As Figure 6A In some aspects, the first plurality of RLC PDU packets can be encoded according to the techniques described above in connection with the example 500 and / or other network coding techniques. Accordingly, each of the first plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets. Figure 5 In some aspects, the first plurality of RLC PDU packets can be encoded according to the techniques described above in connection with the example 500 and / or other network coding techniques. Accordingly, each of the first plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets.

[0084] As Figure 6A In some aspects, the first plurality of RLC PDU packets can be encoded according to the techniques described above in connection with the example 500 and / or other network coding techniques. Accordingly, each of the first plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets.

[0085] In some aspects, the first plurality of RLC PDU packets can be encoded according to the techniques described above in connection with the example 500 and / or other network coding techniques. Accordingly, each of the first plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets.

[0086] AsFigure 6A As further shown by reference number 606, the receiving party can perform a decoding attempt of the first plurality of RLC PDU packets. In some aspects, the receiving party can perform the decoding attempt of the first plurality of RLC PDU packets based at least in part on determining that the number of the first plurality of RLC PDU packets satisfies a first threshold (e.g., a threshold number L of RLC PDUs). In some aspects, the receiving party can perform the decoding attempt by attempting to decode each of the first plurality of RLC PDU packets.

[0087] In some aspects, the receiving party can attempt to decode the first plurality of RLC PDU packets by determining whether the receiving party is able to recover a data block of an original RLC SDU included in the first plurality of RLC PDUs. In some aspects, the receiving party can determine whether any FEC packets of the first plurality of RLC PDU packets are missing or un-decodable. If one or more FEC packets of the RLC PDU packets are missing or un-decodable, the receiving party can attempt to recover the data block of the missing or un-decodable FEC packet by performing forward error correction using other FEC packets in that RLC PDU packet and / or other RLC PDU packets of the first plurality of RLC PDU packets. In these examples, the receiving party can use additional information or bits encoded in the other FEC packets to reconstruct or infer the data block of the missing or un-decodable FEC packet.

[0088] Instead of determining that the L number of RLC PDU packets have been successfully received and performing a decoding attempt for the L number of RLC PDU packets based at least in part on determining that the L number of RLC PDU packets have been successfully received, the receiving party can perform a decoding attempt after receiving an RLC PDU packet having a packet sequence number (SN) that is greater than L. In these aspects, the receiving party determines that an RLC PDU packet having a packet SN that is greater than L (e.g., L+1 or another packet SN that is greater than L) has been received and performs a decoding attempt for the successfully received RLC PDU packets 1 through L based at least in part on determining that the RLC PDU packet having a packet SN that is greater than L has been received.

[0089] As Figure 6B As further shown by reference number 608, the transmitting party can transmit a second plurality of RLC PDU packets (e.g., RLC PDU packet L+1 through RLC PDU packet L+D) to the receiving party. In some aspects, each of the second plurality of RLC PDU packets or a subset thereof can be encoded to include one or more FEC packets using the network coding techniques described above in connection with reference number 604 and / or other network coding techniques. Figure 5

[0090] As​Figure 6B As further shown by reference number 610, the receiving party can determine that the number of the second plurality of RLC PDU packets satisfies a second threshold. The second threshold can be a threshold number of RLC PDU packets, Delta (D), received after a threshold number, L, of RLC PDU packets are received. In some aspects, the receiving party can determine the threshold number of RLC PDU packets, D, based at least in part on an RLC configuration at the RLC layer of the receiving party. In some aspects, the RLC configuration can be configured by an RRC layer of the receiving party. In some aspects, the threshold number of RLC PDU packets, D, can be programmed at the receiving party, can be hard-coded at the receiving party, can be defined in a wireless communication standard, a wireless communication specification, or the like. In some aspects, the transmitting party or another wireless communication device can signal the threshold number of RLC PDU packets, D, to the receiving party.

[0091] An example value for D can be 6 RLC PDU packets. As another example, a value for D can be 0 RLC PDU packets (e.g., the receiving party will transmit the RLC layer feedback report immediately after generating the RLC layer feedback report). However, other values for D can be used. In some aspects, the first number threshold (L) and the second number threshold (D) can be configured together (e.g., in the same RLC configuration). In some aspects, the first number threshold (L) and the second number threshold (D) are related. For example, a value for the first number threshold (L) can be based at least in part on an SDU size of an SDU in which the first plurality of RLC PDU packets are included, and a value for the second number threshold (D) can be based at least in part on the value for the first number threshold (L).

[0092] As further shown by reference number 612 and described in Figure 6B As further shown by reference number 612 and described in

[0093] The RLC layer feedback report can be for the first plurality of RLC PDU packets and can be based at least in part on the decoding attempts for the first plurality of RLC PDU packets. In some aspects, the RLC layer feedback report can include feedback information associated with the first plurality of RLC PDU packets. For example, the RLC layer feedback report can include information that identifies an ACK or a NACK for the first plurality of RLC PDU packets as a whole (e.g., an ACK indicating that the data blocks of the first plurality of RLC PDU packets have been decoded and / or recovered, a NACK indicating that one or more RLC PDU packets cannot be decoded and / or recovered, and / or the like). As another example, the RLC layer feedback report can include information that identifies an ACK or a NACK for each of the first plurality of RLC PDU packets.

[0094] As another example, the RLC layer feedback report can include information that identifies a number of RLC PDU packets of the first plurality of RLC PDU packets for which the decoding attempts failed (e.g., missing or un-decodable RLC PDU packets). As another example, the RLC layer feedback report can include information that identifies a number of FEC packets of the RLC PDU packets included in the first plurality of RLC PDU packets for which the decoding attempts failed (e.g., missing or un-decodable FEC packets). As another example, the RLC layer feedback report can include information that identifies an index associated with the FEC encoded packets of the RLC PDU packets included in the first plurality of RLC PDU packets for which the decoding attempts failed.

[0095] Instead of determining that the delta number of RLC PDU packets have been received after the L RLC PDU packets and transmitting the RLC layer feedback report based at least in part on determining that the delta number of RLC PDU packets have been received after the L RLC PDU packets, the receiver can transmit the RLC layer feedback report after receiving a RLC PDU packet having a packet SN that is greater than a particular packet SN (e.g., the packet SN is a higher packet SN than a packet SN associated with a RLC PDU packet based on which the receiver determines to perform the decoding attempts for the L RLC PDU packets).

[0096] In some aspects, the receiver tracks a counter of RLC PDU packets received by the receiver. The receiver can reset the counter based at least in part on a threshold number of RLC PDU packets (e.g., C RLC PDU packets) (e.g., a number of packet SNs > C) having been received. The threshold (e.g., C) of RLC PDU packets can be configured as an indicator of a maximum length of FEC encoded RLC PDU packets.

[0097] In this way, the receiving party is able to transmit RLC layer feedback for the plurality of RLC PDU packets without having to wait for a polling request from the transmitting party, which reduces processing and memory resources of the transmitting party and radio network resources that would otherwise be consumed in generating and transmitting the polling request. Moreover, the receiving party can include various types of RLC layer feedback in the RLC layer feedback report to assist the transmitting party in determining which FEC packets to retransmit, to assist the transmitting party in determining whether to adjust network coding parameters for subsequent RLC PDU packets, to assist the transmitting party in determining whether to transmit additional RLC PDU packets to enable more robust decoding and forward error correction, and so forth.

[0098] In some aspects, the techniques described Figure 6A and Figure 6B may be extended to be implemented at the PDCP layer in an analogous manner.

[0099] As indicated above, Figure 6A and Figure 6B are provided as one or more examples. Other examples can vary from the examples described Figure 6A and Figure 6B in one or more ways.

[0100] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a receiving party, in accordance with the present disclosure. Example process 700 is an example where the receiving party (e.g., a UE 120, a base station 110, and / or the like) performs operations associated with RLC layer feedback reporting for rateless codes.

[0101] As shown in Figure 7 some aspects, process 700 can include determining that a number of a first plurality of RLC PDU packets received from a transmitting party satisfies a first quantity threshold (block 710). For example, the receiving party (e.g., using transmit processor 200, receive processor 238, controller / processor 240, memory 242, receive processor 258, transmit processor 264, controller / processor 280, memory 282, and / or the like) can determine that a number of a first plurality of RLC PDU packets received from a transmitting party satisfies a first quantity threshold, as described above.

[0102] As shown in Figure 7In some aspects, process 700 can include performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the number of the first plurality of RLC PDU packets satisfies the first quantity threshold (block 720), as further shown in FIG. 7. For example, the receiving side (e.g., using transmit processor 200, receive processor 238, controller / processor 240, memory 242, receive processor 258, transmit processor 264, controller / processor 280, memory 282, and / or the like) can perform a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the number of the first plurality of RLC PDU packets satisfies the first quantity threshold, as described above.

[0103] As Figure 7 In some aspects, process 700 can include transmitting, to the transmitting side, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving the second plurality of RLC PDU packets from the transmitting side, where the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and where the RLC layer feedback report is based at least in part on the decoding attempt (block 730), as further shown in FIG. 7. For example, the receiving side (e.g., using transmit processor 200, receive processor 238, controller / processor 240, memory 242, receive processor 258, transmit processor 264, controller / processor 280, memory 282, and / or the like) can transmit, to the transmitting side, an RLC layer feedback report for the first plurality of RLC PDU packets after receiving the second plurality of RLC PDU packets from the transmitting side, as described above. In some aspects, the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets. In some aspects, the RLC layer feedback report is based at least in part on the decoding attempt.

[0104] Process 700 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0105] In a first aspect, each of the first plurality of RLC PDU packets includes a plurality of FEC encoded packets. In a second aspect, alone or in combination with the first aspect, the plurality of FEC encoded packets included in each of the first plurality of RLC PDU packets are FEC encoded using a rateless network code. In a third aspect, alone or in combination with the first or second aspect, process 700 includes determining that a number of the second plurality of RLC PDU packets satisfies a second quantity threshold, wherein transmitting the RLC layer feedback report includes transmitting, to the transmitting side, the RLC layer feedback report for the first plurality of RLC PUD packets based at least in part on determining that the number of the second plurality of RLC PDU packets satisfies the second quantity threshold.

[0106] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first quantity threshold and the second quantity threshold are indicated in an RLC layer configuration, and the RLC layer configuration is configured at a radio resource control (RRC) layer of the receiver. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the RLC layer feedback report includes information identifying an ACK or a NACK for a RLC PDU group of the first plurality of RLC PDU groups.

[0107] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the RLC layer feedback report includes information identifying a number of RLC PDU groups of the first plurality of RLC PDU groups for which a decoding attempt failed. In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the RLC layer feedback report includes information identifying a number of FEC encoded packets of RLC PDU groups included in the first plurality of RLC PDU groups for which a decoding attempt failed. In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the RLC layer feedback report includes information identifying an index associated with FEC encoded packets of RLC PDU groups included in the first plurality of RLC PDU groups for which a decoding attempt failed.

[0108] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the first quantity threshold and the second quantity threshold are related and configured together. In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the second quantity threshold is based at least in part on the second quantity threshold. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the first quantity threshold is based at least in part on a service data unit size of the first plurality of RLC PDU groups. In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the second quantity threshold is 0 RLC PDU groups.

[0109] Although Figure 7 Example blocks of process 700 are illustrated, but in some aspects, process 700 can include more, fewer, or different blocks than those depicted in FIG. 7. Additionally, or alternatively, two or more of the blocks of process 700 can be performed in parallel. Figure 7 Although

[0110] Figure 8is a diagram illustrating an example process 800 performed, for example, by a receiver, in accordance with aspects of the present disclosure. Example process 800 is an example where the receiver (e.g., UE 120 or base station 110) performs operations associated with RLC layer feedback reporting for rateless codes.

[0111] As Figure 8 As shown in

[0112] As Figure 8 As further shown in

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

[0114] In a first aspect, process 800 includes determining that another RLC PDU packet having another particular packet SN is received from the transmitter, where the other RLC PDU packet is received after the RLC PDU packet, and transmitting, to the transmitter, a RLC layer feedback report for the plurality of RLC PDU packets based at least in part on determining that the other RLC PDU packet having the other particular SN packet is received, where the RLC layer feedback report is based at least in part on the decoding attempt.

[0115] In a second aspect, alone or in combination with the first aspect, process 800 includes determining that a quantity of another plurality of RLC PDU packets received from the transmitter after receiving the plurality of RLC PDU packets satisfies a quantity threshold, and transmitting, to the transmitter, a RLC layer feedback report for the plurality of RLC PDU packets based at least in part on determining that the quantity of the another plurality of RLC PDU packets satisfies the quantity threshold, where the RLC layer feedback report is based at least in part on the decoding attempt. In a third aspect, alone or in combination with one or more of the first or second aspects, process 800 includes transmitting, to the transmitter, the RLC layer feedback report prior to receiving, from the transmitter, a request for the RLC layer feedback report.

[0116] Although Figure 8 Example blocks of process 800 are illustrated, but in some aspects, process 800 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 8. Additionally, or alternatively, two or more blocks of process 800 can be performed in parallel. Figure 8 In a second aspect, alone or in combination with the first aspect, process 800 includes determining that a quantity of another plurality of RLC PDU packets received from the transmitter after receiving the plurality of RLC PDU packets satisfies a quantity threshold, and transmitting, to the transmitter, a RLC layer feedback report for the plurality of RLC PDU packets based at least in part on determining that the quantity of the another plurality of RLC PDU packets satisfies the quantity threshold, where the RLC layer feedback report is based at least in part on the decoding attempt. In a third aspect, alone or in combination with one or more of the first or second aspects, process 800 includes transmitting, to the transmitter, the RLC layer feedback report prior to receiving, from the transmitter, a request for the RLC layer feedback report.

[0117] The following provides an overview of some aspects of the present disclosure:

[0118] Aspect 1 : A method of wireless communication performed by a receiver, comprising: determining that a quantity of a first plurality of radio link layer (RLC) protocol data unit (PDU) packets received from a transmitter satisfies a first quantity threshold; performing a decoding attempt for the first plurality of RLC PDU packets based at least in part on determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; and transmitting, to the transmitter, a RLC layer feedback report for the first plurality of RLC PDU packets after receiving a second plurality of RLC PDU packets from the transmitter, where the second plurality of RLC PDU packets are received after the first plurality of RLC PDU packets, and where the RLC layer feedback report is based at least in part on the decoding attempt.

[0119] Aspect 2: The method of aspect 1, wherein each of the first plurality of RLC PDU packets includes a plurality of forward error correction (FEC) encoded packets.

[0120] Aspect 3: The method of aspect 2, wherein the plurality of FEC encoded packets included in each of the first plurality of RLC PDU packets are FEC encoded using a rateless network code.

[0121] Aspect 4: The method of aspect 1 or 2, further comprising: determining that the number of the second plurality of RLC PDU packets satisfies a second quantity threshold; and wherein transmitting the RLC layer feedback report comprises transmitting the RLC layer feedback report for the first plurality of RLC PDU packets to the transmitting party based at least in part on determining that the number of the second plurality of RLC PDU packets satisfies the second quantity threshold.

[0122] Aspect 5: The method of aspect 4, wherein the first quantity threshold and the second quantity threshold are indicated in a RLC layer configuration; and wherein the RLC layer configuration is configured at a radio resource control (RRC) layer of the receiving party.

[0123] Aspect 6: The method of aspect 5, wherein the first quantity threshold and the second quantity threshold are related and configured together.

[0124] Aspect 7: The method of any of aspects 4-6, wherein the second quantity threshold is based at least in part on the second quantity threshold.

[0125] Aspect 8: The method of any of aspects 4-7, wherein the first quantity threshold is based at least in part on a service data unit size of the first plurality of RLC PDU packets.

[0126] Aspect 9: The method of any of aspects 4-8, wherein the second quantity threshold is 0 RLC PDU packets.

[0127] Aspect 10: The method of any of aspects 1-9, wherein the RLC layer feedback report comprises information identifying an acknowledgement (ACK) or a negative acknowledgement (NACK) for a RLC PDU packet of the first plurality of RLC PDU packets.

[0128] Aspect 11: The method of any of aspects 1-10, wherein the RLC layer feedback report comprises information identifying a number of RLC PDU packets of the first plurality of RLC PDU packets for which a decoding attempt failed.

[0129] Aspect 12: The method of any of aspects 1-11, wherein the RLC layer feedback report comprises information identifying a number of forward error correction (FEC) encoded packets of the RLC PDU packets included in the first plurality of RLC PDU packets for which a decoding attempt failed.

[0130] Aspect 13: The method of any of aspects 1-12, wherein the RLC layer feedback report comprises information identifying an index associated with the forward error correction (FEC) encoded packets of the RLC PDU packets included in the first plurality of RLC PDU packets for which a decoding attempt failed.

[0131] Aspect 14: A method of wireless communication performed by a receiver, comprising: determining that a radio link layer (RLC) protocol data unit (PDU) packet having a particular packet sequence number (SN) is received from a transmitter; and performing a decoding attempt for a plurality of RLC PDU packets received from the transmitter based at least in part on determining that the RLC PDU packet having the particular packet SN is received, wherein the plurality of RLC PDU packets have packet SNs lower than the particular packet SN of the RLC PDU packet.

[0132] Aspect 15: The method of Aspect 14, further comprising: determining that another RLC PDU packet having another particular packet SN is received from the transmitter, wherein the other RLC PDU packet is received after the RLC PDU packet is received, and transmitting a RLC layer feedback report to the transmitter for the plurality of RLC PDU packets based at least in part on determining that the other RLC PDU packet having the other particular SN packet is received, wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0133] Aspect 16: The method of Aspect 14, further comprising: determining that a number of another plurality of RLC PDU packets received from the transmitter after the plurality of RLC PDU packets is received satisfies a number threshold; and transmitting a RLC layer feedback report to the transmitter for the plurality of RLC PDU packets based at least in part on determining that the number of the other plurality of RLC PDU packets satisfies the number threshold, wherein the RLC layer feedback report is based at least in part on the decoding attempt.

[0134] Aspect 17: The method of any one of Aspects 14-16, further comprising: transmitting the RLC layer feedback report to the transmitter prior to receiving a request for the RLC layer feedback report from the transmitter.

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

[0136] Aspect 19: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-13.

[0137] Aspect 20: A device for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-13.

[0138] Aspect 21 : A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more Aspects of Aspects 1-13.

[0139] Aspect 22: A non-transitory computer-readable medium storing a set of instructions for wireless communication that, when executed by one or more processors of a device, cause the device to perform the method of one or more Aspects of Aspects 1-13.

[0140] Aspect 22: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more Aspects of Aspects 14-17.

[0141] Aspect 23: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more Aspects of Aspects 14-17.

[0142] Aspect 24: A device for wireless communication comprising at least one means for performing the method of one or more Aspects of Aspects 14-17.

[0143] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more Aspects of Aspects 14-17.

[0144] Aspect 26: A non-transitory computer-readable medium storing a set of instructions for wireless communication that, when executed by one or more processors of a device, cause the device to perform the method of one or more Aspects of Aspects 14-17.

[0145] The foregoing disclosure provides explanation and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made in light of the above disclosure or can be acquired from practice of the aspects.

[0146] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0147] As used herein, depending on the context, satisfying a threshold can refer to being greater than the threshold, being greater than or equal to the threshold, being less than the threshold, being less than or equal to the threshold, being equal to the threshold, not being equal to the threshold, and / or the like.

[0148] 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 various aspects. In fact, many combinations of features can be assumed unless they are specifically excluded in the claims or disclosure. Although each dependent claim below can directly depend on only one claim, the disclosure of each aspect includes each dependent claim in combination with every other claim in the set. As used in this document, the phrase "at least one of" followed by a list of two or more items means any combination of those items, including single members. As an example, "at least one of a, b, or c" means 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, c-c, and c-c-c or any other ordering of a, b, and c).

[0149] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items, and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and can be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., in an exhaustive list of options).

Claims

1. A method of wireless communication performed by a receiver, comprising: determining that a quantity of a first plurality of radio link control (RLC) layer protocol data unit (PDU) packets received from a transmitter satisfies a first quantity threshold; performing a decoding attempt for the first plurality of RLC PDU packets in response to determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; receiving a second plurality of RLC PDU packets after the first plurality of RLC PDU packets; determining that a quantity of the second plurality of RLC PDU packets satisfies a second quantity threshold; and transmitting, to the transmitter, an RLC layer feedback report for the first plurality of RLC PDU packets in response to determining that the quantity of the second plurality of RLC PDU packets satisfies the second quantity threshold, wherein the RLC layer feedback report is based at least in part on the decoding attempt.

2. The method of claim 1, wherein each of the first plurality of RLC PDU packets includes a plurality of forward error correction (FEC) encoded packets.

3. The method of claim 2, wherein the plurality of FEC encoded packets included in each of the first plurality of RLC PDU packets are FEC encoded using a rateless network code.

4. The method of claim 1, wherein the first quantity threshold and the second quantity threshold are indicated in an RLC layer configuration; and wherein the RLC layer configuration is configured at a radio resource control (RRC) layer of the receiver.

5. The method of claim 1, wherein the first quantity threshold and the second quantity threshold are related and configured together.

6. The method of claim 1, wherein the first quantity threshold is based at least in part on a service data unit size of the first plurality of RLC PDU packets.

7. The method of claim 1, wherein the second quantity threshold is 0 RLC PDU packets.

8. The method of claim 1, wherein the RLC layer feedback report includes information identifying an acknowledgement (ACK) or negative acknowledgement (NACK) for a RLC PDU packet of the first plurality of RLC PDU packets.

9. The method of claim 1, wherein the RLC layer feedback report includes information identifying a quantity of RLC PDU packets of the first plurality of RLC PDU packets for which the decoding attempt failed.

10. The method of claim 1, wherein the RLC layer feedback report includes information identifying a quantity of forward error correction (FEC) encoded packets of RLC PDU packets included in the first plurality of RLC PDU packets for which the decoding attempt failed.

11. The method of claim 1, wherein the RLC layer feedback report includes information identifying an index associated with a forward error correction (FEC) encoded packet of RLC PDU packets included in the first plurality of RLC PDU packets for which the decoding attempt failed. ​ 12. An apparatus for wireless communication, comprising: means for determining that a quantity of a first plurality of radio link control (RLC) layer protocol data unit (PDU) packets received from a transmitting party satisfies a first quantity threshold; means for performing a decoding attempt for the first plurality of RLC PDU packets in response to determining that the quantity of the first plurality of RLC PDU packets satisfies the first quantity threshold; means for receiving a second plurality of RLC PDU packets after the first plurality of RLC PDU packets; means for determining that a quantity of the second plurality of RLC PDU packets satisfies a second quantity threshold; and means for transmitting, to the transmitting party, an RLC layer feedback report for the first plurality of RLC PDU packets in response to determining that the quantity of the second plurality of RLC PDU packets satisfies the second quantity threshold, wherein the RLC layer feedback report is based at least in part on the decoding attempt.

13. The apparatus of claim 12, wherein each of the first plurality of RLC PDU packets includes a plurality of forward error correction (FEC) encoded packets.

14. The apparatus of claim 13, wherein the plurality of FEC encoded packets included in each of the first plurality of RLC PDU packets are FEC encoded using a rateless network code.

15. The apparatus of claim 12, wherein the first quantity threshold and the second quantity threshold are indicated in an RLC layer configuration; and wherein the RLC layer configuration is configured at a radio resource control (RRC) layer of a receiving party.

16. The apparatus of claim 12, wherein the first quantity threshold and the second quantity threshold are related and configured together.

17. The apparatus of claim 12, wherein the first quantity threshold is based at least in part on a service data unit size of the first plurality of RLC PDU packets.

18. The apparatus of claim 12, wherein the second quantity threshold is 0 RLC PDU packets.

19. The apparatus of claim 12, wherein the RLC layer feedback report includes information identifying an acknowledgement (ACK) or negative acknowledgement (NACK) for a RLC PDU packet of the first plurality of RLC PDU packets.

20. The apparatus of claim 12, wherein the RLC layer feedback report includes information identifying a quantity of RLC PDU packets of the first plurality of RLC PDU packets for which the decoding attempt failed.

21. The apparatus of claim 12, wherein the RLC layer feedback report includes information identifying a quantity of forward error correction (FEC) encoded packets in a RLC PDU packet included in the first plurality of RLC PDU packets for which the decoding attempt failed. ​ 22. The device of claim 12, wherein the RLC layer feedback report includes information identifying an index associated with a forward error correction (FEC) encoded packet in a RLC PDU packet included in the first plurality of RLC PDU packets for which the decoding attempt failed.

Images