CN114424672B

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

Info

Publication number: CN114424672B
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: 2024-07-26
Anticipated expiration: 2039-12-17
Also published as: CN114424672A; WO2021120013A1

Abstract

The embodiment of the application relates to a method for monitoring a wake-up signal, terminal equipment and network equipment, wherein the method comprises the following steps: the method comprises the steps that a terminal device receives configuration information sent by a network device, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to one Media Access Control (MAC) entity of the terminal device; and the terminal equipment determines whether to monitor the WUS according to the overlapping condition of the activation periods of the DRX configurations and the monitoring occasions of the wake-up signals WUS. The method for monitoring the wake-up signal, the terminal equipment and the network equipment can effectively reduce the power consumption of the terminal equipment 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 for monitoring a wake-up signal, a terminal device, and a network device.

Background

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

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

Disclosure of Invention

The embodiment of the application provides a method for monitoring a wake-up signal, terminal equipment and network equipment, which can effectively reduce the power consumption of the terminal equipment 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, the method comprising: the method comprises the steps that a terminal device receives configuration information sent by a network device, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to one Media Access Control (MAC) entity of the terminal device; and the terminal equipment determines whether to monitor the WUS according to the overlapping condition of the activation periods of the DRX configurations and the monitoring occasions of the wake-up signals WUS.

In a second aspect, a method for listening for a wake-up signal is provided, the method comprising: the network equipment sends configuration information to the terminal equipment, wherein the configuration information comprises a plurality of Discontinuous Reception (DRX) configurations corresponding to one Media Access Control (MAC) entity of the terminal equipment, and the configuration information is also used for indicating whether the terminal equipment monitors a wake-up signal (WUS); wherein a first DRX configuration of the plurality of DRX configurations corresponds to the primary cell PCell or the primary secondary cell PScell, an active period of the first DRX configuration overlaps with a listening 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 for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

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

In a fifth aspect, a terminal device is provided comprising 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 various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides an apparatus for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

Optionally, the device is a chip.

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

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

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

In the above technical solution, in a case where the network device configures a plurality of DRX configurations for one MAC entity of the terminal device, an activation period of at least some of the plurality of DRX configurations may overlap with a listening occasion of WUS, and at the same time, an activation period of the remaining part of the plurality of DRX configurations may not overlap with a listening occasion of WUS. Therefore, the terminal device determines whether to monitor the WUS according to the overlapping condition of the activation periods of the plurality of DRX configurations and the monitoring occasions of the WUS, so that the power consumption of the terminal device can be effectively reduced.

Drawings

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

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

