Methods, apparatus, and computer program products for providing downlink alarm information triggered by a UE.

By providing a framework for LPWA IoT devices to autonomously select monitoring timing and network caching mechanisms, the problem of increased power consumption of LPWA IoT devices in low-energy environments is solved, thereby extending device lifespan and improving communication system efficiency.

CN123125964APending Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580028161.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-19
Filing Date
2025-04-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

LPWA IoT devices frequently monitor network signaling in low-energy environments, leading to increased power consumption and affecting device lifespan. Existing power-saving mechanisms such as WUS and MICO modes still consume relatively high power in certain scenarios and cannot effectively extend device lifespan.

Method used

A framework is provided that allows LPWA IoT devices to autonomously select monitoring times (MO), reduce unnecessary monitoring by requesting and receiving downlink alarm information, and optimize energy use by combining network node caching mechanisms.

Benefits of technology

By optimizing monitoring timing and network caching, the power consumption of LPWA IoT devices has been reduced, extending device lifespan and improving the sustainability and efficiency of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125964A_ABST
    Figure CN123125964A_ABST
Patent Text Reader

Abstract

Methods, apparatus, and computer program products for providing downlink alarm information triggered by a UE. In the context of one method, the method includes: at a user equipment (UE), determining one or more monitoring opportunities for receiving downlink alarm information from a node; during a first time opportunity, providing the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities; and during a second time opportunity, monitoring the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached between the first and second time opportunities.
Need to check novelty before this filing date? Find Prior Art

Description

Cross-references to related applications

[0001] This application claims priority to Finnish application No. 20245501, filed on April 19, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The example embodiments generally relate to techniques for UE-triggered (user equipment-triggered) downlink alarm information, and more specifically, to a framework for requesting downlink alarm information from network nodes. Background Technology

[0003] Some wireless communication systems can include low-power wide-area (LPWA) Internet of Things (IoT) devices. For example, wireless communication systems can use LPWA IoT devices to provide connectivity in both rural and remote areas (e.g., coverage in areas where cellular connectivity may be difficult to obtain). In some cases, LPWA technologies have power designs that allow devices to operate on batteries for many years (e.g., 10 years), improving the sustainability of communication technologies in both rural and remote areas. Furthermore, some LPWA technologies can facilitate relatively large IoT deployments, accommodating a relatively large number of devices and improving the scalability of IoT. In some cases, LPWA technologies can help integrate sensing and communication, and are used in applications that utilize sensing and low-rate data transmission. For example, LPWA technologies can be cost-effective in terms of device hardware and operating costs. Therefore, LPWA technologies can improve the affordability of wireless communication for a wider range of applications. Summary of the Invention

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

[0005] In an example embodiment, an apparatus is provided comprising: at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, such that the apparatus at least: determines, at a user equipment (UE), one or more monitoring opportunities for receiving downlink alarm information from a node. The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus, during a first time opportunity, provides the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus, during a second time opportunity, monitors the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached between the first time opportunity and the second time opportunity.

[0006] In an example embodiment, an apparatus is provided comprising: at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, such that the apparatus at least: during a first time opportunity, receives a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities for the transmission of downlink alarm information to a user equipment (UE). The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus: during a second time opportunity, provides the transmission of downlink alarm information to the UE, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached at a node between the first time opportunity and the second time opportunity.

[0007] In an example embodiment, an apparatus is provided, comprising: at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, such that the apparatus at least: determines, at a user equipment (UE), one or more monitoring opportunities for receiving downlink alarm information from a node. The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus, during a first time opportunity, provides the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus, during a second time opportunity, monitors the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached prior to the first time opportunity.

[0008] In an example embodiment, an apparatus is provided comprising: at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, such that the apparatus at least: during a first timing period, receives a request for downlink alarm information, wherein the request indicates one or more monitoring timings for the transmission of downlink alarm information to a user equipment (UE). The at least one memory and the computer program code are also configured, together with the at least one processor, such that the apparatus: during a second timing period, provides the transmission of downlink alarm information to the UE, wherein the second timing period is at least partially based on one or more monitoring timings, and wherein the downlink alarm information is associated with downlink data cached at a node prior to the first timing period.

[0009] In an example embodiment, a method is provided that includes: at a user equipment (UE), determining one or more monitoring opportunities for receiving downlink alarm information from a node. The method further includes: during a first time opportunity, providing the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The method further includes: during a second time opportunity, monitoring the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached between the first and second time opportunities.

[0010] In an example embodiment, a method is provided that includes: during a first time period, receiving a request for downlink alarm information, wherein the request indicates one or more monitoring times for the transmission of the downlink alarm information to a user equipment (UE). The method further includes: during a second time period, providing the transmission of the downlink alarm information to the UE, wherein the second time period is at least partially based on one or more monitoring times, and wherein the downlink alarm information is associated with downlink data cached at a node between the first and second time periods.

[0011] In an example embodiment, a method is provided that includes: at a user equipment (UE), determining one or more monitoring opportunities for receiving downlink alarm information from a node. The method further includes: during a first time opportunity, providing the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The method further includes: during a second time opportunity, monitoring the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached prior to the first time opportunity.

[0012] In an example embodiment, a method is provided that includes: during a first time period, receiving a request for downlink alarm information, wherein the request indicates one or more monitoring times for the transmission of the downlink alarm information to a user equipment (UE). The method further includes: during a second time period, providing the transmission of the downlink alarm information to the UE, wherein the second time period is at least partially based on one or more monitoring times, and wherein the downlink alarm information is associated with downlink data cached at a node prior to the first time period.

[0013] In an example embodiment, a non-transitory computer-readable storage medium includes computer instructions that, when executed by a device, cause the device to: at a user equipment (UE), determine one or more monitoring opportunities for receiving downlink alarm information from a node. The computer-executable program code instructions also include program code instructions configured to, when executed,: during a first time opportunity, provide the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The computer-executable program code instructions also include program code instructions configured to, when executed,: during a second time opportunity, monitor the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached between the first and second time opportunities.

[0014] In an example embodiment, a non-transitory computer-readable storage medium includes computer instructions that, when executed by a device, cause the device to: receive a request for downlink alarm information during a first time opportunity, wherein the request indicates one or more monitoring opportunities for the transmission of the downlink alarm information to a user equipment (UE). The computer-executable program code instructions also include program code instructions configured to, when executed,: provide the transmission of downlink alarm information to the UE during a second time opportunity, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached at a node between the first and second time opportunities.

[0015] In an example embodiment, a non-transitory computer-readable storage medium includes computer instructions that, when executed by a device, cause the device to: at a user equipment (UE), determine one or more monitoring opportunities for receiving downlink alarm information from a node. The computer-executable program code instructions also include program code instructions configured to, when executed,: during a first time opportunity, provide the transmission of a request for downlink alarm information, wherein the request indicates one or more monitoring opportunities. The computer-executable program code instructions also include program code instructions configured to, when executed,: during a second time opportunity, monitor the downlink alarm information in response to the request, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached prior to the first time opportunity.

[0016] In an example embodiment, a non-transitory computer-readable storage medium includes computer instructions that, when executed by a device, cause the device to: receive a request for downlink alarm information during a first timing period, wherein the request indicates one or more monitoring timings for the transmission of the downlink alarm information to a user equipment (UE). The computer-executable program code instructions also include program code instructions configured to, when executed,: provide the transmission of downlink alarm information to the UE during a second timing period, wherein the second timing period is at least partially based on one or more monitoring timings, and wherein the downlink alarm information is associated with downlink data cached at a node prior to the first timing period.

[0017] In an example embodiment, an apparatus is provided, comprising: means for determining one or more monitoring times at a user equipment (UE) for receiving downlink alarm information from a node. The apparatus further comprises: means for providing the transmission of a request for the downlink alarm information during a first time period, wherein the request indicates one or more monitoring times. The apparatus further comprises: means for monitoring the downlink alarm information in response to the request during a second time period, wherein the second time period is at least partially based on one or more monitoring times, and wherein the downlink alarm information is associated with downlink data cached between the first and second time periods.

[0018] In an example embodiment, an apparatus is provided, comprising: components for receiving a request for downlink alarm information during a first time opportunity, wherein the request indicates one or more monitoring opportunities for the transmission of the downlink alarm information to a user equipment (UE). The apparatus further comprises: components for providing the transmission of the downlink alarm information to the UE during a second time opportunity, wherein the second time opportunity is at least partially based on one or more monitoring opportunities, and wherein the downlink alarm information is associated with downlink data cached at a node between the first and second time opportunities.

[0019] In an example embodiment, an apparatus is provided, comprising: means for determining one or more monitoring times at a user equipment (UE) for receiving downlink alarm information from a node. The apparatus further comprises: means for providing the transmission of a request for the downlink alarm information during a first time period, wherein the request indicates one or more monitoring times. The apparatus further comprises: means for monitoring the downlink alarm information in response to the request during a second time period, wherein the second time period is at least partially based on one or more monitoring times, and wherein the downlink alarm information is associated with downlink data cached prior to the first time period.

[0020] In an example embodiment, an apparatus is provided, comprising: components for receiving a request for downlink alarm information during a first timing period, wherein the request indicates one or more monitoring timings for the transmission of the downlink alarm information to a user equipment (UE). The apparatus further comprises: components for providing the transmission of the downlink alarm information to the UE during a second timing period, wherein the second timing period is at least partially based on one or more monitoring timings, and wherein the downlink alarm information is associated with downlink data cached at a node prior to the first timing period. Attached Figure Description

[0021] Some exemplary embodiments of this disclosure have been described in general terms. The following description will refer to the accompanying drawings, which are not necessarily drawn to scale, and in the drawings:

[0022] Figure 1 This is a block diagram of an example communication system. Figure 2 The device can be deployed in this example communication system;

