Robust notification alerts for ntn

Abstract

RNA messages for UEs in an NTN are described. An apparatus is configured to receive, from a network function, an indication upon a paging failure associated with a paging message for a UE in an NTN. The apparatus is configured to provide, to at least one AMF, an RNA message for the UE. The RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service.

Description

ROBUST NOTIFICATION ALERTS FOR NTNCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of Greece Patent Application Serial No. 20240100520, entitled “ROBUST NOTIFICATION ALERTS FOR NTN” and filed on July 25, 2024, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to communication systems, and more particularly, to communication systems utilizing non-terrestrial networks (NTNs).INTRODUCTION

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5GNR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be, or may comprise, a network entity or network service (e.g., a robust notification server / service or a robust notification alert server / service (RNS)). The apparatus is configured to receive, from a network function, an indication upon a paging failure associated with a paging message for a user equipment (UE) in a non-terrestrial network (NTN). The apparatus is configured to provide, to at least one access and mobility function (AMF), a robust notification alert (RNA) message for the UE, where the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service.

[0007] In the aspect, the method includes receiving, from a network function, an indication upon a paging failure associated with a paging message for a UE in an NTN. The method also includes providing, to at least one AMF, an RNA message for the UE, where the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service.

[0008] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be, or may comprise, an access and mobility function (AMF). The apparatus is configured to receive an indication of data for transmission to at least one UE. The apparatus is configured to provide, to a radio access network (RAN) node in an NTN, one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel. The apparatus is configured to receive, from a network service, an RNA message for oneor more UEs. The apparatus is configured to provide, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages.

[0009] In the aspect, the method includes receiving an indication of data for transmission to at least one UE. The method includes providing, to a RAN node in an NTN, one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel. The method includes receiving, from a network service, an RNA message for one or more UEs. The method includes providing, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages.

[0010] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be, or may comprise, a network entity (e.g., a network / RAN node such as a base station, gNB, sNB, eNB, etc.) of an NTN. The apparatus is configured to receive one or more paging messages in a first container type for paging one or more user UEs. The apparatus is configured to transmit the one or more paging messages on a first channel that are intended for one or more UEs. The apparatus is configured to receive an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. The apparatus is configured to transmit the RNA message for said the one or more UEs on the second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels.

[0011] In the aspect, the method includes receiving one or more paging messages in a first container type for paging one or more UEs. The method includes transmitting the one or more paging messages on a first channel that are intended for one or more UEs. The method includes receiving an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. The method includes transmitting the RNA message for said the one or more UEs onthe second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels.

[0012] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be, or may comprise, a user equipment (UE). The apparatus is configured to enter a connection management (CM) idle mode. The apparatus is configured to transmit an indication of support for an RNA. The apparatus is configured to monitor for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages.

[0013] In the aspect, the method includes entering a CM idle mode. The method includes transmitting an indication of support for an RNA. The method includes monitoring for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages.

[0014] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG. l is a diagram illustrating an example of a wireless communications system and an access network.

[0016] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0017] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

[0018] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0019] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

[0020] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0021] FIG. 4 is a diagram illustrating an example environment that may support wireless communication.

[0022] FIGs. 5A, 5B, and 5C each illustrate an example network architecture capable of supporting NTN access.

[0023] FIG. 6 is a call flow diagram for wireless communications, in accordance with various aspects of the present disclosure.

[0024] FIG. 7 is a call flow diagram for wireless communications, in accordance with various aspects of the present disclosure.

[0025] FIG. 8 is a call flow diagram for wireless communications, in accordance with various aspects of the present disclosure.

[0026] FIG. 9 is a call flow diagram for wireless communications, in accordance with various aspects of the present disclosure.

[0027] FIG. 10 is diagram illustrating an example of a protocol stack with an RNA protocol for RNA messaging, in accordance with various aspects of the present disclosure.

[0028] FIG. 11 is a flowchart of a method of wireless communication.

[0029] FIG. 12 is a flowchart of a method of wireless communication.

[0030] FIG. 13 is a flowchart of a method of wireless communication.

[0031] FIG. 14 is a flowchart of a method of wireless communication.

[0032] FIG. 15 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.

[0033] FIG. 16 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0034] FIG. 17 is a diagram illustrating an example of a hardware implementation for an example network entity.DETAILED DESCRIPTION

[0035] Wireless communication networks may be designed to support communications between network entities (e.g., network nodes such as base stations, eNBs, gNBs, etc.; entities in a core network) and UEs. In some aspects, a UE may be in a coverage areaof a terrestrial network, and may be served by the terrestrial network. In some aspects, a UE may be outside of coverage of a terrestrial network, and may be within coverage of an NTN, which facilitates wireless communications of the UE.

[0036] However, the UE may be in an environment / location such that the NTN coverage of the UE is poor. For instance, if the UE goes into deep coverage for the NTN or enters a connection management (CM) idle mode (CM IDLE), the UE may be unable to receive or respond to paging requests for mobile terminated (MT) multimedia telephony (MMTEL). In such scenarios, the UE may not receive the attempted communications and / or may not receive a notification of the attempted communication.

[0037] Various aspects relate generally to communication systems utilizing NTNs. Some aspects more specifically relate to RNA messages for UEs in an NTN. In some examples, a network service (e.g., an RNS) may receive, from a network function (e.g., an Internet Protocol multimedia subsystem (IMS)), an indication upon a paging failure associated with a paging message for a UE in a NTN. In response to the indication, the network service may provide, to at least one AMF, an RNA message for the UE, where the notification message carries at least some information (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like) not included in the paging message and notifies the UE at least for the missed paging attempt for the network service. In some examples, an AMF may receive an indication of data for transmission to at least one UE, and provide, to a RAN node in an NTN, one or more paging messages for the UE in a first container type associated with delivery on a first channel. The AMF may receive, from a network service, an RNA message for one or more UEs, and provide, to the RAN node, the RNA message for the one or more UEs in a second container type associated with delivery on a second channel that is different than the first channel for the one or more paging messages. In some examples, a network node of an NTN may receive one or more paging messages in a first container type for paging one or more UEs, and transmit the one or more paging messages on a first channel that are intended for one or more UEs. The network node of the NTN may receive an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message a second channel that is different than the first channel, and transmit the RNA message for said the one or more UEs on thesecond channel that is different than the first channel, where the network node has a first logical channel for paging and a second logical channel for RNA messages, and where the first logical channel and the second logical channel have a different mapping to physical channels. In some examples, a UE may enter a CM idle mode, transmit an indication of support for an RNA, and monitor for an RNA message on a second channel that is different than a first channel for paging messages, where the notification message carries at least some information not included in the paging messages (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like).

[0038] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by enabling an RNS to provide RNA messages, the described techniques can be used to provide a UE with alert messaging when in deep coverage of an NTN. In some examples, by enabling RNS interactions with an AMF, the described techniques can be used to provide a UE with alert messaging securely and in varied UE environment scenarios. In such examples, by extending beyond MT short message service (SMS) messaging over non-access stratum (NAS) for paging failures due to deep coverage, the described techniques can be used to enable an RNS to forward reachability requests and payloads directly to an AMF. In some examples, by enabling RNS interactions with an IMS, the described techniques can be used to provide a UE with alert messaging from an RNS that includes missed communication details.

[0039] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0040] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware,computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0041] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0042] Accordingly, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer- readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0043] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / oruse cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip- level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

[0044] Deployment of communication systems, such as 5GNR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0045] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0046] Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O- RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0047] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both). A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an Fl interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate withrespective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

[0048] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near- RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0049] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an 0-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

[0050] The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation,demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3 GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.

[0051] Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0052] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 111, via an 01 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an 01 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

[0053] The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near- RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

[0054] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0055] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to asforward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to X MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Fx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

[0056] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0057] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0058] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0059] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into midband frequencies. In addition, higher frequency bands are currently being explored to extend 5GNR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0060] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0061] Some wireless communication may be exchanged between a UE 104 and a nonterrestrial network (NTN) device that may include an aerial device or space vehicle, such as a satellite 170. Additional aspects of wireless communication via an NTN are described in connection with FIG. 4 and FIGs. 5A-5C.

[0062] The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or morereceive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0063] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, sNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and / or an RU. The set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).

[0064] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities, such as a robust notification server / service (RNS) 167. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g.,emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position / location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and / or other systems / signals / sensors. The RNS 167 delivers RNAs to the UE 104 via interactions with the AMF 161, the base station 102 (or a portion thereof), and / or an IMS, as described herein.

[0065] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as ina device constellation arrangement. One or more of these devices may collectively access the network and / or individually access the network.

[0066] Referring again to FIG. 1, in certain aspects, the UE 104 may have an RNA component 198 (“component 198”) that may be configured to enter a connection management (CM) idle mode. The component 198 may be configured to transmit an indication of support for an RNA. The component 198 may be configured to monitor for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages. In certain aspects, the base station 102 (e.g., also a network / RAN node, generally, may have an RNA component 199 (“component 199”) that may be configured to receive one or more paging messages in a first container type for paging one or more user UEs. The component 199 may be configured to transmit the one or more paging messages on a first channel that are intended for one or more UEs. The component 199 may be configured to receive an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. The component 199 may be configured to transmit the RNA message for said the one or more UEs on the second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels. In certain aspects, a network service (e.g., an RNS, such as the RNS 167) and / or an AMF, such as the AMF 161, may also include or comprise an instance of the component 199. In the context of a network service, the component 199 may be configured to receive, from a network function, an indication upon a paging failure associated with a paging message for a UE in an NTN. The component 199 may be configured to provide, to at least one AMF, an RNA message for the UE, where the RNA message carries at least some information not included in the a paging message and notifies the UE at least for a missed paging attempt for the network service. In the context of an AMF, the component 199 may be configured to receive an indication of data for transmission to at least one UE. The component 199 may be configured to provide, to a RAN node in an NTN, one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel.The component 199 may be configured to receive, from a network service, an RNA message for one or more UEs. The component 199 may be configured to provide, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages. Aspects for RNA messages for UEs in an NTN improve on / remediate the issues noted herein, and a wireless communication system with satellite access, e.g., via an NTN, is enabled to provide a mechanism for the network to notify a UE of a missed incoming MMTEL MT call(s) when normal paging fails, and accordingly, the user may be informed and take an appropriate action(s) (e.g., move to better coverage for successful call completion or take other actions). Aspects herein enable providing a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages, enable providing a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF (where an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc.), and enable providing a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0067] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slotformats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi- statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

[0068] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may scale with 1 / SCS.Table 1: Numerology, SCS, and CP

[0069] For normal CP (14 symbols / slot), different numerologies p. 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology p, there are 14 symbols / slot and 2^ slots / subframe. The subcarrier spacing may be equal to 2 * 15 kHz, where is the numerology 0 to 4. As such, the numerology p=0 has a subcarrier spacing of 15 kHz and the numerology p=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology p=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

[0070] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0071] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0072] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and / or lower frequencies across the channel bandwidth. A primarysynchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

[0073] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequencydependent scheduling on the UL.

[0074] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK(NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0075] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0076] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallelstreams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

[0077] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0078] The controller / processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly,deciphering, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0079] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0080] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0081] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0082] The controller / processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0083] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the component 198 of FIG. 1.

[0084] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the component 199 of FIG. 1.

[0085] In some examples, a UE may communicate with a terrestrial network. FIG. 4 is a diagram illustrating an example environment 400 that may support wireless communication including aspects of a terrestrial network and a non-terrestrial network, as presented herein. In the illustrated example of FIG. 4, a terrestrial network includes a base station 402 that provides coverage to UEs, such as an example UE 404, located within a coverage area 410 for the terrestrial network. The base station 402 may facilitate communication between the UE 404 and a network node 406. Aspects of the network node 406 may be implemented by a core network, such as the example core network 120 of FIG. 1.

[0086] In some examples, a UE may transmit or receive satellite-based communication (e.g., via an Iridium-like satellite communication system or a satellite-based 3 GPP NTN). For example, an aerial device 422 (which may also be referred to as a space vehicle (SV)) may provide coverage to UEs, such as an example UE 424, located within a coverage area 420 for the aerial device 422. In some examples, the aerial device 422 may communicate with the network node 406 through a feeder link 426 established between the aerial device 422 and a gateway 428 in order to provide service to the UE 424 within the coverage area 420 of the aerial device 422 via a service link 430. The feeder link 426 may include a wireless link between the aerial device 422 and the gateway 428. The service link 430 may include a wireless link between the aerial device 422 and the UE 424. In some examples, the gateway 428 may communicate directly with the network node 406. In some examples, the gateway 428 may communicate with the network node 406 via the base station 402.

[0087] In some aspects, the aerial device 422 may be configured to communicate directly with the gateway 428 via the feeder link 426. The feeder link 426 may include a radio link that provides wireless communication between the aerial device 422 and the gateway 428.

[0088] In other aspects, the aerial device 422 may communicate with the gateway 428 via one or more other aerial devices. For example, the aerial device 422 and a second aerial device 432 may be part of a constellation of satellites (e.g., aerial devices) that communicate via inter-satellite links (ISLs). In the example of FIG. 4, the aerial device 422 may establish an ISL 434 with the second aerial device 432. The ISL 434 may be a radio interface or an optical interface and operate in the RF frequency or optical bands, respectively. The second aerial device 432 may communicate with the gateway 428 via a second feeder link 436.

[0089] In some examples, the aerial device 422 and / or the second aerial device 432 may include an aerial device, such as an unmanned aircraft system (UAS), a balloon, a drone, an unmanned aerial vehicle (UAV), etc. Examples of a UAS platform that may be used for NTN communication include systems including Tethered UAS (TUA), Lighter Than Air UAS (LTA), Heavier Than Air UAS (HTA), and High Altitude Platforms (HAPs). In some examples, the aerial device 422 and / or the second aerial device 432 may include a satellite or a space-borne vehicle placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), Geostationary Earth Orbit (GEO), or High Elliptical Orbit (HEO).

