CN111869314B

CN111869314B - Wireless communication method, terminal device, chip and medium

Info

Publication number: CN111869314B
Application number: CN201880091323.2A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-10-19
Filing date: 2018-10-19
Publication date: 2022-01-11
Anticipated expiration: 2038-10-19
Also published as: WO2020077643A1; CN111869314A

Abstract

The embodiment of the application provides a wireless communication method and terminal equipment, which can reduce the time for monitoring a PDCCH (physical downlink control channel), and further achieve the purpose of saving electricity. The method comprises the following steps: the terminal equipment sends a scheduling request to the network equipment; after transmitting the scheduling request, the MAC entity of the terminal device determines whether to start entering an active period of a DRX cycle, wherein the MAC entity of the terminal device is configured with the DRX cycle.

Description

Wireless communication method, terminal device, chip and medium

Technical Field

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

Background

In a Long Term Evolution (LTE) or New Radio (NR) system, if a terminal device sends a Scheduling Request (SR) to Request an uplink grant, the terminal device starts monitoring a Physical Downlink Control Channel (PDCCH) to obtain a grant (grant) sent by a network device to the terminal device. If the terminal device configures a Discontinuous Reception (DRX) cycle (cycle), the terminal device needs to enter an active time of the DRX cycle after transmitting the SR regardless of whether the terminal device is in an active time of the DRX cycle or in an inactive time of the DRX cycle.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and terminal equipment, which can reduce the time for monitoring a PDCCH (physical downlink control channel), and further achieve the purpose of saving electricity.

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

the terminal equipment sends a scheduling request to the network equipment;

after transmitting the scheduling request, a Media Access Control (MAC) entity (entity) of the terminal device determines whether to start entering an active period of a DRX cycle, wherein the MAC entity of the terminal device is configured with the 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 executing the method in the first aspect.

In particular, the terminal device comprises functional modules for performing the method in the first aspect described above.

In a third aspect, a terminal device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory 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 the computer program from the memory so that the device in which the chip is installed performs the method as in the first aspect described above.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program for causing a computer to perform the method of the first aspect.

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

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

By the technical scheme, after the scheduling request is sent, the MAC entity of the terminal equipment can determine whether to start to enter the active period of the DRX period, and the MAC entity starts to enter the active period of the DRX period when the PDCCH needs to be monitored, so that unnecessary PDCCH monitoring can be avoided, the time for monitoring the PDCCH is shortened, and the purpose of saving power is achieved.

Drawings

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

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

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

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

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

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

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

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

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

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

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

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

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

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

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

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

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

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

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

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

s210, the terminal equipment sends a scheduling request to the network equipment;

s220, after transmitting the scheduling request, the MAC entity of the terminal device determines whether to start entering an active period of a DRX cycle, wherein 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 an uplink grant.

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 the inactive period of the DRX cycle, the terminal device monitors the PDCCH after the MAC entity of the terminal device enters the active period of the DRX cycle.

Therefore, in the embodiment of the present application, after the scheduling request is sent, only when the PDCCH needs to be monitored, the MAC entity of the terminal device determines the active period entering the DRX cycle, and monitors the PDCCH after entering the active period of the DRX cycle, so that unnecessary PDCCH monitoring can be reduced, and the purpose of saving power is achieved.

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

For example, in a scenario that the MAC entity of the terminal device immediately starts to enter the active period of the DRX cycle after the terminal device sends the scheduling request, the MAC entity of the terminal device may not enter the active period of the DRX cycle by delaying sending the scheduling request when the PDCCH does not need to be monitored, so that unnecessary PDCCH monitoring may be reduced, and the purpose of saving power may be achieved.

Therefore, in the embodiment of the present application, the terminal device may send the scheduling request by delaying, so that it is avoided that the MAC entity of the terminal device does not enter the active period of the DRX cycle when the PDCCH does not need to be monitored, and further, unnecessary PDCCH monitoring may be reduced, and the purpose of saving power is achieved.

It is explained below according to a specific embodiment that after transmitting the scheduling request, the MAC entity of the terminal device determines whether to start entering the active period of the DRX cycle.

Alternatively, as in example 1,

the MAC entity of the terminal device determines whether to start entering an active period of the DRX cycle according to the first logical channel triggering 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 may correspond to one or more logical channels. Each logical channel may map 0 or 1 SR configuration of RRC signaling configuration. The SR configuration corresponding to the logical channel that triggers the Buffer Status Report (BSR) is used to transmit the corresponding triggered SR transmission.

