Methods and apparatuses for implementing multi-transmission reception point operation in a wireless communication system

Abstract

The present disclosure provides systems, apparatus, equipment, and methods, including computer programs encoded on storage media, for M-TRP operation under a unified TCI state framework. A UE receives (440, 450) a first control signal from a network entity indicating a first set of transmission configuration indicator (TCI) states. The UE receives (460) a second control signal from the network entity scheduling a physical downlink shared channel (PDSCH) transmission of a multi-transmit receive point (M-TRP) scheme. The second control signal is associated with a second set of TCI states. The UE receives (480) the PDSCH transmission from the network entity using at least one TCI state of the first set of TCI states or using the second set of TCI states based on a configuration of the second control signal.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication, and more specifically to multiple transmit / receive point (M-TRP) operation in a wireless communication system. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface known as Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment (5G UE). Compared to previous generations of cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems typically provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple UEs (such as Orthogonal Frequency Division Multiple Access (OFDMA)). Improvements in mobile broadband have continued the development of such wireless communication technologies. For example, extending the unified Transmission Configuration Indicator (TCI) state framework to M-TRP operation is important; however, implementing M-TRP operation under a unified TCI state framework is challenging. Summary of the Invention

[0004] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] Under a unified TCI state framework, one or more unified TCI states can be indicated to the UE. These unified TCI states can be applied to downlink (DL) and / or uplink (UL) channels and reference signals (RS). The unified TCI state framework reduces signaling overhead and beam indication latency.

[0006] Physical downlink shared channel (PDSCH) transmissions can follow or apply an indicated uniform TCI state (e.g., a first, second, or both indicated uniform TCI states). However, for some control resource sets (CORESETs) or physical downlink control channels (PDCCHs), network (NW) entities can configure these CORESETs or PDCCHs to not follow or apply the indicated uniform TCI states. For example, an NW entity can configure CORESET#0 or at least the CORESET associated with a common search space (CSS) set to not follow or apply the indicated uniform TCI states. Typically, PDSCH transmissions scheduled by CORESET#0 or a CORESET associated with a CSS set carry common signals, such as broadcast signals. Other UEs within the same physical serving cell also receive such PDSCH transmissions. Therefore, determining whether a scheduled PDSCH can follow a uniform TCI state can have increased complexity when PDSCH transmissions are scheduled by these CORESETs.

[0007] 5G NR supports UE-initiated beam selection / switching, allowing the UE to report a recommended reference signal or uniform TCI state. The recommended reference signal or uniform TCI state can correspond to or be derived as the serving beam or serving TCI state for communication between the UE and the NW entity. In some examples, the NW entity can send further acknowledgments to confirm or approve the recommended reference signal or uniform TCI state. This reduces beam switching latency and avoids potential beam failures. However, the set of UL / DL channels or RSs that can apply the UE-recommended beam is not yet defined and may differ from the set of channels or RSs applying the uniform TCI state indicated by the NW entity. Therefore, determining which UL / DL channels or RSs can apply or follow the UE-recommended beam or TCI state can introduce increased complexity.

[0008] During cell handover, mobility (LTM) or mobility-based timekeeping (LTM) is triggered at Layer 1 / L2 (L1 / L2) to reduce latency. low-riseDuring the LTM (Low Mobility Time) triggering process, a field can be added to the PDCCH command for Early Timing Advance (TA) acquisition; this field can be referred to as the Cell Indicator field. This field can be used to indicate whether the triggered Random Access (RA) procedure is for the serving cell or an LTM candidate cell. However, for M-TRP 2 Early Timing Advance (2TA) scenarios, at least for inter-cell 2TA, another field can be introduced into the PDCCH command. This other field indicates which Physical Random Access Channel (PRACH) configuration to use, for example, a PRACH configuration for the serving cell or a PRACH configuration for a candidate cell (e.g., a neighboring cell). When these two fields coexist in the PDCCH command, interpreting them can introduce increased complexity.

[0009] This disclosure addresses the aforementioned and other deficiencies by determining the applicability of a uniform TCI state in receiving PDSCH transmissions, for example, determining whether / how / applying the indicated joint / DL TCI state for PDSCH transmissions scheduled by a CORESET that does not conform to the indicated joint / DL TCI state. PDSCH transmissions can be used to transmit cell-specific signals, such as broadcast signals. When PDSCH transmissions are scheduled by a PDCCH in a CORESET, whether the PDSCH transmission can use / apply / conform to the indicated joint / DL TCI state is based on whether the CORESET uses / applies / conforms to the indicated joint / DL TCI state and / or the downlink control information (DCI) format. As an example, the TCI selection field in the DCI or TCI selection parameters provided by higher layers only takes effect if the scheduling CORESET uses / applies / conforms to the indicated joint / DL TCI state. If the scheduling CORESET does not use / apply / conform to the indicated joint / DL TCI state, the scheduled PDSCH transmission uses / applies / conforms to the same beam as the scheduling CORESET. As another example, the TCI selection field or TCI selection parameter still works even when the CORESET does not use / apply / follow the indicated joint / DL TCI state. As yet another example, the TCI selection parameter only works when the CORESET uses / applies / follows the indicated joint / DL TCI state, but the TCI selection field still works even when the CORESET does not use / apply / follow the indicated joint / DL TCI state.

[0010] According to some aspects, the UE receives from the network entity a first control signal indicating a first Transport Configuration Indicator (TCI) state set. The UE receives from the network entity a second control signal that schedules Physical Downlink Shared Channel (PDSCH) transmission for a Multiple Transmitter Receiver Point (M-TRP) scheme. The second control signal is associated with a second TCI state set. Based on the configuration of the second control signal, the UE receives PDSCH transmission from the network entity using at least one TCI state from the first TCI state set or using the second TCI state set.

[0011] According to some aspects, the NW entity sends a first control signal to the UE indicating a first Transmission Configuration Indicator (TCI) state set. The NW entity sends a second control signal to the UE, which schedules Physical Downlink Shared Channel (PDSCH) transmission for a Multiple Transmitter Receiver Point (M-TRP) scheme. The second control signal is associated with a second TCI state set. Based on the configuration of the second control signal, the NW entity sends PDSCH transmission to the UE (102) using at least one TCI state from the first TCI state set or using the second TCI state set.

[0012] This disclosure also addresses the aforementioned and other deficiencies by determining which channels / RS can follow or apply the beam or TCI state suggested by the UE when UE-indicated beam selection / switching is enabled. In one example, the NW entity configures a signal to indicate whether a channel or RS applies the UE-indicated beam. This signal may include a Radio Resource Control (RRC) message, MAC-CE, or DCI. Whether a channel or RS applies the UE-indicated beam can be configured per channel, per RS, per channel group, or per RS ​​set. In another example, when reporting UE-indicated beams, the UE suggests / indicates which channel / RS can apply the UE-indicated beam. A channel or RS that uses / follows / applies the UE-indicated beam may not use / follow / apply the beam indicated by the NW, and vice versa.

[0013] According to some aspects, the UE receives a first control signal from a network entity, which configures UE-initiated beam selection for a Multiple Transmitter-Receiver Point (M-TRP) scheme. The UE sends a report to the network entity indicating one or more UE-selected beams based on a first control channel. The UE communicates with the network entity using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0014] According to some aspects, the NW entity sends a first control signal to the UE, which configures UE-initiated beam selection for a Multiple Transmit / Receive Point (M-TRP) scheme. The NW entity receives a report from the UE indicating one or more UE-selected beams based on a first control channel. The NW entity communicates with the UE using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0015] This disclosure further addresses the aforementioned and other deficiencies by determining how to interpret fields in the PDCCH command for triggering a contention-free random access (CFRA) procedure when the UE has both inter-cell 2TA and LTM configured. For inter-cell M-TRP 2TA, a first field (e.g., a second DCI field or a PRACH configuration field) is introduced in the PDCCH command to indicate which PRACH configuration to use to trigger the CFRA procedure. The first field may indicate a PRACH configuration for the serving cell or a PRACH configuration for a neighboring cell (e.g., a PRACH configuration associated with an additional physical cell identifier (PCI)). For the LTM procedure, a second field (e.g., a third DCI field or a cell indicator field) is introduced in the PDCCH command to indicate the candidate cell for which the triggered CFRA is intended. The second field may indicate one of the configured candidate cells or the serving cell. In one example, the first field (e.g., the PRACH configuration field) is applied when the second field (e.g., the cell indicator field) indicates the serving cell. In another example, the second field (e.g., the cell indicator field) is applied when the serving cell PRACH configuration is specified in the first field (e.g., the PRACH configuration field). In yet another example, a third field (e.g., a fourth DCI field) is introduced in the PDCCH command to indicate whether the first and / or second fields are applied.

[0016] According to some aspects, the UE receives a control signal from a network entity, which includes a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command. The first field indicates that the PDCCH command is used to trigger Contention-Free Random Access (CFRA) for the serving cell or a neighboring cell. The second field indicates that the PDCCH command is used to trigger a Low-Layer Triggered Mobility (LTM) procedure for the serving cell or a candidate cell. The UE communicates with the network entity based on at least one of the first or second fields of the control signal.

[0017] Depending on some aspects, the NW entity sends a control signal to the UE, which includes a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command. The first field indicates that the PDCCH command is used to trigger Contention-Free Random Access (CFRA) for the serving cell or neighboring cells. The second field indicates that the PDCCH command is used to trigger a Low-Layer Triggered Mobility (LTM) procedure for the serving cell or candidate cell. The NW entity communicates with the UE based on at least one of the first or second fields of the control signal.

[0018] By using the above technologies, M-TRP operation is implemented within a unified TCI framework. Beam selection / switching latency can be reduced. UE and NW entities can have a common understanding of the channel / RS applying the unified TCI state. Therefore, the risk of beam failure or radio link failure (RLF) can be reduced or avoided. The performance of the wireless system can be improved. Attached Figure Description

[0019] Figure 1 The illustration shows a wireless communication system according to an embodiment, which includes multiple user equipment (UEs) and network entities communicating through one or more cells.

[0020] Figure 2A An illustration shows an example system with distributed base stations and / or UEs according to an embodiment.

[0021] Figure 2B Demonstrates the implementation of embodiments in Figure 1 A diagram of an example base station in system B, which includes a central unit (CU) and a distributed unit (DU) of a distributed base station.

[0022] Figure 3A A diagram illustrating an example protocol stack according to an embodiment is shown.

[0023] Figure 3B A diagram illustrating another example protocol stack according to an embodiment is shown.

[0024] Figure 4 This is a signaling diagram illustrating the communication between the UE and the network entity for PDSCH transmission according to an embodiment.

[0025] Figure 5A This is an illustration showing an example of PDSCH transmission according to an embodiment.

[0026] Figure 5B This is an illustration showing another example of PDSCH transmission according to an embodiment.

[0027] Figure 5CThis is an illustration showing yet another example of PDSCH transmission according to an embodiment.

[0028] Figure 6 This is a signaling diagram illustrating the communication between the UE and a network entity for UE-initiated beam selection according to an embodiment.

[0029] Figure 7 This is a signaling diagram illustrating the communication between the UE and a network entity for interpreting PDCCH commands according to an embodiment.

[0030] Figure 8 This is a flowchart of a wireless communication method for PDSCH transmission at the UE according to an embodiment.

[0031] Figure 9 This is a flowchart of a method for wireless communication for PDSCH transmission at a network entity according to an embodiment.

[0032] Figure 10 This is a flowchart of a method for UE-initiated beam selection wireless communication at the UE according to an embodiment.

[0033] Figure 11 This is a flowchart of a method for beam selection wireless communication at a network entity according to an embodiment.

[0034] Figure 12 This is a flowchart of a method for wireless communication at the UE for interpreting PDCCH commands according to an embodiment.

[0035] Figure 13 This is a flowchart of a method for wireless communication at a network entity to indicate a PDCCH command, according to an embodiment.

[0036] Figure 14 This is a diagram illustrating a hardware implementation of an example UE device according to some embodiments.

[0037] Figure 15 This is a diagram illustrating the hardware implementation of one or more example network entities according to some embodiments. Detailed Implementation

[0038] Figure 1A diagram 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, while others may include a decomposed base station architecture. The aggregated base station architecture utilizes 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 across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can 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 / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0039] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality among two or more units located in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.

[0040] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium—such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 for transmitting or receiving information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0041] RU 106 can be configured to implement lower-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node managing RF processing functions or lower-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as lower-level functional partitioning.

[0042] RU 106 can send 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 beamset 132 of RU 106b and a second communication beamset 134b of UE 102b, which may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0043] Any combination or individual reference to RU 106, DU 108, and CU 110 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 the core network. Base station 104 may relay communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0044] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to transmit downlink / forward link communication to UE 102d via the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d, or receives uplink / reverse link communication from UE 102d.

[0045] 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 up to a total of Yx Each carrier allocated in MHz carrier aggregation Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) spectrum bandwidth, of which x Each component carrier (CC) is used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In the example, uplink and downlink carriers may be allocated asymmetrically, with more or fewer carriers allocated to the 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 carriers may be associated with secondary cells (SCells).

[0046] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0047] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmission directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more reception directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmission directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more reception directions of RU 106b. UE 102b can perform beam training to determine the optimal reception and transmission directions for beamformed signals. The transmission and reception directions of UE 102 and base station 104 / RU 106 can be the same or different.

[0048] In a further example, the beamformed signal can be transmitted between the first base station / RU 106a and the second base station 104e. For example, base station 104e of cell 190e can transmit the beamformed signal to RU 106a based on communication beam 138 in one or more transmission directions of base station 104e. RU 106a can receive the beamformed signal from base station 104e of cell 190e based on RU communication beam 136 in one or more reception directions of RU 106a. In a further example, base station 104e transmits a downlink beamformed signal to UE 102e based on communication beam 138 in one or more transmission directions of base station 104e. UE 102e receives the downlink beamformed signal from base station 104e based on UE communication beam 130 in one or more reception directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of base station 104e.

[0049] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In this case, base station 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0050] Uplink / downlink signaling can also be communicated via a Satellite Positioning System (SPS) 114. In the example, the SPS 114 associated with cell 190c can 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 can correspond to one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location systems. The SPS 114 can 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 angle of departure (DL-AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), uplink angle of arrival (UL-AoA), and / or other systems, signals, or sensors.

[0051] Still referencing Figure 1 In some aspects, any UE in UE 102 may include an M-TRP component 140 configured to receive from a network entity a first control signal indicating a first Transport Configuration Indicator (TCI) state set. The M-TRP component 140 is configured to receive from the network entity a second control signal that schedules Physical Downlink Shared Channel (PDSCH) transmissions for the M-TRP scheme. The second control signal is associated with a second TCI state set. The M-TRP component 140 is configured to receive PDSCH transmissions from the network entity based on the configuration of the second control signal, using at least one TCI state from the first TCI state set or using the second TCI state set. For example, a PDSCH transmission refers to data transmission performed via or through a PDSCH.

[0052] In some aspects, any of the base stations 104 or the network entity of the base station 104 may include a configuration component 150 configured to send a first control signal to the UE indicating a first Transmission Configuration Indicator (TCI) state set. The configuration component 150 is configured to send a second control signal to the UE that schedules Physical Downlink Shared Channel (PDSCH) transmission for a Multiple Transmitter Receiver (M-TRP) scheme. The second control signal is associated with a second TCI state set. The configuration component 150 is configured to send PDSCH transmission to the UE (102) based on the configuration of the second control signal, using at least one TCI state from the first TCI state set or using the second TCI state set.

[0053] Still referencing Figure 1In some respects, any of the UEs 102 may include an M-TRP component 140 configured to receive a first control signal from a network entity, the first control signal configuring UE-initiated beam selection for a Multiple Transmit / Receive Point (M-TRP) scheme. The M-TRP component 140 is configured to send a report to the network entity indicating one or more UE-selected beams based on a first control channel. The M-TRP component 140 is configured to communicate with the network entity using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0054] In some aspects, any of the base stations 104 or the network entity of the base station 104 may include a configuration component 150 configured to send a first control signal to the UE, the first control signal configuring UE-initiated beam selection for a Multiple Transmitter Receiver (M-TRP) scheme. The configuration component 150 is configured to receive a report from the UE indicating one or more UE-selected beams based on a first control channel. The configuration component 150 is configured to communicate with the UE using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0055] Still referencing Figure 1 In some aspects, any of UEs 102 may include an M-TRP component 140 configured to receive control signals from a network entity, the control signals including a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command. In some examples, the first field indicates that the PDCCH command is for triggering Contention-Free Random Access (CFRA) for the serving cell or a neighboring cell. In some examples, the first field indicates that the PDCCH command is for triggering CFRA for the serving cell or a candidate cell. The second field indicates that the PDCCH command is for triggering a Low-Layer Triggered Mobility (LTM) procedure for the serving cell or a candidate cell. The M-TRP component 140 is configured to communicate with the network entity based on at least one of the first or second fields of the control signal.

[0056] In some aspects, any of the base stations 104 or the network entity of the base station 104 may include a configuration component 150 configured to send a control signal to the UE, the control signal including a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command. In some examples, the first field indicates that the PDCCH command is for triggering Contention-Free Random Access (CFRA) for the serving cell or a neighboring cell. In some examples, the first field indicates that the PDCCH command is for triggering CFRA for the serving cell or a candidate cell. The second field indicates that the PDCCH command is for triggering a Low-Layer Triggered Mobility (LTM) procedure for the serving cell or a candidate cell. The configuration component 150 is configured to communicate with the UE based on at least one of the first or second fields of the control signal.

[0057] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with one or more other accompanying figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-Advanced (LTE-A), and other wireless technologies such as 6G. It should also be noted that the ideas, concepts, or embodiments in this document can be applied to problems or processes in LTE / NR / 6G or other RATs with similar considerations or concerns.

[0058] Figure 2A An illustration shows an example system 100b with distributed base stations and / or UEs according to an embodiment. (Reference) Figure 2A Examples of wireless communication system 200 include UE 102, base station (BS) 104a, base station 104b, and core network (CN) 115. Base stations 104a and 104b can operate in RAN 105 connected to core network (CN) 115. For example, CN 115 can be implemented as evolved packet core (EPC) 111 or fifth generation (5G) core (5GC) 160. In another example, CN 115 can also be implemented as a sixth generation (6G) core.

