Timing advance indication in random access response for inter-cell multiple transmit and receive point communications

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a different PCI from a PCI of a serving cell of the UE. The UE may receive a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates timing advance (TA) information associated with the additional PCI. Numerous other aspects are described.

Description

Technical Field

[0001] Various aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for timing advance (TA) indication in a random access response (RAR) for inter-cell multiple transmit and receive point (multi-TRP) communications. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephone, 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 a user equipment (UE) or multiple UEs. A UE may communicate with a 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, among other examples).

[0004] The above-mentioned 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 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the UE. The method may include receiving a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates timing advance (TA) information associated with the additional PCI.

[0006] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to send a PRACH communication associated with an additional PCI, the additional PCI being a PCI different from a PCI of a serving cell of the UE. The one or more processors may be configured to receive a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI.

[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 send a PRACH communication associated with an additional PCI, the additional PCI being a PCI different from a PCI of a serving cell of the UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI.

[0008] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a PRACH communication associated with an additional PCI, the additional PCI being a PCI different from a PCI of a serving cell of the apparatus. The apparatus may include means for receiving a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI.

[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 extensively 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 protection 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 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 devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, 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 equipment 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 (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various 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 (UE) 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 An example logical architecture of a distributed RAN according to the present disclosure is illustrated.

[0017] Figure 5 is a diagram illustrating an example of multi-transmitting and receiving point (multi-TRP) communication according to the present disclosure.

[0018] Figure 6 is a diagram illustrating an example of TRP differentiation based at least in part on a control resource set (CORESET) pool index at a UE according to the present disclosure.

[0019] Figure 7 is a diagram illustrating an example of downlink and uplink transmission between a network node and a UE in a wireless network according to the present disclosure.

[0020] Fig. 8A and Figure 8B is a diagram illustrating an example associated with a timing advance (TA) indication in a random access response (RAR) for inter-cell multi-TRP communication according to the present disclosure.

[0021] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0022] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0023] 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 understood 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, functions, or structures and functions 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.

[0024] 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.

[0025] Although various aspects may be described herein using terms 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 RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0026] 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, as well as 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), one 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 in the figure, 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)).

[0027] 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. For example, the network node 110 may include 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.

[0028] 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 the coverage area of ​​the network node 110 and / or the 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 a 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. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0029] In some aspects, the term "base station" or "network node" may refer to an aggregated 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 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.

[0030] 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 can relay 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 communication 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.

[0031] 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).

[0032] 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.

[0033] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can 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.

[0034] 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 operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0035] 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, an air interface, etc. Frequency may be referred to as a carrier, a 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.

[0036] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). 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.

[0037] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on 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 ranges designated 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 "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0038] The frequency between FR1 and FR2 is generally referred to as mid-band frequency. Recent 5G NR research has identified the operating band for these mid-band frequencies as a frequency range designated FR3 (7.125GHz-24.25GHz). The frequency band falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the characteristics of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency ranges designated FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0039] In view of 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 can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can 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 can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0040] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may send a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the UE; and receive a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates timing advance (TA) information associated with the additional PCI. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

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

[0042] Figure 22 is a diagram illustrating an example 200 of a network node 110 communicating with a user equipment (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.

[0043] 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 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0044] 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.

[0045] 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.

[0046] 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 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.

[0047] 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 sent 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 FIG. 8A to FIG. 10 ).

[0048] 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 of the modem 232 shown as DEMOD), 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 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 and / or uplink communications. 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 20 to FIG. 1 ). FIG. 8A to FIG. 10 ).

[0049] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with TA indication in the RAR for inter-cell multi-TRP communication, as described in more detail elsewhere herein. For example, 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 Fig. 9 900 and / or operations of 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 storing 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, Fig. 9 The process 900 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.

[0050] In some aspects, a UE (e.g., UE 120) includes means for sending a PRACH communication associated with an additional PCI, the additional PCI being a PCI different from a PCI of a serving cell of the UE; and / or means for receiving a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI. Means for the UE to perform operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0051] Although Figure 2 The blocks in the 2000 and 2010 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.

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

[0053] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. 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 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) that perform 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. "Network entity" or "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).

[0054] 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, a 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. A 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.

[0055] 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.

[0056] 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.

[0057] 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 the 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 both.

[0058] In some aspects, 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 as having an interface configured to communicate signals with other control functions hosted by CU 310. 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, 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, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0059] 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 partition such as that defined by 3GPP. In some aspects, 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.

[0060] 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 splits, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this 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 communicating with the control plane and user plane of 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.

[0061] The SMO framework 305 may be configured to support RAN deployment and configuration 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.

[0062] The non-RT RIC 315 may be configured to include logic functions that implement 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 communicate 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 implement 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.

[0063] 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).

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

[0065] Figure 4 An example logical architecture of a distributed RAN 400 according to the present disclosure is illustrated.

[0066] The 5G access node 405 may include an access node controller 410. The access node controller 410 may be a central unit (CU) of the distributed RAN 400. In some aspects, a backhaul interface to the 5G core network 415 may terminate at the access node controller 410. The 5G core network 415 may include a 5G control plane component 420 and a 5G user plane component 425 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 410. Additionally or alternatively, a backhaul interface to one or more neighbor access nodes 430 (e.g., another 5G access node 405 and / or an LTE access node) may terminate at the access node controller 410.

[0067] The access node controller 410 may include one or more TRPs 435 and / or may communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). The TRP 435 may be a distributed unit (DU) of the distributed RAN 400. In some aspects, the TRP 435 may correspond to the above combined Figure 1 The network node 110 described herein may include a plurality of TRPs 435. For example, different TRPs 435 may be included in different network nodes 110. Additionally or alternatively, multiple TRPs 435 may be included in a single network node 110. In some aspects, the network node 110 may include a CU (e.g., an access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 may be referred to as a cell, a panel, an antenna array, or an array.

[0068] The TRP 435 may be connected to a single access node controller 410 or to multiple access node controllers 410. In some aspects, there may be a dynamic configuration of split logical functions within the architecture of the distributed RAN 400. For example, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and / or a medium access control (MAC) layer may be configured to terminate at an access node controller 410 or a TRP 435.

[0069] In some aspects, multiple TRPs 435 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., time slot, mini-slot, subframe, or symbol) or in different TTIs using different QCL relationships (e.g., different spatial parameters, different transmit configuration indicator (TCI) states, different precoding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. A TRP 435 may be configured to provide services to a UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 435).

[0070] In some respects, Figure 4 The logical architecture of the distributed RAN 400 described in association may be used to support TA indication in the RAR for inter-cell multi-TRP communications as described herein.

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

[0072] Figure 55 is a diagram illustrating an example 500 of multi-TRP communication (sometimes referred to as multi-panel communication or mTRP communication) according to the present disclosure. Figure 5 As shown, multiple TRPs 505 can communicate with the same UE 120. TRP 505 can correspond to the above combination Figure 4 TRP 435 as described.

[0073] Multiple TRPs 505 (shown as TRP A and TRP B) may communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. The TRPs 505 may coordinate such communications via an interface between the TRPs 505 (e.g., a backhaul interface and / or an access node controller 410). When the TRPs 505 are co-located at the same network node 110 (e.g., when the TRPs 505 are different antenna arrays or panels of the same network node 110), the interface may have less latency and / or higher capacity, and when the TRPs 505 are located at different network nodes 110, the interface may have greater latency and / or lower capacity (compared to co-location). Different TRPs 505 may communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different demodulation reference signal (DMRS) ports, and / or different layers (e.g., different layers in a multi-layer communication).