That is, in this embodiment 1, the first logical channel may trigger a BSR, and in the case of the BSR triggering, the Scheduling Request (SR) may be triggered if a certain condition is satisfied.

Specifically, if a normal bsr (regular bsr) is already triggered and the logical channel scheduling request delay timer (logical channel SR-DelayTimer) is not turned on, the Scheduling Request (SR) is triggered when any one of the following conditions is satisfied:

condition one, if there is no Uplink Shared Channel (UL-SCH) resource available for new transmission;

if the MAC entity of the terminal device is configured with a configured uplink grant(s), and a logical channel determined by a logical channel scheduling request Mask (logical channel sr-Mask) configured at a higher layer does not trigger the Regular BSR;

and thirdly, if the UL-SCH resource available for new transmission cannot meet the Logical Channel Priority (LCP) mapping limitation of the trigger BSR.

Optionally, in this embodiment 1, the first logical channel is configured with first indication information, 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 the scheduling request is sent. Further, the MAC entity of the terminal device may determine whether to start entering the active period of the DRX cycle according to the first indication information.

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

Specifically, in this example 1,

if the first indication information indicates that the MAC entity of the terminal equipment starts to enter the active period of the DRX cycle after the scheduling request is sent, the MAC entity of the terminal equipment determines to start to enter the active period of the DRX cycle after the scheduling request is sent; or

If the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, the MAC entity of the terminal equipment determines not to enter the active period of the DRX cycle after the scheduling request is sent.

Optionally, in this embodiment 1, 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, the MAC entity of the terminal device may perform the active period of the DRX cycle in the following manner:

first, 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.

In the second mode, after delaying the first time length, the MAC entity of the terminal equipment starts to enter the active period of the DRX cycle.

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

Alternatively, as in example 2,

the MAC entity of the terminal device is configured with a second timer, based on which the MAC entity of the terminal device can determine whether to start entering the active period of the DRX cycle.

Specifically, in this example 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 start entering the active period of the DRX cycle when the second timer is overtime; or

After transmitting 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 if the first timer for the DRX cycle starts before the second timer expires, the MAC entity of the terminal device determines to start entering the active period of the DRX cycle.

Alternatively, in embodiment 2, if the first indication information is also configured in the first logical channel corresponding to the scheduling request, that is, as in embodiment 1, the first indication information is also configured in the first logical channel, 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 the scheduling request is sent, the MAC entity of the terminal device may determine whether to start to enter the active period of the DRX cycle based on the second timer and the first indication information. Specifically, it can be realized by:

in a third mode, 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 the scheduling request is sent, the MAC entity of the terminal device starts the second timer or does not start the second timer.

In a fourth mode, 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 the scheduling request is sent, the MAC entity of the terminal device starts the second timer or does not start the second timer.

It should be noted that, in the third manner, if the MAC entity of the terminal device starts the second timer, and determines that the active period of the DRX cycle starts to enter after the second timer expires; 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 entering the active period of the DRX cycle. In the third mode, 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 fourth mode, if the MAC entity of the terminal device starts the second timer, and determines that the active period of the DRX cycle starts to enter after the second timer expires; 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 entering the active period of the DRX cycle. In the fourth mode, 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.

Alternatively, in this embodiment 2,

each logical channel is configured with one second timer; or

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

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

Alternatively, as in example 3,

the DRX cycle in which the MAC entity of the terminal device is configured includes a long cycle and a short cycle, and after transmitting the scheduling request, the MAC entity of the terminal device may determine whether to start entering an active period of the DRX cycle based on the DRX cycle. In particular, the amount of the solvent to be used,

if the current inactive period is in the long cycle of the DRX cycle, after the scheduling request is sent, the MAC entity of the terminal equipment determines to start to enter the active period of the DRX cycle after delaying for a second time; or

If the current inactive period is in the short cycle of the DRX cycle, the MAC entity of the terminal device determines to start entering the active period of the DRX cycle after transmitting the scheduling request.

Alternatively, as in example 4,

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

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

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

The following describes the determination by the terminal device whether to delay sending the scheduling request according to a specific embodiment.

Alternatively, as in example 5,

the terminal equipment determines whether to delay sending the scheduling request according to the first logic channel triggering the scheduling request.

