Emergency communication via a non-terrestrial network

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, an apparatus at a user equipment (UE) may generate a message that includes data associated with a session initiation invite for a public safety answering point (PSAP). The apparatus at the UE may transmit the message via a non-terrestrial network. Numerous other aspects are described.

Description

EMERGENCY COMMUNICATION VIA A NON-TERRESTRIAL NETWORKCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to India Patent Application No. 202341054709, filed on August 15, 2023, entitled “EMERGENCY COMMUNICATION VIA A NON-TERRESTRIAL NETWORK,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.INTRODUCTION

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for emergency communication.

[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 (e.g., bandwidth, transmit power, or the like). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated bythe 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.SUMMARY

[0006] Some aspects described herein relate to a method of wireless communication performed at an apparatus of a user equipment (UE). The method may include generating a message that includes data associated with a session initiation invite for a public safety answering point (PSAP). The method may include transmitting the message via a nonterrestrial network.

[0007] Some aspects described herein relate to a method of wireless communication performed at an apparatus of a device. The method may include obtaining a message that includes data associated with a session initiation invite for a PSAP. The method may include generating the session initiation invite using the data associated with the session initiation invite in the message.

[0008] Some aspects described herein relate to a method of wireless communication performed at an apparatus of a UE. The method may include transmitting a request to establish a real-time text (RTT) communication channel for communication between the UE and a PSAP. The method may include communicating with the PSAP via the RTT communication channel.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to generate a message that includes data associated with a session initiation invite for a PSAP. The one or more processors may be individually or collectively operable to transmit the message via a non-terrestrial network.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the device to obtain a message that includes data associated with a session initiation invite for a PSAP. The one or more processors may be individually or collectively operable to generate thesession initiation invite using the data associated with the session initiation invite in the message.

[0011] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to transmit a request to establish an RTT communication channel for communication between the UE and a PSAP. The one or more processors may be individually or collectively operable to communicate with the PSAP via the RTT communication channel.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to generate a message that includes data associated with a session initiation invite for a PSAP. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit the message via a non-terrestrial network.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a device. The set of instmctions, when executed by one or more processors of the device, may cause the device to obtain a message that includes data associated with a session initiation invite for a PSAP. The set of instructions, when executed by one or more processors of the device, may cause the device to generate the session initiation invite using the data associated with the session initiation invite in the message.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit a request to establish an RTT communication channel for communication between the UE and a PSAP. The set of instructions, when executed by one or more processors of the UE, may cause the UE to communicate with the PSAP via the RTT communication channel.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for generating a message that includes data associated with a session initiation invite for a PSAP. The apparatus may include means for transmitting the message via a non-terrestrial network.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining a message that includes data associated with a session initiation invite for a PSAP. The apparatus may include means for generating the session initiation invite using the data associated with the session initiation invite in the message.

[0017] Some aspects described herein relate to an apparatus for wireless communication.The apparatus may include means for transmitting a request to establish an RTT communication channel for communication between the apparatus and a PSAP. The apparatus may include means for communicating with the PSAP via the RTT communication channel.

[0018] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described with reference to and as illustrated by the drawings and specification.

[0019] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0020] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0021] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0022] Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0023] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0024] Fig. 4 is a diagram illustrating an example of a regenerative satellite deployment and an example of a transparent satellite deployment in a non-terrestrial network (NTN).

[0025] Fig. 5 is a diagram illustrating an example of an emergency calling system, in accordance with the present disclosure.

[0026] Fig. 6 is a diagram illustrating an example associated with emergency communication via an NTN, in accordance with the present disclosure.

[0027] Fig. 7 is a flowchart illustrating an example associated with emergency communication via an NTN, in accordance with the present disclosure.

[0028] Fig. 8 is a flowchart illustrating an example associated with emergency communication via an NTN, in accordance with the present disclosure.

[0029] Fig. 9 is a flowchart illustrating an example associated with emergency communication via an NTN, in accordance with the present disclosure.

[0030] Fig. 10 is a diagram illustrating an example associated with emergency communication via an NTN, in accordance with the present disclosure.

[0031] Fig. 11 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0032] Fig. 12 is a diagram illustrating an example process performed, for example, by a device, in accordance with the present disclosure.

[0033] Fig. 13 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0034] Fig. 14 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0035] Fig. 15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with the present disclosure.

[0036] Fig. 16 is a diagram illustrating an example of an implementation of code and circuitry for an apparatus, in accordance with the present disclosure.

[0037] Fig. 17 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0038] Fig. 18 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with the present disclosure.

[0039] Fig. 19 is a diagram illustrating an example of an implementation of code and circuitry for an apparatus, in accordance with the present disclosure.DETAILED DESCRIPTION

[0040] A user equipment (UE) may be configured to share information with a public safety answering point (PSAP) in the event of an emergency. For example, the UE may be included in a vehicle, and in the event of an emergency involving the vehicle, the UE may share vehicle- related information with the PSAP. A vehicle may include an automobile, a boat, an aircraft, a train, or the like. The PSAP is a physical location, where emergency calls from the public arereceived. The PSAP may include one or more devices that handle incoming emergency communications.

[0041] In an example where the UE is included in a vehicle, if the vehicle is involved in a collision, the UE may be configured to automatically make an emergency call or “eCall” (e.g., a call placed to an emergency number, such as 911 in the United States) to the PSAP and provide vehicle-related information. For example, the UE may transmit a session initiation invite to the PSAP. A session initiation invite may refer to a request to initiate a call. For example, the session initiation invite may indicate a request to establish a voice communication session (e.g., a call) between the UE and the PSAP. According to one or more examples, the session initiation invite may include a “minimum set of data” (MSD) that indicates the vehicle-related information. For example, the MSD may include a standardized set of information that is transmitted by the UE in connection with an emergency call. The vehicle-related information may include airbag deployment information, impact sensor information, location information, vehicle identification information, and / or passenger information, among other examples. The vehicle-related information may bring quicker assistance to passengers in the vehicle. For example, emergency first responders may know a location of the vehicle, a seriousness of the collision, how many passengers are in the vehicle, which airbags deployed, a direction and magnitude of impact, or the like.

[0042] According to one or more examples, the UE may transmit the session initiation invite with the MSD via a terrestrial network (TN) that supports voice calling. However, the UE (e.g., the vehicle that includes the UE) sometimes may be in a remote location where service for a TN is unavailable to the UE. In other cases, service for the TN may be available, but a voice call attempted by the UE may fail. In such instances, service for a non-terrestrial network (NTN) may be available to the UE. However, the NTN may not support voice calling. Accordingly, coverage for emergency communications may be inconsistent, particularly in remote areas. “Terrestrial network” may refer to a wireless communication network that operates using primarily land-based network infrastructure. “Non-terrestrial network” may refer to a wireless communication network that operates using satellite-based, or other aerial-based, network infrastructure.

[0043] Some techniques and apparatuses described herein enable a UE to perform emergency communication via an NTN. In some aspects, if the UE is present at an area where there is a lack of voice coverage, the UE may generate a message that includes data associated with a session initiation invite for a PSAP (e.g., the message may include at least an MSD of the session initiation invite). According to one or more examples, the message may be a short messaging service (SMS) message, or another type of message that is supported by the NTN. Rather than transmitting the session initiation invite, the UE may transmit, via the NTN and to a PSAP, the message that includes the data associated with the session initiation invite. In someaspects, a network node associated with the NTN and / or the PS AP may include a component to generate the session initiation invite (e.g., including the MSD) using the data associated with the session initiation invite in the message. For example, the network node may receive the message transmitted by the UE, generate the session initiation invite using the data associated with the session initiation invite in the message, and transmit the session initiation invite to the PSAP. As another example, the network node may receive the message and transmit the message to the PSAP, and the PSAP may generate the session initiation invite using the data associated with the session initiation invite in the message. In this way, emergency communication that uses the session initiation invite may be performed via the NTN. Using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas).

[0044] In some aspects, the UE may transmit the message via the NTN in one or more narrowband NTN bands, thereby conserving power and improving a performance of the message. In some aspects (e.g., after the PSAP obtains the session initiation invite including the MSD), the UE may transmit, to a network node, a request to establish a real-time text (RTT) communication channel for communication between the UE and the PSAP. Accordingly, the UE may communicate with the PSAP via the RTT communication channel rather than via a voice communication channel, which may not be supported by the NTN. In this way, the UE and the PSAP may exchange information (e.g., vehicle-related information, announcements, or the like) via the NTN. As described above, using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas). Moreover, the RTT communication channel may use a low bandwidth relative to the voice communication channel, thereby conserving network resources.

[0045] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0046] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0047] While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0048] Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and / or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0049] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. A network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission receptionpoint (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

[0050] In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a network node 110 and / or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).

[0051] In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “basestation” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0052] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 1 lOd (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.

[0053] The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0054] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0055] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainmentdevice (e.g., a music device, a video device, and / or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device that is configured to communicate via a wireless or wired medium.

[0056] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and / or an eMTC UE may include, for example, a robot, an unmanned aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Intemet-of-Things (loT) devices, and / or may be implemented as NB-IoT (narrowband loT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0057] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0058] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device -to -device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and / or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and / or other operations described herein as being performed by the network node 110.

[0059] The electromagnetic spectrum is often subdivided, by frequency / wavelength, into various classes, bands, channels, etc. In 5G NR, 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). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is 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.

[0060] 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 mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz).Each of these higher frequency bands falls within the EHF band.

[0061] With the above examples in mind, unless specifically stated otherwise, it should be understood that 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, it should be understood that 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, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

