Method and device for applying a dynamic codebook for HARQ-ACK feedback

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

[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

[0002] Wireless communication technology is making the world more and more connected and networked. In the present disclosure, various embodiments for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback are described.

[0003] When wireless communication is carried out under carrier aggregation (CA), there may be a relatively long waiting time for information transmission between various carriers belonging to different timing advance groups (TAGs). There may be various problems / issues associated with HARQ-ACK information feedback using a dynamic codebook. For example, one of the problems / issues is that when the dynamic codebook is used for HARQ-ACK information feedback regarding dynamic scheduling (e.g., downlink allocation indicated in DCI), the total downlink allocation index (tDAI) or the counter downlink allocation index (cDAI) may not be accurately indicated in the downlink control information (DCI).

[0004] An improved and appropriate design of a control mechanism for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback can help improve the efficiency of a wireless access network. The present disclosure can address at least one of the problems / issues associated with existing systems to improve the performance of wireless communication.

Summary of the Invention

Means for Solving the Problems

[0005] This book relates to methods, systems, and devices for wireless communication, and more specifically, to methods, systems, and devices for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. Various embodiments within the present disclosure may be beneficial for improving the application of a dynamic codebook for HARQ-ACK feedback in order to increase resource utilization efficiency and improve the latency performance of wireless communication.

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes transmitting, by a wireless communication device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, where each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

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

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

[0009] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the above 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.

Brief Description of the Drawings

[0012]

Fig. 1A

[0013]

Fig. 1B

[0014]

Fig. 1C

[0015]

Fig. 2

[0016]

Fig. 3

[0017]

Fig. 4A

[0018]

Fig. 4B

[0019]

Fig. 5

[0020]

Fig. 6

[0021]

Fig. 7

[0022]

Fig. 8

[0023] The present disclosure will now be described in detail with reference to the accompanying drawings, which form a part hereof and illustrate, by way of example, specific examples of the embodiments. However, it should be noted that the present disclosure may be embodied in various different forms and, accordingly, the subject matter contained or claimed is not intended to be limited to any of the embodiments described hereinafter.

[0024] Throughout this specification and the claims, terms may have subtle meanings suggested or implied within the 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 combinations of exemplary embodiments or implementations, whether in whole or in part.

[0025] In general, technical terms can be understood at least in part from their use in context. For example, terms such as "and", "or", or "and / or" as used herein can include various meanings that can depend at least in part on the context in which such terms are used. Typically, "or" is intended to mean, when used to associate a list such as "A, B, or C", "A, B, and C" as used herein in an inclusive sense, as well as "A, B, or C" as used herein in an exclusive sense. In addition, terms such as "one or more" or "at least one" as used herein can, at least in part depending on the context, be used to describe any feature, structure, or property in a singular sense or be used to describe a combination of features, structures, or properties in a plural sense. Similarly, again, terms such as "a", "an", or "the" can be understood, at least in part depending on the context, to convey a singular use or to convey a plural use. In addition, the terms "based on" or "determined by" can be understood as not necessarily intending to convey an exclusive set of factors, but rather, again, can, at least in part depending on the context, allow for the presence of additional factors that are not necessarily explicitly described.

[0026] This disclosure describes a method and device for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. In various embodiments, applying a dynamic codebook for HARQ-ACK feedback can include applying and / or using a TAG-specific dynamic codebook for HARQ-ACK feedback.

[0027] Next-generation (NG) or fifth-generation (5G) wireless communication can provide capabilities ranging from high-speed downloads to supporting real-time low-latency communication. The new-generation (NG) mobile communication system is moving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on the 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 an important technology for multi-frequency aggregation in cellular mobile communication systems (e.g., 4G or 5G). CA includes in-timing-advance-group (TAG) carrier aggregation and cross-TAG carrier aggregation. When using a dynamic codebook for downlink HARQ ACK / NACK, the UE may need to be notified of this scheduling countdown downlink allocation index (DAI) and the total DAI through downlink control information (DCI). In some implementations, the total DAI may require scheduling information for all carriers including the primary cell (Pcell) and all secondary cells (Scell). This requires that the DCI for one carrier obtain scheduling information for other carriers, and the exchange of scheduling information between different carriers may require a certain amount of time, which may be known as the delay for the exchange of scheduling information. For cross-TAG CA, the scheduling information exchange delay between carriers of different TAGs can usually be larger, which seriously affects the scheduling timing and may even cause scheduling failures.

[0029] This disclosure describes various embodiments for transmitting hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, each dynamic HARQ-ACK codebook corresponding to a timing advance group (TAG), which addresses at least one of the problems / issues associated with current systems.

[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 equipments (UE) (152, 154, and 156). The RAN 130 may include a wireless 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 telecommunication. In one implementation, the core network 110 may include a 5G core network (5GC), and the interface 125 may include a new generation (NG) interface.

[0031] Referring to Figure 1A, the first UE 152 may wirelessly receive one or more downlink communications 142 from the RAN 130 and wirelessly transmit one or more uplink communications 141 to the RAN 130. Similarly, the second UE 154 may wirelessly receive a downlink communication 144 from the RAN 130 and wirelessly transmit an uplink communication 143 to the RAN 130, and the third UE 156 may wirelessly receive a downlink communication 146 from the RAN 130 and wirelessly transmit an uplink communication 145 to the RAN 130. For example, but not limited to, the downlink communication may include a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and the uplink communication 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 a 5G new radio (NR) implementation, carrier aggregation (CA) includes intra-TAG CA and inter-TAG CA. Intra-TAG CA refers to CA in which all carriers therein belong to the same TAG, and inter-TAG CA refers to CA in which the aggregated carriers therein belong to different TAGs.

[0033] In some other implementations, carriers belonging to the same TAG may share one timing advance (TA). TA adjustment signaling, e.g., the TA medium access control (MAC) control element (CE) received by the UE on one carrier, may be multiplexed to 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 as carriers belonging to different TAGs. Thus, with respect to the carrier aggregation deployed on the same nodeB site, it is generally regarded as CA within the TAG, and with respect to the carrier aggregation deployed on different nodeB sites, it is generally regarded as CA between TAGs.

[0035] In some other implementations, the HARQ-ACK codebook refers to the whole HARQ information fed back by the UE on one HARQ feedback resource (e.g., PUCCH or PUSCH). The timing parameter (e.g., K1) is one of the important parameters for determining the HARQ-ACK codebook. The timing parameter (e.g., K1) may be the time offset value between the PDSCH and the PUCCH or PUSCH for HARQ-ACK feedback. The way to indicate the K1 parameter is that the network first configures the K1 value set through the radio resource control information element (RRC IE), and then dynamically indicates the value in the K1 value set through the HARQ feedback indication 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 where the size of the HARQ ACK / NACK codebook can be dynamically determined based on downlink allocations across all carriers related to CA. The dynamic codebook mechanisms for 5G New Radio (NR) and Long-Term Evolution (LTE) can be similar. The value of the counter DAI in the DCI indicates the accumulated number of current PDSCHs. The statistical sequence of the accumulated numbers is as follows: First, in ascending order of the serving cell index included in CA for the codebook, and then in ascending order of the PDSCH time-domain opportunities. The value of the total DAI in the DCI indicates the total number of PDSCHs related to CA so far.

[0037] One of the main problems with HARQ ACK / NACK feedback using a dynamic codebook is that, for CA across different TAGs, the DCI for each carrier requires the DAI for other carriers to calculate the total DAI. The scheduling information exchange delay across carriers in different TAGs is usually very large, which seriously affects the scheduling timing and even causes scheduling failures.

[0038] The present invention describes various embodiments for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. When a dynamic codebook is used for HARQ ACK / NACK feedback for carrier aggregation (CA) between transmission and reception points (TAGs), a user equipment (UE) may use two or more dynamic codebooks simultaneously, with each dynamic codebook corresponding to one TAG. When the UE is composed of a plurality of carriers (such as CA) and these carriers belong to a plurality of different TAGs, the UE may use two or more dynamic codebooks to perform HARQ ACK / NACK feedback. Each dynamic codebook is used for the carriers belonging to one of the TAGs. Regarding CA between TAGs, one dynamic codebook is used for the carriers belonging to one of the TAGs, and another dynamic codebook is used for the carriers belonging to another one of the TAGs. When the UE simultaneously receives physical downlink shared channels (PDSCHs) on carriers belonging to a plurality of TAGs for CA, the UE may use a plurality of dynamic codebooks simultaneously for HARQ ACK / NACK feedback, with each dynamic codebook corresponding to one TAG.

[0039] For a non-limiting example, the CA situation between TAGs is shown in FIG. 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 the carriers belonging to one of the TAGs. For example, dynamic codebook 1 (171) for TAG1 (176), and dynamic codebook 2 (172) for another TAG (TAG2, 177). TAG1 (176) may include one or more carriers, such as carrier 1 (173) and carrier 2 (174). TAG2 (177) may include one or more carriers, such as carrier 3 (177).

[0040] The DCI on a carrier may need to determine the counter DAI and the total DAI based on the downlink allocation on other carriers in the same TAG. That is, one counter DAI and one total DAI correspond to one TAG. For inter-TAG CA, the UE may receive the counter DAI and the total DAI for two or more dynamic codebooks simultaneously, and each dynamic codebook corresponds to one TAG.

[0041] For a non-limiting example, the inter-TAG CA situation is shown in FIG. 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). These four carriers are all time-division duplex (TDD) carriers and may have a downlink-uplink configuration with a pattern. One period includes four slots. The first slot is a downlink (D) slot, the second slot is a downlink (D) slot, the third slot is a special (S) slot, and the fourth slot is an uplink (U) slot. For a non-limiting example only, for the first carrier, the downlink allocation on the first slot using (counter DAI, total DAI) is (1, 2), and for the second carrier, the downlink allocation on the first slot using (counter DAI, total DAI) is (2, 2). In some implementations, (counter DAI, total DAI) may be denoted as (cDAI, tDAI). For a non-limiting example only, 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 carrier and the second carrier, and both of them belong to TAG1.

[0042] There may be another single dynamic codebook for the third carrier and the fourth carrier, both of which belong to TAG2. Merely for non-limiting examples, for the third carrier, the downlink allocation on the first slot using (cDAI, tDAI) is (1, 2), and for the fourth carrier, the downlink allocation on the first slot using (cDAI, tDAI) is (2, 2). For the third carrier, the downlink allocation on the second slot using (cDAI, tDAI) is (3, 4), and for the fourth carrier, the downlink allocation on the second slot using (cDAI, tDAI) is (4, 4).

[0043] This disclosure describes various embodiments for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

[0044] FIG. 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) circuitry 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 circuitry 209 (e.g., optical or wired interconnects, Ethernet®, and / or other data transmission media / protocols) for communicating with other base stations and / or a core network. The base station 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

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

