Wake-up signal link adaptation

Abstract

According to some embodiments, a method is performed by a wireless device for adapting a wake-up signal (WUS) configuration. The method comprises obtaining a first WUS configuration. The WUS configuration comprises parameters describing how a network node transmits a WUS. The method further comprises: monitoring for a WUS based on the first WUS 5 configuration; determining to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; obtaining a second WUS configuration; and monitoring for a WUS based on the second WUS configuration.

Description

Wake-Up Signal Link AdaptationTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to link adaptation for a wake-up signa (WUS).BACKGROUND

[0002] Wake-up receiver (WUR), sometimes also referred to as “wake-up radio,” enables a low power receiver in user equipment (UEs), which, upon detecting a wake-up signal (WUS), wakes up the main (baseband / radio frequency (RF) / less power efficient) receiver to detect an incoming message, typically paging (e.g., physical downlink control channel (PDCCH) in a paging occasions (PO), scheduling a paging message on a physical downlink shared channel (PDSCH)) or PDCCH scheduling downlink (DL) data. A benefit of using WUR is lowering energy consumption and longer device battery life, or at a fixed energy consumption the downlink latency can be reduced (shorter discontinuous reception (DRX) / duty-cycles and more frequent checks for incoming transmissions).

[0003] In general, there are two approaches for detecting WUS. A first approach is using the main receiver. In this approach, there is no need for additional dedicated hardware / receiver for monitoring WUS. Coverage of the main receiver is not typically impacted. This approach has limited power saving gain because the main receiver monitors WUS.

[0004] A second approach is to use a dedicated receiver (WUR). This approach uses an extremely low power, simple and low-cost receiver architecture, relaxed requirements, noisier (i.e., less accurate) clock or oscillator. Significant power saving gain can be achieved by maximizing the time in which the main receiver is in the sleep mode. This approach enables zero energy / battery-less devices and energy harvesting operations. There are coverage considerations given the tradeoff between WUR power consumption and sensitivity.

[0005] Third Generation Partnership Project Release 18 includes WUR for New Radio (NR), with a goal of achieving more significant energy efficiency improvement compared to solutions specified in earlier releases. The specification support needed 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 paging early indication (PEI) is the WUS in Release 18 should not be PDCCH-based and allow for asimpler and low power receiver, i.e., WUR with simple modulation and detection techniques (e.g., using on-off keying (OOK) modulation and non-coherent detection).

[0006] Release 18 includes a study item on “low-power wake-up signal and receiver for NR.” The relevant justification and objective sections include the following.

