Wireless communication method, terminal device and network device

Abstract

Embodiments of the present application provide a wireless communication method, a terminal device and a network device. The method comprises: receiving, by the terminal device, DRX configuration information. The DRX configuration information comprises: configuration information of a first timer. The first timer is a timer set for receiving an advanced uplink scheduling grant in a first PDCCH within an RTT. During running of the first timer, the terminal device is in a DRX active period. Therefore, the uplink data transmission efficiency can be improved.

Description

Technical Field

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

[0002] In New Radio (NR), a network device can configure discontinuous reception (DRX) for a terminal device, allowing the terminal device to monitor the physical downlink control channel (PDCCH) during the DRX active time. The DRX configuration information configured by the network device for the terminal device includes the timers drx-HARQ-RTT-TimerUL and drx-RetransmissionTimerUL.

[0003] In the uplink hybrid automatic repeat request (HARQ), after the terminal device completes the first repetition of the physical uplink shared channel (PUSCH), it starts the timer drx-HARQ-RTT-TimerUL corresponding to the HARQ process. After the timer drx-HARQ-RTT-TimerUL times out, the terminal device starts the timer drx-RetransmissionTimerUL corresponding to the HARQ process. The length of the drx-HARQ-RTT-TimerUL is related to the round-trip time (RTT) between the terminal device and the network device. It can be seen that the network device will decide whether to schedule the initial transmission or retransmission based on the PUSCH decoding result. The terminal device will wait for at least one RTT between the terminal device and the network device before receiving the scheduling indication for the initial transmission or retransmission.

[0004] In non-terrestrial networks (NTNs), the RTT is much longer than that of terrestrial networks (TNs). Therefore, if the current DRX configuration is still used in NTNs, it will inevitably lead to low uplink data transmission efficiency. Summary of the Invention

[0005] The embodiments of the present application provide a wireless communication method, a terminal device, and a network device, thereby improving the efficiency of uplink data transmission.

[0006] In a first aspect, a wireless communication method is provided, comprising: receiving DRX configuration information. The DRX configuration information includes configuration information of a first timer. The first timer is a timer set to enable receipt of an advance uplink scheduling grant within a first PDCCH within an RTT. While the first timer is running, the terminal device is in a DRX activation period.

[0007] In a second aspect, a wireless communication method is provided, comprising: sending DRX configuration information to a terminal device. The DRX configuration information includes configuration information of a first timer. The first timer is a timer set to enable receipt of an advance uplink scheduling grant within a first PDCCH within an RTT. While the first timer is running, the terminal device is in a DRX activation period.

[0008] In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or its various implementations.

[0009] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.

[0010] In a fourth aspect, a network device is provided for executing the method in the above second aspect or its various implementations.

[0011] Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.

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

[0013] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of the second aspect or its respective implementations.

[0014] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above or in each of their implementations.

[0015] Specifically, the apparatus includes: a processor for calling and running a computer program from a memory, so that a device equipped with the apparatus executes the method of any one of the first to second aspects or their respective implementations.

[0016] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method of any one of the first to second aspects or their respective implementations.

[0017] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method of any one of the first to second aspects or their respective implementations.

[0018] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method of any one of the first to second aspects or their respective implementations.

[0019] In the present application, the DRX configuration information may include the configuration information of the first timer as above. Based on this, the terminal device can receive an advance uplink scheduling authorization within the RTT without waiting for the RTT or exceeding the RTT to obtain the uplink scheduling authorization, thereby improving the transmission efficiency of the uplink data. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A schematic diagram of the architecture of an NTN system provided in an embodiment of the present application;

[0021] Figure 2 A schematic diagram of the architecture of another NTN system provided in an embodiment of the present application;

[0022] Figure 3 An interactive flow chart of a wireless communication method provided in an embodiment of the present application;

[0023] Figure 4 A schematic diagram of the time relationship of various timers provided in an embodiment of the present application;

[0024] Figure 5 Another schematic diagram of the time relationship of each timer provided in an embodiment of the present application;

[0025] Figure 6 A schematic diagram of another time relationship of various timers provided in an embodiment of the present application;

[0026] Figure 7 A schematic diagram of another time relationship of various timers provided in an embodiment of the present application;

[0027] Figure 8 8 shows a schematic block diagram of a terminal device 800 according to an embodiment of the present application;

[0028] Figure 9 1 shows a schematic block diagram of a network device 900 according to an embodiment of the present application;

