WO2023191675A1 - Wake-up radio with adaptive sensitivity and power consumption - Google Patents

Wake-up radio with adaptive sensitivity and power consumption Download PDF

Info

Publication number
WO2023191675A1
WO2023191675A1 PCT/SE2022/050325 SE2022050325W WO2023191675A1 WO 2023191675 A1 WO2023191675 A1 WO 2023191675A1 SE 2022050325 W SE2022050325 W SE 2022050325W WO 2023191675 A1 WO2023191675 A1 WO 2023191675A1
Authority
WO
WIPO (PCT)
Prior art keywords
wur
power state
state
switching
low power
Prior art date
Application number
PCT/SE2022/050325
Other languages
French (fr)
Inventor
Mohammad MOZAFFARI
Andreas HÖGLUND
Saeedeh MOLOUDI
Mehrnaz AFSHANG
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/SE2022/050325 priority Critical patent/WO2023191675A1/en
Publication of WO2023191675A1 publication Critical patent/WO2023191675A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0245—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal according to signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0254—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity detecting a user operation or a tactile contact or a motion of the device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present disclosure relates to wireless communications, and in particular, to a wake-up radio with adaptive sensitivity and power consumption.
  • the Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • NR New Radio
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • 6G wireless communication systems are also under development.
  • a purpose of a wake-up receiver is to enable a low power receiver in WDs that operates while the main receiver of the WD is asleep.
  • the WUR detects a wake-up signal (WUS)
  • the WUS wakes up the main receiver to detect an incoming message, typically a paging message.
  • a physical downlink control channel (PDCCH) in paging occasions (PO) may be detected by the main receiver which schedules a paging message on a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PO paging occasions
  • a benefit of employing a WUR is lower energy consumption and longer device battery life at the WD. At a fixed energy consumption, the downlink latency can be reduced (shorter discontinuous reception (DRX)/duty-cycles and more frequent checks for incoming transmissions).
  • FIG. 1 is an illustration of an example wakeup signal (WUS) and a paging occasion (PO).
  • WUS wakeup signal
  • PO paging occasion
  • 3GPP Technical Release 15 3GPP Rel-15, e.g., Technical Standard 36 TS 300, v!5.12.0
  • NB- loT narrowband Internet of things
  • LTE-M LTE-M
  • the logic is that a WD would check for a WUS a certain time before its PO, and only if a WUS is detected the WD would continue to check for PDCCH in the PO, and if not, which is most of the time, the WD can go back to a sleep state to conserve energy. Due to the coverage enhancements, the WUS can be of variable length depending on the WD’s coverage.
  • FIG. 2 is an illustration of an example WUS for narrow band Internet of things (NB-IoT) and LTE-M.
  • a WUS is based on the transmission of a short signal that indicates to the WD that it should continue to decode the downlink (DL) control channel, e.g., full narrowband PDCCH (NPDCCH) for NB-IoT. If the WUS is absent, (discontinuous transmission (DTX), i.e., the WD does not detect the WUS) then the WD can go back to sleep without decoding the downlink (DL) control channel.
  • DL downlink
  • NPDCCH full narrowband PDCCH
  • the decoding time for a WUS is considerably shorter than that of the full NPDCCH since it essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces WD power consumption and leads to longer WD battery life.
  • the WUS would be transmitted only when there is a paging for the WD. But if there is no paging for the WD, then the WUS will not be transmitted (i.e., implying a discontinuous transmission, DTX) and the WD would go back to deep sleep, e.g., upon detecting DTX instead of the WUS. This is illustrated in FIG. 1, where white blocks indicate possible WUS and PO positions whereas the black boxes indicate actual WUS and PO positions.
  • a WUS is considered in several parts of the 3GPP LTE Technical Standards, 36-series standard, e.g., 3GPP TS 36.211 V15.14.0, 3GPP TS 36.213 V15.14.0, 3GPP TS 36.304 V15.14.0 and 3GPP TS 36.331 V15.14.0.
  • a WD will report its WUS capability to the network, and WUS gap capability (see below). Further, WUS information was added to the paging message/request from the mobile management entity (MME) to network node (eNB). The network node (eNB) will use the WUS for paging the WD when the WUS is enabled in the cell (i.e. WUS-Conflg present in SI), and the WD supports WUS detection according to the wakeUpSignal-r 15 WD capability (see also the description of WUS gap below).
  • the WUS was introduced for both LTE-M and NB-IoT with support for both DRX and eDRX, For support of DRX, a 1-to-l mapping between the WUS and the PO is implemented.
  • the network node eNB can configure in one WUS gap for WDs using DRX, and another WUS gap for WDs using eDRX See 3GPP TS 36.331 vl 5.14.0, which provides as follows:
  • WUS-Config-NB-rl5 SEQUENCE ⁇ maxDurationF actor-r 15 WU S -MaxDurationF actor-NB - rl5, numP0s-rl5 ENUMERATED ⁇ nl, n2, n4 ⁇
  • WUS-ConfigPerCarrier-NB-rl5 SEQUENCE ⁇ maxDurationF actor-r 15 WU S -MaxDurationF actor-NB - rl5
  • WUS-MaxDurationFactor-NB-rl5 ENUMERATED ⁇ onel28th, one64th, one32nd, onel6th, oneEighth, oneQuarter, oneHalf ⁇ WUS-Config-NB field descriptions time offsetDRX
  • Evolved universal terrestrial radio access network configures time offset-eDRX-Short to a value longer than or equal to time offsetDRX.
  • time offset-eDRX-Long configures time offset-eDRX-Short to a value longer than or equal to time offsetDRX.
  • value mslOOO corresponds to 1000 ms
  • value ms2000 corresponds to 2000 ms.
  • the WD capabilities can also indicate the minimum WUS gaps required for the WD to be able to decode PDCCH in the associated PO, for DRX and eDRX, respectively [3GPP TS 36.331 vl5.14.0], UE-RadioPaginglnfo-NB information element
  • UE-RadioPagingInfo-NB-rl3 SEQUENCE ⁇ ue-Category-NB-rl 3 ENUMERATED ⁇ nbl ⁇
  • wake UpSignalMin G p-eDRX indicates the minimum gap the WD supports between WUS or group wake up signal (GWUS) and associated PO in case of eDRX in frequency division duplex (FDD), as specified in 3GPP TS 36.304 V15.14.0.
  • Value ms40 corresponds to 40 ms
  • value ms240 corresponds to 240 ms and so on. If this field is included, the WD shall also indicate support for WUS or GWUS for paging in DRX.
  • a longer WUS gap of Is or 2s was introduced to enable the use of WUR. That is, starting up the main baseband receiver if a WUR is used for the detection of the WUS may take a long time for which the longer WUS gap is provided. If this is supported in the cell, the network node would include time offset- eDRX-Long in the WUS-Config in system information (SI).
  • SI system information
  • the WD behavior for monitoring paging with WUS is specified, and in Table 7.4-1, which WUS time gap the WD (and eNB) should apply is indicated and depends on the reported WD capability: Paging with Wake Up Signal Paging with Wake Up Signal is only used in the cell in which the WD most recently entered the RRC IDLE state triggered by: reception of RRCEarlyDataCompletc, or reception of RRCConnectionRelease not including noLastCellUpdate,' or reception of RRCConnectionRelease including noLastCellUpdate and the WD was using (G)WUS in this cell prior to this RRC connection attempt.
  • the WD shall monitor the WUS using the WUS parameters provided in System Information.
  • DRX is used and the WD detects WUS the
  • WD shall monitor the following PO.
  • extended DRX is used and the WD detects WUS
  • the WD shall monitor the following numPOs POs or until a paging message including the WD's nonaccess stratum (NAS) identity is received, whichever is earlier. If the WD does not detect the WUS, the WD is not required to monitor the following PO(s).
  • NAS nonaccess stratum
  • numPOs Number of consecutive Paging Occasions (PO) mapped to one WUS provided in system information where (numPOs>V).
  • the WUS configuration includes time-offset between the end of the WUS and start of the first PO of the numPOs POs the WD is required to monitor.
  • the time offset in subframes used to calculate the start of a subframe gO is defined as follows: for WD using DRX, it is the signalled time offsetDRX,' for WD using eDRX, it is the signalled time offset-eDRX-Short if time offset-eDRX-Long is not broadcasted; for WD using eDRX, it is the value determined according to Table 7.4- 1 if time offset-eDRX-Long is broadcasted; Table 7.4-1: Determination of GAP between end of WUS and associated
  • the same time offset applies between the end of WUS and associated first PO of the numPOs POs for all the WUS occurrences for a PTW.
  • the time offset, gO is used to calculate the start of the WUS as defined in 3GPP TS 36.213 v!5.14.0.
  • FIG. 3 is an illustration of an example use of eDRX and DRX WUS gaps for NB-IoT and LTE-M. Since WDs share POs, the network node may, in the worst case, have to transmit up to 3 WUSs for one PO. This corresponds to time offsetDRX, time offset-eDRX-Short, and time offset-eDRX-Long.
  • the objective is to specify the following set of improvements for machine-type communications for BL/CE WDs.
  • a purpose is to reduce the false paging rate, i.e., avoid a given WD unnecessarily being awoken by a WUS transmission intended for another WD.
  • This feature is referred to as 3GPP Rel-16 group WUS, or GWUS.
  • GWUS 3GPP Rel-16 group WUS
  • 3GPP Rel-17 a WUS for NR called a ‘Paging Early Indication’ (PEI) was considered.
  • PEI Paging Early Indication
  • 3GPP Rel-17 PEIs the only gainful use of 3GPP Rel-17 PEIs was for scenarios where the small fraction of WDs are in bad coverage with large synchronization error due to the use of longer DRX cycles.
  • the gain for such WDs were that with the use of PEI they would typically only have to acquire one synchronization signal block (SSB) before decoding a PEI, instead of up to 3 SSBs if PEI is not used (according to WD vendors). So, for WDs, 3GPP Rel-17, the PEI will result in increased performance.
  • SSB synchronization signal block
  • 3GPP Rel-17 PEI will also support WD grouping for false paging reduction, similar to the Rel-16 GWUS above This will provides some gains at higher paging load).
  • PEI being PDCCH-based was considered, as seen in from the next subsection, making it much less interesting for WUR (i.e. the main baseband receiver is required for decoding PEI).
  • 3GPP Rel-18 there has been interest in introducing WUR for NR.
  • the only specification support needed to be able to use a WUR in the WD is the specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO (to allow the WD to start up the main receiver). Therefore, the main difference between 3GPP Rel-17 and 3GPP Rel-18, is that the PEI in the WUS in 3GPP Rel-18 is not PDCCH-based, and allows for a simpler and low power receiver.
  • the WUR may use simple modulation and detection techniques (e.g., using on-off keying, (OOK) modulation and non-coherent detection).
  • OOK on-off keying
  • 5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, WD energy efficiency is also important to 5G.
  • 5G devices may have to be recharged per week or day, depending on the user’s usage time.
  • 5G devices consume tens of milliwatts in RRC idle/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is desirable for improving energy efficiency as well as for a better user experience.
  • Energy efficiency is even more important for WDs without a continuous energy source, e.g., WDs using small rechargeable and single coin cell batteries.
  • sensors and actuators are deployed extensively for monitoring, measuring, charging, etc.
  • their batteries are not rechargeable and expected to last at least few years as described in 3GPP 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 may be desired.
  • the power consumption depends on the configured length of wake-up periods, e.g., paging cycle.
  • 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.
  • fire shutters shall be closed, and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements.
  • eDRX is apparently not suitable for latency-critical use cases.
  • the intention is to study ultra-low power mechanism that can support low latency in 3GPP Rel-18, e.g. lower than eDRX latency.
  • WDs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If WDs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wakeup signal with ultra-low power consumption.
  • Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.
  • the power consumption for monitoring wake-up signal depends on the wakeup signal design and the hardware module of the wake-up receiver used for signal detecting and processing.
  • the study item includes the following:
  • KPIs [RANI] o Primarily target low-power WUS/WUR for powersensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables
  • a benefit of WUR is to reduce the energy consumption of the receiver, such that unless there is paging and data for the WD, the WD can remain in a power saving state. This will extend the battery life of the device and/or enable shorter downlink latency (shorter DRX) at a fixed battery life.
  • the WUR power can be low enough ( ⁇ 3 uW) that this can, in combination with energy harvesting, enable the WUR to be continuously on (i.e., DRX or duty-cycling is not used) without the need for a battery. This can be considered a key enabler of batteryless devices towards 6G.
  • an IEEE WUR is only enabled in stations and not in access points (APs), that is for downlink communication only.
  • the AP advertises that it has WUR operational capability, along with WUR configuration parameters and other information.
  • the band/channel of the WUR for these advertisements can be different from the band/channel used for data reception using the main receiver, e.g., the WUR operates in a 2.4 GHz band, data reception by the main receiver occurs in the 5 GHz band.
  • the WUR operating channel is advertised in the beacon, and that the WUR discovery operating channel may be different from the WUR operating channel.
  • Stations can then request to be configured with a WUR mode of operation.
  • This request has to be granted by the AP, and in case it is granted, the station is further configured/setup for the WUR mode of operation.
  • the configuration may only be valid for the connection to the associated AP, and further the configuration must be tom down/de-configured if the WUR is not used again.
  • Both continuous WUR operation (receiver open all the time) and duty-cycled WUR operation (receiver only open during preconfigured time slots) are supported. For the latter, the length of the duty-cycles and on-time during wake up is part of the WUR configuration.
  • the IEEE WUR operation mode is a “sub-state” of the regular operation and upon the detection of a WUS transmission from the AP, the station will resume the power saving mechanism it was configured with before entering the WUR operation mode. That is, the IEEE has specified a number of different power saving mechanisms. Also, if duty -cycled monitoring of the downlink has been configured for the station, the station will switch to that upon detection of the WUS. Thus, unlike the specified 3GPP mechanism which only covers paging, the WD will continue to monitor PDCCH if WUS is detected. In this way the IEEE WUR functionality is more general, and stills allows for the station to, upon detection of WUS “monitor paging” condition, check the beacon from the AP for which stations there is data, or for the station to directly respond with an uplink transmission.
  • a station receiving the IEEE WUS must synchronize to the wireless medium prior to performing any transmissions. Synchronization involves using synchronization information in the beacon from the AP (typically transmitted every 100ms) or from the transmission to another station. Synchronization to the wireless medium refers to the following in IEEE 802.11 : a station changing from sleep to awake in order to transmit must perform channel clear assessment until it receives one or more frames that allow it to correctly set the virtual carrier sensing. This is to prevent collisions with transmissions from hidden nodes. Essentially, the virtual carrier sensing tells a station to defer for a time period even if the wireless medium appears to be idle, and can be set by receiving frames that indicate the duration of an ongoing frame exchange.
  • Wi-Fi typically one beacon transmission is enough to synchronize with the station (i.e., there is no need to acquire several transmission due to poor coverage).
  • the station also has to apply carrier sensing, and also possibly re-acquire channel sensing parameters, before uplink transmission.
  • the physical wake-up signal (WUS) in the IEEE standards contains complete frames which much be processed by the station.
  • the drawback with this design is that it requires more processing and handling and processing in the station, as compared to a simple WUR design in which there is a trigger for one pre-defined activity in case the WUS is detected.
  • the benefit is that it contains more information and the solution is more general.
  • the IEEE WUS contains information to indicate if the WUS is a WUR synchronization beacon.
  • a WUR discovery beacon, or a regular WUS (intended to wake the station up) is also included in the synchronization beacon.
  • the WUS can also contain proprietary frames, which could be used to directly turn actuators on/off.
  • the transmission uses on/off keying (OOK) modulation, using Manchester coding.
  • multi-carrier OOK which can be generated by an OFDM transmitter (i.e., the WUR can be enabled as a software upgrade in the APs) is used.
  • the WUS is 4 MHz wide, but a 20 MHz channel is reserved.
  • the WUS starts with a 20 MHz legacy preamble (to allows other stations to perform carrier sensing) followed by 4 MHz Manchester coded OOK.
  • Two data rates are supported: 62.5 kbps and 250 kbps.
  • Link adaptation is up to the AP.
  • Each packet is self-contained and includes the data rate.
  • the WUS can contain the following information: • Station ID, or group ID (grouping of stations is supported);
  • WUR beacons contain BSS-ID, synchronization information, time counter;
  • WUR discovery frames contain mobility related information to allow for lower power scan.
  • WUR synchronization beacons are used by stations to obtain rough synchronization.
  • the legacy beacon must still be acquired, and WUR discovery beacons are used to carry (legacy) mobility information to enable quick/low energy scanning. This allows stations using the WUR, to get information related to local and roaming scans for nearby APs, e.g.. synchronization signal identification (SSID) and main radio operating channels, if the channel quality should deteriorate.
  • SSID synchronization signal identification
  • the AP can indicate one or more basic service set (BSS) and BSS-ID, which has a one-to-one mapping with the assigned SSID name in which WUR is supported.
  • BSS basic service set
  • BSS-ID basic service set
  • stations do not have to scan all frequencies/channels.
  • the WUR discovery beacon contains the legacy mobility information, there is some duplication/redundancy in the broadcasted information. This allows for low power scanning, using only the WUR. Note however that mobility in IEEE is restricted to the same AP, and that hand-over between Aps, is not supported in the same way as in 3GPP. If a station in WUR operation mode moves to a new AP, it would have to move out of WUR operation mode and use the main receiver to obtain the beacon, sync, configuration, and associate to the new AP.
  • Some embodiments advantageously provide methods, systems, and apparatuses for a wake-up radio with adaptive sensitivity and power consumption.
  • a WD might be in different coverage conditions, when the WD is in good coverage, the WD may not need to have as high a sensitivity as in poor coverage. Therefore, by adaptively adjusting the required sensitivity based on the WD’s coverage, it is possible to find a solution that reduce the WD power consumption.
  • Some embodiments provide solutions for addressing WUR sensitivity-power consumption tradeoffs in various deployment scenarios.
  • some embodiments provide mechanisms to support adaptive sensitivity and power consumption for WUR to satisfy sensitivity requirements with a minimum average power consumption.
  • Some proposed mechanisms include: 1) adaptive WUR schemes, 2) WUR adaptation criteria, and 3) signaling aspects of WUR adaptation.
  • Some embodiments include mechanisms to support adaptive sensitivity and power consumption for the WUR to satisfy sensitivity requirements with a minimum average power consumption.
  • the solutions enable the use of WUR in a wide range of deployment scenarios that provide substantial WD power savings.
  • the solutions can be considered as an enabler of battery-less (zero-energy) devices towards 5G evolution and 6G.
  • a method a network node includes configuring the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, when to switch the WUR being based at least in part on at least one of a power consumption and a sensitivity of the WUR.
  • the process also includes determining a link quality between the WD and the network node, wherein the at least one parameter is determined based at least in part on the link quality.
  • the method also includes determining a WUR sensitivity parameter , wherein the at least one parameter is determined based at least in part on the WUR receiver sensitivity and the power consumption of the WUR.
  • the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD.
  • the method also includes sending the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
  • a network node for adapting a wakeup receiver, WUR, of a wireless device, WD, to conserve power.
  • the network node includes processing circuitry configured to: configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, when to switch the WUR being based at least in part on at least one of a power consumption and a sensitivity of the WUR.
  • the processing circuitry is further configured to determine a link quality between the WD and the network node and determine the at least one parameter based at least in part on the link quality. In some embodiments, the processing circuitry is further configured to determine a WUR sensitivity parameter and determine the at least one parameter based at least in part on the WUR receiver sensitivity and power consumption of the WUR. In some embodiments, the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD. In some embodiments, the network node also includes a radio interface configured to send the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
  • a method in a WD includes switching the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR.
  • switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR.
  • switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR.
  • switching between the low power state and the high power state includes changing a state of a filter of the WUR.
  • switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR.
  • switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR.
  • switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR.
  • the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD.
  • a wireless device having a wakeup receiver, WUR, and being configured to communicate with a network node.
  • the WD includes processing circuitry configured to: switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR.
  • switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR.
  • switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR.
  • switching between the low power state and the high power state includes changing a state of a filter of the WUR.
  • switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR.
  • switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR.
  • switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR.
  • the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD.
  • FIG. 1 is an illustration of a wakeup signal (WUS) and a paging occasion (PO);
  • FIG. 2 is an illustration of a WUS for narrow band Internet of things (NB-IoT) and LTE-M;
  • FIG. 3 is an illustration of the use of eDRX and DRX WUS gaps for NB-IoT and LTE-M;
  • FIG. 4 illustrates power versus sensitivity for low power radios. In the design of a WUR;
  • FIG. 5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 6 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 11 is a flowchart of an example process in a network node for a wake-up radio with adaptive sensitivity and power consumption according to principles set forth herein;
  • FIG. 12 is a flowchart of an example process in a wireless device for a wakeup radio with adaptive sensitivity and power consumption according to some embodiments of the present disclosure
  • FIG. 13 is a block diagram of a radio receiver structure; and FIG. 14 illustrates multiple LN As each with different sensitivity and power consumption.
  • a design challenge in receivers for loT applications is to minimize the power consumption with an adequate sensitivity level.
  • receiver sensitivity is an important parameter as it provides the lowest power level at which the receiver can detect a WUS.
  • high sensitivity requires more power consuming electronics at the receiver side.
  • low sensitivity for the same communication range will require high radiated power at the transmitter side. Because of this, sensitivity requirements often lead to over-design to ensure reliable communication in adverse conditions.
  • the WUR is used to trigger a higher power radio, ideally the WUR and the higher power radio should have the same range.
  • the tradeoff between sensitivity/cov erage and energy consumption of WUR is shown in FIG. 4, based on the existing low-power radio designs. As can be seen, for every 20 dB improvement in sensitivity, there is at least a lOx increase in power consumption.
  • FIG. 4 illustrates power versus sensitivity for low power radios.
  • the WUR sensitivity should result in a coverage which matches that of the main radio. If not, a WD would effectively have a coverage reduction when WUR operation is configured for the WD, and the WD would become unreachable at the legacy cell-edge since WUS could not be received there.
  • low WURs should be efficiently employed in various deployment scenarios while satisfying the coverage requirements.
  • the main radio has more advanced capabilities compared to a low complexity WUR, the main radio has a higher sensitivity. For instance, to support 5G NR WDs in macro deployment scenarios, the receiver sensitivity should be around -100 dBm (especially for WDs located at the cell-edge).
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node,
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • LME Customer Premises Equipment
  • NB-IOT Narrowband loT
  • radio network node can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node Multi-cell/multicast Coordination Entity
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • Some embodiments provide a wake-up radio with adaptive sensitivity and power consumption.
  • FIG. 5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 5 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a network node 16 is configured to include a parameter configuration unit 32 which is configured to configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state.
  • a wireless device 22 is configured to include a WUR switching unit 34 which is configured to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include a parameter configuration unit 32 which is configured to configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state.
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 that includes a main receiver 83 that is configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the main receiver 83 of the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the WD 22 further includes processing circuitry 84 which is configured to communicate with the main radio receiver and a WUR 85.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the processing circuitry 84 of the wireless device 22 may include a WUR switching unit 34 which is configured to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.
  • a WUR switching unit 34 which is configured to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 5.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 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 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
  • FIGS. 5 and 6 show various “units” such as parameter configuration unit 32, and WUR switching unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 5 and 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 6.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6.
  • the WD 22 receives input data provided by the host computer 24 (Block SI 16).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the WD 22 provides user data (Block S120).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6.
  • the network node 16 receives user data from the WD 22 (Block SI 28).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • FIG. 7 is a flowchart of an example process in a network node 16 for a wakeup radio with adaptive sensitivity and power consumption.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the parameter configuration unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to configure the WD 22 with at least one parameter indicative of when to switch the WUR 85 between a low power state and a high power state, the WUR 85 being configured to consume less power in the low power state than in the high power state, when to switch the WUR 85 being based at least in part on at least one of a power consumption and a sensitivity of the WUR 85 (Block SI 34).
  • the process also includes determining a link quality between the WD 22 and the network node 16, wherein the at least one parameter is determined based at least in part on the link quality.
  • the method also includes determining a WUR sensitivity parameter, wherein the at least one parameter is determined based at least in part on the WUR receiver sensitivity and power consumption of the WUR 85.
  • the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD..
  • the method also includes sending the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
  • FIG. 8 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the WUR switching unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to switch the WUR 85 between a low power state and a high power state, the WUR 85 being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a sensitivity of the WUR 85 (Block S136).
  • switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a filter of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR 85.
  • switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR 85.
  • the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD 22. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD 22.
  • the wake up receiver (WUR) 85 is used for detection of a wake-up signal (WUS) in order to wake up the main (baseband/higher power) receiver to detect an incoming message.
  • the WUS is first received by the RF frontend via the antenna and then passes through the matching network that filters and boosts the incoming WUS.
  • an envelope detector may need to be employed for signal detection and conversion to baseband signal making the circuit simpler and energy efficient.
  • the signal passes through the amplifiers, often the low noise amplifier (LNA) for increasing the sensitivity of the receiver by amplifying weak signals while meeting noise requirements.
  • LNA low noise amplifier
  • the LNA dominates in terms of power consumption. Therefore, while designing an ultra-low-power WUR 85, it may be desirable to eliminate some, if not all, of these power-hungry RF components, to reduce power consumption.
  • FIG. 13 is a block diagram of an example radio receiver structure constructed in accordance with the principles of the present disclosure.
  • WUR 85 may include low noise amplifiers (LNAs) 94, a mixer 96, a local oscillator 98, active filters 100 with sharp frequency responses, phase locked loop (PLL) circuitry (not shown) with accurate crystal frequency references.
  • LNAs low noise amplifiers
  • PLL phase locked loop
  • An LNA 94 improves receiver sensitivity but significantly increases power consumption by the WUR 85. In general, it is desired to minimize or eliminate RF amplification stages (LNA 94, local oscillator (LO) 98, passive mixer 96).
  • ADC 102 analog to digital convertor which converts a continuoustime and continuous-amplitude analog signal to a discrete-time and discrete-amplitude digital signal.
  • LNA 94 low noise amplifier which amplifies very low-power signal without significantly degrading its signal-to-noise ratio.
  • Mixers 96 are used for frequency conversion and are common components in modem radio frequency (RF) systems.
  • a mixer is a nonlinear electrical circuit that creates new frequencies from two signals applied to it. In its most common application, two signals are applied to a mixer, and it produces new signals as the sum and difference of the original frequencies.
  • a mixer converts RF power at one frequency into power at another frequency to make signal processing easier and less expensive.
  • the parameters of the WUR 85 are tuned based on the coverage condition and power consumption of the WUR 85. Specifically, given the sensitivity requirements, the WUR power consumption may be minimized by adjusting the parameters of power-hungry components of the WUR 85. By adaptively adjusting the receiver parameters, the average power consumption of WUR 85 can be minimized. To control how much the sensitivity can be reduced, an expression or function can be used to estimate the WUR sensitivity/cov erage as a function of the receiver parameters.
  • WUR_sensitivity function(receiver parameters) The above function can be linear or non-linear, and time-dependent.
  • the WD 22 (or network node 16 (gNB) if the receiver parameters to be used are signaled to the WD 22) does not reduce the power consumption of the WUR 85 so much such that coverage is lost.
  • gNB network node 16
  • LNA may not use LNA 94 when it does not require high sensitivity.
  • a mechanism for on/off switching of LNA can be employed; o
  • a variable-gain LNA 94 can be used to reach a desired sensitivity with the minimum power consumption; and/or o
  • FIG. 14 illustrates an example of a WUR 85 having multiple LNAs 94, each with different sensitivity and power consumption.
  • the LNAs 94 can be used to enable adjustment the overall sensitivity -power consumption tradeoff.
  • the WUR 85 can switch between different LNAs 94 based on the scenario.
  • LNAs 94 with identical sensitivity and power consumption can be used one after the other to allow adjusting the overall sensitivity -power consumption tradeoff.
  • the WUR 85 can bypass LNAs 94 based on the applicable scenario.
  • the accuracy of frequency generation and local oscillator can be reduced for power saving.
  • the WUR 85 can switch between low-accuracy and high-accuracy local oscillators to reduce the average power consumption;
  • Filter parameters such as roll-off factors can be adjusted based on the deployment scenario, coexistence aspects, and acceptable out-of-band emissions to reduce the WUR power consumption;
  • Variable receiver bandwidth can be considered for the WUR 85 to control the tradeoff between sensitivity/cov erage and power consumption;
  • sampling rate and quantization levels can be adjusted to reduce the WUR power consumption.
  • a dual-modulation WUR structure is considered in which modulation switching is applied to balance the sensitivity and power consumption.
  • a WUR 85 can have the capability of detecting both OOK and frequency shift keying (FSK) modulation schemes.
  • FSK modulation may be used; otherwise the OOK with lower power consumption may be used.
  • modulation switching needs to be done on both receiver and transmitter.
  • modulation other than OOK and FSK may be employed.
  • the modulation parameters may be adapted based on the receiver sensitivity and power consumption
  • the WUR operation mode is adapted based on the coverage and power consumption.
  • WUR operation can be continuous (i.e. , always on) or duty-cycled (periodically or aperiodically on and off).
  • the WUR 85 can have a hybrid mode of operation to adjust its power consumption in different scenarios with different sensitivity requirements.
  • the WUR operation mode is adopted based on the duty-cycle or DRX cycle length. That is, the average WUR power over a longer period of time is modified through higher layer configuration of the how often the WD 22 should wake up and use the WUR 85 to monitor for incoming transmissions (note that in this case the coverage or sensitivity is not reduced).
  • WUR adaptation is performed based on the deployment scenario (e.g., indoor, urban, etc.) and location of the WD 22.
  • WUR adaptation is performed based on the mobility pattern of the WD 22. For example, as the WD 22 moves towards the cell edge the WUR adaptation is done to increase the WUR 85 sensitivity.
  • the WUR adaptation can be triggered when the propagation environment/ characteristic changes due to the WD 22 mobility (e.g., moving from indoor to outdoor).
  • WUR adaptation is performed based on the WD 22 being in certain coverage as may be characterized, for example, by variations of RSRP (Reference Signal Received Power) and/or RSRQ (Reference Signal Received Quality). Furthermore, the adaptation can be determined based on the existing RSRP/ RSRQ map associated with the environment.
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • WUR adaptation is performed based on WD measurement reports, e.g., channel state information (CSI), radio resource management (RRM) measurement reports, etc.
  • WD measurement reports e.g., channel state information (CSI), radio resource management (RRM) measurement reports, etc.
  • the WUR adaption is done according to the WUR battery status. This is particularly useful when the WUR 85 relies on energy harvesting where the amount of available energy is time dependent.
  • the WUR adaption is done based on the main radio WD type and capability.
  • the WUR 85 used for WDs with effectively lower sensitivity can have lower sensitivity.
  • the WUR adaption is done based on the interference experienced by the WD 22.
  • the good link quality in the uplink (UL) and bad link quality in the downlink (DL) can be used for interference detection in the WD 22. Comparing UL and DL link quality is particularly useful for interference detection to adapt the WUR circuit.
  • the WUR adaption for enhanced sensitivity can only be triggered if the coverage enhancement techniques do not provide sufficient sensitivity. For instance, WUR adaption may be triggered after K repetitions. Moreover, the WUR adaptation parameters/schemes and the number of time repetitions, can be jointly adjusted to achieve a desired sensitivitypower consumption tradeoff.
  • the WUR adaptation can be done in at least one of the following ways:
  • WUR adaptation is done every T slots.
  • the periodicity T can be adjusted to balance between sensitivity and power consumption.
  • an LNA can be periodically switched on or off;
  • the WUR 85 adapts as a function of time given the time varying nature of required sensitivity and power consumption. This can be determined based on, for example, WD mobility patterns and distance to the transmitter of the network node 16.
  • the network periodically sends the information about WUR adaptation mechanisms and parameters to the WUR 85 periodically.
  • Such information can be a part of the transmitted WUS or it can be transmitted via a dedicated signaling.
  • the network sends the information about WUR adaptation mechanisms and parameters to the WUR 85 when the WD 22 is in a good coverage condition, thus being reachable without any need for increasing WUR power consumption. In good coverage conditions, additional information bits can be transmitted to the WUR 85 to convey rules for efficient WUR operations.
  • the network sends the information about WUR adaptation mechanisms and parameters and the network prediction about the required WUR sensitivity and its power consumption to the WUR 85.. In this case, there is a time gap between receiving the WUR adaptation information and when the WUR adaption should be performed. For instance, the network informs the WUR 85 about the adaptation mechanism N slots in advance. The value of N can be configurable by the network or pre-defined to the WUR 85.
  • the WD 22 determines which receiver parameters to apply for WUR 85 based on any combination of the following:
  • o Base-station (network node 16) power classification e.g. if the network node 16 (gNB) is a micro, macro, or pico base station, based on RAN4 specified classes
  • o RSRP/RSRQ measurements or similar measurements on any DL signal, from which the WD 22 can estimate it current coverage (open-loop);
  • o Power-control command e.g. if the network node 16 (gNB) is a micro, macro, or pico base station, based on RAN4 specified classes
  • o RSRP/RSRQ measurements or similar measurements on any DL signal, from which the WD 22 can estimate it current coverage (open-loop);
  • o Power-control command o Timing Advance configured for the WD 22; o Signal to interference plus noise ratio (SINR) measurement;
  • New signaling from gNB o Explicit receiver parameters to apply (UE-specific or cellspecific); o WUR configuration or type to apply in the cell (cellspecific). E.g. indication of cell size.; o WUR configuration or type to apply for the WD 22 (UE- specific). E.g. if the WD 22 is stationary; o Coverage mapping to WUR parameters to apply;
  • ⁇ could be semi-statically configured in SI or hard coded in specification
  • WUR parameters could also include whether the WD 22 should use the WUR 85 at all or fall back to legacy operation (monitoring DL with the main receiver 83).
  • Table 1 RSRP thresholds and WUR configurations.
  • RSRP thresholds e.g., A, B, C
  • RSRP thresholds can be presented in linear or dB scale. Also, they can be a function of time. In addition, multiple sets/tables of RSRP thresholds can be considered to increase the deployment flexibility and support a wide range of WUR configurations.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
  • some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Abstract

