Methods, apparatuses, and computer program products for UE-triggered downlink alert information

Abstract

Methods, apparatuses, and computer program products that provide for UE-triggered downlink alert information. In the context of a method, the method includes determining, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node; providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions; and monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

Description

METHODS, APPARATUSES, AND COMPUTER PROGRAM PRODUCTS FORUE-TRIGGERED DOWNLINK ALERT INFORMATIONRELATED APPLICATION

[0001] This application claims priority to FI Application No. 20245501 filed April 19, 2024, which is incorporated herein by reference in its entirety.TECHNOLOGICAL FIELD

[0002] An example embodiment relates generally to techniques for UE-triggered (user equipment-triggered) downlink alert information and, more particularly, to a framework for requesting downlink alert information from a network node.BACKGROUND

[0003] Some wireless communications systems may include low-power wide-area (LPWA) internet-of-things (loT) devices. For instance, a wireless communication system may use LPWA loT devices to provide connectivity in both rural and remote areas (e.g., coverage in areas in which cellular connectivity may not be readily available). In some cases, LPWA technologies have an energy design, which enables devices to operate on a battery for multiple years (e.g., 10 years), thereby improving a sustainability of communication technologies within both rural and remote areas. Moreover, some LPWA technologies may facilitate relatively large loT deployments, which may accommodate a relatively large quantity of devices and improve a scalability of loT. In some cases, LPWA technologies may aid in integrating sensing and communication, which are used for applications that utilize sensing and low-rate data transmission. LPWA technologies may be cost-effective, for example, in terms of both device hardware and operational costs. As such, LPWA technologies may improve an affordability of wireless communications for a broader range of applications.BRIEF SUMMARY

[0004] Methods, apparatuses, and computer program products are disclosed to provide for UE-triggered downlink alert information. In this regard, at least a method, apparatus, and computer program product provide a framework for a UE to request downlink alert information from a network node. By providing for the framework for the UE to request the downlink alert information from the network node, the method, apparatus, and computerprogram product may provide for reduced power consumption at the UE. In some aspects, by reducing the power consumption at the UE, the method, apparatus, and computer program product may increase a quantity of time the UE operates on a battery.

[0005] In an example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to determine, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to provide, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to monitor, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

[0006] In an example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to provide, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

[0007] In an example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to determine, at a user equipment (UE), one or more monitoringoccasions for reception of downlink alert information from a node. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to provide, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to monitor, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered prior to the first time occasion.

[0008] In an example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to receive, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus to provide, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node prior to the first time occasion.

[0009] In an example embodiment, a method is provided that comprises determining, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The method also comprising providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The method also comprises monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

[0010] In an example embodiment, a method is provided that comprises receiving, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alertinformation to a user equipment (UE). The method also comprises providing, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

[0011] In an example embodiment, a method is provided that comprises determining, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The method also comprises providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The method also comprises monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered prior to the first time occasion.

[0012] In an example embodiment, a method is provided that comprises receiving, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The method also comprises providing, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node prior to the first time occasion.

[0013] In an example embodiment, a non-transitory computer readable storage medium comprising computer instructions that, when executed by an apparatus, cause the apparatus to determine, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The computer executable program code instructions also comprise program code instructions configured, upon execution, to provide, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The computer executable program code instructions also comprise program code instructions configured, upon execution, to monitor, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the oneor more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

[0014] In an example embodiment, a non-transitory computer readable storage medium comprising computer instructions that, when executed by an apparatus, cause the apparatus to receive, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The computer executable program code instructions also comprise program code instructions configured, upon execution, to provide, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

[0015] In an example embodiment, a non-transitory computer readable storage medium comprising computer instructions that, when executed by an apparatus, cause the apparatus to determine, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The computer executable program code instructions also comprise program code instructions configured, upon execution, to provide, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The computer executable program code instructions also comprise program code instructions configured, upon execution, to monitor, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered prior to the first time occasion.

[0016] In an example embodiment, a non-transitory computer readable storage medium comprising computer instructions that, when executed by an apparatus, cause the apparatus to receive, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The computer executable program code instructions also comprise program code instructions configured, upon execution, to provide, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoringoccasions, and wherein the downlink alert information is associated with downlink data buffered at a node prior to the first time occasion.

[0017] In an example embodiment, an apparatus is provided that comprises means for determining, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The apparatus also comprises means for providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The apparatus also comprises means for monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

[0018] In an example embodiment, an apparatus is provided that comprises means for receiving, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE). The apparatus also comprises means for providing, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

[0019] In an example embodiment, an apparatus is provided that comprises means for determining, at a user equipment (UE), one or more monitoring occasions for reception of downlink alert information from a node. The apparatus also comprises means for providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions. The apparatus also comprises means for monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered prior to the first time occasion.

[0020] In an example embodiment, an apparatus is provided that comprises means for receiving, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlinkalert information to a user equipment (UE). The apparatus also comprises means for providing, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node prior to the first time occasion.BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Having thus described some example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0022] Figure 1 is a block diagram of an example communication system in which the apparatus of Figure 2 may be deployed;

[0023] Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present disclosure;

[0024] Figure 3 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to provide for UE-triggered downlink alert information in accordance with an example embodiment;

[0025] Figure 4 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to provide for UE-triggered downlink alert information in accordance with an example embodiment;

[0026] Figure 5 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for UE-triggered downlink alert information in accordance with an example embodiment;

[0027] Figure 6 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for UE-triggered downlink alert information in accordance with an example embodiment;

[0028] Figure 7 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for UE-triggered downlink alert information in accordance with an example embodiment; and

[0029] Figure 8 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for UE-triggered downlink alert information in accordance with an example embodiment.DETAILED DESCRIPTION

[0030] Some embodiments of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the disclosure are shown. Indeed, various embodiments of the disclosure may be embodied in many different forms and should not be construed as limited to the example embodiments set forth herein; rather, these example embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and / or stored in accordance with some embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of example embodiments of the present disclosure.

[0031] Additionally, as used herein, the term ‘circuitry’ refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and / or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and / or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that use software or firmware for operation even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term ‘circuitry’ also includes an implementation comprising one or more processors and / or portion(s) thereof and accompanying software and / or firmware. As another example, the term ‘circuitry’ as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device (such as a core network apparatus), field programmable gate array, and / or other computing device.

[0032] As illustrated in the example of Figure 1 , a communications system may include one or more UEs, such as a UE 10. In some embodiments, the UE 10 may be an example of an loT device, such as a LPWA loT device. For example, the wireless communications systems may include one or more LPWA loT devices, such as the UE 10, to widen a deployment of loT devices (e.g., to enable widespread loT deployment). As described herein, a LPWA loT device refers to a device that consumes a relatively low quantity of power whileproviding a relatively wide coverage area. In other words, an LPWA loT device includes a device having low power consumption and wide coverage areas. In some examples, a LPWA loT device (e.g., the UE 10) may transmit a relatively small quantity of data over a relatively long distance or in challenging radio conditions. Accordingly, the wireless communication system may use LPWA loT devices to provide connectivity in both rural and remote areas (e.g., coverage in areas in which cellular connectivity may not be readily available). In some examples, LPWA technologies have an energy design (e.g., an energy-efficient design), enabling devices to operate on a single battery for multiple years (e.g., 10 years), thereby improving a sustainability of communication technologies. Moreover, some LPWA technologies may facilitate relatively large loT deployments, which may accommodate a relatively large quantity of devices and improve a scalability of loT technologies. In some examples, LPWA technologies may aid in integrating sensing and communication and, as such, may be used for applications ranging from environmental monitoring to smartagriculture (e.g., applications that utilize sensing and low-rate data transmission). In some examples, LPWA technologies may be associated with relatively low costs (e.g., may be cost-effective), for example, in terms of both device hardware and operational costs. As such, LPWA technologies may improve an affordability of wireless communications (e.g., cellular communications) for a broader range of applications. In some examples, LPWA technologies may generate a relatively large quantity of data from sensors. Such data may be input into artificial intelligence (Al) algorithms, for example, for analysis and intelligent decisionmaking.

[0033] For example, an LPWA loT device (e.g., an LPWA loT UE, such as the UE 10), may be an example of an loT device, which has rigid power constraints (e.g., constrained energy storage or the energy availability). Additionally, some such devices may be deployed in areas in which the devices may communicate over relatively wide areas (e.g., compared to dense deployment scenarios). As an illustrative example, a LPWA loT device may be deployed in a farm field (e.g., a large farm field) or a factory (e.g., a large factory), in which an access point or a controlling node (e.g., the network node 12) is relatively far from the LPWA loT device. Communications over relatively wide areas may consume more power than, for example, communications over relatively narrow areas. In some cases, to increase a lifetime for an LPWA loT device (e.g., to increase an amount of time the LPWA loT device may operate on a battery), the LPWA loT devices may implement one or more techniques for reducing power consumption. For example, the LPWA loT device may implement one ormore techniques that enable the LPWA loT device to periodically operate in a power saving mode (e.g., go to sleep while not monitoring or receiving any signals in an inactive or idle state).