[0062] In some aspects, the UE 120 may include a communication manager 140. As described in more detail herein, the communication manager 140 may generate a message that includes data associated with a session initiation invite for a PSAP; and transmit the message via an NTN. As described in more detail herein, the communication manager 140 may transmit a request to establish an RTT communication channel for communication between the UE 120 and a PSAP; and communicate with the PSAP via the RTT communication channel. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0063] In some aspects, the network node 110 may include a communication manager 150. In some aspects, a PSAP may include the communication manager 150. As described in more detail herein, the communication manager 150 may obtain a message that includes data associated with a session initiation invite for a PSAP; and generate the session initiation invite using the data associated with the session initiation invite in the message. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0064] In some examples, as shown in Fig. 1, a cell may be provided by a network node 110 used in an NTN. The NTN may include an NTN entity 160 (e.g., a satellite, a balloon, a dirigible, an airplane, an unmanned aerial vehicle (UAV), or a high altitude platform station). The network node 110 of the NTN may be a network node carried by the NTN entity 160 (regenerative deployment) or a network node on the ground that communicates via the NTN entity 160 (bent-pipe or transparent deployment), as described in connection with Fig. 4. In a terrestrial network, communication may be performed without the use of an NTN entity.

[0065] In some examples, the network controller 130 may be connected to an external network 170 (e.g., an internet protocol (IP) network), such as via one or more core network components. A PSAP 180 may also be connected to the network 170. Accordingly, communications transmitted by a UE 120 and received by a network node 110 may be provided to the PSAP 180 via the network controller 130 and the network 170. Similarly, communications transmitted by the PSAP 180 and received at the network controller 130, via the network 170, may be provided to the UE 120 by a network node 110.

[0066] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0067] Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T> 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

[0068] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specificreference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, fdter, and / or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

[0069] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0070] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0071] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and / or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmission and / or reception components, such as one or more components of Fig. 2.

[0072] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein.

[0073] At the network node 110, the uplink signals from UE 120 and / or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and the memory 242 to perform aspects of any of the methods described herein.

[0074] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform one or more techniquesassociated with emergency communication via an NTN, as described in more detail herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 1100 of Fig. 11, process 1200 of Fig. 12, process 1300 of Fig. 13, and / or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and / or interpreting) by one or more processors of the network node 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the network node 110 to perform or direct operations of, for example, process 1100 of Fig. 11, process 1200 of Fig. 12, process 1300 of Fig. 13, and / or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instmctions, among other examples.

[0075] In some aspects, the UE 120 includes means for generating a message that includes data associated with a session initiation invite for a PSAP; and / or means for transmitting the message via an NTN. In some aspects, the UE 120 includes means for transmitting a request to establish an RTT communication channel for communication between the UE 120 and a PSAP; and / or means for communicating with the PSAP via the RTT communication channel. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0076] In some aspects, the network node 110 and / or a PSAP includes means for obtaining a message that includes data associated with a session initiation invite for a PSAP; and / or means for generating the session initiation invite using the data associated with the session initiation invite in the message. The means for the network node 110 or the PSAP to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0077] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0078] In some aspects, an individual processor may perform all of the functions described as being performed by the one or more processors. In some aspects, one or more processors may collectively perform a set of functions. For example, a first set of (one or more) processors of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig.2. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig.2. For example, functions described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0079] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

[0080] Deployment of communication systems, such as 5G NR 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 RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0081] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network 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 network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented asvirtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0082] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an 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)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0083] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

[0084] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or 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 one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

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

[0086] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 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 depending, at least in part, on a functional split, such as a functional split defined by the 3 GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

[0087] Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3 GPP), such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real- time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0088] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized networkelements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) 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 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0089] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-realtime 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 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

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

[0091] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0092] Fig. 4 is a diagram illustrating an example 400 of a regenerative satellite deployment and an example 410 of a transparent satellite deployment in an NTN. In some examples, an NTN may support narrowband (NB)-IoT communication.

[0093] Example 400 shows a regenerative satellite deployment. In example 400, a UE 120 is served by a satellite 420 via a service link 430. For example, the satellite 420 may include a network node 110 (e.g., network node 110a) or a gNB. In some aspects, the satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, or an on-board processing repeater. In some aspects, the satellite 420 may demodulate an uplink radio frequency signal, and may modulate a baseband signal derived from the uplink radio signal to produce a downlink radio frequency transmission. The satellite 420 may transmit the downlink radio frequency signal on the service link 430. The satellite 420 may provide a cell that covers the UE 120.

[0094] Example 410 shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In example 410, a UE 120 is served by a satellite 440 via the service link 430. The satellite 440 may be a transparent satellite. The satellite 440 may relay a signal received from gateway 450 via a feeder link 460. For example, the satellite may receive an uplink radio frequency transmission, and may transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some aspects, the satellite may frequency convert the uplink radio frequency transmission received on the service link 430 to a frequency of the uplink radio frequency transmission on the feeder link 460, and may amplify and / or filter the uplink radio frequency transmission. In some aspects, the UEs 120 shown in example 400 and example 410 may be associated with a Global Navigation Satellite System (GNSS) capability or a Global Positioning System (GPS) capability, though not all UEs have such capabilities. The satellite 440 may provide a cell that covers the UE 120.

[0095] The service link 430 may include a link between the satellite 440 and the UE 120, and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 440 and the gateway 450, and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0096] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

[0097] Fig. 5 is a diagram illustrating an example of an emergency calling system 500, in accordance with the present disclosure.

[0098] As shown, the system 500 may include a network node 505 (e.g., corresponding to network node 110), such as an eNB, which may be a distributed system. The system 500 also includes an NTN infrastructure 510 (e.g., associated with an NB-IoT mobile virtual network operator (MVNO)), which may include an NTN service link provisioning system 515 that is included in the network node 505 (e.g., in a distributed or a co-located manner). The NTN service link provisioning system 515 may include an NTN payload 520 (e.g., corresponding to NTN entity 160 or satellite 440) and an NTN gateway 525 (e.g., corresponding to gateway 450)that communicate via a feeder link, as described in connection with Fig. 4. The network node 505 may include a non-NTN infrastructure functions component 530 (e.g., a non-NTN infrastructure eNB functions component) having a communicative connection with the NTN service link provisioning system 515, an NTN control function 535 of the NTN infrastructure 510, an operations and maintenance component 540, and a core network 545 (e.g., an evolved packet core (EPC)) via an SI interface. Communications (e.g., IP communications) of a PSAP 550 (e.g., that is IP capable) may be via the core network 545. The PSAP 550 may include one or more devices 595 (e.g., computing devices) that handle incoming communications to a call center responsible for answering emergency calls and dispatching emergency services. A translation component 555 may be included in the PSAP 550 (e.g., a device 595 of the PSAP 550), the core network 545, and / or another network component described herein. The translation component 555 may provide translation of a message (e.g., an SMS message) to a session initiation invite (e.g., a session initiation protocol (SIP) invite).

[0099] Additionally, or alternatively, the core network 545 may have a communicative connection with a core network (e.g., an EPC) and / or an access and mobility management function (AMF) 560 associated with a TN 565 (e.g., an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (EUTRAN) and / or NR terrestrial network associated with a mobile network operator (MNO)). Accordingly, communications (e.g., IP communications) of the PSAP 550 may be via the core network / AMF 560. Moreover, a translation component 555 may be included in the core network / AMF 560 in this example.

[0100] The system 500 may include a UE 570 (e.g., corresponding to a UE 120) that may be an in-vehicle device. The UE 570 may have a communicative connection with the NTN infrastructure 510 via a service link, as described in connection with Fig. 4, and with the network node 505 via an access link. In addition to the NTN payload 520, the UE 570 may communicate with a global navigation satellite system (GNSS) 575 in connection with positioning and location data. The UE 570 may include an accident sensor 580 (e.g., one or more sensors, such as an accelerometer, a gyroscope, or the like, configured to detect if a vehicle associated with the UE 570 has been in a collision or experienced an impact), a GNSS receiver 581, and an NTN-IoT communication module 582 (e.g., for a geosynchronous equatorial orbit (GEO) NTN deployment, a low earth orbit (LEO) NTN deployment, or the like).

[0101] In addition, the UE 570 may include an in-vehicle services (IVS) component 585. The IVS component 585 may include one or more emergency calling components configured to share vehicle-related information with an emergency call service. The vehicle-related information may include airbag deployment information, accident sensor information, location information, vehicle identification information, passenger information, or the like. As anexample, the emergency calling components may include a second generation (2G) eCall component 586 and / or a next generation (NG) eCall component 587. The IVS component 585 may also include a translation component 588 (e.g., a translation layer) to provide translation of a session initiation invite (e.g., a SIP invite) to a message (e.g., an SMS message). The translation component 588 may interface with the NG eCall component 587 (e.g., an NG eCall stack) to use IP multimedia subsystem (IMS) capabilities (e.g., limited IMS capabilities). The UE 570 may also include a voice and multimedia component 590 (e.g., an IMS) to provide voice and / or multimedia communication capabilities for the UE 570. The UE 570 may be configured to (e.g., in response to an emergency event) generate a session initiation invite that includes an MSD including vehicle-related information (e.g., airbag deployment information, impact sensor information, location information, vehicle identification information, and / or passenger information, among other examples).

[0102] As shown, the network node 505 may establish an RTT communication channel 597 between the UE 570 and the PSAP 550. Communications transmitted by the UE 570 on the RTT communication channel 597 may be via the service link and / or the access link.

