SIP timer modification for supporting IMS call fallback

By selectively restarting and extending the SIP timer, the problem of insufficient timers during the fallback process in the cellular phone standard is solved, ensuring the successful completion of calls and the improvement of user experience.

CN119072914APending Publication Date: 2024-12-03GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380038169.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-06-03
Filing Date
2023-05-03
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Existing cellular phone standards During the fallback process, the standardization duration of the SIP timer may not be enough to complete the fallback process, causing the UE to terminate the call attempt prematurely, affecting connectivity and user experience.

Method used

By selectively restarting the SIP timer and adding offsets, providing additional time to complete subprocesses in the fallback process, such as the TAU process, ensuring the success of the fallback attempt and the persistence of the call.

Benefits of technology

Extend the time of the fallback process, prevent premature call termination, and improve call success rate and user experience, especially in EPSFB and other similar fallback scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072914A_ABST
    Figure CN119072914A_ABST
Patent Text Reader

Abstract

A user equipment (UE) is configured to initiate a packet switched call via a first radio access technology (RAT), and initiate a plurality of session initiation protocol (SIP) timers in response to initiating the call. In response to the presence of at least one condition in initiating a fallback procedure of a call, the UE is configured to restart a set of a plurality of SIP timers to perform the fallback procedure, where the set may include some or all of the plurality of SIP timers initiated in initiating the call. Each SIP timer has a corresponding default timer duration, and in some cases, restarting the SIP timers in the set includes restarting the SIP timers using a start duration equal to the sum of the default timer duration and the offset, the restarted SIP timer provides a longer duration than when initially started to better accommodate the fallback process.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] Certain cellular telephone standards provide a "fallback" procedure in which a user equipment (UE) can attempt to establish an Internet Protocol Multimedia Subsystem (IMS) call (or other packet-switched call) via a first, typically more advanced radio access technology (RAT), and if the IMS call attempt fails, the UE can "fall back" to a second, typically less advanced RAT. For example, the Third Generation Partnership Project (3GPP) Fifth Generation New Radio (5G NR) set of standards specifies an Evolved Packet System (EPS) Fallback (EPSFB) procedure to facilitate UE connectivity even though 5G NR may not yet be fully configured for voice calls. The EPSFB procedure can be implemented in two ways. In the first approach, an inter-RAT handover occurs after the call is initiated, so that although the call is initiated via the 5G NR RAT, the call is ultimately made via the 3GPP Fourth Generation Long Term Evolution (4G LTE) RAT. In the second method, the network issues a "Release with Redirect" message, which triggers the UE to completely release the 5G NR radio connection and retry the call using a new radio connection to the 4G LTE cell. The 3GPP 4G LTE set of standards also has a similar Circuit Switched Fallback (CSFB) procedure for falling back from the 4G LTE RAT to a third generation (3G) RAT or even a second generation (2G) RAT. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] The present disclosure will be better understood and its numerous features and advantages will become apparent to those skilled in the art by referring to the following examples.The use of the same reference numerals in different drawings indicates similar or identical items.

[0003] Figure 1 is a block diagram of a cellular telephone system that employs conditional SIP timer restarts at call setup for a fallback procedure in accordance with some embodiments.

[0004] Figure 2 According to some embodiments Figure 1 Block diagram of a UE of a system.

[0005] Figure 3 is a combined flow ladder diagram illustrating a SIP timer restart procedure for a scenario where a Release with Redirect message is received as part of a fallback procedure in accordance with some embodiments.

[0006] Figure 4is a combined flow ladder diagram illustrating a SIP timer modification process for a scenario where a Release with Redirect message is not received as part of a fallback process in accordance with some embodiments.

[0007] Figure 5 is a combined flow ladder diagram illustrating a SIP timer modification process for a scenario where a Release with Redirect message is not received and a preferred RAT connection is not available, according to some embodiments.

[0008] Figure 6 is a combined flow ladder diagram illustrating a SIP timer modification process for a scenario where there is a Quality of Service (QoS) timer expiration, according to some embodiments. DETAILED DESCRIPTION

[0009] When a UE initiates a packet-switched call (e.g., an IMS call) via a corresponding RAT, a sequence of Session Initiation Protocol (SIP) messages is exchanged between the UE and the network to establish and then maintain the packet-switched call. The initial SIP message transmitted in this sequence is typically a SIP INVITE message, the transmission of which triggers the UE to start multiple SIP timers. These SIP timers are used to specify various waiting periods for corresponding actions from the network, and when specific messages or other signaling from the network are received, the corresponding SIP timers are stopped or canceled. If a SIP timer expires before being stopped or canceled, the timer expiration triggers one or more corresponding actions from the UE, which may affect the connectivity of the UE. For example, the SIPRequestTimeout timer specifies the maximum time the UE should wait for any response from the network after transmitting the SIP INVITE message. The expiration of the SIPRequestTimeout timer indicates that the network has failed to respond within the specified duration, and this typically triggers the UE to terminate the call establishment, and in some cases, attempt to silently redial the call through an alternative RAT. Other SIP timers are bound to other messages and may also trigger the UE to terminate the call establishment or otherwise affect the behavior of the UE during the call establishment.

