Wireless communication method and terminal equipment

Abstract

A wireless communication method and a terminal device, the method comprising: a terminal device receiving a physical downlink control channel (PDCCH), the PDCCH being used for scheduling transmission of a plurality of transport blocks (TBs), the plurality of TBs being transmitted using a plurality of hybrid automatic request retransmission (HARQ) processes, the plurality of HARQ processes comprise at least one first type of HARQ process and at least one second type of HARQ process, the first type of HARQ process is configured to be in an enabled downlink HARQ feedback mode, and the second type of HARQ process is configured to be in an enabled downlink HARQ feedback mode; and starting or restarting a discontinuous reception (DRX) inactive timer and / or a DRX retransmission timer corresponding to the at least one first type of HARQ process according to the time for completing HARQ feedback on the plurality of TBs.

Description

Wireless communication method and terminal device Technical Field

[0001] The embodiments of the present application relate to the field of communications, and specifically to a method and terminal device for wireless communication. Background Art

[0002] In some scenarios, the concept of discontinuous reception (DRX) is proposed to save power for terminals. If DRX is configured for a terminal device, the terminal device needs to monitor the PDCCH during the DRX active time. The terminal device is in the active time while the DRX inactivity timer (drx-InactivityTimer) is running.

[0003] In the NTN system, the introduction of disabling hybrid automatic repeat request (HARQ) feedback is considered, that is, the network device can configure the HARQ process to disable HARQ feedback or enable HARQ feedback. If a PDCCH schedules the transmission of multiple transport blocks (TBs), the network device can configure the HARQ processes used by some of the multiple TBs to enable HARQ feedback mode, and at the same time configure the HARQ processes used by other TBs in the multiple TBs to disable HARQ feedback mode. In this case, how the terminal device starts or restarts the drx-InactivityTimer to select the appropriate time to monitor the PDCCH is an urgent problem that needs to be solved.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a method and terminal device for wireless communication, which facilitate the terminal device to select an appropriate time to monitor the PDCCH.

[0006] In a first aspect, a method for wireless communication is provided, including: a terminal device receives a physical downlink control channel PDCCH, the PDCCH is used to schedule the transmission of multiple transport blocks TB, wherein the multiple TBs are transmitted using multiple hybrid automatic repeat request HARQ processes, wherein the multiple HARQ processes include at least one first type HARQ process and at least one second type HARQ process, wherein the first type HARQ process is configured to disable a downlink HARQ feedback mode, and the second type HARQ process is configured to enable a downlink HARQ feedback mode; and according to the time when HARQ feedback is completed for the multiple TBs, starting or restarting a discontinuous reception DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first type HARQ process.

[0007] In a second aspect, a terminal device is provided, configured to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the terminal device includes a unit configured to execute the method in the first aspect or any possible implementation of the first aspect.

[0008] In a third aspect, a terminal device is provided, comprising: a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of the first aspect or its implementations.

[0009] In a fourth aspect, a chip is provided for implementing the method in the above-mentioned first aspect or its various implementations.

[0010] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in the above-mentioned first aspect or its various implementations.

[0011] In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method in the above-mentioned first aspect or its various implementations.

[0012] In a sixth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in the above-mentioned first aspect or its various implementations.

[0013] In a seventh aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in the above-mentioned first aspect or its various implementations.

[0014] Based on the above technical solution, for the transmission of multiple TBs scheduled by a PDCCH, when the HARQ process used by some of the multiple TBs is configured as the disabled DL HARQ feedback mode, and the HARQ process used by other TBs is configured as the enabled DL HARQ feedback mode, the terminal device can start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured as the disabled DL HARQ feedback mode according to the time of completing the HARQ feedback for the multiple TBs, that is, determine the PDCCH monitoring timing, which is conducive to avoiding resource waste caused by the terminal device monitoring the PDCCH before completing the HARQ feedback for the multiple TBs. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] 1 to 3 are schematic diagrams of application scenarios provided by embodiments of the present application.

[0016] Figures 4 and 5 are network architecture diagrams of NTN based on transparent data satellites and regenerative data satellites, respectively.

[0017] FIG6 is a schematic diagram of a wireless communication method provided in an embodiment of the present application.

[0018] FIG7 is a schematic diagram of a wireless communication method according to an embodiment of the present application.

[0019] FIG8 is a schematic diagram of a wireless communication method according to another embodiment of the present application.

[0020] FIG9 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0021] FIG10 is a schematic block diagram of a communication device provided in another embodiment of the present application.

[0022] FIG11 is a schematic block diagram of a chip provided in an embodiment of the present application.

[0023] FIG12 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0025] 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), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0026] 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), 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.

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

[0028] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0029] The embodiments of the present application can be applied to non-terrestrial networks (NTN) systems, and can also be applied to terrestrial networks (TN) systems.

[0030] As an example, NTN systems include, but are not limited to, New Radio NTN (NR-NTN) systems and Internet of Things NTN (IoT-NTN) systems. IoT-NTN systems can include Narrow Band Internet of Things over NTN (NB-IoT-NTN) systems and Enhanced Machine Type Communication over NTN (eMTC-NTN) systems.

[0031] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0032] The terminal device can be a station (STATION, 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 capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0033] 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.).

[0034] 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 device in industrial control, a wireless terminal device 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, or a wireless terminal device in smart home, etc. The terminal device involved in the embodiments of the present application may also be referred to as a terminal, user equipment (UE), access terminal device, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal device, mobile device, UE terminal device, wireless communication device, UE agent or UE device, etc. The terminal device may also be fixed or mobile.

