Data inactivity indication and accelerated recovery actions

Abstract

Certain aspects of the present disclosure provide techniques for wireless communications, and more particularly, provide techniques for detecting data inactivity and accelerating recovery actions. A method that may be performed by a user equipment (UE) includes maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and if the inactivity expires due to one or more conditions, accelerating one or more recovery actions.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 174,179, filed on February 11, 2021, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 975,622, filed on February 12, 2020, both of which are assigned to the assignee of the present application and are hereby expressly incorporated by reference in their entireties as if fully set forth below and for all applicable purposes. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications and, more particularly, to detecting data inactivity and accelerating recovery actions. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations, each base station simultaneously supporting communication for multiple communication devices, which are further referred to as user equipment (UE). In a long term evolution (LTE) or advanced LTE (LTE-A) network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation or 5G network), a wireless multiple access communication system may include multiple distributed units (DU) (e.g., edge units (EU), edge nodes (EN), radio heads (RH), smart radio heads (SRH), transmit receive points (TRP), etc.) communicating with multiple central units (CU) (e.g., central nodes (CN), access node controllers (ANC), etc.), wherein a set of one or more distributed units communicating with a central unit may define an access node (e.g., a new radio base station (NR BS), a new radio node B (NR NB), a network node, a 5G NB, a gNB, a gNodeB, etc.). A base station or DU may communicate with a set of UEs on downlink channels (eg, for transmissions from the base station or to the UE) and uplink channels (eg, for transmissions from the UE to the base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example of an emerging telecommunication standard is New Radio (NR), for example, 5G radio access. NR is an enhancement set to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL) to better integrate with other open standards, and is designed to better support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, further improvements to NR technology are needed. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that adopt them. Summary of the invention

[0008] Aspects of the present disclosure relate to wireless communications and, more particularly, to detecting data inactivity and accelerating recovery actions.

[0009] Certain aspects may be implemented in a method for wireless communication by a user equipment (UE). The method generally includes maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and accelerating one or more recovery actions if the inactivity expires due to one or more conditions.

[0010] Certain aspects may be implemented in an apparatus for wireless communication by a user equipment (UE). The apparatus may include a processing system including: a memory including computer-executable instructions and one or more processors configured to execute the computer-executable instructions and cause the processing system to: maintain at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and if the inactivity expires due to one or more conditions, accelerate one or more recovery actions.

[0011] Certain aspects may be implemented in an apparatus for wireless communication by a user equipment (UE). The apparatus may include means for maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and means for accelerating one or more recovery actions if the inactivity expires due to one or more conditions.

[0012] Certain aspects may be implemented in a non-transitory computer-readable medium for wireless communications by a user equipment (UE). The non-transitory computer-readable medium may include computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to: maintain at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and if the inactivity expires due to one or more conditions, accelerate one or more recovery actions.

[0013] Certain aspects may be implemented in a computer program product for wireless communication by a user equipment (UE) embodied on a computer-readable storage medium. The computer-readable storage medium may include code for maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled and accelerating one or more recovery actions if the inactivity expires due to one or more conditions.

[0014] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein in terms of their organization and method of operation and the associated advantages will be better understood through the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims.

[0015] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that other implementations and use cases may occur in many different arrangements and scenarios. The innovations herein may be implemented on many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses may be implemented via integrated chip embodiments and / or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, a wide range of applicability of the described innovations may occur. The range of implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further aggregated, distributed, or OEM devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, the devices in combination with the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc.) The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0016] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0018] Figure 2 is a block diagram illustrating an example logical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0019] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0020] Figure 4 is a block diagram conceptually illustrating designs of an example BS and UE in accordance with certain aspects of the present disclosure.

[0021] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0022] Figure 6Illustrated is an example of a frame format for a New Radio (NR) system in accordance with certain aspects of the present disclosure.

[0023] Figure 7 Examples of P1 , P2 , and P3 processes according to certain aspects of the present disclosure are illustrated.

[0024] Figure 8 Example considerations that may impact the Radio Link Failure (RLF) procedure are illustrated.

[0025] Fig. 9 An example RLF timer and a trigger for starting the RLF timer are illustrated.

[0026] Fig.10 An example RLF timer and a trigger for terminating the RLF timer are illustrated.

[0027] Fig.11 Example operations that may be performed by a user equipment (UE) according to aspects of the present disclosure are illustrated.

[0028] Fig.12 is a diagram illustrating an example wireless communication network with non-terrestrial network entities in accordance with certain aspects of the present disclosure.

[0029] Fig.13 Illustrated are example wireless communications devices configured to perform operations for the methods disclosed herein in accordance with certain aspects of the present disclosure.

[0030] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. DETAILED DESCRIPTION

[0031] Various aspects of the present disclosure relate to wireless communications, and more specifically, to detecting data inactivity and accelerating recovery actions. For example, in some cases, due to various reasons in the uplink (UL) and downlink (DL), data activity (e.g., transmission / reception) may be stalled or gated at a user equipment (UE) in a network. This stagnation of data activity may result in an increase in latency associated with transmission / reception at the UE and a poor user experience. Therefore, various aspects of the present disclosure provide techniques for accelerating recovery actions when the stagnation of data activity is due to one or more specific reasons. By accelerating the recovery action, the UE is able to more quickly restore connection to the network and mitigate stagnant data activity.

[0032] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for New Radio (NR) (new radio access technology or 5G technology).

[0033] NR can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., above 80 MHz), millimeter wave (mmW) targeting high carrier frequency (e.g., 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0034] Due to the availability of large amounts of bandwidth, certain multi-beam wireless systems such as mmW systems are bringing gigabit speeds to cellular networks. However, the unique challenges of severe path loss faced by mmWave systems require new technologies such as hybrid beamforming (analog and digital), which do not exist in 3G and 4G systems. Hybrid beamforming can enhance the link budget / signal-to-noise ratio (SNR) that can be utilized during RACH.

[0035] In such a system, a Node B (NB) and a User Equipment (UE) may communicate using beamforming transmissions. In order for beamforming to operate correctly, the NB may need to monitor the beam using beam measurements performed (e.g., based on a reference signal sent by the NB) and feedback generated at the UE. However, since the direction of the reference signal is unknown to the UE, the UE may need to evaluate several beams to obtain the best Rx beam for a given NB Tx beam. Therefore, if the UE must "sweep" all of its Rx beams to perform measurements (e.g., to determine the best Rx beam for a given NB Tx beam), the UE may incur significant delays in the measurements and battery life impact. In addition, having to scan through all Rx beams is very resource inefficient. Therefore, aspects of the present disclosure provide techniques for assisting UEs when using Rx beamforming to perform measurements of serving cells and neighboring cells.

[0036] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace, or add various processes or components. For example, the method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of various aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method, which is practiced using other structures, functions, or structures and functions other than or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred or superior to other aspects.

[0037] The techniques described herein can be used in various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. Cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Fast-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology under development together with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA 2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the above-mentioned wireless networks and radio technologies, as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other communication systems based on generations, such as 5G and later generations, including NR technologies.

[0038] Example Wireless Communication System

