Sounding reference signal port indicating physical uplink shared channel for simultaneous transmission across multiple panels with shared port
By configuring signaling between the UE and network entities in the wireless communication system, instructing a subset of PUSCH ports of multiple shared panels to transmit collaboratively, the problems of signal transmission reliability and resource utilization efficiency are solved, achieving more efficient signal transmission and resource utilization.
Patent Information
- Application Number
- CN202480020968.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-01-02
- Filing Date
- 2024-02-13
- Publication Date
- 2025-11-04
AI Technical Summary
In wireless communication systems, there is a need to improve signal transmission reliability and resource utilization efficiency, especially in complex and dynamic environments where existing technologies struggle to effectively utilize the antenna ports of multiple panels for efficient signal transmission.
By configuring signaling between the user equipment (UE) and network entities, the probe reference signal (SRS) port of the Physical Uplink Shared Channel (PUSCH) is instructed to be used across multiple panels to enable coordinated transmission among port subsets of multiple panels, and the port combination is dynamically configured using downlink control information (DCI).
It improves the signal transmission reliability and resource utilization efficiency of wireless communication systems, enables more efficient use of time and frequency resources, and enhances the communication capabilities of different types of devices.
Smart Images

Figure CN120898397A_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims priority to U.S. Patent Application No. 18 / 402,523, filed January 2, 2024, and U.S. Patent Application No. 63 / 492,355, filed March 27, 2023, both of which are assigned to the assignee of this application and are thereby fully and expressly incorporated herein by reference as fully set forth herein and for all applicable purposes. Background Technology Technical Field
[0004] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for indicating probe reference signal (SRS) ports for physical uplink shared channel (PUSCH) used for simultaneous transmission (STxMP) across multiple panels with shared ports.
[0005] Description of Related Art
[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available wireless communication system resources.
[0007] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention
[0008] One aspect provides a method for wireless communications by a user equipment (UE). The method includes receiving, from a network entity, a configuration of at least a first set of sounding reference signal (SRS) resources and a second set of SRS resources for codebook-based physical uplink shared channel (PUSCH) transmissions; receiving, from the network entity, signaling scheduling the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, where the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first set of SRS resources and a second set of PUSCH ports corresponding to the subset of SRS ports associated with SRS resources in the second set of SRS resources; and transmitting the at least one PUSCH using the first set of PUSCH ports via a first panel of the UE and using the second set of PUSCH ports via a second panel of the UE.
[0009] Another aspect provides a method for wireless communications by a network entity. The method includes transmitting, to a UE, a configuration of at least a first set of sounding reference signal (SRS) resources and a second set of SRS resources for codebook-based physical uplink shared channel (PUSCH) transmissions; transmitting, to the UE, signaling scheduling the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, where the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first set of SRS resources and a second set of PUSCH ports corresponding to the subset of SRS ports associated with SRS resources in the second set of SRS resources; and receiving the at least one PUSCH, where the at least one PUSCH is transmitted using the first set of PUSCH ports via a first panel of the UE and using the second set of PUSCH ports via a second panel of the UE.
[0010] Other aspects provide an apparatus capable of, configured for, or otherwise adapted to perform any one or more of the preceding methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions, that when executed by a processor of an apparatus, cause the apparatus to perform the preceding methods and those described elsewhere herein; a computer program product embodied on a computer readable medium comprising code for performing the preceding methods and those described elsewhere herein; and / or an apparatus comprising means for performing the preceding methods and those described elsewhere herein. By way of example, an apparatus can include a processing system, a device having a processing system, or a processing system in cooperation with one or more networks.
[0011] For illustrative purposes, certain features are described below in the context of certain examples. Attached Figure Description
[0012] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.
[0013] FIG. 1 An example wireless communication network is depicted.
[0014] FIG. 2 An example decomposed base station architecture is described.
[0015] FIG. 3 Various aspects of the example base station and example user equipment are described.
[0016] FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D Various example aspects of data structures used in wireless communication networks are described.
[0017] FIG. 5 This is a call flowchart illustrating an example of codebook-based uplink (UL) transmission.
[0018] FIG. 6 This is a call flow diagram illustrating an example of UL transmission based on a non-codebook.
[0019] FIG. 7 A table showing the pre-decoding matrix W and the corresponding transmit pre-decoding matrix indicator (TPMI) index for a single-layer transmission using two antenna ports is provided.
[0020] FIG. 8 A table showing the pre-decoding matrix W and the corresponding TPMI index for single-layer transmission using four antenna ports is presented.
[0021] FIG. 9 A table showing the pre-decoding matrix W and the corresponding TPMI index for two-layer transmission using four antenna ports is presented.
[0022] FIG. 10 A table showing the "pre-decoding information and layer number" for the four antenna ports is displayed.
[0023] FIG. 11 A table showing the "pre-decoding information and layer number" for the four antenna ports is displayed.
[0024] FIG. 12 A table showing the "pre-decoding information and layer number" for the two antenna ports is displayed.
[0025] FIG. 13 An example of a spatial multiplexing (SDM) PUSCHSTxMP scheme based on a single downlink control information (DCI) is shown in box form.
[0026] FIG. 14 An example of a single DCI based single frequency network (SFN) PUSCH STxMP scheme is shown in block form.
[0027] FIG. 15A 、 FIG. 15B 、 FIG. 15C 、 FIG. 15D 、 FIG. 15E and FIG. 15F depicts simultaneous uplink transmission of PUSCH 1 and PUSCH 2 on resources that at least partially overlap in time.
[0028] FIG. 16 depicts a process flow of communications in a network between a UE and a network entity.
[0029] FIG. 17 shows a table for explaining the “Precoding information and number of layers” field of a DCI scheduling STxMP PUSCH using SRS resources over 2 ports, where the maximum rank is 1.
[0030] FIG. 18 shows a table for explaining the “Precoding information and number of layers” field of a DCI scheduling STxMP PUSCH using SRS resources over 4 ports, where the maximum rank is 1.
[0031] FIG. 19 shows a table for explaining the “Precoding information and number of layers” field of a DCI scheduling STxMP PUSCH using SRS resources over 4 ports, where the maximum rank is 2.
[0032] FIG. 20 depicts an example configuration of SRS resources, where the PUSCH ports associated with a first set of SRS resources correspond to a subset of SRS ports.
[0033] FIG. 21 depicts an example configuration of SRS resources, where at least half of the rows of a precoding matrix used for a PUSCH transmission behave as zero.
[0034] FIG. 22A and FIG. 22B illustrates examples of precoding matrices dynamically indicated by the “Precoding information and number of layers” field in a DCI, which a UE can use to determine a technique for STxMP.
[0035] FIG. 23 depicts a method for wireless communication.
[0036] FIG. 24 depicts a method for wireless communication.
[0037] FIG. 25 Aspects of an example communication device are depicted.
[0038] FIG. 26 Aspects of an example communication device are depicted. DETAILED DESCRIPTION
[0039] Aspects of the disclosure provide apparatuses, methods, processing systems, and computer readable media for indicating sounding reference signal (SRS) ports for physical uplink shared channel (PUSCH) for simultaneous transmission (STxMP) across multiple panels with shared ports.
[0040] Some wireless networks support codebook-based and non-codebook-based transmission schemes for uplink transmission. Codebook-based UL transmission is based on network configuration and can be used in cases where reciprocity can not hold.
[0041] For codebook-based uplink transmission, a UE can transmit an (uncoded) sounding reference signal (SRS) with up to 2 SRS resources, each resource with 1, 2, or 4 ports. The network (e.g., a base station or gNB) measures the SRS and, based on the measurements, selects one SRS resource and a wideband precoder (also referred to as precoding matrix) to apply to the SRS ports within the selected SRS resource. The network can configure the UE with the selected SRS resource via a SRS resource indicator (SRI) and the wideband precoder via a transmit precoding matrix indicator (TPMI). For dynamic grant, the SRI and TPMI can be configured via uplink (UL) downlink control information (DCI), e.g., scheduling a physical uplink shared channel (PUSCH). The UE determines the selected SRS resource according to the SRI and determines the precoding matrix according to the TPMI and transmits the PUSCH accordingly.
[0042] In some cases, for codebook-based uplink transmission, a UE can be configured with one SRS resource set with a “usage” set to “codebook.” The SRS resource set can have up to 4 SRS resources, and each SRS resource can be configured with multiple SRS ports (e.g., via radio resource control (RRC)). An SRI field in the UL DCI indicates one SRS resource, and the number of ports configured for the indicated SRS resource determines the number of antenna ports to use for transmitting the PUSCH, which is typically transmitted with the same spatial domain filter (UL beam) as the indicated SRS resource. The number of layers (also referred to as rank) and TPMI (indicating precoder) for the scheduled PUSCH can be determined according to a separate DCI field, e.g., which can be referred to as a “precoding information and number of layers” field.
[0043] In some cases, a UE can indicate a maximum number of SRS ports that the UE supports for beams indicated in a beam report. For example, the indication can be provided via a reported capability index, possibly based on a best antenna panel for reception or transmission (Rx / Tx) of the beams. A gNB can utilize the corresponding port number in scheduling SRS for codebook-based PUSCH in case of UL sounding, and will schedule PUSCH with a maximum number of layers limited by the maximum port number supported by the UE.
[0044] When a UE has multiple transmit antenna panels, the ports supported by the UE can generally be used for transmission via any of the antenna panels. In some cases, a UE can be configured to transmit a single uplink channel (e.g., a physical uplink shared channel (PUSCH)) via all of the digital ports and antenna panels that the UE has, while in other cases, a UE can be configured to transmit multiple uplink channels via the digital ports and antenna panels. However, the total number of digital ports supported by the UE is not affected by the UE having multiple antenna panels. Thus, when a UE is configured to transmit via multiple antenna panels, it is desirable to limit the number of ports used for each transmission so that the UE is able to make all of its scheduled transmissions without running out of ports.
[0045] Aspects of the disclosure provide techniques for configuring a UE to transmit one or more uplink channels while sharing digital ports across multiple antenna panels. The described aspects include signaling a first set of SRS ports associated with a first SRS resource of a first set of SRS resources and a second set of SRS ports associated with a second SRS resource of a second set of SRS resources. The UE can then transmit at least one PUSCH using a first set of PUSCH ports via a first antenna panel and using a second set of SRS ports via a second antenna panel.
[0046] Aspects of the disclosure provide techniques for a UE to determine whether a set of digital ports for transmission is dynamically configured or fixed based on a “precoding information and number of layers” field in downlink control information (DCI) that schedules the UE to transmit an uplink channel.
[0047] By enabling a UE to be scheduled to transmit uplink channels simultaneously with shared digital ports between panels, transmissions from the UE can be more reliably received by a network entity. Additionally, more efficient use of time and / or frequency resources in a wireless communications system can be achieved.
[0048] Introduction to Wireless Communication Networks
[0049] The techniques and methods described herein can be used for various wireless communication networks. While aspects can be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure can be applied in other communication systems and standards not explicitly mentioned.
[0050] FIG. 1 An example of a wireless communication network 100 in which aspects described herein can be implemented is depicted.
[0051] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with a network can be considered network entities. Further, the wireless communication network 100 includes ground-based aspects, such as ground-based network entities (e.g., BSs 102), and non-ground-based aspects, such as satellites 140 and aircraft 145, which can include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground-based BSs) and user equipment.
[0052] In the depicted example, the wireless communication network 100 includes BSs 102, UEs 104, and one or more core networks, such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190, that interoperate to provide communication services over various communication links, including wired and wireless links.
[0053] FIG. 1 Various example UEs 104 are depicted, which can more generally include: a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or other similar devices. A UE 104 can also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a remote unit, a remote station, a wireless unit, a remote device, a remote
[0054] The BS 102 wirelessly communicates (e.g., sends signals to and receives signals from) with the UE 104 via communication link 120. The communication link 120 between the BS 102 and the UE 104 can include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from the BS 102 to the UE 104. In various aspects, the communication link 120 can utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.
[0055] The BSs 102 can generally include NodeBs, enhanced NodeBs (eNBs), next generation enhanced NodeBs (ng-eNBs), next generation NodeBs (gNBs or gNodeBs), access points, transceiver base stations, radio base stations, radio transceivers, transceiver functions, transmission reception points, and / or the like. Each of the BSs 102 can provide communication coverage for a respective geographic area 110, which can be referred to as a cell, and which can overlap in some scenarios (e.g., small cells 102' can have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, a BS can provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area, e.g., a home), and / or other types of cells.
[0056] While the BSs 102 are depicted as single communication devices in various aspects, the BSs 102 can be implemented in various configurations. For example, one or more components of the base station can be split into a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC, to name a few examples. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., the BS 102) can include components located at a single physical location or components located at various physical locations. In examples in which the base station includes components located at various physical locations, the various components can each perform functions such that the various components collectively implement similar functionality as a base station located at a single physical location. In some aspects, a base station that includes components located at various physical locations can be referred to as a disaggregated radio access network architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. FIG. 2 An example disaggregated base station architecture is depicted and described.
[0057] Different BSs 102 within the wireless communication network 100 can be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through first backhaul links 132 (e.g., S I interface). BSs 102 configured for 5G (e.g., 5G NR, or Next Generation RAN (NG-RAN)) can interface with the 5GC 190 through second backhaul links 184. The BSs 102 can communicate with one another directly or indirectly (e.g., through the EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.
[0058] The wireless communication network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, or sub-band. For example, 3GPP currently defines frequency range 1 (FR1) to include 410-7125 MHz, which is often (interchangeably) referred to as “sub-6 GHz.” Similarly, 3GPP currently defines frequency range 2 (FR2) to include 24,250- 71,000 MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further subdivided into sub-ranges, such as a first sub-range FR2-1 including 24,250-52,600 MHz and a second sub-range FR2-2 including 52,600-71,000 MHz. Base stations configured to communicate using mmWave / near-mmWave radio frequency bands (e.g., mmWave base stations such as the BSs 180) can leverage beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.
[0059] The communication links 120 between the BSs 102 and, for example, the UEs 104 can be through one or more carriers, which can be portions of the spectrum (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) that are spectrally separated from each other but can or can not be adjacent to each other. The carriers can be according to FDD, TDD, and / or a combination thereof. The communication links 120 can be licensed or unlicensed. In examples where the communication links 120 are licensed, carriers used
[0060] Communication using higher frequency bands can have higher path loss and a shorter range as compared to lower frequency communication. Thus, certain base stations (e.g., gNBs 180) can operate in a mmWave or millimeter wave frequency range (e.g., 6 GHz to 100,000 GHz). These base stations can be referred to as mmWave base stations. The communication links 120 between the base stations 180 and the UEs 104 can be mmWave links.FIG. 1 The beams 182 of the BS 180 and the UE 104 can improve path loss and range with beamforming 182. For example, the BS 180 and the UE 104 can each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 can transmit beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 can receive the beamformed signals from the BS 180 in one or more receive directions 182". The UE 104 can also transmit beamformed signals to the BS 180 in one or more transmit directions 182". The BS 180 can also receive beamformed signals from the UE 104 in one or more receive directions 182'. Then, the BS 180 and the UE 104 can perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UE 104. Notably, the transmit and receive directions of the BS 180 can or can not be the same. Similarly, the transmit and receive directions of the UE 104 can or can not be the same.
[0061] The wireless communication network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in 2.4 GHz and / or 5 GHz unlicensed spectrum.
[0062] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can 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), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).
[0063] The EPC 160 can include various function components, including a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 can be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management.
[0064] Generally, user Internet Protocol (IP) packets are conveyed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to the IP services 176, which can include, for example, the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming sendee, and / or other IP services.
[0065] The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS Gateway 168 can be used to distribute MBMS traffic to the BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a particular service, and / or can be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0066] The 5GC 190 can include various function components including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 can be in communication with a Unified Data Management (UDM) 196.
[0067] The AMF 192 is the control node that processes the signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, quality of service (QoS) flow and session management.
[0068] Internet Protocol (IP) packets are conveyed through the UPF 195, which connects to the IP Services 197 and provides IP address allocation as well as other functions for the UE and for the 5GC 190. The IP Services 197 can include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.
[0069] In various aspects, a network entity or network node can be implemented as an aggregated base station, disaggregated base station, component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
[0070] FIG. 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture can include one or more central units (CU) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 can communicate with one or more distributed units (DU) 230 via respective fronthaul links, such as an Fl interface. The DU 230 can communicate with one or more radio units (RU) 240 via respective front-haul links. The RU 240 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 240.
[0071] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interface of the unit, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals to one or more of the other units through a wired transmission medium. Additionally or alternatively, the units can include a wireless interface, which can include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver), configured to receive signals from or transmit signals to one or more of the other units through a wireless transmission medium, or both.
[0072] In some aspects, the CU 210 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and / or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 210 can be implemented to communicate with the DU 230 for network control and signaling as needed.
[0073] The DU 230 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and / or the like) in accordance, at least in part, with a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 230 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.
[0074] The lower layer functionality can be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, and / or the like) or both based, at least in part, on a functional split, such as a lower layer functional split. In such an architecture, the RUs 240 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0075] The SMO framework 205 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 205 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform, such as Open Cloud (O-Cloud) 290, to perform network element lifecycle management, such as to instantiate virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240, and near-RT RICs 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as Open eNB (O-eNB) 211, via an Ol interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an Ol interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support functionality of the SMO framework 205.
[0076] The non-RT RIC 215 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based direction of applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to, or in communication with, the near-RT RIC 225, such as via an Al interface. The near-RT RIC 225 can be configured to include logical functions that are capable of near real-time control and optimization of RAN elements and resources via data collection and actions via an interface, such as via an E2 interface, that connects one or more CUs 210, one or more DUs 230, or both, and an O-eNB with the near-RT RIC 225.
[0077] In some implementations, to generate AI / ML models to be deployed in near-RT RIC 225, non-RT RIC 215 can receive parameters or external enrichment information from an external server. Such information can be utilized by near-RT RIC 225 and can be received at SMO framework 205 or non-RT RIC 215 from non-network data sources or from network functions. In some examples, non-RT RIC 215 or near-RT RIC 225 can be configured to tune RAN behavior or performance. For example, non-RT RIC 215 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through SMO framework 205, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.
[0078] FIG. 3 Aspects of example BS 102 and UE 104 are depicted.
[0079] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively, 334), transceivers 332a-332t (collectively, 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.
[0080] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively, 352), transceivers 354a-354r (collectively, 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360). UE 104 includes controller / processor 380 that can be configured to implement various functions described herein related to wireless communication.
[0081] With respect to example downlink transmissions, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or other. In some examples, the data can be for the physical downlink shared channel (PDSCH).
[0082] The transmit processor 320 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 can also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).
[0083] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and can provide output symbol streams to the modulators (MODs) in the transceivers 332a-t. Each modulator in transceivers 332a-t can process a respective output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-t can be transmitted via the antennas 334a-t, respectively.
[0084] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive the downlink signals from the BS 102 and can provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.
[0085] A MIMO detector 356 can obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.
[0086] With respect to example uplink transmissions, the UE 104 further includes a transmit processor 364 that can receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 380. The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 364 can be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.
[0087] At the BS 102, the uplink signals from the UE 104 can be received by the antennas 334a-334t, processed by the demodulators in the transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information transmitted by the UE 104. The receive processor 338 can provide the decoded data to a data sink 339 and to the controller / processor 340.
[0088] The memory 342 and the memory 382 can store data and program codes for the BS 102 and the UE 104, respectively.
[0089] The scheduler 344 can schedule UEs for data transmission on the downlink and / or uplink.
[0090] In various aspects, the BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms of outputting data, such as from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-332t, the antennas 334a-334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms of obtaining data, such as from the antennas 334a-334t, the transceivers 332a-332t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.
[0091] In various aspects, the UE 104 can likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms of outputting data, such as from a data source 362, a memory 382, a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms of obtaining data, such as from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, and / or other aspects described herein.
[0092] In some aspects, a processor can be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.
[0093] FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D depict aspects of data structures for a wireless communication network, such as the wireless communication network 100 of FIG. 1 .
[0094] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.
[0095] A wireless communication system can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such a system can also support half-duplex FIG. 4B and FIG. 4D The system bandwidth is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain with OFDM and / or in the time domain with single-carrier frequency division multiplexing (SC-FDM), as
[0096] The wireless communication frame structure can be frequency division duplex (FDD) where for a particular set of subcarriers, the subframes within that set of subcarriers are dedicated for either DL or UL. The wireless communication frame structure can also be time division duplex (TDD) where for a particular set of subcarriers, the subframes within that set of subcarriers are dedicated for both DL and UL.
[0097] In FIG. 4A and FIG. 4C , the wireless communication frame structure is TDD where D is DL, U is UL, and X is flexibly used between DL / UL. A UE can be configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through a received slot format indicator (SFI). In the depicted example, a 10 ms frame is divided into 10 equal sized 1 ms subframes. Each subframe can include one or more slots. In some examples, each slot can include 7 or 14 symbols, depending on the slot format. A subframe can also include mini-slots, which generally have fewer symbols than a full slot. Other wireless communication technologies can have different frame structures and / or different channels.
[0098] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (µ) 0-6 allow for 1, 2, 4, 8, 16, 32, and 64 slots per subframe, respectively. For slot configuration 1, different numerologies 0-2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology µ, there are 14 symbols / slot and 2µ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing can equal kHz, where µ is a numerology 0-6. Thus, numerology has a subcarrier spacing of 15 kHz, and numerology has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 4A 、 FIG. 4B 、 FIG. 4C and FIG. 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 µs.
[0099] As FIG. 4A 、 FIG. 4B 、 FIG. 4C and FIG. 4DAs illustrated in the example of FIG. 1A, a frame can be partitioned into multiple subframes, each subframe having multiple resource blocks (RBs) in the time domain and the frequency domain. In LTE, a resource block contains 12 subcarriers x 14 (or 16) time slots for a total of 168 (12 x 14) or 192 (12 x 16) resource elements (REs). Seven OFDM symbols are typically used to transmit each subframe. Thus, each subframe has 12 x 7 = 84 (for 14 symbols per RB) or 12 x 16 = 192 (for 16 symbols per RB) resource elements. Some of these REs carry reference (pilot) signals (RS) for the UE (e.g., 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).
[0100] As illustrated in the example of FIG. 1A, a frame can be partitioned into multiple subframes, each subframe having multiple resource blocks (RBs) in the time domain and the frequency domain. In LTE, a resource block contains 12 subcarriers x 14 (or 16) time slots for a total of 168 (12 x 14) or 192 (12 x 16) resource elements (REs). Seven OFDM symbols are typically used to transmit each subframe. Thus, each subframe has 12 x 7 = 84 (for 14 symbols per RB) or 12 x 16 = 192 (for 16 symbols per RB) resource elements. Some of these REs carry reference (pilot) signals (RS) for the UE (e.g., 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). FIG. 4A FIG. 1 As illustrated in the example of FIG. 1A, a frame can be partitioned into multiple subframes, each subframe having multiple resource blocks (RBs) in the time domain and the frequency domain. In LTE, a resource block contains 12 subcarriers x 14 (or 16) time slots for a total of 168 (12 x 14) or 192 (12 x 16) resource elements (REs). Seven OFDM symbols are typically used to transmit each subframe. Thus, each subframe has 12 x 7 = 84 (for 14 symbols per RB) or 12 x 16 = 192 (for 16 symbols per RB) resource elements. Some of these REs carry reference (pilot) signals (RS) for the UE (e.g., 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). FIG. 3
[0101] FIG. 4B
[0102] FIG. 1 FIG. 3
[0103]
[0104]
[0105] As illustrated in the example of FIG. 1A, a frame can be partitioned into multiple subframes, each subframe having multiple resource blocks (RBs) in the time domain and the frequency domain. In LTE, a resource block contains 12 subcarriers x 14 (or 16) time slots for a total of 168 (12 x 14) or 192 (12 x 16) resource elements (REs). Seven OFDM symbols are typically used to transmit each subframe. Thus, each subframe has 12 x 7 = 84 (for 14 symbols per RB) or 12 x 16 = 192 (for 16 symbols per RB) resource elements. Some of these REs carry reference (pilot) signals (RS) for the UE (e.g., 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). FIG. 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.
[0106] FIG. 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.
[0107] Overview of Codebook and Non-Codebook Based UL Transmission
[0108] Some deployments support both codebook-based and non-codebook-based transmission schemes for uplink transmission with a wideband pre-decoder (also known as a pre-decoder matrix). Codebook-based UL transmission is based on BS configuration and can be used where reciprocity may not be met.
[0109] FIG. 5 This is a call flowchart 500 illustrating an example of conventional codebook-based (CB) UL transmission using a wideband pre-decoder. The example CB-based UL transmission can occur between the UE 504 and network entity 502 (e.g., gNB). In some respects, network entity 502 may be relative to... FIG. 1 and FIG. 3 The BS 102 depicted and described or relative to FIG. 2 An example of a decomposed base station is depicted and described. Similarly, UE 504 is relative to... FIG. 1 and FIG. 3An example of UE 104 is depicted and described. However, in other respects, the UE may be another type of wireless communication device, and the network entity may be another type of network entity or network node, such as the network entity or network node described herein. As illustrated, UE 504 transmits (non-pre-decoded) SRS 510 with up to two SRS resources (SRS resource 1 and SRS resource 2), where each SRS resource has one, two, or four ports. At 515, network entity 502 measures SRS 510 and, based on the measurement, selects an SRS resource and a wideband pre-decoder to be applied to the SRS ports within the selected SRS resource. In this example, network entity 502 selects SRS resource SRS resource 2.
[0110] As illustrated, network entity 502 configures the selected SRS resources for UE 504 via SRS Resource Indicator (SRI) 520 (e.g., by signaling configuration) and configures the wideband predecoder for UE via Transmit Predecoder Matrix Indicator (TPMI) 525. For dynamic granting, SRI 520 and TPMI 525 can be configured via DCI format 0_1. For configured granting (e.g., for semi-persistent uplink), SRI 520 and TPMI 525 can be configured via RRC signaling or in the DCI.
[0111] At 530, UE 502 determines the selected SRS resource according to SRI 520 and determines the pre-decoding matrix according to TPMI 525. UE 502 uses the selected SRS resource and the pre-decoding matrix indicated by TPMI 525 to transmit PUSCH 535.
[0112] FIG. 6 This is a call flowchart 600 illustrating an example of non-codebook (NCB) based UL transmission. The example NCB-based UL transmission can occur between UE 604 and network entity 602 (e.g., gNB). In some respects, network entity 602 may be relative to... FIG. 1 and FIG. 3 The BS 102 depicted and described or relative to FIG. 2 An example of a decomposed base station is depicted and described. Similarly, UE604 is relative to... FIG. 1 and FIG. 3An example of UE 104 is depicted and described. However, in other respects, the UE may be another type of wireless communication device, and the network entity may be another type of network entity or network node, such as the network entity or network node described herein. As illustrated, network entity 602 transmits one or more DL RS 610, such as CSI-RS or SSB. At 615, UE 604 determines one or more SRS pre-decoders based on measurements of DL RS 610. UE 604 uses the pre-decoders determined at 615 to transmit pre-decoded SRS 620. Although the example shows 2 SRS resources, the UE may utilize up to 4 SRS resources for transmission (where each resource has 1 port). At 625, network entity 602 measures SRS 620 and selects one or more SRS resources from the SRS resources used by the UE when transmitting SRS 620 based on that measurement. In this scenario, since UE 604 uses a pre-decoder to transmit SRS, network entity 602 also effectively selects a pre-decoder by choosing an SRS resource (e.g., SRS resource 2). For non-codebook-based UL transmission, each SRS resource corresponds to a layer. The pre-decoder for a layer is actually the pre-decoder of the SRS emulated by the UE (e.g., by network entity 602). Selecting N SRS resources means that the rank of subsequent transmissions is N. The UE will use the same pre-decoder as the SRS to transmit PUSCH.
[0113] As illustrated, network entity 602 configures the selected SRS resource for UE 604 by sending an SRI 630 corresponding to the selected SRS resource (e.g., by sending a configuration). For dynamic granting, SRI 630 can be configured via DCI format 0_1. For configured granting, SRI can be configured via RRC signaling or in the DCI.
[0114] At 635, UE 602 determines the selected SRS resource based on SRI 630. UE 602 uses the selected SRS resource and the pre-decoding matrix used when transmitting SRS 620 corresponding to the selected SRS resource to transmit PUSCH 640.
[0115] Aspects Related to Precoding Matrix and Transmission Matrix Precoding Indicator Signaling
[0116] According to various aspects of this disclosure, when a wireless communication system uses a spatial division multiplexing (SDM) scheme with a UE sharing digital ports between antenna panels, the UE can be configured with a single maximum number of layers (e.g., 1, 2, or 4 layers) applied to a first SRS resource set and a second SRS resource set. That is, the sum of the number of layers in the first SRS resource set and the second SRS resource set is constrained to be less than or equal to the single maximum number of layers. This single maximum number of layers can be configured independently of the maximum number of layers in a single TRP (sTRP) transmission scheme (which can be configured by a parameter referred to as maxRank or Lmax).
[0117] It may be desirable to develop a technology that allows the total number of PUSCH antenna ports used by the UE for SDM and sTRP communication schemes to be the same.
[0118] In a typical communication system, for each combination of the number of layers (e.g., 1, 2, or 4) and the number of PUSCH ports, a set of pre-decoding matrices with corresponding TPMI indices can be defined (e.g., in the communication specification document). Depending on whether the pre-decoder indicates that only a single port is used for the transmit layer, only a subset of ports (more than one) is used for the transmit layer, or all ports are used for the transmit layer, the various pre-decoding matrices in this set can be described as incoherent, partially coherent, and coherent.
[0119] FIG. 7 Table 700 shows the pre-decoding matrix W and the corresponding TPMI index for single-layer transmission using two antenna ports according to various aspects of this disclosure. The pre-decoding matrix shown at 702 is incoherent because each matrix has only one non-zero value, and therefore only one of the two ports is used for the transmission layer. The pre-decoding matrix shown at 704 is coherent because all values in the matrix are non-zero, and therefore all ports are used for the transmission layer.
[0120] FIG. 8 Table 800 shows the pre-decoding matrix W and corresponding TPMI indexes for a single-layer transmission using four antenna ports according to various aspects of this disclosure, wherein transform pre-decoding is disabled. The pre-decoding matrices shown at 802 are incoherent because each matrix has only one non-zero value, and therefore only one of the four ports is used for the transmission layer. The pre-decoding matrices shown at 804 and 806 are partially coherent because each matrix has more than one (e.g., two) non-zero value and at least one zero value, and therefore only a subset of the four ports is used for the transmission layer. The remaining pre-decoding matrices shown at 808 are coherent because all values in the matrices are non-zero, and therefore all four ports are used for the transmission layer.
[0121] FIG. 9Table 900 shows a pre-decoding matrix W and corresponding TPMI indexes for two-layer transmission using four antenna ports according to various aspects of this disclosure, wherein transform pre-decoding is disabled. The pre-decoding matrix shown at 902 is incoherent because each column of each matrix has only one non-zero value, and therefore only one of the four ports is used to transmit the layer corresponding to that column. The pre-decoding matrix shown at 904 is partially coherent because each column of each matrix has more than one non-zero value and at least one zero value, and therefore only a subset of the four ports is used to transmit the layer corresponding to that column. The remaining pre-decoding matrices shown at 906 are coherent because all values in each column of the matrix are non-zero, and therefore all four ports are used to transmit the layer corresponding to each column.
[0122] The TPMI index can be indicated in the DCI field referred to as "Pre-decoding Information and Layer Count". The value transmitted in the DCI field can be used as a reference in one or more tables corresponding to different numbers of antenna ports and / or different maximum ranks. Based on these tables, the TPMI index, corresponding to the pre-decoding matrix, can be determined, such as... FIG. 7 to FIG. 9 The pre-decoding matrix is shown in the figure.
[0123] FIG. 10 Table 1000 shows the "Pre-decoding Information and Layer Number" for the four antenna ports under the following conditions: transform pre-decoding is disabled; the maximum rank is 2, 3, or 4; and "Uplink Full Power Transmission" (also known as ul-FullPowerTransmission) is not configured, configured as fullpowerMode2, or configured as fullpower. When the "Pre-decoding Information and Layer Number" field has a value between 0 and 11 (inclusive), as shown at 1002, for Layer 1 transmission, the corresponding TPMI index has a value between 0 and 3 (inclusive), and the corresponding pre-decoding matrix is incoherent, as shown in... FIG. 8 As shown at position 802. When the "Pre-decoding Information and Layer Number" field has a value between 0 and 11 (inclusive), as shown at position 1002, for Layer 2 transmission, Layer 3 transmission, and Layer 4 transmission, the corresponding TPMI index has a value between 0 and 5 (inclusive), and the corresponding pre-decoding matrix is incoherent, as shown in... FIG. 9 As shown at position 902.
[0124] When the "Pre-decoding Information and Layer Number" field has a value between 12 and 19 (inclusive), as shown at position 1004, for a Layer 1 transmission, the corresponding TPMI index has a value between 4 and 11 (inclusive), and the corresponding pre-decoding matrix is partially coherent, as shown in... FIG. 8As shown at positions 804 and 806. When the "Pre-decoding Information and Layer Number" field has a value between 20 and 27 (inclusive), as shown at position 1004, for a Layer 2 transmission, the corresponding TPMI index has a value between 6 and 13 (inclusive), and the corresponding pre-decoding matrix is partially coherent, as shown in... FIG. 9 As shown at position 904, when the "Pre-decoding Information and Layer Number" field has a value between 28 and 31 (inclusive), as shown at position 1004, for Layer 3 and Layer 4 transmissions, the corresponding TPMI index has a value of 1 or 2, and the corresponding pre-decoding matrix is partially coherent.
[0125] When the "Pre-decoding Information and Layer Number" field has a value between 32 and 47 (inclusive), as shown at position 1006, for Layer 1 transmission, the corresponding TPMI index has a value between 12 and 27 (inclusive), and the corresponding pre-decoding matrix is coherent, as shown in... FIG. 8 As shown at position 808. When the "Pre-decoding Information and Layer Number" field has a value between 48 and 55 (inclusive), as shown at position 1006, for a 2-layer transmission, the corresponding TPMI index has a value between 14 and 21 (inclusive), and the corresponding pre-decoding matrix is coherent, as shown in... FIG. 9 As shown at position 906, when the "Pre-decoding Information and Layer Number" field has a value between 56 and 59 (inclusive), as shown at position 1004, for a 3-layer transmission, the corresponding TPMI index has a value between 3 and 6 (inclusive), and the corresponding pre-decoding matrix is coherent. When the "Pre-decoding Information and Layer Number" field has a value of 60 or 61, as shown at position 1004, for a 4-layer transmission, the corresponding TPMI index has a value of 3 or 4, and the corresponding pre-decoding matrix is coherent.
[0126] FIG. 11Table 1100 shows the "Pre-decoding Information and Number of Layers" for the four antenna ports under the following conditions: Transform pre-decoding is enabled; and "Uplink Full Power Transmission" (also known as ul-FullPowerTransmission) is not configured or is configured to fullpowerMode2. Table 1100 also shows the "Pre-decoding Information and Number of Layers" for the four antenna ports under the following conditions: Transform pre-decoder is disabled; maximum rank is 1; and "Uplink Full Power Transmission" (also known as ul-FullPowerTransmission) is not configured, is configured to fullpowerMode2, or is configured to fullpower. When the "Pre-decoding Information and Number of Layers" field has a value between 0 and 3 (inclusive), as shown at 1102, the corresponding pre-decoding matrix is incoherent. When the "Pre-decoding Information and Number of Layers" field has a value between 4 and 11 (inclusive), as shown at 1104, the corresponding pre-decoding matrix is partially coherent. Furthermore, when the "predecoding information and layer number" field has a value between 12 and 27 (inclusive), as shown at position 1106, the corresponding predecoding matrix is coherent.
[0127] FIG. 12 Table 1200 shows the "Pre-decoding Information and Number of Layers" for two antenna ports under the following conditions: the transform pre-decoder is enabled; and "Uplink Full Power Transmission" (also known as ul-FullPowerTransmission) is not configured, configured as fullpowerMode2, or configured as fullpower. Table 1200 also shows the "Pre-decoding Information and Number of Layers" for two antenna ports under the following conditions: the transform pre-decoder is disabled; the maximum rank is 1; and "Uplink Full Power Transmission" (also known as ul-FullPowerTransmission) is not configured, configured as fullpowerMode2, or configured as fullpower. When the "Pre-decoding Information and Number of Layers" field has a value of 0 or 1, as shown at 1202, the corresponding pre-decoding matrix is incoherent. When the "Pre-decoding Information and Number of Layers" field has a value between 2 and 5 (inclusive), as shown at 1204, the corresponding pre-decoding matrix is coherent.
[0128] In various aspects of this disclosure, wireless communication systems can use a single DCI-based SDM PUSCH simultaneous transmission (STxMP) scheme with multiple panels for communication (e.g., transmission and reception). A simultaneous transmission scheme with two panels (of PUSCHs) may be referred to as an STx2P scheme. In such schemes, a single DCI schedules the transmission of PUSCHs with two sets of DMRS ports and / or layers, which are transmitted from two panels with different transmit beams and / or different pre-decoders and / or different power control parameters.
[0129] According to various aspects of this disclosure, in a single DCI-based SDM PUSCH STxMP scheme, two sets of layers can be associated with two SRS resource sets.
[0130] In various aspects of this disclosure, the DCI may include an SRS resource set indicator field and two SRI and / or TPMI fields. In such aspects, each of the two SRI fields indicates an SRS resource included in the SRS resource set indicated by the SRS resource set indicator field.
[0131] According to various aspects of this disclosure, dynamic switching between the sTRP scheme and the SDM scheme can be based on the SRS resource set indicator. When the SRS resource set indicator has a value of "00", the PUSCH is associated only with the first SRS resource set (which also indicates the sTRP scheme). When the SRS resource set indicator has a value of "01", the PUSCH is associated only with the second SRS resource set (which also indicates the sTRP scheme). When the SRS resource set indicator has a value of "10", the PUSCH is associated with both SRS resource sets (which also indicate the SDM scheme). When transmitting from two panels, the UE can use the following rank combinations for transmission: 1+1 layers (i.e., 1 layer on the first panel and 1 layer on the second panel), 1+2 layers (i.e., 1 layer on the first panel and 2 layers on the second panel), 2+1 layers (i.e., 2 layers on the first panel and 1 layer on the second panel), or 2+2 layers (i.e., 2 layers on the first panel and 2 layers on the second panel).
[0132] FIG. 13Example 1300 of a single-DCI-based SDM PUSCH STxMP scheme according to various aspects of this disclosure is illustrated in block form. As illustrated, a first set of layers is associated with a first TPMI or a first SRI. The first set of layers is assigned to a PUSCH port associated with the first TPMI or the first SRI. Signals for transmission in the first set of layers are transmitted via a first panel (panel 1) of the UE, and a two-layer transmission to a first TRP (TRP 1) is formed on layers 0 and 1. Similarly, a second set of layers is associated with a second TPMI or a second SRI. The second set of layers is assigned to a PUSCH port associated with the second TPMI or the second SRI. Signals for transmission in the second set of layers are transmitted via a second panel (panel 2) of the UE, and a two-layer transmission to a second TRP (TRP 2) is formed on layers 2 and 3.
[0133] In various aspects of this disclosure, the wireless communication system may use a single-frequency network (SFN) scheme. When the UE transmits an SFNPUSCH, a single DCI schedules the PUSCH, where each DMRS port and / or layer of the PUSCH is transmitted from two panels with different transmit beams, different pre-decoders, and / or different power control parameters. Each DMRS port and / or layer of the PUSCH may be associated with two SRS resource sets. The DCI scheduling the PUSCH may include an SRS resource set indicator field and two SRI fields. In such an aspect, each of the two SRI fields indicates an SRS resource included in the SRS resource set indicated by the SRS resource set indicator field.
[0134] According to various aspects of this disclosure, dynamic switching between the sTRP scheme and the SFN scheme can be based on an SRS resource set indicator. When the SRS resource set indicator has a value of "00", the PUSCH is associated only with the first SRS resource set (which also indicates the sTRP scheme). When the SRS resource set indicator has a value of "01", the PUSCH is associated only with the second SRS resource set (which also indicates the sTRP scheme). When the SRS resource set indicator has a value of "10", the PUSCH is associated with both SRS resource sets (which also indicate the SFN scheme).
[0135] FIG. 14Example 1400 of a single DCI-based SFN PUSCH STxMP scheme according to various aspects of this disclosure is shown in block form. As illustrated, a first layer is associated with a first TPMI or first SRI, and also with a second TPMI or second SRI. The first layer is assigned to the PUSCH port associated with the first TPMI or first SRI and the PUSCH port associated with the second TPMI or second SRI. Similarly, a second layer is also associated with the first TPMI or first SRI and the second TPMI or second SRI. The second layer is also assigned to the PUSCH port associated with both the first TPMI or first SRI and the second TPMI or second SRI. Signals for transmission in both layers are transmitted via the first panel (panel 1) of the UE using a first beam or TCI state, and a two-layer transmission to a first TRP (TRP 1) is formed on layers 0 and 1. The signals used for transmission in both layers are also transmitted via the second panel (panel 2) of the UE using the second beam or TCI state, and form a two-layer transmission to the second TRP (TRP 2) on layers 2 and 3.
[0136] Aspects Related to Uplink Simultaneous Transmission Across Multiple Panels
[0137] In some systems (e.g., NR Rel-18 systems), a UE can simultaneously transmit two different PUSCHs in the same serving cell (e.g., on the same component carrier (CC)) by using different panels at the UE. According to aspects of this disclosure, a wireless communication system can schedule a UE to transmit two PUSCHs using STxMP by transmitting two (or more) DCIs, such that the UE transmits two different PUSCHs in the same serving cell and / or on the same component carrier (CC) when the two PUSCHs overlap at least partially or completely in the time domain. In the frequency domain, the two PUSCHs may or may not overlap.
[0138] PUSCH can be associated with different Control Resource Set (CORESET) pool index values, different SRS resource sets, different beams, different Transmit Configuration Indicator (TCI) states, different power control parameters, and / or different pre-decoders. In some examples, one or more CORESETs are configured by RRC signaling (e.g., ControlResourceSet IE as discussed in 3GPP TS 38.331). A CORESET includes the time and frequency resources in which the UE will search for the DCI. A set of one or more CORESETs can be associated with a CORESET pool identified by a CORESET pool index value (e.g., configured in RRC signaling via the coresetPoolIndex parameter). For example, two CORESET pools can be configured with CORESET pool index values 0 and 1, respectively. In some examples, the CORESET pool index value associated with transmission can be used to determine the default quasi-co-address (QCL) assumption for transmission.
[0139] Simultaneous transmission from two different PUSCHs differs from spatial multiplexing (SDM) and / or frequency multiplexing (FDM) transmission within a single PUSCH.
[0140] The first PUSCH (associated with coresetPoolIndex value 0) may be associated with the first SRS resource set and may be transmitted using the first beam, the first TCI state, the first set of power control parameters and / or the first pre-decoder.
[0141] The second PUSCH (associated with coresetPoolIndex value 1) can be associated with the second SRS resource set and can be transmitted using the second beam, the second TCI state, the second set of power control parameters, and / or the second pre-decoder.
[0142] In the time domain, PUSCH can be scheduled and transmitted in partially or completely overlapping time domain resources. In the frequency domain, PUSCH can be scheduled and transmitted in non-overlapping, partially overlapping, or completely overlapping frequency domain resources. FIG. 15A Simultaneous uplink transmission of PUSCH 1502 (PUSCH 1) and PUSCH 1504 (PUSCH 2) over resources that are completely overlapping in the time domain and in the frequency domain is depicted. FIG. 15B Example simultaneous uplink transmissions of PUSCH 1502 and PUSCH 1504 on resources that completely overlap in the time domain and do not overlap in the frequency domain are depicted. FIG. 15C Simultaneous uplink transmissions of PUSCH 1502 and PUSCH 1504 over resources that are completely overlapping in the time domain and partially overlapping in the frequency domain are depicted. FIG. 15DExample simultaneous uplink transmissions of PUSCH1502 and PUSCH 1504 on resources that partially overlap in the time domain and do not overlap in the frequency domain are depicted. FIG. 15E Example of simultaneous uplink transmission of PUSCH 1502 and PUSCH 1504 on resources that partially overlap in the time domain and partially overlap in the frequency domain is depicted. FIG. 15F Example of simultaneous uplink transmission of PUSCH 1502 and PUSCH 1504 on resources that partially overlap in the time domain and completely overlap in the frequency domain is depicted.
[0143] In all respects of this disclosure, "shared digital port" refers to a UE capable of transmitting P PUSCH ports, regardless of whether the UE is using the STRP scheme or the STxMP scheme. Therefore, for the STxMP scheme, the sum of the PUSCH ports used associated with the first SRS resource set and the PUSCH ports used associated with the second SRS resource set should be P or less.
[0144] According to various aspects of this disclosure, in the case of a UE with a symmetrical panel, the limitation on the total number of PUSCH ports used can be satisfied by limiting the PUSCH ports used for transmission and associated with the first SRS resource set to P / 2 or less, and also limiting the PUSCH ports used for transmission and associated with the second SRS resource set to P / 2 or less.
[0145] For example, in wireless communication systems (such as FIG. 1 In system 100 shown, two SRS resource sets are configured for the UE. Each SRS resource set includes one SRS resource with P ports. For the UE's STRP or non-STxMP PUSCH transmission, one SRS resource set is indicated, and the UE can transmit P PUSCH ports, which are mapped one-to-one to P SRS ports of one of the two SRS resources. For STxMP PUSCH transmission, two SRS resource sets are indicated, but the UE cannot transmit 2P PUSCH ports, which correspond to P SRS ports of the first SRS resource and P SRS ports of the second SRS resource.
[0146] In various aspects of this disclosure, to address the problem of a UE being configured to transmit on too many ports when scheduled to perform STxMP PUSCH transmission, the PUSCH port associated with the first SRS resource set may correspond to a subset of SRS ports from the indicated SRS resources of the first SRS resource set, and the PUSCH port associated with the second SRS resource set may correspond to a subset of SRS ports from the indicated SRS resources of the second SRS resource set. The aforementioned SRS port subset may be fixed (e.g., the first P / 2 SRS ports out of P SRS ports) or may be configured using RRC. FIG. 20 The diagram illustrates how a PUSCH port associated with a first SRS resource set corresponds to a subset of SRS ports of the indicated SRS resources from the first SRS resource set, and how a PUSCH port associated with a second SRS resource set corresponds to a subset of SRS ports of the indicated SRS resources from the second SRS resource set, as will be described in more detail below.
[0147] Aspects Related to Sounding Reference Signal Port Indication for Physical Uplink Shared Channel for Simultaneous Transmission Across Multiple Panels with Shared Ports FIG. 15A to FIG. 15F
[0148] According to various aspects of this disclosure, if a UE is configured with two SRS resource sets whose purpose is set as a "codebook" and is configured to share a digital port between panels by performing simultaneous transmission across multiple panels (STxMP) (which can be set by assigning a value to an information element referred to as "shared digital port between panels"), then when the UE receives a scheduled STxMPPUSCH and indicates the DCI of the TPMI associated with one of the two SRS resource sets, the UE expects one or more (at least half) rows of the indicated pre-decoding matrix to be zero.
[0149] In all respects of this disclosure, the UE expects one or more (at least half) rows of the indicated pre-decoding matrix to be zero, which is equivalent to saying that the UE expects one or more (at least half) of the PUSCH ports and / or SRS ports to be unused.
[0150] According to various aspects of this disclosure, the communication specification may include such limitations. If the communication specification includes such limitations, the DCI for scheduling STxMP PUSCH may be similar to other DCIs (e.g., the DCI for scheduling sTRP PUSCH), wherein one or more TPMI fields in the DCI have similar bit widths.
[0151] In all respects of this disclosure, compared with other types of DCI, the DCI that schedules STxMP PUSCH may have a reduced bit width of one or more TPMI fields in the DCI.
[0152] According to various aspects of this disclosure, a new table is provided for interpreting the "pre-decoding information and layer number" field of a DCI, which includes only permitted TPMIs, such that the DCI is able to have a reduced bit width of one or more TPMI fields in the DCI compared to other types of DCIs.
[0153] In all aspects of this disclosure, a node (e.g., a UE or network entity) may determine which table to use based on at least one of the following: the number of SRS ports of the indicated SRS resources in one of the two SRS resource sets, or the maximum rank configuration of the PUSCH associated with each SRS resource set.
[0154] According to various aspects of this disclosure, the provided tables may only be used for SDM and / or SFN schemes. For multiple DCIs of multiple PUSCHs whose scheduling partially overlaps in time (as referenced above) FIG. 16 As described, whether the UE is expected to perform STxMP depends on whether the second DCI of the scheduled overlapping (i.e., second) PUSCH arrives at the UE. Therefore, for multiple DCIs of multiple PUSCHs that are scheduled to partially overlap in time, the bit width of one DCI cannot be reduced (assuming that the DCI size must be fixed regardless of the other DCIs).
[0155] The techniques provided in this article can be used as a reference. FIG. 1 This can be understood using call flowchart 1600. Call flowchart 1600 depicts an example set of communications between network entity 1602 and UE 1604. In some respects, network entity 1602 can be relative to... FIG. 3 and FIG. 2 The BS 102 depicted and described or relative to FIG. 1 Examples of decomposed base stations are depicted and described. Similarly, UE 1604 is relative to... FIG. 3 and FIG. 17 An example of UE 104 is depicted and described. However, in other respects, the UE may be another type of wireless communication device, and the network entity may be another type of network entity or network node, such as the network entity or network node described herein.
[0156] At 1606, the UE receives from the network entity a configuration for at least a first sounding reference signal (SRS) resource set and a second sounding reference signal resource set for codebook-based Physical Uplink Shared Channel (PUSCH) transmission. This configuration may be received, for example, in RRC signaling.
[0157] At 1608, the UE receives signaling from a network entity that schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE. The signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a second SRS resource set. This signaling may be, for example, one or more DCIs.
[0158] At 1610, the UE sends a PUSCH using the first set of PUSCH ports via the UE's first panel and the network entity receives at least one PUSCH using the second set of PUSCH ports via the UE's second panel.
[0159] FIG. 16 Table 1700 shows the "Pre-decoding information and layer number" fields of a DCI used to interpret scheduling STxMP PUSCHs via SRS resources through two ports, where the maximum rank is 1. Such a DCI could be an example of a DCI that simultaneously schedules at least one PUSCH using resources shared across multiple panels, as in... FIG. 12 As shown at point 1608. Compared to typical DCI, if the UE is configured with codebookSubset = fullyAndPartialAndNonCoherent, two bits can be saved when transmitting the TPMI field because the phase interference decoder is excluded. This is because the phase interference decoder (and...) is excluded. FIG. 18 In comparison, the "pre-decoding information and number of layers" field in DCI is 1 bit instead of the 3 bits used in other types of DCI.
[0160] FIG. 16 Table 1800 shows the "Pre-decoding information and layer number" fields of a DCI used to interpret scheduling STxMP PUSCHs via SRS resources across four ports, where the maximum rank is 1. Such a DCI could be an example of a DCI that simultaneously schedules at least one PUSCH across multiple panels, as shown in... FIG. 11 As shown at position 1608. Compared to a typical DCI, if the UE is configured with codebookSubset = fullyAndPartialAndNonCoherent, one bit is saved when transmitting the TPMI field because the phase interference decoder is excluded. When the "Pre-decoding Information and Layer Number" field in the DCI has a value between 0 and 3 (inclusive), as shown at position 1802, the indicated pre-decoder is incoherent. When the "Pre-decoding Information and Layer Number" field in the DCI has a value between 4 and 11 (inclusive), as shown at position 1804, the indicated pre-decoder is partially coherent. This is because the phase interference decoder (and...) is excluded.FIG. 19 In comparison, the "pre-decoding information and number of layers" field in DCI is 4 bits, instead of the 5 bits used in other types of DCI.
[0161] FIG. 16 Table 1900 illustrates the "Pre-decoding Information and Layer Number" fields of a DCI used to interpret scheduling STxMP PUSCHs via SRS resources across four ports, where the maximum rank is 2. Such a DCI could be an example of a DCI that simultaneously schedules at least one PUSCH across multiple panels, as shown in... FIG. 10 As shown at point 1608. Compared to typical DCI, if the UE is configured with codebookSubset = fullyAndPartialAndNonCoherent, one bit is saved when transmitting the TPMI field because the phase interferometry decoders for Layer 1 and Layer 2, as well as the partial phase interferometry decoder for Layer 2, are excluded. This is because the phase interferometry decoders for Layer 1 and Layer 2, as well as the partial phase interferometry decoder for Layer 2 (and...) are excluded. FIG. 16 In comparison, the "pre-decoding information and number of layers" field of the DCI is 5 bits, instead of the 6 bits used in other types of DCI. However, if the UE is configured with codebookSubset = partialAndNonCoherent, the "pre-decoding information and number of layers" field of the DCI is 5 bits, and it does not save bits compared to other types of DCI, even though partial phase interference decoders are excluded for maximum rank 2.
[0162] According to various aspects of this disclosure, a node (e.g., a UE or network entity) may consider a UE configured to transmit using a “shared digital port between panels” (i.e., STxMP) based on one or more of the following: the UE indicates the capability associated with the shared digital port; the UE receives a configuration to enable the shared digital port (e.g., via RRC signaling) (e.g., FIG. 16 The configuration at 1606), or the maximum rank parameter configured for sTRP operations (e.g., the old maximum rank) is greater than the maximum rank parameter configured for STxMP operations that is applied individually to each SRS resource set.
[0163] For example, if the UE is configured with a legacy maximum rank of 4 and a new maximum rank of 2 for SDM (i.e., the maximum number of layers for SDM PUSCH across the layers associated with the first SRS resource set and the second SRS resource set is 2+2=4), then the UE can be considered to be configured for STxMP.
[0164] In all aspects of this disclosure, "STxMP" can be implemented as an SDM or SFN PUSCH scheme. In this case, the UE can be configured with an SDM or SFN scheme by the RRC (which can be in...). FIG. 16 Example of the configuration shown at point 1606), and the DCI that schedules PUSCH (which can be in FIG. 20 The example DCI shown at 1608 indicates two SRS resource sets (i.e., the SRS resource set indicator field is set to "10"). Since the DCI for scheduling PUSCH indicates two TPMIs (associated with the first and second SRS resource sets respectively), the restriction applies to each of the two TPMIs.
[0165] According to various aspects of this disclosure, "STxMP" can be implemented as multiple DCIs scheduling multiple PUSCHs. In this case, the UE can be configured with two coresetPoolIndex values associated with two SRS resource sets, and the first DCI schedules the first PUSCH (and indicates the first TPMI), but the TPMI restriction applies only when the second DCI (associated with another coresetPoolIndex value) schedules a second PUSCH that partially / completely overlaps with the first PUSCH in time (and indicates the second TPMI). In this case, the TPMI restriction applies to both the first TPMI (indicated by the first DCI for the first PUSCH) and the second TPMI (indicated by the second DCI for the second PUSCH).
[0166] Additionally or alternatively, a limitation may be implemented on the sum of the number of non-zero rows in the first pre-decoding matrix indicated by the first TPMI and the number of non-zero rows in the second pre-decoding matrix indicated by the second TPMI. That is, the sum may be limited to be less than or equal to the number of ports in the first SRS resource (i.e., the first SRS resource set) or the second SRS resource (i.e., the second SRS resource set).
[0167] In all respects of this disclosure, the changes to DCI described above may apply to communication systems using the configured granted PUSCH (CG-PUSCH), except that for type 2 CG, TPMI is indicated by the activated DCI, and for type 1 CG, TPMI is configured by RRC.
[0168] FIG. 21An example configuration 2000 of SRS resources according to various aspects of this disclosure is shown in box form, wherein the PUSCH port associated with a first SRS resource set corresponds to a subset of SRS ports of the indicated SRS resources from the first SRS resource set, and the PUSCH port associated with a second SRS resource set corresponds to a subset of SRS ports of the indicated SRS resources from the second SRS resource set. In the example configuration 2000, ports 0 and 1 are subsets of SRS ports used as PUSCH ports when the UE is scheduled to transmit using either the first or second SRS resource set. As illustrated, the illustrated technique enables the use of an interferometric decoding matrix among P / 2 subsets of used PUSCH ports. However, the illustrated technique cannot dynamically select P / 2 ports from P ports.
[0169] FIG. 20 An example configuration 2100 of SRS resources according to various aspects of this disclosure is shown in box form, wherein at least half of the rows of the pre-decoding matrix used for PUSCH transmission are zero. The illustrated technique allows dynamic selection of P / 2 ports from P ports, as indicated by various pre-decoding matrices having non-zero values in various rows. However, when the UE is configured with 4 SRS ports and transmits at 2 layers, the illustrated technique does not allow the use of phase-interference decoding matrices or even partially phase-interference decoding matrices. For Layer 1 transmission of a UE configured with 4 SRS ports, the pre-decoding matrix can be coherent within the 2 selected ports. However, to dynamically select 2 ports from 4 ports, only groups of ports {0,2} or {1,3} can be selected, and groups of ports {0,1}, {0,3}, etc., cannot be selected. Furthermore, for Layer 2 transmission of a UE configured with 4 ports, the pre-decoding matrix cannot be coherent within the 2 selected ports.
[0170] According to various aspects of this disclosure, if the UE is configured with two SRS source sets whose purpose is set as a "codebook" and configured with a "shared digital port between panels" configured for "STxMP", then the UE can determine that it is complying with FIG. 21 The technique illustrated in the example, which uses a fixed subset of ports, still follows... FIG. 21 The techniques for dynamically selecting ports illustrated herein are (at least in part) based on one or more of the following: UE capability signaling; RRC configuration (e.g., the network can be configured with one of the illustrated techniques); and codebookSubset configuration (e.g., when codebookSubset = noncoherent or codebookSubset = partialAndNonCoherent, the UE follows the following...). FIG. 20The technique shown dynamically selects the port, but when codebookSubset = fullyAndPartialAndNonCoherent, the UE follows the following... FIG. 20 The technique shown uses fixed-group ports); or the DCI dynamically indicates the following: indicating a pre-decoder matrix of smaller size (P / 2 rows) corresponding to a fixed SRS port subset (thus indicating the technique using a fixed port subset, such as...). FIG. 21 The TPMI (as shown) or the pre-decoder matrix indicating the number of rows equal to the number of SRS ports (some of which (P / 2 rows) are zero) (thus indicating the technique for dynamically selecting ports, such as...) FIG. 22A TPMI (as shown).
[0171] FIG. 22B and FIG. 20 Examples 2200 and 2250 illustrate pre-decoding matrices dynamically indicated by the "Pre-decoding Information and Layer Number" field in the DCI, which the UE can use to determine whether to use, for example... FIG. 21 The technique shown uses a fixed subset of ports, or uses a method such as... FIG. 16 The technology shown is dynamic port selection. DCI is... FIG. 20 An example of a DCI is shown at point 1608. When a UE configured with 4 SRS ports and a maximum rank of 2 receives a DCI with a "Pre-decoding Information and Layer Number" field indicating one of the pre-decoding matrices shown in Example 2200, the UE can determine to use, as shown in the example... FIG. 21 The technique shown uses a fixed subset of ports, and a fixed subset of SRS ports, such as ports 0 and 1. When a UE configured with 4 SRS ports and a maximum rank of 2 receives a DCI with a "Pre-decoding Information and Layer Number" field indicating one of the pre-decoding matrices shown in Example 2250, the UE can determine whether to use a pre-decoding matrix as shown in Example 2250. Example Operations The technique shown dynamically selects ports and transmits using a dynamically indicated subset of SRS ports, but without using any phase-interference decoder matrix.
[0172] According to various aspects of this disclosure, the DCI can dynamically indicate a subset of SRS ports (e.g., P / 2 ports out of P SRS ports) and then indicate the TPMI across the selected ports (where P / 2 rows in the pre-decoder matrix are indicated by the TPMI). This makes it possible to use the phase-intervention decoder matrix with a dynamically signaled subset of ports.
[0173] In all aspects of this disclosure, signaling for port selection and TPMI can be performed using a field in the DCI (e.g., the "Pre-decoding Information and Layer Number" field) or by separate fields in the DCI (e.g., a new field indicating port selection and the "Pre-decoding Information and Layer Number" field indicating TPMI and layer number).
[0174] FIG. 23
[0175] FIG. 1 It shows the UE (such as FIG. 3 and FIG. 25 Example of a method 2300 for wireless communication of UE 104.
[0176] Method 2300 begins at step 2305, wherein configuration for at least a first SRS resource set and a second SRS resource set for codebook-based PUSCH transmission is received from the network entity. In some cases, the operation of this step refers to, as described in reference... FIG. 25 The circuitry described for receiving and / or the code for receiving, or the circuitry and / or the code that can be executed.
[0177] Then, method 2300 proceeds to step 2310, wherein signaling is received from a network entity, which schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a second SRS resource set. In some cases, the operation of this step refers to, as referenced FIG. 25 The circuitry described for receiving and / or the code for receiving, or the circuitry and / or the code that can be executed.
[0178] Then, method 2300 proceeds to step 2315, in which at least one PUSCH is transmitted via the first panel of the UE using the first set of PUSCH ports and via the second panel of the UE using the second set of PUSCH ports. In some cases, this step refers to the operation as described in the reference. FIG. 25 The circuitry described for transmitting and / or the code for transmitting, or the circuitry and / or the code that can be executed.
[0179] In some respects, the signaling includes a DCI with a field indicating a TPMI index associated with at least one of the first SRS resource set or the second SRS resource set.
[0180] In some respects, one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, which indicate the corresponding PUSCH port that is not used to send at least one PUSCH.
[0181] In some respects, when a DCI-scheduled UE uses an uplink port shared by multiple panels across the UE to simultaneously transmit at least one PUSCH, the TPMI field is restricted to a limited number of valid values.
[0182] In some respects, the UE uses an uplink port shared by multiple panels across the UE to simultaneously send at least one set of tables defined by the PUSCH to interpret the TPMI fields.
[0183] In some respects, the UE selects one of the tables in the first set based on the following: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first and second SRS resource sets.
[0184] In some aspects, method 2300 further includes determining that the uplink port is shared across multiple panels of the UE based on at least one of the following: the UE transmits signaling indicating the UE's ability to support uplink ports shared across multiple panels of the UE; the UE receives signaling enabling the sharing of uplink ports across multiple panels of the UE; or the maximum rank parameter configured for a single PUSCH transmission is greater than the maximum rank parameter configured for simultaneous PUSCH transmissions on multiple panels. In some cases, this step refers to operations as described in reference... FIG. 25 The circuit described is used for determination and / or the code used for determination, or can be executed by the circuit and / or the code.
[0185] In some aspects, signaling: scheduling the UE to transmit at least one PUSCH simultaneously via SDM or SFN; and indicating a separate TPMI index associated with the first SRS resource set and the second SRS resource set.
[0186] In some aspects, the signaling includes: a first DCI that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0187] In some respects, there are limitations on the number of PUSCH ports in the first group and the sum of the number of PUSCH ports in the second group.
[0188] In some respects, the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0189] In some aspects, method 2300 further includes determining when signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with a second SRS resource set based on at least one of: UE capability signaling; RRC signaling; codebook subset configuration; or indication in DCI. In some cases, the operation of this step refers to, as referenced FIG. 23 The circuit described is used for determination and / or the code used for determination, or can be executed by the circuit and / or the code.
[0190] In one aspect, method 2300 or any aspect thereof may be made by means of a device (such as...) FIG. 24 The communication device 2500 performs the operation, and the device includes various components capable of operating, configured, or adapted to perform the method 2300. The communication device 2500 is described in more detail below.
[0191] It should be noted that FIG. 1 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.
[0192] FIG. 3 This shows the network entities (such as FIG. 2 and FIG. 26 (BS 102) or as relative to FIG. 26 An example of a method 2400 for wireless communication at a decomposed base station is discussed.
[0193] Method 2400 begins at step 2405, wherein the configuration of at least a first SRS resource set and a second SRS resource set for codebook-based PUSCH transmission is sent to the UE. In some cases, the operation of this step refers to, as described in reference... FIG. 26 The circuitry described for transmitting and / or the code for transmitting, or the circuitry and / or the code that can be executed.
[0194] Then, method 2400 proceeds to step 2410, wherein signaling is sent to the UE, which schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in a second SRS resource set. In some cases, the operation of this step refers to, as referenced FIG. 26 The circuitry described for transmitting and / or the code for transmitting, or the circuitry and / or the code that can be executed.
[0195] Then, method 2400 proceeds to step 2415, wherein at least one PUSCH is received, wherein the at least one PUSCH is transmitted via the first panel of the UE using a first set of PUSCH ports and via the second panel of the UE using a second set of PUSCH ports. In some cases, the operation of this step refers to as described in reference FIG. 26 The circuitry described for receiving and / or the code for receiving, or the circuitry and / or the code that can be executed.
[0196] In some respects, the signaling includes a DCI with a field indicating a TPMI index associated with at least one of the first SRS resource set or the second SRS resource set.
[0197] In some respects, one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, which indicate the corresponding PUSCH port that is not used to send at least one PUSCH.
[0198] In some respects, when a DCI-scheduled UE uses an uplink port shared by multiple panels across the UE to simultaneously transmit at least one PUSCH, the TPMI field is restricted to a limited number of valid values.
[0199] In some respects, the UE uses an uplink port shared by multiple panels across the UE to simultaneously send at least one set of tables defined by the PUSCH to interpret the TPMI fields.
[0200] In some respects, the UE selects one of the tables in the first set based on the following: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first and second SRS resource sets.
[0201] In some aspects, method 2400 further includes determining that the uplink port is shared across multiple panels of the UE based on at least one of the following: receiving from the UE signaling an indication that the UE supports the capability of sharing an uplink port across multiple panels of the UE; sending to the UE signaling enabling the sharing of uplink ports across multiple panels of the UE; or sending a maximum rank parameter configured for a single PUSCH that is greater than the maximum rank parameter configured for simultaneous PUSCH transmissions on multiple panels. In some cases, this step refers to operations as described in reference FIG. 26 The circuit described is used for determination and / or the code used for determination, or can be executed by the circuit and / or the code.
[0202] In some aspects, signaling: scheduling the UE to transmit at least one PUSCH simultaneously via SDM or SFN; and indicating a separate TPMI index associated with the first SRS resource set and the second SRS resource set.
[0203] In some aspects, the signaling includes: a first DCI that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0204] In some respects, there are limitations on the number of PUSCH ports in the first group and the sum of the number of PUSCH ports in the second group.
[0205] In some respects, the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0206] In some aspects, method 2400 further includes: determining, based on UE capability signaling, when signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with a second SRS resource set. In some cases, this step refers to the operation as described in reference... FIG. 26 The circuit described is used for determination and / or the code used for determination, or can be executed by the circuit and / or the code.
[0207] In some aspects, method 2400 further includes: indicating, via at least one of the following, that a first set of PUSCH ports corresponding to a subset of SRS ports is associated with a first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports is associated with a second SRS resource set: RRC signaling; codebook subset configuration; or indication in DCI. In some cases, the operation of this step refers to, as referenced FIG. 24 The circuitry described for indication and / or the code for indication, or the circuitry and / or the code that can be executed.
[0208] In one aspect, method 2400 or any aspect thereof may be made by means of a device (such as...) Example Communication Devices The communication device 2600 performs the method, which includes various components capable of operating, configured, or adapted to perform the method 2400. The communication device 2600 is described in more detail below.
[0209] It should be noted that FIG. 25 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.
[0210] FIG. 1
[0211] FIG. 3Various aspects of the example communication device 2500 are described. In some aspects, the communication device 2500 is user equipment, such as those described above relative to... FIG. 3 and FIG. 23 The UE 104 described.
[0212] The communication device 2500 includes a processing system 2505 coupled to a transceiver 2555 (e.g., a transmitter and / or receiver). The transceiver 2555 is configured to transmit and receive signals from the communication device 2500 via an antenna 2560, such as the various signals described herein. The processing system 2505 may be configured to perform processing functions of the communication device 2500, including processing signals received by and / or to be transmitted by the communication device 2500.
[0213] Processing system 2505 includes one or more processors 2510. In various aspects, the one or more processors 2510 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... FIG. 23 As described. One or more processors 2510 are coupled to a computer-readable medium / memory 2530 via a bus 2550. In some aspects, the computer-readable medium / memory 2530 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 2510, cause the one or more processors 2510 to perform relative to FIG. 23 The method 2300 described or any aspect thereof. Note that reference to a processor performing the functions of the communication device 2500 may include one or more processors 2510 performing those functions of the communication device 2500.
[0214] In the depicted example, computer-readable medium / memory 2530 stores code (e.g., executable instructions), such as code 2535 for receiving, code 2540 for transmitting, and code 2545 for determining. Processing the code 2535 for receiving, the code 2540 for transmitting, and the code 2545 for determining enables the communication device 2500 to perform actions relative to... FIG. 23 The method described is 2300 or any aspect thereof.
[0215] One or more processors 2510 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 2530, including circuitry such as circuitry 2515 for receiving, circuitry 2520 for transmitting, and circuitry 2525 for determining. Processing performed using the circuitry 2515 for receiving, the circuitry 2520 for transmitting, and the circuitry 2525 for determining enables the communication device 2500 to perform operations relative to... FIG. 3The method described is 2300 or any aspect thereof.
[0216] The various components of the communication device 2500 can provide for performing relative to FIG. 25 The described method 2300 or any component related thereto. For example, components for transmitting, conveying, or outputting to perform the transmission may include... FIG. 3 The transceiver 354 and / or antenna 352 of the UE 104 illustrated in the figure FIG. 25 The communication device 2500 includes a transceiver 2555 and an antenna 2560. Components for receiving or acquiring data may include... FIG. 26 The transceiver 354 and / or antenna 352 of the UE 104 illustrated in the figure FIG. 1 The transceiver 2555 and antenna 2560 of the communication equipment 2500.
[0217] FIG. 3 Various aspects of the example communication device 2600 are described. In some aspects, the communication device 2600 is a network entity, such as... FIG. 2 and FIG. 2 BS 102 or as relative to FIG. 3 The decomposed base station is discussed.
[0218] Communication device 2600 includes a processing system 2605 coupled to a transceiver 2665 (e.g., a transmitter and / or receiver) and / or a network interface 2675. Transceiver 2665 is configured to transmit and receive signals from communication device 2600 via antenna 2670, such as various signals as described herein. Network interface 2675 is configured to transmit and receive signals from communication device 2600 via a communication link (such as those described herein, such as relative to...). FIG. 24 The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals from the communication device 2600. The processing system 2605 can be configured to perform the processing functions of the communication device 2600, including processing signals received by and / or to be transmitted by the communication device 2600.
[0219] Processing system 2605 includes one or more processors 2610. In various aspects, the one or more processors 2610 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as relative to... FIG. 24 As described. One or more processors 2610 are coupled to a computer-readable medium / memory 2635 via a bus 2660. In some aspects, the computer-readable medium / memory 2635 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2610, cause one or more processors 2610 to perform relative to FIG. 24The method 2400 described or any aspect thereof. Note that reference to a processor of the communication device 2600 performing the function may include one or more processors 2610 of the communication device 2600 performing the function.
[0220] In the depicted example, computer-readable medium / memory 2635 stores code (e.g., executable instructions), such as code 2640 for transmitting, code 2645 for receiving, code 2650 for determining, and code 2655 for indicating. Processing the code 2640 for transmitting, the code 2645 for receiving, the code 2650 for determining, and the code 2655 for indicating enables the communication device 2600 to perform actions relative to... FIG. 24 The method described is 2400 or any aspect thereof.
[0221] One or more processors 2610 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2635, including circuitry such as circuitry 2615 for transmitting, circuitry 2620 for receiving, circuitry 2625 for determining, and circuitry 2630 for indicating. Processing using the circuitry 2615 for transmitting, the circuitry 2620 for receiving, the circuitry 2625 for determining, and the circuitry 2630 for indicating enables the communication device 2600 to perform operations relative to... FIG. 3 The method described is 2400 or any aspect thereof.
[0222] The various components of the communication device 2600 can provide for performing relative to FIG. 26 The described method 2400 or any related components. Components used for sending, transmitting, or outputting to perform the transmission may include... FIG. 3 The transceiver 332 and / or antenna 334 of the BS102 illustrated in the figure are... FIG. 26 The communication device 2600 includes a transceiver 2665 and an antenna 2670. Components for receiving or acquiring data may include... Example Clauses The transceiver 332 and / or antenna 334 of the BS 102 illustrated in the figure are... Additional Notes The transceiver 2665 and antenna 2670 of the communication device 2600.
[0223]
[0224] Specific implementation examples are described in the following numbered clauses:
[0225] Clause 1: A method for wireless communication by a UE, the method comprising: receiving from a network entity the configuration of at least a first SRS resource set and a second SRS resource set for codebook-based PUSCH transmission; receiving from the network entity signaling that the signaling schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across a plurality of panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set; and transmitting the at least one PUSCH via a first panel of the UE using the first set of PUSCH ports and via a second panel of the UE using the second set of PUSCH ports.
[0226] Clause 2: The method according to Clause 1, wherein the signaling includes a DCI having a field indicating a TPMI index associated with at least one of the first SRS resource set or the second SRS resource set.
[0227] Clause 3: The method according to Clause 2, wherein one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
[0228] Clause 4: The method according to Clause 3, wherein when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE, the TPMI field is restricted to a limited number of valid values.
[0229] Clause 5: The method according to Clause 3, wherein: the UE uses a first set of tables defined by the at least one PUSCH to interpret the TPMI field by simultaneously sending an uplink port shared across multiple panels of the UE.
[0230] Clause 6: The method according to Clause 5, wherein the UE selects one of the first set of tables based on the following: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
[0231] Clause 7: The method according to any one of Clauses 1 to 6, the method further comprising: determining that an uplink port is shared across multiple panels of the UE based on at least one of the following: the UE sends signaling indicating the UE's ability to support an uplink port shared across multiple panels of the UE; the UE receives signaling enabling the sharing of uplink ports across multiple panels of the UE; or the maximum rank parameter configured for a single PUSCH transmission is greater than the maximum rank parameter configured for simultaneous PUSCH transmission on multiple panels.
[0232] Clause 8: The method according to any one of Clauses 1 to 7, wherein the signaling: schedules the UE to transmit the at least one PUSCH simultaneously via SDM or SFN; and indicates a separate TPMI index associated with the first SRS resource set and the second SRS resource set.
[0233] Clause 9: The method according to any one of Clauses 1 to 8, wherein the signaling comprises: a first DCI that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0234] Clause 10: The method according to any one of Clauses 1 to 9, wherein there is a limitation on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
[0235] Clause 11: The method according to Clause 10, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0236] Clause 12: The method according to any one of Clauses 1 to 11 further comprises determining when the signaling indicates a first set of PUSCH ports corresponding to the SRS port subset associated with the first SRS resource set and a second set of PUSCH ports corresponding to the SRS port subset associated with the second SRS resource set based on at least one of the following: UE capability signaling; RRC signaling; codebook subset configuration; or indication in DCI.
[0237] Clause 13: A method for wireless communication by a network entity, the method comprising: sending to a UE the configuration of at least a first SRS resource set and a second SRS resource set for codebook-based PUSCH transmission; sending to the UE signaling that the signaling schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across a plurality of panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set; and receiving the at least one PUSCH, wherein the at least one PUSCH is transmitted via a first panel of the UE using the first set of PUSCH ports and via a second panel of the UE using the second set of PUSCH ports.
[0238] Clause 14: The method according to Clause 13, wherein the signaling includes a DCI having a field indicating a TPMI index associated with at least one of the first SRS resource set or the second SRS resource set.
[0239] Clause 15: The method according to Clause 14, wherein one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
[0240] Clause 16: The method according to Clause 15, wherein when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE, the TPMI field is restricted to a limited number of valid values.
[0241] Clause 17: The method according to Clause 15, wherein: the UE uses a first set of tables defined by the at least one PUSCH to interpret the TPMI field by simultaneously sending an uplink port shared across multiple panels of the UE.
[0242] Clause 18: The method according to Clause 17, wherein the UE selects one of the first set of tables based on the following: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
[0243] Clause 19: The method according to any one of Clauses 13 to 18, the method further comprising: determining that an uplink port is shared across multiple panels of the UE based on at least one of the following: receiving from the UE signaling an indication that the UE supports the capability of the uplink port to be shared across multiple panels of the UE; sending to the UE signaling enabling the sharing of the uplink port across multiple panels of the UE; or sending a maximum rank parameter configured for a single PUSCH that is greater than the maximum rank parameter configured for simultaneous PUSCH transmission on multiple panels.
[0244] Clause 20: The method according to any one of Clauses 13 to 19, wherein the signaling: schedules the UE to transmit the at least one PUSCH simultaneously via SDM or SFN; and indicates a separate TPMI index associated with the first SRS resource set and the second SRS resource set.
[0245] Clause 21: The method according to any one of Clauses 13 to 20, wherein the signaling comprises: a first DCI that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0246] Clause 22: The method according to any one of Clauses 13 to 21, wherein there is a limitation on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
[0247] Clause 23: The method according to Clause 22, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0248] Clause 24: The method according to any one of Clauses 13 to 23, the method further comprising: determining, based on UE capability signaling, when the signaling indicates a first set of PUSCH ports associated with the first SRS resource set corresponding to the subset of SRS ports and a second set of PUSCH ports associated with the second SRS resource set corresponding to the subset of SRS ports.
[0249] Clause 25: The method according to any one of Clauses 13 to 24, the method further comprising: indicating, via at least one of the following, that the first set of PUSCH ports corresponding to the subset of SRS ports is associated with the first SRS resource set and the second set of PUSCH ports corresponding to the subset of SRS ports is associated with the second SRS resource set: RRC signaling; codebook subset configuration; or indication in DCI.
[0250] Clause 26: An apparatus comprising: at least one memory including executable instructions; and one or more processors configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 1 to 25.
[0251] Clause 27: An apparatus comprising: a component for performing the method according to any one of Clauses 1 to 25.
[0252] Clause 28: A non-transitory computer-readable medium comprising: executable instructions that, when executed by a processor of a device, cause the device to perform a method according to any one of Clauses 1 to 25.
[0253] Clause 29: A computer program product embodied on a computer-readable storage medium, said computer-readable storage medium including code for performing the method according to any one of Clauses 1 to 25.
[0254] Clause 30: A user equipment (UE) configured for wireless communication, the UE comprising: a memory including computer-executable instructions; and a processor configured to execute the computer-executable instructions and cause the UE to: receive from a network entity a configuration for transmitting at least a first set of sounding reference signals (SRS) resources and a second set of sounding reference signals resources for codebook-based Physical Uplink Shared Channel (PUSCH) transmission; receive from the network entity signaling that the UE uses uplink ports shared across a plurality of panels of the UE to simultaneously transmit at least one PUSCH, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first set of SRS resources and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second set of SRS resources; and transmit the at least one PUSCH using the first set of PUSCH ports via a first panel of the UE and using the second set of PUSCH ports via a second panel of the UE.
[0255] Clause 31: The UE according to Clause 30, wherein the processor is configured to execute the computer-executable instructions to cause the UE to receive the signaling, comprises: the processor being configured to execute the computer-executable instructions and cause the UE to receive downlink control information (DCI) having a field indicating a transmit pre-decoding matrix indicator (TPMI) index associated with at least one of the first SRS resource set or the second SRS resource set.
[0256] Clause 32: The UE according to Clause 31, wherein one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
[0257] Clause 33: The UE as described in Clause 32, wherein when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE, the TPMI field is restricted to a limited number of valid values.
[0258] Clause 34: The UE according to Clause 32, wherein the processor is configured to execute the computer-executable instructions and further cause the UE to: interpret the TPMI field by simultaneously sending a first set of tables defined by the at least one PUSCH for use with an uplink port shared across multiple panels of the UE.
[0259] Clause 35: The UE according to Clause 34, wherein the processor is configured to execute the computer-executable instructions and further causes the UE to select one of the first set of tables based on the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
[0260] Clause 36: The UE according to Clause 30, wherein the processor is configured to execute the computer-executable instructions and further causes the UE to determine that the uplink port is shared across multiple panels of the UE based on at least one of the following: the UE sends signaling indicating the UE's ability to support an uplink port shared across multiple panels of the UE; the UE receives signaling enabling the sharing of uplink ports across multiple panels of the UE; or the maximum rank parameter configured for a single PUSCH is greater than the maximum rank parameter configured for simultaneous PUSCH transmissions on multiple panels.
[0261] Clause 37: The UE according to Clause 30, wherein the processor is configured to execute the computer-executable instructions and, based on the signaling, further cause the UE to: transmit simultaneously the at least one PUSCH via spatial division multiplexing (SDM) or a single-frequency network (SFN); and determine a separate Transmit Predecoding Matrix Indicator (TPMI) index associated with the first SRS resource set and the second SRS resource set.
[0262] Clause 38: The UE according to Clause 30, wherein the processor is configured to execute the computer-executable instructions and cause the UE to receive the signaling comprises: the processor being configured to execute the computer-executable instructions and cause the UE to receive: a first downlink control information (DCI) that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0263] Clause 39: The UE as described in Clause 30, wherein there is a limit on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
[0264] Clause 40: The UE as described in Clause 39, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0265] Clause 41: The UE according to Clause 30, wherein the processor is configured to execute the computer-executable instructions and further causes the UE to determine when the signaling indicates the first set of PUSCH ports corresponding to the SRS port subset associated with the first SRS resource set and the second set of PUSCH ports corresponding to the SRS port subset associated with the second SRS resource set based on at least one of the following: the UE's capability signaling; Radio Resource Control (RRC) signaling; Codebook subset configuration; or indications in downlink control information (DCI).
[0266] Clause 42: A network entity configured for wireless communication, the network entity comprising: a memory including computer-executable instructions; and a processor configured to execute the computer-executable instructions and cause the network entity to: transmit to a user equipment (UE) a configuration of at least a first set of sounding reference signals (SRS) resources and a second set of sounding reference signals resources for codebook-based Physical Uplink Shared Channel (PUSCH) transmission; transmit to the UE signaling that the signaling schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across a plurality of panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first set of SRS resources and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second set of SRS resources; and receive the at least one PUSCH, wherein the at least one PUSCH is transmitted using the first set of PUSCH ports via a first panel of the UE and using the second set of PUSCH ports via a second panel of the UE.
[0267] Clause 43: A network entity according to Clause 42, wherein the processor is configured to execute the computer-executable instructions and cause the network entity to send the signaling comprises: the processor being configured to execute the computer-executable instructions and cause the network entity to send downlink control information (DCI) having a field indicating a transmit pre-decoding matrix indicator (TPMI) index associated with at least one of the first SRS resource set or the second SRS resource set.
[0268] Clause 44: A network entity pursuant to Clause 43, wherein the processor is configured to execute the computer-executable instructions and further causes the network entity to select the TPMI index such that one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
[0269] Clause 45: A network entity pursuant to Clause 44, wherein the processor is configured to execute the computer-executable instructions, and further causes the network entity to: restrict the TPMI field to a limited number of valid values when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE.
[0270] Clause 46: The network entity as described in Clause 44, wherein the processor is configured to execute the computer-executable instructions and further causes the network entity to: select the TPMI field based on a first set of tables of the at least one PUSCH definition to be sent simultaneously for use with an uplink port shared across multiple panels of the UE.
[0271] Clause 47: A network entity pursuant to Clause 46, wherein the processor is configured to execute the computer-executable instructions and further causes the network entity to select one of the first set of tables based on the following: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
[0272] Clause 48: A network entity pursuant to Clause 42, wherein the processor is configured to execute the computer-executable instructions and further causes the network entity to determine that an uplink port is shared across multiple panels of the UE based on at least one of the following: receiving from the UE signaling an indication that the UE supports the capability of sharing an uplink port across multiple panels of the UE; sending to the UE signaling enabling the sharing of uplink ports across multiple panels of the UE; or sending a maximum rank parameter configured for a single PUSCH that is greater than the maximum rank parameter configured for simultaneous PUSCHs on multiple panels.
[0273] Clause 49: A network entity pursuant to Clause 42, wherein the processor is configured to execute the computer-executable instructions and cause the network entity to send the signaling, includes the processor being configured to execute the computer-executable instructions and cause the network entity to: schedule the UE to simultaneously transmit the at least one PUSCH via a spatial division multiplexing (SDM) or single-frequency network (SFN); and indicate separate transmit pre-decoding matrix indicator (TPMI) indices associated with the first SRS resource set and the second SRS resource set.
[0274] Clause 50: A network entity pursuant to Clause 42, wherein the processor is configured to execute the computer-executable instructions and cause the network entity to send the signaling includes the processor being configured to execute the computer-executable instructions and cause the network entity to send: a first downlink control information (DCI) that schedules a first PUSCH and indicates a first TPMI; and a second DCI that schedules a second PUSCH that at least partially overlaps with the first PUSCH in time and indicates a second TPMI.
[0275] Clause 51: A network entity pursuant to Clause 42, wherein the processor is configured to execute the computer-executable instructions and cause the network entity to send the signaling based on a limit on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
[0276] Clause 52: A network entity as described in Clause 51, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
[0277] Clause 53: A network entity pursuant to Clause 42, wherein the processor is configured to execute the computer-executable instructions and further enables the network entity to determine, based on UE capability signaling, when the signaling indicates the first set of PUSCH ports associated with the first SRS resource set corresponding to the subset of SRS ports and the second set of PUSCH ports associated with the second SRS resource set corresponding to the subset of SRS ports.
[0278] Clause 54: The method according to Clause 42, wherein the processor is configured to execute the computer-executable instructions and further cause the network entity to indicate, via at least one of the following: Radio Resource Control (RRC) signaling; codebook subset configuration; or indication in downlink control information (DCI).
[0279]
[0280] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of these claims.
[0281] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.
[0282] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items (including single members). For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).
[0283] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, and so on. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.
[0284] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.
[0285] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” means one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is expressly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person skilled in the art or will later be known are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the UE to: The configuration of at least a first sounding reference signal (SRS) resource set and a second sounding reference signal resource set for codebook-based Physical Uplink Shared Channel (PUSCH) transmission is received from the network entity. The signaling received from the network entity schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set. as well as The at least one PUSCH is transmitted via the first panel of the UE using the first set of PUSCH ports and via the second panel of the UE using the second set of PUSCH ports.
2. The apparatus of claim 1, wherein receiving the signaling comprises: Receive downlink control information (DCI) with a field indicating a transmit pre-decoding matrix indicator (TPMI) index associated with at least one of the first SRS resource set or the second SRS resource set.
3. The apparatus of claim 2, wherein one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
4. The apparatus of claim 3, wherein when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE, the TPMI field is restricted to a limited number of valid values.
5. The apparatus of claim 3, wherein the one or more processors are further configured to cause the UE to: The TPMI field is interpreted by simultaneously sending the first set of tables defined by the at least one PUSCH using an uplink port shared across multiple panels of the UE.
6. The apparatus of claim 5, wherein the one or more processors are further configured to cause the UE to select one of the first set of tables based on the number of SRS ports of the SRS resources indicated in the DCI and a maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
7. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to determine, based on at least one of the following: The UE sends a signaling indicating the UE's ability to support uplink ports shared across multiple panels of the UE; The UE receives signaling that enables sharing of uplink ports across multiple panels of the UE; or The maximum rank parameter for a single PUSCH transmission configuration is greater than the maximum rank parameter for simultaneous PUSCH transmission configurations across multiple panels.
8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Simultaneously transmit at least one PUSCH via spatial division multiplexing (SDM) or single-frequency network (SFN); and Determine the individual Transmit Predecoding Matrix Indicator (TPMI) index associated with the first SRS resource set and the second SRS resource set.
9. The apparatus of claim 1, wherein receiving the signaling includes receiving: Schedule the first PUSCH and indicate the first downlink control information (DCI) of the first TPMI; and The second PUSCH is scheduled to at least partially overlap with the first PUSCH in time and the second DCI is indicated by the second TPMI.
10. The apparatus of claim 1, wherein there is a limitation on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
11. The apparatus of claim 10, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
12. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to determine, based on at least one of the following, when the signaling indicates the first set of PUSCH ports corresponding to the subset of SRS ports associated with the first SRS resource set and the second set of PUSCH ports corresponding to the subset of SRS ports associated with the second SRS resource set: The UE's capability signaling; Radio Resource Control (RRC) signaling; Codebook subset configuration; or Indications in the downlink control information (DCI).
13. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the network entity to: The configuration of at least a first sounding reference signal (SRS) resource set and a second sounding reference signal resource set for codebook-based Physical Uplink Shared Channel (PUSCH) transmission is sent to the User Equipment (UE). Sending signaling to the UE, the signaling scheduling the UE to simultaneously send at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set. as well as Receive the at least one PUSCH, wherein the at least one PUSCH is transmitted via the first panel of the UE using the first set of PUSCH ports and via the second panel of the UE using the second set of PUSCH ports.
14. The apparatus of claim 13, wherein sending the signaling comprises: Send downlink control information (DCI) with a field indicating a transmit pre-decoding matrix indicator (TPMI) index associated with at least one of the first SRS resource set or the second SRS resource set.
15. The apparatus of claim 14, wherein the one or more processors are further configured to cause the network entity to select the TPMI index such that one or more rows of the pre-decoding matrix indicated by the TPMI index have zero values, the zero values indicating a corresponding PUSCH port not used for transmitting the at least one PUSCH.
16. The apparatus of claim 15, wherein the one or more processors are further configured to cause the network entity to restrict the TPMI field to a limited number of valid values when the DCI schedules the UE to simultaneously transmit the at least one PUSCH using an uplink port shared across multiple panels of the UE.
17. The apparatus of claim 15, wherein the one or more processors are further configured to cause the network entity to: The TPMI field is selected based on a first set of tables defined by simultaneously sending the at least one PUSCH using an uplink port shared across multiple panels of the UE.
18. The apparatus of claim 17, wherein the one or more processors are further configured to cause the network entity to select one of the first set of tables based on: the number of SRS ports of the SRS resources indicated in the DCI and the maximum rank configuration for PUSCH associated with each of the first SRS resource set and the second SRS resource set.
19. The apparatus of claim 13, wherein the one or more processors are further configured to cause the network entity to determine, based on at least one of the following: Receive signaling from the UE indicating the UE's ability to support uplink ports shared across multiple panels of the UE; Send signaling to the UE to enable sharing of uplink ports across multiple panels of the UE; or The maximum rank parameter for a single PUSCH transmission configuration is greater than the maximum rank parameter for simultaneous PUSCH transmission configurations across multiple panels.
20. The apparatus of claim 13, wherein sending the signaling includes causing the network entity to: The UE is scheduled to transmit at least one PUSCH simultaneously via spatial division multiplexing (SDM) or single-frequency network (SFN); and Indicates the separate Transmit Predecoding Matrix Indicator (TPMI) index associated with the first SRS resource set and the second SRS resource set.
21. The apparatus of claim 13, wherein sending the signaling comprises sending: Schedule the first PUSCH and indicate the first downlink control information (DCI) of the first TPMI; and The second PUSCH is scheduled to at least partially overlap with the first PUSCH in time and the second DCI is indicated by the second TPMI.
22. The apparatus of claim 13, wherein the one or more processors are further configured to cause the network entity to send the signaling based on a limit on the sum of the number of PUSCH ports in the first group and the number of PUSCH ports in the second group.
23. The apparatus of claim 22, wherein the limitation is based on the number of SRS ports in the SRS resources of the first SRS resource set or the SRS resources of the second SRS resource set.
24. The apparatus of claim 13, wherein the one or more processors are further configured to cause the network entity to determine, based on UE capability signaling, when the signaling indicates a first set of PUSCH ports corresponding to the subset of SRS ports associated with the first SRS resource set and a second set of PUSCH ports corresponding to the subset of SRS ports associated with the second SRS resource set.
25. The apparatus of claim 13, wherein the one or more processors are further configured to cause the network entity to associate the first set of PUSCH ports corresponding to the subset of SRS ports with the first SRS resource set and the second set of PUSCH ports corresponding to the subset of SRS ports with the second SRS resource set via at least one of the following: Radio Resource Control (RRC) signaling; Codebook subset configuration; or Indications in the downlink control information (DCI).
26. A method for wireless communication by a user equipment (UE), the method comprising: The configuration of at least a first sounding reference signal (SRS) resource set and a second sounding reference signal resource set for codebook-based Physical Uplink Shared Channel (PUSCH) transmission is received from the network entity. The signaling received from the network entity schedules the UE to simultaneously transmit at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set. as well as The at least one PUSCH is transmitted via the first panel of the UE using the first set of PUSCH ports and via the second panel of the UE using the second set of PUSCH ports.
27. The method of claim 26, wherein the signaling includes downlink control information (DCI) having a field indicating a transmit pre-decoding matrix indicator (TPMI) index associated with at least one of the first SRS resource set or the second SRS resource set.
28. The method of claim 26, further comprising: The uplink port is determined to be shared across multiple panels of the UE based on at least one of the following: The UE sends a signaling indicating the UE's ability to support uplink ports shared across multiple panels of the UE; The UE receives signaling that enables sharing of uplink ports across multiple panels of the UE; or The maximum rank parameter for a single PUSCH transmission configuration is greater than the maximum rank parameter for simultaneous PUSCH transmission configurations across multiple panels.
29. The method according to claim 26, wherein: The signaling schedules the UE to simultaneously transmit the at least one PUSCH via spatial multiplexing (SDM) or a single-frequency network (SFN); and The signaling indicates a separate Transmit Predecoding Matrix Indicator (TPMI) index associated with the first SRS resource set and the second SRS resource set.
30. A method for wireless communication by a network entity, the method comprising: The configuration of at least a first sounding reference signal (SRS) resource set and a second sounding reference signal resource set for codebook-based Physical Uplink Shared Channel (PUSCH) transmission is sent to the User Equipment (UE). Sending signaling to the UE, the signaling scheduling the UE to simultaneously send at least one PUSCH using uplink ports shared across multiple panels of the UE, wherein the signaling indicates a first set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the first SRS resource set and a second set of PUSCH ports corresponding to a subset of SRS ports associated with SRS resources in the second SRS resource set. as well as Receive the at least one PUSCH, wherein the at least one PUSCH is transmitted via the first panel of the UE using the first set of PUSCH ports and via the second panel of the UE using the second set of PUSCH ports.