Techniques for PUSCH scheduling in wireless communication system

Abstract

In one aspect, the disclosure includes a method, an apparatus, and a computer readable medium for wireless communication at a user equipment (UE) to: receive a downlink control indicator (DCI) from a network entity; and configuring at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include a scheduling request indicator (SRI) field.

Description

[0001] This application is a divisional application of the application with the filing date of November 14, 2020, application number 202080078005.X (international application number PCT / US2020 / 060622), and title "Techniques for PUSCH Scheduling in a Wireless Communication System".

[0002] Cross - reference to Related Applications

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 936,299, entitled "TECHNIQUES FOR PUSCH SCHEDULING IN A WIRELESS COMMUNICATION SYSTEM", filed on November 15, 2019, and U.S. Patent Application No. 17 / 097,952, entitled "TECHNIQUES FOR PUSCH SCHEDULING IN A WIRELESS COMMUNICATION SYSTEM", filed on November 13, 2020, both of which have been assigned to the assignee of this application and are hereby incorporated by reference in their entirety. Background

[0005] The present disclosure generally relates to communication systems, and more particularly to physical uplink shared channel (PUSCH) scheduling in fifth - generation new radio (5G NR).

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple - access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such 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.

[0007] 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 urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvement in 5G NR technology. These improvements can also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0008] Due to the growing demand for wireless communication, it is desirable to improve the efficiency of wireless communication network technology. Overview

[0010] A brief overview of one or more aspects is given below to provide a basic understanding of such aspects. This overview is not an exhaustive survey of all contemplated aspects and is neither intended to identify critical or decisive elements of all aspects nor to delimit 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 the more detailed description that follows.

[0011] One example implementation includes a method of wireless communication that includes: receiving, by a user equipment (UE), a downlink control indicator (DCI) from a network entity; and configuring, by the UE, at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include a scheduling request indicator (SRI) field.

[0012] Another example implementation includes a device for wireless communication that includes a processor and a memory in communication with the processor. The memory stores instructions that, when executed by the processor, cause the processor to: receive, by the UE, a DCI from a network entity; and configure, by the UE, at least one PUSCH transmission based on determining that the DCI does not include the SRI field.

[0013] Another example implementation includes a device for wireless communication that includes means for: receiving, by the UE, a DCI from a network entity; and configuring, by the UE, at least one PUSCH transmission based on determining that the DCI does not include the SRI field.

[0014] Another example implementation includes a non-transitory computer-readable medium storing instructions for wireless communication, the instructions executable by a processor to: receive DCI from a network entity by a UE; and configure at least one PUSCH transmission by the UE based on determining that the DCI does not include the SRI field.

[0015] To achieve the foregoing and related purposes, one or more aspects include the features that are fully described hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Brief Description of the Drawings

[0017] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network in accordance with various aspects of the present disclosure.

[0018] Figure 2A 、 2B Figures 2C and 2D are diagrams respectively illustrating 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 in accordance with various aspects of the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network in accordance with various aspects of the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of communication signaling between a UE and a base station in accordance with various aspects of the present disclosure.

[0021] Figure 5 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure, and more particularly a flowchart of a method of scheduling at least one PUSCH transmission based on DCI.

[0022] Figure 6 is a block diagram illustrating an example of a UE in accordance with various aspects of the present disclosure.

[0023] Figure 7 is a block diagram illustrating an example of a base station in accordance with various aspects of the present disclosure. Detailed Description

[0025] The following detailed description, presented in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0026] Certain aspects of a telecommunications system will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0027] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes 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, system on a chip (SoC), 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 the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software can be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or other terms.

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

[0029] Figure 1 FIG. is an illustration of an example of a wireless communication system and access network 100 configured to select resources in a resource selection window. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)).

[0030] In some aspects, the UE 104 may be configured to operate a communication component 198 and / or a configuration component 240 to determine resources for transmitting a physical uplink shared channel (PUSCH) transmission to a network entity based on downlink control information (DCI). For example, the communication component 198 and / or the configuration component 240 may be configured to: receive DCI from a network entity; determine whether the DCI includes a scheduling request indicator (SRI) field; and transmit at least one PUSCH transmission on the resources based on determining that the DCI does not include the SRI field.

[0031] Accordingly, in some aspects, the network entity 102 (e.g., a base station) may be configured to operate a communication component 199 and / or a configuration component 241 to transmit DCI to the UE 104. For example, the communication component 199 and / or the configuration component 241 may determine whether to include an SRI field in the DCI to be transmitted to the UE 104. The communication component 199 and / or the configuration component 241 may receive a scheduled PUSCH transmission from the UE 104 in response to transmitting the DCI.