[0059] Base station 104a may utilize one or more transmit and / or receive points (TRPs) to cover one or more cells (e.g., cells 124 and 125), and base station 104b may similarly utilize one or more TRPs to cover one or more cells (e.g., cell 126). For example, base station 104a operates cell 124 using TRPs 107-1 and 107-2 and cell 125 using TRP 107-3, and base station 104b operates cell 126 using TRPs 109-1 and 109-2. Cells 124 and 125 operate on one or more of the same carrier frequencies. Cell 126 may operate on one or more of the same carrier frequencies as cells 124 and 125. Alternatively, cell 126 may operate on one or more carrier frequencies different from those of cells 124 and 125. In some implementations, base station 104a connects each of TRPs 107-1, 107-2, and 107-3 via a fiber optic connection or an Ethernet connection. If base station 104a is a gNB, then cells 124 and 125 are NR cells. If base station 104a is an (ng-)eNB, then cells 124 and 125 are Evolved Universal Terrestrial Radio Access (EUTRA) cells. Similarly, if base station 104b is a gNB, then cell 126 is an NR cell, and if base station 104b is an (ng-)eNB, then cell 126 is an EUTRA cell. Cells 124, 125, and 126 can be located in the same Radio Access Network Notification Area (RNA) or different RNAs. Generally, RAN 105 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. UE 102 can support at least 5G NR (or simply "NR") or E-UTRA air interfaces to communicate with base station 104a via TRP 107-1, TRP 107-2, and / or TRP-3. Similarly, UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interfaces to communicate with base station 104b via TRP 109-1 and / or TRP 109-2. Each of base stations 104a and 104b may be connected to CN 115 via an interface (e.g., an S1 or NG interface). Base stations 104a and 104b may also be interconnected via interfaces for interconnecting NG RAN nodes (e.g., X2 or Xn interfaces).

[0060] When a base station (e.g., BS 104a or 104b) transmits DL data via a TRP (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 109-1, or TRP 109-2), BS 104a can generate a packet containing the data and send the packet to TRP 107-1. For example, the packet may be a fronthaul transport protocol data unit. The TRP extracts the data from the packet and transmits the data. In some implementations, base station 104a may include control information for time-critical control and management information directly related to the data in the packet, and the TRP can transmit the data based on the control information. In some implementations, the data includes in-phase and quadrature (IQ) data, physical layer bit sequences, or MAC PDUs. When the TRP receives data from a UE (e.g., UE 102), the TRP generates a packet containing the data and sends the packet to base station 104a. In some implementations, the data includes IQ data, physical layer bit sequences, or MAC PDUs.

[0061] Among other components, EPC 111 may also include a Serving Gateway (SGW) 118, a Mobility Management Entity (MME) 113, and a Packet Data Network Gateway (PGW) 116. Generally, SGW 118 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., and MME 113 is configured to manage authentication, registration, paging, and other related functions. PGW 116 provides connectivity from UE 102 to one or more external packet data networks (e.g., Internet networks and / or Internet Protocol (IP) Multimedia Subsystem (IMS) networks). 5GC 160 includes User Plane Functions (UPF) 162, Access and Mobility Management Functions (AMF) 164, and / or Session Management Functions (SMF) 166. Generally, UPF 162 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.

[0062] like Figure 2A As shown, base station 104a supports cells 124 and 125, and base station 104b supports cell 126. Cells 124, 125, and 126 may partially overlap, allowing UE 102 to select, reselect, or switch from one of cells 124, 125, and 126 to another. For direct exchange of messages or information, base stations 104a and 104b may support X2 or Xn interfaces. Typically, CN 115 can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0063] Base station 104a is equipped with processing hardware 230, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable storage memory for storing instructions, which the one or more general-purpose processors execute. Additionally or alternatively, processing hardware 230 may include dedicated processing units. Processing hardware 230 may include a PHY controller 232 configured to transmit data and control signals on a physical DL channel and DL reference signal with one or more user equipments (e.g., UE 102) via one or more TRPs (e.g., TRP 107-1, TRP 107-2, and / or TRP 107-3). PHY controller 232 is also configured to receive data and control signals on a physical UL channel and / or UL reference signal with one or more user equipments via one or more TRPs (e.g., TRP 107-1, TRP 107-2, and / or TRP 107-3). In the example implementation, processing hardware 230 includes a MAC controller 234 configured to perform random access (RA) procedures with one or more user equipments, manage UL timing advances for one or more user equipments, receive UL MAC PDUs from one or more user equipments, and send DL MAC PDUs to one or more user equipments. Processing hardware 230 may further include an RRC controller 236 to implement procedures and message passing at the RRC sublayer of the protocol communication stack. Base station 104b may include processing hardware 240 similar to processing hardware 230. Specifically, components 242, 244, and 246 may be similar to components 232, 234, and 236, respectively.

[0064] UE 102 is equipped with processing hardware 250, which may include one or more general-purpose processors (such as a CPU), a non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. PHY controller 252 is also configured to receive data and control signals on the physical DL channel and / or DL ​​reference signals with base station 104a or 104b via one or more TRPs (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 109-1 and / or TRP 109-2). PHY controller 252 is also configured to transmit data and control signals on the physical UL channel and / or UL reference signals with base station 104a or 104b via one or more TRPs (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 109-1 and / or TRP 109-2). In the example implementation, processing hardware 250 includes a MAC controller 254 configured to perform random access procedures with base station 104a or 104b, manage UL timing advances for one or more user equipments, send UL MAC PDUs to or from base station 104a or 104b, and receive DL MAC PDUs from or from base station 104a or 104b. Processing hardware 250 may further include an RRC controller 256 to implement procedures and message passing at the RRC sublayer of the protocol communication stack.

[0065] Figure 2B Demonstrates the implementation of embodiments in Figure 1 The diagram illustrates an example base station in system B, which includes a central unit (CU) and distributed units (DU) of a distributed base station. Figure 2B The image illustrates an example distributed or decomposed implementation of one or both of base stations 104a and 104b. In this implementation, each of base stations 104a and / or 104b includes a central unit (CU) 110 and one or more distributed units (DUs) 108. CU 110 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the general-purpose processor, and / or dedicated processing units. For example, CU 110 may include a PDCP controller (e.g., PDCP controllers 234, 244), an RRC controller (e.g., RRC controllers 236, 246), and / or an RRC inactivity controller (e.g., RRC inactivity controllers 138, 148). In some implementations, CU 110 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, CU 110 does not include an RLC controller.

[0066] Each of DU 108 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. For example, the processing hardware may include: a MAC controller (e.g., MAC controller 232, 242) configured to manage or control one or more MAC operations or procedures (e.g., random access procedures); and / or an RLC controller configured to manage or control one or more RLC operations or procedures. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0067] In some implementations, RAN 105 supports Integrated Access and Backhaul (IAB) functionality. In some implementations, DU 108 operates as an IAB node, and CU 110 operates as an IAB donor.

[0068] In some implementations, CU 110 may include a logical node CU-CP 110A that hosts the control plane portion of the PDCP protocol for CU 110. CU 110 may also include a logical node CU-UP 110B that hosts the user plane portion of the PDCP and / or SDAP protocols for CU 110. CU-CP 110A may send control information (e.g., RRC messages, F1 application protocol messages), and CU-UP 110B may send data packets (e.g., SDAP PDUs or IP packets).

[0069] CU-CP 110A can connect to multiple CU-UP 110Bs via the E1 interface. CU-CP 110A selects the appropriate CU-UP 110B for the service requested by UE 102. In some implementations, a single CU-UP 110B can connect to multiple CU-CP 110As via the E1 interface. If CU-CP 110A and DU 108 belong to a gNB, CU-CP 110A can connect to one or more DU 108s via the F1-C and / or F1-U interfaces. If CU-CP 110A and DU 108 belong to an ng-eNB, CU-CP 110A can connect to DU 108 via the W1-C and / or W1-U interfaces. In some implementations, a DU 108 can connect to multiple CU-UP 110Bs under the control of the same CU-CP 110A. In this implementation, the connectivity between CU-UP 110B and DU108 is established by CU-CP 110A using bearer context management functionality.

