Silent internet protocol multimedia subsystem service recovery based on retry-after header with best-effort

WO2024263157A1PCT designated stage expired Publication Date: 2024-12-26GOOGLE LLC

Patent Information

Application Number
PCT/US2023/025765
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-20
Publication Date
2024-12-26

Smart Images

  • Figure US2023025765_26122024_PF_FP_ABST
    Figure US2023025765_26122024_PF_FP_ABST
Patent Text Reader

Abstract

A user equipment (UE) device (102) in a mobile cellular network (100) implements one or more techniques to recover from session initiation protocol (SIP) errors. For example, the UE device selectively performs one or more SIP error recovery procedures based on one or more SIP error recovery criteria in response to receiving a temporary SIP error message (405, 505) from an Internet Protocol Multimedia Subsystem (IMS) network (126).
Need to check novelty before this filing date? Find Prior Art

Description

SILENT INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM SERVICE RECOVERY BASED ON RETRY-AFTER HEADER WITH BEST-EFFORTBACKGROUND

[0001] In some instances, a user equipment device (UE) in a cellular network initiates an internet protocol (IP) multimedia subsystem (IMS) service (e.g., IMS voice call initiation or IMS video call initiation) with an IMS network via a radio access network (RAN) and a core network. As part of establishing the IMS service, the originating (and terminating) UE sends various IMS signaling messages, such as a session initiation protocol (SIP) message, to the IMS network. For example, the UE sends a SIP INVITE request to establish a call session. The IMS network routes the INVITE request to network components associated with the terminating UE. The terminating UE sends a SIP 180 Ringing response, which indicates that the call is being alerted, to the IMS network. The IMS network then sends the SIP 180 Ringing response to the originating UE, which can play a ringback tone to indicate that the terminating UE is being alerted. When the terminating UE answers the call, the terminating UE sends a SIP 200 OK response to the IMS network, which is forwarded to the originating UE. The originating UE then sends a SIP ACK message to confirm the reception of the SIP 200 OK response from the terminating UE. Once the terminating UE receives the SIP ACK message from the originating UE, both UEs are able to start exchanging media.SUMMARY OF EMBODIMENTS

[0002] In accordance with one aspect, a method for selectively performing one or more recovery procedures for session initiation protocol (SIP) errors at a user equipment (UE) device includes, responsive to receiving a temporary SIP error message from an Internet Protocol Multimedia Subsystem (IMS) network, selectively performing one or more SIP error recovery procedures based on one or more SIP error recovery criteria.

[0003] In at least some embodiments, the temporary SIP error message is received in response to transmitting an IMS signaling message to the IMS network to initiate an IMS service.

[0004] In at least some embodiments, selectively performing the one or more SIP error recovery procedures includes, responsive to determining that the temporary SIP error message specifies a duration of time to wait before performing a SIP error recovery procedure, incrementing a SIP error message count; and responsive to determining, based on the SIP error message count, that a SIP error recovery criterion of the plurality SIP error recovery criteria is satisfied, selecting a corresponding SIP error recovery procedure from a plurality of SIP error recovery procedures.

[0005] In at least some embodiments, determining that the SIP error recovery criterion of the plurality SIP error recovery criteria is satisfied includes comparing the SIP error message count to a threshold value.

[0006] In at least some embodiments, the threshold value is a maximum number of allowed silent retry procedures.

[0007] In at least some embodiments, the method further includes at least one of: determining that a first SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being less than the threshold value; determining that a second SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being equal to the threshold value; or determining that a third SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being greater than the threshold value.

[0008] In at least some embodiments, selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria includes, responsive to selecting a first SIP error recovery procedure of a plurality of SIP error recovery procedures based on the one or more SIP error recovery criteria, waiting for a duration of time specified by the temporary SIP error message; and responsive tothe duration of time expiring, performing a retry process for an IMS signaling message associated with the temporary SIP error message.

[0009] In at least some embodiments, selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria includes, responsive to selecting a second SIP error recovery procedure of a plurality of SIP error recovery procedures based on the one or more SIP error recovery criteria, clearing a current call session established with the IMS network; performing an IMS recovery procedure comprising deregistering from the IMS network and re-registering with the IMS network; and responsive to the IMS recovery procedure having completed within a first threshold amount of time, performing a final retry process for an IMS signaling message associated with the temporary SIP error message.

[0010] In at least some embodiments, re-registering with the IMS network includes selecting a Proxy Call Session Control Function (P-CSCF) that is different from the P- CSCF associated with the call session that was cleared.

[0011] In at least some embodiments, performing the final retry process includes, responsive to the IMS recovery procedure having completed within a second threshold amount of time, waiting for a first duration of time based on a second duration of time specified by the temporary SIP error message, responsive to the first duration of time expiring, performing the final retry process for the IMS signaling message; and responsive to the IMS recovery procedure having completed after a second threshold amount of time, immediately performing the final retry process for the IMS signaling message.

[0012] In at least some embodiments, selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria includes, responsive to the IMS recovery procedure having completed after the first threshold amount of time, refraining from performing a retry process for the IMS signaling message.

[0013] In at least some embodiments, selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria includes, responsive to selecting a third SIP error recovery procedure of a plurality of SIP errorrecovery procedures based on the one or more SIP error recovery criteria, refraining from performing a retry process for an IMS signaling message associated with the temporary SIP error message.

[0014] In at least some embodiments, the temporary SIP error message is a SIP INVITE error message.

[0015] In accordance with another aspect, a user equipment device includes one or more radio frequency (RF) modems configured to wirelessly communicate with at least one network; one or more processors coupled to the one or more RF modems; and at least one memory storing executable instructions, the executable instructions configured to manipulate at least one of the one or more processors or the one or more RF modems to perform the methods described above and herein.

[0016] In accordance with a further aspect, a computer-readable storage medium embodies a set of executable instructions, the set of executable instructions to manipulate a user equipment device to perform the methods described above and herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art, by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

[0018] FIG. 1 is a diagram illustrating an example wireless system employing a UE configured to selectively perform one or more SIP INVITE error recovery procedures in accordance with some embodiments.

[0019] FIG. 2 is a block diagram illustrating example modes of a SIP INVITE error recovery mechanism employed by the UE device of FIG. 1 in accordance with some embodiments.

