EP4706301A1 - Resource allocation and power adjustment for wake-up signals - Google Patents

Abstract

Systems and methods are disclosed herein that relate to resource allocation and power adjustment for Wake-Up Receiver (WUR) related downlink signals, e.g., Wake-Up Signals (WUSs), in a wireless network such as, e.g., a Radio Access Network (RAN) of a cellular communications system. In one embodiment, a method performed by a User Equipment (UE) for WUR related downlink signal monitoring and detection comprises monitoring for a WUR related downlink signal in time-domain resources for WUR-related downlink signal monitoring, wherein the time domain resources for WUR-related downlink signal monitoring are based on, or depend on, one or more non- WUR-related downlink signal related time domain resource patterns. In this manner, efficient coexistence with other transmissions can be ensured.

Description

RESOURCE ALLOCATION AND POWER ADJUSTMENT FOR WAKE-UP SIGNALS

RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63/464,519, filed May 5, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to a wireless network and, more specifically, to wakeup signals in a Radio Access Network (RAN) of a cellular communications system.

BACKGROUND

1 Wake- Up Receiver (WUR ) and Wake- UP Signal (WUS )

[0003] Wake-Up Receiver (WUR), sometimes also referred to as ‘wake-up radio’, is about enabling a low power receiver in User Equipments (UEs). ,In case of detection of a Wake-Up Signal (WUS) by the low power receiver (i.e., the WUR), the low power receiver (i.e., the WUR) wakes up a main (baseband/radio frequency (RF)/less power efficient) receiver to detect an incoming message, which is typically related to paging. For example, upon detecting a WUS, the low power receiver wakes up the main receiver to detect a Physical Downlink Control Channel (PDCCH) in Paging Occasions (POs) wherein this PDCCH schedules a paging message on Physical Downlink Shared Channel (PDSCH). The main benefits of employing WUR is lower energy consumption and longer device battery life, or alternatively 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 1 is an illustration of the location, in the time domain, of a WUS and the paging occasion to which it is associated.

[0004] In general, there are two approaches for detecting a WUS. These two approaches are:

• 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 (i.e., a dedicated 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.

[0005] As an example, Figure 2 illustrates an example UE including a main receiver and a dedicated WUR. The WUR is used for monitoring for a WUS. Once WUR detects the intended WUS, it wakes up the main (baseband/RF/less power efficient) receiver to detect further incoming messages (i.e., a main signal). 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 Phase-Shift Keying (PSK). However, the WUS is transmitted using an Orthogonal Frequency Division Multiplexing (OFDM)-based transmitter.

2 WUS for NB-IoT and LTE-M

2.1 Release 15

[0006] In 3^rd Generation Partnership Project (3GPP) Release 15, WUS was specified for Narrowband Internet of Things (NB-IoT) and Fong Term Evolution for Machine type communication (LTE-M). The main motivation was UE energy consumption reduction since, with coverage enhancement, PDCCH can be repeated many times, whereas 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. The UE would continue to check for PDCCH in the PO only if a WUS is detected. Otherwise, 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 coverage enhancements, the WUS can be of variable length depending on the UE’s coverage, see Figure 3 which is an illustration of WUS for NB-IoT and LTE-M.

[0007] A WUS is based on the transmission of a short signal that indicates to the UE that it should continue to decode the downlink (DL) control channel, e.g. full Narrowband PDCCH (NPDCCH) for NB-IoT. If such signal is absent (DTX i.e., 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 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 1, where white blocks indicate possible WUS and PO positions whereas the black boxes indicate actual WUS and PO positions.

[0008] The specification of Release 15 WUS is spread out over several parts of the Long Term Evolution (LTE) 36-series standard, e.g., 3GPP Technical Specifications (TSs) 36.211, 36.213, 36.304, and 36.331.

2.2 WUS UE Grouping Objective in Release 16

[0009] In the 3GPP Release 16 Work Item Description (WID), 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).

[0010] The purpose 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 Release 16 Group WUS, or GWUS. However, this is not directly related to WUR and will not further be explained hereafter.

3 Release 17 NR PEI

[0011] In 3GPP Release 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 Release 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 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 three SSBs if PEI is not used (value according to UE vendors). So, for most UEs, Release 17 PEI will result in gains or increased performance.

[0012] Note that Release 17 PEI will also support UE grouping for false paging reduction, similar to the Release 16 GWUS above, which will have some gains at higher paging load.

[0013] In RAN#93e, it was agreed that PEI will be PDCCH-based, as seen in from the next subsection, making it much less interesting for WUR (i.e., the main baseband receiver is required for decoding PEI). 4 Release 18 NR WUR

[0014] In 3GPP Release 18, there has been rather large interest in introducing 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 Release 17 PEI is the WUS in Release 18 should not be PDCCH- based and allow for a simpler and low power receiver, i.e., WUR with simple modulation and detection techniques (e.g., using OOK modulation and non-coherent detection).

[0015] In Release 18, a study item on “low-power wake-up signal and receiver for NR” was approved. The relevant justification and objective sections are copied below from RP-213645, “Study on low-power Wake-up Signal and Receiver for NR”:

***** START EXCERPT FROM RP-213645 *****

• Justification

5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual's usage time. In general, 5G devices consume tens of milliwatts in RRC idle/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience.

Energy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR 38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required.

The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, eDRX cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment use case, fire shutters shall be closed and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in Rel-18, e.g. lower than eDRX latency.

Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If UEs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wake-up signal with ultra-low power consumption. Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.

The power consumption for monitoring wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver used for signal detecting and processing.

The study should primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g. XR/smart glasses, smart phones. Objective of SI

As opposed to the work on UE power savings in previous releases, this study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy UEs. Solutions should target substantial gains compared to the existing Rel-15/16/17 UE power saving mechanisms. Other aspects such as detection performance, coverage, UE complexity, should be covered by the evaluation.

The study item includes the following objectives:

• Identify evaluation methodology (including the use cases) & KPIs [RANI] o Primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables

■ Other use cases are not precluded

• Study and evaluate low-power wake-up receiver architectures [RANI, RAN4]

• Study and evaluate wake-up signal designs to support wake-up receivers [RANI, RAN4]

• Study and evaluate LI procedures and higher layer protocol changes needed to support the wake-up signals [RAN2, RANI]

• Study potential UE power saving gains compared to the existing Rel-15/16/17 UE power saving mechanisms and their coverage availability, as well as latency impact. System impact, such as network power consumption, coexistence with non-low-power-WUR UEs, network coverage/capacity/ resource overhead should be included in the study [RANI] o Note: The need for RAN2 evaluation will be triggered by RANI when necessary.

***** _END EXCERPT FROM RP-213645 *****

[0016] The 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 extend the battery life of the UE, 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 microwatts (pW)) that this can even, in combination with energy harvesting, enable the WUR to be 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 6^th Generation (6G) systems.

5 Ambient loT and Zero Energy Devices

[0017] The 3GPP Release 18 Radio Access Network (RAN) Working Group is currently discussing the concept of Zero-Energy (ZE) Internet of Things (loT), also known as Ambient loT. ZE loT devices are designed to operate without the need for manual battery replacement or recharging by harvesting energy from the surrounding environment, resulting in low maintenance and long-lasting functionality. However, the small size, ultra-low cost, and battery-less nature of ZE loT devices present unique design challenges. [0018] Supporting ZE loT devices requires significant reduction of power consumption and complexity by simplifying the Radio Frequency (RF) chain and baseband architecture, reducing memory size, and eliminating unnecessary components. To achieve ultra-low power consumption, communication procedures between ZE loT devices and Access Points (APs) must be designed as simply as possible. While Orthogonal Frequency Division Multiplexing (OFDM) may not be suitable for ZE loT devices due to its high-power consumption requirements, simpler waveforms such as OOK/FSK modulation offer a more promising option for enabling ultra-low complexity data transmission and reception. However, one of the key challenges in adopting these simpler waveforms is ensuring compatibility with existing OFDM-based architecture.

[0019] The 3GPP study on Ambient loT (3GPP Technical Report (TR) 22.840) investigates the feasibility of a new loT technology to open new markets within 3GPP systems, whose number of connections and/or device density can be orders of magnitude higher than existing 3GPP loT technologies, and which can provide complexity and power consumption orders-of-magnitude lower than existing 3GPP Eow Power Wide Area (EPWA) technologies such as NB-IoT and LTE- M (also referred to as LTE-MTC).

6 IEEE WUR