[0032] The base station 102 may include a macro cell (high-power cellular base station) and / or a small cell (low-power cellular base station). The macro cell includes a base station. The small cell includes a femto cell, a pico cell, and a micro cell.

[0033] The base stations 102 configured for 4G LTE (collectively, 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., S1 interface). The base stations 102 configured for 5G NR (collectively, Next Generation RAN (NG-RAN)) can interface with the core network 190 via a backhaul link 184. In addition to other functions, the base stations 102 can also perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, 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), subscriber and equipment tracing, Radio Access Network Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 can communicate with each other directly or indirectly (e.g., via the EPC 160 or the core network 190) via a backhaul link 134 (e.g., X2 interface). The backhaul links 132, 134, and 184 can be wired or wireless.

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

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

[0036] The wireless communication system may further 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 communication to determine whether the channel is available.

[0037] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0038] Regardless of whether it is the small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a g Node B (gNB), or another type of base station. Some base stations (such as the gNB 180) may operate in the traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. The extremely high frequency (EHF) is a part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. The radio waves in this frequency band may be referred to as millimeter waves. Near mmW may extend down to 3 GHz frequencies with a 100 millimeter wavelength. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communication using the mmW / near mmW radio frequency band (e.g., 3 GHz–300 GHz) has extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.

[0039] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmission directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more reception directions 182”. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmission directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more reception directions. The base station 180 / UE 104 may perform beam training to determine the best reception direction and transmission direction for each of the base station 180 / UE 104. The transmission direction and reception direction of the base station 180 may be the same or may be different. The transmission direction and reception direction of the UE 104 may be the same or may be different.

[0040] 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 processes signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All User Internet Protocol (IP) packets are routed through the Serving Gateway 166, which is itself 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 functions 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 within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0041] 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 processes signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All User Internet Protocol (IP) packets are routed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services.

[0042] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), or some other suitable term. Base station 102 provides an access point for UE 104 to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, fuel pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0043] Figures 2A - 2D A diagram including example frame structures and resources that may be utilized in the communication between base station 102, UE 104, and / or secondary UE (or sidelink UE) 110 described in this disclosure. Figure 2A It is a diagram 200 illustrating an example of a first subframe within the 5G / NR frame structure. Figure 2B It is a diagram 230 illustrating an example of a DL channel within a 5G / NR subframe. Figure 2C It is a diagram 250 illustrating an example of a second subframe within the 5G / NR frame structure. Figure 2D It is a diagram 280 illustrating an example of a UL channel within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a specific subcarrier set (carrier system bandwidth), the subframes within that subcarrier set are dedicated to DL or UL; or it may be TDD, where for a specific subcarrier set (carrier system bandwidth), the subframes within that subcarrier set are dedicated to both DL and UL. In Figure 2A 、 2CIn the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can be configured with any one of the various available slot formats 0 - 61. Slot formats 0 and 1 are all - DL and all - UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by the received slot format indicator (SFI) (configured dynamically via downlink control information (DCI), or semi - statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G / NR frame structure that is TDD.

[0044] Other wireless communication technologies may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini - slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, while for slot configuration 1, each slot may include 7 symbols. The symbols on the DL can be cyclic prefix (CP) OFDM (CP - OFDM) symbols. The symbols on the UL can 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 slots within a subframe is based on the slot configuration and numerology. For slot configuration 0, different numerologies μ from 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe respectively. For slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per subframe respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2 μ slots per subframe. The sub - carrier spacing and symbol length / duration are dependent on the numerology. The sub - carrier spacing can be equal to 2 μ *15 kHz, where μ is the numerology from 0 to 5. Thus, numerology μ = 0 has a sub - carrier spacing of 15 kHz, while numerology μ = 5 has a sub - carrier spacing of 480 kHz. The symbol length / duration is inversely related to the sub - carrier spacing. Figures 2A - 2D An example is provided with slot configuration 0 having 14 symbols per slot and numerology μ = 0 and 1 slot per subframe. The sub - carrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.

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

[0046] As Figure 2A explained, some REs carry reference (pilot) signals (RSs) for the UE. The RSs can include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs can also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0047] Figure 2B Examples of various DL channels within a subframe of the explained frame are given. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including 9 resource element groups (REGs), each REG including 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) can be in symbol 2 of a particular subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) can be in symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity 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 the number of RBs in the system bandwidth, as well as the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as system information blocks (SIBs)), and paging messages.

