Determining transmission configuration indicator (TCI) state list for multiple

Abstract

The UE (102) receives (305), from a network entity (106a), a configuration of a TCI state list for a first serving cell corresponding to a reference cell. The UE (102) further receives (309) a first parameter and a second parameter from the network entity (106a), the first parameter and the second parameter defining another TCI state list for the second serving cell. The first parameter indicates a type of another TCI state list of the second serving cell and the second parameter indicates at least one of a serving cell index of the first serving cell or one or more TCI state IDs in the TCI state list. The UE (102) communicates (377) with the network entity (106a) using another list of TCI states of the second serving cell. The other TCI state list is based on the second parameter and the TCI state list of the first serving cell.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to transmission configuration indicator (TCI) state lists for multiple transmission reception points (mTRPs). Background Art

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface called fifth generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system may include a 5G core (5GC) network, a 5G radio access network (5G-RAN), user equipment (UE), etc. Compared to other types of wireless communication systems, the 5G NR architecture may provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems may generally be configured to provide various telecommunication services (e.g., telephony, video, data, messaging, broadcast, etc.) based on multiple access technologies (such as orthogonal frequency division multiple access (OFDMA) technologies) that support communication with multiple UEs. Improvements in mobile broadband have been instrumental to the continued development of such wireless communication technologies. For example, in a single transmission reception point (TRP) use case, a unified transmission configuration indicator (TCI) framework has been implemented for downlink and uplink communications between a base station and a user equipment (UE). However, determining the TCI state list in a multiple TRP (mTRP) use case may introduce additional complexity. Summary of the invention

[0004] A simplified overview of one or more aspects is presented below to provide a basic understanding of such aspects. This overview is not an extensive review of all contemplated aspects. This overview 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 preface to a more detailed description presented later.

[0005] A network entity, such as a base station or a unit of a base station, may communicate with a user equipment (UE) on a downlink or uplink using a unified transmission configuration indicator (TCI) framework. However, implementations of the unified TCI framework may be limited to a single transmission reception point (TRP) use case and are not extended to a multiple TRP (mTRP) use case. That is, from the perspective of the UE, channel transmissions, reference signals, etc. may be transmitted to or received from a single TRP, such that the UE may determine a single TCI state associated with a single TRP.

[0006] The TCI state list of the second service cell may be explicitly indicated by a network entity, such as in a radio resource control (RRC) configuration message, or determined based on a reference to a different first service cell. The explicit indication of the TCI state list of the second service cell may correspond to a dl-orJoint-TCI-State-List parameter and / or a ul-TCI-State-List parameter indicated via an RRC configuration message. The reference-based determination of the TCI state list may involve receiving a parameter indicating a cell identifier (ID) of the first service cell. This parameter means that the second service cell of the UE can (re)use the same TCI state list as the indicated first service cell. However, when the TCI framework of the first service cell is associated with a single TRP and the second service cell is associated with an mTRP, obtaining the TCI state list of the second service cell of the UE with reference to different first service cells may result in incompatibility.

[0007] Aspects of the present disclosure address the above and other deficiencies by implementing a reference process to a TCI state list in an example associated with an mTRP. For example, a TCI state list for a single TRP serving cell may be referenced by an mTRP serving cell, and a TCI state list for an mTRP serving cell may be referenced by a single TRP serving cell. For a single TRP use case and / or an mTRP use case, the TCI state list may be determined at the UE and / or network entity.

[0008] According to some aspects, the UE receives a configuration of a TCI state list for a first service cell from a network entity, wherein the first service cell corresponds to a reference cell. The UE further receives a first parameter and a second parameter from the network entity, wherein the first parameter and the second parameter define another TCI state list for a different second service cell. The first parameter indicates a TCI state list type (e.g., joint / separated) for the second service cell. The second parameter indicates at least one of: (i) a service cell index of the first service cell or (ii) one or more TCI state IDs in the TCI state list. The UE communicates with the network entity using another TCI state list for the second service cell, wherein the another TCI state list is based on the second parameter and the TCI state list for the first service cell.

[0009] According to some aspects, the network entity transmits the configuration and parameters as described above to the UE. The network entity communicates with the UE using another TCI state list of the second serving cell as described above.

[0010] According to some aspects, the second network entity transmits to the first network entity a configuration of a TCI state list for a first serving cell, wherein the first serving cell corresponds to a reference cell. The second network entity further transmits to the first network entity a first parameter and a second parameter for another TCI state list for the second serving cell. The second network entity communicates with the UE using the another TCI state list for the second serving cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A diagram showing a wireless communication system including multiple user equipments (UEs) and network entities communicating through one or more cells.

[0012] Figure 2 A signaling diagram of a UE, a base station and a multiple transmission reception point (mTRP) is shown.

[0013] Figure 3 A signaling diagram for determining one or more transport configuration indicator (TCI) state lists associated with an mTRP is shown.

[0014] Figure 4 A signaling diagram for determining one or more TCI state lists based on multiple reference cells is shown.

[0015] Figure 5 is a flow chart of a method of wireless communication at a UE.

[0016] Figure 6 is a flow chart of a method of wireless communication at a first network entity.

[0017] Figure 7 is a flow chart of a method of wireless communication at a second network entity.

[0018] Figure 8 is a diagram illustrating an example of a hardware implementation of an example UE equipment.

[0019] Fig. 9 is a diagram illustrating an example of a hardware implementation of one or more example network entities. DETAILED DESCRIPTION

[0020] Figure 1A diagram 100 of a wireless communication system associated with a plurality of cells 190 is shown. The wireless communication system includes a user equipment (UE) 102 and a base station 104, wherein some base stations 104c include an aggregated base station architecture and other base stations 104a-104b include a decomposed base station architecture. The aggregated base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized unit (CU) 110, which are configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed between two or more units (e.g., RU 106, DU 108, CU 110). For example, CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with CU 110, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106. Each of RU 106, DU 108, and CU 110 may be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station 104 and / or units of base station 104 such as RU 106, DU 108, or CU 110 may be referred to as a transmission reception point (TRP).

[0021] The operation and / or network design of the base station 104 can be based on the aggregated nature of the base station functions. For example, a decomposed base station architecture is utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to as a cloud radio access network (C-RAN). Decomposition may include distributing functions between two or more units located at various physical locations, and virtually distributing the functions of at least one unit, which enables flexibility in network design. Various units of a decomposed base station architecture or a decomposed RAN architecture may be configured to communicate with at least one other unit in wired or wireless communication. For example, CU 110a communicates with DU 108a-108b via a corresponding midhaul link 162 based on an F1 interface. DU 108a-108b may communicate with RU 106a and RU106b-106c via corresponding fronthaul links 160, respectively. RU 106a-106c can communicate with corresponding UE 102a-102c and 102s via one or more radio frequency (RF) access links based on Uu interface. In an example, multiple RU 106 and / or base station 104 can provide services for UE 102 at the same time, such as the access link of RU 106a of cell 190a and the UE 102a of cell 190e served by base station 104c of cell 190e at the same time.

[0022] One or more CUs 110, such as CU 110a or CU 110d, may communicate directly with the core network 120 via a backhaul link 164. For example, CU 110d communicates with the core network 120 via a backhaul link 164 based on a next generation (NG) interface. One or more CUs 110 may also communicate indirectly with the core network 120 through one or more decomposed base station units, such as a near real-time RAN intelligent controller (RIC) 128 via an E2 link and a service management and orchestration (SMO) framework 116 that may be associated with a non-real-time RIC 118. The near real-time RIC 128 may communicate with the SMO framework 116 and / or the non-real-time RIC 118 via an A1 link. The SMO framework 116 and / or the non-real-time RIC 118 may also communicate with an open cloud (O-cloud) 130 via an O2 link. One or more CUs 110 may further communicate with each other via a backhaul link 164 based on an Xn interface. For example, the CU 110d of the base station 104c communicates with the CU 110a of the base station 104b via the backhaul link 164 based on the Xn interface. Similarly, the base station 104c of the cell 190e can communicate with the CU 110a of the base station 104b via the backhaul link 164 based on the Xn interface.

[0023] The RU 106, DU 108, and CU 110, as well as the near real-time RIC 128, the non-real-time RIC 118, and / or the SMO framework 116, may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. The base station 104 or any of the one or more decomposed base station units may be configured to communicate with one or more other base stations 104 or one or more other decomposed base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with executable instructions of the interface may be configured to provide communication between the base station 104 and / or one or more decomposed base station units via a wired or wireless transmission medium. For example, the wired interface may be configured to transmit or receive information / signals through a wired transmission medium, such as a fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 for the cell 190d, or more specifically, a fronthaul link 160 between the RU 106d and the DU 108d. The BBU 112 includes the DU 108d and the CU 110d, which may also have a wired interface configured between the DU 108d and the CU 110d to transmit or receive information / signals between the DU 108d and the CU 110d based on the midhaul link 162. In a further example, a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver), may be configured to transmit or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a of cell 190a and base station 104c of cell 190e via cross-cell communication beams of RU 106a and base station 104c.

[0024] One or more high-level control functions (such as functions related to radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc.) can be hosted at CU 110. Each control function can be associated with an interface for transmitting signals based on one or more other control functions hosted at CU 110. User plane functions (such as central unit-user plane (CU-UP) functions), control plane functions (such as central unit-control plane (CU-CP) functions), or a combination thereof can be implemented based on CU 110. For example, CU 110 may include one or more CU-UP processes and / or one or more CU-CP processes. When implemented in an O-RAN configuration, the CU-UP function can be based on bidirectional communication with the CU-CP function via an interface (such as an E1 interface (not shown)).

[0025] The CU 110 may communicate with the DU 108 for network control and signaling. The DU 108 is a logical unit of the base station 104 that is configured to perform one or more base station functions. For example, the DU 108 may control the operation of one or more RUs 106. One or more of the following may be hosted at the DU 108: a radio link control (RLC) layer, a media access control (MAC) layer, or one or more higher physical (PHY) layers, such as forward error correction (FEC) modules for encoding / decoding, scrambling, modulation / demodulation, etc. The DU 108 may host such functions based on the functional division of the DU 108. The DU 108 may similarly host one or more lower PHY layers, where each lower layer or module may be implemented based on an interface for communicating with other layers and modules hosted at the DU 108, or based on a control function hosted at the CU 110.

[0026] The RU 106 may be configured to implement low-level functions. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions or low-level PHY functions, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functions of the RU 106 may be based on functional partitioning, such as low-level functional partitioning.

[0027] RU 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beam set 132 of RU 106b and a second communication beam set 134b of UE 102b, which may correspond to inter-cell communication beams or cross-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beam set 134a of UE 102b and a RU beam set 136 of RU 106a. Both real-time and non-real-time features of control plane and user plane communications of RU 106 can be controlled by associated DU 108. Therefore, DU 108 and CU 110 can be used in a cloud-based RAN architecture (such as a vRAN architecture), and SMO framework 116 can be used to support non-virtualized and virtualized RAN network elements. For non-virtualized network elements, the SMO framework 116 may support deployment of dedicated physical resources for RAN coverage, where the dedicated physical resources may be managed through an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 116 may interact with a cloud computing platform (such as O-cloud 130) via an O2 link (e.g., a cloud computing platform interface) to manage the network elements. Virtualized network elements may include, but are not limited to, RU 106, DU 108, CU 110, near real-time RIC 128, and the like.