[0070] Figure 3A A simplified example protocol stack 300 is shown for UE 102 to communicate with an eNB / ng-eNB or gNB (e.g., one or both of base stations 104a, 104b). In the example stack 300, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which in turn provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A further provides an RLC channel to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides data delivery services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can then direct to the SDAP sublayer 212 or the RRC sublayer ( Figure 3A (Not shown in the image) provides data transfer services. In some implementations, such as... Figure 3A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or dual connectivity (DC) implemented through the EUTRA and NR interfaces. Further, as... Figure 3A As shown, UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210.

[0071] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 (e.g., from an IP layer that is layered directly or indirectly on PDCP layer 208 or 210) receive packets that can be referred to as SDUs, and (e.g., to RLC layer 206A or 206B) output packets that can be referred to as PDUs. Except where the difference between SDU and PDU is relevant, for simplicity, this disclosure refers to both SDU and PDU as "packets".

[0072] On the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can direct data to the RRC sublayer ( Figure 3A (Not shown) provides a signaling radio bearer (SRB) for exchanging, for example, RRC messages or NAS messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide a data radio bearer (DRB) to support data exchange. The data exchanged on NR PDCP sublayer 210 can be SDAP PDUs, IP packets, or Ethernet packets.

[0073] Figure 3B A diagram illustrating another example protocol stack according to an embodiment is shown. Functionally segmenting the radio protocol stack is possible, as... Figure 3B The radio protocol stack 350 is shown in the diagram. The CU at one or both of base stations 104a and 104b can retain all control and upper-layer functions (e.g., RRC 214, SDAP 212, NR PDCP 210), while lower-layer operations (e.g., NRRLC 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support connectivity to the 5GC, NR PDCP 210 provides SRBs to RRC 214, and NR PDCP 210 provides DRBs to SDAP 212 and SRBs to RRC 214.

[0074] Figure 4 Signaling diagram 400 illustrates communication for PDSCH transmission between UE 102 and network entity 104 according to an embodiment. Network entity 104 may correspond to a base station or a base station element, such as RU 106, DU 108, CU 110, etc. Network entity 104 may communicate with UE 102 via TRP 107-1, 107-2, or 107-3. PDSCH transmission can refer to data transmission performed via PDSCH.

[0075] Network entity 104 can configure certain CORESETs or PDCCHs to not use, follow, or apply the indicated uniform TCI state. For example, network entity 104 can configure CORESET#0 or at least the CORESET associated with a Common Search Space (CSS) set to not use, follow, or apply the indicated uniform TCI state. Typically, PDSCH transmissions scheduled by CORESET#0 or a CORESET associated with a CSS set will carry common signals, such as broadcast signals. Such PDSCH transmissions are also received by other UEs in the same physical serving cell. Therefore, when PDSCH transmissions are scheduled by these CORESETs, determining whether the scheduled PDSCH can use (e.g., apply or follow) the uniform TCI state can have increased complexity.

[0076] refer to Figure 4UE 102 can send or report 410 UE capabilities for supporting a unified TCI state for the M-TRP scheme. Network entity 104 can receive 410 UE capabilities for supporting a unified TCI state for the M-TRP scheme. Network entity 104 can then send 420 a first RRC message, which includes RRC configuration for configuring a list of TCI states (e.g., one or more joint / DL TCI states). Network entity 104 can then send 430 a second RRC message, which includes RRC configuration for configuring which(s) of the indicated joint / DL TCI states are applied to the PDSCH. In some implementations, the first and second RRC messages can be the same RRC message. Network entity 104 then sends 440 a Media Access Control-Control Element (MAC-CE), which activates a subset (e.g., multiple joint / DL TCI states) of joint / DL TCI states from the list of joint / DL TCI states (e.g., configured joint / DL TCI states). UE104 receives a MAC-CE of 440 activating a subset of joint / DL TCI states from the joint / DL TCI state list. Network entity 104 can then send a DCI of 450 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. UE102 can receive a DCI of 450 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. If the MAC-CE activates only one joint / DL TCI state or indicates only two joint / DL TCI states, where each joint / DL TCI state is associated with a different TRP or TRP identifier, then these two activated joint / DL TCI states are the first indicated joint / DL TCI state and the second indicated joint / DL TCI state, respectively. In this case, sending the DCI of 450 can be skipped. The activated or indicated joint / DL TCI states may be referred to as the first TCI state set. The first TCI state set may include a subset of activated joint / DL TCI states from the joint / DL TCI state list (e.g., activated by MAC-CE), or one or more indicated joint / DL TCI states from the activated joint / DL TCI states (e.g., activated by DCI). The MAC-CE (whose activation is from a subset of joint / DL TCI states in the joint / DL TCI state list) or the DCI (whose indication is from one or more joint / DL TCI states from the activated joint / DL TCI states) may be referred to as the first control signal.The first control signal may include MAC-CE (which activates a subset of joint / DL TCI states from the joint / DL TCI state list) or DCI (which indicates one or more joint / DL TCI states from the activated joint / DL TCI states).

[0077] Then, network entity 104 sends a 460 PDCCH transmission in the CORESET that schedules PDSCH transmissions. UE 102 receives the 460 PDCCH transmission in the CORESET that schedules PDSCH transmissions. A PDCCH transmission can refer to a transmission performed via PDCCH. Scheduling a PDCCH transmission can include a DCI with DCI format 1_0 or DCI format 1_1 / 1_2. PDCCH transmissions (e.g., DCIs) in a scheduled CORESET (i.e., a CORESET with scheduled PDCCH / DCIs) may not use, apply, or follow the indicated joint / DL TCI states. One or more TCI states used to receive PDCCH transmissions (e.g., DCIs) in a scheduled CORESET can be referred to as a second TCI state set. The second TCI state set is used to receive the scheduled CORESET (e.g., PDCCH transmissions or DCIs). In some examples, the second TCI state set is different from the first TCI state set. In some other examples, the second TCI state set is the same as the first TCI state set.

[0078] UE 102 and / or BS 104 determine whether and how to use / apply the activated or indicated joint / DL TCI states to receive PDSCH transmissions based on the configuration of the scheduled PDCCH transmissions. In some examples, the configuration of the scheduled PDCCH transmissions includes whether the scheduled CORESET (i.e., the CORESET with scheduled PDCCH / DCI) applies / follows the indicated joint / DL TCI states. The configuration of the scheduled PDCCH transmissions may include whether the second TCI state set is different from the first TCI state set. The configuration of the scheduled PDCCH may further include a DCI format, which includes DCI format 1_0 or DCI format 1_1 / 1_2.

[0079] Subsequently, network entity 104 sends 480 PDSCH transmissions scheduled by the PDCCH in CORESET based on the configuration for scheduling PDCCH transmissions. UE 102 receives 480 PDSCH transmissions scheduled by the PDCCH in CORESET based on the configuration for scheduling PDCCH transmissions.

[0080] In some examples, TRPs (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 109-1, and / or TRP 109-2) may be associated with or identified by a TRP identifier. In some implementations, the NW entity (e.g., base station 104a or 104b) includes or configures the TRP identifier in the UL configuration, which the NW entity sends to the UE (e.g., UE 102) for UL transmission via the TRP identified by the TRP identifier. In some implementations, the UL configuration includes downlink control information (DCI) transmitted on the PDCCH, and / or physical uplink shared channel (PUSCH) configuration, physical uplink control channel (PUCCH) configuration, and / or sounding reference signal (SRS) configuration included in RRC messages (e.g., RRC reconfiguration messages or RRC recovery messages) sent by the NW entity to the UE. In some implementations, UL transmission includes PUSCH transmission, PUCCH transmission, and / or SRS transmission. In some implementations, the NW entity includes a TRP identifier in the DL configuration, and the NW entity sends this DL configuration to UE 102 for DL ​​transmission via the TRP identified by the TRP identifier. In one implementation, the DL configuration includes DCI transmitted on the PDCCH, and / or Channel State Information (CSI) resource configuration, Physical Downlink Shared Channel (PDSCH) configuration, and / or Physical Downlink Control Channel (PDCCH) configuration included in RRC messages (e.g., RRC Reconfiguration messages or RRC Recovery messages) sent by the NW entity to the UE. In some implementations, DL transmission includes CSI Reference Signal (CSI-RS) transmission, Synchronization Signal Block (SSB) transmission, PDSCH transmission, and / or PDCCH transmission.

[0081] In some examples, the NW entity does not send / configure the TRP identifier to the UE and uses an implicit indication to indicate the TRP to the UE. In one implementation, the implicit indication can be one of the following configuration parameters: CORESETPoolIndex , CORESETPoolIndex Values ​​(candidates) dataScramblingIdentityPDSCH , dataScramblingIdentityPDSCH2-r16 ,or PUCCH-ResourceGroup-r16 In this type of implementation, the UE derives the TRP (identifier) ​​from an implicit indication. In some implementations, the NW entity sends an RRC message (e.g., an RRC reconfiguration message or an RRC recovery message) to the UE that includes configuration parameters.

[0082] In some examples, the NW entity configures or indicates a first TRP identifier for the UE. In some implementations, the UE derives the first TRP identifier (value). In some implementations, the NW entity configures or indicates a second TRP identifier (value) for the UE. In some implementations, the UE derives the second TRP identifier (value). In some implementations, the first TRP identifier may be associated with a first TRP. In some implementations, the second TRP identifier may be associated with a second TRP.

[0083] In some implementations, the NW entity configures the serving cell to be associated with a first TRP or a first TRP identifier (value). In some implementations, the NW entity configures a first control resource set (CORESET) associated with the serving cell or the first TRP. The NW entity can configure... CORESETPoolIndex #0 is used to identify the first CORESET. In one implementation, the NW entity may send an RRC message (e.g., an RRC establishment message, an RRC reconfiguration message, or an RRC recovery message) to the UE, which configures the first CORESET and / or includes... CORESETPoolIndex #0. Therefore, the UE monitors the PDCCH on the first CORESET to receive DCI from the NW entity, which means the UE monitors the PDCCH or receives DCI from the NW entity (i.e., from the first TRP) via the first TRP. In this case, the UE determines CORESETPoolIndex #0 indicates the TRP (i.e., the first TRP) of the NW entity.

[0084] In one implementation, the NW entity configures the serving cell associated with the second TRP or the second TRP identifier (value). In other implementations, the second TAG is associated with a non-serving cell, and the NW entity indicates or configures this association in an RRC message. In one implementation, the NW entity configures the non-serving cell associated with the second TRP or the second TRP identifier (value). In some implementations, the NW entity configures the second CORESET to be associated with a serving cell, a non-serving cell, or the second TRP. The NW entity can configure... CORESETPoolIndex #1 is used to identify the second CORESET. In one implementation, the NW entity may send an RRC message (e.g., an RRC establishment message, an RRC reconfiguration message, or an RRC recovery message) to the UE, which configures the second CORESET and / or includes... CORESETPoolIndex #1. Therefore, the UE monitors the PDCCH on the second CORESET to receive DCI from the NW entity, which means the UE monitors the PDCCH or receives DCI from the NW entity (i.e., from the second TRP) via the second TRP. In this case, the UE determines... CORESETPoolIndex #1 indicates the TRP (i.e., the second TRP).

[0085] In some implementations, the NW entity can configure one or more TCI state lists for the component carrier (CC) of the serving cell for the UE, where the CC can be a PCell or SCell. For example, the NW entity can configure a joint TCI state list for the CC of the serving cell. For example, the NW entity can configure a DL TCI state list and / or a UL TCI state list for the CC of the serving cell. A joint TCI state list may include one or more joint TCI states. A DL TCI state list may include one or more DL TCI states. A UL TCI state list may include one or more UL TCI states.

[0086] In some implementations, the NW entity can configure the first RRC parameter for the UE. unifiedTCI-StateType The first RRC parameter unifiedTCI-StateType This can be configured per serving cell. This first RRC parameter... unifiedTCI- StateType This can indicate the type of TCI status list used for the serving cell. For example, the first RRC parameter. unifiedTCI-StateType It can indicate "joint" or "individual". First RRC parameter unifiedTCI-StateType One or more of the following purposes may be provided: if the first RRC parameter for the CC of the serving cell indicates "joint", the NW entity may explicitly or implicitly configure one or more joint TCI state lists for the UE for the CC of the serving cell or for the UE; if the first RRC parameter for the CC of the serving cell indicates "individual", the NW entity may explicitly or implicitly configure one or more DL TCI state lists for the CC of the serving cell for the UE; and / or if the first RRC parameter for the CC of the serving cell indicates "individual", the NW entity may explicitly or implicitly configure one or more UL TCI state lists for the CC of the serving cell for the UE.

[0087] In some examples, if the NW entity explicitly configures one or more TCI state lists for the UE to use for the serving cell's CC, this could mean that the NW entity is configured with RRC (e.g., ServingCellConfig (Explicitly) configure one or more TCI status lists for the serving cell's CC.

[0088] In some examples, if the NW entity implicitly configures one or more TCI state lists for the UE to use the serving cell's CC, it can mean at least one of the following: the NW entity configures (e.g., in RRC configuration)... ServingCellConfigThe UE configures one or more TCI status lists for other serving cells / CCs or reference serving cells / CCs; the UE references one or more TCI status lists for other serving cells / CCs or reference serving cells / CCs; and / or the UE determines that one or more TCI status lists for other serving cells / CCs or reference serving cells / CCs are also used for the CC of the serving cell.

[0089] In some examples, the NW entity may send a first MAC-CE (e.g., send 440 MAC-CE) to the UE when or after the NW entity configures one or more TCI status lists for the UE to use for the serving cell's CC; and / or when or after the UE references or determines one or more TCI status lists for the serving cell's CC.

[0090] In some examples, the first MAC-CE can activate or indicate one or more TCI states from one or more TCI state lists. The one or more TCI states activated / indicated by the first MAC-CE can be mapped to one or more TCI code points in the TCI field. In some cases, the UE can (directly) apply or use one or more TCI states activated / indicated by the first MAC-CE to (subsequently) perform DL and / or UL transmissions.

[0091] In some examples, if the number of TCI states activated / indicated by the first MAC-CE is greater than one, those TCI states activated / indicated by the first MAC-CE can be mapped to one or more TCI code points in the TCI field of the DCI. In some implementations, if the number of TCI states activated / indicated by the first MAC-CE is one, the UE can (directly) apply or use the TCI states activated / indicated by the first MAC-CE for (subsequently) performing DL and / or UL transmissions. In some implementations, if the number of TCI states activated / indicated by the first MAC-CE is two, and / or if the two TCI states activated / indicated by the first MAC-CE are associated with different TRP identifiers or applied to different TRPs, the UE can (directly) apply or use both TCI states activated / indicated by the first MAC-CE for (subsequently) performing corresponding DL and / or UL transmissions.

[0092] In some examples, a TCI state can be mapped to a TCI code point based on the first MAC-CE. In some cases, more than one TCI state can be mapped to a TCI code point based on the first MAC-CE. In some cases, a TCI code point may indicate one of the following: one or more joint TCI states (some joint TCI states may be TCI states associated with a first TRP (identifier), and other joint TCI states may be TCI states associated with a second TRP (identifier), one or more DL TCI states (some DL TCI states may be TCI states associated with a first TRP (identifier), and other DL TCI states may be TCI states associated with a second TRP (identifier), one or more ULTCI states (some UL TCI states may be TCI states associated with a first TRP (identifier), and other UL TCI states may be TCI states associated with a second TRP (identifier), or one or more DL TCI states and one or more UL TCI states (some DL TCI states and UL TCI states may be TCI states associated with a first TRP (identifier), and other DL TCI states and UL TCI states may be TCI states associated with a second TRP (identifier).

[0093] In some examples, the number of joint TCI states indicated by the NW entity in the TCI code point can be up to four. In some cases, the number of DL TCI states indicated by the NW entity in the TCI code point can be up to four. In some cases, the number of UL TCI states indicated by the NW entity in the TCI code point can be up to four.

[0094] For example, one of the following can be mapped to a TCI code point: a joint TCI state associated with a first TRP (identifier) ​​and another joint TCI state associated with a second TRP (identifier); a DL TCI state associated with a first TRP (identifier) ​​and a UL TCI state associated with a second TRP (identifier); a DL TCI state associated with a first TRP (identifier) ​​and another DL TCI state associated with a second TRP (identifier); a UL TCI state associated with a first TRP (identifier) ​​and another UL TCI state associated with a second TRP (identifier); a DL TCI state and a UL TCI state associated with a first TRP (identifier) ​​and a joint TCI state associated with a second TRP (identifier); a DL TCI state and a UL TCI state associated with a first TRP (identifier) ​​and a DL TCI state associated with a second TRP (identifier); or a DLTCI state and a UL TCI state associated with a first TRP (identifier) ​​and a UL TCI state associated with a second TRP (identifier).

[0095] In some examples, the UE may receive a first DCI indicating one or more TCI states (e.g., receiving a 450 DCI). The first DCI may indicate one or more TCI states via the TCI field in the first DCI. In response to receiving the first DCI, the UE may send a first acknowledgment signal to the NW entity via PUCCH or PUSCH transmission. In response to sending the first acknowledgment signal, the UE may apply or use one or more TCI states activated / indicated by the first DCI to perform DL and / or UL transmissions. In some cases, in response to sending the first acknowledgment signal, the UE may apply or use one or more TCI states activated / indicated by the first DCI to perform DL and / or UL transmissions after a first application period. In some cases, the UE may apply or use one or more TCI states activated / indicated by the first DCI to perform DL and / or UL transmissions starting from a first timeslot.

[0096] In some examples, the first time slot may be the earliest time slot following at least the first application time period after the last symbol transmitted in the PUCCH or PUSCH. In some cases, the earliest time slot (used to determine the first time slot) and / or the first application time period may be determined based on the active BWP with the smallest SCS among the active BWPs of carriers / serving cells applying one or more TCI states. In some cases, the first application time period may be in one of the following units: symbol, sub-time slot, time slot, subframe, frame, ms, or second. In some cases, the first application time period may be... beamAppTime .

[0097] In some examples, the UE may receive a first MAC-CE indicating one or more TCI states. For example, the first MAC-CE may indicate one TCI state. Alternatively, the first MAC-CE may indicate more than one TCI state, each of which may be associated with a different TRP or TRP identifier. For example, the first MAC-CE may indicate two TCI states, one associated with a first TRP (identifier) ​​and the other associated with a second TRP (identifier). In this case, the UE may not receive a DCI indicating one or more TCI states to be applied to subsequent DL and / or UL transmissions. In response to receiving the first MAC-CE, the UE may send a second acknowledgment signal to the NW entity via PUCCH or PUSCH transmission. In response to sending the second acknowledgment signal, the UE may apply or use one or more TCI states activated / indicated by the first MAC-CE to perform DL and / or UL transmissions. In some cases, in response to sending the second acknowledgment signal, the UE may apply or use one or more TCI states activated / indicated by the first MAC-CE to perform DL and / or UL transmissions after a second application period. In some cases, the UE may begin applying or using one or more TCI states activated / indicated by the first MAC-CE to perform DL and / or UL transmissions from the second time slot.

[0098] In some examples, the second timeslot can be the earliest timeslot following at least the second application time period after the (last) timeslot of the PUCCH or PUSCH transmission. In some cases, the second application time period can be... In some cases, μ This can be an SCS configuration used for PUCCH or PUSCH transmission; Can be used for The subcarrier spacing configuration, for a frequency range of 1, has a value of 0, and Depend on Provided, or not provided K-Mac In this case, .

[0099] In some examples, the NW entity may send a DCI (e.g., a first DCI) to indicate to the UE, for example, a first combined / DL / UL TCI state and / or a second combined / DL / UL TCI state via the TCI field in the DCI. In some cases, the first combined / DL / UL TCI state and / or the second combined / DL / UL TCI state may be derived from one or more TCI states activated by a first MAC-CE. In some other implementations, the NW entity may send a MAC-CE (e.g., a first MAC-CE) to indicate to the UE the first combined / DL / UL TCI state and / or the second combined / DL / UL TCI state, i.e., only the activation of the first combined / DL / UL TCI state and / or the second combined / DL / UL TCI state. The first combined / DL / UL TCI state may be referred to as the first combined TCI state, the first DL TCI state, or the first UL TCI state. The second combined / DL / UL TCI state may be referred to as the second combined TCI state, the second DL TCI state, or the second UL TCI state. In some cases, the first union / DL TCI state may be associated with the first TRP or the first TRP identifier. In some cases, the second union / DL TCI state may be associated with the second TRP or the second TRP identifier.

[0100] In some examples, the NW entity can configure one or more additional PCIs for the UE. One or more additional PCIs can correspond to one or more neighboring cells surrounding the UE's physical serving cell. In some cases, the additional PCI can be a physical cell index or a logical index corresponding to the physical cell index of a neighboring cell. If the CORESET or TCI state or RRC configuration is associated with or includes the additional PCI, it can mean that the CORESET or TCI state or RRC configuration is associated with, applied to, or transmitted from the neighboring cell corresponding to the additional PCI.

[0101] In some examples, the NW entity can configure one or more candidate cell configurations for the UE. These candidate cell configurations may include information about the UE's neighboring cells or non-serving cells. They may also include information about candidate target cells for the UE to perform the LTM procedure. The candidate cell configuration may include or may be... RRCReconfiguration information, CellGroupConfig IE or SpCellConfig One of the options in IE. The candidate cell can be the UE's currently configured / activated secondary cell (Scell).

[0102] In some examples, the candidate cell configuration may include at least one of the following: candidate cell configuration ID, PCI or a logical index of PCI (e.g., PCI index), one or more TCI status lists of candidate cells, configuration of DL RS (e.g., SSB or CSI-RS) for measuring L1-RSRP and / or L1-SINR for / in candidate cells, or configuration of UL RS (e.g., SRS) for measuring UL CSI for / in candidate cells.

[0103] In some examples, the NW entity can send cell handover commands to the UE. In one example, the NW entity can send cell handover commands via MAC-CE or PDSCH. In some implementations, the UE can receive a second DCI from the NW entity. The second DCI can schedule a PDSCH carrying the CSC.

[0104] In some examples, the cell handover command may indicate the target cell. In some implementations, the cell handover command may include a candidate cell configuration ID. It should be noted that throughout this disclosure, the target cell may be, or may represent, the candidate cell indicated by the cell handover command. In response to receiving the cell handover command or after the action time of the cell handover command, the UE may perform an LTM procedure based on the cell handover command. The UE may determine the target cell and / or its corresponding configuration based on the candidate cell configuration ID indicated in the cell handover command. Upon completion of the LTM procedure, the target cell indicated by the cell handover command may become the new serving cell or PCell. After completing the LTM procedure, the UE moves from the source cell to the target cell. It should be noted that throughout this disclosure, the source cell may be, or may represent, the (original or previous) serving cell prior to receiving the CSC or completing the LTM procedure.

[0105] In some examples, the CSC may include or carry at least one of the following information or fields: information for identifying the target cell, TA-related information, beam indication for the target cell (e.g., a combined or paired UL and DL unified TCI status (index)), and active DL / UL for the target cell or candidate cell. BWP, instructions for triggering an aperiodic TRS transmission from the target cell (wherein, if beam indication signaling for the target cell exists in the first CSC, the aperiodic TRS can be quasi-co-located (QCL) with the downlink reference signal configured in the beam indication signaling for the target cell), instructions for triggering CSI acquisition of the target cell and corresponding reporting to the target cell, instructions for triggering an aperiodic CSI-RS for path loss measurement for uplink power control (wherein, if beam indication signaling for the target cell exists in the first CSC, the aperiodic CSI-RS can be quasi-co-located (QCL) with the downlink reference signal configured in the beam indication signaling for the target cell), instructions for triggering an aperiodic SRS transmission to the target cell, or C-RNTI.

[0106] In some examples, the NW entity can configure a common CORESET for the UE, which can be one of the following CORESETs: - At least the CORESET associated with the Type 0-PDCCH CSS set on the main cell of the MCG. ○ In some cases, the Type0-PDCCH CSS set can be accessed through the MIB. pdcch-ConfigSIB1 Or through PDCCH-ConfigCommon In searchSpaceSIB1 Or through PDCCH-ConfigCommon In searchSpaceZero Configured for DCI format 1_0 with CRC scrambled by SI-RNTI. ○ In some cases, the Type0-PDCCH CSS set can be accessed via... searchSpaceZero By providing searchSpaceMCCH or searchSpaceMTCH supply searchSpaceID =0 is configured for DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI for broadcasting. - At least the CORESET associated with the Type 0A-PDCCH CSS set on the main cell of the MCG. ○ In some cases, the Type0A-PDCCH CSS set can be accessed via... PDCCH-ConfigCommon In sear chSpaceOtherSystemInformation Configured for DCI format 1_0 with CRC scrambled by SI-RNTI. - At least the CORESET associated with the Type 0B-PDCCH CSS set on the main cell of the MCG. ○ In some cases, the Type0B-PDCCH CSS set can be accessed via... searchSpaceMCCH and searchSpaceMTCH Configured for broadcasting using DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI. - At least the CORESET associated with the Type 1-PDCCH CSS set on the primary cell, ○ In some cases, the Type1-PDCCH CSS set can be accessed via... PDCCH-ConfigCommon In ra- SearchSpace Configured for DCI formats with CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI. - At least the CORESET associated with the Type 1A-PDCCH CSS set on the primary cell. ○ In some cases, the Type1A-PDCCH CSS set can be accessed via... PDCCH-ConfigCommon In sdt- SearchSpace Configured for DCI formats with CRC scrambled by C-RNTI or CS-RNTI, which can be associated with communication in the RRC_INACTIVE state. - At least the CORESET associated with the Type 2-PDCCH CSS set on the main cell of the MCG. ○ In some cases, the Type2-PDCCH CSS set can be accessed via... PDCCH-ConfigCommon In pagingSearchSpace Configured for DCI format 1_0 with CRC scrambled by P-RNTI. - At least the CORESET associated with the Type2A-PDCCH CSS set on the main cell of the MCG, ○ In some cases, the Type2A-PDCCH CSS set can be accessed via... pei-ConfigBWP In pei- SearchSpace Configured for DCI format 2_7 with CRC scrambled by PEI-RNTI, or - At least the CORESET associated with the Type3-PDCCH CSS set, ○ In some cases, the Type3-PDCCH CSS set can be accessed via... PDCCH-Config In SearchSpaceTo configure, among which searchSpaceType = common This is for DCI formats with CRCs scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, or CI-RNTI, and only for the primary cell, for DCI formats with CRCs scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI, or ○ In some cases, the Type3-PDCCH CSS set can be accessed via... pdcch-ConfigMulticast In SearchSpace Configured for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, or ○ In some cases, the Type 3-PDCCH CSS set can be accessed via secondary cells. searchSpace MCCH and searchSpaceMTCH Configured for broadcasting DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI.

[0107] In some examples, the public CORESET can be configured by the NW entity to not follow or apply the indicated union / DL TCI state (e.g., the first union / DL TCI state or the second union / DL TCI state).

[0108] In some examples, the NW entity can configure a UE-specific CORESET for the UE. This UE-specific CORESET can be one of the following: a CORESET associated only with the Type 3-PDCCH CSS set on the primary cell, or a CORESET associated with the USS set on either the primary or secondary cell. In some cases, the Type 3-PDCCH CSS set can be configured via... PDCCH- Config In SearchSpace To configure, among which searchSpaceType = common This is for DCI formats with CRCs scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI; or in some cases, the USS set can be used... PDCCH-Config In SearchSpace To configure, among which searchSpaceType = ue - Specific, for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL semi-persistent scheduling V-RNTI.

[0109] In some examples, a UE-specific CORESET can always follow or apply the indicated joint / DL TCI state (e.g., the first joint / DL TCI state or the second joint / DL TCI state), i.e., without further RRC configuration to indicate whether to use / follow / apply.

[0110] Figures 5A to 5C This is an illustration of an example of PDSCH transmission according to an embodiment of this disclosure. For PDSCH transmissions scheduled by a CORESET without applying the indicated TCI, the DL beam indication can be based on whether the PDSCH transmission has a scheduling offset greater than or equal to a threshold. The threshold can be reported by the UE via a UE capability, configured by an NW entity, or predefined, for example, 28 symbols. Figures 5A to 5C An example of DL beam indication for PDSCH transmission in scenarios above a threshold is shown.

[0111] Figure 5A This is an illustration showing an example of a PDSCH transmission according to an embodiment (e.g., whether / how the indicated joint / DL TCI state is applied for a PDSCH transmission). Techniques related to performing beam indication and indicating DCI fields in PDCCH commands under the M-TRP scheme are discussed; for example, how to perform beam indication on a PDSCH scheduled by a CORESET that does not apply the indicated TCI state is discussed. As an example, at least for the S-DCI M-TRP scheme, performing beam indication is challenging when a PDSCH is scheduled by a scheduling CORESET that does not apply the indicated TCI state (e.g., CORESET#0 or (at least) a CORESET associated with a CSS).

[0112] In some examples, UE 102 uses at least one of the indicated TCI states (e.g., joint / DL TCI states) to apply / follow the configuration of the indicated joint / DL TCI state based on the scheduling DCI in the CORESET, and then further receives the PDSCH transmissions scheduled for 580-1a and 580-2a based on the DCI format; and / or the UE receives the PDSCH transmissions scheduled for 580-3a via the same quasi-co-location (QCL) assumption or the TCI state (e.g., a second TCI state set) of the CORESET (e.g., the DCI in the CORESET) used for reception, where the CORESET schedules the PDSCH when the CORESET is not configured to follow / apply the indicated joint / DL TCI state.

[0113] refer to Figure 5A UE 102 receives a MAC-CE of 540 activating a first subset of TCI states (e.g., multiple joint / DL TCI states) from a list of TCI states (e.g., configured joint / DL TCI states). UE 102 can then receive a DCI of 550 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. If the MAC-CE activates only one joint / DL TCI state or indicates only two joint / DL TCI states, where each joint / DL TCI state is associated with a different TRP or TRP identifier, then the two activated joint / DL TCI states are the first indicated joint / DL TCI state and the second indicated joint / DL TCI state, respectively. In this case, receiving the 550 DCI can be skipped.

[0114] Subsequently, UE 102 receives (e.g., decodes) a 560 DL scheduling DCI (e.g., PDCCH) on the CORESET for scheduling PDSCH transmission. DL beam determination for PDSCH can be based on whether the PDSCH transmission has a scheduling offset greater than or equal to a threshold. The threshold can be reported by the UE via UE capabilities, configured by the NW entity, or predefined, such as 28 symbols. When the scheduling offset is higher than the threshold, PDSCH can be scheduled via a DCI with DCI format 1_0 or DCI format 1_1 / 1_2. If the scheduling DCI has DCI format 1_1 / 1_2, the TCI selection field in the DCI can be used to indicate one or more joint / DL TCI states from the activated joint / DL TCI states for the DL beam. If the scheduling DCI has DCI format 1_0, the TCI selection parameter can be used to indicate one or more joint / DL TCI states for the DL beam. The TCI selection parameter can be an RRC parameter. The UE can receive the TCI selection parameter via an RRC message (not shown).

[0115] When the scheduling offset is below the threshold, if the UE supports more than one default beam, the TCI states indicated by the first and second indicators can be applied to the DL beam; if the UE does not support more than one default beam, the TCI state indicated by the first indicator can be used or applied to the DL beam.

[0116] For CORESET#0 or the CORESET associated with CSS (the common CORESET), CORESET#0 or the CORESET associated with CSS may not be configured to apply the indicated TCI state. In some examples, whether the indicated TCI state is applied can be the same for CORESET#0 (or the CORESET associated with CSS) and its scheduled PDSCH.

[0117] like Figure 5AAs shown, UE 102 and / or BS 104 determine whether and how 570-1a and 570-2a apply the activated or indicated joint / DL TCI state to receive PDSCH based on the scheduling PDCCH configuration. For example, the scheduling PDCCH configuration includes whether the scheduling CORESET (i.e., the CORESET with scheduling PDCCH / DCI) applies / follows the indicated joint / DL TCI state. UE 102 and / or BS 104 can determine whether and how 570-1a applies the activated or indicated joint / DL TCI state to receive PDSCH based on whether the scheduling CORESET applies / follows the indicated joint / DL TCI state. When the scheduling CORESET applies / follows (or is configured to apply / follow) the indicated joint / DL TCI state, UE 102 and / or BS 104 can determine how 570-2a applies the activated or indicated joint / DL TCI state to receive PDSCH based on the DCI format (such as DCI format 1_0 or DCI format 1_1 / 1_2).

[0118] In some examples, the NW entity can configure RRC parameters for the UE. For example, the RRC parameter is a second RRC parameter (e.g., refer to...). Figure 4 The UE can receive a second RRC parameter (430) from the NW entity. The NW entity can configure the second RRC parameter to indicate TCI selection for a PDSCH scheduled by DCI format 1_0. The second RRC parameter can be an RRC parameter used for TCI selection. The second RRC parameter can be applied to devices with DCI format 1_0 (e.g., applyIndicatedTCIState-DCI-1-0 The DCI-scheduled PDSCH is used for receiving PDSCH. In some examples, the NW entity can use a second RRC parameter to indicate to the UE which (or which) joint / DL TCI states are applied to receive PDSCH scheduled by the DCI. The candidate value indicated by the second RRC parameter can be the first joint / DL TCI state, or the second joint / DL TCI state, or both the first and second joint / DL TCI states.

[0119] In some examples, the second RRC parameter may be applied or valid only if the NW entity (e.g., via the TCI field in a DCI format 1_1 / 1_2) indicates both the first and second indicated joint / DL TCI states. If the NW entity (e.g., via the TCI field) indicates only the first indicated joint / DL TCI state or only the second indicated joint / DL TCI state, the UE may apply either indicated joint / DL TCI state (i.e., the first or the second indicated joint / DL TCI state) (e.g., via the TCI field) to receive PDSCH scheduled by a DCI with DCI format 1_0.

[0120] In some examples (e.g., via the TCI field in DCI format 1_1 / 1_2), the NW entity indicating both the first and second indicated joint / DL / UL TCI states may mean or refer to the UE maintaining either two active TCI states or maintaining either the first or second indicated joint / DL / UL TCI states. As discussed above, NW entity 104 configures one or more joint / DL / UL TCI states. NW entity 104 activates a subset of the configured joint / DL / UL TCI states. NW entity 104 may use the TCI field to indicate one or both of the activated joint / DL / UL TCI states. The one or more joint / DL / UL TCI states indicated by the TCI field may be referred to as the “indicated joint / DL / UL TCI state”. If only one or two configured joint / DL / UL TCI states are activated, the TCI field may be skipped, and the one or two activated joint / DL / UL TCI states become the “indicated joint / DL / UL TCI state”. The indicated combined / DL / UL TCI state includes one or more combined / DL / UL TCI states indicated by the TCI field, or one or two combined / DL / UL TCI states that are active when the TCI field is skipped. Second RRC message (e.g., reference) Figure 4 The UE can receive a second RRC parameter (430) from the NW entity, which is used to indicate which indicated joint / DL TCI state is applied to the PDSCH transmission scheduled by DCI format 1_0, because not all channels or RSs apply both indicated TCI states. For example, a channel may apply only the first indicated TCI state.

[0121] In some examples, if the NW entity does not configure the second RRC parameter, the UE can (only) apply the first joint / DLTCI state to receive PDSCH scheduled by DCI with DCI format 1_0. In some other examples, if the NW entity does not configure the second RRC parameter, and if the NW entity (via the TCI field) indicates only the first indicated joint / DL TCI state or only the second indicated joint / DL TCI state, the UE can apply either indicated joint / DL TCI state (i.e., the first or the second indicated joint / DL TCI state) to receive PDSCH scheduled by DCI with DCI format 1_0; if the NW entity (via the TCI field) indicates both the first and second indicated joint / DL TCI states, the UE can (only) apply the first joint / DL TCI state to receive PDSCH scheduled by DCI with DCI format 1_0.

[0122] In some examples, the NW entity may configure the second RRC parameter only in the secondary cell (SCell). Therefore, the second RRC parameter may be applicable only to the SCell. In some other examples, the NW entity may configure the second RRC parameter only in the primary cell (PCell) and / or primary-secondary cell (PSCell). Therefore, the second RRC parameter may be applicable only to the PCell and / or PSCell.

[0123] In some examples, the NW entity can configure a TCI selection field in a DCI with DCI format 1_1 / 1_2 to indicate TCI selection for PDSCH scheduled by a DCI with DCI format 1_1 / 1_2. For example, the TCI selection field is the first DCI field in a DCI with DCI format 1_1 or 1_2. In some examples, the first DCI field may not exist even if it is configured. In some examples, the first DCI field may exist only if the NW entity (via the TCI field) indicates both the first indicated joint / DL TCI state and the second indicated joint / DL TCI state. If the NW entity (via the TCI field) indicates only the first indicated joint / DL TCI state or only the second indicated joint / DL TCI state, the UE can apply either indicated joint / DL TCI state (i.e., the first or the second indicated joint / DL TCI state) to receive PDSCH scheduled by a DCI with DCI format 1_1 / 1_2.

[0124] In some examples, the first DCI field can be a field used for TCI selection (e.g., a TCI selection field). In some examples, the NW entity can use the first DCI field to indicate to the UE which (or which) joint / DL TCI states are applied to receive PDSCH scheduled by the DCI. The candidate value indicated by the first DCI field can be a first joint / DL TCI state, or a second joint / DL TCI state, or both.

[0125] In some examples, if the NW entity is not configured with the first DCI field in a DCI with DCI format 1_1 or 1_2, or if the first DCI field does not exist in a DCI with DCI format 1_1 or 1_2, the UE can apply both the first and second joint / DL TCI states to receive PDSCH scheduled by a DCI with DCI format 1_1 or 1_2.

[0126] In some examples, if the NW entity is not configured with the first DCI field in a DCI with DCI format 1_1 or 1_2, or if the first DCI field does not exist in a DCI with DCI format 1_1 or 1_2, then when the NW entity (via the TCI field) indicates only the first indicated joint / DL TCI state or only the second indicated joint / DL TCI state, the UE can apply either the first or the second indicated joint / DL TCI state to receive PDSCH scheduled by a DCI with DCI format 1_1 or 1_2; when the NW entity (via the TCI field) indicates both the first and second indicated joint / DL TCI states, the UE can apply both the first and second joint / DL TCI states to receive PDSCH scheduled by a DCI with DCI format 1_1 / 1_2.

[0127] In some examples, the second RRC parameter and / or the first DCI field may only apply to PDSCHs with a scheduling offset greater than or equal to a threshold. The threshold may be reported by the UE via UE capabilities, configured by the NW entity, or predefined, for example, 28 symbols.

[0128] In some examples, the NW entity can configure a third RRC configuration for the UE to indicate TCI selection for a CORESET. In some examples, the third RRC configuration can be an RRC configuration indicating whether the CORESET follows / applies an indicated uniform TCI state and / or indicating TCI selection for a CORESET. The third RRC configuration can be applied to CORESET#0, a common CORESET, or a UE-specific CORESET. In some examples, the NW entity can use this third RRC configuration to indicate to the UE which (or which) joint / DL TCI states are applied to the received CORESET. In some examples, the candidate values ​​to be applied to a UE-specific CORESET indicated by the third RRC configuration can be a first joint / DL TCI state, or a second joint / DL TCI state, or both first and second joint / DL TCI states. In some examples, the candidate values ​​to be applied to CORESET#0 or a common CORESET indicated by the third RRC configuration can be a first joint / DL TCI state, or a second joint / DL TCI state, or both first and second joint / DL TCI states, or neither first nor second joint / DL TCI states. The third RRC configuration configured for CORESET can instruct CORESET not to apply any of the states in the indicated joint / DL TCI states. The third RRC configuration can instruct the UE not to apply any of the states in the indicated joint / DL TCI states by indicating "neither the first nor the second joint / DL TCI states".

[0129] In some examples, if the NW entity does not configure a third RRC configuration for CORESET, it may mean that CORESET does not apply any of the states in the indicated federated / DL TCI state.

[0130] In some examples, the third RRC configuration can be configured per CORESET. In some implementations, the third RRC configuration for at least CORESET#0 or a common CORESET may include two RRC parameters: one indicating whether the CORESET follows / applies the indicated uniform TCI state, and the other indicating the TCI selection for the CORESET (i.e., first, second, or both). In some cases, the NW entity may configure the third RRC configuration only for UEs operating in M-TRP S-DCI mode. In other cases, the NW entity may configure the third RRC configuration for UEs operating in either M-TRP S-DCI mode or M-TRP M-DCI mode.

[0131] Still referencing Figure 5AIn some examples, UE 102 uses at least one of the indicated TCI states (e.g., combined / DL TCI states) to receive 580-1a and 580-2a PDSCH transmissions based on the configuration of the CORESET indicating / carrying the scheduling DCI, and then further uses / applies / follows the indicated TCI state based on the DCI format. In some examples, the TCI selection field or TCI selection parameter only takes effect when the scheduling DCI in the CORESET applies / follows the indicated TCI state. In some examples, the UE receives 580-1a scheduled PDSCHs via the indicated combined / DL TCI state instructed by the second RRC parameter. The second RRC parameter can only be applied to PDSCHs scheduled by DCI format 1_0 if the scheduling DCI in the CORESET used for PDSCH transmission is configured to apply / follow the indicated combined / DL TCI state.

[0132] In some examples, the UE receives 580-3a scheduled PDSCH transmissions via the same QCL assumption or a TCI state (e.g., a second TCI state set) for receiving a CORESET (e.g., a DCI within the CORESET), which schedules PDSCHs when the CORESET is not configured to follow / apply the indicated joint / DL TCI state. If the scheduled CORESET is CORESET#0 or a common CORESET and / or if the scheduled CORESET does not apply / follow the indicated joint / DL TCI state, the UE may not follow or apply instructions from the second RRC parameter for receiving PDSCHs scheduled by DCI format 1_0. In some examples, this may apply to PCell or PSCell. In some examples, this may apply to scheduling PDSCHs in one of the following search spaces: Type 0 / 0A / 0B / 1 / 1A / 1B / 2 common search space, where the search space type is defined in Section 10.1 of 3GPP TS 38.213.

[0133] In some examples, the UE receives PDSCH transmissions scheduled by 580-2a via the combined / DL TCI state indicated by the instructions in the first DCI field. The first DCI field can only be applied to PDSCH transmissions scheduled by DCI format 1_1 / 1_2 if the scheduling CORESET for PDSCH is configured to apply / follow the indicated combined / DL TCI state. In some examples, if the scheduling CORESET does not apply / follow the indicated combined / DL TCI state, the UE may not follow or apply the instructions from the first DCI field for receiving PDSCHs scheduled by DCI format 1_1 / 1_2.

[0134] The UE can receive 580-3a scheduled PDSCH transmissions via the same QCL assumptions or the TCI state (e.g., a second TCI state set) of the CORESET (e.g., the DCI in the CORESET) used to receive scheduled PDSCH. In some examples, the UE can apply or use the same beam or QCL assumptions or reference signals used to derive spatial reception parameters as the scheduling CORESET in 580-3a, or the same TCI state, to receive PDSCH transmissions scheduled on the scheduling CORESET by DCI format 1_0 or DCI format 1_1 / 1_2.

[0135] In some examples, if the scheduling CORESET does not apply / does not follow the indicated joint / DL TCI state, the UE may apply or use the same beam or QCL assumption or reference signal used to derive spatial reception parameters as the scheduling CORESET (580-3a), or the same TCI state, to receive PDSCH transmissions scheduled on the scheduling CORESET by DCI format 1_0 or DCI format 1_1 / 1_2; otherwise, the UE may apply or use the indicated joint / DL TCI state (indicated by the first TCI field or the second RRC parameter) for PDSCH transmissions (580-1a, 580-2a) to receive the scheduled PDSCH transmissions.

[0136] Figure 5B This illustration shows another example of PDSCH transmission according to an embodiment. In some examples, when the scheduling CORESET does not apply / follow the indicated TCI state, the UE uses at least one of the indicated joint / DL TCI states to receive 580-1b and 580-2b PDSCH transmissions based on the TCI selection parameter or TCI selection field associated with the DCI format. Even when the scheduling CORESET does not apply / follow the indicated TCI state, the TCI selection field or TCI selection parameter can still function.

[0137] refer to Figure 5B UE 102 receives a MAC-CE 540 activating from a first subset of TCI states (e.g., multiple joint / DL TCI states) in a TCI state list (e.g., configured joint / DL TCI states). UE 102 can then receive a DCI 550 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. Afterwards, UE 102 receives (e.g., decodes) a DL-scheduled DCI 560b (e.g., PDCCH) on a CORESET that schedules PDSCH transmissions, and the CORESET can be configured not to follow / apply the indicated joint / DL TCI states.

[0138] like Figure 5B As shown, UE 102 and / or BS 104 determine whether and how 570b applies the activated or indicated joint / DL TCI state to receive PDSCH based on the DCI format of the scheduling DCI (such as DCI format 1_0 or DCI format 1_1 / 1_2).

[0139] In some examples, when the scheduling CORESET does not apply / follow the indicated TCI state, the UE receives 580-1b PDSCH transmissions via the indicated joint / DL TCI state as instructed by the RRC parameter (e.g., the second RRC parameter) for PDSCH scheduled by DCI format 1_0. Even if the scheduling CORESET for PDSCH does not apply / follow the indicated joint / DL TCI state, the second RRC parameter may still apply to PDSCH scheduled by DCI format 1_0. In some examples, if the scheduling CORESET does not apply / follow the indicated joint / DL TCI state, the UE may still follow or apply the 580-1b instruction from the second RRC parameter for receiving PDSCH scheduled by DCI format 1_0. In some examples, this may apply to secondary cells (SCells). In some examples, this may apply to scheduling PDSCH in one of the following search spaces: the Type 3 common search space or a UE-specific search space, where the search space type is defined in Section 10.1 of 3GPP TS 38.213.

[0140] In some examples, when the scheduling CORESET does not apply / follow the indicated TCI state, the UE receives the 580-2b PDSCH transmission via the indicated joint / DL TCI state as specified in the first DCI field instruction for the PDSCH scheduled by DCI format 1_1 / 1_2. Even if the scheduling CORESET does not apply / follow the indicated joint / DL TCI state, the first DCI field may still be applicable to the PDSCH scheduled by DCI format 1_1 / 1_2. In some examples, if the scheduling CORESET does not apply / follow the indicated joint / DL TCI state, the UE may still follow or apply the 580-2b instruction from the first DCI field for receiving the PDSCH scheduled by DCI format 1_1 / 1_2.

[0141] Figure 5CThis is an illustration showing another example of PDSCH transmission according to an embodiment. In some examples, the TCI selection parameter only takes effect when the scheduling CORESET applies / follows the indicated TCI state, but the TCI selection field still takes effect even when the scheduling CORESET does not apply / follow the indicated TCI state.

[0142] refer to Figure 5C UE 102 receives a MAC-CE at 540 activating from a first subset of TCI states (e.g., multiple joint / DL TCI states) in the TCI state list (e.g., configured joint / DL TCI states). UE 102 may receive a DCI at 550 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. Then, UE 102 receives (e.g., decodes) a DL-scheduled DCI (e.g., PDCCH) at 560 on the CORESET that schedules PDSCH transmissions.

[0143] like Figure 5C As shown, UE 102 and / or BS 104 can determine whether and how 570-1c applies the activated or indicated joint / DLTCI state to receive PDSCH based on the DCI format of the scheduling DCI (such as DCI format 1_0 or DCI format 1_1 / 1_2). If the DCI format is DCI format 1_0, UE 102 and / or BS 104 can determine whether 570-2c uses or applies the activated or indicated TCI state to receive PDSCH based on the TCI selection parameters, or determine whether the activated or indicated TCI state is not used based on whether CORESET is configured to follow / apply the indicated TCI state.

[0144] In some examples, if the PDSCH is scheduled on the scheduling CORESET using DCI format 1_0, the UE can receive the 580-3c scheduled PDSCH transmission via the same QCL assumption or the TCI state used to receive the CORESET (e.g., a second TCI state set) when the scheduling CORESET for the PDSCH does not apply / follow the indicated joint / DL TCI state; and when the scheduling CORESET for the PDSCH applies / follows the indicated joint / DL TCI state, the UE can receive the 580-2c scheduled PDSCH transmission via the joint / DL TCI state indicated by the second RRC parameter instruction. If the PDSCH is scheduled on the scheduling CORESET using DCI format 1_0, the second RRC parameter may not be applicable to the PDSCH when the scheduling CORESET for the PDSCH does not apply / follow the indicated joint / DL TCI state. In this case, the UE may not follow or apply the instruction from the second RRC parameter for receiving the PDSCH scheduled by DCI format 1_0. In this case, the UE may not follow or apply the instructions from the second RRC parameters for receiving PDSCH scheduled by DCI format 1_0. In this case, the UE may apply or use the same beam or QCL assumption or reference signal used to derive spatial reception parameters as the scheduling CORESET, or the same TCI state to receive PDSCH.

[0145] In some examples, if the PDSCH is scheduled on a scheduling CORESET using DCI format 1_1 / 1_2, the UE receives the 580-1c scheduled PDSCH transmission via the joint / DL TCI state indicated by the instructions in the first DCI field. When the PDSCH is scheduled on a scheduling CORESET using DCI format 1_1 / 1_2, the first DCI field may still be applicable to the PDSCH even if the scheduling CORESET used for the PDSCH does not apply / follow the indicated joint / DL TCI state. In this case, the UE may still follow or apply the instructions from the first DCI field for receiving the PDSCH scheduled by DCI format 1_1 / 1_2. In some cases, this may apply to the PCell or PSCell. In some cases, this may apply to scheduling the PDCCH in one of the following search spaces: Type 0 / 0A / 0B / 1 / 1A / 1B / 2 common search space, where the search space type is defined in Section 10.1 of 3GPP TS 38.213.

[0146] In some examples, UE 102 and / or BS 104 are based on combinations such as Figures 5A to 5CThe UE capability (or RRC configuration) of the technology described herein determines whether and how to apply the activated or indicated joint / DL TCI state to receive PDSCH transmissions.

[0147] In some examples, the NW entity can configure whether PDSCH transmissions scheduled by a CORESET that does not apply / do not follow the indicated joint / DL TCI state should follow / apply the indicated joint / DL TCI state. If the NW entity configures PDSCH transmissions to apply / follow the indicated joint / DL TCI state, the UE can receive PDSCH transmissions using one of the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both of the first and second indicated joint / DL TCI states, regardless of whether its scheduling CORESET applies / follows the indicated joint / DL TCI state. If the NW entity configures PDSCH transmissions to apply / follow the indicated joint / DL TCI state, the second RRC parameter and / or the first DCI field (if configured) can be used to indicate whether to use the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both of the first and second indicated joint / DL TCI states to receive PDSCH, regardless of whether its scheduling CORESET applies / follows the indicated joint / DL TCI state.

[0148] In some examples, the NW entity can configure, based on UE capabilities, whether PDSCH transmissions scheduled by a CORESET that does not apply / do not comply with the indicated joint / DL TCI state should comply with / apply the indicated joint / DL TCI state. The UE can indicate whether it supports PDSCH transmissions scheduled by a CORESET that does not apply / do not comply with the indicated joint / DL TCI state complying with / applying the indicated joint / DL TCI state.

[0149] Apart from Figures 5A to 5C Beyond the scenarios discussed herein, there are other scenarios. In some examples, before the UE successfully decodes the PDCCH that schedules the PDSCH transmission in a time slot, the UE may (attempt) buffer or receive a (potential) PDSCH transmission via one or more default beams or joint / DL TCI states. In some examples, the one or more default beams or joint / DL TCI states used by the UE to buffer / receive PDSCH transmissions may differ from those indicated by the second RRC parameter or the first DCI field.

[0150] In some examples, the UE may report a first UE capability to indicate one of the following: for M-TRP M-DCI mode or S-DCI mode, whether the UE supports two default beams or receive beams for buffering / receiving a PDSCH before the UE successfully decodes the PDSCH using the scheduled PDCCH; for M-TRP M-DCI mode or S-DCI mode, whether the UE supports two default beams or receive beams for receiving a PDSCH in which the scheduling offset between the scheduled PDCCH and the PDSCH is less than a threshold; for M-TRP M-DCI mode or S-DCI mode, whether the UE supports more than one default beam or receive beam for buffering / receiving a PDSCH before the UE successfully decodes the PDSCH using the scheduled PDCCH; or for M-TRP M-DCI mode or S-DCI mode, whether the UE supports more than one default beam or receive beam for receiving a PDSCH in which the scheduling offset between the scheduled PDCCH and the PDSCH is less than a threshold.

[0151] In some examples, the UE can apply the indicated TCI state regardless of its configuration. In some examples, if the UE indicates via a first UE capability that it supports two or more default beams for buffering / receiving PDSCH, and if the NW entity indicates the first and second indicated joint / DL TCI states, the UE can use the first and second indicated joint / DL TCI states to buffer / receive PDSCH in the time slot prior to the scheduled PDCCH that the UE successfully decodes. The UE can perform this behavior regardless of whether it is configured to monitor CORESETs that do not apply / follow the indicated joint / DL TCI states in the time slot.

[0152] In some examples, if the UE indicates via a first UE capability that it does not support two or more default beams for buffering / receiving PDSCH, and if the NW entity indicates the first and second indicated joint / DL TCI states, the UE may (only) use the first indicated joint / DL TCI state to buffer / receive PDSCH in the time slot prior to the scheduled PDCCH that the UE successfully decodes the PDSCH. The UE can perform this behavior regardless of whether it is configured to monitor CORESETs that do not apply / follow the indicated joint / DL TCI states in the time slot.

[0153] In some examples, if the NW entity indicates only one joint / DL TCI state (e.g., only the first or only the second indicated joint / DL TCI state), then regardless of whether the UE supports two or more default beams for buffering / receiving PDSCH, the UE can use the indicated joint / DL TCI state (first or second indicated joint / DL TCI state) to buffer / receive PDSCH before the UE successfully decodes the PDSCH in the time slot using the scheduled PDCCH.

[0154] In some examples, when determining how to buffer / receive PDSCH, the UE may consider not applying the DL beam of the CORESET with the indicated TCI state. If the UE indicates via a first UE capability that it supports two or more default beams for buffering / receiving PDSCH, when the UE is configured to monitor for CORESETs that do not apply / follow the indicated joint / DL TCI state in a time slot, the UE may use a third beam and one of the first or second indicated joint / DL TCI states to buffer / receive PDSCH in the time slot prior to the scheduled PDCCH for which the UE successfully decodes the PDSCH, where the NW entity indicates the first and second indicated joint / DL TCI states. If a CORESET does not apply the indicated TCI state, the UE may use the DL beam of the CORESET and one of the first or second indicated TCI states. Otherwise, the UE may use both the first and second indicated TCI states.

[0155] In some examples, the third beam may be a DL beam, a QCL assumption, a reference signal used to derive spatial reception parameters, or a TCI state for receiving a CORESET that does not apply / follow the indicated joint / DL TCI state. In some examples, if the UE is configured to monitor more than one CORESET that does not apply / follow the indicated joint / DL TCI state in a time slot, the third beam may be a DL beam, a QCL assumption, a reference signal used to derive spatial reception parameters, or a TCI state for receiving the CORESET with the lowest CORESET index among more than one CORESET. If the UE is not configured to monitor a CORESET that does not apply / follow the indicated joint / DL TCI state in a time slot (or there is no such CORESET), the UE may buffer / receive the PDSCH using the first and second indicated joint / DL TCI states in the time slot prior to the scheduled PDCCH that the UE successfully decodes the PDSCH, where the NW entity indicates the first and second indicated joint / DL TCI states.

[0156] In some examples, if the UE indicates via a first UE capability that it does not support two or more default beams for buffering / receiving PDSCH, and if there is a CORESET that does not apply the indicated TCI state, the UE can use the DL beam of the CORESET. Otherwise, the UE can select the first indicated TCI state. If the UE is configured to monitor CORESETs that do not apply / follow the indicated joint / DL TCI state in a time slot, the UE can use a third beam to buffer / receive PDSCH in a time slot prior to the scheduled PDCCH that the UE successfully decodes the PDSCH. In some cases, the third beam can be a DL beam or a QCL assumption or a reference signal used to derive spatial reception parameters, or a TCI state used to receive CORESETs that do not apply / follow the indicated joint / DL TCI state. In some cases, if the UE is configured to monitor more than one CORESET that does not apply / follow the indicated joint / DL TCI state in a time slot, the third beam may be a DL beam or a QCL assumption or a reference signal used to derive spatial reception parameters or a TCI state of the CORESET with the lowest CORESET index among more than one CORESET.

[0157] If the UE is not configured to monitor a CORESET that does not apply / follow the indicated joint / DL TCI state in a time slot (or there is no such CORESET), then when the NW entity indicates the first and second indicated joint / DL TCI states, the UE can use the first indicated joint / DL TCI state to buffer / receive the PDSCH in the time slot prior to the scheduled PDCCH for which the UE successfully decodes the PDSCH; alternatively, in this case, the UE can use the second indicated joint / DL TCI state.

[0158] If the UE is not configured to monitor for CORESETs that do not apply / follow the indicated joint / DL TCI state in a time slot (or there is no such CORESET), then when the NW entity indicates only one joint / DL TCI state (the first or second indicated joint / DL TCI state), the UE can use the indicated joint / DL TCI state (the first or second indicated joint / DL TCI state) to buffer / receive the PDSCH in the time slot before the UE successfully decodes the PDSCH's scheduled PDCCH.

[0159] Figure 6Signaling diagram 600 illustrates communication between UE 102 and network entity 104 for UE-initiated beam selection according to an embodiment. For example, UE-initiated beam selection / switching or updates can be supported in 5G NR, allowing the UE to report a recommended reference signal or uniform TCI state. The recommended reference signal or uniform TCI state can correspondingly become the serving beam or serving TCI state for communication between UE 102 and NW entity 104. In some implementations, NW entity 104 can send further acknowledgments to confirm the recommended reference signal or uniform TCI state. In this way, latency in beam switching is reduced, and potential beam failures can be avoided. However, the set of UL / DL channels or RSs for applying the UE-recommended beam may differ from the set of channels or RSs for applying the uniform TCI state indicated by NW entity 104. Therefore, determining how to perform UE-initiated beam switching, which UL / DL channels or RS can apply or follow the UE-selected beam (e.g., the UE-recommended beam) or TCI state, whether the NW entity sends feedback, and timeline issues are challenging.

[0160] refer to Figure 6 UE 102 can send or report 610 UE capabilities for supporting UE-initiated beam selection / switching. UE 102 can send 610 UE capability report to the network entity, which indicates the UE capabilities for supporting the M-TRP scheme based on UE-initiated beam selection. NW entity 104 can receive 610 UE capability report from the UE, which indicates the UE capabilities for supporting the M-TRP scheme based on UE-initiated beam selection.

[0161] NW entity 104 sends a first control signal (e.g., including RRC signals for RRC configuration) to the UE for 620 configuring UE-initiated beam selection. UE 102 receives the first control signal (e.g., including RRC signals for RRC configuration) from the network entity for 620 configuring UE-initiated beam selection / switching. NW entity 104 can configure UE-initiated beam selection / switching to the UE based on UE capabilities.

[0162] NW entity 104 can then send a second control signal 630 to configure / indicate whether a channel or RS applies / follows a UE-selected (e.g., UE-suggested, UE-preferred, or qualified) beam in a UE-initiated beam selection / switching. UE 102 can then receive the second control signal 630 to configure / indicate whether a channel or RS applies / follows a UE-selected (e.g., UE-suggested, UE-preferred, or qualified) beam in a UE-initiated beam selection / switching. The second control signal can indicate which DL / UL channel(s) or RS is suitable for applying one or more UE-selected (e.g., UE-preferred, or qualified) beams. The second control signal can be an RRC parameter, MAC-CE, or DCI. In some examples, the second control signal can be common to all DL and / or UL channels or RSs.

[0163] In some examples, the second control signal can be specific to a DL channel / RS or a UL channel / RS. For example, an NW entity can configure a first second control signal for a PDCCH, a second second control signal for a PUCCH, a third second control signal for an AP CSI-RS, a fourth second control signal for an SRS, and possibly more such second control signals for other channels and RSs. If the second control signal is an RRC signal, whether one or more UE-selected beams can be applied to a channel or RS can be configured per channel, per RS, per channel group, or per RS ​​set.

[0164] In some examples, UE 102 sends a 640 report to the network entity, indicating one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) based on a first control signal. NW entity 104 receives the 640 report from the UE, indicating one or more UE-selected beams based on the first control signal. If the NW entity configures UE-initiated beam selection / switching (620) to the UE, the UE can indicate one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) in the report (640). The indicated one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) can be a single beam or at least two beams, each associated with a different TRP or TRP identifier. The UE can report one or more beams for M-TRP operation. The UE can report one or more additional beams to update beams for channels / RS that do not conform to / do not apply the indicated joint / DL / UL TCI state (i.e., beams indicated by the NW). The UE can report, either in a single report or in separate reports, the beams of channels or RSs that comply with / apply the indicated joint / DL / UL TCI status and other beams of channels or RSs that do not comply with / do not apply the indicated TCI status.

[0165] In some examples, UE 102 may also suggest which channel / RS can use one or more UE-selected beams (e.g., UE-suggested, UE-preferred, or qualified beams) when reporting one or more UE-selected beams. The report may further indicate that at least one of the channels or reference signals uses one or more UE-selected beams.

[0166] In response to this report, NW entity 104 may provide feedback or send a 650 confirmation message to confirm that one or more UE-selected beams (e.g., UE-suggested, UE-preferred, or qualified beams) indicated by the UE can be applied. UE 102 may receive a 650 confirmation message to confirm that one or more UE-selected beams (e.g., UE-suggested, UE-preferred, or qualified beams) indicated by the UE can be applied.

[0167] UE 102 and / or NW entity 104 can determine, based on a second control signal, whether to apply one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) from a UE-initiated beam selection / switching to receive a channel or RS. UE 102 communicates with NW entity 104 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme 680. NW entity 104 communicates with UE 102 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme 680. For example, NW entity 104 uses / applies one or more UE-selected beams to transmit 680 the channel or RS indicated by the second control signal, while UE 102 uses / applies one or more UE-selected beams to receive 680 the channel or RS indicated by the second control signal. After sending a report or receiving an acknowledgment message, the UE can apply one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) from the report to a subset or all of the DL / UL channel or RS. After sending a report or receiving an acknowledgment message, the UE may apply one or more UE-selected beams from the report (e.g., UE-suggested, UE-preferred, or qualified beams) instead of the previously applied joint / DL / UL TCI state indicated by the NW entity or one or more UE-selected beams previously applied in the last report (e.g., UE-suggested, UE-preferred, or qualified beams). A channel or RS that follows / applies one or more UE-selected beams may not follow / apply the beams indicated by the NW, and vice versa.

[0168] In some examples, the reported one or more UE-selected (e.g., UE-preferred or qualified) beams may take the form of reference signals used to derive spatial transmit or receive parameters. In other examples, the reported one or more UE-selected (e.g., UE-preferred or qualified) beams may take the form of one or more joint / DL / UL TCI states. In some cases, the amount of reported joint / DL / UL TCI states may depend on whether joint or individual TCI state modes are configured, and / or whether S-TRP or M-TRP operation is configured.

[0169] In some examples, a channel or RS that can apply or follow the joint / DL / UL TCI state indicated by the NW entity may not be able to apply / follow one or more UE-selected (e.g., UE-preferred or qualified) beams reported. A channel or RS that cannot apply or follow the joint / DL / UL TCI state indicated by the NW entity may be able to apply / follow one or more UE-selected (e.g., UE-preferred or qualified) beams reported. For example, CORESET#0 configured to apply / follow the indicated joint / DL TCI state may not be able to apply / follow one or more UE-selected (e.g., UE-preferred or qualified) beams reported. As another example, a periodic CSI-RS configured not to apply / follow the indicated joint / DL TCI state may be able to apply / follow one or more UE-selected (e.g., UE-preferred or qualified) beams reported.

[0170] In some examples, the NW entity can configure the UE to report more than one (e.g., two) UE-selected (e.g., UE-preferred or qualified) beams for M-TRP operation, where each beam corresponds to a TRP or is associated with a TRP identifier. In one example, the first reported beam updates the first indicated joint / DL / UL TCI state, and the second reported beam updates the second indicated joint / DL / UL TCI state. Therefore, the UE applies the first reported beam to channels / RSs applying the first indicated joint / DL / UL TCI state, and the UE applies the second reported beam to channels / RSs applying the second indicated joint / DL / UL TCI state. In some other examples, the UE can report one or more additional beams to update beams for channels / RSs that do not conform to / do not apply the indicated joint / DL / UL TCI state. The UE can report beams in a single report or separately to update the beams for channels / RS that comply with or apply the indicated joint / DL / ULTCI state and to update the beams for channels / RS that do not comply with or do not apply the indicated TCI state.

[0171] Figure 7Signaling diagram 700 illustrates communication between UE 102 and network entity 104 for interpreting PDCCH commands according to an embodiment. For inter-cell M-TRP 2TA, a new DCI field (e.g., a first field or a second DCI field) is introduced in the PDCCH command to indicate which PRACH configuration to use to trigger contention-free random access (CFRA). The new DCI field (e.g., the first field or the second DCI field) may indicate a PRACH configuration for the serving cell or a PRACH configuration for a candidate cell (e.g., a neighboring cell, a PRACH configuration associated with an additional PCI). For LTM (L1 / L2 triggered mobility), a new DCI field (e.g., a second field or a third DCI field) is introduced in the PDCCH command to indicate which candidate cell the triggered CFRA is intended for. The new DCI field (e.g., the second field or the third DCI field) may indicate one of the configured candidate cells or the serving cell. Interpreting these two fields when both new DCI fields are present in the PDCCH command is challenging.

[0172] In some examples, if the NW entity configures an inter-cell M-TRP 2TA for the UE, the NW entity can configure one or more PRACH configurations associated with one or more configured additional PCIs for the UE. In some cases, each PRACH configuration in one or more PRACH configurations is associated with each additional PCI in one or more configured additional PCIs, i.e., a one-to-one mapping.

[0173] In some examples, the NW entity can configure the second DCI field in the PDCCH command to trigger CFRA. In some cases, the second DCI field can indicate whether the PDCCH command is triggering CFRA for the serving cell or neighboring cells. In some cases, the second DCI field can indicate whether the PDCCH command is associated with the serving cell PCI or neighboring cell PCI. In some cases, the second DCI field can indicate whether the PDCCH command is triggering CFRA for a TAG associated with the serving cell PCI or neighboring cell PCI. In some cases, the second DCI field can indicate whether the PRACH configuration associated with the serving cell PCI is applied, or whether the PRACH configuration associated with an additional PCI in the CFRA triggered by the PDCCH command is applied. The second DCI field can be a single field, where one candidate value indicates the PRACH configuration associated with the serving cell PCI, and another candidate value indicates the PRACH configuration associated with an additional PCI. The second DCI field can be a PRACH configuration indication field.

[0174] In some examples, the NW entity can configure the UE to perform LTM. In some cases, before the UE receives the CSC (or early TA acquisition), the NW entity can further configure the UE to preferably acquire the TA value via the RA procedure. If the NW entity configures the UE to acquire the TA value before the UE receives the CSC (or early TA acquisition), the NW entity can configure the third DCI field in the PDCCH command to trigger CFRA. In some cases, the third DCI field can indicate whether the PDCCH command is triggered for the serving cell or an LTM candidate cell. In some cases, the bit width of the third DCI field can be related to the number of LTM candidate cells with early TA acquisition. In some cases, the bit width of the third DCI field can be based on log( C It is determined by +1), where C This is the number of LTM candidate cells that have been configured / implemented with early TA acquisition. In some cases, a code point in the third DCI field is used to indicate the serving cell, such as the lowest code point ("0", "00", or "000") or the highest code point. The third DCI field can be a cell indicator field.

[0175] refer to Figure 7 UE 102 receives a control signal 720 from network entity 104, which includes a first field or a second field different from the first field in a PDCCH command. Network entity 104 sends the control signal 720 to UE 102, which includes a first field or a second field different from the first field in a PDCCH command. In some examples, the first field indicates that the PDCCH command is used to trigger a CFRA for the serving cell or candidate cell. In some examples, the first field indicates that the PDCCH command is used to trigger a CFRA for the serving cell or candidate cell. The second field indicates that the PDCCH command is used to trigger an LTM procedure for the serving cell or candidate cell. The UE and / or BS can determine 770 how to interpret the PDCCH command. UE 102 communicates 780 with network entity 104 based on at least one of the first field (e.g., a second DCI field) or the second field (e.g., a third DCI field) of the control signal. Network entity 104 communicates with UE 102 780 based on at least one of the first field (e.g., the second DCI field) or the second field (e.g., the third DCI field) of the control signal.

[0176] In some examples, the first field (e.g., the second DCI field or the PRACH configuration field) is applied only when the second or third DCI field (e.g., the cell indicator field) indicates the serving cell. In some examples, if both the second and third DCI fields are configured or present in the PDCCH command, the UE processes or applies only the second DCI field when the third DCI field indicates the serving cell, or when the third DCI field indicates the PDCCH command is for the serving cell, or when the third DCI field indicates the lowest (or alternatively the highest) code point.

[0177] For example, if the third DCI field indicates the serving cell, the UE can apply the PRACH configuration associated with the serving cell PCI or additional PCI according to the instructions from the second DCI field.

[0178] In some examples, the second field (e.g., the third DCI field or the cell indicator field) is applied only when the first field (e.g., the second DCI field or the PRACH configuration field) indicates the serving cell PRACH configuration. In some examples, if both the second and third DCI fields are configured or present in a PDCCH command, the UE processes or applies only the third DCI field when the second DCI field indicates that the PDCCH command is associated with the serving cell; or when the second DCI field indicates that the UE applies a PRACH configuration associated with the serving cell or serving PCI for a RA procedure triggered by a PDCCH command; or when the second DCI field indicates that the UE processes or applies only the third DCI field.

[0179] For example, if the second DCI field indicates that the PDCCH command is associated with the serving cell, the UE can apply the trigger RA procedure to the serving cell or LTM candidate cell according to the instructions from the third DCI field.

[0180] In some examples, a third DCI field (e.g., a fourth DCI field) is introduced in the PDCCH command to indicate whether the first or second DCI field is applied. The fourth DCI field may be configured by the NW entity or present in the PDCCH command if both the second and third DCI fields are configured or exist in the command, or if the NW entity has configured both inter-cell M-TRP 2TA and LTM. In some cases, the fourth DCI field may indicate whether the second or third DCI field in the PDCCH command is applied. In some cases, the fourth DCI field may indicate whether the PDCCH command is associated with either inter-cell M-TRP 2TA or LTM.

[0181] In some examples, the second and third DCI fields can be a single DCI field. In some cases, how this DCI field is interpreted can depend on the fourth DCI field. The bit width of a DCI field can be based on max(1, log( C It is determined by +1), where C It is the number of LTM candidate cells with early TA acquisition.

[0182] In some examples, if the fourth DCI field indicates that the PDCCH command is associated with an inter-cell M-TRP 2TA, the UE may use only one bit of the DCI field, and the remaining bits (if any) are reserved, and / or the UE may use one bit of the DCI field to determine whether to apply the PRACH configuration associated with the serving cell PCI or the PRACH configuration associated with an additional PCI in the CFRA triggered by the PDCCH command.

[0183] In some examples, if the fourth DCI field indicates that the PDCCH command is associated with LTM, the UE can use this DCI field to determine whether the PDCCH command is triggered for the serving cell or the LTM candidate cell. In some examples, the fourth DCI field can be a single bit of this DCI field.

[0184] In some examples, the second DCI field (PRACH configuration field) and the third DCI field (cell indicator field) are not allowed to coexist; for example, early TA acquisition for inter-cell 2TA and LTM cannot be configured together.

[0185] In some examples, the NW entity can avoid configuring both inter-cell M-TRP 2TA and LTM for the UE simultaneously. In some cases, the NW entity can avoid configuring both the second and third DCI fields in the PDCCH command simultaneously. In some cases, the NW entity may still be allowed to configure both intra-cell M-TRP 2TA and LTM for the UE simultaneously. Alternatively, the NW entity can avoid configuring both intra-cell M-TRP 2TA (or M-TRP 2TA) and LTM for the UE simultaneously.

[0186] In some examples, for a serving cell configured with LTM, the NW entity can avoid configuring more than one Timing Advance Group (TAG) for that serving cell or a serving cell group containing that serving cell. Alternatively, for a serving cell group configured with more than one TAG, the NW entity can avoid configuring LTM for any serving cell within that serving cell group. Alternatively, for a serving cell configured with more than one TAG, the NW entity can avoid configuring LTM for that serving cell.

[0187] In some other examples, for a serving cell configured with LTM, the NW entity may avoid configuring both an additional PCI and more than one TAG for that serving cell or a group of serving cells containing that serving cell. The NW entity may be allowed to configure only one of an additional PCI or more than one TAG for that serving cell or a group of serving cells containing that serving cell. Alternatively, for a group of serving cells configured with an additional PCI and more than one TAG, the NW entity may avoid configuring LTM for any serving cell within that group. Alternatively, for a serving cell configured with an additional PCI and more than one TAG, the NW entity may avoid configuring LTM for that serving cell.

[0188] In some examples, the UE may not expect to receive both the inter-cell M-TRP 2TA and LTM configurations simultaneously. In some cases, the UE may not expect the second DCI field and the third DCI field to be present in the PDCCH command at the same time.

[0189] In some examples, if the UE receives configurations for both the inter-cell M-TRP 2TA and LTM simultaneously, or if both the second and third DCI fields are present in the PDCCH command, the UE may discard or not use or process the configuration, or the UE may consider or determine that this is an error condition or an incorrect configuration, or the UE may perform RRC reconfiguration, or the UE may discard or not use or process the second and / or third DCI fields.

[0190] Figure 4 and Figures 5A to 5C An example of PDSCH transmission is shown. Figure 6 An example of beam selection initiated by the UE is shown. Figure 7 An example of interpreting the PDCCH command is shown. Figures 8 to 13 Showing the implementation Figures 4 to 7 One or more aspects of the method. Specifically, Figure 8 , Figure 10 and Figure 12 The UE 102 is shown to be paired with Figures 4 to 7 The implementation of one or more aspects. Figure 9 , Figure 11 and Figure 13 104 pairs of network entities are shown. Figures 4 to 7 The implementation of one or more aspects.

[0191] Figure 8 A flowchart 800 illustrates a method for wireless communication at the UE for PDSCH transmission according to an embodiment. (Reference) Figures 1 to 5CThis method can be performed by UE 102. In an embodiment, UE 102 can send an 810 UE capability report to network entity 104, which indicates that UE 102 supports UE capabilities under the M-TRP scheme. For example, refer to... Figure 4 UE102 can send or report 410 UE capabilities for supporting the unified TCI status of the M-TRP scheme.

[0192] UE 102 receives a first control signal from network entity 104 indicating a first TCI state set. For example, refer to... Figure 4 UE 102 receives a MAC-CE 440 activating a subset of joint / DL TCI states from the joint / DL TCI state list. UE 102 may receive a DCI 450 indicating one or more joint / DL TCI states from the activated joint / DL TCI states. If the MAC-CE activates only one joint / DL TCI state or indicates only two joint / DL TCI states, where each joint / DL TCI state is associated with a different TRP or TRP identifier, then the two activated joint / DL TCI states are the first indicated joint / DL TCI state and the second indicated joint / DL TCI state, respectively. In this case, sending the 450 DCI may be skipped. The first TCI state set may include a subset of activated joint / DL TCI states from the joint / DL TCI state list (e.g., activated by the MAC-CE), or one or more indicated joint / DL TCI states from the activated joint / DL TCI states (e.g., activated by the DCI). The first control signal may include MAC-CE or DCI, where MAC-CE activates a subset of joint / DL TCI states from the joint / DL TCI state list, and DCI indicates one or more joint / DL TCI states from the activated joint / DL TCI states.

[0193] UE 102 receives a second control signal 860 from network entity 104, which schedules PDSCH transmission for the M-TRP scheme. The second control signal is associated with a second TCI state set. For example, refer to... Figure 4 UE 102 receives 460 PDCCH transmissions in a CORESET that schedules PDSCH transmissions. One or more TCI states used to receive PDCCH transmissions (e.g., DCI) in a scheduled CORESET may be referred to as a second TCI state set. The second TCI state set is used to receive a scheduled CORESET (e.g., PDCCH transmissions or DCI).

[0194] Based on the configuration of the second control signal, UE 102 receives 880 PDSCH transmissions from network entity 104 using at least one TCI state from the first TCI state set or using the second TCI state set. For example, refer to... Figure 4 UE 102 receives PDSCH transmissions scheduled by PDCCH in CORESET based on the configuration of scheduling PDCCH transmissions. Figure 8 The method for the UE side of the wireless communication link is described, and Figure 9 The network-side methods for wireless communication links are described.

[0195] Figure 9 This is flowchart 900, which describes a method for wireless communication at a network entity. (Reference) Figures 1 to 5C This method can be performed by one or more network entities 104, which may correspond to a base station or a base station element, such as RU 106, DU 108, and / or CU 110. In an embodiment, network entity 104 may receive a UE capability report from UE 102, which indicates that UE 102 supports UE capabilities under the M-TRP scheme. For example, refer to... Figure 4 Network entity 104 can receive UE capabilities 410 for supporting the unified TCI state of the M-TRP scheme.

[0196] Network entity 104 sends a first control signal (940) to UE 102, indicating a first TCI state set. For example, refer to... Figure 4Network entity 104 sends a 440 MAC-CE, which activates a subset (e.g., multiple joint / DL TCI states) from a list of joint / DL TCI states (e.g., configured joint / DL TCI states). Network entity 104 may send a 450 DCI, which indicates one or more joint / DL TCI states from the activated joint / DL TCI states. If the MAC-CE activates only one joint / DL TCI state or indicates only two joint / DL TCI states, where each joint / DL TCI state is associated with a different TRP or TRP identifier, then the two activated joint / DL TCI states are the first indicated joint / DL TCI state and the second indicated joint / DL TCI state, respectively. In this case, sending the 450 DCI may be skipped. The first TCI state set may include a subset of activated joint / DL TCI states from the joint / DL TCI state list (e.g., activated by MAC-CE), or one or more indicated joint / DL TCI states from the activated joint / DL TCI states (e.g., activated by DCI). The first control signal may include MAC-CE or DCI, where MAC-CE activates the subset of joint / DL TCI states from the joint / DL TCI state list, and DCI indicates one or more joint / DL TCI states from the activated joint / DL TCI states.

[0197] Network entity 104 sends a second control signal to UE 102 for PDSCH transmission of the 960-scheduled M-TRP scheme. This second control signal is associated with a second TCI state set. For example, refer to... Figure 4 Network entity 104 sends a 460 PDCCH transmission in a CORESET that schedules PDSCH transmissions. One or more TCI states used to receive PDCCH transmissions (e.g., DCI) in a scheduled CORESET may be referred to as a second TCI state set. The second TCI state set is used to receive a scheduled CORESET (e.g., PDCCH transmissions or DCI).

[0198] Network entity 104, based on the configuration of the second control signal, sends a 980 PDSCH transmission to UE 102 using at least one TCI state from the first TCI state set or using the second TCI state set. For example, refer to... Figure 4 Network entity 104 sends 480 PDSCH transmissions scheduled by PDCCH in CORESET based on the configuration of scheduling PDCCH transmissions.

[0199] Figure 10A flowchart 1000 illustrates a method for UE-initiated beam selection wireless communication at a UE according to an embodiment. (Reference) Figures 1 to 3B and Figure 6 This method can be performed by UE 102. In an embodiment, UE 102 can send a UE capability report (1010) to network entity 104, indicating that UE 102 supports UE capabilities based on the UE-initiated beam selection M-TRP scheme. For example, refer to... Figure 6 UE 102 can send a UE capability report (610) to the network entity, which indicates the UE capabilities used to support the M-TRP scheme based on UE-initiated beam selection.

[0200] UE 102 receives a first control signal 1020 from network entity 104. This first control signal configures UE-initiated beam selection for the Multiple Transmitter-Receiver Point (M-TRP) scheme. For example, refer to... Figure 6 UE 102 receives from the network entity 620 the first control signal (e.g., including RRC signal for RRC configuration) for beam selection initiated by the UE.

[0201] UE 102 can receive a second control signal 1030 from a network entity, which indicates that at least one of the channels or reference signals uses one or more beams selected by the UE. For example, reference... Figure 6 UE 102 can then receive a second control signal 630 for configuring / indicating whether the channel or RS applies / follows the UE-selected (e.g., UE-recommended, UE-preferred, or qualified) beam in a beam selection / switching initiated by the UE.

[0202] UE 102 sends a 1040 report to network entity (104), which indicates one or more beams selected by the UE based on a first control signal. For example, refer to Figure 6 UE 102 sends a 640 report to the network entity, which indicates one or more UE-selected beams (e.g., UE-recommended, UE-preferred, or qualified beams) based on a first control signal. NW entity 104 receives the 640 report from the UE, which indicates one or more UE-selected beams based on the first control signal.

[0203] UE 102 can receive a 1050 acknowledgment message from network entity 104 to acknowledge one or more beams selected by the UE. For example, refer to Figure 6 UE 102 can receive a 650 confirmation message to confirm or approve the application of one or more UE-selected beams (e.g., UE-suggested, UE-preferred, or qualified beams) indicated by the UE.

[0204] UE 102 communicates with network entity 104 1080 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme. For example, reference... Figure 6 UE 102 communicates with NW entity 104 680 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme. Figure 10 The method for the UE side of the wireless communication link is described, and Figure 11 The network-side methods for wireless communication links are described.

[0205] Figure 11 This is a flowchart 1100 of a method for UE-initiated beam selection wireless communication at a network according to an embodiment. (See reference...) Figures 1 to 3B and Figure 6 This method can be performed by one or more network entities 104, which may correspond to a base station or a base station element, such as RU 106, DU 108, and / or CU 110. In an embodiment, network entity 104 may receive a UE capability report from UE 102, which indicates that UE 102 supports UE capabilities based on the UE-initiated beam selection M-TRP scheme. For example, refer to... Figure 6 UE 102 can send a UE capability report (610) to the network entity, which indicates the UE capabilities used to support the M-TRP scheme based on UE-initiated beam selection.

[0206] Network entity 104 sends a first control signal 1120 to UE 102. This first control signal configures UE-initiated beam selection for the Multiple Transmitter-Receiver Point (M-TRP) scheme. For example, refer to... Figure 6 NW entity 104 sends a first control signal (e.g., including an RRC signal for RRC configuration) to the UE to configure the beam selection initiated by the UE.

[0207] Network entity 104 may send a second control signal 1130 to UE 102, the second control signal indicating that at least one of the channels or reference signals uses one or more beams selected by the UE. For example, reference... Figure 6 The NW entity 104 can then send a second control signal 630 to configure / indicate whether the channel or RS applies / follows the UE-selected (e.g., UE-recommended, UE-preferred, or qualified) beam in a beam selection / switching initiated by the UE.

[0208] Network entity 104 receives a report 1140 from UE 102, which indicates one or more beams selected by the UE based on a first control signal. For example, refer to... Figure 6NW entity 104 receives a 640 report from the UE, which indicates one or more beams selected by the UE based on a first control signal.

[0209] Network entity 104 can send an 1150 acknowledgment message to UE 102 to acknowledge one or more beams selected by the UE. For example, refer to Figure 6 NW entity 104 can provide feedback or send a 650 confirmation message to confirm or approve the application of one or more UE-selected beams (e.g., UE-suggested, UE-preferred, or qualified beams) as indicated by the UE.

[0210] Network entity 104 communicates with UE 102 1180 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme. For example, reference... Figure 6 NW entity 104 communicates with UE 102 using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme 680.

[0211] Figure 12 A flowchart 1200 illustrates a method for wireless communication at the UE for interpreting PDCCH commands according to an embodiment. (Reference) Figures 1 to 3B and Figure 7 This method can be executed by UE 102. In an embodiment, UE 102 receives a control signal 1220 from network entity 104, which includes a first field or a second field different from the first field in a PDCCH command. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or candidate cell. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or candidate cell. The second field indicates that the PDCCH command is for triggering an LTM procedure for the serving cell or candidate cell. For example, refer to... Figure 7 UE 102 receives a 720 control signal from network entity 104. This control signal includes a first field or a second field different from the first field in the PDCCH command. The first field indicates that the PDCCH command is used to trigger CFRA for the serving cell or candidate cell. The second field indicates that the PDCCH command is used to trigger LTM procedure for the serving cell or candidate cell.

[0212] UE 102 communicates with network entity 104 1280 based on at least one of the first or second fields of the control signal. For example, refer to Figure 7 UE 102 communicates with network entity 104 780 based on at least one of the first field (e.g., the second DCI field) or the second field (e.g., the third DCI field) of the control signal. Figure 12The method for the UE side of the wireless communication link is described, and Figure 13 The network-side methods for wireless communication links are described.

[0213] Figure 13 This is a flowchart 1300 of a method for wireless communication at a network for instructing PDCCH commands according to an embodiment. (See also...) Figures 1 to 3B and Figure 7 This method can be executed by one or more network entities 104, which may correspond to a base station or a base station element, such as RU 106, DU 108, and / or CU 110. In an embodiment, network entity 104 sends a 1320 control signal to UE 102, which includes a first field or a second field different from the first field in a PDCCH command. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or candidate cell. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or candidate cell. The second field indicates that the PDCCH command is for triggering an LTM procedure for the serving cell or candidate cell. For example, refer to... Figure 7 Network entity 104 sends a 720 control signal to UE 102. This control signal includes a first field or a second field different from the first field in the PDCCH command. The first field indicates that the PDCCH command is used to trigger CFRA for the serving cell or candidate cell. The second field indicates that the PDCCH command is used to trigger LTM procedure for the serving cell or candidate cell.

[0214] Network entity 104 communicates with UE 102 1380 based on at least one of the first or second fields of the control signal. For example, refer to Figure 7 Network entity 104 communicates with UE 102 780 based on at least one of the first field (e.g., the second DCI field) or the second field (e.g., the third DCI field) of the control signal. Figure 14 As described herein, UE equipment 1402 can execute the methods of flowcharts 800, 1000, and 1200. For example... Figure 15 As described in the diagram, one or more network entities 104 can execute the methods of flowcharts 900, 1100, and 1300.

[0215] Figure 14Illustration 1400 illustrates an example of a hardware implementation of UE device 1402. UE device 1402 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1402 may include an application processor 1406, which may have on-chip memory 1406'. In the example, application processor 1406 may be coupled to a secure digital (SD) card 1408 and / or a display 1410. Application processor 1406 may also be coupled to a sensor module 1412, a power supply 1414, an additional memory module 1416, a camera 1418, and / or other related components.

[0216] The UE equipment 1402 may further include a wireless baseband processor 1426, which may be referred to as a modem. The wireless baseband processor 1426 may have on-chip memory 1426'. Together with and similarly to the application processor 1406, the wireless baseband processor 1426 may also be coupled to a sensor module 1412, a power supply 1414, an additional memory module 1416, a camera 1418, and / or other related components. The wireless baseband processor 1426 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1420 and / or one or more transceivers 1430 (e.g., wireless RF transceivers).

[0217] Within one or more transceivers 1430, the UE equipment 1402 may include a Bluetooth module 1432, a WLAN module 1434, an SPS module 1436 (e.g., a GNSS module), and / or a cellular module 1438. The Bluetooth module 1432, WLAN module 1434, SPS module 1436, and cellular module 1438 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1432, WLAN module 1434, SPS module 1436, and cellular module 1438 may each include a dedicated antenna and / or utilize antenna 1440 for communication with one or more other nodes. For example, UE equipment 1402 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1430 and antenna 1440, where network entity 104 may correspond to a base station or a unit of a base station, such as RU 106, DU 108 or CU 110.

[0218] The wireless baseband processor 1426 and application processor 1406 may each include computer-readable media / memory 1426' and 1406', respectively. An additional memory module 1416 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1426', 1406', and 1416 may be non-transitory. The wireless baseband processor 1426 and application processor 1406 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1426', 1406', and 1416. When executed by the wireless baseband processor 1426 / application processor 1406, this software causes the wireless baseband processor 1426 / application processor 1406 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1426 / application processor 1406 during software execution. The wireless baseband processor 1426 / application processor 1406 may be a component of UE 102. UE equipment 1402 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1426 and / or the application processor 1406. In other examples, UE equipment 1402 may be the entire UE 102 and may include additional modules for equipment 1402.

[0219] like Figure 1 The discussion in the article and about Figure 8 The implemented M-TRP component 140 is configured to receive a first control signal from a network entity indicating a first TCI state set. The M-TRP component 140 is also configured to receive a second control signal from the network entity, which schedules PDSCH transmissions for the M-TRP scheme. The second control signal is associated with a second TCI state set. The M-TRP component 140 is configured to receive PDSCH transmissions from the network entity based on the configuration of the second control signal, using at least one TCI state from the first TCI state set or using the second TCI state set.

[0220] like Figure 1 The discussion in the article and about Figure 10 Implemented in this manner, the M-TRP component 140 is configured to receive a first control signal from a network entity, the first control signal configuring UE-initiated beam selection for the M-TRP scheme. The M-TRP component 140 is configured to send a report to the network entity indicating one or more UE-selected beams based on a first control channel. The M-TRP component 140 is configured to communicate with the network entity using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0221] like Figure 1 The discussion in the article and about Figure 12The implemented M-TRP component 140 is configured to receive control signals from a network entity, which include a first field or a second field different from the first field in a PDCCH command. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or a candidate cell. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or a candidate cell. The second field indicates that the PDCCH command is for triggering an LTM procedure for the serving cell or a candidate cell. The M-TRP component 140 is configured to communicate with the network entity based on at least one of the first or second fields of the control signal. The M-TRP component 140 may be located within an application processor 1406 (e.g., at 140a), a radio baseband processor 1426 (e.g., at 140b), or both application processor 1406 and radio baseband processor 1426. M-TRP components 140a to 140b may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for use by one or more processors, or a combination thereof.

[0222] Figure 15 Illustration 1500 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functions. The one or more network entities 104 may include at least one of RU 106, DU 108, or CU 110, or may correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1546, which may have on-chip memory 1546'. In some aspects, CU 110 may further include an additional memory module 1556 and / or a communication interface 1548, both of which may be coupled to the CU processor 1546. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1548 of CU 110 and the communication interface 1528 of DU 108).

[0223] DU 108 may include a DU processor 1526, which may have on-chip memory 1526'. In some aspects, DU 108 may further include an additional memory module 1536 and / or a communication interface 1528, both of which may be coupled to the DU processor 1526. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1528 and RU 106's communication interface 1508.

[0224] RU 106 may include an RU processor 1506, which may have on-chip memory 1506'. In some aspects, RU 106 may further include an additional memory module 1516, a communication interface 1508, and one or more transceivers 1530, all of which may be coupled to the RU processor 1506. RU 106 may further include an antenna 1540, which may be coupled to one or more transceivers 1530, enabling RU 106 to communicate with UE 102 via the antenna 1540 through one or more transceivers 1530.

[0225] On-chip memories 1506', 1526', 1546' and additional memory modules 1516, 1536, 1556 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1506, 1526, 1546 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1506, 1526, 1546, the software causes the processor 1506, 1526, 1546 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by processors 1506, 1526, 1546 during software execution. In the example, configuration component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0226] like Figure 1 The discussion in the article and about Figure 9 Implemented in this way, configuration component 150 is configured to send a first control signal to the UE indicating a first Transport Configuration Indicator (TCI) state set. Configuration component 150 is also configured to send a second control signal to the UE, which schedules PDSCH transmission for the M-TRP scheme. The second control signal is associated with a second TCI state set. Configuration component 150 is configured to send PDSCH transmission to UE 102 based on the configuration of the second control signal, using at least one TCI state from the first TCI state set or using the second TCI state set.

[0227] like Figure 1 The discussion in the article and about Figure 9The configuration component 150 is configured to send a first control signal to the UE, which configures UE-initiated beam selection for a Multiple Transmit / Receive Point (M-TRP) scheme. The configuration component 150 is configured to receive a report from the UE indicating one or more UE-selected beams based on a first control channel. The configuration component 150 is configured to communicate with the UE using one or more UE-selected beams for at least one of the channels or reference signals of the M-TRP scheme.

[0228] like Figure 1 The discussion in the article and about Figure 9 The configuration component 150 is configured to send a control signal to the UE, which includes a first field or a second field different from the first field in a PDCCH command. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or a candidate cell. In some examples, the first field indicates that the PDCCH command is for triggering a CFRA for the serving cell or a candidate cell. The second field indicates that the PDCCH command is for triggering an LTM procedure for the serving cell or a candidate cell. The configuration component 150 is configured to communicate with the UE based on at least one of the first or second fields of the control signal. The configuration component 150 may be located within one or more processors of one or more network entities 104, such as RU processor 1506 (e.g., at 150a), DU processor 1526 (e.g., at 150b), and / or CU processor 1546 (e.g., at 150c). Configuration components 150a-150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1506, 1526, 1546 configured to execute the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1506, 1526, 1546, or a combination thereof.

[0229] It should be noted that throughout this disclosure, a UE may have one or more of the following attributes or behaviors. The following attributes or behaviors of the UE may also imply associated attributes or behaviors of the NW entity.

[0230] The UE can be configured and / or served by the NW entity in the serving cell.

[0231] The UE can (be configured) communicate with NW entities in the serving cell.

[0232] The UE can be configured by the NW entity to include one or more serving cells that may include the serving cell.

[0233] The UE can be activated or instructed by the NW entity to activate one or more serving cells that may include the serving cell.

[0234] The UE can configure and / or indicate one or more BWPs by the NW entity. The UE can indicate and / or configure (in the serving cell) BWPs by the NW entity.

[0235] ○ In some cases, the BWP can be activated as the active BWP.

[0236] In some cases, this BWP can be referred to as an active BWP.

[0237] ○ In some cases, the BWP can be an active DL BWP.

[0238] ○ In some cases, the BWP can be an active UL BWP.

[0239] ○ In some cases, the BWP can be the initial BWP.

[0240] In some cases, this BWP can be the default BWP.

[0241] In some cases, the BWP can be a dormant BWP.

[0242] The UE can be in one of the following states: RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE.

[0243] It should be noted that throughout this disclosure, when a process or description relates to a serving cell, it may mean that the process or description relates to an activity (DL / UL) BWP in the serving cell.

[0244] It should be noted that throughout this disclosure, adjacent communities may be referred to as or replaced by one or more of the following: Non-service cell Cells with a PCI different from the serving cell, TRP associated with a PCI that is different from the PCI of the serving cell.

[0245] It should be noted that throughout this disclosure, if an NW entity configures an inter-cell M-TRP 2TA for a UE in a serving cell, it means that the NW entity has configured two TAGs to associate with that serving cell: one TAG is associated with the serving cell PCI, and the other TAG is associated with an additional PCI in the serving cell. The additional PCI may be associated with or configured in the active TCI state of the serving cell.

[0246] It should be noted that throughout this disclosure, if the NW entity configures an intra-cell M-TRP 2TA for the UE, it means that the NW entity has configured two TAGs to be associated with the serving cell, where both TAGs are associated with the serving cell and / or no additional PCI is configured.

[0247] It should be noted that throughout this disclosure, a scheduling CORESET may mean or be referred to as a CORESET with a scheduling PDCCH. A scheduling CORESET for a PDSCH may mean or be referred to as a CORESET with a PDCCH or a DCI with a scheduling PDSCH.

[0248] It should be noted that throughout this disclosure, the duration of TCI status or beam indication may refer to the actual time when TCI status or beam indication can be applied or become effective, which may be later than the time when TCI status or beam indication is received.

[0249] It should be noted that throughout this disclosure, the configuration or instruction of an NW entity to a UE to operate in S-TRP mode in a serving cell or BWP, or the operation of a serving cell or BWP in S-TRP mode, may mean or be referred to as one of the following: - The NW entity did not configure or indicate a TRP identifier or TRP-related index to any channel or RS in the serving cell or BWP, and / or - The NW entity configures or indicates (only) a TRP identifier or TRP-related index to any channel or RS in the serving cell or BWP, and / or - When a UE or NW entity sends / receives a transmission, (only) one TRP identifier or TRP-related index is configured or indicates or relates to the transmission or applies to the beam / TCI status of the transmission.

[0250] It should be noted that throughout this disclosure, the configuration or instruction of an NW entity to a UE to operate in M-TRP mode in a serving cell or BWP, or the operation of a serving cell or BWP in M-TRP mode, may mean or be referred to as one of the following: - The NW entity configures or indicates more than one TRP identifier or TRP-related index to at least one channel or RS in the serving cell or BWP, and / or - The NW entity configures or indicates a TRP identifier or TRP-related index to a channel or RS in the serving cell or BWP; and the UE derives or determines another TRP identifier or TRP-related index applied to at least one channel or RS in the serving cell or BWP or associated with at least one channel or RS in the serving cell or BWP, and / or - When a UE or NW entity transmits / receives a transmission, more than one TRP identifier or TRP-related index is configured, indicates, relates to, or applies to the beam / TCI of the transmission, and / or - NW entity configures higher-level parameters to UE PDCCH-Config This higher-level parameter includes the serving cell or BWP. ControlResourceSet In coresetPoolIndex Two distinct values, and / or - The UE receives a MAC-CE (e.g., PDSCH TCI activation MAC-CE) from the serving cell or BWP from the NW entity, which indicates that at least one TCI code point is mapped to two TCI states.

[0251] It should be noted that throughout this disclosure, the configuration or instruction of an NW entity to a UE to operate in (M-TRP) M-DCI mode in a serving cell or BWP, or the operation of a serving cell or BWP in (M-TRP) M-DCI mode, may mean or be referred to as one of the following: - The NW entity configures or indicates more than one TRP identifier or TRP-related index to at least one channel or RS in the serving cell or BWP, and / or - The NW entity configures or indicates a TRP identifier or TRP-related index to a channel or RS in the serving cell or BWP; and the UE derives or determines another TRP identifier or TRP-related index applied to at least one channel or RS in the serving cell or BWP or associated with at least one channel or RS in the serving cell or BWP, and / or - NW entity configures higher-level parameters to UE PDCCH-Config This higher-level parameter includes the serving cell or BWP. ControlResourceSet In coresetPoolIndex Two different values.

[0252] It should be noted that throughout this disclosure, the configuration or instruction of an NW entity to a UE to operate in (M-TRP) S-DCI mode in a serving cell or BWP, or the operation of a serving cell or BWP in (M-TRP) S-DCI mode, may mean or be referred to as one of the following: - When a UE or NW entity transmits / receives a transmission, more than one TRP identifier or TRP-related index is configured, indicates, relates to, or applies to the beam / TCI of the transmission, and / or - The UE receives a MAC-CE (e.g., PDSCH TCI activation MAC-CE) from the serving cell or BWP from the NW entity. This MAC-CE indicates that at least one TCI code point is mapped to two TCI states, each of which is associated with a different TRP or a different TRP identifier (value).

[0253] For example, at least one TCI code point is mapped to two joint TCI states, each of which is associated with a different TRP or a different TRP identifier (value). As another example, at least one TCI code point is mapped to two DL TCI states or two UL TCI states, each of which is associated with a different TRP or a different TRP identifier (value). Yet another example, at least one TCI code point is mapped to a DL TCI state and a pair of DL TCI and UL TCI states, wherein the DL TCI state and the pair of DL TCI and UL TCI states are associated with a different TRP or a different TRP identifier (value).

[0254] It should be noted that throughout this disclosure, the TRP identifier can refer to or be referred to as a (candidate) value of the TRP identifier. The first TRP identifier can be a first candidate value or a first TRP identifier value. The second TRP identifier can be a second candidate value or a second TRP identifier value.

[0255] It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X or Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and / or Y". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "B only". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "A+B" or "B+A".

[0256] It should be noted that some or all of the embodiments described above or below may be combined or formed into new or another embodiment.

[0257] It should be noted that the foregoing or following embodiments can be used to solve at least (but not limited to) the problems or scenarios mentioned in this disclosure.

[0258] The following additional considerations apply to the foregoing and the following discussion.

[0259] It should be noted that any two or more of the foregoing or following paragraphs, (sub)bullets, points, actions or claims described in each method / example / implementation may be logically, reasonably and appropriately combined to form a particular method.

[0260] It should be noted that any sentence, paragraph, (sub)bulb, point, action, or claim described in the foregoing or following embodiments / implementations / concepts can be implemented independently and separately to form a particular method. Dependencies such as "based on," "more specifically," and "wherein" in the embodiments / implementations / concepts mentioned in this disclosure are merely one possible embodiment and do not limit a particular method.

[0261] It should be noted that some or all of the following terms and assumptions may be used in the following text.

[0262] BS: A network central unit or network node in an NR used to control one or more TRPs associated with one or more cells. Communication between the BS and the TRP is via fronthaul. A BS can be referred to as a Central Unit (CU), eNB, gNB, or NodeB.

[0263] TRP: Transmit and receive point provides network coverage and communicates directly with the UE. TRP can be referred to as a distributed cell (DU) or network node.

[0264] Cell: A cell consists of one or more associated TRPs; that is, the coverage of a cell is composed of the coverage of all associated TRPs. A cell is controlled by a BS or NW entity. A cell can be referred to as a TRP group (TRPG).

[0265] Serving beam: The UE's serving beam is a beam generated by a network node (e.g., TRP) and configured to communicate with the UE (e.g., for sending and / or receiving).

[0266] Candidate beam: The candidate beam of the UE is a candidate of the serving beam. The serving beam may or may not be a candidate beam.

[0267] The user device in which the technologies of this disclosure are implemented (e.g., UE 102) can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Further, in some cases, the user device can be embedded in an electronic system such as a vehicle's main unit or an advanced driver assistance system (ADAS). Even further, the user device can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0268] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain manner. A hardware module may include a dedicated circuit system or logic that is persistently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or circuit systems (e.g., as contained within a general-purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. The decision to implement a hardware module with a dedicated and permanently configured circuit system or with a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0269] When implemented in software, the technology can be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0270] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is illustrative of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements of the diagram. The appended method claims present the elements of each box in the exemplary order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0271] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide 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 to avoid obscuring such concepts.

[0272] Various apparatuses and methods are presented with reference to aspects of wireless communication systems (such as telecommunications systems). These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can 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.

[0273] An element, or any part of an element, 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0274] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage 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 instructions or data structures accessible by a computer. The storage medium can be any available medium accessible to a computer.

[0275] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can 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 technologies described herein.

[0276] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous 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 can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0277] 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 aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0278] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0279] Unless otherwise expressly stated, the term "some" means 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 having a number of one or more elements. Terms or articles such as "a," "an," and / or "the" may refer to one of the items, features, elements, etc., following that term or article, or may refer to more than one of the items, features, elements, etc., following that term or article. For example, the expression "a small component" does not exclude references to multiple components, because "multiple components" necessarily includes "a small component." Therefore, the expression "a small component" can be interpreted as "at least one small component," or similarly, as "one or more components."

