CN112272930A - Spatial multiplexing of Physical Uplink Control Channel (PUCCH) and Sounding Reference Signal (SRS) - Google Patents

Abstract

Designs for spatial multiplexing of uplink channels are provided. A User Equipment (UE) detects that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted. The UE decides to spatially multiplex the PUCCH and SRS for simultaneous transmission via different sets of one or more antennas. The UE determines time and frequency resources for the PUCCH and SRS to avoid collision of at least a portion of the PUCCH with the SRS. The UE transmits the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

Description

Spatial multiplexing of Physical Uplink Control Channel (PUCCH) and Sounding Reference Signal (SRS)

This application claims priority to U.S. application No.16/431,973, filed 6/5/2019, which claims priority AND benefit to greek provisional application No.20180100253 entitled "SPATIALLY MULTIPLEXING PHYSICAL UPLINK CONTROL CHANNEL (PUCCH) AND SOUNDINGs REFERENCE SIGNAL (SRS)" filed 6/8/2018, both of which are expressly incorporated herein by reference in their entirety.

Technical Field

Aspects of the present disclosure relate to wireless communications, and more particularly, to spatially multiplexing a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS).

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, and so on. These wireless communication systems may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include third generation partnership project (3GPP) Long Term Evolution (LTE) systems, LTE-advanced (LTE-a) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.

In some examples, a wireless multiple-access communication system may include multiple Base Stations (BSs), each capable of supporting communication for multiple communication devices (otherwise referred to as User Equipments (UEs)) simultaneously. In an LTE or LTE-a network, a set of one or more base stations may define an evolved node b (enb). In other examples (e.g., in a next generation, New Radio (NR), or 5G network), a wireless multiple-access communication system may include a plurality of Distributed Units (DUs) (e.g., Edge Units (EUs), Edge Nodes (ENs), Radio Heads (RHs), intelligent radio heads (SRHs), Transmission Reception Points (TRPs), etc.) in communication with a plurality of Central Units (CUs) (e.g., Central Nodes (CNs), Access Node Controllers (ANCs), etc.), wherein a set of one or more distributed units in communication with the center may define an access node (e.g., which may be referred to as a base station, a 5G NB, a next generation node B (gNB or gnnodeb), a TRP, etc.). A base station or distributed unit may communicate with a set of UEs on downlink channels (e.g., for transmissions from or to the base station or UE) and uplink channels (e.g., for transmissions from or to the UE).

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate on a city, country, region, and even global level. New Radios (NR) (e.g., 5G) are an example of an emerging telecommunications standard. NR is an enhanced set of LTE mobile standards promulgated by 3 GPP. It is designed to better integrate with other open standards by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using OFDMA with Cyclic Prefix (CP) on the Downlink (DL) and on the Uplink (UL), thereby better supporting mobile broadband internet access. For this reason, NR supports beamforming, Multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access techniques and telecommunications standards employing these techniques.

Disclosure of Invention

The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the claims that follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "detailed description" one will understand how the features of this disclosure provide advantages that include improved communication between access points and stations in a wireless network.

Certain aspects provide a method for wireless communications by a User Equipment (UE). In summary, the method comprises: detecting that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted; deciding to spatially multiplex the PUCCH and the SRS for simultaneous transmission via different sets of one or more antennas; determining time and frequency resources for the PUCCH and the SRS to avoid collision of at least a portion of the PUCCH with the SRS; transmitting the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

In one aspect, the detecting comprises: detecting that the PUCCH and the SRS are configured or scheduled to be transmitted in the same OFDM symbol.

In one aspect, the portion includes a demodulation reference signal (DMRS).

In one aspect, determining the time and frequency resources comprises: determining different time and frequency resources for the DMRS and the SRS.

In an aspect, the PUCCH is according to PUCCH format 1, 3 or 4.

In one aspect, determining the time and frequency resources comprises: determining that the SRS and the DMRS are to be transmitted on different OFDM symbols.

In one aspect, determining the time and frequency resources comprises: determining that the SRS is to be transmitted on the same OFDM symbol in a different resource block than the DMRS.

In one aspect, determining the time and frequency resources comprises: determining that the SRS is to be transmitted in the same resource block and in the same OFDM symbol as the DMRS, wherein the SRS is scheduled on Resource Elements (REs) that are not scheduled for the DMRS.

In an aspect, the PUCCH is according to PUCCH format 2.

In an aspect, detecting that the PUCCH and the SRS are to be transmitted simultaneously comprises: detecting that the SRS is to be transmitted on the same OFDM symbol in the same resource block as the DMRS.

In one aspect, determining the time and frequency resources comprises: determining a comb pattern for the SRS that is the same as the comb pattern for the DMRS; and determining resources for the SRS on subcarriers not occupied by the DMRS based on the determined comb pattern.

In an aspect, detecting that the PUCCH and the SRS are to be transmitted simultaneously comprises: detecting that at least a remaining portion of the PUCCH and the SRS are configured to be transmitted on a same OFDM symbol of a same resource block.

In one aspect, determining the time and frequency resources comprises: determining the same OFDM symbol of the same resource block for transmission of the remaining portion and the SRS if the SRS is at least one of X resource blocks wide or Y times wider than the PUCCH.

In an aspect, the values of X and Y are determined based on at least one of an SRS use case or a format of the PUCCH.

In one aspect, the values of X and Y are configured via Radio Resource Control (RRC) signaling.

In one aspect, determining the time and frequency resources further comprises: determining a puncturing pattern for the SRS; and determining resources for the remaining portion by puncturing Resource Elements (REs) scheduled for the SRS based on the puncturing pattern.

In an aspect, the puncturing pattern is based on a format of the PUCCH.

In one aspect, the determining further comprises: rate matching the transmission of the SRS around the transmission of the remaining portion.

In one aspect, the remaining portion includes Uplink Control Information (UCI).

Certain aspects provide a method for wireless communications by a User Equipment (UE). In summary, the method comprises: deciding to spatially multiplex a Physical Uplink Shared Channel (PUSCH) and a Sounding Reference Signal (SRS) for simultaneous transmission via different sets of one or more antennas; determining that Uplink Control Information (UCI) is to be transmitted using resources assigned for the PUSCH and determining that at least a portion of time and frequency resources for the PUSCH is to be used for transmission of the SRS; determining a resource mapping pattern for mapping the UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS; mapping the UCI to the PUSCH resources based on the resource mapping pattern; and transmitting the spatially multiplexed PUSCH and SRS after the mapping.

In one aspect, the mapping comprises: mapping at least a portion of UCI bits indicating acknowledgement/negative acknowledgement (ACK/NACK) using the PUSCH resources not used for the SRS.

In one aspect, the mapping comprises: after mapping the at least a portion of the UCI bits indicating ACK/NACK, mapping a remaining portion of the UCI bits indicating ACK/NACK and at least a portion of the UCI bits indicating Channel State Indication (CSI) using the PUSCH resources to be used for SRS.

In one aspect, the mapping comprises: before mapping a UCI bit indicating a Channel Status Indication (CSI), a UCI bit indicating acknowledgement/negative acknowledgement (ACK/NACK) is mapped.

Certain aspects provide a method for wireless communications by a Base Station (BS). In summary, the method comprises: indicating to a User Equipment (UE) that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted within a same component carrier via different sets of one or more antennas at the UE; determining time and frequency resources for the PUCCH and the SRS to avoid collision of at least a portion of the PUCCH with the SRS; signaling the determined time and frequency resources to the UE; and receiving the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

