Detection reference signal trigger technology

Abstract

Certain aspects of the present disclosure provide techniques for wireless communications by a user equipment (UE). The method generally includes: receiving downlink control information (DCI) having at least one block, the at least one block being configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; if the DCI lacks a transmit power control (TPC) command for at least one SRS set, determining a transmit power control (TPC) command to be applied to an A-SRS; and transmitting the A-SRS according to the DCI and the determined TPC command.

Description

Technical Field

[0001] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for triggering an aperiodic sounding reference signal (SRS) via downlink control information (DCI). Background Art

[0002] 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 the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) system, the Advanced LTE (LTE-A) system, the Code Division Multiple Access (CDMA) system, the Time Division Multiple Access (TDMA) system, the Frequency Division Multiple Access (FDMA) system, the Orthogonal Frequency Division Multiple Access (OFDMA) system, the Single Carrier Frequency Division Multiple Access (SC FDMA) system, and the Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, etc.

[0003] In some examples, a wireless multiple access communication system may include multiple base stations (BS), each of which is capable of supporting communication of multiple communication devices (also referred to as user equipment (UE)) simultaneously. In an LTE or LTE-A network, a collection of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation, new radio (NR) or 5G network), a wireless multiple access communication system may include multiple distributed units (DU) (e.g., edge units (EU), edge nodes (EN), radio heads (RH), smart radio heads (SRH), transmit receive points (TRP), etc.) communicating with multiple central units (CU) (e.g., central nodes (CN), access node controllers (ANC), etc.). A collection of one or more distributed units communicating with a central unit may define an access node (e.g., which may be referred to as a base station, 5G NB, next generation NodeB (gNB or gNodeB), TRP, etc.). A base station or distributed unit may communicate with a group of UEs on a downlink channel (e.g., for transmission from a base station or to a UE) and an uplink channel (e.g., for transmission from a UE to a base station or distributed unit).

[0004] These multiple access technologies have been adopted by various telecommunication standards to provide a common protocol that enables different wireless devices to communicate across cities, countries, regions, and even the globe. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard released by 3GPP. It is designed to better support mobile broadband Internet access by increasing spectral efficiency, reducing costs, improving services, leveraging new spectrum, and better integrating with other open standards that use OFDMA with cyclic prefixes (CP) on both downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] However, as the demand for mobile broadband access continues to grow, further improvements to NR and LTE technologies are needed. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that adopt these technologies. Summary of the invention

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

[0007] Certain aspects provide a method of wireless communication by a user equipment (UE). The method generally includes receiving downlink control information (DCI) having at least one block, the at least one block being configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; if the DCI lacks a transmit power control (TPC) command for at least one SRS set, determining a transmit power control (TPC) command to be applied to an A-SRS; and transmitting the A-SRS according to the DCI and the determined TPC command.

[0008] Certain aspects provide a method for wireless communications by a network entity. The method generally includes: sending downlink control information (DCI) having at least one block to at least one user equipment (UE), the at least one block configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; deciding whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions; and processing an A-SRS sent according to the DCI.

[0009] Certain aspects of the present disclosure also provide various devices, means, and computer-readable media configured to perform (or cause a processor to perform) the operations described herein. In fact, various aspects implement and provide enhanced downlink control information (e.g., DCI format 2_3), which is configured to implement flexible SRS triggering for changing SRS usage. The deployment and use scenarios are not limited to antenna switching situations, and can be used when little or no antenna switching occurs. In addition, various aspects implement cross-carrier or cross-component carrier SRS triggering and simultaneous transmission (e.g., CC with PUSCH).

[0010] 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 the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of a few of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to understand the above features of the present disclosure in more detail, reference may be made to some aspects for a more specific description, briefly summarizing the above content, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered as limiting its scope, as the description may admit of other equally effective aspects.

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

[0013] 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.

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

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

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

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

[0018] Fig. 7A and 7B

[0013] Example SRS resource sets and DCI for triggering the SRS resource sets according to some aspects are shown.

[0019] Fig. 8A and 8B

[0046] An example DCI format is shown that may be used to trigger A-SRS in accordance with some aspects.

[0020] Fig. 9 Example operations of a UE according to aspects of the present disclosure are shown.

[0021] Fig.10 Example operations of network entities according to aspects of the present disclosure are shown.

[0022] Fig.11 An example DCI format that may be used to trigger A-SRS according to aspects of the present disclosure is shown.

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

[0024] Various aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for triggering A-SRS via one or more DCI formats. As will be described in more detail below, in some scenarios, the DCI may lack power information (e.g., transmit power control (TPC) commands), and the UE may determine what TPC to apply based on other considerations.

