Applying uplink transmission configuration indicator state with downlink reference signal to codebook-based transmission

Abstract

Certain aspects of the present disclosure provide techniques for applying an uplink transmission configuration indicator (TCI) state with a downlink reference signal to a codebook-based physical uplink shared channel (PUSCH) transmission. An example method generally includes receiving signaling of an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission signal from a network entity, determining whether the TCI state has a source downlink reference signal (RS), and deciding how to handle the codebook-based uplink transmission based on the determination.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 125,990, filed on December 17, 2020, which claims the benefit of and priority to U.S. Provisional Application No. 62 / 951,729, filed on December 20, 2019, both of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes.

[0003] background

[0004] public domain

[0005] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for applying uplink transmission configuration indicator (TCI) states with downlink reference signals to codebook-based physical uplink shared channel (PUSCH) transmissions.

[0006] Related technical description

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name a few.

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

[0009] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should also apply to other multiple access technologies and the telecommunication standards that employ them.

[0010] Brief Overview

[0011] 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 disclosure as expressed in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," one will understand how the features of the present disclosure provide advantages, including improved communication between access points and stations in a wireless network.

[0012] Certain aspects of the subject matter described in this disclosure may be implemented in a method for wireless communications performed by a user equipment (UE). The method generally includes receiving, from a network entity, signaling an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission signal. The method generally includes determining whether the TCI state has a source downlink reference signal (RS). The method generally includes deciding, based on the determination, how to handle the codebook-based uplink transmission.

[0013] Certain aspects of the present disclosure provide a method for wireless communications by a network entity. The method generally includes signaling an uplink TCI state for a codebook-based target uplink transmission signal to a UE. The method generally includes determining how the UE handles codebook-based uplink transmissions based on whether the TCI state has a source downlink RS. The method generally includes processing the codebook-based uplink transmission based on the determination.

[0014] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus generally includes at least one processor and a memory coupled to the at least one processor. The memory generally includes code executable by the at least one processor to cause the apparatus to receive signaling of an uplink TCI state for a codebook-based target uplink transmission signal from a network entity. The memory generally includes code executable by the at least one processor to cause the apparatus to determine whether the TCI state has a source downlink RS. The memory generally includes code executable by the at least one processor to cause the apparatus to determine, based on the determination, how to process the codebook-based uplink transmission.

[0015] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus generally includes at least one processor and a memory coupled to the at least one processor. The memory generally includes code executable by the at least one processor to cause the apparatus to: signal an uplink TCI state for a codebook-based target uplink transmission signal to a UE. The memory generally includes code executable by the at least one processor to cause the apparatus to: determine how the UE handles a codebook-based uplink transmission based on whether the TCI state has a source downlink RS. The memory generally includes code executable by the at least one processor to cause the apparatus to: handle the codebook-based uplink transmission based on the determination.

[0016] Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus generally includes means for receiving, from a network entity, signaling an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission signal. The apparatus generally includes means for determining whether the TCI state has a source downlink RS. The apparatus generally includes means for deciding, based on the determination, how to handle the codebook-based uplink transmission.

[0017] Certain aspects of the present disclosure provide an apparatus for wireless communications. The apparatus generally includes means for signaling an uplink TCI state for a codebook-based target uplink transmission signal to a UE. The apparatus generally includes means for determining how the UE handles codebook-based uplink transmissions based on whether the TCI state has a source downlink RS. The apparatus generally includes means for handling the codebook-based uplink transmission based on the determination.

[0018] Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium having computer-executable code stored thereon for wireless communication. The computer-readable medium generally includes code for receiving, from a network entity, signaling an uplink TCI state for a codebook-based target uplink transmission signal. The computer-readable medium generally includes code for determining whether the TCI state has a source downlink RS. The computer-readable medium generally includes code for deciding, based on the determination, how to handle the codebook-based uplink transmission.

[0019] Certain aspects of the present disclosure provide a computer-readable medium having stored thereon computer-executable code for wireless communication. The computer-readable medium generally includes code for signaling, to a UE, an uplink TCI status for a codebook-based target uplink transmission signal. The computer-readable medium generally includes code for determining how the UE handles a codebook-based uplink transmission based on whether the TCI status has a source downlink RS. The computer-readable medium generally includes code for handling the codebook-based uplink transmission based on the determination.

[0020] To accomplish the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of but a few of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0028] Figure 6 Illustrated are examples of frame formats for New Radio (NR) systems, in accordance with certain aspects of the present disclosure.

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

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

[0031] Figure 9 Illustrated are example quasi-co-location (QCL) relationships in accordance with certain aspects of the present disclosure.

[0032] Figure 10 is a call flow diagram illustrating an example of codebook-based UL transmission.

[0033] Figure 11 is a flow diagram illustrating example operations for wireless communications by a user equipment (UE), in accordance with certain aspects of the present disclosure.

[0034] Figure 12 is a flow diagram illustrating example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure.

[0035] Figure 13 is a call flow diagram illustrating an example of codebook-based UL transmission using uplink TCI states.

[0036] Figure 14 is a call flow diagram illustrating an example of codebook-based UL transmission using uplink TCI states.

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

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

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

[0040] Detailed description

[0041] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for applying uplink transmission configuration indicator (TCI) states with downlink reference signals to codebook-based physical uplink shared channel (PUSCH) transmissions.

[0042] The following description provides examples of applying uplink TCI states with downlink reference signals to codebook-based transmissions in a communication system and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of this disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to some examples may be combined in other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using other structures, functionalities, or a combination of structures and functionalities in addition to or in addition to the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be implemented by one or more elements of the claims. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as superior to or preferred over other aspects.

[0043] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