[0020] Institute of Electrical and Electronics Engineers (IEEE) 802.11 standardized support for WUR in the task group (TG) ba. Similar to the 3GPP solution, the use of WUR is only enabled in stations and not in APs, which 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 Gigahertz (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, where the configuration is only valid for the connection to the associated AP and the configuration must be torn down/de-configured if WUR is no longer used. 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 dutycycles and on-time during wake up is part of the WUR configuration.

[0021] Unlike the 3GPP solution, the WUR operation mode is a “sub-state” of the regular operation and, upon the detection of a WUS transmission from the AP, the station will resume the power saving mechanism it was configured with before entering the WUR operation mode. That is, IEEE has specified a number of different power saving mechanisms, and for example if duty- cycled monitoring of the downlink has been configured for the station, it will switch to that upon detection of the WUS (i.e., unlike the specified 3GPP mechanism which only covers paging, and the UE will continue to monitor PDCCH if WUS is detected). In this way the IEEE WUR functionality is more general, and still allows for the station to, upon detection of WUS, “monitor paging” by checking in the beacon from the AP for which stations there is data, or for the station to directly respond with an uplink transmission.

[0022] The physical wake-up signal (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., WUR can be enabled as a software upgrade in APs). The WUS is 4 MHz wide, but a whole 20 MHz channel is reserved. The WUS starts with a 20 MHz legacy preamble (to allows other stations to perform carrier sense) followed by 4 MHz Manchester coded OOK. Two data rates are supported: 62.5 kbps and 250 kbps, and link adaptation is up to the AP (each packet is self-contained and includes the data rate, i.e. in the WUR there are two possible sync words used to signal the data rate).

7 5G NR Signals and Channels

[0023] Here, some of the key downlink signals and channels in 3GPP 5^th Generation (5G) or New Radio (NR) are briefly discussed.

7.1 Synchronization Signal Block ( SSB )

[0024] The most fundamental aspects of SSB (also referred to as an “SS/PBCH block”) can be summarized as follows (see, e.g., 3GPP Technical Specification (TS) 38.211 V 17.0.0 and 3GPP TS 38.213 V17.0.0):

• An SSB contains the Primary Synchronization Signal (PSS), Secondary Synchronization signal (SSS), Physical Broadcast channel (PBCH) along with the Demodulation Reference Signal (DMRS). o Broadcast Channel (BCH) carries the Master Information Block (MIB)

• In frequency domain, one SSB occupies 20 contiguous resource blocks which is equivalent to 240 subcarriers, as illustrated in Figure 4 (which illustrates the time domain structure of an SSB). In time domain, one SSB spans over 4 OFDM symbols. Among the four symbols, one symbol is for PSS, one symbol is for SSS, and 2 symbols are for PBCH. Specifically, PSS occupies the first OFDM symbol of SSB and spans over 127 subcarriers. SSS is located in the third OFDM symbol of SSB and spans over 127 subcarriers. The total number of resource elements (REs) used for PBCH transmission per SSB is 576. There are, however, 113 unused subcarriers in the first symbol, and 17 unused subcarriers in the third symbol, as shown in Figure 4. Therefore, there are 130 unused resource elements (REs) within an SSB. In the current NR design, the complex-valued symbols corresponding to these unused REs are set to zero. One or more SSBs can be transmitted per SS burst according with the Table 1 below.

• “Cell search” for “SS/PBCH block” accounting for different carrier frequencies and subcarrier spacings: o Within one half-frame there are several occurrences of SSBs. o The SSBs can be located in the first or second half of the frame as indicated via MIB. o One or multiple SSBs (i.e., a group of occurrences) compose a Synchronization Signal (SS) burst. o The SS burst periodicity can be 5 milliseconds (ms), 10ms, 20ms, 40ms, 80ms, or 160ms.

Table 1: Max number of SSBs per SS burst depending on subcarrier spacing (SCS) and carrier frequency

• The frequency position of an SSB is determined based on the synchronization raster and its mapping to a resource element of SSB.

7.2 NR PDCCH and CORESET

[0025] Physical Downlink Control Channel (PDCCH) carries Downlink Control Information (DO). PDCCHs are transmitted in Control Resource Sets (CORESETs) which span over one, two, or three contiguous OFDM symbols over multiple Resource Blocks (RBs). In frequency domain, a CORESET can span over one or multiple chunks of 6 RBs. For CORESETs other than CORESET #0, multiple chunks of 6 RBs can be either contiguous or non-contiguous. CORESET #0, which is configured during the initial access, can only have 24, 48, or 96 RBs. Also, CORESET #0 must be contiguous in frequency domain, and it is not necessarily aligned with the six-RB grid. [0026] During initial network access a UE first acquire SSB and decodes the PBCH. The PBCH provides necessary information for the UE to proceed to decode System Information Block 1 (SIB1). SIB1 is transmitted over the Physical Downlink Shared Channel (PDSCH) and these resources are indicated by PDCCH. The CORESET and Common Search Space Type#0 configurations are provided by Master Information Block (MIB) obtained from SSB.

[0027] Table 2 below shows different configurations and bandwidths of CORESET #0. As can be seen, the bandwidth of CORESET #0 can be up to 17.28 Megahertz (MHz) in Frequency Range 1 (FR1) (15/30 kilohertz (kHz) SCS).

Table 2: Different configurations of CORESET #0 in NR. 7.3 Reference Signals

[0028] Reference signals are predefined signals occupying specific resource elements within the downlink time-frequency grid. The NR specification includes several types of reference signals transmitted in different ways and intended to be used for different purposes by a receiving device. The UE uses the Demodulation Reference Signal (DM-RS) and the Channel State Information Reference Signal (CSI-RS) to aid channel estimation and to support measurements. For phase noise compensation, the UE uses the PDSCH phase Tracking Reference Signal (PT- RS). Positioning Reference Signal (PRS) is used to estimate the position of the UE in the wireless network.

• (DM-RS for PDSCH are intended for channel estimation at the device as part of coherent demodulation. They are present only in the resource blocks used for PDSCH transmission.

• PT-RS can be seen as an extension to DM-RS for PDSCH/PUSCH and are intended for phase-noise compensation. The PT-RS is denser in time but sparser in frequency than the DM-RS, and, if configured, occurs only in combination with DM-RS.

• CSI-RS are downlink reference signals intended to be used by devices to acquire downlink Channel-State Information (CSI). Specific instances of CSI-RS can be configured for time/frequency tracking and mobility measurements.

• Tracking Reference Signals (TRS) are sparse reference signals intended to assist the device in time and frequency tracking. A specific CSI-RS configuration serves the purpose of a TRS.

SUMMARY

[0029] Systems and methods are disclosed herein that relate to resource allocation and power adjustment for Wake-Up Receiver (WUR) related downlink signals, e.g., Wake-Up Signals (WUSs), in a wireless network such as, e.g., a Radio Access Network (RAN) of a cellular communications system. In one embodiment, a method performed by a User Equipment (UE) for WUR related downlink signal monitoring and detection comprises monitoring for a WUR related downlink signal in time-domain resources for WUR-related downlink signal monitoring, wherein the time domain resources for WUR-related downlink signal monitoring are based on, or depend on, one or more non- WUR-related downlink signal related time domain resource patterns. In this manner, efficient coexistence with other transmissions can be ensured.

[0030] In one embodiment, the one or more non- WUR-related downlink signal related time domain resource patterns comprise one or more time domain patterns for one or more non-WUR- related downlink signal transmissions. In one embodiment, the one or more non-WUR-related downlink signal transmissions comprise Synchronization Signal Block (SSB) transmissions. In one embodiment, the one or more non-WUR-related downlink signal transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types. In one embodiment, the one or more downlink reference signal types comprise any one or more of: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information Reference Signal (CSI-RS),and Tracking Reference Signal (TRS).

[0031] In one embodiment, the one or more non-WUR-related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel (PDCCH) search space.

[0032] In one embodiment, the one or more non-WUR-related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel (PDCCH) search space in Control Resource Set, CORESET, #0.

[0033] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are further based on, or depend on, a reserved time domain resource pattern.

[0034] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are contiguous in time.

[0035] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are non-contiguous in time.

[0036] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR-related downlink signal.

[0037] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR-related downlink signal and whether non-WUR-related downlink signal related transmission(s) are present.

[0038] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are such that WUS is not present in a first N symbols of each slot.

[0039] In one embodiment, the time domain resources for WUR-related downlink signal monitoring are such that a WUR-related downlink signal is not present in a last N symbols of each slot.

[0040] In one embodiment, frequency domain resources for WUR-related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE, and monitoring for the WUR-related downlink signal comprises monitoring for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

[0041] In one embodiment, frequency domain resources for WUR-related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain, and monitoring for the WUR-related downlink signal comprises monitoring for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

[0042] In one embodiment, frequency domain resources for WUR-related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain, and monitoring for the WUR-related downlink signal comprises monitoring for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

[0043] In one embodiment, frequency domain resources for WUR-related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE, and monitoring for the WUR-related downlink signal comprises monitoring for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

[0044] In one embodiment, frequency domain resources for WUR-related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUR-related downlink signals, and monitoring for the WUR-related downlink signal comprises monitoring for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

[0045] In one embodiment, the frequency domain resource are located at an edge of a respective downlink bandwidth part.

[0046] In one embodiment, the method further comprises receiving, from a network node, information that indicates or configures the time domain resources for WUR-related downlink signal monitoring. In one embodiment, the method further comprises receiving, from the network node (1002), information that indicates or configures frequency domain resources for WUR- related downlink signal monitoring.

[0047] In one embodiment, monitoring for the WUR-related downlink signal comprise monitoring for the WUR-related downlink signal via a WUR. In one embodiment, monitoring for the WUR-related downlink signal via the WUR comprises dynamically tuning one or more parameters of the WUR based on the time domain resources for WUR-related downlink signal monitoring. [0048] In one embodiment, the WUR-related downlink signal is a Wake-Up Signal, WUS, and the time-domain resources for WUR-related downlink signal monitoring are time-domain resources for WUS monitoring that are based on, or depend on, on e or more non-WUS related time-domain resource patterns.

[0049] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for WUR related downlink signal monitoring and detection is adapted to monitor for a WUR related downlink signal in time-domain resources for WUR related downlink signal monitoring, wherein the time domain resources for WUR related downlink signal monitoring are based on, or depend on, one or more non-WUR related downlink signal related time domain resource patterns.

[0050] In another embodiment, a UE for WUR related downlink signal monitoring and detection comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to monitor for a WUR related downlink signal in time-domain resources for WUR related downlink signal monitoring, wherein the time domain resources for WUR related downlink signal monitoring are based on, or depend on, one or more non-WUR- related downlink signal related time domain resource patterns.

[0051] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for WUR related downlink signal resource configuration and WUR related downlink signal transmission comprises determining time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR-related downlink signal related time domain resource patterns and transmitting, to a UE, information that indicates or configures the UE with the determined time-domain resources for WUR related downlink signal monitoring.

[0052] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for WUR related downlink signal resource configuration and WUR related downlink signal transmission is adapted to determine time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR related downlink signal related time domain resource patterns and transmit, to a UE, information that indicates or configures the UE with the determined time-domain resources for WUR related downlink signal monitoring.

[0053] In another embodiment, a network node for WUR related downlink signal resource configuration and WUR related downlink signal transmission comprises processing circuitry configured to cause the network node to determine time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR related downlink signal related time domain resource patterns and transmit, to a UE, information that indicates or configures the UE with the determined time-domain resources for WUR related downlink signal monitoring.

BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0055] Figure 1 is an illustration of location of a Wake-Up Signal (WUS) and a Paging Occasion (PO) to which it is associated;

[0056] Figure 2 illustrates an example User Equipment (UE) including a main receiver and a dedicated Wake-Up Receiver (WUR);

[0057] Figure 3 is an illustration of WUS for Narrowband Internet of Things (NB-IoT) and Long Term Evolution for Machine Type Communication (LTE-M);

[0058] Figure 4 illustrates the time domain structure of a Synchronization Signal Block (SSB) as defined in 3^rd Generation Partnership Project (3GPP) specifications;

[0059] Figure 5 illustrates examples of non-contiguous WUS resources (within a slot or over multiple slots), in accordance with some embodiments of the present disclosure;

[0060] Figure 6 illustrates an example embodiment in which WUS is located outside a configured downlink bandwidth part (BWP) (e.g., the initial BWP) with a specific frequency offset;

[0061] Figure 7 illustrates an example embodiment in which WUS Resource Blocks (RBs) are within a downlink BWP excluding SSB RBs;

[0062] Figure 8 illustrates an example embodiment in which there are multiple bitmaps at RB-level, slot-level, subcarrier-level, and symbol-level for indicating WUS resources;

[0063] Figure 9 illustrates an example of Power Spectral Density (PSD) relation to the guard band size, in accordance with some embodiments of the present disclosure;

[0064] Figure 10 illustrates the operation of a UE and a network node in accordance with at least some embodiments of the present disclosure;

[0065] Figure 11 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0066] Figure 12 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure;

