Resolving anomalous timing advance commands

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may detect a condition associated with an abnormal timing advance command from a network. Accordingly, the UE may perform a random access channel procedure with the network based at least in part on detecting the condition. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for resolving anomalous timing advance commands. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to detect a condition associated with an abnormal timing advance command (TAC) from a network. The one or more processors may be configured to perform a random access channel (RACH) procedure with the network based at least in part on detecting the condition.

[0006] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include detecting a condition associated with an abnormal TAC from a network. The method may include performing a RACH procedure with the network based at least in part on detecting the condition.

[0007] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to detect a condition associated with an abnormal TAC from a network. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform a RACH procedure with the network based at least in part on detecting the condition.

[0008]

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for detecting a condition associated with an abnormal TAC from a network. The apparatus may include means for performing a RACH procedure with the network based at least in part on detecting the condition.

[0009] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

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

[0011] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0013] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0014] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment in a wireless network according to the present disclosure.

[0015] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0016] Figure 4 is a diagram illustrating an example associated with resolving an abnormal timing advance command (TAC) according to the present disclosure.

[0017] Figure 5 is a diagram illustrating an example associated with tracking an amount of a random access channel procedure according to the present disclosure.

[0018] Figure 6is a diagram illustrating an example process associated with resolving an abnormal TAC according to the present disclosure.

[0019] Figure 7 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0020] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0021] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0022] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or 5G and beyond (e.g., 6G) RATs.

[0023] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0024] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0025] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0026] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0027] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0028] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0029] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0030] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0031] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0033] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0034] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0035] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0036] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0037] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, communication manager 140 may detect a condition associated with an abnormal timing advance command (TAC) from a network (e.g., including network node 110), and may perform a random access channel (RACH) procedure with the network (e.g., via network node 110) based at least in part on detecting the condition. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0038] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0039] Figure 22 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0040] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0041] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0042] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0043] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0044] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to Figures 4 to 7 ).

[0045] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 2 Figures 4 to 7 ).

[0046] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component that can execute or guide e.g. Figure 6 10 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 6 The process 600 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0047] In some aspects, a UE (e.g., Figure 7 The UE 120 and / or the device 700 may include a component for detecting a condition associated with an abnormal TAC from the network and / or a component for performing a RACH procedure with the network based at least in part on detecting the condition. The components for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0048] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0049] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0050] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0051] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0052] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0053] Figure 33 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0054] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or to do both.

