Signaling for enabling uplink transmission configuration indicator status

Abstract

Certain aspects of the present disclosure provide techniques that may allow a base station and a user equipment (UE) to use an uplink transmission configuration indicator (TCI) state. An example method generally includes: providing signaling to a network entity indicating that the UE supports an uplink transmission configuration indicator (TCI) state indicating one or more quasi co-location (QCL) types for one or more reference signals (RS) to be applied to an uplink transmission; receiving a UL TCI after sending the indication; and sending the uplink transmission according to the uplink TCI.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. application No. 17 / 116,633, filed on December 9, 2020, which claims the benefit and priority of U.S. Provisional Patent Application S / N. 62 / 948,166, filed on December 13, 2019, both of which are assigned to the assignee of this application and the contents of which are hereby incorporated by reference in their entirety. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for enabling use of uplink transmission configuration indicator (TCI) status for updating parameters for uplink transmissions from a UE to a network entity. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, 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 Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0005] In some examples, a wireless multiple access communication system may include several base stations (BS), each of which is capable of simultaneously supporting communication of multiple communication devices (also referred to as user equipment (UE)). In an LTE or LTE-A network, a set of one or more base stations may define an evolved B node (eNB). In other examples (e.g., in a next generation, new radio (NR), or 5G network), a wireless multiple access communication system may include several distributed units (DU) (e.g., edge units (EU), edge nodes (EN), radio heads (RH), smart radio heads (SRH), transmission reception points (TRP), etc.) in communication with several central units (CU) (e.g., central nodes (CN), access node controllers (ANC), etc.), wherein 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 base station, a 5G NB, a next generation B node (gNB or g B node), a TRP, etc.). A base station or distributed unit may communicate with a set of UEs on downlink channels (eg, for transmissions from or to the base station) and uplink channels (eg, for transmissions from the UE to the base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. It is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0008] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0009] Certain aspects of the present disclosure provide a method for wireless communication by a user equipment (UE). The method generally includes: signaling to a network entity an indication that the UE supports an uplink transmission configuration indicator (TCI) state with one or more quasi co-location (QCL) types for one or more reference signals (RS) to be applied to an uplink transmission; receiving a UL TCI after sending the indication; and sending the uplink transmission according to the uplink TCI.

[0010] Certain aspects provide a method for wireless communication performed by a network entity. The method generally includes: receiving signaling from a user equipment (UE) indicating that the UE supports an uplink transmission configuration indicator (TCI) state with one or more quasi co-location (QCL) types for one or more reference signals (RS) to be applied to an uplink transmission; sending a UL TCI after receiving the indication; and receiving the uplink transmission according to the uplink TCI.

[0011] Aspects of the present disclosure provide apparatuses, devices, processors, and computer-readable media for performing the methods described herein.

[0012] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

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

[0015] Figure 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.

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

[0017] Figure 4is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

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

[0019] Figure 6 An example of a frame format for a New Radio (NR) system is illustrated in accordance with certain aspects of the present disclosure.

[0020] Figure 7 Illustrated how different synchronization signal blocks (SSBs) may be sent using different beams in accordance with certain aspects of the present disclosure.

[0021] Figure 8 Exemplary transmission resource mappings according to aspects of the present disclosure are shown.

[0022] Fig. 9 An example quasi-co-location (QCL) relationship is illustrated in accordance with certain aspects of the present disclosure.

[0023] Fig.10

[0013] Example operations for wireless communications by a user equipment (UE) are illustrated, in accordance with certain aspects of the present disclosure.

[0024] Fig.11

[0013] Example operations for wireless communications by a network entity are illustrated in accordance with certain aspects of the present disclosure.

[0025] Fig.12 is a call flow diagram illustrating example messages that may be exchanged between a UE and a network entity to signal the UE's support for an uplink transmission configuration indicator (TCI) state, in accordance with certain aspects of the present disclosure.

[0026] Fig.13 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0027] Fig.14 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0028] 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 in other aspects without specific recitation. DETAILED DESCRIPTION

[0029] Aspects of the present disclosure provide apparatus, devices, methods, processing systems, and computer-readable media for enabling uplink transmission configuration indicator (TCI) states for uplink beam and / or path loss reference signal (PLRS) updates.

[0030] The following description provides examples rather than limiting the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality as supplements to the various aspects of the present disclosure set forth herein or in addition. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or explanation". Any aspect described as "exemplary" herein is not necessarily to be interpreted as being superior to or superior to other aspects.

[0031] The technology described herein can 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 can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes other variants of Wideband CDMA (WCDMA) and CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS).

[0032] New Radio (NR) is an emerging wireless communication technology being developed in collaboration with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called "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, although various aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technologies.

[0033] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical services targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0034] Example Wireless Communication System

[0035] Figure 1 An example wireless communication network 100 (e.g., an NR / 5G network) is illustrated in which aspects of the present disclosure may be performed. For example, the wireless network 100 may include a network configured to perform Fig.10 Operation 1000 of determining spatial quasi co-location (QCL) information for UE 120. In some cases, the UE may use the determined spatial QCL information to process a physical downlink control channel (PDCCH) transmission sent in an initial CORESET on an initial BWP. Similarly, base station 110 (e.g., gNB) may be configured to perform Fig.11 Operation 1100 of signaling spatial QCL information to UE 120 and transmitting PDCCH in an initial CORESET and an initial downlink BWP. In other examples, supplemental and / or subsequent control and bandwidth information may also be used relative to the first or initial control and bandwidth information (e.g., as may be used in addition to, in place of, or in lieu of the first or initial control and bandwidth information, as desired).

[0036] like Figure 1 As illustrated in , the wireless network 100 may include several base stations (BS) 110 and other network entities. A BS may be a station that communicates with a user equipment (UE). Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a B node and / or a B node subsystem serving the coverage area, depending on the context in which the term is used. In the NR system, the term "cell" and the next generation B node (gNB), new radio base station (NRBS), 5G NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move according to the location of the mobile BS. In some examples, the base station may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (such as direct physical connections, wireless connections, virtual networks, or analogs using any suitable transmission networks).