[0074] In a first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications of a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 505 (e.g., TRP A and TRP B) may transmit communications to UE 120 on the same PDSCH. For example, communications may be transmitted using a single codeword with different spatial layers for different TRPs 505 (e.g., one of the codewords is mapped to a first set of layers transmitted by a first TRP 505 and is mapped to a second set of layers transmitted by a second TRP 505). As another example, communications may be transmitted using multiple codewords, with different codewords being transmitted by different TRPs 505 (e.g., using different sets of layers). In either case, different TRPs 505 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 505 may use a first QCL relationship or a first TCI state for a first DMRS port set corresponding to a first layer set, and the second TRP 505 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) DMRS port set corresponding to a second (different) layer set. In some aspects, the TCI state in the downlink control information (DCI) (e.g., sent on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Typically, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0075] In a second multi-TRP transmission mode (e.g., Mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, the first PDCCH may schedule a first codeword to be sent by the first TRP 505, and the second PDCCH may schedule a second codeword to be sent by the second TRP 505. In addition, a first DCI (e.g., sent by the first TRP 505) may schedule a first PDSCH communication associated with a first DMRS port set having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 505, and a second DCI (e.g., sent by the second TRP 505) may schedule a second PDSCH communication associated with a second DMRS port set having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 505. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state corresponding to the DCI for the TRP 505. The TCI field of the DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates the first TCI state and the TCI field of the second DCI indicates the second TCI state).

[0076] In some aspects, techniques and apparatus associated with TA indication in RAR for inter-cell multi-TRP communication described herein may be combined with Figure 5 Used in conjunction with the multi-TRP communications described herein.

[0077] As indicated above, Figure 5 Other examples can be found in relation to Figure 5 The examples described are different.

[0078] Figure 6 is a diagram illustrating an example of TRP differentiation based at least in part on a CORESET pool index at a UE in accordance with the present disclosure. In some aspects, a CORESET pool index (or CORESETPoolIndex) value may be used by a UE (e.g., UE 120) to identify a TRP associated with an uplink grant received on a PDCCH.

[0079] A CORESET may refer to a control region that is structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a UE. In some aspects, a CORESET may occupy the first symbol of an orthogonal frequency division multiplexing (OFDM) slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols in the time domain. In 5G, the number of resources included in a CORESET may be flexibly configured, such as by using RRC signaling to indicate the frequency domain region (e.g., the number of resource blocks) or the time domain region (e.g., the number of symbols) of a CORESET.

[0080] like Figure 6 As illustrated, UE 120 may be configured to have multiple CORESETs in a given serving cell. Each CORESET configured for UE 120 may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for UE 120 may be associated with CORESET ID 1, a second CORESET configured for UE 120 may be associated with CORESET ID 2, a third CORESET configured for UE 120 may be associated with CORESET ID 3, and a fourth CORESET configured for UE 120 may be associated with CORESET ID 4.

[0081] like Figure 6 As further illustrated in , two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index value may be associated with a particular TRP 605. For example, Figure 6As illustrated, the first TRP 605 (TRP A) may be associated with CORESET pool index 0, and the second TRP 605 (TRP B) may be associated with CORESET pool index 1. The UE 120 may be configured with information identifying an association between a TRP and a CORESET pool index value assigned to the TRP via a higher layer parameter such as PDCCH-Config. Thus, the UE may identify the TRP that sent the DCI uplink grant by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI uplink grant was sent, determining the CORESET pool index value associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index value.

[0082] In some aspects, TRP differentiation at a UE based at least in part on a CORESET pool index may be utilized in conjunction with techniques and apparatus for TA indication in a RAR for inter-cell multiple TRP communication as described herein.

[0083] As indicated above, Figure 6 Other examples can be found in relation to Figure 6 The examples described are different.

[0084] Figure 7 1 is a diagram illustrating an example 700 of downlink and uplink transmissions between a network node 110 and a UE 120 in a wireless network 100 according to the present disclosure. In some examples, the downlink and / or uplink transmissions are based at least in part on a TA and / or a protection period between communications. As an example, the network node 110 may configure the downlink transmission to end before the guard period begins. As another example, the UE 120 may advance the start time of the uplink transmission based at least in part on the TA.

[0085] As shown by reference numeral 702-1, network node 110 may begin downlink transmission 704-1 to UE 120 at a first point in time. In some examples, the first point in time may be based at least in part on a timing scheme defined by a telecommunication system and / or a telecommunication standard. For illustration, a telecommunication standard may define various time divisions for scheduling transmissions between devices. As an example, a timing scheme may define radio frames (sometimes referred to as frames), wherein each radio frame has a predetermined duration (e.g., 10 milliseconds (ms)). Each radio frame may be further divided into a group of Z (Z ≥ 1) subframes, wherein each subframe may have a predetermined duration (e.g., 1 ms). Each subframe may be further divided into a group of time slots and / or each time slot may include a group of L symbol periods (e.g., fourteen symbol periods, seven symbol periods, or another number of symbol periods). Therefore, the first point in time shown by reference numeral 702-1 may be based at least in part on a time division (e.g., frame, subframe, time slot, mini-time slot, and / or symbol) defined by a telecommunication system.

[0086] In some examples, the network node 110 and the UE 120 may communicate wirelessly with each other (e.g., directly or via one or more network nodes) based at least in part on the defined time division. However, each device may have a different timing reference for the time division. For illustration, and as shown by reference numeral 702-1, the network node 110 may start a downlink transmission 704-1 at a specific time point, which may be associated with the defined time division based at least in part on the time angle of the network node 110. For example, the network node 110 may associate the specific time point with the defined time division (such as the start of a symbol, the start of a time slot, the start of a subframe, and / or the start of a frame). However, the downlink transmission may cause a propagation delay 706 in time, such as a time delay of the downlink transmission traveling between the network node 110 (e.g., RU) and the UE 120, at least in part. As shown by reference numeral 702-2, UE 120 may receive downlink transmission 704-2 (corresponding to downlink transmission 704-1 transmitted by network node 110) at a second point in time that is later in time relative to the first point in time. However, from the time perspective of UE 120, UE 120 may associate the second physical point in time shown by reference numeral 702-2 with the same specific point in time of the defined time partition as network node 110 (e.g., the start of the same symbol, the start of the same mini-slot, the start of the same slot, the start of the same subframe, and / or the start of the same frame). Therefore, as shown in example 700, the time perspective of UE 120 may be delayed in time from the time perspective of network node 110.

[0087] In wireless communication technologies such as 4G / LTE and 5G / NR, a TA value is used to control the timing of uplink transmissions of a UE (e.g., UE 120, etc.) so that a network node 110 (e.g., RU) receives the uplink transmission at a time that is aligned with the internal timing of the network node 110. The network node 110 may determine a TA value to the UE (e.g., directly or via one or more network nodes) by measuring the time difference between the reception of the uplink transmission from the UE and the subframe timing used by the network node 110 (e.g., by determining the difference between when the uplink transmission was assumed to have been received by the network node 110 according to the subframe timing and when the uplink transmission was actually received). The network node 110 may send a TA command (TAC) to command the UE to send future uplink communications earlier or later, thereby reducing or eliminating the time difference and aligning the timing between the UE and the network node 110. The TA command is used to offset the timing difference between the UE and the network node 110 due to different propagation delays that occur when the UE is at different distances from the network node 110. If the TA command is not used, uplink transmissions from different UEs (eg, located at different distances from the network node 110) may collide due to mistiming even if the uplink transmissions are scheduled for different subframes.

