CN113728697B

CN113728697B - Wireless communication method and terminal device

Info

Publication number: CN113728697B
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: 2024-03-08
Anticipated expiration: 2039-09-25
Also published as: CN113728697A; WO2021056226A1

Abstract

The embodiment of the application provides a wireless communication method and terminal equipment, wherein for an HARQ process with a feedback function being closed, the terminal equipment starts or restarts a DRX (discontinuous reception) non-activated timer after dynamically scheduling uplink transmission, dynamically scheduling downlink transmission, pre-configured resource uplink transmission and pre-configured resource uplink downlink transmission, so that the terminal equipment can monitor PDCCH after executing the operations, and the terminal equipment can continuously schedule retransmission or continuous reception of new transmission to network equipment in an NTN (network termination network) network. The wireless communication method comprises the following steps: 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 downlink dynamic scheduling signaling, receiving uplink dynamic scheduling signaling, receiving MAC PDUs on downlink pre-configured resources, and transmitting MAC PDUs on uplink pre-configured resources.

Description

Wireless communication method and terminal device

Technical Field

The embodiments of the present application relate to the field of communications, and more particularly, to a wireless communication method and a terminal device.

Background

The new wireless (5-Generation New Radio,5G NR) system of the fifth generation mobile communication technology defines a Non-terrestrial network (Non-terrestrial networks, NTN) system deployment scenario including a satellite network, and the NTN system can implement continuity of the 5G NR service by means of wide area coverage capability of the satellite. 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, so that in order to ensure the data transmission continuity under the condition of not increasing the number of hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) processes, a higher requirement is put forward on the HARQ scheme in the NTN system, and how to ensure the data transmission continuity under the condition of not increasing the number of HARQ processes is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and terminal equipment, wherein for an HARQ process with a feedback function being closed, the terminal equipment starts or restarts a discontinuous reception (Discontinuous Reception, DRX) inactivity timer after dynamically scheduling uplink transmission, dynamically scheduling downlink transmission, pre-configuring resource uplink and downlink transmission, so that the terminal equipment can monitor a physical downlink control channel (Physical Downlink Control Channel, PDCCH) after executing the operations, and is convenient for continuously scheduling retransmission or continuous reception of retransmission to network equipment in an NTN network.

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

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

the first operation includes at least one of:

receiving downlink dynamic scheduling signaling, receiving uplink dynamic scheduling signaling, receiving media access control protocol data units (Media Access Control Protocol Data Unit, MAC PDUs) on downlink pre-configured resources, and transmitting MAC PDUs on uplink pre-configured resources.

The above-mentioned receiving of the MAC PDU on the downlink pre-configured resource may be receiving of the downlink data on the downlink pre-configured resource, and the above-mentioned transmitting of the MAC PDU on the uplink pre-configured resource may be transmitting of the uplink data on the uplink pre-configured resource.

In a second aspect, a terminal device is provided for performing the method of the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a third aspect, a terminal device is provided comprising 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 various implementation manners thereof.

In a fourth aspect, there is provided an apparatus for implementing the method of the first aspect or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in the first aspect or implementations thereof described above.

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

In a sixth aspect, a computer program product is provided, comprising computer program instructions for causing a computer to perform the method of the first aspect or implementations thereof.

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

By the technical scheme, for the HARQ process with the feedback function closed, the terminal equipment starts or restarts the DRX inactivity timer after the first operation is executed, so that the terminal equipment can monitor the PDCCH continuously after the first operation is executed, 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 of an uplink pre-configured resource according to an embodiment of the present application.

Fig. 6 is a schematic diagram of uplink and downlink transmission of a downlink pre-configured resource according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a terminal device 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 in accordance with 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

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The embodiments of the present application may be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system over unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system over unlicensed spectrum, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), next generation communication system or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, and the like, to which the embodiments of the present application can also be applied.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

The frequency spectrum of the application in the embodiments of the present application is not limited. For example, embodiments of the present application may be applied to licensed spectrum as well as unlicensed spectrum.

