UL Power Control (ULPC) Indication By Associating Uplink Power Control (ULPC) Configuration And Transmission Configuration Indicator (TCI)

By associating transmission configuration indicators and uplink power control configurations in wireless communication systems, the problem of inefficiency of uplink channels in 5G NR technology is solved, and more efficient channel management and performance improvement is achieved.

CN119012327APending Publication Date: 2024-11-22QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411427915.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2020-04-17
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing 5G NR technology has inefficient problems in uplink power control and transmission configuration indicator management, resulting in low channel utilization and affecting the performance of the communication system.

Method used

By determining the association between the transmission configuration indicator (TCI) and the uplink power control (ULPC) configuration based on the control message in a wireless communication system, control information indicating the transmission configuration indicator for the uplink channel is received, And determine the transmission power based on the associated ULPC configuration to achieve efficient management of the UL channel.

Benefits of technology

It improves the transmission efficiency and channel utilization of uplink channels, enhances the performance of communication systems, and is suitable for multiple access technology and other telecommunications standards.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119012327A_ABST
    Figure CN119012327A_ABST
Patent Text Reader

Abstract

The apparatus determines an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on the control message; receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel; and determining a transmission power for a transmission on an uplink (UL) channel based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to communication systems, and more particularly to uplink power control (ULPC) indication by associating ULPC configuration and a transmission configuration indicator (TCI). Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of these multiple access technologies include 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.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region and even global level. An example of a telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services related to enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable low latency communication (URLLC). Some aspects of 5GNR can be based on the 4G Long Term Evolution (LTE) standard. There is a need to further enhance 5GNR technology. These improvements can also be applied to other multiple access technologies and telecommunication standards using these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is provided below to provide a basic understanding of these aspects. The present invention is not an exhaustive overview of all expected aspects, and is neither intended to identify the key or important elements of all aspects nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description provided later.

[0005] In aspects of the present disclosure, methods, computer-readable media, and apparatus are provided. The apparatus determines an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message; receives control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel; and determines a transmission power for transmission on an uplink (UL) channel based on the uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

[0006] In aspects of the present disclosure, methods, computer-readable media, and apparatus are provided. The apparatus determines that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; determines a transmission configuration indicator (TCI) configured for a downlink (DL) channel; and applies the transmission configuration indicator (TCI) configured for the downlink (DL) channel for transmission in the uplink (UL) channel.

[0007] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of some of the various ways in which the principles of the various aspects can be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A , 2B , 2C and 2D are diagrams showing examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

[0010] Figure 3 is a diagram showing an example of a base station and a user equipment (UE) in an access network.

[0011] Figure 4 is a signal flow diagram according to various aspects of the present disclosure.

[0012] Figure 5 is a diagram illustrating example uplink transmission configuration indicator (UL-TCI) states.

[0013] Figure 6An example UE-specific physical uplink shared channel (PUSCH) medium access control (MAC) control element (MAC-CE) for UL-TCI state activation / deactivation is shown.

[0014] Figure 7 An example UE-specific PUSCH MAC-CE for associating an active UL-TCI state with a UL PC configuration is shown in accordance with various aspects of the present disclosure.

[0015] Figure 8 An example UE-specific PUSCH MAC-CE for associating an active UL-TCI state with a UL PC configuration is shown in accordance with various aspects of the present disclosure.

[0016] Fig. 9 An example UE-specific PUSCH MAC-CE for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure.

[0017] Fig.10 An example UE-specific PUSCH MAC-CE for associating multiple TCI code points with corresponding UL PC configurations is shown in accordance with various aspects of the present disclosure.

[0018] Fig.11 An example UE-specific PUSCH MAC-CE for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure.

[0019] Fig.12 An example UE-specific PUSCH MAC-CE for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure.

[0020] Fig.13 A flow chart of a method of wireless communication.

[0021] Fig.14 A flow chart of a method of wireless communication.

[0022] Fig.15 is a conceptual data flow diagram illustrating the flow of data between different units / components in an example apparatus.

[0023] Fig.16 is a diagram illustrating an example of a hardware implementation of an apparatus using a processing system. DETAILED DESCRIPTION

[0024] The specific embodiments given below in conjunction with the accompanying drawings are intended to be descriptions of various configurations, rather than to represent the only configurations that implement the concepts described herein. For the purpose of providing a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is obvious to those skilled in the art that these design concepts can be implemented without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid blurring these concepts.

[0025] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0026] For example, an element or any part of an element or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language or other names, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0027] Accordingly, in one or more example embodiments, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored on a computer-readable medium or encoded into one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0028] Figure 1 1 is a diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, and an evolved packet core (EPC) 160, as well as another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0029] The base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS), Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5GNR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other over backhaul links 134 (eg, X2 interfaces) directly or indirectly (eg, through EPC 160 or core network 190). Backhaul links 134 may be wired or wireless.

[0030] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between base station 102 and UE 104 may include: an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0031] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0032] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

[0033] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may utilize NR and may use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' utilizing NR in the unlicensed spectrum may improve coverage and / or increase capacity of the access network.

[0034] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate at millimeter wave (mmW) frequencies and / or near mmW frequencies in the traditional sub-6 GHz spectrum to communicate with the UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band is spread between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW / near mmW radio bands (e.g., 3 GHz–300 GHz) have extremely high path losses and very short distances. The mmW base station 180 may use beamforming 182 with the UE 104 to compensate for this extremely high path loss and short distance.

[0035] Base station 180 may transmit beamformed signals in one or more transmit directions 182' to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may transmit beamformed signals in one or more transmit directions to base station 180. Base station 180 may receive beamformed signals in one or more receive directions from UE 104. Base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0036] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to allocate MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / end) and for collecting eMBMS-related billing information.

[0037] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0038] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a motor vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a medical device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client, or some other appropriate terminology.

[0039] Reference again Figure 1 In certain aspects, the UE 104 may be configured to determine an association between a transmission configuration indicator (TCI) and an uplink power control (ULPC) configuration (198). The UE 104 may determine a transmission power of an uplink (UL) channel in a particular TCI state based on the association between the TCI and the ULPC configuration.

