RAR enhancements for inter-cell multi-TRP systems

Abstract

A user equipment (UE) may be configured to receive a first RRC configuration from a serving cell, the first RRC configuration including a first configuration of a first PCI and a second PCI. The serving cell may be associated with a first PCI, and an additional cell may be associated with the second PCI different from the first PCI. The UE may be configured to receive a PDCCH command from a network node, the PDCCH command including an indication of a PRACH transmission associated with the second PCI. The UE may be configured to transmit the PRACH transmission associated with the second PCI during a PRACH occasion. The UE may be configured to monitor at least one first CSS in the first CORESET during an RAR window associated with the second PCI. The RAR window may be based on a temporal location of the PRACH occasion.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to a multiple transmit-receive point (TRP) system with an additional PCI configured to send a random access response (RAR). Background Art

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

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory at a user equipment (UE). Based at least in part on information stored in the memory, the at least one processor may be configured to receive a first radio resource control (RRC) configuration from a serving cell, the first radio resource control (RRC) configuration including a first physical cell identifier (ID) (PCI) and a first configuration of a second PCI. The serving cell may be associated with a first PCI, and an additional cell may be associated with the second PCI different from the first PCI. Based at least in part on information stored in the memory, the at least one processor may be configured to receive a physical downlink control channel (PDCCH) command from a network node, the physical downlink control channel (PDCCH) command including an indication of a physical random access channel (PRACH) transmission associated with the second PCI. Based at least in part on information stored in the memory, the at least one processor may be configured to transmit the PRACH transmission associated with the second PCI during a PRACH opportunity. Based at least in part on the information stored in the memory, the at least one processor may be configured to monitor at least one first common search space (CSS) in a first control resource set (CORESET) during a random access response (RAR) window associated with the second PCI. The RAR window may be based on a temporal position of the PRACH opportunity.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory at a network entity. Based at least in part on information stored in the memory, the at least one processor may be configured to receive a configuration of at least one first CSS in a first CORESET associated with a second PCI from a serving cell. The serving cell may be associated with a first PCI different from the second PCI. The network node may be associated with the second PCI. Based at least in part on information stored in the memory, the at least one processor may be configured to send a PDCCH command to a UE, the PDCCH command including an indication of a PRACH transmission. Based at least in part on information stored in the memory, the at least one processor may be configured to receive the PRACH transmission associated with the second PCI from the UE during a PRACH opportunity. Based at least in part on information stored in the memory, the at least one processor may be configured to, in response to receiving the PRACH transmission, send a RAR message to the UE during a RAR window associated with the second PCI. The RAR window may be based on a temporal position of the PRACH opportunity.

[0007] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0010] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0011] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0012] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 is a diagram illustrating an example of a wireless communication system having multiple network nodes configured to communicate with a UE according to various aspects of the present disclosure.

[0015] Figure 5 is a connection flow diagram illustrating an example of a wireless communication system having multiple network nodes configured to trigger a random access response (RAR) to a UE according to various aspects of the present disclosure.

[0016] Figure 6 is a connection flow diagram illustrating another example of a wireless communication system having multiple network nodes configured to trigger a RAR to a UE according to various aspects of the present disclosure.

[0017] Figure 7 is a connection flow diagram illustrating another example of a wireless communication system having multiple network nodes configured to trigger a RAR to a UE according to various aspects of the present disclosure.

[0018] Figure 8is a connection flow diagram illustrating another example of a wireless communication system having multiple network nodes configured to trigger a RAR to a UE according to various aspects of the present disclosure.

[0019] Fig. 9 is a flow chart of a method of wireless communication.

[0020] Fig.10 is another flow chart of a method of wireless communication.

[0021] Fig.11 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0022] Fig.12 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0023] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0024] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any 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] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0026] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0027] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0028] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts 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 radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit-receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0029] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0030] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0031] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0032] Each of these units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) 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 these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0033] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 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 110 may be implemented to communicate with DU 130 for network control and signaling.

[0034] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0035] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0036] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 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 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate 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 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

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

[0039] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0040] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0041] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0042] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "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 the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0044] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0045] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the optimal receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0046] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0047] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0048] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term "UE" may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0049] Refer again Figure 1In certain aspects, the UE 104 may have a RAR monitoring component 198 configured to receive a first RRC configuration from a serving cell, the first RRC configuration including a first configuration of a first PCI and a second PCI. The serving cell may be associated with a first PCI, and the additional cell may be associated with the second PCI different from the first PCI. The RAR monitoring component 198 may be configured to receive a PDCCH order from a network node, the PDCCH order including an indication of a PRACH transmission associated with the second PCI. The RAR monitoring component 198 may be configured to transmit the PRACH transmission associated with the second PCI during a PRACH opportunity. The RAR monitoring component 198 may be configured to monitor at least one first CSS in a first CORESET during a RAR window associated with the second PCI. The RAR window may be based on a temporal position of the PRACH opportunity. In certain aspects, the base station 102 may have a RAR sending component 199 configured to receive a configuration of at least one first CSS in a first CORESET associated with a second PCI from a serving cell. The serving cell may be associated with a first PCI different from the second PCI. The network node may be associated with the second PCI. The RAR sending component 199 may be configured to send a PDCCH command to the UE, the PDCCH command including an indication of a PRACH transmission. The RAR sending component 199 may be configured to receive the PRACH transmission associated with the second PCI from the UE during a PRACH opportunity. The RAR sending component 199 may be configured to send a RAR message to the UE during a RAR window associated with the second PCI in response to receiving the PRACH transmission. The RAR window may be based on the time position of the PRACH opportunity. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0050] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5GNR frame structure as TDD.

[0051] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0052]

[0053] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0054] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0055] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0056] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0057] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0058] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0059] Figure 3 370 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0060] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0061] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier is recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310, as well as the reference signal. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0062] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0063] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0064] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0065] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0066] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0067] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The RAR monitoring component 198 combines various aspects.

[0068] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The RAR sending component 199 combines various aspects.

[0069] Figure 4 4 is a diagram illustrating an example of a wireless communication system having a TRP 410, a TRP 420, and a UE 430. Figure 1 A network node such as a base station 102 in the UE 430 may communicate with a UE 430 via a TRP 410 or a TRP 420. Each of the TRP 410 and the TRP 420 may be configured to send DCI to the UE 430, thereby providing a multi-DCI based design for multi-TRP (mTRP) transmission. In one aspect, a first DCI sent from the TRP 410 may be sent to the UE 430 as a PDCCH 414. The first DCI of the PDCCH 414 may schedule the PDSCH 412 from the TRP 410 to the UE 430. A second DCI sent from the TRP 420 may be sent to the UE 430 as a PDCCH 414. The DCI of the PDCCH 414 may schedule the PDSCH 412 from the TRP 410 to the UE 430.

[0070] In some aspects, TRP 410 and TRP 420 may be transparent to UE 430. In other words, UE 430 may not be able to distinguish between a transmission from TRP 410 and a transmission from TRP 420. UE 430 may use a CORESET value or a CORESETPoolIndex value associated with a transmission to distinguish one transmission from the next. In other words, the CORESETPoolIndex value may allow UE 430 to determine that PDSCH 412 is from TRP 410, PDSCH 422 is from TRP 420, PDCCH 414 is from TRP 410, or PDCCH 424 is from TRP 420. On the other hand, UE 430 may not be able to distinguish between transmissions from different TRPs, but may be able to distinguish between a transmission associated with one CORESET value and a transmission associated with another CORESET value, or a transmission associated with one CORESETPoolIndex and a transmission associated with another CORESETPoolIndex.

[0071] Each CORESET of the UE 430 may be configured with a CORESETPoolIndex value. For example, the UE 430 may be configured (e.g., via RRC configuration) to have a first CORESETPoolIndex 416 and a second CORESETPoolIndex 426. The UE 430 may be configured by a configuration for a PDCCH received by the UE 430, the configuration for the PDCCH may include different values ​​of CORESETPoolIndex in a CORESET of an active BWP for a serving cell of the UE 430. The serving cell may be a network node that configures the UE using an RRC configuration. The RRC configuration may include a configuration of a PCI associated with a serving cell (e.g., a serving cell PCI) and a PCI associated with an additional cell or a non-serving cell (e.g., an additional cell PCI). The configuration may be, for example, a serving cell configuration including a serving cell index, a BWP ID, and a set of additional PCIs, each additional PCI having an additional PCI index and an additional PCI value. The serving cell may be a special cell (SpCell). If the UE is configured with carrier aggregation (CA), the UE may have one serving cell including its primary cell. If the UE is configured with CA, the UE may have a set of serving cells including its primary cell and a set of secondary cells. The primary cell in a set of serving cells may be referred to as a special cell (SpCell).

[0072] The first CORESETPoolIndex 416 and the second CORESETPoolIndex 426 may be distinguished by a value, for example, the first CORESETPoolIndex 416 may be assigned a value of 0 and the second CORESETPoolIndex 426 may be assigned a value of 1. Each of the first CORESETPoolIndex 416 and the second CORESETPoolIndex 426 may also be associated with a TRP. For example, the first CORESETPoolIndex 416 may be associated with the TRP 410 and the second CORESETPoolIndex 426 may be associated with the TRP 420. The configured CORESET of the UE 430 may be associated with one of the CORESETPoolIndex groups. For example, CORESET 417 and CORESET 418 may be associated with a first CORESETPoolIndex 416, and CORESET 427 and CORESET 428 may be associated with a second CORESETPoolIndex 426. Each of these CORESETs may be assigned a value, for example, CORESET 417 may be assigned a value of 1, CORESET 418 may be assigned a value of 2, CORESET 427 may be assigned a value of 3, and CORESET 428 may be assigned a value of 4. In response to the transmitted CORESET having a CORESET value of CORESET 417, UE 430 may associate the transmission with the first CORESETPoolIndex 416. In response to the transmitted CORESET having a CORESET value of CORESET 418, UE 430 may associate the transmission with the first CORESETPoolIndex 416. The first CORESETPoolIndex 416 may be associated with the TRP 410. In response to the transmitted CORESET having a CORESET value of CORESET 427, the UE 430 may associate the transmission with a second CORESETPoolIndex 426. In response to the transmitted CORESET having a CORESET value of CORESET 428, the UE 430 may associate the transmission with a second CORESETPoolIndex 426. The second CORESETPoolIndex 426 may be associated with the TRP 420.

[0073] Each TRP in the network may have the same PCI or a different PCI. The PCI may be an identifier of a cell such as a serving cell, SpCell, or an additional cell. An additional cell may also be referred to as a non-serving cell or a cell that does not use an RRC configuration to configure the UE. Communication between the UE and the additional cell may be scheduled by the serving cell of the UE (such as a SpCell, a primary cell, or a secondary cell). The PCI may be used to identify a cell relative to another cell on the PHY layer and may be used for DL ​​synchronization. In one aspect, if TRP 410 and TRP 420 are intra-cell TRPs, such as different panels of the same cell or different panels of the same base station, the PCIs of TRP 410 and TRP 420 may be the same. On the other hand, if TRP 410 and TRP 420 are inter-cell TRPs, such as different cells or different base stations, the PCIs used for TRP 410 and TRP 420 may be different from each other. Although the network system may have multiple TRPs that send data to the same UE, such as TRP 410 and TRP 420 that send to UE 430, UE 430 may know one PCI, namely, the PCI acquired by the UE during cell search, and may not know any other PCIs.

