Method, device and computer storage medium for communication

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer storage media for communication. The method includes: transmitting downlink control information (DCI) from a network device to a terminal device on a first set of physical downlink control channel (PDCCH) candidates for scheduling a physical downlink shared channel (PDSCH), wherein the DCI includes at least one of a counter downlink allocation indicator (DAI) value and a total DAI value; transmitting the PDSCH from the network device to the terminal device; and receiving a hybrid automatic repeat request acknowledgement (HARQ‑ACK) codebook for the PDSCH from the terminal device, wherein the HARQ‑ACK codebook is generated based on at least one of the counter DAI value and the total DAI value and a first configuration of a second set of PDCCH candidates. In this way, a dynamic HARQ‑ACK codebook can be obtained without introducing additional signaling overhead.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and particularly to methods, devices, and computer storage media for communications. Background Art

[0002] In the 3GPP meeting RAN#86, enhancements to support for multiple transmission and reception point (multi-TRP) deployments have been discussed. For example, it has been proposed to identify and specify features to use multi-TRP and / or multi-panel with Release 16 reliability features as a baseline to improve the reliability and robustness of physical channels other than the physical downlink shared channel (PDSCH), such as the physical downlink control channel (PDCCH), the physical uplink shared channel (PUSCH) and / or the physical uplink control channel (PUCCH). It has also been proposed to identify and specify features to enable inter-cell multi-TRP operation. It has also been proposed to evaluate and specify enhancements for synchronized multi-TRP transmission and multi-panel reception.

[0003] In 3GPP meetings RAN1#98-99, support for physical downlink control channel (PDCCH) repetition was proposed to improve PDCCH reliability and robustness. This means that downlink control information (DCI) can be transmitted more than once from a network device to a terminal device to improve PDCCH reliability and robustness. If PDCCH repetition is implemented, it is necessary to ensure that the same DCI payload is used for the PDCCH repetitions. Summary of the Invention

[0004] Generally speaking, example embodiments of the present disclosure provide methods, devices, and computer storage media for communications.

[0005] In a first aspect, a method of communication is provided. The method includes: transmitting downlink control information (DCI) from a network device to a terminal device on a first set of physical downlink control channel (PDCCH) candidates for scheduling a physical downlink shared channel (PDSCH), wherein the DCI includes at least one of a counter downlink allocation indicator (DAI) value and a total DAI value; transmitting the PDSCH from the network device to the terminal device; and receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook for the PDSCH from the terminal device, wherein the HARQ-ACK codebook is generated based on at least one of the counter DAI value and the total DAI value and a first configuration of a second set of PDCCH candidates.

[0006] In a second aspect, a method of communication is provided. The method includes: detecting, at a terminal device, downlink control information (DCI) on a first set of physical downlink control channel (PDCCH) candidates from a network device for scheduling a physical downlink shared channel (PDSCH), wherein the DCI includes at least one of a counter downlink allocation indicator (DAI) value and a total DAI value; in response to detecting the DCI on the first set of PDCCH candidates, receiving a PDSCH transmitted from the network device; generating a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook for the PDSCH based on at least one of the counter DAI value and the total DAI value and a first configuration of a second set of PDCCH candidates; and transmitting the HARQ-ACK codebook to the network device.

[0007] In a third aspect, a method of communication is provided. The method includes: transmitting downlink control information (DCI) from a network device to a terminal device on a first set of physical downlink control channel (PDCCH) candidates for scheduling communication between the network device and the terminal device, wherein the DCI includes at least one of offset information for communication and first timing information for communication; and performing communication with the terminal device based on second timing information, wherein the second timing information is determined based on a first configuration of a second set of PDCCH candidates, third timing information corresponding to the DCI on the second set of PDCCH candidates, at least one of the offset information and the first timing information, and a time interval between the first set of PDCCH candidates and the second set of PDCCH candidates.

[0008] In a fourth aspect, a method of communication is provided. The method includes: detecting, at a terminal device, downlink control information (DCI) on a first set of physical downlink control channel (PDCCH) candidates from a network device for scheduling communication between the network device and the terminal device, wherein the DCI includes at least one of offset information for communication and first timing information for communication; and in response to detecting the DCI on the first set of PDCCH candidates, performing communication with the network device based on second timing information, wherein the second timing information is determined based on a first configuration of the second set of PDCCH candidates, third timing information corresponding to the DCI on the second set of PDCCH candidates, at least one of the offset information and the first timing information, and a time interval between the first set of PDCCH candidates and the second set of PDCCH candidates.

[0009] In a fifth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to perform the method according to the first or third aspect of the present disclosure.

[0010] In a sixth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to perform the method according to the second or fourth aspect of the present disclosure.

[0011] In a seventh aspect, a computer-readable medium having instructions stored thereon is provided, wherein when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the first, second, third or fourth aspect of the present disclosure.

[0012] In an eighth aspect, a computer program product is provided which is stored on a computer-readable medium and includes machine-executable instructions, wherein when the machine-executable instructions are executed, the machine executes the method according to the first, second, third or fourth aspect of the present disclosure.

[0013] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in conjunction with the accompanying drawings, in which:

[0015] Figure 1 illustrates an example communication network in which embodiments of the present disclosure may be implemented;

[0016] Figure 2 A signaling diagram illustrating an example communication process according to some embodiments of the present disclosure;

[0017] Figure 3A-Figure 3B illustrates an example of an embodiment of the present disclosure;

[0018] Figure 4A-4B illustrates an example of an embodiment of the present disclosure;

[0019] Figure 5 illustrates an example of an embodiment of the present disclosure;

[0020] Figure 6 illustrates an example of an embodiment of the present disclosure;

[0021] Figure 7 illustrates an example of an embodiment of the present disclosure;

[0022] Figure 8A-8B illustrates an example of an embodiment of the present disclosure;

[0023] Figure 9 illustrates an example of an embodiment of the present disclosure;

[0024] Figures 10A-10B illustrates an example of an embodiment of the present disclosure;

[0025] Figures 11A-11B illustrates an example of an embodiment of the present disclosure;

[0026] Figures 12A-12C illustrates an example of an embodiment of the present disclosure;

[0027] Figure 13 illustrates an example of an embodiment of the present disclosure;

[0028] Figure 14 illustrates an example of an embodiment of the present disclosure;

[0029] Figures 15A-15B illustrates an example of an embodiment of the present disclosure;

[0030] Figure 16 illustrates an example of an embodiment of the present disclosure;

[0031] Figure 17 A signaling diagram illustrating an example communication process according to some embodiments of the present disclosure;

[0032] Figure 18 illustrates an example of an embodiment of the present disclosure;

[0033] Figure 19 illustrates a flow chart of an example method according to some embodiments of the present disclosure;

[0034] Figure 20 illustrates a flow chart of an example method according to some embodiments of the present disclosure;

[0035] Figure 21 illustrates a flow chart of an example method according to some embodiments of the present disclosure;

[0036] Figure 22 a flowchart illustrating an example method according to some embodiments of the present disclosure; and

[0037] Figure 23 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0038] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0039] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described merely for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, rather than to impose any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways in addition to the manner described below.

[0040] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0041] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations should be interpreted as open terms meaning "including but not limited to." The term "based on" should be interpreted as "based at least in part on." The terms "some embodiments" and "one embodiment" should be interpreted as "at least some embodiments." The term "another embodiment" should be interpreted as "at least one other embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other definitions, whether explicit or implicit, may be included below.

[0042] In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among many functional alternatives used, and that such a selection is not necessarily better, lesser, higher, or otherwise preferred over other selections.

[0043] As mentioned above, 3GPP meeting RAN1#98-99 proposed supporting PDCCH repetition to improve PDCCH reliability and robustness. That is, DCI can be repeatedly transmitted from a network device to a terminal device more than once, thereby improving PDCCH reliability and robustness.

[0044] Typically, the DCI format has a DAI field. The DAI field may include 1 or 2 bits to indicate the counter DAI value and / or further include 2 bits to indicate the total DAI value. For example, if a dynamic HARQ-ACK codebook is configured, the DAI field may include only 1 or 2 bits to indicate the counter DAI value. For example, the DCI format may be DCI format 1_0 or DCI format 1_2. The counter DAI value in the DCI format indicates the cumulative number of (multiple) {serving cell, PDCCH monitoring opportunity} pairs for which (multiple) PDSCH repetitions or sounding reference signal (SRS) PDSCH releases associated with the DCI format occur as of the current serving cell and the current PDCCH monitoring opportunity, first in ascending order of the serving cell index, and then in ascending order of the PDCCH monitoring opportunity index. For example, the counter DAI value may be any one of {1, 2, 3, 4}. The total DAI value in the DCI format indicates the total number of (multiple) {serving cell, PDCCH monitoring opportunity} pairs for which (multiple) PDSCH repetitions or SRSPDSCH releases associated with the DCI format have occurred up to the current PDCCH monitoring opportunity, and is updated from PDCCH monitoring opportunity to PDCCH monitoring opportunity. For example, the total DAI value can be any one of {1, 2, 3, 4}.

[0045] The total DAI value and / or counter DAI value indicated in the DAI field of the DCI can determine the number and order of bits in the dynamic HARQ-ACK codebook. The so-called HARQ-ACK codebook refers to the feedback sequence generated for the downlink transmission scheduled by the DCI. However, if PDCCH repetition is implemented, the current 3GPP specifications do not specify how to design the values ​​in the DAI field and how to design the HARQ-ACK codebook.

[0046] Embodiments of the present disclosure provide solutions to the above-mentioned problems and / or one or more other potential problems. According to this solution, PDCCH candidates configured for the same PDSCH scheduling can share the same counter DAI value and the same total DAI value. A dynamic HARQ-ACK codebook can be obtained based on the counter and total DAI values ​​included in the PDCCH candidate without introducing additional signaling overhead.

[0047] In the following, the terms "transmission opportunity", "transmission", "repetition", "reception", "reception opportunity", "monitoring opportunity", "PDCCH monitoring opportunity", "PDCCH transmission opportunity", "PDCCH transmission", "PDCCH candidate", "PDCCH reception opportunity", "PDCCH reception", "search space", "CORESET" and "PDCCH repetition" may be used interchangeably. The terms "feedback position", "HARQ-ACK information location", "HARQ-ACK location", "HARQ-ACK location", "HARQ location", "HARQ location", "feedback position" and "feedback location" may be used interchangeably. In the following, the terms "PDCCH repetition", "repeated PDCCH" and "repeated PDCCH signal", "PDCCH candidates configured for the same scheduling" may be used interchangeably. The terms "feedback sequence," "feedback codebook," "HARQ-ACK codebook," "codebook," "HARQ-ACK information," "HARQ-ACK message," "HARQ message," "HARQ information," "feedback message," and "feedback information" may be used interchangeably. The terms "HARQ-ACK information field," "HARQ-ACK information location," "feedback field," and "feedback location" may be used interchangeably.

[0048] Figure 1 An example communication network 100 in which embodiments of the present disclosure may be implemented is illustrated. The network 100 includes a network device 110 and a terminal device 120 served by the network device 110. The network 100 may provide one or more serving cells to serve the terminal device 120. Carrier aggregation (CA) may be supported in the network 100, in which two or more CCs are aggregated to support a wider bandwidth. For example, in Figure 1 In the embodiment of the present invention, the network device 110 can provide a plurality of serving cells to the terminal device 120, including a primary cell (Pcell) 101 corresponding to a primary CC and at least one secondary cell (Scell) 102 corresponding to at least one secondary CC. It will be understood that the number of network devices, terminal devices, and / or serving cells is for illustrative purposes only and does not impose any limitation on the present disclosure. The network 100 may include any suitable number of network devices, terminal devices, and / or serving cells suitable for implementing the present disclosure.

[0049] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs), portable computers, tablet computers, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, vehicle-mounted devices for V2X communication (where X refers to pedestrians, vehicles, or infrastructure / networks), or image capture devices such as digital cameras, gaming devices, music storage and playback devices, or internet devices that enable wireless or wired Internet access and browsing, etc. For ease of discussion, some embodiments will be described below using UE as an example of terminal device 120.

