Wireless communication method, terminal device and network device

CN118923066APending Publication Date: 2024-11-08GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094047.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-06-24
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Under different modes of the HARQ process, it is difficult for the existing technology to effectively adjust the DRX behavior of the terminal device, resulting in poor scheduling performance and difficulty in balancing power saving.

Method used

By distinguishing the first mode and the second mode in the HARQ process, the DRX behavior of the terminal device is determined according to the mode of the HARQ process, including starting different timers to control the monitoring timing of the PDCCH, ensuring better scheduling in different modes. performance and power saving.

Benefits of technology

It achieves optimized DRX behavior in different modes of the HARQ process, improves scheduling performance, and takes into account battery life on terminal devices to ensure good performance in different scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923066A_ABST
    Figure CN118923066A_ABST
Patent Text Reader

Abstract

A wireless communication method, a terminal device and a network device, the method comprising: a terminal device receiving a first PDCCH, the first PDCCH being used for scheduling a first TB, the first TB corresponding to a first HARQ process; the terminal device determines the DRX behavior of the terminal device according to a mode corresponding to the first HARQ process, the mode corresponding to the first HARQ process comprises a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors. According to the method and the device, the influence of different modes of the HARQ on the DRX behaviors is considered, the different DRX behaviors can be determined according to the different modes corresponding to the HARQ process, and the PDCCH is monitored at the proper time, so that the better scheduling performance can be realized when the HARQ process is in the different modes, and the power saving of the terminal equipment can be considered.
Need to check novelty before this filing date? Find Prior Art

Description

Wireless communication method, terminal device, and network device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] When a terminal device is configured with a discontinuous reception (DRX) function, the terminal device may monitor the physical downlink control channel (PDCCH) discontinuously to save power for the terminal device.

[0003] In some communication systems, the modes of a hybrid automatic repeat request (HARQ) process may include a first mode and a second mode. Taking a downlink HARQ process as an example, the first mode may be that the HARQ process performs HARQ feedback, and the second mode may be that the HARQ process does not perform HARQ feedback.

[0004] Summary of the Invention

[0005] The present application provides a wireless communication method, a terminal device, and a network device. The following introduces various aspects of the present application.

[0006] In a first aspect, a wireless communication method is provided, including: a terminal device receives a first PDCCH, the first PDCCH is used to schedule a first transmission block TB, and the first TB corresponds to a first HARQ process; the terminal device determines the DRX behavior of the terminal device according to a mode corresponding to the first HARQ process, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0007] In a second aspect, a wireless communication method is provided, including: a network device sends a first PDCCH, the first PDCCH is used to schedule a first TB, and the first TB corresponds to a first HARQ process; wherein, the mode corresponding to the first HARQ process is used to determine the DRX behavior of the terminal device, and the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0008] In a third aspect, a terminal device is provided, including: a first receiving unit, used to receive a first PDCCH, the first PDCCH is used to schedule a first TB, and the first TB corresponds to a first HARQ process; a first determination unit, used to determine the DRX behavior of the terminal device according to the mode corresponding to the first HARQ process, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0009] In a fourth aspect, a network device is provided, including: a first sending unit, used to send a first PDCCH, the first PDCCH is used to schedule a first TB, the first TB corresponds to a first HARQ process; the mode corresponding to the first HARQ process is used to determine the DRX behavior of the terminal device, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0010] In a fifth aspect, a terminal is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0011] In the sixth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0012] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal and / or network device. In another possible design, the system may also include other devices that interact with the terminal or network device in the solution provided in the embodiment of the present application.

[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a terminal to execute part or all of the steps in the methods of the above aspects.

[0014] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0015] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0016] This application takes into account the impact of different HARQ modes on DRX behavior, and can determine different DRX behaviors according to the different modes corresponding to the HARQ process, so as to monitor the PDCCH at the appropriate time, so that when the HARQ process is in different modes, it can have better scheduling performance and can take into account the power saving of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a wireless communication system used in an embodiment of the present application.

[0018] FIG. 2 is a schematic diagram of a transparent forwarding network architecture.

[0019] FIG3 is a schematic diagram of a regeneration and forwarding network structure.

[0020] FIG4 is a diagram showing an example of the operation process of the DRX duration timer.

[0021] FIG5 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

[0022] FIG6 is an example diagram of a method for starting a first timer provided in an embodiment of the present application.

[0023] FIG7 is an example diagram of another method for starting a first timer provided in an embodiment of the present application.

[0024] FIG8 is an example diagram of a communication method including step S621 provided in an embodiment of the present application.

[0025] FIG9 is an example diagram of a communication method including step S622 provided in an embodiment of the present application.

[0026] FIG10 is an example diagram of a communication method including step S721 provided in an embodiment of the present application.

[0027] FIG11 is an example diagram of a communication method including step S722 provided in an embodiment of the present application.

[0028] FIG12 is an example diagram of feedback timing for scheduling multiple downlink TBs by the first PDCCH according to an embodiment of the present application.

[0029] FIG13 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

[0030] FIG14 is a schematic structural diagram of a network device provided in an embodiment of the present application.

[0031] FIG15 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The technical solution in this application will be described below with reference to the accompanying drawings.

[0033] Communication System

[0034] Figure 1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0035] FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0036] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0037] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0038] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0039] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0041] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0042] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0043] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0044] Non-terrestrial network (NTN)

[0045] NTN provides communication services to users through non-terrestrial means, such as satellites or UAS platforms.

[0046] Terrestrial network communications are difficult to deploy in locations like oceans, mountains, and deserts. Furthermore, due to the cost of setting up and operating communications equipment, terrestrial communications typically don't cover sparsely populated areas. Compared to terrestrial networks (TNs), NTNs offer many advantages. First, NTNs are not restricted by user location. NTNs are not restricted by geographic location. In theory, satellites orbit the Earth, allowing satellite communications to cover every corner of the globe. Furthermore, NTN equipment can cover areas far larger than those covered by terrestrial equipment. For example, a single satellite can cover a large ground area. Second, NTNs have significant social value. NTNs can achieve coverage at a low cost. For example, satellite communications can cover remote mountainous areas or impoverished and underdeveloped countries or regions. This allows people in these areas to enjoy advanced voice communications and mobile internet technologies, narrowing the digital divide with developed regions and promoting their development. Third, NTNs offer long communication distances without significantly increasing communication costs. Furthermore, NTNs are highly stable. For example, NTN communication is not restricted by natural conditions and can be used even in the event of a natural disaster.

[0047] communications satellites

[0048] According to their orbital altitudes, communication satellites can be divided into low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, geostationary Earth orbit (GEO) satellites, and high elliptical orbit (HEO) satellites. The following is a detailed introduction to LEO satellites and GEO satellites.

[0049] LEO satellites have orbital altitudes ranging from 500 km to 1500 km. Their orbital period is approximately 1.5 to 2 hours. Signal propagation delay for single-hop communication between users is typically less than 20 milliseconds, and the maximum satellite visibility time is 20 minutes. The short signal propagation distance and low link loss reduce the transmit power requirements of user terminals.

[0050] GEO satellites orbit at an altitude of 35,786 km. They orbit the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 milliseconds.

[0051] To ensure satellite coverage and increase the capacity of the entire satellite communication system, satellites can use multiple beams to cover the ground. This means that multiple beam footprints can form a satellite's field of view. For example, a single satellite can generate dozens or even hundreds of beams to cover the ground. A single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0052] Satellite network architecture

[0053] The NTN network can be implemented based on a satellite network architecture, which can include the following network elements: gateway, feeder link, service link, satellite, and inter-satellite link (ISL).

[0054] There can be one or more gateways. A gateway can be used to connect satellites to the terrestrial public network. A gateway is usually located on the ground.

[0055] The feeder link may be a link for communication between the gateway and the satellite.

[0056] The service link may be a link for communication between the terminal device and the satellite.

[0057] Satellite network structures can be divided into transparent payload network architecture and regenerative payload network architecture based on the functions they provide.

[0058] Figure 2 is a schematic diagram of a transparent forwarding network architecture. This architecture can provide wireless frequency filtering, frequency conversion, and amplification. It only transparently forwards signals without changing the waveform of the forwarded signal.

