How to apply dynamic codebooks for HARQ-ACK feedback and devices

Abstract

The present disclosure describes a method, system, and device for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. One method includes transmitting, by a wireless communication device, HARQ-ACK based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a timing advance group (TAG). Another method includes receiving, by a wireless communication node, from a wireless communication device, HARQ-ACK based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a TAG.

Description

Technical Field

[0002] , , , , ,

[0004] , , , , ,

[0003] ,

[0001] The present disclosure generally relates to wireless communication. Specifically, the present disclosure relates to methods and devices for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

Background Art

[0005] This book relates to methods, systems, and devices for wireless communication, and more specifically, to methods, systems, and devices for applying dynamic codebooks for hybrid automatic retransmission request acknowledgment (HARQ-ACK) feedback. Various embodiments within this disclosure may be useful for improving the application of dynamic codebooks for HARQ-ACK feedback in order to increase resource utilization efficiency and enhance the latency performance of wireless communication.

[0006] In one embodiment, the disclosure describes a method for wireless communication. The method involves a wireless communication device transmitting a Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a Timing Advance Group (TAG).

[0007] In one embodiment, the disclosure describes a method for wireless communication. The method includes a wireless communication node receiving a hybrid automatic retransmission request acknowledgment (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks from a wireless communication device, where each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

[0008] In some other embodiments, the device for wireless communication may include a memory for storing instructions and a processing network for communicating with the memory. When the processing network executes an instruction, the processing network is configured to perform the method described above.

[0009] In some other embodiments, a device for wireless communication may include a memory for storing instructions and a processing network for communicating with the memory. When the processing network executes an instruction, the processing network is configured to perform the above-described method.

[0010] In some other embodiments, the computer-readable medium comprises instructions that, when executed by a computer, cause the computer to perform the above method.

[0011] The above and other aspects and their implementations are described in more detail in the drawings, the description, and the claims. The present invention further provides, for example, the following: (Item 1) A method for wireless communication, wherein the method is This includes transmitting a Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks by a wireless communication device. Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG). (Item 2) The method described in item 1, wherein each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook. (Item 3) For a dynamic HARQ-ACK codebook that corresponds to a TAG, The Counter Downlink Assignment Index (cDAI) field included in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to the TAG. The method according to either of items 1-2, wherein the total downlink assignment index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG. (Item 4) The method described in any of items 1-3, wherein the TAG index field included in the DCI indicates a TAG, and the TAG corresponds to a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH). (Item 5) The wireless communication device further includes receiving configuration information, The aforementioned configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG. The dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG, as described in item 1. (Item 6) The dynamic HARQ-ACK codebook information included in DCI is the method described in any of items 1-3, which indicates the dynamic HARQ-ACK codebook for the scheduled physical downlink shared channel (PDSCH). (Item 7) A method for wireless communication, wherein the method is The wireless communication node includes receiving a hybrid automatic retransmission request acknowledgment (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks from a wireless communication device. Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG). (Item 8) The method described in item 7, in which each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook. (Item 9) For a dynamic HARQ-ACK codebook that corresponds to a TAG, The Counter Downlink Assignment Index (cDAI) field included in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to the TAG. The method according to any one of items 7-8, wherein the total downlink assignment index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG. (Item 10) The method described in item 7-9, wherein the TAG index field included in the DCI indicates a TAG, the TAG corresponding to a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH). (Item 11) The wireless communication node further includes transmitting configuration information, The aforementioned configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG. The dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG, as described in any of item 7. (Item 12) The dynamic HARQ-ACK codebook information included in DCI is described in item 7-9, indicating the dynamic HARQ-ACK codebook for scheduled physical downlink shared channels (PDSCHs). (Item 13) A wireless communication device comprising a processor and memory, wherein the processor is configured to read code from the memory and to perform the method described in any of items 1-12. (Item 14) A computer program product comprising stored computer-readable program media code, wherein the computer-readable program media code, when executed by a processor, causes the processor to perform any of the methods described in items 1-12. [Brief explanation of the drawing]

[0012] [Figure 1A] Figure 1A shows an example of a wireless communication system that includes one wireless network node and one or more user devices.

[0013] [Figure 1B] Figure 1B shows schematic diagrams of various embodiments of this disclosure.

[0014] [Figure 1C] Figure 1C shows another schematic diagram of various embodiments of this disclosure.

[0015] [Figure 2] Figure 2 shows an example of a network node.

