Public warning system support in narrowband internet of things

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE), such as a narrowband internet of things (NB-IoT) UE, may determine whether a cell supports PWS notification and may respond accordingly. The UE may establish a wireless connection with a network entity associated with a cell. Then, the UE may receive, from the network entity via the wireless connection, a first message that indicates whether PWS notification is supported by the cell. The first message may be a master information block (MIB). The MIB may indicate that one or more PWS messages are scheduled. Additionally, or alternatively, the first message may be a first system information block (SIB). The UE may perform one or more operations to establish a connection with a cell that supports PWS notification.

Description

Qualcomm Ref. No. 2500218WO1PUBLIC WARNING SYSTEM SUPPORT IN NARROWBAND INTERNET OF THINGSCROSS REFRENCE

[0001] The present Application for Patent claims priority to Greece Patent Application No. 20240100772 by SHRESTHA et al., entitled “PUBLIC WARNING SYSTEM SUPPORT IN NARROWBAND INTERNET OF THINGS,” filed November 1, 2024, which is assigned to the assignee hereof, and is expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including public warning system support in narrowband internet of things.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO2SUMMARY

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include establishing a wireless connection with a network entity associated with a cell, where the UE is a narrowband internet of things (NB-IoT) UE and receiving, via the wireless connection, a first message that indicates whether public warning system (PWS) notification is supported by the cell.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to establish a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE and receive, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0007] Another UE for wireless communications is described. The UE may include means for establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE and means for receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to establish a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE and receive, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0009] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the first message may include operations, features, means, or instructions for receiving, via the wireless connection, a master information block (MIB) that indicates that PWS notification may be supported by the cell.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO3

[0010] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the first message may include operations, features, means, or instructions for receiving, via the wireless connection, a MIB that indicates that one or more PWS messages may be scheduled.

[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the MIB includes scheduling information for one or more system information blocks (SIBs) that include the one or more PWS messages.

[0012] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the first message may include operations, features, means, or instructions for receiving, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification may be supported by the cell.

[0013] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the first message may include operations, features, means, or instructions for receiving, via the wireless connection, a first SIB that includes an indication, specific to a public land mobile network (PLMN) associated with the network entity, that PWS notification may be supported by the PLMN.

[0014] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, receiving the first message may include operations, features, means, or instructions for receiving, via the wireless connection, a first SIB that includes an indication that PWS notification may be supported by one or more neighbor cells that neighbor the cell associated with the network entity.

[0015] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for applying a reselection offset to a metric associated with the cell or with a frequency band based on the cell or the frequency band not supporting PWS notification and performing a cell selection procedure in accordance with a bias that may be based on the reselection offset.

[0016] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, orAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO4 instructions for receiving information indicative of a value of the reselection offset, where the information may be received via dedicated signaling from the network entity or in neighbor cell information from another network entity.

[0017] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the cell does not support PWS notification and performing a cell selection procedure based on a set of one or more cells that excludes the cell for a time duration based on the cell not supporting PWS notification.

[0018] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the cell does not support PWS notification and performing one or more periodic search operations to identify and select a second cell that supports PWS notification, where performance of the one or more periodic search operations may be based on a cell prioritization scheme that prioritizes connection with cells that do support PWS notification.

[0019] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving one or more identifiers that indicate a location to which a PWS message pertains.

[0020] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more identifiers include country codes, telecommunication area codes, or both.

[0021] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more identifiers may be received in the PWS message or in a SIB associated with the PWS message.

[0022] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second message that configures the UE with an identifier set, where the UE determines that the PWS message pertains to the UE based on a comparison of the one or more identifiers with the identifier set.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO5

[0023] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving scheduling information for a PWS message, where the scheduling information may be received via a SIB or via dedicated signaling from the network entity.

[0024] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first message indicates that a set of PWS messages may be provided with same scheduling information in a system information window.

[0025] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a SIB that indicates scheduling information for a PWS message and monitoring for the PWS message using the scheduling information only when a paging message or downlink control information (DCI) notification indicates that the PWS message may be available.

[0026] A method for wireless communications by a network entity is described. The method may include establishing a wireless connection with a UE, where the UE is an NB-IoT UE and outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0027] A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to establish a wireless connection with a UE, where the UE is an NB-IoT UE and output, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0028] Another network entity for wireless communications is described. The network entity may include means for establishing a wireless connection with a UE, where the UE is an NB-IoT UE and means for outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO6

[0029] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to establish a wireless connection with a UE, where the UE is an NB- loT UE and output, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0030] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first message may include operations, features, means, or instructions for outputting, via the wireless connection, a MIB that indicates that PWS notification may be supported by the cell.

[0031] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first message may include operations, features, means, or instructions for outputting, via the wireless connection, a MIB that indicates that one or more PWS messages may be scheduled.

[0032] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the MIB includes scheduling information for one or more SIBs that include the one or more PWS messages.

[0033] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first message may include operations, features, means, or instructions for outputting, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification may be supported by the cell.

[0034] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first message may include operations, features, means, or instructions for outputting, via the wireless connection, a first SIB that includes an indication, specific to a PLMN associated with the network entity, that PWS notification may be supported by the PLMN.

[0035] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first message may include operations, features, means, or instructions for outputting, via the wireless connection, aAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO7 first SIB that includes an indication that PWS notification may be supported by one or more neighbor cells that neighbor the cell associated with the network entity.

[0036] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting information indicative of a value of a reselection offset, where the reselection offset may be associated with the cell and biases the cell during a cell selection procedure, where the bias may be based on the cell not supporting PWS notification.

[0037] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting one or more identifiers that indicate a location to which a PWS message pertains.

[0038] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more identifiers include country codes, telecommunication area codes, or both.

[0039] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more identifiers may be included in the PWS message or in a SIB associated with the PWS message.

[0040] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a second message that configures the UE with an identifier set that includes one or more locations to facilitate comparison of the one or more identifiers with the identifier set.

[0041] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting scheduling information for a PWS message, where the scheduling information may be received via a SIB or via dedicated signaling from the network entity.

[0042] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first message indicates that a set ofAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO8PWS messages may be provided with same scheduling information in a system information window.

[0043] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a SIB that indicates scheduling information for a PWS message, where the scheduling information may be usable to monitor for the PWS message only when a paging message or DCI notification indicates that the PWS message may be available.

[0044] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0045] FIG. 1 shows an example of a wireless communications system that supports PWS (PWS) support in narrowband internet of things (NB-IoT) in accordance with one or more aspects of the present disclosure.

[0046] FIG. 2 shows an example of a wireless communications system that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0047] FIG. 3 shows an example of a process flow that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0048] FIGs. 4 and 5 show block diagrams of devices that support PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0049] FIG. 6 shows a block diagram of a communications manager that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0050] FIG. 7 shows a diagram of a system including a device that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO9

[0051] FIGs. 8 and 9 show block diagrams of devices that support PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0052] FIG. 10 shows a block diagram of a communications manager that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0053] FIG. 11 shows a diagram of a system including a device that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.

[0054] FIGs. 12 and 13 show flowcharts illustrating methods that support PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0055] In some wireless communications systems, narrowband internet of things (NB-IoT) radio access technology (RAT) may not support public warning system (PWS) notification. Further, an NB-IoT user equipment (UE) may not support PWS notification reception or other associated functionalities. For example, the NB-IoT UE may not support reading a broadcast notification message in a connected mode (e.g., RRC CONNECTED). If PWS is supported in a cell, the UE may use such a notification to allow a user to be aware of the PWS capability. Since PWS notifications may include important information for users, including safety and disaster information, failing to support PWS notification transmission and reception may present safety concerns for users. Thus, techniques described herein support an NB-IoT UE procedure to handle cases where a cell supports PWS notification and where a cell does not support PWS notification.