[0037] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, 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.

[0038] A base station (BS) may provide communication coverage for macro cells, pico cells, femto cells, 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 subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, 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 Figure 1In the example shown in FIG. 1 , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

[0039] The wireless communication network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions 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. Figure 1 In the example shown in , a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.

[0040] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).

[0041] The wireless communication network 100 may support synchronous or asynchronous operation. For synchronous operation, each BS may have similar frame timing, and transmissions from different BSs may be roughly aligned in time. For asynchronous operation, each BS 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.

[0042] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. Network controller 130 may communicate with BSs 110 via a backhaul. BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0043] UEs 120 (e.g., 120x, 120y, 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 (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor / device, a wearable device (such as a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.)), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a gaming device, an augmented reality device (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs may be considered as 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., which may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0045] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0046] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR. NR may utilize OFDM with CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas (with multi-layer DL transmissions of up to 8 streams) and up to 2 streams per UE. Multi-layer transmissions of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

[0047] In some scenarios, air interface access may be scheduled. For example, a scheduling entity (e.g., a base station (BS), a Node B, an eNB, a gNB, etc.) may allocate resources for communication among some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities may utilize resources allocated by one or more scheduling entities.

[0048] A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs can use the resources scheduled by the UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, UEs can communicate directly with each other in addition to communicating with the scheduling entity.

[0049] Return to Figure 1 , which illustrates various potential deployments for various deployment scenarios. For example, in Figure 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 a downlink and / or uplink. A thin dashed line with double arrows indicates interfering transmissions between the UE and the BS. Other lines illustrate component-to-component (e.g., UE-to-UE) communication options.

[0050] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is illustrated, which may be Figure 1 2. The 5G access node 206 may include an access node controller (ANC) 202. The 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 be terminated at the ANC 202. The backhaul interface to the adjacent next generation access node (NG-AN) 210 may be terminated at the ANC 202. The ANC 202 may include one or more transmit receive points (TRPs) 208 (e.g., cellular cells, BSs, gNBs, etc.).

[0051] The TRP 208 may be a distributed unit (DU). The TRP 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 AND deployments, the TRP 208 may be connected to more than one ANC. Each of the TRPs 208 may include one or more antenna ports. The TRP 208 may be configured to serve traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0052] The logical architecture of the distributed RAN 200 can support various backhaul and fronthaul solutions. This support can occur via and across different deployment types. For example, the logical architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter).

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

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

[0055] Logical functions may be dynamically distributed in the logical architecture of the distributed RAN 200. Figure 5 Described in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU (e.g., TRP 208) or the CU (e.g., ANC 202).

[0056] Figure 3 An example physical architecture of a distributed radio access network (RAN) 300 is illustrated in accordance with aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. The 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.

[0057] 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 a distributed deployment. The C-RU 304 may be close to the edge of the network.

[0058] The DU 306 may host one or more TRPs (edge ​​node (EN), edge unit (EU), radio head (RH), smart radio head (SRH), etc.) The DU may be located at the edge of the network with radio frequency (RF) functionality.

[0059] Figure 4 Explained (such as Figure 1 1 and 120, which may be used to implement aspects of the present disclosure. For example, antenna 452, processors 466, 458, 464, and / or controller / processor 480 of UE 120 may be used to perform Fig.10 Operation 1000 of BS 110, and antenna 434, processor 420, 460, 438 and / or controller / processor 440 of BS 110 may be used to perform Fig.11 Operation 1100.

[0060] At BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller / processor 440. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols (e.g., of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to modulators (MODs) 432a to 432t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a to 432t may be transmitted via antennas 434a to 434t, respectively.

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

[0062] On the uplink, at the UE 120, the transmit processor 464 may receive and process data from a data source 462 (e.g., data for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., control information for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466, if applicable, further processed by demodulators 454a to 454r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signal from the UE 120 may be received by the antenna 434, processed by the modulator 432, detected by the MIMO detector 436, if applicable, and further processed by the receive processor 438 to obtain decoded data and control information sent by the UE 120. Receive processor 438 may provide decoded data to data sink 439 and decoded control information to controller / processor 440 .

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

[0064] Figure 5 Illustrated is a diagram 500 showing an example for implementing a communication protocol stack according to various aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a wireless communication system, such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication 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, these layers of the protocol stack may be implemented as separate software modules, parts of a processor or ASIC, parts of non-co-located devices connected by a communication link, or various combinations thereof. Co-located and non-co-located implementations may be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0065] The first option 505-a illustrates a split implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2ANC 202 in the system) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, while the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may be co-located or non-co-located. The first option 505-a may be useful in a macro cell, a micro cell, or a pico cell deployment.

[0066] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device. 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 can each be implemented by an AN. The second option 505-b can be useful in, for example, a femtocell deployment.

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

[0068] The embodiments discussed herein may include various spacing and timing arrangements. For example, in LTE, the basic transmission time interval (TTI) or packet duration is a 1ms subframe. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16...time slots), depending on the subcarrier spacing. NR RBs are 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, for example, 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

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

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

