Techniques for enhancing radio link failure recovery

Abstract

Aspects described herein relate to reporting out-of-sync on a downlink (DL) to a network entity by sending a report to the network entity indicating an out-of-sync status of the DL based on comparing a difference between a downlink timing measurement for a signal and a previous downlink timing measurement for a previous signal to a threshold. In an example, a network entity receiving the report can send a response signal to cause a device reporting out-of-sync to correct DL timing or perform a random access procedure.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 405,489, filed January 5, 2024, entitled “TECHNIQUES FOR ENHANCING RADIOLINK FAILURE RECOVERY”, the entire disclosure of which is expressly incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication systems in general, and more specifically to recovery from radio link failures (RLF) in wireless communication. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems 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, and Single Carrier Frequency Division Multiple Access (SC-FDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. For example, fifth-generation (5G) wireless communication technology (which may be referred to as 5G New Radio (5G NR)) is designed to expand and support a diverse range of use cases and applications compared to current mobile network generations. In one aspect, 5G communication technologies can include: enhanced mobile broadband addressing for human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communication (URLLC) with certain specifications for latency and reliability; and massive machine-type communication that allows the transmission of a very large number of connected devices and a relatively small amount of non-latency-sensitive information. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a broad overview of all anticipated aspects, nor is it intended to identify key or essential elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0007] According to one aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; one or more memories configured to store instructions individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are individually or in combination configured to execute instructions to cause the apparatus to: perform downlink (DL) timing measurements on signals received from a network entity; and send a report to the network entity indicating a loss-of-synchronization state of the DL based on a comparison of the difference between the downlink timing measurement of the signal and a previous downlink timing measurement of a previous signal with a threshold.

[0008] In another aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; one or more memories configured to store instructions individually or in combination; and one or more processors communicatively coupled to the one or more memories. The one or more processors are individually or in combination configured to execute instructions to cause the apparatus to: receive from the UE a report indicating a loss-of-synchronization state of the downlink (DL) based on a difference between a DL timing measurement of a signal transmitted to a user equipment (UE) and a previous downlink timing measurement of a previous signal transmitted to the UE that is at least equal to or greater than a threshold; and to send a response signal to the UE based on the DL loss-of-synchronization state to correct the downlink timing or initiate a random access procedure.

[0009] On the other hand, a method for wireless communication at a UE is provided, the method comprising: performing a downlink timing measurement of a signal received from a network entity; and sending a report indicating a loss-of-synchronization state of the downlink to the network entity based on a comparison of the difference between the downlink timing measurement of the signal and a previous downlink timing measurement of a previous signal with a threshold.

[0010] On the other hand, a method for wireless communication at a network entity is provided, the method comprising: receiving from the UE a report indicating a loss-of-synchronization state of the DL based on a difference between a DL timing measurement of a signal transmitted to the UE and a previous downlink timing measurement of a previous signal transmitted to the UE being at least equal to or greater than a threshold; and sending a response signal to the UE based on the loss-of-synchronization state of the DL to correct the downlink timing or to initiate a random access procedure.

[0011] In another aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions to perform operations of the methods described herein. In another aspect, an apparatus for wireless communication is provided, the apparatus including components for performing operations of the methods described herein. In yet another aspect, a computer-readable medium is provided, the computer-readable medium including code executable by one or more processors to perform operations of the methods described herein.

[0012] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0013] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided for illustration and not limitation of the disclosed aspects, wherein similar names represent similar elements, and in the drawings: Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are illustrated; Figure 2 These are illustrations illustrating examples of decomposed base station architectures according to various aspects of this disclosure; Figure 3 This is a block diagram illustrating examples of user equipment (UE) according to various aspects of this disclosure; Figure 4 This is a block diagram illustrating examples of base stations according to various aspects of this disclosure; Figure 5 This is a flowchart illustrating an example of a method for reporting a loss-of-synchronization state on the downlink (DL) according to the aspects described herein; Figure 6 This is a flowchart illustrating an example of a method for receiving a report of a lost-synchronization state on a DL from a UE, according to various aspects described herein; and Figure 7 This is a block diagram illustrating examples of multiple-input multiple-output (MIMO) communication systems including base stations and UEs according to various aspects of this disclosure. Detailed Implementation

[0014] Various aspects will now be described with reference to the accompanying drawings. In the following description, numerous specific details are described for illustrative purposes and to provide a thorough understanding of one or more aspects. However, it will be apparent that such aspects can be practiced without these specific details.

[0015] The described features generally relate to recovery from radio link failure (RLF) or beam failure detection (BFD) in wireless communications. For example, a device (such as a user equipment (UE) in fifth-generation (5G) New Radio (NR) or other wireless communication technologies) can communicate with network entities or other devices in a wireless communication network. When the device is operating in a connected mode with a network entity or other device, it can detect an RLF or beam failure in the link between the device and the network entity or other device based on one or more parameters or considerations. When the device detects an RLF or beam failure, it can perform a Radio Resource Control (RRC) connection reconstruction procedure to rebuild the link with the network entity or device (or another network entity or device), thereby maintaining the link for wireless communication. For example, in 5G NR, the device can perform an RRC connection reconstruction procedure as part of a random access (RA) procedure performed with a network entity or other device. In 5G NR, one possible cause of an RLF or beam failure is that the downlink (DL) timing of the network entity loses synchronization at the device receiving the signal from the network entity. DL timing offset can be reflected in autonomous uplink (UL) timing adjustments performed by a device (e.g., a UE), which can affect the accuracy of UL timing. If a network entity detects a loss of synchronization on the UL, it can issue a Physical Downlink Control Channel (PDCCH) command and trigger the RA procedure.

[0016] For example, in 5G NR, in one or more scenarios, the RA procedure triggered by RLF may overlap with the RA procedure of a PDCCH command. In one example, the UE may detect that the Radio Link Detection (RLM) measurement has degraded due to DL timing drift, where the RLF criteria have not yet been met. The UE may accordingly advance the timing applied to the UL based on the drifted DL timing, and the network entity may then detect a loss of synchronization with the UE. In this example, the RLM measurement may continue to degrade and meet the RLF criteria, and the UE may accordingly suspend PDCCH monitoring and initiate RRC reconstruction. The network entity may then trigger the Random Access Channel (RACH) procedure of the PDCCH command, which the UE did not receive due to the suspension of PDCCH monitoring. In another example, the network may trigger the RACH procedure of the PDCCH command before the UE suspends PDCCH monitoring and initiates RRC reconstruction, but the UE may not receive the PDCCH command due to the degraded radio link. After this, the UE may suspend PDCCH monitoring and initiate RRC reconstruction.

[0017] In these situations, due to the out-of-synchronization state on the DL, neither the UE nor the network entity is aware that two different RA processes are occurring in parallel. This can be undesirable for both parties due to additional power or energy consumption, which may be caused by redundant transmissions and / or retransmissions of the physical RACH (PRACH) by the UE or the PDCCH by the network entity, increased signaling overhead, reduced resource utilization efficiency of RACH resources, and ambiguity in the specific implementation by the UE and / or the network entity (e.g., the UE receiving PDCCH commands within a contention-based RA (CBRA) random access response (RAR) window). The aspects described herein can mitigate the aforementioned problems in wireless communication technologies such as 5G NR and / or improve the efficiency (power or energy, resource utilization, signaling, etc.) of devices recovering from RLF and out-of-synchronization states.