[0059] Figure 3 is a schematic diagram of a regenerative forwarding network architecture. This architecture can provide radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, routing / conversion, and encoding / modulation. In this architecture, satellites can perform some or all of the functions of a base station. Intersatellite links can exist within this architecture.

[0060] Discontinuous reception (DRX)

[0061] In some communication systems (eg, LTE systems), network equipment may configure a DRX function for a terminal device. When the terminal device is configured with the DRX function, the terminal device may monitor the PDCCH discontinuously to save power for the terminal device.

[0062] Each medium access control (MAC) entity can have a DRX configuration. The DRX configuration parameters include one or more of the following: DRX cycle (drx cycle), DRX duration timer (drx-onDurationTimer), delay for the terminal device to start the DRX duration timer (drx-StartOffset), DRX inactivity timer (drx-InactivityTimer), DRX retransmission timer (drx-RetransmissionTimer), DRX uplink retransmission timer (drx-ULRetransmissionTimer). It should be noted that in some embodiments, the DRX retransmission timer may refer to the downlink DRX retransmission timer (drx-RetransmissionTimerDL).

[0063] If the terminal device is configured with DRX, the terminal needs to monitor the PDCCH during the DRX active period, and may not monitor the PDCCH during the DRX inactive period. The DRX active period may include the following five situations, for example.

[0064] Case 1: One or more of the following timers are running: DRX onDuration Timer (drx-onDurationTimer), DRX inactivity timer (drx-InactivityTimer), DRX downlink retransmission timer (drx-RetransmissionTimerDL), DRX short TTI retransmission timer (drx-RetransmissionTimerShortTTI), DRX uplink retransmission timer (drx-RetransmissionTimerUL), DRX short TTI uplink retransmission timer (drx-ULRetransmissionTimerShortTTI) and contention resolution timer (mac-ContentionResolutionTimer).

[0065] Case 2: A scheduling request (SR) is transmitted on the physical uplink control channel (PUCCH) or the short physical uplink control channel (SPUCCH) and is in a pending state.

[0066] Case 3: In the non-contention-based random access process, after successfully receiving the random access response, the terminal device has not received an initial transmission indicated by the physical downlink control channel (PDCCH) scrambled by the cell radio network temporary identifier (C-RNTI).

[0067] Case 4: An uplink scheduling grant (UL grant) can be received for a pending HARQ retransmission, and there is data in the HARQ buffer of the synchronous HARQ process.

[0068] Case 5: The terminal device is configured with mpdcch-UL-HARQ-ACK-FeedbackConfig and is currently performing repeated transmission within a bundle.

[0069] The following describes the DRX-related timers in detail.

[0070] DRX persistence timer

[0071] While the DRX duration timer is running, the terminal device can monitor the PDCCH. Figure 4 illustrates an example of the DRX duration timer operation process. As shown in Figure 4, during a DRX cycle, while the DRX duration timer is running, i.e., during the on duration shown in Figure 4, the terminal device can monitor the PDCCH.

[0072] The DRX cycle may include a short DRX cycle or a long DRX cycle. The terminal may determine the time to start the DRX duration timer according to whether the terminal is currently in a short DRX cycle or a long DRX cycle.

[0073] The DRX duration timer can be started when the following conditions are met.

[0074] If a short DRX cycle is used, if the current subframe SFN satisfies [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drxStartOffset) modulo (drx-ShortCycle), the DRX duration timer may be started.