[0071] In NR, a synchronization signal (SS) block (SSB) is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be in a fixed time slot position (such as Figure 6 PBCH is transmitted in the symbols 0-3 shown in . PSS and SSS can be used by UE for cell search and acquisition. PSS can provide half-frame timing, while SS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set periodicity, system frame number, etc.

[0072] Further system information, such as Remaining Minimum System Information (RMSI), System Information Block (SIB), Other System Information (OSI), may be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

[0073] like Figure 7 As shown in , SS blocks can be organized into SS burst sets to support beam sweeping. As shown, each SSB in a burst set can be transmitted using a different beam, which can help the UE quickly acquire both transmit (Tx) and receive (Rx) beams (especially for mmW applications). The physical cell identity (PCI) can still be decoded from the PSS and SSS of the SSB.

[0074] Certain deployment scenarios may include one or two NR deployment options. An option may be configured for non-standalone (NSA) and / or standalone (SA) options. Standalone cells may need to broadcast both SSBs and remaining minimum system information (RMSI) (e.g., using SIB1 and SIB2). Non-standalone cells may only need to broadcast SSBs without broadcasting RMSI. In a single carrier of NR, multiple SSBs may be sent at different frequencies and may include different types of SSBs.

[0075] Control Resource Set (CORESET)

[0076] A control resource set (CORESET) for an OFDMA system (e.g., a communication system that transmits a PDCCH using an OFDMA waveform) may include one or more control resource (e.g., time and frequency resource) sets configured within the system bandwidth for communicating the PDCCH. Within each CORESET, one or more search spaces (e.g., a common search space (CSS), a UE-specific search space (USS), etc.) may be defined for a given UE. A search space is generally an area or portion where a communication device (e.g., a UE) may search for control information.

[0077] According to various aspects of the present disclosure, a CORESET is a time-frequency domain resource set defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) frequency modulations in one symbol period (e.g., the symbol period of a time slot), wherein one frequency modulation 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). A CCE set may be used to transmit a new radio PDCCH (NR-PDCCH), wherein different numbers of CCEs in a set are used to transmit NR-PDCCH using different aggregation levels. Multiple CCE sets may be defined as search spaces for UEs, and thereby a Node B or other base station may transmit the NR-PDCCH to the UE by transmitting the NR-PDCCH in a CCE set of decoding candidates defined within the search space for the UE, and the UE may receive the NR-PDCCH by searching in the search space for the UE and decoding the NR-PDCCH transmitted by the Node B.

[0078] The operating characteristics of a Node B or other base station in an NR communication system may depend on the frequency range (FR) in which the system operates. The frequency range may include one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band), and the communication system (e.g., one or more Node Bs and UEs) may operate in one or more operating bands. The frequency range and operating bands are described in more detail in "Base station (BS) radio transmission and reception" TS38.104 (Release 15), which is available from the 3GPP website.

