Applying uplink transmission configuration indicator status 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. One example method generally includes receiving, from a network entity, signaling of an uplink transmission configuration indicator (TCI) state of a codebook-based target uplink transmission signal, determining whether the TCI state has a source downlink reference signal (RS), and deciding how to handle a codebook-based uplink transmission based on the determination.

Description

[0001] This application is a divisional application of the patent application for invention titled "Applying Uplink Transmission Configuration Indicator Status with Downlink Reference Signals to Codebook-Based Transmissions" with an international filing date of December 18, 2020, an application number of 202080086485.4 (international application number PCT / US2020 / 065978).

[0002] Cross-reference to Related Applications

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

[0004] Aspects of the present disclosure relate to wireless communication, and more particularly, to techniques for applying an uplink transmission configuration indicator (TCI) status with a downlink reference signal to codebook-based physical uplink shared channel (PUSCH) transmissions. Background Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, 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 just a few examples.

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

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

[0008] The systems, methods, and devices of the present disclosure each have several aspects, where no single aspect alone is responsible for their desirable attributes. Without limiting the scope of the present disclosure as expressed by the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "DETAILED DESCRIPTION," it will be understood how the features of the present disclosure provide advantages, including improved communication between an access point and a station in a wireless network.

[0009] Certain aspects of the subject matter described in the present disclosure may be implemented in a method for wireless communication performed by a user equipment (UE). The method generally includes: receiving, from a network entity, signaling of 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 how to process the codebook-based uplink transmission based on the determination.

[0010] Certain aspects of the present disclosure provide a method for wireless communication by a network entity. The method generally includes: sending, to a UE, signaling of an uplink TCI state for a codebook-based target uplink transmission signal. The method generally includes: determining how the UE processes the codebook-based uplink transmission based on whether the TCI state has a source downlink RS. The method generally includes: processing the codebook-based uplink transmission according to the determination.

[0011] 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 perform the following operations: receive signaling of an uplink TCI state for a target uplink transmission signal based on a codebook from a network entity. The memory generally includes code executable by the at least one processor to cause the apparatus to perform the following operations: 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 perform the following operations: decide how to process the codebook-based uplink transmission based on the determination.

[0012] 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 perform the following operations: send signaling of an uplink TCI state for a target uplink transmission signal based on a codebook to a UE. The memory generally includes code executable by the at least one processor to cause the apparatus to perform the following operations: decide how the UE processes the 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 perform the following operations: process the codebook-based uplink transmission according to the determination.

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

[0014] Certain aspects of this disclosure provide a device for wireless communication. The device generally includes: means for sending signaling of an uplink TCI state for a target uplink transmission signal based on a codebook to a UE. The device generally includes: means for deciding how the UE processes the codebook-based uplink transmission based on whether the TCI state has a source downlink RS. The device generally includes: means for processing the codebook-based uplink transmission according to the determination.

[0015] Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium storing computer-executable code for wireless communication. The computer-readable medium generally includes: code for receiving, from a network entity, signaling of 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 process the codebook-based uplink transmission.

[0016] Certain aspects of the present disclosure provide a computer-readable medium storing computer-executable code for wireless communication. The computer-readable medium generally includes: code for sending, to a UE, signaling of an uplink TCI state for a codebook-based target uplink transmission signal. The computer-readable medium generally includes: code for determining, based on whether the TCI state has a source downlink RS, how the UE processes the codebook-based uplink transmission. The computer-readable medium generally includes: code for processing the codebook-based uplink transmission according to the determination.

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

[0018] To understand in detail the manner in which the above-recited features of the present disclosure are used, a more particular description of the above briefly summarized subject matter may be had with reference to the aspects, some of which are illustrated in the drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

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

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

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

[0022] Figure 4 is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) in accordance with certain aspects of the present disclosure.

[0023] Figure 5 is a diagram showing an example for implementing a communication protocol stack according to certain aspects of the present disclosure.

[0024] Figure 6 Illustrates an example of a frame format for a New Radio (NR) system according to certain aspects of the present disclosure.

[0025] Figure 7 Illustrates how different beams can be used to transmit different Synchronization Signal Blocks (SSBs) according to certain aspects of the present disclosure.

[0026] Figure 8 Shows an exemplary transmission resource mapping according to aspects of the present disclosure.

