CN113728697A

CN113728697A - Wireless communication method and terminal device

Info

Publication number: CN113728697A
Application number: CN201980095407.8A
Authority: CN
Inventors: 杨宁
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-25
Filing date: 2019-09-25
Publication date: 2021-11-30
Anticipated expiration: 2039-09-25
Also published as: CN113728697B; WO2021056226A1

Abstract

The embodiment of the application provides a wireless communication method and terminal equipment, for an HARQ process with a feedback function closed, the terminal equipment starts or restarts a DRX (discontinuous reception) inactivity timer after dynamically scheduling uplink transmission, dynamically scheduling downlink transmission, pre-configured resource uplink transmission and pre-configured resource uplink and downlink transmission, so that the terminal equipment can continue to monitor a PDCCH (physical downlink control channel) after performing the operations, and the terminal equipment can continuously schedule retransmission or continuously receive new transmission to the network equipment in an NTN (network transport network). The wireless communication method includes: for the HARQ process with the feedback function turned off, the terminal device starts or restarts the DRX inactivity timer after performing a first operation, wherein the first operation includes at least one of: receiving a downlink dynamic scheduling signaling, receiving an uplink dynamic scheduling signaling, receiving an MAC PDU on a downlink pre-configured resource, and sending the MAC PDU on an uplink pre-configured resource.

Description

Wireless communication method and terminal device

Technical Field

The present embodiments relate to the field of communications, and in particular, to a wireless communication method and a terminal device.

Background

A New wireless (5-Generation New Radio, 5G NR) system of a fifth Generation mobile communication technology defines a Non-terrestrial network (NTN) system deployment scenario including a satellite network, and by means of wide area coverage capability of a satellite, the NTN system can realize continuity of 5G NR services. Because the satellite moves fast relative to the ground, the signal propagation delay between the terminal device and the satellite in the NTN is greatly increased, in order to ensure the data transmission continuity without increasing the number of Hybrid Automatic Repeat reQuest (HARQ) processes, a higher requirement is provided for the HARQ scheme in the NTN system, how to ensure the data transmission continuity without increasing the number of HARQ processes is an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and a terminal device, for an HARQ process with a feedback function being turned off, the terminal device starts or restarts a Discontinuous Reception (DRX) inactivity timer after dynamically scheduling uplink transmission, dynamically scheduling Downlink transmission, pre-configured resource uplink transmission, and pre-configured resource uplink and Downlink transmission, so that the terminal device can continue to monitor a Physical Downlink Control Channel (PDCCH) after performing these operations, and thus the terminal device can continuously schedule retransmission or continuous Reception of new transmission to the network device in an NTN network.

In a first aspect, a wireless communication method is provided, and the method includes:

for the HARQ process with the feedback function turned off, the terminal device starts or restarts the DRX inactivity timer after performing the first operation, wherein,

the first operation includes at least one of:

receiving a downlink dynamic scheduling signaling, receiving an uplink dynamic scheduling signaling, receiving a Media Access Control Protocol Data Unit (MAC PDU) on a downlink pre-configured resource, and transmitting the MAC PDU on an uplink pre-configured resource.

It should be noted that, the receiving of the MAC PDU on the downlink preconfigured resource may also be receiving downlink data on the downlink preconfigured resource, and the sending of the MAC PDU on the uplink preconfigured resource may also be sending uplink data on the uplink preconfigured resource.

In a second aspect, a terminal device is provided, which is configured to perform the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.

In a third aspect, a terminal device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect or each implementation manner thereof.

In a fourth aspect, an apparatus is provided for implementing the method of the first aspect or its implementation manners.

Specifically, the apparatus includes: a processor configured to invoke and run the computer program from the memory, so that the device on which the apparatus is installed performs the method according to the first aspect or its implementations.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method of the first aspect or its implementations.

A sixth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of the first aspect or its implementations.

In a seventh aspect, a computer program is provided, which, when run on a computer, causes the computer to perform the method of the first aspect or its implementations.

Through the technical scheme, for the HARQ process with the feedback function closed, the terminal equipment starts or restarts the DRX inactivity timer after executing the first operation, so that the terminal equipment can continue to monitor the PDCCH after executing the first operation, and the terminal equipment can continuously schedule retransmission or continuous reception of new transmission to the network equipment in the NTN network.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Fig. 2 is a schematic flow chart of a wireless communication method provided according to an embodiment of the present application.

Fig. 3 is a schematic diagram of dynamically scheduling downlink transmission according to an embodiment of the present application.

Fig. 4 is a schematic diagram of dynamically scheduling uplink transmission according to an embodiment of the present application.

Fig. 5 is a schematic diagram of uplink transmission on an uplink preconfigured resource according to an embodiment of the present application.

Fig. 6 is a schematic diagram of uplink and downlink transmission of a downlink preconfigured resource provided in an embodiment of the present application.

Fig. 7 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

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

Fig. 9 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.

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

Detailed Description

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