[0090] In some aspects, the aerial device 422 and / or the second aerial device 432 may implement a transparent payload. For example, after receiving a signal, a transparent aerial device may have the ability to change the frequency carrier of the signal, perform RF filtering on the signal, and amplify the signal before outputting the signal. In such aspects, the signal output by the transparent aerial device may be a repeated signal in which the waveform of the output signal is unchanged relative to the received signal.

[0091] In other aspects, the aerial device 422 and / or the second aerial device 432 may implement a regenerative payload. For example, a regenerative aerial device may have the ability to perform all of or part of the base station functions, such as transforming and amplifying a received signal via on-board processing before outputting a signal. In some such aspects, transformation of the received signal may refer to digital processing that may include demodulation, decoding, switching and / or routing, re-encoding, re-modulation, and / or filtering of the received signal.

[0092] In examples in which the aerial device implements a transparent payload, the transparent aerial device may communicate with the base station 402 via the gateway428. In some such examples, the base station 402 may facilitate communication between the gateway 428 and the network node 406. In examples in which the aerial device implements a regenerative payload, the regenerative aerial device may have an on-board base station. In some such examples, the on-board base station may communicate with the network node 406 via the gateway 428. In some examples, the on-board base station may include a DU and a CU, such as the DU 130 and the CU 110 of FIG. 1. In some examples, the on-board base station may include a DU that is in communication with a corresponding CU that is on the ground.

[0093] FIG. 5A illustrates an example network architecture 500 capable of supporting NTN access, as presented herein. FIG. 5 A illustrates a network architecture with transparent payloads. The network architecture 500 of FIG. 5 A includes a UE 505, an NTN device 502, an NTN gateway 504 (sometimes referred to as “gateways,” “earth stations,” or “ground stations”), and a base station 506 having the capability to communicate with the UE 505 via the NTN device 502. The NTN device 502, the NTN gateway 504, and the base station 506 may be part of a RAN 512 (e.g., an NG-RAN).

[0094] The base station 506 may be a network node that corresponds to the network device / the base station 310 of FIG. 3. The network architecture 500 is illustrated as further including a core network 510. In some aspects, the core network 510 may correspond to the core network 190 described in connection with FIG. 1. The core network 510 may be public land mobile networks (PLMN). In some aspects, the core network may be a 5GCN. Connections in the network architecture 500 with transparent payloads illustrated in FIG. 5A, allow the base station 506 to access the NTN gateway 504 and the core network 510. In some examples, the base station 506 may be shared by multiple PLMNs. Similarly, the NTN gateway 504 may be shared by more than one base station.

[0095] The base station 506 may be referred to by other names such as a gNB, a “satellite node”, a satellite NodeB (sNB), “satellite access node”, etc. The base station 506 may not be the same as terrestrial network gNBs, but may be based on a terrestrial network base station with additional capability. For example, the base station 506 may terminate the radio interface and associated radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505 via the NTN device 502 and the NTN gateway 504. The base station 506 may also support signaling connections and voice and data bearers to the UE 505 and maysupport handover of the UE 505 between different radio cells for the NTN device 502, between different NTN devices and / or between different base stations. The base station 506 may be configured to manage moving radio beams (e.g., for airborne vehicles and / or non-geostationary (non-GEO) devices) and associated mobility of the UE 505. The base station 506 may assist in the handover (or transfer) of the NTN device 502 between different NTN gateways or different base stations. In some examples, the base station 506 may be separate from the NTN gateway 504, e.g., as illustrated in the example of FIG. 5A. In other examples, the base station 506 may include or may be combined with one or more NTN gateways, e.g., using a split architecture. For example, with a split architecture, the base station 506 may include a Central Unit (CU), such as the example CU 110 of FIG. 1, and the NTN gateway 504 may include or act as Distributed Unit (DU), such as the example DU 130 of FIG. 1. The base station 506 may be fixed on the ground with transparent payload operation. In one implementation, the base station 506 may be physically combined with, or physically connected to, the NTN gateway 504 to reduce complexity and cost.

[0096] The NTN gateway 504 may be shared by more than one base station and may communicate with the UE 505 via the NTN device 502. The NTN gateway 504 may be dedicated to one associated constellation of NTN devices. The NTN gateway 504 may be included within the base station 506, e.g., as a base station-DU within the base station 506. The NTN gateway 504 may communicate with the NTN device 502 using control and user plane protocols. The control and user plane protocols between the NTN gateway 504 and the NTN device 502 may: (i) establish and release the NTN gateway 504 to the NTN device 502 communication links, including authentication and ciphering; (ii) update NTN device software and firmware; (iii) perform NTN device Operations and Maintenance (O&M); (iv) control radio beams (e.g., direction, power, on / off status) and mapping between radio beams and NTN gateway UL and DL payload; and / or (v) assist with handoff of the NTN device 502 or radio cell to another NTN gateway.

[0097] Support of transparent payloads with the network architecture 500 shown in FIG. 5A may enable the core network 510 to treat a satellite RAT as a new type of RAT with longer delay, reduced bandwidth and / or higher error rate. Consequently, there may be some impact to PDU session establishment and mobility management (MM) and connection management (CM) procedures. The base station 506 may assistassignment and transfer of the NTN device 502 and radio cells between the base station 506 and the NTN gateway 504 and support handover of the UE 505 between radio cells, NTN devices, and other base stations. Additionally, a coverage area of the base station 506 may be much larger than the coverage area of a terrestrial network base station.

[0098] In the illustrated example of FIG. 5 A, a service link 520 may facilitate communication between the UE 505 and the NTN device 502, a feeder link 522 may facilitate communication between the NTN device 502 and the NTN gateway 504, and an interface 524 may facilitate communication between the base station 506 and the core network 510. The service link 520 and the feeder link 522 may be implemented by a same radio interface (e.g., the NR-Uu interface in some aspects).

[0099] FIG. 5B shows a diagram of a network architecture 525 capable of supporting NTN access, as presented herein. The network architecture 525 shown in FIG. 5B is similar to that shown in FIG. 5A, like designated elements being similar or the same. FIG. 5B, however, illustrates a network architecture with regenerative payloads, as opposed to transparent payloads shown in FIG. 5 A. A regenerative payload, unlike a transparent payload, includes an on-board base station (e.g., includes the functional capability of a base station), and is referred to herein as an NTN device 502 / base station. The on-board base station may be a network node that corresponds to the network device / the base station 310 in FIG. 3. The RAN 512 is illustrated as including the NTN device 502 / base station. Reference to the NTN device 502 / base station may refer to functions related to communication with the UE 505 and the core network 510 and / or to functions related to communication with the NTN gateway 504 and with the UE 505 at a physical radio frequency level.

[0100] An on-board base station may perform many of the same functions as the base station 506 as described previously. For example, the NTN device 502 / base station may terminate the radio interface and associated radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The NTN device 502 / base station may also support signaling connections and voice and data bearers to the UE 505 and may support handover of the UE 505 between different radio cells for the NTN device 502 / base station and between or among different NTN device / base stations. The NTN device502 / base station may assist in the handover (or transfer) of the UE 505 between different NTN gateways and different control networks. The NTN device 502 / base station may hide or obscure specific aspects of the NTN device 502 / base station from the core network 510, e.g., by interfacing to the core network 510 in the same way or in a similar way to a terrestrial network base station. The NTN device 502 / base station may further assist in sharing of the NTN device 502 / base station. The NTN device 502 / base station may communicate with one or more NTN gateways and with one or more core networks via the NTN gateway 504. In some aspects, the NTN device 502 / base station may communicate directly with other NTN device / base stations using Inter-Satellite Links (ISLs), which may support an Xn interface between any pair of NTN device / base stations.

[0101] With low Earth orbit (LEO) devices, the NTN device 502 / base station may manage moving radio cells with coverage at different times. The NTN gateway 504 may be connected directly to the core network 510, as illustrated. The NTN gateway 504 may be shared by multiple core networks, for example, if NTN gateways are limited. In some examples the core network 510 may need to be aware of coverage area(s) of the NTN device 502 / base station in order to page the UE 505 and to manage handover. Thus, as can be seen, the network architecture 525 with regenerative payloads may have more impact and complexity with respect to both the NTN device 502 / base station and the core network 510 than the network architecture 500 including transparent payloads, as shown in FIG. 5 A.

[0102] In the illustrated example of FIG. 5B, a service link 520 may facilitate communication between the UE 505 and the NTN device 502 / base station, a feeder link 522 may facilitate communication between the NTN device 502 / base station and the NTN gateway 504, and an interface 524 may facilitate communication between the NTN gateway 504 and the core network 510. The service link 520 may be implemented by the NR-Uu interface, in some aspects. The feeder link 522 may be implemented by the NG interface over SRI. The interface 524 may be implemented by the NG interface.

[0103] FIG. 5C shows a diagram of a network architecture 550 capable of supporting NTN access, as presented herein. The network architecture shown in FIG. 5C is similar to that shown in FIGs. 5A and 5B, like designated elements being similar or the same. FIG. 5C, however, illustrates a network architecture with regenerative payloads, asopposed to transparent payloads, as shown in FIG. 5A, and with a split architecture for the base station. For example, the base station may be split between a Central Unit (CU), such as the CU 110 of FIG. 1, and a Distributed Unit (DU), such as the DU 130 of FIG. 1. In the illustrated example of FIG. 5C, the network architecture 550 includes an NTN-CU 516, which may be a ground-based base station or a terrestrial base station. The regenerative payloads include an on-board base station DU, and is referred to herein as an NTN-DU 514. The NTN-CU 516 and the NTN-DU 514, collectively or individually, may correspond to the network node associated with the network device / the base station 310 in FIG. 3.

[0104] The NTN-DU 514 communicates with the NTN-CU 516 via the NTN gateway 504. The NTN-CU 516 together with the NTN-DU 514 perform functions, and may use internal communication protocols, which are similar to or the same as a gNB with a split architecture. In the example, the NTN-DU 514 may correspond to and perform functions similar to or the same as a gNB Distributed Unit (gNB-DU), while the NTN- CU 516 may correspond to and perform functions similar to or the same as a gNB Central Unit (gNB-CU). However, the NTN-CU 516 and the NTN-DU 514 may each include additional capability to support the UE 505 access using NTN devices.

[0105] The NTN-DU 514 and the NTN-CU 516 may communicate with one another using an Fl Application Protocol (F1AP), and together may perform some or all of the same functions as the base station 506 or the NTN device 502 / base station as described in connection with FIGs. 5B and 5C, respectively.

[0106] The NTN-DU 514 may terminate the radio interface and associated lower level radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The operation of the NTN-DU 514 may be partly controlled by the NTN-CU 516. The NTN-DU 514 may support one or more radio cells for the UE 505. The NTN-CU 516 may also be split into separate control plane (CP) (NTN-CU-CP) and user plane (UP) (NTN- CU-UP) portions. The NTN-DU 514 and the NTN-CU 516 may communicate over an Fl interface to (a) support control plane signaling for the UE 505 using IP, Stream Control Transmission Protocol (SCTP) and Fl Application Protocol (F1AP) protocols, and (b) to support user plane data transfer for a UE using IP, User DatagramProtocol (UDP), PDCP, SDAP, GTP-U and NR User Plane Protocol (NRUPP) protocols.

[0107] The NTN-CU 516 may communicate with one or more other NTN-CUs and / or with one more other terrestrial base stations using terrestrial links to support an Xn interface between any pair of NTN-CUs and / or between the NTN-CU 516 and any terrestrial base station.

[0108] The NTN-DU 514 together with the NTN-CU 516 may: (i) support signaling connections and voice and data bearers to the UE 505; (ii) support handover of the UE 505 between different radio cells for the NTN-DU 514 and between different NTN-DUs; and (iii) assist in the handover (or transfer) of NTN devices between different NTN gateways or different core networks. The NTN-CU 516 may hide or obscure specific aspects of the NTN devices from the core network 510, e.g., by interfacing to the core network 510 in the same way or in a similar way to a terrestrial network base station.

[0109] In the network architecture 550 of FIG. 5C, the NTN-DU 514 that communicates with and is accessible from an NTN-CU may change over time with LEO devices. With the split base station architecture, the core network 510 may connect to NTN-CUs that are fixed and that do not change over time, which may reduce difficulty with paging of the UE 505. For example, the core network 510 may not need to know which NTN-DU is needed for paging the UE 505. The network architecture with regenerative payloads with a split base station architecture may thereby reduce the core network 510 impact at the expense of additional impact to the NTN-CU 516.

[0110] Although the example of FIG. 5A, 5B, and 5C includes one UE 505, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the network architecture 500. Similarly, the network architecture 500, 525, or 550 may include a larger (or smaller) number of NTN devices, NTN gateways, base stations, RAN, core networks, and / or other components. The illustrated connections that connect the various components in the network architecture 500 include data and signaling connections which may include additional (intermediary) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and / or omitted, depending on desired functionality.

[0111] As described, wireless communication networks may support communications between network entities (e.g., network nodes, or RAN nodes, such as base stations, eNBs, gNBs, etc.; entities in a core network) and UEs, and may extend such communications via Internet-based services such as an IMS. For instance, a UE may be in a wireless communication system with satellite access, such as via an NTN, which facilitates wireless communications of the UE. However, the UE may be in an environment / location such that the NTN coverage of the UE is poor. For instance, if the UE goes into deep coverage for the NTN or enters a CM IDLE mode, the UE may be unable to receive or respond to paging requests for MT MMTEL. In such scenarios, the UE may not receive, or be notified of, the attempted communications.

