Patent Publication Number: US-2021195583-A1

Title: Uplink transmit beam update using uplink transmission configuration indicator state

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
     This application claims benefit of and priority to U.S. Provisional Application No. 62/949,762, filed Dec. 18, 2019, which is hereby assigned to the assignee hereof and hereby expressly incorporated by reference herein in its entirety as if fully set forth below and for all applicable purposes. 
    
    
     FIELD OF THE DISCLOSURE 
     Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for uplink transmit beam update using uplink transmission configuration indicator (TCI) states. 
     BACKGROUND 
     Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These 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, etc.). Examples of such multiple-access systems include 3rd 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 a number of base stations (BSs), which are each capable of simultaneously supporting communication for multiple communication devices, otherwise known as user equipments (UEs). In an 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, a new radio (NR), 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., which may be referred to as a BS, a 5G NB, a next generation NodeB (gNB or gNodeB), a transmit receive point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS to a UE) and uplink channels (e.g., for transmissions from a UE to a BS or DU). 
     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. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 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). To these ends, NR supports 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 need for further improvements in NR and LTE 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 communication performed by a user equipment (UE). The method generally includes receiving, from a network entity, signaling of an uplink transmission configuration indicator (TCI) state update for one or more uplink transmissions. The method generally includes determining the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The method generally includes applying the uplink TCI state to one or more uplink transmissions in accordance with the determination. 
     Certain aspects of the present disclosure provide a method for wireless communication by a network entity. The method generally includes sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The method generally includes processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     Certain aspects provide an apparatus for wireless communication. The apparatus generally includes at least one processor and memory coupled to the at least one processor. The memory generally includes code executable by the at least one processor to cause the apparatus to receive, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions. The memory generally include code executable by the at least one processor to cause the apparatus to determine the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The memory generally include code executable by the at least one processor to cause the apparatus to apply the uplink TCI state to one or more uplink transmissions in accordance with the determination. 
     Certain aspects provide an apparatus for wireless communication. The apparatus generally includes at least one processor and memory coupled to the at least one processor. The memory generally includes code executable by the at least one processor to cause the apparatus to send, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The memory generally include code executable by the at least one processor to cause the apparatus to process one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     Certain aspects provide an apparatus for wireless communication. The apparatus generally includes means for receiving, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions. The apparatus generally includes means for determining the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The apparatus generally includes means for applying the uplink TCI state to one or more uplink transmissions in accordance with the determination. 
     Certain aspects of the present disclosure provide an apparatus for wireless communication. The apparatus generally includes means for sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The apparatus generally includes means for processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     Certain aspects provide a computer readable medium storing computer executable code thereon for wireless communication. The computer readable medium generally includes code for receiving, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions. The computer readable medium generally includes code for determining the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The computer readable medium generally includes code for applying the uplink TCI state to one or more uplink transmissions in accordance with the determination. 
     Certain aspects of the present disclosure provide a computer readable medium storing computer executable code thereon for wireless communication. The computer readable medium generally includes code for sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The computer readable medium generally includes code for processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     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 appended 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. 
    
    
     
       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 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 showing examples 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. 7  illustrates different synchronization signal blocks (SSBs) sent using different beams, in accordance with certain aspects of the present disclosure. 
         FIG. 8  shows an exemplary transmission resource mapping, according to aspects of the present disclosure. 
         FIG. 9  is a table illustrating example uplink transmission configuration indicator (TCI) states, in accordance with certain aspects of the present disclosure. 
         FIG. 10  is a flow diagram illustrating example operations for wireless communications by a UE, in accordance with certain aspects of the present disclosure. 
         FIG. 11  is a flow diagram illustrating example operations for wireless communications by a network entity, in accordance with certain aspects of the present disclosure. 
         FIG. 12  is a block diagram illustrating an example communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure. 
         FIG. 13  is a block diagram illustrating an example communications 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 
     Aspects of the present disclosure provide apparatus, devices, methods, processing systems, and computer readable mediums for uplink transmit beam update using uplink transmission configuration indicator (TCI) states. 
     Aspects of the present disclosure may help provide a unified framework for uplink and downlink TCI states. For downlink, the TCI indication may be provided via a downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) transmission to the user equipment (UE). Depending on the DCI format, the DCI may carry the TCI information for receiving and decoding PDSCH transmission. There is also an option of activating new downlink TCI states via a medium access control (MAC) control element (MAC-CE). 
     In the unified framework, some DCI formats may carry TCI information for UL transmission. The uplink TCI states provide a mechanism to dynamically indicate parameters to use for uplink traffic. Depending on the type of uplink transmission (e.g., periodic, semi-persistent, dynamic), and the content and channel, the way in which the uplink TCI state is conveyed may be different. 
     The following description provides examples of uplink transmit beam update using uplink TCI states, 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. 
     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 subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. The techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with 3G, 4G, and/or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems. 
     New Radio (NR) is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). 
     NR may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth, millimeter wave (mmW) targeting high carrier frequency, massive machine type communications 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. 
     NR supports beamforming and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support multiple (e.g., up to 8) transmit antennas with multi-layer DL transmissions (e.g., up to 8 streams) and multiple (e.g., up to 2) streams per UE. Aggregation of multiple cells may be supported (e.g., up to 8 serving cells). 
       FIG. 1  illustrates an example wireless communication network  100  (e.g., an NR/5G network), in which aspects of the present disclosure may be performed. For example, the wireless network  100  may include a UE  120  configured to perform operations  1100  of  FIG. 11 . Similarly, a base station  110  (e.g., a gNB) may be configured to perform operations  1200  of  FIG. 12 . As shown in  FIG. 1 , the wireless communication network  100  may be in communication with a core network  132 . The core network  132  may in communication with one or more base station (BSs)  110   a - z  (each also individually referred to herein as BS  110  or collectively as BSs  110 ) and/or user equipment (UE)  120   a - y  (each also individually referred to herein as UE  120  or collectively as UEs  120 ) in the wireless communication network  100  via one or more interfaces. 
     According to certain aspects, the BSs  110  and UEs  120  may be configured for uplink transmit beam updates using uplink TCI states. As shown in  FIG. 1 , the BS  110   a  includes a TCI state manager  112 . The TCI state manager  112  may be configured to send signaling of an uplink TCI state update to be applied by the UE  120   a  for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission, in accordance with aspects of the present disclosure. The UE  120   a  includes a TCI state manager  122 . The TCI state manager  122  may be configured to determine if a TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission, in accordance with aspects of the present disclosure. 
     A BS  110   a  may provide communication coverage for a particular geographic area, sometimes referred to as a “cell”, which may be stationary, or may move according to the location of a mobile BS. In some examples, the BSs  110  may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network  100  through various types of backhaul interfaces (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network. 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. 
     A network controller  130  may couple 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. 
     A network controller  130  may be in communication with a set of BSs  110  and provide coordination and control for these BSs  110  (e.g., via a backhaul). In aspects, the network controller  130  may be in communication with a core network  132  (e.g., a 5G Core Network (5GC)), which provides various network functions such as Access and Mobility Management, Session Management, User Plane Function, Policy Control Function, Authentication Server Function, Unified Data Management, Application Function, Network Exposure Function, Network Repository Function, Network Slice Selection Function, etc. 
       FIG. 2  illustrates an example logical architecture of a distributed Radio Access Network (RAN)  200 , which may be implemented in the wireless communication network  100  illustrated in  FIG. 1 . A 5G access node  206  may include an access node controller (ANC)  202 . ANC  202  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 ANC  202 . The backhaul interface to neighboring next generation access Nodes (NG-ANs)  210  may terminate at ANC  202 . ANC  202  may include one or more transmission reception points (TRPs)  208  (e.g., cells, BSs, gNBs, etc.). 
     The TRPs  208  may be a distributed unit (DU). TRPs  208  may be connected to a single ANC (e.g., ANC  202 ) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, TRPs  208  may be connected to more than one ANC. TRPs  208  may each include one or more antenna ports. TRPs  208  may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. 
     The logical architecture of distributed RAN  200  may support various backhauling and fronthauling solutions. This support may occur via and across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). 
     The logical architecture of distributed RAN  200  may share features and/or components with LTE. For example, next generation access node (NG-AN)  210  may support dual connectivity with NR and may share a common fronthaul for LTE and NR. 
     The logical architecture of distributed RAN  200  may enable cooperation between and among TRPs  208 , for example, within a TRP and/or across TRPs via ANC  202 . An inter-TRP interface may not be used. 
     Logical functions may be dynamically distributed in the logical architecture of distributed RAN  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 (e.g., TRP  208 ) or CU (e.g., ANC  202 ). 
       FIG. 3  illustrates an example physical architecture of a distributed Radio Access Network (RAN)  300 , according to aspects of the present disclosure. A centralized core network unit (C-CU)  302  may host core network functions. C-CU  302  may be centrally deployed. C-CU  302  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  304  may host core network functions locally. The C-RU  304  may have distributed deployment. The C-RU  304  may be close 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 BS  110   a  and UE  120   a  (e.g., the wireless communication network  100  of  FIG. 1 ), which may be used to implement aspects of the present disclosure. 
     At the BS  110   a , 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), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH). 
     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 transmit processor  420  may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS). 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) in transceivers  432   a - 432   t . Each modulator in transceivers  432   a - 432   t  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 the modulators in transceivers  432   a - 432   t  may be transmitted via the antennas  434   a - 434   t , respectively. 
     At the UE  120   a , the antennas  452   a - 452   r  may receive the downlink signals from the BS  110   a  and may provide received signals to the demodulators (DEMODs) in transceivers  454   a - 454   r , respectively. Each demodulator in transceivers  454   a - 454   r  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 the demodulators in transceivers  454   a - 454   r , 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   a  to a data sink  460 , and provide decoded control information to a controller/processor  480 . 
     On the uplink, at UE  120   a , 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 (e.g., for the 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 modulators in transceivers  454   a - 454   r  (e.g., for SC-FDM, etc.), and transmitted to the BS  110   a . At the BS  110   a , the uplink signals from the UE  120   a  may be received by the antennas  434 , processed by the demodulators in transceivers  432   a - 432   t , 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   a . 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 memories  442  and  482  may store data and program codes for BS  110   a  and UE  120   a , respectively. A scheduler  444  may schedule UEs for data transmission on the downlink and/or uplink. 
     Antennas  452 , processors  466 ,  458 ,  464 , and/or controller/processor  480  of the UE  120   a  and/or antennas  434 , processors  420 ,  430 ,  438 , and/or controller/processor  440  of the BS  110   a  may be used to perform the various techniques and methods described herein. For example, as shown in  FIG. 2 , the controller/processor  440  of the BS  110   a  has a TCI state manager  441  that sends signaling of an uplink TCI state update to be applied by the UE  120   a  for a dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmissions, or periodic uplink transmissions, according to aspects described herein. As shown in  FIG. 2 , the controller/processor  480  of the UE  120   a  has a TCI state manager  481  that determines if a TCI state update is to be applied for a dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmissions, or periodic uplink transmissions, according to aspects described herein. Although shown at the controller/processor, other components of the UE  120   a  and BS  110   a  may be used to perform the operations described herein. 
       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 wireless communication system, such as a 5G 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. In the second option, RRC layer  510 , PDCP layer  515 , RLC layer  520 , MAC layer  525 , and PHY layer  530  may each be implemented by the AN. The second option  505 - b  may be useful in, for example, 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 as shown in  505 - c  (e.g., the RRC layer  510 , the PDCP layer  515 , the RLC layer  520 , the MAC layer  525 , and the PHY layer  530 ). 
     NR may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. NR may support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Modulation symbols may be 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 may be dependent on the system bandwidth. The minimum resource allocation, called a resource block (RB), may be 12 consecutive subcarriers. The system bandwidth may also be partitioned into subbands. For example, a subband may cover multiple RBs. NR may support a base subcarrier spacing (SCS) of 15 KHz and other SCS may be defined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.). 
       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 partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots (e.g., 1, 2, 4, 8, 16, . . . slots) depending on the SCS. Each slot may include a variable number of symbol periods (e.g., 7, 12, or 14 symbols) depending on the SCS. The symbol periods in each slot may be assigned indices. A sub-slot structure may refer to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols). Each symbol in a slot may be configured for 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 directions may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information. 
     In NR, a synchronization signal block (SSB) is transmitted. In certain aspects, SSBs may be transmitted in a burst where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and/or beam refinement). The SSB includes a PSS, a SSS, and a two symbol PBCH. The SSB can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in  FIG. 3 . The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SSBs may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SSB can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmWave. The multiple transmissions of the SSB are referred to as a SS burst set. SSBs in an SS burst set may be transmitted in the same frequency region, while SSBs in different SS bursts sets can be transmitted at different frequency regions. 
     As shown in  FIG. 7 , the SS blocks may be organized into SS burst sets to support beam sweeping. As shown, each SSB within a burst set may be transmitted using a different beam, which may help a UE quickly acquire both transmit (Tx) and receive (Rx) beams (particular for mmW applications). A physical cell identity (PCI) may still decoded from the PSS and SSS of the SSB. 
     Certain deployment scenarios may include one or both NR deployment options. Some may be configured for non-standalone (NSA) and/or standalone (SA) option. A standalone cell may need to broadcast both SSB and remaining minimum system information (RMSI), for example, with SIB1 and SIB2. A non-standalone cell may only need to broadcast SSB, without broadcasting RMSI. In a single carrier in NR, multiple SSBs may be sent in different frequencies, and may include the different types of SSB. 
     Operating characteristics of a gNB in an NR communications system may be dependent on a frequency range (FR) in which the system operates. A frequency range may include one or more operating bands (e.g., “n1” band, “n2” band, “n7” band, and “n41” band, etc.). A communications system (e.g., one or more gNBs and UEs) may operate in one or more operating bands. 
     A control resource set (CORESET) for an orthogonal frequency division multiple access (OFDMA) system (e.g., a communications system transmitting physical downlink control channel (PDCCH) using OFDMA waveforms) may include one or more control resource (e.g., time and frequency resources) sets configured for conveying PDCCH, within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. Search spaces are generally areas or portions where a communication device (e.g., a UE) may look for (e.g., monitor) control information. 
     A CORESET may be defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) of tones in one symbol period (e.g., a symbol period of a slot), where one tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). Sets of CCEs may be used to transmit new radio PDCCHs (NR-PDCCHs), with different numbers of CCEs in the sets used to transmit NR-PDCCHs using differing aggregation levels. Multiple sets of CCEs may be defined as search spaces for UEs. A gNB may transmit a NR-PDCCH to a UE in a set of CCEs, called a decoding candidate, within a search space for the UE. The UE may receive the NR-PDCCH by searching (e.g., monitoring) in search spaces and decoding the NR-PDCCH. 
     During initial access, a UE may identify an initial CORESET (e.g., referred to as CORESET #0) configuration from an indication (e.g., a pdcchConfigSIB1 field) in system information (e.g., in a maser information block (MIB) carried in PBCH). This initial CORESET may then be used to configure the UE (e.g., with other CORESETs and/or bandwidth parts via dedicated (UE-specific) signaling). When the UE detects a control channel in the CORESET, the UE attempts to decode the control channel, and the UE communicates with the transmitting BS (e.g., the transmitting cell) according to the control information provided in a decoded control channel. 
     When a UE is connected to a cell (or BS), the UE may receive a master information block (MIB). The MIB can be in a synchronization signal and physical broadcast channel (SS/PBCH) block (e.g., in the PBCH of the SS/PBCH block) on a synchronization raster (sync raster). In some scenarios, the sync raster may correspond to a synchronization signal block (SSB). From the frequency of the sync raster, the UE may determine an operating band of the cell. Based on a cell&#39;s operation band, the UE may determine a minimum channel bandwidth and a subcarrier spacing (SCS) of the channel. The UE may then determine an index from the MIB (e.g., four bits in the MIB, conveying an index in a range 0-15). 
     Given this index, the UE may look up or locate a CORESET configuration (this initial CORESET configured via the MIB is generally referred to as the CORESET #0). This may be accomplished from one or more tables of CORESET configurations. These configurations (including single table scenarios) may include various subsets of indices indicating valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of indices in the table. 
     Alternatively or additionally, the UE may select a search space CORESET configuration table from several tables of CORESET configurations. These configurations can be based on a minimum channel bandwidth and SCS. The UE may then look up a CORESET configuration (e.g., a Type0-PDCCH search space CORESET configuration) from the selected table, based on the index. After determining the CORESET configuration (e.g., from the single table or the selected table), the UE may then determine the CORESET to be monitored (as mentioned above) based on the location (in time and frequency) of the SS/PBCH block and the CORESET configuration. 
       FIG. 8  shows an example transmission resource mapping  800 , according to aspects of the present disclosure. In the mapping, a BS (e.g., BS  110   a , shown in  FIG. 1 ) transmits an SS/PBCH block  802 . The SS/PBCH block includes a MIB conveying an index to a table that relates the time and frequency resources of the CORESET  804  to the time and frequency resources of the SS/PBCH block. 
     The BS may also transmit control signaling. In some scenarios, the BS transmits the control signaling in a PDCCH to a UE (e.g., UE  120   a , shown in  FIG. 1 ) in the (time/frequency resources of the) CORESET  804 . The PDCCH may schedule a PDSCH  806 . The BS then transmits the PDSCH  806  to the UE. The UE may receive the MIB in the SS/PBCH block  802 , determine the index, look up a CORESET configuration based on the index, and determine the CORESET  804  from the CORESET configuration and the SS/PBCH block. The UE may then monitor the CORESET  804 , decode the PDCCH in the CORESET  804 , and receive the PDSCH  806  that was allocated by the PDCCH. 
     Different CORESET configurations may have different parameters that define a corresponding CORESET. For example, each configuration may indicate a number of resource blocks (e.g., 24, 48, or 96), a number of symbols (e.g., 1-3), as well as an offset (e.g., 0-38 RBs) that indicates a location in frequency. 
     As discussed above, aspects of the disclosure related to uplink transmit beam state using transmission configuration indication (TCI). 
     It may be desirable for a UE to know which assumptions the UE can make on a channel for different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS for scheduling, link adaptation, and/or beam management purposes. In NR, the concept of quasi co-location (QCL) and TCI states is used to convey information about these assumptions. 
     QCL assumptions are generally defined in terms of channel properties. 3GPP TS 38.214 defines QCL as “two antenna ports are said to be quasi-co-located if properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed.” Different reference signals (RSs) may be considered quasi co-located (QCL&#39;d) if a receiver (e.g., a UE) can apply channel properties determined by detecting a first reference signal to help detect a second signal. TCI states generally include configurations such as QCL-relationships, for example, between the downlink (DL) RSs in one CSI-RS set and the PDSCH demodulation reference signal (DMRS) ports. 
     In some cases, a UE may be configured with up to M TCI states. Configuration of the M TCI states may be via higher layer signalling (e.g., a higher layer parameter TCI-States). A UE may be signalled to decode PDSCH according to a detected PDCCH with downlink control information (DCI) indicating one of the TCI states. Each configured TCI state may include one RS set (e.g., by higher layer parameter TCI-RS-SetConfig) that indicates different QCL assumptions between certain source and target signals. 
     QCL signaling may be provided for RSs and channels across scenarios involving multiple cells, such as in coordinated multipoint (CoMP) scenarios in which multiple transmit receive points (TRPs) or integrated access and backhaul (IAB) nodes each have their own cell ID. 
       FIG. 9  is a table  900  illustrating examples of the association of DL reference signals with corresponding QCL types that may be indicated by a parameter (e.g., TCI-RS-SetConfig). The table  900  shows source RSs, target RSs, and QCL type assumptions that may be configured by a valid UL-TCI state configuration. The target signal generally refers to a signal for which channel properties may be inferred by measuring those channel properties for an associated source signal. As noted above, a UE may use the source RS to determine various channel parameters, depending on the associated QCL type, and use those various channel properties (determined based on the source RS) to process the target signal. Examples of source RSs include phase tracking reference signals (PTRSs), SSBs, sounding reference signal (SRS), and/or CSI-RSs (e.g., CSI-RS for beam management). Examples of target RSs include aperiodic tracking reference signals (TRSs), periodic TRSs, PRACHs, PUCCHs, and/or PUSCHs. The QCL types include the QCL types A/B/C/D discussed below. 
     For the case of two source RSs, the different QCL types can be configured for the same target RS. In the illustrative example, SSB is associated with Type C QCL for P-TRS, while CSI-RS for beam management (CSI-RS-BM) is associated with Type D QCL. 
     QCL types indicated to the UE can be based on a higher layer parameter (e.g., higher layer parameter QCL-Type). QCL types may take one or a combination of the following types: 
     QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}, 
     QCL-TypeB: {Doppler shift, Doppler spread}, 
     QCL-TypeC: {average delay, Doppler shift}, and 
     QCL-TypeD: {Spatial Rx parameter}, 
     Spatial QCL assumptions (QCL-TypeD) may be used to help a UE to select an analog receive (Rx) beam (e.g., during beam management procedures). For example, an SSB resource indicator may indicate a same beam for a previous reference signal should be used for a subsequent transmission. 
     An information element (e.g., CORESET IE) sent via RRC signaling may convey information regarding a CORESET configured for a UE. The CORESET IE generally includes a CORESET ID, an indication of frequency domain resources (e.g., number of RBs) assigned to the CORESET, contiguous time duration of the CORESET in a number of symbols, and Transmission Configuration Indicator (TCI) states. 
     As noted above, a subset of the TCI states provide QCL relationships between DL RS(s) in one RS set (e.g., a TCI-Set) and another signal (e.g., DMRS ports for another transmission). A particular TCI state for a given UE (e.g., for unicast PDCCH) may be conveyed to the UE by a MAC-CE. The TCI state may be selected from the set of TCI states conveyed by the CORESET IE, with the initial CORESET (CORESET #0) generally configured via MIB. 
     Search space information may also be provided via RRC signaling. For example, the SearchSpace IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with one CORESET. The SearchSpace IE identifies a search space configured for a CORESET by a search space ID. In an aspect, the search space ID associated with CORESET #0 is SearchSpace ID #0. The search space is generally configured via PBCH (e.g., carried in the MIB). 
     Aspects of the present disclosure relate to techniques for uplink transmission indicated by the uplink TCI. 
     Example Uplink Transmit Beam Update Using Uplink TCI State 
     Aspects of the present disclosure may help provide a unified framework for uplink (UL) and downlink (DL) transmission configuration indicator (TCI) states. For downlink, the TCI indication may be provided via a downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) transmission to the user equipment (UE). Depending on the DCI format, the DCI may carry the TCI information for receiving and decoding PDSCH transmission. There is also an option of activating new downlink TCI states via a medium access control (MAC) control element (MAC-CE). 
     In the unified framework, some DCI formats may carry TCI information for uplink transmission. The uplink TCI states provide a mechanism to dynamically indicate parameters to use for uplink traffic. Depending on the type of uplink transmission (e.g., periodic, semi-persistent, dynamic), and the content and channel, the way in which the uplink TCI state is conveyed may be different. 
     According to certain aspects, in additional to dynamically scheduled uplink transmission, the uplink TCI state may also update for semi-persistent and/or periodic uplink transmission. 
       FIG. 10  illustrates example operations  1000  for wireless communications, in accordance with certain aspects of the present disclosure. For example, operations  1000  may be performed by a UE (e.g.,  120   a  of  FIG. 1 ). The operations  1000  may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor  480  of  FIG. 2 ). Further, the transmission and reception of signals by the UE in operations  1000  may be enabled, for example, by one or more antennas (e.g., antennas  452  of  FIG. 2 ). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor  480 ) obtaining and/or outputting signals. 
     Operations  1000  begin, at  1002 , by receiving, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions. The uplink TCI state update may indicate an update for a beam and/or path loss reference signal to be used for the one or more uplink transmissions. The one or more uplink transmissions may a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a sounding reference signal (SRS) transmission, and/or a physical random access channel (PRACH) transmission. The signaling of the uplink TCI state update may include downlink control information (DCI) signaling that dynamically schedules the one or more uplink transmissions to which the TCI state update is to be applied. 
     At  1004 , the UE determines the uplink TCI state update is to be applied for a dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. Depending on the type of uplink transmission (e.g., periodic, semi-persistent, dynamic), and the content and channel, the way in which the uplink TCI state is conveyed may be different. 
     At  1006 , the UE applies the uplink TCI state update to one or more uplink transmissions in accordance with the determination. Applying the TCI state update to the one or more uplink transmissions in accordance with the determination may involve applying the TCI state update to the one or more uplink transmission after a preconfigured number of symbols from receiving the signaling of the uplink TCI state update. 
       FIG. 11  illustrates example operations  1100  for wireless communications, in accordance with certain aspects of the present disclosure. For example, operations  1100  may be performed by a network entity, such as a base station (BS) (e.g., BS  110   a  of  FIG. 1 , which may be a gNB) to signal uplink TCI states to a UE performing operations  1000  of  FIG. 10 . The operations  1100  may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor  240  of  FIG. 2 ). Further, the transmission and reception of signals by the BS in operations  1100  may be enabled, for example, by one or more antennas (e.g., antennas  234  of  FIG. 2 ). In certain aspects, the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller/processor  240 ) obtaining and/or outputting signals. 
     Operations  1100  begin, at  1102 , by sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission. The uplink TCI state update may indicate an update for a beam and/or path loss reference signal to be used for the one or more uplink transmissions. The one or more uplink transmissions may include a PUCCH transmission, a PUSCH transmission, a SRS transmission, or a PRACH transmission. The signaling of the uplink TCI state update may include DCI signaling that dynamically schedules the one or more uplink transmissions to which the TCI state update is to be applied. 
     At  1104 , the network entity processes one or more uplink transmissions sent by the UE after applying the uplink TCI state update. Depending on the type of uplink transmission (e.g., periodic, semi-persistent, dynamic), and the content and channel, the way in which the uplink TCI state is conveyed may be different. 
     In some aspects, uplink TCI states may be used to update beam and/or path loss (PL) RS for dynamically scheduled, semi-persistent, and/or periodic uplink transmissions. PL RS may be used for power control of uplink transmissions. 
     According to certain aspects, the type of signaling used to indicate the uplink TCI update is based on the type, content, and/or channel of uplink transmission. For example, a DCI that schedules an aperiodic or dynamic transmission, such as a DCI that schedules a PUSCH transmission for an aperiodic SRS report, a DCI that schedules an SRS transmission, or a DCI that schedules an uplink RACH, may be used to carry the uplink TCI state information. On the other hand, for a periodic uplink transmission, such as to update the resource used for a periodic PUSCH or a periodic SRS, RRC or MAC-CE signaling can be used to send the uplink TCI update because the transmissions are not as dynamic and will be repeated over time. Because the longer term periodic scheduled transmissions are repeated over time, the uplink TCI update may not need to be sent as quickly, and, therefore, may not be limited to DCI signaling for the update. Thus, the BS can determine the signaling to use for sending an uplink TCI update based on the type of the uplink traffic. 
     In some examples, uplink TCI states may be indicated in DCI that dynamically schedules uplink transmissions. For example, DCI may be used to send the uplink TCI update when the DCI dynamically schedules uplink transmissions, such as dynamic PUSCH, PUCCH, SRS, and/or PRACH. 
     In some examples, uplink TCI states may be indicated in DCI that activates (or reactivates) semi-persistent uplink transmissions. For example, DCI may be used to send the uplink TCI update when the DCI actives (or reactivates) semi-persistent uplink transmissions, such as configured grant (CG) based PUSCH and/or semi-persistent SRS transmissions. 
     In some examples, uplink TCI states may be indicated for periodic uplink transmissions. For example, these uplink TCI states may be indicated via radio resource control (RRC), MAC-CE), and/or DCI signalling. Because the TCI states in this case apply to a longer term periodic scheduled transmission, the signalling does not have to be as fast, so it does not need to be limited to DCI. The periodic uplink transmissions may include periodic PUCCH and/or periodic SRS. For example, the RRC or MAC-CE signaling may be used to send the uplink TCI update for periodic uplink transmissions. 
       FIG. 12  illustrates a communications device  1200  that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in  FIG. 10 . The communications device  1200  includes a processing system  1202  coupled to a transceiver  1208  (e.g., a transmitter and/or a receiver). The transceiver  1208  is configured to transmit and receive signals for the communications device  1200  via an antenna  1210 , such as the various signals as described herein. The processing system  1202  may be configured to perform processing functions for the communications device  1200 , including processing signals received and/or to be transmitted by the communications device  1200 . 
     The processing system  1202  includes a processor  1204  coupled to a computer-readable medium/memory  1212  via a bus  1206 . In certain aspects, the computer-readable medium/memory  1212  is configured to store instructions (e.g., computer-executable code) that when executed by the processor  1204 , cause the processor  1204  to perform the operations illustrated in  FIG. 10 , or other operations for performing the various techniques discussed herein for uplink transmit beam update using uplink TCI states. In certain aspects, computer-readable medium/memory  1212  stores code  1214  for receiving, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions; code  1216  for determining the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission; and code  1218  for applying the uplink TCI state to one or more uplink transmissions in accordance with the determination. In certain aspects, the processor  1204  has circuitry configured to implement the code stored in the computer-readable medium/memory  1212 . The processor  1204  includes circuitry  1224  for receiving, from a network entity, signaling of an uplink TCI state update for one or more uplink transmissions; circuitry  1226  for determining the uplink TCI state update is to be applied for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission; and circuitry  1228  for applying the TCI state to one or more uplink transmissions in accordance with the determination. 
       FIG. 13  illustrates a communications device  1300  that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in  FIG. 11 . The communications device  1300  includes a processing system  1302  coupled to a transceiver  1308  (e.g., a transmitter and/or a receiver). The transceiver  1308  is configured to transmit and receive signals for the communications device  1300  via an antenna  1310 , such as the various signals as described herein. The processing system  1302  may be configured to perform processing functions for the communications device  1300 , including processing signals received and/or to be transmitted by the communications device  1300 . 
     The processing system  1302  includes a processor  1304  coupled to a computer-readable medium/memory  1312  via a bus  1306 . In certain aspects, the computer-readable medium/memory  412  is configured to store instructions (e.g., computer-executable code) that when executed by the processor  1304 , cause the processor  1304  to perform the operations illustrated in  FIG. 11 , or other operations for performing the various techniques discussed herein for uplink transmit beam update using uplink TCI states. In certain aspects, computer-readable medium/memory  1312  stores code  1314  for sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission; and code  1316  for processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. In certain aspects, the processor  1304  has circuitry configured to implement the code stored in the computer-readable medium/memory  1312 . The processor  1304  includes circuitry  1324  for sending, to a UE, signaling of an uplink TCI state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission; and circuitry  1326  for processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     Example Aspects 
     In a first aspect, a method of wireless communications by a user equipment (UE), includes receiving, from a network entity, signaling of an uplink transmission configuration indicator (TCI) state update for one or more uplink transmissions; determining the uplink TCI state update is to be applied for a dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmissions, or periodic uplink transmissions; and applying the uplink TCI state update to one or more uplink transmissions in accordance with the determination. 
     In a second aspect, in combination with the first aspect, the uplink TCI state update indicates an update for at least one of: a beam or path loss (PL) reference signal (RS) to be used for the one or more uplink transmissions. 
     In a third aspect, in combination with the second aspect, the one or more uplink transmissions includes at least one of: a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, a sounding reference signal (SRS) transmission, or a physical random access channel (PRACH) transmission. 
     In a fourth aspect, in combination with any of the first through third aspects, the signaling of the uplink TCI state update includes downlink control information (DCI) signaling that dynamically schedules the one or more uplink transmissions to which the TCI state update is to be applied. 
     In a fifth aspect, in combination with the fourth aspect, the DCI dynamically schedules at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a sounding reference signal (SRS), or a physical random access channel (PRACH). 
     In a sixth aspect, in combination with any of the first through fifth aspects, the signaling of the uplink TCI state update includes downlink control information (DCI) signaling that activates or re-activates one or more semi-persistent uplink transmissions to which the TCI state update is to be applied. 
     In a seventh aspect, in combination with the sixth aspect, the DCI activates or re-activates at least one of a configured grant (CG) based physical uplink shared channel (PUSCH) or semi-persistent sounding reference signal (SRS) transmission. 
     In an eighth aspect, in combination with any of the first through seventh aspects, the uplink TCI state update is to be applied to a periodic uplink transmission; and the signaling of the uplink TCI state update includes at least one of radio resource control (RRC) signaling, a media access control (MAC) control element (CE), or a downlink control information (DCI). 
     In a ninth aspect, in combination with the eighth aspect, the periodic uplink transmission includes at least one of a periodic physical uplink control channel (PUCCH) or a periodic sounding reference signal (SRS) transmission. 
     In a tenth aspect, in combination with any of the first through ninth aspects, applying the TCI state update to the one or more uplink transmissions in accordance with the determination includes applying the TCI state to the one or more uplink transmissions after a preconfigured number of symbols from receiving the signaling of the uplink TCI state update. 
     In an eleventh aspect, a method of wireless communications by a network entity includes sending, to a user equipment (UE), signaling of an uplink transmission configuration indicator (TCI) state update to be applied by the UE for dynamically scheduled uplink transmission, semi-persistently scheduled uplink transmission, or periodic uplink transmission; and processing one or more uplink transmissions sent by the UE after applying the uplink TCI state update. 
     In an twelfth aspect, in combination with the eleventh aspect, the uplink TCI state update indicates an update for at least one of: a beam or path loss (PL) reference signal (RS) to be used for the one or more uplink transmissions. 
     In a thirteenth aspect, in combination with any of the eleventh through twelfth aspects, the method further includes determining a type of signaling to use for sending of the uplink TCI state update based on type of the one or more uplink transmissions to which the uplink TCI state update applies. 
     In a fourteenth aspect, in combination with any of the eleventh through thirteenth aspects, the signaling of the uplink TCI state includes downlink control information (DCI) signaling that dynamically schedules the one or more uplink transmissions to which the TCI state update is to be applied. 
     In a fifteenth aspect, in combination with the fourteenth aspect, the DCI dynamically schedules at least one of a physical uplink shared channel (PUSCH) transmission, a physical uplink control channel (PUCCH) transmission, a sounding reference signal (SRS) transmission, or a physical random access channel (PRACH) transmission. 
     In a sixteenth aspect, in combination with any of the eleventh through fifteenth aspects, the signaling of the uplink TCI state update includes downlink control information (DCI) signaling that activates or re-activates one or more semi-persistent uplink transmissions to which the TCI state update is to be applied. 
     In a seventeenth aspect, in combination with the sixteenth aspect, the DCI activates or re-activates at least one of a configured grant (CG) based physical uplink shared channel (PUSCH) or semi-persistent sounding reference signal (SRS) transmission. 
     In an eighteenth aspect, in combination with any of the eleventh through seventeenth aspects, the uplink TCI state update is to be applied to a periodic uplink transmission; and the signaling of the uplink TCI state update includes at least one of radio resource control (RRC) signaling, a media access control (MAC) control element (CE), or a downlink control information (DCI). 
     In a nineteenth aspect, in combination with the eighteenth aspect, the periodic uplink transmission includes at least one of a periodic physical uplink control channel (PUCCH) transmission or a periodic sounding reference signal (SRS) transmission. 
     In a twentieth aspect, in combination with any of the eleventh through nineteenth aspects, applying the TCI state to the one or more uplink transmissions in accordance with the determination includes applying the TCI state to the one or more uplink transmissions after a preconfigured number of symbols from receiving the signaling of the uplink TCI state update. 
     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. 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-UTRA), 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). 
     In 3GPP, the term “cell” can refer to a coverage area of a Node B (NB) and/or a NB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and BS, next generation NodeB (gNB or gNodeB), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. 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 an 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. ABS for a femto cell may be referred to as a femto BS or a home BS. 
     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 (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a healthcare device, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, virtual reality goggles, 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, a robot, a drone, industrial manufacturing equipment, a positioning device (e.g., GPS, Beidou, terrestrial), or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices, which may include remote devices that may communicate with a base station, another remote device, or some other entity. Machine type communications (MTC) may refer to communication involving at least one remote device on at least one end of the communication and may include forms of data communication which involve one or more entities that do not necessarily need human interaction. MTC UEs may include UEs that are capable of MTC communications with MTC servers and/or other MTC devices through Public Land Mobile Networks (PLMN), for example. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, cameras, 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. MTC UEs, as well as other UEs, may be implemented as Internet-of-Things (IoT) devices, e.g., narrowband IoT (NB-IoT) devices. 
     In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell. 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. In some examples, a UE may function 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 communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may communicate directly with one another in addition to communicating with a scheduling entity. 
     The methods disclosed herein comprise one or more steps or actions for achieving the methods. 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 single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, 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, b-b, b-b-b, 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 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 of the 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 “some” 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(f) 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. 
     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 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 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 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. For example, instructions for performing the operations described herein and illustrated in  FIGS. 10 and 11 . 
     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.