[0103] Many vehicles provide support for emergency calling services. For example, the European Union mandates eCall support for all vehicles sold after August 2018. “Emergency calling” may refer to an emergency notification system that automatically and immediately alerts emergency services after a collision of a vehicle. Emergency calling may be implemented in a circuit switching (CS) domain or over IMS. In the CS domain (e.g., for 3G networks), an eCall may include transmitting an MSD (e.g., a minimum set of vehicle-related information, as described herein, that is defined for an eCall) via a voice or data service. For IMS, an eCall may include transmitting the MSD in a SIP invite over an IMS call. To support eCall over IMS, a public land mobile network (PLMN) (e.g., a wireless network that provides wireless coverage for UEs in a particular geographic area via one or more network nodes 110) should support IMS emergency calls, MSD transfer, updated MSD transfer, and routing based on an eCall service uniform resource name (URN).

[0104] The CS and IMS implementations for eCall are defined for TNs. However, there is a possibility that a vehicle collision may occur at a location where cellular connectivity is not available and / or a possibility that an eCall over IMS cannot be established. In such cases, NTN services may be available (e.g., via loT NTN or NR NTN). For example, an loT NTN (e.g., NB loT) network, acting as an MVNO, may be available. However, NTNs do not support eCall services.

[0105] Some techniques and apparatuses described herein enable a UE of a vehicle to perform emergency communication via an NTN. In some aspects, if the vehicle is involved in a collision in an area where there is a lack of voice coverage, the UE may generate a message that includes data associated with a session initiation invite for a PSAP (e.g., the message mayinclude at least an MSD of the session initiation invite). The message may be an SMS message, or another type of message that is supported by the NTN. Rather than transmitting the session initiation invite, the UE may transmit the message that includes the data associated with the session initiation invite via the NTN. In some aspects, a network node associated with the NTN and / or the PSAP may include a component to generate the session initiation invite (e.g., including the MSD) using the data associated with the session initiation invite in the message. In this way, emergency communication that uses the session initiation invite may be performed via the NTN. Using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas).

[0106] In some aspects, the UE may transmit the message via the NTN in one or more narrowband NTN bands, thereby conserving power and improving a performance of the message. In some aspects (e.g., after the PSAP obtains the session initiation invite including the MSD), the UE may transmit, to a network node, a request to establish an RTT communication channel for communication between the UE and the PSAP. Accordingly, the UE may communicate with the PSAP via the RTT communication channel rather than via a voice communication channel, which may not be supported by the NTN. In this way, the UE and the PSAP may exchange information (e.g., vehicle-related information, announcements, or the like) via the NTN. As described above, using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas). Moreover, the RTT communication channel may use a low bandwidth relative to the voice communication channel, thereby conserving network resources.

[0107] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

[0108] Fig. 6 is a diagram illustrating an example 600 associated with emergency communication via an NTN, in accordance with the present disclosure. As shown in Fig. 6, a UE (e.g., UE 120 or UE 570), a network node (e.g., network node 110), and a PSAP (e.g., PSAP 550) may communicate with one another. The UE may be associated with a vehicle, such as an automobile, a boat, an aircraft, a train, or the like. The network node may be associated with an NTN. For example, the network node may be a device of a core network of the NTN. The PSAP may include one or more devices (e.g., the one or more devices 595) that handle incoming communications to a call center responsible for answering emergency calls and dispatching emergency services (e.g., police services, fire services, ambulance services, or the like). The PSAP may have a capability of IP communication (e.g., the PSAP may be IP enabled). The network node and / or the PSAP may include a component (e.g., a translation component 555) for translating a received message, as described below, into a session initiation invite. Prior to the operations shown in Fig. 6, the UE may have detected a collision involvingthe vehicle, and the UE may have generated vehicle-related information (e.g., an MSD) responsive to detecting the collision, as described herein.

[0109] As shown by reference number 605, the UE may detect that a service via a TN is unavailable and / or that a multimedia service (e.g., an IMS service) is unavailable. For example, the UE may detect that the UE has no cellular connectivity and / or that an IMS call attempted by the UE has failed. The UE detecting that the service via the TN is unavailable and / or that the multimedia service is unavailable may indicate to the UE that an emergency communication is to be made via an NTN.

[0110] In response to detecting that the service via the TN is unavailable and / or that the multimedia service is unavailable, the UE may enable one or more NTN bands and acquire service on the NTN. For example, the UE may switch to the NTN (e.g., narrowband over NTN (NB-NTN)) if available. Furthermore, the UE may enter an emergency mode. A system information block (SIB) 1 for NB-NTN may, or may not, include support for eCall (e.g., a lack of a SIB 1 indication for NG eCall may be overridden).[oni] To enable the NTN bands, the UE may activate and / or configure components (e.g., hardware components, such as RF components and associated circuitry, and / or software components) to operate in frequencies associated with the NTN bands to enable the UE to transmit and receive communications in the NTN bands. To acquire service on the NTN, the UE may establish a connection with the NTN (e.g., using an attach procedure, a registration procedure, or the like). The one or more NTN bands may include one or more NB NTN bands.

[0112] As shown by reference number 610, the UE may generate a message that includes data associated with a session initiation invite for the PSAP. The message may be a short message, such as an SMS message, or another type of messaging service message, such as a multimedia messaging service (MMS) message. The message may include a single message (e.g., a single SMS message) or multiple concatenated messages (e.g., concatenated SMS messages) that include the data associated with the session initiation invite. The session initiation invite may be a SIP invite (e.g., used in IMS communication). In some aspects, the session initiation invite may be associated with an eCall or another type of best-effort emergency service for IVS. The data associated with the session initiation invite may include a complete session initiation invite or a portion of a session initiation invite. The data may include vehicle-related information, as described herein, in connection with an event associated with the vehicle (e.g., a collision or another emergency event). For example, the data may include an MSD (e.g., collected by an accident sensor) in connection with the event. As an example, the data may include data relating to a vehicle event, user emergency data, or user non-emergency data.

[0113] As shown, the UE may include an IMS layer 601, a wireless messaging services (WMS) layer 602, and a non-access stratum (NAS) messaging service layer 603. As an example, to generate the message, the UE may generate, at the IMS layer 601 of the UE, the session initiation invite (e.g., that includes the MSD). For example, the UE (e.g., using an NG eCall stack) may generate the MSD (e.g., of 140 octets) within the session initiation invite. The UE may forward the session initiation invite from the IMS layer to the WMS layer 602 of the UE. The UE may generate, at the WMS layer 602, a transfer protocol data unit (TPDU) for the message. The TPDU may include the session initiation invite and may have a destination address set to an address of the PSAP. For example, the UE’s messaging layer may receive the raw session initiation invite and prepare a TPDU (e.g., to be encapsulated in a relay protocol (RP)-User Data information element) with the PSAP destination address and an origination address (e.g., of the UE).

[0114] As shown by reference number 615, the UE may transmit the message (e.g., an emergency message) via the NTN (e.g., via NB NTN or loT NTN). For example, the UE may transmit the message on a service link with an NTN payload (e.g., NTN payload 520). Thus, emergency operation is enabled for the UE while the UE is communicating in NB-IoT over NTN. In some aspects, the UE may transmit the message via the NTN responsive to detecting that the service via the TN is unavailable and / or detecting that the multimedia service is unavailable.

[0115] As an example, to transmit the message via the NTN, the UE may forward the TPDU for the message to the NAS messaging service layer 603 (e.g., a NAS SMS layer) of the UE. The UE may transmit, from the NAS messaging service layer 603, the message via the NTN (e.g., via NB-IoT over NTN). For example, the UE may send the data from the messaging layer to the NAS SMS layer for transmission as an SMS using NB-IoT over NTN. The UE may transmit a single message that includes the session initiation invite or multiple concatenated messages that include the session initiation invite (e.g., if the data for the session initiation invite is larger than a maximum size allowable for a single message).

[0116] The network node and / or the PSAP may obtain (e.g., receive) the message that includes the data for the session initiation invite for the PSAP that was transmitted by the UE (e.g., the network node and / or the PSAP may obtain the multiple concatenated messages that include the data for the session initiation invite). As shown by reference number 620, the network node and / or the PSAP (e.g., using the translation component) may generate the session initiation invite (e.g., that includes the MSD) using the data associated with the session initiation invite in the message (e.g., convert the message into the session initiation invite, translate the message into the session initiation invite, extract the session initiation invite from the message, or the like).

[0117] In some aspects (e.g., when the network node generated the session initiation invite from the message), as shown by reference number 625, the network node may output (e.g., transmit to the PSAP) the session initiation invite. Additionally, as shown by reference number 630, the network node may output, and the PSAP may receive, an indication that the session initiation invite is associated with limited functionality. For example, the indication may indicate that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call (e.g., the PSAP may be made aware that no voice bearers, media bearers, and / or voice call should be expected by the PSAP in connection with the session initiation invite). The PSAP may process (e.g., interpret) the data in the session initiation invite, and the PSAP may arrange for emergency services to be dispatched to the vehicle.

[0118] As shown by reference number 635, the network node and / or the PSAP may output, and the UE may receive, an acknowledgment message that includes a response to the session initiation invite. For example, the PSAP may transmit the acknowledgment message to the network node, and the network node may transmit the acknowledgment message to the UE. The acknowledgment message may provide an indication of acknowledgment of the session initiation invite and / or may include information for an occupant of the vehicle (e.g., a prerecorded message). The acknowledgment message may be a short message, such as an SMS message, or another type of messaging service message, such as an MMS message. In some aspects, the UE and the PSAP may transmit messages (e.g., SMS messages) in sequence until both the UE and the PSAP have transmitted all data.