[0112] For instance, in aspects, if the NTN UE goes into deep coverage, the UE may still monitor RNAs from the network. The RNAs may be delivered to the UE by an NG- RAN node using a PHY channel that may operate at a low signal -to-noise ratio (SNR) / signal-to-interference plus noise ratio (SINR). Aspects herein introduce an RNS as a new core network node, introduce interaction of an RNS and an AMF regarding delivery of RNA messages, and introduce interaction between an RNS and an IMS. Aspects herein for RNA messages for UEs in an NTN improve on / remediate the issues noted above. A wireless communication system with satellite access, e.g., via an NTN, is enabled to provide a mechanism for the network to notify a UE of a missed incoming MMTEL MT call(s) when normal paging fails, and accordingly, the user may be informed and take an appropriate action(s) (e.g., move to better coverage for successful call completion or take other actions). A missed page notification may come from the current / last registered PLMN and may be performed after / immediately after normal paging attempts are exhausted. Further, the notification may include secure information, including but not limited to, a caller-ID, a type of service, a time stamp, an SMS message for the UE having a number of words that is less than a threshold, and / or the like. Additionally, the missed page notification may be received by the UE when in coverage (e.g., with a poor UL condition) or out of coverage, and in such cases, the UE need not camp again on a cell, or re-register to the network. That is, to improve on / remediate the issues noted above, aspects herein enable providing a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages. Aspects also enable providing a UE with alert messaging securely and in varied UE environment scenarios by enabling RNSinteractions with an AMF. In such aspects, an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc. Aspects also enable providing a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0113] FIG. 6 is a call flow diagram 600 for wireless communications, in various aspects. Call flow diagram 600 illustrates RNA messages provided via an NTN for a UE 602 that communicates with a network service (e.g., an RNS 604) via an AMF 606 and / or a network / RAN node (e.g., a network node 698, eNB, gNB, sNB, etc., in various aspects. In aspects, communication between the UE 602, the RNS 604, and the AMF 606 may be provided via, or associated with, an NTN(s) (as described herein). In some aspects, the network node 698 may be an NTN node, e.g., as described in connection with any of FIGs. 1, 4, and / or 5A-5C. According to aspects described herein, the RNS 604 may be configured to provide an RNA message 626 (or multiple RNAs) to the UE 602 via interaction with the AMF 606. While aspects may be described in the context of the UE 602, aspects are also applicable to more than one UE (including the UE 602).

[0114] In the illustrated aspect, the UE 602 may be configured to perform a registration 608 with the AMF 606. The registration may be associated with a NAS security context 609 or NAS payload security context (e.g., for security and integrity protection of NAS messages), in aspects, which may be a most recent or a last used NAS payload security context. The AMF 606 may thus obtain / establish the NAS security context 609 with the UE 602, which may be utilized for delivery of the RNA message 626 and / or other communications, as described herein.

[0115] The UE 602 may be configured to enter (at 610) a CM IDLE mode, e.g., associated with the NTN. The UE 602 may be configured to perform (at 612), with the AMF 606, an RNA registration. The RNA registration may enable the UE 602 to register with the AMF 606 and / or the RNS 604 to receive the RNA message 626, and the RNA registration may include a support indication from the UE 602 that indicates the UE’s support for RNA. The AMF 606 may be configured to select the RNS 604 for the RNA registration and to provide, for the RNS 604, RNA information 614 associated with the RNA registration (at 612). In some aspects, the selection of the RNS may be based on the UE’s support for RNA. For example, if the UE does notindicate support for RNA, the AMF may skip selection of an RNS. The RNA information 614 may include, without limitation, an AMF address of the AMF 606, a subscription permanent identifier (SUPI) of the AMF 606, the RNA security context 616 (e.g., for security and integrity protection of RNA message), and / or the like. In aspects, subsequent to registration (and at 612), the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the RNA security context 616, which may be provided to the RNS 604 by the AMF 606. In aspects, the RNA security context 616 may be the same as the NAS security context 609, may be based on the NAS security context 609, or may be different than the NAS security context 609.

[0116] In aspects, and subsequent to the RNA registration (at 612), the UE 602 may be configured to monitor (at 618) for an RNA message(s) (e.g., the RNA message 626). The UE 602 may be configured to monitor (at 618) for RNA messages on a second channel that is different than a first channel for paging messages. In aspects, the RNA message 626 may carry at least some information not included in the paging messages (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like). In some aspects, the second channel may be configured for DL transmissions and not for UL transmissions.

[0117] The AMF 606 may be configured to receive an indication 620 of data for transmission to at least one UE (e.g., including the UE 602). The AMF 606 may be configured to perform and / or provide (at 622) a paging / service request(s) / message(s) (e.g., via the network node 698) for the UE 602, as described in further detail herein. As one example, the AMF 606 may be configured to provide (at 622), to a RAN node (e.g., the network node 698) in an NTN, one or more paging messages for the UE 602 in a first container type associated with delivery on a first channel. Based on a failure of the performance (at 622) of the paging / service request, by the network node 698, for the UE 602 (e.g., based on deep coverage of the UE 602 in the NTN, UL failure of the UE 602 during the paging process, etc.), an indication 624 thereof may be provided to and received by the RNS 604. That is, the indication 624 may indicate that the UE 602 is not reachable via regular paging operations.

[0118] The RNS 604 may be configured to receive the indication 624 of the paging failure for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message626, e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In aspects, the RNA message 626 may include information associated with the incoming message 618, such as but without limitation, one or more of a caller identifier (ID) associated with of the caller of a call for the UE 602, a type of call for the UE 602, a time stamp associated with the call, an SMS message for the UE 602 having a number of words that is less than a threshold, and / or the like.

[0119] The UE 602 may be configured to check an integrity of and decipher (at 628) the RNA message 626. In aspects, the UE 602 may be configured to check an integrity of the RNA message 626 and to decipher the RNA message 626 (e.g., at 628) based on the last used NAS security context (e.g., the NAS security context 609) of the UE 602.

[0120] The UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, a service / registration request 630 based on reception of the RNA message 626. The UE 602 may also be configured to transmit / provide, and the AMF 606 may be configured to receive, a response 632, e.g., via an RNA message protocol, for the RNS 604 for one or more RNA messages including the RNA message 626. The response 632 may an UL NAS transport that includes a delivery report associated with the one or more RNA messages including the RNA message 626. The AMF 606 may be configured to transmit / provide, and the RNS 604 may be configured to receive, a delivery report 634, e.g., based on the response 632 and / or via an RNA message protocol, and the RNS 604 may in turn forward the delivery report 634 to the IMS or another network entity. In aspects, the RNA message protocol may be a protocol dedicated for RNA messages, e.g., an RNA-specific protocol, and / or may be a protocol that is on top of, and / or transparent to, the NAS protocol.

[0121] In some aspects that utilize the UE 602 NAS, a timer(s) may be utilized by the UE 602 to generate the service / registration request 630 in response to the RNA message 626 reception. In such aspects, this timer(s) value may be configurable at the UE 602, and may be a value that is longer than another timer utilized for responding to paging requests. As one example, the UE 602 may utilize such a timer with an extended value to gather / merge multiple RNA messages (e.g., different instances of the RNA message 626), which the UE 602 may be configured to buffer, for the delivery (e.g.,transmission / provisions) of reports for multiple / all RNA messages in the RNA message response 632 after and / or during the service / registration request 630 transmission and operations.

[0122] FIG. 7 is a call flow diagram 700 for wireless communications, in various aspects. Call flow diagram 700 illustrates RNA messages for UEs in an NTN for a UE 702 that communicates with a network service (e.g., an RNS 704) via an AMF 706, in various aspects. In aspects, communications between the UE 702, the RNS 704, and the AMF 706 may be provided via, or associated with, an NTN(s) (as described herein, while not shown). Call flow diagram 700 also illustrates a network / RAN node (e.g., network node 798), an SMF 703, a UPF 705, and an IMS 707, through which signaling / communications are provided. In some aspects, the network node 798 may be an NTN node, e.g., as described in connection with any of FIGs. 1, 4, and / or 5 A-5C. According to aspects described herein, the RNS 704 may be configured to provide an RNA message (or multiple RNAs) to the UE 602 via interaction with the AMF 706. In the context of RNA messages for UEs in an NTN, call flow diagram 700 shows a UE 702 paging failure and subsequent RNA message metadata file storage. While aspects may be described in the context of the UE 702, aspects are also applicable to more than one UE (including the UE 702).

[0123] In the illustrated aspect, the IMS 707 may be configured to receive a session initiation protocol (SIP) invitation (SIP INVITE) 708 for initiation of MT MMTEL communications (e.g., from caller attempting to reach a user of the UE 702). In aspects, a timer (e.g., a SIP INVITE timer) may be started by the IMS 707 in association with reception of the SIP INVITE 708. The IMS 707 may be configured to transmit / provide, and the UPF 705 may be configured to receive, DL data 710 associated with the SIP INVITE 708. The UPF 705 may be configured to transmit / provide, and the SMF 703 may be configured to receive, a DL data notification 712 based on the DL data 710. The SMF 703 may be configured to configured to transmit / provide, and the AMF 706 may be configured to receive, a message 714 (e.g., a Namf_Communication_NlN2MessageTransfer), which may be an indication of data for transmission to at least one UE (e.g., including the UE 702). The AMF 706 may be configured to transmit / provide, to a RAN node (e.g., the network node 798) in an NTN, one or more paging messages 715 for the UE(s) (e.g., including the UE 702) in a first container type associated with delivery on a first channel. The network node798 may be configured to responsively perform paging 716 for the UE 702. As illustrated, the paging 716 may be unsuccessful, and based on an indication 717 of such paging failure (e.g., based on deep coverage of the UE 702 in the NTN, UL failure of the UE 702 during the paging 716 process, etc.), provided from the network node 798 to the AMF 706, the AMF 706 may be configured to transmit / provide, and the SMF 703 may be configured to receive, a response message 718 (e.g., a Namf_Communication_NlN2MessageTransfer response) indicative of the failure for the paging 716. The SMF 703 may be configured to transmit / provide, and the UPF 705 may be configured to receive, a failure indication 720 indicative of the failure for the paging 716 and based on the response message 718. The UPF 705 may be configured to discard (at 722) buffered data associated with the DL data 710 based on reception of the failure indication 720.

[0124] The IMS 707 may be configured to monitor the timer for its expiration, and may be configured (at 724) to determine the timer expiry and apply filter criteria to divert the communications flow to the RNS 704. In aspects, the IMS 707 may be configured to transmit / provide, and the RNS 704 may be configured to receive, an SIP INVITE 726 (which may be the SIP INVITE 708, in aspects). The SIP INVITE 726 may be received by the UE 702, from a network function (e.g., the IMS 707), as an indication upon a paging failure associated with a paging message (e.g., the paging 716 that failed) for the UE 702 in an NTN (as noted herein, the paging 716 that failed may be based on deep coverage of the UE 702 in the NTN, the UE 702 generally being otherwise unreachable, UL failure of the UE 702 during the paging 716 process, etc.). The RNS 704 may be configured to transmit / provide, and the IMS 707 may be configured to receive, a 200 OK status code 728, which may be responsive to reception of the SIP INVITE 726. The RNS 704 and / or the IMS 707 may be configured to provide (at 730) a message to the caller associated with the SIP INVITE 708. In aspects, the message may be a pre-recorded audio message, such as a voicemail greeting, text data, and / or the like. The RNS 704 may further be configured to store (at 732) an RNA metadata file 734. In aspects, the RNA metadata file 734 may be based on information associated with the SIP INVITE 726, and may include a caller ID associated with of the caller of the call for the UE 702, a type of call for the UE 702, a time stamp associated with the call, and / or the like.

[0125] FIG. 8 is a call flow diagram 800 for wireless communications, in various aspects. Call flow diagram 800 may be a continuing aspect of the call flow diagram 600 in FIG. 6 and / or the call flow diagram 700 in FIG. 7 for protection of an RNA body by an initial AMF and / or a last-serving AMF (e.g., the AMF with a most current NAS / RNA security context of the UE). In aspects, call flow diagram 800 may be applied for an AMF with a registration area, or for AMFs with multiple, respective registration areas. Call flow diagram 800 illustrates RNA messages for UEs in an NTN for a UE 802 that communicates with a network service (e.g., an RNS 804) via at least one AMF 806, in various aspects. In aspects, communications between the UE 802, the RNS 804, and the at least one AMF 806 may be provided via, or associated with, an NTN(s) (as described herein, while not shown). Call flow diagram 800 also illustrates a network node 898 (e.g., which may be associated with an NTN(s)), as well as an SMF 803, a UPF 805, and an IMS 807, through which signaling / communications may be previously provided as described for the call flow diagram 700 in FIG. 7. In some aspects, the network node 898 may be an NTN node, e.g., as described in connection with any of FIGs. 1, 4, and / or 5A-5C. According to aspects described herein, the RNS 804 may be configured to provide an RNA message (or multiple RNAs) to the UE 802 via interaction with the at least one AMF 806. In the context of RNA messages for UEs in an NTN, the call flow diagram 800 shows a UE 802 receiving and responding to an RNA message 820 from the RNS 804 subsequent to a failed paging attempt (e.g., as shown in FIG. 7). In the call flow diagram 800, the UE 802 is configured to monitor, subsequent to an RNA registration, as described herein, for RNA messages on a second channel that is different than a first channel for paging messages. In some aspects, the second channel may be configured for DL transmissions and not for UL transmissions. While aspects may be described in the context of the UE 802, aspects are also applicable to more than one UE (including the UE 802).

[0126] In the illustrated aspect, the at least one AMF 806 may include an initial AMF with which the UE 802 performed a registration associated with obtaining an RNA security context. The at least one AMF 806 may include one or more additional AMFs for which the UE 802 may be registered due to mobility and / or the like, such an a current / active, or a last-serving, AMF. Each of the at least one AMF 806 may be associated with a respective registration area. In aspects, the RNS 804 may be configured totransmit / provide, and the initial AMF of the at least one AMF 806 may be configured to receive, an MT reachability request 808. Based on reception of the MT reachability request 808, the initial AMF of the at least one AMF 806 may be configured to transmit / provide, and the RNS 804 may be configured to receive, an MT reachability response 810. Accordingly, the RNS 804 may establish a connection with the initial AMF of the at least one AMF 806 for provision of the RNA message 820 to the UE 802. In aspects, the RNA message 820 may carry at least some information (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like) not included in the paging message (e.g., the paging 716 that failed in FIG. 6), and the RNA message 820 may notify the UE 802 at least for the missed paging attempt for the RNS 804 (e.g., as a network service associated with NTNs).

[0127] Subsequent to reception of the MT reachability response 810, the RNS 804 may be configured to transmit / provide, and the initial AMF of the at least one AMF 806 may be configured to receive, an unsecured RNA body 812 (e.g., as a Namf_Communication_NlN2MessageTransfer). In aspects, the unsecured RNA body 812 may include one or more portions of information from an RNA metadata file (e.g., the RNA metadata file 734 in FIG. 7), as well as an SMS message having a number of words that is less than a threshold. The SMS message may be based on or associated with the RNA metadata file, in aspects.

[0128] The initial AMF of the at least one AMF 806 may be configured to protect (at 814) the unsecured RNA body 812, e.g., based on a last-used NAS security context of the UE 802 and / or based on the RNA security context of the UE 802, as described herein, to generate a secured RNA body 816. In aspects, the initial AMF of the at least one AMF 806 may be configured to transmit / provide, and the RNS 804 may be configured to receive, the secured RNA body 816. Based on reception of the secured RNA body 816, the RNS 804 may be configured to transmit / provide, and one or more other AMFs of the at least one AMF 806 may be configured to receive, the secured RNA body 816. Accordingly, when the UE 802 is no longer with the initial AMF of the at least one AMF 806, the initial AMF may still secure the RNA body and provide it to the RNS 804 for transmission / provision to other AMFs of the at least one AMF 806, one of which may be currently / actively associated with the UE 802. That is, the RNS 804 may be configured to provide the RNA message 820 to an AMF of the at least one AMF 806 that last served the UE 802, to receive the RNAmessage 820 with security protection from the AMF that last served the UE 802, and to provide, to multiple AMFs (e.g., other ones of the at least one AMF 806), the RNA message 820 with the security protection.

[0129] The current / active AMF of the at least one AMF 806 may receive the secured RNA body 816 and transmit / provide the secured RNA body 816 via a message 818, which the network node 898 may receive. The message 818 may comprise paging or may comprise an RNA-specific next generation application protocol (NGAP) message. In aspects, the current / active AMF of the at least one AMF 806 may be configured to continue to provide the message 818 for RNA until a timer expires, and to cease to provide the message 818 for RNA based on an expiration of the timer.

[0130] As an example, the network node 898 may be configured to receive one or more paging messages in a first container type for paging one or more UEs (e.g., including the UE 802), which the network node 898 may be configured to transmit on a first channel intended for the one or more UEs (e.g., as described above for FIG. 7). The network node 898 be configured to subsequently receive, and the at least one AMF 806 may be configured to transmit / provide, the message 818 for the RNA (e.g., with the secured RNA body 816) in a second container type (e.g., that may be different from the first container type) for the one or more UEs. The second container type may indicate for the network node 898 (e.g., as a network node) to transmit the RNA message 820 on a second channel that is different than the first channel. The network node 898 may also be configured to transmit the RNA message 820 for the one or more UEs (e.g., including the UE 802) on the second channel that is different than the first channel. The network node 898 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the at least one AMF 806 may collect / merge multiple RNA bodies over a period of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 818. The network node 898, subsequent to reception of the message 818, may be configured to generate the RNA message 820 and transmit / provide the RNA message 820 to the UE 802.

[0131] The UE 802 may be configured to trigger (at 822) a service / registration request subsequent to reception of the RNA message 820. The trigger (at 822) for the a service / registration request may enable the UE 802 to establish improved coverage with anNTN (e.g., based on the user being informed by the RNA message 820 and taking an appropriate action(s) such as moving to better coverage for successful call completion or taking another action(s), and / or the like). The UE 802 may be configured to transmit / provide, and the at least one AMF 806 may be configured to receive, an RNA message response 824 (e.g., via UL NAS transport) that notifies the at least one AMF 806 of reception of the RNA message 820. In aspects, the RNA message response 824 may be responsive to and / or indicative of any number of RNA messages and / or RNA bodies therein. The at least one AMF 806, in turn, may be configured to transmit / provide, and the RNS 804 may be configured to receive, an RNA message response 826 (e.g., via a NRNS_Communication_Uplink message), which may be based on the RNA message response 824 received by the at least one AMF 806. In aspects, the RNA message response 824 and / or the RNA message response 826 may be transmitted / provided via an RNA-specific protocol that sits above the NAS. That is, the UE 802 to RNS 804 messaging may be transparent over NAS and handled by an RNA-specific protocol, as described below for FIG. 10. The UE 802 is thus enabled, according to aspects, to transmit a registration request based on reception of an RNA message, and to provide a response for an RNS for one or more RNA messages including the RNA message received.

[0132] FIG. 9 is a call flow diagram 900 for wireless communications, in various aspects. Call flow diagram 900 may be a continuing aspect of the call flow diagram 600 in FIG. 6 and / or the call flow diagram 700 in FIG. 7 for protection of an RNA body by an RNS (e.g., with a last-used or most recent NAS / RNA security context of UE). In aspects, call flow diagram 800 may be applied for an AMF with a registration area, or for AMFs with multiple, respective registration areas.. Call flow diagram 900 illustrates RNA messages for UEs in an NTN for a UE 902 that communicates with a network service (e.g., an RNS 904) via an AMF 906 (e.g., having an associated registration area), in various aspects. In aspects, communications between the UE 902, the RNS 904, and the AMF 906 may be provided via, or associated with, an NTN(s) (as described herein, while not shown). Call flow diagram 900 also illustrates a network node 998 (e.g., which may be associated with an NTN(s)), as well as an SMF 903, a UPF 905, and an IMS 907, through which signaling / communications may be previously provided as described for the call flow diagram 700 in FIG. 7. In some aspects, the network node 998 may be an NTN node, e.g., as described in connectionwith any of FIGs. 1, 4, and / or 5A-5C. According to aspects described herein, the RNS 904 may be configured to provide an RNA message (or multiple RNAs) to the UE 902 via interaction with the AMF 906. In the context of RNA messages for UEs in an NTN, the call flow diagram 900 shows a UE 902 receiving and responding to an RNA message 918 from the RNS 904 subsequent to a failed paging attempt (e.g., as shown in FIG. 7). In the call flow diagram 900, the UE 902 is configured to monitor, subsequent to an RNA registration, as described herein, for RNA messages on a second channel that is different than a first channel for paging messages. In some aspects, the second channel may be configured for DL transmissions and not for UL transmissions. While aspects may be described in the context of the UE 902, aspects are also applicable to more than one UE (including the UE 902).

[0133] In the illustrated aspect, the AMF 906 in association with the UE 902 may have performed a registration associated with obtaining an RNA security context. The AMF 906 may be associated with a registration area. In aspects, the RNS 904 may be configured to transmit / provide, and the AMF 906 may be configured to receive, an MT reachability request 908. Based on reception of the MT reachability request 908, the AMF 906 may be configured to transmit / provide, and the RNS 904 may be configured to receive, an MT reachability response 910. Accordingly, the RNS 904 may establish a connection with the AMF 906 for provision of the RNA message 920 to the UE 902. In aspects, the RNA message 920 may carry at least some information (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like) not included in the paging message (e.g., the paging 716 that failed in FIG. 6), and the RNA message 920 may notify the UE 902 at least for the missed paging attempt for the RNS 904 (e.g., as a network service associated with NTNs).

[0134] Subsequent to reception of the MT reachability response 910, the RNS 904 may be configured to protect (at 912) an unsecured RNA body for the RNA message 918, e.g., based on a last-used NAS security context of the UE 902 and / or based on the RNA security context of the UE 902, as described herein, to generate a secured RNA body 914. In such aspects, the RNA security context of the UE 902 may be previously established when the UE 902 performed its last registration procedure with the AMF 906 (e.g., as similarly described above for FIG. 6 (608, 609)). For example, after the end of a successful registration, the AMF 906 may be configured to have forwarded the UE 902 identity and the RNA security context to the RNS 904, and subsequently,the RNS 904 may be configured to have used this RNA security context to protect the unsecured RNA body (e.g., as the secured RNA body 914. In such aspects, as an example alternative, provision / reception of the MT reachability request 908 and the MT reachability response 910 may optional / omitted. In aspects, the unsecured RNA body may include one or more portions of information from an RNA metadata file (e.g., the RNA metadata file 734 in FIG. 7), as well as an SMS message having a number of words that is less than a threshold. The SMS message may be based on or associated with the RNA metadata file, in aspects.

[0135] In aspects, the RNS 904 may be configured to transmit / provide, and the AMF 906 may be configured to receive, the secured RNA body 914 (e.g., as a Namf_Communication_NlN2MessageTransfer). The AMF 906 may receive the secured RNA body 914 and transmit / provide the secured RNA body 914 via a message 916, which the network node 998 may receive. The message 916 may comprise paging or may comprise an RNA-specific NGAP message. In aspects, the AMF 906 may be configured to continue to provide the message 916 for RNA until a timer expires, and to cease to provide the message 916 for RNA based on an expiration of the timer.

[0136] As an example, the network node 998 may be configured to receive one or more paging messages in a first container type for paging one or more UEs (e.g., including the UE 902), which the network node 998 may be configured to transmit on a first channel intended for the one or more UEs (e.g., as described above for FIG. 7). The network node 998 may be configured to subsequently receive, and the AMF 906 may be configured to transmit / provide, the message 916 for the RNA (e.g., with the secured RNA body 914) in a second container type (e.g., that may be different from the first container type) for the one or more UEs. The second container type may indicate for the network node 998 (e.g., as a network node) to transmit the RNA message 918 on a second channel that is different than the first channel. The network node 998 may also be configured to transmit the RNA message 918 for the one or more UEs (e.g., including the UE 902) on the second channel that is different than the first channel. The network node 998 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the AMF 906 may collect / merge multiple RNA bodies over aperiod of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 916. The network node 998, subsequent to reception of the message 916, may be configured to generate the RNA message 918 and transmit / provide the RNA message 918 to the UE 902.

[0137] The UE 902 may be configured to trigger (at 920) a service / registration request subsequent to reception of the RNA message 918. The trigger (at 920) for the a service / registration request may enable the UE 902 to establish improved coverage with an NTN (e.g., based on the user being informed by the RNA message 918 and taking an appropriate action(s) such as moving to better coverage for successful call completion or taking another action(s), and / or the like). The UE 902 may be configured to transmit / provide, and the AMF 906 may be configured to receive, an RNA message response 922 (e.g., via UL NAS transport) that notifies the AMF 906 of reception of the RNA message 918. In aspects, the RNA message response 922 may be responsive to and / or indicative of any number of RNA messages and / or RNA bodies therein. The AMF 906, in turn, may be configured to transmit / provide, and the RNS 904 may be configured to receive, an RNA message response 924 (e.g., via a NRNS_Communication_Uplink message), which may be based on the RNA message response 922 received by the AMF 906. In aspects, the RNA message response 922 and / or the RNA message response 924 may be transmitted / provided via an RNA- specific protocol that sits above the NAS. That is, the UE 902 to RNS 904 messaging may be transparent over NAS and handled by an RNA-specific protocol, as described below for FIG. 10. The UE 902 is thus enabled, according to aspects, to transmit a registration request based on reception of an RNA message, and to provide a response for an RNS for one or more RNA messages including the RNA message received.

[0138] FIG. 10 is diagram 1000 illustrating an example of a protocol stack with an RNA protocol for RNA messaging, in various aspects. Diagram 1000 illustrates RNA messages for UEs in an NTN for a UE 1002 that communicates with a network service (e.g., an RNS 1004) via an AMF 1006 and an NG-RAN 1098, which may comprise one or more base stations, gNBs, eNBs, and / or the like, in various aspects. In aspects, communications between the UE 1002, the RNS 1004, the AMF 1006, and the NG- RAN 1098 may be provided via, or associated with, an NTN(s) (as described herein, while not shown).

[0139] Diagram 1000 shows a protocol stack 1012 for communications between the UE 1002, the RNS 1004, the AMF 1006, and the NG-RAN 1098, according to prior protocol stack solutions, having NAS and / or hyper-text transfer protocol / 2 (HTTP / 2) above other known protocols.

[0140] According to aspects herein, an RNA-specific protocol 1008 is provided that sits above the NAS for the UE 1002, and an RNA-specific protocol 1010 is provided that sits above the HTTP / 2 for the RNS 1004. That is, as noted above, RNA message responses from the UE 1002 may be transmitted / provided to the RNS 1004 via an RNA-specific protocol that sits above the NAS, where the UE 1002 to RNS 1004 messaging may be transparent over NAS and handled by the RNA-specific protocol (e.g., the RNA-specific protocol 1008 / the RNA-specific protocol 1010). In other words, the aspects herein enable a UE to consume RNA messages over NAS (delivered from a lower layer in a NAS container that is different from paging) from the RNS 1004 as a network service to the upper layer / application layer and with a payload field populated with the RNA body, as described herein. Aspects enable the UE 1002 to respond to these new RNA messages via an RNA-specific protocol (e.g., the RNA protocol 1008 at the UE 1002), and the AMF 1006 may be configured to transport such RNA message responses to the RNS 1004.

[0141] Accordingly, aspects provide a new communication protocol that is RNA-specific and transported over NAS between the RNS 1004 and the UE 1002. The RNA protocol described may be configured to handle delivery of multiple RNA messages, UE 1002 ACKS (e.g., after UE is CM mode connected), retransmissions of RNA messages, and / or the like.

[0142] FIG. 11 is a flowchart 1100 of a method of wireless communication. The method may be performed by a network service (e.g., the RNS 167, 604, 704, 804, 904, 1004; the core network 510; the network entity 1502, 1602, 1760). The method may be for RNA messages for UEs in an NTN. The method may provide for enabling a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages, enabling a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF (e.g., an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure,etc.), and enabling a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0143] At 1102, the network service receives, from a network function, an indication upon a paging failure associated with a paging message for a UE in a NTN. As an example, the reception may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the network service (e.g., the RNS 604) receiving such an indication.

[0144] Regarding the RNS 604 and RNA messages, the UE 602 may be configured to perform (at 612), with the AMF 606, an RNA registration. The RNA registration may enable the UE 602 to register with the AMF 606 and / or the RNS 604 to receive the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), and the RNA registration may include a support indication by the UE 602 of RNA support for the UE 602. In aspects, the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the support indication for RNA support for the UE 602. The AMF 606 may be configured to select the RNS 604 for the RNA registration and to provide, for the RNS 604, RNA information 614 associated with the RNA registration (at 612). The RNA information 614 may include, without limitation, and AMF address of the AMF 606, a SUPI of the AMF 606, the RNA security context 616 (e.g., for security and integrity protection of RNA message), and / or the like. In aspects, subsequent to registration (and at 612), the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the RNA security context 616, which may be provided to the RNS 604 by the AMF 606. In aspects, the RNA security context 616 may be the same as the NAS security context 609, may be based on the NAS security context 609, or may be different than the NAS security context 609. Based on a failure of the performance (at 622) of the paging / service request (e.g., 716 in FIG. 7), by the network node 698, for the UE 602 (e.g., based on deep coverage of the UE 602 in the NTN, UL failure of the UE 602 during the paging process, etc.), an indication 624 (e.g., 726 in FIG. 7) thereof may be provided to and received by the RNS 604. That is, the indication 624 (e.g., 726 in FIG. 7) may indicate that the UE 602 is not reachable via regular paging operations (e.g., 716 in FIG. 7). The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602. In the context of FIG. 7, theIMS 707 may be configured to monitor the timer for its expiration, and may be configured (at 724) to determine the timer expiry and apply filter criteria to divert the communications flow to the RNS 704. In aspects, the IMS 707 may be configured to transmit / provide, and the RNS 704 may be configured to receive, an SIP INVITE 726 (which may be the SIP INVITE 708, in aspects). The SIP INVITE 726 may be received by the UE 702, from a network function (e.g., the IMS 707), as an indication upon a paging failure associated with a paging message (e.g., the paging 716 that failed) for the UE 702 in an NTN (as noted herein, the paging 716 that failed may be based on deep coverage of the UE 702 in the NTN, the UE 702 generally being otherwise unreachable, UL failure of the UE 702 during the paging 716 process, etc.). The RNS 704 may be configured to transmit / provide, and the IMS 707 may be configured to receive, a 200 OK status code 728, which may be responsive to reception of the SIP INVITE 726. The RNS 704 and / or the IMS 707 may be configured to provide (at 730) a message to the caller associated with the SIP INVITE 708. In aspects, the message may be a pre-recorded audio message, such as a voicemail greeting, text data, and / or the like. The RNS 704 may further be configured to store (at 732) an RNA metadata file 734. In aspects, the RNA metadata file 734 may be based on information associated with the SIP INVITE 726, and may include a caller ID associated with of the caller of the call for the UE 702, a type of call for the UE 702, a time stamp associated with the call, and / or the like.