[0020] FIG. 3 is a diagram illustrating an example hardware configuration of a user equipment of the wireless system of FIG. 1 in accordance with some embodiments.

[0021] FIG. 4 illustrates a diagram of an example method of selectively performing SIP INVITE error recovery procedures or techniques in accordance with some embodiments.

[0022] FIG. 5 illustrates a diagram of another example method of selectively performing SIP INVITE error recovery procedures or techniques in accordance with some embodiments.DETAILED DESCRIPTION

[0023] When establishing an IMS service, a UE may receive an error from an IMS network. For example, after the UE sends a SIP INVITE request to the IMS network for initiating a voice (or video) call, the UE may receive temporary SIP INVITE errors, such as a SIP 500 Internal Server Error response, from the IMS network. A SIP INVITE error is typically associated with a retry-after header, which indicates a duration of time the UE is to wait before retrying the SIP INVITE request. After the specified duration of time has passed, the UE performs a silent retry, which is a mechanism used by the UE to reattempt call establishment or session initiation without causing any disruption or audible notification to the user. However, if the IMS network has not resolved the issue that prompted the first SIP INVITE error or is experiencing a new issue, the UE may continually receive SIP INVITE errors with gradually increasing retry-after headers. For example, the UE attempts to establish an IMS service by sending a SIP INVITE request to the IMS network. The IMS network is not able to grant the SIP invite request and sends a first SIP INVITE error with a retry-after header of 2 seconds to the UE. In response to receiving the first SIP INVITE error, the UE waits 2 seconds and performs a silent retry for the SIP INVITE. The IMS network is still experiencing an issue and responds with a second SIP INVITE error with a retry-after header of 8 seconds to the UE. In response to receiving the first SIP INVITE error, the UE waits 8 seconds and performs another silent retry for the SIP INVITE. This process can continue for many more cycles resulting in a poor user experience or the eventual failure to establish the IMS service with the IMS network.

[0024] As such, the following describes embodiments of systems and methods for a UE device to increase the likelihood that a silent retry process will be successful and to avoid a continual loop of SIP INVITE errors when performing silent IMS recovery based on retry-after headers. As described below, the UE device is configured to implement different SIP INVITE error recovery techniques based on the current SIP INVITE error count n (for SIP INVITE errors with a retry-after header) and a specified maximum number N of allowed silent retry procedures (also referred to here as “retries”). Stated differently, the UE device selectively performs one or more SIP error recovery procedures by selecting a SIP error recovery procedure corresponding to a SIP error recovery criterion based on the current SIP INVITE error count n and the specified maximum number N of allowed silent retries.

[0025] For example, after sending a SIP INVITE request, if the UE receives a SIP INVITE error with a retry-after header and the SIP INVITE error count is less than the specified maximum number of silent retries (n < A / ), the UE performs a silent retry for the SIP INVITE request according to one or more specifications, such as the Request for Comments (RFC) 3261 Specification published by the Internet Engineering Task Force (IETF) in June 2002. If the UE receives a SIP INVITE error with a retry-after header and the SIP INVITE error count is equal to the specified maximum number of silent retries (n = N), the UE performs a silent IMS recovery process and then a silent retry for the SIP INVITE request based on the retry-after header of the SIP INVITE error with a best-effort procedure. If the UE receives a SIP INVITE error with a retry- after header and the SIP INVITE error count is equal to the specified maximum number of silent retries plus one (n = N + 1), the UE stops or does not perform a silent retry for the SIP INVITE request and operates according to one or more specifications, such as the RFC 3261 Specification. It should be understood that the SIP INVITE error recovery techniques described herein are applicable to any SIP INVITE errors with a retry-after header, including Specification defined SIP INVITE errors with a retry-after header and mobile network operator-defined SIP INVITE errors with a retry-after header.

[0026] For ease of illustration, the following techniques are described in an example context in which one or more UE devices and one or more RANs implement at least aFifth Generation (5G) New Radio (NR) standard (e.g., Third Generation Partnership Project (3GPP) Release 15, 3GPP Release 16, etc.) (hereinafter, "5G NR" or"5G NR standard"). However, it should be understood that the present disclosure is not limited to networks employing a 5G NR RAT configuration, but rather the techniques described herein can be applied to any combination of different RATs employed at the UE devices and the RANs. It should also be understood that the present disclosure is not limited to any specific network configurations or architectures described herein for implementing radio link failure detection at the UE. Instead, techniques described herein can be applied to any configuration of RANs. Also, the present disclosure is not limited to the examples and context described herein, but rather the techniques described herein can be applied to any network environment where a UE device implements SIP INVITE error recovery techniques.

[0027] FIG. 1 illustrates a mobile cellular network (system) 100 in accordance with at least some embodiments. As shown, the mobile cellular network 100 includes a user equipment (UE) device 102 that is configured to communicate with one or more base stations (BSs) 104 (illustrated as BS 104-1 and BS 104-2) through one or more wireless communication links 106 (illustrated as wireless links 106-1 and 106-2). The UE device 102, in at least some embodiments, includes any of a variety of wireless communication devices, such as a cellular phone, a cellular-enabled tablet computer or cellular-enabled notebook computer, a cellular-enabled wearable device, an automobile, or other vehicle employing cellular services (e.g., for navigation, provision of entertainment services, in-vehicle mobile hotspots, etc.), and so on. In at least some embodiments, the UE device 102 employs a single RAT 108. In other embodiments, the UE device 102 is a multi-mode UE device that employs multiple RATs 108 (illustrated as RAT 108-1 and RAT 108-2). Examples of multiple RATs include a 3GPP Long-Term Evolution (3GPP LTE) RAT 108-1 and a 3GPP Fifth Generation New Radio (5G NR) RAT 108-2.