[0280] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase that follows each ordinal term.

[0281] As used in the specification and drawings, reference numerals are sometimes cross-referenced across drawings to indicate the same or similar features. Features that are identical in multiple drawings may be labeled with the same reference numerals in multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Therefore, the same numerals may indicate the same action.

[0282] Structural and functional equivalents of elements of all aspects described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A”.

[0283] The following examples are illustrative only and can be combined with other examples or doctrines described herein without limitation.

[0284] Example 1 is a method for wireless communication at a UE, comprising: receiving from a network entity a first control signal indicating a first Transmission Configuration Indicator (TCI) state set; receiving from the network entity a second control signal associated with a Physical Downlink Shared Channel (PDSCH) transmission for scheduling a Multiple Transmitter Receiver (M-TRP) scheme, the second control signal being associated with a second TCI state set; and receiving the PDSCH transmission from the network entity using at least one TCI state from the first TCI state set or using the second TCI state set, based on the configuration of the second control signal.

[0285] Example 2 can be combined with Example 1 and further includes: sending a UE capability report to the network entity indicating that the UE (102) supports the UE capability of the M-TRP scheme.

[0286] Example 3 may be combined with any of Examples 1 to 2 and further includes: the second control signal is downlink control information (DCI) on the physical downlink control channel (PDCCH) in the control resource set (CORESET), and the method further includes: receiving from the network entity (104) at least one of a TCI selection parameter or a TCI selection field indicating at least one TCI state in the first TCI state set.