[0040] Figure 2A FIG200 is a diagram showing an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram showing an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, in which for a specific set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to DL or UL; or it can be TDD, in which for a specific set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to both DL and UL. Figure 2A , 2CIn the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with time slot format 28 (mainly DL), where D is DL, U is UL, and X is flexible between DL / UL, and subframe 3 is configured with time slot format 34 (mainly UL). Although subframes 3 and 4 are shown with time slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available time slot formats 0-61. Time slot formats 0 and 1 are DL and UL, respectively. Other time slot formats 2-61 include a mixture of DL, UL and flexible symbols. The UE is configured with the time slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through the received time slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure that is TDD.

[0041] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include microslots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and digital parameters. For slot configuration 0, different digital parameters μ0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe, respectively. For slot configuration 1, different digital parameters 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and digital parameter μ, there are 14 symbols per slot and 2μ slots per subframe. The subcarrier spacing and symbol length / duration are functions of the digital parameters. The subcarrier spacing can be equal to 2 μ *15kKz, where μ is a digital parameter 0 to 5. Thus, a digital parameter μ=0 has a subcarrier spacing of 15kHz and a digital parameter μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figure 2A-2D An example of slot configuration 0 is provided, where each slot has 14 symbols and the numerical parameter μ=0 has 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.

[0042] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0043] like Figure 2A As shown, some of these REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0044] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs), each CCE includes nine RE groups (REGs), and each REG includes four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) can be within symbol 2 of a specific subframe in a frame. The PSS is used by UE104 to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) can be within symbol 4 of a specific subframe in a frame. The SSS is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides multiple RBs in the system bandwidth and a system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent through the PBCH (such as System Information Block (SIB)), and paging messages.

[0045] like Figure 2CAs shown, some of these REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are also possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols in the PUSCH. Depending on whether a short or long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. Although not shown, the UE can send a sounding reference signal (SRS). The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0046] Figure 2D An example of various UL channels within a subframe of a frame is shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), power headroom report (PHR and / or UCI).

[0047] Figure 3is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, while layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with upper layer packet data unit (PDU) transmission, error correction through ARQ, concatenation, segmentation and assembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel prioritization.

[0048] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include: error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying / binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying / M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. Channel estimates can be obtained from reference signals and / or channel condition feedback sent by UE 350. Each spatial stream can then be provided to a different antenna 320 via a respective transmitter 318TX. Each transmitter 318TX can modulate an RF carrier using a respective spatial stream for transmission.

[0049] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, then the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0050] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 160. The controller / processor 359 is also responsible for error detection, which supports HARQ operations using an ACK and / or NACK protocol.

[0051] Similar to the functions described in conjunction with DL transmission performed by the base station 310, the controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper layer PDU transmission, error correction through ARQ, concatenation, segmentation and assembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel priority determination.

[0052] The TX processor 368 may select an appropriate coding and modulation scheme, and to facilitate spatial processing using channel estimates obtained by the channel estimator 358 from a reference signal or feedback sent by the base station 310. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354TX. Each transmitter 354TX may modulate an RF carrier using a corresponding spatial stream for transmission.

[0053] At the base station 310, the UL transmission is processed in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0054] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection, which supports HARQ operations using ACK and / or NACK protocols.

[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 of 198 aspects.

[0056] Figure 4 is a signal flow diagram 400 according to various aspects of the present disclosure. Figure 4 As shown, base station 404 may send control message 406 to UE 402. Control message 406 may indicate an association between one or more uplink (UL) transmission configuration indicator (TCI) states and corresponding one or more UL power control (ULPC) configurations. For example, and as described in detail herein, the ULPC configuration may include information that enables UE 402 to determine the transmission power of the PUSCH. Figure 4 As further shown, the base station 404 can send UL downlink control information (DCI) 408. In some examples, the UL DCI 408 can indicate the TCI state of the UE 402. The UE 402 can determine the UL PC configuration associated with the TCI state based on the control message 406, and can determine the transmit power of the PUSCH based on the UL PC configuration. In some aspects, the UE can determine the UL PC configuration from the TCI field in the DCI 408. The UE 402 can then perform an UL transmission 410 (e.g., data transmission) to the base station 404 based on the transmit power on the PUSCH.

[0057] Figure 5 5 is a diagram 500 illustrating an example UL-TCI (also referred to as UL-TCI state). Figure 5 As shown, each UL-TCI state configuration 502 may include a source reference RS 504, an uplink (UL) RS 506, and a quasi co-location type (qcl-Type) 508. In some examples, the source reference RS 506 may be a sounding reference signal (SRS), a channel state information reference signal (CSI-RS), or a synchronization signal block (SSB). It can be said that the UL-TCI state indicates the beam used for UL transmission on the PUSCH.

[0058] Figure 6 An example UE-specific PUSCH MAC-CE 600 for UL-TCI state activation / deactivation is shown. A base station may configure multiple UL-TCI states to indicate different beams used for UL transmissions (e.g., transmissions on PUSCH). For example, a base station may configure up to 128 UL-TCI states. In some networks, the DCI may not have the capability to indicate 128 different UL-TCI states. However, the DCI may be configured to indicate up to 8 different UL-TCI states from the 128 UL-TCI states.

[0059] For example, the base station may use the UE-specific PUSCH MAC-CE 600 to activate a maximum of 8 UL-TCI states out of 128 UL-TCI states. Figure 6 As shown, the UE-specific PUSCH MAC-CE 600 may include a reserved bit field 602, a serving cell ID field 604, a bandwidth part ID (BWP ID) field 606, and a bitmap, wherein each bit in the bitmap (e.g., bit T0 608, bit T1 610, ..., bit T (N-2)×8+7 612) corresponds to a TCI state. Thus, when a bit in the bitmap (e.g., bit T0 608) is set to '1', the TCI state corresponding to the bit (e.g., the first TCI state) is activated, and when a bit in the bitmap (e.g., bit T1 610) is set to '0', the TCI state corresponding to the bit (e.g., the second TCI state) is deactivated. The bits set to '1' in the bitmap may be assigned to one of eight possible code points in ascending order. For example, if bit T0 608, bit T1 610, and bit T0 608 are set to '1', the TCI state corresponding to the bit (e.g., the first TCI state) is activated, and when a bit in the bitmap (e.g., bit T1 610) is set to '0', the TCI state corresponding to the bit (e.g., the second TCI state) is deactivated. (N-2)×8+7 612 is set to '1' and the remaining bits in the bitmap are set to '0', code point 0 may be set to T0, code point 1 may be set to T1, and code point 2 may be set to T (N-2)×8+7 . For example, the UE may receive a MAC-CE command including a UE-specific PUSCH MAC-CE 600 and may map the activated TCI states to code points (e.g., code point 0 to code point 7). The Transmission Configuration Indication (TCI) field in the DCI may include a code point for indicating the UL-TCI state to the UE.

[0060] If the UE uses the parameter set configuration with index j and the PUSCH power control adjustment state with index l to send PUSCH on the active UL BWP b of carrier f of serving cell c, the UE can determine the PUSCH transmission power in PUSCH transmission opportunity i based on formula (1):

[0061]

[0062] Among them, P PUSCH,b,f,c (i,j,q d ,l) is the PUSCH transmission power, P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c in PUSCH transmission opportunity i, P O_PUSCH,b,f,c (j) is composed of the component P O_NOMINAL_PUSCH,f,c (j) and the component P O_UE_PUSCH,b,f,c (j) is composed of the sum of parameters, where j∈{0,1,...,J-1}, is the bandwidth of PUSCH resource allocation expressed in the number of resource blocks used for PUSCH transmission, α b,f,c, represents the path loss compensation factor, PL b,f,c It can represent the reference signal (RS) index q used by the UE for the active DL BWP. d Determine the downlink path loss estimate in dB, Δ TF,f,c can represent the adjustment related to MCS, f b,f,c 1 may represent a PUSCH power control adjustment state with a closed loop index of 1. oPUSCH,b,f,c It can represent the target signal interference plus noise ratio (SINR) determined by the P0 value. It should be noted that P PUSCH,b,f,c (i,j,q d ,l) is subject to the value of P PUSCH,b,f,c (i,j,q d ,l)(e.g., P PUSCH,b,f,c (i,j,q d ,l) may not exceed P CMAX,f,c (i)).

[0063] In some examples, a UL power control parameter set may be used to control the transmit power of the PUSCH. In one example, the UL power control parameter set may be defined by an information element (IE) referred to herein as SRI-PUSCH-PowerControl. SRI-PUSCH-PowerControl may include any one of four parameters, such as sri-PUSCH-PowerControlId identifying the power control parameter set, sri-PUSCH-PathlossReferenceRS-Id identifying the path loss reference signal, sri-PUSCH-P0-PUSCH-AlphaSetId identifying the P0 value and path loss compensation factor, and sri-PUSCH-ClosedLoopIndex identifying the closed loop index. The UE may use the values ​​set for these four parameters to determine the PUSCH transmission power (e.g., P as defined in formula (1)). PUSCH,b,f,c(i,j,q d ,l)). Table 1 shows an example structure of SRI-PUSCH-PowerControl IE in the Abstract Syntax Notation One (ASN.1) notation format.

