CN114424672A

CN114424672A - Method for monitoring wake-up signal, terminal equipment and network equipment

Info

Publication number: CN114424672A
Application number: CN201980100581.7A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-12-17
Filing date: 2019-12-17
Publication date: 2022-04-29
Also published as: WO2021120013A1

Abstract

The embodiment of the application relates to a method for monitoring a wake-up signal, a terminal device and a network device, wherein the method comprises the following steps: the method comprises the steps that terminal equipment receives configuration information sent by network equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to a Media Access Control (MAC) entity of the terminal equipment; and the terminal equipment determines whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the wakeup signal WUS. The method for monitoring the wake-up signal, the terminal device and the network device in the embodiment of the application can effectively reduce the power consumption of the terminal device under the condition that a plurality of DRX configurations are configured.

Description

Method for monitoring wake-up signal, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method, a terminal device, and a network device for monitoring a wake-up signal.

Background

In the current standardization process of the 5th generation, 5G New Radio (NR), in order to achieve the purpose of power saving, a concept of Discontinuous Reception (DRX) is introduced, that is, a terminal device only needs to monitor a Physical Downlink Control Channel (PDCCH) in an active period, and does not need to monitor the PDCCH in an inactive period. However, the network device may not send the PDCCH to the terminal device in the active period, but the terminal device still needs to monitor the PDCCH in the active period, which may cause a waste of power of the terminal device.

Therefore, how to reduce the power consumption of the terminal device becomes an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a method for monitoring a wake-up signal, a terminal device and a network device, which can effectively reduce the power consumption of the terminal device under the condition that a plurality of DRX configurations are configured.

In a first aspect, a method for listening for a wake-up signal is provided, where the method includes: the method comprises the steps that terminal equipment receives configuration information sent by network equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to a Media Access Control (MAC) entity of the terminal equipment; and the terminal equipment determines whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the wakeup signal WUS.

In a second aspect, a method of listening for a wake-up signal is provided, the method comprising: the method comprises the steps that network equipment sends configuration information to terminal equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to a Media Access Control (MAC) entity of the terminal equipment, and the configuration information is also used for indicating whether the terminal equipment monitors a wakeup signal (WUS); wherein a first DRX configuration of the plurality of DRX configurations corresponds to a primary cell (PCell) or a primary and secondary cell (PScell), an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided for performing the method of the second aspect or its implementation manners.

In particular, the network device comprises functional modules for performing the methods of the second aspect or its implementations described above.

In a fifth 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, and executing the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network 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, and executing the method of the second aspect or each implementation mode thereof.

In a seventh aspect, an apparatus is provided for implementing the method in any one of the first to second aspects or implementations thereof.

Specifically, the apparatus includes: a processor configured to call and run the computer program from the memory, so that the apparatus on which the apparatus is installed performs the method according to any one of the first aspect to the second aspect or the implementation manner thereof.

Optionally, the device is a chip.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

According to the technical scheme, under the condition that the network equipment configures a plurality of DRX configurations for one MAC entity of the terminal equipment, the active period of at least part of the DRX configurations may overlap with the monitoring time of the WUS, and meanwhile, the active period of the rest DRX configurations in the DRX configurations may not overlap with the monitoring time of the WUS. Therefore, the terminal device determines whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the WUS, so that the power consumption of the terminal device can be effectively reduced.

Drawings

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

Fig. 2 is a diagram of a DRX cycle according to an embodiment of the present application.

Fig. 3 is a schematic flow diagram of listening for WUS according to an embodiment of the application.

Fig. 4 is a schematic diagram of a Long DRX cycle and a Short DRX cycle according to an embodiment of the present application.

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

Fig. 6 is a schematic block diagram of a network device according to an embodiment of the present application.

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