[0010] While the use of SIP timers generally helps ensure that the UE does not spend excessive time trying to establish a call that ultimately cannot be established, in some cases, the standardized durations of SIP timers may not be practical for certain cellular fallback scenarios. For example, a Radio Resource Control (RRC) Release with Redirect message may not be received in a timely manner, but some networks may continue to transmit SIP messages even in the absence of an RRC Release with Redirect message, which may cause the UE to continue attempting to use the original RAT or source RAT that was originally used to attempt the call, rather than falling back to an alternative RAT. As another example, the default duration of the SIP RequestTimeout timer is generally insufficient for the UE to complete an LTE silent retry, which may then force the UE to turn to CSFB due to a perceived EPSFB "failure". As yet another example, after EPSFB is completed, a Voice over LTE (VoLTE) call may be terminated immediately due to the expiration of one or more other SIP timers caused by a failure to establish a dedicated bearer in a timely manner. However, it is generally not recommended to override the default SIP timer duration specified by the corresponding cellular standard by simply defaulting to a longer timer duration. Doing so will affect all such IMS calls that utilize the corresponding SIP timers, including emergency calls. For example, setting a longer SIP timer for all cases may result in a longer duration before a call retry is performed, or if the network does not send any audio packets during the extended portion of the timer, the silent phone time will be extended, which may make the user question whether the call is continuing.

[0011] Thus, disclosed herein are systems and techniques for facilitating EPSFB and other similar fallback procedures by selectively restarting SIP timers in response to one or more specified conditions and adding general or timer-specific offsets to the restarted SIP timers to provide additional time to complete various sub-procedures associated with the fallback procedure, depending on the scenario. For example, in one case, after a condition is met for receiving an RRC Release with Redirect message at the UE after the UE attempts to initiate a 5G NR voice (VoNR) call, the UE may restart some or all SIP timers initiated by transmitting a SIP INVITE message and add the same or different offsets to each restarted timer to provide the UE with sufficient time to complete a target area update (TAU) procedure, which is typically implemented as part of the EPSFB procedure after the Release with Redirect message. As another example, after an expiration condition for a quality of service (QoS) reservation timer initiated in response to a SIP Session Progress with Session Description Protocol (SDP) message is met, the UE may restart the QoS reservation timer and add an offset (as well as restart other SIP timers with the corresponding offset) to similarly provide sufficient time for completion of the TAU procedure. These example scenarios, as well as other scenarios involving selectively restarting one or more SIP timers to facilitate an efficient backoff process, are described in detail below.

[0012] Figure 1 A cellular communication system 100 is shown that employs selective SIP timer restart during call origination fallback according to some embodiments. As shown, the system 100 includes a user equipment (UE) 102 and one or more cellular infrastructure networks 104, such as the two illustrated cellular infrastructure networks 104-1 and 104-2. The UE 102 may include any of a variety of electronic wireless communication devices, such as a cellular phone, a cellular-enabled tablet or cellular-enabled laptop, a cellular-enabled watch or other wearable device, a car or other vehicle employing cellular service (e.g., for navigation, providing entertainment services, in-vehicle mobile hotspots, etc.), a cellular access point (or "hotspot"), etc. Each cellular infrastructure network 104 is connected to one or more other cellular infrastructure networks 104 via at least one packet data network (PDN) 106 such as the Internet, via one or more dedicated interconnect data networks, or a combination thereof.

[0013] Each cellular infrastructure network 104 includes a core network 108 and multiple edge networks or radio access networks (RANs) connected via a backhaul infrastructure. Although the cellular infrastructure networks 106-1 and 106-2 are shown as having different core networks 108 (e.g., core networks 108-1 and 108-2, respectively), in other embodiments, multiple cellular infrastructure networks 104 share the same core network 108, but differ in the edge networks connected to the shared core network 108. Each edge network includes at least one base station (BS) 110, such as base stations 110-1 and 110-2, which are operable to wirelessly communicate with UEs within signal range based on one or more radio access technologies (RATs). Examples of base stations 110 include, for example, NodeBs (or base transceiver stations (BTSs)) for Universal Mobile Telecommunications System (UMTS) RAT implementations (also referred to as "3G"), enhanced NodeBs (eNodeBs) for Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) RAT implementations, 5G Node Bs (gNBs) for 3GPP Fifth Generation New Radio (5G NR) RAT implementations, etc. As is known in the art, base stations 110 operate as an "air interface" to establish radio frequency (RF) wireless connections with UEs, and these wireless connections (or "links") are then used as data and voice paths between the UE and the core network 108 for providing various services to the UE, including voice services via circuit-switched networks or packet-switched networks, messaging services such as Simple Messaging Service (SMS) or Multimedia Messaging Service (MMS), multimedia content delivery, presence services, etc. For ease of explanation, base station 110-1 is described in various scenarios below as a 5G NR radio access network (RAN), and is therefore an eNodeB in such scenarios, while base station 101-2 is described in various scenarios as a 4G LTE RAN, and is therefore a gNB in ​​such scenarios. However, it should be understood that base stations 110-1 and 110-2 are not limited to these example configurations. For example, base station 101-1 can be a 4G LTE RAN (e.g., a gNB), and base station 101-2 can be a 3G RAN (e.g., a NodeB), or vice versa.

