Information instructions for Raptor Code

Abstract

Methods, systems, and devices for wireless communications are described. An encoding device (e.g., a network entity or user equipment (UE)) can communicate an indication of an encoding symbol identifier (ESI), a source block number (SBN), or both, to a decoding device in downlink control information (DCI). By way of example, the indication of the SBN and / or ESI can be transmitted using either an unused field or a repurposed field in the downlink control information (DCI) that schedules a transmission including the encoding symbols, or in a new DCI piggybacked on a downlink shared channel transmission including the encoding symbols. Additionally or alternatively, in a first option, the ESI can be explicitly indicated by the DCI. In another option, the network entity can indicate (e.g., via radio resource control messaging) a configuration for implicitly determining the ESI based on information conveyed in the DCI.

Description

[Technical Field]

[0001] introduction The following relates to wireless communications, including information indication(s) for Raptor Code.

[0002]

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and so on. These systems may be capable of supporting 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), LTE-Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes 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 FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM), etc. A wireless multiple-access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses that support information indication for Raptor codes. For example, the described technology provides a coding device (e.g., a network entity or user equipment (UE)) for communicating an indication of encoded symbol identifier(s) (ESI) and / or source block numbers (SBN) for coding symbols associated with a set of source symbols via a rateless code to a decoding device in downlink control information (DCI). By way of example, the indication of SBN and / or ESI can be transmitted using either unused or repurposed fields in downlink control information (DCI) that schedules a transmission including the coding symbols, or in a new DCI piggybacked on a downlink shared channel transmission including the coding symbols. Additionally or alternatively, in a first option, the ESI(s) can be explicitly indicated by the DCI. In another option, the network entity may indicate (e.g., via radio resource control (RRC) messaging) a configuration for implicitly determining the ESI based on information conveyed in the DCI.

[0004] A method of wireless communication in a first network node is described. The method can include participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including the indication in a diverted field, receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of the plurality of source symbols via a rateless code, and decoding the one or more coding symbols based on the SBN to determine the set of the plurality of source symbols.

[0005] A first network node for wireless communication is described, which may include a memory and at least one processor coupled to the memory, wherein the at least one processor is configured to participate in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a diverted field, receive one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of the plurality of source symbols via a rateless code, and decode the one or more coding symbols based on the SBN to determine the set of the plurality of source symbols.

[0006] Another apparatus for wireless communication in a first network node is described, which may include: means for participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including the indication in a diverted field; means for receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of the plurality of source symbols via a rateless code; and means for decoding the one or more coding symbols based on the SBN to determine the set of the plurality of source symbols.

[0007] A non-transitory computer-readable medium storing code for wireless communications in a first network node is described, the code may include instructions executable by a processor to: receive one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of source symbols via a rateless code, and to decode the one or more coding symbols based on the SBN to determine the set of the plurality of source symbols;

[0008]

[0008] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, decoding one or more coding symbols may include operations, features, means, or instructions for decoding one or more coding symbols based on one or more ESI, wherein the DCI includes an indication of one or more ESI corresponding to the one or more coding symbols.

[0009]

[0009] Some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for participating in the communication of an RRC message indicating one or more parameters and determining one or more ESI corresponding to one or more coding symbols based on the one or more parameters and first information included in the DCI, and decoding the one or more coding symbols includes decoding the one or more coding symbols based on the one or more ESI.

[0010] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, the first information includes scheduling information.

[0011]

[0011] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, the scheduling information includes a location of one or more resource blocks, a system frame number, a slot number, or a symbol number.

[0012] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, the first information includes a DCI sequence corresponding to the DCI.

[0013] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, participating in the communication of a DCI may include acts, features, means, or instructions for receiving the DCI.

[0014]

[0014] In some embodiments of the methods, devices, and non-transitory computer-readable media described herein, participating in communication of DCI may include an action, feature, means, or instruction for transmitting DCI.

[0015]

[0015] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, decoding one or more encoding symbols may include operations, features, means, or instructions for determining a set of multiple source symbols from the one or more encoding symbols based on a Raptor code, and the rateless code may be a Raptor code.

[0016] A method of wireless communication in a first network node is described, the method may include participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including an indication in a diverted field, and transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols of the set of the plurality of source symbols via a rateless code.

[0017]

[0017] A first network node for wireless communication is described, which may include a memory and at least one processor coupled to the memory, wherein the at least one processor is configured to participate in communicating a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a diverted field, and to transmit one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of the plurality of source symbols via a rateless code.

[0018] Another apparatus for wireless communication in a first network node is described, which may include: means for participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including an indication in a repurposed field; and means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols of the set of the plurality of source symbols via a rateless code.

[0019] A non-transitory computer-readable medium storing code for wireless communication in a first network node is described, the code may include instructions executable by a processor to transmit one or more coding symbols to a first network node participating in a communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a repurposed field, and one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols from the set of multiple source symbols via a rateless code.

[0020]

[0020] In some embodiments of the methods, devices, and non-transitory computer-readable media described herein, the DCI includes an indication of one or more ESI corresponding to one or more encoding symbols.

[0021]

[0021] Some embodiments of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for participating in the communication of an RRC message indicating one or more parameters for determining one or more ESI corresponding to one or more encoding symbols.

[0022] In some embodiments of the methods, apparatus, and non-transitory computer-readable media described herein, participating in the communication of a DCI may include acts, features, means, or instructions for receiving a DCI.

[0023]

[0023] In some embodiments of the methods, devices, and non-transitory computer-readable media described herein, participating in communication of DCI may include an action, feature, means, or instruction for transmitting DCI.

[0024]

[0024] Some embodiments of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for generating one or more encoding symbols from a set of multiple source symbols based on a Raptor code, and the rateless code may be a Raptor code. [Brief explanation of the drawings]

[0025] [Figure 1]

[0025] A diagram illustrating an example of a wireless communication system that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. [Figure 2]

[0026] FIG. 1 illustrates an example of a wireless communication system that supports information indication for Raptor codes, in accordance with one or more aspects of the present disclosure. [Figure 3]

[0027] FIG. 1 illustrates an example of a Raptor encoding scheme that supports information indication for Raptor codes, in accordance with one or more aspects of the present disclosure. [Figure 4]

[0028] FIG. 1 illustrates an example of a decoding scheme supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 5]

[0029] FIG. 1 illustrates an example of a resource diagram supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 6]

[0030] FIG. 1 illustrates an example process flow for supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 7]

[0031] FIG. 1 is a block diagram of a device that supports information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 8] FIG. 1 is a block diagram of a device that supports information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 9]

[0032] FIG. 1 is a block diagram of a communications manager supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 10]

[0033] FIG. 1 is a diagram of a system including a UE that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. [Figure 11]

[0034] FIG. 1 is a diagram of a system including network entities that support information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 12]

[0035] 1 is a flowchart illustrating a method for supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 13] 1 is a flowchart illustrating a method for supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. [Figure 14] 1 is a flowchart illustrating a method for supporting information indication for Raptor code, in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0026]

[0036] A first network node, such as a user equipment (UE) in the downlink or a network entity in the uplink, may receive a transmission including a set of encoding symbols from a second network node, such as a network entity in the downlink or a UE in the uplink. The encoding symbols may be encoded according to a Raptor code. In the Raptor code, several source symbols may be identified for transmission. The source symbols may be encoded into multiple encoding symbols that are actually transmitted (instead of transmitting the source symbols directly). Each encoding symbol may be associated with one or more of the source symbols. When a receiving network node (e.g., a decoding device) receives a sufficient number of encoding symbols, the receiving network node may decode the encoding symbols to determine the source symbols. The transmitted one or more encoding symbols may include a source block number (SBN) that links the transmitted encoding symbol(s) to the source symbols and an encoding symbol identifier (ESI) for each encoding symbol in the transmission. However, including the SBN and ESI(s) in the transmitted packet may result in increased overhead, which may be undesirable when using Raptor codes at the radio-link control (RLC) or physical (PHY) layers. Additionally, if the header is not received correctly, soft combining of the received packet is not available, since failure to decode the header means that the symbol information is unknown.

[0027]

[0037] Thus, the encoding device and decoding device may communicate an indication of the ESI, the SBN, or both in downlink control information (DCI) (e.g., instead of a header of a packet of a transmission containing the coding symbols). By way of example, the indication of the SBN and / or the ESI may be transmitted using either an unused field or a repurposed field in the DCI scheduling the transmission containing the coding symbols or in a new DCI piggybacked on a downlink shared channel transmission containing the coding symbols. Additionally or alternatively, in a first option, the ESI may be explicitly indicated by the DCI. In another option, a network entity may indicate a configuration (e.g., via radio resource control (RRC) messaging) for implicitly determining the ESI based on information conveyed in the DCI. The configuration message may include parameters to enable the receiving device to determine the ESI from the scheduling information (e.g., resource block position or slot frame number (SFN)) or via the DCI sequence. For example, a UE may receive the scheduling information and generate the ESI based on a function of the scheduling information.

[0028]

[0038] Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects of the present disclosure are described in the context of Raptor encoding and decoding schemes, resource diagrams, and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts related to information instructions for Raptor codes.

[0029]

[0039] 1 illustrates an example of a wireless communication system 100 that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some aspects, the wireless communication system 100 may be a network operating in accordance with a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0030]

[0040] The network entities 105 may be dispersed throughout a geographic area and may include devices of different types or with different capabilities to form the wireless communication system 100. In various embodiments, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other terms. In some aspects, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be one example of a geographic area within which the network entities 105 and the UEs 115 may support communication of signals according to one or more radio access technologies (RATs).

[0031]

[0041] 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 both at different times. The UEs 115 may be devices of different types or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

[0032]