[0048] As Figure 2CAs explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the particular PUCCH format used. Although not shown, the UE may transmit sounding reference signals (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0049] Figure 2D Examples of various UL channels within a subframe of an illustrative frame. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0050] Figure 3It is a block diagram of a base station 310 in communication with a UE 350 in an access network, where the base station 310 can be an example implementation of the base station 102, and where the UE 350 can be an example implementation of the UE 104. In the DL, IP packets from the EPC 160 can be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes the radio resource control (RRC) layer, and layer 2 includes the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast 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 reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0051] The transmit (TX) processor 316 and the receive (RX) processor 370 implement the layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel status feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX modulates an RF carrier with the corresponding spatial stream for transmission.

[0052] At the UE 350, each receiver 354RX receives signals via its corresponding 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 the layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310, as well as the reference signals. These soft decisions may be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by the base station 310 on the physical channel. These data and control signals are then provided to the controller / processor 359 that implements layer 3 and layer 2 functionality.

[0053] The controller / processor 359 may be associated with a memory 360 that stores program code 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 channels and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0054] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0055] Channel estimates derived by the channel estimator 358 from reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0056] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318RX receives signals via its respective corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0057] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between the transport channel and the logical channel, packet reassembly, deciphering, header decompression, and 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 using the ACK and / or NACK protocols to support HARQ operations.

[0058] At least one of the TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 the communication component 198.

[0059] At least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects associated with Figure 1 the communication component 199.

[0060] Referring to Figures 4 - 7 , the features described generally relate to a physical uplink shared channel (PUSCH) scheduled by DCI format 0_1 with or without a scheduling (e.g., SRS) request indicator (SRI) field. The SRS is an uplink reference signal transmitted by the UE 104 to the base station 102. The SRS gives information about the combined effects of multipath fading, scattering, Doppler, and power loss of the transmitted signal.

[0061] For example, when PUSCH transmission is scheduled by DCI format 0_1, subsequently if only a single resource is included in the SRS resource set for codebook or non-codebook use, the DCI may not have an SRI field. The codebook corresponds to a matrix with complex-valued elements that transform data bits (PDSCH) into another data set mapped to each antenna port.

[0062] Examples of codebook-based PUSCH transmissions include UEs such as Figure 1UE 104) transmits one or two SRS resources (e.g., one SRS resource has 1, 2, or 4 ports). In response, a base station (such as base station 102) may indicate an SRI, a transmitted precoding matrix indicator (TPMI), and a transmission rank indicator (TRI) (e.g., a precoding matrix of UE 104 from a precoder codebook and rank). Subsequently, UE 104 performs a PUSCH transmission. Examples of non-codebook based PUSCH transmissions include CSI-RS, which is indicated to UE 104 to assist in calculating the uplink precoder (e.g., using downlink-uplink reciprocity). UE 104 may transmit up to four SRS resources, where each of the SRS resources is a single port and corresponds to a PUSCH layer. Base station 102 indicates a plurality of SRIs and the number of SRIs (i.e., the rank), and then UE 104 performs a PUSCH transmission.

[0063] In this example, the path loss RS for PUSCH transmission corresponds to the configured path loss reference signal (RS) with ID 0, which is configured semi-statically by RRC and cannot be updated dynamically (e.g., when the transmission beam of the SRS resource is updated).

[0064] Accordingly, the present disclosure generally relates to the current problem of efficient resource allocation for uplink transmissions. The resource allocation problem can be caused by the scheduling of PUSCH using DCI format 0_1 which has no SRI field if there is only one SRS resource in the set of SRS resources for codebook or non-codebook use. For example, in one aspect, the present disclosure includes a method, apparatus, and non-transitory computer-readable medium for wireless communication, which are configured to: receive, by a UE, DCI from a network entity; determine, by the UE, whether the DCI includes an SRI field; and transmit, by the UE, at least one PUSCH transmission on a resource based on determining that the DCI does not include the SRI field.

[0065] Figure 4FIG. is a diagram illustrating an example of communication signaling between a UE and a base station according to various aspects of the present disclosure. The UE may correspond to UE 104 and include apparatus 350; a controller / processor 359 (which may include a memory 360), processors 512 (which may include a memory 516, a modem 540), and they may be the entire UE 104 or components of UE 104 (such as a TX processor 368, an RX processor 356, and / or a transceiver 502)) in combination with communication component 198 / configuration component 240. Similarly, the base station may correspond to base station 102 and include apparatus 310; a controller / processor 375 (which may include a memory 376), processors 712 (which may include a memory 716, a modem 740), and they may be the entire base station 102 or components of base station 102 (such as a TX processor 316, an RX processor 370, and / or a transceiver 702)) in combination with communication component 199 / configuration component 241.

[0066] In one aspect, at step 402, base station 102 may transmit a downlink control indicator (DCI). In response to receiving the DCI, at 404, UE 104 may determine whether the DCI includes a scheduling request indicator (SRI) field; and at 406, UE 104 may transmit at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include the SRI field. At 408, UE104 may send the PUSCH transmission to base station 102.

