CN115943594A

CN115943594A - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN115943594A
Application number: CN202080103201.8A
Authority: CN
Inventors: 吴作敏
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-09-22
Filing date: 2020-09-22
Publication date: 2023-04-07
Also published as: WO2022061548A1

Abstract

A method, a terminal device and a network device of wireless communication, the method comprising: the method comprises the steps that terminal equipment receives first downlink control information DCI sent by network equipment, wherein the first DCI is used for scheduling a first hybrid automatic repeat request (HARQ) process to transmit a first Transport Block (TB), the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and the maximum HARQ process number indicated by an HARQ process number indication field in the first DCI format is a first numerical value; and the terminal equipment transmits the first TB through the first HARQ process.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a wireless communication method, terminal equipment and network equipment.

Background

The number of HARQ processes is increased as a terminal capability, the number of Hybrid Automatic Repeat reQuest (HARQ) processes supported by some terminal devices may be greater than 16, the number of HARQ processes supported by some terminal devices may not be greater than 16, or the number of HARQ processes supported by all terminal devices is not greater than 16. In this case, how to schedule data to ensure that the network device and the terminal device have consistent understanding of the HARQ process numbers for scheduling data transmission is an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, which are beneficial to ensuring that the network equipment and the terminal equipment have consistent understanding on HARQ process numbers corresponding to scheduled data transmission when the network equipment schedules data transmission through a first DCI format.

In a first aspect, a method of wireless communication is provided, including: the method comprises the steps that terminal equipment receives first Downlink Control Information (DCI) sent by network equipment, wherein the first DCI is used for scheduling a first hybrid automatic repeat request (HARQ) process to transmit a first Transport Block (TB), the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and the HARQ process number in the first DCI format indicates that the maximum HARQ process number indicated by a domain is a first numerical value; and the terminal equipment transmits the first TB through the first HARQ process.

In a second aspect, a method of wireless communication is provided, including: the network equipment sends first downlink control information DCI to terminal equipment, wherein the first DCI is used for scheduling a first hybrid automatic repeat request (HARQ) process to transmit a first Transport Block (TB), the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a HARQ process number in the first DCI format indicates that a maximum HARQ process number indicated by a domain is a first numerical value.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the terminal device comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

In a fourth aspect, a network device is provided for performing the method of the second aspect or any possible implementation manner of the second aspect. In particular, the network device comprises means for performing the method of the second aspect described above or any possible implementation of the second aspect.

In a fifth aspect, a terminal device is provided, where the terminal device includes: including a processor and memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided, which includes: including a processor and memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.

In a seventh aspect, a chip is provided, which is configured to implement the method in any one of the first aspect to the second aspect or each implementation manner thereof.

Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manner thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Based on the above technical solution, the network device may schedule the terminal device through the first DCI format to perform transmission of the first transport block TB, and the terminal device may determine the target HARQ process number used for data transmission scheduled by the first DCI format in a corresponding manner when the first DCI format supports different HARQ process numbers, so as to ensure that the terminal device and the network device understand the scheduled HARQ process number consistently.

Drawings

Fig. 1A to fig. 1C are schematic diagrams of an application scenario provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of one relationship between the number of HARQ processes and RTT.

Fig. 3 is a schematic diagram of a method of wireless communication provided by an embodiment of the present application.

Fig. 4 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

Fig. 5 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of a communication device according to another embodiment of the present application.

Fig. 7 is a schematic block diagram of a chip provided in an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art without making any creative effort for the embodiments in the present application belong to the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global System for Mobile communications (GSM) System, code Division Multiple Access (CDMA) System, wideband Code Division Multiple Access (WCDMA) System, general Packet Radio Service (GPRS), long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, new Radio (NR) System, evolution System of NR System, LTE-based Access to unlicensed spectrum, LTE-U) System, NR-based to unlicensed spectrum (NR-U) System, non-Terrestrial communication network (NTN) System, universal Mobile Telecommunications System (UMTS), wireless Local Area Network (WLAN), wireless Fidelity (WiFi), 5th-Generation (5G) System, or other communication systems.

Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technologies, mobile Communication systems will support not only conventional Communication, but also, for example, device to Device (D2D) Communication, machine to Machine (M2M) Communication, machine Type Communication (MTC), vehicle to Vehicle (V2V) Communication, or Vehicle networking (V2X) Communication, and the embodiments of the present application can also be applied to these Communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; alternatively, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where the licensed spectrum may also be considered as an unshared spectrum.

Optionally, the communication system in the embodiment of the present application may be applied to an FR1 frequency band (corresponding to a frequency band range of 410MHz to 7.125 GHz), an FR2 frequency band (corresponding to a frequency band range of 24.25GHz to 52.6 GHz), and a new frequency band, for example, a high-frequency band corresponding to a frequency band range of 52.6GHz to 71 GHz.

Optionally, the embodiment of the present application may be applied to a Non-Terrestrial network (NTN) system, and may also be applied to a Terrestrial Network (TN) system.

Various embodiments are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment.

The terminal device may be a STATION (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) STATION, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next generation communication system such as an NR Network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet personal computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical treatment (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), or the like. The terminal device according to the embodiment of the present application may also be referred to as a terminal, a User Equipment (UE), an access terminal device, a vehicle-mounted terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent, or a UE apparatus. The terminal equipment may also be fixed or mobile.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of equipment that uses wearable technique to carry out intelligent design, develop can dress to daily wearing, such as glasses, gloves, wrist-watch, dress and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application function, and need to be matched with other equipment such as a smart phone for use, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In this embodiment, the network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB, eNodeB) in LTE, a relay Station or an Access Point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, a network device in a future evolved PLMN network, or a network device in an NTN network.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a geosynchronous Orbit (GEO) satellite, a High Elliptic Orbit (HEO) satellite, and the like. Alternatively, the network device may be a base station installed on land, water, or the like.

In this embodiment, a network device may provide a service for a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells), and the like, and the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.

Fig. 1A is a schematic structural diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 1A, the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area.

Fig. 1A exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and each network device may include other number of terminal devices within a coverage area, which is not limited in this embodiment of the present invention.

For example, fig. 1B is a schematic architecture diagram of another communication system provided in the embodiment of the present application. Referring to fig. 1B, the terminal device 1101 and the satellite 1102 are included, and wireless communication is enabled between the terminal device 1101 and the satellite 1102. The network formed between the terminal equipment 1101 and the satellite 1102 may also be referred to as the NTN. In the architecture of the communication system shown in fig. 1B, a satellite 1102 may function as a base station, and direct communication may be performed between the terminal device 1101 and the satellite 1102. Under the system architecture, the satellite 1102 may be referred to as a network device. Optionally, the communication system may include a plurality of network devices 1102, and the coverage area of each network device 1102 may include other number of terminal devices, which is not limited in this embodiment of the present application.

For example, fig. 1C is a schematic architecture diagram of another communication system provided in the embodiment of the present application. Referring to fig. 1C, terminal device 1201, satellite 1202, and base station 1203 are included, and terminal device 1201 and satellite 1202 may communicate wirelessly, and satellite 1202 and base station 1203 may communicate wirelessly. The network formed between terminal device 1201, satellite 1202, and base station 1203 may also be referred to as an NTN. In the architecture of the communication system shown in fig. 1C, the satellite 1202 may not have the function of a base station, and the communication between the terminal apparatus 1201 and the base station 1203 requires relay through the satellite 1202. Under this system architecture, base station 1203 may be referred to as a network device. Optionally, the communication system may include a plurality of network devices 1203, and the coverage area of each network device 1203 may include other number of terminal devices, which is not limited in this embodiment of the present application.

It should be noted that fig. 1A to fig. 1C illustrate only an exemplary system to which the present application is applied, and of course, the method shown in the embodiment of the present application may also be applied to other systems, for example, a 5G communication system, an LTE communication system, and the like, which is not specifically limited in the embodiment of the present application.

Optionally, the wireless communication system shown in fig. 1A to 1C may further include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), and the like, which is not limited in this embodiment of the present invention.

It should be understood that, in the embodiments of the present application, a device having a communication function in a network/system may be referred to as a communication device. Taking the communication system 100 shown in fig. 1A as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication of an association relationship. For example, a indicates B, which may mean that a directly indicates B, e.g., B may be obtained by a; it may also mean that a indicates B indirectly, e.g. a indicates C, by which B may be obtained; it can also be shown that there is an association between a and B.

In the description of the embodiments of the present application, the term "correspond" may indicate that there is a direct correspondence or an indirect correspondence between the two, may also indicate that there is an association between the two, and may also indicate and is indicated, configure and is configured, and the like.

In the embodiment of the present application, "predefining" may be implemented by saving a corresponding code, table, or other manners that may be used to indicate related information in advance in a device (for example, including a terminal device and a network device), and the present application is not limited to a specific implementation manner thereof. Such as predefined, may refer to what is defined in the protocol.

In the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and for example, may include an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.

In order to better understand the embodiments of the present application, the HARQ mechanism and HARQ-ACK feedback mechanism related to the present application will be described first.

HARQ mechanism in NR systems

There are two levels of retransmission mechanisms in NR systems: a Hybrid Automatic Repeat reQuest (HARQ) mechanism of a Media Access Control (MAC) layer and an Automatic Repeat reQuest (ARQ) mechanism of a Radio Link Control (RLC) layer. Retransmission of lost or erroneous data is mainly handled by the HARQ mechanism of the MAC layer and is supplemented by the retransmission function of the RLC layer. The HARQ mechanism of the MAC layer can provide fast retransmission and the ARQ mechanism of the RLC layer can provide reliable data transmission.