[0050] As used herein, the term "network equipment" or "base station" (BS) refers to a device that can provide or host a cell or coverage area in which terminal devices can communicate. Examples of network equipment include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), transmit receive point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power nodes such as femto nodes, pico nodes, etc.

[0051] In one embodiment, the terminal device 120 can communicate with the first network device and the second network device ( Figure 1 (not shown) connection. One of the first network device and the second network device may be a primary node, and the other may be a secondary node. The first network device and the second network device 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 may be an eNB and the second RAT device may be a gNB. Information related to different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 120. In one embodiment, the first information may be transmitted from the first network device to the terminal device 120, and the second information may be transmitted from the second network device to the terminal device 120 directly or via the first network device. In one embodiment, information related to configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related to reconfiguration of the terminal device configured by the second network device may be transmitted from the second network device to the terminal device directly or via the first network device. This information may be transmitted via any of the following means: radio resource control (RRC) signaling, media access control (MAC) control element (CE), or downlink control information (DCI).

[0052] In the communication network 100, as Figure 1 As shown in , the network device 110 can transmit data and control information to the terminal device 120, and the terminal device 120 can also transmit data and control information to the network device 110. The link from the network device 110 to the terminal device 120 is called a downlink (DL), and the link from the terminal device 120 to the network device 110 is called an uplink (UL).

[0053] In some embodiments, for downlink transmission, the network device 110 may transmit control information via the PDCCH and / or data via the PDSCH to the terminal device 120. In addition, the network device 110 may transmit one or more reference signals (RSs) to the terminal device 120. The RSs transmitted from the network device 110 to the terminal device 120 may also be referred to as "DL RSs." Examples of DL RSs may include, but are not limited to, a demodulation reference signal (DMRS), a channel state information-reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a fine time and frequency tracking reference signal (TRS), and the like.

[0054] In some embodiments, for uplink transmission, the terminal device 120 may transmit control information via the PUCCH and / or data via the PUSCH to the network device 110. In addition, the terminal device 120 may transmit one or more RSs to the network device 110. The RSs transmitted from the terminal device 120 to the network device 110 may also be referred to as "UL RSs." Examples of UL RSs may include, but are not limited to, DMRS, CSI-RS, SRS, PTRS, fine time and frequency TRS, etc.

[0055] Communications in network 100 may conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), Evolved LTE, Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communications (MTC), and the like. Furthermore, communications may be performed according to any generation of communication protocols currently known or 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.

[0056] A network device 110 (such as a gNB) may be equipped with one or more TRPs or antenna panels. As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) that can be used with a network device located at a particular geographic location. For example, a network device may be coupled to multiple TRPs at different geographic locations to achieve better coverage. One or more TRPs may be included in the same serving cell or in different serving cells.

[0057] It will be understood that a TRP may also be a panel, and a panel may also refer to an antenna array (having one or more antenna elements). Although some embodiments of the present disclosure are described with reference to multiple TRPs as examples, these embodiments are only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, rather than to impose any limitation on the scope of the present disclosure. It will be understood that the present disclosure described herein may be implemented in various ways different from those described below.

[0058] like Figure 1 As shown in FIG, for example, the network device 110 can communicate with the terminal device 120 via TRPs 130-1 and 130-2. Hereinafter, TRP 130-1 may also be referred to as a first TRP, and TRP 130-2 may also be referred to as a second TRP. The first TRP 130-1 and the second TRP 130-2 may be included in the same serving cell (such as, for example, Figure 1 1 and 102) or different service cells provided by the network device 110. Although some embodiments of the present disclosure are described with reference to the first TRP 130-1 and the second TRP 130-2 within the same service cell provided by the network device 110, these embodiments are only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, and do not impose any limitation on the scope of the present disclosure. It should be understood that the present disclosure described herein can be implemented in various ways different from those described below.

[0059] Figure 2 FIG2 illustrates a signaling diagram of an example communication process 200 according to some embodiments of the present disclosure. The process 200 involves Figure 1 The network device 110 and the terminal device 120 are shown.

[0060] like Figure 2As shown in , the network device 110 can transmit (201) DCI to the terminal device 120 on multiple PDCCH candidates for scheduling the same PDSCH (e.g., the same data or the same transport block). The DCI transmitted on the multiple PDCCH candidates can indicate the same counter DAI value and / or the same total DAI value. The terminal device 120 can detect (201) DCI on the multiple PDCCH candidates from the network device 110. For example, the terminal device 120 may not detect DCI or may detect DCI on one or more PDCCH candidates. The network device 110 can transmit (202) a PDSCH to the terminal device 120. In response to detecting DCI on one or more PDCCH candidates, the terminal device 120 can decode (202) the PDSCH transmitted from the network device 110. The terminal device 120 may generate (203) a HARQ-ACK codebook for the PDSCH based on at least a first configuration of at least one PDCCH candidate included in the plurality of PDCCH candidates and a counter DAI value and / or a total DAI value and transmit (204) the HARQ-ACK codebook to the network device 110.

[0061] In some embodiments, the network device 110 may transmit to the terminal device 120 a configuration indicating N PDCCH candidates associated / linked with each other, for example, 2≤N≤8. That is, the N PDCCH candidates are configured to schedule at least one of the same PDSCH, the same data, the same transport block(s), the same PUSCH, the same uplink data, the same downlink data, the same uplink transport block(s), the same downlink transport block(s), the same aperiodic CSI-RS transmission / reception, the same aperiodic SRS transmission / reception, the same PUCCH, and the same CSI feedback. In some embodiments, the network device 110 may transmit to the terminal device 120 a configuration indicating a first group of PDCCH candidates associated / linked with a second group of PDCCH candidates. For example, the first group of PDCCH candidates is configured to schedule at least one of the same PDSCH, the same data, the same transport block(s), the same PUSCH, the same uplink data, the same downlink data, the same uplink transport block(s), the same downlink transport block(s), the same aperiodic CSI-RS transmission / reception, the same aperiodic SRS transmission / reception, the same PUCCH, and the same CSI feedback as the second group of PDCCH candidates. For example, the configuration may be transmitted via any one of radio resource control (RRC) signaling, medium access control (MAC) control element (CE), and DCI.

[0062] In some embodiments, N PDCCH candidates may be included in one search space. In some embodiments, the search space may be associated with one control resource set (CORESET), which may be configured with two transmission configuration indication (TCI) states X and Y. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be configured with TCI state X, and (N-N1) PDCCH candidates may be configured with TCI state Y. Alternatively, in some embodiments, the search space may be associated with two CORESETs. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be associated with a first CORESET, and (N-N1) PDCCH candidates may be associated with a second CORESET. In some embodiments, the N1 PDCCH candidates may be represented as a second group of PDCCH candidates. In some embodiments, the N-N1 PDCCH candidates may be represented as a first group of PDCCH candidates.

[0063] In some embodiments, N PDCCH candidates may be included in two search spaces associated with each other. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be associated with a first search space, and (N-N1) PDCCH candidates may be associated with a second search space. In some embodiments, the two search spaces may be associated with one CORESET. Alternatively, in some embodiments, the two search spaces may be associated with two CORESETs, respectively.

[0064] In some embodiments, N1 PDCCH candidates may be represented as a second group of PDCCH candidates. In some embodiments, N-N1 PDCCH candidates may be represented as a first group of PDCCH candidates.

[0065] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, for example, L=1. In some embodiments, the HARQ-ACK codebook for the PDSCH or SPS PDSCH release scheduled by the DCI in the N PDCCH candidates may include the HARQ-ACK information field corresponding to the L candidate reference PDCCHs. That is, the HARQ-ACK information field for the PDSCH or SPS PDSCH release scheduled by the DCI in any one of the NL non-reference PDCCH candidates may be the same as the HARQ-ACK information field generated for the PDSCH or SPS PDSCH release scheduled by the DCI in the corresponding one of the L reference PDCCH candidates. In other words, for a PDSCH or SPS PDSCH release scheduled by any of the NL PDCCH candidates in the search space and / or CORESET, the HARQ-ACK information field may be generated based on the timing information (e.g., the start and / or end symbols of the PDCCH monitoring opportunity) of the corresponding one of the L reference PDCCH candidates in the associated / linked search space and / or CORESET and the counter DAI value and / or the total DAI value. In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may share the same counter DAI value and the same total DAI value. In some embodiments, the L reference PDCCH candidates may include the first PDCCH candidate, or the first linked PDCCH candidate in the search space and / or CORESET (e.g., the first one). Alternatively, the L reference PDCCH candidates may include the last PDCCH candidate, or the last linked PDCCH candidate in the search space and / or CORESET (e.g., the last one). Alternatively, the L reference PDCCH candidates may include configured PDCCH candidates, or PDCCH candidates configured on the search space and / or CORESET (e.g., via any one of RRC signaling, MAC CE, and DCI). In some embodiments, the HARQ-ACK codebook for the PDSCH or SPS PDSCH release scheduled by the DCI in the NL or in the first set of PDCCH candidates may be generated based on at least one of the counter DAI value and the total DAI value and the configuration of the L or first set of PDCCH candidates.

[0066] In some embodiments, L PDCCH candidates may be denoted as a second group of PDCCH candidates. In some embodiments, NL PDCCH candidates may be denoted as a first group of PDCCH candidates.

[0067] In some embodiments, the configuration of the PDCCH candidate may include at least one of the following: search space information for the PDCCH candidate, CORESET information for the PDCCH candidate, time domain resources for the PDCCH candidate, timing for the PDCCH candidate, PDCCH monitoring opportunity for the PDCCH candidate, time domain resources for the PDCCH monitoring opportunity, timing for the PDCCH monitoring opportunity, time slot for the PDCCH candidate, time slot for the PDCCH monitoring opportunity, start and / or end symbols for the PDCCH candidate, and the number of symbols for the PDCCH candidate. In some embodiments, the configuration may be transmitted via any one of RRC signaling, MAC CE, and DCI.

[0068] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, for example, L = 1. In some embodiments, the L reference PDCCH candidates may contribute to the determination of the counter DAI value and the total DAI value of the PDCCH candidate, while the NL non-reference PDCCH candidates may not contribute to the determination of the counter DAI value and the total DAI value of the PDCCH candidate.

[0069] In some embodiments, if N PDCCH candidates are configured for the same PDSCH scheduling based on the configuration of (multiple) search spaces, (multiple) CORESETs and / or the association / link between N PDCCH candidates, a HARQ-ACK codebook can be generated based on the configuration of the L reference PDCCH candidates and the counter DAI value and / or the total DAI value in the DCI on any one of the N PDCCH candidates. In some embodiments, if PDCCH candidate A and PDCCH candidate B are configured to be associated (e.g., configured for the same PDSCH scheduling). In some embodiments, a HARQ-ACK codebook for the PDSCH or SPS / DSCH release scheduled in the DCI on PDCCH candidate B can be generated based on the counter DAI value and / or the total DAI value and the configuration of PDCCH candidate A. For example, PDCCH candidate A and PDCCH candidate B can share the same counter DAI value and the same total DAI value. For example, only PDCCH candidate A may contribute to the counting of the counter DAI value and the total DAI value of the PDCCH candidate, while PDCCH candidate B may not contribute to the counting of the counter DAI value and the total DAI value of the PDCCH candidate. In some embodiments, a HARQ-ACK codebook for a PDSCH or SPS PDSCH release scheduled by at least one of PDCCH candidate A and PDCCH candidate B may be generated based on the counter DAI value and / or the total DAI value and the configuration of PDCCH candidate A. For example, the configuration of PDCCH candidate A may indicate at least one of a search space, a CORESET, a serving cell index, search space information, CORESET information, a time domain resource, a timing, a PDCCH monitoring opportunity, a time domain resource for a PDCCH monitoring opportunity, a timing for a PDCCH monitoring opportunity, a time slot, a time slot of a sequential PDCCH monitoring opportunity, a start and / or end symbol, the number of symbols, and a CORESETPoolIndex configured for PDCCH candidate A. For example, a HARQ-ACK codebook for PDSCH or SPS PDSCH release scheduled by at least one of PDCCH candidate A and PDCCH candidate B may be generated without considering the counter DAI value and / or the total DAI value in PDCCH candidate B.

