WO2022006850A1

WO2022006850A1 - Transmitting encoding symbol identifier of raptor codes using control channel coding

Info

Publication number: WO2022006850A1
Application number: PCT/CN2020/101321
Authority: WO
Inventors: Kangqi LIU; Changlong Xu; Liangming WU; Jian Li; Xipeng Zhu; Hao Xu
Original assignee: Qualcomm Incorporated
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2022-01-13

Abstract

Methods, systems, and devices for wireless communications are described. A receiving device receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. The receiving device may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The receiving device may decode the packet based at least in part on the block number, the symbol identifier, or the combination thereof.

Description

TRANSMITTING ENCODING SYMBOL IDENTIFIER OF RAPTOR CODES USING CONTROL CHANNEL CODING

FIELD OF TECHNOLOGY

The following relates generally to wireless communications and more specifically to transmitting encoding symbol identifier of raptor codes using control channel coding.

BACKGROUND

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal frequency division multiple access (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support transmitting encoding symbol identifier of raptor codes using control channel coding. Generally, the described techniques provide for separately indicating the block number (e.g., source block number (SBN) ) and/or the symbol identifier (e.g., encoding symbol identifier (ESI) ) from the encoded symbols when rateless coded transmissions are performed. For example, a transmitting device (e.g., a user equipment (UE) and/or a base station) having information to communicate to a receiving device (e.g., a UE and/or base station) may encode packets for transmission to the receiving device that are associated with a corresponding block number and/or symbol identifier (e.g., SBN and/or ESI) . However, the transmitting device may separately transmit or otherwise convey (e.g., in a first portion of a first transmission) an indication of the block number and/or symbol identifier to the receiving device. The transmitter may then transmit or otherwise convey (e.g., in a second transmission and/or in a second portion of the first transmission) one or more instances of the packet. The receiving device may receive the indication of the block number and/or symbol identifier separately from the one or more instances of the packet, and decode the packet using the block number and/or symbol identifier. Accordingly, the soft information (e.g., SBN and/or ESI) for packet may be separately indicated for the packet, which may improve recoverability of the packet when rateless codes are used at the radio link control (RLC) and/or physical (PHY) layer.

A method of wireless communication at a receiving device is described. The method may include receiving, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receiving, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decoding the packet based on the block number, the symbol identifier, or the combination thereof.

An apparatus for wireless communication at a receiving device is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decode the packet based on the block number, the symbol identifier, or the combination thereof.

Another apparatus for wireless communication at a receiving device is described. The apparatus may include means for receiving, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receiving, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decoding the packet based on the block number, the symbol identifier, or the combination thereof.

A non-transitory computer-readable medium storing code for wireless communication at a receiving device is described. The code may include instructions executable by a processor to receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decode the packet based on the block number, the symbol identifier, or the combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the indication of the block number in a downlink assignment indicator field of a downlink control information message.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that a threshold number of instances of the packet was unable to be successfully decoded, and transmitting, based on the determining, a feedback message indicating a number of instances of the packet that was unable to be successfully decoded.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of the symbol identifier in an initial transmission instance of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of the symbol identifier associated with a retransmission instance of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of the symbol identifier associated with a set of retransmission instances of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of the symbol identifier in the first portion of the first transmission and receiving the one or more instances of the packet in the second portion of the first transmission.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the transmission includes at least one of a physical uplink shared channel (PUSCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of the symbol identifier in the first transmission and receiving the one or more instances of the packet in the second transmission.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first transmission includes a physical downlink control channel (PDCCH) transmission and the second transmission includes a PDSCH transmission.

A method of wireless communication at a transmitting device is described. The method may include encoding a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmitting, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmitting, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

An apparatus for wireless communication at a transmitting device is described.

The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

Another apparatus for wireless communication at a transmitting device is described. The apparatus may include means for encoding a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmitting, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmitting, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

A non-transitory computer-readable medium storing code for wireless communication at a transmitting device is described. The code may include instructions executable by a processor to encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the indication of the block number in a downlink assignment indicator field of a downlink control information message.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a feedback message from the receiving device indicating a number of instances of the packet that was unable to be successfully decoded by the receiving device, the feedback message based on the receiving device determining that a threshold number of instances of the packet was unable to be successfully decoded.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the symbol identifier in an initial transmission instance of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the symbol identifier associated with a retransmission instance of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the symbol identifier associated with a set of retransmission instances of the packet.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the symbol identifier in the first portion of the first transmission and transmitting the one or more instances of the packet in the second portion of the first transmission.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the transmission includes at least one of a PUSCH transmission, a PDSCH transmission, or a combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of the symbol identifier in the first transmission and transmitting the one or more instances of the packet in the second transmission.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first transmission includes a PDCCH transmission and the second transmission includes a PDSCH transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for wireless communications that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a wireless communication system that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 3 illustrates an example of a encoding configuration that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 4 illustrates an example of a process that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIGs. 5 and 6 show block diagrams of devices that support transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 8 shows a diagram of a system including a UE that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIG. 9 shows a diagram of a system including a base station that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

FIGs. 10 through 14 show flowcharts illustrating methods that support transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Wireless communication systems may utilize fountain codes, which are rateless codes in the sense that the number of coded packets is potentially limitless. For example, the transmitted packets may be recovered at the receiver side so long as the number of receive packets is slightly larger than the number of resource packets (no matter which packets are received and successfully decoded) . Examples of such rateless codes include luby transform (LT) codes, low-density parity-check (LDPC) codes, raptor codes (an enhanced code based on variations of LDPC and LT codes) , and the like. Fountain codes are also referred to as network codes because they are applied to the network/application layer (e.g., for multimedia broadcast multi-cast service (MBMS) , integrated access and backhaul (IAB) , and the like) . At the receiving side, each coded symbol would either be decoded correctly or discarded. This approach permits a block number (e.g., source block number (SBN) ) and/or a symbol identifier (e.g., encoding symbol identifier) associated with the packets to be added as a header file to the coded symbols. The SBN generally corresponds to an integer identifier for the source block that the encoding symbols within the packet relate to. The ESI generally corresponds to an integer identifier for the encoding symbols within the packet. Each encoded packet may include the SBN (e.g., the first 16 bits) , the ESI (e.g., the last 16 bits) , and the encoding symbol (s) . Based on the SBN and ESI, the transmitting device and receiving device may determine which source symbols were selected to generate the encoding symbol.

However, when such rateless codes (e.g., raptor codes) are applied at the radio link control (RLC) and/or physical (PHY) layers, it is not suitable to add the block number and/or symbol identifier as a header file to the encoded symbols (e.g., this may lead to a loss of the soft information for each encoded symbol) . For example, when the coded symbols are not decoded correctly, it is impossible for the receiver to know which source symbols were selected to generate the encoding symbol.

Aspects of the disclosure are initially described in the context of wireless communications systems. Generally, the described techniques provide for separately indicating the block number (e.g., SBN) and/or the symbol identifier (e.g., ESI) from the encoded symbols when rateless coded transmissions are performed. For example, a transmitting device (e.g., a user equipment (UE) and/or a base station) having information to communicate to a receiving device (e.g., a UE and/or base station) may encode packets for transmission to the receiving device that are associated with a corresponding block number and/or symbol identifier (e.g., SBN and/or ESI) . However, the transmitting device may separately transmit or otherwise convey (e.g., in a first portion of a first transmission) an indication of the block number and/or symbol identifier to the receiving device. The transmitter may then transmit or otherwise convey (e.g., in a second transmission and/or in a second portion of the first transmission) one or more instances of the packet. The receiving device may receive the indication of the block number and/or symbol identifier separately from the one or more instances of the packet, and decode the packet using the block number and/or symbol identifier. Accordingly, the soft information (e.g., SBN and/or ESI) for packet may be separately indicated for the packet, which may improve recoverability of the packet when rateless codes are used at the RLC and/or PHY layer.

Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to transmitting encoding symbol identifier of raptor codes using control channel coding.

FIG. 1 illustrates an example of a wireless communications system 100 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

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

The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) , as shown in FIG. 1.

The base stations 105 may communicate with the core network 130, or with one another, or both. For example, the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) . The base stations 105 may communicate with one another over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) , or indirectly (e.g., via core network 130) , or both. In some examples, the backhaul links 120 may be or include one or more wireless links.

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