[0018] In one example, the UE can detect a loss of synchronization in the deep learning (DL) process and can report this loss of synchronization to a network entity (e.g., before an RLF). The network entity can receive the loss of synchronization report and can accordingly attempt to correct the DL timing by scheduling RS signals, providing advance indication for monitoring PDCCH triggering a RA procedure, triggering the RA procedure for the PDCCH command, etc. In these examples, the UE can correct the DL timing based on RS or can execute the RA procedure for the PDCCH command before the RLF occurs, which can mitigate situations where both RA procedures are triggered (one RA procedure is due to the RLF). This can mitigate or resolve the aforementioned problems caused by two RA procedures in other ways, and can correspondingly reduce power or energy consumption, reduce signaling overhead, and improve the resource utilization of RACH resources, etc.

[0019] The following will refer to Figures 1 to 7 To present the described features in more detail.

[0020] As used in this application, the terms "component," "module," "system," etc., are intended to include computer-related entities such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device itself can be components. One or more components may reside within a process and / or an execution thread, and components may be located in one computer and / or distributed among two or more computers. Furthermore, these components are executable from various computer-readable media on which various data structures are stored. Components can communicate via local and / or remote processes, such as based on signals having one or more data packets (e.g., data from a component that interacts with a local system, another component in a distributed system, and / or interacts with other systems across a network such as the Internet).

[0021] As used herein, a processor configured to perform or be operable to perform a plurality of actions, at least one processor, and / or one or more processors (alone or in combination) are intended to include at least two different processors capable of performing different subsets, overlapping subsets, or non-overlapping subsets of the plurality of actions, or a single processor capable of performing all of the plurality of actions. In a non-limiting example of a plurality of processors capable of performing different combinations of the plurality of actions, the description of a processor configured to perform or be operable to perform actions X, Y, and Z, at least one processor, and / or one or more processors may include at least a first processor configured to perform or be operable to perform a first subset of X, Y, and Z (e.g., performing X) and at least a second processor configured to perform or be operable to perform a second subset of X, Y, and Z (e.g., performing Y and Z). Alternatively, the first, second, and third processors may be configured to perform corresponding actions in actions X, Y, and Z, respectively. It should be understood that any combination of one or more processors may each be configured to perform or be operable to perform any one of the plurality of actions or any combination of the plurality of actions.

[0022] As used herein, a memory, at least one memory, and / or one or more memories (individually or in combination) configured to store or have thereon instructions executable by one or more processors for performing multiple actions are intended to include at least two different memories capable of storing different subsets, overlapping subsets, or non-overlapping subsets of instructions for performing the multiple actions, or a single memory capable of storing instructions for performing all of the multiple actions. In a non-limiting example of one or more memories (alone or in combination) capable of storing different subsets of instructions for performing different actions among the plurality of actions, the description of a memory configured or operable to store or thereon instructions for performing actions X, Y, and Z, at least one memory, and / or one or more memories may include at least a first memory configured or operable to store or thereon instructions for performing a first subset of X, Y, and Z (e.g., instructions for performing X), and at least a second memory configured or operable to store or thereon instructions for performing a second subset of X, Y, and Z (e.g., instructions for performing Y and Z). Alternatively, the first, second, and third memories may be configured to store or thereon a corresponding one of the first subset of instructions for performing X, the second subset of instructions for performing Y, and the third subset of instructions for performing Z. It should be understood that any combination of one or more memories may be configured or operable to store or have thereon any instruction or any combination of instructions executable by one or more processors to perform any of a plurality of actions or any combination of such actions. Furthermore, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute instructions to perform the plurality of actions. For example, in the above non-limiting example of different subsets of instructions for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first and second processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, three processors may access one of three different memories, each storing instructions for performing action X, Y, or Z, and the three processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, a single processor may execute instructions stored in a single memory or distributed across multiple memories to complete the execution of actions X, Y, and Z.

[0023] The technologies described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, single-carrier FDMA, and others. The terms "system" and "network" are often used interchangeably. CDMA systems implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High-Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. ™ UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-A Advanced (LTE-A) are newer versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the Third Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the Third Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the aforementioned systems and radio technologies, as well as in other systems and radio technologies, including cellular (e.g., LTE) communications over shared radio spectrum bands. However, the following description describes LTE / LTE-A systems for illustrative purposes, and the term LTE is used in most of the following description, although these technologies can also be applied beyond LTE / LTE-A applications (e.g., to fifth-generation (5G) New Radio (NR) networks or other next-generation communication systems).

[0024] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described in some examples may be combined in other examples.

[0025] Various aspects or features will be presented according to the system, which may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Combinations of these methods may also be used.

[0026] Figure 1 This is an illustration of an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells may include base stations. Small cells may include femtocells, picocells, and microcells. In this example, base station 102 may also include a gNB 180, as further described herein. In one example, according to aspects described herein, some nodes of the wireless communication system may have a modem 340 for reporting out-of-sync states on the DL and a UE communication component 342. Furthermore, according to aspects described herein, some nodes may have a modem 440 for receiving reports of out-of-sync states on the DL from the UE and a BS communication component 442. Although UE 104 is shown as having modem 340 and UE communication component 342, and base station 102 / gNB 180 is shown as having modem 440 and BS communication component 442, this is an illustrative example, and essentially any node or any type of node may include modem 340 and UE communication component 342 and / or modem 440 and BS communication component 442 for providing the corresponding functionality described herein.

[0027] Base station 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., using the S1 interface). Base station 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) can interface with 5GC 190 via backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) with each other on backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 can be wired or wireless.

[0028] Base station 102 can wirelessly communicate with one or more UEs 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to restricted groups (which may be referred to as a Closed Subscriber Group (CSG)). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may carry one or more carriers. Base station 102 / UE104 may use spectrum allocated per carrier up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) of bandwidth in carrier aggregation for transmissions in the DL and / or UL directions, totaling up to Yx MHz (e.g., corresponding to x component carriers). Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetrical for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0029] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0030] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine the availability of a channel before communication.

[0031] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR, and uses the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network.

[0032] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, can operate in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has extremely high path loss and short range. The mmW base station 180 can be used with the UE 104 in conjunction with beamforming 182 to compensate for extremely high path loss and short range. The base station 102 mentioned herein may include the gNB 180.

[0033] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and BM-SC 170 are connected to the IP Service 176. The IP Service 176 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can act as an entry point for content provider MBMS transmission, authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can allocate MBMS services to base station 102 belonging to a Broadcast-Specific Service Multicast Single Frequency Network (MBSFN) area, and is responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0034] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 may be a control node handling signaling between UE 104 and 5GC 190. Generally, AMF 192 provides QoS streaming and session management. (For example, user Internet Protocol (IP) packets from one or more UEs 104 may be delivered via UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0035] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, transceiver base station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmit-Receive Point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with access to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). IoT UEs may include Machine Type Communication (MTC) / Enhanced MTC (eMTC, also known as Category (CAT)-M or Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In this disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or are based on these technologies. For example, eMTC may include FeMTC (Further eMTC), eFeMTC (Enhanced Further eMTC), mMTC (Massive MTC), etc., and NB-IoT may include eNB-IoT (Enhanced NB-IoT), FeNB-IoT (Further Enhanced NB-IoT), etc. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0036] The deployment of communication systems (such as 5G New Radio (NR) systems) can involve a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS, e.g., BS 102)), or one or more units (or components) performing base station functionality can be implemented in either a converged or decomposed architecture. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as converged base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0037] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0039] In the example, the UE communication component 342 of UE 104 can measure the DL timing of the signal received from base station 102, and when the DL timing has changed by at least a certain amount, the UE communication component 342 can report the DL out-of-synchronization state to base station 102. In the example, the BS communication component 442 of the base station can receive the report from UE 104 and can accordingly configure UE 104 to correct the DL timing, provide UE 104 with an early monitoring opportunity for the control channel, and / or cause the UE to perform an RA procedure to re-establish a connection with base station 102 or another base station, as described herein.