[0070] Figure 3A An example of such an embodiment is illustrated. Figure 3A PDCCH candidates 311, 312, ... 318 are shown. Each PDCCH candidate 311, 312, ... 318 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 3AAs shown in FIG, PDCCH candidates 311 and 314 are associated with TRP 130-1 and serving cell 101. PDCCH candidates 312 and 316 are associated with TRP 130-2 and serving cell 101. PDCCH candidates 313 and 317 are associated with TRP 130-1 and serving cell 102. PDCCH candidates 315 and 318 are associated with TRP 130-2 and serving cell 102. PDCCH candidates 312 and 314 are configured for the same PDSCH schedule, i.e., are linked as PDCCH repetitions. Figure 3A A HARQ-ACK codebook 320 is shown for the PDSCHs scheduled by PDCCH candidates 311, 312, ..., 318. The HARQ-ACK codebook 320 includes HARQ-ACK information fields 321, 322, ..., 327. For example, each feedback field includes one or two bits. PDCCH repetitions 312 and 314 correspond to the same HARQ-ACK information field 322, which may be generated based on the configuration of the PDCCH candidate 312 and the counter DAI value and / or total DAI value included in the PDCCH candidate 312.

[0071] In some embodiments, if PDCCH candidate A and PDCCH candidate B are configured for the same PDSCH scheduling, a HARQ-ACK codebook for a PDSCH or SPS PDSCH release scheduled by at least one of PDCCH candidate A and PDCCH candidate B may be generated based on the counter DAI value and / or the total DAI value and the configuration of PDCCH candidate A. For example, if PDCCH candidate A is missed or decoded unsuccessfully but PDCCH candidate B is successfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field in the HARQ-ACK codebook based on the configuration of PDCCH candidate A and the counter DAI value and / or the total DAI value included in PDCCH candidate A. For example, referring to Figure 3A If the PDCCH candidate 312 is missed or decoded unsuccessfully but the PDCCH candidate 314 is successfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field 322 in the HARQ-ACK codebook 320 based on the configuration of the PDCCH candidate 312 and the counter DAI value and / or the total DAI value included in the PDCCH candidate 312.

[0072] Alternatively, in a case where PDCCH candidate A and PDCCH candidate B are not configured for the same PDSCH scheduling, if PDCCH candidate A is missed or decoded unsuccessfully but PDCCH candidate B is successfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field in the HARQ-ACK codebook based on the configuration of PDCCH candidate B and the counter DAI value and / or the total DAI value included in PDCCH candidate B. For example, based on the configuration of other successfully detected PDCCH candidates, for example, the counter DAI values ​​and / or the total DAI values ​​of the other PDCCH candidates, the terminal device 120 may determine that PDCCH candidate B is configured for a different scheduling from that of PDCCH candidate A.

[0073] Figure 3B An example of such an embodiment is illustrated. Figure 3B PDCCH candidates 311, 312, ... 318 are shown. Each PDCCH candidate 311, 312, ... 318 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 3B As shown in FIG, PDCCH candidates 311 and 314 are associated with TRP 130-1 and serving cell 101. PDCCH candidates 312 and 316 are associated with TRP 130-2 and serving cell 101. PDCCH candidates 313 and 317 are associated with TRP 130-1 and serving cell 102. PDCCH candidates 315 and 318 are associated with TRP 130-2 and serving cell 102. Figure 3B Also shown is a HARQ-ACK codebook 320 for the PDSCH scheduled by the PDCCH candidates 311, 312 ... 318. The HARQ-ACK codebook 320 includes HARQ-ACK information fields 321, 322 ... 327. For example, each feedback field includes one bit or two bits. If the PDCCH candidate 312 is missed or decoded unsuccessfully but the PDCCH candidate 314 is successfully decoded by the terminal device 120, the terminal device 120 can determine based on the counter DAI values ​​and / or total DAI values ​​of the other PDCCH candidates 313 and 315 that the PDCCH candidate 314 is configured for a different scheduling than the PDCCH candidate 312. The terminal device 120 can determine the HARQ-ACK information field 324 corresponding to the PDCCH candidate 314 in the HARQ-ACK codebook 320 based on the configuration of the PDCCH candidate 314 and the counter DAI value and / or total DAI value included in the PDCCH candidate 314.

[0074] In some embodiments, the terminal device 120 can determine whether PDCCH candidate A and PDCCH candidate B are configured for the same or different scheduling based on the configuration of other successfully detected PDCCH candidates, such as the counter DAI value and / or total DAI value of other PDCCH candidates.

[0075] Figure 4A and Figure 4B An example of such an embodiment is illustrated. Figure 4A and Figure 4B PDCCH candidates 411, 412, ..., 418 are each shown. Each PDCCH candidate 411, 412, ..., 418 includes a pair of counter DAI values ​​c and total DAI values ​​t, denoted as (c, t), where c and t are integers, e.g., 1≤c≤4 and 1≤t≤4. PDCCH candidates 411 and 415 are associated with TRP 130-1 and serving cell 101. PDCCH candidates 412 and 416 are associated with TRP 130-2 and serving cell 101. PDCCH candidates 413 and 417 are associated with TRP 130-1 and serving cell 102. PDCCH candidates 414 and 418 are associated with TRP 130-2 and serving cell 102. Figure 4A and Figure 4B Also shown is the HARQ-ACK codebook 420 for the PDSCH scheduled by the PDCCH candidates 411, 412...418. Figure 4A As shown in , the terminal device 120 can determine that the PDCCH candidates 411 and 415 are configured for different scheduling based on the counter DAI values ​​and / or the total DAI values ​​of the successfully detected PDCCH candidates 416 to 418, and therefore correspond to different HARQ-ACK information fields 421 and 424 in the HARQ-ACK codebook 420. Figure 4B As shown in , the terminal device 120 can determine that PDCCH candidates 411 and 415 are configured for the same scheduling and therefore correspond to the same HARQ-ACK information field 421 in the HARQ-ACK codebook 420 based on the counter DAI value and / or total DAI value of the successfully detected PDCCH candidates 416~418.

[0076] In some embodiments, if PDCCH candidate A and PDCCH candidate B are configured for the same PDSCH scheduling, a HARQ-ACK codebook for a PDSCH or SPS PDSCH release scheduled by at least one of PDCCH candidate A and PDCCH candidate B may be generated based on the counter DAI value and / or the total DAI value and the configuration of PDCCH candidate A. For example, if PDCCH candidate A is successfully decoded but PDCCH candidate B is missed or unsuccessfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field corresponding to PDCCH candidate A in the HARQ-ACK codebook based on the configuration of the successfully detected PDCCH candidate A and the counter DAI value and / or the total DAI value included in PDCCH candidate A. For example, referring to Figure 3A If the PDCCH candidate 312 is successfully decoded but the PDCCH candidate 314 is missed or unsuccessfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field 322 corresponding to the PDCCH candidate 312 in the HARQ-ACK codebook 320 based on the configuration of the successfully detected PDCCH candidate 312 and the counter DAI value and / or the total DAI value included in the PDCCH candidate 312. For another example, if the PDCCH candidate 315 is missed or unsuccessfully decoded by the terminal device 120, the terminal device 120 may determine the HARQ-ACK information field 324 corresponding to the PDCCH candidate 315 in the HARQ-ACK codebook 320 based on the configuration of the successfully detected PDCCH candidate 315 and the counter DAI value and / or the total DAI value included in the PDCCH candidate 315.

[0077] In some embodiments, when PDCCH candidate A and PDCCH candidate B are not configured for the same PDSCH scheduling or when no DCI is transmitted on the latter PDCCH candidate B, if PDCCH candidate A is successfully decoded but PDCCH candidate B is missed or decoded unsuccessfully by the terminal device 120, the terminal device 120 may determine the HARQ-ACK codebook (e.g., the HARQ-ACK information field corresponding to PDCCH candidate A in the HARQ-ACK codebook) based on the configuration of the successfully detected PDCCH candidate A and the counter DAI value and / or the total DAI value included in PDCCH candidate A. For example, even if no DCI is transmitted on PDCCH candidate B, the terminal device may assume that PDCCH candidate B is configured for different scheduling. For another example, if PDCCH candidate B is configured for a different scheduling than PDCCH candidate A but is not successfully decoded by the terminal device 120, the terminal device 120 may generate a HARQ-ACK codebook based on the configuration of other successfully decoded PDCCH candidates, for example, based on the counter DAI value and / or total DAI value of the other PDCCH candidates.

[0078] Figure 5 An example of such an embodiment is illustrated. Figure 5 PDCCH candidates 511, 512, ... 518 are shown. Each PDCCH candidate 511, 512, ... 518 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 5 As shown in , it is assumed that PDCCH candidates 512 and 514 are not configured for the same PDSCH scheduling or that DCI is not transmitted on PDCCH candidate 514. If PDCCH candidate 512 is successfully decoded but PDCCH candidate 514 is missed by terminal device 120 or decoded unsuccessfully, terminal device 120 may determine the HARQ-ACK information field 522 corresponding to PDCCH candidate 512 in HARQ-ACK codebook 520 based on the configuration of the successfully detected PDCCH candidate 512 and the counter DAI value and / or the total DAI value included in PDCCH candidate 512. If the other PDCCH candidates 511 to 513 and 515 to 518 are successfully decoded by the terminal device 120, based on the configuration of the other PDCCH candidates 511 to 513 and 515 to 518, for example, based on the counter DAI values ​​and / or total DAI values ​​of the other PDCCH candidates 511 to 513 and 515 to 518, the terminal device 120 can generate a HARQ-ACK codebook 520 including a HARQ-ACK information field 524 corresponding to the PDCCH candidate 514.

[0079] In some embodiments, when PDCCH candidate A and PDCCH candidate B are configured for the same PDSCH scheduling, if both PDCCH candidate A and PDCCH candidate B are missed or decoded unsuccessfully, the terminal device 120 can determine the HARQ-ACK codebook based on the counter DAI value and / or total DAI value of the detected PDCCH candidate.

[0080] Figure 6 An example of such an embodiment is illustrated. Figure 6 PDCCH candidates 611, 612, ... 618 are shown. Each PDCCH candidate 611, 612, ... 618 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 6 As shown in , it is assumed that PDCCH candidates 612 and 614 are configured for the same PDSCH scheduling. If both PDCCH candidates 612 and 614 are missed or decoded unsuccessfully but other PDCCH candidates 611, 613, and 615 to 618 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 611, 613, and 615 to 618, such as the counter DAI values ​​and / or total DAI values ​​of the other PDCCH candidates 611, 613, and 615 to 618, the terminal device 120 may generate a HARQ-ACK codebook 620 including a HARQ-ACK information field 622 corresponding to the PDCCH candidate 612. For example, in this case, the value of the HARQ-ACK information field 622 may be NACK.

[0081] In some embodiments, when PDCCH candidate A and PDCCH candidate B are configured for different scheduling, if both PDCCH candidate A and PDCCH candidate B are missed or decoded unsuccessfully, the terminal device 120 may determine the HARQ-ACK codebook based on the counter DAI value and / or total DAI value of the detected PDCCH candidate.

[0082] Figure 7 An example of such an embodiment is illustrated. Figure 7 PDCCH candidates 711, 712, ... 718 are shown. Each PDCCH candidate 711, 712, ... 718 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 7As shown in , it is assumed that PDCCH candidates 712 and 714 are configured for different scheduling. If both PDCCH candidates 712 and 714 are missed or decoded unsuccessfully but other PDCCH candidates 711, 713, and 715 to 718 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 711, 713, and 715 to 718, for example, based on the counter DAI values ​​and / or total DAI values ​​of the other PDCCH candidates 611, 613, and 615 to 618, the terminal device 120 may generate a HARQ-ACK codebook 720 including a HARQ-ACK information field 722 corresponding to the PDCCH candidate 712 and a HARQ-ACK information field 724 corresponding to the PDCCH candidate 714. For example, in this case, the value of the HARQ-ACK information field 722 may be NACK and the value of the HARQ-ACK information field 724 may also be NACK.

