WO2025188500A1

WO2025188500A1 - Techniques for transmission of low data rate data using control plane cellular internet of things in satellite network systems

Info

Publication number: WO2025188500A1
Application number: PCT/US2025/017077
Authority: WO
Inventors: Amer Catovic; Alberto Rico Alvarino; Haris Zisimopoulos; Umesh PHUYAL; Soo Bum Lee; Bharat Shrestha; Lenaig Genevieve CHAPONNIERE; Prasada Veera Reddy KADIRI
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-03-08
Filing date: 2025-02-24
Publication date: 2025-09-12
Anticipated expiration: 2026-09-08
Also published as: WO2025188500A8

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment may receive, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer dedicated to transmission of data packets to the network entity. Based on the configuration, the UE may establish the first signaling radio bearer and transmit a data packet to the network via the first signaling radio bearer. The data packet may be a voice data packet associated with a voice call. The UE may establish a second signaling radio bearer dedicated to transmission of call signaling packets to the network entity and may transmit a call signaling packet associated with the voice call to the network via the second signaling radio bearer. The network entity may establish separate Non-IP Data Delivery bearers dedicated to respective transmissions of the voice data packet and call signaling packet to a Service Capability Exposure Function.

Description

TECHNIQUES FOR TRANSMISSION OF LOW DATA RATE DATA USING CONTROL PLANE CELLULAR INTERNET OF THINGS IN SATELLITE NETWORK SYSTEMS

CROSS REFERENCE

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20240100169 by CATOVIC et al., entitled “TECHNIQUES FOR TRANSMISSION OF LOW DATA RATE DATA USING CONTROL PLANE CELLULAR INTERNET OF THINGS IN SATELLITE NETWORK SYSTEMS,” filed March 8, 2024, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.

FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including techniques for transmission of low data rate data using Control Plane Cellular Internet of Things (CP CIoT) in satellite network systems.

BACKGROUND

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

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for transmission of low data rate data using Control Plane Cellular Internet of Things (CP CIoT) in satellite network systems. For example, the described techniques provide for transmission of low data rate user data (e.g., voice data associated with a voice call) by a user equipment (UE) using a non-IP Data Delivery (NIDD) service provided by the CP CIoT. Typically, user data, such as voice data, is carried over Internet Protocol (IP) networks using a Real-time Transport Protocol (RTP) and Transmission Control Protocol (TCP)/IP protocol stack. In some cases, however, significant overhead may be associated with the use of the RTP/TCP/IP protocol stack, and such overhead may be prohibitive with respect to achieving low data rates needed to support satellite network systems. Use of the NIDD service by the UE may enable the UE to transmit and receive raw non-IP packets of user data, such as packets associated with voice data, over a signaling bearer and without any underlying transport protocols, thereby avoiding the overhead associated with transmission using the RTP/TCP/IP protocol stack. Using the NIDD bearer, the raw non-IP packets of user data, such as voice data, and in some cases, associated control signaling, such as call signaling, may be transmitted from the UE, via a core network, to a gateway that services non-IP data. The non-IP gateway may in turn communicate with one or more application servers, such as a voice application server, to receive and process the non-IP packets. In some cases, the non-IP packets, such as the voice data packets and/or call signaling packets, may be encapsulated in a container, such as a non-access stratum (NAS) message, and the non-IP packets may be transmitted from the UE, via the core network, to the non-IP gateway while encapsulated in the NAS message.

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity, establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity, and transmitting, via the first signaling radio bearer, a data packet.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity, establish, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity, and transmit, via the first signaling radio bearer, a data packet.

[0007] Another UE for wireless communications is described. The UE may include means for receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity, means for establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity, and means for transmitting, via the first signaling radio bearer, a data packet.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity, establish, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity, and transmit, via the first signaling radio bearer, a data packet. [0009] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the network entity may be a satellite radio access network.

[0010] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, transmitting, via the first signaling radio bearer, the data packet may include operations, features, means, or instructions for encapsulating the data packet in a container that includes a header and transmitting, via the first signaling radio bearer, the data packet encapsulated in the container.

[0011] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the data packet includes a voice data packet associated with a voice call and the first signaling radio bearer may be dedicated to transmission of voice data packets.

[0012] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing the first signaling radio bearer may be based on initiation of the voice call.

[0013] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing a second signaling radio bearer dedicated to transmission of call signaling packets and transmitting, via the second signaling radio bearer, a call signaling packet associated with the voice call.

[0014] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, transmitting, via the second signaling radio bearer, the call signaling packet may include operations, features, means, or instructions for encapsulating the call signaling packet in a container that includes a header and transmitting, via the second signaling radio bearer, the call signaling packet encapsulated in the container.

[0015] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the network entity and based on initiation of a voice call, a request to establish a packet data session and establishing the packet data session.

[0016] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the packet data session may be a Packet Data Network (PDN) connection to a Third Generation Partnership Project (3 GPP) Fourth Generation (4G) core network.

[0017] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the request to establish the packet data session includes an indication that the packet data session may be for a voice service or for an emergency call service.

[0018] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the request to establish the packet data session includes an indication that the packet data session may be for a Control Plane Only PDN connection.

[0019] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the signaling radio bearer configuration may be based on the request to establish the packet data session.

[0020] A method for wireless communications by a network entity is described. The method may include receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection , establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets, transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets, and receiving, via the first signaling radio bearer, a data packet.

[0021] A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to receive, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection , establish, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets, transmit, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets, and receive, via the first signaling radio bearer, a data packet.

[0022] Another network entity for wireless communications is described. The network entity may include means for receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection , means for establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets, means for transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets, and means for receiving, via the first signaling radio bearer, a data packet.

[0023] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection , establish, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets, transmit, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets, and receive, via the first signaling radio bearer, a data packet. [0024] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the signaling radio bearer configuration includes an indication that the first signaling radio bearer may be dedicated to transmission of data packets.

[0025] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the network entity may be a satellite radio access network.

[0026] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the data packet includes a voice data packet associated with a voice call and the first signaling radio bearer may be dedicated to transmission of voice data packets.

[0027] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing the first signaling radio bearer may be further based on receiving, from the UE, a request to establish the voice call via a satellite access connection.

[0028] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing a second signaling radio bearer dedicated to transmission of call signaling packets and receiving, via the second signaling radio bearer, a call signaling packet associated with the voice call.

[0029] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE and via the first signaling radio bearer or the second signaling radio bearer, a container encapsulating a packet and extracting, from the container, the packet.

[0030] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for deciphering the packet using a packet sequence number indicated in a header of the container, establishing, based on the deciphered packet including data, a first Non-IP Data Delivery (NIDD) bearer dedicated to transmission of data packets to a Service Capability Exposure Function (SCEF), and transmitting, to the SCEF and via the first NIDD bearer, the deciphered packet.

[0031] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the data may be voice date.

[0032] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for deciphering the packet using a packet sequence number indicated in a header of the container, establishing, based on the deciphered packet including a call signaling, a second Non-IP Data Delivery (NIDD) bearer dedicated to transmission of call signaling packets to a Service Capability Exposure Function (SCEF), and transmitting, to the SCEF and via the second NIDD bearer, the deciphered packet.

[0033] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing the packet data session, where the packet data session may be a PDN connection to a Third Generation Partnership Project (3 GPP) Fourth Generation (4G) core network.

[0034] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the request to establish the packet data session further includes an indication that the packet data session may be for a voice service or for an emergency call service.

BRIEF DESCRIPTION OF THE DRAWINGS

[0035] FIG. 1 shows an example of a wireless communications system that supports techniques for transmission of low data rate data using Control Plane Cellular Internet of Things (CP CIoT) in satellite network systems in accordance with one or more aspects of the present disclosure. [0036] FIG. 2 shows an example of a portion of a satellite access network system that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0037] FIG. 3 shows an example of a satellite access network system that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0038] FIG. 4 shows an example of a signal flow that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0039] FIG. 5 shows packet overhead associated with the example signal flow of FIG. 4 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0040] FIG. 6 shows an example of a signal flow that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0041] FIG. 7 shows packet overhead associated with the example signal flow of FIG. 6 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0042] FIG. 8 shows an example of a signal flow that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0043] FIG. 9 shows packet overhead associated with the example signal flow of FIG. 8 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. [0044] FIG. 10 shows an example of a process flow that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0045] FIGs. 11 and 12 show block diagrams of devices that support techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0046] FIG. 13 shows a block diagram of a communications manager that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0047] FIG. 14 shows a diagram of a system including a device that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0048] FIGs. 15 and 16 show block diagrams of devices that support techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0049] FIG. 17 shows a block diagram of a communications manager that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0050] FIG. 18 shows a diagram of a system including a device that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0051] FIGs. 19 through 22 show flowcharts illustrating methods that support techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

[0052] Various aspects of the present disclosure relate to a wireless communication device, such as a user equipment (UE), that may transmit low data rate data using Control Plane Cellular Internet of Things (CP CIoT) in satellite network systems. In satellite networks, there is a need to support low data rate voice calls. The data rate may be low due to challenging radio conditions associated with Geostationary Equatorial Orbit (GEO) satellites and due to the large coverage areas of an associated satellite beam (e.g., up to hundreds of miles in radius) comprising large numbers of UEs. For example, such satellite networks may require the data rate to be as low as 1.5 or 2 kbps. This may equate to a rate of one packet of 15-20 bytes every 80 milliseconds.

[0053] Typically, user data, such as voice data, multi-media data, and Internet traffic, may be transmitted between a UE and a core network using a dedicated user plane bearer, while signaling and control information associated with UE registration, mobility updates, security procedures, etc. may typically be transmitted between the UE and core network using a control plane bearer. CP CIoT is a feature of the 3rd Generation Partnership Project (3 GPP) that enables a UE to transmit small amounts of user data to the core network over a control plane bearer rather than over a dedicated user plane bearer. The control plane bearer may facilitate the exchange of control messages, such as Non-Access Stratum (NAS) messages, between the UE and core network in accordance with a NAS protocol. Accordingly, when data is transmitted using CP CIoT, each data packet may be encapsulated in a NAS message (e.g., Evolved Packet System (EPS) Session Management (ESM) Data Transport message). Sending user data, such as voice data, encapsulated in NAS messages over control plane bearers may reduce the need to establish user plane bearers, which, for small amounts of data (e.g., a single packet of 20 bytes), such as low rate voice data, may be inefficient in terms of signaling overhead associated with establishing the user plane bearers.