HARQ uses a Stop-and-Wait Protocol (Stop-and-Wait Protocol) to transmit data. In the stop-wait protocol, the initiator stops to wait for an acknowledgement after transmitting a Transport Block (TB) once. Thus, the sender may stop waiting for an acknowledgement after each transmission, resulting in low user throughput. Therefore, NR uses a plurality of parallel HARQ processes, and when one HARQ process is waiting for acknowledgement information, the transmitting end can continue to transmit data using another HARQ process. These HARQ processes together constitute a HARQ entity that incorporates a stop-and-wait protocol, allowing for continuous transmission of data. HARQ has a difference between uplink HARQ and downlink HARQ. Uplink HARQ is for uplink data transmission and downlink HARQ is for downlink data transmission. The two are independent of each other.

In some cases, the terminal device has a separate HARQ entity for each serving cell. Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes. As an example, each uplink and downlink carrier supports a maximum of 16 HARQ processes. The network device may indicate the maximum HARQ process number to the terminal device through Radio Resource Control (RRC) signaling semi-static configuration according to a deployment situation of the network device. Optionally, in some embodiments, if the network device does not provide the corresponding configuration parameter, the downlink default number of HARQ processes is 8, and the maximum number of HARQ processes supported by each uplink carrier is always 16. Each HARQ process corresponds to a HARQ process ID (also referred to as HARQ process number). For downlink, a Broadcast Control CHannel (BCCH) uses a dedicated Broadcast HARQ process. For uplink, message 3 (Msg 3) transmission in the random procedure uses HARQ ID 0.

In some embodiments, for a terminal device that does not support downlink space division multiplexing, each downlink HARQ process can only process 1 TB at the same time; for a terminal device supporting downlink space division multiplexing, each downlink HARQ process may process 1 or 2 TBs simultaneously. Each uplink HARQ process of the terminal device processes 1 TB simultaneously.

HARQ is classified into two types, synchronous and asynchronous, in the time domain, and non-adaptive and adaptive, in the frequency domain. The NR uplink and downlink use asynchronous adaptive HARQ mechanisms. For asynchronous HARQ, the time interval between the retransmission of the same TB and the last transmission is not fixed. Adaptive HARQ may change the frequency domain resources and MCS used for the retransmission.

With reference to fig. 2, the relationship between the number of supported HARQ processes and RTT will be described by taking downlink transmission as an example. As shown in fig. 2, the maximum number of HARQ processes configured for the terminal device is 16, and in a case that the RTT is small, for example, less than 16ms, the maximum throughput of the terminal device is not affected, or in other words, if the RTT is less than 16ms, when there is traffic to be transmitted, the terminal device may always have parallel HARQ processes for data transmission. Of course, if the RTT is large, for example, much greater than 16ms, all HARQ processes of the terminal device may be used for data transmission, and the feedback of the network device is not obtained, so that the terminal device has a service to be transmitted but no HARQ process can be used, and throughput of data transmission at the terminal device side may be affected.

In the NTN system, the RTT of signal transmission is large due to the long communication distance between the terminal device and the satellite (or the network device). In GEO systems, the RTT of the signal transmission may be on the order of hundreds of milliseconds, for example, the RTT of the signal transmission may be about 600ms at the maximum. In LEO systems, the RTT of the signaling may be on the order of tens of milliseconds. Since RTT of the NTN system is much larger than RTT of the terrestrial communication system, the HARQ mechanism in the NR system is no longer applicable to the NTN system.

As a solution: configuring HARQ processes to disable

The network device may configure de-enabling for at least one downlink HARQ process of the terminal device. For the downlink HARQ process configured to be disabled, the network device can reuse the HARQ process for data transmission without receiving HARQ-ACK information corresponding to feedback of the terminal device for the TB transmitted in the HARQ process. Therefore, the network device can use the disabled HARQ process to schedule a plurality of data packets for the terminal device, thereby reducing the influence of RTT.

As another solution: increasing the number of HARQ processes

Within the range allowed by the terminal device capability, the number of HARQ processes configured for the terminal device by the network device may exceed the maximum number of HARQ processes supported by the NR system. For example, the number of HARQ processes configured for the terminal device by the network device may exceed 16. The increase of the number of HARQ processes indicates that data packets that can be transmitted in parallel between the network device and the terminal device increase, so that the influence caused by RTT can be reduced.

In addition, in a high frequency system, since the supported subcarrier spacing is large, the time occupied by the time slot in the time domain is short. However, the processing time of the terminal device for the scheduled HARQ process does not decrease linearly with increasing subcarrier spacing. Therefore, there may also be a case where all HARQ processes of the terminal device are used for data transmission, and during processing, the terminal device has traffic to be transmitted but no HARQ process can be used, which may affect the throughput of data transmission on the terminal device side. The number of HARQ processes may also be increased in this scenario.

The increase in the number of HARQ processes is one terminal device capability. That is, the number of HARQ processes supported by some terminal devices may be greater than 16, the number of HARQ processes supported by some terminal devices may not be greater than 16, or not all terminal devices may support HARQ processes greater than 16. In this case, how to schedule data to ensure that the network device and the terminal device have consistent understanding of the HARQ process numbers for scheduling data transmission is an urgent problem to be solved. For example, when the terminal device is scheduled by the network device to perform downlink data reception or uplink data transmission, the terminal device needs to determine the HARQ process number corresponding to the downlink data or the uplink data according to the DCI, for example, the HARQ process number indication field in the downlink grant or the uplink grant. For a terminal device supporting the number of HARQ processes greater than 16, assuming that the maximum number of HARQ processes to be indicated is, for example, 32, then the HARQ process number needs to be determined according to 5-bit indication information, and for a non-fallback DCI format, the network device may indicate scheduling of greater than 16 HARQ processes through enhancement, whereas for a fallback DCI format, the HARQ process number indication field is fixed to 4 bits. Since the fallback DCI format is also used for downlink data reception scheduling and uplink data transmission scheduling in the initial access phase, the maximum number of HARQ processes that can be scheduled by the terminal device in the initial access phase is not greater than 16. Therefore, it needs to be ensured that the network device and the terminal device understand the HARQ process number of the scheduled data transmission consistently under different conditions.

Fig. 3 is a schematic flow chart of a method 300 for wireless communication according to an embodiment of the present disclosure. As shown in fig. 3, the method 300 may include at least some of the following:

s310, a network device sends first Downlink Control Information (DCI) to a terminal device, wherein the first DCI corresponds to a first DCI format;

correspondingly, the terminal equipment receives the first DCI.

The first DCI is used to schedule transmission of a first transport block TB through a first HARQ process, where the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a maximum HARQ process number indicated by a HARQ process number indication field in the first DCI format is a first numerical value.

S320, the terminal equipment transmits the first TB through the first HARQ process.

In some embodiments, the first TB is a TB in uplink transmission, that is, the first DCI is used to schedule the terminal device to send the first TB through the first HARQ process, or the first DCI is used to schedule the terminal device to send a first Physical Uplink Shared Channel (PUSCH) through the first HARQ process, where the first PUSCH carries the first TB. In this case, the first HARQ process is an uplink HARQ process and is denoted as a first uplink HARQ process. Then, in S320, the terminal device may send the first TB through the first uplink HARQ process.

In other embodiments, the first TB is a TB in downlink transmission, that is, the first DCI is used to schedule the terminal device to receive the first TB through the first HARQ process, or the first DCI is used to schedule the terminal device to receive a first Physical Downlink Shared Channel (PDSCH) through the first HARQ process, where the first TB is carried in the first PDSCH. In this case, the first HARQ process is a downlink HARQ process, and is denoted as a first downlink HARQ process. The terminal device may receive the first TB through the first downlink HARQ process in S320.

In an embodiment of the present application, the first DCI format may include a HARQ process number indication field, configured to determine a HARQ process number used for scheduled data transmission.

In some embodiments, the HARQ process number indication field is 4 bits, and the HARQ process number used for indication ranges from 0 to 15, in other words, the maximum HARQ process number that can be indicated is 15, i.e. the first value is 15.

In other embodiments, the number of bits included in the HARQ process number indication field may be other values, which are used in other HARQ process number ranges, and the application is not limited thereto. Hereinafter, the first numerical value is described as 15, but the present application is not limited thereto.

In this embodiment of the present application, the terminal device may support a number of HARQ processes greater than the first value, for example, the number of HARQ processes that the terminal device may support is 32.

It should be understood that the number of downlink HARQ processes and the number of uplink HARQ processes of the terminal device may be the same or different, and this is not limited in this application. For example, the number of downlink HARQ processes of the terminal device is configured to be 32, and the number of uplink HARQ processes is configured to be 16. For another example, the number of downlink HARQ processes of the terminal device and the number of uplink HARQ processes are both configured to be 32.

Optionally, in some embodiments, the terminal device may report the number of HARQ processes supported by the terminal device to the network device.

As an embodiment, the terminal device reports downlink capability information of the terminal device to the network device, where the downlink capability information is used to indicate that the number of downlink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled downlink transmission is greater than the first value, where the specific value is equal to the first value plus one.

In this case, if the first TB is a TB in downlink transmission, it may be considered that an HARQ process number range corresponding to the number of downlink HARQ processes configured for the terminal device is the first HARQ process number range, or the maximum HARQ process number for which the terminal device supports scheduled downlink transmission is greater than the first value, where the first HARQ process number range includes HARQ process numbers greater than the first value.

As another embodiment, the terminal device reports uplink capability information of the terminal device to the network device, where the uplink capability information is used to indicate that the number of uplink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value, where the specific value is equal to the first value plus one.

