Patent Description:
The description herein may include concepts that could be pursued but are not necessarily ones that have been previously conceived or pursued. <NPL>, relates to PDCCH-based power saving channels in the RRC_CONNECTED mode for wake-up signaling (WUS) during an inactive state (e.g., C-DRX off periods) and for triggering UE adaptation signaling during the active state (e.g., DRX active time or non-DRX configuration). <NPL>, relates to progressing the design for PDCCH-based power savings signal/channel. WUS misdetection and link recovery aspects are also discussed.

Certain abbreviations that may be found in the description and/or in the Figures are herewith defined as follows:.

In radio technology systems at the time of this application, there are multiple access technologies that have been adopted in various telecommunication standards to provide a common protocol that enables control behavior of different wireless devices control such as user equipment (UE) for communications including uplink (UL) and/or downlink (DL) communications. This behavior can relate to frequency, timing, and power for the communications.

There continues to exist a need for further improvements in at least these telecommunication technologies. Such improvements needed include technologies and operations to make more efficient use of network resources while maintaining a lower power consumption.

Example embodiments of the invention work to improve at least operations in particular associated with failures in such radio technology communications.

As defined by claim <NUM>, the invention provides an apparatus, comprising: means for detecting, by a network device of a communication network, at least one listen-before-talk failure of network node channel access during or preceding a wake-up signal occasion by determining a lack of detection of one or more signals or channels of a synchronization signal block during a discovery reference signal window that is one of during or preceding the wake-up signal occasion; and means for performing on-duration monitoring based on the detecting. Preferred embodiments of the apparatus of claim <NUM> are defined by claims <NUM> to <NUM>.

As defined by claim <NUM>, the invention provides an apparatus, comprising: means for determining, by a network node of a communication network, information comprising a configuration for at least one network device of the communication network for performing on-duration monitoring if a listen-before-talk failure of network node channel access is detected by the at least one network device during or preceding a wake-up signal occasion by determining a lack of detection of one or more signals or channels of a synchronization signal block during a discovery reference signal window that is one of during or preceding the wake-up signal occasion; and means for sending an indication of the information towards the at least one network device. Preferred embodiments of the apparatus of claim <NUM> are defined by claims <NUM> to <NUM>.

The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, in which like reference signs are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and are not necessarily drawn to scale, in which:.

In example embodiments, there is proposed at least method and apparatus to at least perform on-duration monitoring based on detection of a failure of network node channel access during or preceding a wake-up signal occasion.

The modelling of PDCCH-WUS (Wake Up Signalling) on UE power saving in NR and its connection to DRX is under discussion at the 3GPP standards body at the time of this application. DRX has been introduced already to LTE and was inherited by NR as well.

A WUS is designed to allow the UE to skip PDCCH monitoring during DRX OnDurations when there is no data transmission to be done. This monitoring can be performed during a PDCCH occasion time duration (e.g., one or a consecutive number of symbols) during which a MAC entity associated with the UE is configured to monitor the PDCCH.

If the NW intends to schedule the UE, it needs to send a wake up indication to the UE during the WUS occasion(s) to wake up the UE first, the UE will then monitor normal PDCCH for scheduling data at the upcoming DRX OnDuration. DRX OnDuration may refer to starting a timer (e.g., drx-onDurationTimer) during which the UE is in DRX Active Time and monitors PDCCH. WUS may refer to signaling by the NW to the UE based on which the UE starts the timer for the next DRX OnDuration. Such signaling by the NW may be conducted by means of L1 signaling (e.g., by Downlink Control Information - DCI), by means of MAC signaling (e.g., by MAC Control Element), or by means of RRC signaling. Additionally, the WUS may be L1 signaling DCI with CRC scrambled by PS-RNTI based on which the UE decodes the DCI with such WUS control information. The control information may be in form of a bit indicting wake-up or not. The WUS may also be called as WUI (Wake Up Indication), PSI (Power Saving Indication), or DCP (DCI with CRC scrambled by PS-RNTI). Furthermore, the PS-RNTI may be defined as UE identification for indicating a UE to monitor PDCCH on the next occurrence of the connected mode DRX on-duration. The WUS may referred to as "DCI with CRC scrambled by PS-RNTI", where PS-RNTI is the RNTI used to identify the power saving signal for the configured UE.