The embodiment of the application can be applied to various communication systems, such as: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, New Radio (NR) System, Evolution System of NR System, LTE-a System over unlicensed spectrum, NR (NR-b) System, UMTS (Universal Mobile telecommunications System), UMTS (UMTS) System, WLAN-b System over unlicensed spectrum, WiFi-b System, Wireless Local Area Network (WLAN) System, Wireless Local Area network (WiFi) System, GPRS (General Packet Radio Service, GPRS) System, GPRS (GPRS) System, LTE-b System, LTE-a System, NR System, LTE-b System over unlicensed spectrum, and LTE-b System over unlicensed spectrum, Next generation communication systems or other communication systems, etc.

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

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

The frequency spectrum of the application is not limited in the embodiment of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area.

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

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

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

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

The embodiments of the present application are described in conjunction with a terminal device and a network device, where: a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment, etc. The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a next generation communication system, for example, a terminal device in an NR Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

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

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

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

The 5G NR system defines the NTN system deployment scenario including the satellite network. The NTN generally provides communication services to terrestrial users by way of satellite communications. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communication is not limited by user regions, for example, general terrestrial communication cannot cover regions where communication equipment cannot be set up, such as the sea, mountains, desert, and the like, or communication coverage is not performed due to sparse population, and for satellite communication, since one satellite can cover a large ground and the satellite can orbit around the earth, theoretically every corner on the earth can be covered by satellite communication. Second, satellite communication has great social value. Satellite communication can be covered in remote mountainous areas, poor and laggard countries or areas with lower cost, so that people in the areas can enjoy advanced voice communication and mobile internet technology, the digital gap between the areas is favorably reduced and developed, and the development of the areas is promoted. Thirdly, the satellite communication distance is long, and the cost of communication is not obviously increased when the communication distance is increased; and finally, the satellite communication has high stability and is not limited by natural disasters.

Communication satellites are classified into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, geosynchronous Orbit (GEO) satellites, High-elliptic Orbit (HEO) satellites, and the like according to the difference in orbital height.

For example, LEO satellites range in altitude from 500km to 1500km, with corresponding orbital periods of about 1.5 hours to 2 hours. The signal propagation delay for inter-user single-hop communications is typically less than 20 ms. Maximum satellite visibility time 20 minutes. The signal propagation distance is short, the link loss is less, and the requirement on the transmitting power of the user terminal is not high.

As another example, the GEO satellite has an orbital altitude of 35786km and a period of 24 hours of rotation around the earth. The signal propagation delay for inter-user single-hop communications is typically 250 ms.

The conditions for starting or restarting the drx-inactivytytytytimer by the terminal equipment are as follows:

if the terminal receives a PDCCH indicating downlink or uplink initial transmission, the terminal starts or restarts a drx-InactivetyTimer.

The conditions for the terminal to start and stop drx-retransmission timerdl are as follows:

when the terminal equipment receives a PDCCH indicating downlink transmission or when the terminal receives a MAC PDU on the configured downlink authorized resource, the terminal stops the drx-retransmission TimerDL corresponding to the HARQ process. And the terminal starts drx-HARQ-RTT-TimerDL corresponding to the HARQ process after finishing the transmission of the HARQ process feedback aiming at the downlink transmission.

If a timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ of the terminal device is overtime and the downlink data transmitted by using the HARQ process is unsuccessfully decoded, the terminal starts drx-retransmission TimerDL corresponding to the HARQ process.

The conditions for the terminal to start and stop drx-retransmission timerll are:

when the terminal receives a PDCCH indicating uplink transmission or when the terminal sends a MAC PDU on the configured uplink grant resource, the terminal stops the drx-retransmission TimerUL corresponding to the HARQ process. And the terminal starts drx-HARQ-RTT-TimerUL corresponding to the HARQ process after finishing the first retransmission (retransmission) of the PUSCH.

If the timer drx-HARQ-RTT-TimerUL corresponding to a certain HARQ of the terminal is overtime, the terminal starts the drx-retransmission TimerUL corresponding to the HARQ process.

Compared with a cellular network adopted by the traditional NR, the signal propagation delay between the terminal equipment and the satellite in the NTN is greatly increased, and in order to ensure the continuity of data transmission under the condition of not increasing the number of HARQ processes, a scheme for starting or closing the HARQ can be designed.

If the HARQ function is turned off, the terminal device does not need to send HARQ feedback for a Physical Downlink Shared Channel (PDSCH) to the network device.

In case of turning off HARQ feedback, HARQ retransmission is still supported in order to guarantee data transmission reliability.