In this case, if the first TB is a TB in uplink transmission, it may be considered that a HARQ process number range corresponding to the uplink HARQ process number configured by the terminal device is a first HARQ process number range, or the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value, where the first HARQ process number range includes HARQ process numbers greater than the first value.

Optionally, in some embodiments, the first DCI format comprises a fallback DCI format.

It should be understood that the application is not limited to the specific DCI formats that the fallback DCI format includes. As an example, the first TB is a TB in downlink transmission, and the first DCI format includes DCI format 1_0; the first TB is a TB in uplink transmission, and the first DCI format includes DCI format 0_0.

Optionally, in some embodiments, the HARQ process number in the fallback DCI format indicates that the size of the field is a fixed value. For example, the HARQ process number indication field in the fallback DCI format is 4 bits, and the HARQ process number used for indication ranges from 0 to 15, in other words, the maximum HARQ process number that can be indicated is 15, that is, the first value is 15.

In some cases, denoted as case 1, the first DCI format supports data transmission scheduling with HARQ process number not greater than the first value, or the first DCI format supports data transmission scheduling with HARQ process number of the first value +1 (e.g. 16), or the first DCI format does not support data transmission scheduling with HARQ process number greater than the first value. The first HARQ process number corresponding to the first HARQ process may be determined according to the HARQ process number indication field in the first DCI, and a value of the first HARQ process number is maximum of the first value.

In other cases, denoted as case 2, the first DCI format supports data transmission scheduling of different HARQ process numbers under different conditions, or the first DCI format supports different HARQ process number ranges under different conditions.

For example, when a first condition is satisfied, the first DCI format supports data transmission scheduling with the HARQ process number not greater than a first value, and when a second condition is satisfied, the first DCI format supports data transmission scheduling with the HARQ process number greater than the first value.

In still other cases, denoted as case 3, the first DCI format supports data transmission scheduling with a HARQ process number greater than a first value, or the first DCI format supports data transmission scheduling with a HARQ process number greater than a first value +1 (e.g., 16).

For the above cases 2 and 3, since the first DCI format needs to indicate the data transmission scheduling with the HARQ process number greater than the first value, as an implementation manner, the data transmission scheduling with the HARQ process number greater than the first value can be supported by increasing the bit number of the HARQ process number indication field in the first DCI format.

As another implementation manner, the number of bits in the HARQ process number indication field in the first DCI is not changed, the maximum value of the HARQ process number indicated by the HARQ process number indication field is a first value, and the first HARQ process number corresponding to the first HARQ process may be greater than the first value, and if the HARQ process number greater than the first value is to be indicated, additional information is needed to assist in determining the target HARQ process number. For example, a first HARQ process number corresponding to the first HARQ process is determined according to the first information and the HARQ process number indication field in the first DCI.

It should be understood that, in the embodiment of the present application, the first information may be any auxiliary information, for example, the first information may be existing information, and different values are assigned to the existing information to indicate different HARQ process number ranges, or an interpretation manner of the existing information may be modified to indicate different HARQ process number ranges, or a final HARQ process number may be determined by using new information in combination with values of an HARQ process number indication field, and the like, which is not limited in the present application.

By way of example and not limitation, the first information includes at least one of:

a Radio Network Temporary Identity (RNTI) corresponding to the first DCI;

a search space (search space) corresponding to the first DCI;

a Control Channel Element (CCE) index range corresponding to the first DCI;

time domain resources corresponding to the first HARQ process scheduled by the first DCI;

a first information field except the HARQ process number indication field in the first DCI;

and a demodulation reference signal (DMRS) sequence corresponding to the first HARQ process scheduled by the first DCI.

Optionally, the CCE index range corresponding to the first DCI may include at least one CCE index value.

It should be understood that, in this embodiment of the present application, the condition of the HARQ process supported by the first DCI format is known to both the network device and the terminal device, and for condition 1, the terminal device only needs to know the HARQ process number corresponding to the data transmission scheduled by the network device from the HARQ process number indication field in the first DCI format, and for conditions 2 and 3, the terminal device may determine the target HARQ process number scheduled by the network according to the first information and the HARQ process number indication field.

Hereinafter, how to indicate the HARQ process number greater than the first value by the first information aid will be described in detail.

It should be noted that, in this embodiment of the present application, different values or different value ranges of the first information may be used to indicate different HARQ process ranges, or the different values or the different value ranges of the first information may be considered as different auxiliary bit information used to determine a final HARQ process number.

For example, two value ranges of the first information indicate two HARQ process ranges supported by the first DCI format, or the two value ranges may also be considered as 1-bit auxiliary information for determining the target HARQ process number. For another example, four value ranges of the first information indicate four HARQ process ranges supported by the first DCI format, or the four value ranges may also be considered as 2-bit auxiliary information for determining the target HARQ process number.

It should be further understood that when different values or different value ranges of the first information are used as the auxiliary bit information to determine the final HARQ process number, the final HARQ process number may be used as at least one bit of the higher order, or at least one bit of the lower order, or at least one bit in the middle, and the like, which is not limited in this application.

In the following, the first information is taken as an example to assist in indicating two different HARQ process ranges, and when a greater number of HARQ process ranges need to be indicated, only more values or more value ranges need to be configured, which is not limited in the present application.

Mode 1: indicating different HARQ process number ranges by different RNTIs

As an embodiment, a first RNTI is used to indicate a first range of HARQ process numbers, and a second RNTI is used to indicate a second range of HARQ process numbers, where a maximum value of HARQ process numbers included in the first range of HARQ process numbers is greater than a first value, and a maximum value of HARQ process numbers included in the second range of HARQ process numbers is equal to the first value.

That is, the first DCI format corresponding to the first RNTI supports data transmission scheduling in which the HARQ process number is greater than the first numerical value, and the first DCI format corresponding to the second RNTI supports data transmission scheduling in which the HARQ process number is less than or equal to the first numerical value.

For example, the first HARQ process number range is 16 to 31, or 0 to 31, and the second HARQ process range is 0 to 15.

In some embodiments, if the RNTI corresponding to the first DCI is the first RNTI, it indicates that the first HARQ process number is greater than the first numerical value; or, if the RNTI corresponding to the first DCI is the second RNTI, it indicates that the first HARQ process number is less than or equal to the first numerical value. In this case, the first RNTI and the second RNTI may be considered as auxiliary bits for determining the target HARQ process number. For example, the first RNTI corresponds to high order bit 1, and the second RNTI corresponds to high order bit 0. For example, the first HARQ process number range is 16 to 31, and the second HARQ process range is 0 to 15.

For example, if the terminal device receives the first DCI corresponding to the first RNTI, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 1 as the high order of the HARQ process number. Or, if the terminal device receives the first DCI corresponding to the second RNTI, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 0 as the high order of the HARQ process number.

In other embodiments, if the RNTI corresponding to the first DCI is the first RNTI, it indicates that the HARQ process number range to which the first HARQ process number belongs is the first HARQ process number range; or, if the RNTI corresponding to the first DCI is the second RNTI, it indicates that the HARQ process number range to which the first HARQ process number belongs is the second HARQ process number range.

In this case, if the first HARQ process number is greater than the first value, or the first HARQ process number belongs to the first HARQ process number range, additional auxiliary information and the HARQ process number indication field in the first DCI are required to perform joint determination. For example, the target HARQ process number is determined based on the first information field except the HARQ process number indication field in the first DCI. For example, the first HARQ process number range is 0 to 31, and the second HARQ process range is 0 to 15.

As an embodiment, the first HARQ process number is determined according to a part of or all bits in the first information field and all bits in a HARQ process number indication field in the first DCI.

It should be understood that the number of bits used when determining the first HARQ process number by using the first information field in the first DCI may be determined according to the range of HARQ process numbers to be indicated, for example, if the maximum HARQ process number to be indicated is 31, 5 bits of indication information are needed, and if the HARQ process number indication field includes 4 bits, only 1 additional bit is needed for indication.

For example, the first information field may include a Redundancy Version (RV) field, and the RV field includes 2 bits for indicating transmission of a corresponding RV, for example, for indicating one of 0, 1, 2, and 3. When the first DCI format schedules data transmission with a HARQ process number greater than the first value, 1 bit of the 2 bits in the RV field in the first DCI format is used to indicate the RV corresponding to the transmission, e.g., to indicate one of 0 and 3, and the other 1 bit is used to assist in indicating the HARQ process number, e.g., to indicate the highest order or the lowest order in the target HARQ process number.

For another example, if the terminal device receives the first DCI corresponding to the first RNTI, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and part or all of the bits in the first information field. Or, if the terminal device receives the first DCI corresponding to the second RNTI, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI.

Optionally, the first RNTI is an RNTI configured for the terminal device by the network device. For example, the first RNTI is an RNTI specific to the terminal device and configured by the network device for the terminal device, and the first RNTI is used for supporting data transmission scheduling of which the HARQ process number is greater than a first value.

Optionally, the second RNTI is an RNTI configured by the network device for the terminal device. For example, the second RNTI is an RNTI specific to the terminal device and configured by the network device for the terminal device, and the second RNTI is used for supporting data transmission scheduling of which the HARQ process number is smaller than or equal to the first value.

By way of example and not limitation, the first TB is a TB in uplink transmission, and the first RNTI includes at least one of: pre-configuring a Scheduling radio network temporary identifier (Configured Scheduling RNTI, CS-RNTI);

modulation and Coding Scheme Cell Radio Network Temporary identifier (MCS-C-RNTI);

Semi-Persistent scheduling Channel State Information Radio Network Temporary Identity (SP-CSI-RNTI).

The second RNTI comprises at least one of:

temporary Cell RNTI (Temporary Cell RNTI, TC-RNTI), cell RNTI (Cell RNTI, C-RNTI).