[0028] The SMO framework 116 may be configured to communicate directly with one or more RUs 106 using an O1 link. The non-real-time RIC 118 of the SMO framework 116 may also be configured to support the functionality of the SMO framework 116. For example, the non-real-time RIC 118 implements logic functions that are capable of controlling non-real-time RAN features and resources, features / applications of the near real-time RIC 128, and / or artificial intelligence / machine learning (AI / ML) processes. The non-real-time RIC 118 may communicate (or couple) with the near real-time RIC 128, such as through an A1 interface. The near real-time RIC 128 may implement logic functions that are capable of controlling near real-time RAN features and resources based on data collection and interaction through an E2 interface (such as an E2 interface between the near real-time RIC 128 and the CU 110a and the DU 108b).

[0029] The non-real-time RIC 118 may receive parameters or other information from an external server to generate an AI / ML model for deployment in the near-real-time RIC 128. For example, the non-real-time RIC 118 receives parameters or other information from the O-cloud 130 via the O2 link to deploy the AI / ML model to the real-time RIC 128 via the A1 link. The near-real-time RIC 128 may utilize the parameters and / or other information received from the non-real-time RIC 118 or the SMO framework 116 via the A1 link to perform near-real-time functions. The near-real-time RIC 128 and the non-real-time RIC 115 may be configured to adjust the performance of the RAN. For example, the non-real-time RIC 116 monitors patterns and long-term trends to improve the performance of the RAN. The non-real-time RIC 116 may also deploy the AI / ML model through the SMO framework 116 for implementing corrective actions, such as initiating reconfiguration of the O1 link or instructing the management process of the A1 link.

[0030] Any combination of RU 106, DU 108, and CU 110 or any reference thereto individually may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to core network 120. That is, base station 104 may relay communications between UE 102 and core network 120. Base station 104 may be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, cell 190e corresponds to a macro cell, and cells 190a-190d may correspond to a small cell. Small cells include femto cells, micro cells, micro cells, etc. A cell structure including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network."

[0031] Transmissions from the UE 102 to the base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions, and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106 d utilizes the antenna of the base station 104 c of the cell 190 d to transmit downlink / forward link communications to the UE 102 d, or receive uplink / reverse link communications from the UE 102 d, based on the Uu interface associated with the access link between the UE 102 d and the base station 104 c / RU 106 d.

[0032] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) spectrum bandwidth allocated per carrier in up to a total of Yx MHz carrier aggregation, where x component carriers (CCs) are used for communication in each direction of the uplink direction and the downlink direction. The carriers may be adjacent to each other along the spectrum, or may not be adjacent to each other. In an example, uplink carriers and downlink carriers may be allocated in an asymmetric manner, and more or fewer carriers may be allocated for uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

[0033] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via a side link. For example, a side link communication / D2D link utilizes a spectrum of a wireless wide area network (WWAN) associated with uplink communication and downlink communication. The side link communication / D2D link can also use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and / or a physical side link control channel (PSCCH) to transmit information between UEs 102a and 102s. Such side link / D2D communication can be performed via various wireless communication systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, long term evolution (LTE) systems, new radio (NR) systems, etc.

