The present disclosure relates generally to communication systems, and more particularly, to wireless communication including network coding.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at an encoding device. The apparatus transmits an indication for a plurality of user equipments (UEs) to provide feedback for a network coding packet across multiple time periods. The apparatus transmits the network coding packet and receives the feedback from the plurality of UEs across the multiple time periods.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a UE. The apparatus receives an indication to provide feedback for a network coding packet that is staggered in a different time period than a baseline time period. The apparatus receives the network coding packet and transmits the feedback in one time period among multiple time periods associated with the network coding packet.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
Network coding may increase system capacity and improve resource utilization by reducing the number of individual retransmissions, while maintaining system performance by providing the combined retransmission of multiple packets in the network coding transmission. Resources are used more efficiently, because two resources would be used for individual retransmissions, whereas a single resource can be used for the network coded transmission. The network encoded retransmission of multiple packets may enable an increase in the number of transmitters (e.g., UEs) or in the amount of traffic per transmitter (e.g., per UE). As well, the reliability of the communication may be improved, because the receiving UEs may use information from previously received packets in the network coding transmission to decode one or more packets that were not correctly received in the initial transmission. Instead of simply relaying packets of information the encoding device may take multiple packets and combine them together for transmission. The combination of packets may improve information flow in a network. In some aspects, the receiving UEs may provide feedback (e.g., ACK/NACK feedback) to the encoding device for the network encoded transmission.
Aspects presented herein provide a way for receiving UEs to provide feedback to an encoding device, such as a network encoder, which allows for feedback from large numbers of UEs even with limited feedback resources (e.g., PSFCH resources). As presented herein, the feedback for a network coding packet may be staggered across multiple slots, in order to enable increased numbers of receiving UEs to provide their feedback. The encoding device may configure the receiving UEs and/or indicate to the receiving UEs to use feedback staggering based on various metrics. The aspects presented herein may enable the encoding device to receive feedback from an increased number of UEs. Aspects, including the various metrics for feedback staggering, may prioritize some feedback in earlier time periods and/or may improve the reception of some feedback through muting of other feedback.
The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184 (e.g., Xn interface), and the third backhaul links 134 may be wired or wireless.
In some aspects, a base station 102 or 180 may be referred as a RAN and may include aggregated or disaggregated components. As an example of a disaggregated RAN, a base station may include a central unit (CU) 106, one or more distributed units (DU) 105, and/or one or more remote units (RU) 109, as illustrated in
An access network may include one or more integrated access and backhaul (IAB) nodes 111 that exchange wireless communication with a UE 104 or other IAB node 111 to provide access and backhaul to a core network. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. The IAB donor may be a base station 102 or 180 that provides access to a core network 190 or EPC 160 and/or control to one or more IAB nodes 111. The IAB donor may include a CU 106 and a DU 105. IAB nodes 111 may include a DU 105 and a mobile termination (MT). The DU 105 of an IAB node 111 may operate as a parent node, and the MT may operate as a child node.
The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
Some examples of sidelink communication may include vehicle-based communication devices that can communicate from vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from the vehicle-based communication device to road infrastructure nodes such as a Road Side Unit (RSU)), vehicle-to-network (V2N) (e.g., from the vehicle-based communication device to one or more network nodes, such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and/or a combination thereof and/or with other devices, which can be collectively referred to as vehicle-to-anything (V2X) communications. Sidelink communication may be based on V2X or other D2D communication, such as Proximity Services (ProSe), etc. In addition to UEs, sidelink communication may also be transmitted and received by other transmitting and receiving devices, such as Road Side Unit (RSU) 107, etc. Sidelink communication may be exchanged using a PC5 interface, such as described in connection with the example in
The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
A base station 102, whether a small cell 102′ or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.
The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.
The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to
Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing may be equal to 2μ,*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As illustrated in
The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.
As illustrated in
(SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the device 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the device 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the device 350. If multiple spatial streams are destined for the device 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the device 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the device 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the device 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the device 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the device 310 in a manner similar to that described in connection with the receiver function at the device 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the device 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the NC feedback component 198 of
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the NC component 199 of
A resource grid may be used to represent the frame structure. Each time slot may include a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. As illustrated in
The reliability of communication between a transmitting device and a receiving device may be improved through network coding of the communication by an encoding device.
As an example, two or more original transmissions, e.g., two or more initial packets, may be combined through network coding and transmitted as a combination of the initial packets. In an example, a first device may transmit a first packet to a second device, and the second device may transmit a second packet to the first device. Following the transmission of the first and second packets, the encoding device may transmit an encoded combination of the first and second packets, e.g., based on network coding. Each of the devices may decode the packet from the other device in the network coded combination of the packets, with assistance based on the information of their own packet. For example, at the first device, the knowledge of the first packet may assist the first device in decoding the second packet from the network coded transmission of the first and second packet. FIGs, 5A and 5B illustrate another example application of network coding.
In some aspects, network coding, including the aspects presented herein, may be applied for sidelink communication, such as V2X communication. Additionally, or alternatively, the network coding aspects described herein may be applied for non-vehicular sidelink communication. The network coding aspects may also be applied for other types of wireless communication than sidelink.
The encoding device 505 or 515 may identify two or more packets (e.g., original packet(s) TXa and TXb) for transmitting to the receiving device(s) (e.g., 503 and 504). The encoding device 505 or 515 applies a network coding algorithm to the original packets to generate encoded packets (e.g., 507). The encoding device 505 then transmits the encoded packets (e.g., 507) as a data transmission.
The receiving device(s) (e.g., 503 and 504) may then attempt to decode the received encoded packets (e.g., 507) to reconstruct the original packets (e.g., TXa and TXb).
In some examples, to improve communication between a transmitting device (e.g., any of UE 501, UE 502, and/or encoding device 505) and the receiving device (e.g., 503 and 504), the receiving device may transmit feedback, such as ACK/NACK feedback, that indicates whether a packet has been received accurately. For example, the UE 503 in
In some aspects, the encoding device may provide retransmissions for many UEs and may prioritize which packets to retransmit among multiple initial transmissions from multiple UEs. The encoding device may use feedback, e.g., ACK/NACK feedback, to select a subset of packets (or encoded transport block) to include in a network coding transmission. A transport block (TB) is a packet of data that is mapped onto a data channel (e.g., a physical sidelink shared channel (PSSCH), a physical uplink shared channel (PUSCH), a physical downlink shared channel (PDSCH), etc.) for transmission. A transport block may refer to a payload for a physical layer data transmission. In some aspects, the encoding device may select the TBs, or packets, to network encode as a retransmission in order to maximize the change in feedback from NACKs to ACKs. For example, the encoding device may consider the feedback from multiple UEs for multiple packets and may select combinations of packets to network encode that have a higher likelihood of successful receipt. Table 1 illustrates an example of ACK/NACK feedback that may be provided by four UEs (e.g., UE0, UE1, UE2 and UE3) for four packets (e.g., p0, p1, p2, and p3).
Table 1 illustrates that the UEO successfully received p0 and p2, and did not successfully receive p1. The empty cell for p3 indicates absent feedback. The UE1 successfully received p0 and pl, and did not successfully receive p2 and p3. The UE 2 did not successfully receive p0, and successfully received p1, p2, and p3. The UE3 successfully received p0 and p3, did not successfully receive p1, and has absent feedback for p2. The encoding device (e.g., which may also be referred to as an encoder) may assume an ACK for each packet's source UE. Thus, if a fifth UE transmitted p0 and p2, the chart may include an ACK for p0 and p1 for the fifth UE even though the fifth UE does not provide feedback, because the fifth UE is the source of the packets.
Table 2 illustrates an example of possible combinations of packets that the encoding device may transmit with network coding and shows a corresponding indication for the set of four UEs in Table 1 showing the status for the combined packets.
In Table 2, an “A” indicates that both packets have been received successfully (e.g., decoded successfully) by the corresponding UE, a check mark indicates that the UE successfully decoded one of the packets and did not successfully decode the other packet, an “X” indicates that neither packet was successfully decoded, and an empty entry means that feedback was not received for at least one of the packets. In Table 2, the combination p0+p1 has a highest likelihood in changing a NACK for one of the packets to ACK for each of the UEs, which may be referred to as a NACK-to-ACK flip. The combination of p0+p1 has the most checkmarks indicating that one packet was already successfully received by the corresponding UEs. Thus, transmitting p0+p1 enables three of the four UEs to decode a previously undecoded packet. The UE1 successfully received both of the packets of the combination p0+p1. As the UEO, UE2, and UE3 have successfully received one of the packets, the UEs may use the information for the received packet to assist the UEs in decoding the other packet from the network coded transmission, which increases the likelihood of successful receipt by the UEs. The encoding device may select the combination of p0+p 1 to retransmit with network coding.
While the examples in
Aspects presented herein provide a way for receiving UEs to provide feedback to an encoding device, such as a network encoder, which allows for feedback from large numbers of UEs even with limited feedback resources (e.g., PSFCH resources). As presented herein, the feedback for a network coding packet may be staggered across multiple slots, in order to enable increased numbers of receiving UEs to provide their feedback. The encoding device may configure the receiving UEs and/or indicate to the receiving UEs to use feedback staggering based on various metrics.
When the encoding device 704 is going to send a network coding packet, the encoding device 704 may estimate the number of needed PSFCH resources for the network coding packet transmission, at 712. A network coding packet may include multiple TBs, whereas the initial packet transmission may include a single TB, e.g., as described in connection with
In some aspects, the encoding device 704 may determine whether to use staggered feedback for a network coding packet, e.g., at 714. As an example, the encoding device 704 may use staggered feedback if the amount of PSFCH resources for the network coding transmission is more than a threshold amount of resources. The amount of resources for the feedback, e.g., as estimated at 712, may be based on a number of UEs to provide feedback and/or a number of TBs included in the network coding packet. The threshold may be a fixed threshold in some aspects. In other aspects, the threshold may be a configurable threshold. In some aspects, the threshold may be related to an amount of PSFCH resources that are available to the encoding device in the upcoming PSFCH occasion. For example, the amount of available PSFCH resources for the encoding device may exclude PSFCH resources used for normal (e.g., non-network coding) communication, PSFCH resources used by other encoding devices, and/or PSFCH resources already used for other network coding packets from the same encoding device.
The encoding device 704 may further determine a number of slots for the staggered feedback, e.g., at 716. The amount of staggered PSFCH slots for the feedback may be based on the amount of PSFCH for the network coding transmission and/or the delay budgets of the coded packets in the network coding transmission. In an example, the encoding device 704 may consider the minimum of the delay budgets of the coded packets in a network coding transmission.
In some aspects, the number of PSFCH resources allocated for the network coding packet can be the same across the multiple (e.g., staggered) PFSCH slots.
The amount of available feedback resources in a slot may be limited, e.g., a few symbols of a slot. By staggering feedback for network coding packets over multiple slots, more feedback resources may be used for a larger network coding packet (e.g., with multiple TBs and/or a larger number of UEs to provide feedback), and a smaller network coding packet (e.g., with fewer packets and/or a smaller number of UEs to provide feedback) may have feedback provided in a single slot, e.g., without feedback staggering across multiple slots.
When the encoding device 704 decides to use feedback staggering, at 714, the encoding device may indicate to a receiving UE to use the staggered feedback. The indication may be included in the network coding transmission 718. In some aspects, the staggering may be based on previously configured parameters, and the encoding device and the UE(s) may determine to use staggered feedback, e.g., based on a number of packets in the network coding transmission, etc.
A receiving UE 702 may determine which PSFCH resource on which PSFCH slot to use to send the feedback. If the indication indicates to use non-staggered feedback, the UE 702 may transmit the feedback in a following slot, e.g., as described in connection with
For staggered feedback across multiple slots, the receiving UEs may determine their corresponding PSFCH resource in a different manner. In some aspects, the receiving UE(s) (e.g., UE 702) may determine the PSFCH resource, at 720, based on UE ID and/or a packet ID. In an example, each of the receiving UEs may perform a hash on their UE ID and a packet ID for the network coding packet to determine a PSFCH resource. In some aspects, the number of staggered slots (e.g., of the multiple slots for the PSFCH) may be configured at 710, e.g., prior to the network coding transmission. In some aspects, the number of staggered slots (e.g., of the multiple slots for the PSFCH) may be signaled by the encoding device.
In some aspects, a receiving UE 702 may determine the slot in which to send feedback 722 based on the receiving UE's, at 702, distance to the encoding device. As an example, the UEs may be grouped for feedback purposes according to their respective distances from the encoding device. The encoding device may receive feedback from UEs having similar distances in a same slot, for example.
The UEs that are closer to the encoding device may have a better chance of decoding the packets. The UEs that are closer to the encoding device may send feedback at a later slot than UEs that are more distant from the encoding device and less likely to successfully decode a transmission.
In some aspects, a receiving UE may determine the slot in which to send feedback 722 based on a packet priority. If the packet, or TB, that a UE is attempting to decode has a higher priority, the UE may send feedback in an earlier slot than for feedback for lower priority packets.
In some aspects, a receiving UE may determine the slot in which to send feedback 722 based on a packet expiration time or a relative expiration time order. A UE may send feedback in an earlier slot for a packet having an earlier packet expiration time than for a packet have a later expiration time.
The packet priority or relative expiration time order for different packets in a network coding transmission may be signaled in the network coding packet header. The mapping from a packet's order (x) to the number of slots (y) at which the feedback is to be staggered can be configured, e.g., at 706, or may be signaled by the encoding device, e.g., at 718. In some aspects, a mapping in the signaling can include all the input-output pairs (x, y). In some aspects, the signaling, for all the input-output pairs (x, y) associated with a certain output Y, may include the mapping one with the lowest x. If the mapping is similar, the signaling may indicate, or include, the turning points, e.g., particular input-output pairs having a different mapping or at which the mapping changes.
As other transmissions may not be network coding transmissions, the other transmissions may involve fewer feedback resources. In some aspects, in order to avoid using feedback resources of other transmissions for the staggered feedback for the network coding transmission, the PSFCH resources may be divided between resources for staggered feedback and resources for other transmissions.
In some aspects, a subset of one or more UEs may be disabled from sending feedback for a network coding transmission, e.g., to save the PSFCH resources. Additionally, or alternatively, feedback for a part of the TBs included in a network coding transmission may be cancelled or muted. Muted feedback may refer to feedback that is canceled or skipped. As an example, UEs within a particular distance (D) of the encoding device may be muted from, or indicated to skip, sending feedback for a network coding transmission. For example, in
In some aspects, the distance D may be configured, e.g., prior to the network coding transmission. In some aspects, the distance D may be signaled, or otherwise, indicated by the encoding device.
In some aspects, the feedback from closer UEs may be muted based on an RSRP threshold instead of a distance threshold. For example, UEs that measure an RSRP above the RSRP threshold may be indicated to skip transmitting feedback. The RSRP may be measured, e.g., for the network coding transmission.
In some aspects, receiving UEs may cancel unsent feedback after a new network coding packet (e.g., 719) is received. As an example, some feedback may be staggered, e.g., scheduled, at a later slot based on a longer expiration time, lower priority, closer distance to the encoding device, etc. Such feedback may not yet be transmitted when the receiving UE 706 receives a subsequent network coding packet 719. The reception of the subsequent network coding transmission may trigger the receiving UE to cancel or drop the unsent ACK/NACK feedback, at 724) for the prior network coding transmission (e.g., 718).
At 1202, the UE receives an indication to provide feedback for a network coding packet that is staggered in a different time period than a baseline time period. In some aspects, the indication may be comprised in a header of the network coding packet. In some aspects, the indication may be comprised in a configuration for the UE. The reception of the indication may be performed, e.g., by the feedback indication component 1340 of the apparatus 1302 in
At 1204, the UE receives the network coding packet. The network coding packet may include a combination of multiple TBs (e.g., multiple packets that may have been previously transmitted), e.g., as described in connection with
At 1206, the UE transmits the feedback in one time period among multiple time periods associated with the network coding packet. The multiple time periods may correspond to multiple PSFCH slots., e.g., as described in connection with
The communication manager 1332 includes a feedback indication component 1340 that is configured to receive an indication to provide feedback for a network coding packet that is staggered in a different time period than another UE, e.g., as described in connection with 1202 in
The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts of
As shown, the apparatus 1302 may include a variety of components configured for various functions. In one configuration, the apparatus 1302, and in particular the baseband processor 1304, includes means for receiving an indication to provide feedback for a network coding packet that is staggered in a different time period than a baseline time period; means for receiving the network coding packet; and means for transmitting the feedback in one time period among multiple time periods associated with the network coding packet. The apparatus 1302 may further include means for receiving an additional indication indicating to skip sending the feedback for an additional network coding packet. The apparatus 1302 may further include means for measuring a reference signal received power of a signal from an encoding device that is higher than a threshold; and means for skipping a transmission of the feedback for the additional network coding packet. The means may be one or more of the components of the apparatus 1302 configured to perform the functions recited by the means. As described supra, the apparatus 1302 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the means.
At 1402 the encoder transmits an indication for a plurality of UEs to provide feedback for a network coding packet across multiple time periods. In some aspects, the indication may be comprised in a header of the network coding packet. In some aspects, the indication may be comprised in a configuration for the UE(s). The transmission of the indication may be performed, e.g., by the feedback indication component 1540 of the apparatus 1502 in
At 1404, the encoder transmits the network coding packet. The network coding packet may include a combination of multiple TBs (e.g., multiple packets that may have been previously transmitted), e.g., as described in connection with
At 1406, the encoder receives the feedback from the plurality of UEs across the multiple time periods. The multiple time periods may correspond to multiple PSFCH slots., e.g., as described in connection with
In some aspects, the encoder may indicate for one or more UEs to skip sending the feedback for the network coding packet. The one or more UEs may be within a distance of the encoding device or measure a reference signal received power of a signal from the encoding device that is higher than a threshold.
The communication manager 1532 includes a feedback indication component 1540 that is configured to transmit an indication for a plurality of user UEs to provide feedback for a network coding packet across multiple time periods, e.g., as described in connection with 1402 in
The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of
As shown, the apparatus 1502 may include a variety of components configured for various functions. In one configuration, the apparatus 1502, and in particular the baseband unit 1504, includes means for transmitting an indication for a plurality of user UEs to provide feedback for a network coding packet across multiple time periods; means for transmitting the network coding packet; and means for receiving the feedback from the plurality of UEs across the multiple time periods. The apparatus 1502 may further include means for transmitting the indication for the plurality of UEs to provide the feedback across the multiple PSFCH slots in response to an amount of feedback resources for the network coding packet being larger than a threshold. The apparatus 1502 may further include means for allocating a different number of physical sidelink feedback channel resources for the network coding packet across the multiple PSFCH slots. The apparatus 1502 may further include means for allocating a same number of physical sidelink feedback channel resources for the network coding packet across the multiple PSFCH slots. The apparatus 1502 may further include means for receiving the feedback for each UE in a time period based on a corresponding UE ID and a packet ID for the network coding packet. The apparatus 1502 may further include means for receiving the feedback for each UE in a time period based on a corresponding distance from the encoding device. The apparatus 1502 may further include means for receiving the feedback for each UE in a time period based on a packet priority associated with a corresponding feedback. The apparatus 1502 may further include means for receiving the feedback for each UE in a time period based on a packet expiration time associated with a corresponding feedback. The apparatus 1502 may further include means for indicating for one or more UEs to skip sending the feedback for the network coding packet. The means may be one or more of the components of the apparatus 1502 configured to perform the functions recited by the means. As described supra, the apparatus 1502 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the means.
It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims.
Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a method of wireless communication at a user equipment (UE), comprising: receiving an indication to provide feedback for a network coding packet that is staggered in a different time period than a baseline time period; receiving the network coding packet; and transmitting the feedback in one time period among multiple time periods associated with the network coding packet.
In aspect 2, the method of aspect 1 further includes that the multiple time periods correspond to multiple PSFCH slots.
In aspect 3, the method of aspect 2 further includes that the one time period is more than one PSFCH slot after the network coding packet.
In aspect 4, the method of aspect 2 or aspect 3 further includes that a number of the multiple PSFCH slots is based on a number of coded TBs in the network coding packet.
In aspect 5, the method of any of aspects 2-4 further includes that a number of the multiple PSFCH slots is based on a delay budget of packets comprised in the network coding packet.
In aspect 6, the method of any of aspects 1-5 further includes that the indication is comprised in a header of the network coding packet.
In aspect 7, the method of any of aspects 1-5 further includes that the indication is comprised in a configuration for the UE.
In aspect 8, the method of any of aspects 1-7 further includes that the one time period is based on a UE ID and a packet ID for the network coding packet.
In aspect 9, the method of any of aspects 1-8 further includes that the one time period is based on a corresponding distance from an encoding device.
In aspect 10, the method of any of aspects 1-9 further includes that the one time period is based on a packet priority associated with the feedback.
In aspect 11, the method of any of aspects 1-10 further includes that the one time period is based on a packet expiration time associated with the feedback.
In aspect 12, the method of any of aspects 1-11 further includes receiving an additional indication indicating to skip sending the feedback for an additional network coding packet.
In aspect 13, the method of aspect 12 further includes that the additional indication is based on the UE being within a distance of an encoding device.
In aspect 14, the method of aspect 13 further includes measuring a reference signal received power of a signal from an encoding device that is higher than a threshold; and skipping a transmission of the feedback for the additional network coding packet.
Aspect 15 is an apparatus for wireless communication including at least one processor coupled to a memory, the memory and the at least one processor configured to perform the method of any of aspects 1-14.
In aspect 16, the apparatus of aspect 15 further includes at least one of an antenna or a transceiver coupled to the at least one processor.
Aspect 17 is an apparatus for wireless communication including means for performing the method of any of aspects 1-14.
In aspect 18, the apparatus of aspect 17 further includes at least one of an antenna or a transceiver.
Aspect 19 is a non-transitory computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1-14.
Aspect 20 is a method of wireless communication at an encoding device, comprising:
transmitting an indication for a plurality of UEs to provide feedback for a network coding packet across multiple time periods; transmitting the network coding packet; and receiving the feedback from the plurality of UEs across the multiple time periods.
In aspect 21, the method of aspect 20 further includes that the multiple time periods correspond to multiple PSFCH slots.
In aspect 22, the method of aspect 21 further includes that a number of the multiple PSFCH slots is based on a number of UEs.
In aspect 23, the method of aspect 21 or 22 further includes that a number of the multiple PSFCH slots is based on a number of coded transport blocks (TBs) in the network coding packet.
In aspect 24, the method of any of aspects 21-23 further includes that a number of the multiple PSFCH slots is based on a delay budget of packets comprised in the network coding packet.
In aspect 25, the method of any of aspects 20-24 further includes transmitting the indication for the plurality of UEs to provide the feedback across the multiple PSFCH slots in response to an amount of feedback resources for the network coding packet being larger than a threshold.
In aspect 26, the method of any of aspects 20-25 further includes allocating a different number of physical sidelink feedback channel resources for the network coding packet across the multiple PSFCH slots.
In aspect 27, the method of any of aspects 20-25 further includes allocating a same number of physical sidelink feedback channel resources for the network coding packet across the multiple PSFCH slots.
In aspect 28, the method of any of aspects 20-27 further includes the indication is comprised in a header of the network coding packet.
In aspect 29, the method of any of aspects 20-27 further includes the indication is comprised in a configuration for the plurality of UEs.
In aspect 30, the method of any of aspects 20-29 further includes receiving the feedback from the plurality of UEs across the multiple time periods includes: receiving the feedback for each UE in a time period based on a corresponding UE ID and a packet ID for the network coding packet.
In aspect 31, the method of any of aspects 20-30 further includes receiving the feedback from the plurality of UEs across the multiple time periods includes: receiving the feedback for each UE in a time period based on a corresponding distance from the encoding device.
In aspect 32, the method of any of aspects 20-31 further that includes receiving the feedback from the plurality of UEs across the multiple time periods includes: receiving the feedback for each UE in a time period based on a packet priority associated with a corresponding feedback.
In aspect 33, the method of any of aspects 20-32 further includes that receiving the feedback from the plurality of UEs across the multiple time periods includes: receiving the feedback for each UE in a time period based on a packet expiration time associated with a corresponding feedback.
In aspect 34, the method of any of aspects 20-33 further includes indicating for one or more UEs to skip sending the feedback for the network coding packet.
In aspect 35, the method of any of aspects 20-34 further includes that the one or more
UEs are within a distance of the encoding device or measure a reference signal received power of a signal from the encoding device that is higher than a threshold.
Aspect 36 is an apparatus for wireless communication including at least one processor coupled to a memory, the memory and the at least one processor configured to perform the method of any of aspects 20-35.
In aspect 37, the apparatus of aspect 36 further includes at least one of an antenna or a transceiver coupled to the at least one processor.
Aspect 38 is an apparatus for wireless communication including means for performing the method of any of aspects 20-35.
In aspect 39, the apparatus of aspect 38 further includes at least one of an antenna or a transceiver.
Aspect 40 is a non-transitory computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 20-35.