[0067] In one aspect, if a grant-based or grant-free PUSCH transmission is scheduled and / or activated by a DCI format 0_1 that does not include an SRI field, the RS resource index corresponding to the PUSCH-path loss reference RS-Id (corresponding to Id and the associated downlink RS for the path loss configured in the serving cell indicated by "cell" in the "PUCCH-spatial relation information" configuration) mapped to sri-PUSCH-power control Id = X is used for path loss measurement of the PUSCH transmission. The SRI-PUSCH-power control may provide a mapping between the SRI and PUSCH power control parameters (e.g., the mapping may refer to a parameter / index that is configured in the "cell" field of the spatial relation information indicated by the indicated "SRS-resource" configuration in the serving cell) and is configured to have an sri-PUSCH-power control Id = X, where X is a fixed ID, such as 0.

[0068] In one aspect, if a PUSCH transmission is scheduled and / or activated by DCI format 0_1 that does not include an SRI field based on grant or no-grant, the path loss (PL) RS for the PUSCH transmission will be used as the DL RS for QCL RS for DL signals (e.g., PDCCH or PDSCH). Additionally, a new PL RS can be used after X samples of DCI messages are received to stabilize the use of the filtered RS, otherwise the old PL RS can still be used by UE 104 for scheduling PUSCH transmissions. For example, a QCL-Type D (e.g., spatial reception (Rx) parameter) RS can define a default transmission configuration indicator (TCI) state (e.g., the TCI state is dynamically sent in a DCI message that includes a configuration such as the QCL relationship between the downlink RS in a CSI-RS set and the PDSCH DMRS ports) or a QCL assumption for the PDSCH (e.g., the TCI state is configured as one of QCL-Type A - D, and the TCI state defines the QCL assumption between the source RS and the target RS).

[0069] In another example, if a control resource set (CORESET) is configured on a component carrier (CC), the PL RS can be configured as the QCL RS for a CORESET on that CC. The CORESET can be selected from a CORESET with the lowest or highest CORESET ID or a CORESET with the lowest CORESET ID in the most recently monitored time slot. If the CORESET has a configured TCI state, then UE 104 uses that TCI state to define the QCL assumption between the source RS and the target RS. UE 104 can utilize the TCI state and the corresponding QCL assumption based on measurements performed on the QCLed CSI-RS as indicated on the TCI state to determine the PDSCH beam.

[0070] Specifically, if the CORESET has a configured TCI state, then if only a single RS is in that TCI state, the UE 104 may configure the QCL RS to correspond to a QCL-Type A (e.g., Doppler shift, Doppler spread, average delay, delay spread) RS, or if two RSs are in that TCI state, configure the QCL RS to correspond to a QCL-Type D RS. If the CORESET has no configured TCI state, the QCL RS is a QCL-Type D RS. If the CORESET is not configured on a CC, the PL RS is a QCL RS of one of the active TCI states for the PDSCH on that CC. This one active TCI state may have the lowest or highest TCI state ID. If only one RS is in that TCI state, the QCL RS may correspond to a QCL-Type A RS, or if two RSs are in that TCI state, the QCL RS may correspond to a QCL-Type D RS.

[0071] In one aspect, if a grant or non-grant based PUSCH transmission is scheduled and / or activated by DCI format 0_1 that does not include an SRI field, the PL RS for the SRS resource set is used, where the SRS resource set contains a single SRS for use with a codebook or non-codebook associated with the PUSCH transmission. For example, the UE 104 may configure the PL RS of the associated SRS resource set to be used as the PL RS for the scheduled PUSCH transmission. In this example, the mapping between the PL RS and the SRS resource set may be updated by a MAC-CE. The UE 104 may perform antenna switching in various ways depending on the RRC parameter settings in the SRS resource set. In the case where the PL RS is configured by a MAC-CE received by the UE 104, the mapping between the PL RS and the SRS resource set may be updated.

[0072] Figure 5 is a flowchart 500 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 350; controller / processor 359 (which may include memory 360), (one or more) processors 612 (which may include memory 616, modem 640), and they may be the entire UE 104 or components of the UE 104 (such as TX processor 368, RX processor 356, and / or transceiver 602)) in conjunction with communication component 198 / configuration component 240.

[0073] At 502, method 500 includes receiving, by a user equipment (UE), a downlink control indicator (DCI) from a network entity. In one aspect, UE 104 and / or communication component 198 / configuration component 240 may be configured to receive the DCI from the network entity. As such, UE 104 and / or communication component 198 / configuration component 240 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processors 612 (which may include memory 616, modem 640, TX processor 368, and transceiver 602)) may define means for receiving, by the UE, the DCI from the network entity.