[0007] Fifth generation (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 radio resource control (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.

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

[0009] The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, extended discontinuous reception (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. Thus, eDRX is not suitable for latency- critical use cases. Accordingly, the intention is to study ultra-low power mechanism that can support low latency in Release 18, for example, lower than eDRX latency.

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

[0011] The power consumption for monitoring a 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.

[0012] The study targets low-power WUS / WUR for power-sensitive, small form-factor devices including Intemet-of-things (loT) use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g., extended reality (XR) / smart glasses, smart phones.

[0013] As opposed to the work on UE power savings in previous releases, the current 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 target substantial gains compared to the existing Rel-15 / 16 / 17 UE power saving mechanisms. Other aspects such as detection performance, coverage, UE complexity, are covered by the evaluation.

[0014] The study item includes the following objectives:• Identify evaluation methodology (including the use cases) and key performance indicators (KPIs). Primarily target low-power WUS / WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables.• Study and evaluate low-power wake-up receiver architectures.• Study and evaluate wake-up signal designs to support wake-up receivers.• Study and evaluate layer one (LI) procedures and higher layer protocol changes needed to support the wake-up signals.• 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 are also included in the study.

[0015] The benefit of WUR is to reduce the energy consumption of the receiver, such that unless there is paging and data for the UE, the UE can remain in a power saving state. This extends the battery life of the device, or alternatively enables shorter downlink latency (shorter DRX) at a fixed battery life.

[0016] The Release 18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical reportis provided in: TR 38.869, V0.4.0, “Study on low-power Wakeup Signal and Receiver for NR”. Subsequently, there will be a Release 19 work item to specify the various design aspects of WUS / WUR.

[0017] A Release 19 work item (Low-power wake-up signal and receiver for new radio (NR) (low power (LP) WUS / WUR)) will specify the wake-up signal for both RRC Idle / Inactive and RRCConnected states. The objectives of the work item are to specify a LP-WUS design commonly applicable to both IDLE / INACTIVE and CONNECTED modes. This includes specifying OOK (OOK-1 and / or OOK-4) based LP-WUS with overlaid orthogonal frequency division multiplexing (OFDM) sequence(s) over OOK symbol. The LP-WUS design shall ensure that for IDLE / INACTIVE operation, the same information is delivered irrespective of LP-WURtype. The OFDM sequence can carry information.

[0018] OOK1 is an on-off keying waveform with single segment within one OFDM symbol. OOK4 is an OOK waveform with multiple segments within one OFDM symbols.

[0019] At least duty-cycled monitoring of LP-WUS is supported

[0020] For IDLE / INACTIVE modes, an objective is to specify the procedure and configuration of LP-WUS indicating paging monitoring triggered by LP-WUS, including at least configuration, sub-grouping and entry / exit condition for LP-WUS monitoring. Another objective is to specify lower power synchronization signal (LP-SS) with periodicity with Yms for LP-WUR, for synchronization and / or radio resource management (RRM) for serving cell.

[0021] LP-SS is based on OOK-1 and / or OOK-4 waveform with or without overlaid OFDM sequences. Further down selection between with and without overlaid OFDM sequences is to be done within the work item. For LP-WUR that can receive existing primary synchronization signal (PSS) / secondary synchronization signa (SSS), existing PSS / SSS can be used for synchronization and RRM instead of LP-SS.

[0022] The value Y will be decided within the work item. 320ms is the start point.

[0023] Another objective is to specify further RRM relaxation of UE main receiver (MR) for both serving and neighbor cell measurements, and UE serving cell RRM measurement offloaded from MR to LP-WUR, including the necessary conditions. For CONNECTED mode, specify procedures to allow UE MR PDCCH monitoring triggered by LP-WUS including activation and deactivation procedure of LP-WUS monitoring. In CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / radio link monitoring (RLM) / beam failure detection (BFD) / channel state information (CSI) measurements are performed by MR.

[0024] The target coverage of LP-WUS and LP-SS shall be the coverage of physical uplink shared channel (PUSCH) for messages. The optimization of LP-WUS signal design for idle / inactive mode is prioritized over the optimization for connected mode.

[0025] For RRC connected mode, the following is assumed for LP-WUS study:• RLM / BFD / CSI are performed by UE main radio.• RRM measurements are performed by UE main radio.• Ultra-deep sleep state is not allowed for main radio.

[0026] For RRC connected mode, study items include the following:• Study additional support of RRM measurement by LP-WUR for RRC connected mode.• Study RRC connected mode LP-WUS functionality / purpose / procedures.• Study RRC connected mode LP-WUS activation / deactivation procedures.• Study RRC connected mode LP-WUS bandwidth, whether same as IDLE / Inactive mode or different.

[0027] Additional items include studying the relationship between LP-WUS and legacy UE power saving techniques. For example, in RRC CONNECTED mode, study benefit of LP-WUS over existing Rel-15, R16, and R17 power saving techniques for following functionalities: LP-WUS with similar functionality as R16 downlink control information of power saving (DCP); LP-WUS activates / resumes PDCCH monitoring when LP-WUS is received; and interaction with legacy power saving techniques, if any.

[0028] Items for evaluation include: assumption on MR sleep state when LP-WUR is monitoring LP-WUS, such as deep sleep, light sleep, and / or micro sleep; how to activate / deactivate LP-WUS monitoring and deactivate / activate PDCCH monitoring; and the LP-WUS waveform.

[0029] In RRC CONNECTED mode, LP-WUS monitoring can be activated / deactivated by at least one or more of: gNB RRC signaling, with or without UE assistance; gNB L1 / L2 LP-WUS activation / deactivation signaling, with or without UE assistance; based on pre-configured condition(s), such as timer; and / or LP-WUS monitoring by UE is known to gNB, and whether it may be transparent to gNB.

[0030] There currently exist certain challenges. For example, 3GPP introduces the WUS monitoring using WUR in Release 19 to potentially save the UE receiver power during RRC connected and idle mode. The UE may be equipped with an additional WUR to receive the LP- WUS signal. During connected mode, the UE can monitor a WUS signal using the WUR, and if there is no WUS received, the UE can continue to keep the main receiver in sleep mode, therefore, additional power may be saved.

[0031] UE needs to do the following in RRC connected mode: monitors short messages transmitted with paging radio network temporary identifier (P-RNTI) over downlink control information (DCI), if configured; monitors control channels associated with the shared data channel to determine if data is scheduled for the UE; provides channel quality and feedback information; performs neighboring cell measurements and measurement reporting; acquires system information; performs immediate minimization of drive test (MDT) measurement together with available location reporting; and / or if configured by upper layers for multicast-broadcastservices (MBS) reception, acquire multicast control channel (MCCH) change notification and MBS broadcast control information and data.

[0032] To further save UE power, the UE may enable the WUR to monitor the downlink for incoming transmission using the WUS signal without waking up the main receiver. When a WUS signal targeted to the UE is successfully decoded, the UE then wakes up its main receiver to monitor the DCI and control channel. Such behavior is similar with Release 16 DCI based wake up signal but with the notable difference that for WUR the main receiver may be kept in a sleep state for the monitoring of the WUS and need only be woken when there is data for the UE.

[0033] DCI based wake up signal is transmitted in PDCCH and the search space of the PDCCH is configured by the network either UE specific through RRC configuration or common search space. At RRC connected mode, when the network detects the degradation of the signal quality (e.g., SNR) from the feedback signal of the channel (e.g., channel quality indicator (CQI)) or hybrid automatic repeat request (HARQ) feedback, the network may schedule different aggregation level of control channel element (CCE) and therefore, when the UE cannot decode PDCCH, the UE may blindly detect the other PDCCH configuration in terms of the number of the aggregation level of CCE, CCE index, radio network temporary identifier (RNTI), etc.

[0034] However, the WUS is new signal / waveform and during the connected mode, if the configured WUS signal in terms of number of time resources (e.g., repetition), frequency repetition, modulation (e.g., OOK1 and OOK4) cannot be decoded, the UE will keep trying to decode the WUS signal using the configured parameters for WUS signal. Compared to legacy PDCCH search space, there is no flexibility on WUS signal detection and there is no means of adapting the detection of WUS signal by blindly detecting other possible WUS signal configurations.SUMMARY

[0035] As described above, certain challenges currently exist with wake-up signal (WUS) configuration. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments provide mechanisms for WUS signal adaptation. As an example, particular embodiments provide methods for WUS signal adaptation based on the normal user equipment (UE) channel state information (CSI) report, signal-to-noise ratio (SNR) of physical uplink shared channel (PUSCH), physical downlink control channel (PDCCH), and / or hybrid automatic repeat request (HARQ) feedback. Particular embodiments provide method for implementing pre-configured candidates of the WUS signal configuration and wake-up receiver (WUR) blind detecting the candidate configurations.Particular embodiments use history logged data to assist the network to adapt the WUS signal configuration.

[0036] The Release 19 work item objectives match the WUS signal coverage to the third message PUSCH in the RACH procedure, which basically requires full coverage for a WUS signal in a cell. Particular embodiments provide mechanisms to adapt the WUS signal coverage with different radio link quality and therefore both save the network resources and also provide further power saving for the UE (e.g., at cell center where less time resources needed to decode the WUS signal) in RRC connected mode.

[0037] According to some embodiments, a method is performed by a wireless device for adapting a WUS configuration. The method comprises obtaining a first WUS configuration. The WUS configuration comprises parameters describing how a network node transmits a WUS. The method further comprises: monitoring for a WUS based on the first WUS configuration; determining to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; obtaining a second WUS configuration; and monitoring for a WUS based on the second WUS configuration.

[0038] In particular embodiments, obtaining the first WUS configuration comprises receiving the first WUS configuration from the network node and obtaining the second WUS configuration comprises receiving the second WUS configuration from the network node.

[0039] In particular embodiments, obtaining the first WUS configuration comprises selecting a first WUS configuration from a set of candidate WUS configurations and obtaining the second WUS configuration comprises selecting a second WUS configuration from the set of candidate WUS configurations.

[0040] In particular embodiments, a detectability or coverage of the second WUS configuration is different than a detectability or coverage of the first WUS configuration.

[0041] In particular embodiments, determining to adapt the first WUS configuration comprises comparing a received signal quality to a threshold value, receiving a command from the network node, and / or determining the wireless device is not able to blind decode a WUS according to the first WUS configuration.

[0042] In particular embodiments, the WUS configuration includes any one or more of: a signal time duration; a signal start position; a modulation scheme; a signal type; a power boosting value for signal transmission; and a repetition value. In particular embodiments, the first WUS configuration uses OOK modulation with a first number of segments per OFDM symbol and the second WUS configuration uses OOK modulation with a second number of segments per OFDM symbol.

[0043] In particular embodiments, the method further comprises reporting to the network node an indication of the determination to adapt the first WUS configuration.

[0044] In particular embodiments, the method further comprises logging information associated with a WUS decoding attempt.

[0045] In particular embodiments, the method further comprises, upon successful WUS decoding, waking up a main receiver to monitor a control channel for downlink control information.

[0046] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0047] According to some embodiments, a method is performed by a network node for adapting a WUS configuration. The method comprises: transmitting a first WUS configuration to a wireless device; transmitting a WUS to the wireless device according to the first WUS configuration; determining to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; transmitting a second WUS configuration to the wireless device; and transmitting a WUS to the wireless device according to the second WUS configuration.

[0048] In particular embodiments, transmitting the first WUS configuration comprises transmitting a first WUS configuration identifier that identifies a first WUS configuration from a set of candidate WUS configurations and transmitting the second WUS configuration comprises transmitting a second WUS configuration identifier that identifies a second WUS configuration from the set of candidate WUS configurations.

[0049] In particular embodiments, determining to adapt the first WUS configuration comprises comparing a reported signal quality from the wireless device to a threshold value. In particular embodiments, determining to adapt the first WUS configuration is based on hybrid automatic repeat request, HARQ, feedback from the wireless device. In particular embodiments, determining to adapt the first WUS configuration comprises determining the wireless device did not respond to the transmission of the WUS according to the first WUS configuration and / or receiving an indication from the wireless device that the wireless device determined to adapt the first WUS configuration.

[0050] In particular embodiments, the method further comprises receiving from the wireless device information regarding a WUS decoding attempt.

[0051] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0052] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program codeoperable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0053] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0054] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments improve the robustness of the WUS signal detection and improve the efficiency to use the WUS signal resources at the network side when a UE is using the WUR in connected mode.