[0029] Figure 10 1 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application;

[0030] Figure 11 is a schematic structural diagram of a device according to an embodiment of the present application;

[0031] Figure 12 It is a schematic block diagram of a communication system 1200 provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0033] Before introducing the technical solution of this application, the following is an explanation of the relevant knowledge of this application:

[0034] 1. Background of NTN

[0035] The Third Generation Partnership Project (3GPP) is currently researching NTN technology. NTN generally uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts where communication equipment cannot be deployed or where there is a sparse population. However, satellite communications, because a single satellite can cover a large area and orbits the Earth, theoretically every corner of the globe can be covered. Second, satellite communications have significant social value. Satellite communications can provide low-cost coverage in remote mountainous areas and poor, underdeveloped countries or regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting their development. Third, satellite communications offer long range, and the cost of communications does not increase significantly with increasing distance. Finally, satellite communications are highly stable and unaffected by natural disasters.

[0036] Communication satellites are categorized by their orbital altitude into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), Geostationary Earth Orbit (GEO), and High Elliptical Orbit (HEO). Currently, research focuses on LEO and GEO.

[0037] LEO

[0038] Low-orbit satellites have an altitude range of 500 km to 1500 km, with an orbital period of approximately 1.5 to 2 hours. The signal propagation delay for single-hop communication between users is typically less than 20 milliseconds. 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.

[0039] GEO

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

[0041] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0042] 5G NR DRX

[0043] In 5G NR, network equipment can configure the DRX function for terminal devices, so that the terminal can monitor the PDCCH discontinuously to achieve the purpose of terminal power saving. In NR version (Release, Rel) 15, each Media Access Control (MAC) entity has a DRX configuration. The DRX configuration parameters include:

[0044] drx-onDurationTimer: The duration of the terminal device waking up at the beginning of a DRX cycle;

[0045] drx-SlotOffset: The delay for the terminal device to start drx-onDurationTimer;

[0046] drx-InactivityTimer: When the terminal device receives a PDCCH indicating an initial uplink transmission or an initial downlink transmission, the terminal device continues to monitor the PDCCH for a certain duration.

[0047] drx-RetransmissionTimerDL: The maximum duration that the terminal device monitors the PDCCH indicating downlink retransmission scheduling. Each downlink HARQ process except the broadcast HARQ process corresponds to one drx-RetransmissionTimerDL;

[0048] drx-RetransmissionTimerUL: The maximum duration that the terminal device monitors the PDCCH indicating uplink HARQ retransmission scheduling. Each uplink HARQ process corresponds to one drx-RetransmissionTimerUL;

[0049] drx-LongCycleStartOffset: used to configure the long DRX cycle, as well as the subframe offset at the start of the long DRX cycle and the short DRX cycle.

[0050] drx-ShortCycle: DRX short cycle, optional configuration;

[0051] drx-ShortCycleTimer: The duration of the terminal device in the DRX short cycle and no PDCCH is received. It is an optional configuration;

[0052] drx-HARQ-RTT-TimerDL: The minimum waiting time that the terminal device expects to receive the PDCCH indicating downlink scheduling. Each downlink HARQ process other than the broadcast HARQ process corresponds to one drx-HARQ-RTT-TimerDL;

[0053] drx-HARQ-RTT-TimerUL: The minimum waiting time required for the terminal device to receive the PDCCH indicating uplink HARQ retransmission scheduling. Each uplink HARQ process corresponds to one drx-HARQ-RTT-TimerUL.

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

[0055] Any one of the five timers drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL and ra-ContentionResolutionTimer is running.

[0056] The SR is sent on PUCCH and is in pending state.

[0057] In the contention-based random access procedure, the terminal device has not received a PDCCH indication scrambled with a Cell-Radio Network Temporary Identifier (C-RNTI) for an initial transmission after successfully receiving a random access response.

[0058] The conditions for the terminal to start and stop the drx-RetransmissionTimerUL are as follows: when the terminal device receives a PDCCH indicating an uplink transmission, or when the terminal device transmits a MAC Protocol Data Unit (PDU) on the configured uplink grant resource, the terminal stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first repeated transmission of PUSCH (i.e., HARQ retransmission). If the timer drx-HARQ-RTT-TimerUL expires, the terminal device starts the drx-RetransmissionTimerUL corresponding to the HARQ process.