Exemplary, a communication system 100 to which embodiments of the present application apply 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, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment 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 with communication functions, where the network device 110 and the terminal device 120 may be 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 a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

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

Embodiments of the present application describe various embodiments in connection with a terminal device and a network device, wherein: a terminal device may also be called 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, a User device, or the like. The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication functionality, 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, such as a terminal device in an NR network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The 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 can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

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

In the embodiment of the present application, the network device provides services for a cell, and the 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 may belong to 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 transmitting power and are suitable for providing high-rate data transmission services.

The 5G NR system defines an NTN system deployment scenario including a satellite network. NTN typically provides communication services to terrestrial users by way of satellite communications. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communications are not limited by the user region, for example, general land communications cannot cover areas where communication devices cannot be installed, such as oceans, mountains, deserts, etc., or communication coverage is not performed due to rarity of population, while for satellite communications, since one satellite can cover a larger ground, and the satellite can orbit around the earth, theoretically every corner on the earth can be covered by satellite communications. And secondly, satellite communication has great social value. Satellite communication can be covered in remote mountain areas, poor and backward countries or regions with lower cost, so that people in the regions enjoy advanced voice communication and mobile internet technology, and the digital gap between developed regions is reduced, and the development of the regions is promoted. Again, the satellite communication distance is far, 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 (Geostationary Earth Orbit, GEO) satellites, high elliptical Orbit (High Elliptical Orbit, HEO) satellites, and the like according to the Orbit heights.

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 single hop communications between users is typically less than 20ms. The maximum satellite visibility time is 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.

For another example, the GEO satellite orbit altitude is 35786km and the period of rotation around the earth is 24 hours. The signal propagation delay for single hop communications between users is typically 250ms.

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

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

The conditions for starting and stopping drx-retransmission timerdl of the terminal are as follows:

when the terminal equipment receives a PDCCH indicating downlink transmission or the terminal receives a MAC PDU on the configured downlink grant resource, the terminal stops the drx-retransmission timer DL corresponding to the HARQ process. After completing the transmission fed back by the HARQ process for the downlink transmission, the terminal starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process.

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

The conditions for starting and stopping drx-retransmission timer UL are as follows:

when the terminal receives a PDCCH indicating uplink transmission or when the terminal transmits a MAC PDU on the configured uplink grant resource, the terminal stops the drx-retransmission timer UL corresponding to the HARQ process. After finishing the first repetition transmission (repetition) of the PUSCH, the terminal starts the drx-HARQ-RTT-timerl corresponding to the HARQ process.

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

Compared with the 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 data transmission continuity without increasing the number of HARQ processes, a scheme for starting or stopping the HARQ can be designed.

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

In case of closing the 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 feedback for HARQ is not available, the network device may continue to schedule retransmission of uplink transmission or downlink transmission before receiving feedback for uplink transmission or downlink transmission of the terminal device. For the terminal equipment, for uplink data transmission, the terminal equipment can continue to receive uplink retransmission scheduling after the current uplink transmission is sent; for downlink data transmission, the terminal device may continue to receive downlink retransmission schedule before decoding the current downlink transmission is completed. Thus, the uplink discontinuous reception HARQ round trip transmission time timer (Uplink Discontinuous Reception HARQ round trip time Timer, drx-HARQ-RTT-timertl) and the downlink discontinuous reception HARQ round trip transmission time timer (Downlink Discontinuous Reception HARQ round trip time Timer, drx-HARQ-RTT-timertl) may no longer be needed in case HARQ is turned off. Meanwhile, the terminal equipment does not need to wait for the network side to process the receiving situation and schedule the retransmission, so that an uplink discontinuous receiving retransmission timer (Uplink Discontinuous Reception Retransmission Timer, drx-retransmission timer ul) and a downlink discontinuous receiving retransmission timer (Downlink Discontinuous Reception Retransmission Timer, drx-retransmission timer dl) are not needed, that is, the retransmission scheduling at the network side can be a feedback of Acknowledgement (ACK) or negative Acknowledgement (Negative Acknowledgement, NACK) or a receiving moment of uplink data transmission earlier than the network side.