A method, system and apparatus for a wake-up receiver (WUR) with adaptive sensitivity and power consumption. According to one aspect, a wireless device (WD) having a WUR and being configured to communicate with a network node is provided. The WD includes processing circuitry configured to switch the WUR between a low power state and a high power state, the WUR (85) being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.

Description

WAKE-UP RADIO WITH ADAPTIVE SENSITIVITY AND POWER CONSUMPTION
TECHNICAL FIELD
The present disclosure relates to wireless communications, and in particular, to a wake-up radio with adaptive sensitivity and power consumption.
BACKGROUND
The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. Sixth Generation (6G) wireless communication systems are also under development.
A purpose of a wake-up receiver (WUR), sometimes also referred to as ‘wake-up radio’, is to enable a low power receiver in WDs that operates while the main receiver of the WD is asleep. In cases where the WUR detects a wake-up signal (WUS), the WUS wakes up the main receiver to detect an incoming message, typically a paging message. For example, a physical downlink control channel (PDCCH) in paging occasions (PO) may be detected by the main receiver which schedules a paging message on a physical downlink shared channel (PDSCH). A benefit of employing a WUR is lower energy consumption and longer device battery life at the WD. At a fixed energy consumption, the downlink latency can be reduced (shorter discontinuous reception (DRX)/duty-cycles and more frequent checks for incoming transmissions).
FIG. 1 is an illustration of an example wakeup signal (WUS) and a paging occasion (PO). In 3GPP Technical Release 15 (3GPP Rel-15, e.g., Technical Standard 36 TS 300, v!5.12.0), a WUS was specified for narrowband Internet of things (NB- loT) and LTE-M. The motivation for defining the WUS is to reduce WD energy consumption. Since, with the coverage enhancement, PDCCH could be repeated many times and the WUS is relatively much shorter, a shorter reception time at the WD is obtained. The logic is that a WD would check for a WUS a certain time before its PO, and only if a WUS is detected the WD would continue to check for PDCCH in the PO, and if not, which is most of the time, the WD can go back to a sleep state to conserve energy. Due to the coverage enhancements, the WUS can be of variable length depending on the WD’s coverage.
FIG. 2 is an illustration of an example WUS for narrow band Internet of things (NB-IoT) and LTE-M. A WUS is based on the transmission of a short signal that indicates to the WD that it should continue to decode the downlink (DL) control channel, e.g., full narrowband PDCCH (NPDCCH) for NB-IoT. If the WUS is absent, (discontinuous transmission (DTX), i.e., the WD does not detect the WUS) then the WD can go back to sleep without decoding the downlink (DL) control channel. The decoding time for a WUS is considerably shorter than that of the full NPDCCH since it essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces WD power consumption and leads to longer WD battery life. The WUS would be transmitted only when there is a paging for the WD. But if there is no paging for the WD, then the WUS will not be transmitted (i.e., implying a discontinuous transmission, DTX) and the WD would go back to deep sleep, e.g., upon detecting DTX instead of the WUS. This is illustrated in FIG. 1, where white blocks indicate possible WUS and PO positions whereas the black boxes indicate actual WUS and PO positions. In 3GPP Rel-15, a WUS is considered in several parts of the 3GPP LTE Technical Standards, 36-series standard, e.g., 3GPP TS 36.211 V15.14.0, 3GPP TS 36.213 V15.14.0, 3GPP TS 36.304 V15.14.0 and 3GPP TS 36.331 V15.14.0.
A WD will report its WUS capability to the network, and WUS gap capability (see below). Further, WUS information was added to the paging message/request from the mobile management entity (MME) to network node (eNB). The network node (eNB) will use the WUS for paging the WD when the WUS is enabled in the cell (i.e. WUS-Conflg present in SI), and the WD supports WUS detection according to the wakeUpSignal-r 15 WD capability (see also the description of WUS gap below). The WUS was introduced for both LTE-M and NB-IoT with support for both DRX and eDRX, For support of DRX, a 1-to-l mapping between the WUS and the PO is implemented. For support of eDRX, with the possible configuration of 1-to-N (many) POs the network node eNB can configure in one WUS gap for WDs using DRX, and another WUS gap for WDs using eDRX See 3GPP TS 36.331 vl 5.14.0, which provides as follows:
WUS-Config-NB information element
WUS-Config-NB-rl5 ::= SEQUENCE { maxDurationF actor-r 15 WU S -MaxDurationF actor-NB - rl5, numP0s-rl5 ENUMERATED {nl, n2, n4}
DEFAULT nl, numDRX-Cy clesRelaxed-r 15 ENUMERATED {nl, n2, n4, n8}, time offsetDRX-rl5 ENUMERATED {ms40, ms80, ms 160, ms240}, time offset-eDRX-Short-rl5 ENUMERATED {ms40, ms 80, ms 160, ms240}, time offset-eDRX-Long-rl5 ENUMERATED {ms 1000, ms2000} OPTIONAL, - Need OP
Figure imgf000004_0001
WUS-ConfigPerCarrier-NB-rl5 : := SEQUENCE { maxDurationF actor-r 15 WU S -MaxDurationF actor-NB - rl5
Figure imgf000004_0002
WUS-MaxDurationFactor-NB-rl5 : := ENUMERATED {onel28th, one64th, one32nd, onel6th, oneEighth, oneQuarter, oneHalf} WUS-Config-NB field descriptions time offsetDRX
When DRX is used, non-zero gap from the end of the configured maximum WUS duration to the associated PO, see 3GPP TS 36.304 V15.14.0, clause 7.4 and 3GPP TS 36.211. In milliseconds, value ms40 corresponds to 40ms, value ms80 corresponds to 80 ms, and so on. time offset-eDRX-Short
When eDRX is used, the short non-zero gap from the end of the configured maximum WUS duration to the associated PO, see 3GPP TS 36.304 vl5.14.0, clause 7.4 and 3GPP TS 36.211 V15.14.0. In milliseconds, value ms40 corresponds to 40ms, value ms80 corresponds to 80 ms and so on.
Evolved universal terrestrial radio access network (E-UTRAN) configures time offset-eDRX-Short to a value longer than or equal to time offsetDRX. time offset-eDRX-Long
When eDRX is used, the long non-zero gap from the end of the configured maximum WUS duration to the associated PO, see 3GPP TS 36.304 v!5.14.0, clause 7.4 and 3GPP TS 36.211 V15.14.0. In milliseconds, value mslOOO corresponds to 1000 ms, value ms2000 corresponds to 2000 ms.
The WD capabilities can also indicate the minimum WUS gaps required for the WD to be able to decode PDCCH in the associated PO, for DRX and eDRX, respectively [3GPP TS 36.331 vl5.14.0], UE-RadioPaginglnfo-NB information element
UE-RadioPagingInfo-NB-rl3 ::= SEQUENCE { ue-Category-NB-rl 3 ENUMERATED {nbl }
OPTIONAL,
• • • 5 [[ multiCarrierPaging-rl4 ENUMERATED {true}
OPTIONAL
]], [[ mixedOperationMode-rl5 ENUMERATED
{supported} OPTIONAL, wakeUpSignal-r!5 ENUMERATED {true}
OPTIONAL, wakeUpSignalMinGap-eDRX-rl5 ENUMERATED {ms40, ms240, ms 1000, ms2000} OPTIONAL, multiCarrierPagingTDD-rl5 ENUMERATED {true} OPTIONAL ]], [[ ue-Category-NB-rl6 ENUMERATED {nb2}
OPTIONAL, groupWakeUpSignal-rl6 ENUMERATED {true}
OPTIONAL, groupWakeUpSignalAltemation-rl6 ENUMERATED {true} OPTIONAL ]]
Figure imgf000006_0001
wake UpSignalMin G p-eDRX indicates the minimum gap the WD supports between WUS or group wake up signal (GWUS) and associated PO in case of eDRX in frequency division duplex (FDD), as specified in 3GPP TS 36.304 V15.14.0. Value ms40 corresponds to 40 ms, value ms240 corresponds to 240 ms and so on. If this field is included, the WD shall also indicate support for WUS or GWUS for paging in DRX.
In 3GPP Rel-15, a longer WUS gap of Is or 2s was introduced to enable the use of WUR. That is, starting up the main baseband receiver if a WUR is used for the detection of the WUS may take a long time for which the longer WUS gap is provided. If this is supported in the cell, the network node would include time offset- eDRX-Long in the WUS-Config in system information (SI). In 3GPP TS 36.304 V15.14.0, the WD behavior for monitoring paging with WUS is specified, and in Table 7.4-1, which WUS time gap the WD (and eNB) should apply is indicated and depends on the reported WD capability: Paging with Wake Up Signal Paging with Wake Up Signal is only used in the cell in which the WD most recently entered the RRC IDLE state triggered by: reception of RRCEarlyDataCompletc, or reception of RRCConnectionRelease not including noLastCellUpdate,' or reception of RRCConnectionRelease including noLastCellUpdate and the WD was using (G)WUS in this cell prior to this RRC connection attempt.
If the WD is in RRC IDLE state, the WD is not using GWUS according to clause 7.5 and the WD supports WUS, and the WUS configuration is provided in system information, then the WD shall monitor the WUS using the WUS parameters provided in System Information. When DRX is used and the WD detects WUS the, WD shall monitor the following PO. When extended DRX is used and the WD detects WUS, the WD shall monitor the following numPOs POs or until a paging message including the WD's nonaccess stratum (NAS) identity is received, whichever is earlier. If the WD does not detect the WUS, the WD is not required to monitor the following PO(s). If the WD missed a WUS occasion (e.g., due to cell reselection), the WD monitors every PO until the start of next WUS or until the paging transmission window (PTW) ends, whichever is earlier. numPOs = Number of consecutive Paging Occasions (PO) mapped to one WUS provided in system information where (numPOs>V).
The WUS configuration, provided in system information includes time-offset between the end of the WUS and start of the first PO of the numPOs POs the WD is required to monitor. The time offset in subframes used to calculate the start of a subframe gO (see 3GPP TS 36.213 V15.14.0), is defined as follows: for WD using DRX, it is the signalled time offsetDRX,' for WD using eDRX, it is the signalled time offset-eDRX-Short if time offset-eDRX-Long is not broadcasted; for WD using eDRX, it is the value determined according to Table 7.4- 1 if time offset-eDRX-Long is broadcasted; Table 7.4-1: Determination of GAP between end of WUS and associated
PO
Figure imgf000008_0001
The time offset is used to determine the actual subframe gO as follows (taking into consideration resultant system frame number (SFN) and/or hyper-SFN (H-SFN) wrap-around of this computation): gO = PO - time offset, where PO is the Paging Occasion subframe as defined in clause 7.1.
For the WD using eDRX, the same time offset applies between the end of WUS and associated first PO of the numPOs POs for all the WUS occurrences for a PTW.
The time offset, gO, is used to calculate the start of the WUS as defined in 3GPP TS 36.213 v!5.14.0.
In essence, the WD will only use WUR, or time offset-eDRX-Long, if it is capable of starting up the main receiver as quickly as indicated by the value used in SI. If not, it will fall back to using time offset-eDRX-Short (without WUR). FIG. 3 is an illustration of an example use of eDRX and DRX WUS gaps for NB-IoT and LTE-M. Since WDs share POs, the network node may, in the worst case, have to transmit up to 3 WUSs for one PO. This corresponds to time offsetDRX, time offset-eDRX-Short, and time offset-eDRX-Long.
WUS WD grouping objective in 3 GPP Rel-16
In a 3GPP Rel-16 work item descriptions (WID), there was consideration of further development of the WUS to also include WD grouping, such that the number of WDs that are triggered by a WUS is further narrowed down to a smaller subset of the WDs that are associated with a specific paging occasion (PO):
The objective is to specify the following set of improvements for machine-type communications for BL/CE WDs.
Improved DL transmission efficiency and/or WD power consumption:
•
• Specify support for WD-group wake-up signal (WUS) [RANI, RAN2, RAN4]
A purpose is to reduce the false paging rate, i.e., avoid a given WD unnecessarily being awoken by a WUS transmission intended for another WD. This feature is referred to as 3GPP Rel-16 group WUS, or GWUS. However, this is not directly related to WURs and will not further be explained here.
3GPP Rel-17 NR PEI
In 3GPP Rel-17, a WUS for NR called a ‘Paging Early Indication’ (PEI) was considered. However, since at the time, no coverage enhancement was specified for NR, the only gainful use of 3GPP Rel-17 PEIs was for scenarios where the small fraction of WDs are in bad coverage with large synchronization error due to the use of longer DRX cycles. The gain for such WDs were that with the use of PEI they would typically only have to acquire one synchronization signal block (SSB) before decoding a PEI, instead of up to 3 SSBs if PEI is not used (according to WD vendors). So, for WDs, 3GPP Rel-17, the PEI will result in increased performance.
3GPP Rel-17 PEI will also support WD grouping for false paging reduction, similar to the Rel-16 GWUS above This will provides some gains at higher paging load). In RAN#93e, PEI being PDCCH-based was considered, as seen in from the next subsection, making it much less interesting for WUR (i.e. the main baseband receiver is required for decoding PEI).
3 GPP Rel- 18 NR WUR
In 3GPP Rel-18, there has been interest in introducing WUR for NR. As explained above, the only specification support needed to be able to use a WUR in the WD, is the specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO (to allow the WD to start up the main receiver). Therefore, the main difference between 3GPP Rel-17 and 3GPP Rel-18, is that the PEI in the WUS in 3GPP Rel-18 is not PDCCH-based, and allows for a simpler and low power receiver. For example, the WUR may use simple modulation and detection techniques (e.g., using on-off keying, (OOK) modulation and non-coherent detection).
In 3GPP Rel-18, a study item on “low-power wake-up signal and receiver for NR” was approved. The relevant justification and objective sections are copied below:
Justification
5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, WD energy efficiency is also important to 5G. Currently, 5G devices may have to be recharged per week or day, depending on the user’s usage time. In general, 5G devices consume tens of milliwatts in RRC idle/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is desirable for improving energy efficiency as well as for a better user experience.
Energy efficiency is even more important for WDs without a continuous energy source, e.g., WDs 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 3GPP 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 may be desired.
The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, eDRX cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment uses, fire shutters shall be closed, and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in 3GPP Rel-18, e.g. lower than eDRX latency.
Currently, WDs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If WDs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wakeup signal with ultra-low power consumption. Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.
The power consumption for monitoring wake-up signal depends on the wakeup signal design and the hardware module of the wake-up receiver used for signal detecting and processing.
The study should primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g./smart glasses, smart phones.
Objective of System Information (SI)
As opposed to the work on WD power savings in previous releases, this study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy WDs. Solutions should target substantial gains compared to the existing Rel-15/16/17 WD power saving mechanisms. Other aspects such as detection performance, coverage, WD complexity, should be covered by the evaluation.
The study item includes the following:
• Identify evaluation methodology (including the use cases) &
KPIs [RANI] o Primarily target low-power WUS/WUR for powersensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables
■ Other use cases are not precluded
• Study and evaluate low-power wake-up receiver architectures [RAN1, RAN4]
• Study and evaluate wake-up signal designs to support wake-up receivers [RAN 1 , RAN4]
• Study and evaluate LI procedures and higher layer protocol changes needed to support the wake-up signals [RAN2, RANI]
• Study potential WD power saving gains compared to the existing Rel-15/16/17 WD 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 WDs, network coverage/capacity/resource overhead should be included in the study [RANI] o Note: The need for RAN2 evaluation will be triggered by RANI when necessary.
A benefit of WUR is to reduce the energy consumption of the receiver, such that unless there is paging and data for the WD, the WD can remain in a power saving state. This will extend the battery life of the device and/or enable shorter downlink latency (shorter DRX) at a fixed battery life. For short-range communication, the WUR power can be low enough (~3 uW) that this can, in combination with energy harvesting, enable the WUR to be continuously on (i.e., DRX or duty-cycling is not used) without the need for a battery. This can be considered a key enabler of batteryless devices towards 6G.
IEEE WUR
In standards considered by the Institute of Electrical and Electronics Engineers (IEEE), support for a WUR has been specified to a greater extent than in 3 GPP standards. The focus was on a low power WUR and the design uses WUR not only for receiving the WUS, but for control signaling, such as synchronization and for mobility. This allows the stations (corresponding to WDs in 3GPP) to only use the WUR when there is no user-plane data transmission ongoing.
Similar to the 3GPP solution, an IEEE WUR is only enabled in stations and not in access points (APs), that is for downlink communication only. The AP advertises that it has WUR operational capability, along with WUR configuration parameters and other information. The band/channel of the WUR for these advertisements can be different from the band/channel used for data reception using the main receiver, e.g., the WUR operates in a 2.4 GHz band, data reception by the main receiver occurs in the 5 GHz band. Also note that he WUR operating channel is advertised in the beacon, and that the WUR discovery operating channel may be different from the WUR operating channel. Stations can then request to be configured with a WUR mode of operation. This request has to be granted by the AP, and in case it is granted, the station is further configured/setup for the WUR mode of operation. The configuration may only be valid for the connection to the associated AP, and further the configuration must be tom down/de-configured if the WUR is not used again. Both continuous WUR operation (receiver open all the time) and duty-cycled WUR operation (receiver only open during preconfigured time slots) are supported. For the latter, the length of the duty-cycles and on-time during wake up is part of the WUR configuration.
Unlike the 3GPP solution, the IEEE WUR operation mode is a “sub-state” of the regular operation and upon the detection of a WUS transmission from the AP, the station will resume the power saving mechanism it was configured with before entering the WUR operation mode. That is, the IEEE has specified a number of different power saving mechanisms. Also, if duty -cycled monitoring of the downlink has been configured for the station, the station will switch to that upon detection of the WUS. Thus, unlike the specified 3GPP mechanism which only covers paging, the WD will continue to monitor PDCCH if WUS is detected. In this way the IEEE WUR functionality is more general, and stills allows for the station to, upon detection of WUS “monitor paging” condition, check the beacon from the AP for which stations there is data, or for the station to directly respond with an uplink transmission.
A station receiving the IEEE WUS must synchronize to the wireless medium prior to performing any transmissions. Synchronization involves using synchronization information in the beacon from the AP (typically transmitted every 100ms) or from the transmission to another station. Synchronization to the wireless medium refers to the following in IEEE 802.11 : a station changing from sleep to awake in order to transmit must perform channel clear assessment until it receives one or more frames that allow it to correctly set the virtual carrier sensing. This is to prevent collisions with transmissions from hidden nodes. Essentially, the virtual carrier sensing tells a station to defer for a time period even if the wireless medium appears to be idle, and can be set by receiving frames that indicate the duration of an ongoing frame exchange. Note that in Wi-Fi, typically one beacon transmission is enough to synchronize with the station (i.e., there is no need to acquire several transmission due to poor coverage). Unlike operation in licensed bands, the station also has to apply carrier sensing, and also possibly re-acquire channel sensing parameters, before uplink transmission.
The physical wake-up signal (WUS) in the IEEE standards contains complete frames which much be processed by the station. The drawback with this design is that it requires more processing and handling and processing in the station, as compared to a simple WUR design in which there is a trigger for one pre-defined activity in case the WUS is detected. The benefit is that it contains more information and the solution is more general. The IEEE WUS contains information to indicate if the WUS is a WUR synchronization beacon. A WUR discovery beacon, or a regular WUS (intended to wake the station up) is also included in the synchronization beacon. The WUS can also contain proprietary frames, which could be used to directly turn actuators on/off. The transmission uses on/off keying (OOK) modulation, using Manchester coding. However, multi-carrier OOK which can be generated by an OFDM transmitter (i.e., the WUR can be enabled as a software upgrade in the APs) is used. The WUS is 4 MHz wide, but a 20 MHz channel is reserved. The WUS starts with a 20 MHz legacy preamble (to allows other stations to perform carrier sensing) followed by 4 MHz Manchester coded OOK. Two data rates are supported: 62.5 kbps and 250 kbps. Link adaptation is up to the AP. Each packet is self-contained and includes the data rate. In the WUR, there are two possible synchronization words used to signal the data rate.
The WUS can contain the following information: • Station ID, or group ID (grouping of stations is supported);
• Payload up to 22 bytes;
• Short frames contain only basic info; which WUR frame type + addressing;
• Ordinary frames contain control info, and in addition proprietary information;
• WUR beacons contain BSS-ID, synchronization information, time counter;
• Similar structure for WUS and WUR beacons (synchronization words indicate the data rate, the station can then detect the header, from this the station can tell if it is WUS or beacon, then check body); and/or
• WUR discovery frames contain mobility related information to allow for lower power scan.
Regarding mobility, both WUR synchronization beacons and WUR discovery beacons have been specified, which only requires the WUR to be used for reception, such that stations can stay in the WUR operation mode unless there is data transmission for the station. I.e., stations only need to switch back to legacy power saving mode (PSM) upon WUS detection or when moving to a new AP. WUR synchronization beacons are used by stations to obtain rough synchronization. For data transmission, the legacy beacon must still be acquired, and WUR discovery beacons are used to carry (legacy) mobility information to enable quick/low energy scanning. This allows stations using the WUR, to get information related to local and roaming scans for nearby APs, e.g.. synchronization signal identification (SSID) and main radio operating channels, if the channel quality should deteriorate.
That is, in the WUR discovery beacon the AP can indicate one or more basic service set (BSS) and BSS-ID, which has a one-to-one mapping with the assigned SSID name in which WUR is supported. Thus, stations do not have to scan all frequencies/channels. Since the WUR discovery beacon contains the legacy mobility information, there is some duplication/redundancy in the broadcasted information. This allows for low power scanning, using only the WUR. Note however that mobility in IEEE is restricted to the same AP, and that hand-over between Aps, is not supported in the same way as in 3GPP. If a station in WUR operation mode moves to a new AP, it would have to move out of WUR operation mode and use the main receiver to obtain the beacon, sync, configuration, and associate to the new AP.
SUMMARY
Some embodiments advantageously provide methods, systems, and apparatuses for a wake-up radio with adaptive sensitivity and power consumption.
Considering that a WD might be in different coverage conditions, when the WD is in good coverage, the WD may not need to have as high a sensitivity as in poor coverage. Therefore, by adaptively adjusting the required sensitivity based on the WD’s coverage, it is possible to find a solution that reduce the WD power consumption.
Some embodiments provide solutions for addressing WUR sensitivity-power consumption tradeoffs in various deployment scenarios. In particular, some embodiments provide mechanisms to support adaptive sensitivity and power consumption for WUR to satisfy sensitivity requirements with a minimum average power consumption. Some proposed mechanisms include: 1) adaptive WUR schemes, 2) WUR adaptation criteria, and 3) signaling aspects of WUR adaptation.
The support of WUR adaptation-based solutions for addressing WUR sensitivity -power consumption tradeoffs in various deployment scenarios.
Some embodiments include mechanisms to support adaptive sensitivity and power consumption for the WUR to satisfy sensitivity requirements with a minimum average power consumption. The solutions enable the use of WUR in a wide range of deployment scenarios that provide substantial WD power savings. The solutions can be considered as an enabler of battery-less (zero-energy) devices towards 5G evolution and 6G.
According to one aspect, a method a network node includes configuring the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, when to switch the WUR being based at least in part on at least one of a power consumption and a sensitivity of the WUR. According to this aspect, in some embodiments, the process also includes determining a link quality between the WD and the network node, wherein the at least one parameter is determined based at least in part on the link quality. In some embodiments, the method also includes determining a WUR sensitivity parameter , wherein the at least one parameter is determined based at least in part on the WUR receiver sensitivity and the power consumption of the WUR. In some embodiments, the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD. In some embodiments, the method also includes sending the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
According to another aspect, a network node for adapting a wakeup receiver, WUR, of a wireless device, WD, to conserve power is provided. The network node includes processing circuitry configured to: configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, when to switch the WUR being based at least in part on at least one of a power consumption and a sensitivity of the WUR.
According to this aspect, in some embodiments, the processing circuitry is further configured to determine a link quality between the WD and the network node and determine the at least one parameter based at least in part on the link quality. In some embodiments, the processing circuitry is further configured to determine a WUR sensitivity parameter and determine the at least one parameter based at least in part on the WUR receiver sensitivity and power consumption of the WUR. In some embodiments, the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD. In some embodiments, the network node also includes a radio interface configured to send the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
According to yet another aspect, a method in a WD includes switching the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR.
According to this aspect, in some embodiments, switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a filter of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR. In some embodiments, the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD.
According to another aspect, a wireless device, WD, having a wakeup receiver, WUR, and being configured to communicate with a network node is provided. The WD includes processing circuitry configured to: switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR.
According to this aspect, in some embodiments, switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a filter of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR. In some embodiments, the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD.
BRIEF DESCRIPTION OF THE DRAWINGS
A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:
FIG. 1 is an illustration of a wakeup signal (WUS) and a paging occasion (PO);
FIG. 2 is an illustration of a WUS for narrow band Internet of things (NB-IoT) and LTE-M;
FIG. 3 is an illustration of the use of eDRX and DRX WUS gaps for NB-IoT and LTE-M; FIG. 4 illustrates power versus sensitivity for low power radios. In the design of a WUR;
FIG. 5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;
FIG. 6 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;
FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;
FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;
FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;
FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;
FIG. 11 is a flowchart of an example process in a network node for a wake-up radio with adaptive sensitivity and power consumption according to principles set forth herein;
FIG. 12 is a flowchart of an example process in a wireless device for a wakeup radio with adaptive sensitivity and power consumption according to some embodiments of the present disclosure;
FIG. 13 is a block diagram of a radio receiver structure; and FIG. 14 illustrates multiple LN As each with different sensitivity and power consumption.
DETAILED DESCRIPTION
A design challenge in receivers for loT applications is to minimize the power consumption with an adequate sensitivity level. In WUR design, receiver sensitivity is an important parameter as it provides the lowest power level at which the receiver can detect a WUS. Generally, high sensitivity requires more power consuming electronics at the receiver side. In contrast, low sensitivity for the same communication range will require high radiated power at the transmitter side. Because of this, sensitivity requirements often lead to over-design to ensure reliable communication in adverse conditions. When the WUR is used to trigger a higher power radio, ideally the WUR and the higher power radio should have the same range. As an example, the tradeoff between sensitivity/cov erage and energy consumption of WUR is shown in FIG. 4, based on the existing low-power radio designs. As can be seen, for every 20 dB improvement in sensitivity, there is at least a lOx increase in power consumption.
FIG. 4 illustrates power versus sensitivity for low power radios. In the design of a WUR, the WUR sensitivity should result in a coverage which matches that of the main radio. If not, a WD would effectively have a coverage reduction when WUR operation is configured for the WD, and the WD would become unreachable at the legacy cell-edge since WUS could not be received there. In particular, low WURs should be efficiently employed in various deployment scenarios while satisfying the coverage requirements. However, since the main radio has more advanced capabilities compared to a low complexity WUR, the main radio has a higher sensitivity. For instance, to support 5G NR WDs in macro deployment scenarios, the receiver sensitivity should be around -100 dBm (especially for WDs located at the cell-edge). Given the fundamental tradeoff between sensitivity/coverage and power consumption, achieving high sensitivity with low power consumption for a WUR is highly challenging. This can result in a limited deployment of WURs (e.g., indoor-only), or a relatively high power consumption for a WUR, which is not desired Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to a wake-up radio with adaptive sensitivity and power consumption. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.
As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.
In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections. The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, anode external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.
In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.
Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.
Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Some embodiments provide a wake-up radio with adaptive sensitivity and power consumption.
Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
The communication system of FIG. 5 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
A network node 16 is configured to include a parameter configuration unit 32 which is configured to configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state.
A wireless device 22 is configured to include a WUR switching unit 34 which is configured to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.
Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 6. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.
The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include a parameter configuration unit 32 which is configured to configure the WD with at least one parameter indicative of when to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state.
The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 that includes a main receiver 83 that is configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The main receiver 83 of the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
The hardware 80 of the WD 22 further includes processing circuitry 84 which is configured to communicate with the main radio receiver and a WUR 85. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.
The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a WUR switching unit 34 which is configured to switch the WUR between a low power state and a high power state, the WUR being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on a power consumption condition.
In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 5.
In FIG. 6, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
In some embodiments, 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 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 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 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.
In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
Although FIGS. 5 and 6 show various “units” such as parameter configuration unit 32, and WUR switching unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 5 and 6, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 6. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).
FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
FIG. 10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 5 and 6. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block SI 28). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
FIG. 7 is a flowchart of an example process in a network node 16 for a wakeup radio with adaptive sensitivity and power consumption. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the parameter configuration unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to configure the WD 22 with at least one parameter indicative of when to switch the WUR 85 between a low power state and a high power state, the WUR 85 being configured to consume less power in the low power state than in the high power state, when to switch the WUR 85 being based at least in part on at least one of a power consumption and a sensitivity of the WUR 85 (Block SI 34).
In some embodiments, the process also includes determining a link quality between the WD 22 and the network node 16, wherein the at least one parameter is determined based at least in part on the link quality. In some embodiments, the method also includes determining a WUR sensitivity parameter, wherein the at least one parameter is determined based at least in part on the WUR receiver sensitivity and power consumption of the WUR 85. In some embodiments, the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD.. In some embodiments, the method also includes sending the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
FIG. 8 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the WUR switching unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to switch the WUR 85 between a low power state and a high power state, the WUR 85 being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a sensitivity of the WUR 85 (Block S136).
In some embodiments, switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a filter of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a state of an analog-to-digital, ADC, converter. In some embodiments, switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR 85. In some embodiments, switching between the low power state and the high power state includes changing a duty cycle of the WUR 85. In some embodiments, the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ. In some embodiments, the power consumption condition is based at least in part on a battery status of the WD 22. In some embodiments, the power consumption condition is based at least in part on an interference experienced by the WD 22.
Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for a wake-up radio with adaptive sensitivity and power consumption.
As noted above, the wake up receiver (WUR) 85 is used for detection of a wake-up signal (WUS) in order to wake up the main (baseband/higher power) receiver to detect an incoming message. The WUS is first received by the RF frontend via the antenna and then passes through the matching network that filters and boosts the incoming WUS. After input matching, for ultra-low power WUR, an envelope detector may need to be employed for signal detection and conversion to baseband signal making the circuit simpler and energy efficient. Then, the signal passes through the amplifiers, often the low noise amplifier (LNA) for increasing the sensitivity of the receiver by amplifying weak signals while meeting noise requirements. The LNA dominates in terms of power consumption. Therefore, while designing an ultra-low-power WUR 85, it may be desirable to eliminate some, if not all, of these power-hungry RF components, to reduce power consumption.
Adaptive WUR schemes
FIG. 13 is a block diagram of an example radio receiver structure constructed in accordance with the principles of the present disclosure.
WUR 85 may include low noise amplifiers (LNAs) 94, a mixer 96, a local oscillator 98, active filters 100 with sharp frequency responses, phase locked loop (PLL) circuitry (not shown) with accurate crystal frequency references. An LNA 94 improves receiver sensitivity but significantly increases power consumption by the WUR 85. In general, it is desired to minimize or eliminate RF amplification stages (LNA 94, local oscillator (LO) 98, passive mixer 96).
• ADC 102: analog to digital convertor which converts a continuoustime and continuous-amplitude analog signal to a discrete-time and discrete-amplitude digital signal. • LNA 94: low noise amplifier which amplifies very low-power signal without significantly degrading its signal-to-noise ratio.
• Mixers 96 are used for frequency conversion and are common components in modem radio frequency (RF) systems. A mixer is a nonlinear electrical circuit that creates new frequencies from two signals applied to it. In its most common application, two signals are applied to a mixer, and it produces new signals as the sum and difference of the original frequencies. A mixer converts RF power at one frequency into power at another frequency to make signal processing easier and less expensive.
In one embodiment, the parameters of the WUR 85 are tuned based on the coverage condition and power consumption of the WUR 85. Specifically, given the sensitivity requirements, the WUR power consumption may be minimized by adjusting the parameters of power-hungry components of the WUR 85. By adaptively adjusting the receiver parameters, the average power consumption of WUR 85 can be minimized. To control how much the sensitivity can be reduced, an expression or function can be used to estimate the WUR sensitivity/cov erage as a function of the receiver parameters.
WUR_sensitivity = function(receiver parameters) The above function can be linear or non-linear, and time-dependent.
In this way, it can be ensured that the WD 22 (or network node 16 (gNB) if the receiver parameters to be used are signaled to the WD 22) does not reduce the power consumption of the WUR 85 so much such that coverage is lost.
In related embodiments:
• LNA: o WUR 85 may not use LNA 94 when it does not require high sensitivity. For example, a mechanism for on/off switching of LNA can be employed; o Alternatively, a variable-gain LNA 94 can be used to reach a desired sensitivity with the minimum power consumption; and/or o FIG. 14 illustrates an example of a WUR 85 having multiple LNAs 94, each with different sensitivity and power consumption. The LNAs 94 can be used to enable adjustment the overall sensitivity -power consumption tradeoff. The WUR 85 can switch between different LNAs 94 based on the scenario.
Multiple LNAs 94 with identical sensitivity and power consumption can be used one after the other to allow adjusting the overall sensitivity -power consumption tradeoff. The WUR 85 can bypass LNAs 94 based on the applicable scenario.
• The accuracy of frequency generation and local oscillator can be reduced for power saving. For example, the WUR 85 can switch between low-accuracy and high-accuracy local oscillators to reduce the average power consumption;
• Filter parameters such as roll-off factors can be adjusted based on the deployment scenario, coexistence aspects, and acceptable out-of-band emissions to reduce the WUR power consumption;
• PLL accuracy can be reduced based on the required sensitivity to reduce the WUR power consumption;
• Variable receiver bandwidth can be considered for the WUR 85 to control the tradeoff between sensitivity/cov erage and power consumption; and/or
• For ADC, the sampling rate and quantization levels can be adjusted to reduce the WUR power consumption.
In another embodiment, a dual-modulation WUR structure is considered in which modulation switching is applied to balance the sensitivity and power consumption. For example, a WUR 85 can have the capability of detecting both OOK and frequency shift keying (FSK) modulation schemes. In scenarios with higher sensitivity requirements, FSK modulation may be used; otherwise the OOK with lower power consumption may be used. In this case, modulation switching needs to be done on both receiver and transmitter. Note that modulation other than OOK and FSK may be employed. According to principles disclosed herein, the modulation parameters may be adapted based on the receiver sensitivity and power consumption
In yet another embodiment, the WUR operation mode is adapted based on the coverage and power consumption. In general, WUR operation can be continuous (i.e. , always on) or duty-cycled (periodically or aperiodically on and off). In particular, the WUR 85 can have a hybrid mode of operation to adjust its power consumption in different scenarios with different sensitivity requirements.
In yet another embodiment, the WUR operation mode is adopted based on the duty-cycle or DRX cycle length. That is, the average WUR power over a longer period of time is modified through higher layer configuration of the how often the WD 22 should wake up and use the WUR 85 to monitor for incoming transmissions (note that in this case the coverage or sensitivity is not reduced).
WUR adaptation criteria
Different criteria can be considered for the WUR adaptation described in the previous section.
In one embodiment, WUR adaptation is performed based on the deployment scenario (e.g., indoor, urban, etc.) and location of the WD 22.
In another embodiment, WUR adaptation is performed based on the mobility pattern of the WD 22. For example, as the WD 22 moves towards the cell edge the WUR adaptation is done to increase the WUR 85 sensitivity. In addition, the WUR adaptation can be triggered when the propagation environment/ characteristic changes due to the WD 22 mobility (e.g., moving from indoor to outdoor).
In another embodiment, WUR adaptation is performed based on the WD 22 being in certain coverage as may be characterized, for example, by variations of RSRP (Reference Signal Received Power) and/or RSRQ (Reference Signal Received Quality). Furthermore, the adaptation can be determined based on the existing RSRP/ RSRQ map associated with the environment.
In another embodiment, WUR adaptation is performed based on WD measurement reports, e.g., channel state information (CSI), radio resource management (RRM) measurement reports, etc.
In yet another embodiment, the WUR adaption is done according to the WUR battery status. This is particularly useful when the WUR 85 relies on energy harvesting where the amount of available energy is time dependent.
In another embodiment, the WUR adaption is done based on the main radio WD type and capability. The WUR 85 used for WDs with effectively lower sensitivity (for example, a Redcap WD with one receiver antenna branch), can have lower sensitivity. In another embodiment, the WUR adaption is done based on the interference experienced by the WD 22. The good link quality in the uplink (UL) and bad link quality in the downlink (DL) can be used for interference detection in the WD 22. Comparing UL and DL link quality is particularly useful for interference detection to adapt the WUR circuit.
In order to improve sensitivity, coverage enchantment techniques such as repetition and re-transmissions can be used. In this regard, the WUR adaption for enhanced sensitivity can only be triggered if the coverage enhancement techniques do not provide sufficient sensitivity. For instance, WUR adaption may be triggered after K repetitions. Moreover, the WUR adaptation parameters/schemes and the number of time repetitions, can be jointly adjusted to achieve a desired sensitivitypower consumption tradeoff.
Signaling aspects of WUR adaptation
The WUR adaptation can be done in at least one of the following ways:
• Periodically: for example, WUR adaptation is done every T slots. The periodicity T can be adjusted to balance between sensitivity and power consumption. As an example, an LNA can be periodically switched on or off;
• Dynamically: WUR adaptation in an event-triggered manner;
• Continuously over time: the WUR 85 adapts as a function of time given the time varying nature of required sensitivity and power consumption. This can be determined based on, for example, WD mobility patterns and distance to the transmitter of the network node 16.
In one embodiment, the network periodically sends the information about WUR adaptation mechanisms and parameters to the WUR 85 periodically. Such information can be a part of the transmitted WUS or it can be transmitted via a dedicated signaling.
In another embodiment, the network sends the information about WUR adaptation mechanisms and parameters to the WUR 85 when the WD 22 is in a good coverage condition, thus being reachable without any need for increasing WUR power consumption. In good coverage conditions, additional information bits can be transmitted to the WUR 85 to convey rules for efficient WUR operations. In another embodiment, the network sends the information about WUR adaptation mechanisms and parameters and the network prediction about the required WUR sensitivity and its power consumption to the WUR 85.. In this case, there is a time gap between receiving the WUR adaptation information and when the WUR adaption should be performed. For instance, the network informs the WUR 85 about the adaptation mechanism N slots in advance. The value of N can be configurable by the network or pre-defined to the WUR 85.
In another embodiment, the WD 22 determines which receiver parameters to apply for WUR 85 based on any combination of the following:
• Legacy parameters: o Base-station (network node 16) power classification (e.g. if the network node 16 (gNB) is a micro, macro, or pico base station, based on RAN4 specified classes); o RSRP/RSRQ measurements, or similar measurements on any DL signal, from which the WD 22 can estimate it current coverage (open-loop); o Power-control command; o Timing Advance configured for the WD 22; o Signal to interference plus noise ratio (SINR) measurement; o UE GPS (Global Positioning System) Coordinates; o Number of HARQ which is number of hybrid automatic repeat request; o Ec/Io which is energy per chip to interference power ratio; and/or o Any other ways by which the WD 22 could estimate its coverage;
• New signaling from gNB: o Explicit receiver parameters to apply (UE-specific or cellspecific); o WUR configuration or type to apply in the cell (cellspecific). E.g. indication of cell size.; o WUR configuration or type to apply for the WD 22 (UE- specific). E.g. if the WD 22 is stationary; o Coverage mapping to WUR parameters to apply;
■ A table of RSRP-thresholds/intervals mapped to different WUR parameters;
■ Could be semi-statically configured in SI or hard coded in specification;
■ Only RSRP -thresholds is configured in SI, and the associated WUR parameters or configurations to apply hard-coded in specification; o WUR parameters could also include whether the WD 22 should use the WUR 85 at all or fall back to legacy operation (monitoring DL with the main receiver 83).
An example where RSRP -thresholds A, B, and C are configured semi- statically and are broadcast to WDs in system information, is given in Table 1 below:
Table 1: RSRP thresholds and WUR configurations.
Figure imgf000042_0001
The values of RSRP thresholds (e.g., A, B, C) can be presented in linear or dB scale. Also, they can be a function of time. In addition, multiple sets/tables of RSRP thresholds can be considered to increase the deployment flexibility and support a wide range of WUR configurations.
As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.
Abbreviations that may be used in the preceding description include:
ADC Analog to Digital Convertor
DRX Discontinuous Reception
LNA Low-noise Amplifier MIB Master Information Block
OOK On-Off Keying
PBCH Physical Broadcast Channel
PSS Primary Synchronization Signal PLL Phase Locked Loop
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
SSB Synchronization Signal Block
SSS Secondary Synchronization Signal SINR Signal to noise plus interference
WUR Wake-Up Radio
WUS Wake-Up Signal
It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:
1. A method in a network node (16) for adapting a wakeup receiver, WUR (85), of a wireless device, WD (22), to conserve power, the method comprising: configuring (SI 34) the WD (22) with at least one parameter indicative of when to switch the WUR (85) between a low power state and a high power state, the WUR (85) being configured to consume less power in the low power state than in the high power state, when to switch the WUR (85) being based at least in part on at least one of a power consumption and a sensitivity of the WUR (85).
2. The method of Claim 1, further comprising determining a link quality between the WD (22) and the network node (16), wherein the at least one parameter is determined based at least in part on the link quality.
3. The method of any of Claims 1 and 2, further comprising determining a WUR (85) sensitivity parameter, wherein the at least one parameter is determined based at least in part on the WUR (85) receiver sensitivity and the power consumption of the WUR (85).
4. The method of any of Claims 1-3, wherein the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD (22).
5. The method of any of Claims 1-4, further comprising sending the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
6. A network node (16) for adapting a wakeup receiver, WUR (85), of a wireless device, WD (22), to conserve power, the network node (16) comprising processing circuitry configured to: configure the WD (22) with at least one parameter indicative of when to switch the WUR (85) between a low power state and a high power state, the WUR (85) being configured to consume less power in the low power state than in the high power state, when to switch the WUR (85) being based at least in part on at least one of a power consumption and a sensitivity of the WUR (85).
7. The network node (16) of Claim 6, wherein the processing circuitry is further configured to determine a link quality between the WD (22) and the network node (16) and determine the at least one parameter based at least in part on the link quality.
8. The network node (16) of any of Claims 6 and 7, wherein the processing circuitry is further configured to determine a WUR sensitivity parameter and determine the at least one parameter based at least in part on the WUR receiver sensitivity and the power consumption of the WUR (85).
9. The network node (16) of any of Claims 6-8, wherein the parameter indicative of when to switch the WUR power state is based at least in part on at least one of a type of cell serving the WD (22) and a mobility pattern of the WD (22).
10. The network node (16) of any of Claims 6-9, further comprising a radio interface configured to send the at least one parameter a multiple number of time slots in advance of a time to switch between the low power state and the high power state.
11. A method in a wireless device, WD (22), having a wakeup receiver, WUR (85), and being configured to communicate with a network node (16), the method comprising: switching (SI 36) the WUR (85) between a low power state and a high power state, the WUR (85) being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR (85).
12. The method of Claim 11, wherein switching between the low power state and the high power state includes changing a state of a low noise amplifier (94) ofthe WUR (85).
13. The method of any of Claims 11 and 12, wherein switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR (85).
14. The method of any of Claims 11-13, wherein switching between the low power state and the high power state includes changing a state of a filter of the WUR (85).
15. The method of any of Claims 11-14, wherein switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR (85).
16. The method of any of Claims 11-15, wherein switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR (85).
17. The method of any of Claims 11-16, wherein switching between the low power state and the high power state includes changing a state of an analog-to- digital, ADC, converter.
18. The method of any of Claims 11-17, wherein switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR (85).
19. The method of any of Claims 11-18, wherein switching between the low power state and the high power state includes changing a duty cycle of the WUR (85).
20. The method of any of Claims 11-19, wherein the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ.
21. The method of any of Claims 11-20, wherein the power consumption condition is based at least in part on a battery status of the WD (22).
22. The method of any of Claims 11-21, wherein the power consumption condition is based at least in part on an interference experienced by the WD (22).
23. A wireless device, WD (22), having a wakeup receiver, WUR (85), and being configured to communicate with a network node (16), the WD (22) comprising processing circuitry configured to: switch the WUR (85) between a low power state and a high power state, the WUR (85) being configured to consume less power in the low power state than in the high power state, the switching being based at least in part on at least one of a power consumption condition and a receiver sensitivity of the WUR (85).
24. The WD (22) of Claim 23, wherein switching between the low power state and the high power state includes changing a state of a low noise amplifier of the WUR (85).
25. The WD (22) of any of Claims 23 and 24, wherein switching between the low power state and the high power state includes changing a state of a local oscillator of the WUR (85).
26. The WD (22) of any of Claims 23-25, wherein switching between the low power state and the high power state includes changing a state of a filter of the WUR (85).
27. The WD (22) of any of Claims 23-26, wherein switching between the low power state and the high power state includes changing a state of a phase-locked loop of the WUR (85).
28. The WD (22) of any of Claims 23-27, wherein switching between the low power state and the high power state includes changing a state of a bandwidth of the WUR (85).
29. The WD (22) of any of Claims 23-28, wherein switching between the low power state and the high power state includes changing a state of an analog-to- digital, ADC, converter.
30. The WD (22) of any of Claims 23-29, wherein switching between the low power state and the high power state includes changing a modulation and coding scheme, MCS, of the WUR (85).
31. The WD (22) of any of Claims 23-30, wherein switching between the low power state and the high power state includes changing a duty cycle of the WUR (85).
32. The WD (22) of any of Claims 23-31, wherein the power consumption condition is based at least in part on at least one of a reference signal received power, RSRP, and a reference signal received quality, RSRQ.
33. The WD (22) of any of Claims 23-32, wherein the power consumption condition is based at least in part on a battery status of the WD (22).
34. The WD (22) of any of Claims 23-33, wherein the power consumption condition is based at least in part on an interference experienced by the WD (22).
PCT/SE2022/050325 2022-03-31 2022-03-31 Wake-up radio with adaptive sensitivity and power consumption WO2023191675A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2022/050325 WO2023191675A1 (en) 2022-03-31 2022-03-31 Wake-up radio with adaptive sensitivity and power consumption

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2022/050325 WO2023191675A1 (en) 2022-03-31 2022-03-31 Wake-up radio with adaptive sensitivity and power consumption