[0042] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, be, or be included in (e.g., may be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (also sometimes referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may differ relative to these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc. may include disclosure of the UE, base station, apparatus, device, computing system, etc. that are network nodes. For example, a disclosure that a UE is configured to receive information from a base station also discloses that the first network node is configured to receive information from a second network node.Consistent with this disclosure, when a specific example is expanded in accordance with this disclosure (e.g., also disclosing that the UE is configured to receive information from a base station and that the first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in a converse, but broad, open-ended manner. In the above example also disclosing that the UE is configured to receive information from a base station and that the first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, one or more first sets of one or more components, a first processing entity, etc. configured to receive the information, and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0033]

[0043] As described herein, communication of information (e.g., any information, signal, etc.) may be described in various manners using different terms. A disclosure of one communication term includes a disclosure of other communication terms. For example, a first network node may be described as configured to transmit information to a second network node. In this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example, consistent with the present disclosure, a disclosure that a first network node is configured to transmit information to a second network node includes a disclosure that the second network node is configured to receive, acquire, or decode information provided, sent, output, communicated, or transmitted by the first network node.

[0034]

[0044] In some aspects, the network entities 105 may communicate with the core network 130, with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an S1, N2, N3, or other interface protocol). In some aspects, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol), either directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some aspects, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to a midhaul interface protocol), or via the fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or via any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or may include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), among other examples or various combinations thereof. The UE 115 may communicate with the core network 130 via the communication link 155.

[0035]

[0045] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., base transceiver station, radio base station, NR base station, access point, radio transceiver, Node B, eNodeB (eNodeB, eNB), next generation Node B or gigaNode B (all of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), Home Node B, Home eNodeB, or other suitable terminology). In some aspects, the network entities 105 (e.g., base stations 140) may be implemented in a converged (e.g., monolithic, standalone) base station architecture that may be configured to utilize protocol stacks that are physically or logically integrated within a single network entity 105 (e.g., a single RAN node such as the base station 140).

[0036]

[0046] In some aspects, the network entities 105 may be implemented in a split architecture (e.g., split base station architecture, split RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration supported by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT-RIC), a Non-Real Time RIC (Non-RT-RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a disaggregated RAN architecture, one or more components of the network entity 105 may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations).In some aspects, one or more network entities 105 of the split RAN architecture may be implemented as a virtual unit (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0037]

[0047] The division of functionality among the CU 160, the DU 165, and the RU 170 is flexible and can support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed in the CU 160, the DU 165, or the RU 170. For example, a functional division of a protocol stack may be adopted between the CU 160 and the DU 165, such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some aspects, the CU 160 can host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., RRC, service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 can be connected to one or more DUs 165 or RUs 170, which can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., RLC layer, medium access control (MAC) layer) functions and signaling, each of which can be at least partially controlled by the CU 160. Additionally or alternatively, a functional division of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170).In some cases, the functional division between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions related to a protocol layer may be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of the protocol layer may be performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 may be further functionally divided into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some aspects, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented according to an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 105 communicating over such communication link.

[0038]

[0048] In a wireless communication system (e.g., wireless communication system 100), radio access infrastructure and spectrum resources can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with the donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access links and backhaul links (e.g., backhaul communication links 120). An IAB node 104 may include an IAB mobile termination (IAB-MT) that is controlled (e.g., scheduled) by the DU 165 of the associated IAB donor. The IAB-MT may include a separate set of antennas for relaying communications with the UE 115, or may share the same antenna (e.g., of the RU 170) of the IAB node 104 that is used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT, vIAB-MT). In some aspects, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., the IAB node 104, the UE 115) in the relay chain or relay configuration of the access network (e.g., downstream).In such cases, one or more components of the split RAN architecture (e.g., one or more IAB nodes 104, or components of an IAB node 104) may be configured to operate in accordance with the techniques described herein.

[0039]

[0049] For example, an access network (AN) or RAN may include communications between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., also an RU 170), where the CU 160 can communicate with the core network 130 over an interface (e.g., a backhaul link). The IAB donor and IAB node 104 can communicate over an F1 interface according to a protocol (e.g., F1 AP protocol) that defines signaling messages. Additionally or alternatively, CU160 may communicate with the core network via an interface that may be an example of a portion of a backhaul link, and may communicate with other CU160 (e.g., CU160 associated with an alternative IAB donor) via an Xn-C interface that may be an example of a portion of a backhaul link.

[0040]

[0050] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access to the UE 115, wireless self-backhaul capability). The DU 165 may function as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may function as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay a transmission for a UE via one or more other IAB nodes 104). Additionally or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or relay configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 can provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or UE 115.

[0041]

[0051] For example, the IAB node 104 may be referred to as a parent node that supports communication for a child IAB node, or as a child IAB node that is associated with an IAB donor, or both. The IAB donor may include a CU 160 that has a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130 and may function as a parent node for the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may directly signal transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data can be relayed to and from the IAB node 104 via signaling over the NR Uu interface to the MT of the IAB node 104. Communications with the IAB node 104 can be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 can also be scheduled by the DU 165 of the IAB node 104.

[0042]

[0052] For the techniques described herein applied in the context of a split RAN architecture, one or more components of the split RAN architecture may be configured to support the information indication for the Raptor codes described herein. For example, some operations described as being performed by the UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0043]

[0053] The UE 115 may include or 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, and a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or 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 aspects, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (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 an appliance, a vehicle, or a meter, among other examples.

[0044]

[0054] The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as shown in FIG. 1, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples.

[0045]

[0055] The UE 115 and the network entity 105 can communicate wirelessly with each other over one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating 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 may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation on the carrier, user data, or other signaling. The wireless communication system 100 can support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communications between the network entity 105 and other devices may refer to communications between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "transmitting," "receiving," or "communicating" may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or through one or more other network entities 105).

[0046]

[0056] In some aspects, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operation with respect to other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for detection by the UE 115. A carrier may operate in a standalone mode, in which initial acquisition and connection by the UE 115 may be accomplished via that carrier, or the carrier may operate in a non-standalone mode, in which connection is anchored using a different carrier (e.g., of the same radio access technology or a different radio access technology).

[0047]

[0057] The communication links 125 shown in the wireless communication system 100 may include, among other transmission configurations, downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., reverse link transmissions) from the UE 115 to the network entity 105, or both. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

[0048]

[0058] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some aspects the carrier bandwidth may be referred to as the “system bandwidth” of that carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) for a particular radio access technology carrier. Devices (e.g., network entities 105, UEs 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communication using a particular carrier bandwidth or may be configurable to support communication using one of a set of carrier bandwidths. In some aspects, the wireless communication system 100 may include network entities 105 or UEs 115 that support simultaneous communication using carriers associated with multiple carrier bandwidths. In some aspects, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0049]

[0059] A signal waveform transmitted over a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing may be inversely proportional. The amount 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), such that a relatively large amount of resource elements (e.g., within a transmission duration) and a relatively higher-order modulation scheme can accommodate a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), where the use of multiple spatial resources can improve the data rate or data integrity for communication with the UE 115.

[0050]

[0060] The time interval for the network entity 105 or the UE 115 may be, for example, T s =1 / (Δf max N f ) seconds, in which case Δf max may represent the supported subcarrier spacing, and N f may represent the supported Discrete Fourier Transform (DFT) sizes. The communication resource time intervals 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 0 to 1023).

[0051]

[0061] Each frame may include multiple subframes or slots that are numbered consecutively, and each subframe or slot may have the same duration. In some aspects, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain amount of slots. Alternatively, each frame may include a variable amount of slots, and the amount of slots may depend on the subcarrier spacing. Each slot may include a certain amount of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a slot may be further divided into multiple minislots, which are associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be divided into one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.

[0052]

[0062] A subframe, slot, minislot, 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 aspects, the TTI duration (e.g., the amount of symbol periods within 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)).

[0053]

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

[0054]

[0064] The network entity 105 may provide communication coverage via one or more cells, e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used in connection with communication with the network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), etc.) for distinguishing neighboring cells. In some aspects, a cell may also refer to a coverage area 110 in which the logical communication entity operates, or a portion (e.g., a sector) of the coverage area 110. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area, depending on various factors, such as the capabilities of the network entity 105. For example, a cell may be or include, among other examples, a building, a subset of a building, or an outside space between or overlapping with a coverage area 110.

[0055]

[0065] A macro cell generally covers a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 115 that subscribe to service with the network provider that supports the macro cell. A small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) compared to a macro cell, and the small cell may operate using the same or a different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that subscribe to service with the network provider, or it may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in their homes or offices). The network entity 105 may support one or more cells and may also support communication via those one or more cells using one or more component carriers.

[0056]

[0066] In some aspects, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and therefore may provide communication coverage for moving coverage areas 110. In some aspects, different coverage areas 110 associated with different technologies may overlap, but may be supported by the same network entity 105. In some other embodiments, overlapping coverage areas 110 associated with different technologies may also be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network where different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0057]

[0067] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and transmissions from different network entities 105 may not be aligned in time in some aspects. The techniques described herein may be used in connection with either synchronous or asynchronous operation.

[0058]

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

[0059]

[0069] In some aspects, the UEs 115 may be configured to support direct communication with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P) protocol, a D2D protocol, or a sidelink protocol). In some aspects, one or more UEs 115 of a group performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) and may support aspects of such D2D communication being configured (e.g., scheduled) by the network entity 105. In some aspects, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105 or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some aspects, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, with each UE 115 transmitting to each of the other UEs 115 in the group. In some aspects, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other embodiments, D2D communication may occur between UEs 115 without the involvement of the network entity 105.

[0060]

[0070] 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 5G core (5G core, 5GC), which 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 entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be forwarded through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may connect to IP services 150 associated with one or more network operators. The IP services 150 may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0061]

[0071] The wireless communication system 100 can operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, these waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communications using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequency and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0062]

[0072] The wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands, such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some aspects, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0063]

[0073] The network entity 105 (e.g., base station 140, RU 170) or the 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 network entity 105 or the UE 115 may be arranged in one or more antenna arrays or antenna panels that support MIMO operations or are capable of transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly, such as an antenna tower. In some aspects, the antennas or antenna arrays associated with the network entity 105 may be located in various geographic locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming of communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that are capable of supporting various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted through the antenna ports.

[0064]

[0074] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjusting signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals carried through its associated antenna element. The adjustment associated with each of the antenna elements can be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the transmitting or receiving device's antenna array or some other orientation).

[0065]

[0075] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation 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 along different directions by the network entity 105. For example, the network entity 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. The transmissions along different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the network entity 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the network entity 105.

[0066]

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

[0067]