[0046] Figure 3 shows an exemplary user equipment (UE) 300. The UE 300 can be a mobile device, e.g., a smartphone or a mobile communication module disposed within a vehicle. The UE 300 can include a communication interface 302, a system circuitry 304, an input / output interface (I / O) 306, a display circuitry 308, and a storage device 309. The display circuitry can include a user interface 310. The system circuitry 304 can include any combination of hardware, software, firmware, or other logic / circuitry. The system circuitry 304 can be implemented, for example, using one or more system-on-chips (SoCs), application-specific integrated circuits (ASICs), separate analog and digital circuits, and other circuitry. The system circuitry 304 can be part of the implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 can include, by way of example, logic for decoding and playing music and videos, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback, launching applications, receiving user input, storing and retrieving application data, establishing, maintaining, and terminating a cellular phone call or a data connection, for example, for Internet connectivity, establishing, maintaining, and terminating a wireless network connection, a Bluetooth® connection, or other connections, and facilitating the display of relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 can include a graphical user interface, a touch sensor-based display, haptic feedback or other haptic output, voice or face recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of the I / O interface 306 can include a microphone, 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 input.

[0047] Referring to FIG. 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) circuitry 316 that handles signal transmission and reception through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver and may include modulation / demodulation circuitry, digital / analog converters (DACs), shaping tables, analog / digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or, for some devices, through a physical (e.g., wired) medium. The signals transmitted and received may conform to any of a variety of array formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bitrates, and encodings. As one specific example, the communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications 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 regardless of whether they originate from the 3rd Generation Partnership Project (3GPP®), GSM® Association, 3GPP®2, IEEE, or other partnerships or standardization bodies.