[0083] In some embodiments, in the case where PDCCH candidate B is the last PDCCH candidate (for example, if the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate B and does not detect any DCI format in subsequent PDCCH monitoring opportunities), if PDCCH candidate A and PDCCH candidate B are missed or not successfully detected, or if PDCCH candidate A is successfully detected but PDCCH candidate B is missed or not successfully detected, the terminal device 120 may assume that PDCCH candidate B is configured for the same PDSCH scheduling as PDCCH candidate A and generate a HARQ-ACK codebook based on the counter DAI value and / or the total DAI value in the detected PDCCH candidate.

[0084] Figure 8A and Figure 8B An example of such an embodiment is illustrated. Figure 8A and Figure 8B PDCCH candidates 811, 812 ... 814 are shown. Each PDCCH candidate 811, 812 ... 814 comprises a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are integers, eg, 1≤c≤4 and 1≤t≤4.

[0085] exist Figure 8A, it is assumed that PDCCH candidates 812 and 814 are configured for the same PDSCH scheduling. If the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate 814 and does not detect any DCI format in a subsequent PDCCH monitoring opportunity, the terminal device 120 may determine PDCCH candidate 814 as the last PDCCH candidate and may assume that PDCCH candidate 814 is configured for the same PDSCH scheduling as PDCCH candidate 812. If both PDCCH candidates 812 and 814 are missed or decoded unsuccessfully but other PDCCH candidates 811 and 813 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 811 and 813, for example, based on the counter DAI values ​​and / or total DAI values ​​of the PDCCH candidates 811 and 813, the terminal device 120 may generate a HARQ-ACK codebook 820 including a HARQ-ACK information field 822 corresponding to the PDCCH candidates 812 and 814. For example, in this case, the value of the HARQ-ACK information field 822 may be NACK.

[0086] exist Figure 8B , it is assumed that PDCCH candidates 812 and 814 are configured for different scheduling. If the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate 814 and does not detect any DCI format in a subsequent PDCCH monitoring opportunity, the terminal device 120 may determine PDCCH candidate 814 as the last PDCCH candidate and may assume that PDCCH candidate 814 is configured for the same PDSCH scheduling as PDCCH candidate 812. If both PDCCH candidates 812 and 814 are missed or decoded unsuccessfully but other PDCCH candidates 811 and 813 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 811 and 813, for example, based on the counter DAI values ​​and / or total DAI values ​​of the PDCCH candidates 811 and 813, the terminal device 120 may generate a HARQ-ACK codebook 820 including a HARQ-ACK information field 822 corresponding to the PDCCH candidates 812 and 814. For example, in this case, the value of the HARQ-ACK information field 822 may be NACK.

[0087] In some embodiments, if PDCCH candidate B is successfully detected but PDCCH candidate A is missed or not successfully detected (or if PDCCH candidate A is successfully detected), and if the value of the total DAI value in PDCCH candidate B is the same as any PDCCH candidate detected in the same PDCCH monitoring opportunity as PDCCH candidate A, the terminal device 120 can determine the HARQ-ACK information field for PDCCH candidate B based on the configuration of PDCCH candidate A and the counter DAI value and / or total DAI value included in PDCCH candidate B.

[0088] Figure 9 An example of such an embodiment is illustrated. Figure 9 PDCCH candidates 911, 912 ... 918 are shown. Each PDCCH candidate 911, 912 ... 918 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 9 As shown in , in the case where PDCCH candidate 914 is successfully detected but PDCCH candidate 912 is missed or not successfully detected, if the total DAI value in PDCCH candidate 914 is the same as any one of PDCCH candidates 911 and 913 detected in the same PDCCH monitoring opportunity as PDCCH candidate 912, the terminal device 120 can determine the HARQ-ACK information field 922 corresponding to PDCCH candidate 914 in the HARQ-ACK codebook 920 based on the configuration of PDCCH candidate 912 and the counter DAI value and / or total DAI value included in PDCCH candidate 914.

[0089] In some embodiments, if PDCCH candidate B is successfully detected but PDCCH candidate A is missed or not successfully detected (or if PDCCH candidate A is successfully detected), and if the value of the total DAI value in PDCCH candidate B is different from all PDCCH candidates detected in the same PDCCH monitoring opportunity as PDCCH candidate A, the terminal device 120 can determine the HARQ-ACK information field for PDCCH candidate B based on the configuration of PDCCH candidate A and the counter DAI value and / or total DAI value included in PDCCH candidate B.

[0090] Figure 10A and Figure 10B An example of such an embodiment is illustrated. Figure 10A and Figure 10BPDCCH candidates 1011, 1012 ... 1014 are shown. Each PDCCH candidate 1011, 1012 ... 1014 comprises a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are integers, eg, 1≤c≤4 and 1≤t≤4.

[0091] like Figure 10A As shown in , if PDCCH candidate 1014 is successfully detected but PDCCH candidate 1012 is missed or not successfully detected by the terminal device 120, since the total DAI value in PDCCH candidate 1014 is different from all PDCCH candidates 1011 and 1013 detected in the same PDCCH monitoring opportunity as PDCCH candidate 1012, the terminal device 120 can determine the HARQ-ACK information field 1024 corresponding to PDCCH candidate 1014 in the HARQ-ACK codebook 1020 based on the configuration of PDCCH candidate 1014 and the counter DAI value and / or total DAI value included in PDCCH candidate 1014.

[0092] like Figure 10B As shown in , if PDCCH candidates 1012 and 1014 are successfully detected by the terminal device 120, since the total DAI value in PDCCH candidate 1014 is different from that of all PDCCH candidates 1011 to 1013, based on the configuration of PDCCH candidates 1012 and 1014 and the counter DAI value and / or total DAI value included in PDCCH candidates 1012 and 1014, the terminal device 120 can determine the HARQ-ACK information field 1022 corresponding to PDCCH candidate 1012 and the HARQ-ACK information field 1024 corresponding to PDCCH candidate 1014 in the HARQ-ACK codebook 1020.

[0093] In some embodiments, where PDCCH candidate B is the last PDCCH candidate (e.g., if the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate B and does not detect any DCI format in a subsequent PDCCH monitoring opportunity), if PDCCH candidate A and PDCCH candidate B are missed or unsuccessfully detected, or if PDCCH candidate A is successfully detected but PDCCH candidate B is missed or unsuccessfully detected, the terminal device 120 may assume that PDCCH candidate B is configured for a different scheduling than PDCCH candidate A. In this case, the terminal device 120 may retain the HARQ-ACK information field for PDCCH candidate B in the HARQ-ACK codebook, regardless of whether DCI is detected in PDCCH candidate B.

[0094] Figure 11A and Figure 11B An example of such an embodiment is illustrated. Figure 11A and Figure 11B PDCCH candidates 1111, 1112 ... 1114 are shown. Each PDCCH candidate 1111, 1112 ... 1114 comprises a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are integers, eg, 1≤c≤4 and 1≤t≤4.

[0095] exist Figure 11A In the embodiment, it is assumed that PDCCH candidates 1112 and 1114 are configured for the same PDSCH scheduling. If the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate 1114 and does not detect any DCI format in a subsequent PDCCH monitoring opportunity, the terminal device 120 may determine that PDCCH candidate 1114 is the last PDCCH candidate and may assume that PDCCH candidate 1114 is configured for a different scheduling than PDCCH candidate 1112. If both PDCCH candidates 1112 and 1114 are missed or decoded unsuccessfully but the other PDCCH candidates 1111 and 1113 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 1111 and 1113, for example, based on the counter DAI values ​​and / or the total DAI values ​​of the PDCCH candidates 1111 and 1113, the terminal device 120 may generate a HARQ-ACK codebook 1120 including a HARQ-ACK information field 1122 corresponding to the PDCCH candidate 1112. In addition, the terminal device 120 may reserve an additional HARQ-ACK information field 1124 for the PDCCH candidate 1114 at the end of the HARQ-ACK codebook 1120. For example, in this case, the value of the HARQ-ACK information field 1122 and the value of the HARQ-ACK information field 1124 may be NACK.

[0096] exist Figure 11B, it is assumed that PDCCH candidates 1112 and 1114 are configured for different scheduling. If the terminal device 120 does not detect any other DCI format in the same PDCCH monitoring opportunity as PDCCH candidate 1114 and does not detect any DCI format in a subsequent PDCCH monitoring opportunity, the terminal device 120 may determine PDCCH candidate 1114 as the last PDCCH candidate and may assume that PDCCH candidate 1114 is configured for a different scheduling than PDCCH candidate 1112. If both PDCCH candidates 1112 and 1114 are missed or decoded unsuccessfully but the other PDCCH candidates 1111 and 1113 are successfully decoded by the terminal device 120, then based on the configuration of the other PDCCH candidates 1111 and 1113, for example, based on the counter DAI values ​​and / or the total DAI values ​​of the PDCCH candidates 1111 and 1113, the terminal device 120 may generate a HARQ-ACK codebook 1120 including a HARQ-ACK information field 1122 corresponding to the PDCCH candidate 1112. In addition, the terminal device 120 may reserve an additional HARQ-ACK information field 1124 for the PDCCH candidate 1114 at the end of the HARQ-ACK codebook 1120. For example, in this case, the value of the HARQ-ACK information field 1122 and the value of the HARQ-ACK information field 1124 may be NACK.

[0097] In some embodiments, if PDCCH candidate B is successfully detected but PDCCH candidate A is missed or not successfully detected (or if PDCCH candidate A is successfully detected), and if the value of the total DAI value in PDCCH candidate B is the same as any PDCCH candidate detected in the same PDCCH monitoring opportunity as PDCCH candidate A, then the terminal device 120 may determine the HARQ-ACK information field for PDCCH candidate B based on the configuration of PDCCH candidate A and the counter DAI value and / or the total DAI value included in PDCCH candidate B. Alternatively, the terminal device 120 may reserve the HARQ-ACK information field for PDCCH candidate B in the HARQ-ACK codebook.

[0098] Figure 12A 、 Figure 12B and Figure 12C An example of such an embodiment is illustrated. Figure 12A 、 12B 12C show PDCCH candidates 1211, 1212 ... 1214. Each PDCCH candidate 1211, 1212 ... 1214 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are integers, eg, 1≤c≤4 and 1≤t≤4.

[0099] exist Figure 12A , assuming that PDCCH candidates 1212 and 1214 are configured for the same PDSCH scheduling. In a case where PDCCH candidate 1214 is successfully detected but PDCCH candidate 1212 is missed or not successfully detected, if the total DAI value in PDCCH candidate 1214 is the same as any PDCCH candidates 1211 and 1213 detected in the same PDCCH monitoring opportunity as PDCCH candidate 1212, then the terminal device 120 may determine the HARQ-ACK information field 1222 corresponding to PDCCH candidate 1214 in the HARQ-ACK codebook 1220 based on the configuration of PDCCH candidate 1212 and the counter DAI value and / or the total DAI value included in PDCCH candidate 1214. In addition, the terminal device 120 may reserve an additional HARQ-ACK information field 1224 for PDCCH candidate 1214 at the end of the HARQ-ACK codebook 1220. For example, the value 1224 of the HARQ-ACK information field may be NACK in this case.

[0100] exist Figure 12B , assuming that PDCCH candidates 1212 and 1214 are configured for the same PDSCH scheduling. In a case where PDCCH candidate 1214 is successfully detected but PDCCH candidate 1212 is missed or not successfully detected, if the total DAI value in PDCCH candidate 1214 is the same as any PDCCH candidates 1211 and 1213 detected in the same PDCCH monitoring opportunity as PDCCH candidate 1212, the terminal device 120 may reserve an additional HARQ-ACK information field 1224 for PDCCH candidate 1214 at the end of the HARQ-ACK codebook 1220 and indicate HARQ-ACK information for PDCCH candidate 1214 in the reserved HARQ-ACK information field 1224. For example, in this case, the value of the HARQ-ACK information field 1224 may be NACK.

[0101] exist Figure 12C, assuming that PDCCH candidates 1212 and 1214 are configured for different scheduling. In a case where PDCCH candidate 1214 is successfully detected but PDCCH candidate 1212 is missed or not successfully detected, if the total DAI value in PDCCH candidate 1214 is different from all PDCCH candidates 1211 and 1213 detected in the same PDCCH monitoring opportunity as PDCCH candidate 1212, the terminal device 120 may reserve an additional HARQ-ACK information field 1224 for PDCCH candidate 1214 at the end of the HARQ-ACK codebook 1220 and indicate HARQ-ACK information for PDCCH candidate 1214 in the reserved HARQ-ACK information field 1224. For example, in this case, the value of the HARQ-ACK information field 1224 may be NACK.