[0040] Figure 2 A diagram illustrating an example of a decomposed base station 200 architecture is shown. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0041] Each unit in the array (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals or transmit signals to one or more other units via wireless transmission media, or both.

[0042] In some aspects, the CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 210 can be implemented to communicate with the DU 230 for network control and signaling, as needed.

[0043] DU 230 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may, at least in part, host one or more of the following, depending on functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP): a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0044] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the implementation of the DU 230 and CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0045] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0046] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0047] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0048] Turn now Figures 3 to 7 The aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, wherein the aspects in dashed lines may be optional. Although the following text... Figure 5 and Figure 6 The operations described herein are presented in a specific order and / or performed as by the example components, but it should be understood that the ordering of these actions and the components performing the actions may vary depending on the specific implementation. Furthermore, it should be understood that the actions, functions, and / or components described below may be performed by a specially programmed processor, a processor executing specially programmed software or a computer-readable medium, or any other combination of hardware and / or software components capable of performing the described actions or functions.

[0049] refer to Figure 3An example of a specific implementation of UE 104 may include various components, some of which have already been described above and are further described herein, including components such as one or more processors 312 and one or more memories 316 and one or more transceivers 302 communicating via one or more buses 344. For example, one or more processors 312 may include a single processor or multiple processors configured to perform one or more functions described herein. For example, multiple processors may be configured to perform a specific subset of the set of functions described herein, such that multiple processors can perform the set of functions together. Similarly, for example, one or more memories 316 may include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for performing a specific subset of the set of functions described herein, such that multiple memory devices can store instructions or parameters for the set of functions together. According to the aspects described herein, one or more processors 312, one or more memories 316, and one or more transceivers 302 may operate in conjunction with a modem 340 and / or UE communication component 342 for reporting out-of-sync states on the DL.

[0050] In one aspect, one or more processors 312 may include modem 340 and / or may be part of modem 340 using one or more modem processors. Therefore, various functions associated with UE communication component 342 may be included in modem 340 and / or processor 312, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 312 may include any or any combination of a modem processor, or baseband processor, or digital signal processor, or transmit processor, or receiver processor, or transceiver processor associated with transceiver 302. In other aspects, some features of one or more processors 312 and / or modem 340 associated with UE communication component 342 may be performed by transceiver 302.

[0051] Additionally, the memory / multiple memories 316 may be configured to store data used herein and / or a local version of application 375, or one or more sub-components of UE communication component 342 and / or its sub-components executed by at least one processor 312. The memory / multiple memories 316 may include any type of computer-readable medium that can be used by a computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when UE 104 is operating at least one processor 312 to execute UE communication component 342 and / or one or more sub-components of its sub-components, the memory / multiple memories 316 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes and / or associated data defining UE communication component 342 and / or one or more sub-components of its sub-components.

[0052] Transceiver 302 may include at least one receiver 306 and at least one transmitter 308. Receiver 306 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in memory (e.g., a computer-readable medium). Receiver 306 may be, for example, a radio frequency (RF) receiver. In one aspect, receiver 306 may receive signals transmitted by at least one base station 102. Additionally, receiver 306 may process such received signals and may also obtain measurements of these signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter 308 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code including instructions and stored in memory (e.g., a computer-readable medium). Suitable examples of transmitter 308 may include, but are not limited to, RF transmitters.

[0053] Furthermore, in one aspect, UE 104 may include an RF front-end 388 that can operate communicatively with one or more antennas 365 and transceiver 302 to receive and transmit radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by UE 104. The RF front-end 388 may be connected to one or more antennas 365 and may include one or more low-noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.

[0054] On one hand, the LNA 390 can amplify the received signal at the desired output level. On another hand, each LNA 390 can have a specified minimum gain value and a maximum gain value. On yet another hand, the RF front end 388 can use one or more switches 392 to select a particular LNA 390 and its specified gain value based on the desired gain value for a particular application.

[0055] Furthermore, for example, the RF front-end 388 may use one or more PAs 398 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 398 may have a specified minimum gain value and a maximum gain value. In another aspect, the RF front-end 388 may use one or more switches 392 to select a particular PA 398 and its specified gain value based on the desired gain value for a particular application.

[0056] Additionally, for example, the RF front-end 388 may use one or more filters 396 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 396 may be used to filter the output from a corresponding PA 398 to generate an output signal for transmission. In one aspect, each filter 396 may be connected to a specific LNA 390 and / or PA 398. In one aspect, the RF front-end 388 may use one or more switches 392 to select the transmission path or reception path using a specified filter 396, LNA 390, and / or PA 398 based on a configuration as specified by the transceiver 302 and / or processor 312.

[0057] Therefore, transceiver 302 can be configured to transmit and receive wireless signals via RF front end 388 through one or more antennas 365. In one aspect, the transceiver can be tuned to operate at a specified frequency, enabling UE 104 to communicate with, for example, one or more base stations 102 or with one or more cells associated with one or more base stations 102. In another aspect, for example, modem 340 can configure transceiver 302 to operate at a specified frequency and power level based on UE configuration of UE 104 and communication protocols used by modem 340.

[0058] In one aspect, modem 340 may be a multi-band, multi-mode modem capable of processing digital data and communicating with transceiver 302, enabling the use of transceiver 302 to transmit and receive digital data. In another aspect, modem 340 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In another aspect, modem 340 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 340 may control one or more components of UE 104 (e.g., RF front-end 388, transceiver 302) to transmit and / or receive signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the modem's mode and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with UE 104, such as information provided by the network during cell selection and / or cell reselection.

[0059] In one respect, according to the aspects described herein, the UE communication component 342 may optionally include a timing measurement component 352 for measuring the DL timing of signals received from a base station or other network entity, a synchronization state component 354 for detecting the synchronization state on the DL based on the DL timing, and / or a configuration processing component 356 for processing configurations received from the network entity.

[0060] On one hand, processor 312 may correspond to a combination Figure 7 The UE describes one or more processors in the processor. Similarly, memory / multiple memories 316 may correspond to a combination of Figure 7 The UE describes one or more memories.

[0061] refer to Figure 4An example of a specific implementation of base station 102 (e.g., base station 102 and / or gNB 180, as described above) may include various components, some of which have already been described above, but also include components such as one or more processors 412 and one or more memories 416 communicating via one or more buses 444, and one or more transceivers 402. For example, one or more processors 412 may include a single processor or multiple processors configured to perform one or more functions described herein. For example, multiple processors may be configured to perform a specific subset of the set of functions described herein, such that multiple processors can perform the set of functions together. Similarly, for example, one or more memories 416 may include a single memory device or multiple memory devices configured to store instructions or parameters for performing one or more functions described herein. For example, multiple memory devices may be configured to store instructions or parameters for performing a specific subset of the set of functions described herein, such that multiple memory devices can store instructions or parameters for the set of functions together. According to the aspects described herein, one or more processors 412, one or more memories 416, and one or more transceivers 402 may operate in conjunction with a modem 440 and / or a BS communication component 442 for receiving reports of out-of-sync status on the DL from the UE.

