Lower power wake-up signal operation with discontinuous reception configuration

Abstract

Example embodiments of the present disclosure relate to low power wake-up signal (LP-WUS) operation with discontinuous reception (DRX) configuration. In an example method, an apparatus obtains a discontinuous reception (DRX) configuration for the apparatus from a network device. The apparatus monitors a low power wake-up signal (LP-WUS) from the network device during a time period, where at least one of an on duration timer or an inactive timer of the DRX configuration is started based on a point in time at which the LP-WUS is received during the time period. In this manner, a mechanism for an LP-WUS with a DRX configuration may be defined.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to apparatuses, methods, and computer-readable storage media for low-power wake-up signal (LP-WUS) operations with discontinuous reception (DRX) configurations. Background Art

[0002] 5G systems are designed and developed for both mobile phones and vertical use cases. In addition to latency, reliability, and availability, UE energy efficiency is also critical for 5G. Currently, 5G devices may have to be recharged weekly or daily, depending on individual usage times. Typically, 5G devices consume tens of milliwatts in the RRC idle / inactive state and hundreds of milliwatts in the RRC connected state. Designing for extended battery life is necessary for improving energy efficiency and for a better user experience. Summary of the Invention

[0003] Generally, example embodiments of the present disclosure provide solutions for LP-WUS operations with DRX configurations.

[0004] In a first aspect, an apparatus is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: obtain a discontinuous reception (DRX) configuration for the apparatus from a network device; and monitor, during a time period, a low-power wake-up signal (LP-WUS) from the network device, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received during the time period.

[0005] In a second aspect, an apparatus is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: send a discontinuous reception (DRX) configuration for the terminal device to the terminal device; and send first information indicating a time period to the terminal device, the first information configuring the terminal device to: monitor, during the time period, a low-power wake-up signal (LP-WUS) from the apparatus, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received by the terminal device during the time period.

[0006] In a third aspect, a method performed by a terminal device is provided. The method includes: at the terminal device, obtaining a discontinuous reception (DRX) configuration for the terminal device from a network device; and during a time period, the terminal device monitoring a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received during the time period, starting at least one of an on-duration timer or an inactivity timer of the DRX configuration.

[0007] In a fourth aspect, a method performed by a network device is provided. The method includes: the network device sending a discontinuous reception (DRX) configuration for a terminal device to the terminal device; and the network device sending first information indicating a time period to the terminal device, the first information configuring the terminal device to: during the time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, starting at least one of an on-duration timer or an inactivity timer of the DRX configuration.

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes: means for obtaining a discontinuous reception (DRX) configuration for the apparatus from a network device; and means for monitoring a low-power wake-up signal (LP-WUS) from the network device during a time period, wherein based on a time point at which the LP-WUS is received during the time period, starting at least one of an on-duration timer or an inactivity timer of the DRX configuration.

[0009] In a sixth aspect, an apparatus is provided. The apparatus includes: means for sending a discontinuous reception (DRX) configuration for a terminal device to the terminal device; and means for sending first information indicating a time period to the terminal device, the first information configuring the terminal device to: during the time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, starting at least one of an on-duration timer or an inactivity timer of the DRX configuration.

[0010] In a seventh aspect, a non-transitory computer-readable storage medium including instructions is provided. The instructions, when executed by a device, cause the device to at least perform the following: obtain a discontinuous reception (DRX) configuration for the device from a network device; and during a time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received during the time period, starting at least one of an on-duration timer or an inactivity timer of the DRX configuration.

[0011] In an eighth aspect, a non-transitory computer-readable storage medium including instructions is provided. When executed by a device, the instructions cause the device to at least perform the following: send to a terminal device a discontinuous reception (DRX) configuration for the terminal device; and send to the terminal device first information indicating a time period associated with an on-duration of the DRX configuration, the first information configuring the terminal device to, during the time period, monitor for a low-power wake-up signal (LP-WUS) from the device, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received by the terminal device during the time period.

[0012] In a ninth aspect, a computer program including instructions is provided. When executed by a device, the instructions cause the device to at least: obtain from a network device a discontinuous reception (DRX) configuration for the device; and monitor for a low-power wake-up signal (LP-WUS) from the network device during a time period, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received during the time period.

[0013] In a tenth aspect, a computer program including instructions is provided. When executed by a device, the instructions cause the device to at least: send to a terminal device a discontinuous reception (DRX) configuration for the terminal device; and send to the terminal device first information indicating a time period, the first information configuring the terminal device to, during the time period, monitor for a low-power wake-up signal (LP-WUS) from the device, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received by the terminal device during the time period.

[0014] In an eleventh aspect, a device is provided. The device includes: an obtaining circuitry configured to obtain from a network device a discontinuous reception (DRX) configuration for the device; and a monitoring circuitry configured to monitor for a low-power wake-up signal (LP-WUS) from the network device during a time period, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received during the time period.

[0015] In a twelfth aspect, an apparatus is provided. The apparatus includes: a transmitting circuitry configured to send to a terminal device a discontinuous reception (DRX) configuration for the terminal device; and a transmitting circuitry configured to send to the terminal device first information indicating a time period, the first information configuring the terminal device to: during the time period, monitor for a low power wake-up signal (LP-WUS) from the apparatus, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

[0016] It should be understood that the summary is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Some example embodiments will now be described with reference to the drawings, in which:

[0018] Figure 1A An example of a network environment is shown in which some example embodiments of the present disclosure may be implemented;

[0019] Figure 1B A schematic diagram of UE operation with a low power wake-up receiver (WUR) is shown, based on which some example embodiments of the present disclosure may be implemented;

[0020] Figure 2 A flowchart of a communication process according to some example embodiments of the present disclosure is shown;

[0021] Figure 3 A flowchart of an example method implemented at a first device according to some embodiments of the present disclosure is shown;

[0022] Figure 4 Another flowchart of an example method implemented at a second device according to some embodiments of the present disclosure is shown; and

[0023] Figure 5 A simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure is shown; and

[0024] Figure 6 A block diagram of an example of a computer-readable medium according to some example embodiments of the present disclosure is shown.