[0023] Figure 2 This is a block diagram of an apparatus that can be specifically configured according to exemplary embodiments of the present disclosure;

[0024] Figure 3 The illustration is based on an example embodiment, such as in Figure 1 The processing flow of operations executed within the communication system to provide downlink alarm information triggered by the UE;

[0025] Figure 4 The illustration is based on an example embodiment, such as in Figure 1 The processing flow of operations executed within the communication system to provide downlink alarm information triggered by the UE;

[0026] Figure 5 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating the operations performed by an example embodiment of the device for providing downlink alarm information triggered by a UE;

[0027] Figure 6 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating an example embodiment of the device performing operations for providing downlink alarm information triggered by a UE;

[0028] Figure 7 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating operations performed by an example embodiment of the device for providing downlink alarm information triggered by a UE; and

[0029] Figure 8 The illustration is based on an example embodiment, such as by Figure 2 A flowchart of an example embodiment of the device performing operations for providing downlink alarm information triggered by the UE. Detailed Implementation

[0030] Some embodiments of this disclosure will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments of this disclosure. In fact, various embodiments of this disclosure may be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein; rather, these exemplary embodiments are provided so that this disclosure will satisfy applicable legal requirements. The same reference numerals throughout refer to the same elements. 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 according to some embodiments of this disclosure. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the exemplary embodiments of this disclosure.