[0056] As described herein, a UE may determine whether a cell supports PWS notification and may respond accordingly. The UE (e.g., an NB-IoT UE) may establish a wireless connection with a network entity associated with a cell. Then, the UE may receive, from the network entity via the wireless connection, a first message that indicates whether PWS notification is supported by the cell. In some cases, the first message may be a master information block (MIB). The MIB may indicate that one or more PWS messages are scheduled. In some examples, the first message may be a first system information block (SIB) (e.g., SIB1) and may be an example of an NB-IoTAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO10 message. The first SIB may be specific to a cell or may be specific to a public land mobile network (PLMN). In any case, the first SIB may indicate that PWS notification is supported (e.g., by the cell or by the PLMN). The UE may perform one or more operations to establish a connection with a cell that supports PWS notification. For example, the UE may perform a cell selection procedure according to a bias or an offset to select a cell that supports PWS notification. Additionally, or alternatively, the UE may perform periodic searches to identify and select a cell that supports PWS notification.

[0057] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described with reference to a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to PWS support in NB-IoT.

[0058] FIG. 1 shows an example of a wireless communications system 100 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0059] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link(s) 125. The coverageAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO11 area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more RATs.

[0060] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0061] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0062] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via backhaul communicationAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO12 link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0063] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0064] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO)Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO13 system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0065] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may beAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO14 functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0066] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station). The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO15

[0067] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support PWS support in NB-IoT as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0068] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0069] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0070] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communicationsAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO16 system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

[0071] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0072] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / mflx■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Ay may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radioAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO17 frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0073] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0074] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0075] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channelAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO18 candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0076] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0077] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO19

[0078] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

[0079] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0080] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0081] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinationsAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO20 thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0082] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to- many (1 :M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

[0083] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet DataAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO21Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0084] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0085] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO22

[0086] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0087] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0088] In some wireless communications systems (e.g., in LTE), a paging procedure may include sending a PWS notification. A UE may receive the PWS notification (e.g., the warning message) via one or more SIB messages (e.g., SIB10, SIB11, or SIB12).Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO23However, some wireless communications systems may not support such a procedure for NB-IoT devices. For example, an NB-IoT RAT may not support PWS notification and NB-IoT UEs may not support PWS notification reception. Further, NB-IoT UEs may not support some functionalities or communication procedures (e.g., “acceptable cell”, “Camped on Any cell state”, “emergency call”, or the like). Some NB-IoT UEs may fail to support reading a broadcast notification message in an RRC connected state (e.g., RRC CONNECTED). Even if PWS is supported in a cell, the UE may fail to determine that the cell supports PWS notification (e.g., the UE may not be aware of this capability of the cell) unless the UE can read the broadcast notification message.

[0089] Accordingly, techniques described herein may support a UE procedure to handle cases where a cell supports PWS notification and other cases where a cell does not support PWS notification. The wireless communications system 100 may support a UE 115 (e.g., an NB-IoT UE) to determine whether a cell supports PWS notification and to respond accordingly. The UE 115 may establish a wireless connection with a network entity 105 associated with a cell. Then, the UE 115 may receive, from the network entity 105 via the wireless connection, a first message (e.g., an NB-IoT message) that indicates whether PWS notification is supported by the cell. In some cases, the first message may be a MIB. The MIB may indicate that one or more PWS messages are scheduled. In some examples, the first message may be a SIB1 message. The SIB1 message may be specific to a cell or may be specific to a PLMN. In any case, the SIB1 message may indicate that PWS notification is supported (e.g., by the cell or by the PLMN). The UE 115 may perform one or more operations to establish a connection with a cell that supports PWS notification. For example, the UE 115 may perform a cell selection procedure according to a bias or an offset to select a cell that supports PWS notification. Additionally, or alternatively, the UE 115 may perform periodic searches to identify and select a cell that supports PWS notification.

[0090] Techniques described herein may support broadcast of PWS messages for NB-IoT devices (e.g., by re-using one or more LTE mechanisms). Some techniques described in the context of a non-terrestrial network (NTN) may be applied in a terrestrial network (TN). Similarly, some techniques described in the context of a TN may also be applied in an NTN (e.g., if possible). In some cases, the wireless communications system 100 may support one or more indications to devices within anAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO24 intended service area (e.g., for an earthquake and tsunami warning system (ETWS)). As described herein, the term “PWS” may be used to describe one or more public warning systems, which may include ETWS, commercial mobile alert system (CMAS), European public warning system (e.g., EU-ALERT), or the like. As described herein, the terms “PWS notification” and “PWS message transmission” may be used interchangeably and may describe an ability of a cell to notify one or more UEs that a public warning has been issued (e.g., an ability of a cell to output or transmit PWS messages).

[0091] FIG. 2 shows an example of a wireless communications system 200 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. In some cases, the wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more UEs 115 (e.g., a UE 115-a) and one or more network entities 105 (e.g., a network entity 105-a and a network entity 105-b), which may be examples of the corresponding devices as described herein. The network entity 105-a may be associated with (e.g., in communication with, located in) a cell 205-a and the network entity 105-b may be associated with a cell 205-b. In the following description, communications between a UE 115 and a network entity 105 may equally be interpreted as communications between the UE 115 and a cell 205 corresponding to the network entity 105. For example, the network entity 105-a may support communications between the UE 115-a and the cell 205-a. The network entity 105-a and the network entity 105-b may be examples of NTN entities (e.g., satellite devices, or other devices in orbit). As described herein, a UE 115 may refer to an NB- loT device such as an NB-IoT UE.

[0092] The UE 115-a and the network entity 105-a may establish a wireless communication link 210-a. In some cases, the UE 115-a may receive one or more messages via the wireless communication link 210-a. For example, the UE 115-a may receive a PWS support indication 215 via the wireless communication link 210-a. The PWS support indication 215 may indicate whether the cell 205-a supports PWS notification. In a first case, the PWS support indication 215 may indicate that the cell 205-a may transmit PWS notifications (e.g., for NB-IoT devices, including NB-IoTAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO25UEs). In a second case, the PWS support indication 215 may indicate that the cell 205-a does not support PWS notification for NB-IoT UEs.

[0093] In some implementations, one or more downlink messages may carry the PWS support indication 215. For example, the network entity 105-a may provide the PWS support indication 215 via a MIB in NB-IoT (e.g., a reserved bit within the MIB may be used to indicate support for PWS). The PWS support indication 215 may serve one or more purposes. In some cases, the PWS support indication 215 may indicate that the cell 205-a supports PWS message delivery. That is, the PWS support indication 215 may be present in the MIB (e.g., any MIB) from the cell 205-a if the cell 205-a supports PWS notification. In some examples, the presence of a PWS support indication 215 may indicate, to the UE 115-a (e.g., the NB-IoT UE) that one or more PWS messages 225 are scheduled (e.g., scheduled to be delivered to the UE 115-a). Accordingly, the PWS support indication 215 may indicate that the UE 115-a is to receive (e.g., acquire) a PWS message 225.