It should be noted that, if HARQ is turned off, since there is no feedback for HARQ, the network device may continue to schedule retransmission of uplink transmission or downlink transmission before receiving uplink transmission or feedback for downlink transmission of the terminal device. For the terminal device, for uplink data transmission, the terminal device may continue to receive uplink retransmission scheduling after sending the current uplink transmission; for downlink data transmission, the terminal device may continue to receive downlink retransmission scheduling before completing decoding of the current downlink transmission. Therefore, when HARQ is turned off, an Uplink Discontinuous Reception HARQ round trip transmission time Timer (drx-HARQ-RTT-Timer) and a Downlink Discontinuous Reception HARQ round trip transmission time Timer (drx-HARQ-RTT-Timer) may not be needed. Meanwhile, since the terminal device does not need to wait for the network side to process the Reception condition and then schedule Retransmission, the Uplink Discontinuous Reception Retransmission Timer (drx Retransmission Timer, drx-Retransmission Timer) and the Downlink Discontinuous Reception Retransmission Timer (Downlink Discontinuous Reception Retransmission Timer, drx-Retransmission Timer) are also not needed, i.e., the Retransmission scheduling of the network side may be earlier than the receiving time of the network side for Downlink data transmission (Acknowledgement, ACK) or Negative Acknowledgement (NACK) feedback or Uplink data transmission.

In view of the above technical problems, the present application designs a scheme for a terminal device to discontinuously receive a Physical Downlink Control Channel (PDCCH) when HARQ feedback is turned off. Aiming at the HARQ process of closing the HARQ feedback function, by closing DRX-HARQ-RTT-TimerUL, DRX-HARQ-RTT-TimerL, DRX-retransmission TimerUL and DRX-retransmission TimerUL, the terminal equipment does not wait for the detection result of the data packet at the network side any more, and by introducing the restart of a Discontinuous Reception (DRX) inactivity timer (inactivity timer), the terminal equipment can be ensured to continue monitoring the PDCCH after dynamically scheduling uplink transmission/downlink transmission and preconfigured uplink transmission/downlink transmission, and the terminal equipment can continuously schedule retransmission or continuous Reception of new transmission to the network equipment in the NTN network.

The following describes in detail a scheme for a terminal device to discontinuously receive a PDCCH with HARQ feedback turned off, which is designed in the present application for the above technical problem.

Fig. 2 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, and as shown in fig. 2, the method 200 may include some or all of the following:

for the HARQ process with the feedback function turned off, the terminal device starts or restarts a DRX inactivity timer after performing a first operation S210, wherein,

the first operation includes at least one of:

receiving a downlink dynamic scheduling signaling, receiving an uplink dynamic scheduling signaling, receiving an MAC PDU on a downlink pre-configured resource, and sending the MAC PDU on an uplink pre-configured resource.

Note that the terminal device monitors the PDCCH during the DRX inactivity timer (DRX inactivity timer) operation.

In this embodiment of the present application, for the HARQ process with the feedback function turned off, the terminal device does not wait for the packet detection result on the network side after performing the first operation, but starts or restarts the DRX inactivity timer after performing the first operation, so that the terminal device is ensured to be able to continue monitoring the PDCCH after dynamically scheduling uplink transmission, dynamically scheduling downlink transmission, receiving the MAC PDU on the downlink preconfigured resource, or sending the MAC PDU on the uplink preconfigured resource, so that the terminal device can continuously schedule retransmission or continuous reception of new transmission on the network in the NTN network.

Alternatively, the method 200 may be applied to NTN. Namely, the embodiment of the present application can be applied to NTN.

Optionally, the embodiments of the present application may also be applied to systems other than NTN, for example, V2V, D2D, LTE, NR, and communication systems of subsequent evolution, which is not limited in this application.

Optionally, in this embodiment of the application, the terminal device does not start or close a first timer and/or a second timer corresponding to the HARQ process after performing the first operation, a duration of the first timer is a Round Trip Time (RTT) in DRX, the second timer is a timer for retransmission in DRX, and the terminal device may not monitor the PDCCH during operation of the first timer and/or the second timer.

Optionally, the first timer is drx-HARQ-RTT-timerll or drx-HARQ-RTT-TimerDL.

It should be noted that each HARQ process may correspond to a dedicated first timer. The first timer reflects the minimum time interval required by the terminal device from uplink transmission to receiving retransmission scheduling issued by the network.

For example, for newly transmitted or retransmitted downlink data, after the downlink HARQ process feedback is transmitted, the drx-HARQ-RTT-TimerDL corresponding to the HARQ process is started.

For another example, for newly transmitted or retransmitted uplink data, after the uplink HARQ process feedback is transmitted, the drx-HARQ-RTT-timerll corresponding to the HARQ process is started.

Optionally, the second timer is an uplink DRX retransmission timer (DRX-retransmission timer ul) or a downlink DRX retransmission timer (DRX-retransmission timer dl).

It should be noted that each HARQ process may correspond to a dedicated second timer.

Optionally, in this embodiment of the present application, the terminal device starts or restarts the DRX inactivity timer when the terminal device finishes performing the first operation. I.e. the terminal device starts or restarts the DRX inactivity timer immediately after performing the first operation.

Optionally, in this embodiment of the present application, the terminal device starts or restarts the DRX inactivity timer after each execution of the first operation.

Optionally, the terminal device starts or restarts the DRX inactivity timer immediately after each execution of the first operation.