It is noted that a DRX cycle can specify a periodic repetition of the DRX On Duration followed by a possible period of inactivity. An onDurationTimer can specify a number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle. There can be represented a union over the PDCCH-subframe(s) for serving cells.

It is noted that at the time of this application relevant operations based on the standards can include:.

The physical layer may perform a listen-before-talk procedure, according to which transmissions are not performed if a channel is identified as being occupied.

If absence of Wi-Fi cannot be guaranteed (e.g. by regulation) in the band (sub-<NUM>) where NR-U is operating, the baseline assumption is, the NR-U operating bandwidth is an integer multiple of <NUM>. For channel access mechanism, LTE-LAA LBT mechanism is adopted as baseline for <NUM> band and adopted as the starting point of the design for <NUM> band. At least for band where absence of Wi-Fi cannot be guaranteed (e.g. by regulation), LBT can be performed in units of <NUM>.

For <NUM> band, having a <NUM> gap to accommodate for the transceiver turnaround before the immediate transmission of the responding node is beneficial for NR-U, such as for supporting fast A/N feedback, and is permitted per regulation. Restrictions/conditions on when this option can be used will be further identified, e.g., in consideration of fair coexistence.

<FIG> shows a Table of Channel access schemes for initiating a COT by gNB as LBE device. As shown in <FIG> there is CAT2 LBT and CAT4 LBT scenario operations for scenarios <NUM>, <NUM>, and <NUM>. Scenario <NUM> of <FIG> is for DRS alone or multiplexed with non-unicast data e.g., other system information (OSI), Paging, and/or random access response (RAR). Whereas scenario <NUM> of <FIG> is for DRS multiplexed with unicast data, and Scenario <NUM> of <FIG> is for PDCCH and PDSCH. For Scenario <NUM> and <NUM> CAT2 LBT is not allowed.

Note that with regards to <FIG> in standards at the time of this application there is applicability of an LBT scheme other than Cat4 LBT for control messages related to initial/random access, mobility, paging, reference signals only, and PDCCH-only transmissions, e.g. "RACH message <NUM>", handover command, GC-PDCCH, or short message paging transmitted either alone or when multiplexed with DRS have been discussed.

The channel access schemes for NR-based access for unlicensed spectrum can be classified into the following categories:.

For different transmissions in a COT and different channels/signals to be transmitted, different categories of channel access schemes can be used. DRS window occur with SSB burst periodicity.

<FIG> shows a DRS window in NR-U. As shown in column <NUM> of <FIG> there is scenarios including a DRS-WindowLength-r16, and Discovery Burst - WindowLength-r16. Column <NUM> of <FIG> shows resulting additions in ServingCellConfigCommon and ServingCellConfigCommonSIB based on the scenario and also items for further study (FFS) at the time of this application. Column <NUM> of <FIG> shows for the scenario a further study (FFS) item at the time of this application with regards to resulting length configurations based on the scenario. Then column <NUM> of <FIG> shows Agreements including that a DRS transmission window duration can be configured as <NUM><NUM>, <NUM>, <NUM>, <NUM>, or <NUM>, if the DRS transmission window duration is not known, a UE may assume the DRS transmission window has a duration of <NUM>.

WUS monitoring window is an event which starts <NUM> before onDuration period and ends several slots/symbols before onDuration (due to processing time constrains). During that period, UE monitors set of search-space set occasions (one search-space set per CORESET) configured for WUS PS-RNTI.

In addition to this window an onDurationTimer can specify a number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle. While a PDCCH period (pp) can refer to an interval between the start of two consecutive PDCCH occasions and depends on a used PDCCH search space.

It is noted that problems with current standards at the time of this application include that for a network there is basic UE behaviour related to WUS. This basic behavior includes that in a PDCCH-WUS occasion that a UE is monitoring, if the UE is indicated to wake-up to monitor the PDCCH during the next occurrence of the drx-onDurationTimer. After this, the UE starts the drx-onDurationTimer at its next occasion. Otherwise, if no WUS is received, the UE does not start the timer and does not start the active time.

However, it is noted that enforcing the latter as above strictly results in the UE is not to wake up when it is not able to either monitor for or receive WUS during the WUS window, which can be an undesired outcome.