[0039] Figure 1 An example wireless network 100 is illustrated in which aspects of the present disclosure may be performed. For example, one or more UEs 120, such as UE 120a, may include an accelerated recovery manager 122. The accelerated recovery manager 122 may be configured to perform Fig.11 Operation 1100 and other operations disclosed herein for detecting data inactivity and accelerating recovery actions.

[0040] like Figure 1 As shown, wireless network 100 may include multiple BSs 110 and other network entities. According to one example, network entities including BSs and UEs may communicate at high frequencies (eg, >6 GHz) using beams.

[0041] A BS may be a station that communicates with a UE. Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a Node B and / or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and gNB, Node B, 5G NB, AP, NR BS, or TRP may be interchangeable. In some examples, a cell is not necessarily fixed, and the geographic area of ​​a cell may move according to the location of a mobile base station. In some examples, base stations may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in a wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, or similar interfaces using any suitable transport networks).

[0042] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0043] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users at home, etc.). The BS of a macro cell may be referred to as a macro BS. The BS of a pico cell may be referred to as a pico BS. The BS of a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the illustrated example, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

[0044] The wireless network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown, a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.

[0045] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).

[0046] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, BSs may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0047] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. Network controller 130 may communicate with BSs 110 via a backhaul. BSs 110 may also communicate with each other (eg, directly or indirectly via a wireless or wired backhaul).

[0048] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premise equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smart book, ultrabook, medical device or medical equipment, biosensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium. Some UEs may be considered as devices of evolution or machine type communication (MTC), or devices of evolution MTC (eMTC). MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a BS, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices.

[0049] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on a downlink and / or uplink. A dashed line with double arrows indicates interfering transmissions between a UE and a BS.

[0050] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0051] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may also be applicable to other wireless communication systems, such as NR.

[0052] NR may utilize OFDM with CP on both the uplink and downlink, and may include support for half-duplex operation using TDD. A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers in a duration of 0.1 ms, with a subcarrier bandwidth of 75 kHz. In one aspect, each radio frame may include 50 subframes, each having a length of 10 ms. Thus, each subframe may have a length of 0.2 ms. On the other hand, each radio frame may consist of 10 subframes, each having a length of 10 ms, wherein each subframe may have a length of 1 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction for each subframe may be switched dynamically. Each subframe may include DL / UL data and DL / UL control data. The UL and DL subframes for NR may be as follows for Figure 6 and 7A more detailed description is given below. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. The MIMO configuration in the DL can support up to 8 transmit antennas, multi-layer DL transmission of up to 8 streams, and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported with up to 8 serving cells. Alternatively, NR can support different air interfaces other than OFDM-based interfaces. The NR network can include entities such as CU and / or DU.

[0053] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communication between some or all devices and equipment within its service area or cell. In the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. The base station is not the only entity that can act as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE acts as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. The UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In a mesh network example, in addition to communicating with a scheduling entity, UEs may optionally communicate directly with each other.

[0054] Thus, in a wireless communication network with scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more slave entities may communicate using the scheduled resources.

[0055] As described above, the RAN may include a CU and a DU. A NR BS (e.g., a gNB, a 5G Node B, a Node B, a Transmit Receiving Point (TRP), an Access Point (AP)) may correspond to one or more BSs. NR cells may be configured as access cells (ACells) or data-only cells (DCells). For example, a RAN (e.g., a central unit or a distributed unit) may configure a cell. A DCell may be a cell for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or switching. In some cases, a DCell may not send a synchronization signal - in some cases, a DCell may send an SS. The NR BS may send a downlink signal indicating the cell type to the UE. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs based on the indicated cell type to consider for cell selection, access, switching, and / or measurement.

[0056] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is shown, which may be Figure 1 The distributed RAN 200 is implemented in the wireless communication system shown. The 5G access node 206 may include an access node controller (ANC) 202. The ANC may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC. The backhaul interface to the adjacent next generation access node (NG-AN) may terminate at the ANC. The ANC may include one or more TRPs 208 (which may also be referred to as BS, NR BS, Node B, 5G NB, AP, or some other terminology). As described above, TRP may be used interchangeably with "cell".

[0057] The TRP 208 may be a DU. The TRP may be connected to one ANC (ANC 202) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0058] The local architecture 200 can be used to illustrate the fronthaul definition. The architecture can be defined to support fronthaul solutions across different deployment types. For example, the architecture can be based on the sending network capabilities (e.g., bandwidth, latency, and / or jitter bandwidth).

[0059] The architecture may share features and / or components with LTE. According to various aspects, the next generation AN (NG-AN) 210 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

[0060] The architecture may support collaboration between TRPs 208. For example, collaboration may be provisioned within a TRP and / or across TRPs via ANC 202. According to various aspects, an inter-TRP interface may not be required / existent.

[0061] According to various aspects, there may be a dynamic configuration of split logic functions within the architecture 200. Figure 5Described in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU or CU (e.g., TRP or ANC, respectively). According to certain aspects, the BS can include a central unit (CU) (e.g., ANC 202) and / or one or more distributed units (e.g., one or more TRPs 208).

[0062] Figure 3 An example physical architecture of a distributed RAN 300 according to aspects of the present disclosure is illustrated. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU may be centrally deployed. C-CU functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0063] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the network edge.

[0064] The DU 306 may host one or more TRPs (edge ​​nodes (EN), edge units (EU), radio heads (RH), smart radio heads (SRH), etc.) The DU may be located at the edge of the network with radio frequency (RF) capabilities.

[0065] Figure 4 Picture shows Figure 1 1 and 2, which may be used to implement various aspects of the present disclosure. The BS may include a TRP or a gNB.

[0066] At the base station 110, the transmit processor 420 may receive data from the data source 412 and control information from the controller / processor 440. The control information may be used for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. The data may be used for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, such as for PSS, SSS, and cell-specific reference signals (CRS). The transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable), and may provide an output symbol stream to a modulator (MOD) in a transceiver 432a-432t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator in transceivers 432a-432t may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 432a-432t may be transmitted via antennas 434a-434t, respectively.

[0067] At the UE 120, antennas 452a-452r may receive downlink signals from the base station 110 and may provide received signals to demodulators (DEMODs) in transceivers 454a-454r, respectively. Each demodulator in the transceivers 454a-454r may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator in the transceivers 454a-454r may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 456 may obtain received symbols from all demodulators in the transceivers 454a-454r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to the data sink 460, and provide decoded control information to the controller / processor 480.

[0068] On the uplink, at the UE 120a, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals. The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466, if applicable, further processed by modulators in the transceivers 454a-454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120a may be received by the antennas 434a-434t, processed by the modulators in the transceivers 432a-432t, detected by the MIMO detector 436 (if applicable), and further processed by the receive processor 438 to obtain decoded data and control information transmitted by the UE 120a. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

[0069] Memories 442 and 482 may store data and program codes for BS 110 and UE 120a, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0070] The antennas 452, processors 466, 458, 464, and / or controller / processor 480 of the UE 120a may be used to perform the various techniques and methods described herein. Figure 2 As shown, the controller / processor 480 of the UE 120a includes an accelerated recovery manager 281, which may be configured to perform Fig.11 The operations shown in and other operations described herein for detecting data inactivity and accelerating recovery actions. Although shown at the controller / processor, other components of UE 120a and BS 110 may be used to perform the operations described herein.