[0028] In at least some embodiments, the BSs 104 are implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof. Examples of base stations 104 include an Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), Evolved Node B (eNodeB or eNB), Next Generation(NG or NGEN) Node B (gNode B or gNB), and so on. The BSs 104 communicate with the UE device 102 via the wireless links 106, which are implemented using any suitable type of wireless link. The wireless links 106, in at least some embodiments, include a downlink of data and control information communicated from the base stations 104 to the UE device 102, an uplink of data and control information communicated from the UE device 102 to the BSs 104, or both. In at least some embodiments, the wireless links 106 (or bearers), such as data radio bearers (DRBs) and signal radio bearers (SRBs), are implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3GPP 4G LTE, 5G NR, and so on. In at least some embodiments, multiple wireless links 106 are aggregated in a carrier aggregation to provide a higher data rate for the UE device 102. Also, multiple wireless links 106 from multiple base stations 104 are configured, in at least some embodiments, for coordinated multipoint (CoMP) communication with the UE device 102, as well as dual connectivity, such as single-RAT LTE-LTE or NR-NR dual connectivity, or multi-radio access technology (Multi-RAT) dual connectivity (MR-DC) including E-UTRA-NR dual connectivity (EN- DC), NGEN radio access network (RAN) E-UTRA-NR dual connectivity (NGEN-DC), and NR E-UTRA dual connectivity (NE-DC).

[0029] The BSs 104 collectively form a Radio Access Network (RAN) 110, such as an E-UTRAN or 5G NR RAN. The base stations 104 are connected to a core network (CN) 112 (illustrated as CN 112-1 and CN 112-2) via control-plane and userplane interfaces through one or more links 114 (illustrated as link 114-1 and link 114- 2). Depending on the configuration of the mobile cellular network 100, the core network 112 is either an Evolved Packet Core (EPC) network 112-1 or a 5G Core Network (5GC) 112-2. For example, in an E-UTRAN configuration or a 5G non- standalone (NSA) EN-DC configuration, the core network 112 is an EPC network 112-1 that includes, for example, a Mobility Management Entity (MME) 116, a Serving Gateway (SGW) 118, and a Packet Data Network Gateway (PGW) 120. The MME 116 provides control-plane functions, such as registration and authentication of multiple UE devices 102, authorization, mobility management, and so on. The SGW 118 transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The PGW 120 provides connectivity from the UE device 102 to externalpacket data networks 122, such as the Internet 124 and an IMS network 126, by being the point of exit and entry of traffic for the LIE device 102. In a 5G standalone (SA) configuration or an NSA NE-DC or NGEN-DC configuration, the core network 112 is a 5GC network 112-2. The 5GC 112-2 includes, for example, an Access and Mobility Management function (AMF) 128 and a User Plane Function (UPF) 130, and a Session Management Function (SMF) 132. The AMF 128 provides control-plane functions such as registration and authentication of multiple UE devices 102, authorization, mobility management, and so on. The UPF 130 transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The SMF 132 manages protocol data unit (PDU) sessions.

[0030] In at least some embodiments, the core network 112 communicatively couples the UE device 102 to an IMS network 126 via the RAN 110. The IMS network 126 provides various IMS services to the UE device 102, such as IMS short messages, IMS unstructured supplementary service data (USSD), IMS value added service data, IMS supplementary service data, IMS voice calls, and IMS video calls. To this end, an entity (e.g., a server or a group of servers) operating in the IMS network 126 supports packet exchange with the UE device 102. The packets convey signaling (such as session initiation protocol (SIP) messages, IP messages, or other suitable messages) as well as data (or media), such as voice or video. In at least some embodiments, the IMS network includes entities (not shown) such as a Proxy Call Session Control Function (P-CSCF), an Interrogating Call Session Control Function (l-CSCF), a Serving Call Session Control Function (S-CSCF), a Home Subscriber Server (HSS), a Media Gateway Control Function (MGCF), and the like.

[0031] As described above, during IMS service initiation, the UE device 102 sends an IMS signaling message, such as a SIP INVITE request, to the IMS network 126. However, the UE may receive an error from the IMS network. For example, after the UE sends a SIP INVITE request to the IMS network for initiating a voice (or video) call, the UE may receive temporary SIP INVITE errors (e.g., SIP 403, SIP 486, SIP 500, SIP 503, SIP 600, etc.) that are associated with a retry-after header. After the specified duration of time has passed, the UE performs a silent retry for the SIP INVITE request. However, the UE device 102 may continually receive A SIP INVITEerror with a gradually increasing retry-after header if the IMS network 126 continues to experience a problem condition which results in a poor user experience or the eventual failure to establish the IMS service with the IMS network 126.

[0032] However, the UE device 102 of one or more embodiments employs at least one SIP INVITE error recovery mechanism 134 that recovers from SIP INVITE errors, mitigates SIP INVITE error loops, and increases the likelihood that a silent retry will be successful. The SIP INVITE error recovery mechanism 134 includes one or more modes or operations that allow the UE device 102 to recover from a SIP INVITE error loop or mitigate poor user experience resulting from the SIP INVITE error loop. For example, FIG. 2 illustrates various example modes employed singularly or in various combinations by the UE device 102 as part of the SIP INVITE error recovery mechanism 134 in accordance with at least some embodiments. Each of these modes is discussed in greater detail below with respect to FIG. 3 to FIG. 5. One such mode includes a first SIP INVITE error recovery mode 202. During this mode, the SIP INVITE error recovery mechanism 134 performs a silent retry for a SIP INVITE request based on one or more specifications, such as the RFC 3261 Specification. In more detail, after sending a SIP INVITE request, if the UE device 102 receives a SIP INVITE error with a retry-after header from the IMS network 126, the UE device 102 processes a current SIP INVITE error count n (for SIP INVITE errors with a retry-after header) and a specified maximum number N of silent retries. If the SIP INVITE error count is less than the specified maximum number of silent retries (n < N), the UE device 102 performs a silent retry for the SIP INVITE request according to one or more specifications (e.g., the RFC 3261 Specification).

[0033] Another mode includes a second SIP INVITE error recovery mode 204. During this mode, the SIP INVITE error recovery mechanism 134 performs a silent IMS recovery procedure and then performs a silent retry for the SIP INVITE request based on the retry-after header of the SIP INVITE error using a best-effort process. In more detail, after sending a SIP INVITE request, if the UE device 102 receives a SIP INVITE error with a retry-after header from the IMS network 126, the UE device 102 processes the current SIP INVITE error count n and the specified maximum number N of silent retries. If the SIP INVITE error count is equal to the specifiedmaximum number of silent retries (n = N), the UE performs a silent IMS recovery process, including an IMS deregistration procedure and an IMS registration procedure, and then performs a silent retry for the SIP INVITE request based on the retry-after header of the SIP INVITE error with a best-effort procedure.