[0035] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called 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.

[0036] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0037] As an example and not a limitation, in an embodiment of the present application, a network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, 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. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.

[0038] In an embodiment of the present application, the network device can provide services for a cell, and the 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 can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a 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.

[0039] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located within the coverage area.

[0040] Figure 1 exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0041] For example, FIG2 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG2 , a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 can also be referred to as an NTN. In the architecture of the communication system shown in FIG2 , the satellite 1102 can have the function of a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. In the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1102 may be included in the communication system, and each network device 1102 may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0042] For example, FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG3 , it includes a terminal device 1201, a satellite 1202, and a base station 1203. Wireless communication can be performed between the terminal device 1201 and the satellite 1202, and communication can be performed between the satellite 1202 and the base station 1203. The network formed between the terminal device 1201, the satellite 1202, and the base station 1203 can also be referred to as an NTN. In the architecture of the communication system shown in FIG3 , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1203 may be included in the communication system, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0043] It should be noted that Figures 1 to 3 are only examples of the systems to which this application is applicable. Of course, the methods shown in the embodiments of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiments of this application do not make specific limitations on this.

[0044] In some embodiments of the present application, the wireless communication system shown in Figures 1-3 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but the embodiments of the present application are not limited to this.

[0045] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0046] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0047] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0048] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0049] In the embodiments of the present application, "pre-defined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

[0050] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0051] FIG4 and FIG5 show two NTN network architectures, wherein FIG4 is an NTN network architecture based on transparent forwarding, and FIG5 is an NTN network architecture based on regenerative forwarding.

[0052] The NTN network can include one or more gateways, which connect satellites to the terrestrial public network. For NTN networks based on transparent forwarding, communication between the gateway and satellite occurs via feeder links, while communication between the satellite and the terminal occurs via service links. For NTN networks based on regenerative forwarding, satellites communicate with each other via intersatellite links, while communication between the gateway and satellite occurs via feeder links, and communication between the satellite and the terminal occurs via service links.

[0053] In transparent forwarding, the satellite only provides the functions of wireless frequency filtering, frequency conversion and amplification. It only provides transparent forwarding of the signal and does not change the waveform signal it forwards.

[0054] In regenerative forwarding, the satellite not only provides wireless frequency filtering, frequency conversion and amplification functions, but also can provide demodulation / decoding, routing / conversion, encoding / modulation functions. It has some or all of the functions of a base station.

[0055] In some scenarios, in order to save power for the terminal, the concept of discontinuous reception (DRX) is proposed. Specifically, the network device can configure the terminal device to wake up (DRX ON) at a time predicted by the network and monitor the physical downlink control channel (PDCCH). At the same time, the network can also configure the terminal device to sleep (DRX OFF) at a time predicted by the network, that is, the terminal device does not need to monitor the PDCCH. Therefore, if the network device has data to transmit to the terminal device, the network device can schedule the terminal device during the time when the terminal device is in DRX ON, and during the DRC OFF time, the terminal power consumption can be reduced because the radio frequency is turned off.

[0056] In some scenarios, the network device can configure the DRX function for the terminal device so that the terminal device monitors the PDCCH discontinuously to save power. For example, each MAC entity can correspond to a DRX configuration. Optionally, the DRX configuration can include at least one of the following:

[0057] DRX onDuration Timer (drx-onDurationTimer): The duration of the terminal device waking up at the beginning of a DRX cycle.

[0058] DRX slot offset (drx-SlotOffset): The delay for the terminal device to start the drx-onDurationTimer.

[0059] DRX inactivity timer (drx-InactivityTimer): When the terminal device receives a PDCCH indicating an uplink initial transmission or a downlink initial transmission, the terminal device continues to monitor the PDCCH for a certain period of time.

[0060] DRX Downlink Retransmission Timer (drx-RetransmissionTimerDL): The maximum duration that a terminal device monitors the PDCCH indicating downlink retransmission scheduling. Each downlink Hybrid Automatic Repeat reQuest (HARQ) process, except the broadcast HARQ process, corresponds to one drx-RetransmissionTimerDL.

[0061] DRX Uplink Retransmission Timer (drx-RetransmissionTimerUL): The maximum duration that a terminal device monitors the PDCCH indicating uplink retransmission scheduling. Each uplink HARQ process corresponds to one drx-RetransmissionTimerUL.

[0062] Long DRX cycle start offset (longDRX-CycleStartOffset): used to configure the long DRX cycle, as well as the subframe offsets at which the long DRX cycle and the short DRX cycle start.

[0063] Short DRX cycle (drx-ShortCycle): Short DRX cycle, which is an optional configuration.

[0064] Short cycle timer (drx-ShortCycleTimer): The duration that the terminal device is in a short DRX cycle (and does not receive any PDCCH), which is an optional configuration.

[0065] Downlink Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) Timer (HARQ RTT Timer): The minimum waiting time a terminal device must wait to receive a PDCCH indicating downlink scheduling. Each downlink HARQ process, except the broadcast HARQ process, corresponds to one HARQ RTT Timer.

[0066] Short TTI DRX retransmission timer (drx-RetransmissionTimerShortTTI): When short TTI is configured, the length of the downlink retransmission timer.

[0067] Short TTI DRX uplink retransmission timer (drx-ULRetransmissionTimerShortTTI): When short TTI is configured, the duration of the uplink retransmission timer.