[0119] As shown by reference number 640, the network node and / or the PSAP may output, and the UE may receive, an additional message that indicates a request for retransmission of the data associated with the session initiation invite (e.g., the MSD). For example, the PSAP may initiate a request for retransmission of the MSD. As an example, the PSAP may transmit the additional message to the network node, and the network node may transmit the additional message to the UE. The additional message may be a short message, such as an SMS message, or another type of messaging service message, such as an MMS message. Retransmission of the data may be performed in a similar manner as described above. In some aspects, a request for retransmission of the data associated with the session initiation invite (e.g., the MSD) may be made via an RTT stream (e.g., for an eMTC, an NR NTN, or an NR TN type NTN-IoT). For example, the PSAP may transmit, and the UE may receive, via an RTT communication channel between the UE and the PSAP, the request for retransmission of the data associated with the session initiation invite (e.g., the MSD). Accordingly, the UE may retransmit the data associated with the session initiation invite via the RTT communication channel.

[0120] In this way, the UE may perform emergency communication with the PSAP via the NTN. Using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas).

[0121] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

[0122] Fig. 7 is a flowchart illustrating an example 700 associated with emergency communication via an NTN, in accordance with the present disclosure. Example 700 may include the UE, the network node, and the PSAP described in connection with Fig. 6.

[0123] As shown by block 705, the UE may detect (e.g., using IVS) a collision involving the vehicle associated with the UE. As shown by block 710, the UE may generate an MSD (block 710). For example, generating the MSD may be responsive to detecting the collision. The MSD may include vehicle-related information, as described herein. As shown by block 715, the UE may detect whether service is available on a TN. For example, the TN may be a CS network, an LTE network, an NR network, or the like. Responsive to detecting that service is available on the TN (block 715-YES), as shown by block 720, the UE may detect whether call establishment for an IMS call or a CS call failed. Responsive to detecting that the call establishment succeeded (block 720-NO), as shown by block 725, the UE may transmit the MSD in connection with the IMS call or the CS call (e.g., according to a legacy procedure). In some aspects, the UE may employ modified PLMN selection procedures when the UE has a capability to perform emergency communications via an NTN.

[0124] Responsive to detecting that service is unavailable on the terrestrial network (block 715-NO) and / or detecting that the call establishment failed (block 720-YES), as shown by block 730, the UE may enable one or more NTN bands (e.g., NB-IoT NTN bands) and acquire service on an NTN (block 730). The NTN may support short messaging, such as SMS messaging. As shown by block 735, the UE may convert a session initiation invite (e.g., a SIP invite) to include the MSD in a TPDU. The MSD may be encoded in an ASN.1 PER format (e.g., to be encapsulated in an RP-User Data information element). As shown by block 740, the UE may set a destination address associated with the TPDU (e.g., in the RP-User Data information element) to an address of a PSAP. The address may be an address associated with the PSAP’s service center, such as a common telephone number. As shown by block 745, the UE may transmit a control plane data (CP -DAT A) message containing a relay protocol data unit (RPDU) (e.g., an RP-DATA RPDU) in an uplink NAS transport message. A destination address of the RPDU may be set to an SMS center (SMSC) address.

[0125] As shown by block 750, an NTN messaging service gateway (e.g., an NTN SMSC and / or SMS gateway) may forward the user data message (e.g., of the RP-DATA RPDU) to the PSAP. As shown by block 755, the PSAP may process the user data message and transmit a control plane data (CP-DATA) message containing an RPDU (e.g., an RP-DATA RPDU, for SMS delivery of a TPDU) with an IVS message for an occupant of the vehicle. For example,the IVS message may be a pre-recorded announcement (e.g., “Emergency services have been notified of your emergency, and help is on the way.”).

[0126] As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.

[0127] Fig. 8 is a flowchart illustrating an example 800 associated with emergency communication via an NTN, in accordance with the present disclosure. Example 800 may include the UE, the network node, and the PSAP described in connection with Fig. 6.

[0128] As shown by block 805, the UE may detect a collision involving the vehicle associated with the UE, as described herein. As shown by block 810, responsive to detecting the collision, the UE may generate an MSD (e.g., in an ASN.l PER format) and forward the MSD to an IMS layer of the UE to construct (e.g., encode) a session initiation invite (e.g., a SIP invite). As shown by block 815, the UE may determine that an IMS service is unavailable and / or that a terrestrial network RAT is unavailable. As shown by block 820, responsive to determining that the IMS service is unavailable and / or that the terrestrial network RAT is unavailable, the UE may forward the session initiation invite to a WMS layer of the UE.

[0129] As shown by block 825, the UE may determine whether the encoded session initiation invite with the MSD has a size that is greater than a single message length limit (e.g., an SMS message length limit, such as 160 characters). Responsive to determining that the size is not greater than the single message length limit (block 825-NO), as shown by block 830, the UE may provide a single message (e.g., a single SMS) to an NTN NAS layer of the UE (e.g., an NB-NTN NAS layer of the UE) for transmission. Responsive to determining that the size is greater than the single message length limit (block 825-YES), as shown by block 835, the UE may provide concatenated messages (e.g., concatenated SMSs) to the NTN NAS layer of the UE for transmission.

[0130] As shown by block 840, the message(s) may be received at a messaging center or a messaging gateway (e.g., an SMSC or SMS gateway) of a core network (e.g., an NTN core network). As shown by block 845, the core network may convert and reformat the message (e.g., the SMS) into a session initiation invite (e.g., a SIP invite) that includes the MSD. As shown by block 850, the core network may forward the session initiation invite with the MSD to the PSAP. Alternatively, as shown by block 855, the core network may forward the message encoding the session initiation invite with the MSD to a destination address associated with the PSAP. As shown by block 860, the PSAP may convert and reformat the message (e.g., the SMS) into a session initiation invite (e.g., a SIP invite) that includes the MSD.

[0131] As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.

[0132] Fig. 9 is a flowchart illustrating an example 900 associated with emergency communication via an NTN, in accordance with the present disclosure. Example 900 may include the UE, the network node, and the PSAP described in connection with Fig. 6.

[0133] Responsive to receiving a session initiation invite, the PSAP may generate a response (e.g., in a SIP message) with an announcement (e.g., a pre-recorded announcement for an occupant of the vehicle), and as shown by block 905, the PSAP and / or the network node may convert the response into a message (e.g., a mobile terminated (MT) SMS). As shown by block 910, the message may be received at a messaging center or a messaging gateway (e.g., an SMSC or SMS gateway) of the core network (e.g., an NTN core network). As shown by block 915, the core network may forward the message to the UE.

[0134] As shown by block 920, the UE may receive the message (e.g., the SMS message). For example, the UE may receive the message using an NTN RAT. As shown by block 925, the UE may forward the message to a WMS component of the UE and may alert an IMS layer of the UE (e.g., to ensure that the IMS layer is in synchronization with the operations being performed at the WMS component). The WMS component may obtain the announcement of the message (e.g., the WMS component may extract the announcement from the message). As shown by block 930, the UE may forward the announcement to an advanced driver assistance system (ADAS) of the UE. As shown by block 935, the announcement may be output (e.g., displayed) by the ADAS (e.g., in a ADAS user interface).

[0135] As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with respect to Fig. 9.

[0136] Fig. 10 is a diagram illustrating an example 1000 associated with emergency communication via an NTN, in accordance with the present disclosure. As shown in Fig. 10, a UE (e.g., UE 120 or UE 570), a network node (e.g., network node 110), and a PSAP (e.g., PSAP 550) may communicate with one another. The UE may be associated with a vehicle, such as an automobile, a boat, an aircraft, a train, or the like. The network node may be associated with an NTN. For example, the network node may be a device of a core network of the NTN. The PSAP may include one or more devices that handle incoming communications to a call center responsible for answering emergency calls and dispatching emergency services (e.g., police services, fire services, ambulance services, or the like). The PSAP may have a capability of IP communication (e.g., the PSAP may be IP enabled). Prior to the operations shown in Fig. 10, the UE may have detected a collision involving the vehicle, and the UE may have generated vehicle-related information (e.g., an MSD) responsive to detecting the collision, as described herein.

[0137] As shown by reference number 1005, the UE may transmit, and the PSAP may receive, a session initiation invite (e.g., a SIP invite) for the PSAP (e.g., to establish acommunication session between the UE and the PSAP). The session initiation invite may include the vehicle-related information (e.g., an eCall MSD). The UE may transmit the session initiation invite via an IMS service. For example, the UE may transfer the MSD to the PSAP via SIP signaling. Alternatively, the UE may transmit, via an NTN, a message (e.g., an SMS message) that includes data associated with the session initiation invite for the PSAP, as described in connection with Figs. 6-8. As shown by reference number 1010, the PSAP may transmit, and the UE may receive, a response message acknowledging the session initiation invite (e.g., indicating that the UE’s request was successful). In some aspects, the response message may include metadata associated with the emergency call (e.g., eCall metadata). As shown by reference number 1015, one or more media streams between the UE and the PSAP may be established (e.g., started) for the communication session (e.g., emergency call) between the UE and the PSAP. In some aspects, the PSAP may request information from the UE (e.g., request MSD in eCall metadata), the UE may acknowledge the request and transmit the requested information (e.g., eCall MSD), and the PSAP may acknowledge receiving the information (e.g., via the one or more media streams).

