WO2023092431A1

WO2023092431A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2023092431A1
Application number: PCT/CN2021/133301
Authority: WO
Inventors: 张轶; 林亚男
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-11-25
Filing date: 2021-11-25
Publication date: 2023-06-01
Also published as: CN117678175A

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device receives first DCI, the first DCI being used for scheduling N PDSCHs, and HARQ-ACK information corresponding to M PDSCHs among the N PDSCHs being fed back on the same PUCCH. The M PDSCHs comprise a first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: a feedback time sequence set, a first subcarrier spacing and a second subcarrier spacing of the terminal device. The first subcarrier spacing is a subcarrier spacing of the first PDSCH or a subcarrier spacing of a first carrier where the first PDSCH is located, and the second subcarrier spacing is a subcarrier spacing of a PUCCH or a subcarrier spacing of a second carrier where the PUCCH is located. The described solution considers one or more factors such as the feedback time sequence set, the first subcarrier spacing associated with the PDSCH and the second subcarrier spacing associated with the PUCCH, and helps to implement the scheduling of multiple PDSCHs by one DCI in a multicarrier scenario.

Description

Wireless communication method, terminal device and network device

technical field

The present application relates to the field of communication technologies, and more specifically, to a wireless communication method, terminal equipment, and network equipment.

Background technique

In related technologies, one piece of downlink control information (DCI) is usually used to schedule one physical downlink shared channel (physical downlink shared channel, PDSCH), or multiple PDSCHs of the same cell (or the same carrier).

At present, many companies hope that the protocol supports one DCI to schedule PDSCHs of multiple carriers. However, in a multi-carrier scenario, there is currently no suitable solution for how to use one DCI to schedule multiple PDSCHs.

Contents of the invention

In view of the above problems, the present application provides a wireless communication method, a terminal device, and a network device.

In the first aspect, a wireless communication method is provided, including: a terminal device receives a first DCI, the first DCI is used to schedule N PDSCHs, and the hybrid automatic retransmission corresponding to M PDSCHs in the N PDSCHs Request-acknowledgement (hybrid automatic repeat request-acknowledgement, HARQ-ACK) information is fed back on the same physical uplink control channel (physical uplink control channel, PUCCH), and both M and N are positive integers; wherein, the M PDSCHs include the first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the feedback timing set of the terminal device, the first sub Carrier spacing and second subcarrier spacing; wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is The interval is the subcarrier interval of the PUCCH or the subcarrier interval of the second carrier where the PUCCH is located.

In a second aspect, a wireless communication method is provided, including: a network device sends a first DCI, the first DCI is used to schedule N PDSCHs, and the HARQ-ACK information corresponding to M PDSCHs in the N PDSCHs is in The same PUCCH feedback, M and N are both positive integers; wherein, the M PDSCHs include the first PDSCH, and the time domain position of the first PDSCH is associated with the first time unit set, and the first time unit set is based on Determined by at least one of the following information: the feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing; wherein the first subcarrier spacing is the subcarrier spacing of the first PDSCH Or the subcarrier spacing of the first carrier where the first PDSCH is located, the second subcarrier spacing is the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located.

In a third aspect, a terminal device is provided, including: a receiving unit, configured to receive a first DCI, the first DCI is used to schedule N PDSCHs, and HARQ-ACK information corresponding to M PDSCHs in the N PDSCHs In the same PUCCH feedback, M and N are both positive integers; wherein, the M PDSCHs include a first PDSCH, and the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is Determined based on at least one of the following information: the feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing; wherein the first subcarrier spacing is a subcarrier of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located.

In a fourth aspect, a network device is provided, including: a sending unit, configured to send a first DCI, the first DCI is used to schedule N PDSCHs, and HARQ-ACK information corresponding to M PDSCHs in the N PDSCHs In the same PUCCH feedback, M and N are both positive integers; wherein, the M PDSCHs include a first PDSCH, and the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is Determined based on at least one of the following information: the feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing; wherein the first subcarrier spacing is a subcarrier of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located.

According to a fifth aspect, a terminal device is provided, including a memory and a processor, the memory is used to store a program, and the processor is used to invoke the program in the memory to execute the method according to the first aspect.

According to a sixth aspect, a network device is provided, including a memory and a processor, the memory is used to store a program, and the processor is used to invoke the program in the memory to execute the method described in the second aspect.

In a seventh aspect, an apparatus is provided, including a processor, configured to call a program from a memory to execute the method described in the first aspect.

In an eighth aspect, an apparatus is provided, including a processor, configured to call a program from a memory to execute the method described in the second aspect.

A ninth aspect provides a chip, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method described in the first aspect.

In a tenth aspect, a chip is provided, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method described in the second aspect.

In an eleventh aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method described in the first aspect.

In a twelfth aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method described in the second aspect.

A thirteenth aspect provides a computer program product, including a program, the program causes a computer to execute the method described in the first aspect.

A fourteenth aspect provides a computer program product, including a program, the program causes a computer to execute the method described in the second aspect.

A fifteenth aspect provides a computer program, the computer program causes a computer to execute the method described in the first aspect.

A sixteenth aspect provides a computer program, the computer program causes a computer to execute the method described in the second aspect.

In a multi-carrier scenario, when one DCI schedules multiple PDSCHs, one of the multiple PDSCHs (the first PDSCH above) and the PUCCH (used to feed back the HARQ-ACK information of the first PDSCH) may be in different subcarrier. The sub-carrier intervals of different carriers may be different (different sub-carrier intervals result in different time slot lengths), therefore, multiple PDSCHs cannot always be scheduled in exactly the same manner. Based on this, in a multi-carrier scenario, when one DCI needs to be used to schedule multiple PDSCHs, the embodiment of the present application considers the feedback timing set of the terminal device, the first subcarrier interval associated with PDSCH, and the second subcarrier interval associated with PUCCH. One or more of factors such as carrier spacing are helpful to realize the scheduling of multiple PDSCHs by one DCI in a multi-carrier scenario.

Description of drawings

FIG. 1 is a system architecture diagram of a communication system to which an embodiment of the present application can be applied.

FIG. 2 is an example diagram of a feedback window of a Type-1 HARQ-ACK codebook.

FIG. 3 is an example diagram of the arrangement of receivers of multiple candidate PDSCHs in the same time slot.

Fig. 4 is an example diagram of the expansion operation on the k1 set.

FIG. 5 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

FIG. 6 is an exemplary diagram of a possible determination manner of the first time unit set provided by the embodiment of the present application.

Fig. 7 is an exemplary diagram of another possible way of determining the first time unit set provided by the embodiment of the present application.

Fig. 8 is an example diagram of another possible way of determining the first time unit set provided by the embodiment of the present application.

FIG. 9A is an example diagram of a DCI time-domain resource indication manner provided by an embodiment of the present application.

FIG. 9B is another example diagram of the DCI time-domain resource indication manner provided by the embodiment of the present application.

FIG. 10 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

FIG. 11 is a schematic structural diagram of a network device provided by an embodiment of the present application.

Fig. 12 is a schematic structural diagram of the device provided by the embodiment of the present application.

Detailed ways

Communication Systems

FIG. 1 is a wireless communication system 100 applied in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120 . The network device 110 may be a device that communicates with the terminal device 120 . The network device 110 can provide communication coverage for a specific geographical area, and can communicate with the terminal device 120 located in the coverage area.

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within the coverage area. The embodiment of the application does not limit this.

Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system , LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, and satellite communication systems, and so on.

The terminal equipment in the embodiment of the present application may also be referred to as user equipment (user equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (mobile station, MS), mobile terminal (mobile Terminal, MT) ), remote station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a device that provides voice and/or data connectivity to users, and can be used to connect people, objects and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, and the like. The terminal device in the embodiment of the present application can be mobile phone (mobile phone), tablet computer (Pad), notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc. Optionally, UE can be used to act as a base station. For example, a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.

The network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be called an access network device or a wireless access network device, for example, the network device may be a base station. The network device in this embodiment of the present application may refer to a radio access network (radio access network, RAN) node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names in the following, or replace with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), primary station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node , wireless node, access point (access piont, AP), transmission node, transceiver node, base band unit (base band unit, BBU), remote radio unit (Remote Radio Unit, RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning nodes, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem or chip used to be set in the aforementioned equipment or device. The base station can also be a mobile switching center, a device that undertakes the function of a base station in D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication, and a device in a 6G network. Network-side equipment, equipment that assumes base station functions in future communication systems, etc. Base stations can support networks of the same or different access technologies. The embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.

Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or drone may be configured to serve as a device in communication with another base station.

In some deployments, the network device in this embodiment of the present application may refer to a CU or a DU, or, the network device includes a CU and a DU. A gNB may also include an AAU.

Network equipment and terminal equipment can be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the air. In the embodiment of the present application, the scenarios where the network device and the terminal device are located are not limited.

It should be understood that the communication device mentioned in this application may be a network device, or may also be a terminal device. For example, the first communication device is a network device, and the second communication device is a terminal device. In another example, the first communication device is a terminal device, and the second communication device is a network device. In another example, both the first communication device and the second communication device are network devices, or both are terminal devices.

It should also be understood that all or part of the functions of the communication device in this application may also be realized by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).

HARQ timing

