Data transmission method, device and equipment

Abstract

The present invention provides a data transmission method, apparatus, and device. The method includes: a terminal device receiving downlink control information (DCI) sent by a network device; and the terminal device determining, based on the DCI, whether to provide feedback for a hybrid automatic repeat request (HARQ) process indicated by the DCI. This improves the data transmission efficiency between the network device and the terminal device.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a data transmission method, apparatus, and device. Background Art

[0002] A non-terrestrial network (NTN) refers to a communication network between terminal devices and satellites (also known as network devices).

[0003] In an NTN system, retransmission can be performed using the hybrid automatic repeat request (HARQ) mechanism. In the HARQ mechanism, after a terminal device receives downlink data corresponding to a HARQ process sent by a network device, the terminal device decodes the downlink data and sends HARQ feedback to the network device based on the decoding result. Only after the network device receives the HARQ feedback sent by the terminal device does it send retransmitted data or new data to the terminal device through the HARQ process. However, due to the large transmission delay between the terminal device and the network device and the high number of interactions for data transmission through the HARQ mechanism, the efficiency of data transmission through the HARQ mechanism is low. Summary of the Invention

[0004] The embodiments of the present application provide a data transmission method, apparatus, and device, which improve data transmission efficiency.

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, including:

[0006] The terminal device receives downlink control information DCI sent by the network device;

[0007] The terminal device determines, based on the DCI, whether to provide feedback on the hybrid automatic repeat request HARQ process indicated by the DCI.

[0008] In a second aspect, an embodiment of the present application provides a data transmission method, including:

[0009] The network device determines the downlink control information DCI of the terminal device;

[0010] The network device sends the DCI to the terminal device, and the DCI is used by the terminal device to determine whether to provide feedback on the hybrid automatic repeat request HARQ process indicated by the DCI.

[0011] In a third aspect, an embodiment of the present application provides a data transmission device, including a receiving module and a processing module, wherein:

[0012] The receiving module is used to receive downlink control information DCI sent by the network device;

[0013] The processing module is configured to determine, according to the DCI, whether to provide feedback for a hybrid automatic repeat request HARQ process indicated by the DCI.

[0014] In a fourth aspect, an embodiment of the present application provides a data transmission device, comprising: a processing module and a sending module, wherein:

[0015] The processing module is used to determine the downlink control information DCI of the terminal device;

[0016] The sending module is used to send the DCI to the terminal device, and the DCI is used by the terminal device to determine whether to provide feedback to the hybrid automatic repeat request HARQ process indicated by the DCI.

[0017] In a fifth aspect, an embodiment of the present application provides a terminal device, characterized by including:

[0018] transceivers, processors, and memory;

[0019] The memory stores computer-executable instructions;

[0020] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the data transmission method as described in any one of the first aspects.

[0021] In a sixth aspect, an embodiment of the present application provides a network device, characterized by including:

[0022] transceivers, processors, and memory;

[0023] The memory stores computer-executable instructions;

[0024] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the data transmission method as described in any one of the second aspects.

[0025] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer execution instructions, which, when executed by a processor, are used to implement the data transmission method described in any one of the first aspects.

[0026] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer execution instructions, which, when executed by a processor, are used to implement the data transmission method described in any one of the second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A schematic diagram of the HARQ process and RTT provided in an embodiment of the present application;

[0028] Figure 2A A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0029] Figure 2B A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0030] Figure 3 A schematic diagram of processing a first type of HARQ process provided in an embodiment of the present application;

[0031] Figure 4 A flowchart of a data transmission method provided in an embodiment of the present application;

[0032] Figure 5 A flowchart of another data transmission method provided in an embodiment of the present application;

[0033] Figure 6 A flowchart of another data transmission method provided in an embodiment of the present application;

[0034] Figure 7 A flowchart of another data transmission method provided in an embodiment of the present application;

[0035] Figure 8 A flowchart of another data transmission method provided in an embodiment of the present application;

[0036] Figure 9 A schematic diagram of the structure of a data transmission device provided in an embodiment of the present application;

[0037] Figure 10 A schematic structural diagram of another data transmission device provided in an embodiment of the present application;

[0038] Figure 11 A schematic structural diagram of another data transmission device provided in an embodiment of the present application;

[0039] Figure 12 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0040] Figure 13 A schematic diagram of the structure of the network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] To facilitate understanding, first, the concepts involved in this application are explained.

[0042] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), next-generation communication (5th-Generation, 5G) systems or other communication systems, etc.

[0043] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0044] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0045] The embodiments of the present application are not limited to the spectrum to which they are applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum (also known as unlicensed spectrum or shared spectrum).

[0046] The present application describes various embodiments in conjunction with network devices and terminal devices, wherein: a terminal device generally has wireless transceiver functions and may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. A terminal device may be a station (STAION, ST) in a WLAN, 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 functions, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, and a next-generation communication system, such as a terminal device in a NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network.

[0047] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0048] In the embodiments of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, a wearable terminal device, etc. The terminal device involved in the embodiments of the present application may also be referred to as a terminal, 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 mobile station, a remote station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent or a UE device, etc. The terminal device may also be fixed or mobile.

[0049] As an example and not a limitation, in an embodiment of the present application, the terminal device may be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0050] A network device can be a device used to communicate with a mobile device. A network device can be an access point (AP) in WLAN, a base transceiver station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in a NR network, or a network device in a future evolved PLMN network.

[0051] In the embodiments of the present application, the network device may have a mobile feature. For example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located in a location such as land or water.

[0052] In an embodiment of the present application, a network device provides services for a cell (Cell), and a terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to a 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). The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0053] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is used herein to describe an association relationship between associated objects. For example, it indicates that three possible relationships exist between the associated objects. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates that the associated objects exist in an "or" relationship.

[0054] In order to better describe the principles and specific implementation methods of the embodiments of the present application, the relevant technical contents of the embodiments of the present application are described below.

[0055] Downlink control information (DCI): For terminal devices with downlink services, the network device can schedule the transmission of the physical downlink shared channel (PDSCH) for the terminal device through the downlink authorization DCI. The downlink authorization DCI includes indication information of the physical uplink control channel (PUCCH) resources. After receiving the PDSCH, the terminal device can determine the decoding result of the PDSCH (ACK or NACK information) and feed back the decoding result to the network device through the PUCCH resource. In the NR system, the DCI formats for PDSCH scheduling include DCI format 1_0, DCI format 1_1, and DCI format 1_2. Below, the information field and bit size included in the DCI of each DCI format are introduced in combination with Table 1, Table 2 and Table 3 respectively.

[0056] Table 1

[0057]

[0058]

[0059] In Table 1, the downlink allocation index, the TPC command of the scheduled PUCCH, the PUCCH resource indication, and the PDSCH to HARQ feedback timing indication information fields are used to feed back the HARQ-ACK information corresponding to the PDSCH transmission.

[0060] Table 2

[0061]

[0062]

[0063] In Table 2, the downlink allocation index, TPC command for the scheduled PUCCH, PUCCH resource indication, PDSCH to HARQ feedback timing indication, single HARQ-ACK request, PDSCH group index, new feedback indication, and requested PDSCH group number information fields are used to feedback HARQ-ACK information corresponding to the PDSCH transmission.

[0064] Table 3

[0065]

[0066]

[0067] In Table 3, the downlink allocation index, the TPC command of the scheduled PUCCH, the PUCCH resource indication, and the PDSCH-to-HARQ_feedback timing indication information fields are used to feed back the HARQ-ACK information corresponding to the PDSCH transmission.

[0068] In Tables 2 and 3 above, for DCI formats 1_1 and 1_2, the sizes of most information fields included in the DCI may be configured by the network device through higher-layer parameters (e.g., radio resource control (RRC) signaling). For example, if the number of bits corresponding to an information field in a DCI format is 0, this indicates that the DCI format may not include that information field.

[0069] In Tables 1 to 3 above, if the communication transmission between the network device and the terminal device occurs on a shared spectrum (for example, an unlicensed spectrum), or the terminal device sends PUCCH through resources on an unlicensed spectrum, the above DCI may include a channel access indication (ChannelAccess-CPext) information field; if the communication transmission between the network device and the terminal device occurs on a licensed spectrum, the above DCI does not include a channel access indication (ChannelAccess-CPext) information field.

[0070] For terminal devices with uplink services, the network device can schedule the transmission of the physical uplink shared channel (PUSCH) for the terminal device through the uplink authorization DCI. The uplink authorization DCI may include indication information for determining the PUSCH resource, and the terminal device can transmit PUSCH on the determined PUSCH resource according to the uplink authorization DCI. In the NR system, the DCI format for scheduling PUSCH transmission includes DCI format 0_0, DCI format 0_1, or DCI format 0_2.

[0071] Hybrid Automatic Repeat Request (HARQ) mechanism: The HARQ mechanism is a retransmission mechanism at the medium access control (MAC) layer. It retransmits data that has been lost or erroneously transmitted. The HARQ process consists of an uplink HARQ process and a downlink HARQ process, which are independent of each other.

[0072] In related technologies (such as NR systems), a stop-and-wait protocol is typically used for HARQ retransmission. When using the stop-and-wait protocol for HARQ retransmission, after sending a transport block (TB) through a HARQ process, the transmitter stops and waits for acknowledgment information from the receiver (the acknowledgment information is used to indicate whether the receiver has correctly received the transport block TB). During this waiting period, the transmitter cannot send other TBs to the terminal device through the HARQ process. After receiving a TB corresponding to a HARQ process, the receiver decodes the TB. If the decoding is successful, the receiver sends a positive acknowledgment (ACK) to the transmitter. If the decoding fails, the receiver sends a negative acknowledgment (NACK) to the transmitter. If the transmitter receives the ACK information corresponding to the HARQ process, it can send other TBs to the receiver through the HARQ process. If the transmitter receives a NACK corresponding to the HARQ process, or if the transmitter does not receive any response for a long time, the transmitter can retransmit the TB through the HARQ process. In the above process, when the sending end is a network device, the receiving end may be a terminal device. When the sending end is a terminal device, the receiving end may be a network device or another terminal device.

[0073] In related technologies, a network device may indicate the maximum number of HARQ processes for both uplink and downlink to a terminal device through, for example, semi-static configuration via Radio Resource Control (RRC) signaling. If the network device does not provide corresponding configuration parameters, the number of downlink HARQ processes may be a default value, such as 8. The maximum number of HARQ processes supported by each uplink carrier may be 16. Each HARQ process corresponds to a HARQ process number (HPN), also known as a HARQ ID (Identity).