A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a 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 communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

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

The UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated 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 that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.

In some examples (e.g., in a carrier aggregation configuration) , a carrier may also have acquisition signaling or control signaling that coordinates operations for 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 radio frequency channel number (EARFCN) ) and may be positioned according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .

The communication links 125 shown in the wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .

A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the base stations 105, the UEs 115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include base stations 105 or UEs 115 that support simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques 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 consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) . Thus, the more resource elements that a UE 115 receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE 115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.

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

The time intervals for the base stations 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T _s=1/ (Δf _max·N _f) seconds, where Δf _max may represent the maximum supported subcarrier spacing, and N _f may represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource 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., ranging from 0 to 1023) .

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

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

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

Each base station 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a base station 105 (e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) . In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the base station 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with geographic coverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered base station 105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A base station 105 may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers.

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

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

The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timings, and transmissions from different base stations 105 may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

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

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

In some examples, a UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol) . One or more UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105 or be otherwise unable to receive transmissions from a base station 105. In some examples, groups of the UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.

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

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 (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to the network operators IP services 150. The operators IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station 105, may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) . Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) . Each access network transmission entity 145 may include one or more antenna panels. In some configurations, various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105) .

The wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the base stations 105, and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

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

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

The base stations 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , where multiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

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

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

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

A receiving device (e.g., a UE 115) may try multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may try multiple receive 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 an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .

The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A RLC layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or a core network 130 supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

The UEs 115 and the base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link 125. 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 may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

A receiving device (e.g., a UE 115 receiving a transmission from another UE 115 and/or base station 105 and/or a base station 105 receiving a transmission from another base station 105 and/or UE 115) may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. The receiving device may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The receiving device may decode the packet based at least in part on the block number, the symbol identifier, or the combination thereof.

A transmitting device (e.g., a UE 115 performing a transmission to another UE 115 and/or base station 105 and/or a base station 105 performing a transmission to another base station 105 and/or UE 115) may encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier. The transmitting device may transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device. The transmitting device may transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

FIG. 2 illustrates an example of a wireless communication system 200 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. Wireless communication system 200 may include base station 205 and UE 210, which may be examples of the corresponding devices described herein.

In some aspects, base station 205 may be configured or otherwise acting as a transmitting device performing a wireless transmission to UE 210, which may be configured or otherwise acting as a receiving device in this scenario. However, it is to be understood that UE 210 may implement various aspects of the described techniques when acting as or otherwise configured as a transmitting device performing a wireless transmission to base station 205, which would be configured or otherwise acting as the receiving device in this scenario. In some examples, such wireless transmissions may be performed by base station 205 to another base station and/or by UE 210 to another UE.

Wireless communication system 200 may utilize fountain codes, which are rateless codes in that the number of encoded packets to be transmitted is potentially limitless. For example, the transmitted packets 235 may be recovered at the receiver side so long as the number of received packets 240 is slightly larger than the number of source packets (no matter which packets are received and successfully decoded) . Examples of such rateless codes include luby transform (LT) codes, raptor codes (an enhanced code based on variations of low-density parity-check (LDPC) and LT codes) , and the like.

