CN112020094A - Cellular enhancement of application mobility - Google Patents

Abstract

The application relates to cellular enhancements for application mobility. Apparatus, systems, and methods for a wireless device to perform detection and mitigation of data stalls are disclosed. The mitigation may occur during and/or upon initiation of the data connection. The wireless device may establish a data connection with a network through a Wi-Fi interface or a cellular interface and monitor the data connection for data stall conditions/prompts. The wireless device may perform remedial actions in response to detecting a data stall condition/prompt, including initiating a service restoration of the cellular interface, initiating a Radio Access Technology (RAT) upgrade procedure, and/or initiating a handover procedure to a neighboring cell.

Description

Cellular enhancement of application mobility

Priority data

This patent Application claims the benefit of priority from U.S. provisional patent Application serial No. 62/855,620 entitled Cellular Enhancements for Application Mobility filed on 31/5/2019, which is hereby incorporated by reference in its entirety as if fully and fully set forth herein.

Technical Field

The present application relates to wireless devices, and more particularly, to apparatus, systems, and methods for wireless devices to perform various cellular communication techniques.

Background

The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become more sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that take advantage of these functions. In addition, many different wireless communication technologies and wireless communication standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE-advanced (LTE-A), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11(WLAN or Wi-Fi), BLUETOOTH^TMAnd the like.

The introduction of an ever increasing number of features and functions in wireless communication devices has also created a continuing need for improved wireless communications and improved wireless communication devices. In order to increase coverage and better serve the increasing demand and range of intended uses of wireless communications, in addition to the above-described communication standards, there are wireless communication technologies being developed, including fifth generation (5G) New Radio (NR) communications. Accordingly, there is a need for improvements in the areas that support such development and design.

Disclosure of Invention

Embodiments relate to apparatus, systems, and methods for a wireless device to detect and mitigate data stalls during a data connection and/or before establishing a data connection with a network.

The techniques described herein may be implemented in and/or used with a plurality of different types of devices, including, but not limited to, cellular phones, tablets, wearable computing devices, portable media players, and any of a variety of other computing devices.

In some embodiments, a wireless device may perform a method for detecting and/or mitigating data stalls for a data connection. In some embodiments, the method may include a wireless device establishing a data connection with a network. The data connection may be established through a Wi-Fi interface (radio) and/or a cellular interface (radio) of the wireless device. The wireless device may monitor the data connection for a data stall condition and/or a data stall prompt, including activating an upper layer application while a user interface of the wireless device is in a locked state, one or more upper layer applications (e.g., initiated/launched by a user) not receiving one or more network responses to HTTP-GET queries for a specified period of time (e.g., when the application is launched in the foreground), buffer size reduction for media flow, DNS failure, launching an application with low latency quality of service requirements on a lower performance cellular connection, Wi-Fi link loss and/or Wi-Fi backhaul interruption (e.g., connected to a Wi-Fi access point but not assigned a valid IP address). The wireless device may perform a remedial action in response to detecting a data stall condition and/or a data stall prompt, for example, during and/or upon initiating a data connection. The remedial action may include the wireless device initiating a service restoration of a cellular interface of the wireless device, initiating a Radio Access Technology (RAT) upgrade procedure, and/or initiating a handover and/or reselection procedure to a neighboring cell. In some embodiments, the remedial action may be based at least in part on the cause of the data stall condition and/or the data stall prompt, including a backhaul server problem, the cellular interface of the wireless device being connected to a cell operating according to a lower performance Radio Access Technology (RAT), congestion on a current cell, congestion on a cellular core network, a Random Access Channel (RACH) procedure failure, a Radio Link Failure (RLF), and/or launching an application with a low latency quality of service requirement on a lower performance cellular connection.

In some embodiments, a wireless device may perform a method for detecting and/or mitigating data stalls for a data connection when using a higher performance Radio Access Technology (RAT). In some embodiments, the method may include a wireless device camping on a cell operating according to a higher performance RAT. In some embodiments, the higher-performance RAT may be one of Long Term Evolution (LTE) or fifth generation new radio (5G NR), and the cell may be associated with a first Physical Cell Identifier (PCI). The wireless device may initiate one or more data sessions with the network and monitor the one or more data sessions for data stall cues and/or data stall conditions. In response to determining that the neighboring cell satisfies the at least one handover condition and detecting the data stall prompt and/or the data stall condition, the wireless device may initiate a handover and/or reselection procedure to the neighboring cell.

This summary is intended to provide a brief overview of some of the subject matter described in this document. Thus, it should be understood that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, the accompanying drawings, and the claims.

Drawings

A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

fig. 1A illustrates an example wireless communication system according to some embodiments.

Fig. 1B illustrates an example of a Base Station (BS) and an access point in communication with a User Equipment (UE) device, in accordance with some embodiments.

Fig. 2 illustrates an exemplary simplified block diagram of a WLAN Access Point (AP) according to some embodiments.

Fig. 3 illustrates an example block diagram of a UE in accordance with some embodiments.

Fig. 4 illustrates an example block diagram of a BS in accordance with some embodiments.

Fig. 5 illustrates an example block diagram of a cellular communication circuit in accordance with some embodiments.

Fig. 6A shows an example of a connection between an EPC network, an LTE base station (eNB), and a 5G NR base station (gNB).

Fig. 6B shows an example of a protocol stack for an eNB and a gNB.

Fig. 7A illustrates an example of a 5G network architecture that incorporates 3GPP (e.g., cellular) and non-3 GPP (e.g., non-cellular) access at the 5G CN, in accordance with some embodiments.

Fig. 7B illustrates an example of a 5G network architecture that combines dual 3GPP (e.g., LTE and 5G NR) access and non-3 GPP access at a 5G CN in accordance with some embodiments.

Fig. 8 illustrates an example of a baseband processor architecture for a UE, in accordance with some embodiments.

FIG. 9 illustrates a block diagram of an example of an architecture for data quiesce processing, according to some embodiments.

FIG. 10 illustrates a block diagram of an example of an architecture for data stall preemption, according to some embodiments.

Figure 11 shows various performance values for a video call initiated over an LTE and non-LTE connection.

Fig. 12 illustrates a block diagram of an example of a method for a wireless device to detect and mitigate data stalls during a data connection and/or before establishing a data connection with a network, in accordance with some embodiments.

Fig. 13 illustrates a block diagram of an example of a method for avoiding data stalls when camping on an LTE cell, according to some embodiments.

Fig. 14 illustrates a block diagram of an example of a method for a wireless device to detect and/or mitigate data stalls for a data connection when using a higher performance Radio Access Technology (RAT), in accordance with some embodiments.

While features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the disclosure to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.

Detailed Description

Term(s) for

The following is a glossary of terms used in this disclosure:

memory medium-any of various types of non-transitory memory devices or storage devices. The term "storage medium" is intended to include mounting media, such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., a hard disk drive or optical storage; registers or other similar types of memory elements, and the like. The memory medium may also include other types of non-transitory memory or combinations thereof. Further, the memory medium may be located in a first computer system executing the program, or may be located in a different second computer system connected to the first computer system through a network such as the internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside at different locations in different computer systems, e.g., connected by a network. The memory medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.

Carrier medium-a memory medium as described above, and a physical transmission medium such as a bus, a network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

Programmable hardware element — includes various hardware devices that include a plurality of programmable functional blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can range from fine grained (combinatorial logic units or look-up tables) to coarse grained (arithmetic logic units or processor cores). The programmable hardware elements may also be referred to as "configurable logic components".

Computer system — any of various types of computing systems or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, internet appliance, Personal Digital Assistant (PDA), television system, grid computing system, or other device or combination of devices. In general, the term "computer system" may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

User Equipment (UE) (or "UE device") -any of various types of computer systems or devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smart phones (e.g., iphones)^TMBased on Android^TMTelephone), portable gaming devices (e.g., Nintendo DS)^TM、PlayStation Portable^TM、Gameboy Advance^TM、iPhone^TM) A laptop computer, a wearable device (e.g., a smart watch, smart glasses), a personal digital assistant, a portable internet device, a music player, a data storage device, or other handheld device, etc. In general, the term "UE" or "UE device" may be broadly defined to encompass any electronic device, computing device, and/or telecommunications device (or combination of devices) that is portable by a user and capable of wireless communication.

Wireless device-any of various types of computer systems or devices that perform wireless communication. The wireless device may be portable (or mobile) or may be stationary or fixed in some location. A UE is one example of a wireless device.

Communication device-any of various types of computer systems or devices that perform communication, which may be wired or wireless. The communication device may be portable (or mobile) or may be stationary or fixed in some location. A wireless device is one example of a communication device. A UE is another example of a communication device.

Base station-the term "base station" has its full scope in its ordinary sense and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

Processing element-refers to various elements or combinations of elements capable of performing functions in a device, such as a user equipment or a cellular network device. The processing elements may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (application specific integrated circuit), programmable hardware elements such as Field Programmable Gate Arrays (FPGAs), and any of the above in various combinations.

Channel-the medium used to convey information from a sender (transmitter) to a receiver. It should be noted that the term "channel" as used herein may be considered to be used in a manner that is consistent with the standard for the type of device to which the term is used, as the characteristics of the term "channel" may vary from one wireless protocol to another. In some standards, the channel width may be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE may support a scalable channel bandwidth of 1.4MHz to 20 MHz. In contrast, a WLAN channel may be 22MHz wide, while a bluetooth channel may be 1MHz wide. Other protocols and standards may include different definitions for channels. Further, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different purposes such as data, control information, etc.