[0031] Additionally, as used herein, the term "circuit system" means (a) a hardware circuit implementation only (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of a circuit and (multiple) computer program products, the computer program products comprising software and / or firmware instructions stored on one or more computer-readable storage media, the software and / or firmware instructions working together to cause a device to perform one or more functions described herein; and (c) a circuit, such as (multiple) microprocessors or a portion thereof, that operates using software or firmware, even if the software or firmware is not physically present. This definition of "circuit system" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also includes an implementation comprising one or more processors and / or portions thereof, along with accompanying software and / or firmware. As another example, as used herein, the term "circuit system" also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, other network devices (such as core network devices), field-programmable gate arrays, and / or other computing devices.

[0032] like Figure 1As illustrated in the examples, a communication system may include one or more UEs, such as UE 10. In some embodiments, UE 10 may be an example of an IoT device, such as an LPWA IoT device. For example, a wireless communication system may include one or more LPWA IoT devices (such as UE 10) to broaden the deployment of IoT devices (e.g., to enable widespread IoT deployment). As described herein, an LPWA IoT device refers to a device that consumes a relatively low amount of power while providing a relatively wide coverage area. In other words, an LPWA IoT device includes devices with low power consumption and wide coverage areas. In some examples, an LPWA IoT device (e.g., UE 10) can transmit a relatively small amount of data over relatively long distances or under challenging wireless conditions. Therefore, a wireless communication system can use LPWA IoT devices to provide connectivity in both rural and remote areas (e.g., coverage in areas where cellular connectivity may not be readily available). In some examples, LPWA technologies have an energy design (e.g., a high-efficiency design) that allows devices to operate for many years (e.g., 10 years) using a single battery, thereby improving the sustainability of the communication technology. Furthermore, some LPWA technologies can facilitate relatively large IoT deployments that can accommodate a relatively large number of devices and improve the scalability of IoT technologies. In some examples, LPWA technology can help integrate sensing and communication, and therefore can be used in applications ranging from environmental monitoring to smart agriculture (e.g., applications utilizing sensing and low-rate data transmission). In some examples, LPWA technology can be associated with relatively low costs (e.g., it can be cost-effective), for example, in terms of both device hardware and operating costs. Therefore, LPWA technology can improve the affordability of wireless communication (e.g., cellular communication) for a wider range of applications. In some examples, LPWA technology can generate relatively large amounts of data from sensors. Such data can be fed into artificial intelligence (AI) algorithms, for example, for analysis and intelligent decision-making.

[0033] For example, an LPWA IoT device (e.g., an LPWA IoT UE, such as UE 10) can be an example of an IoT device with strict power constraints (e.g., constrained energy storage or energy availability). Additionally, some such devices can be deployed in an area where the device can communicate over a relatively wide area (e.g., compared to a dense deployment scenario). As an illustrative example, an LPWA IoT device can be deployed in farmland (e.g., a large farmland) or a factory (e.g., a large factory), where the access point or control node (e.g., network node 12) is relatively far from the LPWA IoT device. Communication over a relatively wide area can consume more power than, for example, communication over a relatively narrow area. In some cases, to increase the lifespan of the LPWA IoT device (e.g., to increase the amount of time the LPWA IoT device can operate using battery power), the LPWA IoT device can implement one or more technologies for reducing power consumption. For example, the LPWA IoT device can implement one or more technologies that enable the LPWA IoT device to periodically operate in a power-saving mode (e.g., enter sleep mode while not monitoring or receiving any signals in an inactive or idle state).

[0034] For example, UE 10 can be configured for discontinuous reception (DRX), where UE 10 operates in an active state during periodic paging opportunities (POs) to monitor signaling from network node 12. In such an example, during the off-duty period, UE 10 can operate in a power-saving state (e.g., an inactive state) to reduce power consumption. Such an inactive state can include, for example, a Radio Resource Control (RRC) idle state (denoted as RRC_IDLE) or an RRC inactive state (denoted as RRC_INACTIVE). In some examples of DRX, UE 10 can monitor one PO per DRX cycle. As described herein, a PO is a set of PDCCH monitoring opportunities (MOs) that can include one or more time slots (e.g., subframes or OFDM symbols) in which paging signals (e.g., paging DCIs) can be sent to UE 10 (e.g., directly from network node 12 or indirectly via another node, such as another UE). A paging frame (PF) can be an example of a radio frame and can include one or more POs, or the start of a PO. To further reduce power consumption, UE 10 may have extended DRX (eDRX), for example, for one or more connection management (CM) modes, such as CM idle mode (denoted as CM-IDLE) and / or CM connected mode with RRC-INACTIVE (denoted as CM-CONNECTED).

[0035] In other words, a DRX cycle can include one or more on durations and one or more off durations. During the off duration, the device can operate in an inactive state, and during the on duration, the device can operate in an active state, allowing the device to monitor paging signals from the network (e.g., the device's circuitry is configured to receive signaling from the network). Paging signals can indicate that the network has downlink data for the device. Accordingly, in response to receiving a paging signal, the device can determine to operate in an active state (e.g., continue operating in an active state, avoiding transitioning to an inactive state). Alternatively, if the network lacks data for the device, the device can determine to operate in an inactive state (e.g., it can enter sleep mode). In some examples, the device can operate in an inactive state for the duration of an inactive timer. That is, the device can determine when to transition to an active state (e.g., to monitor paging signals) based on the inactive timer. However, in some examples, network node 12 may lack downlink data for UE 10 for multiple DRX cycles. In such an example, the monitoring performed by UE 10 during the on-duration of the DRX cycle may be unnecessary (e.g., it may cause UE 10 to operate in an active state and consume power unnecessarily). Therefore, for such an example, UE 10 monitoring PO may be inefficient (e.g., in terms of power saving).

[0036] For example, an LPWA IoT device may include a soil moisture sensor deployed in remote farmland. The LPWA IoT device can perform soil measurements periodically, such as one or more soil moisture measurements per day. However, unexpected droughts may occur, requiring farmland irrigation systems to provide more water to prevent crop stress. In such an example, a downlink command may be sent from a server (e.g., network node 12) to the soil moisture sensor (e.g., UE 10) to adjust the period (e.g., reduce the interval between measurements). Therefore, signaling for downlink data to the sensor may occur infrequently relative to the duration of the DRX period (e.g., an example of infrequent downlink updates). That is, the frequency with which network node 12 signals downlink data to UE 10 may be lower than the frequency with which UE 10 monitors the PO, potentially leading to increased power consumption at UE 10.

[0037] Alternatively or concurrently, the LPWA IoT device can be configured to receive a WUS (Wake-up Signal), which can provide power saving at the LPWA IoT device, for example, by enabling the LPWA IoT device to operate in a power-saving state (e.g., remain asleep, do not wake up) for one or more DRX-enabled durations during which no downlink data is available to the LPWA (e.g., when the gNB signals 'do not wake up' to the LPWA IoT device). In such an example, the network node (e.g., the gNB) can notify the LPWA IoT device when downlink data is available (e.g., it can signal 'wake up' to the UE), allowing the LPWA IoT device to wake up (e.g., transition to an active state) during future DRX-enabled durations, monitor the paging channel, and / or receive downlink data. In some examples, the WUS can be cell- or group-specific. In such an example, the WUS can wake up one or more UEs that do not have incoming data. Such a UE can wake up to monitor the paging channel and then transition back to sleep after monitoring. WUS can instruct the gNB (e.g., network node 12) to send data to the LPWA IoT device (e.g., UE 10) during a future (e.g., the next) DRX-on duration. In such an example, the LPWA IoT device monitors WUS according to a wake-up cycle (e.g., to receive alarm messages from the gNB). For example, the device may include a receiver that consumes relatively low power and monitors WUS from the network during the on duration of the wake-up cycle, and determines whether to wake up during the on duration of the DRX cycle based on the received WUS. Thus, in such an example, the LPWA IoT monitors WUS (e.g., to indicate 'wake up' or 'don't wake up') regardless of whether data is available to the LPWA IoT device. In some examples, the network node 12 may signal downlink data to the UE 10 less frequently than the UE 10 monitors WUS, which may result in 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 unnecessarily monitor WUS and therefore may unnecessarily operate in an active state (and consume power).

[0038] In other words, WUS can reduce power consumption at UE 10 relative to DRX paging indication by triggering UE 10 wake-up when downlink data (paging) is available to devices in the device group (e.g., the device group to which WUS is sent). However, the power consumption of periodic monitoring of WUS (e.g., which may be power-intensive for LPWA IoT devices themselves), and the power saving achieved by WUS may be relatively low (e.g., insufficient for LPWA IoT devices, and may not provide a sufficiently long lifespan) in scenarios where downlink data reception is sporadic (e.g., with relatively long inter-packet intervals).

[0039] In some examples, LPWA IoT devices can support operation in a Mobile-Initiated Connection (MICO) mode. For instance, some wireless networks (e.g., in 5G) can support MICO mode, which can help LPWA IoT devices conserve power. In MICO mode, a device can suppress listening for paging (and therefore may not be paged) to save battery power. For example, the Access and Mobility Management Function (AMF) can instruct the device to operate in MICO mode and can consider the device unreachable when it is idle (e.g., when the device's CM state in the AMF is CM-IDLE). Therefore, the AMF can reject (e.g., from application functions) one or more requests for downlink data delivery to a device in MICO mode (and whose CM state in the AMF is CM-IDLE with an appropriate reason). In other words, while the device is in CM-CONNECTED, a device in MICO mode can be reachable (e.g., reachable only) for mobile termination data or signaling. Therefore, a device in MICO mode can suppress paging snooping while in CM-IDLE and can halt 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. Triggers can include: device changes (e.g., changes in device configuration requiring updates to device registration with the network), the expiration of a periodic registration timer, pending data, or pending signaling (e.g., a session management procedure being initiated). However, while mobile-initiated data applies to both CM-CONNECTED and CM-IDLE states, mobile-termination data is supported (e.g., only supported) when the device is in CM-CONNECTED state. That is, MICO mode may not support mechanisms for UE 10 to reduce power consumption associated with receiving downlink data (e.g., mobile-termination data). In other words, MICO mode may not enable UE 10 to receive paging signals while conserving power.

[0040] In other words, LPWA IoT UEs have relatively low energy availability and are designed (e.g., expected) to operate for several years. For example, the expected battery life of an LPWA IoT UE could be 10-15 years. Additionally, such UEs can receive or transmit data sporadically (e.g., with large inter-packet intervals). Furthermore, unlike some communication scenarios such as voice calls, LPWA IoT use cases can be latency-tolerant (e.g., can be delayed by seconds to hours). Therefore, due to the low energy availability constraint of LPWA IoT UEs, such UEs can implement techniques to reduce (e.g., minimize) energy consumption at the UE. However, some of these techniques may require the UE to frequently monitor (or listen for) signaling from the network (e.g., wake-up indications, paging information), which consumes power and increases the energy cost for the UE (e.g., energy-constrained UEs).

[0041] In some examples, one or more techniques for UE-triggered downlink alarm information, as described herein, can provide UE 10 with a framework (e.g., autonomy) to select one or more downlink MOs to enable UE 10 to conserve energy (e.g., power saving). UE 10 can be used (e.g., and expects) to monitor and receive downlink alarm information (e.g., wake-up indications, paging information) from the network (e.g., directly from network node 12 or indirectly via another node such as another UE) in one or more downlink MOs. For example, according to one or more techniques for UE-triggered downlink alarm information, as described herein, UE 10 can send a request for downlink alarm information to network node 12. In this request, UE 10 can indicate one or more MOs that UE 10 can be used to receive downlink alarm information during one or more MOs. In other words, UE 10 indicates to network node 12 one or more times that UE 10 is reachable during one or more times (e.g., when UE 10 is reachable during its RRC IDLE / INACTIVE state).

[0042] One or more aspects of this disclosure provide a framework for configuring UE 10 to determine (e.g., autonomously determine) one or more MOs, in which UE 10 can be used to receive downlink alarm information from network node 12. In some examples, one or more MOs may be selected at UE 10 from a set of candidate MOs configured by the network. As described herein, an MO refers to one or more time-domain and / or frequency-domain resources through which UE 10 can monitor downlink alarm 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 can monitor downlink alarm information from the network. In some examples, an MO may be a WUS timing (e.g., a group WUS MO). Additionally or alternatively, an MO may be a PO. As described herein, downlink alarm information refers to information associated with downlink data for the UE. For example, downlink alarm information may include a downlink alarm message indicating whether downlink data is available to UE 10. In some other examples, downlink alarm information may include scheduling information, such as indications of one or more resources for receiving downlink alarm messages, and / or system information (e.g., information available at UE 10 to establish a connection with the network so that UE 10 can receive downlink data). In some examples, downlink alarm information may be a wake-up indication. Additionally or alternatively, in some examples, downlink alarm information may be a paging indication. In some examples, the determination of one or more MOs may be based on downlink characteristics (e.g., downlink data characteristics or downlink alarm information characteristics) indicated to UE 10 by the network. Additionally or alternatively, one or more MOs may be autonomously determined at UE 10 based on (at least) energy availability at UE (e.g., expected energy availability at UE) or the time criticality of operations at UE (such as IoT or non-IoT operations of UE 10). As described herein, energy availability at UE (e.g., energy availability) refers to the amount of energy available at UE for consumption by UE to, for example, perform one or more operations. As described herein, the time criticality of an operation refers to the priority associated with the execution of that operation during a time period. In other words, time-criticality indicates the time sensitivity (e.g., time criticality) associated with the execution of an operation.

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

[0044] In response to an indication from the MO to the network (e.g., via a downlink alarm information request), UE 10 can monitor downlink alarm information from the network in the indicated MO (and receive downlink alarm information (if sent by the network)). In some examples, the downlink alarm information can be sent via the Physical Downlink Control Channel (PDCCH). In some such examples, the downlink alarm information may include a wake-up indication (e.g., downlink control information (DCI), such as DCI format 2_6 for a connected UE or DCI format 2_7 for an idle UE). In some other examples, the downlink alarm information can be sent via the Physical Downlink Shared Channel (PDSCH). In some such examples, the downlink alarm information may include paging information (e.g., a paging control channel (PCCH) message). In some other examples, the downlink alarm information can be sent via a wake-up signal (WUS). Alternatively or additionally, the downlink alarm information can be sent via a sidelink channel. For example, UE 10 can receive downlink alarm information from the network via UE 11 (e.g., via a sidelink). In other words, network node 12 can send downlink alarm information to UE 11 via the downlink, and UE 11 can send (e.g., relay, forward) downlink alarm information to UE 10 via the side link. UE 10 can determine (e.g., select) whether to operate in an active or inactive state based on the downlink alarm information.

[0045] Additionally, according to one or more aspects of this disclosure, network node 12 may receive a downlink alarm information request from UE 10, the downlink alarm information request including information about MOs (e.g., indicating one or more MOs selected by the UE). In one or more embodiments, network node 12 may confirm or reject the MOs selected by the UE. In some such embodiments, network node 12 may recommend one or more different MOs and / or different MO periods (e.g., different configurations for MOs may be recommended). In some examples, network node 12 may instruct network node 12 to cache downlink data (e.g., information) for UE 10 for a threshold amount of time (e.g., a maximum time). In such examples, UE 10 may select one or more MOs that satisfy the threshold amount of time (e.g., within an interval following the maximum time). The threshold amount of time may be based on memory constraints at network node 12, downlink traffic, or quality of service (QoS) constraints, and other examples of parameters that may affect the threshold amount of time that network node 12 caches for data used by the UE. According to one or more embodiments of this disclosure, network node 12 may cache (or otherwise store) downlink data intended for transmission to UE 10 (e.g., data for which network node 12 may send downlink alarm information). In some examples, network node 12 may cache downlink data for a duration between the receipt of a downlink alarm information request and the indicated one or more MOs (e.g., in response to a downlink alarm information request and up to the indicated MO(s)). In some other examples, network node 12 may cache downlink data prior to the receipt of a downlink alarm information request (e.g., until the receipt of a downlink alarm information request). In some examples, in response to a downlink alarm information request, network node 12 may send downlink alarm information to UE 10 on the indicated MO(s).

[0046] One or more techniques, as described herein, for triggering downlink alarm information by the UE, can thus provide a framework for the UE 10 to request downlink alarm information from the network node 12. In some examples, such techniques can improve the efficiency of communications performed by the UE 10 (e.g., IoT-type data transmissions), which can provide reduced power consumption at the UE 10 and Figure 1 Increased sustainability of communication within the communication system.

[0047] Figure 1The communication system can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize services provided by them. The communication system can 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 communication system can support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Depicted in the "cloud" 18). Communication systems may include a central control entity, etc., to provide facilities for different operators' networks to collaborate, for example, in spectrum sharing.

[0048] In some examples of communication systems, such as those exemplified by 5G networks, satellite communications can be used to enhance or supplement 5G service coverage, for example, by providing backhaul. While various aspects of this disclosure are described in the context of 5G, it should be understood that these aspects are also applicable to other systems, such as subsequent generations of communication networks (e.g., improved 5G and 6G). Some possible use cases for satellite communications include providing service continuity for machine-to-machine (M2M) or IoT devices or for passengers in vehicles, or ensuring the service availability of critical communications, and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems, but can also utilize low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite in a mega-constellation can cover a network entity of several enabling satellites that create a ground cell. Ground cells can be created by ground relay nodes or by gNBs located on the ground or in satellites.

[0049] Figure 1 The communication system described is an example of a wireless access system. Figure 1 The communication system can be deployed in this wireless access system, and in practice, the system may include multiple NodeBs, user equipment can access multiple wireless cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the NodeBs can be a home NodeB. Furthermore, multiple different types of wireless cells and multiple wireless cells can be provided in the geographical area of ​​the wireless communication system. Wireless cells can be macrocells (or umbrella cells), macrocells are large cells, typically with a diameter of tens of kilometers, or smaller cells, such as microcells, femtocells, or picocells. Figure 1 A NodeB can provide any type of cell. Cellular wireless systems can be implemented as multi-layer networks comprising several types of cells. Typically, in a multi-layer network, one access node provides one or more cells, and therefore multiple NodeBs can be used to provide such a network structure.

[0050] like Figure 1 As shown, for example, a communication system may include multiple devices configured to communicate via appropriate channels. In this regard, a UE may include a transmitter configured to communicate with a receiver, such as a base station. Conversely, a base station may include a receiver and a transmitter communicating with a receiver, such as a UE. As an example, the communication system may be deployed within radio access architectures based on Advanced Long Term Evolution (LTE-A), New Radio (NR, 5G), Advanced 5G or 6G, and other subsequent generations. However, the system may be deployed in other applications, including within other communication networks such as Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), Wireless Local Area Network (WLAN or WiFi), Global Microwave Access Interoperability (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof. In this regard, Figure 1 An example of a simplified system architecture is depicted, showing some components and functional entities (e.g., logical units) whose implementations may differ from those shown. Figure 1 The connections shown are logical connections, and their corresponding physical connections may differ. Those skilled in the art will understand that the system may include, in addition to... Figure 1 Other functions and structures besides those shown. Figure 1 In the wireless access architecture, UE 10 can be configured to wirelessly connect to a network node 12 (such as a NodeB) providing the cell on one or more communication channels within the cell. UE 10 and network node 12 can communicate via an access link (e.g., a Uu link). Therefore, network node 12 may also be referred to herein as an access node. The physical link from user equipment (e.g., UE 10) to NodeB (e.g., network node 12) is referred to as an uplink or reverse link, while the physical link from NodeB to user equipment is referred to as a downlink or forward link. It should be understood that a NodeB or its functionality can be implemented using any entity suitable for this purpose, such as a node, host, server, or access point (AP).

[0051] Such as Figure 1Communication systems, such as communication systems, may include more than one NodeB. In this case, the NodeBs may also be configured to communicate with each other via wired or wireless links designed for various purposes. For example, such links may be used for signaling purposes. A NodeB is a computing device configured to control the wireless resources of the communication system to which the NodeB may be coupled. A NodeB may also be referred to as a base station, access point, or any other type of interface device, including relay stations capable of operating in wired or wireless environments. A NodeB includes or is coupled to a transceiver. From the transceiver of the NodeB, a connection is provided to an antenna element that establishes a bidirectional wireless link to the user equipment. Thus, according to an example embodiment, the transceiver of the NodeB and the transceiver of the user equipment may include transmitters and receivers configured to communicate via a channel, wherein trainable parameters of the transmitters and receivers can be reconfigured. The antenna element may include multiple antennas or antenna elements. The NodeB is also 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, which is used to route and forward user data packets), a Packet Data Network Gateway (P-GW) for providing connectivity between the User Equipment (UE) and an external packet data network, or a Mobility Management Entity (MME), etc. A User Equipment (also known as a UE, User Terminal, Terminal Equipment, etc.) is a type of device to which resources on the air interface are allocated and assigned, and therefore any features described herein with respect to a User Equipment can be implemented using a corresponding device, such as a relay node. An example of such a relay node is a Layer 3 relay (self-backhaul relay) directed towards a base station.

[0052] User equipment can refer to portable computing devices, including wireless mobile communication devices operating with or without a subscriber identification module (SIM), including but not limited to the following types of devices: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), handheld devices, devices using wireless modems (alarm or measuring devices, etc.), laptops and / or touchscreen computers, tablets, game consoles, laptops, and multimedia devices. It should be understood that user equipment can also be a nearly exclusive uplink device (e.g., an uplink-only device), an example of which is a camera or camcorder used to load images or video clips onto a network. User equipment can also be a device capable of operating in an IoT network, a scenario in which objects are provided with the ability to transmit data over a network without human-to-human or human-to-computer interaction. In other words, UE 10 can be an example of an IoT device configured to operate in one or more IoT networks. User equipment (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more UE functions. User equipment can also be referred to as a subscriber unit, mobile station, remote terminal, access terminal, user terminal, or UE, and other names for means configured to support user equipment operation.

[0053] The various techniques described in this paper can also be applied to cyber-physical systems (CPS) (systems for controlling collaborative computing elements of physical entities). CPS enables the implementation and utilization of an increasing number of interconnected IoT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems are a subclass of cyber-physical systems where the physical systems under discussion possess inherent mobility. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0054] Although these devices have been depicted as a single entity, different units, processors, and / or memory units can be implemented. Figure 1(Not all are shown). Furthermore, the number of receive and / or transmit antennas for user equipment can vary naturally depending on the current implementation. In some examples, the communication system may enable the use of multiple-input multiple-output (MIMO) antennas and may include far more base stations or nodes than other types of communication systems (e.g., so-called small-cell concept systems, such as those associated with LTE), including macro sites cooperating with smaller stations, and employing various wireless technologies depending on service requirements, use cases, and / or available spectrum. In some examples, the communication system may include a 5G network. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control. 5G may include multiple radio interfaces, namely sub-6GHz, cmWave, and mmWave, and may also be integrated with existing legacy radio access technologies such as LTE. Integration with LTE can be implemented as a system, at least in the early stages, where macro coverage is provided by LTE, and 5G radio interface access is obtained from smaller cells via aggregation to LTE. In other words, 5G can support both RAT interoperability (such as LTE-5G) and RI interoperability (radio interface interoperability, such as sub-6GHz-cmWave and sub-6GHz-cmWave-mmWave). One concept to consider for use in 5G networks is network slicing, where multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0055] Some network architectures (such as some in LTE networks) can be fully distributed in the wireless and fully centralized in the core network. Low-latency applications and services in 5G require content to be closer to the wireless, leading to local offloading and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. It can also store and process content near cellular subscribers to accelerate response times. Edge computing encompasses a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing, and can also be categorized as local cloud / fog computing and grid / mesh computing, dewdrop computing, mobile edge computing, small clouds, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented reality and virtual reality, data caching, the 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 can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize services provided by them. The communication network can also support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Depicted by “Cloud” 18). The communication system may also include a central control entity, etc., to provide facilities for different operators’ networks to cooperate, for example, in spectrum sharing.

