Monitoring for pdcch after receiving wake-up signal

Abstract

A method (1200) performed by a user equipment, UE, having a discontinuous reception on- duration timer, drx-onDurationTimer, is provided. The method comprises receiving (1210) a wake-up signal, WUS, from a network node, and based on receiving the WUS, monitoring (1220) for a physical downlink control channel, PDCCH, using a different timer than the drx-onDurationTimer. A corresponding UE, a corresponding method performed by a network node, and a corresponding network node are also provided.

Description

[0001]MONITORING FOR PDCCH AFTER RECEIVING WAKE-UP SIGNAL TECHNICAL FIELD The present disclosure generally relates to wireless communication, and more particularly to monitoring for a Physical Downlink Control Channel (PDCCH) after receiving a wake-up signal (WUS). BACKGROUND A common way for a user equipment (UE) to save energy is to use duty cycled operation where the UE wakes up periodically from a power saving mode to monitor for incoming transmissions such as a physical downlink control channel (PDCCH). Figure 1 illustrates an example of such an energy saving method called discontinuous reception (DRX). The UE uses a discontinuous reception on-duration timer (drx-onDurationTimer) to keep track of how long to stay active and monitor for PDCCH. The UE goes back to sleep mode when the drx- onDurationTimer expires. But if a PDCCH is received during the DRX on-duration, the UE uses a discontinuous reception inactivity timer (drx-InactivityTimer) to remain active longer. The UE starts / restarts the drx-InactivityTimer each time a PDCCH is received, and the UE continues monitoring for PDCCH until the drx-InactivityTimer expires. A wake-up receiver (WUR), sometimes also referred to as a ‘wake-up radio’, may be used at user equipment (UE) for saving energy. A WUR may be a low power receiver in a UE, which, in case of the detection of a wake-up signal (WUS), wakes up the main (baseband / RF / less power efficient) receiver (sometimes also referred to as a ‘main radio’) of the UE to detect an incoming message. The incoming message typically relates to paging. For example, a Physical Downlink Control Channel (PDCCH) may be received in a paging occasion (PO) and may schedule a paging message on a Physical Downlink Shared Channel (PDSCH)). A benefit of employing a WUR is lowering energy consumption and prolonging device battery life, or that at a fixed energy consumption the downlink latency can be reduced (shorter Discontinuous Reception (DRX) / duty- cycles and more frequent checks for incoming transmissions). Figure 2 illustrates a location of a WUS and the paging occasion (PO) to which it is associated. In general, there are two approaches for detecting WUS: • Using the main receiver: o No need for additional dedicated hardware / receiver for monitoring WUS. o Coverage of the main receiver is not typically impacted. o Limited power saving gain as the main receiver monitors WUS. • Using a dedicated receiver (WUR): o Extremely low power, simple and low-cost receiver architecture, relaxed requirements, noisier (i.e., less accurate) clock or oscillator. o Significant power saving gain can be achieved by maximizing the time in which the main receiver can be in the sleep mode. o Enablers for zero energy / battery-less devices, and energy harvesting operations. o There are coverage considerations given the tradeoff between WUR power consumption and sensitivity. As an example, Figure 3 illustrates a dedicated wake up receiver (WUR) being used for monitoring a wake-up signal (WUS). Once the WUR detects the intended WUS, it wakes up the main receiver (which may be a baseband / RF / less power efficient receiver) to detect further incoming messages. Therefore, the main receiver can go to sleep mode and save power until it is triggered by the WUR. Here, the WUR is an ultra-low power and low-complexity receiver which can support simple modulation schemes such as on off keying (OOK), frequency shift keying (FSK), or pulse shape keying (PSK). However, the WUS is transmitted using an OFDM-based transmitter. In release 15 (Rel-15) of the third generation partnership project (3GPP), WUS was specified for Narrowband-Internet of Things (NB-IoT) and Long Term Evolution-Machine Type Communication (LTE-M). The main motivation was UE energy consumption reduction since with the coverage enhancement PDCCH could be repeated many times and the WUS is relatively much shorter and hence requires less reception time for the UE. The logic is that a UE would check for a WUS a certain time before its PO, and only if a WUS is detected the UE would continue to check for PDCCH in the PO. If a WUS is not detected, which is most of the time, the UE can go back to a sleep state to conserve energy. Due to the coverage enhancements the WUS can be of variable length depending on the UE’s coverage. Figure 4 illustrates WUS for NB-IoT and LTE-M. A ‘Wake-up signal’ (WUS) may be based on the transmission of a short signal that indicates to the UE that it should continue to decode the downlink (DL) control channel such as, for example, full Narrowband-PDCCH (NPDCCH) for NB-IoT. If such a signal is absent (DTX (i.e., the UE does not detect it)), then the UE can go back to sleep without decoding the DL control channel. The decoding time for a WUS is considerably shorter than that the decoding time of the full NPDCCH since it essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces UE power consumption and leads to longer UE battery life. The WUS would be transmitted only when there is a paging for the UE. But if there is no paging for the UE, then the WUS will not be transmitted (i.e., implying a discontinuous transmission, DTX) and the UE would go back to deep sleep, e.g., upon detecting DTX instead of WUS. This is illustrated in Figure 2, where blocks with thin edges indicate possible WUS and PO positions whereas the boxes with thick edges (the two blocks in the middle) indicate actual WUS and PO positions. The specification of Rel-15 WUS is spread out over several parts of the LTE 36-series standard, e.g., 36.211, 36.213, 36.304 and 36.331. In the Rel-16, it was agreed that WUS should be further developed to also include UE grouping, such that the number of UEs that are triggered by a WUS is further narrowed down to a smaller subset of the UEs that are associated with a specific paging occasion (PO). The purpose of UE grouping is to reduce the false paging rate, i.e. avoid that a given UE is unnecessarily woken up by a WUS transmission intended for another UE. This feature is referred to as Rel-16 group WUS, or GWUS. However, this is not directly related to WUR and will not further be explained hereafter. In Rel-17, discussions started on introducing a WUS for new radio (NR), then called ‘Paging Early Indication’ (PEI). However, since at the time no coverage enhancement was specified for NR, the only gain for Rel-17 PEI was for scenarios where the small fraction of UEs are in bad coverage and with large synchronization error due to the use of longer discontinuous reception (DRX) cycles. The gain for such UEs were that with the use of PEI they would typically only have to acquire one synchronization signal block (SSB) before decoding PEI, instead of up to 3 SSBs if PEI is not used (value according to UE vendors). So, for most UEs, Rel-17 PEI will result in gains or increased performance. Rel-17 PEI will also support UE grouping for false paging reduction, similar to the Rel-16 GWUS above, which will have some gains at higher paging load. In RAN#93e it was agreed that PEI will be PDCCH-based. As shown below, this makes it much less interesting for WUR (i.e. the main baseband receiver is required for decoding PEI). In Rel-18, there has been rather large interest to introduce WUR for NR, with an ambition for achieving more significant energy efficiency improvement compared to solutions already specified in earlier releases. As explained above, the only specification support needed to be able to use a WUR in the UE, is the specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO to allow the UE to start up the main receiver. Therefore, the main difference to Rel-17 PEI is that the WUS in Rel-18 should not be PDCCH-based, and should allow for a simpler and low power receiver, i.e., a WUR with simple modulation and detection techniques (e.g., using on-off keying (OOK) modulation and non-coherent detection). In Rel-18, a study item on “low-power wake-up signal and receiver for NR” was approved. A benefit of WUR is to reduce the energy consumption of the receiver, such that unless there is any paging and data for the UE it can remain in a power saving state. This will extent the battery life of the device, or alternatively enable shorter downlink latency (shorter DRX) at a fixed battery life. For short-range communication, the WUR power can be low enough (~10 uW) that this can even, in combination with energy harvesting, enable that the WUR is continuously on (i.e. DRX or duty-cycling is not used) without the need for a battery. This can be considered as a key enabler of battery-less devices towards 6G. The Rel-18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical report is provided in 3GPP TR 38.869, V0.4.0, “Study on low-power Wake-up Signal and Receiver for NR”. Subsequently, there will be Rel-19 Work Item to specify the various design aspects of WUS / WUR. IEEE 802.11 standardized the support for WUR in the task group (TG) ba. Similar to the 3GPP solution, the use of a WUR is only enabled in stations and not in access points (APs), that is for downlink communication only. The AP advertises that it has WUR operation capability, along with WUR configuration parameters (among other info, in which band / channel WUR is operational, which can be different from the band / channel used for data transmission using the main receiver, e.g. WUR in 2.4 GHz band but data communication in 5 GHz band. Also note that the WUR operating channel is advertised in the beacon, and that the WUR discovery operating channel may be different from the WUR operating channel.). Stations can then request to be configured with WUR mode of operation. This request has to be granted by the AP, and in case it is granted, the station is further configured / setup for WUR mode of operation (the configuration is only valid for the connection to the associated AP, and further the configuration must be torn down / de-configured if the WUR is not used anymore). Both continuous WUR (receiver open all the time) and duty-cycled WUR (receiver only open during preconfigured time slots) mode of operations are supported. For the latter the length of the duty-cycles and on- time during wake up is part of the WUR configuration. The physical WUS in IEEE contains complete frames which must be processed by the station. The drawback with this design is that it requires more handling and processing in the station, i.e. compared to a simple WUR design which trigger one pre-defined activity in case WUS is detected. The benefit is that it contains more information and the solution is more general. The IEEE WUS contains information to indicate if the WUS is a WUR sync beacon, a WUR discovery beacon, or a regular WUS (intended to wake the station up). The WUS can also contain proprietary frames, which could e.g. be used to directly turn actuators on / off. The transmission uses on / off keying (OOK) modulation, using Manchester coding, but is using multi-carrier OOK which can be generated by an OFDM transmitter (i.e., the WUR can be enabled as a software upgrade in APs). In general, that a main receiver (MR) of a UE is falsely active may be caused by false alarms and false wake-up as defined below: • False alarm: A physical PHY) layer effect of the WUS incorrectly being received when there is none (single UE effect). • False wake-up: A higher layer (HL) effect of a WUS to one UE unnecessarily waking up other UEs sharing the same WUS resource (multi-UE effect). The WUR may have specific sensitivity, detection, and false alarm performance. Depending on the design of the WUR, it may perform reception / detection in specific time intervals (e.g., every ^^^^ ms). Figure 5 illustrates possible outcomes of some example WUS detection cases. Specifically, Figure 5 illustrates: 1) A WUS is correctly detected, 2) A WUS is present but not detected (miss detection), 3) A WUS is not present but the WUR declares that the WUS is detected (false alarm), and 4) A WUS is not present and the WUR does not detect it (correct rejection). In addition to false alarm, false wake-up can happen when multiple UEs belong to the same WUS group a WUS intended for one UE unnecessarily wakes up other UEs sharing the same WUS resource / group (multi-UE effect). Such MR falsely active events result in additional UE power consumption, thus decreasing the potential gain of using a WUR. There currently exist certain challenge(s), however. For example, in WUR operation, the power saving performance is highly susceptible to false alarm and / or wake-up events that are caused by false detection of noise / interference or WUS intended for other UEs being paged in the same WUS group. After being falsely woken-up, a UE may perform all the procedures as usual, which consumes a considerable amount of energy. In particular, since a UE (or its main radio) consumes a considerable amount of energy for ramping up / down, false wake up events can result in additional UE power consumption. Therefore, the potential energy saving gain of using a WUR may be reduced or even become a negative gain. In principle, a false alarm can happen for every WUR trial during a WUR ON duration. Therefore, the number of false alarms increases by the WUR activity duration, or in general the larger the number of WUS decoding attempts per time unit. This can be especially problematic in case of always-on WUR operation or when the WUR ON duration is long. SUMMARY A first aspect provides embodiments of a method performed by a user equipment (UE). The UE has a discontinuous reception on-duration timer (drx-onDurationTimer). The method comprises receiving a wake-up signal (WUS) from a network node, and, based on receiving the WUS, monitoring for a physical downlink control channel (PDCCH) using a different timer than the drx-onDurationTimer. Corresponding embodiments of a UE are also provided. A second aspect provides embodiments of a method performed by a network node for communicating with a first user equipment (UE). The first UE has a discontinuous reception on- duration timer (drx-onDurationTimer). The method comprises transmitting a wake-up signal (WUS) and, after transmitting the WUS, transmitting a physical downlink control channel (PDCCH) within a duration of a different timer than the drx-onDurationTimer. Corresponding embodiments of a network node are also provided. BRIEF DESCRIPTION OF THE DRAWINGS Example embodiments will be described below with reference to the accompanying drawings, on which: Figure 1 illustrates an example of discontinuous reception (DRX); Figure 2 shows example locations of a WUS and the respective paging occasions to which they are associated; Figure 3 shows a wireless device (such as a UE) having a dedicated wake-up receiver accompanying a main receiver; Figure 4 shows a WUS for NB-IoT and LTE-M; Figure 5 shows different WUS detection cases; Figure 6 shows an example where, upon the main receiver being woken up by a WUS or a false alarm, the WUR is in sleep mode causing missed WUS reception; Figure 7 shows an example where, upon the main radio being woken up by a WUS, the gNB sends PDCCH instead of a WUS during a WUR sleep period; Figure 8 shows an example where the WUR keeps monitoring during the DRX onDuration and as long as the UE is in RRC connected mode; Figure 9 shows adaptation of a WUR operation mode after triggering of the main receiver; Figure 10 shows an example where the UE sends feedback after the main receiver is woken up by the WUR; Figure 11 illustrates use of a WUR-onDurationTimer; Figure 12 is a flow chart of a method performed by a UE, according to some embodiments; Figure 13 is a flow chart of a method performed by a network node, according to some embodiments; Figure 14 is a flow chart of a method performed by a UE, according to some embodiments; Figure 15 is a flow chart of a method performed by a network node, according to some embodiments; Figure 16 illustrates a communication system which enables connectivity between UEs, network nodes, and a host; Figure 17 illustrates a UE according to some embodiments; Figure 18 illustrates a network node according to some embodiments; Figure 19 illustrates a host according to some embodiments; Figure 20 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and Figure 21 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION As described above, UEs (or main radios of UEs) may be woken up unnecessarily for various reasons, which may be referred to as false alarm and / or wake-up events. It would be desirable to provide ways for handling the falsely woken-up UEs to reduce the energy consumption. Otherwise, for example in radio resource control (RRC) CONNECTED mode, the main radio of a falsely woken-up UE may stay active for the whole drx-onDuration and / or inactivity timer, which could waste energy. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are disclosed that provide for multiple WUR operation options in radio resource control (RRC) Connected mode. By operating with different options, the UE can reduce the risk of missing information from the gNB and / or detect false wake- up occurrences to at least some extent. For example, according to certain embodiments, three WUR operation options are provided for the UE in RRC Connected mode. Furthermore, according to certain embodiments, systems and methods are provided enabling UEs to deal with a false wake-up. By that, the UEs could reduce the impact of false wake- up on the power saving gain of WUR operation in RRC connected mode. Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of avoiding UEs missing information from gNBs which may be important for proper UE-network operation and reachability. As another example, certain embodiments may provide a technical advantage of increasing gNB awareness of false wake-up and mis-detection events which is beneficial for efficient operations. As another example, certain embodiments may provide a technical advantage of reducing the impact of false wake-up on power saving gain when employing a WUR. As yet another example, certain embodiments may provide a technical advantage of providing solutions that are useful for battery-less (zero-energy) devices, Ambient internet of things (IoT), and energy harvesting operations in 5G-Advanced and 6G. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. As used herein, a ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E- SMLC), etc. Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc. In some embodiments, generic terminology, “radio network node” or simply “network node (NW node)”, is used. It can be any kind of network node which may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc. The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs. The term signal or radio signal used herein can be any physical signal or physical channel. Examples of DL physical signals are reference signal (RS) such as PSS, SSS, CSI-RS, DMRS signals in SS / PBCH block (SSB), discovery reference signal (DRS), CRS, PRS etc. RS may be periodic e.g. RS occasion carrying one or more RSs may occur with certain periodicity e.g.20 ms, 40 ms etc. The RS may also be aperiodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols. One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity e.g.5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset wrt reference time (e.g. serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. Examples of UL physical signals are reference signal such as SRS, DMRS etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPUCCH, sPDSCH, sPUCCH, sPUSCH, MPDCCH, NPDCCH, NPDSCH, E-PDCCH, PUSCH, PUCCH, NPUSCH, etc. The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle etc. According to certain embodiments, a dedicated wake up radio (WUR) is used for monitoring a wake-up signal (WUS). Once the dedicated WUR detects the intended WUS, it wakes up the main (baseband / RF / less power efficient) receiver (MR) to detect further incoming messages. Therefore, the MR can stay in sleep mode and save power until it is triggered by WUR. In particular embodiments, while in RRC connected mode, the dedicated WUR may perform discontinuous monitoring where the WUR wakes up periodically to monitor WUS, or continuous monitoring where the WUR keeps monitoring WUS actively, depending on configuration or implementation. The embodiments described herein are applicable to both types of WUS monitoring methods, but discontinuous monitoring is used for illustration in the following sections. WUR Operation Option 1 In a particular embodiment, the WUR is supposed to go into a sleep mode (i.e., not actively detecting WUS) after waking up the MR either correctly or falsely, as shown in Figure 6. In such operation, when a WUS wakes up the MR to start monitoring for PDCCH (and the associated PDSCH), WUS monitoring will stop when the MR is active, and if there is any actual WUS transmitted to the UE during this time it will be missed, which leads to performance degradation (not just for UE power). Figure 5 illustrates such a scenario where upon a MR being woken up by WUS or false alarm, the WUR in sleep mode misses WUS reception. According to a particular embodiment, however, after sending a WUS to wake up the UE, either intended or unintended (a WUS intended for other UEs in the same group, i.e., false wake- up), the gNB will send a PDCCH instead of a WUS during the WUR sleep period, as illustrated in Figure 7. Specifically, the gNB will send the PDCCH directly to the UE if there is further data arrival during WUR sleep period. The WUR sleep period for a UE can be hard-coded in specifications or configured by a gNB through, e.g., system information or dedicated RRC signaling. Note that a false alarm cannot be handled as the gNB is not aware of false alarm occurrence. In a related particular embodiment, after sending a WUS to wake up the UE, either intended or unintended, the gNB may not be able to transmit another WUS to the UE during the UE WUR sleep period. From a UE perspective, after detecting a WUS, the UE may skip monitoring for WUS during a certain duration such as a UE WUR sleep period. In a related particular embodiment, the WUR sleep period could be fixed to certain length, which may be (or should be) equal or shorter than the MR onDuration. Or the WUR sleep period could be dynamically indicated (e.g., using downlink control information (DCI) or a medium access control (MAC) control element (CE)) or configured while the MR is active and able to receive information from the gNB. In a particular embodiment (which could be up to network implementation), to avoid not being able to reach the UE in case of WUS false alarm, the gNB transmits a second WUS to the UE if there has not been a response within a time corresponding to the drx-onDurationTimer (plus processing delays) from the first WUS transmission. It is noted that, in RRC Connected, the gNB knows that the UE is located in the cell and that there should be a response. WUR Operation Option 2 In option 1 and the embodiments described above, it is possible to deal with intended indications and false wake-up cases, but it may not be possible to handle false alarm because the gNB is not aware of false alarm occurrence. In another particular embodiment, which is described as an Option 2, the dedicated WUR keeps monitoring WUS after waking up the MR. Figure 8 illustrates the example scenario where the WUR keeps monitoring during a DRX onDuration for as long as the UE is in RRC CONNECTED mode. In this case, the gNB can always send a WUS to the UE when data arrives since the WUR actively monitors WUS as long as the UE is in RRC connected mode. According to another particular embodiment, once the WUR detects a WUS while the MR is active, it triggers an extension of the inactivity timer to keep the MR in the active state longer. For example, in a particular embodiment, the UE inactivity timer is restarted at the time a WUS is received or extended by a fixed amount. In case the MR was started due to WUS false alarm or false wake-up, this would get the UE back in to proper operation (without this part the UE would apply a too short drx-onDurationTimer from a gNB point of view). In a particular embodiment, collision handling between the WUR and the MR while the drx-onDurationTimer is running is defined to ensure proper operation of the UE. To ensure neither legacy behavior nor performance is changed, the UE always prioritizes MR, in a particular embodiment. However, if a WUS is received, the UE behavior may be to treat this as a correct WUS and restart the drx-onDurationTimer as described with regard to the previous embodiment. If PDCCH-skip command is received at the same time as a WUS, the UE should, however, prioritize the MR and terminate the DRX onDuration and let the MR go to a sleep state. In another particular embodiment, after the WUR triggers the main receiver, the WUR continues monitoring WUS with a different operation mode / configuration. For example, the WUR operates in an always-on manner and, after detecting a WUS (correctly or due to false alarm), the WUR switches its operation mode to the duty-cycled mode, e.g., for the duration of the drx- onDurationTimer. Specifically, when the main receiver is active but not yet determined if the UE is being addressed, the WUR continues monitoring WUS in a duty-cycled manner. Figure 9 illustrates adaptation of WUR operation mode after triggering the MR, according to certain embodiments. This provides flexibility for WUR power saving while having the possibility of network reachability. The configuration of the WUR duty cycle can depend on false alarm rate, main receiver sleep state and transition time, and latency requirements. This method can address the tradeoff between WUR power consumption and paging mis-detection. Hence, it can provide design flexibility and can be beneficial for UE implementation. In the example shown in Figure 9, the main radio and the duty cycling of the WUR are triggered by a false alarm denoted in Figure 9 by ‘FA’. WUR Operation Option 3 In another particular embodiment, a WUS feedback mechanism is designed where an acknowledgment (ACK) indication is sent by the UE to the gNB after a WUS is received by the WUR. Figure 10 illustrates a UE sending feedback after a MR is woken up by the WUR, according to certain embodiments. By receiving an ACK from a UE that the gNB does not send a WUS to, the gNB will be aware of the occurrence of a false alarm. Upon detection of the WUS, the UE would start the main receiver and transmit the WUS ACK in uplink. The WUS ACK could be any of the following: • A scheduling request (SR) transmission on the UE’s configured PUCCH resources. • A new indication on the UE’s configured PUCCH resources. • A random access using an allocated preamble for the purpose. • A new MAC control element containing the WUS ACK. • RRC signaling of WUS ACK. After sending the feedback to the gNB, the UE could, according to pre-configuration, either let the WUR go into sleep mode for a fixed or dynamically configured period as in option 1 above or let the WUR keep monitoring WUS as in option 2 above. Note that the WUS feedback can also be a discontinuous transmission (DTX) which indicates that WUS mis-detection happens. In this case, the gNB can re-send the WUS to the UE in the following WUS monitoring occasion. False Wake-up Impact Reduction In the current Rel-18 study item (SI) phase, there is no discussion on what happens after UE falsely wakes-up. If a UE is falsely woken-up from time to time and starts monitoring PDCCH during onDuration, the UE power saving gain will be significantly reduced. In a particular embodiment, in both option 1 and 2 discussed above, if the UE wakes up and does not detect any intended PDCCH in the first k (k=1, 2, 3…) monitoring occasions, the MR will go back to a sleep mode and not need to stay monitoring for the whole onDuration. That is, the WUS transmission is always paired with a PDCCH transmission, and if the latter is not received by the UE, the UE will assume it was a WUS false alarm or false wake-up and go back to a sleep state. This could be achieved in practice by combining WUR with Rel-16 Downlink Control Information of Power Saving (DCP), i.e., if the UE detects WUS it continues to monitor PDCCH according to DCP (DCI format 2_6) before the DRX onDuration and will only continue to monitor PDCCH during the onDuration if the DCP PDCCH is detected. The value k is configured to the UE. The value of k can depend on several factors such as UE battery level, PDCCH duration / configuration, and UE bandwidth. For example, as the power consumption for each PDCCH monitoring increases for longer PDCCH duration and larger bandwidth, a smaller value of k should be selected. Also, when the UE battery level is below a certain threshold, a smaller value of k is adopted to conserve the energy. In an alternative particular embodiment of the above, the UE will upon WUS reception start monitoring PDCCH during a time WUR-onDurationTimer, which is different (shorter) than the legacy drx-onDurationTimer. Use of a WUR-onDurationTimer that is shorter than the legacy drx-onDurationTimer illustrated in Figure 11. If PDCCH is detected, the UE would as in legacy operation start the drx-InactivityTimer. In another particular embodiment, in option 3, when the gNB receives an ACK from the UE and realizes the occurrence of false wake-up, it could send information to the unintended UEs and let them sleep again. False Alarm / Wake-up UE Reporting To be able to correctly configure a WUR, it would be beneficial if the network could obtain some statistics on the false alarm and false wake-up from UEs. For example, in a particular embodiment, if the false wake-up rate is too high, the network could configure more WUS UE subgroups containing fewer UEs. In general, it would cause too high control signaling overhead to report such false alarms and false wake-ups on every occurrence (since it may involve multiple UEs and there is no data transmission to or from these UEs), and it is therefore preferable that the UEs gather statistics which are later reported to the network upon later data communication to the network. Note that this embodiment is applicable both to radio resource control (RRC) Idle / Inactive and RRC Connected. The collected UE report could be for example be reported to the network in any of the following formats: • A medium access control (MAC) control element. • A RRC message or information element • An addition to UE Assistance Information • An extension of the self-organizing network (SON) reporting In one example (the third bullet in the list above), the WUS false alarm and false wake-up reporting is introduced as UE Assistance Information in 3GPP technical specification (TS) 38.331 V17.0.0 (additions in bold, underline, italics): UEAssistanceInformation message -- ASN1START -- TAG-UEASSISTANCEINFORMATION-START UEAssistanceInformation ::= SEQUENCE { criticalExtensions CHOICE { ueAssistanceInformation UEAssistanceInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } UEAssistanceInformation-IEs ::= SEQUENCE { delayBudgetReport DelayBudgetReport OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEAssistanceInformation- v1540-IEs OPTIONAL } DelayBudgetReport::= CHOICE { type1 ENUMERATED { msMinus1280, msMinus640, msMinus320, msMinus160,msMinus80, msMinus60, msMinus40, msMinus20, ms0, ms20,ms40, ms60, ms80, ms160, ms320, ms640, ms1280}, ... } UEAssistanceInformation-v1540-IEs ::= SEQUENCE { overheatingAssistance OverheatingAssistance OPTIONAL, nonCriticalExtension UEAssistanceInformation- v1610-IEs OPTIONAL } OverheatingAssistance ::= SEQUENCE { reducedMaxCCs ReducedMaxCCs-r16 OPTIONAL, reducedMaxBW-FR1 ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxBW-FR2 ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxMIMO-LayersFR1 SEQUENCE { reducedMIMO-LayersFR1-DL MIMO-LayersDL, reducedMIMO-LayersFR1-UL MIMO-LayersUL } OPTIONAL, reducedMaxMIMO-LayersFR2 SEQUENCE { reducedMIMO-LayersFR2-DL MIMO-LayersDL, reducedMIMO-LayersFR2-UL MIMO-LayersUL } OPTIONAL } OverheatingAssistance-r17 ::= SEQUENCE { reducedMaxBW-FR2-2-r17 SEQUENCE { reducedBW-FR2-2-DL-r17 ReducedAggregatedBandwidth-r17, reducedBW-FR2-2-UL-r17 ReducedAggregatedBandwidth-r17 } OPTIONAL, reducedMaxMIMO-LayersFR2-2 SEQUENCE { reducedMIMO-LayersFR2-2-DL MIMO-LayersDL, reducedMIMO-LayersFR2-2-UL MIMO-LayersUL } OPTIONAL } ReducedAggregatedBandwidth ::= ENUMERATED {mhz0, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} ReducedAggregatedBandwidth-r17 ::= ENUMERATED {mhz0, mhz100, mhz200, mhz400, mhz800, mhz1200, mhz1600, mhz2000} UEAssistanceInformation-v1610-IEs ::= SEQUENCE { idc-Assistance-r16 IDC-Assistance-r16 OPTIONAL, drx-Preference-r16 DRX-Preference-r16 OPTIONAL, maxBW-Preference-r16 MaxBW-Preference-r16 OPTIONAL, maxCC-Preference-r16 MaxCC-Preference-r16 OPTIONAL, maxMIMO-LayerPreference-r16 MaxMIMO-LayerPreference- r16 OPTIONAL, minSchedulingOffsetPreference-r16 MinSchedulingOffsetPreference-r16 OPTIONAL, releasePreference-r16 ReleasePreference-r16 OPTIONAL, sl-UE-AssistanceInformationNR-r16 SL-UE- AssistanceInformationNR-r16 OPTIONAL, referenceTimeInfoPreference-r16 BOOLEAN OPTIONAL, nonCriticalExtension UEAssistanceInformation- v1700-IEs OPTIONAL } UEAssistanceInformation-v1700-IEs ::= SEQUENCE { ul-GapFR2-Preference-r17 UL-GapFR2-Preference- r17 OPTIONAL, musim-Assistance-r17 MUSIM-Assistance-r17 OPTIONAL, overheatingAssistance-r17 OverheatingAssistance- r17 OPTIONAL, maxBW-PreferenceFR2-2-r17 MaxBW-PreferenceFR2-2- r17 OPTIONAL, maxMIMO-LayerPreferenceFR2-2-r17 MaxMIMO- LayerPreferenceFR2-2-r17 OPTIONAL, minSchedulingOffsetPreferenceExt-r17 MinSchedulingOffsetPreferenceExt-r17 OPTIONAL, rlm-MeasRelaxationState-r17 BOOLEAN OPTIONAL, bfd-MeasRelaxationState-r17 BIT STRING (SIZE (1..maxNrofServingCells)) OPTIONAL, nonSDT-DataIndication-r17 SEQUENCE { resumeCause-r17 ResumeCause OPTIONAL } OPTIONAL, scg-DeactivationPreference-r17 ENUMERATED { scgDeactivationPreferred, noPreference } OPTIONAL, uplinkData-r17 ENUMERATED { true } OPTIONAL, rrm-MeasRelaxationFulfilment-r17 BOOLEAN OPTIONAL, propagationDelayDifference-r17 PropagationDelayDifference-r17 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } UEAssistanceInformation-v19xy-IEs ::= SEQUENCE wur-Assistance-r19 WUR-Assistance-r18 OPTIONAL } IDC-Assistance-r16 ::= SEQUENCE { affectedCarrierFreqList-r16 AffectedCarrierFreqList-r16 OPTIONAL, affectedCarrierFreqCombList-r16 AffectedCarrierFreqCombList-r16 OPTIONAL, ... } < Text omitted > WUR-Assistance-r18 ::= SEQUENCE { falseAlarmReporting-r19 ENUMERATED { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100, spare3, spare2, spare1 } OPTIONAL, ... } < Text omitted > -- TAG-UEASSISTANCEINFORMATION-STOP -- ASN1STOP In another example (the fourth bullet in the list above), the WUS false alarm and false wake-up reporting is introduced as SON-parameters (additions in bold, underline, and italics) in 3GPP technical specification (TS) 38.331 V17.0.0: SON-Parameters information element -- ASN1START -- TAG-SON-PARAMETERS-START SON-Parameters-r16 ::= SEQUENCE { rach-Report-r16 ENUMERATED {supported} OPTIONAL, ..., [[ rlfReportCHO-r17 ENUMERATED {supported} OPTIONAL, rlfReportDAPS-r17 ENUMERATED {supported} OPTIONAL, success-HO-Report-r17 ENUMERATED {supported} OPTIONAL, twoStepRACH-Report-r17 ENUMERATED {supported} OPTIONAL, pscell-MHI-Report-r17 ENUMERATED {supported} OPTIONAL, onDemandSI-Report-r17 ENUMERATED {supported} OPTIONAL ]], [[ WUR-Report-r19 ENUMERATED {supported} OPTIONAL ]] } -- TAG-SON-PARAMETERS-STOP -- ASN1STOP Methods according to some example embodiments In view of the embodiments described above, a first aspect provides embodiments of a method 1200 performed by a UE as illustrated by the flow chart in Figure 12. The UE has a discontinuous reception on-duration timer (drx-onDurationTimer) and / or is adapted to use the drx- onDurationTimer. The UE may for example be configured / adapted to use the drx- onDurationTimer for DRX as described in the background section in connection with Fig.1. The method 1200 comprises receiving 1210 a wake-up signal (WUS) from a network node, and, based on receiving the WUS, monitoring 1220 for a physical downlink control channel (PDCCH) using a different timer than the drx-onDurationTimer. The different timer may for example have a different (for example shorter) duration than the drx-onDurationTimer. After the UE receives the WUS, the UE may for example monitor for the PDCCH during a shorter time than a duration of the drx-onDurationTimer. The different timer may for example be referred to as a WUR-onDurationTimer. According to some embodiments, the WUS is received by a wake-up receiver (WUR). A main receiver may for example wake up to perform the monitoring for the PDCCH, and the main receiver may for example go to a sleep mode before the whole duration of the drx- onDurationTimer has passed unless the PDCCH is detected. The UE may for example comprise the WUR and / or the main receiver. According to some embodiment, the method 1200 comprises starting 1240 a discontinuous reception inactivity timer (drx-InactivityTimer) if the PDCCH is detected. The method 1200 may for example comprise detecting 1230 the PDCCH. In view of the embodiments described above, a second aspect provides a method 1300 performed by a network node, as illustrated by the claim chart in Figure 13. The method 1300 is for the network node to communicate with a first user equipment (UE) having a discontinuous reception on-duration timer (drx-onDurationTimer). The method 1300 comprises transmitting 1310 a wake-up signal (WUS), and, after transmitting the WUS, transmitting 1320 a physical downlink control channel (PDCCH) within a duration of a different timer than the drx- onDurationTimer. The different timer may for example have a different (for example shorter) duration than the drx-onDurationTimer. The different timer may for example be referred to as a WUR-onDurationTimer. The methods described above with reference to Figures 12 and 13 involve a timer other than the drx-onDurationTimer. But embodiments are also envisaged where focus is on other aspects, and where these timers are optional. Examples are illustrated in Figures 14 and 15. Figure 14 illustrates an example method 1400 by a UE for WUR operation in connected mode, according to certain embodiments. In the illustrated embodiment, the method 1400 includes at least one of a receiving step at 1410, a waking up step at 1420, and a performing step at 1430. For example, at step 1410, the UE may receive, by a WUR of the UE, a wakeup signal (WUS) from a network node. At step 1420, for example, the UE may, based on receiving the WUS, wake up a main receiver (MR) of the UE. At step 1430, for example, the UE may, after waking up the MR, perform at least one of: (option 1) transitioning the WUR to a sleep mode for a WUR sleep period; (option 2) continuing to monitor, by the WUR, for at least one additional WUS; and (option 3) transmitting, to the network node, an indication that the WUS was received by the UE. Figure 15 illustrates an example method 1500 by a network node for enabling WUR operation in a UE, according to certain embodiments. In the illustrated embodiment, the method 1500 includes at least one of a configuring step at 1510 and a transmitting step at 1520. For example, at step 1510, the network node may configure the UE to, based on receiving a WUS by a WUR of the UE, perform at least one of: waking up a main receiver (MR) of the UE; (option 1) transitioning the WUR to a sleep mode for a WUR sleep period; (option 2) continuing to monitor, by the WUR, for at least one additional WUS; and (option 3) transmitting, to the network node, an indication that the WUS was received by the UE. As another example, at step 1520, the network node may transmit, to the UE, the WUS for reception by the WUR. Further description FIGURE 16 shows an example of a communication system 1600 in accordance with some embodiments. In the example, the communication system 1600 includes a telecommunication network 1602 that includes an access network 1604, such as a radio access network (RAN), and a core network 1606, which includes one or more core network nodes 1608. The access network 1604 includes one or more access network nodes, such as network nodes 1610a and 1610b (one or more of which may be generally referred to as network nodes 1610), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1612a, 1612b, 1612c, and 1612d (one or more of which may be generally referred to as UEs 1612) to the core network 1606 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 1612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1610 and other communication devices. Similarly, the network nodes 1610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1612 and / or with other network nodes or equipment in the telecommunication network 1602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1602. In the depicted example, the core network 1606 connects the network nodes 1610 to one or more hosts, such as host 1616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1606 includes one more core network nodes (e.g., core network node 1608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host 1616 may be under the ownership or control of a service provider other than an operator or provider of the access network 1604 and / or the telecommunication network 1602, and may be operated by the service provider or on behalf of the service provider. The host 1616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system 1600 of FIGURE 16 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 1602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1602. For example, the telecommunications network 1602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs. In some examples, the UEs 1612 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1604. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). In the example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE 1612c and / or 1612d) and network nodes (e.g., network node 1610b). In some examples, the hub 1614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1614 may be a broadband router enabling access to the core network 1606 for the UEs. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1610, or by executable code, script, process, or other instructions in the hub 1614. As another example, the hub 1614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. The hub 1614 may have a constant / persistent or intermittent connection to the network node 1610b. The hub 1614 may also allow for a different communication scheme and / or schedule between the hub 1614 and UEs (e.g., UE 1612c and / or 1612d), and between the hub 1614 and the core network 1606. In other examples, the hub 1614 is connected to the core network 1606 and / or one or more UEs via a wired connection. Moreover, the hub 1614 may be configured to connect to an M2M service provider over the access network 1604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1610 while still connected via the hub 1614 via a wired or wireless connection. In some embodiments, the hub 1614 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1610b. In other embodiments, the hub 1614 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels. FIGURE 17 shows a UE 1700, which may be an embodiment of the UE 1612 of FIGURE 16, in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input / output interface 1706, a power source 1708, a memory 1710, a communication interface 1712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 17. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 1702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1710. The processing circuitry 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1702 may include multiple central processing units (CPUs). In the example, the input / output interface 1706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 1708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1708 may further include power circuitry for delivering power from the power source 1708 itself, and / or an external power source, to the various parts of the UE 1700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1708 to make the power suitable for the respective components of the UE 1700 to which power is supplied. The memory 1710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1710 includes one or more application programs 1714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1716. The memory 1710 may store, for use by the UE 1700, any of a variety of various operating systems or combinations of operating systems. The memory 1710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1710 may allow the UE 1700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1710, which may be or comprise a device-readable storage medium. The processing circuitry 1702 may be configured to communicate with an access network or other network using the communication interface 1712. The communication interface 1712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1722. The communication interface 1712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1718 and / or a receiver 1720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1718 and receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item- tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1700 shown in FIGURE 17. As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. FIGURE 18 shows a network node 1800, which may be an embodiment of the network node 1610 of FIGURE 16, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The network node 1800 includes a processing circuitry 1802, a memory 1804, a communication interface 1806, and a power source 1808. The network node 1800 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1804 for different RATs) and some components may be reused (e.g., a same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1800. The processing circuitry 1802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1800 components, such as the memory 1804, to provide network node 1800 functionality. In some embodiments, the processing circuitry 1802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1802 includes one or more of radio frequency (RF) transceiver circuitry 1812 and baseband processing circuitry 1814. In some embodiments, the radio frequency (RF) transceiver circuitry 1812 and the baseband processing circuitry 1814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1812 and baseband processing circuitry 1814 may be on the same chip or set of chips, boards, or units. The memory 1804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1802. The memory 1804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1802 and utilized by the network node 1800. The memory 1804 may be used to store any calculations made by the processing circuitry 1802 and / or any data received via the communication interface 1806. In some embodiments, the processing circuitry 1802 and memory 1804 is integrated. The communication interface 1806 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1806 comprises port(s) / terminal(s) 1816 to send and receive data, for example to and from a network over a wired connection. The communication interface 1806 also includes radio front-end circuitry 1818 that may be coupled to, or in certain embodiments a part of, the antenna 1810. Radio front-end circuitry 1818 comprises filters 1820 and amplifiers 1822. The radio front- end circuitry 1818 may be connected to an antenna 1810 and processing circuitry 1802. The radio front-end circuitry may be configured to condition signals communicated between antenna 1810 and processing circuitry 1802. The radio front-end circuitry 1818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1820 and / or amplifiers 1822. The radio signal may then be transmitted via the antenna 1810. Similarly, when receiving data, the antenna 1810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1818. The digital data may be passed to the processing circuitry 1802. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 1800 does not include separate radio front-end circuitry 1818, instead, the processing circuitry 1802 includes radio front-end circuitry and is connected to the antenna 1810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1812 is part of the communication interface 1806. In still other embodiments, the communication interface 1806 includes one or more ports or terminals 1816, the radio front- end circuitry 1818, and the RF transceiver circuitry 1812, as part of a radio unit (not shown), and the communication interface 1806 communicates with the baseband processing circuitry 1814, which is part of a digital unit (not shown). The antenna 1810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1810 may be coupled to the radio front-end circuitry 1818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1810 is separate from the network node 1800 and connectable to the network node 1800 through an interface or port. The antenna 1810, communication interface 1806, and / or the processing circuitry 1802 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1810, the communication interface 1806, and / or the processing circuitry 1802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source 1808 provides power to the various components of network node 1800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1800 with power for performing the functionality described herein. For example, the network node 1800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1808. As a further example, the power source 1808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 1800 may include additional components beyond those shown in FIGURE 18 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1800 may include user interface equipment to allow input of information into the network node 1800 and to allow output of information from the network node 1800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1800. FIGURE 19 is a block diagram of a host 1900, which may be an embodiment of the host 1616 of FIGURE 16, in accordance with various aspects described herein. As used herein, the host 1900 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1900 may provide one or more services to one or more UEs. The host 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input / output interface 1906, a network interface 1908, a power source 1910, and a memory 1912. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGURES 17 and 18, such that the descriptions thereof are generally applicable to the corresponding components of host 1900. The memory 1912 may include one or more computer programs including one or more host application programs 1914 and data 1916, which may include user data, e.g., data generated by a UE for the host 1900 or data generated by the host 1900 for a UE. Embodiments of the host 1900 may utilize only a subset or all of the components shown. The host application programs 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1900 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. FIGURE 20 is a block diagram illustrating a virtualization environment 2000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. Applications 2002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 2004 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2008a and 2008b (one or more of which may be generally referred to as VMs 2008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 2006 may present a virtual operating platform that appears like networking hardware to the VMs 2008. The VMs 2008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2006. Different embodiments of the instance of a virtual appliance 2002 may be implemented on one or more of VMs 2008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 2008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2008, and that part of hardware 2004 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2008 on top of the hardware 2004 and corresponds to the application 2002. Hardware 2004 may be implemented in a standalone network node with generic or specific components. Hardware 2004 may implement some functions via virtualization. Alternatively, hardware 2004 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 2010, which, among others, oversees lifecycle management of applications 2002. In some embodiments, hardware 2004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2012 which may alternatively be used for communication between hardware nodes and radio units. FIGURE 21 shows a communication diagram of a host 2102 communicating via a network node 2104 with a UE 2106 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1612a of FIGURE 16 and / or UE 1700 of FIGURE 17), network node (such as network node 1610a of FIGURE 16 and / or network node 1800 of FIGURE 18), and host (such as host 1616 of FIGURE 16 and / or host 1900 of FIGURE 19) discussed in the preceding paragraphs will now be described with reference to FIGURE 21. Like host 1900, embodiments of host 2102 include hardware, such as a communication interface, processing circuitry, and memory. The host 2102 also includes software, which is stored in or accessible by the host 2102 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 2106 connecting via an over-the-top (OTT) connection 2150 extending between the UE 2106 and host 2102. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2150. The network node 2104 includes hardware enabling it to communicate with the host 2102 and UE 2106. The connection 2160 may be direct or pass through a core network (like core network 1606 of FIGURE 16) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 2106 includes hardware and software, which is stored in or accessible by UE 2106 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2106 with the support of the host 2102. In the host 2102, an executing host application may communicate with the executing client application via the OTT connection 2150 terminating at the UE 2106 and host 2102. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2150 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2150. The OTT connection 2150 may extend via a connection 2160 between the host 2102 and the network node 2104 and via a wireless connection 2170 between the network node 2104 and the UE 2106 to provide the connection between the host 2102 and the UE 2106. The connection 2160 and wireless connection 2170, over which the OTT connection 2150 may be provided, have been drawn abstractly to illustrate the communication between the host 2102 and the UE 2106 via the network node 2104, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection 2150, in step 2108, the host 2102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 2106. In other embodiments, the user data is associated with a UE 2106 that shares data with the host 2102 without explicit human interaction. In step 2110, the host 2102 initiates a transmission carrying the user data towards the UE 2106. The host 2102 may initiate the transmission responsive to a request transmitted by the UE 2106. The request may be caused by human interaction with the UE 2106 or by operation of the client application executing on the UE 2106. The transmission may pass via the network node 2104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2112, the network node 2104 transmits to the UE 2106 the user data that was carried in the transmission that the host 2102 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2114, the UE 2106 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2106 associated with the host application executed by the host 2102. In some examples, the UE 2106 executes a client application which provides user data to the host 2102. The user data may be provided in reaction or response to the data received from the host 2102. Accordingly, in step 2116, the UE 2106 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 2106. Regardless of the specific manner in which the user data was provided, the UE 2106 initiates, in step 2118, transmission of the user data towards the host 2102 via the network node 2104. In step 2120, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2104 receives user data from the UE 2106 and initiates transmission of the received user data towards the host 2102. In step 2122, the host 2102 receives the user data carried in the transmission initiated by the UE 2106. One or more of the various embodiments improve the performance of OTT services provided to the UE 2106 using the OTT connection 2150, in which the wireless connection 2170 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of, for example, data rate, latency, and / or power consumption and, thereby, provide benefits such as, for example, reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and / or extended battery lifetime. In an example scenario, factory status information may be collected and analyzed by the host 2102. As another example, the host 2102 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2102 may store surveillance video uploaded by a UE. As another example, the host 2102 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 2102 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data. In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2150 between the host 2102 and UE 2106, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2102 and / or UE 2106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2150 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2150 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2104. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 2102. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2150 while monitoring propagation times, errors, etc. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. EXAMPLE EMBODIMENTS Group A Example Embodiments Example Embodiment A1. A method performed by a user equipment for Wakeup Receiver (WUR) operation, the method comprising: − any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above. Group B Example Embodiments Example Embodiment B1. A method performed by a network node for enabling Wakeup Receiver (WUR) operation in User Equipment (UE), the method comprising: − any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above. Group C Example Embodiments Example Embodiment C1. A method performed by a user equipment (UE) for Wakeup Receiver (WUR) operation, the method comprising at least one of: receiving, by a WUR of the UE, a wakeup signal (WUS) from a network node; based on receiving the WUS, waking up a main receiver (MR) of the UE; and after waking up the MR, performing at least one of: (option 1) transitioning the WUR to a sleep mode for a WUR sleep period; (option 2) continuing to monitor, by the WUR, for at least one additional WUS; and (option 3) transmitting, to the network node, an indication that the WUS was received by the UE. Example Embodiment C2. The method of Example Embodiment C1, comprising at least one of: receiving, from the network node, an indication that data will be transmitted to the UE during the WUR sleep period; and receiving, from the network node, a Physical Downlink Control Channel (PDCCH) message during the WUR sleep period. Example Embodiment C3. The method of any one of Example Embodiments C1 to C2, wherein transitioning the WUR to the sleep mode for the WUR sleep period comprises ceasing monitoring for additional WUS from the network node during the WUR sleep period. Example Embodiment C4. The method of any one of Example Embodiments C1 to C3, comprising receiving, from the network node, an indication of a time duration associated with the WUR sleep period. Example Embodiment C5. The method of any one of Example Embodiments C1 to C4, wherein the indication of the time duration associated with the WUR sleep period is received via Downlink Control Information (DCI) or Medium Access Control-Control Element (MAC-CE). Example Embodiment C6. The method of any one of Example Embodiments C1 to C5, wherein a time duration associated with the WUR sleep period is less than (and / or shorter than) and / or equal to a time duration of an OnDuration period associated with the MR. Example Embodiment C7. The method of any one of Example Embodiments C1 to C6, wherein the network node is configured not to send another WUS during the WUR sleep period. Example Embodiment C8. The method of Example Embodiment C1, comprising: while monitoring for the at least one additional WUS, receiving and / or detecting the at least one additional WUS from the network node. Example Embodiment C9. The method of Example Embodiment C8, comprising: based on receiving and / or detecting the at least one additional WUS from the network node, increasing an amount of time associated with an inactivity timer of the MR to extend an active state of the MR. Example Embodiment C10. The method of Example Embodiment C9, wherein increasing the amount of time associated with the inactivity timer of the MR comprises restarting the inactivity timer. Example Embodiment C11. The method of any one of Example Embodiments C8 to C10, wherein the WUS and / or the at least one additional WUS is assumed by the UE, the WUR, and / or the MR to be a valid WUS intended for the UE. Example Embodiment C12. The method of any one of Example Embodiments C1 to C11, wherein waking up the MR of the UE comprises initiating monitoring of a PDCCH by the MR for at least one paging occasion. Example Embodiment C13. The method of Example Embodiment C12, comprising: determining that no PDCCH is received during at least a minimum number (k) of paging occasions; and transitioning the MR to a sleep state or inactive state. Example Embodiment C14. The method of Example Embodiment C13, wherein the minimum number (k) of paging occasions is determined based on at least one of: a battery level of the UE, a PDCCH duration, a PDCCH configuration, and a UE bandwidth. Example Embodiment C15. The method of Example Embodiment C12, comprising: determining that a PDCCH is received; and initiating or restarting an inactivity timer associated with the MR. Example Embodiment C16. The method of any one of Example Embodiments C8 to C15 comprising: receiving a PDCCH-skip indication from the network node, and transitioning the MR to a sleep state. Example Embodiment C17. The method of any one of Example Embodiments C8 to C16, comprising: based on receiving the WUS, transitioning to a different operation mode and / or configuration for monitoring for the at least one additional WUS. Example Embodiment C18. The method of Example Embodiment C17, wherein transitioning to the different operation mode and / or configuration comprises transitioning to a duty-cycled mode for a duration. Example Embodiment C19. The method of Example Embodiment C18, wherein the duration is determined based on at least one of: a time period associated with a drx-onDurationTimer, a false alarm rate, a MR sleep state and transition time, and / or a latency requirement. Example Embodiment C20. The method of any one of Example Embodiments C1 to C19, wherein the indication that the WUS was received is transmitted via at least one of: • Scheduling Request (SR) on at least one configured PUCCH resource; • a new indication on at least one configured PUCCH resource; • a Random Access message using an allocated preamble; • a MAC control element; and • RRC signaling. Example Embodiment C21. The method of any one of Example Embodiments C1 to C20, comprising: after transmitting the indication that the WUS was received, transitioning the WUR to sleep mode, or after transmitting the indication that the WUS was received, continuing to monitor, by the WUR, for the at least one additional WUS signal. Example Embodiment C22. The method of any one of Example Embodiments C1 to C21, comprising: after transmitting the indication that the WUS was received, receiving a message from the network node that indicates that the WUS was a false alarm; and based on the message from the network node indicating that the WUS was a false alarm, transitioning the WUR to a sleep mode for a WUR sleep period Example Embodiment C23. The method of any one of Example Embodiments C1 to C22, comprising at least one of: determining that at least one WUS was a false alarm, determining a false alarm rate based on at least one WUS that is determined to be a false alarm, storing information associated with at least one false alarm and / or a false alarm rate, transmitting, to the network node, information indicating with the at least one false alarm and / or a false alarm rate. Example Embodiment C24. The method of Example Embodiment C23, wherein the information indicating the at least one false alarm and / or false alarm rate is transmitted to the network node via at least one of: • a MAC control element, • a RRC message or information element, • UE Assistance Information, and • SON reporting. Example Embodiment C25. The method of any one of Example Embodiments C1 to C24, wherein the WUR comprises a dedicated receiver that is separate from the MR, and / or wherein the WUR requires less power for operation and / or is less complex than the MR. Example Embodiment C26. The method of any one of Example Embodiments C1 to C25, wherein the WUS is received during a WUS duration that occurs prior to a paging occasion associated with a Physical Downlink Control Channel (PDCCH). Example Embodiment C27. The method of any one of Example Embodiments C1 to C26, wherein waking up the MR of the UE comprises initiating monitoring of the PDCCH for detection by the MR of at least one PDCCH message. Example Embodiment C28. The method of Example Embodiments C1 to C27, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Example Embodiment C29. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C28. Example Embodiment C30. A user equipment configured to and / or adapted to perform any of the methods of Example Embodiments C1 to C28. Example Embodiment C31. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C28. Example Embodiment C32. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C28. Example Embodiment C33. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C28. Example Embodiment C34. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments C1 to 28. Group D Example Embodiments Example Embodiment D1. A method performed by a network node for enabling Wakeup Receiver (WUR) operation in User Equipment (UE), the method comprising at least one of: configuring the UE to, based on receiving a Wakeup Signal (WUS) by a WUR of the UE, perform at least one of: waking up a main receiver (MR) of the UE; (option 1) transitioning the WUR to a sleep mode for a WUR sleep period; (option 2) continuing to monitor, by the WUR, for at least one additional WUS; and (option 3) transmitting, to the network node, an indication that the WUS was received by the UE; and transmitting, to the UE, the WUS for reception by the WUR. Example Embodiment D2A. The method of Example Embodiment D1, wherein configuring to perform any one or more functions and / or steps comprises transmitting, to the UE, information that indicates that the UE is to perform the one or more functions and / or steps. Example Embodiment D2B. The method of any one of Example Embodiments D1 to D2A, comprising at least one of: transmitting, to the UE, an indication that data will be transmitted to the UE during the WUR sleep period; and transmitting, to the UE, a Physical Downlink Control Channel (PDCCH) message during the WUR sleep period. Example Embodiment D3. The method of any one of Example Embodiments D1 to D2B, wherein configuring the UE to transition the WUR to the sleep mode for the WUR sleep period comprises configuring the UE to cease monitoring for additional WUS from the network node during the WUR sleep period. Example Embodiment D4. The method of any one of Example Embodiments D1 to D3, comprising transmitting, to the UE, an indication of a time duration associated with the WUR sleep period. Example Embodiment D5. The method of any one of Example Embodiments D1 to D4, wherein the indication of the time duration associated with the WUR sleep period is transmitted via Downlink Control Information (DCI) or Medium Access Control-Control Element (MAC-CE). Example Embodiment D6. The method of any one of Example Embodiments D1 to D5, wherein a time duration associated with the WUR sleep period is less than (and / or shorter than) and / or equal to a time duration of an OnDuration period associated with the MR. Example Embodiment D7A. The method of any one of Example Embodiments D1 to D6, comprising transmitting, to the UE, another WUS during the WUR sleep period. Example Embodiment D7B. The method of any one of Example Embodiments D1 to D6, comprising: determining that no response has been received from the UE for a period of time after the transmission of the WUS; and based on the determining, transmitting, to the UE, another WUS. Example Embodiment D8. The method of Example Embodiment D1, comprising: while the WUR is monitoring for the at least one additional WUS, transmitting at least one additional WUS to the UE. Example Embodiment D9. The method of Example Embodiment D8, comprising configuring the UE to: based on receiving and / or detecting the at least one additional WUS from the network node, increasing an amount of time associated with an inactivity timer of the MR to extend an active state of the MR. Example Embodiment D10. The method of Example Embodiment D9, wherein configuring the UE to increase the amount of time associated with the inactivity timer of the MR comprises configuring the UE to restart the inactivity timer. Example Embodiment D11. The method of any one of Example Embodiments D8 to D10, comprising configuring the UE to assume that the WUS and / or the at least one additional WUS is a valid WUS intended for the UE. Example Embodiment D12. The method of any one of Example Embodiments D1 to D11, configuring the UE to wake up the MR of the UE comprises configuring the UE to initiate monitoring of a PDCCH by the MR for at least one paging occasion. Example Embodiment D13. The method of Example Embodiment D12, comprising configuring the UE to: transition the MR to a sleep state or inactive state when no PDCCH is received during at least a minimum number (k) of paging occasions. Example Embodiment D14. The method of Example Embodiment D13, wherein the minimum number (k) of paging occasions is determined based on at least one of: a battery level of the UE, a PDCCH duration, a PDCCH configuration, and a UE bandwidth. Example Embodiment D15. The method of Example Embodiment D12, comprising configuring the UE to: initiate or restart an inactivity timer associated with the MR when a PDCCH is received. Example Embodiment D16. The method of any one of Example Embodiments D8 to D15 comprising: transmitting, to the UE, a PDCCH-skip indication from the network node, and wherein the UE is configured to transition the MR to a sleep state based on the PDCCH-skip indication. Example Embodiment D17. The method of any one of Example Embodiments D8 to D16, comprising configuring the UE to: based on receiving the WUS, transition to a different operation mode and / or configuration for monitoring for the at least one additional WUS. Example Embodiment D18. The method of Example Embodiment D17, wherein configuring the UE to transition to the different operation mode and / or configuration comprises configuring the UE to transition to a duty-cycled mode for a duration. Example Embodiment D19. The method of Example Embodiment D18, wherein the duration is based on at least one of: a time period associated with a drx-onDurationTimer, a false alarm rate, a MR sleep state and transition time, and / or a latency requirement. Example Embodiment D20. The method of any one of Example Embodiments D1 to D19, wherein the indication that the WUS was received is received via at least one of: • Scheduling Request (SR) on at least one configured PUCCH resource; • a new indication on at least one configured PUCCH resource; • a Random Access message using an allocated preamble; • a MAC control element; and • RRC signaling. Example Embodiment D21. The method of any one of Example Embodiments D1 to D20, comprising configuring the UE to: after transmitting the indication that the WUS was received, transition the WUR to sleep mode, or after transmitting the indication that the WUS was received, continue to monitor, by the WUR, for the at least one additional WUS signal. Example Embodiment D22. The method of any one of Example Embodiments D1 to D21, comprising at least one of: after receiving the indication that the WUS was received, determining that the WUS was a false alarm; transmitting a message to the UE that indicates that the WUS was a false alarm; and / or configuring the UE to, based on the message from the network node indicating that the WUS was a false alarm, transition the WUR to a sleep mode for a WUR sleep period Example Embodiment D23. The method of any one of Example Embodiments D1 to D22, comprising configuring the UE to perform at least one of: determine that at least one WUS was a false alarm, determine a false alarm rate based on at least one WUS that is determined to be a false alarm, store information associated with at least one false alarm and / or a false alarm rate, transmit, to the network node, information indicating the at least one false alarm and / or a false alarm rate. Example Embodiment D24. The method of any one of Example Embodiments D1 to D23, comprising receiving, from the UE, information indicating at least one false alarm and / or false alarm rate. Example Embodiment D25. The method of any one of Example Embodiments D23 to D24, wherein the information indicating the at least one false alarm and / or false alarm rate is transmitted to the network node via at least one of: • a MAC control element, • a RRC message or information element, • UE Assistance Information, and • SON reporting. Example Embodiment D26. The method of any one of Example Embodiments D1 to D25, wherein the WUR comprises a dedicated receiver that is separate from the MR, and / or wherein the WUR requires less power for operation and / or is less complex than the MR. Example Embodiment D27. The method of any one of Example Embodiments D1 to D26, wherein the WUS is transmitted during a WUS duration that occurs prior to a paging occasion associated with a Physical Downlink Control Channel (PDCCH). Example Embodiment D28. The method of any one of Example Embodiments D1 to D27, wherein configuring the UE to wake up the MR of the UE comprises configuring the MR to initiate monitoring of the PDCCH for at least one PDCCH message. Example Embodiment D29. The method of any of the previous Example Embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Example Embodiment D30. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D29. Example Embodiment D31. A network node configured to perform any of the methods of Example Embodiments D1 to D29. Example Embodiment D32. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D29. Example Embodiment D33. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D29. Example Embodiment D34. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D29. Group E Example Embodiments Example Embodiment E1. A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A and C Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry. Example Embodiment E2. A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B and D Example Embodiments; power supply circuitry configured to supply power to the processing circuitry. Example Embodiment E3. A user equipment (UE) for _______________, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A and C Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS 1. A method (1200) performed by a user equipment, UE, having a discontinuous reception on- duration timer, drx-onDurationTimer, the method comprising: receiving (1210) a wake-up signal, WUS, from a network node; and based on receiving the WUS, monitoring (1220) for a physical downlink control channel, PDCCH, using a different timer than the drx-onDurationTimer.