[0044] The techniques described herein can be used for various wireless networks and radio technologies. Although various aspects may be described herein using terms typically associated with 3G, 4G, and / or new radio (e.g., 5G NR) wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations.

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

[0046] NR supports beamforming and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in the DL can support up to 8 transmit antennas (with multi-layer DL transmission of up to 8 streams) and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported using up to 8 serving cells.

[0047] Figure 1 An example wireless communication network 100 (e.g., an NR / 5G network) in which aspects of the present disclosure may be implemented is illustrated. For example, the wireless communication network 100 may include a BS 110 and a UE 120 configured to apply an uplink TCI state with a downlink reference signal to a codebook-based transmission. Figure 1 As shown in FIG, according to aspects of the present disclosure, a BS 110a includes a TCI state manager 112 that handles codebook-based uplink transmissions based on how the UE handles codebook-based uplink transmissions. According to aspects of the present disclosure, a UE 120a includes a TCI state manager 122 that decides how to handle codebook-based uplink transmissions based on whether the TCI state has a source downlink reference signal (RS).

[0048] The wireless communication network 100 may be a NR system (e.g., a 5G NR network). Figure 1 , the wireless communication network 100 may be in communication with a core network 132. The core network 132 may be in communication with one or more base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to herein as BS 110) and / or user equipments (UEs) 120a-y (each also individually referred to herein as UE 120 or collectively referred to herein as UE 120) in the wireless communication network 100 via one or more interfaces.

[0049] A BS may provide communication coverage for a particular geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of mobile BS 110. In some examples, base stations may be interconnected with each other and / or with one or more other base stations or network nodes (not shown) in wireless communication network 100 via various types of backhaul interfaces, such as direct physical connections, wireless connections, virtual networks, or the like using any suitable transport network.

[0050] exist Figure 1In the example shown in FIG, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more cells.

[0051] BS 110 communicates with UEs 120 in wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. Wireless communication network 100 may also include relay stations (e.g., relay station 110r) (also referred to as relays, etc.) that receive transmissions of data and / or other information from upstream stations (e.g., BS 110a or UE 120r) and send transmissions of data and / or other information to downstream stations (e.g., UE 120 or BS 110), or relay transmissions between UEs 120 to facilitate communication between the devices.

[0052] The network controller 130 may be coupled to a set of BSs and provide coordination and control of these BSs (e.g., via backhaul). In various aspects, the network controller 130 may be in communication with a core network 132 (e.g., a 5G core network (5GC)), which provides various network functions such as access and mobility management, session management, user plane functions, policy control functions, authentication server functions, unified data management, application functions, network exposure functions, network repository functions, network slice selection functions, etc.

[0053] Figure 2 Illustrated is an example logical architecture of a distributed radio access network (RAN) 200, which may be Figure 1 2. 5G access node 206 may include an access node controller (ANC) 202. ANC 202 may be a central unit (CU) of distributed RAN 200. A backhaul interface to a next-generation core network (NG-CN) 204 may terminate at ANC 202. A backhaul interface to a neighboring next-generation access node (NG-AN) 210 may terminate at ANC 202. ANC 202 may include one or more transmit / receive points (TRPs) 208 (e.g., cells, BSs, gNBs, etc.).

[0054] The TRP 208 may be a distributed unit (DU). The TRP 208 may be connected to a single ANC (e.g., ANC 202) or to more than one ANC (not illustrated). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP 208 may be connected to more than one ANC. Each TRP 208 may include one or more antenna ports. The TRPs 208 may be configured to serve traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

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

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

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

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

[0059] Figure 3 An example physical architecture of a distributed radio access network (RAN) 300 is illustrated, in accordance with various aspects of the present disclosure. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU 302 can be centrally deployed. C-CU 302 functionality can be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0060] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU 304 can host core network functions locally. The C-RU 304 can have a distributed deployment. The C-RU 304 can be close to the network edge.

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

[0062] Figure 4 Explained (such as Figure 1 ) example components of BS 110 and UE 120, which may be used to implement aspects of the present disclosure.

[0063] 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 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)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, as applicable, and may provide an output symbol stream to the modulators (MODs) in transceivers 432a through 432t. Each modulator may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0064] At UE 120, antennas 452a through 452r may receive downlink signals from base station 110 and may provide received signals to demodulators (DEMODs) within transceivers 454a through 454r, respectively. Each demodulator 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 within transceivers 454a through 454r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

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

[0066] Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0067] The antennas 252, processors 266, 258, 264 and / or controller / processor 280 of the UE 120, and / or the antennas 234, processors 220, 230, 238 and / or controller / processor 240 of the BS 110 may be used to perform the various techniques and methods described herein. Figure 4As shown in FIG. 1 , in accordance with various aspects described herein, the controller / processor 240 of the BS 110a has a TCI state manager 241 that processes codebook-based uplink transmissions according to how the UE processes codebook-based uplink transmissions. Figure 4 As shown in FIG, in accordance with various aspects described herein, the controller / processor 280 of the UE 120a has a TCI state manager 281 that determines how to handle codebook-based uplink transmissions based on whether the TCI state has a source downlink reference signal (RS). Although shown at the controller / processor, other components of the UE 120a and the BS 110a may also be used to perform the operations described herein.

[0068] Figure 5 Illustrated is a diagram 500 showing an example for implementing a communication protocol stack according to various aspects of the present disclosure. The illustrated communication protocol stack 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 illustrates a communication protocol stack including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, these layers of the protocol stack can be implemented as separate software modules, parts of a processor or ASIC, parts of non-colocated devices connected by a communication link, or various combinations thereof. Colocated and non-colocated implementations can be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

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

[0070] The second option 505-b illustrates a unified implementation of the protocol stack, wherein the protocol stack is implemented in a single network access device. In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can each be implemented by an AN. The second option 505-b can be useful, for example, in a femtocell deployment.

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