[0287] Example 4 can be combined with any of Examples 1 to 3 and further includes: receiving the PDSCH transmission from the network entity includes: based on the configuration indication of the second control signal that the second TCI state set is the same as the first TCI state set, using at least one TCI state in the first TCI state set to receive the PDSCH transmission, wherein the at least one TCI state is further based on the DCI format.

[0288] Example 5 can be combined with any of Examples 1 to 3 and further includes: receiving the PDSCH transmission from the network entity includes: receiving the PDSCH transmission using at least one TCI state based on a TCI selection field in the first TCI state set, based on the second DCI format being a second DCI format; or receiving the PDSCH transmission (480, 580-2c, 580-3c) using at least one TCI state based on a TCI selection parameter in the first TCI state set or using the second TCI state set, based on the configuration indication of the second control signal indicating whether the second TCI state set is the same as or different from the first TCI state set, based on the configuration indication of the first TCI format being a first DCI format.

[0289] Example 6 can be combined with any of Examples 1 to 3 and further includes: receiving the PDSCH transmission from the network entity includes: based on the configuration indication of the second control signal that the second TCI state set is different from the first TCI state set, using at least one TCI state from the first TCI state set to receive the PDSCH transmission. The at least one TCI state is based on a TCI selection parameter or TCI selection field associated with the DCI format.