Band-the term "band" has its ordinary meaning in its full scope and includes at least a segment of spectrum (e.g., the radio frequency spectrum) in which channels are used or set aside for the same purpose.

HTTP transaction-the term "HTTP transaction" may refer to an exchange between an HTTP client (requester) and an HTTP server (responder). For example, the exchange may include the HTTP client transmitting (or sending) an HTTP request, such as an HTTP-GET query, to the HTTP server, and receiving (from the HTTP server) an HTTP response, e.g., a response to the HTTP-GET query. Failure of an HTTP transaction may include the HTTP client not receiving a response from the HTTP server, receiving an incomplete response from the HTTP server, and/or not receiving a response for a specified time period (e.g., a timeout period). HTTP transactions may occur over a Transmission Control Protocol (TCP) connection, and may also occur over an encrypted byte stream (e.g., a Transport Layer Security (TLS) protocol connection) on top of the TCP connection. Additionally, HTTP transactions may occur over transport connections that do not use TCP, such as a fast User Data Protocol (UDP) internet connection (QUIC), which provides a reliable stream of encrypted bytes over UDP datagrams.

Automatically-refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or device (e.g., a circuit, programmable hardware element, ASIC, etc.) without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being performed or specified manually by a user, where the user provides input to perform the operation directly. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting a check box, radio selection, etc.) is manually filling out the form, even though the computer system must update the form in response to user action. The form may be automatically filled in by a computer system, wherein the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user entering answers specifying the fields. As indicated above, the user may invoke automatic filling of the form, but not participate in the actual filling of the form (e.g., the user does not manually specify answers to the fields but they are done automatically). This specification provides various examples of operations that are automatically performed in response to actions that have been taken by a user.

About-refers to a value that is close to correct or exact. For example, approximately may refer to a value within 1% to 10% of the exact (or desired) value. It should be noted, however, that the actual threshold (or tolerance) may depend on the application. For example, in some embodiments, "about" may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, etc., as desired or required by a particular application.

Concurrent-refers to parallel execution or performance, wherein tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency may be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements; or "weak parallelism" in which tasks are performed in an interleaved fashion (e.g., by performing time-multiplexing of threads).

Configured-various components may be described as "configured to" perform one or more tasks. In such an environment, "configured to" is a broad expression generally meaning "having a" structure "that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some environments, "configured to" may be a broad recitation of structure generally meaning "having circuitry that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently on. In general, the circuitry forming the structure corresponding to "configured to" may comprise hardware circuitry.

For ease of description, various components may be described as performing one or more tasks. Such description should be construed to include the phrase "configured to". Expressing a component configured to perform one or more tasks is expressly intended to be an interpretation that does not invoke 35u.s.c. § 112(f) on that component.

FIG. 1A and FIG. 1B-communication System

Fig. 1A illustrates a simplified example wireless communication system according to some embodiments. It is noted that the system of fig. 1 is only one example of a possible system, and that the features of the present disclosure may be implemented in any of a variety of systems as desired.

As shown, the exemplary wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B through 106N, etc., over a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Thus, the user equipment 106 is referred to as a UE or UE device.

The Base Station (BS)102A may be a Base Transceiver Station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communication with the UEs 106A-106N.

The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and UE106 may be configured to communicate over a transmission medium utilizing any of a variety of Radio Access Technologies (RATs), also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE-advanced (LTE-a), 5G new radio (5G NR), HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and so forth. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB. Note that if base station 102A is implemented in a 5G NR environment, it may alternatively be referred to as a "gnnodeb" or "gNB.

As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a Public Switched Telephone Network (PSTN) and/or the internet, among various possibilities). Thus, the base station 102A may facilitate communication between user equipment and/or between user equipment and the network 100. In particular, the cellular base station 102A may provide the UE106 with various communication capabilities, such as voice, SMS, and/or data services.

Base station 102A and other similar base stations operating according to the same or different cellular communication standards, such as base station 102b.

Thus, although base station 102A may serve as a "serving cell" for UEs 106A-N as shown in fig. 1, each UE106 may also be capable of receiving signals (and possibly be within its communication range) from one or more other cells (which may be provided by base stations 102B-N and/or any other base stations), which may be referred to as "neighboring cells. Such cells may also be capable of facilitating communication between user equipment and/or between user equipment and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and/or cells providing any of a variety of other granularities of service area sizes. For example, the base stations 102A-B shown in fig. 1 may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

In some embodiments, the base station 102A may be a next generation base station, e.g., a 5G new radio (5G NR) base station or "gNB. In some embodiments, the gNB may be connected to a legacy Evolved Packet Core (EPC) network and/or to a new radio communication core (NRC) network. Further, the gNB cell may include one or more Transmission and Reception Points (TRPs). Further, a UE capable of operating according to the 5G NR may be connected to one or more TRPs within one or more gnbs.

It is noted that the UE106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, e.g., WCDMA or TD-SCDMA air interfaces), LTE-a, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocols (e.g., bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M/H or DVB-H), and/or any other wireless communication protocol. Other combinations of wireless communication standards, including more than two wireless communication standards, are also possible.

Fig. 1B illustrates a user equipment 106 (e.g., one of devices 106A-106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE106 may be a device, such as a mobile phone, a handheld device, a computer or tablet, or virtually any type of wireless device, having cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.).

The UE106 may include a processor configured to execute program instructions stored in a memory. The UE106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, the UE106 may include a programmable hardware element, such as a Field Programmable Gate Array (FPGA) configured to perform any one of the method embodiments described herein or any portion of any one of the method embodiments described herein.

The UE106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE106 may be configured to communicate using, for example, CDMA2000(1xRTT/1xEV-DO/HRPD/eHRPD), LTE/LTE-advanced, or 5G NR using a single shared radio and/or GSM, LTE-advanced, or 5G NR using a single shared radio. The shared radio may be coupled to a single antenna or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, the radio components may include any combination of baseband processors, analog Radio Frequency (RF) signal processing circuits (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuits (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive chains and transmit chains using the aforementioned hardware. For example, the UE106 may share one or more portions of a receive chain and/or a transmit chain among multiple wireless communication technologies, such as those discussed above.

In some embodiments, the UE106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radios) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE106 may include one or more radios shared between multiple wireless communication protocols, as well as one or more radios used exclusively by a single wireless communication protocol. For example, the UE106 may include a shared radio for communicating using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and a separate radio for communicating using each of Wi-Fi and bluetooth. Other configurations are also possible.

FIG. 2-Access Point Block diagram

Fig. 2 illustrates an exemplary block diagram of an Access Point (AP) 112. Note that the block diagram of the AP of fig. 2 is only one example of a possible system. As shown, the AP 112 may include a processor 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a Memory Management Unit (MMU)240 or other circuit or device, which may be configured to receive addresses from the processor 204 and translate the addresses to locations in memory (e.g., memory 260 and Read Only Memory (ROM) 250).

The AP 112 may include at least one network port 270. The network port 270 may be configured to couple to a wired network and provide access to the internet to a plurality of devices, such as the UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide a connection to additional networks, such as the internet.

The AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with the UE106 via the wireless communication circuitry 230. The antenna 234 communicates with the wireless communication circuitry 230 via a communication link 232. The communication chain 232 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, when the AP is co-located with a base station in the case of a small cell, or in other cases where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies including, but not limited to, 5G NR, Long Term Evolution (LTE), LTE-advanced (LTE-a), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, and so forth.

In some embodiments, as described further below, the AP 112 may be configured to implement methods for wireless devices to detect and/or mitigate data stalls during and/or before establishing a data connection, e.g., as described further herein.

FIG. 3-block diagram of a UE

Fig. 3 illustrates an exemplary simplified block diagram of a communication device 106 according to some embodiments. It is noted that the block diagram of the communication device of fig. 3 is only one example of a possible communication device. According to an embodiment, the communication device 106 may be a User Equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and/or a combination of devices, among others. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, the set of components may be implemented as a system on a chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as a separate component or set of components for various purposes. The set of components 300 may be coupled (e.g., communicatively; directly or indirectly) to various other circuitry of the communication device 106.

For example, the communication device 106 can include various types of memory (e.g., including NAND gate (NAND) flash memory 310), input/output interfaces such as a connector I/F320 (e.g., for connecting to a computing system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that can be integrated with the communication device 106 or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., andshort to medium range wireless communication circuit 329 (e.g., Bluetooth)^TMAnd WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for ethernet.

The cellular communication circuitry 330 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as the illustrated antennas 335 and 336. The short-to-medium-range wireless communication circuit 329 may also be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as the antennas 337 and 338 shown. Alternatively, short-to-medium-range wireless communication circuit 329 may be coupled (e.g., communicatively; directly or indirectly) to antennas 335 and 336 in addition to or in lieu of being coupled (e.g., communicatively; directly or indirectly) to antennas 337 and 338. The short-to-medium range wireless communication circuit 329 and/or the cellular communication circuit 330 may include multiple receive chains and/or multiple transmit chains to receive and/or transmit multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

In some embodiments, the cellular communication circuitry 330 may include dedicated receive chains (including and/or coupled (e.g., communicatively; directly or indirectly) to dedicated processors and/or radios) of multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR), as described further below. Further, in some embodiments, the cellular communication circuitry 330 may include a single transmit chain that may be switched between radios dedicated to a particular RAT. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may communicate with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with the dedicated receive chain and a shared transmit chain.

The communication device 106 may also include and/or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and/or a speaker, one or more cameras, one or more buttons, and/or any of a variety of other elements capable of providing information to a user and/or receiving or interpreting user input.

The communication device 106 may also include one or more smart cards 345 having SIM (subscriber identity module) functionality, such as one or more UICC cards (one or more universal integrated circuit cards) 345.

As shown, SOC 300 may include a processor 302 that may execute program instructions for communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to display 360. The processor 302 may also be coupled to a Memory Management Unit (MMU)340, which may be configured to receive addresses from the processor 302 and translate those addresses to locations in memory (e.g., memory 306, Read Only Memory (ROM)350, NAND flash memory 310), and/or to other circuits or devices, such as the display circuit 304, the short-range wireless communication circuit 329, the cellular communication circuit 330, the connector I/F320, and/or the display 360. MMU 340 may be configured to perform memory protections and page table translations or settings. In some embodiments, MMU 340 may be included as part of processor 302.

As described above, the communication device 106 may be configured to communicate using wireless and/or wired communication circuitry. The communication device 106 may be configured to perform methods for detecting and/or mitigating data stalls during data connections and/or prior to establishing data connections with a network, e.g., as further described herein.

As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to transmit scheduling profiles for power conservation to a network. The processor 302 of the communication device 106 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit). Alternatively (or in addition), the processor 302 of the communication device 106, in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, may be configured to implement some or all of the features described herein.