In this embodiment of the present application, before performing step S210, the terminal device first needs to determine the HARQ process that has the feedback function turned off.

Optionally, the terminal device determines, according to the configuration of the network device, the HARQ process with the feedback function being turned off.

For example, the terminal device receives first configuration information sent by a network device, where the first configuration information is used to indicate that part or all HARQ processes close a feedback function; and the terminal equipment determines the HARQ process with the feedback function closed according to the first configuration information.

For example, the first configuration information is Media Access Control Main (MAC) configuration information.

Optionally, the network device may send the first configuration information to the terminal device through broadcast or dedicated Radio Resource Control (RRC) signaling.

Optionally, the network device may further configure relevant parameters of DRX, which specifically include a DRX cycle (DRX cycle), a DRX state duration timer (DRX-onDurationTimer), a DRX inactivity timer (DRX-inactivity timer), an uplink DRX HARQ RTT timer (DRX-HARQ-RTT-timerls), a downlink DRX HARQ RTT timer (DRX-HARQ-RTT-timerls), an uplink DRX retransmission timer (DRX-retransmission timerls), a downlink DRX retransmission timer (DRX-retransmission timerls), and the like.

It should be noted that the relevant parameters of the DRX may be configured together with the first configuration information, that is, the network device may configure the relevant parameters of the DRX and the first configuration information through an RRC signaling.

Optionally, in this embodiment of the present application, the downlink dynamic scheduling signaling is used to schedule a downlink new transmission or a downlink retransmission. That is, when the first operation is downlink dynamic scheduling signaling, the first operation is used for scheduling downlink new transmission or downlink retransmission.

Optionally, the Downlink dynamic scheduling signaling and first Downlink Control Information (DCI) are carried in one PDCCH, a New Data Indicator (NDI) bit in the first DCI is flipped to indicate that the Downlink dynamic scheduling signaling is used for scheduling Downlink New transmission, and the NDI bit in the first DCI is not flipped to indicate that the Downlink dynamic scheduling signaling is used for scheduling Downlink retransmission.

Optionally, in this embodiment of the present application, the uplink dynamic scheduling signaling is used to schedule uplink new transmission or uplink retransmission. That is, when the first operation is uplink dynamic scheduling signaling, the first operation is used for scheduling uplink new transmission or uplink retransmission.

Optionally, the uplink dynamic scheduling signaling and the second DCI are carried in one PDCCH, the NDI bit in the second DCI is turned over to indicate that the uplink dynamic scheduling signaling is used for scheduling uplink new transmission, and the NDI bit in the second DCI is not turned over to indicate that the uplink dynamic scheduling signaling is used for scheduling uplink retransmission.

Optionally, in this embodiment of the present application, the MAC PDU received on the downlink pre-configured resource is a downlink newly transmitted MAC PDU.

Optionally, if the first operation is to receive a MAC PDU on a downlink preconfigured resource, the terminal device receives a first PDCCH, where the first PDCCH includes a first downlink scheduling signaling and a third DCI, where the first downlink scheduling signaling is used to schedule downlink retransmission, and an HARQ process indicated in the third DCI is an HARQ process that has a feedback function turned off; and the terminal device starts or restarts the DRX inactivity timer after receiving the first PDCCH.

Specifically, the terminal device starts or restarts the DRX inactivity timer when receiving the first PDCCH. That is, the terminal device starts or restarts the DRX inactivity timer immediately after receiving the first PDCCH.

Optionally, in this embodiment of the present application, the MAC PDU sent on the uplink preconfigured resource is an uplink newly transmitted MAC PDU.

Optionally, if the first operation is a MAC PDU sent on an uplink preconfigured resource, the terminal device receives a second PDCCH, where the second PDCCH includes a first uplink scheduling signaling and a fourth DCI, where the first uplink scheduling signaling is used to schedule uplink retransmission, and a HARQ process indicated in the fourth DCI is a HARQ process with a feedback function closed; and the terminal device starts or restarts the DRX inactivity timer after receiving the second PDCCH.

Specifically, the terminal device starts or restarts the DRX inactivity timer when receiving the second PDCCH. That is, the terminal device starts or restarts the DRX inactivity timer immediately after receiving the second PDCCH.

The above method 200 is described in detail below by examples 1 to 4.

Optionally, as embodiment 1, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically used to configure relevant parameters of DRX and relevant configuration information of a downlink HARQ process, where the relevant parameters of DRX include DRX cycle, DRX-onDurationTimer, DRX-InactivityTimer, DRX-HARQ-RTT-TimerDL, DRX-retransmission TimerDL, and the like; the downlink HARQ process related configuration information includes configuring 2 DL HARQ processes, where the HARQ feedback function of HARQ ID 1 is in an on state, and the HARQ feedback function of HARQ ID 0 is in an off state.

It should be noted that timer 1 in fig. 3 may be drx-onDurationTimer, timer 2 in fig. 3 may be drx-InactivityTimer, timer 3 in fig. 3 may be drx-HARQ-RTT-TimerDL, and timer 4 in fig. 3 may be drx-retransmission TimerDL.