[0025] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that the description of these embodiments is for illustrative purposes only and helps those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways other than those described below.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0028] References in this disclosure to "one embodiment", "an embodiment", "example embodiment", etc., mean that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that, whether or not explicitly described, the influence of such feature, structure, or characteristic in connection with other embodiments is within the knowledge of those skilled in the art.

[0029] It should be understood that although terms such as "first" and "second" may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the example embodiments, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] The terms used herein are for the purpose of describing particular embodiments and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly dictates otherwise. It will also be understood that the terms "comprises", "comprising", "has", "having", "includes", "including", and / or "containing" when used herein specify the presence of the stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0031] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0032] (a) only hardware circuit implementations (such as implementations only in analog and / or digital circuitry) and

[0033] (b) combinations of hardware circuits and software, such as (where applicable):

[0034] (i) A combination of (one or more) analog and / or digital hardware circuits and software / firmware, and

[0035] (ii) Any portion of (one or more) hardware processors with software (including (one or more) digital signal processors, software, and (one or more) memories, which work together to enable a device, such as a mobile phone or a server, to perform various functions) and

[0036] (c) (One or more) hardware circuits and / or (one or more) processors, such as (one or more) microprocessors or a part of (one or more) microprocessors, which require software (e.g., firmware) to operate, but the software can be absent when not needed.

[0037] This definition of circuitry applies to all uses of this term in this application (including in any claim). As a further example, as used in this application, the term circuitry also encompasses implementations of only hardware circuits or processors (or multiple processors) or a part of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example and if applicable to a particular claim element, the term "circuitry" also encompasses a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0038] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between a terminal device and a network device in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to the fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and / or any other protocol currently known or to be developed in the future. Embodiments of the present disclosure can be applied to various communication systems. Given the rapid development of communication, there will of course also be future types of communication technologies and systems that utilize the present disclosure. The scope of the present disclosure should not be limited to the above systems.

[0039] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from the network. Depending on the terminology and technology applied, the network device may refer to a base station (BS) or an access point (AP), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), relay, low power node (e.g., femto, pico), etc. In the following description, the terms "network device" and "network node" may be used interchangeably.

[0040] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, the terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, mobile phones, cellular phones, smart phones, IP voice (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDA), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback applications, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automation processing chain environment), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0041] For UEs without continuous energy, such as those using small rechargeable and single button cells, energy efficiency is even more critical. The power consumption depends on the configured length of the wake-up period, e.g., the paging cycle. To meet the above battery life requirements, it is desirable to use an eDRX cycle with a large value, resulting in high latency, which is not suitable for services that require both long battery life and low latency. A UE architecture is proposed that uses a wake-up signal to trigger the main radio and an independent receiver with the ability to monitor the wake-up signal with ultra-low power consumption. The main radio operates for data transmission and reception and can be turned off or set to deep sleep unless it is turned on. The power consumption for monitoring the wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver for signal detection and processing.

[0042] The present disclosure is mainly directed to low-power WUS / WUR for power-sensitive, small form factor devices, which include IoT use cases (such as industrial sensors, controllers) and wearable devices. Other use cases are not excluded, for example, XR / smart glasses, smart phones. The present disclosure contemplates the use of a separate low-power wake-up receiver at the UE and evaluates how UE power consumption can be reduced. The goal is that the main radio of the UE can be in a sleep mode (or even powered off) to save power and is only activated when a wake-up signal is received from the network. Basically, the network triggers the UE to wake up exactly in an event-driven manner when needed by sending a specific WUS to the UE, and this specific WUS is monitored by a dedicated LP WUS receiver at the UE. When the UE receives the WUS, the WUS receiver can trigger the wake-up of the normal NR transceiver and can start communication. Thus, the ultra-low-power receiver wakes up the main radio, and otherwise, the main radio is turned off or remains in a deep sleep mode. It is assumed that the low-power wake-up receiver can operate with very low power consumption in an always "on" manner. In fact, by designing a simple (WUS) signal and using dedicated hardware for its monitoring (which can only receive WUS), it is expected to consume significantly less power compared to the NR transceiver.

[0043] The current discussion mainly focuses on DL reception, where LP-WUS can be used to wake up the main radio to receive PDCCH / PDSCH. It is not clear how the UE switches back to the LP-WUS mode. It is also not clear whether LP-WUS works on top of DRX or also works without a DRX configuration. When DRX is configured, the UE monitors the PDCCH during the active time. It is not clear whether and how LP-WUS is monitored during the active time. Therefore, the operation of LP-WUS under a DRX configuration needs to be discussed.

[0044] Example embodiments of the present disclosure relate to how LP-WUS works with DRX. Example embodiments of the present disclosure provide a mechanism to solve the above problems. In some example embodiments of the present disclosure, when the UE is in the LP-WUS mode (i.e., only monitoring LP-WUS), when processing the on-duration / inactivity timer, LP-WUS can be monitored during the configured period, and this period can dynamically start the on-duration / inactivity timer at any point within the configured period. In this way, the operation mechanism for LP-WUS with a DRX configuration can be defined.

[0045] Figure 1AFIG. 0 shows an example of a network environment 100 in which some example embodiments of the present disclosure may be implemented. In the description of the example embodiments of the present disclosure, the network environment 100 may also be referred to as a communication system 100 (e.g., a part of a communication network). For illustrative purposes only, various aspects of the example embodiments will be described in the context of one or more terminal devices and network devices that communicate with each other. However, it should be understood that the description herein may be applied to other types of devices or other similar devices referred to using other terms.

[0046] The network device 110 may provide services to the terminal device 120, and the network device 110 and the terminal device 120 may transmit data and control information to each other. In some embodiments, the network device 110 and the terminal device 120 may communicate using a direct link / channel.

[0047] In the communication system 100, the link from the network device 110 to the terminal device 120 is referred to as a downlink (DL), and the link from the terminal device 120 to the network device 110 is referred to as an uplink (UL). In the downlink, the network device 110 is a transmitting (TX) device (or transmitter), and the terminal device 120 is a receiving (RX) device (or receiver). In the uplink, the terminal device 120 is a transmitting (TX) device (or transmitter), and the network device 110 is an RX device (or receiver). It should be understood that the network device 110 may provide one or more serving cells. As Figure 1A shown, the network device 110 provides one serving cell 102, and the terminal device 120 camps on the serving cell 102. In some embodiments, the network device 110 may provide multiple serving cells. It should be understood that Figure 1A the number of the (multiple) serving cells shown is for illustrative purposes only and does not imply any limitation.