Further, processor 302 may include one or more processing elements, as described herein. Accordingly, the processor 302 may include one or more Integrated Circuits (ICs) configured to perform the functions of the processor 302. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of one or more processors 302.

Further, cellular communication circuitry 330 and short-range wireless communication circuitry 329 may each include one or more processing elements, as described herein. In other words, one or more processing elements may be included in the cellular communication circuitry 330 and, similarly, one or more processing elements may be included in the short-range wireless communication circuitry 329. Accordingly, the cellular communication circuit 330 may include one or more Integrated Circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuit 329. Further, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuit 329.

FIG. 4-block diagram of a base station

Fig. 4 illustrates an example block diagram of a base station 102 in accordance with some embodiments. It is noted that the base station of fig. 4 is only one example of possible base stations. As shown, base station 102 may include a processor 404 that may execute program instructions for base station 102. Processor 404 may also be coupled to a Memory Management Unit (MMU)440 or other circuit or device that may be configured to receive addresses from processor 404 and translate the addresses to locations in memory (e.g., memory 460 and Read Only Memory (ROM) 450).

The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide a plurality of devices, such as the UE device 106, with access to the telephone network as described above in fig. 1 and 2.

The network port 470 (or additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and/or other services to multiple devices, such as UE device 106. In some cases, the network port 470 may be coupled to a telephone network via a core network, and/or the core network may provide the telephone network (e.g., in other UE devices served by a cellular service provider).

In some embodiments, the base station 102 may be a next generation base station, e.g., a 5G new radio (5G NR) base station, or "gNB. In such embodiments, base station 102 may be connected to a legacy Evolved Packet Core (EPC) network and/or to an NR core (NRC and/or 5GC) network. Further, base station 102 may be considered a 5G NR cell and may include one or more Transmit and Receive Points (TRPs). Further, a UE capable of operating according to the 5G NR may be connected to one or more TRPs within one or more gnbs.

The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio 430. Antenna 434 communicates with radio 430 via communication link 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards including, but not limited to, 5G NR, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi and the like.

Base station 102 may be configured to communicate wirelessly using a plurality of wireless communication standards. In some cases, base station 102 may include multiple radios that may enable base station 102 to communicate in accordance with multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio to perform communications according to LTE and a 5G NR radio to perform communications according to 5G NR. In this case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio capable of performing communications in accordance with any of a number of wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further herein below, BS 102 may include hardware and software components for implementing or supporting implementations of features described herein (e.g., for configuring power saving signals in a fifth generation (5G) New Radio (NR) network). The processor 404 of the base station 102 may be configured to implement or support an implementation of some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit), or a combination thereof. Alternatively (or in addition), the processor 404 of the base station 102, in conjunction with one or more of the other components 430, 432, 434, 440, 450, 460, 470, may be configured to implement or support implementations of some or all of the features described herein.

Further, processor 404 may be comprised of one or more processing elements, as described herein. In other words, one or more processing elements may be included in the processor 404. Accordingly, the processor 404 may include one or more Integrated Circuits (ICs) configured to perform the functions of the processor 404. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of one or more processors 404.

Additionally, radio 430 may be comprised of one or more processing elements, as described herein. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more Integrated Circuits (ICs) configured to perform the functions of radio 430. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 430.

FIG. 5: block diagram of cellular communication circuit

Fig. 5 illustrates an exemplary simplified block diagram of a cellular communication circuit according to some embodiments. It is noted that the block diagram of the cellular communication circuit of fig. 5 is only one example of one possible cellular communication circuit. According to an embodiment, the cellular communication circuit 330 may be included in a communication device, such as the communication device 106 described above. As described above, the communication device 106 may be a User Equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and/or a combination of devices, among others.

The cellular communication circuitry 330 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-335b and 336 (in fig. 3). In some embodiments, the cellular communication circuitry 330 may include dedicated receive chains (including and/or coupled (e.g., communicatively; directly or indirectly) to dedicated processors and/or radios) of multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in fig. 5, the cellular communication circuit 330 may include a modem 510 and a modem 520. Modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-a, for example, and modem 520 may be configured for communication according to a second RAT, such as 5G NR, for example.

As shown, modem 510 may include one or more processors 512 and memory 516 in communication with processors 512. The modem 510 may communicate with a Radio Frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX)532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may be in communication with a Downlink (DL) front end 550, which may include circuitry for receiving radio signals via the antenna 335 a.

Similarly, modem 520 can include one or more processors 522 and memory 526 in communication with processors 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with a DL front end 560, which may include circuitry for receiving radio signals via antenna 335 b.

In some implementations, a switch 570 can couple the transmit circuit 534 to an Uplink (UL) front end 572. Further, a switch 570 can couple transmit circuit 544 to an UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Accordingly, when the cellular communication circuitry 330 receives an instruction to transmit in accordance with the first RAT (e.g., supported via the modem 510), the switch 570 may be switched to a first state that allows the modem 510 to transmit signals in accordance with the first RAT (e.g., via a transmit chain that includes the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to the second RAT (e.g., supported via the modem 520), the switch 570 may be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes the transmit circuitry 544 and the UL front end 572).

In some embodiments, the cellular communication circuitry 330 may be configured to perform methods for detecting and/or mitigating data stalls during a data connection and/or prior to establishing a data connection with a network, e.g., as further described herein.

As described herein, modem 510 may include hardware and software components for implementing the features described above or UL data for time division multiplexed NSA NR operations, as well as various other techniques described herein. The processor 512 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit). Alternatively (or in addition), processor 512, in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, may be configured to implement some or all of the features described herein.

Further, processor 512 may include one or more processing elements, as described herein. Accordingly, the processor 512 may include one or more Integrated Circuits (ICs) configured to perform the functions of the processor 512. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of the processor 512.

As described herein, modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

Further, processor 522 may include one or more processing elements, as described herein. Accordingly, the processor 522 may include one or more Integrated Circuits (ICs) configured to perform the functions of the processor 522. Further, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor 522.

5G NR architecture with LTE

In some implementations, fifth generation (5G) wireless communications will initially be deployed concurrently with current wireless communications standards (e.g., LTE). For example, dual connectivity between LTE and 5G new radios (5G NRs or NRs) has been specified as part of the initial deployment of NRs. Thus, as shown in fig. 6A-6B, the Evolved Packet Core (EPC) network 600 may continue to communicate with the current LTE base station (e.g., eNB 602). Further, eNB 602 may communicate with a 5G NR base station (e.g., gNB 604) and may communicate data between EPC network 600 and gNB 604. Thus, EPC network 600 may be used (or reused), and gNB 604 may serve as additional capacity for user equipment, e.g., to provide increased downlink throughput for the UE. In other words, LTE may be used for control plane signaling and NR may be used for user (or data) plane signaling. Thus, LTE may be used to establish a connection with a network and NR may be used for data services.

Fig. 6B shows the proposed protocol stacks for eNB 602 and gNB 604. As shown, eNB 602 may include a Medium Access Control (MAC) layer 632 that interfaces with Radio Link Control (RLC) layers 622a-622 b. The RLC layer 622a may also interface with a Packet Data Convergence Protocol (PDCP) layer 612a, and the RLC layer 622b may interface with a PDCP layer 612 b. Similar to dual connectivity specified in LTE-advanced release 12, PDCP layer 612a may interface with EPC network 600 via a Master Cell Group (MCG) bearer, while PDCP layer 612b may interface with EPC network 600 via a split bearer.