As shown in fig. 3, the terminal device receives a new transmission of PDCCH indication TB1 during the operation of timer 1, uses HARQ ID 0, and starts timer 2 after completing the PDCCH reception. The terminal device then receives the retransmission of 2 PDCCH indication Transport Blocks (TBs) 1 in sequence, and restarts the timer 2 each time it receives a PDCCH indicating TB1 to retransmit the schedule.

As shown in fig. 3, the terminal device receives a new transmission of PDCCH indication TB2 during the operation of timer 1, uses HARQ ID 1, receives a Physical Downlink Shared Channel (PDSCH) on a resource indicated by the PDCCH, and starts timer 3 corresponding to HARQ ID 1 after ACK feedback received for the PDSCH is completed, and starts timer 4 corresponding to HARQ ID 1 after the timer 3 times out.

Optionally, as embodiment 2, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically used to configure relevant parameters of DRX and relevant configuration information of an uplink HARQ process, where the relevant parameters of DRX include DRX cycle, DRX-onDurationTimer, DRX-InactivityTimer, DRX-HARQ-RTT-timerll, DRX-retransmission timerll, and the like; the uplink HARQ process related configuration information includes configuring 2 UL HARQ processes, where the HARQ feedback function of HARQ ID 1 is in an on state and the HARQ feedback function of HARQ ID 0 is in an off state.

It should be noted that timer 1 in fig. 4 may be drx-onDurationTimer, timer 2 in fig. 4 may be drx-InactivityTimer, timer 5 in fig. 4 may be drx-HARQ-RTT-timerll, and timer 6 in fig. 4 may be drx-retransmission timerll.

As shown in fig. 4, the terminal device receives a new transmission of PDCCH indication TB1 during the operation of timer 1, uses HARQ ID 0, and starts timer 2 after completing the PDCCH reception. The terminal device then receives the retransmission of 2 PDCCH indications TB1 in sequence, and restarts timer 2 each time it receives the PDCCH indicating TB1 retransmission scheduling.

As shown in fig. 4, the terminal device receives a new transmission of PDCCH indication TB2 during the operation of timer 1, uses HARQ ID 1, receives a Physical Uplink Shared Channel (PUSCH) on a resource indicated by the PDCCH, and starts timer 5 corresponding to HARQ ID 1 after completing transmission for the PUSCH and starts timer 6 corresponding to HARQ ID 1 after the timer 5 times out.

Optionally, as embodiment 3, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically used to configure relevant parameters of DRX and relevant configuration information of an uplink HARQ process, where the relevant parameters of DRX include DRX cycle, DRX-onDurationTimer, DRX-InactivityTimer, DRX-HARQ-RTT-timerll, DRX-retransmission timerll, and the like; the uplink HARQ process related configuration information includes configuring 2 UL HARQ processes, where the HARQ feedback function of HARQ ID 1 is in an on state and the HARQ feedback function of HARQ ID 0 is in an off state.

It should be noted that timer 1 in fig. 5 may be drx-onDurationTimer, timer 2 in fig. 5 may be drx-InactivityTimer, timer 5 in fig. 5 may be drx-HARQ-RTT-timerll, and timer 6 in fig. 5 may be drx-retransmission timerll.

As shown in fig. 5, the terminal device sends a new transmission of TB1 on an uplink pre-configured resource (configured UL grant), uses HARQ ID 0, and starts timer 2 after the terminal device completes PUSCH transmission. The terminal device then receives the retransmission of 2 PDCCH indications TB1 in sequence, and restarts timer 2 each time it receives the PDCCH indicating TB1 retransmission scheduling.

As shown in fig. 5, the terminal device sends a new transmission of TB2 on an uplink pre-configured resource (configured UL grant), uses HARQ ID 1, starts a timer 5 corresponding to HARQ ID 1 after completing transmission for PUSCH, and starts a timer 6 corresponding to HARQ ID 1 after the timer 5 expires.

Optionally, as embodiment 4, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically used to configure relevant parameters of DRX and relevant configuration information of a downlink HARQ process, where the relevant parameters of DRX include DRX cycle, DRX-onDurationTimer, DRX-InactivityTimer, DRX-HARQ-RTT-TimerDL, DRX-retransmission TimerDL, and the like; the downlink HARQ process related configuration information includes configuring 2 DL HARQ processes, where the HARQ feedback function of HARQ ID 1 is in an on state, and the HARQ feedback function of HARQ ID 0 is in an off state.

It should be noted that timer 1 in fig. 6 may be drx-onDurationTimer, timer 2 in fig. 6 may be drx-InactivityTimer, timer 3 in fig. 6 may be drx-HARQ-RTT-TimerDL, and timer 4 in fig. 6 may be drx-retransmission TimerDL.