[0074] Figure 1 Taking downlink transmission as an example, this paper explains how the number of HARQ processes and the round-trip transmission time (RTT) affect the data transmission throughput. Figure 1 As shown in the figure, the maximum number of HARQ processes configured for the terminal device is 16. The 16 HARQ processes include HARQ0 to HARQ15. The 16 HARQ processes can be continuously scheduled within 16ms. Among them, for a HARQ process such as HARQ0, after it is scheduled, the HARQ process HARQ0 is in a waiting state during the data round trip and cannot be used to transmit other data. Therefore, in Figure 1 In the scenario shown, where the maximum number of HARQ processes on a terminal device is 16, the following situations may occur:

[0075] If the RTT is less than 16ms, within the RTT range after HARQ0 is scheduled, when there is business data to be transmitted, the terminal device can always have parallel HARQ processes (one or more of HARQ1 to HARQ15) for data transmission; when the time after HARQ0 is scheduled exceeds the RTT, HARQ0 can be used to transmit data again. Therefore, data can be continuously transmitted on the HARQ entity composed of HARQ0 to HARQ15 without affecting the maximum throughput of the terminal device. In addition, if the RTT is equal to 16ms and the maximum number of HARQ processes configured for the terminal device is 16, it can be seen by the same token that there is always a HARQ process available to transmit business data; however, if the maximum number of HARQ processes configured for the terminal device is less than 16, then when there is business data to be transmitted, it is possible that all HARQ processes are in a state of waiting for feedback from the network device. At this time, no HARQ process is available, affecting the data transmission throughput of the terminal device.

[0076] If the RTT is much longer than 16ms, for example, the RTT in the NTN system can reach 600ms, the actual situation may be that all HARQ processes of the terminal device are in a state of not receiving feedback from the network device. In this case, when the terminal device has service data to transmit, there will be no HARQ process available for a long time, seriously affecting the data transmission throughput of the terminal device.

[0077] That is, in the application scenario of the NTN system or other similar scenarios, due to the significant increase in RTT, the number of HARQ processes configured in the terminal device does not match the system RTT, which ultimately leads to a decrease in system performance.

[0078] In order to solve the above technical problems, the embodiment of the present application proposes a data transmission method. In order to facilitate understanding of the data transmission method shown in the present application, first, in combination with Figure 2A-2B , describes the architecture of the communication system in this application.

[0079] Figure 2A This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 2A , including terminal equipment 201 and satellite 202, the terminal equipment 201 and satellite 202 can communicate wirelessly. The network formed between the terminal equipment 201 and satellite 202 can also be called NTN. Figure 1 In the communication system architecture shown, satellite 202 functions as a base station, and terminal device 201 can communicate directly with satellite 202. In the system architecture, satellite 202 can be referred to as a network device.

[0080] Figure 2B This is a schematic diagram of another communication system architecture provided by an embodiment of the present application. Figure 2B , including terminal equipment 301, satellite 302 and base station 303. Wireless communication can be carried out between terminal equipment 301 and satellite 302, and communication can be carried out between satellite 302 and base station 303. The network formed by terminal equipment 301, satellite 302 and base station 303 can also be called NTN. Figure 2B In the communication system architecture shown, the satellite 302 does not have the function of a base station, and the communication between the terminal device 101 and the base station 303 needs to be relayed by the satellite 302. In this system architecture, the base station 103 can be called a network device.

[0081] It should be noted that Figure 2A-2B The system to which this application is applicable is merely an example. Of course, the method shown in the embodiment of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and this embodiment of this application does not specifically limit this. The embodiment of this application may include at least part of the following content.

[0082] In the present application, in a scenario with a large RTT (such as NTN), in order to improve the data transmission efficiency between the terminal device and the network device, for the downlink HARQ process of the terminal device, the network device can configure or indicate the HARQ feedback function state corresponding to the downlink HARQ process to the terminal device. For example, the HARQ feedback function state corresponding to the downlink HARQ process is configured to be in a non-enabled state. Correspondingly, if the terminal device determines that the HARQ feedback function state corresponding to the downlink HARQ process is in a non-enabled state, the terminal device is scheduled by the downlink authorization to receive data on the downlink HARQ process, and does not perform HARQ-ACK information feedback on the HARQ process according to the downlink authorization. The network device does not need to wait for the HARQ-ACK information feedback corresponding to the HARQ process, and can continue to schedule other data to the terminal device through the HARQ process, so that the network device does not need to wait, thereby improving the data transmission efficiency between the terminal device and the network device.

[0083] Alternatively, for the uplink HARQ process of the terminal device, the network device can configure or indicate the HARQ feedback function state corresponding to the uplink HARQ process to the terminal device. For example, the HARQ feedback function state corresponding to the uplink HARQ process is configured to be in a non-enabled state. Accordingly, if the terminal device determines that the HARQ feedback function state corresponding to the uplink HARQ process is in a non-enabled state, then after the terminal device is authorized by the uplink to send a TB on the uplink HARQ process, it does not need to wait for the feedback of the network device for the TB, and can use the uplink HARQ process again according to the instruction of the network device to transmit another TB, thereby improving the data transmission efficiency between the terminal device and the network device.

[0084] In the present application, the HARQ feedback function state corresponding to the downlink HARQ process or uplink HARQ process of the terminal device may be in a disabled state. For example, the network device may configure the HARQ feedback function state corresponding to some or all HARQ processes of the terminal device to be enabled or disabled. The disabled state is also referred to as a disabled state.

[0085] Optionally, for the downlink HARQ process, if the HARQ feedback function state corresponding to a HARQ process is enabled, then after the terminal device receives the transmission block TB through the HARQ process, it needs to send the HARQ-ACK information corresponding to the TB to the network device; or, the terminal device needs to receive feedback from the network device on the TB before it can use the HARQ process again; or, the terminal device needs to provide corresponding HARQ-ACK information feedback based on the DCI that schedules the TB; or, the terminal device sends the HARQ-ACK information corresponding to the first physical channel transmitted in the HARQ process to the network device based on the DCI that schedules the transmission of the first physical channel through the HARQ process.

[0086] Optionally, for the downlink HARQ process, if the HARQ feedback function state corresponding to a HARQ process is disabled, then after the terminal device receives a TB through the HARQ process, it does not need to send the HARQ-ACK information corresponding to the TB to the network device; or, the terminal device can use the HARQ process again without receiving feedback from the network device on the TB; or, the terminal device does not need to provide corresponding HARQ-ACK information feedback based on the DCI that schedules the TB; or, the terminal device does not transmit the DCI of the first physical channel through the HARQ process according to the scheduling, and sends the HARQ-ACK information corresponding to the first physical channel transmitted in the HARQ process to the network device.

[0087] Optionally, in the present application, the HARQ-ACK information includes ACK information or NACK information corresponding to the decoding result of the TB.

[0088] Optionally, for the uplink HARQ process, if the HARQ feedback function status corresponding to a HARQ process is enabled, then after the terminal device sends the transmission block TB through the HARQ process, it needs to receive feedback from the network device on the TB before it can use the HARQ process again (for example, use the HARQ process to send a new TB or send the TB again); or, the terminal device waits for feedback from the network device on the first physical channel transmitted in the HARQ process.

[0089] Optionally, for the uplink HARQ process, if the HARQ feedback function status corresponding to a HARQ process is disabled, it means that after the terminal device sends a TB through the HARQ process, it does not need to receive feedback from the network device on the TB before using the HARQ process (for example, using the HARQ process to send a new TB or send the TB again); or, the terminal device does not wait for feedback from the network device on the first physical channel transmitted in the HARQ process.

[0090] Optionally, the time interval between two uses of the same HARQ process is greater than or equal to a first time length, and / or the time interval between two uses of the same HARQ process may be less than a second time length. The first time length is determined based on a decoding time of a receiving device, and the second time length is determined based on an RTT. The first time length is less than the second time length.

[0091] Optionally, for downlink transmission, the feedback includes the terminal device sending HARQ-ACK information to the network device.

[0092] Optionally, for uplink transmission, the feedback includes the network device sending HARQ-ACK information to the terminal device, or the network device sending uplink authorization DCI to the terminal device.

[0093] Optionally, the type of the HARQ process may include a first type or a second type, wherein the first type of HARQ process may include a HARQ process in which the HARQ feedback function state is disabled, and the second type of HARQ process may include a HARQ process in which the HARQ feedback function state is enabled.

[0094] Optionally, for the downlink process:

[0095] The first type of HARQ process can also be called a feedback-disabled HARQ process, or an uplink HARQ feedback-disabled HARQ process. The terminal device does not provide feedback for the first type of HARQ process (it can also be understood as the terminal device does not respond to a scheduling of the first type of HARQ process). That is, after the network device sends a TB to the terminal device through the HARQ process, the terminal device does not need to send a feedback message (ACK or NACK) corresponding to the transmission of the HARQ process to the network device, and the network device can send a TB through the HARQ process, for example, transmit a new TB through the HARQ process. The feedback message may include HARQ-ACK information, and the HARQ-ACK may be ACK or NACK.

[0096] Next, combine Figure 3 , the first type of HARQ process is described.

[0097] Figure 3 This is a schematic diagram of processing the first type of HARQ process provided in an embodiment of the present application. Figure 3 , assuming that the terminal device includes multiple HARQ processes, and HARQ process 7 among the multiple HARQ processes is a first type of HARQ process. The network device sends the downlink data corresponding to PDSCH 0 to the terminal device through HARQ process 7, and NDI is 0. Since HARQ process 7 is a first type of HARQ process, after the terminal device receives the downlink data corresponding to HARQ process 7, the terminal device does not need to send a feedback message of HARQ process 7 to the network device, and the network device does not need to wait for the feedback message of HARQ process 7 sent by the terminal device, and can send other data to the terminal device through HARQ process 7. For example, the network device can send the downlink data corresponding to PSDCH 1 to the terminal device through HARQ process 7, and flip the NDI to 1, wherein flipping the NDI indicates that the downlink data transmitted through the HARQ process 7 is a new downlink data packet. After the network device sends the downlink data corresponding to PDSCH 1 to the terminal device, the network device can continue to send a new downlink data packet corresponding to PDSCH 2 to the terminal device, and flip the NDI to 0.

[0098] The second type of HARQ process can also be called a feedback-enabled HARQ process, or an uplink HARQ feedback-enabled HARQ process. The terminal device provides feedback to the second type of HARQ process (which can also be understood as the terminal device responding to the second type of HARQ process). That is, after the network device sends a TB to the terminal device through the HARQ process, the terminal device needs to send HARQ feedback (ACK or NACK) corresponding to the HARQ process to the network device. After the network device receives the HARQ-ACK, the network device can send other TBs through the HARQ process.

[0099] Optionally, for the uplink process:

[0100] The first type of HARQ process may also be referred to as a feedback-disabled HARQ process, or a downlink HARQ feedback-disabled HARQ process. After the terminal device sends uplink data to the network device through the first type of HARQ process, within a preset duration, such as within an RTT duration, if the network device again schedules the terminal device to perform uplink data transmission through the HARQ process, the terminal device may perform uplink data transmission through the HARQ process.