[0055] BRIEF DESCRIPTION OF THE DRAWINGS

[0056] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 is a flowchart illustrating an example of adapting a WUS configuration, according to a particular embodiment;Figure 2 is a time / frequency diagram illustrating an example of three WUS configurations;Figure 3 shows an example of a communication system, according to certain embodiments;Figure 4 shows a user equipment (UE), according to certain embodiments;Figure 5 shows a network node, according to certain embodiments;Figure 6 is a block diagram of a host, according to certain embodiments;Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;Figure 8 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments;Figure 9 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; andFigure 10 is a flowchart illustrating an example method in a network node, according to certain embodiments.DETAILED DESCRIPTION

[0057] As described above, certain challenges currently exist with wake-up signal (WUS) configuration. For example, the WUS is new signal / waveform and during connected mode, if theconfigured WUS signal in terms of number of time resources (e.g., repetition), frequency repetition, modulation (e.g., on-off keying (OOK), such as OOK1 and OOK4) cannot be decoded, the user equipment (UE) will keep trying to decode the WUS signal using the configured parameters for WUS signal. Compared to legacy physical downlink control channel (PDCCH) search space, there is no flexibility on WUS signal detection and there is no means of adapting the detection of WUS signal by blindly detecting other possible WUS signal configurations.

[0058] Another drawback for fixed WUS signal transmission is that the network may waste time and frequency domain resources when the UE is at the cell center if such signal is targeted to the full coverage or to match the coverage of the physical uplink shared channel (PUSCH) message in random access channel (RACH) procedure (i.e. , using link adaptation as if the UE was on the cell edge). Thus, a solution is needed to improve the robustness of the WUS signal detection and improve the efficiency to use the WUS signal resources at the network side when a UE is using the wake-up receiver (WUR) in connected mode.

[0059] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments provide mechanisms for WUS signal adaptation.

[0060] Particular embodiments are 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.

[0061] Some embodiments include WUS configuration adaptation without network control. For example, a UE may be configured for reception of a WUS. The WUS may have to following configuration parameters:• Signal time duration in terms of number of orthogonal frequency division multiplexing (OFDM) symbols and number of slots.• WUS start position or start symbol (different for different WUS length).• Bandwidth• Modulation scheme and order: e.g., OFDM, single-bit on-off keying (OOK1) or multi-bit OOK (OOK4) with M number of OOK segments per OFDM symbol.• WUS type (OFDM-based WUS or OOK-based WUS).• WUS structure information: sequence, preamble, encoding scheme (e.g., Manchester encoding).• WUS time repetition factor.• Power boosting used for WUS transmission.

[0062] For WUR operation in Radio Resource Control (RRC) Connected state, these parameters would typically be configured upon RRC connection setup and re-configuration and then applied for the UE’s duration in Connected state.

[0063] WUS modulation includes the following cases for OOK:• OOK-1 (single-bit OOK): one OOK segment in each OFDM symbol (ON or OFF symbol);• OOK-4 (multi-bit OOK): multiple OOK segments (M) in each OFDM symbol; for example, an ON / OFF pattern [0,1] within one OFDM symbol, where M=2.

[0064] Among the configuration parameters above, some of the parameters may be configured as a range or a parameter set with several different values. For one example, the WUS resources may be N or 2*N to represent different repetition of the WUS signal in time domain. In another example, different values for repetition factors are included in the LP-WUS configuration as candidates for LP-WUS transmission where the UE may attempt detecting LP-WUS using different repetition factors.

[0065] In yet another example, a maximum repetition factor value may be configured where the UE may monitor for LP-WUS assuming different repetition factors up to the maximum value. For example, if maximum repetition factor = 8 is configured, the UE may attempt to detect LP- WUS assuming repetition factor of 1, 2, 4 or 8, or in general, any factor less than the maximum repetition factor.

[0066] Such configuration may be implemented at the RRC setup / configuration / re- configuration. For another example, the configurations may be listed as a combination or set of different parameters with different configuration number and UE may be configured with a set of configuration numbers. This is illustrated in Table 1 and Table 2 below as one example.