Optionally, in this embodiment 5, the terminal device determines whether to delay sending the scheduling request according to a parameter of the first logical channel, where the parameter of the first logical channel includes at least one of: priority (Priority) of a logical Channel, a list of Subcarrier spacing (SCS) Allowed for the logical Channel, a maximum Physical Uplink Shared Channel (PUSCH) Duration (maxPUSCH-Duration) of the logical Channel, and a grant type (configured grant type1Allowed) of configuration of the logical Channel.

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

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

For how the scheduling request triggers the first logical channel, reference may be made to the related description in embodiment 1, and details are not repeated here.

Alternatively, as in example 6,

the DRX cycle in which the MAC entity of the terminal device is configured includes a long cycle and a short cycle, and the terminal device determines whether to delay transmission of the scheduling request according to the DRX cycle.

In particular, the amount of the solvent to be used,

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

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

Alternatively, as in example 7,

the terminal device determines whether to delay transmission of the scheduling request according to a time that has been in an inactive period of the DRX cycle before.

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

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

Optionally, in this 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 sending the scheduling request to a time point at which a latest first timer for the DRX cycle is started, where the third duration is preconfigured, or the third duration is configured by the network device, and the third duration is less than or equal to a time distance from a first available PUCCH resource location to the time point at which the latest first timer for the DRX cycle is started.

Therefore, in the embodiment of the present application, after the scheduling request is sent, the MAC entity of the terminal device may determine whether to start entering the active period of the DRX cycle, and start entering the active period of the DRX cycle only when the PDCCH needs to be monitored, so that unnecessary PDCCH monitoring may be avoided, the time for monitoring the PDCCH is reduced, and the purpose of saving power is achieved.

Furthermore, the terminal device can send the scheduling request by delaying, thereby avoiding that the MAC entity of the terminal device does not enter the active period of the DRX cycle when the PDCCH does not need to be monitored, and further reducing unnecessary PDCCH monitoring and achieving the purpose of power saving.

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

a communication unit 310, configured to send a scheduling request to a network device;

a processing unit 320, configured to control the MAC entity of the terminal device to determine whether to start entering an active period of a DRX cycle after the communication unit transmits the scheduling request, wherein the MAC entity of the terminal device is configured with the DRX cycle.

Optionally, the processing unit 320 is specifically configured to:

the MAC entity controlling the terminal device determines whether to start entering an active period of the DRX cycle according to the first logical channel triggering the scheduling request.

Optionally, the communication unit 310 is further configured to receive an RRC signaling sent by the network device, where the RRC signaling is used to configure first indication information for the first logical channel, 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 the scheduling request is sent;

the processing unit 320 is specifically configured to:

and the MAC entity controlling the terminal equipment determines whether to start entering the active period of the DRX cycle according to the first indication information.

Optionally, the processing unit 320 is specifically configured to:

if the first indication information indicates that the MAC entity of the terminal equipment starts to enter the active period of the DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to determine the active period of the DRX cycle after the scheduling request is sent; or

And if the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to determine that the MAC entity does not enter the active period of the DRX cycle after the scheduling request is sent.

Optionally, 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 the scheduling request is sent, the processing unit 320 is further configured to:

controlling a MAC entity of the terminal device to start entering an active period of the DRX cycle after a first timer for the DRX cycle is started; or

After delaying the first period of time, the MAC entity controlling the terminal device starts 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 configured to:

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, controlling the MAC entity of the terminal device to start the second timer, and determining to start entering the active period of the DRX cycle after the second timer expires; 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 first timer for the DRX cycle starts before the second timer expires, the MAC entity of the terminal device is controlled to determine to start entering the active 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, where the first indication information is used to indicate whether the MAC entity of the terminal device starts to enter an active period of the DRX cycle after the scheduling request is sent, the processing unit 320 is further configured to:

if the first indication information indicates that the MAC entity of the terminal equipment starts to enter the active period of the DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to start the second timer or not to start the second timer; or

And if the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to start the second timer or not starting the second timer.

Optionally, each logical channel is configured with one of the second timers; or

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

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

the processing unit 320 is specifically configured to:

if the current inactive period is in the long cycle of the DRX cycle, after the communication unit sends the scheduling request, controlling the MAC entity of the terminal equipment to determine to start to enter the active period of the DRX cycle after delaying for a second time; or

If the current inactive period is in the short cycle of the DRX cycle, the MAC entity controlling the terminal device determines to start entering the active period of the DRX cycle after the communication unit transmits the scheduling request.