[0064] Table 1

[0065]

[0066] UL-TCI Configuration

[0067] The UL-TCI may provide a beam indication to a UE (e.g., UE 402) by referring to a reference signal (RS). In some examples, the RRC layer may configure the UL-TCI for the UE by providing an information element (IE) via RRC signaling. Table 2 shows the structure of a first example UL-TCI-State IE in ASN.1 notation format. In Table 2, the UL-TCI-State IE includes ul-TCI-stat-Id and ul-qcl-Type. The ul-qcl-Type parameter may indicate the configuration of the TCI state associated with the ul-TCI-stat-Id. An example of a UL-QCL-Info IE defining a ul-qcl-Type parameter is provided herein with reference to Table 3.

[0068] Table 2

[0069]

[0070] As shown in Table 3, the UL-QCL-Info IE may include a serving cell identifier (e.g., cellId), a physical cell identifier (PCI) that identifies the cell at the physical layer (e.g., physCellId), a bandwidth part identifier (e.g., bwp-Id), and a reference signal (RS) (e.g., referenceSignal). The reference signal (RS) (e.g., referenceSignal) may indicate a CSI-RS, a synchronization signal block (SSB), or an SRS. The bwp-Id information of the CSI-RS may not be configured and defaults to the active bandwidth part in the serving cell.

[0071] Table 3

[0072]

[0073] As previously described, the RRC layer can configure the UL-TCI for the UE by providing an information element (IE) via RRC signaling. Table 4 shows the structure of the second example UL-TCI-State IE in the ASN.1 notation format. In Table 4, the UL-TCI-State IE includes ul-TCI-stat-Id, a serving cell ID (e.g., servingCellId), and a reference signal (RS) identifier (e.g., refereceRS-ID). The reference signal (RS) identifier may indicate a synchronization signal block (SSB), CSI-RS, or SRS. The bwp-Id information of the CSI-RS may not be configured and defaults to the active bandwidth portion in the serving cell.

[0074] Table 4

[0075]

[0076] In some aspects of the present disclosure, when UL-TCI is not configured by RRC layer signaling, the downlink TCI (DL-TCI) configured for PDSCH for the same BWP may be applied to UL-TCI. For example, UL-TCI may refer to DL-TCI, and the UL-TCI pool is the same as the DL-TCI pool.

[0077] Association between UL-TCI and ULPC based on RRC configuration

[0078] In some aspects of the present disclosure, the RRC layer may configure an association between an uplink transmission control indicator (UL-TCI) and an uplink power control (ULPC) configuration. For example, the ULPC configuration may include a set of UL power control parameters that enable the UE to determine the PUSCH transmission power (e.g., P as defined in formula (1)). PUSCH,b,f,c (i,j,q d ,l)). Therefore, in this example, the UL power control parameter set can be associated with a certain TCI state, and the UE can use the UL power control parameter set to determine the PUSCH transmission power in the TCI state. The UL PC configuration can be indicated by the TCI field in the UL DCI.

[0079] Table 5 shows the structure of the first example UL-TCI-State IE in the ASN.1 notation format. In Table 5, it should be noted that the UL-TCI-State IE defines a direct association between the TCI state (e.g., indicated by ul-TCI-stat-Id) and a UL power control parameter set including any one of pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex. In the UL-TCI-State IE of Table 5, the reference signal (RS) (e.g., indicated by refereceRS-ID) can be a synchronization signal block (SSB), CSI-RS, or SRS. The physCellId (PCI) can be included in the UL-TCI-State IE. Each cell ID can correspond to one or more PCIs. The bwp-Id information of the CSI-RS may not be configured and defaults to the active bandwidth portion in the serving cell.

[0080] Table 5

[0081]