After receiving the PDSCH, the terminal device will decode the PDSCH. The terminal device can send the HARQ-ACK information corresponding to the PDSCH to the network device according to the decoding result of the PDSCH. For example, if the PDSCH decoding is successful, the terminal device may send an acknowledgment (acknowledgment, ACK) to the network device; if the PDSCH decoding fails, the terminal device may send a negative acknowledgment (negative acknowledgment, NACK) to the network device. The HARQ-ACK information may sometimes be referred to as feedback information for short. The HARQ-ACK information is generally represented by 1 bit, so the HARQ-ACK information may also be called a feedback bit sometimes. HARQ-ACK information can be carried on the PUCCH. In other words, the terminal device can use the PUCCH to feed back the HARQ-ACK information corresponding to the PDSCH (that is, HARQ feedback).

The HARQ timing may also be referred to as HARQ-ACK timing (HARQ-ACK timing). In some communication systems, such as NR version 15 (release 15, rel-15) system, HARQ timing indicates the time slot where the PDSCH is located to the time slot where the PUCCH is located (or the time slot where the PDSCH is located to the time slot where the HARQ-ACK information corresponding to the PDSCH is located) ) between the slot offset value or the slot timing value (slot timing value). The slot offset value is usually represented by k1.

A common method for determining the HARQ timing is given below. First, the network device may configure a feedback timing set for the terminal device through radio resource control (radio resource control, RRC) signaling. The feedback timing set may include one or more k1 values. Therefore, the feedback timing set may also be called k1 set (k1set). Next, the network device can schedule the PDSCH through the DCI (for ease of description, the PDSCH scheduled by the DCI is called PDSCH 1 below). The DCI may include "PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator)". The "PDSCH-to-HARQ feedback timing indication" is used to indicate an element in the k1 set, that is, a k1 value, to the terminal equipment. The terminal device can determine the timing relationship (or timing relationship) between the time slot where the PDSCH 1 is located and the time slot where the HARQ-ACK information corresponding to the PDSCH 1 is located according to the k1 value. Assuming that the time slot where the HARQ-ACK information is located is time slot n, then the time slot where the PDSCH 1 is located is time slot n-k1. Then, the terminal device may send a PUCCH to the network device at time slot n, so as to transmit the HARQ-ACK information to the network device through the PUCCH.

It should be noted that the value of k1 may be 0. k1=0 can be defined as the last uplink time slot that overlaps with the downlink time slot where the PDSCH is located (k1=0 corresponds to the last UL slot that overlaps with the DL slot for the PDSCH).

Sub-slot (sub-slot) and sub-slot based HARQ timing

The HARQ timing described above is the HARQ timing based on the time slot, that is, the time sequence relationship between the PDSCH and the HARQ-ACK information corresponding to the PDSCH is defined with the time slot as the basic unit. However, the basic unit of HARQ timing is not limited to slots. In some scenarios, HARQ timing may use a shorter time unit as a basic unit. For example, in the ultra-reliable and low latency communications (URLLC) project of NR rel-16, in order to shorten the feedback delay of HARQ-ACK information (or the feedback delay of PUCCH), the project supports A communication architecture based on sub-slots. Exemplarily, one time slot may include 2 or 7 sub-slots. One slot generally includes 14 symbols. Therefore, if one slot includes 2 sub-slots, each sub-slot may include 7 symbols. Similarly, if a time slot includes 7 sub-slots, each sub-slot may include 2 symbols.

The sub-slot-based HARQ timing is basically similar to the slot-based HARQ timing. The main difference between the two is that in the sub-slot-based HARQ timing, k1 represents the offset value between sub-slots.

It should be noted that, in sub-slot-based HARQ timing, the value of k1 may also be 0. However, unlike the definition of k1=0 in slot-based HARQ timing, in sub-slot-based HARQ timing, k1=0 is defined as the last uplink sub-slot that overlaps with the last symbol of PDSCH .

HARQ-ACK codebook

Certain communication systems support multiple types of HARQ-ACK codebooks. The HARQ-ACK codebook may also be called a feedback codebook. Different types of HARQ-ACK codebooks result in different ways of generating HARQ-ACK information. Taking the NR Rel-15 system as an example, the system supports Type-1HARQ-ACK codebook and Type-2HARQ-ACK codebook. The Type-1 HARQ-ACK codebook can also be called a semi-static HARQ-ACK codebook (semi-static HARQ-ACK codebook). The Type-2 HARQ-ACK codebook can also be called a dynamic HARQ-ACK codebook (dynamic HARQ-ACK codebook).

For ease of understanding, the following describes in detail how to generate the HARQ-ACK information corresponding to the Type-1 HARQ-ACK codebook.

First, the number of serving cells (serving cells), the k1 set, and the row index set (a set of row indexes) of the time domain resource assignment (TDRA) table can be configured for the terminal device according to the network device. Each row index in , a row index corresponds to a row (or TDRA row) of the TDRA table, and a row index can define or indicate one or more of the following information: the time slot offset value k0 from PDCCH to PDSCH, The start and length indicators (SLIV) and the PDSCH mapping type (PDSCH mapping type) are used to determine the reception opportunity of the candidate PDSCH (occasion for candidate PDSCH reception) in a semi-static manner. Next, the number of bits of the HARQ-ACK information corresponding to the Type-1 HARQ-ACK codebook can be determined according to the receiving opportunity of the candidate PDSCH. Then, the decoding results of the PDSCHs in the receiving opportunities of each candidate PDSCH can be mapped to corresponding bits in the Type-1 HARQ-ACK codebook.

Specifically, in the feedback mode based on the Type-1 HARQ-ACK codebook, a feedback window may first be determined according to the k1 set. The feedback window may include one or more time slots (the number of time slots included in the feedback window is associated with the number of k1 values in the k1 set). Taking Figure 2 as an example, assuming that the k1 set of the terminal device is configured as {1,2,4}, and the Type-1 HARQ-ACK codebook is carried in time slot n, the feedback window determined according to the k1 set can include the following three Timeslot: {timeslot n-1, timeslot n-2, timeslot n-4}. In the time slots included in the feedback window, the receiving opportunities of candidate PDSCHs can be determined according to the SLIV indicated by a series of row indices.

It can be seen that the number of bits of HARQ-ACK information included in the Type-1 HARQ-ACK codebook does not depend on the number of PDSCHs actually received, but is based on the receiving opportunities of candidate PDSCHs configured semi-statically (that is, the maximum receivable PDSCH number) determined. The advantage of the above definition of the number of bits of the HARQ-ACK codebook is that it can avoid the ambiguity between the understanding of the size of the HARQ-ACK codebook by the terminal device and the network device because the terminal device has not received part of the PDSCH, resulting in the network device being unable to Correctly receive the HARQ-ACK information sent by the terminal device. However, this method needs to reserve feedback information bits for all possible transmitted PDSCHs in the HARQ-ACK codebook. Therefore, the above-mentioned way of defining the number of bits of the HARQ-ACK codebook has the disadvantage of relatively large feedback overhead. Therefore, in some scenarios, some redundant feedback information in the Type-1 HARQ-ACK codebook can be removed to reduce the feedback overhead of the Type-1 HARQ-ACK codebook.

For example, usually, a terminal device can only receive at most one PDSCH at the same time in one carrier. If the receivers of multiple candidate PDSCHs overlap in the time domain, the receivers of the multiple candidate PDSCHs may share one feedback information bit in the Type-1 HARQ-ACK codebook. Taking FIG. 3 as an example, the receiver opportunity 1 of the PDSCH candidate in the time slot shown in FIG. 3 overlaps with the

receiver opportunities

2 and 3 of the candidate PDSCH in the time domain. Therefore, generally speaking, the receiver opportunities of the three PDSCH candidates PDSCH will not be transmitted at the same time. If the corresponding feedback information bits are reserved for candidate

PDSCH receiver opportunities

1, 2, and 3 in the Type-1 HARQ-ACK codebook, it will inevitably lead to redundant feedback information. Therefore, one feedback information bit can be reserved for candidate

PDSCH receiver opportunities

1, 2, and 3, and the feedback information bit can be shared by the three candidate PDSCH receiver opportunities. The so-called sharing means that no matter which candidate PDSCH receiver of the three candidate PDSCH receivers receives the PDSCH, the feedback information corresponding to the PDSCH will be mapped to the same Type-1 HARQ-ACK codebook. on the bits. It can be seen that after adopting this scheme, in the example shown in Figure 3, although the time slot contains 5 candidate PDSCH receiving opportunities, only 2 feedback information bits need to be reserved in the Type-1 HARQ-ACK codebook (It should be understood that the single-codeword transmission is used as an example for illustration here, that is, one PDSCH only carries one transport block (transport block, TB), corresponding to one bit of feedback information). If the terminal device does not have the ability to receive more than one unicast PDSCH (unicast PDSCH) in one time slot, the terminal device will not receive two PDSCHs simultaneously in one time slot. In this case, redundancy of feedback information in the Type-1 HARQ-ACK codebook can be further reduced. Still taking FIG. 3 as an example, if the terminal device is not capable of receiving more than one unicast PDSCH in one time slot, the receivers of the five candidate PDSCHs in FIG. 3 may only share one feedback information bit. That is to say, no matter which of the five candidate PDSCH receivers in Figure 3 receives the PDSCH, the feedback information corresponding to the PDSCH will be mapped to the same bit of the Type-1 HARQ-ACK codebook bit.