[0077] In some aspects, transmission by a device (e.g., by the network entity 105 or the UE 115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 can report feedback indicating precoding weights for one or more beam directions, which may correspond to a set of configured beams across the system bandwidth or one or more subbands. The network entity 105 can transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may be precoded or non-precoded. The UE 115 can provide feedback regarding 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, or a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by the network entity 105 (e.g., base station 140, RU 170), the UE 115 may employ similar techniques to transmit a signal multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or to transmit a signal along a single direction (e.g., to transmit data to a receiving device).

[0068]

[0078] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals from the receiving device (e.g., network entity 105), such as a synchronization signal, a reference signal, a beam selection signal, or other control signals. For example, the receiving device may perform receiving according to multiple receiving directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as “listening” according to different receiving configurations or receiving directions. In some aspects, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receiving configuration may be aligned along a beam direction determined based on listening along different receiving configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening along multiple beam directions).

[0069]

[0079] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate over logical channels. The MAC layer may perform priority handling and multiplexing of logical channels onto transport channels. The MAC layer may also implement error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide establishment, configuration, and maintenance of an RRC connection between the UE 115 and the network entity 105 or core network 130 supporting radio bearers for user plane data. The PHY layer may map transport channels to physical channels.

[0070]

[0080] The UE 115 and the network entity 105 can support retransmission of data to increase the likelihood of successful reception. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood of correct reception of data over a communication link (e.g., communication link 125, D2D communication link 135). HARQ may 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 in poor radio conditions (e.g., low signal-to-noise conditions). In some aspects, a device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback within a particular slot regarding data received via previous symbols in that slot. In some other embodiments, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0071]

[0081] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless network, e.g., a wireless local area network (WLAN) such as a Wi-Fi (i.e., Institute of Electrical and Electronics Engineers (IEEE) 802.11) network, may include access points (APs) that can communicate with one or more wireless or mobile devices. An AP may be coupled to a network, such as the Internet, and may enable mobile devices to communicate over the network (or with other devices coupled to the access point). Wireless devices may communicate bidirectionally with network devices. For example, in a WLAN, a device may communicate with an associated AP via a downlink (e.g., a communication link from the AP to the device) and an uplink (e.g., a communication link from the device to the AP). A wireless personal area network (PAN), which may include a Bluetooth® connection, may provide short-range wireless connectivity between two or more paired wireless devices. For example, a wireless device such as a cellular phone may utilize wireless PAN communications to exchange information such as audio signals with a wireless headset.

[0072]

[0082] In some cases, the coding device (e.g., UE 115 or network entity 105) may perform fountain coding. A fountain code, sometimes called a network code because it is applied in the network layer, may be a rateless code whose generator matrix may have infinite columns. Performing fountain coding means that the coding device divides an RLC service data unit (SDU) into K data blocks s1,...,sK It may involve splitting into, and each data block may contain the same number of bits. The encoding device then uses the mother generation matrix to encode the K data blocks into Z packets p1,..., p z It may be encoded into. For example, the encoding device may

[0073]

Number

[0074] can be determined as, where H kz represents the value of the entry in the k-th row and z-th column of the mother generation matrix H. Each of the Z packets can correspond to a different column of the mother generation matrix.

