Radio access fallback for Internet Protocol Multimedia Subsystem registration

Abstract

This application relates to radio access fallback for Internet Protocol Multimedia Subsystem (IPS) registration. This application also relates to devices and components including apparatus, systems, and methods for IMS registration in wireless networks.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. nonprovisional application No. 17 / 877,862, filed July 29, 2022, and U.S. provisional patent application No. 63 / 240,857, filed September 3, 2021, the entire contents of which are incorporated herein by reference. Background Technology

[0003] The Internet Protocol Multimedia Subsystem (IMS) is a system that resides outside the access network and connects to a Long Term Evolution (LTE) or New Radio (NR) network via a Packet Data Network (PDN) or User Plane Function (UPF). IMS allows services such as text, multimedia messages, and voice calls to be delivered correctly over IP networks. Attached Figure Description

[0004] Figure 1 A network environment according to some implementation schemes is shown.

[0005] Figure 2 The call flow is shown according to some implementation schemes.

[0006] Figure 3 Another call flow is shown according to some implementation schemes.

[0007] Figure 4 The operational flow / algorithm structure according to some implementation schemes is shown.

[0008] Figure 5 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0009] Figure 6 User equipment according to some implementation schemes is shown. Detailed Implementation

[0010] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, and techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B); and the phrase “(A)B” refers to (B) or (A and B), i.e., A is optional.

[0011] The following is a glossary of terms that may be used in this disclosure.

[0012] As used herein, the term "circuit" refers to a portion of or includes said hardware component configured to provide the described functionality. Hardware components may include electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs). In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functionality (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0013] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0014] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, and network interface cards.

[0015] As used herein, the term "user equipment" or "UE" refers to equipment having radio communication capabilities that allow a user to access network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0016] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0017] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a particular device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application or workload units. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualized infrastructure to applications, devices, or systems. The terms "network resource" or "communication resource" can refer to resources accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0018] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0019] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0020] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0021] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, or virtualized network function.

[0022] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0023] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 communicatively coupled to one or more base stations of a radio access network (RAN) 108. The UE 104 and the base stations of RAN 108 may communicate via air interfaces compatible with 3GPP TS, such as those defining LTE, NR, or later-generation system standards. Base station 108 may be an evolved Node B (eNB) for providing one or more LTE cells or a next-generation Node B (gNB) for providing one or more 5G air interface (NR) cells.

[0024] Network environment 100 may also include a core network (CN) 112. For example, CN 112 may include an evolved packet core (EPC) network, a 5th generation core network (5GC), or a later generation core network. CN 112 may be coupled to RAN 108 via fiber optic or wireless backhaul. CN 112 may provide functionality to UE 104 via base station 108. These functions may include managing subscriber profile information, subscriber location, service authentication, or handover functions for voice and data sessions.

[0025] Network environment 100 may also include IMS 116 for providing Internet Protocol (IP) multimedia services to UE 104. IP multimedia services may include, for example, voice (e.g., LTE Voice (VoLTE) or NR Voice (VoNR)), video, messaging, data, and network-based services. IMS signaling has the highest priority 1 according to 3GPP TS 23.203v17.1.0 (2021-06-24) to ensure optimal session voice / media services for the end user.

[0026] The Session Initiation Protocol (SIP) is a signaling protocol primarily involved in "initiating" and "closing" media transmissions for voice services such as VoLTE / VoNR. UE 104 can perform IMS registration for Voice / Simple Messaging (SMS) services via the SIP registration mechanism. UE 104 can perform initial IMS registration upon power-on or during Airplane Mode (APM) handover. UE 104 can also perform IMS refresh registration periodically to maintain the IMS registration status.

[0027] Any delay in IMS registration on a specific radio access technology (RAT) can lead to undesirable UE performance and a poor user experience. For example, without LTE / NR voice service, the signal bar on the user interface may turn gray, regardless of the conditions of the radio frequency (RF) channel.