[0034] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc. based on different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth generation (5G) NR is typically associated with two operating bands referred to as frequency range 1 (FR1) and frequency range 2 (FR2). FR1 ranges from 410 MHz - 7.125 GHz, and FR2 ranges from 24.25 GHz - 52.6 GHz. Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is different from the "extremely high frequency" (EHF) band, but is an approximate subset of that band, the EHF band ranges from 30 GHz - 300 GHz, and is sometimes also referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are often referred to as "mid-band" frequencies. The operating frequency band of mid-band frequencies may be referred to as frequency range 3 (FR3), which ranges from 7.125 GHz to 24.25 GHz. The frequency band within FR3 may include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 may be extended to mid-band frequencies. Higher operating frequency bands have been identified as extending 5G NR communications to above 52.6 GHz associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2 (ranging from 52.6 GHz to 71 GHz), FR4 (ranging from 71 GHz to 114.25 GHz), and FR5 (ranging from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF frequency band. Therefore, unless otherwise expressly stated herein, the term "below 6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Further, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR2-2 and / or FR5, or frequencies that may be within the EHF band.

[0035] UE 102 and base station 104 / RU 106 may each include multiple antennas. Multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, RU 106b transmits a downlink beamformed signal to UE 102b based on a first beam set 132 in one or more transmit directions of RU 106b. UE 102b may receive a downlink beamformed signal from RU 106b based on a second beam set 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit an uplink beamformed signal to RU 106b based on a second beam set 134b in one or more transmit directions of UE 102b. RU 106b may receive an uplink beamformed signal from UE 102b in one or more receive directions of RU 106b. UE 102b may perform beam training to determine the optimal receive and transmit directions of the beamformed signal. The transmit and receive directions of the UE 102 and the base station 104 / RU 106 may be the same or different. In a further example, a beamformed signal may be transmitted between the first base station 104c and the second base station 104b. For example, the RU 106a of the cell 190a may transmit a beamformed signal to the base station 104c of the cell 190e based on the RU beam set 136 in one or more transmit directions of the RU 106a. The base station 104c of the cell 190e may receive a beamformed signal from the RU 106a based on the base station beam set 138 in one or more receive directions of the base station 104c. Similarly, the base station 104c of the cell 190e may transmit a beamformed signal to the RU 106a based on the base station beam set 138 in one or more transmit directions of the base station 104c. The RU 106a may receive a beamformed signal from the base station 104c of the cell 190e based on the RU beam set 136 in one or more receive directions of the RU 106a.

[0036] The base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to a base station 104 or at least one unit of the base station 104, such as a RU 106, a DU 108, and / or a CU 110. The base station 104 may also include and / or be referred to as a next generation evolved node B (ng-eNB), a generation NB (gNB), an evolved NB (eNB), an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network device, or other related terms. The base station 104 or an entity at the base station 104 may be implemented as an IAB node, a relay node, a side link node, an aggregated (integrated) base station having a RU 106 and a BBU including a DU 108 and a CU 110, or may be implemented as a decomposed base station 104b including one or more of the RU 106, the DU 108, and / or the CU 110. The set of converged or disaggregated base stations 104a-104b may be referred to as a next generation radio access network (NG-RAN).

[0037] The core network 120 may include an access and mobility management function (AMF) 121, a session management function (SMF) 122, a user plane function (UPF) 123, a unified data management (UDM) 124, a gateway mobile location center (GMLC) 125, and / or a location management function (LMF) 126. The core network 120 may also include one or more location servers, which may include the GMLC 125 and the LMF 126, as well as other functional entities. For example, the one or more location servers include one or more location / positioning servers, which may include the GMLC 125 and the LMF 126 in addition to one or more of the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc.

[0038] AMF 121 is a control node that handles signaling between UE 102 and core network 120. AMF 121 supports registration management, connection management, mobility management, and other functions. SMF 122 supports session management and other functions. UPF 123 supports packet routing, packet forwarding, and other functions. UDM 124 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. GMLC 125 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 126 receives measurement and assistance information from NG-RAN and UE 102 via AMF 121 to calculate the positioning of UE 102. NG-RAN can use one or more positioning methods to determine the location of UE 102. Positioning UE 102 can involve signal measurement, position estimation, and optional speed calculation based on measurement. Signal measurement can be performed by UE 102 and / or serving base station 104 / RU 106.

[0039] The transmitted signal may also be based on one or more of a satellite positioning system (SPS) 114, such as a signal measured for positioning. In an example, the SPS 114 of the cell 190c may communicate with one or more UEs 102, such as UE 102c, and one or more base stations 104 / RU 106, such as RU 106c. The SPS 114 may correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and / or multiple RTT), wireless local area network (WLAN) signals, terrestrial beacon systems (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink departure angle (DL-AoD), downlink arrival time difference (DL-TDOA), uplink arrival time difference (UL-TDOA), uplink arrival angle (UL-AoA), and / or other systems, signals, or sensors.

[0040] UE 102 may be configured as a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a GPS, a multimedia device, a video device, a digital audio player (e.g., a Moving Picture Experts Group (MPEG) Audio Layer 3 (MP3) player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, a utility meter, a gas pump, a home appliance, a healthcare device, a sensor / actuator, a display, or any other device with similar functionality. Some of UE 102 may be referred to as Internet of Things (IoT) devices, such as parking meters, gas pumps, home appliances, vehicles, healthcare equipment, etc. UE 102 may also be referred to as a station (STA), a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a mobile client, a client, or other similar terms. The term UE may also apply to a roadside unit (RSU), which may communicate with other RSU UEs, non-RSU UEs, the base station 104, and / or entities at the base station 104, such as the RU 106.

[0041] Still refer to Figure 1 In certain aspects, the UE 102 may include a TCI state list determination component 140 configured to receive a configuration of a transmission configuration indicator (TCI) state list of a first serving cell from a network entity, the first serving cell corresponding to a reference cell; receive a first parameter and a second parameter defining another TCI state list for a second serving cell from the network entity, the first parameter indicating a type of the another TCI state list for the second serving cell, the second parameter indicating at least one of: (i) a serving cell index for the first serving cell, or (ii) one or more TCI state identifiers (IDs) in the TCI state list; and communicate with the network entity using the another TCI state list for the second serving cell, the another TCI state list being based on the second parameter and the TCI state list for the first serving cell.

[0042] In certain aspects, the base station 104 or a network entity of the base station 104 may include a TCI state list configuration component 150, which is configured to: transmit a configuration of a TCI state list of a first service cell to a UE, the first service cell corresponding to a reference cell; transmit a first parameter and a second parameter defining another TCI state list for a second service cell to the UE, the first parameter indicating a type of the another TCI state list for the second service cell, and the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state IDs in the TCI state list; and communicate with the UE using the another TCI state list for the second service cell, the another TCI state list being based on the second parameter and the TCI state list of the first service cell. The TCI state list configuration component 150 is further configured to: transmit a configuration of a TCI state list of a first service cell to a first network entity, the first service cell corresponding to a reference cell; transmit a first parameter and a second parameter defining another TCI state list for a second service cell to the first network entity, the first parameter indicating a type of the another TCI state list for the second service cell, the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state identifiers (IDs) in the TCI state list; and communicate with the UE using the another TCI state list for the second service cell, the another TCI state list being based on the second parameter and the TCI state list of the first service cell.

[0043] therefore, Figure 1 A wireless communication system is described that can incorporate aspects of one or more of the other figures described herein (such as Figures 2 to 4 Further, although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-Advanced (LTE-A), and other wireless technologies.

[0044] Figure 2A signaling diagram 200 of a UE 102, a base station 104 operating a cell 190a, a TRP1 106a, and a TRP2 106b is shown. According to the signaling diagram 200, the base station 104 broadcasts 204, 206 one or more synchronization signal blocks (SSBs) via TRP1 106a (e.g., periodically) and broadcasts 208, 210 system information. The system information may include a master information block (MIB) and / or a system information block (SIB). For example, the SIB includes SIB1, and may further include SIB2, SIB3, SIB4, and / or SIB5. The UE 102 initially operates 202 in an idle state (e.g., an RRC_IDLE state). The UE 102 in the idle state receives 206 SSBs from the base station 104 via TRP1 106a and receives 210 system information. In some implementations, the UE 102 detects that the base station 104 transmits 204 SSBs via TRP1 106a. In some implementations, the UE 102 then uses one of the SSBs to perform downlink synchronization with the base station 104 on the cell 190a via TRP1 106a and receives 210 system information via TRP1 106a based on the SSBs.

[0045] The UE 102 may perform a random access procedure 290 to initiate an RRC connection establishment procedure 292. Thus, the UE 102 may transmit 212 a first random access preamble to the TRP1 106a on a time / frequency resource and / or a random access channel (RACH) opportunity, and the TRP1 106a may forward 214 the first random access preamble to the base station 104. In some implementations, the UE 102 selects an SSB from the SSBs for which the RSRP obtained by the UE 102 is higher than a first threshold (e.g., rsrp-ThresholdSSB) for the random access procedure. In other implementations, in the event that no SSB in the SSBs is higher than the first threshold, the UE 102 selects an SSB from the SSBs and uses the SSB to determine the first random access preamble. In such cases, the UE 102 may select the SSB randomly from the SSBs or based on a specific UE implementation. Then, the UE 102 determines the first random access preamble, time / frequency resources, and / or RACH timing based on the selected SSB and the random access configuration parameters included in the system information (e.g., SIB1). In some implementations, the random access configuration parameters indicate one or more associations between the SSB and the random access preamble, RACH timing, and / or time / frequency resources. Based on the selected SSB and the association, the UE 102 determines the first random access preamble, the RACH timing, and / or the time / frequency resources for transmitting the first random access preamble.

[0046] In response to receiving 214 the first random access preamble, the base station 104 transmits 216 a first random access response to TRP1 106a, and TRP1 106a then forwards 218 the first random access response to the UE 102. In some implementations, the base station 104 or TRP1 106a may identify an SSB associated with the first random access preamble, RACH opportunity, and / or time / frequency resource. In the case where a single SSB is associated with the first random access preamble, RACH opportunity, and / or time / frequency resource, the identified SSB may be the SSB selected by the UE 102. In the case where multiple SSBs are associated with the first random access preamble, RACH opportunity, and / or time / frequency resource, the identified SSB may be the same as or different from the SSB selected by the UE 102. In such implementations, the base station 104 transmits 216 the first random access response to the UE 102 via TRP1 106a based on the identified SSB. The base station 104 includes a first preamble ID and a first timing advance (TA) command in a first random access response. The first preamble ID identifies the first random access preamble. The first TA command includes a first TA value.

[0047] In some cases, the UE 102 applies a first TA value, and the UE 102 determines or maintains 220 an uplink that is synchronized (e.g., time-aligned) with the BS 104 (or TRP1 106a and / or TRP2 106b) after applying the first TA value (e.g., in response to applying the first TA value). In some cases, the UE 102 supports multiple TA value operations in a serving cell. In such cases, the UE 102 applies a first TA value, and determines or maintains 220 an uplink that is synchronized (e.g., time-aligned) with the TRP1 106a after applying the first TA value (e.g., in response to applying the first TA value). The UE 102 applies the first TA value for transmitting (subsequent) UL transmissions (e.g., physical uplink control channel (PUCCH) transmissions, physical uplink shared channel (PUSCH) transmissions, and / or sounding reference signal transmissions) until a new or different TA value that updates the first TA value is received from the base station 104. In some implementations, the UE 102 starts a first time alignment timer (TAT) after or upon receiving the first TA command to maintain 220 the (first) UL synchronization (state) with the TRP1 106a or the base station 104. In some implementations, the base station 104 includes the UL grant (i.e., RAR grant) in the random access response.

[0048] In some implementations, after transmitting 216 a random access response or a first TA command to the UE 102 (e.g., in response to transmitting 216 a random access response or a first TA command to the UE 102), the base station 104 initiates a first TAT in parallel to maintain a first UL synchronization for UL and / or DL ​​communications with the UE 102 via TRP1 106a. In some implementations, TRP1 106a generates timing information for or based on a first random access preamble received 212 from the UE 102, and transmits 214 the timing information to the base station 104. For example, the timing information may indicate a propagation delay or a propagation delay offset. Based on the timing information received 214 from TRP1 106a, the base station 104 determines a first TA value.

[0049] Elements 212, 214, 216, 218 and 220 are Figure 2 It is collectively referred to as the random access process 290.

[0050] After (or during) the random access procedure 290, the UE 102 transmits 222, 224 an RRC setup request message (e.g., an RRCSetupRequest message) to the base station 104 via TRP1 106a. In some implementations, the UE 102 transmits 222 the RRC setup request message using the UL grant received 218 in the random access response. In response to the RRC setup request message, the base station 104 transmits 226, 228 an RRC setup message (e.g., an RRCSetup message) to the UE 102 via TRP1 106a. In some implementations, the base station 104 may transmit (e.g., in a MAC control element (MAC-CE)) a MAC protocol data unit (PDU) including a contention resolution indicator to the UE 102 to resolve contention for the random access procedure 290. In some implementations, the base station 104 includes the RRC setup message in the MAC PDU. In other implementations, after transmitting the MAC PDU, the base station 104 transmits another MAC PDU including an RRC setup message to the UE 102. In response to receiving 228 the RRC setup message, the UE 102 transitions 230 to a connected state (e.g., RRC_CONNECTED) and transmits 232, 234 an RRC setup complete message (e.g., RRCSetupComplete message) to the base station 104 via TRP1 106a.

[0051] After performing the RRC connection establishment procedure 292 with the UE 102, the base station 104 may perform (not shown) a security activation procedure with the UE 102 to activate security protection (e.g., integrity protection / integrity checking and encryption / decryption) for UL data and DL data communicated 256, 276 between the UE 102 and the base station 104. After performing the RRC connection establishment procedure 292 or the security activation procedure, the base station 104 may perform (also not shown) a radio bearer configuration procedure with the UE 102 to configure a signaling radio bearer 2 (SRB2) and / or a data radio bearer (DRB) for the UE 102.

[0052] After performing the RRC connection establishment procedure 292, the security activation procedure, or the radio bearer configuration procedure, the base station 104 transmits 236, 238 an RRC reconfiguration message (e.g., an RRCReconfiguration message) to the UE 102 via TRP1 106a, the RRC reconfiguration message including a channel state information (CSI) resource configuration and a CSI report configuration. In response, the UE 102 transmits 240, 242 an RRC reconfiguration completion message (e.g., an RRCReconfigurationComplete message) to the base station 104 via TRP1 106a. In some implementations, the CSI resource configuration includes configuring configuration parameters of channel state information reference signals (CSI-RS) from multiple TRPs 106a, 106b for the UE 102 to use for measurement.

[0053] The base station 104 may transmit 262a, 264a, 262b, 264b reference signals (e.g., SSBs or CSI-RSs) to the UE 102 via TRP1 106a or TRP2 106b. For example, the base station 104 transmits 262b, 264b CSI-RSs via TRP2 106b according to the CSI resource configuration. The UE 102 performs measurements on the CSI-RSs according to the CSI resource configuration. In some implementations, the CSI resource configuration includes configuration parameters for configuring SSBs for the UE 102 to use for measurement. The base station 104 transmits 262b, 264b SSBs via TRP2 106b. The UE 102 performs measurements on the SSBs according to the CSI resource configuration. In other implementations, the RRC reconfiguration message or the CSI resource configuration does not include configuration parameters for configuring the SSBs. In such a case, the base station 104 may still transmit the SSB via TRP2 106b, and the UE 102 may perform measurements on the SSB.

[0054] The base station 104 may transmit 262a, 264a a reference signal (e.g., SSB or CSI-RS) to the UE 102 via TRP1 106a. Based on the CSI reporting configuration, the UE 102 generates a CSI report from the measurement of the CSI-RS or SSB, and transmits 244, 246 the CSI report to the base station 104 via TRP1 106a. In some implementations, the UE 102 transmits 244, 246 the CSI report to the base station 104 on the PUCCH via TRP1 106a. In some implementations, the CSI reporting configuration configures periodic or semi-persistent reporting, or configures semi-persistent or aperiodic reporting triggered by downlink control information (DCI). The CSI report includes a periodic CSI report, a semi-persistent CSI report, and / or an aperiodic CSI report.

[0055] In some implementations, the base station 104 includes the CSI resource configuration and / or the CSI report configuration in a CSI measurement configuration, e.g., a CSI-MeasConfig information element (IE). The base station 104 then includes the CSI measurement configuration in an RRC reconfiguration message transmitted 236, 238 to the UE 102 via TRP 1106a. In other implementations, the CSI resource configuration includes an NZP-CSI-RS-Resource IE, an NZP-CSI-RS-ResourceSet IE, a CSI-SSB-ResourceSet IE, a CSI-ResourceConfig IE, and / or a CSI-ReportConfig IE.

[0056] Elements 236, 238, 240, 242, 244, 246, 262a and 264a are Figure 2 This is collectively referred to as the CSI resource configuration and / or CSI reporting process 294 .

[0057] After receiving 244, 246 the CSI report via TRP1 106a, the base station 104 determines 256, 276 to communicate with the UE 102 via TRP2 106b based on the CSI report while maintaining the (radio) link with the UE 102 via TRP1 106a. In some implementations, the base station 104 makes the determination based on one or more capabilities of the UE 102. In response to the determination, the base station 104 transmits 248, 250 an RRC reconfiguration message to the UE 102 via TRP1 106a, the RRC reconfiguration message including DL and / or UL configuration parameters for DL ​​and / or UL communication, respectively, with the base station 104 via TRP2 106b. In some implementations, the base station 104 includes the DL and UL configuration parameters in a CellGroupConfig IE and includes the CellGroupConfig IE in the RRC reconfiguration message. In some implementations, the base station 104 includes the DL configuration parameters in a BWP-DownlinkDedicated IE and includes the BWP-DownlinkDedicated IE in the RRC reconfiguration message. In some implementations, the base station 104 includes the UL configuration parameters in a BWP-UplinkDedicated IE and includes the BWP-UplinkDedicated IE in the RRC reconfiguration message.

[0058] In response to the RRC reconfiguration message, the UE 102 transmits 252, 254 an RRC reconfiguration complete message to the base station 104 via TRP1 106a. In some implementations, the UE 102 may apply the DL and / or UL configuration parameters to the RRC reconfiguration complete message transmitted 252, 254 to the base station 104 via TRP1 106a upon receiving 250, 252 the RRC reconfiguration message. In such implementations, the UE 102 performs 256 DL and / or UL communications with the base station 104 via TRP2 106b based on the DL and / or UL configuration parameters. The UE 102 may apply the first TA value and / or the first TAT for UL communications with the base station 104 via TRP2 106b.

[0059] In some implementations, the UE 102 may apply a different TA value and / or TAT for UL communications with the base station 104 via TRP2 106b. In such cases, the UE 102 refrains from performing UL communications according to the UL configuration parameters until a TA value acquisition procedure 298 (e.g., a random access procedure or a MAC-CE indication) is performed with the base station 104 via TRP2 106b. In other implementations, the UE 102 refrains from performing DL communications with the base station 104 via TRP2 106b until a TA value acquisition procedure 298 is performed with the base station 104 via TRP2 106b. In some implementations, the base station 104 refrains from performing UL communications and / or configuring UL configuration parameters until after the TA value acquisition procedure 298 with the base station 104 via TRP2 106b is completed. In some implementations, the base station 104 refrains from performing DL communications and / or configuring DL configuration parameters until the TA value acquisition procedure 298 with the base station 104 via TRP2 106b is completed.

[0060] In some implementations, the base station 104 may perform (additional) UL synchronization based on the indication in the RRC reconfiguration message, i.e., for communication with the base station 104 via TRP2 106b. That is, the base station 104 configures the UE 102 to obtain a (second) UL synchronization for communication between the UE 102 and TRP1 106a, while maintaining a first UL synchronization for communication between the UE 102 and TRP2 106b. In other words, the base station 104 configures or instructs the UE 102 to maintain two TA values ​​for communication between the UE 102 and the base station 104 (i.e., between the UE 102 and TRP1 106a and between the UE 102 and TRP2 106b, respectively). In some implementations, the base station 104 may include a configuration (e.g., a field or IE) indicating that (additional) UL synchronization is to be performed for communication between the UE 102 and TRP2 106b in the RRC reconfiguration message. In other words, the configuration enables operation of two TA values ​​for communications between the UE 102 and the base station 104 (ie, between the UE 102 and TRP1 106a and between the UE 102 and TRP2 106b, respectively).

[0061] In some implementations, the UE 102 initiates a second random access procedure 298 in response to the field or IE before transmitting an UL transmission (e.g., a CSI report, a sounding reference signal (SRS), a PUCCH transmission, and / or a PUSCH transmission) to the base station 104 via TRP2 106b. If the RRC reconfiguration message does not include the field or IE, the UE 102 does not initiate the second random access procedure 298 and may transmit an UL transmission (e.g., a CSI report, a sounding reference signal (SRS), a PUCCH transmission, and / or a PUSCH transmission) to the base station 104 via TRP2 106b. In other implementations, the UE 102 refrains from transmitting an UL transmission (e.g., a CSI report, a sounding reference signal (SRS), a PUCCH transmission, and / or a PUSCH transmission) to the base station 104 via TRP2 106b in response to the field or IE. In such cases, the UE 102 does not transmit a random access preamble to the base station 104 via TRP2 106b until a physical downlink control channel (PDCCH) command is received 258, 260 from the base station 104.

[0062] Elements 248, 250, 252 and 254 are Figure 2 It is collectively referred to as the TRP configuration process 296.

[0063] After receiving 236, 238 an RRC reconfiguration message via TRP1 106a, or after performing a CSI resource configuration and CSI reporting procedure 294 or a TRP configuration procedure 296 with the base station 104, the UE 102 may receive 262b, 264b a reference signal (RS) from the base station 104 via TRP2 106b. The RS may be configured in the CSI resource configuration received 236, 238 from the base station 104, such that the UE 102 may receive 262b, 264b the RS after receiving 238 an RRC reconfiguration message from the base station 104, or during or after the CSI resource configuration and CSI reporting procedure 294 or the TRP configuration procedure 296. After performing a TRP configuration procedure 296 with the base station 104, the UE 102 may initiate a random access procedure 298 via TRP2 106b. In response to initiating a second random access procedure 298, the UE 102 transmits 266, 268 a second random access preamble to the base station 104 via TRP2 106b on a time / frequency resource and a random access channel (RACH) opportunity. In response to the second random access preamble, the base station 104 transmits 270, 272 a second random access response to the UE 102 via TRP2 106b. The base station 104 includes a second preamble ID and a second TA command in the second random access response. The second preamble ID indicates the second random access preamble, and the second TA command includes a second TA value. The UE 102 applies the second TA value and determines or maintains 274 an uplink synchronized with the TRP2 106b after applying the second TA value (e.g., in response to applying the second TA value). UE 102 applies the second TA value to transmit (subsequent) UL transmissions (eg, PUCCH transmissions, PUSCH transmissions, and / or SRS transmissions) via TRP2 106b until UE 102 receives a new or different TA value from base station 104 that updates the second TA value.

[0064] In some implementations, the UE 102 starts a second TAT after or upon receiving the second TA command to maintain 274 or manage (second) UL synchronization (state) with the TRP2 106 b or the base station 104. In some implementations, the base station 104 includes a UL grant (i.e., a random access response (RAR) grant) in the second random access response, and the UE 102 may transmit a UL MAC PDU to the base station 104 via the TRP2 106 b according to the UL grant. In the case where the second random access procedure 298 is a contention-based random access procedure, the UE 102 includes a cell radio network temporary identifier (C-RNTI) of the UE 102 in the UL MAC PDU. The base station 104 identifies the UE 102 based on the C-RNTI. In response to the identification, the base station 104 generates a DCI and a cyclic redundancy check (CRC) for the DCI, scrambles the CRC using the C-RNTI, and transmits the DCI and the scrambled CRC to the UE 102 on the PDCCH. In some implementations, the DCI includes a UL grant. Upon receiving the DCI and the scrambled CRC on the PDCCH, the UE 102 determines that the contention-based random access procedure is successfully performed. In the case where the second random access procedure 298 is a contention-free random access procedure, the UE 102 determines that the contention-based random access procedure is successfully performed in response to receiving 270, 272 the second random access response message.

[0065] In some implementations, after transmitting the second TA command to the UE 102 (e.g., in response to transmitting the second TA command to the UE 102), the base station 104 starts a second TAT to maintain 274 a second UL synchronization for UL and / or DL ​​communications 276 with the UE 102 via the TRP2 106b. In some implementations, the TRP1 106a generates timing information for a second random access preamble received from the UE 102 and transmits the timing information to the base station 104. For example, the timing information may indicate a propagation delay or a propagation delay offset. Based on the timing information received from the TRP2 106b, the base station 104 determines a second TA value.

[0066] Elements 258, 260, 262b, 264b, 266, 268, 270, 272, and 274 are Figure 2 It is collectively referred to as the TA value acquisition process or the second random access process 298.

[0067] In some implementations, the UE 102 may suspend communication (e.g., reception of DL channels / RSs or transmission of UL channels / RSs) with the base station 104 via TRP1 106a while performing the second random access procedure 298. Since the UE 102 cannot simultaneously perform the second random access procedure 298 based on a UL beam or RS (i.e., toward a TRP) and transmit (i.e., UL and DL transmissions unrelated to the random access procedure) based on another UL beam or RS (i.e., toward another TRP), the UE 102 may suspend communication. In other implementations, the UE 102 continues to communicate with the base station 104 via TRP2 106b while performing the second random access procedure 298. After successfully completing the second random access procedure 298, the UE 102 performs 276 DL and UL communication with the BS 104 via TRP1 106a and TRP2 106b according to the first TA value and the second TA value, respectively.

[0068] In some implementations, after receiving 252, 254 the RRC reconfiguration complete message from the UE 102, the base station 104 may transmit 258, 260 a PDCCH command to the UE 102 via TRP2 106b to cause the UE 102 to initiate a second random access procedure 298 with the base station 104 via TRP2 106b. In some implementations, the PDCCH command includes a reference signal index and a random access preamble index. Alternatively, the base station 104 may transmit the PDCCH command to the UE 102 via TRP1 106a. In response to the PDCCH command, the UE 102 transmits 266, 268 a random access preamble to the base station 104 via TRP2 106b. In some implementations, the random access preamble index includes a second preamble ID (value) identifying the second random access preamble. Therefore, the UE 102 determines the second random access preamble based on the random access preamble index. In other implementations, the random access preamble index includes a value indicating or instructing the UE 102 to determine the random access preamble by itself. Therefore, the UE 102 determines the second random access preamble by (randomly) selecting the second random access preamble from the random access preambles configured in the system information.

[0069] In some implementations, the PDCCH command is a DCI. The base station 104 generates a DCI and a CRC for the DCI, scrambles the CRC using the C-RNTI, and transmits the DCI and the scrambled CRC to TRP2 106b, for example, via an optical fiber connection. Then, TRP2 106b transmits the DCI and the scrambled CRC to UE 102 on the PDCCH. In some implementations, the base station 104 transmits a first packet including the DCI and the scrambled CRC to TRP2 106b. In some implementations, the base station 104 may transmit control information configuring or indicating time and / or frequency resources for the PDCCH to TRP2 106b. In some implementations, the time and / or frequency resources may include subcarriers, resource elements, or physical resource blocks (PRBs). TRP2 106b transmits the DCI and the scrambled CRC on the time and / or frequency resources according to the control information. In an implementation, the base station 104 includes the control information in the first packet. In other implementations, the base station 104 transmits a second packet including control information to TRP2 106b instead of the first packet. In other implementations, the base station 104 does not transmit control information for the DCI and the scrambled CRC to TRP2 106b. In such implementations, TRP2 106b determines the time and / or frequency resources for the PDCCH and transmits the DCI and the scrambled CRC on the time and / or frequency resources.

[0070] In some implementations, the RS index (e.g., SSB index) identifies one of the SSBs. In some implementations, the base station 104 determines or decodes the SSB index indicated in the CSI report. In other implementations, the base station 104 determines or decodes the SSB index based on the radio resource (e.g., PUCCH resource) at which the base station 104 receives 244, 246 one of the CSI reports for the SSBs. In such implementations, the base station 104 may configure different radio resources for the UE 102 to transmit the CSI report for each of the SSBs. For example, the base station 104 may include a configuration of configuring different radio resources (e.g., PUCCH resources) for the UE 102 to transmit 244, 246 CSI reports for each of the SSBs in an RRC reconfiguration message transmitted to 236, 238 the UE 102. In some implementations, the UE 102 may determine the time / frequency resources and / or RACH timing based on the SSB (indicated in the RS index) and the random access configuration parameters received in the system information, and transmit 266, 268 the second random access preamble on the time / frequency resources and / or RACH timing. In other implementations, the UE 102 may determine the time / frequency resources and / or RACH timing based on the SSB (indicated in the RS index) and the random access configuration parameters received 248, 250 in the RRC reconfiguration message, and transmit 266, 268 the second random access preamble on the time / frequency resources and / or RACH timing.

[0071] In other implementations, the RS index (e.g., CSI-RS index) identifies one of the CSI-RSs. In some implementations, the base station 104 determines or decodes the CSI-RS index indicated in the CSI report. In other implementations, the base station 104 determines or decodes the CSI-RS index based on the radio resources (e.g., PUCCH resources) where the base station 104 receives 244, 246 the CSI report for the CSI-RS. In such implementations, the base station 104 can configure different radio resources for the UE 102 to transmit 244, 246 CSI reports for each of the CSI-RSs. For example, the base station 104 can include a configuration of configuring different radio resources (e.g., PUCCH resources) for the UE 102 to transmit 244, 246 CSI reports for each of the CSI-RSs in an RRC reconfiguration message transmitted 236, 238 to the UE 102. In some implementations, the UE 102 may determine the time / frequency resources and / or RACH opportunities based on the CSI-RS (indicated in the RS index) and the random access configuration parameters in the RRC reconfiguration message that the UE 102 receives 248, 250 from the base station 104. The UE 102 transmits 266, 268 the second random access preamble on the time / frequency resources and / or RACH opportunities. In some implementations, the random access configuration parameters indicate one or more associations between the CSI-RS and the RACH opportunities and / or the time / frequency resources.

[0072] In some implementations, the UE 102 determines a transmission characteristic (e.g., a spatial transmission filter / parameter) based on or with reference to the RS index in the PDCCH order, and transmits 266 a second random access preamble to TRP2 106b using the determined transmission characteristic. For example, the UE 102 may derive the transmission characteristic using the reception characteristic of the RS identified by the RS index received 264b. In some implementations, the transmission characteristic includes a phase, power, and / or transmission precoder. In some implementations, the UE 102 may further determine the transmission characteristic using DL and / or UL configuration parameters received 248, 250 from the base station 104. In other implementations, the UE 102 may determine the transmission characteristic using configuration parameters in system information received 208, 210 from the base station 104. In some implementations, the UE 102 determines transmission characteristics (e.g., spatial transmission filters / parameters) not based on or with reference to the RS index in the PDCCH command, and transmits 266, 268 a second random access preamble to TRP2 106b using the determined transmission characteristics.

[0073] In some implementations, the UE 102 initiates a second random access procedure 298 in response to receiving 248, 250 random access configuration parameters from the base station 104 and after receiving 262b, 264b RS from the base station 104. In such implementations, the base station 104 does not transmit a PDCCH command to cause the UE 102 to perform the second random access procedure 298.

[0074] In some implementations, the RRC reconfiguration message received 248, 250 from the base station 104 includes configuration parameters (e.g., PDCCH configuration, search space configuration, and / or CORESET configuration) for the UE 102 to receive DL transmissions from TRP2 106b. In some implementations, the UE 102 receives 270, 272 a second random access response according to the configuration parameters. In other implementations, the system information received 208, 210 from the base station 104 includes configuration parameters (e.g., PDCCH configuration, search space configuration, and / or CORESET configuration) for the UE 102 to receive 272 a second random access response from TRP2 106b. In such implementations, the UE 102 receives 272 a second random access response according to the configuration parameters. In some implementations, the UE 102 may receive 272 a second random access response from TRP2 106b using reception characteristics of receiving 264b RS.

[0075] Although TRP2 106b is used in the signaling diagram 200, the above description can be applied to TRP3 106c, TRP4 106d, etc. instead of TRP2 106b. In such a case, after successfully completing the random access procedure with the base station 104 via TRP3 106c, TRP4 106d and another cell 102b-102e, similar to the second random access procedure 298, the UE 102 performs 256, 276 DL and UL communications with the BS 104 via TRP according to the first TA value and the second TA value, respectively. Therefore, Figure 2 Processes 290-298 are described for allowing UE 102 to communicate 276 with base station 104 via multiple TRPs (mTRPs). Figure 3 The process used to determine the TCI status list for 375 mTRP is described.

[0076] Figure 3 A signaling diagram 300 is shown for determining one or more TCI state lists associated with an mTRP. Figure 2 Describes Figure 3 Elements 202, 204, 206, 208, 210, 276, 290, 292, 294, 296 and 298.

[0077] After UE 102 performs 276 DL and / or UL communication with base station 104, UE 102 may receive a service cell configuration for configuring a first service cell, a second service cell, a third service cell, etc. from base station 104. In some implementations, the first service cell may be a reference cell, and an entity associated with the second service cell may be able to use the reference cell as a reference for determining a TCI state list for the second service cell. In signaling diagram 300, base station 104 may transmit 303, 305 an RRC (re) configuration message to UE 102 via TRP1 106a. The RRC (re) configuration message may include the TCI state list configuration for the first service cell. In other implementations, base station 104 may transmit (not shown) an RRC (re) configuration message to UE 102 via TRP2 106b.

[0078] The base station 104 may transmit 303, 305 RRC messages (e.g., RRCReconfiguration messages) to the UE 102 to configure the TCI state pool of the first serving cell. "TCI state pool" refers to a TCI state group / list from which the base station 104 may select a TCI state to indicate a beam. In an implementation, the base station 104 may use MAC-CE or DCI to indicate the TCI state in the TCI state pool. The UE 102 applies the indicated TCI state in the TCI state pool to perform 276, 377 DL and UL communications with the base station 104 via TRP1 106a and TRP2 106b. The UE 102 may determine the TCI state pool of the second serving cell based on a reference to the first serving cell, which may be referred to as a reference cell / component carrier (CC). Therefore, the base station 104 may not explicitly configure the TCI state pool of the second serving cell via the ServingCellConfig of the second serving cell.

[0079] The TCI state pool may correspond to a joint TCI state pool or a separate TCI state pool. For a joint TCI state pool, the UE 102 applies the same TCI state to both DL and UL channels / reference signals. For a separate TCI state pool, the UE 102 applies the DL TCI state to the DL channel / reference signal and applies the separate UL TCI state to the UL channel / reference signal. In some examples, the base station 104 may apply a unified TCI framework to indicate the TCI state associated with a single TRP. For example, from the perspective of the UE 102, channel transmissions, reference signals, etc. may be transmitted to or received from a single TRP so that the UE 102 can determine a single TCI state associated with a single TRP. Although a unified TCI framework may be an efficient technique for indicating beams in a single TRP use case, other examples associated with mTRP may include additional complexity in indicating a TCI state list for a serving cell of the mTRP.

[0080] In the first example of mTRP based on the same serving cell / CC, the joint / separate TCI state list may indicate the TCI states of both TRP1 106a and TRP2 106b in the same TCI state list, rather than indicating the joint / separate TCI state corresponding to only one of TRPs 106a, 106b. That is, the joint TCI state list of the mTRP may include the first joint TCI state of TRP1 106a and the second joint TCI state of TRP2 106b in a single joint TCI state list. Similarly, the separate TCI state list of the mTRP may include a single DL TCI state list applicable to both TRP1 106a and TRP2 106b and a single UL TCI state list applicable to both TRP1 106a and TRP2 106b.

[0081] In a second example of mTRP based on the same serving cell / CC, the joint / separate TCI state list may be configured as two joint / separate TCI state lists corresponding to TRP1 106a and TRP2 106b, respectively. That is, the joint TCI state list of the mTRP may include a first joint TCI state list of TRP1 106a and a second joint TCI state list of TRP2 106b. Similarly, the separate TCI state list of the mTRP may include a first DL TCI state list applicable to TRP1 106a and a second DL TCI state list applicable to TRP2 106b, as well as a first UL TCI state list applicable to TRP1 106a and a second UL TCI state list applicable to TRP2 106b.

[0082] The base station 104 may transmit 307, 309 an RRC (re) configuration message to the UE 102 via TRP1 106a or TRP2 106b. The RRC (re) configuration message may include a first RRC parameter indicating a type of the TCI state list of the second serving cell, wherein the type may correspond to a joint TCI state list or a separate TCI state list. The base station 104 may further transmit 315, 317 a second RRC parameter to the UE 102 in the same or different RRC (re) configuration message via TRP1 106a or TRP2 106b. The RRC (re) configuration message may include or configure the TCI state list configuration of the second serving cell. That is, the second RRC parameter in the RRC (re) configuration message may indicate to the UE 102 how to determine the TCI state list of the second serving cell. For example, the second RRC parameter received 315, 317 by the UE 102 from the base station 104 may indicate at least a serving cell index of the first serving cell, and optionally a bitmap indicating a TCI state ID of a TCI state in the first TCI state list. In some cases, instead of indicating a bitmap, the second RRC parameter may use other parameters or information for the UE 102 to determine the TCI state list of the second serving cell. In a further implementation, the second RRC parameter received 315, 317 by the UE 102 from the base station 104 may indicate an additional serving cell index of a third serving cell. In a further implementation, the second RRC parameter received 315, 317 by the UE 102 from the base station 104 may indicate a TCI state list ID of one of the second TCI state list or the third TCI state list. In response to receiving the RRC (re)configuration message from base station 104, UE 102 may transmit (not shown) an RRC (re)configuration complete message to base station 104 via TRP1 106a or TRP2 106b.

[0083] Some implementations may restrict CCs associated with a single TRP to share the same TCI state as CCs associated with an mTRP. That is, if CC1 corresponds to a reference cell associated with an mTRP, then CC2 using CC1 as a reference should also be associated with an mTRP. Similarly, if CC1 corresponds to a reference cell but is associated with a single TRP, then CC2 using CC1 as a reference should also be associated with a single TRP.

[0084] Other implementations may allow CCs associated with a single TRP to share the same TCI state as CCs associated with an mTRP. For example, CC1 corresponding to a reference cell associated with an mTRP may be used as a reference for CC2 corresponding to a single TRP, or CC1 corresponding to a reference cell associated with a single TRP may be used as a reference for CC2 corresponding to an mTRP. In further implementations, additional CCs such as CC3 corresponding to a second reference cell associated with a single TRP may be used as a reference for CC2 associated with an mTRP.

[0085] For a TCI state list that includes the first / second joint TCI state of an mTRP in a single list or includes the separated DL / UL TCI state of an mTRP in a combined DL / UL TCI state list of an mTRP, the second parameter (e.g., unifiedTCI-StateRef) received 315, 317 by the UE 102 from the base station 104 may indicate one or two cell IDs. At least when indicating one cell ID, the second parameter (e.g., unifiedTCI-StateRef) may further indicate a portion of a TCI list in a reference CC that is sorted by TCI indexes for the mTRP. The second parameter (e.g., unifiedTCI-StateRef) may further include a bitmap to indicate the TCI state ID. When two cell IDs are indicated, the second parameter may indicate whether the reference TCI list is for one TRP or two TRPs, and a TCI ID reordering process for the TCI state. In the example, the reference CC is associated with the mTRP.

[0086] For two joint TCI state lists or two sets of separate DL / UL TCI state lists corresponding to the corresponding TRPs of the mTRP, the second parameter (e.g., unifiedTCI-StateRef) received 315, 317 by the UE 102 from the base station 104 may indicate one or two cell IDs. At least when indicating one cell ID, the second parameter (e.g., unifiedTCI-StateRef) may further indicate a TCI list ID. When indicating two cell IDs, the second parameter (e.g., unifiedTCI-StateRef) may indicate to the UE 102 that the TCI lists of the two reference cells are associated with the same TRP and / or the reference cell is configured with two TCI lists. In the example, the reference CC is associated with the mTRP.

[0087] After receiving 303-317 the RRC (re)configuration message from the base station 102 via TRP1 106a or TRP2 106b, the UE 102 determines 375 the TCI state list of the second serving cell based on the second parameter and the TCI state list of the first serving cell. In an example, the TCI state list of the second serving cell may be a subset of the first TCI state list of the first serving cell.

[0088] The base station 104 may then transmit 351, 353 beam indication signaling to the UE 102 via TRP1 106a or TRP2 106b. The beam indication signal may be transmitted 351, 353 by the base station 104 via MAC-CE and / or DCI. The beam indication signal may indicate one or more TCI states in the TCI state list of the second serving cell. In response to receiving 351, 353 beam indication signaling, the UE 102 may transmit 345, 347 an acknowledgement (ACK) signal to the base station 104 via TRP1 106a or TRP2 106b. In response to transmitting 345, 347 ACK to the base station 104, the UE 102 may update 377 the serving beam to perform DL and UL communications with the base station 104 via TRP1 106a and TRP2 106b. For example, UE 102 may receive a DL transmission from base station 104 or transmit an UL transmission to base station 104 via one or more TCI states in a time slot after the application time period. Figure 3 As described above, the TCI state list determination process may be based on a single reference cell. Figure 4 As described above, the TCI state list determination process may be based on multiple reference cells.

[0089] Figure 4 A signaling diagram 400 is shown for determining one or more TCI state lists based on multiple reference cells. Figure 2 Describes Figure 4 Elements 202, 204, 206, 208, 210, 276, 290, 292, 294, 296 and 298. Figure 3 Describes Figure 4 Elements 307, 309, 315, 317, 351, 353, 345, 347 and 377.

[0090] The base station 104 may transmit 403, 405 an RRC (re)configuration message to the UE 102 via TRP1 106a or TRP2 106b. The RRC (re)configuration message may include a TCI state list configuration of the first serving cell (similar to Figure 3303, 305) and a TCI state list configuration of a third serving cell, wherein both the first serving cell and the third serving cell correspond to the reference cell. The TCI state list configuration may be associated with the same or different CCs. The RRC (re) configuration message may be a single RRC (re) configuration message or may be combined with one or more other RRC (re) configuration messages. In response to receiving 403-405, 307-317 RRC (re) configuration messages from the base station 104, the UE 102 may transmit an RRC (re) configuration complete message to the base station 104 via TRP1 106a or TRP2 106b.

[0091] The UE 102 determines 475 the TCI state list of the second service cell based on the second parameter, the TCI state list of the first service cell, and the TCI state list of the third service cell. In an example, the TCI state list of the second service cell may be a combination of the first TCI state list of the first service cell and the third TCI state list of the third service cell. If the TCI state list ID indicates the second / third TCI state list, the UE 102 may determine 475 the TCI state list of the second / third service cell based on the second / third TCI state list. In a further implementation, the UE 102 may determine 475 the TCI state list of the second service cell based on the second RRC parameter and the third TCI state list. Figures 2 to 4 The signaling process associated with mTRP is shown. Figures 5 to 7 Shown is a method for implementing Figures 2 to 4 Specifically, Figure 5 UE 102 is shown Figures 2 to 4 Implementation of one or more aspects. Figure 6 The TRP 106a-106b pair is shown Figures 2 to 4 Implementation of one or more aspects. Figure 7 The base station 104 is shown Figures 2 to 4 Implementation of one or more aspects.

[0092] Figure 5 A flowchart 500 of a method of wireless communication at a UE is shown. Figures 1 to 4 and Figure 8 The method may be performed by UE 102, UE equipment 802, etc., which may include a memory 824' and may correspond to the entire UE 102 or UE equipment 802, or components of the UE 102 or UE equipment 802 such as a wireless baseband processor 824 and / or an application processor 806.

[0093] UE 102 performs 576 at least one of downlink or uplink communication with a network entity. Figures 2 to 4 , UE 102 performs 276 DL or UL communication with base station 104 via TRP1 106a and TRP2 106b. Figure 2 , UE 102 also performs 256 DL and / or UL communications with base station 104 via TRP1 106a and TRP2 106b.

[0094] UE 102 receives 505 from a network entity a configuration of a TCI state list for a first serving cell, the first serving cell corresponding to a reference cell. Figure 3 , the UE 102 receives 305 an RRC configuration from TRP1 106a, the RRC configuration indicating a TCI state list configuration for a first serving cell (eg, a reference cell). Figure 4 , the UE 102 receives 405 an RRC configuration from TRP1 106a, the RRC configuration indicating a TCI state list configuration of a first serving cell (eg, a first reference cell) and a third serving cell (eg, a second reference cell).

[0095] The UE 102 receives 517 from the network entity a first parameter and a second parameter defining another TCI state list for the second serving cell, the first parameter indicating a type of the another TCI state list for the second serving cell, and the second parameter indicating at least one of: (i) a serving cell index of the first serving cell or (ii) one or more TCI state IDs in the TCI state list. Figure 3 to Figure 4 , UE 102 receives 309 RRC configuration including a first RRC parameter indicating the type (e.g., joint / separate) of the TCI state list of the second serving cell. UE 102 also receives 317 RRC configuration including a second RRC parameter indicating how to determine the TCI state list of the second serving cell.

[0096] The UE 102 determines 575 at least one other TCI state list for the second serving cell based on at least one of the at least one TCI state list or the second parameter. Figure 3 , the UE 102 determines 375 a TCI state list for the second serving cell based on the second parameter and the TCI state list for the first serving cell. Figure 4 , the UE 102 determines 475 the TCI state list of the second serving cell based on the second parameter, the TCI state list of the first serving cell, and the TCI state list of the third serving cell.

[0097] UE 102 receives 553 at least one of a MAC-CE or a DCI from a network entity, the MAC-CE or the DCI indicating one or more TCI states in another TCI state list. Figure 3 to Figure 4 , the UE 102 receives 353 beam indication signaling from TRP1 106a via MAC-CE and / or DCI signaling. The beam indication signaling may indicate one or more TCI states in the TCI state list of the second serving cell.

[0098] UE 102 communicates 577 with the network entity using another TCI state list for the second serving cell, the other TCI state list being based on the second parameter and the TCI state list for the first serving cell. Figure 3 to Figure 4 , the UE 102 updates the serving beam to perform 377 communication with the base station 104 via TRP1 106a and TRP2 106b. The communication is based on the determined 375, 475 TCI state list of the second serving cell. Figure 5 A method from the UE side of a wireless communication link is described, while Figure 6 to Figure 7 A method from the network side of a wireless communication link is described.

[0099] Figure 6 600 is a flow chart of a method of wireless communication at a network entity. Figures 1 to 4 and Fig. 9 , the method may be performed by a network entity such as a TRP 106a-106b, which may correspond to the RU 106, the DU 108, the CU 110, the RU processor 942, the DU processor 932, the CU processor 912, etc. The network entity / TRP 106a-106b may include a memory 912' / 932' / 942', which may correspond to the entirety of the network entity / TRP 106a-106b, or a component of the network entity / TRP 106a-106b such as the RU processor 942, the DU processor 932, or the CU processor 912.

[0100] The network entity / TRP1 106a performs 676 at least one of downlink or uplink communication with the UE. Figures 2 to 4 , TRP1 106a performs 276 DL or UL communication with UE 102. Referring again to Figure 2 , TRP1 106a also performs 256 DL and / or UL communication with UE 102.

[0101] The network entity / TRP1 106a transmits 605 to the UE a configuration of a TCI state list for a first serving cell, the first serving cell corresponding to the reference cell. Figure 3, TRP1 106a transmits 305 an RRC configuration to the UE 102, the RRC configuration indicating a TCI state list configuration of the first serving cell (eg, reference cell). Figure 4 , TRP1 106a transmits 405 an RRC configuration to the UE 102, the RRC configuration indicating a TCI state list configuration of the first serving cell (eg, the first reference cell) and the third serving cell (eg, the second reference cell).

[0102] The network entity / TRP1 106a transmits 617 to the UE a first parameter and a second parameter defining another TCI state list for the second serving cell, the first parameter indicating a type of the another TCI state list for the second serving cell, and the second parameter indicating at least one of: (i) a serving cell index of the first serving cell or (ii) one or more TCI state IDs in the TCI state list. For example, referring to Figure 3 to Figure 4 , TRP1 106a transmits 309 to UE 102 an RRC configuration including a first RRC parameter indicating a type (e.g., combined / separated) of the TCI state list of the second serving cell. TRP1 106a also transmits 317 to UE 102 an RRC configuration including a second RRC parameter indicating how to determine the TCI state list of the second serving cell.

[0103] The network entity / TRP1 106a determines or configures 675 at least one further TCI state list for the second serving cell based on at least one of the at least one TCI state list or the second parameter. Figure 3 , TRP1 106a configures or determines 375 the TCI state list of the second serving cell based on the second parameter and the TCI state list of the first serving cell. Figure 4 , TRP1 106a configures or determines 475 the TCI state list of the second serving cell based on the second parameter, the TCI state list of the first serving cell and the TCI state list of the third serving cell.

[0104] The network entity / TRP1 106a transmits 653 to the UE at least one of a MAC-CE or a DCI indicating one or more TCI states in another TCI state list. Figure 3 to Figure 4 , TRP1 106a transmits 353 beam indication signaling to UE 102 via MAC-CE and / or DCI signaling. The beam indication signaling may indicate one or more TCI states in the TCI state list of the second serving cell.

[0105] The network entity / TRP1 106a communicates 677 with the UE another TCI state list for the second serving cell, the another TCI state list being based on the second parameter and the TCI state list for the first serving cell. Figure 3 to Figure 4 , TRP1106a communicates 377 with UE 102 based on the updated serving beam of UE 102. The communication 377 is based on the determined 375, 475 TCI state list of the second serving cell. Figure 6 The method is described from the perspective of TRP 106a-106b, while Figure 7 The method is described from the perspective of base station 104.

[0106] Figure 7 700 is a flow chart of a method of wireless communication at a second network entity. Figures 1 to 4 and Fig. 9 The method may be performed by a base station 104, which may correspond to a RU 106, a DU 108, a CU 110, a RU processor 942, a DU processor 932, a CU processor 912, etc. The base station 104 may include a memory 912' / 932' / 942', which may correspond to the entirety of the base station 104 or a component of the base station 104 such as a RU processor 942, a DU processor 932, or a CU processor 912.

[0107] The second network entity 104 transmits 703 to the first network entity a configuration of a TCI state list of a first serving cell, the first serving cell corresponding to the reference cell. Figure 3 , the base station 104 transmits 303 an RRC configuration to the UE 102 via TRP1 106a and TRP2 106b, the RRC configuration indicating a TCI state list configuration of a first serving cell (eg, a reference cell). Figure 4 , the base station 104 transmits 403 an RRC configuration to the UE 102 via TRP1 106a and TRP2 106b, the RRC configuration indicating a TCI state list configuration of a first serving cell (eg, a first reference cell) and a third serving cell (eg, a second reference cell).

[0108] The second network entity 104 transmits 715 to the first network entity a first parameter and a second parameter defining another TCI state list for the second serving cell, the first parameter indicating a type of the another TCI state list for the second serving cell, and the second parameter indicating at least one of: (i) a serving cell index of the first serving cell or (ii) one or more TCI state IDs in the TCI state list. Figure 3 to Figure 4, the base station 104 transmits 307 an RRC configuration including a first RRC parameter to the UE 102 via TRP1 106a and TRP2 106b, the first RRC parameter indicating the type (e.g., joint / separate) of the TCI state list of the second serving cell. The base station 104 also transmits 315 an RRC configuration including a second RRC parameter to the UE 102 via TRP1 106a and TRP2 106b, the second RRC parameter indicating how to determine the TCI state list of the second serving cell.

[0109] The second network entity 104 communicates 777 with the UE using another TCI state list of the second serving cell, the another TCI state list being based on the second parameter and the TCI state list of the first serving cell. Figure 3 to Figure 4 , the base station 104 communicates 377 with the UE 102 via TRP1 106a and TRP2 106b based on the updated serving beam of the UE 102. The communication 377 is based on the determined 375, 475 TCI state list of the second serving cell. Figure 8 The UE equipment 802 described in the flowchart 500 may perform the method of the flowchart 500. Fig. 9 One or more network entities 104 described in the flowcharts 600-700 may perform the methods of the flowcharts 600-700.

[0110] Figure 8 800 is a diagram illustrating an example of a hardware implementation of a UE equipment 802. Equipment 802 may be a UE 102, a component of a UE, or may implement UE functionality. In some aspects, equipment 802 may include a wireless baseband processor 824 (also referred to as a modem) coupled to one or more transceivers 822 (e.g., a wireless RF transceiver). The wireless baseband processor 824 may include on-chip memory 824'. In some aspects, equipment 802 may further include one or more subscriber identity module (SIM) cards 820 and an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810. The application processor 806 may include on-chip memory 806'.

[0111] Equipment 802 may further include a Bluetooth module 812, a WLAN module 814, an SPS module 816 (e.g., a GNSS module), and a cellular module 817 located within one or more transceivers 822. The Bluetooth module 812, the WLAN module 814, the SPS module 816, and the cellular module 817 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 812, the WLAN module 814, the SPS module 816, and the cellular module 817 may include their own dedicated antennas and / or communicate using antenna 880. The equipment 802 may further include one or more sensor modules 818 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial management unit (IMU), a gyroscope and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and / or other technologies for positioning), additional modules for memory 826, a power supply 830 and / or a camera 832.

[0112] The wireless baseband processor 824 communicates with another UE 102 and / or with a RU associated with the network entity 104 via one or more antennas 880 through the transceiver 822. The wireless baseband processor 824 and the application processor 806 can each include a computer-readable medium / memory 824', 806', respectively. The additional modules of the memory 826 can also be regarded as computer-readable media / memory. Each computer-readable medium / memory 824', 806', 826 can be non-temporary. The wireless baseband processor 824 and the application processor 806 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the wireless baseband processor 824 / application processor 806, enables the wireless baseband processor 824 / application processor 806 to perform the various functions described. The computer-readable medium / memory can also be used to store data manipulated by the wireless baseband processor 824 / application processor 806 when executing the software. The wireless baseband processor 824 / application processor 806 can be a component of the UE 102. The equipment 802 may be a processor chip (modem and / or applications) and include only the wireless baseband processor 824 and / or the application processor 806 , and in another configuration, the equipment 802 may be the entire UE 102 and include additional modules of the equipment 802 .

[0113] As discussed, the TCI state list determining component 140 is configured to receive a configuration of a transmission configuration indicator (TCI) state list for a first serving cell from a network entity, the first serving cell corresponding to a reference cell; receive a first parameter and a second parameter defining another TCI state list for a second serving cell from the network entity, the first parameter indicating a type of the another TCI state list for the second serving cell, the second parameter indicating at least one of: (i) a serving cell index for the first serving cell, or (ii) one or more TCI state identifiers (IDs) in the TCI state list; and communicate with the network entity using the another TCI state list for the second serving cell, the another TCI state list being based on the second parameter and the TCI state list for the first serving cell. The TCI state list determining component 140 may be located within the radio baseband processor 824, the application processor 806, or both the radio baseband processor 824 and the application processor 806. The TCI status list determination component 140 can be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0114] As shown, the equipment 802 may include various components configured for various functions. In one configuration, the equipment 802, and specifically the wireless baseband processor 824 and / or the application processor 806, includes: a component for receiving a configuration of a TCI state list of a first serving cell from a network entity, the first serving cell corresponding to a reference cell; a component for receiving a first parameter and a second parameter defining another TCI state list of a second serving cell from the network entity, the first parameter indicating the type of the another TCI state list of the second serving cell, the second parameter indicating at least one of: (i) a serving cell index of the first serving cell, or (ii) one or more TCI state IDs in the TCI state list; and a component for communicating with the network entity using the another TCI state list of the second serving cell, the another TCI state list being based on the second parameter and the TCI state list of the first serving cell. The equipment 802 further includes a component for performing at least one of downlink or uplink communication with the network entity. The equipment 802 further includes a component for determining at least one another TCI state list of the second serving cell based on at least one TCI state list or at least one of the second parameters. The apparatus 802 further includes means for receiving at least one of a MAC-CE or a DCI from a network entity, the MAC-CE or the DCI indicating one or more TCI states in another TCI state list. The means may be a TCI state list determination component 140 of the apparatus 802 configured to perform the functions recited by the means.

[0115] Fig. 9 900 is a diagram illustrating an example of a hardware implementation of one or more network entities 104. One or more network entities 104 may be a BS, a component of a BS, or may implement BS functionality. One or more network entities 104 may include at least one of a CU 110, a DU 108, or a RU 106. For example, a TCI state list configuration component 150 may be located at one or more network entities 104, such as at a CU 110; at both a CU 110 and a DU 108; at each of a CU 110, a DU 108, and a RU 106; at a DU 108; at both a DU 108 and a RU 106; or at a RU 106.

[0116] The CU 110 may include a CU processor 912. The CU processor 912 may include an on-chip memory 912'. In some aspects, the CU 110 may further include an additional memory module 914 and a communication interface 918. The CU 110 communicates with the DU 108 via a midhaul link 162 (such as an F1 interface). The DU 108 may include a DU processor 932. The DU processor 932 may include an on-chip memory 932'. In some aspects, the DU 108 may further include an additional memory module 934 and a communication interface 938. The DU 108 communicates with the RU 106 via a fronthaul link 160. The RU 106 may include a RU processor 942. The RU processor 942 may include an on-chip memory 942'. In some aspects, the RU 106 may further include an additional memory module 944, one or more transceivers 946, an antenna 980, and a communication interface 948. The RU 106 communicates wirelessly with the UE 102.

[0117] The on-chip memories 912', 932', 942' and the additional memory modules 914, 934, 944 can each be considered as a computer-readable medium / memory. Each computer-readable medium / memory can be non-temporary. Each of the processors 912, 932, 942 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0118] As discussed, the TCI state list configuration component 150 is configured to: transmit a configuration of a TCI state list of a first service cell to a UE, the first service cell corresponding to a reference cell; transmit a first parameter and a second parameter defining another TCI state list for a second service cell to the UE, the first parameter indicating a type of the another TCI state list for the second service cell, the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state IDs in the TCI state list; and communicate with the UE using the another TCI state list for the second service cell, the another TCI state list being based on the second parameter and the TCI state list for the first service cell. The TCI state list configuration component 150 is further configured to: transmit to the first network entity a configuration of a TCI state list of a first serving cell, the first serving cell corresponding to the reference cell; transmit to the first network entity a first parameter and a second parameter defining another TCI state list of a second serving cell, the first parameter indicating a type of the another TCI state list of the second serving cell, the second parameter indicating at least one of: (i) a serving cell index of the first serving cell, or (ii) one or more TCI state identifiers (IDs) in the TCI state list; and communicate with the UE using the another TCI state list of the second serving cell, the another TCI state list being based on the second parameter and the TCI state list of the first serving cell. The TCI state list configuration component 150 may be located within one or more processors of one or more of the CU 110, the DU 108, and the RU 106. The TCI state list configuration component 150 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 for implementation by one or more processors, or some combination thereof.

[0119] One or more network entities 104 may include various components configured for various functions. In one configuration, one or more network entities 104 include: a component for transmitting a configuration of a TCI state list of a first serving cell to a UE, the first serving cell corresponding to a reference cell; a component for transmitting a first parameter and a second parameter defining another TCI state list of a second serving cell to the UE, the first parameter indicating the type of the other TCI state list of the second serving cell, and the second parameter indicating at least one of: (i) a serving cell index of the first serving cell, or (ii) one or more TCI state IDs in the TCI state list; and a component for communicating with the UE using the other TCI state list of the second serving cell, the other TCI state list being based on the second parameter and the TCI state list of the first serving cell. One or more network entities 104 further include a component for performing at least one of downlink or uplink communications with the UE. One or more network entities 104 further include a component for configuring at least one other TCI state list of the second serving cell based on at least one TCI state list or at least one of the second parameters. The one or more network entities 104 further include means for transmitting at least one of a MAC-CE or a DCI to the UE, the MAC-CE or the DCI indicating one or more TCI states in another TCI state list.

[0120] In a further configuration, the one or more network entities 104 further include: means for transmitting to the first network entity a configuration of a TCI state list for a first serving cell, the first serving cell corresponding to the reference cell; means for transmitting to the first network entity a first parameter and a second parameter defining another TCI state list for a second serving cell, the first parameter indicating a type of the another TCI state list for the second serving cell, the second parameter indicating at least one of: (i) a serving cell index for the first serving cell, or (ii) one or more TCI state IDs in the TCI state list; and means for communicating with the UE using the another TCI state list for the second serving cell, the another TCI state list being based on the second parameter and the TCI state list for the first serving cell. The means may be a TCI state list configuration component 150 of the one or more network entities 104 configured to perform the functions recited by the means.

[0121] The specific order or hierarchy of the boxes in the process and flow chart disclosed herein is an illustration of an example method. Therefore, the specific order or hierarchy of the boxes in the process and flow chart can be rearranged. Some boxes can also be merged or deleted. Dashed lines can represent optional elements of the figure. The attached method claims present elements of each box in an example order and are not limited to the specific order or hierarchy presented in the claims, process and flow chart.

[0122] The detailed description set forth herein describes various configurations in conjunction with the accompanying drawings, but does not represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for providing a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form in order to avoid blurring such concepts.

[0123] Various aspects of wireless communication systems (such as telecommunication systems) are presented with reference to various equipment and methods. These equipment and methods are described in the detailed description that follows and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0124] Elements, or any part of elements or any combination of elements can be implemented as a "processing system" including 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, gating logic, discrete hardware circuits, and other similar hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system can execute software, which can be referred to as software, firmware, middleware, microcode, hardware description language, or other. 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, execution threads, processes, functions, or any combination thereof.