[0057] By leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN), edge cloud can be introduced into the Radio Access Network (RAN). Using edge cloud allows access node operations to be performed at least partially in servers, hosts, or nodes operatively coupled to remote radio heads or base stations including radio components. Node operations can also be distributed across multiple servers, nodes, or hosts. The application of the cloudRAN architecture enables real-time RAN functions to be performed on the RAN side (in the distributed unit DU 12), while non-real-time functions are performed centrally (in the centralized unit CU 14).

[0058] It should also be understood that the functional division between core network operations and base station operations can vary based on implementation or may not even exist. Some other technological advancements that can be utilized include big data and all-IP, which could potentially transform how networks are built and managed. 5G (or New Radio) networks can support multiple tiers, where MEC servers can be placed between the core and base stations or NodeBs (gNBs). It should be understood that MEC can also be applied to other types of networks.

[0059] To meet the need for improved deployment and performance of communication systems, the concept of "plug-and-play" NodeBs was introduced. Typically, networks capable of using "plug-and-play" NodeBs include, in addition to the Home NodeB (HNodeB), the Home NodeB Gateway or HNB-GW (Host NodeB Gateway). Figure 1 (Not shown in the image). HNB gateways (HNB-GWs), typically installed within a carrier's network, can aggregate traffic from a large number of HNBs back to the core network.

[0060] Figure 2 An example of device 20 is depicted in the image. Figure 2As shown, the device includes a processing circuitry system 22, a memory 24, and a communication interface 26, associated with or communicating with thereto. The processing circuitry system 22 may communicate with the memory 24 (e.g., a memory device) via a bus for transferring information between components of the device. 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) including gates configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device, such as the processing circuitry system 22). The memory device 24 may be configured to store information, data, content, applications, instructions, etc., for enabling the device 20 to perform various functions according to exemplary embodiments of this disclosure. For example, the memory device 24 may be configured to cache input data for processing by the processing circuitry system. Additionally or alternatively, the memory device 24 may be configured to store instructions for execution by the processing circuitry system. In some embodiments, the device 20 may be embodied in various computing devices as described above. However, in some embodiments, the device 20 may be embodied as a chip or chipset. In other words, device 20 may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on structural components (e.g., substrates). Structural components can provide physical strength, size savings, and / or electrical interaction constraints for the component circuitry included thereon. Therefore, in some cases, device 20 may be configured to implement embodiments of this disclosure on a single chip or as a single "system-on-a-chip." Thus, in some cases, a chip or chipset may constitute a unit for performing one or more operations to provide the functions described herein.

[0061] The processing circuitry system 22 can be embodied in a variety of different ways. For example, the processing circuitry system 22 can be embodied as one or more of various hardware processing components, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other circuitry systems including integrated circuits, such as, for example, ASIC (Application-Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), microcontroller unit (MCU), hardware accelerator, application-specific computer chip, etc. Therefore, in some embodiments, the processing circuitry system 22 may include one or more processing cores configured to execute independently. A multi-core processing circuitry system can implement multiple processing within a single physical package. Additionally or alternatively, the processing circuitry system 22 may include one or more processors configured in series via a bus to enable independent execution, pipelined, and / or multithreading of instructions. In an example embodiment, the processing circuitry system 22 may be configured to execute instructions stored in memory device 24 or otherwise accessible by the processing circuitry system. Alternatively or additionally, the processing circuitry system 22 may be configured to perform hard-coded functions. Therefore, whether configured via hardware or software methods or a combination thereof, the processing circuitry 22 can represent an entity (e.g., physically embodied in a circuitry) capable of performing operations according to embodiments of the present disclosure when configured accordingly. Thus, for example, when the processing circuitry 22 is embodied as an ASIC, FPGA, etc., it can be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processing circuitry 22 is embodied as an executor of instructions, the instructions can 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 can be a processor of a particular device (e.g., an image or video processing system) configured to employ embodiments of the present disclosure by further configuring the processing circuitry 22 with instructions for performing the algorithms and / or operations described herein. The processing circuitry 22 may include a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processing circuitry 22.