It should be noted that the above uses the time slot as the basic unit of HARQ timing to illustrate the generation method of the HARQ-ACK information corresponding to the Type-1 HARQ-ACK codebook, and the generation method of the HARQ-ACK information is also applicable In the case where sub-slots are used as the basic unit of HARQ timing, it is only necessary to regard the elements in the k1 set as sub-slot offset values.

HARQ-ACK signal in dual connectivity (dual connectivity, DC)/carrier aggregation (carrier aggregation, CA) mode Feedback

If the terminal device works in the DC/CA mode, the network device can configure multiple cell groups for the terminal device. For example, the network device may configure a master cell group (master cell group, MCG) and a secondary cell group (secondary cell group, SCG) for the terminal device. MCG corresponds to a master node and includes a set of serving cells. There is a special cell in the group of serving cells, that is, a primary cell (PCell). The primary cell may be the cell where the terminal device initiates a random access procedure.

The SCG corresponds to a secondary node (SN), and includes a group of serving cells. The group of serving cells also has a special cell, that is, a primary secondary cell (PSCell). The primary-secondary cell may be a cell where the terminal device initiates a random access procedure.

In the DC/CA mode, in order to simplify the implementation, the protocol stipulates that the terminal equipment cannot feed back the PUCCH in all serving cells in the MCG and SCG. Therefore, the network device configures the pucch-Cell parameter for the serving cell to implicitly divide a cell group (such as MCG or SCG) into two PUCCH groups (PUCCH group). In the two PUCCH groups, the HARQ-ACK information corresponding to the PDSCH of the cell in one PUCCH group is fed back on the special cell (PCell or PSCell) of the cell group, and the HARQ-ACK information corresponding to the PDSCH of the cell in the other PUCCH group - ACK information is fed back on the pucch-Cell (or PUCCH SCell) configured in the serving cell.

The "pucch-Cell" parameter mentioned above may be located in the PDSCH-Serving Cell Configuration information element (PDSCH-ServingCellConfig information element) of the serving cell. An example of the format of this cell is given below.

As can be seen from the above example, the IE includes a "pucch-Cell" field. This field can be used to define the index of the serving cell that transmits PUCCH in the same cell group. If this field is missing in the PDSCH-serving cell configuration information element of a certain serving cell, the terminal device can carry the HARQ-ACK information corresponding to the serving cell in the PUCCH of the special cell of the cell group to which the serving cell belongs, or, If the serving cell itself is a PUCCH SCell, the terminal device may carry the HARQ-ACK information corresponding to the serving cell in the PUCCH of the serving cell.

One DCI schedules multiple PDSCHs of the same cell

Some communication systems support one DCI to schedule multiple PDSCHs of the same cell (or the same carrier). For example, NR Rel-17 supports one DCI to schedule multiple PDSCH/PUSCH (multi-PDSCH/PUSCH) of the same cell in the work item "Extending current NR operation to 71GHz (Extending current NR operation to 71GHz)".

A DCI is used as an example to schedule multiple PDSCHs (different PDSCHs can be used to bear different TBs) for illustration. The DCI may include an indication field shared by all PDSCHs scheduled by the DCI. For example, the DCI may include a modulation and coding scheme (modulation and coding scheme, MCS). The MCS can be shared by all PDSCHs scheduled by the DCI, that is, the MCSs of all PDSCHs are consistent. In addition, the DCI may also include an indication field for each PDSCH (that is, the indication field is per PDSCH). For example, the DCI may include a redundancy version (redundancy version, RV) indicator field and a new data indicator (new data indicator, NDI) indicator field corresponding to each PDSCH scheduled by the DCI, and an RV indicator field and an NDI indicator field corresponding to different PDSCHs Can be different. For the time-domain resource indication of the multiple PDSCHs, you can refer to the multi-PUSCH (multi-PUSCH) design of 5G NR-U (5G NR in unlicensed spectrum, unlicensed spectrum in 5G NR). That is, the TDRA table can be extended so that each TDRA row of the TDRA table indicates multiple (for example, a maximum of 8) PDSCH SLIVs, PDSCH mapping types, and the time slot offset value k0 from PDCCH to PDSCH.

Further, when one DCI schedules multiple PDSCHs of the same cell, the HARQ-ACK information corresponding to the multiple PDSCHs can be fed back through the same PUCCH. For example, the Type-1 HARQ-ACK codebook may be used to feed back the HARQ-ACK information corresponding to the multiple PDSCHs. In this case, the PDSCH to HARQ feedback timing indication in the DCI can be used to indicate the time slot where a PDSCH (such as the last scheduled PDSCH among the multiple PDSCHs) is located to the PUCCH (the HARQ- ACK information) the timing relationship between the time slots. Taking Figure 4 as an example, assuming that one DCI schedules three PDSCHs in the same cell: PDSCH 1, PDSCH 2, and PDSCH 3, and the PUCCH is used to feed back the HARQ-ACK information corresponding to the three PDSCHs, then the PDSCH in the DCI to The HARQ feedback timing indication can indicate the time slot relationship between the time slot where PDSCH 3 is located and the time slot where PUCCH is located.

Continuing to take Figure 4 as an example, assuming that the k1 set configured by the terminal device is {1}, the time slot offset value between the time slot of PDSCH 1 in Figure 4 and the time slot of PUCCH in Figure 4 is 4, and the time slot of PDSCH 2 in Figure 4 The time slot offset value between the time slot where the PUCCH is located and the time slot where the PUCCH is located is 2, and neither of these two time slot offset values belongs to the elements in the k1 set. If this happens, refer to the previous introduction to the Type-1HARQ-ACK codebook. It can be seen that the feedback window corresponding to the Type-1HARQ-ACK codebook will not include the time slots of PDSCH 1 and PDSCH 2, so Type-1HARQ-ACK Corresponding feedback information bits will not be reserved for PDSCH 1 and PDSCH 2 in the codebook. In order to solve this problem, NR Rel-17 extends the k1 set, so that the slot offset values between the time slots of multiple PDSCHs scheduled by the same DCI and the time slots of the PUCCH can all fall into the k1 set. Still taking FIG. 4 as an example, the k1 set={1} configured on the terminal device can be extended to k1 set={1,2,4}. In this way, the Type-1 HARQ-ACK codebook in slot n (located in the PUCCH of slot n) will be the PDSCH located in slot n-1 (PDSCH 3 in Figure 4), located in slot n-2 The PDSCH (PDSCH 2 in Figure 4) and the PDSCH (PDSCH 1 in Figure 4) located in time slot n-4 both reserve feedback information bits.

One DCI schedules PDSCH of multiple carriers

At present, a scheme of scheduling PDSCHs of multiple carriers with one DCI has gradually been paid attention to and proposed. For example, a work item in NR Rel-17 is how to better support dynamic spectrum sharing (DSS) of LTE and NR. On the carrier shared by LTE and NR, in order to avoid the communication signal of the NR system from interfering with the LTE system, the agreement requires that the NR system does not use the cell-specific reference signal (CRS) resource and PDCCH resource of the LTE system. Therefore, on the shared carrier, the capacity of the PDCCH of the NR system will be affected. A research goal of DSS is to study new mechanisms to solve the problem of low PDCCH capacity in NR systems. Aiming at this problem, a potential solution is to use one DCI to schedule PDSCHs of two different carriers. For example, a DCI transmitted on PCell or SCell can simultaneously schedule PDSCH on PCell and SCell (it should be noted that in this application, "cell (or serving cell)" and "carrier" are two concepts with the same meaning, In the absence of a clear distinction, the two can be replaced by each other). However, due to time constraints, the standardization of the characteristics of one DCI scheduling PDSCH of two carriers in NR Rel-17 has not been completed.

At present, many companies hope that the protocol supports one DCI to schedule PDSCHs of multiple carriers. However, in a multi-carrier scenario, the PUCCH used to feed back the HARQ-ACK information corresponding to the PDSCH and the PDSCH may be located on different carriers. The sub-carrier intervals of different carriers may be different, so that the lengths of time slots of different carriers may be different. When the HARQ-ACK information corresponding to multiple PDSCHs scheduled by the same DCI needs to be fed back through the same PUCCH, how to design the time domain position of the PDSCH so that the HARQ-ACK codebook contained in the PUCCH can include the information of the multiple PDSCHs HARQ-ACK information, there is no suitable solution yet.

In order to solve the above problem, the embodiment of the present application will be described in more detail below with reference to FIG. 5 . FIG. 5 is described from the perspective of interaction between a terminal device and a network device. The terminal device may be, for example, the terminal device 120 in FIG. 1 , and the network device may be, for example, the network device 110 in FIG. 1 .

Referring to Fig. 5, in step S510, the terminal device receives the first DCI sent by the network device. The first DCI can be used to schedule N PDSCHs. N may be a positive integer greater than or equal to 2. In some embodiments, the N PDSCHs may be located on P carriers (P is less than or equal to N). For example, the N PDSCHs may be respectively located on N carriers. That is to say, the first DCI can be used to schedule PDSCHs on N carriers. For example, a terminal device can work in DC/CA mode. In the DC/CA mode, the terminal device will be configured with multiple carriers (or multiple serving cells, serving cells and carriers in this application are two equivalent concepts and can be replaced with each other). In this example scenario, the network device can use the first DCI to schedule multiple carriers in the DC/CA mode.