[0048] Communication in the network environment 100 may be implemented according to any suitable (multiple) communication protocols, including but not limited to cellular communication protocols such as the fourth generation (4G) and fifth generation (5G), wireless local area network communication protocols such as those of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols known currently or to be developed in the future. In addition, the communication may utilize any suitable wireless communication technologies, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technologies known currently or to be developed in the future.

[0049] It should be understood that Figure 1AThe number of devices shown and their connection relationships and types are for illustrative purposes only and do not imply any limitations. The communication system 100 may include any suitable number of devices suitable for implementing the embodiments of the present disclosure.

[0050] As described above, the 5G system is designed and developed for both mobile phones and vertical use cases. In addition to latency, reliability, and availability, UE energy efficiency is also critical for 5G. Currently, 5G devices may have to be recharged weekly or daily, depending on individual usage times. Generally, 5G devices consume tens of milliwatts in the RRC idle / inactive state and hundreds of milliwatts in the RRC connected state. Designs for extending battery life are necessary for improving energy efficiency and a better user experience.

[0051] For UEs without continuous energy sources, such as those using small rechargeable and single button cells, energy efficiency is even more critical. In vertical use cases, sensors and actuators are widely deployed for monitoring, measuring, charging, etc. Generally, their batteries are non-rechargeable and are expected to last at least several years, as described in 3GPP TR 38.875. Wearable devices include smartwatches, rings, e-health related devices, and medical monitoring devices. For typical battery capacities, it is challenging to maintain for up to 1 to 2 weeks as needed.

[0052] Power consumption depends on the configured length of the wake-up period, such as the paging cycle. To meet the above battery life requirements, it is desirable to use an extended discontinuous reception (eDRX) cycle with a large value, resulting in high latency, which is not suitable for services with both long battery life and low latency requirements. For example, in the fire detection and extinguishing use case, within 1 to 2 seconds from the time the fire is detected by the sensor, the fireproof panel should be closed and the fire sprinkler should be turned on by the actuator, and a long eDRX cycle cannot meet the delay requirements. eDRX is clearly not suitable for latency-critical use cases. Therefore, the aim is to study an ultra-low power mechanism that can support low latency (e.g., lower than eDRX latency) in Rel-18.

[0053] Currently, the UE needs to wake up periodically every DRX cycle, which dominates power consumption during periods without signaling or data traffic. If the UE can only wake up when it is triggered (e.g., paged), the power consumption can be significantly reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver with the ability to monitor the wake-up signal using ultra-low power. The main radio operates for data transmission and reception and can be turned off or set to deep sleep unless it is turned on. This will be described in more detail with reference to Figure 1B be described in more detail.

[0054] Figure 1BFIG. 0 shows a schematic diagram of the operation of UE 150 having a low-power wake-up receiver (WUR), based on which some example embodiments of the present disclosure may be implemented. Such UE 150 is mainly targeted at low-power WUS / WUR for power-sensitive, small form factor devices, which include IoT use cases (such as industrial sensors, controllers) and wearable devices. Other use cases are not excluded, for example, XR / smart glasses, smart phones. As Figure 1B shown, UE 150 includes a main radio 170 and a separate receiver, namely an ultra-low-power wake-up receiver 160.

[0055] The main radio 170 of UE 150 may be in a sleep mode (or even powered off) to save power, and is only activated when a wake-up signal is received from the network (e.g., from a network device). Basically, the network triggers UE 150 to wake up exactly in an event-driven manner when needed by sending a specific WUS to UE 150, and this specific WUS is monitored by a dedicated low-power WUS receiver 160 at UE 150. When UE 150 receives the WUS, the WUS receiver 160 may trigger the wake-up of a normal NR transceiver (which is included in the main radio 170), and may start communication. Thus, the ultra-low-power wake-up receiver 160 wakes up the main radio 170, and otherwise, the main radio 170 is turned off or remains in a deep sleep mode, as Figure 1B shown.

[0056] Strictly speaking, the power consumption for monitoring the wake-up signal depends on the wake-up signal design and the hardware modules of the wake-up receiver for signal detection and processing. However, it is assumed that the low-power wake-up receiver 160 can operate in an always "on" manner with very low power consumption. In fact, by designing a simple (WUS) signal and using dedicated hardware for its monitoring (which is only capable of receiving WUS), it is expected to consume significantly less power compared to the NR transceiver.

[0057] Figure 2 FIG. 14 shows a flowchart of a communication process 200 according to some example embodiments of the present disclosure. For the purpose of discussion, the communication process 200 will be described with reference to Figures 1A to 1B The communication process 200 will be described. It should be understood that although the communication process 200 has been described with reference to Figure 1A the network environment 100, this communication process 200 can equally be applied to other similar communication scenarios.

[0058] During communication procedure 200, network device 110 sends (205) a DRX configuration 202 for terminal device 120 to terminal device 120. Accordingly, terminal device 120 can receive (210) the DRX configuration 202. In some embodiments, the DRX configuration 202 may include DRX configuration parameters such as, but not limited to, drx-onDurationTimer, drx-InactivityTimer, drx-ShortCycleTimer, longDRX-CycleStartOffset, drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-ShortCycle, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, etc. In explicit signaling-based DRX adaptation, terminal device 120 is assumed to have a DRX configuration adapted by explicit signaling sent by network device 110. The explicit signaling for adapting the DRX configuration sent by network device 110 may be performed by RRC (such as an RRC message), MAC (such as a MAC CE), or PHY (such as DCI).

[0059] In some embodiments, network device 110 may send (215) first information 204 indicating a time period to terminal device 120. Accordingly, terminal device 120 can receive (220) the DRX configuration 204. The first information 204 may configure terminal device 120 to monitor LP-WUS from network device 110 during the time period. In some embodiments, based on the time point at which LP-WUS is received by terminal device 120 during the time period, the on-duration timer of the DRX configuration may be started. Alternatively or additionally, based on the time point at which LP-WUS is received by terminal device 120 during the time period, the inactivity timer of the DRX configuration may be started. The on-duration timer and the inactivity timer may be indicated by the parameters drx-onDurationTimer and drx-InactivityTimer in the DRX configuration 202, respectively. In an alternative embodiment, terminal device 120 may be pre-configured or implicitly indicated with the time period to monitor LP-WUS from network device 110 during the time period.

