Communication methods, terminal devices, and network devices

Abstract

This invention provides methods, apparatus, and computer storage media for extending the Hybrid Automatic Retransmission Request Acknowledgment (HARQ-ACK) codebook. [Solution] The communication method implemented in the terminal device includes receiving information from the network device indicating a first resource for the initial transmission of a first Hybrid Automatic Retransmission Request (HARQ) feedback for a first data transmission; receiving first downlink control information (DCI) indicating a second resource for the retransmission of the first HARQ feedback; receiving a second DCI indicating a third resource for the initial transmission of a second HARQ feedback having the same priority as the first HARQ feedback for a second data transmission scheduled to occur after the first data transmission; and transmitting the first HARQ feedback to the network device using the second resource.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to a method, apparatus, and computer storage medium for extending a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook.

Background Art

[0002] Downlink control information (DCI) is utilized by a base station (e.g., gNB) to schedule various data transmissions or services on a physical downlink shared channel (PDSCH). When the DCI is decoded, a terminal device (e.g., UE) can receive the transmission and then transmit a corresponding hybrid automatic repeat request (HARQ) feedback for the transmission on a physical uplink control channel (PUCCH). In some cases, the transmission of HARQ feedback on a PUCCH resource may be canceled or discarded. For example, if a PUCCH resource for low-priority HARQ feedback overlaps with a PUCCH resource for high-priority HARQ feedback, the high-priority HARQ feedback is transmitted and the low-priority HARQ feedback is discarded. For another example, in the case of a time division duplex (TDD) system, if a configured grant (CG) PUCCH resource set for semi-persistent scheduling (SPS) HARQ feedback collides with a DL symbol, the transmission of SPS HARQ feedback is canceled. Additionally, if HARQ feedback is multiplexed in a physical uplink shared channel (PUSCH) resource canceled by a UL cancellation instruction from the gNB, the transmission of the HARQ feedback is necessarily canceled.

[0003] In this case, if the gNB does not receive HARQ feedback for a data transmission, it is desirable to trigger a retransmission of the canceled HARQ feedback rather than directly retransmitting the data transmission. This is advantageous for the spectral efficiency of the communication system. [Overview of the project] [Problems that the invention aims to solve]

[0004] Overall, embodiments of the present disclosure provide methods, apparatus, and computer storage media for an extended HARQ feedback mechanism. [Means for solving the problem]

[0005] In a first embodiment, a method of communication is provided. The method includes a terminal device receiving from a network device information indicating a first resource for the initial transmission of a first Hybrid Automatic Repeat Request (HARQ) feedback for a first data transmission; receiving from the network device first downlink control information (DCI) indicating a second resource for the retransmission of the first HARQ feedback; receiving from the network device second downlink control information (DCI) indicating a third resource for the initial transmission of a second HARQ feedback having the same priority as the first HARQ feedback for a second data transmission scheduled to occur after the first data transmission; and transmitting the first HARQ feedback to the network device using the second resource.

[0006] In a second embodiment, a method of communication is provided. The method includes, in a network device, transmitting to a terminal device information indicating a first resource for the initial transmission of a first hybrid automatic retransmission request (HARQ) feedback for a first data transmission; transmitting to the terminal device first downlink control information (DCI) indicating a second resource for retransmitting the first HARQ feedback in accordance with a decision that the first resource for the first HARQ feedback is canceled; transmitting to the terminal device second downlink control information (DCI) indicating a third resource for the initial transmission of a second HARQ feedback having the same priority as the first HARQ feedback for a second data transmission scheduled to occur after the first data transmission; and receiving the first HARQ feedback from the terminal device at the second resource.

[0007] In a third embodiment, a terminal device is provided. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions, when executed by the processor, that cause the terminal device to perform the method according to the first embodiment of this disclosure.

[0008] In a fourth embodiment, a network device is provided. The network device comprises a processor and a memory coupled to the processor. The memory stores instructions, when executed by the processor, that cause the network device to perform the method according to the second embodiment of this disclosure.

[0009] In a fifth embodiment, a computer-readable medium storing instructions is provided. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method according to the first embodiment of the present disclosure.

[0010] In a sixth embodiment, a computer-readable medium storing instructions is provided. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method described in the second embodiment of this disclosure.

[0011] Other features of this disclosure should be easily understood from the following explanation. [Brief explanation of the drawing]

[0012] The above-mentioned and other objectives, features, and advantages of this disclosure will be further clarified by describing in more detail some embodiments of this disclosure in the attached drawings.

[0013] [Figure 1] This figure shows an exemplary communication network that can implement some embodiments of the present disclosure.

[0014] [Figure 2A] This is a schematic diagram illustrating an out-of-order HARQ feedback retransmission according to an embodiment of the present disclosure.

[0015] [Figure 2B] This is a schematic diagram showing an example of HARQ feedback retransmission according to an embodiment of the present disclosure.

[0016] [Figure 2C] This is a schematic diagram illustrating another example of HARQ feedback retransmission according to embodiments of the present disclosure.

[0017] [Figure 3A] This is a schematic diagram illustrating an example of multiplexing HARQ feedback retransmission and initial HARQ feedback transmission within the same PUCCH resource according to an embodiment of the present disclosure.

[0018] [Figure 3B]Schematic diagram showing an exemplary multiplexed type 1 HARQ codebook including sub-codebooks for HARQ feedback retransmission and the first HARQ feedback, respectively.

[0019] [Figure 3C] Schematic diagram showing an exemplary multiplexed type 1 HARQ codebook according to an embodiment of the present disclosure.

[0020] [Figure 4A] Schematic diagram showing another example of multiplexing HARQ feedback retransmission and the first HARQ feedback transmission in the same PUCCH resource according to an embodiment of the present disclosure.

[0021] [Figure 4B] Schematic diagram showing an exemplary multiplexed type 2 HARQ codebook according to an embodiment of the present disclosure.

[0022] [Figure 4C] Schematic diagram showing an example of multiplexing HARQ feedback retransmission in the same PUCCH resource according to an embodiment of the present disclosure.

[0023] [Figure 5] Schematic diagram showing an example of SPS HARQ feedback retransmission according to an embodiment of the present disclosure.

[0024] [Figure 6] Schematic diagram showing another example of SPS HARQ feedback retransmission according to an embodiment of the present disclosure.

[0025] [Figure 7] Schematic diagram showing the process of HARQ feedback retransmission according to an embodiment of the present disclosure.

[0026] [Figure 8]This figure shows another exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0027] [Figure 9] This figure shows another exemplary communication method implemented in a network device according to some embodiments of the present disclosure.

[0028] [Figure 10] This is a schematic block diagram of an apparatus suitable for realizing the embodiments of the present disclosure.

[0029] In the diagram, identical or similar reference numbers represent identical or similar elements. [Modes for carrying out the invention]

[0030] The principles of this disclosure will now be explained with reference to several embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should be understood as not to imply any limitation on the scope of this disclosure. The disclosures described herein can be implemented in a variety of ways other than those described below.

[0031] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by those skilled in the art.

[0032] As used in this text, the term “terminal device” means any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user devices (UEs), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Things (IoE) devices, machine-type communication (MTC) devices, and in-vehicle devices for V2X communication, where the “X” in V2X represents pedestrians, vehicles or infrastructure / networks, or image acquisition devices such as digital cameras, game devices, music storage and playback devices, or internet-connected home appliances that enable wireless or wired internet access and browsing. The term “terminal device” may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. The term “network device” means a device that can provide or host a cell or coverage on which a terminal device can communicate. Examples of network devices include, but are not limited to, low-power nodes such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmit / receive points (TRP), remote radio units (RRU), radio heads (RH), remote radio heads (RRH), femtonodes, and piconodes.