[0071] Figure 5Figure 500 showing an example for implementing a communication protocol stack according to various aspects of the present disclosure is illustrated. The communication protocol stack shown can be implemented by a device operating in a 5G system. Figure 500 illustrates a communication protocol stack including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack can be implemented as separate software modules, parts of a processor or ASIC, parts of non-colocated devices connected by a communication link, or various combinations thereof. Co-location and non-co-location implementations can be used in, for example, a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0072] The first option 505-a shows a split implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2 ANC 202 in ) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by the central unit, and the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may be collocated or non-collocated. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

[0073] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), new radio node-B (NR NB), network node (NN), etc.). In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN. The second option 505-b may be useful in femtocell deployment.

[0074] Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (eg, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).

[0075] Figure 6600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes, each of which has a duration of 1 ms and an index of 0 to 9. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to the symbol period in each slot. A microslot, which may be referred to as a subslot structure, refers to a transmission time interval having a duration less than one slot (e.g., 2, 3, or 4 symbols).

[0076] Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission, and the link direction for each subframe may be switched dynamically. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0077] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two symbols PBCH. It can be transmitted at fixed time slot positions (such as Figure 6 SS blocks are sent in symbols 0-3 shown in . The UE can use PSS and SSS for cell search and acquisition. PSS can provide half-frame timing, and SSS can provide CP length and frame timing. PSS and SSS can provide cell identification. PBCH carries some basic system information, such as downlink system bandwidth, timing information within a radio frame, SS burst set period, system frame number, etc. SS blocks can be organized into several SS bursts to support beam scanning. More system information, such as remaining minimum system information (RMSI), system information block (SIB), and other system information (OSI) can be sent on the physical downlink shared channel (PDSCH) in certain subframes.

[0078] The UE may operate in various radio resource configurations, including a configuration associated with sending a pilot using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.), or a configuration associated with sending a pilot using a common resource set (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for transmitting a pilot signal to the network. When operating in the RRC common state, the UE may select a common resource set for transmitting a pilot signal to the network. In either case, the pilot signal sent by the UE may be received by one or more network access devices (such as an AN, or a DU, or a portion thereof). Each receiving network access device may be configured to receive and measure a pilot signal sent on a common resource set, and also receive and measure a pilot signal sent on a dedicated resource set allocated to a UE, wherein the network access device is a member of a monitoring set of network access devices of the UE. The CU receiving the measurement of the pilot signal sent to it by one or more or (a plurality of) receiving network access devices may use the measurement to identify a serving cell for the UE, or initiate a change in a serving cell for one or more UEs of the UE.

[0079] Example beam refinement process

[0080] As described above, in some multi-beam systems (e.g., millimeter wave (mmW) cellular systems), beamforming may be required to overcome high path loss. As described herein, beamforming may refer to establishing a link between a BS and a UE, wherein the two devices form beams corresponding to each other. Both the BS and the UE find at least one sufficient beam to form a communication link. The BS beam and the UE beam form a so-called beam pair link (BPL). As an example, on the DL, the BS may use a transmit beam, and the UE may receive a transmission using a receive beam corresponding to the transmit beam. The combination of a transmit beam and a corresponding receive beam may be a BPL.

[0081] As part of beam management, the beams used by the BS and UE must be refined from time to time due to changing channel conditions, for example, due to movement of the UE or other objects. In addition, the performance of the BPL may suffer from fading due to Doppler spread. Since channel conditions change over time, the BPL should be updated or refined periodically. Therefore, it may be beneficial if the BS and UE monitor the beams and new BPLs.

[0082] At least one BPL must be established for network access. As mentioned above, new BPLs may need to be discovered later for different purposes. The network may decide to use different BPLs for different channels, or for communicating with different BSs (TRPs), or as a backup BPL in case of failure of an existing BPL.

[0083] The UE usually monitors the quality of the BPL, and the network may refine the BPL from time to time.

[0084] Figure 7 An example of BPL discovery and refinement is shown. In 5G NR, P1, P2, and P3 procedures are used for BPL discovery and refinement. The network uses the P1 procedure to enable the discovery of new BPLs. In the P1 procedure, Figure 7 As shown, the BS transmits different symbols of the reference signal, and each beam is formed in a different spatial direction so as to reach several (most, all) relevant positions of the cell. In other words, the BS transmits beams in different directions over time using different transmit beams.

[0085] In order to successfully receive at least one symbol of this "P1 signal", the UE must find a suitable receive beam. It searches using the available receive beams and applying a different UE beam during each occurrence of the periodic P1 signal.

[0086] Once the UE successfully receives a symbol of the P1 signal, it discovers the BPL. The UE may not want to wait until it has found the best UE receive beam, as this may delay further action. The UE may measure the Reference Signal Received Power (RSRP) and report the symbol index along with the RSRP to the BS. Such a report will typically contain the discovery of one or more BPLs.

[0087] In an example, the UE may determine received signals with high RSRP. The UE may not know which beam the BS uses to transmit; however, the UE may report to the BS the times when it observes signals with high RSRP. The BS may receive the report and may determine which BS beam the BS uses at a given time.

[0088] The BS may then provide P2 and P3 processes to refine the individual BPLs. The P2 process refines the BS beam of the BPL. The BS may transmit several symbols of the reference signal using different BS beams that are spatially close to the BS beam of the BPL (the BS performs scanning using neighboring beams around the selected beam). In P2, the UE keeps its beam constant. Therefore, when the UE uses the same beam as in the BPL (e.g. Figure 7 The BS beams used for P2 may be different from the BS beams used for P1 because they may be spaced closer together or they may be more focused. The UE may measure the RSRP of the various BS beams and indicate the best one to the BS.

[0089] The P3 process refines the UE beam of the BPL (see Figure 7P3 process in ). While the BS beam remains constant, the UE scans using different receive beams (the UE performs scanning using adjacent beams). The UE can measure the RSRP of each beam and identify the best UE beam. The UE can then use the best UE beam for BPL and report the RSRP to the BS.

[0090] Over time, the BS and UE establish several BPLs. When the BS sends a specific channel or signal, it lets the UE know which BPL will be involved so that the UE can tune in the direction of the correct UE receive beam before the signal starts. In this way, each sample of the signal or channel can be received by the UE using the correct receive beam. In an example, the BS can indicate which BPL is involved for a scheduling signal (SRS, CSI-RS) or channel (PDSCH, PDCCH, PUSCH, PUCCH). In NR, this information is called a QCL indication.

[0091] If the properties of the channel conveying symbols on one antenna port can be inferred from the channel conveying symbols on the other antenna port, then the two antenna ports are QCL. QCL supports at least beam management functions, frequency / timing offset estimation functions, and RRM management functions.

[0092] The BS may use the BPL that the UE has received in the past. The transmit beam for the signal to be transmitted and the previously received signal both point in the same direction or are QCLs. A QCL indication may be required by the UE (before the signal to be received) so that the UE can use the correct receive beam for each signal or channel. Some QCL indications may sometimes be needed when the BPL of the signal or channel changes, and some QCL indications are needed for each scheduling instance. The QCL indication may be sent in the downlink control information (DCI), which may be part of the PDCCH channel. Because the DCI is needed to control the information, it may be desirable that the number of bits required to indicate the QCL is not too large. The QCL may be sent in a medium access control-control element (MAC-CE) or a radio resource control (RRC) message.

[0093] According to an example, whenever a UE reports that it has received a BS beam with sufficient RSRP, and the BS decides to use that BPL in the future, the BS assigns it a BPL tag. Thus, two BPLs with different BS beams can be associated with different BPL tags. BPLs based on the same BS beam can be associated with the same BPL tag. Thus, according to this example, the tag is a function of the BS beam of the BPL.

[0094] As mentioned above, wireless systems such as millimeter wave (mmW) systems bring gigabit speeds to cellular networks due to the availability of large amounts of bandwidth. However, the unique challenges of severe path loss faced by such wireless systems require new technologies such as hybrid beamforming (analog and digital), which do not exist in 3G and 4G systems. Hybrid beamforming can enhance the link budget / signal-to-noise ratio (SNR) that can be utilized during RACH.

[0095] In such a system, a Node B (NB) and a User Equipment (UE) can communicate via active beamformed transmit beams. An active beam can be considered as a paired transmit (Tx) and receive (Rx) beam between the NB and the UE, which carries data and control channels such as PDSCH, PDCCH, PUSCH, and PUCCH. As described above, the transmit beam used by the NB and the corresponding receive beam used by the UE for downlink transmission can be referred to as a beam pair link (BPL). Similarly, the transmit beam used by the UE and the corresponding receive beam used by the NB for uplink transmission can also be referred to as a BPL.

[0096] In order for beamforming to operate correctly, the NB may need to monitor the beams using beam measurements performed (e.g., based on reference signals sent by the NB) and feedback generated at the UE. For example, the NB may monitor the active beams using signal measurements performed by the UE, such as NR-SS, CSI-RS, DMRS-CSS, and DMRS-USS. To do this, the NB may send a measurement request to the UE and may subsequently send one or more reference signals for measurement at the UE.

[0097] Since the direction of the reference signal is unknown to the UE, the UE may need to evaluate several beams to obtain the best Rx beam for a given NB Tx beam. However, if the UE has to "sweep" all of its Rx beams to perform measurements (e.g., to determine the best Rx beam for a given NB Tx beam), the UE may incur significant delays and battery life impacts for the measurements. In addition, having to scan through all Rx beams is very resource inefficient. Therefore, aspects of the present disclosure provide techniques for assisting UEs when performing measurements of serving cells and neighboring cells using Rx beamforming.

[0098] like Figure 8As shown, in a multi-beam system, a radio link failure (RLF) process based on radio link monitoring (RLM) measurements can be enhanced by aperiodic synchronization (IS) and out-of-sync (OSS) triggers. The IS and OSS triggers can be initiated by a beam failure recovery (BFR) process. For RLM, at least periodic IS and OOS indications can be based on a metric similar to signal to interference and noise (SINR). Such metrics may include, for example, an assumed PDCCH block error rate (BLER) as in LTE. For the BFR process, at least aperiodic (multiple) indications can be provided to assist the radio link failure (RLF) process. For example, if the same RS is used for beam failure recovery and RLM processes, such aperiodic indications can be provided.

[0099] In some cases, there may be differences between the cell quality metric used by the RLF process and the beam quality metric used by the BFR process. In some cases, these differences may lead to inefficient RLF performance.

[0100] An example of this inefficiency can be seen in Fig. 9 To explain. Fig. 9 An example RLF timer and a trigger for starting the RLF timer are illustrated. As shown, after a threshold number of consecutive OOS indications (referred to as N310) for a primary cell (Pcell), a timer (referred to as T310 timer) may be activated. After the T310 timer expires (e.g., there are no multiple detected IS events), RLF may be declared.

[0101] This may result in unnecessary declarations of RLF. These unnecessary declarations may especially occur in the case of "low SS block geometry", where the UE is unreachable for RLM by the beam carrying the RS, but is reachable by the narrower beam carrying the SS.

[0102] As another example of inefficiency, in some cases, RLF may be delayed unnecessarily. Fig.10 As shown, the RLF timer may be stopped upon receiving a threshold number (N311) of consecutive IS indications for the Pcell. Unfortunately, this may delay the declaration of RLF in the event that beam failure detection actually occurs and there are no candidate beams to recover.

[0103] Example data inactivity indication and accelerated recovery actions

[0104] In some cases, data activity (e.g., transmission / reception) may be blocked (e.g., gated or stalled) at a user equipment (e.g., UE 120a) in both the uplink (UL) and downlink (DL) for various reasons. Such gating may be due to various protocol-specific or non-protocol-specific reasons.

[0105] Non-protocol specific reasons may occur even when the UE is in suitable radio conditions in the current cell and all physical (PHY) layer characteristics are in good conditions with the network (NW). For example, under such conditions, PDCCH transmissions are usually always successfully decoded, and power control and channel state information (CSI) indications are all suitable. In such cases, the current cell may be suitable, where the UE experiences good reference signal strength indicator (RSSI) or reference signal received power (RSRP) to continue in the current cell.

[0106] However, in some cases, when the UE has some UL data from an application that is internal to the modem or generated (e.g., data from an internal modem or generated by an application), non-protocol-specific reasons may cause a stall in UL data transmission from the UE. For example, the UE may report scheduling request (SR) and buffer status report (BSR) information to the NW (e.g., indicating uplink data to be sent), but the NW may not allocate a grant on the physical uplink shared channel (PUSCH) as expected, which would allow the UL data to be sent to the gNB / eNB (e.g., BS 110). In other cases, the NW may grant some resources to the UE for UL transmission, but only grant enough resources for the UE to send the BSR. In other words, in such cases, the amount of resources granted may be just enough to handle the sending of the BSR, but may not be enough to allow the UE to send the UL data for which the BSR is sent.

[0107] When the UE expects some DL data specific to the radio level or application level from the gNB, non-protocol specific reasons may cause the stall of DL data transmission to the UE. In such cases, the UE may successfully decode the Physical Downlink Control Channel (PDCCH) and the expected scheduling for DL ​​data is not included in the PDCCH or PDSCH in the DL when the UE is in good radio conditions.

[0108] Due to non-protocol specific reasons, in the absence of any obvious bad radio activity, such UL / DL data stagnation in the UE / NW may lead to increased transmission / reception latency and poor user experience at the application / end user of the UE. In some cases, such transmission / reception latency may be particularly detrimental in certain wireless communication systems including non-terrestrial network entities such as the wireless communication network 1200, which are prone to problems with round trip delay (RTD) and frequency offset.

[0109] Protocol specific reasons may also cause stalling when the UE is experiencing suitable radio conditions and all PHY layer characteristics are in a suitable shape with NW, which again means that PDCCH decoding is good and power control and CSI indications are good. In such cases, the current cell is suitable, where the UE experiences good RSSI or RSRP to continue in the current cell.

[0110] When the UE has some UL data from the modem internal or generated by the application (e.g., from the internal modem or generated by the application), protocol specific reasons may cause the UL data transmission from the UE to be stalled. For example, the UE may try to initiate an SR procedure, which may fail, causing the UE to fall back to a random access channel (RACH) procedure, which may fail, causing the UE to fall back to a lengthy cell reselection procedure.

[0111] Protocol specific reasons may include the UE and NW losing synchronization (sync) during an ongoing call, for example, with respect to radio level configuration. In some cases, the UE and NW may be out of sync with respect to a connected discontinuous reception (C-DRX) procedure. For example, in some cases, the UE may be in CDRX OFF mode while the NW is in (and / or assumes that the UE is in) CDRX ON mode.

[0112] In some cases, the UE and NW may be out of sync with respect to the active bandwidth part (BWP). For example, the UE may be in a configured BWP X, while the NW assumes that the UE is in a default BWP Y (or vice versa).

[0113] Various other radio procedures may also cause the UE to be out of sync. Examples of such procedures may include ciphering parameters or integrity parameters or MAC CE procedures that enable / disable different features or CC / duplicate / activate / deactivate different access level barring assumptions.

[0114] These various reasons may result in considerable transmit / receive delays. For example, a maximum number of SR retransmissions may need to occur before a RACH procedure is attempted, which may result in considerable delay (e.g., 64×128 ms). Thereafter, a maximum number of RACH preambles may need to be attempted (with a backoff time) before a radio link failure (RLF) is declared, before a radio resource control (RRC) IDLE, RRC connection failure, and / or RRC connection reestablishment procedure is ultimately performed.

[0115] The RACH procedure is well defined, with back-off timers and the number of RACH attempts governed by the RRC and MAC specifications, which can lead to substantial delays in some configurations, especially when the UE is part of a Contention-Free Random Access (CFRA) with limited radio resources. In some cases, up to 200 preambles and back-off timers can be utilized to attempt the RACH procedure in the worst case, which can result in barely tens of ms before the UE declares RLF and enters a new RRC connection via the RRC_IDLE procedure or re-establishment.

[0116] Regardless of whether the UE is not experiencing transmission due to genuine protocol reasons (e.g., SR→RACH→RRC_IDLE→connection establishment, unsynchronized features / protocol states between NW and UE) or due to NW scheduling reasons (e.g., no UL grant or no DL scheduling or Quality of Service (QoS) issues or service level agreement or NW side database issues), the application being used by the user of the UE will not have active data transmission, resulting in a poor user experience.

[0117] Therefore, aspects of the present disclosure provide techniques that can help quickly detect such stalls and perform recovery actions, whether the stall is detected at the modem or application processor level. As will be described herein, the techniques can enable a UE to detect data inactivity and accelerate recovery actions to quickly establish another connection on the same or different cell.

[0118] Fig.11 Example operations 1100 that may be performed by a UE to detect data inactivity and accelerate recovery actions are illustrated. Operations 1100 may be performed, for example, by a UE participating in a communication with a wireless communication network such as Figure 1 The wireless communication network 100 and / or Fig.12 The communication may be performed by a user equipment (e.g., UE 120a) communicating with a base station (e.g., a gNB such as BS 110) within a wireless communication network 1200.

[0119] Operations 1100 begin at 1102 by detecting when uplink or downlink data transmission between a UE and a network has stalled by maintaining at least one inactivity timer.

[0120] At 1104, if the inactivity expires due to one or more conditions, the UE accelerates one or more recovery actions.

[0121] In some cases, the UE may maintain an uplink inactivity timer (T_ul_inactivity) and / or a downlink inactivity timer (T_dl_inactivity), which may be different from Fig. 9 and Fig.10 The T310 timer shown in .

[0122] In some cases, when new data arrives at the UE's modem layer (L2) from the modem, application processor, or any application in the tethered client, the UE may start a timer T_ul_inactivity.

[0123] In some cases, the T_dl_inactivity timer may be started if / when DL data is expected, e.g. in the modem or in the UE's application processor based on corresponding protocol knowledge. In some cases, this timer may be bound to layer 2 at the modem level, expecting feedback from peer layer 2, or this timer may be bound to the application (TCP / HTTP) at the application processor level, expecting feedback from the peer application (TCP / HTTP).

[0124] In some cases, if no data is sent from the UE's modem level within the time period defined by the T_ul_inactivity timer (e.g., before expiration), the UE can determine the reason behind no data being sent and look into further actions based on that reason. If some UL data is sent during the T_ul_inactivity time period, the timer can be stopped or restarted.

[0125] Similarly, for DL ​​traffic, when T_dl_inactivity starts, and when no data is received within the time period defined by the T_dl_inactivity timer (e.g., before expiration), the UE can determine the reason behind not receiving the data and look into further actions based on the reason. If some DL data is received within the T_dl_inactivity time period, the timer can be stopped or restarted.

[0126] In some cases, if the inactivity timer (eg, T_ul_inactivity or T_dl_inactivity) expires, the UE may take action to speed up the recovery process.

[0127] For example, if the T_ul_inactivity timer expires, the UE may immediately declare RLF and may accelerate the RRC_IDLE or RRC connection procedure. In some cases, for example, if the reason for the T_ul_inactivity timer to expire is one of the following, the UE may accelerate the RRC_IDLE or RRC connection procedure:

[0128] (1) Ongoing SR / RACH process;

[0129] (2) lack of data transmission in UL or lack of data acknowledgment in DL (L2 state, if required); or

[0130] (3) There is a mismatch in the configuration between the NW and the UE (e.g., a mismatch in C-DRX state, a mismatch in BWP configuration, a mismatch in ciphering or integrity parameters, a mismatch in MAC CE procedures, or a mismatch in access class restriction assumptions).

[0131] Similarly, if T_dl_inactivity expires, the UE may immediately declare RLF and accelerate the execution of the RRC_IDLE or RRC connection procedure. In some cases, for example, if the reason for the expiration of the T_dl_inactivity timer is one of the following, the UE may accelerate the RRC_IDLE or RRC connection procedure:

[0132] (4) DL status for UL data not received at Layer 2;

[0133] (5) No DL traffic (e.g., Transmission Control Protocol (TCP) acknowledgment (ACK) or TCP response or App response) is received within the period defined by the T_dl_inactivity timer; or

[0134] (6) There is a mismatch in configuration between the NW and the UE (eg, as described above).

[0135] According to various aspects, early inactivity detection and accelerated recovery actions in this manner may help avoid delays in performing RLF / connection reestablishment procedures to establish a new connection for active data transmission / reception, thereby reducing transmission / reception latency at the UE.

[0136] In some cases, the values ​​of the T_ul_inactivity timer and the T_dl_inactivity timer may be appropriately selected, for example, based on the modem / application processor, data type, application requirements (e.g., latency, QOS, service level agreement), modem technology, wireless environment (e.g., channel conditions), etc. For example, an aggressive value for one of these timers may result in waste of radio signaling procedures, but may be justified based on customer requirements for response time and user perceived experience.

[0137] In some cases, the timer value can also be adaptive based on data type, data volume and / or service type. For example, for ultra-reliable low-latency communication (URLLC) service type data, the timer value may be much shorter than other types of service types.

[0138] In addition to the recovery action in the modem, this information (e.g., information about the inactivity timer or the one or more recovery actions) may be indicated to the client (modem / AP / tethered client) or application for appropriate recovery actions at the application level (e.g., retry, switch to a different radio access technology (RAT), different actions based on characteristics) or for informational purposes. In some cases, appropriate recovery actions may include closing and opening a Transmission Control Protocol (TCP) session at the application level, triggering a multipath TCP (MPTCP) type of session, or restarting the connection at the application level. Additionally, in some cases, there may be additional in-band signaling at the application layer for recovery, such as dynamically adjusting the transcoding rate or bandwidth.

[0139] Example Non-Terrestrial Network

[0140] Fig.12 An example of a wireless communication network 1200 including a non-terrestrial network entity 1240 in which aspects of the present disclosure may be practiced is illustrated. In some examples, the wireless communication network 1200 may implement aspects of the wireless communication network 100. For example, the wireless communication network 1200 may include a BS 110a, a UE 120a, and a non-terrestrial network entity 1240 such as a satellite. In the case of a terrestrial network, the BS 110a may serve a coverage area or cell 102a, and in the case of a non-terrestrial network (NTN), the non-terrestrial network entity 1240 may serve the coverage area 102a. Some NTNs may employ airborne platforms (e.g., drones or balloons) and / or spaceborne platforms (e.g., satellites).

[0141] The non-terrestrial network entity 1240 may communicate with the BS 110a and the UE 120a as part of wireless communications in the NTN. In the case of a terrestrial network, the UE 120a may communicate with the BS 110a via a communication link. In the case of NTN wireless communications, the non-terrestrial network entity 1240 may be a serving cell of the UE 120a via the communication link 1220. In certain aspects, the non-terrestrial network entity 1240 may act as a relay for the BS 110a and the UE 120a, thereby relaying data transmission and control signaling notifications 1215.

[0142] The non-terrestrial network entity 1240 may orbit the surface of the earth at a certain altitude. The distance between the non-terrestrial network entity 1240 and the UE 120a may be much greater than the distance between the BS 110a and the UE 120a. The distance between the UE 120a and the non-terrestrial network entity 1240 may cause an increase in the round trip delay (RTD) in the communication on the communication link 1220 between the UE 120a and the non-terrestrial network entity 1240. The movement of the non-terrestrial network entity 1240 may cause a Doppler effect and contribute to a frequency shift in the communication between the UE 120a and the non-terrestrial network entity 1240. The frequency shift may also be caused by an error related to the local oscillation of the UE 120a or the non-terrestrial network entity 1240. The RTD and frequency shift associated with the communication in the NTN may cause inefficiency in transmission, delay, and inability to accurately send and receive messages.

[0143] The UE 120a may determine to connect to the non-terrestrial network entity 1240 using a random access (RA) procedure (e.g., a four-step RA procedure or a two-step RA procedure). The initiation of the RA procedure may begin with the UE 120a sending a RA preamble (e.g., an NR preamble for RA) to the non-terrestrial network entity 1240 or the BS 110a. The UE 120a may send the RA preamble on a physical random access channel (PRACH). In some PRACH designs, there may be no estimation or consideration of RTD or frequency shift associated with NTN. In some networks, such as terrestrial NR networks (e.g., 5G NR), the SSBs sent by the cells are sent on the same frequency interval (e.g., occupy the same frequency interval). In the NTN, the satellite may use multiple antennas to form multiple narrow beams, and the beams may operate on different frequency intervals to mitigate interference between the beams.

[0144] Example Wireless Communication Device

[0145] Fig.13 A communication device 1300 is illustrated, which may include devices configured to perform operations for the techniques disclosed herein (such as, Fig.11Various components (e.g., corresponding to part-plus-function components) of the operations illustrated in FIG.

[0146] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or a receiver). The transceiver 1308 is configured to transmit and receive signals for the communication device 1300, such as the various signals described herein, via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and / or transmitted by the communication device 1300.

[0147] The processing system 1302 includes a processor 1304 coupled to a computer readable medium / memory 1312 via a bus 1306. In some aspects, the computer readable medium / memory 1312 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 1304, cause the processor 1304 to perform Fig.11 , or other operations for performing the various techniques discussed herein for detecting data inactivity and accelerating recovery actions. In some cases, processor 1304 may include reference to Figure 4 One or more components of the UE 130a, such as the controller / processor 480, the transmit processor 464, the receive processor 458, etc. In addition, in some cases, the computer-readable medium / memory 1312 may include reference Figure 4 One or more components of UE 120a, such as memory 482, etc.

[0148] In certain aspects, the computer readable medium / memory 1312 stores code for maintaining 1314, code for accelerating 1316, code for selecting 1318, code for adjusting 1320, and code for indicating 1322.

[0149] In some cases, code for selecting 1314 may include code for maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and the network has stalled.

[0150] In some cases, code for accelerating 1316 may include code for accelerating one or more recovery actions if inactivity expires due to one or more conditions.

[0151] In some cases, code for accelerating 1316 may include code for declaring a radio link failure (RLF) and accelerating the connection process if an uplink inactivity timer expires due to one or more specific reasons.

[0152] In some cases, code for selecting 1318 may include code for selecting a value for at least one inactivity timer based on one or more considerations.

[0153] In some cases, code for adjusting 1320 may include code for adjusting a value of an inactivity timer based on at least one of a data type or an amount of data.

[0154] In some cases, code for indicating 1322 may include code for indicating to the client or application information regarding at least one of: an inactivity timer or one or more recovery actions.

[0155] In some aspects, the processor 1304 has circuitry configured to implement code stored in the computer-readable medium / memory 1312. For example, the processor 1304 includes circuitry for maintaining 1324, circuitry for accelerating 1326, circuitry for selecting 1328, circuitry for adjusting 1330, and circuitry for indicating 1332.

[0156] In some cases, the circuitry for selecting 1324 may include circuitry for maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and the network has stalled.

[0157] In some cases, circuitry for accelerating 1326 may include circuitry for accelerating one or more recovery actions if inactivity expires due to one or more conditions.

[0158] In some cases, the circuitry for accelerating 1326 may include circuitry for declaring a radio link failure (RLF) and accelerating the connection process if the uplink inactivity timer expires due to one or more specific reasons.

[0159] In some cases, circuitry for selecting 1328 may include circuitry for selecting a value for at least one inactivity timer based on one or more considerations.

[0160] In some cases, circuitry for adjusting 1330 may include circuitry for adjusting the value of the inactivity timer based on at least one of a data type or an amount of data.

[0161] In some cases, circuitry for indicating 1332 may include circuitry for indicating to a client or application information regarding at least one of: an inactivity timer or one or more recovery actions.

[0162] In some cases, Fig.11The operations shown in and other operations described herein for detecting data inactivity and accelerating recovery actions can be implemented by one or more components plus functional components. For example, in some cases, such operations can be implemented by components for maintaining, components for accelerating, components for selecting, components for adjusting, and components for indicating.

[0163] In some cases, the means for maintaining, the means for accelerating, the means for selecting, the means for adjusting, and the means for indicating include a processing system, which may include one or more processors, such as, Figure 4 The receive processor 458, transmit processor 464, TX MIMO processor 466 and / or controller / processor 480 of the UE 120a shown in FIG. Fig.13 The processing system 1302 of the communication device 1300 in FIG.

[0164] Sample Clauses

[0165] Examples of implementations are described in the following numbered clauses:

[0166] Clause 1: A method for wireless communications by a user equipment (UE), the method comprising: maintaining at least one inactivity timer to detect when uplink or downlink data transmission between the UE and a network has stalled, and if the inactivity expires due to one or more conditions, accelerating one or more recovery actions.

[0167] Clause 2: The method of clause 1, wherein the at least one inactivity timer comprises an uplink inactivity timer that is started when uplink data arrives in the modem layer or the application processor.

[0168] Clause 3: A method according to clause 2, wherein if uplink data is sent, the uplink inactivity timer is stopped or restarted.

[0169] Clause 4: A method as set forth in any of clauses 1-3, wherein the at least one inactivity timer comprises a downlink inactivity timer which is started if downlink data is expected in at least one of the modem layer or the application processor.

[0170] Clause 5: The method of clause 4, wherein if downlink data is received, the downlink inactivity timer is stopped or restarted.

[0171] Clause 6: A method according to any one of clauses 1 to 5, wherein accelerating one or more recovery actions comprises declaring a radio link failure (RLF) and accelerating the connection process if the uplink inactivity timer expires due to one or more specific reasons.

[0172] Clause 7: A method according to clause 6, wherein the one or more specific causes comprise at least one mismatch in configuration between the UE and the network.

[0173] Clause 8: A method according to clause 7, wherein at least one mismatch in the configuration includes: a mismatch in a connected discontinuous reception (C-DRX) state; a mismatch in a bandwidth part (BWP) configuration; a mismatch in encryption or integrity parameters; a mismatch in a medium access control (MAC) control element (CE) process; or a mismatch in access level restriction assumptions.

[0174] Clause 9: A method according to any one of clauses 6 to 8, wherein the one or more specific causes include at least one of: an ongoing scheduling request (SR); an ongoing random access channel (RACH) procedure; a lack of uplink data transmission or a lack of downlink data confirmation; or a mismatch in configuration between the UE and the network.

[0175] Clause 10: A method according to any one of clauses 6 to 9, wherein the one or more specific causes include at least one of: downlink status not being received; or expected downlink traffic feedback not being received.

[0176] Clause 11: The method of clause 10, wherein the expected downlink traffic feedback comprises at least one of: a transmission control protocol (TCP) acknowledgment, a TCP response, or an application response.

[0177] Clause 12: A method according to any of clauses 1-11, further comprising selecting a value of at least one inactivity timer based on one or more considerations.

[0178] Clause 13: The method of clause 12, wherein the one or more considerations relate to at least one of: modem capabilities, application processor capabilities, data type, application requirements, radio access technology (RAT), or channel conditions.

[0179] Clause 14: The method of clause 13, wherein the application requirement is related to at least one of latency, quality of service (QOS), or a service level agreement.

[0180] Clause 15: The method of any of clauses 12 to 13, further comprising adjusting a value of the inactivity timer based on at least one of a data type or an amount of data.

[0181] Clause 16: A method as set forth in any of clauses 1 to 15, further comprising indicating to the client or application information regarding at least one of: an inactivity timer or one or more recovery actions.

[0182] Clause 17: A processing system for wireless communications, the processing system comprising: a memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the processing system to perform a method according to any one of clauses 1 to 16.

[0183] Clause 18: An apparatus for wireless communication, the apparatus comprising means for performing the method according to any of clauses 1-16.

[0184] Clause 19: A non-transitory computer-readable medium for wireless communications, the non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform a method according to any one of clauses 1 to 16.

[0185] Clause 20: A computer program product for wireless communications, the computer program product being embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any of clauses 1-16.

[0186] Additional considerations

[0187] The method disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, the method steps and / or actions can be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0188] As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccC, or any other arrangement of a, b, and c).

