Indication scheme for rateless code transmission without feedback information

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive downlink control information (DCI) including a grant to schedule a data transmission for the UE, the data transmission being associated with a rateless coding scheme. The UE may determine to disable feedback information for the data transmission based at least in part on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The UE may perform or monitor the data transmission based on the DCI and the rateless coding scheme. The UE may perform or monitor the feedback information for the data transmission based on the determination.

Description

Technical Field

[0001] The following relates to wireless communications, including an indication scheme for rateless code transmission without feedback information. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiple access (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication of multiple communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting indication schemes for rateless code transmissions without feedback information. Generally, the described techniques provide various mechanisms for using signaling to indicate whether a data transmission utilizing a rateless coding scheme is configured without feedback information, such as hybrid automatic repeat / request (HARQ) feedback information. For example, a base station may send a downlink control information (DCI) grant to a user equipment (UE) that schedules a data transmission (e.g., a physical downlink shared channel (PDSCH) transmission and / or a physical uplink shared channel (PUSCH) transmission). At least in some aspects, the DCI may also indicate whether the data transmission utilizes HARQ. For example, a dedicated radio network temporary identifier (RNTI) may be used to scramble at least a portion of the DCI to indicate a HARQ scheme (e.g., whether HARQ is disabled for rateless coded data transmission). New and / or modified DCI fields may be used to indicate the HARQ scheme, wherein the control resource set (CORESET) / search space (SS) set in which the DCI is transmitted may indicate the HARQ scheme, the signaling of semi-persistent scheduling (SPS) resources (e.g., for downlink data transmission) and / or configured grant (CG) resources (e.g., for uplink data transmission) configured for data transmission may indicate the HARQ scheme, and / or the HARQ process number indicated in the DCI may indicate the HARQ scheme. Thus, the UE and the base station may perform / monitor the data transmission (e.g., depending on whether the data transmission is an uplink transmission or a downlink transmission). The UE and the base station may then perform / monitor feedback information for the data transmission based on the determination of whether HARQ is enabled or disabled for the data transmission. For example, feedback information may be sent for non-rateless coded data transmission when HARQ is enabled, or feedback information may not be sent for rateless coded data transmission when HARQ is disabled.

[0004] A method of wireless communication at a UE is described. The method may include receiving DCI including a grant to schedule data transmission for the UE, the data transmission being associated with a rateless coding scheme; determining to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive a data transmission (DCI) including a grant to schedule a data transmission for the UE, the data transmission being associated with a rateless coding scheme; determine to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include means for: receiving DCI including a grant to schedule data transmission for the UE, the data transmission associated with a rateless coding scheme; determining to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive DCI including a grant to schedule a data transmission for the UE, the data transmission associated with a rateless coding scheme; determine to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination.

[0008] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a radio network temporary identifier for scrambling a cyclic redundancy check portion of a DCI, and determining to disable feedback information for data transmission based on the radio network temporary identifier.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining to disable feedback information for data transmission based on a field indicated in a DCI.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the fields include one or more bits associated with a rateless coding scheme configured for a UE with no feedback information, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a HARQ process number, or a combination thereof.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving DCI in a first portion of resources associated with the DCI or a second portion of resources associated with the DCI, and determining to disable feedback information for data transmission based on the DCI received in the first portion of resources or the second portion of resources.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, resources associated with the DCI include a control resource set, a search space set, or both.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a radio resource control configuration indicating a semi-persistent scheduling configuration associated with a data transmission, and determining to disable feedback information for the data transmission based on the radio resource control configuration.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the radio resource control configuration includes a semi-persistent scheduling configuration indication, a configured grant configuration indication, or both.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a HARQ process number indicated in a DCI, and determining to disable feedback information for data transmission based on the HARQ process number.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first set of HARQ process numbers indicates that feedback information can be disabled for data transmission, and a second set of HARQ process numbers indicates that feedback information can be enabled for data transmission using a non-rateless coding scheme.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled, wherein the DCI is based at least in part on the UE capability message.

[0018] A method of wireless communication at a base station is described. The method may include: determining to disable feedback information for a data transmission with a UE, the data transmission being associated with a rateless coding scheme; transmitting DCI including a grant to schedule a data transmission, the feedback information for the data transmission being disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0019] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: determine to disable feedback information for a data transmission with a UE, the data transmission being associated with a rateless coding scheme; transmit a DCI including a grant to schedule a data transmission, the feedback information for the data transmission being disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination.

[0020] Another apparatus for wireless communication at a base station is described. The apparatus may include means for: determining to disable feedback information for a data transmission with a UE, the data transmission being associated with a rateless coding scheme; transmitting DCI including a grant to schedule a data transmission, the feedback information for the data transmission being disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0021] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: determine to disable feedback information for a data transmission with a UE, the data transmission being associated with a rateless coding scheme; transmit DCI including a grant to schedule a data transmission, the feedback information for the data transmission being disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for scrambling a cyclic redundancy check portion of a DCI using a radio network temporary identifier that may be based on determining to disable feedback information for data transmission.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for configuring a field in a DCI to indicate disabling of feedback information for data transmission.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the fields include one or more bits associated with a rate-less coding scheme configured for a UE with no feedback information, a modulation and coding scheme field, a new data indication, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indication, a physical downlink shared channel to feedback information timing indication field, a HARQ process number, or a combination thereof.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending DCI in a first portion of resources associated with the DCI or a second portion of resources associated with the DCI, wherein sending the DCI in the first portion or the second portion indicates disabling feedback information for data transmission.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, resources associated with the DCI include a control resource set, a search space set, or both.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a radio resource control configuration indicating a semi-persistent scheduling configuration associated with a data transmission, wherein the radio resource control configuration indicates disabling of feedback information for the data transmission based on the radio resource control configuration.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the radio resource control configuration includes a semi-persistent scheduling configuration indication, a configured grant configuration indication, or both.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a HARQ process number indicated in a DCI that indicates disabling of feedback information for data transmission.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first set of HARQ process numbers indicates that feedback information may be disabled for data transmission using a rateless coding scheme, and a second set of HARQ process numbers indicates that feedback information may be enabled for data transmission using a non-rateless coding scheme.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled, wherein the DCI is based at least in part on the UE capability message. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An example of a wireless communication system supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure is illustrated.

[0033] Figure 2 An example of a wireless communication system supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure is illustrated.

[0034] Figure 3 Illustrated are examples of downlink control information configurations supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure.

[0035] Figure 4A and Figure 4B Illustrated are example procedures for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure.

[0036] Figure 5 Illustrated are examples of processes supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure.

[0037] Figure 6 and Figure 7 A block diagram of a device supporting an indication scheme for rateless code transmission without feedback information is shown in accordance with aspects of the present disclosure.

[0038] Figure 8 A block diagram of a communication manager supporting an indication scheme for rateless code transmission without feedback information is shown, in accordance with aspects of the present disclosure.

[0039] Figure 9 A diagram is shown of a system including devices supporting an indication scheme for rateless code transmission without feedback information, in accordance with aspects of the present disclosure.

[0040] Figure 10 and Figure 11 A block diagram of a device supporting an indication scheme for rateless code transmission without feedback information is shown in accordance with aspects of the present disclosure.

[0041] Figure 12 A block diagram of a communication manager supporting an indication scheme for rateless code transmission without feedback information is shown, in accordance with aspects of the present disclosure.

[0042] Figure 13 A diagram is shown of a system including devices supporting an indication scheme for rateless code transmission without feedback information, in accordance with aspects of the present disclosure.

[0043] Figures 14 to 18 A flow chart illustrating a method of supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0044] Some wireless communication systems may use rateless coding (such as Raptor codes or other fountain codes) for physical downlink shared channel (PDSCH) and / or physical uplink shared channel (PUSCH) data transmission. For example, the rateless coding scheme may be based on the type of service / message being transmitted (e.g., control plane data, user plane data, etc.). The rateless coding scheme is considered rateless because, as long as the number of received packets is slightly greater than the number of source packets, the transmitted packets can be recovered at the receiver, regardless of which packets were received. Due to the nature of this rateless coding scheme, feedback information, such as hybrid automatic repeat / request (HARQ) acknowledgment information, may not be necessary in some cases. However, some wireless communication systems may not provide a mechanism by which a downlink control information (DCI) grant scheduling a data transmission may indicate that a data transmission using the rateless coding scheme will not utilize feedback information (e.g., hybrid automatic repeat / request (HARQ) feedback information). Since the use of HARQ feedback information cannot be switched, this may mean that HARQ feedback information is used for all data transmissions, which may be an inefficient use of resources when data transmission is performed using a rateless coding scheme.

[0045] Various aspects of the present disclosure are initially described in the context of wireless communication systems. In general, the described techniques provide various mechanisms to signal that data transmissions utilizing a rateless coding scheme are not configured with feedback information, such as HARQ feedback information. For example, a base station may send a DCI grant to a user equipment (UE) that schedules data transmission (e.g., a PDSCH transmission and / or a PUSCH transmission). At least in some aspects, the DCI may also indicate whether the data transmission uses HARQ. For example, a dedicated radio network temporary identifier (RNTI) may be used to scramble at least a portion of the DCI to indicate the HARQ scheme (e.g., disabling HARQ for data transmissions utilizing rateless coding), new and / or modified DCI fields may be used to indicate the HARQ scheme, wherein the control resource set (CORESET) / search space (SS) set in which the DCI is transmitted may indicate the HARQ scheme, signaling of semi-persistent scheduling (SPS) resources (e.g., for downlink data transmission) and / or configured grant (CG) resources (e.g., for uplink data transmission) configured for data transmission may indicate the HARQ scheme, and / or the HARQ process number indicated in the DCI may indicate the HARQ scheme. Thus, the UE and the base station may perform / monitor data transmission (e.g., depending on whether the data transmission is an uplink transmission or a downlink transmission). The UE and the base station may then perform / monitor feedback information for the data transmission based on a determination of whether HARQ is enabled or disabled for the data transmission. For example, feedback information may be sent for data transmission using non-rateless coding when HARQ is enabled, or feedback information may not be sent for data transmission using rateless coding when HARQ is disabled.

[0046] Aspects of the present disclosure are further illustrated by and described in conjunction with apparatus diagrams, system diagrams, and flow diagrams relating to indication schemes for rateless code transmission without feedback information.

[0047] Figure 1 An example of a wireless communication system 100 supporting an indication scheme for rateless code transmission without feedback information in accordance with various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In certain examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof, among others.

[0048] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100 and may be devices of different forms or capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base stations 105 and UEs 115 may support communication of signals according to one or more radio access technologies.

[0049] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be fixed or mobile, or fixed or mobile at different times. The UEs 115 may be devices of different forms or with different capabilities. Figure 1 1. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relays, integrated access and backhaul (IAB) nodes, or other network devices), such as Figure 1 shown.

