Method and apparatus for session description protocol pre-configuration with dedicated quality-of-service resource
The SDP pre-configuration procedure addresses signaling overhead and latency in call setups by negotiating and storing SDP parameters ahead of time, reducing message exchanges and activating QoS resources, thus enhancing call setup efficiency in constrained networks.
Patent Information
- Application Number
- PCT/CN2026/093064
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-20
- Filing Date
- 2026-04-27
- Publication Date
- 2026-11-19
AI Technical Summary
Conventional SDP negotiation during call setup in communication environments with constrained transmission resources or high propagation delays, such as non-terrestrial networks, results in significant signaling overhead and prolonged call setup times.
Implementing an SDP pre-configuration procedure during a SIP registration or pre-call SIP message exchange to negotiate and store SDP parameters, allowing subsequent call setups to utilize these pre-configured parameters without full SDP offer/answer exchanges, and activate dedicated QoS resources in advance.
Reduces signaling overhead and call setup latency by minimizing message exchanges and activating QoS resources prior to call setup, optimizing user experience in constrained environments.
Smart Images

Figure CN2026093064_19112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR SESSION DESCRIPTION PROTOCOL PRE-CONFIGURATION WITH DEDICATED QUALITY-OF-SERVICE RESOURCE
[0001] CROSS REFERENCE TO RELATED APPLICATION
[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 808,691, filed on May 20th, 2025. Further, this application claims the benefit of U.S. Provisional Application No. 63 / 804,723, filed on May 13th, 2025. The contents of these applications are incorporated herein by reference.TECHNICAL FIELD
[0003] The present disclosure relates to wireless communication systems, and more particularly to methods and apparatus for session description protocol (SDP) pre-configuration with dedicated Quality of Service (QoS) resource to facilitate call setup procedures.BACKGROUND
[0004] In communication networks, an Internet Protocol Multimedia Subsystem (IMS) provides multimedia services such as voice, video, and messaging to user equipment (UE) through Session Initiation Protocol (SIP) signaling. During an IMS call setup, the calling and called parties negotiate media session parameters through a Session Description Protocol (SDP) offer / answer exchange. The SDP parameters typically include media codec type, IP addresses, port numbers, and other attributes necessary for establishing a media path between the communicating parties.
[0005] In a conventional IMS call setup procedure, the SDP offer / answer exchange is performed as part of the call setup signaling. For example, when a UE initiates a mobile-originated (MO) call, the UE sends a SIP INVITE message containing an SDP offer to the network. The network processes the offer and returns an SDP answer in a response message such as a 183 Session Progress message. Additional SIP messages, including Provisional Response Acknowledgement (PRACK) , UPDATE, and their corresponding responses, may be exchanged to complete the SDP negotiation and establish preconditions for the media session. This multi-message exchange results in significant signaling overhead during the call setup.
[0006] The signaling overhead associated with SDP negotiation during call setup is particularly problematic in communication environments where transmission resources are constrained or where propagation delays are substantial. For example, in non-terrestrial network (NTN) scenarios involving satellite access, such as geostationary (GEO) satellite access via narrowband Internet of Things (NB-IoT) technology, each round-trip message exchange incurs significant delay due to the large distance between the UE and the satellite. The cumulative effect of multiple SDP-related message exchanges during call setup may result in call setup times that exceed acceptable thresholds for the user experience. Furthermore, the limited bandwidth available over NTN links means that the large message sizes associated with conventional SDP negotiation consume a disproportionate share of the available transmission resources.
[0007] Accordingly, there is a need for techniques that reduce the signaling overhead and delay associated with SDP negotiation during call setup, particularly in communication environments with constrained transmission resources or high propagation delays.SUMMARY OF THE INVENTION
[0008] An embodiment provides a method performed by a user equipment (UE) for communicating with a network entity. The method comprises performing a Session Description Protocol (SDP) pre-configuration procedure with the network entity by exchanging at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. The method further includes storing at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The method further includes triggering activation or modification of a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter. The method further includes, in response to the activation or modification of the dedicated QoS resource, initiating a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource.
[0009] In some aspects, the SDP pre-configuration procedure may be performed during a SIP registration procedure. In some other aspects, the SDP pre-configuration procedure may be performed after a SIP registration procedure and prior to the call setup procedure by transmitting a SIP message for performing the SDP pre-configuration procedure. The dedicated QoS resource may be activated or modified in response to completing the SDP pre-configuration procedure. The at least one stored SDP parameter may be applicable to subsequent call setup procedures during a registration lifecycle of the UE. The UE may initiate the specific call setup procedure by transmitting a SIP INVITE message without an SDP body. The UE may communicate with the network entity via a non-terrestrial network (NTN) access. The dedicated QoS resource may comprise a dedicated Evolved Packet System (EPS) bearer and / or a dedicated QoS flow.
[0010] Another embodiment provides a method performed by a network entity for communicating with a UE.The method includes performing an SDP pre-configuration procedure with the UE by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. The method further includes storing at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The method further includes activating or modifying a dedicated QoS resource based on the at least one stored SDP parameter. The method further includes receiving a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource.
[0011] In some aspects, the network entity may further restore the at least one stored SDP parameter to complete call establishment. For a mobile-terminated call setup procedure, restoring the at least one stored SDP parameter may comprise modifying an SDP body in a SIP INVITE message based on the at least one stored SDP parameter. The dedicated QoS resource may be activated or modified in response to completing the SDP pre-configuration procedure. The network entity may comprise a Proxy Call Session Control Function (P-CSCF) within an Internet Protocol Multimedia Subsystem (IMS) network entity. The dedicated QoS resource may comprise a dedicated EPS bearer and / or a dedicated QoS flow.
[0012] In some aspects, the specific call setup procedure is a mobile-originated call setup procedure, and receiving the SIP message comprises receiving the SIP message from the UE. In some aspects, the specific call setup procedure is a mobile-terminated call setup procedure, and receiving the SIP message comprises receiving the SIP message from an IMS core entity.
[0013] Another embodiment provides a UE including a transceiver for communicating with a network entity, and a processor coupled to the transceiver. The processor is configured to perform an SDP pre-configuration procedure with the network entity by exchanging, via the transceiver, at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. The processor is further configured to store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The processor is further configured to trigger activation or modification of a dedicated QoS resource based on the at least one stored SDP parameter. The processor is further configured to, in response to the activation or modification of the dedicated QoS resource, initiate a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource.
[0014] Another embodiment provides a network entity including a memory for storing instructions, and a processor coupled to the memory. The processor is configured to execute the instructions to perform a Session Description Protocol (SDP) pre-configuration procedure with a user equipment (UE) by exchanging at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. The processor is further configured to store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The processor is further configured to activate or modify a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter, and receive a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource.
[0015] To the accomplishment of the foregoing and related ends, certain embodiments comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative aspects of the embodiments. These aspects are indicative, however, of but a few of the various ways in which the principles of the embodiments may be employed, and the present disclosure is intended to include all such aspects and their equivalents. These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] FIG. 1 depicts an exemplary wireless communications system and access network.
[0017] FIG. 2 depicts block diagrams of a base station in communication with a UE in a wireless network.
[0018] FIG. 3 depicts an exemplary IMS network architecture in which the SDP pre-configuration procedures described herein may be applied.
[0019] FIG. 4 depicts a signaling flow diagram illustrating a signaling flow for an SDP pre-configuration procedure during a SIP registration procedure according to an embodiment of the present disclosure.
[0020] FIG. 5 depicts an exemplary XML body structure for the SDP pre-configuration procedure during a SIP registration procedure according to an embodiment of the present disclosure.
[0021] FIG. 6 depicts a signaling flow diagram illustrating a signaling flow for an SDP pre-configuration procedure using a pre-call SIP message flow according to an embodiment of the present disclosure.
[0022] FIG. 7 depicts an exemplary SDP offer and answer exchange for the SDP pre-configuration procedure using a pre-call SIP message flow according to an embodiment of the present disclosure.
[0023] FIG. 8 depicts a signaling flow diagram illustrating a signaling flow for a mobile-originated call setup procedure with SDP pre-configuration according to an embodiment of the present disclosure.
[0024] FIG. 9 depicts a signaling flow diagram illustrating a signaling flow for a mobile-originated call setup procedure with SDP pre-configuration and early dedicated QoS resource activation according to an embodiment of the present disclosure.
[0025] FIG. 10 depicts a signaling flow diagram illustrating a signaling flow for a mobile-terminated call setup procedure with SDP pre-configuration according to an embodiment of the present disclosure.
[0026] FIG. 11 depicts a signaling flow diagram illustrating a signaling flow for a mobile-terminated call setup procedure with SDP pre-configuration and early dedicated QoS resource activation according to an embodiment of the present disclosure.
[0027] FIG. 12 depicts a flow diagram of a method performed by a UE for communicating with a network entity according to an embodiment of the present disclosure.
[0028] FIG. 13 depicts a flow diagram of a method performed by a UE for communicating with a network entity, including dedicated QoS resource activation, according to an embodiment of the present disclosure.
[0029] FIG. 14 depicts a flow diagram of a method performed by a network entity for communicating with a UE according to an embodiment of the present disclosure.
[0030] FIG. 15 depicts a flow diagram of a method performed by a network entity for communicating with a UE, including dedicated QoS resource activation, according to an embodiment of the present disclosure.DETAILED DESCRIPTION
[0031] The following detailed description is provided to assist those skilled in the art in practicing the present disclosure. Even so, the following detailed description should not be construed to unduly limit the present disclosure, as modifications and variations in the embodiments discussed herein may be made by those of ordinary skill in the art without departing from the scope of the present disclosure.
[0032] Embodiments described herein may be understood in the context of standards developed by the Third Generation Partnership Project (3GPP) . In particular, the present disclosure relates to Internet Protocol Multimedia Subsystem (IMS) call procedures, in which a user equipment (UE) establishes voice or multimedia sessions through Session Initiation Protocol (SIP) signaling with network entities such as a Proxy Call Session Control Function (P-CSCF) . In conventional IMS call setup, Session Description Protocol (SDP) parameters describing media session characteristics, such as IP addresses, port numbers, and codec parameters, are negotiated through an offer / answer exchange embedded within the call setup signaling. This SDP negotiation contributes to the overall message size and the number of round-trip signaling exchanges required to establish a call.
[0033] The techniques described herein are particularly applicable to non-terrestrial network (NTN) access scenarios, such as those involving satellite access as defined in 3GPP specifications. In NTN environments, the communication link between the UE and the network is characterized by high propagation delay and limited bandwidth resources. As a result, the conventional call setup procedure, which may require multiple signaling round trips carrying large SDP payloads, can result in call setup times that significantly exceed acceptable thresholds for user experience.
[0034] To address these challenges, the present disclosure introduces an SDP pre-configuration procedure in which SDP parameters are negotiated and stored at both the UE and the network prior to a call setup procedure. By completing the SDP negotiation in advance, for example, during a SIP registration procedure or through a dedicated pre-call SIP message exchange, the subsequent call setup signaling can be performed with reduced message sizes and fewer signaling exchanges, as the pre-configured SDP parameters may be referenced or restored without requiring a full SDP offer / answer exchange during the call itself.
[0035] While the embodiments described herein are presented primarily in the context of 3GPP NTN access and IMS call procedures, those skilled in the art will appreciate that the techniques disclosed may be applicable to other communication systems and network architectures in which SDP negotiation contributes to call setup latency.
[0036] System Architecture
[0037] FIG. 1 depicts an exemplary wireless communications system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, a satellite 123, an NTN gateway 125, an Evolved Packet Core (EPC) 160, and an additional core network 190 (such as a 5G Core (5GC) , IoT network and 6G communication system) . The base stations 102 may be macrocells (high-power cellular base stations) or small cells (low-power cellular base stations) . Macrocells refer to large-scale base stations, while small cells include femtocells, picocells, and microcells.
[0038] The base stations 102 designed for 4G LTE operation (collectively known as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may connect to the EPC 160 via backhaul links 132 (e.g., S1 interface) . Similarly, base stations 102 configured for 5G NR (collectively designated as Next Generation RAN (NG-RAN) ) may interface with core network 190 through backhaul links 184. The base stations 102 may also be designed as network nodes for a 6G network. The base stations 102 may be configured to perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility management (e.g., handover, dual connectivity) , interference coordination between cells, connection management, load distribution, handling of non-access stratum (NAS) messages, NAS node selection, network synchronization, RAN resource sharing, multimedia broadcast services (MBMS) , subscriber tracking, RAN information management (RIM) , paging services, position determination, and emergency alert distribution. Additionally, base stations 102 may communicate with each other either directly or indirectly (e.g., through the EPC 160 or core network 190) using backhaul links 134 (e.g., X2 interface) , which may be implemented as either wired or wireless connections.
[0039] The base stations 102 may wirelessly communicate with the UEs 104. Each base station 102 may provide coverage for a specific geographic area 110, and there may be overlapping coverage areas 110. For instance, the small cell 102'may have a coverage area 110'that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macrocells may be referred to as a heterogeneous network. This type of network may also include Home Evolved Node Bs (HeNBs) , which may serve a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may involve uplink (UL) (also known as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also known as forward link) transmissions from a base station 102 to a UE 104.
[0040] The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. For each carrier, the base stations 102 and / or UEs 104 may utilize spectrum with bandwidths of various sizes (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) up to 7 MHz per carrier. Through carrier aggregation, these individual carriers may be combined to achieve a total bandwidth of Y×X MHz, where X represents the number of component carriers, enabling higher data rates for transmission in each direction. The carriers may or may not be adjacent to one another. The allocation of carriers may be asymmetric with respect to DL and UL, meaning that more or fewer carriers may be allocated for DL than for UL. The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) , while a secondary component carrier may be referred to as a secondary cell (SCell) .
[0041] In some aspects, the wireless communications system may further include a non-terrestrial network (NTN) component to extend coverage beyond the reach of terrestrial base stations 102. As shown in FIG. 1, the satellite 123 may communicate with the UEs 104 via a service link 121. The satellite 123 may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, or a high-altitude platform station (HAPS) . The satellite 123 may communicate with the NTN gateway 125 via a feeder link 127. The NTN gateway 125 may connect to the base station 102 and / or directly to the EPC 160 or the core network 190 through backhaul links. In some configurations, the NTN gateway 125 may be combined with the base station 102, such that the NTN gateway 125 and the base station 102 are co-located or integrated into a single network entity. In such configurations, the combined NTN gateway 125 and base station 102 may perform the functions of both entities, including managing the feeder link 127 to the satellite 123 and providing connectivity to the EPC 160 or core network 190. The NTN component may enable the wireless communications system to provide ubiquitous coverage, including in remote, rural, or maritime areas where terrestrial network infrastructure may not be available.
[0042] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may utilize the DL / UL WWAN spectrum and may operate on one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH) , physical sidelink discovery channel (PSDCH) , physical sidelink shared channel (PSSCH) , and physical sidelink control channel (PSCCH) . D2D communication may occur through various wireless D2D communication systems, including, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
[0043] The wireless communications system may also include a Wi-Fi access point (AP) 150, which may communicate with Wi-Fi stations (STAs) 152 via communication links 154 in the 5 GHz unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the STAs 152 and AP 150 may perform a clear channel assessment (CCA) before communicating to check if the channel is available.
[0044] The small cell 102'may operate in either licensed or unlicensed frequency spectrums, or both. When using an unlicensed frequency spectrum, the small cell 102'may employ NR and utilize the same 5 GHz unlicensed frequency spectrum as the Wi-Fi AP 150. By employing NR in an unlicensed frequency spectrum, the small cell 102'may enhance coverage and / or increase capacity of the access network.
[0045] A base station 102, which may be a small cell 102'or a large cell (e.g., macro base station) , may include an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180, may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmWave) frequencies, and / or near mmWave frequencies when communicating with the UE 104. When the gNB 180 operates in mmWave or near mmWave frequencies, it may be referred to as an mmWave base station.
[0046] Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Near mmWave may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave.
[0047] Communications using the mmWave and / or near mmWave radio frequency band (e.g., 3 GHz-300 GHz) may experience extremely high path loss and may have a short range. The mmWave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range.
[0048] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 108a. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions 108c. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions 108c'. The bidirectional beamforming capability may be used for establishing reliable mmWave communications. The base station 180 and / or the UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 and / or the UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
[0049] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 may be the control node that processes signaling between the UEs 104 and the EPC 160. In some aspects, the MME 162 may provide bearer and connection management.
[0050] All user Internet protocol (IP) packets may transfer through the Serving Gateway 166, which may connect to the PDN Gateway 172. The PDN Gateway 172 may provide UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 may connect to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and / or other IP services.
[0051] The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0052] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 may be the control node that processes signaling between the UEs 104 and the core network 190. In some aspects, the SMF 194 may provide QoS flow and session management. The UPF 195 may serve as the pathway for all user IP packets. In addition to providing UE IP address allocation, the UPF 195 may perform various other functions. The UPF 195 may connect to IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and potentially additional IP services.
[0053] The base station may also be known as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or other suitable terminology. The base station 102 may function as an access point to the EPC 160 or core network 190 for a UE 104.
[0054] Although this specification discusses 4G and 5G technology, the concepts presented may also be relevant to various other wireless communication standards and technologies. These may include 6G, 5G NR, 4G LTE, LTE-A, CDMA, GSM, non-terrestrial network (NTN) communications, and may extend to future generations of wireless, satellite, and radio access technologies that may evolve from current standards.
[0055] FIG. 2 depicts block diagrams of a base station 210 in communication with a UE 250 in a wireless network. The base station 210 may function as a RAN node with an NTN gateway, and may communicate with the UE 250 via a satellite 270. In some aspects, the communication signals between the base station 210 and the UE 250 may be relayed through the satellite 270, such that uplink transmissions from the UE 250 may be transmitted to the satellite 270 via a service link and forwarded to the base station 210 via a feeder link, and downlink transmissions from the base station 210 may be transmitted to the satellite 270 via the feeder link and forwarded to the UE 250 via the service link. The feeder link may refer to the communication link between the base station 210 and the satellite 270, and the service link may refer to the communication link between the satellite 270 and the UE 250. In some other aspects, the base station 210 may communicate with the UE 250 directly without relaying through the satellite 270. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 275. The controller / processor 275 may implement layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 may include a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
[0056] The controller / processor 275 may manage RRC layer functions related to broadcasting system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, establishment, modification, and release) , radio access technology (RAT) mobility, and the configuration of measurements for UE measurement reporting. The controller / processor 275 may also handle PDCP layer functions related to header compression / decompression, security (including ciphering, deciphering, integrity protection, and integrity verification) , and handover support; RLC layer functions for transferring upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions that include mapping logical channels to transport channels, multiplexing MAC SDUs onto transport blocks (TBs) , demultiplexing MAC SDUs from TBs, reporting scheduling information, error correction through HARQ, priority handling, and logical channel prioritization.
[0057] The transmit (TX) processor 216 and the receive (RX) processor 270 may perform layer 1 functions related to various signal processing tasks. Layer 1, which includes the physical (PHY) layer, may involve error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing.
[0058] The TX processor 216 may handle mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be divided into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream.
[0059] The OFDM stream may be spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 274 may help determine the coding and modulation scheme, as well as assist in spatial processing. These estimates may be derived from a reference signal and / or feedback on channel conditions transmitted by the UE 250. Each spatial stream may be sent to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier with its respective spatial stream for transmission. The transmitted signal from each antenna 220 may be relayed through the satellite 270 via the feeder link and the service link to reach the UE 250.
[0060] At the UE 250, each receiver 254RX may receive a signal through its respective antenna 252. In some aspects, the signal received at each antenna 252 may have been relayed through the satellite 270 via the service link from the base station 210. The receiver 254RX may recover the information modulated onto the RF carrier and may pass it to the RX processor 256. The TX processor 268 and RX processor 256 may handle layer 1 functionality associated with various signal processing tasks. The RX processor 256 may perform spatial processing on the received information to recover any spatial streams intended for the UE 250. If multiple spatial streams are directed to the UE 250, the RX processor 256 may combine them into a single OFDM symbol stream. The RX processor 256 may then convert the time-domain OFDM symbol stream into the frequency domain using a Fast Fourier Transform (FFT) . The frequency-domain signal may consist of a separate OFDM symbol stream for each subcarrier of the OFDM signal.
[0061] The symbols on each subcarrier, and the reference signal, may be recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions may then be decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals may then be provided to the controller / processor 259, which may implement layer 3 and layer 2 functionality.
[0062] The controller / processor 259 may be linked to a memory 260 that may hold program code and data, with the memory 260 being referred to as a computer-readable medium. In the UL, the controller / processor 259 may handle tasks such as demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. Additionally, the controller / processor 259 may be responsible for error detection through an ACK and / or NACK protocol to support HARQ operations.
[0063] Similar to the DL transmission functionality provided by the base station 210, the controller / processor 259 may handle RRC layer functions related to system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functions for header compression / decompression and security (including ciphering, deciphering, integrity protection, and integrity verification) ; RLC layer functions for transferring upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions that include mapping logical channels to transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0064] Channel estimates derived by a channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may assist the TX processor 268 in selecting the appropriate coding and modulation schemes, and in facilitating spatial processing. The spatial streams generated by the TX processor 268 may be transmitted to different antennas 252 via separate transmitters 254TX, with each transmitter modulating an RF carrier with its respective spatial stream. The UL transmission from each antenna 252 may be relayed through the satellite 270 via the service link and the feeder link to the base station 210. The UL transmission may be processed at the base station 210 in a similar manner to the receiver function at the UE 250, where each receiver 218RX may receive a signal through its respective antenna 220, may recover the modulated information, and may send it to the RX processor 270.
[0065] The controller / processor 275 may be linked to a memory 276 that may store program codes and data, with the memory 276 being referred to as a computer-readable medium. In the UL, the controller / processor 275 may manage demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the UE 250. These IP packets may then be forwarded to the EPC 160. The controller / processor 275 may also be responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0066] New Radio (NR) may refer to radios designed to operate on a new air interface (different from OFDMA-based interfaces) or a fixed transport layer (other than IP) . NR may use OFDM with a cyclic prefix (CP) on both the UL and DL, and may support half-duplex operation using time division duplexing (TDD) . NR may include services like Enhanced Mobile Broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or more) , mmWave for high carrier frequencies (e.g., 60 GHz) , massive Machine-Type Communications (mMTC) for non-backward compatible MTC techniques, and / or mission-critical communications targeting ultra-reliable low latency communications (URLLC) .
[0067] The NR RAN may include a central unit (CU) and distributed units (DUs) . A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP) ) may correspond to one or multiple BSs.
[0068] FIG. 3 depicts an exemplary IMS network architecture 300 in which the SDP pre-configuration procedures described herein may be applied. The IMS network architecture 300 includes a UE 302, a satellite 304, an eNB / NTN gateway 306, an Evolved Packet Core (EPC) 308, and an IMS network 316.
[0069] The UE 302 may communicate with the eNB / NTN gateway 306 via the satellite 304. The communication link between the UE 302 and the satellite 304 may be referred to as a service link, and the communication link between the satellite 304 and the eNB / NTN gateway 306 may be referred to as a feeder link. The satellite 304 may be a geostationary earth orbit (GEO) satellite, a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, or a high-altitude platform station (HAPS) . In some aspects, the UE 302 may communicate with the eNB / NTN gateway 306 via a non-terrestrial network (NTN) access, such as narrowband Internet of Things (NB-IoT) over a satellite link. In some other aspects, the UE 302 may communicate with the network via a terrestrial access link without involving a satellite.
[0070] The EPC 308 includes a Mobility Management Entity (MME) 310, a Serving Gateway (S-GW) 312, a Packet Data Network Gateway (P-GW) 314, and a Home Subscriber Server (HSS) 324. The eNB / NTN gateway 306 may connect to the MME 310 and the S-GW 312 for control plane and user plane signaling, respectively. The S-GW 312 may route user data traffic to the P-GW 314, which provides connectivity to external packet data networks including the IMS network 316. The MME 310 may communicate with the HSS 324 for subscriber authentication and mobility management.
[0071] The IMS network 316 includes a Proxy Call Session Control Function (P-CSCF) 318, an Interrogating Call Session Control Function (I-CSCF) 320, a Serving Call Session Control Function (S-CSCF) 322, and an Application Server (AS) 326. The P-CSCF 318 serves as the first point of contact for the UE 302 within the IMS network 316 and handles SIP signaling on behalf of the UE 302. The I-CSCF 320 may perform query functions to the HSS 324 and route SIP messages to the appropriate S-CSCF 322. The S-CSCF 322 may perform session control and registration functions, and may interact with the AS 326 for service execution. The S-CSCF 322 may also communicate with the HSS 324 for subscriber profile retrieval.
[0072] The UE 302 and the P-CSCF 318 may support an SDP pre-configuration procedure in which SDP parameters for media sessions are negotiated and stored prior to a call setup procedure. The UE 302 may include a feature tag in one or more SIP messages to indicate support for SDP pre-configuration. The P-CSCF 318 may likewise indicate support for SDP pre-configuration and may participate in the exchange of SDP parameters with the UE 302. The pre-configured SDP parameters may be stored at both the UE 302 and the P-CSCF 318, and may be used in one or more subsequent call setup procedures during the registration lifecycle of the UE 302. The SDP pre-configuration signaling path between the UE 302 and the P-CSCF 318 is shown in FIG. 3 as a dashed line.
[0073] Although FIG. 3 illustrates the IMS network architecture 300 in the context of an EPC-based network with NTN access, the technology described herein is not limited to this specific network configuration. For example, the techniques described herein may be applied in a 5G system architecture, in which the EPC 308 may be replaced by a 5GC network having an Access and Mobility Management Function (AMF) , a Session Management Function (SMF) , and a User Plane Function (UPF) , and the eNB / NTN gateway 306 may be replaced by a gNB / NTN gateway connected to the 5GC. The IMS network 316 and the SDP pre-configuration procedures between the UE 302 and the P-CSCF 318 may operate in the same manner regardless of whether the underlying access network and core network are based on 4G, 5G, or future generations of wireless communication systems such as 6G. Furthermore, the techniques described herein may be applicable to both terrestrial and non-terrestrial access scenarios, including satellite-based, airborne-based, and other non-terrestrial communication platforms that may be defined in future 3GPP or other standards.
[0074] In an EPS-based network, a default bearer is established when the UE establishes a PDN connection with the network. The default bearer provides basic connectivity with a non-guaranteed bit rate quality of service (QoS) . When a voice or multimedia session requires a dedicated QoS, such as a guaranteed bit rate for voice traffic, a dedicated Quality of Service (QoS) resource may be activated (or modified) between the UE and the P-GW 314 to carry the media traffic with the required QoS characteristics. The dedicated QoS resource is typically activated during the call setup procedure after the SDP parameters have been negotiated, because the SDP parameters (e.g., IP address, port number, and codec) determine the traffic flow template (TFT) and QoS parameters needed to configure the dedicated QoS resource.
[0075] As used herein, the term "dedicated Quality of Service (QoS) resource" refers to a network resource that provides dedicated QoS treatment for a media session. The dedicated QoS resource may encompass different mechanisms for providing dedicated QoS treatment in different network architectures, including but not limited to a dedicated EPS bearer in a 4G system, a QoS flow with a dedicated QoS rule in a 5G system, and similar QoS resource allocation mechanisms in future generations of wireless communication systems, which include a QoS resource providing dedicated QoS treatment for a media session in a 6G system or beyond
[0076] In a typical call setup procedure, the dedicated QoS resource activation occurs between the SIP INVITE message and the 183 Session Progress message, which adds additional latency to the call setup time. In NTN access scenarios where each signaling round trip may involve significant propagation delay, the in-call dedicated QoS resource activation may contribute substantially to the overall call setup time.
[0077] In accordance with the present disclosure, because the SDP parameters may be pre-configured prior to the call setup procedure, the dedicated QoS resource may be activated (or modified) based on the pre-configured SDP parameters after the SDP pre-configuration procedure is completed, and prior to any call setup procedure. By activating (or modifying) the dedicated QoS resource in advance, the call setup procedure may proceed without the additional latency associated with in-call dedicated QoS resource activation.
[0078] SDP Pre-Configuration Procedure
[0079] FIG. 4 depicts a signaling flow diagram illustrating a signaling flow 400 for an SDP pre-configuration procedure during a SIP registration procedure according to an embodiment of the present disclosure. The signaling flow can be applied between a UE 450 and a P-CSCF 470.
[0080] Prior to the signaling flow 400 shown in FIG. 4, the UE 450 is attached to an EPS network and has established an IMS PDN connection. Through the IMS PDN connection establishment procedure, the UE 450 may acquire an IP address and the address of the P-CSCF 470.
[0081] At step 401, the UE 450 sends a SIP REGISTER message to the P-CSCF 470. The SIP REGISTER message includes an SDP pre-config feature tag to indicate that the UE 450 supports the SDP pre-configuration procedure. The feature tag may be included in a header field of the SIP REGISTER message.
[0082] At step 402a, upon receiving the SIP REGISTER message, the P-CSCF 470 determines that the P-CSCF 470 also supports the SDP pre-configuration procedure and agrees to use the SDP pre-configuration mechanism. At step 402b, the P-CSCF 470 responds with a 401 Unauthorized message that also includes the SDP pre-config feature tag. The inclusion of the feature tag in the 401 Unauthorized message indicates to the UE 450 that the P-CSCF 470 supports and has agreed to perform the SDP pre-configuration procedure. Through the exchange of the feature tag in steps 401 and 402b, both the UE 450 and the P-CSCF 470 have confirmed mutual support for the SDP pre-configuration procedure.
[0083] At step 403a, the UE 450 prepares a second SIP REGISTER message carrying the media configurations of the UE 450. At step 403b, the UE 450 sends the SIP REGISTER message to the P-CSCF 470. The SIP REGISTER message includes an XML body containing the requested SDP parameters of the UE 450. The SDP parameters may include, for example, the IP address and port number of the UE 450 for voice Real-time Transport Protocol (RTP) transmission applicable to subsequent IMS calls, and the codec information of the UE 450, such as codec type, parameters, payload type, and ptime.
[0084] At step 404a, the P-CSCF 470 receives the SIP REGISTER message from the UE 450, saves the media configurations of the UE 450, and selects the final media configurations for the SDP pre-configuration. The P-CSCF 470 may select the media configurations based on network policy, available resources, or supported codec capabilities. At step 404b, the P-CSCF 470 responds with a 200 OK message that includes an XML body containing the media configurations selected by the P-CSCF 470. The media configurations selected by the P-CSCF 470 may include, for example, the IP address and port number of the P-CSCF 470 (or of a media gateway associated with the P-CSCF 470) for voice RTP, and the selected codec information applicable to subsequent IMS calls. At step 404c, the UE 450 receives the 200 OK message and saves the media configurations selected by the P-CSCF 470. At this point, the pre-configured SDP parameters are stored at both the UE 450 and the P-CSCF 470.
[0085] In some embodiments, upon completion of the SDP pre-configuration procedure, a dedicated QoS resource may be activated (or modified) based on the pre-configured SDP parameters. Because the SDP parameters, including IP address, port number, and codec, are already known at this stage, the dedicated QoS resource may be configured with the appropriate traffic flow template and QoS parameters without waiting for a call setup procedure to be initiated.
[0086] At step 405, subsequent call setup procedures may be performed using the pre-configured media configurations stored at both the UE 450 and the P-CSCF 470. In embodiments where the dedicated QoS resource has been activated after the SDP pre-configuration procedure, the call setup procedure may proceed without the additional latency associated with in-call dedicated QoS resource activation.
[0087] Because the SDP parameters have already been negotiated and stored during the SIP registration procedure, the subsequent call setup signaling may omit or reduce the SDP payload, thereby reducing the number of signaling messages, the message size, and the overall call setup time. The pre-configured media configurations may remain valid and be used for all IMS calls during the registration lifecycle of the UE 450, unless a re-registration or an explicit update to the SDP parameters is performed.
[0088] FIG. 5 depicts an exemplary XML body structure for the SDP pre-configuration procedure during a SIP registration procedure between a UE 550 and a P-CSCF 570 according to an embodiment of the present disclosure.
[0089] The signaling flow 500 shown in FIG. 5 corresponds to a more detailed example of the SDP pre-configuration procedure described with reference to FIG. 4. At step 501, the UE 550 sends a SIP REGISTER message to the P-CSCF 570 including an SDP pre-config feature tag. At step 502, the P-CSCF 570 responds with a 401 Unauthorized message including the SDP pre-config feature tag, indicating mutual support for the SDP pre-configuration procedure. Steps 501 and 502 correspond to steps 401 and 402b of FIG. 4, respectively.
[0090] At step 503, the UE 550 sends a SIP REGISTER message to the P-CSCF 570 including an XML body that contains the SDP parameters of the UE 550. The XML body may be structured in accordance with an IMS 3GPP XML schema (e.g., "ims-3gpp version 2" ) and may include an sdp-pre-config element encapsulating the SDP parameters. In the example shown in FIG. 5, the XML body includes a state element set to "register"indicating that the SDP pre-configuration is being performed during the registration procedure. The SDP parameters of the UE 550 included in the XML body at step 503 may include, for example:
[0091] a connection information field (c=) indicating the IP address of the UE 550 for media transport (e.g., "IN IP4 10.0.0.1" ) ;
[0092] a media description field (m=) indicating the media type, port number, transport protocol, and supported payload types (e.g., "audio 45912 RTP / AVP 96 97, " indicating an audio media stream on port 45912 using RTP with Audio Video Profile, supporting payload types 96 and 97) ;
[0093] one or more attribute fields (a=) specifying the codec mapping for each payload type (e.g., "rtpmap: 96 codec2 / 8000" indicating that payload type 96 corresponds to the Codec2 codec at a sampling rate of 8000 Hz, and "rtpmap: 97 AMR / 8000" indicating that payload type 97 corresponds to the Adaptive Multi-Rate (AMR) codec at a sampling rate of 8000 Hz) ;
[0094] one or more format parameter fields (a=fmtp) specifying codec-specific parameters (e.g., "fmtp: 96 br=0.7" indicating a bit rate of 0.7 kbps for the Codec2 codec, and "fmtp: 97 mode-change-capability=2" indicating AMR mode change capability) ; and
[0095] a packetization time field (a=ptime) indicating the duration of media carried in each RTP packet (e.g., "ptime: 80" indicating 80 milliseconds per packet) .
[0096] At step 504, the P-CSCF 570 responds with a 200 OK message including an XML body that contains the SDP parameters selected by the P-CSCF 570. The XML body of the 200 OK message may use the same IMS 3GPP XML schema and may include an sdp-pre-config element with a state element set to "registered" indicating that the SDP pre-configuration has been completed. In the example shown in FIG. 5, the P-CSCF 570 has selected a subset of the codec options proposed by the UE 550 at step 503. Specifically, the P-CSCF 570 has selected payload type 96 (Codec2 at 8000 Hz with a bit rate of 0.7 kbps) and has not included payload type 97 (AMR) , indicating that the AMR codec was not selected for subsequent calls. The SDP parameters selected by the P-CSCF 570 may further include the IP address of the P-CSCF 570 or of a media gateway associated with the P-CSCF 570 (e.g., "IN IP4 10.0.0.254" ) , a port number for media transport (e.g., port 60998) , and the packetization time (e.g., "ptime: 80" ) .
[0097] At step 505, subsequent call setup procedures may be performed using the pre-configured media configurations determined at steps 503 and 504. In some embodiments, a dedicated QoS resource may be activated (or modified) based on the pre-configured SDP parameters after step 504 and prior to any call setup procedure. For example, the pre-configured IP addresses, port numbers, and codec selection may be used to configure the traffic flow template and QoS parameters for the dedicated QoS resource.
[0098] Because the SDP parameters, including IP addresses, port numbers, codec selection, and packetization time, have already been negotiated and stored at both the UE 550 and the P-CSCF 570, the subsequent IMS call setup signaling may reference or use these pre-configured parameters without performing a full SDP offer / answer exchange.
[0099] The specific XML schema, element names, SDP parameter values, codec types, and port numbers shown in FIG. 5 are exemplary and may vary depending on the implementation, network configuration, and codec capabilities supported by the UE 550 and the P-CSCF 570.
[0100] FIG. 6 depicts a signaling flow diagram illustrating a signaling flow 600 for an SDP pre-configuration procedure using a pre-call SIP message flow according to an embodiment of the present disclosure. The signaling flow can be applied between a UE 650 and a P-CSCF 670.
[0101] Prior to the signaling flow 600 shown in FIG. 6, the UE 650 is attached to an EPS network, has established an IMS PDN connection, and has completed IMS registration. During the SIP registration procedure, the UE 650 and the P-CSCF 670 may have exchanged the SDP pre-config feature tag to indicate mutual support for the SDP pre-configuration procedure, as described with reference to steps 401 and 402b of FIG. 4.
[0102] At step 601, the UE 650 sends a SIP message to the P-CSCF 670 for the purpose of performing the SDP pre-configuration procedure. The SIP message may be a SIP INFO message, a SIP OPTIONS message, or a SIP INVITE message. The SIP message includes an SDP pre-config feature tag to indicate that the purpose of the message is to perform the SDP pre-configuration procedure, and an SDP offer containing the requested SDP parameters of the UE 650. The SDP parameters may include, for example, the IP address and port number of the UE 650 for voice RTP transmission, and the codec information of the UE 650, such as codec type, parameters, payload type, and ptime.
[0103] At step 602a, the P-CSCF 670 receives the SIP message from the UE 650, agrees to use the SDP pre-configuration mechanism, and selects the final media configurations based on the SDP offer from the UE 650. The P-CSCF 670 constructs a 200 OK message containing an SDP answer with the media configurations selected by the P-CSCF 670. At step 602b, the P-CSCF 670 sends the 200 OK message to the UE 650.
[0104] At step 602c, the UE 650 receives the 200 OK message and saves the media configurations selected by the P-CSCF 670. At this point, the pre-configured SDP parameters are stored at both the UE 650 and the P-CSCF 670. In some embodiments, upon completion of the SDP pre-configuration procedure, a dedicated QoS resource may be activated (or modified) based on the pre-configured SDP parameters. Because the SDP parameters, including IP address, port number, and codec, are already known at this stage, the dedicated QoS resource may be configured with the appropriate traffic flow template and QoS parameters without waiting for a call setup procedure to be initiated.
[0105] At step 602d, when the SDP pre-configuration procedure is performed using a SIP INVITE message, the UE 650 may send an ACK message to the P-CSCF 670 to complete the SIP INVITE transaction. When the SDP pre-configuration procedure is performed using a SIP INFO or SIP OPTIONS message, the ACK message may not be required.
[0106] At step 603, subsequent call setup procedures may be performed using the pre-configured media configurations stored at both the UE 650 and the P-CSCF 670. In embodiments where the dedicated QoS resource has been activated (or modified) after the SDP pre-configuration procedure, the call setup procedure may proceed without the additional latency associated with in-call dedicated QoS resource activation. Because the SDP parameters have already been negotiated and stored during the pre-call SIP message exchange, the subsequent call setup signaling may omit or reduce the SDP payload, thereby reducing the number of signaling messages, the message size, and the overall call setup time. The pre-configured media configurations may remain valid and be used for all IMS calls during the registration lifecycle of the UE 650, unless a re-registration or an explicit update to the SDP parameters is performed.
[0107] The SDP pre-configuration procedure using a pre-call SIP message flow as shown in FIG. 6 may be advantageous in scenarios where decoupling the SDP pre-configuration from the SIP registration procedure is preferred. For example, if the SIP registration procedure fails, the SDP pre-configuration may be performed independently through a subsequent pre-call SIP message after a successful re-registration. Additionally, the pre-call SIP message flow may be extended to support modification of previously pre-configured media configurations by initiating a new pre-call SIP message exchange with updated SDP parameters.
[0108] FIG. 7 depicts an exemplary SDP offer and answer exchange for the SDP pre-configuration procedure using a pre-call SIP message flow between a UE 750 and a P-CSCF 770 according to an embodiment of the present disclosure.
[0109] The signaling flow 700 shown in FIG. 7 corresponds to a more detailed example of the SDP pre-configuration procedure described with reference to FIG. 6. Prior to the signaling flow shown in FIG. 7, the UE 750 has completed IMS registration and both the UE 750 and the P-CSCF 770 have confirmed mutual support for the SDP pre-configuration procedure.
[0110] At step 701, the UE 750 sends a SIP message to the P-CSCF 770. The SIP message may be a SIP OPTIONS message, a SIP INFO message, or a SIP INVITE message. The SIP message includes an SDP offer containing the SDP parameters of the UE 750. In the example shown in FIG. 7, the SDP offer includes the following parameters:
[0111] a connection information field (c=) indicating the IP address of the UE 750 for media transport (e.g., "IN IP4 10.0.0.1" ) ;
[0112] a media description field (m=) indicating the media type, port number, transport protocol, and supported payload types (e.g., "audio 45912 RTP / AVP 96 97, " indicating an audio media stream on port 45912 using RTP with Audio Video Profile, supporting payload types 96 and 97) ;
[0113] one or more attribute fields (a=) specifying the codec mapping for each payload type (e.g., "rtpmap: 96 codec2 / 8000" indicating that payload type 96 corresponds to the Codec2 codec at a sampling rate of 8000 Hz, and "rtpmap: 97 AMR / 8000" indicating that payload type 97 corresponds to the AMR codec at a sampling rate of 8000 Hz) ;
[0114] one or more format parameter fields (a=fmtp) specifying codec-specific parameters (e.g., "fmtp: 96 br=0.7" indicating a bit rate of 0.7 kbps for the Codec2 codec, and "fmtp: 97 mode-change-capability=2" indicating AMR mode change capability) ; and
[0115] a packetization time field (a=ptime) indicating the duration of media carried in each RTP packet (e.g., "ptime: 80" indicating 80 milliseconds per packet) .
[0116] At step 702a, the P-CSCF 770 responds with a 200 OK message including an SDP answer containing the SDP parameters selected by the P-CSCF 770. In the example shown in FIG. 7, the P-CSCF 770 has selected a subset of the codec options proposed by the UE 750 at step 701. Specifically, the P-CSCF 770 has selected payload type 96 (Codec2 at 8000 Hz with a bit rate of 0.7 kbps) and has not included payload type 97 (AMR) , indicating that the AMR codec was not selected for subsequent calls. The SDP answer further includes the IP address of the P-CSCF 770 or of a media gateway associated with the P-CSCF 770 (e.g., "IN IP4 10.0.0.254" ) , a port number for media transport (e.g., port 60998) , and the packetization time (e.g., "ptime: 80" ) . At this point, the pre-configured SDP parameters are stored at both the UE 750 and the P-CSCF 770. In some embodiments, upon completion of the SDP pre-configuration procedure, a dedicated QoS resource may be activated (or modified) based on the pre-configured SDP parameters without waiting for a call setup procedure to be initiated.
[0117] At step 702b, when the SDP pre-configuration procedure is performed using a SIP INVITE message, the UE 750 may send an ACK message to the P-CSCF 770 to complete the SIP INVITE transaction. Step 702b is shown as a dashed line in FIG. 7 to indicate that this step may be conditional on the type of SIP message used at step 701. When the SDP pre-configuration procedure is performed using a SIP OPTIONS or SIP INFO message, the ACK message may not be required.
[0118] At step 703, subsequent call setup procedures may be performed using the pre-configured media configurations stored at both the UE 750 and the P-CSCF 770. In embodiments where the dedicated QoS resource has been activated after the SDP pre-configuration procedure, the call setup procedure may proceed without the additional latency associated with in-call dedicated QoS resource activation.
[0119] The SDP parameters shown in FIG. 7 are carried as a standard SDP body within the SIP message, in contrast to the XML-based structure shown in FIG. 5 for the registration-based embodiment. Both formats may be used to convey the SDP parameters depending on the SIP message type and network implementation. The specific SDP parameter values, codec types, and port numbers shown in FIG. 7 are exemplary and may vary depending on the implementation, network configuration, and codec capabilities supported by the UE 750 and the P-CSCF 770.
[0120] Call Setup Procedure with SDP Pre-Configuration
[0121] FIG. 8 depicts a signaling flow diagram illustrating a signaling flow 800 for a mobile-originated (MO) call setup procedure with SDP pre-configuration according to an embodiment of the present disclosure. The signaling flow 800 can be applied between a UE 850, an NB-RAN 852, an MME 854, an SGW / PGW 856, a PCRF 858, a P-CSCF 870, and an IMS Core 880.
[0122] Prior to the signaling flow 800 shown in FIG. 8, the UE 850 has registered with IMS and has completed the SDP pre-configuration procedure with the P-CSCF 870 by either the registration-based procedure described in FIG. 4 and FIG. 5, or the pre-call SIP message flow described in FIG. 6 and FIG. 7, or by using pre-defined SDP parameters. The pre-configured SDP parameters can be stored at both the UE 850 and the P-CSCF 870.
[0123] At step 801a, the UE 850 initiates an IMS call via GEO satellite access. At step 801b, the UE 850 sends a SIP INVITE message to the P-CSCF 870 via the NB-RAN 852. The SIP INVITE message may be sent without an SDP body or with pre-configured SDP. When the SIP INVITE message is sent without an SDP body, the message size is reduced compared to a conventional call setup procedure in which a full SDP offer is included. When the SIP INVITE message is sent with pre-configured SDP, the UE 850 includes one or more SDP parameters having values equal to the pre-configured SDP parameter values determined during the SDP pre-configuration procedure, such as IP address, port number, codec parameters, and ptime.
[0124] At step 802, the P-CSCF 870 receives the SIP INVITE message from the UE 850 and restores the SDP offer based on the stored SDP pre-configuration. When the SIP INVITE message was received without an SDP body, the P-CSCF 870 constructs a full SDP offer on behalf of the UE 850 using the pre-configured SDP parameters stored at the P-CSCF 870. When the SIP INVITE message was received with pre-configured SDP, the P-CSCF 870 may verify the SDP parameters against the stored pre-configuration and complete the SDP offer as needed.
[0125] At step 803, the P-CSCF 870 forwards the SIP INVITE message with the restored SDP offer to the IMS Core 880. At step 804, the IMS Core 880 responds with a 100 Trying message to the P-CSCF 870.
[0126] At step 805, the IMS Core 880 sends a 183 Session Progress message with an SDP answer to the P-CSCF 870.
[0127] At step 806, a dedicated QoS resource activation procedure may optionally be performed. The dedicated QoS resource activation at step 806 may involve signaling between the PCRF 858, the SGW / PGW 856, the MME 854, and the NB-RAN 852 to establish a bearer with appropriate QoS characteristics for the voice media session. Step 806 is shown as a dashed box in FIG. 8 to indicate that this step is optional and based on operator policy.
[0128] At step 807, the P-CSCF 870 sends a Provisional Response Acknowledgement (PRACK) message to the IMS Core 880 to acknowledge receipt of the 183 Session Progress message. At step 808, the IMS Core 880 responds with a SIP 200 OK message for the PRACK.
[0129] At step 808a, the P-CSCF 870 sends an UPDATE message to the IMS Core 880. At step 808b, the IMS Core 880 responds with a SIP 200 OK message for the UPDATE.
[0130] At step 809a, the IMS Core 880 sends a 180 Ringing message to the P-CSCF 870. At step 809b, the P-CSCF 870 forwards the 180 Ringing message to the UE 850. The 180 Ringing message forwarded to the UE 850 may be sent without an SDP answer or with the pre-configured SDP answer. When the UE 850 sent the SIP INVITE with pre-configured SDP at step 801b, the P-CSCF 870 may restore the SDP answer in the 180 Ringing message before forwarding to the UE 850.
[0131] At step 810a, the remote peer picks up the call. At step 810b, the IMS Core 880 sends a SIP 200 OK message for the INVITE to the P-CSCF 870. At step 810c, the P-CSCF 870 forwards the SIP 200 OK message to the UE 850.
[0132] At step 811a, the UE 850 sends an ACK message to the P-CSCF 870. At step 811b, the P-CSCF 870 forwards the ACK message to the IMS Core 880.
[0133] At step 812, the media paths between the UE 850 and the IMS Core 880 have been established, and voice packet transfer begins.
[0134] By applying the SDP pre-configuration procedure described herein, the MO call setup procedure shown in FIG. 8 may achieve a significant reduction in signaling message size and call setup time compared to a conventional MO call setup procedure. In a conventional procedure, the SIP INVITE message at step 801b would carry a full SDP offer, and additional signaling messages such as 100 Trying, 183 Session Progress, PRACK, and UPDATE would need to be exchanged over the NTN access link between the UE 850 and the P-CSCF 870. With the SDP pre-configuration applied, many of these signaling exchanges between the UE 850 and the P-CSCF 870 may be reduced or eliminated, because the P-CSCF 870 can restore the SDP parameters and handle the signaling with the IMS Core 880 on behalf of the UE 850.
[0135] FIG. 9 depicts a signaling flow diagram illustrating a signaling flow 900 for a mobile-originated (MO) call setup procedure with SDP pre-configuration and early dedicated QoS resource activation according to an embodiment of the present disclosure. The signaling flow 900 can be applied between a UE 950, an NB-RAN 952, an MME 954, an SGW / PGW 956, a PCRF 958, a P-CSCF 970, and an IMS Core 980.
[0136] Prior to the signaling flow 900 shown in FIG. 9, the UE 950 has registered with IMS and has completed the SDP pre-configuration procedure with the P-CSCF 970 by either the registration-based procedure described with reference to FIG. 4 and FIG. 5, or the pre-call SIP message flow described with reference to FIG. 6 and FIG. 7, or by using pre-defined SDP parameters. The pre-configured SDP parameters are stored at both the UE 950 and the P-CSCF 970. Furthermore, a dedicated QoS resource has been activated based on the pre-configured SDP parameters after completion of the SDP pre-configuration procedure and prior to the call setup procedure shown in FIG. 9. Because the SDP parameters, including IP address, port number, and codec, were already known upon completion of the SDP pre-configuration procedure, the dedicated QoS resource was configured with the appropriate traffic flow template and QoS parameters without waiting for a call setup procedure to be initiated.
[0137] At step 901a, the UE 950 initiates an IMS call via GEO satellite access. At step 901b, the UE 950 sends a SIP INVITE message without an SDP body to the P-CSCF 970 via the NB-RAN 952. Because the SDP parameters have been pre-configured and the dedicated QoS resource has been activated prior to the call setup, the SIP INVITE message does not need to carry an SDP body, thereby significantly reducing the message size compared to a conventional call setup procedure.
[0138] At step 902, the P-CSCF 970 receives the SIP INVITE message from the UE 950 and restores the SDP offer based on the stored SDP pre-configuration. Because the SIP INVITE message was received without an SDP body, the P-CSCF 970 constructs a full SDP offer on behalf of the UE 950 using the pre-configured SDP parameters stored at the P-CSCF 970.
[0139] At step 903, the P-CSCF 970 forwards the SIP INVITE message with the restored SDP offer to the IMS Core 980. At step 904, the IMS Core 980 responds with a 100 Trying message to the P-CSCF 970.
[0140] At step 905, the IMS Core 980 sends a 183 Session Progress message with an SDP answer to the P-CSCF 970.
[0141] At step 906a, the P-CSCF 970 sends a PRACK message to the IMS Core 980 to acknowledge receipt of the 183 Session Progress message. At step 906b, the IMS Core 980 responds with a SIP 200 OK message for the PRACK.
[0142] At step 907a, the IMS Core 980 sends an UPDATE message to the P-CSCF 970. At step 907b, the P-CSCF 970 responds with a SIP 200 OK message for the UPDATE.
[0143] At step 908a, the IMS Core 980 sends a 180 Ringing message to the P-CSCF 970. At step 908b, the P-CSCF 970 forwards the 180 Ringing message to the UE 950.
[0144] At step 909a, the remote peer picks up the call. At step 909b, the IMS Core 980 sends a SIP 200 OK message for the INVITE to the P-CSCF 970. At step 910c, the P-CSCF 970 forwards the SIP 200 OK message to the UE 950.
[0145] At step 910a, the UE 950 sends an ACK message to the P-CSCF 970. At step 910b, the P-CSCF 970 forwards the ACK message to the IMS Core 980.
[0146] At step 911, the media paths between the UE 950 and the IMS Core 980 have been established, and voice packet transfer begins.
[0147] Compared to the MO call setup procedure shown in FIG. 8, the signaling flow 900 in FIG. 9 does not include the optional dedicated bearer activation step (step 806 in FIG. 8) during the call setup procedure, because the dedicated QoS resource has already been activated prior to the call setup based on the pre-configured SDP parameters. This eliminates the latency associated with in-call dedicated QoS resource activation, which may contribute a few seconds of additional delay in NTN access scenarios. Additionally, because the INVITE message at step 901b is sent without an SDP body, the signaling exchanged over the NTN access link between the UE 950 and the P-CSCF 970 is further reduced. The combination of SDP pre-configuration and early dedicated QoS resource activation may result in a significantly shorter call setup time, bringing the call setup experience within the acceptable threshold for user experience in NTN access scenarios.
[0148] FIG. 10 depicts a signaling flow diagram illustrating a signaling flow 1000 for a mobile-terminated (MT) call setup procedure with SDP pre-configuration according to an embodiment of the present disclosure. The signaling flow 1000 can be applied between a UE 1050, an NB-RAN 1052, an MME 1054, an SGW / PGW 1056, a PCRF 1058, a P-CSCF 1070, and an IMS Core 1080.
[0149] Prior to the signaling flow 1000 shown in FIG. 10, the UE 1050 has registered with IMS and has completed the SDP pre-configuration procedure with the P-CSCF 1070 by either the registration-based procedure described with reference to FIG. 4 and FIG. 5, or the pre-call SIP message flow described with reference to FIG. 6 and FIG. 7, or by using pre-defined SDP parameters. The pre-configured SDP parameters are stored at both the UE 1050 and the P-CSCF 1070.
[0150] At step 1001, the IMS Core 1080 sends a SIP INVITE message with an SDP offer to the P-CSCF 1070 to initiate a mobile-terminated call to the UE 1050.
[0151] At step 1002a, the P-CSCF 1070 receives the SIP INVITE message from the IMS Core 1080 and removes the SDP offer from the INVITE message. Because the SDP parameters have been pre-configured and stored at both the UE 1050 and the P-CSCF 1070, the P-CSCF 1070 does not need to forward the full SDP offer to the UE 1050 over the NTN access link. At step 1002b, the P-CSCF 1070 forwards the INVITE message to the UE 1050 without the SDP offer or with the pre-configured SDP offer. When the INVITE is forwarded without the SDP offer, the message size is reduced compared to a conventional MT call setup in which the full SDP offer would be transmitted over the NTN access link. When the INVITE is forwarded with the pre-configured SDP offer, the P-CSCF 1070 replaces the SDP offer received from the IMS Core 1080 with the pre-configured SDP parameters stored at the P-CSCF 1070.
[0152] At step 1003, the P-CSCF 1070 sends a 100 Trying message to the IMS Core 1080.
[0153] At step 1004, the P-CSCF 1070 restores the SDP answer based on the stored SDP pre-configuration. The P-CSCF 1070 constructs the SDP answer on behalf of the UE 1050 using the pre-configured SDP parameters, without waiting for the UE 1050 to generate and transmit an SDP answer over the NTN access link. At step 1005, the P-CSCF 1070 sends a 183 Session Progress message with the restored SDP answer to the IMS Core 1080.
[0154] At step 1006, a network-initiated dedicated bearer activation procedure may optionally be performed. The dedicated QoS resource activation at step 1006 may involve signaling between the PCRF 1058, the SGW / PGW 1056, the MME 1054, and the NB-RAN 1052 to establish a bearer with appropriate QoS characteristics for the voice media session. Step 1006 is shown as a dashed box in FIG. 10 to indicate that this step is optional and based on operator policy. In some embodiments, the dedicated QoS resource may have been activated based on the pre-configured SDP parameters after completion of the SDP pre-configuration procedure and prior to the call setup procedure, in which case step 1006 may be skipped.
[0155] At step 1007, the IMS Core 1080 sends a PRACK message to the P-CSCF 1070 to acknowledge receipt of the 183 Session Progress message. At step 1008, the P-CSCF 1070 responds with a SIP 200 OK message for the PRACK.
[0156] At step 1009a, the P-CSCF 1070 sends a 180 Ringing message to the UE 1050. The 180 Ringing message may be sent without an SDP answer or with the pre-configured SDP answer. When the P-CSCF 1070 forwarded the INVITE with the pre-configured SDP offer to the UE 1050 at step 1002b, the UE 1050 may send the 180 Ringing with an SDP answer to the P-CSCF 1070. At step 1009b, the P-CSCF 1070 forwards the 180 Ringing message to the IMS Core 1080.
[0157] At step 1010a, the UE 1050 picks up the call. At step 1010b, the UE 1050 sends a SIP 200 OK message for the INVITE to the P-CSCF 1070. At step 1010c, the P-CSCF 1070 forwards the SIP 200 OK message to the IMS Core 1080.
[0158] At step 1011a, the IMS Core 1080 sends an ACK message to the P-CSCF 1070. At step 1011b, the P-CSCF 1070 forwards the ACK message to the UE 1050.
[0159] At step 1012, the media paths between the UE 1050 and the IMS Core 1080 have been established, and voice packet transfer begins.
[0160] In the MT call setup procedure shown in FIG. 10, the P-CSCF 1070 plays a central role in reducing the signaling exchanged over the NTN access link. By removing or replacing the SDP offer at step 1002a before forwarding the INVITE to the UE 1050, and by restoring the SDP answer at step 1004 on behalf of the UE 1050, the P-CSCF 1070 handles the SDP negotiation with the IMS Core 1080 without requiring the UE 1050 to participate in the full SDP offer / answer exchange over the high-latency NTN access link. This may result in a significant reduction in both the number of signaling round trips and the message size exchanged over the NTN access link, thereby reducing the overall call setup time for mobile-terminated calls.
[0161] FIG. 11 depicts a signaling flow diagram illustrating a signaling flow 1100 for a mobile-terminated (MT) call setup procedure with SDP pre-configuration and early dedicated QoS resource activation according to an embodiment of the present disclosure. The signaling flow 1100 can be applied between a UE 1150, an NB-RAN 1152, an MME 1154, an SGW / PGW 1156, a PCRF 1158, a P-CSCF 1170, and an IMS Core 1180.
[0162] Prior to the signaling flow 1100 shown in FIG. 11, the UE 1150 has registered with IMS and has completed the SDP pre-configuration procedure with the P-CSCF 1170 by either the registration-based procedure described with reference to FIG. 4 and FIG. 5, or the pre-call SIP message flow described with reference to FIG. 6 and FIG. 7, or by using pre-defined SDP parameters. The pre-configured SDP parameters are stored at both the UE 1150 and the P-CSCF 1170. Furthermore, a dedicated QoS resource has been activated based on the pre-configured SDP parameters after completion of the SDP pre-configuration procedure and prior to the call setup procedure shown in FIG. 11.
[0163] At step 1101, the IMS Core 1180 sends a SIP INVITE message with an SDP offer to the P-CSCF 1170 to initiate a mobile-terminated call to the UE 1150.
[0164] At step 1102a, the P-CSCF 1170 receives the SIP INVITE message from the IMS Core 1180 and removes the SDP offer from the INVITE message. Because the SDP parameters have been pre-configured and the dedicated QoS resource has been activated prior to the call setup, the P-CSCF 1170 does not need to forward the SDP offer to the UE 1150 over the NTN access link. At step 1102b, the P-CSCF 1170 forwards the INVITE message to the UE 1150 without the SDP. Because the dedicated QoS resource has already been activated, there is no need to include the SDP offer in the forwarded INVITE message for the purpose of bearer activation or QoS configuration at the UE 1150 side.
[0165] At step 1103, the P-CSCF 1170 sends a 100 Trying message to the IMS Core 1180.
[0166] At step 1104, the P-CSCF 1170 restores the SDP answer based on the stored SDP pre-configuration. The P-CSCF 1170 constructs the SDP answer on behalf of the UE 1150 using the pre-configured SDP parameters, without waiting for the UE 1150 to generate and transmit an SDP answer over the NTN access link. At step 1105, the P-CSCF 1170 sends a 183 Session Progress message with the restored SDP answer to the IMS Core 1180.
[0167] At step 1106a, the IMS Core 1180 sends a PRACK message to the P-CSCF 1170 to acknowledge receipt of the 183 Session Progress message. At step 1106b, the P-CSCF 1170 forwards the PRACK to the IMS Core 1180 and receives a SIP 200 OK message for the PRACK.
[0168] At step 1107a, the IMS Core 1180 sends an UPDATE message to the P-CSCF 1170. At step 1107b, the P-CSCF 1170 responds with a SIP 200 OK message for the UPDATE.
[0169] At step 1108a, the P-CSCF 1170 sends a 180 Ringing message to the UE 1150. At step 1108b, the P-CSCF 1170 forwards the 180 Ringing message to the IMS Core 1180.
[0170] At step 1109a, the UE 1150 picks up the call. At step 1109b, the UE 1150 sends a SIP 200 OK message for the INVITE to the P-CSCF 1170. At step 1109c, the P-CSCF 1170 forwards the SIP 200 OK message to the IMS Core 1180.
[0171] At step 1110a, the IMS Core 1180 sends an ACK message to the P-CSCF 1170. At step 1110b, the P-CSCF 1170 forwards the ACK message to the UE 1150.
[0172] At step 1111, the media paths between the UE 1150 and the IMS Core 1180 have been established, and voice packet transfer begins.
[0173] Compared to the MT call setup procedure shown in FIG. 10, the signaling flow 1100 in FIG. 11 does not include the optional dedicated bearer activation step (step 1006 in FIG. 10) during the call setup procedure, because the dedicated QoS resource has already been activated prior to the call setup based on the pre-configured SDP parameters. Additionally, at step 1102b the INVITE is forwarded to the UE 1150 without the SDP, whereas in FIG. 10 at step 1002b the INVITE may be forwarded without the SDP offer or with the pre-configured SDP offer. Because the dedicated QoS resource has been activated in advance in the embodiment of FIG. 11, there is no need to include the SDP offer in the forwarded INVITE for bearer or QoS configuration purposes, further simplifying the signaling over the NTN access link. The combination of SDP pre-configuration and early dedicated QoS resource activation may result in a significantly shorter call setup time for mobile-terminated calls in NTN access scenarios.
[0174] Methods Performed by UE and Network Entity
[0175] FIG. 12 depicts a flow diagram of a method 1200 performed by a UE for communicating with a network entity according to an embodiment of the present disclosure. The method 1200 may be performed by a UE such as the UE 302 described with reference to FIG. 3, and the network entity may be a P-CSCF such as the P-CSCF 318 described with reference to FIG. 3. The method includes the following steps:
[0176] S1210: Perform an SDP pre-configuration procedure with the network entity by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;
[0177] S1220: Store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure; and
[0178] S1230: Initiate a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter.
[0179] At step S1210, the UE performs an SDP pre-configuration procedure with the network entity by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. The SDP pre-configuration procedure may be performed in several ways. In one embodiment, the SDP pre-configuration procedure is performed during a SIP registration procedure (see FIG. 4 and FIG. 5) , in which the UE transmits a SIP REGISTER message having a feature tag indicating support for the SDP pre-configuration procedure and receives a response message having at least one SDP parameter selected by the network entity. The SDP parameters may be carried in an XML body within the SIP REGISTER message. In another embodiment, the SDP pre-configuration procedure is performed after a SIP registration procedure and prior to the specific call setup procedure, by transmitting a SIP message such as a SIP OPTIONS, SIP INFO, or SIP INVITE message (see FIG. 6 and FIG. 7) . In yet another embodiment, the SDP parameters may be pre-defined parameters agreed upon between the UE and the network entity.
[0180] At step S1220, the UE stores at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The SDP parameters may include, for example, an IP address, a port number, a codec parameter, or a ptime value. The stored SDP parameters may remain valid and be applicable to all subsequent call setup procedures during a registration lifecycle of the UE. The SDP parameters are stored at both the UE and the network entity, such that both sides may reference the pre-configured SDP parameters in subsequent call setup procedures.
[0181] At step S1230, the UE initiates a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter. For mobile-originated calls, the UE may transmit a SIP INVITE message without an SDP body (see step 901b of FIG. 9) , in which case the network entity restores the stored SDP parameters and constructs a full SDP offer on behalf of the UE. Alternatively, the UE may transmit a SIP INVITE message with pre-configured SDP (see step 801b of FIG. 8) , in which the UE includes one or more SDP parameters having values equal to the pre-configured values. For mobile-terminated calls, the network entity may remove or replace the SDP offer in a received SIP INVITE message based on the stored SDP parameters before forwarding to the UE (see steps 1002a and 1002b of FIG. 10) . By using the stored SDP parameters, the signaling message size and the number of signaling exchanges over the NTN access link may be significantly reduced, thereby reducing the overall call setup time. FIG. 13 depicts a flow diagram of a method 1300 performed by a UE for communicating with a network entity according to an embodiment of the present disclosure. The method 1300 may be performed by a UE such as the UE 302 described with reference to FIG. 3, and the network entity may be a P-CSCF such as the P-CSCF 318 described with reference to FIG. 3. The method 1300 is similar to the method 1200 described with reference to FIG. 12, with the addition of a dedicated QoS resource activation step prior to initiating the call setup procedure. The method includes the following steps:
[0182] S1310: Perform an SDP pre-configuration procedure with the network entity by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;
[0183] S1320: Store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;
[0184] S1330: Trigger activation or modification of a dedicated QoS resource based on the at least one stored SDP parameter; and
[0185] S1340: In response to the activation or modification of the dedicated QoS resource, initiating a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource.
[0186] At step S1310, the UE performs an SDP pre-configuration procedure with the network entity by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. Step S1310 may be performed in the same manner as step S1210 of FIG. 12.
[0187] At step S1320, the UE stores at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. Step S1320 may be performed in the same manner as step S1220 of FIG. 12.
[0188] At step S1330, the UE triggers activation (or modification) of a dedicated QoS resource based on the at least one stored SDP parameter. Because the SDP parameters are already known upon completion of the SDP pre-configuration procedure, the dedicated QoS resource may be configured with the appropriate traffic flow template and QoS parameters without waiting for a call setup procedure to be initiated. The dedicated QoS resource may be activated in response to completing the SDP pre-configuration procedure. The dedicated QoS resource may comprise a dedicated bearer, such as a dedicated EPS bearer in a 4G system, a QoS flow with a dedicated QoS rule in a 5G system, or similar QoS resource allocation mechanisms in future generations of wireless communication systems. Activating the dedicated QoS resource prior to the call setup procedure eliminates the latency associated with in-call activation, which may contribute approximately five seconds of additional delay in NTN access scenarios.
[0189] At step S1340, in response to the activation or modification of the dedicated QoS resource at step S1330, the UE initiates a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource. Because both the SDP parameters have been pre-configured and the dedicated QoS resource has been activated, the UE may transmit a SIP INVITE message without an SDP body. The network entity may then restore the stored SDP parameters and construct a full SDP offer on behalf of the UE. For mobile-terminated calls, the network entity may remove the SDP offer from a received SIP INVITE message and forward the INVITE to the UE without SDP, because the dedicated QoS resource has already been activated and there is no need to include the SDP offer for QoS configuration purposes. The detailed signaling flows for the MO and MT call setup procedures with early dedicated QoS resource activation are illustrated in FIG. 9 and FIG. 11, respectively. Compared to the method 1200 of FIG. 12, the method 1300 may achieve a further reduction in call setup time by eliminating the in-call dedicated QoS resource activation step.
[0190] FIG. 14 depicts a flow diagram of a method 1400 performed by a network entity for communicating with a UE according to an embodiment of the present disclosure. The network entity may be a P-CSCF such as the P-CSCF 318 of FIG. 3, and the UE may be the UE 302 of FIG. 3. The method includes the following steps:
[0191] S1410: Perform an SDP pre-configuration procedure with the UE by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;
[0192] S1420: Store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure; and
[0193] S1430: Receive a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed based on the at least one stored SDP parameter.
[0194] At step S1410, the network entity performs an SDP pre-configuration procedure with the UE by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. In one embodiment, the SDP pre-configuration procedure is performed during a SIP registration procedure (see FIG. 4 and FIG. 5) , in which the network entity receives a SIP REGISTER message from the UE having a feature tag indicating support for the SDP pre-configuration procedure, responds with a message including a feature tag confirming mutual support, receives a subsequent SIP REGISTER message containing the SDP parameters of the UE, and responds with the SDP parameters selected by the network entity. In another embodiment, the SDP pre-configuration procedure is performed after a SIP registration procedure by receiving a dedicated SIP message from the UE, such as a SIP OPTIONS, SIP INFO, or SIP INVITE message, containing an SDP offer (see FIG. 6 and FIG. 7) . The network entity selects the final SDP parameters and responds with an SDP answer. In yet another embodiment, the SDP parameters may be pre-defined parameters agreed upon between the UE and the network entity.
[0195] At step S1420, the network entity stores at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. The SDP parameters may include, for example, an IP address, a port number, a codec parameter, or a ptime value. The stored SDP parameters may remain valid and be applicable to all subsequent call setup procedures during a registration lifecycle of the UE. The SDP parameters are stored at both the network entity and the UE, such that both sides may reference the pre-configured SDP parameters in subsequent call setup procedures.
[0196] At step S1430, the network entity receives a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed based on the at least one stored SDP parameter. The specific call setup procedure may be a mobile-originated call setup procedure or a mobile-terminated call setup procedure.
[0197] For mobile-originated calls, the network entity may receive a SIP INVITE message from the UE without an SDP body or with pre-configured SDP. When the SIP INVITE is received without an SDP body, the network entity restores the stored SDP parameters and constructs a full SDP offer on behalf of the UE, then forwards the INVITE with the restored SDP offer to the IMS Core (see steps 802 and 803 of FIG. 8) . When the SIP INVITE is received with pre-configured SDP, the network entity may verify the SDP parameters against the stored pre-configuration and complete the SDP offer as needed.
[0198] For mobile-terminated calls, the network entity receives a SIP INVITE with an SDP offer from the IMS Core and may remove or replace the SDP offer based on the stored SDP parameters before forwarding the INVITE to the UE (see steps 1002a and 1002b of FIG. 10) . The network entity may further restore the SDP answer on behalf of the UE and send a 183 Session Progress message with the restored SDP answer to the IMS Core (see steps 1004 and 1005 of FIG. 10) . By performing the SDP negotiation with the IMS Core on behalf of the UE, the network entity reduces the signaling exchanged over the NTN access link, thereby reducing the overall call setup time.
[0199] FIG. 15 depicts a flow diagram of a method 1500 performed by a network entity for communicating with a UE according to an embodiment of the present disclosure. The network entity may be a P-CSCF such as the P-CSCF 318 of FIG. 3, and the UE may be the UE 302 of FIG. 3. The method 1500 is similar to the method 1400 of FIG. 14, with the addition of a dedicated QoS resource activation step prior to receiving the SIP message for the call setup procedure. The method includes the following steps:
[0200] S1510: Perform SDP pre-configuration procedure with the UE by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;
[0201] S1520: Store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;
[0202] S1530: Activate or modify a dedicated QoS resource based on the at least one stored SDP parameter; and
[0203] S1540: Receive a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource.
[0204] At step S1510, the network entity performs an SDP pre-configuration procedure with the UE by exchanging at least one SIP message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure. Step S1510 may be performed in the same manner as step S1410 of FIG. 14.
[0205] At step S1520, the network entity stores at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure. Step S1520 may be performed in the same manner as step S1420 of FIG. 14.
[0206] At step S1530, the network entity activates (or modifies) a dedicated QoS resource based on the at least one stored SDP parameter. Because the SDP parameters are already known upon completion of the SDP pre-configuration procedure, the network entity may trigger the dedicated QoS resource activation with the appropriate traffic flow template and QoS parameters without waiting for a call setup procedure to be initiated. The activation may involve signaling between the network entity and other network elements such as a PCRF, an SGW / PGW, an MME, and an NB-RAN to establish a bearer with appropriate QoS characteristics for the media session. The dedicated QoS resource may be activated in response to completing the SDP pre-configuration procedure. The dedicated QoS resource may comprise a dedicated bearer, such as a dedicated EPS bearer in a 4G system, a QoS flow with a dedicated QoS rule in a 5G system, or similar QoS resource allocation mechanisms in future generations of wireless communication systems. Activating the dedicated QoS resource prior to the call setup procedure eliminates the latency associated with in-call activation, which may contribute approximately five seconds of additional delay in NTN access scenarios.
[0207] At step S1540, the network entity receives a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource. The specific call setup procedure may be a mobile-originated call setup procedure or a mobile-terminated call setup procedure.
[0208] For mobile-originated calls, the network entity may receive a SIP INVITE message from the UE without an SDP body. Because the dedicated QoS resource has already been activated, the network entity restores the stored SDP parameters, constructs a full SDP offer on behalf of the UE, and forwards the INVITE with the restored SDP offer to the IMS Core. The detailed signaling flow for this procedure is illustrated in FIG. 9.
[0209] For mobile-terminated calls, the network entity receives a SIP INVITE with an SDP offer from the IMS Core and removes the SDP offer before forwarding the INVITE to the UE without SDP, because the dedicated QoS resource has already been activated and there is no need to include the SDP offer for QoS configuration purposes. The network entity restores the SDP answer on behalf of the UE and sends a 183 Session Progress message with the restored SDP answer to the IMS Core. The detailed signaling flow for this procedure is illustrated in FIG. 11. Compared to the method 1400 of FIG. 14, the method 1500 may achieve a further reduction in call setup time by eliminating the in-call dedicated QoS resource activation step.
[0210] Technical Advancement
[0211] The methods and apparatus described herein reduce call setup time in wireless communication systems by pre-configuring SDP parameters prior to call setup, in some implementations, by activating or modifying a dedicated QoS resource based on the pre-configured SDP parameters before a call is initiated. By shifting the SDP negotiation and QoS resource allocation to an earlier stage, the number of signaling messages, the message size, and the number of round-trip exchanges required during call setup are reduced. These reductions are particularly beneficial in NTN access scenarios where each signaling round trip involves significant propagation delay, enabling the call setup time to be brought within acceptable thresholds for user experience.
[0212] It will be appreciated that the embodiments described herein may be practiced individually or in any combination. For example, the SDP pre-configuration procedure during a SIP registration procedure (FIG. 4 and FIG. 5) , the SDP pre-configuration procedure using a pre-call SIP message flow (FIG. 6 and FIG. 7) , and the use of pre-defined SDP parameters may each be implemented independently or in combination with one another. Similarly, the MO call setup procedure (FIG. 8 and FIG. 9) and the MT call setup procedure (FIG. 10 and FIG. 11) may each be implemented independently or together. The activation of a dedicated QoS resource based on the stored SDP parameters (FIG. 9, FIG. 11, FIG. 13, and FIG. 15) may be implemented in combination with any of the SDP pre-configuration embodiments described herein, or may be omitted.
[0213] The features described in the embodiments herein may be combined freely. For example, the feature tag indicating support for the SDP pre-configuration procedure, the storing of SDP parameters at both the UE and the network entity, the initiating of a call setup procedure without an SDP body, the restoring of stored SDP parameters by the network entity on behalf of the UE, the removing or replacing of an SDP body in a SIP INVITE message for mobile-terminated calls, and the activation of a dedicated QoS resource based on the stored SDP parameters, are each independently disclosed features that may be combined in any subset to form further embodiments within the scope of the present disclosure.
[0214] The SDP parameters described herein, including but not limited to IP address, port number, codec type, codec parameters, payload type, and packetization time, may be used in any combination or subset. An embodiment may involve the pre-configuration of a single SDP parameter, a subset of SDP parameters, or all of the described SDP parameters.
[0215] Although certain embodiments have been described with reference to specific network architectures (e.g., EPC, IMS) , specific access technologies (e.g., NB-IoT NTN via GEO satellite) , specific SIP message types (e.g., SIP REGISTER, SIP OPTIONS, SIP INFO, SIP INVITE) , and specific SDP transport formats (e.g., XML body, SDP offer / answer) , each of these features is independently applicable and may be substituted or omitted without departing from the scope of the present disclosure. For example, an embodiment may implement the SDP pre-configuration procedure using any SIP message type not explicitly described herein, or may carry the SDP parameters in a format other than those specifically described.
[0216] Additional Remarks
[0217] For clarity in this specification, certain terminological conventions are observed. The singular forms "a" , "an" , and "the" are intended to encompass plural forms as well, unless the context clearly indicates otherwise. The term "and / or" refers to and encompasses any and all possible combinations of one or more of the associated listed items. The terms "includes, " "including, " "comprises, " and "comprising" specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0218] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration" and should not be construed as necessarily preferred or advantageous over other aspects or designs.
[0219] The use of ordinal designators like "first, " "second, " and so forth in the specification and claims serves to differentiate between multiple instances of similarly named elements. These designators do not imply any inherent sequence, priority, or chronological order in the manufacturing process or functional relationship between elements. Rather, they are employed solely as a means of uniquely identifying and distinguishing between separate instances of elements that share a common name or description.
[0220] Unless specifically stated otherwise, the term "some" refers to one or more. Various combinations using "at least one of" or "one or more of" followed by a list (e.g., A, B, or C) should be interpreted to include any combination of the listed items, including individual items and multiple items.
[0221] Terms such as "coupled, " "connected, " "connecting, " and "electrically connected" are used synonymously to describe a state of being electrically or electronically linked. When an entity is described as being in "communication" with another entity or entities, it implies the capability of sending and / or receiving electrical signals, which may contain image / voice or data / control information, regardless of whether these signals are analog or digital in nature.
[0222] As may be used throughout this specification and the appended claims, terms of approximation and degree such as "substantially, " "approximately, " "generally, " "essentially, " "nearly, " "about, " and similar expressions are used to account for variations in precision, manufacturing tolerances, measurement accuracy, environmental conditions, and inherent material properties that may affect the described features or characteristics. Such variations may range from ±20%in broader applications to progressively tighter tolerances of ±10%, ±5%, ±3%, ±2%, ±1%, or ±0.5%in more precise implementations. The specific degree of variation encompassed by these terms of approximation in any given context is informed by the nature of the component, relationship, or parameter being described, the technical requirements of the particular embodiment, and the understanding of one skilled in the relevant art.
[0223] In the context of this patent specification, the term "user equipment" (UE) encompasses a broad range of devices possessing radio communication capabilities. This definition includes, but is not limited to, smartphones (specifically, handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks) , Personal Data Assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, and any computing device equipped with a wireless communications interface. User equipment may also be referred to by various alternative terms, including but not limited to:client, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. These terms should be considered interchangeable within the context of this document.
[0224] The scope of UEs also extends to Internet of Things (IoT) devices. IoT UEs are characterized by a network access layer specifically designed for low-power IoT applications that typically involve short-lived UE connections. These IoT UEs may employ various technologies for data exchange, including Machine-to-Machine (M2M) , Machine Type Communication (MTC) , or massive MTC (mMTC) . Such data exchanges may occur with an MTC server or device via a Public Land Mobile Network (PLMN) , with other UEs using Proximity Services (ProSe) or Device-to-Device (D2D) communications, or through sensor networks or IoT networks. It is noteworthy that M2M or MTC data exchanges are often initiated by the machine itself rather than by human intervention.
[0225] An IoT network, as referenced in the above section, describes an interconnected system of IoT UEs. These UEs may include uniquely identifiable embedded computing devices integrated within the broader Internet infrastructure. IoT UEs may execute background applications, such as keep-alive messages or status updates, to maintain and facilitate the connections within the IoT network.
[0226] UEs are configured to establish communicative coupling with Radio Access Networks (RANs) through a radio interface. This radio interface is a physical communication interface or layer designed to operate with various cellular communication protocols. These protocols may include, but are not limited to, Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE) protocol, 5G protocol, and New Radio (NR) protocol.
[0227] As a specific example, a UE and a RAN may utilize a Uu interface (such as an LTE-Uu interface) to exchange control plane data. This exchange occurs via a protocol stack comprising multiple layers: a Physical (PHY) layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, and a Radio Resource Control (RRC) layer. In this context, a Downlink (DL) transmission refers to data sent from the RAN to the UE, while an Uplink (UL) transmission refers to data sent from the UE to the RAN.
[0228] Furthermore, UEs may employ a sidelink for direct communication with other UEs, facilitating D2D, Peer-to-Peer (P2P) , and / or ProSe communication. A ProSe interface, for instance, may incorporate one or more logical channels. These channels include, but are not limited to, a Physical Sidelink Control Channel (PSCCH) , a Physical Sidelink Shared Channel (PSSCH) , a Physical Sidelink Discovery Channel (PSDCH) , and a Physical Sidelink Broadcast Channel (PSBCH) .
[0229] The various aspects described herein may be implemented using a variety of hardware and software components. These may include processors, Digital Signal Processors (DSPs) , Application Specific Integrated Circuits (ASICs) , Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, or discrete hardware components. A processor in this context may be a microprocessor, but could also be any conventional processor, controller, microcontroller, or state machine. Processors may also be implemented as combinations of computing devices, such as 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.
[0230] The aspects described in this specification can be implemented through both hardware and software instructions. These instructions may be stored on various types of computer-readable media, including but not limited to Random Access Memory (RAM) , flash memory, Read Only Memory (ROM) , Electrically Programmable ROM (EPROM) , Electrically Erasable Programmable ROM (EEPROM) , registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In a typical configuration, the storage medium is connected to a processor, enabling the processor to read information from and write information to the medium. In some configurations, the storage medium may be integral to the processor itself.
[0231] Some embodiments may involve computers on a distributed computing network, such as a network with multiple clients and / or servers. In such embodiments, clients may run software implementing client-side portions of the described systems and methods, while servers handle requests from these clients. Communication between clients and servers may occur via one or more electronic networks, which may include the Internet, wide area networks, mobile telephone networks, wireless networks (e.g., Wi-Fi, 5G) , or local area networks, implemented using any known network protocols.
[0232] In implementations where the systems described in this specification collect user information, provisions may be made to protect user privacy and data. Specifically, users may be afforded the opportunity to opt in or out of programs or features that collect personal information, such as data related to user preferences or smart device usage patterns. Furthermore, in certain embodiments, data protection measures may be implemented to anonymize collected information prior to storage or utilization. For instance, a user's identity may be anonymized to prevent the determination or association of personally identifiable information with that specific user. Additionally, user preferences and interaction data may be generalized, potentially based on broader demographic categories, rather than being linked to individual users.
[0233] It should be noted that the operational steps described in any exemplary aspects within this specification are provided as examples and for discussion purposes. These operations may be performed in numerous different sequences other than the illustrated sequences. Furthermore, operations described in a single step may actually be performed as multiple distinct steps, and multiple steps may be combined into a single operational step. The steps in the appended figures may be subject to numerous modifications as will be apparent to those skilled in the art.
[0234] Some embodiments may incorporate all explicitly disclosed features as well as additional features that, while not specifically described herein, are compatible with and enhance the core invention. Conversely, other embodiments may selectively omit certain non-disclosed elements, either partially or in their entirety, while still falling within the scope of the invention. This flexibility in feature inclusion or exclusion allows for a range of implementations tailored to specific applications or requirements, without departing from the fundamental principles of the invention.
[0235] The logical stages illustrated in the drawings may be reordered, combined, or broken out if they are not order-dependent. The ordering and groupings presented in this specification are not exhaustive, and other arrangements will be apparent to those skilled in the art. These stages may be implemented in hardware, firmware, software, or any combination thereof.
[0236] The drawings and descriptions provided in this specification offer detailed illustrations of various embodiments of the invention. However, it should be understood by those skilled in the art that these embodiments can be implemented without necessarily adhering to every specific detail provided herein. In some instances, well-established methods, procedures, components, and circuits have been mentioned without elaborate explanations to avoid obscuring the key aspects of the embodiments. It is important to note that the figures presented in this specification, including any component diagrams, are intended for illustrative purposes and may not be drawn to scale. This allows for a clear presentation of the inventive concepts while leaving room for variations and adaptations within the scope of the invention.
[0237] The foregoing outlines the features of several embodiments, enabling those skilled in the art to fully appreciate the aspects of the present disclosure. Those skilled in the art should recognize that the present disclosure provides a foundation for designing or modifying other processes and structures to achieve substantially the same functions and / or substantially the same results as those of the embodiments introduced herein. Furthermore, such equivalent arrangements do not deviate from the spirit and scope of the present disclosure, and various changes, substitutions, and alterations may be made without so departing.
Claims
1.A method performed by a user equipment (UE) for communicating with a network entity, the method comprising:performing a Session Description Protocol (SDP) pre-configuration procedure with the network entity by exchanging at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;storing at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;triggering activation or modification of a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter; andin response to the activation or modification of the dedicated QoS resource, initiating a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource.2.The method of claim 1, wherein the UE is registered in an Internet Protocol Multimedia Subsystem (IMS) network.3.The method of claim 2, wherein the network entity comprises a Proxy Call Session Control Function (P-CSCF) operating within the IMS network.4.The method of claim 1, wherein the SDP pre-configuration procedure is performed during a SIP registration procedure.5.The method of claim 4, wherein exchanging the at least one SIP message comprises:transmitting, by the UE, a SIP REGISTER message having a feature tag indicating support for the SDP pre-configuration procedure; andreceiving, by the UE, a response message having at least one SDP parameter selected by the network entity.6.The method of claim 1, wherein the SDP pre-configuration procedure is performed after a SIP registration procedure and prior to the specific call setup procedure by transmitting, from the UE, a SIP message for performing the SDP pre-configuration procedure.7.The method of claim 1, wherein the dedicated QoS resource is activated or modified in response to completing the SDP pre-configuration procedure.8.The method of claim 1, wherein the at least one stored SDP parameter is applicable to subsequent call setup procedures during a registration lifecycle of the UE.9.The method of claim 1, wherein initiating the specific call setup procedure comprises transmitting, by the UE, a SIP INVITE message without an SDP body.10.The method of claim 1, wherein the UE communicates with the network entity via a non-terrestrial network (NTN) access.11.The method of claim 1, wherein the dedicated QoS resource comprises a dedicated Evolved Packet System (EPS) bearer and / or a dedicated QoS flow.12.A method performed by a network entity for communicating with a user equipment (UE) , the method comprising:performing a Session Description Protocol (SDP) pre-configuration procedure with the UE by exchanging at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;storing at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;activating or modifying a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter; andreceiving a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource.13.The method of claim 12, wherein the network entity comprises a Proxy Call Session Control Function (P-CSCF) operating within an Internet Protocol Multimedia Subsystem (IMS) network.14.The method of claim 13, wherein the P-CSCF performs the SDP pre-configuration procedure with the UE.15.The method of claim 12, further comprising restoring the at least one stored SDP parameter to complete call establishment.16.The method of claim 15, wherein restoring the at least one stored SDP parameter comprises modifying an SDP body in a SIP INVITE message based on the at least one stored SDP parameter.17.The method of claim 12, wherein the specific call setup procedure is a mobile-originated call setup procedure, and receiving the SIP message comprises receiving the SIP message from the UE.18.The method of claim 12, wherein the specific call setup procedure is a mobile-terminated call setup procedure, and receiving the SIP message comprises receiving the SIP message from an IMS core entity.19.The method of claim 12, wherein the SDP pre-configuration procedure is performed during a SIP registration procedure.20.The method of claim 12, wherein the SDP pre-configuration procedure is performed after a SIP registration procedure and prior to the specific call setup procedure by receiving, at the network entity from the UE, a SIP message for performing the SDP pre-configuration procedure.21.The method of claim 12, wherein the dedicated QoS resource is activated or modified in response to completing the SDP pre-configuration procedure.22.The method of claim 12, wherein the at least one stored SDP parameter is applicable to subsequent call setup procedures during a registration lifecycle of the UE.23.The method of claim 12, wherein the network entity communicates with the UE via a non-terrestrial network (NTN) access.24.The method of claim 12, wherein the dedicated QoS resource comprises a dedicated Evolved Packet System (EPS) bearer and / or a dedicated QoS flow.25.A user equipment (UE) comprising:a transceiver configured to communicate with a network entity; anda processor coupled to the transceiver, the processor configured to:perform a Session Description Protocol (SDP) pre-configuration procedure with the network entity by exchanging, via the transceiver, at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;trigger activation or modification of a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter; andin response to the activation or modification of the dedicated QoS resource, initiate a specific call setup procedure of the at least one subsequent call setup procedure using the at least one stored SDP parameter and the dedicated QoS resource.26.The UE of claim 25, wherein the UE is registered in an Internet Protocol Multimedia Subsystem (IMS) network.27.The UE of claim 25, wherein the processor is further configured to perform the SDP pre-configuration procedure during a SIP registration procedure.28.The UE of claim 25, wherein the processor is further configured to perform the SDP pre-configuration procedure after a SIP registration procedure and prior to the specific call setup procedure by transmitting, via the transceiver, a SIP message for performing the SDP pre-configuration procedure.29.The UE of claim 25, wherein the dedicated QoS resource is activated or modified in response to completing the SDP pre-configuration procedure.30.The UE of claim 25, wherein the at least one stored SDP parameter is applicable to subsequent call setup procedures during a registration lifecycle of the UE.31.The UE of claim 25, wherein the transceiver is configured to communicate with the network entity via a non-terrestrial network (NTN) access.32.The UE of claim 25, wherein the dedicated QoS resource comprises a dedicated Evolved Packet System (EPS) bearer and / or a dedicated QoS flow.33.A network entity comprising:a memory for storing instructions; anda processor coupled to the memory and configured to execute the instructions to:perform a Session Description Protocol (SDP) pre-configuration procedure with a user equipment (UE) by exchanging at least one Session Initiation Protocol (SIP) message, wherein the at least one SIP message indicates support for the SDP pre-configuration procedure;store at least one SDP parameter resulting from the SDP pre-configuration procedure, wherein the at least one stored SDP parameter is applicable to at least one subsequent call setup procedure;activate or modify a dedicated Quality of Service (QoS) resource based on the at least one stored SDP parameter; andreceive a SIP message associated with a specific call setup procedure of the at least one subsequent call setup procedure, wherein the specific call setup procedure is performed using the at least one stored SDP parameter and the dedicated QoS resource.34.The network entity of claim 33, wherein the network entity comprises a Proxy Call Session Control Function (P-CSCF) operating within an Internet Protocol Multimedia Subsystem (IMS) network.35.The network entity of claim 33, wherein the processor is further configured to execute the instructions to restore the at least one stored SDP parameter to complete call establishment.36.The network entity of claim 33, wherein the processor is configured to execute the instructions to perform the SDP pre-configuration procedure during a SIP registration procedure.37.The network entity of claim 33, wherein the processor is configured to execute the instructions to perform the SDP pre-configuration procedure after a SIP registration procedure and prior to the specific call setup procedure by receiving, from the UE, a SIP message for performing the SDP pre-configuration procedure.38.The network entity of claim 33, wherein the dedicated QoS resource is activated or modified in response to completing the SDP pre-configuration procedure.39.The network entity of claim 33, wherein the network entity communicates with the UE via a non-terrestrial network (NTN) access.40.The network entity of claim 33, wherein the dedicated QoS resource comprises a dedicated Evolved Packet System (EPS) bearer and / or a dedicated QoS flow.41.The network entity of claim 33, wherein the specific call setup procedure is a mobile-originated call setup procedure, and the processor is configured to execute the instructions to receive the SIP message from the UE.42.The network entity of claim 33, wherein the specific call setup procedure is a mobile-terminated call setup procedure, and the processor is configured to execute the instructions to receive the SIP message from an IMS core entity.