In example embodiments there is at least addressed NR-U scenarios when the UE does not know whether the network has not transmitted a WUS because of case (a) LBT failure or case (b) the lack of data.

In case of (a) LBT failure, during the WUS window Listen Before Talk (LBT) may fail (channel busy), thus the network will not be able to send a potential WUS signal even if data is pending at the network buffer for the UE.

In this regard a network node such as a RAN2 has not specified anything for WUS in connection with NR-U yet because NR-U is not in scope of the WID on UE Power Saving, within which 3GPP defined WUS. although WUS can be configured also for NR-U-capable UEs, no enhancements tailored to NR-U are in current standards at the time of this application. The problem of a larger UE power consumption in NR-U compared to NR will however be apparent when NR-U deployments materialize and the UE power saving topic in NR-U will have to be addressed as part of NR maintenance or at later standards body releases or work items.

In case of (b) the lack of data, for good coexistence, a gNB should not transmit periodic signals, unless they are extremely essential (such as SSB and system information) transmitted with CAT2 in DRS limited to <NUM>/<NUM>% of time/duty-cycle, i.e. <NUM> once <NUM>. For example a gNB may configure SSB burst as often as <NUM> and however needs to perform CAT4 LBT which is not desirable. Therefore, due to coexistence and to save power, a NR-U gNB would not transmit WUS unless the gNB wants to wake up a UE.

If an LBT failure happens during a DRS window (i.e., the gNB did not get channel access during a DRS window using CAT2), there is a high likelihood that the access could have failed also during the WUS window (using CAT4) that follows the DRS window.

In case of LBT failure in downlink, it would be beneficial if the consequent UE behaviour would depend on network decision. Specifically, in case of "delay tolerant" data, the network may wait for the next WUS opportunity to indicate the presence of data to achieve a larger UE power saving, whereas in case of "delay stringent" data the network may prefer to send the data during the next OnDuration despite the WUS was not transmitted because of LBT failure in order to avoid increasing latency (despite the UE would waste unnecessarily power in case of no data).

Therefore example embodiments address at least:.

Before describing the example embodiments in detail, reference is made to <FIG> for illustrating a simplified block diagram of various electronic devices that are suitable for use in practicing the example embodiments.

<FIG> shows a block diagram of one possible and non-limiting exemplary system in which the example embodiments may be practiced. In <FIG>, a user equipment (UE) <NUM> is in wireless communication with a wireless network <NUM>. A UE is a wireless, typically mobile device that can access a wireless network. The UE <NUM> includes one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected through one or more buses. Each of the one or more transceivers TRANS 10D includes a receiver and a transmitter. The one or more buses may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers TRANS 10D are connected to one or more antennas for communication <NUM> and <NUM> to gNB <NUM> and NN <NUM>, respectively. The one or more memories MEM 10B include computer program code PROG 10C. The UE <NUM> communicates with gNB <NUM> and/or NN <NUM> via a wireless link <NUM>.

The gNB <NUM> (NR/<NUM> Node B or possibly an evolved NB) is a base station such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as NN <NUM> and UE <NUM> of <FIG>. The gNB <NUM> provides access to wireless devices such as the UE <NUM> to the wireless network <NUM>. The gNB <NUM> includes one or more processors DP 12A, one or more memories MEM 12C, and one or more transceivers TRANS 12D interconnected through one or more buses. In accordance with the example embodiments these TRANS 12D can include X2 and/or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 12D includes a receiver and a transmitter. The one or more transceivers TRANS 12D are connected to one or more antennas for communication over at least link <NUM> with the UE <NUM>. The one or more memories MEM 12B and the computer program code PROG 12C are configured to cause, with the one or more processors DP 12A, the gNB <NUM> to perform one or more of the operations as described herein. The gNB <NUM> may communicate with another gNB or eNB, or a device such as the NN <NUM>. Further, the link <NUM> and or any other link may be wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further the link <NUM> may be through other network devices such as, but not limited to an NCE/MME/SGW device such as the NCE/MME/SGW <NUM> of <FIG>.