[0094] In some implementations, the PWS support indication 215 may include scheduling information for one or more PWS SIBs (e.g., similar to one or more parameters such as schedulingInfoSIBl-rl3). The PWS support indication 215 may include one or more parameters associated with scheduling PWS messages 225. For example, the PWS support indication 215 within the MIB may include a scheduling information parameter (e.g., schedulingInfoPWS-SIB-rl9) indicating an integer value (e.g., INTEGER (0 . . 15)) that may indicate a SIB associated with a PWS message 225, a quantity of scheduled PWS messages 225, a PWS message type, or any combination thereof. The scheduling information parameter may provide direct scheduling information corresponding to one or more SIBs (e.g., SIB10, SIB11, or SIB12). Accordingly, in some cases, the UE 115-a may refrain from acquiring SIB1 (e.g., skipping acquisition of SIB1). Additionally, or alternatively, the PWS support indication 215 may include a parameter that indicates whether PWS is enabled or supported (e.g., for the cell 205-a). Such a parameter (e.g., pws-Enabled-rl9) may indicate a value (e.g., a BOOLEAN value) such as “true” or “false”. A value of “true” may indicate that PWS notification is enabled or supported while a value of “false” may indicate that PWS notification is disabled (or not supported) for the cell 205-a. In some cases, a spare bit string of the MIB may have a modified (e.g., reduced) size toAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO26 accommodate the parameters associated with the PWS support indication 215. In some examples, the UE 115-a may prioritize reading a SIB1 of the cell 205-a based on the cell 205-a supporting PWS.

[0095] In some cases, the scheduling information parameter may include an index (e.g., the integer value) that indicates (e.g., points to) information associated with a PWS message 225 such as transport block size (TBS), repetitions, periodicity, SIB scheduling offset, or any combination thereof. For example, each index of a set of indexes may be mapped to a respective periodicity (or other parameter) (e.g., indexes 0, 1, and 2 may be mapped to periodicity of rfl28, rf256, and rf512, respectively). Additionally, or alternatively, the scheduling information parameter may be associated with six bits for scheduling information. For example, two bits may indicate a periodicity (e.g., four periodicity values may be considered, such as rf64, rfl28, rf256, and rf512). Similarly, four bits may be used to indicate repetitions and a TBS. In some implementations, a SIB scheduling offset and an index x may be set to 0 for a PWS system information message. In any case, the scheduling information parameter (e.g., schedulingInfoPWS-SIB-rl9) may be present in a MIB or a SIB (e.g., SIB1) as described herein.

[0096] In some implementations, the network entity 105-a may provide the PWS support indication 215 via a SIB (e.g., SIB1). As indicated by the SIB, the PWS support indication 215 may be a cell specific indication. That is, the PWS support indication 215 may indicate that the cell 205-a (and a network entity 105-a thereof) supports PWS message transmission. In response to receiving such a cell specific indication, the UE 115-a may prioritize the indicated cell during a cell selection procedure or a cell reselection procedure (e.g., modifying one or more parameters for a selection procedure to prioritize selection of cells that support PWS). Additionally, or alternatively, the PWS support indication 215 may be a PLMN specific indication. In response to receiving such a PLMN specific indication, the UE 115-a may prioritize the indicated cell during a PLMN selection procedure or a PLMN reselection procedure (e.g., modifying one or more parameters for a selection procedure to prioritize selection of PLMNs that support PWS). In some cases, the UE 115-a may read the SIB that includes the PWS support indication 215. Afterward, an access stratum layer of the UE 115-a may forward the PWS support indication 215 to a non-access stratum layer of the UEAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO27115-a. In some examples, the UE 115-a may receive one or more PWS support indications 215 corresponding to respective neighbor cells of a set of neighbor cells (e.g., a neighbor cell list) in the SIB. For example, the UE 115-a may receive the one or more PWS support indications 215 from the network entity 105-a, the network entity 105-b (e.g., via a wireless communication link 210-b), one or more other network entities 105, or any combination thereof.

[0097] In some implementations, NB-IoT devices described herein may support ranking based cell reselection and may further support frequency priorities for cell selection and reselection. For example, the UE 115-a (e.g., an NB-IoT UE) may be configured with a reselection offset. The UE 115-a may use the reselection offset to bias selection of a cell or a frequency that does not support PWS (or similarly, a cell or a frequency that does support PWS). In some examples, the UE 115-a may store the reselection offset (e.g., in one or more memories of the UE 115-a) and may apply the reselection offset during a next reselection procedure that includes the cell 205. In some cases, the offset may be configured at the UE 115-a (e.g., hard coded at the UE 115-a or defined by one or more standards for a cell that does not support PWS). In some implementations, a network may provide information that indicates one or more reselection offsets. The information may include an offset and a corresponding cell or frequency such that the UE 115-a may identify which cell the offset pertains to. The UE 115-a may receive the information in dedicates signaling or in a neighbor cell information field within a SIB. For example, the UE 115-a may receive, from one or more network entities 105 (e.g., the network entity 105-a, the network entity 105-b, or both), respective indications of reselection offsets associated with respective cells 205 corresponding to the network entities 105.

[0098] In some cases, the UE 115-a may perform a cell reselection procedure based on one or more PWS support indications 215 received from one or more network entities 105. For example, the UE 115-a may determine, based on a PWS support indication 215 from the network entity 105-a, that the cell 205-a does not support PWS message transmission. In response, the UE 115-a may exclude (or bar) the cell 205-a from a set of cells 205 used for the cell reselection procedure for a duration (e.g., at least T seconds, such as 300 seconds). In a case where the UE 115-a is unable to determine a cell 205 that supports PWS message transmission within the duration, the UE 115-aAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO28 may remain in communication with (e.g., camp on) the cell 205-a that may not support PWS. If the UE determines that the cell 205-b supports PWS message transmission prior to an expiration of the duration, the UE 115-a may reselect to the cell 205-b. In some implementations, prioritization may be defined for the cell reselection procedure as described herein. In some cases, if the UE 115-a determines that the UE 115-a is in communication with a cell 205-a that does not support PWS message transmission, the UE 115-a may periodically search for a cell 205 that supports PWS. For example, the UE 115-a may establish a wireless communication link 210-b with the network entity 105-b within the cell 205-b. Then, the UE 115-a may receive a PWS support indication 215 that indicates that the cell 205-b supports PWS message transmission. Accordingly, the UE 115-a may reselect to the cell 205-b (e.g., if the cell 205-a does not support PWS message transmission). In some implementations, the UE 115-a may use (e.g., apply) the prioritization defined for the cell reselection procedure when the UE 115-a is in communication with (e.g., is camping on) an acceptable cell (e.g., a cell 205 determined by the UE 115-a to be acceptable for the prioritization). For example, the UE 115-a may determine that the cell 205-a is an acceptable cell. In response, the UE 115-a may perform periodic searches for the cell 205 that supports PWS using the defined prioritization.

[0099] A beam footprint of a network (e.g., an NTN) may be relatively large (e.g., covering multiple regions, including political territories). Thus, if a network entity outputs a PWS message, all UEs within the beam footprint (e.g., region) may receive the PWS message. As a result, the PWS message may not be applicable for one or more UEs within the beam footprint. Further, providing geographic coordinates to indicate an intended region for the PWS message may incur relatively large signaling overhead for NB-IoT communication (which may present issues due to TBS limitations).