[0062] Communication interface 26 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, configured to receive and / or transmit data including media content in the form of video or image files, one or more audio tracks, etc. In this regard, communication interface 26 may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, communication interface 26 may include circuitry for interacting with the antenna(s) to enable signal transmission via the antenna(s) or processing of signals received via the antenna(s). In some environments, communication interface 26 may alternatively or additionally support wired communication. Thus, for example, 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. Device 20 may be (or included therein) one or more types of devices, such as access nodes (e.g., base stations), UEs, and / or IoT devices.

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

[0064] In at least one example embodiment, device 20 may be an LPWA IoT device with relatively low power availability. Additionally, device 20 may be used for many years (e.g., it may be expected to last for ten years or more). In some examples, device 20 may receive or transmit data sporadically and at relatively large inter-packet intervals (e.g., hours). Therefore, device 20 may be configured to support one or more techniques, as described herein, for UE-triggered downlink alarm information, enabling the LPWA IoT device to conserve energy (e.g., and thus extend the lifespan of device 20). For example, for LPWA IoT use cases where downlink data may be transmitted infrequently, non-periodically, and / or with relatively large gaps between two downlink data transmissions, device 20 may implement one or more techniques, as described herein, for UE-triggered downlink alarm information to conserve power at device 20 (e.g., LPWA IoT UE), when processing downlink alarm information. In some examples, by implementing such techniques, device 20 may avoid frequent listening for downlink alarm information, such as wake-up indications or paging information, for example, during RRC IDLE and / or RRC INACTIVE states.

[0065] For example, based on one or more techniques for UE-triggered downlink alarm information as described herein, device 20 can autonomously determine one or more suitable MOs (for UE power-saving constraints) for receiving downlink alarm information. In other words, device 20 autonomously determines the duration for which it is inactive for power-saving purposes (e.g., in RRC IDLE and / or RRC INACTIVE states) and can select the active duration (e.g., one or more MOs) for receiving downlink alarm messages (e.g., based on the determined inactive duration). In other words, device 20 can select (e.g., based on its convenience, expected power consumption rate) the duration for which it becomes active to monitor (e.g., and receive) downlink messages (such as downlink alarm messages from the network). Therefore, device 20 sends a request for downlink alarm information, wherein the request informs the network node of the determined MOs, enabling the network to send downlink alarm information (e.g., potential downlink alarm information) in the indicated MOs. In other words, device 20 queries (or requests) the network for any downlink information (e.g., downlink alarm information) intended for device 20. Network nodes can send downlink alert information in the indicated MO in response to an MO instruction (e.g., a downlink alert information request).

[0066] Downlink alert information may include information (e.g., any information) sent from the network to the UE indicating the availability of downlink data for the UE. Alternatively or additionally, downlink alert information may include scheduling information or system information. Upon receiving downlink alert information, the UE may prepare (e.g., anticipate preparing) one or more receivers at the UE to receive available downlink data. Additionally, as described herein, inactive state refers to a power-saving mode at the UE, in which the UE does not monitor downlink signals. In some examples, power-saving mode may include an RRC IDLE state or an RRCINACTIVE state.

[0067] In some embodiments, UE 10 may send a request for downlink alarm information according to one or more schemes for transmitting downlink alarm information. In some such embodiments, the scheme for transmitting downlink alarm information may be associated with the timing of network node 12 caching downlink data for UE 10 and / or the timing of UE 10 sending a request for downlink alarm information. Figure 3 The diagram illustrates at least one example embodiment of a scheme for transmitting downlink alarm information, and Figure 4 The diagram illustrates at least one example embodiment of a scheme for transmitting downlink alarm information. For example, the scheme may include... Figure 3 One or more operations shown and / or Figure 4 One or more operations are shown. UE 10 can select a scheme based on an instruction from network node 12. For example, network node 12 can indicate a scheme for transmitting downlink information to UE 10. That is, the scheme selection can be performed by the gNB and indicated to the UE. Alternatively, network node 12 can indicate to UE 10 a triggering criterion for scheme selection. In such an example, UE 10 can select a scheme based on the triggering criterion being met. In some examples, UE 10 can indicate the selected scheme to network node 12.

[0068] Figure 3 This is a processing flow, illustrating the steps performed according to an example embodiment to provide downlink alarm information triggered by a UE, such as in... Figure 1 The flowchart illustrates the operations performed within the communication system. It shows some of the corresponding operations performed at UE 10 and Node 13. UE 10 can be... Figure 1 Illustration and reference Figure 1 An example of UE 10 is described. Additionally, node 13 can be... Figure 1 Illustration and reference Figure 1An example of network node 12 or UE 11 is described. One or more operations performed at UE 10 and / or one or more operations performed at node 13 may be performed in a different order than the example shown. Alternatively or alternatively, one or more operations performed at UE 10 and / or one or more operations performed at node 13 may be omitted. Alternatively or alternatively, one or more other operations may be added. Figure 3 In the example, UE 10 may be an LPWA IoT device (e.g., a sensor or smart metering device in a large agricultural area), where downlink data from node 13 (e.g., network node 12) may be sent to UE 10 relatively infrequently, non-periodically, and / or with relatively large gaps between two downlink data transmissions.

[0069] like Figure 3 As shown, UE 10 can indicate one or more MOs to Node 13 (e.g., gNB) by sending a request for downlink alarm information. After sending the request, UE 10 can transition to an inactive state. During the indicated MO(s) (e.g., only during the indicated MO(s)), UE 10 can transition to an active state (e.g., it can become active, such as based on the DRX on duration or another type of duration similar to WUS MO) to monitor downlink alarm information (e.g., any potential downlink alarm information). The network (e.g., gNB) can cache (e.g., expect to cache or otherwise store) downlink information, such as downlink alarm information and / or associated downlink data, during the inactive period of UE 10, and send the downlink information to UE 10 in the indicated MO(s).

[0070] At step 32, UE 10 (e.g., an LPWA UE) may determine one or more MOs in which UE 10 can be used to receive downlink alarm information (e.g., where UE 10 expects to receive any downlink alarm information). For example, the MO(s) may correspond to suitable resources for monitoring downlink alarm information in an active state, and outside the MO(s), UE 10 may operate in an inactive state to conserve power (e.g., if no downlink alarm information is received in the MO(s), if the downlink alarm 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 indicated by the network (e.g., downlink data characteristics or downlink alarm information characteristics). Additionally or alternatively, UE 10 may autonomously determine the MO(s) based at least on energy availability at UE 10, energy consumption rate at UE 10, and / or the time criticality of one or more operations at UE 10 (e.g., IoT operation, non-IoT operation, application-related operation). For example, UE 10 may select multiple MOs with relatively large inter-MO time intervals based on one or more characteristics of the expected downlink data (e.g., if the expected downlink data has a relatively large average arrival time between downlink alarm messages, if the expected downlink data is latency tolerant, if the expected downlink data has a relatively low priority) and / or the energy availability of UE 10 (e.g., if the energy availability is relatively low).

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

[0072] Alternatively or concurrently, the control information may include second control information indicating a set of candidate MOs for receiving downlink alarm information. For example, the determination of the MO(s) at step 32 may be based on one or more subsets of the MOs indicated to UE 10 by the network (e.g., a preferred subset of the MO(s)). In other words, UE 10 may select the MO(s) from one or more candidate sets (e.g., subsets) of the MO(s) indicated to UE 10 by the network (e.g., directly from network node 12 or via UE 11). For example, in some IoT deployments, multiple groups of UEs may monitor the same time. In some examples, such as for a relatively large group of UEs, the transmission of downlink alarm information in the MO may result in false wake-ups for a relatively large number of UEs (e.g., within the group). That is, the downlink alarm information may be applicable (e.g., intended for) a portion of the UEs in the group, but because the group of UEs monitors the same time, the downlink alarm information may be sent to (and thus wake up) the group of UEs (e.g., not just the portion of the UEs to which the downlink alarm information is intended). Therefore, the network can provide one or more subsets of MOs to the UE and one or more other UEs with similar downlink traffic arrival times, from which the UE can select MOs. In such an example, UEs with similar downlink traffic arrival times can select one or more of the same MOs, and UEs with different downlink arrival times can select one or more different MOs (e.g., so that they do not wake up unnecessarily). Additionally or alternatively, the control information may include third control information indicating a scheme for transmitting downlink alarm information. For example, the third control information (or downlink alarm information characteristics) may instruct UE 10 on a scheme for obtaining downlink alarm information from network node 12.

[0073] At step 34, UE 10 may send a request for downlink alarm information to the network. UE 10 may send this request during a first-time opportunity. The request for downlink alarm information may indicate the availability of receiving downlink alarm information in the MO(s)(s) determined at step 32. In other words, UE 10 may send a request for downlink alarm information indicating the MO(s)(s) determined at step 32. In some examples, this request may be accompanied by an acknowledgment or rejection message from the network.

[0074] For example, in response to the request, UE 10 can receive a message from the network (e.g., directly via network node 12 or indirectly via UE 11). The message may indicate one or more resources for receiving downlink alarm information. A second timing may be based on 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 frequency-domain resources), and the second timing may correspond to one or more time-domain resources. In some examples, the message may indicate acknowledgment at UE 10 of receiving downlink alarm information from (multiple) MOs. In such examples, the acknowledgment indicates that one or more resources overlap with at least a portion of the MOs indicated via the request. In some other examples, the message may include an indication of one or more resources. In such examples, one or more resources may overlap with at least one MO different from the MOs indicated via the request. In other words, the network may reject the MOs indicated via the request and therefore may send a rejection message to UE 10. The rejection message may configure one or more different MOs for UE 10 (e.g., one or more resources overlapping with at least one MO different from the MOs indicated via the request).