[0290] Example 7 can be combined with any of Examples 1 to 3 and further includes: receiving the PDSCH transmission further based on UE capabilities.

[0291] Example 8 is a method for wireless communication at a network entity, comprising: sending a first control signal to a UE indicating a first Transmission Configuration Indicator (TCI) state set; sending a second control signal to the UE to schedule Physical Downlink Shared Channel (PDSCH) transmission of a Multiple Transmitter Receiver (M-TRP) scheme, the second control signal being associated with a second TCI state set; and sending the PDSCH transmission to the UE using at least one TCI state from the first TCI state set or using the second TCI state set, based on the configuration of the second control signal.

[0292] Example 9 can be combined with Example 8 and further includes: receiving from the UE a UE capability report indicating that the UE supports the UE capability of the M-TRP scheme.

[0293] Example 10 may be combined with any of Examples 8 to 9 and further includes: sending the PDSCH transmission to the UE includes: based on the configuration indication of the second control signal that the second TCI state set is the same as the first TCI state set, sending the PDSCH transmission using at least one TCI state in the first TCI state set, wherein the at least one TCI state is further based on a DCI format.

[0294] Example 11 can be combined with any of Examples 8 to 9 and further includes: sending the PDSCH transmission to the UE includes: sending the PDSCH transmission using at least one TCI state based on a TCI selection field in the first TCI state set, based on the second DCI format being a second DCI format; or sending the PDSCH transmission using at least one TCI state based on a TCI selection parameter in the first TCI state set or using the second TCI state set, based on the configuration indication of the second control signal that the second TCI state set is the same as or different from the first TCI state set, based on the first DCI format being a first DCI format.