[0075] If a long DRX cycle is used, if the current subframe SFN satisfies [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset, it can be determined whether the DRX duration timer is started in the current subframe based on the type of the terminal. For example, if the terminal device is a narrowband internet of things (NB-IoT) terminal device, if there is at least one HARQ process corresponding to the uplink or downlink HARQ round-trip time timer (RTT Timer) that is not running, the DRX duration timer is started in the current subframe. Alternatively, if the terminal device is not a NB-IoT device, the DRX duration timer is started in the current subframe.

[0076] DRX deactivation timer and DRX retransmission timer

[0077] When a terminal receives a PDCCH scheduling an initial data transmission, it can start a DRX deactivation timer. As described above, the terminal monitors the PDCCH while the DRX deactivation timer is running. It is understood that based on the DRX deactivation timer, the terminal device can continue to monitor the PDCCH even when there is new data transmission.

[0078] When a terminal receives a PDCCH scheduling data transmission, it can start a DRX retransmission timer after a period of time. Each HARQ process can correspond to a HARQ retransmission timer. As mentioned above, while the DRX retransmission timer is running, the terminal monitors the PDCCH. It is understood that based on the DRX retransmission timer, the terminal device can monitor the PDCCH for retransmission.

[0079] The start time of the DRX deactivation timer and / or the DRX retransmission timer may be related to a HARQ round trip time (RTT) timer.

[0080] In some embodiments, for the DRX downlink retransmission timer, if the HARQ RTT timer times out and the data decoding of the HARQ process fails, the terminal device may start the DRX retransmission timer corresponding to the downlink HARQ process.

[0081] In some embodiments, for the DRX uplink retransmission timer, if the uplink HARQ RTT timer corresponding to a certain uplink HARQ process times out, the terminal may start the DRX uplink retransmission timer corresponding to the uplink HARQ process.

[0082] In some embodiments, for the DRX deactivation timer, if the HARQ RTT timer times out, it can be determined whether to start the DRX inactivity timer based on the type of the terminal. If the terminal device is an NB-IoT terminal device, if the PDCCH indicates that multiple transport blocks (TBs) are scheduled, the DRX inactivity timer can be started when the HARQ RTT timers corresponding to the HARQ processes used by all these TBs have timed out. If the terminal device is an NB-IoT terminal device, if the PDCCH indicates that a TB is scheduled, the DRX inactivity timer can be started when the HARQ RTT timer corresponding to the HARQ process used by this TB has timed out.

[0083] In some embodiments, for the DRX deactivation timer, for the NB-IoT terminal device, if the PDCCH indicates that multiple TBs are scheduled, then when the uplink HARQ RTT timers corresponding to the HARQ processes used by all these TBs have timed out, the DRX deactivation timer is started or restarted. For the NB-IoT terminal device, if the PDCCH indicates that a single TB is scheduled, then when the uplink HARQ RTT timer corresponding to the HARQ process used by the TB has timed out, the DRX deactivation timer is started or restarted. The following will explain in detail how to determine the start time of the HARQ RTT timer and the duration of the timer through some examples.

[0084] Regarding the start of the downlink HARQ RTT timer, in some embodiments, the condition for the terminal device to start the downlink HARQ RTT timer may include: if the terminal receives a PDCCH indicating a downlink transmission, or if the terminal has a configured downlink authorization in the subframe, the HARQ RTT timer may be started in the corresponding subframe according to the type of the terminal. In the case where the terminal device is an NB-IoT terminal device or an enhanced machine type communication (eMTC) terminal device, if the PDCCH indicates that multiple TB transmissions are scheduled, the terminal may start the HARQ RTT timers corresponding to all downlink HARQ processes used by the PDSCHs of the multiple TBs in the subframe where the last repeated transmission of the physical downlink shared channel (PDSCH) of the last TB of the multiple TBs is received. In the case where the terminal device is an NB-IoT terminal device or an eMTC terminal device, if the PDCCH indicates that a single TB transmission is scheduled, the terminal device may start the HARQ RTT timer corresponding to the downlink HARQ process used by the PDSCH in the subframe where the last repeated transmission of the PDSCH is received. When the terminal device is neither an NB-IoT terminal device nor an eMTC terminal device, the HARQ RTT timer corresponding to the downlink HARQ process used by the PDSCH is started in the corresponding subframe.

[0085] Regarding the start of the uplink HARQ RTT timer, in some embodiments, the conditions for the terminal device to start the uplink HARQ RTT timer may include: if the terminal device receives a PDCCH indicating an uplink transmission using an asynchronous HARQ process, or if the terminal device has a configured uplink authorization for a certain asynchronous HARQ process in the subframe, or the terminal receives a PDCCH indicating an uplink transmission using an automatic HARQ process, then it can be determined whether the uplink HARQ RTT timer is started in the subframe based on whether mpdcch-UL-HARQ-ACK-FeedbackConfig is configured. If mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured, when the PDCCH indicates that multiple TB transmissions are scheduled, the terminal device can start the uplink HARQ RTT timers corresponding to all uplink HARQ processes used by the PUSCH in the multiple TBs in the subframe where the last repeated transmission of the physical uplink shared channel (PUSCH) of the last TB of the multiple TBs is completed. If mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured, when the PDCCH indicates that a single TB transmission is scheduled, the terminal device can start the uplink HARQ RTT timer corresponding to the uplink HARQ process used by the PUSCH in the subframe where the last repeated transmission of the PUSCH is completed.

[0086] In some communication standards (eg, R16 standard), the definitions of the HARQ RTT timer and the uplink HARQ RTT timer may be as described below.

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

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

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

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

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

[0092] For eMTC, for frequency division duplex (FDD) and frame structure type 3, the uplink HARQ RTT timer is 4 subframes. For TDD, the uplink HARQ RTT timer is k ULHARQRTT subframes, where k ULHARQRTT Can be k PHICH .

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

[0094] For NB-IoT, if the PDCCH indicates that multiple TBs are scheduled simultaneously, the uplink HARQ RTT timer is 1 + deltaPDCCH subframes, where deltaPDCCH is the time interval from the last subframe of the PUSCH transmission plus 1 subframe to the first subframe of the next PDCCH opportunity.

[0095] In NTN systems, signal transmission latency between terminals and network devices increases significantly. Therefore, some communication protocols (such as the R17 IoT NTN project) specify the addition of an RTT offset to the HARQ RTT timer and uplink HARQ RTT timer definitions. In terrestrial networks (TN), the RTT offset is 0. In NTN systems, the RTT offset is the RTT between the terminal and the base station (e.g., UE-eNB RTT).

[0096] In some communication systems (e.g., R18 IoT NTN communication system), the HARQ process mode may include a first mode and a second mode. Taking the downlink HARQ process as an example, the first mode may be to provide HARQ feedback to a PDSCH receiving terminal using the HARQ process, and the second mode may be to not provide HARQ feedback to a PDSCH receiving terminal using the HARQ process.

[0097] As described above, HARQ can affect DRX behavior. For example, HARQ can affect the start time of a DRX deactivation timer and / or a DRX retransmission timer. This application proposes a communication method to consider the impact of HARQ processes in different modes on DRX behavior.

[0098] FIG5 is a schematic flow chart of a wireless communication method provided in an embodiment of the present application. The method shown in FIG5 can be performed by a terminal device and / or a network device. The network device can be a non-terrestrial network device, such as a satellite or an unmanned aerial vehicle system platform. The serving cell of the terminal device can be an NTN cell.

[0099] The method shown in FIG. 5 may include step S510 and step S520 .

[0100] Step S510: The terminal device receives a first PDCCH. Correspondingly, the network device sends the first PDCCH.

[0101] The first PDCCH can be used to schedule the first TB. It is understood that the first PDCCH can be used to schedule a single TB or multiple TBs. When the first PDCCH schedules a single TB, the first TB can be the TB scheduled by the first PDCCH. When the first PDCCH schedules multiple TBs, the first TB can be any one of the multiple TBs.

[0102] The first TB may be an uplink TB or a downlink TB. When the first PDCCH schedules uplink data, the first TB may be an uplink TB. When the first PDCCH schedules downlink data, the first TB may be a downlink TB.

[0103] The first TB may correspond to a first HARQ process. The first HARQ process may be an uplink HARQ process or a downlink HARQ process. If the first TB is an uplink TB, the first HARQ process may be an uplink HARQ process. If the first TB is a downlink TB, the first HARQ process may be a downlink HARQ process.

[0104] Step S520: The terminal device determines the DRX behavior of the terminal device according to the mode corresponding to the first HARQ process.

[0105] The mode corresponding to the first HARQ process may include a first mode and a second mode. The first mode and the second mode may correspond to different DRX behaviors.

[0106] In some embodiments, the first mode may be a HARQ feedback-enabled mode (or referred to as an enabled mode), and the second mode may be a HARQ feedback-disabled mode (or referred to as a disabled mode). It is understood that when the first HARQ is configured in the HARQ feedback-enabled mode, normal HARQ feedback may be performed for data transmission using the first HARQ process. When the first HARQ is configured in the disabled mode, HARQ feedback may not be performed for data transmission using the first HARQ process.

[0107] In some embodiments, for an uplink HARQ process, the first mode may be a mode supported by a related technology. When the HARQ process is in the second mode, the DRX behavior may be different from the DRX behavior in the first mode.

[0108] It can be understood that this application takes into account the impact of different HARQ modes on DRX behavior, and determines different DRX behaviors according to different modes corresponding to the HARQ process, so that the terminal can monitor PDCCH at the appropriate time, thereby having better scheduling performance in different modes and taking into account terminal power saving.

[0109] The DRX behavior may be a behavior related to the DRX activation period of the terminal device. For example, the DRX behavior may include the start time of the first timer. During the operation of the first timer, the terminal monitors the PDCCH. The first timer may, for example, include a DRX deactivation timer and / or a DRX retransmission timer. Among them, the DRX retransmission timer may correspond to the first HARQ process. The first timer may include an uplink timer and / or a downlink timer. Taking the example that the first timer includes a DRX retransmission timer, the DRX retransmission timer may include an uplink DRX retransmission timer and / or a downlink DRX retransmission timer. In some embodiments, the downlink DRX retransmission timer is also referred to as a DRX retransmission timer.

[0110] It should be noted that starting the first timer may include starting or restarting the first timer. In other words, starting the first timer may include: creating a new first timer and starting the first timer to run, or, if the first timer is running, restarting the first timer based on the timing duration of the first timer.

[0111] When the first HARQ process is in the second mode and the DRX behavior includes a start time of the first timer, the start time of the first timer may be determined based on the first information. The first information may include one or more of the following: a transmission time of the first channel and a timing duration of the first HARQ RTT timer.

[0112] The first HARQ RTT timer may correspond to the first HARQ process. The first HARQ RTT timer may be a HARQ RTT timer corresponding to an uplink or downlink HARQ process, which is not limited in this application.

[0113] The first channel may carry the first TB. The first channel may be, for example, a PDSCH or a PUSCH. When the first PDCCH schedules uplink data, the first channel may be a PUSCH. When the first PDCCH schedules downlink data, the first channel may be a PDSCH.

[0114] In some embodiments, the first information may include the transmission time of the first channel. The first timer may be started at the end time of the transmission of the first channel. For example, the first timer may be started immediately after the terminal device completes the transmission of the first channel.

[0115] Figure 6 is an example diagram of a method for starting a first timer provided by an embodiment of the present application. As shown in Figure 6, the transmission end time of the first channel is t1. At time t1, the first timer can be started.

[0116] It is understandable that when the first HARQ process is in the second mode, the terminal device can ignore the impact of the HARQ RTT timer corresponding to the first HARQ process on the DRX behavior. In other words, the time of starting the first timer can be independent of the HARQ RTT timer corresponding to the first HARQ process.

[0117] The transmission end time of the first channel may be the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

[0118] It should be noted that the time domain unit referred to in the entire application can be any of the following: a subframe, a time slot, or one or more symbols. For example, the transmission end time of the first channel can be the last subframe in the time domain resource occupied by the first channel or the subframe next to the last subframe.

[0119] The first channel may perform repetition transmission. In this case, the transmission end time of the first channel may be the transmission end time of the last repetition transmission of the first channel.

[0120] The first PDCCH can schedule multiple TBs. The multiple TBs may include the first TB. In this case, the transmission end time of the first channel may be the transmission end time of the last TB in the multiple TBs. The HARQ processes corresponding to the multiple TBs may all be in the second mode, which may be, for example, a disabled mode. The HARQ processes corresponding to the multiple TBs may partially be in the first mode and partially in the second mode, which may be, for example, a disabled mode.

[0121] For example, when the first channel is PDSCH and the first PDCCH schedules a single TB, the PDSCH transmission end time may be the subframe where the last repeated transmission of the PDSCH is located. Alternatively, the PDSCH transmission end time may be the subframe next to the subframe where the last repeated transmission of the PDSCH is located.

[0122] Taking the case where the first channel is PUSCH and the first PDCCH schedules a single TB as an example, the PUSCH transmission end time may be the first subframe in which the last repeated PUSCH transmission occurs. Alternatively, the PUSCH transmission end time may be the subframe following the first subframe. The first subframe may be the last subframe in which the last repeated PUSCH transmission occurs.

[0123] For example, if the first channel is PDSCH and the first PDCCH schedules multiple TBs, the PDSCH transmission end time may be the second subframe in which the last repeated transmission of the PDSCH of the last TB among the multiple TBs occurs, or the PDSCH transmission end time may be the subframe next to the second subframe. The second subframe may be the last subframe in which the last repeated transmission of the PDSCH of the last TB among the multiple TBs occurs.

[0124] Taking the case where the first channel is PUSCH and the first PDCCH schedules multiple TBs as an example, the PUSCH transmission end time may be the third subframe in which the last repeated transmission of the PUSCH of the last TB among the multiple TBs is located, or the PUSCH transmission end time may be the subframe next to the third subframe. The third subframe may be the last subframe in which the last repeated transmission of the PUSCH of the last TB among the multiple TBs is located.

[0125] In some other embodiments, the first information may include the timing duration of the first HARQ RTT timer.

[0126] In some embodiments, the first timer may be started after the first HARQ RTT timer expires. For example, when the first PDCCH schedules a single TB, the first timer may be started after the HARQ RTT timer corresponding to the first HARQ process expires. When the first PDCCH schedules multiple TBs, the first timer may be started after the HARQ RTT timers corresponding to all HARQ processes in the second mode in the multiple HARQ processes used by the multiple TBs have expired.

[0127] The start time of the first HARQ RTT timer may be the transmission end time of the first channel. The transmission end time of the first channel may be as described above and will not be repeated here.

[0128] FIG7 is an example diagram of another method for starting a first timer provided by an embodiment of the present application. In the method shown in FIG7 , the first timer can be started after the first HARQ RTT timer times out. As shown in FIG7 , the transmission end time of the first channel is t1. At time t1, the first HARQ RTT timer can be started. The timing duration of the first HARQ RTT timer can be T. At time t2, the first HARQ RTT timer times out. At time t2, the first timer can be started.

[0129] It is understandable that the network device may also perform step S520, that is, the network device may determine the DRX behavior of the terminal device according to the mode corresponding to the first HARQ process and perform scheduling according to the DRX behavior of the terminal device.

[0130] The following describes in detail a method for determining the timing duration of the first HARQ RTT timer.

[0131] It should be noted that the unit of the timing duration of the first HARQ RTT timer may be a time domain unit, for example, the unit may be a subframe.

[0132] In some embodiments, the timing duration of the first HARQ RTT timer may be determined based on a predefined value. The predefined value may be defined by a protocol or defined by a terminal device and / or a network device.

[0133] In some implementations, the timing duration of the first HARQ RTT timer may be a predefined value. For example, the predefined value may be 12 subframes, i.e., the timing duration of the first HARQ RTT timer may be 12 subframes. When the terminal device is an eMTC terminal device and / or an NB-IoT terminal device, it may be determined that the timing duration of the first HARQ RTT timer may be the predefined value.

[0134] In some other implementations, the timing duration of the first HARQ RTT timer may be determined based on a predefined value and a first interval (e.g., which may be expressed as deltaPDCCH). The first interval may, for example, be the time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity. When the terminal device is an NB-IoT terminal device, the timing duration of the first HARQ RTT timer may be determined based on the predefined value and the first interval.

[0135] The first time domain unit can be determined by the transmission time of the first channel. For example, the first time domain unit can be the transmission end time of the first channel plus the time domain unit in which N time domain units are located. Alternatively, the first time domain unit can be the transmission end time of the first channel plus the time domain unit next to the time domain unit in which N time domain units are located. N can be an integer greater than 0. N can be predefined or preconfigured. The transmission end time of the first channel is described above and will not be repeated here.

[0136] Taking the first PDCCH scheduling of a single downlink TB as an example, the first interval may be, for example, the time interval between subframe i and the first subframe corresponding to the next PDCCH monitoring opportunity. Subframe i may be the subframe following the last repeated transmission received by the PDSCH + N subframes, or the subframe following the last repeated transmission received by the PDSCH + N subframes.

[0137] Taking the first PDCCH scheduling multiple downlink TBs as an example, the first interval may be, for example, the time interval between subframe i and the first subframe corresponding to the next PDCCH monitoring opportunity. Subframe i may be the subframe containing the last repeated transmission of the PDSCH received by the last TB among the multiple TBs + the subframe containing N subframes, or the subframe next to the subframe containing the last repeated transmission of the PDSCH received by the last TB among the multiple TBs + the subframe containing N subframes.

[0138] It can be understood that the timing duration of the first HARQ RTT timer described above is determined based on a predefined value and can be applicable to any of the following scenarios: the first PDCCH schedules a single downlink TB, the first PDCCH schedules multiple downlink TBs, the first PDCCH schedules a single uplink TB, and the first PDCCH schedules multiple uplink TBs. In the scenario where the first PDCCH schedules multiple downlink TBs and at least one HARQ process in the HARQ processes corresponding to the multiple TBs is in the second mode, the first interval may also be referred to as the second interval.

[0139] In some embodiments, during the calculation of the timing duration of the first HARQ RTT timer, the RTT offset (RTT offset) of the first HARQ RTT timer may be 0. For example, when the first TB is an uplink TB, the first HARQ process is in the second mode, and the RTT offset may be 0. That is, if the serving cell of the terminal is an NTN cell, the timing duration of the first HARQ RTT timer may be the same as the definition or value in the NT scenario. Alternatively, when the first TB is a downlink TB, the first HARQ process is in the second mode, and in the NTN scenario, the RTT offset may be 0. It can be understood that for a downlink TB, when the mode of the HARQ process corresponding to the downlink TB is the first mode, in the NTN scenario, the RTT offset may be a value specified in relevant technical regulations (for example, it may be UE-eNB RTT).

[0140] When the first PDCCH schedules multiple TBs, the multiple TBs correspond to multiple HARQ processes. The multiple TBs may be downlink TBs. The multiple HARQ processes may all be in the second mode, or a portion of the multiple HARQ processes may be in the second mode. It is understood that the second mode may be a disabled mode. In other words, the multiple HARQ processes may all be in the disabled mode, i.e., none of them perform HARQ feedback, or a portion of the multiple HARQ processes may be in the disabled mode, i.e., some HARQ processes may perform HARQ feedback.

[0141] In the case where the first PDCCH schedules multiple TBs, the timing duration of the first HARQ RTT timer can be determined based on the second information. Multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: the number of HARQ processes that perform HARQ feedback in multiple HARQ processes; the HARQ feedback mode of multiple HARQ processes.

[0142] The HARQ feedback mode may further include a HARQ feedback mode configured with HACK-ACK bundling or a HARQ feedback mode not configured with HACK-ACK bundling.

[0143] As an embodiment, when the number of HARQ processes performing HARQ feedback in multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer can be determined based on a predefined value. For example, the timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval. Optionally, the second interval is the time interval between the second time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the second time domain unit can be determined based on the transmission time of the first channel. For an explanation of the second interval, please refer to the relevant content of the first interval above.

[0144] As an embodiment, when the number of HARQ processes performing HARQ feedback in multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer can be determined based on the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

[0145] In some embodiments, if the first PDCCH schedules multiple downlink TBs simultaneously and the HARQ feedback mode with HACK-ACK bundling is not configured, the timing duration of the first HARQ RTT timer may be 7+m*N+RTT offset. N may be the PUCCH repetition factor, and m may be the number of TBs corresponding to the downlink HARQ process for which HARQ feedback is performed in the multiple HARQ processes corresponding to the multiple TBs indicated in the first PDCCH. This embodiment may be applied to eMTC terminal devices.

[0146] In some embodiments, if the first PDCCH schedules multiple downlink TBs simultaneously and the HARQ feedback mode of HACK-ACK bundling is configured, the first HARQ RTT timer may be 7+k*N+RTT offset. Where N may be the PUCCH repetition factor, and k may be the number of HARQ feedback bundlings. k may satisfy k=ceiling(N TB / M), N TBIt can be the number of TBs corresponding to the HARQ process for HARQ feedback in the multiple TBs indicated in the first PDCCH. M can be the multi-TB HARQ feedback bundling size indicated in the first PDCCH. Wherein, ceiling() indicates rounding up, that is, rounding in the direction of increasing absolute value. For example, ceiling(4.1) = 5, ceiling(4.7) = 5. This embodiment can be applied to eMTC terminal devices.

[0147] In some embodiments, for the case where the first PDCCH schedules multiple downlink TBs at the same time, if these multiple TBs are non-interleaved or if these multiple TBs are interleaved and the HARQ feedback mode of the bundling mode is not configured, if the HARQ process corresponding to one TB (for example, the first TB) among these multiple TBs does not perform HARQ feedback, then the timing duration of the HARQ RTT timer can be k+3+N+RTToffset+deltaPDCCH. Among them, k can be the time interval between the last subframe of the PDSCH transmission for multiple TBs and the first subframe of the corresponding HARQ feedback transmission, N can be the transmission duration of the corresponding HARQ feedback, and deltaPDCCH can be the time interval from the next subframe of the last subframe of the corresponding HARQ feedback transmission + 3+RTToffset to the first subframe of the next PDCCH monitoring opportunity. This embodiment can be applied to NB-IoT terminals.

[0148] It can be understood that for a terminal configured with two HARQ processes, such as an NB-IoT terminal, in the HARQ processes corresponding to multiple TBs scheduled by the first PDCCH, if there is a HARQ process that performs HARQ feedback and a HARQ process that does not perform HARQ feedback, then the definition of the first HARQ RTT timer can be the same as the case where the first PDCCH schedules a single downlink TB in the related technology.

[0149] It should be noted that, when the first PDCCH schedules multiple TBs including the first TB, and the second HARQ process corresponding to the second TB in the multiple TBs is the first mode, the HARQ RTT timer corresponding to the second HARQ process is also calculated using the method of the relevant technology.

[0150] It can be understood that the present application can set the parameters related to HARQ feedback to preset values ​​or calculate them through the HARQ process that performs HARQ feedback based on the method of calculating the timing duration of the HARQ RTT timer in the relevant technology, so as to reasonably configure the impact of the second mode HARQ process on the timing duration of the HARQ RTT timer, so that the duration of the HARQ RTT timer can be more in line with the actual scenario.

[0151] It should be noted that the first HARQ RTT timer can not only be used to determine the start of the first timer, but can also be used to implement other functions, which is not limited in this application. In other words, the method for determining the timing length of the HARQ RTT timer described above can also be applied to other scenarios related to the HARQ RTT timer. For example, based on the timing length of the first HARQ RTT timer, the start time of the DRX duration timer can be determined.

[0152] The technical solution provided by this application is described in detail below through five specific embodiments.

[0153] Example 1

[0154] The first embodiment relates to the case where the first PDCCH schedules a single downlink TB (first TB). The second mode is the HARQ disabled mode, that is, the first HARQ process corresponding to the first TB does not perform HARQ feedback. The method provided in the first embodiment may include steps S610 to S620.

[0155] Step S610: A terminal device in a radio resource control (RRC) connected state receives a first PDCCH indicating scheduling of PDSCH transmission of a TB.

[0156] Step S620: Determine the DRX behavior of the terminal device according to the mode of the first HARQ process used for the PDSCH transmission of the first TB.

[0157] In the case that the mode of the first HARQ process is the second mode, the DRX behavior may include step S621 or step S622.

[0158] Step S621: When the terminal completes PDSCH reception, it may start a DRX deactivation timer and / or a DRX retransmission timer corresponding to the first HARQ process.

[0159] Among them, the moment when the terminal device starts the DRX deactivation timer and / or the DRX retransmission timer corresponding to the first HARQ process can be the PDSCH transmission end time. The PDSCH transmission end time can be the subframe where the last repeated transmission of the PDSCH is located, or the next subframe in which the last repeated transmission of the PDSCH is completed.

[0160] Figure 8 is an example diagram of a communication method including step S621, provided in an embodiment of the present application. In Figure 8 , TB1 may be the first TB, and HARQ process 0 may be the first HARQ process. At PDSCH transmission end time t1, the terminal may start the DRX deactivation timer and / or the DRX retransmission timer corresponding to HARQ process 0.

[0161] Step S622: The terminal starts a first HARQ RTT timer corresponding to the first HARQ process in the subframe where the last repeated transmission of the PDSCH occurs.

[0162] The timing duration of the first HARQ RTT timer may be: a predefined value or a predefined value+deltaPDCCH.

[0163] For example, when the terminal device is an eMTC terminal and / or an NB-IoT terminal device, the timing duration of the first HARQ RTT timer may be a predefined value. Alternatively, when the terminal device is an NB-IoT terminal device, the timing duration of the first HARQ RTT timer may be a predefined value + deltaPDCCH.

[0164] The predefined value may be, for example, 12 subframes.

[0165] deltaPDCCH is the time interval between subframe i and the first subframe corresponding to the next PDCCH monitoring opportunity. Subframe i can be the subframe following the last repeated transmission of the PDSCH + N subframes, or the subframe following the last repeated transmission of the PDSCH + N subframes. N can be predefined.

[0166] FIG9 is an example diagram of a communication method including step S622 provided in an embodiment of the present application. In FIG9 , TB1 may be the first TB, and HARQ process 0 may be the first HARQ process. At PDSCH transmission end time t1, the terminal device may start the first HARQ RTT timer corresponding to HARQ process 0. At time t2 when the first HARQ RTT timer times out, the terminal device may start the DRX deactivation timer and / or the DRX retransmission timer corresponding to HARQ process 0.

[0167] Example 2

[0168] The second embodiment relates to a case where a first PDCCH schedules a single uplink TB (first TB). The first HARQ process corresponding to the first TB is in the second mode. The method provided in the second embodiment may include steps S710 to S720.

[0169] Step S710: A terminal device in an RRC connected state receives a first PDCCH indicating scheduling of PUSCH transmission of a TB.

[0170] Step S720: Determine the DRX behavior of the terminal device according to the mode of the first HARQ process used for the PUSCH transmission of the first TB.

[0171] In the case that the mode of the first HARQ process is the second mode, step S720 may include step S721 or S722.

[0172] Step S721: After completing the PUSCH transmission, the terminal device starts the DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to the first HARQ process.

[0173] The moment of starting the DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to the first HARQ process may be the PUSCH transmission end time. The PUSCH transmission end time may be the (last) subframe in which the last repetition of the PUSCH is located, or the next subframe in which the last repetition of the PUSCH is completed.

[0174] Figure 10 is an example diagram of a communication method including step S721, provided in an embodiment of the present application. In Figure 10 , TB1 may be the first TB, and HARQ process 0 may be the first HARQ process. At PUSCH transmission end time t1, the terminal may start the DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to HARQ process 0.

[0175] Step S722: The terminal device starts the first HARQ RTT timer corresponding to the first HARQ process in the (last) subframe where the last repeated transmission of the PUSCH is located.

[0176] The first HARQ RTT timer may be an uplink HARQ RTT timer. The definition of the timing duration of the first HARQ RTT timer may be the same as the definition of the timing duration of the uplink HARQ RTT timer in a TN scenario in the related art.

[0177] FIG11 is an example diagram of a communication method including step S722 provided in an embodiment of the present application. In FIG11 , TB1 may be the first TB, and HARQ process 0 may be the first HARQ process. At PUSCH transmission end time t1, the terminal device may start the first HARQ RTT timer corresponding to HARQ process 0. At time t2 when the first HARQ RTT timer times out, the terminal device may start the DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to HARQ process 0.

[0178] Example 3

[0179] Embodiment 3 involves a situation where a first PDCCH simultaneously schedules multiple downlink TBs. The multiple downlink TBs include the first TB. The second mode is a HARQ disabled mode, i.e., the first HARQ process corresponding to the first TB does not perform HARQ feedback. The method provided in Embodiment 3 may include steps S810 to S820.

[0180] Step S810: A terminal device in an RRC connected state receives a first PDCCH. The first PDCCH indicates that PDSCH transmission of multiple downlink TBs is scheduled simultaneously.

[0181] Step S810 may include step S811 or step S812.

[0182] In step S811, for a non-bundled HARQ feedback mode, the terminal may sequentially send HARQ feedback to TBs in which the HARQ processes used by multiple simultaneously scheduled downlink TBs are in the first mode (enabled mode).

[0183] In step S812, for the bundled HARQ feedback mode, for the TBs whose HARQ processes are in the first mode (enabled mode) among the multiple simultaneously scheduled downlink TBs, the terminal device sequentially bundles the HARQ feedback information of each of the M TBs according to the HARQ feedback bundling size M to obtain a single HARQ feedback result. The terminal may sequentially transmit these HARQ bundling feedback results.

[0184] Figure 12 is an example diagram of the feedback timing of multiple downlink TBs of the first PDCCH provided in an embodiment of the present application. In Figure 12, the first PDCCH can call multiple downlink TBs, namely TB1 to TB6. Among them, the mode of the HARQ process corresponding to TB2 and TB4 is the second mode, and the mode of the HARQ process corresponding to TB1, TB3, TB5 and TB6 is the first mode. Figure 12(a) shows an example of non-bundled HARQ feedback, that is, an example of step S811. In Figure 12(a), the terminal sends HARQ feedback for TB1, TB3, TB5 and TB6 in sequence. Figure 12(b) shows an example of bound HARQ feedback, that is, an example of step S812. In Figure 12(b), the HARQ feedback bundling size M is 2, then the terminal can bundle the HARQ feedback information of 2 TBs to obtain a feedback result. As shown in Figure 12(b), the HARQ feedback information of TB1 and TB3 is bundled, and the HARQ feedback information of TB5 and TB6 is bundled.

[0185] In step S820, the terminal determines the DRX behavior according to the modes of the HARQ processes corresponding to the multiple downlink TBs.

[0186] The DRX behavior may include one or more of the following behaviors: determining the duration of the HARQ RTT timer, starting a DRX deactivation timer and / or a DRX retransmission timer.

[0187] The length of the HARQ RTT timer can be determined according to the type of terminal device and the HARQ feedback mode.

[0188] As an implementation, when the terminal device type is eMTC, if the first PDCCH schedules multiple downlink TBs simultaneously and no bundled HARQ feedback mode is configured, the timing duration of the HARQ RTT timer can be 7+m*N+RTT offset. Where N can be the PUCCH repetition factor, and m can be the number of TBs in the first mode of the HARQ process used in the multiple downlink TBs indicated in the first PDCCH.

[0189] As an implementation method, when the type of terminal device is eMTC, if the first PDCCH schedules multiple downlink TBs at the same time and the bundled HARQ feedback mode is configured, the HARQ RTT timer can be 7+k*N+RTT offset. Where N is the PUCCH repetition factor. k can be the number of HARQ feedback bundlings, and k can satisfy k=ceiling(N TB / M). N TB It may be the number of TBs in the first mode of the HARQ process used in the multiple downlink TBs indicated in the first PDCCH. M may be the multi-TB HARQ feedback bundling size indicated in the first PDCCH.

[0190] As an implementation method, when the type of terminal device is NB-IoT, if the multiple TBs are non-interleaved or if the multiple downlink TBs are interleaved and no bound HARQ feedback mode is configured, if the HARQ process used by one of the multiple downlink TBs is the second mode, the HARQ RTT timer can be k+3+N+RTToffset+deltaPDCCH. Among them, k can be the time interval between the last subframe of the PDSCH transmission for the multiple downlink TBs and the first subframe of the corresponding HARQ feedback transmission, N can be the transmission duration of the corresponding HARQ feedback, and deltaPDCCH can be the time interval from the next subframe of the last subframe of the corresponding HARQ feedback transmission + 3+RTToffset to the first subframe of the next PDCCH monitoring opportunity. It can be understood that the definition of the HARQ RTT timer in this case can be the same as the case where PDCCH schedules a single downlink TB.

[0191] Example 4

[0192] Embodiment 4 relates to a case where a first PDCCH simultaneously schedules multiple downlink TBs. The multiple downlink TBs include the first TB. The second mode is a HARQ disabled mode, i.e., the first HARQ process corresponding to the first TB does not perform HARQ feedback. The method provided in embodiment 4 may include steps S910 to S920.

[0193] Step S910: The terminal device in the RRC connected state receives a first PDCCH indicating simultaneous scheduling of PDSCH transmissions of multiple downlink TBs.

[0194] In step S920, the terminal determines the DRX behavior according to the modes of the HARQ processes corresponding to the multiple downlink TBs.

[0195] In one implementation, if the HARQ processes used by multiple downlink TBs are all in the second mode, step S920 may include step S921 or step S922.

[0196] Step S921: After completing the PDSCH reception of the multiple TBs, the terminal device starts the DRX deactivation timer and / or the DRX retransmission timer corresponding to the HARQ process used by the multiple downlink TBs.

[0197] The moment when the terminal device starts the DRX deactivation timer and / or the DRX retransmission timer corresponding to the HARQ process used by the multiple downlink TBs can be: the subframe where the last repetition of the PDSCH of the last TB among the multiple downlink TBs is located; or, the next subframe where the last repetition of the PDSCH of the last TB among the multiple downlink TBs is completed.

[0198] In step S922, the terminal device starts the HARQ RTT timer corresponding to the HARQ process in the subframe where the last repeated transmission of the PDSCH of the last TB of the multiple downlink TBs occurs. The timing duration of the HARQ RTT timer can be determined according to a predefined value.

[0199] The timing duration of the HARQ RTT timer can be: a predefined value or a predefined value+deltaPDCCH.

[0200] For example, when the terminal device is an eMTC terminal and / or an NB-IoT terminal device, the timing duration of the first HARQ RTT timer may be a predefined value. Alternatively, when the terminal device is an NB-IoT terminal device, the timing duration of the first HARQ RTT timer may be a predefined value + deltaPDCCH.

[0201] The predefined value may be, for example, 12 subframes.

[0202] deltaPDCCH is the time interval between subframe i and the first subframe corresponding to the next PDCCH monitoring opportunity. Subframe i can be the subframe following the last received PDSCH retransmission plus N subframes, or the subframe following the last received PDSCH retransmission plus N subframes. N can be predefined.

[0203] In another implementation, the HARQ process used by some of the multiple TBs is the second mode. The HARQ process used by some of the multiple TBs is the first mode.

[0204] For the HARQ processes of the first mode used by the multiple downlink TBs, the terminal may start the HARQ RTT timer corresponding to the HARQ process in the subframe where the last repeated transmission of the PDSCH of the last TB of the multiple downlink TBs occurs. The duration of the HARQ RTT timer may be defined using the method given in Example 3, where the RTT offset may be the UE-eNB RTT. After the HARQ RTT timers corresponding to these first-mode HARQ processes expire, the terminal may start the DRX deactivation timer and / or the DRX retransmission timers corresponding to these HARQ processes.

[0205] For the HARQ process of the second mode among the HARQ processes used by the multiple downlink TBs, the terminal device may start the DRX deactivation timer and / or the DRX retransmission timer corresponding to the HARQ process after completing the PDSCH reception of the multiple downlink TBs. The moment when the terminal device starts the DRX deactivation timer and / or the DRX retransmission timer corresponding to the HARQ process used by the multiple downlink TBs may be: the subframe where the last repetition of the PDSCH of the last TB among the multiple downlink TBs is located; or, the next subframe where the last repetition of the PDSCH of the last TB among the multiple downlink TBs is completed.

[0206] For a HARQ process in the second mode among the HARQ processes used by the multiple downlink TBs, the terminal may start the HARQ RTT timer corresponding to the HARQ process in the subframe in which the last repeated transmission of the PDSCH of the last TB of the multiple downlink TBs occurs. The timing duration of the HARQ RTT timer may be a predefined value or a predefined value + deltaPDCCH. Alternatively, the HARQ RTT timer may be determined according to the method provided in Example 3, wherein the RTT offset may be 0.

[0207] After the HARQ RTT timers corresponding to these HARQ processes in the second mode all time out, the terminal may start a DRX deactivation timer and / or a DRX retransmission timer corresponding to these HARQ processes.

[0208] Example 5

[0209] Embodiment 5 relates to a case where a first PDCCH schedules multiple uplink TBs simultaneously. The multiple uplink TBs may include a first TB. The first HARQ process corresponding to the first TB is in the second mode. The method provided in embodiment 5 may include steps S1010 to S1020.

[0210] Step S1010: A terminal in an RRC connected state receives a PDCCH indicating simultaneous scheduling of PUSCH transmissions of multiple uplink TBs.

[0211] Step S1020: If the HARQ process used by at least one TB among the multiple uplink TBs is the second mode, the DRX behavior of the terminal device is determined.

[0212] Step S1020 may include step S1021 or S1022.

[0213] Step S1021: After completing the PUSCH transmission of the multiple uplink TBs, the terminal device starts the DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to the HARQ process.

[0214] The moment when the terminal device starts the above-mentioned DRX deactivation timer and / or the DRX uplink retransmission timer corresponding to the HARQ process can be: the subframe (for example, the last subframe) where the last repeated transmission of PUSCH of the last TB of multiple uplink TBs is located; or, the next subframe in which the last repeated transmission of PUSCH of the last TB of the multiple uplink TBs is completed.

[0215] In step S1022, the terminal device starts the uplink HARQ RTT timer corresponding to the HARQ process in the subframe (eg, the last subframe) where the last repeated transmission of the PUSCH of the last TB of the multiple uplink TBs is located.

[0216] The definition of the timing duration of the uplink HARQ RTT timer may be the same as the definition of the timing duration of the uplink HARQ RTT timer in a TN scenario in the related art.

[0217] After the HARQ RTT Timers corresponding to these HARQ processes in the second mode all time out, the terminal may start a DRX deactivation timer and / or a DRX uplink retransmission timer corresponding to these HARQ processes.

[0218] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 12. The device embodiment of the present application is described in detail below in conjunction with Figures 13 to 15. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0219] 13 is a schematic structural diagram of a terminal device 1300 provided in an embodiment of the present application. The terminal device 1300 may include a first receiving unit 1310 and a first determining unit 1320.