[0059] As described above, the time length of the drx-HARQ-RTT-TimerUL is related to the RTT between the terminal device and the network device. Therefore, the network device will determine whether to schedule the initial transmission or retransmission based on the PUSCH decoding result, and the terminal device will wait for at least one RTT between the terminal device and the network device to receive the scheduling indication of the initial transmission or retransmission. In the NTN network, the RTT is much larger than that of the TN. Therefore, if the current DRX configuration is still used in the NTN, it will inevitably cause the problem of low efficiency of uplink data transmission.

[0060] To solve this technical problem, in the present application, the network device can configure the terminal device with a timer which is a timer set for receiving an uplink scheduling grant in advance within the RTT.

[0061] The following will be described in combination with Figure 1 and Figure 2 , describes the architecture of the NTN system in this application.

[0062] Figure 1 This is a schematic diagram of the architecture of an NTN system provided in an embodiment of the present application. Figure 1 , including terminal device 1101 and satellite 1102, terminal device 1101 and satellite 1102 can communicate wirelessly. The network formed between terminal device 1101 and satellite 1102 can also be called NTN. Figure 1 In the illustrated communication system architecture, satellite 1102 can function as a base station, enabling direct communication between terminal device 1101 and satellite 1102. In this system architecture, satellite 1102 can be referred to as a network device. Optionally, the communication system can include multiple network devices 1102, and each network device 1102 can include a different number of terminal devices within its coverage area, although this is not limited in this embodiment of the present application.

[0063] Figure 2 This is a schematic diagram of another NTN system architecture provided in an embodiment of the present application. Figure 2 , including terminal equipment 1201, satellite 1202 and base station 1203, terminal equipment 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 and base station 1203 can communicate. The network formed by terminal equipment 1201, satellite 1202 and base station 1203 can also be called NTN. Figure 2 In the illustrated communication system architecture, satellite 1202 may not function as a base station, and communication between terminal device 1201 and base station 1203 must be relayed through satellite 1202. In this system architecture, base station 1203 may be referred to as a network device. Optionally, the communication system may include multiple network devices 1203, and each network device 1203 may include a different number of terminal devices within its coverage area, although this is not limited in this embodiment of the present application.

[0064] Optionally, Figure 1 、 Figure 2 The wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this embodiment of the present application does not limit this.

[0065] It should be understood that the terms "system" and "network" are often used interchangeably herein.

[0066] It should be understood that, in the NTN, due to the RTT in the NTN being much larger than that in the NR, and the number of uplink HARQ processes cannot be increased substantially accordingly, the existing HARQ mechanism has a problem of HARQ stalling, that is, all uplink HARQ processes corresponding to the timers drx-HARQ-RTT-TimerUL are in a running state, and there is no idle uplink HARQ process available for uplink transmission. In order to realize continuous data transmission of the NTN system and improve the throughput, the current standard discusses "disabling UL HARQ retransmission". Therefore, the terminal device in the embodiments of the present application can be such a terminal device that disables the uplink HARQ retransmission, and the present application does not limit this.

[0067] The technical solutions of the present application will be described in detail below:

[0068] Figure 3 An interaction flowchart of a wireless communication method provided by the embodiments of the present application is shown in FIG. 1, and the method comprises the following steps: Figure 3

[0069] S310: The network device sends DRX configuration information to the terminal device. The DRX configuration information comprises configuration information of a first timer.

[0070] It should be understood that the first timer is a timer set for receiving an advanced uplink scheduling grant (UL grant) in the first PDCCH within the RTT. During the running of the first timer, the terminal device is in the DRX active period, that is, during the running of the first timer, the terminal device can listen to the first PDCCH.

[0071] It should be understood that the advanced uplink scheduling grant refers to the uplink scheduling grant received within the RTT. The above-mentioned first PDCCH refers to the PDCCH used to carry the advanced uplink scheduling grant.

[0072] It should be understood that the RTT refers to the RTT between the terminal device and the network device.

[0073] It should be understood that the DRX configuration information can comprise other configuration information such as drx-onDurationTimer, drx-SlotOffset, etc. in addition to the configuration information of the first timer described above. The present application will not repeat the details.

[0074] ​Optionally, at the end time of the first repeated transmission of the PUSCH (i.e., HARQ retransmission), the terminal device may start a first timer. During the operation of the first timer, the terminal device monitors the first PDCCH to obtain an advance uplink scheduling grant, and performs uplink data transmission according to the advance uplink scheduling grant.