[0067] A UE may be configured to monitor one or more of the WUS configurations. In particular embodiments, the configurations are decided or ordered by detectability. This means that, for example, configuration #2 has a lower signal-to-noise ratio (SNR) to reach the same detection performance, bit error rate (BER), or block error rate (BLER), than configuration #1, and therefore configuration #2 is more robust or easier to detect than configuration #1, configuration #3 is more robust or easier to detect than configuration #2, and so on if there are more than three different configurations.Table 1: Examples of configurations with different parameter ranges

[0068] In some embodiments, the WUS coverage configurations are different for OFDMbased WUS and for OOK-based WUS. Table 2: Example of WUS coverage configuration table.

[0069] The network may adapt the configuration of the WUS signal based on one or more of the following criteria: the SNR of the received CQI reported by UE, HARQ feedback of ACK or NACK, the SNR of the PUSCH.• when no signal is received from the UE after the WUS transmission targeting to the UE and followed by PDCCH transmission for a related paging signal.

[0070] For one example, network may choose a configuration of WUS to reduce the resources for WUS signal transmission for the UE when the SNR is high and increase the resource of the WUS signal transmission when SNR is low. An example is illustrated in Figure 1.

[0071] Figure 1 is a flowchart illustrating an example of adapting a WUS configuration, according to a particular embodiment.

[0072] The SNR threshold may be configured at the network based on the coverage target design for the WUS signal. For another example, the network may adjust the WUS configuration when there is no signal received after the WUS is transmitted followed by PDCCH for paging. In this case, because there is no signal received and SNR cannot be estimated, the network may configure another WUS signal with another configuration and such configuration may lower the SNR to detect the WUS signal.

[0073] In one embodiment, the value of M in OOK-4 (described above) is adjusted based on the coverage condition. That is, link adaptation may be done by configuring or reconfiguring different values of M. In general, larger M improves the data rate. However, the signal becomes more susceptible to timing error and inter-symbol interference resulting in coverage degradation. In one example, the value of M decreases for improving coverage. In good coverage conditions, such as small cells, larger values of M are adopted.

[0074] In particular embodiments, the UE monitors for WUS but may not detect the signal using one of the WUS signal configurations. The UE may assume the WUS signal sent by network may be reconfigured with another set of parameters indicated in the RRC signaling. When the UE fails to detect the WUS signal with the configured WUS signal parameters, the UE may try another set of the parameters that may be indicated in RRC signaling.

[0075] For Release 19 WUR, the main receiver will likely be used for mobility measurements and reporting. For example, in CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / RLM / BFD / CSI measurements are performed by MR.

[0076] Therefore, in embodiments described above, the legacy reporting using the main receiver may be used by a gNB to reconfigure the WUS coverage configuration. For example, the channel state information (CSI) reported by the UE may be mapped to WUS detection performance, and based on this the gNB may configure or reconfigure the UE with a suitable WUS coverage configuration.

[0077] In particular embodiments, the UE may be configured to monitor multiple WUS coverage configurations, e.g., configuration 1, 2, and 3 in Table 1 if the UE is capable of OFDM-based WUS reception. The UE may, in its WUS monitoring occasions, perform blind decoding of all three formats and the gNB has flexibility in which WUS duration would apply to reach the UE. If in addition all three configurations use the same frequency resource and have the same start time, e.g., start symbol, the UE may attempt early termination of the WUS monitoring over the configured WUS durations at the least possible additional effort. An example is illustrated in Figure 2.

[0078] Figure 2 is a time / frequency diagram illustrating an example of three WUS configurations.

[0079] In particular embodiments, the UE autonomously selects which configuration to use to decode a WUS transmission after being assigned an initial configuration. For example, if the UE initially may be configured with configuration #2, and the UE reports a CQI or other quality indication to the network that is above a threshold, the UE may monitor for WUS using configuration #1 (leaner signal, but requires better channel quality to decode). In another example, if the UE initially is configured with configuration #2, and the UE reports a CQI or other quality indication to the network that is below a threshold, the UE may monitor for WUS using configuration #3 (less lean signal, i.e. requires more network resources, but requires less channel quality to decode).

[0080] In one example, radio quality limits are configured (reported RSRP) for each configuration. If the UE reports a RSRP that is between the limits of configuration #k, the UE autonomously selects that configuration and the network uses that configuration to transmit WUS. In some embodiments, the last CQI or CSI reported by the UE determines the WUS coverage configuration and monitoring applied by the UE. This ensures the UE and gNB have a common understanding and avoids state mismatch between the two.