[0062] Transceiver 402, receiver 406, transmitter 408, one or more processors 412, memory / multiple memories 416, application 475, bus 444, RF front end 488, LNA 490, switch 492, filter 496, PA 498 and one or more antennas 465 may be the same as or similar to the corresponding components of UE 104 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0063] In one respect, according to the aspects described herein, the BS communication component 442 may optionally include a synchronization status processing component 452 for processing, for example, a synchronization status report for DL ​​received from the UE, a status response component 454 for responding to the synchronization status report to improve synchronization at the UE, and / or a configuration component 456 for configuring the UE using one or more parameters, which may be used to report synchronization status, improve synchronization, etc.

[0064] On one hand, processor 412 may correspond to a combination Figure 7 The base station described in the text refers to one or more processors among the processors. Similarly, memory / multiple memories 416 may correspond to a combination of... Figure 7 The base station in the text describes one or more memories.

[0065] Figure 5A flowchart illustrating an example of a method 500 for reporting out-of-step states on a DL, according to the aspects described herein. Figure 6 A flowchart illustrating an example of a method 600 for receiving a report of a lost-synchronization state on a DL from a UE, according to various aspects described herein. In the example, UE 104 can use Figure 1 and / or Figure 3 One or more of the components described in the document are used to perform the action. Figure 5 The functionality described in method 500 is illustrated. In the example, nodes that schedule UE104 using communication resources (such as base station 102 or gNB 180, a monolithic base station or gNB, a portion of a split base station or gNB, a UE in sidelink communication, etc.) can use... Figure 1 and / or Figure 4 One or more of the components described are used to perform Figure 6 The functions described in method 600 are shown. For ease of explanation, methods 500 and 600 are described together; however, methods 500 and 600 do not need to be executed together and can actually be executed independently using separate devices.

[0066] In the example, UE 104 can establish an RRC connection with a network entity (such as a base station) and operate in connected mode by monitoring control channels (e.g., PDCCH) from the network entity designed for communication by UE 104. Over time, the radio conditions between UE 104 and the network entity may change (e.g., when UE 104 moves, or when other devices or potential interference objects move), including the timing of communications (e.g., the time difference between one node transmitting communication and another node receiving communication). In 5G NR, UE 104 can autonomously perform UL timing adjustments, which may reflect or be based on the DL timing offset or difference between the timing of DL signals transmitted by the network entity and the timing of signals received at UE 104. In one example, UE 104 may apply timing advance for uplink communications based on the detection of DL timing drift. In the example, UE 104 may detect DL timing drift based on RLM measurements performed by UE 104 on signals received from the network entity.

[0067] In method 500, at block 502, a DL timing measurement of a signal received from a network entity can be performed. In one aspect, a timing measurement component 352 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can perform the DL timing measurement of the signal received from the network entity. In one example, the timing measurement component 352 can perform the DL timing measurement as part of an RLM measurement performed on the signal received from the network entity to detect DL timing drift (e.g., for autonomous UL timing adjustment). For example, the timing measurement component 352 can know when the signal for RLM was transmitted by the network entity (or when it is expected to be received by UE 104 based on an applied previous timing advance), and the timing measurement component 352 can determine the DL timing measurement of the signal accordingly. The DL timing measurement may include the time of signal reception and / or drift calculated based on the expected reception time of the signal. In one example, the timing measurement component 352 can perform multiple measurements of the signal over time and can detect drift or drift difference accordingly based on comparisons (e.g., subtraction) of the measurements.

[0068] In method 500, at block 504, a report indicating a loss of synchronization in the downlink (DL) can be sent to a network entity based on a comparison of the difference between a downlink timing measurement of the signal and a previous downlink timing measurement of the previous signal with a threshold. On one hand, a synchronization state component 354 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can send a report indicating a loss of synchronization in the DL to a network entity based on a comparison of the difference between a downlink timing measurement of the signal and a previous downlink timing measurement of the previous signal with a threshold. For example, the synchronization state component 354 can calculate the difference between the downlink timing measurement and the previous downlink timing measurement to determine the amount of timing change between the two measurement periods. This can indicate a drift in downlink timing over time (e.g., between two measurement periods).

[0069] In one example, if the difference reaches a threshold (e.g., equal to or above a threshold), this can indicate a loss of synchronization on the DL, which could quickly cause the UE 104 to detect / claim an RLF or beam failure. For example, when the UE observes that the DL timing has been off by a certain amount... (It can be a drift) change, and The value is higher than the threshold. In such cases, UE 104 can report the out-of-synchronization state to the network entity. In one example, synchronization state component 354 can also report the out-of-synchronization state of DL to the network entity when the time alignment timer is still running and no RLF or BFD has been declared since the establishment of the RRC connection with the network entity (or otherwise based on this situation).