[0102] In some embodiments, PDCCH candidate A and PDCCH candidate B may be configured for the same PDSCH scheduling, and the HARQ-ACK codebook may include two separate HARQ-ACK information fields for the PDSCH or SPS PDSCH release scheduled by the two PDCCH candidates A and PDCCH candidate B. In some embodiments, the HARQ-ACK codebook may be generated based on the decoding result of the PDSCH and the (multiple) decoding results of the PDCCH in the corresponding (multiple) PDCCH candidates. For example, it is assumed that the HARQ-ACK information field E is used for the PDSCH or SPS PDSCH release scheduled by the DCI in the PDCCH candidate A, and the HARQ-ACK information field F is used for the PDSCH or SPS PDSCH release scheduled by the DCI in the PDCCH candidate B. The value of the HARQ-ACK information field E can be determined based on the decoding result of the PDSCH and the decoding result of the DCI in the PDCCH candidate A. The value of the HARQ-ACK information field F can be determined based on the decoding result of the PDSCH and the decoding result of the DCI in the PDCCH candidate B. For example, if the TB or scheduled PDSCH is decoded unsuccessfully, and / or if both PDCCH candidate A and PDCCH candidate B are missed or decoded unsuccessfully, both HARQ-ACK information fields E and F may have a value of NACK. If the TB or scheduled PDSCH is decoded successfully, and if PDCCH candidate A is successfully detected but PDCCH candidate B is missed or not successfully detected, the HARQ-ACK information field E may have a value of ACK, while the HARQ-ACK information field F may have a value of NACK. If the TB or scheduled PDSCH is decoded successfully, and if PDCCH candidate B is successfully detected but PDCCH candidate A is missed or not successfully detected, the HARQ-ACK information field F may have a value of ACK, while the HARQ-ACK information field E may have a value of NACK.

[0103] Figure 13 An example of such an embodiment is illustrated. Figure 13 PDCCH candidates 1311, 1312, ... 1314 are shown. Each PDCCH candidate 1311, 1312, ... 1314 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 13 In FIG, it is assumed that the PDCCH candidates 1312 and 1314 are configured for the same PDSCH scheduling. The terminal device 120 may generate a HARQ-ACK codebook 1320 including HARQ-ACK information fields 1322 and 1324 corresponding to the PDCCH candidates 1312 and 1314, respectively. For example, Figure 13 As shown in , if the terminal device 120 misses or fails to successfully detect the PDCCH candidate 1312, the value of the HARQ-ACK information field 1322 may be NACK. If the terminal device 120 successfully detects the PDCCH candidate 1314 and the terminal device 120 successfully decodes the PDSCH or TB scheduled by the PDCCH candidate 1314, the value of the HARQ-ACK information field 1322 may be ACK.

[0104] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, for example, L=1. The HARQ-ACK codebook for the PDSCH or SPS PDSCH release scheduled by the DCI in the N PDCCH candidates may include the HARQ-ACK information field corresponding to the L candidate reference PDCCHs. That is, the HARQ-ACK information field for the PDSCH or SPS PDSCH release scheduled by the DCI in any one of the NL non-reference PDCCH candidates may be the same as the HARQ-ACK information field generated for the PDSCH or SPS PDSCH release scheduled by the DCI in the corresponding one of the L reference PDCCH candidates. In other words, for a PDSCH or SPS PDSCH release scheduled by any of the NL PDCCH candidates in the search space and / or CORESET, the HARQ-ACK information field may be generated based on the timing information (e.g., the start and / or end symbols of the PDCCH monitoring opportunity) of the corresponding one of the L reference PDCCH candidates in the associated / linked search space and / or CORESET and the counter DAI value and / or the total DAI value. In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may share the same counter DAI value and the same total DAI value. In some embodiments, the L reference PDCCH candidates may include the first PDCCH candidate, or the first linked PDCCH candidate in the search space and / or CORESET (e.g., the first one). Alternatively, the L reference PDCCH candidates may include the last PDCCH candidate, or the last linked PDCCH candidate in the search space and / or CORESET (e.g., the last one). Alternatively, the L reference PDCCH candidates may include configured PDCCH candidates, or PDCCH candidates configured on the search space and / or CORESET (eg, via any one of RRC signaling, MAC CE, and DCI).

[0105] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may all contribute to the determination of the counter DAI value and the total DAI value of the PDCCH candidate.

[0106] In some embodiments, if N PDCCH candidates are configured for the same PDSCH scheduling based on the configuration of (multiple) search spaces, (multiple) CORESETs and / or the association / link between N PDCCH candidates, a HARQ-ACK codebook can be generated based on the configuration of the L reference PDCCH candidates and their counter DAI values ​​and / or total DAI values. For example, if PDCCH candidate A and PDCCH candidate B are configured for the same PDSCH scheduling, PDCCH candidate A and PDCCH candidate B can share the same counter DAI value and the same total DAI value. For example, PDCCH candidate A and PDCCH candidate B can both contribute to the counting of the counter DAI value and the total DAI value of the PDCCH candidate. A HARQ-ACK codebook for a PDSCH or SPS PDSCH release scheduled by at least one of PDCCH candidate A and PDCCH candidate B can be generated based on the counter DAI value and / or the total DAI value and the configuration of PDCCH candidate A. For example, the configuration of PDCCH candidate A may indicate at least one of the search space, CORESET, serving cell index, and CORESETPoolIndex configured for PDCCH candidate A. For example, the HARQ-ACK codebook may be generated by considering the counter DAI value and / or the total DAI value in PDCCH candidate B.

[0107] Figure 14 An example of such an embodiment is illustrated. Figure 14 PDCCH candidates 1411, 1412, ... 1418 are shown. Each PDCCH candidate 1411, 1412, ... 1418 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 14 , it is assumed that PDCCH candidates 1412 and 1414 are configured for the same PDSCH scheduling, i.e., are linked as PDCCH repetitions. For example, both PDCCH candidates 1412 and 1414 contribute to the counting of the counter DAI values ​​and the total DAI values ​​of PDCCH candidates 1411 to 1418. In this case, PDCCH candidate 1414 may include a pair of counter DAI values ​​and total DAI values ​​(4,1). However, since PDCCH candidates 1412 and 1414 are linked as PDCCH repetitions, the payload of PDCCH candidate 1414 should be the same as the payload of PDCCH candidate 1412. Therefore, as Figure 14As shown in , a pair of counter DAI values ​​and a total DAI value (4, 1) included in the PDCCH candidate 1414 is replaced by a pair of counter DAI values ​​and a total DAI value (2, 3) included in the PDCCH candidate 1412. Based on the pair of counter DAI values ​​and the total DAI value (2, 3) and the configuration of the PDCCH candidate 1412, the terminal device 120 can generate a HARQ-ACK codebook 1420 including a HARQ-ACK information field 1422 corresponding to the PDCCH candidates 1412 and 1414. In addition, the terminal device 120 can reserve an additional HARQ-ACK information field 1423 for the replaced pair of counter DAI values ​​and the total DAI value (4, 1).

[0108] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, for example, L=1. The HARQ-ACK codebook for the PDSCH or SPS PDSCH release scheduled by the DCI in the N PDCCH candidates may include the HARQ-ACK information field corresponding to the L candidate reference PDCCHs. That is, the HARQ-ACK information field for the PDSCH or SPS PDSCH release scheduled by the DCI in any one of the NL non-reference PDCCH candidates may be the same as the HARQ-ACK information field generated for the PDSCH or SPS PDSCH release scheduled by the DCI in the corresponding one of the L reference PDCCH candidates. In other words, for a PDSCH or SPS PDSCH release scheduled by any one of the NL PDCCH candidates in the search space and / or CORESET, a HARQ-ACK information field can be generated based on the timing information of the corresponding one of the L reference PDCCH candidates in the associated / linked search space and / or CORESET (e.g., the start and / or end symbols of the PDCCH monitoring opportunity) and the counter DAI value and / or the total DAI value.

[0109] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may share the same counter DAI value and the same total DAI value. In some embodiments, the L reference PDCCH candidates may include the first PDCCH candidate, or the first linked search space and / or PDCCH candidate in the CORESET (e.g., the first one). Alternatively, the L reference PDCCH candidates may include the last PDCCH candidate, or the last linked search space and / or PDCCH candidate in the CORESET (e.g., the last one). Alternatively, the L reference PDCCH candidates may include a configured PDCCH candidate, or a PDCCH candidate configured on the search space and / or CORESET (e.g., via any one of RRC signaling, MAC CE, and DCI).

[0110] In some embodiments, the counter DAI values ​​and / or total DAI values ​​of the N PDCCH candidates may be counted separately from the other PDCCH candidates. Alternatively or additionally, the HARQ-ACK information fields for the N PDCCH candidates may be generated separately. For example, assume that there may be other K PDCCH repetitions, each repetition is different from all N PDCCH candidates, and the HARQ-ACK information for the PDSCH or SPS PDSCH released by the K PDCCH candidates is in the same PUCCH and / or the same time slot / sub-time slot as the HARQ-ACK information for the PDSCH or SPS PDSCH released by the N PDCCH candidates. In some embodiments, the counter DAI values ​​and / or total DAI values ​​of the K PDCCH candidates are counted separately from the counter DAI values ​​and / or total DAI values ​​of the N PDCCH candidates. In some embodiments, the HARQ-ACK codebook for the N PDCCH candidates (e.g., HARQ-ACK codebook 2) may be generated separately from the HARQ-ACK codebook for the K PDCCH candidates (e.g., HARQ-ACK codebook 1). For example, HARQ-ACK codebook 2 may be appended or multiplexed after HARQ-ACK codebook 1. For another example, HARQ-ACK codebook 2 may be multiplexed before HARQ-ACK codebook 1. In some embodiments, the counter DAI value may be the accumulated number of PDCCH repetition groups, and / or if the total DAI field is present, the total DAI value may be the total number of PDCCH repetition groups.

[0111] In some embodiments, the N PDCCH candidates configured for the same PDSCH scheduling may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, for example, L=1. The HARQ-ACK information field of the PDSCH or SPS PDSCH release scheduled by the DCI in the N PDCCH candidates may be determined based on the L reference PDCCH candidates. That is, the HARQ-ACK information field of the PDSCH or SPS PDSCH release scheduled by the DCI in any one of the NL non-reference PDCCH candidates may be the same as the HARQ-ACK information field generated for the PDSCH or SPS PDSCH release scheduled by the DCI in the corresponding one of the L reference PDCCH candidates. For example, the L reference PDCCH candidates may contribute to the determination of the counter DAI value and the total DAI value of the PDCCH candidate, while the NL non-reference PDCCH candidates may not contribute to the determination of the counter DAI value and the total DAI value of the PDCCH.

[0112] Figure 15A and Figure 15B An example of such an embodiment is illustrated. Figure 15A and Figure 15B PDCCH candidates 1511, 1512 ... 1518 are shown. Each PDCCH candidate 1511, 1512 ... 1518 comprises a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are integers, eg, 1≤c≤4 and 1≤t≤4.

[0113] exist Figure 15A , it is assumed that PDCCH candidates 1512 and 1514 are configured for the same PDSCH scheduling, i.e., are linked as PDCCH repetitions. Each of PDCCH candidates 1511 and 1513 to 1518 is configured for a different scheduling than PDCCH candidates 1512 and 1514. The terminal device 120 may generate a HARQ-ACK codebook (e.g., HARQ-ACK codebook 1) for PDCCH candidates 1511 and 1513 to 1518, which may include HARQ-ACK information fields 1521 to 1527. The terminal device 120 may generate a separate HARQ-ACK codebook (e.g., HARQ-ACK codebook 2) for PDCCH repetitions 1512 and 1514, which may include a HARQ-ACK information field 1528. The terminal device 120 may add the HARQ-ACK codebook generated for PDCCH repetitions 1512 and 1514 to the HARQ-ACK codebook generated for PDCCH candidates 1511 and 1513 to 1518, thereby obtaining Figure 15AThe HARQ-ACK codebook 1520 shown in FIG.