[0075] Optionally, the above-mentioned DRX configuration information may be carried in any one of the following items, but not limited thereto: signaling involved in a radio resource control (RRC) establishment process, RRC reconfiguration signaling, RRC recovery signaling, etc.

[0076] In summary, in this application, the DRX configuration information may include the configuration information of the first timer as described above. Based on this, the terminal device can receive an advance uplink scheduling authorization within the RTT, without having to wait for the RTT or a duration exceeding the RTT to obtain the uplink scheduling authorization, thereby improving the transmission efficiency of uplink data. Furthermore, through the technical solution of this application, the terminal device can simultaneously support uplink HARQ retransmission scheduling based on or not based on PUSCH decoding results when dynamically scheduling uplink transmission.

[0077] Optionally, the DRX configuration information further includes configuration information of a second timer. The second timer is used to set the minimum waiting time required for the terminal device to receive a non-advance uplink scheduling authorization in the second PDCCH. That is, the second timer here is the timer drx-HARQ-RTT-TimerUL in the standard.

[0078] It should be understood that the current standard does not mention advance uplink scheduling grants. Therefore, the definition of the second timer in the current standard is: the minimum waiting time required for the terminal device to receive the PDCCH indicating uplink HARQ retransmission scheduling. In this application, in order to distinguish between advance and non-advance uplink scheduling grants, the definition of the second timer has been adjusted, but its actual meaning remains the same as in the current standard.

[0079] It should be understood that in the present application, since the uplink scheduling grant is applied in the HARQ retransmission scenario, the PDCCH indicating uplink HARQ retransmission scheduling is the above-mentioned PDCCH carrying the uplink scheduling grant.

[0080] Optionally, the DRX configuration information further includes configuration information of a third timer. The third timer is used to set the maximum duration for the terminal device to monitor the second PDCCH. That is, the third timer here is the timer drx-RetransmissionTimerUL in the standard.

[0081] Optionally, when the second timer times out, the terminal device starts a third timer. That is, when the second timer times out, the terminal device starts the third timer. During the operation of the third timer, the terminal device monitors the second PDCCH.

[0082] Optionally, the duration of the first timer may be the same as or different from the duration of the third timer, and this application does not impose any limitation on this.

[0083] It should be understood that, in the present application, the difference between the first PDCCH and the second PDCCH is that the first PDCCH carries an advance uplink scheduling grant, while the second PDCCH carries a non-advance uplink scheduling grant.

[0084] It should be noted that the above-mentioned first timer, second timer and third timer correspond to the same HARQ process, and they can also be called the first timer corresponding to the HARQ process, the second timer corresponding to the HARQ process and the third timer corresponding to the HARQ process.

[0085] As described above, the RTT in NTN is much greater than the RTT in NR. Therefore, in order to adapt to the RTT in NTN, this application introduces a relevant time offset for the second timer, which is specifically illustrated by the following example:

[0086] Example 1: Figure 4 A schematic diagram of the time relationship of each timer provided in the embodiment of the present application is shown as follows: Figure 4 As shown, at the end time of the first repeated transmission of the PUSCH, the terminal device can start the first timer. The terminal device uses the end time of the first repeated transmission of the PUSCH as the starting time and starts the second timer after the first time offset. That is, the time interval between the start time of the first timer and the second timer is the first time offset. When the second timer times out, the terminal device can start the third timer.

[0087] Optionally, if the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in an unstarted state, the terminal device stops the first timer. If the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in a running state, the first timer and the second timer are stopped. If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the third timer is stopped.

[0088] Example 2: Figure 5 Another time relationship diagram of each timer provided in the embodiment of the present application is as follows: Figure 5As shown, at the end time of the first repeated transmission of the PUSCH, the terminal device can start the first timer and the second timer at the same time. The duration of the second timer is the sum of the default duration of the second timer and the first time offset. When the second timer times out, the terminal device can start the third timer.

[0089] It should be understood that the default duration of the second timer is the duration of the second timer in the TN, and since the RTT in the NTN is much greater than the RTT in the TN, in the present application, a first time offset is added to the default duration of the second timer to form the duration of the second timer in the NTN.

[0090] Optionally, if the terminal device receives an advance uplink scheduling grant in the first PDCCH, the terminal device stops the first timer and the second timer. If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the terminal device stops the third timer.

[0091] Optionally, the first time offset is RTT.