HARQ-ACK information corresponding to M PDSCHs (M is a positive integer greater than or equal to 2, and M≤N) among the N PDSCHs may be fed back through the same PUCCH. For example, the PUCCH may carry a Type-1 HARQ-ACK codebook. The Type-1 HARQ-ACK codebook may reserve bits for HARQ-ACK information corresponding to M PDSCHs. In some embodiments, the terminal device may feed back the HARQ-ACK information corresponding to the M PDSCHs on the PUCCH. For example, the terminal device may generate a HARQ-ACK codebook (Type-1 HARQ-ACK codebook), and the HARQ-ACK codebook may include HARQ-ACK information corresponding to M PDSCHs. Then, the terminal device can send the HARQ-ACK codebook to the network device through the PUCCH.

In some embodiments, the M PDSCHs may be located on Q carriers (Q is less than or equal to M, and the Q carriers belong to the aforementioned P carriers, where Q and P are positive integers). For example, the M PDSCHs may respectively belong to M carriers. Further, in some embodiments, the M carriers may belong to the same PUCCH group (for the concept of the PUCCH group, please refer to the introduction related to "Feedback of HARQ-ACK information in DC/CA mode" above).

In some embodiments, the first DCI includes a PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator), and the PDSCH-to-HARQ feedback timing indicator may indicate the time unit of one or more PDSCHs in the M PDSCHs ( The offset value from the time unit (such as time slot) where the PUCCH is located. For example, the PDSCH-to-HARQ feedback timing indication may indicate an offset value from the time unit of the Xth PDSCH among the M PDSCHs to the time unit of the PUCCH, 1≤X≤M, where X is a positive integer. The Xth PDSCH can be one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, the PDSCH with the smallest associated serving cell index, or the associated serving cell The PDSCH with the largest cell index.

The first scheduled PDSCH mentioned above may be the PDSCH with the earliest end time among the M PDSCHs. The end time mentioned here can refer to the end time of PDSCH transmission (such as the end time of the last symbol of PDSCH), or it can also refer to the end time of the time unit (such as time slot) where PDSCH is located (such as the end time of the last symbol of PDSCH). slot end time). If the M PDSCHs contain at least two PDSCHs with the same end time, and the end time of the at least two PDSCHs with the same end time is earlier than the end time of the remaining PDSCHs in the M PDSCHs, then the first scheduled PDSCH can be Among the at least two PDSCHs, the PDSCH that satisfies the following conditions: the PDSCH with the earliest transmission start time, the PDSCH with the latest transmission start time, the PDSCH with the largest associated serving cell index, the PDSCH with the smallest associated serving cell index, and the subcarrier The PDSCH with the largest interval, or the PDSCH with the smallest subcarrier interval.

The last scheduled PDSCH mentioned above may be the PDSCH with the earliest end time among the M PDSCHs. The end time mentioned here can refer to the end time of PDSCH transmission (such as the end time of the last symbol of PDSCH), or it can also refer to the end time of the time unit (such as time slot) where PDSCH is located (such as the end time of the last symbol of PDSCH). slot end time). If M PDSCHs include at least two PDSCHs with the same end time, and the end time of the at least two PDSCHs with the same end time is later than the remaining PDSCHs in the M PDSCHs, the last scheduled PDSCH may be the at least two Among the PDSCHs, the PDSCH that meets the following conditions: the PDSCH with the earliest transmission start time, the PDSCH with the latest transmission start time, the PDSCH with the largest associated serving cell index, the PDSCH with the smallest associated serving cell index, and the PDSCH with the largest subcarrier spacing , or, the PDSCH with the smallest subcarrier spacing.

The M PDSCHs may include the first PDSCH (it may be any one of the M PDSCHs). The time domain position of the first PDSCH is associated with the first set of time units. The first set of time units may include one or more time units. The embodiment of the present application does not specifically limit the length of a time unit in the first time unit set, for example, it may be a time slot, a sub-slot, or a combination of one or more symbols.

In some embodiments, "the time domain position of the first PDSCH is associated with the first set of time units" may mean that the time domain position of the first PDSCH is determined based on the first set of time units. Alternatively, the first set of time units may be used to define the time domain position of the first PDSCH.