[0114] exist Figure 15B , it is assumed that PDCCH candidates 1512 and 1514 are configured for the same PDSCH scheduling, that is, are linked as a first group of PDCCH repetitions. PDCCH candidates 1515 and 1517 are configured for the same PDSCH scheduling, that is, are linked as a second group of PDCCH repetitions. Each of PDCCH candidates 1511, 1513, 1516 and 1518 is configured for a different scheduling than PDCCH candidates 1512, 1514, 1515 and 1517. The terminal device 120 can generate a HARQ-ACK codebook (e.g., HARQ-ACK codebook 1) for PDCCH candidates 1511, 1513, 1516 and 1518, which may include HARQ-ACK information fields 1521 to 1524. The terminal device 120 may generate a separate HARQ-ACK codebook (e.g., HARQ-ACK codebook 2) for the first group of PDCCH repetitions 1512 and 1514, which may include a HARQ-ACK information field 1525. The terminal device 120 may generate a separate HARQ-ACK codebook (e.g., HARQ-ACK codebook 2) for the second group of PDCCH repetitions 1515 and 1517, which may include a HARQ-ACK information field 1526. The terminal device 120 may append the HARQ-ACK codebooks generated for the first group of PDCCH repetitions 1512 and 1514 and for the second group of PDCCH repetitions 1515 and 1517 after generating the HARQ-ACK codebooks for the PDCCH candidates 1511, 1513, 1516, and 1518, thereby obtaining the following: Figure 15B The HARQ-ACK codebook 1520 shown in FIG.

[0115] In some embodiments, the HARQ-ACK information field in the HARQ-ACK codebook for the PDSCH or SPS PDSCH release scheduled by the N1 PDCCH candidates (e.g., for the same PDSCH scheduling) may be generated based on the PDCCH monitoring occasions of the N1 PDCCH candidates and the counter DAI values ​​and / or total DAI values ​​of the N1 PDCCH candidates. The HARQ-ACK information field for the PDSCH or SPS PDSCH release scheduled by the N-N1 PDCCH candidates (e.g., in the associated search space and / or CORESET) may be retained and may be appended to the HARQ-ACK codebook.

[0116] For example, assuming that there may be K other PDCCH repetitions, each different from all N PDCCH candidates, and the HARQ-ACK information for the PDSCH or SPS PDSCH release scheduled by the K PDCCH candidates is in the same PUCCH and / or the same time slot / subslot as the HARQ-ACK information for the PDSCH or SPS PDSCH release scheduled by the N PDCCH candidates. In some embodiments, the HARQ-ACK information field for the PDSCH or SPS PDSCH release scheduled by N-N1 PDCCH candidates may be retained and appended to the HARQ-ACK codebook generated for the PDSCH or SPS PDSCH release scheduled by N1 and K PDCCH candidates.

[0117] Figure 16 An example of such an embodiment is illustrated. Figure 16 PDCCH candidates 1611, 1612, ... 1618 are shown. Each PDCCH candidate 1611, 1612, ... 1618 includes a pair of counter DAI value c and total DAI value t, denoted as (c, t), where c and t are both integers, such as 1≤c≤4 and 1≤t≤4. Figure 16 , it is assumed that PDCCH candidates 1612 and 1614 are configured for the same PDSCH scheduling, i.e., are linked as PDCCH repetitions. The terminal device 120 may generate a HARQ-ACK codebook 1620 including HARQ-ACK information fields 1621 to 1627 corresponding to PDCCH candidates 1611 to 1613 and 1615 to 1618. For example, based on the configuration of the PDCCH candidate 1612, e.g., the counter DAI value and / or the total DAI value included in the PDCCH candidate 1612, the HARQ-ACK information field 1622 corresponding to the PDCCH candidate 1612 may be determined. The terminal device 120 may retain the HARQ-ACK information field 1628 corresponding to the PDCCH candidate 1614 in the associated search space and / or CORESET. The terminal device 120 may append the HARQ-ACK information field 1628 to the HARQ-ACK codebook 1620 generated for the PDCCH candidates 1611 to 1613 and 1615 to 1618 to obtain Figure 16 The HARQ-ACK codebook 1620 shown in FIG.

[0118] In some embodiments, for the PDCCHs in the N-N1 PDCCH candidates (in the associated search space, CORESET and / or configured with TCI state B), the cyclic redundancy check (CRC) code used for the PDCCH can be scrambled with a specific radio network temporary identifier (RNTI) value (e.g., an RNTI value different from the RNTI value used for the PDCCHs in the N1 PDCCH candidates) or the DMRS sequence of the PDCCH can be generated based on a specific initialization value (e.g., an initialization value different from the initialization value used for the PDCCH in the N1 PDCCH candidate).

[0119] As mentioned above, 3GPP meeting RAN1#98-99 proposed supporting PDCCH repetition to improve PDCCH reliability and robustness. That is, DCI can be repeatedly transmitted from a network device to a terminal device more than once, thereby improving PDCCH reliability and robustness.

[0120] In order to support PDCCH repetition, several additional issues need to be addressed. For example, DCI transmitted via PDCCH can be used to schedule PDSCH transmission to a terminal device, trigger aperiodic channel state information reference signal (A-CSI-RS) transmission to a terminal device, indicate time / frequency resources for aperiodic ZP CSI-RS, schedule PUSCH transmission from a terminal device, trigger aperiodic sounding reference signal (SRS) transmission from a terminal device, trigger aperiodic channel state information (CSI) report transmission from a terminal device, or trigger hybrid automatic repeat request (HARQ) feedback from a terminal device. However, if PDCCH repetition is implemented, it is unclear how to provide an offset indication for PDSCH transmission to a terminal device, A-CSI-RS transmission to a terminal device, indication of time / frequency resources for aperiodic ZP CSI-RS to a terminal device, PUSCH transmission from a terminal device, aperiodic SRS transmission from a terminal device, aperiodic CSI report transmission from a terminal device, or HARQ feedback from a terminal device. Further, if a combination of PDCCH repetitions is expected, the offset value indicated in different PDCCH repetitions should be the same. However, if the offset value indicated in different PDCCH repetitions is the same, it is unclear how to indicate the real-time offset of the corresponding channel / signal transmission and / or reception.

[0121] Embodiments of the present disclosure provide solutions to the aforementioned problems and / or one or more other potential problems. This solution enables both network devices and terminal devices to determine, from PDCCH repetitions, the real-time offset of corresponding transmissions scheduled / triggered by the PDCCH repetitions. Because different physical channel repetitions have the same payload, physical channel repetitions can be combined, thereby improving the reliability and robustness of the physical channels.

[0122] Figure 17 An example signaling diagram illustrating an example process 1700 of communication according to some embodiments of the present disclosure is illustrated. Figure 2 As shown in , process 1700 may involve Figure 1 It should be understood that process 1700 may include additional actions not shown and / or may omit some actions shown, and the scope of the present disclosure is not limited in this respect.

[0123] like Figure 17As shown in , the network device 110 can transmit (1701) DCI to the terminal device 120 on multiple PDCCH candidates for scheduling the same communication between the network device 110 and the terminal device 120. In some embodiments, the multiple PDCCH candidates may include a first group of PDCCH candidates and a second group of PDCCH candidates. For example, the DCI transmitted on the first group of PDCCH candidates may indicate offset information and / or first timing information for communication. For example, the offset information may indicate an offset value K for communication (where K is a non-negative integer, such as 0≤K≤64). For example, the timing information may indicate a scheduling offset between the first group of PDCCH candidates and the communication. Accordingly, the terminal device 120 can detect (1701) DCI on multiple PDCCH candidates from the network device 110. For example, the terminal device 120 may not detect DCI or may detect DCI on one or more PDCCH candidates. The network device 110 may determine (1702) second timing information for communication based on the configuration of the second group of PDCCH candidates, third timing information corresponding to the DCI on the second group of PDCCH candidates, at least one of the offset information and the first timing information, and the time interval between the first group of PDCCH candidates and the second group of PDCCH candidates. In response to detecting the DCI on one of the plurality of PDCCH candidates, the terminal device 120 may determine (1703) second timing information for communication based on the first configuration of the second group of PDCCH candidates, third timing information corresponding to the DCI on the second group of PDCCH candidates, at least one of the offset information and the first timing information, and the time interval between the first group of PDCCH candidates and the second group of PDCCH candidates. Communication is then performed between the network device 110 and the terminal device 120 based on the second timing information (1704). In some embodiments, the communication may include communication of at least one of the following: PDSCH signal, PUSCH signal, PUCCH signal, CSI-RS, non-periodic CSI-RS, zero-power (ZP) CSI-RS, non-periodic ZPCSI-RS, SRS, non-periodic SRS, CSI report, non-periodic CSI report, HARQ feedback (ACK or NACK), etc.

[0124] In some embodiments, the network device 110 may transmit a configuration indicating N PDCCH candidates associated / linked to each other to the terminal device 120, for example, 2≤N≤8. For example, the N PDCCH candidates are configured to schedule at least one of the same PDSCH, the same data or (multiple) same transport blocks, the same PUSCH, the same uplink data, the same downlink data, (multiple) same uplink transport blocks, (multiple) same downlink transport blocks, the same aperiodic CSI-RS transmission / reception, the same aperiodic SRS transmission / reception, the same PUCCH, and the same CSI feedback. For example, the configuration may be transmitted via any one of RRC signaling, MAC CE, and DCI.

[0125] In some embodiments, N PDCCH candidates may be included in one search space. In some embodiments, the search space may be associated with one CORESET, which may be configured with two TCI states X and Y. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be configured with TCI state X, and (N-N1) PDCCH candidates may be configured with TCI state Y. Alternatively, in some embodiments, the search space may be associated with two CORESETs. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be associated with a first CORESET, and (N-N1) PDCCH candidates may be associated with a second CORESET. In some embodiments, the N1 PDCCH candidates may be represented as a second group of PDCCH candidates. In some embodiments, the N-N1 PDCCH candidates may be represented as a first group of PDCCH candidates.

[0126] In some embodiments, N PDCCH candidates may be included in two search spaces associated with each other. For example, N1 PDCCH candidates (where N1 is an integer and 1≤N1≤N) may be associated with a first search space, and (N-N1) PDCCH candidates may be associated with a second search space. In some embodiments, the two search spaces may be associated with one CORESET. Alternatively, in some embodiments, the two search spaces may be associated with two CORESETs, respectively. In some embodiments, N1 PDCCH candidates may be represented as a second group of PDCCH candidates. In some embodiments, N-N1 PDCCH candidates may be represented as a first group of PDCCH candidates.

[0127] In some embodiments, the N PDCCH candidates configured for scheduling the same communication may include L PDCCH candidates serving as reference PDCCH candidates and NL PDCCH candidates serving as non-reference PDCCH candidates, where L is an integer and 1≤L≤N, e.g., L = 1. For example, the N PDCCH candidates configured for scheduling system communications may include PDCCH candidate A and PDCCH candidate B, where PDCCH candidate A serves as the reference PDCCH candidate and PDCCH candidate B serves as the non-reference PDCCH candidate.

[0128] In some embodiments, a scheduling offset for communications scheduled by the PDCCH in PDCCH candidate A (e.g., PDSCH, PUSCH, PUCCH, CSI-RS, SRS communications, etc.) and / or timing for applying a configuration indicated / configured by the PDCCH in PDCCH candidate A (e.g., a TPC command) may be determined based on timing information about PDCCH candidate A and the same offset value K. For example, the timing information about PDCCH candidate A may indicate at least one of the following: a time slot of the PDCCH in PDCCH candidate A; a sub-time slot of the PDCCH in PDCCH candidate A; a starting symbol of the PDCCH in PDCCH candidate A; an ending symbol of the PDCCH in PDCCH candidate A; a starting symbol of a search space, a CORESET, or a monitoring opportunity for PDCCH candidate A; and an ending symbol of a search space, a CORESET, or a monitoring opportunity for PDCCH candidate A.