[0074] UE (such as Figure 1 A UE 430 or UE 104 in the UE may be configured (e.g., configured via RRC) with a list of candidate transmission configuration indication (TCI) states for quasi co-location (QCL) indications. For example, a QCL location may have a list of up to 128 TCI states. These TCI states may be used to configure a TCI state CORESET, non-zero power (NZP) channel state information (CSI) reference signal (NZP-CSI-RS) resources, physical uplink control channel (PUCCH) resources, or sounding reference signal (SRS) resources. The network node may send a medium access control (MAC) control element (MAC-CE) to the UE to activate several RRC-configured TCI states. Such a MAC-CE may be referred to as a TCI activation MAC-CE. In one aspect, for a CORESETPoolIndex of the UE, 2 of the M TCI states may be activated via the MAC-CE. NTCI states for PDSCH QCL indication. The N bits in the DCI can also or alternatively be used to dynamically indicate the TCI state for PDSCH transmission. For example, when N=3, the DCI can indicate one TCI state in eight TCI states. The UE can associate the PDSCH with the CORESETPoolIndex value of the CORESET in which the DCI is received. On the other hand, for one CORESETPoolIndex of the UE, one TCI state among M TCI states can be activated via MAC-CE for PDCCH QCL indication.

[0075] In some aspects, the UE may have the ability to provide an additional PCI configured via RRC for a serving cell or component carrier (CC). For example, the RRC configuration may configure the number of additional PCIs to 1, 2, 3, 4, 5, 6, or 7. The additional cell may be a cell that is not a serving cell of the UE. The serving cell may configure the UE using the RRC configuration, but the additional cell may not configure the UE using the RRC configuration. Each serving cell may be configured with multiple additional PCIs for inter-cell mDCI mTRP. The UE may report its ability to provide an additional PCI configured via RRC for the CC as the maximum number of UE capabilities (that the UE may be able to support) of the additional PCI configured via RRC per CC. In some aspects, the UE may be configured to report more than one maximum number of additional PCIs configured via RRC per CC in order to achieve different UE capability numbers for different UE environments. The UE environment may change, for example, based on the additional SSB time domain position and / or periodicity of the serving cell SSB time domain position and / or periodicity. In one aspect, if each configuration of the SSB time domain position and periodicity of the additional PCI is the same as the SSB time domain position and periodicity of the serving cell PCI, the UE may report the first UE capability as the maximum number of additional PCIs configured by RRC for the CC. If the configuration of the SSB time domain position and periodicity of the additional PCI is different from the SSB time domain position and periodicity of the serving cell PCI, the UE may report the second UE capability as the maximum number of additional PCIs configured by RRC for the CC. UE capabilities may be reported to distinguish between frequency ranges, such as FR1 and FR2. The UE may assume that one or more attributes of one or more additional PCIs are the same as those of the serving cell PCI. In one aspect, for an inter-cell mTRP system, the UE may assume that for an SSB from a serving cell and an SSB configured for an additional PCI different from the serving cell, at least one of the center frequency, SCS, or SFN offset may be the same. The RRC configuration may have one or more indicators indicating attributes associated with a TCI state or QCL. The RRC configuration may not have a PCI value, but may refer to attributes associated with the serving cell PCI and attributes associated with one or more non-serving cell PCIs. The non-serving cell PCI may be referred to as an additional PCI. The RRC configuration may have, for example, an indicator of the SSB of the serving cell, the PCI of the serving cell, an indicator of the SSB of one or more additional PCIs, and a PCI of one or more additional PCIs.

[0076] The serving cell PCI may be associated with one or more active TCI states. An additional PCI may be associated with an active TCI state. In other words, an active TCI state may be associated with a serving cell PCI and zero or one additional PCI. Different PCIs may also be associated with different CORESETPoolIndex values. A first PCI may be associated with a set of activated TCI states for PDSCH or PDCCH and a first CORESETPoolIndex, and a second PCI may be associated with a set of activated TCI states for PDSCH or PDCCH and a second CORESETPoolIndex. In other words, a first PCI may be associated with a first TRP, and a second PCI may be associated with a second TRP.

[0077] exist Figure 5 5 , a connection flow diagram 500 illustrates an example of a wireless communication system having an additional PCI 506 configured to send a PDCCH command 518 to a UE 502. A serving cell PCI 504 of the UE 502 may be different from a special cell (SpCell) PCI 508 of the UE 502. As used herein, a PCI may be a network node associated with a PCI. The serving cell PCI 504 may be a network node (e.g., a TRP) associated with the serving cell PCI of the UE 502, the additional PCI 506 may be a network node associated with the additional PCI of the UE 502, and the SpCell PCI may be a network node associated with the special cell PCI of the UE 502. At 510, the serving cell PCI 504 may configure one or more PCIs for the UE 502, and may output a PCI configuration 512 to the UE 502. UE 502 may receive PCI configuration 512 for one or more PCIs of UE 502 from serving cell PCI 504. For example, PCI configuration 512 may configure serving cell PCI 504 and additional PCI 506 for UE 502. At 514, SpCell PCI 508 may configure one or more PCIs for UE 502 and may output PCI configuration 516 to UE 502. UE 502 may receive PCI configuration 516 for one or more PCIs of UE 502 from SpCell PCI 508. For example, PCI configuration 516 may configure SpCell PCI 508 and additional PCI 506 for UE 502. PCI configuration 516 may also configure additional PCIs for the SpCell that are different from one or more PCIs in PCI configuration 512. PCI configuration 512 or PCI configuration 516 may be, for example, an RRC configuration of UE 502.

[0078] The additional PCI 506 may send a PDCCH command 518 to the UE 502, thereby triggering a PRACH transmission 520 to the PDCCH command 518. In some examples, the PDCCH command 518 may be sent from the serving cell PCI 504 or the SpCell PCI 508 to trigger the PRACH transmission 520 (not shown in the figure). The additional PCI 506 may measure the timing advance (TA) of the UE 502 based on the PRACH transmission 520. In some aspects, if the active TCI state is associated with a PCI different from the serving cell PCI 504, the UE 502 may not be configured to monitor the common search space (CSS) in the CORESET. In other words, if the additional PCI 506 sends a random access response (RAR) 524, the UE 502 may not receive the CSS in the CORESET. The CSS may be a common search space of resources that the UE monitors during a period of time to identify and process DL signals. The RAR may be a message received by the UE during UL synchronization, the message including information used by the UE to synchronize with a cell, such as timing advance (TA) information.

[0079] The additional PCI 506 may be configured to communicate with the SpCell PCI 508 to send the measured TA using TRP coordination 522 between the additional PCI 506 and the SpCell PCI 508. The additional PCI 506 may output the measured TA using the TRP coordination 522. The SpCell PCI 508 may obtain the measured TA using the TRP coordination 522. The SpCell PCI 508 may output a random access response (RAR) 524 to the UE 502. The UE 502 may receive the RAR 524 from the SpCell PCI. If the active TCI state is associated with the SpCell PCI 508, the UE 502 may be configured to monitor the CSS in the CORESET. The UE 502 may send an UL transmission 526 to the additional PCI using the measured TA.

[0080] Although inter-TRP coordination may allow the UE 502 to receive the RAR associated with the additional PCI 506 by using TRP coordination 522 between the additional PCI 506 and the SpCell PCI 508, if the backhaul between the additional PCI 506 and the SpCell PCI 508 is not ideal, there may be a large delay for the additional PCI 506 to communicate the measured TA to the SpCell PCI 508 using TRP coordination 522. This delay may prevent the UE 502 from receiving the RAR 524 within the RAR window because the RAR window may start shortly after the PRACH transmission 520 ends.

[0081] exist Figure 6 6, a connection flow diagram 600 illustrates an example of a wireless communication system having an additional PCI 606 configured to send a PDCCH command 618 to a UE 602. The serving cell PCI of the UE 602 may be the same as the SpCell PCI 608 of the UE 602. At 614, the SpCell PCI 608 may configure one or more PCIs for the UE 602 and may output a PCI configuration 616 to the UE 602. The UE 602 may receive a PCI configuration 616 for one or more PCIs of the UE 602 from the SpCell PCI 608. For example, the PCI configuration 616 may configure the SpCell PCI 608 and the additional PCI 606 for the UE 602. The PCI configuration 616 may be, for example, an RRC configuration of the UE 602.

[0082] The additional PCI 606 may send a PDCCH command 618 to the UE 602, thereby triggering a PRACH transmission 620 to the PDCCH command 618. In some examples, the PDCCH command 618 may be sent from the serving cell PCI or SpCell 608 to trigger the PRACH transmission 620 (not shown). The additional PCI 606 may measure the timing advance (TA) of the UE 602 based on the PRACH transmission 620. In some aspects, if the active TCI state is associated with a PCI different from the SpCell PCI 608, the UE 602 may still not be configured to monitor the CSS in the CORESET. In other words, if the additional PCI 606 sends a RAR 624, the UE 602 may not be able to receive the CSS in the CORESET. To overcome this limitation, the additional PCI 606 may be configured to communicate with the SpCell PCI 608 to send the measured TA using TRP coordination 622 between the additional PCI 606 and the SpCell PCI 608. The additional PCI 606 may output the measured TA using the TRP coordination 622. The SpCell PCI 608 may obtain the measured TA using the TRP coordination 622. The SpCell PCI 608 may output a random access response (RAR) 624 to the UE 602. The UE 602 may receive the RAR 624 from the SpCell PCI. If the active TCI state is associated with the SpCell PCI 608, the UE 602 may be configured to monitor the CSS in the CORESET. The UE 602 may send an UL transmission 626 to the additional PCI using the measured TA.

[0083] Although inter-TRP coordination may allow the UE 602 to receive the RAR from the additional PCI 606 by using TRP coordination 622 between the additional PCI 606 and the SpCell PCI 608, if the backhaul between the additional PCI 606 and the SpCell PCI 608 is not ideal, there may be a large delay for the additional PCI 606 to communicate the measured TA to the SpCell PCI 608 using TRP coordination 622. This delay may prevent the UE 602 from receiving the RAR 624 within the RAR window because the RAR window may start shortly after the PRACH transmission 620 ends.

[0084] To reduce the use Figure 6 TRP coordination in 622 or Figure 5 The additional PCI may be configured to send a RAR to the UE, and the UE may be configured to monitor the CSS in the CORESET associated with the additional PCI.

[0085] In one aspect, the UE may be configured to receive a configuration of a second PCI (e.g., an additional PCI) from a serving cell associated with a first PCI (e.g., a serving cell PCI or a SpCell PCI) that is different from the second PCI. The UE may be configured to receive a PDCCH command from a network node, the PDCCH command including an indication of a PRACH transmission associated with the second PCI. The PDCCH command may be sent from an additional PCI, a serving cell PCI, or a special cell PCI. The UE may be configured to send the PRACH transmission associated with the second PCI in / during a PRACH opportunity. The UE may be configured to monitor at least one first CSS in the first CORESET during a RAR window associated with the second PCI in response to the PRACH transmission. The RAR window may be based on the time position of the PRACH opportunity. For example, the RAR window may be scheduled as a number of symbols after the last symbol of the PRACH opportunity. The PRACH opportunity may be a time period scheduled by the serving cell for the UE to send the PRACH transmission using resources associated with the PRACH transmission. The PRACH opportunity may also be referred to as a PRACH window.

[0086] On the other hand, a network node (e.g., a TRP of an additional PCI or a serving cell PCI) may be configured to send a configuration of at least one first CSS in a first CORESET associated with a second PCI (e.g., an additional PCI) from a serving cell associated with a first PCI (e.g., a serving cell PCI or a SpCell PCI) that is different from the second PCI (e.g., an additional PCI). The network node may be configured to send a PDCCH command to the UE, the PDCCH command including an indication of a PRACH transmission. The network node may be configured to receive the PRACH transmission associated with the second PCI in a PRACH opportunity. The network node may be configured to, in response to the PRACH reception, send a RAR message to the UE during a RAR window associated with the second PCI. The RAR window may be based on the temporal position of the PRACH opportunity.

[0087] exist Figure 7 7, a connection flow diagram 700 illustrates an example of a wireless communication system having an additional PCI 706 configured to send a PDCCH command 718 to a UE 702. A serving cell PCI 704 of the UE 702 may be different from a SpCell PCI 708 of the UE 702. The serving cell PCI 704 may be a network node (e.g., a TRP) associated with the serving cell PCI of the UE 702, the additional PCI 706 may be a network node associated with the additional PCI of the UE 702, and the SpCell PCI 708 may be a network node associated with a special cell PCI of the UE 702. At 710, the serving cell PCI 704 may configure one or more PCIs for the UE 702 and may output a PCI configuration 712 to the UE 702. The UE 702 may receive a PCI configuration 712 for one or more PCIs of the UE 702 from the serving cell PCI 704. For example, PCI configuration 712 may configure serving cell PCI 704 and additional PCI 706 for UE 702. At 714, SpCell PCI 708 may configure one or more PCIs for UE 702 and may output PCI configuration 716 to UE 702. UE 702 may receive PCI configuration 716 for one or more PCIs of UE 702 from SpCell PCI 708. For example, PCI configuration 716 may configure SpCell PCI 708 and additional PCI 706 for UE 702. PCI configuration 712 or PCI configuration 716 may be, for example, an RRC configuration of UE 702.

[0088] The additional PCI 706 may send a PDCCH order 718 to the UE 702, thereby triggering a PRACH transmission 720 to the PDCCH order 718. In some examples, the PDCCH order may be sent from the serving cell PCI 704 or from the SpCell PCI 708 (not shown here). The additional PCI 706 may measure the timing advance (TA) of the UE 702 based on the PRACH transmission 720. In some aspects, if the active TCI state is associated with a PCI different from the serving cell PCI 704, the UE 702 may be configured to monitor the CSS in the CORESET. The CSS may be, for example, an NR type 1 CSS. If the active TCI state is associated with the additional PCI 706, the UE 702 may be configured to monitor the CSS in the CORESET. If the active TCI state is associated with the additional PCI 706, the UE 702 may be configured to monitor the CSS in the CORESET in response to a MAC-CE received from the serving cell PCI 704. The serving cell PCI 704 may output a MAC-CE 722 to the UE 702. The UE 702 may receive the MAC-CE 722. The UE 702 may respond to the serving cell PCI 704 with an ACK 723. The serving cell PCI 704 may obtain the ACK 723 from the UE 702. The additional PCI 706 may send a RAR message to the UE in response to receiving the PRACH transmission 720. The UE 702 may send an UL transmission 726 to the additional PCI using the TA indicated in the RAR. Although one additional PCI 706 is shown in the connection flow diagram 700, in other embodiments, more additional PCIs may be configured with the UE 702 because the PCI configuration 712 may include RRC configurations for multiple PCIs, depending on the UE capabilities of the UE 702. In some aspects, the UE 702 may be configured to process the RAR 724 in response to failing to receive a MAC-CE 722 activating a TCI state associated with the additional PCI 706 .

[0089] In one aspect, one CSS set may be configured in the CORESET and may be applied to the SpCell PCI 708 and the additional PCI 706. The configuration may be, for example, a PCI configuration 712 configured at 710 by the serving cell PCI 704, or a PCI configuration 716 configured at 714 by the SpCell PCI 708. Based on one or more indicators of the MAC-CE 722, the active TCI state of the CORESET in which the CSS set is configured may be associated with the serving cell PCI 704, the additional PCI 706, or the SpCell PCI 708. In some aspects, if the active TCI state is associated with the additional PCI 706, the UE 702 may be configured to monitor the CSS in the CORESET within the RAR window associated with the additional PCI 706, if one or more of the following conditions are met: (a) the additional PCI 706 is configured at 710 by the serving cell PCI 704, (b) the additional PCI 706 is configured at 714 by the SpCell PCI 708, and (c) the additional PCI 706 is associated with the same CORESETPoolIndex or timing advance group (TAG) identifier (ID) for the serving cell PCI 704 and the SpCell PCI 708. In some aspects, if each of these three conditions is met or if condition (b) is met, if the active TCI state is associated with the additional PCI 706, the UE 702 may be configured to monitor the CSS in the CORESET within the RAR window associated with the additional PCI 706. UE 702 may determine that additional PCI 706 is configured by serving cell PCI 704 at 710 by receiving PCI configuration 712 configuring additional PCI 706 from serving cell PCI 704. UE 702 may determine that additional PCI 706 is configured by SpCell PCI 708 at 714 by receiving PCI configuration 716 configuring additional PCI 706 from SpCell PCI 708.

[0090] If the additional PCI 706 associated with the active TCI state of the CORESET associated with the additional PCI 706 is the same as the additional PCI 706 corresponding to the RAR window of the PRACH transmission 720 or the RAR 724, the UE 702 may be configured to monitor the CSS in the CORESET. In other words, in response to the PRACH transmission 720 with the preamble ID indicated by the PDSCH of the RAR 724, the UE 702 may monitor the CSS in the CORESET associated with the additional PCI 706. The PRACH transmission 720 and the RAR 724 may correspond to each other via the preamble ID indicated by the RAR PDSCH.

[0091] The UE 702 may send the UE capabilities 709 to at least one of the serving cell PCI 704 or the SpCell PCI 708. In some aspects, the UE 702 may send the UE capabilities 709 to both the serving cell PCI 704 and the SpCell PCI 708. If the active TCI state is associated with the additional PCI 706, the UE capabilities may have an indicator indicating whether the UE 702 can monitor the CSS in the CORESET. In some aspects, the UE capabilities of the UE 702 may be configured in the RRC configuration, such as by the PCI configuration 712 or the PCI configuration 716. The RRC configuration may apply to the additional PCI 706 and not to other additional PCIs, or to a group of additional PCIs to which the additional PCI 706 belongs.

[0092] In some aspects, if the active TCI state is associated with the SpCell PCI 708, the UE 702 may be configured to determine whether to monitor the CSS in the CORESET. In one aspect, if the active TCI state is associated with the SpCell PCI 708, the UE 702 may be configured not to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 706. On the other hand, if the active TCI state is associated with the SpCell PCI 708, the UE 702 may be configured to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 706. On the other hand, the UE 702 may be configured to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 706 based on an RRC configuration (such as the PCI configuration 712 or the PCI configuration 716). In one aspect, the RRC configuration may enable or disable CSS monitoring in a RAR window associated with a set of additional PCIs (of which the additional PCI 706 is a part). On the other hand, the RRC configuration may enable or disable CSS monitoring in a RAR window associated with an additional PCI 706 based on the configuration of a specific PCI value for the additional PCI 706. Each additional PCI 706 may be enabled or disabled based on a separate trigger, such as a MAC-CE customized for each additional PCI. In one aspect, the UE 702 may be configured to monitor CSS in a RAR window associated with an additional PCI 706 when the active TCI state is associated with the SpCell PCI 708, but may not be configured to monitor CSS in a CORESET in a RAR window associated with a second additional PCI when the active TCI state is associated with the SpCell PCI 708. Such aspects may be useful if there is a hybrid backhaul scenario, such as when the backhaul between the SpCell PCI 708 and the additional PCI 706 has good performance and the backhaul between the SpCell PCI 708 and the second additional PCI does not have good performance.

[0093] In one aspect, a first CSS set may be configured in the CORESET for the SpCell PCI 708, and a second CSS set may be configured in the CORESET for the additional PCI 706. The configuration may be, for example, a PCI configuration 712 configured at 710 by the serving cell PCI 704, or a PCI configuration 716 configured at 714 by the SpCell PCI 708. The active TCI state of the CORESET in which the CSS set is configured may be associated with the additional PCI 706 based on one or more indicators of the MAC-CE 722. In some aspects, the CSS set in the CORESET may be configured for the UE 702 as a CSS set separate from the CSS set in the CORESET associated with the SpCell PCI 708 if one or more of the following conditions are met: (a) the additional PCI 706 is configured at 710 by the serving cell PCI 704, (b) the additional PCI 706 is configured at 714 by the SpCell PCI 708, and (c) the additional PCI 706 is associated with the same CORESETPoolIndex or timing advance group (TAG) identifier (ID) for the serving cell PCI 704 and the SpCell PCI 708. At 714, the CSS set may be configured by the SpCell PCI 708. In some aspects, where each of the three conditions is met or where the above condition (b) is met (the additional PCI 706 is configured by the SpCell PCI 708 at 714), the CSS set in the CORESET may be configured for the UE 702 as a CSS set separate from the CSS set in the CORESET associated with the SpCell PCI 708. The UE 702 may determine that the additional PCI 706 is configured by the serving cell PCI 704 at 710 by receiving a PCI configuration 712 configuring the additional PCI 706 from the serving cell PCI 704. The UE 702 may determine that the additional PCI 706 is configured by the SpCell PCI 708 at 714 by receiving a PCI configuration 716 configuring the additional PCI 706 from the SpCell PCI 708. In some aspects, if the additional PCI 706 is configured by the serving cell PCI 704 at 710 but the SpCell PCI 708 is not configured with the same additional PCI 706 , then the CSS set associated with the additional PCI in the CORESET may be configured by the serving cell PCI 704 at 710 .

[0094] In some aspects, if the active TCI state of the CORESET is associated with the SpCell PCI 708, the UE 702 may be predefined or configured to monitor a first CSS set in the CORESET (associated with the SpCell PCI 708) without monitoring a second CSS set in the CORESET (associated with the additional PCI 706). If the active TCI state of the CORESET is associated with the additional PCI 706, the UE 702 may be configured to monitor the second CSS set in the CORESET (associated with the additional PCI 706) without monitoring the first CSS set in the CORESET (associated with the SpCell PCI 708). The additional PCI may be an additional PCI to which the PRACH transmission 720 or the RAR 724 corresponds. In this aspect, the RAR for the PRACH transmission 720 associated with the serving cell PCI 704 may be sent from the SpCell PCI 708. The RAR for the PRACH transmission 720 associated with the additional PCI 706 may not be sent by a network node (which is not the additional PCI 706). The configuration may be specifically configured via RRC to be the additional PCI 706 or a set of additional PCIs to which the additional PCI 706 belongs. The UE capabilities 709 may have an indicator from the SpCell PCI 708 as to whether the UE 702 can monitor the second CSS set in the CORESET (associated with the additional PCI 706). The UE capabilities 709 may have an indicator as to whether the UE 702 can monitor the first CSS set in the CORESET (associated with the SpCell PCI 708) when the active TCI state of the CORESET is associated with the additional PCI 706.

[0095] In one aspect, the UE 702 may be configured to not expect the active TCI state of the CORESET to be associated with the serving cell PCI 704 or the SpCell PCI 708. In another aspect, the active TCI state of the CORESET may be associated with the serving cell PCI 704 or the additional PCI 706. For example, in one aspect, the UE 702 may be configured to monitor the CSS set associated with the additional PCI 706 in response to the active TCI state being associated with the additional PCI 706. The additional PCI 706 may be the same as the additional PCI to which the PRACH opportunity or RAR window corresponds. In such aspects, the RAR 724 for the PRACH transmission 720 may be sent from the additional PCI 706 instead of from the serving cell PCI 704 or the SpCell PCI 708. In another aspect, the UE 702 may be configured to monitor the CSS set associated with the additional PCI 706 in response to whether the active TCI state is associated with the serving cell PCI 704 or the additional PCI 706. The additional PCI 706 may be the same as the additional PCI corresponding to the PRACH opportunity or RAR window. In another aspect, the UE 702 may be configured to monitor both the first CSS set associated with the first CORESET on the SpCell PCI 708 and the second CSS set associated with the second CORESET on the serving cell PCI 704 to which the additional PCI 706 is associated. The UE 702 may be configured to monitor the second CSS set in response to the active TCI state of the second CORESET being associated with the additional PCI 706, or to monitor the second CSS set regardless of whether the active TCI state of the second CORESET is associated with the serving cell PCI 704 or the additional PCI 706.

[0096] In some aspects, if the active TCI state of the CORESET is associated with the SpCell PCI 708, the UE 702 may be predefined or configured to monitor a first CSS set in the CORESET (associated with the SpCell PCI 708) and not monitor a second CSS in the CORESET (associated with the additional PCI 706). If the active TCI state of the CORESET is associated with the additional PCI 706, the UE 702 may be configured to monitor both the first CSS set in the CORESET (associated with the SpCell PCI 708) and the second CSS set in the CORESET (associated with the additional PCI 706). The additional PCI may be the additional PCI to which the PRACH transmission 720 or the RAR 724 corresponds. In this aspect, the RAR for the PRACH transmission 720 associated with the serving cell PCI 704 may be sent from the SpCell PCI 708 instead of the additional PCI 706 or the serving cell PCI 704. The RAR for the PRACH transmission 720 associated with the additional PCI 706 may be sent by the SpCell PCI 708 or the additional PCI 706. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0097] In some aspects, the UE 702 may be predefined or configured to monitor both the first CSS set (associated with the SpCell PCI 708) and the second CSS set (associated with the additional PCI 706) in the CORESET, regardless of whether the active TCI state of the CORESET is associated with the additional PCI 706 or the SpCell PCI 708. In this aspect, the RAR for the PRACH transmission 720 associated with the serving cell PCI 704 or the RAR for the PRACH transmission 720 associated with the additional PCI 706 may be sent by the SpCell PCI 708 or the additional PCI 706. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0098] In one aspect, the UE 702 may be predefined or configured to monitor a CSS associated with the additional PCI 706 in a first CORESET or to monitor a CSS associated with the SpCell PCI 708 in a second CORESET. In other words, a first CSS associated with the additional PCI 706 may be located in the first CORESET, and a second CSS associated with the SpCell PCI 708 may be located in the second CORESET. The UE 702 may be configured to monitor the RAR in the RAR window based on the CORESET. The RAR window associated with the additional PCI 706 for PRACH may be determined based on the CORESET that is configured with the additional CSS set or configured with the additional PCI 706. The RAR window associated with the additional PCI 706 for the PRACH transmission 720 may start at the first symbol of the earliest CORESET for which the UE 702 is configured to receive the CSS associated with the additional PCI 706, the RAR window being at least a fixed number of symbols after the last symbol of the PRACH opportunity corresponding to the PRACH transmission 720. For a CORESET configured with a CSS associated with the SpCell PCI 708, the UE 702 may not expect the active TCI state of the CORESET to be associated with the additional PCI 706. The CSS of the CORESET may be associated with a PCI such as the serving cell PCI 704 or the additional PCI 706. In one aspect, for a CORESET configured with a CSS associated with the additional PCI 706, the UE 702 may not expect the active TCI state of the CORESET to be associated with the SpCell PCI 708. On the other hand, for a CORESET configured with a CSS associated with an additional PCI 706 , the active TCI state of the CORESET may be associated with the SpCell PCI 708 or the additional PCI 706 .

