Codebook-based uplink transmission using multiple antenna panels and sharable antenna ports

Abstract

Methods, systems, and techniques are disclosed for performing uplink transmissions via multiple antenna panels that may cross-share antenna ports. User equipment (UE) has different uplink transmission behaviors under different multi-panel architectures. A method comprises a UE receiving (504, 604, 1404) a message for configuring at least two sets of SRS resources for codebook-based uplink transmissions by the UE. The UE receives (508, 608, 1408) an uplink grant indicating SRS resources from the at least two sets of SRS resources associated with the PUSCH transmission. The UE sends (510, 610, 141) the PUSCH transmission based on timing conditions associated with one of a first mode of operation (associated with transmissions using the same number of active ports for single-panel or multi-panel transmissions) or a second mode of operation (associated with transmissions using a different number of active ports for single-panel or multi-panel transmissions).

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communications, and more specifically to codebook-based uplink transmissions using multiple antenna panels. BACKGROUND

[0002] The Third Generation Partnership Project (3GPP) specifies a radio interface called Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G Core (5GC) network, a 5G Radio Access Network (5G-RAN), User Equipment (UE), and the like. The 5G NR architecture seeks to provide increased data rates, reduced latency, and / or increased capacity compared to the previous generation of cellular communication systems.

[0003] A UE can have two or more antenna panels for transmitting and receiving wireless signals in various directions. An antenna panel (or panel) includes an array of antennas (of elements) to provide a radio pattern (e.g., a beam in a particular direction) and coverage. Each of the multiple antenna panels can provide two or more antenna ports, which are logical entities to abstract the mapping of physical antennas to a particular transmission channel or signal. An antenna port is associated with a particular reference signal and physical channel and has a unique identifier. For example, in 5G NR, the 3GPP specification functionally defines antenna ports.

[0004] A UE with multiple antenna panels can share or provide the same antenna ports. An antenna port and associated configuration can be referred to as a radio frequency (RF) chain. When a UE has multiple panels, the UE can employ dedicated, shared, or partially shared RF chains. The configuration of multiple panels and how they provide one or more antenna ports is referred to as a panel architecture. Multiple-panel UEs can use various panel architectures, and the behavior is different for each panel architecture (or when switching between panel architectures).

[0005] To enable the UE to provide uplink transmission using multiple panels, a network entity (e.g., a base station) configures two sets of sounding reference signals (SRS) for uplink channel state information (CSI) measurement. The network entity uses the received SRS for channel estimation (e.g., computing CSI including channel quality indicator, precoding matrix indicator, and rank indicator) and optimizes communication parameters with the UE including updating modulation and coding scheme, adjusting transmission power, or updating beamforming weights, etc. When the network entity configures the UE to send a physical uplink shared channel (PUSCH) based on uplink codebook-based transmission, the network entity also configures two sets of SRS resources to support codebook-based PUSCH transmission, e.g., two sets of SRS resources with usage configured as ‘codebook’. The SRS resources are used to provide better channel estimation and feedback to the network entity, which then uses this information to optimize codebook-based PUSCH transmission. Thus, the SRS resources configured for codebook can enhance channel estimation and adaptation of precoding matrix for uplink transmission.

[0006] In operation, the network entity configures different transmission configuration indicator (TCI) states for the SRS resources in the two sets of SRS resources. The TCI states provide information about spatial transmission filter (beam) and uplink power control parameters for each set of SRS resources. By configuring different TCI states for the two sets of SRS resources, the network entity can optimize uplink transmission by adjusting the beam and power control parameters based on channel conditions. The UE can send the two sets of SRS resources from two panels (e.g., antenna arrays), which can improve spatial diversity and enhance channel estimation accuracy. This in turn can enable better adaptation of codebook-based precoding for PUSCH transmission, ultimately improving uplink performance.

[0007] For PUSCH transmission, the network entity can configure the PUSCH to be associated with one SRS resource from one set of SRS resources for single-panel transmission or two SRS resources from two sets of SRS resources for multi-panel transmission. The UE sends the PUSCH from the same antenna port using the same spatial domain filter as the associated SRS resource. The network entity can provide such indication through a field in downlink control information (DCI), e.g., SRS resource set selection. However, when the UE employs various panel architectures including multiple antenna panels providing multiple antenna ports, existing codebook-based precoding operation can not be applicable or can not provide reliable codebook-based uplink transmission. SUMMARY

[0008] The present disclosure provides methods, systems, and techniques for performing uplink transmissions via multiple antenna panels that can cross-share antenna ports. For example, two or more antenna panels can simultaneously transmit codebook-based uplink signals via one or more common antenna ports. When a user equipment (UE) has two or more antenna panels (or “panels” herein), the UE can employ dedicated, shared, or partially shared radio frequency (RF) chains (referred to as different panel architectures or modes of operation). The UE’s behavior in each mode of operation (or when switching between RF chains) is different.

[0009] When two or more panels share a common antenna port, additional transmission delays can arise. Different architectures also impose different restrictions on simultaneous transmissions or the number of ports that can be used by a single panel. Accordingly, the present disclosure provides methods for managing delays in different architectures, simultaneous uplink transmissions using different panels, and managing antenna ports of one or more panels in different architectures.

[0010] Traditionally, a UE uses a single antenna panel for uplink transmissions. The single antenna panel can provide multiple antenna ports. An antenna port (or “port” herein) is a logical entity that serves to abstract the mapping of a physical antenna to a particular transmission channel or signal. In most cases, an antenna port is associated with a particular reference signal and / or physical channel and has a unique corresponding identifier (e.g., 3GPP TS 38.211). For uplink transmissions, a base station (or network entity in general) estimates the uplink channel conditions (e.g., by measuring sounding reference signals (SRS) from the UE). Based on the estimated uplink channel conditions, the base station determines an optimal (producing the highest signal-to-noise ratio among all available matrices) precoding matrix (e.g., 3GPP TS 38.214 § 6.1.1.1) and indicates the precoding matrix to the UE (e.g., via a transmission precoding matrix indicator (TPMI)). The UE then applies the precoding matrix in the uplink transmission, such as in a physical uplink shared channel (PUSCH). Accordingly, traditional precoding matrix determination is performed based on a single antenna panel SRS configuration.

[0011] When multiple antenna panels are simultaneously transmitting SRS (or uplink signals), channel estimation and associated precoding matrix determination require additional considerations. For example, multiple antenna panels can share one or more antenna ports (e.g., by performing cross-panel antenna switching) and incur a delay that impacts SRS transmission (e.g., when signals are processed and transmitted by different panels). In some cases, the delay can cause existing precoding matrices to be outdated (e.g., inaccurate, inapplicable, or useless from the perspective of cross-panel antenna port switching). The present disclosure provides methods and techniques for providing robust codebook-based uplink transmissions using multiple antenna panels (e.g., multiple antenna panels for dedicated or shared antenna ports) by accounting for various delays associated with different panel architectures.

[0012] Benefits of the present disclosure include the ability to use multiple UE antenna panels (e.g., facing various directions) to create better channel conditions than using a single antenna panel, such as when multiple antenna panels are used for common antenna ports. A UE with multiple antenna panels enjoys the option of configuring various RF chains by having multiple antenna panels share some or all antenna ports and having panels use dedicated antenna ports in appropriate situations (e.g., when dedicated antenna ports via a single panel provide the best channel conditions among available options). The present disclosure also provides example precoding matrices for such multi-panel transmissions, whereas previous precoding matrices were for single-panel situations.

[0013] An example method includes a UE receiving, from a network entity, a message for configuring at least two SRS resource sets for codebook-based uplink transmissions by the UE. The UE receives, from the network entity, an uplink grant indicating an SRS resource from the at least two SRS resource sets associated with a PUSCH transmission. The UE transmits the PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode in accordance with the uplink grant.

[0014] The first operational mode is associated with transmissions using a same number of active ports for single-panel or multi-panel transmissions, and the second operational mode is associated with transmissions using different numbers of active ports for single-panel or multi-panel transmissions. For example, active ports include non-zero power ports, or can correspond to non-zero values in precoder matrices shown in Tables 3 and 4. In cases of port sharing, the number of ports for single-panel and multi-panel operations can be the same, can be the same as the number of RF chains, e.g., four. In cases of no cross-panel port sharing, the number of ports for single-panel operations will be less than the number of ports for multi-panel operations.

[0015] This disclosure provides multi-panel transmission with shared ports across panels to allow the same number of ports to be active in single-panel or multi-panel operation. For example, the UE uses this message to configure two or more antenna panels that can be configured to operate in a first operating mode or a second operating mode. In the first operating mode, at least one antenna port is shared between the two or more antenna panels (e.g., the antenna port may be shared by two panels or switched between two panels). In the second operating mode, antenna ports are not shared between the two or more antenna panels (e.g., each port has its own dedicated panel).

[0016] In various aspects, in response to an SRS from the UE and for PUSCH transmission, the network entity sends to the UE a precoder indicated for each of the two or more antenna panels based on a Transmission Rank Indicator (TRI) and a Transmission Precoder Matrix Indicator (TPMI) corresponding to the codebook, the number of ports of which is equal to the number of PUSCH ports per panel. The UE identifies the precoder corresponding to the indicated TRI and TPMI, having an associated layer corresponding to one or more common antenna ports. In some cases, the network entity sends the precoder where the number of non-zero power PUSCH ports per panel is less than or equal to the maximum number of PUSCH ports per panel reported by the UE regarding cross-panel port sharing capabilities. Other implementations are further discussed in the various embodiments described in detail. Attached Figure Description

[0017] Figure 1 A diagram is shown of a wireless communication system comprising multiple user equipment (UEs) and network entities communicating on one or more cells.

[0018] Figure 2 An example port configuration of multiple antenna panels, each with a dedicated panel, is shown according to aspects of this disclosure.

[0019] Figure 3 An example port configuration of multiple antenna panels is shown, in accordance with aspects of this disclosure, in which each antenna port is shared by multiple antenna panels.

[0020] Figure 4 An example port configuration of multiple antenna panels is shown, according to aspects of this disclosure, in which some antenna ports are shared by some of the multiple antenna panels.

[0021] Figure 5 This is a signaling diagram illustrating communication between a user equipment (UE) and a network entity for uplink multi-panel transmission based on a robust codebook, according to aspects of this disclosure.

[0022] Figure 6 is a flow diagram of a method of robust codebook based uplink multi-panel transmission at a UE according to aspects of the present disclosure.

[0023] Figure 7 is a flow diagram of a method of robust codebook based uplink multi-panel transmission at a network entity according to aspects of the present disclosure.

[0024] Figure 8 An example scheduling offset is shown according to aspects of the present disclosure.

[0025] Figure 9 An example of switching mapping of antenna ports on different sounding reference signal (SRS) resource sets is shown according to aspects of the present disclosure.

[0026] Figure 10 An example of switching mapping of antenna ports on different uplink signals is shown according to aspects of the present disclosure.

[0027] Figure 11 An example of switching mapping of some of the antenna ports on different uplink signals is shown according to aspects of the present disclosure.

[0028] Figure 12 An example of antenna port mapping to multiple antenna panels each having multiple associated SRS ports is shown according to aspects of the present disclosure.