Fig. 8 is a schematic block diagram of an apparatus according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication system 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 technical scheme of the embodiment of the application can be applied to various communication systems, for example: 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, a LTE Frequency Division Duplex (FDD) System, a LTE Time Division Duplex (TDD) System, a Long Term Evolution (Advanced) System, a New Radio (NR) System, an Evolution System of an NR System, a to-be-unlicensed-spectrum (LTE-to-be-unlicensed-spectrum) System, a to-be-unlicensed-spectrum (NR) System, a GSM-to-be-unlicensed-spectrum (GSM) System, a CDMA-System, a WCDMA System, a GPRS-Radio (GPRS) System, a LTE-to-be-unlicensed-spectrum (LTE-to-be-unlicensed-spectrum, a LTE-to-be-unlicensed-spectrum (NR) System, a GSM-to-be-capable-spectrum (NR) System, a GSM-to-be-capable-spectrum (LTE-to-be-capable-free-spectrum (NR) System, UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN), Wireless Fidelity (WiFi), next generation communication system, or other communication system.

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. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

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.

It should also be understood that the communication system 100 shown in fig. 1 may also be an NTN system, that is, the network device 110 in fig. 1 may be a satellite.

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

In the communication framework shown in fig. 1, packet-based data streams may be transmitted between end device 120 and network device 110, however, packet-based data streams are typically bursty. In other words, the terminal device 120 has data transmitted for a period of time, but may not have data transmitted for a subsequent longer period of time. Thus, if the terminal device 120 always blindly detects the PDCCH, it may cause excessive power consumption of the terminal device.

To reduce the power consumption of the terminal device, LTE proposes the concept of DRX. Specifically, the network device may configure the terminal device to wake up (DRX ON) at a time predicted by the network, at which time the terminal device monitors the PDCCH; meanwhile, the network can also configure the terminal device to sleep (DRX OFF) at a time predicted by the network, that is, the terminal device does not need to monitor the PDCCH. Thus, if the network device has data to transmit to the terminal device, the network device can schedule the terminal device during the time that the terminal device is in DRX ON, and during DRC OFF, since the radio frequency is OFF, the power consumption of the terminal device can be reduced.

Each Media Access Control (MAC) entity (entity) may have a DRX configuration.

As shown in fig. 2, the Cycle (Cycle) of the DRX configuration configured by the network device for the terminal device is composed of an active period (On Duration) and a dormant period (Opportunity for DRX). In an RRC CONNECTED mode (RRC CONNECTED), if the terminal device configures a DRX function, the terminal device may monitor and receive a PDCCH within an On Duration time; the terminal device does not monitor the PDCCH during the sleep period to reduce power consumption. The Active period may also be referred to as DRX Active Time.

It should be understood that the terminal device in the sleep period in the embodiment of the present application does not receive the PDCCH, but may receive data from other physical channels. The embodiments of the present application are not particularly limited.

For example, the terminal device may receive a Physical Downlink Shared Channel (PDSCH), an acknowledgement/non-acknowledgement (ACK/NACK), and the like. For another example, in Semi-Persistent Scheduling (SPS), the terminal device may receive PDSCH data configured periodically.

For power saving purposes, the DRX described above is introduced, i.e. the terminal device only needs to monitor the PDCCH during the active period, and does not monitor the PDCCH during the inactive period. However, the network device may not send the PDCCH to the terminal device in the active period, that is, the terminal device may not receive the PDCCH in the active period, but the terminal device still needs to monitor the PDCCH in the active period, which may cause a waste of power of the terminal device.

To solve this problem, a Wake-up Signal (WUS) mechanism is introduced. That is, the terminal device may monitor the WUS before starting the DRX on duration timer (DRX on duration timer), and determine whether the DRX on duration timer needs to be started according to the content indicated by the WUS. If the WUS instructs the terminal device to start a DRX-onDurationTimer (i.e., instructs the terminal device to wake up), the terminal device may start the DRX-onDurationTimer in a subsequent DRX cycle and monitor a PDCCH sent by the network device; if the WUS indicates that the terminal device does not start the DRX-onDurationTimer (i.e., indicates that the terminal device is not awake), the terminal device does not start the DRX-onDurationTimer in a subsequent DRX cycle, thereby achieving the purpose of saving power.

Meanwhile, if the timing of monitoring the WUS by the terminal device overlaps with the activation period, the terminal device may not monitor the WUS and start a drx-onDurationTimer by default.

By introducing the WUS mechanism, the network equipment can inform the terminal whether the terminal needs to start the drx-onDurationTimer to monitor the PDCCH by sending the WUS to the terminal equipment before the starting time of the drx-onDurationTimer, and the aim of saving power of the terminal equipment can be further fulfilled.

For example, the network device may notify the terminal device not to start a drx-onDurationTimer when predicting that a certain terminal device will not be scheduled for a future period of time, so that unnecessary PDCCH monitoring performed by the terminal device may be reduced.

In some embodiments of the present application, the communication system 100 may be a 5G NR. The 5G NR further increases the system bandwidth on the basis of 4G to provide a larger data transmission rate, thereby improving the user experience. For example, in 5G NR, for a frequency band below 6GHz, the maximum bandwidth supported by a single carrier may be 100 MHz; for frequency bands above 6GHz, the maximum bandwidth supported by a single carrier may be 400 MHz.

Like the LTE system, the 5G NR can also support the CA technology. For a terminal device supporting the CA feature, the terminal device may have a Primary Cell (PCell), and the network device may also configure one or more Secondary cells (scells) for the terminal device through Radio Resource Control (RRC). The SCell has two states, namely activated state and deactivated state, and only when the SCell is in the activated state, the terminal device can transmit and receive data on the SCell.

The terminal device may monitor the PDCCH on the PCell and the activated SCell(s) at the same time, and transmit and receive data, so that the data transmission rate may be improved.

At present, an enhancement method under the NR CA scenario is proposed, that is, a scheme that 2 DRX configurations can be configured for one MAC entity.

For a scenario where one MAC entity configures two sets of DRX configurations, each DRX configuration has its corresponding active period, and then there may be a case where the active period of one DRX configuration overlaps with the monitoring timing of the WUS, and the active period of the other DRX configuration does not overlap with the monitoring timing of the WUS. In this case, how the terminal device listens to the WUS to reduce power consumption of the terminal device is a problem that needs to be solved urgently.

In view of this, an embodiment of the present application provides a method for monitoring a WUS, which can effectively reduce power consumption of a terminal device when a network device configures multiple DRX configurations for the terminal device.

Fig. 3 is a schematic flow diagram of a method 200 of listening for WUS according to an embodiment of the application. The method described in fig. 3 may be performed by a terminal device, such as terminal device 120 shown in fig. 1, and a network device, such as network device 110 shown in fig. 1. As shown in fig. 3, the method 200 may include at least some of the following.

In 210, the network device sends configuration information to the terminal device, the configuration information comprising a plurality of DRX configurations corresponding to one MAC entity of the terminal device;

in 220, the terminal device receives the configuration information.

In 230, the terminal device determines whether to monitor the WUS according to an overlapping situation of the active periods of the plurality of DRX configurations and the monitoring occasions of the WUS.

The parameters of the DRX configuration may include, but are not limited to:

drx-onDurationTimer: duration of terminal device wake-up at the beginning of one DRX Cycle;

DRX slot offset (DRX-SlotOffset): the terminal equipment starts the time delay of the drx onDurationTimer;

DRX inactivity timer (DRX-inactivity timer): after receiving a PDCCH indicating uplink initial transmission or downlink initial transmission, the terminal equipment continues to monitor the duration of the PDCCH;

DRX downlink retransmission timer (DRX-retransmission timerdl): the terminal equipment monitors the longest duration of the PDCCH indicating the downlink retransmission scheduling. Each downlink HARQ process except for a broadcast Hybrid Automatic Repeat reQuest (HARQ) process corresponds to a drx-retransmission timerdl;

DRX uplink retransmission timer (DRX-retransmission timer ul): the terminal equipment monitors the longest duration of a PDCCH indicating uplink retransmission scheduling. Each uplink HARQ process corresponds to one drx-retransmission TimerUL;

DRX long cycle initial offset (DRX-LongCycleStartOffset): a subframe offset for configuring a Long DRX cycle (Long DRX cycle), and a start of the Long DRX cycle and a DRX Short cycle (Short DRX cycle);

DRX short cycle (DRX-short cycle): short DRX cycle, which is optional configuration;

DRX short cycle timer (DRX-ShortCycleTimer): the duration that the terminal device is in the Short DRX cycle (and does not receive any PDCCH), which is an optional configuration;

DRX downlink HARQ Round Trip Time (RTT) timer (DRX-HARQ-RTT-TimerDL): the terminal device expects to receive the minimum latency required for the PDCCH indicating downlink scheduling. Each downlink HARQ process except the broadcast HARQ process corresponds to one drx-HARQ-RTT-TimerDL;

DRX uplink HARQ RTT timer (DRX-HARQ-RTT-timerll): the terminal equipment expects to receive the minimum waiting time required by the PDCCH indicating the uplink scheduling, and each uplink HARQ process corresponds to one drx-HARQ-RTT-TimerUL.

Among the parameters of the DRX configuration mentioned above, the network device may configure at least one DRX-on duration timer and DRX-inactivity timer for each DRX configuration of the plurality of DRX configurations, respectively, and the DRX configuration parameters other than DRX-on duration timer and DRX-inactivity timer may be common configuration parameters of the plurality of DRX configurations.

Optionally, the active period of the DRX configuration may include the following cases:

a) any one of drx-onDurationTimer, drx-inactivytimeter, drx-retransmission timerdl, drx-retransmission timerll, and a random access contention resolution timer (ra-ContentionResolutionTimer) is running.