[0028] In the current implementation, if an IMS refresh registration fails due to a Transmission Control Protocol (TCP) error or timer F expiration, the UE can retry the registration on the NR RAT. Even after a previous unsuccessful attempt on the NR RAT, the UE can retry IMS registration in the NR. This can lead to consecutive IMS registration failures, which may persist for extended periods, such as exceeding 300 seconds. During this time, the UE may miss multiple Mobile Termination (MT) calls and display a grayed-out bar on the user interface, resulting in a poor user experience. If observed continuously, this can also lead to VoNR / Evolved Packet Service Fallback (EPSFB) voice failures.

[0029] 3GPP TS 24.501v17.3.1 (2021-07-02) defines specific implementation options, in which N1 mode should be disabled if IMS voice is unavailable, and the UE should start a timer to re-enable N1 mode capability.

[0030] Currently, for the initial IMS registration after NR registration, the baseband can include a `max_ims_reg_timer` (default 35 seconds) to monitor IMS registration. If IMS registration fails within this timer, NR will be blocked for 12 minutes. However, in the case of IMS refresh registration, the application processor does not have such a timer.

[0031] The following device operations are considered based on the current network design.

[0032] This can trigger IMS re-registration, which can be IMS registration attempt #0 on Agent-Call Session Control Function (P-CSCF) #1. Timer F (non-INVITE transaction timeout timer) can be set to 128 seconds, with the registration throttling timer set to 30 seconds.

[0033] After 75 seconds, POSIX: broken pipe may cause a TCP socket write error. Timer E (non-INVITE request retransmission interval, UDP only) can be set to two seconds.

[0034] Two seconds later, timer E may expire, and IMS registration retry attempt #1 may occur on P-CSCF #1. Timer E (non-INVITE request retransmission interval, UDP only) can be set to four seconds.

[0035] After an additional 51 seconds, timer F may expire, causing the SIP request to time out. The registered throttling timer can be set to 30 seconds.

[0036] After another 30 seconds, the registered throttling timer may expire, and IMS registered retry attempt #2 may occur on P-CSCF #1. Timer F (non-INVITE transaction timeout timer) can be set to 128 seconds, and the registered throttling timer can be set to 30 seconds.

[0037] A TCP socket write error may occur after an additional 75 seconds, caused by POSIX: broken pipe. Timer E (non-INVITE request retransmission interval, UDP only) can be set to two seconds.

[0038] Two seconds later, timer E may expire, and IMS registration retry attempt #3 may occur on P-CSCF #1. Timer E (non-INVITE request retransmission interval, UDP only) can be set to four seconds.

[0039] After an additional 51 seconds, timer F may expire, causing the SIP request to time out. The registered throttling timer can be set to 30 seconds.

[0040] After another 30 seconds, the registered throttling timer may expire, and IMS registered retry attempt #4 may occur on P-CSCF #2. Timer F (non-INVITE transaction timeout timer) can be set to 128 seconds, and the registered throttling timer can be set to 30 seconds.

[0041] After an additional 26 seconds, the user can dump the call logs, and the UE can recover after the APM handover.

[0042] This sequence illustrates a device stuck in an unwanted state, where the signal bar remains gray for five minutes. Various implementations describe mechanisms to prevent this from happening.

[0043] Some implementations describe initiating a forced fallback to LTE after a period of time (e.g., 30 seconds) during the attempt to refresh IMS registration on NR, blocking NR, and retrying IMS registration on LTE. This helps UE 104 avoid getting stuck in a loop of failed IMS registration on NR and improves the overall performance of UE 104 in cases where IMS registration failure is specific to the NR cell. By performing IMS registration on LTE, the user will be able to make / receive voice calls.