[0029] Figure 13 An example of precoder indication based on a multi-port codebook for mapping multiple antenna ports to multiple panels is shown according to aspects of the present disclosure.

[0030] Figure 14 is a flow diagram of a method of wireless communication at a UE according to aspects of the present disclosure.

[0031] Figure 15 is a flow diagram of a method of wireless communication at a network entity according to aspects of the present disclosure.

[0032] Figure 16 is a diagram illustrating a hardware implementation for an example UE apparatus.

[0033] Figure 17 is a diagram illustrating a hardware implementation for one or more example network entities.

[0034] The same reference numbers in different drawings identify the same elements. DETAILED DESCRIPTION

[0035] The present disclosure provides methods, systems, and techniques for performing uplink transmissions via multiple antenna panels that can cross-share antenna ports. User equipment (UEs) have different uplink transmission behaviors under different multi-panel architectures. Figures 1 to 4 An environment of UE operation is shown, as well as how a UE can use multiple antenna panels for codebook-based uplink transmissions.

[0036] A network entity estimates channel conditions using sounding reference signals (SRS) from a UE. Then, based on the SRS, the network entity computes (or otherwise receives) parameters such as channel quality indicator (CQI), precoding matrix indicator (PMI), and rank indicator (RI). The network entity determines a modulation and coding scheme (MCS) based on the CQI and causes the UE to transmit an uplink signal using the MCS. When the UE has multiple antenna panels, the network entity can configure the SRS from the UE accordingly in view of multiple antenna ports and related attributes (e.g., transmission comb, power scaling, configuration index, etc.). The present disclosure provides methods and techniques for managing multi-panel uplink transmissions, simultaneous uplink signal transmissions using multiple panels, and port and precoder indication of one or more antenna panels.

[0037] In codebook-based transmission schemes, a UE can select a precoding matrix from a codebook to transmit data on the uplink. Codebook-based transmission schemes can optimize the use of multiple antennas to improve system performance. When a UE uses multiple antenna panels to provide multiple antenna ports (some dedicated and some shared in different panel architectures), internal delays and codebook / precoder selection present challenges that conventional practices cannot address (e.g., due to internal delays caused by switching antenna ports between different panels when shared). The present disclosure provides support for codebook-based uplink transmissions from multiple panels for different UE panel architectures, thereby improving the performance of uplink transmissions for each multi-panel architecture (compared to the single-panel case).

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

[0039] Operations of the base stations 104 and / or network design can be based on aggregated characteristics of base station functionality. For example, disaggregated base station architectures are utilized in integrated access backhaul (IAB) networks, open radio access network (O-RAN) networks, or virtualized radio access networks (vRANs), which can also be referred to as cloud radio access networks (C-RANs). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality for at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station architecture or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104a / 104e and / or RUs 106a-106d can communicate with the UEs 102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In an example, multiple RUs 106 and / or base stations 104 can simultaneously serve a UE 102, such as through intra- and / or inter-cell access links between the UE 102 and the RU 106 / base station 104.

[0040] The RUs 106, DUs 108, and CUs 110 can include (or can be coupled to) one or more interfaces configured to send or receive information / signals via a wired or wireless transmission medium. The base station 104 or any of the one or more disaggregated base station units can be configured to communicate with one or more other base stations 104 or one or more other disaggregated base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with executable instructions of the interface can be configured to provide communication between the base station 104 and / or the one or more disaggregated base station units via a wired or wireless transmission medium. For example, a wired interface can be configured to send or receive information / signals over a wired transmission medium, such as via a fronthaul link 160 between the RU 106d and a baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes the DU 108 and the CU 110, which can also have a wired interface (e.g., a midhaul link) configured between the DU 108 and the CU 110 to send or receive information / signals between the DU 108d and the CU 110d. In a further example, a wireless interface that can include a receiver, a transmitter, or a transceiver (such as an RF transceiver) is configured to send and / or receive information / signals via a wireless transmission medium, such as information communicated between the RU 106a and the base station 104e for cross-cell communication beams 136-138 via the RU 106a of the cell 190a and the base station 104e of the cell 190e.

[0041] The RUs 106 can be configured to implement low layer functionality. For example, the RUs 106 are controlled by the DUs 108 and can correspond to logical nodes that host RF processing functionality or lower layer PHY functionality, such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RUs 106 can be based on a functional split, such as a lower layer functional split.

[0042] The RUs 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b of the cell 190b, which can correspond to inter-cell communication beams, or in some examples, cross-cell communication beams. For example, the UE 102b of the cell 190b can communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. Real-time and non-real-time characteristics of the control- and user-plane communications of the RUs 106 can be controlled by the associated DUs 108.

[0043] Any combination of the RUs 106, the DUs 108, and the CUs 110, or individual references thereto, can correspond to a base station 104. Thus, a base station 104 can include at least one of the RUs 106, the DUs 108, or the CUs 110. The base station 104 provides access to a core network for the UEs 102. The base station 104 can relay communications between the UEs 102 and the core network. The base station 104 can be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, the cell 190e can correspond to a macro cell, while the cells 190a-190d can correspond to small cells. Small cells include femto cells, pico cells, micro cells, and the like. A cell structure that includes at least one macro cell and at least one small cell can be referred to as a “heterogeneous network.”

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

[0045] The communication links between the UEs 102 and the base stations 104 / RUs 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links can be associated with one or more carriers, and can be downlink or uplink. Downlink transmissions can be on licensed spectrum, while uplink transmissions can be on unlicensed spectrum, in an example. The UEs 102 and the base stations 104 / RUs 106 can utilize beamforming and directional communication with transmissions from at least one of the base stations 104 / RUs 106 and the UEs 102. The base stations 104 / RUs 106 and the UEs 102 can each include a number of antennas (e.g., antenna elements, antenna faces) that can be used for beamforming and directional communication. For example, each UE 102 can include four antennas, and each base station 104 can include a plurality of rows of antennas. The antennas can be used for receiving and transmitting downlink and uplink communications. The base stations 104 / RUs 106 and the UEs 102 can support any combination of full-duplex, true full-duplex, and / or half-duplex communications. A full-duplex communication system can enable the base stations 104 / RUs 106 and the UEs 102 to simultaneously transmit and receive transmissions. A true full-duplex communication system can enable the base stations 104 / RUs 106 and the UEs 102 to use the same frequency for both the downlink and the uplink transmissions. A half-duplex communication system can enable the base stations 104 / RUs 106 and the UEs 102 to transmit and receive transmissions in a time division duplex (TDD) manner.

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

[0047] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, etc. Fifth generation (5G) NR is often associated with two frequency range (FR) designations, FR1 and FR2. FR1 spans from 410 MHz to 7.125 GHz, and FR2 spans from 24.25 GHz to 52.6 GHz. Despite the fact that a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” frequency range. In comparison, FR2 is often referred to as a “millimeter wave” (mmW) frequency range. FR2 is not to be confused with the “extremely high frequency” (EHF) frequency range, which the International Telecommunications Union (ITU) has identified as spanning from 30 GHz to 300 GHz, and which sometimes is also referred to as a “millimeter wave” frequency range. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. The mid-band frequencies can be referred to as frequency range 3 (FR3), which spans from 7.125 GHz to 24.25 GHz. The bands within FR3 can include characteristics of FR1 and / or FR2. As such, the characteristics of FR1 and / or FR2 can extend into the mid-band frequencies. Higher operating bands have been identified for extending 5G NR communications beyond the 52.6 GHz upper limit of FR2-2. Three of these higher operating bands include FR2-2 (which spans from 52.6 GHz to 71.0 GHz), FR4 (which spans from 71.0 GHz to 114.25 GHz), and FR5 (which spans from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds with the upper limit of the EHF band. As such, unless specifically stated otherwise, the term “sub-6 GHz” can refer to frequencies less than 6 GHz, frequencies within FR1, or may

[0048] The UEs 102 and the base stations 104 / RUs 106 can each include multiple antennas. The multiple antennas can correspond to antenna elements, antenna panels, and / or antenna arrays that can facilitate beamforming operations. For example, the RU 106b transmits downlink beamformed signals to the UE 102b based on a first set of communication beams 132 in one or more transmission directions of the RU 106b. The UE 102b can receive the downlink beamformed signals from the RU 106b based on a second set of communication beams 134b in one or more reception directions of the UE 102b. In further examples, the UE 102b can also transmit uplink beamformed signals to the RU 106b based on the second set of communication beams 134b in one or more transmission directions of the UE 102b. The RU 106b can receive the uplink beamformed signals from the UE 102b in one or more reception directions of the RU 106b.

[0049] The UE 102b can perform beam training to determine optimal reception and transmission directions for beamformed signals. The transmission and reception directions of the UE 102 and the base stations 104 / RUs 106 can be the same or can be different. In further examples, beamformed signals can be communicated between a first base station / RU 106a and a second base station 104e. For example, the base station 104e of the cell 190e can transmit beamformed signals to the RU 106a based on a communication beam 138 in one or more transmission directions of the base station 104e. The RU 106a can receive the beamformed signals from the base station 104e of the cell 190e based on an RU communication beam 136 in one or more reception directions of the RU 106a. In further examples, the base station 104e transmits downlink beamformed signals to the UE 102e based on a communication beam 138 in one or more transmission directions of the base station 104e. The UE 102e receives the downlink beamformed signals from the base station 104e based on a UE communication beam 130 in one or more reception directions of the UE 102e. The UE 102e can also transmit uplink beamformed signals to the base station 104e based on the UE communication beam 130 in one or more transmission directions of the UE 102e such that the base station 104e can receive the uplink beamformed signals from the UE 102e in one or more reception directions of the base station 104e.

[0050] The base stations 104 can include and / or be referred to as network entities. That is, a “network entity” can refer to a base station 104 or at least one element of the base station 104, such as a RU 106, a DU 108, and / or a CU 110. The base stations 104 can also include and / or be referred to as next generation evolved nodeBs (ng-eNBs), generation one NBs (gNBs), evolved NBs (eNBs), access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), TRPs, network nodes, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station with a RU 106 and a BBU 112 including a DU 108 and a CU 110, or as a disaggregated base station including one or more of a RU 106, a DU 108, and / or a CU 110. A set of aggregated or disaggregated base stations can be referred to as a next generation radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 160a can be a secondary node.

[0051] Uplink / downlink signaling can also be communicated via a satellite positioning system (SPS) 114. In an example, the SPS 114 of the cell 190c can communicate with one or more UEs 102, such as the UE 102c, and one or more base stations 104 / RUs 106, such as the RU 106c. The SPS 114 can correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location system. The SPS 114 can be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and / or multi-RTT), wireless local area network (WLAN) signals, terrestrial beacon system (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) techniques, 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 sensor-related.

[0052] Still referring to Figure 1In certain aspects, any UE 102 can include a multi-panel configuration component 140 configured to receive, from a base station 104, a message for configuring at least two SRS resource sets for codebook-based uplink transmissions. The multi-panel configuration component 140 receives, from the base station 104, an uplink grant indicating SRS resources from the at least two SRS resource sets associated with a PUSCH transmission. The UE 102 transmits, in accordance with the uplink grant, the PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode. The first operational mode is associated with multi-panel transmissions and the second operational mode is associated with single-panel transmissions. For example, in the first operational mode, at least one antenna port is shared among two or more antenna panels; in the second operational mode, antenna ports are not shared among two or more antenna panels.