[0016] [Figure 3] Figure 3 shows an example of a user device.

[0017] [Figure 4A] Figure 4A shows a flowchart of the method for wireless communication.

[0018] [Figure 4B] Figure 4B shows a flowchart of another method for wireless communication.

[0019] [Figure 5] Figure 5 shows a flowchart of a non-limiting embodiment for wireless communication.

[0020] [Figure 6] Figure 6 shows a flowchart of a non-limiting embodiment for wireless communication.

[0021] [Figure 7] Figure 7 shows a flowchart of a non-limiting embodiment for wireless communication.

[0022] [Figure 8] Figure 8 shows a flowchart of a non-limiting embodiment for wireless communication. [Modes for carrying out the invention]

[0023] This disclosure will be described in detail hereafter with reference to accompanying drawings that form part of this disclosure and illustrate specific examples of embodiments. However, it should be noted that this disclosure may be embodied in a variety of different forms and is therefore intended to be construed as not being limited to any of the embodiments described below.

[0024] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their explicitly stated meanings. Similarly, phrases such as “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and phrases such as “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. Phrases such as “in one implementation” or “in some implementations” as used herein do not necessarily refer to the same implementation, and phrases such as “in another implementation” or “in other implementations” as used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include exemplary embodiments or combinations of implementations, whether in whole or in part.

[0025] In general, technical terms can be understood, at least partially, from their use in context. For example, terms such as “and,” “or,” or “and / or,” as used herein, may have various meanings that depend, at least partially, on the context in which such terms are used. Typically, when “or” is used to relate a list such as “A, B, or C,” it is intended to mean both “A, B, and C,” used here in an inclusive sense, and “A, B, or C,” used here in an exclusive sense. In addition, terms such as “one or more” or “at least one,” as used herein, may be used, at least partially contextually, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, again, terms such as "a," "an," or "the" can be understood, at least partially depending on the context, to convey singular or plural use. In addition, the terms "based on" or "determined by" can be understood not necessarily as intended to convey an exclusive set of factors, but rather, again, at least partially depending on the context, to allow for the presence of additional factors that are not necessarily explicitly stated.

[0026] This disclosure describes methods and devices for applying dynamic codebooks for Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) feedback. In various embodiments, applying dynamic codebooks for HARQ-ACK feedback may include applying and / or using TAG-specific dynamic codebooks for HARQ-ACK feedback.

[0027] Next-generation (NG) or fifth-generation (5G) wireless communication can offer capabilities ranging from high-speed downloads to supporting real-time, low-latency communication. New generation (NG) mobile communication systems are driving the world towards an increasingly connected and networked society. High-speed, low-latency wireless communication relies on efficient management and allocation of network resources between user equipment and wireless access network nodes (including, but not limited to, wireless base stations).

[0028] Carrier aggregation (CA) is a critical technique for multi-frequency convergence in cellular mobile communication systems (e.g., 4G or 5G). CA includes intra-TAG (intra-TAG) carrier aggregation and cross-TAG carrier aggregation. When using dynamic codebooks for downlink HARQ ACK / NACK, the UE may need to be notified of the Counter Downlink Allocation Index (DAI) and Total DAI for this scheduling through Downlink Control Information (DCI). In some implementations, the Total DAI may require scheduling information for all carriers, including primary cells (Pcells) and all secondary cells (Scells). This requires that DCI for one carrier needs to obtain scheduling information for other carriers, and that the exchange of scheduling information between different carriers may take a certain amount of time, which may be known as the delay for the exchange of scheduling information. With respect to cross-TAG CA, the delay in the exchange of scheduling information between carriers in different TAGs can usually be larger, which can seriously affect scheduling timing and even cause scheduling failures.

[0029] This disclosure describes various embodiments for transmitting Hybrid Auto-Retransmission Request Acknowledgments (HARQ-ACKs) based on two or more dynamic HARQ-ACK codebooks, each corresponding to a Timing Advance Group (TAG) that addresses at least one of the challenges / problems associated with the current system.

[0030] Figure 1 shows a wireless communication system 100 including a core network (CN) 110, a radio access network (RAN) 130, and one or more user devices (UEs) (152, 154, and 156). The RAN 130 may include a radio network base station or an NG radio access network (NG-RAN) base station or node, which may include a nodeB (NB, e.g., gNB) in the context of mobile telecommunications. In one implementation, the core network 110 may include a 5G core network (5GC), and interface 125 may include a next-generation (NG) interface.