[0068] Uplink Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) Timer (UL HARQ RTT Timer): The minimum waiting time required for a terminal device to receive the PDCCH indicating uplink scheduling. Each uplink HARQ process corresponds to one UL HARQ RTT Timer.

[0069] If the terminal device is configured with DRX, the terminal device needs to monitor the PDCCH during the DRX active time. The DRX active time includes the following situations:

[0070] Any of the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerShortTTI, drx-RetransmissionTimerUL, drx-ULRetransmissionTimerShortTTI, and random access contention resolution timer (ra-ContentionResolutionTimer) is running;

[0071] The terminal device has sent a Scheduling Request (SR) on the PUCCH / Short PUCCH (SPUCCH) and is in a pending state;

[0072] In a contention-based random access procedure, the terminal device has not received an initial transmission indicated by a PDCCH scrambled by a cell radio network temporary identifier (Cell RNTI, C-RNTI) after successfully receiving a random access response;

[0073] A UL grant can be received for a pending HARQ retransmission, and the HARQ buffer of the asynchronous HARQ process has data;

[0074] A machine type of communication (MTC) PDCCH uplink HARQ-ACK feedback configuration (mpdcch-UL-HARQ-ACK-FeedbackConfig) is configured and repeated transmission within a bundling group is currently in progress.

[0075] In some scenarios, if the drx-InactivityTimer times out and / or the terminal device receives a DRX command media access control control element (DRX Command MAC CE), the terminal device uses a long DRX cycle.

[0076] In some scenarios, if the drx-ShortCycleTimer times out and / or the terminal device receives a long DRX command MAC CE, the terminal device uses a short DRX cycle.

[0077] In some scenarios, the terminal device can decide when to start the drx-onDurationTimer based on whether it is currently in a long DRX cycle or a short DRX cycle. For example, the specific provisions are as follows:

[0078] If a short DRX cycle is used, and the current subframe satisfies [(SFN×10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle).

[0079] If a long DRX cycle is used, and the current subframe satisfies [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset.

[0080] If the terminal device is a Narrow Band Internet of Things (NB-IoT) terminal, then:

[0081] If there is at least one HARQ RTT Timer corresponding to the HARQ process or the UL HARQ RTT Timer is not running, start the drx-onDurationTimer.

[0082] Otherwise, start drx-onDurationTimer.

[0083] Here, modulo represents the modulo operation.

[0084] In some scenarios, the conditions for the terminal device to start or restart the HARQ RTT Timer are:

[0085] If the terminal device receives a PDCCH indicating a downlink transmission, or if the terminal device has a configured downlink grant in that subframe, then:

[0086] a) If the terminal device is an NB-IoT terminal or an enhanced Machine Type Communication (eMTC) terminal, then:

[0087] a1) If the PDCCH indicates that multiple transport blocks (TB) are scheduled for transmission, the terminal device starts the HARQ RTT Timer corresponding to all downlink HARQ processes used by the PDSCH of the multiple TBs in the subframe where the last repeated transmission of the physical downlink shared channel (PDSCH) of the last TB of the multiple TBs is received.

[0088] a2) Otherwise, the terminal device starts the HARQ RTT Timer corresponding to the downlink HARQ process used by the PDSCH in the subframe where the last repeated transmission of the PDSCH is received.

[0089] b) Otherwise, the terminal device starts the HARQ RTT Timer corresponding to the downlink HARQ process used by the PDSCH.

[0090] If the HARQ RTT Timer times out, then: if the data decoding of the HARQ process fails, the terminal device starts the drx-RetransmissionTimer corresponding to the downlink HARQ process.

[0091] In addition, if the HARQ RTT Timer times out, for the NB-IoT terminal: if PDCCH schedules multiple TBs, then when the HARQ RTT Timers corresponding to the HARQ processes used by the multiple TBs all time out, start or restart the drx-InactivityTimer; otherwise, if PDCCH schedules a single TB, then when the HARQ RTT Timer corresponding to the HARQ process used by the TB times out, start or restart the drx-InactivityTimer.

[0092] In some scenarios, the conditions for the terminal device to start or restart the UL HARQ RTT Timer are:

[0093] If the terminal device receives a PDCCH indicating an uplink transmission using an asynchronous HARQ process, or if the terminal device has a configured uplink grant for an asynchronous HARQ process in the subframe, or if the terminal device receives a PDCCH indicating an uplink transmission using an automatic HARQ process, then:

[0094] a) If mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured;

[0095] a1) If the PDCCH indicates that the transmission of multiple TBs is scheduled, the terminal device starts the UL HARQ RTT Timer corresponding to all uplink HARQ processes used by the physical uplink shared channel (PUSCH) of the multiple TBs in the subframe where the last repeated transmission of the PUSCH of the last TB of the multiple TBs is completed.

[0096] a2) Otherwise, the UE starts the UL HARQ RTT Timer corresponding to the uplink HARQ process used by the PUSCH in the subframe where the last repeated transmission of the PUSCH is completed.

[0097] If the UL HARQ RTT Timer corresponding to a certain uplink HARQ process times out, the terminal device starts the drx-ULRetransmissionTimer corresponding to the uplink HARQ process.

[0098] In addition, if the UL HARQ RTT Timer corresponding to a certain uplink HARQ process times out, for the NB-IoT terminal: if the PDCCH indicates that multiple TBs are scheduled, then when the UL HARQ RTT Timers corresponding to the HARQ processes used by the multiple TBs all time out, the drx-InactivityTimer is started or restarted; otherwise, if the PDCCH schedules a single TB, then when the UL HARQ RTT Timer corresponding to the HARQ process used by the TB times out, the drx-InactivityTimer is started or restarted.