[0070] In one example, the threshold (e.g., The configuration can be configured by the network entity in the RRC or System Information (SI). For example, in method 600, optionally at block 602, a configuration including one or more parameters for reporting a loss of synchronization state can be sent to the UE. In one aspect, configuration component 456 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can send a configuration including one or more parameters for reporting a loss of synchronization state to the UE (e.g., UE 104). For example, in method 500, optionally at block 506, a configuration including one or more parameters for reporting a loss of synchronization state can be received from the network entity. In one aspect, configuration processing component 356 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can receive a configuration including one or more parameters for reporting a loss of synchronization state of the DL from the network entity, and / or process the configuration including one or more parameters for reporting a loss of synchronization state of the DL. For example, configuration component 456 can send configurations in RRC signaling or SI, and / or configuration processing component 356 can receive configurations in RRC signaling or SI. In one example, the configuration can indicate a threshold (e.g., As described in this article, the configuration may include other parameters.

[0071] In the example, the synchronization state component 354 can send reports in uplink control information (UCI) within resources scheduled by network entities, and in media access control (MAC)-control elements (CE). These reports may include information regarding DL timing offsets (e.g., or The measurement of ) or and Differences between (e.g., or In one example, configuration sent by configuration component 456 (e.g., at block 602) and / or received and processed by configuration processing component 356 (e.g., at block 506) can indicate the report content (e.g., whether to include measurements for DL ​​timing offsets or to include differences). Furthermore, for example, synchronization state component 354 can compress or quantize measurements (e.g., DL timing offset measurements or differences) before mapping to UCI or MAC-CE, which can also be based on configuration received from network entities. For example, in method 500, optionally at block 508, downlink timing measurements or differences can be compressed or quantized. In one aspect, synchronization state component 354 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can compress or quantize downlink timing measurements or differences to achieve values ​​that require fewer bits to be transmitted to network entities.

[0072] In one example, UE 104 may be configured with multiple component carriers (CCs) through which the UE communicates with network entities. UE 104 may perform DL timing tracking on one CC, which may be different from the CC on which the UE transmits UCI or MAC-CE, or different from the DL timing reference of the timing advance group (TAG) to which UE 104 is assigned. In this example, synchronization state component 354 may also include an indicator of the DL CC in the report, indicating that DL timing tracking or measurement is performed on that DL CC. The indicator may include an index of the DL CC in the configuration of the multiple CCs configured for UE 104. This can assist network entities in jointly processing out-of-synchronization reports (if received) from multiple CCs.

[0073] In yet another example, the synchronization status component 354 may include the status (e.g., degraded) of RLM measurements, beam management (BM) measurements, etc., in the report, which may help network entities predict the time window of an RLF or beam failure declared by UE 104.

[0074] In method 600, at block 604, a report indicating a loss-of-synchronization state of the DL can be received from the UE based on a difference between a downlink timing measurement of a signal transmitted to the UE and a previous downlink timing measurement of a previous signal transmitted to the UE being at least equal to or greater than a threshold. On one hand, synchronization state processing component 452 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can receive a report indicating a loss-of-synchronization state of the DL from the UE based on a difference between a downlink timing measurement of a signal transmitted to the UE and a previous downlink timing measurement of a previous signal transmitted to the UE being at least equal to or greater than a threshold. For example, as described, this report can be received from the UE 104 in UCI or MAC-CE, and / or may include measurements of the DL timing offset, the difference between the DL timing offset and a threshold, etc.

[0075] Furthermore, for example, the report may include values ​​such as compressed or quantized values. In this example, in method 600, optionally at block 606, the downlink timing measurement or difference may be decompressed or mapped. In one aspect, the synchronization state processing component 452 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) may decompress or map the downlink timing measurement or the difference between the value indicated in the report to the actual value, which may substantially use a decompression algorithm or a mapping of values ​​known to UE 104 and network entities. In yet another example, the report may include an index of the CC on which DL timing tracking is performed, and the synchronization state processing component 452 may process multiple out-of-synchronization reports from multiple CCs based on the indicated index. In yet another example, the report may include an indication of the status (e.g., degradation) of RLM measurements, BM measurements, etc., which the state response component 454 may use to select a specific response to be transmitted to UE 104 for the out-of-synchronization state. For example, if the status of an RLM or BM measurement indicates an impending RLF or beam failure, the status response component 454 can choose a more severe response, such as triggering a RACH measurement, instead of attempting to correct the DL timing.

[0076] In method 600, at block 608, a response signal can be sent to the UE based on the DL's out-of-sync state to correct downlink timing or induce an RA process. On one hand, a state response component 454 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can send a response signal to the UE (e.g., UE 104) based on the DL's out-of-sync state to correct DL timing or induce an RA process. For example, state response component 454 can send a response signal including a non-periodic burst of response signals that schedule tracking reference signals (e.g., tracking reference signal (TRS), non-cell-defined (NCD) synchronization signal block (SSB), etc.) on the DL. In one example, the UE can (e.g., by applying a timing advance determined based on the reference signal) receive and use this signal to correct DL timing. In another example, in method 600, optionally at block 610, DL timing can be corrected based on a response received from the UE to a DL reference signal scheduled in the response signal. On one hand, the synchronization state processing component 452 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can correct DL timing based on a response received from the UE to a DL reference signal scheduled in a response signal. For example, the response may include a DL timing measurement of the DL reference signal performed by UE 104, and in this example, the synchronization state processing component 452 may use the DL timing measurement to generate a timing advance command and transmit it to UE 104.

[0077] In another example, the state response component 454 may send a response signal that includes scheduling an aperiodic RS (e.g., a probe reference signal, a short preamble or sequence with less overhead than PRACH, etc.) on the uplink. This can be co-scheduled with the DL tracking RS to help network entities retune the timing advance MAC-CE without scheduling RA. In this example, in method 600, optionally at block 612, the out-of-synchronization state can be detected based on the receipt of an aperiodic UL reference signal scheduled by the response signal. On one hand, the synchronization state processing component 452 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can detect whether the out-of-synchronization state has been improved based on the receipt of an aperiodic UL reference signal scheduled by the response signal. For example, the synchronization state processing component 452 can determine that UE 104 no longer reports out-of-synchronization state reports based on adjusting the timing advance MAC-CE.

[0078] In another example, the state response component 454 may send a response signal including an advance indication of a monitoring timing for the PDCCH, wherein the PDCCH candidate at the indicated monitoring timing can be used to trigger an RA procedure for the UE (e.g., a contention-free RA (CFRA) or contention-based RA (CBRA) procedure). In this example, in method 600, optionally at block 614, a downlink control channel may be sent during a monitoring timing scheduled in the advance indication in the response signal. In one aspect, the BS communication component 442 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, etc.) may send a downlink control channel (e.g., PDCCH) during a monitoring timing scheduled in the advance indication in the response signal. For example, the BS communication component 442 may send a trigger for an RA procedure in the PDCCH based on a loss-of-synchronization state reported by UE 104, which may reduce the probability of parallel RA procedures at UE 104 and network entities (as described above). In one example, if UE 104 does not detect the RA procedure of the PDCCH command before the end of the indicated monitoring period, UE 104 may perform a regular RLF recovery procedure and initiate an RA procedure for RRC connection reconstruction (e.g., CFRA or CBRA).

[0079] In another example, the state response component 454 may send a response signal that includes a response signal for the RACH procedure that triggers the PDCCH command (e.g., immediately or otherwise based on the response signal). This can reduce the latency or overhead caused by the RLF declaration procedure at UE 104 by scheduling the RACH procedure before UE 104 can detect or declare an RLF. In yet another example, the state response component 454 may send a response signal that includes any combination of the examples above. Furthermore, in some examples, the state response component 454 may select the response signal based on information received in a loss-of-synchronization report from UE 104, as described above.

[0080] In method 500, optionally at block 510, one or more of the following can be received based on the out-of-synchronization state of the DL: indication of one or more aperiodic bursts of downlink RSs or aperiodic uplink RSs; advance indication of the timing of monitoring of a DL control channel that triggers an RA procedure for UL timing acquisition; or a DL control channel command for the RA procedure. In one aspect, UE communication component 342 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, etc.) can receive one or more of the following based on the out-of-synchronization state of the DL: indication of one or more aperiodic bursts of downlink RSs or aperiodic uplink RSs; advance indication of the timing of monitoring of a DL control channel that triggers an RA procedure for UL timing acquisition; or a DL control channel command for the RA procedure, as described above. For example, UE communication component 342 can receive aperiodic bursts of DL RSs and can measure and / or report the timing of DL RSs. In another example, UE communication component 342 may send a non-periodic UL RS as scheduled by a network entity. In yet another example, UE communication component 342 may receive advance indication of the timing of monitoring the DL control channel, and may monitor and / or receive signals that trigger RA, and accordingly initiate an RA procedure with a network entity or another network entity within the range of UE 104. In one example, if UE 104 does not receive any response signal from a network entity, and the RLM measurement performed by UE 104 continues to degrade, UE 104 may perform a regular RLF when criteria are met, to declare the RLF and / or accordingly perform a UE-initiated RA procedure.

[0081] In one example, the priority for UE reporting out-of-synchronization can be configured and / or indicated by a network entity. For instance, when a report overlaps with other UL transmissions or conflicts with DL transmissions, UE 104 can arbitrate based on the priority indication for out-of-synchronization state reports. In another example, based on the priority indication, UE 104 can apply power boosting or dynamic power sharing to transmit out-of-synchronization state reports, or select a multiplexing scheme with other UL channels (e.g., UCI piggybacking on the Physical Uplink Shared Channel (PUSCH)).

[0082] Therefore, for example, in method 600, optionally at block 616, one or more of the following can be sent to the UE: a transmission scheme indication related to sending a report in a UL resource that overlaps with one or more other channels; or a priority rule configuration. In one aspect, configuration component 456 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) can send to the UE: a transmission scheme indication related to sending a report in a UL resource that overlaps with one or more other channels; or a priority rule configuration. For example, one or more other channels can be UL channels or DL ​​channels scheduled by a network entity. In an example, the transmission scheme indication may include a priority indication that indicates priority (or whether to prioritize) the out-of-synchronization state report compared to one or more other channels (e.g., compared to receiving DL communication in overlapping DL resources or compared to sending UL communication in overlapping UL resources). In another example, the priority rule configuration may include an indicator of whether to prioritize sending the out-of-synchronization state report compared to other channels. In the example, configuration component 456 can send transmission scheme indications in dynamic signaling (such as DCI or MAC-CE) and / or send priority rule configurations in semi-static signaling (such as RRC or SI).

