CN114374486A

CN114374486A - HARQ-ACK transmission method, terminal and network side equipment

Info

Publication number: CN114374486A
Application number: CN202011099463.XA
Authority: CN
Inventors: 陈晓航; 潘学明
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-10-14
Filing date: 2020-10-14
Publication date: 2022-04-19
Anticipated expiration: 2040-10-14
Also published as: CN114374486B; WO2022078288A1

Abstract

The application discloses a transmission method of HARQ-ACK, a terminal and network side equipment, and belongs to the technical field of wireless communication. The method comprises the following steps: receiving second information, wherein the second information is used for scheduling, activating or configuring a PDSCH containing the first PDSCH; receiving first information, wherein the first information indicates a first time domain position or a second time domain position, the first time domain position is the time domain position of the first information, and the second time domain position is the time domain position of one or more PDSCHs; determining a first PDSCH according to the first time domain position or the second time domain position; and sending a first HARQ-ACK corresponding to at least part of the PDSCH in the first PDSCH on the first uplink channel. The method and the device can ensure that the HARQ-ACK is prevented from being discarded due to the conflict between the HARQ-ACK and unavailable resources when the terminal transmits the HARQ-ACK corresponding to the PDSCH, and ensure the transmission of the HARQ-ACK.

Description

HARQ-ACK transmission method, terminal and network side equipment

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a transmission method of HARQ-ACK, a terminal and network side equipment.

Background

For Physical Uplink Control Channel (PUCCH) transmission carrying Hybrid Automatic Repeat request acknowledgement (HARQ-ACK), the HARQ-ACK may be discarded due to collision with Downlink (DL) resources, unavailable (invalid) resources, flexible (flexible) resources, or Physical Uplink Control Channel/Physical Uplink shared Channel (PUCCH/PUSCH) of different priorities, thereby causing performance degradation of downlink transmission.

Disclosure of Invention

The embodiment of the application provides a transmission method of HARQ-ACK, a terminal and a network side device, which can solve the problem that the performance of downlink transmission is reduced because the HARQ-ACK is possibly discarded when the HARQ-ACK conflicts with unavailable resources.

In a first aspect, a method for transmitting HARQ-ACK is provided, which is applied to a terminal, and the method includes:

receiving second information for scheduling, activating or configuring a PDSCH including a first PDSCH;

receiving first information, wherein the first information indicates a first time domain position or a second time domain position, the first time domain position is a time domain position of the first information, and the second time domain position is a time domain position of one or more PDSCHs;

determining the first PDSCH according to the first time domain position or the second time domain position;

and sending a first HARQ-ACK corresponding to at least part of PDSCH in the first PDSCH on a first uplink channel.

In a second aspect, a transmission method for HARQ-ACK is provided, which is applied to a network side device, and the method includes:

sending second information to the terminal, wherein the second information is used for scheduling, activating or configuring a PDSCH containing the first PDSCH;

sending first information to the terminal, wherein the first information is used for determining a first PDSCH; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

and receiving a first HARQ-ACK corresponding to at least part of PDSCH in the first PDSCH sent by the terminal on a first uplink channel.

In a third aspect, an apparatus for transmitting HARQ-ACK is provided, including:

a first receiving module, configured to receive second information, where the second information is used to schedule, activate, or configure a PDSCH including a first PDSCH;

the second receiving module is used for receiving the first information; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

a determining module, configured to determine a first PDSCH according to the first time domain position or the second time domain position;

and a sending module, configured to send a first HARQ-ACK corresponding to at least a part of the PDSCH in the first PDSCH on a first uplink channel.

In a fourth aspect, an apparatus for transmitting HARQ-ACK is provided, including:

a first sending module, configured to send second information to a terminal, where the second information is used to schedule, activate, or configure a PDSCH including a first PDSCH;

a second sending module, configured to send first information to the terminal, where the first information is used to determine a first PDSCH; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

a receiving module, configured to receive a first HARQ-ACK corresponding to at least a part of PDSCHs in the first PDSCH sent by the terminal on a first uplink channel.

In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

In a sixth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the second aspect.

In a ninth aspect, there is provided a program product stored on a non-volatile storage medium, the program product being executable by at least one processor to implement a method as in the first aspect, or to implement a method as in the second aspect.

In the embodiment of the application, the terminal determines the first PDSCH according to the first information sent by the network side equipment, and sends the HARQ-ACK corresponding to at least part of the PDSCH in the first PDSCH on the appointed uplink channel, so that the terminal can be ensured to avoid discarding the HARQ-ACK due to the conflict between the HARQ-ACK and unavailable resources when the HARQ-ACK is transmitted, the transmission of the HARQ-ACK is ensured, and the transmission performance of the PDSCH is improved.

Drawings

FIG. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a diagram of the types of symbols included in a slot;

fig. 3 is a flowchart illustrating a transmission method of HARQ-ACK applied to a terminal according to an embodiment of the present application;

fig. 4 is a diagram illustrating an example of a transmission method of HARQ-ACK according to an embodiment of the present application;

fig. 5 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 6 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 7 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 8 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 9 is a flowchart illustrating a transmission method of HARQ-ACK applied to a network side device according to an embodiment of the present application;

fig. 10 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 11 is a diagram illustrating a transmission method of HARQ-ACK according to another embodiment of the present application;

fig. 12 is a diagram illustrating an apparatus for transmitting HARQ-ACK according to an embodiment of the present application;

fig. 13 is a diagram illustrating an apparatus for transmitting HARQ-ACK according to another embodiment of the present application;

fig. 14 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 15 is a schematic hardware configuration diagram of a terminal according to an embodiment of the present application;

fig. 16 is a schematic hardware structure diagram of a network-side device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, and the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation) NR systems^thGeneration, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

First, some technical contents related to the present application are introduced.

1.1 semi-persistent scheduling (SPS)

Compared with the existing mobile communication system, the future 5G mobile communication system needs to adapt to more diversified scenes and service requirements. The main scenes of NR include mobile broadband enhancement (eMBB), large-scale internet of things (mtc), and ultra-high-reliability ultra-low-latency communication (URLLC), and these scenes impose requirements on the system for high reliability, low latency, large bandwidth, wide coverage, and the like.

These different services have different Quality of Service (QoS) requirements, e.g., URLLC supports low-latency, high-reliability services. To achieve higher reliability, data needs to be transmitted using a lower code rate, and faster and more accurate feedback of Channel State Information (CSI) is needed. The eMBB service supports the requirement of high throughput, but is less sensitive to latency and reliability than URLLC. In addition, for some UEs which may support services with different numerical configurations (numerology), the UE supports both URLLC low-latency high-reliability services and high-capacity high-rate eMBB services.

For a service which occurs periodically and has a fixed data packet size, in order to reduce the overhead of downlink control signaling, the network may continuously allocate a certain resource for the transmission of the periodic service in a semi-static scheduling manner. This type of Downlink semi-persistent scheduling is called DL SPS (semi-persistent scheduling), and can reduce the overhead of scheduling the periodically transmitted and small VoLTE voice packets (mainly the overhead of a Physical Downlink Control Channel (PDCCH)), so that more resources are available for scheduling additional UEs.

