Methods and apparatus for maintaining a packet data network connection in mobile communications
By establishing a PDN connection with separate IP and non-IP bearers for IMS signaling and voice traffic, the challenges of slow data rates in satellite-based IMS calls are addressed, enhancing voice quality and reducing protocol overhead.
Patent Information
- Application Number
- PCT/CN2026/095339
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Current network architectures experience slow data rates and transmission delays during Internet Protocol (IP) multimedia subsystem (IMS) voice calls over Narrow Band Internet of Things (NB-IoT) and Non-Terrestrial Network (NTN) via geostationary earth orbit (GEO) satellite, leading to poor user experience.
Implementing a PDN connection with both IP and non-IP EPS bearers, where IMS signaling traffic is transmitted over an IP-type default bearer and voice media is sent as non-IP traffic over a dedicated bearer, reducing protocol overhead and enhancing voice quality in satellite access scenarios.
This approach minimizes header overhead and optimizes bandwidth, ensuring seamless integration with existing IMS control procedures and improving voice service quality in limited bandwidth environments.
Smart Images

Figure CN2026095339_12112026_PF_FP_ABST
Abstract
Description
METHODS AND APPARATUS FOR MAINTAINING A PACKET DATA NETWORK CONNECTION IN MOBILE COMMUNICATIONSCROSS REFERENCE TO RELATED PATENT APPLICATION (S)
[0001] The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63 / 801,910, filed 08 May 2025, the content of which herein being incorporated by reference in its entirety.TECHNICAL FIELD
[0002] The present disclosure is generally related to mobile communications and, more particularly, to maintaining an Internet Protocol (IP) multimedia subsystem (IMS) packet data network (PDN) connection with both Internet Protocol (IP) evolved packet system (EPS) bearer and non-IP EPS bearer with respect to apparatus in mobile communications.BACKGROUND
[0003] Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.
[0004] For current network implementations, the data rate of Internet Protocol (IP) multimedia subsystem (IMS) voice calls over Narrow Band Internet of Things (NB-IoT) , Non-Terrestrial Network (NTN) , or NB-IoT NTN via geostationary earth orbit (GEO) satellite is very slow. It may cause delays in transmission or interruptions during the IMS voice calls. Existing network architectures cannot resolve these issues, leading to a poor user experience.
[0005] Accordingly, designing proper user equipment (UE) and network (NW) operations to improve voice service via satellite access has become an important issue for newly developed wireless communication systems. Therefore, there is a need to provide proper schemes to address this issue.SUMMARY
[0006] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
[0007] One objective of the present disclosure is to propose schemes, concepts, designs, systems, methods, and apparatus pertaining to maintaining an IMS PDN connection with both IP type traffic and non-IP type traffic. It is believed that the above-described issues would be avoided or alleviated by implementing one or more of the proposed schemes described herein.
[0008] In one aspect, a method may involve an apparatus maintaining a PDN connection with a network. The method may also involve the apparatus transmitting or receiving IP type traffic and non-IP type traffic over the PDN connection.
[0009] In one aspect, a method may involve a network apparatus maintaining a PDN connection with a user equipment, wherein a default bearer and a dedicated bearer may be associated with the PDN connection. The method may also involve the network apparatus transmitting or receiving IP type traffic and non-IP type traffic over the PDN connection.
[0010] In one aspect, a method may involve an apparatus establishing a PDN connection with a network. The method may also involve the apparatus indicating support for transporting IMS voice / media traffic using non-IP type traffic / packets over a dedicated bearer of the PDN connection in an uplink (UL) non-access stratum (NAS) message.
[0011] In one aspect, a method may involve a network apparatus maintaining a PDN connection with a user equipment. The method may also involve the network apparatus indicating whether to transmit or receive non-IP type traffic / packets over a dedicated bearer of the PDN connection in a downlink (DL) NAS message.
[0012] In one aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising maintaining a PDN connection with the network. The processor may also perform operations comprising transmitting or receiving, via the transceiver, IP type traffic and non-IP type traffic over the PDN connection.
[0013] In one aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a UE. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising maintaining a PDN connection with the UE. The processor may also perform operations comprising transmitting or receiving, via the transceiver, IP type traffic and non-IP type traffic over the PDN connection.
[0014] In one aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a network. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising establishing a PDN connection with the network. The processor may also perform operations comprising indicating a support of transporting voice traffic using non-IP type traffic over a dedicated bearer of the PDN connection in an uplink (UL) NAS message.
[0015] In one aspect, an apparatus may comprise a transceiver which, during operation, wirelessly communicates with a UE. The apparatus may also comprise a processor communicatively coupled to the transceiver. The processor, during operation, may perform operations comprising maintaining a PDN connection with the UE. The processor may also perform operations comprising indicating whether to transmit or receive non-IP type traffic over a dedicated bearer of the PDN connection in a DL NAS message.
[0016] It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G) , New Radio (NR) , IoT, and NB-IoT, NTN, GEO satellite, Medium Earth Orbit (MEO) satellite, Low Earth Orbit (LEO) satellite, IMS, Industrial Internet of Things (IIoT) , beyond 5G (B5G) , and 6th Generation (6G) , the proposed concepts, schemes and any variation (s) / derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies. Thus, the scope of the present disclosure is not limited to the examples described herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.
[0018] FIG. 1 is a diagram depicting example scenarios under schemes in accordance with implementations of the present disclosure.
[0019] FIG. 2A is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0020] FIG. 2B is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0021] FIG. 3A is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0022] FIG. 3B is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0023] FIG. 4A is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0024] FIG. 4B is a diagram depicting an example scenario under schemes in accordance with implementations of the present disclosure.
[0025] FIG. 5 is a block diagram of an example communication system in accordance with an implementation of the present disclosure.
[0026] FIG. 6 is a flowchart of an example process in accordance with an implementation of the present disclosure.
[0027] FIG. 7 is a flowchart of another example process in accordance with an implementation of the present disclosure.
[0028] FIG. 8 is a flowchart of an example process in accordance with an implementation of the present disclosure.
[0029] FIG. 9 is a flowchart of another example process in accordance with an implementation of the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
[0030] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview
[0031] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes, and / or solutions pertaining to maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
[0032] The present disclosure aims to maintain an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access.
[0033] FIG. 1 illustrates an example scenario 100 of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented. Scenario 100 involves user equipment (UE) 110 in wireless communication with a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, an IMS network, an NTN network, and / or a 6G network) consisting of an access network 120, a core network 130, and a satellite 140. The UE 110 may support IMS voice calls over NB-IoT, NTN, or NB-IoT NTN (NB NTN) via satellite 140 (i.e., earth-orbit satellite access) to connect to the core network 130. UE 110 may be a smartphone, a wearable device, an IoT device, an NB-IoT device, an NTN device, or a tablet, etc. Alternatively, the UE 110 may be a notebook (NB) or personal computer (PC) inserted or installed with a data card which includes a modem and radio-frequency (RF) transceiver (s) to provide wireless communication functionality. The access network 120 may be a 3GPP network (e.g., a public land mobile network (PLMN) , a stand-alone non-public network (SNPN) , an evolved packet core (EPC) network, a 5G network, or a 6G network) . The core network 130 may comprise one or more of an IP multimedia (IM) core network (CN) subsystem, an EPC network, a 5G core network (5GC) , or a 6G core network (6GC) . The satellite 140 may be a GEO satellite, a medium earth orbit (MEO) satellite, or a low earth orbit (LEO) satellite. In one embodiment, the access network 120 is connected to the core network 130 by means of the NG interface, more specifically to a user plane function (UPF) by means of the NG user-plane part (NG-u) , and to an access and mobility management function (AMF) by means of the NG control-plane part (NG-c) ; however, the present disclosure is not limited thereto. The access network 120 may include a base station 121. The base station may be called a BS, a cell, a small cell, or a macro-cell. In addition, the core network 130 may include other entities, such as a satellite network operator (SNO) , a network management system (NMS) , a mobility management entity (MME) , an equipment identity register (EIR) , a permanent equipment identifier (PEI) , a centralized database (e.g., home subscriber server (HSS) , or unified data management (UDM) ) , a policy and charging rules function (PCRF) , a proxy-call session control function (P-CSCF) , a proxy call session control function (P-SCF) , a serving-call session control function (S-CSCF) , a session management function (SMF) , etc. In one embodiment, the UE may access or be connected to the access network 120 via satellite 140, which connects to the core network 130. In one embodiment, the UE110 may access or be connected to the network over the NTN, connecting to the core network 130. In one embodiment, the UE 110 may access or be connected to the access network 120 over an NB-IoT connecting to the core network 130. In one embodiment, the UE 110 may subscribe to a voice call service over NB-IoT NTN (NB NTN) via the access of satellite 140 (i.e., the earth-orbit satellite access) to the core network 130. In one embodiment, the UE 110 may subscribe to the voice call service via satellite 140. In one embodiment, the UE 110 may subscribe to the voice call service over the NB-IoT. In one embodiment, UE 110 may subscribe to the voice call service over the NTN. For illustrative purposes, one base station (base station 121) and one UE (UE 110) may be described hereinafter. However, it is not intended to limit the network scenarios of the present disclosure.
[0034] FIG. 2A is a diagram depicting an example scenario 200a under schemes in accordance with implementations of the present disclosure. The voice over LTE (VoLTE) UE attachment and IMS registration message sequence are shown in FIG. 2A for illustration purposes. After the VoLTE UE completes the LTE attach process and bearer provisioning through RRC Connection Request, Attach Request, and the subsequent signaling between eNB, MME, serving gateway (SGW) , and packet gateway (PGW) , a “Default Bearer Established for IMS Signaling” is created. This default bearer is set up after E-RAB Setup, EPS Session Activate Default Bearer Accept, and Modify Bearer Requests, ensuring the UE has an IP address and network resources specifically for IMS signaling. Once the default bearer is established for IMS signaling, the VoLTE UE can begin “IMS Signaling over IP, ” starting with IMS “SIP Register” messages, as shown in the FIG. 2A. This enables the UE to proceed with IMS Registration and access VoLTE services.
[0035] FIG. 2B is a diagram depicting an example scenario 200b under schemes in accordance with implementations of the present disclosure. Basic VoLTE UE to VoLTE UE voice call establishment (originating side message sequence) is shown in FIG. 2B for illustration purposes. After the necessary SIP signaling messages are exchanged between the VoLTE UE and the IMS core network, the network initiates the setup of a Dedicated (EPS) Bearer. The Dedicated (EPS) Bearer is established through signaling interactions such as E-RAB Setup and Create Bearer Request / Response. Upon successful activation of the Dedicated Bearer, VoLTE voice traffic is transmitted between the two VoLTE UEs using this bearer.
[0036] In the present disclosure, various solutions for transmitting or receiving Internet Protocol (IP) type traffic / packets and non-IP type traffic / packets over a (single) PDN connection between the UE and the network are disclosed. In some embodiments, the network may provide a service to the UE via satellite access. In one example, the service may be provided over narrowband Internet of Things (NB-IoT) radio access technology (RAT) . In one example, a satellite may be GEO. In one example, satellite access may connect to an EPC, a 5GC, or a 6GC. In some embodiments, the PDN connection may be associated with or established for an IMS service, and an access point name (APN or DNN) for the PDN connection may be IMS. In some embodiments, an IMS PDN connection may be associated with one "non-IP type traffic" dedicated EPS bearer and one "IP type traffic" default EPS bearer. In some embodiments, the IP type traffic may include data, a packet, or traffic with an IP header. In some embodiments, the non-IP type traffic may include data, a packet, or traffic without an IP header. In some embodiments, the non-IP type traffic may include data, a packet, or traffic without a user datagram protocol (UDP) header. In some embodiments, the non-IP type traffic may include data, a packet, or traffic with a partial, reduced, minimal, or compressed real-time transport protocol (RTP) header.
[0037] In some embodiments, the PDN connection may include a first bearer and a second bearer, and the IP type traffic / packets and the non-IP type traffic / packets may be transmitted or received over the first bearer and the second bearer, respectively. In some embodiments, the first bearer may be the default bearer, and the IP type traffic / packets may be transmitted or received over the default bearer of the PDN connection. In some embodiments, the second bearer may be the dedicated bearer, and the non-IP type traffic / packets may be transmitted or received over a dedicated bearer of the PDN connection. In one embodiment, IMS voice traffic / packets may be transmitted or received as non-IP traffic / packets over a "non-IP type" dedicated EPS bearer of a PDN connection to reduce the header overhead to the most extreme level, and IMS signaling (e.g., SIP INVITE, etc. ) may be transmitted over an "IP type traffic" default EPS bearer of the PDN connection at the same time to reduce the impact to the IMS control plane (since the IMS network is designed based on "IP" ) . In some embodiments, the IP type traffic / packets transmitted or received over the default bearer of the PDN connection may include IMS signaling packets / traffic. In some embodiments, the non-IP type traffic / packets transmitted or received over the dedicated bearer of the PDN connection may include voice media, voice data, voice packets, or voice traffic.
[0038] In some embodiments, an IMS PDN (for voice over satellite access (e.g., GEO) ) may be used to transmit or receive both IMS signaling traffic / packets and IMS voice traffic / packets. For IMS signaling traffic / packets, the main consideration is to minimize impact on the IMS control plane network (the IMS network is designed on an IP basis) . Accordingly, the default EPS bearer for the IMS PDN connection may be configured as an IP-type transmission (i.e., IMS signaling traffic / packets over IP) . When voice packets are sent over a real-time transport protocol (RTP) / user datagram protocol (UDP) / IP, the RTP header may be 12 Bytes, the UDP header may be 8 Bytes, and the IP header may be at least 20 Bytes. Even with Robust Header Compression (RoHC) to compress the RTP / UDP / IP header, the compressed header size is still not small enough to meet the data rate constraint (e.g., 1 kbps) for satellite access (e.g., GEO) . Accordingly, for voice packets, a non-IP type transmission may be used. By using non-IP-type transmission, the RTP / UDP / IP headers of the voice packets may be removed, and / or the overhead may be reduced to a minimum, e.g., only 1 Byte sequence number (SN) field in the RTP header may be needed.
[0039] FIG. 3A depicts an example scenario 300a under schemes in accordance with an implementation of the present disclosure. FIG. 3B depicts an example scenario 300b under schemes in accordance with an implementation of the present disclosure. As illustrated in FIG. 3A, in some embodiments, a single IMS PDN connection for IMS voice over GEO access may include a default EPS bearer configured as an IP type to transmit or receive IMS signaling traffic / packets and a dedicated EPS bearer configured as a non-IP type to transmit or receive voice packets. As illustrated in FIG. 3B, in some embodiments, the PDN connection may be of an IP type (e.g., IPv4, IPv6, or IPv4v6) . In one example, the PDN connection type for support of IMS voice over NB-IoT NTN may be IP.
[0040] In scenarios with limited bandwidth, such as GEO satellite links, using a no IP / UDP header transport method for IMS voice / media packets may reduce protocol overhead and enhance VoLTE voice quality. An IP-type PDN connection is established for IMS signaling, where SIP (IMS Signaling) messages are transmitted via the default EPS bearer using IP, ensuring compatibility with existing IMS control procedures. For the media path between the UE and the PGW, (IMS) voice data is delivered over a dedicated EPS bearer as non-IP traffic / packets, without IP and UDP headers, which significantly reduces protocol overhead and is suitable for high latency and low bandwidth links. Between the PGW and the IMS network (such as AGW, P-CSCF) , voice media / packet is still transmitted as IP traffic / packet in line with conventional VoLTE operation, ensuring seamless integration with standard systems. This segmented transmission approach addresses both bandwidth optimization and protocol compatibility, supporting efficient real-time voice service between the UE and IMS network.
[0041] In one embodiment, a communication system comprises a UE, a PGW, and an IMS network including IMS signaling and IMS voice entities. The system establishes a PDN connection of IP type. Signaling packets exchanged between the UE and PGW, and IMS signaling functions are carried as IP packets. Voice packets are mapped to a non-IP format for transport between the UE and the PGW, and are converted at the PGW to IP packets for onward transmission to the IMS voice application gateway (AGW) . The protocol stack for the voice path between the UE and the PGW omits the UDP and IP headers and instead applies a streamlined protocol, such as real-time transport protocol slim (RTPSlim) , suitable for carrying encoded voice, such as ultra low bitrate speech codec (ULBC) (AI speech codec) . The architecture supports RTP over IP as the conventional solution, and RTPSlim over non-IP as an alternative, and includes ongoing work for protocol definition and codec integration, as indicated by System Aspects Working Group 4 (SA4) standardization activities.
[0042] In other embodiments, the IMS PDN configuration for IMS voice over GEO access may include a default EPS bearer configured as the non-IP type to transmit or receive IMS signaling packets, and a dedicated EPS bearer configured as the IP type to transmit or receive voice packets.
[0043] In the present disclosure, some control plane (CP) / user plane (UP) (service request block (SRB) / data radio bearer (DRB) ) configurations are disclosed for the IMS PDN connection. In some embodiments, the default EPS bearer may be used or associated with an SRB (e.g., SRB1-bis or SRB1) to transmit the IMS signaling, and the dedicated EPS bearer may be used or associated with a DRB to transmit the voice packets.
[0044] In some embodiments, the default EPS bearer may be used or associated with a DRB to transmit the IMS signaling, and the dedicated EPS bearer may be used or associated with an SRB (e.g., SRB1-bis or SRB1) to transmit the voice packets.
[0045] In some embodiments, as shown in FIG. 3B, the default EPS bearer may be used or associated with a DRB to transmit the IMS signaling, and the dedicated EPS bearer may be used or associated with a DRB to transmit the voice packets.
[0046] In some embodiments, the default EPS bearer may be used or associated with an SRB (e.g., SRB1-bis or SRB1) to transmit the IMS signaling, and the dedicated EPS bearer may be used or associated with an SRB (e.g., SRB1-bis or SRB1) to transmit the voice packets.
[0047] In the present disclosure, the UE and the network may support IP and non-IP Hybrid PDN Type (INHPT) , wherein IP (e.g., Internet Protocol version 4 (IPv4) , Internet Protocol version 6 (IPv6) , or Internet Protocol version 4 and Internet Protocol version 6 (IPv4v6) ) type traffic / packet may be for the default EPS bearer and non-IP type traffic / packet may be for the dedicated EPS bearer. In other words, the UE and the core network may support the PDN connection with both IP EPS bearer and non-IP EPS bearer. In one embodiment, the IP type traffic may be transmitted or received using IPv4, IPv6, or IPv4v6.
[0048] In some embodiments, the UE may establish an IMS PDN connection with the network and indicate support for transporting voice media traffic using non-IP type traffic over a dedicated bearer of the IMS PDN connection in an UL NAS message. In some embodiments, the IMS PDN connection may be of an IP type. In some embodiments, the UE may support INHPT by indicating it in the UE (network) capability or (Extended) protocol configuration. In one embodiment, the UE may indicate support of INHPT in an uplink (UL) non-access stratum (NAS) message. In one embodiment, the UE may indicate support for transporting voice by non-IP type traffic over a dedicated bearer in an (extended) protocol configuration options (PCO) information element (IE) in an UL NAS message. In one embodiment, the UL NAS message may be a PDN connectivity request message. In one embodiment, the UE may indicate support of INHPT in an evolved session management (ESM) information response message. In one embodiment, the UE may indicate support of INHPT in an attach request (message) . In one embodiment, the UE may indicate support of INHPT in a tracking area update request (message) .
[0049] In some embodiments, the network (e.g., the MME) may maintain an IMS PDN connection with the UE and indicate, in a DL NAS message, whether to transmit or receive non-IP type traffic / packet over a dedicated bearer of the IMS PDN connection. In some embodiments, the DL NAS message may be an active dedicated EPS bearer context request message. In some embodiments, the IMS PDN connection may be of an IP type. In some embodiments, the network (e.g., the MME) may support (and accept to use) the INHPT. In one embodiment, the network may indicate support / use of INHPT in an Activate default EPS bearer context request (message) . In one embodiment, the network may indicate support / use of INHPT in an Activate dedicated EPS bearer context request (message) . In one embodiment, the network may indicate support / use of INHPT in an attach accept (message) . In one embodiment, the network may indicate support / use of INHPT in a tracking area update accept (message) .
[0050] In some embodiments, during a dedicated EPS bearer context activation procedure, the network may indicate (for a dedicated bearer to be activated) whether the traffic / packet type to be sent over the bearer is IP (e.g., IPv4, IPv6, or IPv4v6) type traffic / packet or non-IP type traffic / packet.
[0051] FIG. 4A depicts an example scenario 400a under schemes in accordance with an implementation of the present disclosure. FIG. 4B depicts an example scenario 400b under schemes in accordance with an implementation of the present disclosure. In the present disclosure, for the uplink voice packet to be sent over a dedicated bearer using non-IP type traffic / packet, FIG. 3A, FIG. 3B, and FIG. 4A disclose a new packet filter component type identifier (e.g., " (IMS) voice traffic type” ) to indicate to the UE to steer voice traffic to the dedicated EPS bearer context.
[0052] In some embodiments, to build the context of the conversion, the network (e.g., the PGW or the AGW) may convert the "Voice with RTP info (e.g., 1 Byte SN) packet" to "Voice over RTP / UDP / IP packet" in an event that the PGW receives uplink packets from the "non-IP type traffic / packet" dedicated EPS bearer.
[0053] In addition, the network (e.g., the P-CSCF) may analyze the session description protocol (SDP) in the SDP answer and send the authorize / authenticate-request message to the PCRF, including the related service information (IP address, port numbers, media-type information) . The network (e.g., the PCRF) may authorize the request, identify the affected IP-connectivity access network (IP-CAN) session (e.g., the default bearer) that has been established, and initiate a re-auth-request to the PGW to create a dedicated voice bearer with a related traffic flow template. The network (e.g., the PGW or the AGW) may build and / or store the context for the conversion (e.g., IP (s) and Port (s) ) to perform the conversion.
[0054] In some embodiments, the network (e.g., the PGW) may maintain a PDN connection with the UE, and a default bearer and a dedicated bearer may be associated with the PDN connection. Then the network (e.g., the PGW) may transmit or receive IP type traffic and non-IP type traffic over the PDN connection.
[0055] In some embodiments, the network (e.g., the PGW) may receive an uplink non-IP type traffic / packet and convert the uplink non-IP type traffic / packet to the IP type traffic / packet by adding or restoring an IP header to the received uplink non-IP type traffic / packet. In some embodiments, adding or restoring the IP header may be based on IP address information indicated or notified by a network function (e.g., the PCRF) .
[0056] In some embodiments, as shown in FIG. 4A, the network (e.g., the PGW) may receive an uplink non-IP type traffic / packet and convert the uplink non-IP type traffic / packet to the IP type traffic / packet by adding or restoring an IP header and / or a UDP header to the received uplink non-IP type traffic. In some embodiments, adding or restoring the IP and / or UDP headers may be based on IP address information indicated or notified by a network function (e.g., the PCRF) .
[0057] In some embodiments, for the downlink voice packet, the network (e.g., the PGW) may still leverage the current DL traffic flow template (TFT) as usual; but for DL traffic steered to the "non-IP type traffic" dedicated EPS bearer, the network (e.g., the PGW) may convert the DL voice from RTP / UDP / IP voice packets into voice packets with only partial RTP info (e.g., 1 Byte SN) . In some embodiments, the conversion may be simply removing the RTP / UDP / IP headers and using the "1 Byte SN value originally indicated in the removed RTP header" as the converted header portion of the voice packet. In some embodiments, the network (e.g., the AGW or the PGW) may perform RTP header conversion (e.g., reduced RTP header to minimum (e.g., only 1 Byte (RTP) SN field) ) . In some embodiments, the UE may add or restore the UDP / IP header to the received DL non-IP type traffic / packet. In some embodiments, the UE may add or restore the RTP header to the received DL non-IP type traffic / packet. Illustrative Implementations
[0058] FIG. 5 illustrates an example communication system 500 having an example communication apparatus 510 and an example network apparatus 520 in accordance with an implementation of the present disclosure. Each of the communication apparatus 510 and network apparatus 520 may perform various functions to implement schemes, techniques, processes, and methods described herein about maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access, including scenarios / schemes described above, as well as processes 500 and 600 described below.
[0059] Communication apparatus 510 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus, or a computing apparatus. For instance, communication apparatus 510 may be implemented in a smartphone, a smartwatch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer, or a notebook computer. Communication apparatus 510 may also be a part of a machine-type apparatus, which may be a UE, a reduced-capability (ReCap) UE, an IoT, NB-IoT, NTN, NB-IoT over NTN (NB NTN) , enhanced machine type communication (eMTC) , or IIoT UE, such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU) , a wire communication apparatus, or a computing apparatus. For instance, communication apparatus 510 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker, or a home control center. Alternatively, communication apparatus 510 may be implemented in the form of one or more integrated-circuit (IC) chips, such as, for example, and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. Communication apparatus 510 may include at least some of those components shown in FIG. 5, such as a processor 512, for example. Communication apparatus 510 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device, and / or user interface device) , and, thus, such component (s) of communication apparatus 510 are neither shown in FIG. 5 nor described below in the interest of simplicity and brevity.
[0060] Network apparatus 520 may be a part of an electronic apparatus, which may be a network node such as a BS (e.g., a 6gNB, gNB, TRP, or eNB) , a small cell, a network function (entity) (e.g., an MME, an EIR, a PEI, a centralized database (e.g., an HSS) , or a UDM) , a PCRF, a P-CSCF, a P-SCF, an S-CSCF, an AMF, an SMF, or a UPF) , a router, or a gateway (e.g., an NTN gateway, an IMS access gateway (IMS-AGW) , an AGW, a SGW, or a packet data network gateway (PGW) ) of a network. For instance, network apparatus 520 may be implemented in a BS of a 4G / 5G / B5G / 6G network, in an NB-IoT over NTN (NB NTN) apparatus, in an IoT apparatus, in an NB-IoT apparatus, in a IIoT apparatus, in an NTN apparatus, or in a network function (entity) or network apparatus of an IMS network or a satellite (e.g., GEO, MEO, or LEO) IoT network. Alternatively, network apparatus 520 may be implemented in the form of one or more IC chips, such as, for example, and without limitation, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network apparatus 520 may include at least some of the components shown in FIG. 5, such as a processor 522. Network apparatus 520 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device, and / or user interface device) , and, thus, such component (s) of network apparatus 520 are neither shown in FIG. 5 nor described below in the interest of simplicity and brevity.
[0061] In one aspect, each of processors 512 and 522 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 512 and processor 522, each of processor 512 and processor 522 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 512 and processor 522 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 512 and processor 522 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks, including maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access, in a device (e.g., as represented by communication apparatus 510) and a network node (e.g., as represented by network apparatus 520) in accordance with various implementations of the present disclosure.
[0062] In some implementations, communication apparatus 510 may also include a transceiver 516 coupled to processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, transceiver 516 may be capable of wirelessly communicating with different types of UEs and / or wireless networks of different RATs, such as 4G / 5G / B5G / 6G / Satellite. In some implementations, transceiver 516 may be equipped with a plurality of antenna ports (not shown) , such as four. That is, transceiver 516 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications. In some implementations, network apparatus 520 may also include a transceiver 526 coupled to processor 522. Transceiver 526 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 526 may be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations, transceiver 526 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 526 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications. In some implementations, transceiver 526 may be equipped with a wired network interface, such as a fiber optic cable, for communicating with other network nodes / functions.
[0063] In some implementations, communication apparatus 510 may further include a memory 514 coupled to processor 512 and capable of being accessed by processor 512 and storing data therein. In some implementations, network apparatus 520 may further include a memory 524 coupled to processor 522 and capable of being accessed by processor 522 and storing data therein. Each of memory 514 and memory 524 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) , and / or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of memory 514 and memory 524 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) , and / or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of memory 514 and memory 524 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) , and / or phase-change memory.
[0064] Each of communication apparatus 510 and network apparatus 520 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of the capabilities of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., a BS, an AGW, an S-GW, a P-GW, a PCRF, a P-CSCF, a P-SCF, an S-CSCF, an MME, an AMF, an SMF, etc. ) , is provided below with processes 600, 700, 800, and 900. Illustrative Processes
[0065] FIG. 6 illustrates an example process 600 in accordance with an implementation of the present disclosure. Process 600 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access. Process 600 may represent an aspect of implementation of features of communication apparatus 510. Communication apparatus 510 may support IMS voice calls over NB-IoT NTN via an earth-orbit satellite that connects to a core network. Process 600 may include one or more operations, actions, or functions as illustrated by one or more of blocks 610 to 620. Although illustrated as discrete blocks, various blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 600 may be executed in the order shown in FIG. 6 or, alternatively, in a different order. Process 600 may be implemented by communication apparatus 510 or any suitable UE or machine-type devices. Solely for illustrative purposes and without limitation, process 600 is described below in the context of communication apparatus 510 as a UE. Process 600 may begin at block 610.
[0066] At block 610, process 600 may involve processor 512 of communication apparatus 510 maintaining a PDN connection with a network. Process 600 may proceed from block 610 to block 620.
[0067] At block 620, process 600 may involve processor 512 transmitting or receiving, via transceiver 516, IP type traffic and non-IP type traffic over the PDN connection.
[0068] In some implementations, the PDN connection is a single PDN connection.
[0069] In some implementations, a default EPS bearer and a dedicated EPS bearer may be associated with the PDN connection, and the non-IP type traffic / packet is transmitted or received over the dedicated EPS bearer.
[0070] In some implementations, the non-IP type traffic / packet is non-IP type IMS voice traffic / packet, and the IP type traffic / packet is IP type IMS signaling traffic / packet.
[0071] In some implementations, the non-IP type IMS voice traffic / packet is transmitted or received over the dedicated (EPS) bearer, and the IP type IMS signaling traffic / packet is transmitted or received over the default (EPS) bearer.
[0072] In some implementations, the IP type traffic / packet may be transmitted or received over the default EPS bearer.
[0073] In some implementations, the IP type traffic / packet may be transmitted or received over the PDN connection using an IPv4, an IPv6, or an IPv4v6.
[0074] In some implementations, the IP type traffic may include data, a packet, or traffic with an IP header, and the non-IP type traffic may include data, a packet, or traffic without an IP header.
[0075] In some implementations, the non-IP type traffic may include data, a packet, or traffic without a UDP header.
[0076] In some implementations, the non-IP type traffic may include data, packets, or traffic with a partial, reduced, minimal, or compressed RTP header.
[0077] In some implementations, the partial, reduced, minimal, or compressed RTP header may include a sequence numbering field.
[0078] In some implementations, the PDN connection may be associated with or established for an IMS service.
[0079] In some implementations, an APN (or DNN) for the PDN connection (or PDU session) may be ims.
[0080] In some implementations, process 600 may further involve processor 512 transmitting or receiving, via transceiver 516, the IP type traffic / packet and the non-IP type traffic / packet over the PDN connection via a satellite access.
[0081] In some implementations, communication apparatus 510 supports services over an NB-IoT via a GEO satellite.
[0082] In some implementations, the satellite access may be connected to an EPC.
[0083] In some implementations, the service may be provided over NB-IoT RAT.
[0084] In some implementations, process 600 may further involve processor 512 indicating support for transporting IMS voice packet by the non-IP type traffic / packet over a dedicated bearer in a UE capability or in PCO IE in an UL NAS message.
[0085] In some implementations, the UL NAS message may be a PDN connectivity request message.
[0086] In some implementations, the IP type traffic / packet transmitted or received over a default bearer of the PDN connection may include IMS signaling packet.
[0087] In some implementations, the non-IP type traffic / packet may be transmitted or received over a dedicated bearer of the PDN connection, and the non-IP type traffic / packet transmitted or received over the dedicated bearer may include voice media, voice data, voice packets, or voice traffic.
[0088] In some implementations, process 600 may further involve processor 512 transmitting or receiving, via transceiver 516, the IP type traffic over a default bearer of the PDN connection. The IP type traffic transmitted or received over the default bearer of the PDN connection may comprise an IMS signaling packet.
[0089] In some implementations, process 600 may further involve processor 512 transmitting or receiving, via transceiver 516, the non-IP type traffic over a dedicated bearer of the PDN connection. The non-IP type traffic transmitted or received over the dedicated bearer comprises an IMS media packet or an IMS voice packet.
[0090] In some implementations, process 600 may further involve processor 512 receiving, via transceiver 516, an indication of (using) non-IP type traffic / packet associated with a dedicated bearer from the network in a DL NAS message.
[0091] In some implementations, the DL NAS message may be an active dedicated EPS bearer context request message.
[0092] In some implementations, the PDN connection may include a first bearer and a second bearer, and the IP type traffic and the non-IP type traffic may be transmitted or received over the first bearer and the second bearer respectively.
[0093] FIG. 7 illustrates an example process 700 in accordance with an implementation of the present disclosure. Process 700 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access. Process 700 may represent an aspect of implementation of features of communication apparatus 510. Communication apparatus 510 may support IMS voice calls over NB-IoT NTN via an earth-orbit satellite that connects to a core network. Process 700 may include one or more operations, actions, or functions as illustrated by one or more of blocks 710 to 720. Although illustrated as discrete blocks, various blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 700 may be executed in the order shown in FIG. 7 or, alternatively, in a different order. Process 700 may be implemented by communication apparatus 510 or any suitable UE or machine-type devices. Solely for illustrative purposes and without limitation, process 700 is described below in the context of communication apparatus 510 as a UE. Process 700 may begin at block 710.
[0094] At block 710, process 700 may involve processor 512 of communication apparatus 510 establishing a PDN connection with a network. Process 700 may proceed from block 710 to block 720.
[0095] At block 720, process 700 may involve processor 512 indicating support for transporting voice media traffic / packet using non-IP type traffic / packet over a dedicated bearer of the PDN connection in an UL NAS message.
[0096] In some implementations, the PDN connection is a single PDN connection.
[0097] In some implementations, the UL NAS message may be a PDN connectivity request message.
[0098] In some implementations, the PDN connection may be an IP type.
[0099] FIG. 8 illustrates an example process 800 in accordance with an implementation of the present disclosure. Process 800 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access. Process 800 may represent an aspect of implementation of features of network apparatus 520. Process 800 may include one or more operations, actions, or functions as illustrated by one or more of blocks 810 to 820. Although illustrated as discrete blocks, various blocks of process 800 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 800 may be executed in the order shown in FIG. 8 or, alternatively, in a different order. Process 800 may be implemented by network apparatus 520 or any suitable network node (supporting certain network function (s) ) . Solely for illustrative purposes and without limitation, process 800 is described below in the context of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., an AGW, an S-GW, a P-GW, a PCRF, a P-CSCF, a P-SCF, an S-CSCF, an MME, an AMF, an SMF, etc. ) . Process 800 may begin at block 810.
[0100] At block 810, process 800 may involve processor 522 of network apparatus 520 maintaining a PDN connection with communication apparatus 510. A default bearer and a dedicated bearer may be associated with the PDN connection. Process 800 may proceed from block 810 to block 820.
[0101] At block 820, process 800 may involve processor 522 transmitting or receiving, via transceiver 526, IP type traffic / packet and non-IP type traffic / packet over the PDN connection.
[0102] In some implementations, the type of the PDN connection may be IPv4, IPv6, or IPv4v6.
[0103] In some implementations, the IP type traffic may include data, a packet, or traffic with an IP header, and the non-IP type traffic may include data, a packet, or traffic without an IP header.
[0104] In some implementations, process 800 may further involve processor 522 receiving, via transceiver 526, an uplink non-IP type traffic. The process 800 may further involve processor 522 converting the uplink non-IP type traffic to the IP type traffic by adding or restoring an IP header to the received uplink non-IP type traffic.
[0105] In some implementations, the adding or restoring of the IP header may be based on (IP address) information indicated or notified by a PCRF.
[0106] In some implementations, the non-IP type traffic may include data, a packet, or traffic without a UDP header. The process 800 may further involve processor 522 receiving, via transceiver 526, an uplink non-IP type traffic / packet. The process 800 may further involve processor 522 converting the uplink non-IP type traffic / packet to the IP type traffic / packet by adding or restoring an IP header and / or the UDP header to the received uplink non-IP type traffic / packet.
[0107] In some implementations, the adding or restoring of the IP header and the UDP header may be based on (IP address and UDP port) information indicated or notified by a PCRF.
[0108] In some implementations, the network may include a PGW or a UPF.
[0109] FIG. 9 illustrates an example process 900 in accordance with an implementation of the present disclosure. Process 900 may be an example implementation of above scenarios / schemes, whether partially or completely, with respect to maintaining an IMS PDN connection with both IP EPS bearer and non-IP EPS bearer over satellite access. Process 900 may represent an aspect of implementation of features of network apparatus 520. Process 900 may include one or more operations, actions, or functions as illustrated by one or more of blocks 910 to 920. Although illustrated as discrete blocks, various blocks of process 900 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 900 may be executed in the order shown in FIG. 9 or, alternatively, in a different order. Process 900 may be implemented by network apparatus 520 or any suitable network node (supporting certain network function (s) ) . Solely for illustrative purposes and without limitation, process 900 is described below in the context of communication apparatus 510, as a UE, and network apparatus 520, as a network node (e.g., an AGW, an S-GW, a P-GW, a PCRF, a P-CSCF, a P-SCF, an S-CSCF, an MME, an AMF, an SMF, etc. ) . Process 900 may begin at block 910.
[0110] At block 910, process 900 may involve processor 522 of network apparatus 520 maintaining a PDN connection with communication apparatus 510. Process 900 may proceed from block 910 to block 920.
[0111] At block 920, process 900 may involve processor 522 indicating whether to transmit or receive non-IP type traffic / packet over a dedicated bearer of the PDN connection in a DL NAS message.
[0112] In some implementations, the DL NAS message may be an active dedicated EPS bearer context request message.
[0113] In some implementations, the PDN connection may be of an IP type.
[0114] In some implementations, the network may include an MME or an AMF. Additional Notes
[0115] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In some implementation, a PDN connection may be replaced with a PDU session, a default EPS bearer of a PDN connection may be replaced with a quality of service (QoS) Flow associated with the default QoS rule of a PDU session, a dedicated EPS bearer of a PDN connection may be replaced with a QoS Flow not associated with the default QoS rule of a PDU session, a active dedicated EPS bearer context request message may be replaced with a PDU Session Modification Command message, a PDN Connectivity Request Message may be replaced with a PDU Session Establishment Request message, In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.
[0116] Further, with respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.
[0117] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”
[0118] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
A method, comprising:maintaining, by a processor of an apparatus, a packet data network (PDN) connection with a network; andtransmitting or receiving, by the processor, Internet Protocol (IP) type traffic and non-IP type traffic over the PDN connection.The method of Claim 1, wherein a default evolved packet system (EPS) bearer and a dedicated EPS bearer are associated with the PDN connection.The method of Claim 2, wherein the non-IP type traffic is non-IP type IP multimedia subsystem (IMS) voice traffic, and the IP type traffic is IP type IMS signaling traffic; and wherein the non-IP type IMS voice traffic is transmitted or received over the dedicated EPS bearer, and the IP type IMS signaling traffic is transmitted or received over the default EPS bearer.The method of Claim 1, wherein the IP type traffic is transmitted or received over the PDN connection using an Internet Protocol version 4 (IPv4) , an Internet Protocol version 6 (IPv6) , or an Internet Protocol version 4 and Internet Protocol version 6 (IPv4v6) .The method of Claim 1, wherein the IP type traffic comprises data or a packet with an IP header, and wherein the non-IP type traffic comprises data or a packet without an IP header.The method of Claim 1, wherein the non-IP type traffic comprises data or a packet without a user datagram protocol (UDP) header.The method of Claim 1, wherein the non-IP type traffic comprises data or a packet with a minimal, partial, reduced, or compressed real-time transport protocol (RTP) header.The method of Claim 7, wherein the minimal, partial, reduced, or compressed RTP header comprises a sequence numbering field.The method of Claim 1, wherein the PDN connection is associated with an IP multimedia subsystem (IMS) service, and an access point name (APN) for the PDN connection is ims.The method of Claim 1, further comprising:transmitting or receiving, by the processor, the Internet Protocol (IP) type traffic and the non-IP type traffic over the PDN connection via a satellite access.The method of Claim 10, wherein the apparatus supports services over a narrowband Internet of Things (NB-IoT) via a geostationary earth orbit (GEO) satellite.The method of Claim 1, further comprising:indicating, by the processor, a support of transporting IP multimedia subsystem (IMS) voice by the non-IP type traffic over a dedicated bearer in a user equipment (UE) capability or protocol configuration options information element (IE) in an uplink (UL) non-access stratum (NAS) message.The method of Claim 12, wherein the UL NAS message is a PDN connectivity request message.The method of Claim 1, further comprising:transmitting or receiving, by the processor, the IP type traffic over a default bearer of the PDN connection, wherein the IP type traffic transmitted or received over the default bearer of the PDN connection comprises an Internet Protocol (IP) multimedia subsystem (IMS) signaling packet.The method of Claim 1, further comprising:transmitting or receiving, by the processor, the non-IP type traffic over a dedicated bearer of the PDN connection, and wherein the non-IP type traffic transmitted or received over the dedicated bearer comprises an Internet Protocol (IP) multimedia subsystem (IMS) media packet or an IMS voice packet.The method of Claim 1, further comprising:receiving, by the processor, an indication of the non-IP type traffic associated with a dedicated bearer from the network in a downlink (DL) non-access stratum (NAS) message.The method of Claim 16, wherein the DL NAS message is an active dedicated EPS bearer context request message.A method, comprising:maintaining, by a processor of a network, a packet data network (PDN) connection with a user equipment, wherein a default bearer and a dedicated bearer are associated with the PDN connection; andtransmitting or receiving, by the processor, Internet Protocol (IP) type traffic and non-IP type traffic over the PDN connection.The method of Claim 18, wherein a type of the PDN connection is Internet Protocol version 4 (IPv4) , Internet Protocol version 6 (IPv6) , or Internet Protocol version 4 and Internet Protocol version 6 (IPv4v6) .The method of Claim 18, wherein the IP type traffic comprises data or a packet with an IP header, and the non-IP type traffic comprises data or a packet without an IP header.The method of Claim 20, further comprising:receiving, by the processor, an uplink non-IP type traffic; andconverting, by the processor, the uplink non-IP type traffic to the IP type traffic by adding or restoring the IP header to the received uplink non-IP type traffic.The method of Claim 21, wherein the adding or restoring of the IP header is based on IP address information indicated or notified by a policy and charging rules function (PCRF) .The method of Claim 20, wherein the non-IP type traffic comprises data or a packet without a user datagram protocol (UDP) header.The method of Claim 23, further comprising:receiving, by the processor, an uplink non-IP type traffic; andconverting, by the processor, the uplink non-IP type traffic to the IP type traffic by adding or restoring the IP header and the UDP header to the received uplink non-IP type traffic.The method of Claim 23, wherein the adding or restoring of the IP header and the UDP header is based on IP address and UDP port information indicated or notified by a policy and charging rules function (PCRF) .The method of Claim 21, wherein the network comprises a PDN gateway (PGW) .A method, comprising:establishing, by a processor of an apparatus, a packet data network (PDN) connection with a network; andindicating, by the processor, a support of transporting voice traffic using non-Internet Protocol (IP) type traffic over a dedicated bearer of the PDN connection in an uplink (UL) non-access stratum (NAS) message.The method of Claim 27, wherein the UL NAS message is a PDN connectivity request message.The method of Claim 27, wherein the PDN connection is of an Internet Protocol (IP) type.A method, comprising:maintaining, by a processor of a network, a packet data network (PDN) connection with a user equipment; andindicating, by the processor, whether to transmit or receive non-Internet Protocol (IP) type traffic over a dedicated bearer of the PDN connection in a downlink (DL) non-access stratum (NAS) message.The method of Claim 30, wherein the DL NAS message is an active dedicated evolved packet system (EPS) bearer context request message.The method of Claim 30, wherein the PDN connection is of an Internet Protocol (IP) type.The method of Claim 30, wherein the network comprises a mobility management entity (MME) .An apparatus, comprising:a transceiver which, during operation, communicates wirelessly; anda processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:maintaining a packet data network (PDN) connection with a network; andtransmitting or receiving, via the transceiver, Internet Protocol (IP) type traffic and non-IP type traffic over the PDN connection.An apparatus, comprising:a transceiver which, during operation, communicates wirelessly; anda processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:maintaining a packet data network (PDN) connection with a user equipment, wherein a default bearer and a dedicated bearer are associated with the PDN connection; andtransmitting or receiving, via the transceiver, Internet Protocol (IP) type traffic and non-IP type traffic over the PDN connection.An apparatus, comprising:a transceiver which, during operation, communicates wirelessly; anda processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:establishing a packet data network (PDN) connection with a network; andindicating a support of transporting voice traffic using non-Internet Protocol (IP) type traffic over a dedicated bearer of the PDN connection in an uplink (UL) non-access stratum (NAS) message.An apparatus, comprising:a transceiver which, during operation, communicates wirelessly; anda processor communicatively coupled to the transceiver such that, during operation, the processor performs operations comprising:maintaining a packet data network (PDN) connection with a user equipment; andindicating whether to transmit or receive non-Internet Protocol (IP) type traffic over a dedicated bearer of the PDN connection in a downlink (DL) non-access stratum (NAS) message.
