Processing of non-digital data to flow control feedback timing
By setting pre-configuration rules and uplink channel management for UE and base station in wireless communication system, the chaotic problems in downlink data transmission and flow control feedback timing are solved, and efficient data transmission and pipelined processing are achieved.
Patent Information
- Application Number
- CN202180030876.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-04-28
- Filing Date
- 2021-04-29
- Publication Date
- 2024-12-27
- Estimated Expiration
- 2041-04-29
AI Technical Summary
In wireless communication systems, user equipment (UE) and base stations experience confusion and inefficiency in downlink data transmission and flow control feedback timing, especially in the processing of non-digital data flow control feedback timing, leading to unnecessary retransmissions and scheduling errors.
Through pre-configured rules and uplink channel management, the UE and base station work together to ensure the synchronization of downlink data transmission and flow control feedback, avoiding confusion. This includes identifying allocated uplink channel resources and managing flow control feedback based on pre-configured timing, supporting data transmission under semi-persistent scheduling and dynamic scheduling.
It improves pipeline processing efficiency at the UE, avoids confusion between the UE and the base station, ensures efficient scheduling of data transmission and correct flow control feedback, and reduces retransmissions and scheduling errors.
Smart Images

Figure CN115462020B_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 17 / 243,553, filed by Khoshnevisan et al. on April 28, 2021, entitled “HANDLING OF NON-NUMERIC DATA TO FLOW CONTROL FEEDBACK TIMING,” which claims the benefit of U.S. Provisional Patent Application No. 63 / 019,197, filed by Khoshnevisan et al. on May 1, 2020, entitled “HANDLING OF NON-NUMERIC DATA TO FLOW CONTROL FEEDBACK TIMING,” which is assigned to the present assignee. Technical Field
[0003] The following relates generally to wireless communications, and more particularly to processing non-digital data to flow control feedback timing. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, text messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).
[0005] A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication of multiple communication devices, which may be referred to as user equipment (UE). In some wireless communication systems, a base station may send downlink data to a UE, and the UE may be configured to report flow control feedback (e.g., hybrid automatic repeat request (HARQ) feedback) for the downlink data. Improved techniques for receiving downlink data and reporting flow control feedback for downlink data at a UE and for sending downlink data and receiving flow control feedback for downlink data at a base station may be required. Summary of the invention
[0006] The present disclosure relates to methods, systems, devices, and apparatuses that support processing of non-digital data to flow control feedback timing. In general, the described techniques provide for efficiently scheduling downlink data transmission and flow control feedback for downlink data transmission to allow efficient pipeline processing at a user equipment (UE). In one aspect, the UE and the base station may follow preconfigured rules to facilitate downlink data transmission while avoiding confusion at the UE and the base station (e.g., confusion caused by being scheduled to report flow control feedback for downlink data transmission in a different order than the downlink data transmission is received). On the other hand, the UE may be configured to report flow control feedback for downlink data transmission in the next uplink control channel to avoid confusion at the UE and the base station (e.g., in the case where the UE misses downlink control information indicating the timing of flow control feedback for reporting downlink data transmission).
[0007] A method for wireless communication implemented by a UE is described. The method may include receiving first downlink control information for scheduling a first downlink data transmission from a base station, the first downlink control information indicating non-digital data to flow control feedback timing, receiving second downlink control information for scheduling a second downlink data transmission from the base station, the second downlink control information indicating digital data to flow control feedback timing, identifying resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission; and managing flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0008] An apparatus for wireless communication implemented by a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to receive first downlink control information for scheduling a first downlink data transmission from a base station, the first downlink control information indicating non-digital data to flow control feedback timing, receive second downlink control information for scheduling a second downlink data transmission from the base station, the second downlink control information indicating digital data to flow control feedback timing, identify resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission, and manage flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0009] Another apparatus for wireless communication implemented by a UE is described. The apparatus may include: means for receiving first downlink control information for scheduling a first downlink data transmission from a base station, the first downlink control information indicating non-digital data to flow control feedback timing; means for receiving second downlink control information for scheduling a second downlink data transmission from the base station, the second downlink control information indicating digital data to flow control feedback timing; means for identifying resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission; and means for managing flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0010] A non-transitory computer-readable medium storing code implemented by a UE for wireless communication is described. The code may include instructions executable by a processor to receive first downlink control information scheduling a first downlink data transmission from a base station, the first downlink control information indicating non-digital data-to-flow control feedback timing, receive second downlink control information scheduling a second downlink data transmission from the base station, the second downlink control information indicating digital data-to-flow control feedback timing, identify resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission, and manage flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data-to-flow control feedback timing and the first uplink channel.
[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, managing flow control feedback for a first downlink data transmission may include operations, features, components, or instructions for multiplexing flow control feedback for the first downlink data transmission with flow control feedback for a second downlink data transmission in resources of a second uplink channel based on a second uplink channel that occurs simultaneously with or before the first uplink channel.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a time between the first downlink data transmission and the second uplink channel can be greater than or equal to a duration configured for processing the first downlink data transmission.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, managing flow control feedback for a first downlink data transmission may include operations, features, components, or instructions for determining not to multiplex flow control feedback for the first downlink data transmission with flow control feedback for a second downlink data transmission in resources of the second uplink channel based on a second uplink channel occurring after the first uplink channel.
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, flow control feedback for managing a first downlink data transmission may include operations, features, components, or instructions for discarding the flow control feedback for the first downlink data transmission based on a second uplink channel occurring after the first uplink channel.
[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for reporting a negative acknowledgement of the first downlink data transmission in an uplink channel different from the second uplink channel based on discarding flow control feedback for the first downlink data transmission.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second downlink control information may be received in a downlink control channel monitoring opportunity subsequent to the first downlink control information.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a first downlink data transmission prior to a second downlink data transmission.
[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a first downlink data transmission prior to a semi-persistently scheduled downlink data transmission.
[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from a base station, third downlink control information that activates a semi-persistently scheduled downlink data transmission including the semi-persistently scheduled downlink data transmission.
[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control message indicating that a non-digital data-to-flow control feedback timing may be configured in a set of data-to-flow control feedback timings for downlink data transmission from a base station to a UE.
[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message may be a radio resource control (RRC) message including a set of data-to-flow control feedback timing.
[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second downlink control information indicates a downlink allocation index associated with a downlink data transmission group, which downlink data transmission group may be the same as the downlink data transmission group indicated by the first downlink control information, and managing flow control feedback for the first downlink data transmission includes multiplexing the flow control feedback for the first downlink data transmission with the flow control feedback for the second downlink data transmission in resources of a second uplink channel based on the downlink allocation index associated with the downlink data transmission group that is the same as the downlink data transmission group indicated by the first downlink control information.
[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, managing flow control feedback for a first downlink data transmission may include operations, features, components, or instructions for determining not to multiplex the flow control feedback for the first downlink data transmission in a second uplink channel based on a second uplink channel occurring within a duration configured for processing the first downlink data transmission.
[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, managing flow control feedback for a first downlink data transmission may include operations, features, components, or instructions for multiplexing the flow control feedback for the first downlink data transmission with flow control feedback for a semi-persistently scheduled downlink data transmission in resources of the first uplink channel based on a second uplink channel occurring after the first uplink channel.
[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a first downlink data transmission and a second downlink data transmission in a first component carrier.
[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a first downlink data transmission in a first component carrier and receiving a second downlink data transmission in a second component carrier different from the first component carrier.
[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a configuration for a flow control feedback codebook, and wherein the flow control feedback for managing the first downlink data transmission may be based on the configuration for the flow control feedback codebook.
[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the flow control feedback codebook includes an enhanced dynamic flow control feedback codebook.
[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first uplink channel comprises an uplink control channel and the second uplink channel comprises an uplink control channel or an uplink shared channel.
[0030] A method for wireless communication implemented by a base station is described. The method may include sending first downlink control information scheduling a first downlink data transmission to a UE, the first downlink control information indicating non-digital data to flow control feedback timing, sending second downlink control information scheduling a second downlink data transmission to the UE, the second downlink control information indicating digital data to flow control feedback timing, sending third downlink control information to the UE, the third downlink control information activating a semi-persistently scheduled downlink data transmission from the base station and indicating resources of a first uplink channel allocated to flow control feedback for semi-persistently scheduled downlink data transmissions of a plurality of semi-persistently scheduled downlink data transmissions, and receiving flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0031] A device for wireless communication implemented by a base station is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions can be executed by the processor to cause the device to send first downlink control information for scheduling a first downlink data transmission to a UE, the first downlink control information indicating non-digital data to flow control feedback timing, send second downlink control information for scheduling a second downlink data transmission to the UE, the second downlink control information indicating digital data to flow control feedback timing; send third downlink control information to the UE, the third downlink control information activates semi-persistent scheduling of downlink data transmission from the base station and indicates resources of a first uplink channel for flow control feedback of semi-persistent scheduling of downlink data transmissions of multiple semi-persistent scheduling of downlink data transmissions, and receive flow control feedback of the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0032] Another apparatus for wireless communication implemented by a base station is described. The apparatus may include: a component for sending a first downlink control information for scheduling a first downlink data transmission to a UE, the first downlink control information indicating a non-digital data to flow control feedback timing; a component for sending a second downlink control information for scheduling a second downlink data transmission to the UE, the second downlink control information indicating a digital data to flow control feedback timing; a component for sending a third downlink control information to the UE, the third downlink control information activating a semi-persistent scheduled downlink data transmission from the base station and indicating a resource of a first uplink channel for flow control feedback of a semi-persistent scheduled downlink data transmission of a plurality of semi-persistent scheduled downlink data transmissions; and a component for receiving flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0033] A non-transitory computer-readable medium storing code implemented by a base station for wireless communication is described. The code may include instructions executable by a processor to send first downlink control information scheduling a first downlink data transmission to a UE, the first downlink control information indicating non-digital data to flow control feedback timing, send second downlink control information scheduling a second downlink data transmission to the UE, the second downlink control information indicating digital data to flow control feedback timing, send third downlink control information to the UE, the third downlink control information activating a semi-persistently scheduled downlink data transmission from the base station and indicating resources of a first uplink channel allocated to flow control feedback for semi-persistently scheduled downlink data transmissions of a plurality of semi-persistently scheduled downlink data transmissions, and receive flow control feedback for the first downlink data transmission based on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second downlink control information may be sent in a downlink control channel monitoring opportunity subsequent to the first downlink control information.
[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a control message to a UE indicating that a non-digital data-to-flow control feedback timing may be configured in a set of data-to-flow control feedback timings for downlink data transmission from a base station to the UE.
[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a configuration for a flow control feedback codebook to the UE, and wherein the flow control feedback for managing the first downlink data transmission may be based on the configuration for the flow control feedback codebook. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Figure 1 A non-limiting implementation of a wireless communication system supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown.
[0038] Figure 2 A block diagram illustrating semi-persistent scheduling (SPS) according to aspects of the present disclosure is shown.
[0039] Figure 3 A block diagram illustrating flow control feedback for Physical Downlink Shared Channel (PDSCH) reports associated with non-numeric K1 values according to aspects of the present disclosure is shown.
[0040] Figure 4 A block diagram illustrating out-of-order operations according to aspects of the present disclosure is shown.
[0041] Figure 5 A non-limiting implementation of a wireless communication system supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown.
[0042] Figure 6 A block diagram illustrating out-of-order operations according to aspects of the present disclosure is shown.
[0043] Figure 7 A block diagram illustrating flow control feedback for a PDSCH scheduled with a non-numeric K1 value reported in the next Physical Uplink Control Channel (PUCCH) according to aspects of the present disclosure is shown.
[0044] Figure 8 A block diagram illustrating flow control feedback for a PDSCH scheduled with a non-numeric K1 value reported in a PUCCH allocated to an SPS PDSCH according to aspects of the present disclosure is shown.
[0045] Fig. 9 A block diagram illustrating out-of-order operations according to aspects of the present disclosure is shown.
[0046] Fig.10 A block diagram illustrating flow control feedback for PDSCHs in a first group scheduled with a non-numeric K1 value reported in a PUCCH allocated for flow control feedback for PDSCHs in a second group according to aspects of the present disclosure is shown.
[0047] Fig.11A block diagram illustrating flow control feedback of PDSCH reported in an unexpected PUCCH according to aspects of the present disclosure is shown.
[0048] Fig.12 and Fig.13 A block diagram of an apparatus supporting processing of non-digital data into flow control feedback timing according to aspects of the present disclosure is shown.
[0049] Fig.14 A block diagram of a communication manager supporting processing of non-digital data to flow control feedback timing is shown in accordance with aspects of the present disclosure.
[0050] Fig.15 A diagram of a system including a device supporting processing of non-digital data to flow control feedback timing is shown according to aspects of the present disclosure.
[0051] Fig.16 and Fig.17 A block diagram of an apparatus supporting processing of non-digital data into flow control feedback timing according to aspects of the present disclosure is shown.
[0052] Fig.18 A block diagram of a communication manager supporting processing of non-digital data to flow control feedback timing is shown in accordance with aspects of the present disclosure.
[0053] Fig.19 A diagram of a system including a device supporting processing of non-digital data to flow control feedback timing is shown according to aspects of the present disclosure.
[0054] Figures 20 to 31 A flow chart illustrating a method of supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0055] In some wireless communication systems, a base station may send downlink data to a user equipment (UE) in multiple downlink data channels (e.g., multiple allocated resources of a downlink physical data channel). In some cases, the UE may be configured to report flow control feedback of one or more of the downlink data channels to the base station. The base station may use the flow control feedback of the downlink data channel to determine whether to schedule a retransmission of downlink data previously sent in the downlink data channel (e.g., if the UE fails to receive the downlink data). In addition, when the UE is configured to report flow control feedback of downlink data in multiple downlink data channels to the base station, the wireless communication system may establish rules to prevent confusion at the UE or base station.
[0056] In one aspect, if the UE is scheduled for a first downlink data transmission, it may not be desirable for the UE to receive the second downlink data transmission before sending flow control feedback for the first downlink data transmission if the first downlink data transmission and the second downlink data transmission are associated with the same flow control feedback process. On the other hand, if the UE is scheduled for a first downlink data transmission, it may not be desirable for the UE to receive the second downlink data transmission after the first downlink data transmission and report flow control feedback for the second downlink data transmission before reporting flow control feedback for the first downlink data transmission.
[0057] According to these aspects, when the base station receives flow control feedback, the base station can identify that the flow control feedback is for the first downlink data transmission. That is, based on the above rules, the base station can avoid misinterpreting the flow control feedback of one downlink data transmission as the flow control feedback of another downlink data transmission. Because such confusion can be prevented, the base station can avoid unnecessarily erroneously scheduling retransmissions or missing opportunities to schedule retransmissions of downlink data transmissions. In addition, since the UE can be able to process the downlink data transmissions in the order in which the downlink data transmissions are received, the established rules can allow efficient pipeline processing at the UE.
[0058] In some cases, the UE may not receive a timing value (e.g., a digital timing value) for reporting flow control feedback for downlink data transmission in downlink control information (DCI) that schedules a first downlink data transmission. Instead, the UE may receive timing for reporting flow control feedback for the first downlink data transmission in the next DCI. In this case, if the UE misses a DCI including a timing value for reporting flow control feedback for the first downlink data transmission, the flow control feedback for the first downlink data transmission may be delayed. As a result, the UE may be scheduled to receive a second downlink data transmission and report flow control feedback for the second downlink data transmission before flow control feedback for the first downlink data transmission. Therefore, the UE may report flow control feedback for downlink data transmission in an order different from the order in which the downlink data transmission was received, resulting in confusion at the UE and the base station and inefficient pipeline processing at the UE.
[0059] As described herein, a wireless communication system may support efficient techniques for scheduling downlink data transmission and flow control feedback for downlink data transmission to allow efficient pipeline processing at the UE and prevent confusion at the UE and base station. In one aspect, the UE and the base station may follow preconfigured rules to facilitate downlink data transmission while avoiding confusion at the UE and the base station (e.g., confusion caused by being scheduled to report flow control feedback for downlink data transmission in a different order than the downlink data transmission is received). On the other hand, the UE may be configured to report flow control feedback for downlink data transmission in the next uplink control channel to avoid confusion at the UE and the base station (e.g., in the case where the UE misses a DCI indicating timing for reporting flow control feedback for downlink data transmission).
[0060] The aspects of the present disclosure introduced above are described below in the context of a wireless communication system. Non-limiting embodiments of processes and signaling exchanges that support processing of non-digital data to flow control feedback timing are then described. Aspects of the present disclosure are further illustrated and described by reference to apparatus diagrams, system diagrams, and flow charts related to processing of non-digital data to flow control feedback timing.
[0061] Figure 1 A non-limiting embodiment of a wireless communication system 100 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some aspects, the wireless communication system 100 may be a long term evolution (LTE) network, an LTE advanced (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some aspects, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
[0062] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be a geographic area over which the base stations 105 and the UEs 115 may support signal communications according to one or more radio access technologies.
[0063] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary or mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 Some UEs 115 are illustrated in FIG. Figure 1 As shown, the UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices).
[0064] The base stations 105 may communicate with the core network 130 or with each other, or both. For example, the base stations 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130), or directly and indirectly, via the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some aspects, the backhaul links 120 may be or include one or more wireless links.
[0065] One or more of the base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga-NodeB (any of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.
[0066] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some aspects, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as home appliances, vehicles, meters, etc.
[0067] like Figure 1As shown, the UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as base stations 105 and network devices including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.
[0068] UE 115 and base station 105 can communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.
[0069] In some aspects (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be performed by a UE 115 via a carrier, or a carrier may operate in a non-standalone mode in which a connection is anchored using a different carrier (e.g., of the same or different radio access technology).
[0070] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105 (e.g., in a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH)), or a downlink transmission from the base station 105 to the UE 115 (e.g., in a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH)). Sending downlink data in the PDSCH or on the resources of the PDSCH may be referred to as sending the PDSCH, sending control information on the PDCCH or on the resources of the PDCCH may be referred to as sending the PDCCH, sending uplink data in the PUSCH or on the resources of the PUSCH may be referred to as sending the PUSCH, and sending uplink control information in the PUCCH or on the resources of the PUCCH may be referred to as sending the PUCCH. A carrier may carry downlink or uplink communications (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode).
[0071] A carrier may be associated with a specific bandwidth of a radio frequency spectrum, and in some aspects, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a specific radio access technology. The devices of the wireless communication system 100 (e.g., base stations 105, UEs 115, or both) may have a hardware configuration that supports communications on a specific carrier bandwidth or may be configurable to support communications on one of the carrier bandwidths in a set of carrier bandwidths. In some aspects, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communications via carriers associated with multiple carrier bandwidths. In some aspects, each served UE 115 may be configured to operate on a portion (e.g., a sub-band, a BWP) or all of the carrier bandwidth.
[0072] The signal waveform transmitted by the carrier wave may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM technology, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate of the UE 115 can be. Wireless communication resources may refer to a combination of radio spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity used for communication with the UE 115.
[0073] The base station 105 and the UE 115 may support communication using one or more parameters on the carrier, where the parameters may include subcarrier spacing (Δf) and cyclic prefix. The carrier may be divided into one or more BWPs with the same or different parameter sets. In some aspects, the UE 115 may be configured with multiple BWPs. In some aspects, a single BWP for a carrier may be active at a given time, and communication for the UE 115 may be limited to one or more activated BWPs.
[0074] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit. In some aspects, the basic time unit can be referred to as T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0075] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some aspects, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a plurality of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a plurality of symbol periods (e.g., depending on the length of a cyclic prefix prefixed to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots comprising one or more periods. In addition to the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
[0076] A subframe, slot, mini-slot, or cycle may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some aspects, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0077] Physical channels may be multiplexed on a carrier according to various techniques. According to some aspects, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a plurality of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0078] In some aspects, the base stations 105 can be mobile, thus providing communication coverage for mobile geographic coverage areas 110. In some aspects, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other aspects, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. According to some aspects, the wireless communication system 100 can include a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
[0079] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE115 may be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include service priorities, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency may be used interchangeably herein.
[0080] In some aspects, the UE 115 may also communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or unable to receive transmissions from the base station 105. In some aspects, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to each other UE 115 in the group. In some aspects, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.
[0081] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connection, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a user plane function (UPF)) for routing packets or interconnections to an external network. The control plane entity may manage non-access stratum (NAS) functions of UE 115 served by a base station 105 associated with the core network 130, such as mobility, authentication, and bearer management. User IP packets may be transmitted through user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. The operator IP service 150 may include access to the Internet, (multiple) intranets, an IP multimedia subsystem (IMS), or a packet-switched streaming service.
[0082] Some network devices, such as base stations 105, may include subcomponents, such as access network entities 140, which may be access node controllers (ANCs), etc. Each access network entity 140 may communicate with the UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).
[0083] The wireless communication system 100 can operate using one or more frequency bands typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is from about 1 decimeter to 1 meter long. UHF waves may be blocked or redirected by buildings and environmental features, but these waves can penetrate structures sufficiently so that macro cells provide services to UEs 115 located indoors. Compared to transmissions of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz, transmissions of UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).
[0084] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as base stations 105 and UE 115 can adopt carrier sensing for conflict detection and avoidance. In some aspects, operations in unlicensed bands can be based on carrier aggregation configurations and component carriers operating in licensed bands (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, etc.
[0085] The base station 105 or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some aspects, the antennas or antenna arrays associated with the base station 105 may be located at various geographic locations. The base station 105 may have an antenna array having multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.
[0086] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape and steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be implemented by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other direction).
[0087] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, the communication at the bearer or packet data aggregation protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on a logical channel. The medium access control (MAC) layer can perform priority processing and multiplex logical channels into transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration, and maintenance of the RRC connection between the base station 105 or the core network 130 that supports the radio bearer of the user plane data. At the physical layer, the transport channel can be mapped to the physical channel.
[0088] UE 115 and base station 105 can support retransmission of data to increase the possibility of successfully receiving data. Flow control feedback is a technique to increase the possibility of correctly receiving data through communication link 125. Flow control feedback can include an acknowledgment (ACK) indicating that the receiving device successfully decodes the transmission and a negative ACK (NACK) indicating that the receiving device fails to decode the transmission. Flow control feedback (i.e., feedback that controls the communication flow between base station 105 and UE 115) can include hybrid automatic repeat request (HARQ) feedback. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput of the media access control (MAC) layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some aspects, the device can support the same time slot HARQ feedback, wherein the device can provide HARQ feedback for data received in the previous cycle in the time slot in a specific time slot. In other cases, the device can provide HARQ feedback in a subsequent time slot or according to some other time interval.
[0089] In the wireless communication system 100, the base station 105 may use semi-persistent grants to schedule multiple downlink transmissions to the UE 115. Such scheduling may be referred to as semi-persistent scheduling (SPS) and may be used to limit overhead and processing latency (e.g., because semi-static grants may be sent less frequently than dynamic grants).
[0090] Figure 2A block diagram 200 illustrating an SPS according to aspects of the present disclosure is shown. An SPS downlink transmission in a PDSCH may be referred to as an SPS PDSCH 210, and the base station 105 may send higher layer (e.g., RRC) signaling to the UE 115 to configure parameters of the SPS. For example, the base station 105 may send RRC signaling to the UE 115 to indicate the period of the SPS PDSCH 210, the number of flow control feedback processes associated with the SPS PDSCH, etc. The base station 105 may then send an activation DCI 205 to activate the SPS or activate an SPS configuration (e.g., a DCI with a cyclic redundancy check (CRC) scrambled by a cell-specific radio network temporary identifier (CS-RNTI)). The activation DCI 205 may also indicate the time or frequency resources of each SPS PDSCH 210, the modulation and coding scheme (MCS) used for the SPS PDSCH 210, the timing for reporting flow control feedback for each SPS PDSCH 210 in the PUCCH 215, etc.
[0091] Once the SPS configuration is activated by the activation DCI 205, the UE 115 may receive the SPS PDSCH 210 based on the period indicated by the base station 105 until another DCI releases the SPS configuration. The timing for reporting the flow control feedback for the PDSCH may be referred to as the K1 value (e.g., such as a multiple of the time intervals between the PDSCH and the PUCCH to allocate the time slots for reporting the flow control feedback for the PDSCH). The UE 115 may use the K1 value for all SPS PDSCH 210 indicated in the activation DCI 205. Figure 2 , the K1 value of the SPS PDSCH 210 may be 3, and the UE 115 may receive three or more SPS PDSCHs 210 and report flow control feedback of three or more SPS PDSCHs 210. For example, the UE 115 may receive the first SPS PDSCH 210 and report flow control feedback of the first SPS PDSCH 210 three slots later in the first PUCCH 215, the UE 115 may receive the second SPS PDSCH 210 and report flow control feedback of the second SPS PDSCH 210 three slots later in the second PUCCH 215, and the UE 115 may receive the third SPS PDSCH 210 and report flow control feedback of the third SPS PDSCH 210 three slots later in the third PUCCH 215.
[0092] In addition to supporting SPS downlink transmissions and flow control feedback for SPS downlink transmissions, the base station 105 and the UE 115 may support downlink transmissions or PDSCHs in different downlink transmission groups or PDSCH groups. The base station 105 may send a DCI to the UE 115 that schedules the PDSCH and indicates a value (e.g., 0 or 1) of the PDSCH group of the scheduled PDSCH (e.g., in a PDSCH group indicator field). The base station 105 may increase a downlink allocation index (DAI) (e.g., a counter DAI (C-DAI) or a total DAI (T-DAI)) for each PDSCH group. The DCI may also include a bit (e.g., a field for the number of requested PDSCH groups) indicating whether flow control feedback for another PDSCH group (e.g., a PDSCH group different from the PDSCH group including the scheduled PDSCH) is requested.
[0093] In addition, the DCI may include a new feedback indicator (NFI) field indicating whether the UE 115 is to report the flow control feedback of the previous PDSCH. That is, the NFI can operate as a switching bit, and when the NFI is switched, the DAI of the PDSCH group can be reset, and the UE 115 can prohibit the transmission of the flow control feedback (e.g., ACK or NACK) of the PDSCH in the PDSCH group received before the DAI is reset (e.g., only considering the PDSCH received after the reset). If the base station 105 and the UE 115 support multiple PDSCH groups, a flow control codebook can be generated for each PDSCH group separately. The flow control codebook can be referred to as an enhanced type 2 codebook, and the PDSCH group reporting flow control feedback for each PDSCH group can be referred to as a type 2 HARQ codebook group and HARQ retransmission. Therefore, the UE 115 can report flow control feedback for different PDSCH groups separately. In some cases, the UE 115 can be repeated in the same PUCCH for flow control feedback of different PDSCH groups.
[0094] In the above aspects, the base station 105 can configure a K1 value for the PDSCH, and the UE 115 can report the flow control feedback of the PDSCH in the PUCCH allocated K1 time intervals after receiving the PDSCH. That is, the UE 115 can determine the time interval (e.g., time slot) for sending the flow control feedback of the PDSCH from the PDSCH-to-flow-control-feedback-timing-indicator field indicating the K1 value in the DCI that schedules the PDSCH. Such a K1 value can be referred to as a digital K1 value because it indicates the number of time intervals (e.g., time slots) after the PDSCH for which the flow control feedback is to be reported. In some aspects, the UE 115 can receive a DCI (e.g., DCI 1_0 or a fallback downlink DCI) that includes a field having three bits that indicates the K1 value of the PDSCH (e.g., one of the values in the set: {1, 2, ..., 8}). In other aspects, UE 115 may receive a higher layer message indicating a set of K1 values (e.g., a higher layer parameter downlink-data-to-uplink-ACK timing set configured by RRC), and UE 115 may receive DCI including a field having up to three bits indicating one of the K1 values in the set of K1 values configured in the higher layer message.
[0095] However, in some cases, the base station 105 may send an indication of a non-numeric K1 value (e.g., an inapplicable value) for reporting flow control feedback for the PDSCH. The non-numeric K1 value may be configured as one of a set of K1 values indicated by a higher layer message. When the base station 105 indicates a non-numeric K1 value in a first DCI for the PDSCH (e.g., when the PDSCH-to-HARQ-feedback timing indicator field indicates a non-numeric K1 value), flow control feedback for the PDSCH may be postponed until the timing and resources for flow control feedback are provided by the base station 105 in a second DCI. In the case of a type 1 (e.g., semi-static) or type 2 (e.g., dynamic) HARQ codebook, the second DCI may be the next DCI detected in any PDCCH monitoring opportunity after the first DCI indicating a numeric K1 value.
[0096] Figure 3 A block diagram 300 is shown illustrating flow control feedback for PDSCH reports associated with non-numeric K1 values according to aspects of the present disclosure. Figure 3, UE 115 may receive DCI 305-a from base station 105 that schedules PDSCH 310-a and indicates a non-digital K1 value for PDSCH 310-a. Therefore, UE 115 may postpone reporting flow control feedback for PDSCH 310-a until base station 105 provides timing and resources for flow control feedback in the next DCI. Then, UE 115 may receive DCI 305-b that schedules PDSCH 310-b and indicates a digital K1 value for PDSCH 310-b. Because DCI 305-b may indicate a digital K1 value, UE 115 may determine to send flow control feedback for PDSCH 310-a based on the digital K1 value (e.g., if the digital K1 value is 2, then in a PUCCH that is allocated two time intervals later, as shown in the figure). Therefore, UE 115 may report flow control feedback for PDSCH 310-a and PDSCH 310-b in PUCCH 315 based on the digital K1 value. That is, UE 115 may report flow control feedback for PDSCH 310-a and PDSCH 310-b K1 time intervals after PDSCH 310-b (e.g., where K1 is the digital K1 value indicated in DCI 305-b).
[0097] However, in some cases, if UE 115 receives a non-digital K1 value for reporting flow control feedback for a first PDSCH, UE 115 may miss the next DCI indicating a digital K1 value for reporting flow control feedback for the PDSCH. In this case, the flow control feedback for the first PDSCH may be delayed, and UE 115 may be scheduled to receive a second PDSCH and report the flow control feedback for the second PDSCH before the flow control feedback for the first PDSCH. Therefore, UE 115 may report the flow control feedback for the PDSCH in an order different from the order in which the PDSCHs were received. Reporting the flow control feedback for the PDSCH in an order different from the order in which the PDSCHs were received may be referred to as out-of-order operation.
[0098] Figure 4 A block diagram 400 illustrating out-of-order operations according to aspects of the present disclosure is shown. Figure 4, UE 115 may receive a first PDSCH 405-a and a second PDSCH 405-b after a first PDSCH 405-b, and UE 115 may be scheduled to report flow control feedback of PDSCH 405-b in PUCCH 410-b before reporting flow control feedback of PDSCH 405-a in PUCCH 410-a. Out-of-order operation may be allowed if DSCH 405-a and PDSCH 405-b are in different component carriers and PUCCH 410-a and PUCCH 410-b are in the same uplink component carrier. However, in some cases, out-of-order operation may result in inefficient pipeline processing at UE 115 and confusion at base station 105 and UE 115 (e.g., confusion in determining which PDSCH corresponds to received flow control feedback). Therefore, it may not be desirable for UE 115 to support out-of-order operation. The wireless communication system 100 may support efficient techniques for scheduling PDSCH and flow control feedback of the PDSCH to allow efficient pipeline processing at the UE 115 and prevent confusion at the UE 115 and the base station 105 .
[0099] Figure 5 A non-limiting embodiment of a wireless communication system 500 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The wireless communication system 500 includes a UE 115-a, which may include a reference Figure 1 The wireless communication system 200 also includes a base station 105-a, which may include a reference Figure 1 One or more aspects of base station 105 are described. Base station 105-a can provide communication coverage for coverage area 110-a. Wireless communication system 200 can implement aspects of wireless communication system 100. According to some aspects, wireless communication system 500 supports efficient techniques for scheduling PDSCH and flow control feedback of PDSCH.
[0100] exist Figure 5, the base station 105-a may send a DCI to the UE 115-a that schedules the PDSCH 505 with a non-numeric K1 value, and the UE 115-a may report flow control feedback 510 for the PDSCH 505 to the base station 105-a using the techniques described herein. In one aspect, the UE 115-a and the base station 105-a may follow preconfigured rules to receive the PDSCH 505 and report flow control feedback 510 for the PDSCH 505 while avoiding out-of-order operation and preventing confusion at the UE 115-a and the base station 105-a (e.g., confusion caused by being scheduled to report flow control feedback for downlink data transmissions in a different order than the downlink data transmissions were received). On the other hand, UE 115-a can be configured to report flow control feedback 510 of PDSCH 505 in the next uplink control channel to avoid out-of-order operation and prevent confusion at UE 115-a and base station 105-a (e.g., in the event that UE 115-a misses the DCI indicating the digital K1 value).
[0101] Figure 6 A block diagram 600 illustrating out-of-order operations according to aspects of the present disclosure is shown. Figure 6 , UE 115 may receive DCI 605-a from base station 105 that schedules PDSCH 610-a and indicates a non-digital K1 value for PDSCH 610-a. Thus, UE 115 may postpone reporting flow control feedback for PDSCH 610-a until base station 105 provides timing and resources for flow control feedback in a subsequent DCI (e.g., until a digital K1 value is indicated in a subsequent DCI). However, in some cases, prior to receiving a DCI indicating a digital K1 value, UE 115 may be scheduled to receive SPS PDSCH 615 (e.g., or other types of PDSCH) and report flow control feedback for SPS PDSCH 615 (e.g., or other types of PDSCH) in PUCCH 620-a before reporting flow control feedback for PDSCH 610-a.
[0102] For example, UE 115 may miss (e.g., fail to receive or decode) DCI 605-b that schedules PDSCH 610-b and includes a digital K1 value (e.g., K1=3) indicating that UE 115 will report flow control feedback for PDSCH 610-a in PUCCH 620-a. UE 115 may then receive DCI 605-c that schedules PDSCH 610-c, which DCI 605-c includes a digital K1 value indicating that UE 115 will report flow control feedback for PDSCH 610-c and a previous PDSCH associated with a non-digital K1 value in PUCCH 620-b. That is, UE 115 may determine that DCI 605-c is a second DCI indicating a digital K1 value for PDSCH 610-a because UE 115 may have missed DCI 605-b. Therefore, UE 115 may report flow control feedback for PDSCH 610-a in PUCCH 620-b. As a result, flow control feedback for PDSCH 610-a and SPS PDSCH 615 may be out of order relative to the order in which PDSCH 610-a and SPS PDSCH 615 are received. If PDSCH 610-a and SPS PDSCH 615 are in different downlink component carriers, the out-of-order operation may not result in inefficiency. However, base station 105 may still expect flow control feedback for PDSCH 610-a in PUCCH 620-a, but UE 115 may send flow control feedback for PDSCH 610-a in PUCCH 620-b, resulting in confusion at base station 105.
[0103] UE 115 and base station 105 can use the techniques described herein to adapt to or avoid out-of-order operation. In one aspect, if at least one of the PDSCHs is an SPS PDSCH, flow control feedback for multiple PDSCHs can be allowed to be reported in an order different from the order in which the multiple PDSCHs are received. In a given scheduled cell, UE 115 can receive a first PDSCH in time slot i, where the corresponding flow control feedback for the first PDSCH is assigned to be sent in time slot j, and a second PDSCH, where the corresponding flow control feedback for the second PDSCH is assigned to be sent in a time slot prior to time slot j based on whether the first PDSCH or the second PDSCH is an SPS PDSCH (e.g., or another PDSCH without a corresponding PDCCH). In this regard, UE 115 can receive a first PDSCH scheduled by a first DCI indicating a non-digital K1 value, and receive a second PDSCH, where the corresponding timing of the flow control feedback for the first and second PDSCHs is out of order relative to the corresponding timing of receiving the first and second PDSCHs. The UE 115 may receive the first PDSCH before the second PDSCH or may receive the second PDSCH before the first PDSCH.Then, the UE 115 may report flow control feedback of the first PDSCH based on the second PDSCH being an SPS PDSCH.
[0104] On the other hand, the wireless communication system may prohibit a combination of an SPS PDSCH (e.g., an active SPS) and a PDSCH scheduled by a DCI indicating a non-numeric K1 value. For example, when an SPS configuration is activated in a component carrier (e.g., using periodic SPS PDSCH reception and corresponding periodic flow control feedback transmission), it may be desirable for the UE 115 to not receive a DCI that schedules a PDSCH in the same component carrier with a non-numeric K1 value until the SPS configuration is released. If the UE 115 receives a first DCI that activates the SPS PDSCH, and the UE 115 receives a second DCI that indicates a non-numeric K1 value for the PDSCH, the UE 115 may prohibit receiving the PDSCH based on the activated SPS PDSCH. Alternatively, when the UE 115 configures a non-numeric K1 value (e.g., in a set of downlink-data-to-uplink-ACK K1 values), the UE 115 may not expect to configure the SPS configuration, or the UE 115 may not expect to receive a DCI that activates the SPS configuration. If UE 115 receives a control message indicating that a non-digital K1 value is configured in the set of flow control feedback timing of PDSCH, and UE 115 receives DCI activating SPS PDSCH, UE 115 may prohibit receiving SPS PDSCH while configuring non-digital data to flow control feedback timing.
[0105] In yet another aspect, when UE 115 receives a first DCI that schedules a PDSCH with a non-numeric K1 value, UE 115 may consider sending flow control feedback for the PDSCH in the next PUCCH transmission with flow control feedback starting after a PDSCH processing time (e.g., N1 time intervals or symbols) after the end of the PDSCH. Specifically, if UE 115 fails to detect a second DCI indicating a numeric K1 value pointing to the next PUCCH transmission or an earlier PUCCH transmission, UE 115 may consider sending flow control feedback for the PDSCH in the next PUCCH transmission.
[0106] Figure 7 A block diagram 700 is shown illustrating flow control feedback for a PDSCH scheduled with a non-numeric K1 value reported in the next PUCCH according to aspects of the present disclosure. Figure 7 , UE 115 may receive DCI 705 that schedules PDSCH 710 and indicates a non-digital K1 value for reporting flow control feedback for PDSCH 710. However, UE 115 may not receive DCI indicating a digital K1 value before PUCCH 715-b. Therefore, UE 115 may consider reporting flow control feedback for PDSCH 710 in PUCCH 715-b. PUCCH 715-b may be the first PUCCH (e.g., the next PUCCH) after the duration (e.g., N1 symbols) configured for processing PDSCH 710 (e.g., because PUCCH 715-a is allocated during the duration configured for processing PDSCH 710).
[0107] As mentioned above, in Figure 7, UE 115 may determine whether to send flow control feedback for PDSCH 710 in PUCCH 715-b. In some cases, UE 115 may discard flow control feedback for PDSCH 710 scheduled with a non-digital K1 value. In other cases, UE 115 may multiplex flow control feedback for PDSCH 710 scheduled with a non-digital K1 value in PUCCH 715-b. Therefore, determining whether to send flow control feedback in PUCCH may correspond to discarding flow control feedback or sending flow control feedback in PUCCH (e.g., UE 115 may optionally send flow control feedback for PDSCH 710 in PUCCH 715-b). In both cases, the DCI that later indicates the digital K1 value pointing to the PUCCH after PUCCH 715-b may not indicate the timing for reporting flow control feedback for PDSCH 710. That is, if the UE 115 receives a DCI indicating a digital K1 value pointing to a PUCCH subsequent to the PUCCH 715-b, the UE 115 may refrain from reporting flow control feedback for the PDSCH 710 in the PUCCH corresponding to the digital K1 value.
[0108] In yet another aspect, if the UE 115 detects a first DCI scheduling a PDSCH with a non-numeric K1 value that is used to report flow control feedback for the scheduled PDSCH, and there is an SPS PDSCH whose corresponding flow control feedback is to be sent in the PUCCH, the UE 115 may multiplex the flow control feedback for the scheduled PDSCH with the flow control feedback for the SPS PDSCH in the PUCCH.
[0109] Figure 8 A block diagram 800 is shown illustrating flow control feedback for a PDSCH scheduled with a non-numeric K1 value reported in a PUCCH allocated to an SPS PDSCH according to aspects of the present disclosure. Figure 8, UE 115 may receive DCI 805-a (e.g., a first DCI) that schedules PDSCH 810-a and indicates a non-digital K1 value for reporting flow control feedback for PDSCH 810-a. However, UE 115 may miss (e.g., fail to receive or decode) DCI 805-b (e.g., a second DCI) that schedules PDSCH 810-b and indicates a digital K1 value for reporting flow control feedback for PDSCH 810-a and PDSCH 810-b (e.g., corresponding to PUCCH 820-a). Therefore, after receiving SPS PDSCH 815, UE 115 may multiplex the flow control feedback of PDSCH 810-a with the flow control feedback of SPS PDSCH 815 in PUCCH 820-a (e.g., to avoid out-of-order operation). The UE 115 may then receive DCI 805-c scheduling the PDSCH 810-c with the digital K1 value corresponding to the PUCCH 820-b, and the UE 115 may report flow control feedback for the PDSCH 810-c in the PUCCH 820-b.
[0110] In some cases, if the UE 115 fails to detect a DCI 805-b (e.g., a second DCI) indicating a digital K1 value pointing to a time interval for flow control feedback transmission prior to a time interval for flow control feedback transmission for the SPS PDSCH 815, the UE 115 may multiplex the flow control feedback of the PDSCH 810-a with the flow control feedback of the SPS PDSCH 815. The UE 115 may monitor the DCI 805-b indicating the digital K1 value in any PDCCH monitoring opportunity after the PDCCH monitoring opportunity corresponding to the DCI 805-a (e.g., the first DCI) indicating a non-digital K1 value. In addition, if the SPS PDSCH (e.g., a PDSCH scheduled by the first DCI) is received after the DCI 805-a or after the PDSCH 810-a, the UE 115 may multiplex the flow control feedback of the PDSCH 810-a with the flow control feedback of the SPS PDSCH 815. Alternatively, if the time between PDSCH 810-a (e.g., a scheduled PDSCH) and PUCCH 820-a (e.g., a PUCCH allocated for reporting flow control feedback for SPS PDSCH 815) meets the minimum UE PDSCH processing timeline, the UE 115 can multiplex the flow control feedback for PDSCH 810-a with the flow control feedback for SPS PDSCH 815. If the UE 115 receives PDSCH 810-a and SPS PDSCH 815 in the same downlink component carrier, the UE 115 can also multiplex the flow control feedback for PDSCH 810-a with the flow control feedback for SPS PDSCH 815. Alternatively, if UE 115 receives PDSCH 810-a and SPS PDSCH 815 in different downlink component carriers (e.g., for different downlink component carriers and not within the same downlink component carrier, or regardless of whether PDSCH 810-a and SPS PDSCH 815 are in the same or different component carriers), UE 115 may multiplex the flow control feedback of PDSCH 810-a with the flow control feedback of SPS PDSCH 815.
[0111] As reference Figure 2As described, in addition to supporting SPS PDSCH, UE 115 may support multiple PDSCH groups when communicating with base station 105 (e.g., UE 115 is configured with an enhanced dynamic codebook as a PDSCH-HARQ-ACK codebook). If a first DCI schedules a PDSCH in a first PDSCH group and indicates a non-digital K1 value, UE 115 may monitor a second DCI (e.g., a second DCI indicating a digital K1 value for the PDSCH in the first group associated with a non-digital K1 value) that determines the timing for reporting flow control feedback for the PDSCH in the first PDSCH group. The second DCI may be the next DCI detected in any PDCCH monitoring opportunity after the first DCI indicating a digital K1 value and indicating a flow control feedback information report for the first PDSCH group (e.g., the second DCI indicates the same PDSCH group index as the first DCI). For example, the second DCI may include a PDSCH group indicator field indicating the first PDSCH group. Alternatively, the PDSCH group indicator field may indicate the second PDSCH group, but the second DCI may also request flow control feedback for PDSCHs in the first PDSCH group (e.g., a non-scheduled PDSCH group) in a field indicating the number of PDSCH groups requested. However, in some cases, because the UE 115 may be scheduled with a non-numeric K1 value for the first PDSCH, the UE 115 may receive the second PDSCH and report flow control feedback for the second PDSCH before reporting flow control feedback for the first PDSCH.
[0112] Fig. 9 A block diagram 900 illustrating out-of-order operations according to aspects of the present disclosure is shown. Fig. 9 , UE 115 may receive DCI 905-a from base station 105 that schedules PDSCH 910-a in a first PDSCH group and indicates a non-digital K1 value for PDSCH 910-a. Therefore, UE 115 may postpone reporting flow control feedback for PDSCH 910-a until base station 105 provides timing and resources for flow control feedback in a subsequent DCI (e.g., until a digital K1 value is indicated in a subsequent DCI). However, in some cases, before receiving a DCI indicating a digital K1 value in a subsequent DCI requesting flow control feedback for the first PDSCH group, UE 115 may receive DCI 905-b that schedules PDSCH 915 in a second PDSCH group, receive PDSCH 915, and report flow control feedback for PDSCH 915 in PUCCH 920-a before reporting flow control feedback for PDSCH 910-a.
[0113] For example, UE 115 may miss (e.g., fail to receive or decode) DCI 905-c that schedules PDSCH 910-b and includes a digital K1 value and indicates that UE 115 will report flow control feedback for PDSCH 910-a in the first group in PUCCH 910-a (e.g., K1=2). Then, UE 115 may receive DCI 905-d that schedules PDSCH 910-c in the first PDSCH group, which includes a digital K1 value indicating that UE 115 will report flow control feedback for PDSCH 910-c and a previous PDSCH (e.g., PDSCH 910-a) in the first PDSCH group associated with a non-digital K1 value. That is, UE 115 may determine that DCI 905-d is a second DCI indicating a digital K1 value for PDSCH 910-a in the first PDSCH group because UE 115 may have missed DCI 905-c. Therefore, the UE 115 may report flow control feedback for the PDSCH 910-a in the PUCCH 920-b (e.g., for the case of an enhanced dynamic codebook, similar to the reference in the presence of SPS). Figure 6 described scenario).
[0114] As a result, the flow control feedback for PDSCH 910-a and PDSCH 915 may be out of order relative to the order in which PDSCH 910-a and PDSCH 915 were received. If PDSCH 910-a and PDSCH 915 were in different downlink carriers, the out-of-order operation may not result in inefficiency. However, the base station 105 may still expect the flow control feedback for PDSCH 910-a in PUCCH 920-a, but the UE 115 may send the flow control feedback for PDSCH 910-a in PUCCH 920-b, resulting in confusion at the base station 105. The UE 115 and the base station 105 can use the techniques described herein to adapt to or avoid out-of-order operation. Specifically, if UE 115 receives a first DCI that schedules a first PDSCH in a first PDSCH group with a non-digital K1 value, which is used to report flow control feedback of the first PDSCH, and UE 115 receives a second DCI that schedules a second PDSCH in a second group with a digital K1 value, which is used to report flow control feedback of the second PDSCH, then UE 115 can report the flow control feedback of the first PDSCH and the flow control feedback of the second PDSCH in a PUCCH corresponding to the digital K1 value indicated in the second DCI.
[0115] Fig.10A block diagram 1000 is shown illustrating flow control feedback for PDSCH in a first group scheduled with a non-numeric K1 value reported in a PUCCH allocated for flow control feedback for PDSCH in a second group according to aspects of the present disclosure. Fig.10 , UE 115 may receive DCI 1005-a (e.g., first DCI) that schedules PDSCH 1010-a in a first PDSCH group and indicates a non-digital K1 value for reporting flow control feedback for PDSCH 1010-a. Then, UE 115 may receive DCI 1005-b that schedules PDSCH 1015 in a second PDSCH group and indicates a digital K1 value for reporting flow control feedback for PDSCH 1015. However, UE 115 may miss (e.g., fail to receive or decode) DCI 1005-c (e.g., second DCI for the first PDSCH group) that schedules PDSCH 1010-b and indicates a digital K1 value for reporting flow control feedback for PDSCH 1010-a and PDSCH 1010-b. Thus, UE 115 may multiplex flow control feedback for PDSCH 1010-a in the first PDSCH group with flow control feedback for PDSCH 1015 in the second PDSCH group (e.g., to avoid out-of-order operation). UE 115 may then receive DCI 1005-d that schedules PDSCH 1010-c in the first PDSCH group with a digital K1 value corresponding to PUCCH 1020-b, and UE 115 may report the flow control feedback for PDSCH 1010-c in PUCCH 1020-b.
[0116] In one aspect, the DCI indicating the timing of flow control feedback transmission for a PDSCH previously scheduled with a non-digital K1 value indicated by a first DCI is the next DCI indicating a digital K1 value (e.g., in a PDCCH monitoring opportunity following the PDCCH monitoring opportunity corresponding to the first DCI), regardless of the PDSCH group indicated or requested in the first DCI and the next DCI. Fig.10 In the embodiment of the present invention, UE 115 may report flow control feedback of PDSCH 1010-a in PUCCH 1020-a corresponding to the digital K1 value of PDSCH 1015 indicated in DCI 1005-b. In some cases, if PDSCH 1010-a (e.g., a first PDSCH scheduled by a first DCI) and PDSCH 1015 (e.g., a second PDSCH scheduled by a next DCI) are received in the same downlink component carrier, UE 115 may multiplex the flow control feedback of PDSCH 1010-a with the flow control feedback of PDSCH 1015 in PUCCH 1020-a.
[0117] On the other hand, when UE 115 is configured with an enhanced dynamic flow control feedback codebook, if the DCI that schedules the PDSCH indicates a non-numeric K1 value, UE 115 can determine that the scheduled PDSCH is in multiple PDSCH groups (e.g., Fig.10 In this regard, the DCI that determines the timing of flow control feedback for the scheduled PDSCH is the next DCI that indicates the value of digital K1, regardless of the PDSCH group indicated or requested in the DCI (e.g., reference Fig.10 Similar to the above aspect, in Fig.10 In the embodiment of the present invention, UE 115 may report flow control feedback of PDSCH 1010-a in PUCCH 1020-a corresponding to the digital K1 value of PDSCH 1015 indicated in DCI 1005-b. That is, when flow control feedback of one or more PDSCHs in the second group is sent in PUCCH 1020-a, UE 115 may also report flow control feedback of PDSCH 1010-a in the first group scheduled by DCI 1005-a indicating a non-digital K1 value. When UE 115 is scheduled to report flow control feedback of PDSCH 1010-a (and other PDSCHs) in the first group in a later PUCCH (or the same PUCCH 1020-a), UE 115 may report a NACK corresponding to PDSCH 1010-a associated with the non-digital K1 value. UE 115 may report a NACK because PDSCH 1010-a associated with a non-digital K1 value may belong to two PDSCH groups (e.g., a first and a second PDSCH group), but flow control feedback for PDSCH 1010-a may have been reported in the flow control feedback of the first PDSCH group (e.g., in PUCCH 1020-a).
[0118] The base station 105 may increase a first DAI associated with the first PDSCH group and a second DAI associated with the second PDSCH group based on the PDSCH 1010-a in the first and second PDSCH groups. The DAI may indicate the number of PDSCHs of the PDSCH group for which the UE 115 will report its flow control feedback to the base station 105. If the UE 115 fails to receive a plurality of PDSCHs indicated by the DAI from the base station 105, the UE 115 may report NACKs for the remaining PDSCHs that the UE 115 failed to receive. In some cases, the base station 105 may send the first DAI and the second DAI to the UE 115, and in other cases, the base station 105 may send the maximum of the first DAI and the second DAI to the UE 115 (e.g., resulting in some NACKs in the flow control feedback codebook for one of the PDSCH groups). The UE 115 may then generate flow control feedback for the PDSCHs in the first group based on the first DAI, and generate flow control feedback for the PDSCHs in the second group based on the second DAI. Optionally, the UE 115 may generate flow control feedback for the PDSCH in the first group and flow control feedback for the PDSCH in the second group based on a maximum value of the first DAI and the second DAI.
[0119] exist Fig.10 , because for PDSCH 1010-a in the first group, the second DAI associated with the second group can be increased, the UE 115 can report the flow control feedback of PDSCH 1010-a and the flow control feedback of PDSCH 1020-a in the second group in PUCCH 1020-a, and the base station 105 can expect the flow control feedback of PDSCH 1010-a in PUCCH 1020-a. Specifically, the first DAI can be 1, the second DAI can be 2, and the UE 115 can report the flow control feedback of PDSCH 1010-a and PDSCH 1015 in PUCCH 1020-a based on the second DAI. If the base station 105-a indicates the maximum value of the first DAI and the second DAI to the UE 115, and the first DAI is lower than the second DI, when the UE 115 is scheduled to report the flow control feedback of the first PDSCH group, the UE 115 can determine that the PDSCH in the first PDSCH group is lost. That is, the base station 105 may send less PDSCHs to the UE 115 than the number of PDSCHs indicated in the DAI (e.g., because the base station 105 may indicate a second DAI to the UE 115, and the second DAI is greater than the first DAI). Therefore, the UE 115 may report a NACK for the lost PDSCH, and the base station 105 may ignore the NACK for the lost PDSCH (e.g., because the base station 105 may be able to determine that the lost PDSCH corresponding to the NACK was not sent).
[0120] In yet another aspect, when UE 115 receives a DCI that schedules a PDSCH in a PDSCH group with a non-digital K1 value, UE 115 may determine whether to send flow control feedback for the PDSCH in the next PUCCH transmission with a flow control feedback that starts after the PDSCH processing time after the PDSCH ends. In some cases, UE 115 may discard the flow control feedback for the PDSCH scheduled with a non-digital K1 value. In other cases, UE 115 may multiplex the flow control feedback for the PDSCH scheduled with a non-digital K1 value in the next PUCCH transmission. Therefore, determining whether to send flow control feedback in the PUCCH may correspond to discarding flow control feedback or sending flow control feedback in the PUCCH. If UE 115 abandons flow control feedback for the PDSCH, UE 115 may report a NACK for the PDSCH with a non-digital K1 value the next time it requests flow control feedback for the PDSCH group including the PDSCH. Furthermore, if the NFI field is toggled in the DCI that allocates the next PUCCH for flow control feedback, the UE 115 may report the flow control feedback in the next PUCCH.
[0121] Reference above Figures 5 to 10 In the described aspects, UE 115 may report flow control feedback for one PDSCH in a PUCCH allocated for reporting flow control feedback for a different PDSCH. Therefore, it may be a challenge for base station 105 to map flow control feedback received in a PUCCH to a corresponding PDSCH. In particular, reporting flow control feedback for a PDSCH associated with a non-numeric K1 value may result in a flow control feedback codebook mismatch problem.
[0122] Fig.11 A block diagram 1100 is shown illustrating flow control feedback of PDSCH reported in an unexpected PUCCH according to aspects of the present disclosure. Fig.11 1, UE 115 may receive DCI 1105-a that schedules PDSCH 1110-a and indicates a non-digital K1 value for reporting flow control feedback for PDSCH 1110-a. UE 115 may then miss DCI 1105-b that schedules PDSCH 1110-b and indicates a digital K1 value corresponding to PUCCH 1115-a. UE 115 may then receive DCI 1105-c that schedules PDSCH 1110-c and indicates a digital K1 value corresponding to PUCCH 1115-b.
[0123] Therefore, instead of reporting the flow control feedback of PDSCH 1110-a in PUCCH 1115-a, UE 115 may report the flow control feedback of PDSCH 1110-a in PUCCH 1115-b. That is, due to the lost DCI (e.g., DCI 1105-b), UE 115 may avoid sending PUCCH 1115-a (or at least avoid sending the flow control feedback of PDSCH 1110-a in PUCCH 1115-a). Instead, UE 115 may determine that DCI 1105-c is a second DCI that provides timing for reporting the flow control feedback of PDSCH 1110-a. However, base station 105 may expect to receive the flow control feedback of PDSCH 1110-a in PUCCH 1115-a, and there may be a problem with the flow control feedback codebook size mismatch with the flow control feedback received in PUCCH 1115-b. As a result, the base station 105 may be unable to decode the PUCCH 1115-b. The flow control feedback codebook mismatch problem may be caused by using the techniques described herein to report flow control feedback for the PDSCH associated with a non-numeric K1 value (e.g., Fig.11 As shown, although Fig.11 Out-of-order operations not shown).
[0124] To prevent the flow control feedback codebook mismatch problem, the UE 115 can be configured to multiplex the flow control feedback of the PDSCH associated with the non-numeric K1 value within all PUCCHs (e.g., PUCCH resources) that contain flow control feedback within a predefined window after the PDSCH processing time (e.g., N1 time intervals or symbols) after the end of the PDSCH. For example, the UE 115 may send the flow control feedback of the PDSCH in the next M time slots after N1 symbols after the PDSCH. In some cases, the UE 115 may receive an indication of the duration of the time window (e.g., M) in higher layer signaling (e.g., RRC signaling) from the base station 105. Using these techniques, the base station 105 may be able to identify the PUCCH that includes flow control feedback of the PDSCH associated with the non-numeric K1 value (e.g., the UE 115 and the base station 105 may be on the same page). Fig.11 In the present invention, even if UE 115 does not send PUCCH 1115-a due to missing DCI 1105-b (for example, if PUCCH 1115-b is within the time window), UE 115 can multiplex the flow control feedback of PDSCH 1110-a in PUCCH 1115-b, and base station 105 can recognize that the flow control feedback of PDSCH 1110-a is included in PUCCH 1115-b.
[0125] Fig.12A block diagram 1200 of a device 1205 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1205 may include one or more aspects of the UE 115 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0126] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to processing non-digital data to flow control feedback timing, etc.). The information may be passed to other components of the device 1205. The receiver 1210 may include a reference Fig.15 One or more aspects of the transceiver 1520 described herein. The receiver 1210 may utilize a single antenna or a set of antennas.
[0127] The communication manager 1215 can receive a first downlink data transmission scheduled by a first DCI from a base station, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, receive a second downlink data transmission from the base station, wherein the corresponding timing of the flow control feedback of the first downlink data transmission and the second downlink data transmission are out of sequence relative to the corresponding timing of receiving the first downlink data transmission and the second downlink data transmission, and report the flow control feedback of the first downlink data transmission to the base station based on the second downlink data transmission being an SPS downlink data transmission.
[0128] The communication manager 1215 may also receive a first DCI activating SPS downlink data transmission from a base station, receive a second DCI indicating non-digital data for downlink data transmission to flow control feedback timing, and prohibit receiving downlink data transmission based on the activated SPS downlink data transmission.
[0129] The communication manager 1215 may also receive a control message indicating configuration of non-digital data-to-flow control feedback timing in a set of data-to-flow control feedback timing for downlink data transmission from a base station to a UE, receive DCI activating SPS downlink data transmission to the UE, and prohibit reception of SPS downlink data transmission from a base station while configuring the non-digital data-to-flow control feedback timing.
[0130] The communication manager 1215 may also receive a first DCI from the base station that schedules a first downlink data transmission with non-digital data to flow control feedback timing, determine that the UE has failed to receive a second DCI indicating first digital data to flow control feedback timing for reporting flow control feedback for the first downlink data transmission, and manage the flow control feedback for the first downlink data transmission based on the failure to receive the second DCI.
[0131] The communication manager 1215 may also receive a first DCI for scheduling downlink data transmission with non-digital data to flow control feedback timing from the base station, identify resources of an uplink control channel allocated to flow control feedback for SPS downlink data transmission, and multiplex the flow control feedback for downlink data transmission with the flow control feedback for SPS downlink data transmission in the resources of the uplink control channel.
[0132] The communication manager 1215 may also receive from the base station a first DCI for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, receive from the base station a second DCI for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing, and report flow control feedback of the first downlink data transmission and flow control feedback of the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0133] The communication manager 1215 may also receive DCI from the base station for scheduling downlink data transmission with non-digital data to flow control feedback timing, identify one or more uplink control channels allocated within the time window for reporting flow control feedback for downlink data transmission, and multiplex the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window. The communication manager 1215 may include one or more aspects of the communication manager 1510 described herein.
[0134] The communication manager 1215 or its subcomponents may be implemented by hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1215 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
[0135] The communication manager 1215 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some aspects, the communication manager 1215 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some aspects, the communication manager 1215 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof according to various aspects of the present disclosure.
[0136] The transmitter 1220 may transmit signals generated by other components of the device 1205. In some aspects, the transmitter 1220 may be collocated with the receiver 1210 in a transceiver module. That is, the transmitter 1220 may include a reference Fig.15 One or more aspects of the transceiver 1520 are described. The transmitter 1220 may utilize a single antenna or a set of antennas.
[0137] Fig.13 A block diagram 1300 of a device 1305 supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1305 may include one or more aspects of the device 1205 or UE 115 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1345. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0138] The receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to processing non-digital data to flow control feedback timing, etc.). The information may be passed to other components of the device 1305. The receiver 1310 may include a reference Fig.15 One or more aspects of the transceiver 1520 described herein. The receiver 1310 may utilize a single antenna or a set of antennas.
[0139] The communication manager 1315 may include one or more aspects of the communication manager 1215 described herein. The communication manager 1315 may include a PDSCH manager 1320, a flow control feedback manager 1325, a DCI manager 1330, an SPS manager 1335, and a PUCCH manager 1340. The communication manager 1315 may include one or more aspects of the communication manager 1510 described herein.
[0140] The PDSCH 1320 may receive a first downlink data transmission scheduled by a first DCI from a base station, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, and receive a second downlink data transmission from the base station, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of receiving the first downlink data transmission and the second downlink data transmission. The flow control feedback manager 1325 may report flow control feedback for the first downlink data transmission to the base station based on the second downlink data transmission being an SPS downlink data transmission.
[0141] The DCI manager 1330 may receive a first DCI activating SPS downlink data transmission from a base station and receive a second DCI indicating non-digital data for downlink data transmission to flow control feedback timing. The PDSCH manager 1320 may prohibit receiving downlink data transmission based on the activated SPS downlink data transmission.
[0142] The flow control feedback manager 1325 may receive a control message indicating that non-digital data to flow control feedback timing is configured in a set of data to flow control feedback timing for downlink data transmission from the base station to the UE. The DCI manager 1330 may receive DCI to activate SPS downlink data transmission to the UE. The SPS manager 1335 may prohibit receiving SPS downlink data transmission from the base station while configuring non-digital data to flow control feedback timing.
[0143] The DCI manager 1330 may receive a first DCI from a base station that schedules a first downlink data transmission with non-digital data to flow control feedback timing, and determine that the UE fails to receive a second DCI indicating the first digital data to flow control feedback timing for reporting flow control feedback for the first downlink data transmission. The flow control feedback manager 1325 may manage flow control feedback for the first downlink data transmission based on the failure to receive the second DCI.
[0144] The DCI manager 1330 may receive a first DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The PUCCH manager 1340 may identify resources of an uplink control channel allocated for flow control feedback for SPS downlink data transmission. The flow control feedback manager 1325 may multiplex the flow control feedback for downlink data transmission with the flow control feedback for SPS downlink data transmission in the resources of the uplink control channel.
[0145] The DCI manager 1330 may receive from the base station a first DCI for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, and receive from the base station a second DCI for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing. The flow control feedback manager 1325 may report flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0146] The DCI manager 1330 may receive DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The PUCCH manager 1340 may identify one or more uplink control channels allocated within a time window for reporting flow control feedback for downlink data transmission. The flow control feedback manager 1325 may multiplex flow control feedback for downlink data transmission in one or more uplink control channels allocated within a time window.
[0147] The transmitter 1345 may transmit signals generated by other components of the device 1305. In some aspects, the transmitter 1345 may be collocated with the receiver 1310 in the transceiver module. That is, the transmitter 1345 may include a reference Fig.15 One or more aspects of the described transceiver 1520. The transmitter 1345 may utilize a single antenna or a set of antennas.
[0148] Fig.14 A block diagram 1400 of a communication manager 1405 supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The communication manager 1405 may include one or more aspects of the communication manager 1215, the communication manager 1315, or the communication manager 1510 described herein. The communication manager 1405 may include a PDSCH manager 1410, a flow control feedback manager 1415, a DCI manager 1420, an SPS manager 1425, a PUCCH manager 1430, a PDSCH group manager 1435, and a DAI manager 1440. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).
[0149] The PDSCH manager 1410 may receive a first downlink data transmission scheduled by a first DCI from a base station, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission. In some aspects, the PDSCH manager 1410 may receive a second downlink data transmission from a base station, wherein the respective timing of flow control feedback for the first downlink data transmission and the second downlink data transmission is out of order relative to the respective timing of receiving the first downlink data transmission and the second downlink data transmission. The flow control feedback manager 1415 may report flow control feedback for the first downlink data transmission to the base station based on the second downlink data transmission being an SPS downlink data transmission. In some cases, the first downlink data transmission is received before the second downlink data transmission. In some cases, the second downlink data transmission is received before the first downlink data transmission.
[0150] The DCI manager 1420 may receive a first DCI from a base station to activate SPS downlink data transmission. In some aspects, the DCI manager 1420 may receive a second DCI indicating non-digital data for downlink data transmission to flow control feedback timing. In some aspects, the PDSCH manager 1410 may prohibit receiving downlink data transmission based on the activated SPS downlink data transmission. In some aspects, prohibiting receiving downlink data transmission is based on the SPS downlink data transmission and the downlink data transmission being in the same component carrier.
[0151] In some aspects, the flow control feedback manager 1415 may receive a control message indicating that non-digital data to flow control feedback timing is configured in a set of data to flow control feedback timing for downlink data transmission from the base station to the UE. In some aspects, the DCI manager 1420 may receive a DCI to activate SPS downlink data transmission to the UE. The SPS manager 1425 may prohibit receiving SPS downlink data transmission from the base station while configuring non-digital data to flow control feedback timing. In some cases, the control message is an RRC message that includes a set of data to flow control feedback timing.
[0152] In some aspects, the DCI manager 1420 may receive a first DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. In some aspects, the DCI manager 1420 may determine that the UE failed to receive a second DCI indicating first digital data to flow control feedback timing for reporting flow control feedback timing for the first downlink data transmission. In some aspects, the flow control feedback manager 1415 may manage flow control feedback for the first downlink data transmission based on the failure to receive the second DCI.
[0153] In some aspects, the DCI manager 1420 may determine that the UE fails to receive the second DCI prior to the first uplink control channel, which is after the duration configured to process the first downlink data transmission. In some aspects, the flow control feedback manager 1415 may multiplex the flow control feedback for the first downlink data transmission in the first uplink control channel. In some aspects, the flow control feedback manager 1415 may abandon the flow control feedback for the first downlink data transmission scheduled with non-digital data to the flow control feedback timing based on the failure to receive the second DCI.
[0154] In some aspects, the DCI manager 1420 may receive a third DCI indicating a second digital data-to-flow control feedback timing for reporting flow control feedback for a second downlink data transmission in the same downlink data transmission group as the first downlink data transmission. In some aspects, the flow control feedback manager 1415 may report a negative acknowledgement of the first downlink data transmission in an uplink control channel corresponding to the second digital data-to-flow control feedback timing based on discarding the flow control feedback for the first downlink data transmission. In some aspects, reporting the negative acknowledgement of the first downlink data transmission is based on a new feedback indicator (NFI) for the same downlink data transmission group that was not switched in the third DCI.
[0155] In some aspects, the DCI manager 1420 may receive a third DCI indicating a second digital data-to-flow control feedback timing for reporting flow control feedback for the first downlink data transmission. In some aspects, the flow control feedback manager 1415 may refrain from reporting flow control feedback for the first downlink data transmission in an uplink control channel corresponding to the second digital data-to-flow control feedback timing based on determining that the UE failed to receive the second DCI prior to the first uplink control channel after the duration configured for processing the first downlink data transmission.
[0156] In some aspects, the DCI manager 1420 may receive a first DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The PUCCH manager 1430 may identify resources of an uplink control channel allocated for flow control feedback for SPS downlink data transmission. In some aspects, the flow control feedback manager 1415 may multiplex the flow control feedback for downlink data transmission with the flow control feedback for SPS downlink data transmission in the resources of the uplink control channel. In some aspects, the DCI manager 1420 may fail to receive a second DCI indicating digital data to flow control feedback timing that triggered flow control feedback for downlink data transmission prior to the uplink control channel, wherein the multiplexing is based on a failure to receive the second DCI.
[0157] In some aspects, the SPS manager 1425 may receive SPS downlink data transmission after the first DCI for scheduling downlink data transmission, wherein multiplexing is based on receiving SPS downlink data transmission after the first DCI. In some aspects, the SPS manager 1425 may receive SPS downlink data transmission after downlink data transmission, wherein multiplexing is based on receiving SPS downlink data transmission after downlink data transmission. In some cases, the time between downlink data transmission and the uplink control channel is greater than or equal to the minimum time for processing downlink data transmission at the UE. In some cases, downlink data transmission and SPS downlink data transmission are received in the same component carrier or different component carriers.
[0158] In some aspects, the DCI manager 1420 may receive from the base station a first DCI scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing. In some aspects, the DCI manager 1420 may receive from the base station a second DCI scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing. In some aspects, the flow control feedback manager 1415 may report flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0159] The PDSCH group manager 1435 may determine a first downlink data transmission in the first downlink data transmission group and a second downlink data transmission group based on a first DCI indicating non-digital data to flow control feedback timing. In some aspects, the DCI manager 1420 may receive a third DCI from the base station scheduling a third downlink data transmission in the first downlink data transmission group, the third DCI indicating the second digital data to flow control feedback timing. In some aspects, the flow control feedback manager 1415 may report a negative acknowledgement of the first downlink data transmission in a second uplink control channel corresponding to the second digital data to flow control feedback timing based on reporting flow control feedback for the first downlink data transmission in the first uplink control channel.
[0160] The DAI manager 1440 may receive, in a first DCI, a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation index associated with a second downlink data transmission group from a base station. In some aspects, the flow control feedback manager 1415 may generate flow control feedback for one or more downlink data transmissions in a first downlink data transmission group including the first downlink data transmission based on the first downlink allocation index. In some aspects, the flow control feedback manager 1415 may generate flow control feedback for one or more downlink data transmissions in a second downlink data transmission group including the first downlink data transmission and the second downlink data transmission based on the second downlink allocation index.
[0161] In some aspects, the DAI manager 1440 may receive, in a first DCI, from a base station a maximum value of a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation associated with a second downlink data transmission group. In some aspects, the flow control feedback manager 1415 may generate flow control feedback for one or more downlink data transmissions in a first downlink data transmission group including a first downlink data transmission based on a maximum value of the first downlink allocation index and the second downlink allocation index. In some aspects, the flow control feedback manager 1415 may generate flow control feedback for one or more downlink data transmissions in a second downlink data transmission group including a first downlink data transmission and a second downlink data transmission based on a maximum value of the first downlink allocation index and the second downlink allocation index. In some aspects, the PDSCH manager 1410 may receive the first downlink data transmission and the second downlink data transmission in the same component carrier.
[0162] In some aspects, the DCI manager 1420 may receive DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. In some aspects, the PUCCH manager 1430 may identify one or more uplink control channels allocated within a time window for reporting flow control feedback for downlink data transmission. In some aspects, the flow control feedback manager 1415 may multiplex the flow control feedback for downlink data transmission in one or more uplink control channels allocated within the time window. In some aspects, the PUCCH manager 1430 may receive a control message from a base station indicating a time window for reporting flow control feedback. In some cases, the time window for reporting flow control feedback is after a duration configured for processing downlink data transmission. In some aspects, the flow control feedback manager 1415 may multiplex the flow control feedback for downlink data transmission in a set of uplink control channels allocated within the time window.
[0163] Fig.15 A diagram of a system 1500 including a device 1505 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1505 can be an aspect of or include components of the device 1205, device 1305, or UE 115 as described herein. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1510, an I / O controller 1515, a transceiver 1520, an antenna 1525, a memory 1530, and a processor 1540. These components may communicate electronically via one or more buses (e.g., bus 1545).
[0164] The communication manager 1510 may receive a first downlink data transmission scheduled by a first DCI from a base station, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, receive a second downlink data transmission from the base station, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of receiving the first downlink data transmission and the second downlink data transmission, and report flow control feedback for the first downlink data transmission to the base station based on the second downlink data transmission being an SPS downlink data transmission.
[0165] The communication manager 1510 may also receive a first DCI activating SPS downlink data transmission from a base station, receive a second DCI indicating non-digital data for downlink data transmission to flow control feedback timing, and prohibit receiving downlink data transmission based on the activated SPS downlink data transmission.
[0166] The communication manager 1510 may also receive a control message indicating configuration of non-digital data-to-flow control feedback timing in a set of data-to-flow control feedback timing for downlink data transmission from a base station to a UE, receive DCI activating SPS downlink data transmission to the UE, and prohibit reception of SPS downlink data transmission from a base station while configuring the non-digital data-to-flow control feedback timing.
[0167] The communication manager 1510 may also receive, from the base station, a first DCI that schedules a first downlink data transmission with non-digital data to flow control feedback timing, determine that the UE has failed to receive a second DCI indicating first digital data to flow control feedback timing for reporting flow control feedback for the first downlink data transmission, and manage the flow control feedback for the first downlink data transmission based on the failure to receive the second DCI.
[0168] The communication manager 1510 may also receive a first DCI for scheduling downlink data transmission with non-digital data to flow control feedback timing from the base station, identify resources of an uplink control channel allocated to flow control feedback for SPS downlink data transmission, and multiplex the flow control feedback for the downlink data transmission with the flow control feedback for the SPS downlink data transmission in the resources of the uplink control channel.
[0169] The communication manager 1510 may also receive a first DCI from a base station for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, receive a second DCI from the base station for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing, and report flow control feedback of the first downlink data transmission and flow control feedback of the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0170] The communication manager 1510 may also receive DCI for scheduling downlink data transmission with non-digital data to flow control feedback timing from a base station, identify one or more uplink control channels allocated within a time window for reporting flow control feedback for downlink data transmission, and multiplex the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window.
[0171] I / O controller 1515 can manage input and output signals for device 1505. I / O controller 1515 can also manage peripheral devices that are not integrated into device 1505. In some cases, I / O controller 1515 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1515 can utilize a variety of communication protocols such as TCP, HTTP, and HTTPS. Or another known operating system. In other cases, I / O controller 1515 can be represented or interacted with by a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1515 can be implemented as part of a processor. In some cases, a user can interact with device 1505 via I / O controller 1515 or via hardware components controlled by I / O controller 1515.
[0172] The transceiver 1520 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. According to some aspects, the transceiver 1520 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1520 may also include a modem for modulating packets and providing the modulated packets to an antenna for transmission, and demodulating packets received from an antenna.
[0173] In some cases, a wireless device may include a single antenna 1525. However, in some cases, a device may have more than one antenna 1525, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously.
[0174] The memory 1530 may include RAM and ROM. The memory 1530 may store computer-readable computer executable code 1535, which includes instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 1530 may contain BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0175] Processor 1540 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1540 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks supporting processing of non-digital data to flow control feedback timing).
[0176] The code 1535 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code 1535 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 1535 may not be directly executed by the processor 1540, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0177] Fig.16A block diagram 1600 of a device 1605 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1605 may include one or more aspects of the base station 105 as described herein. The device 1605 may include a receiver 1610, a communication manager 1615, and a transmitter 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0178] The receiver 1610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to processing non-digital data to flow control feedback timing, etc.). The information may be passed to other components of the device 1605. The receiver 1610 may include a reference Fig.19 One or more aspects of the transceiver 1920 are described. The receiver 1610 may utilize a single antenna or a set of antennas.
[0179] The communication manager 1615 may send a first downlink data transmission scheduled by a first DCI to the UE, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, send a second downlink data transmission to the UE, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of sending the first downlink data transmission and the second downlink data transmission, and receive flow control feedback for the first downlink data transmission from the UE based on the second downlink data transmission being an SPS downlink data transmission.
[0180] The communication manager 1615 may also send a DCI to the UE to activate SPS downlink data transmission, and while activating the SPS downlink data transmission, prohibit scheduling downlink data transmission with non-digital data-to-flow control feedback timing.
[0181] The communication manager 1615 may also send a control message indicating that non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timing for downlink data transmission from the base station to the UE, and that activation of SPS downlink data transmission to the UE is prohibited while configuring the non-digital data-to-flow control feedback timing.
[0182] The communication manager 1615 may also send a first DCI to the UE for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, send a second DCI to the UE for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing, and receive flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0183] The communication manager 1615 may also send a DCI to the UE that schedules downlink data transmission with non-digital data to flow control feedback timing, identify one or more uplink control channels allocated within the time window for the UE to report flow control feedback for downlink data transmission, and monitor the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window. The communication manager 1615 may include one or more aspects of the communication manager 1910 described herein.
[0184] The communication manager 1615 or its subcomponents may be implemented by hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1615 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
[0185] The communication manager 1615 or its subcomponents can be physically located in various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some aspects, the communication manager 1615 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some aspects, the communication manager 1615 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof according to various aspects of the present disclosure.
[0186] The transmitter 1620 may transmit signals generated by other components of the device 1605. In some aspects, the transmitter 1620 may be collocated with the receiver 1610 in the transceiver module. That is, the transmitter 1620 may include a reference Fig.19 One or more aspects of the transceiver 1920 are described. The transmitter 1620 may utilize a single antenna or a set of antennas.
[0187] Fig.17 A block diagram 1700 of a device 1705 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1705 may include one or more aspects of the device 1605 or base station 105 as described herein. The device 1705 may include a receiver 1710, a communication manager 1715, and a transmitter 1745. The device 1705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0188] The receiver 1710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to processing non-digital data to flow control feedback timing, etc.). The information may be passed to other components of the device 1705. The receiver 1710 may include a reference Fig.19 One or more aspects of the transceiver 1920 are described. The receiver 1710 may utilize a single antenna or a set of antennas.
[0189] The communication manager 1715 may include one or more aspects of the communication manager 1615 described herein. The communication manager 1715 may include a PDSCH manager 1720, a flow control feedback manager 1725, a DCI manager 1730, an SPS manager 1735, and a PUCCH manager 1740. The communication manager 1715 may include one or more aspects of the communication manager 1910 described herein.
[0190] The PDSCH 1720 may transmit to the UE a first downlink data transmission scheduled by a first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, and transmit to the UE a second downlink data transmission, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of transmitting the first downlink data transmission and the second downlink data transmission. The flow control feedback manager 1725 may receive flow control feedback for the first downlink data transmission from the UE based on the second downlink data transmission being an SPS downlink data transmission.
[0191] The DCI manager 1730 may send a DCI to the UE to activate SPS downlink data transmission. The PDSCH manager 1720 may prohibit scheduling downlink data transmission with non-digital data to flow control feedback timing while activating SPS downlink data transmission.
[0192] The flow control feedback manager 1725 may send a control message indicating that non-digital data to flow control feedback timing is configured in the set of data to flow control feedback timing for downlink data transmission from the base station to the UE. The SPS manager 1735 may prohibit activation of SPS downlink data transmission to the UE while configuring the non-digital data to flow control feedback timing.
[0193] The DCI manager 1730 may send a first DCI to the UE that schedules a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, and send a second DCI to the UE that schedules a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing. The flow control feedback manager 1725 may receive flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0194] The DCI manager 1730 may send a DCI to the UE that schedules downlink data transmission with non-digital data to flow control feedback timing. The PUCCH manager 1740 may identify one or more uplink control channels allocated within the time window for the UE to report flow control feedback for downlink data transmission. The flow control feedback manager 1725 may monitor the flow control feedback for downlink data transmission in one or more uplink control channels allocated within the time window.
[0195] The transmitter 1745 may transmit signals generated by other components of the device 1705. In some aspects, the transmitter 1745 may be collocated with the receiver 1710 in the transceiver module. That is, the transmitter 1745 may include a reference Fig.19 One or more aspects of the transceiver 1920 are described. The transmitter 1745 may utilize a single antenna or a set of antennas.
[0196] Fig.18 A block diagram 1800 of a communication manager 1805 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The communication manager 1805 may include one or more aspects of the communication manager 1615, the communication manager 1715, or the communication manager 1910 described herein. The communication manager 1805 may include a PDSCH manager 1810, a flow control feedback manager 1815, a DCI manager 1820, an SPS manager 1825, a PDSCH group manager 1830, a DAI manager 1835, and a PUCCH manager 1840. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).
[0197] The PDSCH manager 1810 may send a first downlink data transmission scheduled by a first DCI to the UE, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission. In some aspects, the PDSCH manager 1810 may send a second downlink data transmission to the UE, wherein the respective timing of flow control feedback for the first downlink data transmission and the second downlink data transmission is out of order relative to the respective timing of sending the first downlink data transmission and the second downlink data transmission. The flow control feedback manager 1815 may receive flow control feedback for the first downlink data transmission from the UE based on the second downlink data transmission being an SPS downlink data transmission. In some cases, the first downlink data transmission is sent before the second downlink data transmission. In some cases, the second downlink data transmission is sent before the first downlink data transmission.
[0198] The DCI manager 1820 may send a DCI to the UE to activate SPS downlink data transmission. In some aspects, the PDSCH manager 1810 may prohibit scheduling downlink data transmission with non-digital data to flow control feedback timing while activating SPS downlink data transmission. In some aspects, the PDSCH manager 1810 may prohibit scheduling downlink data transmission within the same component carrier as the activated SPS downlink data transmission. In some aspects, the flow control feedback manager 1815 may send a control message indicating that non-digital data to flow control feedback timing is configured in a set of data to flow control feedback timing for downlink data transmission from the base station to the UE. The SPS manager 1825 may prohibit activation of SPS downlink data transmission to the UE while configuring non-digital data to flow control feedback timing. In some cases, the control message is an RRC message including a set of data to flow control feedback timing.
[0199] In some aspects, the DCI manager 1820 may send a first DCI to the UE that schedules a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing. In some aspects, the DCI manager 1820 may send a second DCI to the UE that schedules a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing. In some aspects, the flow control feedback manager 1815 may receive flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0200] The PDSCH group manager 1830 may determine a first downlink data transmission in the first downlink data transmission group and the second downlink data transmission group based on a first DCI indicating non-digital data to flow control feedback timing. In some aspects, the DCI manager 1820 may send a third DCI to the UE scheduling a third downlink data transmission in the first downlink data transmission group, the third DCI indicating the second digital data to flow control feedback timing. In some aspects, the flow control feedback manager 1815 may receive a negative acknowledgement of the first downlink data transmission in a second uplink control channel corresponding to the second digital data to flow control feedback timing based on receiving flow control feedback for the first downlink data transmission in the first uplink control channel.
[0201] The DAI manager 1835 may increase a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation index associated with a second downlink data transmission group based on indicating non-digital data to flow control feedback timing in the first DCI. In some aspects, the DAI manager 1835 may send the first downlink allocation index and the second downlink allocation index to the UE in the first DCI. In some aspects, the DAI manager 1835 may send a maximum value of the first downlink allocation index and the second downlink allocation index to the UE in the first DCI. In some aspects, the PDSCH manager 1810 may send the first downlink data transmission and the second downlink data transmission in the same component carrier.
[0202] In some aspects, the DCI manager 1820 may send a DCI to the UE that schedules downlink data transmission with non-digital data to flow control feedback timing. The PUCCH manager 1840 may identify one or more uplink control channels allocated within the time window for the UE to report flow control feedback for downlink data transmission. In some aspects, the flow control feedback manager 1815 may monitor the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window.
[0203] In some aspects, the PUCCH manager 1840 may send a control message to the UE indicating a time window for reporting flow control feedback. In some cases, the time window for reporting flow control feedback is after a duration configured for the UE to process downlink data transmissions. In some aspects, the flow control feedback manager 1815 may monitor flow control feedback for downlink data transmissions in a set of uplink control channels allocated within the time window.
[0204] Fig.19A diagram of a system 1900 including a device 1905 that supports processing non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The device 1905 may include one or more aspects of the device 1605, device 1705, or base station 105 as described herein, or include components of the device 1605, device 1705, or base station 105. The device 1905 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1910, a network communication manager 1915, a transceiver 1920, an antenna 1925, a memory 1930, a processor 1940, and an inter-station communication manager 1945. These components may be in electronic communication via one or more buses (e.g., bus 1950).
[0205] The communication manager 1910 may send a first downlink data transmission scheduled by a first DCI to the UE, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission, send a second downlink data transmission to the UE, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of sending the first downlink data transmission and the second downlink data transmission, and receive flow control feedback for the first downlink data transmission from the UE based on the second downlink data transmission being an SPS downlink data transmission.
[0206] The communication manager 1910 may also send a DCI to the UE to activate SPS downlink data transmission, and while activating the SPS downlink data transmission, prohibit scheduling downlink data transmission with non-digital data-to-flow control feedback timing.
[0207] The communication manager 1910 may also send a control message indicating that non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timing for downlink data transmission from the base station to the UE, and that activation of SPS downlink data transmission to the UE is prohibited while configuring the non-digital data-to-flow control feedback timing.
[0208] The communication manager 1910 may also send a first DCI to the UE for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing, send a second DCI to the UE for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating first digital data to flow control feedback timing, and receive flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0209] The communication manager 1910 may also send a DCI to the UE for scheduling downlink data transmission with non-digital data to flow control feedback timing, identify one or more uplink control channels allocated within a time window for the UE to report flow control feedback for downlink data transmission, and monitor the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window.
[0210] The network communications manager 1915 can manage communications with the core network (eg, via one or more wired backhaul links). According to some aspects, the network communications manager 1915 can manage the delivery of data communications for client devices, such as one or more UEs 115 .
[0211] The transceiver 1920 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. According to some aspects, the transceiver 1920 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1920 may also include a modem for modulating packets and providing the modulated packets to an antenna for transmission, and demodulating packets received from an antenna.
[0212] In some cases, a wireless device may include a single antenna 1925. However, in some cases, a device may have more than one antenna 1925, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously.
[0213] Memory 1930 may include RAM, ROM, or a combination thereof. Memory 1930 may store computer readable code 1935, which includes instructions that, when executed by a processor (e.g., processor 1940), cause the device to perform various functions described herein. In some cases, memory 1930 may include BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0214] Processor 1940 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1940 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1940. Processor 1940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1930) to cause device 1905 to perform various functions (e.g., functions or tasks supporting processing of non-digital data to flow control feedback timing).
[0215] The inter-site communication manager 1945 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other base stations 105. In some aspects, the inter-site communication manager 1945 may coordinate scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some aspects, the inter-site communication manager 1945 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.
[0216] The code 1935 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code 1935 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 1935 may not be directly executed by the processor 1940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0217] Fig. 20 A flow chart illustrating a method 2000 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 2000 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0218] At 2005, the UE may receive a first downlink data transmission scheduled by a first DCI from a base station, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission. The operation of 2005 may be performed according to the method described herein. In some aspects, aspects of the operation of 2005 may be referred to as Figures 12 to 15 The PDSCH manager is used to perform the above operations.
[0219] At 2010, the UE may receive a second downlink data transmission from the base station, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of receiving the first downlink data transmission and the second downlink data transmission. The operations at 2010 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations at 2010 may be described with reference to Figures 12 to 15 The PDSCH manager is used to perform the above operations.
[0220] At 2015, the UE may report flow control feedback of the first downlink data transmission to the base station based on the second downlink data transmission being the SPS downlink data transmission. The operation of 2015 may be performed according to the method described herein. In some non-limiting embodiments, the UE may report flow control feedback of the first downlink data transmission to the base station based on the second downlink data transmission being the SPS downlink data transmission. Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 2015.
[0221] Fig.21 A flow chart illustrating a method 2100 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by the base station 105 or components thereof, as described herein. According to some aspects, the operations of the method 2100 may be implemented by the base station 105 or components thereof, as described herein. Figure 16 to Figure 19 The communication manager described herein performs. In some aspects, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.
[0222] At 2105, the base station may send a first downlink data transmission scheduled by a first DCI to the UE, the first DCI indicating non-digital data to flow control feedback timing for the first downlink data transmission. The operation of 2105 may be performed according to the methods described herein. In some aspects, aspects of the operation of 2105 may be described with reference to Figures 16 to 19 The PDSCH manager is used to perform the above operations.
[0223] At 2110, the base station may send a second downlink data transmission to the UE, wherein respective timings of flow control feedback for the first downlink data transmission and the second downlink data transmission are out of sequence relative to respective timings of sending the first downlink data transmission and the second downlink data transmission. The operations of 2110 may be performed in accordance with the methods described herein. In some aspects, aspects of the operations of 2110 may be described with reference to Figures 16 to 19 The PDSCH manager is used to perform the above operations.
[0224] At 2115, the base station may receive flow control feedback of the first downlink data transmission from the UE based on the second downlink data transmission being an SPS downlink data transmission. The operations of 2115 may be performed according to the methods described herein. In some aspects, the flow control feedback may be performed as described in reference to Figure 16 to Figure 19 The flow control feedback manager is used to perform aspects of the operation of 2115.
[0225] Fig. 22A flow chart illustrating a method 2200 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by the UE 115 or components thereof, as described herein. According to some aspects, the operations of the method 2200 may be implemented by the UE 115 or components thereof, as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0226] At 2205, the UE may receive a first DCI from a base station to activate SPS downlink data transmission. The operation of 2205 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 2205 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0227] At 2210, the UE may receive a second DCI indicating non-digital data for downlink data transmission to flow control feedback timing. The operations of 2210 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 2210 may be described with reference to Figures 12 to 15 The DCI manager is used to perform the above operations.
[0228] At 2215, the UE may prohibit receiving downlink data transmission based on the activated SPS downlink data transmission. The operation of 2215 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2215 may be referred to as Figures 12 to 15 The PDSCH manager is used to perform the above operations.
[0229] Fig.23 A flow chart illustrating a method 2300 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by the base station 105 or components thereof, as described herein. According to some aspects, the operations of the method 2300 may be implemented by the base station 105 or components thereof, as described herein. Figure 16 to Figure 19 The communication manager described herein performs. In some aspects, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.
[0230] At 2305, the base station may send a DCI to the UE to activate SPS downlink data transmission. The operation of 2305 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2305 may be referred to as Figures 16 to 19 The DCI manager is used to perform the above operations.
[0231] At 2310, the base station may disable the use of non-digital data to flow control feedback timing scheduling downlink data transmission while activating SPS downlink data transmission. The operation of 2310 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2310 may be referred to as Figures 16 to 19 The PDSCH manager is used to perform the above operations.
[0232] Fig.24 A flow chart illustrating a method 2400 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2400 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 2400 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0233] At 2405, the UE may receive a control message indicating that a non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timings for downlink data transmission from a base station to the UE. The operation of 2405 may be performed according to the method described herein. In some non-limiting embodiments, the control message may be configured as described in reference to Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 2405.
[0234] At 2410, the UE may receive a DCI activating SPS downlink data transmission to the UE. The operations of 2410 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 2410 may be described with reference to Figures 12 to 15 The DCI manager is used to perform the above operations.
[0235] At 2415, the UE may prohibit receiving SPS downlink data transmissions from the base station while configuring non-digital data to flow control feedback timing. The operations of 2415 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 2415 may be described by reference to Figures 12 to 15 The SPS manager is used to execute.
[0236] Fig.25 A flow chart illustrating a method 2500 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2500 may be implemented by the base station 105 or components thereof, as described herein. According to some aspects, the operations of the method 2500 may be implemented by the base station 105 or components thereof, as described herein. Figure 16 to Figure 19The communication manager described herein performs. In some aspects, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.
[0237] At 2505, the base station may send a control message indicating that non-digital data to flow control feedback timing is configured in a set of data to flow control feedback timing for downlink data transmission from the base station to the UE. The operation of 2505 may be performed according to the method described herein. In some non-limiting embodiments, the control message may be configured as described in reference to Figure 16 to Figure 19 The flow control feedback manager is used to perform aspects of the operation of 2505.
[0238] At 2510, the base station may disable activation of SPS downlink data transmission to the UE while configuring non-digital data to flow control feedback timing. The operations of 2510 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 2510 may be described with reference to Figures 16 to 19 The SPS manager is used to execute.
[0239] Fig.26 A flow chart illustrating a method 2600 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2600 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 2600 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0240] At 2605, the UE may receive a first DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The operation of 2605 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2605 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0241] At 2610, the UE may determine that the UE has failed to receive a second DCI indicating first digital data to flow control feedback timing for reporting a first downlink data transmission. The operation of 2610 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 2610 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0242] At 2615, the UE may manage flow control feedback for the first downlink data transmission based on the failure to receive the second DCI. The operation of 2615 may be performed according to the method described herein. In some non-limiting embodiments, the UE may manage the flow control feedback for the first downlink data transmission based on the failure to receive the second DCI. Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 2615.
[0243] Fig. 27 A flow chart illustrating a method 2700 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2700 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 2700 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0244] At 2705, the UE may receive a first DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The operation of 2705 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2705 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0245] At 2710, the UE may identify resources of an uplink control channel allocated for flow control feedback of SPS downlink data transmission. The operations of 2710 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 2710 may be described by reference to Figures 12 to 15 The PUCCH manager is used to perform the above operations.
[0246] At 2715, the UE may multiplex the flow control feedback for downlink data transmission with the flow control feedback for SPS downlink data transmission in the resources of the uplink control channel. The operation of 2715 may be performed according to the method described herein. In some non-limiting embodiments, the UE may multiplex the flow control feedback for downlink data transmission with the flow control feedback for SPS downlink data transmission in the resources of the uplink control channel. Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 2715.
[0247] Fig.28 A flow chart illustrating a method 2800 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2800 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 2800 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0248] At 2805, the UE may receive from a base station a first DCI for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing. The operation of 2805 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operation of 2805 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0249] At 2810, the UE may receive from the base station a second DCI for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating the timing of the first digital data to the flow control feedback. The operation of 2810 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 2810 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0250] At 2815, the UE may report flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing. The operation of 2815 may be performed according to the method described herein. In some non-limiting embodiments, the UE may report the flow control feedback for the first downlink data transmission and the flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing. Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 2815.
[0251] Fig.29 A flow chart illustrating a method 2900 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 2900 may be implemented by the base station 105 or components thereof, as described herein. According to some aspects, the operations of the method 2900 may be implemented by the base station 105 or components thereof, as described herein. Figure 16 to Figure 19 The communication manager described herein performs. In some aspects, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.
[0252] At 2905, the base station may send a first DCI to the UE for scheduling a first downlink data transmission in a first downlink data transmission group, the first DCI indicating non-digital data to flow control feedback timing. The operation of 2905 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 2905 may be referred to as Figures 16 to 19The DCI manager is used to perform the above operations.
[0253] At 2910, the base station may send a second DCI to the UE for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group, the second DCI indicating the first digital data to the flow control feedback timing. The operation of 2910 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 2910 may be referred to as Figures 16 to 19 The DCI manager is used to perform the above operations.
[0254] At 2915, the base station may receive flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing. The operation of 2915 may be performed according to the method described herein. In some non-limiting embodiments, the flow control feedback may be performed as described in reference to Figure 16 to Figure 19 The flow control feedback manager is used to perform aspects of the operation of 2915.
[0255] Fig.30 A flow chart illustrating a method 3000 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 3000 may be implemented by the UE 115 or components thereof as described herein. According to some aspects, the operations of the method 3000 may be implemented by the UE 115 or components thereof as described herein. Figure 12 to Figure 15 The communication manager described herein performs. In some aspects, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0256] At 3005, the UE may receive DCI from a base station that schedules downlink data transmission with non-digital data to flow control feedback timing. The operation of 3005 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 3005 may be referred to as Figures 12 to 15 The DCI manager is used to perform the above operations.
[0257] At 3010, the UE may identify one or more uplink control channels allocated within a time window for reporting flow control feedback for downlink data transmission. The operations of 3010 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 3010 may be described with reference to Figures 12 to 15 The PUCCH manager is used to perform the above operations.
[0258] At 3015, the UE may multiplex flow control feedback for downlink data transmission in one or more uplink control channels allocated within the time window. The operation of 3015 may be performed according to the method described herein. In some non-limiting embodiments, the UE may multiplex flow control feedback for downlink data transmission in one or more uplink control channels allocated within the time window. Figure 12 to Figure 15 The flow control feedback manager is used to perform aspects of the operation of 3015.
[0259] Fig.31 A flow chart illustrating a method 3100 for supporting processing of non-digital data to flow control feedback timing according to aspects of the present disclosure is shown. The operations of the method 3100 may be implemented by the base station 105 or components thereof, as described herein. According to some aspects, the operations of the method 3100 may be implemented by the base station 105 or components thereof, as described herein. Figure 16 to Figure 19 The communication manager described herein performs. In some aspects, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.
[0260] At 3105, the base station may send a DCI to the UE that schedules downlink data transmission with non-digital data to flow control feedback timing. The operation of 3105 may be performed according to the method described herein. In some non-limiting embodiments, aspects of the operation of 3105 may be referred to as Figures 16 to 19 The DCI manager is used to perform the above operations.
[0261] At 3110, the base station may identify one or more uplink control channels allocated within the time window for UE to report flow control feedback for downlink data transmission. The operations of 3110 may be performed according to the methods described herein. In some non-limiting embodiments, aspects of the operations of 3110 may be described with reference to Figures 16 to 19 The PUCCH manager is used to perform the above operations.
[0262] At 3115, the base station may monitor the flow control feedback of the downlink data transmission in one or more uplink control channels allocated within the time window. The operation of 3115 may be performed according to the method described herein. In some non-limiting embodiments, the flow control feedback of the downlink data transmission may be performed as described in reference to Figure 16 to Figure 19 The flow control feedback manager is used to perform aspects of the operation of 3115.
[0263] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0264] The following provides an overview of aspects of the present disclosure:
[0265] Aspect 1: A method for wireless communication implemented by a UE, comprising: receiving first downlink control information scheduling a first downlink data transmission from a base station, the first downlink control information indicating non-digital data to flow control feedback timing; receiving second downlink control information scheduling a second downlink data transmission from the base station, the second downlink control information indicating digital data to flow control feedback timing; identifying resources of a first uplink channel allocated to flow control feedback for semi-persistently scheduled downlink data transmission; and managing flow control feedback for the first downlink data transmission based at least in part on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0266] Aspect 2: A method according to Aspect 1, wherein managing flow control feedback for a first downlink data transmission includes: at least partially based on a second uplink channel occurring simultaneously with or before the first uplink channel, multiplexing the flow control feedback for the first downlink data transmission with the flow control feedback for the second downlink data transmission in the resources of the second uplink channel.
[0267] Aspect 3: The method according to aspect 2, wherein the time between the first downlink data transmission and the second uplink channel is greater than or equal to the duration configured for processing the first downlink data transmission.
[0268] Aspect 4: A method according to any one of Aspects 1 to 3, wherein managing flow control feedback for a first downlink data transmission includes: determining not to multiplex the flow control feedback for the first downlink data transmission with the flow control feedback for the second downlink data transmission in the resources of the second uplink channel based at least in part on a second uplink channel occurring after the first uplink channel.
[0269] Aspect 5: A method according to any one of Aspects 1 to 4, wherein managing flow control feedback for a first downlink data transmission comprises discarding flow control feedback for the first downlink data transmission based at least in part on a second uplink channel occurring after the first uplink channel.
[0270] Aspect 6: The method according to aspect 5 further comprises: reporting a negative acknowledgement of the first downlink data transmission in an uplink channel different from the second uplink channel based at least in part on the flow control feedback that the first downlink data transmission was discarded.
[0271] Aspect 7: The method according to any one of aspects 1 to 6, wherein the second downlink control information is received in a downlink control channel monitoring opportunity after the first downlink control information.
[0272] Aspect 8: The method according to any one of aspects 1 to 7 further comprises: receiving a first downlink data transmission before the second downlink data transmission.
[0273] Aspect 9: The method according to any one of aspects 1 to 8, further comprising: receiving a first downlink data transmission before the semi-persistently scheduled downlink data transmission.
[0274] Aspect 10: The method according to any one of aspects 1 to 9 further includes: receiving, from a base station, third downlink control information for activating semi-persistently scheduled downlink data transmission including the semi-persistently scheduled downlink data transmission.
[0275] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: receiving a control message indicating that a non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timings for downlink data transmission from the base station to the UE.
[0276] Aspect 12: The method according to aspect 11, wherein the control message is an RRC message including a set of data-to-flow control feedback timing.
[0277] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the second downlink control information indicates a downlink allocation index associated with a downlink data transmission group, which is the same as the downlink data transmission group indicated by the first downlink control information; and managing the flow control feedback of the first downlink data transmission includes multiplexing the flow control feedback of the first downlink data transmission with the flow control feedback of the second downlink data transmission in the resources of the second uplink channel based at least in part on the downlink allocation index associated with the downlink data transmission group that is the same as the downlink data transmission group indicated by the first downlink control information.
[0278] Aspect 14: A method according to any one of Aspects 1 to 13, wherein managing flow control feedback for a first downlink data transmission includes: determining not to multiplex flow control feedback for the first downlink data transmission in a second uplink channel based at least in part on a second uplink channel occurring within a duration configured for processing the first downlink data transmission.
[0279] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the flow control feedback for managing a first downlink data transmission includes: multiplexing the flow control feedback for the first downlink data transmission with the flow control feedback for semi-persistently scheduled downlink data transmission in the resources of the first uplink channel based at least in part on a second uplink channel occurring after the first uplink channel.
[0280] Aspect 16: The method according to any one of aspects 1 to 15, further comprising: receiving a first downlink data transmission and a second downlink data transmission in the first component carrier.
[0281] Aspect 17: The method according to any one of aspects 1 to 16 further comprises: receiving a first downlink data transmission in a first component carrier; and receiving a second downlink data transmission in a second component carrier different from the first component carrier.
[0282] Aspect 18: The method according to any one of aspects 1 to 17 further comprises: receiving a configuration for a flow control feedback codebook, and wherein the flow control feedback for managing the first downlink data transmission is based at least in part on the configuration for the flow control feedback codebook.
[0283] Aspect 19: The method according to Aspect 18, wherein the flow control feedback codebook comprises an enhanced dynamic flow control feedback codebook.
[0284] Aspect 20: The method according to any one of aspects 1 to 19, wherein the first uplink channel comprises an uplink control channel, and the second uplink channel comprises an uplink control channel or an uplink shared channel.
[0285] Aspect 21: A method for wireless communication implemented by a base station, comprising: sending first downlink control information for scheduling a first downlink data transmission to a UE, the first downlink control information indicating non-digital data to flow control feedback timing; sending second downlink control information for scheduling a second downlink data transmission to the UE, the second downlink control information indicating digital data to flow control feedback timing; sending third downlink control information to the UE, the third downlink control information activating semi-persistently scheduled downlink data transmission from the base station and indicating resources of a first uplink channel for flow control feedback of semi-persistently scheduled downlink data transmissions of multiple semi-persistently scheduled downlink data transmissions; and receiving flow control feedback for the first downlink data transmission based at least in part on the second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel.
[0286] Aspect 22: The method according to Aspect 21, wherein the second downlink control information is sent in a downlink control channel monitoring opportunity after the first downlink control information.
[0287] Aspect 23: The method according to any one of Aspects 21 to 22 further includes: sending a control message to the UE, the control message indicating that non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timings for downlink data transmission from the base station to the UE.
[0288] Aspect 24: The method according to any one of aspects 21 to 23 further comprises: sending a configuration for a flow control feedback codebook to the UE, and wherein the flow control feedback for managing the first downlink data transmission is at least partially based on the configuration for the flow control feedback codebook.
[0289] Aspect 25: A method for wireless communication implemented by a UE, comprising: receiving a first downlink data transmission scheduled by first downlink control information from a base station, the first downlink control information indicating non-digital data to flow control feedback timing for the first downlink data transmission; receiving a second downlink data transmission from the base station, wherein the corresponding timing of the flow control feedback for the first downlink data transmission and the second downlink data transmission is out of order relative to the corresponding timing of receiving the first downlink data transmission and the second downlink data transmission; and reporting the flow control feedback of the first downlink data transmission to the base station at least in part based on the second downlink data transmission being a semi-persistently scheduled downlink data transmission.
[0290] Aspect 26: The method according to Aspect 25, wherein the first downlink data transmission is received before the second downlink data transmission.
[0291] Aspect 27: The method according to any one of aspects 25 to 26, wherein the second downlink data transmission is received before the first downlink data transmission.
[0292] Aspect 28: A method for wireless communication at a base station, comprising: sending a first downlink data transmission scheduled by first downlink control information to a UE, the first downlink control information indicating non-digital data to flow control feedback timing for the first downlink data transmission; sending a second downlink data transmission to the UE, wherein the corresponding timing of flow control feedback for the first downlink data transmission and the second downlink data transmission is out of order relative to the corresponding timing of sending the first downlink data transmission and the second downlink data transmission; and receiving flow control feedback for the first downlink data transmission from the UE at least in part based on the second downlink data transmission being a semi-persistently scheduled downlink data transmission.
[0293] Aspect 29: The method according to aspect 28, wherein the first downlink data transmission is sent before the second downlink data transmission.
[0294] Aspect 30: The method according to any one of aspects 28 to 29, wherein the second downlink data transmission is sent before the first downlink data transmission.
[0295] Aspect 31: A method for wireless communication implemented by a UE, comprising: receiving first downlink control information activating semi-persistently scheduled downlink data transmission from a base station; receiving second downlink control information indicating non-digital data for downlink data transmission to flow control feedback timing; and prohibiting reception of downlink data transmission based at least in part on the activated semi-persistently scheduled downlink data transmission.
[0296] Aspect 32: The method according to Aspect 31, wherein the prohibition of receiving the downlink data transmission is based at least in part on semi-persistently scheduling the downlink data transmission and the downlink data transmission in the same component carrier.
[0297] Aspect 33: A method for wireless communication at a base station, comprising: sending downlink control information to a UE to activate semi-persistent scheduling of downlink data transmission; and while activating the semi-persistent scheduling of downlink data transmission, prohibiting the use of non-digital data to flow control feedback timing scheduling of downlink data transmission.
[0298] Aspect 34: The method according to Aspect 33, wherein prohibiting scheduling downlink data transmission comprises: prohibiting scheduling downlink data transmission within the same component carrier as the activated semi-persistently scheduled downlink data transmission.
[0299] Aspect 35: A method for wireless communication implemented by a UE, comprising: receiving a control message indicating configuration of non-digital data-to-flow control feedback timing in a set of data-to-flow control feedback timing for downlink data transmission from a base station to the UE; receiving downlink control information to activate semi-persistently scheduled downlink data transmission to the UE; and prohibiting reception of semi-persistently scheduled downlink data transmission from the base station while configuring the non-digital data-to-flow control feedback timing.
[0300] Aspect 36: The method according to Aspect 35, wherein the control message is an RRC message including a set of data-to-flow control feedback timing.
[0301] Aspect 37: A method for wireless communication at a base station, comprising: sending a control message indicating that non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timing for downlink data transmission from the base station to a UE; and prohibiting activation of semi-persistent scheduling downlink data transmission to the UE while configuring the non-digital data-to-flow control feedback timing.
[0302] Aspect 38: The method according to Aspect 37, wherein the control message is an RRC message including a set of data-to-flow control feedback timing.
[0303] Aspect 39: A method for wireless communication implemented by a UE, comprising: receiving first downlink control information from a base station that schedules a first downlink data transmission with non-digital data to flow control feedback timing; determining that the UE has failed to receive second downlink control information indicating first digital data to flow control feedback timing for reporting flow control feedback for the first downlink data transmission; and managing flow control feedback for the first downlink data transmission based at least in part on the failure to receive the second downlink control information.
[0304] Aspect 40: A method according to Aspect 39, wherein determining that the UE fails to receive the second downlink control information includes: determining that the UE fails to receive the second downlink control information before a first uplink control channel, the first uplink control channel being after a duration configured to process a first downlink data transmission.
[0305] Aspect 41: The method according to Aspect 40 further comprises: multiplexing flow control feedback of the first downlink data transmission in the first uplink control channel.
[0306] Aspect 42: The method according to any one of aspects 40 to 41 further comprises: abandoning flow control feedback of a first downlink data transmission scheduled with non-digital data to flow control feedback timing based at least in part on failure to receive second downlink control information.
[0307] Aspect 43: The method according to Aspect 42 further includes: receiving third downlink control information indicating second digital data to flow control feedback timing, which is used to report flow control feedback of a second downlink data transmission in the same downlink data transmission group as the first downlink data transmission; and reporting a negative confirmation of the first downlink data transmission in an uplink control channel corresponding to the second digital data to flow control feedback timing based at least in part on discarding the flow control feedback of the first downlink data transmission.
[0308] Aspect 44: The method according to aspect 43, wherein reporting the negative acknowledgement of the first downlink data transmission is based at least in part on the NFI of the same downlink data transmission group that was not switched in the third downlink control information.
[0309] Aspect 45: The method according to any one of Aspects 40 to 44 further includes: receiving third downlink control information indicating a second digital data-to-flow control feedback timing for reporting flow control feedback for a first downlink data transmission; and prohibiting reporting flow control feedback for the first downlink data transmission in an uplink control channel corresponding to the second digital data-to-flow control feedback timing based at least in part on determining that the UE failed to receive the second downlink control information before a first uplink control channel, and the first uplink control channel is after a duration configured for processing the first downlink data transmission.
[0310] Aspect 46: A method for wireless communication implemented by a UE, comprising: receiving first downlink control information for scheduling downlink data transmission with non-digital data to flow control feedback timing from a base station; identifying resources of an uplink control channel allocated to flow control feedback for semi-persistently scheduled downlink data transmission; and multiplexing the flow control feedback for the downlink data transmission with the flow control feedback for the semi-persistently scheduled downlink data transmission in the resources of the uplink control channel.
[0311] Aspect 47: The method according to Aspect 46 also includes: failing to receive digital data indicating flow control feedback to trigger downlink data transmission prior to an uplink control channel to a second downlink control information of flow control feedback timing, wherein the multiplexing is at least partially based on failing to receive the second downlink control information.
[0312] Aspect 48: The method according to any one of Aspects 46 to 47 further includes: receiving semi-persistent scheduled downlink data transmission after first downlink control information for scheduling downlink data transmission, wherein the multiplexing is at least partially based on receiving the semi-persistent scheduled downlink data transmission after the first downlink control information.
[0313] Aspect 49: The method according to any one of Aspects 46 to 48 further includes: receiving a semi-persistently scheduled downlink data transmission after the downlink data transmission, wherein the multiplexing is at least partially based on receiving the semi-persistently scheduled downlink data transmission after the downlink data transmission.
[0314] Aspect 50: The method according to any one of aspects 46 to 49, wherein the time between downlink data transmission and the uplink control channel is greater than or equal to the minimum time for processing downlink data transmission at the UE.
[0315] Aspect 51: The method according to any one of aspects 46 to 50, wherein the downlink data transmission and the semi-persistently scheduled downlink data transmission are received in the same component carrier or in different component carriers.
[0316] Aspect 52: A method for wireless communication implemented by a UE, comprising: receiving first downlink control information for scheduling a first downlink data transmission in a first downlink data transmission group from a base station, the first downlink control information indicating non-digital data to flow control feedback timing; receiving second downlink control information for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group from the base station, the second downlink control information indicating first digital data to flow control feedback timing; and reporting flow control feedback of the first downlink data transmission and flow control feedback of the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0317] Aspect 53: The method according to aspect 52 also includes: determining the first downlink data transmission in the first downlink data transmission group and the second downlink data transmission group based at least in part on the first downlink control information indicating non-digital data to flow control feedback timing.
[0318] Aspect 54: The method according to Aspect 53 also includes: receiving third downlink control information for scheduling a third downlink data transmission in the first downlink data transmission group from a base station, the third downlink control information indicating a second digital data to flow control feedback timing; and reporting a negative confirmation of the first downlink data transmission in a second uplink control channel corresponding to the second digital data to flow control feedback timing based at least in part on the flow control feedback reporting the first downlink data transmission in the first uplink control channel.
[0319] Aspect 55: The method according to any one of Aspects 53 to 54 further includes: receiving a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation index associated with a second downlink data transmission group from a base station in a first downlink control information; generating flow control feedback of one or more downlink data transmissions in a first downlink data transmission group including the first downlink data transmission based at least in part on the first downlink allocation index; and generating flow control feedback of one or more downlink data transmissions in a second downlink data transmission group including the first downlink data transmission and the second downlink data transmission based at least in part on the second downlink allocation index.
[0320] Aspect 56: The method according to any one of Aspects 53 to 55, further comprising: receiving a maximum value of a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation associated with a second downlink data transmission group from a base station in a first downlink control information; generating flow control feedback of one or more downlink data transmissions in a first downlink data transmission group including the first downlink data transmission based at least in part on the maximum value of the first downlink allocation index and the second downlink allocation index; and generating flow control feedback of one or more downlink data transmissions in a second downlink data transmission group including the first downlink data transmission and the second downlink data transmission based at least in part on the maximum value of the first downlink allocation index and the second downlink allocation index.
[0321] Aspect 57: The method according to any one of aspects 52 to 56, further comprising: receiving the first downlink data transmission and the second downlink data transmission in the same component carrier.
[0322] Aspect 58: A method for performing wireless communications at a base station, comprising: sending first downlink control information for scheduling a first downlink data transmission in a first downlink data transmission group to a UE, the first downlink control information indicating non-digital data to flow control feedback timing; sending second downlink control information for scheduling a second downlink data transmission in a second downlink data transmission group different from the first downlink data transmission group to the UE, the second downlink control information indicating first digital data to flow control feedback timing; and receiving flow control feedback for the first downlink data transmission and flow control feedback for the second downlink data transmission in a first uplink control channel corresponding to the first digital data to flow control feedback timing.
[0323] Aspect 59: The method according to Aspect 58 further includes: determining a first downlink data transmission in the first downlink data transmission group and the second downlink data transmission group based at least in part on first downlink control information indicating non-digital data to flow control feedback timing.
[0324] Aspect 60: The method according to Aspect 59 also includes: sending third downlink control information for scheduling a third downlink data transmission in the first downlink data transmission group to the UE, the third downlink control information indicating a second digital data to flow control feedback timing; and receiving a negative confirmation of the first downlink data transmission in a second uplink control channel corresponding to the second digital data to flow control feedback timing based at least in part on receiving the flow control feedback of the first downlink data transmission in the first uplink control channel.
[0325] Aspect 61: The method according to any one of Aspects 59 to 60 further includes: increasing a first downlink allocation index associated with a first downlink data transmission group and a second downlink allocation index associated with a second downlink data transmission group based at least in part on indicating non-digital data to flow control feedback timing in the first downlink control information.
[0326] Aspect 62: The method according to Aspect 61 further includes: sending the first downlink allocation index and the second downlink allocation index to the UE in the first downlink control information.
[0327] Aspect 63: The method according to any one of aspects 61 to 62 further includes: sending a maximum value of the first downlink allocation index and the second downlink allocation index to the UE in the first downlink control information.
[0328] Aspect 64: The method according to any one of aspects 58 to 63, further comprising: sending the first downlink data transmission and the second downlink data transmission in the same component carrier.
[0329] Aspect 65: A method for wireless communication implemented by a UE, comprising: receiving downlink control information for scheduling downlink data transmission with non-digital data to flow control feedback timing from a base station; identifying one or more uplink control channels allocated within a time window for reporting flow control feedback for downlink data transmission; and multiplexing the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window.
[0330] Aspect 66: The method according to Aspect 65 further includes: receiving a control message indicating a time window for reporting flow control feedback from a base station.
[0331] Aspect 67: The method according to any one of aspects 65 to 66, wherein the time window for reporting flow control feedback is after a time duration configured for processing downlink data transmission.
[0332] Aspect 68: A method according to any one of Aspects 65 to 67, wherein flow control feedback for downlink data transmission is multiplexed in one or more uplink control channels allocated within a time window, comprises: flow control feedback for downlink data transmission is multiplexed in multiple uplink control channels allocated within a time window.
[0333] Aspect 69: A method for wireless communication at a base station, comprising: sending downlink control information to a UE for scheduling downlink data transmission with non-digital data to flow control feedback timing; identifying one or more uplink control channels allocated within a time window for the UE to report flow control feedback for downlink data transmission; and monitoring the flow control feedback for downlink data transmission in the one or more uplink control channels allocated within the time window.
[0334] Aspect 70: The method according to Aspect 69 further includes: sending a control message indicating a time window for reporting flow control feedback to the UE.
[0335] Aspect 71: A method according to any one of aspects 69 to 70, wherein the time window for reporting flow control feedback is after a duration configured for the UE to process downlink data transmission.
[0336] Aspect 72: A method according to any one of Aspects 69 to 71, wherein monitoring flow control feedback of downlink data transmission in one or more uplink control channels allocated within a time window includes: monitoring flow control feedback of downlink data transmission in multiple uplink control channels allocated within a time window.
[0337] Aspect 73: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 1 to 20.
[0338] Aspect 74: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 1 to 20.
[0339] Aspect 75: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 20.
[0340] Aspect 76: An apparatus for wireless communication implemented by a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 21 to 24.
[0341] Aspect 77: An apparatus for wireless communication implemented by a base station, comprising at least one component for performing the method of any one of aspects 21 to 24.
[0342] Aspect 78: A non-transitory computer-readable medium storing code implemented by a base station for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 21 to 24.
[0343] Aspect 79: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 25 to 27.
[0344] Aspect 80: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 25 to 27.
[0345] Aspect 81: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 25 to 27.
[0346] Aspect 82: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 28 to 30.
[0347] Aspect 83: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of aspects 28 to 30.
[0348] Aspect 84: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of Aspects 28 to 30.
[0349] Aspect 85: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 31 to 32.
[0350] Aspect 86: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 31 to 32.
[0351] Aspect 87: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 31 to 32.
[0352] Aspect 88: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 33 to 34.
[0353] Aspect 89: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of Aspects 33 to 34.
[0354] Aspect 90: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any one of aspects 33 to 34.
[0355] Aspect 91: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 35 to 36.
[0356] Aspect 92: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 35 to 36.
[0357] Aspect 93: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 35 to 36.
[0358] Aspect 94: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 37 to 38.
[0359] Aspect 95: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of aspects 37 to 38.
[0360] Aspect 96: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of aspects 37 to 38.
[0361] Aspect 97: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 39 to 45.
[0362] Aspect 98: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 39 to 45.
[0363] Aspect 99: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 39 to 45.
[0364] Aspect 100: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 46 to 51.
[0365] Aspect 101: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 46 to 51.
[0366] Aspect 102: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 46 to 51.
[0367] Aspect 103: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 52 to 57.
[0368] Aspect 104: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 52 to 57.
[0369] Aspect 105: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 52 to 57.
[0370] Aspect 106: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 58 to 64.
[0371] Aspect 107: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of Aspects 58 to 64.
[0372] Aspect 108: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of aspects 58 to 64.
[0373] Aspect 109: An apparatus for wireless communication implemented by a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 65 to 68.
[0374] Aspect 110: An apparatus for wireless communication implemented by a UE, comprising at least one component for performing the method of any one of aspects 65 to 68.
[0375] Aspect 111: A non-transitory computer-readable medium storing a code implemented by a UE for wireless communication, the code comprising instructions executable by a processor to perform the method of any one of aspects 65 to 68.
[0376] Aspect 112: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 69 to 72.
[0377] Aspect 113: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of aspects 69 to 72.
[0378] Aspect 114: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of aspects 69 to 72.
[0379] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. According to some aspects, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0380] The information and signals described herein may be represented using any of a variety of different technologies and techniques. That is, data, instructions, commands, information, signals, bits, cycles, and chips that may be referenced throughout the specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0381] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.
[0382] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Other aspects and embodiments are within the scope of the present disclosure and the appended claims. According to some aspects, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.
[0383] Computer readable medium includes both non-transitory computer storage medium and communication medium, and computer storage medium and communication medium include any medium that helps to transfer computer program from one place to another place.Non-transitory storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transitory computer readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device or can be used to carry or store required program code mode in the form of instruction or data structure and can be accessed by general or special-purpose computer, or any other non-transitory medium of general or special-purpose processor.In addition, any connection is appropriately referred to as computer readable medium.According to some aspects, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology (such as infrared, radio and microwave) are included in the definition of computer readable medium. Disk and disc, as used herein, includes CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks and Blu-ray discs, where disks usually reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0384] As used herein, including in the claims, "or", as used in a list of items (e.g., a list of items preceded by a phrase such as "at least one" or "one or more"), indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. That is, a non-limiting implementation of an operation or step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".
[0385] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, without regard to the second reference label or other subsequent reference labels.
[0386] The descriptions set forth herein in conjunction with the accompanying drawings describe non-limiting embodiments and configurations and do not represent all aspects that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques may be practiced without these specific details. In some cases, in order to avoid confusing the described aspects and concepts of the non-limiting embodiments, known structures and devices are shown in block diagram form.
[0387] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the aspects and designs described herein, but conforms to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication implemented by a user equipment UE, comprising: receiving, from a network device, first downlink control information scheduling a first downlink data transmission, the first downlink control information indicating a non-digital data-to-flow control feedback timing, wherein the non-digital data-to-flow control feedback timing is associated with a non-digital K1 value; receiving, from the network device, second downlink control information scheduling a second downlink data transmission, the second downlink control information indicating a digital data-to-flow control feedback timing, wherein the digital data-to-flow control feedback timing is associated with a digital K1 value; identifying resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission; as well as managing flow control feedback for the first downlink data transmission based at least in part on a second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel, The flow control feedback for managing the first downlink data transmission includes: multiplexing the flow control feedback for the first downlink data transmission with flow control feedback for the second downlink data transmission in resources of the second uplink channel based at least in part on the second uplink channel occurring simultaneously with or before the first uplink channel, and Based at least in part on the second uplink channel occurring after the first uplink channel, it is determined not to multiplex the flow control feedback for the first downlink data transmission with flow control feedback for the second downlink data transmission in resources of the second uplink channel.
2. The method according to claim 1, wherein: A time between the first downlink data transmission and the second uplink channel is greater than or equal to a duration configured for processing the first downlink data transmission.
3. The method according to claim 1, wherein: The second downlink control information is received in a downlink control channel monitoring opportunity after the first downlink control information.
4. The method according to claim 1, further comprising: The first downlink data transmission is received prior to the second downlink data transmission.
5. The method according to claim 1, further comprising: The first downlink data transmission is received prior to the semi-persistently scheduled downlink data transmission.
6. The method according to claim 1, further comprising: Third downlink control information is received, the third downlink control information activating a plurality of semi-persistently scheduled downlink data transmissions including the semi-persistently scheduled downlink data transmission from the network device.
7. The method according to claim 1, further comprising: A control message is received, the control message indicating that the non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timings for downlink data transmission from the network device to the UE.
8. The method according to claim 7, wherein: The control message is a radio resource control RRC message including a set of data-to-flow control feedback timings.
9. The method according to claim 1, wherein: the second downlink control information indicates a downlink allocation index associated with a downlink data transmission group, the downlink data transmission group being the same as the downlink data transmission group indicated by the first downlink control information; and Managing the flow control feedback for the first downlink data transmission includes multiplexing the flow control feedback for the first downlink data transmission with the flow control feedback for the second downlink data transmission in the resources of the second uplink channel based at least in part on the downlink allocation index associated with the downlink data transmission group that is the same as the downlink data transmission group indicated by the first downlink control information.
10. The method according to claim 1, wherein: Managing the flow control feedback of the first downlink data transmission comprises: The flow control feedback to not multiplex the first downlink data transmission in the second uplink channel is determined based at least in part on the second uplink channel occurring within a time duration configured for processing the first downlink data transmission.
11. The method according to claim 1, further comprising: The first downlink data transmission and the second downlink data transmission are received in a first component carrier.
12. The method according to claim 1, further comprising: receiving the first downlink data transmission in a first component carrier; as well as The second downlink data transmission is received in a second component carrier different from the first component carrier.
13. The method according to claim 1, further comprising: A configuration for a flow control feedback codebook is received, and wherein the flow control feedback governing the first downlink data transmission is based at least in part on the configuration for the flow control feedback codebook.
14. The method according to claim 13, wherein: The flow control feedback codebook includes an enhanced dynamic flow control feedback codebook.
15. The method according to claim 1, wherein: The first uplink channel comprises an uplink control channel, and the second uplink channel comprises an uplink control channel or an uplink shared channel.
16. A method for wireless communication implemented by a network device, comprising: sending first downlink control information scheduling first downlink data transmission to a user equipment UE, the first downlink control information indicating non-digital data to flow control feedback timing, wherein the non-digital data to flow control feedback timing is associated with a non-digital K1 value; sending second downlink control information scheduling a second downlink data transmission to the UE, the second downlink control information indicating a digital data-to-flow control feedback timing, wherein the digital data-to-flow control feedback timing is associated with a digital K1 value; sending third downlink control information to the UE, the third downlink control information activating a plurality of semi-persistently scheduled downlink data transmissions from the network device and indicating resources of a first uplink channel for flow control feedback allocated to a semi-persistently scheduled downlink data transmission among the plurality of semi-persistently scheduled downlink data transmissions; as well as receiving flow control feedback for the first downlink data transmission based at least in part on a second uplink channel and the first uplink channel corresponding to the digital data to flow control feedback timing, Wherein, if the second uplink channel occurs simultaneously with or before the first uplink channel, the flow control feedback of the first downlink data transmission is multiplexed, and if the second uplink channel occurs after the first uplink channel, the flow control feedback of the first downlink data transmission is not multiplexed.
17. The method according to claim 16, wherein: The second downlink control information is transmitted in a downlink control channel monitoring opportunity subsequent to the first downlink control information.
18. The method according to claim 16, further comprising: A control message is sent to the UE, the control message indicating that the non-digital data-to-flow control feedback timing is configured in a set of data-to-flow control feedback timings for downlink data transmission from the network device to the UE.
19. The method according to claim 16, further comprising: A configuration for a flow control feedback codebook is sent to the UE, and wherein the flow control feedback governing the first downlink data transmission is based at least in part on the configuration for the flow control feedback codebook.
20. An apparatus for wireless communication implemented by a user equipment UE, comprising: means for receiving, from a network device, first downlink control information scheduling a first downlink data transmission, the first downlink control information indicating a non-digital data-to-flow control feedback timing, wherein the non-digital data-to-flow control feedback timing is associated with a non-digital K1 value; means for receiving, from the network device, second downlink control information scheduling a second downlink data transmission, the second downlink control information indicating a digital data-to-flow control feedback timing, wherein the digital data-to-flow control feedback timing is associated with a digital K1 value; means for identifying resources of a first uplink channel allocated for flow control feedback for semi-persistently scheduled downlink data transmission; as well as means for managing flow control feedback for the first downlink data transmission based at least in part on a second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel, The means for managing flow control feedback of the first downlink data transmission comprises: means for multiplexing the flow control feedback for the first downlink data transmission with the flow control feedback for the second downlink data transmission in resources of the second uplink channel based at least in part on the second uplink channel occurring simultaneously with or before the first uplink channel, and Means for determining not to multiplex the flow control feedback for the first downlink data transmission with flow control feedback for the second downlink data transmission in resources of the second uplink channel based at least in part on the second uplink channel occurring after the first uplink channel.
21. An apparatus for wireless communication implemented by a network device, comprising: means for sending first downlink control information scheduling a first downlink data transmission to a user equipment UE, the first downlink control information indicating a non-digital data-to-flow control feedback timing, wherein the non-digital data-to-flow control feedback timing is associated with a non-digital K1 value; means for sending second downlink control information scheduling a second downlink data transmission to the UE, the second downlink control information indicating a digital data-to-flow control feedback timing, wherein the digital data-to-flow control feedback timing is associated with a digital K1 value; a means for sending third downlink control information to the UE, the third downlink control information activating a plurality of semi-persistently scheduled downlink data transmissions from the network device and indicating resources of a first uplink channel for flow control feedback allocated to a semi-persistently scheduled downlink data transmission among the plurality of semi-persistently scheduled downlink data transmissions; and means for receiving flow control feedback for the first downlink data transmission based at least in part on a second uplink channel corresponding to the digital data to flow control feedback timing and the first uplink channel, Wherein, if the second uplink channel occurs simultaneously with or before the first uplink channel, the flow control feedback of the first downlink data transmission is multiplexed, and if the second uplink channel occurs after the first uplink channel, the flow control feedback of the first downlink data transmission is not multiplexed.
22. The device according to claim 21, wherein The means for sending the second downlink control information scheduling the second downlink data transmission comprises: A means for transmitting the second downlink control information in a downlink control channel monitoring opportunity after transmitting the first downlink control information.
23. A computer readable medium having stored thereon instructions which, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 15.
24. A computer readable medium having stored thereon instructions which, when executed by a computer, cause the computer to perform the method according to any one of claims 16 to 19.