[0054] Further, the control plane bearer may permit the exchange of both Internet protocol (IP) and non-IP data, while the dedicated user plane bearer may permit the exchange of IP data, but not the exchange of non-IP data, as the 3 GPP networks are part of the global IP network, which delivers data using IP datagrams. The ability to transmit small amounts of data, such as low rate voice data, as non-IP data may reduce additional overhead, such as overhead associated with the transmission of IP data. For instance, typically, user data (e.g., voice data) is carried in IP packets over IP networks using a Real-time Transport Protocol (RTP) and Transmission Control Protocol (TCP)/IP protocol stack. In some cases, however, significant overhead (e.g., in each data packet) may be associated with the use of the RTP/TCP/IP protocol stack, and such overhead may be prohibitive with respect to achieving low data rates needed to support satellite network systems. Non-IP Data Delivery (NIDD) is a service provided in CP CIoT that may enable the UE to send and receive non-IP packets over a control plane bearer. Use of the NIDD service by the UE may enable the UE to transmit and receive raw non-IP packets of data, such as packets associated with voice data, over a control plane bearer and without any underlying transport protocols, thereby avoiding the overhead associated with transmission using the RTP/TCP/IP protocol stack.

[0055] In accordance with aspects of this disclosure, one or more NIDD bearers may be established for the dedicated transmission of raw non-IP packets of user data, such as voice data, and in some cases associated signaling data, such as call signaling data, from the UE, via a core network, and to a gateway that services non-IP data. The non-IP gateway may in turn communicate with one or more application servers, such as a voice application server, to receive and process the non-IP packets. The non-IP packets, such as the voice data packets and/or the call signaling packets, may be encapsulated in a NAS message, such as without an IP header. The NAS message encapsulating the non-IP packets may be transmitted from the UE, via the core network, to the non-IP gateway for processing by an application service, such as a voice application server.

[0056] Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for transmission of low data rate data using CP CIoT in satellite network systems.

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

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

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

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

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

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

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

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

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

[0066] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

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

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

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

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

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

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

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

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

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

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

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

[0078] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity and at least one user plane entity. The control plane entity may manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and interconnect to external networks (e.g., a service capability exposure function (SCEF)). The control plane entity may manage NAS functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. Non-IP packets may be transferred through the control plane entity. The control plane entity may be connected to services 150, such as application services provided via one or more application servers (e.g., a voice application server). The user plane entity may route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P- GW), or a user plane function (UPF)). User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to services 150, such as IP services for one or more network operators. The IP services may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet- Switched Streaming Service.

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

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

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

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

[0083] In accordance with aspects described herein, a UE 115 may receive a signaling radio bearer configuration for a first signaling radio bearer, such as in response to initiation of a voice call via a satellite access connection, and may establish the first signaling radio bearer based on the configuration. For example, the first control plane bearer may be a bearer dedicated to transmission of a user data packet, such as voice data packets associated with the voice call. In some cases, the UE 115 may further establish a second signaling radio bearer, such as a second control plane bearer, dedicated to transmission of a control signaling packet, such as a call signaling packet associated with a voice call. The user data packet may be transmitted to a network entity, such as a core network 130, via the first radio signaling bearer, and the control signaling packet may be transmitted to the network entity via the second signaling radio bearer. The network entity may establish separate NIDD bearers dedicated to respective transmissions of the user data packet and the control signaling packet to a gateway that services non-IP data. In some cases, the gateway may communicate with an application server, such as a voice application server, and the application server may further receive and process the user data packet, such as a voice data packet.

[0084] FIG. 2 shows an example of a portion of a satellite access network system 200 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. In some examples, the satellite access network system 200 may implement or be implemented by aspects of the wireless communications system 100, as described with reference to FIG. 1. The satellite access network system 200 may include a plurality of UEs 215 (such as 215-a, 215-b, 215-c, and 215-d), a core network 230, and a non-terrestrial network (NTN) node 240. The satellite access network system 200 may support multiple RATs, including 4G LTE, 5G NR, or a combination thereof. For example, the NTN node 240 may support one or more of 4G LTE or 5G NR. It should be noted that the satellite access network system 200 may support radio access technologies beyond 5G NR.

[0085] The NTN node 240 may be a satellite, HAPS, HAV, unmanned aerial vehicle, aircraft, balloon, etc. For instance, the NTN node 240 may be in an orbit, such as low earth orbit, medium earth orbit, geostationary earth orbit, or other non- geostationary earth orbit. The NTN node 240 may be positioned at some distance from Earth (e.g., hundreds or thousands of kilometers from Earth), which may vary or remain relatively fixed. The NTN node 240 may include communication circuitry (e.g., one or more processors, memories, modems, baseband circuitries, among other examples), one or more antennas, or one or more transponders to facilitate reception and transmission of radio frequency (RF) signals. In the example of the satellite access network system 200, the NTN node 240 may be a satellite that implements a base station. For instance, the NTN node 240 may be an example of base station 140 described with reference to FIG. 1 and implemented at a satellite. The NTN node 240 may serve a geographic coverage area 210. The geographic coverage area 210 may be an example of the coverage area 110 described with reference to FIG. 1.

[0086] The UEs 215 (e.g., UE 215-a, 215-b, 215-c, and 215-d) may be dispersed throughout the geographic coverage area 210 and each UE 215 may be stationary, or mobile, or both at different times. The UEs 215 may be devices in different forms or having different capabilities. The UEs 215 may be examples of UEs 115 described with reference to FIG. 1.

[0087] The NTN node 240 (e.g., satellite base station) may provide the UEs 215 with connectivity to the core network 230 to provide access to one or more external networks, application services, or the like. For instance, the UEs 215 and the NTN node 240 may perform wireless communication to receive, obtain, transmit, or exchange control information or user data. The NTN node 240 may communicate the control information or user data to the core network 230 to support services for the UEs 215. The core network 230 may be a terrestrial network node and may be positioned on the Earth’s surface or relatively near to the Earth’s surface (e.g., within a mile of the Earth’s surface). In some examples, the terrestrial network node may be anchored or attached to the Earth’s surface. The core network 230 may be an example of core network 130 described with reference to FIG. 1.

[0088] The NTN node 240 (e.g., satellite base station) may facilitate a connection between the UE 215-a and the core network 230. For instance, the UE 215-a may send a request to the NTN node 240 to connect to the core network 230. The NTN node 240 may forward the request to the core network 230 and the NTN node 240 and the core network 230 may coordinate a connection and registration procedure for the UE 215-a. Upon successful registration of the UE 215-a with the core network 230, the NTN node 240 and the core network 230 may coordinate the establishment of dedicated bearers 255 for enabling the exchange of data between the UE 215-a and the core network 230. For instance, the NTN node 240 and the core network 230 may coordinate the establishment of radio bearer 255-a, for transmission of data between the UE 215-a and the NTN node 240, and SI -Application Protocol (AP) bearer 255-b, for transmission of data between the NTN node 240 and the core network 230.

[0089] The radio bearer 255-a may include signaling radio bearers (SRBs) for control plane signaling, e.g., to carry control and signaling information between the UE 215-a and the NTN node 240, and may include data radio bearers (DRBs) for user plane signaling, e.g., to carry user data between the UE 215-a and the NTN node 240. In accordance with aspects described herein, in some cases dedicated SRBs may be established for the transmission of user data, such as non-IP data (e.g., voice data).

[0090] The Sl-AP bearer 255-b may include one or more SI bearers for control plane signaling between the NTN node 240 and the core network 230. The NTN node 240 may facilitate the exchange of data between the UE 215-a and the core network 230 by transmitting the control and signaling information and user data between the UE 215-a and the core network 230 over the radio bearer 255-a and the Sl-AP bearer 255-b. [0091] In some cases, a satellite access network system may have low data rate requirements due to challenging radio conditions associated with GEO satellites and due to the large coverage areas of an associated satellite beam comprising large numbers of UEs. In accordance with aspects described herein, in some cases, to support the low data rate requirements of such satellite access network systems, one or more devices (such as the UE 215-a, the core network 230, or the NTN node 240) may be configured to provide for the transmission of low data rate data using a NIDD service provided by the CP CIoT. Typically, user data is carried over IP networks using RTP and TCP/IP protocol stacks. In some cases, however, significant overhead may be associated with the use of the RTP/TCP/IP protocol stacks, and such overhead may be prohibitive with respect to achieving low data rates needed to support the satellite access network system. As described herein, use of the NIDD service may enable transmission and receipt of raw non-IP packets of user data over an SRB and without any underlying transport protocols, thereby avoiding the overhead associated with transmission using the RTP/TCP/IP protocol stack.

[0092] FIG. 3 shows an example of a satellite access network system 300 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. In some examples, the satellite access network system 300 may implement or be implemented by aspects of the wireless communications system 100 or the satellite access network system 200, as described with reference to FIGs. 1 and 2. For example, the satellite access network system 300 may include a UE 315, a core network 330, a network entity, such as a base station 340 (e.g., a satellite base station), a gateway 345 (such as a SCEF), an application server 350 (such as a voice application server), an IMS server 390, and the Internet 395. The UE 315, core network 330, and base station 340 may be examples of UEs 115 or 215, core network 130 or 230, and base station 140 or NTN node 240, respectively, as described with reference to FIGs. 1 and 2. The satellite access network system 300 may support multiple RATs, including 4G LTE, 5G NR, or a combination thereof. For example, the base station 340 may support one or more of 4G LTE or 5GNR. It should be noted that the satellite access network system 300 may support radio access technologies beyond 5GNR. [0093] In this example, the satellite access network system 300 may support the transmission of non-IP data, such as raw non-IP packets of data associated with a voice call. The UE 315 and the base station 340 may perform wireless communication to receive, obtain, transmit, or exchange control information or user data, such as data associated with the voice call. For instance, initially, RRC signaling, such as RRC connection setup messages, may be transmitted between the UE 315 and the base station 340 to establish an RRC connection between the UE 315 and the base station 340, negotiate modulation, power, and the like. Additionally, one or more RRC configuration messages may be transmitted from the base station 340 to the UE 315 to configure parameters at the UE, configure the UE for various services, establish radio bearers, and the like.

[0094] The base station 340 may be a satellite base station. The base station 340 may provide the UE 315 with connectivity to the core network 330 to provide access to one or more external networks, application services (e.g., voice services for the UE 315), or the like. For instance, the base station 340 may communicate, to the core network 330, control information (e.g., call signaling packets associated with a voice call) or user data (e.g., voice data packets associated with a voice call) to support services for the UE 315.