[0220] The first receiving unit 1310 may be configured to receive a first PDCCH, where the first PDCCH is used to schedule a first TB, and the first TB corresponds to a first HARQ process.

[0221] The first determination unit 1320 can be used to determine the DRX behavior of the terminal device according to the mode corresponding to the first HARQ process, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0222] Optionally, the DRX behavior includes a start time of a first timer, and the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

[0223] Optionally, if the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, and the first information includes one or more of the following: the transmission time of the first channel, wherein the first channel is carried by the first TB; the timing duration of the first HARQ RTT timer, and the first HARQ RTT timer corresponds to the first HARQ process.

[0224] Optionally, the first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

[0225] Optionally, the transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

[0226] Optionally, in the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

[0227] Optionally, in the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

[0228] Optionally, the first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

[0229] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value.

[0230] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

[0231] Optionally, the first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

[0232] Optionally, when the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

[0233] Optionally, when the first PDCCH schedules multiple TBs and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined based on second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: the number of HARQ processes performing HARQ feedback in the multiple HARQ processes; and the HARQ feedback mode of the multiple HARQ processes.

[0234] Optionally, when the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

[0235] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

[0236] Optionally, the second interval is a time interval between a second time domain unit and a first time domain unit corresponding to a next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on a transmission time of the first channel.