[0092] Optionally, the terminal device can determine the RTT based on at least one of the following information, but not limited to: ephemeris information of the NTN cell where the terminal device is located, delay information of the feeder link from the satellite to the ground network, common timing advance (TA), and location information of the terminal device obtained through the Global Navigation Satellite System (GNSS).

[0093] Optionally, the delay information of the feeder link may be the delay on the feeder link, or factors or parameter information causing the delay on the feeder link, etc., and this application does not impose any restrictions on this.

[0094] Optionally, at least one of the ephemeris information of the NTN cell where the terminal device is located, the delay information of the feeder link from the satellite to the ground network, and the public TA can be carried in the broadcast message sent by the network device or the RRC dedicated signaling. This application does not impose any restrictions on this.

[0095] It should be noted that this application does not limit how to determine the RTT based on at least one of the ephemeris information of the NTN cell where the terminal device is located, the delay information of the feeder link from the satellite to the ground network, the public TA, and the location information of the terminal device.

[0096] Example 3: Figure 6 Another time relationship diagram of each timer provided in the embodiment of the present application is as follows: Figure 6As shown, at the end time of the first repeated transmission of the PUSCH, the terminal device can start the first timer. The terminal device uses the timeout time of the first timer as the starting time and starts the second timer after the second time offset. When the second timer times out, the terminal device can start the third timer.

[0097] Optionally, if the terminal device receives an advance uplink scheduling grant in the first PDCCH, the first timer is stopped. If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the third timer is stopped.

[0098] Example 4: Figure 7 Another time relationship diagram of each timer provided in the embodiment of the present application is as follows: Figure 7 As shown, at the end time of the first repeated transmission of the PUSCH, the terminal device can start a first timer. When the first timer expires, the terminal device starts a second timer. The duration of the second timer is the sum of the default duration of the second timer and the second time offset. When the second timer times out, the terminal device can start a third timer.

[0099] Optionally, if the terminal device receives an advance uplink scheduling grant in the first PDCCH, the first timer is stopped. If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the third timer is stopped.

[0100] It should be understood that the default duration of the second timer can be referred to above, and this application will not elaborate on it.

[0101] Optionally, the second time offset is the difference between the RTT and the duration of the first timer.

[0102] It should be understood that the calculation method of RTT can be referred to above, and this application will not go into details.

[0103] For Examples 1-4, it should be understood that the terminal device is in the DRX activation period during the operation phases of the first timer and the third timer, that is, the terminal device can monitor the PDCCH during the operation phases of the first timer and the third timer.

[0104] In summary, this application introduces a relevant time offset for the second timer, thereby adapting to the RTT in the NTN. Furthermore, this application does not need to increase the value range of the third timer. During the operation of the third timer, the terminal device needs to monitor the PDCCH. However, this application adds the above-mentioned first time offset or second time offset. Within the first time offset or second time offset, the terminal device does not need to monitor the PDCCH. Therefore, compared with the method of increasing the value range of the third timer, the technical solution of this application can achieve the purpose of power saving for the terminal device.

[0105] Combined with the above Figures 3 to 7 , describes the method embodiment of the present application in detail, and the following is combined with Figures 8 to 12 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0106] Figure 8 FIG shows a schematic block diagram of a terminal device 800 according to an embodiment of the present application. Figure 8 As shown, the terminal device 800 includes: a communication unit 810, which is used to receive DRX configuration information. The DRX configuration information includes: configuration information of a first timer. The first timer is a timer set to enable the reception of an advance uplink scheduling authorization in the first PDCCH within the RTT. During the operation of the first timer, the terminal device is in a DRX activation period.

[0107] Optionally, the terminal device 800 further includes: a processing unit 820, configured to: start a first timer at the end time of the first repeated transmission of the PUSCH, and monitor the first PDCCH during the running of the first timer.

[0108] Optionally, the DRX configuration information further includes: configuration information of a second timer. The second timer is used to set a minimum waiting time required for the terminal device to receive a non-advance uplink scheduling grant in the second PDCCH.

[0109] Optionally, the processing unit 820 is further configured to: obtain a first time offset, and start a second timer after the first time offset, with the end time of the first repeated transmission of the PUSCH as the starting time.

[0110] Optionally, the processing unit 820 is further configured to: if the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in an unstarted state, stop the first timer; if the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in a running state, stop the first timer and the second timer.

[0111] Optionally, the processing unit 820 is further configured to: obtain a first time offset, and simultaneously start a second timer when starting the first timer, wherein the duration of the second timer is the sum of a default duration of the second timer and the first time offset.