The NN <NUM> can comprise a mobility function device such as an AMF or SMF, further the NN <NUM> may comprise a NR/<NUM> Node B or possibly an evolved NB a base station such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as the gNB <NUM> and/or UE <NUM> and/or the wireless network <NUM>. The NN <NUM> includes one or more processors DP 13A, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS 12D interconnected through one or more buses. In accordance with the example embodiments these network interfaces of NN <NUM> can include X2 and/or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 13D includes a receiver and a transmitter connected to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For instance, the one or more memories MEM 13B and the computer program code PROG 13C are configured to cause, with the one or more processors DP 13A, the NN <NUM> to perform one or more of the operations as described herein. The NN <NUM> may communicate with another mobility function device and/or eNB such as the gNB <NUM> and the UE <NUM> or any other device using, e.g., link <NUM> or another link. These links maybe wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further, as stated above the link <NUM> may be through other network devices such as, but not limited to an NCE/MME/SGW device such as the NCE/MME/SGW <NUM> of <FIG>. The NCE/MME/SGW <NUM> including MME (Mobility Management Entity)/SGW (Serving Gateway) functionality, such as User Plane Functionalities, and/or an Access Management functionality for LTE and similar functionality for <NUM>.

The one or more buses of the device of <FIG> may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers TRANS 12D, TRANS 13D and/or TRANS 10D may be implemented as a remote radio head (RRH), with the other elements of the gNB <NUM> being physically in a different location from the RRH, and the one or more buses <NUM> could be implemented in part as fiber optic cable to connect the other elements of the gNB <NUM> to a RRH.

It is noted that although <FIG> shows a network node or base station such as the gNB <NUM> as in <FIG> and mobility management device such as the NN <NUM> as in <FIG>, these devices can incorporate or be incorporated into an eNodeB or eNB or gNB such as for LTE and NR, and would still be configurable to perform example embodiments as described in this application.

Also it is noted that description herein indicates that "cells" perform functions, but it should be clear that the gNB that forms the cell and/or a user equipment and/or mobility management function device that will perform the functions. In addition, the cell makes up part of a gNB, and there can be multiple cells per gNB.

The wireless network <NUM> may include a network control element (NCE/MME/SGW) <NUM> that may include NCE (Network Control Element), MME (Mobility Management Entity)/SGW (Serving Gateway) functionality, and which provides connectivity with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). The gNB <NUM> and the NN <NUM> are coupled via a link <NUM> and/or link <NUM> to the NCE/MME/SGW <NUM>. In addition, it is noted that the operations in accordance with example embodiments, as performed by the NN <NUM>, may also be performed at the NCE/MME/SGW <NUM>.

The NCE/MME/SGW <NUM> includes one or more processors DP 14A, one or more memories MEM 14B, and one or more network interfaces (N/W I/F(s)), interconnected through one or more buses coupled with the link <NUM> and/or <NUM>. In accordance with the example embodiments these network interfaces can include X2 and/or Xn interfaces for use to perform the example embodiments. The one or more memories MEM 14B include computer program code PROG 14C. The one or more memories MEM14B and the computer program code PROG 14C are configured to, with the one or more processors DP 14A, cause the NCE/MME/SGW <NUM> to perform one or more operations which may be needed to support the operations in accordance with the example embodiments.

The wireless Network <NUM> may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors DP10A, DP12A, DP13A, and/or DP14A and memories MEM 10B, MEM 12B, MEM 13B, and/or MEM 14B, and also such virtualized entities create technical effects.

The computer readable memories MEM 10B, MEM 12B, MEM 13B, and MEM 14B may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories MEM 10B, MEM 12B, MEM 13B, and MEM 14B may be means for performing storage functions. The processors DP10A, DP12A, DP13A, and DP14A may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors DP10A, DP12A, DP13A, and DP14A may be means for performing functions, such as controlling the UE <NUM>, gNB <NUM>, NN <NUM>, NCE/MME/SGW <NUM> and other functions as described herein.

Example embodiments provide at least a method and an apparatus with means to control / adapt the start of an OnDurationtimer if UE detects an LBT failure in downlink during WUS occasions preceding the OnDuration (thus leading to the UE not monitoring for receiving the WUS and/or not monitoring or detecting one or more signals or channels to be transmitted during a discovery reference signal window, such as based on PSS/SSS or PBCH associated with an SSB to be transmitted in DRS by gNB). In accordance with an example embodiment a lack of detection in a DRS window can cause the UE or another network device to determine an LBT failure. For example in accordance with example embodiments an LBT failure of network node channel access can be detected based on a lack of detection of one or more signals or channels to be transmitted during a discovery reference signal window. The claimed invention relates to this embodiment.