Publications (1)

Publication Number Publication Date
WO2023191675A1 true WO2023191675A1 (en) 2023-10-05

Family

ID=81327326

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050325 WO2023191675A1 (en) 2022-03-31 2022-03-31 Wake-up radio with adaptive sensitivity and power consumption

Country Status (1)

Country Link
WO (1) WO2023191675A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160119865A1 (en) * 2014-10-28 2016-04-28 Alcatel-Lucent Usa Inc. Configurable communication modules for flexible communications within an energy-limited wireless system
US20180115952A1 (en) * 2016-10-21 2018-04-26 Qualcomm Incorporated Physical layer design for wakeup radio

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160119865A1 (en) * 2014-10-28 2016-04-28 Alcatel-Lucent Usa Inc. Configurable communication modules for flexible communications within an energy-limited wireless system
US20180115952A1 (en) * 2016-10-21 2018-04-26 Qualcomm Incorporated Physical layer design for wakeup radio

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
3GPP TR 38.875
3GPP TS 36.211
3GPP TS 36.213
3GPP TS 36.304
3GPP TS 36.331
VIVO: "Study on Low-power WUS", vol. TSG RAN, no. Electronic Meeting; 20211206 - 20211217, 29 November 2021 (2021-11-29), XP052097363, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/TSG_RAN/TSGR_94e/Docs/RP-213265.zip RP-213265 Study on Low-power WUS_r2.doc> [retrieved on 20211129] *
WANG PO-HAN PETER ET AL: "A Dual-Mode Wi-Fi/BLE Wake-Up Receiver", IEEE JOURNAL OF SOLID-STATE CIRCUITS, IEEE, USA, vol. 56, no. 4, 21 January 2021 (2021-01-21), pages 1288 - 1298, XP011846151, ISSN: 0018-9200, [retrieved on 20210325], DOI: 10.1109/JSSC.2021.3051142 *