As shown in fig. 6, the terminal device sends a new transmission of TB1 on a downlink pre-configured resource (configured DL assignment), uses HARQ ID 0, and starts timer 2 after the terminal device completes PDSCH reception. The terminal device then receives the retransmission of 2 PDCCH indications TB1 in sequence, and restarts timer 2 each time it receives the PDCCH indicating TB1 retransmission scheduling.

As shown in fig. 6, the terminal device sends a new transmission of TB2 on a downlink preconfigured resource (configured DL assignment), uses HARQ ID 1, starts a timer 3 corresponding to HARQ ID 1 after completing ACK feedback for PDSCH reception, and starts a timer 4 corresponding to HARQ ID 1 after the timer 3 times out.

Therefore, in this embodiment of the present application, for the HARQ process with the feedback function turned off, the terminal device does not wait for the packet detection result on the network side after performing the first operation, but starts or restarts the DRX inactivity timer after performing the first operation, so that the terminal device is ensured to be able to continue monitoring the PDCCH after dynamically scheduling uplink transmission, dynamically scheduling downlink transmission, receiving the MAC PDU on the downlink preconfigured resource, or sending the MAC PDU on the uplink preconfigured resource, and the terminal device is able to continuously schedule retransmission or continuous reception of new transmission on the network in the NTN network.

Fig. 7 shows a schematic block diagram of a terminal device 300 according to an embodiment of the application. As shown in fig. 7, the terminal device 300 includes: the processing unit (310) is used for processing,

for the HARQ process with the feedback function turned off, the processing unit 310 starts or restarts a DRX inactivity timer after performing a first operation, wherein,

the first operation includes at least one of:

Optionally, the processing unit 310 is further configured to not start or close a first timer and/or a second timer corresponding to the HARQ process after performing the first operation, where a duration of the first timer is one RTT in DRX, the second timer is a timer for retransmission in DRX, and the terminal device does not monitor the PDCCH during operation of the first timer and/or the second timer.

Optionally, the processing unit 310 is specifically configured to:

the DRX inactivity timer is started or restarted upon completion of performing the first operation.

Optionally, the processing unit 310 is further configured to determine the HARQ process with the feedback function turned off.

Optionally, the terminal device 300 further includes:

a communication unit 320, configured to receive first configuration information, where the first configuration information is used to indicate that part or all of HARQ processes turn off a feedback function;

the processing unit 310 is specifically configured to:

and determining the HARQ process with the feedback function closed according to the first configuration information.

Optionally, the downlink dynamic scheduling signaling is used for scheduling a downlink new transmission or a downlink retransmission.

Optionally, the downlink dynamic scheduling signaling and the first DCI are carried in one PDCCH, where the new data in the first DCI indicates that the NDI bit is flipped to indicate that the downlink dynamic scheduling signaling is used for scheduling downlink new transmission, and the NDI bit in the first DCI is not flipped to indicate that the downlink dynamic scheduling signaling is used for scheduling downlink retransmission.

Optionally, the uplink dynamic scheduling signaling is used for scheduling uplink new transmission or uplink retransmission.

Optionally, the MAC PDU received on the downlink pre-configured resource is a downlink newly transmitted MAC PDU.

Optionally, the terminal device 300 further includes:

a communication unit 320, configured to receive a first PDCCH, where the first PDCCH includes a first downlink scheduling signaling and a third DCI, where the first downlink scheduling signaling is used to schedule downlink retransmission, and an HARQ process indicated in the third DCI is an HARQ process with a feedback function turned off;

the processing unit 310 is further configured to start or restart the DRX inactivity timer after the communication unit receives the first PDCCH.

Optionally, the processing unit 310 is specifically configured to:

the DRX inactivity timer is started or restarted when the communication unit 320 has finished receiving the first PDCCH.

Optionally, the MAC PDU sent on the uplink pre-configured resource is an uplink newly transmitted MAC PDU.

Optionally, the terminal device 300 further includes:

a communication unit 320, configured to receive a second PDCCH, where the second PDCCH includes a first uplink scheduling signaling and a fourth DCI, where the first uplink scheduling signaling is used to schedule uplink retransmission, and a HARQ process indicated in the fourth DCI is a HARQ process with a feedback function being turned off;

the processing unit 310 is further configured to start or restart the DRX inactivity timer after the communication unit 320 receives the second PDCCH.

Optionally, the processing unit 310 is specifically configured to:

the DRX inactivity timer is started or restarted when the communication unit 320 has finished receiving the second PDCCH.

Alternatively, the terminal device 300 is applied to NTN.

It should be understood that the terminal device 300 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 and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.

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

Optionally, as shown in fig. 8, the communication device 400 may also include a memory 420. From the memory 420, the processor 410 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 420 may be a separate device from the processor 410, or may be integrated into the processor 410.

Optionally, as shown in fig. 8, the communication device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 430 may include a transmitter and a receiver, among others. The transceiver 430 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 400 may specifically be a network device or a base station in the embodiment of the present application, and the communication device 400 may implement a corresponding procedure implemented by the network device or the base station in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the communication device 400 may specifically be a mobile terminal/terminal device in the embodiment of the present application, and the communication device 400 may implement a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Fig. 9 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 500 shown in fig. 9 includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 9, the apparatus 500 may further include a memory 520. From the memory 520, the processor 510 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 520 may be a separate device from the processor 510, or may be integrated into the processor 510.