Fig. 3 is a schematic flow chart of listening to WUS according to an embodiment of the present 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 in accordance with an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general Packet Radio Service (GPRS), long term evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (Frequency Division Duplex, FDD) system, LTE time division duplex (Time Division Duplex, TDD), long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum on unlicensed spectrum, LTE-U system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Acces s, wiMAX) communication system, wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (WIRELESS FIDELITY, WIFI), next generation communication system or other communication system, etc.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle 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 future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (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 the other terminal device arranged to receive/transmit communication signals; and/or an internet of things (Internet of Things, ioT) device. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that may include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device 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 (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.

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

Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment 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 with communication functions, where the network device 110 and the terminal device 120 may be 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 a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should also be appreciated 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 used interchangeably herein.

In the communication framework shown in fig. 1, a packet-based data stream may be transmitted between terminal device 120 and network device 110, however, the packet-based data stream is typically bursty. In other words, the terminal device 120 has data transmission for a period of time, but may not have data transmission for a longer period of time in the following. Thus, if the terminal device 120 blindly detects the PDCCH at all times, excessive power consumption of the terminal device may be caused.

In order 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 at a network-predicted time (DRX ON), at which time the terminal device listens to the PDCCH; at the same time, the network may also configure the terminal device to sleep (DRX OFF) at times predicted by the network, i.e., the terminal device does not have 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 when the terminal device is in DRX ON, and can reduce power consumption of the terminal device due to radio frequency OFF during DRC OFF time.

Each media access Control (MEDIA ACCESS Control, MAC) entity (entity) may have a DRX configuration.

As shown in fig. 2, the period (Cycle) of the DRX configuration configured by the network device for the terminal device is composed of an active period (On Duration) and a sleep period (Opportunity for DRX). In an RRC CONNECTED mode (RRC CONNECTED) if the terminal device is configured with the DRX function, the terminal device can monitor and receive the PDCCH in an On Duration; 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, among other things.

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

For example, the terminal device may receive a physical downlink shared channel (Physical Downlink SHARED CHANNEL, PDSCH), an acknowledgement/non-acknowledgement (ACK/NACK), or the like. For another example, in Semi-persistent scheduling (Semi-PERSISTENT SCHEDULING, SPS), the terminal device may receive periodically configured PDSCH data.

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

To solve this problem, a Wake-up Signal (WUS) mechanism is introduced. That is, the terminal device may monitor WUS before starting a DRX-onduration timer (DRX-onduration timer), and determine whether the DRX-onduration timer needs to be started according to the content indicated by WUS. If the WUS indicates that the terminal device starts DRX-onduration timer (i.e. indicates that the terminal device wakes up), the terminal device may start DRX-onduration timer 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 DRX-onduration timer (i.e. indicates that the terminal device does not wake up), the terminal device does not start DRX-onduration timer in the subsequent DRX cycle, thereby achieving the purpose of saving power.

Meanwhile, if the timing of the terminal device listening to WUS overlaps with the activation period, the terminal device may not listen to WUS, but start drx-onduration timer by default.

By introducing a WUS mechanism, the network device can inform the terminal device whether the terminal needs to start the drx-onduration timer to monitor the PDCCH by sending the WUS to the terminal device before the starting time of the drx-onduration timer, so that the purpose of saving power of the terminal device can be achieved.

For example, if the network device predicts that a certain terminal device will not be scheduled for a future period of time, the terminal device may be informed that the drx-onduration timer is not started, so that unnecessary PDCCH monitoring by the terminal device may be reduced.

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

Like the LTE system, the 5G NR may also support the CA technology. For terminal devices supporting CA characteristics, the network device may configure the terminal device with one or more Secondary cells (scells) through radio resource control (Radio Resource Control, RRC) in addition to one primary Cell (PRIMARY CELL, PCELL). The SCell has two states of activation and deactivation, and the terminal equipment can send and receive data on the SCell only when the SCell is in the activation state.

The terminal device can monitor the PDCCH on the PCell and the activated one or more scells at the same time, and transmit and receive data, so that the data transmission rate can be improved.

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

For a scenario in which one MAC entity configures two sets of DRX configurations, each DRX configuration has its corresponding active period, it may occur that the active period of one DRX configuration overlaps with the listening occasion of WUS, while the active period of the other DRX configuration does not overlap with the listening occasion of WUS. In this case, how to monitor WUS by the terminal device to reduce power consumption of the terminal device is a problem to be solved.

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

Fig. 3 is a schematic flow chart of a method 200 of listening to WUS according to an embodiment of the present application. The method described in fig. 3 may be performed by a terminal device, such as the terminal device 120 shown in fig. 1, and a network device, such as the 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 transmits configuration information to the terminal device, the configuration information including 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 WUS according to the overlapping of the activation periods of the plurality of DRX configurations and the listening occasions of WUS.

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

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

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

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

DRX downlink retransmission timer (DRX-RetransmissionTimerDL): the terminal device listens for the longest duration of the PDCCH indicating the downlink retransmission schedule. Each downlink hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process except for the broadcast HARQ process corresponds to one drx-RetransmissionTimerDL;

DRX uplink retransmission timer (DRX-RetransmissionTimerUL): the terminal device listens for the longest duration of the PDCCH indicating the uplink retransmission schedule. Each uplink HARQ process corresponds to one drx-RetransmissionTimerUL;

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

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

DRX short cycle timer (DRX-ShortCycleTimer): the duration that the terminal device is in Short DRX cycle (and does not receive any PDCCH) is 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 the downlink schedule. Each downlink HARQ process except the broadcast HARQ process corresponds to one drx-HARQ-RTT-TimerDL;

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

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

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

a) Any one of drx-onDurationTimer, drx-INACTIVITYTIMER, DRX-RetransmissionTimerDL, drx-RetransmissionTimerUL and a random access contention resolution timer (ra-ContentionResolutionTimer) is running.

B) The terminal device sends a scheduling request (Scheduling Request, SR) on a physical uplink control channel (Physical Uplink Control Channel, PUCCH) and is in a waiting (pending) state.

C) In the contention-based random access procedure, the terminal device has not received one initial transmission of a Cell radio network temporary identity (Cell-RadioNetworkTemporaryIdentifier, C-RNTI) scrambled PDCCH indication after successful reception of the random access response (Random Access Response, RAR).