In some embodiments, "the time domain position of the first PDSCH is associated with the first set of time units" may mean that part or all of the time domain positions of the first PDSCH are located in the first set of time units. As a possible implementation manner, the time slot where the first PDSCH is located is located in the first time unit set. In other words, the terminal device does not expect the first PDSCH to be located in time units other than the first set of time units on the first carrier. The terminal device does not expect the first PDSCH to be located in a time unit other than the first time unit set on the first carrier, and accordingly, the network device may schedule the first PDSCH so that the first PDSCH is located in the first time unit set . Of course, this embodiment of the present application does not exclude the situation that the network device schedules the first PDSCH so that the first PDSCH is located in a time unit other than the first time unit set (in addition, the "terminal device does not "Expectation" can also be understood in the same or similar way, so I won't go into details later). For example, if the time unit of the HARQ timing of the second carrier (the carrier where the PUCCH is located) is a time slot, the time slot where the first PDSCH is located is located in the first time unit set. As another possible implementation manner, the last symbol of the first PDSCH is located in the first time unit set. In other words, the terminal device does not expect the last symbol of the first PDSCH to be located in a time unit other than the first time unit set on the first carrier. For example, if the time unit of the HARQ timing of the second carrier (the carrier where the PUCCH is located) is a sub-slot, the last symbol of the first PDSCH is located in the first time unit set.

In some embodiments, the first set of time units may be time units on the first carrier. The first set of time units may include at least one time unit, and the at least one time unit overlaps in time domain with the time units in the second set of time units. The at least one time unit may be part or all of the time units on the first carrier that overlap in time domain with the time units in the second time unit set. The second time unit set mentioned here may be a time unit determined based on the time domain position of the PUCCH and the feedback timing set. For example, the second set of time units is the time slot {n-k1} on the second carrier. Among them, n represents the time unit where the PUCCH is located (such as n is the number of the time unit where the PUCCH is located, taking the time unit as a time slot as an example, then n represents the time slot number of the time slot where the PUCCH is located), and k1 represents the feedback of the terminal equipment Each element in the time series collection. In other words, the value range of k1 may be all elements in the feedback timing set. Taking the PUCCH located in time slot n as an example, if the feedback timing set k1 = {1, 2, 4}, the second time unit set may include time slots {n-1, n-2, n-4}.

The embodiment of the present application does not specifically limit the manner of determining the first time unit set. In some embodiments, the first time unit set may be determined based on at least one of the following information: a feedback timing set (or k1 set) of the terminal device, a first subcarrier interval (which may refer to the subcarrier of the first PDSCH spacing or the subcarrier spacing of the first carrier where the first PDSCH is located) and the second subcarrier spacing (may refer to the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located, the PUCCH refers to the subcarrier spacing used for The PUCCH that feeds back the HARQ-ACK information corresponding to the first PDSCH). For example, the first set of time units may be determined based on a feedback timing set of the terminal device. As another example, the first set of time units may be determined based on the second subcarrier spacing. As another example, the first set of time units may be determined based on a size relationship between the first subcarrier spacing and the second subcarrier spacing.

Alternatively, in some embodiments, the first set of inter-units may be determined based on a combination of the above manners. For example, the first inter-unit set may be determined based on the feedback timing set of the terminal device and in combination with the size relationship between the first subcarrier spacing and the second subcarrier spacing.

In addition, in some embodiments, the first time unit set may also be determined in combination with other factors. For example, when determining the first time unit set, in addition to the factors mentioned above, the time unit (such as time slot or sub-slot) on which the HARQ timing of the second carrier (the carrier where the PUCCH is located) is based can also be considered .

The manner of determining the first time unit set is illustrated in more detail below in conjunction with specific embodiments.

Embodiment one

The first set of time units may be determined based on the first parameter and/or the second parameter. The first parameter may be n-k1. This second parameter can be the same as

and / or

related parameters. For example, the second parameter could be

or

n may indicate the time unit where the PUCCH is located (eg, the time slot where the PUCCH is located), μ _DL may indicate the first subcarrier spacing, and μ _UL may indicate the second subcarrier spacing. The relationship between the first subcarrier spacing and μ _DL can use the formula

Sure. For example, the values of μ _DL can be 0, 1, 2, 3, 4 respectively, and correspondingly, the intervals of the first subcarriers can be 15kHz, 30kHz, 60kHz, 120kHz, 240kHz respectively. The relationship between the second subcarrier spacing and μ _DL can also use the formula

It is determined that the values of μ _UL can be 0, 1, 2, 3, 4 respectively, and correspondingly, the intervals of the second subcarriers can be 15kHz, 30kHz, 60kHz, 120kHz, 240kHz respectively.

Several possible implementations of Embodiment 1 are given below.

Implementation method one:

The first set of time units may include time units

Taking time units as time slots as an example, the first set of time units may include time slots

in

Indicates rounding down. In other words, the terminal device does not expect the time domain position of the first PDSCH to be located in the time slot of the first carrier

outside the time slot.

In the first implementation manner, the value range of k1 may be all elements in the feedback timing set of the terminal device. Alternatively, the value range of k1 may be some elements in the feedback timing set of the terminal device. For example, the value range of k1 may be the elements satisfying the following formula in the feedback timing set of the terminal device:

Where mod(·) represents the remainder operation. It should be noted that this example requires that the value of k1 conforms to the value range defined by the formula, but the embodiment of the present application does not limit the specific form of the formula, and the formula can also adopt other deformation forms, for example, in In the case of μ _DL ≤ μ _UL , the above formula can also be rewritten as

In some embodiments, the first time unit set can be determined as a time unit when a certain condition is met

As an example, in the case of μ _DL < μ _UL , the first set of time units may be set to include time units

For example, if μ _DL < μ _UL , the first set of time units may include time units

Among them, k1 may only include elements satisfying the following formula in the feedback sequence set of the terminal device:

Of course, in other examples, in the case of μ _DL > μ _UL , the first set of time units may be set to include time units

Alternatively, in the case of μ _DL = μ _UL , the first set of time units may be set to include time units

A more specific example is given below in conjunction with FIG. 6 . As shown in FIG. 6, three carriers are set between the network device and the terminal device: CC1, CC2, and CC3. Wherein, the subcarrier spacing of CC1 is 15 kHz, the subcarrier spacing of CC2 is 30 kHz, and the subcarrier spacing of CC3 is 60 kHz. In addition, the feedback timing set configured by the network device for the terminal device is {1, 2, 4}.

The terminal device receives the first DCI sent by the network device, where the first DCI is used to schedule the PDSCHs of CC1-CC3. The three carriers may belong to the same PUCCH group, therefore, the HARQ-ACK information corresponding to the PDSCHs of the three carriers may be fed back through the same PUCCH. In the example of FIG. 6, the PUCCH is located in slot 8 on CC2.

If the first PDSCH mentioned above is the PDSCH on CC1, the time domain position of the first PDSCH can be located in the time slot

(corresponding to the first time unit set mentioned above), and the value range of k1 only includes elements in the feedback timing set of the terminal device that satisfy the following formula:

In the feedback timing set {1,2,4}, since only k1=1 satisfies

Therefore, the time slot

for time slot

i.e. slot {3}. In other words, the terminal device does not expect the PDSCH on CC1 to be scheduled in time slots other than the time slot {3} of CC1.

In the "HARQ-ACK codebook" section above, it is introduced how to determine the scheduling and feedback framework of the Type-1 HARQ-ACK codebook based on the feedback timing set of the terminal device. Implementation method 1 reuses the scheduling and feedback framework of the Type-1 HARQ-ACK codebook as much as possible, and does not need a new design of the feedback window (corresponding to the first time unit set), only needs to combine the sub-frames between PDSCH and PUCCH Adaptive adjustments are made to the relationship between carrier spacing. This implementation mode has good compatibility with the current protocol, and the terminal equipment is simple to implement.

Implementation method two:

The first set of time units includes time units

to time unit

time unit between. Taking time units as time slots as an example, the first set of time units may include time slots

to slot

In other words, the terminal device does not expect the time domain position of the first PDSCH to be located in the time slot of the first carrier

to slot

outside the time slot.

It should be noted that the time unit

to time unit

Time units between can include time units

and time units

or, time unit

to time unit

Time units between can include time units

without time units

or, time unit

to time unit

Time units between can include time units

without time units

or, time unit

to time unit

Time units between may not include time units

and time units

Instead, only time units within the time range defined by the two are included.

In some embodiments, when a certain condition is met, the first set of time units can be determined to include time units

to time unit

time unit between. As an example, in the case of μ _DL ≥ μ _UL , the first set of time units may be set to include time units

to time unit

time unit between.

Still taking Figure 6 as an example, if the first carrier is CC2 in Figure 6, and the first PDSCH is the PDSCH on CC2, then the time domain position of the first PDSCH is located in the time slot {(8-{1,2,4} )*1}=time slot {4, 6, 7} (corresponding to the aforementioned first set of time units). In other words, the terminal device does not expect the PDSCH on CC2 to be scheduled in time slots other than the time slot {4, 6, 7} of CC2.

If the first carrier is CC3 in Figure 6, and the first PDSCH is the PDSCH on CC3, then the time domain position of the first PDSCH is located in the time slot {(8-{1,2,4})*2}～{( 8-{1,2,4})*2+2-1}=time slots {8,9,12,13,14,15} (corresponding to the first set of time units mentioned above). In other words, the terminal device does not expect the PDSCH on CC3 to be scheduled in time slots other than the time slots {8, 9, 12, 13, 14, 15} of CC3.

It should be understood that the above implementation manner 1 and implementation manner 2 may be combined with each other if there is no conflict. For example, in some embodiments, if μ _DL < μ _UL , the first set of time units may be determined by means of implementation one; if μ _DL ≥ μ _UL , the first set of time units may be determined by way of implementation two.

The second implementation method reuses the scheduling and feedback framework of the Type-1 HARQ-ACK codebook as much as possible, and does not need a new design of the feedback window (corresponding to the first time unit set), and only needs to combine the sub-frames between PDSCH and PUCCH. Adaptive adjustments are made to the relationship between carrier spacing. This implementation mode has good compatibility with the current protocol, and the terminal equipment is simple to implement.

Implementation method three:

The first set of time units may include all time units overlapping the second set of time units. The second time unit set mentioned here may be a time unit determined based on the time domain position of the PUCCH and the feedback timing set. For example, the second set of time units is the time slot {n-k1} on the second carrier. Wherein, n represents the time unit where the PUCCH is located, and k1 represents an element in the feedback timing set of the terminal device. The value range of k1 may be all elements in the feedback timing set. Taking PUCCH located in time slot n as an example, if the feedback timing set k1={1,2,3,4,7,8}, the second time unit set may include time slots {n-1,n-2,n- 3,n-4,n-7,n-8}.

In some embodiments, if the second carrier uses sub-slots as the basic unit of HARQ timing, the first time unit set can be determined using the third implementation manner. In addition, if the second carrier uses subslots as the basic unit of HARQ timing, the first set of time units may be used to define the time domain position of the last symbol of the first PDSCH. That is, the last symbol of the first PDSCH is located in the first set of time units. In other words, the terminal device does not expect the last symbol of the first PDSCH to be located in a time unit of the first carrier other than the first time unit set.

A more specific example is given below in conjunction with FIG. 7 . As shown in FIG. 7 , three carriers are set between the network device and the terminal device: CC1, CC2, and CC3. Wherein, the subcarrier spacing of CC1 is 15 kHz, the subcarrier spacing of CC2 is 30 kHz, and the subcarrier spacing of CC3 is 60 kHz. In addition, the feedback sequence set configured by the network device for the terminal device is {1, 2, 3, 4, 7, 8}. One slot in CC2 includes 2 sub-slots.

The terminal device receives the first DCI sent by the network device, where the first DCI is used to schedule the PDSCHs of CC1-CC3. The 3 carriers may belong to the same PUCCH group. Therefore, the HARQ-ACK information corresponding to the PDSCHs of the three carriers can be fed back through the same PUCCH. In the example of FIG. 7, the PUCCH is located in the first sub-slot of slot 8 on CC2.

If the aforementioned first PDSCH is the PDSCH on CC1, the first time unit set may include the first half of time slot 2 and time slot 3 on CC1.

If the aforementioned first PDSCH is the PDSCH on CC2, the first set of time units may be the same as the second set of time units. That is, the first time unit set may include two sub-slots of time slot 4, two sub-slots of time slot 6, and two sub-slots of time slot 7 on CC2.

If the aforementioned first PDSCH is the PDSCH on CC3, the first set of time units may include time slots {8, 9, 12, 13, 14, 15} on CC3.

The third implementation method reuses the scheduling and feedback framework of the Type-1 HARQ-ACK codebook as much as possible, and does not need to carry out a new design of the feedback window (corresponding to the first time unit set). Adaptive adjustments are made to the relationship between carrier spacing. This implementation mode has good compatibility with the current protocol, and the terminal equipment is simple to implement.

Embodiment two

The first set of time units may be determined based on a first reference duration. In some embodiments, the first reference duration may be determined based on the second subcarrier spacing (that is, the subcarrier spacing of the PUCCH or the subcarrier spacing of the carrier where the PUCCH is located). In other words, the first reference duration may be determined based on the basic parameter set (numerology) of the PUCCH or the carrier where the PUCCH is located. For example, the length of the first reference duration may be set as 4 time slots under the second subcarrier interval. In addition, the time domain position of the first reference duration may be determined based on the time domain position of the PUCCH. For example, the end time of the first reference duration can be set as the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration can be set as the previous time unit of the time unit where the PUCCH is located (that is, the same as the time unit where the PUCCH is located) The end time of the previous time unit adjacent to the unit in time domain).

A more specific example is given below in conjunction with FIG. 8 . As shown in FIG. 8, three carriers are set between the network device and the terminal device: CC1, CC2, and CC3. Wherein, the subcarrier spacing of CC1 is 15 kHz, the subcarrier spacing of CC2 is 30 kHz, and the subcarrier spacing of CC3 is 60 kHz.

The terminal device receives the first DCI sent by the network device, where the first DCI is used to schedule the PDSCHs of CC1-CC3. The three carriers may belong to the same PUCCH group, therefore, the HARQ-ACK information corresponding to the PDSCHs of the three carriers may be fed back through the same PUCCH. In the example of FIG. 8, the PUCCH is located in slot 8 on CC2.

Since the PUCCH is located on CC2, the first reference duration can be defined based on the subcarrier spacing of CC2. For example, the first reference duration may be defined as 4 time slots at a subcarrier interval of 30 kHz. The end time of the first reference duration may be defined as the start time of the time slot where the PUCCH is located, or the end time of the previous time slot of the time slot where the PUCCH is located.