By way of example and not limitation, the first TB is a TB in downlink transmission, and the first RNTI includes at least one of: CS-RNTI, MCS-C-RNTI, the second RNTI comprising at least one of: TC-RNTI and C-RNTI.

Optionally, in some embodiments, for a first DCI format scrambled using C-RNTI, data transmission scheduling with HARQ process number greater than a first value is supported if a certain condition is met. Optionally, the specific conditions include at least one of: the first DCI format corresponds to a specific search space, for example, a search space specific to the terminal device, and the first DCI format corresponds to a specific CCE index.

Mode 2: indicating different HARQ process number ranges through different search spaces

As an embodiment, the first search space is configured to indicate a first HARQ process number range, and the second search space is configured to indicate a second HARQ process number range, where a maximum value of HARQ process numbers included in the first HARQ process range is greater than a first value, and a maximum value of HARQ process numbers included in the second HARQ process number range is equal to the first value.

That is, the first DCI format corresponding to the first search space supports data transmission scheduling with the HARQ process number greater than the first value, and the first DCI format corresponding to the second search space supports data transmission scheduling with the HARQ process number less than or equal to the first value.

In some embodiments, if the search space corresponding to the first DCI is a first search space, it indicates that the first HARQ process number is greater than the first value; or, if the search space corresponding to the first DCI is a second search space, it indicates that the first HARQ process number is less than or equal to the first value. In this case, the first search space and the second search space may be considered as auxiliary bits for determining the target HARQ process number. For example, the first search space corresponds to the upper bit 1, and the second search space corresponds to the upper bit 0. For example, the first HARQ process number range is 16 to 31, and the second HARQ process range is 0 to 15.

For example, if the terminal device receives the first DCI in the first search space, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 1 as the high order of the HARQ process number. Or, if the terminal device receives the first DCI in the second search space, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 0 as the high order of the HARQ process number.

In other embodiments, if the search space corresponding to the first DCI is a first search space, it indicates that the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or, if the search space corresponding to the first DCI is a second search space, it indicates that the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range. In this case, if the first HARQ process number is greater than the first value, additional auxiliary information and the HARQ process number indication field in the first DCI are required to perform joint indication, which is specifically described in manner 1.

Optionally, the first search space is a search space configured by the network device for the terminal device. For example, the first search space is a search space dedicated to the terminal device and configured by the network device for the terminal device, and the first search space is used for supporting data transmission scheduling in which the HARQ process number is greater than a first value, or data transmission scheduling in a first HARQ process number range.

Optionally, the second search space is a search space configured by the network device for the terminal device. For example, the second search space is a search space dedicated to the terminal device and configured by the network device for the terminal device, and the second search space is used for supporting data transmission scheduling of which the HARQ process number is smaller than or equal to the first value or data transmission scheduling of a second HARQ process number range.

Mode 3: indicating different ranges of HARQ process numbers by different ranges of CCE indices

As an embodiment, the first CCE index range is used to indicate a first HARQ process number range, and the second CCE index range is used to indicate a second HARQ process number range, where the first HARQ process range includes a maximum value of HARQ process numbers greater than a first value, and the second HARQ process number range includes a maximum value of HARQ process numbers equal to the first value.

That is, the first DCI format corresponding to the first CCE index range supports data transmission scheduling in which the HARQ process number is greater than the first value, and the first DCI format corresponding to the second CCE index range supports data transmission scheduling in which the HARQ process number is less than or equal to the first value.

In some embodiments, if the CCE index range corresponding to the first DCI is a first CCE index range, it indicates that the first HARQ process number is greater than the first value; or, if the CCE index range corresponding to the first DCI is the second CCE index range, it indicates that the first HARQ process number is less than or equal to the first value. In this case, the first CCE index range and the second CCE index range may be considered as auxiliary bits for determining the target HARQ process number. For example, the first CCE index range corresponds to upper bit 1 and the second CCE index range corresponds to upper bit 0. For example, the first HARQ process number range is 16 to 31, and the second HARQ process range is 0 to 15.

For example, if a first DCI received by the terminal device corresponds to the first CCE index range, the terminal device determines, according to the HARQ process number indication field in the first DCI and the high bit setting 1 as the HARQ process number, the HARQ process number corresponding to the first DCI. Or, if the first DCI received by the terminal device corresponds to the second CCE index range, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 0 as the high order of the HARQ process number.

In other embodiments, if the CCE index range corresponding to the first DCI is a first CCE index range, it indicates that the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or, if the CCE index range corresponding to the first DCI is a second CCE index range, it indicates that the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range. In this case, if the first HARQ process number is greater than the first value, additional auxiliary information and the HARQ process number indication field in the first DCI are required to perform joint indication, which is specifically described in manner 1.

Optionally, the first CCE index range is a CCE index range configured by the network device for the terminal device. For example, the first CCE index range is configured by the network device for the terminal device to support data transmission scheduling for which the HARQ process number is greater than a first value, or to support data transmission scheduling for a first range of HARQ process numbers.

Optionally, the second CCE index range is a CCE index range configured by the network device for the terminal device. For example, the second CCE index range is configured by the network device for the terminal device to support data transmission scheduling for which the HARQ process number is less than or equal to the first value, or to support data transmission scheduling for a second range of HARQ process numbers.

Mode 4: indicating different HARQ process number ranges by different DMRS

As an embodiment, the first DMRS sequence is configured to indicate a first range of HARQ process numbers, and the second DMRS sequence is configured to indicate a second range of HARQ process numbers, wherein the first range of HARQ process numbers includes a maximum value of HARQ process numbers greater than a first value, and the second range of HARQ process numbers includes a maximum value of HARQ process numbers equal to the first value.

That is, the first DCI format corresponding to the first DMRS sequence supports data transmission scheduling in which the HARQ process number is greater than the first value, and the first DCI format corresponding to the second DMRS sequence supports data transmission scheduling in which the HARQ process number is less than or equal to the first value.

In some embodiments, if the DMRS sequence corresponding to the first DCI is a first DMRS sequence, it indicates that the first HARQ process number is greater than the first value; or, if the DMRS sequence corresponding to the first DCI is a second DMRS sequence, it indicates that the first HARQ process number is less than or equal to the first value. In this case, the first and second DMRS sequences may be considered as auxiliary bits for determining the target HARQ process number. For example, the first DMRS sequence corresponds to upper bit 1, and the second DMRS sequence corresponds to upper bit 0. For example, the first HARQ process number range is 16 to 31, and the second HARQ process range is 0 to 15.

For example, if a first DCI received by the terminal device corresponds to a first DMRS sequence, the terminal device determines, according to an HARQ process number indication field in the first DCI and setting 1 as the high-order bit of the HARQ process number, the HARQ process number corresponding to the first DCI. Or, if the first DCI received by the terminal device corresponds to the second DMRS sequence, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 0 as the high order of the HARQ process number.

In other embodiments, if the DMRS sequence corresponding to the first DCI is a first DMRS sequence, it indicates that the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or, if the DMRS sequence corresponding to the first DCI is a second DMRS sequence, it indicates that the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range. In this case, if the first HARQ process number is greater than the first value, additional auxiliary information and the HARQ process number indication field in the first DCI are required to perform joint indication, which is specifically implemented in manner 1.

Optionally, the first DMRS sequence is a DMRS sequence configured by the network device for the terminal device. For example, the first DMRS sequence is configured by the network device for the terminal device to support data transmission scheduling for which the HARQ process number is greater than a first value, or to support data transmission scheduling for a first range of HARQ process numbers.

Optionally, the second DMRS sequence is a DMRS sequence configured by the network device for the terminal device. For example, the second DMRS sequence is configured by the network device for the terminal device to support data transmission scheduling for which the HARQ process number is less than or equal to the first value, or to support a second range of HARQ process numbers.

Mode 5: indicating different HARQ process number ranges by different time domain resources

As an embodiment, the first time domain resource range is used to indicate a first HARQ process number range, and the second time domain resource range is used to indicate a second HARQ process number range, where a maximum value of HARQ process numbers included in the first HARQ process range is greater than a first value, and a maximum value of HARQ process numbers included in the second HARQ process number range is equal to the first value.

That is, the first DCI format corresponding to the first time domain resource range supports data transmission scheduling with the HARQ process number greater than the first value, and the first DCI format corresponding to the second time domain resource range supports data transmission scheduling with the HARQ process number less than or equal to the first value.

In some embodiments, if the time domain resource range corresponding to the first DCI is a first time domain resource range, it indicates that the first HARQ process number is greater than the first value; or, if the time domain resource range corresponding to the first DCI is a second time domain resource range, it indicates that the first HARQ process number is less than or equal to the first value. In this case, the first and second time domain resource ranges may be considered as auxiliary bits for determining the target HARQ process number. For example, the first time domain resource range corresponds to the high order bit 1, and the second time domain resource range corresponds to the high order bit 0. For example, the first HARQ process number range is 16 to 31, and the second HARQ process range is 0 to 15.

For example, if the PDSCH or PUSCH scheduled by the first DCI received by the terminal device corresponds to the first time domain resource range, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 1 as the high order of the HARQ process number. Or, if the PDSCH or PUSCH scheduled by the first DCI received by the terminal device corresponds to the second time domain resource range, the terminal device determines the HARQ process number corresponding to the first DCI according to the HARQ process number indication field in the first DCI and setting 0 as the high order of the HARQ process number.

In other embodiments, if the time domain resource range corresponding to the first DCI is a first time domain resource range, it indicates that the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or, if the time domain resource range corresponding to the first DCI is a second time domain resource range, it indicates that the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range. In this case, if the first HARQ process number is greater than the first value, additional auxiliary information and the HARQ process number indication field in the first DCI are required to perform joint indication, which is specifically implemented in manner 1.