[0145] At 1104, the network service provides, to at least one AMF, a RNA message for the UE, where the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service. As an example, the provision may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the network service (e.g., the RNS 604) providing such an indication to a UE (e.g., the UE 602).

[0146] The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein.The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In aspects, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) may include information associated with the incoming message 618, such as but without limitation, one or more of a caller identifier (ID) associated with of the caller of a call for the UE 602, a type of call for the UE 602, a time stamp associated with the call, an SMS message for the UE 602 having a number of words that is less than a threshold, and / or the like. In the context of FIG. 8, subsequent to reception of the MT reachability response 810, the RNS 804 may be configured to transmit / provide, and the initial AMF of the at least one AMF 806 may be configured to receive, an unsecured RNA body 812 (e.g., as a Namf_Communication_NlN2MessageTransfer). In aspects, the unsecured RNA body 812 may include one or more portions of information from an RNA metadata file (e.g., the RNA metadata file 734 in FIG. 7), as well as an SMS message having a number of words that is less than a threshold. The SMS message may be based on or associated with the RNA metadata file, in aspects. The initial AMF of the at least one AMF 806 may be configured to protect (at 814) the unsecured RNA body 812, e.g., based on a last-used NAS security context of the UE 802 and / or based on the RNA security context of the UE 802, as described herein, to generate a secured RNA body 816. In aspects, the initial AMF of the at least one AMF 806 may be configured to transmit / provide, and the RNS 804 may be configured to receive, the secured RNA body 816. Based on reception of the secured RNA body 816, the RNS 804 may be configured to transmit / provide, and one or more other AMFs of the at least one AMF 806 may be configured to receive, the secured RNA body 816. Accordingly, when the UE 802 is no longer with the initial AMF of the at least one AMF 806, the initial AMF may still secure the RNA body and provide it to the RNS 804 for transmission / provision to other AMFs of the at least one AMF 806, one of which may be currently / actively associated with the UE 802. That is, the RNS 804 may be configured to provide the RNA message 820 to an AMF of the at least one AMF 806 that last served the UE 802, to receive the RNA message 820 with security protection from the AMF that last served the UE 802, and to provide, to multiple AMFs (e.g., other ones of the at least one AMF 806), the RNA message 820 with the security protection. In the context of FIG. 9, Subsequent to reception of the MT reachability response 910, theRNS 904 may be configured to protect (at 912) an unsecured RNA body for the RNA message 918, e.g., based on a last-used NAS security context of the UE 902 and / or based on the RNA security context of the UE 902, as described herein, to generate a secured RNA body 914. In such aspects, the RNA security context of the UE 902 may be previously established when the UE 902 performed its last registration procedure with the AMF 906 (e.g., as similarly described above for FIG. 6 (608, 609)). For example, after the end of a successful registration, the AMF 906 may be configured to have forwarded the UE 902 identity and the RNA security context to the RNS 904, and subsequently, the RNS 904 may be configured to have used this RNA security context to protect the unsecured RNA body (e.g., as the secured RNA body 914. In such aspects, as an example alternative, provision / reception of the MT reachability request 908 and the MT reachability response 910 may optional / omitted. In aspects, the unsecured RNA body may include one or more portions of information from an RNA metadata file (e.g., the RNA metadata file 734 in FIG. 7), as well as an SMS message having a number of words that is less than a threshold. The SMS message may be based on or associated with the RNA metadata file, in aspects. In aspects, the RNS 904 may be configured to transmit / provide, and the AMF 906 may be configured to receive, the secured RNA body 914 (e.g., as a Namf_Communication_NlN2MessageTransfer). Referring again to FIG. 6, the UE 602 may also be configured to transmit / provide, and the AMF 606 may be configured to receive, a response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9), e.g., via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), for the RNS 604 for one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) may an UL NAS transport that includes a delivery report associated with the one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The AMF 606 may be configured to transmit / provide, and the RNS 604 may be configured to receive, a delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9), e.g., based on the response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) and / or via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), and the RNS 604 may in turn forward the delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9) to the IMS or another network entity. In aspects, the RNA message protocol (e.g., 1008, 1010 in FIG. 10) may be a protocol dedicatedfor RNA messages, e.g., an RNA-specific protocol (e.g., 1008, 1010 in FIG. 10), and / or may be a protocol that is on top of, and / or transparent to, the NAS protocol.