[0072] NR can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. NR can support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers, often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Modulation symbols can be 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 can depend on the system bandwidth. The minimum resource allocation (so-called resource block (RB)) can be 12 contiguous subcarriers. The system bandwidth can also be divided into subbands. For example, a subband can cover multiple RBs. NR can support a base subcarrier spacing (SCS) of 15 kHz, and other SCSs (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.) can be defined relative to the base SCS.

[0073] Figure 6 is a diagram illustrating an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe may contain a variable number of slots (e.g., 1, 2, 4, 8, 16, ... slots), depending on the SCS. Each slot may include a variable number of symbol periods (e.g., 7, 12, or 14 symbols), depending on the SCS. An index may be assigned to the symbol periods in each slot. A subslot structure may refer to a transmission time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols). Each symbol in a slot may be configured as a link direction for data transmission (e.g., DL, UL, or flexible), and the link direction used for each subframe may be dynamically switched. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information.

[0074] In NR, synchronization signal blocks (SS) are transmitted. In some aspects, each SSB can be transmitted in a burst, where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and / or beam refinement). The SSB includes the PSS, SSS, and the two-symbol PBCH. The SSB can be transmitted at fixed time slot positions (such as Figure 3 ) is transmitted in the codeword 0-3 shown in . PSS and SSS can be used by UE 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 the radio frame, SS burst set periodicity, system frame number, etc. SSB can be organized into SS bursts to support beam sweeping. Further system information (such as remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. SSB can be transmitted up to 64 times, for example, up to 64 different beam directions for millimeter waves. Multiple transmissions of SSB are called SS burst sets. SSBs in an SS burst set can be transmitted in the same frequency region, while SSBs in different SS burst sets can be transmitted in different frequency regions.

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

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

[0077] The operational characteristics of a gNB in ​​an NR communication system may depend on the frequency range (FR) in which the system operates. The frequency range may include one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band). The communication system (e.g., one or more gNBs and UEs) may operate in one or more operating bands.

[0078] A control resource set (CORESET) for an orthogonal frequency division multiple access (OFDMA) system (e.g., a communication system that uses an OFDMA waveform to transmit a physical downlink control channel (PDCCH)) may include one or more sets of control resources (e.g., time and frequency resources) within the system bandwidth that are configured to communicate the PDCCH. Within each CORESET, one or more search spaces (e.g., a common search space (CSS), a UE-specific search space (USS), etc.) may be defined for a given UE. A search space is generally an area or portion where a communication device (e.g., a UE) can search for (e.g., monitor) control information.

[0079] A CORESET may be defined in units of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) tones in one symbol period (e.g., the symbol period of a slot), where one tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). A set of CCEs may be used to transmit a New Radio PDCCH (NR-PDCCH), where different numbers of CCEs in a set are used to transmit the NR-PDCCH using different aggregation levels. Multiple CCE sets may be defined as a search space for a UE. The gNB may transmit the NR-PDCCH to the UE in a set of CCEs, referred to as decoding candidates, within the search space for the UE. The UE may receive the NR-PDCCH by searching for (e.g., monitoring) and decoding the NR-PDCCH in the search space.