2. The method of claim 1, wherein said different timer has a shorter duration than the drx- onDurationTimer.

3. The method of claim 2, wherein, after the UE receives the WUS, the UE monitors for the PDCCH during a shorter time than a duration of the drx-onDurationTimer.

4. The method of any of claims 1-2, wherein the WUS is received by a wake-up receiver, WUR, wherein a main receiver wakes up to perform the monitoring for the PDCCH, and wherein the main receiver goes to a sleep mode before the whole duration of the drx-onDurationTimer has passed unless the PDCCH is detected.

5. The method of any of the preceding claims, further comprising: starting (1240) a discontinuous reception inactivity timer, drx-InactivityTimer, if the PDCCH is detected.

6. The method of any of the preceding claims, wherein the method further comprises: transmitting an indication to the network node that the WUS was received; and after transmitting the indication that the WUS was received, receiving, from the network node, information indicating that the received WUS was not intended for the UE.

7. The method of claim 6, wherein the WUS is received by a wake-up receiver, WUR, wherein a main receiver wakes up to perform the monitoring for the PDCCH, and wherein the main receivergoes to a sleep mode in response to reception of the information indicating that the received WUS was not intended for the UE.

8. The method of any of the preceding claims, wherein the method comprises: transmitting an indication to the network node that the WUS was received, wherein the indication is transmitted via: PDCCH resources configured for the UE; or a scheduling request, SR, transmission on PDCCH resources configured for the UE; or a random access preamble allocated to be used for the acknowledgement; or a medium access control, MAC, control element; or radio resource control, RRC, signaling.