[0189] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determining" may include resolving, selecting, choosing, establishing, etc.

[0190] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the present claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein, unless otherwise specified, the singular reference to an element is not intended to mean "one and only one", but to mean "one or more". Unless otherwise specifically specified, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure known or to be known in the future by a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. In addition, nothing disclosed herein is intended to be contributed to the public, whether or not such disclosure is explicitly stated in the claims. Any claim element shall not be interpreted according to the provisions of Section 112, Section 6, Title 35, United States Code, unless the element is explicitly stated using the phrase "a component for...", or in the case of a method claim, the element is stated using the phrase "a step for...".

[0191] The various operations of the above method can be performed by any suitable component capable of performing the corresponding function. The component may include various hardware and / or software (multiple) components and / or (multiple) modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, where there are operations shown in the figure, these operations may have corresponding paired components plus functional components with similar numbers.

[0192] The various illustrative logic blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but as an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0193] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific use of the processing system and the overall design constraints, the bus may include any number of interconnecting buses and bridges. The bus may link various circuits together, including a processor, a machine-readable medium, and a bus interface. Among other things, the bus interface may be used to connect a network adapter to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal 120 (see Figure 1 ), a user interface (e.g., keyboard, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and will not be described further. The processor may be implemented using one or more general purpose and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how to best implement the described functions of the processing system depending on the specific application and the overall design constraints imposed on the entire system.

[0194] If implemented in software, the functions may be stored on or transmitted through a computer-readable medium as one or more instructions or codes. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as representing instructions, data, or any combination thereof. Computer-readable media include both computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, a storage medium may be integrated into the processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium on which instructions separated from a wireless node are stored, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file. As an example, examples of machine-readable storage media may include random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, magnetic disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. Machine-readable media may be included in a computer program product.

[0195] A software module may include a single instruction or multiple instructions, and may be distributed over several different code segments, distributed in different programs, and distributed over multiple storage media. A computer-readable medium may include several software modules. A software module includes instructions, which, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device, or may be distributed over multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functions of a software module below, it should be understood that these functions are implemented by the processor when executing instructions from the software module.

[0196] In addition, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave) is used to send software from a website, server, or other remote source, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disks and optical disks used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks usually reproduce data magnetically, and optical disks reproduce data optically with lasers. Therefore, in some aspects, computer-readable media may include non-temporary computer-readable media (e.g., tangible media). In addition, for other aspects, computer-readable media may include temporary computer-readable media (e.g., signals). The above combination should also be included in the scope of computer-readable media.