[0034] For example, the UE 10 may be configured for discontinuous reception (DRX) in which the UE 10 operates in an active state during periodic paging occasions (POs) to monitor for signaling from the network node 12. In such an example, during off durations, the UE 10 may operate in a power saving state (e.g., an inactive state) in order to reduce power consumption. Such inactive states may include, for example, a radio resource control (RRC) idle state (denoted RRC_IDLE) or an RRC inactive state (denoted RRC_INACTIVE). In some examples of DRX, the UE 10 may monitor one PO per DRX cycle. As described herein, a PO is a set of PDCCH monitoring occasions (MOs), which may include one or multiple time slots (e.g., subframe or OFDM symbols) in which a paging signal (e.g., paging DCI) may be sent to the UE 10 (e.g., directly from the network node 12 or indirectly via another node, such as another UE). A Paging Frame (PF) may be an example of one radio frame and may include one or multiple POs, or a starting point of a PO. To further reduce power consumption, the UE 10 may have an extended DRX (eDRX), for example, for one or more connection management (CM) modes, such as a CM idle mode (denoted CM-IDLE) and / or a CM connected mode (denoted CM-CONNECTED) with RRC-INACTIVE.

[0035] In other words, a DRX cycle may include one or more on durations and one or more off durations. During an off duration the device may operate in an inactive state, and during an on duration the device may operate in an active state such that the device may monitor for paging signals from the network (e.g., circuitry of the device is configured to receive signaling from the network). A paging signal may indicate that the network has downlink data for the device. Accordingly, in response to receiving a paging signal, the device may determine to operate in the active state (e.g., to continue to operate in the active state, to refrain from transitioning to an inactive state). Additionally, for examples in which the network lacks data for the device, the device may determine to operate in the inactive state (e.g., may go to sleep). In some examples, the device may operate in the inactive state for a duration of an inactivity timer. That is, the device may determine when to transition to an active state (e.g., to monitor for paging signals) based on an inactivity timer. In some examples, however, the network node 12 may lack downlink data for the UE 10 for multiple DRX cycles. In such examples, monitoring by the UE 10 during the on durations of the DRX cycles may be unnecessary (e.g., may lead to the UE 10 operating in the active state andconsuming power unnecessarily). Thus, for such examples, it may be inefficient (e.g., in terms of power saving) for the UE 10 to monitor the POs.

[0036] For instance, a LPWA loT device may include a soil moisture sensor deployed in a remote agricultural field. The LPWA loT device may perform soil measurements in accordance with a periodicity, such as one or more soil moisture measurements per day. However, an unexpected dry spell may occur, and necessitate that an irrigation system for the agricultural field provide more water to prevent crop stress. In such an example, a downlink command may be sent from a server (e.g., the network node 12) to the soil moisture sensor (e.g., the UE 10) to adjust the periodicity (e.g., to decrease an interval between measurements). Accordingly, signaling of downlink data to the sensor may occur infrequently (e.g., may be an example of an infrequent downlink update) relative to the on durations of the DRX cycle. That is, a frequency at which the network node 12 signals downlink data to the UE 10 may be lower than a frequency at which the UE 10 monitors POs, which may lead to increased power consumption at the UE 10.

[0037] Additionally, or alternatively, the LPWA loT device may be configured for reception of a WUS (wake-up signal), which may provide power saving at the LPWA loT device, for example, by enabling the LPWA loT device to operate in a power saving state (e.g., to continue to sleep, to not wake up) for one or more DRX on duration periods in which no downlink data is available for the LPWA (e.g., when the gNB signals to the LPWA loT device 'No Wake Up'). In such an example, the network node (e.g., a gNB) may notify the LPWA loT device when downlink data is available (e.g., may signal to the UE 'Wake Up'), such that the LPWA loT device may wake up (e.g., transition to an active state), monitor the paging channel, and / or receive downlink data during a future DRX on duration period. In some examples, a WUS may be cell- or group-specific. In such examples, the WUS may wake up one or more UEs that do not have incoming data. Such UEs may wake up to monitor the paging channel and transition back to the sleep state after the monitoring. The WUS may indicate that the gNB (e.g., the network node 12) intends to send the LPWA loT device (e.g., the UE 10) data in a future (e.g., next) DRX on duration. In such examples, the LPWA loT device monitors for the WUS according to a wake-up cycle (e.g., to receive the alert message from the gNB). For example, the device may include a receiver which consumes relatively low power and monitors for WUSs from the network during on durations of the wake-up cycle and, based on a received WUS, determines whether to wake up during an on duration of a DRX cycle. Thus, in such an example, the LPWA loT monitors for a WUS (e.g., indicating‘Wake Up’ or ‘No Wake Up’) irrespective of whether data is available for the LPWA loT device. In some examples, a frequency at which the network node 12 signals downlink data to the UE 10 may be lower than a frequency at which the UE 10 monitors for the WUS, which may lead to increased power consumption at the UE 10. That is, if the network node 12 lacks downlink data for the UE 10 (e.g., over multiple on durations), the UE 10 may monitor for the WUS unnecessarily and, as such, may operate in the active state (and consume power) unnecessarily.

[0038] In other words, the WUS may reduce energy consumption at the UE 10 relative to DRX paging indications by triggering the UE 12 to wake-up when downlink data (paging) is available for a device in a group of devices (e.g., a group of devices to which the WUS is sent). However, periodic monitoring of the WUS consumes power (e.g., may itself be power expensive for LPWA loT devices) and, for scenarios in which downlink data reception is sporadic (e.g., with relatively long inter-packet intervals), power savings achieved through WUS may be relatively low (e.g., may be insufficient for LPWA loT devices, may not provide for a sufficiently long lifetime).

[0039] In some examples, the LPWA loT device may support operations in accordance with a mobile initiated connection only (MICO) mode. For example, some wireless networks (e.g., in 5G) may support a MICO mode, which may aid the LPWA loT device in power saving. In accordance with the MICO mode, a device may refrain from listening to paging (and thus may not be paged) to conserve battery power. For example, an access and mobility management function (AMF) may indicate, to the device, to operate in the MICO mode and may consider the device unreachable while the device is in an idle state (e.g., while the device CM state in the AMF is CM-IDLE). Consequently, the AMF may reject one or more requests (e.g., from the application function) for downlink data delivery for a device in MICO mode (and whose CM state in the AMF is CM-IDLE, with an appropriate cause). In other words, a device in MICO mode may be reachable (e.g., only reachable) for mobile terminated data or signaling when the device is in CM-CONNECTED. Accordingly, a device in MICO mode may refrain from listening to paging while in CM-IDLE and may stop one or more (e.g., any) access stratum procedures in CM-IDLE, for example, until the device initiates a transition from CM-IDLE to CM-CONNECTED due to a trigger. The trigger may include a change in the device (e.g., a change in configuration of the device) that necessitates an update of the device registration with the network, a periodic registration timer expires, pending data, or pending signaling (e.g., a session management procedure is initiated). However,while mobile originated data applies for both CM-CONNECTED and CM-IDLE state, mobile terminated data is supported (e.g., is only supported) when the device is in a CM- CONNECTED state. That is, the MICO mode may not support a mechanism for the UE 10 to reduce power consumption related to the reception of downlink data (e.g., mobile terminated data). In other words, the MICO mode may not enable the UE 12 to receive a paging signal while conserving power.

[0040] In other words, LPWA loT UEs have relatively low energy availability and may be intended (e.g., expected) to operate for years. For example, an expected battery lifetime of a LPWA loT UE may be 10-15 years. Additionally, such UEs may receive or transmit data sporadically (e.g., with large inter-packet intervals). Moreover, unlike some cases of communication, such as voice calls, LPWA loT use cases may be delay tolerant (e.g., may be delayed for seconds to hours). Therefore, due to LPWA loT UEs being constrained by the low energy availability, such UEs may implement techniques to reduce (e.g., minimize) energy consumption at the UEs. However, some such techniques may necessitate that the UEs frequently monitor (or listen) for signaling from the network (e.g., wake-up indications, paging information), which consumes power and increases energy costs for the UEs (e.g., energy constrained UEs).

[0041] In some examples, one or more techniques for UE-triggered downlink alert information, as described herein, may enable the UE 10 to conserve energy (e.g., save power) by providing the UE 10 with a framework (e.g., an autonomy) to select one or more downlink MOs in which the UE 10 is available (e.g., and desires) to monitor and receive downlink alert information (e.g., wake-up indication, paging information) from the network (e.g., directly from the network node 12 or indirectly via another node, such as another UE). For example, in accordance with the one or more techniques for UE-triggered downlink alert information, as described herein, the UE 10 may send a request for downlink alert information to the network node 12. In the request, the UE10 may indicate the one or more MOs during which the UE 10 it is available to receive the downlink alert information. In other words, the UE 10 indicates, to the network node 12, one or more occasions during which the UE 10 is reachable (e.g., when the UE 10 is reachable during its RRC IDLE / INACTIVE state).