In one aspect, the indication comprises: configuring or scheduling the UE to transmit the PUCCH and SRS in a same OFDM symbol.

In one aspect, the portion includes an uplink demodulation reference signal (DMRS).

In one aspect, determining the time and frequency resources comprises: determining different time and frequency resources for the DMRS and the SRS.

In an aspect, the PUCCH is according to PUCCH format 1, 3 or 4.

In one aspect, determining the time and frequency resources comprises: determining that the SRS and the DMRS are to be received on different OFDM symbols.

In one aspect, determining the time and frequency resources comprises: determining that the SRS is to be received on the same OFDM symbol in a different resource block than the DMRS.

In one aspect, determining the time and frequency resources comprises: determining that the SRS is to be received in a same resource block and in a same OFDM symbol as the DMRS, wherein the SRS is scheduled on Resource Elements (REs) that are not scheduled for the DMRS.

In an aspect, the PUCCH is according to PUCCH format 2.

In an aspect, it is determined that the SRS is to be received on the same OFDM symbol in the same resource block as the DMRS.

In one aspect, determining the time and frequency resources comprises: determining a comb pattern for the SRS that is the same as the comb pattern for the DMRS; and determining resources for the SRS on subcarriers not occupied by the DMRS based on the determined comb pattern.

In one aspect, determining the time and frequency resources comprises: determining that at least a remaining portion of the PUCCH and the SRS are to be transmitted by the UE on a same OFDM symbol of a same resource block.

In one aspect, determining the time and frequency resources comprises: determining the same OFDM symbol for receiving the remaining portion and the same resource block of the SRS if the SRS is at least one of X resource blocks wide or Y times wider than the PUCCH.

In an aspect, the values of X and Y are based on at least one of an SRS use case or a format of the PUCCH.

In one aspect, further comprising: transmitting the values of X and Y to the UE via Radio Resource Control (RRC) signaling.

In one aspect, determining the time and frequency resources further comprises: determining a puncturing pattern for the SRS; and determining resources for the remaining portion by puncturing Resource Elements (REs) scheduled for the SRS based on the puncturing pattern.

In an aspect, the puncturing pattern is based on a format of the PUCCH.

In one aspect, the remaining portion includes Uplink Control Information (UCI).

Certain aspects provide a method for wireless communications by a Base Station (BS). In summary, the method comprises: deciding that a Physical Uplink Shared Channel (PUSCH) and a Sounding Reference Signal (SRS) are to be spatially multiplexed for simultaneous transmission from a UE via different sets of one or more antennas at the UE; indicating the spatial multiplexing to the UE; detecting that Uplink Control Information (UCI) is to be received using resources assigned for the PUSCH, and detecting that at least a portion of time and frequency resources for the PUSCH is to be used for receiving the Sounding Reference Signal (SRS); determining a resource mapping pattern for mapping the UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS; and receiving the UCI based on the resource mapping pattern.

In one aspect, the resource mapping schema includes: mapping at least a portion of UCI bits indicating acknowledgement/negative acknowledgement (ACK/NACK) using the PUSCH resources not used for the SRS.

In one aspect, the resource mapping schema includes: after mapping at least a portion of the UCI bits indicating ACK/NACK, mapping a remaining portion of the UCI bits indicating ACK/NACK and at least a portion of the UCI bits indicating Channel State Indication (CSI) using the PUSCH resources to be used for SRS.

In one aspect, the resource mapping schema includes: before mapping UCI bits indicating Channel State Indication (CSI), UCI bits indicating acknowledgement are mapped.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

Fig. 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

Fig. 2 is a block diagram illustrating an example logical architecture of a distributed Radio Access Network (RAN) in accordance with certain aspects of the present disclosure.

Fig. 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

Fig. 4 is a block diagram conceptually illustrating a design of an example Base Station (BS) and User Equipment (UE), in accordance with certain aspects of the present disclosure.

Fig. 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

Fig. 6 illustrates an example of a frame format for a New Radio (NR) system in accordance with certain aspects of the present disclosure.

Fig. 7A illustrates spatial multiplexing of UL SRS and UL PUCCH according to certain aspects of the present disclosure.

Fig. 7B illustrates spatial multiplexing of UL SRS and UL PUSCH (including piggybacked UCI) in accordance with certain aspects of the present disclosure.

Fig. 8 illustrates example operations performed by a User Equipment (UE) for spatial multiplexing of uplink channels in accordance with certain aspects of the present disclosure.

Fig. 9 illustrates example operations performed by a Base Station (BS) for spatial multiplexing of uplink channels in accordance with certain aspects of the present disclosure.

Fig. 10 illustrates spatially multiplexing SRS with PUCCH format 2 in accordance with certain aspects of the present disclosure.

Fig. 11 illustrates example operations for mapping UCI to PUSCH resources when PDSCH collides with SRS, in accordance with certain aspects of the present disclosure.

Fig. 12 illustrates example operations performed by a Base Station (BS) for mapping UCI to PUSCH resources when PUSCH collides with SRS, in accordance with certain aspects of the present disclosure.

Fig. 13-16 illustrate a communication device that may include various components configured to perform operations for the techniques disclosed herein, in accordance with aspects of the present disclosure.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.

Detailed Description

One constraint for uplink transmission in 5G NR (e.g., according to release 15) is: when a UE is assigned only one Component Carrier (CC), the UE is allowed to transmit only one uplink channel at a time. Multiple uplink channels (e.g., PUCCH, PUSCH, SRS, etc.) can only be Time Division Multiplexed (TDM) within one CC. The NR standard does not allow multiple uplink channels to be transmitted at one time within one CC using any other multiplexing mechanism (e.g., Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), etc.).

One problem with this constraint is: this results in channel collision if the UE has multiple uplink channels configured to transmit simultaneously. In such a case, the UE must drop one or more channels to support a particular channel or must follow complex rules to resolve the conflict.

In certain aspects, future NR versions are likely to support multiple uplink transmit antennas/transmit chains at the UE. In certain aspects, having multiple transmit antennas/transmit chains allows a UE to send multiple uplink channels to the gNB simultaneously in the same time and frequency resources using spatial multiplexing within the same CC.

Certain aspects of the present disclosure discuss a design for: two or more uplink control channels for a UE supporting multiple uplink transmit antennas are spatially multiplexed. For example, spatial multiplexing of SRS and PUCCH includes transmitting SRS using a first set of one or more UL antennas and transmitting PUCCH using a second set of one or more UL antennas different from the first set.

The following description provides examples, but does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than that described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Moreover, the scope of the present disclosure is intended to cover such an apparatus or method implemented with other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.

The techniques described herein may be used for various wireless communication technologies such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includes wideband CDMA (wcdma) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, flash-OFDMA, and the like. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

New Radios (NR) are emerging wireless communication technologies under development that incorporate the 5G technology forum (5 GTF). 3GPP Long Term Evolution (LTE) and LTE-advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization entitled "third Generation partnership project" (3 GPP). Cdma2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although aspects may be described herein using terms commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure may be applied to other generation-based communication systems (e.g., 5G and beyond technologies, including NR technologies).