Additionally, as shown, the gNB 604 may include a MAC layer 634 that interfaces with the RLC layers 624 a-b. The RLC layer 624a may interface with the PDCP layer 612b of eNB 602 via an X2 interface for information exchange and/or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Further, the RLC layer 624b may interface with the PDCP layer 614. Similar to the dual connectivity specified in LTE-advanced release 12, the PDCP layer 614 may interface with the EPC network 600 via a Secondary Cell Group (SCG) bearer. Thus, eNB 602 may be considered a primary node (MeNB), while gNB 604 may be considered a secondary node (SgNB). In some cases, the UE may be required to maintain a connection with both the MeNB and the SgNB. In such cases, MeNB may be used to maintain a Radio Resource Control (RRC) connection with the EPC, while SgNB may be used for capacity (e.g., additional downlink and/or uplink throughput).

5G core network architecture-interworking with Wi-Fi

In some embodiments, a 5G Core Network (CN) may be accessed via (or through) a cellular connection/interface (e.g., via a 3GPP communication architecture/protocol) and a non-cellular connection/interface (e.g., a non-3 GPP access architecture/protocol such as a Wi-Fi connection). Fig. 7A illustrates an example of a 5G network architecture that incorporates 3GPP (e.g., cellular) and non-3 GPP (e.g., non-cellular) access at the 5G CN, in accordance with some embodiments. As shown, a user equipment device (e.g., UE 106) may access a 5G CN through both a radio access network (RAN, e.g., a gNB or base station 604) and an access point, such as AP 112. The AP 112 may include a connection to the internet 700 and a connection to a non-3 GPP interworking function (N3IWF)702 network entity. The N3IWF may include a connection to the core access and mobility management function (AMF)704 of the 5G CN. The AMF 704 may include an example of a 5G mobility management (5G MM) function associated with the UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection with AMF 704. Thus, the 5G CN may support unified authentication over both connections and allow simultaneous registration of UE106 access via the gNB 604 and AP 112. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., a Network Slice Selection Function (NSSF)720, a Short Message Service Function (SMSF)722, an Application Function (AF)724, a Unified Data Management (UDM)726, a Policy Control Function (PCF)728, and/or an authentication server function (AUSF) 730). Note that these functional entities may also be supported by Session Management Functions (SMFs) 706a and 706b of the 5G CN. The AMF 706 may be connected to (or in communication with) the SMF 706 a. Further, the gNB 604 may be in communication with (or connected to) a User Plane Function (UPF)708a, which may also be in communication with the SMF 706 a. Similarly, the N3IWF 702 may communicate with the UPF 708b, which may also communicate with the SMF 706 b. Both UPFs may communicate with a data network (e.g., DNs 710a and 710b) and/or internet 700 and IMS core network 710.

Fig. 7B illustrates an example of a 5G network architecture that combines dual 3GPP (e.g., LTE and 5G NR) access and non-3 GPP access at a 5G CN in accordance with some embodiments. As shown, a user equipment device (e.g., UE 106) may access a 5G CN through both a radio access network (RAN, e.g., a gNB or base station 604 or eNB or base station 602) and an access point, such as AP 112. The AP 112 may include a connection to the internet 700 and a connection to an N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an example of 5G MM functionality associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection with AMF 704. Thus, the 5G CN may support unified authentication over both connections and allow simultaneous registration of UE106 access via the gNB 604 and AP 112. In addition, the 5G CN may support dual registration of UEs on both legacy networks (e.g., LTE via base station 602) and 5G networks (e.g., via base station 604). As shown, the base station 602 may have connectivity to a Mobility Management Entity (MME)742 and a Serving Gateway (SGW) 744. MME 742 may have connections to both SGW 744 and AMF 704. Additionally, the SGW 744 may have connections to both the SMF 706a and the UPF 708 a. As shown, the AMF 704 may include one or more functional entities (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730) associated with the 5G CN. Note that UDM 726 may also include Home Subscriber Server (HSS) functionality, and that the PCF may also include Policy and Charging Rules Function (PCRF). Note also that these functional entities may also be supported by SMF 706a and SMF 706b of the 5G CN. The AMF 706 may be connected to (or in communication with) the SMF 706 a. Further, the gNB 604 may communicate with (or be connected to) a UPF 708a, which may also communicate with the SMF 706 a. Similarly, the N3IWF 702 may communicate with the UPF 708b, which may also communicate with the SMF 706 b. Both UPFs may communicate with a data network (e.g., DNs 710a and 710b) and/or internet 700 and IMS core network 710.

It is noted that in various embodiments, one or more of the network entities described above may be configured to perform methods for a wireless device to detect and/or mitigate data stalls during a data connection and/or prior to establishing a data connection with a network, e.g., as further described herein.

Fig. 8 illustrates an example of a baseband processor architecture for a UE (e.g., UE 106) in accordance with some embodiments. As described above, the baseband processor architecture 800 depicted in fig. 8 may be implemented on one or more radios (e.g., radios 329 and/or 330 described above) or modems (e.g., modems 510 and/or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a legacy NAS 850. The legacy NAS 850 may include a communication connection with a legacy Access Stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and non-3 GPP AS 830 and Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with two access stratum layers. Thus, the 5G NAS 820 may include a plurality of 5G MM entities 826 and 828 and 5G Session Management (SM) entities 822 and 824. The legacy NAS 850 may include functional entities such as a Short Message Service (SMS) entity 852, an Evolved Packet System (EPS) session management (ESM) entity 854, a Session Management (SM) entity 856, an EPS Mobility Management (EMM) entity 858, and a Mobility Management (MM)/GPRS Mobility Management (GMM) entity 860. Further, the legacy AS 870 may include functional entities such AS LTE AS 872, UMTS AS 874, and/or GSM/GPRS 876.

Thus, the baseband processor architecture 800 allows a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3 GPP access). Note that as shown, the 5G MM may maintain separate connection management and registration management state machines for each connection. In addition, a device (e.g., UE 106) may register with a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. Furthermore, a device may be in a connected state in one access and in an idle state in another access, or vice versa. Finally, there may be a common 5G-MM procedure (e.g., registration, de-registration, identification, authentication, etc.) for both accesses.

It is noted that in various embodiments, one or more of the above-described elements may be configured to perform a method for implementing a mechanism for detecting and/or mitigating data stalls during a data connection and/or prior to establishing a data connection with a network, e.g., as further described herein.

Cellular enhancement of application mobility

In some existing implementations, when a mobile station or UE transitions out of Wi-Fi coverage, the mobile station may experience a data stall condition, such as a no-response condition to an HTTP-GET query, which is a common HTTP method for requesting data from a specified resource. For example, a data stall condition may occur when a mobile station transitions between Wi-Fi networks (e.g., Wi-Fi roaming), transitions from a Wi-Fi network to a cellular network, and/or transitions between cells of a cellular network. Further, during a data quiesce condition, the web service may be suspended, e.g., the web page may not be loaded in the web browser, or the map may not be refreshed in the web mapping service application. As another example, streaming music or streaming video playback may pause during playback in a data pause condition. Additionally, during data pause conditions, real-time audiovisual calls may be lost, dropped and/or paused. As another example, an email message may not be loaded during a data stall condition.

Additionally, in some existing implementations, recovery from a data stall condition (e.g., transition to or recovery to cellular service) may be delayed because existing cellular service recovery algorithms are based on a periodic timer and are not aware of the Wi-Fi association status of the UE. For example, in some cases, recovery of cellular service while camped on limited service may be attempted every two minutes. In some other cases, recovery of cellular service while camped on limited service may be attempted every six minutes. Similarly, in some cases, service interruption recovery may be attempted once per minute.

Furthermore, as more utilities are accessed by a mobile station in a locked state (e.g., a state in which the functionality of the mobile station user interface is limited as compared to an unlocked state), such data stall conditions become more prominent and recovery slows due to the mobile station's baseband processor being in a limited service state and/or a service interruption state. Additionally, in some implementations, recovery may be slowed down due to the baseband processor rolling back to a slower speed than the optimal RAT before a data stall condition occurs.

Additionally, in some implementations, the baseband processor may be in a "suboptimal" state when the Wi-Fi link is lost (e.g., disconnected or backhaul detection interrupted). For example, the baseband processor may be in an interrupt-of-service state or a limited-service state. In some cases, the baseband processor may have rolled back to a slower speed than the best RAT (e.g., 1X or DO).

In some embodiments, one or more actions may be performed to initiate an immediate service restoration of the cellular interface and/or upgrade the cellular connection to a higher performance RAT (e.g., to LTE and/or 5G NR) in the above-described cases. For example, the application (and/or application/traffic monitor) may inform (and/or inform) the baseband processor when to activate the application with a user equipment device (UE) such as UE106 that is in a locked state. Such a notification may trigger the baseband processor to attempt immediate service recovery if the baseband processor/cellular interface is in a service interruption state or a limited service state. In such implementations, if no service is found, the existing periodic timer may continue to run. As another example, if a Wi-Fi link is lost, the cellular interface may be promoted to a primary level of data traffic. Such triggers may cause a baseband processor in a lower performance state (e.g., service interruption, limited service, and/or attached to a lower performance (or slower than best) RAT) to attempt immediate service recovery (including frequency list scanning), and/or attempt upgrade to a higher performance RAT (e.g., LTE and/or 5G NR). In some embodiments, when the primary level of data traffic changes (or hands off) from Wi-Fi to cellular, the baseband processor (and/or cellular interface) may attempt to be in (and/or transition to) a higher performance state (e.g., having an active connection with LTE and/or 5G NR cell).