[0083] In method 500, optionally at block 512, one or more of the following can be received from the network entity: a transmission scheme indication related to sending a report in a UL resource that overlaps with one or more other channels; or a priority rule configuration. On one hand, configuration processing component 356 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can receive from the network entity: a transmission scheme indication related to sending a report in a UL resource that overlaps with one or more other channels; or a priority rule configuration, as described above. Synchronization state component 354 can report a loss-of-synchronization state according to the configured priority rules.

[0084] In one example, where resources used for out-of-synchronization status reporting overlap with resources of one or more other UL channels, synchronization state component 354 can multiplex the report with one or more other UL channels to transmit the report based on transmission scheme indication, priority rule configuration, UE capability, or UE processing timeline requirements, or a combination thereof (e.g., at block 504). In one example, UE 104 can report UE capability to a network entity. Similarly, for example, upon receiving an out-of-synchronization status report (e.g., at block 604), synchronization state processing component 452 can demultiplex the report with one or more other UL channels based on transmission scheme indication, priority rule configuration, UE capability, or UE processing timeline requirements, or a combination thereof.

[0085] In another example, to perform RLF or BFD recovery, a network entity may provide auxiliary information to UE 104 in a DCI or MAC-CE, etc., and UE 104 may use this auxiliary information when performing RLF or BFD recovery (e.g., after declaring RLF or BFD). Therefore, for example, in method 600, optionally at block 618, network-based auxiliary information may be sent to the UE for RLF or BFD recovery. On one hand, configuration component 456 (e.g., in conjunction with processor 412, memory / multiple memories 416, transceiver 402, BS communication component 442, etc.) may send network-based auxiliary information to the UE for RLF or BFD recovery. For example, as described, configuration component 456 may send network-based auxiliary information to UE 104 in dynamic or semi-static signaling. In method 500, optionally at block 514, network-based auxiliary information may be received from a network entity for RLF or BFD recovery. On one hand, configuration processing component 356 (e.g., in conjunction with processor 312, memory / multiple memories 316, transceiver 302, UE communication component 342, etc.) can receive network-based auxiliary information from network entities for use in RLF or BFD recovery. In an example, UE communication component 342 can use the auxiliary information when performing RLF or BFD recovery (e.g., after detecting or declaring an RLF based on degraded RLM measurements). For example, the auxiliary information may include configuration or indication of physical PRACH resources that can be shared by the RACH procedures for RLF or BFD recovery and PDCCH commands at UE 104. This can improve PRACH utilization efficiency. In another example, if UE 104 declares an RLF or BFD without transmitting a loss-of-synchronization state report, or if UE 104 does not receive a response from the network entity after transmitting a loss-of-synchronization state report, the auxiliary information can indicate whether UE 104 needs to monitor PDCCH commands within the RAR window of the CBRA. This can reduce ambiguity regarding the specific UE implementation of the RLF or BFD.

[0086] Figure 7 This is a block diagram of a MIMO communication system 700 including base station 102 and UE 104. The MIMO communication system 700 can be illustrated by reference. Figure 1 The wireless communication access network 100 is described in various aspects. Base station 102 may be a reference. Figure 1 Examples of various aspects of the described base station 102 are provided. Base station 102 may be equipped with antennas 734 and 735, and UE 104 may be equipped with antennas 752 and 753. In the MIMO communication system 700, base station 102 can transmit data simultaneously through multiple communication links. Each communication link may be referred to as a "layer," and the "rank" of the communication link indicates the number of layers used for communication. For example, in a 2x2 MIMO communication system in which base station 102 transmits two "layers," the rank of the communication link between base station 102 and UE 104 is two.

[0087] At base station 102, a transmit (Tx) processor 720 can receive data from a data source. The transmit processor 720 can process the data. The transmit processor 720 can also generate control symbols or reference symbols. A transmit MIMO processor 730 can perform spatial processing (e.g., pre-decoding, if applicable) on the data symbols, control symbols, or reference symbols, and can provide output symbol streams to transmit modulators / demodulators 732 and 733. Each modulator / demodulator 732 to 733 can process (e.g., for OFDM, etc.) its corresponding output symbol stream to obtain an output sample stream. Each modulator / demodulator 732 to 733 can further process the output sample stream (e.g., perform analog conversion, amplification, filtering, and up-conversion) to obtain a DL signal. In one example, the DL signal from modulator / demodulator 732 and modulator / demodulator 733 can be transmitted via antenna 734 and antenna 735, respectively.

[0088] UE 104 can be used as a reference. Figure 1 and Figure 3Examples of various aspects of the described UE 104. At UE 104, UE antennas 752 and 753 can receive DL signals from base station 102 and can provide the received signals to modulator / demodulator 754 and modulator / demodulator 755, respectively. Each modulator / demodulator 754 to 755 can adjust (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain an input sample. Each modulator / demodulator 754 to 755 can further process (e.g., for OFDM, etc.) the input sample to obtain a received symbol. A MIMO detector 756 can obtain the received symbols from modulator / demodulator 754 and modulator / demodulator 755, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. The receive (Rx) processor 758 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, thereby providing decoded data for UE 104 to the data output and providing decoded control information to the processor 780 or the memory / multiple memories 782.

[0089] In some cases, processor 780 may execute stored instructions to instantiate UE communication component 342 (see, for example...). Figure 1 and Figure 3 ).

[0090] On the uplink (UL), at UE 104, the transmitting processor 764 can receive and process data from a data source. The transmitting processor 764 can also generate reference symbols for a reference signal. Symbols from the transmitting processor 764 can be pre-decoded (if applicable) by the transmitting MIMO processor 766, further processed by modulator / demodulator 754 and 755 (e.g., for single-carrier FDMA, etc.), and transmitted to base station 102 according to communication parameters received from base station 102. At base station 102, the UL signal from UE 104 can be received by antennas 734 and 735, processed by modulator / demodulator 732 and 733, detected (if applicable) by MIMO detector 736, and further processed by the receiving processor 738. The receiving processor 738 can provide decoded data to a data output and processor 740 or memory / multiple memories 742.

[0091] In some cases, processor 740 may execute stored instructions to instantiate BS communication component 442 (see, for example...). Figure 1 and Figure 4 ).

[0092] Components of UE 104 may be implemented individually or collectively using one or more ASICs, which are adapted to perform some or all of the applicable functions in hardware. Each of the indicated modules may be a component for performing one or more functions related to the operation of the MIMO communication system 700. Similarly, components of base station 102 may be implemented individually or collectively using one or more application-specific integrated circuits (ASICs), which are adapted to perform some or all of the applicable functions in hardware. Each of the indicated components may be a component for performing one or more functions related to the operation of the MIMO communication system 700.

[0093] The following aspects are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0094] Aspect 1 is a method for wireless communication at a UE, the method comprising: performing a downlink timing measurement of a signal received from a network entity; and sending a report to the network entity indicating a loss-of-synchronization state of the downlink based on a comparison between the downlink timing measurement of the signal and a previous downlink timing measurement of a previous signal and a threshold.

[0095] In aspect 2, the method according to aspect 1 includes: wherein the out-of-sync state of transmitting DL is further based on the time alignment timer not expiring and RLF or BFD not being declared.

[0096] In aspect 3, the method according to any one of aspects 1 or 2 includes: receiving configuration from the network entity, the configuration including an indication of the threshold in RRC signaling or SI.