1.2 unlicensed frequency band

In future communication systems, an unlicensed band (unlicensed band) may be used as a supplement to a licensed band (licensed band) to help an operator to expand the capacity of a service. In order to maintain compliance with NR deployment and maximize NR-based unlicensed access as much as possible, unlicensed bands may operate in the 5GHz, 37GHz, and 60GHz bands. The large bandwidth (80 or 100MHz) of the unlicensed band can reduce the implementation complexity of the base station and the UE. Since the unlicensed frequency band is shared by multiple technologies (RATs), such as WiFi, radar, LTE-LAA, etc., in some countries or regions, the unlicensed frequency band must meet rules (regulations) to ensure that all devices can fairly use the resources, such as Listen Before Talk (LBT), Maximum Channel Occupancy Time (MCOT), etc. When a transmission node needs to send information, LBT needs to be performed first, power detection (ED) is performed on surrounding nodes, and when the detected power is lower than a threshold, a channel is considered to be empty (idle), and the transmission node can send the information. Otherwise, the channel is considered to be busy, and the transmitting node cannot transmit. The transmission node may be a base station, a UE, a WiFi AP, etc. After the transmission node starts transmission, the occupied channel time COT cannot exceed the MCOT.

1.3 Downlink semi-persistent scheduling (DL SPS)

The network configures parameters required by the DL SPS for the UE through high-level signaling, such as a period, a Hybrid Automatic Repeat reQuest (HARQ) process number, HARQ-ACK feedback resources, and the like. After the UE configures the DL SPS configuration, the base station activates the configured DL SPS configuration through Downlink Control Information (DCI). The DCI includes transmission parameters such as DL SPS transmission resources and Modulation and Coding Scheme (MCS). The UE determines the time instant of the DL SPS transmission and the frequency resources at the corresponding time instant by receiving the activation DCI. At each DL SPS time, the UE will listen for a corresponding data transmission on the DL SPS resources.

If the network is to release the allocated DL SPS resources, the base station may send a deactivation DCI to release the DL SPS resources.

In addition, the network may configure the UE with one or more DL SPS configuration resources.

1.4HARQ-ACK timing (HARQ-ACK timing)

HARQ-ACK timing is defined as the interval from the end time of downlink data reception to the time of corresponding ACK/NACK feedback. NR supports flexible HARQ-ACK timing configuration for adapting to different services and network deployments. Each UE may configure a UE-specific HARQ-ACK timing table through Radio Resource Control (RRC), where the table includes multiple HARQ-ACK timing values, referred to as K1 values, and K1 is slot-by-slot. When the base station dynamically schedules downlink data transmission, a value of K1 is indicated in DCI in an index manner, where K1 is a value selected from a UE-specific HARQ-ACK timing table and is used to notify the UE of the time when HARQ-ACK is fed back.

If the field indicating the HARQ-ACK timing is not included in the DCI, the UE may determine an interval of the downlink data to HARQ-ACK feedback according to a fixed value.

For one DL SPS PDSCH sent at slot n, its corresponding HARQ-ACK is transmitted on slot n + K, where K is indicated in the DCI activating the DL SPS.

1.5HARQ-ACK codebook (codebook):

for HARQ-ACK processes supporting transport block level (TB-level) feedback, each Transport Block (TB) corresponds to feeding back one HARQ-ACK bit (bit), supporting multiple DL HARQ processes per UE, and also supporting a single DL HARQ process per UE, the UE needs the capability to indicate its minimum HARQ processing time (minimum HARQ processing time means the minimum time required to receive the corresponding HARQ-ACK transmission timing from Downlink data). Asynchronous and adaptive Downlink HARQ is supported for eMBB and URLLC. From the UE perspective, HARQ-ACK feedback for multiple PDSCHs may be transmitted in time in one UL data/control region, constituting one HARQ-ACK codebook on this UL. The timing between PDSCH reception and the corresponding ACK/NACK is specified in DCI (see PDSCH-to-HARQ timing indicators in DCI 1_0, DCI 1_ 1).

In R15, two types of HARQ-ACK codebook are supported, type1 (type-1): semi-static HARQ-ACK codebook and type2 (type-2): dynamic (dynamic) HARQ-ACK codebook. For semi-static HARQ-ACK codebook, the UE determines all PDSCHs that may be fed back in a certain time slot to determine HARQ-ACK codebook according to parameters such as detection opportunity (PDCCH monitoring interference) of PDCCH configured by RRC, time domain resource allocation (PDSCH-time domain resource allocation) of PDSCH, feedback timing (dl-datatoaul-ACK or PDSCH-toHARQ-timing) of PDSCH to HARQ-ACK, and the like. For dynamic HARQ-ACK codebook, UE determines HARQ-ACK codebook according to PDSCH actually scheduled, and because only PDSCH actually scheduled is fed back, the size of the codebook of HARQ-ACK is usually smaller than that of semi-static HARQ-ACK codebook. Which type of codebook the UE specifically uses is determined by RRC configuration.

1.6PUCCH resource determination

In Rel-15, a base station may configure one or more (at most 4) PUCCH resource sets (PUCCH resource sets) for each UE through RRC signaling, and the RRC configures or predefines the maximum bit number of Uplink Control Information (UCI) payload that each resource set (RESET) can carry (e.g., the first RESET is at most 2 bits, the 2 rd 3 rd RESET is N1, N2, the 4 th RESET is at most 1706 bits, N1, N2 is RRC configuration), and each RESET may include multiple PUCCH resources (at most 32 PUCCH resources in the first RESET, and other RESETs each include at most 8 PUCCH resources). On the UE side, the UE needs to feed back HARQ-ACK after receiving the PDSCH, in order to determine the PUCCH resource where the HARQ-ACK is fed back, the UE needs to determine a slot (slot) where the PUCCH is located through K1 in the PDCCH for scheduling the PDSCH, then determine a RESET where the PUCCH is located through the number of bits of the HARQ-ACK that needs to be fed back, and determine which PUCCH resource in the RESET is specifically determined according to a PRI (PUCCH resource indicator) field (when resources included in the RESET are not more than 8) of the PDCCH or a first Control Channel Element (CCE) index (first CCE index) of the PRI + PDCCH (when resources included in the RESET exceed 8). When there is a plurality of HARQ-ACK feedbacks in a slot (slot), UE determines PUCCH resource according to PRI and CCE index in the last DCI (last DCI) for scheduling PDSCH.

1.7 time Slot format (Slot format)

In order to implement flexible network deployment, in an NR system, a transmission direction of each symbol in one slot is configured in a slot format (slot format).