[0053] In certain aspects, any base station 104 or network entity of the base station 104 can include an uplink transmission configuration component 150 configured to transmit, to a UE 102, a message for configuring at least two SRS resource sets for codebook-based uplink transmissions by the UE 102. The uplink transmission configuration component 150 transmits, to the UE 102, an uplink grant indicating SRS resources from the at least two SRS resource sets associated with a PUSCH transmission. The uplink transmission configuration component 150 receives, in accordance with the uplink grant, the PUSCH transmission from the UE based on a timing condition associated with one of a first operational mode or a second operational mode. The first operational mode is associated with multi-panel transmissions and the second operational mode is associated with single-panel transmissions.

[0054] In some implementations, a network entity (e.g., a base station 104) configures a UE 102 to transmit a PUSCH based on codebook-based uplink transmissions. The network entity also configures two SRS resource sets that are associated with a codebook used in the codebook-based uplink transmissions. The SRSs configured by the network entity are intended to support the codebook-based transmissions. For example, the network entity can configure different transmission configuration indicator (TCI) states for SRS resources in the two SRS resource sets. The TCI states provide information about spatial transmission filters (beams) and uplink power control parameters for each SRS resource set.

[0055] By configuring different TCI states for the two SRS resource sets, the network entity can optimize uplink transmission by adjusting beam and power control parameters based on channel conditions. The UE can transmit the two SRS resource sets from two panels, thereby improving spatial diversity and enhancing channel estimation accuracy. Parameter updates can enable better adaptation of codebook-based precoding to PUSCH transmission. The network entity can configure different TCI states for the SRS resources in the two sets, thereby optimizing spatial transmission filters (beams) and uplink power control parameters.

[0056] Thus, Figure 1 A wireless communication system is described that can be implemented in connection with aspects of one or more other figures described herein, such as aspects shown in Figures 2 to 15 Further, although the following description can focus on 5G NR, the concepts described herein can be applicable to other similar areas, such as 5G-Advanced and future releases, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0057] Figure 2 An example port configuration 200 of multiple antenna panels 202, 204, and 206 such that each antenna port has a dedicated panel is shown in accordance with aspects of the present disclosure. As shown, the three panels 202, 204, and 206 can be configured with port connections 220 to support dedicated antenna ports 210 (e.g., two ports on each panel) respectively.

[0058] Figure 3 An example port configuration 300 of multiple antenna panels 302, 304, and 306 such that each antenna port 310 is shared by multiple antenna panels 302, 304, and 306 is shown in accordance with aspects of the present disclosure. As shown, the three panels 302, 304, and 306 can be configured with switchable connections 320 to share or support common antenna ports 310 (e.g., every port on all panels).

[0059] Figure 4 An example port configuration 400 of multiple antenna panels 402, 404, and 406 such that some antenna ports 410 are shared by some of the multiple antenna panels 402, 404, and 406 is shown in accordance with aspects of the present disclosure. As shown, the three panels 402, 404, and 406 can be configured with switchable connections 420 to share or support some of the multiple antenna ports 410. For example, while all three panels 402, 404, and 406 can support ports 0 and 1, ports 2 and 3 can use panels 404 and 406 without using panel 402.

[0060] In Figure 3and Figure 4 In the case of cross-panel antenna switching (e.g., port connection 320 links port 0 and port 1 from panel 302 to panel 306, or port connection 420 links port 0 and port 1 from panel 402 to panel 406), the UE can incur additional processing delay in transmitting uplink signals (e.g., SRS or PUSCH). Thus, when the UE needs to transmit port 0 from panel 306 (switched from panel 302), additional processing delay can be incurred (similarly, when the UE needs to transmit port 0 from panel 406 (switched from panel 402), additional processing delay can be incurred).

[0061] Figures 2 to 4 Different UE panel architectures are shown. When a UE has three (or multiple) antenna panels, the UE can use Figures 2 to 4 any of the architectures shown (the actual port-panel configuration is different). That is, a UE can be configured to have antenna ports that are dedicated (e.g., not shared) to multiple antenna panels (e.g., port configuration 200), antenna ports that are shared by all multiple antenna panels (e.g., port configuration 300), or antenna ports that are shared by some of the multiple antenna panels (e.g., port configuration 400). For these different architectures, the UE’s uplink transmission behavior is different.

[0062] Even if different UEs have multiple antenna panels and have cross-panel port sharing capability, the respective performance of uplink simultaneous multi-panel transmission can be different. For Figure 2 configuration 200 in FIG. 1, the UE is able to simultaneously transmit uplink signals from different panels (on respective dedicated antenna ports). However, for Figure 3 and Figure 4 the UE panel architectures shown in FIGS. 2 and 3, the UE’s simultaneous multi-panel transmission is limited: simultaneous transmission from multiple panels is only possible when the total number of antenna ports used for uplink signals does not exceed the maximum number of antenna ports.

[0063] For different UE panel architectures, the UE capability for the maximum number of ports used for single-panel transmission can also be different. For Figure 2 the UE architecture shown in FIG. 1, the UE is able to transmit uplink signals from one panel (each of panels 202, 204, and 206) through at most only two ports. For Figure 3 the UE architecture in FIG. 2, the UE is able to transmit uplink signals from one panel (each of panels 302, 304, and 306) through at most four ports. For Figure 4UE architecture in FIG. 4, the UE is capable of transmitting uplink signals from the first panel 402 through up to two ports (e.g., port 0 and port 1), and the UE is capable of transmitting uplink signals from the second panel 404 and the third panel 406 through up to 4 ports.

[0064] The methods and techniques herein support uplink transmissions from multiple panels of different UE panel architectures. Aspects of the present disclosure can improve the performance of uplink multi-panel transmissions for each particular UE panel architecture. Without employing the proposed methods, uplink transmissions from multi-panel transmissions can be limited to requiring additional delays for cross-panel antenna switching. Otherwise, as with conventional practices, the UE can be limited to support only two ports per panel, and unable to take advantage of multiple antenna panels.

[0065] Figure 5 is a signaling diagram 500 illustrating communications between a user equipment (UE) 102 and a network entity 104 for robust codebook based uplink multi-panel transmissions, according to aspects of the present disclosure. The network entity 104 can correspond to a base station or a unit of a base station, such as a RU 106, a DU 108, a CU 110, and the like. As shown, the UE 102 transmits 502 a UE capability or report indicating a supported configuration for single-panel and multi-panel based uplink transmissions. The UE capability can optionally indicate a cross-panel port sharing capability, such as using the same antenna port via two or more antenna panels (e.g., configurations 300 and 400). For example, the UE reports a UE capability or a UE report regarding UE panel related information including one or more parameters: a maximum number of ports per SRS resource for single-panel and multi-panel transmissions, an additional processing delay for PUSCH and SRS preparation, and simultaneous transmission operation of signals from different panels.

[0066] Based on the UE capability and related reporting / indication received from the UE, the network entity 104 transmits 504 radio resource control (RRC) signaling configuring two SRS resource sets for codebook-based uplink transmission and accordingly provides the UE with a reporting configuration for cross-panel port sharing status reporting. For example, the network entity can configure two SRS resource sets for codebook-based transmission through radio resource control (RRC) signaling (e.g., RRCReconfiguration). For type-1 configured grant PUSCH, the network entity can configure the uplink grant of PUSCH through RRC signaling, where the network entity can configure the selected SRS resource set index, one or more SRS resource indicators (SRIs), and one or more precoder information indicators, such as transmission rank indicator (TRI) and transmission precoder matrix indicator (TPMI). For dynamic grant PUSCH or type-2 configured grant PUSCH, the network entity can transmit DCI indicating the uplink grant of PUSCH. For aperiodic SRS, the network entity can transmit DCI scheduling SRS.

[0067] In response, the UE 102 reports 506 the cross-panel port sharing status for a set of synchronization signal blocks (SSBs) or channel state information (CSI) reference signals (CSI-RSs). The network entity 104 transmits 508 downlink control information (DCI) (1) to schedule physical uplink shared channel (PUSCH) transmission by indicating one or more SRIs and the precoders associated with the indicated SRIs, and / or (2) to schedule the configured SRS resource sets.

[0068] Accordingly, when one or more timing conditions are met, such as when / if the scheduling offset of PUSCH or SRS is greater than the minimum preparation time of PUSCH or SRS with multi-panel or single-panel transmission, the UE 102 transmits 510 the scheduled PUSCH and SRS resources in the SRS resource set based on the indicated precoders. For example, if the scheduling offset of PUSCH or SRS is greater than or equal to the minimum preparation time of PUSCH or SRS with the reported additional processing delay, the UE transmits the scheduled PUSCH or SRS from one or more panels based on the received RRC signaling and DCI; otherwise, the UE refrains from transmitting the scheduled PUSCH or SRS.