[0099] In some scenarios, the definitions of HARQ RTT Timer and UL HARQ RTT Timer are as follows:

[0100] For eMTC, if the PDCCH indicates that a TB is scheduled, the HARQ RTT Timer is 7+N (in subframes), where N is the PUCCH repetition factor used. For TDD, the HARQ RTT Timer is 3+k+N, where k is the time interval between the last PDSCH retransmission and the first retransmission of the corresponding HARQ feedback, and N is the PUCCH repetition factor used.

[0101] For eMTC, if the PDCCH indicates that multiple TBs are scheduled and HACK-ACK bundling is not configured, the duration of the HARQ RTT Timer is 7+m*N, where N is the PUCCH repetition factor used and m is the number of scheduled TBs indicated by the PDCCH.

[0102] For eMTC, if the PDCCH indicates that multiple TBs are scheduled and HACK-ACK bundling is configured, the duration of the HARQ RTT Timer is 7+k*N, where N is the PUCCH repetition factor used and k is the number of HARQ feedback bundles, k=ceiling(N TB / M),N TB is the number of scheduled TBs indicated by the PDCCH, and M is the HARQ feedback bundling size of multi-TB scheduling indicated by the PDCCH.

[0103] For NB-IoT, if the PDCCH indicates that a TB is scheduled, or if the PDCCH indicates that multiple TBs are scheduled simultaneously and HARQ-ACK bundling is configured, the duration of the HARQ RTT Timer is k+3+N+△PDCCH (unit: subframe), where k is the time interval between the last subframe of the PDSCH transmission and the first subframe of the corresponding HARQ feedback transmission, N is the transmission duration of the corresponding HARQ feedback, and △PDCCH is the time interval from the next subframe of the last subframe of the corresponding HARQ feedback plus 3 subframes to the first subframe of the next PDCCH opportunity.

[0104] For NB-IoT, if PDCCH indicates that multiple TBs are scheduled simultaneously and HARQ-ACK bundling is not configured, the duration of the HARQ RTT Timer is k+2*N+1+△PDCCH (unit: subframe), where k is the time interval between the last subframe of PDSCH transmission and the first subframe of the corresponding HARQ feedback transmission, N is the transmission duration of the corresponding HARQ feedback, and △PDCCH is the time interval from the next subframe of the last subframe of the corresponding HARQ feedback plus 1 subframe to the first subframe of the next PDCCH opportunity.

[0105] For eMTC, for FDD and frame structure type 3, the UL HARQ RTT Timer duration is 4 subframes; for TDD, the UL HARQ RTT Timer duration is k ULHARQRTT subframes, where k ULHARQRTT k PHICH .

[0106] For NB-IoT, if the PDCCH indicates that a TB is scheduled, the duration of the UL HARQ RTT Timer is 4 + △PDCCH subframes, where △PDCCH is the time interval from the last subframe of the PUSCH transmission plus the next subframe of 3 subframes to the first subframe of the next PDCCH opportunity.

[0107] For NB-IoT, if the PDCCH indicates that multiple TBs are scheduled simultaneously, the duration of the UL HARQ RTT Timer is 1 + △PDCCH subframes, where △PDCCH is the time interval from the next subframe after the last subframe of the PUSCH transmission plus 1 subframe to the first subframe of the next PDCCH opportunity.

[0108] Compared with TN system, the signal transmission delay between UE and base station in NTN system is greatly increased. In order to adapt to the large delay characteristics of NTN system, the definition of HARQ RTT Timer and UL RTT Timer is considered to add an RTT on the basis of the above formula. offset , and also stipulates that in the TN system, RTT offset The value is 0. In the NTN system, RTTRTT offset The value is the RTT between the UE and the base station.

[0109] In the NTN system, the introduction of HARQ feedback disabling is being considered. That is, the network device can configure the HARQ process to disable or enable HARQ feedback. For a UE, the network device can configure some of the UE's HARQ processes to enable HARQ feedback mode, while configuring the other HARQ processes of the UE to disable HARQ feedback mode.

[0110] In the NTN system, the above timer definition only considers the case where HACK feedback is enabled. Therefore, when the network device schedules the transmission of multiple TBs, and the HARQ processes used by these TBs include both HACK feedback-enabled HARQ processes and HARQ feedback-disabled HARQ processes, how the terminal device chooses the appropriate time to monitor the PDCCH is an urgent problem that needs to be solved.

[0111] FIG6 is a schematic flow chart of a wireless communication method 200 provided in an embodiment of the present application. As shown in FIG6 , the method 200 may include at least part of the following:

[0112] S210, the terminal device receives a physical downlink control channel PDCCH, where the PDCCH is used to schedule transmission of multiple transport blocks TB, where the multiple TBs are transmitted using multiple hybrid automatic repeat request HARQ processes, where the multiple HARQ processes include at least one first-type HARQ process and at least one second-type HARQ process, where the first-type HARQ process is configured to disable a downlink hybrid automatic repeat request HARQ feedback mode, and the second-type HARQ process is configured to enable a downlink HARQ feedback mode;

[0113] S220: Start or restart a discontinuous reception DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first type HARQ process according to the time when HARQ feedback is completed for the multiple TBs.