[0074] At 504, method 500 includes determining, by the UE, whether the DCI includes a scheduling request indicator (SRI) field. In one aspect, UE 104 and / or communication component 198 / configuration component 240 may be configured to determine whether the DCI includes the SRI field. As such, UE 104 and / or communication component 198 / configuration component 240 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processors 612 (which may include memory 616, modem 640, RX processor 356, and transceiver 602)) may define means for determining, by the UE, whether the DCI includes the SRI field.

[0075] At 506, method 500 includes scheduling, by the UE, at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include the SRI field. In one aspect, UE 104 and / or communication component 198 / configuration component 240 may be configured to schedule at least one PUSCH transmission based on determining that the DCI does not include the SRI field. As such, UE 104 and / or communication component 198 / configuration component 240 (e.g., in conjunction with controller / processor 359 (which may include memory 360), processors 612 (which may include memory 616, modem 640, RX processor 356, and transceiver 602)) may define means for scheduling, by the UE, at least one PUSCH transmission based on determining that the DCI does not include the SRI field.

[0076] Referring Figure 6 , an example implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 612 and memory 616 and transceiver 602 that are in communication via one or more buses 644, which may operate in conjunction with modem 640 and / or configuration component 198 for scheduling PUSCH in NR-U.

[0077] In one aspect, one or more processors 612 may include a modem 640 and / or may be part of a modem 640 that uses one or more modem processors. Accordingly, various functions associated with the communication component 198 may be included in the modem 640 and / or the processor 612, and in one aspect, may be performed by a single processor, while in other aspects, different functions among these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 612 may include any one or any combination of the following: a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receive processor, or a transceiver processor associated with the transceiver 602. In other aspects, some of the features of the one or more processors 612 and / or the modem 640 associated with the communication component 198 may be performed by the transceiver 602.

[0078] Furthermore, the memory 616 may be configured to store data used herein and / or a local version of the application 675, or the communication component 642 and / or one or more of its sub-components executed by at least one processor 612. The memory 616 may include any type of computer-readable medium that can be used by a computer or at least one processor 612, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating at least one processor 612 to execute the communication component 198 and / or one or more of its sub-components, the memory 616 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 198 and / or one or more of its sub-components and / or data associated therewith.

[0079] The transceiver 602 may include at least one receiver 606 and at least one transmitter 608. The receiver 606 may include hardware for receiving data and / or software code executable by a processor, the code including instructions and being stored in a memory (e.g., a computer-readable medium). The receiver 606 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 606 may receive signals transmitted by at least one base station 102. Additionally, the receiver 606 may process such received signals and may also obtain measurements of the signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), and the like. The transmitter 608 may include hardware and / or software executable by a processor for transmitting data, the code including instructions and being stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 608 may include but are not limited to RF transmitters.

[0080] Moreover, on one hand, the UE 104 may include an RF front end 688, which may operate communicatively with one or more antennas 665 and a transceiver 602 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 688 may be connected to one or more antennas 665 and may include one or more low noise amplifiers (LNAs) 690, one or more switches 692, one or more power amplifiers (PAs) 698, and one or more filters 696 for transmitting and receiving RF signals.

[0081] On one hand, the LNA 690 may amplify the received signal to a desired output level. On one hand, each LNA 690 may have specified minimum and maximum gain values. On one hand, the RF front end 688 may use one or more switches 692 to select a particular LNA 690 and its specified gain value based on the desired gain value for a particular application.

[0082] In addition, for example, one or more PAs 698 may be used by the RF front end 688 to amplify the signal to obtain an RF output at a desired output power level. On one hand, each PA 698 may have specified minimum and maximum gain values. On one hand, the RF front end 688 may use one or more switches 692 to select a particular PA 698 and its specified gain value based on the desired gain value for a particular application.

[0083] Additionally, for example, one or more filters 696 may be used by the RF front end 688 to filter the received signal to obtain an input RF signal. Similarly, on one hand, for example, the corresponding filter 696 may be used to filter the output from the corresponding PA 698 to generate an output signal for transmission. On one hand, each filter 696 may be connected to a particular LNA 690 and / or PA 698. On one hand, the RF front end 688 may use one or more switches 692 to select a transmit or receive path using the specified filter 696, LNA 690, and / or PA 698 based on a configuration specified by the transceiver 602 and / or the processor 612.

[0084] Thus, the transceiver 602 may be configured to transmit and receive wireless signals via the RF front end 688 through one or more antennas 665. On one hand, the transceiver may be tuned to operate at a specified frequency such that the UE 104 may communicate, for example, with one or more base stations 102 or one or more cells associated with one or more base stations 102. On one hand, for example, the modem 640 may configure the transceiver 602 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 640.