[0034] An additional mode includes a third IMS service issue mitigation mode 206. During this mode, the SIP INVITE error recovery mechanism 134 stops or does not perform the silent retry process for the SIP INVITE request. In more detail, after sending a SIP INVITE request, if the UE device 102 receives a SIP INVITE error with a retry-after header from the IMS network 126, the UE device 102 processes the current SIP INVITE error count n and the specified maximum number / V of silent retries. If the SIP INVITE error count is equal to the specified maximum number of silent retries plus one (n = / V + 1), the UE device 102 stops or does not perform a silent retry for the SIP INVITE request and operates according to one or more specifications (e.g., the RFC 3261 Specification).

[0035] FIG. 3 illustrates an example device diagram 300 of a UE device 102. In at least some embodiments, the device diagram 300 describes a UE device that implements the SIP INVITE error recovery techniques described herein. The UE device 102 may include additional functions and interfaces that are omitted from FIG. 3 for the sake of clarity. The UE device 102, in at least some embodiments, includes antennas 302, a radio frequency (RF) front end 304, and one or more RF transceivers 306 (e.g., a 3GPP 4G LTE transceiver 306-1 and a 5G NR transceiver 306-2) for communicating with one or more base stations 104 in a RAN 110, such as a 5G RAN, an E-UTRAN, a combination thereof, and so on. The RF front end 304, in at least some embodiments, includes a transmitting (Tx) front end 304-1 and a receiving (Rx) front end 304-2. The Tx front end 304-1 includes components such as one or more power amplifiers (PA), drivers, mixers, filters, and so on. The Rx front end 304-2 includes components such as low-noise amplifiers (LNAs), mixers, filters, and so on. The RF front end 304, in at least some embodiments, couples or connects the one or more transceivers 306, such as the LTE transceiver 306-1 and the 5G NR transceiver 306-2, to the antennas 302 to facilitate various types of wireless communication.

[0036] In at least some embodiments, the antennas 302 of the LIE device 102 include an array of multiple antennas configured similarly to or different from each other. The antennas 302 and the RF front end 304, in at least some embodiments, are tuned to or are tunable to one or more frequency bands, such as those defined by the 3GPP LTE, 3GPP 5G NR, IEEE wireless local area network (WLAN), IEEE wireless metropolitan area network (WMAN), or other communication standards. In at least some embodiments, the antennas 302, the RF front end 304, the LTE transceiver 306-1 , and the 5G NR transceiver 306-2 are configured to support beamforming (e.g., analog, digital, or hybrid) or in-phase and quadrature (l / Q) operations (e.g., I / Q modulation or demodulation operations) for the transmission and reception of communications with one or more base stations 104. By way of example, the antennas 302 and the RF front end 304 operate in sub-gigahertz bands, sub-6 GHz bands, above 6 GHz bands, or a combination of these bands defined by the 3GPP LTE, 3GPP 5G NR, or other communication standards.

[0037] In at least some embodiments, the antennas 302 include one or more receiving antennas positioned in a one-dimensional shape (e.g., a line) or a two- dimensional shape (e.g., a triangle, a rectangle, or an L-shape) for implementations that include three or more receiving antenna elements. While the one-dimensional shape enables the measurement of one angular dimension (e.g., an azimuth or an elevation), the two-dimensional shape enables two angular dimensions to be measured (e.g., both azimuth and elevation). Using at least a portion of the antennas 302, the UE device 102 can form beams that are steered or un-steered, wide or narrow, or shaped (e.g., as a hemisphere, cube, fan, cone, or cylinder). The one or more transmitting antennas may have an un-steered omnidirectional radiation pattern or may produce a wide steerable beam. Either of these techniques enables the UE device 102 to transmit a radio signal to illuminate a large volume of space. In some embodiments, the receiving antennas generate thousands of narrow steered beams (e.g., 2000 beams, 4000 beams, or 6000 beams) with digital beamforming to achieve desired levels of angular accuracy and angular resolution.

[0038] The UE device 102, in at least some embodiments, includes one or more sensors 308 implemented to detect various properties such as one or more oftemperature, supplied power, power usage, battery state, or the like. Examples of sensors include a thermal sensor, a battery sensor, a power usage sensor, and so on.

[0039] The LIE device 102 also includes at least one processor 310. The processor 310, in at least some embodiments, is a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. In at least some embodiments, the processor 310 is implemented at least partially in hardware, including, for example, components of an integrated circuit or a system-on-a-chip (SoC), a digital-signal-processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), other implementations in silicon or other hardware, or a combination thereof.

[0040] Examples of the processor(s) 310 include a communication processor, an application processor, microprocessors, DSPs, controllers, and so on. A communication processor, in at least some embodiments, is implemented as a modem baseband processor, software-defined radio module, configurable modem (e.g., multi-mode, multi-band modem), wireless data interface, wireless modem, or so on. In at least some embodiments, a communication processor supports one or more of data access, messaging, or data-based services of a wireless network, as well as various audio-based communication (e.g., voice calls). An application processor, in at least some embodiments, provides computing resources to applications executing on the UE device 102. For example, an application provides a self-contained operating environment that delivers system capabilities (e.g., graphics processing, memory management, and multimedia processing) to support applications executing on the UE device 102.

[0041] The UE device 102 further includes a non-transitory computer-readable storage media 312 (CRM 312). The computer-readable storage media described herein excludes propagating signals. The CRM 312, in at least some embodiments, includes any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 314 of theUE device 102. In at least some embodiments, the device data 314 includes user data, multimedia data, beamforming codebooks, applications 316, a user interface(s) 318, an operating system of the UE device 102, and so on, which are executable by the processor(s) 310 to enable user-plane communication, control-plane signaling, and user interaction with the UE device 102. The user interface 318, in at least one embodiment, is configured to receive inputs from a user of the UE device 102, such as to receive input from a user that defines and or facilitates one or more aspects of adverse radio link condition detection. In at least some embodiments, the user interface 318 includes a graphical user interface (GUI) that receives the input information via a touch input. In other instances, the user interface 318 includes an intelligent assistant that receives the input information via an audible input or speech. Alternatively, or additionally, the operating system of the UE device 102 is maintained as firmware or an application on the CRM 312 and executed by the processor(s) 310.