The transmission direction of the timeslot in NR has three definitions, Downlink (DL), Uplink (UL), and flexible. When the network configures a timeslot or a symbol to be DL or UL, the transmission direction at that time is clear; when the network configures a slot or a symbol to be flexible, the transmission direction at that time is pending. The network may modify the transmission direction of the slot or symbol of the flexible by dynamic signaling, such as a dynamic Slot Format Indicator (SFI).

As shown in fig. 2, one slot may include downlink (downlink), uplink (uplink) and flexible (flexible) Orthogonal Frequency Division Multiplexing (OFDM) symbols; the Flexible symbol may be rewritten as a downlink or uplink symbol.

A Slot Format Indicator (SFI) may indicate the format of one or more slots. The SFI is transmitted in the GC-PDCCH.

The SFI can flexibly change the slot format according to the requirement so as to meet the service transmission requirement.

And the UE decides whether to monitor the PDCCH or not according to the indication of the SFI.

slot configuration:

the base station may semi-statically configure the UE with one or more cell-specific slot formats via the higher layer parameters UL-DL-configuration-common and UL-DL-configuration-common-Set2 (optional).

The base station may also semi-statically UE configure one or more UE-specific slot formats with a higher layer parameter UL-DL-configuration-determined.

The base station can rewrite the flexible symbol or slot in the semi-static configuration through the SFI carried in the GC-PDCCH.

The transmission direction implicitly indicated by the UE-specific RRC configuration is collectively referred to as measurement (measurement), including:

the method comprises the steps of UE-dedicated periodic or semi-static CSI-RS measurement configured by RRC signaling, periodic CSI reporting and uplink and downlink transmission directions implicitly indicated by a periodic or semi-static SRS.

UE-specific RRC-configured Physical Random Access Channel (PRACH) resources, type1 and type2, are unlicensed for uplink transmission.

For unlicensed upstream transmission of type2, only the transmission on the first active resource is treated as UE-specific data.

The UE-specific transmission comprises PDCSH, ACK/NACK feedback of PUSCH (Physical Uplink Shared Channel), PDSCH (Physical Downlink Shared Channel), DCI triggered aperiodic measurement and the like.

1.8NR R16 PUCCH/PUSCH priority (priority)

In NR 16, it is considered that one UE may support different services at the same time, and the different services correspond to different service requirements, such as time delay, reliability, and the like. Therefore, a mechanism for marking the priority of the PUCCH/PUSCH channel is introduced, and specifically, the priority of a 2-level physical layer is introduced, namely high priority and low priority. The priority of HARQ-ACK such as Scheduling Request (SR), CG PUSCH (physical uplink shared channel), SPS PDSCH (physical downlink shared channel) and release (release) thereof is configured by RRC signaling and is considered low priority for P-CSI or SP-CSI on PUCCH. For HARQ-ACK for dynamically scheduled PDSCH, DG PUSCH, a-CSI/SP-CSI on PUSCH, etc. are indicated by 1-bit field in the corresponding scheduling DCI. The priority of the PUCCH is determined by the HARQ-ACK/SR/CSI carried by the PUCCH. When different channel time domain resources are overlapped, if the different channel time domain resources are overlapped, the multiplexing rule defined by NR R15 is used for processing, and if the different channel time domain resources are not overlapped, the UE discards the channel with low priority and transmits the channel with high priority. If there are both the same priority and different priorities, the UE processes the channels according to the multiplexing rule defined by NR 15, and then processes the channels with different priorities. Meanwhile, when the UE processes different priorities, the UE discards low priority and transmits high priority channels, which also needs a certain processing time, and the R16 protocol defines the requirements of discarding/canceling time when the UE processes different priority channels.

The following describes in detail a transmission method, a terminal, and a network side device of HARQ-ACK provided in the embodiments of the present application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.

Referring to fig. 3, an embodiment of the present application provides a method for transmitting HARQ-ACK, which is applied to a terminal and includes:

step 31: receiving second information for scheduling, activating or configuring a PDSCH including a first PDSCH;

the second information may be downlink grant DCI, dynamically scheduling PDSCH;

the second information may also be DCI activation, PDSCH activation for semi-static scheduling;

the second information may also be RRC, configuring a semi-statically scheduled PDSCH.

Step 32: receiving first information, wherein the first information indicates a first time domain position or a second time domain position, the first time domain position is a time domain position of the first information, and the second time domain position is a time domain position of one or more PDSCHs;

optionally, the time domain position of the PDSCH includes at least one of: starting position, ending position of PDSCH and length of PDSCH.

Step 33: determining the first PDSCH according to the first time domain position or the second time domain position;

step 34: and sending a first HARQ-ACK corresponding to at least part of PDSCH in the first PDSCH on a first uplink channel.

In the embodiment of the application, the terminal determines the first PDSCH according to the first information sent by the network side equipment, and sends the HARQ-ACK corresponding to at least part of the PDSCH in the first PDSCH on the appointed uplink channel, so that when the HARQ-ACK is discarded due to conflict between the HARQ-ACK and unavailable resources, the transmission of the HARQ-ACK is ensured, and the transmission performance of the PDSCH is improved.

In this embodiment, the first PDSCH determined according to the first time domain position or the second time domain position may be one or multiple. If the first PDSCH determined according to the first time domain position or the second time domain position is one, the first HARQ-ACK corresponding to the first PDSCH may be sent on the first uplink channel. And if the first PDSCH is determined to be multiple according to the first time domain position or the second time domain position, sending a first HARQ-ACK corresponding to at least part of PDSCH in the first PDSCH on a first uplink channel.

In this embodiment, optionally, the first information may be carried by DCI or a Radio Resource Control (RRC) message. The DCI may be one of:

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

group-common (DCI).

In this embodiment, optionally, the first PDSCH is one or more PDSCHs.

In this embodiment of the present application, optionally, the first PDSCH is a dynamically scheduled PDSCH or a semi-statically scheduled PDSCH.

In this embodiment of the present application, optionally, the semi-statically scheduled PDSCH is an activated semi-statically scheduled PDSCH or a received semi-statically scheduled PDSCH.

In this embodiment of the application, optionally, the first uplink channel is a PUCCH or a PUSCH.

In this embodiment of the present application, optionally, the first uplink channel is scheduled or configured by a network side.

In this embodiment of the application, optionally, the first uplink channel is indicated by the first information or other indication information. The other indication information may be DCI or RRC message.

In this embodiment of the application, optionally, the HARQ-ACK codebook corresponding to the first HARQ-ACK is one of the following types:

a semi-static codebook; i.e., Type 1(Type 1) codebooks;

a dynamic codebook; i.e., Type 2(Type 2) codebooks;

an enhanced dynamic codebook; namely, Enhanced Type2 codebook;

a codebook based on HARQ-ACK procedures; i.e., Type 3(Type 3) codebooks.

A method of how to determine the first PDSCH will be described below.

1) The first information indicates a first time domain position, where the first time domain position is a time domain position of the first information, and at this time, the first PDSCH includes at least one of:

a PDSCH having a starting position or an ending position after the first time domain position;