[0088] For illustration, without adjusting the start time of the uplink transmission, the UE 120 may be configured to start the uplink transmission at the scheduled time point based at least in part on the defined time division as described elsewhere herein. As shown by reference numeral 710-1, the start of the scheduled time point may occur at a third physical time point based at least in part on the timing angle of the UE 120. However, and as shown by reference numeral 710-2, the scheduled time point with reference to the timing angle of the network node 110 (e.g., RU) may occur at a fourth physical time point that occurs before the third physical time point as shown by reference numeral 710-1. Therefore, the network node 110 may command the UE 120 (e.g., directly or via one or more network nodes) to apply the timing advance 708 to the uplink transmission to better align the reception of the uplink transmission with the timing angle of the network node 110. However, in some examples, the fourth time point shown by reference numeral 710-2 may occur at or near the same physical time point as the third time point shown by reference numeral 710-1, such that uplink transmission from UE 120 to network node 110 causes propagation delay 706. In such a scenario, network node 110 may command UE 120 to apply a timing advance having a time duration corresponding to propagation delay 706.

[0089] As shown in example 700, UE 120 may adjust the start time of uplink transmission 712-1 based at least in part on timing advance 708 and the start of the scheduled time point (e.g., at a third physical time point shown by reference numeral 710-1). Based at least in part on the propagation delay, network node 110 may receive uplink transmission 712-2 (corresponding to uplink transmission 712-1 sent by UE 120) at a fourth physical time point shown by reference numeral 710-2.

[0090] In some examples, the timing advance value may be based at least in part on twice the estimated propagation delay (e.g., propagation delay 706) and / or may be based at least in part on a round trip time (RTT). The network node 110 (e.g., DU or CU) may estimate the propagation delay and / or select the timing advance value based at least in part on communication with the UE 120. As an example, the network node 110 may estimate the propagation delay based at least in part on a network access request message from the UE 120. Additionally or alternatively, the network node 110 may estimate and / or select the timing advance value from a set of fixed timing advance values.

[0091] In some examples, the telecommunications system and / or telecommunications standard may define a protection period 714 (e.g., a time duration) between transmissions to provide sufficient time for the device to switch between different transmission and / or reception modes, for transient stability, and to provide margin for timing misalignment and / or propagation delays between devices. In some examples, a protection period is a period during which no transmission or reception is scheduled and / or allowed to occur. The protection period can provide the device with sufficient time to reconfigure the hardware and / or allow the hardware to stabilize within a threshold to enable subsequent transmissions. The protection period 714 may sometimes be referred to as a gap, a switching protection period, or a guard interval.

[0092] In some examples, the network node 110 (e.g., DU or CU) may select the start transmission time and / or the transmission time duration based at least in part on the receiving device and / or the protection period. For example, the network node 110 may select the amount of content (e.g., data and / or control information) to be sent in the downlink transmission 704-1 based at least in part on starting the transmission at the first time point shown by reference numeral 702-1 and / or the UE 120 completing the reception of the downlink transmission 704-2 before the start point of the protection period 714. Alternatively or additionally, the UE 120 may select the amount of content (e.g., data and / or control information) to be sent in the uplink transmission 712-1 based at least in part on the timing advance 708, the third time point shown by reference numeral 710-1, and / or avoiding starting the uplink transmission 712-1 until the protection period 714 has ended.

[0093] In some aspects, techniques and apparatus associated with TA indication in RAR for inter-cell multi-TRP communication described herein may be combined with Figure 7 The described TA applies in association.

[0094] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.

[0095] As described above, multi-TRP communication enables the UE to communicate with multiple (different) TRPs. In fact, different TRPs communicating with the same UE may be associated with the same physical cell identifier (PCI) or with different PCIs. Multi-TRP communication when different TRPs communicating with the same UE are associated with the same PCI is called intra-cell multi-TRP communication. Multi-TRP communication when different TRPs communicating with the same UE are associated with different PCIs is called inter-cell multi-TRP communication. It is worth noting that in the case of inter-cell multi-TRP communication, from the perspective of the UE, multi-TRP communication is defined in the UE's serving cell, and the UE knows only one PCI - the PCI associated with the serving cell (e.g., the cell acquired during cell search).

[0096] With respect to inter-cell multi-TRP communication, the maximum number of additional PCIs (e.g., PCIs in addition to the PCI of the serving cell) for each component carrier, denoted as X, may be reported as UE capabilities. The UE may support two independent values ​​(X1 and X2) of X, which may be reported as UE capabilities for two different assumptions regarding the additional synchronization signal block (SSB) time domain position and periodicity with respect to the SSB of the serving cell. Here, the value of X1 represents the maximum number of additional PCIs that can be configured when each configuration of the SSB time domain position and periodicity of the additional PCI is assumed to be the same as the configuration of the SSB of the serving cell. In contrast, the value of X2 represents the maximum number of additional PCIs that can be configured when the configuration of the SSB time domain position and periodicity of the additional PCI is not assumed to be the same as the configuration of the SSB of the serving cell. By definition, scenarios supporting the use of X1 and X2 cannot occur simultaneously. The additional PCI may be configured via RRC signaling, and the number of configurable additional PCIs may be one to seven from the perspective of the RRC signal. In addition, for inter-cell multi-TRP operation, the center frequency, subcarrier spacing (SCS), and system frame number (SFN) offset of the SBS of the serving cell and the configured SBS with a different PCI from the serving cell are assumed to be the same. In some aspects, an indicator (e.g., provided via RRC signaling) may be used to indicate non-serving cell information associated with TCI status / QCL information. Here, the indicator may be different from the value of the PCI.

[0097] At least for the purpose of quasi co-location (QCL) indication, a UE may be configured (e.g., via RRC signaling) with up to M (e.g., M=128) candidate transmission configuration indicator (TCI) states. It is noteworthy that, although these TCI states are configured in a PDSCH configuration (e.g., PDSCH-Config), a given TCI state (e.g., associated with a given TCI-StateId) may be used to configure TCI states for resource types other than PDSCH resources (such as CORESET, non-zero power channel state information reference signal (NZP-CSI-RS) resources, physical uplink control channel (PUCCH) resources, or sounding reference signal (SRS) resources, etc.). For PDSCH, a MAC control element (MAC-CE) may be used to activate up to 2 of the M configured TCI states for a QCL indication for a given CORESET pool index (e.g., CORESETPoolIndex). N TCI states. Here, the N (e.g., N=3) bits carried in the DCI can be used to dynamically indicate the TCI state in the activated TCI state to be used in association with the PDSCH communication. For the PDCCH, the MAC-CE can be used to activate one TCI state among the M configured TCI states. It is worth noting that for multi-TRP communications based on multi-DCI, the PDSCH is associated with the CORESET pool index of the CORESET in which the DCI indicating the TCI state is received.

[0098] In addition, a PCI may be associated with a CORESET pool index. The PCI of a serving cell is always associated with an active TCI state, and only one additional PCI may be associated with an active TCI state. For inter-cell multi-TRP, one PCI associated with one or more activated TCI states (for PDSCH / PDCCH reception) is associated with one CORESET pool index, and another PCI associated with one or more activated TCI states (for PDSCH / PDCCH reception) is associated with another CORESET pool index.