9. The method of any of the preceding claims, wherein the WUS is received by a wake-up receiver, WUR, the method comprising: based on receiving the WUS, waking up a main receiver of the UE; and after waking up the main receiver, transitioning the WUR to a sleep mode for a sleep period or continuing using the WUR to monitor for at least one additional WUS.

10. The method of claim 9, further comprising: receiving, from the network node, signaling indicating a length of the sleep period.

11. The method of any of the preceding claims, wherein the WUS is received by a wake-up receiver, WUR, operating in a first operation mode, the method comprising: based on receiving the WUS, waking up a main receiver of the UE and operating the WUR in a second operation mode to monitor for at least one additional WUS.

12. The method of claim 11, wherein the first operation mode provides continuous monitoring for the WUS, and wherein the second operation mode provides discontinuous monitoring for the WUS.

13. The method of any of the preceding claims, further comprising:restarting or extending an inactivity timer upon reception of a second WUS.

14. The method of claim 13, wherein the WUS is received by a wake-up receiver, WUR, wherein a main receiver wakes up to perform the monitoring for the PDCCH, and wherein the restarting or extending of the inactivity timer is to keep the main receiver active longer before the main receiver goes to a sleep mode.

15. The method of any of the preceding claims, further comprising: reporting, to the network node, statistics regarding incorrect reception of WUS and / or reception of WUS intended for other UEs.