[0082] Table 6 shows the structure of a second example UL-TCI-State IE in the ASN.1 notation format. In Table 6, it should be noted that the UL-TCI-State IE defines an indirect association between the TCI state (e.g., indicated by ul-TCI-stat-Id) and the UL power control parameter set represented by sri-PUSCH-powercontrolID. For example, the association between the TCI state and the UL power control parameter set in Table 6 can be considered indirect because the UL-TCI-State IE includes an identifier (e.g., sri-PUSCH-powercontrolID) referring to the UL power control parameter set. In other words, the UL control parameter set may not be explicitly indicated in the UL-TCI-State IE, but may be obtained separately using an identifier (e.g., sri-PUSCH-powercontrolID). The sri-PUSCH-powercontrolID may define any one of the pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex parameters according to the SRI-PUSCH-PowerControl IE described previously with reference to Table 1. In the UL-TCI-State IE of Table 6, the reference signal (RS) (e.g., indicated by refereceRS-ID) can be a synchronization signal block (SSB), CSI-RS, or SRS. The physCellId (PCI) can be included in the UL-TCI-State IE. Each cell ID can correspond to one or more PCIs. The bwp-Id information of the CSI-RS may not be configured and defaults to the active bandwidth portion in the serving cell.

[0083] Table 6

[0084]

[0085] Table 7 shows the structure of a third example UL-TCI-State IE in the ASN.1 notation format. In Table 7, it should be noted that the UL-TCI-State IE defines an indirect association between the TCI state (e.g., indicated by ul-TCI-stat-Id) and the UL power control parameter set represented by sri-PUSCH-powercontrolID. For example, the association between the TCI state and the UL power control parameter set in Table 7 can be considered indirect because the UL-TCI-State IE includes an identifier (e.g., sri-PUSCH-powercontrolID) referring to the UL power control parameter set. In other words, the UL control parameter set may not be explicitly indicated in the UL-TCI-State IE, but may be obtained separately using an identifier (e.g., sri-PUSCH-powercontrolID). The sri-PUSCH-powercontrolID may define the pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex parameters according to the SRI-PUSCH-PowerControl IE described previously with reference to Table 1. In the UL-TCI-State IE of Table 7, the ul-qcl-Type IE may indicate the configuration of the TCI state associated with the ul-TCI-stat-Id. An example of the UL-QCL-Info IE is provided herein with reference to Table 3.

[0086] Table 7

[0087]

[0088] In some aspects of the present disclosure, the RRC layer may configure an association between an uplink transmission control indicator (UL-TCI) and an uplink power control (ULPC) configuration using a first example dedicated RRC message. For example, in a scenario where the DCI does not include a sounding reference signal resource indication (SRI) field but includes a TCI field, the UE may determine an uplink power control (ULPC) configuration for PUSCH transmission power (e.g., P as defined in formula (1)). PUSCH,b,f,c (i,j,q d ,l)) can be indicated by the UL-TCI state indicated in the TCI field. In other words, the UE can determine the uplink power control (ULPC) configuration based on the TCI field of the UL DCI and the association between the UL-TCI and the ULPC configuration defined in the first example dedicated RRC message.

[0089] Table 7 shows the structure of a first example dedicated RRC message for configuring an association between a UL-TCI state and a ULPC. In Table 7, the UL-TCI-state-and-SRI-association IE expressed in an ASN.1 notation format may represent an example implementation of the first example dedicated RRC message previously discussed. In Table 7, ul-TCI-stat-Id may indicate a UL-TCI state defined by the UL-TCI-State IE shown in Table 8. sri-PUSCH-powercontrolID may indicate a ULPC configuration (e.g., a UL power control parameter set) associated with the UL-TCI state. For example, sri-PUSCH-powercontrolID may define any one of the pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex parameters according to the SRI-PUSCH-PowerControl IE described previously with reference to Table 1. Therefore, when the UE receives the UL-TCI-state-and-SRI-association IE shown in Table 7 through RRC signaling, and also receives the UL-TCI indicated by the TCI field in the UL DCI, the UE can determine the UL power control parameter set to be used in the TCI state based on the association configured in the UL-TCI-state-and-SRI-association IE (for example, defined by sri-PUSCH-PowercontrolID in the UL-TCI-state-and-SRI-association IE).

[0090] Table 7

[0091]

[0092] Table 8

[0093]

[0094] In some aspects of the present disclosure, the RRC layer may use a second example dedicated RRC message to configure an association between an uplink transmission control indicator (UL-TCI) and an uplink power control (ULPC) configuration. For example, in a scenario where the DCI includes an SRI field and a TCI field, the UE may determine an uplink power control (ULPC) configuration for PUSCH transmission power (e.g., P as defined in formula (1)). PUSCH,b,f,c (i,j,q d,l)) may be indicated by a SRI and UL-TCI state pair. The uplink power control (ULPC) configuration may be a UL power control parameter set indicated by sri-PUSCH-PowercontrolID. In other words, the UE may receive the SRI and UL-TCI state in the UL DCI, and may determine the uplink power control (ULPC) configuration associated with the SRI and UL-TCI defined in the second example dedicated RRC message (e.g., which may be included in the UL DCI).

[0095] Table 9 shows the structure of a second example dedicated RRC message for configuring the association between the SRI and UL-TCI state pair and the ULPC configuration. In Table 9, the UL-TCI-state-and-SRI-and-ULPCassociation IE expressed in the ASN.1 notation format may represent an example implementation of the second example dedicated RRC message previously discussed. In Table 9, ul-TCI-stat-Id may indicate the UL-TCI state defined by the UL-TCI-State IE shown in Table 8. sri-ID may represent SRI. sri-PUSCH-powercontrolID may indicate the ULPC configuration (e.g., UL power control parameter set) associated with the sri-ID and ul-TCI-stat-Id pair. For example, sri-PUSCH-powercontrolID may define any one of the pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex parameters according to the SRI-PUSCH-PowerControl IE described previously with reference to Table 1. Therefore, when the UE receives the UL-TCI-state-and-SRI-and-ULPC association IE shown in Table 9 through RRC signaling, and also receives the SRI and UL-TCI in the UL DCI, the UE can determine the UL power control parameter set to be used for the SRI and UL-TCI based on the association configured in the UL-TCI-state-and-SRI-and-ULPC association IE (for example, defined by the sri-PUSCH-PowercontrolID in the UL-TCI-state-and-SRI-and-ULPCassociation IE).