New Radio (NR) access (e.g., 5G technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidths (e.g., 80MHz or more), millimeter wave (mmW) targeting high carrier frequencies (e.g., 25GHz or more), massive Machine Type Communication (MTC) targeting non-backward compatible MTC technologies, and/or mission critical targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different Transmission Time Intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services may coexist in the same subframe.

Example Wireless communication System

Fig. 1 illustrates an example wireless communication network 100 in which aspects of the disclosure may be performed. For example, the wireless communication network 100 may be a New Radio (NR) or 5G network. In one aspect, each of BSs 110 and each of UEs 120 may be configured to perform operations related to spatially multiplexing PUCCH and SRS, according to aspects described herein.

As shown in fig. 1, wireless network 100 may include a plurality of Base Stations (BSs) 110 and other network entities. A BS may be a station that communicates with a User Equipment (UE). Each BS 110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a node B (nb) and/or a node B subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and next generation node B (gNB or gnnodeb), new radio base station (NR BS), 5G NB, Access Point (AP), Transmission Reception Point (TRP) may be interchanged. In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile BS. In some examples, the base stations may be interconnected with each other and/or with one or more other base stations or network nodes (not shown) in the wireless communication network 100 by various types of backhaul interfaces (e.g., interfaces that are directly physical connections, wireless connections, virtual networks, or use any suitable transport networks).

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. Frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, subbands, and so on. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks having different RATs. In some cases, NR or 5G RAT networks may be deployed.

A Base Station (BS) may provide communication coverage for a macrocell, picocell, femtocell, and/or other types of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the residence, etc.). The BS for the macro cell may be referred to as a macro BS. The BS for the pico cell may be referred to as a pico BS. The BS for the femto cell may be referred to as a femto BS or a home BS. In the example shown in fig. 1, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102 x. BSs 110y and 110z may be femto BSs for femtocells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

The wireless communication network 100 may also include relay stations. A relay station is a station that receives data transmissions and/or other information from an upstream station (e.g., a BS or a UE) and transmits data transmissions and/or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown in fig. 1, relay station 110r may communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120 r. The relay station may also be referred to as a relay BS, a relay, etc.

The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, repeaters, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 20 watts), while pico BSs, femto BSs, and repeaters may have a lower transmit power level (e.g., 1 watt).

The wireless communication network 100 may support synchronous operation or asynchronous operation. For synchronous operation, BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timings, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operations.

Network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. Network controller 130 may communicate with BS 110 via a backhaul. BSs 110 may also communicate with one another (e.g., directly or indirectly), e.g., via a wireless or wired backhaul.

UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular telephone, a smartphone, a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a cordless telephone, a Wireless Local Loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device (e.g., a smartwatch, a smart garment, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.)), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter/sensor, an industrial manufacturing device, a smart meter/sensor, a smart phone, a smart, A global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium. Some UEs may be considered Machine Type Communication (MTC) devices or evolved MTC (emtc) devices. MTC and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc., which may communicate with a BS, another device (e.g., a remote device), or some other entity. The wireless nodes may provide connectivity, for example, to or from a network (e.g., a wide area network such as the internet or a cellular network) via wired or wireless communication links. Some UEs may be considered internet of things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, and so on. Each subcarrier may be modulated with data. Typically, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing of the subcarriers may be 15kHz and the minimum resource allocation (referred to as a "resource block" (RB)) may be 12 subcarriers (or 180 kHz). Thus, for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal Fast Fourier Transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a sub-band may cover 1.08MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 sub-bands for a system bandwidth of 1.25, 2.5, 5, 10, or 20MHz, respectively.

Although aspects of the examples described herein may be associated with LTE technology, aspects of the disclosure may be applied with other wireless communication systems (e.g., NRs). NR may utilize OFDM with CP on the uplink and downlink, and may include support for half-duplex operation using TDD. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmission with precoding may also be supported. A MIMO configuration in the DL may support up to 8 transmit antennas, with a multi-layer DL transmitting up to 8 streams and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE may be supported. Aggregation of multiple cells with up to 8 serving cells may be supported.

In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication among some or all of the devices and apparatuses within its service area or cell. The scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may serve as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communications. In some examples, the UE may serve as a scheduling entity in a peer-to-peer (P2P) network and/or in a mesh network. In the mesh network example, in addition to communicating with the scheduling entity, the UEs may also communicate directly with each other.

In fig. 1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. The thin dashed line with double arrows indicates the interfering transmission between the UE and the BS.

Fig. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN)200 that may be implemented in the wireless communication network 100 shown in fig. 1. The 5G access node 206 may include an Access Node Controller (ANC) 202. ANC 202 may be a Central Unit (CU) of distributed RAN 200. The backhaul interface to the next generation core network (NG-CN)204 may terminate at ANC 202. The backhaul interface to the neighboring next generation access node (NG-AN)210 may terminate at ANC 202. ANC 202 may include one or more Transmit Receive Points (TRPs) 208 (e.g., cells, BSs, gnbs, etc.).

TRP 208 may be a Distributed Unit (DU). The TRP 208 may be connected to one ANC (e.g., ANC 202) or more than one ANC (not shown). For example, for RAN sharing, radio as a service (RaaS), AND service-specific AND deployments, the TRP 208 may be connected to more than one ANC. TRPs 208 may each include one or more antenna ports. TRP 208 may be configured to provide services to UEs individually (e.g., dynamic selection) or jointly (e.g., joint transmission).

The logical architecture of the distributed RAN 200 may support a fronthaul scheme across different deployment types. For example, the logical architecture may be based on the transmitting network capabilities (e.g., bandwidth, latency, and/or jitter).

The logical architecture of the distributed RAN 200 may share features and/or components with LTE. For example, a next generation access node (NG-AN)210 may support dual connectivity with NRs and may share a common fronthaul for LTE and NRs.

The logical architecture of the distributed RAN 200 may enable cooperation between and among TRPs 208, e.g., within and/or across the TRP via ANC 202. The inter-TRP interface may not be used.

The logical functions may be dynamically distributed in the logical architecture of the distributed RAN 200. As will be described in more detail with reference to fig. 5, a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer may be adaptively placed at a DU (e.g., TRP 208) or a CU (e.g., ANC 202).

Fig. 3 illustrates an example physical architecture of a distributed Radio Access Network (RAN)300 in accordance with aspects of the present disclosure. A centralized core network unit (C-CU)302 may host core network functions. C-CUs 302 may be centrally deployed. The C-CU 302 functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

A centralized RAN unit (C-RU)304 may host one or more ANC functions. Alternatively, C-RU 304 may locally host core network functions. C-RU 304 may have a distributed deployment. The C-RU 304 may be near the network edge.

DU 306 may host one or more TRPs (edge node (EN), Edge Unit (EU), Radio Head (RH), Smart Radio Head (SRH), etc.). The DU may be located at the edge of a Radio Frequency (RF) enabled network.

Fig. 4 shows example components of BS 110 and UE 120 (as depicted in fig. 1) that may be used to implement aspects of the present disclosure. For example, antennas 452, processors 466, 458, 464, and/or controller/processor 480 of UE 120, and/or antennas 434, processors 420, 460, 438, and/or controller/processor 440 of BS 110 may be used to perform various techniques and methods described herein. In one aspect, BS 110 and UE 120 may be configured to perform operations related to spatially multiplexing PUCCH and SRS, according to aspects described herein.

At BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be used for a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), a group common PDCCH (gc PDCCH), etc. The data may be for a Physical Downlink Shared Channel (PDSCH), etc. Processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Processor 420 may also generate reference symbols, e.g., for Primary Synchronization Signals (PSS), Secondary Synchronization Signals (SSS), and cell-specific reference signals (CRS). A Transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to Modulators (MODs) 432a through 432 t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

At UE 120, antennas 452a through 452r may receive downlink signals from base station 110 and may provide received signals to demodulators (DEMODs) 454a through 454r, respectively, in the transceivers. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.

On the uplink, at UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a Physical Uplink Shared Channel (PUSCH)) and control information from a controller/processor 480 (e.g., for a Physical Uplink Control Channel (PUCCH)). Transmit processor 464 may also generate reference symbols for a reference signal (e.g., for a Sounding Reference Signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At BS 110, the uplink signals from UE 120 may be received by antennas 434, processed by modulators 432, detected by a MIMO detector 436 (if applicable), and further processed by a receive processor 438 to obtain decoded data and control information sent by UE 120. A receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller/processor 440.

Controllers/ processors 440 and 480 may direct the operation at base station 110 and UE 120, respectively. Processor 440 and/or other processors and modules at base station 110 may perform or direct the performance of processes for the techniques described herein. Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.

Fig. 5 shows a diagram 500 depicting an example for implementing a communication protocol stack, in accordance with aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a wireless communication system, such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 shows a communication protocol stack that includes a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, the layers of the protocol stack may be implemented as separate software modules, portions of a processor or ASIC, portions of non-co-located devices connected by a communications link, or various combinations thereof. The co-located and non-co-located implementations may be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and/or DU) or UE.

A first option 505-a illustrates a split implementation of a protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., ANC 202 in fig. 2) and a distributed network access device (e.g., DU 208 in fig. 2). In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, while the RLC layer 520, the MAC layer 525 and the physical layer 530 may be implemented by DUs. In various examples, a CU and a DU may be co-located or non-co-located. The first option 505-a may be useful in a macrocell, microcell, or picocell deployment.

A second option 505-b illustrates a unified implementation of a protocol stack, wherein the protocol stack is implemented in a single network access device. In a second option, the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and physical layer 530 may all be implemented by AN. The second option 505-b may be useful in, for example, a femtocell deployment.

Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and physical layer 530) as shown in 505-c.

In LTE, the basic Transmission Time Interval (TTI), or packet duration, is a 1ms subframe. In NR, the subframe is still 1ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16.. slots), depending on the subcarrier spacing. NR RB is 12 consecutive frequency subcarriers. NR may support a basic subcarrier spacing of 15KHz and other subcarrier spacings may be defined relative to the basic subcarrier spacing, e.g., 30KHz, 60KHz, 120KHz, 240KHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

Fig. 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10ms) and may be divided into 10 subframes with indices of 0 through 9, each subframe being 1 ms. Each subframe may include a variable number of slots, depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. An index may be assigned to a symbol period in each slot. A minislot is a sub-slot structure (e.g., 2, 3, or 4 symbols).

Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission, and the link direction for each subframe may be dynamically switched. The link direction may be based on a slot format. Each slot may include DL/UL data as well as DL/UL control information.

In NR, a Synchronization Signal (SS) block is transmitted. The SS block includes PSS, SSs, and two-symbol PBCH. The SS blocks may be transmitted in fixed slot positions (e.g., symbols 0-3 as shown in fig. 6). The PSS and SSS may be used by the UE for cell search and acquisition. The PSS may provide half-frame timing and the SS may provide CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries certain basic system information such as downlink system bandwidth, timing information within the radio frame, SS burst aggregation period, system frame numbering, etc. The SS blocks may be organized into SS bursts to support beam scanning. Additional system information, such as Remaining Minimum System Information (RMSI), System Information Blocks (SIBs), Other System Information (OSI), may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

In some cases, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Such live-life applications with sidelink communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, internet of everything (IoE) communications, IoT communications, mission critical meshes, and/or various other suitable applications. In general, sidelink signals may refer to signals transmitted from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without the need to relay the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and/or control purposes. In some examples, the sidelink signals may be transmitted using licensed spectrum (as opposed to wireless local area networks that typically use unlicensed spectrum).

The UE may operate in various radio resource configurations including configurations associated with transmitting pilots using a set of dedicated resources (e.g., a Radio Resource Control (RRC) dedicated state, etc.), or configurations associated with transmitting pilots using a set of common resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting pilot signals to the network. When operating in the RRC common state, the UE may select a common set of resources for transmitting pilot signals to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices (e.g., AN or DU or portions thereof). Each receiving network access device may be configured to receive and measure pilot signals transmitted on a common set of resources, and also receive and measure pilot signals transmitted on a set of dedicated resources allocated to UEs for which the network access device is a member of the set of network access devices monitoring for the UE. CUs receiving one or more of the network access devices, or receiving measurements to which the network access devices send pilot signals, may use the measurements to identify serving cells for the UEs, or initiate changes to serving cells for one or more of the UEs.

Example designs for spatial multiplexing of Physical Uplink Control Channel (PUCCH) and Sounding Reference Signal (SRS)

One constraint for uplink transmission in 5G NR (e.g., according to release 15) is: the UE is allowed to transmit only one uplink channel at a time within one Component Carrier (CC). Multiple uplink channels (e.g., PUCCH, PUSCH, SRS, etc.) can only be Time Division Multiplexed (TDM) within one CC. The NR standard does not allow multiple uplink channels to be transmitted at one time within one CC using any other multiplexing mechanism (e.g., Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), etc.).

One problem with this constraint is: this results in channel collision if the UE has multiple uplink channels configured or scheduled to transmit simultaneously. In such a case, the UE must drop one or more channels to support a particular channel or must follow complex rules to resolve the conflict.

In certain aspects, future NR versions are likely to support multiple uplink transmit antennas/transmit chains at the UE. In certain aspects, having multiple transmit antennas/transmit chains allows a UE to send multiple uplink channels to the gNB simultaneously in the same time and frequency resources using spatial multiplexing within the same CC.

Certain aspects of the present disclosure discuss designs for spatially multiplexing two or more uplink control channels for a UE supporting multiple uplink transmit antennas. For example, spatial multiplexing of SRS and PUCCH includes transmitting SRS using a first set of one or more UL antennas and transmitting PUCCH using a second set of one or more UL antennas different from the first set.

Fig. 7A illustrates spatial multiplexing of UL SRS and UL PUCCH according to certain aspects of the present disclosure. As shown, UE 702 has four antennas and transmits UL SRS and UL PUCCH as separate spatially multiplexed streams to gNB 704. In an aspect, the UE may transmit UL SRS using one or more of the four UE antennas and may transmit UL PUCCH using one or more remaining antennas.

In certain aspects, the PUCCH generally includes a portion assigned for Uplink Control Information (UCI) and a remaining portion assigned for demodulation reference signals (DMRS). As mentioned in the following description, when spatially multiplexing SRS and PUCCH, it may be beneficial to avoid collision of resources (e.g., time/frequency resources) scheduled for SRS and DMRS.