[0042] One or more aspects of the present disclosure provide a framework for configuring the UE 10 to determine (e.g., autonomously determine) one or more MOs in which the UE 10 is available to receive downlink alert information from the network node 12. In some examples, the one or more MOs may be selected at the UE 10 from a network-configured set of candidate MOs. As described herein, an MO refers to one or more time- and / or frequency-domain resources the UE 10 may monitor for downlink alert information from the network. For example, an MO includes one or more time-domain resources and one or more frequency domain resources via which the UE may monitor for downlink alert information from the network. In some examples, an MO may be a WUS occasion (e.g., a group WUS MO). Additionally, or alternatively, an MO may be PO. As described herein, downlink alert information refers to information associated with downlink data for a UE. For example, the downlink alert information may include a downlink alert message that indicates whether downlink data is available for the UE 10. In some other examples, the downlink alert information may include scheduling information, such as an indication of one or more resources for reception of the downlink alert message and / or system information (e.g., information usable at the UE 10 for establishing a connection with the network such that the UE 10 may receive downlink data). In some examples, the downlink alert information may be a wake-up indication. Additionally, or alternatively, in some examples, the downlink alert information may be a paging indication. In some examples, the determination of the one or more MOs may be based on downlink characteristics (e.g., downlink data or downlink alert information characteristics) indicated to the UE 10 by the network. Additionally, or alternatively, the one or more MOs may be autonomously determined at the UE 10 based on (at least) an energy availability at the UE (e.g., an expected energy availability at the UE) or a time criticality of an operation at the UE, such as an loT operation or a non-IoT operation of the UE 10. As described herein, an energy availability (e.g., an availability of energy) at the UE refers to a quantity of energy at the UE, which is available for consumption by the UE, for example, to perform one or more operations. As described herein a time criticality of an operation refers to a priority associated with performance of the operation during a period of time. In other words, the time criticality indicates a time sensitivity (e.g., time criticality) associated with performance of the operation.

[0043] In accordance with one or more aspects of the present disclosure, the UE 10 may send a downlink alert information request to the network node 12. The downlink alert information request may include MO information. That is, the downlink alert information request may be indicative of one or more MOs for reception of downlink alert information from the network node 12. In some examples, the downlink alert information request may include the MO explicitly. For example, the downlink alert information request may include time-frequency resource information of the MO and / or a periodicity of MOs. For example,the request may include an indication of a time offset and / or a frequency offset relative to one or more time-frequency resources used for transmission of the downlink alert information request. In some other examples, the request may indicate a subset of network-configured candidate MOs (e.g., a selected subset of indexes of MOs spanning a time period). In yet some other examples, the MO may be indicated implicitly. For example, the network node 12 may configure the UE 10 with a fixed (e.g., in a specification) time / frequency offset for the MO, which may be relative to one or more time-frequency resources used for transmission of the downlink alert information request message. In such an example, by sending the downlink alert information request message in a time-frequency resource, the UE 10 may indicate the MO (e.g., implicitly). That is, the network node 12 may determine the MO by applying the fixed time / frequency offset to the time- and / or frequency-domain resource used for transmission of the downlink alert information request.

[0044] In response to the transmission of the indication of the MO to the network (e.g., via the downlink alert information request), the UE 10 may monitor in the indicated MO for the downlink alert information from the network (and receive the downlink alert information if transmitted by the network). In some examples, the downlink alert information may be sent via a physical downlink control channel (PDCCH). In some such examples, the downlink alert information may include a wake-up indication (e.g., downlink control information (DCI), such as DCI format 2_6 for UEs in a connected state or DCI format 2_7 for UEs in idle state). In some other examples, the downlink alert information may be sent via a physical downlink shared channel (PDSCH). In some such examples, the downlink alert information may include paging information (e.g., a paging control channel (PCCH) message). In some other examples, the downlink alert information may be sent via a wake-up signal (WUS). Additionally, or alternatively, the downlink alert information may be sent via a sidelink channel. For example, the UE 10 may receive the downlink alert information from the network via a UE 11 (e.g., via sidelink). That is, the network node 12 may transmit the downlink alert information to the UE 11 via a downlink, and the UE 11 may transmit (e.g., relay, forward) the downlink alert information to the UE 10 via a sidelink. The UE 10 may determine (e.g., choose) to operate in an active state or an inactive state based on the downlink alert information.

[0045] Additionally, in accordance with one or more aspects of the present disclosure, the network node 12 may receive, from the UE 10, the downlink alert information request which includes information on the MO (e.g., may indicate one or more UE-selected MOs). In one ormore embodiments, the network node 12 may either confirm or reject the UE-selected MOs. In some such embodiments, the network node 12 may recommend one or more different MOs and / or a different MO periodicity (e.g., may recommend a different configuration for the MOs). In some examples, the network node 12 may indicate a threshold quantity of time (e.g., a maximum time) the network node 12 buffers downlink data (e.g., information) for the UE 10. In such examples, the UE 10 may select one or more MOs that satisfy the threshold quantity of time (e.g., that are in intervals respecting the maximum time). The threshold quantity of time may be based on memory constraints at the network node 12, downlink traffic, or quality of service (QoS) constraints, among other examples of parameters that may impact a threshold quantity of time that the network node 12 buffers data for a UE. In accordance with one or more embodiments of the present disclosure, the network node 12 may buffer (or otherwise store) downlink data intended for the UE 10 (e.g., data for which the network node 12 may transmit the downlink alert information). In some examples, the network node 12 may buffer downlink data over a duration between reception of the downlink alert information request and the indicated one or more MOs (e.g., may buffer the downlink data in response to the downlink alert information request and until the indicated MO(s)). In some other examples, the network node 12 may buffer downlink data prior to reception of the downlink alert information request (e.g., until reception of the downlink alert information request). In some examples, in response to the downlink alert information request, the network node 12 may transmit the downlink alert information to the UE 10 on the indicated MO(s).

[0046] One or more techniques for UE-triggered downlink alert information, as described herein, may therefore provide a framework for the UE 10 to request downlink alert information from the network node 12. In some examples, such techniques may improve efficiencies for communications (e.g., loT-type of data transmissions) by the UE 10, which may provide for reduced power consumption at the UE 10 and increased sustainability of communications within the communications system of Figure 1.

[0047] The communication system of Figure 1 is also able to communicate with other networks, such as a public switched telephone network or the Internet 16, or utilize services provided by them. The communication system may be an example of a 5G network or one or more other types of networks (e.g., subsequent generations of networks), such as 5G- Advanced and 6G networks. The communications system may support the usage of cloud services, for example at least part of core network operations may be carried out as a cloudservice (this is depicted in Figure 1 by “cloud” 18). The communication system may comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.

[0048] In some examples of the communications system, such as examples in which the communication system is a 5G network, the communication system may utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. While various aspects of the present disclosure are described in the context of 5G, it is to be understood that the such aspects may also be applicable to other systems, such as subsequent generations of communications networks (e.g., 5G- Advanced and 6G). Some possible use cases for satellite communication include providing service continuity for machine-to-machine (M2M) or loT devices or for passengers on board vehicles, or ensuring service availability for critical communications, and future railway / maritime / aeronautical communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node or by a gNB located on-ground or in a satellite.

[0049] The depicted communication system of Figure 1 is an example of a part of a radio access system in which the communication system of Figure 1 may be deployed and in practice, the system may comprise a plurality of NodeBs, the user devices may have access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the NodeBs may be a Home nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The NodeBs of Figure 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of NodeBs may be used to provide such a network structure.

[0050] As shown in Figure 1, for example, a communications system may include a plurality of devices configured to communicate via respective channels. In this regard, theUE may include a transmitter configured to communicate with a receiver, for example, of a base station. Conversely, the base station may include a receiver and a transmitter for communicating with a receiver, for example, of the UE. By way of example, the communication system may be deployed within a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A), new radio (NR, 5G), 5G Advance, or 6G, among other subsequent generations. However, the system may be deployed in other applications including within other communication networks, such as a universal mobile telecommunications system (UMTS) radio access network (UTRAN or E-UTRAN), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof. In this regard, Figure 1 depicts an example of a simplified system architecture showing some elements and functional entities (e.g., logical units), whose implementation may differ from what is shown. The connections shown in Figure 1 are logical connections and corresponding physical connections may be different. It is apparent to a person skilled in the art that the system may comprises other functions and structures than those shown in Figure 1. In the radio access architecture of Figure 1 , the UE 10 may be configured to be in wireless connection on one or more communication channels in a cell with the network node 12 (such as a NodeB) providing the cell. The UE 10 and the network node 12 may communicate via an access link (e.g., a Uu link). As such, the network node 12 may also be referred to herein as an access node. The physical link from a user device (e.g., the UE 10) to a NodeB (e.g., the network node 12) is referred to as an uplink or reverse link and the physical link from the NodeB to the user device is referred to as a downlink or forward link. It should be appreciated that the NodeB s or their functionalities may be implemented by using any node, host, server, or access point (AP), etc. entity suitable for such a usage.

[0051] A communications system, such as the communication system of Figure 1 , may include more than one NodeB in which case the NodeB s may also be configured to communicate with one another over links, wired or wireless, designed for various purposes. For example, such links may be used for signaling purposes. The NodeB is a computing device configured to control the radio resources of the communication system to which the NodeB may be coupled. The NodeB may also be referred to as a base station, an access pointor any other type of interfacing device including a relay station capable of operating in a wired or wireless environment. The NodeB includes or is coupled to transceivers. From the transceivers of the NodeB, a connection is provided to an antenna unit that establishes bidirectional radio links to user devices. As such, the transceivers of the NodeB and the transceivers of the user devices may include transmitters and receivers configured to communicate via a channel with the trainable parameters of the transmitters and receivers able to be reconfigured in accordance with an example embodiment. The antenna unit may comprise a plurality of antennas or antenna elements. The NodeB is further connected to core network 15 (CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc. The user device (also referred to as a UE, user terminal, terminal device, etc.) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station.

[0052] A user device may refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink device (e.g., an uplink-only device), of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in an loT network which is a scenario in which objects are provided with the ability to transfer data over a network without human-to-human or human-to-computer interaction. In other words, the UE 10 may be an example of an loT device configured to operate in one or more loT networks. The user device (or in some embodiments a layer 3 relay node) is configured to perform one or more UE functionalities. The user device may also be referred to as a subscriber unit, mobile station, remote terminal, access terminal, user terminal or UE, among other names of apparatuses configured to support user device operations.

[0053] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of increased amounts of interconnected loT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0054] Although the apparatuses have been depicted as single entities, different units, processors and / or memory units (not all shown in Figure 1) may be implemented. Further, the number of reception and / or transmission antennas of the user devices may naturally vary according to a current implementation. In some examples, the communication system may enable the use of multiple input - multiple output (MIMO) antennas, and may include many more base stations or nodes than other types of communication systems (e.g., so-called small cell concept systems, such as may be associated with ETE), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and / or spectrum available. In some examples, the communication system may include a 5G network. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors, and real-time control. 5G may include multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integratable with existing legacy radio access technologies, such as the ETE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G may support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput, and mobility.