[0112] Optionally, the processing unit 820 is further configured to: stop the first timer and the second timer if the terminal device receives an advance uplink scheduling authorization in the first PDCCH.

[0113] Optionally, the first time offset is RTT.

[0114] Optionally, the processing unit 820 is further configured to: obtain a second time offset, start the second timer after the second time offset, and take the timeout time of the first timer as the starting time.

[0115] Optionally, the processing unit 820 is further configured to: obtain a second time offset, and start a second timer at the time when the first timer expires, wherein the duration of the second timer is the sum of a default duration of the second timer and the second time offset.

[0116] Optionally, the processing unit 820 is further configured to: stop the first timer if the terminal device receives an advance uplink scheduling authorization in the first PDCCH.

[0117] Optionally, the second time offset is the difference between the RTT and the duration of the first timer.

[0118] Optionally, the DRX configuration information further includes: configuration information of a third timer. The third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH.

[0119] Optionally, the processing unit 820 is further configured to: start a third timer when the second timer expires, and monitor the second PDCCH while the third timer is running.

[0120] Optionally, the processing unit 820 is further configured to: stop the third timer if the terminal device receives a non-advance uplink scheduling authorization in the second PDCCH.

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

[0122] It should be understood that the terminal device 800 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above and other operations and / or functions of each unit in the terminal device 800 are respectively for implementing Figure 3 For the sake of brevity, the corresponding processes of the terminal device in the method shown are not repeated here.

[0123] Figure 9 FIG. 1 shows a schematic block diagram of a network device 900 according to an embodiment of the present application. Figure 9As shown, the network device 900 includes: a communication unit 910, configured to send DRX configuration information to a terminal device. The DRX configuration information includes: configuration information of a first timer. The first timer is a timer set to enable the receipt of an advance uplink scheduling grant in a first PDCCH within an RTT. While the first timer is running, the terminal device is in a DRX activation period.

[0124] Optionally, the DRX configuration information further includes: configuration information of a second timer. The second timer is used to set a minimum waiting time required for the terminal device to receive a non-advance uplink scheduling grant in the second PDCCH.

[0125] Optionally, the DRX configuration information further includes: configuration information of a third timer. The third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH.

[0126] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0127] It should be understood that the network device 900 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above and other operations and / or functions of each unit in the network device 900 are respectively to implement Figure 3 For the sake of brevity, the corresponding processes of the network devices in the method shown are not repeated here.

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

[0129] Alternatively, as Figure 10 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 may call and execute a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0130] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0131] Alternatively, as Figure 10 As shown, the communication device 1000 may further include a transceiver 1030 , and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

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

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

[0135] Figure 11 It is a schematic structural diagram of the device of an embodiment of the present application. Figure 11 The device 1100 shown includes a processor 1110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0136] Alternatively, as Figure 11 As shown, the apparatus 1100 may further include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0137] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0138] Optionally, the apparatus 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0139] Optionally, the apparatus 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

[0141] Optionally, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding procedures implemented by the terminal device in each method of the embodiments of the present application. For brevity, details are not described herein.

[0142] Optionally, the apparatus mentioned in the embodiments of the present application can also be a chip. For example, it can be a system chip, a system chip, a chip system, or a system-on-chip chip, etc.

[0143] Figure 12 is a schematic block diagram of a communication system 1200 provided by the embodiments of the present application. As shown in the figure, the communication system 1200 includes a terminal device 1210 and a network device 1220. Figure 12

[0144] The terminal device 1210 can be used to implement the corresponding functions of the terminal device in the above methods, and the network device 1220 can be used to implement the corresponding functions of the network device or base station in the above methods. For brevity, details are not described herein.

[0145] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method embodiments can be completed by integrated logic circuits or instructions in the form of software in the processor. The processor mentioned above can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. Each method, step and logic block disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can be any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware code processor for execution, or a combination of hardware and software modules in the code processor for execution. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, or other mature storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.

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

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

[0148] The embodiment of the present application further provides a computer readable storage medium for storing the computer program.

[0149] Optionally, the computer readable storage medium can be applied to the network device or the base station in the embodiment of the present application, and the computer program makes the computer execute the corresponding procedures implemented by the network device or the base station in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0150] Optionally, the computer readable storage medium can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program makes the computer execute the corresponding procedures implemented by the mobile terminal / terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0151] The embodiment of the present application further provides a computer program product comprising computer program instructions.