[0079] As described above, a CORESET is a collection of time domain and frequency domain resources. A CORESET can be configured to communicate a PDCCH within the system bandwidth. The UE can determine the CORESET and monitor the CORESET to find a control channel. During initial access, the UE can identify the initial CORESET (CORESET#0) configuration from a field (e.g., pdcchConfigSIB1) in a master information block (MIB). The initial CORESET can then be used to configure the UE (e.g., via dedicated (UE-specific) signaling with other CORESETs and / or bandwidth portions). When the UE detects a control channel in a CORESET, the UE attempts to decode the control channel, and the UE communicates with the transmitting BS (e.g., transmitting cell) based on the control data provided in the control channel (e.g., transmitted via the CORESET).

[0080] According to various aspects of the present disclosure, when a UE is connected to a cell (or BS), the UE may receive a master information block (MIB). The MIB may be in a synchronization signal and physical broadcast channel (SS / PBCH) block on a sync raster (e.g., in a PBCH of a SS / PBCH block). In some scenarios, the sync raster may correspond to an SSB. Based on the frequency of the sync raster, the UE may determine an operating frequency band of the cell. Based on the operating frequency band of the cell, the UE may determine a minimum channel bandwidth and a subcarrier spacing (SCS) of the channel. The UE may then determine an index based on the MIB (e.g., four bits in the MIB conveying an index in the range 0-15).

[0081] Given this index, the UE can look up or locate the CORESET configuration (this initial CORESET configured via the MIB is generally referred to as CORESET#0). This can be done according to 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 a table.

[0082] Alternatively or additionally, the UE may select a search space CORESET configuration table from several tables of CORESET configurations. These configurations may be based on the minimum channel bandwidth and the SCS. The UE may then look up the CORESET configuration (e.g., Type 0 - PDCCH search space CORESET configuration) from the selected table based on the index. After determining the CORESET configuration (e.g., from a single table or a selected table), the UE may then determine the CORESET to monitor based on the location (in time and frequency) of the SS / PBCH blocks and the CORESET configuration (as mentioned above).

[0083] Figure 8 An exemplary transmission resource mapping 800 according to aspects of the present disclosure is shown. In the exemplary mapping, a BS (e.g., Figure 1 The BS 110a) shown in FIG. transmits a SS / PBCH block 802. The SS / PBCH block includes a MIB that conveys an index to a table that relates the time and frequency resources of a CORESET 804 to the time and frequency resources of the SS / PBCH block.

[0084] The BS may also transmit control signaling. In some scenarios, the BS may also send control signaling to the UE (e.g., Figure 1 806). The BS then transmits the PDSCH to the UE. The UE may receive the MIB in the SS / PBCH block, determine an index, look up the CORESET configuration based on the index, and determine the CORESET from the CORESET configuration and the SS / PBCH block. The UE may then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH allocated by the PDCCH.

[0085] Different CORESET configurations may have different parameters defining the corresponding CORESET. For example, each configuration may indicate the number of resource blocks (e.g., 24, 48, or 96), the number of symbols (e.g., 1-3), and an offset indicating a location on frequency (e.g., 0-38 RBs).

[0086] QCL port and TCI status relationship

[0087] In many cases, it is important for the UE to know which assumptions it can make about the channels corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode the transmitted signal (e.g., PDCCH or PDSCH). It is also important for the UE to be able to report relevant channel state information (CSI) to the BS (gNB) for scheduling, link adaptation, and / or beam management purposes. In NR, the concepts of Quasi Co-location (QCL) and Transmission Configuration Indicator (TCI) states are used to convey information about these assumptions.

[0088] The QCL assumption is generally defined in the form of channel properties. According to 3GPP TS 38.214, "two antenna ports are said to be quasi-colocated if the properties of the channel over which the codewords on one antenna port are transmitted can be inferred from the channel over which the codewords on the other antenna port are transmitted." Different reference signals (RS) can be considered to be quasi-colocated (QCL) if the receiver (e.g., UE) can apply the channel properties determined by detecting the first reference signal to help detect the second reference signal. The TCI state generally includes configurations such as QCL relationships (e.g., between DL RS and PDSCH DMRS ports in a CSI-RS set).

[0089] In some cases, the UE may be configured with up to M TCI states. The configuration of the M TCI states may be performed via higher layer signaling, while the UE may be signaled to decode the PDSCH based on a detected PDCCH with a DCI indicating one of the TCI states. Each configured TCI state may include one RS set TCI-RS-SetConfig indicating different QCL assumptions between certain source and target signals.

[0090] Fig. 9 An example of association of a DL reference signal and a corresponding QCL type that may be indicated by TCI-RS-SetConfig is illustrated.

[0091] exist Fig. 9 In the example of , a source reference signal (RS) is indicated in the top block and is associated with a target signal indicated in the bottom block. In this context, a target signal generally refers to a signal whose channel properties can be inferred by measuring those channel properties for the associated source signal. As mentioned above, the UE can 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. The target RS does not necessarily need to be the DMRS of the PDSCH, but it can be any other RS: PUSCH DMRS, CSIRS, TRS and SRS.

[0092] As explained, each TCI-RS-SetConfig contains parameters. For example, these parameters can configure the quasi-co-location relationship(s) between the reference signals in the RS set and the DM-RS port group of the PDSCH. The RS set contains references to one or two DLRS and the associated quasi-co-location type (QCL type) of each DL RS configured by the higher layer parameter QCL type.

[0093] like Fig. 9 As illustrated, for the case of two DL RSs, the QCL type may be arranged in various ways. For example, the QCL type may be different, whether referencing the same DL RS or different DL RSs. In the illustrative example, SSB is associated with a type C QCL for P-TRS, while a CSI-RS for beam management (CSIRS-BM) is associated with a type D QCL.

[0094] In some scenarios, the QCL information and / or type may depend on or be a function of other information. For example, the quasi co-location (QCL) type indicated to the UE may be based on a higher layer parameter QCL type and may be one of the following types or a combination thereof:

[0095] QCL type A: {Doppler shift, Doppler spread, average delay, delay spread};

[0096] QCL type B: {Doppler shift, Doppler spread},

[0097] QCL Type C: {average delay, Doppler shift}, and

[0098] QCL type D: {spatial Rx parameters},

[0099] The spatial QCL assumption (QCL type D) may be used to help the UE select an analog Rx beam (eg, during a beam management procedure). For example, the SSB resource indicator may indicate that the same beam used for a previous reference signal should be used for subsequent transmissions.

[0100] The initial CORESET in the NR (e.g., CORESET ID 0 or simply CORESET#0) may be identified during initial access by the UE (e.g., via a field in the MIB). A control resource set information element (CORESET IE) sent via radio resource control (RRC) signaling may convey information about the CORESET configured for the UE. The CORESET IE generally includes the CORESET ID, an indication of the frequency domain resources (e.g., number of RBs) assigned to the CORESET, the continuous time duration of the CORESET in number of symbols, and a transmission configuration indicator (TCI) state.

[0101] As mentioned above, the TCI state subset provides a quasi co-location (QCL) relationship between the DL RS(s) and PDCCH demodulation RS (DMRS) ports in a RS set (e.g., TCI set). The specific TCI state for a given UE (e.g., for unicast PDCCH) can be communicated to the UE by a media access control (MAC) control element (MAC-CE). The specific TCI state is generally selected from a set of TCI states communicated by a CORESET IE, where the initial CORESET (CORESET#0) is generally configured via the MIB.

[0102] Search space information may also be provided via RRC signaling. For example, the Search Space 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 Search Space IE identifies the search space configured for the CORESET by the Search Space ID. In one aspect, the Search Space ID associated with CORESET#0 is Search Space ID#0. The search space is generally configured via PBCH (MIB).

[0103] Example Signaling for Enabling Uplink (UL) Transmission Configuration Indicator (TCI) State

[0104] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for enabling UL TCI states. UL TCI states may be used for UL beam updates and path loss (PL) reference signal (RS) updates, as discussed in further detail herein.

[0105] The Transmission Configuration Indicator (TCI) framework may include a configuration for a single-panel UE with an active beam configured for transmission and reception of a directional signal or channel. Other configurations may include a multi-panel framework for transmission and reception of a directional signal or channel. The multi-panel framework may enable uplink (UL) TCI states for UL beam and PL RS updates, which may be applied to various uplink RS or channels (including physical uplink control channel (PUCCH), sounding reference signal (SRS), physical random access channel (PRACH), and physical uplink shared channel (PUSCH)). However, not all UEs support such a framework.

[0106] In some aspects, the TCI framework can be configured as a unified uplink and downlink TCI framework. In a unified framework, each UL TCI state may include or otherwise be associated with a source reference signal that indicates an uplink transmission beam for a target uplink reference signal or channel. The source reference signal may include, for example, an SRS, SSB, CSI-RS, or other appropriate reference signals. The target uplink resource may be a reference signal (such as an SRS) or various uplink channels (such as PUCCH, PRACH, or PUSCH). Table 1 below illustrates examples of various uplink TCI states, source RS, target uplink RS, and associated QCL types:

[0107]

[0108] Table 1: Example uplink TCI states

[0109] The UL TCI state and the reference signal associated with the UL TCI state may be used to identify updates to various parameters for transmitting UL reference signals or channels. For example, information derived from the UL TCI state and the reference signal associated therewith may be used, for example, for beam updates (e.g., switching from a first beam to a second beam for transmission of uplink signaling to a network entity) and for PL RS updates. The PL RS may be a downlink signal transmitted from a network entity (e.g., a gB node) to a UE and may be used by the UE to determine power control parameters for uplink transmissions. The DCI that schedules uplink transmissions may include an identification of the UL TCI state, and the PL RS may be associated with the UL TCI state. The association of the PL RS with the UL TCI state may indicate to the UE the associated power control parameters for uplink transmissions scheduled by the DCI. The TCI state may also include spatial information (such as an identification of a beam) for the UE to use for uplink transmissions scheduled by the DCI.

[0110] Support for using UL TCI states for UL beam and PL RS updates may be optional and may be implemented on a per-manufacturer or per-device basis. Because not all UEs support using UL TCI states for UL beam and PL RS updates, it may be necessary to inform the network entity whether the UE supports UL TCI states for UL beam and PL RS updates in order to enable using UL TCI states for UL beam and PL RS updates.

[0111] Fig.10 1000 for wireless communications by a UE according to some aspects of the present disclosure. For example, operations 400 may be performed by Figure 1The UE 120 performs to enable use of the UL TCI state for UL beam update and / or UL PL RS update.

[0112] Operations 1000 begin at block 1002, where the UE signals to a network entity an indication that the UE supports UL TCI states with one or more quasi co-location (QCL) types for one or more reference signals to be applied to uplink transmissions.

[0113] At block 1004, the UE receives a UL TCI after sending the indication.

[0114] The UE sends the uplink transmission in accordance with the UL TCI at 1006. Transmitting the uplink transmission in accordance with the UL TCI may include, for example, transmitting the uplink transmission based on a beam update or an update to a power control parameter derived from a PL RS associated with the UL TCI.

[0115] Fig.11 1 illustrates example operations 1100 for wireless communications by a network entity in accordance with some aspects of the present disclosure. For example, operations 400 may be performed by Figure 1 The base station 110 performs to enable the UL TCI state for UL beam update and UL PL RS update.

[0116] Operations 1100 begin at block 1102, where a network entity receives signaling from a user equipment (UE) indicating that the UE supports UL TCI states indicating one or more quasi co-location (QCL) types for one or more reference signals to be applied to uplink transmissions.

[0117] At block 1104, the network entity sends a UL TCI after receiving the indication.

[0118] At block 1106, the network entity receives a UL transmission in accordance with the UL TCI. For example, the network entity may receive the UL transmission on a beam associated with or otherwise indicated by the UL TCI transmitted to the UE at block 1104. In some aspects, the network entity may receive the UL transmission at a received power associated with a power control update derived from a PL RS associated with the UL TCI.

[0119] In some embodiments, the UE may report various capabilities for supporting UL TCI states for beam updating and / or PL RS updating. In one example, the UE may report a single capability. The single capability may indicate the UE capability for supporting UL TCI states for UL beam updating and PL RS updating for all target UL RSs and / or channels.

[0120] In another example, the UE may report a capability for supporting a UL TCI state for UL beam update separately from a capability for supporting a UL TCI state for PL RS update. The UE may report a first capability for supporting a UL TCI state for UL beam update for a target UL RS and channel. The UE may also report a second capability for supporting a UL TCI state for UL PL RS update for a target UL RS and channel. The first and second capabilities may be reported with respect to a specific UL RS and / or channel, or may apply to all target UL RS and / or channels.

[0121] In yet another example, the UE may report individual capabilities on a per-target UL-RS and / or per-target channel basis. For each target UL RS or target channel, the UE may report the capability to support UL TCI states for UL beam updates and / or UL PL RS updates. By doing so, the UE may therefore support the use of TCI states for UL beam updates and / or UL PL RS updates on certain UL RSs or uplink channels, but may not support the use of TCI states for UL beam updates and / or UL PL RS updates on other UL RSs or uplink channels.

[0122] In some embodiments, a network entity may use a flag or other special value to indicate that the use of the UL TCI state for UL beam update and / or UL PL RS update is enabled for a UE that supports the use of the UL TCI state for UL beam update and / or UL PL RS update. The indication may be based on, for example, the configuration of an RRC parameter. That is, if the RRC parameter is configured with a first value or a set of values, the use of the UL TCI state for UL beam update and / or UL PL RS update may be enabled, and if the RRC parameter is configured with a second value or a set of values, the use of the UL TCI state for UL beam update and / or UL PL RS update may be disabled. After receiving the enabling indication from the network entity, the UE may be ready to receive a corresponding new DCI format for the UL TCI state for UL beam update and / or PL RS update of the target UL RS and / or channel. The target UL RS and / or channel may generally include those UL RS and / or channels that the UE has reported support for, as discussed above.

[0123] Fig.1212 is a call flow diagram 1200 illustrating example messages that may be exchanged between a UE 1202 and a network entity 1204 (e.g., a gNode B) to signal support for using a UL TCI state for UL beam updating and / or UL PL RS updating in accordance with certain aspects of the present disclosure. As illustrated, the UE 1202 may transmit a UL TCI state support message 1210 to the network entity 1204. As discussed above, the UL TCI state support message may be one or more messages indicating the UE's support for using a UL TCI state for UL beam updating and / or UL PL RS updating, whether the support is indicated on a per-target UL-RS and / or per-target channel basis for all target UL RSs and / or channels. For example, the UL TCI state support message 1210 may include a single capability indicating the UE's support for using a UL TCI state for UL beam updating and PL RS updating for all target UL RSs and / or target UL channels. In another example, the UL TCI state support message 1210 may include two capabilities. The first capability may indicate the UE's support for using the UL TCI state for UL beam update of all target UL RSs and / or target UL channels, and the second capability may indicate the UE's support for using the UL TCI state for UL PL RS update of all target UL RSs and / or target UL channels. In yet another example, the UL TCI state support message 1210 may include individual capability indications for UL beam update and / or UL PL RS update based on UL TCI state on a per-target UL-RS basis and / or on a per-target channel basis.

[0124] After receiving the UL TCI state support message 1210 indicating that the UE 1202 supports the use of the UL TCI state to update one or both of the UL beam direction or the UL PL RS, the network entity 1204 may transmit the UL TCI 1212 to the UE 1202. For example, the UL TCI may be carried in a downlink control information (DCI) message that schedules uplink transmissions for the UE. In some aspects, the network entity may indicate (alone or in conjunction with the UL TCI) that UL beam and / or PL RS updating based on TCI state is activated, as discussed above.

[0125] Upon receiving the UL TCI 1212, the UE 1202 performs one or more updates at block 1214. The one or more updates may include, for example, a beam update (e.g., a beam switch from a first transmit beam to a second transmit beam), a power control parameter update, etc. based on the UL TCI. For example, the beam update and the power control parameter update may be performed based on a source reference signal associated with the UL TCI 1212. Subsequently, the UE 1202 performs an uplink transmission 1216 based on the UL TCI 1212. In general, when performing the uplink transmission 1216, the UE 1202 applies the beam and / or power control parameters updated at block 1214.

[0126] Fig.13 The description may include a method configured to perform operations for the techniques disclosed herein (such as Fig.10 1300 includes a communication device 1300 including various components (e.g., corresponding to means-plus-function components) of the operations illustrated in . The communication 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 (such as the various signals described herein) for the communication device 1300 via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and / or to be transmitted by the communication device 1300.

[0127] The processing system 1302 includes a processor 1304 coupled to a computer readable medium / memory 1312 via a bus 1306. In some aspects, the computer readable medium / memory 1312 is configured to store programs that, when executed by the processor 1304, cause the processor 1304 to execute Fig.10Instructions (e.g., computer executable code) for performing the operations illustrated in the or other operations discussed herein for signaling various techniques for supporting UE capabilities for supporting UL beam and / or PL RS based on UL TCI state updates. In certain aspects, the computer-readable medium / memory 1312 stores code 1314 for signaling to a network entity an indication that the UE supports an uplink transmission configuration indicator (TCI) state with one or more quasi co-location (QCL) types for one or more reference signals (RSs) to be applied to an uplink transmission; code 1316 for receiving a UL TCI after sending the indication; and code 1318 for sending the uplink transmission in accordance with the uplink TCI. In certain aspects, the processor 1304 has a circuit system configured to implement the code stored in the computer-readable medium / memory 1312. Processor 1304 includes a circuit system 1320 for signaling to a network entity an indication that the UE supports an uplink transmission configuration indicator (TCI) state having one or more quasi-co-location (QCL) types for one or more reference signals (RS) to be applied to an uplink transmission; a circuit system 1322 for receiving a UL TCI after sending the indication; and a circuit system 1324 for sending the uplink transmission based on the uplink TCI.

[0128] Fig.14 The description may include a method configured to perform operations for the techniques disclosed herein (such as Fig.11 1400 includes a communication device 1400 including various components (e.g., corresponding to means-plus-function components) of the operations illustrated in . The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or a receiver). The transceiver 1408 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1400 via an antenna 1410. The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received and / or to be transmitted by the communication device 1400.

[0129] The processing system 1402 includes a processor 1404 coupled to a computer readable medium / memory 1412 via a bus 1406. In some aspects, the computer readable medium / memory 1412 is configured to store programs that, when executed by the processor 1404, cause the processor 1404 to execute Fig.11Instructions (e.g., computer executable code) for performing the operations illustrated in the or other operations discussed herein for signaling various techniques for supporting UE capabilities for supporting UL beam and / or PL RS based on UL TCI state updates. In certain aspects, the computer-readable medium / memory 1412 stores code 1414 for receiving signaling from a user equipment (UE) indicating that the UE supports uplink transmission configuration indicator (TCI) states with one or more quasi co-location (QCL) types for one or more reference signals (RS) to be applied to uplink transmissions; code 1416 for sending a UL TCI after receiving the indication; and code 1418 for receiving the uplink transmission according to the uplink TCI. In certain aspects, the processor 1404 has a circuit system configured to implement the code stored in the computer-readable medium / memory 1412. Processor 1404 includes a circuit system 1420 for receiving signaling from a user equipment (UE) indicating that the UE supports an uplink transmission configuration indicator (TCI) state having one or more quasi-co-location (QCL) types for one or more reference signals (RS) to be applied to an uplink transmission; a circuit system 1422 for sending a UL TCI after receiving the indication; and a circuit system 1424 for receiving the uplink transmission based on the uplink TCI.

[0130] Example Embodiments

[0131] Embodiment 1: A method for wireless communication by a user equipment (UE), comprising: signaling to a network entity an indication of an uplink transmission configuration indicator (TCI) state that the UE supports one or more quasi-co-location (QCL) types for one or more reference signals (RS) to be applied to uplink transmission; receiving a UL TCI after sending the indication; and sending the uplink transmission according to the uplink TCI.

[0132] Embodiment 2: The method of embodiment 1, wherein the QCL type includes a QCL type for one or more RSs for estimating uplink time and frequency offset.

[0133] Embodiment 3: A method as in Embodiment 1 or 2, wherein the uplink transmission includes at least one of a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH) or a physical uplink shared channel (PUSCH).

[0134] Embodiment 4: A method as in any one of embodiments 1 to 3, wherein the signaling indicates that the UE supports a UL TCI state for uplink beam updating.

[0135] Embodiment 5: The method as in any one of embodiments 1 to 4, wherein the signaling indicates that the UE supports a UL TCI state for path loss reference signal (PL RS) update.

[0136] Embodiment 6: The method of any one of embodiments 1 to 4, wherein the signaling includes a single indication of the capability of the UL TCI state for supporting both UL beam updates and path loss reference signal (PL RS) updates for a target UL RS or channel.

[0137] Embodiment 7: A method as in any one of embodiments 1 to 4, wherein the signaling includes an indication of a first capability for supporting a UL TCI state for UL beam update and a second capability for supporting a path loss reference signal (PLRS) update for a target UL RS or channel.

[0138] Embodiment 8: A method as in any one of Embodiments 1 to 4, wherein the signaling includes: an indication of individual capabilities of the UL TCI state for supporting UL beam updates for each target UL RS or channel; and an indication of individual capabilities of the UL TCI state for supporting path loss reference signal (PL RS) updates for each target UL RS or channel.

[0139] Embodiment 9: The method of any one of embodiments 1 to 8 further comprises receiving signaling from a network entity indicating that a UL TCI state has been enabled for the UE based on the indicated UE support.

[0140] Embodiment 10: A method as in Embodiment 9, wherein the signaling is via configuration of radio resource control (RRC) parameters.

[0141] Embodiment 11: The method of embodiment 9 or 10, wherein the UE does not process the UL TCI until the signaling indicates that the UL TCI state has been enabled for the UE.

[0142] Embodiment 12: A method for wireless communication by a network entity, comprising: receiving signaling from a user equipment (UE) indicating that the UE supports an uplink transmission configuration indicator (TCI) state having one or more quasi co-location (QCL) types for one or more reference signals (RS) to be applied to uplink transmission; sending a UL TCI after receiving the indication; and receiving the uplink transmission based on the uplink TCI.

[0143] Embodiment 13: The method of Embodiment 12, wherein the QCL type comprises a QCL type for one or more RSs for estimating uplink time and frequency offset.

[0144] Embodiment 14: A method as in Embodiment 12 or 13, wherein the uplink transmission includes at least one of a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH) or a physical uplink shared channel (PUSCH).

[0145] Embodiment 15: A method as in any one of Embodiments 12 to 14, wherein the signaling indicates that the UE supports a UL TCI state for uplink beam updating.

[0146] Embodiment 16: The method as in any one of embodiments 12 to 15, wherein the signaling indicates that the UE supports a UL TCI state for path loss reference signal (PL RS) update.

[0147] Embodiment 17: The method of any one of Embodiments 12 to 15, wherein the signaling includes a single indication of the capability of the UL TCI state for supporting both UL beam updates and path loss reference signal (PL RS) updates for a target UL RS or channel.

[0148] Embodiment 18: A method as in any one of Embodiments 12 to 15, wherein the signaling includes an indication of a first capability for supporting a UL TCI state for UL beam updates and a second capability for supporting a UL TCI state for a path loss reference signal (PL RS) update for a target UL RS or channel.

[0149] Embodiment 19: A method as in any one of Embodiments 12 to 15, wherein the signaling includes: an indication of individual capabilities of the UL TCI state for supporting UL beam updates for each target UL RS or channel; and an indication of individual capabilities of the UL TCI state for supporting path loss reference signal (PL RS) updates for each target UL RS or channel.

[0150] Embodiment 20: The method of any one of embodiments 12 to 19, further comprising sending signaling to the UE indicating that a UL TCI state has been enabled for the UE based on the indicated UE support.

[0151] Embodiment 21: A method as in Embodiment 20, wherein the signaling is via configuration of radio resource control (RRC) parameters.

[0152] Embodiment 22: The method of embodiment 20 or 21, wherein the network entity assumes that the UE does not process the UL TCI until the signaling indicates that the UL TCI state has been enabled for the UE.

[0153] Additional considerations

[0154] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other 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 can be changed without departing from the scope of the claims.

[0155] 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, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0156] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching 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.

[0157] 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 easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to those of ordinary skill in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. Any element of the claim should not be interpreted under the provisions of 35 U.S.C. § 112 (f), unless the element is explicitly stated using the phrase "device for..." or in the case of a method claim, the element is stated using the phrase "step for...".

[0158] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0159] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed 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. The processor may also be implemented as a combination of computing devices, for example, 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.

[0160] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., 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 user terminal 120 (see Figure 1 ), a user interface (e.g., a 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 will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0161] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include 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 media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0162] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a 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 describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0163] Likewise, 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 technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is 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 Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0164] Thus, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded) thereon, which instructions can be executed by one or more processors to perform the operations described herein. For example, for performing the operations described herein and in Figure 9-10 Instructions for the operations explained in .