[0101] The second type of HARQ process can also be called a feedback-enabled HARQ process, or a downlink HARQ feedback-enabled HARQ process. Within a preset duration after a terminal device sends uplink data to a network device via the first type of HARQ process, if the network device reschedules the terminal device to transmit uplink data via the HARQ process, the terminal device may ignore the scheduling of the HARQ process. In other words, the terminal device does not expect the network device to reschedule the HARQ process within the preset duration.

[0102] In the present application, the network device may configure some HARQ processes in the terminal device to be of the first type or in a disabled state, and the network device may also indicate the type of the HARQ process in the terminal device through DCI. As previously mentioned, when at least some of the HARQ processes in the terminal device are of the first type, the data transmission efficiency between the terminal device and the network device may be improved.

[0103] The technical solutions shown in this application are described in detail below through specific embodiments. It should be noted that the following embodiments can exist independently or in combination with each other, and the same or similar contents will not be repeated in different embodiments.

[0104] Figure 4 This is a flow chart of a data transmission method provided in an embodiment of the present application. Figure 4 ,include:

[0105] S401: The network device determines DCI.

[0106] Optionally, the network device determines DCI and schedules the terminal device to perform downlink reception through the DCI, for example, scheduling the terminal device to perform PDSCH reception, wherein the DCI includes indication information of the HARQ process number corresponding to the downlink transmission.

[0107] Optionally, the network device determines DCI and schedules the terminal device to perform uplink transmission through the DCI, for example, scheduling the terminal device to perform PUSCH transmission, wherein the DCI includes indication information of the HARQ process number corresponding to the uplink transmission.

[0108] Optionally, when determining the DCI, the network device may determine the DCI corresponding to the HARQ process of that type based on the type of the HARQ process to be scheduled by the DCI (the HARQ process indicated by the HARQ process number included in the DCI). For example, the network device determines that the HARQ process to be scheduled by the DCI is a non-enabled HARQ process, so the network device may determine the DCI based on the determined HARQ process type. The type of the HARQ process may be configured by the network device. The type of the HARQ process may be the first type or the second type.

[0109] The network device may or may not pre-configure the type of the HARQ process in the terminal device. If the network device pre-configures the type of the HARQ process, the network device may determine the type of the HARQ process based on the pre-configuration. After the network device pre-configures the type of the HARQ process in the terminal device, the network device may also send the configuration to the terminal device. For example, the network device may send the configuration to the terminal device through RRC signaling, a medium access control (MAC) control element (CE) or DCI. Of course, the network device may also not send the configuration to the terminal device. If the network device does not pre-configure the type of the HARQ process, the network device may determine the type of the HARQ process corresponding to the DCI only when sending the DCI to the terminal device.

[0110] Optionally, the network device or terminal device may determine first information of the DCI for scheduling the HARQ process of the configured type based on the type of the HARQ process. The first information includes at least one of the following information: the length of the DCI; or the radio network temporary identifier (RNTI) corresponding to the DCI; or the search space corresponding to the DCI; or the aggregation level corresponding to the DCI.

[0111] It should be noted that when the first information is different, the process of the network device determining the first information may be different. Figure 5-Figure 8 The above is described in detail in the embodiment shown in the figure and will not be described again here.

[0112] Optionally, the network device may configure the first type of HARQ process to repeat transmission N times. The network device may configure the second type of HARQ process to not repeat transmission, or to repeat transmission for a number of times M. M and N are integers greater than 1. M and N may be different.

[0113] Optionally, the network device may determine the configuration parameter of the first type of HARQ process as the first configuration parameter, and the network device may determine the configuration parameter of the second type of HARQ process as the second configuration parameter, wherein at least one of the first configuration parameter and the second configuration parameter is different.

[0114] S402: The network device sends DCI to the terminal device.

[0115] S403. The terminal device determines, based on the DCI, the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI.

[0116] Optionally, for downlink transmission, the terminal device determines, based on the DCI, whether to provide feedback for the HARQ process scheduled by the DCI.

[0117] Optionally, the terminal device may determine whether to provide feedback on the HARQ process scheduled by the DCI in the following manner: the terminal device determines the type of the HARQ process based on the DCI, and determines whether to provide feedback on the HARQ process scheduled by the DCI based on the type of the HARQ process.

[0118] Optionally, the terminal device may determine whether to provide feedback for a HARQ process scheduled by a DCI in the following manner: the terminal device may determine whether to provide feedback for the HARQ process indicated by the DCI based on first information in the DCI. Optionally, the first information includes at least one of the following: the length of the DCI; or the RNTI corresponding to the DCI; or the search space corresponding to the DCI; or the aggregation level corresponding to the DCI. Optionally, the terminal device may determine the type of the HARQ process based on the first information in the DCI, and determine whether to provide feedback for the HARQ process based on the type of the HARQ process.

[0119] In the above implementation, the type of the HARQ process is the first type or the second type. If the type of the HARQ process is the first type, the terminal device determines not to provide feedback on the HARQ process; or if the type of the HARQ process is the second type, the terminal device determines to provide feedback on the HARQ process.

[0120] Optionally, for uplink transmission, the terminal device determines the HARQ feedback function state corresponding to the HARQ process scheduled by the DCI based on the DCI. Optionally, the terminal device can determine the HARQ feedback function state corresponding to the HARQ process scheduled by the DCI based on the first information of the DCI. Optionally, the first information includes at least one of the following information: the length of the DCI; or the RNTI corresponding to the DCI; or the search space corresponding to the DCI; or the aggregation level corresponding to the DCI. Optionally, the terminal device can determine the type of the HARQ process based on the first information of the DCI, and determine the HARQ feedback function state corresponding to the HARQ process based on the type of the HARQ process.

[0121] It should be noted that when the first information is different, the HARQ feedback function state corresponding to the HARQ process determined by the terminal device according to the first information is also different, or when the first information is different, the terminal device determines the type of the HARQ process according to the first information in a different manner. Figure 5-Figure 8 The above is described in detail in the embodiment shown in the figure and will not be described again here.

[0122] In a possible embodiment, the terminal device may determine, based on the DCI, the type of the HARQ process indicated by the DCI, where the type of the HARQ process is the first type or the second type. After the terminal device determines the type of the HARQ process, it may perform other processing based on the type of the HARQ process. The embodiments of the present application do not specifically limit the processing performed by the terminal device based on the HARQ process.

[0123] In the data transmission method provided in an embodiment of the present application, when a terminal device determines based on DCI that it does not need to provide feedback on a HARQ process indicated by the DCI, the terminal device does not need to provide feedback on the HARQ process, and the network device can transmit other data through the HARQ process without waiting for feedback from the terminal device, thereby improving data transmission efficiency. Furthermore, the terminal device can determine whether feedback on the HARQ process is required based on the DCI, and the network device does not need to send additional signaling to the terminal device, thereby saving signaling overhead.

[0124] Based on any of the above embodiments, Figure 5-Figure 8 The illustrated embodiment describes a process in which a terminal device determines whether to provide feedback to a HARQ process based on different first information.

[0125] Figure 5 A flow chart of another data transmission method provided in an embodiment of the present application. Figure 5 In the embodiment shown, the first information is the length of the DCI. Figure 5 , the method may include:

[0126] S501. A network device determines the length of a DCI, and determines the DCI according to the length of the DCI.

[0127] The network device may determine the length of the DCI according to the type of the HARQ process corresponding to the DCI, and generate the DCI according to the length of the DCI.

[0128] For example, if the HARQ process type is the first type, the network device determines the length of the corresponding DCI to be the first DCI length; or if the HARQ process type is the second type, the network device determines the length of the corresponding DCI to be the second DCI length. The first DCI length and the second DCI length are not equal. Optionally, the first DCI length is smaller than the second DCI length.

[0129] Optionally, when the length of the DCI is the first DCI length, the DCI does not include at least one of the following information fields: TPC command of the physical uplink control channel PUCCH, downlink assignment index (DAI), PUCCH resource indication, timing indication of PDSCH to HARQ feedback, single HARQ-ACK feedback request, PDSCH grouping indication, new feedback indication NFI, and triggered feedback group indication.

[0130] Optionally, when the length of the DCI is the second DCI length, the DCI includes at least one of the following information fields: TPC command of PUCCH, downlink allocation indication DAI, PUCCH resource indication, timing indication of PDSCH to HARQ feedback, single HARQ-ACK feedback request, PDSCH grouping indication, new feedback indication NFI, and triggered feedback group indication.

[0131] When DCI schedules different types of HARQ processes, the corresponding DCI lengths are different, for example, the first DCI length or the second DCI length. The information fields included in the DCI of the first DCI length differ from the information fields included in the DCI of the second DCI length, at least in part. This is explained below using downlink scheduling as an example, with reference to Tables 4-6.