[0095] The base station 340 may facilitate a connection between the UE 315 and the core network 330. For instance, the UE 315 may send a request (such as a request to establish a packet data session) to the base station 340 to connect to the core network 330. The base station 340 may forward the request to the MME of the core network 330, and the MME may manage the connection and registration procedure. Upon successful registration of the UE 315 with the core network 330, the base station 340 and the MME of the core network 330 may coordinate the establishment of dedicated bearers 355, for a PDN connection, enabling the exchange of data between the UE 315 and the core network 330. For instance, the base station 340 and the MME may coordinate the establishment of radio bearers 355-a, for transmission of data between the UE 315 and the base station 340, and SI -Application Protocol (AP) bearers 355-b, for transmission of data between the base station 340 and the core network 330. In particular, the radio bearers 355-a established by the base station 340, in coordination with the MME, may include signaling radio bearers (SRBs) for control plane signaling, e.g., to carry control and signaling information between the UE 315 and the base station 340, and may include data radio bearers (DRBs) for user plane signaling, e.g., to carry user data between the UE 315 and the base station 340. The Sl-AP bearers 355-b may include one or more SI bearers for control plane signaling between the base station 340 and the MME of the core network 330. The base station 340 may facilitate the exchange of data between the UE 315 and the core network 330 by managing radio resources and transmitting the control and signaling information and user data between the UE 315 and the core network 330.

[0096] In some cases, the core network 330 may be connected to one or more external networks or devices through the gateway 345 (e.g., SCEF). The gateway 345 may be a gateway that receives non-IP data from the MME of the core network 330. The core network 330 may be connected to the gateway 345 via a dedicated bearer. For instance, the MME of the core network 330 may establish an NIDD bearer 355-c to transmit non-IP data from the MME of the core network 330 to the gateway 345. For instance, the NIDD bearer may be used to carry raw non-IP user data, such as data associated with a voice call, between the core network 330 and the gateway 345.

[0097] The gateway 345 may be connected to one or more external networks or devices, such as the application server 350 (e.g., a voice application server), via a communication link 365-a. In some cases, the gateway 345 and the application server 350 may be co-located. The gateway 345 may forward, via a communication link 365-a, non-IP data received from the MME of the core network 330 to the application server 350 for processing or for further forwarding to one or more external networks or devices. For instance, the gateway 345 may forward the non-IP user data (e.g., data associated the voice call) to the application server 350 (e.g., a voice application server), and in some cases, the application server 350 may forward, via a communication link 365-b, the user data to the IMS server 390, which may be configured to carry the user data, such as the voice call, over IP networks, or, via a communication link 365-c, to the Internet 395.

[0098] FIG. 4 shows an example of a signal flow 400 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. In some examples, the signal flow 400 may implement or be implemented by aspects of the wireless communications system 100 or the satellite access network systems 200 and 300, as described with reference to FIGs. 1, 2, and 3, respectively. For example, the signal flow 400 may illustrate the flow of control signaling and user data, such as control signaling and voice data associated with a low data rate voice call, using an NIDD service provided by the CP CIoT. However, the signal flow 400 may not be limited to the flow of control signaling and user data associated with a voice call, and may include any type of control signaling and user data. The signal flow 400 may illustrate the flow of control signaling and data (e.g., data associated with a low data rate voice call) and carried by one or more bearers, such as an SRB 455-a, an Sl-AP bearer 455-b, and an NIDD bearer 455-c, between a UE 415, a base station 440 (e.g., a satellite base station), a core network 430 (e.g., MME), and a gateway 445 (e.g., SCEF). The UE 415 may be an example of UE 115, UE 215, or UE 315, as described with reference to FIGs. 1, 2, and 3, respectively. The core network 430 may be an example of core network 130, core network 230, or core network 330, as described with reference to FIGs. 1, 2, and 3, respectively. The base station 440 may be an example of base station 140, NTN node 240, or base station 340, as described with reference to FIGs. 1, 2, and 3, respectively. The gateway 445 may be an example of gateway 345, as described with reference to FIG. 3.

[0099] The SRB 455-a may be established to carry control plane signaling between the UE 415 and the base station 440. For instance, the SRB 455-a may carry RRC signaling for managing radio access connections, radio resources, negotiate modulation and power, etc. between the UE 415 and the base station 440. The SRB 455-a may additionally carry NAS signaling to support registration, session management, mobility updates, security procedures, etc. between the UE 415 and the base station 440. When the base station 440 receives the NAS signaling, the base station 440 may extract a NAS message encapsulated in an RRC message from the signaling. The extracted message may be encapsulated in an Sl-AP protocol message and carried over the Sl-AP bearer 455-b to the core network 430 (e.g., MME). In some cases, to support the low date rate requirements of carrying voice calls over a satellite network system, instead of transmitting the user data associated with the voice call between the UE 415 and the core network 430 using a user plane bearer, CP CIoT may be used to enable the transmission of small amounts of user data from the UE 415 and to the core network 430 over a control plane bearer, such as the SRB 455-a. CP CIoT may provide a service, such as the NIDD service, that enables the UE 415 to transmit and receive raw non-IP packets of data, such as raw non-IP packets associated with a voice call, over the control plane bearer, such as over the SRB 455-a. Transmission of the non-IP packets of user data reduces overhead associated with each packet by avoiding the overhead associated with transmission of IP packets using the RTP/TCP/IP protocol stack. Further, transmission of the non-IP packets over the control plane bearer may avoid the need to establish user plane bearers, which, for transmission of small amounts of data (e.g., a single packet of 20 bytes), may be inefficient in terms of signaling overhead.

[0100] User data sent using the CP CIoT, such as the data packets associated with a voice call, may be encapsulated in a NAS message and transmitted via RRC signaling. For instance, the data packets may be encapsulated in a payload of an ESM Data Transport NAS message. Encapsulating the data packets in the ESM Data Transport NAS message may allow for the logical separation (and later identification by the core network 430) of such packets from other types of information sent over the SRB 455-a. For instance, the UE 415 may send packets of user data (e.g., user data associated with a voice call) encapsulated in the ESM Data Transport NAS message via RRC signaling. In this case, the NAS message may include signaling packets (such as call signaling packets associated with a voice call (in some cases referred to as IMS signaling) (e.g., signaling associated with initiating the call, a ringing indication, call establishment, call termination, and the like)), data packets (such as voice data packets associated with the voice call), or a combination thereof.

[0101] The NAS message (e.g., the ESM Data Transport NAS message) encapsulating the packets of data may be sent to the base station 440 via RRC signaling over the SRB 455-a. The NAS message may be transparently sent through the base station 440, such as via the Sl-AP bearer 455-b, and to the core network 430. That is, because the base station 440 may not process or interpret NAS messages, upon receiving the NAS message from the UE 415, the base station 440 may simply forward the NAS message to the core network 430, via the Sl-AP bearer 455-b, without attempting to process the message. For instance, upon determining that the message is a NAS message, the base station 440 may forward the NAS message to the MME of the core network 430.

[0102] Upon receiving the NAS message, the MME of the core network 430, may extract the packet from the NAS message and send the packet, via the NIDD bearer 455-c, to the gateway 445 (e.g., the SCEF). The NIDD bearer 455-c may be dedicated to transmission of the packets associated with data, such as voice call data). In some cases, the data packets may be further forwarded or processed by an external network or device, such as an application server.

[0103] FIG. 5 shows an example of packet overhead associated with example signal flow 400 of FIG. 4. For example, tables 500-a and 500-b illustrate packet overhead associated with the signal flow 400, described with respect to FIG. 4. Table 500-a shows packet overhead associated with transmission of a user data packet, e.g., a voice data packet, encapsulated in a NAS message and carried over SRB 455-a, and table 500- b shows packet overhead associated with transmission of a control signaling packet, e.g., a call signaling packet, encapsulated in a NAS message and carried over SRB 455- a.

[0104] For instance, transmitting the control signaling and user data packets, e.g., call signaling and voice data packets, encapsulated in the NAS message (e.g., EMS Data Transport NAS message) avoids overhead associated with the use of the RTP/TCP/IP protocol stack, but includes overhead associated with the NAS message and the RRC signaling that transports the NAS message. For instance, in the case of a voice call, for each voice data packet there may be corresponding overhead of approximately 14-18 bytes (which may be significant for a voice call packet having a payload of about 15 bytes, e.g., 93-120% overhead) associated with transmitting the packet encapsulated in the NAS message as shown in table 500-a. Such overhead may affect the quality of the voice call in a satellite network system. Further, for each call signaling packet there may be approximately 26 bytes of overhead. Call signaling may typically occur at the beginning and the end of a voice call and may not normally interfere with the voice data packets. Therefore, there may be a higher tolerance for overhead than in the case of the voice data. However, such overhead may impact the amount of time to establish the voice call, increasing call setup time, and thereby impacting the user experience.

[0105] In addition, sending the control signaling (e.g., call signaling) and user data packets (e.g., voice data packets) encapsulated in the NAS message over a control plane bearer, such as SRB 455-a, as shown and described with respect to FIG. 4, requires the use of acknowledge mode. That is, every packet sent over an SRB, by default, is sent in acknowledge mode, which enables the retransmission of a lost packet. However, this may not be necessary for data packets associated with a voice call because by the time the lost packets are retransmitted the conversation associated with the voice call will have already moved on. Accordingly, a significant amount of bandwidth may be wasted by retransmitting voice data packets that are, by the time they are retransmitted, obsolete.

[0106] Further, sending the signaling and user data packets (such as call signaling and voice data packets) encapsulated in the NAS message does not allow for separate, dedicated logical channels for the user data and signaling. Having dedicated logical channels would allow the network, such as the base station 440, the core network 430, or combination thereof, to treat user data and signaling data received from each dedicated channel differently, such as to provide different Quality of Service (QoS) or different prioritization based on the channel.

