Methods and apparatus for performing downlink and uplink beam indication in a MIMO wireless communication system

Abstract

Example methods, systems, and techniques are disclosed for indicating a joint UL Transport Configuration Indicator (TCI) state for uplink (UL) transmissions (e.g., Physical Uplink Shared Channel (PUSCH)) and a joint DL TCI state for downlink (DL) transmissions (e.g., Physical Downlink Shared Channel (PDSCH)). An example method performed by a user equipment (UE) includes receiving (330) indications of multiple joint TCI states, multiple DL TCI states, or multiple UL TCI states (multiple joint / DL / UL TCI states) from a network entity; receiving (350) a control resource set (CORESET) including scheduling information; and communicating (370) with the network entity based on the scheduling information and the multiple joint / DL / UL TCI states without receiving an indication of a Sounding Reference Signal (SRS) resource set for uplink transmissions or without receiving a configuration for implementing Multiple Transmitter Receiver Point (M-TRP) operation.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to beam determination between a user equipment (UE) and a network used for multiple-input multiple-output (MIMO) communications. Background Technology

[0002] This background description is provided for the purpose of presenting the general context of this disclosure. The work of the currently attributed inventors (to the extent described in this background section) and aspects of the specification that would not have been considered prior art at the time of filing are neither expressly nor impliedly acknowledged as prior art to this disclosure.

[0003] In New Radio (NR), the Unified Transport Configuration Indicator (TCI) framework can be used as a simplified beam indication framework. Under this framework, User Equipment (UE) can be indicated by a Reference Signal (RS) and one or more Unified TCI states, which can be applied to most of the downlink (DL) and / or uplink (UL) channels. The Unified TCI framework can reduce signaling overhead and latency in beam indication. Existing Unified TCI frameworks only consider single transmit-receive-point (S-TRP) scenarios.

[0004] The unified TCI framework can be extended for multiple transmit-receive-point (M-TRP) scenarios, such as repetition schemes, single-frequency networks (SFN), or spatial division multiplexing (SDM) schemes. Furthermore, introducing UL multi-panel simultaneous transmission (STxMP) can lead to other M-TRP schemes, such as Physical Uplink Control Channel (PUCCH) SFN, Physical Uplink Shared Channel (PUSCH) SFN, and PUSCH SDM.

[0005] In the M-TRP scheme, the UE sends signals to or receives signals from multiple TRPs, thereby improving communication reliability because the likelihood of multiple TRPs being blocked or impeded simultaneously is lower compared to a single TRP. However, M-TRP transmission can introduce interference when signals from different TRPs (e.g., to / from) overlap in time and frequency. Therefore, techniques such as using a single-frequency network (SFN) or spatial division multiplexing (SDM) can be implemented to synchronize the transmissions. These techniques (along with other techniques that facilitate communication between the UE and multiple TRPs) can be collectively referred to as the M-TRP scheme.

[0006] A unified TCI state comprises multiple TCI states for use with multiple TRPs and allows the UE to select the optimal TRP for transmission or reception based on the TCI states of these multiple TRPs. The unified TCI state can include a joint TCI state, a downlink TCI state, and an uplink TCI state. The unified TCI state can have two modes: a joint TCI mode and a separate TCI mode. In joint TCI mode, the joint TCI state is used to perform uplink (UL) transmission and downlink (DL) reception; while in separate TCI mode, the DL TCI state is used to perform DL reception, and the UL TCI state is used to perform UL transmission.

[0007] Therefore, the joint / UL TCI state and the joint / DL TCI state are subsets of the unified TCI state. For example, the joint TCI state includes a combination of TCI states for all TRPs (and the corresponding DL or UL TCI states for the joint / DL TCI state and the joint / UL TCI state). During operation, the network entity indicates two (or more) TCI states (e.g., a first unified TCI state and a second unified TCI state) to the UE for executing the M-TRP scheme. The activated TCI state corresponds to the beam or beam configuration used for transmission and reception between the UE and the network entity.

[0008] In current practice, the SRS resource set indicator field exists in DCI format 0_1 / 0_2 only when two SRS resource sets are configured for codebook-based (CB) or non-codebook-based (NCB) uplink transmissions. If only one SRS resource set is configured for CB or NCB transmissions, the SRS resource set indicator field does not exist in DCI format 0_1 / 0_2. See For example, 3GPP technical specification TS 38.214 v.17.2.0, Rel.17, section 6.1.1.1. In this situation, the network entity may be unable to inform the UE (e.g., of multiple joint TCI states of a unified TCI state) which indicated joint / UL TCI state can be applied to send PUSCHs scheduled by DCI format 0_1 / 0_2.

[0009] Furthermore, for MIMO communication, beam indication for PDSCH can be inefficient, depending on whether the UE has been configured for M-TRP operation. Currently, for PDSCH (e.g., scheduled by DCI format 1_1 / 1_2), the two-bit TCI selection field in scheduling DCI format 1_1 / 1_2 can be configured to indicate which indicated joint / DL TCI state (first, second, or both) is applied to receive the scheduled PDSCH. When the UE operates with an M-TRP scheme / feature for PDSCH (e.g., SDM, FDM, TDM, SFN, or CJT), this is used to indicate both the first and second indicated joint / DL TCI states. However, such M-TRP schemes / features for PDSCH require both the first and second indicated joint / DL TCI states to be applied to the PDSCH. When the UE is not configured or implemented with any M-TRP scheme / feature for PDSCH, using a two-bit TCI selection field in signaling may be of little benefit. When it exists but is not utilized, the TCI selection field information may even increase the error rate of decoding PDCCHs including such DCI formats. Summary of the Invention

[0010] This disclosure provides methods, systems, and techniques for indicating a combined UL (combined / UL) Transport Configuration Indicator (TCI) state for uplink (UL) transmissions (e.g., Physical Uplink Shared Channel (PUSCH)) and a combined DL (combined / DL) TCI state for downlink (DL) transmissions (e.g., Physical Downlink Shared Channel (PDSCH)). For example, in multiple-input multiple-output (MIMO) operation, communication between a user equipment (UE) and a network entity can benefit from beam indication or determination using a unified TCI state, for example, to reduce signal overhead or latency. Various aspects of performing DL and UL beam indication or determination within a unified TCI framework are disclosed herein.

[0011] To further improve upon this, some configuration or indication information can be reduced. For example, this disclosure provides methods and techniques for performing beam indication for PUSCH (and thus preserving indication for the unified TCI state) when only one SRS resource set is configured for codebook (CB) or non-codebook (NCB). Additionally, this disclosure provides methods and techniques for using the TCI selection field for PDSCH when the network entity has not configured the UE to operate in a multiple transmit receiver point (M-TRP) scheme / feature.

[0012] According to a general aspect of this disclosure, a method for wireless communication by a user equipment (UE) includes: receiving indications of multiple Joint Transmission Configuration Indicator (TCI) states, multiple Downlink (DL) TCI states, or multiple Uplink (UL) TCI states (multiple joint / DL / UL TCI states) from a network entity. The UE receives a Control Resource Set (CORESET) including scheduling information. The UE then communicates with the network entity based on the scheduling information and the multiple joint / DL / UL TCI states, without receiving indications of a Sounding Reference Signal (SRS) resource set for uplink transmission, or without receiving configurations for implementing Multiple Transmitter Receiver Point (M-TRP) operation.

[0013] In various respects, the method further includes receiving from the network entity a configuration for multiple-input multiple-output (MIMO) operation, the configuration including a radio resource control (RRC) message configuring at least one of the following: (1) whether the uplink transmission is a codebook-based uplink transmission or a non-codebook-based uplink transmission, and the number of SRS resource sets used for the uplink transmission; or (2) a downlink control information (DCI) field in the DCI format relating to beam selection or TCI state selection for downlink reception.

[0014] In some cases, the configuration for MIMO operation further includes a configuration of the number of SRS resource sets associated with the DCI field in DCI format 0_1 ​​or DCI format 0_2. In some cases, the number of SRS resource sets is one, and the DCI field does not appear or further indicate which of the plurality of combined TCI states or plurality of UL TCI states (the plurality of combined / UL TCI states) will be applied to the uplink transmission to the network entity, and wherein the configuration for MIMO operation is for implementation or indication of Single Transmit Receive Point (S-TRP) operation for the timing of sending PUSCH transmissions.

[0015] In some cases, the method further includes determining a beam from the plurality of joint / UL TCI states for sending a PUSCH transmission timing to the network entity based on at least one of the following: (1) a predetermined joint / UL TCI state for uplink transmission; (2) a joint / UL TCI state configured by RRC parameters other than the received configuration; (3) a joint / UL TCI state indicated by the bit value of the SRS resource set indicator field in the received CORESET's DCI; (4) the number of joint / UL TCI states configured by the network entity for sending an SRS resource set associated with a codebook or non-codebook of DCI format 0_1 ​​or DCI format 0_2; (5) a joint TCI state corresponding to a downlink TCI state or QCL assumption for receiving a physical downlink control channel (PDCCH) timing; or (6) a joint TCI state determined based on the start control channel element (CCE) index of the PDCCH timing.

[0016] In various respects, the configuration for MIMO operation further includes a configuration of a TCI selection field associated with TCI selection in DCI format 1_1 or DCI format 1_2 for applying the TCI selection field in the DCI of the received CORESET at the timing of receiving the Physical Downlink Shared Channel (PDSCH).

[0017] In some cases, the configuration for MIMO operation includes Radio Resource Control (RRC) parameters that indicate whether the UE is configured or implemented for the M-TRP operation.

[0018] In some cases, the RRC parameter indicates that the UE is configured and implemented for the M-TRP operation. The method may further include deriving the receive beam based on information in the TCI selection field based on bit values ​​in the DCI including the CORESET; and receiving the PDSCH timing based on the receive beam.

[0019] In some cases, the RRC parameter indicates that the UE is not configured or implemented for the M-TRP operation. The method may further include determining whether a TCI selection field exists in the scheduling DCI of the CORESET; if the TCI selection field is determined to exist, identifying the bit width of the TCI selection; and deriving the receive beam.

[0020] In some cases, the method further includes deriving the received beam based on at least one of the following: (1) a combined / DL TCI state indicated by the bit value of the TCI selection field in DCI format 1_1 or DCI format 1_2; (2) a combined / DL TCI state indicated by a one-bit field in DCI format 1_2 or by two-bit fields in DCI format 1_1; (3) a combined / DL TCI state configured by RRC parameters other than the configuration; or (4) a predefined combined / DL TCI state.

[0021] In all respects, the M-TRP operation includes at least one of the following: Spatial Domain Multiplexing (SDM) PDSCH; Frequency Domain Multiplexing (FDM) PDSCH; Time Domain Multiplexing (TDM) PDSCH; Single Frequency Network (SFN) PDSCH; or Coherent Joint Transmission (CJT) PDSCH.

[0022] According to a general aspect of this disclosure, a method for wireless communication by a network entity includes sending to a user equipment (UE) indications of multiple Joint Transmission Configuration Indicator (TCI) states, multiple Downlink (DL) TCI states, or multiple Uplink (UL) TCI states (multiple joint / DL / UL TCI states). The network entity sends to the UE a Control Resource Set (CORESET) including scheduling information. The network entity then communicates with the UE based on the scheduling information and the multiple joint / DL / UL TCI states, without sending indications of a Sounding Reference Signal (SRS) resource set for uplink transmission or without sending configurations for implementing Multiple Transmitter Receiver Point (M-TRP) operation.

[0023] In various respects, it further includes sending the UE a configuration for multiple-input multiple-output (MIMO) operation, the configuration including a radio resource control (RRC) message configuring at least one of the following: (1) whether the uplink transmission is a codebook-based uplink transmission or a non-codebook-based uplink transmission, and the number of SRS resource sets used for the uplink transmission; or (2) a downlink control information (DCI) field in the DCI format related to beam selection for downlink reception.

[0024] According to a general aspect of this disclosure, an apparatus includes: one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; and at least one memory storing executable instructions. These executable instructions manipulate the processor or at least one of the one or more RF modems to perform the methods discussed in detail herein. Attached Figure Description

[0025] Figure 1A The illustration shows a wireless communication system according to various aspects of this disclosure, which includes multiple user equipment (UEs) and network entities communicating through one or more cells.

[0026] Figure 1B It is the technology used to implement this disclosure. Figure 1A Another example of a wireless communication system is shown in the block diagram of a wireless communication system.

[0027] Figure 1C It is possible Figure 1B A block diagram of an example base station operating in the system, which includes a central unit (CU) and a distributed unit (DU) of a distributed base station.

[0028] Figure 2A yes Figures 1A to 1B The UE can use a block diagram of an example protocol stack for communicating with the base station.

[0029] Figure 2B yes Figures 1A to 1B The UE can communicate with the base station's DU and CU according to the example protocol stack block diagram.

[0030] Figure 3 An example illustration is shown of the Joint Uplink (UL) Joint / UL Transmission Configuration Indicator (TCI) state that will be applied to uplink transmissions according to various aspects of this disclosure.