[0014] Although battery power, signal quality, and other factors may ultimately lead to different prioritizations, all other factors being equal, the UE 102 generally seeks to establish a call with the most advanced RAN that the UE 102 can support. Thus, assuming that the base station 110-1 represents a more advanced RAN than the base station 110-2 (e.g., a 5G NR RAN versus a 4G LTE RAN), the UE 102 will attempt to camp on a cell supported by the base station 110-1. When the user attempts to initiate a packet-switched call (IMS call) such as a VoNR voice or video call, the UE 102 attempts to establish a packet-switched call 112 with the cellular infrastructure network 104-1. However, one or both of the UE 102 or the cellular infrastructure network 104-1 may not have the capability to establish and conduct a packet-switched call between the UE 102 and the cellular infrastructure network 104-1. For example, the UE 102 may generally support 5G NR RAT functionality, but may not be configured to implement VoNR via a 5G NR connection. As another example, the cellular infrastructure network 104-1 may be configured to disable VoNR support for the UE 102, or the cellular infrastructure network 104-1 may be, for example, a 5G NR non-standalone (NSA) deployment, while the UE 102 may only support VoNR via a 5G NR standalone (SA) deployment. In any case, the UE 102 may attempt to establish a packet-switched call with the cellular infrastructure network 104-1, and at some point, one or both of the UE 102 and the cellular infrastructure network 104-1 recognizes that a fallback to a different RAT is needed. As a result, a fallback procedure is initiated, such as EPSFB in the case where the cellular infrastructure network 104-1 is a 5G NR RAN, or CSFB in the case where the cellular infrastructure network 104-1 is a 4G LTE RAN, so that the call establishment is redirected to another RAN, such as the base station 110-2 of the cellular infrastructure network 104-2.

[0015] However, the initial attempt at call setup triggers UE 102 to start multiple SIP timers related to call setup or call maintenance. These SIP timers continue to run (count down) until the corresponding SIP timer expires or a corresponding condition (usually a specific message is received from the network). More specifically, some or all of these SIP timers continue to run during the fallback attempt 114. However, the fallback attempt 114 may take a relatively long time because it may involve one or more lengthy sub-processes, such as LTE silent call retries or processes that attempt to establish a dedicated bearer for quality of service (QoS) purposes. Therefore, there is a great risk that a SIP timer that triggers UE 102 to terminate the call attempt or otherwise triggers UE behavior that negatively affects the fallback attempt 114 will expire unexpectedly while the initiated fallback process is still ongoing, which in turn may result in premature termination of the call attempt.

[0016] Therefore, in at least one embodiment, the UE 102 employs a selective SIP timer restart process 116 in which, in response to certain conditions being met related to the fallback attempt 114, the UE 102 selectively restarts a set of SIP timers, and in some embodiments, adds an offset to some or all of the restarted SIP timers, wherein the added offset may be the same or different for different restarted SIP timers. By restarting the affected SIP timers in response to specific scenarios and adding corresponding offsets, rather than generally extending the SIP timers by de facto default, the UE 102 can provide more time for the fallback attempt 114 to complete and succeed before the expiration of the SIP timer triggers the UE 102 to terminate the call attempt entirely or otherwise take actions that negatively affect the fallback attempt 114, while also maintaining the original SIP timer duration for other packet-switched calls, such as emergency calls or IMS calls using certain RATs, such as Voice over WiFi (VoWiFi) calls using a wireless local area network (WLAN) RAT.

[0017] Figure 2An example hardware implementation 200 of a UE 102 according to some embodiments is shown. In the depicted example, the UE 102 includes at least one application processor 202 (e.g., a central processing unit (CPU) or other general purpose processor), a system memory 204, one or more RF modems 206, one or more RF transceivers 208, and one or more antenna arrays 210, which are suitable for RF signaling and signal processing in one or more frequency bands typically associated with a corresponding RAT (e.g., a 5G NR RAT). Each RF modem 206, RF transceiver 208, and antenna array 210 triplet together supports a corresponding RAT 212. In the illustrated embodiment, the UE 102 supports two RATs 212, namely RAT 212-1 (which is implemented by the RF modem 206-1, the RF transceiver 208-1, and the antenna array 210-1) and RAT 212-2 (which is implemented by the RF modem 206-2, the RF transceiver 208-2, and the antenna array 210-2). Note that in other embodiments, the UE 102 may support more than two RATs 212. Furthermore, the multiple RATs 212 of the UE 102 may implement overlapping hardware. For example, two RATs 212 may share one or more RF modems 206, RF transceivers 208, or antenna arrays 210. As shown using RF modem 206-1, each RF modem 206 includes a baseband processor 214 and a memory 216, which may include, for example, flash memory, non-volatile random access memory (NVRAM) or other non-volatile memory, or static RAM (SRAM) or dynamic RAM (DRAM) or other volatile memory, or a combination thereof. Furthermore, it should be understood that the UE 102 may include multiple RATs 212 for ease of illustration. Figure 2 The present invention also includes a plurality of additional components omitted from the present invention, including, for example, one or more displays, one or more touch screens, a keyboard, a mouse, a touchpad, a microphone, a speaker and other user input / output devices, one or more sensors, a battery or other power source, a graphics processing unit (GPU) or other coprocessor, etc.

[0018] The application processor 202 executes executable instructions from a software stack that includes an operating system (OS) 230 and one or more user software applications, such as user software application 232, and may further include a protocol stack executed by the baseband processor 214 of the RF modem 206. The OS 230 manages the general operation of the various hardware components of the UE 102 by manipulating the application processor 202, as well as supports the execution of one or more user software applications, wherein the executable instructions representing the OS 230 and the user software applications are typically accessed from the system memory 204 for execution by the application processor 202. Thus, the modules of the OS 230 include a cellular phone module 236 that is used to control or facilitate higher-level cellular-related operations of the UE 102, including subscriber identity management, initiation, control, and teardown of cellular connections (including SIP messaging and RRC messaging), authentication, interfacing between cellular connections and user software applications, and the like. In addition, the memory 216 of the RF modem 206 stores one or more protocol stacks 240 for corresponding cellular standards. Each protocol stack 240 stores executable instructions that, when executed by the baseband processor 214, operate the baseband processor 214 to communicate with a base station 110 ( Figure 1 ) performs various operations in accordance with a RAT protocol or other communication protocol associated with the air interface provided by the UE 102, and the UE 102 is attempting to establish a communication link with the base station 110. As is well known, such operations are typically associated with lower level layers of the network protocol, such as some or all of the physical layer, data link layer, and network layer, while the OS 230 and user software applications support higher level layers of the network protocol, such as the transport layer, session layer, presentation layer, and application layer.