Optionally, the apparatus 500 may further comprise an input interface 530. The processor 510 may control the input interface 530 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the apparatus 500 may further comprise an output interface 540. The processor 510 may control the output interface 540 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.

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

Optionally, the apparatus may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

Alternatively, the device mentioned in the embodiments of the present application may also be a chip. For example, it may be a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 10 is a schematic block diagram of a communication system 600 provided in an embodiment of the present application. As shown in fig. 10, the communication system 600 includes a terminal device 610 and a network device 620.

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

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

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

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

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

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

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

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

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

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

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device or the base station in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute corresponding processes implemented by the network device or the base station in the methods in the embodiment of the present application, which is not described herein again for brevity.

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

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

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

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

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

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. With regard to such understanding, the technical solutions of the present application may be essentially implemented or contributed to by the prior art, or may be implemented in a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

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

Claims

A method of wireless communication, comprising:

for a hybrid automatic repeat request HARQ process with the feedback function turned off, the terminal device starts or restarts a discontinuous reception DRX inactivity timer after performing a first operation, wherein,

the first operation includes at least one of:

receiving a downlink dynamic scheduling signaling, receiving an uplink dynamic scheduling signaling, receiving a media access control protocol data unit (MAC PDU) on a downlink pre-configured resource, and sending the MAC PDU on an uplink pre-configured resource.
The method of claim 1, further comprising:

and the terminal equipment does not start or close a first timer and/or a second timer corresponding to the HARQ process after executing the first operation, wherein the duration of the first timer is one round trip transmission time (RTT) in DRX, the second timer is a timer aiming at retransmission in DRX, and the terminal equipment does not monitor a Physical Downlink Control Channel (PDCCH) during the running period of the first timer and/or the second timer.
The method according to claim 1 or 2, wherein the terminal device starts or restarts a DRX inactivity timer after performing the first operation, comprising:

and the terminal equipment starts or restarts the DRX inactivity timer when the terminal equipment finishes the first operation.
The method according to any one of claims 1 to 3, further comprising:

the terminal equipment determines the HARQ process with the feedback function closed.
The method of claim 4, further comprising:

the terminal equipment receives first configuration information, wherein the first configuration information is used for indicating that part or all of HARQ processes close a feedback function;

the determining, by the terminal device, the HARQ process with the feedback function turned off includes:

and the terminal equipment determines the HARQ process with the feedback function closed according to the first configuration information.
The method according to any one of claims 1 to 5, wherein the downlink dynamic scheduling signaling is used for scheduling a downlink new transmission or a downlink retransmission.
The method of claim 6, wherein the downlink dynamic scheduling signaling and a first Downlink Control Information (DCI) are carried in one PDCCH, wherein a New Data Indication (NDI) bit in the first DCI is toggled to indicate that the downlink dynamic scheduling signaling is used for scheduling a downlink new transmission, and wherein the NDI bit in the first DCI is not toggled to indicate that the downlink dynamic scheduling signaling is used for scheduling a downlink retransmission.
The method according to any of claims 1 to 5, wherein the uplink dynamic scheduling signaling is used for scheduling uplink new transmission or uplink retransmission.
The method of claim 8, wherein the uplink dynamic scheduling signaling and the second DCI are carried in one PDCCH, wherein an NDI bit in the second DCI is toggled to indicate that the uplink dynamic scheduling signaling is used for scheduling an uplink new transmission, and wherein an NDI bit in the second DCI is not toggled to indicate that the uplink dynamic scheduling signaling is used for scheduling an uplink retransmission.
The method according to any of claims 1 to 5, wherein the MAC PDU received on the downlink pre-configured resource is a downlink newly transmitted MAC PDU.
The method of claim 10, further comprising:

the terminal equipment receives a first PDCCH, wherein the first PDCCH comprises a first downlink scheduling signaling and a third DCI, the first downlink scheduling signaling is used for scheduling downlink retransmission, and an HARQ process indicated in the third DCI is an HARQ process with a feedback function closed;

the terminal device starts or restarts the DRX inactivity timer after receiving the first PDCCH.
The method of claim 11, wherein the terminal device starts or restarts the DRX inactivity timer after receiving the first PDCCH, comprising:

and the terminal equipment starts or restarts the DRX inactivity timer when receiving the first PDCCH.
The method according to any of claims 1 to 5, wherein the MAC PDU sent on the upstream pre-configured resource is an upstream newly transmitted MAC PDU.
The method of claim 13, further comprising:

the terminal equipment receives a second PDCCH, wherein the second PDCCH comprises a first uplink scheduling signaling and a fourth DCI, the first uplink scheduling signaling is used for scheduling uplink retransmission, and an HARQ process indicated in the fourth DCI is an HARQ process with a feedback function closed;