[0048] Referring to FIG. 3, the system circuit 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 the instructions 326 to perform desired functionality with respect to the UE 300. The parameters 328 may provide and define configurations and operate options for the instructions 326. The memory 322 may store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will transmit (or has received) through the communication interface 302. In various implementations, the system power for the UE 300 may be supplied by a power storage device such as a battery or a transformer.

[0049] The present disclosure describes some embodiments of a method and a device for applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback that may be implemented partially or fully on a wireless network base station and / or user equipment described in FIGS. 2 and 3 above.

[0050] In various embodiments, FIG. 4A shows a flowchart of a method 400 for wireless communication. The method 400 may include step 410: transmitting, by a wireless communication device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, where each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

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

[0052] In some implementations, for a dynamic HARQ-ACK codebook corresponding to a TAG, a counter downlink allocation index (cDAI) field included in downlink control information (DCI) is counted based on the number of carriers that only belong to that TAG, and a total downlink allocation index (tDAI) field included in DCI for the dynamic HARQ-ACK codebook is used for some carriers that only belong to that TAG.

[0053] In some implementations, a TAG index field included in DCI indicates a TAG, and the TAG 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, by a wireless communication device, configuration information, the configuration information including a mapping between a dynamic HARQ-ACK codebook and a TAG, and the dynamic HARQ-ACK codebook being used for some carriers that only belong to that TAG.

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