[0067] Figure 13 shows a network node in accordance with some embodiments of the present disclosure; and [0068] Figure 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

DETAILED DESCRIPTION

[0069] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0070] 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.

[0071] There currently exist certain challenge(s). The support of Wake-Up Receivers (WURs) in the network requires new signaling such as Wake-Up Signals (WUSs) and synchronization signals. That is, the network needs additional transmissions for supporting User Equipments (UEs) equipped with a WUR. However, the coexistence of such new signals with other existing signals and channels (i.e., legacy transmissions such as synchronization signals, reference signals, control channels) can be challenging without proper scheduling and resource allocation solutions. In addition, there can be negative system impacts in terms of network overhead, network energy efficiency, and capacity.

[0072] Regarding 3^rd Generation Partnership Project (3GPP) study, in RAN4#104-bis-e, the following tentative agreement was reached:

RAN4 use guard RBs (if needed) for LP-WUS, which is Granularity of RB. The traditional guardband for NR channel bandwidth defined in TS 101-1 should not be changed.

For case when WUS is smaller than NR channel bandwidth

For case 2-1, the LP-WUS guard RB is number RBs between LP-WUS and NR signals (edge of WUR RB location to nearest edge of eMBB RB)

For case 2-2, the WUS is placed at the edge of the NR channel bandwidth, i.e. the lowest/highest RB of WUS with guard RBs is aligned with the lowest/highest NR transmission bandwidth configuration in spec.

[For case when the WUS/WUR is same as NR channel bandwidth] For case 1, the LP-WUS guard RBs is number RBs between LP-WUS and traditional guardband (edge of WUR RB location to Outermost of NRB)

FFS whether the guard RBs should be symmetric within the WUS channel bandwidth

The solution on how to design the guard Resource Block (RB) for the For Future Study (FFS) item above is needed.

[0073] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed that provide efficient resource allocation and scheduling schemes and configurations to ensure efficient coexistence of WUS with other transmissions and proper support of WUR in a network. Specifically, the embodiments of the present disclosure prevent collision between new signals for supporting WUR and existing signals and channels (i.e., legacy transmissions such as synchronization signals, reference signals, control channels) in a cell (i.e., prevent intra-cell interference). Embodiments are disclosed that cover aspects related to time-frequency resources, periodicity of the transmissions, relation of new signals with legacy signals and channels, power control, indications, and configurations. Specifically, embodiments of the present disclosure may include any one or more of the following:

• Time domain pattern for WUS resources is determined based on the time domain pattern of at least one non- WUS transmission such as the Synchronization Signal Block (SSB), common Physical Downlink Control Channel (PDCCH) search space (e.g., in Control Resource Set (CORESET) #0), and downlink reference signals (e.g., Demodulation Reference Signal (DM-RS), Phase Tracking Reference Signal (PTRS), Channel State Information Reference Signal (CSI-RS), Tracking Reference Signal (TRS)). Both contiguous and non-contiguous WUS time-domain resources are proposed.

• Different frequency positions for WUS with respect to frequency locations of existing signals and channels as well as bandwidth part (BWP) configurations are proposed.

• Details of configurations/indication of WUS resource allocation are presented including a new multiple bitmap approach.

• Adaptive WUS power adjustment based on WUS parameters, UE capabilities, receiver architecture/parameters.

• Defining the relationship between Power Spectral Density (PSD) characteristics, size of guard band, and receiver filter parameters. The transmit power adjustment (e.g., power boosting level) is determined as function of size of guardband and receiver filter parameters. In the case where there is a need to allocate additional guard RB(s) between a WUS signal and other non-WUS transmissions (e.g., enhanced Mobile Broadband (eMBB) signal), the size of the guard RB can be decided by any one or more of the following factors: o The relative PSD difference between a WUS signal and eMBB RB which is closest to the WUS signal. o The PSD difference between the eMBB RB closest to WUS signal at one side of the WUS signal and eMBB signal closest to a WUS signal at the other side of the signal o The filter order implemented at wake up receiver o The modulation order of the eMBB RB closest to the WUS signal at either side [0074] In one embodiment, systems and methods are disclosed herein that enable the guard RB size to be big enough to allow the wake-up receiver implementing a low order filter to save both cost and power. At the same time, the guard band RB is kept as small as possible so the other UE(s) can be scheduled at the same time, so as to improve the spectrum efficiency. Embodiments of the present disclosure provide a solution(s) on the tradeoff between easing the WUR receiver cost/power and spectrum efficiency.

[0075] Certain embodiments may provide one or more of the following technical advantage(s):

• Ensuring efficient coexistence of WUS with other transmissions and proper support of WUR in a network;

• Efficient coexistence of legacy UEs with new UEs equipped with WUR;

• Efficient resource allocation considering system impacts, network overhead, and network energy consumption;

• Network flexibility for properly employing WUR based on various requirements such coverage, energy efficiency, and latency;

• The solutions can be considered as a key enabler of battery-less (zero-energy) devices and energy harvesting operations towards 5G Advanced and 6G.

[0076] Various patterns of time-frequency resources for Wake-Up Signals (WUS) and any other transmissions for supporting Wake-Up Receivers (WUR) are disclosed herein. In addition, embodiments related to power control and configuration aspects are also disclosed.

[0077] In one embodiment, the patterns of time-frequency resources and transmit power for new transmissions for supporting WUR (such as WUS, low-power synchronization signal (EPSS)) are determined based on the patterns of existing signals and channels (such as legacy transmissions for reference signals, control channels). Specifically, to ensure efficient coexistence between different transmissions and minimize impact on the legacy operations, at least the following cases can be envisioned:

• Overlap in time and/or frequency resources for WUR-related transmissions and other existing transmissions in the cell is avoided or minimized (intra-cell interference);

• Transmit power of WUR-related transmissions is dynamically adjusted to minimize impact on other existing transmissions based on several factors such as WUS parameters (e.g., WUS bandwidth), size of WUS guard band, UE capability, receiver architecture, and frequency positions of WUS and other non- WUS transmissions.

[0078] In the following, the term “WUS" is used as a non-limiting example of WUR-related downlink transmissions. One example of another WUR-related downlink transmission to which embodiments of the present disclosure are applicable is the new Low-Power Synchronization Signal (LP-SS), which is received by the WUR.

1 Time-Domain Pattern

[0079] In one embodiment, the time domain resources for WUS are determined based on the time domain pattern of at least one of the following: SSB, common PDCCH search space (e.g., in CORESET#0), and one or more downlink reference signals (e.g., DM-RS, PTRS, CSLRS, and/or TRS). In one embodiment, the time domain resources for WUS are determined such that overlap between the WUS and SSB, common PDCCH search space, and/or downlink reference signals (e.g., DM-RS, PTRS, CSI-RS, and/or TRS) is avoided to minimize intra-cell interference.

[0080] Considering that WUS duration can span over several symbols and slots to provide sufficient coverage, a non-contiguous time-domain pattern for WUS might be needed to avoid overlap with other transmissions. Note that each slot is composed of 14 consecutive OFDM symbols in 5G NR. In one embodiment, WUS symbols within a slot are non-contiguous.

[0081] In another embodiment, WUS slots are non-contiguous (e.g., slots 1 and 3 are used for WUS transmissions but slot 2 is not). In another embodiment, both WUS symbols within a slot and over multiple slots can be non-contiguous to accommodate the existence of different transmissions, as illustrated in Figure 5. Figure 5 illustrates examples of non-contiguous WUS resources (within a slot or over multiple slots).

[0082] In another embodiment, whether time domain WUS resources are contiguous or noncontiguous depends on the WUS duration and presence of other transmissions. For example, whether the time domain WUS resources are contiguous or non-contiguous depends on any one or more of the following: • If WUS duration is less than K symbols, WUS transmission is contiguous otherwise it is non-contiguous. K is, for example, a predefined or configured number of symbols. In one embodiment, K is an integer value. In one embodiment, K is a positive integer value. In one embodiment, K is a non-zero integer value or non-zero positive integer value.

• In slots where any of SSB, reference signals, or common PDCCH transmissions are present, WUS resources are non-contiguous. Otherwise, WUS resources are contiguous.

• If a symbol is not available due to legacy transmission, the next generation NodeB (gNB) postpones WUS transmissions. In this case, WUS resource allocation is adaptive considering legacy transmissions, so the WUS does not have to be punctured.

[0083] In another embodiment, WUS is not present in the first N symbols of each slot. That is, the first N symbols of each slot are reserved for other non-WUS transmissions (e.g., for PDCCH). Some examples for values of N are { 1, 2, 3}.

[0084] In another embodiment, WUS is not present in the last N symbols of each slot. That is, the last N symbols of each slot are reserved for other non-WUS transmissions. Some examples for values of N are { 1 , 2, 3 } .

[0085] In another embodiment, the WUR can dynamically tune its parameters depending on whether a WUS slot is expected or not in order to reduce power consumption during a non-WUS slot. For example, this may include any one or more of the following:

• Depending on latency requirement, different Local Oscillator (LO) sources with different levels of accuracy and power consumption can be selected via a switch. When a WUS slot is expected, a more accurate and more power hungry LO can be selected, while during a non-WUS slot, an LO with lower accuracy and lower power consumption can be selected.

• Different gain settings (e.g., bias) of the RF Low Noise Amplifier (LNA) can be selected depending on if a WUS slot or a non-WUS slot is detected.

• 1 -bit or N-bit ADC can be selected via a switch depending on if a WUS slot or a non-WUS slot is detected.

[0086] In one specific example, the WUS resources depend on the pattern of SSB burst sets in time domain. An SSB burst set consists of one or more SSBs which is always confined to a 5 ms window and is either located in first-half or in the second-half of a 10 millisecond (ms) radio frame. Also, the start symbol of each SSB within an SSB burst is known based on the configuration. In one embodiment, to avoid impact on SSB transmissions, WUS can be transmitted either in the first half or second half of a radio frame where SSBs are not present. In another embodiment, WUS is transmitted over unused symbols between SSBs within a burst set. For SSB configuration Case A (15 kilohertz (kHz) subcarrier spacing (SCS), below 3 GHz carrier), start symbols of four SSBs are {2,8,16,22} over two slots. In this case, considering SSB duration of 4 symbols, WUS can be transmitted on symbols { 1, 6,7,12, 13, 14, 15, 20, 21, 26, 27, 28} over two slots.

[0087] In another embodiment, WUS is not transmitted in symbols allocated to DMRS transmissions which depend on the DMRS mapping type. For example, for DMRS mapping type

A, the first DMRS symbol starts in the 3rd or 4th OFDM symbol in the slot. For DMRS mapping type B, the first DMRS symbol starts in the 1st OFDM symbol in the PDSCH (mini-slot) or if it collides with PDCCH then it can be moved to the first later symbol after the PDCCH.

[0088] In one example, to avoid overlap with DMRS, WUS is not transmitted in the 3rd or 4th OFDM symbol in the slot for DMRS mapping type A. In another example, to avoid overlap with DMRS, WUS is not transmitted in the 1st OFDM symbol in the slot for DMRS mapping type

B. In another example, WUS is not transmitted in the first symbol after the PDCCH.

[0089] Another reference signal which needs to be protected is TRS. In FR1 , the TRS symbols within a slot can be {5^th, 9^th}, or {6^th, 10^th }, or {7^th , 10^th} symbol of the slot. Also, the periodicity of TRS can be { 10, 20, 40, 80} ms. In one embodiment, the WUS is not transmitted in symbols assigned to TRS. For example:

• WUS is not transmitted in {5^th, 9^th} symbols of a slot

• WUS is not transmitted in {6^th, 10^th} symbols of a slot

• WUS is not transmitted in {7^th, 11^th} symbols of a slot

• Based on the periodicity of TRS, WUS is not transmitted in slots in which TRS can be present.

[0090] In another embodiment, WUS is not transmitted in symbols allocated to semi- statically configured transmissions with higher priority, e.g., downlink semi-persistent scheduling transmission for Ultra-Reliable Low-Latency Communication (URLLC) purpose.

[0091] In one embodiment, the time domain resources used for WUS transmission/reception are determined based on a reserved resource pattern defined for WUS. The reserved resource pattern can be fixed in the specification or configured to the UE. In one example, the reserved resource pattern is defined as a set of OFDM symbols within a slot or M consecutive slots, repeated in every N slots, where M=l, 2, . . . and N = 1, 2, . . ., and M < N. In another example, the reserved resource pattern is defined as a repeated subset of K slots out of N consecutive slots symbols.

[0092] When WUS time domain resources overlap with a symbol or a slot which belongs to the reserved resource pattern, WUS is not transmitted in the symbol or the slot. In one embodiment, the time domain resources used for WUS transmission/reception are determined based on a combination (union) of the reserved resource pattern and the time domain pattern of at least one of the SSB, search space sets for common PDCCH (e.g., in CORESET#0), and downlink reference signals (DM-RS, PTRS, CSI-RS, TRS).

[0093] In general, the time domain WUS pattern can be a function of WUS design. For example, coding schemes such as Manchester encoding, and repetitions, WUS data rate (number of WUS symbols/segments within one OFDM symbol. For example, M-OOK means M segments are transmitted within one OFDM symbol). In one embodiment, the WUS time domain pattern depends on:

• Whether Manchester encoding is used o with Manchester encoding bit 1 is mapped to [0,1] and bit 0 is mapped to [1,0]. Hence, the number of WUS symbols is always even.

• Time repetition factor

• Number of WUS symbols transmitted within each OFDM symbol and WUS pay load

2 Frequency-Domain Pattern

[0094] In some embodiments, there can be different frequency positions for WUS with respect to frequency locations of existing signals and channels as well as bandwidth part (BWP) configurations.

[0095] In one embodiment, WUS is located within the bandwidth of the initial BWP.

[0096] In another embodiment, WUS is located outside of the bandwidth of the initial downlink BWP. In this case, there can be a specific frequency offset between the position of initial BWP and WUS frequency position, as shown in Figure 6 which illustrates an example embodiment in which WUS is located outside the BWP with a specific frequency offset. For example, the start RB of WUS is located K RBs after the highest RB of the initial BWP. In one embodiment, K is a predefined or configured value. In one embodiment, K is an integer value. In one embodiment, K is a positive integer value. In one embodiment, K is a non-zero integer value or non-zero positive integer value. In another example, the end RB of WUS is located K RBs before the lowest RB of the initial BWP.

[0097] In an alternative to the above, a separate initial DE BWP is configured for WUS monitoring as part of the WUS configuration (e.g., in system information (SI)). Whenever the UE uses the WUR for DL monitoring, it monitors in the WUS initial DL BWP; and when the UE uses the main receiver, it monitors in the legacy initial DL BWP. The bandwidth of the WUS initial DL BWP is, in one embodiment, implicitly configured to be the same as the WUS bandwidth (either fixed, determined from the SCS, or configurable). In one example, a separate initial DL BWP is configured for WUS as shown below (additions in bold): DownlinkConfigCommon information element

- ASN1 START

- TAG-DOWNLINKCONFIGCOMMON-START

DownlinkConfigCommon ::= SEQUENCE { frequencylnfoDL Frequency! nfoDL OPTIONAL, - Cond InterFreqHOAndServCellAdd initialDownlinkBWP BWP-DownlinkCommon OPTIONAL, -- Cond ServCellAdd initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL, -- Need R initialDownlinkBWP-LPWUS-r19 BWP-DownlinkCommon OPTIONAL -- Need R

- TAG-DOWNLINKCONFIGCOMMON-STOP

- ASN1STOP

[0098] In another example, only frequency allocation and the WUS bandwidth needs to be configured, in this case indicated by the RIV in BWP (reusing legacy format) as shown below:

DownlinkConfigCommon information element

- ASN1 START

- TAG-DOWNLINKCONFIGCOMMON-START

DownlinkConfigCommon ::= SEQUENCE { frequencylnfoDL FrequencylnfoDL OPTIONAL, - Cond

InterFreqHOAndServCellAdd

InitialDownlinkBWP BWP-DownlinkCommon OPTIONAL, - Cond ServCellAdd initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL, - Need R lpWus-Config-r19 LpWus-Config-r19 OPTIONAL - Need R

- TAG-DOWNLINKCONFIGCOMMON-STOP

- ASN1STOP

LpWus-Config information element

- ASN1 START

- TAG-LpWus-Config-START

LpWus-Config ::= SEQUENCE ! genericWusParameters BWP - TAG-LpWus-Config-STOP

- ASN1STOP

[0099] In another embodiment, WUS is located within an initial downlink BWP but it does not overlap with SSB in frequency domain. In another embodiment, WUS does not overlap with CORESET#0 in frequency domain. In any of these cases, a frequency offset between WUS and SSB or CORESET#0 can be configured.

[0100] In another embodiment, WUS can be located in any RBs within the initial downlink BWP excluding physical resource blocks used for SSB, e.g., see Figure 7 which illustrates an example embodiment in which WUS RBs within a downlink BWP excluding SSB RBs.

[0101] In one example, WUS RBs are contiguous. In another example, WUS RBs are noncontiguous.

[0102] In one embodiment, WUS is located at one edge of the downlink BWP (either high edge [higher frequency] or low edge [lower frequency]). In another embodiment, WUS can be located at any of the downlink BWP edges. That is, WUS occupies the first N RBs and/or the last M RBs of downlink BWP RBs.

[0103] Any of the above embodiments can depend on:

• WUS bandwidth,

• UE maximum supported bandwidth,

• Carrier bandwidth,

• Subcarrier spacing for WUS and other transmissions,

• UE capabilities WUR architecture,

• WUS modulation.

3 Configurations/Indication of WUS Resource Allocation

[0104] In one embodiment, time-domain and/or frequency-domain resources for wake-up signals (WUS) are configured and/or indicated to a UE.

[0105] In one embodiment, a pair of time domain resource and frequency domain resource (in number of Physical Resource Blocks (PRBs), including the starting PRB) are configured to the UE to be used for WUS reception.

[0106] In another embodiment, multiple pairs of time domain and frequency domain resources are configured to the UE. The UE is further indicated which time and frequency domain resources to use for WUS reception. [0107] In one example, the indicated time domain and frequency domain resources is used for N subsequent WUS receptions (counting from the first WUS reception after the indication), after which a new indication is provided to the UE. The value of N may be predefined or configured. In one embodiment, the value of N is a positive integer value that is greater than or equal to 1.

[0108] In another example, the indicated time domain and frequency domain resources is used for all subsequent WUS receptions (counting from the first WUS reception after the indication) unless there is a new indication provided to the UE.

[0109] In another example, time and frequency domain resources are indicated to the UE for each WUS reception.

[0110] In one embodiment, the time domain resource for a WUS transmission/reception is defined by a starting OFDM symbol and a duration/length of WUS in terms of consecutive OFDM symbols. Different examples are provided below:

• WUS time domain resource #1: starting OFDM symbol = 0, duration = 14 symbols

• WUS time domain resource #2: starting OFDM symbol = 0, duration = 28 symbols (in this example, WUS time domain resource starts at OFDM symbol number 0 of the first slot and lasts until the end of the second slot)

• WUS time domain resource #3: starting OFDM symbol = 3, duration = 12 symbols (in this example, WUS time domain resource starts at OFDM symbol number 3 of the first slot and lasts until the end of the slot)

[0111] In one embodiment, the time domain resource for a WUS transmission/reception is defined by a set of OFDM symbols within a slot and the number of consecutive slots it occupies. Different examples are provided below:

• WUS time domain resource #4: bitmap indicating OFDM symbols in a slot to use for WUS = [0 0 1 1 1 1 1 1 1 1 1 1 0 0], number of slots = 2 (in this example, WUS time domain resource consists of OFDM symbol number 2-11 in two consecutive slots. That is, WUS time domain resource is not contiguous, e.g., there are some OFDM symbol gap between time resources of the two slots.)

[0112] In one embodiment, the frequency domain resource for a WUS transmission/reception is defined by a starting PRB (RB_sLarL ) and a duration/length in terms of consecutive PRBs (N_RB ). The starting PRB is defined in relation to starting PRB of the associated BWP in which WUS is transmitted/received. The duration needs satisfy: 1 < N_RB < N_B^^l _P — RB_start, where N_B^^L ,^e _R is the size of associated BWP in which WUS is transmitted/received.

[0113] In another embodiment, the frequency domain resource for a WUS transmission/reception is defined by a bitmap indicating a subset of PRBs within the associated BWP in which WUS is transmitted/received. Each bit in the bitmap can represent one or more PRBs (note: RB and PRB are used interchangeably). In this case, the frequency domain resource for WUS is not necessarily contiguous.

[0114] In a more general embodiment, multiple bitmaps are used to indicate WUS resources at symbol- level, slot-level, subcarrier-level, and PRB -level. Figure 8 illustrates an example in which there are multiple bitmaps at RB-level, slot-level, subcarrier-level, and symbol-level for indicating WUS resources. As illustrated in the example of Figure 8:

• Bitmap 1: indicates WUS slots in a frame or any defined duration

• Bitmap 2: indicates WUS symbols in a slot

• Bitmap 3: indicates WUS PRBs in a carrier bandwidth or BWP or any defined bandwidth

• Bitmap 4: indicates WUS subcarriers within a PRB

[0115] Different granularities can be defined for time-frequency resource indication. For example:

• PRB granularity can be { 1 , 2, 4, 6 } .

• Subcarrier granularity can be { 1, 2, 4, 6}

• Slot granularity can be { 1 , 2, 4, 5 }

• Symbol granularity can be { 1, 2, 7}

[0116] In another embodiment, only reserved resources which are not used for WUS transmissions are indicated while remaining resources can be used for WUS. For example, indices of symbols and/or PRBs not usable for WUS is indicated via start and number of the resources.

[0117] The UE receives WUS based on the configured/indicated time-domain and frequencydomain resources for WUS, in combination with the time and frequency domain patterns described in Sections 1 and 2 of the Detailed Description. That is, when the WUS time and/or frequency domain resources overlap with a symbol/slot/PRB in the time and frequency domain patterns described in Sections 1 and 2 of the Detailed Description, WUS is not transmitted on the symbol/slot/PRB. Note that WUS is still transmitted on other remaining symbols/slots/PRBs of the configured/indicated time-domain and frequency-domain resources for WUS.

4 WUS Power Adjustment

[0118] In some embodiments, considering the coverage limitations of WUS and methods of generating WUS with an OFDM transmitter, power boosting in the WUS bandwidth can be applied.

[0119] In one embodiment, power boosting is applied only to certain RBs from the WUS bandwidth considering the impact on adjacent channels. For example, only the L RBs located in the middle of the WUS bandwidth are power boosted. In one embodiment, the value of L is predefined or configured. In one embodiment, the value of L is a positive integer that is greater than or equal to 1. In another embodiment, power boosting is not applied to N RBs located at the edges of the WUS bandwidth. In one embodiment, the value of N is predefined or configured. In one embodiment, the value of L is a positive integer that is greater than or equal to 1.

[0120] In another embodiment, whether power boosting is applied or the level of boosting (e.g., 3 dB or 6 dB) for WUS transmissions depend on the presence of other signals and channels. [0121] In some cases, in order to minimize the impact on other non-WUS transmissions, a proper power control (i.e., increasing/boosting or decreasing) needs to be applied. Examples of power control values are {-6 dB, -3 dB, 0 dB, 3 dB, 6 dB, 9 dB }. The power control scheme depends on the frequency position of WUS and non-WUS transmissions as well as time-frequency overlaps between them. For example, in symbols containing legacy reference signals (or synchronization, control channels) WUS power boosting is not applied or even WUS power is reduced.

[0122] In another embodiment, the power boosting level depends on the frequency separation of WUS and other important aforementioned signals/channels. For example, WUS power boosting is applied if the frequency separation of WUS and SSB is greater than X MHz.

[0123] In another embodiment, the power boosting level depends on the scheduling of neighboring bands. Higher boosting values are selected when neighboring bands are not transmitting while lower values are selected when they are fully occupied.

[0124] In addition, there is a relationship between power spectral density (PSD) characteristics, size of guardband, and receiver filter parameters (see, e.g., Figure 9 which illustrates an example of PSD relation to the guard band size). The transmit power adjustment (e.g., power boosting level) is determined as function of size of guardband and receiver filter parameters.

[0125] In another embodiment, the guard RB size between the WUS signal and other non- WUS transmissions (e.g., eMBB signals) can be determined by the below factors:

1. The relative PSD (Power spectrum density) difference between a WUS signal and eMBB RB which is closest to the WUS signal. (APSD1 and APSD3 in Figure 9)

2. The PSD difference between the eMBB RB closest to WUS signal at one side of the WUS signal and eMBB signal closest to a WUS signal at the other side of the signal (APSD1 in Figure 9)

3. The filter order implemented at wake up receiver

4. The modulation order of the eMBB RB closest to the WUS signal at either side [0126] As one example, the guard RB size is dynamically determined by the scheduled eMBB RB which is nearest to a WUS signal. As the factors determine the guard RB size is changing, so does the guard RB size.

[0127] Another example, the guard RB size can be kept the same, but scheduler at network side should not schedule the higher PSD signal than a WUS signal at both side of WUS signal, [0128] As another example, with WUR filter order is N and the guard RB size M is considered when there is no PSD difference between eMBB signal and WUS signal. When APSD2 and APSD3 are greater than zero, the guard RB size M is scaled in relation to the WUR filter order. Specifically, the size of guard band increases more for lower order filters to suppress the adjacent channel interference.

[0129] As another example, the guard RB size may cover the transition band of WUR filter , therefore the size of guard RB may relate to the WUR filter order. The additional PSD between eMBB signal will contribute more noise to the wake up receiver and thus increasing the guard RB is needed.

5 Further Description

[0130] Figure 10 illustrates the operation of a UE 1000 and a network node 1002 in accordance with at least some of the embodiments described above (e.g., in Sections 1-4 of the Detailed Description). The network node 1002 is, in one embodiment, a RAN node such as, e.g., a base station or a RAN node that performs at least some of the functionality of a base station (e.g., a Distributed Unit (DU) or Central Unit (CU) of a base station (e.g., a gNB) having a distributed architecture including a CU and one or more DUs. Note that optional steps are represented in Figure 10 by dashed lines/boxes.

[0131] As illustrated, the network node 1002 determines time-domain resources for WUS based on one or more non-WUS related time domain resource patterns (step 1004). This determination is made in accordance with any of the embodiments related to determining the time domain resources or pattern for WUS described above (e.g., in Section 1 of the Detailed Description).

[0132] In one embodiment, the one or more non-WUS related time domain resource patterns (based on which the time domain resources for WUS are determined) comprise one or more time domain patterns for one or more non-WUS downlink transmissions. In one embodiment, the one or more non-WUS downlink transmissions comprise SSB transmissions. In one embodiment, the one or more non-WUS downlink transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types. In one embodiment, the one or more downlink reference signal types comprise any one or more of: DMRS, PTRS, CSI-RS, and TRS.

[0133] In one embodiment, the one or more non-WUS related time domain resource patterns (based on which the time domain resources for WUS are determined) comprise a time domain resource pattern for a common PDCCH search space, e.g., in CORESET#0.

[0134] In one embodiment, the time domain resources for WUS are further based on, or depend on, a reserved time domain resource pattern.

[0135] In one embodiment, the time domain resources for WUS are contiguous in time. IN another embodiment, the time domain resources for WUS are non-contiguous in time. In another embodiment, the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS. In another embodiment, the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS and whether non-WUS related transmission(s) are present.

[0136] In one embodiment, the time domain resources for WUS are such that WUS is not present in a first N symbols of each slot. In another embodiment, the time domain resources for WUS are such that WUS is not present in a last N symbols of each slot.

[0137] Further details about the determined time-domain resources for WUS and how they are determined are described above, e.g., in Section 1 of the Detailed Description and those details are equally applicable here.

[0138] Optionally, the network node 1002 also determines frequency domain resources for WUS (step 1006). This determination is made in accordance with any of the embodiments related to determining the frequency domain resources for WUS described above (e.g., in Section 2 of the Detailed Description). In one embodiment, the frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE. In another embodiment, the frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain. In another embodiment, the frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain. In another embodiment, the frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE. In another embodiment, the frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUS. In one embodiment, the frequency domain resource are located at an edge of a respective downlink bandwidth part. [0139] The network node 1002 transmits, to the UE 1000, information (e.g., one or more time domain resource parameters in the illustrated example) that indicates or configures the UE 1000 with the determined time domain resources for WUS and, optionally, information (e.g., one or more frequency domain resource parameters in the illustrated example) that indicates or configures the UE 1000 with the determined frequency domain resources for WUS (step 1008). Further details regarding the configuration or indication of the WUS resource allocation (time and, optionally, frequency resource allocation) are provided above, e.g., in Section 3 of the Detailed Description and those details are equally applicable here.

[0140] At the UE 1000, the UE 1000 monitors (e.g., via a WUR of the UE 1000) for a WUS in the time-domain resources for WUS (step 1010). As stated above, the time domain resources for WUS are based on, or depend on, one or more non- WUS related time domain resource patterns in accordance with any of the embodiments related to determining the time domain resources or pattern for WUS described above (e.g., in Section 1 of the Detailed Description). Optionally, the resources monitored for a WUS include time and frequency resources for WUS (e.g., an intersection of the time resources as determined in step 1004 and the frequency resources as determined in step 1006), e.g., as determined in steps 1004 and 1006 and indicated to the UE 1000 in step 1008.

[0141] At the network node 1002, the network node 1002 refrains from transmitting WUS in resources other than those in the determined time and frequency domain resources for WUS (step 1012). Further details are described above and are equally applicable here. In this example, while the UE 1000 monitors for WUS in step 1010, the network node 1002 transmits, and the UE 1000 detects, a WUS (steps 1014 and 1010A) and, in response, the UE 1000 (e.g., the WUR of the UE 1000) wakes-up a main receiver of the UE 1000 (step 1016). Note that, in some embodiments, the network node 1002 applies power boosting in relation to at least some RBs used for the WUS transmission in step 1014 as described above, e.g., in Section 4 of the Detailed Description.

[0142] Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.

[0143] In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a Radio Access Network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110A and 1110B (one or more of which may be generally referred to as network nodes 1110), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1102, including one or more network nodes 1110 and/or core network nodes 1108.

[0144] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1110 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1112A, 1112B, 1112C, and 1112D (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.

[0145] 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 1100 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 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

[0146] The UEs 1112 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 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1112 and/or with other network nodes or equipment in the telecommunication network 1102 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 1102.

[0147] In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. 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 1106 includes one more core network nodes (e.g., core network node 1108) 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 1108. 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 (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0148] The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 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.

[0149] As a whole, the communication system 1100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1100 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0150] In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunication network 1102 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 Internet of Things (loT) services to yet further UEs.

[0151] In some examples, the UEs 1112 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 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0152] In the example, a hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112C and/or 1112D) and network nodes (e.g., network node 1110B). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 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 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 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 1114 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0153] The hub 1114 may have a constant/persistent or intermittent connection to the network node 1110B. The hub 1114 may also allow for a different communication scheme and/or schedule between the hub 1114 and UEs (e.g., UE 1112C and/or 1112D), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and/or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 1104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 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 1110B. In other embodiments, the hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 1110B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0154] Figure 12 shows a UE 1200 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0155] 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).