b) A terminal device sends a Scheduling Request (SR) on a Physical Uplink Control Channel (PUCCH) and is in a waiting (pending) state.

c) In the contention-based Random Access process, the terminal device does not receive primary initial transmission indicated by a PDCCH scrambled by a Cell-radio network temporary identifier (C-RNTI) after successfully receiving a Random Access Response (RAR).

When the activation period is over, the terminal equipment can extend the duration of the activation period by starting or restarting the drx-inactivity timer. The terminal device may start drx-inactivity timer upon receiving PDCCH, whereby the time of the activation period may be extended with the start of drx-inactivity timer. Of course, the terminal device may restart the DRX-inactivity timer when receiving the PDCCH and currently starting the DRX-inactivity timer.

It should be understood that in the embodiment of the present application, the Active period of the DRX configuration may also be expressed as DRX Active Time or other names, and the DRX configuration may also be expressed as DRX group (group), which is not limited in the embodiment of the present application.

For convenience of subsequent description, the embodiments of the present application will be described by taking a first DRX configuration and a second DRX configuration of a plurality of DRX configurations as an example, but the embodiments of the present application are not limited thereto.

A first DRX configuration of the multiple DRX configurations corresponds to a PCell or a Primary Secondary Cell (PSCell), where the PCell may serve as a working Frequency band 1(Frequency Range 1, FR1), and a network device configures a monitoring time of the WUS on the PCell. The active period of the first DRX configuration overlaps with the monitoring occasion of the WUS.