[0097] In aspect 4, the method according to any one of aspects 1 to 3 includes: wherein sending the out-of-synchronization state of the DL includes: sending a UCI or MAC-CE indicating the out-of-synchronization state of the DL.

[0098] In aspect 5, the method according to any one of aspects 1 to 4 includes: wherein the report includes an indication of the downlink timing measurement or the difference between the downlink timing measurement and the threshold.

[0099] In aspect 6, the method according to aspect 5 includes: compressing or quantizing the downlink timing measurement or the difference, wherein the report includes the compressed or quantized downlink timing measurement or difference.

[0100] In aspect 7, the method according to any one of aspects 1 to 6 includes: wherein the report includes an indication of a CC index, and the signal is received on the DL via the CC index.

[0101] In aspect 8, the method according to any one of aspects 1 to 7 includes: wherein the report additionally includes an indication of the state of an RLM measurement or an indication of the state of an RLM measurement performed by the UE, or an indication of the state of a BM measurement or an indication of the state of a BM measurement.

[0102] In aspect 9, the method according to any one of aspects 1 to 8 includes receiving from the network entity one or more of the following: a transmission scheme indication related to transmitting the report in a UL resource, the UL resource overlapping with one or more other UL channels or one or more other DL channels; or a priority rule configuration semi-statically configured by the network entity.

[0103] In aspect 10, the method according to aspect 9 includes sending the report by sending the report based on a priority indication included in the transmission scheme indication or the priority rule configuration, rather than sending the one or more other UL channels or receiving the one or more other DL channels.

[0104] In aspect 11, the method according to any one of aspects 9 or 10 includes: wherein sending the report includes: applying power boost or dynamic power sharing based on the sending scheme indication or the priority rule configuration.

[0105] In aspect 12, the method according to any one of aspects 9 to 11 includes: wherein sending the report includes: multiplexing the report with the one or more other UL channels based on the transmission scheme indication, the priority rule configuration, UE capabilities, UE processing timeline requirements, or a combination thereof.

[0106] In aspect 13, the method according to any one of aspects 1 to 12 includes: receiving an indication of one or more of an aperiodic burst of a scheduling downlink reference signal or an aperiodic uplink reference signal based on the out-of-synchronization state of the DL.

[0107] In aspect 14, the method according to any one of aspects 1 to 13 includes: receiving an advance indication of the timing of monitoring for a downlink control channel based on the out-of-synchronization state of the DL, the downlink control channel triggering a random access procedure for UL timing acquisition.

[0108] In aspect 15, the method according to any one of aspects 1 to 14 includes: receiving downlink control channel commands for a random access procedure based at least in part on the out-of-synchronization state of the transmitted DL.

[0109] In aspect 16, the method according to any one of aspects 1 to 15 includes: receiving network-based auxiliary information for radio link failure recovery based at least in part on the out-of-synchronization state of the DL.

[0110] In aspect 17, the method according to aspect 16 includes: wherein the network-based auxiliary information includes an indication that PRACH resources can be shared by radio link failure recovery or beam failure recovery procedures and by random access procedures via downlink control channel commands.

[0111] In aspect 18, the method according to any one of aspects 16 or 17, wherein the network-based auxiliary information indicates whether the UE wants to monitor the downlink control channel associated with the random access procedure commanded by the network entity within a random access response window associated with the random access procedure initiated by the UE.

[0112] Aspect 19 is a method for wireless communication at a network entity, the method comprising: receiving from the UE a report indicating a loss-of-synchronization state of the DL based on a difference between a DL timing measurement of a signal transmitted to a UE and a previous downlink timing measurement of a previous signal transmitted to the UE being at least equal to or greater than a threshold; and sending a response signal to the UE based on the loss-of-synchronization state of the DL to correct the downlink timing or to initiate a random access procedure.

[0113] In aspect 20, the method according to aspect 19 includes: sending a configuration to the UE, the configuration including an indication of the threshold in RRC signaling or SI.

[0114] In aspect 21, the method according to any one of aspects 19 or 20 includes: wherein receiving the out-of-synchronization state of the DL includes: receiving a UCI or MAC-CE indicating the out-of-synchronization state of the DL.

[0115] In aspect 22, the method according to any one of aspects 19 to 21 includes: wherein the report includes an indication of the downlink timing measurement or the difference between the downlink timing measurement and the threshold.

[0116] In aspect 23, the method according to aspect 22 includes: decompressing or mapping the downlink timing or the difference between the value specified in the report.

[0117] In aspect 24, the method according to any one of aspects 19 to 23 includes: wherein the report includes an indication of a CC index, through which the signal is received on the DL.

[0118] In aspect 25, the method according to any one of aspects 19 to 24 includes: wherein the report additionally includes an RLM measurement or an indication of the state of an RLM measurement performed by the UE, or a BM measurement or an indication of the state of the BM measurement, and wherein the response signal is sent based on the RLM measurement, the state of the RLM measurement, the BM measurement, or the state of the BM measurement.

[0119] In aspect 26, the method according to any one of aspects 19 to 25 includes sending to the UE one or more of the following: a transmission scheme indication related to sending the report in a UL resource, the UL resource overlapping with one or more other UL channels or one or more other DL channels; or a priority rule configuration semi-statically configured by the network entity.

[0120] In aspect 27, the method according to aspect 26 includes receiving the report by demultiplexing the report with the one or more other UL channels based on the transmission scheme indication, the priority rule configuration, UE capabilities, UE processing timeline requirements, or a combination thereof.

[0121] In aspect 28, the method according to any one of aspects 19 to 27 includes: wherein the response signal includes an indication of an aperiodic burst of a scheduling downlink reference signal; and correcting the downlink timing based on a response to the downlink reference signal received from the UE.

[0122] In aspect 29, the method according to any one of aspects 19 to 28 includes: wherein the response signal includes an indication of scheduling an aperiodic uplink reference signal; and detecting whether the out-of-sync state has been improved based on the aperiodic uplink reference signal.

[0123] In aspect 30, the method according to any one of aspects 19 to 29 includes: wherein the response signal includes an advance indication of the timing of monitoring a downlink control channel, the downlink control channel triggering a random access procedure for UL timing acquisition; and the downlink control channel is transmitted during the monitoring timing.

[0124] In aspect 31, the method according to any one of aspects 19 to 30 includes: wherein the response signal includes a downlink control channel command for a random access channel procedure.

[0125] In aspect 32, the method according to any one of aspects 19 to 31 includes: transmitting network-based auxiliary information for radio link failure recovery, at least in part based on the out-of-synchronization state of the DL.

[0126] In aspect 33, the method according to aspect 32 includes: wherein the network-based auxiliary information includes an indication that PRACH resources can be shared by radio link failure recovery or beam failure recovery procedures and by random access procedures via downlink control channel commands.

[0127] In aspect 34, the method according to any one of aspects 32 or 33 includes: wherein the network-based auxiliary information indicates whether the UE wants to monitor the downlink control channel associated with the random access procedure commanded by the network entity within a random access response window associated with the random access procedure initiated by the UE.

[0128] Aspect 35 is an apparatus for wireless communication, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and operable, when executed by the one or more processors, to cause the apparatus to perform any of the methods described in aspects 1 to 34.

[0129] Aspect 36 is an apparatus for wireless communication, the apparatus including components for performing any of the methods described according to aspects 1 to 34.

[0130] Aspect 37 is one or more computer-readable media, the computer-readable medium including code executable by one or more processors for wireless communication, the code including code for performing any of the methods described according to aspects 1 to 34.