[0125] If the functions described herein are implemented in software, the functions may be stored on a computer-readable medium (such as a non-transitory computer-readable storage medium) or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media include computer storage media and 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 medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is accessible to a computer.

[0126] The aspects, implementations, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may be generated via integrated chip implementations and other non-module component-based devices such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, and the like. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein.

[0127] Devices incorporating the various aspects and features described herein may also include additional components and features for implementing and practicing the various aspects and features claimed and described. For example, the transmission and reception of wireless signals necessarily include many components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., in various configurations.

[0128] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be interpreted in view of the full scope of the disclosure consistent with the language of the claims.

[0129] Unless explicitly stated, references to singular elements do not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not imply an immediate temporal relationship or reaction. That is, phrases such as "when ..." do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a certain condition is met, a certain action will occur, but no specific or immediate time constraints are required for the occurrence of the action. Unless explicitly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B or C" or "one or more of A, B or C" include any combination of A, B and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B and / or multiple C, or may include only A, only B or only C. A set should be interpreted as a set of elements in which the number of elements is one or more.

[0130] Unless expressly indicated otherwise, ordinal terms such as "first" and "second" do not necessarily imply an order in time, sequence, value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term.

[0131] The structural equivalents and functional equivalents of the elements of various aspects described in the entire disclosure known or later learned by those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. The words "module", "mechanism", "element", "device", etc. may not be substitutes for the word "component". Therefore, unless the claim element is clearly stated using the phrase "component for...", any claim element shall not be interpreted as a means plus function. As used herein, the phrase "based on" should not be interpreted as a reference to a closed information set, one or more conditions, one or more factors, etc. In other words, unless clearly stated differently, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

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