[0042] The CRM 312, in at least some embodiments, the CRM 312 further includes a SIP INVITE error counter 320, SIP INVITE error recovery data 322, and either or both of a communication manager 324 and a SIP INVITE error recovery module 326. Alternatively, or additionally, either or both of the communication manager 324 and the SIP INVITE error recovery module 326, in at least some embodiments, are implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE device 102. The SIP INVITE error counter 320 maintains a count n of temporary SIP error messages, such as SIP INVITE errors, with a retry-after header that are received by the UE device 102. The SIP INVITE error recovery data 322, in at least some embodiments, includes data, such as thresholds, parameters, or criteria used by the SIP INVITE error recovery module 326 when performing the SIP INVITE error recovery techniques described herein. For example, in at least some embodiments, the INVITE error recovery data 322 includes the maximum number of allowed silent retries N that the SIP INVITE error recovery module 326 compares against the SIP INVITE error count to determine which one of the SIP INVITE error recovery modes to implement. The maximum number of allowed silent retries N, in at least some embodiments, is specified by the mobile network operator, the IMS network, or the like. In at leastsome embodiments, the maximum number of allowed silent retries N is considered a threshold value.

[0043] In at least some embodiments, the communication manager 324 configures the RF front end 304, the LTE transceiver (modem) 306-1 , the 5G NR transceiver (modem) 306-2, or a combination thereof, to perform one or more wireless communication operations. The SIP INVITE error recovery module 326, in at least some embodiments, implements the SIP INVITE error recovery mechanism 134 for recovering from SIP INVITE errors, mitigating SIP INVITE error loops, and increasing the likelihood that a silent retry will be successful. For example, the INVITE error recovery module 326 is configured to selectively perform in one or more modes, including the first mode 202, in which silent retries are performed according to one or more specifications (e.g., the RFC 3261 Specification), the second mode 204 in which a silent IMS recovery procedure is performed and then a silent retry for the SIP INVITE request is performed based on the retry-after header of the SIP INVITE error using a best-effort process, and a third mode in which the silent retry for the SIP INVITE request is stopped or not performed.

[0044] In more detail, when the UE device 102 receives a SIP INVITE error with a retry-after header from the IMS network 126, the SIP INVITE error counter 320 increments the SIP INVITE error count n. The SIP INVITE error recovery module 326 checks the current SIP INVITE error count n against one or more values or thresholds to determine if one or more SIP INVITE error recovery criteria (also referred to herein as “SIP error recovery criteria”) are satisfied. For example, the UE device 102 compares the SIP INVITE error count n to a threshold or value, such as the maximum number of allowed silent retries N, to determine if one or more SIP INVITE error recovery criteria are satisfied. In at least some embodiments, a first criterion is that the SIP INVITE error count is less than (n < N), a second criterion is that the maximum number of allowed silent retries is equal to the SIP INVITE error count (N = n), and a third criterion is that SIP INVITE error count is equal to the maximum number of allowed silent retries plus one n = N +1), that is, the SIP INVITE error count is greater than the maximum number of allowed silent retries (n > N).

[0045] The SIP INVITE error recovery module 326, in at least some embodiments, selectively performs one or more SIP INVITE error recovery techniques depending on one or more of the SIP INVITE error recovery criteria that have been satisfied. For if the SIP INVITE error recovery module 326 determines that the first SIP INVITE error recovery criterion (n < N) has been satisfied, the SIP INVITE error recovery module 326 configures the UE device 102 to perform a silent retry for the SIP INVITE request according to one or more specifications, such as the RFC 3261 Specification. For example, the UE waits for the duration of time specified by the retry-after header of the SIP INVITE error. After the duration of time has expired, the UE device 102 performs a silent retry by sending another SIP INVITE request to the IMS network 126.

[0046] If the SIP INVITE error recovery module 326 determines that the second SIP INVITE error recovery criterion (n = / V) has been satisfied, the SIP INVITE error recovery module 326 configures the UE device 102 to perform a silent IMS recovery procedure and then a silent retry for the SIP INVITE request based on the retry-after header of the SIP INVITE error using a best-effort process. As part of these procedures, the UE clears the current call session. For example, the UE device 102 sends a SIP BYE request to the IMS network 126. The UE device 102 initializes a timer and performs the silent IMS recovery procedure. For example, the UE device 102 deregisters from the IMS network 126 and then re-registers with the IMS network 126. In at least some embodiments, the UE device 102 also selects a different Proxy Call Session Control Function (P-CSCF) than the P-CSCF used for the previous call session. Selecting a new P-CSCF increases the likelihood that the SIP INVITE request gets satisfied given that the previous P-CSCF has an error condition. The UE device 102 checks the timer and determines if the silent IMS recovery procedure was completed within a first threshold amount of time (10 seconds). If the silent IMS recovery procedure was not completed within the first threshold amount of time, the UE device 102 stops or does not perform a silent retry for the SIP INVITE request and the call drops. In at least some implementations, the UE device 102 proceeds according to one or more specifications, such as the RFC 3261 Specification. For example, if the UE device 102 is not registered with the IMC network 126, the UEdevice 102 continues to try and register to the IMS network 126 based on the one or more Specifications.

[0047] However, if the silent IMS recovery procedure was completed within the first threshold amount of time, the UE device 102 initiates a final silent retry process for the SIP INVITE request based on the retry-after header with a best-effort process. For example, as part of the best-effort process, the UE device 102 checks the timer and determines if the silent IMS recovery procedure was completed within a second threshold amount of time, such as the time duration (e.g., 8 seconds) specified by the retry-after header of the SIP INVITE error. If so, the UE device 102 performs the final silent retry to send another SIP INVITE request based on the retry-after header of the second SIP INVITE error. For example, if the retry-after header specified a wait time of 8 seconds, and the silent IMS recovery process was completed within 3 seconds, the UE device 102 waits another 5 seconds to perform the final silent retry.Otherwise, the UE device 102 immediately performs the final silent retry to send the SIP INVITE request to the IMS network 126. For example, if the silent IMS recovery process was completed between 8 and 10 seconds, the UE device 102 immediately sends the SIP INVITE request to the IMS network 126. If the SIP INVITE error recovery module 326 determines that the third SIP INVITE error recovery criterion (n = A / +1 or n > N) has been satisfied, the SIP INVITE error recovery module 326 configures the UE device 102 to stop (or not perform) a silent retry for the SIP INVITE request and the call drops. In at least some implementations, the UE device 102 then operates according to one or more specifications (e.g., the RFC 3261 Specification).