[0069] Figure 6 is a UE (e.g., Figure 5Flowchart 600 illustrates a method for robust codebook-based uplink multi-panel transmission at UE 102. As shown, the UE sends 602 UE Capability, indicating support configuration for single-panel and multi-panel-based uplink transmission, and optionally indicating cross-panel port sharing capability. The UE receives 604 RRC signaling, which configures two SRS resource sets for codebook-based uplink transmission based on the received UE Capability and UE report. This RRC signaling optionally configures a report configuration with cross-panel port sharing status reports. In response, the UE sends 606 a set of cross-panel port sharing status reports for either SSB or CSI-RS.

[0070] The UE receives a 608 DCI, which schedules a PUSCH or a set of SRS resources configured by indicating one or more SRIs and a precoder associated with the indicated SRI. If the scheduling offset of the PUSCH or SRS is greater than the minimum preparation time for the PUSCH or SRS with multi-panel or single-panel transmission, the UE transmits the SRS resources in the scheduled PUSCH and SRS resource set based on the indicated precoder.

[0071] Figure 7 It is based on aspects of this disclosure in network entities (e.g., Figure 5 The flowchart 700 describes a method for robust codebook-based uplink multi-panel transmission at network entity 104. Flowchart 700 at the network entity complements the method at the UE in flowchart 600. As shown, the network entity receives 702 UE capabilities indicating support configurations for single-panel and multi-panel-based uplink transmission, and optionally indicating cross-panel port sharing capabilities. The network entity sends 704 RRC signaling, which configures two SRS resource sets for codebook-based uplink transmission based on the received UE capabilities and UE reports. This RRC signaling optionally configures a report configuration with cross-panel port sharing status reports. The network entity then receives 706 a set of cross-panel port sharing status reports for either SSB or CSI-RS.

[0072] The network entity sends a 708 DCI, which schedules a PUSCH or a set of SRS resources configured for scheduling by instructing one or more SRIs and a precoder associated with the instructed SRI. Then, when the scheduling offset of the PUSCH or SRS is greater than the minimum preparation time for the PUSCH or SRS with multi-panel or single-panel transmission, the network entity receives the SRS resources in the PUSCH and SRS resource set scheduled by 710 based on the instructed precoder.

[0073] In this disclosure, the RRC signaling can indicate an RRC reconfiguration message from the network entity to the UE, or a system information block (SIB), where the SIB can be an existing SIB (e.g., SIB1) or a new SIB (e.g., SIBJ, where J is an integer greater than 21) sent by the network entity. In some implementations, the network entity receives the UE capability from a core network (e.g., an access and mobility management function (AMF)). In some other implementations, the network entity receives the UE capability from another base station (e.g., a gNB or an eNB).

[0074] Referring generally Figures 5 to 7 , the UE 102 can report or indicate its cross-panel port sharing capability and / or status by specifying one or more of the following attributes. In some cases, the UE can indicate the cross-panel port sharing status in the capability indication. For example, the UE can report a UE capability indicating a maximum number of SRS ports per SRS resource for single-panel transmission and / or a maximum number of SRS ports per SRS resource for multi-panel transmission. The UE can further report at least one UE capability including supported codebook subset coherence types (e.g., full-coherent, partial-coherent, and non-coherent), uplink full-power transmission mode (e.g., as specified in 3GPP TS 38.213 Section 7.1.1), a maximum number of PUSCH layers, a maximum number of non-zero-power PUSCH ports (e.g., active ports) per panel for single-panel and multi-panel transmissions, respectively, e.g., PUSCH associated with one selected SRS resource set or PUSCH associated with more than one selected SRS resource set.

[0075] In an embodiment, the UE can report a UE capability indicating whether it supports cross-panel port sharing (e.g., Figure 3 and Figure 4 example architecture in FIGS. 1-2). In some implementations, the UE reports whether it prefers or explicitly supports cross-panel port sharing. The UE can report the UE capability for any number of configured SRS ports or for each number of configured ports. In one example, when the number of SRS ports is configured as 1, 2, and 4, respectively, the UE reports whether it prefers or supports cross-panel port sharing. For example, in the UE panel configuration 200 of Figure 2 , the UE reports no support or preference for cross-panel port sharing for any number of configured ports. For the UE configurations 300 and 400 of Figure 3 and Figure 4 , the UE reports no support or preference for cross-panel port sharing when the number of SRS ports is configured as 1 or 2, but reports support or preference for cross-panel port sharing when the number of SRS ports is configured as 4.

[0076] In some implementations, the UE reports whether cross-panel port sharing is preferred or implicitly supported based on some other UE capability reports, e.g., simultaneous transmission of SRS resources from two SRS resource sets for codebook-based transmission, additional processing delay for PUSCH or SRS preparation, whether the UE needs a guard period (GP) between SRS resources from different SRS resource sets, etc. In some implementations, the UE reports the UE capability for any number of configured SRS ports. In some other implementations, the UE reports the UE capability for each number of configured ports.

[0077] In one example, the UE can report a UE capability indicating whether it supports simultaneous transmission of SRS resources from different SRS resource sets for codebook, and / or additional processing delay for PUSCH or SRS, and / or whether a GP between SRS resources from different SRS resource sets is preferred when each SRS resource is configured with 1 port, 2 ports, or 4 ports, respectively. Then, if simultaneous transmission of two SRS resources is not supported, or if the additional processing delay is greater than 0, or if the GP is greater than 0, the network entity can determine that cross-panel port sharing is preferred for the SRS resource set; otherwise, the network entity can determine that cross-panel port sharing is not preferred for the SRS resource set.

[0078] In some other implementations, the UE reports via UE capability the maximum number of PUSCH ports or the maximum number of non-zero power PUSCH ports (e.g., active ports) , the maximum number of SRS ports per resource , the maximum number of SRS resource sets for codebook . If , cross-panel port sharing is supported; otherwise, cross-panel port sharing is not supported. In some implementations, the UE can report a UE capability indicating the maximum number of PUSCH ports for each panel for multi-panel transmission. In some cases, the maximum number of non-zero power PUSCH ports (e.g., active ports) can be defined as NZP ports. For PUSCH transmission, the network can indicate a precoder like [1, 0, 0, 0]. In this case, one RF chain is needed.

[0079] In some cases, the UE can report the cross-panel port sharing status via UE assistance information reporting. For example, the UE can report UE assistance information to the network entity to indicate whether the UE supports cross-panel port sharing. The RRC message can carry the UE assistance information. The UE can report at least one parameter in the UE assistance information, including a preferred number of SRS ports per SRS resource for codebook-based transmission; whether the UE is capable of simultaneously transmitting SRS resources from two SRS resource sets; whether the UE needs an additional processing delay for SRS and PUSCH preparation; whether the UE needs a guard period (GP) between SRS resources from different SRS resource sets; a maximum number of PUSCH ports across panels and / or per panel, and other information.

[0080] In some cases, the UE can report the cross-panel port sharing status via layer one (L1) or layer two (L2) reporting. The UE can report whether the UE supports cross-panel port sharing for a set of network beams (e.g., a set of downlink reference signals, such as synchronization signal blocks (SSBs) and CSI reference signals (CSI-RSs)) through uplink control information (UCI) reporting on PUCCH or PUSCH or MAC CE.

[0081] In some implementations, the network entity can enable the reporting through RRC signaling. In one example, the network entity can configure the number of reports in a CSI report configuration to be cross-panel port sharing status reporting for group-based beam reporting. In another example, the network entity can configure the UE to report beam quality, e.g., layer 1 reference signal received power (L1-RSRP) or layer 1 signal to interference plus noise ratio (L1-SINR), for the set of beams.

[0082] In some implementations, the UE reports the cross-panel port sharing status only for the network beams corresponding to the indicated TCI states of PUSCH or SRS. For example, Table 1 below shows one example of UE reporting on cross-panel port sharing status for two configured sets of network beams. In the CSI field, there is information related to CSI-RS resource indicator (CRI), SSB resource indicator (SSBRI), and reference signal received power (RSRP). In some other implementations, the UE reports the cross-panel port sharing status for the corresponding network beams for each activated TCI state of PUSCH or SRS. In some other implementations, the UE reports the cross-panel port sharing status for a subset or all groups of network beams configured by the network entity, where the number of network beam groups to be reported can be configured by the network entity or reported by the UE. Table 1: Example of UE reporting on cross-panel port sharing status for network beam sets from two configurations.

[0083] In one example, for a UE panel configuration 200 of Figure 2 the UE reports that cross-panel port sharing is not supported for any set of network beams; for UE panel structure 2, the UE reports that cross-panel port sharing is supported for any set of network beams; for UE panel structure 3, the UE reports that cross-panel port sharing is supported for a set of network beams corresponding to UE panels 2 and 3, and cross-panel port sharing is supported for the first 2 ports of a set of network beams corresponding to UE panels 1 and 2.

[0084] In some implementations, the UE can report a common indicator indicating whether each port can be shared between PUSCH and SRS corresponding to different SRS resources. In some other implementations, the UE can report a separate indicator for each port indicating whether the port can be shared between PUSCH and SRS corresponding to different SRS resources. In one example, when the UE is configured with 4-port SRS transmission or when the UE reports that it supports a maximum of 4 ports for SRS resources, it can report a 4-bit bitmap indicating whether each port can be shared for SRS resources from different sets.

[0085] In some cases, the network entity can enable or disable cross-panel port sharing at the UE for a serving cell or a serving cell group in an uplink bandwidth part or for a frequency band or a frequency band combination through RRC signaling or a medium access control (MAC) control element (CE).

[0086] In some implementations, the network entity can configure, through RRC signaling or a MAC CE, a maximum total number of PUSCH ports or non-zero-power PUSCH ports for multi-panel transmission, or a maximum number of PUSCH ports or non-zero-power PUSCH ports per panel for multi-panel transmission. If the total number of PUSCH ports or non-zero-power PUSCH ports for multi-panel transmission is less than or equal to the maximum total number of ports for SRS resources of a SRS resource set, the network entity and the UE determine to enable cross-panel port sharing; otherwise, the network entity and the UE determine to disable cross-panel port sharing.

[0087] In some other implementations, the network entity and the UE can determine to enable cross-panel port sharing based on a configured maximum number of ports for SRS resources of a resource set and a number of configured SRS resource sets for codebook-based transmission and a UE capability on a maximum number of PUSCH ports To enable or disable cross-panel port sharing. If If yes, then cross-panel port sharing is enabled; otherwise, cross-panel port sharing is disabled.

[0088] In some other implementations, network entities communicate via RRC signaling or MAC CE. Configure the number of PUSCH ports for each panel or the number of SRS ports associated with a PUSCH associated with an SRI. If If the number of SRS ports configured across the SRS resource set is less than the number of ports configured across the SRS resource set, the network entity and the UE determine to enable cross-panel port sharing; otherwise, the network entity and the UE determine to disable cross-panel port sharing.

[0089] Figure 8 An example scheduling offset of 800 according to aspects of this disclosure is shown. As shown, a network entity may schedule PUSCH or SRS after a Physical Downlink Control Channel (PDCCH) signaling such as DCI. If the scheduling offset between the last symbol of DCI and the first symbol of a scheduled PUSCH or SRS from one or more panels is equal to or greater than the sum of the following two: (1) PUSCH or SRS preparation time and (2) additional processing delay, the UE continues to send PUSCH or SRS.

[0090] For example, the minimum preparation time for PUSCH and SRS can be predefined or reported by the UE via UE capabilities. In one example, the minimum preparation time for PUSCH is T as specified in Section 6.4 of 3GPP TS 38.214. proc,2 The minimum preparation time for SRS is N2 or N2+14 as specified in Section 6.4 of 3GPP TS 38.214. If the scheduling offset between the last symbol of the DCI and the first symbol of the scheduled PUSCH or SRS is less than the PUSCH or SRS preparation time plus the additional processing delay, the UE avoids sending the PUSCH or SRS. Figure 8 An example of processing latency management from one or more panels of PUSCH or SRS is shown.

[0091] Figure 9 An example 900 of antenna ports according to aspects of this disclosure is illustrated, mapping handover to different Sounding Reference Signals (SRS) resource sets. A guard period (GP) is configured between the network entity and the UE for uplink signals transmitted from different panels via cross-panel antenna handover (cross-panel port sharing). As shown, when the offset between the first SRS resource set and the second SRS resource set is greater than the GP, the UE continues transmission, allowing the antenna ports to update the panel mapping for the corresponding SRS resource set.

[0092] In some implementations, GP can be the same as additional processing latency. In other implementations, GP can be predefined or configured by network entities via RRC signaling or MAC CE, or reported by the UE via UE capability reports.

[0093] Network entity configuration requires two uplink signals for cross-panel antenna handover (cross-panel port sharing), where the offset is greater than GP. During GP, the UE avoids transmitting any uplink signals from serving cells or a list of serving cells within the same frequency band or combination of frequency bands sharing the same antenna. The UE can report frequency band combinations sharing the same antenna via UE capabilities. If the offset between the two uplink signals is less than GP, ​​the UE can avoid transmitting the first uplink signal and / or the second uplink signal, or determine that this is a misconfiguration and trigger an RRC reconfiguration request.

[0094] like Figure 9 As shown in Example 900, the network entity is configured with two SRS resource sets. Each SRS resource comes from four antenna ports (ports 0 to 3) based on the UE antenna architecture (e.g., Figure 3 (Configuration 300). Then, the network entity can preferably reserve GP between the two SRS resource sets, so that the UE has sufficient time to perform cross-panel antenna handover.

[0095] In this embodiment, the network entity and / or UE determine the additional processing latency of PUSCH or SRS based on whether UE reporting across panel port sharing is enabled and / or the network entity configuration.

[0096] In some implementations, the UE can report a value for additional processing delay. In other implementations, the value for additional processing delay can be predefined. In one example, additional processing delay is provided in units of symbols or slots, based on the subcarrier spacing of the PUSCH or SRS, or based on the minimum or maximum subcarrier spacing between the DCI scheduling the PUSCH or SRS and the PUSCH or SRS. Table 2 shows an example of a predefined additional processing delay. Table 2: Examples of additional processing delays during PUSCH or SRS preparation time

[0097] Figure 10An example 1000 is shown that switches the antenna ports mapped on different uplink signals according to aspects of the present disclosure. As shown, a cross-panel antenna switch results in an extra processing delay that is greater than zero (e.g., for the second uplink signal, the extra processing delay is greater than zero). In some cases, the network entity and / or UE determines that the extra processing delay can be greater than 0 only for PUSCH or SRS that require a cross-panel antenna switch. The network entity and / or UE determines whether the extra processing delay based on the transmission antenna ports of the first uplink signal in the most recent transmission and the second uplink signal scheduled by the network entity. The UE can transmit the first uplink signal and the second uplink signal, which can be from the same serving cell or from different serving cells in a frequency band or frequency band combination that share a common antenna.

[0098] Figure 11 An example 1100 is shown that switches some of the antenna ports mapped on different uplink signals according to aspects of the present disclosure. Figure 11 An example of zero extra processing delay when a cross-panel antenna switch is needed is shown. As shown, for the first SRS resource set, ports 0 and 1 are mapped to panel 1, and for the second SRS resource set, ports 2 and 3 are mapped to panel 2. Since the scheduled uplink signals do not require a cross-panel antenna switch, the extra processing delay is 0. Otherwise, the extra processing delay can be greater than 0, as shown in example 900. Figure 9

[0099] In some implementations, the extra processing delay is 0 if the UE supports simultaneous transmission of the first uplink signal and the second uplink signal; otherwise, the extra processing delay can be greater than 0. In some other implementations, the extra processing delay can be 0 if the first uplink signal and the second uplink signal are from the same antenna port, e.g., the first uplink signal is an SRS, and the second uplink signal is a PUSCH associated with the SRS; otherwise, the extra processing delay can be greater than 0.

[0100] Figure 12 An example 1200 is shown that maps antenna ports to multiple antenna panels with multiple associated SRS ports per panel according to aspects of the present disclosure. As shown, panels 1 and 2 provide a multi-panel transmission, where the number of SRS ports is four indicates that each panel has two associated SRS ports. The network entity configures or indicates the number of PUSCH ports or associated SRS ports per panel to be two. The first two PUSCH ports are associated with the first two ports of the first indicated SRS resource; the next two PUSCH ports are associated with the first two ports of the second indicated SRS resource.

[0101] ​The network entity can configure or indicate the number of PUSCH ports or associated SRS ports per panel K through RRC signaling, MAC CE, or DCI. The network entity then indicates a precoder for each panel based on the TRI and TPMI corresponding to a codebook with the number of ports equal to the number of PUSCH ports per panel K. The associated SRS ports for the PUSCH ports corresponding to each panel can be predefined, e.g., the first K SRS ports, or indicated by the network entity through RRC signaling, MAC CE, or DCI.

[0102] Figure 13 An example 1300 of precoder indication based on a multi-port codebook for mapping multiple antenna ports to multiple panels is shown in accordance with aspects of the present disclosure. As shown, example 1300 illustrates a multi-panel transmission with orthogonal non-zero-power PUSCH ports when the number of SRS ports is four. The network entity indicates a precoder to the UE based on a four-port codebook with antenna selection. The first indicated precoder can be , and the second indicated precoder can be .

[0103] The network entity can configure or indicate a precoder for each panel based on the TRI and TPMI corresponding to a codebook with the number of ports equal to the number of SRS ports per panel. In some implementations, for each panel, the network entity indicates a precoder where the number of non-zero-power PUSCH ports (e.g., active ports) per panel is less than or equal to the maximum number of PUSCH ports per panel reported by the UE capability. Alternatively, for each precoder, per panel, the network entity indicates a precoder where the number of non-zero-power PUSCH ports per panel is less than or equal to the maximum number of PUSCH ports reported divided by the number of selected SRS resource sets.

[0104] In some cases, the network entity can refrain from indicating the number of non-zero-power PUSCH ports per panel that is greater than the maximum number of PUSCH ports per panel reported by the UE. The UE can refrain from transmitting a PUSCH if the number of non-zero-power PUSCH ports per panel is greater than the maximum number of PUSCH ports per panel reported by the UE.

[0105] In some implementations, for partial-coherent precoders with rank > 1, the indicated TRI and TPMI can correspond to precoders where all layers correspond to the same antenna port, e.g., non-zero coefficients are in the same row. In one example, as shown in Table 3, the following at least one of the 4-port partial-coherent precoders from TPMI 22 to TPMI 37 can be introduced for rank 2 operation. In another example, a dedicated codebook can be defined for the cross-panel port sharing case. The rank 1 codebook can include non-coherent and partial-coherent precoders. The rank 2 codebook can include non-coherent precoders (TPMI 0 to 5) and partial-coherent precoders with the same antenna port for each layer (TPMI 22 to 37). While Table 3 provides a specific example of TPMI indices, the cross-panel port sharing codebook can use precoders in other TPMI indices, as shown in Table 4 (x and n are natural numbers).

[0106] Table 3: Example of rank 2 4-port codebook

[0107] In some other implementations, when the number of ports of the SRS resource is greater than the maximum number of PUSCH ports per panel, the network entity can only indicate non-coherent based precoders.

[0108] In some other implementations, the network entity can configure a codebook subset including partial-coherent precoders with the same antenna port for each layer, e.g., TPMI 22 to 37, through RRC signaling. Table 4: Example of rank 2 4-port codebook

[0109] Figure 14 A flow diagram illustrating a method of wireless communication at a UE is shown 1400. Referring to Figures 1 to 16 , the method can be performed by the UE 102, UE apparatus 1602, etc., which can include memory 1626’, 1606’, 1616 and can correspond to the entire UE 102 or the entire UE apparatus 1602, or a component of the UE 102 or UE apparatus 1602, such as the wireless baseband processor 1626 and / or the application processor 1606.

[0110] The UE reports 1402 to the network entity a capability to configure a first operation mode and a second operation mode based on a capability of the UE to share antenna ports across two or more antenna panels for uplink transmissions, and a status of the first operation mode and the second operation mode with a set of synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs) (e.g., Figure 5operation 502).

[0111] The UE receives 1404, from a network entity, a message (e.g., Figure 5 operation 504) for configuring at least two SRS resource sets for codebook-based uplink transmission by the UE. In response, the UE can report a cross-panel port sharing status of a set of SSBs or CSI-RSs.

[0112] The UE receives 1408, from a network entity, an uplink grant indicating a SRS resource from at least two SRS resource sets associated with a PUSCH transmission (e.g., Figure 5 operation 508).

[0113] The UE transmits 1410, in accordance with the uplink grant, a PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode. The first operational mode is associated with a transmission using a same number of active ports for single-panel or multi-panel transmission. The second operational mode is associated with a transmission using a different number of active ports for single-panel or multi-panel transmission.

[0114] Figure 14 A method of the UE side of a wireless communication link is described, whileA method of the network side of a wireless communication link is described. Figure 15

[0115] Figure 15 is a flow diagram 1500 of a method of wireless communication at a network entity. Referring to Figures 1 to 17 , the method can be performed by one or more network entities 104, which can correspond to a base station or a component of a base station, such as a RU 106, a DU 108, a CU 110, a RU processor 1706, a DU processor 1726, a CU processor 1746, etc. The one or more network entities 104 can include a memory 1706’ / 1726’ / 1746’, which can correspond to the entirety of the one or more network entities 104, or a component of the one or more network entities 104, such as the RU processor 1706, the DU processor 1726, or the CU processor 1746.

[0116] The network entity receives 1502, from a user equipment (UE): a capability to configure a first operational mode and a second operational mode based on a capability of the UE to share antenna ports across two or more antenna panels for uplink transmission, and a status related to the first operational mode and the second operational mode for a set of synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs).

[0117] The network entity transmits 1504, to the UE, a message for configuring at least two sounding reference signal (SRS) resource sets for codebook-based uplink transmission by the UE. The network entity receives a report of a cross-panel port sharing status of a set of SSBs or CSI-RSs.

[0118] The network entity transmits 1508, to the UE, an uplink grant indicating an SRS resource from at least two SRS resource sets associated with a PUSCH transmission.

[0119] The network entity receives 1510, from the UE, a PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode. The first operational mode is associated with a transmission using a same number of active ports for single-panel or multi-panel transmission. The second operational mode is associated with a transmission using different numbers of active ports for single-panel or multi-panel transmission.

[0120] With respect to Figure 14 and Figure 15 One or more detail aspects can be implemented. For example, the UE can configure two or more antenna panels that can be configured to perform operations in the first operational mode or the second operational mode based on the message configuring the at least two SRS resource sets. In the first operational mode, at least one antenna port is shared between the two or more antenna panels. In the second operational mode, antenna ports are not shared between the two or more antenna panels. In some cases, in the first operational mode, the UE shares two or more common antenna ports (e.g., respectively, Figure 3 and Figure 4 configurations 300 and 400 of FIG. 1) between the two or more antenna panels. In the second operational mode, the UE dedicates a fixed number of antenna ports to each of the two or more antenna panels (e.g., configuration 200 of FIG. 1). Figure 2

[0121] In aspects, the UE configures the two or more antenna panels by cross-sharing available antenna ports in the two or more antenna panels in the first operational mode. For example, cross-sharing includes switching common antenna ports between the two or more antenna panels.

[0122] In aspects, the UE receives a downlink control information (DCI) as an uplink grant scheduling a PUSCH transmission (e.g., in the second operational mode). The DCI schedules a configured SRS resource set. The UE transmits a respective SRS via at least one of the two or more antenna panels with dedicated antenna ports based on the configured SRS resource set.

[0123] ​In aspects, a UE receives downlink control information (DCI) indicating one or more SRS resource indicators (SRIs) and associated precoders (e.g., in a first mode of operation). The UE transmits a PUSCH transmission using the SRS resources indicated by the one or more SRIs and the associated precoders.

[0124] In aspects, a UE reports to a network entity a capability to configure a first mode of operation and a second mode of operation based on a capability of the UE to share antenna ports across two or more antenna panels for uplink transmissions.

[0125] In aspects, a UE reports to a network entity a status related to a first mode of operation and a second mode of operation for a set of synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs).