In accordance with example embodiments control and adaptation for these operations can be based on the 5QI, <NUM> QoS Indicator. The 5QI, <NUM> QoS Indicator such as for service latency, such as on the DRX cycle/WUS frequency, and (potentially) accounting also for the number of consecutive LBT failures, according to a network configuration.

In accordance with example embodiments a determined relationship between DRX cycle / WUS frequency and QoS/5QI (service latency) can also include that it can be determined based on tightness or level of a latency target requirement a length of the DRX cycle. For example the higher the tightness or level of a latency target requirement then the shorter the DRS cycle. This determining in accordance with example embodiments can help a network device establish indirectly a dependency between the network indication and a network device QoS profile, for use in operations as disclosed herein.

Operations in accordance with example embodiments will result for instance in the UE performing DRX-OnDuration monitoring without a preceding WUS indication if one or more LBT failures have been detected during the DRS window preceding the DRX-ONDuration and/or if one or more of the configured DRBs have delay-stringent requirement (e.g. based on QoS/5QI).

Example embodiments as disclosed herein include that the DRX-OnDurationtimer is not to be started if the UE detects an LBT failure during one or more DRS window(s) preceding the ONDuration. In accordance with example embodiments the DRS window(s) can be during or preceding a WUS window.

In accordance with example embodiments at least the detecting the LBT failure during these windows can be further depending on the QoS/5QI, and/or depending on the DRS, DRX cycle and/or WUS frequency.

In accordance with example embodiments, there can be determining whether to start an ONDurationtimer, after detecting one or more subsequent LBT failure(s) in DL overlapping at least partially with WUS occasions/window related to control the subsequent ONDuration, is configured by the network e.g. as part of the WUS configuration.

In accordance with example embodiments, the NR-U UE can monitor for Listen-Before-Talk (LBT) failure in DL for the purpose of power saving based at least on a DRS window.

In accordance with example embodiments, the NR-U UE can monitor for subsequent Listen-Before-Talk (LBT) failure(s) in DL for the purpose of power saving.

In accordance with example embodiments, the NR-U UE can monitor for Listen-Before-Talk (LBT) failure(s) in DL for the purpose of power saving only if it is configured to skip starting the DRX-OnDurationtimer.

Further, in accordance with example embodiments, the NR-U UE can be configured to skip starting the DRX-OnDurationtimer when detecting LBT failures, it will start the DRX-OnDurationtimer after N+<NUM> subsequent LBT failures observed during DRS windows that occur closest to the WUS occasions/window. This is to maximize the correlation between probability that DRS had LBT failure (as can be measured by UE) and WUS window had LBT failure, as in accordance with example embodiments.

It should be noted that the above actions may in this way be able to "overwrite" the default UE behaviour, which may be configured through the ps-WakeupOrNot, such that if a UE is configured to continue sleeping in case of not detecting the WUS correctly, the UE may through these triggers still be required to monitor for the PDCCH in the next OnDuration.

It is noted that as described herein example embodiments can be applicable to improve operations using a WUS design where the PDCCH-WUS and/or DCI with CRC is scrambled by PS-RNTI. However, it is further noted that example embodiments can be applied to advantage any WUS design standards acceptances at the time of this application and/or future standards acceptances. The example embodiments can be applicable to improve operations of WUS designs at least such as WUS designs of NB-IoT and/or WUS designs where a WUS is transmitted with a different DCI format than for example but not limited to a format 2_6, or on a different channel than PDCCH, and/or using physical signals/sequences such as DMRS.

Advantages of operations in accordance with example embodiments as disclosed herein include at least that UE behavior in case the WUS overlaps with certain activities including LBT failure in NR-U is defined and gives more flexibility to the network to determine the best tradeoff between UE power saving and latency targets.

<FIG> illustrates operations in accordance with example embodiments which may be performed by a network device such as, but not limited to, a network device such as a UE <NUM> as in <FIG>. As shown in step <NUM> of <FIG> there is detecting, by a network device of a communication network, at least one failure of network node channel access during or preceding a wake-up signal occasion. Then as shown in step <NUM> of <FIG> there is based on the detecting, performing on-duration monitoring.