[0056] In various embodiments, FIG. 4B shows a flowchart of a method 450 for wireless communication. Method 450 may include step 460: receiving, by a wireless communication node, from a wireless communication device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks, where each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

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

[0058] In some implementations, for the dynamic HARQ-ACK codebook corresponding 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 that only belong to that TAG, and the total downlink assignment index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for some carriers that only belong to that TAG.

[0059] In some implementations, 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).

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

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

[0062] (Embodiment 1) This disclosure describes one non-limiting embodiment. In one non-limiting embodiment, when the codebook type for HARQ ACK / NACK feedback is configured as a dynamic codebook by the UE, 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 the dynamic codebook may be related to the number of component carriers that only belong to the corresponding TAG and may not be affected by the number of component carriers in other TAGs.

[0064] In some implementations, regarding inter-TAG CA and the configured dynamic codebooks, the UE receives DCI that schedules PDSCH on one component carrier. The counter DAI and the total DAI in the DCI are determined based only on the downlink allocations on other carriers that belong to the same TAG as the downlink allocation on the carrier.

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

[0066] Regarding a non-limiting example, referring to the schematic diagram of FIG. 1C, with respect to CA, for the UE, downlink data can be received on four component carriers of a primary cell (pcell, 181), a secondary cell 1 (scell1, 182), a secondary cell 2 (scell2, 183), and a secondary cell 3 (scell3, 184). The pcell and scell1 may belong to TAG1, and the 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 the pcell and scell1, and the other dynamic codebook is used for HARQ ACK / NACK feedback for the scell2 and scell3. The above non-limiting example shows that the UE performs HARQ ACK / NACK feedback based on a TAG-specific dynamic codebook.