[0050] Base stations 105 can communicate with core network 130, with each other, or both. For example, base stations 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 can communicate with each other via backhaul links 120 (e.g., via X2, Xn, or other interfaces) directly (e.g., directly between base stations 105), indirectly (e.g., via core network 130), or both. In some examples, backhaul links 120 can be or include one or more wireless links.

[0051] One or more of the base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga-NodeB (any of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.

[0052] In other examples, UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client. UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various objects, such as in appliances, vehicles, meters, and other examples.

[0053] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network devices including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, as shown. Figure 1 shown.

[0054] The UE 115 and the base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a collection of radio spectrum resources with a defined physical layer structure for supporting the communication link 125. For example, a carrier used for the communication link 125 can include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate operations for the carrier, user data, or other signaling. The wireless communication system 100 can use carrier aggregation or multi-carrier operation to support communication with the UE 115. The UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers according to the carrier aggregation configuration. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0055] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, where initial acquisition and connection may be performed by a UE 115 via the carrier, or in a non-standalone mode, where a connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0056] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0057] A carrier can be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth can be one of a plurality of determined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). The devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) can have a hardware configuration that supports communication on a particular carrier bandwidth, or can be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0058] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM technology, a resource element may include one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are anti-correlated. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate of the UE 115 may be. Wireless communication resources may refer to a combination of radio spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with the UE 115.

[0059] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for the UE 115 may be restricted to the one or more active BWPs.

[0060] The time interval of the base station 105 or the UE 115 may be expressed as a multiple of a basic time unit, for example, the basic time unit may be T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0061] Each frame can include multiple consecutively numbered subframes or time slots, and each subframe or time slot can have the same duration. In some examples, the frame can be divided (e.g., in the time domain) into subframes, and each subframe can be further divided into multiple time slots. Alternatively, each frame can include a variable number of time slots, and the number of time slots can depend on the subcarrier spacing. Each time slot can include multiple periods (e.g., depending on the length of the cyclic prefix that precedes each symbol period). In some wireless communication systems 100, the time slot can be further divided into multiple mini-time slots containing one or more symbols. In addition to the cyclic prefix, each symbol period can contain one or more (e.g., N f ) sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0062] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0063] Physical channels can be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels can be multiplexed on a downlink carrier using one or more of a TDM technique, an FDM technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel can be defined by a number of symbol periods and can extend across the system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search the control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. A search space set can include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115.

[0064] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots or other types of cells, or various combinations thereof). The term "cell" can refer to a logical communication entity used to communicate with the base station 105 (e.g., via a carrier) and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish neighboring cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the base station 105, these cells can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping the geographic coverage area 110, etc.

[0065] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Small cells may be associated with base stations 105 that are lower in power than macro cells, and may operate in the same or different frequency bands (e.g., licensed, unlicensed) as the macro cells. Small cells may provide unrestricted access to UEs 115 through a service subscription with a network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office, etc.). A base station 105 may support one or more cells and may also support communications over one or more cells using one or more component carriers.

[0066] In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that can provide access to different types of devices.

[0067] In some examples, base stations 105 can be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0068] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, the base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, the base stations 105 can have different frame timing, and in some examples, transmissions from different base stations 105 can be misaligned in time. The techniques described herein can be used for either synchronous or asynchronous operation.

[0069] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that incorporate sensors or meters to measure or capture information and forward such information to a central server or application that utilizes the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security awareness, physical access control, and transaction-based service charging.

[0070] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or RBs) within a carrier, within a guard band of a carrier, or outside a carrier.

[0071] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0072] In some examples, UE 115 can also communicate directly with other UEs 115 via device-to-device (D2D) communication links 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UEs 115 in the group can be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, a group of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates scheduling resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0073] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) or communicate with the network using vehicle-to-network (V2N) communication via one or more network nodes (e.g., base station 105), or both.

[0074] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entities may manage non-access stratum (NAS) functions associated with the core network 130, such as mobility, authentication, and bearer management, for the UEs 115 served by the base stations 105. User IP packets may be delivered through the user plane entities, which may provide IP address allocation and other functions. The user plane entities may connect to the network operator's IP services 150. The network operator IP services 150 may include access to the internet, an intranet, an IP multimedia subsystem (IMS), or packet-switched streaming services.

[0075] Some network devices, such as base stations 105, may include subcomponents such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with a UE 115 through one or more other access network transmit entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transmit entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., base station 105).

[0076] The wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, however, the waves may be sufficient to penetrate structures for macro cells to provide service to UEs 115 located indoors. Transmissions using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using the lower frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0077] The wireless communication system 100 may also operate in the super high frequency (SHF) region (also known as the centimeter band) using a frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices may be smaller and more closely spaced than the UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory agency.

[0078] The wireless communication system 100 can utilize both licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 can use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as the base station 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in the unlicensed frequency band can be based on a carrier aggregation configuration (e.g., LAA) in combination with component carriers operating in the licensed band. Operations in the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0079] The base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0080] The base station 105 or the UE 115 can use MIMO communication to take advantage of multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0081] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to form or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals transmitted via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other direction).

[0082] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different sets of beamforming weights associated with different transmit directions. Transmissions in different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the base station 105, or by a receiving device such as the UE 115) for later transmission or reception by the base station 105.