[0019] In at least one embodiment, the cell phone module 236 includes a SIP timer management module 238 configured to manage a collection 242 of SIP timers utilized by the cell phone module 236. The collection 242 includes SIP timers 244, which are associated with call establishment and call maintenance and may affect call attempts that are undergoing a fallback process. Such timers may include, for example, the RequestTimeout timer (SIP timer 244-1), the QoS Reservation timer (SIP timer) 244-2, the T1, T2, and T4 timers (SIP timers 244-3, 244-4, and 245-5, respectively), and the timer AN (SIP timers 244-A to 244-N, respectively) as determined in the 3GPP Technical Specification (TS) 24.229 and various corresponding 3GPP Request for Comments (RFCs). Those skilled in the art will appreciate that these SIP timers may negatively impact the fallback attempt due to the duration of the fallback attempt (or corresponding sub-process) relative to the default duration of the timer (e.g., as specified in 3GPP TS 24.299 or other similar specifications). For example, the SIP RequestTimeout timer 244-1 is specified to be set between 5 seconds and 15 seconds, is started by the SIP timer management module 238 when the UE 102 transmits a SIP INVITE message, and is stopped by the SIP timer management module 238 when the UE 102 receives any SIP message in response. In response to the expiration of the timer, the UE should terminate the call establishment and, if the alternative RAT is available, attempt a silent redial of the call over the alternative RAT. As another example, the SIP QoS Reservation timer 244-2 is set to a duration of 6 seconds, is started by the SIP timer management module 238 when the UE 102 receives a SIP 183 with SDP message (i.e., a SIP 183 message with an SDP indicating that a precondition is required, i.e., a dedicated QoS bearer for media is available), and is stopped by the SIP timer management module 238 when the dedicated bearer establishment is complete and the QoS precondition is met. In response to the expiration of the timer, the UE is intended to send a SIP 580 Preconditions Failure message or a SIP CANCEL message to terminate the call.As yet another example, the SIP B timer 244-B is set to a duration of 128 seconds, which is started by the SIP timer management module 238 when the UE 102 transmits a SIP INVITE message, and which is stopped by the SIP timer management module 238 when the UE 102 receives a final SIP message (SIP 2xx, 3xx, 4xx, 5xx, or 6xx message) in response to the SIP INVITE message. In response to the expiration of the timer, the UE is intended to mark the currently used proxy call session control function (P-CSCF) address as unavailable, and then try the next P-CSCF and initiate registration. For ease of reference, Table 7.7.1 of the 3GPP TS 24.229 version 12.9.0 Release 12 standard describes a number of SIP timers that can be managed by the SIP timer management module 238 and set to a default duration that can negatively impact EPSFB or other fallback processes, and is reproduced below:

[0020] Figures 3 to 6 Various example scenarios are shown in which the SIP timer management module 238 selectively restarts the SIP timer (with or without an additional offset) to configure the UE 102 to provide additional time to accommodate various sub-processes performed as part of a call fallback attempt. Although four such scenarios are shown by way of example, the general method of selectively restarting the SIP timer for a fallback attempt in response to one or more specified conditions being satisfied associated with the fallback process is not limited to these specific scenarios, but can be implemented in any of a variety of similar scenarios using the guidance and examples provided herein. In these four example scenarios, the cellular infrastructure network 104-1 is a 5G NR RAN and is therefore the "source" network (or "source" RAT), and the cellular infrastructure network 104-2 is a 4G LTE network, which is the "target" network (or "target" RAT) for fallback purposes. Additionally, for these examples, UE 102 is not configured to support IMS calls over 5G NR, or source network 104-1 is not configured to support IMS calls over 5G NR for UE 102, so some form of EPSFB (or other fallback) is attempted after attempting to initiate a call with source network 104-1.

[0021] Figure 3A combined method ladder diagram 300 is shown, which illustrates the operation of UE 102 in a scenario where an EPSFB attempt is triggered in response to successfully receiving an RRC Release with Redirect message from a 5G NR source network 104-1. At block 302, a user of UE 102 initiates an IMS call via 5G NR, which triggers UE 102 to transmit a SIP INVITE message 303 to source network 104-1. In response to the transmission of the SIP INVITE message 303, at block 304, the SIP timer management module 238 starts an appropriate SIP timer 244.

[0022] Since the source network 104-1 is not configured to support IMS calls (e.g., VoNR) over 5G NR for UE 102 in this scenario, the source network 104-1 cannot respond with a SIP RINGING message to indicate that the destination user agent has received the SIP INVITE message 303. Therefore, the source network 104-1 instead responds to the SIP INVITE message 303 with a SIP TRYING message 305 to indicate that an extended search is being performed, which may take a considerable amount of time. In response to the SIP TRYING message 305, the SIP timer management module 238 stops the appropriate SIP timers, such as the SIP RequestTimeout timer 244-1 and the SIP B timer 244-B.