[0085] In one aspect, the modem 640 can be a multi-band multi-mode modem that can process digital data and communicate with the transceiver 602 to enable the transceiver 602 to transmit and receive digital data. In one aspect, the modem 640 can be multi-band and configured to support multiple frequency bands for a particular communication protocol. In one aspect, the modem 640 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 640 can control one or more components of the UE 104 (e.g., the RF front end 688, the transceiver 602) to implement the transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration can be based on UE configuration information associated with the UE 104, such as provided by the network during cell selection and / or cell reselection.

[0086] In one aspect, the processors 612 can correspond to one or more of the processors described in connection with the UE in Figure 3 Similarly, the memory 616 can correspond to the memory described in connection with the UE in Figure 3

[0087] Referring to Figure 7 , an example implementation of the base station 72 (e.g., the base station 102, as described above) can include various components, some of which have been described above, but also components such as one or more processors 712 and a memory 716 in communication via one or more buses 744, and a transceiver 702, which can operate in conjunction with a modem 740 and a communication component 199 to convey reference signals.

[0088] The transceiver 702, the receiver 706, the transmitter 708, one or more processors 712, the memory 716, the application 775, the bus 744, the RF front end 788, the LNA 790, the switch 792, the filter 796, the PA 798, and one or more antennas 765 can be the same as or similar to the corresponding components of the UE 74 as described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0089] In one aspect, the processors 712 can correspond to one or more of the processors described in connection with the base station in Figure 3 Similarly, the memory 716 can correspond to the memory described in connection with the base station in Figure 3

[0090] Some further example clauses

[0091] The following numbered clauses describe various implementation examples:

[0092] 1. A method for wireless communication at a user equipment (UE), comprising:

[0093] Receiving a downlink control indicator (DCI) from a network entity; and

[0094] Configuring at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include a scheduling request indicator (SRI) field.

[0095] 2. The method of clause 1, wherein configuring the at least one PUSCH transmission further comprises configuring a reference signal resource index corresponding to a path loss measurement of the PUSCH transmission.

[0096] 3. The method of clauses 1-2, wherein the reference signal resource index corresponds to a PUSCH path loss reference signal mapped to an SRIPUSCH power control identifier.

[0097] 4. The method of clauses 1-3, further comprising configuring the SRIPUSCH power control to have the SRIPUSCH power control identifier.

[0098] 5. The method of clauses 1-4, wherein the PUSCH path loss reference signal corresponds to a PUSCH path loss reference signal; and further comprising:

[0099] Updating the path loss PUSCH path loss reference signal based on a media access control (MAC) control element (CE).

[0100] 6. The method of clauses 1-5, wherein configuring the at least one PUSCH transmission further comprises using a downlink reference signal based on the path loss reference signal of the PUSCH transmission for a downlink signal.

[0101] 7. The method of clauses 1-6, wherein the downlink reference signal corresponds to a quasi co-location (QCL) reference signal.

[0102] 8. The method of clauses 1-7, wherein the downlink signal is associated with at least one of a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).

[0103] 9. The method of clauses 1-8, further comprising:

[0104] Determining whether the number of received samples meets a threshold;

[0105] Replacing the path loss reference signal with a new path loss reference signal to stabilize filtering based on determining that the number of received samples meets the threshold; and

[0106] Continuing to utilize the path loss reference signal based on determining that the number of received samples does not meet the threshold.

[0107] 10. The method of clauses 1-9, wherein the quasi-co-location (QCL) type D reference signal defines the default transmission configuration indication (TCI) state or the QCL assumption of the physical downlink shared channel (PDSCH) associated with the downlink signal.

[0108] 11. The method of clauses 1-10, further comprising:

[0109] Determining whether one or more control resource sets (CORESETs) are configured on the component carrier; and

[0110] Configuring the path loss reference signal as a quasi-co-location (QCL) reference signal for at least one of the one or more CORESETs on the component carrier based on determining that the one or more CORESETs are configured on the component carrier.

[0111] 12. The method of clauses 1-11, further comprising configuring the path loss reference signal as a QCL reference signal for the physical downlink shared channel (PDSCH) on the component carrier in an active transmission configuration indication (TCI) state.

[0112] 13. The method of clauses 1-12, wherein configuring the at least one PUSCH transmission further comprises using the path loss reference signal for a sounding reference signal (SRS) resource set, the sounding reference signal resource set including SRS for use by at least one of a codebook or a non-codebook associated with the at least one PUSCH transmission.