[0083] Some signals, such as data signals associated with a particular receiving device, may be transmitted by base station 105 in a single beam direction (e.g., a direction associated with a receiving device such as UE 115). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0084] In some examples, transmission by a device (e.g., by a base station 105 or a UE 115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or radio frequency beamforming to produce a combined beam for transmission (e.g., from the base station 105 to the UE 115). The UE 115 can report feedback indicating precoding weights for one or more beam directions, and the feedback can correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 can transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that can be precoded or unprecoded. The UE 115 can provide feedback for beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals sent by base station 105 in one or more directions, UE 115 may use similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to send signals in a single direction (e.g., to send data to a receiving device).

[0085] When receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from the base station 105, a receiving device (e.g., UE 115) can try multiple receive configurations (e.g., directional listening). For example, the receiving device can try multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device can receive along a single beam direction using a single receive configuration (e.g., when receiving data signals). The single receive configuration can be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., the beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0086] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer can be based on IP. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate on the logical channel. The media access control (MAC) layer can perform priority processing and multiplex the logical channel into the transport channel. The MAC layer can also use error detection technology, error correction technology or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection (which supports radio bearers for user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, the transport channel can be mapped to the physical channel.

[0087] UE 115 and base station 105 can support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique that increases the likelihood of correctly receiving data over communication link 125. HARQ can include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device can support same-slot HARQ feedback, wherein the device can provide HARQ feedback in a particular time slot for data received in a previous symbol in the time slot. In other cases, the device can provide HARQ feedback in a subsequent time slot or according to some other time intervals.

[0088] UE 115 may receive DCI that includes a grant scheduling a data transmission for UE 115, the data transmission being associated with a rateless coding scheme. UE 115 may determine to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. UE 115 may perform or monitor the data transmission based on the DCI and the rateless coding scheme. UE 115 may perform or monitor the feedback information based on the determination to perform the data transmission.

[0089] Base station 105 may determine to disable feedback information for a data transmission with UE 115, the data transmission being associated with a rateless coding scheme. Base station 105 may transmit a DCI including a grant scheduling a data transmission, wherein feedback information for the data transmission is enabled or disabled based at least in part on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. Base station 105 may perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme. Base station 105 may perform or monitor the feedback information for the data transmission in accordance with the determination.

[0090] It should be understood that the techniques described herein can be applied by a UE 115 and / or a base station 105. For example, aspects of the described techniques can be applied by a UE 115 and a base station 105 in a downlink scenario, wherein the base station 105 configures and performs data transmission to the UE 115. In such a downlink scenario, the base station 105 can determine that HARQ will be disabled for the data transmission using rateless coding and signal this to the UE 115. Aspects of the described techniques can also be applied by a UE 115 and a base station 105 in an uplink scenario, wherein the UE 115 configures and performs (at least to some extent) data transmission to the base station 105. In such an uplink scenario, the UE 115 can determine that HARQ will be disabled for the data transmission using rateless coding and signal this to the base station 105. Thus, while the examples discussed herein generally refer to downlink examples in which the base station 105 configures and performs data transmission and a corresponding HARQ scheme, it should be understood that these techniques can also be applied by the UE 115 during uplink scenarios.

[0091] Figure 2 An example of a wireless communication system 200 that supports an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. Various aspects of the described techniques can be implemented at or by a base station 205 and / or a UE 210, which can be examples of corresponding devices described herein.

[0092] In some aspects, base station 205 may be configured as or otherwise act as a transmitting device that performs a data transmission (e.g., a downlink transmission) to UE 210, in which case UE 210 may be configured as or otherwise act as a receiving device. However, it should be understood that UE 210 may implement various aspects of the described techniques when acting as or otherwise configured as a transmitting device that performs a data transmission (e.g., an uplink transmission) to base station 205, in which case base station 205 would be configured as or otherwise act as a receiving device. In some examples, such wireless transmissions may be performed by base station 205 to another base station and / or by UE 210 to another UE. However, various aspects of the described techniques are not limited to downlink transmission scenarios and may be equally applicable to uplink transmission scenarios.

[0093] The wireless communication system 200 can utilize fountain codes, which are rateless codes because the number of encoded packets to be transmitted is potentially infinite. For example, as long as the number of received packets is slightly greater than the number of source packets (regardless of which packets are received and successfully decoded), the transmitted packets can be recovered at the receiving side. Examples of such rateless codes include Luby transform (LT) codes, raptor codes (an enhanced code based on a variant of low-density parity check (LDPC) and LT codes), and the like.

[0094] Fountain codes are also called network codes because they are applied at the network / application layer (e.g., for MBMS, IAB, etc.). On the receiving side, each encoded symbol is either correctly decoded or discarded (e.g., the encoded data packet sent during the symbol). This approach allows the block number (e.g., source block number (SBN)) and / or symbol identifier (e.g., electronic symbol identifier (ESI)) associated with the packet to be added as a header to the encoded symbol. The SBN typically corresponds to the integer identifier of the source block (e.g., the column of the original generator matrix) to which the encoded symbol within the packet refers. The ESI typically corresponds to the integer identifier of the encoded symbol within the packet. Each encoded data packet can include the SBN (e.g., the first 16 bits), the ESI (e.g., the last 16 bits), and the encoded symbol. Based on the SBN and ESI, the transmitting and receiving devices can determine which source symbols (e.g., which column of the original generator matrix) to select to generate the encoded symbol.

[0095] Therefore, fountain codes are rate-free codes that have an infinite number of columns in the original generator matrix generated by the transmitting device. For example, the transmitting device may have K symbols for transmission to the receiving device. Therefore, the original generator matrix may be generated with K rows (corresponding to K symbols), and because fountain codes are rate-free codes, a potentially infinite number of columns may be generated. The number of packets transmitted may correspond to the following formula:

[0096]

[0097] For conventional ARQ schemes, the original generator matrix may start from the identity matrix.

[0098] The recovered data packet (eg, received data packet) may correspond to the following formula:

[0099]

[0100] According to whether the received data packet is reversible or the rank of G′ is K, the condition or scenario for the receiving device to recover the data packet may include G′. The design rule of the original generator matrix is: G′ is reversible and the minimum is N.

[0101] Compared with LT codes, an efficient method can be used to realize the function of fountain codes. For example, the encoding process of each coded symbol may include the sending device randomly selecting a degree d from the degree distribution. i and randomly select d with uniform distribution i different source symbols and perform an exclusive OR (XOR) operation on them.

[0102] At the receiving device, the decoding process may include belief propagation techniques, Gaussian elimination processes, etc. For example, the receiving device may find that the source symbol t is connected to only one source symbol t j The coding symbol S i The receiving device can i Set to t j 、XORS i Set up to connect to S i All encoding symbols of , and remove the connection to the source symbol S i The receiving device can repeat this operation until all S i If there is no encoded symbol connected to only one source symbol, the decoding process fails.

[0103] Raptor codes generally reduce the encoding and decoding complexity of LT codes by reducing the average degree (for example, LDPC plus a weak LT code with a small average degree (such as three)). The precoding process may include generating some redundant symbols, for example, S LDPC symbols (each source symbol will appear three times in all LDPC symbols) and H half symbols (each coded symbol contains an upper limit (H / 2) of the source symbols). The encoding process of each coded symbol may include randomly selecting a degree d from the degree distribution. i , for example, you can choose d i The number of redundant symbols can be based on the first K intermediate symbols.

[0104] The data partitioning and encoding process can be based on different layers of the protocol stack of the sending device. For example, N d data bits. N d bits can be divided into N bits per packet b packets (e.g., S0, S1, S3, ..., S l-2 ,S l-1 Each of N b -bit packets). In the RLC layer, erasure codes (such as fountain codes / rateless coding) can be used to encode across l packets to generate a stream of L encoded packets (e.g., P0, P1, P2, P3, ..., P L-1At the MAC / physical layer, each data packet can be composed of N S symbols (for example, each data packet P may include X0, X1, X2, ..., X Ns-1 Each information symbol may include Q bits (eg, N b ≤N s Q).

[0105] Such rateless coding techniques may be configured to have no feedback information (e.g., no HARQ feedback for the corresponding data transmission). Feedback information for data transmission using rateless coding may be configurable for the UE (e.g., in a downlink scenario) and / or the base station (e.g., in an uplink scenario). Feedback information for data transmission may be based, at least in some aspects, on a service / message type (e.g., based on the service / message type of the data transmission). As a non-limiting example, control plane data transmission using non-rateless coding (e.g., such as RRC signaling) may be configured with feedback information enabled, while user plane data transmission using rateless coding (e.g., such as a delay-tolerant service) may be configured with feedback information disabled. However, wireless communication systems typically do not provide a mechanism to signal or otherwise indicate whether feedback information (e.g., HARQ feedback) for data transmission using rateless coding is disabled.

[0106] Thus, aspects of the described techniques provide various mechanisms that can be used to signal or otherwise convey (e.g., explicitly and / or implicitly) an indication that feedback information is disabled for data transmission using rateless coding and / or enabled for data transmission using non-rateless coding. Figure 2An example downlink scenario is illustrated in which a base station 205 sends a DCI 215 to a UE 210 scheduling a data transmission 220 that utilizes a rateless coding scheme. In some aspects, the UE 210 may determine, at least in some aspects based on the DCI 215, that feedback information (e.g., HARQ feedback information) for the data transmission 220 is disabled. When feedback information is enabled, the UE 210 may attempt to receive and decode a data transmission that utilizes non-rateless coding (e.g., in the example where the data transmission 220 utilizes non-rateless coding) and, based on the results, send feedback information 225 to the base station 205. For example, the feedback information 225 may include acknowledgement (ACK) information for the non-rateless coded data transmission when the UE 210 is able to successfully receive and decode the data transmission, or negative acknowledgement (NACK) information if the UE 210 is unable to successfully receive and decode the data transmission. When disabled, UE 210 may attempt to receive and decode data transmissions 220 using rateless coding, but may not send ACK / NACK information for data transmissions 220 (eg, performing or monitoring feedback information 225 may include UE 210 refraining from sending feedback information 225).

[0107] As previously described, the UE 210 can determine, based at least in part on the DCI 215, that feedback information 225 (e.g., HARQ information, such as ACK / NACK information) is disabled for data transmission 220 using rateless coding. More specifically, the base station 205 can select or otherwise determine to disable feedback information 225 for data transmission 220 using rateless coding. Thus, the base station 205 can utilize various aspects of the described techniques to send or otherwise communicate an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. The DCI 215 can be used, at least in part, by the base station 205 to send or otherwise communicate such an indication. For example, a dedicated RNTI may be used to scramble the DCI 215, new fields may be added and / or existing fields of the DCI 215 to be used may be modified / repurposed, a CORESET / SS set may be used to convey the DCI 215 (e.g., a separate CORESET and / or SS set may be configured for rateless coded data transmission without HARQ), RRC configuration signaling may be used to configure the SPS / CG resources activated by the DCI 215 for data transmission 220, a HARQ process number indicated in the DCI 215 may be used to convey such an indication, etc.

[0108] More specifically, in one example, UE 210 can determine that feedback information 225 is disabled based on a dedicated RNTI used by base station 205 to scramble the CRC portion of DCI 215. That is, when feedback information 225 is disabled, one or more RNTIs can be set aside or otherwise associated with data transmissions using rateless coding. Base station 205 selecting a specific or dedicated RNTI to scramble the CRC portion of DCI 215 can carry or otherwise communicate an indication that data transmission 220 using rateless coding is not configured with feedback information 225. In a non-limiting example, if a dedicated RNTI is blindly detected by UE 210, it can indicate that there is no rateless code for HARQ (e.g., feedback information 225 is disabled for data transmission 220). The dedicated RNTI can be used to scramble other portions, or in some examples, all of DCI 215. Thus, UE 210 can determine to disable feedback information 225 for data transmissions 220 using rateless coding based on the RNTI.

[0109] In another example, one or more fields carried or otherwise communicated in the DCI 215 may be used to indicate that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, a new field having one or more bits may be added to the DCI 215 to indicate to the UE 210 that a rateless code without HARQ is configured for data transmission 220. In other words, the one or more bits communicated in the DCI 215 may be associated with configuring a rateless coding scheme for the UE 210 in the absence of feedback information 225.

[0110] Additionally or alternatively, an existing field in the DCI 215 can be used to carry or otherwise convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, the MCS field can be used to convey the indication (e.g., the MCS field can include five bits, which can be configured as 0 bits if the MCS is not changed, wherein the UE 210 can reuse the previously configured MCS). In another example, a new data indicator (NDI) can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, the NDI field can be configured as 0 bits for a rateless code transmission scheme without HARQ (e.g., feedback information 225 is disabled) or as 1 bit for a non-rateless code transmission scheme with HARQ (e.g., feedback information 225 is enabled when the data transmission 220 uses non-rateless coding).

[0111] In another example, a Redundancy Version (RV) field of the DCI 215 can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, the RV field can be configured as a 0 bit for a rateless code transmission scheme without HARQ (e.g., feedback information 225 is disabled) or as a 1 bit for a non-rateless code transmission scheme with HARQ (e.g., feedback information 225 is enabled when data transmission 220 uses non-rateless coding). In another example, a Downlink Allocation Index (DAI) field of the DCI 215 can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. That is, the DAI field of the DCI 215 can include one or more bits used as a counter DAI (e.g., the DAI field can be set to a first value to indicate that feedback information 225 is enabled for non-rateless code data transmission, or set to a second value to indicate that feedback information 225 is disabled for data transmission 220 using rateless coding).

[0112] In another example, a transmit power control (TPC) field / command of the DCI 215 can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. The TPC command can be used for scheduled PUCCH resources, such as uplink resources used to transmit or otherwise convey feedback information 225. In one example, if no PUCCH is scheduled, the TPC command can be configured with a 0 bit, which can indicate that feedback information 225 is disabled for data transmission 220 using rateless coding. Conversely, if PUCCH is scheduled, the TPC command can be configured with a 1 bit, which can indicate that feedback information 225 is enabled for data transmission using non-rateless coding.

[0113] In another example, a PUCCH resource indicator of the DCI 215 can be used to convey an indication that feedback information 225 is enabled or disabled for data transmission 220 using rateless coding. For example, the PUCCH resource indicator can include three bits, and if no PUCCH is scheduled (e.g., if feedback information 225 is disabled for data transmission 220 using rateless coding), these bits can be configured as zero bits. In another example, a PDSCH to HARQ feedback timing indicator of the DCI 215 can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, the PDSCH to HARQ feedback timing indicator can include three bits, and if no HARQ feedback is scheduled (e.g., if feedback information 225 is disabled for data transmission 220 using rateless coding), these bits can be configured as zero bits.

[0114] In some examples, DCI 215 can be a downlink grant (e.g., DCI format 1_*) or an uplink grant (e.g., DCI format 0_*). Aspects of the described techniques can be applicable to either scenario (e.g., to either DCI format). For example, a new field can be added to an uplink grant (e.g., DCI format 0_*) to indicate to UE 210 that data transmission 220 is configured with feedback information 225 that data transmission using rateless coding is disabled. Similarly, one or more existing fields in the uplink grant can also be used to convey the indication, such as the MCS field, the NDI field, and the RV field.

[0115] In another example, the control channel resources (e.g., CORESET and / or SS set) associated with the DCI 215 can convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. For example, the UE 210 can be configured with one or more CORESETs and / or SS sets in which to monitor the DCI 215. If the DCI 215 is sent in the first portion of the control channel resources (e.g., a specific CORESET and / or SS set), then this can convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. Thus, the base station 205 can use RRC signaling messages to configure UE-specific SS sets and / or CORESETs, which can be divided into two or more parts / portions. If the DCI 215 is sent in the first portion / portion, then a conventional transmission scheme can be configured (e.g., feedback information 225 is enabled for data transmission 220 using non-rateless coding). Conversely, if the DCI 215 is sent in the second portion / part, a rateless coding transmission scheme without HARQ may be configured (eg, feedback information 225 is disabled for data transmission 220 using rateless coding).

[0116] In some aspects, RRC configuration signaling that configures SPS resources and / or CG resources associated with a data transmission can be used to convey an indication of whether feedback information 225 is enabled or disabled for the corresponding data transmission. That is, the base station 205 can send or otherwise communicate to the UE 210 RRC configuration signaling that configures SPS (e.g., semi-persistent downlink resources) and / or CG resources (e.g., semi-persistent uplink resources) to be used for data transmission. The RRC configuration signaling can be configured to indicate that data transmissions scheduled using SPS / CG resources that use rateless coding will have HARQ feedback information disabled. The RRC configuration signaling can be configured to indicate that data transmissions scheduled using SPS / CG resources that use non-rateless coding will have HARQ feedback information enabled.

[0117] In another example, the HARQ process number carried in the DCI 215 or otherwise communicated can be used to convey an indication that feedback information 225 is disabled for data transmission 220 using rateless coding. That is, one or more HARQ process numbers can be reserved for data transmission based on rateless coding. A first set of HARQ process numbers can be associated with feedback information 225 being enabled for data transmission 220 using non-rateless coding, and a second set of HARQ process numbers can be associated with feedback information 225 being disabled for data transmission 220 using rateless coding. In one example, HARQ process number 0000 can be associated with rateless coding transmission without feedback information 225 being enabled, and the NDI field can be set to 1 or configured to 0. In this example, the NDI can also be reused to indicate whether it contains a system data packet. In this example, HARQ process numbers 0001-1111 can refer to a regular transmission scheme (e.g., feedback information 225 is enabled for data transmission using non-rateless coding), where the NDI field indicates whether the transmission is a retransmission. In another example, HARQ process numbers 0000-0001 may be associated with rateless transmission without feedback information 225 being enabled, and the NDI field may be set to 1 or configured to 0. In this example, the NDI may also be reused to indicate whether it contains a system data packet. In this example, HARQ process numbers 0010-1111 may be associated with a conventional transmission scheme (e.g., feedback information 225 is enabled for data transmission using non-rateless coding), where the NDI field indicates whether the transmission is a retransmission.

[0118] In some examples, the DCI 215 can be based on a capability report received from the UE 210. That is, the UE 210 can identify or otherwise determine whether it supports data transmission using rateless coding in situations where HARQ feedback is enabled and / or disabled. The UE 210 can send, communicate, or otherwise provide (and the base station 205 can receive or otherwise obtain) a UE capability message. The UE capability message can carry (e.g., explicitly using one or more bits, fields, etc.) or otherwise communicate (e.g., implicitly using linked or otherwise associated bits, fields, etc.) an indication of whether the UE 205 supports participation in rateless coding data transmission in which HARQ feedback is disabled. For example, the UE 210 can send a UE capability message indicating that performing or monitoring data transmission associated with rateless coding in which feedback information is disabled is not supported. Alternatively, the UE 210 can send a UE capability message indicating that performing or monitoring data transmission associated with rateless coding in which feedback information is disabled is supported.

[0119] In some aspects, the DCI 215 may be based, at least in part, on UE capability information (e.g., whether the UE 210 supports rateless coding data transmission without HARQ feedback). If the UE supports rateless coding without feedback information, the network (e.g., the base station 205) may schedule such rateless coding transmission without feedback information and / or may schedule a legacy transmission scheme (e.g., data transmission using a non-rateless coding scheme) for the UE. If the UE does not support rateless coding transmission without feedback information, the network (e.g., the base station 205) may schedule a legacy transmission scheme for data transmission.

[0120] Thus, UE 210 may receive DCI 215 scheduling a data transmission 220 that uses rateless coding. Based on DCI 215, the CORESET / SS set of DCI 215, the SPS / CG configured resources for data transmission 220 and activated by DCI 215, the HARQ process number, etc., UE 210 may determine that feedback information 225 is disabled for data transmission 220 that uses rateless coding. If feedback information is enabled (e.g., when data transmission 220 uses non-rateless coding), UE 210 may send or otherwise communicate feedback information 225 to provide ACK / NACK information for data transmission 220 that uses non-rateless coding to base station 205. When disabled (e.g., when data transmission 220 uses rateless coding), UE 210 may receive and decode data transmission 220 but may refrain from sending feedback information 225 to base station 205.

[0121] Figure 3 An example of a DCI configuration 300 supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is illustrated. In some examples, the DCI configuration 300 can implement aspects of wireless communication systems 100 and / or 200. Aspects of the DCI configuration 300 can be implemented at or by a UE and / or a base station, which can be examples of corresponding devices described herein.

[0122] As described above, various aspects of the techniques provide various mechanisms that can be used to signal or otherwise convey (e.g., explicitly and / or implicitly) an indication that feedback information is disabled for data transmissions using rateless coding. Generally, a base station may send a DCI including a PDCCH payload 305 and CRC bits 310 to a UE, the DCI scheduling a data transmission utilizing a rateless coding scheme (e.g., in a downlink scenario). It will be appreciated that these techniques can be applicable to uplink scenarios in which a UE schedules and performs data transmissions to a base station (and / or another UE) utilizing rateless coding and indicates that feedback information is disabled. Continuing with the downlink scenario example, the UE may determine, based on the DCI, at least in some aspects, that feedback information (e.g., HARQ feedback information) for data transmissions utilizing rateless coding is disabled. When enabled (e.g., when the data transmission utilizes non-rateless coding), the UE may attempt to receive and decode the data transmission and, based on the result, send feedback information to the base station. For example, the feedback information may include ACK information for the data transmission when the UE is able to successfully receive and decode the data transmission, or NACK information if the UE is unable to successfully receive and decode the data transmission. When disabled (e.g., when the data transmission uses rateless coding), the UE may attempt to receive and decode the data transmission using the rateless coding scheme, but may not send ACK / NACK information for the data transmission (e.g., performing or monitoring feedback information may include the UE refraining from sending feedback information).

[0123] Thus, the UE may determine, based at least in part on the DCI for the scheduled data transmission, that feedback information (e.g., HARQ feedback information, such as ACK / NACK information) is disabled for data transmission using rateless coding. The base station may select or otherwise determine to disable feedback information for data transmission using rateless coding. Thus, the base station may utilize various aspects of the described techniques to send or otherwise communicate an indication that feedback information is disabled for data transmission using a rateless coding scheme. The scheduling DCI may be used, at least in part, by the base station to send or otherwise communicate such an indication. DCI configuration 300 illustrates a non-limiting example of using a dedicated RNTI to scramble at least a portion of the scheduling DCI to convey such an indication.

[0124] For example, the UE may determine that feedback information is disabled based on a dedicated RNTI used by the base station to scramble the CRC portion of the scheduling DCI. That is, when feedback information is enabled, a first one or more RNTIs may be reserved or otherwise associated with data transmission using non-rateless coding, and when feedback information is disabled, a second one or more RNTIs may be reserved or otherwise associated with data transmission using rateless coding. The base station that selects a specific or dedicated RNTI to scramble the CRC portion of the scheduling DCI may carry or otherwise communicate an indication that data transmission using rateless coding is not configured with feedback information.

[0125] More specifically, the scheduling DCI may include a PDCCH payload 305 including bits a0 to a A-1 These bits may be used to carry or otherwise convey information associated with or otherwise activating resources for data transmission using a rateless coding scheme. The base station may add CRC bits 310 to the PDCCH payload 305, which may include bits p0 through p1. L-1 . CRC bits 310 may generally be used as an error checking technique. The base station may determine that data transmission using a rateless coding scheme is to be disabled and select an RNTI for scrambling CRC bits 310 accordingly. For example, the base station may select a first RNTI from a first RNTI set associated with feedback information being enabled for data transmission using non-rateless coding and a second RNTI from a second RNTI set associated with feedback information being disabled for data transmission using rateless coding. The base station may use the RNTI to scramble CRC bits 310 (e.g., bits p0 through p1). L-1 ) to generate or otherwise obtain bits X0 to X L-1 After further processing / modification, the base station may send a packet including the PDCCH payload 305 and the CRC bits C0 to C1 scrambled by the RNTI. L-1 Scheduling DCI.

[0126] It will be appreciated that a dedicated RNTI may be used to scramble other portions, or in some examples all of the scheduling DCI.Thus, the UE may determine based on the RNTI that feedback information for data transmission using rateless coding is disabled.

[0127] Figure 4A and Figure 4BAn example of a process 400 for supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is illustrated. In some examples, process 400 can implement aspects of wireless communication systems 100 and / or 200. Aspects of process 400 can be implemented by or at a UE and / or base station (BS), which can be examples of corresponding devices described herein. In general, Figure 4A The process 400-a illustrates a downlink example, and Figure 4B Process 400 - b illustrates an uplink example, any of which may utilize aspects of the described techniques.

[0128] As described above, various aspects of the techniques provide various mechanisms that can be used to signal or otherwise convey (e.g., explicitly and / or implicitly) an indication that feedback information is disabled for (e.g., not configured for) data transmissions using a rateless coding scheme. Generally, a base station may transmit DCI that schedules data transmissions using a rateless coding scheme (e.g., in a downlink scenario). It will be appreciated that these techniques can be applicable to uplink scenarios in which a UE schedules and performs data transmissions to a base station (and / or another UE) using rateless coding and indicates that feedback information is disabled. Continuing with the downlink scenario example, the UE may determine, at least in some aspects based on the DCI, that feedback information (e.g., HARQ feedback information) for data transmissions using rateless coding is disabled. When enabled (e.g., when the data transmission uses non-rateless coding), the UE may attempt to receive and decode the data transmission and, based on the result, send feedback information to the base station. For example, the feedback information may include ACK information for the data transmission when the UE is able to successfully receive and decode the data transmission, or NACK information if the UE is unable to successfully receive and decode the data transmission. When disabled (e.g., when the data transmission uses rateless coding), the UE may attempt to receive and decode the data transmission using the rateless coding scheme, but may not send ACK / NACK information for the data transmission (e.g., performing or monitoring feedback information may include the UE refraining from sending feedback information).

[0129] Thus, a UE may determine, based at least in part on a DCI scheduling data transmission, that feedback information (e.g., HARQ feedback information, such as ACK / NACK information) is disabled for data transmission using rateless coding. A base station may select or otherwise determine to disable feedback information for data transmission using rateless coding. Thus, a base station may utilize various aspects of the described techniques to transmit or otherwise communicate an indication that feedback information is disabled for data transmission using a rateless coding scheme. The scheduling DCI may be used, at least in part, by the base station to transmit or otherwise communicate such an indication.

[0130] For example, the UE may determine that feedback information is disabled based on RRC configuration signaling that configures SPS resources (in the downlink example) and / or CG resources (in the uplink example) associated with data transmission activated by scheduling DCI. That is, the base station may send or otherwise communicate to the UE RRC configuration signaling that configures SPS (e.g., semi-persistent downlink resources) and / or CG resources (e.g., semi-persistent uplink resources) to be used for data transmission. The RRC configuration signaling may be configured to indicate that data transmission using rateless coding scheduled using SPS / CG resources will cause HARQ feedback information to be disabled.

[0131] More specifically and with reference to Figure 4A In the downlink example shown in process 400-a of FIG, at 405, the base station may send RRC signaling to the UE. The RRC signaling may carry or otherwise convey an indication of an SPS-Config field / bit that identifies various aspects of the semi-persistent downlink resources configured by the RRC signaling. For example, the RRC signaling may indicate the configured time, frequency, space, and / or code resources, the periodicity of such resources, etc. The RRC signaling (e.g., the SPS-Config field / bit) may also carry or otherwise convey an indication that data transmission using rateless coding on such resources is configured with disabled feedback information.

[0132] That is, the network can configure a plurality of SPS configurations (SPS-Config) (e.g., a downlink SPS configuration set) for the UE. Some SPS configurations (e.g., a first subset) may correspond to or otherwise be associated with rateless code data transmission without feedback information. Other SPS configurations (e.g., a second subset) may correspond to or otherwise be associated with a traditional data transmission scheme (e.g., with non-rateless coding). The network may provide or otherwise indicate the index of one or more downlink SPS configurations to the UE. The network may provide an indication using an SPS configuration index (SPS-ConfigIndex) information element (IE) and / or using DCI format 1 that activates a configured scheduling (CS) (e.g., an SPS configuration).

[0133] Then, at 410, the base station may send a scheduling DCI to the UE that activates the configured SPS resources for data transmission using the rateless coding scheme. The UE may determine, based at least in part on the SPS resources configured by RRC signaling, that the SPS resources activated by the scheduling DCI are configured with feedback information that is disabled for data transmission. At 415, the UE may monitor the data transmission using the rateless coding scheme. The data transmission may span one or more PDSCH transmissions.

[0134] If feedback information is enabled for data transmission using non-rateless coding, then at 420, the UE may send or otherwise communicate feedback information (e.g., HARQ feedback information) to the base station providing ACK / NACK information for the data transmission. If feedback information is disabled for data transmission using rateless coding, then the UE may refrain from sending feedback information to the base station. Subsequently, at 425, another DCI may be sent by the base station covering the previously configured SPS resources and, in turn, scheduling the second data transmission performed at 430.

[0135] In the uplink scenario and with reference to Figure 4B In the uplink example shown in process 400-b of , at 435, the base station may send RRC signaling to the UE. The RRC signaling may carry or otherwise convey an indication of a ConfiguredGrantConfig field / bit that identifies various aspects of the CG uplink resources configured by the RRC signaling. For example, the RRC signaling may indicate the configured time, frequency, space, and / or code resources, the periodicity of such resources, etc. The RRC signaling (e.g., the ConfiguredGrantConfig field / bit) may also carry or otherwise convey an indication that data transmission using rateless coding activated on such resources is configured with disabled feedback information.

[0136] That is, the network can configure the UE with multiple CG configurations (ConfigurationGrantConfig) (e.g., uplink CG configuration sets). Some CG configurations (e.g., the first subset) may correspond to or otherwise be associated with rateless code data transmission without feedback information. Other CG configurations (e.g., the second subset) may correspond to or otherwise be associated with a traditional data transmission scheme (e.g., with non-rateless coding). The network may provide or otherwise indicate the index of one or more downlink CG configurations to the UE. The network may provide an indication using the CG configuration index (ConfiguredGrantConfigIndex) IE and / or using DCI format 0 that activates the CS (e.g., CG configuration). Then, at 440, the base station may send a scheduling DCI to the UE that activates the configured CG resources for data transmission using the rateless coding scheme. The UE may determine, at least in part based on the CG resources configured by RRC signaling, that the CG resources activated by the scheduling DCI are configured with feedback information that is disabled for data transmission. At 445, the UE may perform data transmission (e.g., sending) using the rateless coding scheme. Data transmission may span one or more PUSCH transmissions.

[0137] If feedback information is enabled for data transmission using non-rateless coding, then at 450, the base station may send or otherwise communicate feedback information (e.g., HARQ feedback information) to the UE that provides ACK / NACK information for the data transmission. If feedback information is disabled for data transmission using rateless coding, the UE may avoid sending feedback information to the base station. Subsequently, at 455, another DCI may be sent by the base station that covers the previously configured CG resources and instead schedules a second data transmission to be performed (e.g., scheduling a second uplink and / or downlink transmission).

[0138] Figure 5 An example of a process 500 for supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is illustrated. In some examples, process 500 can implement aspects of wireless communication systems 100 and / or 200, DCI configuration 300, and / or process 400. Aspects of process 500 can be implemented by or at base station 505 and / or UE 510, which can be examples of corresponding devices described herein.

[0139] At 515, the base station 505 may schedule a data transmission for the UE 510. For example, the base station 505 may determine that it has a data transmission (e.g., an uplink data transmission and / or a downlink data transmission) to be performed with the UE 510. The base station 505 may determine that the data transmission will utilize a rateless coding scheme, such as a network code. The base station 505 may determine that feedback information (e.g., HARQ feedback information) is disabled for data transmission using rateless coding. Accordingly, the base station 505 may transmit or otherwise transmit (and the UE 510 may receive) a DCI carrying a grant to schedule the data transmission. The DCI may identify the resources to be used for the data transmission. In some aspects, the base station 505 may configure the DCI to carry or otherwise convey an indication that feedback information is disabled for data transmission using rateless coding. For example, the base station 505 may use the RNTI associated with the rateless coding data transmission to scramble the CRC portion of the DCI. In another example, the base station 505 may configure a field in the DCI (e.g., a new field and / or modify / repurpose an existing field) to indicate that feedback information is disabled for the data transmission. For example, fields such as the MCS, NDI, RV, DAI, TPC, PUSCH resource indicator, PDSCH to feedback information timing indicator, and HARQ process number of the DCI, alone or in any combination, may be configured or otherwise communicate an indication that feedback information has been disabled for data transmission using rateless coding. In some aspects, the base station 505 may use RRC signaling to configure the UE 510 with one or more SS sets and / or CORESETs, wherein scheduling DCI sent in a particular SS set and / or CORESET communicates an indication that feedback information is disabled. In some aspects, the base station 505 may use RRC signaling to configure SPS / CG resources without enabling feedback information, and DCI activating the particular SPS / CG resources communicates an indication that feedback information is disabled for data transmission using rateless coding. In some aspects, a HARQ process number may be assigned or otherwise associated with data transmission using rateless coding for which feedback information is disabled. For example, a first set of one or more HARQ process numbers may be associated with data transmission using non-rateless coding with feedback information enabled, and a second set of one or more HARQ process numbers may be associated with data transmission using rateless coding with feedback information disabled.

[0140] Thus, at 520, UE 510 may determine to disable feedback information for data transmission based on the rateless coding scheme (based on data transmission utilizing rateless coding), the DCI, resources associated with the DCI (e.g., the CORESET and / or SS set in which the DCI is received), and / or an SPS configuration associated with the data transmission (e.g., RRC configuration signaling configuring the SPS / CG resources activated by the DCI). For example, UE 510 may identify or otherwise determine that a particular RNTI is used to scramble the CRC portion of the DCI. UE 510 may determine to disable feedback information for data transmission utilizing rateless coding based on the RNTI. For example, UE 510 may determine or otherwise identify which RNTI is used to scramble the CRC portion, thereby determining whether the RNTI is associated with whether feedback information is enabled for data transmission utilizing non-rateless coding or disabled for data transmission utilizing rateless coding.

[0141] In some aspects, a new field may be added to the DCI that includes one or more bits associated with configuring a rateless coding scheme for a UE in the absence of feedback information. That is, a new field may be configured in the DCI and set to a value to indicate that data transmission using rateless coding results in feedback information being disabled. In some aspects, existing fields may be used (e.g., modified and / or reused) to convey an indication that data transmission using rateless coding results in feedback information being disabled. For example, the MCS field, NDI field, RV field, DAI field, TPC field / command, etc. of the DCI may be set to one or more values ​​for conveying the indication, individually or in any combination.

[0142] In some aspects, the UE 510 may determine that feedback information is disabled for data transmission using rateless coding based on the resources in which the DCI is received. For example, the UE may receive DCI scheduling data transmission in a first portion of resources associated with the DCI (e.g., a first one or more CORESETs and / or SS sets) or in a second portion of resources associated with the DCI (e.g., a second one or more CORESETs and / or SS sets). Based on the resources in which the DCI is received, the UE 510 may determine that feedback information is disabled for data transmission using rateless coding.

[0143] In some aspects, the UE 510 may determine to disable feedback information for data transmission using rateless coding based on RRC configuration signaling indicating an SPS configuration associated with the data transmission (e.g., the RRC configuration signal may configure the SPS and / or CG resources activated by the scheduling DCI and used for the data transmission). Thus, the UE 510 may determine that the scheduling DCI activates a particular set of semi-persistent resources and that the configuration signal configuring those semi-persistent resources indicates that data transmission using rateless coding will cause feedback information to be disabled.

[0144] In some aspects, the UE 510 may determine to disable feedback information for data transmission based on the HARQ process numbers indicated in the DCI. For example, a first set of one or more HARQ process numbers may be associated with non-rateless coded data transmissions with feedback information enabled, and a second set of HARQ process numbers may be associated with non-rateless coded data transmissions with feedback information disabled.

[0145] Thus, at 525, UE 510 may perform or monitor data transmission according to the DCI and the rateless coding scheme. That is, in a downlink scenario, UE 510 may receive a PDSCH data transmission from base station 505. In an uplink scenario, UE 510 may send a PUSCH data transmission to base station 505. The data transmission may utilize a rateless coding scheme and may have feedback information disabled.

[0146] Therefore, at 530, UE 510 may perform or monitor feedback information for data transmission based on a determination of whether feedback information is enabled or disabled for data transmission. That is, if feedback information is enabled for downlink data transmission using non-rateless coding, UE 510 may send feedback information carrying or otherwise conveying ACK / NACK information for the data transmission to base station 505. If feedback information is enabled for uplink transmission using non-rateless coding, UE 510 may receive feedback information carrying or otherwise conveying ACK / NACK information for the data transmission from base station 505.

[0147] If feedback information is disabled for data transmission using rateless coding, the UE 510 performing or monitoring the feedback information may include the UE 510 refraining from sending feedback information in downlink data transmission scenarios and / or the base station 505 refraining from sending feedback information in uplink data transmission. Thus, the base station 505 and / or the UE 510 may utilize aspects of the described techniques to perform data transmission (e.g., PDSCH and / or PUSCH) using a rateless coding scheme and convey an indication that feedback information for the data transmission is disabled.

[0148] Figure 6 A block diagram 600 of a device 605 supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is shown. The device 605 can be an example of aspects of the UE 115 as described herein. The device 605 can include a receiver 610, a communication manager 615, and a transmitter 620. The device 605 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0149] The receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an indication scheme for rateless code transmission without feedback information, etc.). The information may be passed to other components of the device 605. The receiver 610 may be a reference Figure 9 Examples of aspects of the transceiver 920 are described. The receiver 610 may utilize a single antenna or a set of antennas.