[0156] The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, memory 1210, a communication interface 1212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 12. 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.

[0157] The processing circuitry 1202 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 1210. The processing circuitry 1202 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 1202 may include multiple Central Processing Units (CPUs).

[0158] In the example, the input/output interface 1206 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 1200. 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.

[0159] In some embodiments, the power source 1208 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 1208 may further include power circuitry for delivering power from the power source 1208 itself, and/or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.

[0160] The memory 1210 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems.

[0161] The memory 1210 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (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 a ‘SIM card.’ The memory 1210 may allow the UE 1200 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 1210, which may be or comprise a device-readable storage medium.

[0162] The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 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 1218 and/or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., the antenna 1222) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0163] In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0164] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, 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). [0165] 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.

[0166] A UE, when in the form of an loT 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 loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 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 loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in Figure 12.

[0167] As yet another specific example, in an loT 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, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0168] 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.

[0169] Figure 13 shows a network node 1300 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0170] 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, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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).

[0171] 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 BS 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).

[0172] The network node 1300 includes processing circuitry 1302, memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 1300 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 NodeB s. 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 1300 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 1300.

[0173] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1300 components, such as the memory 1304, to provide network node 1300 functionality.

[0174] In some embodiments, the processing circuitry 1302 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of Radio Frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 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 the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0175] The memory 1304 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, RAM, 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 1302. The memory 1304 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 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and/or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and the memory 1304 are integrated.