16. The method of claim 15, wherein the reporting is provided: in a medium access control, MAC, element; or in a radio resource control message, RRC, or information element; or in UE Assistance Information; or in SON reporting.

17. The method of any of the preceding claims, wherein the UE comprises a wake-up receiver, WUR, and a main receiver, wherein the WUS is received by the WUR, wherein the main receiver wakes up to perform the monitoring for the PDCCH, and wherein: the WUR is a dedicated receiver that is separate from the main receiver; and / or the WUR requires less power for operation than the main receiver; and / or the WUR is less complex than the main receiver.

18. The method of any of the preceding claims, wherein the WUS is received during a WUS duration that occurs prior to a paging occasion associated with the PDCCH.

19. The method of any of the preceding claims, wherein the method is performed while the UE is in radio resource control, RRC, connected mode.

20. A method (1300) performed by a network node for communicating with a first user equipment, UE, having a discontinuous reception on-duration timer, drx-onDurationTimer, the method comprising: transmitting (1310) a wake-up signal, WUS; and after transmitting the WUS, transmitting (1320) a physical downlink control channel, PDCCH, within a duration of a different timer than the drx-onDurationTimer.

21. The method of claim 20, wherein said different timer has a shorter duration than the drx- onDurationTimer.

22. The method of any of claims 20-21, wherein the WUS was intended for another UE, wherein method further comprises: receiving an indication from the first UE that the WUS was received by the first UE; and transmitting, to the first UE, information indicating that the WUS was not intended for the first UE.