[0096] Table 9

[0097]

[0098] Table 10 shows the structure of a second example dedicated RRC message for configuring the association between the SRI and UL-TCI state pair and the ULPC configuration according to another embodiment. In Table 10, the UL-TCIandSRIId parameter can define a ul-TCI-stat-Id and sri-ID pair. The sri-PUSCH-powercontrolID can indicate the ULPC configuration (e.g., UL power control parameter set) associated with the sri-ID and ul-TCI-stat-Id pair defined by UL-TCI and SRIId. For example, the sri-PUSCH-powercontrolID can define any one of the pathlossReferenceRS-Id, p0-Id, alpha-Id, and closedLoopIndex parameters according to the SRI-PUSCH-PowerControl IE described previously with reference to Table 1. Therefore, when the UE receives the UL-TCI-state-and-SRI-and-ULPC association IE shown in Table 10 through RRC signaling, and also receives the SRI and UL-TCI in the UL DCI, the UE can determine the UL power control parameter set to be used for the SRI and UL-TCI based on the association configured in the UL-TCI-state-and-SRI-and-ULPC association IE (for example, defined by the sri-PUSCH-PowercontrolID in the UL-TCI-state-and-SRI-and-ULPC association IE).

[0099] Table 10

[0100]

[0101] Association between UL-TCI and ULPC based on MAC-CE

[0102] In some aspects of the present disclosure, the UL-TCI may be associated with an uplink power control (ULPC) configuration using a MAC-CE. In these aspects, and as referred to herein Figure 7 As described in detail, MAC-CE may associate each active TCI to a certain SRI-PUSCH-powercontrolID for PUSCH.

[0103] Figure 7 An example UE-specific PUSCH MAC-CE 700 for associating an active UL-TCI state with a UL PC configuration is shown in accordance with various aspects of the present disclosure. Figure 7As shown, the UE-specific PUSCH MAC-CE 700 may include a reserved bit field 702, a serving cell ID field 704, a bandwidth part ID (BWP ID) field 706, and a bitmap, wherein each bit in the bitmap (e.g., bit T0 708, bit T1 710, ..., bit T (N-2)×8+7 712) corresponds to a TCI state. For example, the base station can activate up to eight TCI states by setting bits in the bitmap to '1'. Therefore, when a bit in the bitmap (e.g., bit T0 708) is set to '1', the TCI state corresponding to the bit (e.g., the first TCI state) is activated, and when a bit in the bitmap (e.g., bit T1 710) is set to '0', the TCI state corresponding to the bit (e.g., the second TCI state) is deactivated. The bits set to '1' in the bitmap can be assigned to one of the eight possible code points in ascending order. For example, if bit T0 708, bit T1 710, and bit T0 708 are set to '1', the TCI state corresponding to the bit (e.g., the second TCI state) is deactivated. (N-2)×8+7 712 is set to '1' and the remaining bits in the bitmap are set to '0', code point 0 may be set to T0, code point 1 may be set to T1, and code point 2 may be set to T (N-2)×8+7 .

[0104] like Figure 7As further shown in , one or more octets including the ULPC configuration may be appended to the UE-specific PUSCH MAC-CE 700. Each octet may correspond to a code point, and the ULPC configuration indicated in the octet may be associated with the corresponding code point. For example, if only one bit in the bitmap of the MAC-CE 700 is set to '1', the MAC-CE 700 may include an octet N+1 752, which includes the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0). Therefore, the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0) may be mapped to code point 0. As another example, if eight bits in the bitmap of the MAC-CE 700 are set to '1', the MAC-CE 700 may include: octet N+1 752 including a first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0), octet N+2 754 including a second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1), octet N+3 754 including a third ULPC configuration (e.g., SRI-PUSCH-powercontrolID2), and so on, until a final octet N+8 758 including an eighth ULPC configuration (e.g., SRI-PUSCH-powercontrolID7). In this example, the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0) may be associated with code point 0 (e.g., a first TCI state), the second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1) may be associated with code point 1 (e.g., a second TCI state), and so on. References Figure 8 An example application of the UE-specific PUSCH MAC-CE 700 for four code points is described.

[0105] Figure 8 An example UE-specific PUSCH MAC-CE 800 for associating an active UL-TCI state with a UL PC configuration is shown in accordance with various aspects of the present disclosure. Figure 8 As shown, the base station can set bits T1 802, T4 804, T 12 806 and T 14 808 is set to '1' to activate the four TCI states. The remaining bits can be set to '0'. Therefore, mapping to T1 802, T4 804, T 12 806 and T 14The TCI state of 808 can be mapped to code point 0, code point 1, code point 2 and code point 3 respectively. Figure 8 As shown, the UE-specific PUSCH MAC-CE 800 includes four octets 852, 854, 856, 858 corresponding to code point 0, code point 1, code point 2, and code point 3, respectively. The ULPC configuration included in the octet can be associated with the code point corresponding to the octet. For example, code point 0 can be associated with a first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0), code point 1 can be associated with a second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1), code point 2 can be associated with a third ULPC configuration (e.g., SRI-PUSCH-powercontrolID2), and code point 3 can be associated with a fourth ULPC configuration (e.g., SRI-PUSCH-powercontrolID3). For example, when the UL DCI indicates code point 1 for PUSCH (e.g., '001' in a 3-bit field in the DCI), the UE may determine that the UL-TCI state ID is 4 and the power control parameters for PUSCH should be set according to sri-PUSCH-PowercontrolID1. The UL-TCI states may be defined according to Table 11.

[0106] Table 11

[0107]

[0108] In some aspects of the present disclosure, a plurality of TCI code points may be associated with corresponding uplink power control (ULPC) configurations using MAC-CE. In these aspects, and as referred to herein Fig. 9 As described in detail, MAC-CE may associate each TCI code point to a certain SRI-PUSCH-powercontrolID for PUSCH.