[0100] Accordingly, techniques described herein may reduce signaling overhead associated with PWS message transmission. For example, the network entity 105-a may transmit an identifier message 220 to the UE 115-a. The identifier message 220 may include a list of country codes, area codes, or both (e.g., used for voice call in telecommunication). The list may indicate that a PWS message 225 is intended for a particular area or region associated with one or more country codes, area codes, or both, within the list. The UE 115-a may use the list to identify an intended region of the PWSAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO29 message 225. In some cases, the network entity 105-a may provide country codes in a SIB that carries the PWS message 225, or in the PWS message 225. In some implementations, the UE 115-a (e.g., the NB-IoT UE) may be configured to store the country codes and the area codes (e.g., in one or more memories of the UE 115-a). In some examples, the UE 115-a may receive a NAS message that configures the UE 115-a with one or more country codes, area codes, or both.

[0101] In some implementations, the UE 115-a may be configured with scheduling information (e.g., periodicity, TBS size, and repetitions) for one or more PWS SIBs. For example, the UE 115-a may receive the scheduling information from the network entity 105-a, via one or more SIBs (e.g., SIB1 or SIB31) or via dedicated signaling by a PWS supporting network. In some cases, a MIB (or a SIB1) may provide an additional indication of whether the scheduling information provided in the one or more SIBs are valid (e.g., whether the scheduling information is activated or whether the scheduling information is to be used). Additionally, or alternatively, the MIB may also indicate whether the scheduling information has changed within a duration (e.g., in the last 300 seconds).

[0102] For example, if the UE 115-a is an NB-IoT UE, the system information window (e.g., Si-window) may begin at a subframe (e.g., subframe #0) in a radio frame according to formula (1), HSFN* 1024 + SFN) mod T = FLOOR x / 10) + offset (1) where T is the system information periodicity of the associated system information message, and offset is the offset of a start of the system information window (e.g., si- RadioFrameOffset). If a PWS SIB is broadcast (e.g., activated by a MIB), then the offset may be equal to 0. x may be defined according to formula (2), x = (n — 1) * w (2) where w is a system information window length (e.g., si-WindowLength), and n = s, where s is an integer value (e.g., 0, 1, 2, and so on). The network entity 105-a may refrain from scheduling SIBs in the system information window indicated by n.

[0103] In some implementations, the MIB or the SIB1 may indicate that PWS SIBs are to be provided with same scheduling information in a system information windowAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO30(e.g., determined by n in formula (2)). In such implementations, the network entity 105-a may refrain from broadcasting (e.g., outputting) other SIBs during the PWS delivery period in the system information window (e.g., determined by value ri). In some cases, the network entity 105-a may provide the PWS system information message scheduling in the SIB1. However, the network entity 105-a may refrain from transmitting a transport block (e.g., the resource may be used for another purpose). In some examples, the UE 115-a may ignore and may refrain from reading the system information message (e.g., the UE 115-a may not consider the system information message as a system information subframe). Instead, the UE 115-a may store the scheduling information (e.g., in one or more memories of the UE 115-a). In response to receiving a paging message or a downlink control information (DCI) notification, the UE 115-a may read the PWS SIB using the stored scheduling information.

[0104] FIG. 3 shows an example of a process flow 300 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The process flow 300 includes a UE 115 b, a network entity 105-b, and a network entity 105 c, which may be examples of the corresponding devices as described with respect to FIGs. 1 and 2. In the following description of the process flow 300, the operations between the UE 115 b, the network entity 105-b, and the network entity 105 c may be performed in a different order than the example order shown. Some operations may also be omitted from the process flow 300, and other operations may be added to the process flow 300. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

[0105] At 305, the UE 115-b may establish a wireless connection with the network entity 105-c, which may be associated with a cell (e.g., a cell 205 as described with reference to FIG. 2). In some implementations, the network entity 105-c may establish the wireless connection with the UE 115-b. In some examples, the UE 115-b may establish a second wireless connection with the network entity 105-d. In any case, the UE 115-b may be an example of an NB-IoT UE.

[0106] At 310, the UE 115-b may receive, via the wireless connection, a first message (e.g., an NB-IoT message) that indicates whether PWS notification isAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO31 supported by the cell. The first message may be an example of a PWS support message. For example, the UE 115-b may receive, via the wireless connection, a MIB that indicates that PWS notification is supported by the cell. Additionally, or alternatively, the MIB may indicate that one or more PWS messages are scheduled. The MIB may include scheduling information for one or more SIBs that include the one or more PWS messages

[0107] In some implementations, the UE 115-b may receive, via the wireless connection, a first SIB (e.g., SIB1) that includes a cell-specific indication (e.g., specific to the cell associated with the network entity 105-c). The cell-specific indication may indicate that PWS notification is supported by the cell. Additionally, or alternatively, the first SIB may include a PLMN-specific indication (e.g., specific to a PLMN associated with the network entity 105-c). The PLMN specific indication may indicate that PWS notification is supported by a PLMN (e.g., the PLMN associated with the network entity 105-c). In some cases, the first SIB (e.g., SIB1) may include an indication that PWS notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity 105-c. The one or more neighbor cells may be relatively near the cell associated with the network entity 105-c (e.g., bordering the cell) and may be in range to communicate with the UE 115-b.

[0108] In some cases, the UE 115-b may receive scheduling information for a public warning system message. For example, the UE 115-b may receive the scheduling information via a SIB or via dedicated signaling from the network entity 105-c. Additionally, or alternatively, the PWS support message may indicate that a set of PWS messages are provided with same scheduling information in a system information window. In some examples, the UE 115-b may receive a SIB that indicates scheduling information for the PWS message. In some implementations, the UE 115-b may monitor for the PWS message using the scheduling information only when a paging message or a DCI notification indicates that the PWS message is available.

[0109] At 315, the UE 115-b may receive the PW S message from the network entity 105-c (e.g., if the cell associated with the network entity 105-c supports PWS notification). The PWS message may indicate a warning regarding safety, disaster, or the like. In some cases, the UE 115-b may determine that a cell (e.g., the cell associated with the network entity 105-c) supports PWS notification based on one or moreAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO32 indications. The one or more indications may include one or more of PWS support information, scheduling information corresponding to PWS messages (e.g., information that schedules one or more PWS messages), information that indicates that the cell includes a new NB-IoT cell, or any combination thereof. In other words, if PWS scheduling information is provided, the UE 115-b may indicate that the cell supports PWS (e.g., through an implicit indication). In some cases, the one or more indications may be examples of a MIB, a SIB, or both.

[0110] At 320, the UE 115-b may receive one or more identifiers that indicate a location to which the PWS message pertains. The one or more identifiers may include country codes, telecommunication area codes, or both. In some cases, the UE 115-b may receive the one or more identifiers in the PWS message or in a SIB associated with the PWS message. At 325, the UE 115-b may receive a second message that configures the UE 115-b with an identifier set. Accordingly, the UE 115-b may determine that the PWS message pertains to the UE 115-b (e.g., that the PWS message carries a warning applicable for a user) based on a comparison of the one or more identifiers with the identifier set.[OHl] At 330-a, the UE 115-b may receive information indicative of a value of a reselection offset. For example, the UE 115-b may receive the information via dedicated signaling from the network entity 105-c. Similarly, at 330-b, the UE 115-b may receive information indicative of the value of the reselection offset in neighbor cell information from another network entity (e.g., the network entity 105-d). That is, the network entity 105-d may output neighbor cell information that indicates the value of the reselection offset for the cell associated with the network entity 105-c.

[0112] At 335, the UE 115-b may perform a cell selection procedure in accordance with a bias that is based on the reselection offset. For example, the UE 115-b may apply the reselection offset to a metric associated with the cell or with a frequency band based on the cell or the frequency band not supporting PWS notification. Thus, the UE 115-b may perform the cell selection procedure such that the cell which does not support PWS notification may have a lower priority. Instead, the UE 115-b may prioritize selection of cells that do support PWS notification. In some examples, the UE 115-b may apply a reselection offset to one or more metrics associated with cells or frequencies thatAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO33 support PWS such that the cells or frequencies have a higher priority in the selection procedure.

[0113] In some implementations, the UE 115-b may determine that a cell (e.g., the cell associated with the network entity 105-c) does not support PWS notification. In response, the UE 115-b may perform a cell selection procedure based on a set of one or more cells. The one or more cells may exclude the cell that does not support PWS notification for a time duration based on the cell not supporting PWS notification. For example, the UE 115-b may attempt to select a new cell that supports PWS notification for at least the time duration.

[0114] At 340, if the UE 115-b determines that a cell (e.g., the cell associated with the network entity 105-c) does not support PWS notification, the UE 115-b may perform one or more periodic search operations to identify and select a second cell that supports PWS notification. The UE 115-b may perform the one or more periodic search operations based on a cell prioritization scheme that prioritizes connection with cells that do support PWS notification. Such periodic search operations may result in selection of a cell associated with the network entity 105-d. Accordingly, at 345, the UE 115-b may receive, from the network entity 105-d via a wireless connection, a PWS message that indicates a warning for a user.

[0115] FIG. 4 shows a block diagram 400 of a device 405 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. The device 405, or one or more components of the device 405 (e.g., the receiver 410, the transmitter 415, the communications manager 420), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0116] The receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to PWS support in NB-IoT). Information may be passed on to otherAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO34 components of the device 405. The receiver 410 may utilize a single antenna or a set of multiple antennas.