[0197] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that may be executed by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and in the accompanying drawings.

[0198] In addition, it should be understood that, if applicable, the modules and / or other suitable components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station. For example, such a device can be coupled to a server so that the transfer component is used to perform the methods described herein. Alternatively, the various methods described herein can be provided via a storage component (e.g., RAM, ROM, a physical storage medium such as a compact disk (CD) or a floppy disk, etc.), so that the user terminal and / or base station can obtain the various methods when the storage component is coupled or provided to the device. In addition, any other suitable technology for providing the methods and techniques described herein to the device can be utilized.

[0199] It is to be understood that the present claims are not limited to the precise configuration and components described above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment UE, comprising: selecting a value of at least one inactivity timer for detecting when uplink or downlink data transmission between the UE and a network entity has stalled, wherein the value of the at least one inactivity timer is selected based on a modem capability, an application processor capability, a data type, an application requirement, a radio access technology (RAT), or a combination thereof, of the UE; maintaining the at least one inactivity timer to detect when the uplink or downlink data transmission has stalled; and If the at least one inactivity timer expires due to one or more reasons, one or more recovery actions are accelerated, wherein the accelerating one or more recovery actions includes declaring a radio link failure (RLF).

2. The method according to claim 1, wherein: The at least one inactivity timer includes an uplink inactivity timer that is started when uplink data arrives in a modem layer or an application processor.