On the basis of the above definition, referring to FIG. 8 , if the aforementioned first PDSCH is the PDSCH on CC1, then the first time unit is the time slot {2, 3} on CC1. In other words, the terminal device does not expect the PDSCH on CC1 to be scheduled in time slots other than the time slots {2, 3} on CC1. Similarly, if the aforementioned first PDSCH is the PDSCH on CC2, then the first time unit is the time slots {4, 5, 6, 7} on CC2. In other words, the terminal device does not expect the PDSCH on CC2 to be scheduled in time slots other than the time slots {4, 5, 6, 7} on CC2. Similarly, if the aforementioned first PDSCH is the PDSCH on CC3, then the first time unit is time slots {8, 9, 10, 11, 12, 13, 14, 15} on CC3. In other words, the terminal device does not expect the PDSCH on CC3 to be scheduled in time slots other than the time slots {8, 9, 10, 11, 12, 13, 14, 15} on CC3.

Embodiment 2 provides a brand-new scheduling and feedback framework based on the reference duration. The carrier scheduling and feedback methods provided by the framework are relatively unified compared to carriers with different subcarrier spacings, and the implementation is simple.

Embodiment Three

The method for determining the first time unit has been described in detail above in conjunction with

Embodiments

1 and 2. The following describes in detail the manner of indicating the time-domain resources of the M PDSCHs in conjunction with the third embodiment. It should be understood that the time-domain resource indication manner described in Embodiment 3 can be implemented independently without depending on the foregoing embodiments.

As mentioned above, the M PDSCHs may be respectively located on the M carriers. The network device can configure a TDRA set for each of the M carriers. In other words, the network device configures a TDRA set for each carrier (or for each serving cell).

A TDRA set may be, for example, a TDRA table. A TDRA set may include one or more TDRA rows. Each TDRA line in the TDRA set may contain one or more of the following information: the time slot offset value k0 from the time slot where the DCI is located to the time slot where the PDSCH is located, SLIV, and the mapping type of the PDSCH.

In order to indicate the time domain resources of the M PDSCHs (or the N PDSCHs to which the M PDSCHs belong), a time domain resource indication field may be set in the first DCI. The time domain resource indication field may include one or more indexes. The one or more indexes may be used to indicate the TDRA row corresponding to each PDSCH in the M PDSCHs (or the N PDSCHs to which the M PDSCHs belong).

As an example, the time domain resource indication field may include M indexes, respectively indicating TDRA rows corresponding to the above M PDSCHs (or the N PDSCHs to which the M PDSCHs belong). This implementation of the time-domain resource indication domain has high flexibility.

As another example, the time domain resource indication field may include an index. The index is used to indicate the TDRA row corresponding to each PDSCH in the M PDSCHs (or the N PDSCHs to which the M PDSCHs belong). For example, the time-domain resource indication field may contain an index m, and the index m may indicate that M PDSCHs correspond to rows m+1 of M TDRA sets (such as TDRA tables), and the M TDRA sets refer to the network equipment as M TDRA set configured by carriers (or serving cells). The implementation of the time-domain resource indication field can indicate the time-domain resources of multiple carriers with fewer bits, thereby saving DCI overhead.

A more specific example is given below in conjunction with FIG. 9 (including FIG. 9A and FIG. 9B ).

The network device configures 3 carriers (or 3 serving cells) for the terminal device, and configures a TDRA set for each of the 3 carriers. Assume that the TDRA set configured on each of the three carriers includes two TDRA rows, and each TDRA row includes a time slot offset value k0. Among them, the time slot offset k0 of the TDRA set corresponding to carrier 1 is {1, 2}; the time slot offset k0 of the TDRA set corresponding to carrier 2 is {1, 3}; the time slot offset k0 of the TDRA set corresponding to carrier 3 The gap offset value k0 is {2,4}.

In the example of Figure 9, the first DCI simultaneously schedules the PDSCHs of 3 carriers, and the time slot of the last scheduled PDSCH of the first DCI is to the time slot of the PUCCH (PUCCH is not shown in Figure 9, and the PUCCH is located in Figure 9 The time slot offset value k1=1 of the time slot n) in 9.

In the example of FIG. 9 , the time domain resource indication field of the first DCI may include 1 bit. Values of the time domain resource indication field are 0 and 1 respectively. If the value of the time domain resource indication field is 0, the first DCI may simultaneously indicate that the PDSCHs on the three carriers respectively correspond to the first row of the TDR sets configured for the three carriers. Therefore, the time slot offset values k0 of the PDSCHs of the three carriers are respectively {1, 1, 2}, as shown in FIG. 9A . If the value of the time-domain resource indication field is 1, the first DCI may simultaneously indicate that the PDSCHs on the three carriers respectively correspond to the second row of the TDR sets configured on the three carriers. Therefore, the time slot offset values k0 of the PDSCHs of the three carriers are respectively {2, 3, 4}, as shown in FIG. 9B .

The method embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 9 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 10 to FIG. 12 . It should be understood that the descriptions of the method embodiments correspond to the descriptions of the device embodiments, therefore, for parts not described in detail, reference may be made to the foregoing method embodiments.

FIG. 10 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device 1000 in FIG. 10 includes a receiving unit 1010 . The receiving unit 1010 is configured to receive the first DCI. The first DCI is used to schedule N PDSCHs, and the HARQ-ACK information corresponding to M PDSCHs in the N PDSCHs is fed back on the same PUCCH, and M and N are both positive integers; wherein, the M PDSCHs include the first A PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the feedback timing set of the terminal device, the first Subcarrier spacing and second subcarrier spacing; wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is The carrier spacing is the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located.

Optionally, in some embodiments, the terminal device 1000 may include a feedback unit 1020 . The feedback unit 1020 may be configured to feed back the HARQ-ACK information corresponding to the M PDSCHs to the network device through the PUCCH.

Optionally, the first set of time units is determined based on a first parameter and/or a second parameter, where the first parameter is n-k1, and the second parameter is

or

The n represents the time unit where the PUCCH is located, the k1 represents elements in the feedback timing set, the μ _DL represents the first subcarrier spacing, and the μ _UL represents the second subcarrier spacing .

Optionally, the first set of time units includes a time unit

in

Indicates rounding down.

Optionally, the value range of k1 is an element satisfying the following formula in the feedback timing set:

Where mod(·) represents the remainder operation.

Optionally, the μ _DL is smaller than the μ _UL .

Optionally, the first set of time units includes a time unit

to time unit

time unit between.

Optionally, the μ _DL is greater than or equal to the μ _UL .

Optionally, the first time unit set includes at least one time unit on the first carrier, and the at least one time unit overlaps in time domain with a time unit in the second time unit set, and the first time unit The two time unit sets are determined based on the time domain position of the PUCCH and the feedback timing set.

Optionally, the second time unit set is a time unit {n-k1} on the second carrier, where n indicates the time slot where the PUCCH is located, and k1 indicates a time slot in the feedback timing set element.

Optionally, the first set of time units is determined based on a first reference duration, and the first reference duration is determined based on the second subcarrier spacing.

Optionally, the end time of the first reference duration is the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration is the end of the previous time unit of the time unit where the PUCCH is located time.

Optionally, the first PDSCH is located on the first carrier, and the terminal device does not expect the first PDSCH to be located on the first carrier in time units other than the first set of time units or, the terminal device does not expect the last symbol of the first PDSCH to be located in a time unit other than the first set of time units on the first carrier.

Optionally, the N PDSCHs are respectively located on N carriers, and the M PDSCHs are respectively located on M carriers among the N carriers.

Optionally, the M carriers belong to the same PUCCH group.

Optionally, the first DCI includes a time-domain resource indication field, and the time-domain resource indication field includes an index, and the index is used to indicate the TDRA line corresponding to each PDSCH in the M PDSCHs or the N The TDRA row corresponding to each PDSCH in the PDSCH.

Optionally, the first DCI includes a PDSCH-to-HARQ feedback timing indication, and the PDSCH-to-HARQ feedback timing indication is used to indicate the time unit of the X-th PDSCH among the M PDSCHs to the time unit of the PUCCH offset value.

Optionally, the Xth PDSCH is one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, and the PDSCH with the smallest associated serving cell index , or, the PDSCH with the largest associated serving cell index.

Optionally, the last scheduled PDSCH is the PDSCH with the latest end time among the M PDSCHs; wherein, the end time is the end time of the transmission of the PDSCH, or the end time is the time when the PDSCH is located The unit's end time.

Optionally, the time units in the first set of time units are a combination of one or more of the following: a time slot, a sub-slot, and one or more symbols.

FIG. 11 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device 1100 in FIG. 11 includes a sending unit 1110 . The sending unit 1110 is configured to send the first DCI. The first DCI is used to schedule N PDSCHs, and the HARQ-ACK information corresponding to M PDSCHs in the N PDSCHs is fed back on the same PUCCH, and M and N are both positive integers; wherein, the M PDSCHs include the first A PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the feedback timing set of the terminal device, the first Subcarrier spacing and second subcarrier spacing; wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is The carrier spacing is the subcarrier spacing of the PUCCH or the subcarrier spacing of the second carrier where the PUCCH is located.