[0117] The transmitter 415 may provide a means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to PWS support in NB-IoT). In some examples, the transmitter 415 may be co-located with a receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a set of multiple antennas.

[0118] The communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be examples of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0119] In some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0120] Additionally, or alternatively, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). IfAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO35 implemented in code executed by at least one processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0121] In some examples, the communications manager 420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 410, the transmitter 415, or both. For example, the communications manager 420 may receive information from the receiver 410, send information to the transmitter 415, or be integrated in combination with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.

[0122] The communications manager 420 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 420 is capable of, configured to, or operable to support a means for establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE. The communications manager 420 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first message (e.g., an NB-IoT message) that indicates whether PWS notification is supported by the cell.

[0123] By including or configuring the communications manager 420 in accordance with examples as described herein, the device 405 (e.g., at least one processor controlling or otherwise coupled with the receiver 410, the transmitter 415, the communications manager 420, or a combination thereof) may support techniques for PWS support in NB-IoT, which may result in reduced processing, increased processor compatibility and support for NB-IoT systems, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0124] FIG. 5 shows a block diagram 500 of a device 505 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO36The device 505 may be an example of aspects of a device 405 or a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0125] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to PWS support in NB-IoT). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0126] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to PWS support in NB-IoT). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0127] The device 505, or various components thereof, may be an example of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 520 may include a wireless connection component 525 a PWS support component 530, or any combination thereof. The communications manager 520 may be an example of aspects of a communications manager 420 as described herein. In some examples, the communications manager 520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiverAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO37510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0128] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. The wireless connection component 525 is capable of, configured to, or operable to support a means for establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE. The PWS support component 530 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0129] FIG. 6 shows a block diagram 600 of a communications manager 620 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520, or both, as described herein. The communications manager 620, or various components thereof, may be an example of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 620 may include a wireless connection component 625, a PWS support component 630, a PWS scheduling component 635, an offset application component 640, a cell selection component 645, a PWS non-support component 650, a search component 655, a location identifier component 660, an offset reception component 665, an identifier set component 670, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0130] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The wireless connection component 625 is capable of, configured to, or operable to support a means for establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE. The PWS support component 630 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO38

[0131] In some examples, to support receiving the first message, the PWS support component 630 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a MIB that indicates that PWS notification is supported by the cell.

[0132] In some examples, to support receiving the first message, the PWS support component 630 is capable of, configured to, or operable to support a means for determining that the cell supports PWS notification based on an indication, the indication including one or more of PWS support information, scheduling information corresponding to PWS messages, information that indicates that the cell includes a new NB-IoT cell, or any combination thereof.

[0133] In some examples, to support receiving the first message, the PWS scheduling component 635 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a MIB that indicates that one or more PWS messages are scheduled.

[0134] In some examples, the MIB includes scheduling information for one or more SIBs that include the one or more PWS messages.

[0135] In some examples, to support receiving the first message, the PWS support component 630 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification is supported by the cell.

[0136] In some examples, to support receiving the first message, the PWS support component 630 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first SIB that includes an indication, specific to a PLMN associated with the network entity, that PWS notification is supported by the PLMN.

[0137] In some examples, to support receiving the first message, the PWS support component 630 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first SIB that includes an indication that PWSAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO39 notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity.

[0138] In some examples, the offset application component 640 is capable of, configured to, or operable to support a means for applying a reselection offset to a metric associated with the cell or with a frequency band based at least in part on the cell or the frequency band not supporting PWS notification. In some examples, the cell selection component 645 is capable of, configured to, or operable to support a means for performing a cell selection procedure in accordance with a bias that is based at least in part on the reselection offset.

[0139] In some examples, the offset reception component 665 is capable of, configured to, or operable to support a means for receiving information indicative of a value of the reselection offset, where the information is received via dedicated signaling from the network entity or in neighbor cell information from another network entity.

[0140] In some examples, the PWS non-support component 650 is capable of, configured to, or operable to support a means for determining that the cell does not support PWS notification. In some examples, the cell selection component 645 is capable of, configured to, or operable to support a means for performing a cell selection procedure based at least in part on a set of one or more cells that excludes the cell for a time duration based at least in part on the cell not supporting PWS notification.

[0141] In some examples, the PWS non-support component 650 is capable of, configured to, or operable to support a means for determining that the cell does not support PWS notification. In some examples, the search component 655 is capable of, configured to, or operable to support a means for performing one or more periodic search operations to identify and select a second cell that supports PWS notification, where performance of the one or more periodic search operations is based at least in part on a cell prioritization scheme that prioritizes connection with cells that do support PWS notification.

[0142] In some examples, the location identifier component 660 is capable of, configured to, or operable to support a means for receiving one or more identifiers that indicate a location to which a PWS message pertains.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO40

[0143] In some examples, the one or more identifiers include country codes, telecommunication area codes, or both.

[0144] In some examples, the one or more identifiers are received in the PWS message or in a SIB associated with the PWS message.

[0145] In some examples, the identifier set component 670 is capable of, configured to, or operable to support a means for receiving a second message that configures the UE with an identifier set, where the UE determines that the PWS message pertains to the UE based at least in part on a comparison of the one or more identifiers with the identifier set.

[0146] In some examples, the PWS scheduling component 635 is capable of, configured to, or operable to support a means for receiving scheduling information for a public warning system message, where the scheduling information is received via a SIB or via dedicated signaling from the network entity.

[0147] In some examples, the first message indicates that a set of public warning system messages are provided with same scheduling information in a system information window.