[0129] In some embodiments, the DCI transmitted on PDCCH candidate B may indicate offset information for communication. For example, the DCI in PDCCH candidate B may indicate an offset value K (where K is a non-negative integer, e.g., 0≤K≤64) for communication. In some embodiments, the scheduling offset for communication scheduled by the PDCCH in PDCCH candidate B (e.g., PDSCH, PUSCH, PUCCH, CSI-RS, SRS communication, etc.) and / or the timing for applying the configuration indicated / configured by the PDCCH in PDCCH candidate B (e.g., TPC command) may be determined based on the timing information about PDCCH candidate A and the offset value K. Alternatively, in some embodiments, a scheduling offset for communications scheduled by the PDCCH in PDCCH candidate B (e.g., PDSCH, PUSCH, PUCCH, CSI-RS, SRS communications, etc.) and / or a timing for applying a configuration indicated / configured by the PDCCH in PDCCH candidate B (e.g., a TPC command) may be determined based on timing information about PDCCH candidate B, an offset value K, and a time difference between PDCCH candidate A and PDCCH candidate B. Alternatively, in some embodiments, a scheduling offset for communications scheduled by the PDCCH in PDCCH candidate B (e.g., PDSCH, PUSCH, PUCCH, CSI-RS, SRS communications, etc.) and / or a timing for applying a configuration indicated / configured by the PDCCH in PDCCH candidate B (e.g., a TPC command) may be determined based on a time interval or time difference between PDCCH candidate A and PDCCH candidate B and an offset value K. For example, the timing information about PDCCH candidate B may indicate at least one of the following: a start symbol of the PDCCH in PDCCH candidate B; an end symbol of the PDCCH in PDCCH candidate B; a start symbol of a search space, CORESET, or monitoring opportunity for PDCCH candidate B; and an end symbol of a search space, CORESET, or monitoring opportunity for PDCCH candidate B. For example, a time interval or a time difference between PDCCH candidate A and PDCCH candidate B may indicate the number of slots, subslots, or symbols between a start or end symbol of the PDCCH / search space / CORESET / monitoring opportunity associated with PDCCH candidate A and a start or end symbol of the PDCCH / search space / CORESET / monitoring opportunity associated with PDCCH candidate B.

[0130] Figure 18 An example of such an embodiment is shown in FIG. Figure 18As shown in , PDCCH candidates 1810-1 and 1810-2 can be configured for scheduling communication 1820. For example, PDCCH candidate 1810-1 can serve as a reference PDCCH candidate and PDCCH candidate 1810-2 can serve as a non-reference PDCCH candidate. For example, the DCI transmitted on PDCCH candidates 1810-1 and 1810-2 can indicate the same offset value K. In some embodiments, if terminal device 120 detects a PDCCH on PDCCH candidate 1810-1, then based on the timing information about PDCCH candidate 1810-1 and the offset value K, terminal device 120 can determine a scheduling offset for communication 1820. In some embodiments, if the terminal device 120 detects a PDCCH on PDCCH candidate 1810-2, the terminal device 120 may determine a scheduling offset for communication 1820 based on the timing information about PDCCH candidate 1810-1 and the offset value K, or based on the timing information about PDCCH candidate 1810-2, the time difference X between PDCCH candidate 1810-1 and PDCCH candidate 1810-2, and the offset value K. The time difference X may indicate the number of slots, subslots, or symbols between a start or end symbol of a PDCCH / search space / CORESET / monitoring opportunity associated with PDCCH candidate 1810-1 and a start or end symbol of a PDCCH / search space / CORESET / monitoring opportunity associated with PDCCH candidate 1810-2.

[0131] In some embodiments, the network device 110 may transmit a configuration indicating a first group of PDCCH candidates (or PDCCH candidate B) associated / linked with a second group of PDCCH candidates (or PDCCH candidate A) to the terminal device 120. For example, the first group of PDCCH candidates and the second group of PDCCH candidates are configured to schedule at least one of the same PDSCH, the same data(s) or the same transport block, the same PUSCH, the same uplink data, the same downlink data, the same uplink transport block(s), the same downlink transport block(s), the same aperiodic CSI-RS transmission / reception, the same aperiodic SRS transmission / reception, the same PUCCH, and the same CSI feedback. For example, the configuration may be transmitted via any one of RRC signaling, MAC CE, and DCI.

[0132] In some embodiments, the first set of PDCCH candidates is different from the second set of PDCCH candidates.In some embodiments, PDCCH candidate A is different from PDCCH candidate B.

[0133] In some embodiments, the DCI in the first group of PDCCH candidates (or PDCCH candidate B) may include at least one of the value of the counter DAI, the value of the total DAI, and the offset value K. In some embodiments, the DCI in the second group of PDCCH candidates (or PDCCH candidate A) may include at least one of the value of the counter DAI, the value of the total DAI, and the offset value K. In some embodiments, there may be timing associated with the DCI in the second group of PDCCH candidates (or PDCCH candidate A).

[0134] In some embodiments, the DCI in the first group of PDCCH candidates (or PDCCH candidate B) may be used to schedule communications. In some embodiments, the communications may include communications of at least one of the following: PDSCH, PUSCH, PUCCH, CSI-RS, aperiodic CSI-RS, zero-power (ZP) CSI-RS, aperiodic ZP CSI-RS, SRS, aperiodic SRS, CSI report, aperiodic CSI report, HARQ feedback (ACK or NACK), power control information, transmit power control (TPC) information, etc.

[0135] In some embodiments, a HARQ-ACK codebook for a PDSCH or SPS PDSCH release scheduled by a DCI in a first group of PDCCH candidates (or PDCCH candidate B) may be generated based on at least one of a counter DAI value and a total DAI value and a configuration of a second group of PDCCH candidates (or PDCCH candidate A). In some embodiments, the configuration of the second group of PDCCH candidates (or PDCCH candidate A) may be a slot index, a subslot index, a symbol index, a start symbol, a start symbol index, an end symbol, an end symbol index, and the number of symbols of the PDCCH / search space / CORESET / monitoring opportunity associated with the second group of PDCCH candidates (or PDCCH candidate A).

[0136] In some embodiments, the timing for communications scheduled by the DCI in the first group of PDCCH candidates (or PDCCH candidate B) may be determined based on a time interval between the first group of PDCCH candidates (or PDCCH candidate B) and the second group of PDCCH candidates (or PDCCH candidate A) and an offset K. In some embodiments, the time interval between the first group of PDCCH candidates (or PDCCH candidate B) and the second group of PDCCH (or PDCCH candidate A) candidates may be the number of slots, subslots, or symbols between a start or end symbol of a PDCCH / search space / CORESET / monitoring opportunity associated with the second group of PDCCH candidates (or PDCCH candidate A) and a start or end symbol of a PDCCH / search space / CORESET / monitoring opportunity associated with the first group of PDCCH candidates (or PDCCH candidate B).

[0137] Figure 19 A flow chart of an example method 1900 according to some embodiments of the present disclosure is illustrated. The method 1900 may be performed in a manner such as Figure 1 and / or Figure 2 It should be understood that method 1900 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0138] At block 1910 , the network device 110 transmits DCI on a first set of PDCCH candidates to the terminal device 120 for scheduling a PDSCH, wherein the DCI includes at least one of a counter DAI value and a total DAI value.

[0139] At block 1920 , the network device 110 transmits a PDSCH to the terminal device.

[0140] At block 1930 , the network device 110 receives a HARQ-ACK codebook for the PDSCH from the terminal device, wherein the HARQ-ACK codebook is generated based on at least one of the counter DAI value and the total DAI value and the first configuration of the second set of PDCCH candidates.

[0141] In some embodiments, the DCI on the first set of PDCCH candidates and the DCI on the second set of PDCCH candidates can be used for the same PDSCH scheduling. Alternatively or additionally, the counter DAI value in the DCI on the first set of PDCCH candidates and the counter DAI value in the DCI on the second set of PDCCH candidates can be the same. Alternatively or additionally, the total DAI value in the DCI on the first set of PDCCH candidates and the total DAI value in the DCI on the second set of PDCCH candidates can be the same.

[0142] In some embodiments, the network device 110 may transmit a second configuration to the terminal device 120 indicating an association between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0143] In some embodiments, the first configuration may indicate at least one of a search space, a CORESET, a serving cell, a slot index, a symbol index, a number of symbols, a starting symbol index, and a CORESET pool configured for the second set of PDCCH candidates.

[0144] In some embodiments, the second group of PDCCH candidates may contribute to the determination of at least one of the counter DAI value and the total DAI value of the PDCCH candidate, and the first group of PDCCH candidates may not contribute to the determination of at least one of the counter DAI value and the total DAI value of the PDCCH candidate.

[0145] In some embodiments, each PDCCH candidate in the first set of PDCCH candidates and the second set of PDCCH candidates may contribute to the determination of at least one of a counter DAI value and a total DAI value of the PDCCH candidate.

[0146] Figure 20 A flow chart of an example method 2000 according to some embodiments of the present disclosure is illustrated. The method 2000 may be performed in a manner such as Figure 1 and / or Figure 2 It should be understood that the method 2000 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0147] At block 2010 , the terminal device 120 detects DCI on a first set of PDCCH candidates from the network device 110 for scheduling a PDSCH, wherein the DCI includes at least one of a counter DAI value and a total DAI value.

[0148] At block 2020 , in response to detecting DCI on the first set of PDCCH candidates, the terminal device 120 receives a PDSCH transmitted from the network device 110 .

[0149] At block 2030 , the terminal device 120 generates a HARQ-ACK codebook for the PDSCH based on at least one of the counter DAI value and the total DAI value and the first configuration of the second set of PDCCH candidates.

[0150] At block 2040 , the terminal device 120 transmits the HARQ-ACK codebook to the network device 110 .

[0151] In some embodiments, the DCI on the first set of PDCCH candidates and the DCI on the second set of PDCCH candidates can be used for the same PDSCH scheduling. Alternatively or additionally, the counter DAI value in the DCI on the first set of PDCCH candidates and the counter DAI value in the DCI on the second set of PDCCH candidates can be the same. Alternatively or additionally, the total DAI value in the DCI on the first set of PDCCH candidates and the total DAI value in the DCI on the second set of PDCCH candidates can be the same.

[0152] In some embodiments, the terminal device 120 may receive a second configuration from the network device 110 indicating an association between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0153] In some embodiments, the first configuration may indicate at least one of a search space, a CORESET, a serving cell, a slot index, a symbol index, a number of symbols, a starting symbol index, and a CORESET pool configured for the second set of PDCCH candidates.

[0154] In some embodiments, the second group of PDCCH candidates may contribute to determining at least one of the counter DAI value and the total DAI value of the PDCCH candidate, and the first group of PDCCH candidates may not contribute to determining at least one of the counter DAI value and the total DAI value of the PDCCH candidate.

[0155] In some embodiments, each PDCCH candidate in the first set of PDCCH candidates and the second set of PDCCH candidates may contribute to the determination of at least one of a counter DAI value and a total DAI value of the PDCCH candidate.

[0156] In some embodiments, the network device 110 may generate a HARQ-ACK codebook in the following manner: determining a HARQ-ACK information field corresponding to the first group of PDCCH candidates in the HARQ-ACK codebook based on at least one of the counter DAI value and the total DAI value and the first configuration of the second group of PDCCH candidates; and in response to detecting DCI on at least one of the first group of PDCCH candidates and the second group of PDCCH candidates, indicating a result of decoding the PDSCH in the HARQ-ACK information field.

[0157] In some embodiments, network device 110 may generate a HARQ-ACK codebook by indicating a negative acknowledgement in a HARQ-ACK information field in response to not detecting DCI on the first and second groups of PDCCH candidates.

[0158] In some embodiments, the network device 110 may generate a HARQ-ACK codebook in the following manner: determining a first HARQ-ACK information field corresponding to the second group of PDCCH candidates in the HARQ-ACK codebook based on at least one of the first configuration of the second group of PDCCH candidates, the counter DAI value, and the total DAI value; determining a second HARQ-ACK information field corresponding to the first group of PDCCH candidates in the HARQ-ACK codebook based on at least one of the counter DAI value and the total DAI value; in response to detecting DCI on the second group of PDCCH candidates, indicating a result of decoding the PDSCH in the first HARQ-ACK information field; and in response to detecting DCI on the first group of PDCCH candidates, indicating a result of decoding the PDSCH in the second HARQ-ACK information field.