[0114] In some embodiments, the terminal device is a terminal device in an NTN.

[0115] Optionally, the NTN may be an Internet of Things Non-Terrestrial Communication Network (IoT-NTN) system.

[0116] For example, the Narrow Band Internet of Things over NTN (NB-IoT-NTN) system or the enhanced Machine Type Communication over NTN (eMTC-NTN) system.

[0117] In some embodiments, the terminal device is a NB-IoT terminal or an eMTC terminal.

[0118] In some embodiments, the terminal device is in a connected state.

[0119] In an embodiment of the present application, the HARQ feedback mode can be replaced by a HARQ-ACK feedback mode, and the HARQ feedback can be replaced by HARQ-ACK feedback.

[0120] In some embodiments, the multiple TBs are transmitted via PDSCH, for example, each TB is transmitted via a corresponding PDSCH.

[0121] That is, the first type HARQ process and the second type HARQ process are downlink HARQ processes.

[0122] In some embodiments, the first type of HARQ process is configured to disable a downlink HARQ feedback mode, or in other words, is configured to disable downlink HARQ feedback.

[0123] That is, the first type of HARQ process is a HARQ process with a disabled HARQ feedback mode (or in other words, a HARQ feedback disabled) (a HARQ process with a disabled DL HARQ feedback mode).

[0124] In some embodiments, the second type of HARQ process is configured to enable a downlink HARQ feedback mode, or in other words, is configured to enable downlink HARQ feedback.

[0125] That is, the second type of HARQ process is a HARQ process with an enabled HARQ feedback mode (or, in other words, a HARQ feedback enabled) (a HARQ process with an enabled DL HARQ feedback mode).

[0126] For TBs transmitted using the first type of HARQ process, the terminal device does not need to perform HARQ feedback.

[0127] For TBs transmitted using the second type of HARQ process, the terminal device needs to perform HARQ feedback.

[0128] For example, for a TB transmitted using the second type of HARQ process, the terminal device may feed back a positive acknowledgment (ACK) or a negative acknowledgment (NACK) according to the decoding result of the TB.

[0129] In some embodiments, some of the multiple TBs are transmitted using a first type of HARQ process, while the other TBs are transmitted using a second type of HARQ process. That is, the multiple TBs include TBs that require HARQ feedback (denoted as first type TBs) and TBs that do not require HARQ feedback (denoted as second type TBs).

[0130] In an embodiment of the present application, for the transmission of multiple TBs scheduled by a PDCCH, when a terminal device needs to perform HARQ feedback on some of the multiple TBs, the terminal device needs to perform HARQ feedback on the part of the TBs after completing the reception of the multiple TBs. When the terminal device has not completed the HARQ feedback, the terminal device cannot perform downlink reception. Therefore, the terminal device can determine the timing to start monitoring the PDCCH based on the time when the HARQ feedback is completed for the multiple TBs, thereby avoiding the waste of resources caused by the terminal device monitoring the PDCCH before completing the HARQ feedback for the multiple TBs.

[0131] In some embodiments of the present application, the S210:

[0132] After completing the HARQ feedback of the multiple TBs, start or restart a DRX inactivity timer (drx-InactivityTimer) and / or a DRX retransmission timer (drx-RetransmissionTimer) corresponding to the at least one first-type HARQ process.

[0133] For example, after the HARQ feedback of the multiple TBs is completed, the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-type HARQ process is immediately started or restarted.

[0134] Furthermore, the terminal device monitors the PDCCH during the running period of the drx-InactivityTimer, and / or monitors the PDCCH indicating downlink retransmission scheduling during the running period of the drx-RetransmissionTimer corresponding to each first-type HARQ process.

[0135] Therefore, after completing the HARQ feedback for the multiple TBs, the terminal device starts or restarts the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-class HARQ process, so that the terminal device can enter the active period (active time) as soon as possible to monitor the PDCCH, so that the network device can use the first-class HARQ process to schedule subsequent data transmission as soon as possible, reduce the possibility of HARQ process stalling, and improve the transmission rate and throughput.

[0136] Correspondingly, the network device may send a PDCCH to the terminal device after receiving the HARQ feedback of the terminal device on the multiple TBs, or a PDCCH indicating downlink retransmission scheduling.

[0137] That is, the network device may consider that the terminal device enters the active time after completing the HARQ feedback for the multiple TBs. Furthermore, the network device may send the PDCCH to the terminal device when the terminal device is in the active time.

[0138] It should be understood that in the embodiment of the present application, completing the HARQ feedback of the multiple TBs includes:

[0139] Complete HARQ feedback of the TBs in the multiple TBs that use the second type of HARQ process.

[0140] That is, the HARQ feedback for the TB requiring HARQ feedback is completed.

[0141] It should be understood that the present application does not limit the HARQ feedback mode of the TB using the second type of HARQ process, for example, it can be bundling feedback, or non-bundling feedback, etc.

[0142] In some other embodiments of the present application, the 210:

[0143] After completing the first duration of HARQ feedback of the multiple TBs, start or restart the DRX inactivity timer and / or the DRX retransmission timer corresponding to the at least one first type HARQ process.

[0144] Unlike the previous embodiment, the terminal device does not start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-type HARQ process immediately after completing HARQ feedback for the multiple TBs. Instead, the terminal device starts or restarts the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-type HARQ process after a first time interval after completing HARQ feedback for the multiple TBs.