[0176] The communication interface 1306 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 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. The radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to the antenna 1310 and the processing circuitry 1302. The radio front-end circuitry 1318 may be configured to condition signals communicated between the antenna 1310 and the processing circuitry 1302. The radio front-end circuitry 1318 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 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1320 and/or the amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface 1306 may comprise different components and/or different combinations of components.

[0177] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318; instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes the one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312 as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0178] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

[0179] The antenna 1310, the communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1300. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node 1300. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.

[0180] The power source 1308 provides power to the various components of the network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 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.

[0181] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 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 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

[0182] Figure 14 is a block diagram illustrating a virtualization environment 1400 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 1400 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. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. [0183] Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

[0184] Hardware 1404 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 1406 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1408A and 1408B (one or more of which may be generally referred to as VMs 1408), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.

[0185] The VMs 1408 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of the VMs 1408, 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.

[0186] In the context of NFV, a VM 1408 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 1408, and that part of the hardware 1404 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1408, 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 1408 on top of the hardware 1404 and corresponds to the application 1402.

[0187] The hardware 1404 may be implemented in a standalone network node with generic or specific components. The hardware 1404 may implement some functions via virtualization. Alternatively, the hardware 1404 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 1410, which, among others, oversees lifecycle management of the applications 1402. In some embodiments, the hardware 1404 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 RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0188] 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.

[0189] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired 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.

[0190] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0191] The following embodiments describe some implementations of the solutions described herein. Combinations of these embodiments are also within the scope of the invention.

Group A Embodiments:

[0192] Embodiment 1: A method performed by a User Equipment, UE, (1000) for Wake-Up Signal, WUS, monitoring and detection, the method comprising: monitoring (1010) for a WUS in time-domain resources for WUS, wherein the time domain resources for WUS are based on, or depend on, one or more non-WUS related time domain resource patterns.

[0193] Embodiment 2: The method of embodiment 1, wherein the one or more non-WUS related time domain resource patterns comprise one or more time domain patterns for one or more non-WUS downlink transmissions.

[0194] Embodiment 3: The method of embodiment 2, wherein the one or more non-WUS downlink transmissions comprise SSB transmissions.

[0195] Embodiment 4: The method of embodiment 2 or 3, wherein the one or more non- WUS downlink transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types.

[0196] Embodiment 5: The method of embodiment 4, wherein the one or more downlink reference signal types comprise any one or more of: DMRS, PTRS, CSI-RS, and TRS.

[0197] Embodiment 6: The method of any of embodiments 1 to 5, wherein the one or more non-WUS related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space.

[0198] Embodiment 7: The method of any of embodiments 1 to 5, wherein the one or more non-WUS related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space in Control Resource Set, CORESET, #0.

[0199] Embodiment 8: The method of any of embodiments 1 to 7, wherein the time domain resources for WUS are further based on, or depend on, a reserved time domain resource pattern.

[0200] Embodiment 9: The method of any of embodiments 1 to 8, wherein the time domain resources for WUS are contiguous in time. [0201] Embodiment 10: The method of any of embodiments 1 to 8, wherein the time domain resources for WUS are non-contiguous in time.

[0202] Embodiment 11 : The method of any of embodiments 1 to 8, wherein the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS.

[0203] Embodiment 12: The method of any of embodiments 1 to 8, wherein the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS and whether non- WUS related transmission(s) are present.

[0204] Embodiment 13: The method of any of embodiments 1 to 12, wherein the time domain resources for WUS are such that WUS is not present in a first N symbols of each slot.

[0205] Embodiment 14: The method of any of embodiments 1 to 12, wherein the time domain resources for WUS are such that WUS is not present in a last N symbols of each slot.

[0206] Embodiment 15: The method of any of embodiments 1 to 14, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE, and monitoring (1010) for WUS comprises monitoring (1010) for WUS in the time and frequency domain resources for WUS (e.g., in an intersection of the time domain resources for WUS and the frequency domain resources for WUS).