Optionally, the processing unit 320 is specifically configured to:

the MAC entity controlling the terminal device determines whether to start entering the active period of the DRX cycle after transmitting the scheduling request according to a time that has been in the inactive period of the DRX cycle before.

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

Optionally, the processing unit 320 is specifically configured to:

determining whether to delay sending the scheduling request according to the first logical channel triggering the scheduling request.

Optionally, the processing unit 320 is specifically configured to:

determining whether to delay sending the scheduling request according to a parameter of the first logical channel, the parameter of the first logical channel including at least one of: priority of logical channels, list of SCS allowed for logical channels, maximum PUSCH duration for logical channels, allowed grant type of configuration of logical channels.

Optionally, the communication unit 310 is further configured to:

receiving an 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 configured to:

and determining whether to delay the sending of the scheduling request according to the second indication information.

the processing unit 320 is specifically configured to:

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

And if the current inactive period is in the short cycle of the DRX cycle, determining not to delay sending the scheduling request.

Optionally, the processing unit 320 is specifically configured to:

determining whether to delay transmitting the scheduling request according to a time that has been in an inactive period of the DRX cycle before.

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

and after determining to delay a third duration, sending the scheduling request, or determining by the terminal device to delay sending the scheduling request to a time point of a latest start of the first timer for the DRX cycle, where the third duration is preconfigured, or the third duration is configured by the network device, and is less than or equal to a time distance from a first available PUCCH resource location to a time point of a latest start of the first timer for the DRX cycle.

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

and after the MAC entity of the terminal equipment enters the active period of the DRX period, monitoring 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 embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.

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

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

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

Optionally, as shown in fig. 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, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

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

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

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

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

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

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

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

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

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

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

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

Fig. 6 is a schematic block diagram of a communication system 600 provided in 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.

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

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

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

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

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

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

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

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

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

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

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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

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

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

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

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

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

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

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

Claims

1. A method of wireless communication, comprising:

the terminal equipment sends a scheduling request to the network equipment;

after transmitting the scheduling request, the MAC entity of the terminal device determines whether to start entering an active period of a Discontinuous Reception (DRX) cycle, wherein the MAC entity of the terminal device is configured with the DRX cycle.

2. The method of claim 1, wherein the determining whether to start entering the active period of the DRX cycle by the MAC entity of the terminal device comprises:

and the MAC entity of the terminal equipment determines whether to start entering the activation period of the DRX cycle according to the first logic channel triggering the scheduling request.

3. The method of claim 2, further comprising:

the terminal device receives Radio Resource Control (RRC) signaling sent by the network device, wherein the RRC signaling is used for configuring first indication information for the first logical channel, and the first indication information is used for indicating whether a Media Access Control (MAC) entity of the terminal device starts to enter an active period of the DRX cycle after the scheduling request is sent;

the MAC entity of the terminal device determines whether to start entering an active period of a DRX cycle according to the first logical channel, including:

and the MAC entity of the terminal equipment determines whether to start to enter the active period of the DRX cycle or not according to the first indication information.

4. The method of claim 3, wherein the determining, by the MAC entity of the terminal device, whether to start entering the active period of the DRX cycle according to the first indication information comprises:

If the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, the MAC entity of the terminal equipment determines that the MAC entity does not enter the active period of the DRX cycle after the scheduling request is sent.

5. The method of claim 4, wherein if the first indication information indicates that the MAC entity of the terminal device does not enter an active period of a DRX cycle after the scheduling request is transmitted, the method further comprises:

after the first timer for the DRX period is started, the MAC entity of the terminal equipment starts to enter an active period of the DRX period; or

After delaying the first time period, the MAC entity of the terminal device starts to enter the active period of the DRX cycle.

6. The method according to claim 1, characterized in that the MAC entity of the terminal device is configured with a second timer,

the determining, by the MAC entity of the terminal device, whether to start entering an active period of a DRX cycle after transmitting the scheduling request includes:

after the scheduling request is sent, if the MAC entity of the terminal equipment is in the inactive period of the DRX period, the MAC entity of the terminal equipment starts the second timer and determines to start to enter the active period of the DRX period when the second timer is overtime; or

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 if the MAC entity of the terminal device starts for the first timer of the DRX cycle before the second timer expires, the MAC entity of the terminal device determines to start entering the active period of the DRX cycle.