[0126] In aspects, a UE receives an indication from a network entity whether to enable a first mode of operation at the UE.

[0127] In aspects, a UE determines a scheduling offset between a last symbol of an uplink grant or associated downlink control information (DCI) and a first symbol of a PUSCH transmission or a SRS. The UE identifies a processing delay associated with sharing at least one antenna port in a first mode of operation. The UE identifies a preparation time associated with the UE.

[0128] In aspects, a timing condition is satisfied when the scheduling offset is greater than or equal to a sum of the preparation time and the processing delay. The UE can identify the processing delay by determining the processing delay as a characteristic of the UE, whether the first mode of operation or the second mode of operation has been configured. In some cases, the UE reports the processing delay to the network entity prior to receiving the message.

[0129] In aspects, a UE identifies a processing delay by determining the processing delay to be zero based on a previous uplink transmission when: a scheduled uplink signal does not require cross-panel port switching; simultaneous transmission of multiple uplink signals across two or more antenna panels is supported; or a same antenna port is used.

[0130] In aspects, a UE receives from a network entity a precoder indicated for each of two or more antenna panels based on a transmission rank indicator (TRI) and a transmission precoder matrix indicator (TPMI) corresponding to a codebook whose number of ports is equal to a number of PUSCH ports per panel. In some cases, for a partial coherent precoder of rank greater than one, the UE identifies a precoder corresponding to the indicated TRI and TPMI such that associated layers correspond to one or more common antenna ports.