[0027] Figure 9 Illustrates an example of a Quasi-Co-Location (QCL) relationship according to certain aspects of the present disclosure.

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

[0029] Figure 11 Is a flowchart illustrating an example operation for wireless communication by a User Equipment (UE) according to certain aspects of the present disclosure.

[0030] Figure 12 Is a flowchart illustrating an example operation for wireless communication by a network entity according to certain aspects of the present disclosure.

[0031] Figure 13 Is a call flow diagram illustrating an example of codebook-based UL transmission using uplink TCI state.

[0032] Figure 14 Is a call flow diagram illustrating an example of codebook-based UL transmission using uplink TCI state.

[0033] Figure 15 Illustrates a communication device according to aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.

[0034] Figure 16 Illustrates a communication device according to aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.

[0035] For ease of understanding, the same reference numerals have been used, where possible, to designate identical elements common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. Detailed Description

[0036] Aspects of the present disclosure provide an apparatus, a method, a processing system, and a computer-readable medium for applying an uplink transmission configuration indicator (TCI) state having a downlink reference signal to a codebook-based physical uplink shared channel (PUSCH) transmission.

[0037] The following description provides examples of applying an uplink TCI state having a downlink reference signal to a codebook-based transmission 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 the present disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality that supplement or are additional to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" need not be construed as superior or better than other aspects.

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

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

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

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

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

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

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

[0045] In Figure 1 the example shown, BS110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS110x can be a pico BS for pico cell 102x. BS110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more cells.

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

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

[0048] Figure 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which can be in Figure 1Implemented in the wireless communication network 100 described in the [description]. The 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be the central unit (CU) of the distributed RAN 200. The backhaul interface to the next-generation core network (NG-CN) 204 may be terminated at the ANC 202. The backhaul interface to the adjacent next-generation access node (NG-AN) 210 may be terminated at the ANC 202. The ANC 202 may include one or more transmit receive points (TRP) 208 (e.g., cell, BS, gNB, etc.).

[0049] The TRP 208 may be a distributed unit (DU). The TRP 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not shown). For example, for RAN sharing, radio as a service (RaaS), and service-specific ANC deployments, the TRP 208 may be connected to more than one ANC. Each TRP 208 may include one or more antenna ports. The TRP 208 may be configured to serve traffic to the UE individually (e.g., dynamic selection) or jointly (e.g., joint transmission).

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

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

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

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

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

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

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

[0057] Figure 4 An example of the BS110 and UE 120 components (as depicted in Figure 1 ) is illustrated, which may be used to implement aspects of the present disclosure.

[0058] At the BS110, 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., a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, and / or reference symbols, if applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 432a to 432t. Each modulator may process its respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 432a to 432t may be transmitted via antennas 434a to 434t, respectively.

[0059] At the UE 120, antennas 452a through 452r may receive downlink signals from the base station 110 and may provide the received signals to a demodulator (DEMOD) in each of the transceivers 454a through 454r, respectively. Each demodulator may condition (e.g., filter, amplify, down-convert, and digitize) the respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 456 may obtain received symbols from all of the demodulators in the transceivers 454a through 454r, perform MIMO detection on the received symbols when applicable, and provide detected symbols. The receive processor 458 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 460, and provide the decoded control information to the controller / processor 480.

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

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

[0062] The antennas 252, processors 266, 258, 264, and / or controller / processor 280 of the UE 120 and / or the antenna 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. For example, as Figure 4As shown, in accordance with aspects described herein, the controller / processor 240 of BS110a has a TCI state manager 241 that processes the codebook-based uplink transmission based on how the UE processes the codebook-based uplink transmission. As Figure 4 As shown, in accordance with aspects described herein, the controller / processor 280 of UE 120a has a TCI state manager 281 that determines how to process the codebook-based uplink transmission based on whether the TCI state has a source downlink reference signal (RS). Although shown at the controller / processor, other components of UE 120a and BS110a may also be used to perform the operations described herein.

[0063] Figure 5 FIG. 500 illustrates a diagram showing an example for implementing a communication protocol stack in accordance with aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting uplink-based mobility). FIG. 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 media access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, these layers of the protocol stack may be implemented as separate software modules, parts of a processor or ASIC, parts of non-collocated devices connected by a communication link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in the protocol stack for network access devices (e.g., AN, CU, and / or DU) or UEs.