[0031] Referring to Figure 1A, the first UE 152 may wirelessly receive one or more downlink communications 142 from RAN 130 and wirelessly transmit one or more uplink communications 141 to RAN 130. Similarly, the second UE 154 may wirelessly receive downlink communications 144 from RAN 130 and wirelessly transmit uplink communications 143 to RAN 130, and the third UE 156 may wirelessly receive downlink communications 146 from RAN 130 and wirelessly transmit uplink communications 145 to RAN 130. For example, but not limited to, downlink communications may include a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and uplink communications may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH). One or more downlink communications (142, 144, and / or 146) and / or one or more uplink communications (141, 143, and / or 145) may be transmitted as one or more TAGs.

[0032] In some implementations, for example in new 5G radio (NR) implementations, carrier aggregation (CA) includes intra-TAG CA and inter-TAG CA. Intra-TAG CA refers to a CA where all carriers within it belong to the same TAG, while inter-TAG CA refers to a CA where the aggregated carriers within it belong to different TAGs.

[0033] In some other implementations, carriers belonging to the same TAG may share a single timing advance (TA). TA adjustment signal transmission, such as a TA medium access control (MAC) control element (CE) received by a UE on one carrier, may be multiplexed onto other carriers belonging to the same TAG.

[0034] In some other implementations, carriers deployed on the same nodeB (eNB or gNB) site are configured to belong to the same TAG. Carriers not deployed on the same nodeB site are configured to belong to different TAGs. Therefore, with respect to carrier aggregates deployed on the same nodeB site, it is generally considered an intra-TAG CA, and with respect to carrier aggregates deployed on different nodeB sites, it is generally considered an inter-TAG CA.

[0035] In some other implementations, the HARQ-ACK codebook refers to the entirety of HARQ information fed back by the UE at a single HARQ feedback resource (e.g., PUCCH or PUSCH). A timing parameter (e.g., K1) is one of the key parameters for determining the HARQ-ACK codebook. The timing parameter (e.g., K1) can be a time offset value between the PDSCH and the PUCCH or PUSCH for the HARQ-ACK feedback. One way to indicate the K1 parameter is that the network first configures the K1 value through the Radio Resource Control Information element (RRC IE), and then dynamically indicates the value in the K1 value, which is set through the HARQ feedback instruction field in the Downlink Control Information (DCI).

[0036] In some other implementations, the HARQ ACK / NACK codebook can be dynamic or semi-static. A dynamic HARQ ACK / NACK codebook refers to a codebook generation method in which the size of the HARQ ACK / NACK codebook can be dynamically determined based on the cross-carrier downlink allocation for CA. Dynamic codebook mechanisms for 5G New Radio (NR) and Long-Term Evolution (LTE) may be similar. The value of the counter DAI in DCI indicates the cumulative number of current PDSCHs. The statistical sequence of the cumulative number is as follows: first, in ascending order of serving cell index included in CA with respect to the codebook, and then in ascending order of PDSCH time domain opportunity. The value of the total DAI in DCI indicates the total number of PDSCHs related to CA to date.

[0037] One of the main problems with HARQ ACK / NACK feedback using dynamic codebooks is that, for inter-TAG CAs, the DCI for each carrier requires the DAI for other carriers to calculate the total DAI. The delay in exchanging scheduling information across carriers in different TAGs is usually very large, which can seriously affect scheduling timing and even cause scheduling failures.

[0038] The present invention describes various embodiments for applying dynamic codebooks for hybrid automatic retransmission request acknowledgment (HARQ-ACK) feedback. When a dynamic codebook is used for HARQ ACK / NACK feedback for inter-TAG CAs, the UE may use two or more dynamic codebooks simultaneously, each corresponding to one TAG. When the UE consists of multiple carriers (CAs, etc.) and these carriers belong to multiple different TAGs, the UE may use two or more dynamic codebooks to implement HARQ ACK / NACK feedback. Each dynamic codebook is used for a carrier belonging to one of the TAGs. With respect to inter-TAG CAs, one dynamic codebook is used for a carrier belonging to one of the TAGs, and another dynamic codebook is used for a carrier belonging to another TAG. When the UE simultaneously receives PDSCHs on carriers belonging to multiple TAGs for a CA, the UE may use multiple dynamic codebooks simultaneously for HARQ ACK / NACK feedback, each corresponding to one TAG.