[0138] As shown by reference number 1020, the UE may transmit, and the network node may receive, a request to establish an RTT communication channel (e.g., an RTT stream) for communication (e.g., information exchange) between the UE and the PSAP. The RTT communication channel may correspond to RTT communication channel 597, described herein. As shown by reference number 1025, the network node may cause the RTT communication channel to be established. As shown by reference number 1030, the network node may transmit, and the UE may receive, an indication that the RTT communication channel has been established.

[0139] As shown by reference number 1035, the UE may communicate with the PSAP via the RTT communication channel (e.g., the UE and the PSAP may exchange information via the RTT communication channel). Thus, a voice path that would otherwise be used for an NG eCall using IMS and SIP (that is not supported by NB-IoT) may be replaced with an RTT path (that is allowed by IMS and SIP) that uses low bandwidth. The UE may communicate with the PSAP via the RTT communication channel responsive to receiving the indication that the RTT communication channel has been established.

[0140] In some aspects, to communicate with the PSAP via the RTT communication channel, the UE may receive a request for user data (e.g., relating to a vehicle event) via the RTT communication channel. For example, the PSAP may transmit, via the RTT communication channel, a request message (e.g., a SIP INFO message) requesting additional information from the UE (e.g., information, such as MSD, in addition to the information provided in the session initiation invite). In some aspects, to communicate with the PSAP via the RTT communication channel, the UE may transmit user data via the RTT communication channel. For example, inresponse to the request message, the UE may transmit, via the RTT communication channel, the additional information (e.g., updated MSD information). The additional information may assist in identifying the type of help that is needed for the vehicle.

[0141] In some aspects, to communicate with the PSAP via the RTT communication channel, the UE may receive one or more messages for an occupant of the vehicle. For example, the RTT communication channel may be used for PSAP-to-vehicle-occupant communication (e.g., including announcements, assistance information, estimated time of arrival information, or the like). In some aspects, the PSAP may transmit, via the RTT communication channel, messages with standardized announcements, or the like. In some aspects, the UE may transmit, via the RTT communication channel, information associated with the vehicle that is not part of the MSD.

[0142] As shown by reference number 1040, the PSAP may transmit (e.g., using SIP) a message requesting to terminate the communication session between the UE and the PSAP. As shown by reference number 1045, the media stream(s) for the communication session may be terminated (e.g., responsive to the message requesting to terminate the communication session). As shown by reference number 1050, the UE may transmit, and the PSAP may receive, a response message acknowledging the request to terminate the communication session (e.g., indicating that the PSAP’s request was successful).

[0143] In this way, the UE may communicate with the PSAP via the RTT communication channel rather than via a voice communication channel, which may not be supported by an NTN. Accordingly, the UE and the PSAP may exchange information (e.g., vehicle-related information, announcements, or the like) via the NTN. As described above, using the NTN to perform emergency communication improves a coverage for emergency communication (e.g., in remote areas). Moreover, the RTT communication channel may use a low bandwidth relative to the voice communication channel, thereby conserving network resources.

[0144] As indicated above, Fig. 10 is provided as an example. Other examples may differ from what is described with respect to Fig. 10.

[0145] Fig. 11 is a diagram illustrating an example process 1100 performed, for example, by a UE, in accordance with the present disclosure. Example process 1100 is an example where the UE (e.g., UE 120) performs operations associated with emergency communication via an NTN.

[0146] As shown in Fig. 11, in some aspects, process 1100 may include generating a message that includes data associated with a session initiation invite for a PSAP (block 1110). For example, the UE (e.g., using communication manager 140 and / or translation component 1408, depicted in Fig. 14) may generate a message that includes data associated with a session initiation invite for a PSAP, as described above.

[0147] As further shown in Fig. 11, in some aspects, process 1100 may include transmitting the message via an NTN (block 1120). For example, the UE (e.g., using communication manager 140 and / or transmission component 1404, depicted in Fig. 14) may transmit the message via an NTN, as described above.

[0148] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0149] In a first aspect, the session initiation invite is a SIP invite.

[0150] In a second aspect, alone or in combination with the first aspect, the message is an SMS message or an MMS message.

[0151] In a third aspect, alone or in combination with one or more of the first and second aspects, as shown by block 1130, process 1100 includes detecting that a service via a TN is unavailable, enabling one or more NTN bands, and acquiring service on the NTN, where transmitting the message via the NTN is responsive to detecting that the service via the TN is unavailable. For example, the UE (e.g., using communication manager 140 and / or NTN component 1410, depicted in Fig. 14) may detect that a service via a TN is unavailable, enable one or more NTN bands, and acquire service on the NTN, as described above.

[0152] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more NTN bands include one or more narrowband NTN bands.

[0153] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, as shown by block 1140, process 1100 includes detecting that an IMS service is unavailable, enabling one or more NTN bands, and acquiring service on the NTN, where transmitting the message via the NTN is responsive to detecting that the IMS service is unavailable. For example, the UE (e.g., using communication manager 140 and / or NTN component 1410, depicted in Fig. 14) may detect that an IMS service is unavailable, enable one or more NTN bands, and acquire service on the NTN, as described above.

[0154] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the one or more NTN bands include one or more narrowband NTN bands.

[0155] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, transmitting the message includes transmitting multiple concatenated messages that include the data associated with the session initiation invite.

[0156] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, generating the message includes generating, at an IMS layer of the UE, the session initiation invite, forwarding the session initiation invite from the IMS layer to a wireless messaging services layer of the UE, and generating, at the wireless messaging services layer, aTPDU for the message, the TPDU including the data associated with the session initiation invite and having a destination address set to an address of the PSAP.

[0157] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, transmitting the message includes forwarding the TPDU for the message to a NAS messaging service layer of the UE, and transmitting, from the NAS messaging service layer, the message via the NTN.

[0158] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, as shown by block 1150, process 1100 includes receiving an acknowledgment message that includes a response to the session initiation invite. For example, the UE (e.g., using communication manager 140 and / or reception component 1402, depicted in Fig. 14) may receive an acknowledgment message that includes a response to the session initiation invite, as described above.

[0159] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the message is a first message, and as shown by block 1160, process 1100 further includes receiving a second message that indicates a request for retransmission of the data associated with the session initiation invite. For example, the UE (e.g., using communication manager 140 and / or reception component 1402, depicted in Fig. 14) may receive a message that indicates a request for retransmission of the data associated with the session initiation invite, as described above.

[0160] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, as shown by block 1170, process 1100 includes receiving, via an RTT communication channel between the UE and the PSAP, a request for retransmission of the data associated with the session initiation invite. For example, the UE (e.g., using communication manager 140 and / or reception component 1402, depicted in Fig. 14) may receive, via an RTT communication channel between the UE and the PSAP, a request for retransmission of the data associated with the session initiation invite, as described above.

[0161] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the data associated with the session initiation invite includes one or more of data relating to a vehicle event, user emergency data, or user non-emergency data.

[0162] Although Fig. 11 shows example blocks of process 1100, in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0163] Fig. 12 is a diagram illustrating an example process 1200 performed, for example, by a device, in accordance with the present disclosure. Example process 1200 is an example wherethe device (e.g., network node 110 or PSAP 550) performs operations associated with emergency communication via an NTN.

[0164] As shown in Fig. 12, in some aspects, process 1200 may include obtaining a message that includes data associated with a session initiation invite for a PSAP (block 1210). For example, the device (e.g., using communication manager 150 and / or reception component 1702, depicted in Fig. 17) may obtain a message that includes data associated with a session initiation invite for a PSAP, as described above.

[0165] As further shown in Fig. 12, in some aspects, process 1200 may include generating the session initiation invite using the data associated with the session initiation invite in the message (block 1220). For example, the device (e.g., using communication manager 150 and / or translation component 1708, depicted in Fig. 17) may generate the session initiation invite using the data associated with the session initiation invite in the message, as described above.

[0166] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0167] In a first aspect, as shown by block 1230, process 1200 includes outputting the session initiation invite. For example, the device (e.g., using communication manager 150 and / or transmission component 1704, depicted in Fig. 17) may output the session initiation invite, as described above.

[0168] In a second aspect, alone or in combination with the first aspect, the session initiation invite is a SIP invite.

[0169] In a third aspect, alone or in combination with one or more of the first and second aspects, the message is an SMS message or an MMS message.

[0170] In a fourth aspect, alone or in combination with one or more of the first through third aspects, obtaining the message includes obtaining multiple concatenated messages that include the data associated with the session initiation invite.

[0171] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, as shown by block 1240, process 1200 includes outputting an acknowledgment message that includes a response to the session initiation invite. For example, the device (e.g., using communication manager 150 and / or transmission component 1704, depicted in Fig. 17) may output an acknowledgment message that includes a response to the session initiation invite, as described above.

[0172] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the message is a first message, and as shown by block 1250, process 1200 includes outputting a second message that indicates a request for retransmission of the data associated with the session initiation invite. For example, the device (e.g., using communication manager150 and / or transmission component 1704, depicted in Fig. 17) may output a message that indicates a request for retransmission of the data associated with the session initiation invite, as described above.

[0173] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, as shown by block 1260, process 1200 includes outputting an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call. For example, the device (e.g., using communication manager 150 and / or transmission component 1704, depicted in Fig. 17) may output an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call, as described above.

[0174] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, as shown by block 1260, process 1200 includes receiving an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call. For example, the device (e.g., using communication manager 150 and / or reception component 1702, depicted in Fig. 17) may receive an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call, as described above.

[0175] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, as shown by block 1270, process 1200 includes transmitting, via an RTT communication channel between a UE and the PSAP, a request for retransmission of the data associated with the session initiation invite. For example, the device (e.g., using communication manager 150 and / or transmission component 1704, depicted in Fig. 17) may transmit, via an RTT communication channel between a UE and the PSAP, a request for retransmission of the data associated with the session initiation invite, as described above.