[0150] The communication manager 615 may receive a DCI including a grant to schedule data transmission for a UE, the data transmission being associated with a rateless coding scheme; determine to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination. The communication manager 615 may be an example of aspects of the communication manager 910 described herein.

[0151] The communication manager 615 or its subcomponents may be implemented in hardware, in code (e.g., software) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 615 or its subcomponents may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0152] The communication manager 615 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 615 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 615 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0153] Transmitter 620 can transmit signals generated by other components of device 605. In some examples, transmitter 620 can be co-located with receiver 610 in a transceiver module. For example, transmitter 620 can be a reference Figure 9 Examples of aspects of the transceiver 920 are described. The transmitter 620 may utilize a single antenna or a set of antennas.

[0154] Figure 7 A block diagram 700 of a device 705 supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is shown. The device 705 can be an example of aspects of the device 605 or UE 115 as described herein. The device 705 can include a receiver 710, a communication manager 715, and a transmitter 740. The device 705 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0155] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an indication scheme for rateless code transmission without feedback information). The information may be passed to other components of the device 705. The receiver 710 may be a reference Figure 9 Examples of aspects of the transceiver 920 are described. The receiver 710 may utilize a single antenna or a set of antennas.

[0156] The communication manager 715 may be an example of aspects of the communication manager 615 as described herein. The communication manager 715 may include a grant manager 720, a HARQ enablement manager 725, a data transmission manager 730, and a feedback information manager 735. The communication manager 715 may be an example of aspects of the communication manager 910 as described herein.