[0145] In some embodiments, it can be considered that before the HARQ feedback of the multiple TBs is completed and within the first time period after the HARQ feedback of the multiple TBs is completed, the terminal device cannot perform downlink reception, or in other words, is not yet ready for downlink reception. Therefore, the terminal device can start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-type HARQ process after the first time period after completing the HARQ feedback of the multiple TBs, which is beneficial to reducing the waste of resources caused by the terminal device performing PDCCH monitoring during this time period.

[0146] After the first period of time after completing the HARQ feedback for the multiple TBs, it can be considered that the terminal device is able to perform downlink reception, or is ready for downlink reception. In this case, the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-type HARQ process can be started or restarted to ensure that the terminal device enters the active period (active time) as soon as possible to monitor the PDCCH when it is able to perform downlink reception, so that the network device can use the first-type HARQ process to schedule subsequent data transmission as soon as possible, reduce the possibility of HARQ process stalling, and improve the transmission rate and throughput.

[0147] In some embodiments, the first duration is predefined or configured by the network device.

[0148] For example, 1ms, 3ms, or other time lengths.

[0149] In some embodiments, the first duration is determined based on a switching time between uplink transmission and downlink reception of the terminal device and / or a transmission delay between the network device and the terminal device. Optionally, the transmission delay may be an RTT between the network device and the terminal device.

[0150] Exemplarily, the first duration may be a switching time.

[0151] Exemplarily, the first duration may be the sum of the switching time and the transmission delay.

[0152] Specifically, the terminal device's HARQ feedback for multiple TBs belongs to an uplink sending behavior, and the terminal device's monitoring of PDCCH belongs to a downlink receiving behavior. A certain switching time is required from uplink sending to downlink receiving, and the terminal device cannot perform downlink reception during the switching time. Therefore, the switching time of the terminal device is considered when designing the start time or restart time of the drx-InactivityTimer and / or at least one first-class HARQ process corresponding to the drx-RetransmissionTimer, which is beneficial to reducing the waste of resources caused by the terminal device's PDCCH monitoring during the switching time.

[0153] In addition, in the NTN system, the transmission delay between the network device and the terminal device is relatively large. The HARQ feedback information sent by the terminal device to the network device takes a certain amount of time to reach the network device, and the signal sent by the network device to the terminal device also takes a certain amount of time to reach the terminal device. Before the signal sent by the network device may reach the terminal device, the terminal device does not need to monitor the PDCCH. Therefore, in an embodiment of the present application, the transmission delay between the network device and the terminal device can be considered when designing the start time or restart time of the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to at least one first-class HARQ process, which is beneficial to reducing the waste of resources caused by the terminal device monitoring the PDCCH during the signal propagation process.

[0154] In some embodiments, the method 200 further includes:

[0155] After completing the HARQ feedback of the multiple TBs, start or restart the HARQ round trip time RTT timer corresponding to the at least one second type HARQ process; or

[0156] After completing the reception of the multiple TBs, start or restart the HARQ RTT timer corresponding to the at least one second-type HARQ process.

[0157] The specific execution process is described with reference to the specific examples shown in FIG7 and FIG8 .

[0158] Step 1: The terminal device receives PDCCH.

[0159] The PDCCH indicates that PDSCH transmission of multiple TBs is scheduled simultaneously, wherein the HARQ process used by at least one TB among the multiple TBs is in a disabled DL HARQ feedback mode, and the HARQ process used by at least one TB is in an enabled DL HARQ feedback mode.

[0160] As shown in Figures 7 and 8, the PDCCH schedules PDSCH transmission for six TBs, including TB1 through TB6, which use HARQ processes 0 through 5, respectively. TB2 and TB4 use HARQ processes in the disabled DL HARQ feedback mode, while the other TBs use HARQ processes in the enabled DL HARQ feedback mode. Therefore, the terminal device needs to provide HARQ feedback for TB1, TB3, TB5, and TB6.

[0161] Step 2: The terminal device receives the PDSCH of the multiple TBs.

[0162] Step 3: The terminal device performs HARQ feedback on TB1, TB3, TB5 and TB6.

[0163] FIG7 is an example of performing HARQ feedback using a non-bundling HARQ feedback method. As shown in FIG7 , the terminal device may perform HARQ feedback on TB1 , TB3 , TB5 , and TB6 , respectively.

[0164] FIG8 is an example of performing HARQ feedback using a bundled HARQ feedback method. As shown in FIG8 , the terminal device may perform bundled feedback on TB1 and TB3, and perform bundled feedback on TB5 and TB6.

[0165] Step 4: Start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to HARQ process 1 and HARQ process 3.

[0166] As shown in FIG7 , after the HARQ feedback for TB1 , TB3 , TB5 and TB6 is completed, the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process 1 and the HARQ process 3 are immediately started or restarted.

[0167] As shown in FIG8 , after the first time period after the HARQ feedback for TB1 , TB3 , TB5 and TB6 is completed, the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to HARQ process 1 and HARQ process 3 are started or restarted.

[0168] In summary, in an embodiment of the present application, for the transmission of multiple TBs scheduled by a PDCCH, when the HARQ process used by some TBs in the multiple TBs is configured as the disabled DL HARQ feedback mode, and the HARQ process used by other TBs is configured as the enabled DL HARQ feedback mode, the terminal device can start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured as the disabled DL HARQ feedback mode according to the time for completing the HARQ feedback for the multiple TBs, that is, determine the PDCCH monitoring timing, which is conducive to avoiding resource waste caused by the terminal device monitoring the PDCCH before completing the HARQ feedback for the multiple TBs.