[0107] FIG. 6 shows an example of a signal flow 600 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. In some examples, the signal flow 600 may implement or be implemented by aspects of the wireless communications system 100 or the satellite access network systems 200 or 300, as described with reference to FIGs. 1, 2, and 3, respectively. For example, the signal flow 600 may illustrate the flow of control signaling and user data, such as control signaling and voice data associated with a low data rate voice call, using an NIDD service provided by the CP CIoT. However, the signal flow 600 may not be limited to the flow of control signaling and user data associated with a voice call, and may include any type of control signaling and user data. The signal flow 600 may illustrate the flow of control signaling and user data (e.g., voice data associated with a low data rate voice call) carried by one or more bearers, such as an SRB 655-a, an Sl-AP bearer 655-b, an NIDD bearer 655-c, and a new SRB 655-d between a UE 615, a base station 640 (e.g., a satellite base station), a core network 630 (e.g., MME), and a gateway 645 (e.g., SCEF). The UE 615 may be an example of UE 115, UE 215, or UE 315, as described with reference to FIGs. 1, 2, and 3, respectively. The core network 630 may be an example of core network 130, core network 230, or core network 330, as described with reference to FIGs. 1, 2, and 3, respectively. The base station 640 may be an example of base station 140, NTN node 240, or base station 340, as described with reference to FIGs. 1, 2, and 3, respectively. The gateway 645 may be an example of gateway 345, as described with reference to FIG. 3.

[0108] The signal flow 600 may be implemented to further reduce the overhead, bandwidth, and logical channel constraints associated with the signal flow 400, described with respect to FIG. 4. For instance, the signal flow 600 may introduce a new SRB 655-d that may be dedicated to the transmission of the user data packets (e.g., voice data packets). The new SRB 655-d may be established with RLC transparent mode (TM) dedicated to encapsulating user data packets and the RLC TM may be a mode that does not provide for the retransmission of lost packets. The new SRB 655-d may further provide a separate logical channel for user data packets (e.g., voice data packets) to enable differentiated handling at the MAC and PHY layers.

[0109] In this case, because a dedicated SRB exists for carrying the user data packets, it may not be necessary to have such packets encapsulated in the NAS message, thereby eliminating much of the overhead associated with encapsulating the user data packets in NAS message, such as described with respect to FIG. 5 (although in some cases, use of the NAS message for encapsulating such user data in RRC signaling may remain for backwards compatibility purposes). In this example, the control signaling packets (e.g., call signaling packets) may continue to be encapsulated in a NAS message and carried over the SRB 655-a. Although some overhead may continue to be associated with carrying the control signaling packets, such as call signaling packets, encapsulated in the NAS message, as discussed, there may be a higher tolerance for overhead associated with the call signaling packets as compared to overhead associated with the user data packets. [0110] FIG. 7 shows an example of packet overhead associated with example signal flow 600 of FIG. 6. For example, tables 700-a and 700-b illustrate packet overhead associated with the signal flow 600, described with respect to FIG. 6. Table 700-a shows packet overhead associated with transmission of a user data packet, e.g., a voice data packet, carried over new SRB 655-d, and table 700-b shows packet overhead associated with transmission of a control signaling packet, e.g., a call signaling packet, encapsulated in an NAS message and carried over SRB 655-a.

[OHl] As described with respect to FIG. 6, transmitting user data packets on a dedicated SRB, such as new SRB 655-d, in accordance with the signal flow 600 of FIG. 6 may allow for the reduction of overhead associated with each user data packet relative to overhead associated with a user data packet encapsulated in a NAS message and transmitted via the SRB 455-a, in accordance with the signal flow 400 of FIG. 4.

[0112] In particular, NAS related overhead (e.g., NAS/L3 overhead) may be eliminated from the header of each user data packet when carried by the new SRB 655- d, since the packets carried by the new SRB 655-d may be directly mapped to the NIDD payload. For instance, the NAS user data container header and the NAS message header, shown in table 500-a of FIG. 5, may be eliminated in table 700-a.

[0113] Additionally, RRC overhead associated with RRC message identification may be reduced or eliminated for the user data packet (e.g., a voice data packet) carried by the new SRB 655-d, as RRC messages over the new SRB 655-d may not be necessary since the raw packets may be carried by the new SRB 655-d. As a result, the RRC header, shown in table 500-a of FIG. 5, may be limited to a small number of bits (e.g., 2-3 bits) in table 700-a to include a length indicator indicating a size or length of the packet. In some cases, the RRC header may be eliminated altogether by negotiating, during the initial establishment of the new SRB 655-d, a fixed size or length of packets that may be carried over the new SRB 655-d.

[0114] Further, as the new SRB 655-d may be established in RLC transparent mode, in which lost packets are not retransmitted, thereby conserving bandwidth resources, RLC overhead may be eliminated from the user data packets carried by the new SRB 655-d. For instance, the RLC Acknowledge Mode (AM) header, shown in table 500-a of FIG. 5, may be eliminated in table 700-a.

[0115] As a result, each user data packet carried over the new SRB 655-d may have a significantly smaller amount of overhead as compared to a user data packet encapsulated in a NAS message and carried over SRB 455-a, as described with respect to FIG. 4 and shown in table 500-a of FIG. 5. For instance, as shown in table 700-a, a voice data packet carried over the new SRB 655-d may have approximately 34-35 bits of overhead (approximately 30%). For example, as shown in table 700-a of FIG. 7, the overhead for the voice data packet may include an RTP sequence number used for packet re-ordering and, optionally, packet encryption at the RTP layer, an optional RDS header which may, in some cases, be used to differentiate user data packets (e.g., voice data packets) from control signaling packets (e.g., call signaling packets) when the packets are eventually transmitted from the MME of the core network 630 to the gateway 645 (e.g., SCEF) via the NIDD bearer 655-c, a packet sequence number used for encryption at the NAS layer, an optional RRC header indicating a length or size of the packet, and a MAC header used to identify the new SRB 655-d (such as to identify the SRB as one dedicated to transmission of user data packets).

[0116] Encapsulating the user data packets in a dedicated SRB may allow for the reduction in overhead in each user data packet in a manner that supports the low date rate requirements, such as for voice calls in satellite access network systems, such as satellite access network system 200, described with respect to FIG. 2.

[0117] FIG. 8 shows an example of a signal flow 800 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. In some examples, the signal flow 800 may implement or be implemented by aspects of the wireless communications system 100 or the satellite access network systems 200 or 300, as described with reference to FIGs. 1, 2, and 3, respectively. For example, the signal flow 800 may illustrate the flow of control signaling and user data, such as control signaling and voice data associated with a low data rate voice call, using an NIDD service provided by the CP CIoT. However, the signal flow 800 may not be limited to the flow of control signaling and data associated with a voice call, and may include any type of control signaling and user data. The signal flow 800 may illustrate the flow of control signaling and user data, such as voice data associated with a low data rate voice call, carried by one or more bearers, such as an SRB 855-a, an Sl-AP bearer 855-b, a first NIDD bearer 855-c, a second NIDD bearer 855-f, a first new SRB 855-d, and a second new SRB 855-e between a UE 815, a base station 840 (e.g., a satellite base station), a core network 830 (e.g., MME), and a gateway 845 (e.g., SCEF). The UE 815 may be an example of UE 115, UE 215, or UE 315, as described with reference to FIGs. 1, 2, and 3, respectively. The core network 830 may be an example of core network 130, core network 230, or core network 330, as described with reference to FIGs. 1, 2, and 3, respectively. The base station 840 may be an example of base station 140, NTN node 240, or base station 340, as described with reference to FIGs. 1, 2, and 3, respectively. The gateway 845 may be an example of gateway 345, as described with reference to FIG. 3.

[0118] The signal flow 800 may be implemented to further reduce the overhead and logical channel constraints associated with the signal flow 600, described with respect to FIG 6. For instance, the signal flow 800 may introduce an additional new SRB, such as the second new SRB 855-e, that may be established with RLC AM and may be dedicated to the transmission of control signaling packets, such as the call signaling packets associated with a voice call. Accordingly, in the signal flow 800 user data packets and control signaling packets, such as voice data packets and call signaling packets, may be separately encapsulated and carried over corresponding dedicated SRBs. For instance, user data packets, e.g., voice data packets, may be encapsulated in and carried over the first new SRB 855-d, while control signaling packets, e.g., call signaling packets, may be encapsulated in and carried over the second new SRB 855-e. Because a dedicated SRB, e.g., the second new SRB 855-e, exists for carrying the control signaling packets, e.g., call signaling packets, it may not be necessary to have such packets encapsulated in the NAS message as described with respect to signal flow 600 of FIG. 6, thereby eliminating much of the overhead associated with encapsulating the packets in NAS message, such as shown in FIG. 5.

[0119] The signal flow 800 may additionally introduce a new NIDD bearer, such as new second NIDD bearer 855-f. In this case, the first NIDD bearer 855-c, which may have previously been used to carry both control signaling and user data packets, such as call signaling and voice data packets, may be dedicated to carrying the control signaling packets, e.g., call signaling packets, while the new second NIDD bearer 855-f may be dedicated to carrying user data packets, e.g., voice data packets. Each of the first and second NIDD bearers 855-c and 855-f may map to a separate NIDD Protocol Data Unit (PDU) session and each of the first new SRB 855-d and second new SRB 855-e may map to a separate one of the NIDD PDU sessions (while also maintain the legacy single bearer PDU session). In this way, end-to-end (from the UE 815 to the gateway 845) separation of the user data and control signaling packets, e.g., voice data and call signaling packets may be enabled, avoiding the need for packet identification at the packet level. This further separation of the user data and control signaling packets, e.g., voice data and call signaling packets, into separate logical channels may enable differentiated handling at the MAC and PHY layers. Further, additional overhead may be reduced at both the user data and control signaling packets, e.g., the voice data packet and the call signaling packets.

[0120] FIG. 9 shows an example of packet overhead associated with example signal flow 800 of FIG. 8. For example, tables 900-a and 900-b illustrate packet overhead associated with the signal flow 800, described with respect to FIG. 8. Table 900-a shows packet overhead associated with transmission of a user data packet, e.g., a voice data packet carried over first new SRB 855-d, Sl-AP bearer 855-b, and first NIDD bearer 855-c. Table 900-b shows packet overhead associated with transmission of a control signaling packet, e.g., a call signaling packet, carried over second new SRB 855- e, Sl-AP bearer 855-b, and new second NIDD bearer 855-f.

[0121] As described with respect to FIG. 8, transmitting control signaling packets on a dedicated SRB, such as the second new SRB 855-e, in accordance with the signal flow 800 of FIG. 8, may allow for the reduction of overhead associated with each control signaling packet relative to overhead associated with a control signaling packet encapsulated in a NAS message and transmitted via the SRB 655-a, in accordance with the signal flow 600 of FIG. 6.

[0122] In particular, NAS related overhead (e.g., NAS/L3 overhead) may be eliminated from the header of each control signalling packet when carried by the second new SRB 855-e, since the packets carried by the second new SRB 855-e may be directly mapped to the NIDD payload. For instance, the NAS user data container header and the NAS message header, shown in table 700-b of FIG. 7, may be eliminated (although in some cases, use of the NAS message for encapsulating such data or signaling or both in RRC signaling may remain for backwards compatibility purposes).