When the activation period is over, the terminal device can prolong the duration of the activation period by starting or restarting the drx-InactivityTimer. The terminal device may start the drx-incarvitytimer when receiving the PDCCH, so that the time of the activation period may be prolonged with the start of the drx-incarvitytimer. Of course, the terminal device may also restart the DRX-inactivity timer when it receives the PDCCH and has started the DRX-inactivity timer currently.

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 another name, and the DRX configuration may also be expressed as a DRX group (group), which is not limited in the embodiment of the present application.

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

A first DRX configuration of the plurality of DRX configurations corresponds to a PCell or primary and secondary cell (Primary Secondary Cell, PSCell), which may be a serving cell for Frequency Range 1 (fr 1), on which the network device configures a listening occasion of WUS. The active period of the first DRX configuration overlaps with the listening occasion of WUS.

The second DRX configuration corresponds to a SCell, which may be an FR2 serving cell. The second DRX configuration is not in active period, where the second DRX configuration is not in active period may also be expressed as the active period of the second DRX configuration does not overlap with the listening occasion of WUS.

It should be understood that the serving cell to which the DRX configuration corresponds may also be referred to as a serving cell to which the DRX configuration is associated, or may also be referred to as a serving cell to which the DRX configuration includes, etc. Each DRX configuration may correspond to at least one serving cell, and the serving cell to which one DRX configuration corresponds may use the same set of DRX configurations.

In the communication system, the network device may configure the Short DRX cycle and/or the 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 activation period from the current activation 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 a voice over internet protocol (Internet Protocol, IP) service is performed (Voice Over Intemet Protocol, VOIP), a voice codec typically transmits a VOIP packet for 20ms, so that a Short DRX cycle with a length of 20ms can be configured; while Long DRX cycles may be configured during voice calls for longer periods of silence.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, 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 also be in a Short DRX cycle. In fig. 4, the first DRX configuration is in the Short DRX cycle and the second DRX configuration is in the Long DRX cycle.

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

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

Mode 1

The terminal device determines to monitor WUS.

In the case that the terminal device determines to monitor 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 WUS at the listening occasion of WUS, the terminal device may determine whether to start the second drx-onduration timer based on the configuration of the network device. Optionally, the network device may indicate to the terminal device whether to start the second drx-onduration timer based on the higher layer configuration signaling. If the higher layer configuration signaling indicates the terminal device to start the drx-onduration timer, the terminal device may start the second drx-onduration timer; if the higher 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 equipment monitors WUS and the WUS indicates that the terminal equipment starts the drx-ondurationTimer, the terminal equipment starts a second drx-ondurationTimer.

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

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

If the second DRX configuration is in the Short DRX cycle, the time for the terminal device to start the second DRX-ondurationTimer needs to satisfy: [ (sfn×1o) +subframe number ] module (drx-ShortCycle) = (drx-StartOffset) module (drx-ShortCycle).

Wherein, module represents the modulo operation, SFN represents the frame number of starting the second DRX-onduration timer, subframe number represents the subframe number of starting the second DRX-onduration timer, DRX-ShortCycle represents the period duration of the Short DRX cycle, and DRX-StartOffset represents the subframe offset of starting the second DRX-onduration timer.

If the second DRX is in the Long DRX cycle, the time for the terminal device to start the second DRX-ondurationTimer can be as follows: [ (sfn×10) +subframe number ] module (DRX-LongCycle) =drx-StartOffset, where DRX-LongCycle represents the period duration of the Long DRX cycle.

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

Mode 2

The terminal device determines not to listen to WUS.

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

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

Mode 3

The terminal device determines whether to monitor WUS according to the configuration of the network device.

In particular, if the network device configures the terminal device to monitor WUS, such as the configuration information is also used to indicate whether the terminal device monitors WUS, the terminal device may determine to monitor WUS; if the network device configures the terminal device not to listen to WUS, the terminal device may determine not to listen to WUS.

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

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

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

Mode 4

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

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

Mode 5

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

It should be understood that although modes 1 to 5 are described above respectively, this does not mean that modes 1 to 5 are independent, and that descriptions of the respective modes may be mutually parametric. For example, the related description in mode 1 regarding whether the terminal device determines to start the second drx-onDurationTimer according to the listening result of WUS may be applied to modes 3-5. For brevity of content, modes 3-5 will not be described in any great detail herein.

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

It should be noted that, since the activation period of the first DRX configuration overlaps with the listening occasion of WUS, the terminal device may determine to start the first DRX-onduration timer.

In the embodiment of the application, in the case that the network device configures a plurality of DRX configurations for one MAC entity of the terminal device, at least part of the DRX configurations may have an activation period overlapping with the monitoring time of WUS, and the rest of the DRX configurations may have an activation period not overlapping with the monitoring time of WUS. Therefore, the terminal device determines whether to monitor the WUS according to the overlapping condition of the activation periods of the plurality of DRX configurations and the monitoring occasions 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 above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application.