the terminal device starts or restarts the DRX inactivity timer after receiving the second PDCCH.
The method of claim 14, wherein the terminal device starts or restarts the DRX inactivity timer after receiving the second PDCCH, comprising:

and the terminal equipment starts or restarts the DRX inactivity timer when receiving the second PDCCH.
The method according to any of claims 1 to 15, applied to a non-terrestrial communication network, NTN.
A terminal device, comprising: a processing unit for processing the received data,

for a hybrid automatic repeat request, HARQ, process with the feedback function turned off, the processing unit starts or restarts a discontinuous reception, DRX, inactivity timer after performing a first operation, wherein,

the first operation includes at least one of:

receiving a downlink dynamic scheduling signaling, receiving an uplink dynamic scheduling signaling, receiving a media access control protocol data unit (MAC PDU) on a downlink pre-configured resource, and sending the MAC PDU on an uplink pre-configured resource.
The terminal device according to claim 17, wherein the processing unit is further configured to not start or close a first timer and/or a second timer corresponding to the HARQ process after performing the first operation, a duration of the first timer is one round trip transmission time RTT in DRX, the second timer is a timer for retransmission in DRX, and the terminal device does not monitor a physical downlink control channel PDCCH during operation of the first timer and/or the second timer.
The terminal device according to claim 17 or 18, wherein the processing unit is specifically configured to:

starting or restarting the DRX inactivity timer when the first operation is performed.
The terminal device according to any of claims 17 to 19, wherein the processing unit is further configured to determine the HARQ process with the feedback function turned off.
The terminal device of claim 20, wherein the terminal device further comprises:

a communication unit, configured to receive first configuration information, where the first configuration information is used to indicate that a part or all of HARQ processes close a feedback function;

the processing unit is specifically configured to:

determining the HARQ process with the feedback function closed according to the first configuration information.
The terminal device according to any of claims 17 to 21, wherein the downlink dynamic scheduling signaling is used to schedule a downlink new transmission or a downlink retransmission.
The terminal device of claim 22, wherein the downlink dynamic scheduling signaling and a first Downlink Control Information (DCI) are carried in one PDCCH, wherein a New Data Indication (NDI) bit in the first DCI is toggled to indicate that the downlink dynamic scheduling signaling is used for scheduling a downlink new transmission, and wherein the NDI bit in the first DCI is not toggled to indicate that the downlink dynamic scheduling signaling is used for scheduling a downlink retransmission.
The terminal device according to any one of claims 17 to 21, wherein the uplink dynamic scheduling signaling is used for scheduling an uplink new transmission or an uplink retransmission.
The terminal device of claim 24, wherein the uplink dynamic scheduling signaling and the second DCI are carried in one PDCCH, an NDI bit in the second DCI is flipped to indicate that the uplink dynamic scheduling signaling is used to schedule an uplink new transmission, and an NDI bit in the second DCI is not flipped to indicate that the uplink dynamic scheduling signaling is used to schedule an uplink retransmission.
A terminal device according to any of claims 17 to 21, wherein the MAC PDU received on the downlink pre-configured resource is a downlink newly transmitted MAC PDU.
The terminal device of claim 26, wherein the terminal device further comprises:

a communication unit, configured to receive a first PDCCH, where the first PDCCH includes a first downlink scheduling signaling and a third DCI, where the first downlink scheduling signaling is used to schedule downlink retransmission, and an HARQ process indicated in the third DCI is an HARQ process with a feedback function turned off;

the processing unit is further configured to start or restart the DRX inactivity timer after the communication unit receives the first PDCCH.
The terminal device of claim 27, wherein the processing unit is specifically configured to:

starting or restarting the DRX inactivity timer when the communication unit finishes receiving the first PDCCH.
The terminal device according to any of claims 17 to 21, wherein the MAC PDU sent on the uplink pre-configured resource is an uplink newly transmitted MAC PDU.
The terminal device of claim 29, wherein the terminal device further comprises:

a communication unit, configured to receive a second PDCCH, where the second PDCCH includes a first uplink scheduling signaling and a fourth DCI, where the first uplink scheduling signaling is used to schedule uplink retransmission, and an HARQ process indicated in the fourth DCI is an HARQ process with a feedback function turned off;

the processing unit is further configured to start or restart the DRX inactivity timer after the communication unit receives the second PDCCH.
The terminal device of claim 30, wherein the processing unit is specifically configured to:

starting or restarting the DRX inactivity timer when the communication unit finishes receiving the second PDCCH.
The terminal device according to any of claims 17 to 31, wherein the terminal device is applied to a non-terrestrial communication network (NTN).
A terminal device, comprising: a processor and a memory, the memory for storing a computer program, the processor for invoking and executing the computer program stored in the memory, performing the method of any one of claims 1 to 16.
An apparatus, comprising: a processor for calling and running a computer program from a memory to cause a device in which the apparatus is installed to perform the method of any one of claims 1 to 16.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 16.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 16.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 16.