Optionally, the first time domain resource range is a time domain resource range configured or preset by the network device for the terminal device. For example, the first time domain resource range is configured for the terminal device by the network device to support data transmission scheduling for which the HARQ process number is greater than the first value, or to support data transmission scheduling for the first HARQ process number range.

Optionally, the second time domain resource range is a time domain resource range configured or preset by the network device for the terminal device. For example, the second time domain resource range is configured for the terminal device by the network device to support data transmission scheduling of which the HARQ process number is smaller than or equal to the first value, or to support data transmission scheduling of the second HARQ process number range.

Optionally, in some embodiments, the time domain resource comprises at least one of:

the time slot number or the time slot group corresponding to the HARQ process;

a System Frame Number (SFN) corresponding to the HARQ process Number;

time window corresponding to HARQ process.

For example, the low-order bits in the HARQ process number may be determined according to the timeslot number corresponding to the HARQ process number, or the high-order bits in the HARQ process number may be determined according to the timeslot group Identifier (ID) corresponding to the HARQ process number, or the HARQ process number is determined according to the time window index corresponding to the HARQ process number, where ranges of schedulable HARQ process numbers in different time windows are different, and so on.

As an example, it is assumed that the time domain resource is divided into different periods, and the start position of each period is 2 radio frames each, and the length is 2 radio frames. The maximum number of HARQ processes that can be scheduled in each cycle is 16. Assuming that the maximum number of HARQ processes supported by the first DCI format is 32, the index corresponding to each period may be used to determine the high-order Bit (MSB) or low-order Bit (LSB) of the scheduled HARQ process number. Taking the MSB of the index corresponding to each period for determining the number of the scheduled HARQ process as an example, as shown in table 1.

Period identification	First period 0	First period 1
High order of HARQ process number	0	1

If the terminal device receives the first DCI on the 3 rd subframe of the radio frame P +1, or the terminal device is scheduled to transmit the first TB on the 3 rd subframe of the radio frame P +1, where the HARQ process number in the first DCI indicates the field indication 1100. Wherein P is an integer. The terminal device may determine that the HARQ process number for transmitting the first TB is 01100, i.e. the HARQ process number for the first TB is 12.

If the terminal device receives the first DCI on the 8 th subframe of the radio frame P +2, or the terminal device is scheduled to transmit the first TB on the 8 th subframe of the radio frame P +2, where the HARQ process number in the first DCI indicates the field indication 1100. Accordingly, the terminal device may determine that the HARQ process number for transmitting the first TB is 11100, i.e., the HARQ process number of the first TB is 28.

If the network device needs to schedule the terminal device to retransmit the transport block in the first TB, or the network device schedules the terminal device to transmit using the HARQ process with HARQ process number 12, the network device needs to schedule in the first cycle 0 in the radio frame P +4 × i, where i is a positive integer. For example, the network device may schedule HARQ process with HARQ process number 12 on the 4 th subframe in radio frame P +4, or the network device may schedule HARQ process with HARQ process number 12 on the 7 th subframe in radio frame P + 5.

Optionally, in other embodiments of the present application, different states of the terminal device support different HARQ process ranges corresponding to the first DCI format.

As an example, if the terminal device is in a connected state, the first DCI format supports the first HARQ process range, or if the terminal device is in a non-connected state, for example, an Idle (Idle) state or an inactive (inactive) state, the first DCI format supports the second HARQ process range.

The terminal device may determine, according to the state of the terminal device itself, the HARQ process number used for data transmission scheduled by the first DCI in a corresponding manner. For example, if the terminal device is in the non-connected state, the target HARQ process number is determined according to the value in the HARQ process number indication field in the first DCI, and for example, if the terminal device is in the connected state, the target HARQ process number is determined according to the HARQ process number indication field in the first DCI and by combining the first information.

The foregoing embodiments 1 to 5 may be implemented individually or in combination, and the present application is not limited to these embodiments. For example, different HARQ process ranges are indicated by different RNTIs, and a specific HARQ process number is further determined by the time domain resource corresponding to the first DCI.

In the above, with reference to the modes 1 to 5, it is described how to indicate the HARQ process number greater than the first numerical value when the fallback DCI format supports the data transmission scheduling that the HARQ process number is greater than the first numerical value. In the following, how to implement compatible scheduling with non-fallback DCI formats when the number of HARQ processes supported by the fallback DCI format is the three cases described above is described.

Optionally, in some embodiments, before S310, the method 300 further includes:

and the terminal equipment receives second DCI sent by the network equipment, wherein the second DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the second DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.

In this case, the first DCI format schedules retransmission of the first TB, and the second DCI format schedules initial transmission of the first TB or retransmission of the first TB.

Optionally, in some embodiments, a first HARQ process number corresponding to the first HARQ process is less than or equal to the first numerical value. For example, when the fallback DCI format supports data transmission scheduling with the HARQ process number not greater than the first value, and the non-fallback DCI format supports data transmission scheduling with the HARQ process number greater than the first value, if the non-fallback DCI format schedules initial transmission of the first TB, the fallback DCI format may be used to schedule retransmission of the first TB when the HARQ process number corresponding to the first TB is not greater than the first value. Optionally, in other embodiments, after S310, the method 300 further includes:

and the terminal equipment receives third DCI sent by the network equipment, wherein the third DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the third DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.

In this case, it may be considered that the second DCI format schedules retransmission of the first TB, and the first DCI format schedules initial transmission of the first TB, or may schedule retransmission of the first TB.

In summary, the first DCI format may be used to schedule the initial transmission or retransmission of the first TB, and the second DCI format may also be used to schedule the initial transmission or retransmission of the first TB.

Optionally, in some embodiments, the second DCI format supports the first HARQ process range described above, or the second DCI format supports data transmission scheduling using a HARQ process number greater than the first value.

Optionally, in some embodiments, the second DCI format comprises a non-fallback DCI format.

That is, the fallback DCI format may be used to schedule initial transmission or retransmission of the first TB, and the non-fallback DCI format may be used to schedule initial transmission or retransmission of the first TB.

It should be understood that the application does not limit the specific DCI formats included in the non-fallback DCI format.

As an example, the first TB is a TB in downlink transmission, and the second DCI format includes at least one of DCI format 1_1 and DCI format 1_2.

As another example, the first TB is a TB in uplink transmission, and the second DCI format includes at least one of DCI format 0 _1and DCI format 0 _2.

In the embodiment of the present application, the non-fallback DCI format supports data transmission scheduling with a HARQ process number greater than a first value.

Optionally, in some embodiments, the size of the HARQ process number indication field in the non-fallback DCI format is a fixed value, and data transmission scheduling of a HARQ process number larger than the first value can be supported. For example, the maximum number of HARQ processes configured for the terminal device is 32 (or the maximum HARQ process number is 31), and the HARQ process number indication field in the non-fallback DCI format is 5 bits.

Optionally, in some embodiments, the size of the HARQ process number indication field in the non-fallback DCI format is determined according to the maximum number of HARQ processes configured by the terminal device, and the maximum HARQ process number indication field is a preset value. Or, the size of the HARQ process number indication field in the non-fallback DCI format is configured by the network device, and the maximum value that can be configured is a preset value. Or, the size of the HARQ process number indication field in the non-fallback DCI format is fixed to a preset value.

As an example, assume that the preset value is 4. When the size of the HARQ process number indication field is 4 bits and the maximum number of HARQ processes configured for the terminal device is 32, the range of supportable scheduled HARQ process numbers is 0 to 31, where the HARQ process number is determined according to the HARQ process number indication field and the first information.

In the following, with reference to specific embodiments, how to implement compatible scheduling of a fallback DCI format and a non-fallback DCI format when the number of HARQ processes supported by the fallback DCI format is the aforementioned three cases is described.

For case 1, the fallback DCI format supports data transmission scheduling with HARQ process number less than or equal to the first value, and the non-fallback DCI format supports data transmission scheduling with HARQ process number greater than the first value.

Example 1:

and performing initial transmission of the first TB through the first HARQ process by using non-fallback DCI format scheduling, and performing retransmission of the first TB through the first HARQ process by using non-fallback DCI format scheduling.

For example, for downlink transmission, if the initial transmission of the first TB in the PDSCH is transmitted through the first HARQ process using DCI format 1_1 or DCI format 1_2 scheduling, when retransmission is required, the retransmission of the first TB is also performed through the first HARQ process using DCI format 1 _u1 or DCI format 1 _u2 scheduling. Optionally, the same DCI format may be used to schedule the initial transmission and the retransmission of the first TB through the first HARQ process; alternatively, the initial transmission and retransmission of the first TB may be scheduled by the first HARQ process using different DCI formats, for example, the initial transmission of the first TB may be scheduled by the first HARQ process using DCI format 1_2, and the retransmission of the first TB may be scheduled by the first HARQ process using DCI format 1_1.

For another example, for uplink transmission, if initial transmission of a first TB in a PUSCH is transmitted through a first HARQ process using DCI format 0 _1or DCI format 0 _2scheduling, retransmission of the first TB is also performed through the first HARQ process using DCI format 0 _1or DCI format 0 _2scheduling when retransmission is necessary. Optionally, the same DCI format may be used to schedule the initial transmission and the retransmission of the first TB through the first HARQ process; alternatively, the initial transmission and retransmission of the first TB may be scheduled by the first HARQ process using different DCI formats, for example, the initial transmission of the first TB may be scheduled by the first HARQ process using DCI format 0_2, and the retransmission of the first TB may be scheduled by the first HARQ process using DCI format 0_1.