[0048] FIG. 4 illustrates an example method 400 for selectively performing SIP INVITE error recovery techniques in accordance with at least some embodiments. For ease of discussion, FIG. 4 illustrates method 400 using a hybrid flow / signaling diagram. Also, method 400 is not limited to the sequence of operations shown in FIG. 4, as at least some of the operations can be performed in parallel or in a different sequence. Moreover, in at least some implementations, method 400 can include one or more different operations than those shown in FIG. 4.

[0049] In at least some embodiments, method 400 initiates at block 402 after the UE device 102 registers with the IMS network 126. For example, the UE device 102, in at least some embodiments, initially performs a PDll Session Establishment procedure with the CN 112 via the RAN 110 to establish a PDU Session for a packetbased service (e.g., the IMS service). For example, the UE device 102 sends a PDU Session Establishment Request message for establishing the PDU Session to the CN 112, and the CN 112 sends a PDU Session Establishment Accept message to the UE device 102 via the RAN 110 in response. After establishing the PDU Session, the UE device 102 performs a registration procedure with the IMS network 126 via the RAN 110 and CN 112 to register with the IMS network 126. For example, the UE device 102 sends a first SIP message (e.g., REGISTER message) to the IMS network 126 via the RAN 110 and CN 112 to perform the IMS registration procedure 704. In response, the IMS network 126 sends a second SIP message (e.g., 200 OK) to the UE device 102 via the RAN 110 and CN 112 to accept the registration.

[0050] At block 402, after (or before) successfully registering to the IMS network 126, the UE device 102 receives a request, such as a dial request, for an IMS service (e.g., a voice call) from an application (or another component) of the UE device 102. The UE device 102 initiates the requested IMS service by, for example, sending a first IMS signaling message, such as a first SIP INVITE request 401 , via the RAN 110 and CN 112 to the IMS network 126. At block 404, the UE device 102 initializes the SIP INVITE error counter n, which maintains a count n of SIP INVITE errors with a retry-after header that have been received by the UE device 102 for the current call session. In at least some embodiments, the UE device 102 initializes the SIP INVITE error counter n by setting the counter n to 0 or another value. However, other counter implementations are also applicable. In response to receiving the first SIP INVITE request 401 , the IMS network 126 sends a provisional response message, such as a first SIP 100 Trying message 403, to the UE device 102. This provisional response message, in at least some embodiments, is followed by one or more specific responses.

[0051] At block 406, the UE device 102 receives a first temporary SIP error message, such as a first SIP INVITE error message 405, from the IMS network 126,informing the UE device 102 there is an issue with satisfying the first SIP INVITE request 401 . Examples of SIP INVITE error messages include SIP 486 messages, SIP 500 messages, SIP 503 messages, SIP 600 messages, and so on. In this example, the first SIP INVITE error message 405 includes a retry-after header with a duration time of 2 seconds. At block 408, in response to the first SIP INVITE error message 405 including a retry-after header, the UE device 102 increments the SIP INVITE error count n by a specified amount, such as 1. If the SIP INVITE error message does not include a retry-after header, the UE device 102 does not increment the SIP INVITE error counter n. In this example, after the SIP INVITE error count n is incremented, n =1 because the SIP INVITE error received at block 406 was the first SIP INVITE error with a retry-after header received by the UE device 102.

[0052] At block 410, the UE device 102 checks the current SIP INVITE error count n indicated by the SIP INVITE error counter 320 against one or more values or thresholds to determine if one or more SIP INVITE error recovery criteria are satisfied. For example, the UE device 102 compares the SIP INVITE error count n to a threshold or value, such as the maximum number of allowed silent retries N, to determine if one or more SIP INVITE error recovery criteria are satisfied. As described above, in at least some embodiments, a first criterion is that the SIP INVITE error count is less than (n < N), a second criterion is that the maximum number of allowed silent retries is equal to the SIP INVITE error count (N = n), and a third criterion is that SIP INVITE error count is equal to the maximum number of allowed silent retries plus one (n = A / +1), that is, the SIP INVITE error count is greater than the maximum number of allowed silent retries (n > N).

[0053] At block 410, if the UE device 102 determines that the maximum number of allowed silent retries N equals the current SIP INVITE error count n (e g., N = n) and the maximum number of allowed silent retries N is greater than 1 ( / V > 1), then second SIP INVITE error recovery criterion is satisfied, and the UE device 102 selects a second SIP INVITE error recovery procedure. At block 412, responsive to selecting the second SIP INVITE error recovery procedure, the UE device 102 performs a silent IMS recovery procedure and then performs a silent retry for the SIPINVITE request based on the retry-after header of the SIP INVITE error using a besteffort process, as described below with respect to FIG. 5.

[0054] However, in the current example, the maximum number of allowed silent retries / V is 2 (e.g., / V = 2), and the current SIP INVITE error count n is 1 (e.g., n = 1). As such, at block 410, the UE device 102 determines that the maximum number of allowed silent retries N does not equal the current SIP INVITE error count n (e.g., N = 2 + n = 7) and the maximum number of allowed silent retries N is greater than 1 (N > 1). In other words, the first SIP INVITE error recovery criterion is satisfied, and the UE device 102 selects a first SIP INVITE error recovery procedure. At block 414, responsive to selecting the first SIP INVITE error recovery procedure, the UE device 102 performs a first silent retry for the SIP INVITE request according to one or more specifications, such as the RFC 3261 Specification. For example, the UE device 102 waits for the duration of time specified by the retry-after header of the first SIP INVITE error and performs a silent retry by sending a second SIP INVITE request 407 to the IMS network 126 on the same call session.

[0055] In response to receiving the second SIP INVITE request 407, the IMS network 126 sends a provisional response message, such as a second SIP 100 Trying message 409, to the UE device 102. At block 416, the UE device 102 receives another message 411 from the IMS network 126, such as a SIP INVITE error without a retry-after header or a SIP 200 OK message, that does not require a silent retry to be performed. At block 416, the UE device 102 proceeds according to one or more specifications, such as the RFC 3261 Specification. For example, the UE device 102 stops (or does not perform) a silent retry based on a retry-after header and the call drops. At this point, the old call session is cleared. The UE device 102, in at least some implementations, performs a silent retry using a new call session on the same RAT or different RAT based on carrier requirements.