[0147] FIG. 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by an AMF (e.g., the AMF 161, 606, 706, 806, 906, 1006; the core network 510; the network entity 1502, 1602, 1760). The method may be for RNA messages for UEs in an NTN. The method may provide for enabling a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages, enabling a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF (e.g., an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc.), and enabling a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0148] At 1202, the AMF receives an indication of data for transmission to at least one UE. As an example, the reception may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the AMF (e.g., the AMF 606) receiving such an indication of data for at least one UE (e.g., the UE 602).

[0149] The AMF 606 may be configured to perform a registration 608 with the UE 602. The registration may be associated with a NAS security context 609 or NAS payload security context (e.g., for security and integrity protection of NAS messages), in aspects, which may be a most recent or a last used NAS payload security context. The AMF 606 may thus obtain / establish the NAS security context 609 with the UE 602, which may be utilized for delivery of the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) and / or other communications, as described herein. The UE 602 may be configured to perform (at 612), with the AMF 606, an RNA registration. The RNA registration may enable the UE 602 to register with the AMF 606 and / or the RNS 604 to receive the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), and the RNA registration may include a support indication by the UE 602 of RNA support for the UE 602. In aspects, the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the support indication for RNA support for the UE 602. The AMF 606 may be configured to select the RNS 604 for the RNA registrationand to provide, for the RNS 604, RNA information 614 associated with the RNA registration (at 612). The RNA information 614 may include, without limitation, and AMF address of the AMF 606, a SUPI of the AMF 606, the RNA security context 616 (e.g., for security and integrity protection of RNA message), and / or the like. In aspects, subsequent to registration (and at 612), the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the RNA security context 616, which may be provided to the RNS 604 by the AMF 606. In aspects, the RNA security context 616 may be the same as the NAS security context 609, may be based on the NAS security context 609, or may be different than the NAS security context 609. The AMF 606 may be configured to select the RNS 604 for the RNA registration and to provide, for the RNS 604, RNA information 614 associated with the RNA registration (at 612). The RNA information 614 may include, without limitation, and AMF address of the AMF 606, a SUPI of the AMF 606, the RNA security context 616 (e.g., for security and integrity protection of RNA message), and / or the like. In aspects, subsequent to registration (and at 612), the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the RNA security context 616, which may be provided to the RNS 604 by the AMF 606. In aspects, the RNA security context 616 may be the same as the NAS security context 609, may be based on the NAS security context 609, or may be different than the NAS security context 609. The AMF 606 may be configured to receive an indication 620 (e.g., 714 in FIG. 7) of data for transmission to at least one UE (e.g., including the UE 602). In the context of FIG. 7, the SMF 703 may be configured to configured to transmit / provide, and the AMF 706 may be configured to receive, a message 714 (e.g., a Namf_Communication_NlN2MessageTransfer), which may be an indication of data for transmission to at least one UE (e.g., including the UE 702).

[0150] At 1204, the AMF provides, to a RAN node in a NTN, one or more paging messages for the UE in a first container type associated with delivery on a first channel. As an example, the provision may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the AMF (e.g., the AMF 606) providing such paging messages for a UE (e.g., the UE 602).

[0151] The AMF 606 may be configured to perform and / or provide (at 622) a paging / service request(s) / message(s) (e.g., 716 in FIG. 7) (e.g., via the network node 698) for the UE 602, as described in further detail herein. As one example, the AMF 606 may be configured to provide (at 622), to a RAN node (e.g., the network node 698) in an NTN, one or more paging messages (e.g., 715 in FIG. 7) for the UE 602 in a first container type associated with delivery on a first channel. In the context of FIG. 7, the AMF 706 may be configured to transmit / provide, to a RAN node (e.g., the network node 798) in an NTN, one or more paging messages 715 for the UE(s) (e.g., including the UE 702) in a first container type associated with delivery on a first channel.

[0152] At 1206, the AMF receives, from a network service, an RNA message for one or more UEs. As an example, the reception may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the AMF (e.g., the AMF 606) receiving such an RNA message for one or more UEs (e.g., the UE 602).

[0153] The AMF 606, as noted herein, may perform aspects for RNA message provision for a UE. The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In aspects, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) may include information associated with the incoming message 618, such as but without limitation, one or more of a caller identifier (ID) associated with of the caller of a call for the UE 602, a type of call for the UE 602, a time stamp associated with the call, an SMS message for the UE 602 having a number of words that is less than a threshold, and / or the like. In the context of FIG. 8, subsequent to reception of the MT reachability response 810, the RNS 804 may be configured to transmit / provide, and the initial AMF of the at least one AMF 806 may be configured to receive, an unsecured RNA body 812 (e.g., as a Namf_Communication_NlN2MessageTransfer). In aspects, the unsecured RNAbody 812 may include one or more portions of information from an RNA metadata file (e.g., the RNA metadata file 734 in FIG. 7), as well as an SMS message having a number of words that is less than a threshold. The SMS message may be based on or associated with the RNA metadata file, in aspects. The initial AMF of the at least one AMF 806 may be configured to protect (at 814) the unsecured RNA body 812, e.g., based on a last-used NAS security context of the UE 802 and / or based on the RNA security context of the UE 802, as described herein, to generate a secured RNA body 816. In aspects, the initial AMF of the at least one AMF 806 may be configured to transmit / provide, and the RNS 804 may be configured to receive, the secured RNA body 816. Based on reception of the secured RNA body 816, the RNS 804 may be configured to transmit / provide, and one or more other AMFs of the at least one AMF 806 may be configured to receive, the secured RNA body 816. Accordingly, when the UE 802 is no longer with the initial AMF of the at least one AMF 806, the initial AMF may still secure the RNA body and provide it to the RNS 804 for transmission / provision to other AMFs of the at least one AMF 806, one of which may be currently / actively associated with the UE 802. That is, the RNS 804 may be configured to provide the RNA message 820 to an AMF of the at least one AMF 806 that last served the UE 802, to receive the RNA message 820 with security protection from the AMF that last served the UE 802, and to provide, to multiple AMFs (e.g., other ones of the at least one AMF 806), the RNA message 820 with the security protection. The current / active AMF of the at least one AMF 806 may receive the secured RNA body 816 and transmit / provide the secured RNA body 816 via a message 818, which the network node 898 may receive.

[0154] At 1208, the AMF provides, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages. As an example, the provision may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16, and / or the network interface 1780 in FIG. 17. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the AMF (e.g., the AMF 606) providing such an RNA message for one or more UEs (e.g., the UE 602).