[0099] In one aspect, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the CORESET when the active TCI state of the CORESET is associated with the additional PCI 706. The RAR 724 may be sent from the additional PCI 706 and may not be sent from the serving cell PCI 704 or the SpCell PCI 708. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0100] On the other hand, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the CORESET, regardless of whether the active TCI state of the CORESET is associated with the additional PCI 706 or the SpCell PCI 708. The RAR 724 may be sent from the SpCell PCI 708 or the additional PCI 706. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0101] On the other hand, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the first CORESET and the CSS associated with the SpCell PCI 708 in the second CORESET. If the active TCI state of the first CORESET is associated with the additional PCI 706, the UE 702 may monitor the CSS associated with the additional PCI 706 in the first CORESET. The UE 702 may monitor the CSS associated with the additional PCI 706 in the first CORESET regardless of whether the active TCI state of the first CORESET is associated with the SpCell PCI 708 or the additional PCI 706. The RAR 724 may be sent by the additional PCI 706 or the SpCell PCI 708. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0102] In one aspect, if the additional PCI 706 is configured in 710 by the serving cell PCI 704 but the SpCell PCI 708 is not configured with the same additional PCI 706, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the first CORESET on the serving cell PCI 704 or to monitor the CSS associated with the SpCell PCI in the CORESET on the SpCell. In other words, the first CSS associated with the additional PCI 706 may be located in the first CORESET configured by the serving cell PCI 704, and the second CSS associated with the SpCell PCI 708 may be located in the second CORESET configured by the SpCell PCI 708. In one aspect, for the CORESET configured with the CSS associated with the additional PCI 706, the UE 702 may not expect the active TCI state of the CORESET to be associated with the serving cell PCI 704. On the other hand, for a CORESET configured with a CSS associated with the additional PCI 706 , the active TCI state of the CORESET may be associated with the serving cell PCI 704 or the additional PCI 706 .