[0075] [[ID=​​​​​​​​​​​​​​​

number

[0078] may be equal to, where:

[0079]

number

[0080] is the inverse generator matrix G -1 In general, if a generator matrix G with Q data blocks is invertible, or if the invertible generator matrix G has a rank of K, then the data blocks can be recovered. For conventional ARQ, the original generator matrix may start with an identity matrix.

[0081]

[0085] One type of fountain coding is Luby transform (LT) coding. LT coding is performed by selecting a degree d from a degree distribution. i randomly selected, and may be a type of data block with uniform distribution, d i LT decoding (e.g., belief-propagation (BP) decoding) may involve randomly selecting distinct source symbols s and combining them (e.g., performing one or more exclusive-or (XOR) operations). i (e.g., the coding symbol whose degree is 1) j The decoding device may then find s i A j may be set equal to s i For each coding symbol connected to s i may be XORed with the source symbol s i Such a procedure may be performed by removing each edge connected to s for each value of i. i may continue until one source symbol is determined.

[0082]

number

[0083] If there is no encoding symbol connected only to i o The decoding process may fail for values ​​of . Alternatively, the decoding device may perform a Gaussian elimination (GE) process to decode the encoding symbols.

[0084]

[0086] Raptor coding may be an extension of LT coding. For example, performing Raptor coding may be similar to performing low-density parity check (LDPC) and LT coding, where the number of degrees is equal to or less than a threshold amount (e.g., 3 or less). Raptor codes may be applied for multimedia broadcast multicast services (MBMS). Additionally or alternatively, network codes that may include Raptor codes may be used for IAB.

[0085]

[0087] In some aspects, a decoding device (e.g., a UE 115 or a network entity 105) may receive a set of packets from an encoding device (e.g., a network entity 105 or a UE 115). The header for each of the packets may include an SBN and an ESI for each encoding symbol. The SBN may be an integer identifier for the source block to which the encoding symbol in the packet pertains (e.g., the first 16 bits of the header), and the ESI may be an integer identifier for the encoding symbol in the packet (e.g., the last 16 bits of the header). Each packet may also include one or more encoding symbols. Based on the SBN and the ESI, the encoding device and / or the decoding device may determine which source symbols are selected to generate the encoding symbols. In some aspects, the encoding device may perform triple generation based on the ESI. For example, the encoding device may determine (d, a, b) = Trip(K, X), where K is the number of source symbols and X is the ESI value. In general, d may be equal to Deg[v], where v is equal to Rand[Y,0,2 20 ] and Y may be equal to (B+X*A)%Q, where Q is 2 M , L', or the smallest prime number greater than or equal to K, where M may be the size in bits of K or X, and % is the modulo operator. In an embodiment where M=16, A may be equal to (53591+J(K)*997)%Q, and B may be equal to 10267*(J(K)*997)%Q, where J(K) may be a systematic index associated with K. Additionally, a may be equal to 1+Rand[Y,1,L'-1], and b may be equal to Rand[Y,2,L'], where L' is equal to the smallest prime number greater than or equal to L, and L=K+S+H, where S may correspond to the number of LDPC symbols, and H may correspond to the number of half-symbols.

[0086]

[0088] The symbolization device may perform LT code symbol generation based on triple generation. For example, the symbolization device can determine P encoded symbols according to LTEnc(K,C[0],C[1],...,C[L-1],(d,a,b)). For example, the decoding device may determine b=(b+a)%L’ until b<L while b≧L, and the result may be C[b]. Then, for j=1,...,min(d-1,L-1), the decoding device can determine b=(b+a)%L. Then, while b≧L, the decoding device can determine b=(b+a)%L’ until b<L. Then, the decoding device can determine result=result C[b] and can return the result. Additional details about the encoded symbols can be described with reference to FIG. 3.

[0087]

[0089] In some aspects, the Raptor code can be used as an erasure correction code (e.g., within the application layer). In such an embodiment, each encoded symbol may either be correctly decoded or discarded. Thus, SBN and ESI may be added to the encoded symbols as a header file. However, when the Raptor code is used in the RLC layer or the PHY layer, using SBN and ESI as a header file for the encoded symbols can be disadvantageous. For example, if the decoding device cannot correctly decode an encoded symbol, the decoding device may not have access to the SBN and ESI information. Thus, the decoding device may lose the soft information of each of the encoded symbols and may not be able to determine which source symbols were selected to generate the encoded symbols. In such a case, the decoding device may not be able to perform soft combining, where soft combining refers to a procedure by which the decoding device can combine a first redundant version of a code block with a second code block of a second redundant version to assist decoding.

[0088]

[0090] According to various aspects described herein, the encoding device and decoding device may communicate the ESI(s) and SBN separately from the coding symbols. For example, an indication of the SBN and / or ESI(s) may be transmitted using either an unused field or a repurposed field in the DCI scheduling the transmission including the coding symbols or in a new DCI piggybacked on a downlink shared channel transmission including the coding symbols. Additionally or alternatively, in a first option, the ESI(s) may be explicitly indicated by the DCI. In another option, the network entity 105 may indicate (e.g., via RRC messaging) a configuration for implicitly determining the ESI based on information conveyed in the DCI. The configuration message may include parameters to enable the receiving device to determine the ESI from the scheduling information (e.g., resource block location or SFN) or via the DCI sequence. For example, the UE 115 may receive the scheduling information and may generate the ESI based on a function of the scheduling information.

[0089]

[0091] 2 illustrates an example of a wireless communication system 200 that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. In some aspects, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the encoding device 205 and the decoding device 210 may each be an example of a UE 115 or a network entity 105, as described with reference to FIG. 1.

[0090]

[0092] At an initial time, encoding device 205 may have a set of source symbols to present to decoding device 210. In general, each piece of data of length n bits can be partitioned into K=n / l input symbols (e.g., source symbols), where each input symbol can contain l bits. Encoding device 205 may use these K symbols to generate encoded symbols. To generate each encoded symbol, encoding device 205 may encode the set of source symbols using a rateless code. For example, when performing Raptor coding, encoding device 205 may select a degree d from a degree distribution. i may be selected, at least one of the source symbols may be selected according to the identified degree, and an encoding symbol may be generated based on the selected at least one of the source symbols. More details about Raptor coding may be described elsewhere herein, for example, with reference to FIG. 3.

[0091]

[0093] Each set of encoding symbols may have an associated ESI and SBN. To communicate the ESI, encoding device 205 may communicate an ESI indication 215 (e.g., an indication of the set of ESI) with decoding device 210 over a control channel, e.g., over DCI as described herein.

[0092]

[0094] Whether the encoding device 205 or the decoding device 210 provides the ESI indication 215 may depend on the type of communication to be performed between the encoding device 205 and the decoding device 210. For example, in the case of uplink communication, the decoding device 210 may send the ESI indication 215 to the encoding device 205. In the case of downlink communication, the encoding device 205 may send the ESI indication 215 to the decoding device 210. In the case of sidelink communication, the encoding device 205 or the decoding device 210 may send the ESI indication 215.

[0093]

[0095] To communicate the SBN, the encoding device 205 can communicate the SBN indication 220 (e.g., an indication of SNB) with the decoding device 210 over a control channel, for example, in a DCI that schedules the transmission of the encoded symbols or in a repurposed field in a DCI piggybacked on a downlink shared channel transmission that includes the encoded symbols. As another example, the SBN indication 220 can be transmitted via a MAC control element (MAC-CE) that schedules the transmission of the encoded symbols.

[0094]

[0096] Whether the encoding device 205 or the decoding device 210 provides the SBN indication 220 may be based on the type of communication to be performed between the encoding device 205 and the decoding device 210. For example, for uplink communication, the decoding device 210 may send the SBN indication 220 to the encoding device 205. For downlink communication, the encoding device 205 may send the SBN indication 220 to the decoding device 210. For sidelink communication, the encoding device 205 or the decoding device 210 may send the SBN indication 220.

[0095]

[0097] The encoding device 205 may transmit the coded transmission 225 to the decoding device 210 via a data channel. In some aspects, before transmitting the coded transmission 225, and if the coded transmission 225 is for downlink communication, the encoding device 205 may schedule a downlink data channel (e.g., a physical downlink shared channel (PDSCH)), generate ESI based on the scheduling information, and perform triple generation and LT coding symbol generation (e.g., as described in FIG. 1 ) using the ESI to generate a set of coding symbols. The coded transmission 225 may include a first transport block (TB) that may be divisible or segmentable into K first code blocks (CBs) using channel coding (e.g., K is a positive integer such as 6). Each first CB may include a respective set of packets, and each set of packets may include one or more of the sets of coding symbols. In examples in which the scheduling information provides the ESI indication 215, the scheduling information may indicate resources that the decoding device 210 may use to receive the coded transmission 225 and / or that the encoding device 205 may use to transmit the coded transmission 225. The coded transmission 225 may exclude any indication of the set of ESI, the SBN, or both, based on the encoding device 205 communicating the ESI indication 215, the SBN indication 220, or both, respectively, with the decoding device 210. If the decoding device 210 determines the ESI from the scheduling information, the coded symbols may be transmitted at least partially out of order but may also be transmitted based on the calculated ESI (e.g., based on the result of f(scheduling information)).

[0096]

[0098] Decoding device 210 may receive encoded transmission 225 and may decode one or more encoding symbols for each set of packets, sometimes referred to as a set of encoding symbols. In some aspects, decoding device 210 may decode the set of encoding symbols based on the set of ESI, the SBN, or both. For example, decoding device 210 may perform decoding according to a Raptor code on the set of encoding symbols to generate a set of source symbols. In some aspects where encoded transmission 225 is a downlink transmission, decoding device 210 may generate ESI based on received scheduling information.

[0097]

[0099] After receiving the encoded transmission 225, the decoding device 210 may provide feedback to the encoding device 205. The type of feedback that the decoding device 210 provides may depend on whether the decoding device successfully recovered the set of source symbols. For example, if the decoding device 210 successfully recovers each source symbol in the set of source symbols (e.g., the decoding device 210 successfully decodes each CB in the TB), the decoding device 210 may send an acknowledgement message (e.g., an acknowledgement (ACK)) to the encoding device 205. Alternatively, if the decoding device 210 is not able to successfully recover each source symbol in the set of source symbols (e.g., the decoding device 210 is not able to successfully decode at least one first CB in the first TB), the decoding device 210 may transmit the number of first CBs that the decoding device 210 is not able to decode (e.g., may NACK the first CBs or negatively acknowledged (NACKed) first CBs).

[0098]

[0100] If the decoding device 210 provides the encoding device 205 with the number of NACKed first CBs, the encoding device 205 may perform a retransmission. The retransmission may include a second TB including L=K+N second CBs, where N refers to the number of redundant second CBs. A redundant second CB may be a second CB constructed using multiple first CBs. The K first CBs of the coded transmission 225 may be associated with a first redundancy version (RV), and the K non-redundant second CBs of the retransmission may be associated with a second RV. For example, if the K first CBs of the coded transmission 225 are associated with RV1, the K non-redundant second CBs of the retransmission may be associated with RV2. In a circular buffer, the encoding device 205 may transmit CB_i with RV1, RV2, RV3, etc. The encoding device 205 may consider the K non-redundant second CBs as source symbols of a systematic Raptor code and may generate associated encoding symbols (e.g., N redundant second CBs) for retransmission. If the decoding device 210 cannot decode the N redundant second CBs, the decoding device 210 may perform a decoding process utilizing soft combining, and performing soft combining may be based on the ESI. Additional details about this procedure may be described with reference to FIG. 4. In some cases, the SBN may not change within each HARQ process. Therefore, the SBN indication 220 transmitted for the coded transmission 225 may not need to be retransmitted for the retransmission.

[0099]

[0101] Techniques such as those described herein may have one or more advantages. For example, even if an encoding symbol encoded according to a Raptor code is not correctly decoded, the decoding device 210 may still be able to determine which source symbols were selected to generate the encoding symbol. Additionally, the decoding device 210 may be able to perform soft combining, which may provide soft information of the NACK encoding symbol to the decoding device 210 and thus assist in decoding the source symbol.

[0100]

[0102] 3 illustrates an example of a Raptor encoding scheme 300 that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. In some aspects, the Raptor encoding scheme 300 may be implemented by aspects of the wireless communication system 100. For example, the Raptor encoding scheme 300 may be an example of a scheme by which the encoding device 205 may encode source symbols.

[0101]

[0103] Initially, the encoding device 205 may have a set of source symbols 305. As part of the precoding process, the encoding device 205 may generate intermediate symbols 310. Generating the intermediate symbols 310 may involve mapping each source symbol 305 to a unique intermediate symbol 310. For example, source symbol 305-a may be mapped to intermediate symbol 310-a. Additionally, generating the intermediate symbols may involve mapping multiple source symbols 305 to each of a set of redundant intermediate symbols 315, sometimes referred to as redundant nodes. The redundant intermediate symbols 315 may include S low-density parity-check (LDPC) symbols (e.g., if each source symbol 305 can appear three times across S LDPC symbols). Additionally or alternatively, the redundant intermediate symbols 315 may include H half symbols (e.g., if each encoding symbol 320 can include ceiling(H / 2) source symbols 305). The redundant intermediate symbols 315 may be based on other intermediate symbols 310 (e.g., the first M intermediate symbols 310). The source symbols as described in FIG. 2 may correspond to the source symbols 305 or the intermediate symbols 310.

[0102]

[0104] As part of the LT coding process, the encoding device 205 may generate encoding symbols 320. Generating encoding symbols involves selecting the degree d i and uniformly distribute d iThe encoding method may include choosing or selecting separate intermediate symbols 310 and combining them (e.g., performing one or more XORs). Using a uniform distribution may ensure that each intermediate symbol 310 is selected by approximately the same amount. In one example, encoding device 205 may identify a degree of 2, select intermediate symbol 310-a and another intermediate symbol 310, and combine (e.g., XOR) them to generate encoded symbol 320-a. In another example, encoding device 205 may identify a degree of 1, select intermediate symbol 310-a, and use intermediate symbol 310-a as encoded symbol 320-b. In another example, encoding device 205 may identify a degree of 3, select intermediate symbol 310-a and two other intermediate symbols 310, and combine (e.g., XOR) them to generate encoded symbol 320-c. Some of the encoding symbols 320 may be referred to as systematic symbols 330 and other of the encoding symbols 320 may be referred to as repair symbols 335 .

[0103]

[0105] Performing the procedures described herein may reduce the encoding and decoding complexity of LT codes by lowering their average degrees. In such cases, the encoding device 205 may perform Raptor coding as described herein, which may use LDPC and LT codes (e.g., weak LT codes) with average degrees below a threshold amount (e.g., 3).

[0104]

[0106] 4 illustrates an example of a decoding scheme 400 that supports information indication for Raptor codes in accordance with one or more aspects of the present disclosure. In some aspects, the decoding scheme 400 may be implemented by aspects of the wireless communication system 100. For example, the decoding scheme 400 may be an example of a procedure by which the decoding device 210 can decode a code block of a transmission or retransmission.

[0105]

[0107] As described herein, decoding device 210 may receive an encoded transmission (e.g., encoded transmission 225), where the encoded transmission includes a first TB that can be partitioned into a first set of CBs (e.g., six first CBs, i.e., CB1, CB2, CB3, CB4, CB5, and CB6, having an RV of RV0). Decoding device 210 may perform Raptor decoding on the first set of CBs and may successfully decode a first subset (e.g., CB1, CB3, CB4, and CB5) and may be unable to decode a second subset (e.g., CB2 and CB6). Accordingly, decoding device 210 may provide HARQ feedback to encoding device 205. For example, decoding device 210 may indicate the number of first CBs in the second subset (e.g., 2).

[0106]

[0108] In response, encoding device 205 may send a retransmission including a second TB that can be partitioned into a set of second CBs (e.g., two second CBs, CB7 and CB8, having an RV of RV1). Some of the second CBs may be associated with multiple second CBs. For example, CB7 may be generated by XORing CB2 with CB4, and CB8 may be generated by XORing CB3 with CB5 and CB6.

[0107]

[0109] At 405, decoding device 210 may receive the retransmission. At 410, decoding device 210 may perform first level decoding (e.g., packet CRC or checksum) to attempt to verify the coded bits of the redundant second CBs (e.g., CB7 and CB8). If decoding device 210 successfully receives the coded bits of the redundant second CBs, decoding device 210 may perform Raptor decoding at 415 on the second subset that decoding device 210 was previously unable to decode (e.g., CB2 and CB6 with RV1).

[0108]

[0110] Alternatively, if the decoding device 210 cannot successfully verify that the coded bits of the redundant second CB were correctly received, the decoding device 210 may calculate 420 a log-likelihood ratio (LLR) for the second subset that the decoding device 210 was previously unable to decode. For example, the decoding device 210 may determine the LLR for CB2 with RV1 as LLR(CB7)*sign(CB4) and the LLR for CB6 with RV1 as LLR(CB8)*sign(CB3)*sign(CB5). At 425, the decoding device 210 may perform a soft-combining procedure based on the ESI. For example, the decoding device 210 may combine CB2 of RV1 with CB2 of RV0 and may combine CB6 of RV1 with CB6 of RV0.

[0109]

[0111] At 430, decoding device 210 may successfully attempt to decode the soft-combined second CB. If decoding device 210 is successful and / or if Raptor decoding at 415 is performed, decoding device 210 may transmit an acknowledgement message (e.g., an ACK) to encoding device 205 at 435. If decoding device 210 is unable to successfully decode one or more of the soft-combined second CBs, decoding device 210 may transmit at 440 the number of soft-combined second CBs that decoding device 210 was unable to decode (e.g., 1 if at least one of CB2 and CB6 was successfully decoded, or 2 if neither CB2 nor CB6 was successfully decoded).

[0110]

[0112] In some aspects, after the encoding device 205 receives the number of second CBs that the decoding device 210 was unable to decode, the encoding device 205 may generate a second retransmission that includes a third TB that can be partitioned into a third set of CBs associated with another RV (e.g., RV2). In such an example, the decoding device 210 may repeat the procedures described herein for the second retransmission.

[0111]

[0113] In some aspects, decoding scheme 400 can be applied at a different granularity, for example, decoding scheme 400 can be applied at the coding symbol level instead of the CB level (e.g., a coded transmission can include a first TB that can be partitioned into a set of coding symbols ES1, ES2, ES3, ES4, ES5, and ES6, and schemes 405-440 can be applied to the set of coding symbols).

[0112]

[0114] 5 illustrates example resource diagrams 500 and 505 supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. In some aspects, resource diagrams 500 and 505 may be implemented by aspects of wireless communications system 100. For example, resource diagrams 500 and 505 may illustrate examples of DCI that may indicate SBN and / or ESI for coded symbols transmitted in a shared channel transmission.

[0113]

[0115] As shown in resource diagram 500, DCI 510-a can schedule shared channel transmissions 515, such as a PDSCH or physical uplink shared channel (PUSCH), used to transmit one or more coding symbols. Unused fields of DCI 510-a can be reused or repurposed to indicate SBNs for one or more coding symbols. In some aspects, unused fields of DCI 510-a can be reused or repurposed to indicate ESI for one or more coding symbols.

[0114]

[0116] As shown in resource diagram 505, DCI 510-b may schedule a downlink shared channel transmission 525 (e.g., a PDSCH) used to transmit one or more encoded symbols. The second DCI 520 may be piggybacked on the downlink shared channel transmission 525 (e.g., the downlink shared channel transmission 525 may include the second DCI 520). The decoding device 210 may decode the downlink shared channel transmission 525 and the second DCI 520 separately, and the second DCI 520 may be decoded with higher reliability than the downlink shared channel transmission 525. The decoding device may decode the encoded symbols in the downlink shared channel transmission 525 based on the indication of the SBN and ESI transmitted in the second DCI 520.

[0115]

[0117] FIG. 6 illustrates an example process flow 600 supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. In some aspects, the process flow 600 may implement aspects of the wireless communication system 100. For example, the process flow 600 may be implemented by an encoding device 205-a, which may be an example of an encoding device 205 as described with reference to FIG. 2, and a decoding device 210-a, which may be an example of a decoding device 210 as described with reference to FIG. 2. In the following description of the process flow 600, operations between the encoding device 205-a and the decoding device 210-a may be transmitted in an order different from the example order shown, or operations performed by the encoding device 205-a and the decoding device 210-a may be performed in a different order or at different times. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0116]

[0118] At 610, the encoding device 205-a and the decoding device 210-a may participate in communicating DCI via a rateless code to schedule a transmission including one or more encoding symbols associated with each corresponding set of source symbols among the sets of source symbols. For example, the transmission may be a shared channel transmission (e.g., a PDSCH transmission or a PUSCH transmission).

[0117]

[0119] At 625, encoding device 205-a and decoding device 210-a may participate in communication of a DCI indicating an SBN associated with a source block for the set of multiple source symbols. At 630, encoding device 205-a may transmit one or more encoding symbols scheduled by the DCI communicated at 610. For example, encoding device 205-a may generate encoding symbols from the set of multiple source symbols using a rateless code, such as a Raptor code, at 620 using an SBN and a set of ESI corresponding to the one or more encoding symbols, where the SBN is associated with a source block for the set of multiple source symbols. At 630, encoding device 205-a may transmit the generated one or more encoding symbols via a shared channel transmission scheduled by the DCI at 610.

[0118]

[0120] In some aspects, the DCI indicating the SBN at 625 may be the same DCI communicated at 610 that schedules a transmission including the encoding symbols. In such aspects, the SBN may be indicated in an unused or repurposed field of the DCI. In some aspects, the DCI indicating the SBN at 625 may be included in a downlink shared channel transmission at 630 that includes one or more encoding symbols (e.g., when the encoding device 205-a is a network entity 105 and the decoding device 210-a is a UE).

[0119]

[0121] At 640, the decoding device can decode the encoding symbols based on the indicated SBN.

[0120]

[0122] In some aspects, the DCI indicating the SBN at 625 may include an explicit indication of a set of ESI corresponding to the encoding symbol. Decoding device 210-a may decode one or more encoding symbols based on the indicated set of ESI. For example, if the DCI indicating the SBN at 625 is the same DCI as the DCI communicated at 610 that schedules the transmission including the encoding symbol, another repurposed or unused field within the DCI may indicate the set of ESI. As another example, if the DCI indicating the SBN at 625 is included in a downlink shared channel transmission at 630, the DCI included in the downlink shared channel transmission at 630 may further include an indication of the set of ESI.

[0121]

[0123] In some aspects, the set of ESI may be implicitly indicated by the DCI indicating the SBN at 625 and may be determined by the decoding device 210-a. For example, because the SBN may not change for each HARQ process, the SBN may be explicitly indicated in the DCI as described herein, but the set of ESI may be implicitly indicated and determined by the decoding device 210-a. For example, at 605, the encoding device 205-a and the decoding device 210-a may participate in RRC messaging communication configuring one or more parameters for ESI calculation. For example, the set of ESI may be calculated based on information associated with a DCI scheduling a transmission including a coding symbol and / or a DCI indicating an SBN for the coding symbol. For example, the information associated with a DCI that can be used to determine the set of ESI may be a DCI sequence corresponding to a DCI scheduling a transmission including one or more coding symbols, or the information associated with a DCI that can be used to determine the set of ESI may be scheduling information for a transmission including one or more coding symbols. The RRC messaging at 605 may indicate, for example, whether to use a DCI sequence or scheduling information to determine the set of ESI. Additionally or alternatively, the RRC messaging at 605 may indicate a function for determining the set of ESI from information associated with the DCI.

[0122]

[0124] For example, if a DCI sequence is used to determine the set of ESI, the DCI sequence can be used as input to a hash function that outputs the set of ESI (e.g., ESI = f(DCI sequence)). As another example, if scheduling information is used to determine the set of ESI, the scheduling information can be used as input to a hash function that outputs the set of ESI (e.g., ESI = f(DCI sequence)). For example, the scheduling information may be the location of a resource block, the number of resource blocks, the SFN, a subframe number, a frequency band, a comb number, a modulation and coding scheme, a resource indicator, or a cell radio network temporary identifier (C-RNTI).

[0123]

[0125] Thus, in some aspects, at 615, encoding device 205-a may determine a set of ESI for one or more encoding symbols based on information associated with the DCI communicated at 610. In such aspects, encoding device 205-a may generate encoding symbols from a set of multiple source symbols using the determined set of ESI at 620. At 635, decoding device 210-a may determine a set of ESI for one or more encoding symbols based on information associated with the DCI communicated at 610. In such aspects, decoding device 210-a may decode one or more encoding symbols based on the determined set of ESI at 640. In some aspects, a transmission including one or more encoding symbols at 630 may be scheduled by a MAC-CE instead of a DCI, and thus the MAC-CE may include an indication of the SBN and information from which the set of ESI can be determined (e.g., scheduling information for a transmission including one or more encoding symbols).

[0124]

[0126] In some aspects, the decoding device 210-a may transmit a recognition response message based on decoding one or more encoding symbols at 645. The encoding device 205-a may receive the recognition response message. In some aspects, the decoding device 210-a may transmit an indication of one or more numbers of first CBs that the decoding device 210-a was unable to successfully decode at 650.

[0125]

[0127] In some aspects, the encoding device 205-a may send a retransmission to the decoding device 210-a. The retransmission may include a second TB, where the second TB includes a second set of CBs including a second set of packets associated with the second RV. Each of the first sets of CBs may be associated with a respective first CB of the first set of CBs. In one example, the decoding device 210-a may identify that it failed to decode a CB of the first set of CBs that is not associated with any of the second set of CBs. In such a case, the decoding device 210-a may perform a soft-combining procedure using the first set of CBs and the second set of CBs based on identifying the failure and the generated set of encoding symbols. Additionally, the decoding device 210-a may successfully decode the second set of CBs based on performing the soft-combining procedure. In another example, the decoding device 210-a may decode a CB of the second set of CBs that is not associated with any of the first set of CBs. In such an embodiment, the decoding device 210-a may successfully decode the second set of packets based on decoding a CB that is not associated with any CB in the first set of CBs.

[0126]

[0128] 7 illustrates a block diagram 700 of a device 705 supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. The device 705 may be an example of an aspect of a UE 115 or a network entity 105 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0127]