[0155] The AMF 606, as noted herein, may perform aspects for RNA message provision for a UE. The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG.7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602., as noted herein, may perform aspects for RNA message provision for a UE. The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In the context of FIG. 8, the current / active AMF of the at least one AMF 806 may receive the secured RNA body 816 and transmit / provide the secured RNA body 816 via a message 818, which the network node 898 may receive. The message 818 may comprise paging or may comprise an RNA-specific NGAP message. In aspects, the current / active AMF of the at least one AMF 806 may be configured to continue to provide the message 818 for RNA until a timer expires, and to cease to provide the message 818 for RNA based on an expiration of the timer. In the context of FIG. 9, the AMF 906 may receive the secured RNA body 914 and transmit / provide the secured RNA body 914 via a message 916, which the network node 998 may receive. The message 916 may comprise paging or may comprise an RNA-specific NGAP message. In aspects, the AMF 906 may be configured to continue to provide the message 916 for RNA until a timer expires, and to cease to provide the message 916 for RNA based on an expiration of the timer. Referring again to FIG. 6, the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, a service / registration request 630 (e.g., 822 in FIG. 8; 920 in FIG. 9) based on reception of the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The UE 602 may also be configured to transmit / provide, and the AMF 606 may be configured to receive, a response 632 (e.g., 824 in FIG. 8;922 in FIG. 9), e.g., via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), for the RNS 604 for one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) may an UL NAS transport that includes a delivery report associated with the one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The AMF 606 may be configured to transmit / provide, and the RNS 604 may be configured to receive, a delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9), e.g., based on the response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) and / or via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), and the RNS 604 may in turn forward the delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9) to the IMS or another network entity. In aspects, the RNA message protocol (e.g., 1008, 1010 in FIG. 10) may be a protocol dedicated for RNA messages, e.g., an RNA-specific protocol (e.g., 1008, 1010 in FIG. 10), and / or may be a protocol that is on top of, and / or transparent to, the NAS protocol.

[0156] FIG. 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a network / RAN node (e.g., the base station 102, 402, 506 (or distributed components thereof); network node 698, 798, 898, 998; the satellite 170; the RAN 512; the NTN device 502 (or distributed components thereof); the NTN-DU 514; the NTN-CU 516; the network node 406; the NG-RAN 1098; the network entity 1502, 1602, 1760). The method may be for RNA messages for UEs in an NTN. The method may provide for enabling a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages, enabling a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF (e.g., an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc.), and enabling a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0157] At 1302, the network node receives one or more paging messages in a first container type for paging one or more UEs. As an example, the reception may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the networknode (e.g., the network node 698) receiving such paging messages for one or more UEs (e.g., the UE 602).

[0158] The network node 698, as noted herein, may perform aspects for UE 602 paging via a first type of container. The AMF 606 may be configured to receive an indication 620 (e.g., 714 in FIG. 7) of data for transmission to at least one UE (e.g., including the UE 602). The AMF 606 may be configured to perform and / or provide (at 622) a paging / service request(s) / message(s) (e.g., 716 in FIG. 7) (e.g., via the network node 698) for the UE 602, as described in further detail herein. As one example, the AMF 606 may be configured to provide (at 622), to a RAN node (e.g., the network node 698) in an NTN, one or more paging messages (e.g., 715 in FIG. 7) for the UE 602 in a first container type associated with delivery on a first channel. Based on a failure of the performance (at 622) of the paging / service request (e.g., 716 in FIG. 7), by the network node 698, for the UE 602 (e.g., based on deep coverage of the UE 602 in the NTN, UL failure of the UE 602 during the paging process, etc.), an indication 624 (e.g., 726 in FIG. 7) thereof may be provided to and received by the RNS 604. That is, the indication 624 (e.g., 726 in FIG. 7) may indicate that the UE 602 is not reachable via regular paging operations (e.g., 716 in FIG. 7).

[0159] At 1304, the network node transmits the one or more paging messages on a first channel that are intended for the one or more UEs. As an example, the transmission may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the network node (e.g., the network node 698) transmitting such RNA messages for one or more UEs (e.g., the UE 602).

[0160] The network node 698, as noted herein, may perform aspects for UE 602 paging via a first type of container. The AMF 606 may be configured to perform and / or provide (at 622) a paging / service request(s) / message(s) (e.g., 716 in FIG. 7) (e.g., via the network node 698) for the UE 602, as described in further detail herein. As one example, the AMF 606 may be configured to provide (at 622), to a RAN node (e.g., the network node 698) in an NTN, one or more paging messages (e.g., 715 in FIG. 7) for the UE 602 in a first container type associated with delivery on a first channel. In the context of FIG. 7, the AMF 706 may be configured to transmit / provide, to a RAN node (e.g., the network node 798) in an NTN, one or more paging messages 715 for the UE(s) (e.g., including the UE 702) in a first container type associated with deliveryon a first channel. The network node 798 may be configured to responsively perform paging 716 for the UE 702. As illustrated, the paging 716 may be unsuccessful, and based on an indication 717 of such paging failure (e.g., based on deep coverage of the UE 702 in the NTN, UL failure of the UE 702 during the paging 716 process, etc.), provided from the network node 798 to the AMF 706, the AMF 706 may be configured to transmit / provide, and the SMF 703 may be configured to receive, a response message 718 (e.g., a Namf_Communication_NlN2MessageTransfer response) indicative of the failure for the paging 716.

[0161] At 1306, the network node receives an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. As an example, the reception may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the network node (e.g., the network node 698) receiving such RNA messages for one or more UEs (e.g., the UE 602).

[0162] The network node 698, as noted herein, may perform aspects for RNA message provision for a UE. The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In aspects, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) may include information associated with the incoming message 618, such as but without limitation, one or more of a caller identifier (ID) associated with of the caller of a call for the UE 602, a type of call for the UE 602, a time stamp associated with the call, an SMS message for the UE 602 having a number of words that is less than a threshold, and / or the like. As shown in FIG. 8, the current / active AMF of the at least one AMF 806 may receive the secured RNA body 816 and transmit / provide the secured RNA body 816 via a message 818, which the network node 898 may receive. The message 818may comprise paging or may comprise an RNA-specific NGAP message. In aspects, the current / active AMF of the at least one AMF 806 may be configured to continue to provide the message 818 for RNA until a timer expires, and to cease to provide the message 818 for RNA based on an expiration of the timer. As an example, the network node 898 may be configured to receive one or more paging messages in a first container type for paging one or more UEs (e.g., including the UE 802), which the network node 898 may be configured to transmit on a first channel intended for the one or more UEs (e.g., as described above for FIG. 7). The network node 898 be configured to subsequently receive, and the at least one AMF 806 may be configured to transmit / provide, the message 818 for the RNA (e.g., with the secured RNA body 816) in a second container type (e.g., that may be different from the first container type) for the one or more UEs. The second container type may indicate for the network node 898 (e.g., as a network node) to transmit the RNA message 820 on a second channel that is different than the first channel. The network node 898 may also be configured to transmit the RNA message 820 for the one or more UEs (e.g., including the UE 802) on the second channel that is different than the first channel. The network node 898 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the at least one AMF 806 may collect / merge multiple RNA bodies over a period of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 818. The network node 898, subsequent to reception of the message 818, may be configured to generate the RNA message 820 and transmit / provide the RNA message 820 to the UE 802. As shown in FIG. 9, the AMF 906 may receive the secured RNA body 914 and transmit / provide the secured RNA body 914 via a message 916, which the network node 998 may receive. The message 916 may comprise paging or may comprise an RNA-specific NGAP message. In aspects, the AMF 906 may be configured to continue to provide the message 916 for RNA until a timer expires, and to cease to provide the message 916 for RNA based on an expiration of the timer. As an example, the network node 998 may be configured to receive one or more paging messages in a first container type for paging one or more UEs (e.g., including the UE 902), which the network node 998 may be configured to transmit on a first channel intended for the one or more UEs (e.g., as described above for FIG. 7).The network node 998 may be configured to subsequently receive, and the AMF 906 may be configured to transmit / provide, the message 916 for the RNA (e.g., with the secured RNA body 914) in a second container type (e.g., that may be different from the first container type) for the one or more UEs. The second container type may indicate for the network node 998 (e.g., as a network node) to transmit the RNA message 918 on a second channel that is different than the first channel. The network node 998 may also be configured to transmit the RNA message 918 for the one or more UEs (e.g., including the UE 902) on the second channel that is different than the first channel. The network node 998 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the AMF 906 may collect / merge multiple RNA bodies over a period of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 916. The network node 998, subsequent to reception of the message 916, may be configured to generate the RNA message 918 and transmit / provide the RNA message 918 to the UE 902.

[0163] At 1308, the network node transmits the RNA message for said the one or more UEs on the second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels. As an example, the transmission may be performed by one or more of the component 199, the transceiver(s) 1646, and / or the antennas 1680 in FIG. 16. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the network node (e.g., the network node 698) transmitting such RNA messages for one or more UEs (e.g., the UE 602).

[0164] The network node 698, as noted herein, may perform aspects for RNA message provision for a UE. The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for the UE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocolfrom the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. As shown in FIG. 8, the network node 898 may also be configured to transmit the RNA message 820 for the one or more UEs (e.g., including the UE 802) on the second channel that is different than the first channel. The network node 898 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the at least one AMF 806 may collect / merge multiple RNA bodies over a period of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 818. The network node 898, subsequent to reception of the message 818, may be configured to generate the RNA message 820 and transmit / provide the RNA message 820 to the UE 802. As shown in FIG. 9, the network node 998 may also be configured to transmit the RNA message 918 for the one or more UEs (e.g., including the UE 902) on the second channel that is different than the first channel. The network node 998 may have a first logical channel for paging and a second logical channel for RNA messages, and the first logical channel and the second logical channel may have a different mapping to physical channels, according to aspects. In aspects, the AMF 906 may collect / merge multiple RNA bodies over a period of time (e.g., based on a collection timer), and transmit the multiple RNA bodies together via the message 916. The network node 998, subsequent to reception of the message 916, may be configured to generate the RNA message 918 and transmit / provide the RNA message 918 to the UE 902.

[0165] FIG. 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104, 404, 424, 505, 602, 702, 802, 902, 1002; the apparatus 1504). The method may be for RNA messages for UEs in an NTN. The method may provide for enabling a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages, enabling a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF (e.g., an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc.), and enabling a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0166] At 1402, the UE enters a CM idle mode. As an example, the entry may be performed by one or more of the component 198, the transceiver(s) 1522, and / or the antennas 1580 in FIG. 15. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the UE 602 entering such CL idle mode.

[0167] The UE 602 may be configured to perform a registration 608 with the AMF 606. The registration may be associated with a NAS security context 609 or NAS payload security context (e.g., for security and integrity protection of NAS messages), in aspects, which may be a most recent or a last used NAS payload security context. The AMF 606 may thus obtain / establish the NAS security context 609 with the UE 602, which may be utilized for delivery of the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) and / or other communications, as described herein. The UE 602 may be configured to enter (at 610) a CM IDLE mode, e.g., associated with the NTN. The UE 602 may be configured to perform (at 612), with the AMF 606, an RNA registration.

[0168] At 1404, the UE transmits an indication of support for a RNA. As an example, the entry may be transmission by one or more of the component 198, the transceiver s) 1522, and / or the antennas 1580 in FIG. 15. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the UE 602 transmitting such an indication (e.g., to the AMF 606 for the RNS 604).

[0169] The UE 602 may be configured to perform (at 612), with the AMF 606, an RNA registration. The RNA registration may enable the UE 602 to register with the AMF 606 and / or the RNS 604 to receive the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), and the RNA registration may include a support indication by the UE 602 of RNA support for the UE 602. In aspects, the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the support indication for RNA support for the UE 602. The AMF 606 may be configured to select the RNS 604 for the RNA registration and to provide, for the RNS 604, RNA information 614 associated with the RNA registration (at 612). The RNA information 614 may include, without limitation, and AMF address of the AMF 606, a SUPI of the AMF 606, the RNA security context 616 (e.g., for security and integrity protection of RNA message), and / or the like. In aspects, subsequent to registration (and at 612), the UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, the RNA security context 616, which may be provided to the RNS 604 by theAMF 606. In aspects, the RNA security context 616 may be the same as the NAS security context 609, may be based on the NAS security context 609, or may be different than the NAS security context 609.

[0170] At 1406, the UE monitors for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages. As an example, the monitor may be performed by one or more of the component 198, the transceiver(s) 1522, and / or the antennas 1580 in FIG. 15. FIG. 6 illustrates, in the context of FIGs. 7-10, an example of the UE 602 monitoring for such RNA messages on a second channel.