Fountain codes are also referred to as network codes because they are applied to the network/application layer (e.g., for MBMS, IAB, and the like) . At the receiving side, each encoded symbol would either be decoded correctly or discarded (e.g., the encoded packet (s) transmitted during a symbol) . This approach permits a block number (e.g., SBN) and/or a symbol identifier (e.g., ESI) associated with the packet (s) to be added as a header file to the encoded symbols. The SBN generally corresponds to an integer identifier for the source block (e.g., the column of the original generator matrix 245) that the encoded symbols within the packet relate to. The ESI generally corresponds to an integer identifier for the encoding symbols within the packet. Each encoded packet may include the SBN (e.g., the first 16 bits) , the ESI (e.g., the last 16 bits) , and the encoding symbol (s) . Based on the SBN and ESI, the transmitting device and receiving device may determine which source symbols (e.g., which column of the original generator matrix 245) were selected to generate the encoded symbol.

Accordingly, fountain codes are rateless codes with an unlimited number of columns in the original generator matrix 245 generated by the transmitting device. For example, the transmitting device may have K symbols 250 for transmission to the receiving device. The original generator matrix 245 may therefore be generated with K rows (corresponding to the K symbols 250) and, as the fountain code is a rateless code, a potentially infinite number of columns. The number of transmitted packets may correspond to the formula:

For a conventional ARQ, the original generator matrix 245 may begin with the unit matrix.

The recovered packets (e.g., the received packets 240) may correspond to the formula:

The condition or scenario for the receiving device to recover the packets may include G′ according to the received packets 240 being invertible or the rank of G′ being K. A design rule for the original generator matrix 245 is that G′ is invertible with minimum N.

With respect to LT codes, efficient methods may be utilized to realize the function of fountain codes. For example, the encoding process for each encoding symbol may include the transmitting device randomly choosing a degree d _i from a degree distribution and randomly choosing d _i distinct source symbols with uniform distribution and performing an exclusive or (XOR) function on them.

At the receiving device, the decoding process may include a belief propagation technique, gaussian elimination process, and the like. For example, the receiving device may find an encoding symbol t _j that is connected to only one source symbol S _i (e.g., symbol 250) . The receiving device may set S _i to t _j, XOR S _i to all encoding symbols that are connected to S _i, and remove all edges connected to the source symbol S _i. The receiving device may repeat this until all S _i are determined. If there are no encoding symbols that are connected to only one source symbol, then the decoding process fails.

Raptor codes generally reduce the encoding and decoding complexity of LT codes by reducing the average degree (e.g., LDPC plus weak LT code with a small averaging degree, such as three) . The precoding process may include generating some redundant symbols, such as S LDPC symbols (each source symbol 250 will appear three times in all LDPC symbols) and H half symbols (each encoding symbol containing ceiling (H/2) source symbols 250) . The encoding process for each encoding symbol may include randomly choosing a degree d _i from a degree distribution, e.g., may choose d _i distinct source symbols 250 and XOR them. The number of redundant symbols may be based on the first K intermediate symbols.

Accordingly, in some wireless communication systems each encoding packet may contain the SBN, the ESI, and encoding symbol (s) . Then, based on the SBN and ESI, the transmitting device/receiving device may determine which source symbols 250 were selected to generate the encoding symbol (e.g., corresponding to a column in the original generator matrix 245) . Raptor codes may be used as an erasure-correction coding, particularly at the application layer. Accordingly, each encoded symbol would either be decoded correctly or discarded by the receiving device. This permits adding the SBN and ESI as a header file to the encoded symbols.

However, when such rateless codes (e.g., raptor codes) are applied at the RLC and/or PHY layers, it is not suitable to add the block number and/or symbol identifier as a header file to the encoded symbols (e.g., this may lead to a loss of the soft information for each encoded symbol) . For example, when the encoded symbols are not decoded correctly, it is impossible for the receiver to know which source symbols were selected to generate the encoding symbol.

Accordingly, aspects of the described techniques permit the block number (e.g., SBN) and/or symbol identifier (e.g., ESI) to be transmitted to the receiver separately from the encoded symbols. In some aspects, this may enable reducing the number of bits used to convey the SBN and/or ESI, e.g., less than 16 bits.

In some aspects, when systematic raptor codes are used, the systematic symbols may be transmitted first (e.g., in new transmission instance (s) ) and followed by one or more repair symbols (e.g., in retransmission instance (s) ) . This may include the systematic symbols for new transmissions and repair symbols for retransmissions. In a downlink example, this may include the network using the DAI in the DCI message for the systematic symbols transmission (e.g., the DAI field in the DCI message indicates which column, the source column, of the original generator matrix 245) . The UE may feedback the number of NACK symbols, not the index of the NACK’ d symbols, thus reducing the feedback overhead. In response, the network may transmit the indication of the ESI plus one or more repair symbols.

In an uplink example, the network may transmit an uplink grant (e.g., DCI 0) identifying resources for an uplink transmission from the UE. The UE may transmit the systematic symbols using the resources, with the network indicating the number of NACK symbols, but not the index of the NACK’ d symbols, in the next uplink grant (e.g., DCI 0) . The UE may then transmit the indication of the ESI plus one or more repair symbols. In another option, this may include transmitting systematic symbols plus some repair symbols for a new transmission and repair symbols for retransmissions. This may be similar to the first option, except that the new transmission may include the indication of ESI plus some repair symbols.

Accordingly, base station 205 (the transmitting device in this example) may encode a packet for transmission to UE 210 (the receiving device in this example) . The packet may be associated with a block number (e.g., SBN) and/or a symbol identifier (e.g., ESI) . Base station 205 may transmit, provide for output, or otherwise convey the indication of the block number and/or symbol identifier associated with the packet to UE 210. The indication of the block number and/or symbol identifier may be indicated in a first portion of a first transmission from base station 205. Base station 205 may transmit, provide for output, or otherwise convey one or more instances of the packet in a second transmission (e.g., in different transmissions, such as in PDCCH and PDSCH transmission) or in a second portion of the first transmission (e.g., in different portions of same transmission) from base station 205 to UE 210. UE 210 (the receiving device in this example) may decode the packet based on the block number and/or symbol identifier indicated by base station 205.