Optionally, in some embodiments, the network device 1100 may include a receiving unit 1120 . The receiving unit 1120 may be configured to receive the HARQ-ACK information corresponding to the M PDSCHs fed back by the terminal device through the PUCCH.

or

Optionally, the first set of time units includes a time unit

in

Indicates rounding down.

Where mod(·) represents the remainder operation.

Optionally, the μ _DL is smaller than the μ _UL .

Optionally, the first set of time units includes a time unit

to time unit

time unit between.

Optionally, the μ _DL is greater than or equal to the μ _UL .

Optionally, the M carriers belong to the same PUCCH group.

Fig. 12 is a schematic structural diagram of a device according to an embodiment of the present application. The dashed line in Figure 12 indicates that the unit or module is optional. The apparatus 1200 may be used to implement the methods described in the foregoing method embodiments. Apparatus 1200 may be a chip, a terminal device or a network device.

Apparatus 1200 may include one or more processors 1210 . The processor 1210 can support the device 1200 to implement the methods described in the foregoing method embodiments. The processor 1210 may be a general purpose processor or a special purpose processor. For example, the processor may be a central processing unit (central processing unit, CPU). Alternatively, the processor can also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), off-the-shelf programmable gate arrays (field programmable gate arrays, FPGAs) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

Apparatus 1200 may also include one or more memories 1220 . A program is stored in the memory 1220, and the program can be executed by the processor 1210, so that the processor 1210 executes the methods described in the foregoing method embodiments. The memory 1220 may be independent from the processor 1210 or may be integrated in the processor 1210 .

The apparatus 1200 may also include a transceiver 1230 . The processor 1210 can communicate with other devices or chips through the transceiver 1230 . For example, the processor 1210 may send and receive data with other devices or chips through the transceiver 1230 . Taking the apparatus 1200 as the terminal device 1000 mentioned above as an example, the transceiver 1230 may refer to the receiving unit 1010 or the feedback unit 1020 of the terminal device 1000 . Alternatively, the functions of the receiving unit 1010 or the feedback unit 1020 may be implemented by the transceiver 1230 . Taking the apparatus 1200 as the network device 1100 mentioned above as an example, the transceiver 1230 may refer to the sending unit 1110 and the receiving unit 1120 of the network device 1100 . Alternatively, the functions of the sending unit 1110 and the receiving unit 1120 may be implemented by the transceiver 1230 .

The embodiment of the present application also provides a computer-readable storage medium for storing programs. The computer-readable storage medium can be applied to the terminal device or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program product. The computer program product includes programs. The computer program product can be applied to the terminal device or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal device or the network device provided in the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

It should be understood that in this embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be read by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (digital video disc, DVD)) or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) )wait.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A method for wireless communication, comprising:

The terminal device receives the first downlink control information DCI, the first DCI is used to schedule N physical downlink shared channels PDSCH, and the hybrid automatic repeat request-confirmation HARQ-ACK information corresponding to the M PDSCHs in the N PDSCHs In the same physical uplink control channel PUCCH feedback, both M and N are positive integers;

Wherein, the M PDSCHs include the first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the The feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing;

Wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH Or the subcarrier spacing of the second carrier where the PUCCH is located.
The method according to claim 1, wherein the N PDSCHs are respectively located on N carriers, and the M PDSCHs are respectively located on M carriers among the N carriers.
The method according to claim 2, wherein the M carriers belong to the same PUCCH group.
The method according to any one of claims 1-3, wherein the first set of time units is determined based on a first parameter and/or a second parameter, wherein the first parameter is n- k1, the second parameter is
or
The n represents the time unit where the PUCCH is located, the k1 represents elements in the feedback timing set, the μ DL represents the first subcarrier spacing, and the μ UL represents the second subcarrier spacing .
The method according to claim 4, wherein the first set of time units comprises time units

in
Indicates rounding down.
The method according to claim 5, wherein the value range of the k1 is an element satisfying the following formula in the feedback timing set:
Where mod(·) represents the remainder operation.
The method according to claim 5 or 6, characterized in that the μ DL is smaller than the μ UL .
The method according to claim 4, wherein the first set of time units comprises time units

to time unit
time unit between.
The method according to claim 8, wherein said μ DL is greater than or equal to said μ UL .
The method according to any one of claims 1-9, wherein the time units in the first set of time units include at least one time unit on the first carrier, and the at least one time unit It overlaps with the time units in the second time unit set in the time domain, and the second time unit set is determined based on the time domain position of the PUCCH and the feedback timing set.
The method according to claim 10, wherein the second set of time units is a time unit {n-k1} on the second carrier, the n represents the time slot where the PUCCH is located, and the k1 represents an element in the feedback timing set.
The method according to any one of claims 1-3, wherein the first set of time units is determined based on a first reference duration, and the first reference duration is determined based on the second subcarrier spacing definite.
The method according to claim 12, wherein the end time of the first reference duration is the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration is the time unit where the PUCCH is located. The end time of the previous time unit of the time unit.
The method according to any one of claims 1-13, wherein the first PDSCH is located on the first carrier, and the terminal device does not expect the first PDSCH to be located on the first carrier or, the terminal device does not expect the last symbol of the first PDSCH to be located on the first carrier other than the first set of time units outside time unit.
The method according to any one of claims 1-14, wherein the first DCI includes a time domain resource indication field, and the time domain resource indication field includes an index, and the index is used to indicate the The time-domain resource allocation corresponding to each PDSCH in the M PDSCHs or the TDRA row corresponding to each PDSCH in the N PDSCHs.
The method according to any one of claims 1-15, wherein the first DCI includes a PDSCH to HARQ feedback timing indication, and the PDSCH to HARQ feedback timing indication is used to indicate the M PDSCH The offset value from the time unit where the Xth PDSCH is located to the time unit where the PUCCH is located;

Wherein, the Xth PDSCH is one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, the PDSCH with the smallest associated serving cell index, or , the PDSCH with the largest associated serving cell index.
The method according to claim 16, wherein the last scheduled PDSCH is the PDSCH with the latest end time among the M PDSCHs; wherein the end time is the end time of PDSCH transmission, or The end time is the end time of the time unit where the PDSCH is located.
The method according to any one of claims 1-17, wherein the time units in the first set of time units are one or more of the following: a time slot, a sub-slot, and a or multiple symbols.
A method for wireless communication, comprising:

The network device sends the first downlink control information DCI, the first DCI is used to schedule N physical downlink shared channels PDSCH, the hybrid automatic repeat request-confirmation HARQ-ACK information corresponding to the M PDSCHs in the N PDSCHs In the same physical uplink control channel PUCCH feedback, both M and N are positive integers;

Wherein, the M PDSCHs include the first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the The feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing;

Wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH Or the subcarrier spacing of the second carrier where the PUCCH is located.
The method according to claim 19, wherein the N PDSCHs are respectively located on N carriers, and the M PDSCHs are respectively located on M carriers among the N carriers.
The method according to claim 20, wherein the M carriers belong to the same PUCCH group.
The method according to any one of claims 19-21, wherein the first set of time units is determined based on a first parameter and/or a second parameter, wherein the first parameter is n- k1, the second parameter is
or
The n represents the time unit where the PUCCH is located, the k1 represents elements in the feedback timing set, the μ DL represents the first subcarrier spacing, and the μ UL represents the second subcarrier spacing .
The method of claim 22, wherein the first set of time units comprises time units
in
Indicates rounding down.
The method according to claim 23, wherein the value range of the k1 is an element satisfying the following formula in the feedback timing set:
Where mod(·) represents the remainder operation.
The method according to claim 23 or 24, wherein said μ DL is smaller than said μ UL .
The method of claim 22, wherein the first set of time units comprises time units

to time unit
time unit between.
The method of claim 26, wherein said μ DL is greater than or equal to said μ UL .
The method according to any one of claims 19-27, wherein the first time unit set includes at least one time unit on the first carrier, and the at least one time unit is the same as the second time unit The time units in the unit set overlap in the time domain, and the second time unit set is determined based on the time domain position of the PUCCH and the feedback timing set.
The method according to claim 28, wherein the second set of time units is a time unit {n-k1} on the second carrier, the n represents the time slot where the PUCCH is located, and the k1 represents an element in the feedback timing set.
The method according to any one of claims 19-21, wherein the first set of time units is determined based on a first reference duration, and the first reference duration is determined based on the second subcarrier spacing definite.
The method according to claim 30, wherein the end time of the first reference duration is the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration is the start time of the time unit where the PUCCH is located. The end time of the previous time unit of the time unit.
The method according to any one of claims 19-31, wherein the first PDSCH is located on the first carrier, and the terminal device does not expect the first PDSCH to be located on the first carrier or, the terminal device does not expect the last symbol of the first PDSCH to be located on the first carrier other than the first set of time units outside time unit.
The method according to any one of claims 19-32, wherein the first DCI includes a time domain resource indication field, and the time domain resource indication field includes an index, and the index is used to indicate the The time-domain resource allocation corresponding to each PDSCH in the M PDSCHs or the TDRA row corresponding to each PDSCH in the N PDSCHs.
The method according to any one of claims 19-33, wherein the first DCI includes a PDSCH-to-HARQ feedback timing indication, and the PDSCH-to-HARQ feedback timing indication is used to indicate the timing of the M PDSCHs. The offset value from the time unit where the Xth PDSCH is located to the time unit where the PUCCH is located;