[0099] In some wireless communication systems, two TAs may be specified for uplink multi-DCI based multi-TRP communications. In such a scenario, different TRPs may have different TA values. For inter-cell multi-DCI multi-TRP communications, the UE and the network node need to know the uplink TA for sending uplink communications associated with a TRP associated with an additional PCI (e.g., a PCI different from the PCI of the UE's serving cell).

[0100] Some aspects described herein provide techniques and apparatus for TA indication in a RAR for multi-TRP communications between cells. In some aspects, a UE may send a physical random access channel (PRACH) communication associated with an additional PCI (e.g., a PCI different from the PCI of the UE's serving cell). The UE may then receive a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI. In this way, the UE and the network node may understand an uplink TA that may be used to send uplink communications associated with a TRP associated with the additional PCI, thereby improving the reliability and performance of multi-TRP communications between cells. Additional details are provided below.

[0101] Fig. 8A and Figure 8B 8 are diagrams respectively illustrating examples 800a and 800b associated with TA indication in RAR for inter-cell multi-TRP communication according to the present disclosure. Fig. 8A and Figure 8B As shown, examples 800a and 800b include communications between a UE 802, a serving cell PCI 804, an additional PCI 806, and a special cell (SpCell) PCI 808. In some aspects, the UE 802, the serving cell PCI 804, the additional PCI 806, and the SpCell PCI 808 may be included in a wireless network, such as the wireless network 100. The UE 802, the serving cell PCI 804, the additional PCI 806, or the SpCell PCI 808 may communicate via one or more wireless access links (which may include uplinks and downlinks) or one or more backhaul links.

[0102] UE 802 may correspond to UE 120 or one or more other wireless communication devices described herein.

[0103] The serving cell PCI 804 may correspond to a serving cell of the UE 120. In some aspects, the serving cell may be a special cell (SpCell) of the UE 120 (e.g., a primary cell (Pcell) of the UE 120 or a primary secondary cell (Pcell) of the UE 120) or a secondary cell (Scell) of the UE 120. In some aspects, the serving cell PCI 804 may correspond to a cell supported by one or more network nodes 110, one or more TRPs 435, one or more TRPs 505, one or more TRPs 606, or one or more other wireless communication devices described herein.

[0104] The additional PCI 806 may correspond to a cell having a PCI different from the PCI of the serving cell of the UE 802. In some aspects, the additional PCI 806 may be configured in a SpCell of the UE 802 or in a Scell ​​of the UE 802. In some aspects, the additional PCI 806 may correspond to a cell supported by one or more network nodes 110, one or more TRPs 435, one or more TRPs 505, one or more TRPs 606, or one or more other wireless communication devices described herein.

[0105] The SpCell PCI 808 may correspond to the SpCell of the UE 802. The SpCell of the UE 802 may be, for example, a Pcell of the UE 802 or a PSCell of the UE 802. In some aspects, the SpCell PCI 808 may correspond to a cell supported by one or more network nodes 110, one or more TRPs 435, one or more TRPs 505, one or more TRPs 606, or one or more other wireless communication devices described herein. In some aspects, if the serving cell of the UE 802 is the SpCell of the UE 802, the serving cell PCI 804 may be the same as the SpCell PCI 808.

[0106] Fig. 8A An example 800a is illustrated in which the additional PCI 806 is activated when the UE 802 sends a PRACH communication associated with the additional PCI 806.

[0107] like Fig. 8A As shown in reference numeral 810, UE 802 and serving cell PCI 804 may establish an RRC connection. That is, UE 802 and a TRP associated with a serving cell of UE 802 (e.g., a TRP of a serving cell supporting UE 802, which corresponds to serving cell PCI 804) may establish an RRC connection.

[0108] As indicated by reference numeral 812, after establishing the RRC connection, UE 802 may send a measurement report and serving cell PCI 804 may receive the measurement report. That is, UE 802 may perform one or more measurements based at least in part on the SSB configuration associated with the serving cell and one or more additional PCIs (e.g., non-serving cells) of UE 802, and may report results of the one or more measurements (e.g., one or more Layer 1 (L1) RSRP values) to TRP associated with the serving cell.

[0109] As indicated by reference numeral 814, the serving cell PCI 804 may send a PDCCH order, and the UE 802 may receive the PDCCH order, wherein the PDCCH order indicates a PRACH configuration associated with the additional PCI 806. For example, a TRP associated with a serving cell of the UE 802 may determine, based at least in part on the measurement report, that the additional PCI 806 is to be configured or activated for the UE 802. In some aspects, the serving cell PCI 804 may trigger a contention-free random access (CFRA) to the additional PCI 806 by sending a PDCCH order to the UE 802 indicating the PRACH configuration associated with the additional PCI 806.

[0110] As shown by reference numeral 816, UE 802 may send PRACH communications associated with additional PCI 806, and additional PCI 806 may receive the PRACH communications. That is, UE 802 may send PRACH communications associated with additional PCI 806, and a TRP corresponding to additional PCI 806 may receive the PRACH communications. In some aspects, UE 802 sends PRACH communications based at least in part on a PDCCH order. That is, in some aspects, the PDCCH order may trigger UE 802 to provide PRACH communications associated with additional PCI 806.

[0111] As shown in reference numeral 818, the SpCell 808 may send a RAR message in response to the PRACH communication associated with the additional PCI, and the UE 802 may receive the RAR message. That is, the TRP supporting the SpCell corresponding to the SpCell PCI 808 may send a RAR message in response to the PRACH communication associated with the additional PCI 806, and the UE 802 may receive the RAR message.

[0112] In some aspects, the RAR message indicates TA information associated with the additional PCI 806. For example, the RAR message may indicate TA information (e.g., TA value, TA command, etc.) associated with the additional PCI 806. In some aspects, the TA information indicates a TA to be applied for uplink communications associated with the additional PCI 806.

[0113] In example 800a, as shown by reference numeral 820a, the additional PCI 806 is activated before the UE 802 sends a PRACH communication associated with the additional PCI 806. That is, in example 800a, the additional PCI 806 is associated with one or more active TCI states before the PRACH communication. In other words, the additional PCI 806 is active when the UE 802 sends a PRACH communication associated with the additional PCI 806.

[0114] In some aspects, the UE 802 may apply the TA information in association with sending uplink communications based at least in part on the additional PCI 806 being associated with one or more active TCI states when sending PRACH communications associated with the additional PCI 806. For example, as indicated by reference numeral 822, the UE 802 may apply the TA information within a processing timeline after receiving the RAR message indicating the TA information, such that the UE 802 applies the TA information to uplink communications sent by the UE 802.

[0115] Figure 8B Example 800b is illustrated in which additional PCI 806 is not activated when UE 802 sends PRACH communications associated with additional PCI 806. Operations associated with reference numerals 810, 812, 814, 816, and 818 as shown in example 800b may be similar to those described above in conjunction with example 800a.

[0116] However, in example 800b, as shown by reference numeral 820b, the additional PCI 806 is not activated before the UE 802 sends a PRACH communication associated with the additional PCI 806. That is, in example 800b, the additional PCI 806 is not associated with one or more active TCI states when the UE 802 sends the PRACH communication.

[0117] In some aspects, if the additional PCI 806 is not associated with any active TCI state, the UE 802 may store the TA information indicated in the RAR message. In some aspects, the UE 802 may store the TA information for a time period defined by the TA information window 824. The TA information window 824 corresponds to a time period during which the UE 802 is valid. In some aspects, once the TA information window 824 has elapsed, the UE 802 may determine that the TA information has expired. That is, the UE 802 may discard the TA information upon determining that the TA information window has elapsed.

[0118] For example, in example 800b, UE 802 may determine, based at least in part on TA information window 824, that TA information has not expired when additional PCI 806 is activated. In this scenario, as shown by reference numeral 820b, additional PCI 806 is activated before the end of TA information window 824. That is, within TA information window 824 (i.e., before TA information expires), additional PCI 806 is associated with one or more active TCI states. Therefore, as shown by reference numeral 822, UE 802 may apply TA information within a processing timeline after receiving a RAR message indicating TA information, so that UE 802 applies TA information to uplink communications sent by UE 802.

[0119] In some aspects, the UE 802 may determine that the TA information has expired based at least in part on the TA information window 824. That is, the UE 802 may determine that the TA information has expired while the additional PCI 806 is not activated. In this scenario, the additional PCI 806 is not activated before the end of the TA information window 824. In some aspects, the UE 802 may discard the TA information based at least in part on determining that the additional PCI 806 is not associated with any active TCI state before the TA information expires.

[0120] In some aspects, the start of the TA information window 824 is at the end of PRACH communications associated with the additional PCI 806. Additionally or alternatively, the start of the TA information window 824 is at the end of reception of a RAR message (e.g., end of RAR PDSCH reception). In some aspects, the duration of the TA information window 824 is pre-configured on the UE 802 according to a wireless communication standard. In some aspects, the duration of the TA information window 824 is configured on the UE 802 by a network node (e.g., network node 110).

[0121] In some aspects, the UE 802 may send UE capability information indicating a maximum number of TA information items that may be stored by the UE 802 for a single cell. Additionally or alternatively, the UE 802 may send UE capability information indicating a maximum number of TA information items that may be stored by the UE 802 for multiple cells.

[0122] It is noteworthy that for RAR messaging, a Type 1 common search space (CSS) may be configured only in the SpCell of UE 802, and therefore, RAR messages are sent from the SpCell. In addition, when the active TCI state is associated with the additional PCI 806, the UE 802 may not be configured to monitor the Type 1 CSS. Therefore, some inter-TRP coordination is required so that TA information (measured in the TRP associated with the additional PCI 806) can be obtained by the SpCell. In some aspects, after receiving the PRACH communication, the additional PCI 806 (e.g., a TRP supporting a cell corresponding to the additional PCI 806) may send TA information associated with the additional PCI 806 to the SpCell PCI 808 (e.g., a TRP supporting the SpCell of UE 802). Thus, in some aspects, as shown in examples 800a and 800b, SpCell PCI 808 can send RAR messages on the SpCell of UE 802, and UE 802 can receive RAR messages on the SpCell of UE 802. In some aspects, the SpCell of UE 802 can be a Pcell of UE 802 or a PSCell of UE 802.

[0123] With respect to RAR monitoring performed by UE 802 (e.g., monitoring performed in association with receiving a RAR message including a TA), the RAR monitoring window may start at the first symbol of the earliest CORESET in which the UE 802 is configured to receive PDCCH communications of a type 1 PDCCH CSS set, which is at least one symbol after the last symbol of a PRACH opportunity corresponding to a PRACH communication sent by the UE 802. Here, the symbol duration may correspond to the SCS of the type 1 PDCCH CSS set. Such a RAR monitoring window is referred to herein as a first RAR monitoring window. However, for non-ideal backhaul, inter-TRP coordination may require a certain amount of delay, which means that a certain amount of delay may be required between the PRACH communication and the type 1 PDCCH communication provided on the SpCell.

[0124] Thus, in some aspects, the UE 802 may be configured such that the start of the RAR monitoring window is at the first symbol of the earliest CORESET, which is at least a specific amount of time after the end of the PRACH opportunity corresponding to the PRACH communication associated with the additional PCI 806. Such a RAR monitoring window is referred to herein as a second RAR monitoring window. In some aspects, the specific amount of time corresponds to a specific number of symbols, a specific number of time slots, or a specific number of milliseconds. In some aspects, a specific amount of time is configured for each additional PCI 806. In some aspects, a specific amount of time is associated with multiple additional PCIs 806. In some aspects, the duration of the RAR monitoring window is configured for each additional PCI.

[0125] In some aspects, the UE 802 may perform monitoring during the second RAR monitoring window (eg, the UE 802 may avoid performing RAR monitoring in a legacy RAR monitoring window (eg, the first RAR monitoring window)).

[0126] In some aspects, the UE 802 may perform monitoring during both the first RAR monitoring window and the second RAR monitoring window (eg, the UE 802 may perform RAR monitoring in both a legacy RAR monitoring window and a RAR monitoring window that includes an amount of delay, as described above).

[0127] In some aspects, the UE 802 may perform monitoring during a first RAR monitoring window, and may selectively perform monitoring during a second RAR monitoring window based at least in part on the monitoring results during the first RAR monitoring window. For example, the UE 802 may perform monitoring during the first monitoring window. Here, if the UE 802 does not detect a PDCCH communication scrambled by a random access radio network temporary identifier (RA-RNTI) associated with a PRACH opportunity corresponding to a PRACH communication during the first RAR monitoring window, the UE 802 may perform monitoring during the second RAR window. On the contrary, if the UE 802 detects a PDCCH communication scrambled by a RA-RNTI associated with a PRACH opportunity corresponding to a PRACH communication during the first RAR monitoring window, the UE 802 may avoid performing monitoring during the second RAR window. In some aspects, the UE 802 may send UE capability information indicating whether the UE 802 supports monitoring RAR messages in multiple RAR monitoring windows.

[0128] In some aspects, as described above, the additional PCI 806 may be active when the UE 802 sends PRACH communications associated with the additional PCI 806. In addition, in some aspects, the additional PCI 806 may be configured on the SpCell PCI 808. In such a scenario, a PDCCH command may be sent after the TCI state associated with the additional PCI 806 is activated (i.e., after the additional PCI 806 is activated), and then a PDCCH command may be sent in the CORESET when the active TCI state is associated with the additional PCI 806 (i.e., the PDCCH command may be sent from the additional PCI 806). However, when the active TCI state is associated with the additional PCI, the UE 802 may not be configured to monitor the Type 1 CSS. Under such conditions, in order to indicate the TA information associated with the additional PCI 806, a RAR message may be sent from the SpCell (e.g., the cell corresponding to the SpCell PCI 808). Here, if CFRA is triggered on the SpCell (i.e., when a PDCCH command is sent from an additional PCI configured on the SpCell), then (1) the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDCCH associated with the RAR message (e.g., a PDCCH of DCI format 1_0 including a cyclic redundancy check (CRC) scrambled by the RA-RNTI associated with the PRACH opportunity corresponding to the PRACH communication sent by the UE 802), and (2) the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDSCH scheduled by the PDCCH associated with the RAR message (e.g., a PDSCH scheduled with the RA-RNTI associated with the PRACH opportunity corresponding to the PRACH communication sent by the UE 802). Therefore, the QCL assumption needs to be defined for the following scenario: CFRA is triggered on the SpCell by a PDCCH command sent from the additional PCI 806, and the RAR message is sent on the SpCell.

[0129] Thus, in some aspects, the UE 802 may receive a PDCCH command in a CORESET, wherein an active TCI state of the CORESET is associated with an additional PCI 806, wherein the PDCCH command triggers PRACH communication associated with the additional PCI 806, and the additional PCI 806 is configured in a SpCell (e.g., a Pcell of the UE 802 or a PSCell of the UE 802). In this scenario, the UE 802 may determine that the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDCCH associated with the RAR message. The UE 802 may also determine that the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDSCH scheduled by the PDCCH associated with the RAR message. Here, UE 802 may receive the RAR message based at least in part on the assumption that (1) the DMRS QCL characteristics of the CORESET associated with the type-1 PDCCH CSS set will be used to receive the PDCCH associated with the RAR message, and (2) the QCL assumption of the PDSCH scheduled by the PDCCH associated with the RAR message matches the QCL assumption of the CORESET associated with the type-1 PDCCH CSS set used to receive the PDCCH associated with the RAR message.

[0130] As indicated above, Fig. 8A and Figure 8B Other examples can be found in the Fig. 8A and Figure 8B The examples described are different.

[0131] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a UE according to the present disclosure. Example process 900 is an example in which a UE (eg, UE 120, UE 802, etc.) performs operations associated with TA indication in a RAR for inter-cell multi-TRP communication.

[0132] like Fig. 9 As shown, in some aspects, process 900 may include sending a PRACH communication associated with an additional PCI that is a different PCI than a PCI of a serving cell of the UE (block 910). Fig.10 The communication manager 140 and / or the sending component 1004 depicted in FIG. 1004 may send a PRACH communication associated with an additional PCI, which is a PCI different from the PCI of the UE's serving cell, as described above.

[0133] like Fig. 9As further shown, in some aspects, process 900 may include receiving a RAR message in response to a PRACH communication associated with an additional PCI, wherein the RAR message indicates TA information associated with the additional PCI (block 920). Fig.10 The communication manager 140 and / or receiving component 1002 depicted in FIG. 1 may receive a RAR message in response to a PRACH communication associated with an additional PCI, wherein the RAR message indicates TA information associated with the additional PCI, as described above.

[0134] Process 900 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.

[0135] In a first aspect, additional PCIs are associated with one or more active TCI states.

[0136] In a second aspect, alone or in combination with the first aspect, further comprising: a processing timeline after receiving the RAR message indicating the TA information, applying the TA information in association with sending uplink communications.

[0137] In a third aspect, the additional PCI is not associated with any active TCI state.

[0138] In a fourth aspect, alone or in combination with the third aspect, process 900 includes: storing TA information indicated in a RAR message; determining that the TA information has not expired based at least in part on a TA information window; and applying the TA information in association with sending uplink communications based at least in part on determining that the TA information has not expired and determining that an additional PCI is associated with one or more active TCI states before the TA information expires.

[0139] In a fifth aspect, alone or in combination with one or more of the third and fourth aspects, process 900 includes: storing TA information indicated in a RAR message; determining that the TA information has expired based at least in part on a TA information window; and discarding the TA information based at least in part on determining that the TA information has expired and determining that an additional PCI was not associated with any active TCI state before the TA information expired.

[0140] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes selectively discarding TA information based at least in part on a TA information window.

[0141] In a seventh aspect, in combination with the sixth aspect, the start of the TA information window is at the end of a PRACH communication associated with the additional PCI.

[0142] In an eighth aspect, in combination with the sixth aspect, the start of the TA information window is at the end of reception of the RAR message.

[0143] In a ninth aspect, alone or in combination with one or more of the sixth to eighth aspects, the duration of the TA information window is pre-configured on the UE according to a wireless communication standard.

[0144] In a tenth aspect, alone or in combination with one or more of the sixth to ninth aspects, a duration of a TA information window is configured on a UE by a network node.

[0145] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 900 includes sending UE capability information indicating at least one of a maximum number of TA information items that can be stored by the UE for a single cell or a maximum number of TA information items that can be stored by the UE for multiple cells.

[0146] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a RAR message is received on a Pcell of the UE or a PScell ​​of the UE.

[0147] In a thirteenth aspect, alone or in combination with one or more of aspects one to twelfth, a RAR message is received based at least in part on performing monitoring during a RAR monitoring window, wherein the start of the RAR monitoring window is at a first symbol of an earliest CORESET, which is at least a specific amount of time after the end of a PRACH opportunity corresponding to a PRACH communication associated with an additional PCI.

[0148] In a fourteenth aspect, in combination with the thirteenth aspect, the specific amount of time corresponds to a specific number of symbols, a specific number of time slots, or a specific number of milliseconds.

[0149] In a fifteenth aspect, either alone or in combination with one or more of the thirteenth to fourteenth aspects, a specific amount of time is configured for each additional PCI.

[0150] In a sixteenth aspect, alone or in combination with one or more of the thirteenth to fifteenth aspects, a particular amount of time is associated with a plurality of additional PCIs.

[0151] In a seventeenth aspect, alone or in combination with one or more of the thirteenth to sixteenth aspects, a duration of a RAR monitoring window is configured for each additional PCI.

[0152] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the process 900 includes performing monitoring during both the first RAR monitoring window and the second RAR monitoring window.

[0153] In a nineteenth aspect, alone or in combination with one or more of aspects one to seventeen, process 900 includes: performing monitoring during a first RAR monitoring window; and selectively performing monitoring during a second RAR monitoring window based at least in part on the monitoring results during the first RAR monitoring window.

[0154] In the twentieth aspect, in combination with the nineteenth aspect, selectively performing monitoring during the second RAR monitoring window includes performing monitoring during the second RAR window based at least in part on PDCCH communications scrambled by an RA-RNTI associated with a PRACH opportunity corresponding to a PRACH communication not detected during the first RAR monitoring window.

[0155] In the twenty-first aspect, in combination with the nineteenth aspect, selectively performing monitoring during the second RAR monitoring window includes avoiding performing monitoring during the second RAR window based at least in part on PDCCH communications scrambled by RA-RNTI associated with a PRACH opportunity corresponding to a PRACH communication detected during the first RAR monitoring window.

[0156] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, process 900 includes sending UE capability information indicating whether the UE supports monitoring RAR messages in multiple RAR monitoring windows.

[0157] In the twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, process 900 includes: receiving a PDCCH command in a CORESET, the active TCI state of the CORESET being associated with an additional PCI, wherein the PDCCH command triggers PRACH communication associated with the additional PCI, and wherein the additional PCI is configured in a Pcell of the UE or a PScell ​​of the UE; determining that a DMRS QCL characteristic of the PDCCH command does not match a DMRS QCL characteristic of a PDCCH associated with a RAR message; and determining that the DMRS QCL characteristic of the PDCCH command does not match a DMRS QCL characteristic of a PDSCH scheduled by the PDCCH associated with the RAR message.

[0158] In a twenty-fourth aspect, in combination with the twenty-third aspect, a RAR message is received based at least in part on the assumption that a DMRS QCL characteristic of a CORESET associated with a type-1 PDCCH CSS set will be used to receive a PDCCH associated with the RAR message, and that a QCL assumption of a PDSCH scheduled by the PDCCH associated with the RAR message matches a QCL assumption of a CORESET associated with a type-1 PDCCH CSS set for receiving the PDCCH associated with the RAR message.

[0159] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks of the blocks of process 900 may be performed in parallel.

[0160] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include a TA information component 1008, among other things.

[0161] In some aspects, the apparatus 1000 may be configured to perform Fig. 8A and Figure 8B Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.10 The device 1000 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.10 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 implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0162] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 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 apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0163] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 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 1006. In some aspects, the transmitting component 1004 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 1004 can be co-located with the receive component 1002 in a transceiver.