[0132] For example, when the DCI format is DCI format 1_0, the number of bits of each DCI field (also referred to as an information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 4:

[0133] Table 4

[0134]

[0135]

[0136] Referring to Table 4, if the network device determines that the DCI length is the first DCI length, the lengths of the following four DCI fields (also referred to as information fields) in the DCI are 0: downlink allocation index, scheduled PUCCH TPC command, PUCCH resource indication, and PDSCH to HARQ feedback timing indication. In other words, if the network device determines that the DCI length is the first DCI length, the DCI does not include the following four information fields: downlink allocation index, scheduled PUCCH TPC command, PUCCH resource indication, and PDSCH to HARQ feedback timing indication.

[0137] For example, when the DCI format is DCI format 1_1, the number of bits of each DCI field (also referred to as an information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 5:

[0138] Table 5

[0139]

[0140]

[0141]

[0142] Please refer to Table 5. If the network device determines that the length of the DCI is the first DCI length, the length of the following eight DCI fields (also referred to as information fields) in the DCI is 0: downlink allocation index, TPC command for scheduled PUCCH, PUCCH resource indication, PDSCH to HARQ feedback timing indication, single HARQ-ACK request, PDSCH group index, new feedback indication, and requested number of PDSCH groups. In other words, if the network device determines that the length of the DCI is the first DCI length, the DCI does not include the following eight information fields: downlink allocation index, TPC command for scheduled PUCCH, PUCCH resource indication, PDSCH to HARQ feedback timing indication, single HARQ-ACK request, PDSCH group index, new feedback indication, and requested number of PDSCH groups.

[0143] For example, when the DCI format is DCI format 1_2, the number of bits of each DCI field (also referred to as an information field) in the DCI corresponding to the first DCI length and the second DCI length is as shown in Table 6:

[0144] Table 6

[0145]

[0146]

[0147] Please refer to Table 6. If the network device determines that the length of the DCI is the first DCI length, the lengths of the following four DCI fields (also referred to as information fields) in the DCI are 0: downlink allocation index, scheduled PUCCH TPC command, PUCCH resource indication, and PDSCH-to-HARQ_feedback timing indication. In other words, if the network device determines that the length of the DCI is the first DCI length, the DCI does not include the following four information fields: downlink allocation index, scheduled PUCCH TPC command, PUCCH resource indication, and PDSCH-to-HARQ_feedback timing indication.

[0148] S502: The network device sends DCI to the terminal device.

[0149] S503. The terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the length of the DCI.

[0150] Optionally, the terminal device may first determine the length of the DCI, and then determine whether to provide feedback for the HARQ process indicated by the DCI based on the length of the DCI. The DCI length may be a first DCI length or a second DCI length. If the DCI length is the first DCI length, the terminal device determines not to provide feedback for the HARQ process; or if the DCI length is the second DCI length, the terminal device determines to provide feedback for the HARQ process.

[0151] The terminal device can perform DCI detection (also known as PDCCH detection) through different DCI lengths, and determine the DCI length used when detecting the DCI as the length of the DCI. For example, if the terminal device detects the DCI according to the first DCI length, it can be determined that the length of the DCI is the first DCI length; or, if the terminal device detects the DCI according to the second DCI length, it can be determined that the length of the DCI is the second DCI length. In the process of performing PDCCH detection by the terminal device, when the length of the DCI is the first DCI length, the information bits included in the DCI are relatively few, and the reliability of the PDCCH detection can be increased when the same PDCCH transmission resources are used.

[0152] Optionally, the above detection may be blind detection. For ease of description, the following description will be made by taking blind detection as an example. The blind detection involved below may also be referred to as DCI blind detection or PDCCH blind detection.

[0153] In actual applications, if a terminal device uses the first DCI length and the second DCI length for blind detection, the terminal device may perform blind detection more frequently. To reduce the number of blind detections performed by the terminal device, the terminal device may determine the DCI length used for blind detection based on the configuration of its HARQ process by the network device.

[0154] For example, if all HARQ processes in the terminal device are configured as the first type, the DCI length used by the terminal device for PDCCH blind detection includes the first DCI length. In this case, the terminal device may not use the second DCI length for blind detection, so that the terminal device performs fewer blind detections.

[0155] For example, if all HARQ processes in the terminal device are configured as the second type, the DCI length used by the terminal device for PDCCH blind detection includes the second DCI length. In this case, the terminal device may not use the first DCI length for blind detection, so that the terminal device performs fewer blind detections.

[0156] For example, if some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the DCI length used by the terminal device for PDCCH detection includes the first DCI length and the second DCI length.

[0157] In actual application, in addition to receiving DCI for scheduling data transmission, the terminal device may also receive other types of DCI. When the terminal device receives other types of DCI, the terminal device can perform blind detection of other types of DCI using other DCI lengths. In other words, the DCI length used by the terminal device for blind detection can also be other DCI lengths (DCI lengths other than the first DCI length and the second DCI length).

[0158] When a terminal device uses a first DCI length and a second DCI length for PDCCH blind detection, in order to reduce the number of blind detections performed by the terminal device, different aggregation levels can be configured for different DCI lengths. For example, the first DCI length is configured to correspond to a first aggregation level, and the second DCI length is configured to correspond to a second aggregation level, and the first aggregation level is less than or equal to the second aggregation level. Since the first DCI length is less than the second DCI length, while ensuring the reliability of the same PDCCH transmission, the resources required to transmit the DCI corresponding to the first DCI length are less than the resources required to transmit the DCI corresponding to the second DCI length, thereby reducing the number of PDCCH blind detections performed by the terminal device.

[0159] In order to reduce false alarms of DCI blind detection, after the terminal device detects DCI through a DCI length, the terminal device can further determine whether the type of HARQ process corresponding to the DCI is consistent with the type of HARQ process corresponding to the DCI length. If they are consistent, it will determine whether to provide feedback to the HARQ process. If they are inconsistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.

[0160] For example, if the terminal device detects the DCI according to the first DCI length, the terminal device can determine that the type of the HARQ process indicated by the DCI is the first type according to the first DCI length. The terminal device can further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device can determine not to provide feedback for the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0161] For example, if the terminal device detects the DCI according to the second DCI length, the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type according to the second DCI length. The terminal device can further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to provide feedback on the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0162] In the above two examples, other methods may be: the terminal device determines the type of the HARQ process through the type of the HARQ process pre-configured by the network device; or the terminal device may determine the type of the HARQ process through Figure 6-Figure 8 The type of HARQ process is determined in any manner in the embodiments.

[0163] exist Figure 5 In the illustrated embodiment, a terminal device determines whether to provide feedback for the HARQ process indicated by the DCI based on the length of the DCI. If the terminal device determines not to provide feedback for the HARQ process indicated by the DCI, the terminal device does not need to provide feedback for that HARQ process, and the network device can transmit other data through that HARQ process without waiting for feedback from the terminal device, thereby improving data transmission efficiency. Furthermore, the type of HARQ process can be implicitly indicated by the length of the DCI, eliminating the need for additional signaling in the DCI and saving signaling overhead.

[0164] Figure 6 A flow chart of another data transmission method provided in an embodiment of the present application. Figure 6 In the embodiment shown, the first information is the RNTI corresponding to the DCI. Figure 6 , the method may include:

[0165] S601: The network device determines the RNTI corresponding to the DCI, and scrambles the DCI according to the RNTI.

[0166] The network device may determine the RNTI corresponding to the DCI according to the type of the HARQ process indicated by the DCI.

[0167] For example, if the type of the HARQ process is the first type, the network device determines that the RNTI corresponding to the DCI is the first RNTI; or if the type of the HARQ process is the second type, the network device determines that the RNTI corresponding to the DCI is the second RNTI.

[0168] The network device can configure a first RNTI and / or a second RNTI for the terminal device, wherein the first RNTI is used to scramble the DCI (downlink authorization DCI) corresponding to the first type of HARQ process, and the second RNTI is used to scramble the downlink authorization DCI corresponding to the second type of HARQ process.

[0169] For example, if all HARQ processes in the terminal device are configured as the first type, the network device may configure a first RNTI for the terminal device. In other words, the RNTI configured by the network device for the terminal device includes the first RNTI. If all HARQ processes in the terminal device are configured as the second type, the network device may configure a second RNTI for the terminal device. In other words, the RNTI configured by the network device for the terminal device includes the second RNTI. If some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the network device may configure a first RNTI and a second RNTI for the terminal device. In other words, the RNTI configured by the network device for the terminal device includes the first RNTI and the second RNTI.

[0170] After the network device determines to obtain the DCI and the RNTI corresponding to the DCI, the network device may scramble the DCI using the RNTI corresponding to the DCI.

[0171] It should be noted that if the HARQ process type is the first type, the length of the DCI generated by the network device may be the first length. If the HARQ process type is the second type, the length of the DCI generated by the network device may be the second length. This process can be seen in S501 and will not be further described here.

[0172] S602: The network device sends DCI to the terminal device.

[0173] S603. The terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the RNTI corresponding to the DCI.

[0174] Optionally, the terminal device may first determine the RNTI corresponding to the DCI, and then determine whether to provide feedback for the HARQ process indicated by the DCI based on the RNTI corresponding to the DCI. The RNTI corresponding to the DCI is the first RNTI or the second RNTI. If the RNTI corresponding to the DCI is the first RNTI, the terminal device determines not to provide feedback for the HARQ process, or, if the RNTI corresponding to the DCI is the second RNTI, the terminal device determines to provide feedback for the HARQ process.

[0175] The terminal device can perform DCI detection (also known as PDCCH detection) through different RNTIs, and determine the RNTI used when detecting the DCI as the RNTI corresponding to the DCI. For example, if the terminal device detects the DCI based on the first RNTI, it can be determined that the RNTI corresponding to the DCI is the first RNTI; or, if the terminal device detects the DCI based on the second RNTI, it can be determined that the RNTI corresponding to the DCI is the second RNTI. In the above process, whether to feedback the HARQ process can be determined by the RNTI corresponding to the DCI, without adding indication information in the DCI, which not only saves signaling overhead, but also makes the reliability of PDCCH detection higher.

[0176] Optionally, the above detection may be a blind detection. For ease of description, the following description will be made by taking the blind detection as an example.

[0177] In actual application, if the terminal device uses the first RNTI and the second RNTI for blind detection, the terminal device may perform blind detection more frequently. In order to reduce the number of blind detections performed by the terminal device, the terminal device can determine the RNTI used for blind detection based on the configuration of its HARQ process by the network device.

[0178] For example, if all HARQ processes in the terminal device are configured as the first type, the RNTI used by the terminal device for PDCCH detection includes the first RNTI. In this case, the terminal device may not use the second RNTI for blind detection, so that the terminal device performs fewer blind detections.

[0179] For example, if all HARQ processes in the terminal device are configured as the second type, the RNTI used by the terminal device for PDCCH detection includes the second RNTI. In this case, the terminal device may not use the first RNTI for blind detection, so that the terminal device performs fewer blind detections.

[0180] For example, if some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the RNTI used by the terminal device for PDCCH detection includes the first RNTI and the second RNTI.

[0181] To reduce false alarms from blind DCI detection, after a terminal device detects DCI using an RNTI, it can further determine whether the type of HARQ process corresponding to the DCI is consistent with the type of HARQ process corresponding to the RNTI. If they are consistent, it determines whether to provide feedback for the HARQ process. If they are inconsistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.

[0182] For example, if the terminal device detects the DCI through the first RNTI, the terminal device can determine that the type of the HARQ process indicated by the DCI is the first type based on the first RNTI. The terminal device can further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device can determine not to provide feedback for the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0183] For example, if the terminal device detects the DCI through the second RNTI, the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type according to the second RNTI. The terminal device can further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to provide feedback on the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0184] In the above two examples, other methods may be: the terminal device determines the type of the HARQ process through the type of the HARQ process pre-configured by the network device; or the terminal device may determine the type of the HARQ process through Figure 5 、 Figure 7-Figure 8 The type of HARQ process is determined in any manner in the embodiments.

[0185] exist Figure 6 In the illustrated embodiment, a terminal device can determine whether to provide feedback for the HARQ process indicated by the DCI based on the RNTI corresponding to the DCI. If the terminal device determines not to provide feedback for the HARQ process indicated by the DCI, the terminal device does not need to provide feedback for that HARQ process, and the network device can transmit other data through that HARQ process without waiting for feedback from the terminal device, thereby improving data transmission efficiency. Furthermore, the RNTI corresponding to the DCI implicitly indicates the type of HARQ process, eliminating the need to add additional signaling in the DCI and saving signaling overhead.