[0067] FIG. 5 shows a flowchart of a method 500 for a UE that processes a TAG-specific dynamic codebook. The method 500 may include some or all of the following steps: step 510 where the UE is configured with a codebook type for HARQ ACK / NACK feedback as a dynamic codebook; step 520 where the UE determines the number of dynamic codebooks based on the number of TAGs and determines the component carrier instances for each dynamic codebook based on the component carrier instances for the TAGs; step 530 where 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 as a dynamic codebook. When 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 the cumulative downlink allocation and the total downlink allocation based on cDAI and tDAI in the DCI scheduling the PDSCH.

[0069] Referring to step 520, 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 the TAG. In some implementations, the UE may determine the number of dynamic codebooks for HARQ ACK / NACK feedback according to the number of configured TAGs. 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 feeds back HARQ ACK / NACK based on each dynamic codebook. In some implementations, the UE feeds back HARQ ACK / NACK for the PDSCH on each component carrier by using the dynamic codebook corresponding to the component carrier.

[0071] (Embodiment 2) This disclosure describes another non-limiting embodiment, and in another non-limiting embodiment, 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 the counter DAI indicates the cumulative number of downlink allocations received so far for the TAG. In some implementations, the statistical sequence of the cumulative numbers 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 the total DAI indicates the total number of downlink allocations received so far for the TAG.

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

[0073] FIG. 6 shows a flowchart of a 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 where the UE determines the TAG to which the component carrier belongs and all of the other component carriers belonging to the TAG based on the component carrier on which the DCI with cDAI and tDAI is received; step 620 where the UE determines the cumulative number of downlink allocations received according to the counter DAI information and total DAI information in the received DCI and the total number of downlink allocations received for the TAG, and the UE determines the position for the downlink allocation in the dynamic HARQ-ACK codebook.

[0074] Referring to step 610, the UE receives DCI with 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 received downlink allocations according to the counter DAI information and the total DAI information in the received DCI, and determines the total number of received downlink allocations for the TAG. The counter DAI information in the DCI is used to indicate the cumulative number of received downlink allocations so far, and the total DAI information in the DCI is used to indicate the total number of received downlink allocations so far for the TAG. The UE can determine whether it has missed a downlink allocation based on multiple pairs of the front and back of the counter DAI information and the total DAI information.

[0076] The UE determines the position for the downlink allocation in the dynamic HARQ-ACK codebook to transmit HARQ ACK / NACK feedback information. In some implementations, the dynamic HARQ-ACK codebook can be a bit string where each bit corresponds to HARQ information (such as ACK or NACK) for the downlink allocation. The size of the dynamic HARQ-ACK codebook is determined based on the total number of downlink allocations corresponding to the TAG.

[0077] (Embodiment 3) This disclosure describes another non-limiting embodiment, in which a UE may receive DCI containing TAG information, whereby the UE may 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 obtains the TAG information.

[0079] FIG. 7 shows a flowchart of a method 700 for a UE to obtain TAG information in DCI. Method 700 may include some or all of the following steps: step 710 where the UE obtains TAG configuration information; step 720 where the UE determines a 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 the 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 a dynamic codebook based on the correspondence between the dynamic codebook and the TAG. In some implementations, since the dynamic codebook corresponds to the TAG, the UE determines the dynamic codebook from TAG information such as the TAG-ID indicated in the DCI.

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

[0083] In some implementations, configuration information, such as a radio resource control (RRC) information element (IE) received by a UE, includes dynamic codebook information used to indicate a correspondence between a dynamic codebook and a component carrier instance. Methods for dynamic codebook configuration information include, but are not limited to, the RRC IE representing dynamic codebook information or the RRC IE representing 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 including a dynamic codebook index and one or more serving cell indexes.