The second DRX configuration corresponds to a SCell, which may be a FR2 serving cell. The second DRX configuration is not in the active period, wherein the absence of the second DRX configuration in the active period may also be expressed as the active period of the second DRX configuration does not overlap with the monitoring timing of the WUS.

It should be understood that a serving cell corresponding to a DRX configuration may also be referred to as a serving cell associated with one DRX configuration, or may also be referred to as a serving cell included in one DRX configuration, and the like. Each DRX configuration can correspond to at least one service cell, and the service cells corresponding to one DRX configuration can use the same DRX configuration.

In the communication system, the network device may configure a Short DRX cycle and/or a Long DRX cycle for the terminal device according to different service scenarios. If the terminal device currently uses the Short DRX cycle, the time interval for the terminal device to enter the next active period from the current active period is Short. If the terminal device currently uses the Long DRX cycle, the time interval for the terminal device to enter the next activation period from the current activation period is longer.

For example, when performing Voice Over Internet Protocol (VOIP) service based on Internet Protocol (IP), a Voice codec usually sends a VOIP packet for 20ms, and then a Short DRX cycle with a length of 20ms can be configured; and a Long DRX cycle may be configured during a longer silence period during a voice call.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone.

Optionally, the first DRX configuration may be in a Long DRX cycle, or may also be in a Short DRX cycle. Similar to the first DRX configuration, the second DRX configuration may be in a Long DRX cycle, or may be in a Short DRX cycle. In fig. 4, the first DRX configuration is in Short DRX cycle and the second DRX configuration is in Long DRX cycle.

The terminal device may independently start a first DRX-onDurationTimer in a first DRX configuration and a second DRX-onDurationTimer in a second DRX configuration. Furthermore, the terminal device may switch to the respective DRX cycles independently for the first DRX configuration and the second DRX configuration. For example, as shown in fig. 4, the terminal device may switch to a Short DRX cycle for the first DRX configuration, while the second DRX configuration may still be in a Long DRX cycle.

In an embodiment of the present application, the terminal device may determine whether to listen to the WUS according to the following manner.

Mode 1

The terminal device determines to listen to the WUS.

In the case where the terminal device determines to listen for WUS, further, the method 200 may further include: and the terminal equipment determines whether to start the second drx-onDurationTimer according to the monitoring result of the WUS.

Specifically, if the terminal device does not monitor the WUS at the listening timing of the WUS, the terminal device may determine whether to start the second drx-onDurationTimer based on the configuration of the network device. Optionally, the network device may indicate to the terminal device whether to start the second drx-onDurationTimer based on the higher layer configuration signaling. If the high-level configuration signaling indicates the terminal device to start the drx-onDurationTimer, the terminal device may start a second drx-onDurationTimer; if the high layer configuration signaling indicates that the terminal device does not start the drx-onDurationTimer, the terminal device may not start the second drx-onDurationTimer.