[0055] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0056] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional split such as defined by 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0057] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional partitioning, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0058] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0059] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0060] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0061] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0062] When transmitting to a network node (e.g., to an RU), the UE may apply a timing advance value to determine when to initiate an uplink transmission (e.g., when to cause the UE's antenna to begin transmitting RF waves or other electromagnetic waves). In order to improve the quality and reliability of uplink transmissions from the UE to the network node, the network node may send a TAC to the UE (e.g., via the RU) to adjust the timing advance value applied by the UE. For example, each TAC may indicate a positive or negative value by which the UE should adjust the timing advance value applied to the uplink transmission.

[0063] In some cases, the UE may receive multiple TACs within a time window that causes an uplink transmission failure. For example, continuous adjustment of the timing advance value by the network node may cause the UE to reach a maximum retransmission amount of an uplink transmission (e.g., an RLC packet). The UE typically performs a radio link failure (RLF) procedure (e.g., an RLF recovery procedure) based on the maximum retransmission amount reached. Typically, the RLF procedure consumes a large amount of power and processing resources at both the UE and the network node, and increases network congestion by consuming network resources.

[0064] Some techniques and apparatuses described herein enable a UE (e.g., Figure 7 The UE 120 and / or the apparatus 700) is capable of performing a random access channel (RACH) procedure with the network (e.g., via a network node 110, such as a RU 340 and / or a device for controlling the RU 340, such as a DU 330 and / or a CU 310) based on detecting a condition associated with an abnormal TAC. For example, the TAC may be associated with a timing adjustment value that sums to a total timing adjustment value, such that the condition may include: the total timing adjustment value satisfies an adjustment threshold within a time window. Additionally or alternatively, the condition may include: the amount of TACs received within the time window satisfies an amount threshold. Therefore, the UE 120 may correct the timing advance value without performing an RLF process, which saves power and processing resources at both the UE 120 and the network node 110, and reduces network congestion by saving network resources.

[0065] Generally speaking, the RACH procedure is faster than the RLF procedure. Therefore, when the abnormal TAC is resolved using the RACH procedure, the UE 120 further reduces latency and increases throughput compared to performing the RLF procedure. In addition, unlike the RLF procedure, the RACH procedure can be performed without dropping calls (e.g., voice over NR (VoNR) calls). Therefore, the UE 120 reduces dropped calls, which further saves power and processing resources at both the UE 120 and the network node 110, and reduces network congestion by saving network resources.

[0066] Figure 4 4 is a diagram illustrating an example 400 associated with resolving an abnormal TAC according to the present disclosure. Figure 4 As shown in FIG, the network node 110 and the UE 120 may communicate with each other (e.g., in Figure 1 wireless network 100).

[0067] As indicated by reference numeral 405, the network node 110 may send (e.g., directly or via a RU 340 controlled by the network node 110) one or more TACs, and the UE 120 may receive the one or more TACs. The TACs may include a medium access control (MAC) message (e.g., exchanged via a physical (PHY) layer of the network node 110 and the UE 120). Each TAC may indicate a value, and the UE 120 may adjust a timing advance value applied to uplink transmissions to the network node 110 (e.g., directly or via a RU 340 controlled by the network node 110) by the indicated value. Thus, each TAC may be associated with a direction; for example, a TAC may indicate a positive value and thus be associated with a positive direction, or may indicate a negative value and thus be associated with a negative direction.

[0068] As shown at reference numeral 410, UE 120 can detect a condition associated with an abnormal TAC from a network (e.g., a network including network node 110). For example, UE 120 can track TACs received within a sliding time window (e.g., as described in conjunction with reference numeral 405). The time window can be 0.5 seconds, 1 second, 1.5 seconds, 2 seconds, etc.

[0069] The condition may include that the total timing adjustment value associated with the TAC within the time window satisfies the adjustment threshold. In some aspects, the UE 120 may determine the total timing adjustment value by summing the values ​​indicated by the TAC to determine the total timing adjustment value. The UE 120 may determine the total timing adjustment value by summing the values ​​indicated by all TACs associated with the same direction. For example, the total timing adjustment value may include only positive values ​​indicated by the TAC or only negative values ​​indicated by the TAC. Additionally or alternatively, the condition may include that all TACs received within the time window indicate values ​​associated with the same direction (so that the total timing adjustment value is associated with a single direction). For example, the UE 120 may detect the condition when it receives TACs that all indicate positive values ​​within the time window and the sum of these positive values ​​is the total timing adjustment value that satisfies the adjustment threshold. In another example, the UE 120 may detect the condition when it receives TACs that all indicate negative values ​​within the time window and the sum of these negative values ​​is the total timing adjustment value that satisfies the adjustment threshold.

[0070] UE 120 may determine the throttling threshold based at least in part on a speed associated with UE 120. For example, UE 120 may increase the throttling threshold when the speed associated with UE 120 is lower, and may decrease the throttling threshold when the speed associated with UE 120 is higher. In one example, the throttling threshold may be 57 , wherein when the speed associated with UE 120 is at least 1000 kilometers per hour (km / h), In some aspects, UE 120 may continuously determine the throttling threshold based on a speed associated with UE 120. Alternatively, UE 120 may determine the throttling threshold based on a bin that includes the speed associated with UE 120. For example, UE 120 may determine a first throttling threshold when the speed associated with UE 120 is within a first range (also referred to as a “first bin”), determine a second throttling threshold when the speed associated with UE 120 is within a second range (also referred to as a “second bin”), and so on. UE 120 may determine the UE's velocity based on measurements from a global navigation satellite system (GNSS) (e.g., global positioning system (GPS) measurements), measurements from a magnetic and inertial measurement unit (MIMU) associated with UE 120, measurements from an inertial measurement unit (IMU) associated with UE 120, measurements from another type of sensor associated with UE 120, measurements based on signals from one or more cellular nodes (e.g., network node 110 and / or another network node), measurements based on cellular network access (e.g., access to a network including network node 110), and / or measurements based on Euler angles, etc.

[0071] Additionally or alternatively, the throttling threshold may be preconfigured (e.g., stored in a memory of UE 120). In a combined example, UE 120 may select from a plurality of possible throttling thresholds based on a speed associated with UE 120 (e.g., according to a bin including a speed associated with UE 120, as described above).

[0072] The condition may additionally or alternatively include that the amount of TACs received within the time window satisfies the amount threshold. In some aspects, the UE 120 may determine the amount of TACs by counting all TACs received within the time window. Alternatively, the UE 120 may determine the amount of TACs by counting TACs associated with the same direction. For example, the amount of TACs may include only TACs indicating positive values ​​or only TACs indicating negative values. Additionally or alternatively, the condition may include that all TACs received within the time window indicate values ​​associated with the same direction (so that the amount of TACs is associated with a single direction). For example, the UE 120 may detect the condition when all TACs indicating positive values ​​are received within the time window and the amount of TACs satisfies the amount threshold. In another example, the UE 120 may detect the condition when all TACs indicating negative values ​​are received within the time window and the amount of TACs satisfies the amount threshold.

[0073] UE 120 may determine the amount threshold based at least in part on a speed associated with UE 120. For example, UE 120 may increase the amount threshold when the speed associated with UE 120 is lower and may decrease the amount threshold when the speed associated with UE 120 is higher. In some aspects, UE 120 may continuously determine the amount threshold as a function of the speed associated with UE 120. Alternatively, UE 120 may determine the amount threshold as a function of a bin that includes the speed associated with UE 120, similar to what is described above in connection with adjusting the threshold.

[0074] Additionally or alternatively, the amount threshold may be preconfigured (e.g., stored in a memory of UE 120). In a combined example, UE 120 may select from a plurality of possible amount thresholds based on a speed associated with UE 120 (e.g., according to a bin including a speed associated with UE 120, as described above).

[0075] As indicated by reference numeral 415, the UE 120 may perform a RACH procedure with the network (e.g., via the network node 110) based at least in part on detecting the condition. For example, the UE 120 may send a RACH preamble (also referred to as "Msg1," a "random access message," or "RAM") and receive a random access response (RAR) (also referred to as "Msg2") from the network node 110. For example, the network node 110 may send downlink control information (DCI) on a physical downlink control channel (PDCCH) within a RAR window that schedules transmission of the RAR on a physical downlink shared channel (PDSCH). The RAR may include a timing advance field that indicates a timing advance value for use by the UE 120. Thus, the UE 120 may replace a timing advance (TA) value (e.g., stored in a memory of the UE 120) with a TA value received in a timing advance (TA) command (e.g., in the RAR) during the RACH procedure that is an accumulated TA value based on the TAC. Thus, UE 120 may use the RACH procedure to resolve anomalies in TACs (eg, too many TACs, typically in a single direction, within a time window).

[0076] UE 120 may complete the RACH procedure by sending Msg3 (e.g., a physical uplink shared channel (PUSCH) message) and receiving Msg4 (e.g., a PDCCH message indicating a contention resolution timer and a PDSCH message including a MAC control element (MAC-CE)) from network node 110. Accordingly, UE 120 may acknowledge Msg4 (e.g., by sending a hybrid automatic repeat request (HARQ) acknowledgement signal (ACK)). Although described as using a 4-step RACH procedure, UE 120 may alternatively use a 2-step RACH procedure (e.g., using MsgA instead of Msg1 and Msg3, and receiving MsgB instead of Msg2 and Msg4).

[0077] As shown by reference numeral 420, the UE 120 can track the amount of RACH procedures performed based on detecting the condition. In some aspects, the UE 120 can track the amount of RACH procedures, such as in conjunction with Figure 5 Thus, the UE 120 may iteratively perform the operations described in conjunction with reference numerals 405, 410, and 415 and track the amount of RACH procedures accordingly.

[0078] As shown by reference numeral 425, UE 120 may trigger RLF based at least in part on the amount of RACH procedures satisfying a RACH threshold. For example, UE 120 may perform cell selection (e.g., by performing measurements and selecting a synchronization signal block (SSB) for initial access). Thus, after selecting a cell, UE 120 may send an RRC connection reestablishment request (e.g., an RRCConnectionReestablishmentRequest message as defined in the 3GPP specification) and may receive an RRC connection reestablishment message (e.g., an RRCConnectionReestablishment message as defined in the 3GPP specification) from the selected cell. UE 120 may trigger RLF only after failing to resolve an anomaly in TAC (e.g., too many TACs in a single direction within a time window, typically) using one or more RACH procedures (e.g., as described in conjunction with reference numeral 415).

[0079] By using the combination Figure 4In the described technology, UE 120 performs a RACH procedure with network node 110 based on detecting a condition associated with an abnormal TAC. UE 120 performs an RLF procedure only as a fallback. Therefore, UE 120 saves power and processing resources at both UE 120 and network node 110 compared to performing an RLF procedure. In addition, UE 120 reduces network congestion by saving network resources compared to performing an RLF procedure. When utilizing a RACH procedure to resolve an abnormal TAC, UE 120 further reduces latency and increases throughput compared to performing an RLF procedure.

[0080] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0081] Figure 5 5 is a diagram illustrating an example 500 associated with tracking the amount of RACH procedures according to the present disclosure. Example 500 includes an iterative process for tracking RACH procedures triggered by conditions associated with abnormal TACs. For example, the iterative process may be performed by a UE (e.g., Figure 7 UE 120 and / or device 700) to execute.