[0055] Some network architectures, such as in LTE networks, may be fully distributed in the radio and fully centralized in the core network. The low latency applications and servicesin 5G require bringing the content close to the radio which leads to local break out and multiaccess edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time- critical control, and healthcare applications).

[0056] The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 16, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 18). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.

[0057] Edge cloud may be brought into radio access network (RAN) by utilizing network function virtualization (NVF) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes, or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 12) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 14).

[0058] It should also be understood that the distribution of labor between core network operations and base station operations may differ based on implementation or even be nonexistent. Some other technology advancements that may be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio,NR) networks may support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in other types of networks as well.

[0059] For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” Node Bs, includes, in addition to Home NodeBs (HnodeBs), a home node B gateway, or HNB-GW (not shown in Figure 1). A HNB Gateway (HNB-GW), which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

[0060] One example of an apparatus 20 is depicted in Figure 2. As shown in Figure 2, the apparatus includes, is associated with, or is in communication with processing circuity 22, a memory 24 and a communication interface 26. The processing circuitry 22 may be in communication with the memory 24 (e.g., a memory device) via a bus for passing information among components of the apparatus. The memory device 24 may be non- transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device 24 may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processing circuitry 22). The memory device 24 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 20 to carry out various functions in accordance with an example embodiment of the present disclosure. For example, the memory device 24 could be configured to buffer input data for processing by the processing circuitry. Additionally, or alternatively, the memory device 24 could be configured to store instructions for execution by the processing circuitry. The apparatus 20 may, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus 20 may be embodied as a chip or chip set. In other words, the apparatus 20 may comprise one or more physical packages (e.g., chips) including materials, components and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. The apparatus 20 may therefore, in some cases, be configured to implement an embodiment of the present disclosure on a single chip or as a single “system on a chip.” As such, in some cases, a chipor chipset may constitute means for performing one or more operations for providing the functionalities described herein.

[0061] The processing circuitry 22 may be embodied in a number of different ways. For example, the processing circuitry 22 may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processing circuitry 22 may include one or more processing cores configured to perform independently. A multi-core processing circuitry may enable multiprocessing within a single physical package. Additionally, or alternatively, the processing circuitry 22 may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and / or multithreading. In an example embodiment, the processing circuitry 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processing circuitry.Alternatively, or additionally, the processing circuitry 22 may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processing circuitry 22 may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processing circuitry 22 is embodied as an ASIC, FPGA or the like, the processing circuitry may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processing circuitry 22 is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processing circuitry 22 may be a processor of a specific device (e.g., an image or video processing system) configured to employ an embodiment of the present disclosure by further configuration of the processing circuitry 22 by instructions for performing the algorithms and / or operations described herein. The processing circuitry 22 may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processing circuitry.

[0062] The communication interface 26 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and / or transmit data, including media content in the form of video or image files, one or more audio tracks or the like. In this regard, the communication interface 26 may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network. Additionally, or alternatively, the communication interface 26 may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface 26 may alternatively or also support wired communication. As such, for example, the communication interface 26 may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. The apparatus 20 may be (or be included in) one or more types of devices, such as an access node (e.g., a base station), a UE, and / or an loT device.

[0063] In one example embodiment, the network node 12 may include the apparatus 20. For example, the network node 12 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for UE-triggered downlink alert information, as described herein. In another example embodiment, the UE 10 may include the apparatus 20. For example, the UE 10 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for UE-triggered downlink alert information, as described herein. Additionally, or alternatively, the UE 11 may include the apparatus 20. For example, the UE 11 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for UE-triggered downlink alert information, as described herein.

[0064] The apparatus 20 may, in at least one example embodiment, be an LPWA loT device with relatively low energy availability. Additionally, the apparatus 20 may be used for multiple years (e.g., may be expected to last ten or more years). In some examples, the apparatus 20 may receive or transmit data sporadically and with relatively larger inter-packet intervals (e.g., hours). Accordingly, the apparatus 20 may be configured to support one or more techniques for UE-triggered downlink alert information, as described herein, such thatthe LPWA loT device may conserve energy (e.g., and thus extend the lifetime of the apparatus 20). For example, for LPWA loT use cases in which the downlink data may be sent infrequently, non-periodically and / or with a relatively large gap between two downlink data transmissions, the apparatus 20 may implement one or more techniques for UE-triggered downlink alert information, as described herein, to save power at the apparatus 20 (e.g., an LPWA loT UE) in handling downlink alert information. In some examples, by implementing such techniques, the apparatus 20 may avoid frequent listening of downlink alert information such as wake-up indication or paging information, for example, during RRC IDLE and / or RRC INACTIVE states.

[0065] For example, in accordance with one or more techniques for UE-triggered downlink alert information, as described herein, the apparatus 20 may autonomously determine one or more suitable (for UE power saving constraints) MOs to receive downlink alert information. In other words, the apparatus 20 autonomously determine durations in which the apparatus 20 is inactive for power saving purposes (e.g., in RRC IDLE and / or RRC INACTIVE states) and may select active durations (e.g., one or more MOs) in which it is available to receive downlink alert messages (e.g., based on the determined inactive durations). In other words, the apparatus 20 may select (e.g., at its convenience, based on a desired energy consumption rate) durations to become active for monitoring (e.g., and reception) of downlink messages, such as downlink alert messages from the network. Accordingly, the apparatus 20 sends a request for downlink alert information in which the request informs the network node of the determined MOs so that the network may transmit downlink alert information (e.g., potential downlink alert information) in the indicated MOs. In other words, the apparatus 20 queries (or requests) the network on any downlink information (e.g., downlink alert information) that is intended for the apparatus 20. The network node may transmit the downlink alert information in the indicated MOs in response to the MO indication (e.g., the downlink alert information request).

[0066] The downlink alert information may include information (e.g., any information) transmitted from the network to a UE that is indicative of availability of downlink data intended for the UE. Additionally, or alternatively, the downlink alert information may include scheduling information or system information. Upon receiving of the downlink alert information, the UE may prepare (e.g., is expected to prepare) one or more receivers at the UE for reception of the available downlink data. Additionally, as described herein, the inactive state refers to a power saving mode at the UE in which the UE is not monitoringdownlink signal. In some examples, the power saving mode may include an RRC IDLE state or an RRC INACTIVE state.

[0067] In some embodiments, the UE 10 may transmit a request for downlink alert information in accordance with one or more schemes for communication of downlink alert information. In some such embodiments, a scheme for communication of downlink alert information may be associated with a timing at which the network node 12 buffers downlink data for the UE 10 and / or a timing at which the UE 10 transmits a request for downlink alert information. At least one example embodiment of a scheme for communication of downlink alert information is illustrated in Figure 3 and at least one example embodiment of a scheme for communication of downlink alert information is illustrated in Figure 4. For example, a scheme may include one or more operations illustrated in Figure 3 and / or one or more operations illustrated in Figure 4. The UE 10 may select a scheme based on an indication from the network node 12. For example, the network node 12 may indicate a scheme for communication of the downlink information to the UE 10. That is, selection of the scheme may be performed by the gNB and indicated to the UE. Additionally, or alternatively, the network node 12 may indicate triggering criteria to the UE 10 for selection of a scheme. In such an example, the UE 10 may select a scheme based on the triggering criteria being satisfied. In some examples, the UE 10 may indicate the selected scheme to the network node 12.

[0068] Figure 3 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to provide for UE-triggered downlink alert information in accordance with an example embodiment. The process flow illustrates some respective operations performed at the UE 10 and a node 13. The UE 10 may be an example of a UE 10 illustrated by and described with reference to Figure 1. Additionally, the node 13 may be an example of a network node 12 or a UE 11 illustrated by and described with reference to Figure 1. One or more operations performed at the UE 10 and / or one or more operations performed at the node 13 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 10 and / or one or more operations performed at the node 13 may be omitted. Additionally, or alternatively, one or more other operations may be added. In the example of Figure 3, the UE 10 may be an LPWA loT device (e.g., a sensor in a large farming area or a smart-metering device), in which downlink data from the node 13 (e.g., the network node 12) may be sent tothe UE 10 relatively infrequently, non-periodically and / or with a relatively large gap between two downlink data transmissions.

[0069] As illustrated in Figure 3, the UE 10 may indicate one or more MOs to the node 13 (e.g., a gNB) by sending a request for downlink alert information. After sending the request, the UE 10 may transition to an inactive state. During (e.g., only during) the indicated MO(s), the UE 10 may transition to an active state (e.g., may become active, such as in accordance with a DRX on duration or another type of duration which may be similar to a WUS MO) to monitor for downlink alert information (e.g., any potential downlink alert information). The network (e.g., gNB) may buffer (e.g., is expected to buffer or otherwise store) downlink information, such as the downlink alert information and / or associated downlink data, during the inactive period of the UE 10 and send the downlink information to the UE 10 in the indicated MO(s).