In certain aspects, when PUCCH and PUSCH are configured to be transmitted in the same symbol or symbols, the standard allows for piggybacking UCI bits on PUSCH resources, e.g., by transmitting at least a portion of the UCI bits using PUSCH resources. Fig. 7B illustrates spatial multiplexing of UL SRS and PUSCH (including piggybacked UCI) in accordance with certain aspects of the present disclosure. As shown, UE 702 sends UL SRS and UL PUSCH as separate spatially multiplexed streams to gNB 704. In an aspect, the UE may transmit UL SRS using one or more of the four UE antennas and may transmit UL PUSCH using one or more remaining antennas. As mentioned in the following description, when spatially multiplexing the SRS and the PUSCH including the piggybacked UCI, it may be beneficial to avoid collision of resources (e.g., time/frequency resources) scheduled for the SRS and the UCI. Further, as discussed in certain aspects, if collision of the UCI and SRS is unavoidable, the UE attempts to avoid collision of at least the ACK/NACK portion of the UCI with the SRS.

The gNB typically uses DMRS to estimate the UL channel between the UE and the gNB. In certain aspects, it may be beneficial to avoid collision of resources (e.g., time/frequency resources) scheduled for SRS and DMRS. In an aspect, as long as the gmb correctly receives and decodes the DMRS, the gmb may separate the UCI and SRS based on the DMRS even if their respective resources collide. In certain aspects, when spatially multiplexing SRS and PUCCH (as shown in fig. 7A), one or more rules may be defined to avoid collision of resources scheduled for the DMRS portions of SRS and PUCCH. In this context, collision of resources refers to scheduling two channels on the same OFDM symbol and the same Resource Block (RB) and possibly the same Resource Elements (REs).

Fig. 8 illustrates example operations 800 performed by a User Equipment (UE) for spatial multiplexing of uplink channels in accordance with certain aspects of the present disclosure. At 802, the operations 800 begin by: the detection PUCCH and SRS will be transmitted simultaneously. For example, the PUCCH and SRS are configured (e.g., via RRC signaling) or scheduled (e.g., via DCI) to be transmitted in the same OFDM symbol. At 804, the UE decides to spatially multiplex the PUCCH and SRS for simultaneous transmission via different sets of one or more antennas. In one aspect, transmissions included in the same OFDM symbol are transmitted simultaneously. At 806, the UE determines time and frequency resources for transmission of the PUCCH and SRS to avoid collision of at least a portion of the PUCCH with the SRS. In an aspect, a portion of the PUCCH includes DMRS. At 808, the UE transmits the spatially multiplexed PUCCH and SRS using the determined time and frequency resources. In one aspect, determining time and frequency resources comprises: different time and frequency resources for the DMRS and SRS are determined.

Fig. 9 illustrates example operations 900 performed by a base station (e.g., a gNB) for spatially multiplexing uplink channels in accordance with certain aspects of the present disclosure. At 902, the operations 900 begin by: indicating to a User Equipment (UE) that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted within a same component carrier via different sets of one or more antennas at the UE. At 904, the BS determines time and frequency resources for the PUCCH and SRS to avoid collision of at least a portion of the PUCCH with the SRS. In an aspect, a portion of the PUCCH includes DMRS. At 906, the BS signals the determined time and frequency resources to the UE. At 908, the BS receives the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

NR (e.g., in release 15) defines five different formats for PUCCH, including PUCCH formats 0-4. PUCCH formats 1, 3, and 4 are generally configured to have four or more OFDM symbols and are generally referred to as long PUCCH formats. According to current NR design, UCI and DMRS are always time division multiplexed in PUCCH formats 1, 3 and 4. For example, UCI and DMRS are scheduled on alternating OFDM symbols. PUCCH formats 0 and 2 are generally configured to have 1 or 2 OFDM symbols and are generally referred to as short PUCCH formats. In certain aspects, separate rule sets may be defined for spatial multiplexing of SRS with different PUCCH formats.

Spatial multiplexing of SRS with PUCCH formats 1, 3, or 4

In certain aspects, when SRS and PUCCH formats 1, 3 or 4 are spatially multiplexed, and when SRS and PUCCH are configured or scheduled to be transmitted on the same symbol, SRS may not be allowed to collide with DMRS portion of PUCCH. As described above, the gNB estimates an uplink channel using DMRS. Not allowing SRS to collide with DMRS helps to protect the DMRS and may assist channel estimation of PUCCH at the gNB. In an aspect, the SRS is not allowed to be scheduled on resources (e.g., time and frequency resources) assigned for the DMRS. For example, SRS is not allowed to be scheduled on the same symbol of the same RB as DMRS. In an aspect, if the DMRS is assigned a specific symbol of a given RB, the SRS is allowed to be transmitted in the same symbol of a different RB. In an aspect, the SRS is not allowed to be transmitted in Resource Elements (REs) assigned to DMRSs. However, the SRS is allowed to be transmitted on different REs (not assigned to DMRSs) of the same symbol in the same RB.

In certain aspects, SRS is allowed to collide with UCI. For example, the SRS is allowed to be scheduled on the same symbol of the same RB as the UCI. In an aspect, the SRS and UCI are allowed to be scheduled in the same RE of the same RB.

Spatial multiplexing of SRS with PUCCH Format 2

In certain aspects, when SRS and PUCCH format 2 are spatially multiplexed, and when SRS and PUCCH are configured or scheduled to be transmitted on the same symbol of the same RB, SRS is scheduled to have the same comb pattern as PUCCH and is scheduled on subcarriers not scheduled for DMRS. In an aspect, using the same comb pattern helps to avoid collisions of SRS and DMRS. In an aspect, when SRS and PUCCH format 2 are not configured or scheduled to be transmitted on the same symbol of the same RB, a nominal comb type is used for SRS.

In certain aspects, when frequency division multiplexing channels, the comb pattern is defined by a division of subcarriers between channels. For example, when FDM is performed on UCI and DMRS, in comb 3, DMRS occupies one third of the subcarriers and UCI occupies the remaining subcarriers. For example, in comb 3, DMRS occupies subcarrier indices 1, 4, 7, 10, and so on, and UCI occupies the remaining subcarriers.

In comb 2, DMRS occupies half of the subcarriers, and the remaining subcarriers are occupied by UCI. In comb 4, DMRS occupies one quarter of the subcarriers, and the remaining subcarriers are occupied by UCI.

According to the NR standard (e.g., release 15), PUCCH format 2 uses comb 3, and the nominal comb type for SRS is either comb 2 or comb 4. Thus, in certain aspects, when SRS and PUCCH format 2 are configured or scheduled to collide (e.g., configured or scheduled to be transmitted in the same symbol of the same RB), the UE changes the comb pattern of SRS to comb 3 to match the comb pattern of PUCCH format 2.

Fig. 10 illustrates spatially multiplexing SRS with PUCCH format 2 in accordance with certain aspects of the present disclosure.

As shown, PUCCH format 2 uses comb pattern 3 to frequency division multiplex UCI and DMRS in the same OFDM symbol, with DMRS bits occupying one third of the subcarriers assigned for PUCCH and the remaining two thirds of the subcarriers occupied by UCI bits. SRS is also scheduled using comb pattern 3 on the same OFDM symbol as PUCCH, where SRS occupies one third of the subcarriers assigned for SRS and occupies subcarriers not occupied by DMRS. As shown, since the same comb pattern is used, the SRS does not collide with the DMRS part of the PUCCH. However, as shown, the SRS collides with at least a part of the UCI part of the PUCCH.

In certain aspects, when spatially multiplexing the SRS and the PUCCH having any one of PUCCH formats 0-4, the SRS may be allowed to collide with at least a portion of the UCI, although the SRS may not be allowed to collide with the DMRS portion of the PUCCH. As described above, as long as the gNB correctly receives and decodes the DMRS and estimates the PUCCH based on the DMRS, the gNB can separate the UCI and the SRS even if their respective resources collide. Therefore, it is beneficial to protect DMRS with respect to UCI.