[0186] Figure 7 A flow chart of another data transmission method provided in an embodiment of the present application. Figure 7 In the embodiment shown, the first information is the search space corresponding to the DCI. Figure 7, the method may include:

[0187] S701: A network device determines a DCI and a search space corresponding to the DCI.

[0188] The network device may determine the search space corresponding to the DCI according to the type of the HARQ process indicated by the DCI.

[0189] For example, if the type of the HARQ process is the first type, the network device determines that the search space corresponding to the DCI is the first search space; or if the type of the HARQ process is the second type, the network device determines that the search space corresponding to the DCI is the second search space.

[0190] The network device may configure a first search space and / or a second search space for the terminal device, wherein the first search space is used to transmit the DCI (downlink grant DCI) corresponding to the first type of HARQ process, and the second search space is used to transmit the DCI corresponding to the second type of HARQ process. Of course, the network device may also configure other search spaces for the terminal device.

[0191] For example, if all HARQ processes in the terminal device are configured as the first type, the network device may configure a first search space for the terminal device. In other words, the search space configured by the network device for the terminal device includes the first search space. If all HARQ processes in the terminal device are configured as the second type, the network device may configure a second search space for the terminal device. In other words, the search space configured by the network device for the terminal device includes the second search space. If some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the network device may configure the first search space and the second search space for the terminal device. In other words, the search space configured by the network device for the terminal device includes the first search space and the second search space.

[0192] It should be noted that if the HARQ process type is the first type, the length of the DCI generated by the network device may be the first length. If the HARQ process type is the second type, the length of the DCI generated by the network device may be the second length. This process can be described in S501 and will not be described in detail here. And / or, if the HARQ process type is the first type, the RNTI corresponding to the DCI determined by the network device may be the first RNTI. If the HARQ process type is the second type, the RNTI corresponding to the DCI determined by the network device may be the second RNTI. This process can be described in S601 and will not be described in detail here.

[0193] S702. The network device sends DCI to the terminal device through the search space corresponding to the DCI.

[0194] For example, if the search space corresponding to the DCI is the first search space, the network device transmits the DCI through the first search space. If the search space corresponding to the DCI is the second search space, the network device transmits the DCI through the second search space.

[0195] S703. The terminal device determines the HARQ feedback function status corresponding to the HARQ process scheduled by the DCI according to the search space corresponding to the DCI.

[0196] Optionally, the terminal device may first determine the search space corresponding to the DCI, and then determine whether to provide feedback for the HARQ process indicated by the DCI based on the search space corresponding to the DCI. The search space corresponding to the DCI is the first search space or the second search space. If the search space corresponding to the DCI is the first search space, the terminal device determines not to provide feedback for the HARQ process, or, if the search space corresponding to the DCI is the second search space, the terminal device determines to provide feedback for the HARQ process.

[0197] The terminal device can perform DCI detection (also known as PDCCH detection) through different search spaces, and determine the search space used when the DCI is detected as the search space corresponding to the DCI. For example, if the terminal device detects the DCI based on the first search space, it can be determined that the search space corresponding to the DCI is the first search space; or, if the terminal device detects the DCI based on the second search space, it can be determined that the search space corresponding to the DCI is the second search space. In the above process, whether to feedback the HARQ process can be determined through the search space corresponding to the DCI, without adding indication information in the DCI, which not only saves signaling overhead, but also makes the reliability of PDCCH detection higher.

[0198] Optionally, the above detection may be a blind detection. For ease of description, the following description will be made by taking the blind detection as an example.

[0199] In actual application, if the terminal device uses the first search space and the second search space for blind detection, the terminal device may perform blind detection more frequently. In order to reduce the number of blind detections performed by the terminal device, the terminal device may determine the search space used for blind detection based on the configuration of its HARQ process by the network device.

[0200] For example, if all HARQ processes in the terminal device are configured as the first type, the search space used by the terminal device for PDCCH detection includes the first search space. In this case, the terminal device may not use the second search space for blind detection, so that the terminal device performs fewer blind detections.

[0201] For example, if all HARQ processes in the terminal device are configured as the second type, the search space used by the terminal device for PDCCH detection includes the second search space. In this case, the terminal device may not use the first search space for blind detection, so that the terminal device performs fewer blind detections.

[0202] For example, if some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the search space used by the terminal device for PDCCH detection includes the first search space and the second search space.

[0203] To reduce false alarms from blind DCI detection, after a terminal device detects DCI using a search space, it can further determine whether the type of HARQ process corresponding to the DCI is consistent with the type of HARQ process corresponding to the search space. If they are consistent, it determines whether to provide feedback for the HARQ process. If they are inconsistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.

[0204] For example, if the terminal device detects DCI through the first search space, the terminal device can determine that the type of the HARQ process indicated by the DCI is the first type based on the first search space. The terminal device can further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device can determine not to provide feedback for the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0205] For example, if the terminal device detects DCI through the second search space, the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type based on the second search space. The terminal device can further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to provide feedback on the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0206] In the above two examples, other methods may be: the terminal device determines the type of the HARQ process through the type of the HARQ process pre-configured by the network device; or the terminal device may determine the type of the HARQ process through Figure 5 、 Figure 6 or Figure 8 The type of HARQ process is determined in any manner in the embodiments.

[0207] exist Figure 7 In the illustrated embodiment, a terminal device can determine whether to provide feedback for the HARQ process indicated by the DCI based on the search space corresponding to the DCI. If the terminal device determines not to provide feedback for the HARQ process indicated by the DCI, the terminal device does not need to provide feedback for that HARQ process, and the network device can transmit other data through that HARQ process without waiting for feedback from the terminal device, thereby improving data transmission efficiency. Furthermore, the search space corresponding to the DCI can implicitly indicate the type of HARQ process, eliminating the need to add additional signaling in the DCI and saving signaling overhead.

[0208] Figure 8 A flow chart of another data transmission method provided in an embodiment of the present application. Figure 8 In the embodiment shown, the first information is the aggregation level corresponding to the DCI. Figure 8 , the method may include:

[0209] S801. A network device determines a DCI and an aggregation level corresponding to the DCI.

[0210] The network device may determine the aggregation level corresponding to the DCI according to the type of the HARQ process indicated by the DCI.

[0211] For example, if the HARQ process type is the first type, the network device determines that the aggregation level corresponding to the DCI is the first aggregation level; or if the HARQ process type is the second type, the network device determines that the aggregation level corresponding to the DCI is the second aggregation level.

[0212] The network device may configure the first aggregation level and / or the second aggregation level for the terminal device. Of course, the network device may also configure other aggregation levels for the terminal device.

[0213] For example, if all HARQ processes in a terminal device are configured as the first type, the network device may configure a first aggregation level for the terminal device. In other words, the aggregation level configured by the network device for the terminal device includes the first aggregation level. If all HARQ processes in the terminal device are configured as the second type, the network device may configure a second aggregation level for the terminal device. In other words, the aggregation level configured by the network device for the terminal device includes the second aggregation level. If some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the network device may configure the first aggregation level and the second aggregation level for the terminal device. In other words, the aggregation level configured by the network device for the terminal device includes the first aggregation level and the second aggregation level.

[0214] It should be noted that if the HARQ process type is the first type, the length of the DCI generated by the network device may be the first length. If the HARQ process type is the second type, the length of the DCI generated by the network device may be the second length. This process can be described in S501 and will not be further described here. And / or, if the HARQ process type is the first type, the network device may determine that the RNTI corresponding to the DCI may be the first RNTI. If the HARQ process type is the second type, the network device may determine that the RNTI corresponding to the DCI may be the second RNTI. This process can be described in S601 and will not be further described here. And / or, if the HARQ process type is the first type, the network device may determine that the search space corresponding to the DCI may be the first search space. If the HARQ process type is the second type, the network device may determine that the search space corresponding to the DCI may be the second search space. This process can be described in S701 and will not be further described here.

[0215] S802. The network device sends DCI to the terminal device according to the aggregation level.

[0216] S803. The terminal device determines the HARQ feedback function state corresponding to the HARQ process scheduled by the DCI according to the aggregation level corresponding to the DCI.

[0217] Optionally, the terminal device may first determine the aggregation level corresponding to the DCI, and then determine whether to provide feedback for the HARQ process indicated by the DCI based on the aggregation level corresponding to the DCI. The aggregation level corresponding to the DCI is the first aggregation level or the second aggregation level. If the aggregation level corresponding to the DCI is the first aggregation level, the terminal device determines not to provide feedback for the HARQ process, or, if the aggregation level corresponding to the DCI is the second aggregation level, the terminal device determines to provide feedback for the HARQ process.

[0218] The terminal device can perform DCI detection (also known as PDCCH detection) at different aggregation levels, and determine the aggregation level used when detecting the DCI as the aggregation level corresponding to the DCI. For example, if the terminal device detects the DCI according to the first aggregation level, it can be determined that the aggregation level corresponding to the DCI is the first aggregation level; or, if the terminal device detects the DCI according to the second aggregation level, it can be determined that the aggregation level corresponding to the DCI is the second aggregation level. In the above process, whether to provide feedback to the HARQ process can be determined by the aggregation level corresponding to the DCI, without adding indication information in the DCI, which not only saves signaling overhead but also makes the reliability of PDCCH detection higher.

[0219] Optionally, the above detection may be a blind detection. For ease of description, the following description will be made by taking the blind detection as an example.

[0220] In actual applications, if a terminal device uses the first aggregation level and the second aggregation level for blind detection, the terminal device may perform more blind detections. To reduce the number of blind detections performed by the terminal device, the terminal device may determine the aggregation level used for blind detection based on the configuration of its HARQ process by the network device.

[0221] For example, if all HARQ processes in the terminal device are configured as type 1, the aggregation level used by the terminal device for PDCCH detection includes aggregation level 1. In this case, the terminal device may not use the second aggregation level for blind detection, so that the terminal device performs fewer blind detections.

[0222] For example, if all HARQ processes in the terminal device are configured as the second type, the aggregation level used by the terminal device for PDCCH detection includes the second aggregation level. In this case, the terminal device may not use the first aggregation level for blind detection, so that the terminal device performs fewer blind detections.

[0223] For example, if some HARQ processes in the terminal device are configured as the first type and some HARQ processes are configured as the second type, the aggregation levels used by the terminal device for PDCCH detection include the first aggregation level and the second aggregation level.

[0224] To reduce false alarms from blind DCI detection, after a terminal device detects DCI at one aggregation level, it can further determine whether the type of HARQ process corresponding to the DCI is consistent with the type of HARQ process corresponding to that aggregation level. If they are consistent, it determines whether to provide feedback for the HARQ process. If they are inconsistent, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.