[0070] At step 32, the UE 10 (e.g., an LPWA UE) may determine one or more MOs in which the UE 10 is available for reception of downlink alert information (e.g., where the UE 10 expects to receive any downlink alert information). For example, the MO(s) may correspond to suitable resources for monitoring for downlink alert information in an active state and, outside the MO(s) the UE 10 may operate in an inactive state to conserve power (e.g., if no downlink alert information is received in the MO(s), if the downlink alert information indicates a lack of downlink data for the UE). In some examples, the determination of the MO(s) may be based on downlink characteristics (e.g., downlink data or downlink alert information characteristics) indicated by the network. Additionally, or alternatively, the UE 10 may autonomously determine the MO(s) based on at least energy availability at the UE 10, an energy consumption rate at the UE 10, and / or a time criticality of one or more operations at the UE 10 (e.g., an loT operation, a non-IoT operation, an operation associated with an application). For example, the UE 10 may choose MO(s) with a relatively large inter-MO time interval based on one or more characteristics of expected downlink data (e.g., if the expected downlink data has a relatively large average interdownlink alert information-arrival, if the expected downlink data is delay tolerant, if the expected downlink data has a relatively low priority) and / or an energy availability of the UE 10 (e.g., if the energy availability is relatively low).

[0071] In some examples, at step 30, the UE 10 may receive control information from the node 13. The control information may include first control information indicative of the one or more downlink characteristics. For example, the first control information may beindicative of an average inter-packet-arrival time associated with downlink data for the UE 10, a time criticality associated with the downlink data for the UE 10, a priority associated with downlink data for the UE 10, a packet delay budget associated with downlink data for the UE 10, a frequency associated with downlink alert information transmissions, and / or a likelihood of a downlink alert information transmission occurring during a time interval.

[0072] Additionally, or alternatively, the control information may include second control information indicative of a set of candidate MOs for reception of the downlink alert information. For example, the determination of the MO(s) at step 32 may be based on one or more subsets of MOs (e.g., preferred subsets of MO(s)) indicated to the UE 10 by the network. In other words, the UE 10 may select the MO(s) from one or more candidate sets (e.g., subsets) of MO(s) indicated to the UE 10 by the network (e.g., directly from the network node 12 or via the UE 11). For example, in some loT deployments, multiple groups of UEs may monitor for a same occasion. In some examples, such as for relatively large groups of UEs, transmission of downlink alert information in an MO may lead to false wakeups for a relatively large quantity of UEs (e.g., within the group). That is, the downlink alert information may be applicable to (e.g., intended for) a portion of UEs in a group, but because the group of UEs monitor for a same occasion, the downlink alert information may be sent to (and thus wake-up) the group of UEs (e.g., rather than only the portion of UEs for which the downlink alert information is intended). Accordingly, the network may provide, to the UE and one or more other UEs with similar downlink traffic arrival times, one or more subsets of MO(s) from which the UEs may select the MO(s). In such an example, UEs with similar downlink traffic arrival times may select one or more of the same MOs, and UEs with different downlink arrival times may select one or more different MOs (e.g., so they don't wake up unnecessarily). Additionally, or alternatively, the control information may include third control information indicative of a scheme for communication of the downlink alert information. For example, the third control information (or the downlink alert information characteristics) may indicate to the UE 10 a scheme for obtaining the downlink alert information from the network node 12.

[0073] At step 34, the UE 10 may transmit a request for downlink alert information to the network. The UE 10 may transmit the request during a first time occasion. The request for downlink alert information may indicate an availability of the UE 10 to receive the downlink alert information in the MO(s) determined at step 32. In other words, the UE 10 may send a request for downlink alert information that is indicative of the MO(s) determined at step 32.In some examples, the request may be accompanied by a confirmation or rejection message from the network.

[0074] For example, responsive to the request, the UE 10 may receive a message from the network (e.g., directly via the network node 12 or indirectly via the UE 11). The message may indicate one or more resources for reception of the downlink alert information. The second time occasion may be based on the one or more resources. That is, the one or more resources may include one or more time-domain resources (e.g., and one or more frequencydomain resources) and the second time occasion may correspond to the one or more timedomain resources. In some examples, the message may be indicative of a confirmation of the MO(s) for reception of the downlink alert information at the UE 10. In such examples, the confirmation indicates that the one or more resources overlap at least a portion of the MO(s) indicated via the request. In some other examples, the message may include an indication of the one or more resources. In such examples, the one or more resources may overlap at least one MO that is different from the MO(s) indicated via the request. In other words, the network may reject the MO(s) indicated via the request and, as such, may transmit a rejection message to the UE 10. The rejection message may configure the UE 10 with one or more different MOs (e.g., one or more resources that overlap at least one MO that is different from the MO(s) indicated via the request).

[0075] In some examples, at step 35, the node 13 (e.g., a gNB) buffers or otherwise stores downlink information (e.g., downlink data, downlink alert information) intended for the UE 10. That is, for examples in which the node 13 is the network entity 12, the node 13 may buffer downlink information for the UE 10. In some examples, the network node 12 may buffer downlink information in response to the request and until (e.g., up to) the indicated MO(s). In other words, the node 13 may buffer downlink information intended for the UE 10 while the UE 10 operates in an inactive state.

[0076] In some examples, at step 36, the node 13 (e.g., a gNB, a UE) may transmit the downlink alert information to the UE 10 in response to the request. The node 13 may transmit the downlink information during a second time occasion, which is based on the one or more monitoring occasions. For example, the second time occasion may overlap with at least a portion of the one or more MOs (e.g., may coincide with at least a portion of the one or more MOs, may correspond to one or more time-domain resources that overlap with at least a portion of the one or more MOs). That is, in some examples, the gNB sends downlink alert information on the indicated MO(s). In some other examples, the second time occasion mayoverlap with at least a portion of an MO that is different from the one or more MOs indicated via the request. For example, the network node 12 may reject the indicated MO(s) and configure the UE 10 with another MO that is different from (e.g., non-overlapping with the time- and / or frequency-domain) the indicated MO(s).

[0077] In some examples, the downlink alert information may be indicative of a status associated with downlink data buffered between the first time occasion and the second time occasion. For example, the network may send a downlink alert message during an MO in one or more pre-configured time and / or frequency resources. In some such examples, the downlink alert information may indicate an availability of downlink data for the UE 10. Alternatively, the downlink alert information may indicate a lack (or unavailability) of downlink data for the UE 10. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE 10 may acquire, for example, to establish a connection with the network. In some examples, the downlink alert information may include downlink data.

[0078] In some examples, such as examples in which the node 13 is the network node 12, the node 13 may transmit the downlink alert information on a PDCCH or a PDSCH, in which the PDCCH includes, for example, a wake-up indication (e.g., DCI 2_6), and the PDSCH includes, for example, paging information (e.g., a PCCH). In some other examples, such as examples in which the node 13 is the UE 11, the node 13 may transmit the downlink alert information on a sidelink channel (e.g., a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH)). In some examples, the downlink alert information may enable the UE 10 to prepare to operate in an active state, for example, and follow on or more protocols to establish a connection with the network node 12 (e.g., to receive downlink data buffered at the network node 12).

[0079] In some examples, at step 38, the UE 10 may determine to operate in (e.g., may choses) the active or inactive state based on downlink alert information. For example, the UE 10 may determine to operate in accordance with the active state based on the status indicating the availability of downlink data for the UE 10. Alternatively, the UE 10 may determine tooperate in accordance with the inactive state based on the status indicating the lack of downlink data for the UE 10.

[0080] In some examples, the UE 10 may update a periodicity and configuration associated with MOs based on the received downlink alert information (or based on received downlink data information). In some such examples, the update may be implicitly known by the network. Additionally, or alternatively, the UE 10 may transmit an indication of the updated periodicity (or one or more second MO(s) selected in accordance with the periodicity) to the network. As an illustrative example, the UE 10, which initially selected (e.g., at step 32) one or more MOs with a first periodicity (e.g., of X seconds), may select one or more second MOs with a second periodicity. The second periodicity may be greater than the first periodicity (e.g., the UE 10 may increase the periodicity to 2X seconds or some other suitable multiple of X seconds), for example, if there is no available downlink data for the UE 10 (e.g., during 5 consecutive MOs, or some other suitable quantity of consecutive MOs).

[0081] Figure 4 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to provide for UE-triggered downlink alert information in accordance with an example embodiment. The process flow illustrates some respective operations performed at the UE 10 and the node 13. The UE 10 may be an example of a UE 10 illustrated by and described with reference to Figure 1. Additionally, the node 13 may be an example of a node 13 illustrated by and described with reference to Figure 3. For example, the network node 13 may be an example of a network node 12 or a UE 11 illustrated by and described with reference to Figure 1. One or more operations performed at the UE 10 and / or one or more operations performed at the node 13 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 10 and / or one or more operations performed at the node 13 may be omitted.Additionally, or alternatively, one or more other operations may be added. In the example of Figure 4, the UE 10 may be an LPWA loT device (e.g., a sensor in a large farming area or a smart-metering device), in which downlink data from the network node 12 may be sent to the UE 10 relatively infrequently, non-periodically, and / or with a relatively large gap between two downlink data transmissions.