[0129] The receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to information instructions for Raptor codes). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0128]

[0130] The transmitter 715 can provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 can transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to information instructions for a Raptor code), user data, control information, or any combination thereof. In some aspects, the transmitter 715 can be collocated with the receiver 710 within a transceiver module. The transmitter 715 can utilize a single antenna or a set of multiple antennas.

[0129]

[0131] The communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be examples of means for performing various aspects of the information instructions for the Raptor code described herein. For example, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0130]

[0132] In some aspects, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof, may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or supporting means for performing the functions described in this disclosure. In some aspects, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0131]

[0133] Additionally or alternatively, in some aspects, communications manager 720, receiver 710, transmitter 715, or various combinations or components thereof, may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functionality of communications manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in this disclosure).

[0132]

[0134] In some aspects, the communications manager 720 can be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 can receive information from the receiver 710 and transmit information to the transmitter 715, or can be integrated in combination with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0133]

[0135] The communications manager 720 can support wireless communications in a first network node according to embodiments disclosed herein. For example, the communications manager 720 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including one or more coding symbols, or the DCI including an indication in a diverted field. The communications manager 720 can be configured as or otherwise support a means for receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of multiple source symbols via a rateless code. The communications manager 720 can be configured as or otherwise support a means for decoding the one or more coding symbols based on the SBN to determine the set of multiple source symbols.

[0134]

[0136] Additionally or alternatively, communications manager 720 can support wireless communications in the first network node in accordance with embodiments disclosed herein. For example, communications manager 720 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a diverted field. Communications manager 720 can be configured as or otherwise support a means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of multiple source symbols via a rateless code.