a PDSCH having a starting position or an ending position located before the first time domain position.

Optionally, the time domain position of the first information is a starting position or an ending position of a downlink channel carrying the first information, and the downlink channel is a physical downlink control channel PDCCH or PDSCH.

Optionally, a distance between the time domain position of the first PDSCH and a first time is greater than or equal to a first time length, the first time length is an initial position of a first uplink channel for sending the first HARQ-ACK, and the first time length is configured or predefined by a network side. The first PDSCH may include one or more PDSCHs.

If the first PDSCH includes a plurality of PDSCHs, a distance between a time domain position of any one PDSCH in the first PDSCH and a first time is greater than or equal to a first duration.

Optionally, the first duration is an offset value K1 between the PDSCH and the HARQ-ACK.

Where K1 is indicated by or configured by the network, K1 may be a slot (slot), a sub-slot (sub-slot), or a symbol (symbol), etc.

Specifically, K1 is an offset value between the PDSCH and the corresponding HARQ-ACK feedback time.

Optionally, the first duration is a first processing time N1.

Optionally, the first processing time may be any one or more of:

PDSCH processing time, such as Tproc, 1;

PUSCH preparation time, such as Tproc, 2;

uplink transmission cancellation time, e.g., Tproc,2+ d 1;

a first multiplexing time, such as Tproc,1+ 1;

a second multiplexing time, such as Tproc,2+ 1;

PUCCH preparation time, e.g., N3.

Optionally, an interval between the time domain position of the first PDSCH and a second time is not greater than a second duration, where the second time is the first time domain position or the second time domain position or the starting position of the first uplink channel, and the second duration is configured or predefined by a network side. The first PDSCH may include one or more PDSCHs.

If the first PDSCH comprises a plurality of PDSCHs, the interval between the time domain position of any one PDSCH in the first PDSCH and the second time is not more than the second time length.

Optionally, the second duration is a maximum value or a minimum value in a network side configuration or a predefined time domain position set.

Referring to fig. 4, in fig. 4, the first information indicates a first time domain position, where the first time domain position is a time domain position t0 of the first information (in this embodiment, t0 is an end position of a PDCCH or a PDSCH carrying the first information), and the first PDSCH is a PDSCH whose start position or end position is located after the first time domain position t0, that is, PDSCH5, PDSCH6 and PDSCH7 in fig. 4. A distance (T1, T2, and T3) between a time domain position (end position) of any one PDSCH in the first PDSCH and a first time T2 is greater than or equal to N1, the first time T2 is a start position of a first uplink channel (PUCCH2) for transmitting the first HARQ-ACK, and N1 is a processing time of the PDSCH or the PUSCH. In this embodiment, optionally, the first information is further used to indicate a PUCCH2 for transmitting the first HARQ-ACK.

Referring to fig. 5, in fig. 5, the first information indicates a first time domain position, where the first time domain position is a time domain position t0 of the first information (in this embodiment, t0 is an end position of a PDCCH or a PDSCH carrying the first information), and the first PDSCH is a PDSCH whose end position is before a first time domain position t0, that is, PDSCH1, PDSCH2, PDSCH3, PDSCH4, and PDSCH5 in fig. 5. The interval between the time domain position (starting position or ending position) of any one PDSCH in the first PDSCH and T0 is not more than T0, and T0 is the maximum value or the minimum value in a network side configuration or a predefined time domain position set.

Referring to fig. 6, in fig. 6, the first information indicates a first time domain position, where the first time domain position is a time domain position t0 of the first information (in this embodiment, t0 is an end position of a PDCCH or a PDSCH carrying the first information), and the first PDSCH is a PDSCH (PDSCH3, PDSCH4, PDSCH5) whose end position is before the first time domain position t0 and a PDSCH (PDSCH6, PDSCH7) whose end position is after the first time domain position t 0. A distance between a time domain position (start position or end position) of any one PDSCH in the first PDSCH and a first time T2 is greater than or equal to N1, the first time T2 is a start position of a first uplink channel (PUCCH2) for transmitting the first HARQ-ACK, N1 is a processing time of the PDSCH or the PUSCH, and a distance between the time domain position of any one PDSCH in the first PDSCH and T0 is not greater than T0, and T0 is a maximum value or a minimum value in a network side configuration or a predefined time domain position set.

In the above figures, DL denotes downlink, UL denotes uplink, and S denotes that the slot includes DL, Flexible, or UL, and in the following similar figures, the same meanings are given and description thereof is not repeated.

2) The first information indicates a second time domain location, the second time domain location being a time domain location of one or more of the first PDSCHs;

21) if the second time domain position is a time domain position, the first PDSCH includes at least one of:

a PDSCH having a starting position or an ending position after the second time domain position;

a PDSCH having a starting position or an ending position that precedes the second time domain position;

a PDSCH located at the second time-domain location.

Optionally, a distance between a time domain position (a starting position or an ending position) of the first PDSCH and a first time is greater than or equal to a first time length, the first time length is a starting position of a first uplink channel for sending the first HARQ-ACK, and the first time length is configured or predefined by a network side. The first PDSCH may include one or more PDSCHs.

Optionally, the first duration is K1.

Optionally, the first duration is a first processing time N1.

Optionally, the first processing time may be any one or more of:

PDSCH processing time, such as Tproc, 1;

PUSCH preparation time, such as Tproc, 2;

uplink transmission cancellation time, e.g., Tproc,2+ d 1;

a first multiplexing time, such as Tproc,1+ 1;

a second multiplexing time, such as Tproc,2+ 1;

PUCCH preparation time, e.g., N3.

Optionally, an interval between the time domain position (start position or end position) of the first PDSCH and a second time is not greater than a second time length, where the second time length is configured or predefined by the network side, and the second time length is the first time domain position or the second time domain position or the start position of the first uplink channel. The first PDSCH may include one or more PDSCHs.

If the first PDSCH includes a plurality of PDSCHs, the interval between the time domain position (start position or end position) of any one PDSCH in the first PDSCH and the second time is not greater than the second time duration,

Referring to fig. 7, in fig. 7, the first information indicates a second time domain position, which is a time domain position t1, and the first PDSCH is a PDSCH whose starting position is located after the second time domain position t1, that is, PDSCH5, PDSCH6 and PDSCH7 in fig. 7. A distance between a time domain position (a start position or an end position) of any one PDSCH in the first PDSCH and a first time t2 is greater than or equal to N1, the first time t2 is a start position of a first uplink channel (PUCCH2) for transmitting the first HARQ-ACK, and N1 is a processing time of the PDSCH or the PUSCH.

22) The second time domain position is a set of time domain positions, and the first PDSCH is a PDSCH in the set of time domain positions.

Further optionally, the first information indicates a candidate PDSCH time window, the second time domain position is a set of time domain positions in the candidate PDSCH time window, and the first PDSCH is a PDSCH in the candidate PDSCH time window.

The candidate PDSCH time window may be one or more slots (slots), one or more subframes (subframes) or one or more symbols (symbols), etc.