[0023] In addition, the source network 104-1 recognizes that the IMS call cannot be completed via 5G NR and therefore initiates an EPSFB procedure by transmitting an RRC Release with Redirect message 307 to direct the UE 102 to fall back to the 4G LTE RAT. Therefore, in response to the RRC Release with Redirect message 307, at box 308, the UE 102 determines whether the IMS call (or other packet switched call) can be supported via the target RAT (i.e., via the 4G LTE RAT supported by the target network 104-2). If the IMS call is not available, then at box 310, the UE 102 does not change any running SIP timers 244 and continues to manage the fallback process according to the default or standardized process. In this particular case, since the fallback attempt will not work due to the unavailability of the IMS call via the "fallback" network, the subsequent expiration of one or more running SIP timers will cause the UE 102 to terminate the call attempt.

[0024] Returning to block 308, if the UE 102 determines that IMS calls are available (supported) through the target network 104-2, then at block 312, in response to the conditions for receiving the RRC Release with Redirect message 307 being met and the conditions that the target network 104-2 can support packet-switched calls (i.e., IMS calls) being met, the SIP timer management module 238 prepares for an EPSFB attempt by restarting those running SIP timers 244 that may affect the EPSFB attempt. This may include, for example, the SIP timer management module 238 restarting some or all of the SIP Request Timeout timer 244-1, the SIP QoS Reservation timer 244-2, the SIP T1, T2, and T4 timers (timers 244-3 to 244-6), the SIP timer AN (timers 244-A to 244-N), etc. In addition, recognizing that the sub-process of successfully completing the EPSFB attempt may require an extended duration, in some embodiments, the SIP timer management module 238 may add an additional offset to the default duration of the corresponding restarted SIP timer. This offset may be the same value for each restarted timer. For example, the offset may be specified as 10 seconds, so that the SIP RequestTimeout timer 244-1 (with a default duration of, for example, 15 seconds) will restart with a starting duration of the sum of the default duration and the offset to be applied (or 25 seconds), while the SIP QoSReservation timer 244-2 (with a default duration of 6 seconds) will restart with a starting duration of 16 seconds. In other embodiments, different offsets may be applied to different restarted SIP timers. For example, the offset applied to each restarted SIP timer may be proportional to its default duration (e.g., an offset of 150%). In other embodiments, a specific offset applied to each restarted SIP timer or a standard offset applied to each restarted SIP timer may be selected based on analysis, estimation, simulation, or a combination thereof.

[0025] As the SIP timer 244 is restarted (and, in some embodiments, extended from its default duration by introducing an offset), the UE 102 performs one or more sub-procedures of the EPSFB attempt. One such sub-procedure that is relatively long, and therefore may result in the expiration of a SIP timer that is not restarted according to the techniques described herein, is a Tracking Area Update (TAU) procedure that is typically performed during a handover or fallback procedure. It should be understood that from the perspective of the target network 104-2, the UE 102 is effectively in an "idle" state when the EPSFB procedure is initiated, and therefore, the target network 104-2 needs to determine the location of the UE 102 at the cell level rather than the tracking area (TA) level. Therefore, as part of the EPSFB procedure, and after (or simultaneously with) restarting the SIP timer at box 312, the UE 102 and the target network 104-2 conduct a TAU procedure 314 so that the target network 104-2 can identify the "cell" location of the UE 102. As is known in the art, the procedure generally includes transmission of a TAU request message 315, which includes various information about UE 102, such as core network capabilities, last visited tracking area identifier (TAI), EPS bearer status, etc. In response, assuming the mobility management entity (MME) of target network 104-2 accepts the UE's request, target network 104-2 responds with a TAU accept message 317, which, among other things, informs the MME that a new Globally Unique Temporary UE Identity (GUTI) has been allocated for UE 102. In response to TAU accept message 317, UE 102 transmits a TAU complete message 319 to acknowledge receipt and signal that the TAU procedure is complete.

[0026] In the illustrated scenario, the TAU procedure 314 and other sub-procedures of the EPSFB attempt are completed before any restarted and extended SIP timers expire, thereby allowing the UE 102 sufficient time to complete the EPSFB procedure without causing a premature call termination due to the expiration of the default duration of the original SIP timer, which does not adequately account for the relatively long duration that may be required for successful fallback after a failed attempt to initiate a call using a RAT that is not available to support packet-switched calls.

[0027] Figure 4A combined method ladder diagram 400 is shown, which illustrates the operation of UE 102 in a scenario where an EPSFB attempt is triggered in response to failure to receive an RRC Release with Redirect message from 5G NR source network 104-1. At block 402, a user of UE 102 initiates an IMS call via 5G NR, which triggers UE 102 to transmit a SIP INVITE message 403 to source network 104-1. In response to transmission of SIP INVITE message 403, at block 404, SIP timer management module 238 starts an appropriate SIP timer 244.

[0028] In this scenario, the source network 104-1 does not respond with any SIP message or RRC Release with Redirect message. Therefore, due to the lack of a received response, the SIP RequestTimeout timer 244-1 will eventually expire (box 406). However, unlike conventional approaches in which the expiration of this timer automatically triggers call termination, and unlike in some approaches in which the modem redials using a different RAT, in at least one embodiment, instead, the UE 102 uses a restarted (and extended) SIP timer to implement the fallback attempt. Therefore, at box 408, the UE determines whether VoNR (i.e., IMS calls via 5G NR) is disabled or otherwise unavailable to support packet-switched calls via the UE 102 (e.g., due to software settings or configuration at the UE 102), and whether the US 102 is currently using a 5G NR RAT (e.g., RAT 212-1, Figure 2 ). If any of these conditions is false (or "no"), a UE-initiated fallback attempt is not recommended, so at block 410 UE 104 defaults to a conventional approach, where UE 102 attempts a silent redial of the user-initiated call via an alternative RAT (e.g., 4G LTE RAT).