Aiming at the technical problems, the application designs a scheme for discontinuous reception of a physical downlink control channel (Physical Downlink Control Channel, PDCCH) by terminal equipment under the condition of closing HARQ feedback. Aiming at the HARQ process for closing the HARQ feedback function, by closing the DRX-HARQ-RTT-TimerUL, the DRX-HARQ-RTT-TimerDL and the DRX-retransmission TimerUL, the terminal equipment does not wait for the data packet detection result of the network side any more, and by introducing the restart of a discontinuous reception (Discontinuous Reception) and DRX inactivity timer, the terminal equipment can be ensured to continuously monitor the PDCCH after dynamically scheduling uplink/downlink transmission and preconfigured uplink/downlink transmission, and the terminal equipment can continuously schedule retransmission or new continuous reception of the network equipment in the NTN network.

The following describes in detail a scheme of the terminal device discontinuously receiving PDCCH in the case of closing HARQ feedback, which is designed for the above technical problem in the present application.

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

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

the first operation includes at least one of:

receiving downlink dynamic scheduling signaling, receiving uplink dynamic scheduling signaling, receiving MAC PDUs on downlink pre-configured resources, and transmitting MAC PDUs on uplink pre-configured resources.

The terminal device listens to the PDCCH during the operation of the DRX inactivity timer (DRX inactivity timer).

In the embodiment of the present application, for the HARQ process with the feedback function turned off, the terminal device does not wait for the data packet detection result of the network side after executing the first operation, but starts or restarts the DRX inactivity timer after executing the first operation, so that the terminal device is guaranteed to be able to dynamically schedule uplink transmission, dynamically schedule downlink transmission, receive MAC PDUs on the downlink pre-configured resource, or be able to continue to monitor PDCCH after sending MAC PDUs on the uplink pre-configured resource, so that the terminal device is able to continuously schedule retransmission or continuous reception of new transmission to the network in the NTN network.

Alternatively, the method 200 may be applied to NTN. I.e. embodiments of the present application may be applied to NTN.

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

Optionally, in this embodiment of the present 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, where 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-timerl 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 for the terminal device to transmit from the uplink to the reception of the retransmission schedule issued by the network.

For example, for new transmission or retransmission of downlink data, after the feedback of the downlink HARQ process is completed, the drx-HARQ-RTT-TimerDL corresponding to the HARQ process is started.

For another example, for new transmission or retransmission of uplink data, the drx-HARQ-RTT-timer ul corresponding to the uplink HARQ process is started after the feedback of this HARQ process is completed.

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 the embodiment of the present application, the terminal device starts or restarts the DRX inactivity timer when the first operation is performed. I.e. the terminal device starts or restarts the DRX inactivity timer immediately after the first operation is performed.

Optionally, in an 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 the embodiment of the present application, before executing the above step S210, the terminal device first needs to determine the HARQ process with the feedback function turned off.

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

For example, the terminal device receives first configuration information sent by the 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 master configuration (Media Access Control main, MAC main) information.

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

Optionally, the network device may further configure relevant parameters of DRX, including a DRX cycle (DRX cycle), a DRX state duration timer (DRX-onduration timer), a DRX inactivity timer (DRX-inactivity timer), an uplink DRX HARQ RTT timer (DRX-HARQ-RTT-timer ul), a downlink DRX HARQ RTT timer (DRX-HARQ-RTT-timer dl), an uplink DRX retransmission timer (DRX-retransmission timer ul), a downlink DRX retransmission timer (DRX-retransmission timer dl), 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 the embodiment of the present application, the downlink dynamic scheduling signaling is used to schedule downlink new transmission or downlink retransmission. I.e. the first operation is for scheduling a downlink new transmission or a downlink retransmission when the first operation is downlink dynamic scheduling signaling.