[0135]

[0137] By including or configuring a communications manager 720 in accordance with embodiments described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communications manager 720, or a combination thereof) can support techniques for more efficient utilization of communications resources.

[0136]

[0138] 8 shows a block diagram 800 of a device 805 supporting information indication for Raptor code in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a device 705, a UE 115, or a network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0137]

[0139] The receiver 810 can provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to information instructions for Raptor codes). The information can be passed to other components of the device 805. The receiver 810 can utilize a single antenna or a set of multiple antennas.

[0138]

[0140] The transmitter 815 can provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., a control channel, a data channel, an information channel related to information instructions for a Raptor code). In some aspects, the transmitter 815 can be collocated with the receiver 810 within a transceiver module. The transmitter 815 can utilize a single antenna or a set of multiple antennas.

[0139]

[0141] Device 805 or its various components may be an example of a means for performing various aspects of the information instructions for Raptor codes described herein. For example, communications manager 820 may include an SBN instruction manager 825, an encoding symbol receiving manager 830, a decoding manager 835, an encoding symbol transmitting manager 840, or any combination thereof. Communications manager 820 may be an example of aspects of communications manager 720 as described herein. In some aspects, communications manager 820 or its various components may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 810, transmitter 815, or both. For example, communications manager 820 may receive information from receiver 810 and transmit information to transmitter 815, or may be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0140]

[0142] The communications manager 820 can support wireless communications in a first network node according to embodiments disclosed herein. The SBN indication manager 825 can be configured as or otherwise support a means for participating in the communication of a DCI, where the DCI includes an indication of an SBN associated with a source block for a set of multiple source symbols, where the DCI includes scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, where the DCI is included in a downlink shared channel transmission including one or more coding symbols, or where the DCI includes an indication in a diverted field. The coding symbol reception manager 830 can be configured as or otherwise support a means for receiving one or more coding symbols, where each respective coding symbol of the one or more coding symbols is associated with a respective corresponding set of source symbols among the set of multiple source symbols via a rateless code. The decoding manager 835 can be configured as or otherwise support a means for decoding one or more coding symbols based on the SBN to determine the set of multiple source symbols.

[0141]

[0143] Additionally or alternatively, the communications manager 820 can support wireless communications in the first network node according to embodiments disclosed herein. The SBN indication manager 825 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including one or more coding symbols, or the DCI including an indication in a diverted field. The coding symbol transmission manager 840 can be configured as or otherwise support a means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of multiple source symbols via a rateless code.

[0142]

[0144] 9 illustrates a block diagram 900 of a communications manager 920 supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. Communications manager 920 may be an example of aspects of communications manager 720, communications manager 820, or both, as described herein. Communications manager 920 or various components thereof may be an example of a means for implementing various aspects of information indication for Raptor codes described herein. For example, communications manager 920 may include an SBN indication manager 925, an encoding symbol reception manager 930, a decoding manager 935, an encoding symbol transmission manager 940, an ESI manager 945, an RRC manager 950, a DCI reception manager 955, a DCI transmission manager 960, a Raptor code manager 965, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0143]

[0145] The communications manager 920 can support wireless communications in a first network node according to embodiments disclosed herein. The SBN indication manager 925 can be configured as or otherwise support a means for participating in the communication of a DCI, where the DCI includes an indication of an SBN associated with a source block for a set of multiple source symbols, where the DCI includes scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, where the DCI is included in a downlink shared channel transmission including one or more coding symbols, or where the DCI includes an indication in a diverted field. The coding symbol reception manager 930 can be configured as or otherwise support a means for receiving one or more coding symbols, where each respective coding symbol of the one or more coding symbols is associated with a respective corresponding set of source symbols among the set of multiple source symbols via a rateless code. The decoding manager 935 can be configured as or otherwise support a means for decoding one or more coding symbols based on the SBN to determine the set of multiple source symbols.

[0144]

[0146] In some aspects, to support decoding one or more coding symbols, the ESI manager 945 may be configured as or otherwise support a means for decoding one or more coding symbols based on one or more ESI, where the DCI includes an indication of the one or more ESI corresponding to the one or more coding symbols.

[0145]

[0147] In some aspects, the RRC manager 950 may be configured or otherwise support a means for participating in communication of RRC messages, where the RRC messages indicate one or more parameters. In some aspects, the ESI manager 945 may be configured or otherwise support a means for determining, based on the one or more parameters and the first information included in the DCI, one or more ESI corresponding to one or more coding symbols, where decoding the one or more coding symbols includes decoding the one or more coding symbols based on the one or more ESI.

[0146]

[0148] In some aspects, the first information includes scheduling information.

[0147]

[0149] In some aspects, the scheduling information includes a location, SFN, slot number, or symbol number of one or more resource blocks.

[0148]

[0150] In some aspects, the first information includes a DCI sequence corresponding to the DCI.

[0149]

[0151] In some aspects, to support participation in DCI communications, DCI reception manager 955 may be configured as or otherwise support a means for receiving DCI.

[0150]

[0152] In some aspects, to support participation in the communication of DCI, DCI transmission manager 960 may be configured as or otherwise support a means for transmitting DCI.

[0151]

[0153] In some aspects, to support decoding one or more encoding symbols, the Raptor code manager 965 may be configured with or otherwise support a means for determining a set of source symbols from one or more encoding symbols based on a Raptor code, and the rateless code is a Raptor code.

[0152]

[0154] Additionally or alternatively, communications manager 920 can support wireless communications in the first network node in accordance with embodiments disclosed herein. In some aspects, SBN indication manager 925 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a diverted field. Encoding symbol transmission manager 940 can be configured as or otherwise support a means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of multiple source symbols via a rateless code.

[0153]

[0155] In some aspects, the DCI includes an indication of one or more ESI corresponding to one or more coding symbols.

[0154]

[0156] In some aspects, the RRC manager 950 may be configured or otherwise support a means for participating in the communication of RRC messages, the RRC messages indicating one or more parameters for the determination of one or more ESI corresponding to one or more coding symbols.

[0155]

[0157] In some aspects, to support participation in DCI communications, DCI reception manager 955 may be configured as or otherwise support a means for receiving DCI.

[0156]

[0158] In some aspects, to support participation in the communication of DCI, DCI transmission manager 960 may be configured as or otherwise support a means for transmitting DCI.

[0157]

[0159] In some aspects, the Raptor code manager 965 may be configured as or otherwise support a means for generating one or more encoding symbols from a set of multiple source symbols based on a Raptor code, and the rateless code is a Raptor code.

[0158]

[0160] 10 illustrates a diagram of a system 1000 including a device 1005 supporting information indication for Raptor code in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of, or may include components of, a device 705, a device 805, or a UE 115, as described herein. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communications manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0159]

[0161] The I / O controller 1010 can manage input and output signals for the device 1005. The I / O controller 1010 can also manage peripheral devices not built into the device 1005. In some cases, the I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1010 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 can be implemented as part of a processor, such as the processor 1040. In some cases, a user may interact with the device 1005 through the I / O controller 1010 or through hardware components controlled by the I / O controller 1010 .

[0160]

[0162] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have two or more antennas 1025, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1015 may be capable of bidirectional communication via one or more antennas 1025, a wired link, or a wireless link, as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may be capable of bidirectional communication with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets and providing the modulated packets to one or more antennas 1025 for transmission and for demodulating packets received from the one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and one or more antennas 1025, may be an example of the transmitter 715, the transmitter 815, the receiver 710, the receiver 810, or any combination thereof, or components thereof, as described herein.

[0161]

[0163] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable computer-executable code 1035, which includes instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but (e.g., when compiled and executed) may cause a computer to perform the functions described herein. In some cases, the memory 1030 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0162]

[0164] The processor 1040 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 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be incorporated within the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting information instructions for the Raptor code). For example, the device 1005 or a component of the device 1005 may include a processor 1040 and a memory 1030 coupled to the processor 1040, where the processor 1040 and the memory 1030 are configured to perform various functions described herein.

[0163]

[0165] The communications manager 1020 can support wireless communications in a first network node according to embodiments disclosed herein. For example, the communications manager 1020 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including one or more coding symbols, or the DCI including an indication in a diverted field. The communications manager 1020 can be configured as or otherwise support a means for receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of multiple source symbols via a rateless code. The communications manager 1020 can be configured as or otherwise support a means for decoding the one or more coding symbols based on the SBN to determine the set of multiple source symbols.

[0164]

[0166] Additionally or alternatively, the communications manager 1020 can support wireless communications in the first network node in accordance with embodiments disclosed herein. For example, the communications manager 1020 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a repurposed field. The communications manager 1020 can be configured as or otherwise support a means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of multiple source symbols via a rateless code.

[0165]

[0167] By including or configuring a communications manager 1020 in accordance with embodiments described herein, the device 1005 can support techniques for improved communications reliability, more efficient utilization of communications resources, and improved inter-device coordination.

[0166]

[0168] In some aspects, communications manager 1020 can be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1015, one or more antennas 1025, or any combination thereof. Although communications manager 1020 is shown as a separate component, in some aspects, one or more functions described with reference to communications manager 1020 can be supported or performed by processor 1040, memory 1030, code 1035, or any combination thereof. For example, code 1035 can include instructions executable by processor 1040 to cause device 1005 to perform various aspects of the information instructions for Raptor code described herein, or processor 1040 and memory 1030 can be otherwise configured to perform or support such operations.

[0167]

[0169] FIG. 11 shows a diagram of a system 1100 including a device 1105 supporting information indication for Raptor code in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of or include components of a device 705, a device 805, or a network entity 105 described herein. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, communication via one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support outputting and obtaining communications, such as a communications manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, code 1130, and a processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0168]

[0170] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some aspects, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some aspects, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some aspects, the device 1105 may include one or more antennas 1115 that may be capable of transmitting or receiving (e.g., simultaneously) wireless transmissions. The transceiver 1110 may also include a modem for modulating signals, providing the modulated signals for transmission (e.g., by a wired transmitter, via one or more antennas 1115), receiving the modulated signals (e.g., from a wired receiver, from one or more antennas 1115), and demodulating the signals. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1115 configured to support various receive or acquisition operations, or one or more interfaces coupled with one or more antennas 1115 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1110 may include, or be configured to couple with, one or more processors or memory components operable to perform or support an operation based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof.In some implementations, the transceiver 1110, or the transceiver 1110 and one or more antennas 1115, or the transceiver 1110 and one or more antennas 1115 and one or more processor or memory components (e.g., the processor 1135, or the memory 1125, or both) may be included on a chip or chip assembly installed on the device 1105. In some aspects, the transceiver may be operable to support communication over one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0169]