[0033] In one embodiment, a terminal device can be connected to a first network device and a second network device. One of the first and second network devices may be a master node and the other a secondary node. The first and second network devices may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information regarding different RATs may be transmitted to the terminal device from at least one of the first or second network device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information regarding the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of terminal devices set by the second network device may be transmitted from the second network device directly to the terminal devices or via the first network device.

[0034] As used herein, the singular forms “one” and “the foregoing” also include the plural form unless explicitly indicated in the context. The term “including” and its variations should be understood as open-ended terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” Terms such as “first,” “second,” etc., may refer to different or identical subjects. The following may include other explicit and implicit definitions.

[0035] In some examples, values, procedures, or devices are referred to as “best,” “worst,” “highest,” “minimum,” “maximum,” etc. Such descriptions are intended to show that a choice can be made from among many usable functional alternatives, and it should be understood that such a choice does not need to be better, smaller, higher, or otherwise more desirable than other choices.

[0036] As described above, it is desirable that the retransmission of canceled HARQ feedback be supported in the communication system. The trigger for such HARQ feedback retransmission may be implemented in a one-time manner. For example, HARQ feedback retransmission may be triggered by dynamic DL allocation from the gNB. Additionally or alternatively, in the case of SPS transmission, the UE may postpone the transmission of HARQ feedback that conflicts with DL symbols until the next available PUCCH occasion.

[0037] Currently, there is no scheme for the arrangement of PUCCH resources for HARQ feedback retransmissions and PUCCH resources for the initial HARQ feedback transmission (also referred to as the newly transmitted HARQ-ACK) regarding the out-of-order condition of HARQ-ACKs. Furthermore, it is desirable to reduce PUCCH transmissions by supporting efficient multiplexing of retransmitted HARQ-ACKs for DL ​​data transmissions and the initial HARQ-ACKs for other DL data transmissions, which are transmitted within the same HARQ-ACK codebook and in the same PUCCH resource. On the other hand, it is necessary to study the construction of HARQ-ACK codebooks for the initial HARQ-ACK and retransmitted HARQ-ACKs. For this purpose, it is also necessary to design HARQ-ACK codebooks suitable for such HARQ-ACK retransmissions and possible multiplexing.

[0038] Embodiments of this disclosure provide solutions to the above and other potential problems. Generally, an extended HARQ feedback mechanism is provided to facilitate communication between terminal devices and network devices. This mechanism provides a clear definition for out-of-order HARQ-ACK conditions for two PUCCH resources for a retransmitted HARQ-ACK and a newly transmitted HARQ-ACK. This also provides a solution for the UE to determine priority between dynamic SPS HARQ-ACK retransmission triggers and semi-static SPS HARQ-ACK deferral rules. Furthermore, since a HARQ-ACK retransmission for one data transmission may be multiplexed within the same codebook as at least one of the HARQ retransmissions for other data transmissions or the initial HARQ-ACK transmission, fewer PUCCH transmissions can be achieved. Thus, spectral efficiency and system performance can be improved, while overhead for UCI is reduced by providing an improved method for constructing multiplexed HARQ-ACK codebooks.

[0039] The principles and embodiments of this disclosure will be described in detail below with reference to the attached drawings.

[0040] Figure 1 is a schematic diagram of an exemplary communication network 100 that can implement embodiments of the present disclosure. As shown in Figure 1, the communication network 100 may include terminal devices 110 and network devices 120. In some embodiments, the terminal devices 110 may be served by the network devices 120. The number of devices in Figure 1 is given for illustrative purposes only and should be understood as not implying any limitation to the present disclosure. The communication network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing embodiments of the present disclosure.

[0041] As shown in Figure 1, the terminal device 110 may communicate with the network device 120 via a channel such as a wireless communication channel. Communication in the communication network 100 may comply with any appropriate standard, including but not limited to, the Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA®), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), and Machine Type Communication (MTC). Furthermore, communication may be performed according to any generation of communication protocol that is currently known or will be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, and fifth-generation (5G) communication protocols.

[0042] The terminal device 110 may transmit uplink data to the network device 120 via uplink data channel transmission. For example, the uplink data channel transmission may be a PUSCH transmission. Of course, any other suitable format is also possible. In some embodiments, the terminal device 110 may receive downlink data from the network device 120 via downlink data channel transmission. For example, the downlink data channel transmission may be a PDSCH transmission. Of course, any other suitable format is also possible.

[0043] The terminal device 110 may receive a DCI indicating data transmission from the network device 120 via a downlink control channel transmission. For example, the downlink control channel transmission may be a PDCCH transmission. Of course, any other suitable form is also possible.

[0044] The terminal device 110 may transmit UCI, for example, HARQ feedback information, to the network device 120 via uplink channel transmission. For example, the uplink channel transmission may be a PUCCH or PUSCH transmission. Of course, any other suitable form is also possible.

[0045] The network device 120 may provide the terminal device 110 with multiple serving cells (not shown herein), such as a primary cell (PCell), a primary secondary cell (PSCell), a secondary cell (SCell), a special cell (sPCell), and so on. Each serving cell may correspond to a CC. The terminal device 110 can transmit to the network device 120 via CCs. The terminal device 110 may also transmit to the network device 120 via multiple CCs, for example, in the case of carrier aggregation (CA). The network device 120 may schedule downlink data transmissions via different CCs in various ways.

[0046] When the terminal device 110 receives data transmission from the network device 120, it generates and transmits a HARQ-ACK codebook that includes HARQ feedback for the data transmission.

[0047] To better understand the enhanced HARQ feedback mechanism proposed in this disclosure, we refer here to Figure 7. Figure 7 is a schematic diagram showing a HARQ feedback retransmission process 700 according to an embodiment of this disclosure. The process 700 shown in Figure 7 involves a terminal device 110 and a network device 120 as shown in Figure 1. For illustrative purposes, the process 700 will be described with reference to Figure 1. It should be understood that the process 700 may include additional operations not shown, and / or some of the illustrated operations may be omitted, and the scope of this disclosure is not limited in this respect.

[0048] As shown in Figure 7, the network device 120 transmits information to the terminal device 110 indicating a first resource for the first transmission of HARQ feedback for the first data transmission (705). The first data transmission may include a semi-permanent scheduling (SPS) transmission or a dynamically scheduled downlink transmission.

[0049] If the network device 120 determines that the first resource for the first HARQ feedback is canceled by the terminal device 110 (710), the network device 120 sends a first DCI to the terminal device 110 indicating a second resource for retransmitting the first HARQ feedback (715).

[0050] The network device 120 sends a second DCI to the terminal device 110 (720) indicating a third resource for the first transmission of the second HARQ feedback for the second data transmission. The second data transmission is scheduled to occur after the first data transmission, and the priority of the first HARQ feedback is the same as the priority of the second HARQ feedback.

[0051] Generally, it is not assumed that a terminal device in a given cell, for example, terminal device 110, receives a first PDSCH and a second PDSCH that starts after the first PDSCH, the second PDSCH being allocated to send a corresponding HARQ-ACK in a resource that ends before the start of a different resource allocated to send a HARQ-ACK for the first PDSCH, where the two resources are in different slots for associated HARQ-ACK transmissions, and the HARQ-ACKs for the two PDSCHs are associated with the same priority in the HARQ-ACK codebook. This is the so-called out-of-order rule for HARQ feedback transmissions. Therefore, terminal device 110 should not be confused about the resources for the initial HARQ-ACK transmission and the HARQ-ACK retransmission when determining whether the out-of-order HARQ-ACK rule is met.