[0082] As shown by reference numeral 510, UE 120 may initiate a RACH counter (e.g., represented by Continuous_RACH_number) at zero (or another initial starting value). For example, UE 120 may initiate a RACH counter (e.g., represented by Continuous_RACH_number) at zero (or another initial starting value). Figure 1 The RACH counter is initiated after an RRC connection is established with a cell in the wireless network 100 (eg, via the network node 110).

[0083] As indicated by reference numeral 520, UE 120 may receive one or more TACs. The TACs may include MAC messages (e.g., exchanged via the PHY layers of network node 110 and UE 120). Figure 4 As described, each TAC may indicate a value, and UE 120 may adjust the timing advance value applied to uplink transmissions to network node 110 (eg, directly or via RU 340 controlled by network node 110) by the indicated value.

[0084] As shown at reference numeral 530, UE 120 can detect whether a condition associated with an abnormal TAC is satisfied. In some aspects, UE 120 can detect such as in conjunction with Figure 4 When UE 120 detects that the condition is not met, UE 120 may return to the operation described in conjunction with reference numeral 520 (eg, receiving a TAC from the network).

[0085] When UE 120 detects that the condition is met, UE 120 may determine whether the RACH counter meets the RACH threshold, as shown by reference numeral 540. The RACH threshold may be preconfigured (e.g., stored in a memory of UE 120). Alternatively, the RACH threshold may be selected based on channel conditions associated with UE 120 and network node 110 (e.g., a CQI or another indicator of channel quality associated with a channel between UE 120 and network node 110). For example, UE 120 may increase the RACH threshold when the channel quality is better and decrease the RACH threshold when the channel quality is worse.