[0164] The transmitting component 1004 can transmit a PRACH communication associated with an additional PCI, the additional PCI being a PCI different from a PCI of a serving cell of the UE. The receiving component 1002 can receive a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI.

[0165] The TA information component 1008 can store the TA information indicated in the RAR message.

[0166] The TA information component 1008 can determine that the TA information has not expired based at least in part on the TA information window.

[0167] The TA information component 1008 can apply the TA information in association with transmitting the uplink communication based at least in part on determining that the TA information has not expired and determining that the additional PCI is associated with one or more active TCI states before the TA information expires.

[0168] The TA information component 1008 can determine that the TA information has expired based at least in part on the TA information window.

[0169] The TA information component 1008 can discard the TA information based at least in part on determining that the TA information has expired and determining that the additional PCI was not associated with any active TCI state prior to the expiration of the TA information.

[0170] Transmitting component 1004 can transmit UE capability information indicating at least one of a maximum number of TA information items that can be stored by the UE for a single cell or a maximum number of TA information items that can be stored by the UE for multiple cells.

[0171] The receiving component 1002 can perform monitoring during both the first RAR monitoring window and the second RAR monitoring window.

[0172] The receiving component 1002 can perform monitoring during a first RAR monitoring window.

[0173] The receiving component 1002 can selectively perform monitoring during the second RAR monitoring window based at least in part on the monitoring results during the first RAR monitoring window.