[0052] In some exemplary embodiments, it is assumed that the third resource is transmitted after the first resource, regardless of whether the third resource precedes or follows the second resource. In these embodiments, when determining whether the out-of-order rule is met for a retransmitted HARQ-ACK transmission for a DL data transmission and the first HARQ-ACK transmission for other DL data transmissions transmitted later, the terminal device 110 may consider the first PUCCH resource (i.e., the first resource) whose first HARQ-ACK transmission was canceled as the resource for the HARQ-ACK retransmission for the out-of-order HARQ-ACK condition. Thus, the out-of-order HARQ-ACK rule is met as long as the first PUCCH resource for the canceled HARQ-ACK for the previous data transmission is transmitted before the PUCCH resource for the first valid HARQ-ACK transmission for the later data transmission.

[0053] In addition or alternatively, in the embodiments described above, when determining whether the out-of-order rule is met for a retransmitted HARQ-ACK transmission for DL ​​data transmission and for another retransmitted HARQ-ACK transmission for other DL data transmissions transmitted later, the terminal device 110 may assume that the PUCCH resource for HARQ-ACK retransmission is triggered and transmitted before the PUCCH resource for HARQ-ACK retransmission for DL ​​data transmitted later.

[0054] Figure 2A is a schematic diagram showing an out-of-order HARQ feedback retransmission 201 according to an embodiment of the present disclosure. As shown in Figure 2A, the network device 120 transmits DCI 211 and PDSCH#1 212, DCI 213 and PDSCH 214, DCI 215 and PDSCH#2 216 to the terminal device 110 in sequence. The initial transmission of HARQ feedback for PDSCH 212 and 214 is expected to be transmitted on PUCCH#1 217 and PUCCH 218. The lower-priority PUCCH#1 217 for the Extended Mobile Broadband (eMBB) PDSCH 212 overlaps with the higher-priority PUCCH 218 for the Ultra-Reliable and Low-Latency Communication (URLLC) PDSCH 214, so the initial transmission of HARQ feedback on PUCCH#1 217 is canceled. Furthermore, the first transmission of HARQ feedback for PDSCH#2 216, which also belongs to the eMBB service, is scheduled to be on PUCCH#2 219. Since network device 120 knows of the cancellation of PUCCH#1 217, network 120 then sends DCI 220 to trigger a HARQ-ACK retransmission on PUCCH#3 221. Upon receiving DCI 220, terminal device 110 determines that PUCCH#1 217 was transmitted before PUCCH#2 219 for PDSCH#2, and that the out-of-order HARQ-ACK rule is met.

[0055] To avoid violating the out-of-order HARQ-ACK rule, network device 120 may select a PUCCH resource that is sent after PUCCH#1 217 in order to send the first HARQ-ACK transmission for PDSCH#2 216. For example, it may select PUCCH#2 219 itself, or any other PUCCH that is sent before PUCCH#2 219. Network device 120 may then send a DCI 220 to indicate PUCCH#2 219.

[0056] In some other exemplary embodiments, the third resource may be assumed to be transmitted after the second resource. Therefore, the out-of-order HARQ-ACK rule is satisfied as long as the PUCCH resource for HARQ-ACK retransmission (i.e., the second resource) is transmitted before the PUCCH resource for the initial HARQ-ACK transmission for a later data transmission. This means that the actual PUCCH resource for HARQ-ACK transmission is used for the out-of-order HARQ-ACK condition.

[0057] In these embodiments, resource determination for HARQ-ACK retransmission performed in the network device 120 may be based on the above rules. Figure 2B is a schematic diagram showing an example of HARQ feedback retransmission 202 according to an embodiment of the present disclosure. As shown in Figure 2B, the network device 120 transmits DCI 211 and PDSCH#1 212, DCI 213 and PDSCH 214, DCI 215 and PDSCH#2 216 to the terminal device 110 in sequence. The initial transmission of HARQ feedback for PDSCH 212 and 214 is expected to be transmitted on PUCCH#1 217 and PUCCH 218. Since the low-priority PUCCH#1 217 for eMBB PDSCH 212 overlaps with the high-priority PUCCH 218 for URLLC PDSCH 214, the initial transmission of HARQ feedback on PUCCH#1 217 is canceled. Furthermore, the initial transmission of HARQ feedback for PDSCH#2 216, which also belongs to the eMBB service, is scheduled to occur on PUCCH#2 221. To avoid violating the out-of-order HARQ-ACK rule, network device 120 may select a PUCCH resource that is sent before PUCCH#2 221 in order to retransmit the HARQ-ACK for PDSCH#1 212. For example, it may select PUCCH#2 221 itself, or any other PUCCH that is sent before PUCCH#2 221. Network device 120 may then transmit DCI 220 to indicate PUCCH#2 221.

[0058] In some other exemplary embodiments, to avoid a violation of the out-of-order HARQ-ACK rule, after deciding to cancel HARQ feedback on a PUCCH resource, the network device 120 may immediately trigger a DCI for scheduling a HARQ-ACK retransmission, or before sending a DCI for scheduling other data transmissions. Figure 2C is a schematic diagram showing another example of a HARQ feedback retransmission 203 according to embodiments of the present disclosure.

[0059] As shown in Figure 2C, the network device 120 sequentially transmits DCI 211 and PDSCH#1 212, DCI 213 and PDSCH 214, DCI 215 and PDSCH#2 216 to the terminal device 110. The initial transmission of HARQ feedback for PDSCH 212 and 214 is expected to be transmitted on PUCCH#1 resource 217 and PUCCH resource 218. The lower priority PUCCH#1 217 for eMBB PDSCH 212 overlaps with the higher priority PUCCH 218 for URLLC PDSCH 214, so the initial transmission of HARQ feedback on PUCCH#1 resource 217 is canceled. The network device 120 may then transmit DCI 220 to trigger a HARQ-ACK retransmission before any other DCI (e.g., DCI 215) for scheduling a later PDSCH#216 belonging to the eMBB service. Therefore, the HARQ-ACK retransmission on PUCCH#2 219, as indicated by DCI 220, is inherently earlier than the initial HARQ-ACK transmission on PUCCH#3 221, as indicated by DCI 215.

[0060] In some other embodiments, it is specified that the HARQ-ACK retransmission and the initial HARQ-ACK transmission cannot be multiplexed on a PUCCH resource. For example, if terminal device 110 determines that the second resource and the third resource are identical or overlapping in the time domain, the initial transmission of the second HARQ feedback on the third resource may be canceled. Alternatively, the HARQ-ACK retransmission on the second resource may be canceled. In another example, terminal device 110 does not assume that the HARQ-ACK for a newly scheduled PDSCH is indicated to be transmitted within a slot / subslot for the PUCCH for retransmission. In other words, network device 120 may avoid scheduling the HARQ-ACK retransmission and the initial HARQ-ACK transmission to be on the same PUCCH.

[0061] Upon receiving the information, the first DCI, and the second DCI, the terminal device 110 generates a first HARQ feedback (725). The first HARQ feedback may be included in a HARQ-ACK codebook which may further include at least one more HARQ feedback for other data transmissions. In other words, a HARQ-ACK retransmission may be multiplexed with the initial HARQ-ACK retransmission (e.g., the second HARQ feedback) or additional HARQ-ACK retransmissions.

[0062] Terminal device 110 transmits the first HARQ feedback on the second resource to network device 120 (730). Figure 3A is a schematic diagram showing an example of multiplexing HARQ feedback retransmission and initial HARQ feedback transmission on the same PUCCH resource according to an embodiment of the present disclosure. As shown in Figure 3A, network device 120 transmits DCI 311 and PDSCH 312, DCI 313 and PDSCH 314, DCI 315 and PDSCH 316 to terminal device 110 in sequence. The initial transmission of HARQ feedback for PDSCH 312 and 314 is expected to be scheduled on PUCCH 317 and PUCCH 318. Since the low-priority PUCCH 317 for the HARQ-ACK, at least for eMBB PDSCH 312, overlaps with the high-priority PUCCH 318 for the HARQ-ACK, at least for URLLC PDSCH 314, the initial transmission of HARQ feedback on PUCCH 317 is canceled.