In certain aspects, a rule may be defined when the UCI portions of the SRS and PUCCH are configured to collide. In an aspect, when the UCI portions of the SRS and PUCCH are configured or scheduled to be transmitted on the same symbol and the same RB, both the SRS and PUCCH are scheduled and transmitted on the colliding resources only when the SRS is at least X RBs wide and/or Y times larger (e.g., in number of RBs) than the PUCCH size.

In one aspect, the values of X and Y depend on the SRS use case. For example, SRS use cases may include codebook-based SRS (when uplink transmission is based on a precoder selected from a codebook), non-codebook based SRS (when a UE selects its own precoder to transmit the SRS), SRS with antenna switching (e.g., when a UE transmits the SRS on one antenna at a time). In one aspect, the values of X and Y depend on the PUCCH format. For example, if PUCCH is using format 0 or 1, the X and Y values may be large, and if PUCCH is using format 2, 3, or 4, the X and Y values may be small. In an aspect, the values of X and Y may be RRC-configured or implicitly derived at the UE.

In certain aspects, SRS and PUCCH are not allowed to collide if the above condition on the size of SRS is not satisfied. For example, one of the channels is dropped following the nominal priority rule defined in NR (e.g., release 15).

In certain aspects, when the PUCCH (or at least the UCI portion of the PUCCH) is configured to collide with SRS, the UE may schedule the PUCCH (or at least the UCI) by puncturing resources (e.g., REs) scheduled for SRS based on the puncturing pattern. In an aspect, puncturing resources to be scheduled for SRS comprises: SRS transmission on a resource overlapping with the PUCCH (or at least UCI) is discarded, and SRS transmission on a resource not overlapping with the PUCCH (or at least UCI) is not discarded. For example, assuming that SRS is scheduled on 12 REs with signals s1, s2, …, s12, and also assuming that 6 REs of the 12 REs collide with PUCCH transmission (e.g., REs carrying s1, …, s6 collide with PUCCH), puncturing in this case means that the UE discards s1-s6 and transmits s7, …, s12 (i.e., the remaining unpunctured signals on non-overlapping REs). In an aspect, the puncturing pattern for SRS may be RRC-configured or included in DCI.

Additionally or alternatively, the puncturing pattern depends on the PUCCH format. For example, if the SRS resource collides with PUCCH formats 0 and 2, the UE punctures the SRS resource, and if the SRS resource collides with PUCCH formats 1, 3, or 4, the UE does not puncture the SRS resource.

In certain aspects, when the PUCCH (or at least the UCI portion of the PUCCH) is configured to collide with SRS, the UE may rate match SRS around the PUCCH (or at least UCI) transmission. For example, according to the same example as used to explain puncturing, rate matching means that the UE regenerates another SRS signal of length 6, e.g., a1, …, a6, based on the new length of the SRS, and transmits a1, …, a6 on 6 non-overlapping REs.

In certain aspects, when PUCCH and PUSCH are configured to be transmitted in the same symbol or symbols, the standard allows for piggybacking UCI bits on PUSCH resources, e.g., by transmitting at least a portion of the UCI bits using PUSCH resources. In certain aspects, when UCI bits are piggybacked on PUSCH resources and PUSCH collides with SRS (e.g., when SRS and PUSCH are spatially multiplexed, as shown in fig. 7B), the UE first maps UCI bits to PUSCH resources (e.g., symbols/REs) that do not collide with SRS to protect UCI. In an aspect, if there are not enough PUSCH resources to transmit all UCI bits that do not collide with SRS, the remainder of the UCI bits may be mapped to PUSCH resources (e.g., symbols/REs) that collide with SRS. In an aspect, the UE first maps ACK/NACK bits and then maps CSI reports in order to protect the ACK/NACK bits. For example, the UE maps ACK/NACK bits and a portion of the CSI report to PUSCH resources that do not collide with SRS, and maps the remaining portion of the CSI report to PUSCH resources that do collide with SRS. In an aspect, the PUSCH (including piggybacked UCI) and SRS are transmitted on different sets of antennas.

Fig. 11 illustrates example operations 1100 performed by a UE for mapping UCI to PUSCH resources when a PDSCH collides with an SRS, in accordance with certain aspects of the present disclosure.

At 1102, the operations 1100 begin by: the PUSCH and SRS are spatially multiplexed with a decision to transmit simultaneously via different sets of one or more antennas. At 1104, the UE determines that Uplink Control Information (UCI) is to be transmitted using resources assigned for PUSCH and determines that at least a portion of the time and frequency resources for PUSCH are to be used for transmission of SRS (e.g., SRS collides with a portion of PUSCH). At 1106, the UE determines a resource mapping pattern for mapping UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of UCI with SRS. At 1108, the UE maps UCI to PUSCH resources based on the resource mapping mode. At 1110, the UE transmits the spatially multiplexed PUSCH and SRS after mapping.

Fig. 12 illustrates example operations 1200 performed by a BS (e.g., a gNB) for mapping UCI to PUSCH resources when PUSCH collides with SRS, in accordance with certain aspects of the present disclosure.

At 1202, the operations 1200 begin by: a decision is made to spatially multiplex a Physical Uplink Shared Channel (PUSCH) and a Sounding Reference Signal (SRS) for simultaneous transmission from a UE via different sets of one or more antennas at the UE. At 1204, the BS indicates spatial multiplexing to the UE. At 1206, the BS detects that Uplink Control Information (UCI) is to be received using resources assigned for PUSCH and detects that at least a portion of time and frequency resources for PUSCH is to be used for receiving Sounding Reference Signals (SRS). At 1208, the BS determines a resource mapping pattern for mapping UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of UCI with SRS. At 1210, the BS receives UCI based on the resource mapping pattern.

In one aspect, the resource mapping schema includes: a portion of the UCI bits is first mapped using PUSCH resources not used for SRS, and then the remaining portion of the UCI bits is mapped using PUSCH resources to be used for SRS. In one aspect, the resource mapping schema includes: UCI bits indicating ACK/NACK bits are mapped before UCI bits indicating Channel Status Indication (CSI) to protect ACK/NACK.