[0174] The sending component 1004 can send UE capability information indicating whether the UE supports monitoring RAR messages in multiple RAR monitoring windows.

[0175] The receiving component 1002 can receive a PDCCH order in a CORESET whose active TCI state is associated with an additional PCI, wherein the PDCCH order triggers a PRACH communication associated with the additional PCI, and wherein the additional PCI is configured in a Pcell of the UE or a PScell ​​of the UE.

[0176] Receiving component 1002 can determine that a DMRS QCL characteristic of the PDCCH command does not match a DMRS QCL characteristic of the PDCCH associated with the RAR message.

[0177] Receiving component 1002 can determine that a DMRS QCL characteristic of the PDCCH command does not match a DMRS QCL characteristic of a PDSCH scheduled by a PDCCH associated with the RAR message.

[0178] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The collection of (one or more) components shown in can perform the operations described by Fig.10 Another collection of components shown in FIG. 1 performs one or more functions.

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

[0180] Aspect 1: A method of wireless communication performed by a UE, the method comprising: sending a PRACH communication associated with an additional PCI, wherein the additional PCI is a PCI different from the PCI of a serving cell of the UE; and receiving a RAR message in response to the PRACH communication associated with the additional PCI, wherein the RAR message indicates TA information associated with the additional PCI.

[0181] Aspect 2: The method according to aspect 1, wherein the additional PCI is associated with one or more active TCI states.