[0207] Embodiment 16: the method of any of embodiments 1 to 14, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain, and monitoring (1010) for WUS comprises monitoring (1010) for WUS in the time and frequency domain resources for WUS (e.g., in an intersection of the time domain resources for WUS and the frequency domain resources for WUS). [0208] Embodiment 17: The method of any of embodiments 1 to 14, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain, and monitoring (1010) for WUS comprises monitoring (1010) for WUS in the time and frequency domain resources for WUS (e.g., in an intersection of the time domain resources for WUS and the frequency domain resources for WUS).

[0209] Embodiment 18: The method of any of embodiments 1 to 14, wherein frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE, and monitoring (1010) for WUS comprises monitoring (1010) for WUS in the time and frequency domain resources for WUS (e.g., in an intersection of the time domain resources for WUS and the frequency domain resources for WUS). [0210] Embodiment 19: The method of any of embodiments 1 to 14, wherein frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUS, and monitoring (1010) for WUS comprises monitoring (1010) for WUS in the time and frequency domain resources for WUS (e.g., in an intersection of the time domain resources for WUS and the frequency domain resources for WUS).

[0211] Embodiment 20: The method of any of embodiments 15 to 19, wherein the frequency domain resource are located at an edge of a respective downlink bandwidth part.

[0212] Embodiment 21: The method of any of embodiments 1 to 20, further comprising receiving (1008), from a network node (1002), information that indicates or configures the time domain resources for WUS.

[0213] Embodiment 22: The method of embodiment 21, further comprising receiving (1008), from the network node (1002), information that indicates or configures frequency domain resources for WUS.

[0214] Embodiment 23: The method of any of embodiments 1 to 22, wherein monitoring (1010) for WUS comprise monitoring (1010) for WUS via a Wake-Up Receiver, WUR.

[0215] Embodiment 24: The method of embodiment 23, wherein monitoring (1010) for WUS via the WUR comprises dynamically tuning one or more parameters of the WUR based on the time domain resources for WUS.

[0216] Embodiment 25: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

[0217] Embodiment 26: A method performed by a network node (1002) for Wake-Up Signal, WUS, resource configuration and WUS transmission, the method comprising: determining (1004) time-domain resources for WUS based on one or more non-WUS related time domain resource patterns; and transmitting (1008), to a User Equipment, UE, (1000), information that indicates or configures the UE with the determined time-domain resources for WUS.

[0218] Embodiment 27: The method of embodiment 26, wherein the one or more non-WUS related time domain resource patterns comprise one or more time domain patterns for one or more non-WUS downlink transmissions.

[0219] Embodiment 28: The method of embodiment 27, wherein the one or more non-WUS downlink transmissions comprise SSB transmissions. [0220] Embodiment 29: The method of embodiment 27 or 28, wherein the one or more non-

WUS downlink transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types.

[0221] Embodiment 30: The method of embodiment 29, wherein the one or more downlink reference signal types comprise any one or more of: DMRS, PTRS, CSI-RS, and TRS.

[0222] Embodiment 31 : The method of any of embodiments 26 to 30, wherein the one or more non- WUS related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space.

[0223] Embodiment 32: The method of any of embodiments 26 to 30, wherein the one or more non- WUS related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space in Control Resource Set, CORESET, #0.

[0224] Embodiment 33: The method of any of embodiments 26 to 32, wherein the time domain resources for WUS are further determined based on, or depend on, a reserved time domain resource pattern.

[0225] Embodiment 34: The method of any of embodiments 26 to 33, wherein the time domain resources for WUS are contiguous in time.

[0226] Embodiment 35: The method of any of embodiments 26 to 33, wherein the time domain resources for WUS are non-contiguous in time.

[0227] Embodiment 36: The method of any of embodiments 26 to 33, wherein the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS.

[0228] Embodiment 37: The method of any of embodiments 26 to 33, wherein the time domain resources for WUS are either contiguous in time or non-contiguous in time, depending on a duration of the WUS and whether non- WUS related transmission(s) are present.

[0229] Embodiment 38: The method of any of embodiments 26 to 37, wherein the time domain resources for WUS are determined such that WUS is not present in a first N symbols of each slot.

[0230] Embodiment 39: The method of any of embodiments 26 to 37, wherein the time domain resources for WUS are determined such that WUS is not present in a last N symbols of each slot.

[0231] Embodiment 40: The method of any of embodiments 26 to 39, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUS.

[0232] Embodiment 41: The method of any of embodiments 26 to 39, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUS.

[0233] Embodiment 42: The method of any of embodiments 26 to 39, wherein frequency domain resources for WUS are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUS.

[0234] Embodiment 43: The method of any of embodiments 26 to 39, wherein frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUS.

[0235] Embodiment 44: The method of any of embodiments 26 to 39, wherein frequency domain resources for WUS are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUS, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUS.

[0236] Embodiment 45: The method of any of embodiments 40 to 44, wherein the frequency domain resource are located at an edge of a respective downlink bandwidth part.

[0237] Embodiment 46: The method of any of embodiments 26 to 45, further comprising transmitting (1014), to the UE (1000), a WUS in the determined time domain resources for WUS. [0238] Embodiment 47: The method of embodiment 46, wherein transmitting (1014) the WUS in the determined time domain resources for WUS comprises applying power boosting for at least some of the determined time domain resources for WUS used for transmission of the WUS. [0239] Embodiment 48: The method of embodiment 47, wherein power boosting is applied to only a certain number of RBs at a center of a bandwidth of the WUS.

[0240] Embodiment 49: The method of embodiment 47, wherein power boosting is applied to RBs other than a certain number of RBs at a center of a bandwidth of the WUS. [0241] Embodiment 50: The method of any of embodiments 47 to 49, wherein whether power boosting is applied or a level of power boosting applied depends on presence of other non-WUS transmissions.

[0242] Embodiment 51: The method of any of embodiments 47 to 49, wherein a level of power boosting applied depends on an amount of frequency separation between the WUS and other non-WUS transmissions.

[0243] Embodiment 52: The method of any of embodiments 47 to 49, wherein a level of power boosting applied depends on a scheduling of one or more neighboring frequency bands or one or more neighboring bandwidth parts.

[0244] Embodiment 53: The method of any of embodiments 46 to 52, wherein a guard band size between the WUS and one or more other non-WUS transmissions is based on any one or more of the following factors: a relative PSD (Power spectrum density) difference between the WUS signal and an eMBB RB which is closest to the WUS signal; a PSD difference between an eMBB RB of a first eMBB signal closest to WUS signal at one side of the WUS signal and an eMBB RB of a second eMBB signal closest to the WUS signal at the other side of the WUS signal; a filter order implemented at a wake up receiver of the UE; a modulation order of the eMBB RB closest to the WUS signal at either side of the WUS.

[0245] Embodiment 54: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Group C Embodiments