[0060] The terminal device 120 monitors (225) LP-WUS from the network device 110 during this time period. For example, the terminal device 120 may perform LP-WUS monitoring based on the first information 204 or pre-configuration or implicit indication during this time period. In some embodiments, based on the time point at which LP-WUS is received during this time period, the on-duration timer of the DRX configuration may be started. Alternatively or additionally, based on the time point at which LP-WUS is received during this time period, the inactivity timer of the DRX configuration may be started. In alternative embodiments, the timer may not be started, but LP-WUS may only be monitored at this time period. In this way, the mechanism for monitoring LP-WUS under the DRX configuration can be defined.

[0061] In some embodiments, this time period may be associated with the on-duration of the DRX configuration. For example, the on-duration of the DRX configuration may be based on the time that the drx-onDurationTimer is running. Alternatively, for example, in the case where the inactivity timer can be directly started, there may be no on-duration at all.

[0062] In some embodiments, at the time point based on receiving LP-WUS from the network device 110, the on-duration timer may be started or restarted. For example, after receiving LP-WUS from the network device 110 and before the on-duration timer expires, the main radio in the terminal device 120 may be turned on to monitor the PDCCH from the network device 110. When the on-duration timer expires, the main radio in the terminal device 120 may be turned off or set to deep sleep. In some embodiments, this time point may be within this time period. Alternatively, there may be a delay after LP-WUS reception, and the start of the on-duration timer may not fall within the time period for LP-WUS monitoring.

[0063] In some embodiments, when receiving LP-WUS for wake-up monitoring PDCCH from the network device 110, the on-duration timer may run only for the remaining time period of the on-duration after receiving LP-WUS from the network device 110. For example, the time period for LP-WUS monitoring may be considered as part of the on-duration. In an example, the on-duration may be the time period from t1 to t3, and the terminal device 120 may receive LP-WUS from the network device 110 at the moment t2 between t1 and t3. Therefore, during the time period from t2 to t3, the main radio in the terminal device 120 may be turned on to monitor the PDCCH from the network device 110. At the end of the on-duration, that is, at the moment t3, the on-duration timer may expire, and the main radio in the terminal device 120 may be turned off or set to deep sleep.

[0064] In some embodiments, the on-duration timer may run for a period of the on-duration value regardless of at which time point the LP-WUS is received. For example, the period for LP-WUS monitoring may be considered not to be part of the on-duration. The starting point of the on-duration timer may be dynamically triggered by the received LP-WUS, and the on-duration timer may run for a period of the on-duration value regardless of at which point the LP-WUS is received. In an example, the on-duration may be a time period from t1 to t3 = t1 + Δt1, and the terminal device 120 may receive the LP-WUS from the network device 110 at a moment t2 between t1 and t3. The on-duration timer may be started at the moment t2 and expire at the moment t4 = t2 + Δt2, and Δt2 may be equal to or may not be equal to Δt1. Thus, during the time period from t2 to t4, the primary radio in the terminal device 120 may be turned on to monitor the PDCCH from the network device 110. When the on-duration timer expires at the moment t4, the primary radio in the terminal device 120 may be turned off or set to deep sleep.

[0065] In some embodiments, the LP-WUS may not be configured or may not be monitored outside the on-duration. For example, both the primary radio and the LP-WUS receiver of the terminal device 120 may be turned off or set to deep sleep during the "OFF time" of the on-duration mode.

[0066] In some embodiments, the time period may be the on-duration of the DRX configuration. For example, the on-duration may be mainly used for the period of LP-WUS decoding. In an example, the LP-WUS receiver of the terminal device 120 may be turned on during the on-duration. In some embodiments, the terminal device 120 may start an inactivity timer when receiving the LP-WUS. In an example, when the LP-WUS is received during the on-duration, the inactivity timer may be started, and the primary radio of the terminal device 120 may monitor the PDCCH before the inactivity timer expires.

[0067] In some embodiments, when receiving the LP-WUS, the terminal device 120 may wake up to monitor the PDCCH until receiving a UL grant or a DL allocation from the network device 110, and start an inactivity timer based on receiving the UL grant or the DL allocation. For example, when receiving the LP-WUS, the primary radio of the terminal device 120 may start to monitor the PDCCH. When the primary radio receives the first PDCCH, the inactivity timer may be started, and the primary radio may keep monitoring the PDCCH before the inactivity timer expires.

[0068] According to the above embodiments, the terminal device 120 can be configured to monitor the LP-WUS, and when the LP-WUS is received, it can be switched to monitoring the PDCCH. When switched to monitoring the PDCCH, the terminal device 120 can determine whether to continue monitoring the PDCCH in the normal DRX configuration or switch back to monitoring the LP-WUS in various ways.

[0069] In some embodiments, when the timer associated with the monitoring of the PDCCH expires, the terminal device 120 can switch from monitoring the PDCCH to monitoring the LP-WUS. For example, before the timer expires, the terminal device 120 can operate with the normal DRX configuration for a period of time (which can be more than one DRX cycle). In other words, when switched to monitoring the PDCCH, the terminal device 120 can continue to monitor the PDCCH with the normal DRX configuration for a period of time, during which the main radio of the terminal device 120 can be turned on and off as in the normal DRX configuration. When the terminal device 120 is monitoring the PDCCH or when the timer is running, there is no need to send the LP-WUS to wake up the PDCCH monitoring for each on-duration. The timer for switching back to monitoring the LP-WUS can be implemented in various ways (e.g., similar to the short DRX cycle timer).

[0070] In some embodiments, after the terminal device 120 starts using the long DRX cycle, the timer for switching back to monitoring the LP-WUS can be started. In other words, when switched to monitoring the PDCCH, the terminal device 120 can continue to monitor the PDCCH with the normal DRX configuration. When the long DRX cycle is started, the terminal device 120 can start the timer for switching back to monitoring the LP-WUS.