[0131] The UE equipment 1602 as described below can perform the method of flowchart 1400. As described below, some or all of the methods of flowchart 1400 can be performed by a special-purpose programmable apparatus, such as the UE equipment 1602, to perform the functions described herein. Figure 16 The UE equipment 1602 as described below can perform the method of flowchart 1400. As described below, some or all of the methods of flowchart 1400 can be performed by a special-purpose programmable apparatus, such as the UE equipment 1602, to perform the functions described herein. Figure 17 The one or more network entities 104 as described below can perform the method of flowchart 1500. As described below, some or all of the methods of flowchart 1500 can be performed by a special-purpose programmable apparatus, such as the one or more network entities 104, to perform the functions described herein.

[0132] Figure 16 FIG. 1600 is a diagram 1600 illustrating an example of a hardware implementation for the UE equipment 1602. The UE equipment 1602 can be a UE 102, a component of a UE 102, or can implement UE functionality. The UE equipment 1602 can include an application processor 1606, which can have on-chip memory 1606'. In examples, the application processor 1606 can be coupled to a secure digital (SD) card 1608 and / or a display 1610. The application processor 1606 can also be coupled to a sensor module 1612, a power supply 1614, an additional memory module 1616, a camera 1618, and / or other related components. For example, the sensor module 1612 can control a barometric sensor / altimeter, a motion sensor 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.

[0133] The UE equipment 1602 can further include a wireless baseband processor 1626, which can be referred to as a modem. The wireless baseband processor 1626 can have on-chip memory 1626'. Together with and similar to the application processor 1606, the wireless baseband processor 1626 can also be coupled to the sensor module 1612, the power supply 1614, the additional memory module 1616, the camera 1618, and / or other related components. The wireless baseband processor 1626 can additionally be coupled to one or more subscriber identity modules (SIM) cards 1620 and / or one or more transceivers 1630 (e.g., wireless RF transceivers).

[0134] Within one or more transceivers 1630, the UE equipment 1602 can include a Bluetooth module 1632, a WLAN module 1634, an SPS module 1636 (e.g., GNSS module), and / or a cellular module 1638. The Bluetooth module 1632, WLAN module 1634, SPS module 1636, and cellular module 1638 can each include a transceiver on a chip (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1632, WLAN module 1634, SPS module 1636, and cellular module 1638 can each include a dedicated antenna and / or utilize the antennas 1640 to communicate with one or more other nodes. For example, the UE equipment 1602 can communicate with another UE 102 (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication) through the transceivers 1630 via the antennas 1640, where the network entity 104 can correspond to a base station or a element of a base station, such as a RU 106, a DU 108, or a CU 110.

[0135] The wireless baseband processor 1626 and the application processor 1606 can each include a computer-readable medium / memory 1626', 1606', respectively. The additional memory module 1616 can also be viewed as a computer-readable medium / memory. Each computer-readable medium / memory 1626', 1606', 1616 can be non-transitory. The wireless baseband processor 1626 and the application processor 1606 can each be responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1626', 1606', 1616. The software, when executed by the wireless baseband processor 1626 / application processor 1606, causes the wireless baseband processor 1626 / application processor 1606 to perform the various

[0136] As Figure 1 discussed and with respect to Figure 6 and Figure 14implemented, the multi-panel configuration component 140 is configured to receive, from a base station 104, a message for configuring at least two SRS resource sets for codebook-based uplink transmission. The multi-panel configuration component 140 receives, from the base station 104, an uplink grant indicating a SRS resource from the at least two SRS resource sets associated with a PUSCH transmission. The UE 102 transmits the PUSCH transmission based on a timing condition associated with one of the first operational mode or the second operational mode, in accordance with the uplink grant. The multi-panel configuration component 140 can be within the application processor 1606 (e.g., at 140a), the wireless baseband processor 1626 (e.g., at 140b), or both the application processor 1606 and the wireless baseband processor 1626. The multi-panel configuration component 140a and 140b can be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured with specially configured processing

[0137] Figure 17 FIG. 1700 is a diagram 1700 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 can be a base station, a component of a base station, or can implement base station functionality. The one or more network entities 104 can include or can correspond to at least one of the RUs 106, the DUs 108, or the CUs 110. The CU 110 can include a CU processor 1746, which can have on-chip memory 1746'. In some aspects, the CU 110 can further include an additional memory module 1756 and / or a communication interface 1748, which can both be coupled to the CU processor 1746. The CU 110 can communicate with the DUs 108 over a backhaul link 162, such as an Fl interface between the communication interface 1748 of the CU 110 and the communication interface 1728 of the DU 108.

[0138] The DU 108 can include a DU processor 1726, which can have on-chip memory 1726'. In some aspects, the DU 108 can further include an additional memory module 1736 and / or a communication interface 1728, which can both be coupled to the DU processor 1726. The DU 108 can communicate with the RUs 106 over a fronthaul link 160 between the communication interface 1728 of the DU 108 and the communication interface 1708 of the RU 106.

[0139] The RU 106 can include a RU processor 1706, which can have on-chip memory 1706'. In some aspects, the RU 106 can further include an additional memory module 1716, a communication interface 1708, and one or more transceivers 1730, all of which can be coupled to the RU processor 1706. The RU 106 can further include an antenna 1740, which can be coupled to the one or more transceivers 1730, such that the RU 106 can communicate with the UE 102 via the antenna 1740 through the one or more transceivers 1730.

[0140] The on-chip memories 1706', 1726', 1746' and the additional memory modules 1716, 1736, 1756 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1706, 1726, 1746 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor 1706, 1726, 1746, causes the processor 1706, 1726, 1746 to perform the various functions described herein. The computer-readable medium / memory can also be used for storing data that is manipulated by the processor 1706, 1726, 1746, when executing software. In an example, the uplink transmission configuration component 150 can be located at any of the one or more network entities 104, such as at the CU 110; at both the CU 110 and the DU 108; at each of the CU 110, the DU 108, and the RU 106; at the DU 108; at both the DU 108 and the RU 106; or at the RU 106.

[0141] As Figure 1 discussed and with respect to Figure 7 and Figure 15As implemented, the uplink transmission configuration component 150 is configured to transmit, to the UE 102, a message for configuring at least two SRS resource sets for codebook-based uplink transmission by the UE 102. The uplink transmission configuration component 150 transmits, to the UE 102, an uplink grant indicating a SRS resource from the at least two SRS resource sets associated with a PUSCH transmission. The uplink transmission configuration component 150 receives, from the UE, the PUSCH transmission based on a timing condition associated with one of the first mode of operation or the second mode of operation in accordance with the uplink grant. The uplink transmission configuration component 150 can be within one or more processors of one or more network entities 104, such as within RU processor(s) 1706 (e.g., at 150a), DU processor(s) 1726 (e.g., at 150b), and / or CU processor(s) 1746 (e.g., at 150c). The uplink transmission configuration component 150a-c can be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1706, 1726, 1746 configured to perform the stated processes / algorithm, stored within computer-readable medium(s) for implementation by one or more processors 1706, 1726, 1746, or combinations thereof.

[0142] The specific order or hierarchy of the blocks in the processes and flow diagrams disclosed herein are examples. Therefore, the specific order or hierarchy of blocks in the processes and flow diagrams can be rearranged or the blocks can be combined or deleted. Dotted line can indicate optional elements. The accompanying method claims present elements of the various blocks in example order, and are not limited to the specific order or hierarchy presented in the claims.

[0143] The detailed description set forth below in connection with the appended drawings describes various configurations and does not represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without using these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts being described.

[0144] Aspects of wireless communications systems, such as telecommunication systems, are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, calling flows, systems, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0145] An element, or any portion of an element, or any combination of elements can be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), 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 functionality described throughout this disclosure. One or more processors in the processing system can execute software that can be referred to as software, firmware, middleware, microcode, hardware description language, or other. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination of them.

[0146] If the functions described herein are implemented in software, they can be stored on or in a computer-readable medium, such as a non-transitory computer-readable storage medium, and executed by one or more processing units. Computer- readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or other

[0147] Aspects, implementations and / or use cases described herein can be implemented across many different platforms, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations and / or use cases can be realized across discrete components, integrated circuits, and / or other hardware, across firmware and / or software, or across microcontrollers, embedded controllers, and / or other processors. For example, aspects, implementations and / or use cases can be implemented as a system-on-chip (SoC) or system-in-package (Sip) that can be further incorporated into a variety of devices, such as personal and mobile computing devices, consumer electronics, industrial equipment, and / or automotive systems, to name a few.

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

[0149] The description herein is provided to enable those skilled in the art to practice various aspects as described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not to be limited to the aspects described herein but are to be accorded the full scope consistent with the language of the claims, wherein reference to an aspect and additional aspects means an element or steps can be present or omitted to practice that one of the aspects, depending on the common sense of a person skilled in the art.

[0150] A reference to an element in the singular is not intended to mean“one and only one” unless specifically stated, but rather“one or more.” Unless specifically stated otherwise, the term“some” refers to one or more. Combinations such as“at least one of A, B, or C,”“one or more of A, B, or C,” and the like mean A, B, and / or C individually, A and B, A and C, B and C, or A and B and C. When the phrase“at least one of’ or“one or more of’ appears in the

[0151] The term“some” refers to one or more unless specifically stated otherwise. Combinations such as“at least one of A, B, or C,”“one or more of A, B, or C,” and the like mean A, B, and / or C individually, A and B, A and C, B and C, or A and B and C. When the phrase“at least one of’ or“one or more of’ appears herein, this is taken to mean that a combination of one or more of the grouped elements is acceptable. The conjunctive term“or” should be interpreted in the inclusive sense, i.e.,“and / or,” unless it is explicitly stated to the contrary.