[0081] In one example of autonomous configuration selection, when the UE performs an uplink transmission, a new timer is started or restarted. If the timer expires, the UE selects a more robust or easily detectable configuration. In one option, when the timer expires the UE selects the most robust configuration (e.g., configuration #3 in Table 1). The rationale behind this option is that when the UE has not performed an uplink transmission (neither physical uplink shared channel (PUSCH) or the physical uplink control channel (PUCCH)) the network has no means to estimate the UEs channel quality and thereby determine a suitable configuration for the UE, or the UE has failed to detect the WUS due to being configured with a configuration that is not robust enough to enable the UE to detect the WUS. This provides a mechanism to facilitate that the configuration with best or more optimal coverage may be used unless the network recently has measured the radio quality and found it sufficient for the use of a slimmer configuration.

[0082] In embodiments when a group of UEs are served with the same WUS, the link adaptation may be adapted to the group. One adaptation is to base the link adaptation on the UE in the group with the worst radio condition.

[0083] Some embodiments for WUS configuration adaptation are based on network command. In particular embodiments, the UE may be configured with a WUS with certain configurable entry and exit conditions. Such entry and exit conditions may be monitored by either UE or network and the entry and exist action may be determined by network or UE. When such condition is monitored by the network, the network may stop the WUS transmission and reconfigure the UE with a different WUS configuration, either with a medium access control (MAC) command or the RRC reconfiguration. In particular embodiments, a configuration index may be indicated.

[0084] When such condition is monitored by the UE, when the UE exits the WUS procedure autonomously based on monitored conditions, the UE may notify the network and the network may respond to the UE with a new WUS configuration. The network may also exit the WUS procedure based on UE decision. In particular embodiments, the UE does not need to notify the network when the entry and exit condition is determined by the UE, e.g., when the UE may enter and exit WUS operation frequently, to reduce signaling overhead. In a related option, UE may notify the network based a configurable timer.

[0085] The conditions the network may monitor include any one or more of the following:1. SNR of PUSCH2. CQI from UE report3. HARQ ACK and NACK feedback

[0086] The conditions the UE may monitor: include any one or more of the following:1. WUS signal quality, e.g. SNR, BLER / BER or RSRP2. serving cell signal quality

[0087] If the UE moves to worse coverage during its stay in RRC Connected mode, the UE’s current WUS coverage configuration (i.e., WUS duration) may not be sufficient to reach the UE, neither for downlink data nor for configuring with a more robust WUS coverage configuration with a longer WUS duration. The UE therefore becomes unreachable by the network. In particular embodiments, the UE therefore still monitors PDCCH, e.g., a DRX on-duration in association to the Connected mode mobility measurements when the main receiver anyway needs to be started (i.e., for the radio resource management (RRM) / radio link monitoring (RLM) / beam failure detection (BFD) / channel state information (CSI)measurements). In this way, the gNB may reach the UE to re-configure it also if the UE moves to worse coverage. In the above embodiment, oneoption is that the UE sends a report to the network when the UE exits the WUS procedure, for example, out of WUS coverage.

[0088] In particular embodiments related to the UE, the UE logs information related to the WUS decoding attempts and reports it to the network. Such reporting may take place immediately or provided to the network based on request, or they may be collected and provided as part of the logged data. This type of logging is sometimes also known as minimization of drive test (MDT). The logged data comprises information related to the WUS configuration the UE has assumed or used to decode the WUS. Examples of logged data / information include:• WUS configuration ID, e.g., WUS config #1, WUS config #2, WUS config #3 as shown in Table 1 or Figure 1.• Time domain resources in number of OFDM symbols• Repetition number• Modulation scheme, e.g., OOK1, OOK4• WUS type, e.g., OFDM-based WUS, OOK-based WUS• WUS duration• Aggregation level• SNR level at decoding attempt• Estimated, calculated or hypothetical BLER at decoding attempt• Measured values, e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Noise Ratio (SNR), etc.) of the serving cell at the decoding attempt• Number of previous attempts

[0089] In one example, if the UE first tries to decode WUS using configuration #1 but has failed to do, then it tries to decode WUS using configuration #2 which is expected to be more robust and easier to detect than configuration #1. According to this embodiment, the UE logs the information related to the WUS decoding attempt as listed above.

[0090] In another example, the UE first tries to decode the WUS using configuration #1 but fails and makes a new attempt using configuration #2 which also leads to failure. The UE then successfully decodes the WUS using configuration #3. This information is logged in the UE and signaled to the network.

[0091] The receiving network node may use the information for adapting the future transmission parameters of WUS. The network node may also use the information for reconfiguring one or more network parameters for enhancing the WUS coverage.

[0092] Because logging the information may result in increased UE power consumption, some embodiments only trigger the logging when needed or to reduce the amount of logging. In one example, the UE starts logging only when the UE has failed to decode WUS N number of time over last time period Tl, where N and Tl may be configurable. Tl may be expressed in absolute time or in terms of DRX cycles, for example, last 5 DRX cycles. Both N and Tl may be configurable or predefined parameters. After the UE has successfully decoded a WUS, the UE may stop logging.

[0093] Figure 3 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

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

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

[0096] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. 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 106 includes one more core network nodes (e.g., core network node 108) 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 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0098] As a whole, the communication system 100 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0099] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 maysupport network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 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 loT services to yet further UEs.

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

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

[0102] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to anM2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 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 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0103] Figure 4 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0105] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. 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.

[0106] The processing circuitry 202 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 210. The processing circuitry 202 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 202 may include multiple central processing units (CPUs).

[0107] In the example, the input / output interface 206 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 200. 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.

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

[0109] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0110] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 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 210, which may be or comprise a device-readable storage medium.

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

[0112] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-basedcommunication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

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

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

[0115] A UE, when in the form of an Internet of Things (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 TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, amotion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking 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 independence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.

[0116] 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 and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

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

[0118] Figure 5 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0119] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0120] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0121] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0122] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0123] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be onseparate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0124] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 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 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

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

[0126] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part ofthe communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

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

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

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

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

[0131] Figure 6 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0132] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0133] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FL AC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0134] Figure 7 is a block diagram illustrating a virtualization environment 500 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 500 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.

[0135] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0136] Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

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

[0138] In the context of NFV, a VM 508 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 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0139] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 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 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0140] Figure 8 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of Figure 3 and / or UE 200 of Figure 2), network node (such as network node 110a of Figure 3 and / or network node 300 of Figure 3), and host (such as host 116 of Figure 3 and / or host 400 of Figure 4) discussed in the preceding paragraphs will now be described with reference to Figure 6.

[0141] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0142] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0143] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0144] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0145] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the userdata carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0146] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0147] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE.

[0148] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0149] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connectionmay be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

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

[0151] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0152] FIGURE 9 is a flowchart illustrating an example method 900 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 9 may be performed by UE 200 described with respect to FIGURE 4. The wireless device is operable to adapt a wake-up signal (WUS) configuration.

[0153] The method begins at step 912, where the wireless device (e.g., UE 200) obtains a first WUS configuration. The WUS configuration comprises parameters describing how a network node transmits a WUS. For example, the WUS configuration includes any one or more of: a signal time duration (e.g., number of OFDM symbols and / or number of slots); a signal start position; a signal bandwidth; a modulation scheme (e.g., OFDM, OOK1, OOK4, etc.); a signal type (e.g., OFDM-based, OOK-based, etc.); a power boosting value for signal transmission; and a repetition value.

[0154] In particular embodiments, obtaining the first WUS configuration comprises receiving the first WUS configuration from the network node.

[0155] In particular embodiments, obtaining the first WUS configuration comprises selecting a first WUS configuration from a set of candidate WUS configurations.

[0156] In particular embodiments, the wireless device may obtain the first WUS configuration according to any of the embodiments and examples described herein.

[0157] At step 914, the wireless device monitors for a WUS based on the first WUS configuration. The wireless device may monitor for the WUS with a wake-up receiver (WUR) while a main receiver of the wireless device is in a low-power sleep state.

[0158] At step 916, the wireless device determines to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance.