[0109] Fig. 9 An example UE-specific PUSCH MAC-CE 900 for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure. Fig. 9As shown, the UE-specific PUSCH MAC-CE 900 may include a reserved bit field 902, a serving cell ID field 904, a bandwidth part ID (BWP ID) field 906, and a bitmap, wherein each bit in the bitmap (e.g., bit CP0 908, bit CP1 910, ..., bit CP7 912) corresponds to a TCI code point in the UL DCI. For example, the base station can activate up to 8 TCI code points (e.g., TCI states) for the UL DCI by setting the bits in the bitmap to '1'. Therefore, when a bit in the bitmap (e.g., bit CP0 908) is set to '1', the TCI code point corresponding to the bit (e.g., code point 0) is activated in the UL DCI, and when a bit in the bitmap (e.g., bit CP1 910) is set to '0', the TCI code point corresponding to the bit (e.g., code point 1) is deactivated in the UL DCI.

[0110] like Fig. 9 As further shown in , one or more octets including the ULPC configuration may be appended to the UE-specific PUSCH MAC-CE 900. Each octet may correspond to a code point, and the ULPC configuration indicated in the octet may be associated with the corresponding code point. For example, if only one bit in the bitmap of the MAC-CE 900 is set to '1', the MAC-CE 900 may include octet 3 952, which includes the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0). Therefore, the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0) may be mapped to code point 0. As another example, if eight bits in the bitmap of the MAC-CE 900 are set to '1', the MAC-CE 900 may include: octet 3 952 including the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0), octet 4 954 including the second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1), and so on, until the last octet 9 956 including the eighth ULPC configuration (e.g., SRI-PUSCH-powercontrolID7). In this example, the first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0) may be associated with code point 0 (e.g., the first TCI state), the second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1) may be associated with code point 1 (e.g., the second TCI state), and so on. Reference is made to Fig.10An example application of a UE-specific PUSCH MAC-CE 900 for four code points is described.

[0111] Fig.10 An example UE-specific PUSCH MAC-CE 1000 is shown for associating multiple TCI code points in a UL DCI with corresponding UL PC configurations in accordance with various aspects of the present disclosure. Fig.10 As shown, the base station can activate four TCI code points by setting bits CP01002, CP1 1004, CP2 1006, and CP34 1008 in the bitmap to '1'. The remaining bits can be set to '0'. Fig.10 As shown, the UE-specific PUSCH MAC-CE 1000 includes four octets 1052, 1054, 1056, 1058 corresponding to code point 0, code point 1, code point 2, and code point 3, respectively. The ULPC configuration included in the octet can be associated with the code point corresponding to the octet. For example, code point 0 can be associated with a first ULPC configuration (e.g., SRI-PUSCH-powercontrolID0), code point 1 can be associated with a second ULPC configuration (e.g., SRI-PUSCH-powercontrolID1), code point 2 can be associated with a third ULPC configuration (e.g., SRI-PUSCH-powercontrolID2), and code point 3 can be associated with a fourth ULPC configuration (e.g., SRI-PUSCH-powercontrolID3). For example, when the UL DCI indicates code point 2 for PUSCH (e.g., '010' in a 3-bit field in the DCI), the UE can determine the UL-TCI state associated with code point 2 and determine that the power control parameters for PUSCH for the UL-TCI state should be set according to sri-PUSCH-PowercontrolID2.

[0112] In some aspects of the present disclosure, a single TCI code point may be associated with an uplink power control (ULPC) configuration using MAC-CE. In these aspects, and as referred to herein Fig.12 As described in detail, MAC-CE may associate a TCI code point to a certain SRI-PUSCH-powercontrolID for PUSCH.

[0113] Fig.11 An example UE-specific PUSCH MAC-CE 1100 for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure. Fig.11As shown, the UE-specific PUSCH MAC-CE 1100 may include a reserved bit field 1102, a serving cell ID field 1104, a bandwidth part ID (BWP ID) field 1106, a TCI state ID / code point ID (CPID) field 1150, and an uplink power control (ULPC) configuration field 1152. Fig.11 As shown, the ULPC configuration field 1152 may include SRI-PUSCH-powercontrolID. Therefore, the MAC-CE 1100 associates the code point (e.g., CPID) or TCI state ID in the field 1150 with the ULPC configuration (e.g., sri-PUSCH-powercontrolID) indicated in the ULPC configuration field 1152.

[0114] Fig.12 An example UE-specific PUSCH MAC-CE 1200 for associating a TCI code point with a UL PC configuration is shown in accordance with various aspects of the present disclosure. Fig.12 As shown, the UE-specific PUSCH MAC-CE 1200 may include a reserved bit field 1202, a serving cell ID field 1204, a bandwidth part ID (BWP ID) field 1206, a TCI state ID / code point ID (CPID) field 1250, a SRI-ID field 1252, and an uplink power control (ULPC) configuration field 1254. Fig.12 As shown, the ULPC configuration field 1254 may include SRI-PUSCH-powercontrolID. Therefore, the MAC-CE 1200 associates the code point (e.g., CP ID) or TCI state ID in field 1250 and the SRI-ID indicated in the SRI-ID field 1252 with the ULPC configuration (e.g., sri-PUSCH-powercontrolID) indicated in the ULPC configuration field 1254.

[0115] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 402; apparatus 1502 / 1502'; processing system 1614, which may include memory 360, and which may be the entire UE 402 or a component of UE 402, such as TX processor 368, RX processor 356 and / or controller / processor 359).

[0116] At 1302, the UE determines an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message (e.g., an RRC message from a base station). In some aspects of the present disclosure, the association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is a direct association or an indirect association. In some aspects of the present disclosure, the uplink power control (ULPC) configuration (e.g., Table 1) includes a power control parameter set, the power control parameter set including at least one of the following: a target signal-to-interference-plus-noise ratio (SINR), a path loss compensation factor, a path loss downlink reference signal (RS), or a closed loop index value.

[0117] In some aspects of the present disclosure, the association between one or more transmission configuration indicators TCI and one or more corresponding uplink power control (ULPC) configurations is a direct association. In these aspects, the control message includes a transmission configuration indicator (TCI) parameter and a power control parameter set (e.g., Table 5).

[0118] In some aspects of the present disclosure, the association between one or more transmission configuration indicators TCI and one or more corresponding uplink power control (ULPC) configurations is an indirect association. In these aspects, one or more corresponding uplink power control (ULPC) configurations are defined by reference to a power control information element (IE) (e.g., Table 6).

[0119] In some aspects of the disclosure, the control message is a dedicated radio resource control (RRC) message, and the control message does not include a sounding reference signal resource indication (SRI) field.