For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described further.

As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be regarded as the disclosure of the present application.

It should be understood that, in the various method embodiments of the present application, the sequence number of each process described above does not mean that the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Having described the method of listening to WUS in detail above according to an embodiment of the present application, a communication device according to an embodiment of the present application will be described below with reference to fig. 5 to 7, and 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 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 a plurality of discontinuous reception DRX configurations corresponding to one medium access control MAC entity of the terminal device.

A processing unit 320, configured to determine whether to monitor the WUS according to the overlapping situation of the activation periods of the multiple DRX configurations and the monitoring occasions of the wake-up 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 activation period of the first DRX configuration overlaps with a listening occasion of the WUS and a second DRX configuration of the multiple DRX configurations is not in the activation period, the processing unit 320 is specifically configured to: it is determined to monitor the WUS.

Optionally, in an 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 according to the monitoring result of the WUS.

Optionally, in an embodiment of the present application, the processing unit 320 is specifically configured to: if the WUS is not monitored at its listening occasion, determining whether to start the second DRX duration timer based on a higher layer configuration; if the WUS is monitored, the WUS is used for indicating the terminal equipment to start a DRX continuous timer, and the second DRX continuous timer is determined to be started; and if the WUS is monitored, the WUS is used for indicating the terminal equipment not to start the DRX duration timer, and the second DRX duration timer is determined not to be started.

Optionally, in an embodiment of the present 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 not to start the second DRX duration timer, starting the second DRX duration timer.

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

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

Optionally, in an 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 a terminal device in the method 200, and the corresponding operation of the terminal device in the method 200 may be implemented, which is not described herein 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 4l0, configured to send configuration information to a terminal device, where the configuration information includes a plurality of discontinuous reception DRX configurations corresponding to one medium access control MAC entity of the terminal device, and the configuration information is further configured to indicate whether the terminal device listens for a wake-up signal WUS; wherein a first DRX configuration of the plurality of DRX configurations corresponds to the primary cell PCell or the primary secondary cell PScell, an active period of the first DRX configuration overlaps with a listening occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.

Optionally, in the embodiment of the present application, if the configuration information is used to instruct the terminal device to monitor the wake-up signal WUS, and the terminal device does not monitor the WUS at the monitoring opportunity 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 operation of the network device in the method 200 may be implemented, which is not described herein for brevity.

Fig. 7 is a schematic block 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, from which the processor 510 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 7, the communication device 500 may further comprise a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the method in an embodiment of the application.

Wherein 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 in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, the number of which may be one or more.

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

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

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 may call and run a computer program from a memory to implement the method in an embodiment of the present application.

Optionally, as shown in fig. 8, the apparatus 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the 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 acquire information or data sent by the other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. Wherein 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 other devices or chips.

Optionally, the apparatus may be applied to a terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a network device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

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

It should be appreciated that the processor of an embodiment 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks 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 embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus 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 appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in 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 functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

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

Optionally, the computer readable storage medium may be applied to a terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

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

The embodiment of the application also provides a computer program.

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

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein 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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within 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 listening for a wake-up signal, the method comprising:

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

The terminal equipment determines whether to monitor the WUS according to the overlapping condition of the activation periods of the DRX configurations and the monitoring time of the wake-up signal WUS;

Wherein a first DRX configuration of the multiple DRX configurations corresponds to a primary cell PCell or a primary secondary cell PScell, and when an activation period of the first DRX configuration overlaps with a listening occasion of the WUS and a second DRX configuration of the multiple DRX configurations is not in the activation period, the determining, by the terminal device, whether to listen to the WUS according to an overlapping situation of the activation period of the multiple DRX configurations and the listening occasion of the wake-up signal WUS includes:

the terminal equipment determines to monitor the WUS;

Or alternatively

Wherein a first DRX configuration of the plurality of DRX configurations corresponds to PCell or PScell, and when an active period of the first DRX configuration overlaps with a listening occasion of the WUS and a second DRX configuration of the plurality of DRX configurations is not in the active period, the determining, by the terminal device, whether to listen to the WUS according to an overlapping situation of the active period of the plurality of DRX configurations and the listening occasion of the wake-up signal WUS includes:

The terminal equipment determines not to monitor the WUS; or (b)

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

2. The method according to claim 1, wherein the method further comprises:

And the terminal equipment determines whether a second DRX continuous timer in the second DRX configuration is started or not according to the monitoring result of the WUS.

3. The method according to claim 2, wherein the determining, by the terminal device, whether the second DRX duration timer in the second DRX configuration is started according to the WUS listening result, 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 based on high-layer configuration;

if the terminal equipment monitors the WUS and the WUS is used for indicating the terminal equipment to start a DRX continuous timer, the terminal equipment determines to start the second DRX continuous 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.

4. The method of claim 3, wherein the terminal device determining whether to start the second DRX duration timer based on a higher layer configuration comprises:

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

and if the high-level configuration signaling configures the terminal equipment not to start the second DRX duration timer, the terminal equipment starts the second DRX duration timer.

5. The method of claim 1, 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.

6. The method according to any of claims 1 to 5, wherein the first DRX configuration is in a DRX long cycle or the first DRX configuration is in a DRX short cycle.

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

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

Wherein a first DRX configuration of the plurality of DRX configurations corresponds to the primary cell PCell or the primary secondary cell PScell, an active period of the first DRX configuration overlaps with a listening occasion of the WUS, and a second DRX configuration of the plurality of DRX configurations is not in the active period.

8. The method of claim 7, wherein if the configuration information is used to instruct the terminal device to listen for a wake-up signal WUS, and the terminal device does not listen for the WUS at a listening occasion of the WUS, the method further comprises:

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

The network device indicates to the terminal device whether to start the second DRX duration timer through higher layer configuration signaling.

9. The method according to claim 7 or 8, wherein the first DRX configuration is in a DRX long cycle or the first DRX configuration is in a DRX short cycle.

10. A terminal device, comprising:

A communication unit, configured to receive configuration information sent by a network device, where the configuration information includes a plurality of discontinuous reception DRX configurations corresponding to one medium access control MAC entity of the terminal device;

A processing unit, configured to determine whether to monitor WUS according to the overlapping situation of the activation periods of the DRX configurations and the monitoring occasions of the wake-up signals WUS;

Wherein, a first DRX configuration of the multiple DRX configurations corresponds to a primary cell PCell or a primary secondary cell PScell, and when an activation period of the first DRX configuration overlaps with a listening occasion of the WUS and a second DRX configuration of the multiple DRX configurations is not in the activation period, the processing unit is specifically configured to:

Determining to monitor the WUS;

Or alternatively

Wherein a first DRX configuration of the plurality of DRX configurations corresponds to PCell or PScell, and when an active period of the first DRX configuration overlaps with a listening occasion of the WUS and a second DRX configuration of the plurality of DRX configurations is not in the active period, the processing unit is specifically configured to:

Determining not to monitor the WUS; or (b)

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

11. The terminal device of claim 10, wherein the processing unit is further configured to:

And determining whether a second DRX duration timer in the second DRX configuration is started according to the monitoring result of the WUS.

12. The terminal device according to claim 11, wherein the processing unit is specifically configured to:

If the WUS is not monitored at its listening occasion, determining whether to start the second DRX duration timer based on a higher layer configuration;

If the WUS is monitored, the WUS is used for indicating the terminal equipment to start a DRX continuous timer, and the second DRX continuous timer is determined to be started;

And if the WUS is monitored, the WUS is used for indicating the terminal equipment not to start the DRX duration timer, and the second DRX duration timer is determined not to be started.

13. The terminal device according to claim 12, 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 not to start the second DRX duration timer, starting the second DRX duration timer.

14. The terminal device of claim 10, wherein if the processing unit determines not to monitor the WUS, the processing unit is further configured to:

A DRX duration timer in the plurality of DRX configurations is started.

15. The terminal device according to any of the claims 10 to 14, wherein the first DRX configuration is in a DRX long cycle or the first DRX configuration is in a DRX short cycle.

16. A network device, comprising:

A communication unit, configured to send configuration information to a terminal device, where the configuration information includes a plurality of discontinuous reception DRX configurations corresponding to one medium access control MAC entity of the terminal device, and the configuration information is further configured to indicate whether the terminal device listens for a wake-up signal WUS;

17. The network device of claim 16, wherein if the configuration information is used to instruct the terminal device to listen for a wake-up signal WUS, and the terminal device does not listen for the WUS at a listening occasion 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.

18. The network device of claim 16 or 17, wherein the first DRX configuration is in a DRX long cycle or the first DRX configuration is in a DRX short cycle.

19. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 6.

20. A network device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 7 to 9.

21. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 6.

22. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 7 to 9.

23. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 6.

24. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 7 to 9.

25. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 6.

26. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 7 to 9.