Wherein, the Xth PDSCH is one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, the PDSCH with the smallest associated serving cell index, or , the PDSCH with the largest associated serving cell index.
The method according to claim 34, wherein the last scheduled PDSCH is the PDSCH with the latest end time among the M PDSCHs; wherein the end time is the end time of PDSCH transmission, or The end time is the end time of the time unit where the PDSCH is located.
The method according to any one of claims 19-35, wherein the time units in the first set of time units are one or more of the following: a time slot, a sub-slot, and a or multiple symbols.
A terminal device, characterized in that it includes:

The receiving unit is configured to receive the first downlink control information DCI, the first DCI is used to schedule N physical downlink shared channels PDSCH, and the hybrid automatic repeat request-acknowledgment HARQ corresponding to the M PDSCHs in the N PDSCHs - ACK information is fed back on the same physical uplink control channel PUCCH, and both M and N are positive integers;

Wherein, the M PDSCHs include the first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the The feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing;

Wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH Or the subcarrier spacing of the second carrier where the PUCCH is located.
The terminal device according to claim 37, wherein the N PDSCHs are respectively located on N carriers, and the M PDSCHs are respectively located on M carriers among the N carriers.
The terminal device according to claim 38, wherein the M carriers belong to the same PUCCH group.
The terminal device according to any one of claims 37-39, wherein the first set of time units is determined based on a first parameter and/or a second parameter, wherein the first parameter is n -k1, the second parameter is
or
The n represents the time unit where the PUCCH is located, the k1 represents elements in the feedback timing set, the μ DL represents the first subcarrier spacing, and the μ UL represents the second subcarrier spacing .
The terminal device according to claim 40, wherein the first set of time units includes a time unit
in
Indicates rounding down.
The terminal device according to claim 41, wherein the value range of k1 is an element satisfying the following formula in the feedback timing set:
Where mod(·) represents the remainder operation.
The terminal device according to claim 41 or 42, wherein the μ DL is smaller than the μ UL .
The terminal device according to claim 40, wherein the first set of time units includes a time unit
to time unit
time unit between.
The terminal device according to claim 44, wherein the μ DL is greater than or equal to the μ UL .
The terminal device according to any one of claims 37-45, wherein the first time unit set includes at least one time unit on the first carrier, and the at least one time unit is the same as the second The time units in the time unit set overlap in the time domain, and the second time unit set is determined based on the time domain position of the PUCCH and the feedback timing set.
The terminal device according to claim 46, wherein the set of second time units is a time unit {n-k1} on the second carrier, and the n represents the time slot where the PUCCH is located, so The above k1 represents an element in the feedback timing set.
The terminal device according to any one of claims 37-39, wherein the first set of time units is determined based on a first reference duration, and the first reference duration is determined based on the second subcarrier The interval is fixed.
The terminal device according to claim 48, wherein the end time of the first reference duration is the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration is the start time of the PUCCH The end time of the previous time unit of the current time unit.
The terminal device according to any one of claims 37-49, wherein the first PDSCH is located on the first carrier, and the terminal device does not expect the first PDSCH to be located on the first Time units on the carrier other than the first set of time units; or, the terminal device does not expect the last symbol of the first PDSCH to be located on the first carrier except the first set of time units other time units.
The terminal device according to any one of claims 37-50, wherein the first DCI includes a time domain resource indication field, and the time domain resource indication field includes an index, and the index is used to indicate the The time-domain resource allocation TDRA row corresponding to each PDSCH in the M PDSCHs or the TDRA row corresponding to each PDSCH in the N PDSCHs.
The terminal device according to any one of claims 37-51, wherein the first DCI includes a PDSCH to HARQ feedback timing indication, and the PDSCH to HARQ feedback timing indication is used to indicate that among the M PDSCHs The offset value from the time unit where the Xth PDSCH is located to the time unit where the PUCCH is located;

Wherein, the Xth PDSCH is one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, the PDSCH with the smallest associated serving cell index, or , the PDSCH with the largest associated serving cell index.
The terminal according to claim 52, wherein the last scheduled PDSCH is the PDSCH with the latest end time among the M PDSCHs; wherein the end time is the end time of PDSCH transmission, or The end time is the end time of the time unit where the PDSCH is located.
The terminal device according to any one of claims 37-53, wherein the time units in the first set of time units are one or more of the following: time slots, sub-slots, and One or more symbols.
A network device, characterized in that it includes:

A sending unit, configured to send first downlink control information DCI, where the first DCI is used to schedule N physical downlink shared channels PDSCH, hybrid automatic repeat request-confirmation HARQ corresponding to M PDSCHs in the N PDSCHs - ACK information is fed back on the same physical uplink control channel PUCCH, and both M and N are positive integers;

Wherein, the M PDSCHs include the first PDSCH, the time domain position of the first PDSCH is associated with a first time unit set, and the first time unit set is determined based on at least one of the following information: the The feedback timing set of the terminal device, the first subcarrier spacing and the second subcarrier spacing;

Wherein, the first subcarrier spacing is the subcarrier spacing of the first PDSCH or the subcarrier spacing of the first carrier where the first PDSCH is located, and the second subcarrier spacing is the subcarrier spacing of the PUCCH Or the subcarrier spacing of the second carrier where the PUCCH is located.
The network device according to claim 55, wherein the N PDSCHs are respectively located on N carriers, and the M PDSCHs are respectively located on M carriers among the N carriers.
The network device according to claim 56, wherein the M carriers belong to the same PUCCH group.
The network device according to claim 57, wherein the first set of time units is determined based on a first parameter and/or a second parameter, wherein the first parameter is n-k1, and the second The second parameter is
or
The n represents the time unit where the PUCCH is located, the k1 represents elements in the feedback timing set, the μ DL represents the first subcarrier spacing, and the μ UL represents the second subcarrier spacing .
The network device according to claim 58, wherein the first set of time units comprises a time unit
in
Indicates rounding down.
The network device according to claim 59, wherein the value range of k1 is an element satisfying the following formula in the feedback timing set:
Where mod(·) represents the remainder operation.
The network device according to claim 59 or 60, wherein the μ DL is smaller than the μ UL .
The network device according to claim 58, wherein the first set of time units comprises a time unit
to time unit
time unit between.
The network device according to claim 62, wherein the μ DL is greater than or equal to the μ UL .
The network device according to any one of claims 55-63, wherein the first time unit set includes at least one time unit on the first carrier, and the at least one time unit is the same as the second The time units in the time unit set overlap in the time domain, and the second time unit set is determined based on the time domain position of the PUCCH and the feedback timing set.
The network device according to claim 64, wherein the second set of time units is a time unit {n-k1} on the second carrier, and the n represents the time slot where the PUCCH is located, so The above k1 represents an element in the feedback timing set.
The network device according to any one of claims 55-57, wherein the first set of time units is determined based on a first reference duration, and the first reference duration is determined based on the second subcarrier The interval is fixed.
The network device according to claim 66, wherein the end time of the first reference duration is the start time of the time unit where the PUCCH is located; or, the end time of the first reference duration is the start time of the PUCCH The end time of the previous time unit of the current time unit.
The network device according to any one of claims 55-67, wherein the first PDSCH is located on the first carrier, and the terminal device does not expect the first PDSCH to be located on the first Time units on the carrier other than the first set of time units; or, the terminal device does not expect the last symbol of the first PDSCH to be located on the first carrier except the first set of time units other time units.
The network device according to any one of claims 55-68, wherein the first DCI includes a time domain resource indication field, and the time domain resource indication field includes an index, and the index is used to indicate the The time-domain resource allocation TDRA row corresponding to each PDSCH in the M PDSCHs or the TDRA row corresponding to each PDSCH in the N PDSCHs.
The network device according to any one of claims 55-69, wherein the first DCI includes a PDSCH-to-HARQ feedback timing indication, and the PDSCH-to-HARQ feedback timing indication is used to indicate that among the M PDSCHs The offset value from the time unit where the Xth PDSCH is located to the time unit where the PUCCH is located;

Wherein, the Xth PDSCH is one of the PDSCHs satisfying the following conditions among the M PDSCHs: the first scheduled PDSCH, the last scheduled PDSCH, the PDSCH with the smallest associated serving cell index, or , the PDSCH with the largest associated serving cell index.
The network device according to claim 70, wherein the last scheduled PDSCH is the PDSCH with the latest end time among the M PDSCHs; wherein the end time is the end time of PDSCH transmission, Or the end time is the end time of the time unit where the PDSCH is located.
The network device according to any one of claims 55-71, wherein the time units in the first set of time units are one or more of the following: time slots, sub-slots, and One or more symbols.
A terminal device, characterized in that it includes a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory to execute the program described in any one of claims 1-18 Methods.
A network device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute any one of claims 19-36 Methods.
An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 1-18.
An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 19-36.
A chip, characterized by comprising a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-18.
A chip, characterized by comprising a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of claims 19-36.
A computer-readable storage medium, characterized in that a program is stored thereon, the program causes a computer to execute the method according to any one of claims 1-18.
A computer-readable storage medium, characterized in that a program is stored thereon, and the program causes a computer to execute the method according to any one of claims 19-36.
A computer program product, characterized by comprising a program, the program causes a computer to execute the method according to any one of claims 1-18.
A computer program product, characterized by comprising a program, the program causes a computer to execute the method according to any one of claims 19-36.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1-18.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 19-36.