[0123] As a result, each control signaling packet, e.g., call signaling packet, carried over the second new SRB 855-e may have a smaller amount of overhead as compared to a control signaling packet encapsulated in a NAS message and carried over SRB 655-a, as described with respect to FIG. 6 and shown in table 700-b of FIG. 7. For instance, as shown in table 900-b, a call signaling packet carried over the second new SRB 855-e may have approximately 18 bytes of overhead. For example, as shown in table 900-b of FIG. 9, the overhead may include an II protocol header, an RDS header, L3 encapsulation with security protection, an optional RRC header indicating a length or size of the packet, an RLC AM header, and a MAC header. Furthermore, as a result of the end-to-end logical separation of the user data (e.g., voice data packets) and control signaling data (e.g., call signaling packets), overhead associated with a user data packet may also be reduced, such as by eliminating the RDS header. Thus, as shown in table 900-a of FIG. 9, the user data packet (e.g., voice data packet) carried over the first new SRB 855-d may have approximately 26-27 bits of overhead (approximately 22% of the overall packet size).

[0124] Accordingly, separately encapsulating the data and call signaling packets in dedicated SRBs, for end-to-end logical separation of the packet flow, may allow for the reduction in overhead in both data packets and call signaling packets in a manner that supports the low date rate requirements for calls in satellite network systems, such as satellite access network system 300 described with respect to FIG. 3.

[0125] FIG. 10 shows an example of a process flow 1000 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure.

[0126] In some examples, process flow 1000 may implement aspects of wireless communications system 100 or satellite access network systems 200 or 300, as described with reference to FIGs. 1, 2, and 3, respectively. Process flow 1000 may be implemented by a UE 1015, a base station 1040 (e.g., a satellite base station), and a core network 1030 (e.g., an MME of the core network 1030), and a gateway 1045 (e.g., a SCEF of the gateway 1045) as described herein. In the following description of the process flow 1000, the communications between the UE 1015, the base station 1040, the core network 1030, and the gateway 1045 may be transmitted in a different order than the example order shown, or the operations performed by the UE 1015, the base station 1040, the core network 1030, and the gateway 1045 may be performed in different orders or at different times. Some operations may also be omitted from the process flow 1000, and other operations may be added to the process flow 1000.

[0127] In some examples, the operations illustrated in process flow 1000 may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code (e.g., software or firmware) executed by a processor, or any combination thereof. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

[0128] At step 1002, the UE 1015 may send a request to the base station 1040 (e.g., a satellite base station) to connect to the core network 1030. In some cases, the UE 1015 may include, in the connection request, an indication to perform voice calls using CP CIoT optimization. For example, the connection request may be a request to establish a packet data session and the indication may be included in the request to establish the packet data session. In some cases, the packet data session request may be a PDN connection establishment request message for a PDN connection to the core network 1030, and the core network may be a 3 GPP 4G core network. In some cases, the packet data session request may further include an indication that the packet data session is for a Control Plane Only PDN connection. In some cases, the packet data session request may include an indication of an access point name (APN), such as an APN value that identifies an APN dedicated to servicing voice calls. In some cases, the request may further include an indication that the packet data session is for a voice service, for an emergency call service, or a combination thereof. [0129] At step 1004, the base station 1040 may forward the connection request, such as the packet data session request, to the core network 1030, such as to the MME of the core network 1030, and the MME may manage the connection and registration procedure.

[0130] At step 1006, in response to successful registration of the UE 1015 and based on the connection request, such as the packet data session request, including an indication to perform voice calls using CP CIoT optimization, the indication of the dedicated APN, the indication of the Control Plane Only PDN connection, the indication that the packet data session is for a voice or emergency service, or a combination thereof, the core network 1030 may determine configuration information for establishing one or more dedicated SRBs for separately carrying user data packets, e.g., voice data packets associated with voice calls, control signaling packets, e.g., call signaling packets associated with voice calls, or both. In some cases, the core network 1030 may determine the configuration information based on detecting an initiation of a satellite access voice call from the UE 1015. The configuration information may include first configuration information for configuring a first SRB dedicated to transmission of user data packets, e.g., voice data packets associated with voice calls. The configuration information may, additionally or alternatively, include second configuration information for configuring a second SRB dedicated to transmission of control signal packets, e.g., call signaling packets associated with voice calls.

[0131] At step 1008, based on the successful registration of the UE 1015 with the core network 1030, the core network 1030 may provide the base station 1040 with the configuration information associated with establishment of one or more dedicated SRBs.

[0132] At step 1010, the base station 1040 may transmit, to the UE 1015, the configuration information associated with the establishment of the one or more dedicated SRBs.

[0133] At step 1012, the UE 1015, the base station 1040, and the core network 1030 may coordinate the establishment of the one or more SRBs and the packet data session. For instance, the one or more SRBs may be configured and established, based on the configuration information, at one or more of the UE 1015, the base station 1040, and the core network 1030. For instance, based at least in part on the first configuration information, a first SRB dedicated to transmission of user data packets, e.g., voice data packets associated with voice calls, may be established. Additionally or alternatively, based at least in part on the second configuration information, a second SRB dedicated to transmission of control signaling packets, e.g., call signaling packets associated with voice calls, may be established. The UE 1015, the base station 1040, and the core network 1030 may further coordinate the establishment of the PDU session. For instance, the packet data session may be the Control Plane Only PDN connection. In some cases, the packet data session may be for a voice service, an emergency service, or a combination thereof. In some cases, the packet data session may be associated with an APN dedicated to servicing voice calls.

[0134] At step 1014, the UE 1015 may transmit one or more user data packets (e.g., voice data packets) to the core network 1030, via the base station 1040, and over the first SRB. In some cases, the user data packet may be encapsulated in a container and the container may be transmitted over the first SRB. The container may include a header comprising a length of the user data packet, a packet sequence number of the user data packet, and identification information of the SRB carrying the user data packet, which may provide an indication that the container encapsulates a user data packet (e.g., a voice data packet). In some cases, the header may include RDS header information, which may provide an indication that the container encapsulates a user data packet (e.g., a voice data packet). In some cases, the header may include additional or different information.

[0135] At step 1016, the UE 1015 may transmit one or more control signaling packets (e.g., call signaling packets) to the core network 1030, via the base station 1040, and over the second SRB. In some cases, the control signaling packet may be encapsulated in a container and the container may be transmitted over the second SRB. The container may include a header comprising a length of the control signaling packet, a packet sequence number of the control signaling packet, and identification information of the SRB carrying the control signaling packet, which may provide an indication that the container encapsulates a control signaling packet (e.g., a call signaling packet). In some cases, the header may include RDS header information, which may provide an indication that the container encapsulates a control signaling packet (e.g., a call signaling packet). In some cases, the header may include additional or different information.

[0136] At step 1018, the core network 1030 may receive the user data packets, via the first SRB, and extract and decipher the user data packets. For instance, the core network 1030 may receive a user data packet, e.g., a voice data packet associated with a voice call, encapsulated in a container transmitted over the first SRB. The core network 1030 may extract the user data packet from the container and decipher the user data packet using the packet sequence number in the header of the packet.

[0137] At step 1020, the core network 1030 may establish, based at least in part on the deciphered packet comprising the user data packet, a first NIDD bearer dedicated to transmission of user data packets, e.g., voice data packets, to the gateway 1045 (e.g., SCEF of the gateway 1045). In some cases, the core network 1030 may establish the first NIDD bearer at the time the first and second SRBs are established, such as at step 1012.

[0138] At step 1022, the core network 1030 may transmit the user data packets to the gateway 1045, via the first NIID bearer.

[0139] At step 1024, the core network 1030 may receive the control signaling packets, via the second SRB, and extract and decipher the control signaling packets. For instance, the core network 1030 may receive a control signaling packet, e.g., a call signaling packet associated with a voice call, encapsulated in a container transmitted over the second SRB. The core network 1030 may extract the control signaling packet from the container and decipher the control signaling packet using the packet sequence number in the header of the packet.

[0140] At step 1026, the core network 1030 may establish, based at least in part on the deciphered packet comprising the control signaling packet, a second NIDD bearer dedicated to transmission of control signaling packets, e.g., call signaling packets, to the gateway 1045 (e.g., SCEF of the gateway 1045). In some cases, the core network 1030 may establish the second NIDD bearer at the time the first and second SRBs are established, such as at step 1012.

[0141] At step 1028, the core network 1030 may transmit the control signaling packets to the gateway 1045 via the second NIID bearer.

[0142] FIG. 11 shows a block diagram 1100 of a device 1105 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of aspects of a UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105, or one or more components of the device 1105 (e.g., the receiver 1110, the transmitter 1115, the communications manager 1120), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0143] The receiver 1110 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for transmission of low data rate data using CP CIoT in satellite network systems). Information may be passed on to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

[0144] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for transmission of low data rate data using CP CIoT in satellite network systems). In some examples, the transmitter 1115 may be co-located with a receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas. [0145] The communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be examples of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

[0147] Additionally, or alternatively, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure). [0148] In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0149] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The communications manager 1120 is capable of, configured to, or operable to support a means for establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The communications manager 1120 is capable of, configured to, or operable to support a means for transmitting, via the first signaling radio bearer, a data packet.

[0150] By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 (e.g., at least one processor controlling or otherwise coupled with the receiver 1110, the transmitter 1115, the communications manager 1120, or a combination thereof) may support techniques for reduced overhead and processing, and more efficient utilization of communication resources.

[0151] FIG. 12 shows a block diagram 1200 of a device 1205 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of a device 1105 or a UE 115 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. The device 1205, or one of more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, the communications manager 1220), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0152] The receiver 1210 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for transmission of low data rate data using CP CIoT in satellite network systems). Information may be passed on to other components of the device 1205. The receiver 1210 may utilize a single antenna or a set of multiple antennas.

[0153] The transmitter 1215 may provide a means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for transmission of low data rate data using CP CIoT in satellite network systems). In some examples, the transmitter 1215 may be co-located with a receiver 1210 in a transceiver module. The transmitter 1215 may utilize a single antenna or a set of multiple antennas.

