WO2020077643A1

WO2020077643A1 - Wireless communication method and terminal device

Info

Publication number: WO2020077643A1
Application number: PCT/CN2018/111102
Authority: WO
Inventors: 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2018-10-19
Filing date: 2018-10-19
Publication date: 2020-04-23
Also published as: CN111869314B; CN111869314A

Abstract

Embodiments of the present application provide a wireless communication method and a terminal device. The duration of monitoring a PDCCH can be reduced, so as to achieve the purpose of power saving. The method comprises: a terminal device sends a scheduling request to a network device; an MAC entity of the terminal device determines whether to start to enter active time of a DRX cycle after the scheduling request is sent, wherein the DRX cycle is configured to the MAC entity of the terminal device.

Description

Wireless communication method and terminal equipment

Technical field

Embodiments of the present application relate to the field of communications, and more specifically, to wireless communication methods and terminal devices.

Background technique

In a Long Term Evolution (LTE) or New Radio (NR) system, if a terminal device sends a scheduling request (Scheduling Request, SR) to request an uplink grant, the terminal device will start monitoring the physical downlink control channel (Physical Downlink Control Channel, PDCCH) to obtain a grant from the network device to the terminal device. If the terminal device is configured with a discontinuous reception (DRX) cycle, regardless of whether the terminal device is in the active period of the DRX cycle or the inactive period of the DRX cycle, after sending the SR, the terminal Devices need to enter the active time of the DRX cycle.

Summary of the invention

The embodiments of the present application provide a wireless communication method and a terminal device, which can reduce the time for monitoring the PDCCH, thereby achieving the purpose of saving power.

In a first aspect, a wireless communication method is provided. The method includes:

The terminal device sends a scheduling request to the network device;

After sending the scheduling request, the Media Access Control (MAC) entity of the terminal device determines whether to enter the activation period of the DRX cycle, where the MAC entity of the terminal device is configured DRX cycle.

It should be noted that after the MAC entity of the terminal device enters the active period of the DRX cycle, the terminal device needs to monitor the PDCCH.

In a second aspect, a terminal device is provided for performing the method in the first aspect.

Specifically, the terminal device includes a functional module for performing the method in the first aspect described above.

In a third aspect, a terminal device is provided, including a processor and a memory. 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 execute the method in the first aspect.

In a fourth aspect, a chip is provided for implementing the method in the first aspect.

Specifically, the chip includes a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the method as described in the first aspect above.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, which causes the computer to execute the method in the first aspect described above.

According to a sixth aspect, there is provided a computer program product, including computer program instructions, the computer program instructions causing a computer to perform the method in the first aspect described above.

In a seventh aspect, a computer program is provided, which when run on a computer, causes the computer to execute the method in the first aspect described above.

Through the above technical solution, after sending the scheduling request, the MAC entity of the terminal device can determine whether to enter the active period of the DRX cycle, and only enter the active period of the DRX cycle when the PDCCH needs to be monitored, thereby avoiding unnecessary PDCCH monitoring , To reduce the time of monitoring PDCCH, and then achieve the purpose of power saving.

BRIEF DESCRIPTION

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

2 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

FIG. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.

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

FIG. 5 is a schematic block diagram of a chip according to an embodiment of the present application.

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

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of this application.

The embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (Wideband Code) Division Multiple Access (WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, new wireless (New Radio, NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (WiFi), next-generation communication system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, device to device (Device to Device, D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and vehicle-to-vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communications system.

Optionally, the communication system in the embodiments of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) configuration. Web scene.

The embodiments of the present application do not limit the applied spectrum. For example, the embodiments of the present application may be applied to licensed spectrum or unlicensed spectrum.

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

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within the coverage area. This application The embodiment does not limit this.

Optionally, the 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 embodiments of the present application.

It should be understood that the devices with communication functions in the network / system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiments of the present application.

The embodiments of the present application describe various embodiments in combination with a terminal device and a network device, where the terminal device may also be called a user equipment (User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal equipment can be a station (STAION, ST) in the WLAN, it can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems, such as terminal devices in NR networks or Terminal equipment in the public land mobile network (PLMN) network that will evolve in the future.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices can also be referred to as wearable smart devices, which is a general term for applying wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions that do not depend on smartphones, such as smart watches or smart glasses, and only focus on a certain type of application functions, and need to cooperate with other devices such as smartphones Use, such as various smart bracelets and smart jewelry for sign monitoring.

The network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, or a WCDMA A base station (NodeB, NB) can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network Or network equipment in the PLMN network that will evolve in the future.

In the embodiment of the present application, the network device provides services for the cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be the network device (for example The cell corresponding to the base station) can belong to a macro base station or a base station corresponding to a small cell (Small cell), where the small cell can include: a metro cell, a micro cell, and a pico cell cells), femtocells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

FIG. 2 is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG. 2, the method 200 may include the following content:

S210, the terminal device sends a scheduling request to the network device;

S220. After sending the scheduling request, the MAC entity of the terminal device determines whether to enter the active period of the DRX cycle, where the MAC entity of the terminal device is configured with the DRX cycle.

It should be noted that the scheduling request is used to request uplink authorization.

Optionally, after the MAC entity of the terminal device enters the active period of the DRX cycle, the terminal device needs to monitor the PDCCH.

For example, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, after the MAC entity of the terminal device enters the active period of the DRX cycle, the terminal device monitors the PDCCH.

Therefore, in the embodiment of the present application, after sending the scheduling request, only when the PDCCH needs to be monitored, the MAC entity of the terminal device determines to enter the activation period of the DRX cycle, and monitors the PDCCH after entering the activation period of the DRX cycle, so Reduce unnecessary PDCCH monitoring to achieve the purpose of power saving.

Optionally, in the embodiment of the present application, before sending the scheduling request, the terminal device determines whether to delay sending the scheduling request.

For example, after the terminal device sends the scheduling request, the MAC entity of the terminal device immediately begins to enter the active period of the DRX cycle. By delaying sending the scheduling request, the MAC entity of the terminal device does not enter DRX when it is not necessary to monitor the PDCCH The periodic activation period, thus, unnecessary PDCCH monitoring can be reduced to achieve the purpose of power saving.

Therefore, in the embodiment of the present application, the terminal device may send a scheduling request by delay, thereby avoiding that the MAC entity of the terminal device does not enter the activation period of the DRX cycle when PDCCH monitoring is not required, and thus, unnecessary PDCCH monitoring may be reduced , To achieve the purpose of power saving.

In the following, according to a specific embodiment, it is explained that after sending the scheduling request, the MAC entity of the terminal device determines whether to enter the activation period of the DRX cycle.

Optionally, as Embodiment 1,

The MAC entity of the terminal device determines whether to enter the active period of the DRX cycle according to the first logical channel that triggers the SR.

It should be noted that the MAC entity of the terminal device may be configured with 0, 1, or multiple SR configurations, and each SR configuration is composed of a series of Physical Uplink Control Channel (PUCCH) resources. Each SR configuration can correspond to one or more logical channels. Each logical channel can map 0 or 1 SR configuration configured by RRC signaling. The SR configuration corresponding to the logical channel that triggers the buffer status report (Buffer Status Report, BSR) is used to transmit the corresponding triggered SR transmission.

That is to say, in the first embodiment, the first logical channel can trigger the BSR, and in the case where the BSR is triggered, the scheduling request (SR) can be triggered if certain conditions are met.

Specifically, if a regular BSR (Regular BSR) has been triggered and the logical channel scheduling request delay timer (logicalChannelSR-DelayTimer) is not started, the scheduling request (SR) is triggered when any one of the following conditions is met:

Condition 1, if there is no uplink shared channel (Up-Shared Channel, UL-SCH) resource available for new transmission;

Condition 2: If the MAC entity of the terminal device is configured with the configured uplink grant (configured uplink (grant (s)), and the logical channel determined by the logical channel scheduling request mask (logicalChannelSR-Mask) configured by the upper layer does not trigger the Regular BSR ;

Condition 3: If the UL-SCH resources available for new transmission cannot meet the logical channel priority (Logical Channel Prioritization, LCP) mapping limit that triggers BSR.

Optionally, in the first embodiment, the first logical channel is configured with first indication information, and the first indication information is used to indicate whether the MAC entity of the terminal device starts to enter the DRX cycle after sending the scheduling request Activation period. Further, the MAC entity of the terminal device may determine whether to enter the activation period of the DRX cycle according to the first indication information.

Optionally, the first indication information may be configured by a network device, for example, the network device may configure the first indication information for the first logical channel through radio resource control (Radio Resource Control, RRC) signaling.

Specifically, in this embodiment 1,

If the first indication information indicates that the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity of the terminal device determines to start the active period of the DRX cycle; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity of the terminal device determines not to enter the activation period of the DRX cycle.

Optionally, in Embodiment 1, if the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device may perform DRX in the following manner Activation period of the cycle:

Manner 1: After the first timer for the DRX cycle is started, the MAC entity of the terminal device starts to enter the active period of the DRX cycle.

Manner 2: After the delay of the first duration, the MAC entity of the terminal device starts to enter the activation period of the DRX cycle.

It should be noted that the first timer for the DRX cycle may be a DRX on timer (drx-onDurationTimer). drx-onDurationTimer corresponds to the duration at the beginning of the DRX cycle. The drx-onDurationTimer is started from the beginning of the subframe to the period of the DRX slot offset (drx-SlotOffset). In other words, drx-onDurationTimer starts during the DRX cycle. When the DRX cycle is Long DRX Cycle (Long DRX Cycle) and Short DRX Cycle (Short DRX Cycle), drx-SlotOffset is different.

Optionally, as Embodiment 2,

The MAC entity of the terminal device is configured with a second timer, and the MAC entity of the terminal device may determine whether to enter the active period of the DRX cycle based on the second timer.

Specifically, in this embodiment 2,

After sending the scheduling request, if the MAC entity of the terminal device is in the inactive period of the DRX cycle, the MAC entity of the terminal device starts the second timer, and determines to enter the DRX cycle when the second timer times out Activation period; or

After sending the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device starts the second timer, and if the second timer expires before the second When a timer starts, the MAC entity of the terminal device determines to start the activation period of the DRX cycle.

Optionally, in Embodiment 2, if the first logical channel corresponding to the scheduling request is also configured with the first indication information, that is, as in Embodiment 1 above, the first logical channel is also configured with the first Indication information, and the first indication information is used to indicate whether the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device may be based on the second timer and the first The instruction information determines whether to enter the activation period of the DRX cycle. Specifically, it can be implemented as follows:

Manner 3: If the first indication information indicates that the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device starts the second timer or does not start the second timing Device.

Manner 4: If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device starts the second timer or does not start the second timing Device.

It should be noted that, in the above manner three, if the MAC entity of the terminal device starts the second timer, the MAC entity of the terminal device starts the second timer, and determines to start to enter when the second timer times out The activation period of the DRX cycle; or the MAC entity of the terminal device starts the second timer, and if the first timer for the DRX cycle starts before the second timer expires, the MAC entity of the terminal device determines to start entry The active period of the DRX cycle. In the above manner three, if the MAC entity of the terminal device does not start the second timer, the MAC entity of the terminal device starts to enter the active period of the DRX cycle.

It should be noted that in the above manner 4, if the MAC entity of the terminal device starts the second timer, the MAC entity of the terminal device starts the second timer, and it is determined that the entry starts when the second timer times out. The activation period of the DRX cycle; or the MAC entity of the terminal device starts the second timer, and if the first timer for the DRX cycle starts before the second timer expires, the MAC entity of the terminal device determines to start entry The active period of the DRX cycle. In the above manner 4, if the MAC entity of the terminal device does not start the second timer, the MAC entity of the terminal device does not enter the active period of the DRX cycle until the first timer starts.

Optionally, in this embodiment 2,

Each logical channel is configured with this second timer; or

Each scheduling request configuration is configured with a second timer; or

The MAC entity of the terminal device is configured with the second timer.

Optionally, as Embodiment 3,

The DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle. After sending the scheduling request, the MAC entity of the terminal device may determine whether to enter the active period of the DRX cycle based on the DRX cycle. specifically,

If the current non-activation period is in the long period of the DRX cycle, after sending the scheduling request, the MAC entity of the terminal device determines to start the activation period of the DRX cycle after delaying the second time; or

If the current non-activation period is in the short period of the DRX cycle, after sending the scheduling request, the MAC entity of the terminal device determines to start the activation period of the DRX cycle.

Optionally, as Embodiment 4,

The MAC entity of the terminal device determines whether to start entering the active period of the DRX cycle after sending the scheduling request according to the time that has previously been in the inactive period of the DRX cycle.

For example, the MAC entity of the terminal device has been in the inactive period of the DRX cycle before T1. If T1 is greater than the first threshold, after sending the scheduling request, the MAC entity of the terminal device determines to start the activation of the DRX cycle Time period; if T1 is less than or equal to the first threshold, then after sending the scheduling request, the MAC entity of the terminal device determines not to enter the activation period of the DRX cycle.

It should be noted that the first threshold may be pre-configured or configured by the network device.

In the following, according to a specific embodiment, the terminal device determines whether to delay sending the scheduling request.

Optionally, as Embodiment 5,

The terminal device determines whether to delay sending the scheduling request according to the first logical channel that triggers the scheduling request.

Optionally, in Embodiment 5, the terminal device determines whether to delay sending the scheduling request according to the parameters of the first logical channel. The parameters of the first logical channel include at least one of the following: the priority of the logical channel ( Priority), the list of allowed subcarrier spacing (SCS) of the logical channel, the maximum physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) duration of the logical channel (maxPUSCH-Duration), the allowed authorization type of the configuration of the logical channel (configuredGrantType1Allowed).

Optionally, in Embodiment 5, the terminal device may determine whether to delay sending the scheduling request according to the second indication information configured in the first logical channel, where the second indication information is used to indicate the terminal Whether the device delayed sending the scheduling request.

Optionally, the second indication information may be configured by the network device through RRC signaling.

For how to trigger the first logical channel by the scheduling request, reference may be made to the related description in Embodiment 1 above, and details are not described herein again.

Optionally, as Embodiment 6,

The DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle. The terminal device determines whether to delay sending the scheduling request according to the DRX cycle.

specifically,

If the current inactive period is in a long period of the DRX cycle, the terminal device determines to delay sending the scheduling request; or

If the current inactive period is in a short period of the DRX cycle, the terminal device determines not to delay sending the scheduling request.

Optionally, as Embodiment 7,

The terminal device determines whether to delay sending the scheduling request according to the time in the inactive period of the DRX cycle.

For example, the time when the MAC entity of the terminal device has been in the inactive period of the DRX cycle is T2. If T2 is greater than the second threshold, the terminal device determines not to delay sending the scheduling request; if T2 is less than or equal to the second threshold, Then, the terminal device determines to delay sending the scheduling request.

It should be noted that the second threshold may be pre-configured or configured by the network device.

Optionally, in the embodiment of the present application, if the terminal device determines to delay sending the scheduling request, the terminal device determines to delay sending the scheduling request after a third duration, or, the terminal device determines to delay to the most recent DRX cycle The scheduling request is sent at a time point when the first timer starts, where the third duration is pre-configured, or the third duration is configured by the network device, and the third duration is less than or equal to the first available The time distance from the location of the PUCCH resource to the closest time point when the first timer for the DRX cycle starts.

Therefore, in the embodiment of the present application, after sending the scheduling request, the MAC entity of the terminal device can determine whether to enter the activation period of the DRX cycle, and only when the PDCCH needs to be monitored to enter the activation period of the DRX cycle. Necessary PDCCH monitoring, reducing the time to monitor PDCCH, so as to achieve the purpose of power saving.

Further, the terminal device can send a scheduling request by delay, thereby avoiding that the MAC entity of the terminal device does not enter the activation period of the DRX cycle when it is not necessary to monitor the PDCCH, and thus, unnecessary PDCCH monitoring can be reduced to save power. .

FIG. 3 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in FIG. 3, the terminal device 300 includes:

The communication unit 310 is used to send a scheduling request to the network device;

The processing unit 320 is configured to, after the communication unit sends the scheduling request, control the MAC entity of the terminal device to determine whether to enter the active period of the DRX cycle, where the MAC entity of the terminal device is configured with the DRX cycle.

Optionally, the processing unit 320 is specifically used to:

The MAC entity that controls the terminal device determines whether to start the activation period of the DRX cycle according to the first logical channel that triggers the scheduling request.

Optionally, the communication unit 310 is further configured to receive RRC signaling sent by the network device, where the RRC signaling is used to configure first indication information for the first logical channel, and the first indication information is used to indicate that the After the scheduling request, whether the MAC entity of the terminal device starts to enter the activation period of the DRX cycle;

The processing unit 320 is specifically used for:

The MAC entity controlling the terminal device determines whether to enter the activation period of the DRX cycle according to the first indication information.

Optionally, the processing unit 320 is specifically used to:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the activation period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity that controls the terminal device determines to start the activation period of the DRX cycle ;or

If the first indication information indicates that the MAC entity of the terminal device does not enter the DRX cycle activation period after sending the scheduling request, after sending the scheduling request, the MAC entity controlling the terminal device determines not to enter the DRX cycle activation period .

Optionally, if the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the processing unit 320 is further configured to:

After the first timer for the DRX cycle is started, the MAC entity that controls the terminal device starts to enter the active period of the DRX cycle; or

After the first time delay, the MAC entity that controls the terminal device begins to enter the active period of the DRX cycle.

Optionally, the MAC entity of the terminal device is configured with a second timer,

The processing unit 320 is specifically used for:

After the communication unit 310 sends the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device is controlled to start the second timer, and it is determined that the second timer times out Start entering the activation period of the DRX cycle; or

After the communication unit 310 sends the scheduling request, if the MAC entity of the terminal device is in the inactive period of the DRX cycle, the MAC entity of the terminal device is controlled to start the second timer, and if the second timer expires When the first timer for the DRX cycle starts, the MAC entity that controls the terminal device determines to start the activation period of the DRX cycle.

Optionally, if first indication information is configured in the first logical channel corresponding to the scheduling request, and the MAC entity of the terminal device is configured with the second timer, wherein the first indication information is used to indicate After the scheduling request is sent, whether the MAC entity of the terminal device starts to enter the active period of the DRX cycle, the processing unit 320 is also used to:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device is controlled to start the second timer or not to start the second timer; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device is controlled to start the second timer or not to start the second timer.

Optionally, each logical channel is configured with one second timer; or

Each scheduling request configuration is configured with a second timer; or

The MAC entity of the terminal device is configured with the second timer.

Optionally, the DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle,

The processing unit 320 is specifically used for:

If the current non-activation period is in the long period of the DRX cycle, after the communication unit sends the scheduling request, the MAC entity that controls the terminal device determines to start the DRX cycle activation period after a second delay; or

If the current inactive period is in a short period of the DRX cycle, after the communication unit sends the scheduling request, the MAC entity that controls the terminal device determines to start the active period of the DRX cycle.

Optionally, the processing unit 320 is specifically used to:

The MAC entity that controls the terminal device determines whether to start entering the active period of the DRX cycle after sending the scheduling request according to the time that has previously been in the inactive period of the DRX cycle.

Optionally, before the communication unit 310 sends the scheduling request, the processing unit 320 is also used to determine whether to delay sending the scheduling request.

Optionally, the processing unit 320 is specifically used to:

According to the first logical channel that triggered the scheduling request, determine whether to delay sending the scheduling request.

Optionally, the processing unit 320 is specifically used to:

Determine whether to delay sending the scheduling request according to the parameters of the first logical channel. The parameters of the first logical channel include at least one of the following: the priority of the logical channel, the allowed SCS list of the logical channel, and the maximum PUSCH duration of the logical channel , The type of allowed authorization of logical channel configuration.

Optionally, the communication unit 310 is also used to:

Receiving RRC signaling sent by the network device, where the RRC signaling is used to configure second indication information for the first logical channel, and the second indication information is used to indicate whether the terminal device delays sending the scheduling request;

The processing unit 320 is specifically used for:

According to the second instruction information, determine whether to delay sending the scheduling request.

The processing unit 320 is specifically used for:

If the current inactive period is in the long period of the DRX cycle, determine to delay sending the scheduling request; or

If the current inactive period is in a short period of the DRX cycle, it is determined that the scheduling request is not delayed.

Optionally, the processing unit 320 is specifically used to:

According to the time that has been in the inactive period of the DRX cycle before, determine whether to delay sending the scheduling request.

Optionally, if the processing unit 320 determines to delay sending the scheduling request, the processing unit 320 is further configured to:

The scheduling request is sent after a delay of a third duration is determined, or the terminal device determines to delay sending the scheduling request to a point in time when the first timer for the DRX cycle starts, wherein the third duration is pre-configured, or The third time duration is configured by the network device, and the third time duration is less than or equal to the time distance from the first available PUCCH resource location to the nearest time point when the first timer for the DRX cycle starts.

Optionally, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the communication unit 310 is also used to:

After the MAC entity of the terminal device enters the active period of the DRX cycle, it monitors the PDCCH.

It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 300 are respectively for implementing the method shown in FIG. For the sake of brevity, the corresponding process of the terminal device in 200 will not be repeated here.

FIG. 4 is a schematic structural diagram of a communication device 400 provided by an embodiment of the present application. The communication device 400 shown in FIG. 4 includes a processor 410, and the processor 410 can call and run a computer program from the memory to implement the method in the embodiments of the present application.

Optionally, as shown in FIG. 4, the communication device 400 may further include a memory 420. The processor 410 can call and run a computer program from the memory 420 to implement the method in the embodiments of the present application.

The memory 420 may be a separate device independent of the processor 410, or may be integrated in the processor 410.

Optionally, as shown in FIG. 4, the communication device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.

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

Optionally, the communication device 400 may specifically be a network device according to an embodiment of the present application, and the communication device 400 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. .

Optionally, the communication device 400 may specifically be a mobile terminal / terminal device according to an embodiment of the present application, and the communication device 400 may implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, for simplicity And will not be repeated here.

5 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 500 shown in FIG. 5 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 5, the chip 500 may further include a memory 520. The processor 510 can call and run a computer program from the memory 520 to implement the method in the embodiments of the present application.

The memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.

Optionally, the chip 500 may further include an input interface 530. The processor 510 can control the input interface 530 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the chip 500 may further include an output interface 540. The processor 510 can control the output interface 540 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.

Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the methods of the embodiments of the present application. No longer.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system chips, chip systems, or system-on-chip chips.

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

Among them, the terminal device 610 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 620 can be used to implement the corresponding functions implemented by the network device in the above method. .

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has signal processing capabilities. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as a random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and register. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronic Erasable programmable read only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not limiting. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data) SDRAM (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, 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.

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

Optionally, the computer-readable storage medium may be applied to the network device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application For the sake of brevity, I will not repeat them here.

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

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. Repeat again.

Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application, For brevity, I will not repeat them here.

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

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, the computer is allowed to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. And will not be repeated here.

Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application, and when the computer program runs on the computer, the computer is implemented by the mobile terminal / terminal device in performing various methods of the embodiments of the present application For the sake of brevity, I will not repeat them here.

Those of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians 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.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A wireless communication method, characterized in that it includes:

The terminal device sends a scheduling request to the network device;

After the scheduling request is sent, the media access control MAC entity of the terminal device determines whether to start the discontinuous reception DRX cycle activation period, where the MAC entity of the terminal device is configured with the DRX cycle.
The method according to claim 1, wherein the MAC entity of the terminal device determines whether to start entering the activation period of the DRX cycle, including:

The MAC entity of the terminal device determines whether to start the activation period of the DRX cycle according to the first logical channel that triggers the scheduling request.
The method according to claim 2, wherein the method further comprises:

The terminal device receives radio resource control RRC signaling sent by the network device, where the RRC signaling is used to configure first indication information for the first logical channel, and the first indication information is used to indicate After the scheduling request, whether the MAC entity of the terminal device starts to enter the activation period of the DRX cycle;

The MAC entity of the terminal device determines whether to enter the activation period of the DRX cycle according to the first logical channel, including:

The MAC entity of the terminal device determines whether to enter the activation period of the DRX cycle according to the first indication information.
The method according to claim 3, wherein the MAC entity of the terminal device determines whether to start the activation period of the DRX cycle according to the first indication information, including:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity of the terminal device determines to start to enter DRX The activation period of the cycle; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the active period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity of the terminal device determines not to enter DRX The activation period of the cycle.
The method according to claim 4, wherein if the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the method further comprises:

After the first timer for the DRX cycle is started, the MAC entity of the terminal device starts to enter the active period of the DRX cycle; or

After the delay of the first duration, the MAC entity of the terminal device starts to enter the activation period of the DRX cycle.
The method according to claim 1, wherein the MAC entity of the terminal device is configured with a second timer,

After sending the scheduling request, the MAC entity of the terminal device determines whether to enter the activation period of the DRX cycle, including:

After sending the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device starts the second timer, and determines that the second timer times out Start entering the activation period of the DRX cycle; or

After sending the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device starts the second timer, and if the second timer expires For the start of the first timer of the DRX cycle, the MAC entity of the terminal device determines to start the activation period of the DRX cycle.
The method according to claim 6, wherein if the first indication information is configured in the first logical channel corresponding to the scheduling request, and the MAC entity of the terminal device is configured with the second timer , Where the first indication information is used to indicate whether the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, the method further includes:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device starts the second timer or does not start the Second timer; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device starts the second timer or does not start the Second timer.
The method according to claim 6 or 7, wherein

Each logical channel is configured with the second timer; or

Each scheduling request configuration is configured with the second timer; or

The MAC entity of the terminal device is configured with the second timer.
The method according to claim 1, wherein the DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle,

After sending the scheduling request, the MAC entity of the terminal device determines whether to enter the activation period of the DRX cycle, including:

If the current non-activation period is in the long period of the DRX cycle, after sending the scheduling request, the MAC entity of the terminal device determines to start the activation period of the DRX cycle after delaying the second time; or

If the current non-activation period is in the short period of the DRX cycle, after sending the scheduling request, the MAC entity of the terminal device determines to start the activation period of the DRX cycle.
The method according to claim 1, characterized in that, after sending the scheduling request, the MAC entity of the terminal device determines whether to start an activation period of a DRX cycle, including:

The MAC entity of the terminal device determines whether to start entering the active period of the DRX cycle after sending the scheduling request according to the time that has previously been in the inactive period of the DRX cycle.
The method according to any one of claims 1 to 10, wherein before the terminal device sends the scheduling request, the method further comprises:

The terminal device determines whether to delay sending the scheduling request.
The method according to claim 11, wherein the terminal device determining whether to delay sending the scheduling request includes:

The terminal device determines whether to delay sending the scheduling request according to the first logical channel that triggers the scheduling request.
The method according to claim 12, wherein the terminal device determining whether to delay sending the scheduling request according to the first logical channel includes:

The terminal device determines whether to delay sending the scheduling request according to the parameters of the first logical channel, and the parameters of the first logical channel include at least one of the following: the priority of the logical channel and the subcarrier interval allowed by the logical channel The SCS list, the maximum physical uplink shared channel PUSCH duration of the logical channel, and the allowed grant type of the configuration of the logical channel.
The method of claim 12, wherein the method further comprises:

The terminal device receives RRC signaling sent by the network device, the RRC signaling is used to configure second indication information for the first logical channel, and the second indication information is used to indicate whether the terminal device is delayed Send the scheduling request;

The terminal device determining whether to delay sending the scheduling request according to the first logical channel includes:

The terminal device determines whether to delay sending the scheduling request according to the second indication information.
The method according to claim 11, wherein the DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle,

The terminal device determining whether to delay sending the scheduling request includes:

If the current inactive period is in a long period of the DRX cycle, the terminal device determines to delay sending the scheduling request; or

If the current inactive period is in a short period of the DRX cycle, the terminal device determines not to delay sending the scheduling request.
The method according to claim 11, wherein the terminal device determining whether to delay sending the scheduling request includes:

The terminal device determines whether to delay sending the scheduling request according to the time in the inactive period of the DRX cycle.
The method according to any one of claims 11 to 16, wherein if the terminal device determines to delay sending the scheduling request, the method further comprises:

The terminal device determines to delay sending the scheduling request after a third duration, or the terminal device determines to delay sending the scheduling request to a point in time when the first timer for the DRX cycle starts recently, wherein the first The three time durations are pre-configured, or the third time duration is configured by the network device, and the third time duration is less than or equal to the first available physical uplink control channel PUCCH resource location to the nearest for the DRX cycle The time distance of the time point when the first timer is started.
The method according to any one of claims 1 to 17, wherein if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the method further comprises:

After the MAC entity of the terminal device enters the active period of the DRX cycle, the terminal device listens to the physical downlink control channel PDCCH.
A terminal device is characterized by comprising:

Communication unit, used to send scheduling request to network equipment;

The processing unit is configured to control the media access control MAC entity of the terminal device to determine whether to start the discontinuous reception DRX cycle activation period after the communication unit sends the scheduling request, wherein the MAC of the terminal device The entity is configured with a DRX cycle.
The terminal device according to claim 19, wherein the processing unit is specifically configured to:

The MAC entity controlling the terminal device determines whether to start the activation period of the DRX cycle according to the first logical channel that triggers the scheduling request.
The terminal device according to claim 20, wherein the communication unit is further configured to receive radio resource control RRC signaling sent by the network device, and the RRC signaling is used to configure the first logical channel First indication information, which is used to indicate whether the MAC entity of the terminal device starts to enter the activation period of the DRX cycle after sending the scheduling request;

The processing unit is specifically used for:

The MAC entity controlling the terminal device determines whether to enter the activation period of the DRX cycle according to the first indication information.
The terminal device according to claim 21, wherein the processing unit is specifically configured to:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity that controls the terminal device determines to start entering The active period of the DRX cycle; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, after sending the scheduling request, the MAC entity that controls the terminal device determines not to enter The active period of the DRX cycle.
The terminal device according to claim 22, wherein if the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the processing unit further uses to:

After the first timer for the DRX cycle is started, the MAC entity that controls the terminal device starts to enter the active period of the DRX cycle; or

After the delay for the first duration, the MAC entity that controls the terminal device starts to enter the activation period of the DRX cycle.
The terminal device according to claim 19, wherein the MAC entity of the terminal device is configured with a second timer,

The processing unit is specifically used for:

After the communication unit sends the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device is controlled to start the second timer, and it is determined that the The second timer expires and begins to enter the active period of the DRX cycle; or

After the communication unit sends the scheduling request, if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the MAC entity of the terminal device is controlled to start the second timer, and if the first Before the second timer expires, the first timer for the DRX cycle starts, and the MAC entity that controls the terminal device determines to start the activation period of the DRX cycle.
The terminal device according to claim 24, wherein if the first indication information is configured in the first logical channel corresponding to the scheduling request, and the MAC entity of the terminal device is configured with the second timing Wherein the first indication information is used to indicate whether the MAC entity of the terminal device starts to enter the active period of the DRX cycle after sending the scheduling request, and the processing unit is further used to:

If the first indication information indicates that the MAC entity of the terminal device starts to enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device is controlled to start the second timer or not to start The second timer; or

If the first indication information indicates that the MAC entity of the terminal device does not enter the activation period of the DRX cycle after sending the scheduling request, the MAC entity of the terminal device is controlled to start the second timer or not start The second timer is described.
The terminal device according to claim 24 or 25, characterized in that

Each logical channel is configured with the second timer; or

Each scheduling request configuration is configured with the second timer; or

The MAC entity of the terminal device is configured with the second timer.
The terminal device according to claim 19, wherein the DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle,

The processing unit is specifically used for:

If the current non-activation period is in a long period of the DRX cycle, after the communication unit sends the scheduling request, the MAC entity that controls the terminal device determines to start the DRX cycle activation period after a second delay; or

If the current inactive period is in a short period of the DRX cycle, after the communication unit sends the scheduling request, the MAC entity that controls the terminal device determines to start the active period of the DRX cycle.
The terminal device according to claim 19, wherein the processing unit is specifically configured to:

The MAC entity that controls the terminal device determines whether to start entering the active period of the DRX cycle after sending the scheduling request according to the time that has previously been in the inactive period of the DRX cycle.
The terminal device according to any one of claims 19 to 28, wherein before the communication unit sends the scheduling request, the processing unit is further configured to determine whether to delay sending the scheduling request.
The terminal device according to claim 29, wherein the processing unit is specifically configured to:

According to the first logical channel that triggered the scheduling request, determine whether to delay sending the scheduling request.
The terminal device according to claim 30, wherein the processing unit is specifically configured to:

Determine whether to delay sending the scheduling request according to the parameters of the first logical channel. The parameters of the first logical channel include at least one of the following: the priority of the logical channel, the allowed subcarrier spacing SCS list of the logical channel, and the logic The maximum physical uplink shared channel PUSCH duration of the channel and the allowed grant type of the logical channel configuration.
The terminal device according to claim 30, wherein the communication unit is further configured to:

Receiving RRC signaling sent by the network device, where the RRC signaling is used to configure second indication information for the first logical channel, and the second indication information is used to indicate whether the terminal device delays sending the schedule request;

The processing unit is specifically used for:

According to the second instruction information, determine whether to delay sending the scheduling request.
The terminal device according to claim 29, wherein the DRX cycle configured by the MAC entity of the terminal device includes a long cycle and a short cycle,

The processing unit is specifically used for:

If the current inactive period is in a long period of the DRX cycle, determine to delay sending the scheduling request; or

If the current inactive period is in a short period of the DRX cycle, it is determined that the scheduling request is not delayed.
The terminal device according to claim 29, wherein the processing unit is specifically configured to:

According to the time that has been in the inactive period of the DRX cycle before, it is determined whether to delay sending the scheduling request.
The terminal device according to any one of claims 29 to 34, wherein if the processing unit determines to delay sending the scheduling request, the processing unit is further configured to:

The scheduling request is sent after a delay of a third duration is determined, or the terminal device determines to delay sending the scheduling request to a point in time when the first timer for the DRX cycle starts recently, where the third duration is a Configured, or, the third duration is configured by the network device, and the third duration is less than or equal to the first available physical uplink control channel PUCCH resource location to the nearest first timer for the DRX cycle The time distance of the starting time.
The terminal device according to any one of claims 19 to 35, wherein if the MAC entity of the terminal device is in an inactive period of the DRX cycle, the communication unit is further used to:

After the MAC entity of the terminal device enters the active period of the DRX cycle, it monitors the physical downlink control channel PDCCH.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of claims 1 to 18 One of the methods.
A chip, characterized by comprising: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 18.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 18.
A computer program product, characterized in that it includes computer program instructions, which cause the computer to execute the method according to any one of claims 1 to 18.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1 to 18.