[0131] The above detailed description, illustrated in conjunction with the accompanying drawings, describes examples and does not represent only examples that can be implemented or fall within the scope of the claims. The term "example" as used in this description means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0132] Information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0133] The various exemplary frames and components described in connection with the disclosure herein may be implemented or executed using specially programmed devices, such as, but not limited to, processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, designed to perform the functions described herein. While a specially programmed processor may be a microprocessor, in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0134] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or code on or transmitted via a non-transitory computer-readable medium. Other examples and specific implementations fall within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using hardware, firmware, hardwired, software executed by a specially programmed processor, or any combination of these. Features implementing the functions may also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations. Additionally, as used herein, including in the claims, the word "or" used in a list of entries beginning with "at least one of" indicates a distributed list, such that a list such as "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0135] Computer-readable media includes both computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of carrying or storing desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disks and optical discs include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, where disks typically copy data magnetically, while optical discs use lasers to copy data optically. Combinations of the above are also included within the scope of computer-readable media.

[0136] The prior description of this disclosure is provided to enable those skilled in the art to implement or use it. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Furthermore, while elements of the described aspects and / or embodiments are described or claimed in the singular, plural forms are contemplated unless explicitly stated otherwise. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication, the apparatus comprising: transceiver; One or more memories, the one or more memories being configured to store instructions individually or in combination; and One or more processors, the one or more processors being communicatively coupled to the one or more memories, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the device to: Perform downlink (DL) timing measurements on signals received from network entities; as well as A report indicating the DL's out-of-sync state is sent to the network entity based on comparing the difference between the downlink timing measurement of the signal and the previous downlink timing measurement of the previous signal with a threshold.

2. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to further transmit the out-of-synchronization state of DL based on the time alignment timer not expiring and radio link failure (RLF) or beam failure detection (BFD) not being declared.

3. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive configuration from the network entity, the configuration including an indication of the threshold in Radio Resource Control (RRC) signaling or System Information (SI).

4. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to transmit the out-of-synchronization state of DL in uplink control information (UCI) or media access control (MAC)-control element (CE).

5. The apparatus of claim 1, wherein the report includes an indication of the downlink timing measurement or the difference between the downlink timing measurement and the threshold.

6. The apparatus of claim 5, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to compress or quantize the downlink timing measurement or the difference, wherein the report includes the compressed or quantized downlink timing measurement or difference.

7. The apparatus of claim 1, wherein the report includes an indication of a component carrier (CC) index, through which the signal is received on the DL.

8. The apparatus of claim 1, wherein the report additionally includes a radio link monitoring (RLM) measurement or an indication of the status of an RLM measurement performed by the apparatus, or a beam management (BM) measurement or an indication of the status of a BM measurement.

9. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive one or more of the following from the network entity: The transmission scheme indication associated with transmitting the report in the uplink (UL) resource, which overlaps with one or more other UL channels or one or more other DL channels; or Prioritization rules are configured semi-statically by the network entity.

10. The apparatus of claim 9, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to transmit the report based on a priority indication included in the transmission scheme indication or the priority rule configuration, rather than transmitting the one or more other UL channels or receiving the one or more other DL channels.

11. The apparatus of claim 9, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to transmit the report at least in part by configuring application power boost or dynamic power sharing based on the transmission scheme indication or the prioritization rule.

12. The apparatus of claim 9, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to transmit the report at least in part by multiplexing the report with the one or more other UL channels based on the transmission scheme instruction, the prioritization rule configuration, user equipment (UE) capabilities, UE processing timeline requirements, or a combination thereof.

13. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive an indication of one or more of an aperiodic burst of a downlink reference signal or an aperiodic uplink reference signal based on the out-of-synchronization state of the DL.

14. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive an advance indication of the timing of monitoring of a downlink control channel based on the out-of-synchronization state of the DL, the downlink control channel triggering a random access procedure for UL timing acquisition.

15. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive downlink control channel commands for a random access procedure based at least in part on the out-of-sync state of transmitting the DL.

16. The apparatus of claim 1, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive network-based auxiliary information for radio link failure recovery, at least in part based on the out-of-sync state of the DL.

17. The apparatus of claim 16, wherein the network-based auxiliary information includes an indication that physical random access channel (PRACH) resources can be shared by radio link failure recovery or beam failure recovery procedures and random access procedures via downlink control channel commands.

18. The apparatus of claim 16, wherein the network-based auxiliary information indicates whether the apparatus should monitor the downlink control channel associated with the random access procedure commanded by the network entity within a random access response window associated with a random access procedure initiated by the user equipment (UE).

19. An apparatus for wireless communication, the apparatus comprising: transceiver; One or more memories, the one or more memories being configured to store instructions individually or in combination; and One or more processors, the one or more processors being communicatively coupled to the one or more memories, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the device to: A report indicating a loss-of-synchronization state of the DL is received from the UE based on a difference between a downlink (DL) timing measurement of a signal transmitted to the user equipment (UE) and a previous downlink timing measurement of a previous signal transmitted to the UE, which is at least equal to or greater than a threshold; and Based on the out-of-synchronization state of the DL, a response signal is sent to the UE to correct the downlink timing or to initiate a random access procedure.

20. The apparatus of claim 19, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to send a configuration to the UE, the configuration including an indication of the threshold in Radio Resource Control (RRC) signaling or System Information (SI).

21. The apparatus of claim 19, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to receive the out-of-synchronization state of the DL in uplink control information (UCI) or media access control (MAC)-control element (CE).

22. The apparatus of claim 19, wherein the report includes an indication of the downlink timing measurement or the difference between the downlink timing measurement and the threshold.

23. The apparatus of claim 22, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to decompress or map the downlink timing or the difference between the value specified in the report.

24. The apparatus of claim 19, wherein the report includes an indication of a component carrier (CC) index, through which the signal is received on the DL.

25. The apparatus of claim 19, wherein the report additionally includes a radio link monitoring (RLM) measurement or an indication of the status of an RLM measurement performed by the UE, or a beam management (BM) measurement or an indication of the status of the BM measurement, and wherein the response signal is transmitted based on the RLM measurement, the status of the RLM measurement, the BM measurement, or the status of the BM measurement.

26. The apparatus of claim 19, wherein the one or more processors are individually or in combination configured to execute the instructions to cause the apparatus to send one or more of the following to the UE: The transmission scheme indication associated with transmitting the report in the uplink (UL) resource, which overlaps with one or more other UL channels or one or more other DL channels; or Prioritization rules are configured semi-statically by the device.

27. A method for conducting wireless communication at a user equipment (UE), the method comprising: Perform downlink (DL) timing measurements on signals received from network entities; as well as A report indicating the DL's out-of-sync state is sent to the network entity based on comparing the difference between the downlink timing measurement of the signal and the previous downlink timing measurement of the previous signal with a threshold.

28. The method of claim 27, wherein the out-of-synchronization state of transmitting the DL is further based on the time alignment timer not expiring and radio link failure (RLF) or beam failure detection (BFD) not being declared.

29. A method for conducting wireless communication at a network entity, the method comprising: A report indicating a loss-of-synchronization state of the DL is received from the UE based on a difference between a downlink (DL) timing measurement of a signal transmitted to the user equipment (UE) and a previous downlink timing measurement of a previous signal transmitted to the UE, which is at least equal to or greater than a threshold; and Based on the out-of-synchronization state of the DL, a response signal is sent to the UE to correct the downlink timing or to initiate a random access procedure.

30. The method according to claim 29, further comprising: The configuration is sent to the UE, the configuration including an indication of the threshold in Radio Resource Control (RRC) signaling or System Information (SI).

Images