[0086] When the UE 120 detects that the RACH counter meets the RACH threshold, the UE 120 can trigger an RLF, as shown by reference numeral 550a. Therefore, the UE 120 can determine that an anomaly of TAC (e.g., too many TACs in a single direction, usually within a time window) cannot be resolved after one or more RACH procedures (e.g., as described in conjunction with reference numeral 550b). In addition, the UE 120 can return to the operations described in conjunction with reference numeral 510 (e.g., resetting the RACH counter) and the operations described in conjunction with reference numeral 520 (e.g., receiving TAC from the network).

[0087] When UE 120 detects that the RACH counter fails to meet the RACH threshold, UE 120 may trigger a RACH procedure, as shown by reference numeral 550b. Thus, UE 120 may attempt to use a RACH procedure (e.g., as combined with Figure 4 described) to remedy anomalies in TAC (e.g., excessive TAC, typically in a single direction within a time window).

[0088] Additionally, UE 120 may increment the RACH counter as indicated by reference numeral 560. UE 120 may return to operations described in connection with reference numeral 520 (eg, receiving a TAC from the network).

[0089] Thus, the RACH counter enables the UE 120 to determine when an anomaly in the TAC (e.g., too many TACs, typically in a single direction, within a time window) is unlikely to be resolved by additional RACH procedures. The RACH counter may also be reset based on additional conditions. The additional conditions may include that the UE 120 receives a TAC associated with a direction opposite to the direction associated with the previous TAC (the most recently received TAC). For example, the UE 120 may receive a TAC indicating a negative value after the most recent TAC indicates a positive value, or may receive a TAC indicating a positive value after the most recent TAC indicates a negative value. Thus, the UE 120 may reset the RACH counter to zero (or another initial value) based on receiving a TAC associated with a direction opposite to the direction associated with the previous TAC. Additionally or alternatively, the additional conditions may include that a TAC is not received within an interval after the previous TAC (the most recently received TAC) is received. For example, the UE 120 may not receive a TAC within 0.5 seconds (or 1 second, 1.5 seconds, 2 seconds, or a different interval) of receiving the most recent TAC. Thus, UE 120 may reset the RACH counter to zero (or another initial value) based on not receiving a TAC within the interval.