[0031] Figure 4 An example flowchart is shown for the UE to determine the joint / UL TCI status according to various aspects of this disclosure.

[0032] Figure 5 An example flowchart is shown for determining the joint / UL TCI status of network entities according to various aspects of this disclosure.

[0033] Figure 6 An example illustration is shown of the combined downlink (DL) combined / DL transport configuration indicator (TCI) state that will be applied to uplink transmissions according to various aspects of this disclosure.

[0034] Figure 7 An example flowchart is shown for the UE determining the joint / DL TCI state according to various aspects of this disclosure.

[0035] Figure 8 An example flowchart is shown for determining the joint / DL TCI status of network entities according to various aspects of this disclosure.

[0036] Figure 9An example flowchart is shown for the UE to determine the joint / UL TCI status according to various aspects of this disclosure.

[0037] Figure 10 An example flowchart is shown for the UE determining the joint / DL TCI state according to various aspects of this disclosure.

[0038] Figure 11 An example flowchart of a method performed by a UE according to various aspects of this disclosure is shown.

[0039] Figure 12 An example flowchart of a method performed by a network entity according to various aspects of this disclosure is shown.

[0040] Figure 13 This is a diagram illustrating the hardware implementation for an example UE device.

[0041] Figure 14 This is a diagram illustrating the hardware implementation for one or more example network entities.

[0042] The same number indicates the same component. Detailed Implementation

[0043] This disclosure provides methods, systems, and techniques for indicating a combined UL (combined / UL) Transport Configuration Indicator (TCI) state for uplink (UL) transmissions (e.g., Physical Uplink Shared Channel (PUSCH)) and a combined DL (combined / DL) TCI state for downlink (DL) transmissions (e.g., Physical Downlink Shared Channel (PDSCH)). For example, in multiple-input multiple-output (MIMO) operation, communication between a user equipment (UE) and a network entity can benefit from beam indication or determination using a unified TCI state, for example, to reduce signal overhead or latency. Various aspects of performing DL and UL beam indication or determination within a unified TCI framework are disclosed herein.

[0044] This disclosure provides methods and techniques for resolving ambiguities in beam indication for a scheduled PUSCH when the PUSCH is scheduled by DCI format 0_1 / 0_2, which does not include the SRS resource set indicator field. This disclosure further provides methods and techniques for reducing the error rate of decoding DCI format 1_1 / 1_2 with a TCI selection field (e.g., when the UE is not configured or implemented for M-TRP operation). For example, in previous practices, when the UE is not configured or implemented for M-TRP operation, the UE may not be aware of which indicated joint / UL TCI state is applied to transmit a PUSCH scheduled by DCI format 0_1 / 0_2. Additionally, the error rate of decoding DCI format 1_1 / 1_2 with a TCI selection field may be unnecessarily high.

[0045] In the M-TRP scheme, the UE sends signals to or receives signals from multiple TRPs, thereby improving communication reliability because the likelihood of multiple TRPs being blocked or impeded simultaneously is lower compared to a single TRP. However, M-TRP transmission can introduce interference when signals from different TRPs (e.g., to / from) overlap in time and frequency. Therefore, techniques such as using a single-frequency network (SFN) or spatial division multiplexing (SDM) can be implemented to synchronize the transmissions. These techniques (along with other techniques that facilitate communication between the UE and multiple TRPs) can be collectively referred to as the M-TRP scheme.

[0046] A unified TCI state comprises multiple TCI states (e.g., multiple beams) for use with multiple TRPs and allows the UE to select the optimal TRP for transmission or reception based on the TCI states of multiple TRPs. A unified TCI state can include a joint TCI state, a downlink TCI state, and an uplink TCI state. A unified TCI state can have two modes: a joint TCI mode and a separate TCI mode. In joint TCI mode, the joint TCI state is used to perform uplink (UL) transmission and downlink (DL) reception; while in separate TCI mode, the DL TCI state is used to perform DL reception, and the UL TCI state is used to perform UL transmission. Therefore, the joint / UL TCI state and the joint / DL TCI state are subsets of the unified TCI state. For example, a joint TCI state includes a combination of the TCI states of all TRPs (and the corresponding DL or UL for the joint / DL TCI state and the joint / UL TCI state). During operation, the network entity indicates two (or more) TCI states (e.g., a first unified TCI state and a second unified TCI state) to the UE for executing the M-TRP scheme. The activated TCI state corresponds to the beam or beam configuration used for transmission and reception between the UE and the network entity.

[0047] In known practice, when two SRS resource sets are configured for codebook-based (CB) or non-codebook-based (NCB) uplink transmissions, only the SRS resource set indicator field exists in DCI format 0_1 / 0_2. If only one SRS resource set is configured for CB or NCB transmissions, the SRS resource set indicator field does not exist in DCI format 0_1 / 0_2. See For example, 3GPP technical specification TS 38.214 v.17.2.0, Rel.17, section 6.1.1.1. In this situation, the network entity may be unable to inform the UE (e.g., of multiple joint TCI states of a unified TCI state) which indicated joint / UL TCI state can be applied to send PUSCHs scheduled by DCI format 0_1 / 0_2.

[0048] In existing technologies for MIMO communication, for a PDSCH (e.g., scheduled by DCI format 1_1 / 1_2), the two-bit TCI field in the scheduling DCI format 1_1 / 1_2 can be configured to indicate which indicated joint / DL TCI state (first or second, or both) is applied to receive the scheduled PDSCH. This is used to indicate both the first and second indicated joint / DL TCI states when the UE operates with an M-TRP scheme / feature for PDSCH (e.g., SDM, FDM, TDM, SFN, or CJT). However, such M-TRP schemes / features for PDSCH require both the first and second indicated joint / DL TCI states to be applied to the PDSCH. When the UE is not configured or implemented with any M-TRP scheme / feature for PDSCH, using the two-bit TCI selection field in signaling may be of little use. When TCI selection field information exists but is not utilized, it may even increase the error rate of decoding PDCCH, including such DCI formats.

[0049] As discussed below, this disclosure provides various examples to address the problems discussed above and provides how to perform beam indication for PUSCH scheduled by DCI format 0_1 / 0_2 when the SRS resource indicator field is not present in the scheduling DCI. Various examples also disclose how to design or utilize the TCI selection field when no M-TRP scheme / feature for PDSCH is configured or implemented. For example, aspects of this disclosure include wireless communication methods performed by the UE. Example methods include: receiving indications of multiple joint TCI states, multiple DL TCI states, or multiple UL TCI states (multiple joint / DL / UL TCI states) from a network entity; receiving a control resource set (CORESET) including scheduling information; and communicating with the network entity based on the scheduling information and the multiple joint / DL / UL TCI states without receiving an indication of the sounding reference signal (SRS) resource set for uplink transmission or without receiving configuration for implementing multiple transmit receiver point (M-TRP) operation.

[0050] Additionally, this disclosure provides methods for power control, including how to determine uplink transmission power after a cell-specific BFR has been completed or after each TRP BFR has been completed. It should also be noted that the ideas, concepts, or embodiments throughout this document can be applied to issues or procedures with similar considerations or concerns in LTE / NR / 6G or other radio access technologies (RATs).

[0051] Figure 1AA 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).

[0052] The operation and / or network design of base station (BS) 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 across two or more units in various physical locations, as well as virtually distributing functionality for 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 (BS) 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 RU 106 and / or BS 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RU 106 / BS 104.

[0053] 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 media, such as a fronthaul link 160 between RU 106d and the baseband unit (BBU) 112 of BS 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 to transmit or receive 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) is configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and BS 104e in cell 190e via inter-cell communication beams 136 to 138 of RU 106a and BS 104e.

[0054] 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 that manages 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.

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

[0056] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to BS 104. Therefore, BS 104 may include at least one of RU 106, DU 108, or CU 110. BS 104 provides UE 102 with access to the core network. BS 104 may relay communication between UE 102 and the core network (not shown). BS 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".

[0057] Transmissions from UE 102 to BS 104 / RU 106 are called uplink (UL) transmissions, while transmissions from BS 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 BS 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and BS 104d / RU 106d.

[0058] The communication link between UE 102 and BS 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 BS 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, where, 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 a secondary cell (Scell).

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

[0060] UE 102 and BS 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 in one or more transmit directions of RU 106b based on a first communication beamset 132. UE 102b may receive downlink beamforming signals from RU 106b in one or more receive directions of UE 102b based on a second communication beamset 134b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b in one or more transmit directions of UE 102b based on the second communication beamset 134b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for beamforming signals. The transmission and reception directions of UE 102 and BS 104 / RU 106 can be the same or different.

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

[0062] BS 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to BS 104 or at least one element of BS 104, such as RU 106, DU 108, and / or CU 110. BS 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 station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Entities at BS 104 may be implemented as IAB nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations, or decomposed base stations 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 BS 104e and base station / RU 106a. In such cases, BS 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0063] Uplink / downlink signaling can also be transmitted 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 BS 104 / RU 106 (such as RU 106c). The SPS 114 can correspond to one or more of the Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location systems. The SPS114 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.

[0064] Still referencing Figure 1A In some respects, any of the UEs 102 may include a beam determination component 140 configured to receive from the BS 104 an indication of multiple joint TCI states, multiple DL TCI states, or multiple UL TCI states (multiple joint / DL / UL TCI states); receive a control resource set (CORESET) including scheduling information; and communicate with the BS 104 based on the scheduling information and the multiple joint / DL / UL TCI states without receiving an indication of a sounding reference signal (SRS) resource set for uplink transmission, or without receiving a configuration for implementing multiple transmit receiver point (M-TRP) operation.

[0065] BS 104 may include a beam determination component 150 configured to send to UE 102 indications of multiple Joint Transmission Configuration Indicator (TCI) states, multiple Downlink (DL) TCI states, or multiple Uplink (UL) TCI states (multiple joint / DL / UL TCI states). Beam determination component 150 sends to UE 102 a control resource set (CORESET) including scheduling information. Beam determination component 150 then communicates with UE 102 based on the scheduling information and the multiple joint / DL / UL TCI states without sending indications of a Sounding Reference Signal (SRS) resource set for uplink transmission, or without sending configurations for implementing Multiple Transmitter Receiver Point (M-TRP) operation.

[0066] therefore, Figure 1AA wireless communication system that can be implemented in conjunction with one or more other 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.

[0067] Now for reference Figure 1B Another example of the wireless communication system 100 includes UE 102, BS 104, BS 106, and core network (CN) 110. BS 104 and 106 can operate in RAN 105 connected to core network (CN) 110. For example, CN 110 can be implemented as an evolved packet core (EPC) 111 or a fifth-generation (5G) core (5GC) 160. In another example, CN 110 can also be implemented as a sixth-generation (6G) core.

[0068] BS 104 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 106 may similarly utilize one or more TRPs to cover one or more cells (e.g., cell 126). For example, BS 104 operates cell 124 using TRPs 107-1 and 107-2 and cell 125 using TRP 107-3, and base station 106 operates cell 126 using TRPs 108-1 and 108-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, BS 104 connects each of TRPs 107-1, 107-2, and 107-3 via a fiber optic connection or an Ethernet connection. If BS 104 is a gNB, then cells 124 and 125 are NR cells. If BS 104 is an (ng-)eNB, then cells 124 and 125 are Evolved Universal Terrestrial Radio Access (EUTRA) cells. Similarly, if base station 106 is a gNB, then cell 126 is an NR cell, and if base station 106 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 base station 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 BS 104 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 interface to communicate with base station 106 via TRP 108-1 and / or TRP 108-2. Each of BS 104 and 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). BS 104 and 106 may also interconnect via an interface for interconnecting NG RAN nodes (e.g., X2 or Xn interface).

[0069] When a base station (e.g., BS 104 or 106) transmits DL data via a TRP (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, or TRP 108-2), BS 104 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 it. In some implementations, BS 104 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 BS 104. In some implementations, the data includes IQ data, physical layer bit sequences, or MAC PDUs.

[0070] Among other components, EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. Generally, SGW 112 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., and MME 114 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.

[0071] like Figure 1B As shown, BS 104 supports cells 124 and 125, and base station 106 supports cell 126. Cells 124, 125, and 126 can partially overlap, allowing UE 102 to select, reselect, or hand over from one of cells 124, 125, and 126 to another. For direct message or information exchange, BS 104 and base station 106 can support X2 or Xn interfaces. Generally, CN 110 can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0072] BS 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable storage of instructions executed by the one or more general-purpose processors. Alternatively, processing hardware 130 may include dedicated processing units. Processing hardware 130 may include a PHY controller 132 configured to transmit data and control signals on physical DL channels and DL reference signals 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 132 is also configured to receive data and control signals on physical UL channels and / or UL reference signals 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 130 includes a MAC controller 134 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 130 may further include an RRC controller 136 to implement procedures and message passing at the RRC sublayer of the protocol communication stack. Base station 106 may include processing hardware 141 similar to processing hardware 130. Specifically, components 142, 144, and 146 may be similar to components 132, 134, and 136, respectively.

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