[0113] 14. The method of clauses 1-13, further comprising updating the mapping between the path loss reference signal and the SRS resource set based on a media access control (MAC) control element (CE).

[0114] 15. The method of clauses 1-14, wherein the DCI corresponds to DCI format 0_1.

[0115] 16. An apparatus for wireless communication by a user equipment (UE), comprising:

[0116] A transceiver;

[0117] A memory configured to store instructions; and

[0118] One or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to:

[0119] Receive a downlink control indicator (DCI) from a network entity; and

[0120] Configure at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include the scheduling request indicator (SRI) field.

[0121] 17. The apparatus of clause 16, wherein the one or more processors configured to configure the at least one PUSCH transmission are further configured to configure a reference signal resource index corresponding to path loss measurement for the PUSCH transmission.

[0122] 18. The apparatus of clauses 16 - 17, wherein the reference signal resource index corresponds to a PUSCH path loss reference signal mapped to an SRI PUSCH power control identifier.

[0123] 19. The apparatus of clauses 16 - 18, wherein the one or more processors are configured to configure the SRI PUSCH power control to have the SRI PUSCH power control identifier.

[0124] 20. The apparatus of clauses 16 - 19, wherein the PUSCH path loss reference signal corresponds to a PUSCH path loss reference signal; and wherein the one or more processors are configured to:

[0125] Update the path loss PUSCH path loss reference signal based on a media access control (MAC) control element (CE).

[0126] 21. The apparatus of clauses 16 - 20, wherein the one or more processors configured to configure the at least one PUSCH transmission are further configured to use a downlink reference signal of the path loss reference signal transmitted through the PUSCH for a downlink signal.

[0127] 22. The apparatus of clauses 16 - 21, wherein the downlink reference signal corresponds to a quasi - co - located (QCL) reference signal.

[0128] 23. The apparatus of clauses 16 - 22, wherein the downlink signal is associated with at least one of a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0129] 24. The apparatus of clauses 16 - 23, wherein the one or more processors are configured to:

[0130] Determine whether the number of received samples meets a threshold;

[0131] Based on determining that the number of received samples meets the threshold, replace the path loss reference signal with a new path loss reference signal to stabilize filtering; and

[0132] Based on determining that the number of received samples does not meet the threshold, continue to utilize the path loss reference signal.

[0133] 25. The apparatus according to clauses 16 - 24, wherein the quasi - co - location (QCL) type D reference signal defines the default transmission configuration indicator (TCI) state or the QCL assumption of the physical downlink shared channel (PDSCH) associated with the downlink signal.

[0134] 26. The apparatus according to clauses 16 - 25, wherein the one or more processors are configured to:

[0135] Determine whether one or more control resource sets (CORESETs) are configured on a component carrier; and

[0136] Based on determining that the one or more CORESETs are configured on the component carrier, configure the path loss reference signal as the quasi - co - location (QCL) reference signal for at least one of the one or more CORESETs on the component carrier.

[0137] 27. The apparatus according to clauses 16 - 26, wherein the one or more processors are configured to configure the path loss reference signal as the QCL reference signal for the physical downlink shared channel (PDSCH) on the component carrier in an active transmission configuration indicator (TCI) state.

[0138] 28. The apparatus according to clauses 16 - 27, wherein the one or more processors configured to schedule the at least one PUSCH transmission are further configured to use the path loss reference signal for a sounding reference signal (SRS) resource set, the sounding reference signal resource set including SRS for use by at least one of a codebook or a non - codebook associated with the at least one PUSCH transmission.

[0139] 29. A device for a user equipment (UE) to perform wireless communication, comprising:

[0140] Means for receiving a downlink control indicator (DCI) from a network entity; and

[0141] Means for configuring at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include the scheduling request indicator (SRI) field.

[0142] 30. The apparatus of clause 29 further includes means for performing the method of clauses 1-15.

[0143] 31. A non-transitory computer-readable medium for a user equipment (UE), comprising code executable by one or more processors to:

[0144] receive a downlink control indicator (DCI) from a network entity; and

[0145] configure at least one physical uplink shared channel (PUSCH) transmission based on determining that the DCI does not include the scheduling request indicator (SRI) field.

[0146] 32. The non-transitory computer-readable medium of clause 31 further includes code executable by one or more processors to perform the method of clauses 1-15.

[0147] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example approaches. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in these process / flowcharts can be rearranged. Additionally, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0148] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, where the singular forms of elements are recited unless otherwise stated not to mean "one and only one", but "one or more". The term "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" need not be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term "some / a certain" 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 "any combination of A, B, C, or the like" include any combination of A, B, and / or C, and may include multiple A's, multiple B's, or multiple C's. 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 "any combination of A, B, C, or the like" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as all structural and functional equivalents are hereby expressly incorporated by reference and are intended to be covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The terms "module", "mechanism", "element", "device", etc. may not be substitutes for the term "apparatus". Thus, no claim element should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