[0090] By using the combination Figure 5 In the described technology, UE 120 performs a RACH procedure with network node 110 based on detecting a condition associated with an abnormal TAC. UE 120 performs an RLF procedure only as a fallback. Therefore, UE 120 saves power and processing resources at both UE 120 and network node 110 compared to performing an RLF procedure. In addition, UE 120 reduces network congestion by saving network resources compared to performing an RLF procedure. When utilizing a RACH procedure to resolve an abnormal TAC, UE 120 further reduces latency and increases throughput compared to performing an RLF procedure.

[0091] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0092] Figure 6 600 is a diagram illustrating an example process 600 performed, for example, by a UE according to the present disclosure. The example process 600 is a diagram in which a UE (e.g., Figure 7 An example of UE 120 and / or device 700 performing operations associated with resolving an abnormal TAC.

[0093] like Figure 6 As shown, in some aspects, process 600 may include detecting a condition associated with an abnormal TAC from the network (block 610). For example, a UE (e.g., using Figure 7The communications manager 140 and / or detection component 708 depicted in FIG. 1 may detect conditions associated with abnormal TACs from the network, as described herein.

[0094] like Figure 6 As further shown, in some aspects, process 600 may include performing a RACH procedure with the network based at least in part on detecting the condition (block 620). Figure 7 The communications manager 140, receiving component 702, and / or sending component 704 depicted in FIG. 1 may perform a RACH procedure with the network based at least in part on detecting the condition, as described herein.

[0095] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0096] In a first aspect, the TAC comprises a MAC message.

[0097] In a second aspect, alone or in combination with the first aspect, the condition includes: a total timing adjustment value associated with the TAC satisfies an adjustment threshold within a time window.

[0098] In a third aspect, alone or in combination with one or more of the first and second aspects, the total timing adjustment value is associated with a single direction.

[0099] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the adjustment threshold is based at least in part on a speed associated with the UE.

[0100] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the condition includes: an amount of TAC satisfies an amount threshold within a time window.

[0101] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the amount threshold is based at least in part on a speed associated with the UE.

[0102] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 600 includes: (e.g., using Figure 7 ) to track the amount of RACH procedures performed based on detecting the condition; and triggering RLF (e.g., using the communication manager 140, the receiving component 702, and / or the sending component 704) based at least in part on the amount of RACH procedures satisfying a RACH threshold.

[0103] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, tracking the amount of RACH procedures comprises: receiving (e.g., using the communication manager 140 and / or the receiving component 702) a TAC associated with a direction opposite to a direction associated with a previous TAC; and resetting a counter for the RACH procedures based at least in part on receiving the TAC (e.g., using the communication manager 140 and / or the tracking component 710).

[0104] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, tracking the amount of RACH procedures comprises: not receiving a TAC (e.g., using the communication manager 140 and / or the receiving component 702) within an interval after receiving a previous TAC; and resetting a counter of the RACH procedures (e.g., using the communication manager 140 and / or the tracking component 710) based at least in part on not receiving the TAC.

[0105] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 600 includes replacing a TA value stored at the UE with a TA value received in a TA command during a RACH procedure.

[0106] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 In some embodiments, the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more blocks of the blocks of process 600 may be executed in parallel.

[0107] Figure 7 is a diagram of an example apparatus 700 for wireless communication according to the present disclosure. Apparatus 700 may be a UE, or a UE may include apparatus 700. In some aspects, apparatus 700 includes a receiving component 702 and a sending component 704 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 700 may communicate with another apparatus 706 (such as a UE, a network node, or another wireless communication device) using receiving component 702 and sending component 704. As further shown, apparatus 700 may include a communication manager 140. Communication manager 140 may include one or more of a detection component 708 and / or a tracking component 710, among others.

[0108] In some aspects, the apparatus 700 may be configured to perform Figures 4 to 5 Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein (such as Figure 6 In some aspects, the apparatus 700 and / or Figure 7 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 7 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0109] The receiving component 702 may receive communications from the device 706, such as reference signals, control information, data communications, or combinations thereof. The receiving component 702 may provide the received communications to one or more other components of the device 700. In some aspects, the receiving component 702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 700. In some aspects, the receiving component 702 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0110] The transmitting component 704 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 706. In some aspects, one or more other components of the device 700 may generate communications and may provide the generated communications to the transmitting component 704 for transmission to the device 706. In some aspects, the transmitting component 704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 706. In some aspects, the transmitting component 704 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 704 can be co-located with the receive component 702 in a transceiver.