[0025] The following description provides examples and does not limit the scope, applicability or examples set forth in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace or add various processes or components. For example, the described method may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with respect 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 a device or method that is practiced using structures and functions or other structures and functions of various aspects of the present disclosure set forth herein in addition to or different from those set forth herein. It should be understood that any aspect of the present disclosure described herein may be embodied by one or more elements of the claims. The term "exemplary" used herein means "used as an example, instance or illustration". Any aspect described herein as "exemplary" is not necessarily to be interpreted as being more preferred or more advantageous than other aspects.

[0026] 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 wireless technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband Code Division Multiple Access (WCDMA) and other variants of 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 part of Universal Mobile Telecommunications System (UMTS).

[0027] New Radio (NR) is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (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 can be used for the above-mentioned wireless networks and radio technologies as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other communication systems based on generations, such as 5G and higher, including NR technologies.

[0028] New radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting broadband (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 their respective quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0029] Example Wireless Communication System

[0030] Figure 1 An example wireless communication network 100 is shown in which aspects of the present disclosure may be performed. For example, a UE 120 may be configured to perform Fig. 9 The operation 900 is to send the Fig.10 In operation 1000, the base station 110 transmits a DCI triggered A-SRS.

[0031] like Figure 1 As shown, the wireless network 100 may include multiple 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 Node B (NB) and / or a Node B 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 NodeB (gNB), new radio base station (NR BS), 5G NB, access point (AP) or transmit receive point (TRP) may be interchangeable. In some examples, the cell is not necessarily stationary, and the geographic area of ​​the cell may move according to the location of the mobile BS. In some examples, the base station may use any suitable transport network, interconnected with each other and / or with 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, etc.

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

[0033] 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., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). The BS of a macro cell may be referred to as a macro BS. The BS of a pico cell may be referred to as a pico BS. The BS of a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, base stations 110a, 110b, and 110c may be macro base stations for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. Base stations 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.

[0034] 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 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, 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.

[0035] 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).

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

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

[0038] UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical device, biometric sensor / device, wearable device such as smart watch, smart clothes, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. 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 can communicate with a BS, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.

[0039] Some wireless networks, such as LTE, use 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 commonly referred to as tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with 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 the 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 can also be divided 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.

[0040] 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 both 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 transmissions with precoding may also be supported. The MIMO configuration in the DL may support up to 8 transmit antennas, up to 8 streams per UE, and multi-layer DL transmissions of up to 2 streams. Multi-layer transmissions of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported through up to 8 serving cells.

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

[0042] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with double arrows represents interfering transmissions between a UE and a BS.

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

[0044] 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 shown). For example, for RAN sharing, Radio as a Service (RaaS), and service specific and deployment, the TRP 208 may be connected to more than one ANC. Each TRP 208 may include one or more antenna ports. The TRP 208 may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0045] The logical architecture of the distributed RAN 200 can support front-end backhaul solutions across different deployment types. For example, the logical architecture can be based on the sending network capabilities (e.g., bandwidth, delay and / or jitter).

[0046] 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 front-end backhaul for LTE and NR.

[0047] The logical architecture of the distributed RAN 200 may enable cooperation between TRPs 208, for example, within a TRP and / or across TRPs via the ANC 202. An intra-TRP interface may not be used.

[0048] Logical functions can be dynamically distributed in the logical architecture of the distributed RAN 200. Figure 5Described 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., ANC202).

[0049] Figure 3 An example physical architecture of a distributed radio access network (RAN) 300 according to aspects of the present disclosure is shown. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. C-CU 302 functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity.

[0050] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Alternatively, 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 network edge.

[0051] 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) capabilities.

[0052] Figure 4 BS 110 and UE 120 (eg Figure 1 4, 54, 56, 57, 58, 59 and 60 of the UE 120 may be used to perform Fig. 9 Similarly, antenna 434, processors 420, 430, 438, and / or controller / processor 440 of UE 120 may be configured to perform Fig.10 Operation 1000.

[0053] 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., for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS). A 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 (if applicable), and may provide output symbol streams to modulators (MODs) 432a to 432t. Each modulator 432 can process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a through 432t can be transmitted via antennas 434a through 434t, respectively.

[0054] 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) in transceivers 454a to 454r, 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 if applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