[0225] For example, if the terminal device detects the DCI through the first aggregation level, the terminal device can determine that the type of the HARQ process indicated by the DCI is the first type according to the first aggregation level. The terminal device can further confirm whether the type of the HARQ process is the first type according to other methods. If the terminal device confirms that the type of the HARQ process is also the first type according to other methods, the terminal device can determine not to provide feedback for the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the second type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0226] For example, if the terminal device detects the DCI through the second aggregation level, the terminal device can determine that the type of the HARQ process indicated by the DCI is the second type according to the second aggregation level. The terminal device can further confirm whether the type of the HARQ process is the second type according to other methods. If the terminal device confirms that the type of the HARQ process is also the second type according to other methods, the terminal device can determine to provide feedback on the HARQ process, thereby reducing false alarms of DCI blind detection. If the terminal device determines that the type of the HARQ process is the first type according to other methods, the terminal device can ignore the scheduling of the DCI, or the terminal device can not receive the PDSCH scheduled by the DCI.

[0227] In the above two examples, other methods may be: the terminal device determines the type of the HARQ process through the type of the HARQ process pre-configured by the network device; or the terminal device may determine the type of the HARQ process through Figure 5-Figure 7 The type of HARQ process is determined in any manner in the embodiments.

[0228] exist Figure 8 In the illustrated embodiment, a terminal device determines whether to provide feedback for the HARQ process indicated by the DCI based on the aggregation level corresponding to the DCI. If the terminal device determines not to provide feedback for the HARQ process indicated by the DCI, the terminal device does not need to provide feedback for that HARQ process, and the network device can transmit other data through that HARQ process without waiting for feedback from the terminal device, thereby improving data transmission efficiency. Furthermore, the aggregation level corresponding to the DCI implicitly indicates the type of HARQ process, eliminating the need for additional signaling in the DCI and saving signaling overhead.

[0229] On the basis of any one of the above embodiments, after the terminal device receives the DCI sent by the network device, if the DCI indicates feedback on the HARQ process indicated by the DCI, the DCI includes a single HARQ-ACK feedback request. Optionally, when the single HARQ-ACK feedback request is triggered, the terminal device sends feedback information corresponding to the HARQ process in the terminal device to the network device, that is, the HARQ feedback codebook may include HARQ-ACK feedback information corresponding to the first type and the second type of HARQ processes. Alternatively, when the single HARQ-ACK feedback request is not triggered, the terminal device does not send the HARQ-ACK feedback information corresponding to the first type of HARQ process to the network device, that is, the uplink HARQ feedback codebook does not include the HARQ-ACK feedback information corresponding to the first type of HARQ process.

[0230] Based on any of the above embodiments, more parallel HARQ processes can be configured for the terminal device, thereby improving the communication efficiency between the terminal device and the network device. For example, in an NTN system, if 16 HARQ processes are currently typically configured for a terminal device, in this application, the number of HARQ processes configured for the terminal device can be greater than 16.

[0231] Based on any of the above embodiments, a terminal device receives a DCI sent by a network device, where the DCI is used to indicate the release of semi-persistent scheduling (SPS), and the terminal device determines whether to provide feedback on the DCI based on the DCI. It should be noted that the manner in which the terminal device determines whether to provide feedback on the DCI is the same as the manner in which the terminal device determines whether to provide feedback on the HARQ indicated by the DCI in the above embodiments, and will not be further described herein.

[0232] Optionally, during the uplink process, the network device may schedule the terminal device to perform uplink transmission. For example, the network device may schedule the terminal device to perform uplink transmission via a HARQ process. When the network device schedules the terminal device to perform uplink transmission via a first HARQ process, the terminal device may determine whether to transmit uplink data to the network device via the first HARQ process based on the type of the first HARQ process.

[0233] Optionally, when the network device schedules the terminal device to perform uplink transmission through the first HARQ process, the terminal device may first determine whether the terminal device has transmitted uplink data through the first HARQ process within a preset time length before the current moment. If the terminal device has not transmitted uplink data through the first HARQ process within the preset time length before the current moment, the terminal device sends uplink data to the network device through the first HARQ process. If the terminal device transmits uplink data through the first HARQ process within the preset time length before the current moment, the terminal device determines whether to transmit uplink data to the network device through the first HARQ process based on the type of the first HARQ process. Optionally, if the type of the first HARQ process is the first type, the terminal device transmits uplink data to the network device through the first HARQ process; if the type of the first HARQ process is the second type, the terminal device may ignore the scheduling of the network device, that is, the terminal device does not send uplink data to the network device through the first HARQ process.

[0234] In the above process, when the network device schedules the terminal device to transmit uplink data through the first type of HARQ process, the network device can continuously schedule the terminal device to transmit uplink data through the first type of HARQ process. After the terminal device transmits the uplink data through the first type of HARQ process, the terminal device does not need to wait for a preset period of time, and the terminal device can perform uplink data transmission through the first type of HARQ process again, thereby improving the data transmission efficiency between the terminal device and the network device.

[0235] Figure 9 This is a schematic diagram of the structure of a data transmission device provided in an embodiment of the present application. The data transmission device 10 can be set in a terminal device. Figure 9 The data transmission device 10 may include a receiving module 11 and a processing module 12, wherein:

[0236] The receiving module 11 is used to receive downlink control information DCI sent by the network device;

[0237] The processing module 12 is configured to determine, according to the DCI, whether to provide feedback for a hybrid automatic repeat request HARQ process indicated by the DCI.

[0238] The data transmission device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0239] In a possible implementation, the processing module 12 is specifically configured to:

[0240] Determine whether to provide feedback for the HARQ process indicated by the DCI according to the first information of the DCI.

[0241] In a possible implementation manner, the first information includes at least one of the following information:

[0242] The length of the DCI;

[0243] A wireless network equipment temporary identifier RNTI corresponding to the DCI;

[0244] The search space corresponding to the DCI;

[0245] The aggregation level corresponding to the DCI.

[0246] In a possible implementation, the processing module 12 is specifically configured to:

[0247] Determining, according to the DCI, a type of the HARQ process, where the type of the HARQ process is a first type or a second type, where the first type of HARQ process is a HARQ process for which a terminal device does not perform feedback, and the second type of HARQ process is a HARQ process for which a terminal device performs feedback;

[0248] Determine whether to provide feedback for the HARQ process indicated by the DCI according to the type of the HARQ process.

[0249] In a possible implementation, the processing module 12 is specifically configured to:

[0250] If the type of the HARQ process is the first type, no feedback is provided for the HARQ process indicated by the DCI;

[0251] If the type of the HARQ process is the second type, feedback is provided for the HARQ process indicated by the DCI.

[0252] In a possible implementation manner, the first information is the length of the DCI; and the processing module is specifically configured to:

[0253] If the length of the DCI is the first DCI length, determining not to provide feedback for the HARQ process; or

[0254] If the length of the DCI is the second DCI length, it is determined to provide feedback to the HARQ process.

[0255] In a possible implementation, the first DCI length is smaller than the second DCI length.

[0256] In a possible implementation manner, if the DCI is detected according to the first DCI length, the length of the DCI is the first DCI length; or,

[0257] If the DCI is detected according to the second DCI length, the length of the DCI is the second DCI length.

[0258] In one possible implementation, the first DCI length corresponds to a first aggregation level;

[0259] The second DCI length corresponds to a second aggregation level.

[0260] In a possible implementation manner, the first aggregation level is less than or equal to the second aggregation level.

[0261] In a possible implementation manner, the length of the DCI is a first DCI length; and the DCI does not include at least one of the following information fields:

[0262] TPC command of the physical uplink control channel PUCCH;

[0263] Downlink allocation indication DAI;

[0264] PUCCH resource indication;

[0265] Timing indication from physical downlink shared channel PDSCH to HARQ feedback;

[0266] Single HARQ-ACK feedback request;

[0267] PDSCH group indication;

[0268] New Feedback Indicator NFI;

[0269] Trigger feedback group indication.

[0270] In a possible implementation manner, the length of the DCI is a second DCI length; and the DCI includes at least one of the following information fields:

[0271] TPC command for PUCCH;

[0272] DAI;

[0273] PUCCH resource indication;

[0274] Timing indication from PDSCH to HARQ feedback;

[0275] Single HARQ-ACK feedback request;

[0276] PDSCH group indication;

[0277] NFI;

[0278] Trigger feedback group indication.

[0279] In a possible implementation, the HARQ process in the terminal device is configured as a first type, and the DCI length used by the terminal device for PDCCH detection includes the first DCI length.

[0280] In a possible implementation, the HARQ process in the terminal device is configured as the second type, and the DCI length used by the terminal device for PDCCH detection includes the second DCI length.

[0281] In a possible implementation, some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the DCI length used by the terminal device for PDCCH detection includes the first DCI length and the second DCI length.

[0282] In a possible implementation manner, the first information is the RNTI corresponding to the DCI; and the processing module 12 is specifically configured to:

[0283] If the RNTI corresponding to the DCI is the first RNTI, determining not to provide feedback for the HARQ process; or

[0284] If the RNTI corresponding to the DCI is the second RNTI, it is determined to provide feedback to the HARQ process.

[0285] In a possible implementation manner, if the DCI is detected according to the first RNTI, the RNTI corresponding to the DCI is the first RNTI; or,

[0286] If the DCI is detected according to the second RNTI, the RNTI corresponding to the DCI is the second RNTI.

[0287] In a possible implementation, the HARQ process in the terminal device is configured as a first type, and the RNTI used by the terminal device for PDCCH detection includes the first RNTI.

[0288] In a possible implementation, the HARQ process in the terminal device is configured as the second type, and the RNTI used by the terminal device for PDCCH detection includes the second RNTI.

[0289] In a possible implementation, some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the RNTI used by the terminal device for PDCCH detection includes the first RNTI and the second RNTI.

[0290] In a possible implementation manner, the first information is a search space corresponding to the DCI; and the processing module is specifically configured to:

[0291] If the search space corresponding to the DCI is the first search space, determining not to provide feedback for the HARQ process; or

[0292] If the search space corresponding to the DCI is the second search space, it is determined to provide feedback to the HARQ process.

[0293] In a possible implementation manner, if the DCI is detected in the first search space, the search space corresponding to the DCI is the first search space; or,

[0294] If the DCI is detected in the second search space, the search space corresponding to the DCI is the second search space.

[0295] In a possible implementation, the HARQ process in the terminal device is configured as a first type, and the search space for the terminal device to perform PDCCH detection includes the first search space.

[0296] In a possible implementation, the HARQ process in the terminal device is configured as the second type, and the search space for the terminal device to perform PDCCH detection includes the second search space.

[0297] In a possible implementation, some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the search space for PDCCH detection by the terminal device includes the first search space and the second search space.

[0298] In a possible implementation manner, the first information is the aggregation level corresponding to the DCI; and the processing module 12 is specifically configured to:

[0299] If the aggregation level corresponding to the DCI is the first aggregation level, determining not to provide feedback for the HARQ process; or

[0300] If the aggregation level corresponding to the DCI is the second aggregation level, it is determined to provide feedback to the HARQ process.

[0301] In a possible implementation manner, if the DCI is detected according to the first aggregation level, the aggregation level corresponding to the DCI is the first aggregation level; or,

[0302] If the DCI is detected according to the second aggregation level, the aggregation level corresponding to the DCI is the second aggregation level.

[0303] In a possible implementation, the HARQ process in the terminal device is configured as a first type, and the aggregation level for the terminal device to perform PDCCH detection includes the first aggregation level.

[0304] In a possible implementation, the HARQ process in the terminal device is configured as the second type, and the aggregation level for the terminal device to perform PDCCH detection includes the second aggregation level.

[0305] In a possible implementation, some HARQ processes in the terminal device are configured as the first type, and some HARQ processes are configured as the second type, and the aggregation level for the terminal device to perform PDCCH detection includes the first aggregation level and the second aggregation level.

[0306] In a possible implementation, the receiving module 11 is further configured to:

[0307] Receive second information sent by the network device, where the second information is used to configure the type of at least one HARQ process in the terminal device.

[0308] In one possible implementation, the second information includes at least one of the following information:

[0309] Radio Resource Control (RRC) signaling;

[0310] DCI;

[0311] Medium Access Control MAC Control Unit CE.

[0312] In a possible implementation, the processing module 12 is specifically configured to:

[0313] When the type of the HARQ process determined by the processing module according to the DCI is the same as the type of the HARQ process indicated by the second information, the following steps are performed: determining according to the DCI whether to provide feedback for the hybrid automatic repeat request HARQ process indicated by the DCI.

[0314] In a possible implementation, the processing module 12 is further configured to:

[0315] When the type of the HARQ process determined by the processing module according to the DCI is different from the type of the HARQ process indicated by the second information, the DCI is discarded or the PDSCH corresponding to the DCI is not received.

[0316] In a possible implementation, the DCI indicates feedback on the HARQ process indicated by the DCI, and the DCI includes a single HARQ-ACK feedback request.

[0317] Figure 10 This is a schematic diagram of the structure of another data transmission device provided in an embodiment of the present application. Figure 9 Based on the example shown. Figure 10 , the data transmission device 10 further includes a sending module 13, wherein,

[0318] The sending module 13 is used to send feedback information corresponding to the HARQ process in the terminal device to the network device when the single HARQ-ACK feedback request is triggered.

[0319] The data transmission device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0320] Figure 11 This is a structural diagram of another data transmission device provided in an embodiment of the present application. The data transmission device 20 can be set in a network device. Figure 11 The data transmission device 20 may include: a processing module 21 and a sending module 22, wherein:

[0321] The processing module 21 is used to determine the downlink control information DCI of the terminal device;

[0322] The sending module 22 is configured to send the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to provide feedback on a hybrid automatic repeat request HARQ process indicated by the DCI.

[0323] The data transmission device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0324] In a possible implementation, the processing module 21 is specifically configured to:

[0325] Determining the DCI according to the type of the HARQ process;

[0326] The type of the HARQ process is a first type or a second type, the first type of HARQ process is a HARQ process in which the terminal device does not perform feedback, and the second type of HARQ process is a HARQ process in which the terminal device performs feedback.

[0327] In a possible implementation, the processing module 21 is specifically configured to:

[0328] The first information of the DCI is determined according to the type of the HARQ process.

[0329] In a possible implementation manner, the first information includes at least one of the following information:

[0330] The length of the DCI;

[0331] A wireless network equipment temporary identifier RNTI corresponding to the DCI;

[0332] The search space corresponding to the DCI;

[0333] The aggregation level corresponding to the DCI.

[0334] In a possible implementation manner, the first information is the length of the DCI; and the processing module 21 is specifically configured to:

[0335] If the type of the HARQ process is the first type, determining the length of the DCI to be a first DCI length; or,

[0336] If the type of the HARQ process is the second type, determine that the length of the DCI is the first DCI length.

[0337] In a possible implementation, the first DCI length is smaller than the second DCI length.

[0338] In a possible implementation manner, the length of the DCI is a first DCI length; and the DCI does not include at least one of the following information fields:

[0339] TPC command of the physical uplink control channel PUCCH;

[0340] Downlink allocation indication DAI;

[0341] Physical uplink control channel PUCCH resource indication;

[0342] Timing indication from physical downlink shared channel PDSCH to HARQ feedback;

[0343] Single HARQ-ACK feedback request;

[0344] PDSCH group indication;

[0345] New Feedback Indicator NFI;

[0346] Trigger feedback group indication.

[0347] In a possible implementation manner, the length of the DCI is a second DCI length; and the DCI includes at least one of the following information fields:

[0348] TPC command for PUCCH;

[0349] DAI;

[0350] PUCCH resource indication;

[0351] Timing indication from PDSCH to HARQ feedback;

[0352] Single HARQ-ACK feedback request;

[0353] PDSCH group indication;

[0354] NFI;

[0355] Trigger feedback group indication.

[0356] In a possible implementation manner, the first information is the RNTI corresponding to the DCI; and the processing module 21 is specifically configured to:

[0357] The type of the HARQ process is the first type, and the RNTI corresponding to the DCI is determined to be the first RNTI; or

[0358] The type of the HARQ process is the second type, and the RNTI corresponding to the DCI is determined to be the second RNTI.

[0359] In a possible implementation manner, the first information is a search space corresponding to the DCI; and the processing module 21 is specifically configured to:

[0360] The type of the HARQ process is the first type, and the search space corresponding to the DCI is determined to be the first search space; or,

[0361] The type of the HARQ process is the second type, and the search space corresponding to the DCI is determined to be the second search space.

[0362] In a possible implementation manner, the first information is the aggregation level corresponding to the DCI; and the processing module 21 is specifically configured to:

[0363] The type of the HARQ process is the first type, and the network device determines that the aggregation level corresponding to the DCI is the first aggregation level; or

[0364] The type of the HARQ process is the second type, and the network device determines that the aggregation level corresponding to the DCI is the second aggregation level.

[0365] The data transmission device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0366] Figure 12 This is a schematic diagram of the structure of the terminal device provided in the embodiment of this application. Figure 12 Terminal device 30 may include a transceiver 31, a memory 32, and a processor 33. Transceiver 31 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter, transmission port, transmission interface, or similar descriptions. The receiver may also be referred to as a receiver, receiver, reception port, reception interface, or similar descriptions. For example, transceiver 31, memory 32, and processor 33 are interconnected via a bus 34.

[0367] The memory 32 is used to store program instructions;

[0368] The processor 33 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 30 to execute any of the above-mentioned data transmission methods.

[0369] The receiver of the transceiver 31 can be used to perform the receiving function of the terminal device in the above-mentioned data transmission method. The transmitter of the transceiver 31 can be used to perform the sending function of the terminal device in the above-mentioned data transmission method.

[0370] The terminal device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment. Its implementation principles and beneficial effects are similar and will not be repeated here.

[0371] Figure 13 This is a schematic diagram of the structure of the network device provided in the embodiment of this application. Figure 13 Network device 40 may include a transceiver 41, a memory 42, and a processor 43. Transceiver 41 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, a transmitter, a transmission port, a transmission interface, or similar descriptions. The receiver may also be referred to as a receiver, a receiver, a reception port, a reception interface, or similar descriptions. For example, transceiver 41, memory 42, and processor 43 are interconnected via a bus 44.

[0372] The memory 42 is used to store program instructions;

[0373] The processor 43 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 30 to execute any of the above-mentioned data transmission methods.

[0374] The transmitter of the transceiver 41 can be used to perform the sending function of the network device in the above-mentioned data transmission method.

[0375] The network device provided in the embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principles and beneficial effects are similar, so they will not be repeated here.

[0376] The present embodiment provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the above-mentioned data transmission method. The implementation principles and beneficial effects thereof are similar and will not be further described here.

[0377] The present application also provides a computer program product that can be executed by a processor. When the computer program product is executed, it can implement the data transmission method performed by any of the terminal devices shown above. The implementation principles and beneficial effects are similar and will not be further described here.

[0378] An embodiment of the present application provides a system on a chip or a system chip, which can be applied to a terminal device. The system on a chip or the system chip includes: at least one communication interface, at least one processor, and at least one memory. The communication interface, memory, and processor are interconnected through a bus. The processor executes instructions stored in the memory, so that the base station can execute the above-mentioned data transmission method.

[0379] An embodiment of the present application provides a system on chip or a system chip, which can be applied to network equipment. The system on chip or the system chip includes: at least one communication interface, at least one processor, and at least one memory. The communication interface, memory, and processor are interconnected through a bus. The processor executes instructions stored in the memory, so that the base station can execute the above-mentioned data transmission method.

[0380] All or part of the steps of the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-mentioned method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), random access memory (RAM), flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disc, and any combination thereof.

[0381] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0382] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0383] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0384] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

[0385] In this application, the term "include" and its variations may refer to non-restrictive inclusion; the term "or" and its variations may refer to "and / or". The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. In this application, "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship.

Claims

1. A data transmission method, characterized in that: include: The terminal device receives downlink control information DCI sent by the network device; The terminal device determines, according to the DCI, whether to provide feedback for the hybrid automatic repeat request HARQ process indicated by the DCI, The terminal device determining, according to the DCI, whether to provide feedback on the HARQ process indicated by the DCI includes: the terminal device determining, according to the first information of the DCI, whether to provide feedback on the HARQ process indicated by the DCI; The first information of the DCI includes the length of the DCI, and the terminal device determines, based on the first information of the DCI, whether to provide feedback for the HARQ process indicated by the DCI, including: if the length of the DCI is a first DCI length, determining, by the terminal device, not to provide feedback for the HARQ process; if the length of the DCI is a second DCI length, determining, by the terminal device, to provide feedback for the HARQ process; The first DCI length is smaller than the second DCI length; If the length of the DCI is the first DCI length, the DCI does not include the following information fields: a transmit power control TPC command of a physical uplink control channel PUCCH; a downlink allocation indication DAI; a PUCCH resource indication; a timing indication from a physical downlink shared channel PDSCH to HARQ feedback; The type of the HARQ process is a first type or a second type, the first type of HARQ process is a HARQ process for which the terminal device does not perform feedback, and the second type of HARQ process is a HARQ process for which the terminal device performs feedback; Part of the HARQ processes in the terminal device are configured as the first type, and part of the HARQ processes are configured as the second type.

2. The method according to claim 1, characterized in that The first information further includes at least one of the following information: A wireless network equipment temporary identifier RNTI corresponding to the DCI; The search space corresponding to the DCI; The aggregation level corresponding to the DCI.