In some embodiments, an application (and/or traffic monitor) may collect information related to data stalls and/or data stall predictions and may send (or inform) the collected information to a baseband processor of a UE, such as UE 106. In some embodiments, the collected information may include aggregated data quiesce hints, such as multiple foreground applications that encountered a data quiesce (e.g., did not receive a web response to an HTTP-GET query). In some implementations, the collected information may include warnings from the media stack/layer (or application) (e.g., the core medium detects a reduction in buffer size indicating a possible data stall). In some implementations, such an alert may indicate an upcoming data stall. In some embodiments, the collected information may include DNS failures.

In some embodiments, the media stack/layer (or application) may set an interface (or software entity/layer) to declare an emergency deadline (e.g., a signaling time to emergency), where emergency may be, for example, a data stall condition and/or an unreasonably long startup delay. In some implementations, the media stack/layer may set, update, and/or clear the emergency deadline. In some embodiments, an emergency deadline may be set for each task, and/or tasks may be grouped based at least in part on a shared connection pool. In some embodiments, each time the emergency deadline associated with a connection pool is changed, the interface may determine (or calculate) a next occurring emergency deadline and may set (and/or clear) the next occurring emergency deadline. In some embodiments, interfaces may share an emergency deadline and a connection UUID with other layers (e.g., MPTCP) and/or software entities. In other words, the interface may inform other layers of the emergency deadline and/or the connection UUID. In some implementations, the MPTCP layer may use the emergency deadline to determine (or decide) when to establish the sub-flow. In some embodiments, the software entity may use the emergency deadline to schedule a Reliable Network Fallback (RNF), Wi-Fi roaming scan, and/or RAT upgrade procedure.

For example, fig. 9 illustrates a block diagram of an example of an architecture for data quiesce processing, according to some embodiments. The architecture shown in fig. 9 may be used with (or implemented together with) any of the systems or devices shown in the above figures, as well as other devices. In various embodiments, some of the illustrated elements may be omitted. Additional elements may also be used as desired. As shown, the architecture may operate as follows.

As shown, a connection manager 904 (e.g., a software entity, a layer of a communication fabric, and/or an application) may monitor various data connections 902 a-c. The data connections 902a-c may be used for various upper-level (foreground) applications, such as internet browsers, email applications, and/or various other upper-level applications that may not require low-latency data connections. Connection manager 904 may interact and communicate with a connection interface (or connection core layer) 906. Connection interface 906 may manage HTTP connections (e.g., serving data connections 902 a-c). Additionally, the connection manager 906 may monitor for a response to the HTTP _ GET request, e.g., via communication with the network stack (or layer) 908. The network stack 908 may include a TCP layer 918 (or more generally, a transport layer that supports HTTP transactions over TCP and/or UDP connections) and may interact with a Wi-Fi interface (or layer) 928 and/or a cellular interface (or layer) 938. Thus, connection requests from the data connections 902a-c may flow from the connection manager 904 to one of the Wi-Fi interface 928 or the cellular interface 938 via the connection interface 906 and the network stack 908 (e.g., depending on which interface is the primary interface for the data).

Connection interface 906 may communicate the HTTP _ GET request response to core (layer) 910 (e.g., a software entity, a layer of a communication architecture, and/or an application). Core 910 may report an HTTP response header timeout to monitoring entity 912. Monitoring entity 912 may monitor HTTP response header timeouts on a per upper layer application basis. In other words, monitoring entity 912 may monitor the HTTP response header for each data connection (e.g., each of data connections 902a-c) for a timeout. In some embodiments, monitoring entity 912 may track the number of HTTP response header timeouts for each time period. In other words, monitoring entity 912 may track the number of HTTP response header timeouts within a given time period. Further, monitoring entity 912 may notify telephony entity 914 of the condition when the number of HTTP response header timeouts exceeds a threshold for a period of time. In such cases, telephony entity 914 may report the aggregated data quiesce prompt to a cellular interface 938 (e.g., a cellular baseband processor). Upon receiving the aggregated data quiesce prompt, cellular interface 938 may take one or more actions as described herein.

For example, if cellular interface 938 is in a service-disrupted state or a limited-service state, cellular interface 938 may attempt immediate service resumption. In such implementations, if no service is found, the existing periodic timer may continue to run. As another example, the cellular interface 938 may attempt to upgrade to a more optimized RAT (e.g., LTE and/or 5G NR). As another example, the cellular interface 938 may deprioritize the current cell (e.g., the current LTE and/or 5G NR cell) and attempt to handover (or move) to a better (or best) performing neighbor cell (e.g., the neighbor LTE and/or neighbor 5G NR cell).

In some embodiments, the actions selected by the cellular interface 938 may be based, at least in part, on the cause of the data stall. For example, cellular interface 938 may attempt immediate service discovery based at least in part on data stalls caused by backhaul server problems (e.g., no radio problems detected). As another example, the cellular interface 938 may attempt a RAT upgrade based at least in part on a data stall caused by the cellular interface 938 being connected to a lower-performing RAT. As another example, the cellular interface 938 may attempt handover to a neighboring cell based at least in part on data stalls caused by radio congestion on the current cell (e.g., the current LTE and/or 5G NR cell) and/or congestion on the cellular core network.

In some embodiments, once the cellular interface 938 receives the aggregated data quiesce prompt (or more generally, the data quiesce prompt), the cellular interface 938 may ignore (or ignore) additional data quiesce prompts for a period of time. In other words, to prevent multiple back-to-back data stall cues, the cellular interface 938 may use (or have) a back-off timer that may be started upon receipt of the data stall cue. Thus, any subsequent data stall cue received before the back-off timer expires may be ignored (or disregarded). For example, in some embodiments, the cellular interface 938 may ignore subsequent data stall prompts for 30 seconds (or 1 minute, 2 minutes, etc.) upon receiving the data stall prompts.

As another example, fig. 10 illustrates a block diagram of an example of an architecture for data stall preemption, according to some embodiments. The architecture shown in fig. 10 may be used with (or implemented together with) any of the systems or devices shown in the above figures, as well as other devices. In various embodiments, some of the illustrated elements may be omitted. Additional elements may also be used as desired. As shown, the architecture may operate as follows.

As shown, a media stack 1004 (e.g., a software entity, a layer of a communication architecture, and/or an application) may monitor various media (e.g., streaming content such as video and/or music) connections 1002 a-c. The media connections 1002a-c may be used for various upper-level (foreground) applications, such as a streaming music service and/or a streaming video service and/or various other upper-level applications that may require low-latency data connections. The media stack 1004 may interact and communicate with a connection interface (or connection core) 1006. Connection interface (or layer) 1006 may manage media protocol connections (e.g., serve media connections 1002 a-c). In addition, the connection interface 1006 may monitor for a response to a media protocol request, e.g., via communication with a network stack (or layer) 1008. The network stack 1008 may interact with a Wi-Fi interface (or layer) 1028 and/or a cellular interface (or layer) 1038. Thus, connection requests from the media connections 1002a-c may flow from the media stack 1004 to one of the Wi-Fi interface 1028 or the cellular interface 1038 via the connection interface 1006 and the network stack 1008.

Further, the connection interface 1006 may receive emergency deadline information (e.g., an amount of time to buffer data) from the media stack 1004. The connection interface may communicate the emergency deadline information to the monitoring entity 1012. The monitoring entity 1012 may monitor the emergency deadline information on a per upper layer application basis. In other words, the monitoring entity 1012 may monitor the emergency deadline information for each media connection (e.g., each of the media connections 1002 a-c). In some implementations, the monitoring entity 1012 may provide (or notify) the telephony entity 1014 of a media alert (e.g., an upcoming media pause prompt) any time the emergency deadline (e.g., an amount of time to buffer data) falls below a threshold. In some embodiments, the threshold may be an amount of time, such as 5 seconds, 10 seconds, 15 seconds, and/or 20 seconds. Telephone entity 1014 may report the media alert (e.g., as a data pause prompt) to cellular interface 1038 (e.g., a cellular baseband processor). Upon receiving the media alert, cellular interface 1038 may take one or more actions as described above.

For example, if cellular interface 1038 is in a service interruption state or a limited service state, cellular interface 1038 may attempt immediate service recovery. In such implementations, if no service is found, the existing periodic timer may continue to run. As another example, the cellular interface 1038 may attempt to upgrade to a more optimized RAT (e.g., LTE and/or 5G NR). As another example, the cellular interface 1038 may cancel the priority of the current cell (e.g., the current LTE and/or 5G NR cell) and attempt to handover (or move) to a better (or best) performing neighbor cell (e.g., the neighbor LTE and/or neighbor 5G NR cell).

In some embodiments, the action selected by cellular interface 1038 may be based at least in part on the cause of the media alert (e.g., an upcoming media pause prompt). For example, cellular interface 1038 may attempt immediate service discovery based at least in part on a media alert caused by a backhaul server problem (e.g., no radio problem detected). As another example, cellular interface 1038 may attempt a RAT upgrade based at least in part on a media pre-warning caused by cellular interface 1038 being connected to a lower-performing RAT. As another example, cellular interface 1038 may attempt handover to a neighboring cell based at least in part on a media precaution caused by radio congestion on a current cell (e.g., a current LTE and/or 5G NR cell) and/or congestion on a cellular core network.