[0148] In some examples, the PWS scheduling component 635 is capable of, configured to, or operable to support a means for receiving a SIB that indicates scheduling information for a public warning system message. In some examples, the PWS scheduling component 635 is capable of, configured to, or operable to support a means for monitoring for the public warning system message using the scheduling information only when a paging message or downlink control information notification indicates that the public warning system message is available.

[0149] FIG. 7 shows a diagram of a system 700 including a device 705 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The device 705 may be an example of or include components of a device 405, a device 505, or a UE 115 as described herein. The device 705 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 705 may include components for bi-directional voice and data communications including components for transmitting and receivingAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO41 communications, such as a communications manager 720, an input / output (I / O) controller, such as an I / O controller 710, a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

[0150] The I / O controller 710 may manage input and output signals for the device 705. The I / O controller 710 may also manage peripherals not integrated into the device 705. In some cases, the I / O controller 710 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 710 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 710 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as the at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0151] In some cases, the device 705 may include a single antenna. However, in some other cases, the device 705 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bi-directionally via the one or more antennas 725 using wired or wireless links as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 715 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725. The transceiver 715, or the transceiver 715 and one or more antennas 725, may be an example of a transmitter 415, a transmitter 515, a receiver 410, a receiver 510, or any combination thereof or component thereof, as described herein.

[0152] The at least one memory 730 may include random access memory (RAM) and read-only memory (ROM). The at least one memory 730 may store computer- readable, computer-executable, or processor-executable code, such as the code 735. TheAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO42 code 735 may include instructions that, when executed by the at least one processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 735 may not be directly executable by the at least one processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 730 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0153] The at least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 740. The at least one processor 740 may be configured to execute computer- readable instructions stored in a memory (e.g., the at least one memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting PWS support in NB-IoT). For example, the device 705 or a component of the device 705 may include at least one processor 740 and at least one memory 730 coupled with or to the at least one processor 740, the at least one processor 740 and the at least one memory 730 configured to perform various functions described herein.

[0154] In some examples, the at least one processor 740 may include multiple processors and the at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 740 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (whichAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO43 may include the at least one processor 740) and memory circuitry (which may include the at least one memory 730)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 740 or a processing system including the at least one processor 740 may be configured to, configurable to, or operable to cause the device 705 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 735 (e.g., processor-executable code) stored in the at least one memory 730 or otherwise, to perform one or more of the functions described herein.

[0155] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a means for establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE. The communications manager 720 is capable of, configured to, or operable to support a means for receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0156] By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 may support techniques for PWS support in NB-IoT, which may result in improved communication reliability, reduced latency, improved user experience related reduced processing, increased processor compatibility and support for NB-IoT systems, reduced power consumption, improved coordination between devices, improved utilization of processing capability, reduced signaling overhead, and more efficient utilization of communication resources, among other advantages.

[0157] In some examples, the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 715, the one or more antennas 725, or any combination thereof. Although the communications manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 720 may be supported by or performed by the at leastAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO44 one processor 740, the at least one memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the at least one processor 740 to cause the device 705 to perform various aspects of PWS support in NB-IoT as described herein, or the at least one processor 740 and the at least one memory 730 may be otherwise configured to, individually or collectively, perform or support such operations.

[0158] FIG. 8 shows a block diagram 800 of a device 805 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805, or one or more components of the device 805 (e.g., the receiver 810, the transmitter 815, the communications manager 820), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0159] The receiver 810 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0160] The transmitter 815 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 805. For example, the transmitter 815 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocolAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO45 stack). In some examples, the transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include or be coupled with a modem.

[0161] The communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be examples of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0162] In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0163] Additionally, or alternatively, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting,Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO46 individually or collectively, a means for performing the functions described in the present disclosure).

[0164] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0165] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for establishing a wireless connection with a UE, where the UE is an NB-IoT UE. The communications manager 820 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0166] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 (e.g., at least one processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) may support techniques for PWS support in NB-IoT, which may result in reduced processing, increased processor compatibility and support for NB-IoT systems, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0167] FIG. 9 shows a block diagram 900 of a device 905 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a device 805 or a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least oneAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO47 memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0168] The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0169] The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

[0170] The device 905, or various components thereof, may be an example of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 920 may include a wireless connection manager 925 a PWS support manager 930, or any combination thereof. The communications manager 920 may be an example of aspects of a communications manager 820 as described herein. In some examples, the communications manager 920, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise inAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO48 cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0171] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. The wireless connection manager 925 is capable of, configured to, or operable to support a means for establishing a wireless connection with a UE, where the UE is an NB-IoT UE. The PWS support manager 930 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0172] FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, may be an example of means for performing various aspects of PWS support in NB-IoT as described herein. For example, the communications manager 1020 may include a wireless connection manager 1025, a PWS support manager 1030, a PWS scheduling manager 1035, an offset manager 1040, a location identifier manager 1045, an identifier set manager 1050, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0173] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The wireless connection managerAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO491025 is capable of, configured to, or operable to support a means for establishing a wireless connection with a UE, where the UE is an NB-IoT UE. The PWS support manager 1030 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0174] In some examples, to support outputting the first message, the PWS support manager 1030 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a MIB that indicates that PWS notification is supported by the cell.

[0175] In some examples, to support outputting the first message, the PWS scheduling manager 1035 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a MIB that indicates that one or more PWS messages are scheduled.

[0176] In some examples, the MIB includes scheduling information for one or more SIBs that include the one or more PWS messages.

[0177] In some examples, to support outputting the first message, the PWS support manager 1030 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification is supported by the cell.

[0178] In some examples, to support outputting the first message, the PWS support manager 1030 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first SIB that includes an indication, specific to a PLMN associated with the network entity, that PWS notification is supported by the PLMN.

[0179] In some examples, to support outputting the first message, the PWS support manager 1030 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first SIB that includes an indication that PWS notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO50

[0180] In some examples, the offset manager 1040 is capable of, configured to, or operable to support a means for outputting information indicative of a value of a reselection offset, where the reselection offset is associated with the cell and biases the cell during a cell selection procedure, where the bias is based at least in part on the cell not supporting PWS notification.

[0181] In some examples, the location identifier manager 1045 is capable of, configured to, or operable to support a means for outputting one or more identifiers that indicate a location to which a PWS message pertains.

[0182] In some examples, the one or more identifiers include country codes, telecommunication area codes, or both.

[0183] In some examples, the one or more identifiers are included in the PWS message or in a SIB associated with the PWS message.

[0184] In some examples, the identifier set manager 1050 is capable of, configured to, or operable to support a means for outputting a second message that configures the UE with an identifier set that includes one or more locations to facilitate comparison of the one or more identifiers with the identifier set.

[0185] In some examples, the PWS scheduling manager 1035 is capable of, configured to, or operable to support a means for outputting scheduling information for a public warning system message, where the scheduling information is received via a SIB or via dedicated signaling from the network entity.

[0186] In some examples, the first message indicates that a set of public warning system messages are provided with same scheduling information in a system information window.

[0187] In some examples, the PWS scheduling manager 1035 is capable of, configured to, or operable to support a means for outputting a SIB that indicates scheduling information for a public warning system message, where the scheduling information is usable to monitor for the public warning system message only when a paging message or downlink control information notification indicates that the public warning system message is available.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO51

[0188] FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of or include components of a device 805, a device 905, or a network entity 105 as described herein. The device 1105 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support outputting and obtaining communications, such as a communications manager 1120, a transceiver 1110, one or more antennas 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1140).