[0044] In some implementations, the NR can be unblocked based on the LTE IMS registration status (LTE-IMS-Registration-Status) and the pre-occupied LTE cell. For example, for the first attempt to unblock the NR (and attempt to register IMS on the NR), UE 104 can unblock the NR once the IMS registration on LTE is successful. For the next attempt to unblock the NR, UE 104 may not unblock the NR until UE 104 moves to a new LTE cell, or in some implementations, wait for the blocking timer to expire. To avoid blocking / unblocking loops, a maximum threshold for retry attempts can be set. In some implementations, this threshold can be set to three attempts; however, in other implementations, this can be different.

[0045] Figure 2 and Figure 3 Call flows 200 and 300 according to some implementation schemes are illustrated respectively. Call flows 200 / 300 may be implemented by the circuitry (e.g., processing circuitry) of UE 104.

[0046] At 204, call flow 200 may include attempting IMS registration on NR.

[0047] If it is determined at 208 that the IMS registration on the NR was successful within a predetermined time period (e.g., 30 seconds), then call flow 200 can end at 212. At this point, existing specific implementations can be followed.

[0048] If it is determined at 208 that the IMS registration on the NR is unsuccessful for the scheduled period of time, call flow 200 can proceed to initiate a local NR RRC release at 216.

[0049] After initiating a local NR RRC release at 216, call flow 200 may include determining whether the quality of the LTE cell is greater than a threshold. If the quality, based on Reference Received Power (RSRP), Reference Received Quality (RSRQ), or Signal-to-Noise Ratio (SNR), is less than the threshold, call flow 200 may terminate at 212. If the quality meets the threshold, call flow 200 may proceed to fall back to LTE at 224.

[0050] Call flow 200 may also include determining at 228 whether IMS registration on LTE was successful. If IMS registration on LTE is unsuccessful, call flow 200 may terminate at 212. If IMS registration on LTE is successful, call flow 200 may proceed to call flow 300.

[0051] Call flow 300 may include blocking the NR due to IMS registration failure on the NR. Blocking the NR prevents the UE from retrying IMS registration on the NR.

[0052] Call flow 300 may also include starting or restarting a blocking timer at 308. The blocking timer can be (re)started with a predetermined value (such as, for example, 12 minutes).

[0053] Call flow 300 may include determining at 312 whether IMS registration on LTE was successful. In the first instance of call flow 300 (from call flow 200), the UE may have already registered on LTE from 224 / 228. However, in subsequent instances, due to the loss of IMS registration on LTE at box 324, UE 104 may need to retry IMS registration on LTE, as described below.

[0054] If IMS registration on LTE fails at 312, call flow 300 can proceed to 316 and will wait there until the blocking timer expires.

[0055] If IMS registration on LTE is successful at 312, call flow 300 can proceed to 320 to determine if the retry counter is equal to zero.

[0056] If at 320 the retry counter equals zero (meaning IMS registration on NR has not yet been attempted in the context of call flow 300) or at 316 the blocking timer expires, call flow 300 proceeds to 324 to unblock NR and retry IMS registration on NR. To retry IMS registration on NR, UE 104 may perform an LTE-to-NR reselection, and therefore, lose the IMS registration on LTE.

[0057] Call flow 300 may include determining at 326 whether IMS registration on the NR was successful.

[0058] If registration on the NR is confirmed to be successful at 326, the call flow can proceed to reset the retry counter to zero at 328 and end at 332.

[0059] If registration on NR fails at point 326, call flow 300 can proceed to point 336 to increment the retry counter by 1, and then proceed to point 304 to block NR due to IMS registration failure. The UE can also attempt to perform IMS registration on LTE again.

[0060] If it is determined at 320 that the retry counter is not equal to zero (meaning that IMS registration on NR has been attempted at least once in call flow 300), then call flow 300 proceeds to 340 to determine whether the retry counter is less than the maximum threshold (e.g., 3).

[0061] If it is determined at 340 that the retry counter is not less than the maximum threshold, then call flow 300 can proceed to 316 and will wait there until the blocking timer expires.