Or if the terminal device monitors the WUS and the WUS indicates the terminal device to start the drx-onDurationTimer, the terminal device starts the second drx-onDurationTimer.

Or, if the terminal device monitors the WUS and the WUS indicates that the terminal device does not start the drx-onDurationTimer, the terminal device may not start the second drx-onDurationTimer.

If the terminal device determines to start the second DRX-onDurationTimer, the terminal device may determine the time to start the second DRX-onDurationTimer according to whether the second DRX configuration is currently in a Short DRX cycle or a Long DRX cycle, as follows:

if the second DRX configuration is in a Short DRX cycle, the time for the terminal device to start the second DRX onDurationTimer needs to satisfy: [ (SFN × 10) + subframe number ] module (drx-ShortCycle) (drx-StartOffset) module (drx-ShortCycle).

Wherein modulo represents the modulo operation, SFN represents the frame number to start the second DRX-onDurationTimer, subframe number represents the subframe number to start the second DRX-onDurationTimer, DRX-ShortCycle represents the cycle duration of the Short DRX cycle, and DRX-StartOffset represents the subframe offset to start the second DRX-onDurationTimer.

If the second DRX is in the Long DRX cycle, the time for the terminal device to start the second DRX onDurationTimer may satisfy: [ (SFN × 10) + subframe number ] module (DRX-LongCycle) ═ DRX-StartOffset, where DRX-LongCycle denotes the cycle duration of Long DRX cycle.

In the technical solution of the mode 1, the terminal device monitors the WUS, so that the terminal device can still achieve the purpose of power saving based on the WUS in the second DRX configuration.

Mode 2

The terminal device determines not to listen to the WUS.

In this case, the terminal device may start the first drx-onDurationTimer and the second drx-onDurationTimer at the same time.

In the technical scheme of the mode 1, the behavior of the terminal device is consistent with the behavior of the existing terminal device for monitoring the WUS, that is, as long as the time for monitoring the WUS by the terminal device overlaps with the activation period of the DRX configuration, the terminal device does not monitor the WUS, and needs to start a DRX-onDurationTimer, so that the terminal device can blindly detect the PDCCH during the activation period and obtain the scheduling of the network device in time.

Mode 3

And the terminal equipment determines whether to monitor the WUS according to the configuration of the network equipment.

Specifically, if the network device configures the terminal device to monitor the WUS, for example, the configuration information is also used to indicate whether the terminal device monitors the WUS, the terminal device may determine to monitor the WUS; if the network device configures the terminal device not to listen to the WUS, the terminal device may determine not to listen to the WUS.

As an example, if the network device may send a PDCCH to the terminal device within a preset time, the network device may configure the terminal device to monitor the WUS; the network device may configure the terminal device not to monitor the WUS if the network device may not send the PDCCH to the terminal device within a preset time.

As another example, if the traffic of the terminal device at the current time is large, the network device may configure the terminal device not to monitor the WUS; if the traffic of the terminal device at the current moment is normal or small, the network device can configure the terminal device to monitor the WUS.

In the case that the terminal device determines to monitor the WUS, further, the terminal device may also determine whether to start the second drx-onDurationTimer according to a monitoring result of the WUS.

Mode 4

When at least one of the first DRX configuration and the second DRX configuration is in a Long DRX cycle, the terminal device may determine to monitor the WUS.

Referring again to fig. 4, the second DRX configuration is in the Long DRX cycle, the terminal device may determine to monitor the WUS.

Mode 5

When at least one DRX configuration in the first DRX configuration and the second DRX configuration is in a Short DRX cycle, the terminal device can determine whether to monitor the WUS according to the configuration of the network device.

It should be understood that although modes 1-5 are described separately above, this does not mean that modes 1-5 are independent and the descriptions of the various modes may be parameterized with one another. For example, the description about whether the terminal device determines to start the second drx on duration timer according to the monitoring result of the WUS in mode 1 may be applicable to modes 3 to 5. For the sake of brevity, modes 3-5 are not described here too much.

It should also be understood that "first" and "second" in the embodiments of the present application are merely for distinguishing different objects, and do not limit the scope of the embodiments of the present application.