[0064] The first option 505-a shows a split implementation of the protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., Figure 2 ANC 202 in Figure 2 and a distributed network access device (e.g.,

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

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

[0067] 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 Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers, which are also often referred to as frequency tones, frequency slots, etc. Each subcarrier can be modulated with data. The modulation symbols can be transmitted in the frequency domain under OFDM and in the time domain under 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 consecutive subcarriers. The system bandwidth can also be divided into subbands. For example, one subband can cover multiple RBs. NR can support a base Subcarrier Spacing (SCS) of 15KHz, and other SCSs can be defined relative to the base SCS (e.g., 30kHz, 60kHz, 120kHz, 240kHz, etc.).

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

[0069] 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 PSS, SSS, and a two-symbol PBCH. The SSB can be transmitted in fixed time slot positions (such as Figure 3 symbol 0-3 as shown). The PSS and SSS can be used by the UE for cell search and acquisition. The PSS can provide half-frame timing, and the SSS can provide CP length and frame timing. The PSS and SSS can provide cell identity. The 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. The 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. The SSB can be transmitted up to 64 times, e.g., up to 64 different beam directions for millimeter wave. Multiple transmissions of the SSB are referred to as an SS burst set. The SSBs in an SS burst set can be transmitted in the same frequency region, while the SSBs in different SS burst sets can be transmitted in different frequency regions.

[0070] As Figure 7 shown, the SS blocks can be organized into SS burst sets to support beam sweeping. As shown, each SSB within the burst set can be transmitted using a different beam, which can help the UE quickly acquire both the 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.

[0071] Some deployment scenarios may include one or two NR deployment options. A certain option can be configured for non-standalone (NSA) and / or standalone (SA) options. A standalone cell may need to broadcast both the SSB and the Remaining Minimum System Information (RMSI) (e.g., using SIB1 and SIB2). A non-standalone cell may only need to broadcast the SSB and not the RMSI. In a single carrier in NR, multiple SSBs can be sent at different frequencies and can include different types of SSBs.

[0072] The operating characteristics of the gNB in an NR communication system can depend on the frequency range (FR) of system operation. The frequency range can include one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band, etc.). The communication system (e.g., one or more gNBs and UEs) can operate in one or more operating bands.

[0073] 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) configured within the system bandwidth for conveying 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 a region or portion where a communication device (e.g., a UE) can look for (e.g., monitor) control information.

[0074] A CORESET may be defined in terms of resource element groups (REGs). Each REG may include a fixed number (e.g., twelve) of subcarriers in one symbol period (e.g., the symbol period of a time slot), where one subcarrier in one symbol period is called 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 the set are used to transmit the NR-PDCCH using different aggregation levels. Multiple sets of CCEs may be defined as search spaces for a UE. The gNB may transmit the NR-PDCCH to the UE in a set of CCEs that are referred to as decoding candidates within the search space for the UE. The UE may receive the NR-PDCCH by searching (e.g., monitoring) and decoding the NR-PDCCH in the search space.

[0075] During initial access, the UE may identify an initial CORESET (e.g., referred to as CORESET#0) configuration from an indication (e.g., pdcchConfigSIB1) in the system information (e.g., in the master information block (MIB) carried in the PBCH). This initial CORESET may then be used to configure the UE (e.g., together 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., the transmitting cell) according to the control information provided in the decoded control channel.

[0076] When the UE is connected to a cellular cell (or BS), the UE can receive the Master Information Block (MIB). The MIB can be in the Synchronization Signal and Physical Broadcast Channel (SS / PBCH) block on the synchronization raster (e.g., in the PBCH of the SS / PBCH block). In some scenarios, this synchronization raster can correspond to a Synchronization Signal Block (SSB). Based on the frequency of the synchronization raster, the UE can determine the operating band of the cellular cell. Based on the operating band of the cellular cell, the UE can determine the minimum channel bandwidth and the Subcarrier Spacing (SCS) of the channel. The UE can then determine an index according to the MIB (e.g., four bits in the MIB, conveying an index in the range 0 - 15).

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

[0078] Alternatively or additionally, the UE can select a search - space CORESET configuration table from several tables of CORESET configurations. These configurations can be based on the minimum channel bandwidth and SCS. The UE can 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 the selected table), the UE can then determine the CORESET to be monitored based on the location (in time and frequency) of the SS / PBCH block and the CORESET configuration (as mentioned above).

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