As discussed above, in some aspects this may include base station 205 configuring a DAI field of the DCI message to indicate the block number associated with the packet. In some examples, the indication of the symbol identifier may be provided in an initial transmission instance of the packet (e.g., a new transmission, such as ESI + repair symbol (s) in the new transmission) . In some examples, the indication of the symbol identifier may be provided or otherwise associated with a retransmission instance of the packet (e.g., a repair symbol, such as ESI + repair symbol (s) ) . For example, this may include base station 205 transmitting the indication of the symbol identifier (e.g., ESI 215) along with repair symbol 220 (e.g., the ESI + one repair symbol) .

In some examples, the indication of the symbol identifier may be provided or otherwise associated with a plurality of retransmission instances of the packet. For example, this may include base station 205 transmitting the indication of the symbol identifier (e.g., ESI 215) along with repair symbol 220, repair symbol 225, and repair symbol 230 (e.g., the ESI + multiple repair symbols) . In some aspects, this may include the indication of the ESI including the ESI of the first repair symbol (e.g., repair symbol 220) as well as the number of repair symbols (e.g., with three repair symbols being shown by way of example only) . In some aspects, the indication of the ESI may be encoded using control channel coding (e.g., polar coding, which may be used for control channel coding) to improve reliability. The ESI can be transmitted in either PxCCH or PxSCH, or other channels.

In some aspects, UE 210 may feedback NACK information indicating the number of NACK symbols that were unable to be successfully decoded, but not an index of the NACK’d symbols. Accordingly, UE 210 may determine that a threshold number of instances of the packet were unable to be successfully decoded. UE may transmit a feedback message to base station 205 indicating the number of instances of the packet that were unable to be successfully decoded, but not indicating the index of the NACK’d symbols.

FIG. 3 illustrates an example of an encoding configuration 300 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. In some examples, encoding configuration 300 may implement aspects of wireless communication systems 100 and/or 200. Aspects of encoding configuration 300 may be implemented by a transmitting device, which may be an example of a UE and/or base station is described.

As discussed above, aspects of the described techniques provide a mechanism where the block number and/or symbol identifier associated with packet (e.g., ESI and/or SBN) are transmitted or otherwise conveyed from a transmitting device to a receiving device separately from the encoded symbol (e.g., packet) . For example, the transmitting device may encode the packet for transmission to the receiving device, with the packet being associated with the block number (e.g., SBN) and/or symbol identifier (e.g., ESI) . The transmitting device may transmit or otherwise convey the indication of the block number and/or symbol identifier associated with the packet in a first portion of a first transmission. The transmitting device may transmit or otherwise convey instance (s) of the packet to the receiving device in a second portion of the first transmission or in a second transmission.

In one example, encoding configuration 300 illustrates an uplink example (e.g., when the UE is acting or otherwise configured as the transmitting device) where the ESI is encoded with control channel coding (e.g., polar codes) and transmitted together with the encoded data (which was encoded with data channel coding, such as LDPC codes) in PUSCH. Accordingly, the transmitting device may transmit the indication of the symbol identifier (e.g., ESI) in the first portion of the first transmission and the instances of the packet in the second portion of the first transmission, e.g., separately encoded and transmitted within a PUSCH transmission.

In the uplink example, the transmitting device may perform transport block size (TBS) determination using the formula

K _UL-SCH=TBS+L _CRC, TB+L _CRC, CB≈N _info= (N _RE-Q′ _ESI) *R*Q _m*v

where R is the indicated code rate, Q _m is the modulation order, v is the number of layers, and N _RE is the total number of resource elements (REs) per layer of the PUSCH that UL-SCH can be mapped to (with overhead such as DMRS, etc., excluded) . In the uplink example, Q′ _ESI may be determined using the formula

In another example, encoding configuration 300 illustrates a downlink example (e.g., when the base station is acting or otherwise configured as the transmitting device) where the ESI is added in the DCI message and transmitted in PDCCH. For example, the transmitting device may transmit the indication of the symbol identifier (e.g., ESI) in the first transmission (e.g., the DCI transmitted in PDCCH) and the instance (s) of the packet in the second transmission (e.g., in PDSCH) . In another downlink example, encoding configuration 300 illustrates a downlink example where the ESI is encoded with control channel coding (e.g., polar codes) and transmitted together with the encoded data (which is encoded with data channel coding, such as LDPC coding) in PDSCH (e.g., control information is transmitted in PDSCH) .

In the downlink example, the transmitting device may perform TBS determination using the formula

K _UL-SCH=TBS+L _CRC, TB+L _CRC, CB≈N _info= (N _RE-Q′ _ESI) *R*Q _m*v

where R is the indicated code rate, Q _m is the modulation order, v is the number of layers, and N _RE is the total number of REs per layer of the PUSCH that DL-SCH can be mapped to (with overhead such as DMRS, etc., excluded) . In the downlink example, Q′ _ESI may be determined using the formula

Accordingly, the transmitting device may determine Q′ _ESI (e.g., the number of REs used to indicate the symbol identifier) based on ESI 305 (e.g., the indication of the symbol identifier) which is encoded using channel coding 310 (e.g., control channel coding using polar codes) and output as control information. The transmitting device may determine N _RE-Q′ _ESI (e.g., the number of REs minus the REs used to indicate the symbol identifier) based on data 315 (e.g., information to be communicated in the packet at the TB level) . Data 315 is fed into channel coding 320, which may map the data to a channel for transmission. The channel coding 320 may be performed on multiple layers, with two layers being shown by way of example only (e.g., channel coding 320-a and channel coding 320-b) . The channel coding may be performed at the codeblock level. The data for each layer may be output to redundancy version (RV) functions, depending on whether the data will be transmitted in an initial transmission (e.g., RV 0) or one or more retransmission instances (e.g., RV N) . For example, the data from channel coding 320-a may be output to RV 325 (e.g., RV 0) for initial or new transmission and output to RV 330 (e.g., RV N) for retransmission. Similarly, the data from channel coding 320-b may be output to RV 340 (e.g., RV 0) for initial or new transmission and output to RV 345 (e.g., RV N) for retransmission. Accordingly, the output of RV 325 and RV 340 are fed to raptor encoding 335 for encoding before transmission in a new or initial transmission. Similarly, the output of RV 330 and RV 345 are fed to raptor encoding 350 for encoding before transmission in a retransmission instance.