[0165] In addition, it should be appreciated that modules and / or other appropriate means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station where 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, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0166] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment UE, comprising: transmitting to a network entity a UE capability indicating that the UE supports an uplink (UL) transmission configuration indicator (TCI) state with one or more quasi co-located (QCL) types for one or more reference signals (RS) to be applied for uplink transmission; receiving an indication of a UL TCI status after transmitting the UE capabilities; and The uplink transmission is sent according to the indicated UL TCI state, wherein sending the uplink transmission according to the indicated UL TCI state includes sending the uplink transmission based on a beam update associated with the indicated UL TCI state.

2. The method of claim 1, wherein sending the uplink transmission according to the indicated UL TCI state alternatively comprises sending the uplink transmission based on an update of a power control parameter derived from a path loss reference signal (PL RS).

3. The method of claim 1, wherein the QCL type comprises a QCL type for one or more RSs for estimating uplink time and frequency offset.

4. The method of claim 1, wherein the uplink transmission comprises at least one of a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH), or a physical uplink shared channel (PUSCH).

5. The method of claim 1, wherein the UE capability indicates that the UE supports a UL TCI state for uplink beam updating.

6. The method of claim 1, wherein the UE capability indicates that the UE supports a UL TCI state for PL RS updating.

7. The method of claim 1, wherein the UE capabilities include a single indication of a capability for supporting a UL TCI state for at least a UL beam update for a target UL RS or channel.