[0029] However, if both conditions are true (or "yes"), then at box 412, the UE 102 confirms that the RRC Release with Redirect message has not been received. If such a message has in fact been received, but the SIP Request Timeout timer 244-1 has expired, then an EPSFB attempt is not recommended, so at box 410 the UE 102 defaults to the conventional method of silently redialing the call via the alternative RAT. Otherwise, if the condition that the RRC Release with Redirect message is not received is met, the UE 102 continues to make fallback attempts by attempting to camp on the target network 104-2 with IMS. Therefore, at box 414, the UE 102 switches from the source RAT to the target RAT (e.g., from using RAT 212-1 to using RAT 212-2), and at box 416, the UE 102 restarts some or all running (or expired) SIP timers, and in some embodiments, adds the same or different offsets to some or all restarted SIP timers. This SIP timer restart (with the additional offset) prepares the UE 102 to initiate execution of the sub-procedure of the EFSFB procedure without premature termination due to the expiration of the SIP timer originally started by issuing the SIP INVITE message 403. For example, the UE 102 and the target network 104-2 engage in a TAU procedure 418, which is successfully completed in the illustrated embodiment. In addition, after completing the TAU procedure 418, the target network 104-2 signals that it is attempting to complete the call by transmitting a SIP TRYING message 419, which triggers the SIP timer management module 238 to stop the SIP RequestTimeout timer 244-1 restarted at block 416. The process of attempting to complete the IMS call using the target network 104-2 can then proceed using a standardized process, with the remaining restarted and still running SIP timers controlling the behavior of the UE 102 in response to corresponding conditions as the process progresses.