[0039] Regarding a non-restrictive example, a CA situation between TAGs is shown in Figure 1B. There may be two or more dynamic codebooks used for HARQ-ACK feedback. Each dynamic codebook corresponds to a TAG, and each dynamic codebook is used for carriers belonging to one of the TAGs, e.g., dynamic codebook 1(171) for TAG1(176), and dynamic codebook 2(172) for another TAG(TAG2, 177). TAG1(176) may have one or more carriers, e.g., carrier 1(173) and carrier 2(174). TAG2(177) may have one or more carriers, e.g., carrier 3(177).

[0040] DCI on a carrier may need to determine the counter DAI and total DAI based on downlink assignments on other carriers within the same TAG. That is, one counter DAI and one total DAI correspond to one TAG. With respect to inter-TAG CAs, the UE may simultaneously receive counter DAI and total DAI for two or more dynamic codebooks, each dynamic codebook corresponding to one TAG.

[0041] For a non-restrictive example, the inter-TAG CA situation is shown in Figure 1C. There may be two or more dynamic codebooks used for HARQ-ACK feedback. The first carrier 181 and the second carrier 182 may belong to the first TAG (TAG1, 191), and the third carrier 183 and the fourth carrier 184 may belong to the second TAG (TAG2, 192). All four of these carriers are time-division duplex (TDD) carriers and may be in a downlink-uplink configuration with a pattern, where one period has four slots, the first slot being a downlink (D) slot, the second slot being a downlink (D) slot, the third slot being a special (S) slot, and the fourth slot being an uplink (U) slot. In a purely non-restrictive example, for the first carrier, the downlink allocation on the first slot using (counterDAI, totalDAI) is (1,2), and for the second carrier, the downlink allocation on the first slot using (counterDAI, totalDAI) is (2,2). In some implementations, (counterDAI, totalDAI) may be denoted as (cDAI, tDAI). In a purely non-restrictive example, for the first carrier, the downlink allocation on the second slot using (cDAI, tDAI) is (3,4), and for the second carrier, the downlink allocation on the second slot using (cDAI, tDAI) is (4,4). There may be a single dynamic codebook for the first and second carriers, both of which belong to TAG1.

[0042] There may be separate single dynamic codebooks for the third and fourth carriers, both belonging to TAG2. Simply as an unrestricted example, for the third carrier, the downlink assignment on the first slot using (cDAI, tDAI) is (1, 2), and for the fourth carrier, the downlink assignment on the first slot using (cDAI, tDAI) is (2, 2). For the third carrier, the downlink assignment on the second slot using (cDAI, tDAI) is (3, 4), and for the fourth carrier, the downlink assignment on the second slot using (cDAI, tDAI) is (4, 4).

[0043] This disclosure describes various embodiments for applying dynamic codebooks for Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) feedback.

[0044] Figure 2 shows an exemplary radio access network or radio communication base station 200. The base station 200 may include a radio transmission / reception (Tx / Rx) network 208 for transmitting / receiving communications with one or more UEs and / or one or more other base stations. The base station may include a network interface network 209 (e.g., optical or wired interconnect, Ethernet®, and / or other data transmission media / protocols) for communicating with other base stations and / or the core network. The base station 200 may optionally include an input / output (I / O) interface 206 for communicating with operators, etc.