[0159] In particular embodiments, determining to adapt the first WUS configuration comprises comparing a received signal quality to a threshold value. For example, the wireless device, during a time when the main receiver is operational and measuring reference signals, may determine that a downlink signal quality has changed either for the better or worse, and thus thewireless device may determine to autonomously adapt the WUS configuration to better suit the current network conditions. For example, the wireless device may move towards the center of the cell and thus adapt a WUS configuration that uses less resources because the signal quality is better. As another example, the wireless device may move towards the edge of a cell and thus adapt a WUS configuration that uses more resources because the signal quality is poorer.

[0160] In particular embodiments, determining to adapt the first WUS configuration comprises receiving a command from the network node. For example, the network node may monitor SNR of uplink signals from the wireless device to determine whether to adapt a WUS configuration, or the network node may determine to adapt a WUS configuration based on HARQ feedback from the wireless device. As another example, the network node may not receive uplink signals from the wireless device after sending the wireless device a WUS and determine to adapt the WUS configuration. Upon the determination, the network node may send an updated configuration to the wireless device. The updated configuration may comprise updated configuration parameters, or an index to a WUS configuration already configured at the wireless device.

[0161] In particular embodiments, determining to adapt the first WUS configuration comprises determining the wireless device is not able to blind decode a WUS according to the first WUS configuration. For example, the wireless device may be configured with several WUS configurations, such as illustrated in Figure 2 or described in Tables 1 and 2. The wireless device may attempt blind decoding according to a first pre-configured WUS configuration. If the blind decoding is successful, the wireless device may stop there and not attempt blind decoding according to any of the other WUS configurations. If the blind decoding is unsuccessful, then the wireless device determines to adapt the WUS configuration and perform blind decoding according to a second pre-configured WUS configuration.

[0162] In particular embodiments, the wireless device may determine to adapt the first WUS configuration according to any of the embodiments and examples described herein.

[0163] At step 918, the wireless device may report to the network node an indication of the determination to adapt the first WUS configuration. For example, when the wireless device determines to autonomously adapt the WUS configuration, the wireless device may inform the network node so that the network node knows to use the adapted configuration. In some embodiments, the report may include the adapted WUS configuration. In some embodiments, the report may only indicate that the WUS configuration was adapted, and the network node determines the new WUS configuration.

[0164] At step 920, the wireless device may log information associated with a WUS decoding attempt. For example, the wireless device may log unsuccessful WUS decoding attempts and / or the reason for unsuccessful attempt. The wireless device may also log successful decoding attempts. In particular embodiments, the wireless device may log information associated with a WUS decoding attempt according to any of the embodiments and examples described herein.

[0165] In some embodiments, the wireless device may report the logged information to the network node, either autonomously or upon request from the network node.

[0166] At step 922, the wireless device obtains a second WUS configuration. In particular embodiments, obtaining the second WUS configuration comprises receiving the second WUS configuration from the network node. In particular embodiments, obtaining the second WUS configuration comprises selecting a second WUS configuration from a set of candidate WUS configurations.

[0167] In particular embodiments, a detectability or coverage of the second WUS configuration is different than a detectability or coverage of the first WUS configuration.

[0168] In particular embodiments, the first WUS configuration uses OOK modulation with a first number of segments per OFDM symbol and the second WUS configuration uses OOK modulation with a second number of segments per OFDM symbol.

[0169] In particular embodiments, the wireless device may obtain the second WUS configuration according to any of the embodiments and examples described herein.

[0170] At step 924, the wireless device monitors for a WUS based on the second WUS configuration.

[0171] At step 926, upon successful WUS decoding, the wireless device wakes up the main receiver to monitor a control channel for downlink control information.

[0172] Modifications, additions, or omissions may be made to method 900 of FIGURE 9. Additionally, one or more steps in the method of FIGURE 9 may be performed in parallel or in any suitable order. For example, in some embodiments step 920 may be performed before steps 918 and / or 916.

[0173] FIGURE 10 is a flowchart illustrating an example method 1000 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 10 may be performed by network node 300 described with respect to FIGURE 5. The network node is operable to adapt a WUS configuration.

[0174] The method begins at step 1012, where the network node (e.g., network node 300) transmits a first WUS configuration to a wireless device. The WUS configuration comprises parameters describing how the network node transmits a WUS. The WUS configuration isdescribed in more detail with respect to FIGURE 9 and the embodiments and examples described herein.

[0175] In particular embodiments, transmitting the first WUS configuration comprises transmitting a first WUS configuration identifier that identifies a first WUS configuration from a set of candidate WUS configurations.

[0176] At step 1014, the network node transmits a WUS to the wireless device according to the first WUS configuration.

[0177] At step 1016, the network node determines to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance.

[0178] In particular embodiments, determining to adapt the first WUS configuration comprises comparing a reported signal quality (e.g., RSRP, SNR, etc.) from the wireless device to a threshold value.

[0179] In particular embodiments, determining to adapt the first WUS configuration is based on hybrid automatic repeat request, HARQ, feedback from the wireless device.

[0180] In particular embodiments, determining to adapt the first WUS configuration comprises determining the wireless device did not respond to the transmission of the WUS according to the first WUS configuration.

[0181] In particular embodiments, determining to adapt the first WUS configuration comprises receiving an indication from the wireless device that the wireless device determined to adapt the first WUS configuration.

[0182] In particular embodiment, the network node may determine to adapt the first WUS configuration according to any of the embodiments and examples described herein.

[0183] At step 1018, the network node receives from the wireless device information regarding a WUS decoding attempt. For example, the wireless device may log information regarding WUS decoding attempts and report the information to the network node. The network node may use the information to determine whether to adapt a WUS configuration, or how to adapt a WUS configuration.

[0184] At step 1020, the network node transmits a second WUS configuration to the wireless device. In particular embodiments, transmitting the second WUS configuration comprises transmitting a second WUS configuration identifier that identifies a second WUS configuration from the set of candidate WUS configurations.

[0185] At step 1022, the network node transmits a WUS to the wireless device according to the second WUS configuration.

[0186] Modifications, additions, or omissions may be made to method 1000 of FIGURE 10. Additionally, one or more steps in the method of FIGURE 10 may be performed in parallel or in any suitable order. For example, in some embodiments step 1018 may be performed before step 1016.