3. The method according to claim 2, wherein: If the uplink data is sent, the uplink inactivity timer is stopped or restarted.

4. The method according to claim 1, wherein: The at least one inactivity timer includes a downlink inactivity timer that is started if downlink data is expected in at least one of the modem layer or the application processor.

5. The method according to claim 4, wherein: If downlink data is received, the downlink inactivity timer is stopped or restarted.

6. The method according to claim 1, wherein: The accelerating one or more recovery actions further comprises accelerating a connection process if the uplink inactivity timer expires due to one or more specific reasons.

7. The method according to claim 6, wherein: The one or more causes include at least one mismatch in configuration between the UE and the network entity.

8. The method according to claim 7, wherein: At least one mismatch in the configuration comprises: Mismatch in connected discontinuous reception C-DRX state; Mismatch in bandwidth part BWP configuration; mismatch in encryption or integrity parameters; Mismatch in the Medium Access Control (MAC) Control Element (CE) procedure; or Mismatch in access class restriction assumptions.

9. The method according to claim 6, wherein: The one or more reasons include at least one of the following: Ongoing scheduling request SR; Ongoing random access channel RACH procedure; Lack of uplink data transmission or lack of downlink data acknowledgment; or A mismatch in configuration between the UE and the network entity.

10. The method according to claim 6, wherein: The one or more reasons include at least one of the following: Downlink status is not received; or Expected downlink traffic feedback was not received.