7. The method of claim 6, wherein if a first indication information is configured in a 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 whether the MAC entity of the terminal device starts to enter an active period of a DRX cycle after the scheduling request is sent, the method further comprises:

if the first indication information indicates that the MAC entity of the terminal equipment starts to enter the active period of a DRX cycle after the scheduling request is sent, the MAC entity of the terminal equipment starts the second timer or does not start the second timer; or

And if the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, the MAC entity of the terminal equipment starts the second timer or does not start the second timer.

8. The method of claim 6,

each logical channel is configured with one of the second timers; or

Each scheduling request configuration is configured with one of the second timers; or

9. The method of claim 1, wherein the DRX cycle that the MAC entity of the terminal device is configured with comprises a long cycle and a short cycle,

And if the current inactive period is in the short cycle of the DRX cycle, after the scheduling request is sent, the MAC entity of the terminal equipment determines to start to enter the active period of the DRX cycle.

10. The method of claim 1, wherein the determining, by the MAC entity of the terminal device, whether to start entering the active period of the DRX cycle after transmitting the scheduling request comprises:

and the MAC entity of the terminal equipment determines whether to start entering the active period of the DRX period after the scheduling request is sent according to the time which is in the inactive period of the DRX period before.

11. The method according to any of claims 1 to 10, wherein before the terminal device transmits the scheduling request, the method further comprises:

the terminal device determines whether to delay sending the scheduling request.

12. The method of claim 11, wherein the terminal device determining whether to delay sending the scheduling request comprises:

and the terminal equipment determines whether to delay the sending of the scheduling request according to a first logic channel triggering the scheduling request.

13. The method of claim 12, wherein the terminal device determining whether to delay sending the scheduling request according to the first logical channel comprises:

the terminal device determines whether to delay sending the scheduling request according to the parameter of the first logical channel, wherein the parameter of the first logical channel includes at least one of the following: the priority of the logical channel, the list of the allowed subcarrier intervals SCS of the logical channel, the duration of the maximum physical uplink shared channel PUSCH of the logical channel, and the allowed authorization type of the configuration of the logical channel.

14. The method of claim 12, further comprising:

the terminal device receives an 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 determining, by the terminal device, whether to delay sending the scheduling request according to the first logical channel includes:

and the terminal equipment determines whether to delay the sending of the scheduling request according to the second indication information.

15. The method of claim 11, wherein the DRX cycle that the MAC entity of the terminal device is configured with comprises a long cycle and a short cycle,

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

And if the current inactive period is in the short cycle of the DRX cycle, the terminal equipment determines not to delay the sending of the scheduling request.

16. The method of claim 11, wherein the terminal device determining whether to delay sending the scheduling request comprises:

the terminal device determines whether to delay transmission of the scheduling request according to a time that has been in an inactive period of a DRX cycle before.

17. The method of claim 11, wherein if the terminal device determines to delay sending the scheduling request, the method further comprises:

the terminal device determines to delay a third duration before sending the scheduling request, or the terminal device determines to delay sending the scheduling request to a time point when a first timer for a DRX cycle is started most recently, where the third duration is preconfigured, or the third duration is configured by the network device, and the third duration is less than or equal to a time distance from a first available PUCCH resource location to a time point when the first timer for the DRX cycle is started most recently.

18. The method according to any of claims 1 to 10 and 12 to 17, wherein if the MAC entity of the terminal device is in the inactive period of the DRX cycle, the method further comprises:

after the MAC entity of the terminal equipment enters the activation period of the DRX period, the terminal equipment monitors a physical downlink control channel PDCCH.

19. A terminal device, comprising:

a communication unit for transmitting a scheduling request to a network device;

a processing unit, configured to control a media access control MAC entity of the terminal device to determine whether to start entering an active period of a discontinuous reception DRX cycle after the communication unit transmits the scheduling request, wherein the MAC entity of the terminal device is configured with the DRX cycle.

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

and controlling the MAC entity of the terminal equipment to determine whether to start entering the activation period of the DRX cycle according to the first logic channel triggering the scheduling request.

21. 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, wherein the RRC signaling is configured to configure first indication information for the first logical channel, and the first indication information is used to indicate whether a MAC entity of the terminal device starts to enter an active period of the DRX cycle after the scheduling request is sent;

the processing unit is specifically configured to:

and controlling the MAC entity of the terminal equipment to determine whether to start to enter the active period of the DRX cycle according to the first indication information.

22. The terminal device of claim 21, wherein the processing unit is specifically configured to:

If the first indication information indicates that the MAC entity of the terminal equipment does not enter the active period of the DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to determine that the MAC entity does not enter the active period of the DRX cycle after the scheduling request is sent.

23. The terminal device of claim 22, wherein if the first indication information indicates that the MAC entity of the terminal device does not enter an active period of a DRX cycle after the scheduling request is sent, the processing unit is further configured to:

controlling a MAC entity of the terminal device to start entering an active period of a DRX cycle after a first timer for the DRX cycle is started; or

Controlling the MAC entity of the terminal device to start entering an active period of a DRX cycle after delaying the first duration.

24. 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 configured to:

after the communication unit sends the scheduling request, if the MAC entity of the terminal equipment is in the inactive period of the DRX cycle, controlling the MAC entity of the terminal equipment to start the second timer, and determining that the MAC entity of the terminal equipment starts to enter the active period of the DRX cycle after the second timer is overtime; or

After the communication unit sends the scheduling request, if the MAC entity of the terminal device is in the inactive period of the DRX cycle, controlling the MAC entity of the terminal device to start the second timer, and if the MAC entity of the terminal device is started aiming at the first timer of the DRX cycle before the second timer is overtime, controlling the MAC entity of the terminal device to determine to start entering the active period of the DRX cycle.

25. The terminal device of claim 24, wherein if a 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 whether the MAC entity of the terminal device starts to enter an active period of a DRX cycle after the scheduling request is sent, the processing unit is further configured to:

if the first indication information indicates that the MAC entity of the terminal equipment starts to enter the active period of a DRX cycle after the scheduling request is sent, controlling the MAC entity of the terminal equipment to start the second timer or not to start the second timer; or

26. The terminal device of claim 24,

each logical channel is configured with one of the second timers; or

27. The terminal device of claim 19, wherein the DRX cycle that the MAC entity of the terminal device is configured with comprises a long cycle and a short cycle,

the processing unit is specifically configured to:

And if the current inactive period is in the short cycle of the DRX cycle, controlling the MAC entity of the terminal equipment to determine to start to enter the active period of the DRX cycle after the communication unit sends the scheduling request.

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

and the MAC entity controlling the terminal equipment determines whether to start entering the active period of the DRX period after the scheduling request is sent according to the time which is in the inactive period of the DRX period before.

29. The terminal device according to any of claims 19 to 28, wherein the processing unit is further configured to determine whether to delay sending the scheduling request before the communication unit sends the scheduling request.

30. The terminal device of claim 29, wherein the processing unit is specifically configured to:

and determining whether to delay the sending of the scheduling request according to a first logic channel triggering the scheduling request.

31. The terminal device of claim 30, wherein the processing unit is specifically configured to:

determining whether to delay sending the scheduling request according to a parameter of the first logical channel, wherein the parameter of the first logical channel comprises at least one of the following: the priority of the logical channel, the list of the allowed subcarrier intervals SCS of the logical channel, the duration of the maximum physical uplink shared channel PUSCH of the logical channel, and the allowed authorization type of the configuration of the logical channel.

32. The terminal device of claim 30, wherein the communication unit is further configured to:

the processing unit is specifically configured to:

33. The terminal device of claim 29, wherein the DRX cycle that the MAC entity of the terminal device is configured with comprises a long cycle and a short cycle,

the processing unit is specifically configured to:

34. The terminal device of claim 29, wherein the processing unit is specifically configured to:

determining whether to delay transmission of the scheduling request according to a time that has been in an inactive period of a DRX cycle before.

35. The terminal device of claim 29, wherein if the processing unit determines to delay sending the scheduling request, the processing unit is further configured to:

and after determining that the third duration is delayed, sending the scheduling request, or determining that the scheduling request is sent by delaying to a time point when a first timer for the DRX period is started recently, wherein the third duration is preconfigured, or the third duration is configured by the network equipment and is less than or equal to a time distance from a first available Physical Uplink Control Channel (PUCCH) resource position to the time point when the first timer for the DRX period is started recently.

36. The terminal device according to any of claims 19 to 28 and 30 to 35, wherein if the MAC entity of the terminal device is in the inactive period of the DRX cycle, the communication unit is further configured to:

and after the MAC entity of the terminal equipment enters the activation period of the DRX period, monitoring a Physical Downlink Control Channel (PDCCH).

37. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 18.

38. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 18.

39. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 18.