[0045] The base station may also include a system network 204. The system network 204 may include a processor 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of the processors 124 to perform the functions of the base station. Parameters 228 may include parameters to support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0046] Figure 3 shows an exemplary user device (UE) 300. The UE 300 may be a mobile device, such as a smartphone or a mobile communication module placed in a vehicle. The UE 300 may include a communication interface 302, a system network 304, an input / output interface (I / O) 306, a display network 308, and a storage device 309. The display network may include a user interface 310. The system network 304 may include any combination of hardware, software, firmware, or other logic / circuit networks. The system network 304 may be implemented, for example, using one or more system-on-a-chip (SoCs), application-specific integrated circuits (ASICs), separate analog and digital circuits, and other networks. The system network 304 may be part of the implementation of any desired functionality in the UE 300. In this regard, the system circuitry 304 may include logic to facilitate, for example, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; launching applications; receiving user input; saving and retrieving application data; establishing, maintaining, and terminating mobile phone calls or data connections for internet connectivity, for example; establishing, maintaining, and terminating wireless network connections, Bluetooth® connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch sensor display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include microphones, video and still cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0047] Referring to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) network 316 that handles the transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be radio transceivers and include a modulation / demodulation network, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception through one or more antennas or (with respect to some devices) through a physical (e.g., wired) medium. The signals transmitted and received may conform to any of the following diverse array formats, protocols, modulation (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Communications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / Long-Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether they originate from the Third Generation Partnership Project (3GPP®), GSM® Association, 3GPP®2, IEEE, or other partnerships or standardization bodies.

[0048] Referring to Figure 3, the system network 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute instructions 326 to perform desired functionality with respect to the UE300. The parameters 328 provide and define configurations and may operate options for instructions 326. The memory 322 may store any BT, WiFi, 3G, 4G, 5G, or other data that the UE300 will transmit (or receive) through the communication interface 302. In various implementations, system power for the UE300 may be supplied by a battery or a power storage device such as a transformer.

[0049] This disclosure describes several embodiments of methods and devices for applying dynamic codebooks for hybrid automatic retransmission request acknowledgment (HARQ-ACK) feedback, which may be partially or fully implemented on wireless network base stations and / or user equipment as described in Figures 2 and 3 above.

[0050] In various embodiments, Figure 4A shows a flowchart of Method 400 for wireless communication. Method 400 may include step 410: a wireless communication device transmits a Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a Timing Advance Group (TAG).

[0051] In some implementations, each dynamic HARQ-ACK codebook is used for a few carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook.

[0052] In some implementations, for a dynamic HARQ-ACK codebook corresponding to a TAG, the Counter Downlink Allocation Index (cDAI) field in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to that TAG, while the Total Downlink Allocation Index (tDAI) field in the DCI for the dynamic HARQ-ACK codebook is used for a few carriers belonging only to that TAG.

[0053] In some implementations, the TAG index field included in the DCI indicates a TAG, which corresponds to a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

[0054] In some implementations, method 400 may further include receiving configuration information by a wireless communication device, the configuration information including a mapping between a dynamic HARQ-ACK codebook and a TAG, and the dynamic HARQ-ACK codebook is used for several carriers that belong only to that TAG.

[0055] In some implementations, the dynamic HARQ-ACK codebook information included in DCI indicates the dynamic HARQ-ACK codebook for scheduled physical downlink shared channels (PDSCHs).

[0056] In various embodiments, Figure 4B shows a flowchart of Method 450 for wireless communication. Method 450 may include step 460: a wireless communication node receives a Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) from a wireless communication device based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a Timing Advance Group (TAG).

[0057] In some implementations, each dynamic HARQ-ACK codebook is used for a few carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook.

[0058] In some implementations, for a dynamic HARQ-ACK codebook corresponding to a TAG, the Counter Downlink Allocation Index (cDAI) field in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to that TAG, while the Total Downlink Allocation Index (tDAI) field in the DCI for the dynamic HARQ-ACK codebook is used for a few carriers belonging only to that TAG.

[0059] In some implementations, the TAG index field included in the DCI indicates a TAG, which corresponds to a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

[0060] In some implementations, method 450 may further include transmitting configuration information by a wireless communication node, the configuration information including a mapping between a dynamic HARQ-ACK codebook and a TAG, and the dynamic HARQ-ACK codebook is used for several carriers that belong only to that TAG.

[0061] In some implementations, the dynamic HARQ-ACK codebook information included in DCI indicates the dynamic HARQ-ACK codebook for scheduled physical downlink shared channels (PDSCHs).

[0062] (Embodiment 1) This disclosure describes one non-limiting embodiment in which, when a codebook type for HARQ ACK / NACK feedback is configured by the UE as a dynamic codebook, the UE determines the number of dynamic codebooks according to the number of configured TAGs, and each dynamic codebook corresponds to one TAG.

[0063] In some implementations, the size of a dynamic codebook may be related to the number of component carriers belonging only to the corresponding TAG, and may not be affected by the number of component carriers in other TAGs.

[0064] In some implementations, with respect to inter-TAG CAs and the configured dynamic codebooks, the UE receives a DCI that schedules PDSCHs on one component carrier. The counter DAI and total DAI in the DCI are determined based solely on the downlink assignments on the carrier and the downlink assignments on other carriers belonging to the same TAG.