[0080] During initial access, the UE may identify the initial CORESET (e.g., referred to as CORESET#0) configuration from an indication in system information (e.g., in a Master Information Block (MIB) carried in the PBCH) (e.g., pdcchConfigSIB1). This initial CORESET may then be used to configure the UE (e.g., along with other CORESETs and / or bandwidth parts via dedicated (UE-specific) signaling). When the UE detects a control channel in the CORESET, the UE attempts to decode the control channel, and the UE communicates with the transmitting BS (e.g., transmitting cell) based on the control information provided in the decoded control channel.

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

[0082] Given this index, the UE can look up or locate the CORESET configuration (this initial CORESET configured via the MIB is generally referred to as CORESET #0). This can be done based on one or more tables of CORESET configurations. These configurations (including a single table scenario) may include various subsets of indices indicating valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of indices in the table.

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

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

[0085] The BS may also transmit control signaling. In some scenarios, the BS sends control signaling to the UE (e.g., Figure 1804 ). The UE 120 (shown in FIG. 1 ) transmits control signaling to the UE 120. The PDCCH may schedule the PDSCH 806. The BS then transmits the PDSCH 806 to the UE. The UE may receive the MIB in the SS / PBCH block 802, determine an index, look up the CORESET configuration based on the index, and determine the CORESET 804 from the CORESET configuration and the SS / PBCH block. The UE may then monitor the CORESET 804, decode the PDCCH in the CORESET 804, and receive the PDSCH 806 assigned by the PDCCH.

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

[0087] As discussed above, aspects of the present disclosure relate to uplink transmit beam status using transmission configuration indication (TCI).

[0088] It is desirable for a user equipment (UE) to know which assumptions it can make about the channels used for different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode the transmitted signal (e.g., the physical downlink control channel (PDCCH) or the physical downlink shared channel (PDSCH)). It is also important to enable the UE to report relevant channel state information (CSI) to the base station (BS) (e.g., the next generation Node B (gNB)) for scheduling, link adaptation, and / or beam management purposes. In New Radio (NR), the concepts of Quasi Co-location (QCL) and state are used to convey information about these assumptions.

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

[0090] In some cases, a UE may be configured with up to M TCI states. The configuration of the M TCI states may be via higher layer signaling (e.g., the higher layer parameter TCIState). Downlink control information (DCI) indicating one of the TCI states may be used to signal the UE to decode the PDSCH based on the detected PDCCH. Each configured TCI state may include an RS set (e.g., via the higher layer parameter TCI-RS-SetConfig) that indicates different QCL assumptions between certain source and target signals.

[0091] QCL signaling can be provided to RSs and channels across scenarios involving multiple cells, such as in coordinated multi-point (CoMP) scenarios where multiple transmit reception points (TRPs) or integrated access and backhaul (IAB) nodes each have their own cell ID.

[0092] Figure 9 is a table 900 illustrating an example of an association of DL reference signals with corresponding QCL types that may be indicated by a parameter (eg, TCI-RS-SetConfig).

[0093] Table 900 shows the source RS, target RS and QCL type assumptions that can be configured by the valid UL-TCI state configuration. A target signal generally refers to a signal whose channel characteristics can be inferred by measuring those channel characteristics for the associated source signal. As mentioned above, the UE can use the source RS to determine various channel parameters depending on the associated QCL type, and use those various channel properties (determined based on the source RS) to process the target signal. Examples of source RS include phase tracking reference signal (PTRS), SSB, sounding reference signal (SRS) and / or CSI-RS (e.g., CSI-RS for beam management). Examples of target RS include aperiodic tracking reference signal (TRS), periodic TRS, PRACH, PUCCH and / or PUSCH. QCL types include QCL types A / B / C / D discussed below.

[0094] For the case of two source RSs, different QCL types can be configured for the same target RS. In the illustrative example, the synchronization signal block (SSB) is associated with type C QCL for periodic TRS (P-TRS), while the CSI-RS for beam management (CSI-RS-BM) is associated with type D QCL.

[0095] The QCL type indicated to the UE may be based on higher layer parameters (e.g., QCL type). The QCL type may be one or a combination of the following:

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

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

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

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

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

[0101] Information elements (e.g., CORESET IE) sent via RRC signaling can convey information about the CORESET configured for the UE. The CORESET IE generally includes the CORESET ID, an indication of the frequency domain resources assigned to the CORESET (e.g., the number of RBs), the continuous time duration of the CORESET in number of symbols, and the Transmission Configuration Indicator (TCI) status.

[0102] As mentioned above, the TCI state subset provides the QCL relationship between the DL RS(s) in one RS set (e.g., TCI set) and another signal (e.g., a DMRS port for another transmission). The specific TCI state for a given UE (e.g., for a unicast PDCCH) can be communicated to the UE by the MAC-CE. The TCI state can be selected from the TCI state set communicated by the CORESET IE, where the initial CORESET (CORESET#0) is generally configured via the MIB.

[0103] Search space information can also be provided via RRC signaling. For example, the Search Space IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with a CORESET. The Search Space IE identifies the search space configured for the CORESET by a Search Space ID. In one aspect, the Search Space ID associated with CORESET#0 is Search Space ID#0. The search space is generally configured via the PBCH (e.g., carried in the MIB).

[0104] Some deployments (e.g., NR Release 15 and 16 systems) support codebook-based transmission for UL transmission. Codebook-based UL transmission can be based on BS feedback.

[0105] Figure 10is a call flow diagram illustrating an example of a conventional codebook-based UL transmission using a wideband precoder. As illustrated, the UE transmits (unprecoded) SRS with up to two SRS resources (where each resource has one, two, or four ports). The BS measures the SRS and, based on the measurement, selects one SRS resource and the wideband precoder to be applied to the SRS ports within the selected resource.

[0106] As illustrated, the BS configures the selected SRS resources for the UE via the SRS Resource Indicator (SRI) and the wideband precoder for the UE via the Transmit Precoder Matrix Indicator (TPMI). For dynamic grants, the SRI and TPMI can be configured via DCI format 0_1. For configured grants (e.g., for semi-persistent uplink), the SRI and TPMI can be configured via RRC or DCI.

[0107] The UE determines selected SRS resources according to the SRI and precoding according to the TPMI, and transmits the PUSCH accordingly.

[0108] Aspects of the present disclosure relate to techniques for applying uplink TCI states with downlink reference signals to codebook-based physical uplink transmissions.

[0109] Example uplink TCI with downlink RS for codebook-based PUSCH transmission

[0110] Aspects of the present disclosure may facilitate applying uplink (UL) transmission configuration indicator (TCI) states to codebook-based physical uplink shared channel (PUSCH) transmissions, such as those described above.

[0111] As mentioned above, the uplink TCI state may provide a mechanism for indicating what parameters to use to (transmit and) decode uplink traffic. The uplink TCI state may have a downlink source reference signal (RS) to indicate the beam used for uplink PUSCH transmission, as shown in FIG. Figure 9 As explained in the third line of .

[0112] However, without sounding reference signal (SRS) transmission, the BS may not be able to determine (and indicate) the precoding metric and target rank of the uplink TCI codebook for PUSCH transmission.

[0113] According to aspects of the present disclosure, uplink TCI states with downlink RSs may be applied to codebook-based PUSCH transmission.

[0114] Figure 111 illustrates example operations 1100 for wireless communications by a UE in accordance with certain aspects of the present disclosure. Operations 1100 may be performed, for example, by a UE (e.g., UE 120a in wireless communication network 100). Operations 1100 may be implemented as a process on one or more processors (e.g., Figure 2 Furthermore, signal transmission and reception by the UE in operation 1100 may be performed by, for example, one or more antennas (e.g., Figure 2 In certain aspects, signal transmission and / or reception by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 280).

[0115] Operations 1100 begin, at 1102, by receiving signaling of an uplink TCI state for a codebook-based target uplink transmission signal from a network entity.

[0116] At 1104, the UE determines whether the TCI state has a source downlink RS.

[0117] At 1106, the UE decides how to handle codebook-based uplink transmissions based on the determination.

[0118] Figure 12 Example operations 1200 for wireless communications by a network entity are illustrated in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a BS (e.g., BS 110a in wireless communication network 100, which may be a gNB). Operations 1200 may be complementary to operations 1200 performed by a UE. Operations 1200 may be implemented as a process on one or more processors (e.g., Figure 2 Furthermore, signal transmission and reception by the BS in operation 1200 may be performed by, for example, one or more antennas (e.g., Figure 2 In some aspects, signal transmission and / or reception by the BS may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., controller / processor 240).

[0119] Operations 1200 begin, at 1202, by signaling to a user equipment (UE) an uplink TCI state for a codebook-based target uplink transmission signal.

[0120] At 1204, the network entity determines how the UE handles codebook-based uplink transmission based on whether the TCI state has a source downlink RS.

[0121] At 1206, the network entity processes the codebook-based uplink transmission according to the determination.

[0122] In this way, the uplink TCI state with the downlink source RS can be applied to codebook-based uplink transmissions, such as PUSCH.

[0123] In some cases, the uplink TCI state with the downlink source RS may not be applied to codebook-based PUSCH transmission. Accordingly, for such codebook-based PUSCH transmission, the source RS may instead be an uplink RS (e.g., SRS).

[0124] In some cases, a first downlink RS may be transmitted to the UE, followed by an uplink TCI state with a second downlink RS. In this case, the UE may report measurements of the Transmission Rank Indication (TRI) and / or Transmit Precoding Matrix Indicator (TPMI) determination based on the first downlink RS.

[0125] In such a case, the first downlink RS used for TRI / TPMI determination may be the same as or different from the second downlink RS indicated in the uplink TCI state. The determined TRI / TPMI may be signaled in the uplink TCI state. For example, when the two downlink RSs are different, the determined TRI / TPMI may be signaled using the TCI state (and the UE may use the signaled TRI / TPMI).

[0126] Otherwise, if the two downlink RSs are of the same type, then signaling of the determined TRI / TPMI (using the UL TCI status) may not be necessary because the UE can actually learn ("memorize") the determined TRI / TPMI based on the first downlink RS (because the first downlink RS and the second downlink RS are of the same type). In some cases, the UE can determine the TRI / TPMI based on the first downlink RS.

[0127] If the uplink TCI state indicates the TRI / TPMI parameters to be used, the UE may use those signaled parameters. In one example, a single bit in the downlink control information (DCI) may indicate whether the UE may use the same or different TRI / TPMI parameters.

[0128] In some cases, the SRS resource indicator (SRI) and TRI / TPMI may be transmitted with the uplink TCI status, such as Figure 13 and Figure 14 As shown in .

[0129] Figure 13 Explains something similar to Figure 10As illustrated, the UE transmits an SRS to the base station, followed by an uplink TCI status with a downlink RS. The base station determines the TRI / TPMI based on the SRS. The base station may update the uplink TCI status to carry the determined TRI / TPMI and transmit an uplink TCI status with the downlink RS, SRS, and the determined TRI / TPMI. The UE may then transmit a PUSCH based on the TPMI signaled using UL TCI status signaling.

[0130] like Figure 14 As illustrated in , in some cases, UL TCI and SRI / TRI / TPMI may be conveyed in different signals. In the illustrated example, uplink TCI and SRI are indicated in one signal (e.g., via DCI), while TRI / TPMI is conveyed in a second signal (e.g., via MAC-CE).

[0131] Figure 15 Illustrated are methods that may include being configured to perform operations for the techniques disclosed herein (such as Figure 12 1500 includes various components (e.g., corresponding to means-plus-function components) for communicating with the communication device 1500. The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or receiver). The transceiver 1508 is configured to transmit and receive signals for the communication device 1500 (such as the various signals described herein) via an antenna 1510. The processing system 1502 can be configured to perform processing functions for the communication device 1500, including processing signals received and / or to be transmitted by the communication device 1500.

[0132] The processing system 1502 includes a processor 1504 coupled to a computer readable medium / memory 1512 via a bus 1506. In some aspects, the computer readable medium / memory 1512 is configured to store data that, when executed by the processor 1504, causes the processor 1504 to execute Figure 12Instructions (e.g., computer-executable code) for performing the operations illustrated in the description or other operations discussed herein for applying uplink TCI states with downlink reference signals to codebook-based PUSCH transmissions of various techniques. In certain aspects, the computer-readable medium / memory 1512 stores code 1514 for receiving signaling of an uplink TCI state for a codebook-based target uplink transmission signal from a network entity; code 1516 for determining whether the TCI state has a source downlink RS; and code 1518 for deciding how to handle the codebook-based uplink transmission based on the determination. In certain aspects, the processor 1504 has circuitry configured to implement the code stored in the computer-readable medium / memory 1512. Processor 1504 includes circuitry 1524 for receiving signaling of an uplink TCI state for a codebook-based target uplink transmission signal from a network entity; code 1526 for determining whether the TCI state has a source downlink RS; and circuitry 1528 for deciding how to handle the codebook-based uplink transmission based on the determination.

[0133] For example, the means for receiving (or the means for obtaining) may include Figure 2 The receiver and / or antenna(s) 252 of the UE 120a illustrated in FIG. Figure 15 Circuitry 1524 of a communication device in a communication device for receiving signaling of an uplink TCI state for a target uplink transmission signal based on a codebook from a network entity. The means for communicating may include a transmitter, a receiver, or both. The means for generating, the means for performing, the means for determining, the means for taking action, the means for determining, the means for coordinating may include a processing system, which may include one or more processors, such as Figure 2 The receive processor 258, transmit processor 264, TX MIMO processor 266 and / or controller / processor 280 of the UE 120a illustrated in FIG. Figure 15 The processing system 1502 of the communication device 1500 in FIG.

[0134] Figure 16 Illustrated are methods that may include being configured to perform operations for the techniques disclosed herein (such as Figure 1216. The communication device 1600 includes various components (e.g., corresponding to means-plus-function components) that perform the operations illustrated in FIG. 16. The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and / or receiver). The transceiver 1608 is configured to transmit and receive signals for the communication device 1600 (such as the various signals described herein) via an antenna 1610. The processing system 1602 can be configured to perform processing functions for the communication device 1600, including processing signals received and / or to be transmitted by the communication device 1600.

[0135] The processing system 1602 includes a processor 1604 coupled to a computer readable medium / memory 1612 via a bus 1606. In some aspects, the computer readable medium / memory 1612 is configured to store data that, when executed by the processor 1604, causes the processor 1604 to execute Figure 12 Instructions (e.g., computer-executable code) for performing the operations illustrated in the or other operations discussed herein for applying uplink TCI states with downlink reference signals to codebook-based PUSCH transmissions of various techniques for applying uplink TCI states with downlink reference signals to codebook-based PUSCH transmissions. In certain aspects, the computer-readable medium / memory 1612 stores code 1614 for signaling an uplink TCI state for a codebook-based target uplink transmission signal to a UE; code 1616 for determining how the UE handles codebook-based uplink transmissions based on whether the TCI state has a source downlink RS; and code 1618 for processing the codebook-based uplink transmission based on the determination. In certain aspects, the processor 1604 has circuitry configured to implement the code stored in the computer-readable medium / memory 1612. Processor 1604 includes circuitry 1624 for signaling an uplink TCI state for a codebook-based target uplink transmission signal to a UE; circuitry 1626 for determining how the UE is to process codebook-based uplink transmissions based on whether the TCI state has a source downlink RS; and circuitry 1628 for processing the codebook-based uplink transmissions based on the determination.

[0136] For example, means for transmitting (or means for outputting for transmission) may include Figure 2 The transmitter unit 254 and / or antenna(s) 252 of the UE 120a illustrated in FIG. Figure 16The circuit system 1624 of the communication device 1600 in FIG. 1 is configured to signal an uplink TCI state for a target uplink transmission signal based on a codebook to a UE. The means for communicating may include a transmitter, a receiver, or both. The means for generating, the means for performing, the means for determining, the means for taking action, the means for determining, and the means for coordinating may include a processing system that may include one or more processors, such as Figure 2 The receive processor 258, transmit processor 264, TX MIMO processor 266 and / or controller / processor 280 of the UE 120a illustrated in FIG. Figure 16 The processing system 1602 of the communication device 1600 in FIG.

[0137] Example aspects

[0138] In a first aspect, a method of wireless communication by a user equipment (UE) includes: receiving signaling of an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission signal from a network entity; determining whether the TCI state has a source downlink reference signal (RS); and deciding how to handle the codebook-based uplink transmission based on the determination.

[0139] In a second aspect, in combination with the first aspect, the codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

[0140] In a third aspect, in combination with any one of the first to second aspects, if the determination is that the uplink TCI state has a source downlink RS, the decision is not to apply the TCI state to the codebook-based uplink transmission.

[0141] In a fourth aspect, in combination with any one of the first to third aspects, uplink transmission parameters have been determined based on a first downlink RS before receiving the TCI state; the TCI state has a second downlink RS as a source downlink RS; and deciding how to handle the codebook-based uplink transmission depends at least in part on whether the first downlink RS and the second downlink RS are of the same type.

[0142] In the fifth aspect, in combination with the fourth aspect, the types of the first downlink RS and the second downlink RS include one of: a first QCL type, which indicates a QCL assumption about Doppler frequency shift, Doppler spread, average delay and delay spread; a second QCL type, which indicates a QCL assumption about Doppler frequency shift and Doppler spread; a third QCL type, which indicates Doppler frequency shift and average delay; and a fourth QCL type, which indicates a QCL assumption about spatial relationship.

[0143] In a sixth aspect, in combination with any one of the fourth and fifth aspects, if the first downlink RS and the second downlink RS are of the same type, the decision is to use previously determined transmission parameters.

[0144] In a seventh aspect, in combination with any one of the fourth to sixth aspects, if the first downlink RS and the second downlink RS are of different types, the decision is to use transmission parameters signaled using the uplink TCI state.

[0145] In an eighth aspect, in combination with the seventh aspect, in addition to the source downlink RS, the uplink transmission parameter is also indicated in a UL TCI.

[0146] In a ninth aspect, in combination with any one of the fourth to eighth aspects, the method further comprises: determining the uplink transmission parameter based on the first downlink RS before receiving the TCI state.

[0147] In a tenth aspect, in combination with any one of the fourth to ninth aspects, the first downlink RS and the second downlink RS are the same downlink RS.

[0148] In the eleventh aspect, in combination with any one of the first to tenth aspects, the method further includes: transmitting a sounding reference signal (SRS) to the network entity before receiving the uplink TCI state; and receiving uplink transmission parameters from the network entity based on the SRS; wherein the decision is to apply the uplink transmission parameters and the UL TCI state to the codebook-based uplink transmission.

[0149] In a twelfth aspect, in combination with the eleventh aspect, at least some of the uplink transmission parameters are signaled separately from the UL TCI state.

[0150] In a thirteenth aspect, in combination with any one of the eleventh and twelfth aspects, the uplink transmission parameter is indicated in a UL TCI in addition to the source downlink RS.

[0151] In a fourteenth aspect, in combination with any one of the fourth to thirteenth aspects, the uplink transmission parameter includes at least one of a transmission rank indication (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

[0152] In a fifteenth aspect, a method for wireless communication by a network entity comprises: signaling an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission signal to a user equipment (UE); determining how the UE handles codebook-based uplink transmission based on whether the TCI state has a source downlink reference signal (RS); and handling the codebook-based uplink transmission according to the determination.

[0153] In a sixteenth aspect, in combination with the fifteenth aspect, the codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

[0154] In a seventeenth aspect, in combination with the fifteenth and sixteenth aspects, if the uplink TCI state has a source downlink RS, the decision is that the UE does not apply the TCI state to the codebook-based uplink transmission.

[0155] In an eighteenth aspect, in combination with any one of aspects fifteen to seventeen, uplink transmission parameters have been determined based on a first downlink RS before sending the TCI state; the TCI state has a second downlink RS as a source downlink RS; and determining how the UE processes the codebook-based uplink transmission depends at least in part on whether the first downlink RS and the second downlink RS are of the same type.

[0156] In the nineteenth aspect, in combination with the eighteenth aspect, the types of the first downlink RS and the second downlink RS include one of: a first QCL type, which indicates a QCL assumption about Doppler frequency shift, Doppler spread, average delay and delay spread; a second QCL type, which indicates a QCL assumption about Doppler frequency shift and Doppler spread; a third QCL type, which indicates Doppler frequency shift and average delay; and a fourth QCL type, which indicates a QCL assumption about spatial relationship.

[0157] In a twentieth aspect, in combination with any one of the eighteenth to nineteenth aspects, if the first downlink RS and the second downlink RS are of the same type, the determination is that the UE uses previously determined transmission parameters.

[0158] In a twenty-first aspect, in combination with any one of aspects eighteen to twentieth, if the first downlink RS and the second downlink RS are of different types, the determination is that the UE uses transmission parameters signaled using the uplink TCI state.

[0159] In a twenty-second aspect, in combination with the twenty-first aspect, in addition to the source downlink RS, the network entity further indicates the uplink transmission parameters in an uplink TCI.

[0160] In a twenty-third aspect, in combination with any one of aspects eighteen to twenty-second, the UE determines the uplink transmission parameter based on a first downlink RS before receiving the TCI state.

[0161] In a twenty-fourth aspect, in combination with any one of the eighteenth to twenty-third aspects, the first downlink RS and the second downlink RS are the same downlink RS.

[0162] In aspect 25, in combination with any one of aspects 15 to 24, the method further includes: receiving a sounding reference signal (SRS) from the UE before sending the uplink TCI state; and transmitting uplink transmission parameters to the UE based on the SRS; wherein the determination is that the UE applies the uplink transmission parameters and the UL TCI state to the codebook-based uplink transmission.

[0163] In a twenty-sixth aspect, in combination with the twenty-fifth aspect, at least some of the uplink transmission parameters are signaled separately from the UL TCI state.

[0164] In a twenty-seventh aspect, in combination with any one of the twenty-fifth and twenty-sixth aspects, the uplink transmission parameters are indicated in a UL TCI in addition to the source downlink RS.

[0165] In a twenty-eighth aspect, in combination with any one of aspects eighteen to twenty-seven, the uplink transmission parameter comprises at least one of a transmission rank indication (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

[0166] The techniques described herein can be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the 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, and others. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and 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 named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR is an emerging wireless communication technology under development.

[0167] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and BS, next-generation Node B (gNB or g-Node B), access point (AP), distributed unit (DU), carrier, or transmit reception point (TRP) can be used interchangeably.

[0168] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0169] A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a customer premises equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor / device, a wearable device (such as a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet, etc.)), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a gaming device, an augmented reality device (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device configured to communicate via a wireless or wired medium.

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

[0171] In some scenarios, air interface access may be scheduled. For example, a scheduling entity (e.g., base station (BS), B node, eNB, gNB, etc.) may allocate resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entities may utilize resources allocated by one or more scheduling entities. The base station is not the only entity that can be used 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 communication. In some examples, a UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, UEs may communicate directly with each other in addition to communicating with the scheduling entity.

[0172] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of the specific steps and / or actions may be modified without departing from the scope of the claims.

[0173] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to encompass: 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 ordering of a, b, and c).

[0174] 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, database, or another data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Furthermore, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0175] The preceding description is provided to enable anyone 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 universal principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but rather should be granted the full scope consistent with the claim language, with references to elements in the singular not intended to mean "one and only one" (unless specifically stated otherwise) but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. All structural and functional equivalents of the various aspects described herein to those skilled in the art, now or hereafter known, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. No element of a claim should be construed under 35 USC §112(f) unless the element is explicitly recited using the phrase "means for..." or, in the case of a method claim, the element is recited using the phrase "step for..."

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

[0177] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0178] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement signal processing functions at the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., a keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art and will not be described further. The processor may be implemented using one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0179] If implemented in software, each function may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location 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 the processor so that the processor can read and write information from / to the storage medium. In an alternative embodiment, the storage medium may be integrated into the processor. As an example, the machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separate from the wireless node, all of which may be accessed by the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as a cache and / or general register file. As examples, 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 embodied in a computer program product.

[0180] A software module may include a single instruction or many instructions and may be distributed across several different code segments, between different programs, and across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that, when executed by a device (such as a processor), cause a processing system to perform various functions. These software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During the execution of the software module, the processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0181] Likewise, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless 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 Disks typically reproduce data magnetically, while discs use lasers to reproduce data optically. 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.

[0182] Thus, certain 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 stored (and / or encoded) thereon instructions, which are 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 in Figure 11 and 12 Instructions for the operations explained in .

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

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

Claims

1. A method for wireless communication by a user equipment (UE), comprising: receiving signaling of an uplink transmission configuration indicator (TCI) state for a target uplink transmission signal based on a codebook from a network entity; determining whether the uplink TCI state has a source downlink reference signal (RS); as well as A decision is made based on the determination how to process a codebook-based uplink transmission.

2. The method of claim 1, wherein: The codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

3. The method of claim 1, wherein: If the determination is that the uplink TCI state has a source downlink RS, the decision is not to apply the uplink TCI state to the codebook-based uplink transmission.

4. The method of claim 1, wherein: The uplink transmission parameter has been determined based on the first downlink RS before receiving the uplink TCI state; The uplink TCI state has a second downlink RS as a source downlink RS; as well as Deciding how to handle the codebook-based uplink transmission depends at least in part on whether the first downlink RS and the second downlink RS are of the same type.

5. The method of claim 4, wherein: Types of the first downlink RS and the second downlink RS include one of the following: a first QCL type indicating QCL assumptions regarding Doppler shift, Doppler spread, average delay, and delay spread; a second QCL type indicating a QCL assumption regarding a Doppler shift and a Doppler spread; a third QCL type indicating a Doppler shift and an average delay; as well as A fourth QCL type indicating a QCL assumption about a spatial relationship.

6. The method of claim 4, wherein: If the first downlink RS and the second downlink RS are of the same type, the decision is to use previously determined transmission parameters.

7. The method of claim 4, wherein: If the first downlink RS and the second downlink RS are of different types, the decision is to use transmission parameters signaled using the uplink TCI state.

8. The method of claim 7, wherein: In addition to the source downlink RS, the uplink transmission parameters are also indicated in the UL TCI.

9. The method of claim 4, further comprising: The uplink transmission parameter is determined based on a first downlink RS before receiving the uplink TCI state.

10. The method of claim 4, wherein: The first downlink RS and the second downlink RS are the same downlink RS.

11. The method of claim 1, further comprising: transmitting a sounding reference signal (SRS) to the network entity before receiving the uplink TCI state; as well as receiving uplink transmission parameters from the network entity based on the SRS; The decision is to apply the uplink transmission parameters and the uplink TCI state to the codebook-based uplink transmission.

12. The method of claim 11, wherein: At least some of the uplink transmission parameters are signaled separately from the uplink TCI state.

13. The method of claim 11, wherein: In addition to the source downlink RS, the uplink transmission parameters are also indicated in the uplink TCI.

14. The method of claim 4, wherein: The uplink transmission parameter includes at least one of a transmission rank indication (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

15. A method for wireless communication by a network entity, comprising: signaling, to a user equipment (UE), a state of an uplink transmission configuration indicator (TCI) for a target uplink transmission signal based on a codebook; determining how the UE processes codebook-based uplink transmissions based on whether the uplink TCI state has a source downlink reference signal (RS); as well as The codebook-based uplink transmission is processed according to the determination.

16. The method of claim 15, wherein: The codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

17. The method of claim 15, wherein: If the uplink TCI state has a source downlink RS, the determination is that the UE does not apply the uplink TCI state to the codebook-based uplink transmission.

18. The method of claim 15, wherein: The uplink transmission parameter has been determined based on the first downlink RS before sending the uplink TCI state; The uplink TCI state has a second downlink RS as a source downlink RS; as well as Determining how the UE processes the codebook-based uplink transmission depends at least in part on whether the first downlink RS and the second downlink RS are of the same type.

19. The method of claim 18, wherein: Types of the first downlink RS and the second downlink RS include one of the following: a first QCL type indicating QCL assumptions regarding Doppler shift, Doppler spread, average delay, and delay spread; a second QCL type indicating a QCL assumption regarding a Doppler shift and a Doppler spread; a third QCL type indicating a Doppler shift and an average delay; as well as A fourth QCL type indicating a QCL assumption about a spatial relationship.

20. The method of claim 18, wherein: If the first downlink RS and the second downlink RS are of the same type, the determination is that the UE uses a previously determined transmission parameter.

21. The method of claim 18, wherein: If the first downlink RS and the second downlink RS are of different types, the determination is that the UE uses transmission parameters signaled using the uplink TCI state.

22. The method of claim 21, wherein: In addition to the source downlink RS, the network entity also indicates the uplink transmission parameters in an uplink TCI.

23. The method of claim 18, wherein: The UE determines the uplink transmission parameter based on a first downlink RS before receiving the uplink TCI state.

24. The method of claim 18, wherein: The first downlink RS and the second downlink RS are the same downlink RS.

25. The method of claim 15, further comprising: receiving a sounding reference signal (SRS) from the UE before sending the uplink TCI state; as well as transmitting uplink transmission parameters to the UE based on the SRS; The determination is that the UE applies the uplink transmission parameter and the uplink TCI state to the codebook-based uplink transmission.

26. The method of claim 25, wherein: At least some of the uplink transmission parameters are signaled separately from the uplink TCI state.

27. The method of claim 25, wherein: In addition to the source downlink RS, the uplink transmission parameters are also indicated in the uplink TCI.

28. The method of claim 18, wherein: The uplink transmission parameter includes at least one of a transmission rank indication (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

29. A wireless communication device, comprising: at least one processor; as well as A memory coupled to the at least one processor, the memory comprising code executable by the at least one processor to cause the apparatus to: receiving signaling of an uplink transmission configuration indicator (TCI) state for a target uplink transmission signal based on a codebook from a network entity; determining whether the uplink TCI state has a source downlink reference signal (RS); as well as A decision is made based on the determination how to process a codebook-based uplink transmission.

30. A wireless communication device, comprising: at least one processor; as well as A memory coupled to the at least one processor, the memory comprising code executable by the at least one processor to cause the apparatus to: signaling, to a user equipment (UE), a state of an uplink transmission configuration indicator (TCI) for a target uplink transmission signal based on a codebook; determining how the UE processes codebook-based uplink transmissions based on whether the uplink TCI state has a source downlink reference signal (RS); as well as The codebook-based uplink transmission is processed according to the determination.

Images