[0071] In alternative embodiments, the timer can be started or restarted after PDCCH reception. Alternatively or additionally, the timer can be started or restarted after an uplink transmission. For example, whenever the terminal device 120 performs PDCCH reception or uplink transmission, the timer can be started or restarted. In this way, if the timer expires, it means that no UL / DL transmission has occurred during the period when the timer is running, and the terminal device 120 can then switch to monitoring the LP-WUS. The value of the timer can be configured by the network device 110. Alternatively, the value of the timer can be a default value.

[0072] In some embodiments, based on determining that long DRX is to be started or receiving a long DRX command media access control (MAC) control element (CE) from network device 110, terminal device 120 may switch to monitoring LP-WUS. For example, a timer or command for starting a long DRX cycle may be reused to start the LP-WUS mode. In other words, terminal device 120 does not experience a long DRX cycle and may switch back to monitoring LP-WUS before the long DRX cycle starts.

[0073] In some embodiments, LP-WUS may be associated with each on-duration for each DRX cycle in a DRX configuration. In other words, it is always required that LP-WUS trigger PDCCH monitoring during each on-duration of each DRX cycle. In some embodiments, terminal device 120 may monitor LP-WUS during each on-duration of each DRX cycle. If terminal device 120 does not receive LP-WUS during the on-duration, terminal device 120 will not monitor the PDCCH.

[0074] In some embodiments, based on determining that the active time has ended, terminal device 120 may switch from monitoring the PDCCH to monitoring LP-WUS. In other words, after the active time ends, terminal device 120 may automatically return to the LP-WUS mode. In the next cycle, if PDCCH transmission is required, network device 110 will need to send another LP-WUS to wake up PDCCH monitoring on the primary radio of terminal device 120.

[0075] In some embodiments, network device 110 may provide an LP-WUS configuration to terminal device 120. The LP-WUS configuration may include a time period associated with the on-duration of the DRX configuration and other required information for LP-WUS, such as when the UE should monitor LP-WUS, i.e., the LP-WUS monitoring occasion. For example, terminal device 120 may receive first information 204 from network device 110 indicating the time period. Alternatively or additionally, terminal device 120 may receive second information from network device 110 regarding a timer associated with the monitoring of the PDCCH. Alternatively or additionally, terminal device 120 may receive third information from network device 110 that configures terminal device 120 to switch to monitoring LP-WUS when long DRX is to be started or when a long DRX command MAC CE is received from network device 110. Alternatively or additionally, terminal device 120 may receive fourth information from network device 110 that configures terminal device 120 to switch from monitoring the PDCCH to monitoring LP-WUS when the active time ends. Terminal device 120 may monitor LP-WUS based on the received information.

[0076] Through processing flow 200, a mechanism for LP-WUS with DRX configuration can be defined.

[0077] Figure 3 A flowchart of an example method 300 implemented at the terminal device 120 according to some other embodiments of the present disclosure is shown. For purposes of discussion, method 300 will be described Figures 1A to 2 from the perspective of the terminal device 120.

[0078] At block 310, the terminal device 120 obtains a DRX configuration for the terminal device 120 from the network device 110. At block 320, the terminal device 120 monitors LP-WUS from the network device 110 during a period of time. In some embodiments, based on the time point at which LP-WUS is received during this period, an on-duration timer of the DRX configuration is started. Alternatively or additionally, based on the time point at which LP-WUS is received during this period, an inactivity timer of the DRX configuration is started.

[0079] In some embodiments, the on-duration timer may be started or restarted at the time point based on receiving LP-WUS from the network device 110. In some embodiments, when receiving LP-WUS of the wake-up monitoring physical downlink control channel (PDCCH) from the network device 110, the on-duration timer may run only for the remaining period of the on-duration after receiving LP-WUS from the network device 110. In some embodiments, the on-duration timer may run for a period of the on-duration value regardless of the time point at which LP-WUS is received.

[0080] In some embodiments, LP-WUS may not be configured or may not be monitored outside the on-duration. In some embodiments, this period of time may be the on-duration of the DRX configuration. In some embodiments, the terminal device 120 may start an inactivity timer when receiving LP-WUS.

[0081] In some embodiments, when receiving LP-WUS, the terminal device 120 may wake up to monitor the PDCCH until receiving a UL grant or a DL assignment from the network device 110. Based on receiving the UL grant or the DL assignment, the terminal device 120 may start an inactivity timer.

[0082] In some embodiments, when a timer associated with the monitoring of PDCCH expires, the terminal device 120 may switch from monitoring PDCCH to monitoring LP-WUS. In some embodiments, the timer may be started after the terminal device 120 starts using a long DRX cycle. In some embodiments, the timer may be started or restarted after receiving PDCCH. Alternatively or additionally, the timer may be started or restarted after an uplink transmission.

[0083] In some embodiments, based on determining to start long DRX or receiving a long DRX command media access control (MAC) control element (CE) from the network device 110, the terminal device 120 may switch to monitoring LP-WUS. In some embodiments, LP-WUS may be associated with each on-duration for each DRX cycle in a DRX configuration. In some embodiments, based on determining that the active time ends, the terminal device 120 may switch from monitoring PDCCH to monitoring LP-WUS.

[0084] In some embodiments, the terminal device 120 may receive first information 204 from the network device 110 indicating the time period. Alternatively or additionally, the terminal device 120 may receive second information from the network device 110 regarding a timer associated with the monitoring of PDCCH. Alternatively or additionally, the terminal device 120 may receive third information from the network device 110 that configures the terminal device 120 to switch to monitoring LP-WUS when long DRX is to be started or when a long DRX command MAC CE is received from the network device 110. Alternatively or additionally, the terminal device 120 may receive fourth information from the network device 110 that configures the terminal device 120 to switch from monitoring PDCCH to monitoring LP-WUS when the active time ends.

[0085] Figure 4 Another flowchart of an example method 400 implemented at the network device 110 according to some other embodiments of the present disclosure is shown. For purposes of discussion, method 400 will be described with reference to Figures 1A to 2 the perspective of the network device 110.

[0086] At block 410, the network device 110 sends a DRX configuration for the terminal device 120 to the terminal device 120. At block 420, the network device 110 sends first information indicating a time period to the terminal device 120. The first information configures the terminal device 120 to monitor LP-WUS from the network device 110 during the time period. In some embodiments, based on the time point at which the LP-WUS is received by the terminal device 120 during the time period, the on-duration timer of the DRX configuration is started. Alternatively or additionally, based on the time point at which the LP-WUS is received by the terminal device 120 during the time period, the inactivity timer of the DRX configuration is started.