[0082] As illustrated in the example of Figure 4, the UE 10 may operate in (e.g., remain in) an inactive state for an autonomously determined suitable duration (e.g., based on a desired energy consumption rate). The UE 10 may transition from the inactive sate to an active state, and while active (e.g., for a relatively brief duration, such as one or moremilliseconds), the UE 10 may transmit a request to the network (e.g., gNB) for downlink alert information. The network (e.g., gNB) may buffer (e.g., is expected to buffer or otherwise store) downlink information, such as the downlink alert information and / or associated downlink data, until the network receives (e.g., explicitly receives) the request from the UE 10.

[0083] At step 42, the UE 10 (e.g., an LPWA UE) may determine one or more MOs in which the UE 10 is available for reception of downlink alert information (e.g., where the UE 10 expects to receive any downlink alert information). For example, the MO(s) may correspond to suitable resources for monitoring for downlink alert information in an active state and, outside the MO(s) the UE 10 may operate in an inactive state to conserve power, for example, if no downlink alert information is received in the MO(s), or if the downlink alert information indicates a lack of downlink data for the UE. In some examples, the determination of the MO(s) may be based on downlink characteristics (e.g., downlink data or downlink alert information characteristics) indicated by the network. Additionally, or alternatively, the UE 10 may autonomously determine the MO(s) based on at least energy availability at the UE 10, an energy consumption rate at the UE 10, and / or a time criticality of one or more operations at the UE 10 (e.g., an loT operation, a non-IoT operation, an operation associated with an application). For example, the UE 10 may choose MO(s) with a relatively large inter-MO time interval based on one or more characteristics of expected downlink data (e.g., if the expected downlink data has a relatively large average interdownlink alert information-arrival, is delay tolerant, has a relatively low priority) and / or an energy availability of the UE 10 (e.g., if the energy availability is relatively low).

[0084] In some examples, at step 40, the UE 10 may receive control information from the node 13. The control information may include first control information indicative of the one or more downlink characteristics. For example, the first control information may be indicative of an average inter-packet-arrival time associated with downlink data for the UE 10, a time criticality associated with the downlink data for the UE 10, a priority associated with downlink data for the UE 10, a packet delay budget associated with downlink data for the UE 10, a frequency associated with downlink alert information transmissions, and / or a likelihood of a downlink alert information transmission occurring during a time interval.