[0074] Figure 1C Describe an example distributed or decomposed implementation of one or both of BS 104, 106. In this implementation, each of BS 104 and / or 106 includes a central unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 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 172 may include a PDCP controller (e.g., PDCP controllers 134, 144), an RRC controller (e.g., RRC controllers 136, 146), and / or an RRC inactivity controller (e.g., RRC inactivity controllers 138, 148). In some implementations, CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In some implementations, CU 172 does not include an RLC controller.

[0075] Each DU in DU 174 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 controllers 132, 142) 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.

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

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

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

[0079] Figure 2A An example protocol stack 200 is shown in a simplified manner, which allows UE 102 to communicate with an eNB / ng-eNB or gNB (e.g., one or both of BS 104, 106).

[0080] In example stack 200, 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 then provides an RLC channel to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NRPHY 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 transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can then provide data transfer services to the SDAP sublayer 212 or the RRC sublayer (…). Figure 2A (Not shown in the image) provides data transfer services. In some implementations, such as... Figure 2A 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 2A As shown, UE 102 can support the layering of NR PDCP 210 on top of EUTRA RLC206A, and the layering of SDAP sublayer 212 on top of NR PDCP sublayer 210.

[0081] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 (e.g., from an IP layer that is layered directly or indirectly above 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".

[0082] On the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can direct data to the RRC sublayer ( Figure 2A(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.

[0083] Therefore, it is possible to functionally segment the radio protocol stack, such as... Figure 2B The radio protocol stack 250 is shown in the diagram. The CU at one or both of BS 104, 106 can retain all control and upper-layer functionality (e.g., RRC 214, SDAP 212, NR PDCP 210), while lower-layer operations (e.g., NR RLC 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.

[0084] Next, refer to Figures 3 to 12 Several example scenarios will be discussed. In the following scenarios, BS 104 can communicate with UE 102 via TRP 107-1, 107-2, or 107-3. Generally, Figures 3 to 12 The same events in the same figures are labeled with the same reference numerals.

[0085] Figure 3 Example illustration 300 shows a Joint Uplink (UL) Joint / UL Transport Configuration Indicator (TCI) state that will be applied to uplink transmissions according to various aspects of this disclosure. As shown, UE 102 may send 310 to network entity 104 (NW) regarding UE capabilities supporting a unified TCI state for M-TRP operation. Network entity 104 sends 320 a Radio Resource Control (RRC) configuration to the UE, thereby configuring: (1) one or more Joint / UL TCI states, (2) whether to use CB-based UL transmissions or NCB-based UL transmissions, and / or (3) one or more SRS resource sets associated with CB / NCB of DCI format 0_1 ​​or 0_2.

[0086] Network entity 104 sends a Media Access Control (MAC) control element (CE) at 330 to activate multiple joint / ULTCI states from the configured multiple joint / UL TCI states. Network entity 104 may optionally send downlink control information (DCI) indicating a first joint / UL TCI state, a second joint / UL TCI state, or both of the activated joint / UL TCI states. In some cases, two or more joint / UL TCI states may be activated or indicated at 330 and 340.

[0087] Network entity 104 sends a 350 scheduling DCI with DCI format 0_1 ​​or DCI format 0_2 to UE 102 on a control resource set (CORESET). UE 102 detects the scheduling DCI on the CORESET (e.g., it may carry other information). Upon detection, UE 102 (and / or network entity 104) determines whether a first DCI field (e.g., a probe reference signal (SRS) resource indicator field) is present or accessible in the 360 ​​scheduling DCI. UE 102 also determines the bit width of the 360 ​​first DCI field (if present) and how to interpret the first DCI field, and / or which indicated joint / UL TCI state or spatial transmission filter is applied to the scheduled Physical Uplink Shared Channel (PUSCH) transmission timing, based on the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 ​​or DCI format 0_2. The determination may be based on a first signaling or mechanism further described below.

[0088] UE 102 then transmits the scheduled PUSCH transmission opportunity via the determined and indicated joint / UL TCI state or spatial transmission filter.

[0089] Figure 4 The UE is shown according to various aspects of this disclosure (e.g., Figure 3 Example flowchart 400 for determining the joint / UL TCI status of UE 102. Flowchart 400 describes the applicable... Figure 3 The call flow diagram 300 illustrates the operation of this section. As shown, flowchart 400 begins with receiving the RRC parameters at 402, configuring whether to use CB-based or NCB-based UL transmission in the active UL BWP or in the serving cell.

[0090] The UE receives configurations for one or more SRS resource sets associated with a CB or NCB of DCI format 0_1 ​​or DCI format 0_2 in the active UL BWP or serving cell. The UE detects a scheduling DCI of DCI format 0_1 ​​or DCI format 0_2 on the CORESET.

[0091] The UE determines whether a first DCI field (e.g., an SRS resource indicator field) exists in the 460-scheduled DCI, the bit width of the first DCI field (if the first DCI field exists), how to interpret the first DCI field, and / or which indicated joint / UL TCI state or spatial transmission filter will be applied to the scheduled PUSCH transmission timing.

[0092] The UE then transmits the scheduled PUSCH transmission opportunity via the determined indicated joint / UL TCI state or spatial transmission filter.

[0093] Figure 5 Network entities (e.g., according to various aspects of this disclosure) are shown. Figure 3 Example flowchart 500 for determining the joint / UL TCI status of network entity 104. Flowchart 500 describes the applicable... Figure 3 The call flow diagram 300 shows a portion of the operation. As shown, flowchart 500 begins by sending the RRC parameters 502 to the UE to configure whether to use CB-based UL transmission or NCB-based UL transmission in the active UL BWP or in the serving cell.

[0094] The network entity sends configuration information for one or more SRS resource sets associated with a CB or NCB of DCI format 0_1 ​​or DCI format 0_2 in the active UL BWP or serving cell. The UE detects a scheduling DCI of DCI format 0_1 ​​or DCI format 0_2 on the CORESET.

[0095] The network entity determines, based on the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2, and / or based on signaling / mechanisms, whether 560 indicates the first DCI field (e.g., SRS resource indicator field) in the scheduled DCI, (when indicated) the bit width of the first DCI field, and / or which indicated joint / UL TCI state or spatial transmission filter is applied to determine the timing of how to receive the scheduled PUSCH transmission.

[0096] The network entity then receives the scheduled PUSCH transmission opportunity via the determined and indicated joint / UL TCI status or spatial transmission filter.

[0097] Figure 6 An example illustration 600 shows a Joint Downlink (DL) Joint / DL Transport Configuration Indicator (TCI) state that will be applied to uplink transmissions according to various aspects of this disclosure. As shown, UE 102 sends 612 UE capabilities to network entity 104 to support a unified TCI state for M-TRP operations.

[0098] Network entity 104 sends 622 to configure RRC configuration for one or more federated / DL TCI states, and / or whether a second DCI field (e.g., a TCI selection field) exists in DCI format 1_1 or DCI format 1_2.

[0099] Network entity 104 sends 632 to activate MAC-CE from multiple joint / DL TCI states of the configured joint / DL TCI states. Network entity 104 may optionally send 642 to indicate DCI from a first joint / DL TCI state, a second joint / DL TCI state, or both of the first and second joint / DL TCI states of the activated joint / DL TCI states.

[0100] Network entity 104 sends 652 scheduling DCI with DCI format 1_1 or DCI format 1_2 on CORESET.

[0101] UE 102 and / or network entity 104 determine whether a second DCI field exists in the 662 scheduling DCI based on whether the RRC parameter is configured to have a second DCI field, whether the UE receives any RRC parameter that configures or implements the M-TRP PDSCH feature / scheme, and / or based on the second signaling or mechanism further described below, the bit width of the second DCI field when it exists, and / or how to interpret the second DCI field when it exists.

[0102] Network entity 104 sends the PSDCH scheduled by 672 via the indicated federated / DL TCI state indicated by the TCI selection field and / or signaling or mechanism.

[0103] Figure 7 The UE (e.g., according to various aspects of this disclosure) is shown. Figure 6 Example flowchart 700 for determining the joint / DL TCI state in UE 102. Flowchart 700 describes the applicable... Figure 6 The call flow diagram 600 shows a portion of the operation. As shown, flowchart 700 begins with the UE receiving 722 an RRC parameter configuring whether a second DCI field (e.g., a TCI selection field) exists in DCI format 1_1 or DCI format 1_2.

[0104] The UE detects a scheduling DCI with DCI format 1_1 or DCI format 1_2 on CORESET 752. The UE determines whether a second DCI field exists in the scheduling DCI 762, the bit width of the second DCI field if it exists, and / or how to interpret the second DCI field if it exists, based on whether the RRC parameter is configured to have a second DCI field, whether the UE receives any RRC parameter that configures / implements MTRP PDSCH features or schemes, and / or based on further second signaling or mechanisms below.

[0105] The UE then receives the PDSCH scheduled by 772 via the indicated joint / DL TCI state as indicated by the TCI selection field and / or signaling or mechanism.

[0106] Figure 8 Network entities (e.g., according to various aspects of this disclosure) are shown. Figure 6 Example flowchart 800 for determining the federated / DL TCI state of network entity 104. Flowchart 800 describes the applicable... Figure 6 The call flow diagram 600 shows a portion of the operation. As shown, flowchart 800 begins by sending the RRC parameter 822 to the UE to configure whether a second DCI field (e.g., a TCI selection field) exists in DCI format 1_1 or DCI format 1_2.

[0107] Network entities send 852 scheduling DCIs with DCI format 1_1 or DCI format 1_2 on CORESET.

[0108] The network entity determines, based on whether the network entity is configured to have a second DCI field, whether the network entity sends any RRC parameter for configuring / implementing M-TRP PDSCH features / schemes, and / or based on signaling or mechanisms, whether 862 indicates the second DCI field in the scheduling DCI, the bit width of the second DCI field when indicated, and / or how the second DCI field is indicated when indicated.

[0109] The network entity then sends the PDSCH scheduled by 872 to the UE via the indicated joint / DL TCI state as indicated by the TCI selection field and / or signaling or mechanism.

[0110] Figure 9 An example flowchart 900 is shown for a UE determining the joint / UL TCI state according to various aspects of this disclosure. As shown, the UE receives 920 configuration of CB / NCB. txConfig The configuration, and one or two SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2.

[0111] The UE detects on the CORESET that 950 has a scheduling DCI with DCI format 0_1 / 0_2. The UE determines whether the number of configured SRS resource sets associated with 960 and the CB / NCB of DCI format 0_1 / 0_2 is one or two.

[0112] When the UE determines that the quantity is one (960), the UE uses other signaling or mechanisms (965, as discussed in the first embodiment of the signaling or mechanism below) to determine which indicated joint / UL TCI state or spatial transmission filter is applied to transmit the scheduled PUSCH transmission opportunity. The UE then transmits the scheduled PUSCH transmission opportunity (970) via the indicated joint / UL TCI state or spatial transmission filter determined above.

[0113] When the UE determines that the quantity is two at 960, the UE determines that there are two bits of the SRS resource set indicator field in the DCI scheduling at 973. The UE then sends the scheduled PUSCH transmission opportunity at 980 via the union / UL TCI state indicated by the SRS resource set indicator field.

[0114] Figure 10 An example flowchart 1000 is shown for a UE determining the joint / DL TCI state according to various aspects of this disclosure. As shown, the UE receives 1022 a configuration indicating that a TCI selection field exists in either DCI format 1_1 or DCI format 1_2.

[0115] The UE detects a scheduling DCI with DCI format 1_1 / 1_2 on CORESET 1052. The UE determines whether it has received any RRC parameters for configuring / implementing M-TRP PDSCH features / schemes on 1057.

[0116] When the UE determines that 1057 has implemented the M-TRP PDSCH feature or scheme, the UE determines that there is a two-bit TCI selection in the 1082 scheduling DCI (e.g., in the second DCI field). The UE then receives the PDSCH scheduled by 1087 via the indicated joint / DL TCI state indicated by the two-bit TCI selection field.

[0117] When the UE determines that the M-TRP PDSCH feature or scheme has not yet been implemented in 1057, the UE determines or identifies, based on other signaling / mechanisms (e.g., the second embodiment or signaling / mechanism discussed below), whether the TCI selection field in the scheduled DCI in 1062 is one bit, two bits, or absent. The UE then receives the PDSCH scheduled in 1072 via the indicated joint / DL TCI state indicated by the TCI selection field and / or other signaling / mechanisms.

[0118] The various examples and embodiments discussed below are applicable to the above. Figures 3 to 10 The example methods or flowcharts shown in the document.

[0119] In some implementations, the TRP (e.g., TRP 107-1, TRP 107-2, TRP 107-3, TRP 108-1, and / or TRP 108-2) may be associated with or identified by a TRP identifier. In some implementations, a network entity (e.g., base station 104 or 106) includes or configures the TRP identifier in the UL configuration, and the network entity sends this UL configuration 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 network entity to the UE. In some implementations, UL transmission includes PUSCH transmission, PUCCH transmission, and / or SRS transmission. In some implementations, the network entity includes a TRP identifier in the DL configuration, which the network entity sends 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 (such as RRC Reconfiguration messages or RRC Recovery messages) sent by the network 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.

[0120] In other implementations, the network 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 network entity sends an RRC message (e.g., an RRC reconfiguration message or an RRC recovery message) to the UE that includes configuration parameters.

[0121] In some implementations, the network entity configures or indicates a first TRP identifier for the UE. In some implementations, the UE derives a first TRP identifier (value). In some implementations, the network entity configures or indicates a second TRP identifier (value) for the UE. In some implementations, the UE derives a 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.

[0122] In some implementations, the network entity configures the serving cell to be associated with a first TRP or a first TRP identifier (value). In some implementations, the network entity configures a first control resource set (CORESET) associated with the serving cell or the first TRP. The network entity can configure... CORESETPoolIndex #0 is used to identify the first CORESET. In one implementation, the network entity may send an RRC message (e.g., an RRC setup 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 network entity, which means the UE monitors the PDCCH or receives DCI from the network entity (i.e., from the first TRP) via the first TRP. In such a case, the UE determines CORESETPoolIndex #0 indicates the TRP (i.e., the first TRP) of the network entity.

[0123] In one implementation, the network 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 network entity indicates or configures this association in an RRC message. In one implementation, the network entity configures the non-serving cell associated with the second TRP or the second TRP identifier (value). In some implementations, the network entity configures the second CORESET to be associated with a serving cell, a non-serving cell, or the second TRP. The network entity can configure... CORESETPoolIndex #1 is used to identify the second CORESET. In one implementation, the network entity may send an RRC message (e.g., an RRC setup 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 network entity, which means the UE monitors the PDCCH or receives DCI from the network entity (i.e., from the second TRP) via the second TRP. In such a case, the UE determines... CORESETPoolIndex #1 indicates the TRP (i.e., the second TRP).

[0124] In some implementations, the network 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 network entity can configure a joint TCI state list for the CC of the serving cell. For example, the network 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 UL TCI states.

[0125] In some implementations, the network entity can configure the first RRC parameter for the UE. unifiedTCI-StateType First RRC parameter unifiedTCI-StateType This can be configured per serving cell. 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 "separate". First RRC parameter unifiedTCI-StateType One or more of the following can be provided: - If the first RRC parameter of the CC used for the serving cell indicates "joint", the network entity can explicitly or implicitly configure one or more joint TCI state lists for the CC used for the serving cell or the UE. - If the first RRC parameter for the CC used for the serving cell indicates "separate", the network entity can explicitly or implicitly configure one or more DL TCI status lists for the CC used for the serving cell for the UE. - If the first RRC parameter of the CC used for the serving cell indicates "separate", the network entity can explicitly or implicitly configure one or more UL TCI status lists for the CC used for the serving cell for the UE.

[0126] In some implementations, if the network entity implicitly configures one or more TCI state lists for the serving cell's CC for the UE, then the configuration can mean

[0127] - Network entities are configured in RRC (e.g., ServingCellConfig (Explicitly) configure one or more TCI status lists for the CC of the serving cell.

[0128] In some implementations, if the network entity implicitly configures one or more TCI state lists for the serving cell's CC for the UE, then the configuration can mean at least one of the following: - Network entities are configured in RRC (e.g., ServingCellConfig Configure 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 for reference serving cells / CCs; - The UE determines that one or more TCI status lists used for other serving cells / CCs or reference serving cells / CCs are also used for the serving cell's CC.

[0129] In some implementations, the network entity may send the first MAC-CE to the UE when or after the following occurs: - The network entity configures one or more TCI state lists for the UE to use for the serving cell's CC; and / or - The UE references or determines one or more TCI status lists for the CC used to serve the cell.

[0130] In some implementations, 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 for (subsequently) performing DL and / or UL transmissions.

[0131] In some implementations, 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 apply to different TRPs. The UE can then (directly) apply or use these two TCI states activated / indicated by the first MAC-CE for (subsequently) performing DL and / or UL transmissions.

[0132] In some implementations, a TCI state can be mapped to a TCI code point based on a 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, the TCI code point can indicate one of the following: - One or more joint TCI states, Some joint TCI states can be TCI states associated with the first TRP (identifier), while other joint TCI states can be TCI states associated with the second TRP (identifier). - One or more DL TCI states, Some DL TCI states can be TCI states associated with the first TRP (identifier), while other DL TCI states can be TCI states associated with the second TRP (identifier). - One or more UL TCI statuses, Some UL TCI states can be TCI states associated with the first TRP (identifier), while other UL TCI states can be TCI states associated with the second TRP (identifier). - One or more DL TCI states and one or more UL TCI states.

[0133] Some TCI states can be TCI states associated with the first TRP (identifier), while other TCI states can be TCI states associated with the second TRP (identifier). In some cases, the number of joint TCI states indicated by a network entity in the TCI code point can be up to four. In some cases, the number of DL TCI states indicated by a network entity in the TCI code point can be up to four. In some cases, the number of UL TCI states indicated by a network entity in the TCI code point can be up to four.

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

[0135] In some implementations, the UE may receive a first DCI indicating one or more TCI states. The first DCI may indicate one or more TCI states via a TCI field. In response to receiving the first DCI, the UE may send a first acknowledgment signal to the network 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.

[0136] In some cases, the first time slot may be the earliest time slot following at least the first application period after the last symbol of the PUCCH or PUSCH transmission. In some cases, the earliest time slot (used to determine the first time slot) and / or the first application 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 period may be in units of: symbol, sub-time slot, time slot, subframe, frame, ms, or second. In some cases, the first application period may be... beamAppTime .

[0137] In other implementations, the UE may receive a first MAC-CE indicating one or more TCI states. For example, the first MAC-CE may indicate a single 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 with a second TRP (identifier). In such cases, 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 network 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.

[0138] In some cases, the second timeslot can be the earliest timeslot within at least the second application time period following the (last) timeslot of a PUCCH or PUSCH transmission. In some cases, the second application time period can be... In some cases, μ can be an SCS configuration used for PUCCH or PUSCH transmissions; It can be used for values ​​of 0 for a frequency range of 1. The subcarrier spacing configuration, and Depend on K-Mac Provided, or if not provided K-Mac ,but .

[0139] In some implementations, the network entity may send a DCI (e.g., a first DCI) to indicate a first joint / DL / UL TCI state and / or a second joint / DL / UL TCI state to the UE (e.g., via the TCI field in the DCI). In some cases, the first joint / DL / UL TCI state and / or the second joint / DL / UL TCI state may be derived from one or more TCI states activated by a first MAC-CE. In some other implementations, the network entity may send a MAC-CE (e.g., a first MAC-CE) to indicate the first joint / DL / UL TCI state and / or the second joint / DL / UL TCI state to the UE, i.e., activating only the first joint / DL / UL TCI state and / or the second joint / DL / UL TCI state. The first joint / DL / UL TCI state may be referred to as the first joint TCI state, the first DL TCI state, or the first UL TCI state. The second joint / DL / UL TCI state may be referred to as the second joint 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 / DLTCI state may be associated with the second TRP or the second TRP identifier.

[0140] Several aspects are present in the following embodiments that relate to beam indication for PUSCH scheduled by DCI format 0_1 / 0_2 and the design / utilization of TCI selection fields when no M-TRP scheme / feature for PDSCH is configured or implemented. For example, the following embodiments can be applied to signaling or mechanisms for the UE to determine beam configuration in operations 965 and 1062.

[0141] In some implementations, within an active UL BWP or in the serving cell, the network entity can configure one or more SRS resource sets for DCI format 0_1 / 0_2 for the UE. In some cases, within an active UL BWP or in the serving cell, the network entity can configure one or more SRS resource sets for DCI format 0_1 / 0_2 associated with the CB for the UE. In some cases, within an active UL BWP or in the serving cell, the network entity can configure one or more SRS resource sets for DCI format 0_1 / 0_2 associated with the NCB for the UE.

[0142] In some implementations, the network entity can configure RRC parameters for the UE. txConfig This indicates whether the UE uses codebook-based or non-codebook-based transmission in an active ULBWP or in the serving cell. RRC parameters txConfig It can indicate CB or NCB (i.e., codebook or not codebook ).

[0143] In some implementations, if the RRC parameter txConfig The system indicates that the CB (CB Frame) and / or, if the network entity configures two SRS resource sets associated with the CB of DCI format 0_1 / 0_2 for the UE, the UE can determine that a first DCI field exists in each of DCI formats 0_1 / 0_2. In some implementations, if the RRC parameter... txConfig The NCB is indicated, and / or if the network entity configures two SRS resource sets associated with the NCB of DCI format 0_1 / 0_2 for the UE, the UE can determine that a first DCI field exists in both DCI formats 0_1 and 0_2. In some cases, the first DCI field may be an SRS resource set indicator field.

[0144] In some implementations, the UE can receive or detect a scheduling DCI with DCI format 0_1 / 0_2 on the CORESET.

[0145] In some implementations, if a first DCI field exists in DCI format 0_1 / 0_2, the network entity can use the first DCI field to indicate which indicated union / UL TCI state is applied to the transmission of one or more PUSCH transmissions scheduled by the DCI format 0_1 / 0_2.

[0146] For example, - If the first DCI field indicates code point "00", the UE can apply the first indicated joint / UL TCI state to send one or more PUSCH transmission opportunities.

[0147] - If the first DCI field indicates code point "01", the UE can apply the second indicated joint / UL TCI state to send one or more PUSCH transmission opportunities.

[0148] - If the first DCI field indicates code point "10" or "11", the UE may apply the first indicated joint / ULTCI state to send one or more PUSCH transmission opportunities associated with the first SRS resource set. The UE may apply the second indicated joint / ULTCI state to send one or more PUSCH transmission opportunities associated with the second SRS resource set.

[0149] In some implementations, if the RRC parameter txConfigThe instruction CB, and / or if the network entity configures a (only) SRS resource set associated with the CB of DCI format 0_1 / 0_2 for the UE, allows the UE to determine whether the first DCI field may or may not be present in DCI format 0_1 / 0_2. In some implementations, if the RRC parameter txConfig The NCB is indicated, and / or if the network entity has configured (only) one SRS resource set associated with the NCB for the UE, the UE can determine whether the first DCI field may or may not exist in DCI format 0_1 / 0_2.

[0150] In some implementations, if the RRC parameter txConfig The UE can determine that a first DCI field does not exist in DCI format 0_1 / 0_2 if the network entity has configured a (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2. In this implementation, the UE can apply the first indicated joint / UL TCI state to send one or more PUSCH transmission opportunities scheduled by DCI format 0_1 / 0_2. Alternatively, in this implementation, the UE can apply the second indicated joint / UL TCI state to send one or more PUSCH transmission opportunities scheduled by DCI format 0_1 / 0_2.

[0151] In some implementations, if the RRC parameter txConfig The network entity can configure a second RRC parameter for the UE if it has configured a CB (or NCB) and / or if it has configured a single SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2 for the UE. The second RRC parameter can indicate whether the first indicated joint / UL TCI state or the second indicated joint / UL TCI state is applied to the transmission of PUSCH (or one or more PUSCH transmission opportunities) scheduled by DCI format 0_1 / 0_2 without the first DCI field. In such an implementation, the UE can determine that the first DCI field does not exist in DCI format 0_1 / 0_2. The UE can then transmit one or more PUSCH transmission opportunities scheduled by DCI format 0_1 / 0_2 based on the second RRC parameter.

[0152] In some implementations, if the RRC parameter txConfigThe UE can determine that a first DCI field exists in DCI format 0_1 / 0_2 if the network entity configures a (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2, and / or if the network entity configures the UE with (only) one SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2. In this implementation, the UE can determine that the first DCI field includes one bit in DCI format 0_1 / 0_2.

[0153] In some other implementations, if the RRC parameter txConfig Indicates the CB (or NCB), and / or if the network entity has configured the UE with (only) one SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2, - If one of the following occurs, the UE can determine that the first DCI field exists in DCI format 0_1 / 0_2 respectively, and / or the UE can determine that the first DCI field includes one bit in DCI format 0_1 / 0_2 respectively: o The UE receives a MAC-CE that activates the first and second joint / UL TCI states / maps the first and second joint / UL TCI states to (at least) one TCI field code point, and / or the UE has already applied the MAC-CE, or o The UE receives a DCI with a TCI field, which indicates a TCI field code point having the first and second indicated joint / ULTCI states, and / or the UE has applied the TCI field code point indication. Otherwise, the UE can determine that the first DCI field does not exist in DCI format 0_1 / 0_2 respectively.

[0154] When the UE determines that the first DCI field exists in DCI format 0_1 / 0_2 respectively, when the RRC parameter txConfigWhen indicating a CB (or NCB), and / or when a network entity configures a UE with (only) one SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2, the UE determines whether the first DCI field is used only to indicate the first indicated joint / UL TCI state or the second indicated joint / UL TCI state is applied to the transmission of PUSCH (or one or more PUSCH transmissions) scheduled by DCI format 0_1 / 0_2. This can mean how the UE interprets the "SRS Resource Indicator Field" and "Precoding Information and Layer Digital Segment" in DCI format 0_1 / 0_2 as independent of the first DCI field. The UE can interpret the "SRS Resource Indicator Field" and "Precoding Information and Layer Digital Segment" in DCI format 0_1 / 0_2 based on (only) one configured SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2. The network entity can indicate the first indicated TCI or the second indicated TCI through the first DCI field of the corresponding DCI format. In one example, the first DCI field may occupy / include 1 bit, which indicates either the first indicated TCI or the second indicated TCI. In another example, the first DCI field may still occupy / include 2 bits, and the network entity avoids indicating the field code point as "10" or "11", which indicates either "both the first indicated joint / UL TCI state and the second indicated joint / UL TCI state" or "reserved".

[0155] In some implementations, when a network entity configures only one SRS resource set for DCI format 0_1 / 0_2 respectively, the network entity can configure a first DCI field that exists for DCI format 0_1 / 0_2.

[0156] In some implementations, if the RRC parameter txConfig The system indicates that the CB (or NCB), and / or if the network entity has configured a (only) one SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2 for the UE, the UE can determine that the first DCI field does not exist in DCI format 0_1 / 0_2 respectively. If the RRC parameter... txConfig Instructing the CB (or NCB), and / or if the network entity has configured a UE with (only) one SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2, the network entity may be required to perform one of the following: - Network entities avoid sending DCI format 0_1 / 0_2 separately to schedule one or more PUSCH transmission opportunities for the UE; or This could mean that the network entity only sends DCI format 0_0 to schedule PUSCH transmissions for the UE. - Network entities should avoid sending a MAC-CE to the UE, which could activate two combined / UL TCI states or map two combined / UL TCI states to TCI field code points in DCI format 0_1 / 0_2; or - Network entities should avoid sending a MAC-CE to the UE that could activate two joint / UL TCI states or map two joint / UL TCI states to at least one TCI field code point in DCI format 0_1 / 0_2; or - Network entities avoid sending DCIs with a TCI field to the UE, which indicates TCI field code points with a first combined / ULTCI state and a second combined / UL TCI state.

[0157] In some implementations, if the RRC parameter txConfig Instructions for a CB (or NCB), and / or if the network entity has configured the UE with (only) one SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2, the UE may not expect one of the following or may identify one of the following as an error condition: - The network entity sends DCI format 0_1 / 0_2 respectively to schedule one or more PUSCH transmission opportunities for the UE; or - The network entity sends a MAC-CE to the UE, which can activate two joint / UL TCI states or map two joint / UL TCI states to TCI field code points in DCI format 0_1 / 0_2; or - The network entity sends a MAC-CE to the UE, which activates two joint / UL TCI states or maps the two joint / UL TCI states to at least one TCI field code point in DCI format 0_1 / 0_2; or - The network entity sends a DCI with a TCI field to the UE, which indicates a TCI field code point with a first combined / UL TCI state and a second combined / UL TCI state.

[0158] In some implementations, if the RRC parameter txConfigThe network entity may indicate that if the UE has configured a (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2, the UE can determine that a first DCI field does not exist in DCI format 0_1 / 0_2. In some cases, the (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2 may be configured by the network entity to conform to / share / apply the indicated joint / UL TCI state. The network entity may further configure whether the (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2 conforms to / shares / applies the first indicated joint / UL TCI state or the second indicated joint / UL TCI state.

[0159] In some implementations, - If only one SRS resource set associated with a CB (or NCB) of DCI format 0_1 / 0_2 is configured by a network entity to conform to the federated / UL TCI state indicated by the application / shared / app, o Then the UE can apply the same indicated joint / UL TCI state, which follows / shares / applies the same SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2, to send one or more PUSCH transmission opportunities scheduled by DCI format 0_1 / 0_2.

[0160] Otherwise, The UE can determine whether to send one or more PUSCH transmissions scheduled by DCI format 0_1 / 0_2 based on the mechanism mentioned in Embodiment 1, specifying either the first indicated joint / UL TCI state or the second indicated joint / UL TCI state. For example, it can use either the first indicated joint / UL TCI state or the second indicated joint / UL TCI state, or based on the second RRC parameter or the first DCI field.

[0161] Alternatively, the network entity can avoid performing one of the events mentioned above.

[0162] In some other implementations, if the RRC parameter txConfigThe network entity must configure the (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2 to conform to / share / apply the indicated joint / UL TCI state if the network entity configures the UE with the (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2. In this implementation, the UE can apply the same indicated joint / UL TCI state to conform to / share / apply the (only) SRS resource set associated with the CB (or NCB) to send one or more PUSCH transmission opportunities scheduled by DCI format 0_1 / 0_2.

[0163] In some other implementations, if the RRC parameter txConfig The UE determines, based on the indicated joint / DL TCI state for receiving a CORESET with a scheduled PDCCH, which will be applied to the PUSCH transmission timings scheduled by DCI formats 0_1 / 0_2, if the network entity has configured (only) one SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2. In one example, if the UE applies the first indicated joint / DL TCI state to receive a CORESET with a scheduled PDCCH, the UE applies the first indicated joint / UL TCI state to transmit the scheduled PUSCH transmission timing. In another example, if the UE applies the second indicated joint / DL TCI state to receive a CORESET with a scheduled PDCCH, the UE applies the second indicated joint / UL TCI state to transmit the scheduled PUSCH transmission timing. If a CORESET with a scheduling PDCCH is configured / indicated to be applied together with two indicated joint / DL TCI states, the UE can determine whether to use the first or second indicated joint / UL TCI state, or the indicated joint / UL TCI state with a lower TCI state ID.

[0164] In some other implementations, the UE determines whether to apply the first or second indicated joint / UL TCI state based on whether the control resource set (CORESET) with scheduled PDCCH conforms to / shares / applies at least one of the first or second indicated joint / DL TCI states. In some cases, if the CORESET with scheduled PDCCH is configured not to conform to / share / applies either or both indicated joint / DL TCI states, the UE can determine to use the first or second indicated joint / UL TCI state to transmit PUSCH transmissions scheduled by DCI format 0_1 / 0_2. In some other cases, if the CORESET with scheduled PDCCH is configured not to conform to / share / applies either indicated joint / DL TCI state, the UE can determine to transmit one or more PUSCH transmissions scheduled by DCI format 0_1 / 0_2, derived from the spatial transmission filter, based on the QCL assumptions or spatial reception parameters or SSB used to receive the CORESET with scheduled PDCCH.

[0165] In some other implementations, if the RRC parameter txConfig The UE determines, based on the location of the scheduled PDCCH (or PDCCH candidate), whether to apply the first indicated joint / UL TCI state or the second indicated joint / UL TCI state to the PUSCH scheduled by DCI format 0_1 / 0_2, the CB (or NCB) indicated by the network entity, and / or if the network entity configures a (only) SRS resource set associated with the CB (or NCB) of DCI format 0_1 / 0_2. In one example, the UE may determine whether to apply the first indicated joint / UL TCI state or the second indicated joint / UL TCI state to the PUSCH scheduled by DCI format 0_1 / 0_2 based on the starting control channel element (CCE) index for the scheduled PDCCH (or PDCCH candidate). Even-numbered starting CCE indices may correspond to the first indicated TCI state, and odd-numbered starting CCE indices may correspond to the second indicated TCI state.

[0166] The second signaling or mechanism (e.g., for operations 662, 762, 862, and 1062) can be implemented in the following embodiments to utilize the TCI selection field in DCI format 1_1 / 1_2 when no M-TRP PDSCH scheme / feature is configured / implemented.

[0167] In some implementations, the network entity can configure the UE to have a second DCI field in DCI format 1_1 / 1_2. The second DCI field can indicate which indicated joint / DL TCI state the UE is applied to receive PDSCH scheduled by DCI format 1_1 / 1_2. For example, the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both. In some cases, the second DCI field is a TCI selection field. The presence of the second DCI field can be determined by RRC parameters. tci-SelectionPresentIn-DCI Configure it.

[0168] In some implementations, network entities can configure RRC parameters to configure / implement M-TRP PDSCH schemes or features (e.g., SDM, FDM, TDM, SFN, or CJT). Network entities can configure different RRC parameters to configure / implement different M-TRP PDSCH schemes or features (e.g., SDM, FDM, TDM, SFN, or CJT).

[0169] In some implementations, the UE can receive or detect a scheduling DCI with DCI format 1_1 / 1_2 on the CORESET.

[0170] In some implementations, if a second DCI field exists in the network entity configuration DCI format 1_1 / 1_2, - If the network entity has not configured any RRC parameters for configuring / implementing the M-TRP PDSCH scheme or feature, or if the NW entity only configures or implements PDSCH-CJT, but the UE only supports one joint / DL TCI state for performing PDSCH-CJT, then the UE determines that the second DCI field is a one-bit field in DCI format 1_1 / 1_2. In such cases, the second DCI field can indicate either the first or second indicated joint / DL TCI state. - Otherwise, the UE determines that the second DCI field is a two-bit field in DCI format 1_1 / 1_2. In this case, the second DCI field may indicate the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both the first and second indicated joint / DL TCI states.

[0171] In some implementations, if a second DCI field exists in the network entity configuration DCI format 1_1 / 1_2, - If the network entity does not configure any RRC parameter for configuring / implementing the M-TRP PDSCH scheme or feature, or if the NW entity only configures or implements PDSCH-CJT, but the UE only supports one joint / DL TCI state for performing PDSCH-CJT, If so, the UE determines that the second DCI field is a one-bit field in DCI format 1_2. In this case, the second DCI field can indicate the combined / DL TCI state indicated by the first or second. The UE determines that the second DCI field is a two-bit field in DCI format 1_1. In this case, the second DCI field can indicate the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both the first and second indicated joint / DL TCI states. - Otherwise, the UE determines that the second DCI field is a two-bit field in DCI format 1_1 / 1_2. In this case, the second DCI field may indicate the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both the first and second indicated joint / DL TCI states.

[0172] In some implementations, if a second DCI field exists in the network entity configuration DCI format 1_1 / 1_2, and

[0173] If a network entity has not configured any RRC parameter for configuring / implementing the M-TRP PDSCH scheme or feature, or

[0174] If the NW entity only configures or implements PDSCH-CJT, but the UE only supports one joint / DL TCI state for performing PDSCH-CJT, - Then network entities can avoid indicating both the first joint / DL TCI state and the second joint / DL TCI state via the second DCI field, and / or - If the UE receives a second DCI field indicating both the first and second combined / DL TCI states, the UE can determine that this is an error condition, and / or - If the second DCI field indicates both the first and second combined / DL TCI states, the UE may not apply / use the instructions indicated by the second DCI field in the DCI. In some implementations, if the network entity does not configure any RRC parameter for configuring / implementing an M-TRPPDSCH scheme or feature (e.g., SDM, FDM, TDM, SFN, or CJT), or if the NW entity only configures or implements PDSCH-CJT, but the UE only supports one joint / DL TCI state for performing PDSCH-CJT, the network entity can avoid configuring a second DCI field. In other implementations, the network entity and UE can determine the presence of a second DCI field based on whether any of the M-TRPPDSCH schemes are configured / implemented and whether RRC parameters implementing a second DCI field are configured. Then, for PDSCH scheduled by DCI format 1_1 / 1_2, whether to apply the first indicated joint / DL TCI state or the second indicated joint / DL TCI state can be predefined or configured by additional RRC signaling.

[0175] Additional description

[0176] It should be noted that throughout this disclosure, a UE may have one or more of the following attributes or behaviors. These attributes or behaviors of the UE may also imply associated attributes or behaviors of network entities.

[0177] ● The UE can be configured and / or served by network entities in the serving cell.

[0178] ● The UE can (be configured) communicate with network entities in the serving cell.

[0179] ● The UE can be configured by a network entity to include one or more serving cells that may include the serving cell.

[0180] ● The UE can be activated or instructed by a network entity to activate one or more serving cells that may include the serving cell.

[0181] ● The UE can be configured and / or instructed by a network entity to use one or more BWPs. The UE can be instructed and / or configured (in the serving cell) by a network entity to use BWPs.

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

[0183] In some cases, the BWP can be referred to as the active BWP.

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

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

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

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

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

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

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

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

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

[0193] It should be noted that throughout this disclosure, the association of an SRS resource set with a CB in DCI format 0_1 ​​can be interpreted as meaning or referred to as the SRS resource set being generated by... srs-ResourceSetToAddModList Configuration, and with the value " codebook of use Associated. It should be noted that throughout this disclosure, the association of an SRS resource set with an NCB of DCI format 0_1 ​​can be interpreted as, or referred to as, the SRS resource set being associated with, by... srs-ResourceSetToAddModList Configuration, and with the value " nonCodeBook of use Related.

[0194] It should be noted that throughout this disclosure, the association of an SRS resource set with a CB in DCI format 0_2 can be interpreted as meaning or referred to as the SRS resource set being provided by... srs-ResourceSetToAddModListDCI-0-2 Configuration, and with the value " codebook of use Associated. It should be noted that throughout this disclosure, the association of an SRS resource set with an NCB of DCI format 0_2 can be interpreted as, or referred to as, the SRS resource set being associated with, by... srs-ResourceSetToAddModListDCI-0-2 Configuration, and with the value " nonCodeBook of use Related.

[0195] It should be noted that throughout this disclosure, the configuration or indication by a network entity of a UE to operate in S-TRP mode in a serving cell or BWP, or the operation of a UE in S-TRP mode for a serving cell or BWP, may mean or be referred to as one of the following: - The network entity has not configured or indicated a TRP identifier or TRP-related index to any channel or RS in the serving cell or BWP; and / or - A network 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 network entity sends / receives a transmission, (only) one TRP identifier or TRP-related index is configured or indicates or relates to the transmission or is applied to the beam / TCI state of the transmission.

[0196] It should be noted that throughout this disclosure, the configuration or indication by a network entity of a UE to operate in M-TRP mode in a serving cell or BWP, or the operation of a UE in M-TRP mode in a serving cell or BWP, may mean or be referred to as one of the following: - A network 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 - A network 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 an application to at least one channel or RS in the serving cell or BWP or another TRP identifier or TRP-related index associated with that at least one channel or RS; and / or - When a UE or network entity transmits / receives a transmission, more than one TRP identifier or TRP-related index is configured, indicates, relates to, or is applied to the beam / TCI state of the transmission; and / or - Network entities configure higher-layer parameters to the 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 from the serving cell or BWP from the network entity (e.g., PDSCH TCI activates MAC-CE), which indicates that at least one TCI code point is mapped to two TCI states.

[0197] It should be noted that throughout this disclosure, the configuration or indication by a network entity of a UE to operate in (M-TRP) M-DCI mode in a serving cell or BWP, or the operation of a UE in (M-TRP) M-DCI mode in a serving cell or BWP, may mean or be referred to as one of the following: - A network 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 - A network 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 that at least one channel or RS, and / or - Network entities configure higher-layer parameters to the UE PDCCH-Config This higher-level parameter includes the serving cell or BWP. ControlResourceSet In coresetPoolIndex Two different values.

[0198] It should be noted that throughout this disclosure, the configuration or indication by a network entity of a UE to operate in (M-TRP) S-DCI mode in a serving cell or BWP, or the operation of a UE in (M-TRP) S-DCI mode for a serving cell or BWP, may mean or be referred to as one of the following: - When a UE or network entity transmits / receives a transmission, more than one TRP identifier or TRP-related index is configured, indicates, relates to, or is applied to the beam / TCI state of the transmission; and / or - The UE receives a MAC-CE from the serving cell or BWP (e.g., PDSCH TCI activated MAC-CE) from a network entity. The 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).

[0199] 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 DL TCI state / UL TCI state pair, wherein the DL TCI state and the pair are associated with a different TRP or a different TRP identifier (value).

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

[0201] Figure 11 A flowchart of a wireless communication method 1100 at the UE is shown. (Reference) Figure 1A , Figure 1B , Figures 3 to 10 and Figure 13 The method can be performed by UE 102, UE equipment 1302, etc., which may include memories 1326', 1306', 1316 and may correspond to the entire UE 102 or the entire UE equipment 1302, or components of UE 102 or UE equipment 1302 (e.g., BFR post-update component 1110) (such as wireless baseband processor 1326 and / or application processor 1306).

[0202] like Figure 11 As shown, method 1100 begins by optionally receiving 1120 configuration for MIMO operation from the network entity (similar to...). Figure 3 , Figure 6 , Figure 9 and Figure 10 The corresponding operations are 320, 622, 920, and 1022.

[0203] The UE receives indications from the network entity of more than 1130 Joint Transport Configuration Indicator (TCI) states, multiple downlink (DL) TCI states, or multiple uplink (UL) TCI states (multiple joint / DL / UL TCI states) (similar to...). Figure 3 Operation 330 and Figure 6 Operation 632).

[0204] The UE receives 1150 CORESETs (similar to scheduling information) from the network entity. Figure 3 Operation 350 and Figure 6 Operation 652).

[0205] The UE communicates with network entities based on scheduling information and multiple joint / DL / UL TCI states 1175, without needing to receive indications of probe reference signals (SRS) for uplink transmission or configurations for implementing multiple transmit receiver point (M-TRP) operation (similar to...). Figure 3 Operation 370 and Figure 6 Operation 372).

[0206] In various respects, the method further includes receiving from a network entity a configuration for multiple-input multiple-output (MIMO) operation, the configuration including a radio resource control (RRC) message configuring at least one of the following: (1) whether the uplink transmission is a codebook-based uplink transmission or a non-codebook-based uplink transmission, and the number of SRS resource sets used for the uplink transmission; or (2) a downlink control information (DCI) field in the DCI format relating to beam selection or TCI state selection for downlink reception.

[0207] In some cases, the configuration for MIMO operation further includes the configuration of the number of SRS resource sets associated with the DCI field in DCI format 0_1 ​​or DCI format 0_2. In some cases, the number of SRS resource sets is one, and the DCI field does not appear or further indicate which of the multiple combined TCI states or multiple UL TCI states (multiple combined / UL TCI states) will be applied to the uplink transmission to the network entity, and the configuration for MIMO operation is for implementing or indicating single transmit receive point (S-TRP) operation for the timing of sending PUSCH transmissions.

[0208] In some cases, the method further includes determining a beam from a plurality of joint / UL TCI states for sending PUSCH transmission timing to a network entity based on at least one of the following: (1) a predetermined joint / UL TCI state for uplink transmission; (2) a joint / UL TCI state configured by RRC parameters other than the received configuration; (3) a joint / UL TCI state indicated by the bit value of the SRS resource set indicator field in the received CORESET DCI; (4) a joint / UL TCI state configured by the network entity for transmitting the number of SRS resource sets associated with the codebook or non-codebook of DCI format 0_1 ​​or DCI format 0_2; (5) a joint TCI state corresponding to the downlink TCI state or QCL assumption for receiving the physical downlink control channel (PDCCH); or (6) a joint TCI state determined based on the start control channel element (CCE) index of the PDCCH timing.

[0209] In various respects, the configuration for MIMO operation further includes a configuration of a TCI selection field associated with TCI selection in DCI format 1_1 or DCI format 1_2 for applying the TCI selection field in the DCI of the received CORESET at the timing of receiving the Physical Downlink Shared Channel (PDSCH).

[0210] In some cases, the configuration for MIMO operation includes Radio Resource Control (RRC) parameters, which indicate whether the UE is configured or implemented for M-TRP operation.

[0211] In some cases, the RRC parameters indicate that the UE is configured and implemented for M-TRP operation. The method may further include deriving the receive beam based on information in the TCI selection field, which includes bit values ​​in the DCI containing the CORESET; and receiving the PDSCH timing based on that receive beam.

[0212] In some cases, the RRC parameter indicates that the UE is not configured or implemented for M-TRP operation. The method may further include determining whether a TCI selection field exists in the CORESET's scheduling DCI; if a TCI selection field is determined to exist, identifying the bit width of its TCI selection; and deriving the receive beam.

[0213] In some cases, the method further includes deriving the received beam based on at least one of the following: (1) a combined / DL TCI state indicated by the bit value of the TCI selection field in DCI format 1_1 or DCI format 1_2; (2) a combined / DL TCI state indicated by a one-bit field in DCI format 1_2 or by two-bit fields in DCI format 1_1; (3) a combined / DL TCI state configured by RRC parameters other than configuration; or (4) a predefined combined / DL TCI state.

[0214] In all respects, M-TRP operation includes at least one of the following: Spatial Domain Multiplexing (SDM) PDSCH; Frequency Domain Multiplexing (FDM) PDSCH; Time Domain Multiplexing (TDM) PDSCH; Single Frequency Network (SFN) PDSCH; or Coherent Joint Transmission (CJT) PDSCH.

[0215] Figure 12 This is a flowchart of method 1200 for wireless communication at a network entity. Method 1200 and... Figure 11 Method 1100 is complementary. (Reference) Figure 1A , Figure 1B , Figures 3 to 10 ,and Figure 14 Method 1200 can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, RU processor 1406, DU processor 1426, CU processor 1446, etc.). One or more network entities 104 may include memories 1406' / 1426' / 1446', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1406, DU processor 1426, or CU processor 1446).

[0216] Method 1200 begins by optionally sending 1220, the configuration for MIMO operation, to the UE (similar to...). Figure 3 Operation 320 and Figure 6 Operation 622).

[0217] The network entity sends the UE more than 1230 indications of the Joint Transport Configuration Indicator (TCI) status, multiple downlink (DL) TCI statuses, or multiple uplink (UL) TCI statuses (multiple joint / DL / UL TCI statuses) (similar to...). Figure 3 Operation 330 and Figure 6 Operation 632).

[0218] The network entity sends a 1250 CORESET containing scheduling information to the UE (similar to...). Figure 3 Operation 350 and Figure 6 Operation 652).

[0219] The network entity communicates with the UE based on scheduling information and multiple joint / DL / UL TCI states 1275, without sending indications of probe reference signals (SRS) for uplink transmission or configurations for implementing multiple transmit receiver point (M-TRP) operation (similar to...). Figure 3 Operation 370 and Figure 6 Operation 372).

[0220] like Figure 13 The UE equipment 1302 described herein can perform method 1100. For example... Figure 14 One or more network entities (or BSs) 104 described herein may execute method 1200.

[0221] Figure 13 This is a diagram 1300 illustrating an example of a hardware implementation for UE device 1302. UE device 1302 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1302 may include an application processor 1306, which may have on-chip memory 1306'. In this example, application processor 1306 may be coupled to a secure digital (SD) card 1308 and / or a display 1310. Application processor 1306 may also be coupled to a sensor module 1312, a power supply 1314, an additional memory module 1316, a camera 1318, and / or other related components. For example, sensor module 1312 may control a barometer / altimeter, motion sensors (such as an inertial management unit (IMU)), a gyroscope, an accelerometer, a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.

[0222] The UE equipment 1302 may further include a wireless baseband processor 1326, which may be referred to as a modem. The wireless baseband processor 1326 may have on-chip memory 1326'. Together with and similarly to the application processor 1306, the wireless baseband processor 1326 may also be coupled to a sensor module 1312, a power supply 1314, an additional memory module 1316, a camera 1318, and / or other related components. The wireless baseband processor 1326 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1320 and / or one or more transceivers 1330 (e.g., wireless RF transceivers).

[0223] Within one or more transceivers 1330, the UE equipment 1302 may include a Bluetooth module 1332, a WLAN module 1334, an SPS module 1336 (e.g., a GNSS module), and / or a cellular module 1338. The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include a dedicated antenna and / or utilize antenna 1340 for communication with one or more other nodes. For example, UE equipment 1302 can communicate with another UE 102 (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1330 and antenna 1340, wherein network entity 104 may correspond to a base station or a unit of a base station (such as RU 1013, DU 1014 or CU 110).

[0224] The wireless baseband processor 1326 and application processor 1306 may each include computer-readable media / memory 1326' and 1306', respectively. An additional memory module 1316 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1326', 1306', and 1316 may be non-transitory. The wireless baseband processor 1326 and application processor 1306 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1326', 1306', and 1316. When executed by the wireless baseband processor 1326 / application processor 1306, this software causes the wireless baseband processor 1326 / application processor 1306 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 1326 / application processor 1306 during software execution. The wireless baseband processor 1326 / application processor 1306 may be a component of UE 102. UE equipment 1302 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1326 and / or the application processor 1306. In other examples, UE equipment 1302 may be the entire UE 102 and may include additional modules for equipment 1302.

[0225] like Figure 1A and Figure 1B The discussion and references in Figures 3 to 10Implemented, the beamforming component 140 is configured to receive indications of multiple joint TCI states, multiple DL TCI states, or multiple UL TCI states (multiple joint / DL / UL TCI states) from network entity 104; receive a control resource set (CORESET) including scheduling information; and communicate with the network entity based on the scheduling information and the multiple joint / DL / UL TCI states without receiving indications of a sounding reference signal (SRS) resource set for uplink transmission or without receiving configuration for implementing multiple transmit receiver point (M-TRP) operation.

[0226] Beamforming component 140 may be located within application processor 1306 (e.g., at 140a), wireless baseband processor 1326 (e.g., at 140b), or both application processor 1306 and wireless baseband processor 1326. Beamforming 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 implementation by one or more processors, or a combination thereof.

[0227] Figure 14 This is a diagram 1400 illustrating an example of a hardware implementation for 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 functionality. The one or more network entities 104 may include at least one of RU 106, DU 1014, or CU 110, or may correspond to at least one of these. CU 110 may include a CU processor 1446, which may have on-chip memory 1446'. In some aspects, CU 110 may further include an additional memory module 1456 and / or a communication interface 1448, both of which may be coupled to the CU processor 1446. CU 110 may communicate with DU 1014 via a midhaul link 162 (such as an F1 interface between the communication interface 1448 of CU 110 and the communication interface 1428 of DU 1014).

[0228] DU 1014 may include a DU processor 1426, which may have on-chip memory 1426'. In some aspects, DU 1014 may further include an additional memory module 1436 and / or a communication interface 1428, both of which may be coupled to the DU processor 1426. DU 1014 may communicate with RU 106 via a frontlink 160 between DU 1014's communication interface 1428 and RU 106's communication interface 1408.

[0229] RU 106 may include an RU processor 1406, which may have on-chip memory 1406'. In some aspects, RU 106 may further include an additional memory module 1416, a communication interface 1408, and one or more transceivers 1430, all of which may be coupled to the RU processor 1406. RU 106 may further include an antenna 1440, which may be coupled to one or more transceivers 1430, enabling RU 106 to communicate with UE 102 via the antenna 1440 through one or more transceivers 1430.

[0230] On-chip memories 1406', 1426', 1446' and additional memory modules 1416, 1436, 1456 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1406, 1426, 1446 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1406, 1426, 1446, the software causes the processor 1406, 1426, 1446 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1406, 1426, 1446 during software execution. In the example, the beamforming 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 1014; at each of CU 110, DU 1014, and RU 106; at DU 1014; at both DU 1014 and RU 106; or at RU 106.

[0231] Beamforming component 150 can perform various operations and signaling (such as) according to the examples provided herein. Figures 3 to 10 and Figure 12 The beamforming components 150a to 150c may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors 1406, 1426, 1446 configured to perform the stated process / algorithm, and / or stored in a computer-readable medium for use by one or more processors 1406, 1426, 1446, or a combination thereof.

[0232] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is an illustration 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 exemplary / optional elements in the illustrations. 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.

[0233] The detailed descriptions presented herein, in conjunction with accompanying drawings, illustrate various configurations and do not represent the only configuration 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.

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

[0235] 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 can 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.

[0236] 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 computer-accessible instructions or data structures. The storage medium can be any available medium that is computer-accessible.

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

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

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

[0240] 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, phrases such as "when" do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply 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 may 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.

[0241] 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 can be interpreted as a set of elements having a number of one or more elements.

[0242] 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 following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures 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 figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).

[0243] 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".

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

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

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

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

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

[0249] It should be noted that some or all of the following terms and assumptions may be used below. A BS may include a network central unit or network node in an NR for controlling one or more TRPs associated with one or more cells. Communication between the BS and the TRP is via fronthaul. The BS may be referred to as a Central Unit (CU), eNB, gNB, or NodeB. A TRP may include: a transmit and receive point that provides network coverage and communicates directly with the UE. A TRP may be referred to as a Distributed Unit (DU) or network node. A cell may include one or more associated TRPs; for example, the coverage of a cell consists of the coverage of all associated TRPs. A cell is controlled by a BS or network entity. A cell may be referred to as a TRP group (TRPG). A serving beam may include a beam generated by a network node (e.g., a TRP) and configured to communicate with the UE (e.g., for transmission and / or reception). A candidate beam for the UE is a candidate for the serving beam. The serving beam may or may not be a candidate beam.

[0250] 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. Furthermore, in some cases, the user device can be embedded in an electronic system (such as the main unit of a vehicle 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.

[0251] 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 way. A hardware module may include a dedicated circuit system or logic that is permanently 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 a circuit system (e.g., included within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

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

[0253] 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 may be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” shall 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.) may be construed as “at least based on A”.

[0254] Example

[0255] Example 1 is a method for wireless communication by a user equipment (UE), the method comprising: Receive configuration for multiple-input multiple-output (MIMO) operations from network entities; Receive multiple joint downlink (DL) (joint / DL) Transport Configuration Indicator (TCI) statuses, multiple joint uplink (UL) (joint / UL) TCI statuses, or both, from the network entity; Receives a control resource set (CORESET) including scheduling information; and Based on the scheduling information and the multiple joint / DL or joint / UL TCI states, the network entity communicates without receiving an indication of a probe reference signal (SRS) resource set for uplink transmission or a configuration for implementing multiple transmit receiver point (M-TRP) operation.

[0256] Example 2 is the method as described in Example 1, wherein the configuration for MIMO operation includes a Radio Resource Control (RRC) message configuring at least one of the following: (1) Whether the uplink transmission from the UE to the network entity is a codebook-based uplink transmission or a non-codebook-based uplink transmission, and the number of SRS resource sets used for the uplink transmission; or (2) DCI fields in the downlink control information (DCI) format related to beam selection or TCI state selection for downlink reception.

[0257] Example 3 is the method as described in Example 2, wherein the configuration for MIMO operation further includes the configuration of the number of SRS resource sets associated with the DCI fields in DCI format 0_1 ​​or DCI format 0_2.

[0258] Example 4 is the method as described in Example 3, wherein the number of SRS resource sets is two, and wherein the configuration for MIMO operation is an M-TRP operation for being implemented or indicated for the timing of sending Physical Uplink Shared Channel (PUSCH) transmissions.

[0259] Example 5 is the method described in Example 4, further including: The beam is obtained from the plurality of joint / UL TCI states based on the SRS resource set indicator field that identifies the beam by the number of bits, and the communication with the network entity includes sending the PUSCH transmission timing using the obtained beam.

[0260] Example 6 is the method as described in Example 3, wherein the number of SRS resource sets is one, and the DCI field does not appear or further indicate which of the plurality of combined / UL TCI states will be applied to the uplink transmission to the network entity, and wherein the configuration for the MIMO operation is for a single transmit receive point (TRP) operation that is implemented or indicated for the timing of sending PUSCH transmissions.

[0261] Example 7 is the method as described in Example 6, further comprising: The beam is determined from the plurality of joint / UL TCI states for the timing of sending PUSCH transmissions to the network entity based on at least one of the following: (1) Predetermined joint / UL TCI status for uplink transmission; (2) The combined / UL TCI status configured by RRC parameters other than the received configuration; (3) The combined / UL TCI status indicated by the bit value of the SRS resource set indicator field in the received CORESET DCI; (4) The network entity is configured to send the number of joint / UL TCI states of the SRS resource set associated with the codebook or non-codebook of DCI format 0_1 ​​or DCI format 0_2; (5) The unified / joint TCI state corresponding to the downlink TCI state or QCL assumption used for receiving the Physical Downlink Control Channel (PDCCH); or (6) The unified / joint TCI state determined based on the starting control channel element (CCE) index of the PDCCH timing.

[0262] Example 8 is the method as described in Example 2, wherein the configuration for MIMO operation further includes a configuration of a TCI selection field associated with TCI selection in DCI format 1_1 or DCI format 1_2 for applying the TCI selection field in the DCI of the received CORESET at the timing of receiving the Physical Downlink Shared Channel (PDSCH) of one of the plurality of combined / DL TCI states.

[0263] Example 9 is the method as described in Example 8, wherein the configuration for MIMO operation includes a Radio Resource Control (RRC) parameter that indicates whether the UE is configured or implemented for the M-TRP operation.

[0264] Example 10 is a method as described in Example 9, wherein the RRC parameter indicates that the UE is configured and implemented for the M-TRP operation, and the method further includes: The receive beam is derived based on the information in the TCI selection field, including bit values, of the DCI in the CORESET; and The timing of receiving the PDSCH is based on the receiving beam.

[0265] Example 11 is a method as described in Example 9, wherein the RRC parameter indicates that the UE is not configured or implemented for the M-TRP operation, and the method further includes: Determine whether the CORESET's scheduling DCI contains a TCI selection field; When the existence of the TCI selection field is determined, the bit width of the TCI selection is identified; and The receiving beam is obtained.

[0266] Example 12 is a method as described in Example 11, further comprising: The received beam is derived based on at least one of the following: (1) The combined / DLTCI status indicated by the bit value of the TCI selection field in DCI format 1_1 or DCI format 1_2; (2) The combined / DL TCI status indicated by a one-bit field in DCI format 1_2 or by a two-bit field in DCI format 1_1; (3) The joint / DL TCI state configured by RRC parameters other than those described above; or (4) Predefined joint / DL TCI state.

[0267] Example 13 is a method as described in any one of Examples 1 to 12, wherein the M-TRP operation includes at least one of the following: Spatial Domain Multiplexing (SDM) PDSCH; Frequency Domain Multiplexing (FDM) PDSCH; Time-Domain Multiplexing (TDM) PDSCH; Single-Frequency Network (SFN) PDSCH; or Coherent Joint Transmission (CJT) PDSCH.

[0268] Example 14 is a method for wireless communication by a network entity, the method comprising: Send the configuration for multiple-input multiple-output (MIMO) operation to the user equipment (UE); Send to the UE multiple joint downlink (DL) (joint / DL) transmission configuration indicator (TCI) statuses, multiple joint uplink (UL) (joint / UL) TCI statuses, or both; Sending a control resource set (CORESET) including scheduling information to the user equipment (UE); and Based on the scheduling information and the multiple combined / DL or combined / UL TCI states, the system communicates with the UE without sending an indication of a probe reference signal (SRS) resource set for uplink transmission or without sending a configuration for implementing multiple transmit receiver point (M-TRP) operation.

[0269] Example 15 is the method as described in Example 14, wherein the configuration for the MIMO operation includes a Radio Resource Control (RRC) message configuring at least one of the following: (1) Whether the uplink transmission from the UE to the network entity is a codebook-based uplink transmission or a non-codebook-based uplink transmission, and the number of SRS resource sets used for the uplink transmission; or (2) Downlink Control Information (DCI) field in the DCI format related to beam selection for downlink reception.

[0270] Example 16 is the method as described in Example 15, wherein the configuration for the MIMO operation further includes the configuration of the number of SRS resource sets associated with the DCI fields in DCI format 0_1 ​​or DCI format 0_2.

[0271] Example 17 is the method as described in Example 16, wherein the number of SRS resource sets is two, and wherein the configuration for the MIMO operation is an M-TRP operation for configuring or indicating the timing of receiving Physical Uplink Shared Channel (PUSCH) transmissions from the UE.

[0272] Example 18 is the method as described in Example 17, wherein the communication with the UE includes receiving the PUSCH transmission timing using a beam derived from the plurality of joint / UL TCI states based on an SRS resource indicator field that identifies the beam by the number of bits.

[0273] Example 19 is the method as described in Example 16, wherein the number of SRS resource sets is one, and the DCI field does not appear or further indicate which of the plurality of combined / UL TCI states will be applied to the uplink transmission to the network entity, and wherein the configuration for the MIMO operation is for a single transmit receive point (TRP) operation that is implemented or indicated for the timing of sending PUSCH transmissions.

[0274] Example 20 is the method as described in Example 19, further comprising: Avoid sending at least one of the following: DCI format 0_1 ​​or DCI format 0_2; A Media Access Control (MAC) control element (CE) capable of activating two combined / UL TCI states or mapping two combined / UL TCI states to TCI code points; The instruction indicates that when a TCI is sent to activate MAC-CE, the instruction activates at least two joint / UL TCI states or maps at least two joint / UL TCI states to TCI code points; or DCI, which has TCI field code points indicating two combined / UL TCI states.

[0275] Example 21 is the method as described in Example 15, wherein the configuration for MIMO operation further includes the configuration of the TCI selection field in DCI format 1_1 or DCI format 1_2.

[0276] Example 22 is the method as described in Example 21, wherein the configuration for the MIMO operation includes Radio Resource Control (RRC) parameters that indicate whether the UE is configured or implemented for the M-TRP operation.

[0277] Example 23 is a method as described in Example 22, wherein the RRC parameter indicates that the UE is not configured or implemented for the M-TRP operation, and the method further includes at least one of the following: Avoid indicating two combined / DL TCI states via the TCI selection field; or Avoid configuring the TCI selection field in DCI.

[0278] Example 24 is a method as described in Example 23, wherein the method further includes avoiding indicating “10” in the TCI selection field.

[0279] Example 25 is a piece of equipment that includes: One or more radio frequency (RF) modems; A processor, the processor being coupled to the one or more RF modems; and At least one memory storing executable instructions for manipulating at least one of the processor or the one or more RF modems to perform the method as described in any one of Examples 1 to 24.

[0280] Example 26 is a method for a user equipment (UE), the method comprising: Receive one or more RRC parameters to configure whether to use codebook-based (CB) uplink (UL) transmission or non-codebook-based (NCB) uplink (UL) transmission, and / or one or more SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2, which is related to the presence of the first DCI field in DCI format 0_1 / 0_2; Receive one or more RRC parameters to configure the presence of a second DCI field in DCI format 1_1 / 1_2; Receive the first indication of the combined / DL / UL TCI status and / or the second indication of the combined / DL / UL TCI status; The scheduling DCI with DCI format 0_1 / 0_2 or DCI format 1_1 / 1_2 is detected on CORESET. Therefore, the scheduling DCI is decoded based on whether the S-TRP operation or the M-TRP operation is configured / implemented / indicated for the PUSCH transmission timing or PDSCH reception timing scheduled by the scheduling DCI. Based on the determination, the transmit beam or receive beam is obtained; Based on the obtained transmit or receive beam, the scheduled PUSCH transmission timing or PDSCH reception timing is determined.

[0281] Example 27 is a method as described in Example 26, wherein: If the scheduling DCI format is DCI format 0_1 / 0_2, then determining whether an S-TRP operation or an M-TRP operation is configured / implemented / indicated for PUSCH further includes: If the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2 is two, then the M-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing. If the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2 is one, then the S-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing.

[0282] Example 28 is a method as described in Example 26, wherein: If the scheduling DCI format is DCI format 1_1 / 1_2, then determining whether an S-TRP operation or an M-TRP operation is configured / implemented / indicated for PDSCH further includes: If the UE receives any RRC parameter for configuring / implementing MTRP PDSCH features / schemes, then the M-TRP operation is configured / implemented / indicated for the scheduled PDSCH transmission timing; If the UE does not receive any RRC parameter for configuring / implementing MTRP PDSCH features / schemes, then S-TRP operation is configured / implemented / indicated for the scheduled PDSCH transmission timing.

[0283] Example 29 is the method described as in Example 27, wherein: The determination of the transmission beam further includes: If the M-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing, the UE determines that the first DCI field exists in the scheduling DCI and that the first DCI field includes two bits, and the UE derives the transmission beam based on the first DCI field. If the S-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing, the UE uses the first signaling / mechanism to derive the transmission beam.

[0284] Example 30 is the method described as in Example 28, wherein: The determination of the receiving beam based on the above further includes: If the M-TRP operation is configured / implemented / indicated for the scheduled PDSCH transmission timing, the UE determines that the second DCI field exists in the scheduled DCI and that the second DCI field includes two bits, and the UE derives the receive beam based on the second DCI field; If the S-TRP operation is configured / implemented / indicated for the scheduled PDSCH transmission timing, the UE determines whether the second DCI field exists in the scheduled DCI and / or the bit width of the second DCI field (if it exists) based on the second signaling / mechanism, and the UE derives the receive beam based on the second DCI field (if it exists) and / or the second signaling / mechanism.

[0285] Example 31 is the method described in Example 29, wherein: The first signaling / mechanism includes one of the following: the first indicated joint / UL TCI state, the second indicated joint / UL TCI state, the indicated joint / UL TCI state configured by additional RRC parameters, the indicated joint / UL TCI state indicated by the first DCI field including one bit, or the indicated joint / UL TCI state configured to be applied to the transmission of a configured SRS resource set associated with a CB / NCB of DCI format 0_1 / 0_2.

[0286] Example 32 is the method described as in Example 30, wherein: The second signaling / mechanism includes one of the following: an indicated joint / DL TCI state indicated by the second DCI field including one bit, an indicated joint / DL TCI state indicated by the second DCI field including two bits with reserved code points, or an indicated joint / DL TCI state configured by another additional RRC parameter.

[0287] Example 33 is the method described as in Example 26, wherein: The first DCI field is the SRS resource indicator field.

[0288] Example 34 is the method described as in Example 26, wherein: The second DCI field is the TCI selection field.

[0289] Example 35 is the method described as in Example 28, wherein: The MTRP PDSCH feature / scheme is one of SDM PDSCH, FDM PDSCH, TDM PDSCH, SFN PDSCH or CJTPDSCH.

[0290] Example 36 is a method for a network (NW) entity, the method comprising: Send one or more RRC parameters to configure whether to use codebook-based (CB) uplink (UL) transmission or non-codebook-based (NCB) uplink (UL) transmission, and / or one or more SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2, which is related to the presence of the first DCI field in DCI format 0_1 / 0_2; Send one or more RRC parameters to configure the presence of a second DCI field in DCI format 1_1 / 1_2; Send an indication of the first indicated joint / DL / UL TCI status and / or the second indicated joint / DL / UL TCI status; The scheduled DCI with DCI format 0_1 / 0_2 or DCI format 1_1 / 1_2 is transmitted on CORESET. Therefore, the information in the scheduling DCI is indicated based on whether the S-TRP operation or the M-TRP operation is configured / implemented / indicated for the PUSCH transmission timing or PDSCH reception timing scheduled by the scheduling DCI. Based on the determination, the receiving beam or the transmitting beam is obtained; Based on the obtained receive or transmit beam, the scheduled PUSCH transmission timing or PDSCH reception timing is determined.

[0291] Example 37 is a method as described in Example 36, wherein: If the scheduling DCI format is DCI format 0_1 / 0_2, then determining whether an S-TRP operation or an M-TRP operation is configured / implemented / indicated for PUSCH further includes: If the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2 is two, then the M-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing. If the number of configured SRS resource sets associated with the CB / NCB of DCI format 0_1 / 0_2 is one, then the S-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing.

[0292] Example 38 is a method as described in Example 36, wherein: If the scheduling DCI format is DCI format 1_1 / 1_2, then determining whether an S-TRP operation or an M-TRP operation is configured / implemented / indicated for PDSCH further includes: If the NW entity sends any RRC parameter for configuring / implementing MTRP PDSCH features / schemes, then the M-TRP operation is configured / implemented / indicated for the timing of PDSCH transmission; If the NW entity does not send any RRC parameter for configuring / implementing MTRP PDSCH features / schemes, then the S-TRP operation is configured / implemented / indicated for the timing of PDSCH transmission.

[0293] Example 39 is the method described as in Example 37, wherein: The determination of the receiving beam based on the above further includes: If the M-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing, the NW entity indicates the first DCI field, which includes two bits, in the scheduled DCI, and the NW entity derives the receive beam based on the first DCI field. If the S-TRP operation is configured / implemented / indicated for the scheduled PUSCH transmission timing, the NW entity uses the first signaling / mechanism to derive the receive beam.

[0294] Example 40 is the method described as in Example 38, wherein: The determination of the transmission beam further includes: If the M-TRP operation is configured / implemented / indicated for the scheduled PDSCH reception timing, the NW entity indicates the second DCI field, which includes two bits, in the scheduled DCI, and the NW entity derives the transmit beam based on the second DCI field. If the S-TRP operation is configured / implemented / indicated for the scheduled PDSCH reception timing, the NW entity determines whether to indicate the second DCI field in the scheduled DCI, and / or determines the bit width of the second DCI field (if indicated) based on the second signaling / mechanism, and the NW entity derives the transmit beam based on the second DCI field (if indicated) and / or the second signaling / mechanism.

[0295] Example 41 is the method described in Example 39, wherein: The first signaling / mechanism includes one of the following: the first indicated joint / UL TCI state, the second indicated joint / UL TCI state, the indicated joint / UL TCI state configured by additional RRC parameters, the indicated joint / UL TCI state indicated by the first DCI field including one bit, or the indicated joint / UL TCI state configured to be applied to the transmission of a configured SRS resource set associated with a CB / NCB of DCI format 0_1 / 0_2.

[0296] Example 42 is the method described as in Example 40, wherein: The second signaling / mechanism includes one of the following: an indicated joint / DL TCI state indicated by the second DCI field including one bit, an indicated joint / DL TCI state indicated by the second DCI field including two bits with reserved code points, or an indicated joint / DL TCI state configured by another additional RRC parameter.

[0297] Example 43 is the method described as in Example 36, wherein: The first DCI field is the SRS resource indicator field.

[0298] Example 44 is the method described as in Example 36, wherein: The second DCI field is the TCI selection field.

[0299] Example 45 is a method as described in Example 38, wherein: The MTRP PDSCH feature / scheme is one of SDM PDSCH, FDM PDSCH, TDM PDSCH, SFN PDSCH or CJTPDSCH.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: Receive from network entities (330) multiple indications of combined transport configuration indicator (TCI) status, multiple downlink DL TCI status, or multiple uplink UL TCI status (multiple combined / DL / UL TCI status); Receive (350) a control resource set CORESET including scheduling information; and Based on the scheduling information and the multiple joint / DL / UL TCI states, the network entity communicates (370) without receiving an indication of the probe reference signal SRS resource set for uplink transmission or without receiving a configuration for implementing multiple transmit receiver point M-TRP operation.

2. The method of claim 1, further comprising receiving configuration from the network entity for multiple-input multiple-output (MIMO) operation, the configuration including a Radio Resource Control (RRC) message configuring at least one of the following: (1) Whether the uplink transmission is codebook-based or non-codebook-based, and the number of SRS resource sets used for said uplink transmission; or (2) DCI fields in the downlink control information (DCI) format related to beam selection or TCI state selection for downlink reception.

3. The method of claim 2, wherein the configuration for MIMO operation further includes the configuration of the number of SRS resource sets associated with the DCI fields in DCI format 0_1 ​​or DCI format 0_2.

4. The method of claim 3, wherein the number of SRS resource sets is one and the DCI field does not appear or further indicate which of the plurality of combined TCI states or the plurality of UL TCI states (the plurality of combined / UL TCI states) will be applied to the uplink transmission of the network entity, and wherein the configuration for the MIMO operation is for a single transmit receiver point S-TRP operation implemented or indicated for the timing of sending PUSCH transmissions.

5. The method of claim 4, further comprising: The beam is determined from the plurality of joint / UL TCI states for the timing of sending PUSCH transmissions to the network entity based on at least one of the following: (1) Predetermined joint / UL TCI status for uplink transmission; (2) The combined / UL TCI status configured by RRC parameters other than the received configuration; (3) The combined / UL TCI status indicated by the bit value of the SRS resource set indicator field in the received CORESET DCI; (4) The number of joint / UL TCI states configured by the network entity for sending SRS resource sets associated with codebooks or non-codebooks of DCI format 0_1 ​​or DCI format 0_2; (5) The joint TCI state corresponding to the downlink TCI state or QCL assumption used for receiving the physical downlink control channel (PDCCH); or (6) The joint TCI state determined based on the CCE index of the starting control channel element of the PDCCH timing.

6. The method of claim 2, wherein the configuration for MIMO operation further includes a configuration of a TCI selection field associated with TCI selection in DCI format 1_1 or DCI format 1_2 for applying one of the plurality of joint TCI states or the plurality of DL TCI states (the plurality of joint / DL TCI states) to receive the Physical Downlink Shared Channel (PDSCH) timing, wherein the selection field in the DCI of the CORESET is received.

7. The method of claim 6, wherein the configuration for MIMO operation includes Radio Resource Control (RRC) parameters, the RRC parameters indicating whether the UE is configured or implemented for the M-TRP operation.

8. The method of claim 7, wherein the RRC parameter indicates that the UE is configured and implemented for the M-TRP operation, and the method further comprises: The receive beam is derived based on the information in the TCI selection field, which includes bit values, in the DCI of the CORESET; as well as The timing of receiving the PDSCH is based on the receiving beam.

9. The method of claim 7, wherein the RRC parameter indicates that the UE is not configured or implemented for the M-TRP operation, and the method further comprises: Determine whether the CORESET's scheduling DCI contains a TCI selection field; When the existence of the TCI selection field is determined, the bit width of the TCI selection is identified; and The receiving beam is obtained.

10. The method of claim 9, further comprising: The received beam is derived based on at least one of the following: (1) The combined / DL TCI state indicated by the bit value of the TCI selection field in DCI format 1_1 or DCI format 1_2; (2) The combined / DL TCI status indicated by a one-bit field in DCI format 1_2 or by a two-bit field in DCI format 1_1; (3) The joint / DL TCI state configured by RRC parameters other than those described above; or (4) Predefined joint / DL TCI state.

11. The method of any one of claims 1 to 12, wherein the M-TRP operation comprises at least one of the following: Spatial domain multiplexing (SDM) and PDSCH; Frequency domain multiplexing (FDM) PDSCH; Time-domain multiplexing (TDM) PDSCH; Single-frequency network SFN PDSCH; or Coherent Joint Transmission (CJT PDSCH).

12. A method for wireless communication by a network entity, the method comprising: Send to the User Equipment (UE) an indication of (330) multiple Joint Transmission Configuration Indicator (TCI) status, multiple Downlink DL TCI status, or multiple Uplink UL TCI status (multiple joint / DL / UL TCI status); Send (350) a control resource set CORESET including scheduling information to the UE; and Based on the scheduling information and the multiple combined / DL / UL TCI states, the system communicates with the UE (370) without sending an indication of a probe reference signal (SRS) for uplink transmission or a configuration for implementing multiple transmit receiver point (M-TRP) operation.

13. The method of claim 12, further comprising sending a configuration for multiple-input multiple-output (MIMO) operation to the UE, the configuration including a Radio Resource Control (RRC) message, the RRC message configuring at least one of the following: (1) Whether the uplink transmission is codebook-based or non-codebook-based, and the number of SRS resource sets used for said uplink transmission; or (2) Downlink control information DCI field in DCI format related to beam selection for downlink reception.

14. The method of claim 13, wherein the configuration for the MIMO operation further comprises: The configuration of the number of SRS resource sets associated with the DCI fields in DCI format 0_1 ​​or DCI format 0_2; or Configuration of the TCI selection field in DCI format 1_1 or DCI format 1_2.

15. An apparatus comprising: One or more radio frequency (RF) modems; A processor, the processor being coupled to the one or more RF modems; as well as At least one memory storing executable instructions for manipulating at least one of the processor or the one or more RF modems to perform the method as claimed in any one of claims 1 to 14.

Images