It should be noted that, since the active period of the first DRX configuration overlaps with the monitoring timing of the WUS, the terminal device may determine to start the first DRX-onDurationTimer.

In the embodiment of the application, when a network device configures a plurality of DRX configurations for one MAC entity of a terminal device, an active period of at least a part of the DRX configurations may overlap with a monitoring occasion of a WUS, and an active period of the remaining part of the DRX configurations may not overlap with the monitoring occasion of the WUS. Therefore, the terminal device determines whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the WUS, so that the power consumption of the terminal device can be effectively reduced.

The preferred embodiments of the present application have been described in detail with reference to the accompanying drawings, however, the present application is not limited to the details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the technical idea of the present application, and these simple modifications are all within the protection scope of the present application.

For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and various combinations that may be possible are not described in this application in order to avoid unnecessary repetition.

For example, various embodiments of the present application may be arbitrarily combined with each other, and the same should be considered as the disclosure of the present application as long as the concept of the present application is not violated.

It should be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

The method of listening for WUS according to the embodiment of the present application is described above in detail, and a communication device according to the embodiment of the present application will be described below with reference to fig. 5 to 7, and the technical features described in the method embodiment are applicable to the following device embodiments.

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

a communication unit 310, configured to receive configuration information sent by a network device, where the configuration information includes multiple DRX configurations corresponding to a MAC entity of the terminal device.

And the processing unit 320 is configured to determine whether to monitor the WUS according to an overlapping situation of the active periods of the multiple DRX configurations and the monitoring occasions of the wakeup signal WUS.

Optionally, in this embodiment of the present application, a first DRX configuration of the multiple DRX configurations corresponds to a primary cell PCell or a primary secondary cell PScell, and when an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS and a second DRX configuration of the multiple DRX configurations is not in the active period, the processing unit 320 is specifically configured to: determining to listen to the WUS.

Optionally, in this embodiment of the present application, the processing unit 320 is further configured to: and determining whether a second DRX duration timer in the second DRX configuration is started or not according to the monitoring result of the WUS.

Optionally, in this embodiment of the application, the processing unit 320 is specifically configured to: determining whether to start the second DRX duration timer based on a high-level configuration if the WUS is not monitored at the monitoring opportunity of the WUS; if the WUS is monitored and the WUS is used for indicating the terminal equipment to start a DRX duration timer, and determining to start the second DRX duration timer; and if the WUS is monitored and the WUS is used for indicating the terminal equipment not to start the DRX duration timer, determining not to start the second DRX duration timer.

Optionally, in this embodiment of the application, the processing unit 320 is specifically configured to: if the processing unit is configured by the high-level configuration signaling to start the second DRX continuous timer, starting the second DRX continuous timer; and if the processing unit is configured by the high-level configuration signaling to not start the second DRX continuous timer, starting the second DRX continuous timer.

Optionally, in this embodiment of the present application, a first DRX configuration of the multiple DRX configurations corresponds to a PCell or a PScell, and when an active period of the first DRX configuration overlaps with a monitoring timing of the WUS and a second DRX configuration of the multiple DRX configurations is not in the active period, the processing unit 320 is specifically configured to: determining not to listen to the WUS; or determining whether to monitor the WUS according to the configuration of the network equipment.

Optionally, in this embodiment of the application, if the processing unit 320 determines not to monitor the WUS, the processing unit 320 is further configured to: starting a DRX duration timer in the plurality of DRX configurations.

Optionally, in this embodiment of the present application, the first DRX configuration is in a DRX long cycle, or the first DRX configuration is in a DRX short cycle.

It should be understood that the terminal device 300 may correspond to the terminal device in the method 200, and corresponding operations of the terminal device in the method 200 may be implemented, which are not described herein again for brevity.

Fig. 6 shows a schematic block diagram of a network device 400 of an embodiment of the application. As shown in fig. 6, the network device 400 includes:

a communication unit 410, configured to send configuration information to a terminal device, where the configuration information includes multiple DRX (discontinuous reception) configurations corresponding to a MAC entity of the terminal device, and the configuration information is further configured to indicate whether the terminal device monitors a wake-up signal WUS; wherein a first DRX configuration of the plurality of DRX configurations corresponds to a primary cell (PCell) or a primary and secondary cell (PScell), an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.

Optionally, in this embodiment of the application, if the configuration information is used to instruct the terminal device to monitor a wake up signal WUS, and the terminal device does not monitor the WUS at a monitoring time of the WUS, the network device 400 further includes: a processing unit 420, configured to configure whether the terminal device starts a second DRX duration timer in the second DRX configuration;