Claims

1. A method for wireless communication by a user equipment (UE), comprising: Receiving, by the UE, a downlink control indicator (DCI) from a network entity that does not have a scheduling request indicator (SRI) field; In response to the DCI not having the SRI field, configuring a physical uplink shared channel (PUSCH) path loss reference signal (RS) resource index based on a mapping of the PUSCH path loss RS identifier (ID) to a SRIPUSCH power control ID equal to zero; and Transmitting, via the UE, one or more RSs for path loss measurement for PUSCH transmission based on the configured PUSCH path loss RS resource index.

2. The method according to claim 1, wherein configuring the PUSCH path loss RS resource index comprises configuring the PUSCH path loss RS resource index according to the PUSCH path loss RS ID mapped to the SRIPUSCH power control ID equal to zero.

3. The method according to claim 1, further comprising receiving a media access control (MAC) control element (MAC-CE) to update the mapping between the PUSCH path loss RS ID and the SRIPUSCH power control ID.

4. The method according to claim 1, wherein the DCI is formatted as DCI format 0_1.

5. The method according to claim 1, further comprising using a downlink RS based on the PUSCH transmission for a downlink signal.

6. The method according to claim 1, further comprising using a path loss RS for a sounding reference signal (SRS) resource set, the SRS resource set including SRSs for use in at least one of a codebook or a non-codebook associated with the PUSCH transmission.

7. A user equipment (UE) comprising: A memory storing instructions; A transceiver; And One or more processors communicatively coupled to the memory and the transceiver, the one or more processors being configured to execute the instructions to: Receive, via the transceiver, a downlink control indicator (DCI) from a network entity that does not have a scheduling request indicator (SRI) field; In response to the DCI not having the SRI field, configure a physical uplink shared channel (PUSCH) path loss reference signal (RS) resource index based on a mapping of the PUSCH path loss RS identifier (ID) to a SRIPUSCH power control ID equal to zero; and Transmit, via the transceiver, one or more RSs for path loss measurement for PUSCH transmission based on the configured PUSCH path loss RS resource index.

8. The UE according to claim 7, wherein configuring the PUSCH path loss RS resource index comprises configuring the PUSCH path loss RS resource index according to the PUSCH path loss RS ID mapped to the SRIPUSCH power control ID equal to zero.

9. The UE according to claim 7, wherein the one or more processors are further configured to receive a Medium Access Control (MAC) Control Element (MAC-CE) to update the mapping between the Physical Uplink Shared Channel (PUSCH) path loss Reference Signal (RS) identifier (ID) and the SRIPUSCH power control ID.

10. The UE according to claim 7, wherein the DCI is formatted as DCI format 0_1.

11. The UE according to claim 7, wherein the one or more processors are further configured to use a downlink RS based on the PUSCH transmission for downlink signals.

12. The UE according to claim 7, wherein the one or more processors are further configured to use the path loss RS for a sounding reference signal (SRS) resource set, the SRS resource set including SRS for use in at least one of a codebook or a non-codebook associated with the PUSCH transmission.

13. A User Equipment (UE) comprising: means for receiving a Downlink Control Indicator (DCI) from a network entity, the DCI not having a Scheduling Request Indicator (SRI) field; means for, in response to the DCI not having the SRI field, configuring a PUSCH path loss RS resource index based on a mapping of a Physical Uplink Shared Channel (PUSCH) path loss Reference Signal (RS) identifier (ID) to a SRIPUSCH power control ID equal to zero; and means for transmitting one or more RSs for path loss measurement for PUSCH transmission based on the configured PUSCH path loss RS resource index.

14. The UE according to claim 13, wherein configuring the PUSCH path loss RS resource index comprises configuring the PUSCH path loss RS resource index according to the PUSCH path loss RS ID mapped to the SRIPUSCH power control ID equal to zero.

15. The UE according to claim 13, further comprising means for receiving a Medium Access Control (MAC) Control Element (MAC-CE) to update the mapping between the PUSCH path loss RS ID and the SRIPUSCH power control ID.

16. The UE according to claim 13, wherein the DCI is formatted as DCI format 0_1.

17. The UE according to claim 13, further comprising means for using a downlink RS of the one or more RSs based on the PUSCH transmission for downlink signals.

18. The UE according to claim 13, further comprising means for using the path loss RS for a sounding reference signal (SRS) resource set, the SRS resource set including SRS for use in at least one of a codebook or a non-codebook associated with the PUSCH transmission.

Images