[0133] Example 1 is a method for wireless communication at a UE, comprising: receiving a configuration of a TCI state list of a first service cell from a network entity, the first service cell corresponding to a reference cell; receiving a first parameter and a second parameter defining another TCI state list of a second service cell from the network entity, the first parameter indicating a type of the another TCI state list of the second service cell, the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state IDs in the TCI state list; and communicating with the network entity using the another TCI state list of the second service cell, the another TCI state list being based on the second parameter and the TCI state list of the first service cell.

[0134] Example 2 may be combined with Example 1 and include: configuration of the TCI state list is further directed to a third serving cell, the third serving cell corresponding to the second reference cell.

[0135] Example 3 may be combined with Example 1 and include: the other TCI state list of the second serving cell is further based on the TCI state list of a third serving cell, the third serving cell corresponding to the second reference cell.

[0136] Example 4 may be combined with any one of Examples 2-3 and include: the second parameter indicates a serving cell index, and the serving cell index further indicates a third serving cell.

[0137] Example 5 may be combined with any one of Examples 2-4 and include: the other TCI state list of the second serving cell is further based on a combination of the TCI state lists of the first serving cell and the third serving cell.

[0138] Example 6 may be combined with any one of Examples 1-4 and include: another TCI state list of the second serving cell corresponds to a subset of the TCI state list of the first serving cell.