In accordance with the example embodiments as described in the paragraph above, wherein the network device is in a sleep mode, and wherein the on-duration monitoring is performed without receiving a preceding wake-up signal indicating wake-up during a wake-up signal occasion associated with the sleep mode.

In accordance with the example embodiments as described in the paragraphs above, wherein the failure of network node channel access is detected based on a lack of detection of one or more signals or channels to be transmitted during a discovery reference signal window for the network device.

In accordance with the example embodiments as described in the paragraphs above, wherein the failure is during a discovery reference signal window that is one of during or preceding the wake-up signal occasion.

In accordance with the example embodiments as described in the paragraphs above, wherein the failure of network node channel access comprises at least one listen before talk failure of a device of the communication network.

In accordance with the example embodiments as described in the paragraphs above, wherein at least one of detecting or performing on-duration monitoring is based on an indication from the communication network.

In accordance with the example embodiments as described in the paragraphs above, wherein the indication is based on at least one of a discontinuous reception cycle or a wake-up signal frequency associated with the network device, and wherein the indication accounts for a number of consecutive ones of the failure of the network node channel access.

In accordance with the example embodiments as described in the paragraphs above, wherein the on-duration monitoring comprises discontinuous reception on-duration monitoring.

In accordance with the example embodiments as described in the paragraphs above, wherein the performing on-duration monitoring comprises: based on an indication from the communication network, determining to start a discontinuous reception On-duration timer for the on-duration monitoring.

In accordance with the example embodiments as described in the paragraphs above, wherein starting the discontinuous reception On-duration timer is performed after N+<NUM> subsequent listen before talk failures observed during at least one discovery reference signal window that occur closest the wake-up signal occasion.

In accordance with the example embodiments as described in the paragraphs above, wherein at least one of the N+<NUM> subsequent listen before talk failures observed during the at least one discovery reference signal window is occurring not later than the wake-up signal occasion.

In accordance with the example embodiments as described in the paragraphs above, wherein determining to start a discontinuous reception for the On-duration monitoring is based on a wake-up signal configuration from the communication network.

In accordance with the example embodiments as described in the paragraphs above, wherein the on-duration monitoring is performed based on determining that the at least one data radio bearer affected by the failure comprises a delay-stringent requirement.

In accordance with the example embodiments as described in the paragraphs above, wherein the delay-stringent requirement comprises at least one of a communication network technology requirement or a quality of service requirement.

In accordance with the example embodiments as described in the paragraphs above, there is determining, based on a required maximum latency level of the delay-stringent requirement of the at least one data radio bearer affected by the failure, a length of the at least one of a discontinuous reception cycle.

In accordance with the example embodiments as described in the paragraphs above, wherein the determined length of the at least one of a discontinuous reception cycle is used to establish a dependency between the indication from the communication network and a quality of service requirement of the network device.

A non-transitory computer-readable medium (MEM 10B as in <FIG>) storing program code (PROG 10C as in <FIG>), the program code executed by at least one processor (DP 10A as in <FIG>) to perform the operations as at least described in the paragraphs above.

In accordance with an example embodiment as described above there is an apparatus comprising: means for detecting (TRANS 10D, MEM 10B, PROG 10C, and DP 10A as in <FIG>), by a network device (UE <NUM> as in <FIG>) of a communication network (Network <NUM> as in <FIG>), at least one failure of network node channel access during or preceding a wake-up signal occasion; and means based on the detecting, for performing (TRANS 10D, MEM 10B, PROG 10C, and DP 10A as in <FIG>) on-duration monitoring.

In the example aspect according to the paragraph above, wherein at least the means for detecting and performing comprises a non-transitory computer readable medium [MEM 10B] encoded with a computer program [PROG 10C] executable by at least one processor [DP 10A].

<FIG> illustrates operations in accordance with example embodiments which may be performed by a network device such as, but not limited to, a network device such as a gNB <NUM> or NN <NUM> as in <FIG>. As shown in step <NUM> of <FIG> there is determining, by a network node of a communication network, information comprising a configuration for performing on-duration monitoring if a failure of network node channel access is detected during or preceding a wake-up signal occasion. Then as shown in step <NUM> of <FIG> there is sending an indication of the information towards the at least one network device.