[0237] Optionally, when the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined based on the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

[0238] Optionally, the first channel is PDSCH or PUSCH.

[0239] Optionally, the time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

[0240] Optionally, the service cell of the terminal device is an NTN cell.

[0241] Optionally, the terminal device is an NB-IoT terminal device and / or an eMTC terminal device.

[0242] FIG14 is a schematic structural diagram of a network device 1400 provided in an embodiment of the present application. The network device 1400 may include a first sending unit 1410 .

[0243] The first sending unit 1410 can be used to send a first PDCCH, the first PDCCH is used to schedule a first TB, and the first TB corresponds to a first HARQ process; wherein, the mode corresponding to the first HARQ process is used to determine the DRX behavior of the terminal device, and the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

[0244] Optionally, the DRX behavior includes a start time of a first timer, and the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

[0245] Optionally, if the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, and the first information includes one or more of the following: the transmission time of the first channel, wherein the first channel is carried by the first TB; the timing duration of the first HARQ RTT timer, and the first HARQ RTT timer corresponds to the first HARQ process.

[0246] Optionally, the first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

[0247] Optionally, the transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

[0248] Optionally, in the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

[0249] Optionally, in the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

[0250] Optionally, the first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

[0251] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value.

[0252] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

[0253] Optionally, the first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