Optionally, the downlink dynamic scheduling signaling and first downlink control information (Downlink Control Information, DCI) are carried in one PDCCH, a new data indication (New Data Indicator, NDI) bit in the first DCI is toggled to indicate that the downlink dynamic scheduling signaling is used to schedule a downlink new transmission, and an NDI bit in the first DCI is not toggled to indicate that the downlink dynamic scheduling signaling is used to schedule a downlink retransmission.

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

Optionally, the uplink dynamic scheduling signaling and the second DCI are carried in one PDCCH, and NDI bits in the second DCI are flipped to indicate that the uplink dynamic scheduling signaling is used to schedule uplink new transmissions, and NDI bits in the second DCI are not flipped to indicate that the uplink dynamic scheduling signaling is used to schedule uplink retransmissions.

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

Optionally, if the first operation is to receive a MAC PDU on a downlink pre-configured 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 with a feedback function being turned off; and the terminal device starts or restarts the DRX inactivity timer after receiving the first PDCCH.

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

Optionally, in the embodiment of the present application, the MAC PDU sent on the uplink pre-configured resource is an uplink new MAC PDU.

Optionally, if the first operation is a MAC PDU sent on an uplink pre-configured 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 an HARQ process indicated in the fourth DCI is an HARQ process with a feedback function being turned off; and the terminal device starts or restarts the DRX inactivity timer after receiving the second PDCCH.

Specifically, when the terminal device receives the second PDCCH, the terminal device starts or restarts the DRX inactivity timer. 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 way of 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 configured to configure relevant parameters of DRX and relevant configuration information of a downlink HARQ process, where relevant parameters of DRX include DRX cycle, DRX-onduration timer, DRX-inactivity timer, DRX-HARQ-RTT-timer dl, DRX-retransmission timer dl, and so on; the downlink HARQ process related configuration information includes configuring 2 DL HARQ processes, where the HARQ feedback function of HARQ ID 1 is on and the HARQ feedback function of HARQ ID 0 is off.

It should be noted that, the timer 1 in fig. 3 may be drx-onduration timer, the timer 2 in fig. 3 may be drx-incarvitytimer, the timer 3 in fig. 3 may be drx-HARQ-RTT-timer dl, and the timer 4 in fig. 3 may be drx-retransmission timer dl.

As shown in fig. 3, the terminal device receives a new transmission of a PDCCH indicating TB1 during the operation of the timer 1, uses HARQ ID 0, and starts the timer 2 after the terminal device completes the PDCCH reception. The terminal device then receives 2 PDCCH indicating retransmissions of transport block (Transmission block, TB) 1 in turn, and the terminal device restarts timer 2 after each reception of PDCCH indicating a TB1 retransmission schedule.

As shown in fig. 3, the terminal device receives a new transmission of a PDCCH indicating TB2 during the operation of timer 1, uses HARQ ID 1, receives a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) on a resource indicated by the PDCCH, starts a timer 3 corresponding to HARQ ID 1 after completing ACK feedback received for the PDSCH, and starts a timer 4 corresponding to HARQ ID 1 after the timer 3 expires.

Optionally, as embodiment 2, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically configured to configure relevant parameters of DRX and relevant configuration information of an uplink HARQ process, where relevant parameters of DRX include DRX cycle, DRX-onduration timer, DRX-inactivity timer, DRX-HARQ-RTT-timer ul, DRX-retransmission timer ul, 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 on and the HARQ feedback function of HARQ ID 0 is off.

It should be noted that, the timer 1 in fig. 4 may be drx-onduration timer, the timer 2 in fig. 4 may be drx-incarvitytimer, the timer 5 in fig. 4 may be drx-HARQ-RTT-timer ul, and the timer 6 in fig. 4 may be drx-retransmission timer ul.

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

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 (Physical Uplink Shared Channel, PUSCH) on the resource indicated by the PDCCH, and starts a timer 5 corresponding to HARQ ID 1 after completing the transmission for the PUSCH, and starts a timer 6 corresponding to HARQ ID 1 after the timer 5 expires.

Optionally, as embodiment 3, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically configured to configure relevant parameters of DRX and relevant configuration information of an uplink HARQ process, where relevant parameters of DRX include DRX cycle, DRX-onduration timer, DRX-inactivity timer, DRX-HARQ-RTT-timer ul, DRX-retransmission timer ul, 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 on and the HARQ feedback function of HARQ ID 0 is off.