[0063] The network device 120 then transmits a DCI 319 indicating a PUCCH 320 for HARQ-ACK retransmission for PDSCH 312. It further indicates that the initial HARQ-ACK transmission for PDSCH 316 is also transmitted on PUCCH 320. In this case, the terminal device 110 may construct a HARQ-ACK codebook that includes at least the HARQ-ACK retransmission for PDSCH 312 and the initial HARQ-ACK transmission for PDSCH 316. In other words, the retransmitted HARQ-ACK and the initial HARQ-ACK are multiplexed on the same PUCCH 320.

[0064] The HARQ-ACK codebook may be a Type 1 or Type 2 HARQ-ACK codebook and may be constructed in various ways. Figure 3B is a schematic diagram showing an exemplary multiplexed Type 1 HARQ codebook 302, including HARQ-ACK codebooks 320 and 321 for the retransmitted HARQ feedback and the initial HARQ feedback, as shown in Figure 3A. As shown in Figure 3B, the set of K1 values ​​associated with the low-priority PUCCH for the eMBB service is {1,3,5}, and the set of K1 values ​​associated with the high-priority PUCCH for the URLLC service is {1,2}. Table 1 shows an exemplary Time-Domain Resource Allocation (TDRA) list associated with both the low-priority and high-priority PUCCH configured for the terminal device 110. Based on the TIFF2026048929000002.tif42108TDRA list and a set of K1 values, the terminal device 110 may simply generate a first HARQ-ACK codebook 320 for the retransmitted HARQ-ACK on PUCCH 317 and a second HARQ-ACK codebook 321 for the initial HARQ-ACK on PUCCH 325, where the first HARQ-ACK codebook 320 precedes the second HARQ-ACK codebook 321. Each of the HARQ-ACK codebooks 320 and 321 contains a plurality of HARQ bits 321 to 326. The method of constructing the type-1 HARQ-ACK codebook shown in Figure 3B is simple, but it is not very desirable in terms of resource efficiency and system performance. In particular, since some of the DL slots within the HARQ-ACK multiplexing window based on the K1 set and the slots for PUCCH 317 and PUCCH 325 are the same as slots N and N+2, the HARQ-ACK positions for PDSCH occasions in slots N and N+2 are actually generated twice within the multiplexed HARQ-ACK codebook 302. Based on the TDRA list, three PDSCH occasions are generated within one slot, resulting in a total of six unnecessary redundant HARQ bits for slots N and N+2 in the multiplexed HARQ-ACK codebook 302. This method of constructing the HARQ-ACK codebook results in a larger UCI payload that wastes resources and degrades system performance.

[0065] An exemplary embodiment of the present disclosure provides an improved design for a Type 1 HARQ-ACK codebook. Figure 3C is a schematic diagram showing an exemplary multiplexed Type 1 HARQ codebook 303 according to an embodiment of the present disclosure. The HARQ codebook 303 includes HARQ bits 331-334 for the retransmitted HARQ feedback and the initial HARQ feedback, as shown in Figure 3A. The TDRA list and set of K1 values ​​set for the terminal device are the same as in the example shown in Figure 3B. To remove unnecessary redundant HARQ bits, the terminal device 110 may determine a new K1 value for each of the retransmitted HARQ-ACK bits, for example, the K1' value for the retransmitted HARQ-ACK bit for PDSCH 312 is the slot offset between PSDCH 312 and PUCCH 320 newly indicated by the trigger DCI for HARQ-ACK retransmission. In the example shown in Figure 3A, K1'=7. The terminal device 110 then determines a new set of K1 values, namely {1,3,5,7}, based on the union of the K1 value set and the K1' values ​​set by the RRC. Based on the TDRA list and the new set of K1 values, the terminal device 110 may generate a multiplexed HARQ-ACK codebook 303 for the retransmitted HARQ-ACK and the original HARQ-ACK, as shown in Figure 3C. This method of constructing the HARQ-ACK codebook is more efficient because it can reduce the UCI payload.

[0066] The exemplary embodiments of this disclosure also provide improvements to the design of Type 2 HARQ-ACK codebooks. Figure 4A is a schematic diagram showing another example according to embodiments of this disclosure in which a retransmitted HARQ feedback and the initial HARQ feedback are multiplexed on a Type 2 HARQ-ACK codebook and transmitted on the same PUCCH 419. Network device 120 sequentially transmits PDSCH#1 (not shown), DCI 411 and PDSCH#2 412 with t-DAI=2, DCI 413 and PDSCH#3 414 with t-DAI=3, and DCI 415 and PDSCH#4 416 with t-DAI=1 to terminal device 110. Terminal device 110 may not know the scheduling of PDSCH#3 414 because it did not detect DCI 413.

[0067] As shown in Figure 4A, the initial transmission of HARQ feedback for PDSCH#1 (not shown), PDSCH#2 412, and PDSCH#3 414 is expected to be scheduled to occur on PUCCH 417. However, PUCCH 417 may be canceled due to a collision with a higher-priority PUCCH, and the network device 120 may decide that it is necessary to trigger a retransmission for the canceled HARQ-ACK bit on PUCCH 417. In this case, the network device 120 may allocate a new PUCCH 419 to retransmit the canceled HARQ-ACK feedback bit. For example, if the first HARQ-ACK for another PDSCH transmission, e.g., PDSCH#4 416, is also indicated to be transmitted on PUCCH 419 or a PUCCH resource that overlaps with PUCCH 419, the network device 120 may assume that the terminal device 110 multiplexes the HARQ feedback for the retransmitted HARQ-ACK bits for PDSCH#1 to PDSCH#3 and the first HARQ-ACK bit for PDSCH#4 on a Type 2 HARQ-ACK codebook and transmits the HARQ-ACK codebook on PUCCH 419.

[0068] A simple Type 2 HARQ-ACK codebook construction method in terminal device 110 is to place the HARQ-ACK codebook for the retransmitted HARQ-ACK bits after or before the HARQ-ACK codebook for the first HARQ-ACK bits. The counter DAI(c-DAI) value and total DAI(t-DAI) value are counted separately for the two HARQ-ACK codebooks, and each HARQ-ACK codebook is determined based on the corresponding c-DAI and t-DAI. However, if a DCI detection miss occurs, for example, if terminal device 110 fails to detect DCI 413, the multiplexed HARQ-ACK codebook will include two retransmitted HARQ-ACK bits for PDSCH#1 to PDSCH#2 412 and one initial HARQ-ACK bit for PDSCH#4 416. On the other hand, network device 120 still assumes a HARQ-ACK codebook containing HARQ-ACK bits for all four PDSCHs. In other words, terminal device 110 and network device 120 may have different understandings of the HARQ-ACK codebook size and HARQ-ACK bit order for multiplexing the retransmitted HARQ-ACK bits with the initial HARQ-ACK bits. This can prevent network device 120 from correctly decoding the HARQ-ACK codebook, leading to a decrease in the reliability of data transmission.

[0069] To eliminate the size and order uncertainties described above and to improve the design of the HARQ-ACK codebook, in some exemplary embodiments, for two HARQ-ACK codebooks, one for the retransmitted HARQ-ACK and one for the initial HARQ-ACK, the c-DAI value and the t-DAI value may be counted separately or together, and the DCI 418 for triggering the HARQ-ACK retransmission may further include a t-DAI value indicating the total number of HARQ feedback bits in the retransmitted HARQ-ACK and the initial transmitted HARQ-ACK. In the example shown in Figure 4A, t-DAI = 4, i.e., the HARQ-ACK codebook may contain 4 HARQ bits. In some other exemplary embodiments, the DCI 418 may include multiple t-DAI values ​​indicating the number of HARQ feedback bits in the retransmitted and the number of HARQ feedback bits in the initial HARQ-ACK, respectively. The DAI values ​​may be contained in an occupied field or an additional field within the DCI.