The length of the candidate PDSCH time window may be determined according to a network configuration, such as an RRC configuration, or according to a set of offset values K1 for PDSCH and HARQ-ACK feedback.

Specifically, the first information indicates a candidate PDSCH time window, and may be that the indicated candidate PDSCH time window and a contained PDSCH time domain position are determined with a receiving position of the first information as a reference point; the indicated candidate PDSCH time window and the included PDSCH time domain position may also be determined with the starting position of the first uplink channel as a reference point.

Optionally, the first information indicates at least one of the following information: a starting time domain position, an ending time domain position of the set of time domain positions, and a length of the set of time domain positions. For example, the first information indicates a starting time domain position and an ending time domain position of the candidate PDSCH time window.

The first information may also indicate time domain locations of the multiple PDSCHs as the set of time domain locations.

Specifically, the first information indicates time domain positions of the multiple PDSCHs, and may be that the indicated time domain positions of the multiple PDSCHs are determined with the receiving position of the first information as a reference point; the time domain positions of the indicated PDSCHs may also be determined with the starting position of the first uplink channel as a reference point.

Referring to fig. 8, in fig. 8, the first information indicates a second time domain position, which is a set of time domain positions (PDSCH3, PDSCH4, PDSCH5, PDSCH6 and PDSCH7), and the first PDSCH is a PDSCH in the set of time domain positions. A distance between a time domain position of any one PDSCH in the first PDSCH and a first time t2 is greater than or equal to N1, the first time t2 is a starting position of a first uplink channel (PUCCH2) for transmitting the first HARQ-ACK, and N1 is a processing time of the PDSCH or the PUSCH.

3) In some embodiments, the first information indicates a first packet, the first packet being a packet corresponding to one or more of the first PDSCH;

optionally, the first packet includes one or more packets.

Optionally, the packet corresponding to the PDSCH is determined by one of the following methods:

configured by an RRC message;

indicated by the scheduled or activated DCI.

Optionally, the packet corresponding to the PDSCH is indicated by a scheduled or activated DCI display, or implicitly indicated by a format or a Radio Network Temporary Identity (RNTI) of the scheduled or activated DCI.

4) In some embodiments, the first information indicates a first HARQ process, the first HARQ process being a HARQ process corresponding to one or more of the first PDSCH;

optionally, the first HARQ process includes one or more HARQ processes.

Optionally, when the first HARQ process includes multiple HARQ processes, the first HARQ process includes identifiers of the multiple HARQ processes, or includes an identifier of a starting HARQ process and an identifier of an ending HARQ process.

In some embodiments of the present application, 1) above may be combined with 3) and/or 4), i.e. the first information indicates the first packet and/or the first HARQ process in addition to the first time domain location.

At this time, determining the first PDSCH according to the first information includes: and determining the first PDSCH according to the first time domain position and the first grouping and/or the first HARQ process.

In some embodiments of the present application, the above 2) may be combined with 3) and/or 4), i.e. the first information indicates the first packet and/or the first HARQ process in addition to the second time domain location.

At this time, determining the first PDSCH according to the first information includes: and determining the first PDSCH according to the second time domain position and the first grouping and/or the first HARQ process.

In the foregoing embodiments, optionally, the first HARQ-ACK satisfies at least one of the following conditions:

if the HARQ-ACK of the target PDSCH in the first PDSCH is not sent, the HARQ-ACK of the target PDSCH is contained in the first HARQ-ACK, and further, ACK or NACK can be generated for the target PDSCH;

if the HARQ-ACK of the target PDSCH in the first PDSCH has been sent, the first HARQ-ACK does not include the HARQ-ACK of the target PDSCH, or the first HARQ-ACK includes the HARQ-ACK of the target PDSCH, and further, ACK or NACK may be generated for the target PDSCH;

if the time domain position of the target PDSCH in the first PDSCH is a resource which can not be used for downlink transmission, the HARQ-ACK of the target PDSCH is not included in the first HARQ-ACK;

if the target PDSCH needs to be transmitted in the first uplink channel but the first PDSCH does not include the target PDSCH, the first HARQ-ACK does not include HARQ-ACK of the target PDSCH, or the first HARQ-ACK includes HARQ-ACK of the target PDSCH, further, ACK or NACK may be generated for the target PDSCH.

In the foregoing embodiment, if the network side device has indicated the first uplink channel, the terminal transmits HARQ-ACK on the indicated first uplink channel, and in this embodiment of the present application, if the network side device does not indicate the first uplink channel, the method further includes:

determining the feedback position of HARQ-ACK corresponding to the PDSCH according to an offset value K1 between the PDSCH and the HARQ-ACK;

and if the feedback position of the HARQ-ACK corresponding to the PDSCH conflicts with other resources, sending the HARQ-ACK corresponding to the PDSCH through a second uplink channel, wherein the second uplink channel is the uplink channel closest to the PDSCH.

In the embodiment of the application, the transmission of some conflicting HARQ-ACKs is recovered on the uplink resource closest to the PDSCH, so that the phenomenon that a plurality of HARQ-ACKs are transmitted on a certain indicated uplink resource in a concentrated manner, the uplink load is large, and the uplink performance is influenced is avoided.

Optionally, the second uplink channel is a PUCCH or a PUSCH.

Referring to fig. 9, an embodiment of the present application further provides a method for transmitting HARQ-ACK, which is applied to a network device, and includes:

step 91: sending second information to the terminal, wherein the second information is used for scheduling, activating or configuring a PDSCH containing the first PDSCH;

and step 92: sending first information to a terminal, wherein the first information is used for determining a first PDSCH; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

Step 93: and receiving a first HARQ-ACK corresponding to at least part of PDSCH in the first PDSCH sent by the terminal on a first uplink channel.

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

group-common (DCI).

Optionally, the first PDSCH is one or more PDSCHs.

Optionally, the first PDSCH is a dynamically scheduled PDSCH or a semi-persistently scheduled PDSCH.

Optionally, the semi-persistently scheduled PDSCH is an activated semi-persistently scheduled PDSCH or a received semi-persistently scheduled PDSCH.

Optionally, the first uplink channel is a PUCCH or a PUSCH.

Optionally, the first uplink channel is indicated by the network side device through the first information or other indication information.

Optionally, the time domain position of the first information is a starting position or an ending position of a downlink channel carrying the first information, and the downlink channel is a PDCCH or a PDSCH.

Optionally, the second time domain position is a time domain position.

Optionally, the second time domain position is a set of time domain positions, and the first PDSCH is a PDSCH in the set of time domain positions.

Optionally, the first information indicates a candidate PDSCH time window, and the second time domain position is a set of time domain positions in the candidate PDSCH time window.

Optionally, the first information indicates at least one of the following information: a starting time domain position, an ending time domain position of the set of time domain positions, and a length of the set of time domain positions.

Optionally, the first information further indicates at least one of:

a first packet, which is a packet corresponding to one or more PDSCHs in the first PDSCH;

a first HARQ process, wherein the first HARQ process is a HARQ process corresponding to one or more PDSCHs in the first PDSCH.

Optionally, the first packet includes one or more packets.

Optionally, the method further includes:

sending a packet corresponding to the PDSCH to the terminal by one of the following modes:

RRC message configuration;

a DCI indication of scheduling or activation.

Optionally, the packet corresponding to the PDSCH is indicated by a scheduled or activated DCI display, or implicitly indicated by a format of the scheduled or activated DCI or a radio network temporary identifier.

Optionally, the first HARQ process includes one or more HARQ processes.

The HARQ-ACK transmission method according to the embodiment of the present application may also be applied to an unlicensed Frequency band, and a scenario in which HARQ-ACK cannot be transmitted due to LBT, such as a Time Division multiplexing (TDD) or Frequency Division multiplexing (FDD) scenario of the unlicensed Frequency band.

For Semi-Persistent Scheduling (SPS), in the conventional scheme, HARQ-ACK feedback time of each SPS configuration is indicated by respective active Downlink Control Information (DCI), so HARQ-ACKs corresponding to SPS Physical Downlink Shared Channels (PDSCHs) of different SPS configurations may be fed back at different times. And if the HARQ-ACK feedback time corresponding to one SPS PDSCH conflicts with other resources, the HARQ-ACK of the SPS PDSCH is discarded, so that the performance of the SPS PDSCH is reduced.

The HARQ-ACK transmission method is suitable for transmission of the HARQ-ACK of the SPS PDSCH, so that when the terminal transmits the HARQ-ACK corresponding to the SPS PDSCH, the HARQ-ACK is prevented from being discarded due to conflict between the HARQ-ACK and unavailable resources, transmission of the HARQ-ACK is guaranteed, and transmission performance of the SPS PDSCH is improved.

The following description will be given with reference to specific examples.

Examples 1 to 1

The UE receives a first DCI sent by the network side at time t0, where the first DCI indicates a PUCCH or PUSCH at time t2, and the UE transmits a HARQ-ACK corresponding to the first SPS PDSCH carried on the PUCCH or PUSCH at time t 2.

Wherein the first SPS PDSCH is determined according to one or more of:

option 1: SPS PDSCH whose starting position or ending position is located after time t0, where an interval between a time domain position (starting position or ending position) of any one PDSCH in the first SPS PDSCH and time t2 is greater than or equal to K1;

option 2: SPS PDSCH with start or end position between time t0 and time t2-N1 (including time t 2-N1), please refer to fig. 4;

option 3: SPS PDSCH indicated in the first DCI;

3 a: if the first DCI indicates a time domain position, transmitting HARQ-ACK corresponding to the SPS PDSCH of the time domain position and at least part of SPS PDSCH in the SPS PDSCH of which the starting position or the ending position is positioned behind the time domain position on the PUCCH or PUSCH;

3 b: if one time domain position set is indicated in the first DCI, HARQ-ACK corresponding to at least part of SPS PDSCH in the time domain position set is transmitted on the PUCCH or PUSCH.

Where N1 is the first processing time.

Optionally, the first processing time may be any one or more of:

PDSCH processing time, such as Tproc, 1;

PUSCH preparation time, such as Tproc, 2;

uplink transmission cancellation time, e.g., Tproc,2+ d 1;

a first multiplexing time, such as Tproc,1+ 1;

a second multiplexing time, such as Tproc,2+ 1;

PUCCH preparation time, e.g., N3.

The first SPS PDSCH is an activated SPS PDSCH, or, a received SPS PDSCH;

the PUCCH or PUSCH is indicated by the first DCI, which may also be configured by RRC;

the first DCI may be a DCI (dl grant with scheduling PDSCH) for scheduling PDSCH, a DCI (dl grant with scheduling PDSCH) not for scheduling PDSCH, or a DCI (ul grant with scheduling PUSCH) for scheduling PUSCH.

Examples 1 to 2

The terminal receives activation DCI sent by a network side, wherein the activation DCI indicates that K1 is 2; k1 is an offset value between PDSCH and HARQ-ACK feedback;

referring to fig. 10, if the terminal does not receive the DCI indicating the PUCCH2 for transmitting the HARQ-ACK, and the HARQ-ACKs of SPS PDSCHs 1-6 are all delayed to be transmitted to PUCCH1 due to the collision of the feedback positions with DL; the HARQ-ACK feedback position for SPS PDSCH7 is determined to be PUCCH1 according to K1 ═ 2, and therefore is not deferred.

Referring to fig. 11, if the terminal receives DCI at time t0, the DCI indicates PUCCH2 at time t 2; SPS PDSCH 5-7 with the starting position or the ending position between the time t0 and the time t2-N1 (including the time t 2-N1) are transmitted on PUCCH 2;

the original HARQ-ACK feedback position of the SPS PDSCH7 is PUCCH1, and the HARQ-ACK feedback position of the SPS PDSCH7 is delayed to PUCCH2 because the DCI is received to indicate PUCCH2, so that the loads of the PUCCH1 and the PUCCH2 are balanced.

Example 2-1

The network side configures or indicates a candidate (candidates) PDSCH time window corresponding to the SPS HARQ-ACK PUCCH.

For a PUCCH, such as PUCCH1, carrying SPS HARQ-ACK for a given time domain location, the HARQ-ACK contained in PUCCH1 is determined by at least one of:

if the HARQ-ACK of the candidate PDSCH is not transmitted, the HARQ-ACK of the candidate PDSCH is contained in the PUCCH 1;

if the HARQ-ACK of one candidate PDSCH is already sent, the UE does not generate and does not contain the HARQ-ACK of the candidate PDSCH in the PUCCH; or the UE generates HARQ-ACK for the candidate PDSCH and includes the HARQ-ACK for the candidate PDSCH in the PUCCH 1.

If the candidate PDSCH is UL resource or other resource which can not be used for downlink transmission, the HARQ-ACK of the candidate PDSCH is not contained in the PUCCH.

If the HARQ-ACK of one SPS PDSCH is transmitted on the PUCCH1, but the candidate PDSCH time window corresponding to the PUCCH1 does not contain the SPS PDSCH, the UE does not generate and does not contain the HARQ-ACK of the SPS PDSCH in the PUCCH; or the UE generates HARQ-ACK for the SPS PDSCH and includes the HARQ-ACK for the SPS PDSCH in the PUCCH 1.

Optionally, the candidate PDSCH time window corresponding to the PUCCH1 may be indicated or updated by DCI.

Optionally, the DCI is an SPS activation DCI.

Optionally, the RNTI of the DCI is an RNTI of the SPS.

Optionally, the DCI may schedule the PDSCH or not schedule the PDSCH.

Optionally, the PUCCH resource indicated by the DCI is a resource of the PUCCH 1.

Examples 2 to 2