[0176] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the data associated with the session initiation invite includes one or more of data relating to a vehicle event, user emergency data, or user non-emergency data.

[0177] Although Fig. 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0178] Fig. 13 is a diagram illustrating an example process 1300 performed, for example, by a UE, in accordance with the present disclosure. Example process 1300 is an example where the UE (e.g., UE 120) performs operations associated with emergency communication via an NTN.

[0179] As shown in Fig. 13, in some aspects, process 1300 may include transmitting a request to establish an RTT communication channel for communication between the UE and a PSAP (block 1310). For example, the UE (e.g., using communication manager 140 and / or transmission component 1404, depicted in Fig. 14) may transmit a request to establish an RTT communication channel for communication between the UE and a PSAP, as described above.

[0180] As further shown in Fig. 13, in some aspects, process 1300 may include communicating with the PSAP via the RTT communication channel (block 1320). For example, the UE (e.g., using communication manager 140, reception component 1402, and / or transmission component 1404, depicted in Fig. 14) may communicate with the PSAP via the RTT communication channel, as described above.

[0181] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0182] In a first aspect, as shown by block 1330, process 1300 includes transmitting a session initiation invite for the PSAP via an IMS service. For example, the UE (e.g., using communication manager 140 and / or transmission component 1404, depicted in Fig. 14) may transmit a session initiation invite for the PSAP via an IMS service, as described above.

[0183] In a second aspect, alone or in combination with the first aspect, as shown by block 1340, process 1300 includes transmitting, via an NTN, a message that includes data associated with a session initiation invite for the PSAP. For example, the UE (e.g., using communication manager 140 and / or transmission component 1404, depicted in Fig. 14) may transmit, via an NTN, a message that includes data associated with a session initiation invite for the PSAP, as described above.

[0184] In a third aspect, alone or in combination with one or more of the first and second aspects, as shown by block 1350, process 1300 includes receiving an indication that the RTT communication channel has been established, where communicating with the PSAP via the RTT communication channel is responsive to receiving the indication. For example, the UE (e.g., using communication manager 140 and / or reception component 1402, depicted in Fig. 14) may receive an indication that the RTT communication channel has been established, as described above.

[0185] In a fourth aspect, alone or in combination with one or more of the first through third aspects, communicating with the PSAP via the RTT communication channel includes receiving a request for user data via the RTT communication channel.

[0186] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, communicating with the PSAP via the RTT communication channel includes transmitting user data via the RTT communication channel.

[0187] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, communicating with the PS AP via the RTT communication channel includes receiving one or more messages for a vehicle occupant via the RTT communication channel.

[0188] Although Fig. 13 shows example blocks of process 1300, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

[0189] Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure. The apparatus 1400 may be a UE, or a UE may include the apparatus 1400. In some aspects, the apparatus 1400 includes a reception component 1402 and a transmission component 1404, which may be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using the reception component 1402 and the transmission component 1404. As further shown, the apparatus 1400 may include the communication manager 140. The communication manager 140 may include one or more of a translation component 1408 or an NTN component 1410, among other examples.

[0190] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 6-10. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process HOO ofFig. 11, process 1300 of Fig. 13, or a combination thereof. In some aspects, the apparatus 1400 and / or one or more components shown in Fig. 14 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0191] The reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1406. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may providethe processed signals to the one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.

[0192] The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1406. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1406. In some aspects, the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1406. In some aspects, the transmission component 1404 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in a transceiver.

[0193] The translation component 1408 may generate a message that includes data associated with a session initiation invite for a PSAP. The transmission component 1404 may transmit the message via an NTN.

[0194] The NTN component 1410 may detect that a service via a TN is unavailable. The NTN component 1410 may enable one or more NTN bands. The NTN component 1410 may acquire service on the NTN.

[0195] The NTN component 1410 may detect that an IMS service is unavailable. The NTN component 1410 may enable one or more NTN bands. The NTN component 1410 may acquire service on the NTN.

[0196] The reception component 1402 may receive an acknowledgment message that includes a response to the session initiation invite. The reception component 1402 may receive, via an RTT communication channel, a request for retransmission of the data associated with the session initiation invite.

[0197] The transmission component 1404 may transmit a request to establish an RTT communication channel for communication between the UE and a PSAP. The reception component 1402 and / or the transmission component 1404 may communicate with the PSAP via the RTT communication channel.

[0198] The transmission component 1404 may transmit a session initiation invite for the PSAP via an IMS service. The transmission component 1404 may transmit, via an NTN, amessage that includes data associated with a session initiation invite for the PSAP. The reception component 1402 may receive an indication that the RTT communication channel has been established.

[0199] The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.

[0200] Fig. 15 is a diagram illustrating an example 1500 of a hardware implementation for an apparatus 1505 employing a processing system 1510, in accordance with the present disclosure. The apparatus 1505 may be a UE.

[0201] The processing system 1510 may be implemented with a bus architecture, represented generally by the bus 1515. The bus 1515 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1510 and the overall design constraints. The bus 1515 links together various circuits including one or more processors and / or hardware components, represented by the processor (or processing circuitry) 1520, the illustrated components, and the computer-readable medium / memory (or memory circuitry) 1525. The processor 1520 may include multiple processors, such as processor 1520a, processor 1520b, and processor 1520c. The memory 1525 may include multiple memories, such as memory 1525a, memory 1525b, and memory 1525c. The bus 1515 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0202] The processing system 1510 may be coupled to a transceiver 1530. The transceiver 1530 is coupled to one or more antennas 1535. The transceiver 1530 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 1530 receives a signal from the one or more antennas 1535, extracts information from the received signal, and provides the extracted information to the processing system 1510, specifically the reception component 1402. In addition, the transceiver 1530 receives information from the processing system 1510, specifically the transmission component 1404, and generates a signal to be applied to the one or more antennas 1535 based at least in part on the received information.

[0203] The processing system 1510 includes a processor 1520 coupled to a computer- readable medium / memory 1525. The processor 1520 is responsible for general processing,including the execution of software stored on the computer-readable medium / memory 1525. The software, when executed by the processor 1520, causes the processing system 1510 to perform the various functions described herein for any particular apparatus. The computer- readable medium / memory 1525 may also be used for storing data that is manipulated by the processor 1520 when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor 1520, resident / stored in the computer readable medium / memory 1525, one or more hardware modules coupled to the processor 1520, or some combination thereof.

[0204] In some aspects, the processing system 1510 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the receive processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1505 for wireless communication includes means for generating a message that includes data associated with a session initiation invite for a PSAP, and / or means for transmitting the message via an NTN. In some aspects, the apparatus 1505 for wireless communication includes means for transmitting a request to establish an RTT communication channel for communication with a PSAP, and / or means for communicating with the PSAP via the RTT communication channel. The aforementioned means may be one or more of the aforementioned components of the apparatus 1400 and / or the processing system 1510 of the apparatus 1505 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1510 may include the TX MIMO processor 266, the receive processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the receive processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0205] Fig. 15 is provided as an example. Other examples may differ from what is described in connection with Fig. 15.

[0206] Fig. 16 is a diagram illustrating an example 1600 of an implementation of code and circuitry for an apparatus 1605, in accordance with the present disclosure. The circuitry may include processing circuitry and memory circuitry. The apparatus 1605 may be a UE, or a UE may include the apparatus 1605.

[0207] As shown in Fig. 16, the apparatus 1605 may include circuitry for generating a message that includes data associated with a session initiation invite for a PSAP (circuitry 1620). For example, the circuitry 1620 may enable the apparatus 1605 to generate a message that includes data associated with a session initiation invite for a PSAP.

[0208] As shown in Fig. 16, the apparatus 1605 may include, stored in computer-readable medium 1525, code for generating a message that includes data associated with a session initiation invite for a PSAP (code 1625). For example, the code 1625, when executed byprocessor 1520, may cause processor 1520 to generate a message that includes data associated with a session initiation invite for a PSAP.

[0209] As shown in Fig. 16, the apparatus 1605 may include circuitry for transmitting the message via an NTN (circuitry 1630). For example, the circuitry 1630 may enable the apparatus 1605 to transmit the message via an NTN.

[0210] As shown in Fig. 16, the apparatus 1605 may include, stored in computer-readable medium 1525, code for transmitting the message via an NTN (code 1635). For example, the code 1635, when executed by processor 1520, may cause processor 1520 to cause transceiver 1530 to transmit the message via an NTN.

[0211] As shown in Fig. 16, the apparatus 1605 may include circuitry for transmitting a request to establish an RTT communication channel for communication with a PSAP (circuitry 1640). For example, the circuitry 1640 may enable the apparatus 1605 to transmit a request to establish an RTT communication channel for communication with a PSAP.

[0212] As shown in Fig. 16, the apparatus 1605 may include, stored in computer-readable medium 1525, code for transmitting a request to establish an RTT communication channel for communication with a PSAP (code 1645). For example, the code 1645, when executed by processor 1520, may cause processor 1520 to cause transceiver 1530 to transmit a request to establish an RTT communication channel for communication with a PSAP.

[0213] As shown in Fig. 16, the apparatus 1605 may include circuitry for communicating with the PSAP via the RTT communication channel (circuitry 1650). For example, the circuitry 1650 may enable the apparatus 1605 to communicate with the PSAP via the RTT communication channel.