[0120] In some aspects of the present disclosure, the control message is a dedicated radio resource control (RRC) message. In these aspects, the control message also includes a sounding reference signal resource indication (SRI) field. The control message (e.g., Table 9, Table 10) may indicate an association between a SRI value and a transmission configuration indicator (TCI) value pair and a corresponding uplink power control (ULPC) configuration (e.g., sri-PUSCH-PowercontrolID).

[0121] In some aspects of the present disclosure, the control message is a MAC-CE (e.g., MAC-CE 700, 800). The MAC-CE activates one or more transmission configuration indicators (TCIs) and indicates one or more corresponding uplink power control (ULPC) configurations for the activated one or more transmission configuration indicators (TCIs). In other aspects, the control message is a MAC-CE (e.g., MAC-CE 900, 1000). The MAC-CE is configured to associate multiple code points representing one or more transmission configuration indicators (TCIs) with one or more corresponding uplink power control (ULPC) configurations. In some aspects of the present disclosure, the control message is a MAC-CE (e.g., MAC-CE 1100). The MAC-CE is configured to associate a single code point representing one of the one or more transmission configuration indicators (TCIs) with one of the one or more corresponding uplink power control (ULPC) configurations. In some aspects of the present disclosure, the control message is a MAC-CE (e.g., MAC-CE 1200). The MAC-CE is configured to associate a single codepoint representing one of one or more transmission configuration indicators (TCIs) and a single sounding reference signal resource indication (SRI) value with one of one or more corresponding uplink power control (ULPC) configurations.

[0122] At 1304, the UE receives control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel.

[0123] Finally, at 1306, the UE determines a transmission power for transmissions on an uplink (UL) channel based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

[0124] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 402; apparatus 1502 / 1502'; processing system 1614, which may include memory 360, and which may be the entire UE 402 or a component of UE 402, such as TX processor 368, RX processor 356 and / or controller / processor 359).

[0125] At 1402, the UE determines that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel.

[0126] At 1404, the UE determines a transmission configuration indicator (TCI) configured for a downlink (DL) channel.

[0127] Finally, at 1406, the UE applies the transmission configuration indicator (TCI) configured for the downlink (DL) channel for transmission in the uplink (UL) channel.

[0128] Fig.15 15 is a conceptual data flow diagram 1500 illustrating the flow of data between different units / components in an example apparatus 1502. The apparatus may be a UE. The apparatus includes a receiving component 1504 that receives a control message 1518 and a DCI message 1520. In some examples, the control message 1518 may be a radio resource control (RRC) message (e.g., Figure 4 1526). In some examples, the control message 1518 can be a MAC-CE (e.g., MAC-CE 700, 800, 900, 1000, 1100, 1200). The apparatus also includes a transmitting component 1506 that transmits at least one UL signal 1538 to a base station 1550. The apparatus also includes a control information receiving component 1508 that receives control information (e.g., DCI 1524) indicating a transmission configuration indicator (TCI) (e.g., TCI 1526) for transmission on an uplink (UL) channel. The control information can include UL PC configuration information in a field of TCI 1526.

[0129] The apparatus also includes a TCI and ULPC association determining component 1510 that determines an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations (e.g., ULPC configuration 1528) based on a control message (e.g., control message 1522). The apparatus also includes a transmission power determining component 1512 that determines a transmission power (e.g., transmission power 1530) for a transmission on an uplink (UL) channel based on an uplink power control (ULPC) configuration (e.g., ULPC configuration 1528) associated with the transmission configuration indicator (TCI).

[0130] The apparatus also includes a TCI determination component 1514 that determines (e.g., based on a control message 1532) that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel, and determines (e.g., based on a control message 1532) a transmission configuration indicator (TCI) (e.g., DL TCI 1534) that is configured for a downlink (DL) channel; and a TCI application component 1516 that applies a transmission configuration indicator (TCI) (e.g., DL TCI 1536) that is configured for a downlink (DL) channel for transmission in an uplink (UL) channel.

[0131] The apparatus may include performing the above Fig.13 and Fig.14 Each block in the algorithm in the flowchart is an additional component. Therefore, the above Fig.13 and Fig.14 Each block in the flowchart of can be performed by a component and a device that may include one or more of those components. These components can be one or more hardware components specifically configured to perform the process / algorithm, which are implemented by a processor configured to perform the process / algorithm, the process / algorithm is stored in a computer-readable medium, implemented by a processor, or some combination thereof.

[0132] Fig.16 1 is a schematic diagram 1600 showing an example of a hardware implementation of an apparatus 1502' using a processing system 1614. The processing system 1614 may be implemented with a bus architecture, generally represented by a bus 1624. The bus 1624 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1614 and the overall design constraints. The bus 1624 links together various circuits, including one or more processors and / or hardware components, generally represented by the processor 1604, components 1504, 1506, 1508, 1510, 1512, 1514, 1516, and computer readable medium / memory 1606. The bus 1624 may also link together various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further.

[0133] The processing system 1614 may be coupled to the transceiver 1610. The transceiver 1610 is coupled to one or more antennas 1620. The transceiver 1610 provides a means for communicating with various other devices over a transmission medium. The transceiver 1610 receives signals from the one or more antennas 1620, extracts information from the received signals, and provides the extracted information to the processing system 1614 (specifically, the receiving component 1504). In addition, the transceiver 1610 receives information from the processing system 1614 (specifically, the transmitting component 1506) and generates signals applied to the one or more antennas 1620 based on the received information. The processing system 1614 includes a processor 1604 coupled to a computer-readable medium / memory 1606. The processor 1604 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory 1606. When the software is executed by the processor 1604, the software causes the processing system 1614 to perform the various functions described above for any particular device. The computer-readable medium / memory 1606 may also be used to store data manipulated by the processor 1604 when executing software. The processing system 1614 also includes at least one of the components 1504, 1506, 1508, 1510, 1512, 1514, 1516. The component may be a software component located / stored in the computer-readable medium / memory 1606 and executed in the processor 1604, one or more hardware components coupled to the processor 1604, or some combination thereof. The processing system 1614 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 1614 may be the entire UE (e.g., see Figure 3 of 350).

[0134] In one configuration, an apparatus 1502 / 1502' for wireless communication includes: a unit for determining an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message; a unit for receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel; and a unit for determining a transmission power for transmission on an uplink (UL) channel based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI); a unit for determining that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; a unit for determining a transmission configuration indicator (TCI) configured for a downlink (DL) channel; and a unit for applying a transmission configuration indicator (TCI) configured for a downlink (DL) channel for transmission in an uplink (UL) channel.