[0087] In some embodiments, the first information may configure the terminal device 120 to start or restart the on-duration timer at the time point based on receiving the LP-WUS from the network device 110. In some embodiments, the first information may configure the terminal device 120 to run the on-duration timer only for the remaining time period of the on-duration after the terminal device 120 receives the LP-WUS from the network device 110

[0088] In some embodiments, the first information may configure the terminal device 120 to run the on-duration timer for a period of the on-duration value, regardless of the time point at which the terminal device 120 receives the LP-WUS. In some embodiments, the LP-WUS may not be configured or may not be sent outside the duration.

[0089] In some embodiments, the time period may be the on-duration of the DRX configuration. In some embodiments, the first information may configure the terminal device 120 to start the inactivity timer when the terminal device 120 receives the LP-WUS.

[0090] In some embodiments, the first information may configure the terminal device 120 to start the inactivity timer when the terminal device 120 receives a UL grant or a DL allocation after receiving the LP-WUS during the on-duration.

[0091] In some embodiments, the network device 110 may send second information about a timer associated with the monitoring of the PDCCH to the terminal device 120. The second information may configure the terminal device 120 to switch from monitoring the PDCCH to monitoring the LP-WUS when the timer expires. In some embodiments, the second information may configure the terminal device 120 to start the timer after the terminal device 120 starts using a long DRX cycle. In some embodiments, the second information may configure the terminal device 120 to start or restart the timer after the terminal device 120 receives a PDCCH. Alternatively or additionally, the second information may configure the terminal device 120 to start or restart the timer after an uplink transmission of the terminal device 120.

[0092] In some embodiments, the network device 110 may send third information to the terminal device 120, and the third information configures the terminal device 120 to switch to monitoring the LP-WUS when it is to start long DRX or when it receives a long DRX command media access control (MAC) control element (CE) from the network device 110. In some embodiments, the LP-WUS may be associated with each on-duration for each DRX cycle in the DRX configuration. In some embodiments, the network device 110 may send fourth information to the terminal device 120, and the fourth information configures the terminal device 120 to switch from monitoring the PDCCH to monitoring the LP-WUS when the active time ends.

[0093] In some embodiments, a device (e.g., the terminal device 120) capable of performing method 300 may include components for performing the corresponding steps of method 300. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

[0094] In some example embodiments, the device includes: a component for obtaining a discontinuous reception (DRX) configuration for the device from a network device; and a component for monitoring a low power wake-up signal (LP-WUS) from the network device during a time period. In some example embodiments, based on the time point when the LP-WUS is received during the time period, an on-duration timer of the DRX configuration is started. Alternatively or additionally, based on the time point when the LP-WUS is received during the time period, an inactivity timer of the DRX configuration is started.

[0095] In some embodiments, based on the time point when the LP-WUS is received from the network device 110, the on-duration timer may be started or restarted.

[0096] In some embodiments, when receiving a LP-WUS for waking up to monitor the Physical Downlink Control Channel (PDCCH) from the network device 110, the on-duration timer may run only for the remaining period of the on-duration after receiving the LP-WUS from the network device 110.

[0097] In some embodiments, the on-duration timer may run for a period of the on-duration value regardless of at which time point the LP-WUS is received. In some embodiments, the LP-WUS may not be configured or may not be monitored outside the on-duration. In some embodiments, this period may be the on-duration of the DRX configuration.

[0098] In some embodiments, the apparatus may further include components for starting an inactivity timer when receiving the LP-WUS. In some embodiments, the apparatus may further include components for waking up to monitor the PDCCH when receiving the LP-WUS until a UL grant or a DL assignment is received from the network device 110; and components for starting an inactivity timer based on receiving the UL grant or the DL assignment.

[0099] In some embodiments, the apparatus may further include components for switching from monitoring the PDCCH to monitoring the LP-WUS when a timer associated with the monitoring of the PDCCH expires. In some embodiments, the timer may be started after the terminal device starts using a long DRX cycle. In some embodiments, the timer may be started or restarted after receiving the PDCCH. Alternatively or additionally, the timer may be started or restarted after an uplink transmission.

[0100] In some embodiments, the apparatus may further include components for switching to monitoring the LP-WUS based on determining to start long DRX or receiving a long DRX command Media Access Control (MAC) control element (CE) from the network device 110.

[0101] In some embodiments, the LP-WUS may be associated with each on-duration for each DRX cycle in the DRX configuration. In some embodiments, the apparatus may further include components for switching from monitoring the PDCCH to monitoring the LP-WUS based on determining that the active time ends.

[0102] In some embodiments, the apparatus may further include components for receiving, from the network device 110, first information 204 indicating the time period. Alternatively or additionally, the apparatus may further include components for receiving, from the network device 110, second information regarding a timer associated with the monitoring of the PDCCH. Alternatively or additionally, the apparatus may further include components for receiving, from the network device 110, third information that configures the terminal device 120 to switch to monitoring LP-WUS when long DRX is to be started or when a long DRX command MAC CE is received from the network device 110. Alternatively or additionally, the apparatus may further include components for receiving, from the network device 110, fourth information that configures the terminal device 120 to switch from monitoring the PDCCH to monitoring LP-WUS at the end of the active time.

[0103] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 300. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the apparatus to perform in conjunction with the at least one processor.

[0104] In some embodiments, an apparatus (e.g., network device 110) capable of performing method 400 may include components for performing the corresponding steps of method 400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0105] In some example embodiments, the apparatus includes: components for sending, to the terminal device, a discontinuous reception (DRX) configuration for the terminal device; and components for sending, to the terminal device, first information indicating a time period, the first information configuring the terminal device to monitor a low power wake-up signal (LP-WUS) from the network device during the time period. In some embodiments, based on the time point at which the LP-WUS is received by the terminal device during the time period, an on-duration timer of the DRX configuration is started. Alternatively or additionally, based on the time point at which the LP-WUS is received by the terminal device during the time period, an inactivity timer of the DRX configuration is started.

