Patent Publication Number: US-2020295895-A1

Title: Rate matching for new radio (nr) physical downlink shared channel (pdsch) and physical uplink shared channel (pusch)

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims the benefit of Application No. PCT/CN2017/104081 entitled “RATE MATCHING FOR NEW RADIO (NR) PHYSICAL DOWNLINK SHARED CHANNEL (PDSCH) AND PHYSICAL UPLINK SHARED CHANNEL (PUSCH),” which was filed on Sep. 28, 2017. The aforementioned application is herein incorporated by reference in its entirety. 
    
    
     FIELD 
     The present disclosure relates generally to communication systems, and more particularly, to methods and apparatus relating to rate matching for new radio (NR) physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH). 
     BACKGROUND 
     Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple-access technologies include Long Term Evolution (LTE) 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. 
     In some examples, a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs). In LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation or 5G network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a new radio base station (NR BS), a new radio node-B (NR NB), a network node, 5G NB, eNB, etc.). A base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit). 
     These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example of an emerging telecommunication standard is new radio (NR), for example, 5G radio access. NR is a set of enhancements to the LTE mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband. Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. 
     However, as the demand for mobile broadband access continues to increase, there exists a desire for further improvements in NR technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies. 
     BRIEF SUMMARY 
     The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which 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 communications between access points and stations in a wireless network. 
     Certain aspects provide a method for wireless communications by a user equipment (UE). The method generally includes receiving a rate matching resource (RMR) configuration from a serving cell, identifying one or more first resource elements (REs) to be rate matched around at least in part based on a transmission numerology associated with the RMR configuration, wherein the one or more first REs are used for reference signal (RS) transmission in the serving cell or a neighboring cell, and mapping a physical downlink shared channel (PDSCH) to one or more second REs not including the first REs. 
     Certain aspects provide a method for wireless communications by a user equipment (UE). The method generally includes receiving a rate matching resource (RMR) configuration from a serving cell, identifying one or more first resource elements (REs) to be rate matched around for physical uplink shared channel (PUSCH) at least in part based on signaling configurations relating to physical uplink control channel (PUCCH) and sounding reference signals (SRS) in the RMR configuration, and mapping a physical uplink shared channel (PUSCH) to one or more second REs not including the first REs. 
     Aspects generally include methods, apparatus, systems, computer readable mediums, and processing systems, as substantially described herein with reference to and as illustrated by the accompanying drawings. 
     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, and this description is intended to include all such aspects and their equivalents. 
    
    
     
       BRIEF DESCRIPTION OF THE 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 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 BS and user equipment (UE), in accordance with certain aspects of the present disclosure. 
         FIG. 5  is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure. 
         FIG. 6  illustrates an example of a DL-centric subframe, in accordance with certain aspects of the present disclosure. 
         FIG. 7  illustrates an example of an UL-centric subframe, in accordance with certain aspects of the present disclosure. 
         FIG. 8  illustrates an example of a UE located in an overlapping coverage areas of two cells, in accordance with certain aspects of the present disclosure. 
         FIG. 9  illustrates example operations for wireless communications by a wireless device, in accordance with aspects of the present disclosure. 
         FIG. 9A  illustrates a wireless communications device that may include various components configured to perform operations for the techniques disclosed herein, such as one or more of the operations illustrated in  FIG. 9 . 
         FIG. 10  illustrates an example of a main cell using a larger subcarrier spacing (SCS) than a neighboring cell, in accordance with aspects of the present disclosure. 
         FIG. 11  illustrates an example of a main cell using a smaller subcarrier spacing (SCS) than a neighboring cell, in accordance with aspects of the present disclosure. 
         FIG. 12  illustrates example operations for wireless communications by a wireless device, in accordance with aspects of the present disclosure. 
         FIG. 12A  illustrates a wireless communications device that may include various components configured to perform operations for the techniques disclosed herein, such as one or more of the operations illustrated in  FIG. 12 . 
         FIG. 13A  illustrates a set of semi-statically configured resources in uplink (UL) regular burst that is reserved for long physical uplink control channel (PUCCH), in accordance with aspects of the present disclosure. 
         FIG. 13B  illustrates rate matching to avoid all resource elements (REs) in a long PUCCH regions, in accordance with aspects of the present disclosure. 
         FIG. 14A  also illustrates a set of semi-statically configured resources in UL regular burst that is reserved for long PUCCH, in accordance with aspects of the present disclosure, 
         FIG. 14B  illustrates REs not occupied by PUCCH in the regions allocated for PUCCH to be occupied by PUSCH, in accordance with aspects of the present disclosure. 
         FIG. 15  illustrates an example symbol in an UI, short duration of a slot, in accordance with aspects of the present disclosure. 
         FIG. 16  illustrates an example precoder set, in accordance with aspects of the present disclosure. 
         FIG. 17  illustrates an example rate matching resource, 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 
     Aspects of the present disclosure relate to methods and apparatus relating to rate matching for new radio (NR) physical downlink shared channel (PDSCH) and. physical uplink shared channel (PUSCH). 
     Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for new radio (NR) (new radio access technology or 5G technology). 
     NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe. 
     Generally, wireless devices conforming to wireless standards such as the Long Term Evolution (LTE) standards or the 5G New Radio (NR) standards use uplink and downlink reference signals for channel estimation or equalization. In some cases, any interference with downlink or uplink reference signals may result in inaccurate estimations by the receiver of the reference signals. To prevent this, for example, a user equipment (UE) that is receiving downlink reference signals may need to avoid interference from other UEs&#39; aperiodic channel state information reference signals (A-CSI-RS), other cells&#39; CSI-RS, other cells&#39; synchronization signals (SS), aperiodic sounding reference signal (SRS) structures for A-SRS (if SRS can be multiplexed with physical uplink shared channel (PUSCH)), physical uplink control channel (PUCCH) structures (if unused PUCCH resource can be used for PUSCH), signals/channels in legacy systems (e.g, LTE cell-specific reference signals (CSR)/SS, phase tracking reference signal (PTRS), tracking reference signals, etc. 
     Certain embodiments discussed herein relate to configuring a UE to perform physical downlink shared channel (PUSCH) rate matching around non-zero power CSI-RS (NZP CSI-RS) in neighboring cells in order to enable the UE to accurately estimate reference signal received power (RSRP) on the CSI-RS detected from a cell other than the cell transmitting the PDSCH. Also, certain embodiments discussed herein relate to configuring a UE to perform PUSCH rate matching around physical uplink control channel (PUCCH) on the uplink (UL). 
     The following description provides examples, and is not limiting of 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 instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in 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. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using 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 networks 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), cdma.2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM), An OFDMA network may implement a radio technology such as NR (e.g. 5G RA), Evolved UTRA (E-U IRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and. E-UTRA. are part of Universal Mobile Telecommunication System (UMTS). NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (SGTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA., UMTS, LIE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and LIMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). 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, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies. 
     Example Wireless Communications System 
       FIG. 1  illustrates an example wireless network  100 , such as a new radio (NR) or 5G network, in which aspects of the present disclosure may be performed. For example, UE  120  may perform operations  9000  of  FIG. 9  as well as operation  1200  of  FIG. 12 . 
     As illustrated in  FIG. 1 , the wireless network  100  may include a number of BSs  110  and other network entities. ABS may be a station that communicates with UEs. 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 and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network  100  through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network. 
     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, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. 
     A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, 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 subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in  FIG. 1 , the BSs  110   a ,  110   b  and  110   c  may be macro BSs for the macro cells  102   a ,  102   b  and  102   c , respectively. The BS  110   x  may be a pico BS for a pico cell  102   x.  The BSs  110   y  and  110   z  may be femto BS for the femto cells  102   y  and  102   z,  respectively. A BS may support one or multiple (e.g., three) cells. 
     The wireless network  100  may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data 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 , a relay station  110   r  may communicate with the BS  110   a  and a UE  120   r  in order to facilitate communication between the BS  110   a  and the UE  120   r.  A relay station may also be referred to as a relay BS, a relay, etc. 
     The wireless network  100  may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network  100 . For example, macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt). 
     The wireless network  100  may support synchronous or asynchronous operation. For synchronous operation, the 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 timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation. 
     A network controller  130  may be coupled to a set of BSs and provide coordination and control for these BSs. The network controller  130  may communicate with the BSs  110  via a backhaul. The BSs  110  may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul. 
     The UEs  120  (e.g.,  120   x ,  120   y , etc.) may be dispersed throughout the 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 phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WU) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, 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 vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices. 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. A dashed line with double arrows indicates interfering transmissions between a UE and a BS. 
     Certain 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, etc. Each subcarrier may be modulated with data. In general, modulation symbols arc 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 be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively. 
     While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR. NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span  12  sub-carriers with a sb-carrier bandwidth of 75 kHz over a 0.1 ms duration. Each radio frame may consist of 50 subframes with a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL, transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based. NR networks may include entities such CUs and/or DUs. 
     In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. A UE may function as a scheduling entity in a peer-to-peer (P 2 P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity. 
     Thus, in a wireless communication network with a scheduled access to time—frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources. 
     As noted above, a RAN may include a CU and DUs. A NR BS (e.g., eNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cell (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. sonic cases DCells may not transmit synchronization signals—in some case cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider the cell selection, access, handover, and/or measurement based on the indicated cell type. 
       FIG. 2  illustrates an example logical architecture of a distributed radio access network (RAN)  200 , which may be implemented in the wireless communication system illustrated in  FIG. 1 . A  5 G access node  206  may include an access node controller (ANC)  202 . The ANC may be a central unit (CU) of the distributed RAN  200 . The backhaul interface to the next generation core network (NG-CN)  204  may terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC. The ANC may include one or more TRPs  208  (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with “cell.” 
     The TRPs  208  may be a DU. The TRPs may be connected to one ANC (ANC  202 ) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. 
     The local architecture  200  may be used to illustrate frormal definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). 
     The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN)  210  may support dual connectivity with NR. The NG-AN may share a common fronthaul for LIE and NR. 
     The architecture may enable cooperation between and among TRPs  208 . For example, cooperation may be preset within a TRP and/or across TRPs via the ANC  202 . According to aspects, no inter-TRP interface may be needed/present. 
     According to aspects, a dynamic configuration of split logical functions may be present within the architecture  200 . As will be described in more detail with reference to  FIG. 5 , the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively). According to certain aspects, a BS may include a central unit (CU) (e.g., ANC  202 ) and/or one or more distributed units (e.g., one or more TRPs  208 ). 
       FIG. 3  illustrates an example physical architecture of a distributed RAN  300 , according to aspects of the present disclosure. A centralized core network unit (C-CU)  302  may host core network functions. The C-CU may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. 
     A centralized RAN unit (C-RU)  304  may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have distributed deployment. The C-RU may be closer to the network edge. 
     A DU  306  may host one or more TRPs (edge node (EN), an edge unit (EU), a radio head (RH), a smart radio head (SRH), or the like). The DU may be located at edges of the network with radio frequency (RF) functionality. 
       FIG. 4  illustrates example components of the BS  110  and UE  120  illustrated in  FIG. 1 , which may be used to implement aspects of the present disclosure. As described above, the BS may include a TRP. One or more components of the BS  110  and UE  120  may be used to practice aspects of the present disclosure. For example, antennas  452 , Tx/Rx  222 , processors  466 ,  458 ,  464 , and/or controller/processor  480  of the UE  120  and/or antennas  434 , processors  460 ,  420 ,  438 , and/or controller/processor  440  of the BS  110  may be used to perform the operations described herein (e.g., operations  9000  of  FIG. 9  as well as operation  1200  of  FIG. 12 ). 
       FIG. 4  shows a block diagram of a design of a BS  110  and a UE  120 , which may be one of the BSs and one of the UEs in  FIG. 1 . For a restricted association scenario, the base station  110  may be the macro BS  110 c in  FIG. 1 , and the UE  120  may be the UE  120   y.  The base station  110  may also be a base station of some other type. The base station  110  may be equipped with antennas  434   a  through  434   t,  and the UE  120  may be equipped with antennas  452   a  through  452   r.    
     At the base station  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 for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc. The data may be for the Physical Downlink Shared Channel (PDSCH), etc. The processor  420  may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor  420  may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal. 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 the modulators (MODs)  432   a  through  432   t.  For example, the TX MIMO processor  430  may perform certain aspects described herein for RS multiplexing. Each modulator  432  may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator  432  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  432   a  through  432   t  may be transmitted via the antennas  434   a  through  434   t,  respectively. 
     At the UE  120 , the antennas  452   a  through  452   r  may receive the downlink signals from the base station  110  and may provide received signals to the demodulators (DEMODs)  454   a  through  454   r,  respectively. Each demodulator  454  may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator  454  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 the demodulators  454   a  through  454   r , perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector  456  may provide detected RS transmitted using techniques described herein. 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 . According to one or more cases, CoMP aspects can include providing the antennas, as well as some Tx/Rx functionalities, such that they reside in distributed units. For example, some Tx/Rx processings can be done in the central unit, while other processing can be done at the distributed units. For example, in accordance with one or more aspects as shown in the diagram, the BS mod/demod  432  may be in the distributed units. 
     On the uplink, at the UE  120 , a transmit processor  464  may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from a data source  462  and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor  480 . The transmit processor  464  may also generate reference symbols for a reference signal. The symbols from the transmit processor  464  may be precoded by a TX MIMO processor  466  if applicable, further processed by the demodulators  454   a  through  454   r  (e.g., for SC-FDM, etc.), and transmitted to the base station  110 . At the BS  110 , the uplink signals from the UE  120  may be received by the antennas  434 , processed by the 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 the UE  120 . The receive processor  438  may provide the decoded data to a data sink  439  and the decoded control information to the controller/processor  440 . 
     The controllers/processors  440  and  480  may direct the operation at the base station  110  and the UE  120 , respectively. The processor  440  and/or other processors and modules at the base station  110  may perform or direct, e.g., the execution of the functional blocks illustrated in  FIG. 9 , and/or other processes for the techniques described herein. The processor  480  and/or other processors and modules at the UE  120  may also perform or direct processes for the techniques described herein. The memories  442  and  482  may store data and program codes for the BS  110  and the UE  120 , respectively. A scheduler  444  may schedule UEs for data transmission on the downlink and/or uplink. 
       FIG. 5  illustrates a diagram  500  showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a in a  5 G system (e.g., a system that supports uplink-based mobility). Diagram  500  illustrates a communications protocol stack including 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 a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof, Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE. 
     A first option  505 - a  shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC  202  in  FIG. 2 ) and distributed network access device (e.g., DU  208  in  FIG. 2 ). In the first option  505 - a,  an RRC layer  510  and a PDCP layer  515  may be implemented by the central unit, and an RLC layer  520 , a MAC layer  525 , and a PHY layer  530  may be implemented by the DU. In various examples the CU and the DU may be collocated or non-collocated. The first option  505 - a  may be useful in a macro cell, micro cell, or pico cell deployment. 
     A second option  505 - b  shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), a new radio Node-B (NR NB), a network node (NN), or the like.). In the second option, the RRC layer  510 , the PDCP layer  515 , the RLC layer  520 , the MAC layer  525 , and the PHY layer  530  may each be implemented by the AN. The second option  505 - b  may be useful in a femto cell deployment. 
     Regardless of whether a network access device implements part or all of a protocol stack, a UE may implement an entire protocol stack (e.g., the RRC layer  510 , the PDCP layer  515 , the RLC layer  520 , the MAC layer  525 , and the PHY layer  530 ). 
       FIG. 6  is a diagram  600  showing an example of a DL-centric subframe. The DL-centric subframe may include a control portion  602 . The control portion  602  may exist in the initial or beginning portion of the DL-centric subframe. The control portion  602  may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe. In sonic configurations, the control portion  602  may be a physical DL control channel (PDCCH), as indicated in  FIG. 6 . The DL-centric subframe may also include a DL data portion  604 . The DL data portion  604  may sometimes be referred to as the payload of the DL-centric subframe. The DL data portion  604  may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). In some configurations, the DL data portion  604  may be a physical DL shared channel (PDSCH). 
     The DL-centric subframe may also include a common UL portion  606 . The common UL portion  606  may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL, portion  606  may include feedback information corresponding to various other portions of the DL-centric subframe. For example, the common UL portion  606  may include feedback information corresponding to the control portion  602 . Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion  606  may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated in  FIG. 6 , the end of the DL data portion  604  may be separated in time from the beginning of the common UL portion  606 . This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. 
       FIG. 7  is a diagram  700  showing an example of an UL-centric subframe. The UL -centric subframe may include a control portion  702 . The control portion  702  may exist in the initial or beginning portion of the UL-centric subframe. The control portion  702  in  FIG. 7  may be similar to the control portion described above with reference to  FIG. 6 . The UL-centric subframe may also include an UL data portion  704 . The UL data portion  704  may sometimes be referred to as the payload of the UL-centric subframe. The UL data portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e,g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion  702  may be a physical DL control channel (PDCCH). 
     As illustrated in  FIG. 7 , the end of the control portion  702  may be separated in time from the beginning of the UL data portion  704 . This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric subframe may also include a common UL portion  706 . The common UL portion  706  in  FIG. 7  may be similar to the common UL portion  706  described above with reference to  FIG. 7 . The common UL portion  706  may additionally or alternatively include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. 
     In some circumstances, two or more subordinate entities UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE 1 ) to another subordinate entity (e.g., UE 2 ) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum). 
     A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of 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 a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs. 
     Rate Matching for New Radio (NR) Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) 
     Generally, wireless devices conforming to wireless standards such as the Long Term Evolution (LTE) standards or the 5G New Radio (NR) standards use uplink and downlink reference signals for channel estimation or equalization. In some cases, any interference with downlink or uplink reference signals may result in inaccurate estimations by the receiver of the reference signals. To prevent this, for example, a user equipment (UE) that is receiving downlink reference signals may need to avoid interference from other UEs&#39; aperiodic channel state information reference signals (A-CSI-RS), other cells&#39; CSI-RS, other cells&#39; synchronization signals (SS), aperiodic sounding reference signal (SRS) structures for A-SRS (if SRS can be multiplexed with physical uplink shared channel (PUSCH)), physical uplink control channel (PUCCH) structures (if unused PUCCH resource can be used for PDSCH), signals/channels in legacy systems (e.g., LIE cell-specific reference signals (CSR)/SS, phase tracking reference signal (PTRS), trucking reference signals, etc. 
       FIG. 8  illustrates an example of a UE  820  (e.g., UE  120 ) located in an area where the cell radius of Cell  830  (e.g., main cell) overlaps with the cell radius of Cell  840  (e.g., neighboring cell). As shown in  FIG. 8 , UE  820  may receive CSI-RS from BS  810  (e.g., BA  110 ) in Cell  830  and CSI-RS (e.g., A-CSI-RS) from BS  812  (e.g., BS  110 ) in Cell  840 . In addition, UE  820  may receive data/control information from BS  810  through the PDSCH. However, under the NR standards, PDSCH is beamformed through a large number of antennas while CSI-RS is transmitted without beamforming. As a result, the signal strength associated with PDSCH resource elements (REs) is higher than the signal strength associated with CSI-RS REs. 
     Accordingly, in the embodiments of  FIG. 8 , if REs of PDSCH in Cell  830  collide with the REs of non-precoded CSI-RS (e.g., non-zero power (NZP) CSI-RS) in Cell  840 . cell-edge UEs (e.g., UE  820 ) may not be able to estimate reference signal received power (RSRP) on the CSI-RS detected in Cell  840 . The cell-edge UEs&#39; inability to estimate the RSRP may result in transmitting inaccurate CSI feedback and, in some cases, ping-pong handover of UE  820  between Cell  830  and Cell  840  based on the CSI-RSRP. In the embodiments described herein, a NZP CSI-RS refers to CSI-RS transmitted in, for example, a neighboring cell (e.g., Cell  840 ) that may create interference for an edge UE (e.g., UE  820 ) when the REs on which the NZP CSI-RS (e.g., REs  860 ) are transmitted collide with the REs of PDSCH (e.g., PDSCH  850 ) in, for example, the serving cell (e.g., Cell  830 ). In addition, in the embodiments described herein, ZP CSI-RS refers to rate matching resource(s) MIR) used for configuring a UE to perform PDSCH rate matching around the NZP CSI-RS. In some embodiments, the ZP CSI-RS may be transmitted to the UE by a serving cell (e.g., Cell  830 ). 
     Accordingly, certain embodiments discussed herein relate to configuring a UE (e.g., UE  120 , UE  820 , etc.) to perform PDSCH rate matching around NZP CSI-RS in neighboring cells in order to enable the UE to accurately estimate RSRP on the CSI-RS detected from a cell other than the cell transmitting the PDSCH. 
       FIG. 9  illustrates example operations for wireless communications by a wireless device, in accordance with aspects of the present disclosure. In some embodiments, the wireless device may be a UE. At  902 , operations  900  begin by receiving a rate matching resource (RMR) configuration from a serving cell. At  904 , operations  900  continue by identifying one or more first resource elements (REs) to be rate matched around at least in part based on a transmission numerology associated with the MIR configuration, wherein the one or more first REs are used for reference signal (RS) transmission in the serving cell or a neighboring cell. At  906 , operations  900  continue by mapping a physical downlink shared channel (PDSCH) to one or more second REs not including the first REs. 
       FIG. 9A  illustrates a wireless communications device  900 A that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as one or more of the operations illustrated in  FIG. 9 . The communications device  900 A includes a processing system  914  coupled to a transceiver  912 . The transceiver  912  is configured to transmit and receive signals for the communications device  900 A via an antenna  913 . The processing system  914  may be configured to perform processing functions for the communications device  900 A, such as processing signals, etc. 
     The processing system  914  includes a processor  909  coupled to a computer-readable medium/memory  911  via a bus  921 . In certain aspects, the computer-readable medium/memory  911  is configured to store instructions that when executed by processor  909 , cause the processor  909  to perform one or more of the operations illustrated in  FIG. 9 , or other operations for performing the various techniques discussed herein. 
     In certain aspects, the processing system  914  further includes a receiving component  920  for performing one or more of the operations illustrated at  902  in  FIG. 9 . Additionally, the processing system  914  includes an identifying component  922  for performing one or more of the operations illustrated at  904  in  FIG. 9 . Further, the processing system  914  includes a mapping component  924  for performing one or more of the operations illustrated at  906  in  FIG. 9 . 
     The receiving component  920 , the receiving component  922 , the identifying component  924 , and the mapping component  926  may be coupled to the processor  909  via bus  921 . In certain aspects, receiving component  920 , the receiving component  922 , the identifying component  924 , and the mapping component  926  may be hardware circuits. In certain aspects, receiving component  920 , the receiving component  922 , the identifying component  924 , and the mapping component  926  may be software components that are executed and run on processor  909 . 
     As described above, PDSCH rate matching may be performed by a UE around NZP CSI-RS detected from a cell (e.g., Cell  840  of  FIG. 8 ) other than the cell transmitting the PDSCH (e.g, Cell  830  of  FIG. 8 ). 
     In some embodiments, both cells may use identical numerology. For example, Cell  830  and Cell  840  of  FIG. 8  may, for instance, use the same kind of subcarrier spacing, slot format, symbol duration, etc. In such embodiments, the UE (e.g., UE  830 , UE  120 ) may receive rate matching (RMR) configuration from Cell  830  (e.g., serving cell), including zero power (ZP) CSI-RS resources, which configures the UE for performing PDSCH rate matching. In some embodiments, the configuration may be semi-static, for situations when the UE receives periodic or semi-persistent NZP CSI-RS in neighboring cells (e.g., Cell  840  of  FIG. 8 ). In some embodiments, the UE may be configured through a dynamic indication, for situations when the UE receives aperiodic NZP CSI-RS in neighboring cells. 
     In some embodiments, the ZP CSI-RS may be configured via the CSI framework. In some embodiments, the CSI-RS transmit power may be a parameter in the RS setting, the CSI-RS resource set, and/or the CSI-RS resources. in such embodiments, the CSI-RS transmit power parameter may at least include a value of zero. For example, in sonic embodiments, the transmit power parameter may be 1-bit to indicate ZP as opposed to NZP or, in some embodiments, the transmit power parameter may be multiple hits to indicate multiple NZP levels. 
     In some embodiments, the CSI-RS resources may inherit the transmit power property from the parent RS setting. For example, if a RS setting is configured as ZP, all CSI-RS resource sets and/or CSI-RS resources associated with it are ZP by default, In another example, if a CSI-RS resource set is configured as ZP, all CSI-RS resources associated with it are ZP by default. In some embodiments, for an individual CSI-RS resource set or CSI-RS resource, a non-zero CSI-RS transmit power can be further configured as a parameter of the CSI-RS resource set or CSI-RS resource, to override the ZP setting of its parent RS setting. 
     In some embodiments, the cells may use different numerology. FIG,  10  shows an example of Cell  1030  using a larger subcarrier spacing (SCS), and also a longer symbol duration, than Cell  1040 . For example, as shown in  FIG. 8 , Cell  1030  has a SCS of 15 kHz while Cell  1040  has a SCS of 30 kHz. In such embodiments, the numerology of Cell  1040  may be transparent to Cell  1030 . Accordingly, the UE in Cell  1030  may be configured with ZP CSI-RS (e.g., ZP CSI-RS  1050  and ZP CSI-RS  1055 ) using the same transmission numerology in Cell  1030 . In some embodiments, a set of ZP CSI-RS may be configured, where each may be associated with a different RB comb. This is in order to match Cell  1040 ′s CSI-RS set or resource (e.g., NZP CSI-RS  1060  and NZP CSI-RS  1070 ). As an example, in some embodiments, for dynamic ZP CSI-RS indication, a set of ZP CSI-RS may be indicated, in one example of such embodiments, one ZP RS setting, or a ZP CSI-RS resource set may be indicated. In another example, 4 sets of ZP CSI-RS resources may be semi-statically configured and 1out of 4 sets may be dynamically indicated by 2-bits in DCI. In such an example, each set may include several CSI-RS configured via the CSI framework. For instance, CSI-RS configured in CSI framework may not be ZP. 
     Another example of the cells using different numerology is shown in  FIG. 11 , in which Cell  1130  is using a smaller SCS than Cell  1140 . In such embodiments, the UE in Cell  1130  may be configured with ZP CSI-RS using the same transmission numerology in Cell  1130 , A set of ZP CSI-RS, in some embodiments, may be configured, where each is associated with different slots. For example, as shown in  FIG. 11 , ZP CSI-RS  1150  and  1152  are associated with one slot (comprising 14 symbols) and ZP CSI-RS  1154  and  1156  are associated with the next slot (comprising 14 symbols). In such embodiments, each ZP CSI-RS resource may be configured with a higher density than NZP CSI-RS. In some embodiments, the ZP CSI-RS may be configured with a transmission numerology other than that for the PDSCH. In some embodiments, the ZP CSI-RS configuration may include a parameter to indicate a SCS (e.g., 15 kHz), while the transmission numerology (e.g., 30 kHz SCS) is separately configured for PDSCH and NZP CSI-RS (e.g., NZP CSI-RS  1160  and NZP CSI-RS  1162  etc. In such embodiments, the UE identifies the REs under SCS of 30 kHz that are overlapping with the ZP CSI-RS in SCS of 15 kHz. After identifying such REs, in some embodiments, the UE may assume that these REs are not mapped with PUSCH. 
     Certain embodiments discussed herein relate to configuring a UE to perform PUSCH rate matching around physical uplink control channel (PUCCH) on the uplink (UL). 
       FIG. 12  illustrates example operations for wireless communications by a wireless device, in accordance with aspects of the present disclosure. In some embodiments, the wireless device may be a UE. At  1202 , operations  1200  begin by receiving a rate matching resource (RMR) configuration from a serving cell. At  1204 , operations  1200  continue identifying one or more first resource elements (REs) to be rate matched around for physical uplink shared channel (PUSCFI) at least in part based on signaling configurations relating to physical uplink control channel (PUCCH) and sounding reference signals (SRS) in the RMR configuration. At  1206 , operations  1200  continue by mapping a physical uplink shared channel (PUSCH) to one or more second REs not including the first REs. 
       FIG. 12A  illustrates a wireless communications device  1200 A that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as one or more of the operations illustrated in HG  12 . The communications device  1200 A includes a processing system  1214  coupled to a transceiver  1212 . The transceiver  1212  is configured to transmit and receive signals for the communications device  1200 A via an antenna  1213 . The processing system  1214  may be configured to perform processing functions for the communications device  1200 A, such as processing signals, etc. 
     The processing system  1214  includes a processor  1209  coupled to a computer-readable medium/memory  1211  via a bus  1221 . In certain aspects, the computer-readable medium/memory  1211  is configured to store instructions that when executed by processor  1209 , cause the processor  1209  to perform one or more of the operations illustrated in  FIG. 12 , or other operations for performing the various techniques discussed herein. 
     In certain aspects, the processing system  1214  further includes a receiving component  1220  for performing one or more of the operations illustrated at  1202  in  FIG. 12 . Additionally, the processing system  1214  includes an identifying component  1222  for performing one or more of the operations illustrated at  1204  in  FIG. 12 . Further, the processing system  1214  includes a mapping component  1224  for performing one or more of the operations illustrated at  1206  in  FIG. 12 . 
     The receiving component  1220 , the receiving component  1222 , the identifying component  1224 , and the mapping component  1226  may be coupled to the processor  1209  via bus  1221 . In certain aspects, receiving component  1220 , the receiving component  1222 , the identifying component  1224 , and the mapping component  1226  may be hardware circuits. In certain aspects, receiving component  1220 , the receiving component  1222 , the identifying component  1224 , and the mapping component  1226  may be software components that are executed and run on processor  1209 . 
     In some embodiments, the PUSCH rate matching is performed to enable long PUSCH to avoid long PUCCH. As described above, in some embodiments, the UE may receive RMR configuration (e.g., which may include LP CSI-RS) from a serving cell to be configured for performing PUSCH rate matching.  FIG. 13A  illustrates a set of semi-statically configured resources in long PUCCH regions  1302  and  1304 , within UL regular burst UL regular burst, that are reserved for transmitting long PUCCH (e.g., including location in time and frequency, frequency hopping pattern, etc.). 
     In some embodiments, semi-static rate matching may be performed by the UE to allow long PUSCH to avoid the entire long PUCCH regions  1302  and  1304 . The long PUCCH regions  1302  and  1304  are shared by all UEs in a cell (e.g., long PUCCH regions  1302  could be either UE-specifically or cell-specially configured). If PUSCH resource allocation partially overlaps with the configured long PUCCH regions  1302  and  1304 , as described above, the PUSCH resource element (RE) mapping may avoid REs in the long PUCCH regions  1302  and  1304 . This is shown in  FIG. 13B , where certain resources (e.g., unused resources  1303  and  1305 ) in regions  1302  and  1304  allocated for long PUCCH have remained unused when they are not occupied by long PUCCH. In other words,  FIG. 13B  shows PUSCH RE mapping avoiding all REs in the long PUCCH regions  1302  and  1304 . 
     In some other embodiments, dynamic rate matching may be performed by the UE enabling long PUSCH to avoid resources that are actually used for long PUCCH in the regions (e.g., regions  1302  and  1304 ) allocated for long PUCCH. Similar to  FIG. 13A ,  FIG. 14A  also illustrates a set of semi-statically configured resources in long PUCCH regions  1402  and  1404 , within UL regular burst  1400  that is reserved for long PUCCH (e.g., including location in time and frequency, frequency hopping pattern, etc.). Unlike  FIG. 13B , however,  FIG. 14B  illustrates resources  1403  and  1405 , that are not occupied by PUCCH in the regions allocated for PUCCH, to be occupied by PUSCH. Because, as described above, in the embodiments of  FIG. 14B , dynamic rate matching is performed to enable PUSCH to only avoid resources that are actually used by long PUCCH in the regions  1402  and  1404  allocated for long PUCCH. 
     In the embodiments of  FIG. 14B , in the UL grant, the used (or unused) long-PUCCH resources may be indicated in addition to PUSCH resource allocation. However, in some embodiments, the indication may be omitted, if the PUSCH resource allocation does not overlap with the long-PUCCH regions. In some embodiments, the indication may be merged with long-PUCCH resource indication. For example, a UE may receive an indication of a subset of configured resources for rate matching, where one resource in the subset may be further indicated as the resource for its own long-PUCCH transmission in the same slot. 
     In some embodiments, the UE may perform PUSCH rate matching to avoid signals/channels in a UL common burst.  FIG. 15  illustrates an example symbol  1502  in an UL short duration of a slot. In some embodiments, the UE may perform semi-static rate matching such that the PUSCH may avoid the entire UL short duration. For example, in such embodiments, based on the slot format, UE may not map long PUSCH to REs in UL short duration, if long PUSCH exists. 
     In sonic embodiments, the UE may perform semi-static rate matching such that the PUSCH may avoid reserved resources in UL short duration. For example, in such embodiments, the UE may not map PUSCH to resources reserved for short PUCCH. For example,  FIG. 15  shows bandwidth  1502 , which refers to a scheduled bandwidth for a first UE&#39;s short PUSCH. In one example, the UE may not map PUSCH to resources of bandwidth  1502 . which includes resources reserved for short PUSCH. Also, in some embodiments, the UE may not map PUSCH to RE combs reserved for SRS. 
     In some embodiments, the UE (e.g., first UE) may perform dynamic rate matching such that the PUSCH may avoid resources actually used for other signals/channels. In such embodiments, in an UL grant, the UE (e.g., first UE) may receive an indication with which one or more RE combs may be rate-matched around. due to aperiodic SRS transmission. In some embodiments, this may be performed by configuring/indicating (subband-dependent) the ZP SRS resource. For example,  FIG. 15  shows sub-band  1506 , which includes resources over which a second UE transmits aperiodic SRS. Such resources are shown as comb  1508 . As described above, in some embodiments, in sub-band  1508  the first UE may perform dynamic rate matching such that PUSCH may avoid the aperiodic SRS transmissions of the second UE. As such, the first UE&#39;s short PUSCH may be mapped to comb  1510 , which refer to resources over which the second UE does not transmit aperiodic SRS, which comb  1508  is indicated as ZP SRS for the first UE. Note that short PUSCH of the first UE may be mapped to the rest of the resources in sub-band  1506 . For example, short PUSCH of the first UE may be mapped to resources  1512  and  1514 . 
     In some embodiments, the UE may perform PUSCH rate matching around PUCCH without being limited to long PUCCH or UL common burst PUCCH/SRS. In such embodiments, the rate matching may be precoder dependent. For example, in some embodiments, for a UL closed MIMO, the UE may be assigned with a UL precoder in the wideband or subband level. In some embodiments, the PUSCH rate matching occurs only with configured precoders. In such embodiments, a precoder set of PUSCH rate matching may be used. As an example, for PUSCH rank  1 , the total precoder hypothesis includes a set: {p 1 , p 2  . . . , p 8 } (e.g., as shown in  FIG. 16 ), from which {p 1 , p 2 } may be selected. If either p 1  or p 2  precoder is selected on a certain subband, then rate matching is performed on these subbands. 
     For example, for PUCCH rank  2 , both the first layer and the second layer are rate-matched based on the precoder set. In some embodiments, for any other precoder not included in the selected set, no rate matching is performed. In some embodiments, the precoder set may be configured via higher layer signaling/semi-static signaling or dynamic signaling. As discussed, FIG,  16  illustrates a UL regular burst  1600  with a UL long burst  1602 .  FIG. 16  also illustrates an example precoder set {p 1 , p 2  . . . , p 8 }, where p 1  and p 2  are selected or assigned and, therefore, rate matching is performed on the corresponding subbands. 
     In some embodiments, a rate-matching resource (RMR) can be configured separately, for both DL and UL. The configuration may be semi-static or dynamic. A semi-static configuration, in sonic embodiments, may be used for periodic/semi-persistent NZP CSI-RS or long/short PUCCH in neighboring cells. A dynamic configuration, in some embodiments, may be used for aperiodic NZP CSI-RS or long/short. PUCCH in neighboring cells. In some embodiments, a DL rate-matching resource may be linked to multiple DL CSI-RS resources, where the CSI-RS resource corresponds to the neighboring cells&#39; CSI-RS time/frequency resources. In some embodiments, a DL rate-matching resource may be linked to the neighboring cells&#39; SS blocks or even other (radio access technologies&#39;) RATs&#39; (such as LTE) SS blocks or pilot REs. In some embodiments, a UL rate-matching resource may be linked to UL long/short PUCCH configurations that correspond to the neighboring cells&#39; long/short PUCCH resource configuration. In some embodiments, activation or deactivation of a rate-matching resource may be semi-static or dynamic. In sonic embodiments, each linked resource may be activated or deactivated via bitmap-like operations. 
       FIG. 17  illustrates an example RMR  1706 .  FIG. 17  illustrates an aggregation of one or more neighboring cells&#39; CSI-RS setting(s)  1702  and. LTE&#39;s SS blocks setting(s)  1704  into RMR  1706 . In some embodiments, when bath settings (e.g.,  1702  and  1704 ) within the rate-matching resource are aggregated, rate matching is performed by the UE on those reference signals. For example, as shown resources  1708  are rate-matched for LTE PSS/SSS and resources  1710  are rate-matched for the one or more neighboring cell&#39;s CSI-RS. 
     The methods disclosed herein comprise one or more steps or actions for achieving the described 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. 
       101141  As used herein, a phrase referring to at least one of a list of items refers to any combination of those items, including single members. As an example, “at least one of a. b, or c” is intended to cover a, h, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g, a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, h-b, b-h-h, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). 
     As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may 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. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, 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 oilier 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.” Unless specifically stated otherwise, the term “sonic” refers to one or more. 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 under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” 
     The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering. 
     For example, means for transmitting and/or means for receiving may comprise one or more of a transmit processor  420 , a TX MIMO processor  430 , a receive processor  438 , or antennas)  434  of the base station  110  and/or the transmit processor  464 , a TX MIMO processor  466 , a receive processor  458 , or antenna.(s)  452  of the user equipment  120 . Additionally, means for generating, means for multiplexing, and/or means for applying may comprise one or more processors, such as the controller/processor  440  of the base station  110  and/or the controller/processor  480  of the user equipment  120 . 
     The various illustrative logical blocks, modules and circuits described in connection with the present 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 comprise a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PRY 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 link 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 with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the 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 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 include 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 the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium may be coupled to a 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 media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media 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 media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that 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 and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media. 
     Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise 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. 
     Further, it should be appreciated that modules and/or other appropriate 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 can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (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 means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized. 
     It is to be understood that the claims are not limited to the precise configuration and components illustrated 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.