3. The method according to claim 1, characterized in that If the DCI is detected according to the first DCI length, the length of the DCI is the first DCI length; or, If the DCI is detected according to the second DCI length, the length of the DCI is the second DCI length.

4. The method according to claim 1, wherein The first DCI length corresponds to a first aggregation level; The second DCI length corresponds to a second aggregation level.

5. The method according to claim 4, characterized in that The first aggregation level is less than or equal to the second aggregation level.

6. The method according to claim 1, characterized in that If the length of the DCI is the first DCI length, the DCI does not include one or more of the following information fields: Single HARQ-ACK feedback request; PDSCH group indication; New Feedback Indicator NFI; Trigger feedback group indication.

7. The method according to claim 1, characterized in that If the length of the DCI is the second DCI length, the DCI includes one or more of the following information fields: TPC command for PUCCH; DAI; PUCCH resource indication; Timing indication from PDSCH to HARQ feedback; Single HARQ-ACK feedback request; PDSCH group indication; NFI; Trigger feedback group indication.

8. The method according to claim 1, characterized in that The DCI length used by the terminal device for PDCCH detection includes the first DCI length and the second DCI length.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The terminal device receives second information sent by the network device, where the second information is used to configure the type of at least one HARQ process in the terminal device.

10. The method according to claim 9, characterized in that The second information includes at least one of the following information: Radio Resource Control (RRC) signaling; DCI; Medium Access Control MAC Control Unit CE.

11. The method according to claim 9, characterized in that The terminal device determines, according to the DCI, whether to provide feedback for a hybrid automatic repeat request HARQ process indicated by the DCI, including: When the type of the HARQ process determined by the terminal device according to the DCI is the same as the type of the HARQ process indicated by the second information, the terminal device performs the following steps: Determine, according to the DCI, whether to provide feedback for the HARQ process indicated by the DCI.

12. The method according to claim 9, characterized in that The method further comprises: When the type of the HARQ process determined by the terminal device according to the DCI is different from the type of the HARQ process indicated by the second information, the terminal device discards the DCI or does not receive the PDSCH corresponding to the DCI.

13. The method according to any one of claims 1 to 8, characterized in that The DCI indicates feedback on the HARQ process indicated by the DCI, and the DCI includes a single HARQ-ACK feedback request.

14. The method according to claim 13, characterized in that The method further comprises: When the single HARQ-ACK feedback request is triggered, the terminal device sends feedback information corresponding to the HARQ process in the terminal device to the network device.

15. A data transmission method, characterized in that: include: The network device determines the downlink control information DCI of the terminal device; The network device sends the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to provide feedback on a hybrid automatic repeat request HARQ process indicated by the DCI. The network device determining the DCI of the terminal device includes: the network device determining the DCI according to the type of the HARQ process; The type of the HARQ process is a first type or a second type, the first type of HARQ process is a HARQ process for which the terminal device does not perform feedback, and the second type of HARQ process is a HARQ process for which the terminal device performs feedback; Part of the HARQ processes in the terminal device are configured as the first type, and part of the HARQ processes are configured as the second type; The network device determining the DCI according to the type of the HARQ process includes: the network device determining first information of the DCI according to the type of the HARQ process; The first information of the DCI includes the length of the DCI, and the network device determines the first information of the DCI according to the type of the HARQ process, including: if the type of the HARQ process is the first type, the network device determines the length of the DCI to be a first DCI length; if the type of the HARQ process is the second type, the network device determines the length of the DCI to be a second DCI length; The first DCI length is smaller than the second DCI length; Among them, if the length of the DCI is the first DCI length, the DCI does not include the following information fields: transmit power control TPC command of the physical uplink control channel PUCCH; downlink allocation indication DAI; PUCCH resource indication; timing indication of physical downlink shared channel PDSCH to HARQ feedback.

16. The method according to claim 15, characterized in that The first information further includes at least one of the following information: A wireless network equipment temporary identifier RNTI corresponding to the DCI; The search space corresponding to the DCI; The aggregation level corresponding to the DCI.

17. The method according to claim 15, characterized in that If the length of the DCI is the first DCI length, the DCI does not include at least one of the following information fields: Single HARQ-ACK feedback request; PDSCH group indication; New Feedback Indicator NFI; Trigger feedback group indication.

18. The method according to claim 15, characterized in that If the length of the DCI is the second DCI length, the DCI includes at least one of the following information fields: TPC command for PUCCH; DAI; PUCCH resource indication; PDSCH to HARQ feedback timing indication; Single HARQ-ACK feedback request; PDSCH group indication; NFI; Trigger feedback group indication.

19. A data transmission device, characterized in that: It includes a receiving module and a processing module, wherein: The receiving module is used to receive downlink control information DCI sent by the network device; The processing module is configured to determine, according to the DCI, whether to provide feedback for a hybrid automatic repeat request HARQ process indicated by the DCI; The processing module is specifically configured to: determine, based on the first information of the DCI, whether to provide feedback for the HARQ process indicated by the DCI; The first information of the DCI includes the length of the DCI, and the processing module is specifically configured to: if the length of the DCI is the first DCI length, determine not to provide feedback to the HARQ process; if the length of the DCI is the second DCI length, determine to provide feedback to the HARQ process; The first DCI length is smaller than the second DCI length; If the length of the DCI is the first DCI length, the DCI does not include the following information fields: a transmit power control TPC command of a physical uplink control channel PUCCH; a downlink allocation indication DAI; a PUCCH resource indication; a timing indication from a physical downlink shared channel PDSCH to HARQ feedback; The type of the HARQ process is a first type or a second type, the first type of HARQ process is a HARQ process for which the terminal device does not perform feedback, and the second type of HARQ process is a HARQ process for which the terminal device performs feedback; Part of the HARQ processes of the terminal device are configured as the first type, and part of the HARQ processes are configured as the second type.

20. The device according to claim 19, characterized in that The first information further includes at least one of the following information: A wireless network equipment temporary identifier RNTI corresponding to the DCI; The search space corresponding to the DCI; The aggregation level corresponding to the DCI.

21. The device according to claim 19, characterized in that If the DCI is detected according to the first DCI length, the length of the DCI is the first DCI length; or, If the DCI is detected according to the second DCI length, the length of the DCI is the second DCI length.

22. The device according to claim 19, characterized in that The first DCI length corresponds to a first aggregation level; The second DCI length corresponds to a second aggregation level.

23. The device according to claim 22, characterized in that The first aggregation level is less than or equal to the second aggregation level.

24. The device according to claim 19, characterized in that If the length of the DCI is the first DCI length, the DCI does not include one or more of the following information fields: Single HARQ-ACK feedback request; PDSCH group indication; New Feedback Indicator NFI; Trigger feedback group indication.

25. The device according to claim 19, characterized in that If the length of the DCI is the second DCI length, the DCI includes one or more of the following information fields: TPC command for PUCCH; DAI; PUCCH resource indication; Timing indication from PDSCH to HARQ feedback; Single HARQ-ACK feedback request; PDSCH group indication; NFI; Trigger feedback group indication.

26. The device according to claim 19, characterized in that The DCI length used by the terminal device for PDCCH detection includes the first DCI length and the second DCI length.

27. The device according to any one of claims 19 to 26, characterized in that The receiving module is further configured to: Receive second information sent by the network device, where the second information is used to configure the type of at least one HARQ process in the terminal device.

28. The device according to claim 27, characterized in that The second information includes at least one of the following information: Radio Resource Control (RRC) signaling; DCI; Medium Access Control MAC Control Unit CE.

29. The device according to claim 27, characterized in that The processing module is specifically used for: When the type of the HARQ process determined by the processing module according to the DCI is the same as the type of the HARQ process indicated by the second information, the following steps are performed: determining according to the DCI whether to provide feedback for the hybrid automatic repeat request HARQ process indicated by the DCI.

30. The device according to claim 27, characterized in that The processing module is further configured to: When the type of the HARQ process determined by the processing module according to the DCI is different from the type of the HARQ process indicated by the second information, the DCI is discarded or the PDSCH corresponding to the DCI is not received.

31. The device according to any one of claims 19 to 26, characterized in that The DCI indicates feedback on the HARQ process indicated by the DCI, and the DCI includes a single HARQ-ACK feedback request.

32. A data transmission device, characterized in that: include: Processing module and sending module, wherein, The processing module is used to determine the downlink control information DCI of the terminal device; The sending module is used to send the DCI to the terminal device, where the DCI is used by the terminal device to determine whether to provide feedback on the hybrid automatic repeat request HARQ process indicated by the DCI; The processing module is specifically configured to: determine the DCI according to the type of the HARQ process; The type of the HARQ process is a first type or a second type, the first type of HARQ process is a HARQ process for which the terminal device does not perform feedback, and the second type of HARQ process is a HARQ process for which the terminal device performs feedback; Part of the HARQ processes in the terminal device are configured as the first type, and part of the HARQ processes are configured as the second type; The processing module is specifically configured to: determine the first information of the DCI according to the type of the HARQ process; The first information of the DCI includes the length of the DCI, and the processing module is specifically configured to: if the type of the HARQ process is the first type, determine that the length of the DCI is a first DCI length; if the type of the HARQ process is the second type, determine that the length of the DCI is a second DCI length; The first DCI length is smaller than the second DCI length; If the length of the DCI is the first DCI length, the DCI does not include the following information fields: Transmit power control (TPC) command for the physical uplink control channel (PUCCH); downlink allocation indication (DAI); PUCCH resource indication; and timing indication from the physical downlink shared channel (PDSCH) to HARQ feedback.

33. The device according to claim 32, characterized in that The first information further includes at least one of the following information: A wireless network equipment temporary identifier RNTI corresponding to the DCI; The search space corresponding to the DCI; The aggregation level corresponding to the DCI.

34. The device according to claim 32, characterized in that If the length of the DCI is the first DCI length, the DCI does not include at least one of the following information fields: Single HARQ-ACK feedback request; PDSCH group indication; New Feedback Indicator NFI; Trigger feedback group indication.

35. The device according to claim 32, characterized in that If the length of the DCI is the second DCI length, the DCI includes at least one of the following information fields: TPC command for PUCCH; DAI; PUCCH resource indication; PDSCH to HARQ feedback timing indication; Single HARQ-ACK feedback request; PDSCH group indication; NFI; Trigger feedback group indication.

36. A terminal device, characterized in that: include: transceivers, processors, and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the data transmission method according to any one of claims 1 to 14.

37. A network device, characterized in that: include: transceivers, processors, and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the data transmission method according to any one of claims 15 to 18.

38. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the data transmission method according to any one of claims 1 to 14, or the data transmission method according to any one of claims 15 to 18.

Images