In some embodiments, the upgrade to a higher performance RAT may be based on one or more triggers (e.g., upgrade DO from 1X to LTE and/or 5G NR). In some embodiments, transmission watermark checking may be relaxed and/or ignored to allow (immediate) RAT upgrade procedures. In some embodiments, once LTE based, at least one round of frequency list scanning may be performed. In some embodiments, a RAT upgrade may not be triggered if/when it has been attempted within a specified time period (e.g., 15 seconds, 30 seconds, 1 minute, etc.). In some embodiments, RAT upgrade may not be triggered if/when another RAT upgrade procedure is ongoing (e.g., has been triggered based on existing BSR logic). In some embodiments, an Ongoing Out of Service (OOS) timer may not be reset based on the triggering of a RAT upgrade procedure.

In some embodiments, when a UE, such as UE106, is in a Cell-dedicated channel (Cell-DCH) state, various conditions (or criteria) may be met before attempting a RAT upgrade upon receipt of a data stall prompt (and/or a media early warning/upcoming media stall prompt). In some embodiments, the condition may be that the SIB19 message broadcast from a lower performing cell (e.g., UMTS cell) includes a higher performing (e.g., LTE and/or 5G NR) neighbor cell. In some embodiments, another condition may be that the UE previously camped on a higher performing cell/RAT before moving to a lower performing cell/RAT (e.g., for a specified period of time). For example, the UE may have rolled back from a higher performing cell/RAT to a lower performing cell/RAT for voice calls and may not have been able to upgrade back to the higher performing cell/RAT. In some embodiments, the specified time period may be on the order of minutes and/or hours. In some embodiments, another condition may be that the UE has camped on (or connected to) a lower performance cell/RAT for a specified period of time. In some embodiments, the specified time period may be on the order of seconds and/or minutes. In some embodiments, all conditions may need to be met in order for the UE to attempt a RAT upgrade procedure upon receipt of a data stall prompt and/or a media pre-warning/upcoming media stall prompt. In some embodiments, at least one of these conditions may need to be met in order for the UE to attempt a RAT upgrade procedure upon receiving a data stall prompt and/or a media pre-warning. In some embodiments, at least two of these conditions may need to be met in order for the UE to attempt a RAT upgrade procedure upon receiving a data stall prompt and/or a media pre-warning. In some embodiments, additional conditions may be considered and/or required for the UE to attempt a RAT upgrade procedure upon receiving a data stall prompt and/or a media pre-warning.

In some embodiments, when a UE (such as UE 106) receives a data stall warning (and/or a media advance or an upcoming data stall/media stall warning) due to a RACH failure and/or Radio Link Failure (RLF), the UE may not attempt a RAT upgrade procedure until a specified number of RACH failures and/or RLFs have been encountered. In other words, when more than a threshold number of RACH failures, RLFs, and/or combinations of RACH failures and RLFs have been encountered, the UE may (immediately) attempt a RACH upgrade procedure upon receiving a data stall prompt and/or a media advance due to RACH failures and/or RLFs. In some embodiments, the threshold number may be decreased and/or increased based at least in part on the amount of time between RACH failures and/or RLFs, e.g., the threshold number may decrease as the amount of time decreases and/or the threshold number may increase as the amount of time increases.

In some implementations, when a UE is in idle mode, the UE may implement various techniques in order to avoid a particular cell. For example, in some implementations, the UE may collect Random Access Channel (RACH) statistics for a plurality of previously camped cells (e.g., in some implementations, for the last 10 cells camped on). The previously camped-on cell may be saved in a database on the UE, such as a strip cell database. Further, the UE may track multiple RACH failures, IRAT attempts, and/or OOS indications per cell and/or frequency. In some implementations, when respective thresholds are reached (e.g., a specified number of RACH failures, IRAT attempts, OOS indications, and/or some combination thereof exceed the thresholds), the corresponding cell and/or frequencies within the cell may be barred (e.g., the UE will avoid camping on the corresponding cell/frequency). In such cases, the UE may attempt to camp on other cells and/or frequencies that may have fewer (or fewer) problems due to RACH failure, IRAT attempts, and/or OOS indications. Additionally, the UE may disable a particular cell/frequency for a specified period of time (e.g., the UE may start at the time the particular cell/frequency is disabled). In some implementations, after a specified period of time, the UE may again attempt to camp on a previously barred cell and/or frequency.

In some implementations, the UE may force a RAT upgrade to LTE/5G NR based on RACH failure and/or Radio Link Failure (RLF). In some implementations, the UE can check whether the SIB19 broadcast on the 3G cell includes a higher performance (e.g., LTE and/or 5G NR) neighbor cell. In such cases, upon meeting certain thresholds related to RLF and/or RACH failures, the UE may deactivate the WCDMA RAT and trigger an LTE/5G NR search on the network access stratum level to attempt to upgrade the RAT.

In some embodiments, such prohibition of cell/frequency and/or RAT upgrades may be assisted by an Application Processor (AP) of a UE, such as UE106, e.g., a processor that monitors data stall conditions. For example, in some embodiments, the AP may trigger a data stall indication to the baseband processor of the UE (e.g., notify the baseband processor of a data stall condition, such as an actual detected data stall, DNS failure, and/or media stall warning). The baseband processor may then check (or determine) whether the serving cell has a record of RLF and/or RACH failures in the strip database and/or within a specified time period (e.g., within the last 15 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, etc.). Additionally, if the UE is idle and the LTE/5G RN cell is broadcast by the 3G cell (e.g., via SIB19 message), the baseband processor may deactivate the current cell and trigger the RAT upgrade procedure.

In some embodiments, RAT upgrades may be based, at least in part, on initiating applications with low latency requirements, such as video call and/or streaming media applications. Such behavior may be based on applications with low latency requirements launched on lower performance RATs with poor audio/video performance and extended video stutter. In other words, the UE may initiate a RAT upgrade based on launching an application with low latency requirements to avoid poor audio/video performance and extended video stalls. For example, fig. 11 shows various performance values for a video call initiated over an LTE and non-LTE connection. For example, a video call initiated over an LTE cellular connection experiences fewer audio stall conditions than a video call initiated over a non-LTE cellular connection. Thus, initiating a RAT upgrade when a video call is initiated may improve call quality and/or call reliability regardless of the connection used to receive the video call. In some embodiments, a UE (such as UE 106) may attempt a RAT upgrade via SLS scanning for LTE and/or 5G NR cells based on initiating an application with low latency requirements when the UE camps on a standalone (cellular) cell. In some embodiments, if the UE is in a 3G connected state, the UE may attempt to upgrade to LTE and/or 5G NR, e.g., via scanning for cells included in the SIB19 message. Note that in some embodiments, the RAT upgrade procedure may include a hysteresis timer to prevent overscan of RAT upgrade attempts.

Fig. 12 illustrates a block diagram of an example of a method for a wireless device to detect and mitigate data stalls during a data connection and/or before establishing a data connection with a network, in accordance with some embodiments. The method shown in fig. 12 may be used in conjunction with any of the systems or devices shown in the above figures, as well as other devices. In various embodiments, some of the method elements shown may be performed concurrently in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, the method may operate as follows.

At 1202, a wireless device (such as UE 106) can establish a data connection with a network. In some embodiments, the data connection may be established through a Wi-Fi interface (radio) and/or a cellular interface (radio) of the wireless device.

At 1204, the wireless device may monitor the data connection for a data stall condition and/or a data stall prompt. In some implementations, the data quiesce hints may include any one, any combination, and/or all of the following: activating an upper layer application while a user interface of the wireless device is in a locked state, one or more upper layer applications (e.g., initiated/launched by a user) not receiving one or more network responses to HTTP-GET queries for a specified period of time, buffer size reduction for media streaming, DNS failure, launching an application with low latency quality of service requirements at a lower performance cellular connection, Wi-Fi link loss and/or Wi-Fi backhaul interruption (e.g., connected to a Wi-Fi access point but not assigned a valid IP address) for a data connection. In some embodiments, the wireless device monitors network responses to HTTP-GET queries on a per upper layer application basis. In some implementations, the wireless device can monitor HTTP response header timeouts to determine whether the network has responded to an HTTP-GET query.

At 1206, in response to detecting the data stall condition and/or the data stall prompt, the wireless device may perform a remedial action. In some implementations, the wireless device may also start a timer, such as a back-off timer, in response to detecting the data stall condition and/or the data stall prompt. In some embodiments, the wireless device may ignore subsequent (or additional) data stall conditions and/or data stall prompts until the timer expires.

In some embodiments, the remedial action may include the wireless device initiating a service restoration of a cellular interface of the wireless device, initiating a Radio Access Technology (RAT) upgrade procedure, and/or initiating a handover and/or reselection procedure to a neighboring cell. In some embodiments, the remedial action may be based at least in part on the data quiesce condition and/or the reason for the data quiesce prompt. In some embodiments, the reason for the data stall condition and/or the data stall cue may include any one, any combination, and/or all of the following: backhaul server problems, a cellular interface of a wireless device being connected to a cell operating according to a lower performance Radio Access Technology (RAT), congestion on a current cell, congestion on a cellular core network, Random Access Channel (RACH) procedure failure, Radio Link Failure (RLF), and/or starting an application with low latency quality of service requirements on a lower performance cellular connection.