[0189] The transceiver 1110 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1110 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1115, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1115, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1115 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1115 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operationsAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO52 based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1110, or the transceiver 1110 and the one or more antennas 1115, or the transceiver 1110 and the one or more antennas 1115 and one or more processors or one or more memory components (e.g., the at least one processor 1135, the at least one memory 1125, or both), may be included in a chip or chip assembly that is installed in the device 1105. In some examples, the transceiver 1110 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0190] The at least one memory 1125 may include RAM, ROM, or any combination thereof. The at least one memory 1125 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1130. The code 1130 may include instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non -transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by a processor of the at least one processor 1135 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1125 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1135 may include multiple processors and the at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0191] The at least one processor 1135 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, oneAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO53 or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1135. The at least one processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1125) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting PWS support in NB-IoT). For example, the device 1105 or a component of the device 1105 may include at least one processor 1135 and at least one memory 1125 coupled with one or more of the at least one processor 1135, the at least one processor 1135 and the at least one memory 1125 configured to perform various functions described herein. The at least one processor 1135 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1130) to perform the functions of the device 1105. The at least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as within one or more of the at least one memory 1125).

[0192] In some examples, the at least one processor 1135 may include multiple processors and the at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1135 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1135) and memory circuitry (which may include the at least one memory 1125)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1135 or a processing system including the at least one processor 1135 may be configured to, configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein. Further, asAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO54 described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1125 or otherwise, to perform one or more of the functions described herein.

[0193] In some examples, a bus 1140 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1105, or between different components of the device 1105 that may be co-located or located in different locations (e.g., where the device 1105 may refer to a system in which one or more of the communications manager 1120, the transceiver 1110, the at least one memory 1125, the code 1130, and the at least one processor 1135 may be located in one of the different components or divided between different components).

[0194] In some examples, the communications manager 1120 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1120 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1120 may manage communications with one or more other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1120 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0195] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for establishing a wireless connection with a UE, where the UE is an NB-IoT UE. The communications manager 1120 is capable of, configured to, or operable to support a means for outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO55

[0196] By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 may support techniques for PWS support in NB-IoT, which may result in improved communication reliability, reduced latency, improved user experience related reduced processing, increased processor compatibility and support for NB-IoT systems, reduced power consumption, improved coordination between devices, improved utilization of processing capability, reduced signaling overhead, and more efficient utilization of communication resources, among other advantages.

[0197] In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1110, the one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the transceiver 1110, one or more of the at least one processor 1135, one or more of the at least one memory 1125, the code 1130, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1135, the at least one memory 1125, the code 1130, or any combination thereof). For example, the code 1130 may include instructions executable by one or more of the at least one processor 1135 to cause the device 1105 to perform various aspects of PWS support in NB-IoT as described herein, or the at least one processor 1135 and the at least one memory 1125 may be otherwise configured to, individually or collectively, perform or support such operations.

[0198] FIG. 12 shows a flowchart illustrating a method 1200 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO56

[0199] At 1205, the method may include establishing a wireless connection with a network entity associated with a cell, where the UE is an NB-IoT UE. The operations of 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by a wireless connection component 625 as described with reference to FIG. 6.

[0200] At 1210, the method may include receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell. The operations of 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by a PWS support component 630 as described with reference to FIG. 6.

[0201] FIG. 13 shows a flowchart illustrating a method 1300 that supports PWS support in NB-IoT in accordance with one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1300 may be performed by a network entity as described with reference to FIGs. 1 through 3 and 8 through 11. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0202] At 1305, the method may include establishing a wireless connection with a UE, where the UE is an NB-IoT UE. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a wireless connection manager 1025 as described with reference to FIG. 10.

[0203] At 1310, the method may include outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a PWS support manager 1030 as described with reference to FIG. 10.

[0204] The following provides an overview of aspects of the present disclosure:Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO57

[0205] Aspect 1 : A method for wireless communications at a UE, comprising: establishing a wireless connection with a network entity associated with a cell, wherein the UE is an NB-IoT UE; and receiving, via the wireless connection, a first message that indicates whether PWS notification is supported by the cell.

[0206] Aspect 2: The method of aspect 1, wherein receiving the first message comprises: receiving, via the wireless connection, a MIB that indicates that PWS notification is supported by the cell.

[0207] Aspect 3 : The method of any of aspects 1 through 2, wherein receiving the first message comprises: receiving, via the wireless connection, a MIB that indicates that one or more PWS messages are scheduled.

[0208] Aspect 4: The method of aspect 3, wherein the MIB includes scheduling information for one or more SIBs that include the one or more PWS messages.

[0209] Aspect 5 : The method of any of aspects 1 through 4, wherein receiving the first message comprises: receiving, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification is supported by the cell.

[0210] Aspect 6: The method of any of aspects 1 through 5, wherein receiving the first message comprises: receiving, via the wireless connection, a first SIB that includes an indication, specific to a PLMN associated with the network entity, that PWS notification is supported by the PLMN.

[0211] Aspect 7: The method of any of aspects 1 through 6, wherein receiving the first message comprises: receiving, via the wireless connection, a first SIB that includes an indication that PWS notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity.

[0212] Aspect 8: The method of any of aspects 1 through 7, further comprising: applying a reselection offset to a metric associated with the cell or with a frequency band based at least in part on the cell or the frequency band not supporting PWS notification; and performing a cell selection procedure in accordance with a bias that is based at least in part on the reselection offset.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO58

[0213] Aspect 9: The method of aspect 8, further comprising: receiving information indicative of a value of the reselection offset, wherein the information is received via dedicated signaling from the network entity or in neighbor cell information from another network entity.

[0214] Aspect 10: The method of any of aspects 1 through 9, further comprising: determining that the cell does not support PWS notification; and performing a cell selection procedure based on a set of one or more cells that excludes the cell for a time duration based at least in part on the cell not supporting PWS notification.

[0215] Aspect 11 : The method of any of aspects 1 through 10, further comprising: determining that the cell does not support PWS notification; and performing one or more periodic search operations to identify and select a second cell that supports PWS notification, wherein performance of the one or more periodic search operations is based at least in part on a cell prioritization scheme that prioritizes connection with cells that do support PWS notification.

[0216] Aspect 12: The method of any of aspects 1 through 11, further comprising: receiving one or more identifiers that indicate a location to which a PWS message pertains.

[0217] Aspect 13: The method of aspect 12, wherein the one or more identifiers include country codes, telecommunication area codes, or both.

[0218] Aspect 14: The method of any of aspects 12 through 13, wherein the one or more identifiers are received in the PWS message or in a SIB associated with the PWS message.

[0219] Aspect 15: The method of any of aspects 12 through 14, further comprising: receiving a second message that configures the UE with an identifier set, wherein the UE determines that the PWS message pertains to the UE based on a comparison of the one or more identifiers with the identifier set.

[0220] Aspect 16: The method of any of aspects 1 through 15, further comprising: receiving scheduling information for a PWS message, wherein the scheduling information is received via a SIB or via dedicated signaling from the network entity.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO59

[0221] Aspect 17: The method of any of aspects 1 through 16, wherein the first message indicates that a set of PWS messages are provided with same scheduling information in a system information window.

[0222] Aspect 18: The method of any of aspects 1 through 17, further comprising: receiving a SIB that indicates scheduling information for a PWS message; and monitoring for the PWS message using the scheduling information only when a paging message or DCI notification indicates that the PWS message is available.