FIG. 4 illustrates an example of a process 400 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. In some examples, process 400 may implement aspects of wireless communication systems 100 and/or 200, and/or encoding configuration 300. Aspects of process 400 may be implemented by transmitting device 405 and/or receiving device 410, which may be examples of the corresponding devices described herein. In one example, transmitting device 405 may be an example of a UE and/or base station performing a transmission to receiving device 410. Similarly, receiving device 410 may be an example of a UE and/or base station receiving a transmission from transmitting device 405.

At 415, transmitting device 405 may encode a packet for transmission to receiving device 410. In some aspects, the packet may be associated with the block number (e.g., an SBN) and/or a symbol identifier (e.g., an ESI) .

At 420, transmitting device 405 may transmit (and receiving device 410 may receive) an indication of the block number and/or symbol identifier associated with the packet in a first portion of a first transmission. In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the block number in a DAI field of the DCI message. In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the symbol identifier in an initial transmission instance of the packet (e.g., in a new transmission) .

In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the symbol identifier associated with a retransmission instance of the packet (e.g., ESI plus a repair symbol) . In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the symbol identifier associated with the plurality of retransmission instances of the packet (e.g., ESI plus multiple repair symbols) .

In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the symbol identifier in the first portion of the first transmission and receiving the instances of the packet in the second portion of the first transmission (e.g., the first transmission may include a PUSCH and/or PDSCH transmission) .

In some aspects, this may include transmitting device 405 transmitting (and receiving device 410 receiving) the indication of the symbol identifier in the first transmission and the instances of the packet in the second transmission. The first transmission may include a PDCCH transmission and the second transmission may include a PDSCH transmission in this example.

At 425, transmitting device 405 may transmit (and receiving device 410 may receive) one or more instances of the packet in a second portion of the first transmission or in a second transmission.

At 430, a receiving device 410 may decode the packet based on the block number and/or symbol identifier.

In some aspects, this may include receiving device 410 determining that a threshold number of instances of the packet was unable to be successfully decoded. Accordingly, the receiving device 410 may transmit (and transmitting device 405 may receive) a feedback message indicating the number of instances of the packet that were unable to be successfully decoded. The receiving device 410 may not provide an indication of the index of the packets that were unable to be successfully decoded.

FIG. 5 shows a block diagram 500 of a device 505 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 or base station 105 as described herein. The device 505 may include a receiver 510, a communications manager 515, and a transmitter 520. The device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmitting encoding symbol identifier of raptor codes using control channel coding, etc. ) . Information may be passed on to other components of the device 505. The receiver 510 may be an example of aspects of the

transceiver

820 or 920 as described with reference to FIGs. 8 and 9. The receiver 510 may utilize a single antenna or a set of antennas.

When device 505 is acting as a receiving device, the communications manager 515 may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decode the packet based on the block number, the symbol identifier, or the combination thereof.

When device 505 is acting as a transmitting device, the communications manager 515 may also encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The communications manager 515 may be an example of aspects of the

communications manager

810 or 910 as described herein.

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

The communications manager 515, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communications manager 515, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communications manager 515, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

Transmitter 520 may transmit signals generated by other components of the device 505. In some examples, the transmitter 520 may be collocated with a receiver 510 in a transceiver module. For example, the transmitter 520 may be an example of aspects of the

transceiver

820 or 920 as described with reference to FIGs. 8 and 9. The transmitter 520 may utilize a single antenna or a set of antennas.

FIG. 6 shows a block diagram 600 of a device 605 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The device 605 may be an example of aspects of a device 505, a UE 115, or a base station 105 as described herein. The device 605 may include a receiver 610, a communications manager 615, and a transmitter 635. The device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmitting encoding symbol identifier of raptor codes using control channel coding, etc. ) . Information may be passed on to other components of the device 605. The receiver 610 may be an example of aspects of the

transceiver

820 or 920 as described with reference to FIGs. 8 and 9. The receiver 610 may utilize a single antenna or a set of antennas.

The communications manager 615 may be an example of aspects of the communications manager 515 as described herein. The communications manager 615 may include an indication manager 620, a data manager 625, and a coding manager 630. The communications manager 615 may be an example of aspects of the

communications manager

810 or 910 as described herein.

The indication manager 620 may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device.

The data manager 625 may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

The coding manager 630 may decode the packet based on the block number, the symbol identifier, or the combination thereof. The coding manager 630 may encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier.

The indication manager 620 may transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device.

The data manager 625 may transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

Transmitter 635 may transmit signals generated by other components of the device 605. In some examples, the transmitter 635 may be collocated with a receiver 610 in a transceiver module. For example, the transmitter 635 may be an example of aspects of the

transceiver

820 or 920 as described with reference to FIGs. 8 and 9. The transmitter 635 may utilize a single antenna or a set of antennas.

FIG. 7 shows a block diagram 700 of a communications manager 705 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The communications manager 705 may be an example of aspects of a communications manager 515, a communications manager 615, or a communications manager 810 described herein. The communications manager 705 may include an indication manager 710, a data manager 715, a coding manager 720, a SBN indication manager 725, a feedback manager 730, and an ESI indication manager 735. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The indication manager 710 may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. In some examples, the indication manager 710 may transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device.

The data manager 715 may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. In some examples, the data manager 715 may transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