[0055] On the uplink, at the UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) transmission and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals (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 a demodulator in the transceivers 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120 may be received by the 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 transmitted by the UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

[0056] Figure 5 A diagram 500 is shown showing an example for implementing a communication protocol stack according to aspects of the present disclosure. The communication protocol stack shown can be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 shows a communication protocol stack, including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a media access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack can be implemented as independent modules of software, parts of a processor or ASIC, parts of devices that are not connected together by a communication link, or various combinations thereof. For example, collocated and non-collocated implementations can be used in a protocol stack of a network access device (e.g., AN, CU, and / or DU) or a UE.

[0057] The first option 505-a illustrates a separate implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2 ANC 202 in the 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 collocated or non-collocated. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

[0058] 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 may be useful in, for example, a femtocell deployment.

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

[0060] In LTE, the basic transmission time interval (TTI) or packet duration is a 1ms subframe. In NR, the subframe is still 1ms, but the basic TTI is called a time slot. Depending on the subcarrier spacing, the subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16...time slots). NR RB is 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15KHz, and other subcarrier spacings such as 30kHz, 60kHz, 120kHz, 240kHz, etc. can be defined relative to the basic subcarrier spacing. The symbol and time slot lengths are proportional to the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0061] Figure 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into radio frame units. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes, each 1 ms, indexed from 0 to 9. Depending on the subcarrier spacing, 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). The symbol periods in each slot may be assigned indices. A mini slot, which may be referred to as a subslot structure, refers to a transmission time interval having a duration less than one slot (e.g., 2, 3, or 4 symbols).

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

[0063] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and dual-symbol PBCH. The SS block can be transmitted at a fixed time slot position, such as Figure 6 Symbols 0-3 shown. The UE can use PSS and SSS for cell search and acquisition. PSS can provide half-frame timing, and 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 a radio frame, SS burst set period, system frame number, etc. SS blocks can be organized into SS bursts to support beam scanning. Further system information such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI) can be sent on the physical downlink shared channel (PDSCH) in certain subframes. For example, for mmW, SS blocks can be sent up to 64 times with up to 64 different beam directions. Up to 64 transmissions of SS blocks are called SS burst sets.

[0064] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical grids, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal transmitted from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be delivered using a licensed spectrum (unlike wireless local area networks that typically use unlicensed spectrum).