[0080] The BS can also transmit control signaling. In some scenarios, the BS transmits in the PDCCH in the CORESET 804 (time / frequency resources) to the UE (e.g., Figure 1The UE 120) shown in the figure transmits control signaling. The PDCCH can schedule the PDSCH 806. The BS then transmits the PDSCH 806 to the UE. The UE can receive the MIB in the SS / PBCH block 802, determine the 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 can then monitor the CORESET 804, decode the PDCCH in the CORESET 804, and receive the PDSCH 806 allocated by the PDCCH.

[0081] Different CORESET configurations can have different parameters that define the corresponding CORESET. For example, each configuration can 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 position in frequency (e.g., 0 - 38 RBs).

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

[0083] It is desirable for a user equipment (UE) to know what assumptions the UE 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., physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH)). For purposes of scheduling, link adaptation, and / or beam management, it is also important for the UE to be able to report relevant channel state information (CSI) to a base station (BS) (e.g., a next-generation Node B (gNB)). In New Radio (NR), the concepts of quasi-co-location (QCL) and state are used to convey information about these assumptions.

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

[0085] 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 TCI state). The UE may be signaled to decode a PDSCH based on a detected PDCCH with downlink control information (DCI) indicating one of the TCI states. Each configured TCI state may include a set of RSs (e.g., via the higher layer parameter TCI-RS-SetConfig), which indicates different QCL assumptions between certain source signals and target signals.

[0086] QCL signaling may be provided for RSs and channels across scenarios involving multiple cells, such as in a coordinated multipoint (CoMP) scenario where multiple transmit receive points (TRPs) or integrated access and backhaul (IAB) nodes each have their own cell IDs.

[0087] Figure 9 Table 900 is an example table illustrating the association of DL reference signals with corresponding QCL types that can be indicated by a parameter (e.g., TCI-RS-SetConfig).

[0088] Table 900 shows source RSs, target RSs, and QCL type assumptions that can be configured by a 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 an associated source signal. As mentioned above, a UE can use a source RS to determine various channel parameters depending on the associated QCL type, and use those various channel attributes (determined based on the source RS) to process the target signal. Examples of source RSs include phase tracking reference signals (PTRS), SSBs, sounding reference signals (SRS), and / or CSI-RS (e.g., CSI-RS for beam management). Examples of target RSs include aperiodic tracking reference signals (TRS), periodic TRS, PRACH, PUCCH, and / or PUSCH. QCL types include QCL types A / B / C / D discussed below.

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

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

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

[0092] QCL Type B: {Doppler shift, Doppler spread},

[0093] QCL Type C: {Average delay, Doppler shift}, and

[0094] QCL Type D: {Spatial Rx parameters},

[0095] The spatial QCL assumption (QCL Type D) can be used to assist the UE in selecting an analog receive (Rx) beam (e.g., during a beam management procedure). For example, the SSB resource indicator can indicate that the same beam used for a previous reference signal should be used for a subsequent transmission.

[0096] The information element sent via RRC signaling (e.g., the CORESET IE) 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 terms of symbol numbers, and the transmission configuration indicator (TCI) state.

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

[0098] The 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 the search space ID. In one aspect, the search space ID associated with CORESET#0 is search space ID#0. The search space is generally configured via the PBCH (e.g., carried in the MIB).

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

[0100] Figure 10It is a call flow diagram illustrating an example of a conventional codebook - based UL transmission using a wide - band precoder. As illustrated, the UE transmits (un - precoded) SRS with up to 2 SRS resources, where each resource has 1, 2, or 4 ports. The BS measures the SRS and based on the measurement, selects one SRS resource and a wide - band precoder to be applied to the SRS ports within the selected resource.

[0101] As illustrated, the BS configures the selected SRS resource for the UE via a SRS resource indicator (SRI) and configures the wide - band precoder for the UE via a transmit precoder matrix indicator (TPMI). For a dynamic grant, the SRI and TPMI can be configured via DCI format 0_1. For a configured grant (e.g., for semi - persistent uplink), the SRI and TPMI can be configured via RRC or DCI.

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

[0103] Aspects of the present disclosure relate to techniques for applying an uplink TCI state with a downlink reference signal to a codebook - based physical uplink transmission.