[0056] FIG. 5 illustrates another example method 500 for selectively performing SIP INVITE error recovery techniques in accordance with at least some embodiments. For ease of discussion, FIG. 5 illustrates method 500 using a hybrid flow / signaling diagram. Also, method 500 is not limited to the sequence of operations shown in FIG. 5, as at least some of the operations can be performed in parallel or ina different sequence. Moreover, in at least some implementations, method 500 can include one or more different operations than those shown in FIG. 5.

[0057] In at least some embodiments, method 500 initiates at block 502 after the UE device 102 registers with the IMS network 126 as described above with respect to FIG. 5. At block 502, after (or before) successfully registering to the IMS network 126, the UE device 102 receives a request, such as a dial request, for an IMS service (e.g., a voice call) from an application (or another component) of the UE device 102. The UE device 102 initiates the requested IMS service by, for example, sending a first IMS signaling message, such as a first SIP INVITE request 501 , via the RAN 110 and CN 112 to the IMS network 126. At block 504, the UE device 102 initializes the SIP INVITE error counter n, which maintains a count n of SIP INVITE errors with a retry-after header that have been received by the UE device 102 for the current call session. In at least some embodiments, the UE device 102 initializes the SIP INVITE error counter n by setting the counter n to 0 or another value. However, other counter implementations are also applicable. In response to receiving the first SIP INVITE request 501 , the IMS network 126 sends a provisional response message, such as a first SIP 100 Trying message 503, to the UE device 102. This provisional response message, in at least some embodiments, is followed by one or more specific responses.

[0058] At block 506, the UE device 102 receives a first temporary SIP error message, such as a first SIP INVITE error message 505, such as a SIP 500 Server Internal Error message, from the IMS network 126. In this example, the first SIP INVITE error message 505 includes a retry-after header with a duration time of 2 seconds. In response to the first SIP INVITE error message 505 including a retry- after header, the UE device 102 increments the SIP INVITE error count n to 1. If the SIP INVITE error message does not include a retry-after header, the UE device 102 does not increment the SIP INVITE error counter n. At block 508, the UE device 102 checks the current SIP INVITE error count n against the maximum number of allowed silent retries N (N = 2 in this example) and determines that the first SIP INVITE error recovery criterion is satisfied. For example, the UE device 102 determines that the SIP INVITE error count n is less than the maximum number of allowed silent retries N(e.g. , n = 1 is less than N = 2). Responsive to the first SIP INVITE error recovery criterion being satisfied, the UE device 102 selects the first SIP INVITE error recovery procedure.

[0059] At block 510, responsive to selecting the first SIP INVITE error recovery procedure, the UE device 102 performs a first silent retry for the SIP INVITE request according to one or more specifications, such as the RFC 3261 Specification. For example, the UE device 102 waits for the duration of time (e.g., 2 seconds) specified by the retry-after header of the first SIP INVITE error and performs a silent retry by sending a second SIP INVITE request 507 to the IMS network 126 on the same call session. In response to receiving the second SIP INVITE request 507, the IMS network 126 sends a provisional response message, such as a second SIP 100 Trying message 509, to the UE device 102. At block 512, the UE device 102 receives a second SIP INVITE error message 511 , such as a SIP 503 Service Unavailable message, from the IMS network 126. In this example, the second SIP INVITE error message 511 includes a retry-after header with an increased duration of time compared to the first SIP INVITE error message 505. In response to the second SIP INVITE error message 511 including a retry-after header, the UE device 102 increments the SIP INVITE error count n to 2.

[0060] At block 514, the UE device 102 checks the current SIP INVITE error count n against the maximum number of allowed silent retries N and determines that the second SIP INVITE error recovery criterion is satisfied. For example, the UE device 102 determines that the SIP INVITE error count n is equal to the maximum number of allowed silent retries N (e.g., n = 2 and N = 2, so n = N). Responsive to the second SIP INVITE error recovery criterion being satisfied, the UE device 102 selects the second SIP INVITE error recovery procedure.

[0061] At block 516, responsive to selecting the second SIP INVITE error recovery procedure, the UE device 102 clears the current call session. For example, the UE device 102 sends a SIP BYE request to the IMS network 126. The UE device 102 also initializes a timer and performs a silent IMS recovery procedure 513. For example, at block 518, the UE device 102 deregisters from the IMS network 126. At block 520, the UE device 102 registers with the IMS network 126. As part of theregistration process, the UE device 102 selects a different Proxy Call Session Control Function (P-CSCF) than the P-CSCF used for the previous call session. At block 522, the UE device 102 checks the timer and determines if the silent IMS recovery procedure was completed within a first threshold amount of time (10 seconds). At block 530, if the silent IMS recovery procedure was not completed within the first threshold amount of time, the UE device 102 stops or refrains from performing a silent retry for the second SIP INVITE request. Then, at block 532, the UE device 102 proceeds according to one or more specifications, such as the RFC 3261 Specification. For example, if the UE device 102 is not registered with the IMC network 126, the UE device 102 continues to try and register to the IMS network 126 based on the one or more Specifications.

[0062] However, at block 524, if the silent IMS recovery procedure was completed within the first threshold amount of time, the UE device 102 initiates a final silent retry to send a third SIP INVITE request 515 based on the retry-after header with a besteffort process. For example, as part of the best-effort process, the UE device 102 checks the timer and determines if the silent IMS recovery procedure was completed within a second threshold amount of time, such as the time duration (e.g., 8 seconds) specified by the retry-after header of the second SIP INVITE error message 511. If so, the UE device 102 performs the final silent retry to send to the third SIP INVITE request 515 based on the retry-after header of the second SIP INVITE error message 511. For example, if the retry-after header specified a wait time of 8 seconds, and the silent IMS recovery process was completed within 3 seconds, the UE device 102 waits another 5 seconds to perform the final silent retry. Otherwise, the UE device 102 immediately performs the final silent retry to send the third SIP INVITE request 515 to the IMS network 126. For example, if the silent IMS recovery process was completed between 8 and 10 seconds, the UE device 102 immediately sends the third SIP INVITE request 515 to the IMS network 126.