[0187] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0188] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0189] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0190] Some example embodiments are described below.Group A Embodiments1. A method performed by a user equipment for adapting a wake-up signal (WUS) configuration, the method comprising: monitoring for wake-up signal (WUS) configurations based at least on a set of WUS configuration candidates; determining whether a WUS signal with a first WUS configuration from among the set of WUS configuration candidates is received; in response to determining that the WUS signal with the first WUS configuration is received, updating one or more operational parameters based at least on the received WUS configuration, wherein the one or more operational parameters comprise at least one of a signal time duration, a start position, a bandwidth, a modulation scheme, a repetition factor, or a powerlevel; and entering a low-power mode or waking from the low-power mode in response to updating the one or more operational parameters.2. The system of embodiment 1, wherein updating the one or more operational parameters is further based at least on a channel state information (CSI) report, a signal-to-noise ratio (SNR) of a physical uplink shared channel (PUS CH), or a historical network data.3. The system of any one of the embodiments 1-2, wherein each of the set of WUS configuration candidates comprises the one or more operational parameters associated with a respective WUS configuration.4. The method of any one of the embodiments 1-3, further comprising: in response to determining that the WUS signal with the first WUS configuration is not received, determining whether the WUS signal with a second WUS configuration is received; in response to determining that the second WUS configuration is received, updating the one or more operational parameters based at least on the second WUS configuration; and re-entering the low-power mode or waking from the low-power mode in response to updating the one or more operational parameters based at least on the second WUS configuration.5. The method of any one of the embodiments 1-4, further comprising: automatically selecting a WUS configuration from among the set of WUS configuration candidates to decode the WUS signal based at least on one or more quality indicators comprising a last reported channel quality indicator (CQI); and decoding the WUS signal with the selected WUS configuration.6. The method of any one of the embodiments, 6, wherein the WUS configuration is selected based at least on radio quality limits configured for the set of WUS configuration candidates, wherein the selected WUS configuration is associated with a reported radio signal quality that is within a threshold range.7. The method of any one of the embodiments 1-5, further comprising: initiating or restarting a timer upon performing an uplink transmission;determining that a second WUS configuration is more detectable than an initially selected WUS configuration; and selecting the second WUS configuration to decode the WUS signal if the timer expires before any subsequent uplink transmission is initiated.8. The method of embodiment 7, wherein determining that the second WUS configuration is more detectable than the initially selected WUS configuration comprises: determining that the second WUS configuration is associated with a signal power level higher than the first WUS configuration; determining that the second WUS configuration is associated with a modulation scheme that is more error-resistant; or determining that the second WUS configuration is associated with an increased signal redundancy through a higher repetition factor compared to the first WUS configuration.9. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.10. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.11. The method of any of the previous embodiments, further comprising:- providing user data; and- forwarding the user data to a host computer via the transmission to the base station.Group B Embodiments12. A method performed by a network node for managing Wake-Up Signal (WUS) operations for a user equipment (UE), the method comprising: transmitting a wake-up signal (WUS) signal with a first WUS configuration from among a set of WUS configuration candidates to a user equipment (UE); receiving feedback from the UE, the feedback comprising at least one of a channel state information (CSI) report, a signal-to-noise ratio (SNR) of a physical uplink shared channel (PUSCH), or historical network data; and based on the received feedback, determining whether to maintain the first WUSconfiguration or select a second WUS configuration from among the set of WUS configuration candidates for subsequent transmissions.13. The method of embodiment 12, further comprising updating the one or more operational parameters of the at least one of the set of WUS configuration candidates based on the received feedback.14. The method of any one of the embodiments 12-13, further comprising: in response to determining that the feedback indicates non-receipt of the WUS signal, selecting the second WUS configuration for the subsequent transmissions; and transmitting the second WUS configuration to the UE.15. The method of any one of the embodiments 12-14, further comprising: transmitting the second WUS configuration to the UE to adapt to the UE’s current coverage and operational requirements, wherein the operational requirements comprise a signal quality requirement, a signal strength requirement, and a channel quality requirement.16. The method of any one of the embodiments 12-15, further comprising: receiving logged data reported by the UE, the logged data comprising WUS configuration attempts, WUS decoding success or failure instances, and signal quality measurements; and updating one or more subsequent WUS signal transmission parameters based at least on the logged data, wherein the one or more subsequent WUS signal transmission parameters comprise a WUS signal time duration and a WUS start symbol or position.17. The method of any one of the embodiments 16, wherein the logged data comprises a WUS configuration identifier (ID), time domain resources, a repetition number, a modulation scheme, a WUS type, a WUS duration, an aggregation level, a SNR level at decoding attempt, and estimated or measured values of serving cell signal quality at the time of decoding attempt.18. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.19. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.20. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.Group C Embodiments21. A user equipment for adapting a wake-up signal (WUS) configuration, 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.22. A network node for managing wake-up signal (WUS) operations for a user equipment (UE), the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.23. A user equipment (UE) for adapting a wake-up signal (WUS) configuration, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A 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

Claims1. A method (900) performed by wireless device (200) for adapting a wake-up signal, WUS, configuration, the method comprising: obtaining (912) a first WUS configuration, the WUS configuration comprising parameters describing how a network node transmits a WUS; monitoring (914) for a WUS based on the first WUS configuration; determining (916) to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; obtaining (922) a second WUS configuration; and monitoring (924) for a WUS based on the second WUS configuration.

2. The method of claim 1, wherein obtaining the first WUS configuration comprises receiving the first WUS configuration from the network node and obtaining the second WUS configuration comprises receiving the second WUS configuration from the network node.

3. The method of claim 1, wherein obtaining the first WUS configuration comprises selecting a first WUS configuration from a set of candidate WUS configurations and obtaining the second WUS configuration comprises selecting a second WUS configuration from the set of candidate WUS configurations.

4. The method of any one of claims 1 -3, wherein a detectability or coverage of the second WUS configuration is different than a detectability or coverage of the first WUS configuration.

5. The method of any one of claims 1-4, wherein determining to adapt the first WUS configuration comprises comparing a received signal quality to a threshold value.

6. The method of any one of claims 1-4, wherein determining to adapt the first WUS configuration comprises receiving a command from the network node.

7. The method of any one of claims 1-4, wherein determining to adapt the first WUS configuration comprises determining the wireless device is not able to blind decode a WUS according to the first WUS configuration.

8. The method of any one of claims 1-6, wherein the WUS configuration includes any one or more of: a signal time duration; a signal start position; a modulation scheme; a signal type; a power boosting value for signal transmission; and a repetition value.