[0106] In some embodiments, the first information may configure the terminal device to start or restart an on-duration timer at a time point based on receiving the LP-WUS from the network device.

[0107] In some embodiments, the first information may configure the terminal device to run the on-duration timer only for the remaining time period of the on-duration after the terminal device receives the LP-WUS from the network device.

[0108] In some embodiments, the first information may configure the terminal device to run an on-duration timer for a period of the on-duration value, regardless of at which time point the terminal device receives the LP-WUS.

[0109] In some embodiments, the LP-WUS may not be configured or may not be sent outside the on-duration. In some embodiments, this time period may be the on-duration configured for DRX. In some embodiments, the first information may configure the terminal device to start an inactivity timer when the terminal device receives the LP-WUS.

[0110] In some embodiments, the first information may configure the terminal device to start an inactivity timer when the terminal device receives a UL grant or a DL allocation after receiving the LP-WUS within the on-duration.

[0111] In some embodiments, the apparatus may further include a component for sending second information to the terminal device regarding a timer associated with the monitoring of the PDCCH. The second information may configure the terminal device to switch from monitoring the PDCCH to monitoring the LP-WUS when the timer expires. In some embodiments, the second information may configure the terminal device to start the timer after the terminal device starts using a long DRX cycle. In some embodiments, the second information may configure the terminal device to start or restart the timer after the terminal device receives the PDCCH. Alternatively or additionally, the second information may configure the terminal device to start or restart the timer after the terminal device's uplink transmission.

[0112] In some embodiments, the apparatus may further include a component for sending third information to the terminal device, and the third information configures the terminal device to switch to monitoring the LP-WUS when it is to start long DRX or when receiving a long DRX command media access control (MAC) control element (CE) from the network device.

[0113] In some embodiments, the LP-WUS may be associated with each on-duration for each DRX cycle in the DRX configuration. In some embodiments, the apparatus may further include a component for sending fourth information to the terminal device, and the fourth information configures the terminal device to switch from monitoring the PDCCH to monitoring the LP-WUS at the end of the active time.

[0114] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 400. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform.

[0115] Figure 5 FIG. 4 shows a simplified block diagram of a device 500 suitable for implementing some example embodiments of the present disclosure. The device 500 may be provided to implement a communication device, for example, such as Figure 1A shown network device 110 or terminal device 120. As shown, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more communication modules 540 coupled to the processor 510.

[0116] The communication module 540 is for two-way communication. The communication module 540 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0117] The processor 510 may be of any type suitable for a local technical network and, by way of non-limiting example, may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 500 may have multiple processors, such as an application specific integrated circuit chip that is subordinate in time to a clock synchronized with the main processor.

[0118] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that do not persist during a power outage.

[0119] The computer program 530 includes computer-executable instructions executed by the associated processor 510. The program 530 may be stored in the ROM 524. The processor 510 may execute any suitable actions and processes by loading the program 530 into the RAM 522.

[0120] Embodiments of the present disclosure may be implemented by the program 530, which causes the device 500 to perform as referred to Figure 2Any process of the present disclosure described above. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0121] In some example embodiments, the program 530 may be tangibly embodied in a computer-readable medium, which may be included in the device 500 (such as in the memory 520) or in other storage devices accessible by the device 500. The device 500 may load the program 530 from the computer-readable medium into the RAM 522 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0122] Figure 6 A block diagram of an example of a computer-readable medium 1000 according to some example embodiments of the present disclosure is shown. The computer-readable medium 600 has the program 530 stored thereon. Note that although the computer-readable medium 600 is depicted in the form of a CD or DVD in Figure 6 the computer-readable medium 600 may be any other form suitable for carrying or storing the program 530.

[0123] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, a microprocessor, or other computing devices. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers, or other computing devices, or some combination thereof.

[0124] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the methods 300 or 400 described above with reference to Figure 3 or Figure 4 Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules may be combined or split among program modules as needed. The machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0125] The program code for performing the methods of the present disclosure can be written in any combination of one or more programming languages. This program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the program code is executed by the processor or controller, the specific functions / operations in the flowcharts and / or block diagrams are implemented. The program code can execute entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0126] In the context of the present disclosure, the computer program code or related data can be carried by any suitable carrier so that the device, apparatus, or processor can perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0127] The computer-readable media can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0128] Furthermore, although the operations are described in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be construed as limiting the scope of the present disclosure, but rather as describing particular features of a particular embodiment. Certain features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0129] Although the present disclosure has been described in language specific to structural features and / or method acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the above specific features and acts are disclosed as example forms of implementing the claims.

[0130] List of Abbreviations

[0131] LP-WUS Low Power Wakeup Signal

[0132] MAC Media Access Control

[0133] DRX Discontinuous Reception

[0134] TAT Time Alignment Timer

[0135] WUR Wakeup Receiver

[0136] eDRX Extended Discontinuous Reception

[0137] IoT Internet of Things

[0138] PDCCH Physical Downlink Control Channel

[0139] PDSCH Physical Downlink Shared Channel

[0140] DCI Downlink Control Information

[0141] RRC Radio Resource Control

Claims

1. A device, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least: obtain a discontinuous reception (DRX) configuration for the device from a network device; and monitor a low power wake-up signal (LP-WUS) from the network device during a time period, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received during the time period.

2. The device according to claim 1, wherein the time period is associated with an on-duration of the DRX configuration.

3. The device according to claim 1 or 2, wherein the on-duration timer is started or restarted at a time point based on receiving the LP-WUS from the network device.

4. The device according to any one of claims 1 to 3, wherein when receiving the LP-WUS for waking up to monitor a physical downlink control channel (PDCCH) from the network device, the on-duration timer runs only for a remaining time period of the on-duration after receiving the LP-WUS from the network device.

5. The device according to any one of claims 1 to 3, wherein the on-duration timer runs for a period of an on-duration value regardless of at which time point the LP-WUS is received.

6. The device according to any one of claims 1 to 5, wherein the LP-WUS is not configured or not monitored outside the on-duration.

7. The device according to any one of claims 1 to 6, wherein the time period is the on-duration of the DRX configuration.

8. The device according to claim 7, wherein the device is further caused to: start the inactivity timer when receiving the LP-WUS.