[0104] Receiving signaling of an uplink transmission configuration indicator (TCI) state for a codebook - based target uplink transmission signal from a network entity;

[0105] Determining whether the uplink TCI state has a source downlink reference signal (RS); and

[0106] Deciding how to handle the codebook - based uplink transmission based on the determination.

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

[0108] Aspects of the present disclosure can help apply an uplink (UL) transmission configuration indicator (TCI) state to a codebook - based physical uplink shared channel (PUSCH) transmission, such as those PUSCH transmissions described above.

[0109] As mentioned above, the uplink TCI state can provide a mechanism for indicating what parameters to use to (transmit and) decode uplink traffic. The uplink TCI state can have a downlink source reference signal (RS) to indicate the beam for uplink PUSCH transmission, as illustrated in the Figure 9 third row of the figure showing the uplink TCI state.

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

[0111] According to aspects of the present disclosure, uplink TCI states with downlink RSs can be applied to codebook-based PUSCH transmissions.

[0112] Figure 11 An example operation 1100 for wireless communication by a UE in accordance with some aspects of the present disclosure is illustrated. Operation 1100 can be performed, for example, by a UE (e.g., UE 120a in the wireless communication network 100). Operation 1100 can be implemented as software components executed and run on one or more processors (e.g., Figure 2 the controller / processor 280). Additionally, signal transmission and reception by the UE in operation 1100 can be implemented, for example, by one or more antennas (e.g., Figure 2 the antenna 252). In some aspects, signal transmission and / or reception by the UE can be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., the controller / processor 280).

[0113] Operation 1100 begins at 1102 with receiving, from a network entity, signaling of an uplink TCI state for a codebook-based target uplink transmission signal.

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

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

[0116] Figure 12 An example operation 1200 for wireless communication by a network entity in accordance with some aspects of the present disclosure is illustrated. Operation 1200 can be performed, for example, by a BS (e.g., BS110a in the wireless communication network 100, which can be a gNB). Operation 1200 can be complementary to operation 1200 performed by the UE. Operation 1200 can be implemented as software components executed and run on one or more processors (e.g., Figure 2 the controller / processor 240). Additionally, signal transmission and reception by the BS in operation 1200 can be implemented, for example, by one or more antennas (e.g., Figure 2 the antenna 234). In some aspects, signal transmission and / or reception by the BS can be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., the controller / processor 240).

[0117] Operation 1200 starts at 1202 with signaling to a user equipment (UE) of an uplink TCI state for a codebook-based target uplink transmission signal.

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

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

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

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

[0122] 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 for transmission rank indication (TRI) and / or transmit precoding matrix indicator (TPMI) determination based on the first downlink RS.

[0123] In such cases, the first downlink RS 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 is signaled with the TCI state (and the UE may use the signaled TRI / TPMI).

[0124] Otherwise, if the two downlink RSs are of the same type, signaling of the determined TRI / TPMI may not be required (with the UL TCI state) because the UE can actually learn (“memorize”) the determined TRI / TPMI based on the first downlink RS (since the first downlink RS is of the same type as the second downlink RS). In some cases, the UE may determine the TRI / TPMI based on the first downlink RS.

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

[0126] In some cases, the uplink TCI state can be used to transmit the SRS resource indicator (SRI) and TRI / TPMI, as Figure 13 and Figure 14 shown.

[0127] Figure 13 Illustrates a call flow for codebook-based PUSCH transmission similar to Figure 10 As illustrated, the UE transmits SRS to the BS, and then transmits an uplink TCI state with a downlink RS. The BS determines the TRI / TPMI based on the SRS. The BS may update the uplink TCI state to carry the determined TRI / TPMI, and transmit the uplink TCI state with the downlink RS, SRS, and the determined TRI / TPMI. The UE may then transmit the PUSCH based on the TPMI signaled with the UL TCI state.

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

[0129] Figure 15 Illustrates a communication device 1600 that may include various components (e.g., corresponding to apparatus plus function components) configured to perform operations for the techniques disclosed herein, such as Figure 12 the operations illustrated. 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 may 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.