[0171] In aspects, and subsequent to the RNA registration (at 612), the UE 602 may be configured to monitor (at 618) for an RNA message(s) (e.g., the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9)). The UE 602 may be configured to monitor (at 618) for RNA messages on a second channel that is different than a first channel for paging messages. In aspects, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) may carry more information than the paging messages and / or at least some information not included in the paging message (e.g., a caller identifier, a call type, a time stamp, a limited word SMS message, and / or the like). In some aspects, the second channel may be configured for DL transmissions and not for UL transmissions. The AMF 606 may be configured to receive an indication 620 (e.g., 714 in FIG. 7) of data for transmission to at least one UE (e.g., including the UE 602). The AMF 606 may be configured to perform and / or provide (at 622) a paging / service request(s) / message(s) (e.g., 716 in FIG. 7) (e.g., via the network node 698) for the UE 602, as described in further detail herein. As one example, the AMF 606 may be configured to provide (at 622), to a RAN node (e.g., the network node 698) in an NTN, one or more paging messages (e.g., 715 in FIG. 7) for the UE 602 in a first container type associated with delivery on a first channel. Based on a failure of the performance (at 622) of the paging / service request (e.g., 716 in FIG. 7), by the network node 698, for the UE 602 (e.g., based on deep coverage of the UE 602 in the NTN, UL failure of the UE 602 during the paging process, etc.), an indication 624 (e.g., 726 in FIG. 7) thereof may be provided to and received by the RNS 604. That is, the indication 624 (e.g., 726 in FIG. 7) may indicate that the UE 602 is not reachable via regular paging operations (e.g., 716 in FIG. 7). The RNS 604 may be configured to receive the indication 624 (e.g., 726 in FIG. 7) of the paging failure (e.g., 716 in FIG. 7) for theUE 602, and based at least in part thereon, the RNS 604 may be configured to transmit / provide, and the UE 602 may be configured to receive, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9), e.g., via the AMF 606 and the network node 698, as described in further detail herein. The RNA message 626 (and / or the RNA body thereof) (e.g., 820 in FIG. 8; 918 in FIG. 9) may be transmitted / received via NAS message protocol from the RNS 604 to the AMF 606 to the network node 698, and to the UE 602. In aspects, the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) may include information associated with the incoming message 618, such as but without limitation, one or more of a caller identifier (ID) associated with of the caller of a call for the UE 602, a type of call for the UE 602, a time stamp associated with the call, an SMS message for the UE 602 having a number of words that is less than a threshold, and / or the like. The UE 602 may be configured to check an integrity of and decipher (at 628) the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). In aspects, the UE 602 may be configured to check an integrity of the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) and to decipher the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9) (e.g., at 628) based on the last used NAS security context (e.g., the NAS security context 609) of the UE 602. The UE 602 may be configured to transmit / provide, and the AMF 606 may be configured to receive, a service / registration request 630 (e.g., 822 in FIG. 8; 920 in FIG. 9) based on reception of the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The UE 602 may also be configured to transmit / provide, and the AMF 606 may be configured to receive, a response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9), e.g., via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), for the RNS 604 for one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) may an UL NAS transport that includes a delivery report associated with the one or more RNA messages including the RNA message 626 (e.g., 820 in FIG. 8; 918 in FIG. 9). The AMF 606 may be configured to transmit / provide, and the RNS 604 may be configured to receive, a delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9), e.g., based on the response 632 (e.g., 824 in FIG. 8; 922 in FIG. 9) and / or via an RNA message protocol (e.g., 1008, 1010 in FIG. 10), and the RNS 604 may in turn forward the delivery report 634 (e.g., 826 in FIG. 8; 924 in FIG. 9) to the IMS or another network entity. In aspects, the RNA message protocol (e.g., 1008, 1010 in FIG. 10) may be a protocol dedicated for RNA messages, e.g., an RNA-specific protocol (e.g., 1008, 1010 in FIG. 10), and / or may be a protocol that is on top of, and / or transparent to, the NAS protocol.

[0172] FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include at least one cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceiver). The cellular baseband processor(s) 1524 may include at least one on-chip memory 1524'. In some aspects, the apparatus 1504 may further include one or more subscriber identity modules (SIM) cards 1520 and at least one application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor(s) 1506 may include on-chip memory 1506'. In some aspects, the apparatus 1504 may further include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., GNSS module), one or more sensor modules 1518 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and / or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies used for positioning), additional memory modules 1526, a power supply 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or utilize the antennas 1580 for communication. The cellular baseband processor(s) 1524 communicates through the transceiver(s) 1522 via one or more antennas 1580 with the UE 104 and / or with an RU associated with a network entity 1502. The cellular baseband processor(s) 1524 and the application processor(s) 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory modules 1526 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor(s) 1524 and the application processor(s) 1506 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor(s) 1524 / application processor(s) 1506,causes the cellular baseband processor(s) 1524 / application processor(s) 1506 to perform the various functions described supra. The cellular baseband processor(s) 1524 and the application processor(s) 1506 are configured to perform the various functions described supra based at least in part of the information stored in the memory. That is, the cellular baseband processor(s) 1524 and the application processor(s) 1506 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor(s) 1524 / application processor(s) 1506 when executing software. The cellular baseband processor(s) 1524 / application processor(s) 1506 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1504 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, and in another configuration, the apparatus 1504 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1504.

[0173] As discussed supra, the component 198 may be configured to enter a CM idle mode. The component 198 may be configured to transmit an indication of support for an RNA. The component 198 may be configured to monitor for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages. The component 198 may be configured to check an integrity of the RNA message and deciphering the RNA message based on the last used NAS security context of the UE. The component 198 may be configured to receive the RNA message on the second channel that is different than the first channel for the paging messages. The component 198 may be configured to transmit a registration request based on reception of the RNA message. The component 198 may be configured to provide a response for a robust notification alert service for one or more RNA messages including the RNA message. The component 198 may be further configured to perform any of the aspects described in connection with the flowcharts in FIGs. 11, 12, 13, 14, and / or any of theaspects performed by a UE, for any of FIGs. 4-10. The component 198 may be within the cellular baseband processor(s) 1524, the application processor(s) 1506, or both the cellular baseband processor(s) 1524 and the application processor(s) 1506. The component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer- readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1504 may include a variety of components configured for various functions. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for entering a CM idle mode. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for transmitting an indication of support for an RNA. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for monitoring for an RNA message on a second channel that is different than a first channel for paging messages, where the RNA message carries at least some information not included in the paging messages. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for checking an integrity of the RNA message and deciphering the RNA message based on the last used NAS security context of the UE. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for receiving the RNA message on the second channel that is different than the first channel for the paging messages. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for transmitting a registration request based on reception of the RNA message. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and / or the application processor(s) 1506, may include means for providing a response for a robust notification alert service for one or more RNA messages including the RNA message. The means may be the component 198of the apparatus 1504 configured to perform the functions recited by the means. As described supra, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0174] FIG. 16 is a diagram 1600 illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or an RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include the CU 1610; both the CU 1610 and the DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both the DU 1630 and the RU 1640; or the RU 1640. The CU 1610 may include at least one CU processor 1612. The CU processor(s) 1612 may include on-chip memory 1612'. In some aspects, the CU 1610 may further include additional memory modules 1614 and a communications interface 1618. The CU 1610 communicates with the DU 1630 through a midhaul link, such as an Fl interface. The DU 1630 may include at least one DU processor 1632. The DU processor(s) 1632 may include on-chip memory 1632'. In some aspects, the DU 1630 may further include additional memory modules 1634 and a communications interface 1638. The DU 1630 communicates with the RU 1640 through a fronthaul link. The RU 1640 may include at least one RU processor 1642. The RU processor(s) 1642 may include on-chip memory 1642'. In some aspects, the RU 1640 may further include additional memory modules 1644, one or more transceivers 1646, antennas 1680, and a communications interface 1648. The RU 1640 communicates with the UE 104. The on-chip memory 1612', 1632', 1642' and the additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1612, 1632, 1642 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.

[0175] As discussed supra, the component 199 may be configured to receive one or more paging messages in a first container type for paging one or more user UEs. The component 199 may be configured to transmit the one or more paging messages on a first channel that are intended for one or more UEs. The component 199 may be configured to receive an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. The component 199 may be configured to transmit the RNA message for said the one or more UEs on the second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels. The component 199 may be further configured to perform any of the aspects described in connection with the flowcharts in FIGs. 11, 12, 13, 14, and / or any of the aspects performed by a network entity, such as a network / RAN (e.g., a base station, eNB, gNB, sNB, etc.), for any of FIGs. 4- 10. The component 199 may be within one or more processors of one or more of the CU 1610, DU 1630, and the RU 1640. The component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 may include means for receiving one or more paging messages in a first container type for paging one or more user UEs. In one configuration, the network entity 1602 may include means for transmitting the one or more paging messages on a first channel that are intended for one or more UEs. In one configuration, the network entity 1602 may include means for receiving an RNA message in a second container type for the one or more UEs, where the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel. In one configuration, the network entity 1602 may include means for transmitting the RNA message for saidthe one or more UEs on the second channel that is different than the first channel, and where the network node has a first logical channel for paging and a second logical channel for RNA messages, where the first logical channel and the second logical channel have a different mapping to physical channels. The means may be the component 199 of the network entity 1602 configured to perform the functions recited by the means. As described supra, the network entity 1602 may include the TX processor 316, the RX processor 370, and the controller / processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0176] FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for a network entity 1760. In one example, the network entity 1760 may be within the core network 120. The network entity 1760 may include at least one network processor 1712. The network processor(s) 1712 may include on-chip memory 1712'. In some aspects, the network entity 1760 may further include additional memory modules 1714. The network entity 1760 communicates via the network interface 1780 directly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU 1702, and / or with the UE 104. The on-chip memory 1712' and the additional memory modules 1714 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The network processor(s) 1712 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) when executing software.

[0177] As discussed supra, the component 199, e.g., for a network service (e.g., an RNS), may be configured to receive, from a network function, an indication upon a paging failure associated with a paging message for a UE in an NTN. The component 199 may be configured to provide, to at least one AMF, an RNA message for the UE, where the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service. The component 199 may be configured to receive, from the AMF prior to theRNA message, one or more of an AMF address for RNAs for the UE, a SUPI for the UE, or a UE security context for the UE. The component 199 may be configured to protect the RNA message based on a last used NAS security context of the UE. The component 199 may be configured to provide the RNA message to an AMF that last served the UE. The component 199 may be configured to receive the RNA message with security protection from the AMF that last served the UE. The component 199 may be configured to provide, to multiple AMFs, the RNA message with the security protection. The component 199 may be configured to receive a response from the UE for one or more RNA messages. The component 199, e.g., for a network function (e.g., an AMF), may be configured to receive an indication of data for transmission to at least one UE. The component 199 may be configured to provide, to a RAN node in an NTN, one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel. The component 199 may be configured to receive, from a network service, an RNA message for one or more UEs. The component 199 may be configured to provide, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages. The component 199 may be configured to continue to provide the RNA message until a timer expires. The component 199 may be configured to cease to provide the RNA message based on an expiration of the timer. The component 199 may be configured to receive a support indication, from the one or more UEs, that the UE supports RNA. The component 199 may be configured to select the network service for the RNA. The component 199 may be configured to provide, to the network service prior to receipt of the RNA message, one or more of an AMF address for RNAs for the one or more UEs, a SUPI for the one or more UEs, or a UE security context for the one or more UEs. The component 199 may be configured to receive the RNA message from the network service. The component 199 may be configured to provide, to the network service, the RNA message with security protection, where the RNA message received from the network service includes the security protection. The component 199 may be configured to receive a response from a UE of the one or more UEs, wherein the response is for one or more RNA messages including the RNA message. The component 199 may be configured to provide the response to the network service. The component 199 may be further configured to perform any of theaspects described in connection with the flowcharts in FIGs. 11, 12, 13, 14, and / or any of the aspects performed by a network entity, such as a network service (e.g., an RNS) and / or a network function (e.g., an AMF), for any of FIGs. 4-10. The component 199 may be within the network processor(s) 1712. The component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. The network entity 1760 may include a variety of components configured for various functions. In one configuration, the network entity 1760, e.g., for a network service (e.g., an RNS), may include means for receiving, from a network function, an indication upon a paging failure associated with a paging message for a UE in an NTN. In one configuration, the network entity 1760 may include means for providing, to at least one AMF, an RNA message for the UE, where the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service. In one configuration, the network entity 1760 may include means for receiving, from the AMF prior to the RNA message, one or more of an AMF address for RNAs for the UE, a SUPI for the UE, or a UE security context for the UE. In one configuration, the network entity 1760 may include means for protecting the RNA message based on a last used NAS security context of the UE. In one configuration, the network entity 1760 may include means for providing the RNA message to an AMF that last served the UE. In one configuration, the network entity 1760 may include means for receiving the RNA message with security protection from the AMF that last served the UE. In one configuration, the network entity 1760 may include means for providing, to multiple AMFs, the RNA message with the security protection. In one configuration, the network entity 1760 may include means for receiving a response from the UE for one or more RNA messages.

[0178] In one configuration, the network entity 1760, e.g., for a network function (e.g., an AMF), may include means for receiving an indication of data for transmission to at least one UE. In one configuration, the network entity 1760 may include means for providing, to a RAN node in an NTN, one or more paging messages for the at leastone UE in a first container type associated with delivery on a first channel. In one configuration, the network entity 1760 may include means for receiving, from a network service, an RNA message for one or more UEs. In one configuration, the network entity 1760 may include means for providing, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages. In one configuration, the network entity 1760 may include means for continuing to provide the RNA message until a timer expires. In one configuration, the network entity 1760 may include means for ceasing to provide the RNA message based on an expiration of the timer. In one configuration, the network entity 1760 may include means for receiving a support indication, from the one or more UEs, that the UE supports RNA. In one configuration, the network entity 1760 may include means for selecting the network service for the RNA. In one configuration, the network entity 1760 may include means for providing, to the network service prior to receipt of the RNA message, one or more of an AMF address for RNAs for the one or more UEs, a SUPI for the one or more UEs, or a UE security context for the one or more UEs. In one configuration, the network entity 1760 may include means for receiving the RNA message from the network service. In one configuration, the network entity 1760 may include means for providing, to the network service, the RNA message with security protection, where the RNA message received from the network service includes the security protection. In one configuration, the network entity 1760 may include means for receiving a response from a UE of the one or more UEs, wherein the response is for one or more RNA messages including the RNA message. In one configuration, the network entity 1760 may include means for providing the response to the network service. The means may be the component 199 of the network entity 1760 configured to perform the functions recited by the means.

[0179] Wireless communication networks that support communications between network entities (e.g., network nodes such as base stations, eNBs, gNBs, etc.; entities in a core network) and UEs, may extend such communications via Internet-based services such as an IMS. For instance, a UE may be in a 5G system with satellite access, such as via an NTN, which facilitates wireless communications of the UE. However, the UE may be in an environment / location such that the NTN coverage of the UE is poor. For instance, if the UE goes into deep coverage for the NTN or enters a CM IDLE mode,the UE may be unable to receive or respond to paging requests for MT MMTEL. In such scenarios, the UE may not receive, or be notified of, the attempted communications.

[0180] Aspects herein for RNA messages for UEs in an NTN improve on / remediate the issues noted above. For example, aspects enable providing a UE with alert messaging when in deep coverage of an NTN by enabling an RNS to provide RNA messages. Aspects also enable providing a UE with alert messaging securely and in varied UE environment scenarios by enabling RNS interactions with an AMF. In such aspects, an RNS is enabled to forward reachability requests and payloads directly to an AMF by extending beyond MT SMS messaging over NAS for paging failures due to deep coverage, UL failure, etc.. Aspects also enable providing a UE with alert messaging from an RNS that includes missed communication details by enabling RNS interactions with an IMS.