Therefore, under the condition that the number of HARQ processes scheduled by the fallback DCI format and the non-fallback DCI format is different, the initial transmission and retransmission behaviors scheduled by the non-fallback DCI format are limited, and the condition that the HARQ process with the HARQ process number larger than 16 cannot be scheduled can be avoided.

Example 2: using non-fallback DCI format scheduling to perform initial transmission of a first TB through a first HARQ process, wherein if the number of the HARQ process of the first HARQ process is larger than 15, using the non-fallback DCI format scheduling to perform retransmission of the first TB through the first HARQ process; or, if the HARQ process number of the first HARQ process is less than or equal to 15, scheduling retransmission of the first TB through the first HARQ process using a non-fallback DCI format or a fallback DCI format.

For example, for downlink transmission, if DCI format 1_1 or DCI format 1 _u2 is used to schedule initial transmission of a first TB in a PDSCH through a first HARQ process, when retransmission is required, if the HARQ process number of the first HARQ process is greater than 15, then DCI format 1 _u1 or DCI format 1 _u2 is also used to schedule retransmission of the first TB through the first HARQ process; alternatively, if the HARQ process number of the first HARQ process is less than or equal to 15, the retransmission of the first TB may be scheduled through the first HARQ process using DCI format 1 _0or DCI format 1 _1or DCI format 1 _2.

For another example, for uplink transmission, if DCI format 0 _u1 or DCI format 0 _u2 is used to schedule initial transmission of a first TB in the PDSCH through a first HARQ process, and if the HARQ process number of the first HARQ process is greater than 15 when retransmission is required, DCI format 0 _u1 or DCI format 0 _u2 is also used to schedule retransmission of the first TB through the first HARQ process; alternatively, if the HARQ process number of the first HARQ process is less than or equal to 15, the retransmission of the first TB may be scheduled through the first HARQ process using DCI format 0 _0or DCI format 0 _1or DCI format 0 _2.

Therefore, in this embodiment 2, there is no limitation on the scheduling of the HARQ process whose HARQ process number is less than or equal to 15, and the flexibility of the scheduling can be improved.

Example 3: and performing initial transmission of the first TB through the first HARQ process by using fallback DCI format scheduling, and performing retransmission of the first TB through the first HARQ process by using non-fallback DCI formats or the fallback DCI format scheduling.

Therefore, under the condition that the number of HARQ processes scheduled by the fallback DCI format and the non-fallback DCI format is different, the range of the number of HARQ processes scheduled by the non-fallback DCI format may be greater than the range of the number of HARQ processes scheduled by the fallback DCI format, and therefore, no limitation may be imposed on the number of HARQ processes scheduled by the fallback DCI format.

For case 2, the fallback DCI format supports data transmission scheduling with HARQ process number greater than the first value in a specific case, and the non-fallback DCI format supports data transmission scheduling with HARQ process number greater than the first value.

How the fallback DCI format supports data transmission scheduling with HARQ process number greater than the first value refers to the specific implementation in the foregoing manner 1 to manner 5.

Hereinafter, taking the first RNTI and the second RNTI to respectively indicate that the fallback DCI format supports the data transmission scheduling with the HARQ process number greater than 15 and the data transmission scheduling with the HARQ process number less than or equal to 15 as an example, how to implement the compatible scheduling of the fallback DCI format and the non-fallback DCI format is described.

Example 4: and scheduling the fallback DCI format scrambled by the first RNTI to perform initial transmission of the first TB through the first HARQ process, and scheduling the fallback DCI format scrambled by the non-fallback DCI format or the first RNTI to perform retransmission of the first TB through the first HARQ process.

Specifically, the fallback DCI format scrambled with the first RNTI may support data transmission scheduling with a HARQ process number greater than 15, and when the first TB is retransmitted, the selected DCI format also needs to support the HARQ process number greater than 15, so that a non-fallback DCI format or the fallback DCI format scrambled with the first RNTI may be selected.

Example 5: and scheduling the first TB through a first HARQ process by using the fallback DCI format scrambled by the second RNTI, and performing retransmission of the first TB through the first HARQ process by using a non-fallback DCI format or the fallback DCI format.

Specifically, the fallback DCI format scrambled using the second RNTI may support data transmission scheduling with HARQ process number less than or equal to 15, and thus when performing retransmission of the first TB, the selected DCI format only needs to support the HARQ process number less than or equal to 15, and thus, the fallback DCI format (which may be scrambled using any RNTI) or a non-fallback DCI format may be selected.

Example 6: and scheduling the first TB through a first HARQ process by using a non-fallback DCI format, and scheduling the first TB through the first HARQ process by using a fallback DCI format scrambled by using the non-fallback DCI format or the first RNTI.

Specifically, the non-fallback DCI format may support data transmission scheduling with a HARQ process number greater than 15, and when the first TB is retransmitted, the selected DCI format also needs to support the HARQ process number greater than 15, so that the non-fallback DCI format or the fallback DCI format scrambled by the first RNTI may be selected.

Example 7: using non-fallback DCI format scheduling to perform initial transmission of a first TB through a first HARQ process, wherein if the HARQ process number of the first HARQ process is larger than 15, using the fallback DCI format scrambled by the non-fallback DCI format or a first RNTI to perform retransmission of the first TB through the first HARQ process; or, if the HARQ process number of the first HARQ process is less than or equal to 15, scheduling retransmission of the first TB through the first HARQ process using a non-fallback DCI format or a fallback DCI format.

To sum up, when the DCI format for the initial transmission scheduling is determined according to the DCI format for the initial transmission scheduling, the DCI format supporting the HARQ process number greater than or equal to the HARQ process number supported by the DCI format for the initial transmission scheduling may be selected, or the DCI format supporting the HARQ process number used by the initial transmission scheduling may also be selected.

Therefore, in this embodiment of the present application, when the first DCI format supports different HARQ process numbers, the terminal device may determine, in an appropriate manner, the HARQ process number corresponding to the data transmission scheduled by the first DCI format, so as to ensure that the network device and the terminal device understand the scheduled HARQ process number consistently.

While method embodiments of the present application are described in detail above with reference to fig. 3, apparatus embodiments of the present application are described in detail below with reference to fig. 4-8, it being understood that apparatus embodiments correspond to method embodiments and that similar descriptions may refer to method embodiments.

Fig. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 4, the terminal apparatus 400 includes:

a communication unit 410, configured to receive first downlink control information DCI sent by a network device, where the first DCI is used to schedule transmission of a first transport block TB through a first hybrid automatic repeat request HARQ process, where the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a maximum HARQ process number indicated by a HARQ process number indication field in the first DCI format is a first numerical value; and

transmitting the first TB through the first HARQ process.

Optionally, in some embodiments, the first HARQ process number is determined according to first information corresponding to the first DCI and a HARQ process number indication field in the first DCI.

Optionally, in some embodiments, the first information corresponding to the first DCI includes at least one of:

a Radio Network Temporary Identifier (RNTI) corresponding to the first DCI;

a search space corresponding to the first DCI;

a Control Channel Element (CCE) index range corresponding to the first DCI;

Optionally, the first information includes an RNTI corresponding to the first DCI, where the first HARQ process number is greater than the first numerical value or a HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range, when the RNTI corresponding to the first DCI is the first RNTI; or, when the RNTI corresponding to the first DCI is the second RNTI, the first HARQ process number is less than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is the second HARQ process number range.

Optionally, in some embodiments, the first TB is a TB in uplink transmission, and the first RNTI includes at least one of the following: CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI; and/or the second RNTI comprises at least one of the following:

a temporary cell radio network temporary identifier TC-RNTI and a cell radio network temporary identifier C-RNTI.

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and the first RNTI includes at least one of the following: CS-RNTI, MCS-C-RNTI; and/or the presence of a gas in the gas,

the second RNTI comprises at least one of:

the temporary cell radio network temporary identifier TC-RNTI and the cell radio network temporary identifier C-RNTI.

Optionally, in some embodiments, the first information includes a search space corresponding to the first DCI, wherein,

under the condition that the search space corresponding to the first DCI is a first search space, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the search space corresponding to the first DCI is a second search space, the first HARQ process number is less than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.

Optionally, in some embodiments, the first search space comprises a terminal device-specific search space, and/or the second search space comprises a common search space.

Optionally, in some embodiments, the first information includes a CCE index range corresponding to the first DCI, where the first HARQ process number is greater than the first numerical value or a HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range, where a search space corresponding to the first DCI is a first CCE index range; or, when the search space corresponding to the first DCI is a second CCE index range, the first HARQ process number is less than or equal to the first value, or a HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.

Optionally, in some embodiments, the first CCE index range is configured or preset by the network device and/or the second CCE index range is configured or preset by the network device.

Optionally, the first information includes a time domain resource corresponding to the first HARQ process scheduled by the first DCI, where, when the time domain resource corresponding to the first HARQ process corresponds to a first time domain resource range, the first HARQ process number is greater than the first value, or a HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or, in the case that the time domain resource corresponding to the first HARQ process corresponds to a second time domain resource range, the first HARQ process number is less than or equal to the first value, or the HARQ process number range to which the first HARQ process number belongs is the second HARQ process number range.

Optionally, in some embodiments, the first time domain resource range is configured or preset by the network device, and/or the second time domain resource range is configured or preset by the network device.

Optionally, in some embodiments, in a case that the first HARQ process number is greater than the first numerical value, or a HARQ process number range to which the first HARQ process number belongs is the first HARQ process number range, the first information further includes a first information field except for the HARQ process number indication field in the first DCI.