[0139] Example 7 may be combined with any of Examples 1-6 and include: the TCI state list of the first service cell includes one or more combined TCI state lists corresponding to both the first TRP and the second TRP.

[0140] Example 8 may be combined with Example 7 and include: the one or more combined TCI state lists correspond to at least one of a joint TCI state list, a downlink TCI state list, or an uplink TCI state list.

[0141] Example 9 can be combined with any one of Examples 1-6 and include: the second parameter indicates one or more TCI state IDs, and the TCI state list of the first service cell includes one or more first TCI state lists of the first TRP, and the one or more first TCI state lists of the first TRP are separated from one or more second TCI state lists of the second TRP.

[0142] Example 10 may be combined with Example 9 and include: a TCI state ID in the one or more TCI state IDs corresponds to one or more first TCI state lists of the first TRP or one or more second TCI state lists of the second TRP.

[0143] Example 11 can be combined with Example 10 and include: the TCI state ID corresponds to one or more first TCI state lists of the first TRP, and includes: another TCI state list of the second service cell is based on one or more first TCI state lists of the first TRP or at least one of the second parameters.

[0144] Example 12 may be combined with any of Examples 1-11 and further include: receiving at least one of a MAC-CE or a DCI from a network entity, the MAC-CE or the DCI indicating one or more TCI states in another TCI state list.