[0075] In some examples, at step 35, node 13 (e.g., gNB) caches or otherwise stores downlink information intended for UE 10 (e.g., downlink data, downlink alarm information). That is, in the example where node 13 is network entity 12, node 13 can cache downlink information for UE 10. In some examples, network node 12 can cache downlink information in response to the request until (e.g., until) the indicated MO(s). In other words, node 13 can cache downlink information intended for UE 10 when UE 10 is operating in an inactive state.

[0076] In some examples, at step 36, node 13 (e.g., gNB, UE) may send downlink alarm information to UE 10 in response to the request. Node 13 may send the downlink information during a second timing period based on one or more monitoring timings. For example, the second timing period may overlap with at least a portion of one or more MOs (e.g., it may coincide with at least a portion of one or more MOs, and may correspond to one or more time-domain resources overlapping with at least a portion of one or more MOs). That is, in some examples, the gNB sends downlink alarm information on the indicated MO(s). In some other examples, the second timing period may overlap with at least a portion of a MO that is different from the one or more MOs indicated via the request. For example, network node 12 may reject the indicated MO(s) and configure another MO for UE 10 that is different from the indicated MO(s) (e.g., does not overlap with the time and / or frequency domains).

[0077] In some examples, downlink alarm information may indicate the status associated with downlink data cached between a first time point and a second time point. For example, the network may send downlink alarm messages during MO in one or more pre-configured time and / or frequency resources. In some such examples, downlink alarm information may indicate the availability of downlink data for UE 10. Alternatively, downlink alarm information may indicate the lack (or unavailability) of downlink data for UE 10. In some other examples, downlink alarm information may include control information (e.g., scheduling information or system information). For example, downlink alarm information may include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such examples, downlink alarm messages (e.g., indicating the status of downlink data) may be sent from the network via a data channel in (multiple) indicating resources. Additionally or alternatively, downlink alarm information may include system information that UE 10 can obtain, such as information used to establish a connection with the network. In some examples, downlink alarm information may include downlink data.

[0078] In some examples, such as where node 13 is network node 12, node 13 may transmit downlink alarm information on the PDCCH or PDSCH, where the PDCCH includes, for example, a wake-up indication (e.g., DCI 2_6), and the PDSCH includes, for example, paging information (e.g., PCCH). In some other examples, such as where node 13 is UE 11, node 13 may transmit downlink alarm information on a sideline channel (e.g., the Physical Sideline Shared Channel (PSSCH) or the Physical Sideline Control Channel (PSCCH)). In some examples, the downlink alarm information may enable UE 10 to prepare for operation in an active state, for example, and to follow one or more protocols to establish a connection with network node 12 (e.g., to receive downlink data buffered at network node 12).

[0079] In some examples, at step 38, UE 10 may determine (e.g., optionally) whether to operate in an active or inactive state based on downlink alarm information. For example, UE 10 may determine to operate in an active state based on a status indication of the availability of downlink data for UE 10. Alternatively, UE 10 may determine to operate in an inactive state based on a status indication of the lack of downlink data for UE 10.

[0080] In some examples, UE 10 may update the period and configuration associated with the MO based on received downlink alarm information (or received downlink data information). In some such examples, the network may implicitly know of the update. Alternatively or additionally, UE 10 may send an indication of the updated period (or one or more second MOs selected based on the period) to the network. As an illustrative example, UE 10, which initially selects (e.g., at step 32) one or more MOs with a first period (e.g., X seconds), may select one or more second MOs with a second period. The second period may be longer than the first period (e.g., UE 10 may increase the period to 2X seconds or some other suitable multiple of X seconds), for example, if no downlink data is available for UE 10 (e.g., during 5 consecutive MOs or during some other suitable number of consecutive MOs).

[0081] Figure 4 This is a processing flow, illustrating the steps performed according to an example embodiment to provide downlink alarm information triggered by a UE, such as in... Figure 1 The flowchart illustrates the operations performed within the communication system. It shows some of the corresponding operations performed at UE 10 and Node 13. UE 10 can be... Figure 1 Illustration and reference Figure 1 An example of UE 10 is described. Additionally, node 13 can be... Figure 3 Illustration and reference Figure 3 An example of the described node 13. For example, network node 13 could be... Figure 1 Illustration and reference Figure 1 An example of network node 12 or UE 11 is described. One or more operations performed at UE 10 and / or one or more operations performed at node 13 may be performed in a different order than the example shown. Alternatively or alternatively, one or more operations performed at UE 10 and / or one or more operations performed at node 13 may be omitted. Alternatively or alternatively, one or more other operations may be added. Figure 4 In the example, UE 10 may be an LPWA IoT device (e.g., a sensor or smart metering device in a large agricultural area), where downlink data from network node 12 may be sent to UE 10 relatively infrequently, non-periodically, and / or with relatively large gaps between two downlink data transmissions.

[0082] like Figure 4 As illustrated in the example, UE 10 can operate in an inactive state (e.g., remain in an inactive state) for an inactive period of time determined autonomously (e.g., based on a desired energy consumption rate). UE 10 can transition from an inactive state to an active state, and when active (e.g., for a relatively short duration, such as one or more milliseconds), UE 10 can send a request for downlink alarm information to the network (e.g., gNB). The network (e.g., gNB) can cache (e.g., expect to cache or otherwise store) downlink information, such as downlink alarm information and / or associated downlink data, until the network receives (e.g., explicitly receives) the request from UE 10.