[0169] In one implementation, after completing the HARQ feedback for the multiple TBs, the terminal device may immediately start the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured in the disabled DL HARQ feedback mode, so that the terminal device can enter the active period (active time) to monitor the PDCCH as soon as possible, so that the network device can use the HARQ process configured in the disabled DL HARQ feedback mode to schedule subsequent data transmission as soon as possible, reduce the possibility of the HARQ process stalling, and improve the transmission rate and throughput.

[0170] In another implementation, before completing the first duration of HARQ feedback for the multiple TBs, the terminal device is not yet ready to receive and / or the signal sent by the network device cannot reach the terminal device. Therefore, the terminal device can start the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured as the disabled DL HARQ feedback mode after completing the first duration of HARQ feedback for the multiple TBs, so that the terminal device can enter the active period (active time) to monitor the PDCCH as soon as possible, so that the network device can use the HARQ process configured as the disabled DL HARQ feedback mode to schedule subsequent data transmission as soon as possible, reduce the possibility of HARQ process stalling, and improve the transmission rate and throughput.

[0171] The above text, in combination with Figures 6 to 8, describes in detail the method embodiment of the present application. The following text, in combination with Figures 9 to 12, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0172] FIG9 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG9 , the terminal device 400 includes:

[0173] A communication unit 410 is configured to receive a physical downlink control channel (PDCCH), where the PDCCH is used to schedule transmission of multiple transport blocks (TBs), where the multiple TBs are transmitted using multiple hybrid automatic repeat request (HARQ) processes, where the multiple HARQ processes include at least one first-type HARQ process and at least one second-type HARQ process, where the first-type HARQ process is configured to disable a downlink HARQ feedback mode, and the second-type HARQ process is configured to enable a downlink HARQ feedback mode;

[0174] The processing unit 420 is configured to start or restart a discontinuous reception DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first type HARQ process according to the time when HARQ feedback is completed for the multiple TBs.

[0175] In some embodiments, the processing unit 420 is further configured to:

[0176] After completing HARQ feedback for the multiple TBs, start or restart a DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first-type HARQ process.

[0177] In some embodiments, the processing unit 420 is further configured to:

[0178] After completing the first duration of HARQ feedback for the multiple TBs, start or restart the DRX inactivity timer and / or the DRX retransmission timer corresponding to the at least one first type HARQ process.

[0179] In some embodiments, the first duration is predefined or configured by the network device.

[0180] In some embodiments, the first duration is determined based on the switching time of the terminal device from uplink transmission to downlink reception and / or the transmission delay between the network device and the terminal device.

[0181] In some embodiments, the performing HARQ feedback on the plurality of TBs includes:

[0182] Complete HARQ feedback for the TBs in the multiple TBs that use the second type of HARQ process.

[0183] In some embodiments, the processing unit 420 is further configured to:

[0184] After completing HARQ feedback for the multiple TBs, start or restart a HARQ round trip time (RTT) timer corresponding to the at least one second-type HARQ process; or

[0185] After completing the reception of the multiple TBs, start or restart the HARQ RTT timer corresponding to the at least one second-type HARQ process.

[0186] In some embodiments, the terminal device is a terminal device in a non-terrestrial network NTN.

[0187] In some embodiments, the terminal device is a narrowband Internet of Things (NB-IoT) terminal or an enhanced machine type communication (eMTC) terminal.

[0188] Alternatively, in some embodiments, the communication module may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The determination module may be one or more processors.

[0189] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 400 are respectively for realizing the corresponding processes of the terminal device in the method 200 shown in Figures 6 to 8. For the sake of brevity, they will not be repeated here.

[0190] In summary, in an embodiment of the present application, for the transmission of multiple TBs scheduled by a PDCCH, when the HARQ process used by some TBs in the multiple TBs is configured as the disabled DL HARQ feedback mode, and the HARQ process used by other TBs is configured as the enabled DL HARQ feedback mode, the terminal device can start or restart the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured as the disabled DL HARQ feedback mode according to the time for completing the HARQ feedback for the multiple TBs, that is, determine the PDCCH monitoring timing, which is conducive to avoiding resource waste caused by the terminal device monitoring the PDCCH before completing the HARQ feedback for the multiple TBs.

[0191] In one implementation, after completing the HARQ feedback for the multiple TBs, the terminal device may immediately start the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured in the disabled DL HARQ feedback mode, so that the terminal device can enter the active period (active time) to monitor the PDCCH as soon as possible, so that the network device can use the HARQ process configured in the disabled DL HARQ feedback mode to schedule subsequent data transmission as soon as possible, reduce the possibility of the HARQ process stalling, and improve the transmission rate and throughput.

[0192] In another implementation, before completing the first duration of HARQ feedback for the multiple TBs, the terminal device is not yet ready to receive and / or the signal sent by the network device cannot reach the terminal device. Therefore, the terminal device can start the drx-InactivityTimer and / or the drx-RetransmissionTimer corresponding to the HARQ process configured as the disabled DL HARQ feedback mode after completing the first duration of HARQ feedback for the multiple TBs, so that the terminal device can enter the active period (active time) to monitor the PDCCH as soon as possible, so that the network device can use the HARQ process configured as the disabled DL HARQ feedback mode to schedule subsequent data transmission as soon as possible, reduce the possibility of HARQ process stalling, and improve the transmission rate and throughput.