[0062] If it is determined at 340 that the retry counter is less than the maximum threshold, call flow 300 can proceed to 344 to detect LTE cell changes.

[0063] If no LTE cell change is detected at 344, call flow 300 can proceed to 316 and will wait there until the blocking timer expires.

[0064] If an LTE cell change is detected at 344, call flow 300 can proceed to 320 to unblock the NR and retry IMS registration on the NR.

[0065] Figure 4 An operational flow / algorithm structure 400 according to some implementation schemes is shown. The operational flow / algorithm structure 400 may be implemented by a UE (such as, for example, UE 104, UE 600) or its components (such as processor 604).

[0066] The operation process / algorithm structure 400 may include determining at 404 that NR access has failed to register with IMS on NR and has been blocked.

[0067] The operation flow / algorithm structure 400 may also include detecting one or more conditions at 408. In various implementations, conditions may relate to whether the UE has successfully performed IMS registration on LTE, conditions of the blocking timer, LTE cell change conditions, or the value of the retry counter. Generally, these conditions may be similar to those described above. Figure 3 The conditions described in boxes 312, 316, 320, 340, and 344.

[0068] When one or more conditions are detected at 408, the operation flow / algorithm structure 400 can proceed to 412 to unblock NR access and retry IMS registration on NR.

[0069] While the embodiments described in this disclosure describe the management of IMS registration on NR and LTE, other embodiments may also be applied to other RATs. For example, in some embodiments, if a UE determines that access to a first RAT is blocked due to a failure of IMS registration on the first RAT, it may attempt to detect conditions (including some conditions involving conditional access to a fallback second RAT), and if the conditions are detected, it may unblock access to the first RAT and retry IMS registration on the first RAT.

[0070] Figure 5 An operational flow / algorithm structure 500 according to some implementation schemes is shown. The operational flow / algorithm structure 500 may be implemented by a UE (such as, for example, UE 104, UE 600) or its components (such as processor 604).

[0071] The operation flow / algorithm structure 500 may include determining at 504 that the IMS registration on the NR has failed for a predetermined period of time. In some implementations, the predetermined period of time is 30 seconds.

[0072] The operation flow / algorithm structure 500 may also include initiating NR release at 508. This can be based on the determination at box 504.

[0073] The operation procedure / algorithm structure 500 may also include attempting to perform IMS registration on LTE at 512. If IMS registration on LTE is successful, NR access can be blocked until one or more conditions are met. These conditions may involve the value of a blocking timer, LTE cell change conditions, or a retry counter. Generally, these conditions may be similar to those described above. Figure 3 The conditions described in boxes 312, 316, 320, 340, and 344.

[0074] Figure 6 A UE 600 according to some implementation schemes is shown. UE 600 may be similar to Figure 1 The UE 104 is essentially interchangeable with it.

[0075] UE 600 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, stock sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0076] UE 600 may include a processor 604, RF interface circuitry 608, memory / storage device 612, user interface 616, sensor 620, drive circuitry 622, power management integrated circuit (PMIC) 624, antenna structure 626, and battery 628. Components of UE 600 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 6 The block diagram is intended to show a high-level view of some of the components of the UE 600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0077] The components of UE 600 can be coupled to various other components via one or more interconnects 632, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0078] Processor 604 may include processor circuitry such as baseband processor circuitry (BB) 604A, central processing unit circuitry (CPU) 604B, and graphics processing unit circuitry (GPU) 604C. Processor 604 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures) from memory / storage device 612 to cause UE 600 to perform operations as described herein (such as those described, for example, with respect to call flows 200 and 300).

[0079] In some implementations, the baseband processor circuitry 604A can access the communication protocol stack 636 in the memory / storage device 612 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuitry 604A can access the communication protocol stack 636 to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and NAS layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuitry 608.