The coding manager 720 may decode the packet based on the block number, the symbol identifier, or the combination thereof. In some examples, the coding manager 720 may encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier.

The SBN indication manager 725 may receive the indication of the block number in a downlink assignment indicator field of a DCI message. In some examples, the SBN indication manager 725 may transmit the indication of the block number in a DAI field of a DCI message.

The feedback manager 730 may determine that a threshold number of instances of the packet was unable to be successfully decoded. In some examples, the feedback manager 730 may transmit, based on the determining, a feedback message indicating a number of instances of the packet that was unable to be successfully decoded. In some examples, the feedback manager 730 may receive a feedback message from the receiving device indicating a number of instances of the packet that was unable to be successfully decoded by the receiving device, the feedback message based on the receiving device determining that a threshold number of instances of the packet was unable to be successfully decoded.

The ESI indication manager 735 may receive an indication of the symbol identifier in an initial transmission instance of the packet. In some examples, the ESI indication manager 735 may receive an indication of the symbol identifier associated with a retransmission instance of the packet. In some examples, the ESI indication manager 735 may receive an indication of the symbol identifier associated with a set of retransmission instances of the packet. In some examples, the ESI indication manager 735 may receive an indication of the symbol identifier in the first portion of the first transmission and receiving the one or more instances of the packet in the second portion of the first transmission.

In some examples, the ESI indication manager 735 may receive an indication of the symbol identifier in the first transmission and receiving the one or more instances of the packet in the second transmission. In some examples, the ESI indication manager 735 may transmit an indication of the symbol identifier in an initial transmission instance of the packet. In some examples, the ESI indication manager 735 may transmit an indication of the symbol identifier associated with a retransmission instance of the packet.

In some examples, the ESI indication manager 735 may transmit an indication of the symbol identifier associated with a set of retransmission instances of the packet. In some examples, the ESI indication manager 735 may transmit an indication of the symbol identifier in the first portion of the first transmission and transmitting the one or more instances of the packet in the second portion of the first transmission. In some examples, the ESI indication manager 735 may transmit an indication of the symbol identifier in the first transmission and transmitting the one or more instances of the packet in the second transmission. In some cases, the transmission includes at least one of a PUSCH transmission, a PDSCH transmission, or a combination thereof. In some cases, the first transmission includes a PDCCH transmission and the second transmission includes a PDSCH transmission. In some cases, the transmission includes at least one of a PUSCH transmission, a PDSCH transmission, or a combination thereof. In some cases, the first transmission includes a PDCCH transmission and the second transmission includes a PDSCH transmission.

FIG. 8 shows a diagram of a system 800 including a device 805 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The device 805 may be an example of or include the components of device 505, device 605, or a UE 115 as described herein. The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 810, a transceiver 820, an antenna 825, memory 830, a processor 840, and an I/O controller 850. These components may be in electronic communication via one or more buses (e.g., bus 855) .

When device 805 is acting as a receiving device, the communications manager 810 may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decode the packet based on the block number, the symbol identifier, or the combination thereof.

When device 805 is acting as a transmitting device, the communications manager 810 may also encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

Transceiver 820 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 820 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 820 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 825. However, in some cases the device may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

The memory 830 may include random access memory (RAM) , read-only memory (ROM) , or a combination thereof. The memory 830 may store computer-readable code 835 including instructions that, when executed by a processor (e.g., the processor 840) cause the device to perform various functions described herein. In some cases, the memory 830 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor 840 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, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting transmitting encoding symbol identifier of raptor codes using control channel coding) .

The I/O controller 850 may manage input and output signals for the device 805. The I/O controller 850 may also manage peripherals not integrated into the device 805. In some cases, the I/O controller 850 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 850 may utilize an operating system such as

or another known operating system. In other cases, the I/O controller 850 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 850 may be implemented as part of a processor. In some cases, a user may interact with the device 805 via the I/O controller 850 or via hardware components controlled by the I/O controller 850.

The code 835 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 835 may not be directly executable by the processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

FIG. 9 shows a diagram of a system 900 including a device 905 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The device 905 may be an example of or include the components of device 505, device 605, or a base station 105 as described herein. The device 905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 910, a network communications manager 915, a transceiver 920, an antenna 925, memory 930, a processor 940, and an inter-station communications manager 945. These components may be in electronic communication via one or more buses (e.g., bus 955) .

When device 905 is acting as a receiving device, the communications manager 910 may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device, receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet, and decode the packet based on the block number, the symbol identifier, or the combination thereof.

When device 905 is acting as a transmitting device, the communications manager 910 may also encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier, transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device, and transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.

Network communications manager 915 may manage communications with the core network (e.g., via one or more wired backhaul links) . For example, the network communications manager 915 may manage the transfer of data communications for client devices, such as one or more UEs 115.

Transceiver 920 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 920 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 920 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 925. However, in some cases the device may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

The memory 930 may include RAM, ROM, or a combination thereof. The memory 930 may store computer-readable code 935 including instructions that, when executed by a processor (e.g., the processor 940) cause the device to perform various functions described herein. In some cases, the memory 930 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor 940 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting transmitting encoding symbol identifier of raptor codes using control channel coding) .

Inter-station communications manager 945 may manage communications with other base station 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 945 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-station communications manager 945 may provide an X2 interface within an LTE/LTE-Awireless communication network technology to provide communication between base stations 105.

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

FIG. 10 shows a flowchart illustrating a method 1000 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The operations of method 1000 may be implemented by a UE 115 or base station 105 or its components as described herein. For example, the operations of method 1000 may be performed by a communications manager as described with reference to FIGs. 5 through 9. In some examples, a UE or base station may execute a set of instructions to control the functional elements of the UE or base station to perform the functions described below. Additionally or alternatively, a UE or base station may perform aspects of the functions described below using special-purpose hardware.