Fig. 13 illustrates a communication device 1300, which communication device 1300 may include various components (e.g., corresponding to elements plus functional components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in fig. 8. The communication device 1300 includes a processing system 1302 coupled to a transceiver 1310. The transceiver 1310 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1300 via the antenna 1312. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and/or to be transmitted by the communication device 1300.

The processing system 1302 includes a processor 1304 coupled to a computer-readable medium/memory 1306 via a bus 1308. In certain aspects, the computer-readable medium/memory 1306 is configured to store computer-executable instructions that, when executed by the processor 1304, cause the processor 1304 to perform the operations shown in fig. 8 or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1302 further includes a detection component 1314, a decision component 1316, and a schedule component 1318 for performing the operations illustrated in fig. 8. In one aspect, detection component 1314 is configured to: the detection PUCCH and the SRS are configured to be transmitted simultaneously. The decision component 1316 is configured to: the PUSCH and SRS are spatially multiplexed with a decision to transmit simultaneously via different sets of one or more antennas. The scheduling component 1318 is configured to: time and frequency resources for the PUCCH and SRS are scheduled to avoid collision of at least a portion of the PUCCH (e.g., the DMRS) with the SRS. The transceiver 1310 is configured to: the spatially multiplexed PUCCH and SRS are transmitted using the scheduled time and frequency resources. The components 1314, 1318 may be coupled to the processor 1304 via the bus 1308. In some aspects, the component 1314 and 1318 may be a hardware circuit. In some aspects, the component 1314 and 1318 may be a software component that executes and runs on the processor 1304.

Fig. 14 illustrates a communication device 1400, which communication device 1400 may include various components (e.g., corresponding to elements plus functional components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in fig. 9. The communication device 1400 includes a processing system 1402 coupled to a transceiver 1410. The transceiver 1410 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1400 via the antenna 1412. The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received and/or to be transmitted by the communication device 1400.

The processing system 1402 includes a processor 1404 coupled to a computer-readable medium/memory 1406 via a bus 1408. In certain aspects, the computer-readable medium/memory 1406 is configured to store computer-executable instructions that, when executed by the processor 1404, cause the processor 1404 to perform the operations shown in fig. 9 or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1402 further includes an indicating component 1414, a determining component 1416, and a signaling component 1418 for performing the operations shown in fig. 9. In one aspect, the indication component is configured to: it is determined and indicated (e.g., using transceiver 1410) to the UE that the PUCCH and SRS are to be transmitted simultaneously. The determination component 1416 is configured to: time and frequency resources for the PUCCH and the SRS are determined to avoid collision of at least a portion of the PUCCH (e.g., the DMRS) with the SRS. The signaling component 1418 is configured to: the determined time and frequency resources are signaled (e.g., using the transceiver 1410) to the UE. The transceiver 1410 is configured to: receiving the spatially multiplexed PUCCH and SRS using the determined time and frequency resources. The components 1414, 1418 may be coupled to the processor 1404 via the bus 1408. In some aspects, the component 1414 and 1418 may be hardware circuitry. In some aspects, the components 1414 and 1418 may be software components that execute and run on the processor 1404.

Fig. 15 illustrates a communication device 1500, which communication device 1500 may include various components (e.g., corresponding to elements plus functional components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in fig. 11. The communication device 1500 includes a processing system 1502 coupled to a transceiver 1510. The transceiver 1510 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1500 via the antenna 1512. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received and/or to be transmitted by the communication device 1500.

The processing system 1502 includes a processor 1504 coupled to a computer-readable medium/memory 1506 via a bus 1508. In certain aspects, the computer-readable medium/memory 1506 is configured to store computer-executable instructions that, when executed by the processor 1504, cause the processor 1504 to perform the operations shown in fig. 11 or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1502 further includes a decision component 1514, a determination component 1516, and a mapping component 1518 for performing the operations illustrated in fig. 11. In one aspect, the decision component 1514 is configured to: the PUSCH and SRS are spatially multiplexed with a decision to transmit simultaneously via different sets of one or more antennas. The determination component 1516 is configured to: determining that the UCI is to be transmitted using resources assigned for PUSCH, and determining that at least a portion of the time and frequency resources for PUSCH are to be used for transmission of SRS. The determining component 1516 is further configured to: determining a resource mapping pattern for mapping the UCI to the PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS. The mapping component 1518 is configured to: mapping the UCI to the PUSCH resources based on the resource mapping mode. The transceiver 1510 is configured to: the spatially multiplexed PUSCH and SRS are transmitted after the mapping. The components 1514, 1518 may be coupled to the processor 1504 via a bus 1508. In some aspects, the components 1514, 1518 may be hardware circuitry. In some aspects, the components 1514, 1518 may be software components that execute and run on the processor 1504.

Fig. 16 illustrates a communication device 1600, which communication device 1600 may include various components (e.g., corresponding to elements plus functional components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in fig. 12. The communication device 1600 includes a processing system 1602 coupled to a transceiver 1610. The transceiver 1610 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1600 via an antenna 1612. The processing system 1602 may be configured to perform processing functions for the communication device 1600, including processing signals received and/or to be transmitted by the communication device 1600.

The processing system 1602 includes a processor 1604 coupled to a computer-readable medium/memory 1606 via a bus 1608. In certain aspects, the computer-readable medium/memory 1606 is configured to store computer-executable instructions that, when executed by the processor 1604, cause the processor 1604 to perform the operations shown in fig. 12 or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1602 further includes a decision component 1614, an indication component 1616, a detection component 1618, and a determination component 1620 for performing the operations shown in fig. 12. In one aspect, the decision component 1614 is configured to: the determination is to spatially multiplex the PUSCH and SRS for simultaneous transmission from the UE via different sets of one or more antennas at the UE. The indication component 1616 is configured to: spatial multiplexing is indicated to the UE. The detection component 1618 is configured to: detecting that the UCI is to be received using resources assigned for PUSCH and detecting that at least a portion of the time and frequency resources for PUSCH are to be used for receiving SRS. The determination component 1620 is configured to: determining a resource mapping pattern for mapping the UCI to the PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS. The transceiver is configured to: the UCI is received based on a resource mapping pattern. The components 1614 and 1620 may be coupled to the processor 1604 via a bus 1608. In some aspects, the component 1614 and 1620 may be hardware circuits. In some aspects, the components 1614 and 1620 may be software components that execute and run on the processor 1604.

The methods disclosed herein comprise one or more steps or actions for achieving the method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

As used herein, a phrase referring to "at least one of a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to encompass any combination of a, b, c, a-b, a-c, b-c, and a-b-c, as well as multiples of the same element (e.g., any other ordering of a, b, and c), a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or a, b, and c).

As used herein, the term "determining" includes a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Further, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and so forth. Further, "determining" may include resolving, selecting, establishing, and the like.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The term "some" means one or more unless explicitly stated otherwise. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed in accordance with the provisions of 35 u.s.c. § 112 clause 6, unless the element is explicitly recited using the phrase "unit for … …", or in the case of a method claim, the element is recited using the phrase "step for … …".

The various operations of the methods described above may be performed by any suitable means that can perform the respective functions. These units may include various hardware and/or software components and/or modules, including but not limited to: a circuit, an Application Specific Integrated Circuit (ASIC), or a processor. Generally, where there are operations shown in the figures, those operations may have corresponding counterpart units plus functional components with similar numbering.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

If implemented in hardware, an example hardware configuration may include a processing system in the wireless node. The processing system may be implemented using a bus architecture. The buses may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. A bus may connect together various circuits including the processor, the machine-readable medium, and the bus interface. The bus interface may also be used, among other things, to connect a network adapter to the processing system via the bus. The network adapter may be used to implement signal processing functions of the PHY layer. In the case of a user terminal 120 (see fig. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also connect various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented using one or more general and/or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how best to implement the described functionality for a processing system depending on the particular application and the overall design constraints imposed on the overall system.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium separate from the wireless node having instructions stored thereon, all of which may be accessed by the processor through a bus interface. Alternatively or in addition, the machine-readable medium or any portion thereof may be integrated into a processor, for example, which may be a cache and/or a general register file. Examples of a machine-readable storage medium may include, by way of example, RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer readable medium may include a plurality of software modules. The software modules include instructions that, when executed by an apparatus, such as a processor, cause a processing system to perform various functions. The software modules may include a sending module and a receiving module. Each software module may be located in a single storage device or distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from the hard drive into RAM. During execution of the software module, the processor may load some of the instructions into the cache to increase access speed. One or more cache lines may then be loaded into the general register file for execution by the processor. It will be understood that when reference is made below to the functionality of a software module, such functionality is achieved by the processor when executing instructions from the software module.

Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and

optical disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically with lasers. Thus, in some aspects, computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). Further, for other aspects, the computer readable medium may comprise a transitory computer readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

Accordingly, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. Such as instructions for performing the operations described herein and shown in fig. 8-9 and 11-12.

Further, it should be appreciated that modules and/or other suitable means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device may be coupled to a server to facilitate communicating means for performing the methods described herein. Alternatively, various methods described herein can be provided via a storage unit (e.g., RAM, ROM, a physical storage medium such as a Compact Disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage unit to the device. Further, any other suitable technique for providing the methods and techniques described herein to a device may be used.

It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims (30)

1. A method for wireless communications by a User Equipment (UE), comprising:

detecting that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted;

deciding to spatially multiplex the PUCCH and the SRS for simultaneous transmission via different sets of one or more antennas;

determining time and frequency resources for the PUCCH and the SRS to avoid collision of at least a portion of the PUCCH with the SRS; and

transmitting the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

2. The method of claim 1, wherein the detecting comprises: detecting that the PUCCH and the SRS are configured or scheduled to be transmitted in the same OFDM symbol.

3. The method of claim 1, wherein the portion comprises a demodulation reference signal (DMRS).

4. The method of claim 3, wherein determining the time and frequency resources comprises: determining different time and frequency resources for the DMRS and the SRS.

5. The method of claim 4, in which the PUCCH is according to PUCCH format 1, 3, or 4.

6. The method of claim 5, wherein the determining comprises: determining that the SRS and the DMRS are to be transmitted on different OFDM symbols.

7. The method of claim 5, wherein the determining comprises: determining that the SRS is to be transmitted on a same OFDM symbol in a different resource block than the DMRS.

8. The method of claim 5, wherein the determining comprises: determining that the SRS is to be transmitted in a same resource block and in a same OFDM symbol as the DMRS, wherein the SRS is scheduled on Resource Elements (REs) that are not scheduled for the DMRS.

9. The method of claim 4, wherein the PUCCH is according to PUCCH format 2, and wherein the detecting comprises: detecting that the SRS is to be transmitted on the same OFDM symbol in the same resource block as the DMRS.

10. The method of claim 10, wherein the determining comprises:

determining a comb pattern for the SRS that is the same as the comb pattern for the DMRS; and

determining resources for the SRS on subcarriers not occupied by the DMRS based on the determined comb pattern.

11. The method of claim 1, wherein the detecting comprises: detecting that at least a remaining portion of the PUCCH and the SRS are configured to be transmitted on a same OFDM symbol of a same resource block.

12. The method of claim 11, wherein the determining comprises: determining the same OFDM symbol of the same resource block for transmission of the remaining portion and the SRS if the SRS is at least one of X resource blocks wide or Y times wider than the PUCCH.

13. The method of claim 12, wherein values of X and Y are determined based on at least one of an SRS use case or a format of the PUCCH.

14. The method of claim 12, wherein the values of X and Y are configured via Radio Resource Control (RRC) signaling.

15. The method of claim 12, wherein the determining further comprises:

determining a puncturing pattern for the SRS; and

determining resources for the remaining portion by puncturing Resource Elements (REs) scheduled for the SRS based on the puncturing pattern.

16. The method of claim 15, wherein the puncturing pattern is based on a format of the PUCCH.

17. The method of claim 12, wherein the determining further comprises: rate matching the transmission of the SRS around the transmission of the remaining portion.

18. The method of claim 11, wherein the remaining portion comprises Uplink Control Information (UCI).

19. A method for wireless communications by a User Equipment (UE), comprising:

deciding to spatially multiplex a Physical Uplink Shared Channel (PUSCH) and a Sounding Reference Signal (SRS) for simultaneous transmission via different sets of one or more antennas;

determining that Uplink Control Information (UCI) is to be transmitted using resources assigned for the PUSCH and determining that at least a portion of time and frequency resources for the PUSCH is to be used for transmission of the SRS;

determining a resource mapping pattern for mapping the UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS;

mapping the UCI to the PUSCH resources based on the resource mapping pattern; and

transmitting the spatially multiplexed PUSCH and SRS after the mapping.

20. The method of claim 19, wherein the mapping comprises:

mapping at least a portion of UCI bits indicating acknowledgement/negative acknowledgement (ACK/NACK) using the PUSCH resources that will not be used for the SRS.

21. The method of claim 20, wherein the mapping comprises: after mapping the at least a portion of the UCI bits indicating ACK/NACK, mapping a remaining portion of the UCI bits indicating ACK/NACK and at least a portion of the UCI bits indicating Channel State Indication (CSI) using the PUSCH resources to be used for SRS.

22. The method of claim 19, wherein the mapping comprises: before mapping a UCI bit indicating a Channel Status Indication (CSI), a UCI bit indicating acknowledgement/negative acknowledgement (ACK/NACK) is mapped.

23. A method for wireless communications by a Base Station (BS), comprising:

indicating to a User Equipment (UE) that a Physical Uplink Control Channel (PUCCH) and a Sounding Reference Signal (SRS) are to be simultaneously transmitted within a same component carrier via different sets of one or more antennas at the UE;

determining time and frequency resources for the PUCCH and the SRS to avoid collision of at least a portion of the PUCCH with the SRS;

signaling the determined time and frequency resources to the UE; and

receiving the spatially multiplexed PUCCH and SRS using the determined time and frequency resources.

24. The method of claim 23, wherein the indication comprises: configuring or scheduling the UE to transmit the PUCCH and SRS in a same OFDM symbol.

25. The method of claim 23, wherein the portion comprises an uplink demodulation reference signal (DMRS).

26. The method of claim 25, wherein determining the time and frequency resources comprises: determining different time and frequency resources for the DMRS and the SRS.

27. A method for wireless communications by a Base Station (BS), comprising:

deciding that a Physical Uplink Shared Channel (PUSCH) and a Sounding Reference Signal (SRS) are to be spatially multiplexed for simultaneous transmission from a UE via different sets of one or more antennas at the UE;

indicating the spatial multiplexing to the UE;

detecting that Uplink Control Information (UCI) is to be received using resources assigned for the PUSCH, and detecting that at least a portion of time and frequency resources for the PUSCH is to be used for receiving a Sounding Reference Signal (SRS);

determining a resource mapping pattern for mapping the UCI to PUSCH resources, wherein the resource mapping pattern avoids collision of the UCI with the SRS; and

receiving the UCI based on the resource mapping mode.

28. The method of claim 27, wherein the resource mapping schema comprises: mapping at least a portion of UCI bits indicating acknowledgement/negative acknowledgement (ACK/NACK) using the PUSCH resources that will not be used for the SRS.

29. The method of claim 28, wherein the resource mapping schema comprises: after mapping the at least a portion of the UCI bits indicating ACK/NACK, mapping a remaining portion of the UCI bits indicating ACK/NACK and at least a portion of the UCI bits indicating Channel State Indication (CSI) using the PUSCH resources to be used for SRS.

30. The method of claim 27, wherein the resource mapping schema comprises: before mapping UCI bits for indicating Channel State Indication (CSI), UCI bits for indicating acknowledgement are mapped.

Images