[0171] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but (e.g., when compiled and executed) may cause a computer to perform functions described herein. In some cases, the memory 1125 may include a BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0170]

[0172] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be incorporated within the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1125) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting information instructions for the Raptor code). For example, the device 1105 or a component of the device 1105 may include the processor 1135 and the memory 1125 coupled to the processor 1135, where the processor 1135 and the memory 1125 are configured to perform various functions described herein. Processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1130) to perform functions of device 1105. Processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored on device 1105 (e.g., in memory 1125). In some implementations, processor 1135 may be a component of a processing system. A processing system may generally refer to a system or set of machines or components that receives inputs, processes the inputs, and generates a set of outputs (e.g., that can be passed to other systems or components of device 1105).For example, the processing system of device 1105 may refer to a system that includes various other components or subcomponents of device 1105, such as processor 1135, or transceiver 1110, or communications manager 1120, or other components or combinations of components of device 1105. The processing system of device 1105 may interface with other components of device 1105 and can process information (e.g., inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1105 may include a processing system and one or more interfaces for outputting information, acquiring information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to output information and acquire information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system and a transmitter of the chip or modem, such that device 1105 can transmit information output from the chip or modem. Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system and a receiver of a chip or modem, such that device 1105 can obtain information or signal input and pass that information to the processing system. Those skilled in the art will readily recognize that a first interface may also obtain information or signal input and a second interface may also output information or signal output.

[0171]

[0173] In some aspects, bus 1140 can support communications of (e.g., within) protocol layers of a protocol stack. In some aspects, bus 1140 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which can include communications performed within a component of device 1105 or between different components of device 1105, which can be collocated or located in different locations (e.g., device 1105 can refer to a system in which one or more of communications manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 can be located in one of or divided among different components).

[0172]

[0174] In some aspects, the communications manager 1120 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1120 may manage the forwarding of data communications for client devices, such as one or more UEs 115. In some aspects, the communications manager 1120 may manage communications with other network entities 105 and may include a controller or scheduler for cooperating with the other network entities 105 to control communications with the UEs 115. In some aspects, the communications manager 1120 may support an X2 interface within LTE / LTE-A wireless communications network technologies to provide communications between network entities 105.

[0173]

[0175] The communications manager 1120 can support wireless communications in the first network node according to embodiments disclosed herein. For example, the communications manager 1120 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including one or more coding symbols, or the DCI including an indication in a diverted field. The communications manager 1120 can be configured as or otherwise support a means for receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a respective corresponding set of source symbols among the set of multiple source symbols via a rateless code. The communications manager 1120 can be configured as or otherwise support a means for decoding the one or more coding symbols based on the SBN to determine the set of multiple source symbols.

[0174]

[0176] Additionally or alternatively, the communications manager 1120 can support wireless communications in the first network node in accordance with embodiments disclosed herein. For example, the communications manager 1120 can be configured as or otherwise support a means for participating in the communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including an indication in a diverted field. The communications manager 1120 can be configured as or otherwise support a means for transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the set of multiple source symbols via a rateless code.

[0175]

[0177] By including or configuring a communications manager 1120 in accordance with embodiments described herein, the device 1105 can support techniques for improved communications reliability, more efficient utilization of communications resources, and improved inter-device coordination.

[0176]

[0178] In some aspects, communications manager 1120 can be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with transceiver 1110, one or more antennas 1115 (e.g., if applicable), or any combination thereof. Although communications manager 1120 is shown as a separate component, in some aspects, one or more functions described with reference to communications manager 1120 can be supported or performed by transceiver 1110, processor 1135, memory 1125, code 1130, or any combination thereof. For example, code 1130 can include instructions executable by processor 1135 to cause device 1105 to perform various aspects of the information instructions for Raptor code described herein, or processor 1135 and memory 1125 can be otherwise configured to perform or support such operations.

[0177]

[0179] FIG. 12 illustrates a flowchart illustrating a method 1200 for supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. The operations of method 1200 may be performed by a UE or a network entity or components thereof as described herein. For example, the operations of method 1200 may be performed by a UE 115 or a network entity as described with reference to FIGS. 1 through 11. In some aspects, the UE or network entity may execute a set of instructions to control functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may perform aspects of the described functions using dedicated hardware.

[0178]

[0180] At 1205, the method may include participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including the indication in a diverted field. The operations of 1205 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1205 may be performed by an SBN indication manager 925 described with reference to FIG. 9.

[0179]

[0181] At 1210, the method may include receiving one or more encoding symbols, each respective encoding symbol of the one or more encoding symbols being associated with a respective corresponding set of source symbols among the plurality of sets of source symbols via a rateless code. The operations of 1210 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1210 may be performed by an encoding symbol reception manager 930 as described with reference to FIG. 9.

[0180]

[0182] At 1215, the method may include decoding one or more encoding symbols based on the SBN to determine a set of source symbols. The operations of 1215 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1215 may be performed by a decoding manager 935 as described with reference to FIG. 9.

[0181]

[0183] FIG. 13 illustrates a flowchart illustrating a method 1300 for supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. The operations of method 1300 may be performed by a UE or a network entity or components thereof as described herein. For example, the operations of method 1300 may be performed by a UE 115 or a network entity as described with reference to FIGS. 1 through 11. In some aspects, the UE or network entity may execute a set of instructions to control functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may perform aspects of the described functions using dedicated hardware.

[0182]

[0184] At 1305, the method may include participating in communication of an RRC message, the RRC message indicating one or more parameters. The operations of 1305 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1305 may be performed by the RRC manager 950 described with reference to FIG. 9.

[0183]

[0185] At 1310, the method may include participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including the indication in a diverted field. The operations of 1310 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1310 may be performed by an SBN indication manager 925 described with reference to FIG. 9.

[0184]

[0186] At 1315, the method may include receiving one or more encoding symbols, each respective encoding symbol of the one or more encoding symbols being associated with a respective corresponding set of source symbols among the sets of source symbols via a rateless code. The operations of 1315 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1315 may be performed by an encoding symbol reception manager 930 as described with reference to FIG. 9.

[0185]

[0187] At 1320, the method may include determining one or more ESI corresponding to the one or more encoding symbols based on the one or more parameters and the first information included in the DCI. The operations of 1320 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1320 may be performed by the ESI manager 945 described with reference to FIG. 9.

[0186]

[0188] At 1325, the method may include decoding one or more encoding symbols based on the SBN to determine a set of source symbols, where decoding the one or more encoding symbols includes decoding the one or more encoding symbols based on the one or more ESI. The operations of 1325 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1325 may be performed by a decoding manager 935 as described with reference to FIG. 9.

[0187]

[0189] FIG. 14 illustrates a flowchart illustrating a method 1400 for supporting information indication for Raptor codes in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be performed by a UE or a network entity or components thereof as described herein. For example, the operations of method 1400 may be performed by a UE 115 or a network entity as described with reference to FIGS. 1 through 11. In some aspects, the UE or network entity may execute a set of instructions to control functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may perform aspects of the described functions using dedicated hardware.

[0188]

[0190] At 1405, the method may include participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a set of multiple source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the set of multiple source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols, or the DCI including the indication in a diverted field. The operations of 1405 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1405 may be performed by an SBN indication manager 925 described with reference to FIG. 9.

[0189]

[0191] At 1410, the method may include transmitting one or more encoding symbols, each respective encoding symbol of the one or more encoding symbols being associated with a corresponding set of source symbols from the plurality of sets of source symbols via a rateless code. The operations of 1410 may be performed in accordance with embodiments as disclosed herein. In some aspects, aspects of the operations of 1410 may be performed by an encoding symbol transmission manager 940 as described with reference to FIG. 9.

[0190]

[0192] The following provides a summary of aspects of the disclosure.

[0191]

[0193] Aspect 1: A method of wireless communication in a first network node, the method including: participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including an indication in a repurposed field; receiving one or more coding symbols, each respective coding symbol of the one or more coding symbols associated with a respective corresponding set of source symbols of the plurality of source symbols via a rateless code; and decoding the one or more coding symbols based on the SBN to determine the plurality of source symbols.

[0192]

[0194] Aspect 2: The method of aspect 1, wherein decoding one or more encoding symbols includes decoding one or more encoding symbols based on one or more ESI, and the DCI includes an indication of the one or more ESI corresponding to the one or more encoding symbols.

[0193]

[0195] Aspect 3: The method of aspect 1, further including: participating in communication of an RRC message indicating one or more parameters; and determining one or more ESI corresponding to one or more coding symbols based on the one or more parameters and first information included in the DCI; and decoding the one or more coding symbols includes decoding the one or more coding symbols based on the one or more ESI.

[0194]

[0196] Aspect 4: The method of aspect 3, wherein the first information includes scheduling information.

[0195]

[0197] Aspect 5: The method of aspect 4, wherein the scheduling information includes a location of one or more resource blocks, a system frame number, a slot number, or a symbol number.

[0196]

[0198] Aspect 6: The method of aspect 3, wherein the first information includes a DCI sequence corresponding to the DCI.

[0197]

[0199] Aspect 7: The method of any one of aspects 1 to 6, wherein participating in DCI communication includes receiving DCI.

[0198]

[0200] Aspect 8: The method of any one of aspects 1 to 6, wherein participating in DCI communication includes transmitting DCI.

[0199]

[0201] Aspect 9: The method of any one of aspects 1 to 8, wherein decoding the one or more encoding symbols includes determining a plurality of source symbols from the one or more encoding symbols based on a Raptor code, and the rateless code is a Raptor code.

[0200]

[0202] Aspect 10: A method of wireless communication in a first network node, the method including: participating in communication of a DCI, the DCI including an indication of an SBN associated with a source block for a plurality of source symbols, the DCI including scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the DCI being included in a downlink shared channel transmission including the one or more coding symbols or the DCI including an indication in a repurposed field; and transmitting one or more coding symbols, each respective coding symbol of the one or more coding symbols being associated with a corresponding set of source symbols among the plurality of source symbols via a rateless code.

[0201]

[0203] Example 11: The method of example 10, wherein the DCI includes an indication of one or more ESI corresponding to one or more encoding symbols.

[0202]

[0204] Aspect 12: The method of aspect 10, further comprising participating in communication of an RRC message, the RRC message indicating one or more parameters for determining one or more ESI corresponding to one or more coding symbols.

[0203]

[0205] Aspect 13: The method of any one of aspects 10 to 12, wherein participating in DCI communication includes receiving DCI.

[0204]

[0206] Example 14: The method of any one of Examples 10 to 12, wherein participating in DCI communication includes transmitting DCI.

[0205]

[0207] Aspect 15: The method of any one of aspects 10 to 14, further comprising generating one or more encoding symbols from the plurality of source symbols based on a Raptor code, wherein the rateless code is a Raptor code.

[0206]

[0208] Aspect 16: A first network node for wireless communication, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform a method according to any of aspects 1 to 9.

[0207]

[0209] Aspect 17: An apparatus for wireless communication in a first network node, the apparatus comprising at least one means for performing the method of any of aspects 1-9.

[0208]

[0210] Aspect 18: A non-transitory computer-readable medium having stored thereon code for wireless communications, the code, when executed by a network node, causing the network node to perform a method as recited in any of aspects 1-9.

[0209]

[0211] Aspect 19: A first network node for wireless communication, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to execute a method according to any of aspects 10 to 15.

[0210]

[0212] Aspect 20: An apparatus for wireless communication in a first network node, comprising: at least one means for performing the method of any of aspects 10-15.

[0211]

[0213] Aspect 21: A non-transitory computer-readable medium having stored thereon code for wireless communications, the code, when executed by a network node, causing the network node to perform a method as described in any of aspects 10-15.

[0212]

[0214] The methods described herein represent possible implementations, and operations and steps may be rearranged or otherwise modified, other implementations are possible, and aspects from two or more of these methods may be combined.

[0213]

[0215] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for illustrative purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may also 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.

[0214]

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

[0215]

[0217] The various example blocks and components described in connection with the disclosure herein may be implemented or performed 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 alternatively, 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0216]