the communication unit 410 is further configured to: and indicating whether to start the second DRX duration timer or not to the terminal equipment through high-layer configuration signaling.

It should be understood that the network device 400 may correspond to the network device in the method 200, and the corresponding operations of the network device in the method 200 may be implemented, which are not described herein again for brevity.

Fig. 7 is a schematic structural diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 shown in fig. 7 comprises 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. 7, the communication device 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, as shown in fig. 7, the communication device 500 may further include a transceiver 530, and the processor 5710 may control the transceiver 530 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 530 may include a transmitter and a receiver, among others. The transceiver 530 may further include one or more antennas.

Optionally, the communication device 500 may specifically be a network device in the embodiment of the present application, and the communication device 500 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 500 may specifically be a terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding procedure implemented by the terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

Fig. 8 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 600 shown in fig. 8 includes a processor 610, and the processor 610 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. 8, the apparatus 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

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

Optionally, the apparatus may be applied to the network device in the embodiment of the present application, and the apparatus 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.

Alternatively, the apparatus 600 may be a chip. 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.

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.

Fig. 9 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 9, the communication system 700 includes a terminal device 710 and a network device 720.

The terminal device 710 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 720 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.

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 terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the terminal 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 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.

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 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 terminal 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 network device in the embodiment of the present application, and the computer program instructions enable the computer to execute the 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.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the 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 terminal 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 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.

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

A method of listening for a wake-up signal, the method comprising:

the method comprises the steps that terminal equipment receives configuration information sent by network equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to a Media Access Control (MAC) entity of the terminal equipment;

and the terminal equipment determines whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the wakeup signal WUS.
The method of claim 1, wherein a first DRX configuration of the plurality of DRX configurations corresponds to a primary cell (PCell) or a primary secondary cell (PScell), and wherein when an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS and a second DRX configuration of the plurality of DRX configurations is not in the active period, the terminal device determines whether to monitor the WUS according to an overlapping condition of the active periods of the plurality of DRX configurations and the monitoring occasion of a wake-up signal (WUS), comprising:

the terminal device determines to monitor the WUS.
The method of claim 2, further comprising:

and the terminal equipment determines whether a second DRX duration timer in the second DRX configuration is started or not according to the monitoring result of the WUS.
The method of claim 3, wherein the terminal device determining whether a second DRX duration timer in the second DRX configuration is started based on the monitoring result of the WUS comprises:

if the terminal equipment does not monitor the WUS at the monitoring time of the WUS, the terminal equipment determines whether to start the second DRX duration timer or not based on high-level configuration;

if the terminal equipment monitors the WUS and the WUS is used for indicating the terminal equipment to start a DRX duration timer, the terminal equipment determines to start the second DRX duration timer;

and if the terminal equipment monitors the WUS and the WUS is used for indicating the terminal equipment not to start the DRX continuous timer, the terminal equipment determines not to start the second DRX continuous timer.
The method of claim 4, wherein the terminal device determining whether to start the second DRX duration timer based on a higher layer configuration comprises:

if the terminal equipment is configured by the high-level configuration signaling to start the second DRX continuous timer, the terminal equipment starts the second DRX continuous timer;

and if the terminal equipment is configured by the high-level configuration signaling to not start the second DRX continuous timer, the terminal equipment starts the second DRX continuous timer.
The method of claim 1, wherein a first DRX configuration of the plurality of DRX configurations corresponds to a PCell or a PScell, and wherein when an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS and a second DRX configuration of the plurality of DRX configurations is not in the active period, the terminal device determines whether to monitor the WUS according to an overlapping situation of the active period of the plurality of DRX configurations and the monitoring occasion of a wake-up signal WUS, comprising:

the terminal device determines not to monitor the WUS; or

And the terminal equipment determines whether to monitor the WUS according to the configuration of the network equipment.
The method of claim 6, wherein if the terminal device determines not to listen to the WUS, the method further comprises:

the terminal device starts a DRX duration timer in the plurality of DRX configurations.
The method according to any of claims 2 to 7, wherein the first DRX configuration is in a DRX long cycle or wherein the first DRX configuration is in a DRX short cycle.
A method of listening for a wake-up signal, the method comprising:

the method comprises the steps that network equipment sends configuration information to terminal equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to a Media Access Control (MAC) entity of the terminal equipment, and the configuration information is also used for indicating whether the terminal equipment monitors a wakeup signal (WUS);