[0065] The UE may operate in various radio resource configurations, including a configuration associated with sending a pilot using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with sending a pilot using a common resource set (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for sending a pilot signal to the network. When operating in the RRC common state, the UE may select a common resource set for sending a pilot signal to the network. In either case, the pilot signal sent by the UE may be received by one or more network access devices (e.g., an AN or DU or a portion thereof). Each receiving network access device may be configured to receive and measure a pilot signal sent on a common resource set, and also receive and measure a pilot signal sent on a dedicated resource set allocated to a UE, for which the network access device is a member of a monitoring set of the network access device of the UE. One or more receiving network access devices or a CU to which a receiving network access device sends a pilot signal measurement value may use the measurement value to identify a serving cell of the UE, or initiate a change in a serving cell of one or more UEs.

[0066] SRS resource configuration example

[0067] SRS generally refers to a reference signal that can be used for channel quality determination and / or other purposes. In some instances, a UE may send an SRS to and / or for a network entity (e.g., a base station such as an eNodeB / gNodeB) to determine the channel quality of an uplink path of a sub-portion of a frequency band (e.g., a bandwidth portion or BWP). The network entity may use the SRS signal to determine a portion of the system bandwidth to be allocated (e.g., for a specific UE at a specific time). Wideband SRS transmissions may allow the network to determine which portion across the entire bandwidth has better channel quality than other areas. In this case, the network entity may allocate a specific frequency region that best suits each UE.

[0068] like Fig. 7A As shown, a UE may be configured with one or more SRS resource sets. Each SRS resource set may be used for a specific purpose, such as antenna switching, beam management, or codebook-based transmission. Each SRS resource set may have a corresponding identifier and / or SRS resource set to be sent by a UE. As shown, multiple SRS resources may be grouped in an SRS resource set depending on the usage (e.g., whether the SRS is used for antenna switching, codebook-based, non-codebook-based, and / or beam management).

[0069] SRS information can be sent in a variety of ways. For example, SRS resource sets can be sent aperiodically, semi-persistently, or periodically. For aperiodic transmission, the UE can be triggered to dynamically send SRS resource sets, for example, via downlink control information (DCI). For periodic transmission, the UE can be configured to send SRS resource sets at a given period (different SRS resource sets or SRS resources with SRS resource sets can be sent at different periods). For semi-persistent transmission, the UE can be notified by signal to periodically send SRS resource sets for a duration (for example, until stopped by signal).

[0070] like Figure 7B As shown, for A-SRS transmission, bit information can be used to trigger SRS related indication. As a specific example, 2 bits in DL or UL DCI can be used to trigger the transmission of SRS resource sets. In some instances, each A-SRS resource set can be marked with a value of 1, 2, or 3, corresponding to DCI code points 01, 10, or 11, while DCI code point 00 indicates no A-SRS transmission.

[0071] SRS configuration can be provided in a variety of ways. In some examples, each AP SRS resource set can be configured via radio resource control (RRC) signaling. In this way, RRC signaling can include a slot offset (field slotOffset), which can indicate an integer value from 1 to 32. The slot offset indicates the number of time slots between the triggering DCI and the actual transmission of the SRS-ResourceSet. If the slot offset field does not exist, the UE does not apply an offset (value 0). Once the DCI selects an SRS resource set, the slot offset is fixed. Each SRS resource in the set also has an associated symbol index (startPosition) that contains the first symbol of the SRS resource. SRS resources can span one or more consecutive OFDM symbols.

[0072] Example of A-SRS triggered by DCI without TPC

[0073] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for triggering A-SRS via certain DCI formats, such as lack of power command information (eg, lack of TPC commands).

[0074] As mentioned above, various formats of DCI may trigger A-SRS. For example, DCI format 2_3 may be used to switch UE uplink transmission (UL Tx) from one serving cell to another serving cell. For example, such DCI may switch UE uplink transmission to a cell that is not configured to send UL PUSCH and PUCCH for A-SRS for a specific purpose ("antenna switching").

[0075] DCI format 2_3 is generally used to transmit a set of TPC commands for SRS transmission by one or more UEs. Along with the TPC commands, an SRS request may also be sent. The content of DCI format 2_3 is arranged into multiple blocks: block 1, block 2, ... block B.

[0076] like Fig. 8A and 8B As shown, there are two types of DCI formats 2_3: Type A and Type B.

[0077] With Type-A, the UE is configured with one block. This may apply to a component carrier (CC) set and contain an SRS request (eg, 0, 2 bits) to identify the CC set. N TPC commands may be provided for each CC in the set.

[0078] With Type B, the UE is configured with one or more blocks. Each block applies to one UL carrier and contains an SRS request (0, 2 bits) and a TPC command (2 bits) for determining an SRS resource set.

[0079] Traditionally, there are certain limitations to using DCI formats 2-3. Such limitations include, for example, that SRS triggering is usually limited to "antenna switching" using SRS and CCs that are not configured with PUSCH ("PUSCH-free" CCs).

[0080] Various aspects of the present disclosure provide and implement new DCI (which can be considered as enhanced DCI formats 2-3). This new DCI can achieve flexible SRS triggering for different SRS purposes, which is in contrast to traditional DCI formats 2-3, which are limited to SRS triggering for "Antenna Switching". Ideally, such DCI can achieve cross-carrier SRS triggering (for example, DCI sent on one CC triggers SRS on another CC) even on CCs configured with PUSCH. In some cases, the UL component carrier (CC) can be configured as PUSCH / PUCCH or PUSCH-free. This can help to achieve flexible cross-CC SRS transmission (from UEs supporting UL-CA) with relatively little or no switching time (for example, cross-CC SRS transmission can occur in subsequent time slots that meet the time slot offset of the corresponding SRS resource set).

[0081] Aspects of the present disclosure propose additional enhancements to the multicast DCI (GC-DCI) format design for A-SRS triggering. For example, some formats may enable A-SRS triggering through DCI lacking TPC commands (SRS triggering without TPC).

[0082] Fig. 9 900 is shown as an example operation of a UE performing wireless communications. For example, the operation 900 may be performed by Figure 1 or Figure 4 UE 120 performs to send an A-SRS triggered by a DCI without TPC.

[0083] Operations 900 begin at 902 by receiving downlink control information (DCI) having at least one block configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set. At 904, if the DCI lacks a transmit power control (TPC) command for at least one SRS set, the UE determines a transmit power control (TPC) command to be applied to an A-SRS. At 906, the UE transmits the A-SRS according to the DCI and the determined TPC command.

[0084] Fig.10 shows what can be considered Fig. 9 Example operation 1000 is a supplement to operation 900. For example, operation 1000 may be performed by Figure 1 1 or 4 BS 110 performs to send a DCI without TPC to trigger the A-SRS from the UE (perform Fig. 9 Operation 900).

[0085] Operations 1000 begin at 1002, where downlink control information (DCI) having at least one block is sent to at least one user equipment (UE), the at least one block being configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set. At 1004, a network entity determines whether to include a transmit power control (TPC) command in the DCI for at least one SRS resource set based on one or more conditions. At 1006, the network entity processes an A-SRS sent according to the DCI.

[0086] In some cases, the DCI may be a type B DCI with a configurable block length, allowing blocks without TPC. For CCs with PUSCH, power control for SRS sets with purpose "codebook" may follow PUSCH power control. Thus, if the triggered SRS resource set is for "codebook" purpose, then TPC commands may not need to be indicated.

[0087] Therefore, the DCI may have a type B block with only an "SRS request" field, because if the SRS request triggers a "codebook" SRS resource set for a CC with PUSCH, the TPC command may not be present. On the other hand, for CCs without PUSCH, a TPC command may be provided. In order to skip TPC commands in some blocks, the block length may need to be reconfigured (e.g., via RRC signaling) instead of a fixed block length.

[0088] There are various options for the type of use of the SRS triggered by a block of type B without TPC. According to one option, the SRS request may only trigger the SRS resource set with "codebook" use. As described above, in this case, it may not be necessary to include a TPC command in the block. As a result, the block length may be, for example, only 2 bits, and the UE should only read 2 bits of the block.

[0089] According to another option, the submitted SRS request may trigger SRS resource sets with mixed usage. For example, the SRS request field may trigger two SRS resource sets: one for "codebook" and the other for "antenna switching". In this case, the TPC command in the DCI may only apply to the non-"codebook" set of the CC (i.e., "antenna switching" for the above example). The transmit power of the SRS (UL PRS) used for positioning may be based on open-loop power control. Therefore, in this case, the TPC command may also not exist.

[0090] In some cases, for UEs configured with 2_3 DCI type-B in a block without TPC commands, the latest TPC command from the serving cell can be implicitly indicated to the UE as applicable to the CC. As a special case, the serving cell can also send this TPC before the DCI format 2_3 that triggers A-SRS for the specific purpose of indicating TPC.

[0091] In some cases, a CC may be configured with or without PUSCH. For carrier aggregation (CA) without PUSCH, an implicitly indicated TPC command may be applied to SRS with "antenna switching" purposes. For PUSCH CA, an implicitly indicated TPC command may be applied to a triggered SRS set.

[0092] For intra-band CCs, the path loss of CCs may be very similar. That is why in some cases CCs may share the same TPC command.

[0093] like Fig.11 As shown, in some cases, the new type C DCI format 2_3 can be used to trigger A-SRS with DCI without TPC. Fig.11 In the example shown, if the CC has triggered an SRS set with "codebook" usage, there are various options for the configuration of the TPC field and the corresponding UE behavior.

[0094] For example, in one case, an SRS request may trigger only the set of SRS resources that have "codebook" usage. In this case, according to one option, a variable block size may be used to allow for the absence of TPC commands for that CC. According to another option, a fixed block size may be used (and a dummy value of TPC that the UE ignores may be used).

[0095] In another case, the SRS request field may trigger a set of SRS resources with mixed usage. In this case, the TPC command may be applied to a non-"codebook" set of this CC.

[0096] Aspects of the present disclosure provide a novel DCI design that can implement flexible SRS triggering for different SRS usages. The DCI design can implement cross-CC SRS triggering and simultaneous transmission (eg, for CCs configured with PUSCH).

[0097] Example Embodiments

[0098] Embodiment 1: A method for wireless communication by a user equipment (UE), comprising: receiving downlink control information (DCI) having at least one block, wherein the at least one block is configured to trigger a non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; if the DCI lacks a transmit power control (TPC) command for the at least one SRS set, determining a TPC command to be applied to the A-SRS; and sending the A-SRS according to the DCI and the determined TPC command.

[0099] Embodiment 2: A method according to embodiment 1, wherein the at least one block includes an SRS request field, the SRS request field is configured to trigger SRS transmission on at least one SRS resource set of a component carrier (CC) configured for physical uplink shared channel (PUSCH) transmission, and the determination includes determining to apply a TPC command received for PUSCH transmission when sending A-SRS.

[0100] Embodiment 3: The method according to embodiment 2 also includes receiving radio resource control (RRC) signaling of the block length to reflect the lack of TPC commands.

[0101] Embodiment 4: A method according to any one of embodiments 1-2, wherein the SRS request field triggers an SRS resource set for codebook or positioning purposes.

[0102] Embodiment 5: A method according to Embodiment 4, wherein the at least one block has a variable block size depending on whether a TPC command is included; or the at least one block has a fixed block size regardless of whether a TPC command is included, and if the TPC command is not included, the block includes a value in a TPC command field that is ignored by the UE.

[0103] Embodiment 6: A method according to any one of embodiments 1-5, wherein an SRS request field triggers one or more SRS resource sets with mixed uses.

[0104] Embodiment 7: A method according to Embodiment 6, wherein the DCI lacks a TPC command for a first SRS set in an SRS set for a first purpose; and the DCI includes a TPC command for a second SRS set in an SRS set for a second purpose.

[0105] Embodiment 8: A method according to embodiment 7, wherein the first purpose includes a codebook or positioning; and the second purpose includes antenna switching.

[0106] Embodiment 9: A method according to any one of embodiments 1-8, wherein the at least one block includes an SRS request field, which SRS request field does not trigger a TPC command for A-SRS on a component carrier (CC); and the determination includes determining to apply a TPC command previously received from a serving cell when sending A-SRS on the CC.

[0107] Embodiment 10: According to the method described in Embodiment 9, the method further includes receiving a TPC command specifically applied to A-SRS triggered by DCI.

[0108] Embodiment 11: A method according to any one of embodiments 1-10, wherein, if the CC is not configured for physical uplink shared channel (PUSCH) transmission, the previously received TPC command is applied to the A-SRS sent on the SRS set for antenna switching purposes; or if the CC is configured for PUSCH transmission, the previously received TPC command is applied to the A-SRS sent on one or more SRS sets triggered by the SRS.

[0109] Embodiment 12: A method for a network entity to perform wireless communications, comprising: sending downlink control information (DCI) having at least one block to at least one user equipment (UE), wherein the at least one block is configured to trigger non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; determining whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions; and processing an A-SRS sent according to the DCI.

[0110] Embodiment 13: A method according to embodiment 12, wherein the one or more conditions include: the at least one block includes an SRS request field, which triggers SRS transmission on at least one SRS resource set of a component carrier (CC) configured for a physical uplink shared channel (PUSCH) transmission, and when sending A-SRS, the UE applies a TPC command received for PUSCH transmission.

[0111] Embodiment 14: The method according to embodiment 13 also includes sending block-length radio resource control (RRC) signaling to reflect the lack of TPC commands.

[0112] Embodiment 15: A method according to any one of embodiments 13-14, wherein the one or more conditions further include an SRS request field triggering an SRS resource set for codebook or positioning purposes.

[0113] Embodiment 16: A method according to embodiment 15, wherein the at least one block has a variable block size depending on whether a TPC command is included; or the at least one block has a fixed block size regardless of whether a TPC command is included, and if the TPC command is not included, the block includes a value in a TPC command field that is ignored by the UE.

[0114] Embodiment 17: A method according to any one of embodiments 12-16, wherein the SRS request field triggers one or more SRS resource sets with mixed uses.

[0115] Embodiment 18: A method according to Embodiment 17, wherein the DCI lacks a TPC command for a first SRS set in an SRS set for a first purpose; and the DCI includes a TPC command for a second SRS set in an SRS set for a second purpose.

[0116] Embodiment 19: A method according to embodiment 18, wherein the first use includes codebook or positioning; and the second use includes antenna switching.

[0117] Embodiment 20: A method according to any one of embodiments 12-19, wherein the at least one block includes an SRS request field, which SRS request field does not trigger a TPC command for A-SRS on a component carrier (CC); and when sending A-SRS on the CC, the UE applies a TPC command previously received from a serving cell.

[0118] Embodiment 21: According to the method described in Embodiment 20, the method further includes sending a TPC command specifically applied to A-SRS triggered by DCI.

[0119] Embodiment 22: A method according to any one of embodiments 12-21, wherein, if the CC is not configured for physical uplink shared channel (PUSCH) transmission, the previously sent TPC command will be applied to the A-SRS sent on the SRS set for antenna switching purposes; or if the CC is configured for PUSCH transmission, the previously sent TPC command will be applied to the A-SRS sent on one or more SRS sets triggered by the SRS.

[0120] Embodiment 23: An apparatus for wireless communication by a user equipment (UE), comprising: a component for receiving downlink control information (DCI) having at least one block, wherein the at least one block is configured to trigger non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; a component for determining a transmit power control (TPC) command to be applied to A-SRS if the DCI lacks a TPC command for the at least one SRS set; and a component for sending A-SRS based on the DCI and the determined TPC command.

[0121] Embodiment 24: An apparatus for wireless communication by a network entity, comprising: a component for sending downlink control information (DCI) having at least one block to at least one user equipment (UE), wherein the at least one block is configured to trigger non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; a component for deciding whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions; and a component for processing an A-SRS sent according to the DCI.

[0122] Embodiment 25: An apparatus for wireless communication by a user equipment (UE), comprising: a receiver configured to receive downlink control information (DCI) having at least one block, wherein the at least one block is configured to trigger non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; at least one processor configured to determine a transmit power control (TPC) command to be applied to an A-SRS if the DCI lacks a TPC command for at least one SRS set; and a transmitter configured to send an A-SRS based on the DCI and the determined TPC.

[0123] Embodiment 26: An apparatus for wireless communication by a network entity, comprising: a transmitter configured to send downlink control information (DCI) having at least one block to at least one user equipment (UE), wherein the at least one block is configured to trigger non-periodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; and at least one processor configured to determine whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions, and to process an A-SRS sent according to the DCI.

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

[0125] 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. For 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 multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, c).