[0218] 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 using one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and 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. The features implementing those functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0217]

[0219] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks can reproduce data magnetically, and discs can reproduce data optically using a laser.Combinations of the above are also included within the scope of computer-readable media.

[0218]

[0220] The term "or" as used herein is an inclusive "or" unless limiting language is used to the listed alternatives. For example, a reference to "X is based on A or B" shall be interpreted as including within its scope X is based on A, X is based on B, and X is based on A and B. In this regard, a reference to "X is based on A or B" refers to "at least one of A or B" or "one or more of A or B," since "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" shall be interpreted as including within its scope X is based on A, X is based on B, X is based on C, X is based on A and B, X is based on A and C, X is based on B and C, and X is based on A, B, and C. In this regard, a reference to "X is based on A, B, or C" refers to "at least one of A, B, or C" or "one or more of A, B, or C," since "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" shall be interpreted to include within its scope X is based on A and X is based on B, but not X is based on A and B. Also, as used herein, the phrase "based on" is not to be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) shall be interpreted as "based on at least A," unless expressly stated otherwise. Also, as used herein, the phrase "set" shall be interpreted as including the possibility of a set having one member. That is, the phrase "set" shall be interpreted similarly to "one or more" or "at least one."

[0219]

[0221] The terms "determine" or "determining" encompass various actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or another data structure), resolving, and the like. "Determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. "Determining" can also include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0220]

[0222] In the figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes among the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0221]

[0223] The description set forth herein with respect to the drawings describes exemplary configurations and does not necessarily represent every example that may be implemented or that falls within the scope of the claims. As used herein, the term "aspect" or "example" means "serving as an aspect, example, instance, or illustration" and does not mean "preferred" or "advantageous over other aspects." The Detailed Description includes specific details for the purpose of providing an understanding of the described technology. However, these technologies can be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0222]

[0224] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the embodiments and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, comprising: Memory and at least one processor coupled to the memory; wherein the at least one processor: participate in the communication of downlink control information, wherein the downlink control information includes an indication of a source block number associated with a source block for a plurality of source symbols, the downlink control information includes scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the downlink control information is included in a downlink shared channel transmission including the one or more coding symbols, or the downlink control information includes the indication within a diverted field. receiving the one or more encoding symbols, wherein each respective encoding symbol of the one or more encoding symbols is associated with a respective corresponding set of source symbols of the plurality of source symbols via a rateless code; decoding the one or more encoding symbols based on the source block number to determine the plurality of source symbols; It is configured as follows: A first network node.

2. 2. The first network node of claim 1, wherein the downlink control information includes an indication of one or more coding symbol identifiers corresponding to the one or more coding symbols, and wherein, to decode the one or more coding symbols, the at least one processor is configured to decode the one or more coding symbols based on the one or more coding symbol identifiers.

3. the at least one processor: Participating in the communication of radio resource control messages indicating one or more parameters; further configured to determine one or more coding symbol identifiers corresponding to the one or more coding symbols based on the one or more parameters and first information included in the downlink control information; to decode the one or more coding symbols, the at least one processor is configured to decode the one or more coding symbols based on the one or more coding symbol identifiers. The first network node of claim 1 .

4. The first network node of claim 3 , wherein the first information includes the scheduling information.

5. The first network node of claim 4 , wherein the scheduling information comprises a location of one or more resource blocks, a system frame number, a slot number, or a symbol number.

6. The first network node of claim 3 , wherein the first information comprises a downlink control information sequence corresponding to the downlink control information.

7. The first network node of claim 1 , wherein the at least one processor is configured to receive the downlink control information in order to participate in the communication of the downlink control information.

8. 2. The first network node of claim 1, wherein, to participate in the communication of the downlink control information, the at least one processor is configured to transmit the downlink control information.

9. To decode the one or more encoding symbols, the at least one processor: and determining the plurality of source symbols from the one or more encoded symbols based on a Raptor code, wherein the rateless code is the Raptor code. The first network node of claim 1 .

10. A first network node for wireless communication, comprising: Memory and at least one processor coupled to the memory; wherein the at least one processor: participate in the communication of downlink control information, wherein the downlink control information includes an indication of a source block number associated with a source block for a plurality of source symbols, the downlink control information includes scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the downlink control information is included in a downlink shared channel transmission including the one or more coding symbols, or the downlink control information includes the indication within a diverted field. configured to transmit the one or more encoding symbols; each respective encoding symbol of the one or more encoding symbols is associated with a corresponding set of source symbols of the plurality of source symbols via a rateless code. A first network node.

11. The first network node of claim 10 , wherein the downlink control information includes an indication of one or more coding symbol identifiers corresponding to the one or more coding symbols.

12. the at least one processor: and further configured to participate in the communication of a radio resource control message indicating one or more parameters for determining one or more coding symbol identifiers corresponding to the one or more coding symbols. The first network node of claim 10.

13. The first network node of claim 10 , wherein the at least one processor is configured to receive the downlink control information to participate in the communication of the downlink control information.

14. The first network node of claim 10 , wherein to participate in the communication of the downlink control information, the at least one processor is configured to transmit the downlink control information.

15. the at least one processor: and further configured to generate the one or more encoding symbols from the plurality of source symbols based on a Raptor code, wherein the rateless code is the Raptor code. The first network node of claim 10.

16. 1. A method of wireless communication in a first network node, comprising: participating in the communication of downlink control information, the downlink control information including an indication of a source block number associated with a source block for a plurality of source symbols, the downlink control information including scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the downlink control information being included in a downlink shared channel transmission including the one or more coding symbols, or the downlink control information including the indication in a diverted field; receiving the one or more encoding symbols, each respective encoding symbol of the one or more encoding symbols being associated with a respective corresponding set of source symbols of the plurality of source symbols via a rateless code; decoding the one or more encoding symbols based on the source block number to determine the source symbols; and A method comprising:

17. decoding the one or more coding symbols, decoding the one or more coding symbols based on one or more coding symbol identifiers, wherein the downlink control information includes an indication of the one or more coding symbol identifiers corresponding to the one or more coding symbols.

17. The method of claim 16.

18. participating in the communication of radio resource control messages indicating one or more parameters; determining one or more coding symbol identifiers corresponding to the one or more coding symbols based on the one or more parameters and first information included in the downlink control information; Further comprising: decoding the one or more coding symbols includes decoding the one or more coding symbols based on the one or more coding symbol identifiers.

17. The method of claim 16.

19. The method of claim 18 , wherein the first information includes the scheduling information.

20. 20. The method of claim 19, wherein the scheduling information includes a location of one or more resource blocks, a system frame number, a slot number, or a symbol number.

21. 20. The method of claim 18, wherein the first information comprises a downlink control information sequence corresponding to the downlink control information.

22. participating in the communication of the downlink control information receiving the downlink control information; 17. The method of claim 16.

23. participating in the communication of the downlink control information transmitting the downlink control information.

17. The method of claim 16.

24. decoding the one or more coding symbols, determining the plurality of source symbols from the one or more encoded symbols based on a Raptor code, wherein the rateless code is the Raptor code.

17. The method of claim 16.

25. 1. A method of wireless communication in a first network node, comprising: participating in the communication of downlink control information, the downlink control information including an indication of a source block number associated with a source block for a plurality of source symbols, the downlink control information including scheduling information for a transmission including one or more coding symbols derived from the plurality of source symbols, the downlink control information being included in a downlink shared channel transmission including the one or more coding symbols, or the downlink control information including the indication in a diverted field; transmitting the one or more encoding symbols, each respective encoding symbol of the one or more encoding symbols being associated with a corresponding set of source symbols of the plurality of source symbols via a rateless code; A method comprising:

26. 26. The method of claim 25, wherein the downlink control information includes an indication of one or more coding symbol identifiers corresponding to the one or more coding symbols.

27. 26. The method of claim 25, further comprising participating in communication of a radio resource control message, the radio resource control message indicating one or more parameters for determining one or more coding symbol identifiers corresponding to the one or more coding symbols.

28. participating in the communication of the downlink control information receiving the downlink control information; 26. The method of claim 25.

29. participating in the communication of the downlink control information transmitting the downlink control information.

26. The method of claim 25.

30. generating the one or more encoding symbols from the plurality of source symbols based on a Raptor code, wherein the rateless code is the Raptor code; 26. The method of claim 25.

Images