[0157] Grant manager 720 may receive DCI including a grant scheduling a data transmission for a UE, the data transmission associated with a rateless coding scheme.

[0158] The HARQ enablement manager 725 may determine to disable feedback information for data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission.

[0159] The data transmission manager 730 may perform or monitor data transmission according to the DCI and the rateless coding scheme.

[0160] The feedback information manager 735 may perform or monitor feedback information for data transmission according to the determination.

[0161] Transmitter 740 can transmit signals generated by other components of device 705. In some examples, transmitter 740 can be co-located with receiver 710 in a transceiver module. For example, transmitter 740 can be a reference Figure 9 Examples of aspects of the transceiver 920 are described. The transmitter 740 may utilize a single antenna or a set of antennas.

[0162] Figure 8 A block diagram 800 of a communication manager 805 supporting an indication scheme for rateless code transmission without feedback information is shown in accordance with aspects of the present disclosure. The communication manager 805 may be an example of aspects of the communication manager 615, the communication manager 715, or the communication manager 910 as described herein. The communication manager 805 may include a grant manager 810, a HARQ enablement manager 815, a data transmission manager 820, a feedback information manager 825, an RNTI manager 830, a DCI configuration manager 835, a CORESET / SS set manager 840, an SPS / CG manager 845, a HARQ process number manager 850, a DL feedback manager 855, and a UL feedback manager 860. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0163] Grant manager 810 may receive DCI including a grant scheduling a data transmission for a UE, the data transmission associated with a rateless coding scheme.