[0254] Optionally, when the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

[0255] Optionally, when the first PDCCH schedules multiple TBs and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined based on second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: the number of HARQ processes performing HARQ feedback in the multiple HARQ processes; and the HARQ feedback mode of the multiple HARQ processes.

[0256] Optionally, when the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

[0257] Optionally, the timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

[0258] Optionally, the second interval is a time interval between a second time domain unit and a first time domain unit corresponding to a next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on a transmission time of the first channel.

[0259] Optionally, when the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined based on the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

[0260] Optionally, the first channel is PDSCH or PUSCH.

[0261] Optionally, the time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

[0262] Optionally, the service cell of the terminal device is an NTN cell.

[0263] Optionally, the terminal device is an NB-IoT terminal device and / or an eMTC terminal device.

[0264] Figure 15 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 15 indicate that the unit or module is optional. Apparatus 1500 may be used to implement the method described in the above method embodiment. Apparatus 1500 may be a chip, a terminal device, or a network device.

[0265] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0266] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store programs that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the above method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0267] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips via the transceiver 1530.

[0268] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0269] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0270] The present application also provides a computer program that can be applied to a terminal or network device provided in the present application, and enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0271] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0272] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0273] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

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

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

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

[0277] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0278] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

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

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

[0282] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a first physical downlink control channel PDCCH, where the first PDCCH is used to schedule a first transport block TB, and the first TB corresponds to a first hybrid automatic repeat request HARQ process; The terminal device determines the discontinuous reception DRX behavior of the terminal device according to the mode corresponding to the first HARQ process, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