[0182] Aspect 3: The method according to aspect 1, further comprising: applying the TA information in association with sending uplink communication at a processing timeline after receiving the RAR message indicating the TA information.

[0183] Aspect 4: The method according to aspect 1, wherein the additional PCI is not associated with any active TCI state.

[0184] Aspect 5: According to the method described in Aspect 1, the method also includes: storing the TA information indicated in the RAR message; determining that the TA information has not expired based at least in part on a TA information window; and applying the TA information in association with sending uplink communications based at least in part on determining that the TA information has not expired and determining that the additional PCI is associated with one or more active TCI states before the TA information expires.

[0185] Aspect 6: According to the method described in Aspect 1, the method also includes: storing the TA information indicated in the RAR message; determining that the TA information has expired based at least in part on a TA information window; and discarding the TA information based at least in part on determining that the TA information has expired and determining that the additional PCI is not associated with any active TCI state before the TA information expires.

[0186] Aspect 7: The method according to aspect 1 further comprises selectively discarding the TA information based at least in part on a TA information window.

[0187] Aspect 8: The method according to aspect 7, wherein the start of the TA information window is when the PRACH communication associated with the additional PCI ends.

[0188] Aspect 9: The method according to aspect 7, wherein the start of the TA information window is when the reception of the RAR message ends.

[0189] Aspect 10: The method according to aspect 7, wherein the duration of the TA information window is pre-configured on the UE according to a wireless communication standard.

[0190] Aspect 11: The method according to aspect 7, wherein the duration of the TA information window is configured on the UE by a network node.

[0191] Aspect 12: According to the method according to aspect 1, the method also includes sending UE capability information, the UE capability information indicating at least one of the maximum number of TA information items that can be stored by the UE for a single cell or the maximum number of TA information items that can be stored by the UE for multiple cells.

[0192] Aspect 13: The method according to Aspect 1, wherein the RAR message is received on a Pcell of the UE or a PScell ​​of the UE.

[0193] Aspect 14: A method according to Aspect 1, wherein the RAR message is received at least in part based on performing monitoring during a RAR monitoring window, wherein the start of the RAR monitoring window is at the first symbol of the earliest CORESET, and the earliest CORESET is at least a specific amount of time after the end of the PRACH opportunity corresponding to the PRACH communication associated with the additional PCI.

[0194] Aspect 15: The method according to aspect 14, wherein the specific amount of time corresponds to a specific number of symbols, a specific number of time slots, or a specific number of milliseconds.

[0195] Aspect 16: The method according to aspect 14, wherein the specific amount of time is configured for each additional PCI.

[0196] Aspect 17: The method according to aspect 14, wherein the specific amount of time is associated with a plurality of additional PCIs.

[0197] Aspect 18: The method according to aspect 14, wherein the duration of the RAR monitoring window is configured for each additional PCI.

[0198] Aspect 19: The method according to aspect 1, further comprising performing monitoring during both the first RAR monitoring window and the second RAR monitoring window.

[0199] Aspect 20: According to the method of aspect 1, the method also includes: performing monitoring during a first RAR monitoring window; and selectively performing monitoring during a second RAR monitoring window based at least in part on the monitoring results during the first RAR monitoring window.

[0200] Aspect 21: A method according to Aspect 20, wherein selectively performing monitoring during the second RAR monitoring window includes: performing monitoring during the second RAR window based at least in part on PDCCH communications encrypted by an RA-RNTI associated with a PRACH opportunity corresponding to the PRACH communication not detected during the first RAR monitoring window.

[0201] Aspect 22: A method according to Aspect 20, wherein selectively performing monitoring during the second RAR monitoring window includes: avoiding performing monitoring during the second RAR window based at least in part on PDCCH communications encrypted by an RA-RNTI associated with a PRACH opportunity corresponding to the PRACH communication detected during the first RAR monitoring window.

[0202] Aspect 23: According to the method of Aspect 1, the method also includes sending UE capability information, wherein the UE capability information indicates whether the UE supports monitoring the RAR message in multiple RAR monitoring windows.

[0203] Aspect 24: According to the method described in Aspect 1, the method further includes: receiving a PDCCH command in a CORESET, the active TCI state of the CORESET being associated with the additional PCI, wherein the PDCCH command triggers the PRACH communication associated with the additional PCI, and wherein the additional PCI is configured in the Pcell of the UE or the PScell ​​of the UE; determining that the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDCCH associated with the RAR message; and determining that the DMRS QCL characteristics of the PDCCH command do not match the DMRS QCL characteristics of the PDSCH scheduled by the PDCCH associated with the RAR message.

[0204] Aspect 25: A method according to Aspect 24, wherein the RAR message is received at least in part based on the following assumptions: the DMRS QCL characteristics of the CORESET associated with the type 1 PDCCH cyclic shift set will be used to receive the PDCCH associated with the RAR message; and the QCL assumption of the PDSCH scheduled by the PDCCH associated with the RAR message matches the QCL assumption of the CORESET associated with the type 1 PDCCH CSS set used to receive the PDCCH associated with the RAR message.

[0205] Aspect 26: 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 25.

[0206] Aspect 27: A device for wireless communication, the device comprising: a memory; and 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 25.

[0207] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 25.

[0208] Aspect 29: A non-transitory computer-readable medium storing 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 25.

[0209] Aspect 30: 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 device, cause the device to perform one or more of the methods described in aspects 1 to 25.

[0210] 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.

[0211] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of 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, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method 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 it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0212] 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.