It should be noted that, the timer 1 in fig. 5 may be drx-onduration timer, the timer 2 in fig. 5 may be drx-incarvitytimer, the timer 5 in fig. 5 may be drx-HARQ-RTT-timer ul, and the timer 6 in fig. 5 may be drx-retransmission timer ul.

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

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

Optionally, as embodiment 4, the terminal device receives RRC configuration information sent by the network device, where the RRC configuration information is specifically configured to configure relevant parameters of DRX and relevant configuration information of a downlink HARQ process, where relevant parameters of DRX include DRX cycle, DRX-onduration timer, DRX-inactivity timer, DRX-HARQ-RTT-timer dl, DRX-retransmission timer dl, and so on; the downlink HARQ process related configuration information includes configuring 2 DL HARQ processes, where the HARQ feedback function of HARQ ID 1 is on and the HARQ feedback function of HARQ ID 0 is off.

It should be noted that, the timer 1 in fig. 6 may be drx-onduration timer, the timer 2 in fig. 6 may be drx-incarvitytimer, the timer 3 in fig. 6 may be drx-HARQ-RTT-timer dl, and the timer 4 in fig. 6 may be drx-retransmission timer dl.

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

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

Therefore, in the embodiment of the present application, for the HARQ process with the feedback function turned off, the terminal device does not wait for the data packet detection result on the network side after executing the first operation, but starts or restarts the DRX inactivity timer after executing the first operation, so that it is ensured that the terminal device can dynamically schedule uplink transmission, dynamically schedule downlink transmission, receive MAC PDUs on the downlink pre-configured resource, or can continue to monitor PDCCH after sending MAC PDUs on the uplink pre-configured resource, so that the terminal device can continuously schedule retransmission or continuous reception of new transmission to the network in the NTN network.

Fig. 7 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in fig. 7, the terminal device 300 includes: the processing unit 310 is configured to process the data,

for HARQ processes with the feedback function turned off, the processing unit 310 starts or restarts a DRX inactivity timer after performing the 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 the first operation is performed, 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:

when the first operation is performed, the DRX inactivity timer is started or restarted.

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

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 a part or all of HARQ processes close a feedback function;

the processing unit 310 specifically is 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 to schedule downlink new transmission or downlink retransmission.

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

Optionally, the uplink dynamic scheduling signaling is used to schedule uplink new transmissions or uplink retransmissions.

Optionally, the MAC PDU received on the downlink pre-configured resource is a downlink new 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 being 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:

when the communication unit 320 receives the first PDCCH, the DRX inactivity timer is started or restarted.

Optionally, the MAC PDU sent on the uplink pre-configured resource is an uplink new 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 an indicated HARQ process in the fourth 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 320 receives the second PDCCH.

Optionally, the processing unit 310 is specifically configured to:

when the communication unit 320 receives the second PDCCH, the DRX inactivity timer is started or restarted.

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 foregoing 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, which is not described herein for brevity.

Fig. 8 is a schematic structural diagram of a communication device 400 provided in an embodiment of the present application. The communication device 400 shown in fig. 8 comprises a processor 410, from which the processor 410 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 8, the communication device 400 may also include a memory 420. Wherein the processor 410 may call and run a computer program from the memory 420 to implement the methods in embodiments of the present application.

Wherein 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 in particular, may send information or data to other devices, or receive information or data sent by other devices.

Among other things, transceiver 430 may include a transmitter and a receiver. Transceiver 430 may further include antennas, the number of which may be one or more.

Optionally, the communication device 400 may be specifically a network device or a base station in the embodiment of the present application, and the communication device 400 may implement a corresponding flow implemented by the network device or the base station in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 400 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 400 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 9, the apparatus 500 may further comprise a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the methods in embodiments of the present application.

Wherein 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 sent by other devices or chips.

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