[0145] Example 13 may be combined with any of Examples 1-12 and include: the TCI status list and the other TCI status list correspond to any of: (a) a joint type TCI status list of mTRP, or (b) a separate type TCI status list of mTRP.

[0146] Example 14 is a method of wireless communication at a network entity, comprising: transmitting a configuration of a TCI state list of a first service cell to a UE, the first service cell corresponding to a reference cell; transmitting a first parameter and a second parameter defining another TCI state list of a second service cell to the UE, the first parameter indicating a type of the another TCI state list of the second service cell, the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state IDs in the TCI state list; and communicating with the UE using the another TCI state list of the second service cell, the another TCI state list being based on the second parameter and the TCI state list of the first service cell.

[0147] Example 15 may be combined with Example 14 and include: configuration of the TCI state list is further directed to a third serving cell, the third serving cell corresponding to the second reference cell.

[0148] Example 16 may be combined with Example 14 and include: the other TCI state list of the second serving cell is further based on the TCI state list of a third serving cell, the third serving cell corresponding to the second reference cell.

[0149] Example 17 may be combined with any one of Examples 15-16 and include: the second parameter indicates a serving cell index, and the serving cell index further indicates a third serving cell.

[0150] Example 18 may be combined with any one of Examples 15-17 and include: the other TCI state list of the second serving cell is further based on a combination of the TCI state lists of the first serving cell and the third serving cell.