9. The device according to any one of claims 1 to 7, wherein the device is further caused to: wake up to monitor the PDCCH when receiving the LP-WUS until receiving a UL grant or a DL allocation from the network node; and start the inactivity timer based on receiving the UL grant or the DL allocation.

10. The device according to claim 1, wherein the device is further caused to: switch from monitoring the PDCCH to monitoring the LP-WUS when a timer associated with the monitoring of the PDCCH expires.

11. The device according to claim 10, wherein the timer is started after the device starts using a long DRX cycle.

12. The device according to claim 10, wherein the timer is started or restarted after at least one of PDCCH reception or uplink transmission.

13. The device according to any one of claims 1 to 12, wherein the device is further caused to: Based on determining that long DRX is to be started or receiving a long DRX command media access control (MAC) control element (CE) from the network device, switch to monitoring the LP-WUS.

14. The apparatus according to any one of claims 1 to 13, wherein the LP-WUS is associated with each on-duration for each DRX cycle in the DRX configuration.

15. The apparatus according to any one of claims 1 to 14, wherein the apparatus is further caused to: Based on determining that the active time has ended, switch from monitoring the PDCCH to monitoring the LP-WUS.

16. The apparatus according to any one of claims 1 to 15, wherein the apparatus is further caused to receive at least one of the following from the network device: First information indicating the time period; Second information regarding a timer associated with the monitoring of the PDCCH; Third information that configures the apparatus to: when long DRX is to be started or a long DRX command MAC CE is received from the network device, switch to monitoring the LP-WUS; or Fourth information that configures the apparatus to: when the active time ends, switch from monitoring the PDCCH to monitoring the LP-WUS.

17. An apparatus, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: send a discontinuous reception (DRX) configuration for the terminal device to the terminal device; and send first information indicating a time period to the terminal device, the first information configuring the terminal device to: during the time period, monitor a low power wake-up signal (LP-WUS) from the apparatus, wherein based on the time point at which the LP-WUS is received by the terminal device during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

18. The apparatus according to claim 17, wherein the time period is associated with the on-duration of the DRX configuration.

19. The apparatus according to claim 17 or 18, wherein the first information configures the terminal device to: at the time point based on receiving the LP-WUS from the apparatus, start or restart the on-duration timer.

20. The apparatus according to any one of claims 17 to 19, wherein the first information configures the terminal device to: run the on-duration timer only for the remaining time period of the on-duration after the terminal device receives the LP-WUS from the apparatus.

21. The apparatus according to any one of claims 17 to 19, wherein the first information configures the terminal device to: run the on-duration timer for a period of on-duration values, regardless of at which time point the LP-WUS is received by the terminal device.

22. The apparatus according to any one of claims 17 to 21, wherein the LP-WUS is not configured or not sent outside the on-duration.

23. The apparatus according to any one of claims 17 to 22, wherein the time period is the on-duration of the DRX configuration.

24. The apparatus according to claim 23, wherein the first information configures the terminal device to: start the inactivity timer when the LP-WUS is received by the terminal device.

25. The apparatus according to any one of claims 17 to 23, wherein the first information configures the terminal device to: start the inactivity timer when the UL grant or the DL allocation is received by the terminal device after the LP-WUS is received by the terminal device during the on-duration.

26. The apparatus according to claim 17, wherein the apparatus is further caused to: send second information about a timer associated with the monitoring of the PDCCH to the terminal device, the second information configuring the terminal device to: when the timer expires, switch from monitoring the PDCCH to monitoring the LP-WUS.

27. The apparatus according to claim 26, wherein the second information configures the terminal device to: start the timer after the terminal device starts using a long DRX cycle.

28. The apparatus according to claim 26, wherein the second information configures the terminal to: start or restart the timer after at least one of the PDCCH reception or the uplink transmission of the terminal device.

29. The apparatus according to any one of claims 17 to 28, wherein the apparatus is further caused to: send third information to the terminal device, the third information configuring the terminal device to: when long DRX is to be started or when a long DRX command media access control (MAC) control element (CE) is received from the apparatus, switch to monitoring the LP-WUS.

30. The apparatus according to any one of claims 17 to 29, wherein the LP-WUS is associated with each on-duration of each DRX cycle in the DRX configuration.

31. The apparatus according to any one of claims 17 to 30, wherein the apparatus is further caused to: send fourth information to the terminal device, the fourth information configuring the terminal device to: when the active time ends, switch from monitoring the PDCCH to monitoring the LP-WUS.

32. A method, comprising: at a terminal device, obtaining a discontinuous reception (DRX) configuration for the terminal device from a network device; and during a time period, the terminal device monitoring a low power wake-up signal (LP-WUS) from the network device, wherein at least one of an on-duration timer or an inactivity timer of the DRX configuration is started based on a time point at which the LP-WUS is received during the time period.

33. A method, comprising: Sending, via a network device, a discontinuous reception (DRX) configuration for the terminal device; and Sending, via the network device, first information indicating a time period to the terminal device, the first information configuring the terminal device to: during the time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

34. An apparatus, comprising: means for obtaining, from a network device, a discontinuous reception (DRX) configuration for the terminal device; and means for monitoring, during a time period, a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

35. An apparatus, comprising: means for sending, to a terminal device, a discontinuous reception (DRX) configuration for the terminal device; and means for sending, to the terminal device, first information indicating a time period, the first information configuring the terminal device to: during the time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

36. A non-transitory computer-readable medium, comprising program instructions that, when executed by a device, cause the device to at least perform the following: Obtain, from a network device, a discontinuous reception (DRX) configuration for the device; and During a time period, monitor a low-power wake-up signal (LP-WUS) from the network device, wherein based on a time point at which the LP-WUS is received during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

37. A non-transitory computer-readable medium, comprising program instructions that, when executed by a device, cause the device to at least perform the following: Send, to a terminal device, a discontinuous reception (DRX) configuration for the terminal device; and Send, to the terminal device, first information indicating a time period associated with an on-duration of the DRX configuration, the first information configuring the terminal device to: during the time period, monitor a low-power wake-up signal (LP-WUS) from the device, wherein based on a time point at which the LP-WUS is received by the terminal device during the time period, at least one of an on-duration timer or an inactivity timer of the DRX configuration is started.

Images