[0103] In one aspect, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the CORESET on the serving cell PCI 704 when the active TCI state of the CORESET is associated with the additional PCI 706. The RAR 724 may be sent from the additional PCI 706 and may not be sent from the serving cell PCI 704 or the SpCell PCI 708. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0104] On the other hand, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the CORESET on the serving cell PCI 704, regardless of whether the active TCI state of the CORESET is associated with the additional PCI 706 or the serving cell PCI 704. The RAR 724 may be sent from the serving cell PCI 704 or the additional PCI 706. The configuration may be specifically configured via RRC to the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0105] On the other hand, the UE 702 may be predefined or configured to monitor the CSS associated with the additional PCI 706 in the first CORESET on the serving cell PCI 704 and the CSS associated with the SpCell PCI 708 in the second CORESET on the SpCell PCI 708. If the active TCI state of the first CORESET is associated with the additional PCI 706, the UE 702 may monitor the CSS associated with the additional PCI 706 in the first CORESET on the serving cell PCI 704. The UE 702 may monitor the CSS associated with the additional PCI 706 in the first CORESET on the serving cell PCI 704, regardless of whether the active TCI state of the first CORESET is associated with the serving cell PCI 704 or the additional PCI 706. The RAR 724 may be sent by the additional PCI 706 or the serving cell PCI 704. The configuration may be specifically configured via RRC as the additional PCI 706 or a group of additional PCIs to which the additional PCI 706 belongs.

[0106] In some aspects, the TCI activation MAC-CE 722 indicating that the active TCI state of the CORESET (in which the Type 1 CSS is configured) is associated with the additional PCI may not be received by the UE 702 in time for the UE 702 to monitor the RAR window for RAR 724. In some aspects, the UE may treat this situation as an error condition. In other words, the network may be configured to ensure that the RAR 724 can be sent from the additional PCI within the RAR window associated with the additional PCI 706 (e.g., by enabling such a feature via RRC configuration or MAC-CE). Therefore, the network may be configured to transmit a MAC CE to activate the TCI state associated with the additional PCI 706 for the CORESET in which the Type 1 CSS is configured.

[0107] In one aspect, if the UE 702 does not receive the TCI activation MAC CE 722 indicating that the active TCI state of the CORESET (in which the Type 1 CSS is configured) is associated with the additional PCI in time for the UE 702 to monitor the RAR window for RAR 724, and if the UE 702 is predefined or configured not to monitor the CSS set associated with the serving cell PCI 704 or SpCell PCI 708 in the CORESET when the active TCI state is associated with the serving cell PCI 704 or SpCell PCI 708, the UE 702 may consider that the reception of the RAR 724 is unsuccessful. In one aspect, the UE 702 may increment the PRACH transmission counter.

[0108] In one aspect, if the UE 702 does not receive the TCI activation MAC CE 722 indicating that the active TCI state of the CORESET (in which Type 1 CSS is configured) is associated with the additional PCI in time for the UE 702 to monitor the RAR window for RAR724, and if the UE 702 is predefined or configured to monitor the CSS set associated with the serving cell PCI 704 or SpCell PCI 708 in the CORESET when the active TCI state is associated with the serving cell PCI 704 or SpCell PCI 708, then the UE 702 may consider that the reception of the RAR 724 is unsuccessful if the UE 702 does not receive the RAR from both the serving cell PCI 704 or SpCell PCI 708 and the additional PCI 706. In one example, if the UE 702 receives the RAR associated with the additional PCI 706 from the serving cell PCI 704 or the SpCell PCI 708 but not the additional PCI 706, the UE 702 may apply the received TA to the UL transmission associated with the additional PCI 706. In another example, if the UE 702 does not receive the RAR 724 from the additional PCI 706, the UE 702 may consider that the reception of the RAR is unsuccessful. The UE 702 may ignore the RAR received from the serving cell PCI 704 or the SpCell PCI 708. In some aspects, if the UE 702 does not receive the RAR from both the serving cell PCI 704 or the SpCell PCI 708 and the additional PCI 706, the UE 702 may be configured to consider that the reception of the RAR 724 is unsuccessful. In some other aspects, if the UE 702 does not receive the RAR 724 from the additional PCI 706, the UE 702 can be configured or consider that the reception of the RAR 724 was unsuccessful.

[0109] exist Figure 8800 illustrates an example of a wireless communication system having an additional PCI 806 configured to send a PDCCH command 818 to a UE 802. The serving cell PCI of the UE 802 may be the same as the SpCell PCI 808 of the UE 802. The additional PCI 806 may be a network node associated with the additional PCI of the UE 802, and the SpCell PCI 808 may be a network node associated with the special cell PCI of the UE 802. At 814, the SpCellPCI 808 may configure one or more PCIs for the UE 802, and may output a PCI configuration 816 to the UE 802. The UE 802 may receive a PCI configuration 816 for one or more PCIs of the UE 802 from the SpCell PCI 808. For example, the PCI configuration 816 may configure the SpCell PCI 808 and the additional PCI 806 for the UE 802. The PCI configuration 816 may be, for example, an RRC configuration of the UE 802 .

[0110] The additional PCI 806 may send a PDCCH command 818 to the UE 802, thereby triggering a PRACH transmission 820 to the PDCCH command 818. In some examples, the PDCCH command may be sent from the SpCell PCI 808 (not shown here). The additional PCI 806 may measure the timing advance (TA) of the UE 802 based on the PRACH transmission 820. In some aspects, if the active TCI state is associated with a PCI different from the SpCell PCI 808, the UE 802 may be configured to monitor the CSS in the CORESET. The CSS may be, for example, an NR type 1 CSS. If the active TCI state is associated with the additional PCI 806, the UE 802 may be configured to monitor the CSS in the CORESET. If the active TCI state is associated with the additional PCI 806, the UE 802 may be configured to monitor the CSS in the CORESET in response to a MAC-CE received from the SpCell PCI 808. The SpCell PCI 808 may output a MAC-CE 822 to the UE 802. The UE 802 may receive the MAC-CE 822. The UE 802 may respond to the SpCell PCI 808 with an ACK 823. The SpCell PCI 808 may obtain the ACK 823 from the UE 802. The UE 802 may send an UL transmission 826 to the additional PCI using the measured TA. Although one additional PCI 806 is shown in the connection flow diagram 800, in other embodiments, more additional PCIs may be configured with the UE 802 because the PCI configuration 816 may include RRC configurations for multiple PCIs, depending on the UE capabilities of the UE 802.

[0111] In one aspect, one CSS set may be configured in the CORESET and may be applied to the SpCell PCI 808 and the additional PCI 806. The configuration may be, for example, a PCI configuration 816 configured by the SpCell PCI 808 at 814. The active TCI state of the CORESET in which the CSS set is configured may be associated with the SpCell PCI 808 or the additional PCI 806 based on one or more indicators of the MAC-CE 822. In some aspects, if the active TCI state is associated with the additional PCI 806, the UE 802 may be configured to monitor the CSS in the CORESET within a RAR window associated with the additional PCI 806, and the additional PCI 806 is configured by the SpCell PCI 808 at 814. The UE 802 may determine that the additional PCI 806 is configured by the SpCell PCI 808 at 814 by receiving the PCI configuration 816 configuring the additional PCI 806 from the SpCell PCI 808.

[0112] If the additional PCI 806 associated with the active TCI state of the CORESET associated with the additional PCI 806 is the same as the additional PCI 806 corresponding to the RAR window of the PRACH transmission 820 or the RAR 824, the UE 802 may be configured to monitor the CSS in the CORESET. In other words, in response to the PRACH transmission 820 with the preamble ID indicated by the PDSCH of the RAR 824, the UE 802 may monitor the CSS in the CORESET associated with the additional PCI 806. The PRACH transmission 820 and the RAR 824 may correspond to each other via the preamble ID indicated by the PDSCH.

[0113] The UE 802 may send the UE capabilities 809 to the SpCell PCI 808. If the active TCI state is associated with the additional PCI 806, the UE capabilities may have an indicator indicating whether the UE 802 may monitor the CSS in the CORESET. In some aspects, the UE capabilities of the UE 802 may be configured in the RRC configuration, such as by the PCI configuration 816. The RRC configuration may apply to the additional PCI 806 and not to other additional PCIs, or to a group of additional PCIs to which the additional PCI 806 belongs.

[0114] In some aspects, if the active TCI state is associated with the SpCell PCI 808, the UE 802 may be configured to determine whether to monitor the CSS in the CORESET. In one aspect, if the active TCI state is associated with the SpCell PCI 808, the UE 802 may be configured not to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 806. On the other hand, if the active TCI state is associated with the SpCell PCI 808, the UE 802 may be configured to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 806. On the other hand, the UE 802 may be configured to monitor the CSS in the CORESET in the RAR window associated with the additional PCI 806 based on an RRC configuration (such as the PCI configuration 816). In one aspect, the RRC configuration may enable or disable CSS monitoring in a RAR window associated with a set of additional PCIs (of which the additional PCI 806 is a part). On the other hand, the RRC configuration may enable or disable CSS monitoring in a RAR window associated with the additional PCI 806 based on the configuration of a specific PCI value for the additional PCI 806. Each additional PCI 806 may be enabled or disabled based on a separate trigger, such as a MAC-CE customized for each additional PCI. In one aspect, the UE 802 may be configured to monitor the CSS in the RAR window associated with the additional PCI 806 when the active TCI state is associated with the SpCell PCI 808, but may not be configured to monitor the CSS in the CORESET in the RAR window associated with the second additional PCI when the active TCI state is associated with the SpCell PCI 808. Such aspects may be useful if there is a hybrid backhaul scenario, such as when the backhaul between the SpCell PCI 808 and the additional PCI 806 has good performance and the backhaul between the SpCell PCI 808 and the second additional PCI does not have good performance.

[0115] In one aspect, a first CSS set may be configured in the CORESET for the SpCell PCI 808, and a second CSS set may be configured in the CORESET for the additional PCI 806. The configuration may be, for example, a PCI configuration 816 configured by the SpCell PCI 808 at 814. At 814, the SpCell PCI 808 may configure the second CSS associated with the additional PCI 806 and the additional PCI 806 via the PCI configuration 816. The active TCI state of the CORESET in which the CSS set is configured may be associated with the additional PCI 806 based on one or more indicators of the MAC-CE 822. The UE 802 may determine that the additional PCI 806 is configured by the SpCell PCI 808 at 814 by receiving the PCI configuration 816 configuring the additional PCI 806 from the SpCell PCI 808.

