Patent Application
20230412346
The present disclosure relates generally to communication systems, and more particularly, to a groupcast or broadcast communication and more specifically to 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. The apparatus may be a network encoding device at a UE or a base station. The apparatus may be configured to receive a plurality of indications for a plurality of transport blocks (TBs) for the network encoding device to retransmit. The apparatus may further be configured to transmit, to a plurality of user equipments (UEs), a feedback collection network coding (FCNC) request for a subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a network coding (NC) packet including a second indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The apparatus may also be configured to receive, from at least one of the plurality of UEs, feedback associated with the FCNC request based on the FCNC feedback configuration and to encode, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of UEs.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be configured to receive, from a network encoding device, a FCNC request for a subset of a plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a first indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The apparatus may further be configured to transmit, to the network encoding device, feedback associated with the FCNC request based on the FCNC feedback configuration.
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 by providing information regarding each of the combined packets that may allow UEs that did not receive either one of the combined packets to derive the packet that it failed to receive from the combination of packets. In some aspects, the receiving UEs may provide feedback (e.g., ACK/NACK feedback) to the encoding device for the network encoded transmission.
In the case of groupcasting, an encoding device may receive indications of a plurality of packets for which it is responsible for retransmission. The encoding device, initially, may not have sufficient ACK/NACK information for all, or any, of the plurality of packets. The ACK/NACK information may not be sufficient if the expected number of NACK-to-ACK flips using network coding is smaller than a constant, K, that may be known (preconfigured) or configured. In some aspects, the encoding device may run out of ACK/NACK information. The PSFCH resources for feedback from receiving UEs to the network encoding device, in some aspects, may be limited.
Aspects presented herein provide a way for an encoding device to collect feedback (e.g., ACK/NACK) information regarding the plurality of packets. The encoding device may select a subset of the plurality of packets for transmission in a feedback collection network coding (FCNC) request. In some aspects, the FCNC request includes an indication that the FCNC request is associated with a FCNC feedback configuration. The FCNC feedback configuration, in some aspects, may be different from a feedback configuration for NC packets that are not FCNC requests. For example, a configuration for feedback associated with the FCNC request may be different than a configuration for feedback associated with a NC packet that is not an FCNC request. The feedback configuration associated with the FCNC request may indicate a number of shared feedback resources (e.g., bins) for providing feedback related to each TB in the subset of the plurality of TBs. A receiving device may be configured to identify and/or select a particular shared feedback resource based on identifiers associated with the receiving device.
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, and the third backhaul links 134 may be wired or wireless.
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.
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 (71 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
In certain aspects, the base station 180 may include a feedback collection network coding component 199 that may be configured to receive a plurality of indications for a plurality of TBs for the network encoding device to retransmit. The feedback collection network coding component 199 may further be configured to transmit, to a plurality of UEs, a FCNC request for a subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The feedback collection network coding component 199 may also be configured to receive, from at least one of the plurality of UEs, feedback associated with the FCNC request based on the FCNC feedback configuration and to encode, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of UEs. 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
As illustrated in
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 UE 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 UE 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 UE 350. If multiple spatial streams are destined for the UE 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 base station 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 base station 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 base station 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 base station 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 base station 310 in a manner similar to that described in connection with the receiver function at the UE 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 UE 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 198 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.
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 may then transmit 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 UE0 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 p1, 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 UE0, 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+p1 to retransmit with network coding.
While the examples in
Aspects presented herein provide a way to collect information for determining which combined packets will result in an expected number of NACK-to-ACK flips. For example, an encoding device may transmit a feedback collection network coding packet including a subset of the packets (e.g., transport blocks) for which the encoding device is responsible for retransmitting to collect information relating to the subset of packets. The subset of the packets may be included in a plurality of transport blocks of the feedback collection network coding packet.
While the examples in
Aspects presented herein further provide a way to collect feedback information for a plurality of receiving devices in a limited number of feedback (e.g., PSFCH) resources by configuring shared feedback resources (e.g., bins) that may be used by multiple receiving devices. The shared feedback resources, in some aspects may be dynamically configured or known (preconfigured).
Based on the rank assigned 712 by the encoding device 704, the encoding device 704 may select 714 a subset of the plurality of TBs based on the rank assigned 712 to each TB of the plurality of the TBs. In some aspects, the encoding device 704 may select 714 the subset of the plurality of TBs randomly. The selection 714 may be based on an identification of a number of TBs (e.g., a maximum number of TBs) that may be included in the subset. The (maximum) number of TBs may be based on an amount of feedback resources (e.g., PSFCH resources) available for receiving feedback. The subset of the plurality of TBs selected 714 by the encoding device, in some aspects, may include the plurality of TBs if the maximum number of TBs is greater than the number of TBs in the plurality of TBs for retransmission.
The encoding device 704 may then transmit, and the receiving devices 706 may receive, a feedback collection network coding packet (request) 716. The feedback collection network coding packet may include an indication that the packet is a feedback collection network coding request associated with a FCNC feedback configuration. The FCNC feedback configuration, in some aspects, may be different from a feedback configuration for NC packets that are not FCNC requests. For example, the FCNC feedback configuration may indicate for a receiving device to provide feedback to the encoding device via a different PSFCH resource than for NC packets that are not FCNC requests or may indicate a different method for determining a PSFCH resource for providing feedback to the encoding device than for NC packets that are not FCNC requests. The indication may include a bit in the header of the FCNC request. The FCNC feedback configuration, in some aspects, includes a third indication of a first number of shared feedback resources (e.g., bins). In some aspect, the first number of shared feedback resources (e.g., bins) is associated with each TB in the subset of TBs included in the FCNC request. In some aspects, each of the shared feedback resources is associated with a different subset of UEs in a plurality of UEs (the receiving devices 706) and the first number of shared feedback resources is smaller than a number of UEs in the plurality of UEs.
Based on receiving the feedback collection network coding packet (request) 716, the receiving devices 706 may identify 718 a set of resources for providing feedback to the encoding device 704. The set of resources may include a feedback resource associated with each TB in the subset of TBs included in the feedback collection network coding packet (request) 716. The feedback resources associated with the feedback collection network coding packet (request) 716 may be divided into a set of resource pools corresponding to the TBs in the subset of TBs. Each resource pool associated with a TB may be further subdivided into a first number of bins (shared feedback resources) that may be selected by a receiving device for providing feedback. The number of bins may be known (e.g., preconfigured) or signaled by the encoding device. A number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the subset of TBs, such that NB*NT≤N. In some aspects, the number, NB, of bins may be one of (1) the largest integer smaller than NP/NT, (2) a largest number of bins in a known (preconfigured) set of candidate values for the number of bins, or (3) a default value unless the default value is larger than NP/NT. The number of bins, NB, may be smaller than a number of bins used for other NC packets based on the inclusion of more TBs in the FCNC request than in other NC packets.
The particular resources in the set of resources identified 718 by the receiving devices 706 may be based on one or more of a packet ID associated with the subset of TBs (e.g., to identify a resource pool associated with the TB), a device ID, a zone ID, a beam ID, or other identifier associated with the receiving device that may be different for different devices associated with a same encoding device. For example, the receiving devices 706 may, for each TB in the subset of TBs, determine a resource pool associated with the TB and then perform a hashing function of one or more of the device ID, the zone ID, the beam ID, or the other ID to identify a particular resource in the resource pool. In other aspects, the receiving device may use other methods of identifying a corresponding bin known to one of ordinary skill in the art.
Based on the received feedback collection network coding packet (request) 716, the receiving devices 706 may transmit feedback 720 via the identified 718 set of resources. The encoding device 704 may receive the feedback 720 from the receiving devices 706 along with feedback from a plurality of receiving devices via the PSFCH resources including the identified 718 set of resources such that the feedback from multiple receiving devices may be received via a same PSFCH resource for one or more TBs in the subset of TBs. The received feedback may provide sufficient information regarding the TBs in the subset of TBs to the encoding device to determine that a certain number, K, of NACK-to-ACK flips may be expected based on a network coding packet including a combination of packets including one or more of the TBs in the subset of TBs.
Based on the feedback 720 received from the receiving devices 706, the encoding device 704 may determine which of the plurality of TBs to combine in a subsequent set of NC packets. The encoding device 704 may encode 722, based on the received feedback 720, the plurality of TBs into a set of NC packets 724 for transmission to receiving devices. Each packet in the set of NC packets 724 may include a set of TBs that each include information related to a combination of two or more TBs in the plurality of TBs that the encoding device is responsible for retransmitting. The set of NC packets 724 may be standard NC packets (e.g., NC packets that are not FCNC requests) and the feedback configuration associated with the NC packets 724 may be different than the feedback configuration associated with the feedback collection network coding packet (request) 716.
Diagram 860 illustrates that a base station 882 (e.g., as an example of an encoding device) may communicate the FCNC packet 802 with a first UE 862 and a second UE 872. The first UE 862 may be associated with a first set of identifiers including C-RNTI 1 863, Zone ID 1 864, and SSB ID 1 865 that may be used to determine a shared feedback resource “Bin 1” 866. The second UE 872 may be associated with a second set of identifiers including C-RNTI 2 873, Zone ID 2 874, and SSB ID 2 875 that may be used to determine a shared feedback resource “Bin 0” 876. The shared feedback resource may be determined based on a hashing function applied to one or more of the identifiers associated with the UEs or based on a modulo (based on the number of bins) applied to one or more identifiers. In some aspects, a same shared feedback resource (e.g., bin) may be used by a UE for providing feedback for each TB in the subset of TBs included in the FCNC packet 802.
The specific resources associated with a particular shared feedback resource (bin) may be determined based on the number of TBs included in the FCNC packet 802 and the amount of resources in the PSFCH resource pool 807a associated with the FCNC packet 802. Similarly, the number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the FCNC packet 802, such that NB*NT≤N. In some aspects, the number, NB, of bins may be one of (1) the largest integer smaller than NP/NT, (2) a largest number of bins in a known (preconfigured) set of candidate values for the number of bins, or (3) a default value unless the default value is larger than NP/NT. The feedback configuration for the FCNC packet 802 may be different from a feedback configuration for a NC packet that is not a FCNC packet based on the increased number of TBs included in the FCNC packet 802 such that for a NC packet that is not a FCNC packet each resource pool for a TB is larger and can be subdivided into a larger number of bins.
In some aspects, the number of TBs, M, in the plurality of TBs may be larger than can be included in a FCNC request and the encoding device may determine which TBs to include in the FCNC request. In order to determine which TBs to include in the FCNC request, the encoding device may identify a number of TBs in the subset of the plurality of TBs (e.g., the number of TBs that may be included in a FCNC request) based on available resources for feedback (e.g., PSFCH resources). In some aspects, the encoding device may assign a rank to each TB of the plurality of the TBs. The rank assigned to each TB of the plurality of TBs is based on at least one of an expiration time associated with the TB, a priority associated with the TB, a location of a source of the TB, a TB size, or a TB range specification. The encoding device may then select the subset of the plurality of TBs based on the rank assigned to each TB of the plurality of the TBs.
At 904, the encoding device may transmit, to a plurality of receiving devices and/or UEs a FCNC request for the subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs. For example, 904 may be performed by FCNC transmission component 1344 or by FCNC transmission component 1444. In some aspects, the FCNC request may be a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration. The second indication that the NC packet is associated with the FCNC feedback configuration may include a bit in a header of the FCNC request. The FCNC feedback configuration, in some aspects, may be different from a feedback configuration for NC packets that are not FCNC requests. For example, referring to
The FCNC feedback configuration may include a third indication of a first number of shared feedback resources (bins), where each of the shared feedback resources may be associated with a different subset of receiving devices and/or UEs in the plurality of receiving devices and/or UEs and the first number of shared feedback resources is smaller than a number of receiving devices and/or UEs in the plurality of receiving devices and/or UEs. In some aspects, the first number of shared feedback resources is based on a number of feedback resources available for receiving the feedback from the plurality of UEs and a number of TBs in the subset of the plurality of TBs. The number of bins may be known (e.g., preconfigured) or signaled by the encoding device. In addition to signaling the number of bins, the FCNC request may include an indication of a method for a receiving device to identify a bin (e.g., a specific resource in a set of PSFCH resources) for providing feedback. A number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the subset of TBs, such that NB*NT≤N. In some aspects, the first number, NB, of bins may be one of (1) a largest integer that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs (e.g., NP/NT), (2) a largest value in a set of values that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, or (3) a threshold value if the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs is greater than the threshold value.
At 906, the encoding device may receive, from at least one of the plurality of receiving devices and/or UEs feedback associated with the FCNC request based on the FCNC feedback configuration. For example, 906 may be performed by FCNC feedback reception component 1346 or by FCNC feedback reception component 1446. The feedback may be based on a feedback configuration indicated in a FCNC request. For example, referring to
Finally, at 908, the encoding device may encode, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of receiving devices and/or UEs. For example, 908 may be performed by NC encoding component 1348 or by NC encoding component 1448. The combinations of TBs in the plurality of TBs combined in each NC packet may be selected to such that a number of expected NACK-to-ACK flips is above a threshold or is maximized. For example, referring to
In some aspects, the number of TBs, M, in the plurality of TBs may be larger than can be included in a FCNC request and the encoding device may determine which TBs to include in the FCNC request. In order to determine which TBs to include in the FCNC request, the encoding device may identify, at 1004, a number of TBs in the subset of the plurality of TBs (e.g., the number of TBs that may be included in a FCNC request) based on available resources for feedback (e.g., PSFCH resources). For example, 1004 may be performed by FCNC TB selection component 1342 or by FCNC TB selection component 1442. For example, referring to
At 1006, the encoding device may assign a rank to each TB of the plurality of the TBs. For example, 1006 may be performed by FCNC TB selection component 1342 or by FCNC TB selection component 1442. The rank assigned to each TB of the plurality of TBs, in some aspects, may be based on at least one of an expiration time associated with the TB, a priority associated with the TB, a location of a source of the TB, a TB size, or a TB range specification. In some aspects, a rank may be based on a weighted average calculated based on two or more of the expiration time associated with the TB, the priority associated with the TB, the location of a source of the TB, the TB size, or the TB range specification. For example, referring to
At 1008, the encoding device may then select the subset of the plurality of TBs based on the rank assigned to each TB of the plurality of the TBs. For example, 1008 may be performed by FCNC TB selection component 1342 or by FCNC TB selection component 1442. The selected subset of the plurality of TBs may be a number of TBs identified, at 1004, as the number of TBs to be included in the FCNC request with the highest rank as assigned at 1006. The selected subset of the plurality of TBs, in some aspects, may be a number of TBs less than the number of TBs identified, at 1004, as a maximum number of TBs to be included in the FCNC request with an assigned, at 1006, rank that is higher than a threshold. In some aspects, the encoding device 704 may select 714 the subset of the plurality of TBs randomly. For example, referring to
At 1010, the encoding device may transmit, to a plurality of receiving devices and/or UEs a FCNC request for the subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs. For example, 1010 may be performed by FCNC transmission component 1344 or by FCNC transmission component 1444. In some aspects, the FCNC request may be a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration. The second indication that the NC packet is associated with the FCNC feedback configuration may include a bit in a header of the FCNC request. The FCNC feedback configuration, in some aspects, may be different from a feedback configuration for NC packets that are not FCNC requests. For example, referring to
The FCNC feedback configuration may include a third indication of a first number of shared feedback resources (bins), where each of the shared feedback resources may be associated with a different subset of receiving devices and/or UEs in the plurality of receiving devices and/or UEs and the first number of shared feedback resources is smaller than a number of receiving devices and/or UEs in the plurality of receiving devices and/or UEs. In some aspects, the first number of shared feedback resources is based on a number of feedback resources available for receiving the feedback from the plurality of UEs and a number of TBs in the subset of the plurality of TBs. The number of bins may be known (e.g., preconfigured) or signaled by the encoding device. In addition to signaling the number of bins, the FCNC request may include an indication of a method for a receiving device to identify a bin (e.g., a specific resource in a set of PSFCH resources) for providing feedback. A number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the subset of TBs, such that NB*NT≤N. In some aspects, the first number, NB, of bins may be one of (1) a largest integer that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs (e.g., NP/NT), (2) a largest value in a set of values that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, or (3) a threshold value if the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs is greater than the threshold value.
At 1012, the encoding device may receive, from at least one of the plurality of receiving devices and/or UEs feedback associated with the FCNC request based on the FCNC feedback configuration. For example, 1006 may be performed by FCNC feedback reception component 1346 or by FCNC feedback reception component 1446. The feedback may be based on a feedback configuration indicated in a FCNC request. For example, referring to
Finally, at 1014, the encoding device may encode, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of receiving devices and/or UEs. For example, 1008 may be performed by NC encoding component 1348 or by NC encoding component 1448. The combinations of TBs in the plurality of TBs combined in each NC packet may be selected to such that a number of expected NACK-to-ACK flips is above a threshold or is maximized. For example, referring to
The FCNC feedback configuration may include a second indication of a first number of shared feedback resources (bins), where each of the shared feedback resources may be associated with a different subset of receiving devices and/or UEs in the plurality of receiving devices and/or UEs and the first number of shared feedback resources is smaller than a number of receiving devices and/or UEs in the plurality of receiving devices and/or UEs. In some aspects, the first number of shared feedback resources is based on a number of feedback resources available for receiving the feedback from the plurality of UEs and a number of TBs in the subset of the plurality of TBs. The number of bins may be known (e.g., preconfigured) or signaled by the encoding device. In addition to signaling the number of bins, the FCNC request may include an indication of a method for a receiving device to identify a bin (e.g., a specific resource in a set of PSFCH resources) for providing feedback. A number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the subset of TBs, such that NB*NT≤N. In some aspects, the first number, NB, of bins may be one of (1) a largest integer that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs (e.g., NP/NT), (2) a largest value in a set of values that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, or (3) a threshold value if the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs is greater than the threshold value.
At 1104, the receiving device may transmit, to the network encoding device, feedback associated with the FCNC request based on the FCNC feedback configuration. For example, 1104 may be performed by feedback transmission component 1544. Transmitting, at 1104, the feedback associated with the FCNC request may include identifying a set of resources for providing feedback to the encoding device. Identifying the set of resources for providing feedback may include identifying a resource pool associated with each TB in the subset of the plurality of TBs and identifying a shared feedback resource in each resource pool for transmitting feedback regarding an associated TB in the subset of the plurality of TBs. The resource pool associated with each TB may be identified based on a packet identifier associated with the corresponding TB, and the shared feedback resource may be identified based on one or more of a UE identifier, a communication session identifier, a zone identifier, or a beam identifier. For example, referring to
The FCNC feedback configuration may include a second indication of a first number of shared feedback resources (bins), where each of the shared feedback resources may be associated with a different subset of receiving devices and/or UEs in the plurality of receiving devices and/or UEs and the first number of shared feedback resources is smaller than a number of receiving devices and/or UEs in the plurality of receiving devices and/or UEs. In some aspects, the first number of shared feedback resources is based on a number of feedback resources available for receiving the feedback from the plurality of UEs and a number of TBs in the subset of the plurality of TBs. The number of bins may be known (e.g., preconfigured) or signaled by the encoding device. In addition to signaling the number of bins, the FCNC request may include an indication of a method for a receiving device to identify a bin (e.g., a specific resource in a set of PSFCH resources) for providing feedback. A number, NB, of bins may be determined based on a number, NP, of available PSFCH resources and a number, NT, of TBs in the subset of TBs, such that NB*NT≤N. In some aspects, the first number, NB, of bins may be one of (1) a largest integer that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs (e.g., NP/NT), (2) a largest value in a set of values that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, or (3) a threshold value if the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs is greater than the threshold value.
At 1204, the receiving device may identify a set of resources for providing feedback to the encoding device. For example, 1204 may be performed by feedback resource identification component 1542. Identifying, at 1204, the set of resources for providing feedback may include identifying, at 1204a, a resource pool associated with each TB in the subset of the plurality of TBs. The resource pool associated with each TB may be identified based on a packet identifier associated with the corresponding TB. The receiving device may additionally identify, at 1204b, a shared feedback resource in each resource pool for transmitting feedback regarding an associated TB in the subset of the plurality of TBs. The shared feedback resource may be identified based on one or more of a UE identifier, a communication session identifier, a zone identifier, or a beam identifier. For example, referring to
Finally, at 1206, the receiving device may transmit, to the network encoding device, feedback associated with the FCNC request based on the FCNC feedback configuration. For example, 1206 may be performed by feedback transmission component 1544. Transmitting, at 1204, the feedback associated with the FCNC request may include transmitting the feedback via the set of resources identified at 1204. For example, referring to
The communication manager 1332 includes a packet retransmission identification component 1340 that is configured to receive a plurality of indications for a plurality of TBs for the network encoding device to retransmit, e.g., as described in connection with 902 and 1002 of
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 cellular baseband processor 1304, includes means for receiving a plurality of indications for a plurality of TBs for the network encoding device to retransmit. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for transmitting, to a plurality of UEs, a FCNC request for a subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for receiving, from at least one of the plurality of UEs, feedback associated with the FCNC request based on the FCNC feedback configuration. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for encoding, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of UEs. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for assigning a rank to each TB of the plurality of TBs. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for selecting the subset of the plurality of TBs based on the rank assigned to each TB of the plurality of TBs. The apparatus 1302, and in particular the cellular baseband processor 1304, may also include means for identifying a number of TBs included in the subset of the plurality of TBs based on available resources for the feedback. 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.
The communication manager 1432 includes a packet retransmission identification component 1440 that is configured to receive a plurality of indications for a plurality of TBs for the network encoding device to retransmit, e.g., as described in connection with 902 and 1002 of
The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts of
As shown, the apparatus 1402 may include a variety of components configured for various functions. In one configuration, the apparatus 1402, and in particular the baseband unit 1404, includes means for receiving a plurality of indications for a plurality of TBs for the network encoding device to retransmit. The apparatus 1402, and in particular the baseband unit 1404, may also include means for transmitting, to a plurality of UEs, a FCNC request for a subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The apparatus 1402, and in particular the baseband unit 1404, may also include means for receiving, from at least one of the plurality of UEs, feedback associated with the FCNC request based on the FCNC feedback configuration. The apparatus 1402, and in particular the baseband unit 1404, may also include means for encoding, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of UEs. The apparatus 1402, and in particular the baseband unit 1404, may also include means for assigning a rank to each TB of the plurality of TBs. The apparatus 1402, and in particular the baseband unit 1404, may also include means for selecting the subset of the plurality of TBs based on the rank assigned to each TB of the plurality of TBs. The means may be one or more of the components of the apparatus 1402 configured to perform the functions recited by the means. As described supra, the apparatus 1402 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.
The communication manager 1532 includes a FCNC reception component 1540 that is configured to receive, from a network encoding device, a FCNC request for a subset of a plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a first indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests, e.g., as described in connection with 1102 and 1202 of
The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts 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 cellular baseband processor 1504, includes means for receiving, from a network encoding device, a FCNC request for a subset of a plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a first indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests. The apparatus 1502, and in particular the cellular baseband processor 1504, may also include means for transmitting, to the network encoding device, feedback associated with the FCNC request based on the FCNC feedback configuration. The apparatus 1502, and in particular the cellular baseband processor 1504, may also include means for identifying a set of resources for transmitting the feedback associated with the FCNC request based on the FCNC feedback configuration.
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 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.
As described above, in some aspects, the encoding device may have insufficient information for determining which combined packets will result in at least an expected number, e.g., a known or configured number K, of NACK-to-ACK flips. The minimum expected number of expected NACK-to-ACK flips, in some aspects, may be a function of a known or configured value K and a bin size associated with a feedback configuration.
Aspects presented herein provide a way to collect information for determining which combined packets will result in an expected number of NACK-to-ACK flips. For example, an encoding device may transmit a feedback collection network coding packet including a subset of the packets (e.g., transport blocks) for which the encoding device is responsible for retransmitting to collect information relating to the subset of packets. The subset of the packets may be included in a plurality of transport blocks of the feedback collection network coding packet.
As described above, the number of resources used to receive individual feedback from each of the UEs in a subset of UEs may be more than is available in a slot or a set of PSFCH resources associated with the feedback from the subset of UEs. The feedback resources, e.g., for a feedback collection network coding packet for the purpose of bootstrapping, may exceed the available feedback resources in the slot or the set of PSFCH resources associated with the feedback from the subset of UEs. Bootstrapping may refer to soliciting feedback for the packets, for example.
Aspects presented herein provide a way to collect feedback information for a plurality of receiving devices in a limited number of feedback (e.g., PSFCH) resources by configuring shared feedback resources (e.g., bins) that may be used by multiple receiving devices. The shared feedback resources, in some aspects may be dynamically configured or known (preconfigured).
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. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. 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 an apparatus for wireless communication including at least one processor coupled to a memory and configured to receive a plurality of indications for a plurality of TBs for the network encoding device to retransmit; transmitting, to a plurality of UEs, a FCNC request for a subset of the plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a second indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests; receive, from at least one of the plurality of UEs, feedback associated with the FCNC request based on the FCNC feedback configuration; and encode, based on the received feedback, the plurality of TBs in at least one NC packet for transmission to the plurality of UEs.
Aspect 2 is the apparatus of aspect 1, the at least one processor further configured to assign a rank to each TB of the plurality of TBs; and select the subset of the plurality of TBs based on the rank assigned to each TB of the plurality of TBs.
Aspect 3 is the apparatus of aspect 2, where the rank assigned to each TB of the plurality of the TBs is based on at least one of an expiration time associated with the TB, a priority associated with the TB, a location of a source of the TB, a TB size, or a TB range specification.
Aspect 4 is the apparatus of any of aspects 1 to 3, the at least one processor further configured to identify a number of TBs included in the subset of the plurality of TBs based on available resources for the feedback.
Aspect 5 is the apparatus of any of aspects 1 to 4, where the second indication that the NC packet is associated with the FCNC feedback configuration includes a bit in a header of the FCNC request.
Aspect 6 is the apparatus of any of aspects 1 to 5, further including a transceiver couple to the at least one processor, where the FCNC feedback configuration includes a third indication of a first number of shared feedback resources, where each of the shared feedback resources is associated with a different subset of UEs in the plurality of UEs and the first number of shared feedback resources is smaller than a number of UEs in the plurality of UEs.
Aspect 7 is the apparatus of aspect 6, where the first number of shared feedback resources is based on a number of feedback resources available for receiving the feedback from the plurality of UEs and a number of TBs in the subset of the plurality of TBs.
Aspect 8 is the apparatus of aspect 7, where the first number of shared feedback resources is one of: (1) a largest integer that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, (2) a largest value in a set of values that is smaller than the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs, or (3) a threshold value if the number of feedback resources available for receiving feedback from the plurality of UEs divided by the number of transport blocks in the subset of the plurality of TBs is less than the threshold value.
Aspect 9 is the apparatus of any of aspects 1 to 8, where the subset of the plurality of TBs includes one or more TBs for which there is insufficient information to determine that a threshold number of NACK-to-ACK flips is expected based on a transmission of a first NC packet including a combination of TBs from the subset of the plurality of TBs.
Aspect 10 is the apparatus of aspect 9, where the threshold number of NACK-to-ACK flips is one of a known threshold value, or a lesser of the known threshold value and a value dependent upon a number of bins used to receive the feedback associated with the FCNC request.
Aspect 11 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to receive, from a network encoding device, a FCNC request for a subset of a plurality of TBs for collecting feedback information regarding the subset of the plurality of TBs, the FCNC request being a NC packet including a first indication that the NC packet is associated with an FCNC feedback configuration, the FCNC feedback configuration being different from a feedback configuration for NC packets that are not FCNC requests; and transmit, to the network encoding device, feedback associated with the FCNC request based on the FCNC feedback configuration.
Aspect 12 is the apparatus of aspect 11, where the FCNC feedback configuration includes a second indication of a first number of shared feedback resources, where each of the shared feedback resources is associated with a different subset of UEs in a plurality of UEs and the first number of shared feedback resources is smaller than a number of UEs in the plurality of UEs, where the UE is included in the plurality of UEs.
Aspect 13 is the apparatus of any of aspects 11 and 12, where the FCNC feedback configuration includes a second indication of a first number of shared feedback resources, where each of the shared feedback resources is associated with a different subset of UEs in a plurality of UEs and the first number of shared feedback resources is smaller than a number of UEs in the plurality of UEs, where the UE is included in the plurality of UEs
Aspect 14 is the apparatus of aspect 13, where the first number of shared feedback resources is based on a number of feedback resources available for transmitting the feedback and a number of transport blocks in the subset of the plurality of TBs.
Aspect 15 is the apparatus of any of aspects 11 to 14, further including a transceiver coupled to the at least one processor, the at least one processor further configured to identify a set of resources for transmitting the feedback associated with the FCNC request based on the FCNC feedback configuration.
Aspect 16 is the apparatus of aspect 15, where the at least one processor is configured to identify the set of resources by identifying a resource pool associated with each TB in the subset of the plurality of TBs; and identifying a shared feedback resource in each resource pool for transmitting feedback regarding an associated TB in the subset of the plurality of TBs.
Aspect 17 is the apparatus of aspect 16, where the resource pool associated with each TB is identified based on a packet identifier associated with the corresponding TB, and where the shared feedback is identified based on one or more of a UE identifier, a communication session identifier, a zone identifier, or a beam identifier
Aspect 18 is a method of wireless communication for implementing any of aspects 1 to 17.
Aspect 19 is an apparatus for wireless communication including means for implementing any of aspects 1 to 17.
Aspect 20 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 17.