[0126] 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, etc. In addition, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determining" may include resolving, selecting, choosing, establishing, etc.

[0127] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. It will be readily apparent to those skilled in the art that various modifications to these aspects are to be made, and the general principles defined herein may be applicable to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein, unless otherwise stated, the elements in the singular form are not intended to represent "one and only one", but to represent "one or more". Unless otherwise specified, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described in this disclosure known or to be known by a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. According to the provisions of 35 USC112 (f), no claim element shall be interpreted unless the element is explicitly described using the phrase "a component for...", or in the case of a method claim, the element is described using the phrase "a step for...".

[0128] The various operations of the above methods may be performed by any suitable means capable of performing the corresponding functions. The means 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 operations are illustrated in a figure, those operations may have corresponding components with similarly numbered corresponding parts-plus-functions. For example, Fig. 9 and 10 The various operations shown can be performed by Figure 4 More specifically, Fig.10 The operation 1000 can be performed by Figure 4 The processors 420, 460, 438 and / or the controller / processor 440 of the BS 110 are shown to execute, and Fig. 9 The operations 900 may be performed by one or more of the processors 466 , 458 , 464 and / or the controller / processor 480 of the UE 120 .

[0129] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed by 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 alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0130] 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 of the processing system and the overall design constraints, the bus may include any number of interconnecting buses and bridges. The bus may link various circuits together, 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 equipment 120 (see Figure 1), a user interface (e.g., keyboard, 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, etc., which are well known in the art and are not described further. The processor may be implemented using one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how to best implement the described functionality of the processing system depending on the specific application and the overall design constraints imposed on the entire system.

[0131] If implemented in software, the functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Software should be broadly interpreted as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include computer storage media and communication media, including any media that facilitates 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 information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. For example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium on which instructions separated from a wireless node are stored, all of which may be accessed by the processor through a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as in the case of a cache and / or a general register file. For 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 included in a computer program product.

[0132] A software module may include a single instruction or multiple instructions and may be distributed over several different code segments, different programs, and multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device or may be distributed over multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard disk into a RAM. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. Then, one or more cache lines may be loaded into a general register file for execution by the processor. When the functions of a software module are mentioned below, it will be understood that such functions are implemented by the processor when executing instructions from the software module.

[0133] In addition, any connection is properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Optical disks, where magnetic disks typically reproduce data magnetically, and optical disks 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.

[0134] 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, the instructions being executable by one or more processors to perform the operations described herein. For example, a computer program product for performing the operations described herein and Fig. 9 and 10 The operations shown in the instructions.

[0135] In addition, it should be understood that the modules and / or other appropriate components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or a base station. For example, such a device can be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein can be provided by a storage component (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that the user terminal and / or the base station can obtain the various methods when the storage component is coupled or provided to the device. In addition, any other suitable technology for providing the methods and techniques described herein to the device can be utilized.

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

Claims

1. A method for wireless communication by a user equipment UE, comprising: receiving downlink control information (DCI) having at least one block, the at least one block being configured to trigger an aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; receiving radio resource control (RRC) signaling of a block length of the at least one block to reflect the absence of a transmit power control (TPC) command for the at least one SRS resource set in the DCI; If the DCI lacks a TPC command for the at least one SRS resource set, determining a TPC command to be applied to an aperiodic SRS; and The aperiodic SRS is sent according to the DCI and the determined TPC command.

2. The method according to claim 1, wherein: The at least one block comprises an SRS request field configured to trigger SRS transmission on at least one SRS resource set of a component carrier CC configured for a physical uplink shared channel PUSCH transmission; and The determining includes determining to apply a TPC command received for a PUSCH transmission when transmitting an aperiodic SRS.

3. The method according to claim 2, in, The SRS request field triggers an SRS resource set for codebook or positioning purposes.

4. The method according to claim 3, wherein: The at least one block has a variable block size depending on whether a TPC command is included; or The at least one block has a fixed block size regardless of whether a TPC command is included, and if no TPC command is included, the block includes a value in a TPC command field that is ignored by the UE.

5. The method according to claim 2, in, The SRS request field triggers one or more SRS resource sets with mixed usage.

6. The method according to claim 5, wherein: The DCI lacks a TPC command for a first SRS resource set of the SRS resource sets for the first usage; and The DCI includes a TPC command for a second SRS resource set among the SRS resource sets for the second usage.

7. The method according to claim 6, wherein: The first use includes codebook or positioning; and A second use involves antenna switching.

8. The method according to claim 1, wherein: The at least one block includes an SRS request field, the SRS request field not having a TPC command triggering an aperiodic SRS on the component carrier CC; and The determining includes determining to apply a TPC command previously received from a serving cell when transmitting an aperiodic SRS on a CC.

9. The method of claim 8, further comprising receiving a TPC command specifically applied to aperiodic SRS triggered by DCI.

10. The method according to claim 8, wherein: If the CC is not configured for physical uplink shared channel (PUSCH) transmission, the previously received TPC command is applied to the aperiodic SRS sent on the SRS resource set for antenna switching purposes; or If the CC is configured for PUSCH transmission, the previously received TPC command is applied to the aperiodic SRS sent on one or more SRS resource sets triggered by the SRS.

11. A method for wireless communication by a network entity, comprising: Sending downlink control information DCI having at least one block to at least one user equipment UE, wherein the at least one block is configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal SRS resource set; determining whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions; sending radio resource control (RRC) signaling of a block length of the at least one block to the at least one UE to reflect the absence of a TPC command for the at least one SRS resource set in the DCI; and Processing the aperiodic SRS transmitted according to the DCI.

12. The method according to claim 11, wherein: The one or more conditions include: the at least one block includes an SRS request field, the SRS request field triggering SRS transmission on at least one SRS resource set of a component carrier CC configured for a physical uplink shared channel PUSCH transmission; and When sending aperiodic SRS, the UE applies the TPC command received for the PUSCH transmission.

13. The method according to claim 12, in, The one or more conditions also include: the SRS request field triggers an SRS resource set for codebook or positioning purposes.

14. The method according to claim 13, wherein: The at least one block has a variable block size depending on whether a TPC command is included; or The at least one block has a fixed block size regardless of whether a TPC command is included, and if no TPC command is included, the block includes a value in a TPC command field that is ignored by the UE.

15. The method according to claim 12, in, The SRS request field triggers one or more SRS resource sets with mixed usage.

16. The method according to claim 15, wherein: The DCI lacks a TPC command for a first SRS resource set of the SRS resource sets for the first usage; and The DCI includes a TPC command for a second SRS resource set among the SRS resource sets for the second usage.

17. The method according to claim 16, wherein: The first use includes codebook or positioning; and A second use involves antenna switching.

18. The method of claim 11, wherein: The at least one block includes an SRS request field, the SRS request field not having a TPC command triggering an aperiodic SRS on the component carrier CC; and When sending aperiodic SRS on a CC, the UE applies the TPC command previously received from the serving cell.

19. The method of claim 18, further comprising sending a TPC command specifically applied to aperiodic SRS triggered by DCI.

20. The method of claim 18, wherein: If the CC is not configured for physical uplink shared channel (PUSCH) transmission, the previously sent TPC command shall be applied to the aperiodic SRS sent on the SRS resource set for antenna switching purposes; or If the CC is configured for PUSCH transmission, the previously sent TPC command will be applied to the aperiodic SRS sent on one or more SRS resource sets triggered by SRS.

21. An apparatus for wireless communication by a user equipment UE, comprising: means for receiving downlink control information (DCI) having at least one block, the at least one block being configured to trigger an aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set; means for receiving radio resource control (RRC) signaling of a block length of the at least one block to reflect the absence of a transmit power control (TPC) command for the at least one SRS resource set in the DCI; means for determining a TPC command to be applied to an aperiodic SRS if the DCI lacks a TPC command for the at least one SRS resource set; and means for transmitting the aperiodic SRS according to the DCI and the determined TPC command.

22. An apparatus for wireless communication by a network entity, comprising: means for sending downlink control information DCI having at least one block to at least one user equipment UE, the at least one block being configured to trigger an aperiodic SRS transmission from the UE on at least one sounding reference signal SRS resource set; means for deciding whether to include a transmit power control (TPC) command in the DCI for the at least one SRS resource set based on one or more conditions; means for sending radio resource control (RRC) signaling of a block length of the at least one block to the at least one UE to reflect the absence of a TPC command for the at least one SRS resource set in the DCI; and Means for processing aperiodic SRS transmitted according to DCI.

23. An apparatus for wireless communication by a user equipment UE, comprising: A receiver configured to receive downlink control information (DCI) having at least one block, the at least one block being configured to trigger an aperiodic SRS transmission from the UE on at least one sounding reference signal (SRS) resource set ； and receiving radio resource control RRC signaling of a block length of the at least one block to reflect the absence of a transmit power control TPC command for the at least one SRS resource set in the DCI; at least one processor configured to determine a TPC command to be applied to an aperiodic SRS if the DCI lacks a TPC command for the at least one SRS resource set; and The transmitter is configured to transmit the aperiodic SRS according to the DCI and the determined TPC command.

24. An apparatus for wireless communication by a network entity, comprising: A transmitter configured to send downlink control information DCI having at least one block to at least one user equipment UE, wherein the at least one block is configured to trigger aperiodic SRS transmission from the UE on at least one sounding reference signal SRS resource set ； and sending radio resource control (RRC) signaling of a block length of the at least one block to the at least one UE to reflect the absence of a TPC command for the at least one SRS resource set in the DCI; and At least one processor is configured to decide whether to include a transmit power control TPC command in a DCI for the at least one SRS resource set based on one or more conditions, and process an aperiodic SRS sent according to the DCI.

25. A computer program product comprising a computer readable medium having instructions stored thereon, the instructions being executable by one or more processors to perform the method of any one of claims 1-10.

26. A computer program product comprising a computer readable medium having instructions stored thereon, the instructions being executable by one or more processors to perform the method of any one of claims 11-20.

Images