[0154] The device 1205, or various components thereof, may be an example of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1220 may include an SRB configuration manager 1225, an SRB manager 1230, a packet transmission manager 1235, or any combination thereof. The communications manager 1220 may be an example of aspects of a communications manager 1120 as described herein. In some examples, the communications manager 1220, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0155] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. The SRB configuration manager 1225 is capable of, configured to, or operable to support a means for receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The SRB manager 1230 is capable of, configured to, or operable to support a means for establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The packet transmission manager 1235 is capable of, configured to, or operable to support a means for transmitting, via the first signaling radio bearer, a data packet.

[0156] FIG. 13 shows a block diagram 1300 of a communications manager 1320 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The communications manager 1320 may be an example of aspects of a communications manager 1120, a communications manager 1220, or both, as described herein. The communications manager 1320, or various components thereof, may be an example of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1320 may include an SRB configuration manager 1325, an SRB manager 1330, a packet transmission manager 1335, a packet data session manager 1340, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0157] The communications manager 1320 may support wireless communications in accordance with examples as disclosed herein. The SRB configuration manager 1325 is capable of, configured to, or operable to support a means for receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The SRB manager 1330 is capable of, configured to, or operable to support a means for establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The packet transmission manager 1335 is capable of, configured to, or operable to support a means for transmitting, via the first signaling radio bearer, a data packet.

[0158] In some examples, the signaling radio bearer configuration includes an indication of a length of a container for encapsulating a data packet to be transmitted via the first signaling radio bearer.

[0159] In some examples, the network entity is a satellite radio access network.

[0160] In some examples, to support transmitting, via the first signaling radio bearer, the data packet, the packet transmission manager 1335 is capable of, configured to, or operable to support a means for encapsulating the data packet in a container that includes a header. In some examples, to support transmitting, via the first signaling radio bearer, the data packet, the packet transmission manager 1335 is capable of, configured to, or operable to support a means for transmitting, via the first signaling radio bearer, the data packet encapsulated in the container.

[0161] In some examples, the container includes a NAS message container of a Radio Resource Control (RRC) protocol.

[0162] In some examples, the header includes a length of the data packet encapsulated in the container, a sequence number of the data packet encapsulated in the container, an indication that the container encapsulates a voice data packet, or a combination thereof.

[0163] In some examples, the data packet includes a reliable data service (RDS) protocol header that is indicative that the container encapsulates a voice data packet.

[0164] In some examples, the data packet includes a voice data packet associated with a voice call. In some examples, the first signaling radio bearer is dedicated to transmission of voice data packets. [0165] In some examples, establishing the first signaling radio bearer is based on initiation of the voice call.

[0166] In some examples, the SRB manager 1330 is capable of, configured to, or operable to support a means for establishing a second signaling radio bearer dedicated to transmission of call signaling packets. In some examples, the packet transmission manager 1335 is capable of, configured to, or operable to support a means for transmitting, via the second signaling radio bearer, a call signaling packet associated with the voice call.

[0167] In some examples, the call signaling packet is in accordance with an IMS signaling protocol.

[0168] In some examples, to support transmitting, via the second signaling radio bearer, the call signaling packet, the packet transmission manager 1335 is capable of, configured to, or operable to support a means for encapsulating the call signaling packet in a container that includes a header. In some examples, to support transmitting, via the second signaling radio bearer, the call signaling packet, the packet transmission manager 1335 is capable of, configured to, or operable to support a means for transmitting, via the second signaling radio bearer, the call signaling packet encapsulated in the container.

[0169] In some examples, the container is a NAS message container of a Radio Resource Control (RRC) protocol.

[0170] In some examples, the header includes a length of the call signaling packet encapsulated in the container, a sequence number of the call signaling packet encapsulated in the container, an indication that the container encapsulates the call signaling packet, or a combination thereof.

[0171] In some examples, the call signaling packet includes an RDS protocol header that is indicative that the container encapsulates the call signaling packet.

[0172] In some examples, the packet data session manager 1340 is capable of, configured to, or operable to support a means for transmitting, to the network entity and based on initiation of a voice call, a request to establish a packet data session. In some examples, the packet data session manager 1340 is capable of, configured to, or operable to support a means for establishing the packet data session.

[0173] In some examples, the packet data session is a Packet Data Network (PDN) connection to a 3 GPP 4G core network.

[0174] In some examples, the request to establish the packet data session includes an indication that the packet data session is for a voice service or for an emergency call service.

[0175] In some examples, the request to establish the packet data session includes an APN value corresponding to a requested service.

[0176] In some examples, the request to establish the packet data session includes an indication that the packet data session is for a Control Plane Only PDN connection.

[0177] In some examples, receiving the signaling radio bearer configuration is based on the request to establish the packet data session.

[0178] FIG. 14 shows a diagram of a system 1400 including a device 1405 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of or include components of a device 1105, a device 1205, or a UE 115 as described herein. The device 1405 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 1405 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1420, an input/output (I/O) controller, such as an I/O controller 1410, a transceiver 1415, one or more antennas 1425, at least one memory 1430, code 1435, and at least one processor 1440. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1445).

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

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

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

[0182] The at least one processor 1440 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1440 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1440. The at least one processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting techniques for transmission of low data rate data using CP CIoT in satellite network systems). For example, the device 1405 or a component of the device 1405 may include at least one processor 1440 and at least one memory 1430 coupled with or to the at least one processor 1440, the at least one processor 1440 and the at least one memory 1430 configured to perform various functions described herein. In some examples, the at least one processor 1440 may include multiple processors and the at least one memory 1430 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1440 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1440) and memory circuitry (which may include the at least one memory 1430)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1440 or a processing system including the at least one processor 1440 may be configured to, configurable to, or operable to cause the device 1405 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1435 (e.g., processor-executable code) stored in the at least one memory 1430 or otherwise, to perform one or more of the functions described herein.

[0183] The communications manager 1420 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1420 is capable of, configured to, or operable to support a means for receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The communications manager 1420 is capable of, configured to, or operable to support a means for establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The communications manager 1420 is capable of, configured to, or operable to support a means for transmitting, via the first signaling radio bearer, a data packet.

[0184] By including or configuring the communications manager 1420 in accordance with examples as described herein, the device 1405 may support techniques for reduced overhead, resulting in reduced latency and power consumption, and more efficient utilization of communication resources.

[0185] In some examples, the communications manager 1420 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1415, the one or more antennas 1425, or any combination thereof. Although the communications manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1420 may be supported by or performed by the at least one processor 1440, the at least one memory 1430, the code 1435, or any combination thereof. For example, the code 1435 may include instructions executable by the at least one processor 1440 to cause the device 1405 to perform various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein, or the at least one processor 1440 and the at least one memory 1430 may be otherwise configured to, individually or collectively, perform or support such operations.

[0186] FIG. 15 shows a block diagram 1500 of a device 1505 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of aspects of a network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communications manager 1520. The device 1505, or one or more components of the device 1505 (e.g., the receiver 1510, the transmitter 1515, the communications manager 1520), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0189] The communications manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be examples of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

[0191] Additionally, or alternatively, the communications manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

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

[0193] The communications manager 1520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1520 is capable of, configured to, or operable to support a means for receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The communications manager 1520 is capable of, configured to, or operable to support a means for establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The communications manager 1520 is capable of, configured to, or operable to support a means for transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The communications manager 1520 is capable of, configured to, or operable to support a means for receiving, via the first signaling radio bearer, a data packet.

[0194] By including or configuring the communications manager 1520 in accordance with examples as described herein, the device 1505 (e.g., at least one processor controlling or otherwise coupled with the receiver 1510, the transmitter 1515, the communications manager 1520, or a combination thereof) may support techniques for reduced overhead and processing, and more efficient utilization of communication resources. [0195] FIG. 16 shows a block diagram 1600 of a device 1605 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of aspects of a device 1505 or a network entity 105 as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communications manager 1620. The device 1605, or one of more components of the device 1605 (e.g., the receiver 1610, the transmitter 1615, the communications manager 1620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0198] The device 1605, or various components thereof, may be an example of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1620 may include a packet data session manager 1625, an SRB manager 1630, an SRB configuration manager 1635, a packet reception manager 1640, or any combination thereof. The communications manager 1620 may be an example of aspects of a communications manager 1520 as described herein. In some examples, the communications manager 1620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1610, the transmitter 1615, or both. For example, the communications manager 1620 may receive information from the receiver 1610, send information to the transmitter 1615, or be integrated in combination with the receiver 1610, the transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0199] The communications manager 1620 may support wireless communications in accordance with examples as disclosed herein. The packet data session manager 1625 is capable of, configured to, or operable to support a means for receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The SRB manager 1630 is capable of, configured to, or operable to support a means for establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The SRB configuration manager 1635 is capable of, configured to, or operable to support a means for transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The packet reception manager 1640 is capable of, configured to, or operable to support a means for receiving, via the first signaling radio bearer, a data packet. [0200] FIG. 17 shows a block diagram 1700 of a communications manager 1720 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The communications manager 1720 may be an example of aspects of a communications manager 1520, a communications manager 1620, or both, as described herein. The communications manager 1720, or various components thereof, may be an example of means for performing various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein. For example, the communications manager 1720 may include a packet data session manager 1725, an SRB manager 1730, an SRB configuration manager 1735, a packet reception manager 1740, a packet extraction manager 1745, a packet deciphering manager 1750, a NIDD bearer manager 1755, a packet transmission manager 1760, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0201] The communications manager 1720 may support wireless communications in accordance with examples as disclosed herein. The packet data session manager 1725 is capable of, configured to, or operable to support a means for receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The SRB manager 1730 is capable of, configured to, or operable to support a means for establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The SRB configuration manager 1735 is capable of, configured to, or operable to support a means for transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The packet reception manager 1740 is capable of, configured to, or operable to support a means for receiving, via the first signaling radio bearer, a data packet.

[0202] In some examples, the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets.

[0203] In some examples, the signaling radio bearer configuration includes an indication of a length of a container for encapsulating a data packet to be transmitted by the UE via the first signaling radio bearer.

[0204] In some examples, the network entity is a satellite radio access network.

[0205] In some examples, the data packet includes a voice data packet associated with a voice call. In some examples, the first signaling radio bearer is dedicated to transmission of voice data packets.

[0206] In some examples, establishing the first signaling radio bearer is further based on receiving, from the UE, a request to establish the voice call via a satellite access connection.

[0207] In some examples, the SRB manager 1730 is capable of, configured to, or operable to support a means for establishing a second signaling radio bearer dedicated to transmission of call signaling packets. In some examples, the packet reception manager 1740 is capable of, configured to, or operable to support a means for receiving, via the second signaling radio bearer, a call signaling packet associated with the voice call.