Given by the candidate PDSCH time window, for the number of slots to receive SPS PDSCH, HARQ-ACKs for PDSCH of these slots will be transmitted on the designated PUCCH.

For a given PUCCH, the determination of HARQ-ACK contained in the PUCCH is achieved by:

set j is 0-HARQ-ACK information bit index (sequence number of HARQ-ACK information bit)

Set n_s＝0–slot index

while

if a UE is configured to receive a SPS PDSCH in slot n_s(if the UE is configured in slot n_sReceive SPS PDSCH

if the UE has reported HARQ-ACK information for the SPS PDSCH (if the UE has reported HARQ-ACK information for the SPS PDSCH)

Or ACK

else

end if

j＝j+1；

end if

n_s＝n_s+1；

end while

It should be noted that, in the transmission method of HARQ-ACK provided in the embodiment of the present application, the execution subject may be a transmission apparatus of HARQ-ACK, or a control module in the transmission apparatus of HARQ-ACK for executing the transmission method of HARQ-ACK. In the embodiment of the present application, a method for performing HARQ-ACK transmission by a transmission apparatus for HARQ-ACK is taken as an example to describe the transmission apparatus for HARQ-ACK provided in the embodiment of the present application.

Referring to fig. 12, the present application further provides an apparatus 120 for transmitting HARQ-ACK, including:

a first receiving module 122, configured to receive second information, where the second information is used to schedule, activate, or configure a PDSCH including a first PDSCH;

a second receiving module 122, configured to receive first information, where the first information indicates a first time domain position or a second time domain position, where the first time domain position is a time domain position of the first information, and the second time domain position is a time domain position of one or more PDSCHs;

a determining module 123, configured to determine the first PDSCH according to the first time domain position or the second time domain position;

a sending module 124, configured to send a first HARQ-ACK corresponding to at least a part of the PDSCH in the first PDSCH on the first uplink channel.

Optionally, the time domain position of the first information is a starting position or an ending position of a downlink channel carrying the first information, and the downlink channel is a PDCCH or a PDSCH

Optionally, the first PDSCH includes at least one of:

Optionally, the second time domain position is a time domain position, and the first PDSCH includes at least one of:

a PDSCH located at the second time-domain location.

Optionally, a distance between the time domain position of the first PDSCH and a first time is greater than or equal to a first time length, the first time length is an initial position for sending the first uplink channel, and the first time length is configured or predefined by a network side. The first PDSCH may include one or more PDSCHs.

Optionally, the first information indicates a candidate PDSCH time window, the second time domain position is a set of time domain positions in the candidate PDSCH time window, and the first PDSCH is a PDSCH in the candidate PDSCH time window.

Optionally, the first information further indicates at least one of:

Optionally, the first packet includes one or more packets.

configured by an RRC message;

indicated by the scheduled or activated DCI.

Optionally, the first HARQ process includes one or more HARQ processes.

In this embodiment of the application, optionally, the first information may be carried by DCI or RRC message. The DCI may be one of:

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

group-common (DCI).

Optionally, the first PDSCH is one or more PDSCHs.

Optionally, the first uplink channel is a PUCCH or a PUSCH.

Optionally, the first uplink channel is indicated by the first information or other indication information.

Optionally, the HARQ-ACK codebook corresponding to the first HARQ-ACK is one of the following types:

a semi-static codebook;

a dynamic codebook;

an enhanced dynamic codebook;

a codebook based HARQ-ACK procedure.

The transmission apparatus of HARQ-ACK in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The transmission apparatus of HARQ-ACK in the embodiment of the present application may be an apparatus having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The HARQ-ACK transmission apparatus provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 3 to fig. 8, and achieve the same technical effect, and is not described herein again to avoid repetition.

Referring to fig. 13, the present application further provides an apparatus 130 for transmitting HARQ-ACK, including:

a first sending module 131, configured to send second information to the terminal, where the second information is used to schedule, activate, or configure a PDSCH including the first PDSCH;

a second sending module 132, configured to send first information to the terminal, where the first information is used to determine the first PDSCH; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

a receiving module 133, configured to receive a first HARQ-ACK corresponding to at least a part of PDSCHs in the first PDSCH sent by the terminal on the first uplink channel.

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

group-common (DCI).

Optionally, the first PDSCH is one or more PDSCHs.

Optionally, the first uplink channel is a PUCCH or a PUSCH.

Optionally, the second time domain position is a time domain position.

Optionally, the first information further indicates at least one of:

Optionally, the first packet includes one or more packets.

Optionally, the second sending module is further configured to send a packet corresponding to the PDSCH to the terminal in one of the following manners:

RRC message configuration;

a DCI indication of scheduling or activation.

Optionally, the first HARQ process includes one or more HARQ processes.

As shown in fig. 14, the embodiment of the present application further provides a communication device 140, which includes a processor 141, a memory 142, and a program or an instruction stored in the memory 142 and executable on the processor 141, for example, when the communication device 140 is a terminal, the program or the instruction is executed by the processor 141 to implement the above-mentioned processes of the HARQ-ACK transmission method embodiment applied to the terminal, and the same technical effects can be achieved. When the communication device 140 is a network device, the program or the instruction is executed by the processor 141 to implement the above processes of the HARQ-ACK transmission method embodiment applied to the network device, and can achieve the same technical effect, and the details are not repeated here to avoid repetition.

Fig. 15 is a schematic hardware structure diagram of a terminal implementing the embodiment of the present application. The terminal 150 includes but is not limited to: a radio frequency unit 151, a network module 152, an audio output unit 153, an input unit 154, a sensor 155, a display unit 156, a user input unit 157, an interface unit 158, a memory 159, and a processor 1510.

Those skilled in the art will appreciate that terminal 150 may also include a power source (e.g., a battery) for powering the various components, which may be logically coupled to processor 1510 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The terminal structure shown in fig. 15 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that, in the embodiment of the present application, the input Unit 154 may include a Graphics Processing Unit (GPU) 1541 and a microphone 1542, and the Graphics processor 1541 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 156 may include a display panel 1561, and the display panel 1561 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 157 includes a touch panel 1571 and other input devices 1572. Touch panel 1571, also referred to as a touch screen. Touch panel 1571 may include two portions, a touch detection device and a touch controller. Other input devices 1572 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In this embodiment, the rf unit 151 receives downlink data from a network device and then processes the downlink data in the processor 1510; in addition, the uplink data is sent to the network side equipment. Generally, the radio frequency unit 151 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 159 may be used to store software programs or instructions as well as various data. The memory 159 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 159 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 1510 may include one or more processing units; optionally, the processor 1510 may integrate an application processor, which primarily handles operating system, user interface, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1510.

The radio frequency unit 151 is configured to receive second information, where the second information is used to schedule, activate, or configure a PDSCH including a first PDSCH;

a radio frequency unit 151, further configured to receive first information, where the first information indicates a first time domain position or a second time domain position, where the first time domain position is a time domain position of the first information, and the second time domain position is a time domain position of one or more PDSCHs;

a processor 1510 configured to determine a first PDSCH from the first or second time domain location;

the radio frequency unit 151 is further configured to send a first HARQ-ACK corresponding to at least a part of the PDSCH in the first PDSCH on the first uplink channel.

Optionally, the first PDSCH includes at least one of:

a PDSCH located at the second time-domain location.

If the first PDSCH comprises a plurality of PDSCHs, the interval between the time domain position of any one PDSCH in the first PDSCH and the second time is not more than the second time length,

Optionally, the first information further indicates at least one of:

Optionally, the first packet includes one or more packets.

configured by an RRC message;

indicated by the scheduled or activated DCI.

Optionally, the first HARQ process includes one or more HARQ processes.

Optionally, the first information may be carried by DCI or RRC message. The DCI may be one of:

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

group-common (DCI).

Optionally, the first PDSCH is one or more PDSCHs.

Optionally, the first uplink channel is a PUCCH or a PUSCH.

a semi-static codebook;

a dynamic codebook;

an enhanced dynamic codebook;

a codebook based HARQ-ACK procedure.

The embodiment of the application also provides network side equipment. As shown in fig. 16, the network device 160 includes: antenna 161, radio frequency device 162, baseband device 163. The antenna 161 is connected to a radio frequency device 162. In the uplink direction, rf device 162 receives information via antenna 161 and sends the received information to baseband device 163 for processing. In the downlink direction, the baseband device 163 processes information to be transmitted and transmits the processed information to the rf device 162, and the rf device 162 processes the received information and transmits the processed information through the antenna 161.

The band processing means may be located in the baseband means 163, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 163, where the baseband means 163 includes a processor 164 and a memory 165.

The baseband device 163 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 16, wherein one chip, for example, the processor 164, is connected to the memory 165 to call up the program in the memory 165 to perform the network device operations shown in the above method embodiments.

The baseband device 163 may further include a network interface 166, such as a Common Public Radio Interface (CPRI), for exchanging information with the radio frequency device 162.

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 165 and executable on the processor 164, and the processor 164 calls the instructions or programs in the memory 165 to perform the method executed by each module shown in fig. 9, and achieve the same technical effects, which are not described herein for avoiding repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing HARQ-ACK transmission method embodiment applied to a terminal or a network device, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, so as to implement each process of the above HARQ-ACK transmission method embodiment applied to a terminal or a network-side device, and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

An embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the foregoing HARQ-ACK transmission method embodiment applied to a terminal or a network device, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the above embodiment of the sending method for PDCCH, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A transmission method of hybrid automatic repeat request acknowledgement (HARQ-ACK) is applied to a terminal and is characterized by comprising the following steps:

receiving second information, wherein the second information is used for scheduling, activating or configuring a PDSCH (physical downlink shared channel) containing a first PDSCH (physical downlink shared channel);

2. The method of claim 1, wherein the time domain position of the first information is a starting position or an ending position of a downlink channel carrying the first information, and the downlink channel is a Physical Downlink Control Channel (PDCCH) or a PDSCH.

3. The method of claim 1, wherein the first PDSCH comprises at least one of:

4. The method of claim 1, wherein the second time domain position is one time domain position, and wherein the first PDSCH comprises at least one of:

a PDSCH located at the second time-domain location.

5. The method of claim 1, wherein a distance between a time domain position of the first PDSCH and a first time is greater than or equal to a first duration, the first time is a starting position for transmitting the first uplink channel, and the first duration is configured or predefined by a network side.

6. The method of claim 1, wherein an interval between the time domain position of the first PDSCH and a second time is not greater than a second duration, wherein the second time is the first time domain position or the second time domain position or a starting position of the first uplink channel, and wherein the second duration is configured or predefined by a network side.

7. The method of claim 1, wherein the second time domain location is a set of time domain locations, and wherein the first PDSCH is a PDSCH in the set of time domain locations.

8. The method of claim 7, wherein the first information indicates a candidate PDSCH time window, and wherein the second time domain position is a set of time domain positions in the candidate PDSCH time window.

9. The method of claim 7, wherein the first information indicates at least one of: a starting time domain position, an ending time domain position of the set of time domain positions, and a length of the set of time domain positions.

10. The method of claim 1, wherein the first information further indicates at least one of:

a first hybrid automatic repeat request HARQ process, wherein the first HARQ process is a HARQ process corresponding to one or more PDSCHs in the first PDSCH.

11. The method of claim 10, wherein the first packet comprises one or more packets.

12. The method of claim 10, wherein the packet corresponding to the PDSCH is determined by one of:

configured by a radio resource control, RRC, message;

indicated by the scheduled or activated downlink control information DCI.

13. The method of claim 12, wherein the packet corresponding to the PDSCH is indicated by a scheduled or activated DCI display or implicitly indicated by a format of the scheduled or activated DCI or a radio network temporary identity.

14. The method of claim 10, wherein the first HARQ process comprises one or more HARQ processes.

15. The method as claimed in claim 14, wherein the first HARQ process comprises a plurality of HARQ processes, and comprises an identifier of a plurality of HARQ processes, or comprises an identifier of a starting HARQ process and an identifier of an ending HARQ process.

16. The method of claim 1, wherein the first information is carried by one of:

dynamically scheduling DCI of the PDSCH;

DCI of an unscheduled PDSCH;

dynamically scheduling DCI of PUSCH;

a group common DCI;

RRC message.

17. The method of claim 1, wherein the first PDSCH is a dynamically scheduled PDSCH or a semi-persistently scheduled PDSCH.

18. The method of claim 17, wherein the semi-persistently scheduled PDSCH is an activated semi-persistently scheduled PDSCH or a received semi-persistently scheduled PDSCH.

19. The method according to claim 1, wherein the first uplink channel is a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH).

20. The method of claim 1, wherein the first uplink channel is indicated by the first information or other indication information.

21. The method of claim 1, wherein the HARQ-ACK codebook for the first HARQ-ACK is one of the following types:

a semi-static codebook;

a dynamic codebook;

an enhanced dynamic codebook;

a codebook based HARQ-ACK procedure.

22. A transmission method of HARQ-ACK is applied to network side equipment, and is characterized by comprising the following steps:

sending first information to the terminal, wherein the first information is used for determining the first PDSCH; the first information indicates a first time domain position or a second time domain position, the first time domain position being a time domain position of the first information, the second time domain position being a time domain position of one or more PDSCHs;

23. An apparatus for transmitting HARQ-ACK, comprising:

24. An apparatus for transmitting HARQ-ACK, comprising:

25. A terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the method for transmission of HARQ-ACK according to any of claims 1 to 22.

26. A network side device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the transmission method of HARQ-ACK according to claim 23.

27. A readable storage medium, on which a program or instructions are stored, which program or instructions, when executed by a processor, carry out the method of transmission of HARQ-ACK according to any one of claims 1 to 22, or the steps of the method of transmission of HARQ-ACK according to claim 23.