[0223] Aspect 19: A method for wireless communications at a network entity, comprising: establishing a wireless connection with a UE, wherein the UE is an NB-IoT UE; and outputting, via the wireless connection, a first message that indicates whether PWS notification is supported by a cell associated with the network entity.

[0224] Aspect 20: The method of aspect 19, wherein outputting the first message comprises: outputting, via the wireless connection, a MIB that indicates that PWS notification is supported by the cell.

[0225] Aspect 21 : The method of any of aspects 19 through 20, wherein outputting the first message comprises: outputting, via the wireless connection, a MIB that indicates that one or more PWS messages are scheduled.

[0226] Aspect 22: The method of aspect 21, wherein the MIB includes scheduling information for one or more SIBs that include the one or more PWS messages.

[0227] Aspect 23: The method of any of aspects 19 through 22, wherein outputting the first message comprises: outputting, via the wireless connection, a first SIB that includes an indication, specific to the cell associated with the network entity, that PWS notification is supported by the cell.

[0228] Aspect 24: The method of any of aspects 19 through 23, wherein outputting the first message comprises: outputting, via the wireless connection, a first SIB that includes an indication, specific to a PLMN associated with the network entity, that PWS notification is supported by the PLMN.

[0229] Aspect 25: The method of any of aspects 19 through 24, wherein outputting the first message comprises: outputting, via the wireless connection, a first SIB thatAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO60 includes an indication that PWS notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity.

[0230] Aspect 26: The method of any of aspects 19 through 25, further comprising: outputting information indicative of a value of a reselection offset, wherein the reselection offset is associated with the cell and biases the cell during a cell selection procedure, wherein the bias is based at least in part on the cell not supporting PWS notification.

[0231] Aspect 27: The method of any of aspects 19 through 26, further comprising: outputting one or more identifiers that indicate a location to which a PWS message pertains.

[0232] Aspect 28: The method of aspect 27, wherein the one or more identifiers include country codes, telecommunication area codes, or both.

[0233] Aspect 29: The method of any of aspects 27 through 28, wherein the one or more identifiers are included in the PWS message or in a SIB associated with the PWS message.

[0234] Aspect 30: The method of any of aspects 27 through 29, further comprising: outputting a second message that configures the UE with an identifier set that includes one or more locations to facilitate comparison of the one or more identifiers with the identifier set.

[0235] Aspect 31 : The method of any of aspects 19 through 30, further comprising: outputting scheduling information for a PWS message, wherein the scheduling information is received via a SIB or via dedicated signaling from the network entity.

[0236] Aspect 32: The method of any of aspects 19 through 31, wherein the first message indicates that a set of PWS messages are provided with same scheduling information in a system information window.

[0237] Aspect 33: The method of any of aspects 19 through 32, further comprising: outputting a SIB that indicates scheduling information for a PWS message, wherein the scheduling information is usable to monitor for the PWS message only when a paging message or DCI notification indicates that the PWS message is available.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO61

[0238] Aspect 34: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 18.

[0239] Aspect 35: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 18.

[0240] Aspect 36: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 18.

[0241] Aspect 37: A network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 19 through 33.

[0242] Aspect 38: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 19 through 33.

[0243] Aspect 39: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 19 through 33.

[0244] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0245] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO62

[0246] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0247] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0248] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0249] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of aAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO63 computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0250] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0251] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of thoseAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO64 nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0252] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0253] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0254] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may beAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO65 implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0255] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Docket No. PY2778GR.WO (114958.4688)

Claims

Qualcomm Ref. No. 2500218WO66CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: establish a wireless connection with a network entity associated with a cell; receive, via the wireless connection, a first message indicative of whether public warning system notification is supported by the cell, wherein the first message comprises a narrowband internet of things (NB-IoT) message; and performing one or more signaling operations in accordance with whether the public warning system notification is supported by the cell.

2. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive, via the wireless connection, a master information block that indicates that public warning system notification is supported by the cell.

3. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive, via the wireless connection, a master information block that indicates that one or more public warning system messages are scheduled.

4. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: determine that the cell supports public warning system (PWS) notification based at least in part on an indication, the indication comprising one or more of PWS support information, scheduling information corresponding to PWSAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO67 messages, information that indicates that the cell comprises a new NB-IoT cell, or any combination thereof.

5. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive, via the wireless connection, a first system information block that includes an indication, specific to the cell associated with the network entity, that public warning system notification is supported by the cell.

6. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive, via the wireless connection, a first system information block that includes an indication, specific to a public land mobile network associated with the network entity, that public warning system notification is supported by the public land mobile network.

7. The UE of claim 1, wherein, to receive the first message, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive, via the wireless connection, a first system information block that includes an indication that public warning system notification is supported by one or more neighbor cells that neighbor the cell associated with the network entity.

8. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: apply a reselection offset to a metric associated with the cell or with a frequency band based at least in part on the cell or the frequency band not supporting public warning system notification; and perform a cell selection procedure in accordance with a bias that is based at least in part on the reselection offset.

9. The UE of claim 8, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO68 receive information indicative of a value of the reselection offset, wherein the information is received via dedicated signaling from the network entity or in neighbor cell information from another network entity.

10. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine that the cell does not support public warning system notification; and perform a cell selection procedure based on a set of one or more cells that excludes the cell for a time duration based at least in part on the cell not supporting public warning system notification.

11. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine that the cell does not support public warning system notification; and perform one or more periodic search operations to identify and select a second cell that supports public warning system notification, wherein performance of the one or more periodic search operations is based at least in part on a cell prioritization scheme that prioritizes connection with cells that do support public warning system notification.

12. The UE of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: determine that the cell is an acceptable cell, wherein performance of the one or more periodic search operations based at least in part on the cell prioritization scheme is based at least in part on the UE being in communications with the acceptable cell.

13. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive one or more identifiers that indicate a location to which a public warning system message pertains.Attorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO6914. The UE of claim 12, wherein the one or more identifiers include country codes, telecommunication area codes, or both, and wherein the one or more identifiers are received in the public warning system message or in a system information block associated with the public warning system message.

15. The UE of claim 12, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive a second message that configures the UE with an identifier set, wherein the UE determines that the public warning system message pertains to the UE based on a comparison of the one or more identifiers with the identifier set.

16. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive scheduling information for a public warning system message, wherein the scheduling information is received via a system information block or via dedicated signaling from the network entity.

17. The UE of claim 1, wherein the first message indicates that a set of public warning system messages are provided with same scheduling information in a system information window.

18. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive a system information block that indicates scheduling information for a public warning system message; and monitor for the public warning system message using the scheduling information only when a paging message or downlink control information notification indicates that the public warning system message is available.

19. A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to: establish a wireless connection with a user equipment (UE); andAttorney Docket No. PY2778GR.WO (114958.4688)Qualcomm Ref. No. 2500218WO70 output, via the wireless connection, a first message indicative of whether public warning system notification is supported by a cell associated with the network entity, wherein the first message comprises a narrowband internet of things (NB-IoT) message.

20. A method for wireless communications at a user equipment (UE), comprising: establishing a wireless connection with a network entity associated with a cell; and receiving, via the wireless connection, a first message indicative of whether public warning system notification is supported by the cell, wherein the first message comprises a narrowband internet of things (NB-IoT) message.Attorney Docket No. PY2778GR.WO (114958.4688)

Images