[0152] Optionally, the computer program product can be applied to the network device or the base station in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding procedures implemented by the network device or the base station in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0153] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding procedures implemented by the mobile terminal / terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0154] The embodiment of the present application further provides a computer program.

[0155] Optionally, the computer program can be applied to the network device or the base station in the embodiment of the present application, and when the computer program runs on the computer, the computer program makes the computer execute the corresponding procedures implemented by the network device or the base station in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0156] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiment of the present application, and when the computer program runs on the computer, the computer program makes the computer execute the corresponding procedures implemented by the mobile terminal / terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

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

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

[0159] 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.

[0160] 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.

[0161] 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.

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

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

Claims

1. A wireless communication method, characterized in that: include: Receiving discontinuous reception (DRX) configuration information; The DRX configuration information includes: configuration information of a first timer; the first timer is a timer set to enable receiving an advance uplink scheduling grant in a first physical downlink control channel (PDCCH) within a round-trip transmission time (RTT); the advance uplink scheduling grant is an uplink scheduling grant received within the RTT; while the first timer is running, the terminal device is in a DRX activation period; The method further comprises: At the end time of the first repeated transmission of the physical uplink shared channel PUSCH, starting the first timer; The DRX configuration information further includes: configuration information of a second timer; the second timer is used to set a minimum waiting time required for the terminal device to expect to receive a non-advance uplink scheduling grant in the second PDCCH, wherein the start time of the second timer is the same as or after the first timer, wherein the second timer is drx-HARQ-RTT-TimerUL; The DRX configuration information further includes: configuration information of a third timer; the third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH; The method further comprises: When the second timer expires, start the third timer; The third timer is drx-RetransmissionTimerUL.

2. The method according to claim 1, characterized in that Also includes: While the first timer is running, the first PDCCH is monitored.

3. The method according to claim 1, characterized in that Also includes: Get the first time offset; The second timer is started after the first time offset, with the end time of the first repeated transmission of the PUSCH as the starting time.

4. The method according to claim 3, characterized in that Also includes: If the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in an inactive state, stopping the first timer; If the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in a running state, the first timer and the second timer are stopped.

5. The method according to claim 1, wherein Also includes: Get the first time offset; simultaneously starting the first timer, and starting the second timer; The duration of the second timer is the sum of a default duration of the second timer and the first time offset.

6. The method according to claim 5, characterized in that Also includes: If the terminal device receives an advance uplink scheduling authorization in the first PDCCH, the first timer and the second timer are stopped.

7. The method according to any one of claims 3 to 6, characterized in that: The first time offset is the RTT.

8. The method according to claim 1, characterized in that Also includes: Obtaining a second time offset; The second timer is started after the second time offset, with the timeout time of the first timer as the starting time.

9. The method according to claim 1, characterized in that Also includes: Obtaining a second time offset; When the first timer expires, start the second timer; The duration of the second timer is the sum of the default duration of the second timer and the second time offset.

10. The method according to claim 8, characterized in that Also includes: If the terminal device receives an advance uplink scheduling authorization in the first PDCCH, the first timer is stopped.

11. The method according to any one of claims 8 to 10, characterized in that: The second time offset is a difference between the RTT and a duration of the first timer.

12. The method according to claim 1, characterized in that Also includes: While the third timer is running, the second PDCCH is monitored.

13. The method according to claim 1 or 12, characterized in that Also includes: If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the third timer is stopped.

14. A wireless communication method, characterized in that: include: Send DRX configuration information to the terminal device; The DRX configuration information includes: configuration information of a first timer; the first timer is a timer set to enable receiving an advance uplink scheduling grant in a first PDCCH within an RTT; the advance uplink scheduling grant is an uplink scheduling grant received within the RTT; during the operation of the first timer, the terminal device is in a DRX activation period; The first timer is started at the end time of the first repeated transmission of the physical uplink shared channel PUSCH; The DRX configuration information further includes: configuration information of a second timer; the second timer is used to set a minimum waiting time required for the terminal device to expect to receive a non-advance uplink scheduling grant in the second PDCCH, wherein the start time of the second timer is the same as or after the first timer, wherein the second timer is drx-HARQ-RTT-TimerUL; The DRX configuration information further includes: configuration information of a third timer; the third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH; The third timer is started at the timeout period of the second timer, and the third timer is drx-RetransmissionTimerUL.