11. The method according to claim 10, wherein: The expected downlink traffic feedback includes at least one of the following: a Transmission Control Protocol TCP acknowledgement, a TCP response, or an application response.

12. The method according to claim 1, wherein: The application requirement is related to at least one of latency, quality of service (QOS), or service level agreement.

13. The method of claim 1, further comprising adjusting a value of the at least one inactivity timer based on at least one of a data type or an amount of data.

14. The method of claim 1, further comprising indicating to a client or application information regarding at least one of: the at least one inactivity timer; or The one or more recovery actions.

15. A processing system for wireless communication, comprising: a memory including computer executable instructions; as well as one or more processors configured to execute the computer executable instructions and cause the processing system to: selecting a value of at least one inactivity timer for detecting when uplink or downlink data transmission between a user equipment (UE) and a network entity has stalled, wherein the value of the at least one inactivity timer is selected based on a modem capability, an application processor capability, a data type, an application requirement, a radio access technology (RAT), or a combination thereof of the UE; maintaining the at least one inactivity timer to detect when the uplink or downlink data transmission has stalled; and If the at least one inactivity timer expires due to one or more reasons, one or more recovery actions are accelerated, wherein accelerating the one or more recovery actions includes declaring a radio link failure (RLF).

16. The processing system of claim 15, wherein: The at least one inactivity timer includes an uplink inactivity timer that is started when uplink data arrives in a modem layer or an application processor.