[0130] The processing system 1502 includes a processor 1504 coupled to a computer-readable medium / memory 1512 via a bus 1506. In certain aspects, the computer-readable medium / memory 1512 is configured to store instructions that, when executed by the processor 1504, cause the processor 1504 to perform Figure 12Instructions (e.g., computer-executable code) for the operations described herein or for other operations for performing the various techniques discussed herein for applying an uplink TCI state with a downlink reference signal to a codebook-based PUSCH transmission. In some 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 determining how to process the codebook-based uplink transmission based on the determination. In some aspects, the processor 1504 has circuitry configured to implement the code stored in the computer-readable medium / memory 1512. The 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 determining how to process the codebook-based uplink transmission based on the determination.

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

[0132] Figure 16 illustrates that may include circuitry configured to perform operations for the techniques disclosed herein, such as Figure 12A communication device 1600 of various components (e.g., corresponding to apparatus-plus-function components) of the operations described herein. The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and / or a receiver). The transceiver 1608 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1600 via an antenna 1610. The processing system 1602 may 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.

[0133] 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 instructions (e.g., computer-executable code) that, when executed by the processor 1604, cause the processor 1604 to perform Figure 12 the operations described herein or other operations for performing the various techniques discussed herein for applying an uplink TCI state with a downlink reference signal to a codebook-based PUSCH transmission. In some aspects, the computer-readable medium / memory 1612 stores code 1614 for signaling to a UE an uplink TCI state for a codebook-based target uplink transmission signal; code 1616 for determining how the UE processes a codebook-based uplink transmission based on whether the TCI state has a source downlink RS; and code 1618 for processing the codebook-based uplink transmission according to the determination. In some aspects, the processor 1604 has circuitry configured to implement the code stored in the computer-readable medium / memory 1612. The processor 1604 includes circuitry 1624 for signaling to a UE an uplink TCI state for a codebook-based target uplink transmission signal; circuitry 1626 for determining how the UE processes a codebook-based uplink transmission based on whether the TCI state has a source downlink RS; and circuitry 1628 for processing the codebook-based uplink transmission according to the determination.

[0134] For example, a device for transmitting (or a device for outputting for transmission) may include Figure 2 the transmitter unit 254 of the UE120a and / or (an) antenna 252 as illustrated herein, and / or Figure 16The circuitry 1624 of the communication device 1600 in for signaling to a UE an uplink TCI state for a codebook-based target uplink transmission signal. The apparatus for communication can include a transmitter, a receiver, or both. The apparatus for generating, the apparatus for performing, the apparatus for determining, the apparatus for taking action, the apparatus for determining, the apparatus for coordinating can include a processing system that can include one or more processors, such as Figure 2 the receiving processor 258, the transmitting processor 264, the TX MIMO processor 266, and / or the controller / processor 280 of the UE 120a illustrated in and / or Figure 16 the processing system 1602 of the communication device 1600 in .

[0135] Example aspect

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

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

[0138] 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 determination is not to apply the TCI state to the codebook-based uplink transmission.

[0139] 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 the source downlink RS; and determining how to process 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.

[0140] In a fifth aspect, in combination with the fourth aspect, the types of the first downlink RS and the second downlink RS include one of the following: a first QCL type that indicates QCL assumptions regarding Doppler shift, Doppler spread, mean delay, and delay spread; a second QCL type that indicates QCL assumptions regarding Doppler shift and Doppler spread; a third QCL type that indicates Doppler shift and mean delay; and a fourth QCL type that indicates QCL assumptions regarding spatial relationship.

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

[0142] 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 the transmission parameters signaled using the uplink TCI state.

[0143] In an eighth aspect, in combination with the seventh aspect, in addition to the source downlink RS, the uplink transmission parameters are also indicated in the UL TCI.

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

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

[0146] In an 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.

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

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