In some embodiments, when the cause of the data stall condition and/or the data stall prompt comprises a backhaul server problem, the first remedial action may comprise the wireless device initiating a service recovery procedure. In some embodiments, when the cause of the data stall condition and/or the data stall prompt comprises the cellular interface of the wireless device being connected to a cell operating according to a lower performance Radio Access Technology (RAT), the first remedial action may comprise the wireless device initiating a Radio Access Technology (RAT) upgrade procedure. In some embodiments, when the cause of the data stall condition and/or the data stall prompt includes congestion on the current cell and/or congestion on the cellular core network, the first remedial action may include the wireless device initiating a handover and/or reselection procedure to the neighboring cell. In some embodiments, when the cause of the data stall condition and/or the data stall prompt comprises a RACH procedure failure and/or an RLF, the first remedial action may comprise the wireless device initiating a RAT upgrade procedure. In some embodiments, when the cause of the data stall condition and/or the data stall prompt comprises launching an application with low latency quality of service requirements on a lower performance cellular connection, the first remedial action may comprise the wireless device initiating a RAT upgrade procedure.

Data stutter handling on LTE

In some implementations, even when on higher performance RATs such as LTE and/or 5G NR, congested areas may experience (very) high cellular congestion, resulting in high data stalls, compared to less populated areas. In some embodiments, the causes of data stalls may include cell level issues, such as congestion, and core network issues. In some implementations, to initiate a data session, a UE may establish a default delay for internet traffic while camped on an LTE band with a corresponding Physical Cell Identifier (PCI). However, if a UE encounters an uplink/downlink (UL/DL) data stall due to network congestion, network overload, and/or any other network problems, there may be no technique for the UE to terminate an unsuccessful data session and attempt to camp on another LTE band/PCI unless the UE meets the connection mode switching criteria. Such a scenario may result in the UE attempting to initiate a data session on the same camped-on LTE band, and the corresponding PCI (assuming the UE does not have mobility issues) resulting in a stalled data session and poor user experience.

In some embodiments, based on the aggregated data stall cue (e.g., as described herein) or DNS failure cue, a baseband processor of a UE, such as the UE106, may trigger various actions, such as deactivation and/or reactivation of the internet PDN and/or local RLF and re-establishment of the RRC connection. In some embodiments, deactivation and/or reactivation of the internet PDN may force the core network to re-establish the context of the UE. In some embodiments, triggering the re-establishment of the local RLF and RRC connection may force the RAN to re-establish the context of the UE. In some embodiments, when multiple data stall cues are received for (or on) a current serving cell (or if multiple data stall cues are received), the baseband processor of the UE may lower the priority of the current serving cell, allowing the UE to move to a higher or best performing neighbor cell.

In some embodiments, after the application processor detects an unsuccessful/stalled data session, the application processor may indicate the unsuccessful/stalled data session to the baseband processor. Further, after receiving the data stall indication from the application processor, the baseband processor may start an inter/intra frequency measurement report and start a timer if there is a strong inter/intra frequency neighbor cell available. Then, if the UE receives an rrcconnecrenfig message from the network for handover to a new PCI, the UE may camp on the new PCI and continue the data session. Alternatively, if the UE does not receive the rrcConnecReconfig message for handover for a period of time and the neighbor cells are available, the UE may terminate the current data session and exit the current serving PCI for a specified period of time and reselect (handover) to the strongest neighbor cell based on idle mode measurement reports from the intra-frequency/inter-frequency neighbor cells. Such a scheme may avoid data stalls and may improve the user experience.

Fig. 13 illustrates a block diagram of an example of a method for avoiding data stalls when camping on an LTE cell, according to some embodiments. The method shown in fig. 13 may be used in conjunction with any of the systems or devices shown in the above figures, as well as other devices. In various embodiments, some of the method elements shown may be performed concurrently in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, the method may operate as follows.

At 1302, a UE (such as UE 106) may camp on an LTE band with a corresponding Physical Cell Identifier (PCI). At 1304, the UE may initiate (e.g., via an upper layer application) a data session. At 1306, an application processor and/or application layer of the UE may determine whether a data stall has been detected. At 1308, if a data pause has not been detected, the UE may continue the data session on the LTE band with the corresponding PCI. Alternatively, at 1310, if a data stall is detected (e.g., the application processor detects an unsuccessful/stalled data session, the application processor may indicate the unsuccessful/stalled data session to the baseband processor), the baseband processor of the UE may determine whether any inter-frequency and/or intra-frequency neighboring cells are included in the connection mode measurement report. If there are no neighboring cells included in the connection mode measurement report, the UE may continue the data session on the LTE band with the corresponding PCI at 1308. Alternatively, at 1312, if there are neighboring cells included in the neighbor report, the baseband processor may determine whether any of the neighboring cells are eligible for handover (e.g., whether any of the neighboring cells have a measured RSRP that exceeds a threshold for radio conditions that trigger a handover). If there are no neighboring cells eligible for handover, the UE may continue the data session on the LTE band with the corresponding PCI at 1308. Alternatively, if there are neighboring cells eligible for handover, the UE may proceed with either of two options (e.g., -1 and-2). As an option, the baseband processor may initiate inter/intra frequency neighbor measurement reporting at 1314, and may initiate a timer for the handover procedure at 1316. At 1318, the UE may determine whether a handover message (e.g., an rrcconnecrenfig message for handover to the new PCI) has been received before the time expires. At 1320, if a handover message has been received before the timer expires, the baseband processor may initiate a handover procedure (e.g., indicated in the handover message) to the new PCI and continue the data session. Alternatively, if a handover message is not received and/or a timer expires, the UE may terminate the data session at 1322. Note that the UE may also choose to terminate the data session at 1322 in response to determining that there are neighboring cells eligible for handover at 1312. At 1324, the baseband processor may monitor inter-frequency and/or intra-frequency measurements, e.g., in RRC idle mode. At 1326, the baseband processor may disable the current serving cell for a specified period of time. At 1328, the baseband processor may initiate an attachment procedure to attach to the new LTE band and corresponding PCI based on the inter-frequency and/or intra-frequency measurements at 1324.

Fig. 14 illustrates a block diagram of an example of a method for a wireless device to detect and/or mitigate data stalls for a data connection when using a higher performance Radio Access Technology (RAT), in accordance with some embodiments. The method shown in fig. 14 may be used in conjunction with any of the systems or devices shown in the above figures, as well as other devices. In various embodiments, some of the method elements shown may be performed concurrently in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, the method may operate as follows.

At 1402, one or more data sessions may be initiated with a network by a wireless device, such as UE 106. In some embodiments, the data connection may be established through a Wi-Fi interface (radio) and/or a cellular interface (radio) of the wireless device. In some embodiments, the wireless device may camp on a cell operating according to a higher performance RAT. In some embodiments, the higher performance RAT may be one of Long Term Evolution (LTE) or fifth generation new radio (5G NR). In some embodiments, the cell may be associated with a first Physical Cell Identifier (PCI);

at 1404, the wireless device can monitor one or more data for a data stall cue and/or a data stall condition. In some implementations, the data quiesce hints may include any one, any combination, and/or all of the following: activating an upper layer application while a user interface of the wireless device is in a locked state, one or more upper layer applications (e.g., initiated/launched by a user) not receiving one or more network responses to HTTP-GET queries for a specified period of time, buffer size reduction for media streaming, DNS failure, launching an application with low latency quality of service requirements on a lower performance cellular connection, Wi-Fi link loss to service a data connection, and/or Wi-Fi backhaul interruption (e.g., connected to a Wi-Fi access point but not assigned a valid IP address). In some embodiments, the wireless device monitors network responses to HTTP-GET queries on a per upper layer application basis. In some implementations, the wireless device can monitor HTTP response header timeouts to determine whether the network has responded to an HTTP-GET query.

At 1406, the wireless device can initiate a handover procedure to the neighboring cell in response to determining that the neighboring cell satisfies the at least one handover condition and detecting the data stall prompt and/or the data stall condition. In some embodiments, determining that the neighboring cell satisfies the at least one handover condition may comprise: the wireless device determines that the neighbor cell is included in the connected mode measurement report as an inter-frequency and/or intra-frequency neighbor cell; and determining that the neighboring cell has a measured Received Signal Received Power (RSRP) that exceeds a threshold of radio conditions for triggering the handover. In some embodiments, the connection mode measurement report may include a rrcconnecrenfig message.

In some embodiments, initiating a handover and/or reselection procedure to a neighboring cell may include the wireless device initiating an inter-frequency/intra-frequency measurement report and starting a handover (or reselection) timer. In such embodiments, the wireless device may initiate a handover procedure to the new PCI as indicated by the handover message in response to receiving the handover message from the cell before the handover timer expires, and may continue the data session on the new PCI. In some embodiments, in response to determining that a handover message has not been received from a cell before a handover timer expires, the wireless device may terminate a data session, monitor for inter-frequency/intra-frequency measurements while in Radio Resource Control (RRC) idle mode, inhibit the cell for a specified period of time, and initiate an attachment procedure to attach to a new cell and corresponding PCI based on the inter-frequency and/or intra-frequency measurements. Additionally, the wireless device may initiate a new data session on the corresponding PCI.