[0208] In some examples, the call signaling packet is in accordance with an IMS signaling protocol.

[0209] In some examples, the packet reception manager 1740 is capable of, configured to, or operable to support a means for receiving, from the UE and via the first signaling radio bearer or the second signaling radio bearer, a container encapsulating a packet. In some examples, the packet extraction manager 1745 is capable of, configured to, or operable to support a means for extracting, from the container, the packet. [0210] In some examples, the container includes a header including an indication of a packet type, a packet sequence number, a packet length, or a combination thereof.

[0211] In some examples, the container is a NAS message container of a Radio Resource Control (RRC) protocol.

[0212] In some examples, the data packet includes a reliable data service (RDS) protocol header that is indicative of a type of packet encapsulated by the container.

[0213] In some examples, the packet deciphering manager 1750 is capable of, configured to, or operable to support a means for deciphering the packet using the packet sequence number.

[0214] In some examples, the NIDD bearer manager 1755 is capable of, configured to, or operable to support a means for establishing, based on the deciphered packet including data, a first NIDD bearer dedicated to transmission of data packets to an SCEF. In some examples, the packet transmission manager 1760 is capable of, configured to, or operable to support a means for transmitting, to the SCEF and via the first NIDD bearer, the deciphered packet.

[0215] In some examples, the data is voice data.

[0216] In some examples, the NIDD bearer manager 1755 is capable of, configured to, or operable to support a means for establishing, based on the deciphered packet including a call signaling, a second NIDD bearer dedicated to transmission of call signaling packets to an SCEF. In some examples, the packet transmission manager 1760 is capable of, configured to, or operable to support a means for transmitting, to the SCEF and via the second NIDD bearer, the deciphered packet.

[0217] In some examples, the network entity is a mobility management entity.

[0218] In some examples, the packet data session manager 1725 is capable of, configured to, or operable to support a means for establishing the packet data session, where the packet data session is a PDN connection to a 3GPP 4G core network.

[0219] In some examples, the request to establish the packet data session further includes an indication that the packet data session is for a voice service or for an emergency call service. [0220] In some examples, the request to establish the packet data session includes an APN value corresponding to a requested service.

[0221] FIG. 18 shows a diagram of a system 1800 including a device 1805 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The device 1805 may be an example of or include components of a device 1505, a device 1605, or a network entity 105 as described herein. The device 1805 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1805 may include components that support outputting and obtaining communications, such as a communications manager 1820, a transceiver 1810, one or more antennas 1815, at least one memory 1825, code 1830, and at least one processor 1835. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1840).

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

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

[0224] The at least one processor 1835 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1835 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1835. The at least one processor 1835 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1825) to cause the device 1805 to perform various functions (e.g., functions or tasks supporting techniques for transmission of low data rate data using CP CIoT in satellite network systems). For example, the device 1805 or a component of the device 1805 may include at least one processor 1835 and at least one memory 1825 coupled with one or more of the at least one processor 1835, the at least one processor 1835 and the at least one memory 1825 configured to perform various functions described herein. The at least one processor 1835 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1830) to perform the functions of the device 1805. The at least one processor 1835 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1805 (such as within one or more of the at least one memory 1825). In some examples, the at least one processor 1835 may include multiple processors and the at least one memory 1825 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1835 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1835) and memory circuitry (which may include the at least one memory 1825)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1835 or a processing system including the at least one processor 1835 may be configured to, configurable to, or operable to cause the device 1805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1825 or otherwise, to perform one or more of the functions described herein.

[0225] In some examples, a bus 1840 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1840 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1805, or between different components of the device 1805 that may be co-located or located in different locations (e.g., where the device 1805 may refer to a system in which one or more of the communications manager 1820, the transceiver 1810, the at least one memory 1825, the code 1830, and the at least one processor 1835 may be located in one of the different components or divided between different components).

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

[0227] The communications manager 1820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1820 is capable of, configured to, or operable to support a means for receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The communications manager 1820 is capable of, configured to, or operable to support a means for establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The communications manager 1820 is capable of, configured to, or operable to support a means for transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The communications manager 1820 is capable of, configured to, or operable to support a means for receiving, via the first signaling radio bearer, a data packet.

[0228] By including or configuring the communications manager 1820 in accordance with examples as described herein, the device 1805 may support techniques for reduced overhead, resulting in reduced latency and reduced power consumption, and more efficient utilization of communication resources.

[0229] In some examples, the communications manager 1820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1810, the one or more antennas 1815 (e.g., where applicable), or any combination thereof. Although the communications manager 1820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1820 may be supported by or performed by the transceiver 1810, one or more of the at least one processor 1835, one or more of the at least one memory 1825, the code 1830, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1835, the at least one memory 1825, the code 1830, or any combination thereof). For example, the code 1830 may include instructions executable by one or more of the at least one processor 1835 to cause the device 1805 to perform various aspects of techniques for transmission of low data rate data using CP CIoT in satellite network systems as described herein, or the at least one processor 1835 and the at least one memory 1825 may be otherwise configured to, individually or collectively, perform or support such operations. [0230] FIG. 19 shows a flowchart illustrating a method 1900 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or its components as described herein. For example, the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0231] At 1905, the method may include receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by an SRB configuration manager 1325 as described with reference to FIG. 13.

[0232] At 1910, the method may include establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by an SRB manager 1330 as described with reference to FIG. 13.

[0233] At 1915, the method may include transmitting, via the first signaling radio bearer, a data packet. The operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a packet transmission manager 1335 as described with reference to FIG. 13.

[0234] FIG. 20 shows a flowchart illustrating a method 2000 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a UE or its components as described herein. For example, the operations of the method 2000 may be performed by a UE 115 as described with reference to FIGs. 1 through 14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0235] At 2005, the method may include receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity. The operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by an SRB configuration manager 1325 as described with reference to FIG. 13.

[0236] At 2010, the method may include establishing, based on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by an SRB manager 1330 as described with reference to FIG. 13.

[0237] At 2015, the method may include transmitting, via the first signaling radio bearer, a data packet. The operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a packet transmission manager 1335 as described with reference to FIG. 13.

[0238] At 2020, the method may include establishing a second signaling radio bearer dedicated to transmission of call signaling packets. The operations of 2020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed by an SRB manager 1330 as described with reference to FIG. 13.

[0239] At 2025, the method may include transmitting, via the second signaling radio bearer, a call signaling packet associated with the voice call. The operations of 2025 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2025 may be performed by a packet transmission manager 1335 as described with reference to FIG. 13.

[0240] FIG. 21 shows a flowchart illustrating a method 2100 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2100 may be performed by a network entity as described with reference to FIGs. 1 through 10 and 15 through 18. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0241] At 2105, the method may include receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The operations of 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a packet data session manager 1725 as described with reference to FIG. 17.

[0242] At 2110, the method may include establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The operations of 2110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed by an SRB manager 1730 as described with reference to FIG. 17.

[0243] At 2115, the method may include transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by an SRB configuration manager 1735 as described with reference to FIG. 17. [0244] At 2120, the method may include receiving, via the first signaling radio bearer, a data packet. The operations of 2120 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed by a packet reception manager 1740 as described with reference to FIG. 17.

[0245] FIG. 22 shows a flowchart illustrating a method 2200 that supports techniques for transmission of low data rate data using CP CIoT in satellite network systems in accordance with one or more aspects of the present disclosure. The operations of the method 2200 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2200 may be performed by a network entity as described with reference to FIGs. 1 through 10 and 15 through 18. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0246] At 2205, the method may include receiving, from a UE, a request to establish a packet data session, where the request includes an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection. The operations of 2205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a packet data session manager 1725 as described with reference to FIG. 17.

[0247] At 2210, the method may include establishing, based on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets. The operations of 2210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed by an SRB manager 1730 as described with reference to FIG. 17.

[0248] At 2215, the method may include transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, where the signaling radio bearer configuration includes an indication that the first signaling radio bearer is dedicated to transmission of data packets. The operations of 2215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed by an SRB configuration manager 1735 as described with reference to FIG. 17.

[0249] At 2220, the method may include receiving, via the first signaling radio bearer, a data packet. The operations of 2220 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed by a packet reception manager 1740 as described with reference to FIG. 17.

[0250] At 2225, the method may include establishing a second signaling radio bearer dedicated to transmission of call signaling packets. The operations of 2225 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2225 may be performed by an SRB manager 1730 as described with reference to FIG. 17.

[0251] At 2230, the method may include receiving, via the second signaling radio bearer, a call signaling packet associated with the voice call. The operations of 2230 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2230 may be performed by a packet reception manager 1740 as described with reference to FIG. 17.

[0252] The following provides an overview of aspects of the present disclosure:

[0253] Aspect 1 : A method for wireless communications by a UE, comprising: receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity; establishing, based at least in part on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity; and transmitting, via the first signaling radio bearer, a data packet.

[0254] Aspect 2: The method of aspect 1, wherein the network entity is a satellite radio access network. [0255] Aspect 3 : The method of any of aspects 1 through 2, wherein transmitting, via the first signaling radio bearer, the data packet comprises: encapsulating the data packet in a container that includes a header; and transmitting, via the first signaling radio bearer, the data packet encapsulated in the container.

[0256] Aspect 4: The method of any of aspects 1 through 3, wherein the data packet comprises a voice data packet associated with a voice call, and the first signaling radio bearer is dedicated to transmission of voice data packets.

[0257] Aspect 5: The method of aspect 4, wherein establishing the first signaling radio bearer is based at least in part on initiation of the voice call.

[0258] Aspect 6: The method of any of aspects 4 through 5, further comprising: establishing a second signaling radio bearer dedicated to transmission of call signaling packets; and transmitting, via the second signaling radio bearer, a call signaling packet associated with the voice call.

[0259] Aspect 7: The method of aspect 6, wherein transmitting, via the second signaling radio bearer, the call signaling packet comprises: encapsulating the call signaling packet in a container that includes a header; and transmitting, via the second signaling radio bearer, the call signaling packet encapsulated in the container.

[0260] Aspect 8: The method of any of aspects 1 through 7, further comprising: transmitting, to the network entity and based at least in part on initiation of a voice call, a request to establish a packet data session; and establishing the packet data session.

[0261] Aspect 9: The method of aspect 8, wherein the packet data session is a Packet Data Network (PDN) connection to a Third Generation Partnership Project (3 GPP) Fourth Generation (4G) core network.