[0080] The baseband processor circuit 604A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0081] Memory / storage device 612 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 636) that can be executed by one or more processors in processor 604 to cause UE 600 to perform the various operations described herein. Memory / storage device 612 includes any type of volatile or non-volatile memory that can be distributed throughout UE 600. In some embodiments, some memory / storage devices 612 may be located on processor 604 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 612 may be located external to processor 604 but accessible via a memory interface. Memory / storage device 612 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0082] RF interface circuitry 608 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows UE 600 to communicate with other devices via a radio access network. RF interface circuitry 608 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0083] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 626 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 604.

[0084] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 626.

[0085] In various implementations, the RF interface circuit 608 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0086] Antenna 626 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 626 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 626 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. Antenna 626 may have one or more panels designed for a specific frequency band (including bands in FR1 or FR2).

[0087] User interface circuitry 616 includes various input / output (I / O) devices designed to enable users to interact with UE 600. User interface 616 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 600.

[0088] Sensor 620 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0089] The driving circuitry 622 may include software and hardware elements for operating specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 600. The driving circuitry 622 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 600. For example, the driving circuitry 622 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of sensor circuitry 620 and controlling and allowing access to sensor circuitry 620; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0090] The PMIC 624 manages the power supplied to various components of the UE 600. Specifically, relative to the processor 604, the PMIC 624 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0091] In some implementations, the PMIC 624 may control or otherwise be part of various power-saving mechanisms of the UE 600, including the DRX described herein.

[0092] Battery 628 can power UE 600, but in some examples, UE 600 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 628 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 628 may be a typical lead-acid automotive battery.

[0093] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0094] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, or network element described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0095] Example

[0096] Further exemplary implementations are provided in the following sections.

[0097] Example 1 includes a method comprising: determining that Internet Protocol Multimedia Subsystem (IMS) registration on a New Radio (NR) fails for a predetermined period of time; initiating an NR release based on the determination; and attempting to perform IMS registration on Long Term Evolution (LTE) based on the determination.

[0098] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the predetermined time period is 30 seconds.

[0099] Example 3 includes the method according to Example 1 or some other example herein, further comprising: successfully performing IMS registration on LTE; and blocking NR access based on the successful execution of the IMS registration on LTE.

[0100] Example 4 includes the method described in Example 3 or another embodiment of this document, and further includes: determining that a retry counter is equal to zero, the retry counter being used to track the number of unsuccessful retries for IMS registration on the NR; and based on determining that the retry counter is equal to zero, releasing the blocking of NR access and retrying IMS registration on the NR.

[0101] Example 5 includes the method described in Example 3 or another embodiment of this document, further comprising: determining that a retry counter is not equal to zero, the retry counter being used to track the number of unsuccessful retries for IMS registration on the NR; determining that the retry counter is less than a predetermined threshold for retry attempts based on the determination that the retry counter is not equal to zero; detecting an LTE cell change based on the determination that the retry counter is less than the predetermined threshold; and unblocking NR access and retrying IMS registration on the NR based on the detection of the LTE cell change.

[0102] Example 6 includes the method described in Example 3 or another embodiment of this document, further comprising: starting or restarting a blocking timer after the NR access is blocked; determining that a retry counter is not equal to zero, the retry counter being used to track the number of unsuccessful retries for IMS registration on the NR; determining that the retry counter is not less than a predetermined threshold for retry attempts based on the determination that the retry counter is not equal to zero; detecting the expiration of the blocking timer based on the determination that the retry counter is not less than the predetermined threshold; and releasing the blocking of NR access and retrying IMS registration on the NR based on the detection of the expiration of the blocking timer.