[0030] Figure 5 A combined method ladder diagram 500 is shown, which illustrates triggering an EPSFB attempt in response to failure to receive an RRC Release with Redirect message from the 5G NR source network 104-1. Figure 4 The operation of UE 102 in the scenario is similar to that in the scenario. However, Figure 5 The difference in the scenario is that UE 102 and target network 104-2 (target network #1) cannot complete the TAU procedure, so UE 102 initiates a second fallback, in this case a CSFB procedure, to fall back to another target network 104-3 (target network #2) ( Figure 1 400). Thus, as with diagram 400, diagram 500 includes blocks 402 to 412, which represent initiating an IMS call to source network 104-1 via SIP INVITE message 403, starting appropriate SIP timers, expiring SIP RequestTimeout timer 244-1 due to no reply SIP message or RRC message being received, determining whether an EPSFB attempt is appropriate, and if so, switching to target RAT #1 at block 514, and then restarting the running and expired SIP timer at block 516 (using an offset in some embodiments) in response to the above conditions being met.

[0031] However, with Figure 4 The scene is different. Figure 5 , the TAU procedure 519 is not completed with the target network 104-2 (target #1), which in turn causes the re-started (and extended) SIP RequestTimeout timer 244-1 to expire (block 520). The second expiration of the SIP RequestTimeout timer 244-1 signals to the UE 102 to end the current dialing attempt, and instead, initiate a silent redial of the call over the target #2 RAT (target network 104-3) at block 522, such as via a CSFB attempt 523 with the 3G RAN represented by the target network 104-3. For this attempt, if IMS is available on the target network 104-3, the SIP timer management module 238 restarts all running SIP timers 244 (and expired SIP RequestTimeout timer 244-1) using the offset, and continues the CSFB attempt using these re-started (and extended) timers. However, if the IMS is not available on the target network 104-3, the SIP timer management module 238 stops all running SIP timers and then attempts a silent redial through the circuit-switched network represented by the target network 104-3.

[0032] Figure 6A combined method ladder diagram 600 is shown, which illustrates the operation of UE 102 in a scenario where an EPSFB attempt is triggered in response to a failure to receive a dedicated bearer for media related to an IMS call from source network 104-1. At box 602, UE 102 initiates an IMS call via 5G NR by transmitting a SIP INVITE message 603 to source network 104-1. In response to the transmission of SIP INVITE message 603, at box 604, SIP timer management module 238 starts an appropriate SIP timer 244. Since source network 104-1 is not configured to support IMS calls (e.g., VoNR) over 5G NR for UE 102 in this scenario, source network 104-1 responds to SIP INVITE message 603 with a SIP TRYING message 605 to indicate that an extended search is being performed, which may take a considerable amount of time. In response to the SIP TRYING message 605, the SIP timer management module 238 stops the appropriate SIP timers, such as the SIP RequestTimeout timer 244-1 and the SIP B timer 244-B.

[0033] In addition, in this scenario, the source network 104-1 cannot confirm receipt of the SIP INVITE message at the destination, and therefore, the source network 104-1 does not reply with a SIP 180 RINGING message, but instead replies with a SIP 183 PROGRESS message 607 to indicate that call setup is still in progress. In addition, the SIP 183 PROGRESS message 607 includes a Session Description Protocol (SDP) field that indicates a prerequisite for establishing a dedicated bearer for the media of the attempted call. Receipt of the SIP 183 PROGRESS message 607 with this SDP prerequisite triggers the SIP timer management module 238 to start the SIP QoS Reservation timer 244-2 at box 608. However, in this case, no RRCRelease with Redirect message is received from the source network 104-1, indicating that a dedicated bearer has not yet been established for the IMS call, and therefore the SIP QoS Reservation timer 244-2 eventually expires at box 610.

[0034] The expiration of the SIP QoS Reservation timer 244-2 would normally trigger the UE to terminate the attempted call via transmission of a SIP CANCEL message or a SIP 680 Preconditions Failure message. However, in at least one embodiment, the UE 102 uses a restarted (and extended) SIP timer to implement a fallback attempt in response to the condition for the expiration of the QoS Reservation timer 244-2 being met, rather than causing the attempted call to fail at this time. Thus, at block 612, the UE 102 determines whether VoNR is disabled or otherwise unavailable to support packet-switched calls via the UE 102, and whether the UE 102 is currently using a 5G NR RAT (e.g., RAT 212-1, Figure 2 ). If any of these conditions is false (or "no"), a UE-initiated fallback attempt is not recommended, so the UE 102 defaults to a conventional approach at block 614, where the UE 102 terminates the call attempt via transmission of a SIP CANCEL message 613.

[0035] However, if both conditions are true (or "yes"), then at block 616, UE 102 acknowledges that a RRCRelease with Redirect message has not been received. If such a message has in fact been received, but SIPRequestTimeout timer 244-1 has expired, then an EPSFB attempt is not recommended, so UE 102 defaults to the conventional method of terminating the attempted call via transmission of SIP CANCEL message 613 at block 614. Otherwise, if a RRCRelease with Redirect message is not received, UE 102 proceeds with a fallback attempt by attempting to camp on target network 104-2 with IMS. Thus, at block 618, UE 102 switches from the source RAT to the target RAT (e.g., from using RAT 212-1 to using RAT 212-2), and at block 620, UE 102 restarts some or all running (or expired) SIP timers (including expired SIP QoS Reservation timer 244-2), and in some embodiments, adds the same or different offsets to some or all restarted SIP timers. This SIP timer restart (with the additional offset) prepares UE 102 to initiate execution of the sub-procedure of the EFSFB procedure without premature termination due to expiration of the SIP timer originally started by issuing SIP INVITE message 603. For example, UE 102 and target network 104-2 engage in a TAU procedure 621, which completes successfully in the illustrated embodiment. The process of attempting to complete the IMS call using target network 104-2 may then proceed using standardized procedures, with the remaining restarted and still running SIP timers controlling the behavior of UE 102 in response to corresponding conditions as the process progresses.

[0036] The above described systems and techniques may be further better understood by considering the following examples, either alone or in combination:

[0037] Example 1: A method implemented at a user equipment (UE), the method comprising: initiating a packet-switched call via a first radio access technology (RAT), starting multiple Session Initiation Protocol (SIP) timers in response to initiating the call, and restarting a set of multiple SIP timers for a fallback procedure in response to at least one condition existing when initiating a fallback procedure for the call.

[0038] Example 2: The method of Example 1, wherein each SIP timer has a corresponding default timer duration, and restarting the SIP timers in the set comprises restarting using a start duration equal to the sum of the default timer duration and an offset.

[0039] Example 3: The method of Example 2, wherein the offset is the same for each SIP timer in the set.

[0040] Example 4: The method of Example 2, wherein an offset of one SIP timer in the set is different from an offset of another SIP timer in the set.

[0041] Example 5: The method of any one of Examples 1 to 4, wherein the set is a plurality of SIP timers.

[0042] Example 6: The method of any one of Examples 1 to 5, wherein the set of one or more SIP timers includes at least one of a SIP RequestTimeout timer or a SIP Quality of Service (QoS) Reservation timer.

[0043] Example 7: The method of any one of Examples 1 to 6, wherein the first RAT is a fifth generation new radio (5GNR) RAT, and the fallback procedure is an evolved packet system (EPS) fallback (EPSFB) procedure.

[0044] Example 8: The method of any one of Examples 1 to 7, wherein starting the plurality of SIP timers comprises starting the plurality of SIP timers in response to transmission of a SIP INVITE message by the UE to the first network via the first RAT.

[0045] Example 9: The method of Example 8, wherein the at least one condition includes receiving a Release with Redirect message from the first network and determining that the second network can support packet switched calls.

[0046] Example 10: The method of Example 8, wherein the at least one condition includes failure to receive a Release with Redirect message before expiration of a SIPRequestTimeout timer among the plurality of SIP timers, and determining that the UE is not available to support packet-switched calls using the first RAT.

[0047] Example 11: A method as described in Example 8, wherein at least one condition includes expiration of a SIP Quality of Service (QoS) Reservation timer after the first network fails to establish a dedicated bearer for the packet-switched call, fails to receive a Release and Redirect message from the first network, and determines that the UE is not available to support packet-switched calls using the first RAT.

[0048] Example 12: The method of any of Examples 1 to 6, wherein the first RAT is a fourth generation long term evolution (4G LTE) RAT, and the fallback procedure is a circuit switched fallback (CSFB) procedure.

[0049] Example 13: A user equipment (UE) comprising: at least one modem, at least one radio frequency (RF) transceiver, and at least one RF antenna array configured to support multiple radio access technologies (RATs); at least one processor coupled to the at least one modem, at least one RF transceiver, and at least one RF antenna array; and at least one memory coupled to the at least one processor, the at least one memory storing one or more sets of executable instructions configured to manipulate one or both of the at least one modem or the at least one processor to perform a method as described in any one of Examples 1 to 12.

[0050] Example 14: A non-transitory computer-readable medium storing one or more sets of executable instructions configured to manipulate at least one processor of a user device to perform a method as described in any one of Examples 1 to 12.

[0051] Example 15: An electronic device comprising the non-transitory computer-readable medium of Example 14, and at least one processor for executing one or more sets of executable instructions.

[0052] In some embodiments, certain aspects of the techniques described above may be implemented by one or more processors of a processing system that executes software. The software includes one or more executable instruction sets stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The software may include instructions and certain data that manipulate the one or more processors to perform one or more aspects of the techniques described above when executed by one or more processors. A non-transitory computer-readable storage medium may include, for example, a magnetic or optical disk storage device, a solid-state storage device such as a flash memory, a cache, a random access memory (RAM), or one or more other non-volatile memory devices, etc. The executable instructions stored on a non-transitory computer-readable storage medium may be source code, assembly language code, object code, or other instruction formats interpreted or otherwise executed by one or more processors.

[0053] Computer-readable storage media may include any storage medium or combination of storage media that can be accessed by a computer system during use to provide instructions and / or data to the computer system. Such storage media may include, but are not limited to, optical media (e.g., compact discs (CDs), digital versatile discs (DVDs), Blu-ray discs), magnetic media (e.g., floppy disks, tapes, or magnetic hard drives), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or micro-electromechanical system (MEMS)-based storage media. Computer-readable storage media may be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., a magnetic hard drive), removably attached to a computing system (e.g., an optical disc or flash memory based on a universal serial bus (USB)), or coupled to a computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0054] It should be noted that not all activities or elements described above in the general description are required, parts of a specific activity or device may not be required, and one or more additional activities may be performed, or, in addition to those described, additional elements may be included. In addition, the order in which the activities are listed is not necessarily the order in which they are performed. In addition, the concepts have been described with reference to specific embodiments. However, it will be understood by those of ordinary skill in the art that various modifications and changes may be made without departing from the scope of the present disclosure as set forth in the appended claims. Therefore, the description and drawings will be regarded as having an illustrative rather than a restrictive meaning, and all such modifications are intended to be included within the scope of the present disclosure.