[0151] Example 19 may be combined with any one of Examples 14-17 and include: the other TCI state list of the second serving cell corresponds to a subset of the TCI state list of the first serving cell.

[0152] Example 20 may be combined with any of Examples 14-19 and include: the TCI state list of the first service cell includes one or more combined TCI state lists corresponding to both the first TRP and the second TRP.

[0153] Example 21 may be combined with Example 20 and include: one or more combined TCI state lists correspond to at least one of a joint TCI state list, a downlink TCI state list, or an uplink TCI state list.

[0154] Example 22 can be combined with any of Examples 14-19 and include: the second parameter indicates one or more TCI state IDs, and the TCI state list of the first service cell includes one or more first TCI state lists of the first TRP, and the one or more first TCI state lists of the first TRP are separated from one or more second TCI state lists of the second TRP.

[0155] Example 23 may be combined with Example 22 and include: a TCI state ID in the one or more TCI state IDs corresponds to one or more first TCI state lists of the first TRP or one or more second TCI state lists of the second TRP.

[0156] Example 24 can be combined with Example 23 and include: the TCI state ID corresponds to one or more first TCI state lists of the first TRP, and includes: another TCI state list of the second service cell is based on one or more first TCI state lists of the first TRP or at least one of the second parameters.

[0157] Example 25 may be combined with any one of Examples 14-24 and further include: transmitting at least one of a MAC-CE or a DCI to the UE, the MAC-CE or the DCI indicating one or more TCI states in another TCI state list.

[0158] Example 26 may be combined with any of Examples 14-25 and include: the TCI status list and the other TCI status list correspond to any of: (a) a joint type TCI status list of an mTRP, or (b) a separate type TCI status list of an mTRP.

[0159] Example 27 is a method for wireless communication at a second network entity, comprising: transmitting a configuration of a TCI state list of a first service cell to a first network entity, the first service cell corresponding to a reference cell; transmitting a first parameter and a second parameter defining another TCI state list of a second service cell to the first network entity, the first parameter indicating a type of the another TCI state list of the second service cell, the second parameter indicating at least one of: (i) a service cell index of the first service cell, or (ii) one or more TCI state IDs in the TCI state list; and communicating with a UE using the another TCI state list of the second service cell, the other TCI state list being based on the second parameter and the TCI state list of the first service cell.

[0160] Example 28 is an apparatus for wireless communication for implementing the method as described in any of Examples 1-27.

[0161] Example 29 is an apparatus for wireless communications including means for implementing the method of any of Examples 1-27.

[0162] Example 30 is a non-transitory computer readable medium storing computer executable code, which, when executed by a processor, causes the processor to implement the method as described in any one of Examples 1-27.

Claims

1. A method for wireless communication at a user equipment UE, comprising: receiving, from a network entity, a configuration of a transmission configuration indicator (TCI) state list of a first serving cell, the first serving cell corresponding to a reference cell; receiving, from the network entity, a first parameter and a second parameter defining another TCI state list for a second serving cell, wherein the first parameter indicates a type of the another TCI state list for the second serving cell, and the second parameter indicates at least one of the following: (i) a serving cell index of the first serving cell, or (ii) one or more TCI status identifiers ID in the TCI status list; as well as The another TCI state list of the second serving cell is used to communicate with the network entity, the another TCI state list being based on the second parameter and the TCI state list of the first serving cell.

2. The method of claim 1, wherein: The configuration of the TCI state list is further for a third serving cell, and the third serving cell corresponds to the second reference cell.

3. The method of claim 1, wherein: The another TCI state list of the second serving cell is further based on the TCI state list of a third serving cell, the third serving cell corresponding to a second reference cell.

4. The method according to any one of claims 2 to 3, wherein: The second parameter indicates the serving cell index, and the serving cell index further indicates the third serving cell.

5. The method according to any one of claims 2 to 4, wherein: The another TCI state list of the second serving cell is further based on a combination of the TCI state lists of the first serving cell and the third serving cell.

6. The method according to any one of claims 1 to 4, wherein: The another TCI state list of the second serving cell corresponds to a subset of the TCI state list of the first serving cell.

7. The method according to any one of claims 1 to 6, wherein: The TCI state list of the first serving cell includes one or more combined TCI state lists corresponding to both a first transmission reception point TRP and a second TRP.

8. The method of claim 7, wherein: The one or more combined TCI state lists correspond to at least one of a joint TCI state list, a downlink TCI state list, or an uplink TCI state list.

9. The method according to any one of claims 1 to 6, wherein: The second parameter indicates the one or more TCI state IDs, and the TCI state list of the first service cell includes one or more first TCI state lists of the first transmission receiving point TRP, and the one or more first TCI state lists of the first TRP are separated from one or more second TCI state lists of the second TRP.

10. The method of claim 9, wherein: A TCI state ID in the one or more TCI state IDs corresponds to the one or more first TCI state lists of the first TRP or the one or more second TCI state lists of the second TRP.

11. The method of claim 10, wherein: The TCI state ID corresponds to the one or more first TCI state lists of the first TRP, and wherein the other TCI state list of the second service cell is based on the one or more first TCI state lists of the first TRP or at least one of the second parameters.

12. The method of any one of claims 1 to 11, further comprising: At least one of a media access control element MAC-CE or downlink control information DCI is received from the network entity, the MAC-CE or the DCI indicating one or more TCI states from the other TCI state list.

13. The method according to any one of claims 1 to 12, wherein: The TCI status list and the another TCI status list correspond to any one of the following: (a) a list of TCI states of the combined type of multiple transmission reception points mTRP, or (b) List of TCI status of the isolated types of the mTRP.

14. A method of wireless communication at a network entity, comprising: Transmitting a configuration of a transmission configuration indicator TCI state list of a first serving cell to a user equipment UE, where the first serving cell corresponds to a reference cell; transmitting, to the UE, a first parameter and a second parameter defining another TCI state list of a second serving cell, wherein the first parameter indicates a type of the another TCI state list of the second serving cell, and the second parameter indicates at least one of the following: (i) a serving cell index of the first serving cell, or (ii) one or more TCI status identifiers ID in the TCI status list; as well as The another TCI state list of the second serving cell is used to communicate with the UE, the another TCI state list being based on the second parameter and the TCI state list of the first serving cell.

15. The method of claim 14, wherein: The configuration of the TCI state list is further for a third serving cell, and the third serving cell corresponds to the second reference cell.

16. The method of claim 14, wherein: The another TCI state list of the second serving cell is further based on the TCI state list of a third serving cell, the third serving cell corresponding to a second reference cell.

17. The method according to any one of claims 14 to 16, wherein: The TCI status list and the another TCI status list correspond to any one of the following: (a) a list of TCI states of the combined type of multiple transmission reception points mTRP, or (b) List of TCI status of the isolated types of the mTRP.

18. A method of wireless communication at a second network entity, comprising: Transmitting a configuration of a transmission configuration indicator (TCI) state list of a first serving cell to a first network entity, wherein the first serving cell corresponds to a reference cell; transmitting to the first network entity a first parameter and a second parameter defining another TCI state list for a second serving cell, wherein the first parameter indicates a type of the another TCI state list for the second serving cell, and the second parameter indicates at least one of the following: (i) a serving cell index of the first serving cell, or (ii) one or more TCI status identifiers ID in the TCI status list; as well as Communicate with a user equipment (UE) using the other TCI state list of the second serving cell, the other TCI state list being based on the second parameter and the TCI state list of the first serving cell.

19. An apparatus for wireless communication, comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to implement the method of any one of claims 1 to 18.

Images