8. The method of claim 1, wherein the UE capabilities include an indication of a first capability for supporting a UL TCI state for a UL beam update for a target UL RS or channel.

9. The method of claim 2, wherein the UE capabilities further include an indication of a second capability for supporting a UL TCI state for a PL RS update of a target UL RS or channel.

10. The method of claim 1, wherein the UE capabilities include: An indication of the individual capability of the UL TCI state to support UL beam updates for each target UL RS or channel.

11. The method of claim 2, wherein the UE capabilities further include an indication of individual capabilities for supporting UL TCI states for PL RS updating per target UL RS or channel.

12. The method of claim 1, further comprising receiving signaling from the network entity indicating that a UL TCI state has been activated for the UE based on the indicated UE support.

13. The method of claim 12, wherein the signaling is based on configuration of Radio Resource Control (RRC) parameters.

14. The method of claim 12, wherein the UE does not process the UL TCI until the signaling indicates that a UL TCI state has been activated for the UE.

15. A method for wireless communication by a network entity, comprising: receiving a UE capability indicating that the user equipment UE supports an uplink transmission UL configuration indicator TCI state with one or more quasi co-located QCL types for one or more reference signals RS to be applied for uplink transmission; sending an indication of UL TCI status after receiving the UE capabilities; and The uplink transmission is received according to the indicated UL TCI state, wherein receiving the uplink transmission according to the indicated UL TCI state includes receiving the uplink transmission based on a beam update associated with the indicated UL TCI state.