[0116] In some aspects, if the active TCI state is associated with the SpCell PCI 808, the UE 802 may be configured to monitor the CSS set in the CORESET associated with the serving cell PCI. If the active TCI state is associated with the additional PCI 806, the UE 802 may be configured to monitor the CSS set in the CORESET associated with the additional PCI 806. The additional PCI may be an additional PCI to which the PRACH transmission 820 or the RAR 824 corresponds. In this aspect, the RAR for the PRACH transmission 820 associated with the SpCell PCI 808 may be sent from the SpCell PCI 808. The RAR for the PRACH transmission 820 associated with the additional PCI 806 may not be sent by a network node (which is not the additional PCI 806). The configuration may be specifically configured via RRC to be an additional PCI 806 or a set of additional PCIs to which the additional PCI 806 belongs. The UE capabilities 809 may have an indicator as to whether the UE 802 can monitor the CSS set in the CORESET associated with the additional PCI 806 from the SpCell PCI 808. The UE capabilities 809 may have an indicator as to whether the UE 802 can monitor the CSS set in the CORESET associated with the SpCell PCI 808 when the active TCI state is associated with the additional PCI 806.

[0117] In some aspects, if the active TCI state is associated with the SpCell PCI 808, the UE 802 may be configured to monitor the CSS set in the CORESET associated with the serving cell PCI. If the active TCI state is associated with the additional PCI 806, the UE 802 may be configured to monitor the CSS set in the CORESET associated with the additional PCI 806 and associated with the serving cell PCI. The additional PCI may be the additional PCI to which the PRACH transmission 820 or the RAR 824 corresponds. In this aspect, the RAR for the PRACH transmission 820 associated with the SpCell PCI 808 may be sent from the SpCell PCI 808 instead of the additional PCI 806 or the SpCell PCI 808. The RAR for the PRACH transmission 820 associated with the additional PCI 806 may be sent by the SpCell PCI 808 or the additional PCI 806. The configuration may be specifically configured via RRC as an additional PCI 806 or a group of additional PCIs to which the additional PCI 806 belongs.

[0118] In some aspects, the UE 802 may be configured to monitor a CSS set in a CORESET associated with the additional PCI 806 and associated with the serving cell PCI, regardless of whether the active TCI state is associated with the additional PCI 806 or the SpCellPCI 808. In this aspect, a RAR for a PRACH transmission 820 associated with the SpCell PCI 808 or a RAR for a PRACH transmission 820 associated with the additional PCI 806 may be sent by the SpCell PCI 808 or the additional PCI 806. The configuration may be specifically configured via RRC to be an additional PCI 806 or a set of additional PCIs to which the additional PCI 806 belongs.

[0119] In one aspect, the UE 802 may be configured to monitor a CSS in a CORESET associated with the additional PCI 806 or to monitor a CSS in a CORESET associated with the SpCell PCI 808. In other words, a first CSS may be located in a first CORESET associated with the additional PCI 806, and a second CSS may be located in a second CORESET associated with the SpCell PCI 808. The UE 802 may be configured to monitor a RAR window based on a CORESET. The RAR window associated with the additional PCI 806 for PRACH may be determined based on a CORESET that is configured with the additional CSS set or configured with the additional PCI 806. The RAR window associated with the additional PCI 806 for the PRACH transmission 820 may start at the first symbol of the earliest CORESET at which the UE 802 is configured to receive a CSS in a CORESET associated with the additional PCI 806. In other words, the RAR window may start a fixed number of symbols after the last symbol of the PRACH opportunity corresponding to the PRACH transmission 820. For a CORESET associated with the SpCell PCI 808, the UE 802 may not expect an active TCI state for a CORESET associated with the additional PCI 806. In one aspect, for a CORESET associated with the additional PCI 806, the UE 802 may not expect an active TCI state for a CORESET associated with the SpCell PCI 808. On the other hand, for a CORESET associated with the additional PCI 806, the active TCI state for the CORESET may be associated with the SpCell PCI 808 or the additional PCI 806.

[0120] In one aspect, the UE 802 may be configured to monitor the CSS associated with the additional PCI 806 in the CORESET when the active TCI state is associated with the additional PCI 806. The RAR 824 may be sent from the additional PCI 806 and may not be sent from the SpCellPCI 808 or the SpCell PCI 808. The configuration may be specifically configured via RRC to the additional PCI 806 or a group of additional PCIs to which the additional PCI 806 belongs.

[0121] On the other hand, the UE 802 may be configured to monitor the CSS associated with the additional PCI 806 in the CORESET, regardless of whether the active TCI state is associated with the additional PCI 806 or the SpCell PCI 808. The RAR 824 may be sent from the SpCell PCI 808 or the additional PCI 806. The configuration may be specifically configured via RRC to the additional PCI 806 or a group of additional PCIs to which the additional PCI 806 belongs.

[0122] On the other hand, the UE 802 may be configured to monitor the CSS associated with the additional PCI 806 in the first CORESET associated with the additional PCI 806 or the CSS associated with the SpCell PCI 808 in the second CORESET associated with the SpCell PCI 808. If the active TCI state of the first CORESET is associated with the additional PCI 806, the UE 802 may monitor the CSS associated with the additional PCI 806 in the first CORESET associated with the additional PCI 806. The UE 802 may monitor the CSS associated with the additional PCI 806 in the first CORESET associated with the additional PCI 806, regardless of whether the active TCI state is associated with the SpCell PCI 808 or the additional PCI 806. The RAR 824 may be sent by the additional PCI 806 or the SpCell PCI 808. The configuration may be specifically configured via RRC to the additional PCI 806 or a group of additional PCIs to which the additional PCI 806 belongs.

[0123] In some aspects, the TCI activation selected by the MAC-CE 822 may not be received by the UE 802 in time for the UE 802 to monitor the RAR window for RAR 824. In some aspects, the TCI activation selected by the MAC-CE 822 may not be activated by the UE 802 in time for the UE 802 to monitor the RAR window for RAR 824. In one aspect, if the UE 802 does not activate the TCI in time for the UE 802 to monitor the RAR window for RAR 824, the UE 802 may send an indication of the error in the ACK 823. For example, the UE 802 may send a time period offset in the ACK 823 corresponding to the delay in monitoring the RAR window. In response, the SpCell PCI 808 may indicate to the additional PCI 806 to ensure that the RAR 824 can be sent from the additional PCI 806 within the new RAR window. In some aspects, the additional PCI 806 may receive the ACK 823 and apply the corresponding time period offset.

[0124] In one aspect, if the UE 802 does not activate the TCI in time for the UE 802 to monitor the RAR window for the RAR 824, the UE 802 may not monitor the CSS set associated with the SpCell PCI 808 in the CORESET if the active TCI state is associated with the SpCell PCI 808. The UE 802 may not consider the reception of the RAR 824 to be successful. The UE 802 may send a NACK to the additional PCI 806 in the UL transmission 826, which may serve as a request to retransmit the RAR 824. In one aspect, the UE 802 may increment a transmission counter.

[0125] In one aspect, if the UE 802 does not activate the TCI in time for the UE 802 to monitor the RAR window for the RAR 824, the UE 802 may monitor the CSS set associated with the SpCell PCI 808 in the CORESET if the active TCI state is associated with the SpCell PCI 808. If the UE 802 does not receive the RAR from both the SpCell PCI 808 and the additional PCI 806, the UE 802 may not consider the reception of the RAR 824 to be successful. If the UE 802 receives the RAR from the SpCell PCI 808 but not the additional PCI 806, the UE 802 may apply the received TA to the UL transmission to the SpCell PCI 808. If the UE 802 does not receive the RAR 824 from the additional PCI 806, the UE 802 may not consider the reception of the RAR to be successful. The UE 802 may ignore the RAR received from the SpCell PCI 808. In some aspects, the UE 802 may be configured to switch between not considering the reception of the RAR 824 successful if the UE 802 does not receive the RAR from both the SpCell PCI 808 and the additional PCI 806, or not considering the reception of the RAR 824 successful if the UE 802 does not receive the RAR 824 from the additional PCI 806. The SpCell PCI 808 may be configured to select one aspect or the other by sending an indication in the MAC-CE 822 to switch the UE 802 between the two aspects.

[0126] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 430, UE 702, UE 802; device 1104). At 904, the UE may receive a configuration of a second PCI from a serving cell, the serving cell being associated with a first PCI different from the second PCI. For example, 904 may be performed by Figure 7702 in the UE, which may receive the configuration of the second PCI as a PCI configuration 712 from the serving cell PCI 704 or a PCI configuration 716 from the SpCell PCI 708. The serving cell PCI 704 may be associated with a PCI that is different from the PCI of the additional PCI 706. The SpCell PCI 708 may be associated with a PCI that is different from the PCI of the additional PCI 706. In addition, 904 may be performed by Fig.11 Component 198 of device 1104 is executed.

[0127] At 906, the UE may receive a PDCCH command from a network node associated with the second PCI, the PDCCH command including an indication of PRACH transmission. In some aspects, the PDCCH command may be received from the serving cell PCI 704 or from the SpCell PCI 708 (not shown here). For example, 906 may be received by Figure 7 702 in the UE, which may receive a PDCCH command 718 from the additional PCI 706. The PDCCH command 718 may be associated with an indication of a PRACH transmission 720. In addition, 906 may be performed by Fig.11 Component 198 of device 1104 is executed.

[0128] At 908, the UE may send a PRACH transmission associated with the additional PCI in a PRACH opportunity. For example, 908 may be performed by Figure 7 702 in the UE, which may send a PRACH transmission 720 associated with the additional PCI 706 in the PRACH opportunity. In addition, 908 may be performed by Fig.11 Component 198 of device 1104 is executed.

[0129] At 910, the UE may receive a MAC-CE that activates a TCI state associated with a second PCI for a first CORESET. For example, 910 may be performed by Figure 7 702 in the UE, the UE may receive a MAC-CE 722 from the serving cell PCI 704. The MAC-CE may activate the TCI state associated with the second PCI for the first CORESET. In addition, 910 may be performed by Fig.11 Component 198 of device 1104 is executed.

[0130] At 912, the UE may monitor at least one first CSS in the first CORESET during a RAR window associated with the second PCI. The RAR window may be based on the time position of the PRACH opportunity. For example, 912 may be composed of Figure 7Executed by UE 702 in the UE, the UE may monitor at least one first CSS in the first CORESET during the RAR window associated with the additional PCI 706. In addition, 912 may be performed by Fig.11 Component 198 of device 1104 is executed.

[0131] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310; TRP 410, TRP 420, additional PCI 706, additional PCI 806; network entity 1102, network entity 1202). At 1002, the network node may receive a configuration of at least one first CSS in a first CORESET associated with a second PCI from a serving cell. The serving cell may be associated with a first PCI different from the second PCI. The network node may be associated with the second PCI. For example, 1002 may be performed by additional PCI 706, which may receive PCI configuration 713 from serving cell PCI 704 and / or SpCell PCI 708. The configuration may be received via inter-TRP communication or coordination. PCI configuration 713 may define at least one first CSS in a first CORESET associated with a PCI of the additional PCI. The PCI of the serving cell PCI 704 may be different from the PCI of the additional PCI 706. The PCI of the SpCell PCI 708 may be different from the PCI of the additional PCI 706. The additional PCI 706 may be associated with the additional PCI of the PCI configuration 713. Fig.12 Component 199 of network entity 1202 in is executed.

[0132] At 1004, the network node may send a PDCCH order to the UE, the PDCCH order including an indication of a PRACH transmission. For example, 1004 may be performed by additional PCI 706, which may send a PDCCH order 718 to the UE 702. The PDCCH order 718 may include an indication of a PRACH transmission 720. Additionally, 1004 may be performed by Fig.12 Component 199 of network entity 1202 in is executed.

[0133] At 1006, the network node may receive a PRACH transmission associated with the second PCI from the UE during the PRACH opportunity. For example, 1006 may be performed by the additional PCI 706, which may receive the PRACH transmission 720 from the UE 702 during the PRACH opportunity. In addition, 1006 may be performed by Fig.12 Component 199 of network entity 1202 in is executed.