[0065] In some implementations, with respect to inter-TAG CA, the UE may apply two or more dynamic HARQ-ACK codebooks for HARQ ACK / NACK feedback, with each dynamic HARQ-ACK codebook corresponding to one TAG.

[0066] For a non-restrictive example, referring to the schematic diagram in Figure 1C, with respect to CA, the UE may receive downlink data on four component carriers: primary cell (pcell, 181), secondary cell 1 (scell1, 182), secondary cell 2 (scell2, 183), and secondary cell 3 (scell3, 184). pcell and scell1 may belong to TAG1, and scell2 and scell3 may belong to TAG2. The UE may apply two dynamic codebooks for HARQ ACK / NACK feedback. One dynamic codebook is used for HARQ ACK / NACK feedback for pcell and scell1, and the other dynamic codebook is used for HARQ ACK / NACK feedback for scell2 and scell3. The above non-restrictive example illustrates that the UE performs HARQ ACK / NACK feedback based on TAG-specific dynamic codebooks.

[0067] Figure 5 shows a flowchart of method 500 for a UE that processes TAG-specific dynamic codebooks. Method 500 may include some or all of the following steps: step 510 in which the UE configures the codebook type for HARQ ACK / NACK feedback as dynamic codebooks; step 520 in which the UE determines the number of dynamic codebooks based on the number of TAGs and determines the component carrier instance for each dynamic codebook based on the component carrier instance for TAGs; step 530 in which the UE transmits HARQ ACK / NACK feedback based on each dynamic codebook.

[0068] Referring to step 510, the UE is configured with a codebook type for HARQ ACK / NACK feedback as a dynamic codebook. Once the UE is configured with a HARQ-ACK codebook type as a dynamic codebook through upper layer signaling (NR RRC IE), the UE may use its dynamic HARQ-ACK codebook for HARQ ACK / NACK feedback. In some implementations, the UE may obtain cumulative downlink allocation and total downlink allocation based on the cDAI and tDAI in the DCI that schedules the PDSCH.

[0069] Referring to step 520, the UE determines the number of dynamic codebooks based on the number of TAGs, and the component carrier instance for each dynamic codebook based on the component carrier instance for each TAG. In some implementations, the UE may determine the number of dynamic codebooks for HARQ ACK / NACK feedback according to the number of TAGs configured. Since each dynamic codebook corresponds to a TAG, the UE may determine the component carrier instance for each dynamic codebook according to the component carrier instance for each TAG.

[0070] Referring to step 530, the UE provides HARQ ACK / NACK feedback based on each dynamic codebook. In some implementations, the UE provides HARQ ACK / NACK feedback for PDSCH on each component carrier by having the component carrier use the corresponding dynamic codebook.

[0071] (Embodiment 2) This disclosure describes other non-limiting embodiments in which a TAG-specific dynamic codebook mechanism is generated based on the DAI fields (tDAI and / or cDAI) in the DCI. In some implementations, the DCI may include counter DAI information and total DAI information. The value of counter DAI indicates the cumulative number of downlink assignments received to date for the TAG. In some implementations, the statistical sequence of the cumulative number is as follows: first, in ascending order of the serving cell index belonging to the TAG, and then in ascending order of the scheduled PDSCH in the time domain for the TAG. The value of total DAI indicates the total number of downlink assignments received to date for the TAG.

[0072] In some implementations, when the UE receives a downlink assignment on a component carrier, the UE may determine the TAG to which the component carrier belongs and all other component carriers under that TAG. The UE retrieves the counter DAI information and total DAI information in the DCI and determines the total number of downlink assignments received under the TAG to date and the cumulative number for downlink assignments received under the TAG to date.

[0073] Figure 6 shows a flowchart of Method 600 for a UE that processes counter DAI information and total DAI information in the DCI for a TAG. Method 600 may include some or all of the following steps: Step 610 in which the UE determines the TAG to which a component carrier belongs and all other component carriers belonging to the TAG based on the component carrier to which the DCI with cDAI and tDAI has been received; Step 620 in which the UE determines the cumulative number of downlink assignments received and the total number of downlink assignments received for the TAG according to the counter DAI information and total DAI information in the DCI that has been received, and the UE determines the position for the downlink assignment in the dynamic HARQ-ACK codebook.

[0074] Referring to step 610, the UE receives the DCI with the cDAI and tDAI on the component carrier. In some implementations, according to the TAG configuration information for the component carrier, the UE determines the TAG to which the component carrier belongs. In some implementations, according to the TAG configuration information, the UE determines all other component carriers belonging to the TAG.