[0070] Upon receiving DCI 418, terminal device 110 may construct a Type 2 HARQ-ACK codebook containing four HARQ bits for the multiplexed HARQ feedback retransmission and the initial HARQ feedback transmission. Thus, even if some of the DCI is missing or not successfully decoded, terminal device 110 can determine the size of the HARQ codebook and which DCIs are missing based on the t-DAI from network device 120.

[0071] Figure 4B is a schematic diagram showing an exemplary multiplexed Type 2 HARQ codebook 402 according to an embodiment of the present disclosure. As shown in Figure 4B, the HARQ codebook 402 includes four HARQ bits 421-424, each representing the HARQ feedback for PDSCH#1 (not shown)-PDSCH#4. Since the terminal device 110 cannot decode DCI 413, the HARQ feedback for PDSCH#3 414 is padded with a NACK bit.

[0072] Figure 4C is a schematic diagram illustrating an example of multiplexing HARQ feedback retransmissions on the same PUCCH resource according to an embodiment of the present disclosure. As shown in Figure 4C, the network device 120 transmits PDSCH 441 and 443 to the terminal device 110. The initial HARQ-ACK transmissions for PDSCH 441 and 443 are expected to be triggered on PUCCH 442 and 444. If multiple initial HARQ-ACK transmissions are canceled, for example, if both PUCCH 442 and 444 are canceled, the network device 120 may multiplex the multiple HARQ-ACK retransmissions on the same PUCCH. For example, the network device 120 may transmit DCI 445 indicating PUCCH 346 for scheduling HARQ-ACK retransmissions for PDSCH 441 and 443.

[0073] In this case, DCI 445 may include separate t-DAI values ​​for multiple Type 2 HARQ-ACK codebooks. The t-DAI values ​​may be carried on the extended total DAI field or on several unused fields within the trigger DCI, such as the time-domain resource allocation field, frequency-domain allocation field, HARQ process number field, etc. Even if the DCI with the largest DAI value is missing or cannot be decoded by the terminal device 110, uncertainty about the size of the HARQ-ACK codebooks between the terminal device 110 and the network device 120 can be eliminated, thereby improving the reliability performance of the communication system.

[0074] Process 700 is also applicable to SPS HARQ feedback retransmission. Figure 5 is a schematic diagram showing an example of SPS HARQ feedback retransmission 500 according to an embodiment of the present disclosure. As shown in Figure 5, network device 120 transmits SPS PDSCH 511-513 to terminal device 110. The corresponding first HARQ-ACK transmissions for SPS PDSCH 511-513 are expected to be triggered on the configured authorization PUCCH 521 and 522, and PUCCH 523. However, the first HARQ-ACK transmission for SPS PDSCH 513 on PUCCH 523 is canceled because PUCCH 523 conflicts with a DL symbol.

[0075] In an embodiment where a dynamic DCI instruction triggering an SPS HARQ-ACK retransmission is received from the network device 120, the terminal device 110 may use PUCCH 541, indicated in DCI 531, for the HARQ-ACK retransmission for the SPS PDSCH 513.

[0076] In some other embodiments, the terminal device 110 may determine a PUCCH for HARQ-ACK retransmission for SPS PDSCH 513 based on the SPS HARQ-ACK deferral rule. Specifically, if the SPS HARQ-ACK deferral rule is enabled, the terminal device 110 may find the next available PUCCH resource (e.g., PUCCH 542) for HARQ-ACK retransmission for SPS PDSCH 513.

[0077] In an embodiment where a dynamic DCI instruction to trigger SPS HARQ-ACK retransmission is received and an SPS HARQ-ACK deferral rule is also enabled, resource determination based on the DCI instruction may be specified to have a higher priority than resource determination based on the SPS HARQ-ACK deferral rule. In other words, in this case, the dynamic DCI instruction overrides the SPS HARQ-ACK deferral rule. This provides the gNB with flexibility in controlling SPS HARQ-ACK retransmission. For example, as shown in Figure 5, the PUCCH resource 542 may be determined based on a semi-static SPS HARQ-ACK deferral rule, while the gNB may dynamically trigger the PUCCH resource 542 in advance of the PUCCH resource 542 for SPS HARQ-ACK retransmission to reduce latency, which is advantageous for system performance for SPS HARQ-ACK, particularly for URLLC traffic.

[0078] In embodiments where a dynamic DCI instruction is received and the SPS HARQ-ACK deferral rule is enabled simultaneously, resource determination based on the SPS HARQ-ACK deferral rule may be specified to have a higher priority than resource determination based on the DCI instruction. In this case, if the SPS HARQ-ACK deferral rule is set on the terminal device 110, the network device 120 does not need to send a DCI 531 to schedule the HARQ-ACK retransmission. Thus, it is easy to eliminate uncertainty on the UE side regarding the PUCCH resource determination for the retransmitted SPS HARQ-ACK.

[0079] In some exemplary embodiments, only one of the SPS HARQ-ACK deferral rules and dynamic DCI instructions is enabled, which may be configured by signaling between terminal device 110 and network device 120.

[0080] Figure 6 is a schematic diagram showing another example of an SPS HARQ feedback retransmission 600 according to an embodiment of the present disclosure. As shown in Figure 6, terminal device 110 is configured to have an SPS HARQ-ACK deferral rule, while the PUCCH resource 616 on CC#1 allocated for the first SPS HARQ-ACK transmission for SPS PDSCH 612 conflicts with DL symbol or SSB or CORESET#0.

[0081] In the above case, terminal device 110 may determine that PUCCH resource 616 is unavailable for the initial HARQ-ACK transmission and, based on the SPS HARQ-ACK deferral rule, find the next available PUCCH 619 for the HARQ-ACK retransmission of SPS PDSCS 616.

[0082] Alternatively, if PUSCH resource 626 on CC#2 overlaps with an unavailable PUCCH resource 616, the terminal device 110 may multiplex the HARQ-ACK transmission for SPS PDSCH 613 on PUSCH 626 on CC#2, rather than delaying the HARQ-ACK transmission for SPS PDSCH 613 on PUCCH 619 according to the SPS HARQ-ACK deferral rule. This is advantageous for reducing the delay of SPS HARQ-ACK transmission.

[0083] Embodiments of this disclosure provide solutions to the above and other potential problems. Generally, an extended HARQ feedback mechanism is provided to facilitate communication between terminal devices and network devices. This mechanism provides a clear definition for out-of-order HARQ-ACK conditions for two PUCCH resources for a retransmitted HARQ-ACK and a newly transmitted HARQ-ACK. This also provides a solution for the UE to determine priority between dynamic SPS HARQ-ACK retransmission triggers and semi-static SPS HARQ-ACK deferral rules. Furthermore, since a HARQ-ACK retransmission for one data transmission may be multiplexed within the same codebook as at least one of the HARQ retransmissions for other data transmissions or the initial HARQ-ACK transmission, fewer PUCCH transmissions can be achieved. Thus, spectral efficiency and system performance can be improved, while overhead for UCI is reduced by providing an improved method for constructing multiplexed HARQ-ACK codebooks.

[0084] <Example of implementation of the method> Therefore, embodiments of this disclosure provide communication methods implemented in terminal devices and network devices. These methods will be described below with reference to Figures 8-9.

[0085] Figure 8 shows exemplary communication methods 800 implemented in a terminal device according to some embodiments of the present disclosure. For example, method 800 may be implemented in a terminal device 110 as shown in Figure 1. Method 800 will now be described with reference to Figure 1 for illustrative purposes. It should be understood that method 800 may include additional blocks not shown and / or some of the illustrated blocks may be omitted, and the scope of the present disclosure is not limited in this respect.