[0134] At 1008, the network node may, in response to receiving the PRACH transmission, send a RAR message to the UE during a RAR window associated with the second PCI. The RAR window may be based on a temporal position of the PRACH opportunity. For example, 1008 may be performed by an additional PCI 706, which may send a RAR 724 to the UE 702 during a RAR window associated with the additional PCI 706. The sending may be in response to receiving the PRACH transmission 720. The RAR window may be based on a temporal position of a PRACH opportunity of the PRACH transmission 720. For example, the RAR window may be located 5 ms after the end of the PRACH opportunity of the PRACH transmission 720. Additionally, 1008 may be performed by Fig.12 Component 199 of network entity 1202 in is executed.

[0135] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), a memory 1126, a power supply 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using antennas 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or the RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The memory 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1124 / application processor 1106, enables the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software. The cellular baseband processor 1124 / application processor 1106 may be a component of the UE 350 and may include a memory 360 and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 1104 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1124 and / or the application processor 1106, while in another configuration, the device 1104 may be an entire UE (eg, see. Figure 3 UE 350) and includes additional modules of device 1104.

[0136] As discussed above, component 198 is configured to receive a first RRC configuration from a serving cell, the first RRC configuration including a first configuration of a first PCI and a second PCI. The serving cell may be associated with a first PCI, and an additional cell may be associated with the second PCI different from the first PCI. Component 198 may be configured to receive a PDCCH order from a network node, the PDCCH order including an indication of a PRACH transmission associated with the second PCI. Component 198 may be configured to transmit the PRACH transmission associated with the second PCI during a PRACH opportunity. Component 198 may be configured to monitor at least one first CSS in a first CORESET during a RAR window associated with the second PCI. The RAR window may be based on the time position of the PRACH opportunity. Component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. As shown, device 1104 may include multiple components configured for various functions. In one configuration, the apparatus 1104 (and in particular the cellular baseband processor 1124 and / or the application processor 1106) includes means for receiving a configuration of a second PCI from a serving cell, the serving cell being associated with a first PCI different from the second PCI. The apparatus 1104 may include means for monitoring at least one first CSS in a first CORESET during a RAR window associated with the second PCI. The apparatus 1104 may include means for sending the PRACH transmission based on the PDCCH command. The RAR window may be based on the timing of the PRACH transmission. The apparatus 1104 may include means for receiving a PDCCH command from a network node associated with the second PCI, the PDCCH command including an indication of the PRACH transmission. The apparatus 1104 may include means for receiving an RRC configuration from the serving cell, the RRC configuration including a set of TCI states associated with the first CORESET. The apparatus 1104 may include means for receiving a MAC-CE including selecting a first TCI state as an active TCI state from a first TCI state and a second TCI state. The apparatus 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the active TCI state being associated with the second PCI different from the first PCI.The device 1104 may include a component for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the following: (a) the active TCI state is associated with the second PCI different from the first PCI, (b) the SpCell serving the UE configures the second PCI, and (c) the second PCI is associated with the CORESETPoolIndex for the serving cell and the SpCell or is associated with a timing advance group (TAG) TAG ID for the serving cell and the SpCell. The device 1104 may include a component for sending UE capabilities, the UE capabilities including a first indicator for monitoring the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI. The device 1104 may include a component for receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The apparatus 1104 may include means for receiving an RRC configuration including a second indicator for activating the capability for monitoring the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI. The apparatus 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the selection indicating the first TCI state as the active TCI state. The apparatus 1104 may include means for suppressing monitoring the at least one first CSS in the first CORESET during the RAR window in response to the selection indicating the second TCI state as the active TCI state. The apparatus 1104 may include means for receiving an RRC configuration including an indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window. The device 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the RRC configuration including the indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window. The device 1104 may include means for sending UE capabilities, the UE capabilities including a first indicator for the ability to monitor the at least one first CSS in the first CORESET when the SpCell configures the at least one first CSS in the first CORESET. The device 1104 may include means for suppressing monitoring the at least one first CSS in the first CORESET during the RAR window associated with at least one other second PCI. The device 1104 may include means for receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state.The device 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the selection indicating the first TCI state as the active TCI state. The device 1104 may include means for suppressing monitoring the at least one first CSS in the first CORESET during the RAR window in response to the selection indicating the second TCI state as the active TCI state. The device 1104 may include means for receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The device 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window and during a second RAR window associated with the first PCI in response to the selection indicating the first TCI state as the active TCI state. The device 1104 may include means for suppressing monitoring the at least one first CSS in the first CORESET during the RAR window in response to the selection indicating the second TCI state as the active TCI state. The device 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window and during a second RAR window associated with the first PCI. The device 1104 may include means for receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The device 1104 may include means for sending a UE capability including a first indicator of an ability to monitor the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI. The device 1104 may include means for receiving an RRC configuration including a first indicator that the first TCI state is associated with the at least one first CSS in the first CORESET and the second PCI and a second indicator that the second TCI state is associated with the at least one second CSS in the second CORESET and the first PCI. The device 1104 may include means for receiving a MAC-CE including selecting the first TCI state as the active TCI state from the first TCI state and the second TCI state. The apparatus 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window in response to the RRC configuration including the first indicator associating the first TCI state with the at least one first CSS in the first CORESET and the second PCI and indicating the selection of the first TCI state as the active TCI state. The apparatus 1104 may include means for receiving a MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state.The device 1104 may include means for monitoring the at least one first CSS in at least one of the first CORESET or the second CORESET during the RAR window in response to the selection indicating the first TCI state as the active TCI state. The device 1104 may include means for refraining from monitoring the at least one first CSS in at least one of the first CORESET or the second CORESET during the RAR window in response to the selection indicating the second TCI state as the active TCI state. The device 1104 may include means for receiving a MAC-CE including selecting the second TCI state as the active TCI state from the first TCI state and the second TCI state. The device 1104 may include means for monitoring the at least one first CSS in the first CORESET during the RAR window associated with the second PCI and during the second RAR window associated with the first PCI. The device 1104 may include means for receiving a RAR message during at least one of the RAR window associated with the second PCI and the second RAR window associated with the first PCI. The device 1104 may include a component for processing the RAR message in response to receiving the RAR message during the second RAR window associated with the first PCI. The device 1104 may include a component for suppressing processing the RAR message in response to receiving the RAR message during the second RAR window associated with the second PCI. The device 1104 may include a component for receiving the RAR message during at least one of the RAR window associated with the second PCI and the second RAR window associated with the first PCI. The device 1104 may include a component for processing the RAR message in response to receiving the RAR message during the RAR window associated with the second PCI. The device 1104 may include a component for suppressing processing the RAR message in response to receiving the RAR message during the second RAR window associated with the first PCI. The component may be a component 198 of the device 1104 configured to perform the functions recited by the component. As described above, the device 1104 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, these components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0137] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the component 199, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both the DU 1230 and the RU 1240; or the RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include a memory 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link such as an F1 interface. DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include memory 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include memory 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and memory 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0138] As discussed above, component 199 is configured to receive a configuration of at least one first CSS in a first CORESET associated with a second PCI from a serving cell. The serving cell may be associated with a first PCI different from the second PCI. The network node may be associated with the second PCI. Component 199 may be configured to send a PDCCH command to a UE, the PDCCH command including an indication of a PRACH transmission. Component 199 may be configured to receive the PRACH transmission associated with the second PCI from the UE during a PRACH opportunity. Component 199 may be configured to send a RAR message to the UE during a RAR window associated with the second PCI in response to receiving the PRACH transmission. Component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination thereof. Network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for receiving a configuration of at least one first CSS in a first CORESET associated with a second PCI from a serving cell associated with a first PCI different from the second PCI. The network entity 1202 may include a component for sending a RAR message to the UE during a RAR window associated with the second PCI. The network entity 1202 may include a component for sending a PDCCH order to the UE, the PDCCH order including an indication of a PRACH transmission. The network entity 1202 may include a component for receiving the PRACH transmission from the UE based on the PDCCH order. The RAR window may be based on the timing of the PRACH transmission. The component may be a component 199 of the network entity 1202 configured to perform the functions recorded by the component. As described above, the network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, these components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0139] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0140] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0141] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0142] A device configured to "output" data (such as, transmit, signal or message) may, for example, transmit the data using a transceiver, or may transmit the data to a device that transmits the data. A device configured to "obtain" data (such as, transmit, signal or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data.

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

[0144] Aspect 1 is a method of wireless communication at a UE, wherein the method may include: receiving a configuration of a second PCI from a serving cell, the serving cell being associated with a first PCI different from the second PCI. The method may include: monitoring at least one first CSS in a first CORESET during a RAR window associated with the second PCI.

[0145] Aspect 2 is a method according to aspect 1, wherein the method may include: receiving a PDCCH command from a network node associated with the second PCI, the PDCCH command including an indication of a PRACH transmission. The method may include: sending the PRACH transmission based on the PDCCH command. The RAR window may be based on the timing of the PRACH transmission.

[0146] Aspect 3 is a method according to aspect 2, wherein monitoring the at least one first CSS in the first CORESET during the RAR window associated with the second PCI may be responsive to the second PCI being associated with the PRACH or the RAR window.

[0147] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the method may include: receiving an RRC configuration from the serving cell, the RRC configuration including a TCI state set associated with the first CORESET.

[0148] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the first CORESET may include a first TCI state associated with the at least one first CSS and the second PCI in the first CORESET. The first CORESET may include a second TCI state associated with the at least one first CSS and the first PCI in the first CORESET.

[0149] Aspect 6 is a method according to aspect 5, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting the first TCI state as an active TCI state from the first TCI state and the second TCI state.

[0150] Aspect 7 is a method according to aspect 6, wherein the serving cell may include a SpCell serving the UE.

[0151] Aspect 8 is a method according to aspect 7, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may be associated with the second PCI different from the first PCI in response to the active TCI state.

[0152] Aspect 9 is a method according to aspect 6, wherein the serving cell may not include a SpCell serving the UE.

[0153] Aspect 10 is a method according to Aspect 9, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may be responsive to (a) the active TCI state being associated with the second PCI different from the first PCI, (b) the SpCell serving the UE is configured with the second PCI, and (c) the second PCI is associated with the CORESETPoolIndex for the serving cell and the SpCell or is associated with a timing advance group (TAG) TAG ID for the serving cell and the SpCell.

[0154] Aspect 11 is a method according to any one of Aspects 1 to 10, wherein the method may include: sending UE capabilities, the UE capabilities including a first indicator for monitoring the ability of the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI.

[0155] Aspect 12 is a method according to aspect 11, wherein the method may include: receiving an RRC configuration, the RRC configuration including a second indicator for activating the capability for monitoring the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI.

[0156] Aspect 13 is a method according to any one of aspects 1 to 12, wherein the RRC configuration may be associated with a set of additional PCIs. The set of additional PCIs may include the second PCI.

[0157] Aspect 14 is a method according to aspect 5, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the first TCI state as the selection of the active TCI state, monitoring the at least one first CSS in the first CORESET during the RAR window. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the second TCI state as the selection of the active TCI state, suppressing monitoring the at least one first CSS in the first CORESET during the RAR window.

[0158] Aspect 15 is a method according to aspect 5, wherein the method may include: receiving an RRC configuration, the RRC configuration including an indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to the RRC configuration including the indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window, monitoring the at least one first CSS in the first CORESET during the RAR window.

[0159] Aspect 16 is a method according to aspect 15, wherein the RRC configuration may be associated with a set of additional PCIs. The set of additional PCIs may include the second PCI.

[0160] Aspect 17 is a method according to aspect 15, wherein the method may include: refraining from monitoring the at least one first CSS in the first CORESET during the RAR window associated with at least one other second PCI.

[0161] Aspect 18 is a method according to any one of aspects 1 to 17, wherein the first CORESET may include a first TCI state associated with the at least one first CSS and the second PCI in the first CORESET. The first CORESET may include a second TCI state associated with at least one second CSS and the first PCI in at least one of the first CORESET or the second CORESET.

[0162] Aspect 19 is a method according to aspect 18, wherein the serving cell may include a SpCell serving the UE. The SpCell may configure the at least one first CSS in the first CORESET.

[0163] Aspect 20 is a method according to aspect 19, wherein the method may include: sending UE capabilities, the UE capabilities including a first indicator for monitoring the capability of the at least one first CSS in the first CORESET when the SpCell configures the at least one first CSS in the first CORESET.

[0164] Aspect 21 is a method according to aspect 18, wherein the serving cell may not include a SpCell serving the UE. The SpCell may configure the second PCI. The second PCI may be associated with a CORESETPoolIndex for the serving cell and the SpCell or associated with a TAG ID for the serving cell and the SpCell. The SpCell may configure the at least one first CSS in the first CORESET.

[0165] Aspect 22 is a method according to aspect 18, wherein the serving cell may not include a SpCell serving the UE. The serving cell may configure the second PCI. The SpCell may not configure the second PCI. The serving cell may configure the at least one first CSS in the first CORESET.

[0166] Aspect 23 is a method according to aspect 18, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The second TCI state may be associated with the at least one second CSS in the first CORESET and the first PCI. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the first TCI state as the selection of the active TCI state, monitoring the at least one first CSS in the first CORESET during the RAR window. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the second TCI state as the selection of the active TCI state, suppressing monitoring of the at least one first CSS in the first CORESET during the RAR window.

[0167] Aspect 24 is a method according to aspect 18, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The second TCI state may be associated with the at least one second CSS in the first CORESET and the first PCI. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the selection of the first TCI state as the active TCI state, monitoring the at least one first CSS in the first CORESET during the RAR window and during a second RAR window associated with the first PCI. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the selection of the second TCI state as the active TCI state, suppressing monitoring of the at least one first CSS in the first CORESET during the RAR window.

[0168] Aspect 25 is a method according to aspect 18, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may include monitoring the at least one first CSS in the first CORESET during the RAR window and during a second RAR window associated with the first PCI. The second TCI state may be associated with the at least one second CSS in the first CORESET and the first PCI.

[0169] Aspect 26 is a method according to aspect 18, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. The method may include: sending UE capabilities, the UE capabilities including a first indicator for monitoring the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI.

[0170] Aspect 27 is a method according to aspect 18, wherein the method may include: receiving an RRC configuration, the RRC configuration including a first indicator that the first TCI state is associated with the at least one first CSS in the first CORESET and the second PCI, and a second indicator that the second TCI state is associated with the at least one second CSS in the second CORESET and the first PCI. The method may include: receiving a MAC-CE, the MAC-CE including selecting the first TCI state as an active TCI state from the first TCI state and the second TCI state. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to the RRC configuration including the first indicator that the first TCI state is associated with the at least one first CSS in the first CORESET and the second PCI and indicating the selection of the first TCI state as the active TCI state, monitoring the at least one first CSS in the first CORESET during the RAR window.

[0171] Aspect 28 is a method according to aspect 18, wherein the method may include: receiving a MAC-CE, the MAC-CE including selecting an active TCI state from the first TCI state and the second TCI state. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the first TCI state as the selection of the active TCI state, monitoring the at least one first CSS in at least one of the first CORESET or the second CORESET during the RAR window. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to indicating the second TCI state as the selection of the active TCI state, suppressing monitoring the at least one first CSS in at least one of the first CORESET or the second CORESET during the RAR window.

[0172] Aspect 29 is a method according to any one of aspects 1 to 28, wherein the first CORESET may include a first TCI state associated with the at least one first CSS in the first CORESET and the second PCI. The first CORESET may include a second TCI state associated with the at least one first CSS in at least one of the first CORESET or the second CORESET and the first PCI. The method may include: receiving a MAC-CE, the MAC-CE including selecting the second TCI state as an active TCI state from the first TCI state and the second TCI state. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: monitoring the at least one first CSS in the first CORESET during the RAR window associated with the second PCI and during the second RAR window associated with the first PCI.

[0173] Aspect 30 is a method according to aspect 29, wherein the method may include: receiving a RAR message during at least one of the RAR window associated with the second PCI and the second RAR window associated with the first PCI. The method may include: in response to receiving the RAR message during the second RAR window associated with the first PCI, processing the RAR message. The method may include: in response to receiving the RAR message during the second RAR window associated with the second PCI, refraining from processing the RAR message.

[0174] Aspect 31 is a method according to aspect 19, wherein the method may include: receiving a RAR message during at least one of the RAR window associated with the second PCI and the second RAR window associated with the first PCI. The method may include: in response to receiving the RAR message during the RAR window associated with the second PCI, processing the RAR message. The method may include: in response to receiving the RAR message during the second RAR window associated with the first PCI, refraining from processing the RAR message.

[0175] Aspect 32 is a method of wireless communication at a network node, wherein the method may include receiving, from a serving cell associated with a first PCI different from a second PCI, a configuration of at least one first CSS in a first CORESET associated with the second PCI. The method may include sending a RAR message to a UE during a RAR window associated with the second PCI.

[0176] Aspect 33 is a method according to aspect 32, wherein the method may include: sending a PDCCH command to the UE, the PDCCH command including an indication of a PRACH transmission. The method may include: receiving the PRACH transmission from the UE based on the PDCCH command. The RAR window may be based on the timing of the PRACH transmission.

[0177] Aspect 34 is an apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 1 to 33 based at least in part on information stored in the memory.

[0178] Aspect 35 is the apparatus of aspect 34, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0179] Aspect 36 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 33.