[0152] Unless specifically stated otherwise, ordinal terms such as "first" and "second" do not necessarily indicate temporal, sequential, numerical, etc. order, but are used to distinguish one from another. Reference numerals in the description and drawings that cross-hatch to one another are meant to illustrate possible relationships between the entities identified by the reference numerals. Multiple reference numerals in the description and drawings that cross-hatch to one another are meant to illustrate possible relationships between the entities identified by the reference numerals. Similar reference numerals in the description and drawings may refer to similar features in multiple drawings. Sometimes, "X" is used to generically refer to multiple variations of a feature. For example, "X06" can generically refer to all reference numbers ending in "06" (e.g., 206, 306, 406, etc.).

[0153] Structural equivalents and functional equivalents of elements of the various aspects described throughout this disclosure, which will be known or later become known to those of ordinary skill in the art, are expressly incorporated herein by reference and covered by the claims. The words "module," "mechanism," "element," "device," and the like can not be exclusive of the generic term "means." Thus, any recitation of "means" in a claim element should not be interpreted as a disclaimer of claim elements that describe "means" plus function. As used herein, the phrase "based on" shall not be construed as a reference to an closed set of information, conditions, factors, etc. Rather, the phrase "based on" shall be construed as "based, at least in part, on."

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

[0155] Example 1. A method for wireless communication by a user equipment (UE), the method comprising:

[0156] receiving, from a network entity, a message for configuring at least two sets of sounding reference signal (SRS) resources for codebook-based uplink transmission by the UE;

[0157] receiving, from the network entity, an uplink grant indicating an SRS resource from the at least two sets of SRS resources associated with a physical uplink shared channel (PUSCH) transmission; and

[0158] transmission associated with the first operational mode or the second operational mode, the first operational mode being associated with transmissions using a same number of active ports for single-panel or multi-panel transmissions, the second operational mode being associated with transmissions using different numbers of active ports for single-panel or multi-panel transmissions.

[0159] Example 2. The method of example 1, further comprising:

[0160] configuring, by the UE based on the message, two or more antenna panels that can be configured to perform in the first operational mode or the second operational mode, wherein:

[0161] in the first operational mode, sharing at least one antenna port between the two or more antenna panels; and

[0162] in the second operational mode, not sharing antenna ports between the two or more antenna panels.

[0163] Example 3. The method of example 2, wherein configuring the two or more antenna panels comprises:

[0164] in the first operational mode, sharing two or more common antenna ports between the two or more antenna panels; or

[0165] in the second operational mode, dedicating a fixed number of antenna ports to each of the two or more antenna panels.

[0166] Example 4. The method of example 2 or 3, wherein configuring the two or more antenna panels comprises:

[0167] in the first operational mode, cross-sharing available antenna ports in the two or more antenna panels.

[0168] Example 5. The method of example 2 or 3, wherein receiving the uplink grant comprises:

[0169] in the second operational mode, receiving a downlink control information (DCI) as the uplink grant scheduling the PUSCH transmission, the DCI scheduling a configured SRS resource set; and the method further comprising:

[0170] transmitting respective SRSs based on the configured SRS resource set via at least one of the two or more antenna panels having dedicated antenna ports.

[0171] Example 6. The method of any one of examples 1 to 4, wherein receiving the uplink grant comprises:

[0172] In this first mode of operation, receiving downlink control information (DCI) indicating one or more SRS resource indicators (SRIs) and associated precoders; and

[0173] wherein transmitting the PUSCH transmission comprises:

[0174] transmitting the PUSCH transmission using the SRS resources indicated by the one or more SRIs and the associated precoders.

[0175] Example 7. The method of any of Examples 1-6, further comprising:

[0176] reporting to the network entity a capability to configure the first mode of operation and the second mode of operation based on a capability of the UE to share antenna ports across the two or more antenna panels for uplink transmissions.

[0177] Example 8. The method of any of Examples 1-7, further comprising:

[0178] reporting to the network entity a status related to the first mode of operation and the second mode of operation for a set of synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs).

[0179] Example 9. The method of Example 8, wherein the status comprises at least one of:

[0180] a maximum number of SRS ports per SRS resource for uplink transmissions;

[0181] a supported codebook subset coherence type;

[0182] a mode of uplink full power transmission; or

[0183] an indication of whether the reporting is explicit or implicit.

[0184] Example 10. The method of Example 8, wherein reporting the status related to the first mode of operation and the second mode of operation comprises:

[0185] sending UE assistance information by a radio resource control (RRC) message to indicate:

[0186] a preferred number of SRS ports per SRS resource for codebook-based transmissions;

[0187] whether the UE transmits the SRS resources from the at least two SRS resource sets simultaneously;

[0188] a request for processing preparation by the UE;

[0189] a guard period between the SRS resources from the at least two SRS resource sets; or

[0190] a maximum number of PUSCH ports of (1) each of the two or more antenna panels or (2) shared between the two or more antenna panels.

[0191] Example 11. The method of example 8, wherein reporting the status related to the first and second operation modes comprises:

[0192] indicating to the network entity, via layer 1 or layer 2 reporting, whether the UE supports port sharing between the two or more antenna panels for a set of network beams.

[0193] Example 12. The method of any one of examples 1-11, further comprising:

[0194] receiving, from the network entity, an enablement indication of whether the first operation mode is to be enabled at the UE.

[0195] Example 13. The method of example 12, wherein receiving the enablement indication comprises:

[0196] identifying, in the message for configuring the UE, at least one of: a maximum number of PUSCH ports, a maximum number of non-zero power (NZP) PUSCH ports, a maximum number of PUSCH ports per antenna panel, or a maximum number of NZP PUSCH ports per antenna panel for multi-panel transmission; and

[0197] determining the enablement indication based on a maximum number of antenna ports across SRS resources of the SRS resource set in view of the identified maximum number.

[0198] Example 14. The method of example 12, wherein receiving the enablement indication comprises:

[0199] identifying, in the message for configuring the UE, a maximum number of ports of SRS resources in a resource set and a number of SRS resource sets for codebook-based transmission configuration; and

[0200] determining the enablement indication based on a number of PUSCH ports supported by the UE in view of the identified maximum number.

[0201] Example 15. The method of example 12, wherein receiving the enablement indication comprises:

[0202] identifying, in the message for configuring the UE, a number of PUSCH ports per panel and a number of associated SRS ports for a PUSCH transmission associated with one SRI; and

[0203] the enabling indication based on a comparison between a number of PUSCH ports per panel and a number of associated SRS ports for a PUSCH transmission associated with one SRI.

[0204] Example 16. The method of any of examples 1-15, further comprising:

[0205] determining a scheduling offset between a last symbol of the uplink grant or associated downlink control information (DCI) and a first symbol of the PUSCH transmission or SRS;

[0206] identifying a processing delay associated with sharing at least one antenna port in the first operational mode; and

[0207] identifying a preparation time associated with the UE.

[0208] Example 17. The method of example 16, wherein the timing condition is satisfied when the scheduling offset is greater than or equal to a sum of the preparation time and the processing delay.

[0209] Example 18. The method of example 16, further comprising:

[0210] determining a guard period between uplink signals transmitted from different antenna panels of the two or more antenna panels.

[0211] Example 19. The method of example 18, wherein the guard period is equal to the processing delay.

[0212] Example 20. The method of example 18, wherein the guard period is configured by the network entity or associated with the UE.

[0213] Example 21. The method of example 18, wherein the timing condition is satisfied when the scheduling offset is greater than the guard period.

[0214] Example 22. The method of any of examples 16-21, wherein identifying the processing delay comprises:

[0215] determining the processing delay as a characteristic of the UE regardless of whether the first operational mode or the second operational mode has been configured.

[0216] Example 23. The method of any of examples 1-22, further comprising:

[0217] reporting the processing delay to the network entity prior to receiving the message.

[0218] Example 24. The method of any of examples 16-21, wherein identifying the processing delay comprises:

[0219] The processing delay is determined to be zero based on a previous uplink transmission when:

[0220] The scheduled uplink signal does not require switching across panel ports;

[0221] Multiple uplink signals are supported to be transmitted simultaneously across the two or more antenna panels; or

[0222] The same antenna port is used.

[0223] Example 25. The method of any of Examples 1-24, further comprising:

[0224] receiving, from the network entity, a precoder indicated for each of the two or more antenna panels based on a transmission rank indicator (TRI) and a transmission precoder matrix indicator (TPMI) corresponding to the codebook, a number of ports of the codebook being equal to a number of PUSCH ports per panel.

[0225] Example 26. The method of Example 25, wherein receiving the precoder indicated for each of the two or more antenna panels comprises:

[0226] for a partial-coherent precoder of rank greater than one, identifying the precoder corresponding to the indicated TRI and TPMI such that associated layers correspond to one or more common antenna ports.

[0227] Example 27. The method of Example 25, wherein receiving the precoder indicated for each of the two or more antenna panels comprises:

[0228] receiving, from the network entity, a precoder where a number of non-zero-power PUSCH ports per panel is less than or equal to a maximum number of PUSCH ports per panel reported by the UE regarding a cross-panel port sharing capability.

[0229] Example 28. The method of Example 25, wherein receiving the precoder indicated for each of the two or more antenna panels comprises:

[0230] receiving, from the network entity, a non-coherent precoder when a number of ports of an SRS resource is greater than a maximum number of PUSCH ports per panel.

[0231] Example 29. The method of Example 25, wherein receiving the precoder indicated for each of the two or more antenna panels comprises:

[0232] receive, from the network entity, a codebook subset to include partial coherence precoders with one or more common antenna ports for each layer.

[0233] Example 30. A method for wireless communications by a network entity, the method comprising:

[0234] transmitting, to a user equipment (UE), a message for configuring at least two sets of sounding reference signal (SRS) resources for codebook-based uplink transmissions by the UE;

[0235] transmitting, to the UE, an uplink grant indicating an SRS resource from the at least two sets of SRS resources associated with a physical uplink shared channel (PUSCH) transmission; and

[0236] receiving, from the UE in accordance with the uplink grant, the PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode, the first operational mode associated with transmissions using a same number of active ports for single-panel or multi-panel transmissions, the second operational mode associated with transmissions using different numbers of active ports for single-panel or multi-panel transmissions.

[0237] Example 31. The method of example 30, wherein the message configures two or more antenna panels in the UE to perform operations in the first operational mode or the second operational mode, wherein:

[0238] in the first operational mode, at least one antenna port is shared among the two or more antenna panels; and

[0239] in the second operational mode, antenna ports are not shared among the two or more antenna panels.

[0240] Example 32. The method of example 31, wherein the message configures two or more antenna panels in the UE to perform operations:

[0241] in the first operational mode, two or more common antenna ports are shared among the two or more antenna panels; or

[0242] in the second operational mode, a fixed number of antenna ports are dedicated to each of the two or more antenna panels.

[0243] Example 33. The method of example 31 or 32, wherein the message configures two or more antenna panels in the UE to perform operations:

[0244] in the first operational mode, available antenna ports in the two or more antenna panels are cross-shared.

[0245] Example 34. The method of example 31 or 32, wherein transmitting the uplink grant comprises:

[0246] when the UE is in the second mode of operation, transmitting downlink control information (DCI) as the uplink grant scheduling the PUSCH transmission, the DCI scheduling a configured SRS resource set; and the method further comprising:

[0247] receiving respective SRS via at least one of the two or more antenna panels with dedicated antenna ports based on the configured SRS resource set.

[0248] Example 35. The method of any of examples 30 to 33, wherein transmitting the uplink grant comprises:

[0249] when the UE is in the first mode of operation, transmitting downlink control information (DCI) indicating one or more SRS resource indicators (SRIs) and associated precoders; and

[0250] wherein receiving the PUSCH transmission comprises:

[0251] monitoring the PUSCH transmission in SRS resources indicated by the one or more SRIs and the associated precoders.

[0252] Example 36. The method of any of examples 30 to 35, further comprising:

[0253] receiving, from the UE, a capability report configuring the first mode of operation and the second mode of operation based on a capability of the UE to share antenna ports across the two or more antenna panels for uplink transmissions.

[0254] Example 37. The method of any of examples 30 to 36, further comprising:

[0255] receiving, from the UE, a status report related to the first mode of operation and the second mode of operation for a set of synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs).

[0256] Example 38. The method of example 37, wherein the status report comprises at least one of:

[0257] a maximum number of SRS ports per SRS resource for uplink transmissions;

[0258] a supported codebook subset coherence type;

[0259] a mode of uplink full power transmission; or

[0260] whether the report is explicit or implicit.

[0261] Example 39. The method of example 37, wherein receiving the status report related to the first operational mode and the second operational mode comprises:

[0262] receiving the UE assistance information via a radio resource control (RRC) message to indicate:

[0263] a preferred number of SRS ports per SRS resource for codebook-based transmission;

[0264] whether the UE is to simultaneously transmit the SRS resource from the at least two SRS resource sets;

[0265] a request for processing preparation by the UE;

[0266] a guard period between the SRS resource from the at least two SRS resource sets; or

[0267] a maximum number of PUSCH ports of (1) each of the two or more antenna panels or (2) shared between the two or more antenna panels.

[0268] Example 40. The method of example 37, wherein receiving the status report related to the first operational mode and the second operational mode comprises:

[0269] receiving an indication from the UE whether the UE supports port sharing between the two or more antenna panels for a set of network beams via a layer 1 or layer 2 report.

[0270] Example 41. The method of any of examples 30-40, further comprising:

[0271] sending an indication to the UE whether the first operational mode is to be enabled at the UE.

[0272] Example 42. The method of any of examples 30-41, further comprising:

[0273] receiving a report from the UE of a processing delay associated with sharing at least one antenna port in the first operational mode prior to sending the message.

[0274] Example 43. The method of any of examples 30-42, further comprising:

[0275] transmit, to the UE, a precoder indicated for each of the two or more antenna panels based on a transmission rank indicator (TRI) and a transmission precoder matrix indicator (TPMI) corresponding to the codebook, a number of ports of the codebook being equal to a number of PUSCH ports per panel.

[0276] Example 44. The method of example 43, wherein transmitting the precoder indicated for each of the two or more antenna panels comprises:

[0277] for partial coherent precoders of rank greater than one, identifying the precoder corresponding to the indicated TRI and TPMI such that the associated layers correspond to one or more common antenna ports.

[0278] Example 45. The method of example 43, wherein transmitting the precoder indicated for each of the two or more antenna panels comprises:

[0279] transmit, to the UE, a precoder where a number of non-zero power PUSCH ports per panel is less than or equal to a maximum number of PUSCH ports per panel reported by the UE with respect to a cross-panel port sharing capability.

[0280] Example 46. The method of example 43, wherein transmitting the precoder indicated for each of the two or more antenna panels comprises:

[0281] transmit, to the UE, a non-coherent precoder when a number of ports of an SRS resource is greater than a maximum number of PUSCH ports per panel.

[0282] Example 47. The method of example 43, wherein transmitting the precoder indicated for each of the two or more antenna panels comprises:

[0283] transmit, to the UE, a codebook subset to include partial coherent precoders having one or more common antenna ports for each layer.

[0284] Example 48. An apparatus for wireless communication comprising a transceiver, a memory, and a processor coupled to the memory and the transceiver, the apparatus configured to implement a method of any of examples 1-47.

[0285] Example 49. An apparatus comprising a processor configured to cause a user equipment (UE) to:

[0286] receive control signaling configuring:

[0287] two sets of sounding reference signal (SRS) resources for codebook-based transmission; and

[0288] a physical uplink shared channel (PUSCH) transmission scheme as codebook-based transmission; and

[0289] whether the SRS resources from different sets are from the same antenna port

[0290] receiving an uplink grant indicating:

[0291] one or two SRS resources from the configured set of SRS resources associated with the PUSCH transmission; and

[0292] a precoder associated with each SRS resource based on a predefined codebook and a PUSCH port

[0293] transmitting the PUSCH based on the indicated precoder if an offset between a last symbol of the uplink grant and a first symbol of the PUSCH is greater than or equal to a minimum preparation time plus an additional processing delay.

[0294] Example 50. An apparatus comprising a processor configured to cause a base station (BS) to:

[0295] transmit control signaling configuring:

[0296] two sets of sounding reference signal (SRS) resources for codebook-based transmission; and

[0297] a physical uplink shared channel (PUSCH) transmission scheme as codebook-based transmission; and

[0298] whether the SRS resources from different sets are from the same antenna port

[0299] transmitting an uplink grant indicating:

[0300] one or two SRS resources from the configured set of SRS resources associated with the PUSCH transmission; and

[0301] a precoder associated with each SRS resource based on a predefined codebook and a PUSCH port

[0302] receiving the PUSCH based on the indicated precoder if an offset between a last symbol of the uplink grant and a first symbol of the PUSCH is greater than or equal to a minimum preparation time plus an additional processing delay.

Claims

1. A method for wireless communications by a user equipment (UE), comprising: receiving (504, 604, 1404), from a network entity, a message for configuring at least two sounding reference signal (SRS) resource sets for codebook-based uplink transmissions by the UE; receiving (508, 608, 1408), from the network entity, an uplink grant indicating an SRS resource from the at least two SRS resource sets associated with a physical uplink shared channel (PUSCH) transmission; and transmitting (510, 610, 1410), in accordance with the uplink grant, the PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode, the first operational mode being associated with transmissions using a same number of active ports for single-panel or multi-panel transmissions and the second operational mode being associated with transmissions using different numbers of active ports for single-panel or multi-panel transmissions.

2. The method of claim 1, further comprising: configuring, by the UE, two or more antenna panels configurable to perform in the first operational mode or the second operational mode based on the message, wherein: in the first operational mode, at least one antenna port is shared among the two or more antenna panels; and in the second operational mode, antenna ports are not shared among the two or more antenna panels.

3. The method of claim 2, wherein configuring the two or more antenna panels comprises: in the first operational mode, sharing two or more common antenna ports among the two or more antenna panels; or in the second operational mode, dedicating a fixed number of antenna ports to each of the two or more antenna panels.

4. The method of claim 2 or 3, wherein configuring the two or more antenna panels comprises: in the first operational mode, cross-sharing available antenna ports in the two or more antenna panels.

5. The method of claim 2 or 3, wherein receiving the uplink grant comprises: in the second operational mode, receiving a downlink control information (DCI) as the uplink grant scheduling the PUSCH transmission, the DCI scheduling a configured SRS resource set; and the method further comprising: transmitting respective SRSs based on the configured SRS resource set via at least one of the two or more antenna panels with dedicated antenna ports.

6. The method of any one of claims 1 to 4, wherein receiving the uplink grant comprises: in the first operational mode, receiving a downlink control information (DCI) indicating one or more SRS resource indicators (SRIs) and associated precoders; and wherein transmitting the PUSCH transmission comprises: transmitting the PUSCH transmission using SRS resources indicated by the one or more SRIs and the associated precoders.

7. The method of any one of claims 1 to 6, further comprising: reporting, to the network entity, a capability to configure the first and second operation modes based on a capability of the UE to share antenna ports across the two or more antenna panels for uplink transmissions.

8. The method of any one of claims 1-7, further comprising: reporting, to the network entity, a status related to the first and second operation modes for a set of synchronization signal blocks, SSBs, or channel state information reference signals, CSI-RSs.

9. The method of any one of claims 1-8, further comprising: receiving, from the network entity, an indication of whether to enable the first operation mode at the UE.

10. The method of any one of claims 1-9, further comprising: determining a scheduling offset between a last symbol of the uplink grant or associated downlink control information, DCI, and a first symbol of the PUSCH transmission or SRS; identifying a processing delay associated with sharing at least one antenna port in the first operation mode; and identifying a preparation time associated with the UE.

11. The method of claim 10, wherein the timing condition is satisfied when the scheduling offset is greater than or equal to a sum of the preparation time and the processing delay.

12. The method of any one of claims 10 or 11, wherein identifying the processing delay comprises: determining the processing delay as a characteristic of the UE regardless of whether the first or second operation mode is configured.

13. The method of any one of claims 1-12, further comprising: reporting the processing delay to the network entity prior to receiving the message.

14. The method of any one of claims 10 or 11, wherein identifying the processing delay comprises: determining the processing delay as zero based on a previous uplink transmission when: a scheduled uplink signal does not require cross-panel port switching; simultaneous transmission of multiple uplink signals across the two or more antenna panels is supported; or a same antenna port is used.

15. The method of any one of claims 1-14, further comprising: receiving, from the network entity, a precoder indicated for each of the two or more antenna panels based on a transmission rank indicator, TRI, and a transmission precoder matrix indicator, TPMI, corresponding to the codebook, a number of ports of the precoder being equal to a number of PUSCH ports per panel.

16. The method of claim 15, wherein receiving the precoder indicated for each of the two or more antenna panels comprises: for a partial coherent precoder of rank greater than one, identifying the precoder corresponding to the indicated TRI and TPMI having associated layers corresponding to one or more common antenna ports.

17. A method for wireless communications by a network entity, the method comprising: ​ transmit (504, 604, 1404), to a user equipment, UE, a message for configuring at least two sounding reference signal, SRS, resource sets for codebook-based uplink transmission by the UE; transmit (508, 608, 1408), to the UE, an uplink grant indicating a SRS resource from the at least two SRS resource sets associated with a physical uplink shared channel, PUSCH, transmission; and receive (510, 610, 1410), from the UE, the PUSCH transmission based on a timing condition associated with one of a first operational mode or a second operational mode according to the uplink grant, the first operational mode being associated with a transmission using a same number of active ports for single-panel or multi-panel transmission and the second operational mode being associated with a transmission using different numbers of active ports for single-panel or multi-panel transmission.

18. The method of claim 17, wherein the message configures two or more antenna panels in the UE to perform operations in the first operational mode or the second operational mode, wherein: in the first operational mode, at least one antenna port is shared among the two or more antenna panels; and in the second operational mode, antenna ports are not shared among the two or more antenna panels.

19. An apparatus for wireless communication, comprising a transceiver, a memory, and a processor, the processor coupled to the memory and the transceiver, the apparatus configured to implement a method as in any of claims 1-18.

Images