[0111] In some aspects, detection component 708 can detect conditions associated with abnormal TACs from the network (eg, received via device 706, such as a network node). Detection component 708 can include combining Figure 2The MIMO detector, receive processor, controller / processor, memory, or combination thereof of the UE described herein. The receiving component 702 and / or the sending component 704 can perform a RACH procedure with the network (e.g., via the device 706) based at least in part on the detection of the condition by the detection component 708. Thus, the tracking component 710 can replace the TA value stored in the memory of the device 700 with the TA value received in the TA command (e.g., by the receiving component 702) during the RACH procedure. The tracking component 710 can include a combination of Figure 2 A transmit MIMO processor, a transmit processor, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE is described.

[0112] In some aspects, tracking component 710 can track an amount of RACH procedures performed based on detecting the condition by detecting component 708. Receiving component 702 and / or sending component 704 can trigger RLF based at least in part on an amount of RACH procedures satisfying a RACH threshold.

[0113] Figure 7 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 7 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Figure 7 Two or more components shown in may be implemented in a single component, or Figure 7 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 7 The assembly of (one or more) components shown in the executable is described as being composed of Figure 7 Another collection of components shown in the figure performs one or more functions.

[0114] The following provides an overview of some aspects of the disclosure:

[0115] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: detecting a condition associated with an abnormal timing advance command (TAC) from a network; and performing a random access channel (RACH) procedure with the network based at least in part on detecting the condition.

[0116] Aspect 2: The method according to aspect 1, further comprising: replacing a timing advance (TA) value stored at the UE with a TA value received in a TA command during the RACH procedure.

[0117] Aspect 3: The method according to any one of aspects 1 to 2, wherein the TAC includes a medium access control message.

[0118] Aspect 4: The method according to any one of aspects 1 to 3, wherein the condition includes: a total timing adjustment value associated with the TAC satisfies an adjustment threshold within a time window.

[0119] Aspect 5: The method according to aspect 4, wherein the total timing adjustment value is associated with a single direction.

[0120] Aspect 6: The method according to any one of aspects 4 to 5, wherein the adjustment threshold is based at least in part on a speed associated with the UE.

[0121] Aspect 7: The method according to any one of aspects 1 to 6, wherein the condition includes: the amount of the TAC satisfies an amount threshold within a time window.

[0122] Aspect 8: The method according to aspect 7, wherein the amount threshold is based at least in part on a speed associated with the UE.

[0123] Aspect 9: According to any one of aspects 1 to 8, the method also includes: tracking the amount of RACH procedures performed based on detecting the condition; and triggering a radio link failure (RLF) based at least in part on the amount of RACH procedures satisfying a RACH threshold.

[0124] Aspect 10: The method of aspect 9, wherein tracking the amount of RACH procedures comprises: receiving a TAC associated with a direction opposite to the direction associated with a previous TAC; and resetting a counter of RACH procedures based at least in part on receiving the TAC.

[0125] Aspect 11: The method according to any one of aspects 9 to 10, wherein tracking the amount of RACH procedures includes: not receiving a TAC within an interval after receiving a previous TAC; and resetting a counter of RACH procedures based at least in part on not receiving the TAC.

[0126] Aspect 12: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0127] Aspect 13: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 11.

[0128] Aspect 14: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 11.

[0129] Aspect 15: A non-transitory computer-readable medium storing a code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0130] Aspect 16: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.

[0131] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0132] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0133] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0134] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of each aspect includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0135] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated. In addition, as used herein, the articles "one" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise clearly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: Detecting conditions associated with abnormal timing advance commands (TACs) from the network; as well as A random access channel (RACH) procedure is performed with the network based at least in part on detecting the condition.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to: A timing advance (TA) value stored in the memory is replaced with a TA value received in a TA command during the RACH procedure. The apparatus of claim 1 , wherein the TAC comprises a medium access control message.

4. The apparatus according to claim 1, wherein the condition comprises: A total timing adjustment value associated with the TAC satisfies an adjustment threshold within a time window.

5. The apparatus of claim 4, wherein the overall timing adjustment value is associated with a single direction.