[0086] In 810, the terminal device 110 receives information from the network device 120 indicating a first resource for the first transmission of a first hybrid automatic retransmission request (HARQ) feedback for a first data transmission. The first data transmission may include a semi-permanent scheduling (SPS) transmission or a dynamically scheduled downlink transmission.

[0087] At 820, the terminal device 110 receives first downlink control information (DCI) from the network device 120 indicating a second resource for retransmitting the first HARQ feedback.

[0088] At 830, the terminal device 110 receives a second DCI from the network device 120 indicating a third resource for the first transmission of a second HARQ feedback for a second data transmission scheduled to occur after the first data transmission. The priority of the first HARQ feedback is the same as the priority of the second HARQ feedback.

[0089] In some exemplary embodiments, the third resource may be assumed to be sent after the first resource.

[0090] In some exemplary embodiments, the third resource may be assumed to be transmitted after the second resource.

[0091] In some exemplary embodiments, the terminal device 110 may determine that the second resource and the third resource are identical or overlap in the time domain. In this case, the terminal device 110 may cancel the initial transmission of the second HARQ feedback on the third resource.

[0092] In some exemplary embodiments, the terminal device 110 may determine that the second resource and the third resource are identical or overlap in the time domain. In this case, the terminal device 110 may cancel the retransmission of the first HARQ feedback at the second resource.

[0093] At 840, the terminal device 110 transmits a second HARQ feedback to the network device 120 on the third resource.

[0094] In some exemplary embodiments, the terminal device 110 may determine that the second resource and the third resource are identical or overlap in the time domain. In this case, the terminal device 110 may generate a HARQ-ACK codebook in which the first HARQ feedback and the second HARQ feedback are multiplexed within the HARQ-ACK codebook. The terminal device 110 may then transmit the HARQ-ACK codebook in the second resource.

[0095] In some exemplary embodiments, a second resource may be configured for retransmission of at least one third HARQ feedback for at least one third data transmission, and the HARQ-ACK codebook further includes at least one third HARQ feedback.

[0096] In embodiments where the HARQ-ACK codebook is a Type 1 HARQ-ACK codebook, to generate the HARQ-ACK codebook, the terminal device 110 may determine a first K1 value indicating a slot offset between the resource receiving the first data transmission and a second resource. The terminal device 110 may then determine a target K1 value set including the first K1 value and a preset K1 value. A Type 1 HARQ-ACK codebook including at least a first HARQ feedback and a second HARQ feedback may be generated based on the target K1 value set.

[0097] In embodiments where the HARQ-ACK codebook is a type 2 HARQ-ACK codebook, in order to generate the HARQ-ACK codebook, the terminal device 110 may generate a type 2 HARQ codebook that includes at least a first HARQ feedback and a second HARQ feedback, based on a first DCI indicating the total number of HARQ feedback bits to be multiplexed.

[0098] In embodiments where the HARQ-ACK codebook is a type 2 HARQ-ACK codebook, the terminal device 110 may generate a type 2 HARQ codebook based on a first DCI, which includes at least a first HARQ feedback and a second HARQ feedback. In these embodiments, the first DCI may include a first DCI field indicating the number of retransmitted HARQ feedback bits and a second DCI field indicating the number of initial transmitted HARQ feedback bits.

[0099] In some exemplary embodiments, the first HARQ feedback may be included in a Type 2 HARQ-ACK codebook, and the terminal device 110 may receive information indicating a fourth resource for the first transmission of the fourth HARQ feedback for a fourth data transmission. If the instruction from the first DCI indicates that the second resource is for retransmission of at least the first and fourth HARQ feedback, the terminal device 110 may generate a Type 2 HARQ codebook based on the first DCI that includes at least the first and fourth HARQ feedback. In these embodiments, the first DCI may include a first DCI field indicating the number of first HARQ feedback bits to be retransmitted, and another DCI field indicating the number of fourth HARQ feedback bits to be retransmitted. The first and second DCI fields may correspond to a first x number of bits and a second x number of bits in the total DAI field, or to the total DAI field and other indicator fields.

[0100] In an embodiment where the first data transmission is an SPS transmission and an SPS HARQ-ACK deferral rule is set in the terminal device 110, when the first DCI is received, the terminal device 110 may determine that resource determination based on the first DCI has a higher priority than resource determination based on the SPS HARQ-ACK deferral rule.

[0101] Alternatively, in embodiments where the first data transmission is an SPS transmission, resource determination based on the SPS HARQ-ACK deferral rule may have a higher priority than resource determination based on the first DCI. In this case, if the SPS HARQ-ACK deferral rule is set on the terminal device 110, the terminal device 110 may find the next available PUCCH resource based on the SPS HARQ-ACK deferral rule and ignore dynamic DL allocation to trigger an SPS HARQ-ACK retransmission. Then, dynamically triggering a HARQ-ACK retransmission by DCI becomes applicable only to HARQ-ACKs for dynamically scheduled PDSCHs.

[0102] In some exemplary embodiments, only one of the SPS HARQ-ACK deferral rules and dynamic DCI instructions is enabled, which may be configured by signaling between terminal device 110 and network device 120.

[0103] If terminal device 110 is configured to have an SPS HARQ-ACK deferral rule, and the PUCCH resource on CC#1 allocated for SPS HARQ-ACK transmission conflicts with DL symbol / SSB / CORESET#0 as shown in Figures 5-6, then if the PUCCH resource on CC#2 overlaps with the said PUCCH resource, the said PUCCH resource becomes unavailable for HARQ-ACK transmission.

[0104] In some exemplary embodiments, when faced with the above case, terminal device 110 may find the next available PUCCH resource on CC#1 for sending an SPS HARQ-ACK in accordance with the SPS HARQ-ACK deferral rule.

[0105] In some other exemplary embodiments, when faced with the above case, terminal device 110 may multiplex the HARQ-ACK on the PUSCH resource on CC#2 rather than following the SPS HARQ-ACK deferral rule.

[0106] Figure 9 shows an exemplary communication method 900 implemented in a network device according to some embodiments of the present disclosure. For example, method 900 may be implemented in a network device 120 as shown in Figure 1. Method 900 will now be described with reference to Figure 1 for illustrative purposes. It should be understood that method 900 may include additional blocks not shown and / or some of the illustrated blocks may be omitted, and the scope of the present disclosure is not limited in this respect.

[0107] As shown in Figure 9, in block 910, the network device 120 transmits to the terminal device 110 information indicating a first resource for the first transmission of the first HARQ feedback for the first data transmission. For example, the first data transmission may include a semi-permanent scheduling (SPS) transmission or a dynamically scheduled downlink transmission.

[0108] In block 920, the network device 120 determines whether the first resource for the first HARQ feedback is canceled by the terminal device 110.

[0109] If the first resource for the first HARQ feedback is canceled, at 930, the network device 120 sends a first DCI to the terminal device 110 indicating a second resource for retransmitting the first HARQ feedback.

[0110] In some exemplary embodiments, a second resource may be configured for retransmission of at least one third HARQ feedback for at least one third data transmission, and the HARQ-ACK codebook further includes at least one third HARQ feedback.

[0111] At 940, the network device 120 sends a second DCI to the terminal device 110 indicating a third resource for the first transmission of a second HARQ feedback for a second data transmission scheduled to occur after the first data transmission. The priority of the first HARQ feedback is the same as the priority of the second HARQ feedback.

[0112] In some exemplary embodiments, the third resource may be assumed to be sent after the first resource.

[0113] In some exemplary embodiments, the third resource may be assumed to be transmitted after the second resource.

[0114] At 950, the network device 120 receives the first HARQ feedback from the terminal device 110 on the second resource.

[0115] In some exemplary embodiments, in order to receive a first HARQ feedback, the network device 120 may receive a HARQ-ACK codebook in a second resource, and the first and second HARQ feedbacks are multiplexed within the HARQ-ACK codebook.