23. The method of any of claims 20-22, wherein the method comprises: receiving an indication from the first UE that the WUS was received by the first UE, wherein the indication is received via: PDCCH resources configured for the first UE; or a scheduling request, SR, transmission on PDCCH resources configured for the first UE; or a random access preamble allocated to be used for the acknowledgement; or a medium access control, MAC, control element; or radio resource control, RRC, signaling.

24. The method of any of claims 20-23, further comprising: transmitting signaling indicating a length of a sleep period during which a wake-up receiver, WUR, that receives the WUS is to be kept in a sleep mode after receiving the WUS.

25. The method of any of claims 20-24, further comprising:receiving, from the first UE, statistics regarding incorrect reception of WUS and / or reception of WUS intended for other UEs.

26. The method of claim 25, wherein the reporting is received: in a medium access control, MAC, element; or in a radio resource control message, RRC, or information element; or in UE Assistance Information; or in SON reporting.

27. The method of any of claims 20-26, wherein the WUS is transmitted during a WUS duration that occurs prior to a paging occasion associated with the PDCCH.

28. The method of any of claims 20-27, further comprising: determining that no response has been received from the first UE for a period of time after the transmission of the WUS; and based on the determining, transmitting another WUS to the first UE.

29. A user equipment, UE, (1700) having a discontinuous reception on-duration timer, drx- onDurationTimer, the UE comprising processing circuitry (1702) configured to: receive a wake-up signal, WUS, from a network node (1800); and based on receiving the WUS, monitor for a physical downlink control channel, PDCCH, using a different timer than the drx-onDurationTimer.