[0164] The HARQ enabling manager 815 may determine to disable feedback information for data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission.

[0165] The data transmission manager 820 may perform or monitor data transmission according to the DCI and the rateless coding scheme.

[0166] The feedback information manager 825 may perform or monitor feedback information for data transmission according to the determination.

[0167] The RNTI manager 830 may identify a radio network temporary identifier for scrambling a cyclic redundancy check portion of the DCI. In some examples, the RNTI manager 830 may determine to disable feedback information for data transmission based on the radio network temporary identifier.

[0168] The DCI configuration manager 835 may determine to disable feedback information for data transmission based on fields indicated in the DCI. In some cases, the fields include one or more bits associated with a rateless coding scheme configured for no feedback information for the UE, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a hybrid automatic repeat / request process number, or a combination thereof.

[0169] The CORESET / SS set manager 840 may receive DCI in a first portion of resources associated with the DCI or in a second portion of resources associated with the DCI. In some examples, the CORESET / SS set manager 840 may determine to disable feedback information for data transmission based on the DCI received in the first portion of resources or the second portion of resources. In some cases, the resources associated with the DCI include a CORESET, an SS set, or both.

[0170] The SPS / CG manager 845 may receive an RRC configuration indicating a semi-persistent scheduling configuration associated with a data transmission. In some examples, the SPS / CG manager 845 may determine to disable feedback information for the data transmission based on the RRC configuration. In some cases, the RRC configuration includes an SPS configuration indication, a CG configuration indication, or both.

[0171] The HARQ process number manager 850 may identify the HARQ process number indicated in the DCI. In some examples, the HARQ process number manager 850 may determine to disable feedback information for data transmission based on the HARQ process number. In some cases, a first set of HARQ process numbers indicates that feedback information may be disabled for data transmission, and a second set of HARQ process numbers indicates that feedback information may be enabled for data transmission using a non-rateless coding scheme. The HARQ process number manager 850 may send a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled. In some cases, the DCI is based at least in part on the UE capability message.

[0172] Figure 9A diagram of a system 900 including a device 905 supporting an indication scheme for rateless code transmission without feedback information in accordance with various aspects of the present disclosure is shown. The device 905 may be an example of, or include components of, the device 605, device 705, or UE 115 as described herein. The device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, including a communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may communicate electronically via one or more buses (e.g., bus 945).

[0173] The communication manager 910 may: receive DCI including an authorization to schedule data transmission for a UE, the data transmission being associated with a rateless coding scheme; determine to disable feedback information for the data transmission based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination.

[0174] I / O controller 915 can manage input and output signals for device 905. I / O controller 915 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 915 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 915 can utilize a controller such as 915. In some cases, the I / O controller 915 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 915 may be implemented as part of a processor. In some cases, a user may interact with the device 905 via the I / O controller 915 or via hardware components controlled by the I / O controller 915.

[0175] The transceiver 920 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 920 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 920 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, as well as demodulate packets received from the antenna.

[0176] In some cases, a wireless device may include a single antenna 925. However, in some cases, the device may have more than one antenna 925 capable of sending or receiving multiple wireless transmissions simultaneously.

[0177] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 930 may contain, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 940 may be configured to operate the memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting an indication scheme for rateless code transmission without feedback information).

[0179] The code 935 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 935 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code 935 may not be directly executed by the processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0180] Figure 10 A block diagram 1000 of a device 1005 supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is shown. The device 1005 can be an example of aspects of the base station 105 as described herein. The device 1005 can include a receiver 1010, a communication manager 1015, and a transmitter 1020. The device 1005 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0181] The receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an indication scheme for rateless code transmission without feedback information, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Figure 13 Examples of various aspects of the described transceiver 1320. The receiver 1010 may utilize a single antenna or a set of antennas.

[0182] The communication manager 1015 may determine to disable feedback information for a data transmission with the UE, the data transmission being associated with a rateless coding scheme; transmit DCI including a grant to schedule a data transmission, feedback information for the data transmission being enabled or disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission in accordance with the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission in accordance with the determination. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein.

[0183] The communication manager 1015 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functionality of the communication manager 1015 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functionality described in this disclosure.

[0184] The communication manager 1015 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1015 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0185] Transmitter 1020 can transmit signals generated by other components of device 1005. In some examples, transmitter 1020 can be co-located with receiver 1010 in a transceiver module. For example, transmitter 1020 can be a reference Figure 13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1020 can utilize a single antenna or a set of antennas.

[0186] Figure 11A block diagram 1100 of a device 1105 supporting an indication scheme for rateless code transmission without feedback information according to aspects of the present disclosure is shown. The device 1105 can be an example of aspects of the device 1005 or base station 105 as described herein. The device 1105 can include a receiver 1110, a communication manager 1115, and a transmitter 1140. The device 1105 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0187] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to an indication scheme for rateless code transmission without feedback information, etc.). The information may be passed to other components of the device 1105. The receiver 1110 may be a reference Figure 13 Examples of various aspects of the described transceiver 1320. The receiver 1110 may utilize a single antenna or a set of antennas.

[0188] The communication manager 1115 may be an example of aspects of the communication manager 1015 as described herein. The communication manager 1115 may include a HARQ enabling manager 1120, a grant manager 1125, a data transmission manager 1130, and a feedback information manager 1135. The communication manager 1115 may be an example of aspects of the communication manager 1310 as described herein.

[0189] The HARQ enabling manager 1120 may determine to disable feedback information for data transmission with the UE, the data transmission being associated with the rateless coding scheme.

[0190] Grant manager 1125 may send a DCI including a grant to schedule a data transmission for which feedback information is enabled or disabled based on a rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission.

[0191] The data transmission manager 1130 may perform or monitor data transmission according to the DCI and the rateless coding scheme.

[0192] The feedback information manager 1135 may perform or monitor feedback information for data transmission according to the determination.

[0193] Transmitter 1140 can transmit signals generated by other components of device 1105. In some examples, transmitter 1140 can be co-located with receiver 1110 in a transceiver module. For example, transmitter 1140 can be a reference Figure 13 Examples of aspects of the described transceiver 1320. The transmitter 1140 may utilize a single antenna or a set of antennas.

[0194] Figure 12 A block diagram 1200 of a communication manager 1205 supporting an indication scheme for rateless code transmission without feedback information is shown in accordance with aspects of the present disclosure. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 as described herein. The communication manager 1205 may include a HARQ enabling manager 1210, a grant manager 1215, a data transmission manager 1220, a feedback information manager 1225, an RNTI manager 1230, a DCI configuration manager 1235, a CORESET / SS set manager 1240, an SPS / CG manager 1245, a HARQ process number manager 1250, a DL feedback manager 1255, and a UL feedback manager 1260. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0195] The HARQ enabling manager 1210 may determine to disable feedback information for data transmission with the UE, the data transmission being associated with a rateless coding scheme.

[0196] Grant manager 1215 may send a DCI including a grant to schedule a data transmission for which feedback information is enabled or disabled based on a rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission.

[0197] The data transmission manager 1220 may perform or monitor data transmission according to the DCI and the rateless coding scheme.

[0198] The feedback information manager 1225 may perform or monitor feedback information for data transmission according to the determination.

[0199] The RNTI manager 1230 may scramble the CRC portion of the DCI using the RNTI based on the determination to disable feedback information for data transmission.

[0200] The DCI configuration manager 1235 may configure a field in the DCI to indicate disabling of feedback information for data transmission. In some cases, the field includes one or more bits associated with a rateless coding scheme configured for no feedback information for the UE, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a hybrid automatic repeat / request process number, or a combination thereof.

[0201] The CORESET / SS set manager 1240 may send the DCI in a first portion of resources associated with the DCI or in a second portion of resources associated with the DCI, wherein sending the DCI in the first portion or the second portion indicates disabling feedback information for data transmission. In some cases, the resources associated with the DCI include a CORESET, an SS set, or both.

[0202] The SPS / CG manager 1245 may send a radio resource control configuration indicating a semi-persistent scheduling configuration associated with the data transmission, wherein the radio resource control configuration indicates disabling feedback information for the data transmission based on the radio resource control configuration. In some cases, the radio resource control configuration includes an SPS configuration indication, a CG configuration indication, or both.