[0103] Example 7 includes the method described in Example 3 or another embodiment of this document, further comprising: starting or restarting a blocking timer after the NR access is blocked; determining that a retry counter is not equal to zero, the retry counter being used to track the number of unsuccessful retries for IMS registration on the NR; determining that the retry counter is less than a predetermined threshold for retry attempts based on the determination that the retry counter is not equal to zero; determining that an LTE cell change has not been detected based on the determination that the retry counter is less than the predetermined threshold; detecting the expiration of the blocking timer based on the determination that the LTE cell change has not been detected; and releasing the blocking of NR access and retrying IMS registration on the NR based on the detection of the expiration of the blocking timer.

[0104] Example 8 includes the method according to Example 6 or Example 7 or some other embodiment of the present invention, and further includes setting the value of the blocking timer to 12 minutes.

[0105] Example 9 includes the method according to any one of Examples 5 to 7 or some other embodiment herein, wherein the predetermined threshold is 3.

[0106] Example 10 includes the method according to any one of Examples 4 to 7 or some other example of this document, and further includes: determining that the retry of IMS registration on the NR is unsuccessful; and based on the determination that the retry of IMS registration on the NR is unsuccessful, incrementing the retry counter and blocking NR access.

[0107] Example 11 includes the method according to Example 10 or some other embodiment of this document, wherein retrying IMS registration on NR includes performing LTE to NR reselection, and the method further includes: based on the determination that the retrying IMS registration on NR is unsuccessful, attempting IMS registration on LTE.

[0108] Example 12 may include a method for operating a UE, the method comprising: determining that NR access has been blocked due to IMS registration failure on the NR; and, based on the determination that NR access has been blocked due to IMS registration failure on the NR, unblocking the NR access and retrying IMS registration on the NR.

[0109] Example 13 may include the method described in Example 12 or some other example herein, and further includes: starting a blocking timer based on the determination that NR access is blocked due to IMS registration failure on the NR; detecting the expiration of the blocking timer; and further, based on detecting the expiration of the blocking timer, unblocking NR access and retrying IMS registration on the NR.

[0110] Example 14 may include the method described in Example 12 or some other embodiment herein, and further includes: successfully performing IMS registration on LTE.

[0111] Example 15 may include the method described in Example 14 or some other embodiment herein, and further includes: determining that a retry counter is equal to zero based on the successful execution of IMS registration on the LTE, the retry counter being used to track the number of unsuccessful retries of IMS registration on the NR; and further, based on determining that the retry counter is equal to zero, unblocking NR access and retrying IMS registration on the NR.

[0112] Example 16 may include the method described in Example 14 or some other embodiment of this document, further comprising: determining, based on the successful execution of IMS registration on the LTE, that a retry counter is not equal to zero and is less than a predetermined threshold, the retry counter being used to track the number of unsuccessful retries of IMS registration on the NR; determining that the LTE cell has changed; and further, based on the determination that the retry counter is not equal to zero and is less than the predetermined threshold and the determination that the LTE cell has changed, unblocking NR access and retrying IMS registration on the NR.

[0113] Example 17 may include a method for operating a UE, the method comprising: determining that access to the first RAT is blocked due to Internet Protocol Multimedia Subsystem (IMS) registration failure on the first RAT; and, based on the determination that access to the first RAT is blocked due to IMS registration failure on the first RAT, unblocking access to the first RAT and retrying IMS registration on the first RAT.

[0114] Example 18 may include the method described in Example 17 or some other embodiment of this document, and further includes: based on the determination that access to the first RAT is blocked due to IMS registration failure on the first RAT, starting a blocking timer; detecting the expiration of the blocking timer; and further based on detecting the expiration of the blocking timer, unblocking access to the first RAT and retrying IMS registration on the first RAT.

[0115] Example 19 may include the method described in Example 17 or some other embodiment herein, and further includes: successfully performing IMS registration on a second RAT.

[0116] Example 20 may include the method described in Example 19 or some other embodiment herein, further comprising: determining that a retry counter is equal to zero based on the successful execution of the IMS registration on the second RAT, the retry counter being used to track the number of unsuccessful retries of the IMS registration on the first RAT; and further, based on determining that the retry counter is equal to zero, unblocking access to the first RAT and retrying the IMS registration on the first RAT.