6. The apparatus of claim 4, wherein the adjustment threshold is based at least in part on a speed associated with the UE.

7. The apparatus of claim 1, wherein the conditions include: The amount of the TAC satisfies an amount threshold within a time window.

8. The apparatus of claim 7, wherein the amount threshold is based at least in part on a speed associated with the UE.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to: tracking an amount of RACH procedures performed based on detecting the condition; and A radio link failure (RLF) is triggered based at least in part on an amount of the RACH procedures satisfying a RACH threshold.

10. The apparatus of claim 9, wherein the one or more processors for tracking the amount of RACH procedures are configured to: receiving a TAC associated with a direction opposite to the direction associated with a previous TAC; and A counter for a RACH procedure is reset based at least in part on receiving the TAC.

11. The apparatus of claim 9, wherein the one or more processors for tracking the amount of RACH procedures are configured to: No TAC is received within an interval after receipt of a previous TAC; and A counter for the RACH procedure is reset based at least in part on not receiving the TAC.

12. A method of wireless communication performed by a user equipment (UE), the method comprising: Detecting conditions associated with abnormal timing advance commands (TACs) from the network; as well as A random access channel (RACH) procedure is performed with the network based at least in part on detecting the condition.

13. The method according to claim 12, further comprising: A timing advance (TA) value stored at the UE is replaced with a TA value received in a TA command during the RACH procedure. The method of claim 12 , wherein the TAC comprises a medium access control message.

15. The method of claim 12, wherein the conditions include: A total timing adjustment value associated with the TAC satisfies an adjustment threshold within a time window.

16. The method of claim 15, wherein the total timing adjustment value is associated with a single direction.

17. The method of claim 15, wherein the adjustment threshold is based at least in part on a speed associated with the UE.

18. The method of claim 12, wherein the conditions include: The amount of the TAC satisfies an amount threshold within a time window.

19. The method of claim 18, wherein the amount threshold is based at least in part on a speed associated with the UE.

20. The method according to claim 12, further comprising: tracking an amount of RACH procedures performed based on detecting the condition; as well as A radio link failure (RLF) is triggered based at least in part on an amount of the RACH procedures satisfying a RACH threshold.

21. The method of claim 20, wherein tracking the amount of RACH procedures comprises: receiving a TAC associated with a direction opposite to the direction associated with a previous TAC; as well as A counter for a RACH procedure is reset based at least in part on receiving the TAC.

22. The method of claim 20, wherein tracking the amount of RACH procedures comprises: No TAC is received within the interval after the previous TAC is received; as well as A counter for the RACH procedure is reset based at least in part on not receiving the TAC.

23. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: Detecting conditions associated with abnormal timing advance commands (TACs) from the network; as well as A random access channel (RACH) procedure is performed with the network based at least in part on detecting the condition.

24. The non-transitory computer-readable medium of claim 23, wherein the one or more instructions, when executed by the one or more processors of the UE, further cause the UE to: A timing advance (TA) value stored in the memory is replaced with a TA value received in a TA command during the RACH procedure.

25. The non-transitory computer readable medium of claim 23, wherein the condition comprises: A total timing adjustment value associated with the TAC satisfies an adjustment threshold within a time window.

26. The non-transitory computer readable medium of claim 23, wherein the condition comprises: The amount of the TAC satisfies an amount threshold within a time window.

27. The non-transitory computer-readable medium of claim 23, wherein the one or more instructions, when executed by the one or more processors of the UE, further cause the UE to: tracking an amount of RACH procedures performed based on detecting the condition; and A radio link failure (RLF) is triggered based at least in part on an amount of the RACH procedures satisfying a RACH threshold.

28. The non-transitory computer-readable medium of claim 27, wherein the one or more instructions to cause the UE to track the amount of the RACH procedures cause the UE to: receiving a TAC associated with a direction opposite to the direction associated with a previous TAC, or not receiving a TAC within an interval after receiving the previous TAC; and A counter for a RACH procedure is reset based at least in part on receiving the TAC or not receiving the TAC.

29. An apparatus for wireless communication, the apparatus comprising: means for detecting a condition associated with an anomalous timing advance command (TAC) from a network; and Means for performing a random access channel (RACH) procedure with the network based at least in part on detecting the condition.

30. The apparatus according to claim 29, further comprising: Means for replacing a timing advance (TA) value stored in said memory with a TA value received in a TA command during said RACH procedure.

Images