17. The processing system of claim 16, wherein: If the uplink data is sent, the uplink inactivity timer is stopped or restarted.

18. The processing system of claim 15, wherein: The at least one inactivity timer includes a downlink inactivity timer that is started if downlink data is expected in at least one of the modem layer or the application processor.

19. The processing system of claim 18, wherein: If downlink data is received, the downlink inactivity timer is stopped or restarted.

20. The processing system of claim 15, wherein: To speed up the one or more recovery actions, the one or more processors are further configured to cause the processing system to speed up a connection process if the uplink inactivity timer expires due to the one or more reasons.

21. The processing system of claim 20, wherein: The one or more causes include at least one mismatch in configuration between the UE and the network entity.

22. The processing system of claim 21, wherein: At least one mismatch in the configuration comprises: Mismatch in connected discontinuous reception C-DRX state; Mismatch in bandwidth part BWP configuration; mismatch in encryption or integrity parameters; Mismatch in the Medium Access Control (MAC) Control Element (CE) procedure; or Mismatch in access class restriction assumptions.

23. The processing system of claim 20, wherein: The one or more reasons include at least one of the following: Ongoing scheduling request SR; Ongoing random access channel RACH procedure; Lack of uplink data transmission or lack of downlink data acknowledgment; a mismatch in configuration between the UE and the network entity; Downlink status is not received; or Expected downlink traffic feedback is not received, wherein the expected downlink traffic feedback includes at least one of the following: a Transmission Control Protocol TCP acknowledgement, a TCP response, or an application response.

24. The processing system of claim 15, wherein: The application requirement is related to at least one of latency, quality of service (QOS), or service level agreement.

25. The processing system of claim 24, wherein: The one or more processors are configured to cause the processing system to adjust the value of the at least one inactivity timer based on at least one of a type of data or an amount of data.

26. The processing system of claim 15, wherein: The one or more processors are configured to cause the processing system to indicate to a client or application information regarding at least one of: the at least one inactivity timer; or The one or more recovery actions.

27. An apparatus for wireless communication by a user equipment UE, comprising: means for selecting a value of at least one inactivity timer for detecting when uplink or downlink data transmission between the UE and a network entity has stalled, wherein the value of the at least one inactivity timer is selected based on modem capabilities, application processor capabilities, data type, application requirements, radio access technology (RAT), or a combination thereof of the UE; means for maintaining said at least one inactivity timer to detect when said uplink or downlink data transmission has stalled; and Means for accelerating one or more recovery actions if the at least one inactivity timer expires due to one or more reasons, wherein the accelerating one or more recovery actions comprises declaring a radio link failure (RLF).

28. A non-transitory computer-readable medium for wireless communication by a user equipment (UE), comprising: Computer executable instructions, when executed by one or more processors of a processing system, cause the processing system to: selecting a value of at least one inactivity timer for detecting when uplink or downlink data transmission between the UE and a network entity has stalled, wherein the value of the at least one inactivity timer is selected based on a modem capability, an application processor capability, a data type, an application requirement, a radio access technology (RAT), or a combination thereof, of the UE; maintaining the at least one inactivity timer to detect when the uplink or downlink data transmission has stalled; and If the at least one inactivity timer expires due to one or more reasons, one or more recovery actions are accelerated, wherein the accelerating one or more recovery actions includes declaring a radio link failure (RLF).

Images