Optionally, in some embodiments, the first information includes a first information field except for the HARQ process number indication field in the first DCI, where the first HARQ process number is determined according to the first information corresponding to the first DCI and the HARQ process number indication field in the first DCI, and the method includes: the first HARQ process number is determined according to part of or all bits in the first information domain and all bits in an HARQ process number indication domain in the first DCI.

Optionally, in some embodiments, the first information field includes a redundancy version RV field.

Optionally, in some embodiments, the first HARQ process number is less than or equal to the first numerical value, and the first HARQ process number is determined according to a HARQ process number indication field in the first DCI.

Optionally, before receiving the first DCI transmitted by the network device, the communication unit 410 is further configured to: receiving second DCI sent by the network device, where the second DCI is used to schedule transmission of the first TB through the first HARQ process, where the second DCI corresponds to a second DCI format, and a schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.

Optionally, after receiving the first DCI transmitted by the network device, the communication unit 410 is further configured to: and receiving third DCI sent by the network equipment, wherein the third DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the third DCI corresponds to a second DCI format, and the maximum HARQ process number which can be scheduled by the second DCI format is greater than the first numerical value.

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and the second DCI format includes at least one of DCI format 1_1 and DCI format 1_2; or the first TB is a TB in uplink transmission, and the second DCI format includes at least one of DCI format 0_1 and DCI format 0 _u2.

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and the first DCI format includes DCI format 1_0; or the first TB is a TB in uplink transmission, and the first DCI format includes DCI format 0_0.

Optionally, in some embodiments, the communication unit 410 is further configured to: reporting downlink capability information of the terminal equipment to the network equipment, wherein the downlink capability information is used for indicating that the number of downlink HARQ processes supported by the terminal equipment is greater than a specific numerical value, or the maximum HARQ process number of the scheduled downlink transmission supported by the terminal equipment is greater than the first numerical value, and the specific numerical value is equal to the first numerical value plus one; and/or reporting uplink capability information of the terminal device to the network device, where the uplink capability information is used to indicate that the number of uplink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value, where the specific value is equal to the first value plus one.

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and an HARQ process number range corresponding to the configured number of downlink HARQ processes of the terminal device is a first HARQ process number range, or a maximum HARQ process number that the terminal device supports scheduled downlink transmission is greater than the first value; or, the first TB is a TB in uplink transmission, and a HARQ process number range corresponding to the uplink HARQ process number configured by the terminal device is a first HARQ process number range, or the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value.

Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to a terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing a corresponding flow of the terminal device in the method 300 shown in fig. 3, and are not described herein again for brevity.

Fig. 5 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of fig. 5 includes:

a communication unit 510, configured to send first downlink control information DCI to a terminal device, where the first DCI is used to schedule transmission of a first transport block TB through a first hybrid automatic repeat request HARQ process, where the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a maximum HARQ process number indicated by a HARQ process number indication field in the first DCI format is a first numerical value.

Optionally, in some embodiments, the first HARQ process number is indicated by first information corresponding to the first DCI and a HARQ process number indication field in the first DCI.

a Radio Network Temporary Identifier (RNTI) corresponding to the first DCI;

a search space corresponding to the first DCI;

a Control Channel Element (CCE) index range corresponding to the first DCI;

and the first DCI schedules a demodulation reference signal (DMRS) sequence corresponding to the first HARQ process.

Optionally, in some embodiments, the first information includes an RNTI corresponding to the first DCI, wherein,

under the condition that the RNTI corresponding to the first DCI is a first RNTI, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the RNTI corresponding to the first DCI is a second RNTI, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.

Optionally, in some embodiments, the first TB is a TB in uplink transmission, and the first RNTI includes at least one of the following: CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI; and/or the presence of a gas in the gas,

the second RNTI comprises at least one of:

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and the first RNTI includes at least one of the following: CS-RNTI, MCS-C-RNTI; and/or the presence of a gas in the atmosphere,

the second RNTI comprises at least one of:

Optionally, in some embodiments, the first information includes a first information field except for the HARQ process number indication field in the first DCI, where the first HARQ process number is indicated by first information corresponding to the first DCI and a HARQ process number indication field in the first DCI, and the method includes: the first HARQ process number is indicated by part or all bits in the first information field and all bits in an HARQ process number indication field in the first DCI.

Optionally, in some embodiments, before transmitting the first DCI to the terminal device, the communication unit 510 is further configured to: and sending second DCI to the terminal equipment, wherein the second DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the second DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.

Optionally, in some embodiments, after transmitting the first DCI to the terminal device, the communication unit 510 is further configured to: and sending third DCI to the terminal equipment, wherein the third DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the third DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.

Optionally, in some embodiments, the communication unit 510 is further configured to: receiving downlink capability information of the terminal device reported by the terminal device, where the downlink capability information is used to indicate that the number of downlink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled downlink transmission is greater than the first value, where the specific value is equal to the first value plus one; and/or receiving uplink capability information of the terminal device, which is reported by the terminal device, wherein the uplink capability information is used for indicating that the number of uplink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number of the scheduled uplink transmission supported by the terminal device is greater than the first value, and the specific value is equal to the first value plus one.

Optionally, in some embodiments, the first TB is a TB in downlink transmission, and an HARQ process number range corresponding to the configured number of downlink HARQ processes of the terminal device is a first HARQ process number range, or a maximum HARQ process number that the terminal device supports scheduled downlink transmission is greater than the first value; or,

the first TB is a TB in uplink transmission, and the HARQ process number range corresponding to the uplink HARQ process number configured for the terminal device is a first HARQ process number range, or the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method 300 shown in fig. 3, and are not described herein again for brevity.

Fig. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 6, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, as shown in fig. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.

Optionally, the communication device 600 may specifically be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 600 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 600 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the chip 700 may further include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given 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.

Fig. 8 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 8, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

the method comprises the steps that terminal equipment receives first Downlink Control Information (DCI) sent by network equipment, wherein the first DCI is used for scheduling a first hybrid automatic repeat request (HARQ) process to transmit a first Transport Block (TB), the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and the HARQ process number in the first DCI format indicates that the maximum HARQ process number indicated by a domain is a first numerical value;

and the terminal equipment transmits the first TB through the first HARQ process.
The method of claim 1, wherein the first HARQ process number is determined according to first information corresponding to the first DCI and a HARQ process number indication field in the first DCI.
The method of claim 2, wherein the first information corresponding to the first DCI comprises at least one of:

a Radio Network Temporary Identifier (RNTI) corresponding to the first DCI;

a search space corresponding to the first DCI;

a Control Channel Element (CCE) index range corresponding to the first DCI;

time domain resources corresponding to the first HARQ process scheduled by the first DCI;

a first information field except the HARQ process number indication field in the first DCI;

and a demodulation reference signal (DMRS) sequence corresponding to the first HARQ process scheduled by the first DCI.
The method of claim 2 or 3, wherein the first information comprises an RNTI corresponding to the first DCI, wherein,

under the condition that the RNTI corresponding to the first DCI is a first RNTI, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the RNTI corresponding to the first DCI is a second RNTI, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method of claim 4, wherein the first TB is a TB in an uplink transmission, and wherein the first RNTI comprises at least one of: CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI; and/or the presence of a gas in the gas,

the second RNTI comprises at least one of:

the temporary cell radio network temporary identifier TC-RNTI and the cell radio network temporary identifier C-RNTI.
The method of claim 4, wherein the first TB is a TB in a downlink transmission, and wherein the first RNTI comprises at least one of: CS-RNTI, MCS-C-RNTI; and/or the presence of a gas in the atmosphere,

the second RNTI comprises at least one of:

the temporary cell radio network temporary identifier TC-RNTI and the cell radio network temporary identifier C-RNTI.
The method of any of claims 2-6, wherein the first information comprises a search space corresponding to the first DCI, wherein,

under the condition that the search space corresponding to the first DCI is a first search space, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the search space corresponding to the first DCI is a second search space, the first HARQ process number is less than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method of claim 7, wherein the first search space comprises a search space dedicated to a terminal device and/or wherein the second search space comprises a common search space.
The method of any of claims 2-8, wherein the first information comprises a CCE index range corresponding to the first DCI, wherein,

under the condition that the search space corresponding to the first DCI is a first CCE index range, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the search space corresponding to the first DCI is a second CCE index range, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method of claim 9, wherein the first CCE index range is configured or preset by the network device and/or wherein the second CCE index range is configured or preset by the network device.
The method of any of claims 2-10, wherein the first information comprises time domain resources corresponding to the first HARQ process scheduled by the first DCI, wherein,

under the condition that the time domain resource corresponding to the first HARQ process corresponds to the first time domain resource range, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is the first HARQ process number range; or,

and under the condition that the time domain resource corresponding to the first HARQ process corresponds to a second time domain resource range, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is the second HARQ process number range.
The method according to claim 11, wherein the first time domain resource range is configured or preset by the network device, and/or wherein the second time domain resource range is configured or preset by the network device.
The method according to any of claims 4, 7, 9, and 11, wherein in case that the first HARQ process number is greater than the first numerical value, or the range of HARQ process numbers to which the first HARQ process number belongs is the first range of HARQ process numbers, the first information further includes a first information field in the first DCI except for the HARQ process number indication field.
The method of any of claims 2-13, wherein the first information comprises a first information field in the first DCI except for the HARQ process number indication field, wherein,

the first HARQ process number is determined according to the first information corresponding to the first DCI and the HARQ process number indication field in the first DCI, and includes:

the first HARQ process number is determined according to part of or all bits in the first information domain and all bits in an HARQ process number indication domain in the first DCI.
The method of claim 14, wherein the first information field comprises a Redundancy Version (RV) field.
The method of claim 1, wherein the first HARQ process number is less than or equal to the first value, and wherein the first HARQ process number is determined according to a HARQ process number indication field in the first DCI.
The method of claim 16, wherein before the terminal device receives the first DCI transmitted by the network device, the method further comprises:

and the terminal equipment receives second DCI sent by the network equipment, wherein the second DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the second DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.
The method of claim 16, wherein after the terminal device receives the first DCI transmitted by the network device, the method further comprises:

and the terminal equipment receives a third DCI sent by the network equipment, wherein the third DCI is used for scheduling the first TB transmitted through the first HARQ process, the third DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.
The method of claim 17 or 18, wherein the second DCI format comprises a non-fallback DCI format.
The method of any of claims 17-19, wherein the first TB is a TB in a downlink transmission, and wherein the second DCI format comprises at least one of DCI format 1 _1and DCI format 1 _2; or,

the first TB is a TB in uplink transmission, and the second DCI format includes at least one of DCI format 0_1 and DCI format 0_2.
The method of any of claims 1-20, wherein the first DCI format comprises a fallback DCI format.
The method of any one of claims 1-21, wherein the first TB is a TB in a downlink transmission, and wherein the first DCI format comprises DCI format 1_0; or,

the first TB is a TB in uplink transmission, and the first DCI format includes DCI format 0_0.
The method according to any one of claims 1-22, further comprising: the terminal device reports downlink capability information of the terminal device to the network device, wherein the downlink capability information is used for indicating that the number of downlink HARQ processes supported by the terminal device is greater than a specific value, or the maximum HARQ process number of the terminal device supporting scheduled downlink transmission is greater than the first value, and the specific value is equal to the first value plus one; and/or the presence of a gas in the gas,

the terminal device reports uplink capability information of the terminal device to the network device, where the uplink capability information is used to indicate that the number of uplink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value, where the specific value is equal to the first value plus one.
The method according to any of claims 1-23, wherein the first TB is a TB in downlink transmission, the HARQ process number range corresponding to the configured number of downlink HARQ processes of the terminal device is a first HARQ process number range, or the maximum HARQ process number that the terminal device supports scheduled downlink transmission is greater than the first value; or,

the first TB is a TB in uplink transmission, and the HARQ process number range corresponding to the uplink HARQ process number configured by the terminal device is the first HARQ process number range, or the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value.
A method of wireless communication, comprising:

the method comprises the steps that network equipment sends first downlink control information DCI to terminal equipment, wherein the first DCI is used for scheduling a first hybrid automatic repeat request (HARQ) process to transmit a first Transport Block (TB), the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and the maximum HARQ process number indicated by an HARQ process number indication field in the first DCI format is a first numerical value.
The method of claim 25, wherein the first HARQ process number is indicated by first information corresponding to the first DCI and a HARQ process number indication field in the first DCI.
The method of claim 26, wherein the first information corresponding to the first DCI comprises at least one of:

a Radio Network Temporary Identifier (RNTI) corresponding to the first DCI;

a search space corresponding to the first DCI;

a Control Channel Element (CCE) index range corresponding to the first DCI;

time domain resources corresponding to the first HARQ process scheduled by the first DCI;

a first information field except the HARQ process number indication field in the first DCI;

and the first DCI schedules a demodulation reference signal (DMRS) sequence corresponding to the first HARQ process.
The method of claim 26 or 27, wherein the first information comprises an RNTI corresponding to the first DCI, wherein,

under the condition that the RNTI corresponding to the first DCI is a first RNTI, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the RNTI corresponding to the first DCI is a second RNTI, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method of claim 28, wherein the first TB is a TB in an uplink transmission, and wherein the first RNTI comprises at least one of: CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI; and/or the presence of a gas in the gas,

the second RNTI comprises at least one of:

the temporary cell radio network temporary identifier TC-RNTI and the cell radio network temporary identifier C-RNTI.
The method of claim 28, wherein the first TB is a TB in a downlink transmission, and wherein the first RNTI comprises at least one of: CS-RNTI, MCS-C-RNTI; and/or the presence of a gas in the gas,

the second RNTI comprises at least one of:

the temporary cell radio network temporary identifier TC-RNTI and the cell radio network temporary identifier C-RNTI.
The method of any of claims 26-30, wherein the first information comprises a search space corresponding to the first DCI, wherein,

under the condition that the search space corresponding to the first DCI is a first search space, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the search space corresponding to the first DCI is a second search space, the first HARQ process number is less than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method according to claim 31, wherein the first search space comprises a terminal device specific search space and/or wherein the second search space comprises a common search space.
The method of any one of claims 26-32, wherein the first information comprises a CCE index range corresponding to the first DCI, wherein,

under the condition that the search space corresponding to the first DCI is a first CCE index range, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the search space corresponding to the first DCI is a second CCE index range, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a second HARQ process number range.
The method of claim 33, wherein the first CCE index range is configured or preset by the network device and/or wherein the second CCE index range is configured or preset by the network device.
The method of any of claims 26-34, wherein the first information comprises time domain resources corresponding to the first HARQ process scheduled by the first DCI, wherein,

under the condition that the time domain resource corresponding to the first HARQ process corresponds to a first time domain resource range, the first HARQ process number is larger than the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is a first HARQ process number range; or,

and under the condition that the time domain resource corresponding to the first HARQ process corresponds to a second time domain resource range, the first HARQ process number is smaller than or equal to the first numerical value, or the HARQ process number range to which the first HARQ process number belongs is the second HARQ process number range.
The method according to claim 35, wherein the first time domain resource range is configured or preset by the network device, and/or wherein the second time domain resource range is configured or preset by the network device.
The method according to any of claims 28, 31, 33, 35, wherein in case the first HARQ process number is larger than the first value or the range of HARQ process numbers to which the first HARQ process number belongs is the first range of HARQ process numbers, the first information further comprises a first information field in the first DCI except for the HARQ process number indication field.
The method of any one of claims 26-37, wherein the first information comprises a first information field in the first DCI other than the HARQ process number indication field, wherein,

the first HARQ process number is indicated by first information corresponding to the first DCI and a HARQ process number indication field in the first DCI, and includes:

the first HARQ process number is indicated by a part of or all bits in the first information field and all bits in an HARQ process number indication field in the first DCI.
The method of claim 38 wherein the first information field comprises a Redundancy Version (RV) field.
The method of claim 25, wherein the first HARQ process number is less than or equal to the first value, and wherein the first HARQ process number is determined according to a HARQ process number indication field in the first DCI.
The method of claim 40, wherein before the network device sends the first DCI to the terminal device, the method further comprises:

and the network equipment sends second DCI to the terminal equipment, wherein the second DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the second DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.
The method of claim 41, wherein after the network device sends the first DCI to the terminal device, the method further comprises:

and the network equipment sends third DCI to the terminal equipment, wherein the third DCI is used for scheduling the first TB to be transmitted through the first HARQ process, the third DCI corresponds to a second DCI format, and the schedulable maximum HARQ process number of the second DCI format is greater than the first numerical value.
The method of claim 41 or 42, wherein the second DCI format comprises a non-fallback DCI format.
The method of any one of claims 41-43 wherein the first TB is a TB in a downlink transmission and the second DCI format comprises at least one of DCI format 1 _u1 and DCI format 1 _u2; or,

the first TB is a TB in uplink transmission, and the second DCI format includes at least one of DCI format 0_1 and DCI format 0_2.
The method of any of claims 25-44, wherein the first DCI format comprises a fallback DCI format.
The method of any one of claims 25-45, wherein the first TB is a TB in downlink transmission, and wherein the first DCI format comprises DCI format 1_0; or,

the first TB is a TB in uplink transmission, and the first DCI format includes DCI format 0_0.
The method of any one of claims 25-46, further comprising: the network device receives downlink capability information of the terminal device reported by the terminal device, where the downlink capability information is used to indicate that the number of downlink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled downlink transmission is greater than the first value, where the specific value is equal to the first value plus one; and/or the presence of a gas in the gas,

the network device receives uplink capability information of the terminal device, where the uplink capability information is used to indicate that the number of uplink HARQ processes supported by the terminal device is greater than a specific value, or that the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value, where the specific value is equal to the first value plus one.
The method according to any of claims 25-47 wherein the first TB is a TB in downlink transmission, and the HARQ process number range corresponding to the number of downlink HARQ processes configured for the terminal device is the first HARQ process number range, or the maximum HARQ process number that the terminal device supports scheduled downlink transmission is greater than the first value; or,

the first TB is a TB in uplink transmission, and the HARQ process number range corresponding to the uplink HARQ process number configured by the terminal device is the first HARQ process number range, or the maximum HARQ process number supported by the terminal device for scheduled uplink transmission is greater than the first value.
A terminal device, comprising:

a communication unit, configured to receive first downlink control information DCI sent by a network device, where the first DCI is used to schedule transmission of a first transport block TB through a first hybrid automatic repeat request HARQ process, where the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a maximum HARQ process number indicated by an HARQ process number indication field in the first DCI format is a first numerical value; and

and transmitting the first TB through the first HARQ process.
A network device, comprising:

a communication unit, configured to send first downlink control information DCI to a terminal device, where the first DCI is used to schedule transmission of a first transport block TB through a first hybrid automatic repeat request HARQ process, where the first HARQ process corresponds to a first HARQ process number, the first DCI corresponds to a first DCI format, and a maximum HARQ process number indicated by an HARQ process number indication field in the first DCI format is a first numerical value.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 24.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 24.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 24.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 24.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 24.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 25 to 48.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 25 to 48.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 25 to 48.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 25 to 48.
A computer program, characterized in that the computer program causes a computer to perform the method of any of claims 25 to 48.