[0159] In some embodiments, the network device 110 may generate a HARQ-ACK codebook in the following manner: in response to not detecting DCI on the second set of PDCCH candidates, indicating a negative acknowledgement in the first HARQ-ACK information field; and in response to not detecting DCI on the first set of PDCCH candidates, indicating a negative acknowledgement in the second HARQ-ACK information field.

[0160] In some embodiments, the counter DAI value in the DCI on at least one of the first group of PDCCH candidates and the second group of PDCCH candidates may be the accumulated number of the third group of PDCCH candidates as of the current PDCCH monitoring opportunity. Alternatively or additionally, the total DAI value in the DCI on at least one of the first group of PDCCH candidates and the second group of PDCCH candidates may be the total number of the third group of PDCCH candidates as of the current PDCCH monitoring opportunity. Alternatively or additionally, the third group of PDCCH candidates may include the first group of PDCCH candidates and the second group of PDCCH candidates.

[0161] Figure 21 A flow chart of an example method 2100 according to some embodiments of the present disclosure is illustrated. The method 2100 may be performed in a manner such as Figure 1 and / or Figure 17 It should be understood that the method 2100 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0162] At block 2110 , the network device 110 transmits DCI to the terminal device 120 on the first set of PDCCH candidates for scheduling communication between the network device 110 and the terminal device 120 , wherein the DCI includes at least one of offset information for communication and first timing information for communication.

[0163] In block 2120, the network device 110 performs communication with the terminal device 120 based on the second timing information, wherein the second timing information is determined based on the first configuration of the second group of PDCCH candidates, the third timing information corresponding to the DCI on the second group of PDCCH candidates, the offset information and at least one of the first timing information, and the time interval between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0164] In some embodiments, the DCI on the first set of PDCCH candidates and the DCI on the second set of PDCCH candidates may be used to schedule the same communication.Alternatively or additionally, the offset information in the DCI on the first set of PDCCH candidates and the offset information in the DCI on the second set of PDCCH candidates may be the same.

[0165] In some embodiments, the network device 110 may transmit a second configuration to the terminal device 120 indicating an association between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0166] In some embodiments, the first configuration may indicate at least one of a search space, a CORESET, a serving cell, a slot index, a symbol index, a number of symbols, a starting symbol index, and a CORESET pool configured for the second set of PDCCH candidates.

[0167] In some embodiments, the third timing information may indicate at least one of the following: a time slot for transmitting DCI on the second group of PDCCH candidates; a sub-time slot for transmitting DCI on the second group of PDCCH candidates; a starting symbol for transmitting DCI on the second group of PDCCH candidates; an ending symbol for transmitting DCI on the second group of PDCCH candidates; a starting symbol of a search space, CORESET or monitoring opportunity for the second group of PDCCH candidates; and an ending symbol of a search space, CORESET or monitoring opportunity for the second group of PDCCH candidates.

[0168] Figure 22 A flow chart of an example method 2200 according to some embodiments of the present disclosure is illustrated. The method 2200 may be performed in a manner such as Figure 1 and / or Figure 17 It should be understood that method 2200 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

[0169] At block 2210 , the terminal device 120 detects DCI on a first set of PDCCH candidates from the network device 110 for scheduling communication between the network device and the terminal device 120 , wherein the DCI includes at least one of offset information for communication and first timing information for communication.

[0170] In block 2220, in response to detecting the DCI on the first group of PDCCH candidates, the terminal device 120 performs communication with the network device 110 based on second timing information, wherein the second timing information is determined based on the first configuration of the second group of PDCCH candidates, third timing information corresponding to the DCI on the second group of PDCCH candidates, offset information and at least one of the first timing information, and a time interval between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0171] In some embodiments, the DCI on the first set of PDCCH candidates and the DCI on the second set of PDCCH candidates may be used to schedule the same communication.Alternatively or additionally, the offset information in the DCI on the first set of PDCCH candidates and the offset information in the DCI on the second set of PDCCH candidates may be the same.

[0172] In some embodiments, the terminal device 120 may receive a second configuration from the network device 110 indicating an association between the first group of PDCCH candidates and the second group of PDCCH candidates.

[0173] In some embodiments, the first configuration may indicate at least one of a search space, a CORESET, a serving cell, a slot index, a symbol index, a number of symbols, a starting symbol index, and a CORESET pool configured for the second set of PDCCH candidates.

[0174] In some embodiments, the third timing information may indicate at least one of the following: a time slot for transmitting DCI on the second group of PDCCH candidates; a sub-time slot for transmitting DCI on the second group of PDCCH candidates; a starting symbol for transmitting DCI on the second group of PDCCH candidates; an ending symbol for transmitting DCI on the second group of PDCCH candidates; a starting symbol of a search space, CORESET or monitoring opportunity for the second group of PDCCH candidates; and an ending symbol of a search space, CORESET or monitoring opportunity for the second group of PDCCH candidates.

[0175] Figure 23 is a simplified block diagram of a device 2300 suitable for implementing embodiments of the present disclosure. The device 2300 can be considered as Figure 1 10, terminal device 120 and / or TRP 130 shown in FIG. Figure 1The network device 110, terminal device 120 and / or TRP 130 shown in FIG is implemented at or as at least a part of the network device 110, terminal device 120 and / or TRP 130.

[0176] As shown, device 2300 includes a processor 2310, a memory 2320 coupled to processor 2310, a suitable transmitter (TX) and receiver (RX) 2340 coupled to processor 2310, and a communication interface coupled to TX / RX 2340. Memory 2310 stores at least a portion of program 2330. TX / RX 2340 is used for bidirectional communication. TX / RX 2340 has at least one antenna to facilitate communication, but in practice, the access nodes mentioned in this application may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME) / Serving Gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0177] Assume that the program 2330 includes program instructions that, when executed by the associated processor 2310, enable the device 2300 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1 to 22 The embodiments herein may be implemented by computer software executable by the processor 2310 of the device 2300, or by hardware, or by a combination of software and hardware. The processor 2310 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 2310 and the memory 2320 may form a processing component 2350 suitable for implementing various embodiments of the present disclosure.

[0178] Memory 2320 may be of any type suitable for the local technology network and may be implemented using any appropriate data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 2320 is shown in device 2300, several physically separate memory modules may be present in device 2300. Processor 2310 may be of any type suitable for the local technology network and, by way of non-limiting example, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 2300 may have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0179] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0180] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in program modules, that are executed in a device on a target real or virtual processor to perform the operations described above with reference to Figure 19 、 Figure 20 、 Figure 21 and / or Figure 22 The process or method described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. Machine-executable instructions for program modules can be executed on a local device or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0181] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0182] The program code above can be embodied on a machine-readable medium, which can be any tangible medium that can contain or store a program for use by an instruction execution system, device or equipment or used in combination with it. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium can include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0183] In addition, although each operation is described in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in order, or that all illustrated operations be performed to achieve desired results. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but should be interpreted as describing features that may be specific to a particular embodiment. Some features described in the context of separate embodiments may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0184] Although the disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method performed by a terminal device, comprising: receiving two physical downlink control channel (PDCCH) candidates from a network device, the two PDCCH candidates comprising a first PDCCH candidate and a second PDCCH candidate, the first PDCCH candidate and the second PDCCH candidate being linked as a PDCCH repetition; receiving, from the network device, a physical downlink shared channel (PDSCH) scheduled on the two PDCCH candidates; determining a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook for the PDSCH based on a start time of the first PDCCH candidate, wherein the first PDCCH candidate is earlier than the second PDCCH candidate; as well as Transmitting HARQ-ACK information to the network device based on the HARQ-ACK codebook.

2. The method of claim 1 , wherein determining the HARQ-ACK codebook comprises: The HARQ-ACK codebook is determined based on at least one of a counter downlink allocation indicator (DAI) value and a total DAI value and the start time, wherein the counter DAI value and the total DAI value are detected on at least one PDCCH candidate of the first PDCCH candidate and the second PDCCH candidate.

3. The method according to claim 2, wherein: The counter DAI value detected on the first PDCCH candidate is the same as the counter DAI value detected on the second PDCCH candidate; and / or A total DAI value detected on the first PDCCH candidate is the same as a total DAI value detected on the second PDCCH candidate.

4. The method according to claim 1, further comprising: A configuration indicating that the first PDCCH candidate and the second PDCCH candidate are linked as the PDCCH repetition is received from the network device. The method of claim 1 , wherein the start time is based on a start symbol or a start slot.

6. The method of claim 1 , wherein determining the HARQ-ACK codebook comprises: Determine a HARQ-ACK information field in the HARQ-ACK codebook, wherein the HARQ-ACK information is indicated in the HARQ-ACK information field.

7. The method according to claim 2, wherein: The counter DAI value detected on at least one of the first PDCCH candidate and the second PDCCH candidate is an accumulated number related to PDCCH monitoring opportunities; The total DAI value detected on at least one of the first PDCCH candidate and the second PDCCH candidate is a total number of a set of PDCCH monitoring opportunities, wherein the set of PDCCH monitoring opportunities includes the PDCCH monitoring opportunity.

8. A method performed by a network device, comprising: Transmitting two physical downlink control channel (PDCCH) candidates to a terminal device, the two PDCCH candidates comprising a first PDCCH candidate and a second PDCCH candidate, the first PDCCH candidate and the second PDCCH candidate being linked as a PDCCH repetition; Transmitting a physical downlink shared channel (PDSCH) to the terminal device on the two PDCCH candidates; Receive hybrid automatic repeat request acknowledgement HARQ-ACK information from the terminal device based on the HARQ-ACK codebook, The HARQ-ACK codebook is determined for the PDSCH based on a start time of the first PDCCH candidate, wherein the first PDCCH candidate is earlier than the second PDCCH candidate.

9. The method of claim 8, wherein the HARQ-ACK codebook is further determined based on at least one of a counter downlink allocation indicator (DAI) value and a total DAI value, wherein the counter DAI value and the total DAI value are indicated on at least one of the first PDCCH candidate and the second PDCCH candidate.

10. The method according to claim 9, wherein: The counter DAI value indicated on the first PDCCH candidate is the same as the counter DAI value indicated on the second PDCCH candidate; and / or The total DAI value indicated on the first PDCCH candidate is the same as the total DAI value indicated on the second PDCCH candidate.

11. The method according to claim 8, further comprising: A configuration indicating that the first PDCCH candidate and the second PDCCH candidate are linked as the PDCCH repetition is transmitted to the terminal device.

12. The method of claim 8, wherein the start time is based on a start symbol or a start slot.

13. A terminal device comprising: The processor is configured to enable the terminal device to: receiving two physical downlink control channel (PDCCH) candidates from a network device, the two PDCCH candidates comprising a first PDCCH candidate and a second PDCCH candidate, the first PDCCH candidate and the second PDCCH candidate being linked as a PDCCH repetition; receiving, from the network device, a physical downlink shared channel (PDSCH) scheduled on the two PDCCH candidates; determining a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook for the PDSCH based on a start time of the first PDCCH candidate, wherein the first PDCCH candidate is earlier than the second PDCCH candidate; as well as Transmitting HARQ-ACK information to the network device based on the HARQ-ACK codebook.

14. The terminal device according to claim 13, wherein the processor is further configured to cause the terminal device to: The HARQ-ACK codebook is determined based on at least one of a counter downlink allocation indicator (DAI) value and a total DAI value and the start time, wherein the counter DAI value and the total DAI value are detected on at least one PDCCH candidate of the first PDCCH candidate and the second PDCCH candidate.

15. The terminal device according to claim 13, wherein: The counter DAI value detected on the first PDCCH candidate is the same as the counter DAI value detected on the second PDCCH candidate; and / or A total DAI value detected on the first PDCCH candidate is the same as a total DAI value detected on the second PDCCH candidate.

16. The terminal device according to claim 13, wherein the processor is further configured to cause the terminal device to: A configuration indicating that the first PDCCH candidate and the second PDCCH candidate are linked as the PDCCH repetition is received from the network device. The terminal device according to claim 13 , wherein the start time is based on a start symbol or a start time slot.

Images