[0117] Example 21 may include the method described in Example 19 or some other embodiment of this document, further comprising: determining, based on the successful execution of the IMS registration on the second RAT, that a retry counter is not equal to zero and is less than a predetermined threshold, the retry counter being used to track the number of unsuccessful retryes of the IMS registration on the first RAT; determining that the cell of the second RAT has changed; and further, based on the determination that the retry counter is not equal to zero and is less than the predetermined threshold and the determination that the cell of the second RAT has changed, unblocking access to the first RAT and retrying the IMS registration on the first RAT.

[0118] Example 22 may include an apparatus comprising one or more elements for performing the method or any other method or process described herein, as described in or associated with any of Examples 1 to 21.

[0119] Example 23 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described or associated with any of Examples 1 to 21.

[0120] Example 24 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1 to 21 or any other method or process described herein.

[0121] Example 25 may include any of the methods, techniques, or processes described or associated with any of Examples 1 to 21, or a portion or component thereof.

[0122] Example 26 may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, according to or related to any of Examples 1 to 21.

[0123] Example 27 may include a signal, or a portion thereof, described or associated with any of Examples 1 to 21.

[0124] Example 28 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or otherwise in this disclosure, according to any of Examples 1 to 21.

[0125] Example 29 may include a data-encoded signal, or a portion or component thereof, as described or associated with any of Examples 1 to 21, or otherwise described in this disclosure.

[0126] Example 30 may include signals encoded in datagram, IE, packet, frame, segment, PDU or message format according to any one of Examples 1 to 21, or other means thereof, or as otherwise described in this disclosure.

[0127] Example 31 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 21.

[0128] Example 32 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 21.

[0129] Example 33 may include signals in a wireless network as shown and described herein.

[0130] Example 34 may include methods for communicating in a wireless network as shown and described herein.

[0131] Example 35 may include a system for providing wireless communication as shown and described herein.

[0132] Example 36 may include a device for providing wireless communication as shown and described herein.

[0133] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0134] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause an electronic device to perform the following operations: The New Radio (NR) access was blocked due to failure to register with the Internet Protocol Multimedia Subsystem (IMS) over NR. Based on the determination that NR access was blocked due to failure of IMS registration on NR, one or more conditions are detected, the one or more conditions involving: determining whether IMS registration on LTE was successful; the value of the retry counter; Determining whether the LTE cell has been changed; or determining whether the blocking timer has expired; as well as Based on the determination that NR access was blocked due to failure of IMS registration on NR and the detection of one or more of the conditions, the blocking of NR access is lifted and IMS registration on NR is retried.

2. The one or more computer-readable media of claim 1, wherein the instructions, when executed, further cause the electronic device to: Based on the determination that NR access was blocked due to IMS registration failure on NR, a blocking timer is started; and The expiration of the blocking timer is detected as one of the conditions.

3. The one or more computer-readable media of claim 1, wherein the instructions, when executed, further cause the electronic device to: IMS registration on LTE was successfully performed.

4. The one or more computer-readable media according to claim 3, wherein, In order to detect one or more of the conditions, the electronic device is used to: Based on the successful execution of IMS registration on LTE, the retry counter is determined to be equal to zero. The retry counter is used to track the number of times IMS registration on NR has failed to retry.

5. The one or more computer-readable media according to claim 3, wherein, In order to detect one or more of the conditions, the electronic device is used to: Based on the successful execution of IMS registration on LTE, it is determined that the retry counter is not equal to zero and is less than a predetermined threshold. The retry counter is used to track the number of times IMS registration on NR fails to retry. as well as The LTE cell has been confirmed to have changed.