[0203] The HARQ process number manager 1250 may select a HARQ process number indicated in the DCI that indicates that feedback information for data transmission is disabled. In some cases, a first set of HARQ process numbers indicates that feedback information is disabled for data transmission, and a second set of HARQ process numbers indicates that feedback information is enabled for data transmission using a non-rateless coding scheme. The HARQ process number manager 1250 may receive a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled, wherein the DCI is based at least in part on the UE capability message.

[0204] Figure 13 A diagram of a system 1300 including a device 1305 supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure is shown. Device 1305 may be an example of, or include components of, device 1005, device 1105, or base station 105 as described herein. Device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communications manager 1310, a network communications manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-station communications manager 1345. These components may be in electronic communication via one or more buses (e.g., bus 1350).

[0205] The communication manager 1310 may: determine to disable feedback information for data transmission with the UE, the data transmission being associated with a rateless coding scheme; send DCI including an authorization for scheduling data transmission, feedback information for the data transmission being enabled or disabled based on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission; perform or monitor the data transmission according to the DCI and the rateless coding scheme; and perform or monitor the feedback information for the data transmission according to the determination.

[0206] The network communications manager 1315 can manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1315 can manage data communication transmissions for client devices such as one or more UEs 115 .

[0207] The transceiver 1320 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1320 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1320 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, as well as demodulate packets received from the antenna.

[0208] In some cases, a wireless device may include a single antenna 1325. However, in some cases, a device may have more than one antenna 1325, which may be capable of sending or receiving multiple wireless transmissions simultaneously.

[0209] Memory 1330 may include RAM, ROM, or a combination thereof. Memory 1330 may store computer-readable code 1335 including instructions that, when executed by a processor (e.g., processor 1340), cause the device to perform various functions described herein. In some cases, memory 1330 may include, among other things, a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0210] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting an indication scheme for rateless code transmission without feedback information).

[0211] The inter-site communication manager 1345 can manage communications with other base stations 105 and can include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-site communication manager 1345 can coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1345 can provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between the base stations 105.

[0212] The code 1335 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1335 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code 1335 may not be directly executed by the processor 1340, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0213] Figure 14 A flow chart is shown illustrating a method 1400 for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1400 may be implemented by reference to Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0214] At 1405, the UE may receive a DCI including a grant for scheduling data transmission for the UE, the data transmission being associated with a rateless coding scheme. The operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be as described with reference to Figures 6 to 9 The authorization manager described is executed.

[0215] At 1410, the UE may determine to disable feedback information for data transmission based on the rateless coding scheme and one or more of: DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figures 6 to 9 The described HARQ enabling manager is executed.

[0216] At 1415, the UE may perform or monitor data transmission according to the DCI and the rateless coding scheme. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be as described with reference to Figures 6 to 9 The data transfer manager described is executed.

[0217] At 1420, the UE may perform or monitor feedback information for data transmission based on the determination. The operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be as described with reference to Figures 6 to 9 The described feedback information manager is executed.

[0218] Figure 15 A flow chart is shown illustrating a method 1500 for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by reference to Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0219] At 1505, the UE may receive a DCI including a grant for scheduling data transmission for the UE, the data transmission being associated with a rateless coding scheme. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be as described with reference to Figures 6 to 9 The authorization manager described is executed.

[0220] At 1510, the UE may identify a radio network temporary identifier for scrambling a cyclic redundancy check portion of the DCI. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figures 6 to 9 The RNTI manager described is used to perform

[0221] At 1515, the UE may determine to disable feedback information for data transmission based on the rateless coding scheme and one or more of: DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be as described with reference to Figures 6 to 9 The described HARQ enabling manager is executed.

[0222] At 1520, the UE may determine to disable feedback information for data transmission based on the radio network temporary identifier. The operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1520 may be as described with reference to Figures 6 to 9 The RNTI manager described is used to perform

[0223] At 1525, the UE may perform or monitor data transmission according to the DCI and the rateless coding scheme. The operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operations of 1525 may be as described with reference to Figures 6 to 9 The data transfer manager described is executed.

[0224] At 1530, the UE may perform or monitor feedback information for data transmission based on the determination. The operations of 1530 may be performed according to the methods described herein. In some examples, aspects of the operations of 1530 may be as described with reference to Figures 6 to 9 The described feedback information manager is executed.

[0225] Figure 16 A flow chart is shown illustrating a method 1600 for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1600 may be implemented by reference to Figures 6 to 9 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0226] At 1605, the UE may receive a DCI including a grant for scheduling data transmission for the UE, the data transmission being associated with a rateless coding scheme. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be as described with reference to Figures 6 to 9 The authorization manager described is executed.

[0227] At 1610, the UE may determine to disable feedback information for data transmission based on the rateless coding scheme and one or more of: DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be as described with reference to Figures 6 to 9 The described HARQ enabling manager is executed.

[0228] At 1615, the UE may determine to disable feedback information for data transmission based on the field indicated in the DCI. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be as described in reference to Figures 6 to 9 The DCI configuration manager described is executed.

[0229] At 1620, the UE may perform or monitor data transmission according to the DCI and the rateless coding scheme. The operations of 1620 may be performed according to the methods described herein. In some examples, aspects of the operations of 1620 may be as described in reference to Figures 6 to 9 The data transfer manager described is executed.

[0230] At 1625, the UE may perform or monitor feedback information for data transmission based on the determination. The operations of 1625 may be performed according to the methods described herein. In some examples, aspects of the operations of 1625 may be as described with reference to Figures 6 to 9 The described feedback information manager is executed.

[0231] Figure 17 A flow chart is shown illustrating a method 1700 for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by reference to Figures 10 to 13 In some examples, the base station may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0232] At 1705, the base station may determine to disable feedback information for data transmission with the UE, the data transmission being associated with a rateless coding scheme. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be as described with reference to Figures 10 to 13 The described HARQ enabling manager is executed.

[0233] At 1710, a base station may transmit a DCI including a grant to schedule data transmission, feedback information for data transmission enabled or disabled based on a rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 10 to 13 The authorization manager described is executed.

[0234] At 1715, the base station may perform or monitor data transmission according to the DCI and the rateless coding scheme. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Figures 10 to 13 The data transfer manager described is executed.

[0235] At 1720, the base station may perform or monitor feedback information for data transmission based on the determination. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be as described with reference to Figures 10 to 13 The described feedback information manager is executed.

[0236] Figure 18 A flow chart is shown illustrating a method 1800 for supporting an indication scheme for rateless code transmission without feedback information in accordance with aspects of the present disclosure. The operations of the method 1800 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by reference to Figures 10 to 13 In some examples, the base station may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0237] At 1805, the base station may determine to disable feedback information for data transmission with the UE, the data transmission being associated with a rateless coding scheme. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be as described with reference to Figures 10 to 13 The described HARQ enabling manager is executed.

[0238] At 1810, the base station may send a radio resource control configuration indicating a semi-persistent scheduling configuration associated with data transmission, wherein the radio resource control configuration indicates disabling feedback information for data transmission based on the radio resource control configuration. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Figures 10 to 13 The SPS / CG manager described is used to perform the above operations.

[0239] At 1815, the base station may transmit a DCI including a grant to schedule data transmission, feedback information for data transmission enabled or disabled based on a rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or a semi-persistent scheduling configuration associated with the data transmission. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Figures 10 to 13The authorization manager described is executed.

[0240] At 1820, the base station may perform or monitor data transmission according to the DCI and the rateless coding scheme. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be as described with reference to Figures 10 to 13 The data transfer manager described is executed.

[0241] At 1825, the base station may perform or monitor feedback information for data transmission based on the determination. The operations of 1825 may be performed according to the methods described herein. In some examples, aspects of the operations of 1825 may be as described with reference to Figures 10 to 13 The described feedback information manager is executed.

[0242] The following provides an overview of various aspects of the present disclosure:

[0243] Aspect 1: A method for wireless communication at a UE, comprising: receiving DCI, the DCI including a grant to schedule data transmission for the UE, the data transmission associated with a rateless coding scheme; determining to disable feedback information for the data transmission based at least in part on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or an SPS configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0244] Aspect 2: The method of aspect 1 further comprising: identifying an RNTI used to scramble a CRC portion of the DCI; and determining to disable feedback information for data transmission based at least in part on the RNTI.

[0245] Aspect 3: The method according to any one of aspects 1 to 2 further includes: determining to disable feedback information for data transmission based at least in part on a field indicated in the DCI.

[0246] Aspect 4: A method according to aspect 3, wherein the field includes one or more bits associated with a rate-less coding scheme for configuring no feedback information for the UE, an MCS field, an NDI, an RV field, a DAI field, a TPC field, a PUSCH resource indicator, a PDSCH to feedback information timing indicator field, a HARQ process number, or a combination thereof.

[0247] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: receiving DCI in a first part of resources associated with the DCI or a second part of resources associated with the DCI; and determining to disable feedback information for data transmission based at least in part on the DCI received in the first part of the resources or the second part of the resources.

[0248] Aspect 6: The method according to aspect 5, wherein the resources associated with the DCI include a control resource set, a search space set, or both.

[0249] Aspect 7: The method according to any one of aspects 1 to 6 further includes: receiving an RRC configuration indicating an SPS configuration associated with data transmission; and determining to disable feedback information for data transmission based at least in part on the RRC configuration.

[0250] Aspect 8: The method according to Aspect 7, wherein the RRC configuration includes an SPS configuration indication, a CG configuration indication, or both.

[0251] Aspect 9: The method according to any one of aspects 1 to 8 further includes: identifying a HARQ process number indicated in the DCI; and determining to disable feedback information for data transmission based at least in part on the HARQ process number.

[0252] Aspect 10: The method of aspect 9, wherein the first set of HARQ process numbers indicates that feedback information is disabled for data transmission, and the second set of HARQ process numbers indicates that feedback information is enabled for data transmission using a non-rateless coding scheme.

[0253] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: sending a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled, wherein the DCI is at least partially based on the UE capability message.

[0254] Aspect 12: A method for wireless communication at a base station, comprising: determining to disable feedback information for data transmission with a UE, the data transmission being associated with a rateless coding scheme; sending DCI, the DCI including an authorization for scheduling data transmission, the feedback information for the data transmission being disabled based at least in part on the rateless coding scheme and one or more of: the DCI, resources associated with the DCI, or an SPS configuration associated with the data transmission; performing or monitoring the data transmission in accordance with the DCI and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission in accordance with the determination.

[0255] Aspect 13: The method of aspect 12, further comprising: scrambling a CRC portion of the DCI using an RNTI, the RNTI being based at least in part on determining to disable feedback information for data transmission.

[0256] Aspect 14: The method according to any one of aspects 12 to 13, further comprising: configuring a field in the DCI to indicate disabling of feedback information for data transmission.

[0257] Aspect 15: A method according to aspect 14, wherein the field includes one or more bits associated with a rateless coding scheme for configuring no feedback information for the UE, an MCS field, an NDI, an RV field, a DAI field, a TPC field, a PUSCH resource indicator, a PDSCH to feedback information timing indicator field, a HARQ process number, or a combination thereof.