[0149] 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 indicator (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

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

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

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

[0153] In an eighteenth aspect, in combination with any one of the fifteenth to seventeenth aspects, the uplink transmission parameter has been determined based on a first downlink RS before the TCI state is sent; the TCI state has a second downlink RS as the 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.

[0154] In a nineteenth aspect, in combination with the eighteenth aspect, the types of the first downlink RS and the second downlink RS include one of the following: a first QCL type that indicates a QCL assumption regarding Doppler shift, Doppler spread, average delay, and delay spread; a second QCL type that indicates a QCL assumption regarding Doppler shift and Doppler spread; a third QCL type that indicates Doppler shift and average delay; and a fourth QCL type that indicates a QCL assumption regarding spatial relation.

[0155] 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 the previously determined transmission parameter.

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

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

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

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

[0160] In a twenty - fifth aspect, in combination with any one of the fifteenth to twenty - fourth aspects, the method further includes: receiving a sounding reference signal (SRS) from the UE before transmitting the uplink TCI state; and transmitting the 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.

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

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

[0163] In a twenty - eighth aspect, in combination with any one of the eighteenth to twenty - seventh aspects, the uplink transmission parameters include at least one of a transmission rank indicator (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

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

[0165] In 3GPP, the term "cell" may 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 an NR system, the terms "cell" and BS, Next Generation Node B (gNB or g Node B), Access Point (AP), Distributed Unit (DU), carrier, or Transmission and Reception Point (TRP) may be used interchangeably.

[0166] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unconstrained access by UEs having a service subscription. A pico cell may cover a relatively small geographic area and may allow unconstrained access by UEs having a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow constrained access by UEs associated with that femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a residence, etc.). The BS for a macro cell may be referred to as a macro BS. The BS for a pico cell may be referred to as a pico BS. The BS for a femto cell may be referred to as a femto BS or a home BS.

[0167] A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a customer premise 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, a ultrabook, an appliance, a medical device or equipment, a biometric sensor / device, a wearable device (such as a smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, 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, a reality augmentation 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.

[0168] Some UEs may be considered as machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) or provide connectivity to the network, for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0169] In some scenarios, air interface access may be scheduled. For example, a scheduling entity (e.g., a base station (BS), a B node, an eNB, a gNB, etc.) may allocate resources for communication among some or all of the 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 the scheduled communication, the subordinate entities may utilize the resources allocated by one or more scheduling entities. A base station is not the only entity that can serve as a scheduling entity. In some examples, a UE may act as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the 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 a scheduling entity.

[0170] The various methods disclosed herein include one or more steps or acts for implementing the methods. These method steps and / or acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of the steps or acts is specified, the order and / or use of the specific steps and / or acts may be altered without departing from the scope of the claims.

[0171] As used herein, the phrase reciting "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

[0172] As used herein, the term "determine" covers a variety of acts. For example, "determine" may include computing, calculating, processing, deriving, researching, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Moreover, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Moreover, "determine" may include parsing, selecting, choosing, establishing, and the like.

[0173] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, wherein the recitation of a singular element is not intended to mean "one and only one" (unless specifically so stated) but "one or more." Unless specifically stated otherwise, the term "some / a" refers to one or more. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as all structural and functional equivalents are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. No element of a claim should be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for."

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

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

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

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

[0178] Software modules may include a single instruction or many instructions and may be distributed across several different code segments, among different programs, and across multiple storage media. Computer-readable media may include several software modules. These software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. These software modules may include a transmission module and a reception 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 a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may then be loaded into the general register file for execution by the processor. When referring to the functionality of a software module hereinafter, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0179] Similarly, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio, and microwave is included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and disc, where disk typically reproduces data magnetically, while disc reproduces data optically with a laser. Thus, in some aspects, a computer-readable medium may include a non-transitory computer-readable medium (e.g., a tangible medium). Additionally, for other aspects, a computer-readable medium may include a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0180] Accordingly, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored thereon (and / or encoded thereon) that can be executed by one or more processors to perform the operations described herein. For example, instructions for performing the operations described and illustrated in Figure 11 and 12 the operations described herein.

[0181] Moreover, it should be appreciated that modules and / or other suitable means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or a base station where applicable. For example, such devices can be coupled to a server to facilitate transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.) such 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. Additionally, any other suitable technology can be utilized that is adapted to provide the methods and techniques described herein to a device.

[0182] It will be understood that the claims are not limited to the exact configurations and components described above. Various modifications, substitutions, and variations can be made in the layout, operation, and details of the methods and apparatuses described above without departing from the scope of the claims.

Claims

1. A wireless communication device, comprising: at least one processor; and a memory coupled to the at least one processor, the memory including code executable by the at least one processor to cause the device to perform the following operations: receive signaling of an uplink transmission configuration indicator (TCI) state for a codebook-based target uplink transmission from a network entity; determine uplink transmission parameters; determine whether the TCI state has a source downlink reference signal (RS); and decide, based on the determination, whether to apply at least one of the uplink transmission parameters or the TCI state to the codebook-based uplink transmission.

2. The device according to claim 1, wherein the codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