30. The UE of claim 29, wherein the processing circuitry is configured to perform the method of any of clams 2-19.

31. A user equipment, UE, (1700) having a discontinuous reception on-duration timer, drx- onDurationTimer, the UE being configured to: receive a wake-up signal, WUS, from a network node (1800); and based on receiving the WUS, monitor for a physical downlink control channel, PDCCH, using a different timer than the drx-onDurationTimer.

32. The UE of claim 31, wherein the UE is configured to perform the method of any of claims 2- 19.

33. A network node (1800) for communicating with a first user equipment, UE, (1700) having a discontinuous reception on-duration timer, drx-onDurationTimer, the network node comprising processing circuitry (1802) configured to: transmit a wake-up signal, WUS; and after transmitting the WUS, transmit a physical downlink control channel, PDCCH, within a duration of a different timer than the drx-onDurationTimer.

34. The network node of claim 33, wherein the processing circuitry is configured to perform the method of any of clams 21-28.

35. A network node (1800) for communicating with a first user equipment, UE, (1700) having a discontinuous reception on-duration timer, drx-onDurationTimer, the network node being configured to: transmit a wake-up signal, WUS; and after transmitting the WUS, transmit a physical downlink control channel, PDCCH, within a duration of a different timer than the drx-onDurationTimer.

36. The network node of claim 35, wherein the network node is configured to perform the method of any of claims 21-28.

Images