[0258] Aspect 16: The method according to any one of Aspects 12 to 15 further includes: sending DCI in a first part of resources associated with the DCI or a second part of resources associated with the DCI, wherein sending the DCI in the first part or the second part indicates disabling feedback information for data transmission.

[0259] Aspect 17: The method according to aspect 16, wherein the resources associated with the DCI include a control resource set, a search space set, or both.

[0260] Aspect 18: The method according to any one of aspects 12 to 17 further comprises: sending an RRC configuration indicating an SPS configuration associated with the data transmission, wherein the RRC configuration indicates disabling of feedback information for the data transmission based at least in part on the RRC configuration.

[0261] Aspect 19: The method according to Aspect 18, wherein the RRC configuration includes an SPS configuration indication, a CG configuration indication, or both.

[0262] Aspect 20: The method according to any one of aspects 12 to 19, further comprising: selecting a HARQ process number indicated in the DCI, the HARQ process number indicating disabling of feedback information for data transmission.

[0263] Aspect 21: The method according to aspect 20, wherein the first set of HARQ process numbers indicates that feedback information is disabled for data transmission using a rateless coding scheme, and the second set of HARQ process numbers indicates that feedback information is enabled for data transmission using a non-rateless coding scheme.

[0264] Aspect 22: The method according to any one of Aspects 12 to 21 further includes: receiving a UE capability message indicating support for performing or monitoring data transmission associated with a rateless coding scheme in which feedback information is disabled, wherein the DCI is at least partially based on the UE capability message.

[0265] Aspect 23: An apparatus for wireless communication at a UE, 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 a method according to any one of aspects 1 to 11.

[0266] Aspect 24: An apparatus for wireless communication at a UE, comprising at least one component for performing the method according to any one of aspects 1 to 11.

[0267] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0268] Aspect 26: An apparatus for wireless communication at a base station, 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 any one of aspects 12 to 22.

[0269] Aspect 27: An apparatus for wireless communication at a base station, comprising at least one component for performing the method according to any one of aspects 12 to 22.

[0270] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 22.

[0271] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0272] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system are described for illustrative purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR is used throughout the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0273] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout this specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0274] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative embodiment, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0275] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0276] Computer readable medium includes two kinds of non-transitory computer storage medium and communication medium, and communication medium includes any medium that is convenient for transferring a computer program from one place to another place.Non-transitory storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transitory computer readable medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transitory medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is sent from a website, server or other remote source using a coaxial cable, optical cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave, etc. are all included in the definition of computer readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0277] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0278] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only the first reference label is used in the specification, the description applies to any similar component having the same first reference label, without regard to the second or other subsequent reference labels.

[0279] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all possible examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details intended to provide an understanding of the technology. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0280] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the overall principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving downlink control information, the downlink control information comprising a grant scheduling data transmission for the UE, the data transmission associated with a rateless coding scheme; determining to disable feedback information for the data transmission based at least in part on the rateless coding scheme and one or more of: the downlink control information, resources associated with the downlink control information, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission according to the downlink control information and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission based on the determination, wherein When it is determined to disable feedback information for the data transmission, the feedback information is disabled for data transmission using a rateless coding scheme and enabled for data transmission using a non-rateless coding scheme.

2. The method according to claim 1, further comprising: identifying a radio network temporary identifier used to scramble a cyclic redundancy check portion of the downlink control information; as well as Determining to disable feedback information for the data transmission is based at least in part on the radio network temporary identifier.

3. The method according to claim 1, further comprising: Determining to disable feedback information for the data transmission is based at least in part on a field indicated in the downlink control information.

4. The method of claim 3, wherein the field comprises one or more bits associated with the rateless coding scheme configured with no feedback information for the UE, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a hybrid automatic repeat / request process number, or a combination thereof.

5. The method according to claim 1, further comprising: receiving the downlink control information in a first portion of the resources associated with the downlink control information or a second portion of the resources associated with the downlink control information; as well as Determining to disable feedback information for the data transmission is based at least in part on the downlink control information received in the first portion of the resources or the second portion of the resources.

6. The method of claim 5, wherein the resources associated with the downlink control information comprise a control resource set, a search space set, or both.

7. The method according to claim 1, further comprising: receiving a radio resource control configuration indicating the semi-persistent scheduling configuration associated with the data transmission; as well as Determining to disable feedback information for the data transmission is based at least in part on the radio resource control configuration.

8. The method of claim 7, wherein the radio resource control configuration comprises a semi-persistent scheduling configuration indication, a configured grant configuration indication, or both.

9. The method according to claim 1, further comprising: identifying a hybrid automatic repeat / request process number indicated in the downlink control information; as well as Determining to disable feedback information for the data transmission is based at least in part on the hybrid automatic repeat / request process number.

10. The method of claim 9, wherein a first set of hybrid automatic repeat / request process numbers indicates that the feedback information is disabled for the data transmission, and a second set of hybrid automatic repeat / request process numbers indicates that the feedback information is enabled for data transmission using a non-rateless coding scheme.

11. The method according to claim 1 , further comprising: A UE capability message is sent, the UE capability message indicating support for performing or monitoring the data transmission associated with the rateless coding scheme with the feedback information disabled, wherein the downlink control information is based at least in part on the UE capability message.

12. A method for wireless communication at a base station, comprising: determining to disable feedback information for data transmission with a user equipment (UE), the data transmission being associated with a rateless coding scheme; transmitting downlink control information, the downlink control information comprising a grant to schedule the data transmission, the feedback information for the data transmission being disabled based at least in part on the rateless coding scheme and one or more of: the downlink control information, resources associated with the downlink control information, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission according to the downlink control information and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission based on the determination, wherein When it is determined to disable feedback information for the data transmission, the feedback information is disabled for data transmission using a rateless coding scheme and enabled for data transmission using a non-rateless coding scheme.

13. The method according to claim 12, further comprising: A cyclic redundancy check portion of the downlink control information is scrambled using a radio network temporary identifier that disables feedback information for the data transmission based at least in part on the determination.

14. The method according to claim 12, further comprising: A field in the downlink control information is configured to indicate disabling of feedback information for the data transmission.

15. The method of claim 14, wherein the field comprises one or more bits associated with the rateless coding scheme configured with no feedback information for the UE, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a hybrid automatic repeat / request process number, or a combination thereof.

16. The method according to claim 12, further comprising: The downlink control information is sent in a first portion of the resources associated with the downlink control information or in a second portion of the resources associated with the downlink control information, wherein sending the downlink control information in the first portion or the second portion indicates disabling feedback information for the data transmission.

17. The method of claim 16, wherein the resources associated with the downlink control information comprise a control resource set, a search space set, or both.

18. The method according to claim 12, further comprising: A radio resource control configuration is sent that indicates the semi-persistent scheduling configuration associated with the data transmission, wherein the radio resource control configuration indicates disabling of feedback information for the data transmission based at least in part on the radio resource control configuration.

19. The method of claim 18, wherein the radio resource control configuration comprises a semi-persistent scheduling configuration indication, a configured grant configuration indication, or both.

20. The method of claim 12, further comprising: A hybrid automatic repeat / request process number indicated in the downlink control information is selected, wherein the hybrid automatic repeat / request process number indicates disabling feedback information for the data transmission.

21. The method of claim 20, wherein a first set of hybrid automatic repeat / request process numbers indicates that the feedback information is disabled for the data transmission using the rateless coding scheme, and a second set of hybrid automatic repeat / request process numbers indicates that the feedback information is enabled for data transmission using a non-rateless coding scheme.

22. The method according to claim 12, further comprising: A UE capability message is received, the UE capability message indicating support for performing or monitoring the data transmission associated with a rateless coding scheme with the feedback information disabled, wherein the downlink control information is based at least in part on the UE capability message.

23. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving downlink control information, the downlink control information comprising a grant scheduling data transmission for the UE, the data transmission associated with a rateless coding scheme; determining feedback information for the data transmission based at least in part on the rateless coding scheme and one or more of: the downlink control information, resources associated with the downlink control information, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission according to the downlink control information and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission based on the determination, wherein When it is determined to disable feedback information for the data transmission, the feedback information is disabled for data transmission using a rateless coding scheme and enabled for data transmission using a non-rateless coding scheme.

24. The device of claim 23, wherein the instructions are further executable by the processor to cause the device to: identifying a radio network temporary identifier used to scramble a cyclic redundancy check portion of the downlink control information; and Determining to disable feedback information for the data transmission is based at least in part on the radio network temporary identifier.

25. The device of claim 23, wherein the instructions are further executable by the processor to cause the device to: Determining to disable feedback information for the data transmission is based at least in part on a field indicated in the downlink control information.

26. The apparatus of claim 25, wherein the field comprises one or more bits associated with the rateless coding scheme configured with no feedback information for the UE, a modulation and coding scheme field, a new data indicator, a redundancy version field, a downlink allocation index field, a transmit power control field, a physical uplink shared channel resource indicator, a physical downlink shared channel to feedback information timing indicator field, a hybrid automatic repeat / request process number, or a combination thereof.

27. The device of claim 23, wherein the instructions are further executable by the processor to cause the device to: receiving the downlink control information in a first portion of the resources associated with the downlink control information or a second portion of the resources associated with the downlink control information; and Determining to disable feedback information for the data transmission is based at least in part on the downlink control information received in the first portion of the resources or the second portion of the resources.

28. The apparatus of claim 27, wherein the resources associated with the downlink control information comprise a control resource set, a search space set, or both.

29. An apparatus for wireless communication at a base station, comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: determining to disable feedback information for data transmission with a user equipment (UE), the data transmission being associated with a rateless coding scheme; transmitting downlink control information, the downlink control information including a grant to schedule the data transmission, the feedback information for the data transmission being enabled or disabled based at least in part on the rateless coding scheme and one or more of: the downlink control information, resources associated with the downlink control information, or a semi-persistent scheduling configuration associated with the data transmission; performing or monitoring the data transmission according to the downlink control information and the rateless coding scheme; and performing or monitoring the feedback information for the data transmission based on the determination, wherein When it is determined to disable feedback information for the data transmission, the feedback information is disabled for data transmission using a rateless coding scheme and enabled for data transmission using a non-rateless coding scheme.

30. The device of claim 29, wherein the instructions are further executable by the processor to cause the device to: A cyclic redundancy check portion of the downlink control information is scrambled using a radio network temporary identifier that disables feedback information for the data transmission based at least in part on the determination.

31. A computer-readable medium having program code recorded thereon, wherein: The program code may be executed by one or more processors of a user equipment (UE) to cause the processors to perform the method according to any one of claims 1 to 11.

32. A computer-readable medium having program code recorded thereon, wherein: The program code may be executed by one or more processors of a base station to cause the processors to perform the method according to any one of claims 12 to 22.

Images