Similar Documents

Publication Publication Date Title
US20210037470A1 (en) Wireless Device Grouping Indication Using Wakeup Signal
JP6490185B2 (en) Method and network node in a wireless communication network
US20230063026A1 (en) Aspects of wake-up signal (wus) transmission in idle mode
JP2018504068A (en) Network node and method in a wireless telecommunication network
EP3857986B1 (en) State transition processes for wireless device power savings
US11849395B2 (en) Adapting wake up signal repetitions
US11558765B2 (en) Control information based activation of measurement reporting configurations
US20230397129A1 (en) Wireless communication reference signal selection based on exposure limitations
US20220361243A1 (en) Flexible energy detection in unlicensed spectrum
EP4039045B1 (en) Adapting maximum allowed cca failures based on single occasion periodicity
US20220417970A1 (en) Methods for determining minimum scheduling offset application delay
WO2023191675A1 (en) Wake-up radio with adaptive sensitivity and power consumption
CN115552959A (en) Adapting a periodic configuration based on a spatial relationship
WO2023200390A1 (en) Mechanisms for efficient wake-up radio operation
WO2024063686A1 (en) Wakeup signal synchronization
US20230397116A1 (en) Configuration of wake up signal for new radio wireless device paging
US11258663B2 (en) Master carrier operation for multi-carrier unlicensed technologies
WO2023240502A1 (en) Wireless communication method, terminal device, and network device
WO2024063691A1 (en) Wake-up signal scheme for wake-up management
WO2023014278A1 (en) Network node, wireless device and methods for edrx operation
WO2023033700A1 (en) Synchronization signal block (ssb) provision adaptation for wireless devices
WO2023014269A1 (en) Synchronization signal block (ssb) transmissions and monitoring for reduced capability (redcap) wireless devices
WO2023158365A1 (en) Wireless device, node and methods performed thereby, for handling a transmission
WO2023096565A1 (en) First node, second node, and methods performed thereby, for handling a receiver at a wireless device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22715218

Country of ref document: EP

Kind code of ref document: A1