3. The device according to claim 1, wherein: the uplink transmission parameters are determined based on a first downlink RS before receiving the TCI state; the TCI state has a second downlink RS as the source downlink RS; and deciding whether to apply at least one of the uplink transmission parameters or the TCI state to the codebook-based uplink transmission depends at least in part on the first downlink RS and the second downlink RS.

4. The device according to claim 3, wherein the type of at least one of the first downlink RS or the second downlink RS includes at least one of the following: a first quasi-co-location (QCL) type that indicates QCL assumptions regarding Doppler shift, Doppler spread, average delay, and delay spread; a second QCL type that indicates QCL assumptions regarding Doppler shift and Doppler spread; a third QCL type that indicates Doppler shift and average delay; or a fourth QCL type that indicates QCL assumptions regarding spatial relationship.

5. The device according to claim 3, wherein if the first downlink RS and the second downlink RS are of the same type, the decision is to use the previously determined transmission parameters.

6. The device according to claim 3, wherein: the transmission parameters are received from the network entity; and if the first downlink RS and the second downlink RS are of different types, the decision is to use the transmission parameters.

7. The device according to claim 3, wherein the uplink transmission parameters are determined based on a first downlink RS before receiving the TCI state.

8. The device according to claim 1, wherein the code is executable by the at least one processor to further cause the device to: transmit a sounding reference signal (SRS) to the network entity ； and receive the 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.

9. The apparatus according to claim 8, wherein at least some of the uplink transmission parameters are signaled separately from the UL TCI state.

10. The apparatus according to claim 1, wherein the uplink transmission parameters include at least one of a transmission rank indicator (TRI), a transmit precoding matrix indicator (TPMI), or a sounding reference signal resource indicator (SRI).

11. A wireless communication apparatus, comprising: at least one processor; and a memory coupled to the at least one processor, the memory including code executable by the at least one processor to cause the apparatus to perform the following operations: signal to a user equipment (UE) an uplink transmission configuration indicator (TCI) state for codebook-based target uplink transmission; determine whether the UE applies at least one of the uplink transmission parameters or the TCI state to the codebook-based uplink transmission based on whether the TCI state has a source downlink reference signal (RS); and process the codebook-based uplink transmission according to the determination.

12. The apparatus according to claim 11, wherein the codebook-based uplink transmission includes a physical uplink shared channel (PUSCH).

13. The apparatus according to claim 11, wherein: the uplink transmission parameters are determined based on a first downlink RS before transmitting the TCI state; the TCI state has a second downlink RS as the source downlink RS; and determining whether the UE applies at least one of the uplink transmission parameters or the TCI state to the codebook-based uplink transmission depends at least in part on the first downlink RS and the second downlink RS.

14. The apparatus according to claim 13, wherein the type of at least one of the first downlink RS or the second downlink RS includes at least one of the following: a first quasi-co-location (QCL) type that indicates QCL assumptions regarding Doppler shift, Doppler spread, average delay, and delay spread; a second QCL type that indicates QCL assumptions regarding Doppler shift and Doppler spread; a third QCL type that indicates Doppler shift and average delay; or a fourth QCL type that indicates QCL assumptions regarding spatial relationship.

15. The apparatus according to claim 13, wherein 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.

16. The apparatus according to claim 13, wherein: the transmission parameters are transmitted from the apparatus; and if the first downlink RS and the second downlink RS are of different types, the determination is that the UE uses the transmission parameters.

17. The apparatus according to claim 11, wherein the code is executable by the at least one processor to further cause the apparatus to: receive a sounding reference signal (SRS) from the UE ； and Transmit the 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.

18. The apparatus according to claim 17, wherein at least some of the uplink transmission parameters are signaled separately from the UL TCI state.

19. The apparatus according to claim 11, wherein the uplink transmission parameters include at least one of a transmission rank indicator (TRI), a transmit precoding matrix indicator (TPMI), or an SRS resource indicator (SRI).

20. A method for wireless communication at a user equipment, comprising: receiving, from a network entity, signaling of an uplink transmission configuration indicator (TCI) state for a target codebook-based uplink transmission; determining uplink transmission parameters; determining whether the TCI state has a source downlink reference signal (RS); and deciding, based on the determination, whether to apply at least one of the uplink transmission parameters or the TCI state to the codebook-based uplink transmission.

Images