[0083] At step 42, UE 10 (e.g., an LPWA UE) may determine one or more MOs in which UE 10 can be used to receive downlink alarm information (e.g., where UE 10 expects to receive any downlink alarm information). For example, the MO(s) may correspond to suitable resources for monitoring downlink alarm information in an active state, and outside the MO(s), UE 10 may operate in an inactive state to conserve power (e.g., if no downlink alarm information is received in the MO(s), or if the downlink alarm 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 indicated by the network (e.g., downlink data characteristics or downlink alarm information characteristics). Additionally or alternatively, UE 10 may autonomously determine the MO(s) based at least on energy availability at UE 10, energy consumption rate at UE 10, and / or the time criticality of one or more operations at UE 10 (e.g., IoT operation, non-IoT operation, application-related operation). For example, UE 10 may select multiple MOs with relatively large inter-MO time intervals based on one or more characteristics of the expected downlink data (e.g., if the expected downlink data has a relatively large average arrival time between downlink alarm messages, is latency tolerant, or has a relatively low priority) and / or the energy availability of UE 10 (e.g., if energy availability is relatively low).

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

[0085] Alternatively or concurrently, the control information may include second control information indicating a set of candidate MOs for receiving downlink alarm information. For example, the determination of the MO(s) at step 42 may be based on one or more subsets of the MOs indicated to UE 10 by the network (e.g., a preferred subset of the MO(s)). In other words, UE 10 may select the MO(s) from one or more candidate sets (e.g., subsets) of the MO(s) indicated to UE 10 by node 13. For example, in some IoT deployments, multiple groups of UEs may monitor the same time. In some examples, such as for a relatively large group of UEs, the transmission of downlink alarm information in the MOs may result in false wake-ups for a relatively large number of UEs. That is, the downlink alarm information may be applicable (e.g., intended for) a portion of the UEs in the group, but because the group of UEs monitors the same time, the downlink alarm information may be sent to (and thus wake up) that group of UEs (e.g., not just the portion of the UEs to which the downlink alarm information is intended). Therefore, the network can provide UE 10 and one or more other UEs with one or more subsets of MOs, from which the UE can select MOs, such that UEs with similar downlink service arrival times can select the same MOs, and UEs with different downlink arrival times can select different MOs (e.g., so they do not needlessly wake up). Additionally or alternatively, the control information may include third control information indicating a scheme for transmitting downlink alarm information. For example, the third control information (or downlink alarm information feature) may indicate to UE 10 a scheme for obtaining downlink alarm information from the network (e.g., directly via network node 12 or indirectly via UE 11). One or more schemes may be configured at UE 10 via control signaling (e.g., third control signaling). Additionally or alternatively, one or more schemes may be configured at UE 10 in other ways. In some such examples, the third control signaling may indicate a scheme configured at UE 10 (e.g., a scheme configured at UE 10 via other control signaling from the network or otherwise configured at UE 10). In other words, in some examples, the gNB can configure UE 10 to use a scheme by sending a configuration message that may include an explicit indication or triggering criterion for switching from another scheme (e.g., any other scheme used for downlink alarm information transmission) to this scheme. In some examples, the triggering criterion may include a threshold energy availability level. In such examples, UE 10 may switch from another scheme to this scheme based on the energy availability at UE 10 meeting (e.g., falling below) a threshold energy availability level.As an illustrative example, if the energy availability level at UE 10 drops below a threshold energy availability level, UE 10 may switch to (e.g., a scheme recommended by the gNB). In some examples, when UE 10 performs a switch between schemes (e.g., from scheme one to scheme two), UE 10 may indicate the scheme to the gNB. In other words, in response to a switch from scheme one to scheme two (e.g., based on the fulfillment of switch criteria), UE 10 may send an indication of scheme two to the network node.

[0086] In some examples, at step 44, node 13 (e.g., gNB) caches or otherwise stores downlink information (e.g., downlink data, downlink alert information) intended for UE 10. For example, the network may cache downlink information for UE 10 before receiving a request (e.g., until a request for downlink alert information with indications of MO(s) is received from UE 10). For example, the indicated MO(s) may follow (e.g., immediately) the request from the first time point when it is sent from UE 10, and therefore, node 13 may cache downlink data for UE 10 until the first time point (e.g., may stop caching downlink data for UE 10 in response to receiving the request). In other words, when UE 10 is operating in an inactive state, network node 12 may cache downlink information intended for UE 10.

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

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

[0089] In some examples, downlink alarm information may indicate the status associated with downlink data cached between a first time point and a second time point. For example, the network may send downlink alarm messages during MO in one or more pre-configured time and / or frequency resources. In some such examples, downlink alarm information may indicate the availability of downlink data for UE 10. Alternatively, downlink alarm information may indicate the lack (or unavailability) of downlink data for UE 10. In some other examples, downlink alarm information may include control information (e.g., scheduling information or system information). For example, downlink alarm information may include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such examples, downlink alarm messages (e.g., indicating the status of downlink data) may be sent from the network via a data channel in (multiple) indicating resources. Additionally or alternatively, downlink alarm information may include system information that UE 10 can obtain, such as information used to establish a connection with the network. In some examples, downlink alarm information may include downlink data.

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

[0091] Now for reference Figure 5 This describes some operations performed by device 20 (e.g., UE 10) in an example embodiment to provide UE-triggered downlink alarm information. For example... Figure 5 As shown, device 20 can request downlink alarm information from nodes (e.g., network node 12, UE 11).

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

[0093] like Figure 5 As shown in block 52, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing the transmission of a request for downlink alarm information from a node. Apparatus 20 can provide the transmission of the request such that the transmission occurs during a first timing event (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 indication of one or more MOs determined at step 50. In other words, apparatus 20 can indicate one or more MOs determined at step 50 via the request.

[0094] In some examples, device 20 can be based on a scheme (such as by...) Figure 3 and / or Figure 4 Illustration and reference Figure 3 and / or Figure 4 The described scheme is used to provide the transmission of the request. For example, according to the scheme described... Figure 3 Illustration and reference Figure 3In the described scheme, device 20 can provide the transmission of the request, enabling the network (e.g., network node 12) to cache downlink data for device 20 (e.g., in response to the request). That is, the request can trigger the network to cache downlink data for device 20. Therefore, in response to the request, the network can cache downlink data for device 20 between a first time opportunity and a second time opportunity, wherein the first time opportunity is associated with the transmission of the request (e.g., and therefore also with the reception of the request at the network), and the second time opportunity is associated with the reception of downlink alarm information at device 20 (e.g., and therefore also with the transmission of downlink alarm information from the network). According to this scheme, the MO for receiving downlink alarm information can occur for a period of time after the transmission of the request. For example, the first and second time opportunities can be separated by a duration during which device 20 operates in an inactive state. Thus, the network can cache (or otherwise store) downlink information for device 20 during its inactive period and send downlink alarm information in the MO (e.g., during the active period of device 20). MO may include one or more second resources associated with a second timing, which may overlap with at least a portion of one or more MOs determined in step 50 or with different MOs.

[0095] like Figure 5As shown in block 54, device 20 includes components (e.g., processing circuitry 22, memory device 24) for monitoring downlink alarm information in response to the request. Device 20 may monitor downlink alarm information during a second timing period, which may be based on one or more monitoring timing periods. The downlink alarm information is associated with downlink data cached between the first and second timing periods. For example, the downlink alarm information may indicate a state associated with the downlink data cached between the first and second timing periods. For example, the downlink alarm information may indicate the availability of downlink data for device 20. In such an example, the state corresponds to the availability of downlink data. In some other examples, the downlink alarm information may indicate a lack of downlink data for device 20. In such an example, the state corresponds to a lack (or unavailability) of downlink data for device 20. In some other examples, the downlink alarm information may include control information (e.g., scheduling information or system information). For example, the downlink alarm information may include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such an example, a downlink alert message (e.g., indicating the status of downlink data) may be sent from the network via a data channel in one of multiple indicator resources. Alternatively or additionally, the downlink alert information may include system information available to the UE 10, such as information used to establish a connection with the network (e.g., for receiving downlink data). In some examples, the downlink alert information may include downlink data.

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

[0097] In some examples, device 20 can receive downlink alarm information based on the activity state. Additionally, in some examples, device 20 can determine whether to operate in an inactive or active state (e.g., selectable, chooseable) based on the downlink alarm information (e.g., based on the status of downlink data, based on control information). In other words, based on the downlink alarm information, device 20 can transition to an inactive state or continue operating in an active state.

[0098] Now for reference Figure 6 This describes, in an example embodiment, some operations performed at device 20 (e.g., node 13, which may be an example of network node 12 or UE 11) for providing downlink alarm information triggered by the UE. Figure 6 As shown, device 20 can send downlink alarm information to UE (e.g., UE 10, which may be an example of an LPWA IoT device).

[0099] like Figure 6 As shown in block 60, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for receiving a request for downlink alarm information from a UE. Apparatus 20 may receive the request during a first timing event (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may indicate one or more MOs for the transmission of downlink alarm information to the UE. The one or more MOs may correspond to time-domain and / or frequency-domain resources in which the UE can use to receive downlink alarm information.

[0100] like Figure 6As shown in block 62, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing transmission of downlink alarm information to a UE. Apparatus 20 may provide transmission of downlink alarm information during a second timing period, which may be based on one or more MOs. In some examples, the second timing period may correspond to one or more time-domain and / or frequency-domain resources overlapping with at least a portion of one or more MOs. For example, apparatus 20 may accept one or more MOs, and in some examples, provide transmission of an acknowledgment message to the UE. In such examples, the acknowledgment message may indicate that one or more time-domain and / or frequency-domain resources for receiving downlink alarm information overlap with at least a portion of one or more MOs. In some other examples, the second timing period may correspond to one or more time-domain and / or frequency-domain resources overlapping with at least a portion of an MO, which is different from one or more MOs. For example, apparatus 20 may reject one or more MOs (e.g., due to scheduling conflicts at the UE and / or one or more other UEs), and in some examples, may send a message to the UE indicating one or more time-domain and / or frequency-domain resources overlapping with at least a portion of an MO that is different from one or more MOs. In such an example, the MO can be determined at device 20 based on one or more MOs. For example, one or more MOs can be taken into account in the determination of the MO, so that the MO can be adapted to the UE.

[0101] In some examples, in response to the request, the network (e.g., device 20 or other device) can cache downlink data for the UE. Therefore, downlink alarm information can be associated with the downlink data cached at the network. In some examples, downlink alarm information can indicate the status associated with downlink data cached between a first time point and a second time point. For example, downlink alarm information can indicate the availability of downlink data for the UE. In such examples, the status corresponds to the availability of downlink data. In some other examples, downlink alarm information can indicate the 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, downlink alarm information can include control information (e.g., scheduling information or system information). For example, downlink alarm information can include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such examples, downlink alarm messages (e.g., indicating the status of downlink data) can be transmitted from the network via a data channel in (multiple) indicating resources. Alternatively or concurrently, downlink alert information may include system information that the UE can obtain, such as information used to establish a connection with the network (e.g., for receiving downlink data). In some examples, downlink alert information may include downlink data.

[0102] Now for reference Figure 7 This describes some operations performed by device 20 (e.g., UE 10) in an example embodiment to provide UE-triggered downlink alarm information. For example... Figure 7 As shown, device 20 can request downlink alarm information from nodes (e.g., network node 12, UE 11).

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

[0104] like Figure 7 As shown in block 72, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing the transmission of a request for downlink alarm information from a node. Apparatus 20 can provide the transmission of this request such that the transmission occurs during a first timing event (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 indication of one or more MOs determined at step 70. In other words, apparatus 20 can indicate one or more MOs determined at step 70 via the request.

[0105] In some examples, device 20 can be based on a scheme (such as by...) Figure 3 and / or Figure 4 Illustration and reference Figure 3 and / or Figure 4 The described scheme is used to provide the transmission of the request. For example, according to the scheme described... Figure 4 Illustration and reference Figure 4In the described scheme, device 20 can provide the transmission of the request such that the network (e.g., network node 12) can cache downlink data for device 20 before the network receives the request (e.g., until the network receives the request). That is, the network can cache downlink data for device 20 before a first time opportunity associated with the transmission of the request (e.g., and therefore, the reception of the request at the network). According to such a scheme, the MO for receiving downlink alarm information can be after the first time opportunity (e.g., immediately following the first time opportunity, or after the first time opportunity). That is, a second time opportunity can be associated with one or more second resources that follow (e.g., immediately following, or after) the one or more first resources associated with the first time opportunity. Therefore, in some examples, device 20 includes components (e.g., processing circuitry 22, memory device 24) for providing a transition from an inactive state to an active state at device 20, such that device 20 can provide the transmission of the request (and subsequent reception of downlink alarm information) in the active state.

[0106] like Figure 7 As shown in block 74, device 20 includes components (e.g., processing circuitry 22, memory device 24) for monitoring downlink alarm information in response to the request. Device 20 may monitor downlink alarm information during a second timing period, which may be based on one or more monitoring timing periods. The downlink alarm information is associated with downlink data cached prior to the first timing period. For example, the downlink alarm information may indicate a state associated with downlink data cached prior to the first timing period. For example, the downlink alarm information may indicate the availability of downlink data for device 20. In such an example, the state corresponds to the availability of downlink data. In some other examples, the downlink alarm information may indicate a lack of downlink data for device 20. In such an example, the state corresponds to a lack (or unavailability) of downlink data for device 20. In some other examples, the downlink alarm information may include control information (e.g., scheduling information or system information). For example, the downlink alarm information may include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such an example, a downlink alert message (e.g., indicating the status of downlink data) may be sent from the network via a data channel in one of multiple indicator resources. Alternatively or additionally, the downlink alert information may include system information available to the UE 10, such as information used to establish a connection with the network (e.g., for receiving downlink data). In some examples, the downlink alert information may include downlink data.

[0107] In some examples, device 20 includes components (e.g., processing circuitry 22, communication interface 26) for receiving downlink alarm information in response to the request. Device 20 may receive the downlink alarm information during a second timing period, where the second timing period is based on one or more MOs. For example, the second timing period may correspond to one or more time-domain and / or frequency-domain resources overlapping with at least a portion of one or more MOs. The device may determine whether to operate in an inactive or active state (e.g., selectable, chooseable) based on the downlink alarm information (e.g., based on the state of downlink data). In some examples, device 20 may receive downlink alarm information based on the active state. Additionally, in some examples, the device may determine whether to operate in an inactive or active state (e.g., selectable, chooseable) based on the downlink alarm information (e.g., based on the state of downlink data). In other words, based on the downlink alarm information, device 20 may transition to an inactive state or continue operating in an active state.

[0108] Now for reference Figure 8 This describes, in an example embodiment, some operations performed at device 20 (e.g., node 13, which may be an example of network node 12 or UE 11) for providing downlink alarm information triggered by the UE. Figure 8 As shown, device 20 can send downlink alarm information to UE (e.g., UE 10, which may be an example of an LPWA IoT device).

[0109] like Figure 8 As shown in block 80, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for receiving a request for downlink alarm information from a UE. Apparatus 20 may receive the request during a first timing event (e.g., a first one or more time-domain resources, which may be associated with one or more frequency-domain resources). The request may indicate one or more MOs for the transmission of downlink alarm information to the UE. The one or more MOs may correspond to time-domain and / or frequency-domain resources in which the UE can use to receive downlink alarm information.

[0110] like Figure 8As shown in block 82, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing downlink alarm information to the UE. Apparatus 20 may provide the transmission of downlink alarm information during a second timing period, which may be based on one or more MOs. In some examples, the second timing period may correspond to one or more time-domain and / or frequency-domain resources overlapping with at least a portion of one or more MOs. The network (e.g., apparatus 20 or another apparatus) may cache downlink data for the UE prior to (e.g., until) the receipt of the request. Therefore, downlink alarm information may be associated with downlink data cached prior to the first timing period. In some examples, downlink alarm information may indicate a state associated with downlink data cached prior to the first timing period. For example, downlink alarm information may indicate the availability of downlink data for the UE. In such an example, the state corresponds to the availability of downlink data. In some other examples, downlink alarm information may indicate a lack of downlink data for the UE. In such an example, the state corresponds to a lack (or unavailability) of downlink data for the UE. In some other examples, downlink alarm information may include control information (e.g., scheduling information or system information). For example, downlink alarm information may include control information that may include scheduling information (e.g., time and / or frequency resources) for receiving downlink alarm messages. In such examples, downlink alarm messages (e.g., indicating the status of downlink data) may be transmitted from the network via a data channel in (multiple) indication resources. Alternatively or additionally, downlink alarm information may include system information that the UE can obtain, such as information used to establish a connection with the network (e.g., for receiving downlink data). In some examples, downlink alarm information may include downlink data.

[0111] As described above, a method, apparatus, and computer program product for providing downlink alarm information triggered by a UE are disclosed. In this regard, a method, apparatus, and computer program product are configured to provide the transmission of a request for downlink alarm information from a network node. By providing the transmission of the request for downlink alarm information, the method, apparatus, and computer program product can provide reduced power consumption at the UE. In some aspects, reduced power consumption can lead to increased UE lifetime, more efficient data transmission with the UE, and operation over a wider coverage area.

[0112] Figures 5-8A flowchart depicting a method according to an exemplary embodiment of the present disclosure is illustrated. It should be understood that each block of the flowchart and combinations of blocks in the flowchart can be implemented by various means, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more processes in the above-described process can be embodied by computer program instructions. In this regard, the computer program instructions embodying the above-described processes can be stored in a memory device 24 of the apparatus 20 employing an embodiment of the present disclosure and executed by a processor 22. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine, such that the resulting computer or other programmable device performs the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can instruct a computer or other programmable device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of art, the execution of which performs the functions specified in the flowchart blocks. Computer program instructions can also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device, thereby producing a computer-implemented process, such that the instructions executing on the computer or other programmable device provide operations for implementing the functions specified in the flowchart blocks. Therefore, the flowchart blocks support combinations of components for performing specified functions and combinations of operations for performing specified functions. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by a computer system based on dedicated hardware or a combination of dedicated hardware and computer instructions for performing the specified functions. Those skilled in the art to which this disclosure pertains will be able to conceive of many modifications and other embodiments of the disclosure set forth herein, benefiting from the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that this disclosure is not limited to the disclosed exemplary embodiments, and modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe some exemplary embodiments in the context of some exemplary combinations of elements and / or functions, it should be understood 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 the elements and / or functions explicitly described above are also contemplated, as may be set forth in some of the appended claims. Although specific terms are used herein, they are used in a general and descriptive sense and not for limiting purposes.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the means to at least: Determine one or more monitoring opportunities for receiving downlink alert information from the node; During the first timing period, a request for the downlink alarm information is transmitted, wherein the request indicates the one or more monitoring timings; as well as During a second time period, the downlink alarm information is monitored in response to the request, wherein the second time period is at least partially based on the one or more monitoring time periods, and wherein the downlink alarm information is associated with downlink data cached between the first time period and the second time period.

2. The apparatus of claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: In response to the request, a message is received from the node, wherein the message indicates one or more resources for receiving the downlink alarm information, and wherein the second timing is at least partially based on the one or more resources.

3. The apparatus of claim 2, wherein the message indicates at the apparatus confirmation of the one or more monitoring opportunities for receiving the downlink alarm information, and wherein the confirmation indicates that the one or more resources overlap with at least a portion of the one or more monitoring opportunities.

4. The apparatus of claim 2, wherein the message includes an indication of the one or more resources, and wherein the one or more resources overlap with at least one monitoring time that is different from the one or more monitoring times.

5. The apparatus according to any one of claims 1 to 4, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The downlink alarm information is received from the node during the second time period, at least in part based on the monitoring.

6. The apparatus of claim 5, wherein the downlink alarm information includes at least one of the following: system information associated with receiving the downlink data from the node, or an indication of one or more resources for receiving the downlink alarm message from the node.

7. The apparatus of claim 5, wherein the downlink alarm information includes a downlink alarm message, and wherein the downlink alarm message indicates a status associated with the downlink data.

8. The apparatus of claim 7, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: Based at least in part on the downlink alert message, it is determined whether to take action based on the active or inactive state.

9. The apparatus of claim 8, wherein the state indicates the 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: The decision to operate based on the activity status is made at least in part based on the availability of downlink data for the device indicated by the status.

10. The apparatus of claim 8, wherein the state indication addresses 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: Based at least in part on the lack of downlink data for the device indicated by the status, it is determined to operate according to the inactive state.

11. The apparatus of claim 10, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: Based at least in part on the lack of downlink data for the device, a second or more monitoring opportunities are determined, wherein a first period associated with the one or more monitoring opportunities is shorter than a second period associated with the second or more monitoring opportunities; and Provides a transmission of indication of the second or more monitoring timings to the node.

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

13. The apparatus of claim 12, wherein the one or more downlink characteristics include at least one of the following: average inter-packet arrival time associated with the downlink data, time criticality associated with the downlink data, priority associated with the downlink data, packet delay budget associated with the downlink data, frequency associated with downlink alarm information transmission, or probability of downlink alarm information transmission occurring during a time interval.

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

15. The apparatus according to any one of claims 1 to 14, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The node receives second control information, wherein the second control information indicates a set of candidate monitoring opportunities for receiving the downlink alarm information, and wherein the determination of one or more monitoring opportunities is at least in part based on the set of candidate monitoring opportunities.

16. The apparatus according to any one of claims 1 to 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 indicates a scheme for transmitting the downlink alarm information, and wherein the transmission of the request is in accordance with the scheme.

17. The apparatus according to any one of claims 1 to 15, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: A switch is made from a first scheme for transmitting other downlink alert information to a second scheme for transmitting the downlink alert information, wherein the transmission of the requested information is at least partially based on the switch and is in accordance with the second scheme.

18. The apparatus of claim 17, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The node receives 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. The apparatus of claim 17, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The node receives a first indication of a trigger criterion associated with a switch from the first scheme to the second scheme, wherein the switch is met at least in part based on the trigger criterion.

20. The apparatus of claim 19, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: In response to the switching, a second indication of the second scheme is transmitted to the node.

21. The apparatus of claim 19, wherein the triggering criterion includes a threshold energy availability level, and wherein the switching is based at least in part on the energy availability at the apparatus satisfying the threshold energy availability level.

22. The apparatus according to any one of claims 1 to 21, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: In response to the downlink alarm information, monitor the physical downlink control channel or the physical downlink shared channel.

23. An apparatus comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the means to at least: During the first timing period, a request for downlink alarm information is received, wherein the request indicates one or more monitoring timings for the transmission of the downlink alarm information to the user equipment (UE); as well as During a second timing period, the downlink alarm information is transmitted to the UE, wherein the second timing period is at least partially based on the one or more monitoring timing periods, and wherein the downlink alarm information is associated with downlink data cached at the node between the first timing period and the second timing period.

24. A method comprising: At the user equipment, determine one or more monitoring opportunities for receiving downlink alarm information from the node; During the first timing period, a request for the downlink alarm information is transmitted, wherein the request indicates the one or more monitoring timings; as well as During a second time period, the downlink alarm information is monitored in response to the request, wherein the second time period is at least partially based on the one or more monitoring time periods, and wherein the downlink alarm information is associated with downlink data cached between the first time period and the second time period.

25. A method comprising: During the first timing period, a request for downlink alarm information is received, wherein the request indicates one or more monitoring timings for the transmission of the downlink alarm information to the user equipment (UE); as well as During a second timing period, the downlink alarm information is transmitted to the UE, wherein the second timing period is at least partially based on the one or more monitoring timing periods, and wherein the downlink alarm information is associated with downlink data cached at the node between the first timing period and the second timing period.