[0180] Aspect 37 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 33.

[0181] Aspect 38 is a method for wireless communication at a UE, wherein the method may include: receiving a first radio resource control (RRC) configuration from a serving cell, the first radio resource control (RRC) configuration including a first physical cell identifier (ID) (PCI) and a first configuration of a second PCI. The serving cell may be associated with a first PCI, and an additional cell may be associated with the second PCI different from the first PCI. The method may include: sending a PRACH transmission associated with the second PCI during a physical random access channel (PRACH) opportunity. The method may include: monitoring at least one first common search space (CSS) in a first control resource set (CORESET) during a random access response (RAR) window associated with the second PCI. The RAR window may be based on the time position of the PRACH opportunity.

[0182] Aspect 39 is a method according to aspect 38, wherein the method may include: receiving a physical downlink control channel (PDCCH) command from a network node, the physical downlink control channel (PDCCH) command including an indication of the PRACH transmission associated with the second PCI.

[0183] Aspect 40 is a method according to aspects 38 to 39, wherein the method may include: receiving a medium access control (MAC) control element (MAC-CE), the medium access control (MAC) control element (MAC-CE) including an indicator for activating a first TCI state associated with the second PCI for the first CORESET.

[0184] Aspect 41 is a method according to any one of aspects 38 to 40, wherein the serving cell may include a SpCell serving the UE.

[0185] Aspect 42 is a method according to aspects 38 to 41, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to the active TCI state of the first CORESET being associated with the second PCI different from the first PCI, monitoring the at least one first CSS in the first CORESET during the RAR window.

[0186] Aspect 43 is a method according to aspect 38, wherein the serving cell may be different from the SpCell serving the UE. The method may also include: receiving a second RRC configuration, the second RRC configuration including a second configuration of a third PCI different from the first PCI. The SpCell may be associated with the third PCI

[0187] Aspect 44 is a method according to aspect 43, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may include: in response to (a) the active TCI state being associated with the second PCI different from the first PCI, (b) the SpCell serving the UE is configured with the second PCI associated with a third PCI, and (c) the second PCI is associated with the same CORESETPoolIndex for the serving cell and the SpCell or is associated with the same TAG ID for the serving cell and the SpCell, monitoring the at least one first CSS in the first CORESET during the RAR window.

[0188] Aspect 45 is a method according to aspects 38 to 44, wherein the method may include: sending UE capabilities, the UE capabilities including a first indicator for monitoring the at least one first CSS in the first CORESET when the active TCI state is associated with the second PCI.

[0189] Aspect 46 is a method according to aspect 45, wherein the first RRC configuration may include a second indicator, the second indicator being used to activate the capability for monitoring the at least one first CSS in the first CORESET in response to the active TCI state being associated with the second PCI.

[0190] Aspect 47 is a method according to any one of aspects 38 to 46, wherein the first configuration may include a set of additional PCIs. The set of additional PCIs may include the second PCI.

[0191] Aspect 48 is a method according to aspect 46, wherein the first configuration may include one additional PCI. The one additional PCI may be the second PCI.

[0192] Aspect 49 is a method according to aspect 43, wherein the method may include: in response to the active TCI state of the first CORESET being associated with the third PCI, refraining from monitoring the at least one first CSS in the first CORESET during the RAR window.

[0193] Aspect 50 is a method according to aspect 43, wherein the method may include: in response to the active TCI state of the first CORESET being associated with the third PCI associated with the SpCell, monitoring the at least one first CSS in the first CORESET during the RAR window.

[0194] Aspect 51 is a method according to aspect 43, wherein the second RRC configuration may include an indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window in response to an active TCI state of the first CORESET being associated with the third PCI associated with the SpCell. Monitoring the at least one first CSS in the first CORESET during the RAR window may include: monitoring the at least one first CSS in the first CORESET during the RAR window in response to (a) the second RRC configuration including the indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window and (b) the active TCI state of the first CORESET being associated with the third PCI.

[0195] Aspect 52 is a method according to aspect 51, wherein the second RRC configuration may be associated with a set of additional PCIs. The set of additional PCIs may include the second PCI.

[0196] Aspect 53 is a method according to aspect 51, wherein the second RRC configuration may be associated with one PCI. The one PCI may include the second PCI.

[0197] Aspect 54 is a method according to aspects 38 to 53, wherein the method may include: receiving a configuration of at least one second CSS in a second CORESET on a special cell (SpCell). The SpCell may be associated with a third PCI. The method may include: receiving a configuration of the at least one first CSS in the first CORESET for a set of additional PCIs. The set of additional PCIs may include the second PCI. The first CSS may be different from the second CSS.

[0198] Aspect 55 is a method according to aspect 54, wherein the serving cell may include a special cell (SpCell) serving the UE. The SpCell may configure the at least one first CSS in the first CORESET.

[0199] Aspect 56 is a method according to aspect 54, wherein the serving cell may not include a special cell (SpCell) serving the UE. The SpCell may configure the second PCI. The SpCell may be associated with a third PCI different from the first PCI. The second PCI may be associated with the same CORESETPoolIndex for the serving cell and the SpCell or with the same timing advance group (TAG) ID for the serving cell and the SpCell. The SpCell may configure the at least one first CSS in the first CORESET

[0200] Aspect 57 is a method according to aspect 54, wherein the serving cell may not include a special cell (SpCell) serving the UE. The serving cell may configure the second PCI. The SpCell may not configure the second PCI. The SpCell may be associated with a third PCI. The serving cell may configure the at least one first CSS in the first CORESET.

[0201] Aspect 58 is a method according to aspect 54, wherein the second CORESET may be the same as the first CORESET.

[0202] Aspect 59 is a method according to aspect 58, wherein the method may include: in response to the first active TCI state of the first CORESET being associated with the second PCI, monitoring the at least one first CSS in the first CORESET during the RAR window. The method may include: in response to the second active TCI state of the second CORESET being associated with the second PCI, suppressing monitoring the at least one second CSS in the second CORESET during the RAR window. The method may include: in response to the second active TCI state of the second CORESET being associated with the third PCI, monitoring the at least one second CSS in the second CORESET during the RAR window. The method may include: in response to the first active TCI state of the first CORESET being associated with the third PCI, suppressing monitoring the at least one first CSS in the first CORESET during the RAR window.

[0203] Aspect 60 is a method according to aspect 58, wherein the method may include: in response to the first active TCI state of the first CORESET and the second CORESET being associated with the second PCI, monitoring both the at least one first CSS in the first CORESET and the at least one second CSS in the second CORESET during the RAR window. The method may include: in response to the second active TCI state of the second CORESET being associated with the third PCI, monitoring the second CSS in the second CORESET during the RAR window. The method may include: in response to the second active TCI state of the second CORESET being associated with the third PCI, refraining from monitoring the at least one first CSS in the first CORESET during the RAR window.

[0204] Aspect 61 is a method according to aspect 58, wherein monitoring the at least one first CSS in the first CORESET during the RAR window may include: monitoring both the at least one first CSS in the first CORESET and the second CSS in the second CORESET during the RAR window.

[0205] Aspect 62 is a method according to aspect 54, wherein the second CORESET may be different from the first CORESET, and the RAR window associated with the second PCI may be based on the first CORESET.

[0206] Aspect 63 is a method according to aspect 62, wherein the method may include: in response to the active TCI state of the first CORESET being associated with the second PCI, monitoring the at least one first CSS in the first CORESET during the RAR window. The method may include: refraining from monitoring the second CSS in the second CORESET during the RAR window.

[0207] Aspect 64 is a method according to aspect 62, wherein the method may include: in response to the first active TCI state of the second CORESET being associated with the first PCI or the second PCI or in response to the second active TCI state of the second CORESET being associated with the second PCI or the third PCI, monitoring at least one first CSS in the first CORESET during the RAR window. The method may include: refraining from monitoring the second CSS in the second CORESET during the RAR window.