15. A terminal device, characterized in that: include: a communication unit, configured to receive DRX configuration information; The DRX configuration information includes: configuration information of a first timer; the first timer is a timer set to enable receiving an advance uplink scheduling grant in a first PDCCH within an RTT; the advance uplink scheduling grant is an uplink scheduling grant received within the RTT; during the operation of the first timer, the terminal device is in a DRX activation period; The terminal device further includes a processing unit, which is configured to: At the end time of the first repeated transmission of the PUSCH, starting the first timer; The DRX configuration information further includes: configuration information of a second timer; the second timer is used to set a minimum waiting time required for the terminal device to expect to receive a non-advance uplink scheduling grant in the second PDCCH, wherein the start time of the second timer is the same as or after the first timer, wherein the second timer is drx-HARQ-RTT-TimerUL; The DRX configuration information further includes: configuration information of a third timer; the third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH; The processing unit is further configured to: When the second timer expires, start the third timer; The third timer is drx-RetransmissionTimerUL.

16. The terminal device according to claim 15, characterized in that The processing unit is further configured to: monitor the first PDCCH while the first timer is running.

17. The terminal device according to claim 15, characterized in that The processing unit is further configured to: Get the first time offset; The second timer is started after the first time offset, with the end time of the first repeated transmission of the PUSCH as the starting time.

18. The terminal device according to claim 17, characterized in that The processing unit is further configured to: If the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in an inactive state, stopping the first timer; If the terminal device receives an advance uplink scheduling grant in the first PDCCH and the second timer is in a running state, the first timer and the second timer are stopped.

19. The terminal device according to claim 15, characterized in that The processing unit is further configured to: Get the first time offset; simultaneously starting the first timer, and starting the second timer; The duration of the second timer is the sum of a default duration of the second timer and the first time offset.

20. The terminal device according to claim 19, characterized in that The processing unit is further configured to: If the terminal device receives an advance uplink scheduling authorization in the first PDCCH, the first timer and the second timer are stopped.

21. The terminal device according to any one of claims 17 to 20, characterized in that: The first time offset is the RTT.

22. The terminal device according to claim 15, characterized in that The processing unit is further configured to: Obtaining a second time offset; The second timer is started after the second time offset, with the timeout time of the first timer as the starting time.

23. The terminal device according to claim 15, characterized in that The processing unit is further configured to: Obtaining a second time offset; When the first timer expires, start the second timer; The duration of the second timer is the sum of the default duration of the second timer and the second time offset.

24. The terminal device according to claim 22, characterized in that The processing unit is further configured to: If the terminal device receives an advance uplink scheduling authorization in the first PDCCH, the first timer is stopped.

25. The terminal device according to any one of claims 22 to 24, characterized in that: The second time offset is a difference between the RTT and a duration of the first timer.

26. The terminal device according to claim 15, characterized in that The processing unit is further configured to: While the third timer is running, the second PDCCH is monitored.

27. The terminal device according to claim 15 or 26, characterized in that: The processing unit is further configured to: If the terminal device receives a non-advance uplink scheduling grant in the second PDCCH, the third timer is stopped.

28. A network device, characterized in that: include: A communication unit, configured to send DRX configuration information to a terminal device; The DRX configuration information includes: configuration information of a first timer; the first timer is a timer set to enable receiving an advance uplink scheduling grant in a first PDCCH within an RTT; the advance uplink scheduling grant is an uplink scheduling grant received within the RTT; during the operation of the first timer, the terminal device is in a DRX activation period; The first timer is started at the end time of the first repeated transmission of the physical uplink shared channel PUSCH; The DRX configuration information further includes: configuration information of a second timer; the second timer is used to set a minimum waiting time required for the terminal device to expect to receive a non-advance uplink scheduling grant in the second PDCCH, wherein the start time of the second timer is the same as or after the first timer, wherein the second timer is drx-HARQ-RTT-TimerUL; The DRX configuration information further includes: configuration information of a third timer; the third timer is used to set a maximum duration for the terminal device to monitor the second PDCCH; The third timer is started at the timeout period of the second timer, and the third timer is drx-RetransmissionTimerUL.

29. A terminal device, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method according to any one of claims 1 to 13.

30. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to claim 14.

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

32. A device, characterized in that include: A processor is configured to call and execute a computer program from a memory, so that a device equipped with the apparatus executes the method according to claim 14.

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

34. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to claim 14.

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

36. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to perform the method as claimed in claim 14 .

Images