[0262] Aspect 10: The method of any of aspects 8 through 9, wherein the request to establish the packet data session comprises an indication that the packet data session is for a voice service or for an emergency call service.

[0263] Aspect 11 : The method of any of aspects 8 through 10, wherein the request to establish the packet data session comprises an indication that the packet data session is for a Control Plane Only PDN connection. [0264] Aspect 12: The method of any of aspects 8 through 11, wherein receiving the signaling radio bearer configuration is based at least in part on the request to establish the packet data session.

[0265] Aspect 13 : A method for wireless communications by a network entity, comprising: receiving, from a UE, a request to establish a packet data session, wherein the request comprises an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection ; establishing, based at least in part on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets; transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets; and receiving, via the first signaling radio bearer, a data packet.

[0266] Aspect 14: The method of aspect 13, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets.

[0267] Aspect 15: The method of any of aspects 13 through 14, wherein the network entity is a satellite radio access network.

[0268] Aspect 16: The method of any of aspects 13 through 15, wherein the data packet comprises a voice data packet associated with a voice call, and the first signaling radio bearer is dedicated to transmission of voice data packets.

[0269] Aspect 17: The method of aspect 16, wherein establishing the first signaling radio bearer is further based at least in part on receiving, from the UE, a request to establish the voice call via a satellite access connection.

[0270] Aspect 18: The method of any of aspects 16 through 17, further comprising: establishing a second signaling radio bearer dedicated to transmission of call signaling packets; and receiving, via the second signaling radio bearer, a call signaling packet associated with the voice call. [0271] Aspect 19: The method of aspect 18, further comprising: receiving, from the UE and via the first signaling radio bearer or the second signaling radio bearer, a container encapsulating a packet; and extracting, from the container, the packet.

[0272] Aspect 20: The method of aspect 19, further comprising: deciphering the packet using a packet sequence number indicated in a header of the container; establishing, based at least in part on the deciphered packet comprising data, a first NonIP Data Delivery (NIDD) bearer dedicated to transmission of data packets to a Service Capability Exposure Function (SCEF); and transmitting, to the SCEF and via the first NIDD bearer, the deciphered packet.

[0273] Aspect 21 : The method of aspect 20, wherein the data is voice date

[0274] Aspect 22: The method of any of aspects 19 through 21, further comprising: deciphering the packet using a packet sequence number indicated in a header of the container; establishing, based at least in part on the deciphered packet comprising a call signaling, a second Non-IP Data Delivery (NIDD) bearer dedicated to transmission of call signaling packets to a Service Capability Exposure Function (SCEF); and transmitting, to the SCEF and via the second NIDD bearer, the deciphered packet.

[0275] Aspect 23: The method of any of aspects 13 through 22, further comprising: establishing the packet data session, wherein the packet data session is a PDN connection to a Third Generation Partnership Project (3 GPP) Fourth Generation (4G) core network.

[0276] Aspect 24: The method of any of aspects 13 through 23, wherein the request to establish the packet data session further comprises an indication that the packet data session is for a voice service or for an emergency call service.

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

[0278] Aspect 26: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 12. [0279] Aspect 27: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 12.

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

[0281] Aspect 29: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 13 through 24.

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

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

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

[0285] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [0286] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

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

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

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

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

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

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

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

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

Claims

CLAIMS What is claimed is:

1. A method for wireless communications by a user equipment (UE), comprising: receiving, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity; establishing, based at least in part on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity; and transmitting, via the first signaling radio bearer, a data packet.

2. The method of claim 1, wherein the network entity is a satellite radio access network.

3. The method of claim 1, wherein transmitting, via the first signaling radio bearer, the data packet comprises: encapsulating the data packet in a container that includes a header; and transmitting, via the first signaling radio bearer, the data packet encapsulated in the container.

4. The method of claim 1, wherein the data packet comprises a voice data packet associated with a voice call, and wherein the first signaling radio bearer is dedicated to transmission of voice data packets.

5. The method of claim 4, wherein establishing the first signaling radio bearer is based at least in part on initiation of the voice call.

6. The method of claim 4, further comprising: establishing a second signaling radio bearer dedicated to transmission of call signaling packets; and transmitting, via the second signaling radio bearer, a call signaling packet associated with the voice call.

7. The method of claim 6, wherein transmitting, via the second signaling radio bearer, the call signaling packet comprises: encapsulating the call signaling packet in a container that includes a header; and transmitting, via the second signaling radio bearer, the call signaling packet encapsulated in the container.

8. The method of claim 1, further comprising: transmitting, to the network entity and based at least in part on initiation of a voice call, a request to establish a packet data session; and establishing the packet data session.

9. The method of claim 8, wherein the packet data session is a Packet Data Network (PDN) connection to a Third Generation Partnership Project (3 GPP) Fourth Generation (4G) core network.

10. The method of claim 8, wherein the request to establish the packet data session comprises an indication that the packet data session is for a voice service or for an emergency call service.

11. The method of claim 8, wherein the request to establish the packet data session comprises an indication that the packet data session is for a Control Plane Only PDN connection.

12. The method of claim 8, wherein receiving the signaling radio bearer configuration is based at least in part on the request to establish the packet data session.

13. A method for wireless communications by a network entity, comprising: receiving, from a user equipment (UE), a request to establish a packet data session, wherein the request comprises an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection; establishing, based at least in part on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets; transmitting, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets; and receiving, via the first signaling radio bearer, a data packet.

14. The method of claim 13, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets.

15. The method of claim 13, wherein the network entity is a satellite radio access network.

16. The method of claim 13, wherein the data packet comprises a voice data packet associated with a voice call, and wherein the first signaling radio bearer is dedicated to transmission of voice data packets.

17. The method of claim 16, wherein establishing the first signaling radio bearer is further based at least in part on receiving, from the UE, a request to establish the voice call via a satellite access connection.

18. The method of claim 16, further comprising: establishing a second signaling radio bearer dedicated to transmission of call signaling packets; and receiving, via the second signaling radio bearer, a call signaling packet associated with the voice call.

19. The method of claim 18, further comprising: receiving, from the UE and via the first signaling radio bearer or the second signaling radio bearer, a container encapsulating a packet; and extracting, from the container, the packet.

20. The method of claim 19, further comprising: deciphering the packet using a packet sequence number indicated in a header of the container; establishing, based at least in part on the deciphered packet comprising data, a first Non-IP Data Delivery (NIDD) bearer dedicated to transmission of data packets to a Service Capability Exposure Function (SCEF); and transmitting, to the SCEF and via the first NIDD bearer, the deciphered packet.

21. The method of claim 20, wherein the data is voice data.

22. The method of claim 19, further comprising: deciphering the packet using a packet sequence number indicated in a header of the container; establishing, based at least in part on the deciphered packet comprising a call signaling, a second Non-IP Data Delivery (NIDD) bearer dedicated to transmission of call signaling packets to a Service Capability Exposure Function (SCEF); and transmitting, to the SCEF and via the second NIDD bearer, the deciphered packet.

23. The method of claim 13, further comprising: establishing the packet data session, wherein the packet data session is a PDN connection to a Third Generation Partnership Project (3GPP) Fourth Generation (4G) core network.

24. The method of claim 13, wherein the request to establish the packet data session further comprises an indication that the packet data session is for a voice service or for an emergency call service.

25. An apparatus for wireless communications at a user equipment (UE), comprising: one or more processors; and instructions stored in one or more memories and executable by the one or more processors, individually or collectively, to cause the apparatus to: receive, from a network entity, a signaling radio bearer configuration for a first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets to the network entity; establish, based at least in part on the signaling radio bearer configuration, the first signaling radio bearer dedicated to transmission of data packets to the network entity; and transmit, via the first signaling radio bearer, a data packet.

26. The UE of claim 25, wherein, to transmit the data packet, the instructions are executable by the one or more processors, individually or collectively, to cause the apparatus to: encapsulate the data packet in a container that includes a header; and transmit, via the first signaling radio bearer, the data packet encapsulated in the container, wherein the data packet comprises a voice data packet associated with a voice call, and wherein the first signaling radio bearer is dedicated to transmission of voice data packets.

27. The UE of claim 25, wherein the first signaling radio bearer is dedicated to transmission of voice data packets associated with a voice call, and wherein the instructions are executable by the one or more processors, individually or collectively, to further cause the apparatus to: establish a second signaling radio bearer dedicated to transmission of call signaling packets; encapsulate a call signaling packet associated with the voice call in a container that includes a header; and transmit, via the second signaling radio bearer, the call signaling packet encapsulated in the container.

28. An apparatus for wireless communications at a network entity, comprising: one or more processors; and instructions stored in one or more memories and executable by the one or more processors, individually or collectively, to cause the apparatus to: receive, from a user equipment (UE), a request to establish a packet data session, wherein the request comprises an indication that the packet data session is for a Control Plane Only Packet Data Network (PDN) connection; establish, based at least in part on the request to establish the packet data session, a first signaling radio bearer dedicated to transmission of data packets; transmit, to the UE, a signaling radio bearer configuration for the first signaling radio bearer, wherein the signaling radio bearer configuration comprises an indication that the first signaling radio bearer is dedicated to transmission of data packets; and receive, via the first signaling radio bearer, a data packet.

29. The network entity of claim 28, wherein the first signaling radio bearer is dedicated to transmission of voice data packets associated with a voice call, and wherein the instructions are further executable by the one or more processors, individually or collectively, to cause the apparatus to: establish a second signaling radio bearer dedicated to transmission of call signaling packets; and receive, via the second signaling radio bearer, a call signaling packet associated with the voice call.

30. The network entity of claim 29, wherein, to receive the data packet or the call signaling packet, the instructions are executable by the one or more processors, individually or collectively, to cause the apparatus to receive a container encapsulating a packet comprising the data packet or the call signaling packet, and wherein the instructions are further executable by the one or more processors, individually or collectively, to cause the apparatus to: extract, from the container, the packet, wherein the container includes a header, and wherein the header comprises an indication of a packet sequence number; decipher the packet using the packet sequence number; establish, based at least in part on the deciphered packet comprising data, a first Non-IP Data Delivery (NIDD) bearer dedicated to transmission of data packets to a Service Capability Exposure Function (SCEF); transmit, to the SCEF and via the first NIDD bearer, the deciphered packet comprising the data; establish, based at least in part on the deciphered packet comprising a call signaling packet, a second NIDD bearer dedicated to transmission of call signaling packets to the SCEF; and transmit, to the SCEF and via the second NIDD bearer, the deciphered packet comprising the call signaling packet.