[0181] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

[0182] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unlessspecifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,”“element,” “device,” and the like may not be a substitute for the word “means.” Assuch, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0183] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

[0184] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

[0185] Aspect 1 is a method of wireless communication at a network service, comprising: receiving, from a network function, an indication upon a paging failure associated with a paging message for a user equipment (UE) in a non-terrestrial network (NTN); and providing, to at least one access and mobility function (AMF), a robust notification alert (RNA) message for the UE, wherein the RNA message carries at least some information not included in the paging message and notifies the UE at least for the missed paging attempt for the network service.

[0186] Aspect 2 is the method of aspect 1, wherein the network service is a robust notification service (RNS) associated with one or more NTNs.

[0187] Aspect 3 is the method of any of aspects 1 and 2, wherein the network function comprises an internet protocol multimedia subsystem (IMS).

[0188] Aspect 4 is the method of any of aspects 1 to 3, wherein the RNA message for the UE further includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

[0189] Aspect 5 is the method of any of aspects 1 to 4, further comprising: receiving, from the AMF prior to the RNA message, one or more of an AMF address for RNAs for the UE, a subscription permanent identifier (SUPI) for the UE, or a UE security context for the UE.

[0190] Aspect 6 is the method of any of aspects 1 to 5, further comprising: protecting the RNA message based on a last used non-access stratum (NAS) security context of the UE.

[0191] Aspect 7 is the method of any of aspects 1 to 5, wherein providing the RNA message for the UE includes: providing the RNA message to an AMF that last served the UE;receiving the RNA message with security protection from the AMF that last served the UE; and providing, to multiple AMFs, the RNA message with the security protection.

[0192] Aspect 8 is the method of any of aspects 1 to 7, wherein providing the RNA message to the at least one AMF includes providing the RNA message to a last serving AMF for the UE.

[0193] Aspect 9 is the method of any of aspects 1 to 7, wherein providing the RNA message to the at least one AMF includes providing the RNA message to multiple AMFs based on at least one registration area.

[0194] Aspect 10 is the method of any of aspects 1 to 9, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

[0195] Aspect 11 is the method of any of aspects 1 to 10, further comprising: receiving a response from the UE for one or more RNA messages.

[0196] Aspect 12 is a method of wireless communication at an access and mobility function (AMF), comprising: receiving an indication of data for transmission to at least one user equipment (UE); providing, to a radio access network (RAN) node in a nonterrestrial network (NTN), one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel; receiving, from a network service, a robust notification alert (RNA) message for one or more UEs; and providing, to the RAN node, the RNA message for the one or more UEs in a second container type associated with a delivery on a second channel that is different than the first channel for the one or more paging messages.

[0197] Aspect 13 is the method of aspect 12, further comprising: continuing to provide the RNA message until a timer expires; and ceasing to provide the RNA message based on an expiration of the timer.

[0198] Aspect 14 is the method of any of aspects 12 and 13, wherein the network service is a robust notification service (RNS) associated with one or more NTNs.

[0199] Aspect 15 is the method of any of aspects 12 to 14, wherein the RNA message for each UE includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

[0200] Aspect 16 is the method of any of aspects 12 to 15, further comprising: receiving a support indication, from the one or more UEs, that the UE supports RNA; selecting the network service for the RNA; and providing, to the network service prior to receipt of the RNA message, one or more of an AMF address for RNAs for the one or more UEs, a subscription permanent identifier (SUPI) for the one or more UEs, or a UE security context for the one or more UEs.

[0201] Aspect 17 is the method of aspect 16, wherein the RNA message received from the network service includes security based on a last used non-access stratum (NAS) security context of the one or more UEs.

[0202] Aspect 18 is the method of any of aspects 12 to 16, wherein the AMF is a last serving AMF for the UE, the method further comprising: receiving the RNA message from the network service; and providing, to the network service, the RNA message includes the security protection, wherein the RNA message received from the network service with security protection.

[0203] Aspect 19 is the method of any of aspects 12 to 16, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

[0204] Aspect 20 is the method of any of aspects 12 to 19, further comprising: receiving a response from a UE of the one or more UEs, wherein the response is for one or more RNA messages including the RNA message; and providing the response to the network service.

[0205] Aspect 21 is a method of wireless communication at a network node of a nonterrestrial network (NTN) receiving one or more paging messages in a first container type for paging one or more user equipments (UEs); transmitting the one or more paging messages on a first channel that are intended for one or more UEs; receiving a robust notification alert (RNA) message in a second container type for the one or more UEs, wherein the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel; and transmitting the RNA message for said the one or more UEs on the second channel that is different than the first channel, and wherein the network node has a first logical channel for paging and a second logical channel for RNA messages, wherein the first logical channel and the second logical channel have a different mapping to physical channels.

[0206] Aspect 22 is the method of aspect 21, wherein the RNA message for each UE of the one or more UEs includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

[0207] Aspect 23 is a method of wireless communication at a user equipment (UE), comprising: entering a connection management (CM) idle mode; transmitting an indication of support for a robust notification alert (RNA); and monitoring for an RNA message on a second channel that is different than a first channel for paging messages, wherein the RNA message carries at least some information not included in the paging messages.

[0208] Aspect 24 is the method of aspect 23, wherein the second channel is configured for downlink transmissions and not uplink transmissions.

[0209] Aspect 25 is the method of any of aspects 23 and 24, wherein the RNA message includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message for the UE having a number of words that is less than a threshold.

[0210] Aspect 26 is the method of any of aspects 23 to 25, wherein the RNA message includes security based on a last used non-access stratum (NAS) security context of the UE.

[0211] Aspect 27 is the method of any of aspects 23 to 26, further comprising: checking an integrity of the RNA message and deciphering the RNA message based on the last used NAS security context of the UE.

[0212] Aspect 28 is the method of any of aspects 23 to 27, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

[0213] Aspect 29 is the method of any of aspects 23 to 28, further comprising: receiving the RNA message on the second channel that is different than the first channel for the paging messages.

[0214] Aspect 30 is the method of any of aspects 23 to 29, further comprising: transmitting a registration request based on reception of the RNA message; and providing a response for a robust notification alert service for one or more RNA messages including the RNA message.

[0215] Aspect 31 is an apparatus for wireless communication at a network service, comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 1 to 11.

[0216] Aspect 32 is an apparatus for wireless communication at a network service, comprising means for performing each step in the method of any of aspects 1 to 11.

[0217] Aspect 33 is the apparatus of any of aspects 31 to 32, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 1 to 11.

[0218] Aspect 34 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a network service, the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 1 to 11.

[0219] Aspect 35 is an apparatus for wireless communication at an access and mobility function (AMF), comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 12 to 20.

[0220] Aspect 36 is an apparatus for wireless communication at an access and mobility function (AMF), comprising means for performing each step in the method of any of aspects 12 to 20.

[0221] Aspect 37 is the apparatus of any of aspects 35 to 36, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 12 to 20.

[0222] Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at an access and mobility function (AMF), the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 12 to 20.

[0223] Aspect 39 is an apparatus for wireless communication at a network node of a nonterrestrial network (NTN), comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 21 to 22.

[0224] Aspect 40 is an apparatus for wireless communication at a network node of a nonterrestrial network (NTN), comprising means for performing each step in the method of any of aspects 21 to 22.

[0225] Aspect 41 is the apparatus of any of aspects 39 to 40, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 21 to 22.

[0226] Aspect 42 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a network node of a non-terrestrial network (NTN), the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 21 to 22.

[0227] Aspect 43 is an apparatus for wireless communication at a user equipment (UE), comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 23 to 30.

[0228] Aspect 44 is an apparatus for wireless communication at a user equipment (UE), comprising means for performing each step in the method of any of aspects 23 to 30.

[0229] Aspect 45 is the apparatus of any of aspects 43 to 44, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 23 to 30.

[0230] Aspect 46 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a user equipment (UE), the code when executed by at least one processor causes the at least one processor to perform the method of any of aspects 23 to 30.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a network service, comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to: receive, from a network function, an indication upon a paging failure associated with a paging message for a user equipment (UE) in a non-terrestrial network (NTN); and provide, to at least one access and mobility function (AMF), a robust notification alert (RNA) message for the UE, wherein the RNA message carries at least some information not included in the paging message and notifies the UE at least for a missed paging attempt for the network service.

2. The apparatus of claim 1, wherein the network service is a robust notification service (RNS) associated with one or more NTNs.

3. The apparatus of claim 1, wherein the network function comprises an internet protocol multimedia subsystem (IMS).

4. The apparatus of claim 1, wherein the RNA message for the UE further includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

5. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to:receive, from the AMF prior to the RNA message, one or more of an AMF address for RNAs for the UE, a subscription permanent identifier (SUPI) for the UE, or a UE security context for the UE.

6. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: protect the RNA message based on a last used non-access stratum (NAS) security context of the UE.

7. The apparatus of claim 1, wherein to provide the RNA message for the UE, wherein the at least one processor, individually or in any combination, is configured to: provide the RNA message to an AMF that last served the UE; receive the RNA message with security protection from the AMF that last served the UE; and provide, to multiple AMFs, the RNA message with the security protection.

8. The apparatus of claim 1, wherein to provide the RNA message to the at least one AMF, wherein the at least one processor, individually or in any combination, is configured to provide the RNA message to a last serving AMF for the UE.

9. The apparatus of claim 1, wherein to provide the RNA message to the at least one AMF, wherein the at least one processor, individually or in any combination, is configured to provide the RNA message to multiple AMFs based on at least one registration area.

10. The apparatus of claim 1, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

11. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: receive a response from the UE for one or more RNA messages.

12. An apparatus for wireless communication at an access and mobility function (AMF), comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to: receive an indication of data for transmission to at least one user equipment (UE); provide, to a radio access network (RAN) node in a non-terrestrial network(NTN), one or more paging messages for the at least one UE in a first container type associated with delivery on a first channel; receive, from a network service, a robust notification alert (RNA) message for one or more UEs; and provide, to the RAN node, the RNA message for the one or more UEs in a second container type associated with delivery on a second channel that is different than the first channel for the one or more paging messages.

13. The apparatus of claim 12, wherein the at least one processor, individually or in any combination, is further configured to: continue to provide the RNA message until a timer expires; and cease to provide the RNA message based on an expiration of the timer.

14. The apparatus of claim 12, wherein the network service is a robust notification service (RNS) associated with one or more NTNs.

15. The apparatus of claim 12, wherein the RNA message for each UE includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

16. The apparatus of claim 12, wherein the at least one processor, individually or in any combination, is further configured to: receive a support indication, from the one or more UEs, that the UE supports RNA; select the network service for the RNA; and provide, to the network service prior to receipt of the RNA message, one or more of an AMF address for RNAs for the one or more UEs, a subscription permanent identifier (SUPI) for the one or more UEs, or a UE security context for the one or more UEs.

17. The apparatus of claim 16, wherein the RNA message received from the network service includes security based on a last used non-access stratum (NAS) security context of the one or more UEs.

18. The apparatus of claim 12, wherein the AMF is a last serving AMF for the UE, wherein the at least one processor, individually or in any combination, is further configured to: receive the RNA message from the network service; and provide, to the network service, the RNA message with security protection, wherein the RNA message received from the network service includes the security protection.

19. The apparatus of claim 12, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

20. The apparatus of claim 12, wherein the at least one processor, individually or in any combination, is further configured to: receive a response from a UE of the one or more UEs, wherein the response is for one or more RNA messages including the RNA message; and provide the response to the network service.

21. An apparatus for wireless communication at a network node of a non-terrestrial network (NTN), comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to: receive one or more paging messages in a first container type for paging one or more user equipments (UEs); transmit the one or more paging messages on a first channel that are intended for the one or more UEs; receive a robust notification alert (RNA) message in a second container type for the one or more UEs, wherein the second container type indicates for the network node to transmit the RNA message on a second channel that is different than the first channel; and transmit the RNA message for said the one or more UEs on the second channel that is different than the first channel, and wherein the network node has a first logical channel for paging and a second logical channel for RNA messages, wherein the first logical channel and the second logical channel have a different mapping to physical channels.

22. The apparatus of claim 21, wherein the RNA message for each UE of the one or more UEs includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message having a number of words that is less than a threshold.

23. An apparatus for wireless communication at a user equipment (UE), comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to:enter a connection management (CM) idle mode; transmit an indication of support for a robust notification alert (RNA); and monitor for an RNA message on a second channel that is different than a first channel for paging messages, wherein the RNA message carries at least some information not included in the paging messages.

24. The apparatus of claim 23, wherein the second channel is configured for downlink transmissions and not uplink transmissions.

25. The apparatus of claim 23, wherein the RNA message includes one or more of: a caller identifier (ID) associated with a call for the UE, a type of the call for the UE, a time stamp, or a short message service (SMS) message for the UE having a number of words that is less than a threshold.

26. The apparatus of claim 23, wherein the RNA message includes security based on a last used non-access stratum (NAS) security context of the UE.

27. The apparatus of claim 26, wherein the at least one processor, individually or in any combination, is further configured to: check an integrity of the RNA message and deciphering the RNA message based on the last used NAS security context of the UE.

28. The apparatus of claim 23, wherein the RNA message is based on a protocol dedicated for RNA messages, and wherein the protocol is on top of a non-access stratum (NAS) protocol.

29. The apparatus of claim 23, further comprising at least one transceiver coupled to the at least one processor, wherein the at least one processor, individually or in any combination, is further configured to: receive, via the at least one transceiver, the RNA message on the second channel that is different than the first channel for the paging messages.

30. The apparatus of claim 23, wherein the at least one processor, individually or in any combination, is further configured to: transmit a registration request based on reception of the RNA message; and provide a response for a robust notification alert service for one or more RNA messages including the RNA message.

Images