16. The method of claim 15, wherein receiving the uplink transmission according to the indicated UL TCI state alternatively comprises receiving the uplink transmission based on an update of a power control parameter derived from a path loss reference signal (PL RS).

17. The method of claim 15, wherein the QCL type comprises a QCL type for one or more RSs for estimating uplink time and frequency offset.

18. The method of claim 15, wherein the uplink transmission comprises at least one of a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH), or a physical uplink shared channel (PUSCH).

19. The method of claim 15, wherein the UE capability indicates that the UE supports a UL TCI state for uplink beam updating.

20. The method of claim 16, wherein the UE capability indicates that the UE supports a UL TCI state for PL RS updating.

21. The method of claim 15, wherein the UE capabilities include a single indication of a capability for supporting a UL TCI state for at least a UL beam update for a target UL RS or channel.

22. The method of claim 15, wherein the UE capabilities include an indication of a first capability for supporting a UL TCI state for a UL beam update for a target UL RS or channel.

23. The method of claim 16, wherein the UE capabilities further include an indication of a second capability for supporting a UL TCI state for a PL RS update of a target UL RS or channel.

24. The method of claim 15, wherein the UE capabilities include: An indication of the individual capability of the UL TCI state to support UL beam updates for each target UL RS or channel.

25. The method of claim 16, wherein the UE capabilities further include an indication of individual capabilities for supporting UL TCI states for PL RS updating per target UL RS or channel.