[0063] In response to receiving the third SIP INVITE request 515, the IMS network 126 sends a provisional response message, such as a second SIP 100 Trying message 517, to the UE device 102. At block 526, the UE device 102 receives a third SIP INVITE error message 519, such as a SIP 500 Server Internal errormessage, from the IMS network 126. In this example, the third SIP INVITE error message 519 includes a retry-after header. In response to the third SIP INVITE error message 519 including a retry-after header, the LIE device 102 increments the SIP INVITE error count n to 3.

[0064] At block 528, the UE device 102 checks the current SIP INVITE error count n against the maximum number of allowed silent retries N and determines that the third SIP INVITE error recovery criterion is satisfied. For example, the UE device 102 determines that the SIP INVITE error count n is greater than the maximum number of allowed silent retries N (e.g., n = 3 and N = 2, so n > N). Responsive to the third SIP INVITE error recovery criterion being satisfied, the UE device 102 selects the third SIP INVITE error recovery procedure. At block 530, responsive to selecting the third SIP INVITE error recovery procedure, the UE device 102 stops or refrains from performing a silent retry for the second SIP INVITE request. Then, at block 532, the UE device 102 proceeds according to one or more specifications, such as the RFC 3261 Specification.

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

[0066] A computer readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use toprovide instructions and / or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media (e.g., floppy disc , magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0067] Note that not all of the activities or elements described above in the general description are required, that a portion of a specific activity or device may not be required, and that one or more further activities may be performed, or elements included, in addition to those described. Still further, the order in which activities are listed are not necessarily the order in which they are performed. Also, the concepts have been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present disclosure as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure.

[0068] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any feature(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature of any or all the claims. Moreover, the particular embodiments disclosed above are illustrative only, as the disclosed subject matter may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. No limitations are intended to the details of construction or design herein shown, other than asdescribed in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the claims below.

Claims

WHAT IS CLAIMED IS:1 . A method for selectively performing one or more recovery procedures for session initiation protocol (SIP) errors at a user equipment (UE) device (102), the method comprising: responsive to receiving a temporary SIP error message (405, 505) from an Internet Protocol Multimedia Subsystem (IMS) network (126), selectively performing one or more SIP error recovery procedures based on one or more SIP error recovery criteria.

2. The method of claim 1 , further comprising: responsive to transmitting an IMS signaling message (401 , 501) to the IMS network to initiate an IMS service, receiving the temporary SIP error message.

3. The method of any one of claims 1 or 2, wherein selectively performing the one or more SIP error recovery procedures comprises: responsive to determining that the temporary SIP error message specifies a duration of time to wait before performing a SIP error recovery procedure, incrementing a SIP error message count (320); and responsive to determining, based on the SIP error message count, that a SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied, selecting a corresponding SIP error recovery procedure from a plurality of SIP error recovery procedures (134).

4. The method of claim 3, wherein determining that the SIP error recovery criterion of the plurality SIP error recovery criteria is satisfied comprises comparing the SIP error message count to a threshold value.

5. The method of claim 4, wherein the threshold value is a maximum number of allowed silent retry procedures.

6. The method of claim 4, further comprising at least one of:determining that a first SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being less than the threshold value; determining that a second SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being equal to the threshold value; or determining that a third SIP error recovery criterion of the one or more SIP error recovery criteria is satisfied based on the SIP error message count being greater than the threshold value.

7. The method of any one of claims 1 or 6, wherein selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria comprises: responsive to selecting a first SIP error recovery procedure of a plurality of SIP error recovery procedures (134) based on the one or more SIP error recovery criteria, waiting for a duration of time specified by the temporary SIP error message; and responsive to the duration of time expiring, performing a retry process for an IMS signaling message associated with the temporary SIP error message.

8. The method of any one of claim 1 to 7, wherein selectively performing one or moreSIP error recovery procedures based on the one or more SIP error recovery criteria comprises: responsive to selecting a second SIP error recovery procedure of a plurality of SIP error recovery procedures (134) based on the one or more SIP error recovery criteria, clearing a current call session established with the IMS network; performing an IMS recovery procedure comprising deregistering from the IMS network and re-registering with the IMS network; and responsive to the IMS recovery procedure having completed within a first threshold amount of time, performing a final retry process for an IMS signaling message associated with the temporary SIP error message.

9. The method of claim 8, wherein re-registering with the IMS network comprises selecting a Proxy Call Session Control Function (P-CSCF) that is different from the P-CSCF associated with the call session that was cleared.

10. The method of any one of claim 8 or 9, wherein performing the final retry process comprises: responsive to the IMS recovery procedure having completed within a second threshold amount of time: waiting for a first duration of time based on a second duration of time specified by the temporary SIP error message; and responsive to the first duration of time expiring, performing the final retry process for the IMS signaling message; and responsive to the IMS recovery procedure having completed after a second threshold amount of time, immediately performing the final retry process for the IMS signaling message.11 . The method of any one of claims 8 to 10, wherein selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria comprises: responsive to the IMS recovery procedure having completed after the first threshold amount of time, refraining from performing a retry process for the IMS signaling message.

12. The method of any one of claims 1 to 11 , wherein selectively performing one or more SIP error recovery procedures based on the one or more SIP error recovery criteria comprises: responsive to selecting a third SIP error recovery procedure of a plurality of SIP error recovery procedures (134) based on the one or more SIP error recovery criteria, refraining from performing a retry process for an IMS signaling message associated with the temporary SIP error message.

13. The method of any one of claims 1 to 12, wherein the temporary SIP error message is a SIP INVITE error message.

14. A user equipment device (102), comprising: one or more radio frequency (RF) modems (306) configured to wirelessly communicate with at least one network (100); one or more processors (310) coupled to the one or more RF modems; and at least one memory (312) storing executable instructions, the executable instructions configured to manipulate at least one of the one or more processors or the one or more RF modems to perform the method of any of the preceding claims.

15. A computer-readable storage medium (312) embodying a set of executable instructions, the set of executable instructions to manipulate a user equipment device (102) to perform the method of any of claims 1 to 13.

Citation Information

Patent Citations

  • Error handling during IMS subscription for registration status

    US20180152908A1

  • Error handling during IMS registration

    US20180183839A1

  • Recovery from a potential proxy call session control function (p-CSCF) failure during call origination

    US20180248920A1

Cited By

  • Resolving unsynchronized internet protocol multimedia subsystem call states between a network and a user equipment

    WO2026173571A1