[0208] Aspect 65 is a method according to aspect 62, wherein the method may include: monitoring both the at least one first CSS in the first CORESET and the second CSS in the second CORESET during the RAR window. Monitoring the at least one first CSS in the first CORESET may include: monitoring the at least one first CSS in the first CORESET in response to the active TCI state of the first CORESET being associated with the second PCI. Monitoring the at least one first CSS in the first CORESET may include: monitoring the at least one first CSS in the first CORESET in response to the active TCI state of the first CORESET being associated with the first PCI or the second PCI or in response to the active TCI state of the first CORESET being associated with the second PCI and the third PCI.

[0209] Aspect 66 is a method according to aspects 38 to 65, wherein the method may include: reporting the random access response as unsuccessful in response to at least one of the following: (a) failure to receive a medium access control (MAC) control element (MAC-CE), the medium access control (MAC) control element (MAC-CE) including an indicator for activating an active TCI state of the first CORESET; (b) the second CORESET is associated with the second PCI; or (c) in response to the active TCI state being associated with the first PCI or with a third PCI associated with a special cell (SpCell), not monitoring the at least one first CSS in the first CORESET.

[0210] Aspect 67 is a method according to aspects 38 to 66, wherein the method may include: receiving a RAR message during the RAR window associated with the second PCI. The method may include: processing the RAR message in response to a failure to receive a medium access control (MAC) control element (MAC-CE), the medium access control (MAC) control element (MAC-CE) including an indicator for activating a TCI state associated with the second PCI of the first CORESET or the second CORESET.

[0211] Aspect 68 is a method of wireless communication at a network node. The method may include receiving, from a serving cell, a configuration of at least one first common search space (CSS) in a first control resource set (CORESET) associated with a second physical cell identifier (ID) (PCI). The serving cell may be associated with a first PCI different from the second PCI. The network node may be associated with the second PCI. The method may include receiving, from the UE during a physical random access channel (PRACH) opportunity, a PRACH transmission associated with the second PCI. The method may include, in response to receiving the PRACH transmission, sending a random access response (RAR) message to the UE during a RAR window associated with the second PCI. The RAR window may be based on a temporal position of the PRACH opportunity.

[0212] Aspect 69 is a method according to aspect 68, wherein the method may include: sending a physical downlink control channel (PDCCH) order to the UE, the physical downlink control channel (PDCCH) order including an indication of the PRACH transmission.

[0213] Aspect 70 is a method according to any one of aspects 68 to 69, wherein the method may include

[0214] Aspect 71 is an apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 38 to 70 based at least in part on information stored in the memory.

[0215] Aspect 72 is the apparatus of aspect 71, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0216] Aspect 73 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 38 to 70.

[0217] Aspect 74 is a computer-readable medium (eg, a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 38 to 70 .

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving a first radio resource control (RRC) configuration from a serving cell, the first radio resource control (RRC) configuration comprising a first configuration of a first physical cell identifier (ID) (PCI) and a second PCI, wherein the serving cell is associated with the first PCI and an additional cell is associated with the second PCI different from the first PCI; transmitting, during a physical random access channel (PRACH) opportunity, a PRACH transmission associated with the second PCI; as well as At least one first common search space (CSS) in a first control resource set (CORESET) is monitored during a random access response (RAR) window associated with the second PCI, wherein the RAR window is based on a time position of the PRACH opportunity.

2. The device according to claim 1, further comprising: a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: A physical downlink control channel (PDCCH) order is received from a network node via the transceiver, the physical downlink control channel (PDCCH) order including an indication of the PRACH transmission associated with the second PCI.

3. The apparatus of claim 1, wherein the serving cell comprises a special cell (SpCell).

4. The device according to claim 1, wherein: In order to monitor the at least one first CSS in the first CORESET during the RAR window, the at least one processor is further configured to: in response to the active TCI state of the first CORESET being associated with the second PCI different from the first PCI, monitor the at least one first CSS in the first CORESET during the RAR window.

5. The apparatus of claim 1, wherein the serving cell is different from a special cell (SpCell), wherein the at least one processor is further configured to: A second RRC configuration is received, the second RRC configuration comprising a second configuration of a third PCI different from the first PCI, wherein the SpCell is associated with the third PCI.

6. The device according to claim 5, wherein: In order to monitor the at least one first CSS in the first CORESET during the RAR window, the at least one processor is further configured to: monitor the at least one first CSS in the first CORESET during the RAR window in response to (a) the active TCI state of the first CORESET is associated with the second PCI different from the first PCI, (b) the second RRC configuration includes the second PCI, and (c) the second PCI is associated with the same CORESETPoolIndex for the serving cell and the SpCell or is associated with the same timing advance group (TAG) TAGID for the serving cell and the SpCell.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: UE capabilities are sent, the UE capabilities comprising a first indicator for monitoring the at least one first CSS in the first CORESET in response to an active TCI state of the first CORESET being associated with the second PCI.

8. The apparatus of claim 7, wherein the first RRC configuration comprises a second indicator for activating the capability for monitoring the at least one first CSS in the first CORESET in response to the active TCI state being associated with the second PCI.

9. The apparatus of claim 1, wherein the first configuration further comprises a set of additional PCIs, wherein the set of additional PCIs comprises the second PCI.

10. The apparatus of claim 1, wherein the first configuration further comprises an additional PCI, wherein the additional PCI comprises the second PCI.

11. The apparatus of claim 5, wherein the at least one processor is further configured to: In response to an active TCI state of the first CORESET being associated with the third PCI, monitoring of the at least one first CSS in the first CORESET is suppressed during the RAR window.

12. The apparatus of claim 5, wherein the at least one processor is further configured to: In response to an active TCI state of the first CORESET being associated with the third PCI, monitoring the at least one first CSS in the first CORESET during the RAR window.

13. The apparatus of claim 5, wherein the second RRC configuration further comprises: an indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window in response to an active TCI state of the first CORESET being associated with the third PCI associated with the SpCell, wherein, to monitor the at least one first CSS in the first CORESET during the RAR window, the at least one processor is further configured to: In response to (a) the second RRC configuration including the indicator for enabling monitoring of the at least one first CSS in the first CORESET during the RAR window and (b) the active TCI state of the first CORESET is associated with the third PCI, monitoring the at least one first CSS in the first CORESET during the RAR window.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a first configuration of at least one second CSS in a second CORESET on a special cell (SpCell), wherein the SpCell is associated with a third PCI; and A second configuration of the at least one first CSS in the first CORESET for a set of additional PCIs is received, wherein the set of additional PCIs includes the second PCI, wherein the first CSS is different from the second CSS.

15. The apparatus according to claim 14, wherein the serving cell comprises the SpCell serving the UE, wherein the SpCell configures the at least one first CSS in the first CORESET.

16. An apparatus according to claim 14, wherein the serving cell does not include the SpCell serving the UE, wherein the SpCell configures the second PCI, wherein the SpCell is associated with the third PCI different from the first PCI, wherein the second PCI is associated with the same CORESETPoolIndex for the serving cell and the SpCell or is associated with the same timing advance group (TAG) ID for the serving cell and the SpCell, and wherein the SpCell configures the at least one first CSS in the first CORESET.

17. The apparatus according to claim 14, wherein the serving cell does not include the SpCell serving the UE, wherein the serving cell configures the second PCI, wherein the SpCell is not configured with the second PCI, wherein the SpCell is associated with the third PCI, and wherein the serving cell configures the at least one first CSS in the first CORESET.

18. The apparatus of claim 14, wherein the second CORESET is the same as the first CORESET.

19. The apparatus of claim 18, wherein the at least one processor is further configured to: monitoring the at least one first CSS in the first CORESET during the RAR window in response to a first active TCI state of the first CORESET being associated with the second PCI; refraining from monitoring the at least one second CSS in the second CORESET during the RAR window in response to a second active TCI state of the second CORESET being associated with the second PCI; monitoring the at least one second CSS in the second CORESET during the RAR window in response to the second active TCI state of the second CORESET being associated with the third PCI; as well as In response to the first active TCI state of the first CORESET being associated with the third PCI, monitoring the at least one first CSS in the first CORESET is suppressed during the RAR window.

20. The apparatus of claim 18, wherein the at least one processor is further configured to: monitoring both the at least one first CSS in the first CORESET and the at least one second CSS in the second CORESET during the RAR window in response to the first active TCI states of the first CORESET and the second CORESET being associated with the second PCI; In response to a second active TCI state of the second CORESET being associated with the third PCI, monitoring the second CSS in the second CORESET during the RAR window; and In response to the second active TCI state of the second CORESET being associated with the third PCI, refraining from monitoring the at least one first CSS in the first CORESET during the RAR window.

21. The device according to claim 18, wherein To monitor the at least one first CSS in the first CORESET during the RAR window, the at least one processor is further configured to: Both the at least one first CSS in the first CORESET and the second CSS in the second CORESET are monitored during the RAR window.

22. The apparatus of claim 14, wherein the second CORESET is different from the first CORESET and the RAR window associated with the second PCI is based on the first CORESET.

23. The apparatus of claim 22, wherein the at least one processor is further configured to: In response to an active TCI state of the first CORESET being associated with the second PCI, monitoring the at least one first CSS in the first CORESET during the RAR window; and Monitoring of the second CSS in the second CORESET is suppressed during the RAR window.

24. The apparatus of claim 22, wherein the at least one processor is further configured to: In response to a first active TCI state of the second CORESET being associated with the first PCI or the second PCI or in response to a second active TCI state of the second CORESET being associated with the second PCI or the third PCI, monitoring at least one first CSS in the first CORESET during the RAR window; and Monitoring of the second CSS in the second CORESET is suppressed during the RAR window.

25. The apparatus of claim 22, wherein the at least one processor is further configured to: monitoring the at least one first CSS in the first CORESET and the second CSS in the second CORESET during the RAR window, wherein: To monitor the at least one first CSS in the first CORESET, the at least one processor is further configured to: in response to an active TCI state of the first CORESET being associated with the second PCI, monitor the at least one first CSS in the first CORESET, or In order to monitor the at least one first CSS in the first CORESET, the at least one processor is further configured to: monitor the at least one first CSS in the first CORESET in response to the active TCI state of the first CORESET being associated with the first PCI or the second PCI or in response to the active TCI state of the first CORESET being associated with the second PCI and the third PCI.

26. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a RAR message during the RAR window associated with the second PCI; and In response to a failure to receive a medium access control (MAC) control element (MAC-CE), processing the RAR message, the medium access control (MAC) control element (MAC-CE) including an indicator for activating a TCI state associated with the second PCI of the first CORESET or the second CORESET.

27. An apparatus for performing wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving, from a serving cell, a configuration of at least one first common search space (CSS) in a first control resource set (CORESET) associated with a second physical cell identifier (ID) (PCI), wherein the serving cell is associated with a first PCI different from the second PCI, wherein the network node is associated with the second PCI; receiving, from a user equipment (UE) a physical random access channel (PRACH) transmission associated with the second PCI during a PRACH opportunity; as well as In response to receiving the PRACH transmission, a random access response (RAR) message is sent to the UE during a RAR window associated with the second PCI, wherein the RAR window is based on a temporal position of the PRACH opportunity.

28. The apparatus according to claim 27, further comprising: a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: A physical downlink control channel (PDCCH) order is sent to the UE via the transceiver, the physical downlink control channel (PDCCH) order including an indication of the PRACH transmission.

29. A method of communicating at a user equipment (UE), the method comprising: receiving a first radio resource control (RRC) configuration from a serving cell, the first radio resource control (RRC) configuration comprising a first configuration of a first physical cell identifier (ID) (PCI) and a second PCI, wherein the serving cell is associated with the first PCI and an additional cell is associated with the second PCI different from the first PCI; transmitting, during a physical random access channel (PRACH) opportunity, a PRACH transmission associated with the second PCI; as well as At least one first common search space (CSS) in a first control resource set (CORESET) is monitored during a random access response (RAR) window associated with the second PCI, wherein the RAR window is based on a time position of the PRACH opportunity.

30. A method of communicating at a network node, the method comprising: sending, from a serving cell to a user equipment (UE), a radio resource control (RRC) configuration of at least one first common search space (CSS) in a first control resource set (CORESET) associated with a second physical cell identifier (ID) (PCI), wherein the serving cell is associated with a first PCI different from the second PCI; receiving, from the UE during a physical random access channel (PRACH) opportunity, a PRACH transmission associated with the second PCI; as well as In response to receiving the PRACH transmission, a random access response (RAR) message is sent to the UE during a RAR window associated with the second PCI, wherein the RAR window is based on a temporal position of the PRACH opportunity.

Images