[0295] Example 12 can be combined with any of Examples 8 to 9 and further includes: sending the PDSCH transmission to the UE includes: based on the configuration indication of the second control signal that the second TCI state set is different from the first TCI state set, using at least one TCI state from the first TCI state set to send the PDSCH transmission. The at least one TCI state is based on a TCI selection parameter or TCI selection field associated with the DCI format.

[0296] Example 13 is a method for wireless communication at a UE, comprising: receiving (620) a first control signal from a network entity (104) configuring UE-initiated beam selection for a Multiple Transmit Receive Point (M-TRP) scheme; sending (640) to the network entity (104) a report indicating one or more UE-selected beams based on the first control signal; and communicating (680) with the network entity (104) using the one or more UE-selected beams for at least one of a channel or reference signal of the M-TRP scheme.

[0297] Example 14 can be combined with Example 13 and includes: sending (610) a UE capability report to the network entity (104) indicating that the UE (102) supports the UE capability of the M-TRP scheme based on the beam selection initiated by the UE; and receiving (650) an acknowledgment message from the network entity (104) to acknowledge the beam selected by the one or more UEs.

[0298] Example 15 may be combined with any of Examples 13 to 14 and further includes: receiving (630) a second control signal from the network entity, the second control signal instructing at least one of the channel or the reference signal to use the beam selected by the one or more UEs.