[0075] Referring to step 620, the UE determines the cumulative number of downlink assignments received according to the counter DAI information and total DAI information in the received DCI, and determines the total number of downlink assignments received for the TAG. The counter DAI information in the DCI is used to show the cumulative number of downlink assignments received to date, and the total DAI information in the DCI is used to show the total number of downlink assignments received to date for the TAG. Based on multiple front and back pairs of counter DAI information and total DAI information, the UE may determine whether any downlink assignments have been missed.

[0076] The UE determines the location for downlink assignments within a dynamic HARQ-ACK codebook to transmit HARQ ACK / NACK feedback information. In some implementations, the dynamic HARQ-ACK codebook may be a bit string where each bit corresponds to HARQ information (ACK or NACK, etc.) for a downlink assignment. The size of the dynamic HARQ-ACK codebook is determined based on the total number of downlink assignments corresponding to the TAGs.

[0077] (Embodiment 3) This disclosure describes other non-limiting embodiments in which a UE may receive a DCI containing TAG information, thereby enabling the UE to determine a dynamic codebook based on the correspondence between the TAG and the dynamic codebook. In some implementations, the UE may obtain a component carrier instance for the dynamic codebook based on the component carrier instance included by the TAG.

[0078] In some implementations, a TAG index (TAG-ID) may be used to indicate TAG information, and the DCI includes a field for the TAG-ID. The UE receives the TAG-ID field in the DCI and retrieves the TAG information.

[0079] Figure 7 shows a flowchart of Method 700 for a UE to obtain TAG information in DCI. Method 700 may include some or all of the following steps: Step 710 in which the UE obtains TAG configuration information; Step 720 in which the UE determines the dynamic codebook based on the correspondence between the dynamic codebook and the TAG.

[0080] Referring to step 710, the UE obtains TAG configuration information. In some implementations, the UE may receive serving cell configuration information including a TAG-ID. The TAG-ID may indicate the TAG to which the serving cell (carrier) belongs. In some implementations, the UE may obtain all component carrier instances under the TAG indicated by the TAG-ID.

[0081] Referring to step 720, the UE determines the dynamic codebook based on the correspondence between the dynamic codebook and the TAG. In some implementations, the dynamic codebook corresponds to the TAG, so the UE determines the dynamic codebook from the TAG information, such as the TAG-ID, as shown in the DCI.

[0082] (Embodiment 4) This disclosure describes another non-limiting embodiment in which DCI may include dynamic codebook information. In some implementations, radio resource configuration information includes a correspondence between a dynamic codebook and a component carrier instance.

[0083] In some implementations, configuration information such as Radio Resource Control (RRC) Information Elements (IEs) received by the UE includes dynamic codebook information used to indicate the correspondence between dynamic codebooks and component carrier instances. Methods for dynamic codebook configuration information include, but are not limited to, having the RRC IE represent dynamic codebook information or having the RRC IE represent a dynamic codebook index.

[0084] In some implementations, the correspondence between a dynamic codebook and a component carrier instance may be referred to as a mapping. Methods for representing the correspondence between a dynamic codebook and a component carrier instance may include, but are not limited to,: a dynamic codebook index in serving cell configuration information; or one or more serving cell indexes in dynamic codebook configuration information; or separate configuration information containing a dynamic codebook index and one or more serving cell indexes.

[0085] In some implementations, dynamic codebook information is included in layer 1 signaling. For example, a UE may receive dynamic codebook information indicated in the DCI. In some implementations, the way in which a dynamic codebook is indicated in the DCI may include, but are not limited to, the following: a field in the DCI indicates a dynamic codebook index; or a field in the DCI corresponds to a dynamic codebook.

[0086] Figure 8 shows a flowchart of Method 800 for a UE to receive dynamic codebook information in DCI. Method 800 may include some or all of the following steps: Step 810 in which the UE receives dynamic codebook configuration information and correspondence between the dynamic codebook and component carrier instances; Step 820 in which the UE receives dynamic codebook information in DCI and determines the dynamic codebook; and Step 830 in which the UE uses the dynamic codebook to perform HARQ ACK / NACK feedback.