[0055] The benefits, other advantages, and solutions to the problems have been described above with respect to specific embodiments. However, the benefits, advantages, solutions to the problems, and any features that may cause any benefit, advantage, or solution to appear or become more prominent should not be interpreted as key, essential, or basic features of any or all claims. In addition, the specific embodiments disclosed above are merely illustrative, because the disclosed subject matter can be modified and practiced in different but equivalent ways that are obvious to those skilled in the art who benefit from the teachings herein. Except as described in the appended claims, it is not intended to limit the details of the construction or design shown herein. Therefore, it is obvious that the specific embodiments disclosed above can be changed or modified, and all such variations are considered to be within the scope of the disclosed subject matter. Therefore, the protection sought herein is exactly what is set forth in the appended claims.

Claims

1. A method implemented at a user equipment UE, the method include: Initiating a packet switched call via a first radio access technology RAT; In response to initiating the call, starting a plurality of Session Initiation Protocol (SIP) timers; as well as In response to at least one condition being present when a fallback procedure for the call is initiated, the set of the plurality of SIP timers is restarted for the fallback procedure.

2. The method according to claim 1, in: Each SIP timer has a corresponding default timer duration; as well as Restarting the SIP timers in the set includes restarting with a start duration equal to the sum of the default timer duration and an offset.

3. The method according to claim 2, in, The offset is the same for each SIP timer in the set.

4. The method according to claim 2, in, The offset of one SIP timer in the set is different from the offset of another SIP timer in the set.

5. The method according to any one of claims 1 to 4, in, The set is the plurality of SIP timers.

6. The method according to any one of claims 1 to 5, in, The set of one or more SIP timers includes at least one of a SIP RequestTimeout timer or a SIP Quality of Service (QoS) Reservation timer.

7. The method according to any one of claims 1 to 6, in: The first RAT is a fifth generation new radio 5G NR RAT; and The fallback procedure is an Evolved Packet System EPS Fallback EPSFB procedure.

8. The method according to any one of claims 1 to 7, in, Starting the plurality of SIP timers includes starting the plurality of SIP timers in response to transmission of a SIP INVITE message by the UE to a first network via the first RAT.

9. The method according to claim 8, in, The at least one condition includes receiving a Release with Redirect message from the first network and determining that a second network is capable of supporting the packet switched call.

10. The method according to claim 8, in, The at least one condition includes failure to receive a Release with Redirect message before expiration of a SIP RequestTimeout timer among the plurality of SIP timers, and determining that the UE is unavailable to support the packet switched call using the first RAT.

11. The method according to claim 8, in, The at least one condition includes expiration of a SIP Quality of Service QoSReservation timer after the first network fails to establish a dedicated bearer for the packet switched call, fails to receive a Release and Redirect message from the first network, and determines that the UE is unavailable to support the packet switched call using the first RAT.

12. The method according to any one of claims 1 to 6, in: The first RAT is a fourth generation long term evolution 4G LTE RAT; and The fallback process is a Circuit Switched Fallback CSFB process.

13. A user equipment UE, include: at least one modem, at least one radio frequency (RF) transceiver, and at least one RF antenna array, wherein the at least one modem, the at least one RF transceiver, and the at least one RF antenna array are configured to support multiple radio access technologies (RATs); at least one processor coupled to the at least one modem, the at least one RF transceiver, and the at least one RF antenna array; as well as At least one memory, the at least one memory being coupled to the at least one processor, the at least one memory storing one or more sets of executable instructions, the one or more sets of executable instructions being configured to manipulate one or both of the at least one modem or the at least one processor to perform the method of any one of claims 1 to 12.

14. A non-transitory computer-readable medium storing one or more sets of executable instructions configured to manipulate at least one processor of a user device to perform the method of any one of claims 1 to 12.

15. An electronic device, include: The non-transitory computer readable medium of claim 14; as well as At least one processor, the at least one processor is configured to execute one or more sets of executable instructions.