[0246] Embodiment 55: A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0247] Embodiment 56: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0248] Embodiment 57: A user equipment (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 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

1. A method performed by a User Equipment, UE, (1000) for Wake-Up Receiver, WUR, related downlink signal monitoring and detection, the method comprising: monitoring (1010) for a WUR related downlink signal in time-domain resources for WUR-related downlink signal monitoring, wherein the time domain resources for WUR-related downlink signal monitoring are based on, or depend on, one or more non- WUR-related downlink signal related time domain resource patterns.

2. The method of claim 1, wherein the one or more non- WUR-related downlink signal related time domain resource patterns comprise one or more time domain patterns for one or more non-WUR-related downlink signal transmissions.

3. The method of claim 2, wherein the one or more non-WUR-related downlink signal transmissions comprise Synchronization Signal Block, SSB, transmissions.

4. The method of claim 2 or 3, wherein the one or more non-WUR-related downlink signal transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types.

5. The method of claim 4, wherein the one or more downlink reference signal types comprise any one or more of: Demodulation Reference Signal, DMRS; Phase Tracking Reference Signal, PTRS; Channel State Information Reference Signal, CSI-RS; and Tracking Reference Signal, TRS.

6. The method of any of claims 1 to 5, wherein the one or more non-WUR-related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space.

7. The method of any of claims 1 to 5, wherein the one or more non-WUR-related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space in Control Resource Set, CORESET, #0.

8. The method of any of claims 1 to 7, wherein the time domain resources for WUR-related downlink signal monitoring are further based on, or depend on, a reserved time domain resource pattern.

9. The method of any of claims 1 to 8, wherein the time domain resources for WUR-related downlink signal monitoring are contiguous in time.

10. The method of any of claims 1 to 8, wherein the time domain resources for WUR-related downlink signal monitoring are non-contiguous in time.

11. The method of any of claims 1 to 8, wherein the time domain resources for WUR-related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR-related downlink signal.

12. The method of any of claims 1 to 8, wherein the time domain resources for WUR-related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR-related downlink signal and whether non-WUR-related downlink signal related transmission(s) are present.

13. The method of any of claims 1 to 12, wherein the time domain resources for WUR- related downlink signal monitoring are such that WUS is not present in a first N symbols of each slot.

14. The method of any of claims 1 to 12, wherein the time domain resources for WUR- related downlink signal monitoring are such that a WUR-related downlink signal is not present in a last N symbols of each slot.

15. The method of any of claims 1 to 14, wherein frequency domain resources for WUR- related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE, and monitoring (1010) for the WUR-related downlink signal comprises monitoring (1010) for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

16. The method of any of claims 1 to 14, wherein frequency domain resources for WUR- related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain, and monitoring (1010) for the WUR- related downlink signal comprises monitoring (1010) for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

17. The method of any of claims 1 to 14, wherein frequency domain resources for WUR- related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain, and monitoring (1010) for the WUR-related downlink signal comprises monitoring (1010) for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

18. The method of any of claims 1 to 14, wherein frequency domain resources for WUR- related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE, and monitoring (1010) for the WUR-related downlink signal comprises monitoring (1010) for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

19. The method of any of claims 1 to 14, wherein frequency domain resources for WUR- related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUR-related downlink signals, and monitoring (1010) for the WUR-related downlink signal comprises monitoring (1010) for the WUR-related downlink signal in the time and frequency domain resources for WUR-related downlink signal monitoring.

20. The method of any of claims 15 to 19, wherein the frequency domain resource are located at an edge of a respective downlink bandwidth part.

21. The method of any of claims 1 to 20, further comprising receiving (1008), from a network node (1002), information that indicates or configures the time domain resources for WUR-related downlink signal monitoring.

22. The method of claim 21, further comprising receiving (1008), from the network node (1002), information that indicates or configures frequency domain resources for WUR-related downlink signal monitoring.

23. The method of any of claims 1 to 22, wherein monitoring (1010) for the WUR-related downlink signal comprise monitoring (1010) for the WUR-related downlink signal via a Wake- Up Receiver, WUR.

24. The method of claim 23, wherein monitoring (1010) for the WUR-related downlink signal via the WUR comprises dynamically tuning one or more parameters of the WUR based on the time domain resources for WUR-related downlink signal monitoring.

25. The method of any of claims 1 to 24, wherein the WUR-related downlink signal is a Wake-Up Signal, WUS, and the time-domain resources for WUR-related downlink signal monitoring are time-domain resources for WUS monitoring that are based on, or depend on, on e or more non-WUS related time-domain resource patterns.

26. A User Equipment, UE, (1000) for Wake-Up Receiver, WUR, -related downlink signal monitoring and detection, the UE (1000) adapted to: monitor (1010) for a WUR related downlink signal in time-domain resources for WUR related downlink signal monitoring, wherein the time domain resources for WUR related downlink signal monitoring are based on, or depend on, one or more non-WUR related downlink signal related time domain resource patterns.

27. The UE (1000) of claim 26, further adapted to perform the method of any of claims 2 to 25.

28. A User Equipment, UE, (1000; 1200) for Wake-Up Receiver, WUR, -related downlink signal monitoring and detection, the UE (1000) comprising: a communication interface (1212) comprising a transmitter (1218) and a receiver (1220); and processing circuitry (1202) associated with the communication interface (1212), the processing circuitry (1202) configured to cause the UE (1000; 1200) to monitor (1010) for a WUR related downlink signal in time-domain resources for WUR related downlink signal monitoring, wherein the time domain resources for WUR related downlink signal monitoring are based on, or depend on, one or more non-WUR-related downlink signal related time domain resource patterns.

29. The UE (1000) of claim 26, wherein the processing circuitry (1202) is further configured to cause the UE (1000; 1200) to perform the method of any of claims 2 to 25.

30. A method performed by a network node (1002) for Wake-Up Receiver, WUR, -related downlink signal resource configuration and WUR related downlink signal transmission, the method comprising: determining (1004) time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR-related downlink signal related time domain resource patterns; and transmitting (1008), to a User Equipment, UE, (1000), information that indicates or configures the UE (1000) with the determined time-domain resources for WUR related downlink signal monitoring.

31. The method of claim 30, wherein the one or more non-WUR related downlink signal related time domain resource patterns comprise one or more time domain patterns for one or more non-WUR related downlink signal transmissions.

32. The method of claim 31, wherein the one or more non-WUR related downlink signal transmissions comprise Synchronization Signal Block, SSB, transmissions.

33. The method of claim 31 or 32, wherein the one or more non-WUR related downlink signal transmissions comprise downlink reference signal transmissions of one or more downlink reference signal types.

34. The method of claim 33, wherein the one or more downlink reference signal types comprise any one or more of: Demodulation Reference Signal, DMRS; Phase Tracking Reference Signal, PTRS; Channel State Information Reference Signal, CSI-RS; and Tracking Reference Signal, TRS.

35. The method of any of claims 30 to 34, wherein the one or more non-WUR related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space.

36. The method of any of claims 30 to 34, wherein the one or more non-WUR related downlink signal related time domain resource patterns comprise a time domain resource pattern for a common Physical Downlink Control Channel, PDCCH, search space in Control Resource Set, CORESET#0.

37. The method of any of claims 30 to 36, wherein the time domain resources for WUR related downlink signal monitoring are further determined based on, or depend on, a reserved time domain resource pattern.

38. The method of any of claims 30 to 37, wherein the time domain resources for WUR related downlink signal monitoring are contiguous in time.

39. The method of any of claims 30 to 37, wherein the time domain resources for WUR related downlink signal monitoring are non-contiguous in time.

40. The method of any of claims 30 to 37, wherein the time domain resources for WUR related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR related downlink signal.

41. The method of any of claims 30 to 37, wherein the time domain resources for WUR related downlink signal monitoring are either contiguous in time or non-contiguous in time, depending on a duration of the WUR related downlink signal and whether non-WUR related downlink signal related transmission(s) are present.

42. The method of any of claims 30 to 41, wherein the time domain resources for WUR related downlink signal monitoring are determined such that the WUR related downlink signal is not present in a first N symbols of each slot.

43. The method of any of claims 30 to 41, wherein the time domain resources for WUR related downlink signal monitoring are determined such that the WUR related downlink signal is not present in a last N symbols of each slot.

44. The method of any of claims 30 to 43, wherein frequency domain resources for WUR related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUR related downlink signal monitoring.

45. The method of any of claims 30 to 43, wherein frequency domain resources for WUR related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap SSB in the frequency domain, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUR related downlink signal monitoring.

46. The method of any of claims 30 to 43, wherein frequency domain resources for WUR related downlink signal monitoring are within an initial downlink bandwidth part configured for the UE but do not overlap CORESET#0 in the frequency domain, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUR related downlink signal monitoring.

47. The method of any of claims 30 to 43, wherein frequency domain resources for WUR related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUR related downlink signal monitoring.

48. The method of any of claims 30 to 43, wherein frequency domain resources for WUR related downlink signal monitoring are outside of an initial downlink bandwidth part configured for the UE and within a separate downlink bandwidth part configured for WUR related downlink signal transmission, and the method further comprises transmitting (1008), to the UE (1000), information that indicates or configures the UE (1000) with the frequency domain resources for WUR related downlink signal monitoring.

49. The method of any of claims 44 to 48, wherein the frequency domain resource are located at an edge of a respective downlink bandwidth part.

50. The method of any of claims 44 to 49, wherein the frequency domain resource and guardband size are dependent on carrier bandwidth.

51. The method of any of claims 30 to 50, further comprising transmitting (1014), to the UE (1000), a WUR related downlink signal in the determined time domain resources for WUR related downlink signal monitoring.

52. The method of claim 51, wherein transmitting (1014) the WUR related downlink signal in the determined time domain resources for WUR related downlink signal monitoring comprises applying power boosting for at least some of the determined time domain resources that are used for transmission of the WUS.

53. The method of claim 52, wherein power boosting is applied to only a certain number of Resource Blocks, RBs, at a center of a bandwidth of the WUR related downlink signal.

54. The method of claim 52, wherein power boosting is applied to RBs other than a certain number of RBs at a center of a bandwidth of the WUR related downlink signal.

55. The method of any of claims 52 to 54, wherein whether power boosting is applied or a level of power boosting applied depends on presence of other non-WUR related downlink signal transmissions.

56. The method of any of claims 52 to 54, wherein a level of power boosting applied depends on an amount of frequency separation between the WUR related downlink signal and other non- WUR related downlink signal transmissions.

57. The method of any of claims 52 to 54, wherein a level of power boosting applied depends on a scheduling of one or more neighboring frequency bands or one or more neighboring bandwidth parts.

58. The method of any of claims 51 to 57, wherein a guard band size between the WUR related downlink signal and one or more other non-WUR related downlink signal transmissions is based on any one or more of the following factors:

• a relative Power Spectral Density, PSD, difference between the WUR related downlink signal and an enhanced Mobile Broadband, eMBB, Resource Block, RB, which is closest to the WUR related downlink signal;

• a PSD difference between an eMBB RB of a first eMBB signal closest to WUR related downlink signal at one side of the WUR related downlink signal and an eMBB RB of a second eMBB signal closest to the WUR related downlink signal at the other side of the WUR related downlink signal;

• a filter order implemented at a wake up receiver of the UE;

• a modulation order of the eMBB RB closest to the WUS signal at either side of the WUR related downlink signal.

59. The method of any of claims 30 to 58, wherein the WUR-related downlink signal is a Wake-Up Signal, WUS, and the time-domain resources for WUR-related downlink signal monitoring are time-domain resources for WUS monitoring that are based on, or depend on, on e or more non-WUS related time-domain resource patterns.

60. A network node (1002) for Wake-Up Receiver, WUR, -related downlink signal resource configuration and WUR related downlink signal transmission, the network node (1002) adapted to: determine (1004) time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR related downlink signal related time domain resource patterns; and transmit (1008), to a User Equipment, UE, (1000), information that indicates or configures the UE with the determined time-domain resources for WUR related downlink signal monitoring.

61. The network node (1002) of claim 60, further adapted to perform the method of any of claims 31 to 59.

62. A network node (1002; 1300) for Wake-Up Receiver, WUR, -related downlink signal resource configuration and WUR related downlink signal transmission, the network node (1002; 1300) comprising processing circuitry (1302) configured to cause the network node (1002; 1300) to: determine (1004) time-domain resources for WUR related downlink signal monitoring based on one or more non-WUR related downlink signal related time domain resource patterns; and transmit (1008), to a User Equipment, UE, (1000), information that indicates or configures the UE with the determined time-domain resources for WUR related downlink signal monitoring.

63. The network node (1002) of claim 62, wherein the processing circuitry (1302) is further configured to cause the network node (1002; 1300) to perform the method of any of claims 31 to