26. The method of claim 15, further comprising sending signaling indicating that a UL TCI state has been activated for the UE based on the indicated UE support.

27. The method of claim 26, wherein the signaling is based on configuration of Radio Resource Control (RRC) parameters.

28. The method of claim 26, wherein the network entity assumes that the UE does not process UL TCI until the signaling indicates that a UL TCI state has been activated for the UE.

29. An apparatus for wireless communication by a user equipment UE, comprising: a memory having executable instructions stored thereon; as well as one or more processors configured to execute the executable instructions so that the apparatus: transmitting to a network entity a UE capability indicating that the UE supports an uplink transmission configuration indicator TCI state with one or more quasi co-located QCL types for one or more reference signals, RS, to be applied for uplink transmission; receiving an indication of a UL TCI status after transmitting the UE capabilities; as well as The uplink transmission is sent according to the indicated UL TCI state, wherein, in order to send the uplink transmission according to the indicated UL TCI state, the one or more processors are configured to cause the device to send the uplink transmission based on a beam update associated with the indicated UL TCI state.

30. The apparatus of claim 29, wherein: To send the uplink transmission in accordance with the indicated UL TCI state, the one or more processors are alternatively configured to cause the apparatus to send the uplink transmission based on an update of a power control parameter derived from a path loss reference signal, PL RS.

31. The apparatus of claim 29, wherein the QCL type comprises a QCL type for one or more RSs for estimating uplink time and frequency offset.

32. The apparatus of claim 29, wherein the uplink transmission comprises at least one of a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH), or a physical uplink shared channel (PUSCH).

33. The apparatus of claim 29, wherein the UE capability indicates that the UE supports a UL TCI state for uplink beam updating.

34. The apparatus of claim 30, wherein the UE capability indicates that the UE supports a UL TCI state for PL RS updating.

35. The apparatus of claim 29, wherein the UE capabilities include a single indication of a capability for supporting a UL TCI state for at least a UL beam update for a target UL RS or channel.

36. The apparatus of claim 29, wherein the UE capabilities include an indication of a first capability for supporting a UL TCI state for a UL beam update for a target UL RS or channel.

37. The apparatus of claim 30, wherein the UE capabilities further include an indication of a second capability for supporting a UL TCI state for a PL RS update of a target UL RS or channel.

38. The apparatus of claim 29, wherein the UE capabilities include: An indication of the individual capability of the UL TCI state to support UL beam updates for each target UL RS or channel.

39. The apparatus of claim 30, wherein the UE capabilities further include an indication of individual capabilities for supporting UL TCI states for PL RS updates per target UL RS or channel.

40. The apparatus of claim 29, further comprising receiving signaling from the network entity indicating that a UL TCI state has been activated for the UE based on the indicated UE support.

41. The apparatus of claim 40, wherein the signaling is based on configuration of Radio Resource Control (RRC) parameters.

42. The apparatus of claim 40, wherein the UE does not process the UL TCI until the signaling indicates that a UL TCI state has been activated for the UE.

43. A device for wireless communication by a user equipment UE, comprising: means for transmitting to a network entity a UE capability indicating that the UE supports an uplink UL transmission configuration indicator TCI state with one or more quasi co-located QCL types for one or more reference signals, RS, to be applied for uplink transmission; means for receiving an indication of a UL TCI status after transmitting the UE capabilities; as well as Means for sending the uplink transmission in accordance with the indicated UL TCI state, wherein the means for sending the uplink transmission in accordance with the indicated UL TCI state comprises means for sending the uplink transmission based on a beam update associated with the indicated UL TCI state.

44. The apparatus of claim 43, wherein the means for sending the uplink transmission in accordance with the indicated UL TCI state comprises means for sending the uplink transmission based on an update of a power control parameter derived from a path loss reference signal (PL RS).

Images