2. The method according to claim 1, characterized in that The DRX behavior includes a start time of a first timer, where the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

3. The method according to claim 2, characterized in that If the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, where the first information includes one or more of the following: a transmission time of a first channel, wherein the first channel is carried on the first TB; The timing duration of a first HARQ round trip time (RTT) timer, where the first HARQ RTT timer corresponds to the first HARQ process.

4. The method according to claim 3, characterized in that The first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

5. The method according to claim 4, characterized in that The transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

6. The method according to claim 4 or 5, characterized in that In the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

7. The method according to any one of claims 4 to 6, characterized in that In the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

8. The method according to claim 3, characterized in that The first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

9. The method according to claim 8, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value.

10. The method according to claim 9, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

11. The method according to claim 10, characterized in that The first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

12. The method according to claim 8, characterized in that When the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

13. The method according to claim 8, characterized in that When the first PDCCH schedules multiple TBs, and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined according to second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: The number of HARQ processes performing HARQ feedback among the multiple HARQ processes; The HARQ feedback modes of the multiple HARQ processes.

14. The method according to claim 13, characterized in that When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

15. The method according to claim 14, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

16. The method according to claim 15, characterized in that The second interval is a time interval between the second time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on the transmission time of the first channel.

17. The method according to claim 13, wherein When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined according to the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

18. The method according to any one of claims 3 to 17, characterized in that The first channel is PDSCH or PUSCH.

19. The method according to claim 5, 11 or 16, characterized in that The time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

20. The method according to claims 1-19, characterized in that The service cell of the terminal device is a non-terrestrial communication network NTN cell.

21. The method according to claims 1-20, characterized in that The terminal device is a narrowband Internet of Things (NB-IoT) terminal device and / or an enhanced machine type communication (eMTC) terminal device.

22. A wireless communication method, characterized in that: include: The network device sends a first physical downlink control channel PDCCH, where the first PDCCH is used to schedule a first transport block TB, and the first TB corresponds to a first hybrid automatic repeat request HARQ process; The mode corresponding to the first HARQ process is used to determine the discontinuous reception DRX behavior of the terminal device, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

23. The method according to claim 22, characterized in that The DRX behavior includes a start time of a first timer, where the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

24. The method according to claim 23, wherein If the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, where the first information includes one or more of the following: a transmission time of a first channel, wherein the first channel is carried on the first TB; The timing duration of a first HARQ round trip time (RTT) timer, where the first HARQ RTT timer corresponds to the first HARQ process.