[0214] As shown in Fig. 16, the apparatus 1605 may include, stored in computer-readable medium 1525, code for communicating with the PSAP via the RTT communication channel (code 1655). For example, the code 1655, when executed by processor 1520, may cause processor 1520 to cause transceiver 1530 to communicate with the PSAP via the RTT communication channel.

[0215] Fig. 16 is provided as an example. Other examples may differ from what is described in connection with Fig. 16.

[0216] Fig. 17 is a diagram of an example apparatus 1700 for wireless communication, in accordance with the present disclosure. The apparatus 1700 may be a network node or a PSAP, or a network node or a PSAP may include the apparatus 1700. In some aspects, the apparatus 1700 includes a reception component 1702 and a transmission component 1704, which may be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 1700 may communicate with another apparatus 1706 (such as a UE, a base station, or another wireless communication device) using thereception component 1702 and the transmission component 1704. As further shown, the apparatus 1700 may include the communication manager 150. The communication manager 150 may include a translation component 1708, among other examples.

[0217] In some aspects, the apparatus 1700 may be configured to perform one or more operations described herein in connection with Figs. 6-10. Additionally, or alternatively, the apparatus 1700 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12, or a combination thereof. In some aspects, the apparatus 1700 and / or one or more components shown in Fig. 17 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 17 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instmctions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0218] The reception component 1702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1706. The reception component 1702 may provide received communications to one or more other components of the apparatus 1700. In some aspects, the reception component 1702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1700. In some aspects, the reception component 1702 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2.

[0219] The transmission component 1704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1706. In some aspects, one or more other components of the apparatus 1700 may generate communications and may provide the generated communications to the transmission component 1704 for transmission to the apparatus 1706. In some aspects, the transmission component 1704 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1706. In some aspects, the transmission component 1704 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2. Insome aspects, the transmission component 1704 may be co-located with the reception component 1702 in a transceiver.

[0220] The reception component 1702 may obtain a message that includes data associated with a session initiation invite for a PSAP. The translation component 1708 may generate the session initiation invite using the data associated with the session initiation invite in the message.

[0221] The transmission component 1704 may output the session initiation invite. The transmission component 1704 may output an acknowledgment message that includes a response to the session initiation invite. The transmission component 1704 may output an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call.

[0222] The reception component 1702 may receive an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call. The transmission component 1704 may transmit, via an RTT communication channel, a request for retransmission of the data associated with the session initiation invite.

[0223] The number and arrangement of components shown in Fig. 17 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 17. Furthermore, two or more components shown in Fig. 17 may be implemented within a single component, or a single component shown in Fig. 17 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 17 may perform one or more functions described as being performed by another set of components shown in Fig. 17.

[0224] Fig. 18 is a diagram illustrating an example 1800 of a hardware implementation for an apparatus 1805 employing a processing system 1810, in accordance with the present disclosure. The apparatus 1805 may be a network node or a PSAP.

[0225] The processing system 1810 may be implemented with a bus architecture, represented generally by the bus 1815. The bus 1815 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1810 and the overall design constraints. The bus 1815 links together various circuits including one or more processors and / or hardware components, represented by the processor (or processing circuitry) 1820, the illustrated components, and the computer-readable medium / memory (or memory circuitry) 1825. The processor 1820 may include multiple processors, such as processor 1820a, processor 1820b, and processor 1820c. The memory 1825 may include multiple memories, such as memory 1825a, memory 1825b, and memory 1825c. The bus 1815 may also linkvarious other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0226] The processing system 1810 may be coupled to a transceiver 1830. The transceiver 1830 is coupled to one or more antennas 1835. The transceiver 1830 provides a means for communicating with various other apparatuses over a transmission medium. The transceiver 1830 receives a signal from the one or more antennas 1835, extracts information from the received signal, and provides the extracted information to the processing system 1810, specifically the reception component 1702. In addition, the transceiver 1830 receives information from the processing system 1810, specifically the transmission component 1704, and generates a signal to be applied to the one or more antennas 1835 based at least in part on the received information.

[0227] The processing system 1810 includes a processor 1820 coupled to a computer- readable medium / memory 1825. The processor 1820 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1825. The software, when executed by the processor 1820, causes the processing system 1810 to perform the various functions described herein for any particular apparatus. The computer- readable medium / memory 1825 may also be used for storing data that is manipulated by the processor 1820 when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor 1820, resident / stored in the computer readable medium / memory 1825, one or more hardware modules coupled to the processor 1820, or some combination thereof.

[0228] In some aspects, the processing system 1810 may be a component of the network node 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In some aspects, the processing system 1810 may be a component of a PSAP. In some aspects, the apparatus 1805 for wireless communication includes means for obtaining a message that includes data associated with a session initiation invite for a PSAP, and / or means for generating the session initiation invite using the data associated with the session initiation invite in the message. The aforementioned means may be one or more of the aforementioned components of the apparatus 1700 and / or the processing system 1810 of the apparatus 1805 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1810 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0229] Fig. 18 is provided as an example. Other examples may differ from what is described in connection with Fig. 18.

[0230] Fig. 19 is a diagram illustrating an example 1900 of an implementation of code and circuitry for an apparatus 1905, in accordance with the present disclosure. The circuitry may include processing circuitry and memory circuitry. The apparatus 1905 may be a network node or a PSAP, or a network node or a PSAP may include the apparatus 1905.

[0231] As shown in Fig. 19, the apparatus 1905 may include circuitry for obtaining a message that includes data associated with a session initiation invite for a PSAP (circuitry 1920). For example, the circuitry 1920 may enable the apparatus 1905 to obtain a message that includes data associated with a session initiation invite for a PSAP.

[0232] As shown in Fig. 19, the apparatus 1905 may include, stored in computer-readable medium 1825, code for obtaining a message that includes data associated with a session initiation invite for a PSAP (code 1925). For example, the code 1925, when executed by processor 1820, may cause processor 1820 to cause transceiver 1830 to obtain a message that includes data associated with a session initiation invite for a PSAP.

[0233] As shown in Fig. 19, the apparatus 1905 may include circuitry for generating the session initiation invite using the data associated with the session initiation invite in the message (circuitry 1930). For example, the circuitry 1930 may enable the apparatus 1905 to generate the session initiation invite using the data associated with the session initiation invite in the message.

[0234] As shown in Fig. 19, the apparatus 1905 may include, stored in computer-readable medium 1825, code for generating the session initiation invite using the data associated with the session initiation invite in the message (code 1935). For example, the code 1935, when executed by processor 1820, may cause processor 1820 to generate the session initiation invite using the data associated with the session initiation invite in the message.

[0235] Fig. 19 is provided as an example. Other examples may differ from what is described in connection with Fig. 19.

[0236] The following provides an overview of some Aspects of the present disclosure:

[0237] Aspect 1 : A method of wireless communication performed at an apparatus of a user equipment (UE), comprising: generating a message that includes data associated with a session initiation invite for a public safety answering point (PSAP); and transmitting the message via a non-terrestrial network.

[0238] Aspect 2: The method of Aspect 1, wherein the session initiation invite is a session initiation protocol (SIP) invite.

[0239] Aspect 3 : The method of any of Aspects 1-2, wherein the message is a short messaging service (SMS) message or a multimedia messaging service (MMS) message.

[0240] Aspect 4: The method of any of Aspects 1-3, further comprising: detecting that a service via a terrestrial network is unavailable; enabling one or more non-terrestrial networkbands; and acquiring service on the non-terrestrial network, wherein transmitting the message via the non-terrestrial network is responsive to detecting that the service via the terrestrial network is unavailable.

[0241] Aspect 5: The method of Aspect 4, wherein the one or more non-terrestrial network bands include one or more narrowband non-terrestrial network bands.

[0242] Aspect 6: The method of any of Aspects 1-5, further comprising: detecting that an internet protocol multimedia subsystem (IMS) service is unavailable; enabling one or more nonterrestrial network bands; and acquiring service on the non-terrestrial network, wherein transmitting the message via the non-terrestrial network is responsive to detecting that the IMS service is unavailable.

[0243] Aspect 7: The method of Aspect 6, wherein the one or more non-terrestrial network bands include one or more narrowband non-terrestrial network bands.

[0244] Aspect 8: The method of any of Aspects 1-7, wherein transmitting the message comprises: transmitting multiple concatenated messages that include the data associated with the session initiation invite.

[0245] Aspect 9: The method of any of Aspects 1-8, wherein generating the message comprises: generating, at an internet protocol multimedia subsystem (IMS) layer of the UE, the session initiation invite; forwarding the session initiation invite from the IMS layer to a wireless messaging services layer of the UE; and generating, at the wireless messaging services layer, a transfer protocol data unit (TPDU) for the message, the TPDU including the data associated with the session initiation invite and having a destination address set to an address of the PSAP.

[0246] Aspect 10: The method of Aspect 9, wherein transmitting the message comprises: forwarding the TPDU for the message to a non-access stratum (NAS) messaging service layer of the UE; and transmitting, from the NAS messaging service layer, the message via the nonterrestrial network.

[0247] Aspect 11 : The method of any of Aspects 1-10, further comprising: receiving an acknowledgment message that includes a response to the session initiation invite.

[0248] Aspect 12: The method of any of Aspects 1-11, wherein the message is a first message, and wherein the method further comprises: receiving a second message that indicates a request for retransmission of the data associated with the session initiation invite.

[0249] Aspect 13: The method of any of Aspects 1-12, further comprising: receiving, via a real-time text (RTT) communication channel between the UE and the PSAP, a request for retransmission of the data associated with the session initiation invite.