[0135] The aforementioned means may be one or more of the aforementioned components of the apparatus 1502 and / or a processing system 1614 of the apparatus 1502' configured to perform the functions recited by the aforementioned means. As described above, the processing system 1614 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0136] Further disclosures are included in the appendix.

[0137] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of the blocks in these process / flowcharts can be rearranged according to design preferences. In addition, some blocks can be combined or omitted. The attached method claims present the elements of each block in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0138] The above description is provided to enable any technician in the field to implement the various aspects described herein. Various modifications in these aspects are obvious to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should conform to the full range consistent with the expression content of the claims, wherein, unless explicitly stated, the elements mentioned in the singular form are not intended to mean "one and only one", but to mean "one or more". The word "exemplary" used in this article means "used as an example, instance or illustration". Any aspect described as "exemplary" in this article is not necessarily interpreted as preferred or more advantageous than other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, A only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members or some members of A, B, or C. All structures and functions equivalent to the elements of the various aspects described throughout the present disclosure that are known or to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included in the claims. In addition, regardless of whether the disclosure is expressly recited in the claims, the content disclosed herein is not intended to be dedicated to the public. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "unit." Therefore, unless the element is expressly recited using the phrase "unit for...", the element shall not be interpreted as a unit plus function.

Claims

1. A method for wireless communication of a user equipment (UE), include: determining an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message, wherein the control message is a dedicated radio resource control (RRC) message; receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel, wherein the control information further comprises a sounding reference signal resource indication (SRI) field, and wherein the control message indicates an association between a pair of SRI value and transmission configuration indicator (TCI) value and a corresponding uplink power control (ULPC) configuration; and A transmission power for the transmission on the uplink (UL) channel is determined based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

2. The method according to claim 1, in, The uplink power control (ULPC) configuration includes a power control parameter set, the power control parameter set including at least one of the following: a target signal-to-interference-plus-noise ratio (SINR), a path loss compensation factor, a path loss downlink reference signal (RS), or a closed loop index value.

3. The method according to claim 1, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is a direct association or an indirect association.

4. The method according to claim 3, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is the direct association, wherein the control message includes a transmission configuration indicator (TCI) parameter and a power control parameter set.

5. The method according to claim 3, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is the indirect association, and wherein the one or more corresponding uplink power control (ULPC) configurations are defined by reference to a power control information element (IE).

6. The method according to claim 1, further comprising: include: Transmitting to a base station on the uplink (UL) channel is performed based on the determined transmission power.

7. An apparatus for wireless communication, include: Memory; as well as at least one processor coupled to the memory and configured to: determining an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message, wherein the control message is a dedicated radio resource control (RRC) message; receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel, wherein the control information further comprises a sounding reference signal resource indication (SRI) field, and wherein the control message indicates an association between a pair of SRI value and transmission configuration indicator (TCI) value and a corresponding uplink power control (ULPC) configuration; and A transmission power for the transmission on the uplink (UL) channel is determined based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

8. The device according to claim 7, in, The uplink power control (ULPC) configuration includes a power control parameter set, the power control parameter set including at least one of the following: a target signal-to-interference-plus-noise ratio (SINR), a path loss compensation factor, a path loss downlink reference signal (RS), or a closed loop index value.

9. The device according to claim 7, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is a direct association or an indirect association.

10. The device according to claim 9, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is the direct association, wherein the control message includes a transmission configuration indicator (TCI) parameter and a power control parameter set.

11. The device according to claim 9, in, The association between the one or more transmission configuration indicators (TCIs) and the one or more corresponding uplink power control (ULPC) configurations is the indirect association, and wherein the one or more corresponding uplink power control (ULPC) configurations are defined by reference to a power control information element (IE).

12. The device according to claim 7, in, The at least one processor is further configured to: Transmitting to a base station on the uplink (UL) channel is performed based on the determined transmission power.

13. An apparatus for wireless communication, include: means for determining an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations based on a control message, wherein the control message is a dedicated radio resource control (RRC) message; means for receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel, wherein the control information further comprises a sounding reference signal resource indication (SRI) field, and wherein the control message indicates an association between a pair of SRI values ​​and a transmission configuration indicator (TCI) value and a corresponding uplink power control (ULPC) configuration; and Means for determining a transmission power for the transmission on the uplink (UL) channel based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

14. A computer readable medium storing computer executable code, wherein when the code is executed by a processor, the processor is caused to perform the following operations: determining, based on the control message, an association between one or more transmission configuration indicators (TCIs) and one or more corresponding uplink power control (ULPC) configurations, in, The control message is a dedicated Radio Resource Control (RRC) message; receiving control information indicating a transmission configuration indicator (TCI) for transmission on an uplink (UL) channel, wherein the control information further comprises a sounding reference signal resource indication (SRI) field, and wherein the control message indicates an association between a pair of SRI value and transmission configuration indicator (TCI) value and a corresponding uplink power control (ULPC) configuration; and A transmission power for the transmission on the uplink (UL) channel is determined based on an uplink power control (ULPC) configuration associated with the transmission configuration indicator (TCI).

15. A method for wireless communication of a user equipment (UE), include: determining that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; determining a transmission configuration indicator (TCI) configured for a downlink (DL) channel; and The transmission configuration indicator (TCI) configured for a downlink (DL) channel is applied for transmission in the uplink (UL) channel.

16. An apparatus for wireless communication, include: means for determining that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; means for determining a transmission configuration indicator (TCI) configured for a downlink (DL) channel; as well as Means for applying the transmission configuration indicator (TCI) configured for a downlink (DL) channel for transmissions in the uplink (UL) channel.

17. An apparatus for wireless communication, include: Memory; as well as at least one processor coupled to the memory and configured to: determining that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; determining a transmission configuration indicator (TCI) configured for a downlink (DL) channel; and The transmission configuration indicator (TCI) configured for a downlink (DL) channel is applied for transmission in the uplink (UL) channel.

18. A computer readable medium storing computer executable code, wherein when the code is executed by a processor, the processor is caused to perform the following operations: determining that no transmission configuration indicator (TCI) is configured for an uplink (UL) channel; determining a transmission configuration indicator (TCI) configured for a downlink (DL) channel; and The transmission configuration indicator (TCI) configured for a downlink (DL) channel is applied for transmission in the uplink (UL) channel.