[0085] In some implementations, the dynamic codebook information is included in layer 1 signal transmission. For example, a UE may receive dynamic codebook information indicated in the DCI. In some implementations, methods for indicating a dynamic codebook within the DCI may include, but are not limited to: a field in the DCI indicating a dynamic codebook index; or a field in the DCI corresponding to a dynamic codebook.

[0086] FIG. 8 shows a flowchart of a method 800 for a UE that receives dynamic codebook information in DCI. The method 800 may include some or all of the following steps: step 810 in which the UE receives configuration information of a dynamic codebook and a correspondence between the dynamic codebook and a component carrier instance; and 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] The present disclosure describes a method, an apparatus, and a computer-readable medium for wireless communication. The present disclosure addresses problems related to applying a dynamic codebook for hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback. The method, device, and computer-readable medium described in the present disclosure can enhance the performance of wireless communication by applying a dynamic codebook for HARQ-ACK feedback, and thus improve efficiency and overall performance. The method, device, and computer-readable medium described in the present disclosure can improve the overall efficiency of a wireless communication system.

[0088] References throughout this specification to features, advantages, or similar language do not imply that all of the features and advantages that can be realized using the solution should be, or are included in, any single implementation. Rather, the language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, discussions of the features and advantages throughout this specification, and similar language, may, but do not necessarily, refer to the same embodiment.

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

Claims

1. A method for wireless communication, the method comprising: transmitting, by a wireless communication device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks; wherein each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

2. The method according to claim 1, wherein each dynamic HARQ-ACK codebook is used for some carriers that only belong to the TAG corresponding to the dynamic HARQ-ACK codebook.

3. For a dynamic HARQ-ACK codebook corresponding to a TAG, a countdown downlink allocation index (cDAI) field included in downlink control information (DCI) is counted based on the number of carriers that only belong to the TAG, and a total downlink allocation index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for some carriers that only belong to the TAG. The method according to any one of claims 1-2.

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

5. further comprising receiving, by the wireless communication device, configuration information, wherein the configuration information includes a mapping between a dynamic HARQ-ACK codebook and a TAG, and the dynamic HARQ-ACK codebook is used for some carriers that only belong to the TAG. The method according to claim 1.

6. The method according to any one of claims 1-3, wherein the dynamic HARQ-ACK codebook information included in DCI indicates a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

7. A method for wireless communication, the method comprising: receiving, by a wireless communication node, from a wireless communication device, a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on two or more dynamic HARQ-ACK codebooks; wherein each dynamic HARQ-ACK codebook corresponds to a timing advance group (TAG).

8. The method according to claim 7, wherein each dynamic HARQ-ACK codebook is used for some carriers belonging only to the TAG corresponding to the dynamic HARQ-ACK codebook.

9. For a dynamic HARQ-ACK codebook corresponding to a TAG, a countdown downlink allocation index (cDAI) field included in downlink control information (DCI) is counted based on the number of carriers belonging only to the TAG, and a total downlink allocation index (tDAI) field included in the DCI for the dynamic HARQ-ACK codebook is used for some carriers belonging only to the TAG. The method according to any one of claims 7-8.

10. The method according to any one of claims 7-9, wherein a TAG index field included in DCI indicates a TAG, and the TAG corresponds to a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

11. further comprising transmitting, by the wireless communication node, configuration information, wherein the configuration information includes a mapping between a dynamic HARQ-ACK codebook and a TAG, and the dynamic HARQ-ACK codebook is used for some carriers belonging only to the TAG. The method according to any one of claims 7.

12. The method according to any one of claims 7-9, wherein the dynamic HARQ-ACK codebook information included in DCI indicates a dynamic HARQ-ACK codebook for a scheduled physical downlink shared channel (PDSCH).

13. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method according to any one of claims 1-12.

14. A computer program product comprising stored computer-readable program media code, wherein when the computer-readable program media code is executed by a processor, the processor is caused to implement the method according to any one of claims 1-12.

Images