[0250] Aspect 14: The method of any of Aspects 1-13, wherein the data associated with the session initiation invite includes one or more of data relating to a vehicle event, user emergency data, or user non-emergency data.

[0251] Aspect 15: A method of wireless communication performed at an apparatus of a device, comprising: obtaining a message that includes data associated with a session initiation invite for a public safety answering point (PSAP); and generating the session initiation invite using the data associated with the session initiation invite in the message.

[0252] Aspect 16: The method of Aspect 15, further comprising: outputting the session initiation invite.

[0253] Aspect 17: The method of any of Aspects 15-16, wherein the session initiation invite is a session initiation protocol (SIP) invite.

[0254] Aspect 18: The method of any of Aspects 15-17, wherein the message is a short messaging service (SMS) message or a multimedia messaging service (MMS) message.

[0255] Aspect 19: The method of any of Aspects 15-18, wherein obtaining the message comprises: obtaining multiple concatenated messages that include the data associated with the session initiation invite.

[0256] Aspect 20: The method of any of Aspects 15-19, further comprising: outputting an acknowledgment message that includes a response to the session initiation invite.

[0257] Aspect 21: The method of any of Aspects 15-20, wherein the message is a first message, and wherein the method further comprises: outputting a second message that indicates a request for retransmission of the data associated with the session initiation invite.

[0258] Aspect 22: The method of any of Aspects 15-21, further comprising: outputting an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call.

[0259] Aspect 23: The method of any of Aspects 15 or 17-21, further comprising: receiving an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call.

[0260] Aspect 24: The method of any of Aspects 15, 17-21, or 23, further comprising: transmitting, via a real-time text (RTT) communication channel between a user equipment and the PSAP, a request for retransmission of the data associated with the session initiation invite.

[0261] Aspect 25: The method of any of Aspects 15-24, wherein the data associated with the session initiation invite includes one or more of data relating to a vehicle event, user emergency data, or user non-emergency data.

[0262] Aspect 26: A method of wireless communication performed at an apparatus of a user equipment (UE), comprising: transmitting a request to establish a real-time text (RTT) communication channel for communication between the UE and a public safety answering point (PSAP); and communicating with the PSAP via the RTT communication channel.

[0263] Aspect 27: The method of Aspect 26, further comprising: transmitting a session initiation invite for the PSAP via an internet protocol multimedia subsystem (IMS) service.

[0264] Aspect 28: The method of any of Aspects 26-27, further comprising: transmitting, via a non-terrestrial network, a message that includes data associated with a session initiation invite for the PSAP.

[0265] Aspect 29: The method of any of Aspects 26-28, further comprising: receiving an indication that the RTT communication channel has been established, wherein communicating with the PSAP via the RTT communication channel is responsive to receiving the indication.

[0266] Aspect 30: The method of any of Aspects 26-29, wherein communicating with the PSAP via the RTT communication channel comprises: receiving a request for user data via the RTT communication channel.

[0267] Aspect 31 : The method of any of Aspects 26-30, wherein communicating with the PSAP via the RTT communication channel comprises: transmitting user data via the RTT communication channel.

[0268] Aspect 32: The method of any of Aspects 26-31, wherein communicating with the PSAP via the RTT communication channel comprises: receiving one or more messages for a vehicle occupant via the RTT communication channel.

[0269] Aspect 33 : An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-32.

[0270] Aspect 34: A device for wireless communication, comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to perform the method of one or more of Aspects 1-32.

[0271] Aspect 35: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-32.

[0272] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instmctions executable by a processor to perform the method of one or more of Aspects 1-32.

[0273] Aspect 37: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-32.

[0274] Aspect 38: An apparatus for wireless communication at a user equipment (UE), comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the UE to perform the method of one or more of Aspects 1-32.

[0275] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0276] As used herein, the term “component” is intended to be broadly construed as hardware and / or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0277] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0278] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0279] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connectionwith the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Claims

WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising: one or more memories; and one or more processors, coupled to the one or more memories, and configured to cause the UE to: generate a message that includes data associated with a session initiation invite for a public safety answering point (PSAP); and transmit the message via a non-terrestrial network.

2. The apparatus of claim 1, wherein the session initiation invite is a session initiation protocol (SIP) invite.

3. The apparatus of claim 1, wherein the message is a short messaging service (SMS) message or a multimedia messaging service (MMS) message.

4. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: detect that a service via a terrestrial network is unavailable; enable one or more non-terrestrial network bands; and acquire service on the non-terrestrial network, wherein the one or more processors are configured to cause the UE to transmit the message via the non-terrestrial network responsive to detecting that the service via the terrestrial network is unavailable.

5. The apparatus of claim 4, wherein the one or more non-terrestrial network bands include one or more narrowband non-terrestrial network bands.

6. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: detect that an internet protocol multimedia subsystem (IMS) service is unavailable; enable one or more non-terrestrial network bands; and acquire service on the non-terrestrial network, wherein the one or more processors are configured to cause the UE to transmit the message via the non-terrestrial network responsive to detecting that the IMS service is unavailable.

7. The apparatus of claim 6, wherein the one or more non-terrestrial network bands include one or more narrowband non-terrestrial network bands.

8. The apparatus of claim 1, wherein the one or more processors, to cause the UE to transmit the message, are configured to cause the UE to: transmit multiple concatenated messages that include the data associated with the session initiation invite.

9. The apparatus of claim 1, wherein the one or more processors, to cause the UE to generate the message, are configured to cause the UE to: generate, at an internet protocol multimedia subsystem (IMS) layer of the UE, the session initiation invite; forward the session initiation invite from the IMS layer to a wireless messaging services layer of the UE; and generate, at the wireless messaging services layer, a transfer protocol data unit (TPDU) for the message, the TPDU including the data associated with the session initiation invite and having a destination address set to an address of the PSAP.

10. The apparatus of claim 9, wherein the one or more processors, to cause the UE to transmit the message, are configured to cause the UE to: forward the TPDU for the message to a non-access stratum (NAS) messaging service layer of the UE; and transmit, from the NAS messaging service layer, the message via the non-terrestrial network.

11. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: receive an acknowledgment message that includes a response to the session initiation invite.

12. The apparatus of claim 1, wherein the message is a first message, and wherein the one or more processors are further configured to cause the UE to: receive a second message that indicates a request for retransmission of the data associated with the session initiation invite.

13. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to:receive, via a real-time text (RTT) communication channel between the UE and the PSAP, a request for retransmission of the data associated with the session initiation invite.

14. The apparatus of claim 1, wherein the data associated with the session initiation invite includes one or more of data relating to a vehicle event, user emergency data, or user nonemergency data.

15. An apparatus for wireless communication at a device, comprising: one or more memories; and one or more processors, coupled to the one or more memories, and configured to cause the device to: obtain a message that includes data associated with a session initiation invite for a public safety answering point (PSAP); and generate the session initiation invite using the data associated with the session initiation invite in the message.

16. The apparatus of claim 15, wherein the one or more processors are further configured to cause the device to: output the session initiation invite.

17. The apparatus of claim 15, wherein the session initiation invite is a session initiation protocol (SIP) invite, and wherein the message is a short messaging service (SMS) message or a multimedia messaging service (MMS) message.

18. The apparatus of claim 15, wherein the one or more processors, to cause the device to obtain the message, are configured to cause the device to: obtain multiple concatenated messages that include the data associated with the session initiation invite.

19. The apparatus of claim 15, wherein the one or more processors are further configured to cause the device to: output an acknowledgment message that includes a response to the session initiation invite.

20. The apparatus of claim 15, wherein the message is a first message, and wherein the one or more processors are further configured to cause the device to:output a second message that indicates a request for retransmission of the data associated with the session initiation invite.

21. The apparatus of claim 15, wherein the one or more processors are further configured to cause the device to: output an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call.

22. The apparatus of claim 15, wherein the one or more processors are further configured to cause the device to: receive an indication that the session initiation invite is to be unaccompanied by establishment of a data radio bearer or reception of a voice call.

23. The apparatus of claim 15, wherein the one or more processors are further configured to cause the device to: transmit, via a real-time text (RTT) communication channel between a user equipment and the PSAP, a request for retransmission of the data associated with the session initiation invite.

24. An apparatus for wireless communication at a user equipment (UE), comprising: one or more memories; and one or more processors, coupled to the one or more memories, and configured to cause the UE to: transmit a request to establish a real-time text (RTT) communication channel for communication between the UE and a public safety answering point (PSAP); and communicate with the PSAP via the RTT communication channel.

25. The apparatus of claim 24, wherein the one or more processors are further configured to cause the UE to: transmit a session initiation invite for the PSAP via an internet protocol multimedia subsystem (IMS) service.

26. The apparatus of claim 24, wherein the one or more processors are further configured to cause the UE to: transmit, via a non-terrestrial network, a message that includes data associated with a session initiation invite for the PSAP.

27. The apparatus of claim 24, wherein the one or more processors, to cause the UE to communicate with the PSAP via the RTT communication channel, are configured to cause the UE to: receive a request for user data via the RTT communication channel; and transmit the user data via the RTT communication channel.

28. The apparatus of claim 24, wherein the one or more processors, to cause the UE to communicate with the PSAP via the RTT communication channel, are configured to cause the UE to: receive one or more messages for a vehicle occupant via the RTT communication channel.

29. A method of wireless communication performed at an apparatus at a user equipment (UE), comprising: generating a message that includes data associated with a session initiation invite for a public safety answering point (PSAP); and transmitting the message via a non-terrestrial network.

30. The method of claim 29, wherein the message is a short messaging service (SMS) message or a multimedia messaging service (MMS) message.

Images