[0116] In some exemplary embodiments, the HARQ-ACK codebook may be a Type 1 HARQ-ACK codebook, which is based on a target K1 value set including a first K1 value indicating a slot offset between a resource to which a first data transmission is sent and a second resource, and a preset K1 value.

[0117] In some exemplary embodiments, the HARQ-ACK codebook may be a Type 2 HARQ-ACK codebook, and the first DCI indicates the total number of HARQ feedback bits for at least the first HARQ feedback and the second HARQ feedback.

[0118] In some exemplary embodiments, the HARQ-ACK codebook may be a Type 2 HARQ-ACK codebook, and the first DCI includes a first DCI field indicating the number of retransmitted HARQ feedback bits and a second DCI field indicating the number of initial transmitted HARQ feedback bits.

[0119] In some exemplary embodiments, the first HARQ feedback may be included in a Type 2 HARQ-ACK codebook, the first DCI may indicate that a second resource is set up for retransmission of at least the first HARQ feedback and the fourth HARQ feedback, and the first DCI may include a first DCI field indicating the number of retransmitted HARQ feedback bits. In these embodiments, the network device 120 may further transmit information indicating a fourth resource for the first transmission of the fourth HARQ feedback for the fourth data transmission.

[0120] In embodiments where the first data transmission is an SPS transmission, resource determination based on the first DCI has a higher priority than resource determination based on the SPS HARQ-ACK deferral rule. In other words, in this case, the dynamic DCI instruction overrides the SPS HARQ-ACK deferral rule.

[0121] Alternatively, in embodiments where the first data transmission is an SPS transmission, resource determination based on the SPS HARQ-ACK deferral rule has a higher priority than resource determination based on the first DCI. In this case, if the SPS HARQ-ACK deferral rule is set on the terminal device 110, the network device 120 does not need to send a dynamic DL allocation for scheduling HARQ-ACK retransmission.

[0122] In some exemplary embodiments, only one of the SPS HARQ-ACK deferral rules and dynamic DCI instructions is enabled, which may be configured by signaling between terminal device 110 and network device 120.

[0123] If terminal device 110 is configured to have an SPS HARQ-ACK deferral rule, and the PUCCH resource on CC#1 allocated for SPS HARQ-ACK transmission conflicts with DL symbol / SSB / CORESET#0 as shown in Figures 5-6, then if the PUCCH resource on CC#2 overlaps with the said PUCCH resource, the said PUCCH resource becomes unavailable for HARQ-ACK transmission.

[0124] In some exemplary embodiments, the network device 120 may assume that, when faced with the above case, the terminal device 110 will find the next available PUCCH resource on CC#1 for sending an SPS HARQ-ACK in accordance with the SPS HARQ-ACK deferral rule.

[0125] In some other exemplary embodiments, the network device 120 may assume that, when faced with the above case, the terminal device 110 will multiplex the HARQ-ACK on the PUSCH resource on CC#2 rather than complying with the SPS HARQ-ACK deferral rule.

[0126] An exemplary embodiment of this disclosure provides an extended HARQ feedback mechanism. Based on this mechanism, dynamic out-of-order HARQ-ACK retransmission and SPS HARQ-ACK deferral are supported. Furthermore, a HARQ-ACK retransmission for one data transmission may be multiplexed within the same codebook as at least one of the HARQ retransmissions or the initial HARQ-ACK transmission for other data transmissions, thereby generating fewer redundant bits. This can improve spectral efficiency and system performance while simultaneously reducing UCI overhead.

[0127] <Example of device implementation> Figure 10 is a schematic block diagram of a device 1000 suitable for implementing an embodiment of the present disclosure. Device 1000 can be considered as another exemplary embodiment of the terminal device 110 or network device 120 shown in Figure 1. Therefore, device 1000 can be implemented in or as part of the terminal device 110 or network device 120.

[0128] As illustrated, the device 1000 comprises a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX / RX 1040. The memory 1010 stores at least a portion of the program 1030. The TX / RX 1040 is used for bidirectional communication. The TX / RX 1040 has at least one antenna to facilitate communication, although the access node referred to herein may actually have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between Mobility Management Entities (MMEs) / Access and Mobility Management Functions (AMFs) / SGWs / UPFs and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal devices.

[0129] Program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2 to 9. Embodiments of the present may be implemented by computer software executable by the processor 1010 of the device 1000, by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1010 and memory 1020 may form a processing means 1050 suitable for implementing various embodiments of the present disclosure.

[0130] Memory 1020 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 1020 is shown in device 1000, several physically different memory modules may exist within device 1000. Processor 1010 may be of any type suitable for a local technology network and may include, as non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. Device 1000 may have multiple processors, for example, application-specific integrated circuit chips that are temporally dependent on a clock that synchronizes the main processor.

[0131] In some embodiments, the terminal device comprises a circuit which receives from a network device information indicating a first resource for the initial transmission of a first Hybrid Automatic Retransmission Request (HARQ) feedback for a first data transmission; receives from the network device first downlink control information (DCI) indicating a second resource for retransmitting the first HARQ feedback; receives from the network device second DCI indicating a third resource for the initial transmission of a second HARQ feedback having the same priority as the first HARQ feedback for a second data transmission scheduled to occur after the first data transmission; and configures the network device to transmit the first HARQ feedback on the second resource.

[0132] In some exemplary embodiments, the third resource is assumed to be sent after the first resource.

[0133] In some exemplary embodiments, the third resource is assumed to be transmitted after the second resource.

[0134] In some exemplary embodiments, the circuit may further be configured to cancel the initial transmission of the second HARQ feedback at the third resource, depending on the determination that the second resource and the third resource are identical or overlapping in the time domain.

[0135] In some exemplary embodiments, the circuit may be configured to transmit the first HARQ feedback by generating a HARQ-ACK codebook in which the first HARQ feedback and the second HARQ feedback are multiplexed, and by transmitting the HARQ-ACK codebook at the second resource, based on the determination that the second resource and the third resource are identical or overlapping in the time domain.

[0136] In some exemplary embodiments, a second resource is configured for retransmitting at least one third HARQ feedback for at least one third data transmission, and the HARQ-ACK codebook further includes at least one third HARQ feedback.

[0137] In some embodiments, the HARQ-ACK codebook includes a Type 1 HARQ-ACK codebook, and the circuit may further determine a first K1 value indicating a slot offset between the resource receiving the first data transmission and the second resource, determine a target K1 value set including the first K1 value and a preset K1 value, and generate the Type 1 HARQ-ACK codebook including at least the first HARQ feedback and the second HARQ feedback based on the target K1 value set.

[0138] In some embodiments, the HARQ-ACK codebook includes a Type 2 HARQ-ACK codebook, and the circuit may further be configured to generate a Type 2 HARQ codebook including at least the first HARQ feedback and the second HARQ feedback based on the first DCI indicating the total number of HARQ feedback bits.

[0139] In some embodiments, the HARQ-ACK codebook includes a Type 2 HARQ-ACK codebook, and the circuit may further be configured to generate a Type 2 HARQ codebook including at least the first HARQ feedback and the second HARQ feedback based on the first DCI, which includes a first DCI field indicating the number of retransmitted HARQ feedback bits and a second DCI field indicating the number of initial transmitted HARQ feedback bits.

[0140] In some exemplary embodiments, the first HARQ feedback is included in a Type 2 HARQ-ACK codebook, and the circuit may further receive information indicating a fourth resource for the first transmission of the fourth HARQ feedback for a fourth data transmission, and generate the Type 2 HARQ codebook including at least the first HARQ feedback and the fourth HARQ feedback based on the first DCI, which includes a first DCI field indicating the number of retransmitted HARQ feedback bits, according to instructions from the first DCI indicating that the second resource is for retransmitting at least the first HARQ feedback and the fourth HARQ feedback.