25. The method according to claim 24, characterized in that The first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

26. The method according to claim 25, characterized in that The transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

27. The method according to claim 25 or 26, characterized in that In the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

28. The method according to any one of claims 25 to 27, characterized in that In the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

29. The method according to claim 24, wherein The first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

30. The method according to claim 29, wherein The timing duration of the first HARQ RTT timer is determined based on a predefined value.

31. The method according to claim 30, wherein The timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

32. The method according to claim 31, characterized in that The first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

33. The method according to claim 29, wherein When the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

34. The method according to claim 29, wherein When the first PDCCH schedules multiple TBs, and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined according to second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: The number of HARQ processes performing HARQ feedback among the multiple HARQ processes; The HARQ feedback modes of the multiple HARQ processes.

35. The method according to claim 34, wherein When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

36. The method according to claim 35, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

37. The method according to claim 36, characterized in that The second interval is a time interval between the second time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on the transmission time of the first channel.

38. The method according to claim 34, wherein When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined according to the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

39. The method according to any one of claims 24 to 38, wherein The first channel is PDSCH or PUSCH.

40. The method according to claim 26, 32 or 37, wherein: The time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

41. The method according to claims 22-40, characterized in that The service cell of the terminal device is a non-terrestrial communication network NTN cell.

42. The method according to claims 22-41, characterized in that The terminal device is a narrowband Internet of Things (NB-IoT) terminal device and / or an enhanced machine type communication (eMTC) terminal device.

43. A terminal device, characterized in that: include: A first receiving unit is configured to receive a first physical downlink control channel (PDCCH), where the first PDCCH is used to schedule a first transport block (TB), and the first TB corresponds to a first hybrid automatic repeat request (HARQ) process; The first determination unit is used to determine the discontinuous reception DRX behavior of the terminal device according to the mode corresponding to the first HARQ process, wherein the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

44. The terminal device according to claim 43, characterized in that The DRX behavior includes a start time of a first timer, where the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

45. The terminal device according to claim 44, characterized in that If the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, where the first information includes one or more of the following: a transmission time of a first channel, wherein the first channel is carried on the first TB; The timing duration of a first HARQ round trip time (RTT) timer, where the first HARQ RTT timer corresponds to the first HARQ process.

46. ​​The terminal device according to claim 45, characterized in that The first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

47. The terminal device according to claim 46, characterized in that The transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

48. The terminal device according to claim 46 or 47, characterized in that In the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

49. The terminal device according to any one of claims 46 to 48, characterized in that: In the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

50. The terminal device according to claim 45, characterized in that The first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

51. The terminal device according to claim 50, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value.

52. The terminal device according to claim 51, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

53. The terminal device according to claim 52, characterized in that The first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

54. The terminal device according to claim 50, characterized in that When the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

55. The terminal device according to claim 50, characterized in that When the first PDCCH schedules multiple TBs, and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined according to second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: The number of HARQ processes performing HARQ feedback among the multiple HARQ processes; The HARQ feedback modes of the multiple HARQ processes.

56. The terminal device according to claim 55, characterized in that When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

57. The terminal device according to claim 56, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

58. The terminal device according to claim 57, characterized in that The second interval is a time interval between the second time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on the transmission time of the first channel.

59. The terminal device according to claim 55, characterized in that When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined according to the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

60. The terminal device according to any one of claims 45 to 59, characterized in that: The first channel is PDSCH or PUSCH.

61. The terminal device according to claim 47, 53 or 58, characterized in that: The time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

62. The terminal device according to claims 43-61, characterized in that: The service cell of the terminal device is a non-terrestrial communication network NTN cell.

63. The terminal device according to claims 43-62, characterized in that: The terminal device is a narrowband Internet of Things (NB-IoT) terminal device and / or an enhanced machine type communication (eMTC) terminal device.

64. A network device, characterized in that include: A first sending unit is configured to send a first physical downlink control channel PDCCH, where the first PDCCH is used to schedule a first transport block TB, and the first TB corresponds to a first hybrid automatic repeat request HARQ process; The mode corresponding to the first HARQ process is used to determine the discontinuous reception DRX behavior of the terminal device, and the mode corresponding to the first HARQ process includes a first mode and a second mode, and the first mode and the second mode correspond to different DRX behaviors.

65. The network device according to claim 64, characterized in that The DRX behavior includes a start time of a first timer, where the first timer includes a DRX deactivation timer and / or a DRX retransmission timer.

66. The network device according to claim 65, characterized in that If the first HARQ process is in the second mode, the start time of the first timer is determined based on first information, where the first information includes one or more of the following: a transmission time of a first channel, wherein the first channel is carried on the first TB; The timing duration of a first HARQ round trip time (RTT) timer, where the first HARQ RTT timer corresponds to the first HARQ process.

67. The network device according to claim 66, characterized in that The first information includes the transmission time of the first channel, and the first timer is started based on the transmission end time of the first channel.

68. The network device according to claim 67, characterized in that The transmission end time of the first channel is the last time domain unit in the time domain resources occupied by the first channel or the next time domain unit of the last time domain unit in the time domain resources occupied by the first channel.

69. The network device according to claim 67 or 68, characterized in that In the case where the first channel performs repeated transmission, the transmission end time of the first channel is the transmission end time of the last repeated transmission of the first channel.

70. The network device according to any one of claims 67 to 69, characterized in that: In the case where the first PDCCH schedules multiple TBs, the transmission end time of the first channel is the transmission end time of the last TB among the multiple TBs.

71. The network device according to claim 66, wherein: The first information includes a timing duration of the first HARQ RTT timer, and the first timer is started after the first HARQ RTT timer times out.

72. The network device according to claim 71, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value.

73. The network device according to claim 72, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a first interval.

74. The network device according to claim 73, characterized in that The first interval is a time interval between the first time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the first time domain unit is determined based on the transmission time of the first channel.

75. The network device according to claim 71, wherein: When the first TB is an uplink TB, the RTT offset of the first HARQ RTT timer is 0.

76. The network device according to claim 71, characterized in that When the first PDCCH schedules multiple TBs, and the multiple TBs are all downlink TBs, the timing duration of the first HARQ RTT timer is determined according to second information, wherein the multiple TBs correspond to multiple HARQ processes, and the second information includes one or more of the following: The number of HARQ processes performing HARQ feedback among the multiple HARQ processes; The HARQ feedback modes of the multiple HARQ processes.

77. The network device according to claim 76, characterized in that When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is 0, the timing duration of the first HARQ RTT timer is determined according to a predefined value.

78. The network device according to claim 77, characterized in that The timing duration of the first HARQ RTT timer is determined based on a predefined value and a second interval.

79. The network device according to claim 78, characterized in that The second interval is a time interval between the second time domain unit and the first time domain unit corresponding to the next PDCCH monitoring opportunity, wherein the second time domain unit is determined based on the transmission time of the first channel.

80. The network device according to claim 76, wherein: When the number of HARQ processes performing HARQ feedback in the multiple HARQ processes is greater than 0, the timing duration of the first HARQ RTT timer is determined according to the HARQ feedback mode of the multiple HARQ processes and the number of HARQ processes performing HARQ feedback in the multiple HARQ processes.

81. The network device according to any one of claims 64 to 80, characterized in that: The first channel is PDSCH or PUSCH.

82. The network device according to claim 68, 74 or 79, characterized in that The time domain unit is any one of the following: a subframe, a time slot, or one or more symbols.

83. The network device according to claim 64-82, characterized in that The service cell of the terminal device is a non-terrestrial communication network NTN cell.

84. The network device according to claims 64-83, characterized in that The terminal device is a narrowband Internet of Things (NB-IoT) terminal device and / or an enhanced machine type communication (eMTC) terminal device.

85. A terminal, characterized in that The terminal comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so as to enable the terminal to execute the method according to any one of claims 1 to 21.

86. A network device, characterized in that The network device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so as to enable the network device to execute the method according to any one of claims 22 to 42.

87. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 21.

88. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the device to execute the method according to any one of claims 22 to 42.

89. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 21.

90. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 22 to 42.

91. A computer-readable storage medium, characterized in that A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 to 21.

92. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 22 to 42.

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

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

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

96. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 22 to 42.