9. The method of claim 8, wherein the first WUS configuration uses on-off keying, OOK, modulation with a first number of segments per orthogonal frequency division multiplexing, OFDM, symbol and the second WUS configuration uses OOK modulation with a second number of segments per OFDM symbol.

10. The method of any one of claims 1-9, further comprising reporting (918) to the network node an indication of the determination to adapt the first WUS configuration.

11. The method of any one of claims 1-10, further comprising logging (920) information associated with a WUS decoding attempt.

12. The method of any one of claims 1-11, further comprising, upon successful WUS decoding, waking up (926) a main receiver to monitor a control channel for downlink control information.

13. A wireless device (200) capable of adapting a wake-up signal (WUS) configuration, the wireless device comprising processing circuitry (202) operable to: obtain a first WUS configuration, the WUS configuration comprising parameters describing how a network node transmits a WUS; monitor for a WUS based on the first WUS configuration; determine to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; obtain a second WUS configuration; and monitor for a WUS based on the second WUS configuration.

14. The wireless device of claim 13, wherein the processing circuitry is operable to obtain the first WUS configuration by receiving the first WUS configuration from the network node and obtain the second WUS configuration by receiving the second WUS configuration from the network node.

15. The wireless device of claim 13, wherein the processing circuitry is operable to obtain the first WUS configuration by selecting a first WUS configuration from a set of candidate WUS configurations and obtain the second WUS configuration by selecting a second WUS configuration from the set of candidate WUS configurations.

16. The wireless device of any one of claims 13-15, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by comparing a received signal quality to a threshold value.

17. The wireless device of any one of claims 13-15, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by receiving a command from the network node.

18. The wireless device of any one of claims 13-15, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by determining the wireless device is not able to blind decode a WUS according to the first WUS configuration.

19. The wireless device of any one of claims 13-18, the processing circuitry further operable to report to the network node an indication of the determination to adapt the first WUS configuration.

20. The wireless device of any one of claims 13-19, the processing circuitry further operable to, upon successful WUS decoding, wake up a main receiver to monitor a control channel for downlink control information.

21. A method (1000) performed by a network node (300) for adapting a wake-up signal, WUS, configuration, the method comprising: transmitting (1012) a first WUS configuration to a wireless device, the WUS configuration comprising parameters describing how the network node transmits a WUS;transmitting (1014) a WUS to the wireless device according to the first WUS configuration; determining (1016) to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; transmitting (1020) a second WUS configuration to the wireless device; and transmitting (1022) a WUS to the wireless device according to the second WUS configuration.

22. The method of claim 21, wherein transmitting the first WUS configuration comprises transmitting a first WUS configuration identifier that identifies a first WUS configuration from a set of candidate WUS configurations and transmitting the second WUS configuration comprises transmitting a second WUS configuration identifier that identifies a second WUS configuration from the set of candidate WUS configurations.

23. The method of any one of claims 21-22, wherein a detectability or coverage of the second WUS configuration is different than a detectability or coverage of the first WUS configuration.

24. The method of any one of claims 21-23, wherein determining to adapt the first WUS configuration comprises comparing a reported signal quality from the wireless device to a threshold value.

25. The method of any one of claims 21-23, wherein determining to adapt the first WUS configuration is based on hybrid automatic repeat request, HARQ, feedback from the wireless device.

26. The method of any one of claims 21-23, wherein determining to adapt the first WUS configuration comprises determining the wireless device did not respond to the transmission of the WUS according to the first WUS configuration.

27. The method of any one of claims 21-23, wherein determining to adapt the first WUS configuration comprises receiving an indication from the wireless device that the wireless device determined to adapt the first WUS configuration.

28. The method of any one of claims 21-27, wherein the WUS configuration includes anyone or more of: a signal time duration; a signal start position; a modulation scheme; a signal type; a power boosting value for signal transmission; and a repetition value.

29. The method of claim 28, wherein the first WUS configuration uses on-off keying, OOK, modulation with a first number of segments per orthogonal frequency division multiplexing, OFDM, symbol and the second WUS configuration uses OOK modulation with a second number of segments per OFDM symbol.

30. The method of any one of claims 21-29, further comprising receiving (1018) from the wireless device information regarding a WUS decoding attempt.

31. A network node (300) capable of adapting a wake-up signal, WUS, configuration, the network node comprising processing circuitry (302) operable to: transmit a first WUS configuration to a wireless device, the WUS configuration comprising parameters describing how the network node transmits a WUS; transmit a WUS to the wireless device according to the first WUS configuration; determine to adapt the first WUS configuration based on one or more factors affecting a WUS detection performance; transmit a second WUS configuration to the wireless device; and transmit a WUS to the wireless device according to the second WUS configuration.

32. The method of claim 31, wherein the processing circuitry is operable to transmit the first WUS configuration by transmitting a first WUS configuration identifier that identifies a first WUS configuration from a set of candidate WUS configurations and transmit the second WUS configuration by transmitting a second WUS configuration identifier that identifies a second WUS configuration from the set of candidate WUS configurations.

33. The method of any one of claims 31-32, wherein a detectability or coverage of the second WUS configuration is different than a detectability or coverage of the first WUSconfiguration.

34. The method of any one of claims 31-33, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by comparing a reported signal quality from the wireless device to a threshold value.

35. The method of any one of claims 31-33, wherein the processing circuitry is operable to determine to adapt the first WUS configuration based on hybrid automatic repeat request, HARQ, feedback from the wireless device.

36. The method of any one of claims 31-33, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by determining the wireless device did not respond to the transmission of the WUS according to the first WUS configuration.

37. The method of any one of claims 31-33, wherein the processing circuitry is operable to determine to adapt the first WUS configuration by receiving an indication from the wireless device that the wireless device determined to adapt the first WUS configuration.

38. The method of any one of claims 31-37, wherein the WUS configuration includes any one or more of: a signal time duration; a signal start position; a modulation scheme; a signal type; a power boosting value for signal transmission; and a repetition value.

39. The method of claim 38, wherein the first WUS configuration uses on-off keying, OOK, modulation with a first number of segments per orthogonal frequency division multiplexing, OFDM, symbol and the second WUS configuration uses OOK modulation with a second number of segments per OFDM symbol.

40. The method of any one of claims 31-39, the processing circuitry further operable to receive from the wireless device information regarding a WUS decoding attempt.

Images