6. An apparatus comprising: An interface that enables communication using the first radio access technology (RAT); as well as The processing circuit coupled to the interface is used for: It was determined that access to the first RAT was blocked due to a failed registration with the Internet Protocol Multimedia Subsystem (IMS) on the first RAT. Based on the determination that access to the first RAT was blocked due to IMS registration failure on the first RAT, one or more conditions are detected, the one or more conditions involving: determining whether IMS registration on the second RAT was successful; the value of the retry counter; Determining whether the cell of the second RAT has been changed; or determining whether the blocking timer has expired; as well as Based on the determination that access to the first RAT was blocked due to IMS registration failure on the first RAT and the detection of one or more of the conditions, the access to the first RAT is unblocked and IMS registration on the first RAT is retried.

7. The apparatus of claim 6, wherein the processing circuit is further configured to: Based on the determination that access to the first RAT was blocked due to IMS registration failure on the first RAT, a blocking timer is started; and The expiration of the blocking timer is detected as one of the conditions.

8. The apparatus of claim 6, wherein the processing circuit is further configured to: IMS registration on the second RAT was successfully performed.

9. The apparatus according to claim 8, wherein, In order to detect one or more of the conditions, the processing circuit is used to: Based on the successful execution of IMS registration on the second RAT, the retry counter is determined to be equal to zero. The retry counter is used to track the number of times the IMS registration on the first RAT failed to retry.

10. The apparatus according to claim 8, wherein, In order to detect one or more of the conditions, the processing circuit is used to: Based on the successful execution of IMS registration on the second RAT, it is determined that the retry counter is not equal to zero and is less than a predetermined threshold. The retry counter is used to track the number of times the IMS registration on the first RAT failed to retry. as well as It has been determined that the cell of the second RAT has been changed.

11. A method for Internet Protocol Multimedia Subsystem (IMS) registration in a wireless network, the method comprising: Determine the duration of unsuccessful Internet Protocol Multimedia Subsystem (IMS) registration on the New Radio (NR) network. Based on the aforementioned determination, NR release is initiated; as well as Based on the predetermined period of time during which IMS registration on NR is determined to be unsuccessful, IMS registration on LTE is successfully performed. Based on the successful execution of IMS registration on LTE, detect one or more conditions related to the value of the blocking timer, LTE cell change condition, or retry counter; as well as Block NR access until one or more of the conditions are detected.

12. The method of claim 11, wherein the predetermined time period is 30 seconds.

13. The method of claim 11, further comprising: NR access is blocked based on successful execution of IMS registration on LTE.

14. The method of claim 13, wherein detecting the one or more conditions comprises: The retry counter is set to zero. This retry counter is used to track the number of unsuccessful retries registered on the NR via IMS.

15. The method of claim 14, further comprising: It was determined that retrying IMS registration on the NR was unsuccessful; as well as If it is determined that retrying IMS registration on the NR is unsuccessful, the retry counter is incremented and NR access is blocked.

16. The method of claim 15, wherein retrying IMS registration on NR includes performing LTE-to-NR reselection, and the method further includes: Since retrying IMS registration on NR is unsuccessful, we will attempt IMS registration on LTE.

17. The method of claim 13, wherein detecting the one or more conditions comprises: The retry counter is determined to be non-zero and less than a predetermined threshold for retry attempts. The retry counter is used to track the number of unsuccessful retries registered on the NR via IMS. as well as Based on the determination that the retry counter is less than the predetermined threshold, an LTE cell change is detected.

18. The method of claim 17, wherein the predetermined threshold is 3.

19. The method of claim 13, wherein detecting the one or more conditions comprises: Start or restart the blocking timer after blocking NR access; The retry counter is determined to be neither equal to zero nor less than a predetermined threshold for retry attempts, the retry counter being used to track the number of unsuccessful retries registered on the NR via IMS; as well as Based on the determination that the retry counter is not less than the predetermined threshold, the expiration of the blocking timer is detected.

20. The method of claim 19, further comprising: Set the value of the blocking timer to 12 minutes.

Images