Optionally, the apparatus may be applied to a network device or a base station in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the network device or the base station in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Fig. 10 is a schematic block diagram of a communication system 600 provided by 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 used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 620 may be used to implement the corresponding functions implemented by the network device or the base station in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks 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 a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct 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 memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

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

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein 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 a network device or a base station in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding flows implemented by the network device or the base station in the methods in the embodiments of the present application, which are not described herein for brevity.

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

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device or a base station in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device or the base station in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely 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 think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to 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

1. A method of wireless communication, comprising:

the method comprises the steps that terminal equipment receives first configuration information, wherein the first configuration information is used for indicating that a part or all of hybrid automatic repeat request (HARQ) processes close a feedback function;

the terminal equipment determines an HARQ process with a feedback function closed according to the first configuration information;

for a HARQ process determined to have 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 media access control protocol data unit, MAC PDU, on the downlink pre-configured resource and transmitting the MAC PDU on the uplink pre-configured resource.

2. The method according to claim 1, wherein the method further comprises:

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, the duration of the first timer is one round trip transmission time RTT in the DRX, the second timer is a timer aiming at retransmission in the DRX, and the terminal equipment does not monitor a physical downlink control channel PDCCH during the operation of the first timer and/or the second timer.

3. The method of claim 1, wherein the terminal device starts or restarts a DRX inactivity timer after performing the first operation, comprising:

and when the terminal equipment finishes the first operation, starting or restarting the DRX inactivity timer.

4. A method according to any of claims 1 to 3, characterized in that the MAC PDU received on the downlink pre-configured resource is a downlink new MAC PDU.

5. The method according to claim 4, wherein the method further comprises:

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 closed feedback function;

The terminal device starts or restarts the DRX inactivity timer after receiving the first PDCCH.

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

and when the terminal equipment receives the first PDCCH, starting or restarting the DRX inactivity timer.

7. A method according to any of claims 1 to 3, characterized in that the MAC PDU sent on the uplink pre-configured resource is an uplink new MAC PDU.

8. The method of claim 7, wherein the method further comprises:

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 the HARQ process indicated in the fourth DCI is the HARQ process with the feedback function closed;

the terminal device starts or restarts the DRX inactivity timer after receiving the second PDCCH.

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

And when the terminal equipment receives the second PDCCH, starting or restarting the DRX inactivity timer.

10. A method according to any of claims 1 to 3, characterized in that the method is applied to a non-terrestrial communication network NTN.

11. A terminal device, comprising: a communication unit and a processing unit,

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

the processing unit is used for determining an HARQ process with a feedback function closed according to the first configuration information;

for a HARQ process determined to have the feedback function turned off, the processing unit starts or restarts a discontinuous reception, DRX, inactivity timer after performing the first operation, wherein,

the first operation includes at least one of:

12. The terminal device according to claim 11, 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, where 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.

13. The terminal device according to claim 11, wherein the processing unit is specifically configured to:

and starting or restarting the DRX inactivity timer when the first operation is performed.

14. The terminal device according to any of the claims 11 to 13, characterized in that the MAC PDU received on the downlink pre-configured resource is a downlink new MAC PDU.

15. The terminal device according to claim 14, characterized in that 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.

16. The terminal device according to claim 15, wherein the processing unit is specifically configured to:

and when the communication unit receives the first PDCCH, starting or restarting the DRX inactivity timer.

17. The terminal device according to any of the claims 11 to 13, characterized in that the MAC PDU sent on the uplink pre-configured resource is an uplink new MAC PDU.

18. The terminal device according to claim 17, characterized in that 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.

19. The terminal device according to claim 18, wherein the processing unit is specifically configured to:

and when the communication unit receives the second PDCCH, starting or restarting the DRX inactivity timer.

20. Terminal device according to any of the claims 11 to 13, characterized in that the terminal device is applied to a non-terrestrial communication network NTN.

21. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 10.

22. A wireless communications apparatus, comprising: a processor for invoking and running a computer program from memory to cause a device in which the wireless communication apparatus is installed to perform the method of any of claims 1-10.

23. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 10.