In accordance with the example embodiments as described in the paragraphs above, wherein the configuration is for use while the at least one network device is in a sleep mode, and wherein the configuration is for the on-duration monitoring to be performed without a preceding wake-up signal indicating wake-up during a wake-up signal occasion associated with the sleep mode.

In accordance with the example embodiments as described in the paragraphs above wherein the configuration is for use for detecting the failure of network node channel access based on a lack of detection of one or more signals or channels to be transmitted during a discovery reference signal window.

In accordance with the example embodiments as described in the paragraphs above wherein, the configuration is for use for detecting the failure of network node channel access during a discovery reference signal window that is one of during or preceding the wake-up signal occasion.

In accordance with the example embodiments as described in the paragraphs above wherein the configuration is based on at least one of a discontinuous reception cycle or a wake-up signal frequency associated with the at least one network device, and wherein the indication accounts for a number of consecutive ones of the failure of the network node channel access.

In accordance with the example embodiments as described in the paragraphs above wherein the configuration is for use in determining to start a discontinuous reception On-duration timer for the on-duration monitoring after N+<NUM> subsequent listen before talk failures observed during at least one discovery reference signal window that occur closest to the wake-up signal occasion.

In accordance with the example embodiments as described in the paragraphs above wherein the information comprises a configuration to start a discontinuous reception On-duration timer for the on-duration monitoring based on a wake-up signal configuration from the communication network.

In accordance with the example embodiments as described in the paragraphs above wherein the information comprises on-duration monitoring configuration based on at least one data radio bearer affected by the failure comprises a delay-stringent requirement.

In accordance with the example embodiments as described in the paragraphs above wherein the delay-stringent requirement comprises at least one of a communication network technology requirement or a quality of service requirement.

In accordance with the example embodiments as described in the paragraphs above wherein the information comprises a configuration to determine, based on a required maximum latency level of the delay-stringent requirement of the at least one data radio bearer affected by the failure, a length of the at least one of a discontinuous reception cycle.

In accordance with the example embodiments as described in the paragraphs above wherein the determined length of the at least one of a discontinuous reception cycle is used to establish a dependency between the indication from the communication network and a quality of service requirement of the at least one network device.

A non-transitory computer-readable medium (MEM 12B and/or MEM 13B as in <FIG>) storing program code (PROG 12C and/or PROG 13C as in <FIG>), the program code executed by at least one processor (DP 12A and/or DP 13A as in <FIG>) to perform the operations as at least described in the paragraphs above.

In accordance with an example embodiment as described above there is an apparatus comprising: means for determining (TRANS 12D and/or TRANS 13D, MEM 12B and/or MEM 13B, PROG 12C and/or PROG 13C, and DP 12A and/or DP 13A as in <FIG>), by a network node (gNB <NUM> and/or NN <NUM> as in <FIG>) of a communication Network <NUM> as in <FIG>), information comprising a configuration (MEM 12B and/or MEM 13B, PROG 12C and/or PROG 13C, and DP 12A and/or DP 13A as in <FIG>) for use by at least one network device (UE <NUM> as in <FIG>) of the communication network to perform on-duration monitoring if a failure of network node channel access is detected during or preceding a wake-up signal occasion; and means for sending (TRANS 12D and/or TRANS 13D, MEM 12B and/or MEM 13B, PROG 12C and/or PROG 13C, and DP 12A and/or DP 13A as in <FIG>) an indication of the information towards the at least one network device.

In the example aspect according to the paragraph above, wherein at least the means for determining and sending comprises a non-transitory computer readable medium [MEM 12B and/or MEM 13B as in <FIG>] encoded with a computer program [PROG 12C and/or PROG 13C as in <FIG>] executable by at least one processor [DP 12A and/or DP 13A and in <FIG>].

In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

Embodiments may be practiced in various components such as integrated circuit modules.

Claim 1:
An apparatus, comprising:
means (10A-D) for detecting, by a network device (<NUM>) of a communication network (<NUM>), at least one listen-before-talk failure of network node channel access during or preceding a wake-up signal occasion by determining a lack of detection of one or more signals or channels of a synchronization signal block during a discovery reference signal window that is one of during or preceding the wake-up signal occasion; and
means (10A-D) for performing on-duration monitoring based on the detecting.