[0085] Additionally, or alternatively, the control information may include second control information indicative of a set of candidate MOs for reception of the downlink alert information. For example, the determination of the MO(s) at step 42 may be based on one ormore subsets of MOs (e.g., preferred subsets of MO(s)) indicated to the UE 10 by the network. In other words, the UE 10 may select the MO(s) from one or more candidate sets (e.g., subsets) of MO(s) indicated to the UE 10 by the node 13. For example, in some loT deployments, multiple groups of UEs may monitor for a same occasion. In some examples, such as for relatively large groups of UEs, transmission of downlink alert information in an MO may lead to false wakeups for a relatively large quantity of UEs. That is, the downlink alert information may be applicable to (e.g., intended for) a portion of UEs in a group, but because the group of UEs monitor for a same occasion, the downlink alert information may be sent to (and thus wake-up) the group of UEs (e.g., rather than only the portion of UEs for which the downlink alert information is intended). Accordingly, the network may provide, to the UE 10 and one or more other UEs, one or more subsets of MO(s) from which the UEs may select the MO(s), so that UEs with similar downlink traffic arrival times may select the same MO(s), and UEs with different downlink arrival times may select different MO(s) (e.g., so they don't wake up unnecessarily). Additionally, or alternatively, the control information may include third control information indicative of a scheme for communication of the downlink alert information. For example, the third control information (or the downlink alert information characteristics) may indicate to the UE 10 a scheme for obtaining the downlink alert information from network (e.g., directly via the network node 12 or indirectly via the UE 11). The one or more schemes may be configured at the UE 10 via control signaling (e.g., the third control signaling). Additionally, or alternatively, or the one or more schemes may be otherwise configured at the UE 10. In some such examples, the third control signaling may indicate a scheme configured at the UE 10 (e.g., configured at the UE 10 via other control signaling form the network or otherwise configured at the UE 10). In other words, in some examples, the gNB may configure the UE 10 to use a scheme by sending a configuration message, which may include an explicit indication or a triggering-criteria to switch to the scheme from another scheme for communication of downlink alert information (e.g., any other scheme for downlink alert information). In some examples, the triggering criteria may include a threshold energy availability level. In such examples, the UE 10 may switch to the scheme from the other scheme based on an availability of energy at the UE 10 satisfying (e.g., falling below) the threshold energy availability level. As an illustrative example, if the energy availability level at the UE 10 falls below the threshold energy availability level, the UE 10 may switch to the scheme (e.g., recommended by the gNB). In some examples, when the UE 10 performs switching between schemes (e.g., from a first scheme to a secondscheme), the UE 10 may indicate a scheme to the gNB. In other words, responsive to switching from a first scheme to a second scheme (e.g., based on the switching criteria being satisfied), the UE 10 may transmit an indication of the second scheme to the network node.

[0086] In some examples, at step 44, the node 13 (e.g., gNB) buffers or otherwise stores downlink information (e.g., downlink data, downlink alert information) intended for the UE 10. For example, the network may buffer downlink information for the UE 10 prior to reception of the request (e.g., until it receives a request for downlink alert information with an indication of MO(s)) from the UE 10. For example, the indicated MO(s) may follow (e.g., immediately follow) a first time occasion during which the request is transmitted from the UE 10 and, as such, the node 13 may buffer downlink data for the UE 10 up to the first time occasion (e.g., may stop buffering downlink data for the UE 10 in response to receiving the request). In other words, the network node 12 may buffer downlink information intended for the UE 10 while the UE 10 operates in an inactive state.

[0087] At step 45, the UE 10 may transmit a request for downlink alert information to the network. The UE 10 may transmit the request during a first time occasion. The downlink alert information may indicate an availability of the UE 10 to receive the downlink alert information in the MO(s) determined at step 42. In other words, the UE 10 sends a request for downlink alert information to the network 12 and includes MO information in the request. In some examples, the indicated MO(s) may follow (e.g., are expected to follow) the first time occasion. For example, the first time occasion may be associated with one or more first resources and the second time occasion may be associated with one or more second resources following (e.g., subsequent to in the time-domain) the one or more first resources. To conserve power, the UE 10 may operate in the inactive state until the UE 10 determines to send the request. In other words, the UE 10 may transition from the inactive state to the active state such that the UE 10 may transmit the request.

[0088] In some examples, at step 46, the node 13 (e.g., a gNB, a UE) may transmit the downlink alert information to the UE 10 in response to the request. The node 13 may transmit the downlink information during a second time occasion, which is based on the one or more monitoring occasions. For example, the second time occasion may overlap with at least a portion of the MO(s) (e.g., may coincide with at least a portion of the MO(s), may correspond to one or more time-domain resources that overlap with at least a portion of the MO(s)). That is, the node 13 may send downlink alert information on the indicated MO(s).

[0089] In some examples, the downlink alert information may be indicative of a status associated with downlink data buffered between the first time occasion and the second time occasion. For example, the network may send a downlink alert message during an MO in one or more pre-configured time and / or frequency resources. In some such examples, the downlink alert information may indicate an availability of downlink data for the UE 10. Alternatively, the downlink alert information may indicate a lack (or unavailability) of downlink data for the UE 10. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE 10 may acquire, for example, to establish a connection with the network. In some examples, the downlink alert information may include downlink data.

[0090] In some examples, at step 48, the UE 10 may determine to operate in (e.g., may choses) the active or inactive state based on downlink alert information. For example, the UE 10 may determine to operate in accordance with the active state based on the status indicating the availability of downlink data for the UE 10. Alternatively, the UE 10 may determine to operate in accordance with the inactive state based on the status indicating the lack of downlink data for the UE 10. In some examples, by indicating the one or more MOs determined at step 42 to the network node 12, the UE 12 may reduce power consumption at the UE 12 and, as such, may increase power saving at the UE 12. Additionally, or alternatively, the UE 10 may determine to perform one or more operations based on the downlink alert information (e.g., in accordance with updated system information). In some examples, the UE 10 may determine to operate in the inactive state based on a lack of downlink alert information.

[0091] Referring now to Figure 5, some operations performed by the apparatus 20 (e.g., the UE 10) in order to provide for UE-triggered downlink alert information, in one example embodiment, are depicted. As shown in Figure 5, the apparatus 20 may request downlink alert information from a node (e.g., the network node 12, the UE 11).

[0092] As shown in block 50 of Figure 5, the apparatus 20 includes means (e.g., the processing circuitry 22, the memory device 24) for determining one or more MOs forreception of downlink alert information from the node. The apparatus 20 may, in some examples, determine the one or more MOs based on downlink characteristics (e.g., downlink data and / or downlink alert information characteristics). In some examples, the apparatus 20 may include means (e.g., the processing circuitry 22, the memory device 24) for selecting the one or more MOs from among a set of candidate MOs configured at the apparatus (e.g., indicated to the apparatus 20 by the network node, or otherwise configured at the apparatus 20). In some examples, the apparatus 20 may autonomously determine the one or more MOs, for example, based on an energy availability at the apparatus 20 and / or a time criticality associated with one or more operations at the apparatus 20 (e.g., one or more loT operations, one or more non-IoT operations, one or more operations associated with an application).

[0093] As shown in block 52 of Figure 5, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for transmission of a request for the downlink alert information from the node. The apparatus 20 may provide for transmission of the request, such that transmission of the request occurs during a first time occasion (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may include an indication of the one or more MOs determined at step 50. In other words, the apparatus 20 may indicate, via the request, the one or more MOs determined at step 50.

[0094] In some examples, the apparatus 20 may provide for transmission of the request in accordance with a scheme, such as a scheme illustrated by and described with reference to Figure 3 and / or Figure 4. For example, in accordance with a scheme illustrated by and described with reference to Figure 3, the apparatus 20 may provide for transmission of the request such that the network (e.g., the network node 12) may buffer downlink data for the apparatus 20 (e.g., in response to the request). That is, the request may trigger the network to buffer downlink data for the apparatus 20. Accordingly, in response to the request, the network may buffer downlink data for the apparatus 20 between the first time occasion and a second time occasion, in which the first time occasion is associated with the transmission of the request (e.g., and therefore also associated with the reception of the request at the network) and the second time occasion is associated with reception of the downlink alert information at the apparatus 20 (e.g., and therefore also associated with the transmission of the downlink alert information from the network). In accordance with such a scheme, an MO used for reception of the downlink alert information may occur some duration after transmission of the request. For example, the first time occasion and the second time occasionmay be separated by a duration during which the apparatus 20 operates in an inactive state. As such, the network may buffer (or otherwise store) the downlink information for the apparatus 20 during the inactive period of the apparatus 20 and send the downlink alert information in the MO (e.g., during an active period of the apparatus 20). The MO may include one or more second resources associated with the second time occasion, which may overlap with at least a portion of the one or more MOs determined at step 50, or a different MO.

[0095] As shown in block 54 of Figure 5, the apparatus 20 includes means (e.g., the processing circuitry 22, the memory device 24) for monitoring for the downlink alert information in response to the request. The apparatus 20 may monitor for the downlink alert information during a second time occasion which may be based on the one or more monitoring occasions. The downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion. For example, the downlink alert information may be indicative of a status associated with the downlink data buffered between the first time occasion and the second time occasion. For example, the downlink alert information may indicate an availability of downlink data for the apparatus 20. In such an example, the status corresponds to an availability of the downlink data. In some other examples, the downlink alert information may indicate a lack of downlink data for the apparatus 20. In such examples, the status corresponds to the lack (or unavailability) of downlink data for the apparatus 20. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE 10 may acquire, for example, to establish a connection with the network (e.g., for reception of the downlink data). In some examples, the downlink alert information may include downlink data.

[0096] In some examples, the apparatus 20 may include the means (e.g., the processing circuitry 22, the communication interface 26) for receiving the downlink alert information in response to the request. The apparatus 20 may receive the downlink alert information during the second time occasion, which may be based on the one or more MOs. For example, thesecond time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of the one or more MOs. In another example, the second time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of an MO, which is different from the one or more MOs. In such an example, the MO may be determined based on the one or more MOs. For example, the MO may be determined based on a rejection of the one or more MOs by the network node. The MO may be determined at the apparatus 20 or the MO may be determined at the node and then indicated to the apparatus 20. In some examples, the node may reject the one or more MOs based on a scheduling conflict (e.g., for the apparatus and / or one or more other apparatuses). In some examples, the one or more MOs may be considered in a determination of the MO, such that the MO may be suitable for the apparatus 20.

[0097] In some examples, the apparatus 20 may receive the downlink alert information in accordance with the active state. Additionally, in some examples, the apparatus 20 may determine to operate in (e.g., may select, may choose) an inactive state or the active state based on the downlink alert information (e.g., based on the status of the downlink data, based on the control information). In other words, based on the downlink alert information, the apparatus 20 may transition to an inactive state or continue to operate in the active state.

[0098] Referring now to Figure 6, some operations performed at the apparatus 20 (e.g., the node 13, which may be an example of the network node 12 or the UE 11) in order to provide for UE-triggered downlink alert information, in one example embodiment, are depicted. As shown in Figure 6, the apparatus 20 may transmit downlink alert information to a UE (e.g., the UE 10, which may be an example of an LPWA loT device).

[0099] As shown in block 60 of Figure 6, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for receiving a request for downlink alert information from the UE. The apparatus 20 may receive the request during a first time occasion (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may be indicative of one or more MOs for transmission of the downlink alert information to the UE. The one or more MOs may correspond to time- and / or frequency-domain resources in which the UE is available to receive the downlink alert information.

[0100] As shown in block 62 of Figure 6, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for providing for transmission of the downlink alert information to the UE. The apparatus 20 may provide for the transmission ofthe downlink alert information during a second time occasion, which may be based on the one or more MOs. In some examples, the second time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of the one or more MOs. For example, the apparatus 20 may accept the one or more MOs and, in some examples, provide for transmission of a confirmation message to the UE. In such an example, the confirmation message may indicate that the one or more time- and / or frequency-domain resources for reception of the downlink alert information overlap with at least a portion of the one or more MOs. In some other examples, the second time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of an MO, which is different from the one or more MOs. For example, the apparatus 20 may reject the one or more MOs (e.g., due to a scheduling conflict at the UE and / or one or more other UEs) and, in some examples, may transmit a message to the UE indicating one or more time- and / or frequency-domain resources that overlap with at least a portion of an MO that is different from the one or more MOs. In such an example, the MO may be determined at the apparatus 20 based on the one or more MOs. For example, the one or more MOs may be considered in a determination of the MO, such that the MO may be suitable for the UE.

[0101] In some examples, in response to the request, the network (e.g., the apparatus 20 or another apparatus) may buffer downlink data for the UE. Accordingly, the downlink alert information may be associated with downlink data buffered at the network. In some examples, the downlink alert information may be indicative of a status associated with downlink data buffered between the first time occasion and the second time occasion. For example, the downlink alert information may indicate an availability of downlink data for the UE. In such an example, the status corresponds to an availability of the downlink data. In some other examples, the downlink alert information may indicate a lack of downlink data for the UE. In such examples, the status corresponds to the lack (or unavailability) of downlink data for the UE. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE may acquire, for example, to establish a connection with the network(e.g., for reception of the downlink data). In some examples, the downlink alert information may include downlink data.

[0102] Referring now to Figure 7, some operations performed by the apparatus 20 (e.g., the UE 10) in order to provide for UE-triggered downlink alert information, in one example embodiment, are depicted. As shown in Figure 7, the apparatus 20 may request downlink alert information from a node (e.g., the network node 12, the UE 11).

[0103] As shown in block 70 of Figure 7, the apparatus 20 includes means (e.g., the processing circuitry 22, the memory device 24) for determining one or more MOs for reception of downlink alert information from the node. The apparatus 20 may, in some examples, determine the one or more MOs based on downlink characteristics (e.g., downlink data and / or downlink alert information characteristics). In some examples, the apparatus 20 may include means (e.g., the processing circuitry 22, the memory device 24) for selecting the one or more MOs from among a set of candidate MOs configured at the apparatus (e.g., indicated to the apparatus 20 by the network node, or otherwise configured at the apparatus 20). In some examples, the apparatus 20 may autonomously determine the one or more MOs, for example, based on an energy availability at the apparatus 20 and / or a time criticality associated with one or more operations at the apparatus 20 (e.g., one or more loT operations, one or more non-IoT operations, one or more operations associated with an application).

[0104] As shown in block 72 of Figure 7, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for providing for transmission of a request for the downlink alert information from the node. The apparatus 20 may provide for transmission of the request, such that transmission of the request occurs during a first time occasion (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may include an indication of the one or more MOs determined at step 70. In other words, the apparatus 20 may indicate, via the request, the one or more MOs determined at step 70.

[0105] In some examples, the apparatus 20 may provide for transmission of the request in accordance with a scheme, such as a scheme illustrated by and described with reference to Figure 3 and / or Figure 4. For example, in accordance with a scheme illustrated by and described with reference to Figure 4, the apparatus 20 may provide for transmission of the request such that the network (e.g., the network node 12) may buffer downlink data for the apparatus 20 prior to (e.g., until) reception of the request by the network. That is, the network may buffer downlink data for the apparatus 20 prior to the first time occasion associated withthe transmission of the request (e.g., and thus the reception of the request at the network). In accordance with such a scheme, an MO used for reception of the downlink alert information may follow the first time occasion (e.g., may immediately follow the first time occasion, may be subsequent to the first time occasion). That is, the second time occasion may be associated with one or more second resources which follow (e.g., immediately follow, are subsequent to) one or more first resources associated with the first time occasion. Accordingly, in some examples, the apparatus 20 includes means (e.g., the processing circuitry 22, the memory device 24) for providing for transition at the apparatus 20 from an inactive state to an active state, such that the apparatus 20 may provide for transmission of the request (and subsequently reception of the downlink alert information) in the active state.

[0106] As shown in block 74 of Figure 7, the apparatus 20 includes means (e.g., the processing circuitry 22, the memory device 24) for monitoring for the downlink alert information in response to the request. The apparatus 20 may monitor for the downlink alert information during a second time occasion which may be based on the one or more monitoring occasions. The downlink alert information is associated with downlink data buffered prior to the first time occasion. For example, the downlink alert information may be indicative of a status associated with the downlink data buffered prior to the first time occasion. For example, the downlink alert information may indicate an availability of downlink data for the apparatus 20. In such an example, the status corresponds to an availability of the downlink data. In some other examples, the downlink alert information may indicate a lack of downlink data for the apparatus 20. In such examples, the status corresponds to the lack (or unavailability) of downlink data for the apparatus 20. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE 10 may acquire, for example, to establish a connection with the network (e.g., for reception of the downlink data). In some examples, the downlink alert information may include downlink data.

[0107] In some examples, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for receiving the downlink alert information in responseto the request. The apparatus 20 may receive the downlink alert information during the second time occasion, in which the second time occasion is based on the one or more MOs. For example, the second time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of the one or more MOs. The apparatus may determine to operate in (e.g., may select, may choose) an inactive state or an active state based on the downlink alert information (e.g., based on the status of the downlink data). In some examples, the apparatus 20 may receive the downlink alert information in accordance with the active state. Additionally, in some examples, the apparatus may determine to operate in (e.g., may select, may choose) an inactive state or the active state based on the downlink alert information (e.g., based on the status of the downlink data). In other words, based on the downlink alert information, the apparatus 20 may transition to an inactive state or continue to operate in the active state.

[0108] Referring now to Figure 8, some operations performed at the apparatus 20 (e.g., the node 13, which may be an example of the network node 12 or the UE 11) in order to provide for UE-triggered downlink alert information, in one example embodiment, are depicted. As shown in Figure 8, the apparatus 20 may transmit downlink alert information to a UE (e.g., the UE 10, which may be an example of an LPWA loT device).

[0109] As shown in block 80 of Figure 8, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for receiving a request for downlink alert information from the UE. The apparatus 20 may receive the request during a first time occasion (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may be indicative of one or more MOs for transmission of the downlink alert information to the UE. The one or more MOs may correspond to time- and / or frequency-domain resources in which the UE is available to receive the downlink alert information.

[0110] As shown in block 82 of Figure 8, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26) for providing for transmission of the downlink alert information to the UE. The apparatus 20 may provide for the transmission of the downlink alert information during a second time occasion, which may be based on the one or more MOs. In some examples, the second time occasion may correspond to one or more time- and / or frequency-domain resources that overlap with at least a portion of the one or more MOs. The network (e.g., the apparatus 20 or another apparatus) may buffer downlink data for the UE prior to (e.g., until) reception of the request. Accordingly, the downlink alertinformation may be indicative of a status associated with downlink data buffered prior to the first time occasion. For example, the downlink alert information may indicate an availability of downlink data for the UE. In such an example, the status corresponds to an availability of the downlink data. In some other examples, the downlink alert information may indicate a lack of downlink data for the UE. In such examples, the status corresponds to the lack (or unavailability) of downlink data for the UE. In some other examples, the downlink alert information may include control information (e.g., scheduling information or system information). For example, the downlink alert information may include control information which may include scheduling information (e.g., time and / or frequency resource) for reception of a downlink alert message. In such an example, the downlink alert message (e.g., indicative of a status of the downlink data) may be sent from the network via a data channel in the indicate resource(s). Additionally, or alternatively, the downlink alert information may include system information that the UE may acquire, for example, to establish a connection with the network (e.g., for reception of the downlink data). In some examples, the downlink alert information may include downlink data.

[0111] As described above, methods, apparatuses, and computer program products are disclosed to provide for UE-triggered downlink alert information. In this regard, a method, apparatus, and computer program product are configured to provide for the transmission of a request for downlink alert information from a network node. By providing for the transmission of the request for the downlink alert information, the method, apparatus, and computer program product may provide for reduced power consumption at a UE. In some aspects, reduced power consumption may lead to an increased lifetime for the UE, as well as data being communicated with the UE more effectively and over wider coverage areas.

[0112] Figures 5-8 illustrate flowcharts depicting methods according to an example embodiment of the present disclosure. It will be understood that each block of the flowcharts and combination of blocks in the flowcharts may be implemented by various means, such as hardware, firmware, processor, circuitry, and / or other communication devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 24 of an apparatus 20 employing an embodiment of the present disclosure and executed by a processor 22. As will be appreciated, any such computer program instructions may be loaded onto a computer or otherprogrammable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations 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 operations for implementing the functions specified in the flowchart blocks. Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions. Many modifications and other embodiments of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the example embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe some example embodiments in the context of some example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense and not for purposes of limitation.

Claims

What is claimed is:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine one or more monitoring occasions for reception of downlink alert information from a node; provide, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions; and monitor, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

2. An apparatus according to claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: responsive to the request, receive a message from the node, wherein the message is indicative of one or more resources for reception of the downlink alert information, and wherein the second time occasion is based at least in part on the one or more resources.

3. An apparatus according to claim 2, wherein the message is indicative of a confirmation of the one or more monitoring occasions for reception of the downlink alert information at the apparatus, and wherein the confirmation indicates that the one or more resources overlap at least a portion of the one or more monitoring occasions.

4. An apparatus according to claim 2, wherein the message comprises an indication of the one or more resources, and wherein the one or more resources overlap at least one monitoring occasion that is different from the one or more monitoring occasions.

5. An apparatus according to any one of claims 1-4, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive the downlink alert information from the node during the second time occasion based at least in part on the monitoring.

6. An apparatus according to claim 5, wherein the downlink alert information comprises at least one of the following: system information associated with reception of the downlink data from the node or an indication of one or more resources for reception of a downlink alert message from the node.

7. An apparatus according to claim 5, wherein the downlink alert information comprises a downlink alert message, and wherein the downlink alert message is indicative of a status associated with the downlink data.

8. An apparatus according to claim 7, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: determine to operate in accordance with an active state or an inactive state based at least in part on the downlink alert message.

9. An apparatus according to claim 8, wherein the status indicates an availability of downlink data for the apparatus, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: determine to operate in accordance with the active state based at least in part on the status indicating the availability of downlink data for the apparatus.

10. An apparatus according to claim 8, wherein the status indicates a lack of downlink data for the apparatus, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: determine to operate in accordance with the inactive state based at least in part on the status indicating the lack of downlink data for the apparatus.

11. An apparatus according to claim 10, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: determine a second one or more monitoring occasions based at least in part on the lack of downlink data for the apparatus, wherein a first periodicity associated with the one or more monitoring occasions is less than a second periodicity associated with the second one or more monitoring occasions; and provide for transmission of an indication of the second one or more monitoring occasions to the node.

12. An apparatus according to any one of claims 1-11, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive first control information from the node, wherein the first control information is indicative of one or more downlink characteristics, and wherein determination of the one or more monitoring occasions is based at least in part on the one or more downlink characteristics.

13. An apparatus according to claim 12, wherein the one or more downlink characteristics comprise at least one of the following: an average inter-packet-arrival time associated with the downlink data, a time criticality associated with the downlink data, a priority associated with the downlink data, a packet delay budget associated with the downlink data, a frequency associated with downlink alert information transmissions, or a likelihood of a downlink alert information transmission occurring during a time interval.

14. An apparatus according to any one of claims 1-13, wherein determination of the one or more monitoring occasions is based at least in part on at least one of the following: an availability of energy at the apparatus, a rate of energy consumption at the apparatus, or a time criticality associated with one or more operations at the apparatus.

15. An apparatus according to any one of claims 1-14, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive second control information from the node, wherein the second controlinformation is indicative of a set of candidate monitoring occasions for reception of the downlink alert information, and wherein determination of the one or more monitoring occasions is based at least in part on the set of candidate monitoring occasions.

16. An apparatus according to any one of claims 1-15, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive third control information from the node, wherein the third control information is indicative of a scheme for communication of the downlink alert information, and wherein transmission of the request is in accordance with the scheme.

17. An apparatus according to any one of claims 1-15, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: switch from a first scheme for communication of other downlink alert information to a second scheme for communication of the downlink alert information, wherein transmission of the request is in accordance with the second scheme based at least in part on the switch.

18. An apparatus according to claim 17, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive, from the node, an indication of a second request to switch from the first scheme to the second scheme, wherein the switch is in response to the second request.

19. An apparatus according to claim 17, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive, from the node, a first indication of triggering criteria associated with a switch from the first scheme to the second scheme, wherein the switch is based at least in part on the triggering criteria being satisfied.

20. An apparatus according to claim 19, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: responsive to the switch, provide for transmission of a second indication of the second scheme to the node.

21. An apparatus according to claim 19, wherein the triggering criteria comprises a threshold energy availability level, and wherein the switch is based at least in part on an availability of energy at the apparatus satisfying the threshold energy availability level.

22. An apparatus according to any one of claims 1-21, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: monitor a physical downlink control channel or a physical downlink shared channel for the downlink alert information.

23. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE); and provide, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

24. A method comprising: determining, at a user equipment, one or more monitoring occasions for reception of downlink alert information from a node; providing, during a first time occasion, for transmission of a request for the downlink alert information, wherein the request is indicative of the one or more monitoring occasions; and monitoring, during a second time occasion, for the downlink alert information in response to the request, wherein the second time occasion is based at least in part on the oneor more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered between the first time occasion and the second time occasion.

25. A method comprising: receiving, during a first time occasion, a request for downlink alert information, wherein the request is indicative of one or more monitoring occasions for transmission of the downlink alert information to a user equipment (UE); and providing, during a second time occasion, for transmission of the downlink alert information to the UE, wherein the second time occasion is based at least in part on the one or more monitoring occasions, and wherein the downlink alert information is associated with downlink data buffered at a node between the first time occasion and the second time occasion.

Images