wherein a first DRX configuration of the plurality of DRX configurations corresponds to a primary cell (PCell) or a primary and secondary cell (PScell), an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.
The method of claim 9, wherein if the configuration information indicates that the terminal device listens for a Wake Up Signal (WUS) and the terminal device does not listen to the WUS at a listening time for the WUS, the method further comprises:

the network equipment configures whether the terminal equipment starts a second DRX duration timer in the second DRX configuration;

and the network equipment indicates whether to start the second DRX duration timer or not to the terminal equipment through high-level configuration signaling.
The method according to claim 9 or 10, wherein the first DRX configuration is in DRX long cycle or the first DRX configuration is in DRX short cycle.
A terminal device, comprising:

a communication unit, configured to receive configuration information sent by a network device, where the configuration information includes multiple DRX (discontinuous reception) configurations corresponding to a MAC entity of the terminal device;

and the processing unit is used for determining whether to monitor the WUS according to the overlapping condition of the active periods of the plurality of DRX configurations and the monitoring time of the wakeup signal WUS.
The terminal device of claim 12, wherein a first DRX configuration of the multiple DRX configurations corresponds to a primary cell PCell or a primary and secondary cell PScell, and wherein when an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS and a second DRX configuration of the multiple DRX configurations is not in the active period, the processing unit is specifically configured to:

determining to listen to the WUS.
The terminal device of claim 13, wherein the processing unit is further configured to:

and determining whether a second DRX duration timer in the second DRX configuration is started or not according to the monitoring result of the WUS.
The terminal device of claim 14, wherein the processing unit is specifically configured to:

determining whether to start the second DRX duration timer based on a high-level configuration if the WUS is not monitored at the monitoring opportunity of the WUS;

if the WUS is monitored and the WUS is used for indicating the terminal equipment to start a DRX duration timer, and determining to start the second DRX duration timer;

and if the WUS is monitored and the WUS is used for indicating the terminal equipment not to start the DRX duration timer, determining not to start the second DRX duration timer.
The terminal device of claim 15, wherein the processing unit is specifically configured to:

if the processing unit is configured by the high-level configuration signaling to start the second DRX continuous timer, starting the second DRX continuous timer;

and if the processing unit is configured by the high-level configuration signaling to not start the second DRX continuous timer, starting the second DRX continuous timer.
The terminal device of claim 12, wherein a first DRX configuration of the multiple DRX configurations corresponds to a PCell or a PScell, and wherein when an active period of the first DRX configuration overlaps with a listening timing of the WUS and a second DRX configuration of the multiple DRX configurations is not in the active period, the processing unit is specifically configured to:

determining not to listen to the WUS; or

And determining whether to monitor the WUS according to the configuration of the network equipment.
The terminal device of claim 17, wherein if the processing unit determines not to listen to the WUS, the processing unit is further configured to:

starting a DRX duration timer in the plurality of DRX configurations.
The terminal device according to any of claims 13-18, wherein the first DRX configuration is in DRX long cycle or wherein the first DRX configuration is in DRX short cycle.
A network device, comprising:

a communication unit, configured to send configuration information to a terminal device, where the configuration information includes multiple DRX (discontinuous reception) configurations corresponding to a MAC (media access control) entity of the terminal device, and the configuration information is further configured to indicate whether the terminal device monitors a wake-up signal WUS;

wherein a first DRX configuration of the plurality of DRX configurations corresponds to a primary cell (PCell) or a primary and secondary cell (PScell), an active period of the first DRX configuration overlaps with a monitoring occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.
The network device of claim 20, wherein if the configuration information indicates that the terminal device listens for a Wake Up Signal (WUS) and the terminal device does not listen to the WUS at a listening time of the WUS, the network device further comprises:

a processing unit, configured to configure whether the terminal device starts a second DRX duration timer in the second DRX configuration;

the communication unit is further configured to:

and indicating whether to start the second DRX duration timer or not to the terminal equipment through high-layer configuration signaling.
The network device of claim 20 or 21, wherein the first DRX configuration is in DRX long cycle or wherein the first DRX configuration is in DRX short cycle.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor for invoking and executing the computer program stored in the memory, performing the method of any one of claims 1 to 8.
A network 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, performing the method of any of claims 9 to 11.
An apparatus, 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 8.
An apparatus, 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 9 to 11.
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 8.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 9 to 11.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 8.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 9 to 11.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1 to 8.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 9 to 11.