[0087] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure addresses issues related to applying dynamic codebooks for Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) feedback. The methods, devices, and computer-readable media described herein can enhance the performance of wireless communication and therefore improve efficiency and overall performance by applying dynamic codebooks for HARQ-ACK feedback. The methods, devices, and computer-readable media described herein can improve the overall efficiency of wireless communication systems.

[0088] Throughout this specification, references to features, advantages, or similar terms do not imply that all features and advantages that can be realized using the Solution should be included in any single implementation thereof. Rather, terms referring to features and advantages should be understood to mean that specific features, advantages, or characteristics described in relation to a particular embodiment are included in at least one embodiment of the Solution. Accordingly, discussions of features and advantages, as well as similar terms, throughout this specification may, but not necessarily, refer to the same embodiment.

[0089] Furthermore, the features, advantages, and characteristics described herein can be combined in any preferred manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the present solution may be implemented without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages that may not be present in all embodiments of the present solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication, wherein the method is The wireless communication device includes transmitting HARQ-ACK based on two or more Dynamic Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) codebooks, Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG), A method in which each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding by the dynamic HARQ-ACK codebook.

2. For the dynamic HARQ-ACK codebook corresponding to the TAG, The Counter Downlink Assignment Index (cDAI) field included in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to the TAG. The method according to claim 1, wherein the total downlink assignment index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG.

3. The method according to claim 1, wherein the TAG index field included in the DCI indicates the TAG, and the TAG corresponds to the dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

4. The wireless communication device further includes receiving configuration information, The method according to claim 1, wherein the configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG.

5. The method according to claim 1, wherein the dynamic HARQ-ACK codebook information included in the DCI indicates the dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

6. A method for wireless communication, wherein the method is The wireless communication node includes receiving HARQ-ACKs from a wireless communication device based on two or more Dynamic Hybrid Auto Retransmission Request Acknowledgment (HARQ-ACK) codebooks, Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG), A method in which each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding by the dynamic HARQ-ACK codebook.

7. For the dynamic HARQ-ACK codebook corresponding to the TAG, The Counter Downlink Assignment Index (cDAI) field included in the Downlink Control Information (DCI) is counted based on the number of carriers belonging only to the TAG. The method according to claim 6, wherein the total downlink assignment index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for several carriers belonging only to the TAG.

8. The method according to claim 6, wherein the TAG index field included in the DCI indicates the TAG, and the TAG corresponds to the dynamic HARQ-ACK codebook for the scheduled physical downlink shared channel (PDSCH).

9. The wireless communication node further includes transmitting configuration information, The method according to claim 6, wherein the configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG.

10. The method according to claim 6, wherein the dynamic HARQ-ACK codebook information included in the DCI indicates the dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

11. Apparatus, the apparatus, The memory that stores the instructions, At least one processor that communicates with the memory and Equipped with, When the at least one processor executes the instruction, the at least one processor, The device is configured to transmit HARQ-ACK based on two or more Dynamic Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) codebooks. Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG), Each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook.

12. The apparatus according to claim 11, wherein the TAG index field included in the DCI indicates the TAG, and the TAG corresponds to the dynamic HARQ-ACK codebook for the scheduled physical downlink shared channel (PDSCH).

13. When the at least one processor executes the instruction, the at least one processor, The device is further configured to receive configuration information, The apparatus according to claim 11, wherein the configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG.

14. The apparatus according to claim 11, wherein the dynamic HARQ-ACK codebook information included in the DCI indicates the dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

15. Apparatus, the apparatus, The memory that stores the instructions, At least one processor that communicates with the memory and Equipped with, When the at least one processor executes the instruction, the at least one processor, The device is configured to receive HARQ-ACKs from a wireless communication device based on two or more Dynamic Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) codebooks. Each dynamic HARQ-ACK codebook corresponds to a Timing Advance Group (TAG), Each dynamic HARQ-ACK codebook is used for several carriers that belong only to the TAGs corresponding to the dynamic HARQ-ACK codebook.

16. The apparatus according to claim 15, wherein the TAG index field included in the DCI indicates the TAG, and the TAG corresponds to the dynamic HARQ-ACK codebook for the scheduled physical downlink shared channel (PDSCH).

17. When the at least one processor executes the instruction, the at least one processor, The device is further configured to transmit configuration information, The apparatus according to claim 15, wherein the configuration information includes a mapping between the dynamic HARQ-ACK codebook and the TAG.

18. The apparatus according to claim 15, wherein the dynamic HARQ-ACK codebook information included in the DCI indicates the dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

Images