[0213] 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 various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects 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, and 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).

[0214] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more entries and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries 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 entries and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: sending a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the UE; as well as receiving a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, The RAR message indicates timing advance (TA) information associated with the additional PCI.

2. The UE of claim 1, wherein the additional PCI is associated with one or more active transmission configuration indicator (TCI) states.

3. The UE according to claim 1, further comprising: At a processing timeline after receiving the RAR message indicating the TA information, the TA information is applied in association with transmitting uplink communications.

4. The UE of claim 1, wherein the additional PCI is not associated with any active transmission configuration indicator (TCI) state.

5. The UE of claim 1, wherein the one or more processors are further configured to: storing the TA information indicated in the RAR message; determining, based at least in part on the TA information window, that the TA information has not expired; and The TA information is applied in association with transmitting uplink communications based at least in part on determining that the TA information has not expired and determining that the additional PCI is associated with one or more active transmit configuration indicator (TCI) states prior to expiration of the TA information.

6. The UE of claim 1, wherein the one or more processors are further configured to: storing the TA information indicated in the RAR message; determining that the TA information has expired based at least in part on a TA information window; and The TA information is discarded based at least in part on determining that the TA information has expired and determining that the additional PCI was not associated with any active transmit configuration indicator (TCI) state prior to the expiration of the TA information. 7 . The UE of claim 1 , wherein the one or more processors are further configured to selectively discard the TA information based at least in part on a TA information window.

8. The UE according to claim 7, wherein the start of the TA information window is when the PRACH communication associated with the additional PCI ends.

9. The UE according to claim 7, wherein the start of the TA information window is when the reception of the RAR message ends.

10. The UE of claim 7, wherein the duration of the TA information window is preconfigured on the UE according to a wireless communication standard.

11. The UE of claim 7, wherein the duration of the TA information window is configured on the UE by a network node.

12. The UE of claim 1 , wherein the one or more processors are further configured to send UE capability information indicating at least one of a maximum number of TA information items that can be stored by the UE for a single cell or a maximum number of TA information items that can be stored by the UE for multiple cells.

13. The UE of claim 1, wherein the RAR message is received on a primary cell (Pcell) of the UE or a primary secondary cell (PScell) of the UE.

14. The UE of claim 1 , wherein the RAR message is received based at least in part on performing monitoring during a RAR monitoring window, wherein a start of the RAR monitoring window is at a first symbol of an earliest control resource set (CORESET), the earliest control resource set (CORESET) being at least a specific amount of time after an end of a PRACH opportunity corresponding to the PRACH communication associated with the additional PCI.

15. The UE of claim 14, wherein the specific amount of time corresponds to a specific number of symbols, a specific number of time slots, or a specific number of milliseconds.

16. The UE of claim 14, wherein the specific amount of time is configured for each additional PCI.

17. The UE of claim 14, wherein the specific amount of time is associated with a plurality of additional PCIs.

18. The UE of claim 14, wherein the duration of the RAR monitoring window is configured for each additional PCI.

19. The UE of claim 1, wherein the one or more processors are further configured to perform monitoring during both a first RAR monitoring window and a second RAR monitoring window.

20. The UE of claim 1, wherein the one or more processors are further configured to: performing monitoring during a first RAR monitoring window; and Monitoring is selectively performed during a second RAR monitoring window based at least in part on the monitoring results during the first RAR monitoring window.

21. The UE of claim 20, wherein to selectively perform monitoring during the second RAR monitoring window, the one or more processors are configured to: Monitoring is performed during the second RAR window based at least in part on a physical downlink control channel (PDCCH) communication scrambled by a random access radio network temporary identifier (RA-RNTI) associated with a PRACH opportunity corresponding to not detecting the PRACH communication during the first RAR monitoring window.

22. The UE of claim 20, wherein to selectively perform monitoring during the second RAR monitoring window, the one or more processors are configured to: Monitoring is avoided during the second RAR window based at least in part on a physical downlink control channel (PDCCH) communication scrambled by a random access radio network temporary identifier (RA-RNTI) associated with a PRACH opportunity corresponding to detecting the PRACH communication during the first RAR monitoring window.

23. The UE of claim 1, wherein the one or more processors are further configured to send UE capability information indicating whether the UE supports monitoring the RAR message in multiple RAR monitoring windows.

24. The UE of claim 1, wherein the one or more processors are further configured to: receiving a physical downlink control channel (PDCCH) command in a control resource set (CORESET), an active transmit configuration indicator (TCI) state of the CORESET being associated with the additional PCI, wherein the PDCCH command triggers the PRACH communication associated with the additional PCI, and wherein the additional PCI is configured in a primary cell (Pcell) of the UE or a primary secondary cell (PScell) of the UE; determining that a demodulation reference signal (DMRS) quasi co-location (QCL) characteristic of the PDCCH command does not match a DMRS QCL characteristic of a PDCCH associated with the RAR message; and It is determined that the DMRS QCL characteristic of the PDCCH command does not match a DMRS QCL characteristic of a physical downlink shared channel (PDSCH) scheduled by the PDCCH associated with the RAR message.

25. The UE of claim 24, wherein the RAR message is received based at least in part on the following assumptions: The DMRS QCL characteristics of the CORESET associated with a Type 1 PDCCH Common Search Space (CSS) set shall be used to receive the PDCCH associated with the RAR message; and A QCL assumption of the PDSCH scheduled by the PDCCH associated with the RAR message matches a QCL assumption of the CORESET associated with the Type-1 PDCCH CSS set used to receive the PDCCH associated with the RAR message.

26. A method of wireless communication performed by a user equipment (UE), the method comprising: sending a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the UE; as well as receiving a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, The RAR message indicates timing advance (TA) information associated with the additional PCI.

27. The method of claim 26, wherein the additional PCI is associated with one or more active transmit configuration indicator (TCI) states.

28. The method according to claim 26, further comprising: At a processing timeline after receiving the RAR message indicating the TA information, the TA information is applied in association with transmitting uplink communications.

29. The method of claim 26, wherein the additional PCI is not associated with any active transmit configuration indicator (TCI) state.

30. The method of claim 26, further comprising: storing the TA information indicated in the RAR message; determining, based at least in part on the TA information window, that the TA information has not expired; as well as The TA information is applied in association with transmitting uplink communications based at least in part on determining that the TA information has not expired and determining that the additional PCI is associated with one or more active transmit configuration indicator (TCI) states prior to expiration of the TA information.

31. The method of claim 26, further comprising: storing the TA information indicated in the RAR message; determining that the TA information has expired based at least in part on a TA information window; as well as The TA information is discarded based at least in part on determining that the TA information has expired and determining that the additional PCI was not associated with any active transmit configuration indicator (TCI) state prior to the expiration of the TA information.

32. The method of claim 26, further comprising selectively discarding the TA information based at least in part on a TA information window.

33. The method of claim 26, further comprising sending UE capability information indicating at least one of a maximum number of TA information items that can be stored by the UE for a single cell or a maximum number of TA information items that can be stored by the UE for multiple cells.

34. A non-transitory computer readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: sending a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the UE; as well as receiving a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, The RAR message indicates timing advance (TA) information associated with the additional PCI.

35. An apparatus for wireless communication, the apparatus comprising: means for transmitting a physical random access channel (PRACH) communication associated with an additional physical cell identifier (PCI), the additional PCI being a PCI different from a PCI of a serving cell of the apparatus; and means for receiving a random access response (RAR) message in response to the PRACH communication associated with the additional PCI, The RAR message indicates timing advance (TA) information associated with the additional PCI.

Images