At 1005, the UE or base station may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. The operations of 1005 may be performed according to the methods described herein. In some examples, aspects of the operations of 1005 may be performed by an indication manager as described with reference to FIGs. 5 through 9.

At 1010, the UE or base station may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The operations of 1010 may be performed according to the methods described herein. In some examples, aspects of the operations of 1010 may be performed by a data manager as described with reference to FIGs. 5 through 9.

At 1015, the UE or base station may decode the packet based on the block number, the symbol identifier, or the combination thereof. The operations of 1015 may be performed according to the methods described herein. In some examples, aspects of the operations of 1015 may be performed by a coding manager as described with reference to FIGs. 5 through 9.

FIG. 11 shows a flowchart illustrating a method 1100 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The operations of method 1100 may be implemented by a UE 115 or base station 105 or its components as described herein. For example, the operations of method 1100 may be performed by a communications manager as described with reference to FIGs. 5 through 9. In some examples, a UE or base station may execute a set of instructions to control the functional elements of the UE or base station to perform the functions described below. Additionally or alternatively, a UE or base station may perform aspects of the functions described below using special-purpose hardware.

At 1105, the UE or base station may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. The operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be performed by an indication manager as described with reference to FIGs. 5 through 9.

At 1110, the UE or base station may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be performed by a data manager as described with reference to FIGs. 5 through 9.

At 1115, the UE or base station may decode the packet based on the block number, the symbol identifier, or the combination thereof. The operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be performed by a coding manager as described with reference to FIGs. 5 through 9.

At 1120, the UE or base station may determine that a threshold number of instances of the packet was unable to be successfully decoded. The operations of 1120 may be performed according to the methods described herein. In some examples, aspects of the operations of 1120 may be performed by a feedback manager as described with reference to FIGs. 5 through 9.

At 1125, the UE or base station may transmit, based on the determining, a feedback message indicating a number of instances of the packet that was unable to be successfully decoded. The operations of 1125 may be performed according to the methods described herein. In some examples, aspects of the operations of 1125 may be performed by a feedback manager as described with reference to FIGs. 5 through 9.

FIG. 12 shows a flowchart illustrating a method 1200 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The operations of method 1200 may be implemented by a UE 115 or base station 105 or its components as described herein. For example, the operations of method 1200 may be performed by a communications manager as described with reference to FIGs. 5 through 9. In some examples, a UE or base station may execute a set of instructions to control the functional elements of the UE or base station to perform the functions described below. Additionally or alternatively, a UE or base station may perform aspects of the functions described below using special-purpose hardware.

At 1205, the UE or base station may receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device. The operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed by an indication manager as described with reference to FIGs. 5 through 9.

At 1210, the UE or base station may receive an indication of the symbol identifier in an initial transmission instance of the packet. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be performed by an ESI indication manager as described with reference to FIGs. 5 through 9.

At 1215, the UE or base station may receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be performed by a data manager as described with reference to FIGs. 5 through 9.

At 1220, the UE or base station may decode the packet based on the block number, the symbol identifier, or the combination thereof. The operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operations of 1220 may be performed by a coding manager as described with reference to FIGs. 5 through 9.

FIG. 13 shows a flowchart illustrating a method 1300 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The operations of method 1300 may be implemented by a UE 115 or base station 105 or its components as described herein. For example, the operations of method 1300 may be performed by a communications manager as described with reference to FIGs. 5 through 9. In some examples, a UE or base station may execute a set of instructions to control the functional elements of the UE or base station to perform the functions described below. Additionally or alternatively, a UE or base station may perform aspects of the functions described below using special-purpose hardware.

At 1305, the UE or base station may encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier. The operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed by a coding manager as described with reference to FIGs. 5 through 9.

At 1310, the UE or base station may transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed by an indication manager as described with reference to FIGs. 5 through 9.

At 1315, the UE or base station may transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed by a data manager as described with reference to FIGs. 5 through 9.

FIG. 14 shows a flowchart illustrating a method 1400 that supports transmitting encoding symbol identifier of raptor codes using control channel coding in accordance with aspects of the present disclosure. The operations of method 1400 may be implemented by a UE 115 or base station 105 or its components as described herein. For example, the operations of method 1400 may be performed by a communications manager as described with reference to FIGs. 5 through 9. In some examples, a UE or base station may execute a set of instructions to control the functional elements of the UE or base station to perform the functions described below. Additionally or alternatively, a UE or base station may perform aspects of the functions described below using special-purpose hardware.

At 1405, the UE or base station may encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier. The operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed by a coding manager as described with reference to FIGs. 5 through 9.

At 1410, the UE or base station may transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed by an indication manager as described with reference to FIGs. 5 through 9.

At 1415, the UE or base station may transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed by a data manager as described with reference to FIGs. 5 through 9.

At 1420, the UE or base station may transmit an indication of the symbol identifier in an initial transmission instance of the packet. The operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed by an ESI indication manager as described with reference to FIGs. 5 through 9.

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

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications 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, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, 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) .

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

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. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include random-access memory (RAM) , read-only memory (ROM) , electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a 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 in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A method for wireless communication at a receiving device, comprising:

receiving, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device;

receiving, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet; and

decoding the packet based at least in part on the block number, the symbol identifier, or the combination thereof.
The method of claim 1, further comprising:

receiving the indication of the block number in a downlink assignment indicator field of a downlink control information message.
The method of claim 1, further comprising:

determining that a threshold number of instances of the packet was unable to be successfully decoded; and

transmitting, based at least in part on the determining, a feedback message indicating a number of instances of the packet that was unable to be successfully decoded.
The method of claim 1, further comprising:

receiving an indication of the symbol identifier in an initial transmission instance of the packet.
The method of claim 1, further comprising:

receiving an indication of the symbol identifier associated with a retransmission instance of the packet.
The method of claim 1, further comprising:

receiving an indication of the symbol identifier associated with a plurality of retransmission instances of the packet.
The method of claim 1, further comprising:

receiving an indication of the symbol identifier in the first portion of the first transmission and receiving the one or more instances of the packet in the second portion of the first transmission.
The method of claim 7, wherein the transmission comprises at least one of a physical uplink shared channel (PUSCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a combination thereof.
The method of claim 1, further comprising:

receiving an indication of the symbol identifier in the first transmission and receiving the one or more instances of the packet in the second transmission.
The method of claim 9, wherein the first transmission comprises a physical downlink control channel (PDCCH) transmission and the second transmission comprises a physical downlink shared channel (PDSCH) transmission.
A method for wireless communication at a transmitting device, comprising:

encoding a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier;

transmitting, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device; and

transmitting, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.
The method of claim 11, further comprising:

transmitting the indication of the block number in a downlink assignment indicator field of a downlink control information message.
The method of claim 11, further comprising:

receiving a feedback message from the receiving device indicating a number of instances of the packet that was unable to be successfully decoded by the receiving device, the feedback message based at least in part on the receiving device determining that a threshold number of instances of the packet was unable to be successfully decoded.
The method of claim 11, further comprising:

transmitting an indication of the symbol identifier in an initial transmission instance of the packet.
The method of claim 11, further comprising:

transmitting an indication of the symbol identifier associated with a retransmission instance of the packet.
The method of claim 11, further comprising:

transmitting an indication of the symbol identifier associated with a plurality of retransmission instances of the packet.
The method of claim 11, further comprising:

transmitting an indication of the symbol identifier in the first portion of the first transmission and transmitting the one or more instances of the packet in the second portion of the first transmission.
The method of claim 17, wherein the transmission comprises at least one of a physical uplink shared channel (PUSCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a combination thereof.
The method of claim 11, further comprising:

transmitting an indication of the symbol identifier in the first transmission and transmitting the one or more instances of the packet in the second transmission.
The method of claim 19, wherein the first transmission comprises a physical downlink control channel (PDCCH) transmission and the second transmission comprises a physical downlink shared channel (PDSCH) transmission.
An apparatus for wireless communication at a receiving device, comprising:

a processor,

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device;

receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet; and

decode the packet based at least in part on the block number, the symbol identifier, or the combination thereof.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive the indication of the block number in a downlink assignment indicator field of a downlink control information message.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

determine that a threshold number of instances of the packet was unable to be successfully decoded; and

transmit, based at least in part on the determining, a feedback message indicating a number of instances of the packet that was unable to be successfully decoded.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive an indication of the symbol identifier in an initial transmission instance of the packet.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive an indication of the symbol identifier associated with a retransmission instance of the packet.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive an indication of the symbol identifier associated with a plurality of retransmission instances of the packet.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive an indication of the symbol identifier in the first portion of the first transmission and receiving the one or more instances of the packet in the second portion of the first transmission.
The apparatus of claim 27, wherein the transmission comprises at least one of a physical uplink shared channel (PUSCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a combination thereof.
The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to:

receive an indication of the symbol identifier in the first transmission and receiving the one or more instances of the packet in the second transmission.
The apparatus of claim 29, wherein the first transmission comprises a physical downlink control channel (PDCCH) transmission and the second transmission comprises a physical downlink shared channel (PDSCH) transmission.
An apparatus for wireless communication at a transmitting device, comprising:

a processor,

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier;

transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device; and

transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit the indication of the block number in a downlink assignment indicator field of a downlink control information message.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

receive a feedback message from the receiving device indicating a number of instances of the packet that was unable to be successfully decoded by the receiving device, the feedback message based at least in part on the receiving device determining that a threshold number of instances of the packet was unable to be successfully decoded.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit an indication of the symbol identifier in an initial transmission instance of the packet.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit an indication of the symbol identifier associated with a retransmission instance of the packet.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit an indication of the symbol identifier associated with a plurality of retransmission instances of the packet.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit an indication of the symbol identifier in the first portion of the first transmission and transmitting the one or more instances of the packet in the second portion of the first transmission.
The apparatus of claim 37, wherein the transmission comprises at least one of a physical uplink shared channel (PUSCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a combination thereof.
The apparatus of claim 31, wherein the instructions are further executable by the processor to cause the apparatus to:

transmit an indication of the symbol identifier in the first transmission and transmitting the one or more instances of the packet in the second transmission.
The apparatus of claim 39, wherein the first transmission comprises a physical downlink control channel (PDCCH) transmission and the second transmission comprises a physical downlink shared channel (PDSCH) transmission.
An apparatus for wireless communication at a receiving device, comprising:

means for receiving, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device;

means for receiving, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet; and

means for decoding the packet based at least in part on the block number, the symbol identifier, or the combination thereof.
An apparatus for wireless communication at a transmitting device, comprising:

means for encoding a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier;

means for transmitting, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device; and

means for transmitting, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.
A non-transitory computer-readable medium storing code for wireless communication at a receiving device, the code comprising instructions executable by a processor to:

receive, in a first portion of a first transmission from a transmitting device, an indication of at least one of a block number, a symbol identifier, or a combination thereof, associated with a transmission of a packet from the transmitting device to the receiving device;

receive, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet; and

decode the packet based at least in part on the block number, the symbol identifier, or the combination thereof.
A non-transitory computer-readable medium storing code for wireless communication at a transmitting device, the code comprising instructions executable by a processor to:

encode a packet for transmission from the transmitting device to a receiving device, the packet associated with a block number and a symbol identifier;

transmit, in a first portion of a first transmission from the transmitting device, an indication of at least one of the block number, the symbol identifier, or a combination thereof, associated with the transmission of the packet from the transmitting device to the receiving device; and

transmit, in a second transmission from the transmitting device or in a second portion of the first transmission from the transmitting device, one or more instances of the packet.