In some embodiments, initiating a handover and/or reselection procedure to a neighboring cell may include the wireless device monitoring inter-frequency/intra-frequency measurements while in Radio Resource Control (RRC) idle mode, barring the cell for a specified time period, initiating an attachment procedure to attach to a new cell and a corresponding PCI based on the inter-frequency and/or intra-frequency measurements, and initiating a new data session on the corresponding PCI.

It is well known that the use of personally identifiable information should comply with privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be explicitly stated to the user.

Embodiments of the present disclosure may be implemented in any of various forms. For example, some embodiments may be implemented as a computer-implemented method, a computer-readable memory medium, or a computer system. Other embodiments may be implemented using one or more custom designed hardware devices, such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements, such as FPGAs.

In some embodiments, a non-transitory computer-readable memory medium may be configured such that it stores program instructions and/or data, wherein the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets.

In some embodiments, a device (e.g., UE106 or BS 102) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The apparatus may be embodied in any of various forms.

Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims (20)

1. A user equipment device (UE), the UE comprising:

at least one antenna;

at least one radio, wherein the at least one radio is configured to perform cellular communication using at least one radio access technology, RAT;

one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform voice and/or data communications;

wherein the one or more processors are configured to cause the UE to:

establish a data connection with a network via one of a Wi-Fi interface or a cellular interface;

monitoring the data connection for data stall conditions and/or data stall cues;

in response to detecting the data quiesce condition and/or the data quiesce prompt, performing at least one remedial action, wherein the remedial action includes at least one of:

initiating a service recovery of the cellular interface of the UE;

initiating a radio access technology, RAT, upgrade procedure; or

A handover and/or reselection procedure to a neighboring cell is initiated.

2. The UE of claim 1, wherein the UE is further configured to,

wherein the data stall condition and/or the data stall prompt comprise one or more of:

activating an upper layer application when a user interface of the UE is in a locked state;

one or more upper-layer applications initiated by the user do not receive one or more network responses to the HTTP-GET query within a specified time period;

buffer size reduction for media streams;

a DNS failure;

launching an application with a low latency quality of service requirement over a lower performance cellular connection;

a Wi-Fi link loss serving the data connection; or

Wi-Fi backhaul interruption.

3. The UE of claim 2, wherein the UE is further configured to,

wherein the UE monitors network responses to HTTP-GET queries on a per upper layer application basis.

4. The UE of claim 2, wherein the UE is further configured to,

wherein the one or more processors are further configured to cause the UE to:

HTTP response header timeouts are monitored to determine if the network has responded to an HTTP-GET query.

5. The UE of claim 1, wherein the UE is further configured to,

wherein the at least one remedial action is based at least in part on a data stall condition and/or a reason for a data stall prompt, and wherein the reason for a data stall condition and/or a data stall prompt includes one or more of:

a backhaul server problem;

the cellular interface of the UE is connected to a cell operating according to a lower performance radio access technology, RAT;

congestion on the current cell;

congestion on the cellular core network;

random access channel RACH process failure;

radio link failure, RLF; or

An application with low latency quality of service requirements is started on a lower performance cellular connection.

6. The UE of claim 5, wherein the UE is further configured to,

wherein when the cause of the data stall condition and/or data stall prompt comprises a backhaul server problem, a first remedial action comprises the UE initiating a service recovery procedure;

wherein, when the cause of the data stall condition and/or data stall prompt comprises the cellular interface of the UE being connected to a cell operating according to a lower performing RAT, a first remedial action comprises the UE initiating a RAT upgrade procedure;

wherein, when the cause of the data stall condition and/or data stall prompt comprises congestion on a current cell and/or congestion on a cellular core network, a first remedial action comprises the UE initiating a handover and/or reselection procedure to a neighboring cell;

wherein when the cause of the data stall condition and/or data stall prompt comprises a RACH procedure failure and/or RLF, a first remedial action comprises the UE initiating a RAT upgrade procedure; and

wherein when the cause of the data stall condition and/or data stall prompt comprises launching an application with low latency quality of service requirements on a lower performance cellular connection, the first remedial action comprises the UE initiating a RAT upgrade procedure.

7. The UE of claim 1, wherein the UE is further configured to,

wherein the one or more processors are further configured to cause the UE to:

starting a timer in response to detecting a data stall condition and/or a data stall prompt; and

ignoring subsequent data stall conditions and/or data stall prompts until the timer expires.

8. An apparatus, comprising:

a memory; and

at least one processor in communication with the memory;

wherein the at least one processor is configured to:

camping on a cell operating according to a higher performance radio access technology, RAT, wherein the higher performance RAT comprises one of Long term evolution, LTE, or fifth generation new radio, 5G NR, and wherein the cell is associated with a first physical cell identifier, PCI;

generating instructions for initiating one or more data sessions;

monitoring the one or more data sessions for data stall cues and/or data stall conditions;

in response to determining that a neighboring cell satisfies at least one handover condition and detecting a data stall prompt and/or a data stall condition, a handover and/or reselection procedure to the neighboring cell is initiated.

9. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein to determine that the neighboring cell satisfies at least one handover condition, the at least one processor is further configured to:

determining that the neighbor cell is included in a connected mode measurement report as an inter-frequency and/or intra-frequency neighbor cell; and

determining that the neighboring cell has a measured received signal received power, RSRP, that exceeds a threshold of radio conditions for triggering a handover.

10. The apparatus of claim 9, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein the connection mode measurement report comprises a rrcConnecReconfig message.

11. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein, to initiate a handover and/or reselection procedure to the neighboring cell, the at least one processor is further configured to:

generating instructions for initiating inter-frequency/intra-frequency measurement reporting; and

an instruction to start a switchover timer is generated.

12. The apparatus of claim 11, wherein the first and second electrodes are disposed in a substantially cylindrical configuration,

wherein the at least one processor is further configured to:

in response to receiving a handover message from the cell before the handover timer expires, generating instructions for initiating a handover procedure to a new PCI indicated by the handover message; and

continuing the one or more data sessions on the new PCI.

13. The apparatus of claim 11, wherein the first and second electrodes are disposed in a substantially cylindrical configuration,

wherein the at least one processor is further configured to:

terminating the one or more data sessions in response to determining that a handover message has not been received from the cell prior to expiration of the handover timer;

monitoring inter/intra frequency measurements while in radio resource control, RRC, idle mode;

barring the cell for a specified time period;

generating instructions for initiating an attachment procedure to attach to a new cell and a corresponding PCI based on the inter-frequency and/or intra-frequency measurements; and

generating an instruction to initiate a new data session on the corresponding PCI.

14. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein to generate instructions to initiate a handover and/or reselection procedure to the neighboring cell, the at least one processor is further configured to:

monitoring inter/intra frequency measurements while in radio resource control, RRC, idle mode;

barring the cell for a specified time period;

generating instructions for initiating an attachment procedure to attach to a new cell and a corresponding PCI based on the inter-frequency and/or intra-frequency measurements; and

generating an instruction to initiate a new data session on the corresponding PCI.

15. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein the data stall condition and/or the data stall prompt comprise one or more of:

activating an upper layer application while a user interface in communication with the device is in a locked state;

one or more upper-layer applications initiated by the user do not receive one or more network responses to the HTTP-GET query within a specified time period;

buffer size reduction for media streams;

a DNS failure;

launching an application with a low latency quality of service requirement over a lower performance cellular connection; and/or

A Wi-Fi link serving the one or more data sessions is lost.

16. The apparatus as set forth in claim 15, wherein,

wherein the device monitors network responses to HTTP-GET queries on a per upper-layer application basis; and wherein the at least one processor is further configured to:

HTTP response header timeouts are monitored to determine if the network has responded to HTTP-GET queries.

17. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

wherein, to generate instructions for initiating a handover and/or reselection procedure to the neighboring cell, the at least one processor is further configured to perform at least one of:

forcing a core network to re-establish context via deactivation and/or reactivation of an internet packet data network, PDN;

forcing a re-establishment of context with the radio access network ran via triggering of the local radio link failure, RLF, and re-establishment of the radio resource control, RRC, connection; or

Triggering reselection and/or handover to the neighboring cell via lowering the priority of the cell.

18. A non-transitory computer readable memory medium storing program instructions executable by processing circuitry to cause a user equipment device, UE, to:

establish a data connection with a network via one of a Wi-Fi interface or a cellular interface;

monitoring the data connection for data stall conditions and/or data stall cues;

in response to detecting the data quiesce condition and/or the data quiesce prompt, performing at least one remedial action, wherein the remedial action includes at least one of:

initiating a service recovery of the cellular interface of the UE;

initiating a radio access technology, RAT, upgrade procedure; or

A handover and/or reselection procedure to a neighboring cell is initiated.

19. The non-transitory computer readable memory medium of claim 18,

wherein when the cause of the data quiesce condition and/or data quiesce prompt comprises a backhaul server problem, a first remedial action comprises initiating a service recovery procedure; and

wherein when the cause of the data stall condition and/or data stall prompt comprises congestion on a current cell and/or congestion on a cellular core network, the first remedial action comprises initiating a handover and/or reselection procedure to a neighboring cell.

20. The non-transitory computer readable memory medium of claim 18,

wherein, when the cause of the data stall condition and/or data stall prompt comprises at least one of: the cellular interface of the UE is connected to a cell operating according to a lower performing RAT, a random access channel RACH procedure failure and/or a radio link failure, RLF, or an application with low latency quality of service requirements is started on a lower performing cellular connection.

Images