[0193] Figure 10 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in Figure 10 includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0194] Optionally, as shown in FIG10 , the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0195] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0196] Optionally, as shown in FIG10 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0197] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

[0198] Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0199] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0200] Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in Figure 11 includes a processor 710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0201] Optionally, as shown in FIG11 , the chip 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0202] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0203] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

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

[0205] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0206] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0207] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0208] FIG12 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG12 , the communication system 900 includes a terminal device 910 and a network device 920 .

[0209] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be repeated here.

[0210] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0211] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0212] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0213] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0214] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0215] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0216] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0217] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0218] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0219] The embodiment of the present application also provides a computer program.

[0220] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0221] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0222] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0223] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

[0225] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

[0227] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0228] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a physical downlink control channel PDCCH, where the PDCCH is used to schedule transmission of multiple transport blocks TB, where the multiple TBs are transmitted using multiple hybrid automatic repeat request HARQ processes, where the multiple HARQ processes include at least one first type HARQ process and at least one second type HARQ process, where the first type HARQ process is configured to disable a downlink HARQ feedback mode, and the second type HARQ process is configured to enable a downlink HARQ feedback mode; According to the time when HARQ feedback is completed for the multiple TBs, a discontinuous reception DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first type HARQ process is started or restarted.

2. The method according to claim 1, characterized in that The starting or restarting a discontinuous reception (DRX) inactivity timer and / or a DRX retransmission timer corresponding to the at least one first-type HARQ process according to a time when HARQ feedback is completed for the multiple TBs includes: After completing HARQ feedback for the multiple TBs, start or restart a DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first-type HARQ process.

3. The method according to claim 1, characterized in that The starting or restarting a discontinuous reception (DRX) inactivity timer and / or a DRX retransmission timer corresponding to the at least one first-type HARQ process according to a time when HARQ feedback is completed for the PDSCH includes: After completing the first duration of HARQ feedback for the multiple TBs, start or restart the DRX inactivity timer and / or the DRX retransmission timer corresponding to the at least one first type HARQ process.

4. The method according to claim 3, characterized in that The first duration is predefined or configured by the network device.

5. The method according to claim 3 or 4, characterized in that The first duration is determined according to the switching time of the terminal device from uplink transmission to downlink reception, and / or the transmission delay between the network device and the terminal device.

6. The method according to any one of claims 1 to 5, characterized in that The completing HARQ feedback for the multiple TBs includes: Complete HARQ feedback for the TBs in the multiple TBs that use the second type of HARQ process.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: After completing HARQ feedback for the multiple TBs, start or restart a HARQ round trip time (RTT) timer corresponding to the at least one second-type HARQ process; or After completing the reception of the multiple TBs, start or restart the HARQ RTT timer corresponding to the at least one second-type HARQ process.

8. The method according to any one of claims 1 to 7, characterized in that The terminal device is a terminal device in a non-terrestrial network NTN.

9. The method according to any one of claims 1 to 8, characterized in that The terminal device is a narrowband Internet of Things (NB-IoT) terminal or an enhanced machine type communication (eMTC) terminal.

10. A terminal device, characterized in that: include: a communication unit, configured to receive a physical downlink control channel (PDCCH), where the PDCCH is used to schedule transmission of multiple transport blocks (TBs), where the multiple TBs are transmitted using multiple hybrid automatic repeat request (HARQ) processes, where the multiple HARQ processes include at least one first-type HARQ process and at least one second-type HARQ process, where the first-type HARQ process is configured to disable a downlink HARQ feedback mode, and the second-type HARQ process is configured to enable a downlink HARQ feedback mode; The processing unit is configured to start or restart a discontinuous reception DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first type HARQ process according to the time when HARQ feedback is completed for the multiple TBs.

11. The terminal device according to claim 10, characterized in that The processing unit is further configured to: After completing HARQ feedback for the multiple TBs, start or restart a DRX inactivity timer and / or a DRX retransmission timer corresponding to the at least one first-type HARQ process.

12. The terminal device according to claim 10, characterized in that The processing unit is further configured to: After completing the first duration of HARQ feedback for the multiple TBs, start or restart the DRX inactivity timer and / or the DRX retransmission timer corresponding to the at least one first type HARQ process.

13. The terminal device according to claim 12, characterized in that The first duration is predefined or configured by the network device.

14. The terminal device according to claim 12 or 13, characterized in that: The first duration is determined according to the switching time of the terminal device from uplink transmission to downlink reception, and / or the transmission delay between the network device and the terminal device.

15. The terminal device according to any one of claims 10 to 14, characterized in that: The completing HARQ feedback for the multiple TBs includes: Complete HARQ feedback for the TBs in the multiple TBs that use the second type of HARQ process.

16. The terminal device according to any one of claims 10 to 15, characterized in that: The processing unit is further configured to: After completing HARQ feedback for the multiple TBs, start or restart a HARQ round trip time (RTT) timer corresponding to the at least one second-type HARQ process; or After completing the reception of the multiple TBs, start or restart the HARQ RTT timer corresponding to the at least one second-type HARQ process.

17. The terminal device according to any one of claims 10 to 16, characterized in that: The terminal device is a terminal device in a non-terrestrial network NTN.

18. The terminal device according to any one of claims 10 to 17, characterized in that: The terminal device is a narrowband Internet of Things (NB-IoT) terminal or an enhanced machine type communication (eMTC) terminal.

19. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 9.

20. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 9.

21. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 9.

22. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to execute the method according to any one of claims 1 to 9.

23. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 9.

Images