[0299] Example 16 may be combined with any of Examples 13 to 14 and further includes: the report further instructing at least one of the channel or the reference signal to use the beam selected by the one or more UEs.

[0300] Example 17 is a method for wireless communication at a network entity, comprising: sending (620) a first control signal to a user equipment (UE) (102) configuring UE-initiated beam selection for a multiple transmit-receive point (M-TRP) scheme; receiving (640) from the UE (102) a report indicating one or more UE-selected beams based on the first control signal; and communicating (680) with the UE (102) using the one or more UE-selected beams for at least one of a channel or reference signal of the M-TRP scheme.

[0301] Example 18 can be combined with Example 17 and includes: receiving (610) a UE capability report from the UE (102) indicating that the UE (102) supports the UE capability of the M-TRP scheme based on the beam selection initiated by the UE; and sending (650) an acknowledgment message to the UE (102) to acknowledge the beam selected by the one or more UEs.

[0302] Example 19 may be combined with any of Examples 17 to 18 and further includes: sending (630) a second control signal to the UE (102), the second control signal instructing at least one of the channel or the reference signal to use a beam selected by the one or more UEs.

[0303] Example 20 may be combined with any of Examples 17 to 18 and further includes: the report further instructing at least one of the channel or the reference signal to use the beam selected by the one or more UEs.

[0304] Example 21 is a method of wireless communication at a UE, comprising: receiving a control signal from a network entity (104), the control signal including a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command, the first field indicating that the PDCCH command is for triggering Contention-Free Random Access (CFRA) for a serving cell or a candidate cell, and the second field indicating that the PDCCH command is for triggering a Low-Layer Triggered Mobility (LTM) procedure for the serving cell or the candidate cell; and communicating with the network entity (104) based on at least one of the first field or the second field of the control signal.

[0305] Example 22 can be combined with Example 21 and includes: the first field is a Physical Random Access Channel (PRACH) configuration field, and the second field is a cell indicator field.

[0306] Example 23 may be combined with any of Examples 21 to 22 and further includes: communicating with the network entity (104) includes: communicating with the network entity (104) based on the first field when the second field indicates the serving cell.

[0307] Example 24 may be combined with any of Examples 21 to 22 and further includes: communicating with the network entity (104) includes: communicating with the network entity (104) based on the second field when the first field indicates that the PDCCH command is associated with the serving cell.

[0308] Example 25 may be combined with any of Examples 21 to 22 and further includes: the control signal further includes a third field indicating whether at least one of the first field or the second field is applied in the PDCCH command.

[0309] Example 26 is a method for wireless communication at a network entity, comprising: sending a control signal to a user equipment (UE) (102), the control signal including a first field or a second field different from the first field in a Physical Downlink Control Channel (PDCCH) command, the first field indicating that the PDCCH command is for triggering contention-free random access (CFRA) for a serving cell or a candidate cell, and the second field indicating that the PDCCH command is for triggering a lower-layer triggered mobility (LTM) procedure for the serving cell or the candidate cell; and communicating with the UE (102) based on at least one of the first field or the second field of the control signal.

[0310] Example 27 can be combined with Example 26 and includes: the first field is a Physical Random Access Channel (PRACH) configuration field, and wherein the second field is a cell indicator field.

[0311] Example 28 may be combined with any of Examples 26 to 27 and further includes: the communication with the UE (102) includes: communicating with the UE (102) based on the first field when the second field indicates the serving cell.

[0312] Example 29 may be combined with any of Examples 26 to 27 and further includes: the communication with the UE (102) includes: communicating with the UE (102) based on the second field when the first field indicates that the PDCCH command is associated with the serving cell.

[0313] Example 30 may be combined with any of Examples 26 to 27 and further includes: the control signal further includes a third field indicating whether at least one of the first field or the second field in the PDCCH command is applied.

[0314] Example 31 is an apparatus for wireless communication, the apparatus including a transceiver, a memory, and a processor coupled to the memory and the transceiver. The apparatus is configured to implement the method as described in any one of claims 1 to 30.

[0315] Example 32 is an apparatus for wireless communication, the apparatus including components for implementing the method as described in any one of Examples 1 to 30.

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

Claims

1. A method for wireless communication at a user equipment (UE) (102), comprising: Receive (440, 450) a first control signal indicating a first Transmission Configuration Indicator (TCI) state set from network entity (104); Receive (460) a second control signal from the network entity (104) for scheduling the Physical Downlink Shared Channel (PDSCH) transmission of the Multiple Transmitter Receiver (M-TRP) scheme, the second control signal being associated with a second TCI state set; and Based on the configuration of the second control signal, the PDSCH transmission is received (480) from the network entity (104) using at least one TCI state from the first TCI state set or using the second TCI state set.

2. The method of claim 1, further comprising: Send (410) a UE capability report to the network entity (104) indicating that the UE (102) supports the UE capability of the M-TRP scheme.

3. The method of any one of claims 1 to 2, wherein the second control signal is downlink control information (DCI) on the physical downlink control channel (PDCCH) in the control resource set (CORESET), the method further comprising: Receive (430, 450) from the network entity (104) at least one of the TCI selection parameters or TCI selection fields indicating at least one TCI state in the first TCI state set.

4. The method of any one of claims 1 to 3, wherein receiving (480) the PDSCH transmission from the network entity (104) comprises: The configuration based on the second control signal indicates that the second TCI state set is the same as the first TCI state set, and that at least one TCI state from the first TCI state set is used to receive (480, 580-1a, 580-2a) the PDSCH transmission, wherein the at least one TCI state is further based on the DCI format.

5. The method of any one of claims 1 to 3, wherein receiving (480) the PDSCH transmission from the network entity (104) comprises: Based on the fact that the DCI format is the second DCI format, the PDSCH transmission (480, 580-1c) is received using the at least one TCI state based on the TCI selection field in the first TCI state set. or Based on the DCI format being the first DCI format, and based on the configuration indication of the second control signal, the second TCI state set is the same as or different from the first TCI state set. The PDSCH transmission is received (480, 580-2c, 580-3c) using at least one TCI state based on the TCI selection parameter in the first TCI state set or using the second TCI state set.

6. The method of any one of claims 1 to 3, wherein receiving (480) the PDSCH transmission from the network entity (104) comprises: The configuration based on the second control signal indicates that the second TCI state set is different from the first TCI state set, and that at least one TCI state from the first TCI state set is used to receive (480, 580-1b, 580-2b) the PDSCH transmission, wherein the at least one TCI state is based on a TCI selection parameter or TCI selection field associated with the DCI format.

7. The method of any one of claims 1 to 3, wherein receiving (480) the PDSCH transmission is further based on UE capability.

8. A method for wireless communication at a network entity (104), comprising: Send a first control signal (440, 450) indicating the first Transmission Configuration Indicator (TCI) state set to the User Equipment (UE) (102); Sending (460) a second control signal to the UE (102) to schedule the Physical Downlink Shared Channel (PDSCH) transmission of the Multiple Transmitter Receiver (M-TRP) scheme, the second control signal being associated with a second TCI state set; and Based on the configuration of the second control signal, the PDSCH transmission is sent to the UE (102) (480) using at least one TCI state from the first TCI state set or using the second TCI state set.

9. The method of claim 8, further comprising: The UE (102) receives (410) a UE capability report indicating that the UE (102) supports the UE capability of the M-TRP scheme.

10. The method of any one of claims 8 to 9, wherein sending (480) the PDSCH transmission to the UE (102) comprises: The configuration based on the second control signal indicates that the second TCI state set is the same as the first TCI state set, and that at least one TCI state from the first TCI state set is used to send (480, 580-1a, 580-2a) the PDSCH transmission, wherein the at least one TCI state is further based on the DCI format.

11. The method of any one of claims 8 to 9, wherein sending (480) the PDSCH transmission to the UE (102) comprises: Based on the fact that the DCI format is the second DCI format, the PDSCH transmission (480, 580-1c) is sent using at least one TCI state based on the TCI selection field in the first TCI state set; or Based on the DCI format being the first DCI format, and based on the configuration indication of the second control signal, the second TCI state set is the same as or different from the first TCI state set. The PDSCH transmission is sent using at least one TCI state based on the TCI selection parameter in the first TCI state set or using the second TCI state set.

12. The method of any one of claims 8 to 9, wherein sending (480) the PDSCH transmission to the UE (102) comprises: The configuration based on the second control signal indicates that the second TCI state set is different from the first TCI state set, and that at least one TCI state from the first TCI state set is used to send (480, 580-1b, 580-2b) the PDSCH transmission, wherein the at least one TCI state is based on a TCI selection parameter or TCI selection field associated with the DCI format.

13. An apparatus for wireless communication, the apparatus comprising a transceiver, a memory, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 12.

Images