[0141] In some exemplary embodiments, the first data transmission includes a semi-permanent scheduling (SPS) transmission, an SPS HARQ-ACK deferral rule is enabled in the terminal device, and the circuit may further be configured to determine, upon receiving the first DCI, that resource determination based on the first DCI has a higher priority than resource determination based on the SPS HARQ-ACK deferral rule.

[0142] In some embodiments, the network device comprises a circuit which transmits to a terminal device information indicating a first resource for the initial transmission of a first Hybrid Automatic Retransmission Request (HARQ) feedback for a first data transmission; transmits to the terminal device first downlink control information (DCI) indicating a second resource for retransmitting the first HARQ feedback in accordance with a decision that the first resource for the first HARQ feedback is canceled; transmits to the terminal device second DCI indicating a third resource for the initial transmission of a second HARQ feedback having the same priority as the first HARQ feedback for a second data transmission scheduled to occur after the first data transmission; and the terminal device is configured to receive the first HARQ feedback at the second resource.

[0143] In some exemplary embodiments, the third resource is assumed to be sent after the first resource.

[0144] In some exemplary embodiments, the third resource is assumed to be transmitted after the second resource.

[0145] In some exemplary embodiments, the circuit may be configured to receive the first HARQ feedback by receiving a HARQ-ACK codebook in which the first HARQ feedback and the second HARQ feedback are multiplexed at the second resource.

[0146] In some exemplary embodiments, a second resource is configured for retransmitting at least one third HARQ feedback for at least one third data transmission, and the HARQ-ACK codebook further includes at least one third HARQ feedback.

[0147] In some exemplary embodiments, the HARQ-ACK codebook is a Type 1 HARQ-ACK codebook, which is based on a target K1 value set including a first K1 value indicating a slot offset between a resource to which a first data transmission is sent and a second resource, and a preset K1 value.

[0148] In some exemplary embodiments, the HARQ-ACK codebook is a Type 2 HARQ-ACK codebook, and the first DCI indicates the total number of HARQ feedback bits for at least the first HARQ feedback and the second HARQ feedback.

[0149] In some exemplary embodiments, the HARQ-ACK codebook is a Type 2 HARQ-ACK codebook, and the first DCI includes a first DCI field indicating the number of retransmitted HARQ feedback bits and a second DCI field indicating the number of initial transmitted HARQ feedback bits.

[0150] In some exemplary embodiments, the first HARQ feedback is included in a Type 2 HARQ-ACK codebook, the first DCI indicates that the second resource is set up for retransmission of at least the first HARQ feedback and the fourth HARQ feedback, the first DCI includes a first DCI field indicating the number of retransmitted HARQ feedback bits, and the circuit may further be configured to transmit information indicating the fourth resource for the first transmission of the fourth HARQ feedback for the fourth data transmission.

[0151] In some exemplary embodiments, the first data transmission includes a semi-permanent scheduling (SPS) transmission, and the resource determination based on the first DCI has a higher priority than the resource determination based on the SPS HARQ-ACK deferral rule.

[0152] As used herein, the term “circuit” may mean a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of an analog and / or digital hardware circuit and software / firmware. In yet another example, a circuit may be any part of a hardware processor having a digital signal processor, software and one or more memories, which work together to cause a device such as a terminal or network device to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor such as a microprocessor or a part thereof that requires software / firmware for operation, but the software may not be present if it is not required for operation. As used herein, the term “circuit” also includes the implementation of a hardware circuit or one or more processors alone, or a part of a hardware circuit or one or more processors and their (or their) accompanying software and / or firmware.

[0153] Overall, various embodiments of the Disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various embodiments of the Disclosure are illustrated and described using block diagrams, flowcharts, or any other pictorial representation, it should be understood that any blocks, devices, systems, techniques, or methods described herein may be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0154] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed within a device on a real or virtual processor of interest to perform the processes or methods described above with reference to Figures 2 to 9. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or realize a specific abstract data type. In various embodiments, the functions of program modules may be combined or separated among program modules as needed. The machine-executable instructions of a program module may be executed within a local or distributed device. In a distributed device, program modules may reside in both local and remote storage media.

[0155] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the program code may implement the functions / operations specified in the flowcharts and / or block diagrams. The program code may run entirely on a machine, partially on a machine, as an independent software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0156] The program code described above may be implemented on a machine-readable medium, which may be any tangible medium that can contain or store programs used by or associated with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any suitable combination of the aforementioned mediums. More specific examples of machine-readable storage media may include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0157] While the operations have been described in a specific order, it should not be understood that, in order to obtain the desired results, these operations must be performed in the specific order shown, or in a sequential order, or that all of the described operations must be performed. In some cases, multitasking or parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately or in any suitable subcombination in multiple embodiments.

[0158] While this disclosure has been described in language specific to structural features and / or methodological behavior, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A method performed by a terminal device, To determine a first Physical Uplink Control Channel (PUCCH) resource for transmitting first Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, The first PUCCH resource overlaps with a downlink symbol, and the physical uplink shared channel (PUSCH) resource is available earlier than the second PUCCH resource for retransmitting the first HARQ-ACK information, the PUSCH resource transmits the first HARQ-ACK information to the network device, including: method.

2. The second HARQ-ACK information is multiplexed in the PUSCH resource, The priority of the first HARQ-ACK information is the same as the priority of the second HARQ-ACK information. The first HARQ-ACK information is placed after the second HARQ-ACK information. The method according to claim 1.

3. The second PUCCH resource is determined based on semi-permanent scheduling (SPS) HARQ-ACK deferral information. The method according to claim 1.

4. The aforementioned first HARQ-ACK information is for semi-permanent scheduling (SPS) physical downlink shared channel (PDSCH). The method according to claim 1.

5. Means for determining a first physical uplink control channel (PUCCH) resource for transmitting first hybrid automatic retransmission request acknowledgment (HARQ-ACK) information, The system includes, if the first PUCCH resource overlaps with a downlink symbol and the physical uplink shared channel (PUSCH) resource is available earlier than the second PUCCH resource for retransmitting the first HARQ-ACK information, the PUSCH resource provides means for transmitting the first HARQ-ACK information to a network device. Terminal device.

6. The second HARQ-ACK information is multiplexed in the PUSCH resource, The priority of the first HARQ-ACK information is the same as the priority of the second HARQ-ACK information. The first HARQ-ACK information is placed after the second HARQ-ACK information. The terminal device according to claim 5.

7. The second PUCCH resource is determined based on semi-permanent scheduling (SPS) HARQ-ACK deferral information. The terminal device according to claim 5.

8. The aforementioned first HARQ-ACK information is for semi-permanent scheduling (SPS) physical downlink shared channel (PDSCH). The terminal device according to claim 5.

9. Means for determining a first physical uplink control channel (PUCCH) resource for first hybrid automatic retransmission request acknowledgment (HARQ-ACK) information, If the first PUCCH resource overlaps with a downlink symbol, and the physical uplink shared channel (PUSCH) resource is available earlier than the second PUCCH resource for retransmitting the first HARQ-ACK information, the PUSCH resource includes means for receiving the first HARQ-ACK information from a terminal device. Network device.

10. The second HARQ-ACK information is multiplexed in the PUSCH resource, The priority of the first HARQ-ACK information is the same as the priority of the second HARQ-ACK information. The first HARQ-ACK information is placed after the second HARQ-ACK information. The network device according to claim 9.

11. The second PUCCH resource is determined based on semi-permanent scheduling (SPS) HARQ-ACK deferral information. The network device according to claim 9.

12. The aforementioned first HARQ-ACK information is for semi-permanent scheduling (SPS) physical downlink shared channel (PDSCH). The network device according to claim 9.

Images